An organization's Azure hierarchy includes a management group named Corp-MG, a subscription named Sales-Sub inside Corp-MG, and a resource group named App-RG inside Sales-Sub. An administrator must implement the following security requirements:
1. Members of a group named Audit-Team must be able to view all resources in Corp-MG, Sales-Sub, and App-RG, but must not be allowed to modify or create any resources outside of App-RG.
2. Members of Audit-Team must also be able to create, start, and delete virtual machines, but only within App-RG.
3. To enforce compliance, no virtual machines deployed within Sales-Sub are permitted to have public IP addresses.
To meet these requirements using the principle of least privilege and native Azure capabilities, which combination of role assignments and governance tools should the administrator configure?
- Assign the Reader role to Audit-Team at the Corp-MG scope, assign the Contributor role to Audit-Team at the App-RG scope, and assign an Azure Policy definition to Sales-Sub that denies virtual machines with public IP addresses.Cevap
- BAssign the Reader role to Audit-Team at the Corp-MG scope, assign the Contributor role to Audit-Team at the App-RG scope, and create a custom Azure RBAC role at the Sales-Sub scope that denies virtual machine deployments containing public IP addresses.
- CAssign the Reader role to Audit-Team at the Corp-MG scope, assign the Reader role to Audit-Team at the Sales-Sub scope, and assign an Azure Policy definition to App-RG that denies virtual machines with public IP addresses.
- DAssign the Contributor role to Audit-Team at the Corp-MG scope, assign the Reader role to Audit-Team at the App-RG scope, and assign an Azure Policy definition to Sales-Sub that denies virtual machines with public IP addresses.