Pass the Salesforce AI Specialist Agentforce-Specialist Questions and answers with CertsForce

The correct answer is B because Salesforce Knowledge is the correct source when the business requirement depends on governed support documentation, publishing state, and current article versions. A knowledge-based Agentforce Data Library uses Knowledge as the managed content source, allowing the agent to ground responses in approved Knowledge content instead of static uploaded files. Option A is wrong because a file-based library does not provide the same native Knowledge publishing and version governance; uploaded documents can become stale unless actively maintained. Option C is wrong because the two library types are not equivalent for content lifecycle management. Salesforce guidance for Knowledge-based libraries and service grounding emphasizes using published Knowledge content and data category or library configuration to control what the agent can search and use.

As outlined in the AgentForce External Services and Prompt Flow Integration Guide, when data is retrieved from a registered external service via REST API, the response payload is stored as External Service Records. These records can then be referenced dynamically within prompt templates through External Service Record merge fields.

This approach allows the large language model (LLM) to use the fetched data as contextual grounding during prompt execution, ensuring that generated responses are accurate and consistent with the latest API results.

Option B is incorrect because AgentForce does not use XML merge fields for API responses; JSON data is automatically mapped to object structures. Option C is also incorrect — the “Add Prompt Instructions” element modifies prompt context or tone but does not pass external data for merge use.

Therefore, the correct method is Option A – Use External Service Record merge fields, ensuring the external service data is directly available for prompt templates.

Universal Containers (UC) is using Apex classes within an Agent Action for their Agentforce Agent. Deploying Apex in Salesforce has specific requirements, especially when tied to Agentforce functionality. Let’s evaluate the options.

Option A: The Apex classes must have at least 75% code coverage from unit tests, and all dependencies must be in the deployment package.Salesforce enforces a strict requirement that all Apex classes must achieve at least 75% code coverage from unit tests for deployment to production, regardless of their use case (e.g., Agentforce, triggers, or web services). Additionally, when Apex is invoked by an Agent Action (e.g., via a Flow or direct invocation), all dependencies (e.g., referenced classes, objects) must be included in the deployment package to ensure functionality. This is a standard deployment consideration in Salesforce and applies to Agentforce, making this the correct answer.

Option B: Apex classes invoked by an Agent Action may be deployed with less than 75% test coverage as long as the agent is not activated in production.Salesforce’s 75% code coverage requirement is mandatory for production deployment, regardless of whether the agent is activated. There’s no exemption based on activation status—coverage is enforced at the deployment stage. This option is incorrect and contradicts Salesforce’s Apex deployment rules.

Option C: The Apex classes may bypass the 75% code coverage requirement as long as they are only used by the agent.No such bypass exists in Salesforce. The 75% code coverage rule applies universally to all Apex in production, including classes used by Agentforce. Agent-specific usage doesn’t waive this requirement, making this incorrect.

Why Option A is Correct:

The 75% code coverage requirement and inclusion of dependencies are fundamental Salesforce deployment rules, applicable to Apex in Agent Actions. This ensures reliability and functionality in production, as per official documentation.

The correct answer is A. Since historical policy versions must remain searchable, the solution is not deletion; it is deterministic retrieval scoping. A custom retriever with a dynamic filter can use the customer’s Contract record to pass the applicable policy version at runtime. That limits candidate chunks before semantic ranking, reducing the risk that the LLM receives the wrong policy version. Option B helps add context to chunks, but it still leaves the LLM to choose among versions after retrieval, which is weaker for legal accuracy. Option C creates unnecessary operational complexity by splitting every policy version into separate data streams. Data 360 retrievers are designed to search indexes and can be customized with filters and runtime filter values for more precise grounding.

The correct answer is A. The requirement is operational observability: escalation rate, session duration, topic effectiveness, and the ability to prioritize underperforming agent actions. Agentforce Observability is the native Salesforce area for this because it includes Agent Analytics for aggregate performance metrics and session-level data for deeper investigation. Option B is wrong because the Einstein Trust Layer Audit Trail is primarily governance and audit data around AI interactions, not a service operations dashboard for resolution scoring and action optimization. Option C is not a standard Salesforce capability for these Agentforce metrics. For a live customer service agent, the right model is to use Agent Analytics to identify patterns and then use tracing/session data to inspect where failures or low-quality outcomes are occurring.

Comprehensive and Detailed Explanation From Exact Extract of AgentForce Documents:

According to the AgentForce Orchestration and Action Sequencing Guidelines in the official documentation, deterministic execution order is best achieved by using custom state variables and conditional logic rather than relying solely on LLM reasoning or topic instructions.

AgentForce’s orchestration framework allows developers to define variables that represent the successful completion of specific actions (e.g., “sessionsRetrieved,” “eligibilityVerified,” etc.). Subsequent actions can then include conditional filters that only allow execution if prior steps have been completed. This approach ensures that actions execute in a strict, logical sequence — preventing the LLM from reordering steps arbitrarily.

Option A (relying on topic instructions) provides guidance to the LLM but does not enforce execution order programmatically, which means errors can still occur if the reasoning engine interprets steps differently. Option C (priority and sequence indicators) assists in contextual selection but does not create dependency-based control between actions.

Therefore, per AgentForce best practices, the correct approach is Option B – using custom variables with conditional filters. This guarantees deterministic workflow sequencing, prevents premature action execution, and aligns with the “Action Dependency and Conditional Execution Model” described in the AgentForce Implementation Guide.

The AgentForce Data Cloud Retrieval and Ranking Guide highlights that when outdated Knowledge articles appear before newer ones, administrators should configure ranking factors that prioritize content based on recency. The documentation specifies: “Adding a recency ranking factor using the LastModifiedDate or LastPublishedDate fields ensures the retrieval prioritizes the most up-to-date documents, improving response relevance.”

Option A (disabling keyword index) would remove precision in retrieval and does not address recency.

Option B (changing chunking strategy) affects data segmentation, not ranking order.

Therefore, Option C — adding a ranking factor for recency — is the correct way to ensure updated articles are prioritized.

References (AgentForce Documents / Study Guide):

AgentForce Data Cloud Hybrid Search Configuration Guide: “Applying Recency Ranking”

AgentForce Knowledge Management Handbook: “Prioritizing Updated Articles in Search”

AgentForce Study Guide: “Ranking and Weighting Strategies for Knowledge Retrieval”

Universal Containers can achieve the request to explore similar opportunities by using the standard Copilot action. Agent has built-in actions to handle natural language queries, such as “Show me other opportunities like this one.” The standard action will process the query and return results based on predefined matching criteria like opportunity details and past Closed Won deals.

This approach avoids the need to create custom flows or Apex classes, leveraging out-of-the-box functionality.

For further details, refer to Agent for Sales documentation regarding standard actions and natural language processing.

The correct answer is A. Entitlement data must be available before the reasoning engine decides which subagents or actions are eligible. Setting custom variables in before reasoning ensures the membership tier is hydrated early enough to drive deterministic filters, available when rules, and flow inputs. Option B is wrong because after reasoning occurs too late for initial action visibility and routing decisions in the current reasoning cycle. Option C is wrong because the Agent Router is for routing/classification logic, not the best place to establish reusable entitlement state for action filters and downstream flow logic. The key Agentforce design principle is to make access conditions deterministic before the LLM sees tools. That prevents the agent from offering bronze, silver, or gold actions outside the customer’s actual entitlement level.

The AgentForce Retriever Configuration Guide specifies that filters are used to refine and constrain search results within a retriever setup. Filters operate by applying conditions (up to 10) on indexed fields such as document type, category, region, or update date. This targeted filtering ensures that the retrieved data is highly relevant to the current user query or context.

For instance, an AgentForce retriever could be configured to include only documents tagged as “Active” or within a specific product line, reducing noise and improving grounding accuracy for the LLM. This mechanism supports precision retrieval, which directly improves both the accuracy and reliability of generated responses.

Option B is incorrect because filters do not handle encryption or masking of sensitive data — those functions are managed through Data Cloud security and access controls. Option C is incorrect because retrievers do not aggregate or summarize documents; they retrieve data for grounding, leaving summarization to the LLM reasoning layer.

Therefore, the correct answer is Option A – Filters narrow search results using field-based conditions to improve relevancy and retrieval precision.