Agentforce Specialist Mock Exam: Key Concepts by Domain
Before you sit a timed Agentforce Specialist mock exam, you need to know what's actually being tested. Below is every domain from the official exam blueprint, broken down into the concrete concepts that show up again and again across our 144-question practice bank, so you can study with intent instead of rereading Trailhead modules at random.
Key concepts to know, domain by domain
Each domain below lists the concepts that come up most often in our practice question bank, the same questions you'll see in the timed mock exam.
AI Agents
Configure standard and custom topics and actions per agent type, understand the reasoning engine, manage Agentforce security and the agent user, and connect agents to channels.
1. Agent Setup & Types
Agentforce Agent User: Dedicated system user executing actions (e.g., running a Flow). Requires explicit permissions like Run Flows, plus Knowledge object/field access and Allow View Knowledge.
Agent Types: Know when to use Employee Agent (internal productivity), Service Agent (customer support), or Sales/SDR Agent (lead qualification, nurture, Close/Account Plan generation).
2. Execution & Actions
Topics & Classification: Topics group related Actions; the Classification Description drives topic-level intent recognition, while Action Instructions tell the reasoning engine when to invoke an action.
Reasoning Engine: The planner interprets natural language, builds execution plans, and selects Topics then Actions. Action dependencies must be declared via API name for correct sequencing.
Standard vs. Custom: Standard actions cover common patterns out of the box. Build custom actions calling a Flow or Apex only when standard coverage falls short.
3. Trust & Lifecycle
Model Playground: Sandbox environment to test utterances against the reasoning engine. Tune hyperparameters like Temperature, Frequency, and Presence Penalty.
Einstein Trust Layer: Dynamic Grounding injects org data; Data Masking is validated via Generative AI Audit Data. Toxicity scores range from 0 (unsafe) to 1 (safe).
Environment Activation: Activation state is per environment. An agent tested and active in a sandbox must still be manually activated in production.
Prompt Engineering
Know when to use Prompt Builder, manage and run prompt templates, field generation and Flex types, grounding techniques, and prompt best practices.
1. Templates & Design
Template Types: Field Generation (human-in-the-loop, needs a Dynamic-Forms-enabled field), Flex (callable from Apex/Flow/LWC), and Sales Email.
RTCCF Structure: Role, Task, Context, Constraints, Format: Salesforce's documented skeleton for a well-designed prompt.
Instruction Formatting: Wrap instructions in triple quotes (""") as directives; use role-play instructions ("Act as...") to control tone.
2. Grounding Techniques
Merge Fields: Related list fields via the field picker, External Object Record merge fields (Salesforce Connect), and External Service Record merge fields (REST API responses via a template-triggered prompt flow).
BYO-LLM: Einstein Studio lets you bring an external LLM into Prompt Builder instead of a standard Salesforce-hosted model.
3. Permissions & Limitations
Prompt Execute User: Run-only permission set (no create/edit rights), the right choice for front-line users like sales reps.
Known Limitations: Template changes aren't logged in the Setup Audit Trail; the User related list isn't supported for grounding.
Token Limits: Random token-limit failures on a working template are almost always record-to-record data variance, not LLM capacity changing with demand.
Data Cloud for Agentforce
Use the Agentforce Data Library, ground responses on unstructured data via chunking and indexing, Data Cloud retrievers, and search types (keyword, vector, hybrid).
1. Data Library
1:1 Relationship: An Agentforce Data Library has a strict 1:1 relationship with its agent, though it can pull from multiple sources (Knowledge, files, web).
Immutable Source: Once a data source is chosen it cannot be changed. If you need a different source, create a new library.
2. Retrievers & Search
AI Retriever: Performs contextual, embedding-based search over an indexed repository to ground responses in verifiable data.
Custom Retrievers: Built in Einstein Studio from a search index, DMO, and data space; filters (up to 10) and ranking (e.g. recency) are optional.
Search Types: Keyword for exact/structured terms, semantic/vector for typo-tolerant natural language, hybrid when queries mix both.
3. Reporting & Permissions
Data Lake Objects: AIAgentSession (session container) → AIAgentInteraction (steps/events) → AIAgentInteractionMessage (individual messages).
Runtime Access: The Agentforce Service Agent User needs the Data Cloud User permission set to retrieve Knowledge-grounded answers at runtime. This is separate from Manage Knowledge, which only covers authoring.
Development Lifecycle
Test agents in the Agentforce Testing Center, deploy from sandbox to production, and manage and monitor agent adoption.
1. Testing Center
Synthetic Testing: Runs synthetic conversations; doesn't modify live CRM data or consume Einstein Request quota; available in sandbox and production.
Success Criteria: Specify the Expected Topic API Name to validate intent classification routed correctly, not just the final answer.
Credit Visibility: Gives visibility into AI credit / Einstein Request consumption tied to test runs specifically.
2. Deployment & Monitoring
Production Deployment: Requires manual agent activation, 75% Apex test coverage, and planned/versioned dependencies (Flows, Apex).
Session Tracing: Captures the full execution trace for a session: reasoning engine decisions, actions, prompt/gateway I/O, and errors.
Multi-agent Interoperability
Understand the Model Context Protocol (MCP), the agent-to-agent protocol, and when to use the Agent API.
1. Protocols & APIs
MCP: Lets an agent discover, connect to, and invoke external tools/models through a standardized schema, without hardcoding API calls.
A2A Protocol: For communication and delegation between separate agents, distinct from MCP's agent-to-external-tool focus.
Agent API: The programmatic entry point for invoking an Agentforce agent from outside its native channels.
Ready to test what you just read?
Take a free Agentforce Specialist mock exam under real timed conditions, then see your score broken down by domain so you know exactly where to focus next.
Take the mock examMock Exam FAQ
Everything you need to know before you start your Agentforce Specialist mock exam.