McAfee Secure

Salesforce Certified Agentforce Specialist Bundle

Exam Code: Certified Agentforce Specialist

Exam Name Certified Agentforce Specialist

Certification Provider: Salesforce

Corresponding Certification: Salesforce Certified Agentforce Specialist

Salesforce Certified Agentforce Specialist Bundle $25.00

100% Salesforce Certified Agentforce Specialist Guaranteed Success With Testking Training Materials

Get Real Certified Agentforce Specialist Exam Questions & Expert Verified Answers as Experienced on the Real Exam!

  • Questions & Answers

    Certified Agentforce Specialist Questions & Answers

    258 Questions & Answers

    The ultimate exam preparation tool, Questions & Answers mirrors the actual Certified Agentforce Specialist exam while allowing you to hone and measure every aspect of your test-taking ability.

  • Certified Agentforce Specialist Video Course

    Certified Agentforce Specialist Training Course

    66 Video Lectures

    Certified Agentforce Specialist Video Course is developed by Salesforce Professionals to help you pass the Certified Agentforce Specialist exam.

    Description

    This course will improve your knowledge and skills required to pass Certified Agentforce Specialist exam.

Certified Agentforce Specialist Practice Tests

Satisfaction Guaranteed

Money Back Guarantee

Testking provides hassle-free money back guarantee with our products. That is because we have 100% trust in the abilities of our professional and experience product team, and our record is a proof of that.

99.6% PASS RATE
Total Cost: $164.98
Bundle Price: $139.98

Purchase Individually

  • Questions & Answers

    Questions & Answers

    258 Questions

    $124.99
  • Certified Agentforce Specialist Video Course

    Training Course

    66 Video Lectures

    $39.99

Salesforce Certified Agentforce Specialist Practice Test 2

Question 10

At Bluehaven University, an internal student services team is improving student advising while preparing a production promotion (SF-T10-01). The administrator observes that a prompt template is deployed but invokes a Flow not present or active in production. Any fix must ensure that student records never cross program authorization boundaries. Which action best addresses the issue while preserving the stated requirement?

  1. Validate and activate the intended prompt template version after deployment; implement it with a named deployment owner.
  2. Include required Flow and template dependencies in a controlled deployment plan; implement it with a controlled rollback path.
  3. Replace hard-coded environment-specific references with approved context bindings; implement it and keep the business rule enforceable.
  4. Use a properly configured sandbox with safe representative data for action tests; implement it with traceable change approval.

Explanation

Correct Answer

B:

The documented failure is that a prompt template is deployed but invokes a Flow not present or active in production. Include required Flow and template dependencies in a controlled deployment plan for Bluehaven University's student advising workflow (SF-T10-01) while respecting that student records never cross program authorization boundaries. Its outcome is not established merely by changing instructions: In a controlled Student_Request__c acceptance test, the production prompt resolves all referenced automation resources successfully; the record is retained under Bluehaven University's rollout (SF-T10-01). The underlying reason is that Prompt templates can depend on metadata and automation beyond template text. In this student advising scenario, this separates supported agent behavior from assumptions about the AI model.

Incorrect Answers

A:

The action “Validate and activate the intended prompt template version after deployment; implement it with a named deployment owner” addresses a separate source case: A revised prompt arrives in production but callers keep receiving the earlier active version. The correction must ensure that work order updates follow supported automation guardrails. Its underlying reason is: Deployment and activation are separate steps in prompt lifecycle. This question instead describes a prompt template is deployed but invokes a Flow not present or active in production. The correction must ensure that student records never cross program authorization boundaries. The original answer “Include required Flow and template dependencies in a controlled deployment plan; implement it with a controlled rollback path” targets that failure because prompt templates can depend on metadata and automation beyond template text.

C:

The action “Replace hard-coded environment-specific references with approved context bindings; implement it and keep the business rule enforceable” addresses a separate source case: A prompt created in a sandbox references a test record identifier not present in production. The correction must ensure that employee identity is verified before accessing private tickets. Its underlying reason is: Reusable templates require portable bindings for environment-specific context. This question instead describes a prompt template is deployed but invokes a Flow not present or active in production. The correction must ensure that student records never cross program authorization boundaries. The original answer “Include required Flow and template dependencies in a controlled deployment plan; implement it with a controlled rollback path” targets that failure because prompt templates can depend on metadata and automation beyond template text.

D:

The action “Use a properly configured sandbox with safe representative data for action tests; implement it with traceable change approval” addresses a separate source case: A team proposes batch-testing an order cancellation agent directly in production. The correction must ensure that supplier prices are never shown outside entitled teams. Its underlying reason is: Agent tests can invoke business actions and therefore require environmental isolation. This question instead describes a prompt template is deployed but invokes a Flow not present or active in production. The correction must ensure that student records never cross program authorization boundaries. The original answer “Include required Flow and template dependencies in a controlled deployment plan; implement it with a controlled rollback path” targets that failure because prompt templates can depend on metadata and automation beyond template text.

Question 11

At Juniper Civic, a public agency service counter is improving permit status during an agent routing evaluation (SF-A25-03). The administrator observes that customers need assistance with cases and troubleshooting through a public support site. Any fix must ensure that citizen information stays limited to the relevant case. Which underlying Agentforce or Salesforce design principle explains the appropriate approach?

  1. Agent type selection should follow user audience and operational purpose; interpret this with boundaries enforced by supported platform controls.
  2. Employee agents target workforce use cases rather than unauthenticated service traffic; interpret this as a necessary control for deterministic outcomes.
  3. Service agents target service interactions and channel-specific customer needs; interpret this while preserving the specified source of truth.
  4. Agent Script separates top-level system, config, variables, start_agent, and subagent responsibilities; interpret this without inferring extra permissions from an LLM response.

Explanation

Correct Answer

C:

The governing distinction is: Service agents target service interactions and channel-specific customer needs. In this permit status scenario, this separates supported agent behavior from assumptions about the AI model. Because customers need assistance with cases and troubleshooting through a public support site, the intended response is to choose a Service agent configured for the customer service channel and supported actions. An observable check is that a customer session can obtain permitted case guidance and escalate appropriately.

Incorrect Answers

A:

The idea “Agent type selection should follow user audience and operational purpose; interpret this with boundaries enforced by supported platform controls” explains another source-defined situation: An internal procurement helper is configured as a public service agent with customer-facing entry points. The correction must ensure that citizen information stays limited to the relevant case. That situation depends on: Agent type selection should follow user audience and operational purpose. The present question instead concerns customers need assistance with cases and troubleshooting through a public support site. The correction must ensure that citizen information stays limited to the relevant case. Its directly relevant mechanism is: Service agents target service interactions and channel-specific customer needs.

B:

The idea “Employee agents target workforce use cases rather than unauthenticated service traffic; interpret this as a necessary control for deterministic outcomes” explains another source-defined situation: Employees need internal HR and IT knowledge while customers must not see confidential responses. The correction must ensure that quoted amounts use authorized account and price-book records. That situation depends on: Employee agents target workforce use cases rather than unauthenticated service traffic. The present question instead concerns customers need assistance with cases and troubleshooting through a public support site. The correction must ensure that citizen information stays limited to the relevant case. Its directly relevant mechanism is: Service agents target service interactions and channel-specific customer needs.

D:

The idea “Agent Script separates top-level system, config, variables, start_agent, and subagent responsibilities; interpret this without inferring extra permissions from an LLM response” explains another source-defined situation: An administrator puts all conversational logic into system messages instead of separating routing and subagent behavior. The correction must ensure that supplier prices are never shown outside entitled teams. That situation depends on: Agent Script separates top-level system, config, variables, start_agent, and subagent responsibilities. The present question instead concerns customers need assistance with cases and troubleshooting through a public support site. The correction must ensure that citizen information stays limited to the relevant case. Its directly relevant mechanism is: Service agents target service interactions and channel-specific customer needs.

Question 12

At Westmoor Sports, a consumer membership desk is improving membership renewals after a knowledge-policy revision (SF-A14-03). The administrator observes that a service agent handles warranty inspection but its broad existing topic attracts unrelated requests. Any fix must ensure that member records cannot be exposed to other members. Which underlying Agentforce or Salesforce design principle explains the appropriate approach?

  1. Standard agent topics can be reused when they already fit the task; interpret this as distinct from unrelated UI configuration.
  2. Topic descriptions and instructions guide appropriate task selection; interpret this as a necessary control for deterministic outcomes.
  3. Natural-language instructions alone are weaker than deterministic protected-action controls; interpret this rather than assuming a generative instruction is an access rule.
  4. API connectivity does not override CRM or agent execution authorization; interpret this as a necessary control for deterministic outcomes.

Explanation

Correct Answer

B:

The governing distinction is: Topic descriptions and instructions guide appropriate task selection. In this membership renewals scenario, this separates supported agent behavior from assumptions about the AI model. Because a service agent handles warranty inspection but its broad existing topic attracts unrelated requests, the intended response is to add a custom topic with focused scope and clear routing instructions. An observable check is that warranty questions enter the custom topic while unrelated shipping questions do not.

Incorrect Answers

A:

The idea “Standard agent topics can be reused when they already fit the task; interpret this as distinct from unrelated UI configuration” explains another source-defined situation: A customer asks for a common supported case status operation already provided by a standard Agentforce topic. The correction must ensure that part inventory decisions use approved current records. That situation depends on: Standard agent topics can be reused when they already fit the task. The present question instead concerns a service agent handles warranty inspection but its broad existing topic attracts unrelated requests. The correction must ensure that member records cannot be exposed to other members. Its directly relevant mechanism is: Topic descriptions and instructions guide appropriate task selection.

C:

The idea “Natural-language instructions alone are weaker than deterministic protected-action controls; interpret this rather than assuming a generative instruction is an access rule” explains another source-defined situation: A refund action accepts an unverified customer amount and bypasses the approved amount limit. The correction must ensure that member records cannot be exposed to other members. That situation depends on: Natural-language instructions alone are weaker than deterministic protected-action controls. The present question instead concerns a service agent handles warranty inspection but its broad existing topic attracts unrelated requests. The correction must ensure that member records cannot be exposed to other members. Its directly relevant mechanism is: Topic descriptions and instructions guide appropriate task selection.

D:

The idea “API connectivity does not override CRM or agent execution authorization; interpret this as a necessary control for deterministic outcomes” explains another source-defined situation: An application uses a wide integration credential to call agents for multiple unrelated tenants. The correction must ensure that production changes remain gated by approval. That situation depends on: API connectivity does not override CRM or agent execution authorization. The present question instead concerns a service agent handles warranty inspection but its broad existing topic attracts unrelated requests. The correction must ensure that member records cannot be exposed to other members. Its directly relevant mechanism is: Topic descriptions and instructions guide appropriate task selection.

Question 13

At Greenwell Energy, a field technician assistance team is improving asset inspection after a customer-reported regression (SF-G02-02). The administrator observes that an agent sometimes emits policy-inconsistent responses but only uptime is monitored. Any fix must ensure that plant access boundaries are not weakened by chatbot replies. Which continuing control best prevents this issue from recurring?

  1. Validate observability setup when provisioning each agent; review it with audit evidence from regression testing.
  2. Set review thresholds for quality and safety indicators; review it with audit evidence from regression testing.
  3. Keep tracing and privacy retention practices reviewed; review it with a documented exception process.
  4. Alert on repeated action errors and confirm fixes with retests; review it before expanding channel availability.

Explanation

Correct Answer

B:

The preventive control directly addresses repeat failures: Set review thresholds for quality and safety indicators; require the check in the next release review at Greenwell Energy (SF-G02-02). It complements the corrective action, track instruction adherence and relevant safety metrics alongside availability, and protects the explicit condition that plant access boundaries are not weakened by chatbot replies.

Incorrect Answers

A:

This safeguard, “Validate observability setup when provisioning each agent; review it with audit evidence from regression testing”, reduces a different source-defined risk: An analytics dashboard shows empty agent session charts after rollout. The correction must ensure that member records cannot be exposed to other members. That risk depends on: Monitoring dashboards depend on instrumentation and data ingestion. The recurring problem here is an agent sometimes emits policy-inconsistent responses but only uptime is monitored. The correction must ensure that plant access boundaries are not weakened by chatbot replies. The originally selected control “Set review thresholds for quality and safety indicators; review it with audit evidence from regression testing” is more specific because agent health includes trust and quality measures as well as uptime.

C:

This safeguard, “Keep tracing and privacy retention practices reviewed; review it with a documented exception process”, reduces a different source-defined risk: Operators receive complaint tickets but cannot correlate them to failing agent sessions. The correction must ensure that student records never cross program authorization boundaries. That risk depends on: Observability provides evidence of actual runtime behavior rather than anecdotes. The recurring problem here is an agent sometimes emits policy-inconsistent responses but only uptime is monitored. The correction must ensure that plant access boundaries are not weakened by chatbot replies. The originally selected control “Set review thresholds for quality and safety indicators; review it with audit evidence from regression testing” is more specific because agent health includes trust and quality measures as well as uptime.

D:

This safeguard, “Alert on repeated action errors and confirm fixes with retests; review it before expanding channel availability”, reduces a different source-defined risk: One custom action intermittently fails but average conversation ratings remain high. The correction must ensure that service changes follow approved warranty conditions. That risk depends on: Action telemetry supports targeted repair that broad satisfaction scores cannot. The recurring problem here is an agent sometimes emits policy-inconsistent responses but only uptime is monitored. The correction must ensure that plant access boundaries are not weakened by chatbot replies. The originally selected control “Set review thresholds for quality and safety indicators; review it with audit evidence from regression testing” is more specific because agent health includes trust and quality measures as well as uptime.

Question 14

At Alpine Hospitality, a concierge service organization is improving guest escalation after a customer-reported regression (SF-T05-01). The administrator observes that the test suite passes replies but chooses the wrong subagent for escalation requests. Any fix must ensure that escalations preserve only the needed guest context. Which underlying Agentforce or Salesforce design principle explains the appropriate approach?

  1. Subagent evaluation measures routing independent of response wording; interpret this as a necessary control for deterministic outcomes.
  2. Test results must be adjudicated when expected outcomes become obsolete; interpret this while preserving the specified source of truth.
  3. A passing final response does not prove the correct action path; interpret this independent of the surface wording of the conversation.
  4. Agent lifecycle requires version control and recoverable release states; interpret this rather than assuming a generative instruction is an access rule.

Explanation

Correct Answer

A:

The governing distinction is: Subagent evaluation measures routing independent of response wording. In this guest escalation scenario, this separates supported agent behavior from assumptions about the AI model. Because the test suite passes replies but chooses the wrong subagent for escalation requests, the intended response is to inspect expected and actual subagent selections and adjust routing criteria. An observable check is that escalation utterances route to the intended subagent in repeat tests.

Incorrect Answers

B:

The idea “Test results must be adjudicated when expected outcomes become obsolete; interpret this while preserving the specified source of truth” explains another source-defined situation: A test fails because its expected action list references a removed legacy action. The correction must ensure that citizen information stays limited to the relevant case. That situation depends on: Test results must be adjudicated when expected outcomes become obsolete. The present question instead concerns the test suite passes replies but chooses the wrong subagent for escalation requests. The correction must ensure that escalations preserve only the needed guest context. Its directly relevant mechanism is: Subagent evaluation measures routing independent of response wording.

C:

The idea “A passing final response does not prove the correct action path; interpret this independent of the surface wording of the conversation” explains another source-defined situation: Testing Center reports the correct response text but the wrong configured action executed. The correction must ensure that guest profile fields are used only with permitted access. That situation depends on: A passing final response does not prove the correct action path. The present question instead concerns the test suite passes replies but chooses the wrong subagent for escalation requests. The correction must ensure that escalations preserve only the needed guest context. Its directly relevant mechanism is: Subagent evaluation measures routing independent of response wording.

D:

The idea “Agent lifecycle requires version control and recoverable release states; interpret this rather than assuming a generative instruction is an access rule” explains another source-defined situation: A newly activated agent version gives an incorrect action routing during rollout. The correction must ensure that donor details cannot be revealed across accounts. That situation depends on: Agent lifecycle requires version control and recoverable release states. The present question instead concerns the test suite passes replies but chooses the wrong subagent for escalation requests. The correction must ensure that escalations preserve only the needed guest context. Its directly relevant mechanism is: Subagent evaluation measures routing independent of response wording.

Question 15

At Westmoor Sports, a consumer membership desk is improving membership renewals as a new data source is onboarded (SF-A21-02). The administrator observes that a service agent action runs with a privileged user context that grants excessive record visibility. Any fix must ensure that member records cannot be exposed to other members. Which observable result would best demonstrate that the correction actually worked?

  1. A high-severity case remains open until required approval is recorded; confirm this and compare with approved baseline behavior.
  2. A user without field access cannot obtain the protected value through the agent; confirm this using a least-privilege test identity.
  3. A cross-account record access test fails under the agent's runtime security context; confirm this using a least-privilege test identity.
  4. An employee can retrieve internal policy guidance while an external user cannot; confirm this using a representative sandbox fixture.

Explanation

Correct Answer

C:

This is the direct acceptance signal for the reported failure: In a controlled Contact acceptance test, a cross-account record access test fails under the agent's runtime security context; the record is retained under Westmoor Sports's rollout (SF-A21-02). The chosen correction was to configure and verify the actual agent user and execution permissions for the action; the measurement therefore tests the relevant source, routing or authorization outcome rather than unrelated activity.

Incorrect Answers

A:

The proposed observation “A high-severity case remains open until required approval is recorded; confirm this and compare with approved baseline behavior” would check a different original case: An agent would close a high-severity case directly without the required human approval. The correction must ensure that service changes follow approved warranty conditions. Its mechanism is: Sensitive agent operations need deterministic approval gates beyond conversational requests. In the present case, a service agent action runs with a privileged user context that grants excessive record visibility. The correction must ensure that member records cannot be exposed to other members; the more direct acceptance evidence is “A cross-account record access test fails under the agent's runtime security context; confirm this using a least-privilege test identity” because the user identity executing an action determines which permissions can apply.

B:

The proposed observation “A user without field access cannot obtain the protected value through the agent; confirm this using a least-privilege test identity” would check a different original case: A template returns a confidential account field in a customer-facing response. The correction must ensure that policy terms come from the current approved revision. Its mechanism is: Field-level security still governs agent grounding and action results. In the present case, a service agent action runs with a privileged user context that grants excessive record visibility. The correction must ensure that member records cannot be exposed to other members; the more direct acceptance evidence is “A cross-account record access test fails under the agent's runtime security context; confirm this using a least-privilege test identity” because the user identity executing an action determines which permissions can apply.

D:

The proposed observation “An employee can retrieve internal policy guidance while an external user cannot; confirm this using a representative sandbox fixture” would check a different original case: Employees need internal HR and IT knowledge while customers must not see confidential responses. The correction must ensure that quoted amounts use authorized account and price-book records. Its mechanism is: Employee agents target workforce use cases rather than unauthenticated service traffic. In the present case, a service agent action runs with a privileged user context that grants excessive record visibility. The correction must ensure that member records cannot be exposed to other members; the more direct acceptance evidence is “A cross-account record access test fails under the agent's runtime security context; confirm this using a least-privilege test identity” because the user identity executing an action determines which permissions can apply.

Question 16

At Harbor Logistics, a distribution operations team is improving shipment exception triage after a documented configuration change (SF-D16-01). The administrator observes that an LLM response requires current account status stored in a structured DMO rather than long documents. Any fix must ensure that shipment changes remain attributable and reversible. Which action best addresses the issue while preserving the stated requirement?

  1. Use a supported structured data grounding path for the permitted account fields; implement it with a named deployment owner.
  2. Adjust the retriever result count and chunk design to include required related context; implement it with least-privilege execution.
  3. Use a coherent chunking strategy to index smaller meaningful guide sections; implement it with a named deployment owner.
  4. Check source ingestion, indexing readiness and retriever association before changing the prompt; implement it with least-privilege execution.

Explanation

Correct Answer

A:

The documented failure is that an LLM response requires current account status stored in a structured DMO rather than long documents. Use a supported structured data grounding path for the permitted account fields for Harbor Logistics's shipment exception triage workflow (SF-D16-01) while respecting that shipment changes remain attributable and reversible. Its outcome is not established merely by changing instructions: In a controlled Shipment__c acceptance test, test output reflects exact account status with the right record ID; the record is retained under Harbor Logistics's rollout (SF-D16-01). The underlying reason is that Structured record grounding differs from unstructured chunk search. In this shipment exception triage scenario, this separates supported agent behavior from assumptions about the AI model.

Incorrect Answers

B:

The action “Adjust the retriever result count and chunk design to include required related context; implement it with least-privilege execution” addresses a separate source case: A high-confidence answer cites an incomplete single chunk when the procedure spans several sections. The correction must ensure that financial identifiers are masked outside authorized roles. Its underlying reason is: Retrieval window and chunk boundaries together affect grounding completeness. This question instead describes an LLM response requires current account status stored in a structured DMO rather than long documents. The correction must ensure that shipment changes remain attributable and reversible. The original answer “Use a supported structured data grounding path for the permitted account fields; implement it with a named deployment owner” targets that failure because structured record grounding differs from unstructured chunk search.

C:

The action “Use a coherent chunking strategy to index smaller meaningful guide sections; implement it with a named deployment owner” addresses a separate source case: A twenty-page support guide is indexed as one oversized passage and retrieval is imprecise. The correction must ensure that employee procedures cannot be exposed to anonymous users. Its underlying reason is: Chunking trades passage granularity against preservation of useful context. This question instead describes an LLM response requires current account status stored in a structured DMO rather than long documents. The correction must ensure that shipment changes remain attributable and reversible. The original answer “Use a supported structured data grounding path for the permitted account fields; implement it with a named deployment owner” targets that failure because structured record grounding differs from unstructured chunk search.

D:

The action “Check source ingestion, indexing readiness and retriever association before changing the prompt; implement it with least-privilege execution” addresses a separate source case: A knowledge-backed agent has no useful results after initial library setup. The correction must ensure that guest profile fields are used only with permitted access. Its underlying reason is: Data-library setup is a pipeline with dependent indexing and retrieval stages. This question instead describes an LLM response requires current account status stored in a structured DMO rather than long documents. The correction must ensure that shipment changes remain attributable and reversible. The original answer “Use a supported structured data grounding path for the permitted account fields; implement it with a named deployment owner” targets that failure because structured record grounding differs from unstructured chunk search.

Question 17

At Harbor Logistics, a distribution operations team is improving shipment exception triage during cross-channel acceptance testing (SF-A17-03). The administrator observes that a service agent is configured but customers cannot reach it from the approved support site. Any fix must ensure that shipment changes remain attributable and reversible. Which observable result would best demonstrate that the correction actually worked?

  1. An end user opens the authorized support entry point and sees the intended agent behavior; confirm this and retain a reproducible test record.
  2. A test email follows the expected intake and response handling without a live-chat assumption; confirm this using a least-privilege test identity.
  3. A Slack user sees only authorized internal actions and records; confirm this with production-equivalent source conditions.
  4. An authenticated application request receives a valid agent response and session mapping; confirm this and retain a reproducible test record.

Explanation

Correct Answer

A:

This is the direct acceptance signal for the reported failure: In a controlled Shipment__c acceptance test, an end user opens the authorized support entry point and sees the intended agent behavior; the record is retained under Harbor Logistics's rollout (SF-A17-03). The chosen correction was to connect the appropriate supported digital experience channel and test the service session; the measurement therefore tests the relevant source, routing or authorization outcome rather than unrelated activity.

Incorrect Answers

B:

The proposed observation “A test email follows the expected intake and response handling without a live-chat assumption; confirm this using a least-privilege test identity” would check a different original case: A team assumes an asynchronous support email flow has the same state and latency as an interactive web chat. The correction must ensure that billing adjustments require verified eligibility. Its mechanism is: Channel context changes how an agent receives messages and maintains interaction. In the present case, a service agent is configured but customers cannot reach it from the approved support site. The correction must ensure that shipment changes remain attributable and reversible; the more direct acceptance evidence is “An end user opens the authorized support entry point and sees the intended agent behavior; confirm this and retain a reproducible test record” because an agent definition does not automatically establish its channel delivery.

C:

The proposed observation “A Slack user sees only authorized internal actions and records; confirm this with production-equivalent source conditions” would check a different original case: Internal employees expect the company agent in Slack but the connector exposes an unrelated public service agent. The correction must ensure that quoted amounts use authorized account and price-book records. Its mechanism is: Channel connections must preserve the intended audience and authorization context. In the present case, a service agent is configured but customers cannot reach it from the approved support site. The correction must ensure that shipment changes remain attributable and reversible; the more direct acceptance evidence is “An end user opens the authorized support entry point and sees the intended agent behavior; confirm this and retain a reproducible test record” because an agent definition does not automatically establish its channel delivery.

D:

The proposed observation “An authenticated application request receives a valid agent response and session mapping; confirm this and retain a reproducible test record” would check a different original case: A custom mobile application needs server-driven interaction with an already configured Agentforce agent. The correction must ensure that policy terms come from the current approved revision. Its mechanism is: Agent API enables programmatic agent interaction from external applications. In the present case, a service agent is configured but customers cannot reach it from the approved support site. The correction must ensure that shipment changes remain attributable and reversible; the more direct acceptance evidence is “An end user opens the authorized support entry point and sees the intended agent behavior; confirm this and retain a reproducible test record” because an agent definition does not automatically establish its channel delivery.

Question 18

At Fairmont Finance, a regulated client experience team is improving account onboarding during an agent routing evaluation (SF-D14-01). The administrator observes that a high-confidence answer cites an incomplete single chunk when the procedure spans several sections. Any fix must ensure that financial identifiers are masked outside authorized roles. Which continuing control best prevents this issue from recurring?

  1. Maintain separate index and retriever change records; review it with a documented exception process.
  2. Verify mapping, field-level permissions, and data freshness; review it with audit evidence from regression testing.
  3. Review recall and precision with a documented question set; review it and retest after dependent metadata changes.
  4. Test queries that might tempt use of unrelated public data; review it after configuration or data-source updates.

Explanation

Correct Answer

C:

The preventive control directly addresses repeat failures: Review recall and precision with a documented question set; require the check in the next release review at Fairmont Finance (SF-D14-01). It complements the corrective action, adjust the retriever result count and chunk design to include required related context, and protects the explicit condition that financial identifiers are masked outside authorized roles.

Incorrect Answers

A:

This safeguard, “Maintain separate index and retriever change records; review it with a documented exception process”, reduces a different source-defined risk: A team creates a search index and expects prompt templates to query it without a retriever. The correction must ensure that billing adjustments require verified eligibility. That risk depends on: Search indexes organize content; retrievers select relevant indexed content for a use case. The recurring problem here is a high-confidence answer cites an incomplete single chunk when the procedure spans several sections. The correction must ensure that financial identifiers are masked outside authorized roles. The originally selected control “Review recall and precision with a documented question set; review it and retest after dependent metadata changes” is more specific because retrieval window and chunk boundaries together affect grounding completeness.

B:

This safeguard, “Verify mapping, field-level permissions, and data freshness; review it with audit evidence from regression testing”, reduces a different source-defined risk: An LLM response requires current account status stored in a structured DMO rather than long documents. The correction must ensure that shipment changes remain attributable and reversible. That risk depends on: Structured record grounding differs from unstructured chunk search. The recurring problem here is a high-confidence answer cites an incomplete single chunk when the procedure spans several sections. The correction must ensure that financial identifiers are masked outside authorized roles. The originally selected control “Review recall and precision with a documented question set; review it and retest after dependent metadata changes” is more specific because retrieval window and chunk boundaries together affect grounding completeness.

D:

This safeguard, “Test queries that might tempt use of unrelated public data; review it after configuration or data-source updates”, reduces a different source-defined risk: A private reimbursement policy is being answered with generic public web snippets. The correction must ensure that plant access boundaries are not weakened by chatbot replies. That risk depends on: Source boundaries should reflect whether knowledge is internal, external, or confidential. The recurring problem here is a high-confidence answer cites an incomplete single chunk when the procedure spans several sections. The correction must ensure that financial identifiers are masked outside authorized roles. The originally selected control “Review recall and precision with a documented question set; review it and retest after dependent metadata changes” is more specific because retrieval window and chunk boundaries together affect grounding completeness.

Question 19

At Fairmont Finance, a regulated client experience team is improving account onboarding during a least-privilege verification (SF-A10-02). The administrator observes that an agent sometimes sends cancellation requests for orders that are already shipped. Any fix must ensure that financial identifiers are masked outside authorized roles. Which observable result would best demonstrate that the correction actually worked?

  1. Missing-input tests follow a deliberate fallback branch without accidental action execution; confirm this while testing the unauthorized case.
  2. Two consecutive credit requests produce at most one approved credit action; confirm this and compare with approved baseline behavior.
  3. An over-limit request is denied before any payment record is changed; confirm this and retain a reproducible test record.
  4. A shipped-order test cannot invoke cancellation while eligible orders can; confirm this while testing the unauthorized case.

Explanation

Correct Answer

D:

This is the direct acceptance signal for the reported failure: In a controlled Account acceptance test, a shipped-order test cannot invoke cancellation while eligible orders can; the record is retained under Fairmont Finance's rollout (SF-A10-02). The chosen correction was to filter the cancellation action on the required order state before execution; the measurement therefore tests the relevant source, routing or authorization outcome rather than unrelated activity.

Incorrect Answers

A:

The proposed observation “Missing-input tests follow a deliberate fallback branch without accidental action execution; confirm this while testing the unauthorized case” would check a different original case: Dynamic script instructions expose an empty variable in a critical business condition. The correction must ensure that billing adjustments require verified eligibility. Its mechanism is: Template expression correctness depends on typed variables and explicit conditions. In the present case, an agent sometimes sends cancellation requests for orders that are already shipped. The correction must ensure that financial identifiers are masked outside authorized roles; the more direct acceptance evidence is “A shipped-order test cannot invoke cancellation while eligible orders can; confirm this while testing the unauthorized case” because action filters constrain which actions are available under defined conditions.

B:

The proposed observation “Two consecutive credit requests produce at most one approved credit action; confirm this and compare with approved baseline behavior” would check a different original case: An agent issues a customer credit twice during one support session after a repeated request. The correction must ensure that safety-critical changes need an attributable human approval. Its mechanism is: A mutable state flag can enforce a rule independent of LLM wording. In the present case, an agent sometimes sends cancellation requests for orders that are already shipped. The correction must ensure that financial identifiers are masked outside authorized roles; the more direct acceptance evidence is “A shipped-order test cannot invoke cancellation while eligible orders can; confirm this while testing the unauthorized case” because action filters constrain which actions are available under defined conditions.

C:

The proposed observation “An over-limit request is denied before any payment record is changed; confirm this and retain a reproducible test record” would check a different original case: A refund action accepts an unverified customer amount and bypasses the approved amount limit. The correction must ensure that member records cannot be exposed to other members. Its mechanism is: Natural-language instructions alone are weaker than deterministic protected-action controls. In the present case, an agent sometimes sends cancellation requests for orders that are already shipped. The correction must ensure that financial identifiers are masked outside authorized roles; the more direct acceptance evidence is “A shipped-order test cannot invoke cancellation while eligible orders can; confirm this while testing the unauthorized case” because action filters constrain which actions are available under defined conditions.

Question 20

At Redfern Aviation, a supplier operations group is improving spare-part quotations during an agent routing evaluation (SF-D11-01). The administrator observes that product support queries contain error IDs alongside natural-language descriptions. Any fix must ensure that supplier prices are never shown outside entitled teams. Which action best addresses the issue while preserving the stated requirement?

  1. Use a coherent chunking strategy to index smaller meaningful guide sections; implement it with a named deployment owner.
  2. Create the search index over the appropriate DMO content and fields; implement it with traceable change approval.
  3. Use a hybrid keyword-and-vector search configuration for the indexed knowledge; implement it within the documented Salesforce configuration.
  4. Consolidate or precisely filter the approved current source before routing retrieval; implement it before the next environment promotion.

Explanation

Correct Answer

C:

The documented failure is that product support queries contain error IDs alongside natural-language descriptions. Use a hybrid keyword-and-vector search configuration for the indexed knowledge for Redfern Aviation's spare-part quotations workflow (SF-D11-01) while respecting that supplier prices are never shown outside entitled teams. Its outcome is not established merely by changing instructions: In a controlled Quote acceptance test, tests retrieve the exact error-code guidance and semantically relevant explanations; the record is retained under Redfern Aviation's rollout (SF-D11-01). The underlying reason is that Hybrid retrieval can combine exact lexical signals with semantic similarity. In this spare-part quotations scenario, this separates supported agent behavior from assumptions about the AI model.

Incorrect Answers

A:

The action “Use a coherent chunking strategy to index smaller meaningful guide sections; implement it with a named deployment owner” addresses a separate source case: A twenty-page support guide is indexed as one oversized passage and retrieval is imprecise. The correction must ensure that employee procedures cannot be exposed to anonymous users. Its underlying reason is: Chunking trades passage granularity against preservation of useful context. This question instead describes product support queries contain error IDs alongside natural-language descriptions. The correction must ensure that supplier prices are never shown outside entitled teams. The original answer “Use a hybrid keyword-and-vector search configuration for the indexed knowledge; implement it within the documented Salesforce configuration” targets that failure because hybrid retrieval can combine exact lexical signals with semantic similarity.

B:

The action “Create the search index over the appropriate DMO content and fields; implement it with traceable change approval” addresses a separate source case: A Data 360 source is ingested but no searchable index exists for its content. The correction must ensure that student records never cross program authorization boundaries. Its underlying reason is: Ingestion alone does not provide retriever-ready search access. This question instead describes product support queries contain error IDs alongside natural-language descriptions. The correction must ensure that supplier prices are never shown outside entitled teams. The original answer “Use a hybrid keyword-and-vector search configuration for the indexed knowledge; implement it within the documented Salesforce configuration” targets that failure because hybrid retrieval can combine exact lexical signals with semantic similarity.

D:

The action “Consolidate or precisely filter the approved current source before routing retrieval; implement it before the next environment promotion” addresses a separate source case: Two overlapping libraries contain conflicting versions of the same return policy. The correction must ensure that copyrighted manuscripts remain within the approved workspace. Its underlying reason is: Duplicate knowledge sources can make retrieval ambiguous even with correct prompts. This question instead describes product support queries contain error IDs alongside natural-language descriptions. The correction must ensure that supplier prices are never shown outside entitled teams. The original answer “Use a hybrid keyword-and-vector search configuration for the indexed knowledge; implement it within the documented Salesforce configuration” targets that failure because hybrid retrieval can combine exact lexical signals with semantic similarity.