Application Gateway (Layer 7) in Azure - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

How does Azure Application Gateway handle HTTP requests with path-based routing?

Consider an Azure Application Gateway configured with path-based routing rules. What happens when a client sends an HTTP request to a URL path that matches one of the defined routing rules?

A The Application Gateway forwards the request to the backend pool associated with the matching path rule.

B The Application Gateway rejects the request with a 403 Forbidden error.

C The Application Gateway forwards the request to all backend pools simultaneously.

D The Application Gateway redirects the request to the frontend IP address.

💡 Hint

Think about how path-based routing directs traffic to specific backend pools.

Azure Application Gateway uses path-based routing rules to forward HTTP requests to the backend pool that matches the URL path. It does not reject, broadcast, or redirect the request in this scenario.

❓ security

intermediate

What happens if you enable Web Application Firewall (WAF) on Azure Application Gateway and a request contains a SQL injection attack?

Azure Application Gateway has Web Application Firewall (WAF) enabled. A client sends a request containing a SQL injection attack pattern. What is the expected behavior?

A The Application Gateway forwards the request to the backend pool without inspection.

B The Application Gateway redirects the request to a custom error page hosted on the backend.

C The Application Gateway logs the attack but allows the request to pass through.

D The WAF detects the attack and blocks the request before it reaches the backend pool.

💡 Hint

Consider the purpose of WAF in protecting web applications.

When WAF is enabled, it inspects incoming requests for attack patterns like SQL injection and blocks malicious requests before they reach backend servers.

❓ Architecture

advanced

Which Azure Application Gateway configuration supports SSL termination and end-to-end SSL encryption simultaneously?

You want to configure Azure Application Gateway to decrypt incoming SSL traffic and then re-encrypt it before sending to backend servers. Which configuration achieves this?

A Configure the Application Gateway to use TCP load balancing.

B Enable SSL passthrough on the Application Gateway without SSL certificates.

C Enable SSL termination on the Application Gateway and configure HTTPS listeners and backend HTTPS settings with certificates.

D Disable SSL termination and use HTTP listeners only.

💡 Hint

Think about how SSL termination and re-encryption work together.

SSL termination decrypts traffic at the gateway, and re-encryption requires HTTPS listeners and backend HTTPS settings with certificates to encrypt traffic again to backend servers.

✅ Best Practice

advanced

What is the recommended way to scale Azure Application Gateway to handle increased traffic?

Your web application is experiencing increased traffic. How should you scale Azure Application Gateway to maintain performance?

A Increase the instance count of the Application Gateway and enable autoscaling.

B Manually increase the size of backend VMs only.

C Add more backend pools without changing the Application Gateway.

D Switch to a Basic SKU Application Gateway for better performance.

💡 Hint

Consider how Application Gateway scales to handle more requests.

Scaling Application Gateway involves increasing instance count and enabling autoscaling to automatically adjust capacity based on traffic.

🧠 Conceptual

expert

What is the effect of enabling the 'Cookie-based affinity' feature on Azure Application Gateway?

Azure Application Gateway supports 'Cookie-based affinity'. What does enabling this feature do?

A It caches cookies at the Application Gateway to reduce backend load.

B It ensures that all requests from a client session are routed to the same backend server by using a cookie.

C It encrypts cookies to enhance security between client and backend.

D It disables session persistence and distributes requests randomly.

💡 Hint

Think about how session persistence works in load balancing.

Cookie-based affinity uses a cookie to keep a client session tied to the same backend server, ensuring session persistence.