Nail the AI-201: Agentforce Prep That’s Built for Real-World Implementation

When a customer chat is initiated, Einstein Service Replies provides generative AI replies or draft emails based on recommended Knowledge articles. This feature uses the information from the Salesforce Knowledge base to generate responses that are relevant to the customer ' s query, improving the efficiency and accuracy of customer support interactions.

Option B is correct because Einstein Service Replies is responsible for generating AI-driven responses based on knowledge articles.

Option A (Einstein Reply Recommendations) is focused on recommending replies but does not generate them.

Option C (Einstein Grounding) refers to grounding responses in data but is not directly related to drafting replies.

Einstein Service Replies Overview: https://help.salesforce.com/s/articleView?id=sf.einstein_service_replies.htm

The correct answer is A because vectorization converts text chunks into numerical embeddings that capture semantic meaning. In Agentforce and Data 360 retrieval scenarios, large documents are first broken into smaller chunks or passages, and those chunks are then converted into vectors. The retrieval engine can compare a user’s question or prompt with those vectors to find content that is meaningfully similar, not merely keyword-matched. Option B is wrong because vectorization is not encryption; security and storage controls are separate platform concerns. Option C is wrong because vectorization is not a compression mechanism and is not used primarily to reduce file size or storage cost. Salesforce Data 360 documentation describes chunking as creating manageable semantic units and vectorization as converting those chunks into numeric representations of text.

For improving sales operations efficiency, Einstein Studio is ideal for creating AI-powered models that can predict outcomes based on data. One of the most valuable use cases is predicting customer lifetime value, which helps sales teams focus on high-value accounts and make more informed decisions. Customer lifetime value (CLV) predictions can optimize strategies around customer retention, cross-selling, and long-term engagement.

Option B is the correct choice as predicting customer lifetime value is a well-established use case for AI in sales.

Option A (customer sentiment) is typically handled through NLP models, while Option C (product popularity) is more of a marketing analysis use case.

Salesforce Einstein Studio Use Case Overview: https://help.salesforce.com/s/articleView?id=sf.einstein_studio_overview

UC has grounded a prompt template with a related list, but the responses are incorrect during UAT. Grounding with related lists in Agentforce allows the AI to access data from child records linked to a parent object. Let’s analyze the options.

Option A: The related list is Read Only.Read-only status (e.g., via field-level security or sharing rules) might limit user edits, but it doesn’t inherently prevent the AI from accessing related list data for grounding, as long as the running user (or system context) has read access. This is unlikely to cause incorrect responses and is not a primary consideration, making it incorrect.

Option B: The related list prompt template option is not enabled.There’s no specific " related list prompt template option " toggle in Prompt Builder. When grounding with a Record Snapshot or Flex template, related lists are included if properly configured (e.g., via object relationships). This option seems to be a misphrasing and doesn’t align with documented settings, making it incorrect.

Option C: The related list is not on the parent object’s page layout.In Agentforce, grounding with related lists relies on the related list being defined and accessible in the parent object’s metadata, often tied to its presence on the page layout. If the related list isn’t on the layout, the AI might not recognize or retrieve its data correctly, leading to incomplete or incorrect responses. Salesforce documentation notes that related list data availability can depend on layout configuration, making this a plausible and common issue during UAT, and thus the correct answer.

Why Option C is Correct:

The absence of the related list from the parent object’s page layout can disrupt data retrieval for grounding, leading to incorrect AI responses. This is a known configuration consideration in Agentforce setup and testing, as per official guidance.

For Field Generation prompt templates to display the Sparkle icon (indicating AI-generated content), the target field must be explicitly associated with the prompt template on the Lightning page layout. Even if the prompt template is activated, failing to add the field to the page layout and link it to the template will result in the field behaving as a standard field. Salesforce documentation emphasizes that page layout configuration is mandatory to enable AI-driven field interactions.

Reactivating the layout (A) is unnecessary unless the layout itself was modified after activation.

Case objects are supported for Field Generation (B is incorrect).

According to the AgentForce Retrieval Optimization Guide, when handling ambiguous search terms such as “package,” which may refer to multiple concepts, the recommended approach is to use hybrid search. The documentation defines hybrid search as: “A combined retrieval method that leverages keyword-based precision and semantic embeddings to capture contextual intent. This approach ensures high recall while maintaining exact-term precision.”

This method allows AgentForce to resolve ambiguity by using semantic context to interpret meaning while maintaining keyword-based precision for deterministic matching. The guide further notes: “Hybrid retrieval offers the optimal balance between contextual understanding and exact-term accuracy, especially in multi-domain or ambiguous queries.”

In contrast, semantic search only may misinterpret terms without adequate context, and keyword search only lacks the contextual reasoning to differentiate between meanings. Thus, Option A aligns with Salesforce’s documented best practice for retrieval precision and contextual relevance.

References (AgentForce Documents / Study Guide):

AgentForce Retrieval and Indexing Guide: “Hybrid Search for Contextual and Exact Matching”

AgentForce Study Guide: “Improving Query Precision with Hybrid Search”

AgentForce Knowledge Base Implementation Notes

The AI audit trail in Salesforce provides a detailed log of AI activities, including the data used, its handling, and masking procedures applied in the Einstein Trust Layer. It allows the Agentforce Specialist to inspect and verify that sensitive data, such as addresses, is appropriately masked before being used in prompts or outputs.

Enable data encryption on the address field: While encryption ensures data security at rest or in transit, it does not verify masking in AI operations.

Review the platform event logs: Platform event logs capture system events but do not specifically focus on the handling or masking of sensitive data in AI processes.

Inspect the AI audit trail: This is the most relevant option, as it provides visibility into how data is processed and masked in AI activities.

The correct answer is B. The agent is grounded on a Knowledge data library, and the goal is broad FAQ coverage without manually writing every test. Agentforce Testing Center can generate test scenarios directly from the knowledge sources available to the agent, which makes it the best fit for building an initial regression suite quickly. Option A is valid only when the team already has prepared test cases, but the scenario says manual authoring would take too long. Option C can test routing and tool selection based on subagents and actions, but it does not directly exploit the 200 FAQ articles as the source for test coverage. For knowledge-grounded agents, generating test cases from available Knowledge content is the efficient and relevant approach.

Per the AgentForce Testing Center Operations Guide, the batch testing feature allows organizations to upload structured CSV test templates containing real-world user utterances, expected classifications, and desired outcomes. Once uploaded, these test cases are executed in bulk within the Testing Center to validate agent accuracy, reasoning consistency, and grounding before activation.

This structured approach supports repeatable, scalable testing and ensures objective evaluation across multiple topics and scenarios.

Option B (manual testing) is suitable for early prototyping but not scalable or auditable. Option C (relying on pilot feedback) occurs post-deployment and risks exposing users to unverified behavior.

Therefore, the recommended approach is Option A – Upload a structured CSV test template and run batch test cases in Testing Center.

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