Module 15 study plan
Module 15 · Give each week a clear focus.
8 weeks · About 6 hours per week
Fundamentals and Core Concepts
Define in your own words every core term in Domain 1 and group them into a one-page concept map that shows how the terms relate.
Explain the module's overall architecture from memory on a blank sheet, then compare it against your notes and correct every gap.
Write five original practice questions on Domain 1 fundamentals and answer them one week later without notes.
Your checkpoint
A one-page Domain 1 concept map plus a 300-word plain-language summary of the core model, checked against your source notes.
Fundamentals and Core Concepts & Implementation and Configuration
Trace a single end-to-end request or workflow through the module and annotate each step with the configuration setting that controls it.
List every configuration parameter mentioned in Domain 1 material and state its default, valid range, and effect.
Set up a working sandbox instance and change three parameters, recording the before/after behavior.
Your checkpoint
A configuration parameter table (parameter, default, valid values, effect) with at least 15 entries and three verified sandbox experiments.
Implementation and Configuration
Implement the standard baseline configuration in your sandbox from a clean install, timing yourself.
Configure two non-default scenarios (for example high-availability or restricted access) and document the differences from baseline.
Break your own configuration three ways and record the exact error each break produces.
Your checkpoint
A reproducible baseline setup script or checklist that rebuilds your sandbox from scratch in under 45 minutes, plus a log of three induced failures.
Planning and Design & Implementation and Configuration
Translate five stated business requirements into design decisions, naming the Domain 3 settings each decision drives.
Draft a sizing and capacity estimate for a small deployment and justify each number with a stated assumption.
Review your design against the baseline from week 3 and list every place the design departs from it and why.
Your checkpoint
A two-page design document covering requirements, chosen architecture, sizing assumptions, and the configuration mapping table.
Operations, Monitoring, and Maintenance
Identify the key health and performance indicators for the module and state a normal range and an alert threshold for each.
Build a monitoring view or dashboard in your sandbox that surfaces those indicators.
Run a routine maintenance task end to end (backup, log rotation, or patch cycle) and record the steps and timing.
Your checkpoint
A monitoring and maintenance runbook with at least eight indicators, thresholds, and one completed maintenance cycle logged with timestamps.
Operations, Monitoring, and Maintenance & Troubleshooting and Governance
Inject four realistic faults into your sandbox and diagnose each using only logs and metrics, recording time to resolution.
Write a triage decision tree that routes a symptom to the most likely cause in three steps or fewer.
Map each fault you injected to the governance control that would have prevented or detected it.
Your checkpoint
A troubleshooting log of four faults with symptom, evidence, root cause, fix, and time to resolution, plus a one-page triage tree.
Troubleshooting and Governance & Planning and Design
Write the governance section of your design document: access control, change management, audit, and data handling.
Perform a change-review exercise on your own week 4 design and list the risks you missed.
Answer 40 mixed practice questions across all five domains under timed conditions and tag each miss by domain.
Your checkpoint
A governance addendum to the design document plus a scored 40-question practice set with every miss tagged and explained.
Fundamentals and Core Concepts & Planning and Design & Implementation and Configuration & Operations, Monitoring, and Maintenance & Troubleshooting and Governance
Re-drill every missed question from weeks 1 through 7 until you can explain the correct answer without notes.
Rebuild the sandbox from your week 3 checklist and complete one fault injection from memory.
Take two full-length timed practice exams and compare domain-level scores between them.
Your checkpoint
A final readiness sheet showing domain-level practice scores, remaining weak areas, and a one-page personal cheat sheet.
Milestones
Week 2: You can explain the core model and trace one end-to-end workflow without notes, and your parameter table has at least 15 verified entries.
Week 4: Your sandbox rebuilds from your own checklist in under 45 minutes, and your design document maps every requirement to a concrete configuration decision.
Week 6: You diagnosed four injected faults from logs and metrics alone, with a median time to resolution under 20 minutes.
Week 8: Two full-length timed practice exams both score at or above your target pass margin, with no domain below 70 percent.