EGATSU-SP study materials
EGATSU-SP study resources

EGATSU-SP study plan

EGATSU-SP · Give each week a clear focus.

8 weeks · About 6 hours per week

Week 1

Fundamentals and Terminology & Design and Architecture

  • Define every core term in Domain 1 in your own words and record each definition in a personal glossary

  • Draw a one-page diagram that maps the major architectural components and how they interact

  • List the five most common trade-offs in design decisions and give a concrete example of each

  • Solve 20 terminology recall questions and log every miss with the reason it was missed

Your checkpoint

A 40-term personal glossary plus a one-page architecture diagram annotated with component responsibilities and interfaces

Week 2

Design and Architecture

  • Compare at least three architecture patterns and document when each is the correct choice

  • Produce a decision matrix that scores candidate designs against scalability, cost, and maintainability

  • Trace how a single requirement propagates into at least two design components

  • Write a short design rationale for a sample scenario that justifies each major choice

Your checkpoint

A 3-page design rationale document with a scored decision matrix for one worked scenario

Week 3

Design and Architecture & Implementation and Configuration

  • Translate one approved design into a build sequence with ordered configuration steps

  • Configure a minimal working environment that reflects the design from week 2

  • Document every configuration parameter and the reason it was set to that value

  • Identify the three configuration settings most likely to cause production incidents

Your checkpoint

A configuration runbook listing every parameter, its value, and its justification, validated by a working build

Week 4

Implementation and Configuration

  • Implement the remaining core configuration items from the runbook without consulting notes

  • Write a repeatable setup script or checklist that another person could follow unaided

  • Reproduce the build from scratch in a clean environment and record every deviation

  • Explain the difference between implementation choices that are reversible and those that are not

Your checkpoint

A clean-environment rebuild completed end to end, with a deviation log showing zero unexplained differences

Week 5

Planning and Requirements Analysis & Implementation and Configuration

  • Convert a vague stakeholder request into testable acceptance criteria

  • Identify missing requirements in a sample brief and write the clarifying questions you would ask

  • Map each acceptance criterion to the implementation element that satisfies it

  • Prioritize requirements using a stated method and defend the ordering in writing

Your checkpoint

A requirements traceability matrix linking each acceptance criterion to its implementation element

Week 6

Testing, Verification, and Quality Assurance

  • Design a test plan that covers functional, integration, and negative cases for the week 3 build

  • Execute the plan and record pass or fail for every case with evidence

  • Write a defect report that states the expected result, actual result, and reproduction steps

  • Verify that every acceptance criterion from week 5 has at least one corresponding test

Your checkpoint

A completed test plan with execution results, defect reports, and a coverage check against all acceptance criteria

Week 7

Operations, Maintenance, and Troubleshooting & Security, Compliance, and Risk Management

  • Write a troubleshooting decision tree for the three most probable failure modes

  • Perform a risk assessment that rates likelihood and impact for at least eight identified risks

  • List the compliance obligations that apply to the scenario and the control that satisfies each

  • Draft an incident response sequence from detection through post-incident review

Your checkpoint

A risk register with rated risks, mapped controls, and an incident response checklist

Week 8

Fundamentals and Terminology & Planning and Requirements Analysis & Design and Architecture & Implementation and Configuration & Testing, Verification, and Quality Assurance & Operations, Maintenance, and Troubleshooting & Security, Compliance, and Risk Management

  • Take two full timed practice exams and record the score per domain

  • Re-study only the two weakest domains and rewrite the glossary entries for any term still unclear

  • Re-derive the architecture diagram from memory and compare it to the week 1 version

  • Build a one-page exam-day reference sheet of formulas, terms, and decision rules

Your checkpoint

A domain-by-domain score report from two timed practice exams plus a one-page final reference sheet

Milestones

Week 2: You can explain the architecture diagram from memory and justify three design trade-offs without notes

Week 4: A clean-environment rebuild succeeds with zero unexplained deviations from the runbook

Week 6: Every acceptance criterion has at least one executed test, and all failures have a written defect report

Week 8: Practice exam scores are at least 80% in every domain, with no domain below 70%