Domain 2 · 33.1% of the CCDV-F exam
Applications and Integration
Turn a business need into requirements, carry it through the life cycle, and build the Claude application: API mechanics, engineering practice, product design, and configuration.
Task statements
- 2.1 · 3.4%
Understanding Requirements
Translate business goals into functional, non-functional, infrastructure, and measurable technical requirements that can drive Claude application architecture.
- 2.2 · 2.8%
Systems Life Cycle
A Claude application moves through requirements, design, implementation, verification, release, operation, and change. A model swap or a prompt edit is a new pass through that cycle, not a silent replacement.
- 2.3 · 6.8%
Claude API Mechanics
The Messages API is stateless: the client sends the history every time. Streaming changes when tokens arrive, not what they cost. Batch is for work nobody is waiting on and that does not need a multi-turn tool loop. Prompt caching pays when the stable prefix comes first.
- 2.4 · 7.4%
Software Engineering Foundations
A Claude application is still a service. The Messages call is HTTP and JSON, the client is asynchronous, and prompts, schemas, and model ids belong in version control and in review. Refactor the code into a unit a reviewer can check.
- 2.5 · 8.6%
Claude Application Design
Claude Code, Desktop, claude.ai, the API, and the SDKs do not interpret a product the same way. The application draws a boundary between instructions and untrusted content, declares the schema it will parse, keeps sessions from going stale, and treats plugins as dependencies.
- 2.6 · 4.1%
Configuration Management
Shared behavior lives in project configuration. CLAUDE.md is guidance and files are concatenated. settings.json is where a rule is enforced. Model ids, prompts, and plugin versions are pinned so a change is a reviewable diff.
Build exercises
Build a Requirements-to-Architecture Planner
2.1 · Beginner · 40 minutes
- Classify business statements as functional or non-functional requirements.
- Identify performance, scalability, security, and cost constraints.
- Convert vague requirements into measurable acceptance criteria.
- Map requirements to architecture considerations.
Write the life cycle for one Claude job
2.2 · Beginner · 30 minutes
- Where requirements end and design starts.
- What verification has to show.
- Which signals operation watches.
- How a model change re-enters the cycle.
Classify six calls: real time, stream, batch, or cache
2.3 · Intermediate · 35 minutes
- Who stores the conversation.
- When batch is allowed.
- What streaming does and does not change.
- How to order a cached prompt.
Split a Claude client into reviewable pieces
2.4 · Intermediate · 40 minutes
- Which HTTP failures are retries.
- Where the prompt lives.
- How to test parsing without a live call.
- How to keep a side effect out of the parser.
Draw one feature on two surfaces
2.5 · Intermediate · 40 minutes
- What changes between Claude Code and the API.
- Where untrusted text goes.
- What the schema must contain.
- When a session is thrown away.
Separate guidance, enforcement, and pins
2.6 · Beginner · 30 minutes
- Which file a clone receives.
- What concatenation implies when two files disagree.
- Where a hard prohibition goes.
- What to pin besides the model.