CCDV-F Practice Questions

A.  

Page on every error, on the grounds that paging guarantees that no error is missed by the team during normal operation across the application's lifecycle.

B.  

Disable logging for any error that does not page, treating non-paging errors as not worth recording for later review either.

C.  

Categorize errors by severity based on impact and recoverability, then route each category to the appropriate channel for paging or logging.

D.  

Log every error with the same severity, on the grounds that differentiating severity adds complexity that does not pay off in most application setups over time.

A.  

Automated tests of the Claude integration, linting, and any other standard quality gates the team applies to its other services.

B.  

A full end-to-end production deployment on every pull request to catch all possible issues before any code is merged into the main branch.

C.  

Automated tests of the Claude integration only, with linting handled separately during local development on each developer's machine.

D.  

Automated linting and security scanning, with Claude integration testing handled manually during pre-release verification by a designated reviewer.

A.  

Structure the prompt to request output in a schema that is described in plain English, with downstream systems parsing whatever shape Claude produces.

B.  

Define a clear schema and structure the prompt to request output in that schema, with downstream systems handling any validation needed.

C.  

Define a clear schema, structure the prompt to request output in that schema, and validate Claude’s output against the schema before passing it downstream.

D.  

Avoid structured output and use free-form text everywhere instead, on the grounds that free-form text is more flexible and handles edge cases better than structured schemas.

A.  

Retiring the system, since shipping is the final lifecycle stage for any application that reaches production.

B.  

Running a formal post-deployment review that assesses the development phase before the team does any further work on the system.

C.  

Operating and maintaining the system, including monitoring, responding to issues, and planning evolution.

D.  

Handing the system over to a separate operations team that will manage it independently of the development team going forward.

A.  

Add more explicit instructions so the most recent rules dominate the model's interpretation of the prompt during each request.

B.  

Audit the prompt for overlap, contradiction, and obsolete content, then refactor so each instruction is clear, current, and non-redundant.

C.  

Tighten only the contradictory rules first, treating the overlap and obsolete content as lower-priority work the team can address later.

D.  

Split the prompt across multiple system prompts so the model sees a smaller portion at any given time.

A.  

Use distinct keys for each environment so a compromise in one environment does not affect the others during normal operation across the application's lifecycle.

B.  

Rotate the same key across environments at random intervals on the grounds that random rotation provides isolation between environments without requiring distinct keys.

C.  

Use the same key across all environments for simplicity and treat the propagation of any compromise as a known operational tradeoff for the team's key management approach.

D.  

Use a single development key everywhere on the grounds that production keys are too risky to deploy across the application's three environments during normal operation.

A.  

Approve the pull request and add the missing pieces yourself in a follow-up commit so the teammate can move on to other work immediately.

B.  

Approve the pull request as-is, on the grounds that the feature works in the happy path and the missing pieces can be added in follow-up commits.

C.  

Request changes that move prompt and model configuration to a configurable location and add tests, treating the missing error handling as a follow-up release item.

D.  

Request changes that move prompt and model configuration to a configurable location, add error handling for Claude API failures, and add tests for the integration.

A.  

Self-hosting under BYOC for an initial pilot, then evaluating whether to migrate to Anthropic-hosted infrastructure once the agent's data-handling patterns are better understood.

B.  

Deploying on Anthropic-hosted infrastructure while the team drafts a request to update the enterprise data residency policy to accommodate hosted AI deployments.

C.  

Self-hosting under BYOC to satisfy the data residency requirement, while working with the infrastructure team to reduce the operational overhead of managing the deployment.

D.  

Deploying on Anthropic-hosted infrastructure to meet the team's shipping timeline, and flagging the data residency requirement for a follow-up compliance review after launch.

A.  

Iterate on the prompt to address the underperforming category, validate the change with evals, and continue refining as needed.

B.  

Tell users to avoid the underperforming category by adding warnings in the application's user interface about handled inputs.

C.  

Replace the prompt with a new one aligned to the underperforming category, treating any common-case performance change as a known tradeoff.

D.  

Add the underperforming category to a separate Claude application with its own prompt so the original prompt does not change.

A.  

The third-party abstraction layer, on the grounds that multi-provider support is valuable for any application as a matter of long-term flexibility across vendors.

B.  

Both integration paths in parallel, where the application uses each path on different runs to compare which performs better in production over time.

C.  

A custom multi-provider abstraction layer the team builds in-house so that the team controls every part of the abstraction the application uses for its API calls.

D.  

Direct integration with Claude through its SDK, because no multi-provider need exists and abstraction would add complexity that does not pay off.