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 47

Question 460

A supported Azure Virtual Machine Scale Set with five existing instances enables encryption at host in its configuration today. It will also create new scale-set instances next week. What must operators do to ensure that both the old and new VM instances obtain host encryption?

  1. Nothing after changing the scale-set model: the encryption automatically becomes active on all existing running instances with no reallocation.
  2. Delete and redeploy the complete scale set because encryption at host is impossible to enable on an existing VMSS.
  3. Enable guest Azure Disk Encryption on all old instances and encryption at host only on the newly created ones.
  4. Allow new scale-set VMs to use the updated host-encryption setting and deallocate/reallocate the existing eligible instances so that host encryption takes effect there too.

Explanation

Correct Answer

D:

The scale-set configuration applies host encryption to newly created VMs automatically, but existing instances must be deallocated and reallocated for the encryption to apply. Validate supported VM sizes and coordinate instance servicing to maintain capacity.

Incorrect Answers

A:

Enabling the setting in an existing scale set does not retroactively encrypt the temporary disks and caches of already running instances. An instance-level deallocation and reallocation step is needed for previously deployed VMs.

B:

Microsoft supports enabling encryption at host on an existing scale set. A full scale-set deletion is unnecessary and would risk disrupting running workloads and their dependent resources.

C:

Azure Disk Encryption is not a compatible bridge for this feature: VMs that currently or previously used ADE cannot enable encryption at host. Mixing guest ADE with encryption-at-host settings would create a prohibited deployment path.

Question 461

A VM size and region support encryption at host, and the VM has never used Azure Disk Encryption. However, an attached Ultra Disk has a 512e sector size and was created on April 15, 2023. The encryption-at-host rollout fails the documented disk-compatibility prerequisite. What corrective action should be planned?

  1. Ignore the Ultra Disk age because sector size and creation date never affect encryption-at-host eligibility.
  2. Change the disk cache setting to ReadWrite to bypass the encryption-at-host disk prerequisite.
  3. Enable guest Azure Disk Encryption on the old Ultra Disk first and then turn on encryption at host on the VM.
  4. Snapshot the pre-May-13-2023 512e disk and create a supported replacement disk from that snapshot before enabling encryption at host and validating the VM.

Explanation

Correct Answer

D:

Microsoft requires a 512e Ultra Disk or Premium SSD v2 disk created before May 13, 2023 to be snapshotted and recreated as a new disk before encryption at host is enabled. After the replacement, confirm the remaining VM and disk prerequisites and schedule the approved rollout.

Incorrect Answers

A:

Microsoft documents a creation-date restriction for 512e-sector Ultra Disks and Premium SSD v2 disks. The disk was created before the stated cutoff, so ignoring its age leaves the compatibility failure unresolved.

B:

Disk caching settings are not an encryption-at-host eligibility bypass. The issue is the disk’s 512e format and pre-cutoff creation date, not whether the guest wants read or write caching.

C:

Azure Disk Encryption and encryption at host are mutually incompatible for a VM that has ever used ADE. Enabling ADE would add a separate blocker rather than fix the older disk.

Question 462

An auditor requests evidence that an existing Azure VM has encryption at host enabled, rather than only default managed-disk encryption. Which check is decisive?

  1. Look only for a disk encryption set assigned to one managed disk.
  2. Inspect the VM security/encryption-at-host configuration property and confirm its enabled state.
  3. Confirm that the Azure storage service encrypts managed disks by default.
  4. Verify that the guest OS has BitLocker installed, regardless of actual VM settings.

Explanation

Correct Answer

B:

The VM-level encryption-at-host setting establishes whether this protection is enabled, subject to supported configuration.

Incorrect Answers

A:

A disk encryption set selects keys for managed-disk encryption; it does not alone prove the VM host setting protects temporary data and caches.

C:

Default managed-disk encryption protects persistent disk data at rest and does not by itself establish host-cache or temporary-disk encryption.

D:

BitLocker inside a guest indicates a different encryption mechanism and does not prove the Azure encryptionAtHost setting is enabled.

Question 463

A team uses an ephemeral OS disk and wants to assert encryption-at-host protection for its supported Azure VM. What must be established first?

  1. Confirm support for encryption at host on the chosen VM family and region, then enable it and validate the state.
  2. Assign a disk encryption set to the ephemeral OS disk and assume this alone enables host encryption.
  3. Rely on managed-disk server-side encryption to protect all ephemeral data on the VM host.
  4. Turn on Azure Disk Encryption inside the guest at the same time as encryption at host.

Explanation

Correct Answer

A:

Encryption at host is subject to VM support and configuration; eligible ephemeral OS data is encrypted with platform-managed keys at the host when enabled.

Incorrect Answers

B:

An ephemeral OS disk resides on VM-local storage rather than a separately managed OS disk to which a disk encryption set is attached.

C:

Default server-side encryption applies to managed disks and does not establish encryption of VM temporary/ephemeral storage in this scenario.

D:

Azure Disk Encryption and encryption at host are incompatible for VMs that currently or previously used ADE; enabling both is not the prerequisite.

Question 464

An Azure VM has encryption at host enabled. Its managed OS and data disks use a disk encryption set backed by customer-managed keys. An auditor asks whether the temporary disk and the managed-disk caches use the same type of encryption key on the VM host. Which answer is technically accurate?

  1. All host-resident temporary data and all disk caches must use the customer-managed key because the managed OS disk uses one.
  2. Temporary disks remain unencrypted because Azure Storage server-side encryption already protects all host-local temporary storage.
  3. Guest Azure Disk Encryption must be enabled for temporary disks before encryption at host can encrypt managed disk caches.
  4. Encryption at host uses platform-managed keys for temporary and ephemeral OS disks, while managed OS/data disk caches follow the platform-managed or customer-managed key type of the corresponding disks.

Explanation

Correct Answer

D:

Microsoft states that encryption at host encrypts temporary disks and ephemeral OS disks with platform-managed keys. OS and data disk caches use the key model selected for their associated managed disks, including customer-managed keys where configured.

Incorrect Answers

A:

Customer-managed keys associated with managed disks govern the encryption of their corresponding OS/data disk caches, but they do not make host temporary disks customer-key encrypted. The temporary disk key model differs.

B:

Server-side encryption of Azure managed disks by itself does not cover data on the host temporary disk or disk caches. Enabling encryption at host encrypts those host-local surfaces, with documented key-type differences.

C:

Azure Disk Encryption operates in the guest and cannot be combined with encryption at host on VMs that currently or previously used ADE. It is not a prerequisite for cache encryption.

Question 465

Before enabling encryption at host on an existing production VM fleet, an administrator must reduce disruption risk and confirm that any required deallocation and reallocation will be recoverable. Which change-control action should precede rollout?

  1. Enable encryption at host on every VM at once without checking VM-size or prior disk-encryption restrictions.
  2. Verify VM and disk compatibility, test the exact procedure in nonproduction, capture an authorized recovery plan, and schedule any required deallocate/reallocate steps.
  3. Assume managed disk Storage Service Encryption automatically protects host temp data and cached I/O, so no configuration change is needed.
  4. Disable Azure VM backup and delete all restore points before enabling encryption at host.

Explanation

Correct Answer

B:

Microsoft documents eligibility restrictions and deallocation/reallocation requirements for existing instances; staging the process and preserving a tested recovery path reduces rollout risk.

Incorrect Answers

A:

The feature has support restrictions, and blind production changes can fail or interrupt VMs without an approved rollback procedure.

C:

Disk service encryption and encryption at host cover different data paths, so default SSE cannot by itself satisfy host temporary/cached data requirements.

D:

Removing recovery points reduces recoverability and is not a prerequisite for enabling the supported encryption-at-host feature.

Question 466

A supported Azure VM and its managed disks must be relocated to another resource group in the SAME subscription and region. Which operation should the administrator use?

  1. Use Azure Resource Mover to replicate the VM into another Azure region.
  2. Edit the VM resource ID manually in the deployed ARM JSON without an Azure move operation.
  3. Move only the VM resource, leaving disks and dependent network resources unexamined.
  4. Use the Azure resource move workflow after validating supported dependencies and destination scope.

Explanation

Correct Answer

D:

A supported resource-group move changes management scope while preserving resource location; validate and include required dependencies.

Incorrect Answers

A:

Resource Mover addresses inter-region relocation; the case requires a resource-group change within the existing region.

B:

Azure resource IDs are assigned by Resource Manager; changing a text reference does not move a live resource.

C:

Azure VM moves have dependent disks and networking that can block or break unsupported isolated moves.

Question 467

An Azure VM is being moved from subscription A to subscription B in the SAME Microsoft Entra tenant. Both have suitable regions. What must be checked before the resource move?

  1. Add a subscription Owner role to the VM guest account and ignore dependent disks.
  2. Treat the move as a cross-region replication even though no region change is requested.
  3. Validate resource/provider eligibility, destination registration and co-located dependent resources before moving.
  4. Change the target subscription to a different Entra tenant to simplify the move.

Explanation

Correct Answer

C:

Cross-subscription moves need same-tenant scope plus validated resource providers and dependencies, which may need consolidation first.

Incorrect Answers

A:

Guest operating-system privileges do not replace Azure resource move prerequisites or dependency checks.

B:

The standard cross-subscription move changes scope, not physical region; separate regional replication is not inherently required.

D:

An ordinary resource move across subscriptions cannot directly cross Entra tenants; this would introduce a new incompatibility.

Question 468

An Azure VM currently runs in West Europe; the application must run in North Europe to reduce latency. Which strategy actually changes its physical region?

  1. Move only the VM to another resource group in West Europe.
  2. Change the VM tag named Location to North Europe.
  3. Change the VM size to a North Europe-supported family without migrating the resource.
  4. Use supported Azure Resource Mover or a tested cross-region migration/redeployment plan including dependencies.

Explanation

Correct Answer

D:

Azure Resource Mover supports moving eligible VMs and associated dependencies between regions through a controlled process.

Incorrect Answers

A:

An Azure resource-group move changes resource ID/scope but not resource location.

B:

Tags contain metadata; changing a Location tag never moves Azure compute to a different datacenter.

C:

Selecting a VM SKU does not relocate an existing regional resource.

Question 469

Azure VMs `web-a` and `web-b` belong to the SAME availability set `as-web` in resource group `rg-old`. A team wants to move ONLY `web-a` and its OS disk to `rg-new` while leaving the other VM and the shared availability set in `rg-old`; all resources are in one subscription and region. Validation rejects the proposed subset. Which supported move rule accounts for this result?

  1. Stop only `web-a`, then move its VM resource separately; stopping converts its availability-set association into a movable standalone VM.
  2. Change the display name of `as-web` after copying `web-a` to `rg-new`; a rename removes the availability-set dependency automatically.
  3. A VM that belongs to an availability set cannot be moved individually. Plan a supported coordinated move of the entire availability set and its VMs and dependent resources, or redesign the deployment if that group cannot move together.
  4. Use Azure Resource Mover cross-region replication to transfer just `web-a` while keeping the same resource region; cross-region replication bypasses availability-set move constraints.

Explanation

Correct Answer

C:

Microsoft's documented VM move limitations prohibit moving an individual VM from an availability set independently of the set. The move design must account for the set and other associated VMs and required network/disk dependencies in a supported scope operation; this is different from moving a standalone VM.

Incorrect Answers

A:

Deallocation or shutdown does not detach a VM from its availability set, and a same-subscription resource-group move has rules about dependent resources that stopping a single VM does not waive. A single-member move remains unsupported for VMs in the same availability set.

B:

Renaming or copying an availability-set label does not modify a VM's Azure resource identity or detach it from an existing availability-set placement. This option supplies no supported coordinated resource-group move.

D:

Azure Resource Mover is designed for supported region moves rather than an exception to single-VM availability-set constraints during a resource-group-only move. It cannot justify moving one member of a shared set while leaving the rest unchanged.

Question 470

A zone-specific application VM must be migrated to a DIFFERENT Azure region with its own availability zones. How should placement be planned?

  1. Perform a resource-group move and expect the existing zone number to become a destination-region placement.
  2. Keep the existing regional VM but update its DNS alias to claim it runs in the target region.
  3. Migrate or redeploy with compatible destination-region zones, disk placement and recovery testing.
  4. Change only the source VM availability-set name.

Explanation

Correct Answer

C:

Availability zones are regional; migration must select supported target zone and dependent disk configuration, then validate cutover.

Incorrect Answers

A:

Resource-group changes do not relocate a VM across regions or make its zone assignment portable.

B:

DNS affects name resolution, not the location of the VM or its managed disks.

D:

Availability sets are separate placement constructs and renaming one does not move a zonal VM to another region.