CRT-550 Salesforce Certified Marketing Cloud Consultant Exam (SP25) Free Practice Exam Questions (2025 Updated)

GTL (Guide Template Language) is used in Marketing Cloud's Content Builder to process JSON responses directly inside email content. Since Sunny Sky API provides weather information likely in a JSON format, GTL is the appropriate way to parse the response and personalize the email in real time without needing external services or complex scripting.

—

Exact Extract from Salesforce Documentation:

Source: Salesforce Help – Guide Template Language (GTL)

→ "Guide Template Language (GTL) enables parsing of JSON objects for dynamic content inside emails, CloudPages, and SMS messages. GTL is designed specifically to personalize content using external data sources directly within a send."

Source: Marketing Cloud Developer Guide – GTL Overview

→ "Use GTL to retrieve, parse, and render JSON content into Marketing Cloud messages."

—

Comprehensive Explanation:

Long codes can be used for outbound messaging across multiple countries. However, inbound messaging capabilities are often restricted to specific countries due to local regulations and carrier requirements. If NTO needs to support inbound messages (i.e., two-way communication) in each country, they may need to provision separate long codes for each country to comply with local regulations and ensure message deliverability.​

Since the marketer has little coding experience, creating Data Relationships (via Contact Builder) and enabling segmentation using Data Filters is the best approach. Data Filters are a marketer-friendly, drag-and-drop tool that allow segmentation without the need for SQL or scripting.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – Data Filters

→ "Data Filters allow non-technical users to segment data extensions using an intuitive interface without needing SQL or scripting knowledge."

Source: Salesforce Help – Data Relationships in Contact Builder

→ "Data Relationships connect Data Extensions and enable users to create filters based on joined data without writing code."

—

Comprehensive and Detailed Explanation:

The correct answer is D — Contact Builder Attribute Groups.

Contact Builder Attribute Groups allow you to combine multiple Data Extensions (e.g., purchases and loyalty membership) into one relational view.

Then you can easily query and filter based on conditions like "purchase date in last 6 months AND not a loyalty member."

❌ Why others are wrong:

A: Behavioral Triggers are related to real-time actions like website behavior, not cross-data queries.

B: Advertising Studio is for paid advertising, not internal audience segmentation.

C: Customer Data Platform (CDP) would be overkill unless NTO had an enterprise-wide CDP already (which isn’t mentioned).

Exact Extract from Salesforce Official Documentation:

Salesforce Help — Contact Builder Attribute Groups Overview:

"Use Attribute Groups to define and model relationships between data extensions and organize contact attributes to create targeted audiences."

(Source: https://help.salesforce.com/s/articleView?id=sf.mc_cb_attribute_groups.htm )

—

Comprehensive and Detailed Explanation:

The correct answer is D — Build rules before uploading the respective content.

Best practice is to define dynamic content rules first (e.g., “Points < 1000: Content A; Points 1000–5000: Content B”) before building and uploading the content blocks.

This makes setting up Dynamic Content Blocks in Content Builder easier and more structured.

❌ Why others are wrong:

A: Custom Lists are older Email Studio concepts, not relevant to dynamic content best practices in Content Builder.

B: Standardizing field names is good practice, but not directly tied to dynamic content rule building.

C: Synchronized DEs are for Salesforce CRM data, which is not mentioned here.

Exact Extract from Salesforce Official Documentation:

Salesforce Help — Dynamic Content Setup:

"Create rules for dynamic content before associating the respective content assets to ensure correct audience targeting within the email template."

(Source: https://help.salesforce.com/s/articleView?id=sf.mc_es_dynamic_content.htm )

—

Tokenized Sending allows PII (such as email addresses) to stay external until send time; however, once pulled in via personalization strings, PII can still be displayed within emails.

Since Tokenized Sending relies on live API calls to an external database during sends, Salesforce Marketing Cloud's normal service-level guarantees (e.g., send speed and reliability) no longer apply because they now depend on third-party system response times.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – Tokenized Sending Overview

→ "Tokenized Sending retrieves sensitive customer data at send time, reducing Marketing Cloud's data storage liability. However, if personalization strings reference retrieved fields, PII can still be displayed in the email."

Source: Salesforce Help – Tokenized Sending Limitations

→ "Marketing Cloud does not guarantee service levels for sends that rely on external Tokenized Sending lookups."

—

Comprehensive and Detailed Explanation:

The correct answer is D — A Sender Authentication Package (SAP) should be used for Cloud Kicks.

SAP provides a dedicated IP, Private Domain, DKIM, and SPF alignment, critical for brand deliverability and reputation.

Since Cloud Kicks will operate with its own brand identity, even under the same parent org, setting a distinct SAP ensures inbox placement and avoids shared reputation issues.

❌ Why others are wrong:

A: NTO already has an SAP; Cloud Kicks needs its own setup.

B and C: Private Domains without full SAP (dedicated IP, DKIM, SPF) are not sufficient alone for full brand reputation management.

Exact Extract from Salesforce Official Documentation:

Salesforce Help — Sender Authentication Package Overview:

"Use the Sender Authentication Package (SAP) to configure custom sending domains, dedicated IPs, and authenticated email, ensuring maximum deliverability and brand identity."

(Source: https://help.salesforce.com/s/articleView?id=sf.mc_es_sender_authentication_package.htm )

—

Comprehensive and Detailed Explanation:

The correct answer is B — Create a new data extension and link it to the other data extension.

Best practice is to separate different data streams into different Data Extensions and use relationships (via Contact Builder Attribute Groups) to link them logically.

This allows independent updates from different sources without risking overwriting primary contact data.

❌ Why others are wrong:

A: Adding more fields to the main DE would make the model heavy and harder to manage, especially with separate feeds.

C: Salesforce Data Extensions are specific to CRM integration and not mentioned here.

D: New populations are used when contacts are fully separate audiences, which is not the case here (it's the same contact base).

Exact Extract from Salesforce Official Documentation:

Salesforce Help — Contact Builder Data Relationships:

"Use separate data extensions for distinct types of information and create relationships between them to build a scalable contact data model."

(Source: https://help.salesforce.com/s/articleView?id=sf.mc_cb_data_model.htm )

—

To filter records entering a journey based on an updated status field (“shipped”), the marketer should use:

An Entry Source Filter to limit which contacts actually enter the journey at the point of entry (e.g., only those whose order status is 'shipped' today).

An SQL Query to preprocess or segment records within a Data Extension before injecting them into the journey.

Filter Activity is used inside Automation Studio (not at the journey entry point), and Decision Splits occur after entry — not before.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – Entry Source Filters

→ "An entry source filter defines criteria that records must meet before entering a journey."

Source: Salesforce Help – SQL Query Activities

→ "Use SQL Query Activities to select, transform, and filter data from one or more data extensions."

—

Each File Drop Automation must monitor a unique directory, and that directory cannot be shared across multiple File Drop Automations (B).

The file trigger directory must be inside the import folder structure for Enhanced FTP (C).

Using an external FTP site is not supported for File Drop Automations — it must be Salesforce's Enhanced FTP. The limitation on the number of triggers is not five; it's based on system and licensing limits.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – File Drop Automation Requirements

→ "Each File Drop Automation must have its own unique directory. The directory must reside within the Import directory."

Source: Salesforce Help – Enhanced FTP File Drop Automations

→ "File Drop Automations require files to be dropped into a directory under the Import folder on Marketing Cloud’s Enhanced FTP."

_Send Data Views are built-in system tables in Marketing Cloud that capture detailed tracking data across multiple channels including Email, SMS, and Push. They can be queried via SQL Query Activities to extract insights about sends, clicks, opens, bounces, and more.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – Data Views in Marketing Cloud

→ "_Send Data Views provide detailed tracking data for sends across all messaging channels, including Email, Mobile, and Push. Query these views for advanced reporting."

—

Distributed Marketing is specifically designed to allow centralized marketing teams to control messaging and branding while empowering field teams (subsidiaries, partners) to personalize and send communications. It ensures consistency, compliance, and unified branding across campaigns.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – Distributed Marketing Overview

→ "Distributed Marketing helps central teams create standardized messaging while allowing local teams to personalize and send communications — ensuring branding consistency."

Source: Salesforce Product Documentation – Distributed Marketing for Salesforce

→ "Unify your brand experience across every customer communication while enabling personalization and local customization."

The _Click data view in Marketing Cloud stores information about link clicks for up to six months. By writing and executing a SQL query against this data view in Automation Studio, the customer can accurately identify subscribers who have clicked on any links within the specified timeframe.​

Comprehensive and Detailed Explanation:

The correct answer is A — Implement two separate Marketing Cloud instances.

To fully segregate test data (sandbox) from production data with zero risk of mixing, separate instances are necessary.

Business Units (BU) would still share the same All Subscribers list — so using BUs alone is not sufficient for strict separation.

❌ Why others are wrong:

B and D: Filtering doesn’t prevent accidental cross-contamination.

C: Business Units are logical partitions, but not physical — they still share the same SubscriberKey space at the instance level.

Exact Extract from Salesforce Official Documentation:

Salesforce Help — Sandbox vs Production in Marketing Cloud:

"For true separation of test and production data in Marketing Cloud, separate instances are required. Business Units do not guarantee complete data segregation."

(Source: https://help.salesforce.com/s/articleView?id=sf.mc_es_sandbox_testing.htm )

—

Marketing Cloud Connect requires a Subscriber Key that matches a Lead ID, Contact ID, or User ID for native tracking and send logging to work properly. If a custom object is used without these IDs, Marketing Cloud cannot push tracking data (such as email opens or clicks) back into Sales Cloud against those recipients.

—

Exact Extract from Salesforce Documentation:

Source: Salesforce Help – Marketing Cloud Connect Tracking

→ "Tracking data is automatically pushed back to the appropriate Lead, Contact, or User object when using Salesforce Send Logging. If the subscriber key does not match these standard IDs, tracking data cannot be associated with recipients in Sales Cloud."

Source: Salesforce Marketing Cloud Connect Guide – Contact Model Requirements

→ "A standard object ID (Lead ID, Contact ID, or User ID) must be used to ensure synchronization and tracking between Salesforce and Marketing Cloud."

—

BuildRowSetFromJSON() is an AMPscript function specifically designed to parse JSON payloads into usable row sets inside emails. This allows marketers to iterate through JSON objects easily and display order details dynamically in triggered transactional emails.

—

Exact Extracts from Salesforce Documentation:

Source: Salesforce Help – AMPscript BuildRowSetFromJSON() Function

→ "BuildRowSetFromJSON parses a JSON string and creates a rowset suitable for use in AMPscript loops."

Source: Salesforce Help – Formatting JSON in Emails

→ "Use BuildRowSetFromJSON to extract and format dynamic data from JSON payloads in triggered transactional sends."

—

✅ Comprehensive and Detailed Explanation:

B (Publication List) allows subscribers to opt down or up in terms of subscription types. Customers indicating product interests and preferred messaging frequency would fit into Publication List management.

C (Auto-Suppression List) can exclude certain groups or preferences at the message send level automatically, especially if customers opt-down or unsubscribe partially.

❌ Why Others Are Incorrect:

A: Suppression Lists are manually managed and aren't dynamically tied to preferences.

D: Domain Exclusion blocks entire domains (e.g., gmail.com) — not individual preference management.

Exact Extract:

Salesforce Help: Publication Lists Overview

"Publication lists manage opt-ins and opt-outs at a more granular level, allowing customers to control which messages they want to receive."

Salesforce Help: Auto-Suppression Lists

"Auto-suppression lists automatically prevent messages from being sent to specific subscribers based on business rules and preferences."

════════════════════════════

════════════════════════════════════════════

Comprehensive and Detailed Explanation:

The correct answer is D — A GUID or another generated ID for Contact Key.

Best practice is to use a channel-agnostic, stable, unique identifier for Contact Key.

Email addresses and phone numbers can change. A GUID (Globally Unique Identifier) or system-generated ID ensures persistent identification across email, SMS, push, and other channels.

❌ Why others are wrong:

A: Physical Address isn't unique and can change.

B: Phone number can change and is not unique to a single identity.

C: Email addresses are prone to change over time (job switch, preference change).

Exact Extract from Salesforce Official Documentation:

Salesforce Help — Subscriber Key and Contact Key Best Practices:

"Use a non-channel specific, unique, and persistent identifier, such as a generated GUID or system ID, as the Subscriber Key (Contact Key) across all messaging channels."

(Source: https://help.salesforce.com/s/articleView?id=sf.mc_es_contact_key_best_practices.htm )

—

Comprehensive and Detailed Explanation:

The correct answer is C — Use Synchronized Data Extensions on the Case Object with a Boolean filter on the Contact Me field.

With Marketing Cloud Connect, the Case object can be synchronized into Marketing Cloud.

You can apply filters based on fields like "Contact Me = True" directly within Journey Builder or Automation Studio without manually importing reports.

❌ Why others are wrong:

A: Journey Builder doesn't handle direct data imports from Service Cloud.

B: Manual imports and Filter Activities are unnecessary when synchronized data is available.

D: Import Wizard processes are manual and not scalable for ongoing automated campaigns.

Exact Extract from Salesforce Official Documentation:

Salesforce Help — Synchronized Data Extensions:

"Synchronized Data Extensions allow you to bring Salesforce object data (such as Cases) into Marketing Cloud for use in segmentation, filtering, and journeys without manual imports."

(Source: https://help.salesforce.com/s/articleView?id=sf.mc_co_synchronized_data_extensions.htm )