mcAfee Secure Website
23

Microsoft AZ-104 Bundle

Exam Code: AZ-104

Exam Name Microsoft Azure Administrator

Certification Provider: Microsoft

Corresponding Certification: Microsoft Certified: Azure Administrator Associate

AZ-104 Training Materials $44.99

Reliable & Actual Study Materials for AZ-104 Exam Success

The Latest AZ-104 Exam Questions as Experienced in the Actual Test!

  • 24
    Questions & Answers

    AZ-104 Questions & Answers

    606 Questions & Answers

    Includes questions types found on actual exam such as drag and drop, simulation, type in, and fill in the blank.

  • 25
    AZ-104 Video Course

    AZ-104 Training Course

    132 Video Lectures

    Based on Real Life Scenarios which you will encounter in exam and learn by working with real equipment.

  • exam =30
    Study Guide

    AZ-104 Study Guide

    458 PDF Pages

    Study Guide developed by industry experts who have written exams in the past. They are technology-specific IT certification researchers with at least a decade of experience at Fortune 500 companies.

exam =32

Microsoft Azure Administrator (AZ-104) Practice Tests

Guarantee

Satisfaction Guaranteed

Pass4sure has a remarkable Microsoft Candidate Success record. We're confident of our products and provide no hassle product exchange. That's how confident we are!

99.3% Pass Rate
Total Cost: $194.97
Bundle Price: $149.98

Purchase Individually

  • exam =34
    Questions & Answers

    Questions & Answers

    606 Questions

    $124.99
    exam =35
  • exam =37
    AZ-104 Video Course

    Training Course

    132 Video Lectures

    $39.99
  • exam =36
    Study Guide

    Study Guide

    458 PDF Pages

    $29.99

Microsoft AZ-104 Practice Test 52

Question 510

Two tiers of a legacy app use a classic availability set in Azure region eastus; the application tier currently has only one VM in that set and its load balancer has no second backend target. The operator must protect against host failure within the regional availability-set design rather than implement autoscaling. What is the most direct correction?

  1. Create an automatic VM scale set and abandon the existing availability set, although no elastic-capacity requirement exists.
  2. Add only a load-balancer frontend IP without creating another running application VM.
  3. Add a second application VM in the same availability set and include both healthy replicas in the suitable load-balancer backend pool.
  4. Assign a ReadOnly Azure management lock to the single VM so Azure places it into two fault domains.

Explanation

Correct Answer

C:

An availability set spreads multiple VM instances across fault and update domains to reduce correlated maintenance and hardware exposure. With only one VM, no alternate application instance exists when the first fails. Deploying another replica into that same availability set and configuring a suitable health-probed load-balancer backend provides actual instance redundancy. Confirm that application data/session handling supports a second instance and that both VMs can serve requests before relying on the improved availability.

Incorrect Answers

A:

A VM scale set can provide scalable redundant compute, but replacing an established legacy availability-set deployment is not the direct requirement when capacity elasticity is explicitly out of scope. The existing set can accommodate more than one application VM. Adding a redundant replica within that supported topology is the minimal targeted correction.

B:

A load-balancer frontend with only one backend instance does not create a failover path if that VM fails. The frontend can direct traffic only to configured and healthy backend targets, so an additional VM and correct pool membership are required. Merely changing a virtual IP cannot produce application availability.

D:

Management locks control resource changes through Azure Resource Manager; they do not clone VMs, distribute one VM over multiple physical fault domains or protect it from hardware loss. The single-instance application would still have a single compute point of failure. Add a real second VM rather than a control-plane lock.

Question 511

A workload has healthy VM replicas across three zones, but customers connect directly to the public IP of one VM. Which configuration makes clients use surviving replicas when that VM fails?

  1. Add an Azure management lock to the single advertised VM address.
  2. Provide a health-probed load-balanced frontend across the zonal VM replicas and point clients to it.
  3. Assign the VM identity an Azure Monitor Reader role.
  4. Create a zone-redundant disk for the VM that still receives all traffic.

Explanation

Correct Answer

B:

A load balancer frontend can distribute client flows among healthy replicas so a single failed zone/instance does not remain the sole target.

Incorrect Answers

A:

A management lock cannot redirect network flows when the target compute instance is unavailable.

C:

Monitoring permissions enable insight, not application-level failover routing.

D:

A replicated disk does not make traffic to one failed VM reach independent running compute.

Question 512

An Azure application VM in zone 1 has become inaccessible during an availability-zone outage. Its business data is on a supported zone-redundant (ZRS) managed data disk, and a compatible standby VM already runs in zone 2. The incident team needs access to the disk data before zone 1 recovers. Which supported recovery action directly uses the ZRS data disk?

  1. Force detach the ZRS data disk from the unavailable VM, attach it to the compatible VM in zone 2, and validate filesystem/application state before resuming service.
  2. Assume ZRS automatically moves the original VM, its NIC and its guest processes to zone 2 as soon as an outage starts.
  3. Convert the ZRS data disk to an LRS disk in the failed zone and attach it to a zone-2 VM, because only LRS supports recovery.
  4. Create a public DNS CNAME to the original VM resource ID; DNS resolution causes Azure to move its ZRS disk to another availability zone.

Explanation

Correct Answer

A:

Microsoft documents force detach for supported ZRS managed data disks when the attached VM is affected by a zonal outage. Detach the data disk from the failed VM and attach it to an eligible VM in the surviving zone; disk availability does not by itself guarantee application recovery, so validate the mounted data and service.

Incorrect Answers

B:

ZRS synchronously replicates the managed disk data across zones, not the running virtual machine, NIC or operating-system processes. Recovery of affected compute requires a separate VM or workload procedure.

C:

ZRS provides cross-zone disk durability and access. Converting to LRS in the failed zone would reduce resiliency and is unnecessary for attaching a supported ZRS data disk to another zone. Force detach applies to supported data disks, not arbitrary VM OS disks.

D:

DNS records control name resolution, not disk attachment or VM recovery. An Azure VM resource ID is not a mechanism that reassigns ZRS disk ownership or makes a failed VM run in another zone.

Question 513

A service design claims high availability because VMs are spread across zones. Operations must PROVE end-to-end service continuity. What test is essential?

  1. Check only that three availability-zone labels exist in the portal.
  2. Increase the OS disk capacity on every VM.
  3. Change all VM public IPs to static without testing backend health.
  4. Conduct a controlled failover simulation verifying the application, probes, routing and state recovery.

Explanation

Correct Answer

D:

A controlled failure exercise tests real application availability, including traffic distribution and state recovery behavior.

Incorrect Answers

A:

Placement metadata is not evidence that client traffic and state survive a replica or zone failure.

B:

More disk capacity does not prove the application handles failed instances.

C:

Static IP allocation alone does not verify request routing, state continuity or load-balancer health.

Question 514

An existing VM Scale Set should grow from three instances when average CPU exceeds a defined threshold for a specified window. Which configuration is required?

  1. Increase a storage account’s throughput quota.
  2. Change the DNS TTL for the scale set’s public hostname.
  3. Configure an autoscale metric rule using Percentage CPU, a scale-out action and appropriate cooldown.
  4. Configure a VM availability set but no metric threshold.

Explanation

Correct Answer

C:

VMSS autoscale evaluates CPU metrics, aggregation/window thresholds, scaling actions and cooldown.

Incorrect Answers

A:

Storage account performance settings do not trigger VM Scale Set instance changes.

B:

DNS caching does not govern Azure autoscale actions.

D:

Availability sets control host placement; they do not define elastic capacity policy.

Question 515

A VM Scale Set shrinks after load falls but immediately scales back out repeatedly near the CPU threshold. Which settings reduce oscillation?

  1. Tune scale-in and scale-out thresholds/windows with appropriate cooldown and instance minimums.
  2. Increase the public IP DNS TTL only.
  3. Delete the autoscale setting but expect automatic resizing to continue.
  4. Change the VM disk encryption key to slow down scaling.

Explanation

Correct Answer

A:

Separate thresholds, stable evaluation periods and cooldown reduce rapid cycling near a noisy CPU boundary.

Incorrect Answers

B:

DNS cache duration does not alter metric-driven replica count decisions.

C:

Removing autoscale settings disables the intended automated behavior.

D:

Disk encryption does not provide an autoscale hysteresis or cooldown policy.

Question 516

A VM Scale Set image was updated, but the team needs controlled rollout to existing instances without updating every VM at once. What should be selected?

  1. Assign a storage blob lifecycle policy to the VMSS resource group.
  2. Select an appropriate rolling upgrade policy and validate the health and batching settings.
  3. Use an availability set instead of a VMSS to apply an image model change.
  4. Change the external DNS record before triggering any scale set instance upgrade.

Explanation

Correct Answer

B:

VMSS upgrade policies control propagation of updated instance models, including rolling batches and health behavior.

Incorrect Answers

A:

Blob lifecycle rules automate object tiering/deletion and do not roll VM images.

C:

Availability sets do not implement VMSS image model rollout.

D:

DNS configuration alone cannot apply a new VM image to running scale set instances.

Question 517

A critical VM Scale Set must retain at least THREE running workers even when traffic is zero. Which autoscale parameter enforces the baseline?

  1. Set maximum replicas to three and leave minimum at zero.
  2. Use a CPU scale-in rule with no lower boundary.
  3. Reduce the health-probe interval without defining a minimum capacity.
  4. Set autoscale profile minimum instance count to three.

Explanation

Correct Answer

D:

The autoscale minimum capacity ensures a VMSS will not intentionally scale below three instances.

Incorrect Answers

A:

A maximum limit caps capacity but does not guarantee any running baseline when the minimum permits zero.

B:

A scale-in action without a floor can reduce below the required safety capacity.

C:

Probe frequency affects health detection, not the autoscale lower bound.

Question 518

A VM Scale Set needs TEN instances on weekdays from 09:00 through 18:00, but a lower capacity outside that time. Which autoscale feature directly implements this?

  1. Create recurring schedule-based profiles for the specified hours and corresponding instance counts.
  2. Increase the VM’s local temporary disk capacity at 09:00.
  3. Modify a CPU scale-out threshold and assume it always triggers precisely at 09:00.
  4. Publish a CNAME record during business hours.

Explanation

Correct Answer

A:

Scheduled VMSS autoscale conditions support specified time windows and desired capacity profiles.

Incorrect Answers

B:

Local disk capacity cannot schedule replica changes for predictable hours.

C:

CPU-based rules react to measured demand rather than guaranteeing exact clock-time capacity.

D:

DNS records do not command VMSS instance count.

Question 519

An Azure VM Scale Set uses rolling upgrades. Operations must prevent an unhealthy application instance from being promoted in a rolling batch. Which health configuration provides the required signal?

  1. Configure a supported Application Health extension with an application endpoint/protocol and use its health state for the rolling upgrade.
  2. Add only a resource-group tag called AppHealth and assume rolling upgrades read it.
  3. Disable the application probe and use a storage account replication status as VM health.
  4. Change the scale set custom DNS hostname to mark every instance healthy.

Explanation

Correct Answer

A:

The Application Health extension probes the running application and supplies instance health status used to gate rolling upgrades.

Incorrect Answers

B:

Resource tags are metadata and do not supply VMSS instance application-health probe results.

C:

Storage account replication health does not check whether a VMSS application instance starts correctly or responds to requests.

D:

DNS aliases do not prove per-instance app health and cannot replace VMSS rolling-upgrade probe state.

Question 520

A team deployed six standalone Azure VMs but expects a VMSS autoscale setting to add or remove them as a group. What is required?

  1. Add the same resource-group tag to standalone VMs and keep them outside any VMSS.
  2. Deploy and manage the workload through a supported Virtual Machine Scale Set with an instance scaling profile.
  3. Create an availability set containing the standalone VMs and automatically inherit VMSS autoscale.
  4. Create a single load-balancer frontend but never configure a scale-set resource.

Explanation

Correct Answer

B:

Azure autoscale acts on scale-set capacity defined by a VMSS resource, not independent VM resources.

Incorrect Answers

A:

Matching tags do not enroll standalone VMs in a VMSS model or scaling group.

C:

Availability sets spread placement across domains but are not VMSS instance-scaling controllers.

D:

A load balancer can distribute requests, but does not by itself dynamically create or delete standalone VMs.