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 88

Question 870

A protected production Azure VM in East US has a valid Recovery Services vault recovery point. Auditors need to boot a separate copy in resource group rg-restore-audit and a restricted test VNet in the same supported region; the running production VM and its disks must not be overwritten. Which Azure Backup restore approach should be selected?

  1. Mount the backup for file-level recovery and expect it to create a runnable copy of the original VM in rg-restore-audit.
  2. Choose a supported Create new VM/alternate-location restore from the selected recovery point, specifying the isolated test resource group and network.
  3. Select Replace existing VM from that recovery point; move the test DNS record afterward and keep production disks unchanged.
  4. Enable Azure Site Recovery test failover, even though this VM only has Azure Backup protection and no Site Recovery replication.

Explanation

Correct Answer

B:

Azure Backup supports restoring a VM as a new machine from an eligible recovery point rather than replacing production. Supply a compatible target resource group and network, validate resource prerequisites, and keep the production instance running.

Incorrect Answers

A:

Azure VM file recovery mounts a recovery point for retrieving individual files; it does not reconstruct and boot an independent virtual machine. It cannot fulfill the auditors' complete-VM test requirement.

C:

Replace existing VM is an original-location recovery operation that replaces the source's disks or VM state. Changing DNS afterward does not protect the original VM from the restore's destructive overwrite.

D:

Site Recovery test failover requires an already protected Site Recovery replicated item. An Azure Backup recovery point alone is not an ASR replication configuration; use the supported Azure VM backup restore choices already available.

Question 871

A Recovery Services vault backs up a production Windows VM every night. Last night's job failed before creating a new recovery point, but the vault still lists earlier valid VM recovery points. The service owner has authorized an urgent restore if an available point meets the incident's documented data-loss tolerance. What must the recovery operator establish before selecting the VM restore operation?

  1. Use the failed backup job ID as though it were a recovery point, because every scheduled job creates a restorable snapshot even when it fails.
  2. Examine the protected VM's actual available recovery points and timestamps, choose the latest suitable valid point, and disclose any RPO gap before restoring.
  3. Immediately overwrite the production VM with a guessed time from last night's schedule without verifying that a recovery point exists.
  4. Disable the Recovery Services vault's backup policy and wait for the next nightly schedule before examining any older recovery point.

Explanation

Correct Answer

B:

Earlier recovery points can remain available even if the most recent job failed. Confirm a usable point, examine its age and relevant consistency requirements against approved recovery objectives, then choose the appropriate supported restore path.

Incorrect Answers

A:

A failed scheduled job is evidence of an unsuccessful protection operation, not proof of a usable new recovery point. The operator must choose an actual listed recovery point rather than invent one from the failed job identifier.

C:

Original-location restore can replace the source VM disks. Guessing an unavailable time risks destructive action without recoverable data and bypasses the scenario's requirement to disclose the actual recovery-point age.

D:

Disabling a policy neither repairs the last failed job nor invalidates earlier restorable recovery points. Waiting until another schedule unnecessarily delays recovery while legitimate backup points already exist.

Question 872

A finance share protected by Azure Files snapshot-tier backup contains 30,000 files. Yesterday a clerk overwrote only `accounts/quarterly.csv`. The share is still online, and management explicitly forbids rolling back unrelated files. An eligible point from before the overwrite remains in the protected share's backup inventory. Which operation best meets the requirement?

  1. Restore the entire source VM from Azure VM Backup and assume that its disks contain the separately managed Azure Files share.
  2. Run a full-share original-location restore that replaces the whole online share, including files modified correctly after yesterday's recovery point.
  3. Use the protected Azure Files share's supported item-level restore to recover `accounts/quarterly.csv` from the selected snapshot-tier point to an approved original or alternate file destination.
  4. Restore a Blob container from its Blob version history; Azure Files SMB shares and Blob containers share one recovery-point inventory.

Explanation

Correct Answer

C:

Azure Backup supports item-level files/folders restoration from eligible snapshot-tier Azure Files recovery points. Select the specific file and supported target, verify its recovered contents, and preserve newer changes to other live share files.

Incorrect Answers

A:

Azure Files is a managed SMB file service with its own backup item. A VM-disk recovery targets a protected VM, not the independently protected share whose single file was overwritten.

B:

A complete share rollback would affect valid changes in thousands of unrelated files. Although full-share restore is supported in suitable Azure Files configurations, its broader restore scope violates the explicit file-only recovery constraint.

D:

Blob versioning applies to Blob objects, not the separate Azure Files backup inventory. A Blob container restore does not select this share's SMB file recovery point or return the overwritten file.

Question 873

An Azure VM is compromised. The incident-response team must preserve the original VM and disks for forensic imaging. An uncompromised Azure Backup recovery point has already been selected, and an isolated recovery VNet is available. Which TWO actions protect evidence and prove the recovered workload is usable before any approved cutover? Select TWO answers.

  1. Validate the restored application and its required dependencies within the isolation boundary before permitting production cutover.
  2. Use the Replace existing VM restore option to overwrite the compromised source disks immediately.
  3. Restore files directly into the still-compromised operating system and resume service without isolation.
  4. Attach restored disks to the original evidence VM before forensic imaging is completed.
  5. Restore the selected recovery point as a separate VM or disks in isolated resources, leaving the compromised originals unchanged.

Explanation

Correct Answers

A:

An isolated restore is not automatically a successful business recovery. Test application startup, data access and dependent services inside the recovery boundary, then document results for the incident-response team. This validates usability without allowing the restored VM to contact production before security clearance. The action complements restoring to separate resources: one protects evidence, while this one checks the integrity of the recovery before a controlled cutover.

E:

Azure Backup supports restoring disks or creating a new VM from a selected recovery point. By directing that restore to separate resources in the isolation VNet, responders can preserve the compromised machine and original disks for evidence. The new workload must remain disconnected from production until approved testing and security review have completed. This is the central choice that allows recovery work without using Replace existing against the forensic source.

Incorrect Answers

B:

Replace existing overwrites the source VM’s disks with recovered contents. That risks destroying the exact on-disk state investigators were instructed to preserve, and it is not the safe restore type for this incident. Azure Backup offers creation of a new VM and disk restore paths that let responders maintain the forensic original.

C:

File-level restore into the compromised guest mixes recovered data with an operating system that remains untrusted. It does not preserve an isolated clean recovery environment and may contaminate the recovery with active malware or persistence mechanisms. The requirement is to restore separate resources while retaining the source for evidence, not to repair the compromised VM in place.

D:

Attaching recovered disks to the compromised VM can modify the incident scene and expose clean data to the untrusted guest. It also prevents the forensic team from preserving the original disk state in a controlled manner before recovery work. Keep the original VM and its disks untouched; stage restored assets in separately authorized resources.

Question 874

An administrator is preparing to create a new Azure VM from a valid Recovery Services vault recovery point. The restore wizard currently selects a subnet that cannot reach the application's private database. The restore has not started and the approved destination VNet and subnet are available. What should be corrected before the restore?

  1. Always select an unrelated isolated VNet and complete production cutover without testing database reachability.
  2. Restore an Azure Files SMB share from its recovery point instead of configuring the VM network.
  3. Select the approved destination VNet and subnet in the Create new VM restore settings, and verify required routes and NSG access before restoring.
  4. Replace the existing VM disks with the recovery point and assume disk content automatically changes the VM's NIC subnet and firewall rules.

Explanation

Correct Answer

C:

Azure Backup's Create new VM restore allows selecting a resource group, target virtual network, and subnet. Choosing the approved reachable subnet before the restore, and verifying route and NSG constraints, addresses the actual network mismatch without changing the recovery point or backup dataset.

Incorrect Answers

A:

Isolation can be appropriate for forensic recovery, but selecting an unrelated VNet for production cutover does not satisfy the stated private-database reachability requirement. The approved target subnet is already available and must be selected deliberately for this VM restore.

B:

Azure Files share recovery restores share data and is unrelated to the VM's network-interface placement. The task concerns creating a VM from a VM backup recovery point and choosing its destination network.

D:

Replacing OS/data disks affects stored VM data, not the NIC's VNet and subnet assignment. Without adjusting network configuration, the restored application can remain disconnected from the private database.

Question 875

A Windows Azure VM runs a stateful order-processing application. Azure Backup reports last night's enhanced-policy VM backup job as Completed, but the recorded recovery point is `Crash-consistent` after the application-consistent snapshot attempt failed. The recovery contract requires a demonstrated application-consistent restore and recovery-time verification, not merely a successful storage snapshot. Which response should the backup administrator take before signing off?

  1. Approve the application-consistency requirement immediately because any Completed VM backup job means all VSS writers successfully quiesced the application.
  2. Review the recovery point's recorded consistency type and relevant VSS/backup extension behavior, remediate the application-consistency failure, and test restoring a suitable app-consistent point in isolation before attesting recovery objectives.
  3. Extend vault retention from 30 to 90 days; longer retention automatically converts old crash-consistent recovery points into application-consistent points.
  4. Switch the vault's backup-storage redundancy from LRS to GRS; geo-replication retroactively makes an existing crash-consistent snapshot application-consistent.

Explanation

Correct Answer

B:

Azure Backup distinguishes application-consistent, file-system-consistent and crash-consistent recovery points. An enhanced-policy backup can succeed with a crash-consistent fallback after app-consistent capture fails, so inspect actual consistency metadata and VSS/extension results. Restore the supported quiescing path, generate a suitable application-consistent backup and exercise an isolated application restore to assess RPO and recovery time instead of equating job completion with application assurance.

Incorrect Answers

A:

A Completed job means Azure Backup recorded an eligible recovery point; it does not assert that a Windows application's Volume Shadow Copy Service writers succeeded. The case specifically states the result is crash-consistent following an application quiescing failure. Approving the app-consistency requirement would ignore the documented recovery-point classification and the absence of a verified application restore.

C:

Recovery-point retention controls how long points are preserved, not how the original guest application was quiesced. Extending retention cannot transform the data already captured in a crash-consistent snapshot into an application-consistent snapshot. The operator must resolve application writer/backup consistency issues and create and test an eligible new point.

D:

LRS versus GRS determines durability and geographic redundancy of stored backup data, not the consistency level of a VM recovery point. Replicating an existing crash-consistent point copies that existing state; it does not re-run VSS writers or capture pending application I/O. Verify the actual backup consistency mechanism and test restore instead of changing vault redundancy.

Question 876

A critical Azure VM is pinned to availability zone 1 in East US, and its OS/data disks use supported managed disk types (neither zone-redundant nor Ultra Disks). East US has verified capacity and supports Azure Site Recovery zone-to-zone protection. Corporate data-residency policy prohibits the VM's replicated data leaving East US, but operations needs a recoverable VM if zone 1 fails. Which protection design matches these constraints?

  1. Configure Azure Site Recovery to replicate the VM from East US to West US, since a second Azure region is required even when data cannot leave East US.
  2. Keep only the VM's daily locally redundant backup recovery points and claim the VM is asynchronously replicated into an alternate availability zone.
  3. Convert the running zonal VM into an availability-set member through a resource tag; availability sets independently hold an asynchronously replicated hot VM in zone 2.
  4. Enable Azure Site Recovery disaster recovery BETWEEN availability zones, selecting an eligible alternate zone in East US and a different target resource group, then validate recovery in a supported drill.

Explanation

Correct Answer

D:

Microsoft documents Site Recovery zone-to-zone protection for eligible zonal Azure VMs in supported regions. It replicates between distinct zones without moving protected data outside the source region; the operator selects disaster recovery between availability zones and validates target eligibility. Source and target resource groups must be different even for same-region zone-to-zone DR. Drill and capacity tests are still needed, and a region-wide outage remains outside this narrow design.

Incorrect Answers

A:

Region-to-region Site Recovery would replicate VM data outside East US, violating the explicit residency rule. Azure Site Recovery also documents zone-to-zone replication within a supported region, so a second region is not inherently required to protect against a single availability-zone failure. A regional disaster would be a separate resilience risk that this design does not claim to cover.

B:

A daily Azure VM backup preserves recovery points for restoration but does not automatically provide the continuous asynchronous protected replica and failover procedure described for Site Recovery. Locally redundant backup storage does not create a standby VM replica in a separately selected zone. Backup can complement the solution for point-in-time recovery but does not satisfy this zone-level replication decision alone.

C:

Availability sets distribute VM instances across fault and update domains, not across independently selected Azure availability zones, and tagging a zonal VM does not migrate it into an availability set or duplicate its disks. The organization requires replicated VM state for a zonal outage; use the documented zone-to-zone Site Recovery workflow instead of metadata or availability-set assumptions.

Question 877

Before an Azure-to-Azure Site Recovery rollout, an administrator must verify that the existing VM generation, operating system, managed disk SKUs and any attached specialized disks meet the CURRENT replication support limits. The team must not start replication of an unsupported configuration. Which documented prerequisite should be used?

  1. Test failover, application checks and cleanup, recording observed RPO/RTO.
  2. Configure Site Recovery protection for supported disks and validate application consistency.
  3. Review the current Azure-to-Azure Site Recovery support matrix, checking the exact source VM generation, OS, managed disks, controller and target-region eligibility before enabling protection.
  4. Build an Azure Site Recovery recovery plan with groups and dependency steps.

Explanation

Correct Answer

C:

Microsoft publishes an Azure-to-Azure Site Recovery support matrix defining eligible VM platforms, managed-disk SKUs, controllers, operating systems, replication limits and exclusions such as temporary disk replication. Validate the actual source and target configuration against that matrix before enabling replication; a successful backup or later failover test is not a substitute for support eligibility.

Incorrect Answers

A:

A test failover measures recoverability only after a supported configuration is already replicating and can be booted in an isolated recovery network. The case asks whether the VM's disks, image and architecture are eligible before enabling protection, so consult the Azure-to-Azure Site Recovery support matrix and fix unsupported components first.

B:

Enabling protection assumes that the VM and every replicated disk are supported. Although disk support and application consistency matter later, the step requested is to check current OS, generation, disk SKU, controller and target-region eligibility against the published matrix first.

D:

A Site Recovery recovery plan orchestrates multiple workload recovery steps and dependencies once protected VMs are eligible. The requirement here is to verify support for the VM's disk/image configuration before enabling protection. Consult the current Azure-to-Azure support matrix, resolve incompatibilities, and then design the recovery plan.

Question 878

Azure-to-Azure Site Recovery replicates a production E-series VM from East US to West US. Replica synchronization is current, but a validation failover in West US reports `CoreCountSubscriptionQuotaReached` for the configured recovery VM family. The source-region compute quotas and the target VNet are healthy. Which change directly resolves this failover readiness defect?

  1. Raise East US source-family vCPU quotas; the source VM continues running there, so West US compute quotas are irrelevant.
  2. Increase the Recovery Services vault's geo-redundant backup storage setting, which automatically allocates more West US compute vCPUs.
  3. Check available West US subscription and VM-family vCPU quotas, request the required target-family increase or select a compatible recovery VM size with capacity, then rerun failover validation.
  4. Disable the VM's ongoing Site Recovery replication and keep only daily Azure VM Backup, assuming that it retains the same region failover readiness.

Explanation

Correct Answer

C:

Site Recovery target VM creation needs suitable SKU availability and adequate target subscription/region quotas. Resolve the named target-family limit or choose an eligible alternative and validate target network/capacity in a new failover test.

Incorrect Answers

A:

Source-region quota supports the running production VM. The stated failure happens when provisioning a recovery VM in West US, so changing East US capacity cannot grant West US family-specific compute entitlement.

B:

Vault backup redundancy protects backup configuration or recovery-point storage as applicable, not the quota consumed by the target Azure VM. A GRS setting is not a mechanism for reserving or increasing West US compute cores.

D:

Azure VM Backup retains periodic restore points but does not replace Site Recovery's replicated-VM failover workflow or its target compute prerequisites. Removing replication reduces disaster recovery readiness instead of fixing the reported quota.

Question 879

A SQL Server application VM has its OS disk and two transaction/data disks included in Azure-to-Azure Site Recovery protection. No disks have been added since replication was configured. The application requires a recovery point that can restore its in-flight database state consistently, not only a crash-consistent disk image. Which protection design best addresses the requirement?

  1. Configure supported application-consistent recovery-point generation and validate the application’s recovery behavior across its protected disks.
  2. Protect only the VM OS disk because application databases recover automatically without data disk replication.
  3. Create an Azure Site Recovery recovery plan but leave all recovery-point consistency settings unchanged.
  4. Enable replication on a newly attached disk even though the VM has no new or unprotected disks.

Explanation

Correct Answer

A:

Azure Site Recovery distinguishes crash-consistent from application-consistent recovery points. For a workload that needs a consistent database state, configure supported application-consistent snapshots using the relevant in-guest mechanisms, subject to application and platform support, and check that the required disks are actually replicated. Test recovery to confirm the database’s behavior rather than assuming a crash-consistent point includes outstanding application transactions. This is different from merely adding disks to an already protected VM or sequencing multiple machines in a recovery plan.

Incorrect Answers

B:

Replicating only the OS disk omits the database files and logs on the data disks identified in the scenario. A recovery point that lacks necessary application data cannot reproduce the intended service consistently. Verify supported disk protection and recovery-point type rather than assuming database recovery is automatic without the data volumes.

C:

A Site Recovery recovery plan controls failover orchestration and ordering across machines; it does not by itself change whether an individual recovery point is application-consistent. The case is about the consistent state of one database VM and its disks. Select and validate the appropriate recovery-point consistency mechanism.

D:

There is no newly attached or unprotected disk in this scenario. The separate Azure Site Recovery procedure for newly added disks is useful when a protected VM receives more data disks, but it will not improve the current workload’s application consistency. Use a supported application-consistent recovery-point policy and verify recovery instead.

Question 880

Three protected Azure VMs form a billing service: `sql-db` must finish startup before `api-core`, and a web frontend must start last. All three already replicate to the same Azure Site Recovery target region. During a failover the operator also needs an approved manual check after database startup and before the API tier starts. Which configuration supports this ordered dependency workflow?

  1. Put all three replicated VMs in the same default recovery group and assume Site Recovery starts them one-by-one in database-to-web dependency order.
  2. Increase the Azure Backup daily retention policy to introduce an ordering dependency between Site Recovery VM startups.
  3. Only change the target VNet's DNS servers; DNS settings alone create ordered Site Recovery startup groups and a manual approval step.
  4. Create or customize a Site Recovery recovery plan with separate ordered VM groups and an appropriate manual or runbook action between the database and API groups; test it.

Explanation

Correct Answer

D:

Site Recovery recovery plans group protected VMs in an explicit startup order and can insert manual instructions or supported automation runbooks. Put SQL first, validate database readiness, then start API and web groups and rehearse the steps in a test failover.

Incorrect Answers

A:

A single recovery-plan group starts its included machines together rather than enforcing the required sequential tier readiness. The database's success cannot be verified before the API runs if everything is in one group with no intervening action.

B:

Backup retention controls how long backup recovery points are kept. It does not specify failover sequence, insert human actions, or coordinate startup of already Site Recovery-replicated VMs.

C:

Correct DNS helps users reach recovered services but does not order VM starts or enforce a database-readiness gate. Recovery-plan group configuration is the mechanism that expresses this dependency in the failover workflow.