Pass the Salesforce Marketers Marketing-Cloud-Administrator Questions and answers with ExamsMirror

Creating separate business units for each brand is necessary when:

Brand-specific Domains: Separate business units allow for the configuration of brand-specific private domains, which are crucial for maintaining brand identity and trust in email campaigns by customizing link and image paths.

Use Case: If different brands under NTO need to leverage their unique domains for sending emails and hosting content, setting up distinct business units allows each brand to manage its sender profiles, content, and subscriber interactions independently.

To append an Urchin Tracking Module (UTM) variable string to links in emails, the Marketing Cloud admin should use the Web Analytics Connector (WAC). This functionality automatically appends tracking parameters, such as UTM parameters, to all URLs in outgoing emails. This allows for detailed tracking of email effectiveness within analytics platforms like Google Analytics. The Web Analytics Connector can be configured within Email Studio to include specific UTM parameters as required by marketing strategies.

The user in question holds roles that do not inherently include permissions to send emails. The roles assigned are:

Content Creator: Typically has permissions to create content but not necessarily to send emails.

Data Manager: Manages data but does not have email sending permissions.

Marketing Cloud Viewer: Can view campaigns and data but cannot execute or modify them.

To resolve this issue so that the user can send emails, the admin must: A. Edit permissions and Grant permissions to Send - This action involves customizing the user’s permissions to include the ability to send emails. This can be done either by adjusting the permissions in one of the existing roles (if customization is possible and appropriate) or by creating a custom role or permission set that includes email sending capabilities.

For the entertainment company's setup using Contact Builder and Journey Builder, the two data sources essential to incorporate are:

A. Customer Data: This is crucial because it includes basic customer identifiers such as email addresses, which are necessary for sending emails and personalizing communications.

B. Event Registration: This data is critical as it contains the event-specific details needed for the decision splits in the journey, such as event ID, event type, and event name, which will determine the content of emails, including dynamic venue details through AMPscript.

These data sources ensure that the journeys can be personalized and targeted based on the customer's registered events, enhancing the relevance and effectiveness of the communications.

To limit the distribution of Marketing Cloud tracking data via email to only those within the ntoretail.com domain:

Add a Domain to the Export Email Whitelist: Configure the settings to include 'ntoretail.com' in the export email whitelist. This ensures that only email addresses from this domain can receive exported data.

Enforce Export Email Whitelist: Activate this setting to strictly enforce the whitelist during data exports, preventing any non-whitelisted domains from receiving tracking data.

To create and schedule a weekly report with high-level metrics, the Marketing Cloud admin should use Analytics Builder. Analytics Builder allows users to create, view, and share reports and dashboards. The Account Send Summary report shows how many emails were sent in a given time period

To resolve the issue of "Insufficient User Permissions" while setting up Marketing Cloud Connect, the action that should correct this issue is to apply the appropriate user mappings in the CRM configuration. This involves ensuring that the Salesforce user is correctly linked with the Marketing Cloud user credentials and roles. The error indicates a mismatch or an incomplete configuration in linking Salesforce and Marketing Cloud users, which user mappings can correctly align.

The Content Builder Settings under Setup allow the admin to create a default Header and Footer for emails. These settings apply to emails created in Content Builder only. The other settings do not have an option to create a default Header and Footer for emails.

The best way to prevent the prefix [PREVIEW] from deploying in live sends is to wrap the subject line with AMP script that checks if the send is a test send or a live send. For example:

%%[

IF _IsTestSend == true THEN

SET @subject = "[PREVIEW] " + @subject

ENDIF

]%%

Using Proof instead of [PREVIEW] does not solve the problem, as it still shows up in live sends. Adding [PREVIEW] to the subject line validation list does not prevent it from deploying, but rather prevents any email with [PREVIEW] in the subject line from being saved. Requiring several campaign approvals does not guarantee that the prefix will be removed before sending.

Following a Contact Delete request, certain data types remain within the account:

B. Contact data in non-sendable data extensions: This data does not directly link to an individual's subscriber key or contact ID, allowing it to persist in the system for reporting and analytical purposes without targeting specific individuals.

C. General tracking data at the job level: This includes aggregated data on email opens, clicks, and other engagement metrics collected at the campaign level, not tied to individual contact identities, thus remaining in the system post-deletion.