Nordlicht Reisen GmbH, a fictional travel agency, wants to know what its Azure solution should be as a whole. Each lesson of the course answered one question on its own: sign-in, the database, backup, the portal, the move, the network. Now the answers lie side by side. Region, names and tiers agree; at two points, however, requirements truly stand against each other. This project organizes the answers into a decision folder: seven decisions, the list of the two remaining contradictions and how they are resolved, one architecture overview, one Bicep sketch and a review against the pillars of the Well-Architected Framework. It is created on paper. Nothing is deployed, and no command runs against Azure.
Prior knowledge. The project assumes all lessons of modules A1 to A6, plus the template of the requirements sheet from lesson 0.2 and the ADR form from lesson 0.1. The lessons are not repeated here; the folder refers to them by number. How to justify and record decisions is taught in "K4, lesson 4.1.3," how to present an architecture in "K4, lesson 4.1.4" (C4 model), and the review against the Well-Architected Framework in "K4, lesson 4.7.1." The version of this project in the AZ-104 course ("AZ-104, lesson 6.1") deploys an environment instead; here you only design.
What the folder contains
| Part | Content | Where in the solution |
|---|---|---|
| 1 | the shared requirements sheet of the folder (rows M-01 to M-10) | Exercise 1 |
| 2 | seven decisions, each with references to the lessons | Solution 1 |
| 3 | the two contradictions that the lessons deliberately leave open, and their resolution | Solution 1 |
| 4 | the architecture overview | Solution 2 |
| 5 | the shared Bicep sketch | Solution 2 |
| 6 | the review against the five pillars and the open risks | Solution 2 |
The seven decisions cover all four areas of the exam. The assignment is a convention of this course; you may divide them differently as long as each decision has exactly one owner.
| No. | Decision | Area | Lessons |
|---|---|---|---|
| D1 | Identity, access, secrets | Identity, governance, monitoring | 1.2, 1.3, 1.4 |
| D2 | Governance and monitoring | Identity, governance, monitoring | 1.1, 1.5, 1.6 |
| D3 | Data storage | Data storage | 2.1 to 2.5 |
| D4 | Recovery and availability | Business continuity | 3.1 to 3.4 |
| D5 | Compute and application | Infrastructure | 4.1 to 4.7 |
| D6 | Migration | Infrastructure | 5.1 to 5.4 |
| D7 | Network | Infrastructure | 6.1 to 6.4 |