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 7

Question 60

At Beacon Medical, an internal clinic IT service desk is improving employee IT triage during an agent routing evaluation (SF-P21-01). The administrator observes that a manager assumes Trust Layer usage automatically grants agents unrestricted access to customer records. Any fix must ensure that employee identity is verified before accessing private tickets. Which action best addresses the issue while preserving the stated requirement?

  1. Use the supported Salesforce Trust Layer protections and enforce source access rules; implement it before the next environment promotion.
  2. Treat retrieved text as data, enforce higher-priority agent instructions and permission controls; implement it within the documented Salesforce configuration.
  3. Configure access within the established Salesforce permission model and use approved grounding sources; implement it with least-privilege execution.
  4. Configure the supported model-access restrictions for the relevant AI features; implement it with traceable change approval.

Explanation

Correct Answer

C:

The documented failure is that a manager assumes Trust Layer usage automatically grants agents unrestricted access to customer records. Configure access within the established Salesforce permission model and use approved grounding sources for Beacon Medical's employee IT triage workflow (SF-P21-01) while respecting that employee identity is verified before accessing private tickets. Its outcome is not established merely by changing instructions: In a controlled Case acceptance test, a least-privilege agent cannot ground on records outside its permission scope; the record is retained under Beacon Medical's rollout (SF-P21-01). The underlying reason is that Trust safeguards complement rather than supersede object and field authorization. In this employee IT triage scenario, this separates supported agent behavior from assumptions about the AI model.

Incorrect Answers

A:

The action “Use the supported Salesforce Trust Layer protections and enforce source access rules; implement it before the next environment promotion” addresses a separate source case: A case-summary prompt may contain personal contact information that must not be exposed beyond authorization. The correction must ensure that student records never cross program authorization boundaries. Its underlying reason is: The Trust Layer supplies security and privacy safeguards but cannot replace data permissions. This question instead describes a manager assumes Trust Layer usage automatically grants agents unrestricted access to customer records. The correction must ensure that employee identity is verified before accessing private tickets. The original answer “Configure access within the established Salesforce permission model and use approved grounding sources; implement it with least-privilege execution” targets that failure because trust safeguards complement rather than supersede object and field authorization.

B:

The action “Treat retrieved text as data, enforce higher-priority agent instructions and permission controls; implement it within the documented Salesforce configuration” addresses a separate source case: A retrieved knowledge article includes instructions telling the assistant to ignore the company policy. The correction must ensure that work order updates follow supported automation guardrails. Its underlying reason is: External content must not become trusted operational instruction merely because it is retrieved. This question instead describes a manager assumes Trust Layer usage automatically grants agents unrestricted access to customer records. The correction must ensure that employee identity is verified before accessing private tickets. The original answer “Configure access within the established Salesforce permission model and use approved grounding sources; implement it with least-privilege execution” targets that failure because trust safeguards complement rather than supersede object and field authorization.

D:

The action “Configure the supported model-access restrictions for the relevant AI features; implement it with traceable change approval” addresses a separate source case: Policy prohibits use of an unapproved model in production prompt generation. The correction must ensure that production changes remain gated by approval. Its underlying reason is: Model governance must explicitly constrain the available model choices. This question instead describes a manager assumes Trust Layer usage automatically grants agents unrestricted access to customer records. The correction must ensure that employee identity is verified before accessing private tickets. The original answer “Configure access within the established Salesforce permission model and use approved grounding sources; implement it with least-privilege execution” targets that failure because trust safeguards complement rather than supersede object and field authorization.

Question 61

At Beacon Medical, an internal clinic IT service desk is improving employee IT triage during a least-privilege verification (SF-D06-01). The administrator observes that a help team needs answers from internal installation manuals rather than customer account fields. Any fix must ensure that employee identity is verified before accessing private tickets. Which action best addresses the issue while preserving the stated requirement?

  1. Configure supported citations or retrieval traceability for the knowledge-backed answer path; implement it with least-privilege execution.
  2. Create an authorized Agentforce Data Library backed by the approved policy documents; implement it and keep the business rule enforceable.
  3. Configure supported retriever filters for jurisdiction and effective policy data; implement it with a controlled rollback path.
  4. Ingest the approved manuals into an Agentforce Data Library and connect the correct retriever; implement it with a controlled rollback path.

Explanation

Correct Answer

D:

The documented failure is that a help team needs answers from internal installation manuals rather than customer account fields. Ingest the approved manuals into an Agentforce Data Library and connect the correct retriever for Beacon Medical's employee IT triage workflow (SF-D06-01) while respecting that employee identity is verified before accessing private tickets. Its outcome is not established merely by changing instructions: In a controlled Case acceptance test, a test installation question uses a relevant manual chunk and not an unrelated account field; the record is retained under Beacon Medical's rollout (SF-D06-01). The underlying reason is that Unstructured document knowledge and CRM record grounding serve different source needs. In this employee IT triage scenario, this separates supported agent behavior from assumptions about the AI model.

Incorrect Answers

A:

The action “Configure supported citations or retrieval traceability for the knowledge-backed answer path; implement it with least-privilege execution” addresses a separate source case: Agent replies about service terms are plausible but reviewers cannot find where they came from. The correction must ensure that policy terms come from the current approved revision. Its underlying reason is: Source attribution enables reviewers to challenge grounded answers. This question instead describes a help team needs answers from internal installation manuals rather than customer account fields. The correction must ensure that employee identity is verified before accessing private tickets. The original answer “Ingest the approved manuals into an Agentforce Data Library and connect the correct retriever; implement it with a controlled rollback path” targets that failure because unstructured document knowledge and CRM record grounding serve different source needs.

B:

The action “Create an authorized Agentforce Data Library backed by the approved policy documents; implement it and keep the business rule enforceable” addresses a separate source case: Support agents answer policy questions from PDFs but there is no managed knowledge grounding resource. The correction must ensure that student records never cross program authorization boundaries. Its underlying reason is: Data Libraries connect managed knowledge sources to grounding tools and retrieval. This question instead describes a help team needs answers from internal installation manuals rather than customer account fields. The correction must ensure that employee identity is verified before accessing private tickets. The original answer “Ingest the approved manuals into an Agentforce Data Library and connect the correct retriever; implement it with a controlled rollback path” targets that failure because unstructured document knowledge and CRM record grounding serve different source needs.

C:

The action “Configure supported retriever filters for jurisdiction and effective policy data; implement it with a controlled rollback path” addresses a separate source case: A policy retriever mixes country-specific employment procedures in the same response. The correction must ensure that sensitive product claims must cite approved knowledge. Its underlying reason is: Retrieval filters narrow candidate passages before generation uses them. This question instead describes a help team needs answers from internal installation manuals rather than customer account fields. The correction must ensure that employee identity is verified before accessing private tickets. The original answer “Ingest the approved manuals into an Agentforce Data Library and connect the correct retriever; implement it with a controlled rollback path” targets that failure because unstructured document knowledge and CRM record grounding serve different source needs.

Question 62

At Redfern Aviation, a supplier operations group is improving spare-part quotations during an agent routing evaluation (SF-D09-03). The administrator observes that a twenty-page support guide is indexed as one oversized passage and retrieval is imprecise. Any fix must ensure that supplier prices are never shown outside entitled teams. Which underlying Agentforce or Salesforce design principle explains the appropriate approach?

  1. Retrieval window and chunk boundaries together affect grounding completeness; interpret this as distinct from unrelated UI configuration.
  2. Chunking trades passage granularity against preservation of useful context; interpret this with boundaries enforced by supported platform controls.
  3. Search indexes organize content; retrievers select relevant indexed content for a use case; interpret this while preserving the specified source of truth.
  4. Source attribution enables reviewers to challenge grounded answers; interpret this as distinct from unrelated UI configuration.

Explanation

Correct Answer

B:

The governing distinction is: Chunking trades passage granularity against preservation of useful context. In this spare-part quotations scenario, this separates supported agent behavior from assumptions about the AI model. Because a twenty-page support guide is indexed as one oversized passage and retrieval is imprecise, the intended response is to use a coherent chunking strategy to index smaller meaningful guide sections. An observable check is that a specific fault query retrieves the relevant troubleshooting section rather than the entire guide.

Incorrect Answers

A:

The idea “Retrieval window and chunk boundaries together affect grounding completeness; interpret this as distinct from unrelated UI configuration” explains another source-defined situation: 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. That situation depends on: Retrieval window and chunk boundaries together affect grounding completeness. The present question instead concerns a twenty-page support guide is indexed as one oversized passage and retrieval is imprecise. The correction must ensure that supplier prices are never shown outside entitled teams. Its directly relevant mechanism is: Chunking trades passage granularity against preservation of useful context.

C:

The idea “Search indexes organize content; retrievers select relevant indexed content for a use case; interpret this while preserving the specified source of truth” explains another source-defined situation: 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 situation depends on: Search indexes organize content; retrievers select relevant indexed content for a use case. The present question instead concerns a twenty-page support guide is indexed as one oversized passage and retrieval is imprecise. The correction must ensure that supplier prices are never shown outside entitled teams. Its directly relevant mechanism is: Chunking trades passage granularity against preservation of useful context.

D:

The idea “Source attribution enables reviewers to challenge grounded answers; interpret this as distinct from unrelated UI configuration” explains another source-defined situation: Agent replies about service terms are plausible but reviewers cannot find where they came from. The correction must ensure that policy terms come from the current approved revision. That situation depends on: Source attribution enables reviewers to challenge grounded answers. The present question instead concerns a twenty-page support guide is indexed as one oversized passage and retrieval is imprecise. The correction must ensure that supplier prices are never shown outside entitled teams. Its directly relevant mechanism is: Chunking trades passage granularity against preservation of useful context.

Question 63

At Harbor Logistics, a distribution operations team is improving shipment exception triage during a least-privilege verification (SF-A25-01). The administrator observes that customers need assistance with cases and troubleshooting through a public 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 employee can retrieve internal policy guidance while an external user cannot; confirm this using a representative sandbox fixture.
  2. The helper is accessible only to authorized employees through approved internal channels; confirm this and confirm the resulting trace.
  3. A customer session can obtain permitted case guidance and escalate appropriately; confirm this while testing the unauthorized case.
  4. A Slack user sees only authorized internal actions and records; confirm this with production-equivalent source conditions.

Explanation

Correct Answer

C:

This is the direct acceptance signal for the reported failure: In a controlled Shipment__c acceptance test, a customer session can obtain permitted case guidance and escalate appropriately; the record is retained under Harbor Logistics's rollout (SF-A25-01). The chosen correction was to choose a Service agent configured for the customer service channel and supported actions; the measurement therefore tests the relevant source, routing or authorization outcome rather than unrelated activity.

Incorrect Answers

A:

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, customers need assistance with cases and troubleshooting through a public support site. The correction must ensure that shipment changes remain attributable and reversible; the more direct acceptance evidence is “A customer session can obtain permitted case guidance and escalate appropriately; confirm this while testing the unauthorized case” because service agents target service interactions and channel-specific customer needs.

B:

The proposed observation “The helper is accessible only to authorized employees through approved internal channels; confirm this and confirm the resulting trace” would check a different original case: 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. Its mechanism is: Agent type selection should follow user audience and operational purpose. In the present case, customers need assistance with cases and troubleshooting through a public support site. The correction must ensure that shipment changes remain attributable and reversible; the more direct acceptance evidence is “A customer session can obtain permitted case guidance and escalate appropriately; confirm this while testing the unauthorized case” because service agents target service interactions and channel-specific customer needs.

D:

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, customers need assistance with cases and troubleshooting through a public support site. The correction must ensure that shipment changes remain attributable and reversible; the more direct acceptance evidence is “A customer session can obtain permitted case guidance and escalate appropriately; confirm this while testing the unauthorized case” because service agents target service interactions and channel-specific customer needs.

Question 64

At Bluehaven University, an internal student services team is improving student advising following a quarterly access review (SF-P01-01). The administrator observes that a support team copies case comments into a consumer chatbot to create CRM case summaries. Any fix must ensure that student records never cross program authorization boundaries. Which underlying Agentforce or Salesforce design principle explains the appropriate approach?

  1. Prompt Builder creates reusable Salesforce-grounded prompt templates instead of unmanaged external text entry; interpret this as distinct from unrelated UI configuration.
  2. Prompt Builder generates contextual text and should not replace deterministic business-rule execution; interpret this without inferring extra permissions from an LLM response.
  3. A reusable prompt template standardizes instructions and connects them to trusted contextual data; interpret this while preserving the specified source of truth.
  4. Clear role, context, constraints, and output format improve prompt consistency; interpret this with boundaries enforced by supported platform controls.

Explanation

Correct Answer

A:

The governing distinction is: Prompt Builder creates reusable Salesforce-grounded prompt templates instead of unmanaged external text entry. In this student advising scenario, this separates supported agent behavior from assumptions about the AI model. Because a support team copies case comments into a consumer chatbot to create CRM case summaries, the intended response is to use Prompt Builder with a record-grounded field generation template for the approved case summary field. An observable check is that an authorized agent invokes the record-field prompt and the summary references the intended case only.

Incorrect Answers

B:

The idea “Prompt Builder generates contextual text and should not replace deterministic business-rule execution; interpret this without inferring extra permissions from an LLM response” explains another source-defined situation: A nightly data cleanup requirement is being treated as a request for open-ended generated prose. The correction must ensure that customer order details stay within each authorized account. That situation depends on: Prompt Builder generates contextual text and should not replace deterministic business-rule execution. The present question instead concerns a support team copies case comments into a consumer chatbot to create CRM case summaries. The correction must ensure that student records never cross program authorization boundaries. Its directly relevant mechanism is: Prompt Builder creates reusable Salesforce-grounded prompt templates instead of unmanaged external text entry.

C:

The idea “A reusable prompt template standardizes instructions and connects them to trusted contextual data; interpret this while preserving the specified source of truth” explains another source-defined situation: Regional teams handwrite inconsistent product descriptions despite having approved CRM product facts. The correction must ensure that supplier prices are never shown outside entitled teams. That situation depends on: A reusable prompt template standardizes instructions and connects them to trusted contextual data. The present question instead concerns a support team copies case comments into a consumer chatbot to create CRM case summaries. The correction must ensure that student records never cross program authorization boundaries. Its directly relevant mechanism is: Prompt Builder creates reusable Salesforce-grounded prompt templates instead of unmanaged external text entry.

D:

The idea “Clear role, context, constraints, and output format improve prompt consistency; interpret this with boundaries enforced by supported platform controls” explains another source-defined situation: A field generation prompt produces variable-length paragraphs where downstream users require a brief summary. The correction must ensure that member records cannot be exposed to other members. That situation depends on: Clear role, context, constraints, and output format improve prompt consistency. The present question instead concerns a support team copies case comments into a consumer chatbot to create CRM case summaries. The correction must ensure that student records never cross program authorization boundaries. Its directly relevant mechanism is: Prompt Builder creates reusable Salesforce-grounded prompt templates instead of unmanaged external text entry.

Question 65

At Summit Pharma, a regulated information center is improving product information following a quarterly access review (SF-G01-04). The administrator observes that operators receive complaint tickets but cannot correlate them to failing agent sessions. Any fix must ensure that sensitive product claims must cite approved knowledge. Which underlying Agentforce or Salesforce design principle explains the appropriate approach?

  1. Monitoring dashboards depend on instrumentation and data ingestion; interpret this independent of the surface wording of the conversation.
  2. Observability provides evidence of actual runtime behavior rather than anecdotes; interpret this as distinct from unrelated UI configuration.
  3. Session volume alone does not indicate successful business outcomes; interpret this while preserving the specified source of truth.
  4. Agent quality changes can arise from retrieval behavior as well as prompt text; interpret this rather than assuming a generative instruction is an access rule.

Explanation

Correct Answer

B:

The governing distinction is: Observability provides evidence of actual runtime behavior rather than anecdotes. In this product information scenario, this separates supported agent behavior from assumptions about the AI model. Because operators receive complaint tickets but cannot correlate them to failing agent sessions, the intended response is to enable supported session tracing and review agent interaction diagnostics. An observable check is that a failed session is traceable from utterance through selected actions and returned response.

Incorrect Answers

A:

The idea “Monitoring dashboards depend on instrumentation and data ingestion; interpret this independent of the surface wording of the conversation” explains another source-defined situation: An analytics dashboard shows empty agent session charts after rollout. The correction must ensure that member records cannot be exposed to other members. That situation depends on: Monitoring dashboards depend on instrumentation and data ingestion. The present question instead concerns operators receive complaint tickets but cannot correlate them to failing agent sessions. The correction must ensure that sensitive product claims must cite approved knowledge. Its directly relevant mechanism is: Observability provides evidence of actual runtime behavior rather than anecdotes.

C:

The idea “Session volume alone does not indicate successful business outcomes; interpret this while preserving the specified source of truth” explains another source-defined situation: 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 situation depends on: Session volume alone does not indicate successful business outcomes. The present question instead concerns operators receive complaint tickets but cannot correlate them to failing agent sessions. The correction must ensure that sensitive product claims must cite approved knowledge. Its directly relevant mechanism is: Observability provides evidence of actual runtime behavior rather than anecdotes.

D:

The idea “Agent quality changes can arise from retrieval behavior as well as prompt text; interpret this rather than assuming a generative instruction is an access rule” explains another source-defined situation: 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 situation depends on: Agent quality changes can arise from retrieval behavior as well as prompt text. The present question instead concerns operators receive complaint tickets but cannot correlate them to failing agent sessions. The correction must ensure that sensitive product claims must cite approved knowledge. Its directly relevant mechanism is: Observability provides evidence of actual runtime behavior rather than anecdotes.

Question 66

At Greenwell Energy, a field technician assistance team is improving asset inspection before a seasonal service launch (SF-A08-02). The administrator observes that a conversational path exits the correct subagent without completing the expected action. Any fix must ensure that plant access boundaries are not weakened by chatbot replies. Which observable result would best demonstrate that the correction actually worked?

  1. Ineligible cases never trigger the refund action while responses remain understandable; confirm this and retain a reproducible test record.
  2. Traces show the condition evaluated before any authorized action; confirm this while testing the unauthorized case.
  3. A rerun follows the intended subagent and calls the action exactly once; confirm this using a least-privilege test identity.
  4. The supported standard action retrieves the requested case status within authorization scope; confirm this using a least-privilege test identity.

Explanation

Correct Answer

C:

This is the direct acceptance signal for the reported failure: In a controlled Asset acceptance test, a rerun follows the intended subagent and calls the action exactly once; the record is retained under Greenwell Energy's rollout (SF-A08-02). The chosen correction was to inspect Agent Script transitions and the trace preview to locate the wrong route; the measurement therefore tests the relevant source, routing or authorization outcome rather than unrelated activity.

Incorrect Answers

A:

The proposed observation “Ineligible cases never trigger the refund action while responses remain understandable; confirm this and retain a reproducible test record” would check a different original case: The agent must enforce a refund eligibility rule but still explain decisions conversationally. The correction must ensure that donor details cannot be revealed across accounts. Its mechanism is: Hybrid reasoning combines fixed business logic with flexible language generation. In the present case, a conversational path exits the correct subagent without completing the expected action. The correction must ensure that plant access boundaries are not weakened by chatbot replies; the more direct acceptance evidence is “A rerun follows the intended subagent and calls the action exactly once; confirm this using a least-privilege test identity” because trace evidence is needed to distinguish routing errors from language-generation errors.

B:

The proposed observation “Traces show the condition evaluated before any authorized action; confirm this while testing the unauthorized case” would check a different original case: An LLM decides whether an approval rule applies after the protected action has already executed. The correction must ensure that part inventory decisions use approved current records. Its mechanism is: In hybrid reasoning the script can evaluate conditions and actions before LLM response generation. In the present case, a conversational path exits the correct subagent without completing the expected action. The correction must ensure that plant access boundaries are not weakened by chatbot replies; the more direct acceptance evidence is “A rerun follows the intended subagent and calls the action exactly once; confirm this using a least-privilege test identity” because trace evidence is needed to distinguish routing errors from language-generation errors.

D:

The proposed observation “The supported standard action retrieves the requested case status within authorization scope; confirm this using a least-privilege test identity” would check a different original case: 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. Its mechanism is: Standard agent topics can be reused when they already fit the task. In the present case, a conversational path exits the correct subagent without completing the expected action. The correction must ensure that plant access boundaries are not weakened by chatbot replies; the more direct acceptance evidence is “A rerun follows the intended subagent and calls the action exactly once; confirm this using a least-privilege test identity” because trace evidence is needed to distinguish routing errors from language-generation errors.

Question 67

At Alpine Hospitality, a concierge service organization is improving guest escalation during a controlled sandbox pilot (SF-A30-03). The administrator observes that an integration sends each message as a new agent session and loses follow-up context. Any fix must ensure that escalations preserve only the needed guest context. Which observable result would best demonstrate that the correction actually worked?

  1. A second turn refers to the prior conversation context and supported action outcome; confirm this and confirm the resulting trace.
  2. A client token cannot retrieve unrelated tenant context or perform forbidden actions; confirm this using a representative sandbox fixture.
  3. A follow-up request correctly uses the intended session while a new session remains isolated; confirm this and compare with approved baseline behavior.
  4. The same transition appears consistently in both visual and script representations; confirm this with production-equivalent source conditions.

Explanation

Correct Answer

C:

This is the direct acceptance signal for the reported failure: In a controlled Case acceptance test, a follow-up request correctly uses the intended session while a new session remains isolated; the record is retained under Alpine Hospitality's rollout (SF-A30-03). The chosen correction was to manage session identifiers and lifecycle according to the Agent API contract; the measurement therefore tests the relevant source, routing or authorization outcome rather than unrelated activity.

Incorrect Answers

A:

The proposed observation “A second turn refers to the prior conversation context and supported action outcome; confirm this and confirm the resulting trace” would check a different original case: An external partner requires conversational follow-ups but the design offers only a one-shot Flow endpoint. The correction must ensure that escalations preserve only the needed guest context. Its mechanism is: Agent API supports conversation patterns that differ from single transaction automation endpoints. In the present case, an integration sends each message as a new agent session and loses follow-up context. The correction must ensure that escalations preserve only the needed guest context; the more direct acceptance evidence is “A follow-up request correctly uses the intended session while a new session remains isolated; confirm this and compare with approved baseline behavior” because programmatic agents rely on explicit session management rather than browser state.

B:

The proposed observation “A client token cannot retrieve unrelated tenant context or perform forbidden actions; confirm this using a representative sandbox fixture” would check a different original case: 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. Its mechanism is: API connectivity does not override CRM or agent execution authorization. In the present case, an integration sends each message as a new agent session and loses follow-up context. The correction must ensure that escalations preserve only the needed guest context; the more direct acceptance evidence is “A follow-up request correctly uses the intended session while a new session remains isolated; confirm this and compare with approved baseline behavior” because programmatic agents rely on explicit session management rather than browser state.

D:

The proposed observation “The same transition appears consistently in both visual and script representations; confirm this with production-equivalent source conditions” would check a different original case: Developers fear that visual routing changes and Agent Script edits produce separate incompatible agents. The correction must ensure that patient notes are visible only to approved clinical roles. Its mechanism is: Canvas and Script are two editing views over the same Agent Script definition. In the present case, an integration sends each message as a new agent session and loses follow-up context. The correction must ensure that escalations preserve only the needed guest context; the more direct acceptance evidence is “A follow-up request correctly uses the intended session while a new session remains isolated; confirm this and compare with approved baseline behavior” because programmatic agents rely on explicit session management rather than browser state.

Question 68

At Greenwell Energy, a field technician assistance team is improving asset inspection before expanding the internal rollout (SF-A21-01). The administrator observes that a service agent action runs with a privileged user context that grants excessive record visibility. Any fix must ensure that plant access boundaries are not weakened by chatbot replies. Which observable result would best demonstrate that the correction actually worked?

  1. A user without field access cannot obtain the protected value through the agent; confirm this using a least-privilege test identity.
  2. A high-severity case remains open until required approval is recorded; confirm this and compare with approved baseline behavior.
  3. A cross-account record access test fails under the agent's runtime security context; 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 Asset acceptance test, a cross-account record access test fails under the agent's runtime security context; the record is retained under Greenwell Energy's rollout (SF-A21-01). 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 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 plant access boundaries are not weakened by chatbot replies; the more direct acceptance evidence is “A cross-account record access test fails under the agent's runtime security context; confirm this using a representative sandbox fixture” because the user identity executing an action determines which permissions can apply.

B:

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 plant access boundaries are not weakened by chatbot replies; the more direct acceptance evidence is “A cross-account record access test fails under the agent's runtime security context; confirm this using a representative sandbox fixture” because the user identity executing an action determines which permissions can apply.

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, 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; the more direct acceptance evidence is “A cross-account record access test fails under the agent's runtime security context; confirm this using a representative sandbox fixture” because the user identity executing an action determines which permissions can apply.

Question 69

At Trillium Services, an internal HR help desk is improving employee leave guidance after a customer-reported regression (SF-A13-02). The administrator observes that a customer asks for a common supported case status operation already provided by a standard Agentforce topic. Any fix must ensure that employee case files are accessible only to the case owner. Which observable result would best demonstrate that the correction actually worked?

  1. Warranty questions enter the custom topic while unrelated shipping questions do not; confirm this and compare with approved baseline behavior.
  2. The supported standard action retrieves the requested case status within authorization scope; confirm this with production-equivalent source conditions.
  3. An over-limit request is denied before any payment record is changed; confirm this and retain a reproducible test record.
  4. The first session turn correctly sees a false flag and later turns see the updated value; confirm this and confirm the resulting trace.

Explanation

Correct Answer

B:

This is the direct acceptance signal for the reported failure: In a controlled Employee_Case__c acceptance test, the supported standard action retrieves the requested case status within authorization scope; the record is retained under Trillium Services's rollout (SF-A13-02). The chosen correction was to configure the applicable standard topic and action instead of duplicating a custom implementation; the measurement therefore tests the relevant source, routing or authorization outcome rather than unrelated activity.

Incorrect Answers

A:

The proposed observation “Warranty questions enter the custom topic while unrelated shipping questions do not; confirm this and compare with approved baseline behavior” would check a different original case: A service agent handles warranty inspection but its broad existing topic attracts unrelated requests. The correction must ensure that employee case files are accessible only to the case owner. Its mechanism is: Topic descriptions and instructions guide appropriate task selection. In the present case, a customer asks for a common supported case status operation already provided by a standard Agentforce topic. The correction must ensure that employee case files are accessible only to the case owner; the more direct acceptance evidence is “The supported standard action retrieves the requested case status within authorization scope; confirm this with production-equivalent source conditions” because standard agent topics can be reused when they already fit the task.

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, a customer asks for a common supported case status operation already provided by a standard Agentforce topic. The correction must ensure that employee case files are accessible only to the case owner; the more direct acceptance evidence is “The supported standard action retrieves the requested case status within authorization scope; confirm this with production-equivalent source conditions” because standard agent topics can be reused when they already fit the task.

D:

The proposed observation “The first session turn correctly sees a false flag and later turns see the updated value; confirm this and confirm the resulting trace” would check a different original case: An agent checks whether a compensation was issued but its mutable flag has no reliable initial state. The correction must ensure that sensitive product claims must cite approved knowledge. Its mechanism is: Mutable Agent Script variables hold state that deterministic conditions can use. In the present case, a customer asks for a common supported case status operation already provided by a standard Agentforce topic. The correction must ensure that employee case files are accessible only to the case owner; the more direct acceptance evidence is “The supported standard action retrieves the requested case status within authorization scope; confirm this with production-equivalent source conditions” because standard agent topics can be reused when they already fit the task.

Question 70

At Aster Retail, a storefront service desk is improving order-support before expanding the internal rollout (SF-P20-02). The administrator observes that a retrieved knowledge article includes instructions telling the assistant to ignore the company policy. Any fix must ensure that customer order details stay within each authorized account. Which underlying Agentforce or Salesforce design principle explains the appropriate approach?

  1. The Trust Layer supplies security and privacy safeguards but cannot replace data permissions; interpret this while preserving the specified source of truth.
  2. External content must not become trusted operational instruction merely because it is retrieved; interpret this with boundaries enforced by supported platform controls.
  3. Trust safeguards complement rather than supersede object and field authorization; interpret this as distinct from unrelated UI configuration.
  4. Prompt Builder generates contextual text and should not replace deterministic business-rule execution; interpret this without inferring extra permissions from an LLM response.

Explanation

Correct Answer

B:

The governing distinction is: External content must not become trusted operational instruction merely because it is retrieved. In this order-support scenario, this separates supported agent behavior from assumptions about the AI model. Because a retrieved knowledge article includes instructions telling the assistant to ignore the company policy, the intended response is to treat retrieved text as data, enforce higher-priority agent instructions and permission controls. An observable check is that a malicious-article test does not trigger unauthorized actions or policy overrides.

Incorrect Answers

A:

The idea “The Trust Layer supplies security and privacy safeguards but cannot replace data permissions; interpret this while preserving the specified source of truth” explains another source-defined situation: A case-summary prompt may contain personal contact information that must not be exposed beyond authorization. The correction must ensure that student records never cross program authorization boundaries. That situation depends on: The Trust Layer supplies security and privacy safeguards but cannot replace data permissions. The present question instead concerns a retrieved knowledge article includes instructions telling the assistant to ignore the company policy. The correction must ensure that customer order details stay within each authorized account. Its directly relevant mechanism is: External content must not become trusted operational instruction merely because it is retrieved.

C:

The idea “Trust safeguards complement rather than supersede object and field authorization; interpret this as distinct from unrelated UI configuration” explains another source-defined situation: A manager assumes Trust Layer usage automatically grants agents unrestricted access to customer records. The correction must ensure that employee identity is verified before accessing private tickets. That situation depends on: Trust safeguards complement rather than supersede object and field authorization. The present question instead concerns a retrieved knowledge article includes instructions telling the assistant to ignore the company policy. The correction must ensure that customer order details stay within each authorized account. Its directly relevant mechanism is: External content must not become trusted operational instruction merely because it is retrieved.

D:

The idea “Prompt Builder generates contextual text and should not replace deterministic business-rule execution; interpret this without inferring extra permissions from an LLM response” explains another source-defined situation: A nightly data cleanup requirement is being treated as a request for open-ended generated prose. The correction must ensure that customer order details stay within each authorized account. That situation depends on: Prompt Builder generates contextual text and should not replace deterministic business-rule execution. The present question instead concerns a retrieved knowledge article includes instructions telling the assistant to ignore the company policy. The correction must ensure that customer order details stay within each authorized account. Its directly relevant mechanism is: External content must not become trusted operational instruction merely because it is retrieved.