CCAR-P 無料問題集「Anthropic Claude Certified Architect - Professional」

（A）Risk-stratified sampling that reviews all low-confidence and high-impact outputs and a smaller random sample of high-confidence routine outputs.

（B）Universal review of every output regardless of confidence or throughput impact.

（C）Inverse sampling that reviews only high-confidence routine outputs and skips low-confidence and high- impact outputs.

（D）No sampling, relying entirely on user complaints to reveal quality and safety problems after they affect users.

（A）Hide the scope-addition request from the broader delivery team to avoid a difficult conversation, allowing the change to proceed without team awareness of its timeline implications.

（B）Acknowledge the request, describe the scope and timeline implications transparently, and propose options-defer it, descope something else, or extend the timeline-for the stakeholder to choose.

（C）Accept the additional scope into the current release without describing the timeline or descoping implications, allowing the delivery plan to absorb unacknowledged changes until they surface as delays.

（D）Decline the request outright without acknowledging the stakeholder's underlying need or offering alternatives such as deferral, descoping, or timeline extension.

（A）A pure agent loop with open web-browsing tools to surface the most current policy information, without constraining retrieval to the authoritative internal corpus.

（B）Multi-agent orchestration with a planner, researcher, and writer agent for every query.

（C）Augmented LLM with retrieval-augmented generation over the indexed authoritative corpus and citation rendering on each answer.

（D）A static prompt with the entire policy corpus concatenated into every request.

（A）Inside the system prompt as a natural-language instruction for Claude to ignore unauthorized documents.

（B）Nowhere in the pipeline; rely on the model's general refusal behavior to reject unauthorized document access without any enforced access control.

（C）At the retrieval layer, before any role-restricted content reaches the prompt-construction step or the model.

（D）After the response is generated, by post-filtering content that should not have been retrieved.

（A）An architecture overview and a list of known limitations, without component-level diagrams, interface contracts, configuration parameters, or operational runbooks to support implementation.

（B）Component responsibilities, contracts between components, sequence diagrams of the dominant flows, configuration parameters with defaults, and operational runbooks.

（C）Component responsibilities and interface contracts only, without sequence diagrams of the dominant flows, configuration parameters with defaults, or runbooks to guide operational tasks.

（D）An architecture overview and sequence diagrams for the dominant flows, without interface contracts, configuration-parameter tables, or operational runbooks for the delivery team to follow.

（A）A single one-page architecture diagram with no ADRs, no runbooks, no on-call playbook, and no list of known limitations to support operators or future maintainers.

（B）Code comments scattered across individual source files with no integrating architecture overview, no ADRs, no runbooks, and no on-call playbook to orient operators or new team members.

（C）Architecture overview, ADRs, component-level diagrams, runbooks for common operations, an on-call playbook, and a list of known limitations.

（D）A verbal handover walkthrough conducted on the day of transition, with no written architecture overview, ADRs, runbooks, playbook, or known limitations captured for future reference.

（A）Tool-call payloads and outcomes are recorded with redaction applied to known sensitive fields.

（B）Model identity and version on each turn are not recorded with the turn artifacts.

（C）Latency and token usage on every span are emitted to the central metrics pipeline.

（D）Request-scoped correlation identifiers do not propagate across agent and tool calls.

（E）Trace spans for each agent step are exported to the shared distributed-tracing backend.