HOTSPOT - You design a solution for the web tier of WebApp1 as shown in the exhibit. For each of the following statements, select Yes if the statement is true. Otherwise, select No. NOTE: Each correct selection is worth one point. Hot Area:
Suggested Answer:
Box 1: Yes - Any new deployments to Azure must be redundant in case an Azure region fails. Traffic Manager is resilient to failure, including the failure of an entire Azure region.
Box 2: No - Traffic Manager provides load balancing, but not auto-scaling.
Box 3: No - Automatic failover using Azure Traffic Manager: when you have complex architectures and multiple sets of resources capable of performing the same function, you can configure Azure Traffic Manager (based on DNS) to check the health of your resources and route the traffic from the non-healthy resource to the healthy resource. Reference: https://docs.microsoft.com/en-us/azure/traffic-manager/traffic-manager-overview https://docs.microsoft.com/en-us/azure/networking/disaster-recovery-dns-traffic-manager
Should be Y,Y,N
(Yes) Traffic manager distributes load to two sites (redundancy). (Yes) The graphic clearly shows an "Azure Web App", which is production. By default, production web apps support auto scale. (No) Azure Traffic manager does automatic failover, so no manual configuration is necessary.
YYN
"In this way, the App Service plan is the scale unit of the App Service apps. If the plan is configured to run five VM instances, then all apps in the plan run on all five instances. If the plan is configured for autoscaling, then all apps in the plan are scaled out together based on the autoscale settings."
https://learn.microsoft.com/en-us/azure/app-service/overview-hosting-plans
YYN, with Std Web App plan you get autoscale vertical and horizontal.
https://learn.microsoft.com/en-us/azure/app-service/manage-scale-up
https://azure.microsoft.com/en-us/pricing/details/app-service/windows/
Since the question says whether the design supports auto scaling since it is Azure Web App it supports auto scaling and doesn't matter whether it is configured or defaulted to manual or not. So the answer should be Y,Y,N
YYN, Dont ask me why, because I am magician.
Traffic Manager is based on DNS routing which means is redundant, also it provides automaic failover in case of regional outage
By default, Azure App Service is configured with manual scaling. This means that when you initially deploy an App Service, you would need to manually specify the number of instances to run your app on. Since the diagram doesn't indicate whether autoscaling is configured, and because manual scaling is the default, we assume that the design does not automatically support autoscaling unless otherwise stated. so it is YNN
In my opinion answer is correct.
1. Y - TM supports here a redundancy. We have two regions and we can add more if it is necessary.
2. No - TM has nothing to do with autoscaling. Autoscaling is on AppService level. Design as a whole has nothing with that.
3. No - if azure region fails no need to do anything manual.
I will go for YYN
1- Y - Yep all requirements are met
2- Y - All app service STD and onwards support auto-scaling
3- N - Because Traffic Manager DNS-based traffic load balancer => using Endpoints, in this case of type Azure and target type App services, then routing method in this case you could use either weighted or priority - preferably weighted with 1 and 1 hence equal workload and if one fails then routed to the other, if priority is used then 1 and 2 assigned but one assigned 1 will do all work and if fails then other region kicks in, of course other routing methods are performance, subnet, Multivalue, Geographic - really more info required to chose the correct one
Y,Y,N
"Whenever possible, solutions must be deployed to Azure by using the Standard pricing tier of Azure App Service."
- Standard Plan supports auto-scaling up to 10 instances.
YNN , let's end the discussion guys:
1. Y for obvious reasons I can't bother explaining
2. N autoscaling web apps are in preview mode so you absolutely should not use this in production as of August 2023, PERIOD!
3. N it will auto fail-over same behavior as with AWS route 53
Should be Y N N:
Y - Redundancy is okay, we have two regions
N - Azure Web App means nothing. There are different plans in Azure App Plan. Plans Standard and above provides autoscale. Basic plan does not. We can't assume they have Standard or Premium plan.
No - No auto failover
"We can't assume they have Standard or Premium plan" - you don't need to.
You just need to read the actual problem and you will find out you are told specifically to deploy using Standard whenever possible.
Yes, we can assume it is Standard plan.
"Whenever possible, solutions must be deployed to Azure by using the Standard pricing tier of Azure App Service."
I think YYN
Same question as AZ-304
https://www.examtopics.com/discussions/microsoft/view/49469-exam-az-304-topic-13-question-2-discussion/
And the answer provided is YYN and all comment sections agrees.
So the problem is with the wording of the question? We all agree TM doesn't provide auto scale and webapp does, so its a question of whether you are looking at the design as a whole or only at TM. I am inclined towards design as a whole.
All 3 statements specifically state "The design ... blah". The entire picture = the design. No problem here, and it's not ""a question of whether you look at the design as a whole or only TM".
gentlemen I have counted the questions of this dump, from the first of the topic 1 to the last of T16 - 1 There are 202 questions and not 209, moderator at least tell the questions.
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
ezfix
Highly Voted 2 years, 2 months agoBartol0
Highly Voted 2 years, 2 months agoGalron
2 years, 1 month agoSeMo0o0o0o
Most Recent 3 weeks, 6 days agoSIJUTHOMASP
1 month, 2 weeks ago_punky_
1 month, 2 weeks agocosmicT73
1 month, 4 weeks agoprofesorklaus
4 months, 2 weeks agoLazylinux
7 months, 2 weeks agomanemanevski123
9 months, 1 week agoSDiwan
9 months, 3 weeks agoziggy1117
1 year agobabakeyfgir
1 year agojojorabbit2021
1 year, 3 months agosawanti
1 year, 3 months agorishisoft1
8 months, 3 weeks agoxRiot007
9 months agomarcellov
1 year, 2 months agosawanti
1 year, 3 months agoInvalidNickname
1 year, 4 months agoyonie
1 year, 7 months agoAdventureChick
1 year, 2 months agoRogercampos
1 year, 9 months ago