CCAR-P Practice Question: Developer Productivity and Operational Enablement
Which mechanism best facilitates secure, ephemeral access to Anthropic API keys for developers within a containerized CI environment?
⚠ Common exam trap
Candidates suggest hardcoding API keys in configuration files or embedding them directly into source control repositories.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Using a secrets management service to inject keys as environment variables at runtime.
Utilizing a secrets management service such as HashiCorp Vault or AWS Secrets Manager allows for the injection of short-lived credentials into the environment. This minimizes the risk of long-lived key exposure in logs or source control. By automating secret rotation and access control, organizations can ensure developer productivity remains high without compromising the overall security posture of the infrastructure.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Hardcoding the API keys in the source code repository with encryption.
Why it's wrong here
Hardcoding secrets, even when encrypted, creates a significant security risk and management burden. It forces developers to re-commit code whenever keys rotate, violating the principle of least privilege. Secrets should be managed outside of the codebase to prevent accidental exposure and simplify the rotation process across different environments.
- ✗
Storing API keys in a local .env file on every developer workstation.
Why it's wrong here
Local environment files are prone to being accidentally committed to version control systems, leading to potential key leakage. This approach also makes credential management difficult to audit and rotate, creating an insecure development workflow that does not scale well across distributed teams or automated continuous integration platforms.
- ✓
Using a secrets management service to inject keys as environment variables at runtime.
Why this is correct
Injecting secrets as environment variables at runtime is a best practice that keeps sensitive information out of the repository. This method supports automated rotation and granular access control, ensuring that only authorized services can retrieve the credentials, thereby enhancing security and reducing the operational burden on the development team.
- ✗
Distributing shared API keys via a secure internal messaging channel.
Why it's wrong here
Sharing credentials via messaging channels is insecure and lacks an audit trail. It makes rotating keys difficult, as every team member who received the key must be updated. This method also creates a single point of failure and increases the risk of unauthorized access within the organizational ecosystem.
About these practice questions
One of 262 original CCAR-P practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Anthropic exam blueprint
This CCAR-P practice question is part of Courseiva's free Anthropic certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the CCAR-P exam.