The booking database of Nordlicht Reisen GmbH runs in Azure (lesson 2.1). Now sales wants many heavy reports in the morning, on campaign days the load is ten times as high, 400 external users at the partner hotels may see only their own bookings, and the table holds passport numbers that nobody in IT should read in plain text either. The exam calls this: recommend a solution for database scalability and recommend a solution for data protection. Both are selection questions with limits.
Prior knowledge. Service, tier and compute form are in lesson 2.1. K3 shows backup and restore in lesson 3.6.5, hashing, encrypting and signing in lesson 3.3.6, keys in the vault in lesson 1.4. High availability and disaster recovery of the data come in lessons 3.1, 3.2 and 3.4 and are only touched on here. What is new is which path fits which requirement.
The requirement
All numbers are assumptions of the task.
| Requirement | Source | Measure (assumption) |
|---|---|---|
| Reports must not slow down bookings | Sales | 40 heavy queries at the same time, 7 to 9 a.m. |
| Ten times the load on campaign days | Marketing | dates known two weeks ahead |
| Hotels see only their own bookings | Partner contracts | about 400 external users, access through the interface |
| Passport numbers never in plain text in IT | Data protection | database administrators don't see them either |
| Support sees email addresses masked | Data protection | only the last characters |
| The data protection officer controls the key of the database encryption | Data protection | key from lesson 1.4 |
| Restore to any point in time of the last weeks | Operations | 35 days |
| Keep booking receipts for a long time | Controlling | ten years (the tax advisers settle it with binding effect) |
| Log accesses | Audit | all administrator accesses traceable |