AZ-700T00: Designing and Implementing Microsoft Azure Networking Solutions Quiz Questions and Answers
Answer :
Azure Load Balancer (Standard)
Explanation :
Azure Load Balancer (Standard) operates at layer 4 (TCP/UDP), supports millions of requests per second, offers zone-redundancy for high availability, and is designed to handle non-HTTP(S) traffic within a single Azure region. Application Gateway and Front Door handle HTTP(S) at layer 7, and Traffic Manager is DNS-based, not a layer 4 load balancer.
A business needs to direct user traffic across their applications deployed in East US and West Europe for disaster recovery.
Explanation :
Azure Traffic Manager is a DNS-based global traffic distributor, ideal for routing user requests to different regional deployments (e.g., East US and West Europe) for geo-redundancy or disaster recovery. Azure Load Balancer is used for regional load balancing within a virtual network, and Application Gateway is an HTTP(S)-focused, Layer 7 solution.
Reliable, private connectivity that does not traverse the public Internet
Explanation :
Azure ExpressRoute provides private connections that do not traverse the public Internet, offering more reliability, faster speeds, consistent latencies, and higher security than typical Internet connections or VPNs. Traditional VPNs use encrypted tunnels over the Internet, which can be affected by public network conditions.
Azure Monitor is Azure’s primary native service for collecting, analyzing, and visualizing metrics and logs from across resources. Microsoft Defender for Cloud leverages Azure Monitor for security insights, while Azure Security Benchmark is a set of best-practice recommendations—not a log collection or analytics platform.
ExpressRoute Global Reach allows you to connect your on-premises sites together through the Microsoft global network by linking multiple ExpressRoute circuits, enabling site-to-site connectivity between regions. ExpressRoute Direct provides a high-bandwidth direct port to Microsoft's backbone, not cross-site connectivity.
Enables communication between Azure resources within the same VNet.
Explanation :
By default, Azure VNets allow secure communication between Azure resources within the same VNet. Outbound internet communication is allowed by default, but inbound internet access is restricted unless a public IP or appropriate rule is assigned. VNets can connect across regions using peering, so option D is incorrect.
For Point-to-Site VPNs, using Azure AD authentication and RADIUS authentication allows integration with corporate credentials. Azure certificate authentication relies on certificates, but not directory credentials. Static shared keys are not used for Point-to-Site client authentication.
Azure VNets enable communication between Azure resources.
Explanation :
{{Correct. Virtual Networks can connect
Azure resources including VMs, the App Service Environment, Azure Kubernetes Service, and Azure
virtual machine scale sets. You can use service endpoints to connect to other Azure resource types,
such as Azure SQL databases and storage accounts.}}
Azure Front Door is a global service, whereas Azure Application Gateway is regional.
Explanation :
Azure Front Door is a global service designed for HTTP/HTTPS load balancing across regions and global content delivery, while Azure Application Gateway is a regional service designed for HTTP/HTTPS load balancing within a particular Azure region. Both operate at Layer 7.
{{Correct. You can enable ExpressRoute Premium to extend
connectivity across geopolitical boundaries. For example, if you connect to Microsoft in Amsterdam
through ExpressRoute, you'll have access to all Microsoft cloud services hosted in all regions across
the world.}}
