Free Salesforce Certified Marketing Cloud Next Consultant practice test: 30 questions with answers

The if block with an else branch chooses between two blocks of content based on a condition. The each block repeats content over a list, a partial inserts a reusable fragment, and a plain merge field only outputs a value and cannot choose between messages.

AMPscript uses %%[ ]%% script blocks with IF, THEN and ENDIF to show content conditionally based on a variable. An each loop is Handlebars syntax for repeating content, a duplicate send is unnecessary, and a landing page consent banner cannot personalize email content.

Content variations let the same campaign present different content to separate groups, so results can be compared. Running two duplicate flows against the full audience would email everyone twice, a business unit setting applies one value to all sends, and two landing pages cannot share one address.

An event-based trigger starts the flow as soon as the form submission event arrives, which matches the near real-time requirement. A daily schedule, a weekly refreshed segment and a long wait step each delay entry until a later batch or interval.

A personalized data source feeds current values into the template at send time, so each recipient sees their own recent products. Manual weekly edits go stale, PDF attachments are not personalized email content, and contact point values store addresses for reaching a person rather than product data.

Identity resolution applies match and reconciliation rules to records from different sources to create unified individual profiles. The other capabilities measure delivery, store permissions and produce predictions, and none of them combines records into one person's profile.

A data stream ingests records from a source system into Data 360 and maps the fields to data model objects so they can be used for segmentation. Saved audiences, landing page components and dashboard widgets are other platform features, and none of them ingests source data.

Segments can only use data that is available in Data 360, so the field must be ingested and mapped to a data model object first. Manual uploads and template formulas bypass the unified data, and consent objects store permissions rather than customer attributes.

Matching on a field that several people can share, such as an email address used by a family, can merge distinct people, so the match rules should be reviewed first. Activation targets, brand colors and banner placement do not decide how records are merged into profiles.

A segment filters only the data it is built on, so unification quality directly affects it, and published segments reach contacts through activation. Exporting segments to a spreadsheet is not required for flows, and segments refresh their membership rather than being rebuilt by hand before each send.

Business units separate records, users and settings for each brand inside one environment, so each team sees only its own data. Folder names organize content but do not restrict access, administrator profiles grant rights across all brands, and a shared sending domain does not isolate anything.

Domain authentication uses DNS records, such as DKIM and SPF entries, that let receiving servers verify the sending domain. A user-level sender address does not authenticate the domain, a website setting does not affect mail verification, and a consent banner is a web page element with no bearing on sender authentication.

Least privilege means granting only the access a role needs, which a tailored permission set does. The administrator profile, a shared login and View All Data each give far more access than an email builder needs, and a shared login also removes individual accountability.

Documented approvers and shared naming and ownership standards make shared assets easier to govern across business units. Identical permissions everywhere ignore business unit boundaries, and turning off change history or review removes the controls governance depends on.

A sandbox or test environment lets the team exercise the flow without reaching real customers, and seed accounts the team controls confirm what each message looks like. Pausing a production flow still exposes it to live data, sending to real customers is not a test, and a second business unit on the same live list does not remove the risk.

Privacy rules such as GDPR require an unambiguous affirmative action for marketing consent, and a pre-ticked box fails that test. A privacy link does not turn an implied choice into valid consent, consent rules cover email as well as SMS, and showing the checkbox again later does not fix an invalid opt-in.

A person may agree to marketing email but not to SMS, or to one brand but not another, so a single flag can overstate consent. The other options describe a naming rule that does not exist, an engagement score and template formatting, none of which explains why consent is recorded by purpose and channel.

Consent is handled per channel, so an email opt-out does not change the subscriber's SMS consent. SMS is not exempt from opt-out rules, and content variations do not bypass suppression, so those options describe incorrect rules.

Non-essential cookies should not be set until the visitor has given consent, and the choice should be recorded. Setting cookies before the banner, showing it only after a form submit, and replacing it with a footer link all let tracking run without a real opt-in decision.

Double opt-in adds a second, explicit confirmation step before consent is recorded as valid, which gives stronger evidence of the person's intent. Recording consent before any confirmation, importing addresses without consent, and opting people in by default all fail that standard.

A human approval step lets the agent speed up drafting while keeping the policy that a person reviews every message. Publishing before review breaks the policy, banning AI drafts gives up the benefit without a stated reason, and self-approval removes the human check entirely.

Features must be available at prediction time, so recent behavior and past purchases are valid inputs. The outcome itself and data recorded after the window cause target leakage, and a unique record ID carries no general pattern that helps the model predict new contacts.

Conversational messaging supports two-way exchanges, so a customer's reply can continue in the same conversation. One-way SMS campaigns, clickable email links and push notifications all send messages without a continuing exchange.

Natural-language requests are useful for drafting segment logic, but the marketer should check the criteria and counts before the audience is used. Automatic activation skips that review, manual export bypasses platform controls, and consent objects do not authorize segment changes.

Providing the written guidelines as grounding material and keeping a human review step gives the best control over tone and claims. Relying on past sends, assuming automatic compliance or restricting copy to one word does not guarantee the rules are followed.

Pre-built dashboards provide standard views of marketing performance without the effort of custom reporting. Manual exports and screenshots are slow and inconsistent, and consent objects store permissions rather than performance metrics.

Comparing comparable periods and audiences shows whether the timing change caused the difference. Deleting the flow erases the evidence, enlarging the audience does not change the rate, and a landing page consent banner does not affect how emails are opened.

Filters on business unit and date range narrow a pre-built dashboard without changing the underlying data. Editing copies by hand is slow and error-prone, deleting other units' data destroys records they need, and consent objects control messaging permissions rather than report scope.

High clicks with few purchases usually point to a disconnect after the click, such as an offer that does not match the email or a page that is hard to use. Database size, the sender domain and banner color do not explain why clicks fail to convert.

A dimension is an attribute used to group or filter results, such as campaign name, while clicks, purchases and delivered counts are measures. Each of the other options is a numeric measure calculated from the data.