The booking database, the Active Directory, and the file storage of Nordlicht Reisen GmbH, a fictional travel agency, are still in its own data center in Hamburg (G-03, G-04, G-06). On the way to Azure, Hamburg and Azure talk to each other for months: databases are synchronized, servers sign in to the on-premises Active Directory, offices access files. This lesson chooses the connection and plans how names are resolved across it.
Prior knowledge: AZ-104, lesson 4.2 explains peering, routes, and gateway transit; lesson 6.1 of this course covers hub-and-spoke and the choice between your own hub and Virtual WAN; AZ-104, lesson 4.5 covers Azure DNS and private zones; lesson 1.3 of this course covers access to on-premises resources with Application Proxy, Entra Private Access, or VPN. None of that is repeated here. What is new is the choice of the line and the question of how names cross it. Private endpoints, firewall, and performance optimization belong to lesson 6.3.
The requirement
All numbers are assumptions of the exercise, not measured. G-01 to G-10 apply; the data center keeps the addresses 192.168.0.0/16, and Azure plans 10.0.0.0/8.
| No. | Requirement | Type | Metric | Weight | Source |
|---|---|---|---|---|---|
| 6.2-01 | Hamburg and Azure are connected privately and encrypted. | R | traffic not open over the internet | Must | Data protection |
| 6.2-02 | The connection carries the synchronization of the booking database and file access (G-03, G-06). | Q | sustained 600 Mbit/s, peak 900 Mbit/s; assumption | Must | Operations |
| 6.2-03 | The failure of a device or a zone on the Azure side does not break the connection. | Q | no interruption on a failure; assumption | Must | Management |
| 6.2-04 | The failure of the line in Hamburg is absorbed by a second path. | Q | second path through a different provider; assumption | Should | Management |
| 6.2-05 | The connection is operational in six weeks. | R | 6 weeks; assumption | Should | Management |
| 6.2-06 | Response times of the database between Hamburg and Azure vary little. | Q | variation at most 10 ms; assumption | Could | Operations |
| 6.2-07 | Names of the on-premises directory (nordlicht.example.com) resolve in Azure, and Azure names resolve in Hamburg (G-04). |
F | both directions | Must | Operations |
| 6.2-08 | The address spaces of Hamburg and Azure do not overlap. | R | no overlap | Must | Operations |
| 6.2-09 | Costs fall before operating comfort, not before availability (ranking from lesson 0.2). | K | ranking | Could | Management |