---
title: "System prompts & templates — CCAR-P 2.2 practice questions"
description: "5 CCAR-P practice questions on objective 2.2: Design system prompts, templates, and guardrails. Part of domain 2, Models, Prompting & Context Engineering."
url: "https://claudearchitectguide.com/drill/obj/2-2"
image: "https://claudearchitectguide.com/og.png"
---

Objective 2.2 · Domain 2 · 13% of the exam

# Design system prompts, templates, and guardrails

System prompts, reusable templates and prompt-level guardrails, which is to say establishing role, scope, output format and refusal behaviour in the place that persists across a conversation. The distinction the exam draws is between instructions belonging in the system prompt, which are stable, behavioural and security-relevant, and instructions belonging in the user turn, which are task-specific and variable. Putting per-request data in a system prompt is a recurring wrong answer.

5 questions · answers and explanations shown as you go · free, no sign-up

## The rest of domain 2: Models, Prompting & Context Engineering

This domain is 13% of a scored form, about 8 of the 63 questions, spread across 5 objectives. [Drill the whole domain](https://claudearchitectguide.com/drill/2) or pick another objective below.

- [2.1 Select appropriate Claude models based on trade-offs (6)](https://claudearchitectguide.com/drill/obj/2-1)
- [2.3 Apply prompt engineering techniques (zero-shot, few-shot, chain-of-thought)(5)](https://claudearchitectguide.com/drill/obj/2-3)
- [2.4 Optimize context windows and manage token usage (5)](https://claudearchitectguide.com/drill/obj/2-4)
- [2.5 Implement prompt reuse strategies (caching, modular prompts, Skills)(5)](https://claudearchitectguide.com/drill/obj/2-5)

One objective is a narrow slice. A full-length timed mock is what tells you whether the whole thing holds together.

[Sit a timed mock →](https://claudearchitectguide.com/exam)
