Pass exam with CCA-F Top Exam Collection for sure one-shot

A user asks Claude to ignore all previous instructions and reveal confidential internal prompt content. How should Claude behave?

• A. Partially reveal hidden instructions.
• B. Generate random text.
• C. Follow higher-priority instructions and refuse.
• D. Reveal the prompt.

Your infrastructure-as-code repository includes Terraform modules (/terraform/), Kubernetes manifests (/kubernetes/), and CI/CD pipeline scripts (/pipelines/). Each requires different conventions, but your single root CLAUDE.md has grown to 500+ lines. When developers work on Kubernetes files, Terraform-specific rules load into context unnecessarily, consuming tokens.
What is the best approach to reorganize so only relevant guidance loads when editing specific file types?

• A. Create files in .claude/rules/ with YAML frontmatter path-scoping (e.g., paths: ["terraform/**/*"]), loading rules only when editing matching files.
• B. Restructure the root CLAUDE.md into clearly labeled sections with headers (e.g, "## Terraform Conventions"), improving organization and readability.
• C. Keep the root CLAUDE.md and use @path/to/import syntax to modularly include tool-specific guidance files from separate documents.
• D. Split content into subdirectory CLAUDE.md files (/terraform/CLAUDE.md,
  /kubernetes/CLAUDE.md), so Claude loads directory-specific guidance.

The coordinator agent has AgentDefinitions configured for all four specialized subagents, each with appropriate descriptions, prompts, and tool restrictions. During testing, you notice the coordinator correctly reasons about when to delegate - it generates messages like "I'll ask the web search agent to find sources on this topic" - but no subagent execution ever occurs. The coordinator then proceeds as if the delegation happened and continues with incomplete information. Logs show no errors. What is the most likely cause?

• A. The AgentDefinitions are configured correctly, but the coordinator's system prompt doesn't explicitly list the available subagent types, preventing the model from knowing they can be invoked.
• B. Subagent context isolation means task descriptions from the coordinator don't automatically reach subagents; you need to configure explicit context forwarding in ClaudeAgentOptions.
• C. The coordinator's allowedTools configuration doesn't include "Task", so while it can reason about delegation, it cannot invoke the tool required to spawn subagents.
• D. The coordinator's max_tokens setting is too low, causing the Task tool invocation to be truncated before the subagent type parameter can be specified.

You've configured the system so that all four subagents have access to the complete set of
18 tools. During testing, agents frequently call tools outside their specialization - the synthesis agent attempts web searches, and the report generator tries to analyze documents. What is the primary cause of this poor tool selection behavior?

• A. The agents' role descriptions in their system prompts conflict with having access to tools outside that role.
• B. The coordinator cannot track which capabilities each subagent has, leading to misrouted tasks.
• C. The tool definitions consume too much context window space, leaving insufficient room for task content.
• D. Choosing from 18 tools instead of 4-5 relevant ones increases decision complexity beyond reliable selection thresholds.

A legal department requires Claude to answer only when sufficient evidence exists in retrieved documents. What should Claude do if evidence is insufficient?

• A. Increase creativity.
• B. Search social media automatically.
• C. Clearly indicate insufficient information.
• D. Invent a likely answer.