最新的Anthropic Claude Certified Architect - Foundations - CCAR-F免費考試真題

A. Replace the default prompt using --system-prompt-file ./CLAUDE.md, which bypasses default prompt assembly and loads only the project rules.

B. Run in --bare mode and pass --append-system-prompt-file ./CLAUDE.md to load the required project standards explicitly while skipping automatic discovery.

C. Keep the default initialization and add --exclude-dynamic-system-prompt-sections to improve prompt-cache reuse across CI runners.

D. Run in --bare mode and repeat all review criteria directly in the -p prompt for every invocation.

A. Spawn a sub-agent to explore physics independently, then manually synthesize its findings with the rendering knowledge accumulated in the main conversation.

B. Summarize key rendering findings, then spawn a sub-agent for physics exploration with that summary in its initial context.

C. Continue in the current context with more targeted prompts referencing the specific classes by name.

D. Use /clear to reset context completely, then start fresh with physics exploration using file paths from the project's CLAUDE.md.

A. Implement retry logic with exponential backoff inside each tool implementation so transient errors are resolved transparently within the tool before any failure result is surfaced to Claude in the agentic loop.

B. Remove is_error: true and return the error details as normal tool content, so Claude reasons about the response as data rather than treating it as a flagged failure condition that biases retry behavior.

C. Add an error classification step in the agentic loop that intercepts tool errors before Claude sees them, tags each as "retry," "try_alternative," or "escalate," and appends that recommendation to the tool result.

D. Return error-type-specific messages with is_error: true, e.g., "Order not found-try get_customer to search by phone" for data errors and "Database timeout (transient)-retry should succeed" for infrastructure errors.

A. Set timeout-minutes: 5 on the GitHub Actions step and monitor per-run costs through the Anthropic Console usage dashboard.

B. Set --permission-mode dontAsk to automatically deny tool-permission requests that are not in the explicitly allowed set.

C. Use the --model flag to select a smaller, less expensive model so that every iteration uses fewer tokens and costs less.

D. Add --max-turns 10 --max-budget-usd 2.00 to the claude -p invocation to cap agentic turns and expenditure.

A. Choosing from 18 tools instead of 4-5 relevant ones increases decision complexity beyond reliable selection thresholds.

B. The agents' role descriptions in their system prompts conflict with having access to tools outside that role.

C. The tool definitions consume too much context window space, leaving insufficient room for task content.

D. The coordinator cannot track which capabilities each subagent has, leading to misrouted tasks.

A. Add few-shot examples to the system prompt demonstrating correct selection for each ambiguous tool pair, such as showing when issue_credit applies versus when process_refund is appropriate.

B. Consolidate semantically overlapping tools - merge issue_credit and process_refund into a single resolve_compensation tool with an action parameter, and fold check_delivery_status into lookup_order with an optional include_tracking flag.

C. Split the tools across two sub-agents - a "financial resolution" agent with process_refund , issue_credit ,and apply_promo_code , and a "delivery operations" agent with the remaining delivery tools - with a coordinator routing between them.

D. Enable the tool search tool with defer_loading on the six new tools, keeping the original four always loaded, so the agent dynamically discovers specialized tools only when needed.

A. Consolidate into a single get_property_with_neighborhood(property_id) tool returning both datasets.

B. Create a lookup_address(property_id) helper tool for retrieving addresses.

C. Change get_neighborhood_info to accept property_id, resolving the address internally.

D. Add retry logic and timeout handling to get_property_details.

A. Increased hallucinations only.

B. Higher token usage and cost.

C. Lower reliability.

D. Reduced model capability.

A. Implement two-phase generation in which a second Claude call scores every test against quality criteria and filters out low-scoring tests before presenting them to developers.

B. Restrict test generation to directories where historical quality metrics show higher acceptance rates, disabling it in areas where generated tests consistently require substantial editing.

C. Document your testing standards in CLAUDE.md, including valuable-test criteria, available fixtures and their intended uses, and examples distinguishing meaningful behavioural tests from trivial assertions.

D. Add post-generation coverage analysis that automatically filters out every generated test that does not increase line coverage beyond the existing test suite.

A. It compresses model weights.

B. It permanently retrains Claude.

C. It supplies relevant external knowledge during inference.

D. It changes token pricing.

A. Configure hooks for all three: a PreToolUse hook script that blocks Edit calls targeting db/migrations/,a PreToolUse hook script that adds logging convention context before edits, and a PostToolUse hook that runs Prettier after TypeScript edits.

B. Move all three requirements into .claude/rules/ as path-scoped rules: one targeting db/migrations/** that forbids editing those files, and others targeting **/*.ts for the logging convention and formatting instruction.

C. Rewrite all three requirements in CLAUDE.md using stronger directive language and add few- shot examples that demonstrate Claude refusing to edit migration files and running Prettier after edits.

D. Add Edit(./db/migrations/**) to permissions.deny in the project settings, keep the logging preference in CLAUDE.md, and add a PostToolUse hook on the Edit tool that runs Prettier on changed TypeScript files.

A. Prompt routing based on request type.

B. Disable retrieval.

C. Maximum temperature.

D. One prompt for every scenario.

A. Index all agent outputs in a shared vector store. When resuming, each agent queries the store using semantic search to retrieve relevant prior findings.

B. Persist the coordinator's conversation log containing all task delegations and responses, providing this to agents when resuming.

C. Have each agent persist a structured export to a known location. On resume, the coordinator loads the manifest and injects relevant state into agent prompts.

D. Have each agent maintain its own persistent state file and reload it independently at the start of each session.

A. Max tokens

B. Context window

C. Prompt length

D. Temperature

A. Define a strict output schema and include format normalization rules in your prompt.

B. Extract data as-is and normalize formats in post-processing code after Claude returns.

C. Use separate extraction calls for each field to ensure consistent handling of each type.

D. Request multiple extraction attempts per document and select the most common format.