Exam AZ-300 All Questions

View all questions & answers for the AZ-300 exam

Exam AZ-300 topic 2 question 43 discussion

Actual exam question from Microsoft's AZ-300

Question #: 43
Topic #: 2

You develop an entertainment application where users can buy and trade virtual real estate. The application must scale to support thousands of users.
The current architecture includes five Azure virtual machines (VM) that connect to an Azure SQL Database for account information and Azure Table Storage for backend services. A user interacts with these components in the cloud at any given time.
✑ Routing Service "" Routes a request to the appropriate service and must not persist data across sessions.
✑ Account Service "" Stores and manages all account information and authentication and requires data to persist across sessions
✑ User Service "" Stores and manages all user information and requires data to persist across sessions.
✑ Housing Network Service "" Stores and manages the current real-estate economy and requires data to persist across sessions.
✑ Trade Service "" Stores and manages virtual trade between accounts and requires data to persist across sessions.
Due to volatile user traffic, a microservices solution is selected for scale agility.
You need to migrate to a distributed microservices solution on Azure Service Fabric.
Solution: Deploy a Windows container to Azure Service Fabric for each component.
Does the solution meet the goal?

A. Yes
B. No

Show Suggested Answer

Suggested Answer: B 🗳️

by Musk at Dec. 8, 2019, 10:56 p.m.

Comments

Submit Cancel

bbbb

Highly Voted 5 years, 6 months ago

I think the reason the answer is NO is due to the routing service. It needs to be stateless so the suggested solution does not natively meet this requirement.

upvoted 17 times

...

Ekramy_Elnaggar

Highly Voted 5 years, 6 months ago

it is mentioned "Due to volatile user traffic, a microservices solution is selected for scale agility" , so we need to separate components as it might have different scalability requirements , so I guess it is A not B

upvoted 14 times

...

azurecert2021

Most Recent 4 years, 5 months ago

given answer is correct as Azure Service Fabric is a distributed systems platform for deploying and managing scalable and reliable microservices and containers. In Azure Service Fabric while writting reliable service we can make a choice of stateless or stateful. but there is no information about container whether thye are stateful or stateless but Deploy a Windows container to Azure Service Fabric for each component will not scale to support thousands of users so instead they should use Service Fabric managed cluster to scale out.

upvoted 1 times

...

azurecert2021

4 years, 5 months ago

Azure Service Fabric is a distributed systems platform for deploying and managing scalable and reliable microservices and containers. In Azure Service Fabric while writting reliable service we can make a choice of stateless or stateful. but there is no information about container whether thye are stateful or stateless but Deploy a Windows container to Azure Service Fabric for each component will not scale to support thousands of users so instead they should use Service Fabric managed cluster to scale out.

upvoted 1 times

...

umangsingh123

4 years, 9 months ago

It should be YES . As said on on Microsoft page "Service Fabric provides a sophisticated, lightweight runtime that supports stateless and stateful microservices"

upvoted 1 times

...

magpi

4 years, 9 months ago

Stateful environments can comprehend stateless applications. Not the best design, for sure, but it works.

upvoted 1 times

...

cttay71

4 years, 9 months ago

According to https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-containers-overview The container is stateful, Routing service needs to be stateless. My Answer is NO

upvoted 1 times

cttay71

4 years, 9 months ago

https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-application-and-service-manifests I think you can have stateful containers and stateless containers. Each questions say to have containers for each component, I would like to change my answer to YES

upvoted 1 times

...

BEB

4 years, 10 months ago

The Answer is B. Initially, they had 5 VMs==> redundancy. Now, they plan to use ONE container per Microservice/component.. there should at least be some level of autoscale added to the sentence. (especially that they are using the solution for scale agility). Otherwise, the fabric supports both Statefull and stateless (although microsoft, for good reasons, is paying special attention to stateful..

upvoted 1 times

...

Valica

4 years, 10 months ago

Service Fabric enables you to build applications that consist of microservices or containers. Stateless microservices (such as protocol gateways and web proxies) do not maintain a mutable state outside a request and its response from the service. Azure Cloud Services worker roles are an example of a stateless service. Stateful microservices (such as user accounts, databases, devices, shopping carts, and queues) maintain a mutable, authoritative state beyond the request and its response. Today's Internet-scale applications consist of a combination of stateless and stateful microservices. https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-overview

upvoted 1 times

wcj_55

4 years, 10 months ago

I am going with B (No). The scenario appears to have all of the needed solution components except for a place to store the containers. (Container Registry)

upvoted 1 times

...

Xanmorn

5 years ago

It is NO. Service Fabric has only Stateful containers so it does not work for the Stateless Routing Service. https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-overview

upvoted 3 times

jonnybugaloo

5 years ago

It should be yes, from your link: Service Fabric provides a sophisticated, lightweight runtime that supports stateless and stateful microservices. Since the questions inform Deploy a Windows Container for each component...

upvoted 4 times

...

JAWS1600

4 years, 11 months ago

Service Fabric enables you to build and manage scalable and reliable applications composed of microservices. These distributed microservices run at high density on a shared pool of machines, which is referred to as a cluster. Service Fabric provides a sophisticated, lightweight runtime that supports stateless and stateful microservices. https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-overview

upvoted 2 times

...

HariJakkula

5 years ago

Read the question carefully. "Deploy a Windows Container". Meaning one container to meet all the requirements. So the answer given here is correct. "No".

upvoted 1 times

jonnybugaloo

5 years ago

Read the question carefully. you forgot the FOR EACH COMPONENT part

upvoted 2 times

...

Prash85

5 years ago

answer should be YES

upvoted 1 times

...

tmurfet

5 years ago

"You need to migrate to a distributed microservices solution" -- IMO implies a container solution is wrong (even though containers can run microservices).

upvoted 2 times

tmurfet

4 years, 11 months ago

According to the following: "https://docs.microsoft.com/en-us/azure/container-instances/container-instances-volume-azure-files" linux containers can be stateful, not Windows containers.

upvoted 3 times

...

keithtemplin

5 years, 1 month ago

States a (as in single) windows container when the requirements call for a "microservices solution" which typically calls for separation.

upvoted 1 times

...

BeCalmAndSmile

5 years, 2 months ago

Should be YES. You can deploy existing applications as guest executables, Service Fabric stateless or stateful Reliable services or Reliable Actors in containers, and you can mix services in processes and services in containers in the same application.

upvoted 3 times

...

Famous_Guy

5 years, 2 months ago

answer is YES because you need separate containers for Stateless Services and Stateful Services

upvoted 4 times

...

Khang

5 years, 3 months ago

B is correct. Since routing service is stateless

upvoted 6 times

...

Load full discussion...