Azure Firewall for centralized security - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create an Azure Firewall resource in a resource group.

Azure

az network firewall create --name myFirewall --resource-group [1] --location eastus

Drag options to blanks, or click blank then click option'

AmyResourceGroup

BcentralRG

CfirewallRG

Deastus

Attempts:

3 left

💡 Hint

Common Mistakes

Using the location name instead of the resource group name.

Confusing resource group with location.

The --resource-group parameter specifies the resource group where the firewall will be created. Here, centralRG is the correct resource group name.

2fill in blank

medium

Complete the code to create a firewall policy named 'centralPolicy'.

Azure

az network firewall policy create --name [1] --resource-group centralRG

Drag options to blanks, or click blank then click option'

AcentralPolicy

BfirewallPolicy

CpolicyCentral

DdefaultPolicy

Attempts:

3 left

💡 Hint

Common Mistakes

Using a generic or default name instead of the specified one.

Mixing up policy names.

The --name parameter sets the name of the firewall policy. Here, centralPolicy is the intended name.

3fill in blank

hard

Fix the error in the command to associate the firewall policy with the firewall.

Azure

az network firewall update --name myFirewall --resource-group centralRG --[1] centralPolicy

Drag options to blanks, or click blank then click option'

Apolicy-id

Bpolicy

Cfirewall-policy

DfirewallPolicy

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect parameter names like 'policy' or 'policy-id'.

Missing hyphens in the parameter name.

The correct parameter to associate a firewall policy is --firewall-policy.

4fill in blank

hard

Fill both blanks to create a network rule collection that allows HTTP traffic.

Azure

az network firewall network-rule collection create --firewall-name myFirewall --resource-group centralRG --name AllowHTTP --priority 100 --action Allow --rule-name [1] --protocols [2] --source-addresses '*' --destination-ports 80 --destination-addresses '*'

Drag options to blanks, or click blank then click option'

AAllowHTTPRule

BDenyHTTPRule

CTCP

DUDP

Attempts:

3 left

💡 Hint

Common Mistakes

Using a deny rule name when the action is Allow.

Choosing UDP protocol for HTTP traffic.

The rule name should be descriptive like AllowHTTPRule. HTTP uses the TCP protocol, so TCP is correct for protocols.

5fill in blank

hard

Fill all three blanks to create an application rule collection allowing access to example.com.

Azure

az network firewall application-rule collection create --firewall-name myFirewall --resource-group centralRG --name AllowWeb --priority 200 --action Allow --rule-name [1] --protocols [2] --target-fqdns [3] --source-addresses '*'

Drag options to blanks, or click blank then click option'

AAllowExampleRule

BHttp=80

Cexample.com

DHttps=443

Attempts:

3 left

💡 Hint

Common Mistakes

Using HTTP protocol instead of HTTPS for secure sites.

Incorrect or missing target domain.

The rule name AllowExampleRule describes the purpose. HTTPS protocol on port 443 is typical for secure web access, and example.com is the target domain.

Practice

1. What is the primary purpose of Azure Firewall in a cloud environment?

easy

A. To centralize network security and control traffic

B. To store large amounts of data securely

C. To provide virtual machines for computing

D. To manage user identities and access

Solution

1. Step 1: Understand Azure Firewall's role

   Azure Firewall is designed to protect cloud resources by controlling and monitoring network traffic centrally.

2. Step 2: Differentiate from other services

   Storing data, providing VMs, or managing identities are roles of other Azure services, not Azure Firewall.

3. Final Answer:

   To centralize network security and control traffic -> Option A

4. Quick Check:

   Azure Firewall = Centralized network security [OK]

Hint: Azure Firewall controls traffic centrally, not data or users [OK]

Common Mistakes:

• Confusing Azure Firewall with storage services
• Thinking it manages user identities
• Assuming it provides computing resources

2. Which subnet name is required when deploying Azure Firewall in a virtual network?

easy

A. Subnet1

B. AzureFirewallSubnet

C. FirewallSubnet

D. DefaultSubnet

Solution

1. Step 1: Recall Azure Firewall deployment requirements

   Azure Firewall requires a dedicated subnet named exactly 'AzureFirewallSubnet' for deployment.

2. Step 2: Check other options

   Other subnet names like 'FirewallSubnet' or 'DefaultSubnet' are incorrect and will cause deployment failure.

3. Final Answer:

   AzureFirewallSubnet -> Option B

4. Quick Check:

   Subnet name must be AzureFirewallSubnet [OK]

Hint: Use exact subnet name 'AzureFirewallSubnet' for firewall deployment [OK]

Common Mistakes:

• Using generic subnet names instead of required one
• Misspelling the subnet name
• Not creating a dedicated subnet for Azure Firewall

3. Given this Azure Firewall rule collection, what traffic will be allowed?

{
  "name": "AllowWeb",
  "rules": [
    {"name": "AllowHTTP", "protocol": "TCP", "port": 80, "action": "Allow"},
    {"name": "AllowHTTPS", "protocol": "TCP", "port": 443, "action": "Allow"}
  ]
}

medium

A. All traffic regardless of protocol or port

B. All TCP traffic on any port

C. Only HTTPS traffic on port 443

D. Only HTTP and HTTPS traffic on ports 80 and 443

Solution

1. Step 1: Analyze the rule collection

   The rules explicitly allow TCP traffic on ports 80 (HTTP) and 443 (HTTPS) only.

2. Step 2: Exclude other traffic

   Other ports or protocols are not allowed since no rules permit them.

3. Final Answer:

   Only HTTP and HTTPS traffic on ports 80 and 443 -> Option D

4. Quick Check:

   Rules allow TCP ports 80 and 443 only [OK]

Hint: Check ports and protocols in rules to find allowed traffic [OK]

Common Mistakes:

• Assuming all TCP traffic is allowed
• Ignoring port restrictions
• Confusing protocol types

4. You deployed Azure Firewall but traffic is not passing through. Which configuration mistake could cause this?

medium

A. Subnet name is not 'AzureFirewallSubnet'

B. Public IP address is assigned to the firewall

C. Firewall rules allow HTTP and HTTPS traffic

D. Virtual network has multiple subnets

Solution

1. Step 1: Identify deployment requirements

   Azure Firewall requires the subnet to be named 'AzureFirewallSubnet' exactly for proper routing.

2. Step 2: Understand impact of wrong subnet name

   If the subnet name is incorrect, firewall won't route traffic, causing blockage.

3. Final Answer:

   Subnet name is not 'AzureFirewallSubnet' -> Option A

4. Quick Check:

   Correct subnet name is critical for traffic flow [OK]

Hint: Check subnet name first if firewall blocks traffic [OK]

Common Mistakes:

• Assuming public IP causes blockage (it is required)
• Ignoring subnet naming rules
• Thinking multiple subnets cause traffic issues

5. You want to centralize security for multiple virtual networks using Azure Firewall. Which setup is best practice?

hard

A. Deploy separate Azure Firewalls in each virtual network without routing

B. Use network security groups only without Azure Firewall

C. Deploy one Azure Firewall in a hub virtual network and route traffic from spoke networks through it

D. Deploy Azure Firewall without a public IP address

Solution

1. Step 1: Understand centralized security architecture

   Using a hub-and-spoke model, one Azure Firewall in the hub network protects multiple spoke networks by routing traffic through it.

2. Step 2: Evaluate other options

   Deploying multiple firewalls increases cost and complexity; NSGs alone don't provide centralized control; firewall needs public IP for internet traffic.

3. Final Answer:

   Deploy one Azure Firewall in a hub virtual network and route traffic from spoke networks through it -> Option C

4. Quick Check:

   Hub-and-spoke with one firewall = centralized security [OK]

Hint: Use hub network firewall to protect multiple spokes [OK]

Common Mistakes:

• Deploying multiple firewalls unnecessarily
• Relying only on network security groups
• Omitting public IP for Azure Firewall