🇺🇸 Microsoft Certified: Azure Administrator Associate · subject

Microsoft Certified: Azure Administrator Associate Configure Load Balancing and Network Monitoring Syllabus

The Configure Load Balancing and Network Monitoring syllabus for Microsoft Certified: Azure Administrator Associate in full: 3 chapters, 12 topics and 1 sub-topic, every one listed below, plus 51 Configure Load Balancing and Network Monitoring flashcards with answers.

3Chapters
12Topics
1Sub-topics
51Flashcards

Configure Load Balancing and Network Monitoring syllabus: all 3 chapters

Expand any chapter to see its topics and sub-topics.

  1. Azure Load Balancer

    4 topics
    • Public vs internal load balancers
    • Load balancer SKUs (Basic vs Standard)
    • Backend pools and health probes
    • Load balancing and inbound NAT rules
      • Session persistence and distribution modes
  2. Application Gateway

    4 topics
    • Layer 7 load balancing concepts
    • Listeners, rules, and backend pools
    • Path-based and multi-site routing
    • Web Application Firewall (WAF) integration
  3. Network Monitoring and Troubleshooting

    4 topics
    • Network Watcher capabilities
    • Connection troubleshoot and IP flow verify
    • NSG flow logs and traffic analytics
    • Effective routes and next hop diagnostics

Microsoft Certified: Azure Administrator Associate Configure Load Balancing and Network Monitoring flashcards — 51 questions with answers

  1. What is the difference between a public and an internal Azure Load Balancer?

    A public load balancer has a public frontend IP and balances inbound internet traffic to backend VMs; an internal (private) load balancer has a private frontend IP and balances traffic only within a virtual network or from on-premises (e.g., for internal/multi-tier apps).

  2. At which OSI layer does Azure Load Balancer operate, and what protocols does it handle?

    Azure Load Balancer is a Layer 4 (transport) load balancer; it distributes TCP and UDP traffic based on IP address and port, with no awareness of application/HTTP content.

  3. At which OSI layer does Azure Application Gateway operate?

    Application Gateway is a Layer 7 (application) load balancer; it makes routing decisions based on HTTP/HTTPS attributes such as URL path, host header, and cookies.

  4. Name the two SKUs of Azure Load Balancer.

    Basic and Standard.

  5. What is the default availability/SLA difference between Basic and Standard Load Balancer?

    Standard Load Balancer provides a 99.99% SLA; Basic Load Balancer has no SLA.

  6. How many instances can a backend pool hold in Basic vs Standard Load Balancer?

    Basic supports up to 300 instances in the backend pool; Standard supports up to 1000 instances.

  7. What is the default security posture of a Standard Load Balancer regarding NSGs?

    Standard Load Balancer is secure by default (closed): inbound traffic is blocked unless explicitly allowed by a Network Security Group. Basic Load Balancer is open by default.

  8. Which Load Balancer SKU supports Availability Zones?

    Only the Standard SKU supports zone-redundant and zonal frontends; Basic does not support Availability Zones.

  9. Are Basic and Standard Load Balancer frontend IP SKUs interchangeable with Public IP SKUs?

    No. A Basic Load Balancer requires a Basic SKU public IP, and a Standard Load Balancer requires a Standard SKU public IP; the SKUs must match.

  10. What is a backend pool in Azure Load Balancer?

    A backend pool is the group of backend resources (VMs, VM scale set instances, or IP addresses) that receive distributed traffic from the load balancer.

  11. What is the purpose of a health probe in Azure Load Balancer?

    A health probe checks the health of backend instances; the load balancer only sends new flows to instances that report healthy, and stops sending to instances that fail the probe.

  12. What probe protocols are supported by Azure Load Balancer health probes?

    TCP, HTTP, and HTTPS (HTTPS only on Standard SKU).

  13. For an HTTP/HTTPS health probe, what response indicates a healthy backend?

    An HTTP 200 OK response returned within the probe timeout indicates the instance is healthy.

  14. What happens to existing TCP connections when a health probe marks an instance as unhealthy (Standard LB)?

    On Standard Load Balancer, new connections are not sent to the unhealthy instance, but existing established TCP connections continue (default behavior); with 'all probes down' configuration, all connections including UDP can be reset.

  15. What does a load balancing rule define in Azure Load Balancer?

    A load balancing rule maps a frontend IP and port to a backend pool and backend port, associating it with a health probe to distribute incoming traffic across the pool.

  16. What is an inbound NAT rule in Azure Load Balancer?

    An inbound NAT rule forwards traffic from a specific frontend IP/port to a specific port on a single backend instance (e.g., RDP/SSH to one VM), rather than distributing across the pool.

  17. What is the key difference between a load balancing rule and an inbound NAT rule?

    A load balancing rule distributes traffic across all healthy instances in the backend pool, while an inbound NAT rule directs traffic to one specific backend instance/port.

  18. What is the default load distribution mode (session persistence) of Azure Load Balancer?

    Five-tuple hash: source IP, source port, destination IP, destination port, and protocol; this distributes flows across instances without session affinity.

  19. What session persistence options does Azure Load Balancer support besides the default five-tuple?

    Source IP affinity (two-tuple: source IP + destination IP) and source IP + protocol affinity (three-tuple).

  20. What is the purpose of HA Ports in Standard Load Balancer?

    HA Ports is a load balancing rule that balances ALL TCP and UDP flows on all ports simultaneously (port 0), commonly used for network virtual appliances (NVAs) in high availability scenarios.

Show the other 31 Configure Load Balancing and Network Monitoring flashcards
  1. What are the three main components of an Application Gateway request flow?

    Listeners (receive incoming requests), rules (define how requests are routed), and backend pools (the targets that serve the request).

  2. What is a listener in Application Gateway?

    A listener is a logical entity that checks for incoming connection requests using a configured protocol, port, host, and IP address; it determines whether a request is accepted.

  3. What are the two types of listeners in Application Gateway?

    Basic listeners (route based only on port/protocol) and multi-site listeners (route based on the host header/domain name to support multiple sites on one gateway).

  4. What is path-based routing in Application Gateway?

    Path-based (URL path) routing directs requests to different backend pools based on the URL path of the request (e.g., /images/* to one pool, /video/* to another) using a path-based routing rule with a URL path map.

  5. What is multi-site routing in Application Gateway?

    Multi-site routing hosts multiple web applications/domains on the same Application Gateway, routing requests to different backend pools based on the host header (e.g., contoso.com vs fabrikam.com).

  6. What is a Web Application Firewall (WAF) in the context of Application Gateway?

    WAF is a feature of Application Gateway that provides centralized protection of web apps against common exploits such as SQL injection and cross-site scripting (XSS), based on OWASP core rule sets.

  7. Which OWASP rule set versions does Azure WAF support?

    Azure WAF supports OWASP Core Rule Set (CRS), including versions such as CRS 3.2, 3.1, and 3.0 (and newer), which define managed rules against common attacks.

  8. What are the two modes of Azure Web Application Firewall?

    Detection mode (monitors and logs threats but does not block) and Prevention mode (blocks intrusions and attacks detected by the rules).

  9. On which Application Gateway tier is WAF available?

    WAF requires the WAF or WAF_v2 (Standard_v2-based) SKU/tier of Application Gateway; it is not available on the basic Standard tier.

  10. What is Azure Network Watcher?

    Network Watcher is a regional service providing tools to monitor, diagnose, view metrics, and enable/disable logging for resources in an Azure virtual network.

  11. List four diagnostic tools provided by Azure Network Watcher.

    IP flow verify, Next hop, Connection troubleshoot, Connection monitor, Packet capture, VPN troubleshoot, NSG flow logs, and Effective security rules (any four).

  12. What does the IP flow verify tool in Network Watcher do?

    IP flow verify checks whether a packet is allowed or denied to/from a VM based on Network Security Group rules, and identifies the specific NSG rule responsible for the decision.

  13. What inputs does IP flow verify require?

    Direction (inbound/outbound), protocol (TCP/UDP), local IP and port, and remote IP and port for the target VM.

  14. What does the Next hop tool in Network Watcher determine?

    Next hop determines how traffic from a VM is routed to a destination IP, returning the next hop type (e.g., Internet, VirtualAppliance, VirtualNetworkGateway, None) and the route table that produced it, useful for diagnosing routing issues.

  15. What does Connection troubleshoot in Network Watcher do?

    Connection troubleshoot tests and diagnoses a connection between a source (VM) and a destination (VM, FQDN, URI, or IP), returning reachability status, latency, hop-by-hop topology, and any issues (NSG, route, or CPU/memory).

  16. What is the difference between Connection Monitor and Connection troubleshoot?

    Connection troubleshoot performs a one-time, on-demand connectivity check, while Connection Monitor provides continuous, ongoing monitoring of connectivity over time with alerting.

  17. What are NSG flow logs in Network Watcher?

    NSG flow logs record information about IP traffic flowing through a Network Security Group, capturing allowed and denied flows; logs are stored in an Azure Storage account in JSON format.

  18. Where are NSG flow logs stored?

    In an Azure Storage account (as JSON), from which they can be analyzed manually or ingested by Traffic Analytics.

  19. What are the two versions of NSG flow logs and how do they differ?

    Version 1 logs basic 5-tuple flow and allow/deny decisions; Version 2 adds throughput information (bytes and packets transmitted in each direction) and flow state.

  20. What is Traffic Analytics in Azure?

    Traffic Analytics is a cloud-based solution that processes NSG flow logs to provide visibility into network activity, identify hotspots, security threats, traffic flow patterns, and usage across the Azure environment; it uses a Log Analytics workspace.

  21. What prerequisite is required to use Traffic Analytics?

    NSG flow logs must be enabled, and a Log Analytics workspace must be configured to store and process the analyzed data.

  22. What does the Effective routes feature show for a VM?

    Effective routes displays the combined/aggregated routes applied to a VM's network interface, including system (default) routes, BGP routes, and user-defined routes (UDRs), showing which route actually applies.

  23. What does the Effective security rules feature show?

    Effective security rules show the aggregated NSG rules applied to a network interface, combining subnet-level and NIC-level NSG rules to reveal the net effect on traffic.

  24. What are the possible next hop types returned by the Next hop diagnostic?

    Internet, VirtualAppliance, VirtualNetworkGateway, VnetLocal, VnetPeering, VirtualNetworkServiceEndpoint, and None (traffic dropped).

  25. When Next hop returns 'None', what does it indicate?

    It indicates there is no valid route for the destination (often due to a user-defined route directing traffic to 'None'), so the traffic is dropped/blackholed.

  26. Can Basic Load Balancer backend pools span across availability sets or virtual networks?

    No. Basic Load Balancer backend members must be in a single availability set or VM scale set; Standard Load Balancer backend members can be any VM in a single virtual network (more flexible).

  27. What type of public IP does Standard Load Balancer use, and is it zone-redundant?

    Standard Load Balancer uses a Standard SKU public IP, which is created as zone-redundant by default (can also be zonal).

  28. What is the purpose of outbound rules in Standard Load Balancer?

    Outbound rules provide explicit, configurable SNAT (source NAT) for backend instances to reach the internet, letting you define outbound port allocation and which frontend IPs are used.

  29. What is a key cost difference between Basic and Standard Load Balancer?

    Basic Load Balancer is free (no charge), while Standard Load Balancer is charged based on the number of rules configured and the volume of data processed.

  30. Which load balancing solution should you choose for SSL/TLS termination and cookie-based session affinity?

    Application Gateway (Layer 7), because it supports SSL/TLS termination, end-to-end SSL, and cookie-based session affinity; Azure Load Balancer (Layer 4) cannot do these.

  31. What does Connection Monitor measure between endpoints?

    Connection Monitor measures connectivity, round-trip latency, and percentage of packet loss between source and destination endpoints continuously, and can alert when thresholds are breached or topology changes.

Microsoft Certified: Azure Administrator Associate Configure Load Balancing and Network Monitoring FAQ

What is in the Microsoft Certified: Azure Administrator Associate Configure Load Balancing and Network Monitoring syllabus?

Microsoft Certified: Azure Administrator Associate Configure Load Balancing and Network Monitoring is split into 3 chapters: Azure Load Balancer, Application Gateway and Network Monitoring and Troubleshooting. Together they contain 12 topics and 1 sub-topic.

How many chapters are in Microsoft Certified: Azure Administrator Associate Configure Load Balancing and Network Monitoring?

3 chapters, containing 12 topics and 1 sub-topic. The largest chapter is Azure Load Balancer, with 4 topics.

Are there flashcards for Microsoft Certified: Azure Administrator Associate Configure Load Balancing and Network Monitoring?

Yes — a 51-card Configure Load Balancing and Network Monitoring deck, printed in full in the flashcards section of this page and available in the Examius app with spaced repetition. The free plan covers one exam of your choice, including its flashcards; Examius Pro, a one-time purchase, unlocks every other exam and deck.