최신Anthropic Claude Certified Architect - Professional - CCAR-P무료샘플문제

A. The capability needs to query a live database for the most recent regulatory filings.

B. The capability must also be callable from a developer's command-line interface.

C. The capability requires direct authentication against the corporate identity provider.

D. The capability is procedural knowledge with no live external-system calls required.

A. The model generates a plausible-sounding answer that is unsupported by any retrieved document.

B. A database connection timeout causes a retrieval call to return an empty result set.

C. An expired TLS certificate blocks outbound API calls to the Claude endpoint.

D. A misconfigured load balancer routes requests to a deprecated API version.

E. The model refuses a legitimate query because surface features trigger an overly broad safety pattern.

A. Stop measuring production outcomes once the deployment has successfully launched, treating the go- live milestone as the end of the evaluation and iteration cycle.

B. Rebuild the entire system architecture from scratch at the start of every iteration cycle regardless of what production telemetry, evaluations, and stakeholder feedback indicate is needed.

C. Discard the evaluation framework and reference set once the deployment is in production, accepting that future iterations will have no structured basis for measuring the impact of changes.

D. Review production telemetry, sampled output evaluations, and stakeholder feedback to identify the highest-impact change for the next cycle, then plan the change against the evaluation framework.

A. Source code alone with no integrating architecture overview, ADRs, component contracts, evaluation framework, runbooks, on-call playbook, or known-limitations register to support the delivery team.

B. The most recent set of design presentation slides without component-level diagrams, interface contracts, an evaluation framework with a reference set, runbooks, or a known-limitations register.

C. Architecture overview, ADRs, component contracts, evaluation framework with reference set, runbooks, on-call playbook, and known limitations.

D. A verbal walkthrough conducted on the day of handoff with no written architecture overview, ADRs, component contracts, evaluation framework, runbooks, playbook, or known limitations.

A. Skip the rationale, alternatives, and trade-off discussion entirely and simply announce the chosen decision, leaving both audiences without the context needed to implement or validate it.

B. Lead with the decision, the business outcomes it serves, and the trade-offs accepted; follow with the technical rationale, alternatives, and implementation implications for the engineering audience.

C. Open with a deep dive into low-level implementation details targeted at engineering leads, and stop there without addressing the business outcomes or trade-offs the executive sponsor needs.

D. Present a single undifferentiated narrative that addresses technical and business concerns with equal weight throughout, treating both audiences as requiring the same depth on every section.

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

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

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

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

A. Inverse sampling that reviews only high-confidence routine outputs and skips low-confidence and high- impact outputs.

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

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

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