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 85

Question 840

The finance team has a single production Windows VM in eastus, no Recovery Services vault, no Azure Backup policy, and no other backup configuration. Policy requires daily Azure VM recovery points retained for 30 days. Which TWO actions establish protection for this VM? Select TWO answers.

  1. Enable Storage Blob soft delete on an unrelated general-purpose storage account and assume VM disk recovery points appear.
  2. Move the VM to westus before creating an eastus Recovery Services vault, although the workload must remain in eastus.
  3. Select or create a supported daily Azure VM backup policy in the vault and enable backup protection for the VM under that policy.
  4. Create a Recovery Services vault in the VM’s supported region with appropriate access and redundancy configuration.
  5. Assign the VM the Azure subscription Owner role; management rights alone automatically schedule recovery points.

Explanation

Correct Answers

C:

Azure VM backup uses policies to establish when recovery points are created and how long they are retained. In the eligible Recovery Services vault, select or create a supported policy meeting the daily schedule and 30-day retention, then enable protection for the VM. This turns the policy into an operating backup configuration rather than merely a document or an alert. Confirm the initial backup job completes and that the resulting recovery points meet the contractual cadence.

D:

A Recovery Services vault is the Azure Backup resource that stores and governs VM recovery points. Create it in the supported region for the eastus VM and choose the required access and redundancy defaults for the backup data. The vault is the prerequisite target for the policy and VM protection operation. Vault creation alone does not start backups; the complementary selection and enablement of the VM policy are separately necessary.

Incorrect Answers

A:

Blob soft delete protects eligible deleted blob objects and does not schedule Azure VM snapshots or vault recovery points for this instance. No current VM backup configuration exists. The administrator needs a Recovery Services vault and a VM backup policy with protection enabled, not a generic blob feature on an unrelated account.

B:

Azure VM backup normally uses a Recovery Services vault in the same region as the protected VM, and the business has not approved a VM relocation. Moving a production VM to another region creates needless operational change without configuring backup protection. Create an eligible vault in the VM’s current region and enable protection there instead.

E:

Azure subscription Owner is a broad control-plane permission, not a scheduled backup policy. Giving the VM or an administrator this role would not create recovery points by itself and is excessive for the stated task. Backup must be configured through an eligible Recovery Services vault, the VM workload and an actual backup policy.

Question 841

A production VM resides in West Europe. A new Recovery Services vault was created in East US, and the portal cannot enroll the VM in that vault for standard Azure VM backup. What is the required arrangement?

  1. Select a Backup vault in East US and assume all VM Backup workload locations are supported there.
  2. Create or select a Recovery Services vault in West Europe and configure protection for the West Europe VM under a supported backup policy.
  3. Add a soft-delete setting to the East US vault to bypass the workload region requirement.
  4. Increase the VM vCPU quota in East US so a West Europe VM can be backed up by that vault.

Explanation

Correct Answer

B:

For standard Azure VM backup, the protecting Recovery Services vault and VM must be in the same Azure region; the VM must use a supported policy in West Europe.

Incorrect Answers

A:

Backup vault workload support and location cannot be assumed interchangeable with standard Azure VM backup in a Recovery Services vault.

C:

Soft delete protects deleted backup instances, not the eligibility of cross-region vault-to-VM enrollment.

D:

VM compute-core quota does not change the Azure Backup vault’s same-region requirement for protecting a VM.

Question 842

A Recovery Services vault is used for Azure VM backups. Security specifically wants recovery of backup data after an authorized operator accidentally deletes a backup instance. Which control directly supplies a recovery window?

  1. A resource-group Reader assignment, which makes every deletion permanently reversible.
  2. Turning off all audit logs so the deleted backup instance cannot be detected.
  3. Enable and retain the vault’s supported Azure Backup soft-delete protection for deleted backup data, and validate the applicable retention/security configuration.
  4. Change the target VM availability zone, which rehydrates deleted backup recovery points.

Explanation

Correct Answer

C:

Azure Backup soft delete preserves eligible deleted backup data for its configured period; recovery and security requirements must use supported vault settings.

Incorrect Answers

A:

Reader is read-only but does not provide recoverability once an authorized deletion is performed through another identity.

B:

Removing audit trails harms incident response and does not preserve deleted backup data for recovery.

D:

A VM availability-zone setting concerns compute failure domains and cannot reconstruct deleted backup instances or restore points.

Question 843

A new Recovery Services vault in West Europe will store recovery points for supported Azure VMs. It has no protected items yet. Compliance prohibits replicating backup data to another Azure region, but a complete availability-zone outage must not make the backed-up data unavailable. The planned workload and region support ZRS. Which vault storage-redundancy setting meets BOTH requirements before backup is enabled?

  1. Use locally redundant storage (LRS) because its three replicas are guaranteed to be distributed across independent availability zones.
  2. Retain default geo-redundant storage (GRS) and enable Cross Region Restore, because it keeps every backup copy inside West Europe.
  3. Select zone-redundant storage (ZRS) for the Recovery Services vault before protecting the VMs.
  4. Keep geo-redundant storage but apply a CanNotDelete management lock; the lock converts offsite backup replication into same-region zone redundancy.

Explanation

Correct Answer

C:

ZRS spreads supported vault backup-data copies across availability zones of the SAME Azure region. In West Europe it supplies a documented option to withstand a zone failure without geo-replicating the data to a paired region. Select ZRS in the Recovery Services vault while the redundancy setting is still editable, before enrolling the first protected item. The question concerns redundancy of backup data, not just availability of the backup service.

Incorrect Answers

A:

LRS keeps copies in the primary Azure region, but it does not guarantee that those copies span independent availability zones. The requirement is explicitly to remain recoverable during an availability-zone outage. LRS therefore cannot supply the required zonal backup-data resilience, even if other service components are zone resilient.

B:

GRS replicates backup data to a paired secondary Azure region; Cross Region Restore can expose recovery points there. That helps regional disaster recovery, but directly conflicts with the regulator’s ban on copies leaving West Europe. It does not implement an all-copies-in-one-region solution.

D:

An Azure management lock restricts certain management-plane delete operations. It does not transform GRS replication geography, alter the vault’s storage-redundancy SKU, or stop the secondary-region copy created by GRS. The only listed option satisfying both placement and zone-survival constraints is ZRS.

Question 844

Security requires a Recovery Services vault protecting critical VMs to resist an attacker who gains one backup administrator account and tries to disable soft delete or delete protection. What is the layered Azure Backup defense?

  1. Grant the attacker subscription Owner so the vault treats the deletion as a known administrator action.
  2. Rely on Azure VM NIC NSG rules to prevent all vault management operations.
  3. Turn off the vault audit logs so unauthorized deletions do not appear in monitoring.
  4. Configure eligible multi-user authorization with Resource Guard, supported soft delete, least-privilege RBAC and vault security settings for protected critical operations.

Explanation

Correct Answer

D:

Multi-user authorization with Resource Guard and soft-delete controls provide separate security and recovery layers for destructive backup operations.

Incorrect Answers

A:

Broad subscription Owner increases destructive privilege and is contrary to separating duties for high-risk backup operations.

B:

VM network-security groups filter VM traffic and do not by themselves authorize or block Azure Backup vault management operations.

C:

Disabling audit logs removes evidence and has no protective effect against deleting protected backup items.

Question 845

An Azure Backup administrator must create and edit daily backup policies and manage scheduled or on-demand protection for VMs in ONE existing Recovery Services vault. The administrator must not grant other users access, delete the vault or receive subscription-wide Owner rights. Which built-in Azure role should be assigned at the vault scope to authorize backup POLICY management with least privilege?

  1. Backup Operator on the vault, because it can create or modify Azure VM backup policies as well as perform on-demand backup and restore.
  2. Backup Contributor on the specific Recovery Services vault; it can manage backup policies and protection operations without granting role assignments or permission to delete the vault.
  3. Backup Reader on the vault, because viewing backup job status also grants policy write and protection-management operations.
  4. Owner on the entire subscription, because a subscription-wide role is a prerequisite for editing the policy of an already-existing Recovery Services vault.

Explanation

Correct Answer

B:

Backup Contributor is the Azure Backup built-in role with permissions to create, modify and delete backup policies as well as manage protection operations, excluding Recovery Services vault deletion and access delegation. Grant it at the particular vault instead of the entire subscription; confirm applicable resource-specific prerequisites when protecting or restoring VMs. The policy-management requirement distinguishes it from Backup Operator.

Incorrect Answers

A:

Microsoft documents that Backup Operator can enable supported protection, start on-demand backups and perform restore operations, but it EXCLUDES backup policy management. The case expressly requires creating and editing VM backup policies in addition to running backup jobs. Backup Operator alone does not include that write capability, so use a vault-scoped Backup Contributor for policy administration.

C:

Backup Reader is intended for monitoring protection state, jobs and backup-related configuration without modifying backup policies or triggering management operations. Having visibility into the current schedule does not authorize a new policy or a change in retention. The administrator needs the defined backup management permissions of Backup Contributor, not a read-only monitoring role.

D:

Subscription Owner would be powerful enough to edit backup policies, but it can also manage unrelated subscription resources and role assignments, contradicting the requirement to avoid broad administration. The Recovery Services vault already exists, and Microsoft documents Backup Contributor scoped to the vault for backup policy management. Subscription-wide Owner is not a prerequisite and violates least privilege.

Question 846

An Azure administrator is retiring Recovery Services vault `rv-legacy` in a public Azure region where secure-by-default soft delete for Recovery Services vaults is generally available. All VM backups have been stopped and their backup items moved to the soft-deleted state; there are no active protected items, Site Recovery replicated items, registered backup servers, storage accounts or private endpoints. Security requires the deleted vault and its retained data to remain recoverable for the configured soft-delete period rather than to be purged immediately. Which supported action meets this requirement?

  1. Disable the vault's mandatory soft-delete feature, delete all recovery points permanently, and then delete the vault without any recovery period.
  2. Keep one protected VM actively backing up and delete the vault directly; the running backup item automatically turns into a soft-deleted vault with no cleanup.
  3. Initiate vault deletion in the Azure portal after the listed active dependencies are cleared; the vault enters a soft-deleted state, preserving the documented recovery window.
  4. Wait for all currently soft-deleted backup items to expire before attempting vault deletion, because a vault with only soft-deleted items can never itself be soft-deleted.

Explanation

Correct Answer

C:

Microsoft documents that, with secure-by-default vault soft delete generally available, the Azure portal can soft-delete a Recovery Services vault that is empty or contains only soft-deleted backup items. The vault can be recovered during its configured retention window; the operator has already cleared the other documented dependencies.

Incorrect Answers

A:

Microsoft's current secure-by-default retention protects deleted backup data and vaults. In the stated generally available region, disabling soft delete is not an allowed prerequisite, and immediate permanent purge would violate the recoverability requirement.

B:

An actively protected item is still a dependency that must be removed before deleting a Recovery Services vault. Secure-by-default vault deletion is supported when there are no active protected items and only allowed soft-deleted backup items remain, not by retaining active backup jobs.

D:

This rule reflects older permanent-deletion guidance rather than the current secure-by-default vault soft-delete behavior. In the specified generally available region, an Azure portal delete is allowed when a Recovery Services vault holds only soft-deleted items; the vault itself moves to the soft-deleted state, so waiting for those items to expire is not necessary for the requested retirement.

Question 847

A Recovery Services vault protects six Azure VMs. Five nightly backups succeed, but one VM's backup job fails with an error that the team has not yet investigated. Before altering shared vault settings or protected items, what is the most appropriate first troubleshooting step to identify the affected VM and cause?

  1. Select vault type based on supported datasource and backup model.
  2. Inspect vault backup jobs/protection status to identify the specific failing item.
  3. Create a Recovery Services vault in an eligible region and enable VM backup.
  4. Stop protection and delete backup items only through supported authorized retention workflow.

Explanation

Correct Answer

B:

Open the Recovery Services vault's Backup jobs view, filter the failed job and inspect the affected VM's failure code, error details and protection status. Microsoft documents specific VM backup failures requiring different fixes, so selecting remediation before identifying that error can disrupt healthy workloads. This step establishes the root-cause investigation; it does not itself guarantee the job will succeed on retry.

Incorrect Answers

A:

Choosing between Backup and Recovery Services vaults is an initial workload design decision. The six VMs already have a Recovery Services vault, and five backups succeed. Replacing the vault does not diagnose the single failed operation or identify its error code.

C:

Creating another Recovery Services vault and enabling VM backup is a provisioning action, not error diagnosis for a protected VM in an existing functioning vault. It can introduce duplicate configuration while concealing the original failed job's reported cause.

D:

Stopping protection and deleting backup items would remove recovery coverage and may delete retained backup data. An unexplained single-VM job failure does not justify destructive changes, especially because five other protected VMs succeed. Read the failed job's error details and apply the corresponding documented fix instead.

Question 848

An admin needs to protect Azure Virtual Machines and also managed disks using Azure Backup. Which vault selection reflects the supported data-source distinction?

  1. A Backup vault is always required for standard Azure VM backups and can replace every Recovery Services vault.
  2. A Recovery Services vault is universally required for standalone managed disk backup.
  3. Use Recovery Services vault for supported Azure VM backups and Backup vault for the eligible standalone Azure Disk Backup datasource; confirm each workload support matrix.
  4. An Azure DNS private zone hosts both backup policies and stores the recovery points.

Explanation

Correct Answer

C:

The vaults have different supported backup workloads; selecting by datasource prevents invalid protection configurations.

Incorrect Answers

A:

Standard Azure VM backup traditionally uses a Recovery Services vault; treating Backup vault as universal for VM protection is incorrect.

B:

Azure Disk Backup is a Data Protection workload managed using a Backup vault, not universally a Recovery Services vault datasource.

D:

Private DNS zones provide name resolution rather than Azure Backup policies or managed recovery-point vault storage.

Question 849

A team needs agentless Azure Disk Backup for an individual managed data disk in West Europe. The backups should use supported incremental operational-tier snapshots, not Azure VM backup for an entire machine. Which vault design must be used?

  1. Use an Azure Recovery Services vault for entire-VM backup as a substitute for individual managed-disk operational backup.
  2. Create an Azure Backup vault only in North Europe and expect it to protect the West Europe managed disk across regions.
  3. Create a Blob operational-backup policy and attach it directly to the managed disk without configuring a disk Backup vault.
  4. Create an Azure Backup vault in West Europe, select a supported Azure Disk protection policy, and authorize the vault identity and snapshot resource group.

Explanation

Correct Answer

D:

Microsoft documents individual managed disk protection through an Azure Backup vault, a disk backup policy, and managed-identity permissions to the disk and snapshot resource group. The vault must be in the same region as the disk. Operational snapshots remain in the customer subscription rather than being copied into vault storage.

Incorrect Answers

A:

Recovery Services vaults protect Azure VM backup workloads, but the question explicitly asks for the dedicated Azure Disk Backup operational snapshot workflow for a managed disk. That workload uses Azure Backup vault and disk-specific policy rather than treating the full VM as the backup item.

B:

Azure Disk Backup requires the source disk and Backup vault to be in the same region. Cross-subscription support does not imply cross-region protection, so a North Europe vault cannot directly protect the stated West Europe disk.

C:

Azure Blob operational backup is a separate datasource and policy type. Attaching a Blob policy to a managed disk would not generate the managed-disk incremental snapshots or the required disk backup instance.

Question 850

An administrator is creating a NEW Azure Blob Backup policy in the current Resiliency experience. The company needs continuous point-in-time operational recovery of block blobs and also wants offsite vaulted retention. Which policy configuration matches the current Azure Backup model?

  1. Use an Azure Recovery Services vault VM policy and assume it automatically enables Blob point-in-time restore.
  2. Use a supported Backup vault and create a new Blob backup policy with the vaulted backup tier and operational backup retention configured as supported.
  3. Create a new Blob backup policy using only the operational tier, with the vaulted tier explicitly switched off.
  4. Use only an Azure Files share-snapshot policy because Blob Backup does not support continuous operational recovery.

Explanation

Correct Answer

B:

Azure Backup supports operational Blob protection for continuous local point-in-time recovery and a vaulted backup tier for offsite retained recovery points. In the current new Blob backup policy workflow, vaulted backup is selected by default and cannot be disabled, so a new policy can combine it with operational protection when supported. Configure the Backup vault, policy retention settings, and required identity permissions for the storage account, taking account of workload limitations and cost.

Incorrect Answers

A:

Azure Recovery Services vault VM backup policies protect supported virtual machine workloads and do not automatically configure Blob versioning, change feed, soft delete, and point-in-time recovery. Azure Blob Backup is a separate protected datasource with a Backup vault and its own policy configuration. Using an unrelated VM backup policy would not establish the requested continuous and vaulted Blob protection.

C:

Microsoft documents that the new Blob backup policy experience does not allow creation of an operational-only policy: vaulted backup is selected by default and cannot be turned off. Existing operational backup configurations and policies are unaffected, but the scenario explicitly asks for a new policy. This proposed configuration is therefore unsupported in the specified workflow and would not meet the requirement for offsite vaulted retention anyway.

D:

Azure Files share snapshots protect file-share content and are not interchangeable with Azure Blob Storage data protection. Azure Blob Backup provides an operational tier based on Blob versioning, change feed, soft delete and point-in-time restore, plus an optional vaulted protection component in supported configurations. An Azure Files-only policy would not protect the specified block blobs or provide their requested offsite copies.