Salesforce Updated Agentforce-Specialist Exam Questions and Answers by sami

To access externally-hosted models, such as a large language model (LLM) hosted on AWS, the Model Builder in Salesforce is the appropriate tool. Model Builder allows teams to integrate and deploy external AI models into the Salesforce platform, making it possible to leverage models hosted outside of Salesforce infrastructure while still benefiting from the platform ' s native AI capabilities.

Option B, App Builder, is primarily used to build and configure applications in Salesforce, not to integrate AI models.

Option C, Copilot Builder, focuses on building assistant-like tools rather than integrating external AI models.

Model Builder enables seamless integration with external systems and models, allowing Salesforce users to use external LLMs for generating AI-driven insights and automation.

Salesforce Agentforce Specialist References:

For more details, check the Model Builder guide here: https://help.salesforce.com/s/articleView?id=sf.model_builder_external_models.htm

The correct answer is A because the requirement is immediate, deterministic sequencing after account creation. Procedural instructions in Agent Script are designed for multi-step workflows where the agent must run actions in a required order without waiting for another user turn. The specialist should structure the workflow so that after account creation succeeds, the procedural logic runs the verification email step before advancing to profile setup. Option B is weaker because making an action available does not force immediate execution. Option C is phrased incorrectly because run belongs in Agent Script procedural instructions, not inside the create account action itself. Salesforce Agent Script recipes describe action chaining with run, step tracking, procedural instructions, and automatic follow-up action execution in multi-step workflows.

For Einstein Sales Emails to generate personalized follow-up emails, it is crucial to ground the email content with the most up-to-date and accurate information. Grounding refers to connecting the AI model with real-time data. The most appropriate technique in this case is Ground with Record Merge Fields. This method ensures that the content in the emails pulls dynamic and accurate data directly from Salesforce records, such as lead or contact information, ensuring the follow-up is relevant and customized based on the specific record.

Record Merge Fields ensure the generated emails are highly personalized using data like lead name, company, or other Salesforce fields directly from the records.

Apex Merge Fields are typically more suited for advanced, custom logic-driven scenarios but are not the most straightforward for this use case.

Automatic grounding using Draft with Einstein is a different feature where Einstein automatically drafts the email, but it does not specifically ground the content with record-specific data like Record Merge Fields.

Salesforce Einstein Sales Emails Documentation: https://help.salesforce.com/s/articleView?id=release-notes.rn_einstein_sales_emails.htm

To address security compliance concerns and provide visibility into the prompt text sent to the LLM, how it is masked, and the masked response, the Agentforce Specialist should recommend enabling the audit trail in the Einstein Trust Layer. This feature captures and logs the prompts sent to the large language model (LLM) along with the masking of sensitive information and the AI ' s response. This audit trail ensures full transparency and compliance with security requirements.

Option A (Einstein Shield Event logs) is focused on system events rather than specific AI prompt data.

Option B (debug logs) would not provide the necessary insight into AI prompt masking or responses.

For further details, refer to Salesforce ' s Einstein Trust Layer documentation about auditing and security measures.