πŸ”’ Guided

Pre-launch preview. Authorised access only.

Incorrect code

Guided by A Guide to Cloud
Explore AB-900 AI-901
Guided AZ-305 Domain 4
Domain 4 β€” Module 11 of 12 92%
29 of 30 overall

AZ-305 Study Guide

Domain 1: Design Identity, Governance, and Monitoring Solutions

  • Monitoring & Logging Design
  • Choosing Authentication Methods
  • Designing Identity Management
  • Authorizing Access to Resources
  • Secrets, Keys & Certificates
  • Governance at Scale
  • Compliance & Identity Governance

Domain 2: Design Data Storage Solutions

  • Relational Data: Choosing Your SQL Platform
  • Database Performance & Scalability
  • Database Security & Compliance
  • Cosmos DB & Semi-Structured Data
  • Blob, Data Lake & Azure Files
  • Data Integration & Analytics

Domain 3: Design Business Continuity Solutions

  • Recovery Objectives: RPO, RTO & SLA Free
  • Backup & Recovery for Compute Free
  • Backup for Databases & Unstructured Data Free
  • High Availability for Compute Free
  • High Availability for Data Free

Domain 4: Design Infrastructure Solutions

  • Compute Design: VMs & When to Use Them
  • Container Solutions: AKS, ACI & Container Apps
  • Serverless & Batch Processing
  • Messaging Architecture
  • Event-Driven Architecture
  • API Integration & Caching
  • App Configuration & Automated Deployment
  • Migration Strategy & Assessment
  • Executing Migrations
  • Network Connectivity: Internet & Hybrid
  • Network Security & Performance
  • Load Balancing & Routing

AZ-305 Study Guide

Domain 1: Design Identity, Governance, and Monitoring Solutions

  • Monitoring & Logging Design
  • Choosing Authentication Methods
  • Designing Identity Management
  • Authorizing Access to Resources
  • Secrets, Keys & Certificates
  • Governance at Scale
  • Compliance & Identity Governance

Domain 2: Design Data Storage Solutions

  • Relational Data: Choosing Your SQL Platform
  • Database Performance & Scalability
  • Database Security & Compliance
  • Cosmos DB & Semi-Structured Data
  • Blob, Data Lake & Azure Files
  • Data Integration & Analytics

Domain 3: Design Business Continuity Solutions

  • Recovery Objectives: RPO, RTO & SLA Free
  • Backup & Recovery for Compute Free
  • Backup for Databases & Unstructured Data Free
  • High Availability for Compute Free
  • High Availability for Data Free

Domain 4: Design Infrastructure Solutions

  • Compute Design: VMs & When to Use Them
  • Container Solutions: AKS, ACI & Container Apps
  • Serverless & Batch Processing
  • Messaging Architecture
  • Event-Driven Architecture
  • API Integration & Caching
  • App Configuration & Automated Deployment
  • Migration Strategy & Assessment
  • Executing Migrations
  • Network Connectivity: Internet & Hybrid
  • Network Security & Performance
  • Load Balancing & Routing
Domain 4: Design Infrastructure Solutions Premium ⏱ ~18 min read

Network Security & Performance

NSGs, Azure Firewall, WAF, DDoS Protection, and Azure Bastion β€” design network security that protects at every layer without sacrificing performance.

Network security and performance design

β˜• Simple explanation

Network security is a layered defence. No single control stops everything β€” you need multiple layers:

NSGs: Firewall rules on subnets and NICs (L3/L4 β€” IP and port filtering).

Azure Firewall: Central firewall with FQDN filtering, threat intelligence, and TLS inspection (Premium tier) (L3-L7).

WAF: Web Application Firewall protecting against OWASP attacks (SQL injection, XSS) (L7).

DDoS Protection: Absorbs massive volumetric attacks before they reach your resources.

Bastion: Secure RDP/SSH access to VMs without public IPs.

Network security architecture follows defence-in-depth:

  • Perimeter: DDoS Protection, Azure Firewall, WAF (Front Door/App Gateway)
  • Network: NSGs, ASGs, network segmentation, Private Link
  • Access: Azure Bastion (no public IPs on VMs), Just-in-Time VM access
  • Performance: ExpressRoute Global Reach, Azure CDN, Accelerated Networking

Network security layers

Network Security Services
ServiceOSI LayerScopeKey FeatureBest For
NSGL3/L4Subnet or NICIP/port allow/deny rulesMicro-segmentation between subnets
ASGL3/L4Grouped resourcesTag-based rules (no IP management)Dynamic rules based on application groups
Azure FirewallL3-L7Central (hub VNet)FQDN filtering, threat intel, TLS inspection (Premium only)Centralised egress control, network-level security
WAFL7Edge (Front Door / App GW)OWASP protection, custom rules, bot protectionWeb application protection (SQL injection, XSS)
DDoS Network ProtectionL3/L4VNet-levelVolumetric attack mitigation, adaptive tuningProtecting public endpoints from DDoS attacks
Azure BastionL7Per-VNetBrowser-based RDP/SSH, no public IP neededSecure VM management access

Azure Firewall tiers

Azure Firewall Tiers
FeatureBasicStandardPremium
ThroughputUp to 250 MbpsUp to 30 GbpsUp to 100 Gbps
FQDN filteringYesYesYes
Threat intelligenceAlert onlyAlert and denyAlert and deny
DNS proxyNoYesYes
TLS inspectionNoNoYes β€” decrypt, inspect, re-encrypt
IDPSNoNoYes β€” signature-based intrusion detection
URL filteringNoNoYes β€” full URL path, not just FQDN
Web categoriesNoYesYes
Best forSmall environments, SMBs, cost-sensitiveMost production workloadsRegulated industries needing deep packet inspection
πŸ’‘ Exam tip: Know which features require Premium

Three features are Premium-only: TLS inspection (decrypt and inspect encrypted traffic), IDPS (intrusion detection and prevention), and URL filtering (inspect full URL path, not just domain). If a scenario mentions inspecting encrypted traffic or detecting intrusion signatures, the answer is Azure Firewall Premium.

NSG vs Azure Firewall β€” when to use each

ScenarioUse NSGUse Azure FirewallUse Both
Simple subnet isolationβœ…Overkillβ€”
FQDN-based egress filteringCan’t do thisβœ…β€”
Centralised logging of all trafficLimitedβœ…βœ…
TLS inspectionNoβœ… (Premium)βœ…
Hub-spoke networkSpoke subnetsHub firewallβœ… Both

🏦 Elena’s defence-in-depth:

  1. DDoS Network Protection on VNet β€” absorbs volumetric attacks
  2. Front Door WAF β€” blocks OWASP attacks at the edge
  3. Azure Firewall Premium in hub VNet β€” FQDN filtering, TLS inspection, threat intelligence
  4. NSGs on every subnet β€” micro-segmentation between application tiers
  5. Azure Bastion β€” no public IPs on any VM, RDP/SSH through browser

Network performance optimisation

TechniqueWhat It DoesWhen to Use
Accelerated NetworkingBypasses host networking stack (SR-IOV)All production VMs that support it (free)
ExpressRoute Global ReachConnect on-prem sites through ExpressRoute backboneBranch-to-branch traffic via Microsoft network
Azure CDN / Front DoorCache content at edge POP locationsStatic content, global user base
Proximity Placement GroupsCo-locate VMs in same data centreUltra-low latency between VMs (HPC, trading)
ℹ️ Well-Architected Framework connection

Security pillar: Defence-in-depth β€” multiple layers, each catching what the previous missed. NSGs at the network level, WAF at the application level, DDoS at the perimeter.

Performance Efficiency: Accelerated Networking should be enabled on all VMs that support it β€” it’s free and reduces latency. Proximity Placement Groups for latency-sensitive workloads.

Cost Optimisation: Azure Firewall Basic tier for small networks. DDoS Network Protection is per protected public IP β€” covers all resources in a VNet with one plan.

Knowledge check

Question

What's the difference between NSGs and Azure Firewall?

Click or press Enter to reveal answer

Answer

NSGs filter at L3/L4 (IP/port) at the subnet/NIC level β€” simple, distributed, free. Azure Firewall filters at L3-L7 (including FQDN, TLS inspection, threat intelligence) in a centralised hub β€” more powerful, costs money. Use both: NSGs for micro-segmentation, Firewall for centralised control.

Click to flip back

Question

What does Azure Bastion provide?

Click or press Enter to reveal answer

Answer

Secure RDP/SSH access to VMs through the Azure portal (browser-based) without needing public IPs on VMs. Traffic goes over TLS to the Bastion host, then to the VM over the private network. Eliminates the attack surface of exposed RDP/SSH ports.

Click to flip back

Question

When should you upgrade from DDoS Protection Basic to DDoS Network Protection?

Click or press Enter to reveal answer

Answer

Upgrade when you have public-facing resources that need: guaranteed SLA-backed mitigation, real-time attack metrics and diagnostics, cost protection (credit for scale-out during attacks), and rapid response team access. Basic (free, always-on) protects the Azure platform. DDoS Network Protection specifically protects YOUR resources with adaptive tuning and alerting.

Click to flip back

Knowledge Check

🏦 Elena needs to protect FinSecure Bank's web applications from SQL injection and XSS attacks at the edge, while also filtering all outbound traffic from VMs through a central firewall with FQDN rules. Which combination should she recommend?

Knowledge Check

πŸ—οΈ GlobalTech's public-facing web app in Southeast Asia serves customers across Asia-Pacific. Users in Japan and Australia report slow page loads. The app also experienced a DDoS attack last month that caused 2 hours of downtime. Which combination should Priya recommend to solve both performance and protection issues?

🎬 Video coming soon


Next up: The final piece β€” routing traffic efficiently β€” Load Balancing & Routing.

← Previous

Network Connectivity: Internet & Hybrid

Next β†’

Load Balancing & Routing

Guided

I learn, I simplify, I share.

A Guide to Cloud YouTube Feedback

© 2026 Sutheesh. All rights reserved.

Guided is an independent study resource and is not affiliated with, endorsed by, or officially connected to Microsoft. Microsoft, Azure, and related trademarks are property of Microsoft Corporation. Always verify information against Microsoft Learn.