Pass with professional CCA-F actual quiz materials

The coordinator provides detailed step-by-step instructions to the web search subagent, specifying exact search queries, source priorities, and date filters. Production monitoring reveals three issues: (1) the subagent reports "insufficient results" rather than trying alternative approaches when pre-specified searches fail, (2) research quality drops for emerging topics that don't match expected patterns, and (3) the subagent rarely surfaces valuable tangential sources.
What's the most effective way to improve subagent adaptability?

• A. Remove procedural details entirely, delegating with simple goals like "research X thoroughly" and relying on the subagent's general capabilities.
• B. Implement a topic classification step where the coordinator categorizes requests as "well-defined" or "exploratory" and uses different instruction styles for each category.
• C. Add explicit fallback directives to the detailed instructions: "If specified searches yield fewer than N results, attempt alternative query formulations before reporting failure."
• D. Specify research goals and quality criteria (coverage breadth, source diversity, recency) rather than procedural steps, letting the subagent determine its search strategy.

The agent verifies customer identity through a multi-step process before resetting passwords.
During testing, you notice that after the customer answers the third verification question, the agent asks them to provide their name again, as if the earlier exchange never happened. What's the most likely cause of this behavior?

• A. The conversation history isn't being passed in subsequent API requests.
• B. The verification tool is clearing the agent's internal state after each successful validation step.
• C. Claude's memory retention is limited to two conversational turns by default, requiring explicit configuration to extend it.
• D. The prompt lacks instructions telling Claude to remember information across multiple exchanges.

During a billing dispute resolution, your agent successfully retrieves customer info via get_customer and order details via lookup_order, but when attempting to call process_refund, the tool returns a timeout error. The agent has enough information to explain the charges and verify refund eligibility, but cannot actually process the refund due to the backend failure. What approach best balances first-contact resolution with appropriate error handling?

• A. Escalate immediately to a human agent since the refund action cannot be completed
• B. Explain the billing confirm refund eligibility, acknowledge the system issue preventing immediate processing, and offer escalation or retry later
• C. Implement automatic retries with exponential backoff for process_refund, keeping the conversation open until the refund is successfully processed
• D. Confirm the refund will be processed and close the conversation, since the system has all necessary information to complete it automatically

You are using Claude Code to accelerate software development. Your team uses it for code generation, refactoring, debugging, and documentation. You need to integrate it into your development workflow with custom slash commands, CLAUDE.md configurations, and understand when to use plan mode vs direct execution.
Your monorepo contains shared coding standards in /docs/standards/ : security-rules.md (for services handling user data), testing-petterns.md (for all packages), and api-conventions.md (for API-facing services). Your 15 packages are organized by feature domain ( /packages/auth/,
/packages/billing/, /packages/notifications/ , etc.) without naming conventions indicating which handle user data or expose APIs. Package maintainers are expected to configure their own local development settings, as they understand their package's domain requirements. Currently, all package CLAUDE.md files duplicate all three standards, applying irrelevant guidance. What's the most effective approach?

• A. Create .claude/rules/ files for each standard with YAML frontmatter paths listing every package directory where that standard should apply.
• B. Use @imports in each package's CLAUDE.md to reference only the specific standard files relevant to that package, based on the maintainer's domain knowledge.
• C. Create a shared-stendards.md that uses @imports to combine all three standards, then have each package's CLAUDE.md import that combined file.
• D. Put all standards in the root CLAUDE.md with override instructions like "ignore security-rules.md when working in packages that don't handle user data."

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

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