Application Gateway (Layer 7) in Azure - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create an Application Gateway resource in Azure.

Azure

az network application-gateway create --name myAppGateway --resource-group myResourceGroup --location eastus --sku [1]

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

APremium_v2

BStandard

CBasic

DStandard_v2

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing SKUs with version suffixes when the task asks for the basic SKU.

Using SKUs meant for other Azure services.

The Standard SKU is a common choice for basic Application Gateway setups.

2fill in blank

medium

Complete the code to add a listener to the Application Gateway.

Azure

az network application-gateway http-listener create --gateway-name myAppGateway --name myListener --frontend-port [1] --resource-group myResourceGroup

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

A80

B8080

C443

D8443

Attempts:

3 left

💡 Hint

Common Mistakes

Using HTTPS port 443 for an HTTP listener.

Choosing uncommon ports without configuration.

Port 80 is the default port for HTTP traffic and commonly used for listeners.

3fill in blank

hard

Fix the error in the backend pool configuration by completing the code.

Azure

az network application-gateway address-pool create --gateway-name myAppGateway --resource-group myResourceGroup --name myBackendPool --servers [1]

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

A10.0.0.4,10.0.0.5

B10.0.0.4;10.0.0.5

C10.0.0.4 10.0.0.5

D10.0.0.4

Attempts:

3 left

💡 Hint

Common Mistakes

Using spaces or semicolons instead of commas to separate IPs.

Providing only one IP when multiple are needed.

The --servers parameter requires IP addresses separated by commas without spaces.

4fill in blank

hard

Fill both blanks to configure a routing rule that connects the listener to the backend pool.

Azure

az network application-gateway rule create --gateway-name myAppGateway --resource-group myResourceGroup --name myRule --http-listener [1] --rule-type [2] --address-pool myBackendPool

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

AmyListener

BBasic

CAdvanced

DdefaultListener

Attempts:

3 left

💡 Hint

Common Mistakes

Using a listener name that does not exist.

Choosing 'Advanced' rule type when a basic rule is needed.

The listener name must match the created listener, and the rule type for simple routing is Basic.

5fill in blank

hard

Fill all three blanks to create a health probe for the backend pool.

Azure

az network application-gateway probe create --gateway-name myAppGateway --resource-group myResourceGroup --name myHealthProbe --protocol [1] --host [2] --path [3]

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

AHttp

Bmybackend.contoso.com

C/healthcheck

DHttps

Attempts:

3 left

💡 Hint

Common Mistakes

Using HTTPS without proper backend configuration.

Incorrect or missing health probe path.

The health probe uses HTTP protocol, targets the backend host, and checks the /healthcheck path.