Deploying an Azure key vault to each enterprise-scale landing zone
You have an Azure subscription. You plan to deploy enterprise-scale landing zones based on the Microsoft Cloud Adoption Framework for Azure. The deployment will include a single-platform landing zone for all shared services and three application landing zones that will each host a different Azure application. You need to recommend which resource to deploy to each landing zone. The solution must meet the Cloud Adoption Framework best-practice recommendations for enterprise-scale landing zones. What should you recommend?
Community Votes
73% of anonymous learners picked answer D. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
Azure Key Vault is the security resource recommended in every application landing zone (separate key vaults per environment/region); Azure Firewall and VNet gateways belong to the shared connectivity subscription, not each app landing zone.
In a Cloud Adoption Framework enterprise-scale landing zone design, each application landing zone should include its own Azure Key Vault to store secrets, keys, and certificates isolated per application environment, while shared platform resources such as firewalls and gateways live in the connectivity/network hub.
Choosing Azure Firewall (A) or a VNet gateway (B) — those are shared platform/connectivity resources deployed once in the network hub, not per application landing zone.
Community Discussion (9 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Microsoft Cloud Adoption Framework enterprise-scale landing zone architecture places an Azure Key Vault in each application landing zone (with separate key vaults for each application environment in each region) to isolate and secure secrets, keys, and certificates. This matches the recommendation to deploy a security resource to each landing zone.Why the Other Options Are Wrong
Azure Firewall (A) and VNet gateway (B) are connectivity/network-hub resources deployed once in the shared platform/connectivity subscription, not repeated in every application landing zone. An Azure Private DNS zone (C) is also a shared service typically centralized in the connectivity hub rather than per application landing zone.Community Comment Notes
The community favored D (67 votes). Multiple comments cite the enterprise-scale landing zone documentation showing Azure Key Vault in each application landing zone and separate key vaults per environment, while firewalls/gateways belong to the connectivity subscription.Official Reference
Related Analysis
Practice All SC-100 Questions
Access 110 questions with complete answers and detailed explanations.
View Full SC-100 Practice Test →