Home / artificial-intelligence-machine-learning / Salesforce Certified Agentforce Specialist (AI-201) / Cheat Sheet
Salesforce Certified Agentforce Specialist (AI-201)

AI-201 Cheat Sheet

AI-201 Tests Which Agent Layer to Change — Not Louder Prompt Instructions

For builders who configure agents, prompt templates and grounding in Salesforce. When an agent misbehaves, the exam wants the right layer fixed: topic description, filter, scripted step, retriever or permissions, rather than more wording.

Check Your Readiness →
Among the harder certs
Avg: Not published by Salesforce
Pass: 750 / 1000
Most candidates understand Salesforce Certified Agentforce Specialist (AI-201) concepts — and still fail. This exam tests how you apply knowledge under pressure.

AI-201 Domain Map (Spring '26 guide)

Most items describe an agent or template producing the wrong result and ask what to change. Weights come from secondary reproductions of the Spring '26 guide; one source puts Governance at 5%. The older five-section Summer '25 outline with Development Lifecycle at 20% is superseded.

  1. 01
    AI Agents (35%) — Atlas reasoning, topics, actions, Agent Script, variables and filters, agent user, channels, Agent API
  2. 02
    Prompt Engineering (20%) — Prompt Builder template types, grounding, prompt flows, permission sets, activation, Trust Layer
  3. 03
    Data 360 Fundamentals (20%) — Agentforce Data Library, chunking, keyword vs vector vs hybrid search, retrievers
  4. 04
    Testing, Deployment, and Maintenance (10%) — Testing Center, test cases, agent metadata dependencies, data kits
  5. 05
    Governance and Observability (10%) — Command Center, session tracing, agent analytics, optimization insights
  6. 06
    Multi-Agent Orchestration (5%) — SOMA vs MOMA, orchestrator and specialist agents, MCP vs A2A

Wrong instinct vs correct approach

An agent is activated but customers cannot find it on the company website
✕ Wrong instinct

Activate it again or use the Agent API

✓ Correct approach

Website deployment needs a Messaging for In-App and Web channel, an Omni-Channel flow routing to the agent and an embedded deployment. The Agent API is for custom apps with no standard channel.

A support manager forwards one customer complaint about a bad agent answer and asks why it happened
✕ Wrong instinct

Open the Command Center dashboard

✓ Correct approach

Aggregates cannot explain one conversation. Session tracing shows the topic chosen, actions run, inputs, outputs and errors. The Trust Layer audit trail covers prompts, masking and toxicity, not action execution.

Users see the old wording after a team edits a prompt template and deploys it
✕ Wrong instinct

Clear the cache and wait for it to update

✓ Correct approach

Only the active version runs. Edits create a new version that must be activated, and after deployment you confirm activation in the target org; previewing against several records first verifies grounding.

Agentforce must use a partner's rate calculator and separately collaborate with a partner's autonomous planning agent
✕ Wrong instinct

Use A2A for both integrations

✓ Correct approach

The calculator is a tool, so expose it through MCP or a standard action under Agentforce's control. The partner agent owns its reasoning and multi-step planning, which is what Agent2Agent (A2A) is for.

An agent and its actions deploy to production but every action fails
✕ Wrong instinct

Redeploy the agent metadata alone

✓ Correct approach

Agent metadata depends on flows, Apex, prompt templates and permission sets deploying with it. The agent user is data, so create and permission it in production, and move Data 360 indexes and retrievers with data kits.

Know these cold

  • ▸ Prompt Template Manager builds and activates; Prompt Template User only runs templates
  • ▸ Ground with merge fields first, prompt flows for cross-object data, Apex only for complex logic
  • ▸ Keyword for IDs and codes, vector for paraphrases, hybrid as the default for mixed content
  • ▸ One index needs an individual retriever; answers across sources need an ensemble retriever
  • ▸ Agentforce Data Library auto-provisions data stream, index and retriever but limits chunking control
  • ▸ Atlas routes on topic classification descriptions; keep topics distinct jobs, not one per question
  • ▸ Employee agents run with the user's access; Service agents run as a dedicated agent user
  • ▸ Testing Center in a sandbox; response evaluation judges meaning, not exact phrasing
  • ▸ SOMA is Single-Org Multi-Agent; MOMA delegates across orgs; keep delegation chains shallow
  • ▸ Audit trail, observability and feedback data all depend on Data 360 storage

Can you answer these without checking your notes?

In this scenario: "An agent is activated but customers cannot find it on the company website" — what should you do first?
Website deployment needs a Messaging for In-App and Web channel, an Omni-Channel flow routing to the agent and an embedded deployment. The Agent API is for custom apps with no standard channel.
In this scenario: "A support manager forwards one customer complaint about a bad agent answer and asks why it happened" — what should you do first?
Aggregates cannot explain one conversation. Session tracing shows the topic chosen, actions run, inputs, outputs and errors. The Trust Layer audit trail covers prompts, masking and toxicity, not action execution.
In this scenario: "Users see the old wording after a team edits a prompt template and deploys it" — what should you do first?
Only the active version runs. Edits create a new version that must be activated, and after deployment you confirm activation in the target org; previewing against several records first verifies grounding.

Common Exam Mistakes — What candidates get wrong

Strengthening topic instructions to enforce a step that must never be skipped

Instructions are interpreted by the model and can be ignored. Rules that must always hold belong in filters on variables, which gate topics and actions, or in deterministic steps written in Agent Script for hybrid reasoning.

Switching to a larger model when the agent quotes the wrong document

If the retriever returns the wrong passages, any model answers from them. Fix retrieval: adjust chunk size, use hybrid search for SKUs and part numbers, add retriever filters on metadata, or refresh the search index.

Building a Flex template where a Field Generation template fits

Field Generation binds to one field on a Lightning record page with Dynamic Forms. Flex has custom inputs and no UI placement, so it is called from flows, Apex or agent actions. Sales Email and Record Summary are standard types too.

Confusing zero data retention with Trust Layer data masking

Zero data retention stops model providers storing or training on prompts. Data masking replaces sensitive values before the prompt leaves Salesforce and restores them in the response. A personal-data exposure requirement points to masking.

Giving the Service agent user the System Administrator profile

The agent user should get least-privilege permission sets covering only each action's objects and fields. Also review system context flows, which bypass the agent user's restrictions, before adding them as actions.

Resources to help you pass Salesforce Agentforce Specialist on your first attempt

AI-201 asks which agent layer to fix. See whether you pick topics, filters or retrievers correctly.