Process of elimination here:
A. Wrong. Scale up would cause disruption since you resizing a live webapp, scale out makes more sense
B. Wrong. Why use a VM scale set for a web app, solution must minimise costs therefore a web app is more cost effective.
C. Wrong. Un-necessary disruption for not much benefit. True autoscaling would be more cost effective since it can run 24/7
D. This will work
A. Configure the Scale Up settings for a web app ❌
Scaling up increases the power of individual instances, which increases costs rather than minimizing them.
B. Deploy a virtual machine scale set that scales out on a 75 percent CPU threshold ❌
Using VM scale sets requires managing infrastructure, which is more expensive than using Azure App Service with auto-scaling.
C. Create a runbook that resizes virtual machines automatically to a smaller size outside of business hours ❌
This approach is more applicable to VM-based environments rather than PaaS-based web apps, and it doesn't provide dynamic scaling during business hours.
Thus, Option D (Scale Out settings for a web app) is the most cost-effective solution
i think answer C is correct.
Reason :- Scale out, you need "Standard","Premium v2 Service Plan" or "Premium v3 Service Plan" , none is mentioned in case study.
https://azure.microsoft.com/en-us/pricing/details/app-service/windows/
"Whenever possible, solutions must be deployed to Azure by using the Standard pricing tier of Azure App Service."
This would leave D as the answer since scaling up would require downtime which is not what the qn wants
Okay you scale out but where is your scale in rule?
All the options talking about scaling out/scale set but not mentioning anything about scaling in so no I would go with C the correct answer.
Indeed all the answers are incomplete. A, B and D scale only out/up but never in/down. C reduces the number of nodes but never increases it.
Ignoring that, I'd go for D.
A - Scale Up requires reboot, thus downtime, not ideal
B - VMSS would make sense if app would run on VMs. But we're supposed to use "the Standard pricing tier of Azure App Service," which seems possible here as the app is currently running on IIS.
C - Custom runbook seems not an adequate option for any scenario.
D - Scale Out -> should do the trick
According to: "Whenever possible, solutions must be deployed to Azure by using the Standard pricing tier of Azure App Service" we have to discard IAAS (App Service) and Discard "Scale Up" (standard tier) Response: D Configure Scale Out for web app
in the question:
Whenever possible, solutions must be deployed to Azure by using the Standard pricing tier of Azure App Service.
solution: scale set :|
This section is not available anymore. Please use the main Exam Page.AZ-304 Exam Questions
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
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.
norbitek
Highly Voted 3 years, 9 months agoBoxGhost
Highly Voted 3 years, 7 months agompeh95
Most Recent 4 weeks, 1 day agosapien45
2 years, 10 months agoAzureExpertwannabe
3 years, 3 months agoDpejic
3 years, 4 months agodonathon
3 years, 4 months agoabullones
3 years, 5 months agostudent22
3 years, 5 months agochichi0307
3 years, 6 months agochichi0307
3 years, 6 months agosyu31svc
3 years, 6 months agosouvik123
3 years, 7 months agojamess
3 years, 8 months agoWard
3 years, 8 months agopentium75
3 years, 8 months agoEl_Hechizo
3 years, 8 months agog_db1
3 years, 8 months agog_db1
3 years, 8 months agotvs2021
3 years, 9 months agohoangton
3 years, 8 months ago