AZ-305 Practice Question 89: Application Security Groups Segmentation
Microsoft Azure Solutions Architect Expert (AZ-305) · Test 9 · question 9 of 10
A three-tier application runs in a single virtual network subnet: web, application, and database virtual machines are mixed together on the same subnet because of an earlier lift-and-shift, and the company does not want to re-architect the subnet layout right now. The network design must allow only the web tier to receive inbound traffic from the internet, allow only the application tier to receive traffic from the web tier on its application port, and allow only the database tier to receive traffic from the application tier on its database port, all while the VMs keep scaling in and out and new VMs are added to a tier without anyone editing firewall rules by IP address each time.
What should you recommend?
Show answer and explanation
Answer:
Application security groups let you group network interfaces by role, such as web, application, or database, regardless of subnet, and network security group rules can then use those groups as the source or destination instead of hardcoded IP addresses or ranges. Adding or removing a VM only means adding or removing its NIC from the group, so scaling in and out never requires editing a rule, and the three tiers can be enforced even while sharing one subnet.
Option A operates at the subnet level, so it cannot separate web, application, and database traffic when all three tiers share the same subnet.
Option C adds a centralized firewall and routing, which is more infrastructure than the requirement calls for and still needs some way to identify which VMs belong to which tier; it does not remove the need for per-tier grouping and adds an inline appliance the scenario does not ask for.
Option D reintroduces exactly the manual, per-IP rule maintenance the requirement says to avoid, and giving every VM a public IP also increases the attack surface unnecessarily.
Reference: Application security groups