Azure SQL firewall rules - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a firewall rule allowing access from a specific IP address.

Azure

az sql server firewall-rule create --resource-group myResourceGroup --server myServer --name AllowMyIP --start-ip-address [1] --end-ip-address [1]

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

AmyServer

B255.255.255.0

C192.168.1.1

D0.0.0.0

Attempts:

3 left

💡 Hint

Common Mistakes

Using the server name instead of an IP address.

Using an IP range when only a single IP is needed.

The start and end IP address must be the specific IP you want to allow, here '192.168.1.1'.

2fill in blank

medium

Complete the code to list all firewall rules for an Azure SQL server.

Azure

az sql server firewall-rule list --resource-group myResourceGroup --server [1]

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

AmyResourceGroup

BfirewallRule1

CAllowMyIP

DmyServer

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing resource group name with server name.

Using a firewall rule name instead of server name.

The server name is required to list its firewall rules.

3fill in blank

hard

Fix the error in the command to delete a firewall rule named 'AllowMyIP'.

Azure

az sql server firewall-rule delete --resource-group myResourceGroup --server myServer --name [1]

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

AmyResourceGroup

BAllowMyIP

CmyServer

DdeleteRule

Attempts:

3 left

💡 Hint

Common Mistakes

Using the server or resource group name instead of the rule name.

Using an incorrect rule name.

The --name parameter must be the firewall rule name to delete, here 'AllowMyIP'.

4fill in blank

hard

Fill both blanks to create a firewall rule allowing access from IP range 10.0.0.1 to 10.0.0.255.

Azure

az sql server firewall-rule create --resource-group myResourceGroup --server myServer --name AllowRange --start-ip-address [1] --end-ip-address [2]

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

A10.0.0.1

B10.0.0.255

C192.168.0.1

D255.255.255.255

Attempts:

3 left

💡 Hint

Common Mistakes

Swapping start and end IP addresses.

Using unrelated IP addresses.

The start IP is 10.0.0.1 and the end IP is 10.0.0.255 to cover the range.

5fill in blank

hard

Fill all three blanks to update a firewall rule named 'AllowOffice' to allow IP 203.0.113.5.

Azure

az sql server firewall-rule update --resource-group [1] --server [2] --name [3] --start-ip-address 203.0.113.5 --end-ip-address 203.0.113.5

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

AmyResourceGroup

BmyServer

CAllowOffice

D203.0.113.5

Attempts:

3 left

💡 Hint

Common Mistakes

Using IP address as resource group or server name.

Mixing up the order of parameters.

Resource group, server name, and rule name must be specified to update the rule.

Practice

1. What is the main purpose of Azure SQL firewall rules?

easy

A. To control which IP addresses can access the database

B. To encrypt data stored in the database

C. To backup the database automatically

D. To monitor database performance

Solution

1. Step 1: Understand firewall rules function

   Azure SQL firewall rules specify which IP addresses are allowed to connect to the database.

2. Step 2: Compare with other options

   Encryption, backup, and monitoring are different features not controlled by firewall rules.

3. Final Answer:

   To control which IP addresses can access the database -> Option A

4. Quick Check:

   Firewall rules = control IP access [OK]

Hint: Firewall rules control IP access, not encryption or backup [OK]

Common Mistakes:

• Confusing firewall rules with encryption settings
• Thinking firewall rules manage backups
• Assuming firewall rules monitor performance

2. Which of the following is the correct way to define a firewall rule in Azure SQL?

easy

A. Specify a username and password

B. Specify only a single IP address without a range

C. Specify a start IP and an end IP address range

D. Specify a database name and region

Solution

1. Step 1: Recall firewall rule structure

   Azure SQL firewall rules require a start IP and an end IP to define the allowed range.

2. Step 2: Eliminate incorrect options

   Single IP alone is not enough; username/password and database name/region are unrelated to firewall rules.

3. Final Answer:

   Specify a start IP and an end IP address range -> Option C

4. Quick Check:

   Firewall rule = start IP + end IP [OK]

Hint: Firewall rules need IP ranges, not usernames or database names [OK]

Common Mistakes:

• Trying to use usernames instead of IP addresses
• Defining only one IP without a range
• Confusing firewall rules with database settings

3. Given a firewall rule with start IP 192.168.1.10 and end IP 192.168.1.20, which IP address can connect?

medium

A. 192.168.1.9

B. 192.168.2.10

C. 192.168.1.21

D. 192.168.1.15

Solution

1. Step 1: Understand IP range inclusion

   The firewall rule allows IPs from 192.168.1.10 up to 192.168.1.20 inclusive.

2. Step 2: Check each IP against the range

   192.168.1.9 is below start IP, 192.168.1.15 is inside range, 192.168.1.21 and 192.168.2.10 are outside the range.

3. Final Answer:

   192.168.1.15 -> Option D

4. Quick Check:

   IP inside range = allowed [OK]

Hint: Check if IP is between start and end IP inclusive [OK]

Common Mistakes:

• Choosing IP just outside the range
• Ignoring inclusive range boundaries
• Confusing similar IP addresses

4. You created a firewall rule with start IP 10.0.0.5 and end IP 10.0.0.3. What is the problem?

medium

A. The rule allows all IPs by mistake

B. Start IP is greater than end IP, so the rule is invalid

C. The IP addresses are in different subnets

D. There is no problem; the rule is valid

Solution

1. Step 1: Check IP range order

   The start IP must be less than or equal to the end IP for a valid range.

2. Step 2: Identify invalid range

   Here, 10.0.0.5 is greater than 10.0.0.3, making the range invalid.

3. Final Answer:

   Start IP is greater than end IP, so the rule is invalid -> Option B

4. Quick Check:

   Start IP ≤ End IP for valid rule [OK]

Hint: Start IP must be less or equal to end IP [OK]

Common Mistakes:

• Ignoring IP order in the range
• Assuming different subnets cause errors
• Thinking invalid range allows all IPs

5. You want to allow access only from your office IP 203.0.113.25 and your home IP 198.51.100.10. How should you configure Azure SQL firewall rules?

hard

A. Create two separate firewall rules, each with start and end IP set to one of the IPs

B. Create one firewall rule with start IP 198.51.100.10 and end IP 203.0.113.25

C. Create one firewall rule with start IP 0.0.0.0 and end IP 255.255.255.255

D. Create a firewall rule with start IP 198.51.100.10 and end IP 198.51.100.10 only

Solution

1. Step 1: Understand IP range rules

   Firewall rules allow ranges of IPs; to allow two separate IPs, create two rules each with start and end IP the same.

2. Step 2: Evaluate options

   Create two separate firewall rules, each with start and end IP set to one of the IPs correctly creates two rules for each IP. Create one firewall rule with start IP 198.51.100.10 and end IP 203.0.113.25 creates a large range including unwanted IPs. Create one firewall rule with start IP 0.0.0.0 and end IP 255.255.255.255 allows all IPs, which is insecure. Create a firewall rule with start IP 198.51.100.10 and end IP 198.51.100.10 only allows only one IP, missing the other.

3. Final Answer:

   Create two separate firewall rules, each with start and end IP set to one of the IPs -> Option A

4. Quick Check:

   Separate IPs need separate rules [OK]

Hint: Use separate rules for separate IPs, same start and end IP [OK]

Common Mistakes:

• Trying to combine non-contiguous IPs in one rule
• Allowing all IPs by mistake
• Creating only one rule for multiple IPs