MC-Con-201 Exam Dumps and Practice Questions

The 'Forward to Agent' flow step in an Agentforce-generated conversational email campaign serves to route complex inquiries or conversations that exceed the AI's capabilities to a human agent. This step enables seamless escalation when the conversational AI cannot adequately handle a customer question or when human judgment is needed to resolve an issue, ensuring customers receive appropriate support.

These two personalization elements require different data sources based on their origin and nature. The sales rep's name is stored in Agentforce Sales (Salesforce CRM), so it should be retrieved using the Agentforce Sales CRM data source to pull related Contact/Lead data. The unique, time-sensitive promo code is managed in Marketing Cloud Next and needs to be specified per campaign activation, making Campaign Variables the appropriate choice. Campaign Variables allow the promo code to be defined and injected at campaign launch time, ensuring each activation can use a different, unique code without modifying the underlying customer data.

To send a personalized verification code immediately after a customer initiates a login, where an external web service generates the code at send time, the consultant should recommend using an API-triggered flow with a dynamic/real-time data source (such as a REST API data source). The flow can be triggered via API with the customer's email or identifier, and the Send Email Message step can include a dynamic data source that makes a real-time API call to the external web service to fetch the verification code. This ensures the code is generated fresh at send time and included in the email without pre-storing it in Marketing Cloud Next.

The Marketing Cloud Manager permission set is a global role that grants broad permissions but does not automatically restrict access to a specific Business Unit. To ensure agency users can only access and deploy campaigns in the EMEA Business Unit, a new permission set must be created that includes both the necessary campaign management capabilities and explicit EMEA Business Unit restrictions. This custom permission set should then be assigned to the agency user accounts. This approach maintains security and data governance by limiting agency access to only the region they are contracted to manage.