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 86

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.

Question 851

An Azure Backup vault in North Europe protects supported Blob data with VAULTED recovery points under a retention policy. Its Immutable vault property is currently Enabled but not locked, so a sufficiently privileged administrator could disable immutability. Security has now completed its impact review and requires the vaulted recovery points to remain protected from deletion for their policy retention period even if an attacker compromises the backup administrator account. Which action establishes the required IRREVERSIBLE vault control?

  1. Enable Blob soft delete on the source storage account only; this automatically makes all existing Azure Backup vaulted recovery points impossible to delete.
  2. In the Backup vault Properties > Immutable vault settings, lock the already-enabled immutability after confirming the retention impact, putting it into Enabled and locked state.
  3. Leave vault immutability in its Enabled but unlocked state, because privileged vault administrators can never disable that state.
  4. Apply an Azure Resource Manager ReadOnly management lock to the source Blob container only, because this automatically enables WORM protection for vaulted recovery points.

Explanation

Correct Answer

B:

Microsoft documents that an Enabled (unlocked) immutable vault may still have immutability disabled. Moving the Backup vault property to Enabled and locked makes immutability irreversible and blocks operations that would destroy protected vaulted recovery points during their policy-based retention. Verify governance approval and impact before locking: you cannot later turn the setting off. Azure Backup vault immutability protects the vaulted layer, not source-service operational snapshots.

Incorrect Answers

A:

Blob soft delete is a protection and recovery mechanism for eligible source storage blobs. It is not equivalent to locking the Azure Backup vault immutability property and does not make the vault’s retained recovery points unchangeable. Operational Blob backup is a separate layer and is not protected by the immutable-vault setting.

C:

Enabled without locking is intentionally reversible. A sufficiently privileged user can disable the immutability control, which violates the stated requirement to resist compromise of that same backup administrator. Irreversibility requires the separate Lock action; merely leaving the currently enabled property unchanged does not supply it.

D:

A management-plane ReadOnly lock on a source Blob container does not enable immutable Azure Backup vaulted recovery points or guarantee their retention. The control must be applied to the Backup vault’s immutable-vault settings. Source Blob WORM policies and operational snapshots are separate mechanisms.

Question 852

A Backup vault named bv-archive was created in West Europe with locally redundant storage (LRS), but no protected data sources have been added. A newly approved policy now requires ZRS for future VAULTED Azure Blob backup data so recovery points survive an availability-zone outage without being copied to another region. The protected workload and region support ZRS, and there are no existing recovery points to preserve. What must the administrator do?

  1. Edit the existing Backup vault’s redundancy from LRS to ZRS because it has no protected data sources yet.
  2. Change the storage replication property on a Recovery Services vault and assume the change also updates bv-archive.
  3. Attach a storage redundancy Azure Policy assignment to bv-archive; Azure Policy automatically converts its existing vault storage to ZRS in place.
  4. Create a new Backup vault in West Europe with ZRS chosen at creation, then onboard the eligible vaulted Blob protection to that vault.

Explanation

Correct Answer

D:

Microsoft’s Azure Backup reliability guidance distinguishes vault types: a Backup vault’s storage redundancy is selected during VAULT CREATION and then locked. Because the current LRS vault holds no backups, the direct supported remediation is to create another Backup vault in West Europe configured with ZRS, and use that vault for the new eligible vaulted Blob policy. This differs from the pre-first-backup editing window of Recovery Services vaults.

Incorrect Answers

A:

Unlike a Recovery Services vault, where the setting can be changed before protecting workloads, a Backup vault locks the backup-data redundancy setting once the VAULT RESOURCE IS CREATED. The lack of protected items does not reopen the existing bv-archive storage choice. An in-place LRS-to-ZRS edit is not supported.

B:

Recovery Services vault and Backup vault are separate resource types with their own configuration and supported workloads. Editing a different vault does not change the already-created bv-archive resource or supply the required ZRS protection for its eventual vaulted Blob backups.

C:

Azure Policy can audit or restrict future configurations when appropriate, but it does not bypass an Azure Backup vault’s immutable post-creation redundancy setting. Assigning a governance policy alone does not replace the existing LRS vault with supported ZRS storage.

Question 853

A Backup vault `bv-docs` has its system-assigned managed identity enabled and will protect block blobs in GPv2 storage account `stlegal` through a supported Azure Blob backup policy. Vault and storage account meet region and workload requirements. A protection-readiness check says the Backup vault lacks permissions on `stlegal`. The human administrator has Reader access and cannot expand the vault identity to subscription-wide Contributor. Which assignment fixes this service-identity authorization gap most precisely?

  1. Give the human administrator Backup Reader on `bv-docs`; this automatically grants the vault identity write permissions to the protected storage account.
  2. Assign Storage Blob Data Reader to the human administrator on `stlegal`; the backup service can then create backup-owned protection controls using the administrator's session.
  3. Give the Backup vault managed identity general Contributor at the subscription scope to avoid selecting a specialized storage role.
  4. Assign the built-in Storage Account Backup Contributor role to the Backup vault system-assigned managed identity on `stlegal`, wait for RBAC propagation, and rerun the protection-readiness check.

Explanation

Correct Answer

D:

Microsoft specifies Storage Account Backup Contributor for the Backup vault's managed identity on protected Azure Blob storage accounts, covering the necessary backup and storage protection operations such as backup-owned delete locks. Assign it at the specific `stlegal` account scope, let access propagate, and confirm the vault readiness check. The human caller's permissions are separate from the vault identity's permissions.

Incorrect Answers

A:

Backup Reader permits a human to inspect supported backup information, not to endow a separate Backup vault managed identity with storage account control. The readiness error identifies the service identity, so changing only the operator's vault read access cannot authorize protection on `stlegal`.

B:

Storage Blob Data Reader gives a principal read-only Blob data-plane access; it is not the role Microsoft specifies for a Backup vault to apply backup-related storage protections and manage the necessary configuration. Giving that role to the human does not make the separate system-assigned managed identity authorized on the storage account.

C:

Broad Contributor at subscription scope is unnecessarily powerful and does not follow the documented least-privilege storage backup role model. The vault identity requires the appropriate permissions on the named storage datasource, not general management of all subscription resources. Avoid excess RBAC grants when a purpose-built role exists.

Question 854

A company uses Azure Disk Backup for managed disks in one supported region. Production disk recovery points and test disk recovery points need different retention policies. More importantly, production backup operators must not be able to administer or restore the test team’s backup instances, and test operators must not administer production backup instances. Both teams currently have Backup Contributor permissions at the scope of a shared Backup vault; the security review requires a verifiable backup-management authorization boundary. Which design should the administrators implement for new protection?

  1. Keep the shared Backup vault, use one default retention policy, and leave both teams as Backup Contributors at vault scope because the policy name enforces operator isolation.
  2. Keep the shared Backup vault and create differently named production and test backup policies, but retain the existing unrestricted vault-level Backup Contributor assignments for both teams.
  3. Grant both operator groups subscription Owner in the same subscription while putting their protected disk resources into separate Azure resource groups; the Owner role is narrower than Backup Contributor.
  4. Use separate supported Backup vaults for production and test disks, configure the distinct retention policies, and scope each team’s backup administration to its own vault and authorized source disks, without broad access to the other vault.

Explanation

Correct Answer

D:

Microsoft Azure Backup guidance recommends separate vaults when independently managed departments or production and nonproduction environments require separate access boundaries. Distinct vault-level RBAC grants plus appropriate permissions on each source Disk Backup resource enforce that separation, while each vault can hold its own supported disk retention policy. Both teams must be removed from any legacy overbroad shared-vault role assignments as part of the transition.

Incorrect Answers

A:

A shared default policy cannot enforce the separate retention periods and does not override the role grants already permitting both teams to manage the same vault. The requested boundary concerns who can administer backup instances, not merely how long points are retained.

B:

Different backup policies can produce different schedules/retention in one vault, but keeping both groups as vault-level Backup Contributors still allows broad management across the shared vault. Renaming or splitting policies is insufficient for the explicit independent authorization boundary.

C:

Subscription Owner grants broadly elevated permissions, not a restricted backup-management boundary. Separate resource groups alone do not remove existing cross-team vault access or reduce subscription Owner permissions; this would weaken least privilege.

Question 855

An administrator must ensure deleted Azure Backup instances remain recoverable during the supported soft-delete retention period. Which vault-level review or configuration is most appropriate given that some regions enforce soft delete by default?

  1. Grant required scoped backup permissions to the vault identity.
  2. Check support matrix and use a Recovery Services vault or another eligible service.
  3. Verify the vault soft-delete state, supported retention and security controls for the protected datasource.
  4. Validate regional and datasource restrictions rather than assume global coverage.

Explanation

Correct Answer

C:

Soft delete retains eligible deleted backup items for a recovery window rather than allowing immediate irretrievable removal. Verify the vault’s enforced/default soft-delete state and configure supported retention/security settings where adjustable; never assume every vault region or datasource exposes an enable/disable switch.

Incorrect Answers

A:

Data-source identity permissions let backup jobs reach the storage or disk resource; they don't alter redundancy, soft-delete retention or job reporting.

B:

A backup-vault support matrix helps establish workload eligibility but doesn't create retention against accidental deletion of backups. Configure supported soft-delete and backup security controls for the protected datasource so deleted backup items can be retained and recoverable for the relevant protection window.

D:

Checking region/support constraints establishes eligibility; it doesn't configure soft-delete retention for accidentally deleted backup items.

Question 856

Azure Disk Backup is configured for managed disk `disk-invoices` in East US, subscription A. The Backup vault `bv-fin` is also in East US but in subscription B. Its managed identity already has Disk Backup Reader on the source disk. The operator selected an East US snapshot resource group in subscription B, and configuration fails with `UserErrorSnapshotRGSubscriptionMismatch`. Business policy requires leaving the source disk in subscription A and keeping the eligible cross-subscription vault. Which correction is required?

  1. Move the source disk into subscription B because Azure Disk Backup prohibits a Backup vault and source disk in different subscriptions.
  2. Enable geo-redundant backup vault storage so incremental snapshots can be created in a resource group from the vault subscription.
  3. Select or create the snapshot resource group in subscription A, where the source disk resides, and grant `bv-fin` managed identity Disk Snapshot Contributor on that group.
  4. Keep the snapshot group in subscription B and give its owner subscription-wide Owner on subscription A; the additional Azure RBAC scope removes the snapshot subscription restriction.

Explanation

Correct Answer

C:

Microsoft requires the disk and its incremental-snapshot resource group to be in the same subscription, even though an eligible Backup vault can reside in a different subscription of the same region. Use an East US snapshot resource group within source subscription A and give the Backup vault managed identity Disk Snapshot Contributor on that group. Its already-confirmed Disk Backup Reader role on the source disk remains in place.

Incorrect Answers

A:

Azure Disk Backup permits a Backup vault and source disk in different subscriptions when regional and other prerequisites are satisfied. Moving the workload disk is not required and violates the case's explicit subscription boundary. The failing prerequisite concerns where incremental snapshots for that disk are created.

B:

Azure Disk Backup creates operational-tier incremental disk snapshots in a customer-selected snapshot resource group and does not use backup vault redundancy to override snapshot locality. GRS settings on the Backup vault do not make a resource group in subscription B valid for a disk that belongs to subscription A.

D:

Giving broadly privileged Owner rights does not alter where Azure managed-disk incremental snapshots may reside. The service still rejects a snapshot group in a different subscription from its source disk, and subscription-wide Owner introduces unnecessary privilege. Correct the snapshot group subscription and assign the documented scoped snapshot role instead.

Question 857

A backup operations team needs a single view of job health across several Recovery Services and Backup vaults. Which supported Azure experience should it use for cross-vault monitoring rather than opening each vault separately?

  1. Grant required scoped backup permissions to the vault identity.
  2. Use Azure Business Continuity Center (Resiliency) for cross-vault monitoring, with Backup Reports or Azure Monitor for deeper trends.
  3. Enable vault soft-delete/security controls and validate workload support.
  4. Choose an Azure Backup vault and the supported blob protection model.

Explanation

Correct Answer

B:

Azure Business Continuity Center (Resiliency) provides at-scale visibility across backup and disaster recovery resources, including backup job monitoring. Backup Reports and Azure Monitor complement the operational view with workspace-based history; the older Backup center experience is no longer directly searchable in the Azure portal.

Incorrect Answers

A:

Granting a vault-managed identity permissions may correct a specific datasource authorization failure. It does not combine job status from several vaults into one operational view.

C:

Soft delete prevents loss of supported backup data after accidental deletion; it does not aggregate failed or successful backup jobs across separate vaults.

D:

Selecting a Backup vault and a blob protection model determines how an eligible datasource is protected. It does not provide a consolidated cross-vault job inventory or reporting experience.

Question 858

The operations team protects a supported Azure Windows VM in a Recovery Services vault. Compliance requires one scheduled backup each night at 23:00 UTC and 30 days of restorable daily recovery points in the vault; on-demand snapshots alone do not satisfy the policy. What should be configured?

  1. Enable only on-demand managed-disk snapshots and rely on a two-day snapshot instant-restore window.
  2. Create or modify an Azure VM backup policy with a daily 23:00 UTC schedule and 30-day daily retention, then associate the VM with that policy.
  3. Configure only monthly and yearly long-term retention tiers and disable the daily VM backup schedule.
  4. Enable a VM-creation Azure Policy assignment without selecting the backup schedule or retention values required by compliance.

Explanation

Correct Answer

B:

An Azure VM backup policy defines backup frequency, time and retention. Associating the VM with a daily policy set to 23:00 UTC and 30-day retention meets both required dimensions.

Incorrect Answers

A:

Standalone disk snapshots and the short instant-restore snapshot retention are not equivalent to 30 days of scheduled vault recovery points for the protected VM.

C:

Monthly/yearly retention controls preserve selected long-term points but do not by themselves configure the required daily backup schedule and 30 daily points.

D:

A governance policy can enroll eligible VMs, but without a backup policy specifying the stated schedule and 30-day daily retention, it does not establish the compliance configuration.

Question 859

A supported SQL Server database on a Windows Azure VM uses the full recovery model. The organization already backs up the VM daily, but the database must also be recoverable to a specific minute between those whole-VM recovery points. A Recovery Services vault in the VM's region is available, and security approves workload-aware protection. Which policy design meets this database-level point-in-time recovery requirement?

  1. Keep only the daily Azure VM image backup; any application-consistent VM recovery point automatically provides transaction-log restoration to each intervening minute.
  2. Enable a subscription policy that onboards the VM to image backup but does not discover or protect individual SQL database backup items.
  3. Increase monthly retention on the existing VM image backup policy and assume longer image retention generates SQL Server log backups.
  4. Discover and protect the SQL Server databases in the Recovery Services vault using a supported SQL-in-Azure-VM workload backup policy with full/differential and frequent transaction-log backups; verify recovery coverage of the log chain.

Explanation

Correct Answer

D:

Azure Backup supports SQL Server in Azure VMs as a workload protected in a Recovery Services vault. For supported databases in full recovery model, configure SQL database discovery and full/differential and transaction-log backup schedules. Transaction-log backups allow SQL database point-in-time restoration within the uninterrupted available log chain; validate successful log jobs and recovery prerequisites rather than assuming a daily VM image can restore to an arbitrary intervening minute.

Incorrect Answers

A:

An Azure VM image or application-consistent snapshot provides a recovery point at its own capture time. It does not automatically create a transaction-log backup chain with fine-grained database point-in-time restore between daily VM snapshots. The requirement is explicitly for restoring SQL Server to a minute inside the backup interval; protect the SQL workload and configure log backups instead.

B:

Azure Policy can automate eligible VM backup enrollment, but simply onboarding the whole VM does not discover SQL database objects and configure their workload-specific transaction-log schedule. The recovery requirement concerns one database's point in time between VM-image recovery points, so a SQL-in-VM backup policy is necessary.

C:

Monthly or yearly retention determines how long selected recovery points are kept; it does not increase the frequency or granularity of SQL transaction-log capture. A longer daily VM backup history still lacks the required between-snapshot database log chain unless separate SQL workload backups are configured.

Question 860

Finance already backs up Azure VMs daily using a valid Recovery Services vault policy with 30-day daily retention. New audit rules require a representative monthly recovery point for 60 months and a yearly recovery point for five years, without reducing daily protection. Which policy change meets the additional obligation?

  1. Add monthly and yearly retention tiers to the existing eligible VM backup policy for the specified 60-month and five-year durations while keeping daily backups enabled.
  2. Change the backup schedule to one backup per month and remove daily backups, assuming monthly frequency is the required Azure VM backup schedule.
  3. Set only the instant-restore snapshot retention to five years; the vault policy needs no long-term settings.
  4. Stop backup with Retain Data, because preserving the most recent historical point creates monthly/yearly future points without another job.

Explanation

Correct Answer

A:

The VM policy can retain selected daily/weekly recovery points for monthly and yearly long-term horizons. Specifying 60 monthly and five yearly periods satisfies the audit requirement without removing daily scheduled protection.

Incorrect Answers

B:

Azure VM extension backup schedules are daily or weekly; monthly/yearly are retention tiers, not an alternative calendar-frequency backup job that would satisfy ongoing daily protection.

C:

Instant Restore snapshots have short separate retention windows; they cannot replace 60 months of vault long-term recovery-point retention.

D:

Stopping backup preserves historical data but stops new recovery points. It cannot produce the upcoming monthly and annual protected points the requirement calls for.