A city IT team is hardening two workloads: a public static website for park permits and a private database holding citizen payment records. Which control pairing best matches exposure and data sensitivity?
Select an answer to reveal the explanation.
Short Explanation
Think of the park-permits site like a storefront on Main Street and the payment database like the vault in the back. The storefront can use a CDN and WAF to soak up junk traffic; the vault stays off the public street with tight NSG rules and no public IP. Same city, totally different exposure.
Full Explanation
Public static content is commonly protected at the edge with a content delivery network and web application firewall to absorb volumetric noise and common web attacks. Sensitive databases should remain on private networks, reachable only through controlled paths, with network security groups or equivalent filters and without a public IP. Matching controls to exposure and data sensitivity is a core cloud security practice rather than applying one posture to every workload.