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 46

Question 450

An infrastructure team must deploy the same four-VM application topology into dev, test and production subscriptions. VM names must incorporate the environment; all VMs need standardized `CostCenter` and `Owner` tags, with only subnet IDs and size differing by environment. Reviewers require a reproducible declared configuration. Which approach best meets the requirement?

  1. Individually create every VM in the portal and later apply tags through a one-time interactive script.
  2. Define VM resources, names and tags in a version-controlled Bicep module and supply validated environment-specific parameters for sizes and subnet IDs.
  3. Store a single VM image in Azure Compute Gallery and assume image replication also distributes tags, subnet assignments and deployment naming.
  4. Assign the Reader role to the deployment principal and specify all environments in one VM display name.

Explanation

Correct Answer

B:

Bicep defines resource type, name and tags declaratively while separate parameter inputs vary subnet and size by deployment environment. This creates reviewable, repeatable topology rather than relying on hand-built VMs.

Incorrect Answers

A:

Manual portal creation and post-hoc tagging produces mutable configuration with avoidable drift and does not deliver the requested declarative topology across subscriptions.

C:

Compute Gallery distributes image versions; it does not express each environment’s VM resource names, Azure resource tags, NIC attachments or infrastructure deployment parameters.

D:

Reader cannot create VMs, and one display name cannot model distinct per-environment resource instances or their required tags and network attachments.

Question 451

A VM creation pipeline supplies credentials through plaintext command arguments. Which Azure configuration or procedure is the best fit?

  1. Use secure secrets/SSH keys and protected automation environment variables.
  2. Attach its NIC to the approved subnet and omit direct public IP.
  3. Configure supported SSH public key authentication when provisioning.
  4. Deploy VM definitions through tested Bicep/ARM with per-environment parameters.

Explanation

Correct Answer

A:

Command-line plaintext credentials may be recorded in pipeline logs, shell history or process arguments. Use a secret store or other protected automation input and supported SSH-key authentication so the VM is created without exposing reusable passwords in command text.

Incorrect Answers

B:

A private-subnet NIC would reduce inbound exposure but would not prevent administrator passwords from appearing in plaintext CI command arguments. Credential-handling changes, such as protected secrets or SSH key approaches where supported, address the described leak.

C:

SSH public keys establish guest administrator access, not VM networking, gallery replication or other VM settings.

D:

Deploying VMs from tested ARM/Bicep templates enables repeatability but does not stop a pipeline from exposing passwords in its command line, logs or outputs. Move secret material to secure parameters or a protected secret store, avoid echoing credentials, and use supported SSH keys or managed identities when applicable.

Question 452

A staging VM has no inbound internet requirement but developers require remote management. What should the administrator do to resolve this specific case?

  1. Use an Azure Compute Gallery image definition/version that meets region and replication criteria.
  2. Configure supported SSH public key authentication when provisioning.
  3. Check regional subscription compute quota and request allowed increase or reduce size.
  4. Use Azure Bastion/VPN or privileged private path rather than open public RDP.

Explanation

Correct Answer

D:

Bastion, VPN or an authorized private management connection reaches the VM without adding a public RDP or SSH listener to the internet. Network and RBAC controls can still limit who may administer the staging VM.

Incorrect Answers

A:

Compute Gallery provides supported and replicated images. The staging VM already exists; sharing an OS image does not create the private Bastion/VPN management path required when no public inbound access is allowed.

B:

SSH public key configuration establishes a login credential for eligible Linux guests. It does not itself provide a permitted network route to a VM that intentionally has no public inbound endpoint.

C:

A regional compute vCPU quota can prevent VM provisioning, but the scenario states only a requirement for private remote administration of a staging VM. Increasing quota neither removes exposed management ports nor provides a private access path. Use Bastion, VPN or another approved private management route instead of internet-facing RDP.

Question 453

A regulated team approves Azure Compute Gallery image version `2026.10.0` of definition `win-secure-2022`. The version is replicated to East US but a production VM must be built in West Europe and use this exact vetted image. The standard network and credentials are already configured. What should the administrator check and select before provisioning?

  1. Change the VM security type to Trusted Launch and allow any public Marketplace image; that guarantees the organization’s approved version.
  2. Connect the VM through Bastion and select any version from the gallery without regard to target-region replication.
  3. Assign an existing NIC in West Europe and choose a default Marketplace image, because subnet choice implies the curated OS version.
  4. Ensure image version `2026.10.0` is replicated/available in West Europe, then reference that exact gallery image version as the VM image.

Explanation

Correct Answer

D:

Azure Compute Gallery maintains named image definitions and versioned replicas. The target region must have the approved version available, and the VM image reference must identify it explicitly.

Incorrect Answers

A:

Trusted Launch does not establish an immutable approved gallery version; a generic Marketplace image would bypass the explicit version-control requirement.

B:

Bastion is a management access path. It neither replicates images nor confirms that the requested gallery version is available to deploy in West Europe.

C:

NIC selection determines where a VM connects, not which approved OS image version it uses. A default Marketplace image would fail the curated-version requirement.

Question 454

A newly provisioned supported Azure VM will store temporary-disk data and OS/data-disk cache content on the virtualization host. A security control requires encryption of these host-resident contents before the VM begins carrying production data. Which configuration supplies the coverage?

  1. Enable encryption only on an unrelated Azure Storage diagnostics account and assume that encrypts the VM host caches.
  2. Enable Blob soft delete on the diagnostics account to prevent plaintext VM cache storage.
  3. Enable encryption at host on the supported VM configuration and confirm the required subscription and VM-size prerequisites.
  4. Use an Azure management CanNotDelete lock on the VM to encrypt its temporary disk.

Explanation

Correct Answer

C:

Encryption at host starts on the VM host and protects temporary disks and OS/data disk caches at rest. It is distinct from ordinary managed disk server-side encryption.

Incorrect Answers

A:

A diagnostics account encrypts its own stored data; it does not implement host-side encryption for the VM temporary disk or disk cache.

B:

Soft delete is an object-recovery control, not cryptographic protection of VM host temporary data.

D:

A management lock controls Azure Resource Manager delete operations. It does not encrypt transient host data or disk caches.

Question 455

An organization requires host-side encryption for temporary disks and disk caches on its Azure VMs. An existing VM uses a legacy size that Microsoft does not list as supporting encryption at host; the portal hides the setting. The team has approval to resize or redeploy the VM but must not substitute a different encryption control. What is the correct design decision?

  1. Leave the unsupported VM size in place and force the encryptionAtHost flag through an ARM deployment.
  2. Enable guest Azure Disk Encryption and describe it as equivalent to encryption at host.
  3. Assume standard managed disk server-side encryption automatically encrypts every VM's host-side cache and temporary disk.
  4. Choose a VM size and deployment configuration that support encryption at host, then enable the feature after checking prerequisites.

Explanation

Correct Answer

D:

Encryption at host has VM-family and configuration prerequisites; Microsoft explicitly excludes legacy unsupported VM sizes. Since the owner permits a resize or redeployment, first select a supported size and check the applicable disk and subscription configuration. Enable encryption at host only after those prerequisites are met and verify the VM's resulting setting. That produces the required protection for host-side caches and eligible temporary/ephemeral disks rather than merely relying on managed-disk server-side encryption or guest Azure Disk Encryption.

Incorrect Answers

A:

A hidden or unsupported feature cannot be made supported by forcing a property through ARM. Encryption-at-host availability depends on Azure VM size and other eligibility constraints, and an unsupported configuration might reject the deployment or fail policy validation. The requirement is to achieve real host-side encryption, so the operator must select an eligible configuration before enabling the feature, not bypass the portal's compatibility signal.

B:

Azure Disk Encryption runs through guest-oriented encryption technology and is distinct from Azure's encryption at host feature. Microsoft documents limitations on combining them, including a restriction on VMs that currently or previously used Azure Disk Encryption. Swapping in ADE would therefore neither provide the same host-encryption guarantee nor meet the stated requirement that a different control not be substituted.

C:

Default server-side encryption protects managed-disk storage at rest, but it does not by itself establish that transient host caches and temporary disks are encrypted with the encryption-at-host feature. Azure documents encryption at host separately, including eligible VM sizes and host-specific behavior. Treating regular managed-disk protection as a substitute would produce a false compliance assertion for this VM.

Question 456

A Windows VM previously used Azure Disk Encryption (ADE) for its OS volume, but ADE is now disabled. Compliance wants Azure encryption at host on this exact existing VM and proposes simply enabling the encryptionAtHost setting. Which Microsoft-documented restriction must the administrator explain before approving the change?

  1. Encryption at host can be enabled immediately because ADE is no longer currently active on the VM.
  2. The VM must first enable both ADE and encryption at host so the host cache is protected twice.
  3. Only storage account firewall rules determine whether Azure VM encryption at host is supported.
  4. Encryption at host is not supported on a VM that currently has or has ever had ADE enabled, so this VM cannot use that conversion path.

Explanation

Correct Answer

D:

Microsoft documents an explicit incompatibility: encryption at host cannot be enabled on a virtual machine or scale set that currently uses, or has ever used, Azure Disk Encryption. Disabling ADE today does not erase the VM's previous ADE history. Consequently, simply setting encryptionAtHost on this same VM would not be an approved conversion. The engineering team must plan a supported new VM or alternative architecture and assess disk migration requirements without misrepresenting the old VM as eligible. Host encryption and guest ADE are distinct controls with different supported paths.

Incorrect Answers

A:

Microsoft's restriction is historical, not just a check of the present ADE setting. Even if the guest encryption extension is removed or ADE is disabled, the existing VM's previous ADE use makes encryption at host unsupported for that VM. An operator must not infer the VM has become eligible by observing that the guest feature is currently switched off; the exact VM history matters.

B:

ADE and encryption at host are not stacked as complementary controls on the same VM. Microsoft states encryption at host cannot be enabled on a VM that currently or previously used ADE, and ADE cannot be enabled on disks with host encryption. Enabling both would contradict the documented incompatibility instead of satisfying the compliance requirement.

C:

Storage account firewall policy governs network access to storage services, not the compatibility between Azure Disk Encryption and the VM's host-side encryption feature. No adjustment to selected networks, public endpoint settings or private connectivity removes the documented ADE history restriction on the VM. This choice addresses a different Azure Storage administration problem entirely.

Question 457

A group of supported Azure VMs uses a disk encryption set with customer-managed keys for managed OS and data disks. The VMs have never used guest Azure Disk Encryption. Security now requires encryption of their host-side caches and temporary disks while retaining customer-managed keys for the managed disks. Which change meets both requirements?

  1. Enable Azure encryption at host on the supported VMs while keeping the existing disk encryption set and customer-managed keys; verify VM prerequisites.
  2. Enable Azure Disk Encryption inside the guests and encryption at host simultaneously on the same machines.
  3. Replace customer-managed disk keys with platform-managed keys because encryption at host never supports customer-managed keys.
  4. Change the encryption setting on an unrelated Azure Storage diagnostics account and leave the VM host setting disabled.

Explanation

Correct Answer

A:

Encryption at host encrypts VM host-side storage such as eligible temporary disks and the caches for OS and data disks. Microsoft documents that caches use customer-managed keys when the corresponding disk uses customer-managed encryption, so existing disk encryption sets can remain. Check supported VM size and subscription prerequisites, verify there is no ADE history, then enable the host setting on the eligible VMs. This addresses the uncovered host-side surfaces without replacing the organization's disk key-management decision or confusing it with guest encryption.

Incorrect Answers

B:

Azure Disk Encryption is a guest encryption mechanism that is incompatible with encryption at host on the same VM according to Microsoft restrictions. These VMs have no ADE history, so enabling ADE now would remove the option to use the requested host encryption. It would also introduce unnecessary guest key-management complexity rather than extending protection to caches and temporary disks using the host feature.

C:

Customer-managed keys for managed disks do not inherently prevent encryption at host. Microsoft explains that a disk's host cache can use the customer's managed key when the underlying disk uses that key. Replacing the disk encryption set with platform-managed encryption would violate the requirement to retain CMKs and would not be necessary to satisfy the newly requested host-side protection.

D:

A storage account used for diagnostics is a different Azure resource from the VM host and its managed disk caches. Changing that account's encryption configuration would affect diagnostic objects, not enable the encryptionAtHost property on the VM. The operator must configure the supported host feature on the VM itself while retaining the existing customer-managed disk-key configuration.

Question 458

An already deployed Windows Azure VM is running in production. Its VM size supports encryption at host, it has never used ADE, and the required subscription prerequisites are complete. Operations have an approved maintenance window to enable encryption at host on this existing VM. Which implementation sequence should the runbook specify?

  1. Change only the managed disk server-side encryption setting while keeping encryptionAtHost disabled.
  2. Set encryptionAtHost while the VM stays continuously allocated, then assume existing host data was re-encrypted without a restart.
  3. Enable guest Azure Disk Encryption just before enabling encryption at host, to satisfy the host prerequisite.
  4. Deallocate the existing VM, update its supported encryption-at-host setting, and start/reallocate it, verifying the resulting protection.

Explanation

Correct Answer

D:

For an eligible existing VM, plan a maintenance window, deallocate the VM, enable the encryption-at-host configuration, and then reallocate or restart it. Microsoft's portal guidance says that existing VMs must be deallocated and reallocated for encryption to take effect. Check that disk type, VM size and ADE history are supported before the change, and confirm the resulting VM setting afterward. The deliberate interruption is operationally significant, so the runbook must not present enabling the property on an already running VM as a zero-downtime change.

Incorrect Answers

A:

Managed-disk server-side encryption does not replace the encryption-at-host setting for host-side caches and temporary disks. The stated maintenance request concerns the VM host encryption layer, not merely data stored in the Azure managed-disk service. Leaving encryptionAtHost disabled would fail the compliance requirement regardless of how the managed disks are encrypted at rest.

B:

Changing an existing VM's encryption behavior needs the supported stop/deallocation and reallocation process; a running status alone does not prove the new host storage protection has taken effect. Microsoft specifically notes that existing VMs must be deallocated and reallocated to be encrypted with encryption at host. Skipping that lifecycle requirement makes the rollout unverifiable or unsupported for the stated existing machine.

C:

Enabling ADE would contradict the prerequisite that the machine remain eligible for encryption at host. Microsoft disallows host encryption on VMs that have ever used Azure Disk Encryption and also disallows ADE on disks protected by host encryption. Guest ADE is not a preparatory step for this feature; introducing it would make the desired operation invalid.

Question 459

A company will deploy NEW Azure VMs into a protected subscription. Every eligible VM must have encryption at host enabled from initial provisioning; noncompliant deployments must be prevented before their workload begins. What is the right administrative design?

  1. Declare encryption-at-host on supported VM deployments and enforce the requirement through appropriate Azure Policy deny controls during provisioning.
  2. Create every VM with host encryption off, then manually enable it after the VM has begun processing production data.
  3. Enable Blob soft delete on the subscription’s diagnostics storage accounts and assume the VM host cache is encrypted.
  4. Set a CanNotDelete lock on each VM instead of configuring host encryption.

Explanation

Correct Answer

A:

The target is an enforced at-create control. Configure the supported VM property in deployment definitions and use a suitable deny policy so unsupported or noncompliant requests do not proceed unnoticed.

Incorrect Answers

B:

Enabling host encryption only after workload startup violates the never-start-unprotected requirement and can require VM deallocation/reallocation.

C:

Blob soft delete provides recovery for eligible blob deletions, not encryption of a VM’s temporary disks or caches.

D:

Management locks block ARM deletion and can prevent some updates, but they do not encrypt VM host-resident contents.

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.