Exam AZ-300 All Questions

View all questions & answers for the AZ-300 exam

Exam AZ-300 topic 3 question 1 discussion

Actual exam question from Microsoft's AZ-300

Question #: 1
Topic #: 3

You have an Azure App Service API that allows users to upload documents to the cloud with a mobile device. A mobile app connects to the service by using
REST API calls.
When a new document is uploaded to the service, the service extracts the document metadata. Usage statistics for the app show significant increases in app usage.
The extraction process is CPU-intensive. You plan to modify the API to use a queue.
You need to ensure that the solution scales, handles request spikes, and reduces costs between request spikes.
What should you do?

A. Configure a CPU Optimized virtual machine (VM) and install the Web App service on the new instance.
B. Configure a series of CPU Optimized virtual machine (VM) instances and install extraction logic to process a queue.
C. Move the extraction logic into an Azure Function. Create a queue triggered function to process the queue.
D. Configure Azure Container Service to retrieve items from a queue and run across a pool of virtual machine (VM) nodes using the extraction logic.

Show Suggested Answer

Suggested Answer: C 🗳️

by kpham at May 6, 2020, 11:57 a.m.

Comments

Submit Cancel

zanhsieh

Highly Voted 5 years ago

I will pick Option C. A single CPU Optimized VM cannot handle solution scale - the scale means horizontal scale, not vertical scale - so option A is out. A series CPU Optimized VMs doesn't fit 'reduce costs between request spikes' since they are always on. Turn some of VMs off cannot handle spike well. So option B is off. Option D are similar to Option B but Microsoft tried to loot you with ACS on VMs. Although ACS (deprecated?) might have quickier warm up time, but VMs scaling is still a problem related to cost. Also Option C will be cost less than Option D since the customer does not need to maintain a single VM at all.

upvoted 8 times

...

AhmedAL

Most Recent 4 years, 8 months ago

c is correct to me as its expensive operation that is somehow independent fro the rest of the app - based on a lot of assumptions I am making :) but this is more of an application architecture question type that I deal with every day

upvoted 2 times

...

BOC

4 years, 9 months ago

C is the correct answer - Azure function reduces cost as it is stateless

upvoted 2 times

...

tjohn

4 years, 10 months ago

Answer is C REST API is called by the Mobile app. The REST API, just drops the request in an Azure queue. The Queue insertion triggers an Azure Function, which takes whatever time needed. After completion the success or failure response is captured and things are complete.

upvoted 2 times

...

Ashwinee

5 years ago

Azure function app has time limit. It is mentioned that the process is CPU intensive. Is it right solution.

upvoted 1 times

BiggusJiggus

4 years, 11 months ago

Better than any other answer here from a cost perspective

upvoted 2 times

thisexaminer

4 years, 9 months ago

I'm mostly upvoting you for your name. BiggusJiggus... awesome

upvoted 2 times

...

aurora21

4 years, 11 months ago

CPU intensive for possible a short period of time and hence Azure Function

upvoted 1 times

...

WassWave

4 years, 10 months ago

If you use a premium plan for your function you will have an unlimited execution time plus the auto scale feature

upvoted 1 times

...

Zixxer2Go

5 years, 1 month ago

Not an expert (yet), but my understanding would be: 1) a VM requirement is not mentioned, and serverless technology is built for Functions like this, 2) spikes in traffic are a fundamental advantage of serverless apps...they only "cost money" when they are triggered. A single VM or group of VM's present a continuous cost scenario.

upvoted 1 times

...

RegisK

5 years, 1 month ago

Azure function reduce costs as it is stateless

upvoted 2 times

...

kpham

5 years, 1 month ago

Explain please

upvoted 2 times

SIDNEY1

5 years, 1 month ago

I don't know a lot about the App Service, and I may be wrong in my explanation but here it is anyway. The only likely answer, IMO, is C. The others answer choices are about VMs, which don't present the scalable option the scenario's after. Azure Functions provides that true ability scale without the administrative overhead of VMs. So, it'd be best to move the logic into an AZ Function and let it do it.

upvoted 1 times

tartar

4 years, 9 months ago

C is ok

upvoted 2 times

...

AnshMan

5 years, 1 month ago

https://docs.microsoft.com/en-us/azure/azure-functions/functions-bindings-storage-queue-trigger?tabs=csharp

upvoted 1 times

...