Azure Network Engineer AZ-700 练习

VPN Gateway connects networks over encrypted tunnels. Databases, storage, and CDNs are different.

ExpressRoute provides private connectivity to Azure. Public routes, DNS records, and load balancers are different.

Virtual WAN centralizes networking hubs. Databases, DNS zones, and firewalls are different.

Bastion provides secure remote access without exposing public IPs. Websites, databases, and storage are different.

Site-to-site VPNs connect entire networks. Client VPNs, DNS records, and firewalls are different.

Point-to-site VPNs connect individual clients. Network-to-network VPNs, load balancers, and DNS zones are different.

Virtual networks isolate Azure resources. Databases, firewalls, and DNS records are resources or services.

Hub-spoke centralizes shared services. Single networks, DNS zones, and load balancers are different.

Virtual Network Manager helps manage many VNets. Databases, firewalls, and DNS zones are different.

VPN Gateway tunnels, ExpressRoute provides private links, Virtual WAN creates hubs, and Bastion enables secure access.

Route tables define custom routing. Databases, firewalls, and DNS zones are different.

Load Balancer distributes traffic at layer 4. WAF, DNS, and databases are different.

Application Gateway routes HTTP traffic at layer 7. DNS, databases, and storage are different.

Traffic Manager routes traffic at DNS level. Databases, firewalls, and CDNs are different.

Front Door provides global HTTP routing and acceleration. DNS records, databases, and firewalls are different.

NAT Gateway provides outbound internet access. Load balancers, DNS servers, and firewalls are different.

Load balancing rules map frontend traffic to backends. Firewall rules, DNS records, and storage policies are different.

Health probes verify backend availability. Firewall rules, DNS records, and load balancers are different.

Session affinity keeps clients on one backend. Firewall rules, DNS records, and storage policies are different.

Load Balancer is L4, App Gateway is L7, Traffic Manager is DNS, and Front Door is a global edge.

Private endpoints give services private IP addresses. Public sites, DNS records, and firewalls are different.

Private DNS zones resolve names inside VNets. Public records, firewalls, and load balancers are different.

VNet peering connects virtual networks. Public connections, DNS records, and firewalls are different.

Service endpoints provide VNet access to Azure services. DNS records, firewalls, and load balancers are different.

Private Link exposes services through private endpoints. DNS zones, firewalls, and CDNs are different.

DNS resolves names to IPs. Filtering, encryption, and reports are different.

Private IPs are used inside VNets. Public addresses, DNS records, and firewall rules are different.

VNet integration connects services to networks. Public sites, DNS records, and firewalls are different.

Private resolver handles private DNS. Firewalls, load balancers, and databases are different.

Private endpoints give private access, private DNS resolves, VNet peering connects networks, and service endpoints access services.

NSGs filter traffic with rules. Databases, DNS zones, and load balancers are different.

Azure Firewall filters network traffic. Databases, DNS zones, and load balancers are different.

WAF protects web applications. DNS, databases, and CDNs are different.

DDoS Protection mitigates attacks. Backups, DNS, and firewalls are different.

ASGs group VMs by application. DNS records, firewalls, and load balancers are different.

Service tags represent Azure service IP ranges. VM names, databases, and storage accounts are different.

NVAs provide network functions. DNS records, databases, and load balancers are different.

JIT access opens ports temporarily. Always-open ports, deletion, and DNS are different.

Bastion enables secure remote access. Public sites, databases, and DNS zones are different.

NSGs apply traffic rules, Firewall is managed, WAF protects web apps, and DDoS defends against attacks.

Network Watcher provides diagnostics. Databases, DNS zones, and load balancers are different.

Flow logs record NSG traffic decisions. DNS records, backups, and buckets are different.

Connection monitors verify connectivity. Firewalls, DNS records, and load balancers are different.

Packet capture records traffic. Blocking, DNS resolution, and IP assignment are different.

Topology visualizes network resources. Firewall rules, DNS records, and load balancers are different.

IP flow verify checks traffic decisions. Backups, DNS queries, and load balancers are different.

Effective rules show applied NSG rules. DNS records, firewalls, and load balancers are different.

Azure Monitor collects monitoring data. DNS, CDN, and storage are different.

NSG diagnostics help troubleshoot rules. Backups, DNS records, and load balancers are different.

Network Watcher diagnoses, flow logs record traffic, connection monitors test links, and packet capture records packets.

Hub-spoke centralizes shared services. Single networks, DNS zones, and load balancers are different.

Virtual WAN creates global hubs. Databases, firewalls, and DNS zones are different.

Quotas limit resources. Models, datasets, and DNS records are different.

Availability zones provide isolation within regions. DNS records, firewalls, and load balancers are different.

Transit routing goes through a hub. Direct routing, DNS, and firewalls are different.

Segmentation isolates workloads. Merging, deleting firewalls, and DNS are different.

Cost optimization balances spend and needs. Buying more, disabling security, and reports are different.

High availability plans for failures. DNS records, firewalls, and load balancers are components.

Design patterns are reusable approaches. Firewall rules, DNS records, and load balancers are components.

Hub-spoke uses a central hub, Virtual WAN creates global hubs, quotas limit resources, and segmentation isolates workloads.