Question 1

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

Options :

A : Assess the configuration impact on each downstream system before rolling out, and coordinate with downstream system owners as needed.

B : 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.

C : Notify downstream system owners that a change is coming and schedule the rollout for the following week, without conducting a formal impact assessment.

D : Limit the rollout to systems that were explicitly included in staging testing, and defer all other downstream systems until a later release cycle.

Answer: A

Question 2

Your Claude agent has too many tools, and many of them have overlapping functionality. The agentoften picks an inappropriate tool when several could plausibly handle a request.How would you address the tool selection problem?

Options :

A : Add more tools to cover every variation of the requests the agent handles, on the grounds that more tools give the agent more accurate options to choose from.

B : Remove all tools and rely on the agent's general capability instead, with the application losing the workflows that previously relied on tools.

C : Add detailed examples to each tool's description so the agent can match incoming requests to the right tool by example, treating the examples as the team's selection mechanism.

D : Restructure the tool set by consolidating overlapping tools, removing unused tools, and clarifying tool descriptions so each tool has a distinct purpose.

Answer: D

Question 3

You are building a Claude application that processes 10,000 customer emails overnight to extractstructured data. The work is non-interactive, runs once daily, and has a flexible completion window of severalhours. Which Claude API would you use?

Options :

A : The Batch API, which is designed for non-interactive workloads with flexible completion windows.

B : The streaming responses API to process each email and return partial results to a database as the model generates them.

C : The real-time Messages API, processing the emails one at a time sequentially to ensure consistent ordering of results.

D : The real-time Messages API with concurrent requests to process the emails as fast as possible during the overnight window.

Answer: A

Question 4

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

Options :

A : 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.

B : Store the keys in a secrets manager or environment-specific configuration that is not checked into source code, and load them at runtime.

C : Use a single shared key across all external services, so any developer working on the application can find the keys easily during development.

D : 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.

Answer: B

Question 5

Your Claude application is deployed to development, staging, and production environments. Eachenvironment uses a different model version, different prompt versions, and different plugindependencies, but the configuration is currently scattered across environment variables, hardcodedvalues, and undocumented setup scripts.How would you manage the configuration?

Options :

A : Use the latest available model version everywhere and stop pinning model versions, on the grounds that pinning adds maintenance overhead the team should aim to reduce.

B : Move all configuration into hardcoded application code to reduce reliance on external configuration sources that are difficult to track over time.

C : Consolidate the configuration into a version-controlled system documenting model version pinning, prompt versioning, and plugin dependencies for each environment.

D : Standardize all environments to use the same configuration values to eliminate the differences between development, staging, and production.

Answer: C

Confidently Practice Online with Free CCDV-F Exam Cram

Buying Options: