Your company, named Contoso, Ltd, has an Azure subscription that contains the resources show in the following table.

You plan to deploy Azure Front Door. The solution must meet the following requirement:
* Requests to a URL of https://contoso.azurefd.net/uk must be routed to App1uk.
* Requests to a URL of https://contoso.azurefd.net/us must be routed to App1us.
* Requests to a URL of https://contoso.azurefd.net/images must be routed to the storage account closest to the user.
What is the minimum number of backend pools and routing rules you should create? To answer, the appropriate number to the correct component. Each number may be used once, more than once, or not at all.
You may need to drag the spilt bar between panes scroll to view content:
Note: Each correct selection is worth one point.

Recent Comments (The most recent comments are at the top.)
3 Backend Pools | 3 Rules
I believe this is a Classic Front Door question. The first reference link provides an overview of classic routing. The questions shows we have a single frontend (contoso.azurefd.net) and there are three paths - /uk, /us, and /images.
The second link shows the three paths would each be a separate rule.
Regarding the number of backend pools, the question states, "...must be routed to [App1uk or App1us]" for the two App Services. The third link does not indicate there is a way to route traffic to a specific app service based on location. However, if we put each app service in its own backend pool, we can have the path rule route to the correct App Service everytime. The Latency routing logic is fine for storage accounts, but not the App Services based on the question requirements.
References
https://learn.microsoft.com/en-us/azure/frontdoor/front-door-routing-architecture?pivots=front-door-classic
https://learn.microsoft.com/en-us/azure/frontdoor/front-door-route-matching?pivots=front-door-classic#frontend-host-matching
https://learn.microsoft.com/en-us/azure/frontdoor/routing-methods...