Your Claude application runs long agentic workflows where the agent makes many tool calls, and the conversation history grows quickly. After about 20 tool calls, you notice the agent's responses become less focused and sometimes ignore earlier task constraints.
How would you address this?

• A. Remove tool calling from the workflow entirely so the agent operates as a single text-generation step with no tool outputs accumulating in the context window.
• B. Apply context engineering techniques such as tool output pruning or compaction to keep the active task state visible while reducing the volume of older content.
• C. Increase the model's context window so the agent can hold every tool output at full detail across the entire workflow no matter how many tool calls it accumulates.
• D. Restart the agent every five tool calls to prevent any drift, with the agent losing all task state at each restart point during the workflow.

You are designing a Claude application that maintains user sessions across multi-turn conversations. The product team has asked how the application will handle session lifecycle: when sessions should expire, how state is reset, and how the application avoids carrying stale context into new conversations.
How would you design session lifecycle?

• A. Define explicit session expiration rules but rely on users to start new conversations when they want fresh context, with no automatic reset triggers in the application.
• B. Define state reset triggers tied to specific application events but apply them across all sessions globally, with no per-session expiration rules.
• C. Define a single short session timeout that applies across all conversations and treat the timeout as the application's complete session lifecycle mechanism.
• D. Define explicit session expiration rules, state reset triggers, and rules for starting fresh sessions so stale context does not leak into new conversations.

You have just shipped a new Claude-powered application to production. The development phase is complete, and the system is now in active use by internal teams.
The next phase of work for this system is...

• A. Retiring the system, since shipping is the final lifecycle stage for any application that reaches production.
• B. Handing the system over to a separate operations team that will manage it independently of the development team going forward.
• C. Running a formal post-deployment review that assesses the development phase before the team does any further work on the system.
• D. Operating and maintaining the system, including monitoring, responding to issues, and planning evolution.

Your team is preparing to roll out a configuration change that updates several prompt versions across a Claude application used by multiple downstream systems. The change has already been tested in staging, but the team has not assessed how the prompt change will affect each downstream system that depends on the application's output.
What would you do before rolling out the change?

• A. Assess the configuration impact on each downstream system before rolling out, and coordinate with downstream system owners as needed.
• B. Limit the rollout to systems that were explicitly included in staging testing, and defer all other downstream systems until a later release cycle.
• C. Document the prompt version changes in the application changelog and proceed with the rollout, treating the staging test results as sufficient evidence of impact across all downstream systems.
• D. Notify downstream system owners that a change is coming and schedule the rollout for the following week, without conducting a formal impact assessment.

Your team uses Claude Code across multiple repositories. You want the team's rules and general coding standards to apply to all repositories, and other rules to apply only to specific repositories. The team is currently duplicating instructions across every repository's CLAUDE.md file.
How would you address this?

• A. Use a single repository's CLAUDE.md as the central source of truth and link to it from every other repository's CLAUDE.md file.
• B. Stop using CLAUDE.md altogether and ask each developer to configure Claude Code manually for each project they work on.
• C. Use a CLAUDE.md hierarchy that scopes general standards broadly and project-specific context within each repository's local CLAUDE.md.
• D. Move all instructions to a separate documentation site that developers consult during Claude Code sessions across all repositories.