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 77

Question 760

At Delta Transit, a passenger support center is improving service disruption updates during a least-privilege verification (SF-D11-02). The administrator observes that product support queries contain error IDs alongside natural-language descriptions. Any fix must ensure that safety-critical changes need an attributable human approval. Which underlying Agentforce or Salesforce design principle explains the appropriate approach?

  1. Hybrid retrieval can combine exact lexical signals with semantic similarity; interpret this with boundaries enforced by supported platform controls.
  2. Structured record grounding differs from unstructured chunk search; interpret this independent of the surface wording of the conversation.
  3. Ingestion alone does not provide retriever-ready search access; interpret this rather than assuming a generative instruction is an access rule.
  4. Data-library setup is a pipeline with dependent indexing and retrieval stages; interpret this as distinct from unrelated UI configuration.

Explanation

Correct Answer

A:

The governing distinction is: Hybrid retrieval can combine exact lexical signals with semantic similarity. In this service disruption updates scenario, this separates supported agent behavior from assumptions about the AI model. Because product support queries contain error IDs alongside natural-language descriptions, the intended response is to use a hybrid keyword-and-vector search configuration for the indexed knowledge. An observable check is that tests retrieve the exact error-code guidance and semantically relevant explanations.

Incorrect Answers

B:

The idea “Structured record grounding differs from unstructured chunk search; interpret this independent of the surface wording of the conversation” explains another source-defined situation: 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 situation depends on: Structured record grounding differs from unstructured chunk search. The present question instead concerns product support queries contain error IDs alongside natural-language descriptions. The correction must ensure that safety-critical changes need an attributable human approval. Its directly relevant mechanism is: Hybrid retrieval can combine exact lexical signals with semantic similarity.

C:

The idea “Ingestion alone does not provide retriever-ready search access; interpret this rather than assuming a generative instruction is an access rule” explains another source-defined situation: 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. That situation depends on: Ingestion alone does not provide retriever-ready search access. The present question instead concerns product support queries contain error IDs alongside natural-language descriptions. The correction must ensure that safety-critical changes need an attributable human approval. Its directly relevant mechanism is: Hybrid retrieval can combine exact lexical signals with semantic similarity.

D:

The idea “Data-library setup is a pipeline with dependent indexing and retrieval stages; interpret this as distinct from unrelated UI configuration” explains another source-defined situation: 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. That situation depends on: Data-library setup is a pipeline with dependent indexing and retrieval stages. The present question instead concerns product support queries contain error IDs alongside natural-language descriptions. The correction must ensure that safety-critical changes need an attributable human approval. Its directly relevant mechanism is: Hybrid retrieval can combine exact lexical signals with semantic similarity.

Question 761

At Yardley Homes, a property warranty contact center is improving warranty service after a customer-reported regression (SF-G04-03). The administrator observes that an analytics dashboard shows empty agent session charts after rollout. Any fix must ensure that service changes follow approved warranty conditions. Which continuing control best prevents this issue from recurring?

  1. Validate observability setup when provisioning each agent; review it and confirm the control remains effective after release.
  2. Set review thresholds for quality and safety indicators; review it and retest after dependent metadata changes.
  3. Track resolution and escalation causes over time; review it with a documented exception process.
  4. Review knowledge quality trends after ingestion changes; review it as part of periodic access and quality reviews.

Explanation

Correct Answer

A:

The preventive control directly addresses repeat failures: Validate observability setup when provisioning each agent; require the check in the next release review at Yardley Homes (SF-G04-03). It complements the corrective action, verify appropriate session trace, audit, feedback and analytics setup, and protects the explicit condition that service changes follow approved warranty conditions.

Incorrect Answers

B:

This safeguard, “Set review thresholds for quality and safety indicators; review it and retest after dependent metadata changes”, reduces a different source-defined risk: An agent sometimes emits policy-inconsistent responses but only uptime is monitored. The correction must ensure that employee case files are accessible only to the case owner. That risk depends on: Agent health includes trust and quality measures as well as uptime. The recurring problem here is an analytics dashboard shows empty agent session charts after rollout. The correction must ensure that service changes follow approved warranty conditions. The originally selected control “Validate observability setup when provisioning each agent; review it and confirm the control remains effective after release” is more specific because monitoring dashboards depend on instrumentation and data ingestion.

C:

This safeguard, “Track resolution and escalation causes over time; review it with a documented exception process”, reduces a different source-defined risk: A support agent has many sessions yet few requests reach a resolved state. The correction must ensure that plant access boundaries are not weakened by chatbot replies. That risk depends on: Session volume alone does not indicate successful business outcomes. The recurring problem here is an analytics dashboard shows empty agent session charts after rollout. The correction must ensure that service changes follow approved warranty conditions. The originally selected control “Validate observability setup when provisioning each agent; review it and confirm the control remains effective after release” is more specific because monitoring dashboards depend on instrumentation and data ingestion.

D:

This safeguard, “Review knowledge quality trends after ingestion changes; review it as part of periodic access and quality reviews”, reduces a different source-defined risk: Agent resolution scores fall when a new knowledge source is connected. The correction must ensure that policy terms come from the current approved revision. That risk depends on: Agent quality changes can arise from retrieval behavior as well as prompt text. The recurring problem here is an analytics dashboard shows empty agent session charts after rollout. The correction must ensure that service changes follow approved warranty conditions. The originally selected control “Validate observability setup when provisioning each agent; review it and confirm the control remains effective after release” is more specific because monitoring dashboards depend on instrumentation and data ingestion.

Question 762

At Harbor Logistics, a distribution operations team is improving shipment exception triage after a documented configuration change (SF-D14-03). The administrator observes that a high-confidence answer cites an incomplete single chunk when the procedure spans several sections. Any fix must ensure that shipment changes remain attributable and reversible. Which action best addresses the issue while preserving the stated requirement?

  1. Adjust the retriever result count and chunk design to include required related context; implement it within the documented Salesforce configuration.
  2. Use semantic vector search over suitable indexed text passages; implement it and keep the business rule enforceable.
  3. Create and activate a retriever tied to the desired search index and bind it in the prompt; implement it before the next environment promotion.
  4. Consolidate or precisely filter the approved current source before routing retrieval; implement it before the next environment promotion.

Explanation

Correct Answer

A:

The documented failure is that a high-confidence answer cites an incomplete single chunk when the procedure spans several sections. Adjust the retriever result count and chunk design to include required related context for Harbor Logistics's shipment exception triage workflow (SF-D14-03) 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 questions return the prerequisite and exception sections needed for a correct response; the record is retained under Harbor Logistics's rollout (SF-D14-03). The underlying reason is that Retrieval window and chunk boundaries together affect grounding completeness. In this shipment exception triage scenario, this separates supported agent behavior from assumptions about the AI model.

Incorrect Answers

B:

The action “Use semantic vector search over suitable indexed text passages; implement it and keep the business rule enforceable” addresses a separate source case: Users describe a known policy concept using varied language absent from the document title. The correction must ensure that safety-critical changes need an attributable human approval. Its underlying reason is: Vector retrieval matches semantic similarity rather than requiring exact words. This question instead describes a high-confidence answer cites an incomplete single chunk when the procedure spans several sections. The correction must ensure that shipment changes remain attributable and reversible. The original answer “Adjust the retriever result count and chunk design to include required related context; implement it within the documented Salesforce configuration” targets that failure because retrieval window and chunk boundaries together affect grounding completeness.

C:

The action “Create and activate a retriever tied to the desired search index and bind it in the prompt; implement it before the next environment promotion” addresses a separate source case: 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. Its underlying reason is: Search indexes organize content; retrievers select relevant indexed content for a use case. This question instead describes a high-confidence answer cites an incomplete single chunk when the procedure spans several sections. The correction must ensure that shipment changes remain attributable and reversible. The original answer “Adjust the retriever result count and chunk design to include required related context; implement it within the documented Salesforce configuration” targets that failure because retrieval window and chunk boundaries together affect grounding completeness.

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 a high-confidence answer cites an incomplete single chunk when the procedure spans several sections. The correction must ensure that shipment changes remain attributable and reversible. The original answer “Adjust the retriever result count and chunk design to include required related context; implement it within the documented Salesforce configuration” targets that failure because retrieval window and chunk boundaries together affect grounding completeness.

Question 763

At Yardley Homes, a property warranty contact center is improving warranty service before expanding the internal rollout (SF-A22-03). The administrator observes that an action attempts to read a protected custom object based only on a user's natural-language request. Any fix must ensure that service changes follow approved warranty conditions. Which underlying Agentforce or Salesforce design principle explains the appropriate approach?

  1. An agent conversation is not an authorization bypass for CRM data; interpret this rather than assuming a generative instruction is an access rule.
  2. Sensitive agent operations need deterministic approval gates beyond conversational requests; interpret this while preserving the specified source of truth.
  3. The user identity executing an action determines which permissions can apply; interpret this as a necessary control for deterministic outcomes.
  4. API connectivity does not override CRM or agent execution authorization; interpret this as a necessary control for deterministic outcomes.

Explanation

Correct Answer

A:

The governing distinction is: An agent conversation is not an authorization bypass for CRM data. In this warranty service scenario, this separates supported agent behavior from assumptions about the AI model. Because an action attempts to read a protected custom object based only on a user's natural-language request, the intended response is to enforce object and record authorization in the underlying action or automation. An observable check is that the agent declines or safely escalates an unauthorized object request.

Incorrect Answers

B:

The idea “Sensitive agent operations need deterministic approval gates beyond conversational requests; interpret this while preserving the specified source of truth” explains another source-defined situation: 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. That situation depends on: Sensitive agent operations need deterministic approval gates beyond conversational requests. The present question instead concerns an action attempts to read a protected custom object based only on a user's natural-language request. The correction must ensure that service changes follow approved warranty conditions. Its directly relevant mechanism is: An agent conversation is not an authorization bypass for CRM data.

C:

The idea “The user identity executing an action determines which permissions can apply; interpret this as a necessary control for deterministic outcomes” explains another source-defined situation: A service agent action runs with a privileged user context that grants excessive record visibility. The correction must ensure that plant access boundaries are not weakened by chatbot replies. That situation depends on: The user identity executing an action determines which permissions can apply. The present question instead concerns an action attempts to read a protected custom object based only on a user's natural-language request. The correction must ensure that service changes follow approved warranty conditions. Its directly relevant mechanism is: An agent conversation is not an authorization bypass for CRM data.

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 an action attempts to read a protected custom object based only on a user's natural-language request. The correction must ensure that service changes follow approved warranty conditions. Its directly relevant mechanism is: An agent conversation is not an authorization bypass for CRM data.

Question 764

At Ironwood Insurance, a claims service team is improving claims guidance after a knowledge-policy revision (SF-D03-03). The administrator observes that a private reimbursement policy is being answered with generic public web snippets. Any fix must ensure that policy terms come from the current approved revision. Which underlying Agentforce or Salesforce design principle explains the appropriate approach?

  1. Source boundaries should reflect whether knowledge is internal, external, or confidential; interpret this independent of the surface wording of the conversation.
  2. A library answer depends on the freshness of its ingested and indexed content; interpret this without inferring extra permissions from an LLM response.
  3. Knowledge availability requires both indexing and audience-aware scope controls; interpret this with boundaries enforced by supported platform controls.
  4. Ingestion alone does not provide retriever-ready search access; interpret this rather than assuming a generative instruction is an access rule.

Explanation

Correct Answer

A:

The governing distinction is: Source boundaries should reflect whether knowledge is internal, external, or confidential. In this claims guidance scenario, this separates supported agent behavior from assumptions about the AI model. Because a private reimbursement policy is being answered with generic public web snippets, the intended response is to use an approved internal Data Library rather than ungoverned external web results. An observable check is that answer traces show internal approved reimbursement sections as the grounding source.

Incorrect Answers

B:

The idea “A library answer depends on the freshness of its ingested and indexed content; interpret this without inferring extra permissions from an LLM response” explains another source-defined situation: A revised employee handbook was uploaded but an agent still cites the prior edition. The correction must ensure that employee case files are accessible only to the case owner. That situation depends on: A library answer depends on the freshness of its ingested and indexed content. The present question instead concerns a private reimbursement policy is being answered with generic public web snippets. The correction must ensure that policy terms come from the current approved revision. Its directly relevant mechanism is: Source boundaries should reflect whether knowledge is internal, external, or confidential.

C:

The idea “Knowledge availability requires both indexing and audience-aware scope controls; interpret this with boundaries enforced by supported platform controls” explains another source-defined situation: Two subsidiaries share a platform but must not retrieve each other's knowledge documents. The correction must ensure that member records cannot be exposed to other members. That situation depends on: Knowledge availability requires both indexing and audience-aware scope controls. The present question instead concerns a private reimbursement policy is being answered with generic public web snippets. The correction must ensure that policy terms come from the current approved revision. Its directly relevant mechanism is: Source boundaries should reflect whether knowledge is internal, external, or confidential.

D:

The idea “Ingestion alone does not provide retriever-ready search access; interpret this rather than assuming a generative instruction is an access rule” explains another source-defined situation: 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. That situation depends on: Ingestion alone does not provide retriever-ready search access. The present question instead concerns a private reimbursement policy is being answered with generic public web snippets. The correction must ensure that policy terms come from the current approved revision. Its directly relevant mechanism is: Source boundaries should reflect whether knowledge is internal, external, or confidential.

Question 765

At Bluehaven University, an internal student services team is improving student advising after a documented configuration change (SF-D09-02). The administrator observes that a twenty-page support guide is indexed as one oversized passage and retrieval is imprecise. Any fix must ensure that student records never cross program authorization boundaries. Which observable result would best demonstrate that the correction actually worked?

  1. The template resolves expected retrieved passages during preview; confirm this and compare with approved baseline behavior.
  2. Test output reflects exact account status with the right record ID; confirm this with production-equivalent source conditions.
  3. A specific fault query retrieves the relevant troubleshooting section rather than the entire guide; confirm this while testing the unauthorized case.
  4. Test retrieval returns the authoritative effective-date policy without duplicate superseded passages; confirm this and compare with approved baseline behavior.

Explanation

Correct Answer

C:

This is the direct acceptance signal for the reported failure: In a controlled Student_Request__c acceptance test, a specific fault query retrieves the relevant troubleshooting section rather than the entire guide; the record is retained under Bluehaven University's rollout (SF-D09-02). The chosen correction was to use a coherent chunking strategy to index smaller meaningful guide sections; the measurement therefore tests the relevant source, routing or authorization outcome rather than unrelated activity.

Incorrect Answers

A:

The proposed observation “The template resolves expected retrieved passages during preview; confirm this and compare with approved baseline behavior” would check a different original case: 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. Its mechanism is: Search indexes organize content; retrievers select relevant indexed content for a use case. In the present case, a twenty-page support guide is indexed as one oversized passage and retrieval is imprecise. The correction must ensure that student records never cross program authorization boundaries; the more direct acceptance evidence is “A specific fault query retrieves the relevant troubleshooting section rather than the entire guide; confirm this while testing the unauthorized case” because chunking trades passage granularity against preservation of useful context.

B:

The proposed observation “Test output reflects exact account status with the right record ID; confirm this with production-equivalent source conditions” would check a different original case: 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. Its mechanism is: Structured record grounding differs from unstructured chunk search. In the present case, a twenty-page support guide is indexed as one oversized passage and retrieval is imprecise. The correction must ensure that student records never cross program authorization boundaries; the more direct acceptance evidence is “A specific fault query retrieves the relevant troubleshooting section rather than the entire guide; confirm this while testing the unauthorized case” because chunking trades passage granularity against preservation of useful context.

D:

The proposed observation “Test retrieval returns the authoritative effective-date policy without duplicate superseded passages; confirm this and compare with approved baseline behavior” would check a different original 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 mechanism is: Duplicate knowledge sources can make retrieval ambiguous even with correct prompts. In the present case, a twenty-page support guide is indexed as one oversized passage and retrieval is imprecise. The correction must ensure that student records never cross program authorization boundaries; the more direct acceptance evidence is “A specific fault query retrieves the relevant troubleshooting section rather than the entire guide; confirm this while testing the unauthorized case” because chunking trades passage granularity against preservation of useful context.

Question 766

At Delta Transit, a passenger support center is improving service disruption updates during a least-privilege verification (SF-D12-01). The administrator observes that users describe a known policy concept using varied language absent from the document title. Any fix must ensure that safety-critical changes need an attributable human approval. Which continuing control best prevents this issue from recurring?

  1. Check index build health when source schema changes; review it as part of periodic access and quality reviews.
  2. Verify mapping, field-level permissions, and data freshness; review it with audit evidence from regression testing.
  3. Retire obsolete chunks and review source precedence rules; review it with a documented exception process.
  4. Test representative paraphrases and inspect irrelevant near-matches; review it after configuration or data-source updates.

Explanation

Correct Answer

D:

The preventive control directly addresses repeat failures: Test representative paraphrases and inspect irrelevant near-matches; require the check in the next release review at Delta Transit (SF-D12-01). It complements the corrective action, use semantic vector search over suitable indexed text passages, and protects the explicit condition that safety-critical changes need an attributable human approval.

Incorrect Answers

A:

This safeguard, “Check index build health when source schema changes; review it as part of periodic access and quality reviews”, reduces a different source-defined risk: 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. That risk depends on: Ingestion alone does not provide retriever-ready search access. The recurring problem here is users describe a known policy concept using varied language absent from the document title. The correction must ensure that safety-critical changes need an attributable human approval. The originally selected control “Test representative paraphrases and inspect irrelevant near-matches; review it after configuration or data-source updates” is more specific because vector retrieval matches semantic similarity rather than requiring exact words.

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 users describe a known policy concept using varied language absent from the document title. The correction must ensure that safety-critical changes need an attributable human approval. The originally selected control “Test representative paraphrases and inspect irrelevant near-matches; review it after configuration or data-source updates” is more specific because vector retrieval matches semantic similarity rather than requiring exact words.

C:

This safeguard, “Retire obsolete chunks and review source precedence rules; review it with a documented exception process”, reduces a different source-defined risk: Two overlapping libraries contain conflicting versions of the same return policy. The correction must ensure that copyrighted manuscripts remain within the approved workspace. That risk depends on: Duplicate knowledge sources can make retrieval ambiguous even with correct prompts. The recurring problem here is users describe a known policy concept using varied language absent from the document title. The correction must ensure that safety-critical changes need an attributable human approval. The originally selected control “Test representative paraphrases and inspect irrelevant near-matches; review it after configuration or data-source updates” is more specific because vector retrieval matches semantic similarity rather than requiring exact words.

Question 767

At Valley Utilities, a customer billing center is improving billing questions after a documented configuration change (SF-A11-02). The administrator observes that an agent confuses a user-provided email address with the authenticated contact ID. Any fix must ensure that billing adjustments require verified eligibility. Which observable result would best demonstrate that the correction actually worked?

  1. Two consecutive credit requests produce at most one approved credit action; confirm this and compare with approved baseline behavior.
  2. A shipped-order test cannot invoke cancellation while eligible orders can; confirm this with production-equivalent source conditions.
  3. An attempted cross-account request fails despite a plausible supplied email address; confirm this using a representative sandbox fixture.
  4. An over-limit request is denied before any payment record is changed; confirm this and retain a reproducible test record.

Explanation

Correct Answer

C:

This is the direct acceptance signal for the reported failure: In a controlled Billing_Account__c acceptance test, an attempted cross-account request fails despite a plausible supplied email address; the record is retained under Valley Utilities's rollout (SF-A11-02). The chosen correction was to use trusted linked identity context for account-specific action authorization; the measurement therefore tests the relevant source, routing or authorization outcome rather than unrelated activity.

Incorrect Answers

A:

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 confuses a user-provided email address with the authenticated contact ID. The correction must ensure that billing adjustments require verified eligibility; the more direct acceptance evidence is “An attempted cross-account request fails despite a plausible supplied email address; confirm this using a representative sandbox fixture” because trusted linked identity is not interchangeable with unverified conversational text.

B:

The proposed observation “A shipped-order test cannot invoke cancellation while eligible orders can; confirm this with production-equivalent source conditions” would check a different original case: An agent sometimes sends cancellation requests for orders that are already shipped. The correction must ensure that sensitive product claims must cite approved knowledge. Its mechanism is: Action filters constrain which actions are available under defined conditions. In the present case, an agent confuses a user-provided email address with the authenticated contact ID. The correction must ensure that billing adjustments require verified eligibility; the more direct acceptance evidence is “An attempted cross-account request fails despite a plausible supplied email address; confirm this using a representative sandbox fixture” because trusted linked identity is not interchangeable with unverified conversational text.

D:

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 confuses a user-provided email address with the authenticated contact ID. The correction must ensure that billing adjustments require verified eligibility; the more direct acceptance evidence is “An attempted cross-account request fails despite a plausible supplied email address; confirm this using a representative sandbox fixture” because trusted linked identity is not interchangeable with unverified conversational text.

Question 768

At Redfern Aviation, a supplier operations group is improving spare-part quotations during cross-channel acceptance testing (SF-M02-01). The administrator observes that a basic FAQ workflow has one data source and no specialized actions yet architects propose six coordinating agents. 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. Define approved handoff inputs and evidence needed by the recipient agent; implement it within the documented Salesforce configuration.
  2. Keep a single appropriately scoped agent when multi-agent orchestration adds no control or scale benefit; implement it before the next environment promotion.
  3. Use separate specialized agents with controlled task delegation when the isolation benefit justifies complexity; implement it with least-privilege execution.
  4. Require authenticated agent identities and enforce recipient-side authorization for delegated tasks; implement it with a controlled rollback path.

Explanation

Correct Answer

B:

The documented failure is that a basic FAQ workflow has one data source and no specialized actions yet architects propose six coordinating agents. Keep a single appropriately scoped agent when multi-agent orchestration adds no control or scale benefit for Redfern Aviation's spare-part quotations workflow (SF-M02-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, the single-agent implementation answers supported FAQs without orchestration overhead; the record is retained under Redfern Aviation's rollout (SF-M02-01). The underlying reason is that Multiple agents should be chosen for a business or control need, not novelty. In this spare-part quotations scenario, this separates supported agent behavior from assumptions about the AI model.

Incorrect Answers

A:

The action “Define approved handoff inputs and evidence needed by the recipient agent; implement it within the documented Salesforce configuration” addresses a separate source case: A service agent delegates a case to a specialized billing agent without the required case identifier. The correction must ensure that customer order details stay within each authorized account. Its underlying reason is: Multi-agent coordination depends on explicit context and controlled responsibility transfer. This question instead describes a basic FAQ workflow has one data source and no specialized actions yet architects propose six coordinating agents. The correction must ensure that supplier prices are never shown outside entitled teams. The original answer “Keep a single appropriately scoped agent when multi-agent orchestration adds no control or scale benefit; implement it before the next environment promotion” targets that failure because multiple agents should be chosen for a business or control need, not novelty.

C:

The action “Use separate specialized agents with controlled task delegation when the isolation benefit justifies complexity; implement it with least-privilege execution” addresses a separate source case: A support and finance workflow has distinct permissions and responsibilities that one broad agent cannot govern safely. The correction must ensure that student records never cross program authorization boundaries. Its underlying reason is: Multi-agent design can separate responsibilities but increases orchestration complexity. This question instead describes a basic FAQ workflow has one data source and no specialized actions yet architects propose six coordinating agents. The correction must ensure that supplier prices are never shown outside entitled teams. The original answer “Keep a single appropriately scoped agent when multi-agent orchestration adds no control or scale benefit; implement it before the next environment promotion” targets that failure because multiple agents should be chosen for a business or control need, not novelty.

D:

The action “Require authenticated agent identities and enforce recipient-side authorization for delegated tasks; implement it with a controlled rollback path” addresses a separate source case: A specialist agent trusts a delegated instruction to reveal private data outside its permitted audience. The correction must ensure that citizen information stays limited to the relevant case. Its underlying reason is: Cross-agent messages are requests, not blanket grants of authority. This question instead describes a basic FAQ workflow has one data source and no specialized actions yet architects propose six coordinating agents. The correction must ensure that supplier prices are never shown outside entitled teams. The original answer “Keep a single appropriately scoped agent when multi-agent orchestration adds no control or scale benefit; implement it before the next environment promotion” targets that failure because multiple agents should be chosen for a business or control need, not novelty.

Question 769

At Juniper Civic, a public agency service counter is improving permit status following a quarterly access review (SF-A20-02). The administrator observes that internal employees expect the company agent in Slack but the connector exposes an unrelated public service agent. Any fix must ensure that citizen information stays limited to the relevant case. Which continuing control best prevents this issue from recurring?

  1. Retest identity and session mapping on each channel; review it and confirm the control remains effective after release.
  2. Test interruptions, escalation and transcription errors; review it with a documented exception process.
  3. Test session expiration and cross-user session isolation; review it before expanding channel availability.
  4. Test cross-workspace access and installation governance; review it before expanding channel availability.

Explanation

Correct Answer

D:

The preventive control directly addresses repeat failures: Test cross-workspace access and installation governance; require the check in the next release review at Juniper Civic (SF-A20-02). It complements the corrective action, configure the approved internal agent channel and enforce user identity and workspace scope, and protects the explicit condition that citizen information stays limited to the relevant case.

Incorrect Answers

A:

This safeguard, “Retest identity and session mapping on each channel; review it and confirm the control remains effective after release”, reduces a different source-defined risk: A service agent is configured but customers cannot reach it from the approved support site. The correction must ensure that financial identifiers are masked outside authorized roles. That risk depends on: An agent definition does not automatically establish its channel delivery. The recurring problem here is internal employees expect the company agent in Slack but the connector exposes an unrelated public service agent. The correction must ensure that citizen information stays limited to the relevant case. The originally selected control “Test cross-workspace access and installation governance; review it before expanding channel availability” is more specific because channel connections must preserve the intended audience and authorization context.

B:

This safeguard, “Test interruptions, escalation and transcription errors; review it with a documented exception process”, reduces a different source-defined risk: A spoken customer request needs a human handoff but the voice implementation has only text fallback. The correction must ensure that shipment changes remain attributable and reversible. That risk depends on: Voice channel delivery has modality and escalation requirements beyond text-only configuration. The recurring problem here is internal employees expect the company agent in Slack but the connector exposes an unrelated public service agent. The correction must ensure that citizen information stays limited to the relevant case. The originally selected control “Test cross-workspace access and installation governance; review it before expanding channel availability” is more specific because channel connections must preserve the intended audience and authorization context.

C:

This safeguard, “Test session expiration and cross-user session isolation; review it before expanding channel availability”, reduces a different source-defined risk: An integration sends each message as a new agent session and loses follow-up context. The correction must ensure that service changes follow approved warranty conditions. That risk depends on: Programmatic agents rely on explicit session management rather than browser state. The recurring problem here is internal employees expect the company agent in Slack but the connector exposes an unrelated public service agent. The correction must ensure that citizen information stays limited to the relevant case. The originally selected control “Test cross-workspace access and installation governance; review it before expanding channel availability” is more specific because channel connections must preserve the intended audience and authorization context.

Question 770

At Trillium Services, an internal HR help desk is improving employee leave guidance after a knowledge-policy revision (SF-D02-01). The administrator observes that a revised employee handbook was uploaded but an agent still cites the prior edition. Any fix must ensure that employee case files are accessible only to the case owner. Which continuing control best prevents this issue from recurring?

  1. Run cross-tenant retrieval-denial checks after source changes; review it and confirm the control remains effective after release.
  2. Monitor ingestion failures and index availability; review it and retest after dependent metadata changes.
  3. Monitor data-sync and indexing completion after each publication; review it before expanding channel availability.
  4. Evaluate chunk boundaries on headings, procedures, and exceptions; review it with audit evidence from regression testing.

Explanation

Correct Answer

C:

The preventive control directly addresses repeat failures: Monitor data-sync and indexing completion after each publication; require the check in the next release review at Trillium Services (SF-D02-01). It complements the corrective action, refresh the library ingestion and search assets then retest retrieval against the revised passage, and protects the explicit condition that employee case files are accessible only to the case owner.

Incorrect Answers

A:

This safeguard, “Run cross-tenant retrieval-denial checks after source changes; review it and confirm the control remains effective after release”, reduces a different source-defined risk: Two subsidiaries share a platform but must not retrieve each other's knowledge documents. The correction must ensure that member records cannot be exposed to other members. That risk depends on: Knowledge availability requires both indexing and audience-aware scope controls. The recurring problem here is a revised employee handbook was uploaded but an agent still cites the prior edition. The correction must ensure that employee case files are accessible only to the case owner. The originally selected control “Monitor data-sync and indexing completion after each publication; review it before expanding channel availability” is more specific because a library answer depends on the freshness of its ingested and indexed content.

B:

This safeguard, “Monitor ingestion failures and index availability; review it and retest after dependent metadata changes”, reduces a different source-defined risk: 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. That risk depends on: Data-library setup is a pipeline with dependent indexing and retrieval stages. The recurring problem here is a revised employee handbook was uploaded but an agent still cites the prior edition. The correction must ensure that employee case files are accessible only to the case owner. The originally selected control “Monitor data-sync and indexing completion after each publication; review it before expanding channel availability” is more specific because a library answer depends on the freshness of its ingested and indexed content.

D:

This safeguard, “Evaluate chunk boundaries on headings, procedures, and exceptions; review it with audit evidence from regression testing”, reduces a different source-defined risk: 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. That risk depends on: Chunking trades passage granularity against preservation of useful context. The recurring problem here is a revised employee handbook was uploaded but an agent still cites the prior edition. The correction must ensure that employee case files are accessible only to the case owner. The originally selected control “Monitor data-sync and indexing completion after each publication; review it before expanding channel availability” is more specific because a library answer depends on the freshness of its ingested and indexed content.