5 CCA-F Practice Questions: Claude Code Configuration & Workflows (with Explanations)

Correct answer: B

Plan mode is designed for exactly this case: a large, multi-file change with architectural implications where multiple valid approaches exist. In plan mode Claude reads files and explores but does not edit, then presents a plan you can review (or refine with Ultraplan) before approving execution. This prevents costly rework on a 45-file migration.

• bypassPermissions mode is incorrect because it disables safety checks and is intended only for isolated containers/VMs; rushing a 45-file migration with no oversight is risky.
• Default mode, since plan mode is only for read-only investigation and a migration is a write task is incorrect. Plan mode is specifically about deferring writes during a write task: you explore in plan mode, then approve and switch to edit mode for execution.
• dontAsk mode is incorrect because it auto-denies anything outside the allow rules, making interactive design work impractical; it is for locked-down CI, not exploratory architectural work.

Correct answer: B

The -p / --print flag is the documented non-interactive mode: Claude processes the prompt, prints the response to stdout, and exits without waiting for input. It is the canonical entry point for CI/CD scripts and the Agent SDK.

• --interactive=false is incorrect; there is no such flag in the documented CLI.
• --ci-mode is incorrect; no such flag exists. The intent is achieved through -p combined with flags like --output-format json and permission flags.
• --detach is incorrect; there is no --detach flag. Background sessions are launched with --bg, which is a different concept (a long-lived background agent, not a one-shot exit-on-done run).

Correct answer: A

For CI integrations that consume the output programmatically, run with -p, set --output-format json, and (when you need a stable shape) pass --json-schema. The schema enforces the structure of the structured_output field so a downstream script can map findings to inline PR comments without ad-hoc parsing.

• -p with --verbose, parsing with regex is incorrect: free-form text is unstable across runs and Claude versions; regex parsing is exactly what --json-schema replaces.
• Interactive mode with --resume is incorrect: interactive mode waits for stdin and is not appropriate for CI. --resume picks up an existing session by ID and is unrelated to structured CI output.
• claude --teleport is incorrect: --teleport resumes a web session in a local terminal; it does not convert output to JSON.

Correct answer: B

Nested CLAUDE.md files load on-demand when Claude reads files in those subdirectories, which is the documented mechanism for directory-scoped conventions. For conventions that span the codebase (like 'all *.test.tsx files'), .claude/rules/ files with a paths glob frontmatter load only when matching files are read, which is more efficient than a directory-level CLAUDE.md.

• Add every testing convention to the root CLAUDE.md is incorrect: it bloats the always-loaded context and causes Vitest rules to interfere when editing Playwright tests.
• Tell developers to manually paste the relevant convention is incorrect: it is unreliable and defeats the purpose of persistent project memory.
• Single /testing skill is incorrect: a skill is invoked on demand (typed or auto-invoked by description match), not on every file edit. For per-file-type conventions, path-scoped rules or nested CLAUDE.md are the right primitives.

Correct answer: A

Path-scoped rules are exactly this: a markdown file under .claude/rules/ with a paths field in the YAML frontmatter that uses glob patterns. The rule is loaded into context only when Claude reads files matching the pattern, keeping unrelated sessions lean and ensuring Terraform conventions are not noise outside that scope.

• Append the Terraform conventions to the root CLAUDE.md is incorrect: root CLAUDE.md loads on every session regardless of what you are doing, defeating the targeting goal.
• PreToolUse hook on every Bash call is incorrect: hooks enforce shell-side behavior at lifecycle events; they are not the documented mechanism for path-scoped contextual instructions, and would inject rules on unrelated Bash calls too.
• ~/.claude/rules/terraform.md with no frontmatter is incorrect: rules without a paths field load unconditionally, and the user-level path means they would apply to every project on the machine, not just this one.