Start today's 10-question Claude Architect Foundations set with source-backed explanations, local progress, and a fresh rotation every morning.
Claude Certified Architect, Foundations
Get 120 verified questions, every choice explained, Exam Mode, Practice Mode, random tests, readiness tracking, previous scores, and no ads.
Secure checkout by Stripe. Instant unlock on this page. No subscription.
Choose an unlock option to continue. We will confirm your site email in one quick checkout step.
Use this Claude Architect Foundations practice test to review Claude Certified Architect, Foundations. Questions rotate daily and each explanation links to the source used to validate the answer.
120 verified questions are in the live bank. Free daily questions are selected from a rotating sample set. Unlock Pro to access the full question bank.
The top-level system parameter is the correct location for durable instructions. Anthropic's documentation explicitly states that system prompts use this field, making it the appropriate choice for setting instructions that should apply consistently across all messages in an interaction. Messages with a role of 'system' inside the messages array are not suitable for durable instructions. These messages are intended to provide context or guidance within the conversation flow, not as persistent settings. The anthropic-version header is not used for passing instructions in Messages API interactions. This header is typically used for specifying the version of the API being used, not for setting custom instructions. The stop_sequence field is used to specify a sequence of characters that will terminate the response. It is not intended for passing durable instructions or guidance.
Favoring capability when the workload genuinely requires it aligns with Anthropic's guidance, as it prioritizes performance over cost or latency. Always choosing the fastest model is too narrow; it ignores other critical factors like capabilities and cost, which can lead to suboptimal outcomes. Keeping the cheapest model and compensating only with longer prompts does not address the core issue of workload requirements and can result in missed opportunities for better performance. Avoiding testing and assuming all Claude models can reach the same quality level is risky; it disregards the variability in model capabilities and can lead to unreliable workflows.
XML tags are specifically recommended by Anthropic for separating different sections in prompts. This allows for better organization and clarity. A longer unstructured paragraph would not effectively separate instructions, examples, and background material, leading to potential confusion. Using a different workspace for each section is impractical within the Claude API context and does not address the need for separation within a single prompt. A stop_sequence can be used to signal the end of a response but does not provide a method for structuring or separating different parts of the prompt itself.
The durable system instruction moves to the top-level system parameter. Anthropic's migration guide calls out that system guidance belongs in that top-level field in the Messages API. Into a role system message in the messages array: This is incorrect because role-specific instructions should be part of the conversation flow, not static system parameters. Into the request-id response header: This option is wrong as it does not belong in the response headers. Headers are for metadata about the request or response, not for instruction parameters. Into the max_tokens field: This choice is incorrect because max_tokens controls the maximum number of tokens generated in a response, not system instructions.
The correct answer accurately reflects Anthropic's positioning of the Messages API as offering fine-grained control for custom agent loops, while Managed Agents provide a pre-built managed agent infrastructure. This distinction is supported by the source excerpt which emphasizes the flexibility and customization options available through the Messages API. This option is incorrect because it misrepresents the capabilities of both APIs. The source does not limit the use of the Messages API to single-turn prompts or exclude Managed Agents from multi-turn work. This explanation is inaccurate as it confuses authentication requirements with the nature of the APIs. Both the Messages API and Managed Agents require authentication, but they serve different purposes and have different features. Managed Agents are not limited to Claude Code; they can be used with other Claude Platform APIs. The source does not restrict Managed Agents to Claude Code alone.
Controllable prompt changes allow teams to understand the impact of each modification, leading to better optimization. Adding random extra examples does not necessarily improve the prompt's effectiveness; it may introduce irrelevant information. Switching models without testing prompts can lead to unpredictable and potentially worse results. Judging prompt quality by response length is unreliable as it does not reflect the actual utility or accuracy of the generated text.
message_stop correctly identifies the event that marks the conclusion of a Claude streaming response, signaling the end of content delivery. message_start indicates the beginning of a message stream, not its end. It should be used at the start of a new message sequence. content_block_delta represents incremental updates within a message block during streaming. It is not the final event to mark the end of a response. workspace_end refers to the completion of an entire workspace session, which is unrelated to the specific end of a Claude message stream.
Extended thinking is explicitly documented as a Claude capability that allows the model to spend more time on deeper reasoning, making it the most direct match for handling difficult tasks. Multimodal input allows Claude to process and respond based on various types of data, but it does not directly address the need for deeper reasoning in difficult tasks. Tool use enables Claude to access external resources or perform specific actions, which can be useful for complex tasks, but it is not specifically designed for extended thinking. Structured outputs help format responses in a predictable way, which can be beneficial for clarity and organization, but they do not enhance the depth of reasoning required for difficult tasks.
The correct answer fits the source-backed scenario because Anthropic's guidance explicitly states that stable role, behavior, and operating instructions should be placed in the system prompt to apply consistently throughout the interaction. Repeatedly including the instruction in every assistant response is unnecessary and could lead to redundancy and potential confusion. It does not belong here as it would not provide consistent application across the entire interaction. Only including the instruction in the last user message is too late and ineffective. The behavior should be established from the beginning of the interaction to ensure consistency throughout, not just at the end. Placing the instruction in a stop_sequence field is incorrect because stop sequences are used to signal when Claude should stop generating text, not for providing instructions or behaviors.
Correct. According to Anthropic's guidance, a tool_use stop reason indicates that Claude is calling a tool and expects the application to execute or handle that tool interaction before continuing the loop. Incorrect. Treating the answer as a fully completed natural-language response when a tool_use stop reason is received would not allow for the execution of the requested tool interaction. Incorrect. Discarding the response because tool_use indicates an API authentication failure is incorrect. A tool_use stop reason does not imply an API authentication issue; it simply means Claude is calling a tool. Incorrect. Retrying the same request without tools when a tool_use stop reason is received would not address the fact that Claude is expecting to handle a tool interaction.
Unlock the full 120-question bank to keep practicing now.
Unlock all 120 Claude Architect Foundations questions, explanations, review tools, and exam-style practice.
A 50-question CCAF PDF for short review sessions. Questions come first, then the answer review and explanations later in the file.
We will ask for your site email in a quick checkout step, remember it on this browser, and use it again for restore.
Use the same email for checkout, restore, and the dashboard on this browser.
Your selected purchase will stay attached while you confirm the checkout email.
Choose an unlock option to continue. We will confirm your site email in one quick checkout step.
Choose the question count, question set, session mode, and timer for your full-bank practice.
Set a target once. We will keep the next study action visible before every Pro session.
Start Exam Mode or Practice Mode to build your readiness trend on this browser.
Box scores, domain breakdowns, and full answer explanations for Pro exam attempts on this browser.
Get the full bank, Exam Mode, Practice Mode, question sets, random tests, readiness tracking, saved box scores, and review tools for this exam.
The PDF versions keep questions first and move the answer review, explanations, and distractor notes to the back of the file.
You've answered 0/10 questions in today's set.
Locked: 110 more questions in the full bank.
Locked: exam simulation mode, practice mode, readiness tracking, and saved review history.
Checkout stays on this page, so you can keep practicing, unlock the full bank, and start Exam Mode or Practice Mode when you are ready.
Answer questions today and this will become a rolling 7-day scorecard.
Guest progress saves automatically on this device. Add an email later when you want a magic link that keeps your daily CCAF practice in sync across browsers.
Guest progress saves on this device automatically
Use these official Anthropic resources alongside the daily practice set. They cover the provider's own exam page, study guide, or prep material.
Availability note: Claude certification availability may vary by Anthropic partner or public certification access. Always confirm current eligibility and scheduling through Anthropic’s official certification or partner resources. Need adjacent Anthropic practice pages too? Anthropic practice hub.
The free daily Claude Architect Foundations set includes crawlable question text, answer choices, the correct answer explanation, wrong-answer distractor explanations when the reviewed bank provides them, objective mapping, and source links. Pro-only bank questions stay locked; this section mirrors only the 10 free daily questions already shown on this page.
In a top-level system parameter
The top-level system parameter is the correct location for durable instructions. Anthropic's documentation explicitly states that system prompts use this field, making it the appropriate choice for setting instructions that should apply consistently across all messages in an interaction. Messages with a role of 'system' inside the messages array are not suitable for durable instructions. These messages are intended to provide context or guidance within the conversation flow, not as persistent settings. The anthropic-version header is not used for passing instructions in Messages API interactions. This header is typically used for specifying the version of the API being used, not for setting custom instructions. The stop_sequence field is used to specify a sequence of characters that will terminate the response. It is not intended for passing durable instructions or guidance.
Favor capability even if latency or cost are higher when the workload genuinely requires it
Favoring capability when the workload genuinely requires it aligns with Anthropic's guidance, as it prioritizes performance over cost or latency. Always choosing the fastest model is too narrow; it ignores other critical factors like capabilities and cost, which can lead to suboptimal outcomes. Keeping the cheapest model and compensating only with longer prompts does not address the core issue of workload requirements and can result in missed opportunities for better performance. Avoiding testing and assuming all Claude models can reach the same quality level is risky; it disregards the variability in model capabilities and can lead to unreliable workflows.
XML tags to separate the prompt sections
XML tags are specifically recommended by Anthropic for separating different sections in prompts. This allows for better organization and clarity. A longer unstructured paragraph would not effectively separate instructions, examples, and background material, leading to potential confusion. Using a different workspace for each section is impractical within the Claude API context and does not address the need for separation within a single prompt. A stop_sequence can be used to signal the end of a response but does not provide a method for structuring or separating different parts of the prompt itself.
Into the top-level system parameter
The durable system instruction moves to the top-level system parameter. Anthropic's migration guide calls out that system guidance belongs in that top-level field in the Messages API. Into a role system message in the messages array: This is incorrect because role-specific instructions should be part of the conversation flow, not static system parameters. Into the request-id response header: This option is wrong as it does not belong in the response headers. Headers are for metadata about the request or response, not for instruction parameters. Into the max_tokens field: This choice is incorrect because max_tokens controls the maximum number of tokens generated in a response, not system instructions.
The Messages API gives fine-grained control for custom agent loops, while Managed Agents provide a pre-built managed agent harness
The correct answer accurately reflects Anthropic's positioning of the Messages API as offering fine-grained control for custom agent loops, while Managed Agents provide a pre-built managed agent infrastructure. This distinction is supported by the source excerpt which emphasizes the flexibility and customization options available through the Messages API. This option is incorrect because it misrepresents the capabilities of both APIs. The source does not limit the use of the Messages API to single-turn prompts or exclude Managed Agents from multi-turn work. This explanation is inaccurate as it confuses authentication requirements with the nature of the APIs. Both the Messages API and Managed Agents require authentication, but they serve different purposes and have different features. Managed Agents are not limited to Claude Code; they can be used with other Claude Platform APIs. The source does not restrict Managed Agents to Claude Code alone.
Make controllable prompt changes and measure the impact rather than changing everything at once
Controllable prompt changes allow teams to understand the impact of each modification, leading to better optimization. Adding random extra examples does not necessarily improve the prompt's effectiveness; it may introduce irrelevant information. Switching models without testing prompts can lead to unpredictable and potentially worse results. Judging prompt quality by response length is unreliable as it does not reflect the actual utility or accuracy of the generated text.
message_stop
message_stop correctly identifies the event that marks the conclusion of a Claude streaming response, signaling the end of content delivery. message_start indicates the beginning of a message stream, not its end. It should be used at the start of a new message sequence. content_block_delta represents incremental updates within a message block during streaming. It is not the final event to mark the end of a response. workspace_end refers to the completion of an entire workspace session, which is unrelated to the specific end of a Claude message stream.
Extended thinking
Extended thinking is explicitly documented as a Claude capability that allows the model to spend more time on deeper reasoning, making it the most direct match for handling difficult tasks. Multimodal input allows Claude to process and respond based on various types of data, but it does not directly address the need for deeper reasoning in difficult tasks. Tool use enables Claude to access external resources or perform specific actions, which can be useful for complex tasks, but it is not specifically designed for extended thinking. Structured outputs help format responses in a predictable way, which can be beneficial for clarity and organization, but they do not enhance the depth of reasoning required for difficult tasks.
In the system prompt
The correct answer fits the source-backed scenario because Anthropic's guidance explicitly states that stable role, behavior, and operating instructions should be placed in the system prompt to apply consistently throughout the interaction. Repeatedly including the instruction in every assistant response is unnecessary and could lead to redundancy and potential confusion. It does not belong here as it would not provide consistent application across the entire interaction. Only including the instruction in the last user message is too late and ineffective. The behavior should be established from the beginning of the interaction to ensure consistency throughout, not just at the end. Placing the instruction in a stop_sequence field is incorrect because stop sequences are used to signal when Claude should stop generating text, not for providing instructions or behaviors.
Execute or handle the requested tool interaction before continuing the loop
Correct. According to Anthropic's guidance, a tool_use stop reason indicates that Claude is calling a tool and expects the application to execute or handle that tool interaction before continuing the loop. Incorrect. Treating the answer as a fully completed natural-language response when a tool_use stop reason is received would not allow for the execution of the requested tool interaction. Incorrect. Discarding the response because tool_use indicates an API authentication failure is incorrect. A tool_use stop reason does not imply an API authentication issue; it simply means Claude is calling a tool. Incorrect. Retrying the same request without tools when a tool_use stop reason is received would not address the fact that Claude is expecting to handle a tool interaction.
dotCreds builds Claude Architect Foundations practice questions from public exam objectives and Anthropic exam and documentation references. The questions are written for realistic study practice, not copied from exam dumps.
Each question includes an explanation and, when available, a source link back to the provider documentation or reference used to validate the answer. That keeps the practice tied to study material you can actually review.
The page tracks today's answered count and accuracy for the 10-question daily set, then saves a 7-day score history on this device so you can see your recent practice trend.
The site is the fastest way to start Claude Architect Foundations practice without installing anything. It is built for daily recall, quick weak-topic discovery, and source-backed explanations you can review immediately.
The web page is the quick daily practice layer. If a dotCreds app is available for Claude Architect Foundations, the app is better for larger banks, focused weak-domain drills, longer review sessions, and mobile study routines.
Availability note: Claude certification availability may vary by Anthropic partner or public certification access. Always confirm current eligibility and scheduling through Anthropic’s official certification or partner resources before you plan around this practice set.
Unlock the full 120-question bank, Exam Mode, Practice Mode, random tests, readiness tracking, previous scores, and no ads.
Secure Stripe checkout opens next using the site email already entered above.
Flexible search understands AI-901, ai901, ai 901, 901, ai, network plus, and saa c03.