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

A. Add a priority instruction directing the model to evaluate all instructions and apply whichever appears most contextually appropriate on each request.

B. Keep both instructions and rely on the model to decide which one to follow on each request.

C. Increase temperature so output randomness masks the contradiction.

D. Remove or rewrite the gap-filling instruction so the prompt consistently constrains the model to source- supported content.

A. Disable prompt caching entirely to ensure fresh context processing on every request, preventing stale prefix content from affecting latency-sensitive interactions.

B. Reduce retrieval depth to the top-k passages that historically cover the answer, and cache stable system- prompt content.

C. Increase retrieval depth to the corpus maximum to improve recall regardless of latency.

D. Switch every turn to the heaviest available model to maximize output quality, accepting that the increased model latency will worsen the per-turn SLO rather than improve it.

A. Place a human reviewer in the loop for a randomly selected sample of requests, without defining criteria for what the reviewer should check or which output categories require mandatory review.

B. Place a human reviewer between the model's output and any high-impact, irreversible action, with explicit criteria for what the reviewer must check before approval.

C. Remove all human review steps from the pipeline to maximize throughput, accepting that high-impact and irreversible actions will be taken without any human approval or oversight.

D. Place a human reviewer only after the irreversible action has already executed, making the review a post-hoc audit rather than a meaningful pre-action check or approval gate.

A. Centralized authorship by a single platform team responsible for every Skill produced.

B. Per-developer authorship across the 280 engineers with no team-level coordination required.

C. Fully decentralized authorship across the 14 teams with no review before publication.

D. Federated authorship across the 14 teams with a central review and publication gate.

A. Instruct each engineer to configure their preferred Claude model in personal user-scope settings.

B. Store the team's shared API key in the project-scope settings.json so all engineers use the same credential.

C. Apply managed configuration to enforce non-overridable security and compliance policies across all team members.

D. Commit shared MCP server definitions and tool permissions in project-scope configuration files alongside the repository.

E. Set editor theme and display preferences at the project scope so they are uniform across workstations.

A. Add additional MCP servers to give the team more capability, which increases rather than reduces the number of tool definitions loaded into the session's context budget.

B. Increase the prompt's verbosity with additional instructions and context, which consumes more of the context budget rather than reducing the tool-definition overhead causing the issue.

C. Disable every MCP server in the configuration to free up context budget, accepting that the team loses all tool access and cannot perform any MCP-dependent task in the session.

D. Enable Tool Search so tool definitions are deferred and discovered on demand rather than loaded into context upfront.

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. 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.

C. 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.

D. 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.

A. A dashboard alert threshold needs a small numerical adjustment to reduce false-positive noise, which can be handled as an operational configuration change without a new design cycle.

B. A minor copy edit is requested in a customer-facing string within the existing UI, which can be handled as a localized content change without altering component responsibilities or contracts.

C. The system's current architecture cannot meet the new requirements without changes to component responsibilities or core contracts.

D. A runbook step requires a clarification edit to improve on-c all guidance accuracy, which can be handled as a documentation update without changes to component responsibilities or core contracts.

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

B. The model generates a plausible-sounding answer unsupported by any retrieved document.

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

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

E. A database connection timeout causes retrieval to return an empty result set.