SF-Admin Agentforce AI Practice Question
An administrator at a retail company has built an Agentforce Service Agent that handles returns and exchanges. During testing, the agent correctly answers product questions but fails to initiate a return because it cannot find the 'Initiate Return' action. The action was created as an Apex class implementing the @InvocableMethod annotation. Which step should the administrator take to make the action available to the agent?
⚠ Common exam trap
The trap here is assuming that any invocable Apex method is automatically available to an agent without explicitly adding it as an action in Agent Builder.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Create an invocable action in Agent Builder and reference the Apex class.
Agentforce agents can use actions built from Flows, Apex, or Prompt Templates, but these must be explicitly added as actions in Agent Builder. Simply creating an Apex class with @InvocableMethod does not make it available; the administrator must create an action that references the class. This ensures the agent can discover and invoke the method during conversations.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Create an invocable action in Agent Builder and reference the Apex class.
Why this is correct
In Agent Builder, actions are defined by selecting an invocable method (Flow, Apex, or Prompt Template). The administrator must create a new action, choose 'Apex' as the action type, and select the class that implements @InvocableMethod. This registers the action with the agent so it can be invoked during conversations. Without this step, the agent has no knowledge of the Apex method.
- ✗
Add the Apex class to the agent's permission set and enable 'Agentforce Action Access'.
Why it's wrong here
Permission sets grant users access to Apex classes, but they do not register actions with an agent. Agentforce actions are configured in Agent Builder, not through permission sets. While the running user needs access to the Apex class, that alone does not make the action available to the agent. The action must be explicitly defined in the agent's configuration.
- ✗
Deploy the Apex class to the agent's connected app and add it as a remote site setting.
Why it's wrong here
Connected apps and remote site settings are used for external integrations and callouts, not for registering actions within Agentforce. The Apex class is internal to Salesforce and does not require a connected app or remote site. The correct mechanism is to define an action in Agent Builder that references the invocable Apex method.
- ✗
Add the Apex class to the agent's Einstein Trust Layer configuration.
Why it's wrong here
The Einstein Trust Layer is responsible for data masking, zero-data retention, and audit trails; it does not register actions for an agent. Adding the Apex class there will not make it discoverable in Agent Builder. The action must be exposed through the agent's action registry, which is done by assigning the Apex class as an action in the Agentforce Agent configuration.
About these practice questions
This SF-Admin question is part of Courseiva's 202-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Salesforce exam blueprint
This SF-Admin practice question is part of Courseiva's free Salesforce certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SF-Admin exam.