CCAR-P Practice Question: Developer Productivity and Operational Enablement
How should a development team manage sensitive system instructions that they do not want users to see or modify?
⚠ Common exam trap
Candidates store sensitive system instructions on the client side where end-users can easily inspect and tamper with them.
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
✓
Store the instructions on the server and use them to build the request payload.
System instructions must be handled server-side to remain protected from client-side interference. By keeping the logic in the backend, developers ensure that users cannot inspect, modify, or inject instructions into the conversation. This pattern is fundamental to security, ensuring the integrity of the model's behavior and protecting the intellectual property of the prompt logic from malicious actors or unauthorized tampering by end-users.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Obfuscate the prompt by converting it to base64 before sending it to the client.
Why it's wrong here
Base64 is an encoding, not a security layer. Any user can easily decode it. Obfuscation provides a false sense of security and does nothing to protect the instructions from determined users. Logic must always reside in the backend to be truly secure and outside the reach of the client-side environment.
- ✓
Store the instructions on the server and use them to build the request payload.
Why this is correct
Keeping instructions on the server ensures they are never exposed to the client. The server constructs the full request, including the hidden system instructions, and sends it to the API. This is the only way to effectively prevent client-side manipulation and maintain the integrity of the model's operational constraints.
- ✗
Ask the model to never repeat its instructions to the user.
Why it's wrong here
Relying on the model to enforce its own security is unreliable, as prompt injection can easily bypass these instructions. The model should never be the primary line of defense for security. Robust security must be implemented at the architectural level by ensuring instructions never reach the client in the first place.
- ✗
Hardcode the prompts in the client-side JavaScript to minimize server latency.
Why it's wrong here
Hardcoding prompts in the client-side code makes them immediately accessible to anyone who inspects the application. This is a severe security risk and violates basic application design principles for sensitive logic. Performance gains are irrelevant if the system is completely insecure, making this an unacceptable approach for professional production applications.
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.