Explanation:
The request is for a scheduled, standardized report (not a raw data extract) containing high-level metrics. This requires a built-in reporting tool that can format the data, apply a schedule, and automatically distribute it via email. While a custom automation could be built, the most efficient and appropriate solution uses the native reporting and scheduling feature.

Correct Option:

B. Analytics Builder:
Select the "Account Send Summary" in Reports and schedule a weekly report to be sent. This is the correct and most straightforward solution. Analytics Builder (or the Discover Reports tab) contains standard reports like "Account Send Summary." It allows an admin to schedule a report to run weekly and automatically email the formatted report (e.g., as a PDF or within the email body) to the marketing manager, meeting the exact requirement.

Incorrect Options:

A. Email Studio:
Select the 'Account Send Summary' in Tracking Reports and schedule a weekly report to be sent. The Tracking tab in Email Studio is for ad-hoc, on-demand analysis of recent sends. It does not have a native scheduling and email distribution feature for recurring reports. This would require the manager to log in each week or the admin to manually run and send it.

C. Automation Studio:
Create a Query Activity to query data from the "Sent" Data View, then use an Email activity to automate the sending of the data. While this is technically possible and would work, it is an overly complex, custom-coded solution for a simple standard report request. It requires SQL knowledge to write the query, design an email template, and format the data. The built-in scheduled report feature in Analytics Builder is the simpler, admin-friendly, out-of-the-box solution intended for this purpose.

Reference:
Analytics Builder documentation covers report scheduling and distribution, allowing users to "schedule reports to run daily, weekly, or monthly" and "email report results to any valid email address." This is the designed workflow for automated metric distribution.

Explanation
To automatically add UTM parameters to all links in outgoing emails, Marketing Cloud provides Parameter Manager. This feature appends tracking parameters—such as utm_source, utm_medium, and utm_campaign—to URLs without requiring manual edits in each email. It ensures consistent tagging for analytics platforms, including Google Analytics. Parameter Manager applies tagging at the account, email, or link level, making it the most efficient and scalable option.

Correct Option Explanation

B. Configure Parameter Manager
Parameter Manager is built specifically to automate link tagging across all emails or selected sends. It allows the admin to define default UTM parameters and automatically appends them to hyperlinks in emails, ensuring consistent and accurate tracking for analytics tools. This eliminates manual tagging and reduces errors.

Incorrect Option Explanations

A. Use Web and Mobile Analytics
Web and Mobile Analytics collects data on website or app behavior but does not tag email links. It cannot append UTM parameters automatically and is unrelated to outbound email link tracking.

C. Link a Google Analytics Account
Linking a Google Analytics account enables integration and tracking but does not automatically add UTM parameters to email links. UTM tagging must still be done manually unless Parameter Manager is used.

Reference
Salesforce Documentation: Parameter Manager Overview

Marketing Cloud Help: Automatically Tag Email Links with UTM Parameters

Trailhead: Optimize Email Tracking with Parameter Manager

Explanation:
The concern is specifically about unauthorized API access (external systems connecting to the Marketing Cloud API) and reducing related threats. The most effective, direct, and non-intrusive method to restrict access to the API—and thus reduce the threat surface—is to ensure that the API endpoint is only accessible from a pre-approved, secure set of IP addresses belonging to the trusted integrating systems. This security measure is known as IP Whitelisting.

Correct Option:

A. IP Whitelisting
IP Whitelisting (also called IP Address Restrictions) is a feature in Marketing Cloud's security settings that allows an administrator to define a list of trusted IP addresses.

When this feature is enabled, any connection attempt to the Marketing Cloud API or user interface originating from an IP address not on the approved list is automatically blocked.

This is a powerful defensive measure that drastically reduces the risk of API attacks by malicious actors attempting to access the account from unknown or unsecured networks.

Incorrect Options:

B. Field Level Encryption:
This feature protects data at rest within the Marketing Cloud database (e.g., encrypting PII fields). It is a measure for data security, not a control mechanism for restricting API access itself.

C. Advanced Audit Trail:
The Advanced Audit Trail (AAT) is a monitoring and reporting tool that records user actions and system changes (including API calls) for later investigation and compliance review. It helps identify a threat after it occurs but does not actively prevent the unauthorized API access.

D. Single Sign On Authentication (SSO):
SSO requires human users to log in using their corporate credentials, improving UI login security. However, SSO is often not used for API authentication, which typically relies on OAuth (Client ID/Secret) tokens. Even with SSO enabled, unauthorized API access via an untrusted IP would remain a threat without IP Whitelisting.

Reference:
Salesforce Marketing Cloud Security Settings Documentation (IP Address Whitelisting)

Explanation:
Separate Business Units (BUs) are used to provide complete data, user, and operational isolation between distinct brands. The strongest technical driver for separate BUs is the need for brand-specific sending infrastructure and domain reputation management. This includes using unique private domains for hosting email content (images, links), which is a core branding and deliverability requirement that cannot be shared across BUs.

Correct Option:

C. Brand-specific private domains are required for images and links.
This is a definitive reason for separate Business Units. Private Domains (like images.brandA.com and links.brandB.com) are configured at the Business Unit level. If each brand requires its own dedicated private domain for image wrapping and link tracking to maintain distinct brand identity and sender reputation, they must be housed in separate BUs, as a single BU can only have one set of private domains.

Incorrect Options:

A. A new sender profile is needed for sending transactional emails.
Sender Profiles (defining "From" name, address, reply-to) can be created and managed within a single Business Unit. You can have multiple sender profiles (e.g., orders@brandA.com, support@brandB.com) in one BU. Separate BUs are not required for this.

B. Multiple FTP users must be accommodated.
FTP Users (for Enhanced FTP access) are managed at the parent Enterprise Business Unit level, not at the child BU level. Multiple FTP users can be created and granted access to different folders within the account's central FTP, regardless of how many BUs exist. BU separation is not needed for FTP user management.

Reference:
Marketing Cloud documentation on Business Units states that a primary consideration for creating separate BUs is "managing distinct brand identities and reputations," which includes the configuration of Private Domains and Sender Authentication Packages (SAP). Since private domains are a BU-level setting, separate brands needing unique domains require separate BUs.

Explanation
When configuring Synchronized Data Sources, Marketing Cloud allows admins to apply filters to limit which Salesforce CRM records are synced. To ensure that only marketable contacts are brought into Marketing Cloud, a custom boolean field—such as Is_Marketable__c = TRUE—is the ideal filter. This allows Salesforce to control eligibility upstream and ensures that only clean, permissioned contacts enter Marketing Cloud for segmentation and sending.

Correct Option Explanation

C. Select all records where custom boolean field is true
Using a custom Salesforce boolean field (e.g., Marketable__c) gives full control over which contacts are synchronized. Admins define marketability rules in Salesforce CRM, and Marketing Cloud only syncs records that meet that criteria. This aligns with best practices for data cleanliness, privacy compliance, and minimizing unnecessary data storage.

Incorrect Option Explanations

A. Select all records created since a certain date
Filtering by creation date does not ensure the contacts are marketable. It would sync all recently created records, including those without permission or valid contact information.

B. Select all records that have an email address
Having an email address does not mean the contact is marketable or compliant with opt-in regulations. This filter could still sync unsubscribed, bounced, or otherwise non-permissioned contacts.

Reference
Salesforce Documentation: Synchronized Data Sources – Filter Settings

Trailhead: Connect Marketing Cloud and Salesforce CRM