DRAG DROP -
You have virtual machines (VMs) that run a mission-critical application.
You need to ensure that the VMs never experience down time.
What should you recommend? To answer, drag the appropriate solutions to the correct scenarios. Each solution may be used once, more than once, or not at all.
You may need to drag the split bar between panes or scroll to view content.
NOTE: Each correct selection is worth one point.
Select and Place:
Box 1: Scale set -
A virtual machine scale set allows you to deploy and manage a set of identical, autoscaling virtual machines.
Box 2: Availability Set -
An Availability Set is a logical grouping capability for isolating VM resources from each other when they're deployed. Azure makes sure that the VMs you place within an Availability Set run across multiple physical servers, compute racks, storage units, and network switches. If a hardware or software failure happens, only a subset of your VMs are impacted and your overall solution stays operational. Availability Sets are essential for building reliable cloud solutions.
Box 3: Fault domain -
A fault domain is a logical group of underlying hardware that share a common power source and network switch, similar to a rack within an on-premises datacenter. As you create VMs within an availability set, the Azure platform automatically distributes your VMs across these fault domains. This approach limits the impact of potential physical hardware failures, network outages, or power interruptions.
Incorrect Answers:
An update domain is a group of VMs and underlying physical hardware that can be rebooted at the same time.
References:
https://docs.microsoft.com/en-us/azure/virtual-machines/windows/tutorial-create-vmss https://docs.microsoft.com/en-us/azure/virtual-machines/windows/tutorial-availability-sets
Answer: 1: Scale set 2:Availability zone (not given in option) 3:Availability set
Good Catch
Not agree. Scale set, Fault domain, Availability set.
for Box 2 -> Scale Sets - To protect your virtual machine scale sets from datacenter-level failures, you can create a scale set across Availability Zones. https://docs.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-use-availability-zones
Yes, Because there isn't Availability Zones as answer option the only one possibile is Scale Sets spread across different Availability Zones.
Correct Single-zone and zone-redundant scale sets: When you deploy a virtual machine scale set, you can choose to use a single Availability Zone in a region, or multiple zones. When you create a scale set in a single zone, you control which zone all those VM instances run in, and the scale set is managed and autoscales only within that zone. A zone-redundant scale set lets you create a single scale set that spans multiple zones. As VM instances are created, by default they are evenly balanced across zones.
This line is to protect scale-set. but here question is to protect virtual machine. So your given answer is wrong.
Correct answers: Maintain application performance across identical VMs: Scale Set Maintain application availability when an Azure datacenter fails: Availability Zone Maintain application performance across different VMs: Availability Set
repeat question https://www.examtopics.com/exams/microsoft/az-303/view/5/ question no 45 Correct Answer is Scale sets, Availability Zone and Availability Sets Scale Sets - identical VMs in auto scaling Availability Zone - when an data center fails. Availability sets are for when underlying physical server or power supply fails within a data center. Availability Sets - Fault Domain is not a solution but a feature within availability set incase of planned maintenance like server patching. Credit deepbond
Availability set is within DC whereas AZs are across DCs. The given answer choices are wrong
Box 1 Scale Set, Box 3 - Avail set, For Box 2 no answer might be Avail Zone. See comments in https://www.examtopics.com/discussions/microsoft/view/38152-exam-az-303-topic-1-question-45-discussion/
On exam today 22/11/21 Score 839
I would go Scale set for Q3, from a read they can work with pre-existing, different spec VMs. And availability set is for availability, not performance. Also as vharsh16 said, Q2 should be availability zone, maybe it's best to forget this question!
Feel like Availability Zones should be an option here but in its absence: Maintain appliccation performance - Scale Sets Maintain application availability when AZ DC is down - Scales Sets (configured for multiple availabilty zones) Maintain Application performance accros differnt VMs - currently Scales Sets do not support diffrent VMs, although this is coming....so Availability Sets for this one.