Correct Answer: A

Correct Answer(s):

Routing rules and backend listeners - You can configure the hosting of multiple web sites when you create an application gateway. You need to define backend address pools using virtual machines. You then configure listeners and rules based on domains that you own to make sure web traffic arrives at the appropriate servers in the pools.

https://docs.microsoft.com/bs-latn-ba/azure//application-gateway/create-multiple-sites-portal

Wrong Answers:

CNAME and A records - These are used for domain registrations.

Routing method and DNS time to live (TTL) - DNS TTL (time to live) is a setting that tells the DNS resolver how long to cache a query before requesting a new one. This is nothing to do with routing.

Path-based redirection and websockets - Path Based Routing allows you to route traffic to back-end server pools based on URL Paths of the request.

Correct Answer: D

Correct Answer(s):

a custom rule that uses a match rule - Custom rules allow you to create tailored rules to suit the exact needs of your applications and security policies. Now, you can restrict access to your web applications by country/region. As with all

custom rules, this logic can be compounded with other rules to suit the needs of your application.

To create a geo-filtering custom rule in the Azure portal, simply select Geo location as the Match Type, and then select the country/region or countries/regions you want to allow/block from your application.

https://docs.microsoft.com/en-us/azure/web-application-firewall/ag/geomatch-custom-rules

Wrong Answers:

a frontend host association This is to add a frontend profile.

a managed rule set - Azure-managed rule sets provide an easy way to deploy protection against a common set of security threats.

a custom rule that uses a rate limit rule - A rate control rule limits abnormally high traffic from any client IP address.

Correct Answer: B

Correct Answer:

Box 1: 2 Listeners

One listener for As1.contoso.com, and one listener for As2.contoso.com.

Note: Multiple site hosting enables you to configure more than one web application on the same port of application gateways using public-facing listeners. It allows you to configure a more efficient topology for your deployments by adding up to 100+ websites to one application gateway. Each website can be directed to its own backend pool. For example, three domains, contoso.com, fabrikam.com, and adatum.com, point to the IP address of the application gateway. You'd create three multi-site listeners and configure each listener for the respective port and protocol setting.

You can also define wildcard host names in a multi-site listener and up to 5 host names per listener.

Box 2: 2 Routing rules

Application Gateway request routing rules Rule type When you create a rule, you choose between basic and path-based.

*

Choose basic if you want to forward all requests on the associated listener (for example, blog.contoso.com/*) to a single backend pool.

*

Choose path-based if you want to route requests from specific URL paths to specific backend pools. The path pattern is applied only to the path of the URL, not to its query parameters.

Associated backend pool

Associate to the rule the backend pool that contains the backend targets that serve requests that the listener receives.

*

For a basic rule, only one backend pool is allowed. All requests on the associated listener are forwarded to that backend pool.

*

For a path-based rule, add multiple backend pools that correspond to each URL path. The requests that match the URL path that's entered are forwarded to the corresponding backend pool. Also, add a default backend pool. Requests that

don't match any URL path in the rule are forwarded to that pool.

Reference: https://learn.microsoft.com/en-us/azure/application-gateway/multiple-site-overview

Correct Answer:

Reference: https://docs.microsoft.com/en-us/azure/load-balancer/skus

https://docs.microsoft.com/en-us/azure/load-balancer/load-balancer-outbound-connections#outboundrules