Domain 2 – Applications and Integration (33.1%) – Dominant domain

6 lessons, each ending with a practice scenario (Pro)

Log in to save your progress.

1. ✓2.1 — Understanding RequirementsRequirements sit on three layers: Business, Functional, Infrastructure / non-functional; The Derivation Chain: Business → functional → infrastructure. Skip a layer, or run backwards, and a requirement has nothing to trace to.Scenario: Pro
2. ✓2.2 — Systems Life CycleCanonical phases and what they own: Planning and requirements; Design; Development; Testing — designing the regression eval set (derived from requirements, not reverse-engineered from incidents); Implementation and deployment — the cutover plan that swaps pilot for production (happens once); Operations and maintenance — standing cost-per-task dashboard, error triage, prompt fixes, plan for moving off a deprecated model (recurs for the life of the system); Retirement — switching off and disposing of logs; data disposition is part of this phase.Scenario: Pro
3. ✓2.3 — Claude API MechanicsThe Messages API is how an application talks to Claude. A request needs exactly three parameters: model, maxtokens, messages. Everything else is optional. The API is stateless: the application resends the transcript every turn.Scenario: Pro
4. ✓2.4 — Software Engineering FoundationsSerial loop wastes the rate limit. Unbounded fan-out trips the token-bucket limiter and turns the run into a 429 storm. Correct shape: worker pool or semaphore sized against documented RPM/ITPM/OTPM headroom. Transient failures retried with jittered exponential backoff honouring retry-after.Scenario: Pro
5. ✓2.5 — Claude Application DesignFour design decisions: where instructions live, where untrusted content goes, what contract the output honours, and how sessions are scoped.Scenario: Pro
6. ✓2.6 — Configuration ManagementConfiguration is anything that changes behaviour without being code. Managed exactly like code: version control, review, deployment pipeline.Scenario: Pro