An Apex invocable action is being considered as the backing for an agent action. Which characterisation matches how the Agentforce Specialist exam expects you to treat it?

The specialist role selects and configures actions; it does not author Apex. Apex invocable actions are a legitimate and examinable backing type, chosen when the required logic exceeds what Flow can express declaratively, such as complex iteration, intricate transformations or a callout pattern Flow handles poorly. Recognising when to reach for one, and knowing that a developer will build it, is the expected depth. The claim that Apex must be wrapped in a Flow is wrong: an invocable action is directly selectable as an action backing, and the wrapping myth is the closest-looking trap because Flow can indeed call Apex, so both arrangements exist and only one is required. Treating Apex as the default inverts the platform guidance, which favours declarative Flow first for maintainability and for the fact that the same team can change it. Declaring Apex entirely out of scope is also wrong; the boundary the intake draws is that Apex may appear as the thing an action wires to, never as code you write or debug in an exam item. Adjacent fact: the Agent User needs access to the Apex class in its permission set, exactly as it needs Flow access, or the action fails at run time with no useful conversational signal.