Module E1 of 3 · Exam and certification

Course revision guide

45 min 3 stages distilled 4 figures

The whole course in one place, arranged for revision. Each stage below gives you its figure, the distinctions worth holding in your head, and the fastest routes back into the full material. Skim the figures first, then test yourself against the distinctions: anything you cannot explain from memory points at the stage to revisit.

Digitalisation course visual spine

The three stages name the parts, then build and run the systems, then decide what to build and with whom, which puts strategy last and makes it reachable only once the distinctions and the operating disciplines are in hand.

Foundations names the things. Applied builds and runs them. Strategy decides what to build, with whom, and how value is realised. The spine is the route a learner takes through the course.

Digitalisation course spine: Foundations, Applied, Strategy Three vertical bands stacked top to bottom, one per course stage. Each band has a stage identity card on the left (stage number, name, outcome, source) and that stage's modules as numbered cards arranged in a grid on the right. A red SPINE arrow runs down the right margin showing the route a learner takes from Foundations through Applied to Strategy. STAGE 1 Foundations Name the parts. Distinguishdigitisation,digitalisation,transformation. SOURCE GOV.UK Service Manual MODULE 1 Definitions anddistinctions MODULE 2 Context and drivers MODULE 3 Digital buildingblocks MODULE 4 Data and standards MODULE 5 Platforms, journeys,APIs MODULE 6 Risks and governancebasics STAGE 2 Applied Build and run digitalsystems. Pipelines,integration, capabilitymaps, SRE. SOURCE TOGAF Standard 10 MODULE 7 Data pipelines andmedallion MODULE 8 Analytics,measurement, control MODULE 9 APIs and integration MODULE 10 Capability maps, valuestreams, TOGAF MODULE 11 Operations,observability, SRE STAGE 3 Strategy Decide what to build, withwhom, and how value isrealised. SOURCE MSP 5th edition MODULE 12 Strategy, roadmaps,target operatingmodels MODULE 13 Data sharing and trustframeworks MODULE 14 Platforms, ecosystems,vendor management MODULE 15 Measurement, risk,legacy, change SPINE

Stage 1: Telling the three words apart, and the building blocks underneath them

Classify a digital change scenario

The medium test, the work-loop test and the operating-model test run in order and each NO ends the walk at a named classification, so a change is digitisation or digitalisation by the test it fails rather than by the label its business case uses.

Three yes-or-no checkpoints classify any change in seconds. The first no fixes the answer; the test cannot accidentally over-claim transformation. Gartner IT Glossary; Rogers (2016).

Three checkpoints that classify any digital change Three cards in a horizontal chain. Each card splits into two zones. The top white or red-soft zone carries the test name, a QUESTION block, and the YES evidence. The bottom red-soft zone carries the classification that the test yields on NO. Two if-yes arrows link Step 1 to Step 2 to Step 3. Card 2 is emphasised because the work-loop test is the inflection point between digitisation and digitalisation. CLASSIFY ANY DIGITAL CHANGE IN THREE TESTS STEP 1 Gartner Medium test QUESTION Did the information move frompaper, tape, or analogue todigital file? IF NO stops here Not yet a digital change IF YES The medium has changed. Continue to Step 2. STEP 2 Gartner Work-loop test QUESTION Did the work itself change:automation, decision flow,real-time data? IF NO Gartner Digitisation IF YES The loop has changed. Continue to Step 3. STEP 3 Rogers (2016) Operating-model test QUESTION Did the value, the revenue, orthe governance change? IF NO Gartner Digitalisation IF YES Digital transformation. New model, new evidence. if yes if yes

Hold these distinctions

  • Digitisation converts the medium, digitalisation redesigns the work around digital data, and digital transformation changes the operating model and the proposition
  • AI adoption is an accelerant that acts at all three levels rather than a fourth level above them
  • Infrastructure, platform and software as a service differ in where the boundary of provider responsibility sits, not in how modern they are
  • Master data governs the shared entities an organisation describes; reference data governs the controlled lists it describes them with, and they need different owners
  • IT governance runs the assets, data governance decides ownership and permitted use, and digital governance decides which services exist and who answers for them
  • Data protection by design under the UK GDPR and WCAG 2.2 AA under the 2018 accessibility regulations are design-time legal duties, not launch-time quality checks
Full stage summaryScenario practice

Stage 2: Making data move, integrate and stay observable once it is live

Medallion architecture

Each of the four layers carries a contract underneath it, lineage recorded at source, schema and timestamp at bronze, published quality SLAs at silver, owner and semantics in the catalogue at gold, so a layer that has only been renamed has not earned its place.

Medallion is a recommended pattern, not a universal requirement; the value comes from the per-layer contract, not the labels. Databricks medallion guidance; DAMA-DMBOK 2; W3C PROV-DM.

Medallion architecture as four contract-bound layers Four stage cards left to right: Source, Bronze, Silver, Gold. Each card splits into an upper zone naming what the layer holds and a red-soft CONTRACT zone underneath naming the obligation the layer must meet. Silver emphasised because conformance is the layer where quality SLAs become explicit. Arrows between cards carry the transform name (capture, cleanse and conform, curate for use case). MEDALLION: EACH LAYER EARNS ITS PLACE BY MEETING THE CONTRACT UNDER IT STAGE 1 Source RAW PRODUCER Operational systems andexternal feeds. CONTRACT Captured as-is, lineagerecorded. STAGE 2 Bronze INGESTED COPY Schema-on-read landingzone. CONTRACT Schema, timestamp,source recorded. STAGE 3 Silver CONFORMED Cleaned, joined,deduplicated. CONTRACT Quality SLAs publishedper dataset. STAGE 4 Gold DECISION-READY Curated for one specificuse case. CONTRACT Owner, SLAs, semanticsin catalogue. capture cleanse and conform curate for use case

Hold these distinctions

  • Bronze preserves raw arrivals for replay, silver holds conformed data with the rules recorded, and gold holds products shaped for consumption
  • ETL controls what reaches the warehouse and needs the questions known in advance; ELT keeps the raw record for unasked questions and pays for it in storage and compute
  • A performance indicator measures how well something is done, a risk indicator warns before it goes wrong, and a vanity metric changes no decision at all
  • A capability is what an organisation can do, a process is one way of doing it, and a function is a group of people, so a capability map that mirrors the org chart is drawn wrong
  • Metrics aggregate cheaply for alerting, logs reconstruct a single event, and traces are the only signal that explains where time went across services
  • Retrieval fixes missing or changing knowledge, fine-tuning fixes form and task shape, and prompting is the reversible first move before either
  • DevOps Research and Assessment measures software delivery; the Digital Operational Resilience Act regulates European Union financial entities, and the shared acronym is a trap
Full stage summaryScenario practice

Stage 3: Sequencing a roadmap, and holding trust when the work leaves your organisation

12 month roadmap with dependencies

Each bar ends in a gate naming its evidence, quality SLAs live, two services migrated, auth and limits enforced, and dashed arrows chain only some, data foundations to platform v1 to the gateway and self-service, then legacy retirement, so a slipped gate moves the bars behind.

A roadmap is sequenced commitments with evidence gates, not a list of wishes. Each bar's right edge is the next bar's left edge for a reason. GOV.UK Service Manual; Kotter (2012); DORA.

Twelve-month roadmap with evidence gates and dependencies A Gantt-style chart over four quarters with six initiative bars. Each bar shows the initiative span and a red GATE stripe at its right edge stating the evidence required to close. Dashed dependency arrows connect each gate to the start of the next initiative that depends on it (data foundations -> platform v1 -> API gateway and self-service; self-service -> legacy retirement). Measurement loop runs across all four quarters as the continuous evidence stream. INITIATIVEQ1Q2Q3Q4 Data foundations GATE Quality SLAs live Platform v1 GATE Two services migrated API gateway GATE Auth and limitsenforced Self-service tier GATE First-week onboarding works Legacy retirement GATE Two systemsretired Measurement loop GATE Quarterly reviews running Dashed arrows are dependencies; the next bar cannot start until the previous bar's gate passes.

Hold these distinctions

  • Now is funded and staffed, next is gated on a stated dependency, and later is a direction that has not earned a date
  • Project funding buys a scope and disbands the team; product funding sustains a team against an outcome and re-decides the level each cycle
  • A platform is an internal product that has to be worth choosing; a portal is a place to find things, and calling a portal a platform changes nothing
  • Recognised legitimate interests removes the balancing test only for the purposes the Data (Use and Access) Act 2025 lists; everything else keeps it
  • The Cyber Security and Resilience Bill reforms the UK Network and Information Systems Regulations 2018 and is not an implementation of NIS2
  • The Digital Operational Resilience Act is European Union financial-sector law and shares only an acronym with the DevOps delivery research
  • Under Data Best Practice a dataset is presumed open and each restriction must be justified against a named harm, applied as narrowly as the harm allows
Full stage summaryScenario practice

Exam technique for the two papers

The Foundation paper is 40 single-answer questions in 60 minutes, closed book, and it tests precise recall. This course rewards holding definitions apart that ordinary usage blurs, so revise the distinctions first: digitisation against digitalisation, an API against an integration, a capability against an org unit, a metric against a target. Most wrong answers here are the right answer to the neighbouring question.

The options are written so that measuring them does not help. The correct answer is as often the short one as the long one, and no option is there to be eliminated for being obviously silly, so eliminate on meaning rather than on shape. Read the stem twice: a single qualifying word usually decides which of two defensible options is being asked for.

The Practitioner paper is 8 workplace scenarios in 90 minutes, open book, scored five, three, one and zero. Rank the options rather than hunting a single right answer. In this domain the five-point answer usually changes how the work is done rather than buying a tool for it, and it names who owns the outcome afterwards. The three-point answer is often a genuine improvement that leaves the old process untouched underneath. Use the reference panel to confirm a standard or a date, not to learn the topic inside 90 minutes.

The primary sources behind the course

Version-sensitive claims across the course anchor to primary, dated sources, and every stage summary cites the ones its teaching rests on. They are collected here so revision starts from the authority rather than from a summary of it.

When the distinctions hold from memory and the figures feel obvious, you are ready to drill the papers and then sit the mocks.

Start the exam practiceGo straight to the mocks