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 51

Question 500

A VM data disk needs Azure Storage server-side encryption with a customer-managed Key Vault key, not guest BitLocker. Which component should be configured?

  1. An Azure Network Security Group attached to the data disk.
  2. A VM availability set with more update domains.
  3. A disk encryption set backed by the approved Key Vault key and identity permissions, used by the managed disk.
  4. A Blob container stored access policy controlling SAS expiry.

Explanation

Correct Answer

C:

A disk encryption set is the server-side managed-disk mechanism for customer-managed keys and requires access to the key.

Incorrect Answers

A:

NSGs govern network traffic and cannot select a managed disk encryption key.

B:

Availability sets determine host placement and maintenance distribution, not cryptographic key selection.

D:

SAS delegation relates to object storage data requests and cannot encrypt a VM managed disk with a customer key.

Question 501

A managed data disk remains attached to an Azure VM, but Linux mounts the filesystem read-only after errors. What is the right troubleshooting boundary?

  1. Add an Azure subscription Owner role to the guest user as a filesystem repair.
  2. Increase DNS TTL for the VM hostname.
  3. Create a new Azure public IP for the disk.
  4. Inspect guest filesystem health, device mount options and relevant Azure disk access state before changing roles.

Explanation

Correct Answer

D:

The guest may remount read-only after filesystem/storage errors; inspect logs, filesystem and device state at the correct layer.

Incorrect Answers

A:

Guest filesystem read-only remounts are not normally repaired by Azure control-plane RBAC grants.

B:

DNS TTL affects name resolution, not an attached filesystem’s write state.

C:

Public IP configuration does not alter the storage device or its mount mode.

Question 502

An enterprise deploys Azure VMs in the same region but under two different subscriptions. Both teams select availability zone 1 and assume this means the VMs occupy the same physical datacenter. Before approving that co-location claim, which Azure configuration fact should be checked?

  1. Compare each subscription’s logical-to-physical availability-zone mapping using the supported Azure location or zone-peers APIs, because logical zone numbers can map to different physical zones.
  2. Accept the claim without inspection because every Azure subscription maps logical zone 1 to the same physical facility in that region.
  3. Add matching physicalZone tags on the two VMs; VM tags automatically move both instances into the same datacenter.
  4. Enable VNet peering between the subscriptions; peering causes Azure to remap the physical zone behind the logical label.

Explanation

Correct Answer

A:

Azure assigns availability-zone numbers as logical labels within each subscription. Different subscriptions can map the same logical zone number to different physical zones, so use Azure’s published location/zone mapping information or the relevant APIs before making a physical co-location claim.

Incorrect Answers

B:

The numbering is not a region-wide guarantee across subscriptions. Microsoft documents that subscription A and subscription B may have different logical-to-physical mappings for the same region.

C:

Azure resource tags provide metadata for organization and governance. A user-defined tag cannot change a VM’s availability-zone placement or its subscription-specific physical zone mapping.

D:

Virtual network peering enables connectivity between VNets but does not change where VM compute is physically placed. Routing configuration cannot remap the subscription’s logical availability-zone labels.

Question 503

Two new VMs must tolerate planned host maintenance and an individual host failure in one Azure region, but cross-zone placement is not required. What should be configured at creation?

  1. Assign the same static public IP to both VMs with no load-balancing service.
  2. Place the new VMs in one availability set so Azure spreads them across fault and update domains.
  3. Deploy a storage account with GRS but leave both VMs on the same host.
  4. Enable an Azure resource-group ReadOnly lock on the VMs.

Explanation

Correct Answer

B:

Availability sets spread VM instances across fault and update domains within a datacenter and are selected when creating VMs.

Incorrect Answers

A:

Sharing a frontend IP without correct load-balancer architecture does not define maintenance/fault isolation.

C:

Geo-redundant object storage does not distribute the compute placement of Azure VMs.

D:

Resource locks do not control planned platform maintenance domains.

Question 504

An existing Azure VM was created without an availability set. The operator now wants it in a new availability set without changing the disk contents. What limitation applies?

  1. Existing VMs can join an availability set merely by editing the public IP resource.
  2. Availability-set membership is chosen at VM creation; plan a supported recreate/redeploy using preserved disks.
  3. Changing the VM’s tags automatically places it into the availability set.
  4. A Microsoft Entra directory group owner can change placement without touching VM resources.

Explanation

Correct Answer

B:

Azure requires availability-set membership at creation; recreating a VM around existing managed disks is a separate supported strategy.

Incorrect Answers

A:

Public IP settings do not alter availability-set membership of a VM.

C:

Tags do not control Azure fault/update domain placement.

D:

Directory group ownership is unrelated to VM availability placement settings.

Question 505

An internal order-processing service runs on a single VM in availability zone 1. Its load balancer probes and regional VNet are healthy, but a zone 1 outage would leave no running application instance. The region supports zone-spread VMs. Which change directly makes the application resilient to one zone failure?

  1. Move only the current VM from zone 1 to zone 2 and keep a single running instance.
  2. Add a storage-account read-access geo-replica while retaining the only application VM.
  3. Deploy at least one additional independent application VM in another zone and distribute traffic across healthy instances.
  4. Put a resource-level CanNotDelete management lock on the existing VM to prevent zone outages.

Explanation

Correct Answer

C:

At least two independent VM replicas in different availability zones give the service surviving compute capacity when zone 1 fails. Configure an appropriate load-balanced frontend and health probes so new client requests reach the surviving healthy replica, and ensure application state/dependencies tolerate failover. Merely placing one VM in a zone protects that VM only within the zone’s failure domain; distributing actual application instances is the operative resilience change. Confirm enough capacity remains for required throughput during the failed-zone condition.

Incorrect Answers

A:

Moving the only VM to a different zone changes which single zone can cause downtime; it does not create a redundant compute instance. When the new zone fails the application would still be unavailable. An application-level design needs healthy replica capacity outside the failed zone, coupled with traffic routing that avoids unhealthy instances.

B:

Geo-replicating a storage account can improve data durability but it does not replicate or start the application compute. If the only VM becomes unavailable, the service remains down even when blob data survives. The required failure domain is a zone hosting the app VM, so redundant application instances rather than storage-only copies are needed.

D:

An Azure management lock prevents certain control-plane updates or deletions; it does not change physical zone failure behavior. The VM can become unreachable during a zone outage regardless of a CanNotDelete lock. A lock is a governance protection, not a compute availability or traffic failover mechanism.

Question 506

A TCP service has backend VMs in multiple Azure availability zones. It needs a resilient public Layer-4 frontend with health-based traffic distribution. Which Azure service configuration is required?

  1. Use an Azure DNS zone alone without health probes or a traffic frontend.
  2. Use only an availability set, which spans datacenters in separate regions.
  3. Configure Standard Load Balancer with an appropriate zone-redundant frontend and healthy backend pool/probe rules.
  4. Configure Azure Container Registry geo-replication for the VM process.

Explanation

Correct Answer

C:

A zone-redundant Standard Load Balancer frontend with appropriate backend and health configuration distributes traffic across eligible zonal VMs.

Incorrect Answers

A:

Public DNS A records alone do not maintain health-based TCP load distribution among backend instances.

B:

Availability sets address in-region fault/update domains, not Layer-4 traffic balancing or global availability zones.

D:

Container image distribution does not provide an ingress load balancer for already running VMs.

Question 507

A managed disk currently has a zone placement incompatible with the Azure VM target zone. What is required before the disk can serve that VM?

  1. Create or migrate to a disk with compatible zonal/zone-redundant placement, then attach it to the VM.
  2. Change only the disk’s display name to the target zone.
  3. Assign the Reader role to the VM identity to override the disk’s zone.
  4. Enable a virtual network service endpoint for Microsoft.Storage.

Explanation

Correct Answer

A:

Disk placement must be compatible with the VM’s zone; a supported new disk/snapshot/copy or ZRS design can address the mismatch.

Incorrect Answers

B:

Resource naming cannot change underlying physical disk-zone placement.

C:

RBAC may govern management actions, but does not make an unavailable disk zone attachable.

D:

Service endpoints secure network access to supported PaaS endpoints; they do not move managed disk zones.

Question 508

Six Azure VMs are in one availability set configured with five update domains. Operations is planning for Azure platform maintenance that requires host restarts. Which statement correctly describes how the update domains are processed?

  1. Azure reboots all six VMs simultaneously because fault domains, not update domains, control planned maintenance.
  2. Azure automatically expands the availability set to six update domains, assigning every VM a unique domain.
  3. Azure always reboots update domains in strict numeric order and never places two VMs in one update domain.
  4. Azure restarts only one update domain at a time; a sixth VM can share the first domain, and maintenance order need not be sequential.

Explanation

Correct Answer

D:

Azure performs planned-maintenance restarts one update domain at a time for VMs in an availability set. With six VMs and five domains, the sixth may be placed with the first; update domains are not necessarily processed in numeric sequence.

Incorrect Answers

A:

The availability set's update domains explicitly govern how Azure rolls through planned maintenance. They are not replaced by fault domains, which primarily represent hardware failure boundaries.

B:

The availability set's configured update-domain count does not grow automatically as VMs are added. With five domains, the sixth VM can share an existing update domain.

C:

Azure does not guarantee numeric update-domain ordering, and multiple VMs can belong to one domain. The administration plan cannot assume a strict 1–5 reboot sequence or one VM per domain.

Question 509

All application VMs are in an Azure availability set in one region. The business must also recover from a complete outage of that region. What additional design is required?

  1. Increase update domains in the same availability set and assume that covers other Azure regions.
  2. Use one additional VM in the same availability zone with no cross-region state replication.
  3. Enable a VM tag called SecondaryRegion.
  4. Plan cross-region disaster recovery with replicated application state and tested failover.

Explanation

Correct Answer

D:

Regional disaster recovery requires a separate recovery region, appropriate replication and tested application failover.

Incorrect Answers

A:

Availability-set fault/update domains are regional and cannot handle a regional outage.

B:

Same-zone extra capacity remains exposed to the same region-wide outage.

C:

Tags do not implement geographic data replication or failover.

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.