Exam AZ-700 All Questions

View all questions & answers for the AZ-700 exam

Exam AZ-700 topic 2 question 26 discussion

Actual exam question from Microsoft's AZ-700

Question #: 26
Topic #: 2

HOTSPOT
-

You have two Azure App Service instances that host the web apps shown the following table.

You deploy an Azure 2 that has one public frontend IP address and two backend pools.

You need to publish all the web apps to the application gateway. Requests must be routed based on the HTTP host headers.

What is the minimum number of listeners and routing rules you should configure? To answer, select the appropriate options in the answer area.

NOTE: Each correct selection is worth one point.

Show Suggested Answer

Suggested Answer:

by TJ001 at Jan. 19, 2023, 8:04 a.m.

Comments

Submit Cancel

TJ001

Highly Voted 2 years ago

Answer seems correct 1) 1 Multi site Listener mapping each backend app service (total 2) 2) 1 routing rule mapping per listener/backend pool with Multi site option (total 2)

upvoted 22 times

daemon101

1 year, 6 months ago

When configuring path-based routing, you will see this "You can route traffic from this rule's listener to different backend targets based on the URL path of the request. You can also apply a different set of Backend settings based on the URL path.". With this, I would go for 1 listener and 1 routing rule.

upvoted 4 times

...

JohnAvlakiotis

1 year, 8 months ago

I also went to the portal to deploy it, and there seems to be the only way to do that. Even if the listener is a wildcard listener you will not be able to split it to 2 different back end pools from the same listener IMHO

upvoted 4 times

Webesciaki

1 year, 1 month ago

agree - as we need to have 2 different backends we need 2 rules. You can't reuse listener for diff rule. so IMHO 2 rules and 2 listeners (multi site)

upvoted 1 times

...

TJ001

2 years ago

pls note if the no of site per app Service is 1 in that case also total no of routing rule will be 2. because the front end listeners are different and it is scenario of creating Basic site listener still requiring rule mapping per listener

upvoted 1 times

TJ001

2 years ago

small correction...in this case as well ...Multi site listener will be created and there is a sub option ... single site/multiple site within the Multi site selection..so both the case Multi site listener is created but there could be 1 or more sites within that selection

upvoted 2 times

...

ieboaix

1 year ago

the given answer is correct https://learn.microsoft.com/en-us/training/modules/configure-azure-application-gateway/3-determine-routing

upvoted 1 times

...

Zeppoonstream

Highly Voted 1 year, 9 months ago

what is meant by "You deploy an Azure 2" ??

upvoted 11 times

daemon101

1 year, 6 months ago

I guess it's supposed to be Application Gateway Standard V2

upvoted 8 times

...

sam881989

Most Recent 1 year ago

Was able to configure with 1 rule and 1 Listener. Also did multiple variations like adding 2 web apps in 2 different pools and 4 web apps in both the pools and still it worked with 1 rule and 1 listener. Had to use path based routing and multisite option to make it work!

upvoted 3 times

sam881989

1 year ago

Correction. The answer is correct. Path based routing does not work in this situation

upvoted 2 times

...

NSF2

1 year ago

I am quite agree with below, since it was tested in the lab. So the answer is not correct Listener: Create a single multi-site listener with the wildcard hostname configuration: Multi-site Listener: Hostname: *.contoso.com Routing rules: Create 4 routing rules to route requests to the respective backend pools based on the host header: Rule 1: Hostname: app1.contoso.com -> Backend pool (as1.contoso.com) Rule 2: Hostname: app2.contoso.com -> Backend pool (as1.contoso.com) Rule 3: Hostname: app3.contoso.com -> Backend pool (as2.contoso.com) Rule 4: Hostname: app4.contoso.com -> Backend pool (as2.contoso.com) By using a multi-site listener, you can minimize the number of listeners you need to configure: 1 multi-site listener 4 routing rules

upvoted 3 times

...

Lazylinux

1 year, 1 month ago

First for those mixing between Basic and multi-site If you create Basic listener than you will not be prompted to enter FQDN for that specific listener meaning that the App Gateway, will be listening to ONLY one Domain or sub-domain and NOTHING else and this is achieved by using DNS either A-record that points to IP address of the App-GWY or CNAME that points to FQDN of the App GWY If you chose multi-site (SINGLE) it means you are hosting more than 1 domain/subdomain (as the name indicates) and you can use A-record or CNAME as mentioned above, however the difference here is that each request is intercepted by App GWY and directed to the correct listener which in turn processed by the associated routing rule hence backend. Which is the case in this question. see below further

upvoted 3 times

Lazylinux

1 year, 1 month ago

Now if you chose Multi-site (Multiple/wildcard), this allows you to add upto 5 hostnames as most people have indicated in the posts, however what they are missing here is the fact you have two separate backend App services that service 2 hostnames each and hence even though we can use 5 hostnames, it is NOT possible to separate the backend using one listener or routing rule. The thing to remember routing rules and listener go in relation 1-1 and hence if a listener is already associated with one routing rule you CANNOT use it with another routing rule i.e. when you create routing rule, you will get this error “There are no unassociated listeners available. Create a new listener and then try again.” So we are here restricted by the fact we have 2 backends (App services) that respond to certain FQDN as per table in the question. See below Further

upvoted 5 times

Lazylinux

1 year, 1 month ago

Therefore we need 2 Multi-site (Multiple/wildcard) and 2 routing rules as per below Listener 1- Multi-site (Multiple/wildcard) Hostnames: app1.contoso.com and app2.contoso.com Backend1= As1.contoso.com RoutingRule1= Listener1+backend1 and httpseting1 with health probe Listener 2- Multi-site (Multiple/wildcard) Hostnames: app3.contoso.com and app4.contoso.com Backend2= As2.contoso.com RoutingRule2= Listener2+backend2 and httpseting1 with health probe See below further

upvoted 6 times

Lazylinux

1 year, 1 month ago

Note: You could use the same health probe and Https settings on differ listeners/routing rules if they are all same i.e. front port 43 and backend port is 43 Also if we did NOT have Multi-site (Multiple/wildcard) i.e. we have Multi-site (SINGLE) as per application Gateway version 1 then we would need 4 listeners and 4 routing rules with 2 backends because you can only have one hostname per listener and YES you can use wild card such as * but if you did like *.constoso.com or app*.contoso.com but you will have problem of directing all traffic to ONE BACKEND More info found here: https://learn.microsoft.com/en-us/azure/application-gateway/multiple-site-overview#allowed-characters-in-the-host-names-field

upvoted 2 times

sirio

12 months ago

But then the answer is 3 listeners and 3 routing rules if we consider to use multi-site with wildcard? Thanks

upvoted 3 times

...

IE17

1 year, 4 months ago

1 Multi-listener and 2 routing rules... https://learn.microsoft.com/en-us/azure/application-gateway/create-multiple-sites-portal

upvoted 1 times

c2e9cb4

1 year, 1 month ago

The URL is a good reference but on same url yo share they're showing 2 routing rule with a Distinct listenner for each rule 2Rules*1Listenner(each) = 2Listenner

upvoted 1 times

...

WMG

1 year, 9 months ago

Answer is wrong, created this setup in our lab environment. Read: https://learn.microsoft.com/en-us/azure/application-gateway/multiple-site-overview#wildcard-host-names-in-listener

upvoted 1 times

...

henryhung

1 year, 9 months ago

From ChatGPT Plus(GPT-4) You can use a multi-site listener to consolidate your configuration. A multi-site listener allows you to host multiple web apps on a single application gateway, routing requests based on the host header. In this case, you can create just one multi-site listener and configure the necessary routing rules. Listener: Create a single multi-site listener with the wildcard hostname configuration: Multi-site Listener: Hostname: *.contoso.com Routing rules: Create 4 routing rules to route requests to the respective backend pools based on the host header: Rule 1: Hostname: app1.contoso.com -> Backend pool (as1.contoso.com) Rule 2: Hostname: app2.contoso.com -> Backend pool (as1.contoso.com) Rule 3: Hostname: app3.contoso.com -> Backend pool (as2.contoso.com) Rule 4: Hostname: app4.contoso.com -> Backend pool (as2.contoso.com) By using a multi-site listener, you can minimize the number of listeners you need to configure: 1 multi-site listener 4 routing rules

upvoted 4 times

MrBlueSky

1 year, 9 months ago

You posting these ChatGPT answers is not helpful dude.

upvoted 30 times

Lazylinux

1 year, 1 month ago

Because he is dumplings!!

upvoted 1 times

getafix

5 months, 2 weeks ago

and you won all the wisdom trophies. Get over yourself and show some respect. Idiot

upvoted 1 times

...

drprepper_

1 year, 10 months ago

You only need 1 multi-site listener I think? https://learn.microsoft.com/en-us/azure/application-gateway/multiple-site-overview#wildcard-host-names-in-listener You can wildcard the start of the FQDN then just two routing rule 1 for each pool? So 1 and 2?

upvoted 5 times

wooyourdaddy

1 year, 10 months ago

I agree that it is 1 multi-site listener using either wildcard or up 5 hostnames as per the link you cited. Then it would be a routing rule for each backend, so 2 in total.

upvoted 2 times

...

flurgen248

1 year, 11 months ago

Answer is correct: https://learn.microsoft.com/en-us/azure/application-gateway/application-gateway-components#types-of-listeners Create a multi-site listener for each Azure App Service, and each listener needs one rule.

upvoted 1 times

...