CCAR-P Practice Question: Developer Productivity and Operational Enablement
Which architectural pattern is best suited for long-running, multi-step agentic workflows that require human-in-the-loop intervention?
⚠ Common exam trap
Many candidates choose simple message queues or naive retry logic, failing to recognize that state machine orchestration is specifically required to maintain context across human-in-the-loop pause points.
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
✓
State machine-driven orchestration with persistent task queues.
The 'Orchestrator-Worker' pattern with a state machine is ideal for complex workflows. By saving the state of the agent at each step in a database, the system can pause for human review and resume seamlessly once input is received. This pattern provides the necessary durability and auditability for production applications, ensuring that developer productivity is not hampered by fragile, monolithic processes that fail on restart.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Monolithic synchronous execution from the user's browser.
Why it's wrong here
Synchronous execution is fragile and prone to timeouts during long-running tasks. It does not support persistent state across interactions, making it impossible to reliably handle human-in-the-loop steps. This approach limits scalability and creates a poor experience for developers trying to implement robust, multi-step AI orchestration logic in production.
- ✗
Stateless API calls with all context re-sent in every request.
Why it's wrong here
Resending full context in every request is highly inefficient and quickly hits token limits. It also provides no mechanism to store the state of a long-running process while waiting for human interaction. This pattern is not viable for complex workflows that require state management and persistence over extended periods.
- ✓
State machine-driven orchestration with persistent task queues.
Why this is correct
State machines allow for robust tracking of long-running processes. By using queues to manage tasks, the system can pause, wait for external input, and reliably resume. This provides the durability required for complex agentic workflows, making it easier for developers to build, test, and maintain sophisticated AI-driven business processes.
- ✗
Client-side polling of the Anthropic API directly from the frontend.
Why it's wrong here
Exposing API interaction logic to the client is a significant security risk and prevents effective orchestration or state management. It makes the workflow difficult to audit and manage centrally. Developers should always route AI interactions through a secure backend to ensure proper control, logging, and security for the application.
About these practice questions
This CCAR-P question is part of Courseiva's 262-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 Anthropic exam blueprint
This CCAR-P practice question is part of Courseiva's free Anthropic 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 CCAR-P exam.