AZ-500 Case Study 02
This is a case study. Case studies are not timed separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided.
To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other questions in this case study.
Contoso, Ltd. is a consulting company that has a main office in Montreal and two branch offices in Seattle and New York.
The company hosts its entire server infrastructure in Azure.
Contoso has two Azure subscriptions named Sub1 and Sub2. Both subscriptions are associated to an Azure Active Directory (Azure AD) tenant named contoso.com.
Contoso.com contains the users shown in the following table.
Name | City | Role |
User1 | Montreal | Global administrator |
User2 | MONTREAL | Security administrator |
User3 | London | Privileged role administrator |
User4 | Ontario | Application administrator |
User5 | Seattle | Cloud application administrator |
User6 | Seattle | User administrator |
User7 | Sydney | Reports reader |
User8 | Sydney | None |
User9 | Sydney | Owner |
Contoso.com contains the security groups shown in the following table.
Name | Membership type | Dynamic membership rule |
Group1 | Dynamic user | user.city -contains “ON” |
Group2 | Dynamic user | user.city -match “*on” |
Sub1 contains six resource groups named RG1, RG2, RG3, RG4, RG5, and RG6.
User9 creates the virtual networks shown in the following table.
Name | Resource group |
VNET1 | RG1 |
VNET2 | RG2 |
VNET3 | RG3 |
VNET4 | RG4 |
Sub1 contains the locks shown in the following table.
Name | Set on | Lock type |
Lock1 | RG1 | Delete |
Lock2 | RG2 | Read-only |
Lock3 | RG3 | Delete |
Lock4 | RG3 | Read-only |
Sub1 contains the Azure policies shown in the following table.
Policy definition | Resource type | Scope |
Allowed resource types | networkSecurityGroups | RG4 |
Not allowed resource types | virtualNetworks/subnets | RG5 |
Not allowed resource types | networkSecurityGroups | RG5 |
Not allowed resource types | virtualNetworks/virtualNetworkPeerings | RG6 |
Sub2 contains the virtual networks shown in the following table.
Name | Subnet |
VNetwork1 | Subnet11, Subnet12, and Subnet13 |
VNetwork2 | Subnet21 |
Sub2 contains the virtual machines shown in the following table.
Name | Network interface | Application Security group | Connected to |
VM1 | NIC1 | ASG1 | Subnet11 |
VM2 | NIC2 | ASG2 | Subnet11 |
VM3 | NIC3 | None | Subnet12 |
VM4 | NIC4 | ASG1 | Subnet13 |
VM5 | NIC5 | None | Subnet21 |
All virtual machines have public IP addresses and the Web Server (IIS) role installed. The firewalls for each virtual machine allow ping requests and web requests.
Sub2 contains the network security groups (NSGs) shown in the following table.
Name | Associated to |
NSG1 | NIC2 |
NSG2 | Subnet11 |
NSG3 | Subnet13 |
NSG4 | Subnet21 |
NSG1 has the inbound security rules shown in the following table.
Priority | Port | Protocol | Source | Destination | Action |
65000 | Any | Any | VirtualNetwork | VirtualNetwork | Allow |
65001 | Any | Any | AzureLoadBalancer | Any | Allow |
65500 | Any | Any | Any | Any | Deny |
NSG2 has the inbound security rules shown in the following table.
Priority | Port | Protocol | Source | Destination | Action |
100 | 80 | TCP | Internet | VirtualNetwork | Allow |
65000 | Any | Any | VirtualNetwork | VirtualNetwork | Allow |
65001 | Any | Any | AzureLoadBalancer | Any | Allow |
65500 | Any | Any | Any | Any | Deny |
NSG3 has the inbound security rules shown in the following table.
Priority | Port | Protocol | Source | Destination | Action |
100 | Any | TCP | ASG1 | ASG1 | Allow |
150 | Any | Any | ASG2 | VirtualNtwork | Allow |
200 | Any | Any | Any | Any | Denny |
65000 | Any | Any | VirtualNetwork | VirtualNetwork | Allow |
65001 | Any | Any | AzureLoadBalancer | Any | Allow |
65500 | Any | Any | Any | Any | Deny |
NSG4 has the inbound security rules shown in the following table.
Priority | Port | Protocol | Source | Destination | Action |
100 | Any | Any | Any | Any | Allow |
65000 | Any | Any | VirtualNetwork | VirtualNetwork | Allow |
65001 | Any | Any | AzureLoadBalancer | Any | Allow |
65500 | Any | Any | Any | Any | Deny |
NSG1, NSG2, NSG3, and NSG4 have the outbound security rules shown in the following table.
Priority | Port | Protocol | Source | Destination | Action |
65000 | Any | Any | VirtualNetwork | VirtualNetwork | Allow |
65001 | Any | Any | Any | Internet | Allow |
65500 | Any | Any | Any | Any | Deny |
Contoso identifies the following technical requirements:
- Deploy Azure Firewall to VNetwork1 in Sub2.
- Register an application named App2 in contoso.com.
- Whenever possible, use the principle of least privilege.
- Enable Azure AD Privileged Identity Management (PIM) for contoso.com.
