Salesforce Certified Marketing Cloud Account Engagement Specialist (MC-201) Practice Tests

Explanation

All prospects in Account Engagement begin with a default grade of D, which is the lowest grade on the A-through-D scale. Grades increase only when a prospect's demographic or firmographic attributes match configured profile criteria. Because Thomas's job title, industry, and company size do not match any criteria, no upward grade adjustments are applied and he retains the starting grade of D. Unlike scoring, which is activity-based and reactive to behavioral engagement, grading is based solely on explicit profile attributes and does not decay over time.

Explanation

Completion actions can be configured directly on Account Engagement Forms and Files, as well as on form handlers, custom redirects, emails, and page actions. When a prospect submits a form, any configured completion actions fire immediately for that individual prospect. When a prospect clicks a tracked link to download a file hosted in Account Engagement, completion actions configured on that file execute right away. Dynamic lists are a segmentation mechanism that automatically controls list membership based on criteria — they are not prospect-facing assets and do not support completion actions. Automation rules are themselves an automation mechanism used to apply bulk actions to matching prospects; they are not marketing assets that prospects interact with directly. Segmentation rules are one-time database filtering tools used for building lists and adding prospects to campaigns, and they do not support completion action configuration.

Explanation

SPF (Sender Policy Framework) is a DNS TXT record that specifies which mail servers are authorized to send email on behalf of a domain. When Account Engagement's sending servers are listed in the domain's SPF record, receiving servers can verify that an incoming message originated from an authorized source, reducing the likelihood of messages being flagged as spam or rejected. DKIM adds a cryptographic digital signature to email headers so recipients can verify message integrity, but does not specify authorized sending servers. DMARC builds on both SPF and DKIM to instruct receiving servers how to handle messages that fail authentication checks and enables aggregate reporting, but requires SPF and DKIM to be in place first. MX records direct incoming mail to the domain's mail servers and are unrelated to outbound authorization.

Explanation

The Marketing role is purpose-built for practitioners who create and manage content and campaigns, including A/B and multivariate tests on forms, landing pages, and emails. This role excludes access to technical setup tasks such as connector configuration, tracker domain management, and system-level administration, keeping those capabilities exclusively in the Administrator role. The Administrator role is an unrestricted super-user role with full system access including connector monitoring and domain management, which exceeds what this specialist requires. The Sales Manager role focuses on pipeline visibility and prospect reporting, not content creation or testing. The Sales role is the most restrictive role, limited to viewing and editing only the prospects assigned to that user, with no campaign management capabilities.

Explanation

Engagement Studio supports sub-day hourly wait step durations with a minimum of 2 hours and a maximum of 8 hours. Available increments include all whole-hour values from 2 through 8 hours. A 1-hour wait increment is not among the available selections — sub-day waits begin at 2 hours. A 30-minute wait is not supported. These sub-day wait steps enable programs that respond to prospect behavior within the same business day rather than requiring the legacy 1-day minimum gap between steps. A 2-hour wait placed between a registration trigger and a follow-up send step is fully supported under current platform capabilities.