Online Access Free CCDV-F Practice Test

You are setting up a Claude application that requires API keys for several external services.
What is the best way to store the keys?

• A.Email the keys to each developer as needed and have each developer paste the keys into their local environment when they begin working on the application's code.
• B.Use a single shared key across all external services, so any developer working on the application can find the keys easily during development.
• C.Store the keys in a secrets manager or environment-specific configuration that is not checked into source code, and load them at runtime.
• D.Put the keys in the application's configuration file and check the configuration file into the team's repository alongside the rest of the source code.

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 a single short session timeout that applies across all conversations and treat the timeout as the application's complete session lifecycle mechanism.
• B.Define explicit session expiration rules, state reset triggers, and rules for starting fresh sessions so stale context does not leak into new conversations.
• C.Define state reset triggers tied to specific application events but apply them across all sessions globally, with no per-session expiration rules.
• D.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.

You are building an MCP server that exposes several internal data sources as MCP resources. The server needs to be deployed so multiple Claude applications can integrate with it.
How would you approach the build and deployment?

• A.Build the MCP server with resource and tool definitions scoped to the first Claude application that needs it, and extend the definitions to additional applications as each integration is requested.
• B.Author the server with clearly defined resources, tools, and prompts, choose a communication pattern, and deploy to an accessible hosting environment.
• C.Deploy the MCP server only on individual developer machines, with the Claude applications unable to reach the server outside each developer's machine.
• D.Bypass the MCP server and embed each data source directly in every Claude application that needs the data, with each application maintaining its own integration.

Your team is preparing a new Claude application for production, and the product team has asked for a cost projection. The team needs to estimate the cost based on expected request volume, average input length, and average output length. How would you build the projection?

• A.Build a cost model that combines expected request volume, average input tokens, average output tokens, the chosen model's pricing, and any caching benefits.
• B.Build a cost model that uses the average per-request cost from a similar Claude application the team built last year, scaling that figure by expected request volume.
• C.Build a cost model that combines expected request volume and average input tokens, treating output tokens as a small enough share of cost to leave out of the projection.
• D.Build a cost model based on expected request volume and the chosen model's pricing, treating average input and output token counts as variables to be estimated post-launch.

Your Claude application uses structured output that is consumed by downstream code. The team wants to handle malformed or unexpected output gracefully so it does not crash downstream systems.
The best choice for handling this issue would be to...

• A.Crash on any unexpected output and require manual recovery on affected requests the application handles during normal operation.
• B.Use the output the model produces and leave schema enforcement to a later phase of production after the application is more complete.
• C.Apply defensive parsing to handle unexpected fields, missing values, and type mismatches that the downstream code might otherwise crash on.
• D.Silently drop any output that does not match expectations so downstream systems do not see the malformed output the application receives from the model.