Application Gateway (Layer 7) in Azure - Time & Space Complexity

Time Complexity: Application Gateway (Layer 7)

O(n)

Understanding Time Complexity

We want to understand how the work done by an Application Gateway grows as more requests come in.

Specifically, how does the number of requests affect the processing time and resource use?

Scenario Under Consideration

Analyze the time complexity of processing incoming HTTP requests through an Application Gateway.

// Pseudocode for request processing
foreach (request in incomingRequests) {
  authenticate(request);
  applyWebApplicationFirewall(request);
  routeToBackend(request);
  logRequest(request);
}

This sequence shows how each request is handled one by one by the Application Gateway at Layer 7.

Identify Repeating Operations

Look at what happens repeatedly for each request:

• Primary operation: Processing each HTTP request through authentication, firewall checks, routing, and logging.
• How many times: Once per incoming request.

How Execution Grows With Input

As the number of requests increases, the Application Gateway processes each one individually.

Input Size (n)	Approx. Api Calls/Operations
10	10 request processings
100	100 request processings
1000	1000 request processings

Pattern observation: The work grows directly with the number of requests; double the requests, double the work.

Final Time Complexity

Time Complexity: O(n)

This means the processing time grows linearly with the number of incoming requests.

Common Mistake

[X] Wrong: "The Application Gateway processes all requests at once, so time stays the same no matter how many requests arrive."

[OK] Correct: Each request requires separate processing steps, so more requests mean more total work.

Interview Connect

Understanding how request load affects processing helps you design and explain scalable cloud solutions confidently.

Self-Check

"What if the Application Gateway used caching to skip some processing steps for repeated requests? How would the time complexity change?"

Practice

1. What is the main function of an Azure Application Gateway at Layer 7?

easy

A. It stores data in a scalable database.

B. It manages virtual machines in a subnet.

C. It routes web traffic based on URL paths and content.

D. It provides DNS resolution for domain names.

Solution

1. Step 1: Understand Layer 7 role

   Layer 7 means the application layer, which handles web traffic content like URLs.

2. Step 2: Identify Application Gateway function

   Application Gateway routes traffic based on URL paths and content, unlike DNS or VM management.

3. Final Answer:

   It routes web traffic based on URL paths and content. -> Option C

4. Quick Check:

   Layer 7 routing = URL-based traffic routing [OK]

Hint: Layer 7 means web content routing, not VM or DNS tasks [OK]

Common Mistakes:

• Confusing Application Gateway with DNS or VM services
• Thinking it works at network layer instead of application layer
• Assuming it stores data like a database

2. Which of the following is the correct way to define a frontend IP configuration for an Azure Application Gateway in ARM template JSON?

easy

A. {\"name\": \"appGatewayFrontendIP\", \"properties\": {\"publicIPAddress\": {\"id\": \"/subscriptions/.../publicIPAddresses/myPublicIP\"}}}

B. {\"name\": \"appGatewayFrontendIP\", \"location\": \"eastus\"}

C. {\"frontendIP\": \"myPublicIP\"}

D. {\"ipConfig\": {\"publicIP\": \"myPublicIP\"}}

Solution

1. Step 1: Review ARM template frontend IP syntax

   The frontend IP config requires a name and properties including a reference to a public IP resource by its ID.

2. Step 2: Match correct JSON structure

   {\"name\": \"appGatewayFrontendIP\", \"properties\": {\"publicIPAddress\": {\"id\": \"/subscriptions/.../publicIPAddresses/myPublicIP\"}}} correctly uses "name" and "properties" with "publicIPAddress" and its "id" field, matching ARM schema.

3. Final Answer:

   {"name": "appGatewayFrontendIP", "properties": {"publicIPAddress": {"id": "/subscriptions/.../publicIPAddresses/myPublicIP"}}} -> Option A

4. Quick Check:

   Frontend IP config needs name + publicIPAddress id [OK]

Hint: Look for 'properties' with 'publicIPAddress' and 'id' fields [OK]

Common Mistakes:

• Missing 'properties' wrapper around publicIPAddress
• Using 'location' inside frontend IP config incorrectly
• Incorrect field names like 'frontendIP' or 'ipConfig'

3. Given this simplified ARM snippet for an Application Gateway backend HTTP settings, what will be the effect of setting "pickHostNameFromBackendAddress" to true?

{
  "name": "appGatewayBackendHttpSettings",
  "properties": {
    "port": 80,
    "protocol": "Http",
    "pickHostNameFromBackendAddress": true
  }
}

medium

A. The backend hostname is taken from the backend pool IP or FQDN instead of the HTTP settings.

B. The Application Gateway ignores the backend pool and uses the frontend hostname.

C. The backend HTTP settings port is ignored and defaults to 443.

D. The Application Gateway disables SSL termination.

Solution

1. Step 1: Understand 'pickHostNameFromBackendAddress'

   This setting tells the gateway to use the hostname from the backend pool's address (IP or FQDN) for HTTP requests.

2. Step 2: Analyze effect on backend requests

   When true, the hostname in HTTP headers matches backend pool address, not the HTTP settings hostname.

3. Final Answer:

   The backend hostname is taken from the backend pool IP or FQDN instead of the HTTP settings. -> Option A

4. Quick Check:

   pickHostNameFromBackendAddress true = use backend pool hostname [OK]

Hint: True means use backend pool hostname, not HTTP settings hostname [OK]

Common Mistakes:

• Thinking it changes port or protocol
• Confusing frontend hostname with backend hostname
• Assuming it disables SSL termination

4. You deployed an Application Gateway but it fails to route traffic to backend servers. The backend pool uses IP addresses, but the health probes always fail. What is a likely cause?

medium

A. The Application Gateway subnet is too large.

B. The backend HTTP settings have 'pickHostNameFromBackendAddress' set to true but backend IPs lack proper DNS names.

C. The frontend IP configuration is missing a public IP address.

D. The backend pool uses FQDNs instead of IP addresses.

Solution

1. Step 1: Understand health probe failure with IP backend pool

   If 'pickHostNameFromBackendAddress' is true, the gateway uses backend hostname from IP, which fails if no DNS name exists.

2. Step 2: Identify mismatch causing probe failure

   Backend IPs lack DNS names, so probes fail when hostname is required but missing.

3. Final Answer:

   The backend HTTP settings have 'pickHostNameFromBackendAddress' set to true but backend IPs lack proper DNS names. -> Option B

4. Quick Check:

   IP backend + pickHostNameFromBackendAddress true = probe fails [OK]

Hint: Check if backend IPs have DNS names when pickHostNameFromBackendAddress is true [OK]

Common Mistakes:

• Blaming subnet size for routing issues
• Assuming frontend IP config missing public IP causes backend probe failure
• Confusing backend pool IPs with FQDNs

5. You want to configure an Azure Application Gateway to route requests to different backend pools based on URL paths: /images/* to an image server pool and /api/* to an API server pool. Which configuration step is essential to achieve this?

hard

A. Configure the backend HTTP settings to use HTTPS only.

B. Assign multiple public IP addresses to the frontend configuration.

C. Use multiple frontend ports with the same backend pool.

D. Create path-based routing rules with URL path maps specifying backend pools for each path.

Solution

1. Step 1: Understand URL-based routing requirement

   Routing based on URL paths requires path-based routing rules with URL path maps.

2. Step 2: Configure path-based rules

   Define URL path maps that link specific URL patterns like '/images/*' and '/api/*' to their respective backend pools.

3. Final Answer:

   Create path-based routing rules with URL path maps specifying backend pools for each path. -> Option D

4. Quick Check:

   URL path routing = path-based rules with URL maps [OK]

Hint: Use path-based routing rules with URL maps for URL path routing [OK]

Common Mistakes:

• Thinking multiple public IPs are needed for URL routing
• Using multiple frontend ports without path rules
• Assuming backend HTTP settings control URL routing