A choir-library helper must remember that a household already borrowed the Messiah score, call the inventory tool, and then send the pickup message in that order. Which pairing names those three needs?
Select an answer to reveal the explanation.
Short Explanation
Think of remembering the Messiah loan, calling inventory, then sending the pickup text, in that order. Memory is what happened before, tools are what you can invoke, orchestration is the sequence. Swap those names and the workflow falls apart.
Full Explanation
For an agentic choir-library helper, three concepts must stay distinct: memory holds what happened before (the household already borrowed the Messiah score), tools are invokable capabilities (the inventory API), and orchestration is the ordered control of steps (remember, then call inventory, then send the pickup message). That pairing matches the three needs in the stem and keeps state, capability, and control flow from collapsing into one vague 'agent' label.
Saying memory is the inventory API and tools are the remembered loan reverses the definitions: APIs are tools to invoke; prior loan state belongs in memory. Calling orchestration a GPU temperature reading invents a hardware metric that has nothing to do with sequencing agent steps for the choir desk. Collapsing all three needs into clustering of unused folder colors replaces agent design with an unrelated unsupervised grouping task.
Exam caveat: memory ≠ tools ≠ orchestration. Mixing those labels is a common distractor pattern on agent questions, so name each role explicitly.
Operational check: persist the prior Messiah loan in durable memory, require the inventory tool result before composing the pickup message, and fail closed if orchestration tries to send pickup without a successful inventory check.