HOTSPOT
You deploy a Web App to Azure. The Web App uses several Basic tier, single instance virtual machines (Vms).
The App includes a web tier, services tier, data tier, and a compute-intensive processing tier, as shown in the
following diagram:
You have the following requirements:
The application must be available during all Azure platform events, including planned (VM restarts required)
and unplanned (hardware failure) events.
You must simplify VM deployments by using JSON templates and the Azure Resource Manager (ARM).
The processing tier must support high volume CPU loads at peak times throughout the year.
The web tier must support high volumes of incoming Internet traffic during peak times throughout the year.
The company has authorized downtime for the infrastructure upgrades. Future updates must not include
downtime.
The infrastructure upgrades must provide the most economical solution while meeting all requirements.
Users report application outages during planned Azure maintenance windows. You plan to upgrade the
application to support upcoming company initiatives as well as address the user reports.
You need to upgrade the application and infrastructure.
For each tier, which action should you perform? To answer, select the appropriate action from each list in the
answer area.
Hot Area:

Explanation:
Web tier: Use 2 Standard tier VMs in a new availability set, load balanced with Azure Load Balancer.
The web tier must support high volumes of incoming Internet traffic during peak times throughout the year.
Services: Use 2 Standard Tier VM in a new availability set.
Data: Use 2 Standard tier VMs contained within the services tier availability set.
Processing: Use 2 Dv2-series Vms in a new scale set.
The processing tier must support high volume CPU loads at peak times throughout the year.
Dv2-series, a follow-on to the original D-series, features a more powerful CPU. The Dv2-series CPU is about
35% faster than the D-series CPU.
Automatic scaling of virtual machines in a scale set is the creation or deletion of machines in the set as needed
to match performance requirements. As the volume of work grows, an application may require additional
resources to enable it to effectively perform tasks.https://docs.microsoft.com/en-us/azure/virtual-machines/virtual-machines-windows-sizes
https://docs.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-autoscale-overview
I think the data tier should “use 2 standard tier VMs in a new availability set”, don’t understand why need to included in services tier’s availability set?
1
0
Agreed
0
0
the question says “The infrastructure upgrades must provide the most economical solution while meeting all requirements”. so its cheaper to put The Data TIer in the same availability set as the services. The requirements will still be met
0
0
I respectfully disagree. You can only control the number of fault and update domains but not the actual placement of any particular VM within an availability set. VMs are automatically allocated to fault and update domains by Azure.
-> If you place two different tiers in the same availability set, all virtual machines in the same application tier can be rebooted at once.
-> You have to place different tiers in different availability sets, as also recommended in the documentation:
https://docs.microsoft.com/en-us/azure/virtual-machines/windows/manage-availability#configure-each-application-tier-into-separate-availability-sets
1
0
yep, each one should get its own availability set.
0
0
VM Scale Sets are are also availability sets.
A scale set is an implicit availability set with 5 fault domains and 5 update domains.
https://docs.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-overview#frequently-asked-questions-for-scale-sets
0
0
BTW, part of new 243Q 70-533 dumps are available here:
https://drive.google.com/open?id=0B-ob6L_QjGLpfnV3MVl6X3pXOWw1Z3YtQUpJRVRiTkNkbGNFbVBNRXhjSkw3bWk1WHdYcW8
Best Regards!
0
0