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 89

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.

Question 881

An operator configured only daily Azure VM backups for a service with an aggressive regional outage recovery time objective. The service must be able to restart in a secondary region using continuously replicated VM state. What additional Azure service meets this intent?

  1. Use Azure Backup retention only and assume new VMs are continuously operating in a second region.
  2. Configure supported Azure-to-Azure Site Recovery replication and a tested failover target; retain Azure Backup separately for point-in-time recovery.
  3. Increase the Recovery Services vault storage account file-share quota; that creates a ready-to-run secondary VM.
  4. Turn on Windows Server File History inside the primary VM and assume regional disaster recovery is thereby configured.

Explanation

Correct Answer

B:

Site Recovery replicates supported machines into the chosen target region and enables tested failover workflows, complementing backup rather than replacing it.

Incorrect Answers

A:

Point-in-time backups are important for recovery but are not equivalent to a ready-to-failover continuously replicated regional VM state.

C:

File-share quotas do not protect the VM’s compute configuration or establish a secondary-region recovery target.

D:

Guest file versioning does not provision a supported cross-region VM replication/failover architecture.

Question 882

Azure-to-Azure Site Recovery is already replicating VM vm-accounting. Operations adds a new managed data disk that holds report exports. The vault reports a replication-health warning and lists the new disk as Not protected. The recovery plan must include the new data. What is the corrective action?

  1. Disable Site Recovery on the VM and erase all existing replicated recovery points immediately.
  2. Open the replicated item’s Disks pane and enable replication for the newly added unprotected data disk.
  3. Change only the VM’s Azure Backup daily retention policy, leaving Site Recovery disk protection unchanged.
  4. Create an application-consistent recovery point without enabling replication for the new disk.

Explanation

Correct Answer

B:

When a new managed disk is attached after Azure-to-Azure replication was enabled, Site Recovery identifies it as available for protection rather than automatically guaranteeing replication. In the Recovery Services vault, open Replicated Items, select the VM and its Disks pane, then enable replication for the disk marked Not protected. After initial synchronization completes, the disk becomes protected and the related health warning can clear. Validate recovery coverage and data expectations before relying on future failover.

Incorrect Answers

A:

Disabling replication and deleting recovery points would disrupt existing disaster-recovery protection and is unnecessary for adding a supported managed disk. Azure Site Recovery has a targeted procedure to add protection for the new disk while the VM remains a replicated item. Preserve existing protected disks and follow that procedure instead of resetting disaster recovery.

C:

Azure Backup policy retention controls backup recovery points, not the list of Azure Site Recovery replicated disks. Changing backup retention would not copy the new report-export disk to the recovery region or resolve the Not protected warning. Use the Site Recovery replicated-item disk controls instead.

D:

Application-consistent snapshots address transaction or application state for disks that are included in protection. They do not cause an unprotected newly attached disk to be replicated automatically. The disk must first be enrolled in replication, after which the team can validate recovery consistency against its actual workload.

Question 883

Azure-to-Azure Site Recovery already protects VM vm-orders from East US to West US. Its replicated-item Network settings still select West US virtual network `dr-old`. Security has provisioned approved target VNet `dr-secured` with subnet `app`. An administrator updated the source-to-target network-mapping DEFAULT for future VMs, but vm-orders is still configured for dr-old. Before a real regional failover, which action changes the destination for THIS already-protected VM without affecting other replication items?

  1. Open vm-orders under Site Recovery Replicated Items, edit its Network settings, and select target VNet dr-secured and subnet app for its failover NIC configuration.
  2. Change the general source-to-target network mapping once more; all existing protected VMs automatically switch their previously selected target VNet/subnet retroactively.
  3. Run a test failover into dr-secured and clean it up; the test-network selection automatically becomes the target VNet for real failover of all existing VMs.
  4. Add a subnet route table pointing at dr-secured in East US; this rewrites the Site Recovery target VNet recorded for vm-orders in West US.

Explanation

Correct Answer

A:

Site Recovery maintains target-network settings for each replicated VM, including its VNet and subnet choices. Microsoft states that modifying a network mapping adjusts defaults for NEW replication rather than existing protected items. For this already-replicating VM, open the Replicated Item Network settings and explicitly select the intended West US VNet/subnet (and eligible NIC settings), then verify the recovery configuration before the next actual failover.

Incorrect Answers

B:

A source-to-target VNet mapping is a default used when replication is enabled for new items. Microsoft explicitly states that modifying a network mapping does not change already protected VMs' target VNet selections. Repeating the global mapping edit therefore leaves vm-orders pointing at dr-old. The per-item network configuration must be changed directly.

C:

A test failover network is chosen for a rehearsal and should ordinarily be isolated from the production recovery network. Choosing dr-secured as a test destination does not implicitly rewrite the existing item's configured production-failover target. It also risks deploying a rehearsal VM into the production recovery network. Update the replicated item's actual Network settings, leaving the test environment separate.

D:

Subnet route tables determine traffic forwarding for network interfaces; they cannot modify Site Recovery metadata about the VNet/subnet to attach to the replica on a real failover. A route from an East US subnet does not change vm-orders' recorded West US target NIC destination. The failure domain is per-item recovery configuration, not packet routing.

Question 884

An Azure-to-Azure Site Recovery disaster recovery drill for replicated VM vm-claims has finished successfully in a nonproduction target VNet. Staff verified the recovered application and recorded results, but the replicated item still shows Cleanup test failover pending and the temporary test VM exists. Production VMs and ongoing replication must remain protected. What is the correct next administrative operation?

  1. Select Commit on the production failover workflow; this finalizes test failover and keeps the temporary drill VM as the protected primary.
  2. Run Re-protect against the temporary test-failover VM, treating it as a committed production failover that must now replicate in reverse.
  3. Select Cleanup test failover on the replicated item, record the drill observations and confirm Testing is complete so Site Recovery removes the temporary test resources while source replication continues.
  4. Disable Site Recovery replication for the source VM and manually delete the source disks, because test-failover cleanup requires destroying the production replication relationship.

Explanation

Correct Answer

C:

Azure Site Recovery documents Cleanup test failover after validating the test VM and application. Record observations and choose Testing is complete to remove the temporary VM/resources and clear the test-failover state while the original protected VM continues normal replication. This completes the drill without converting it into a real failover or deleting the primary VM.

Incorrect Answers

A:

Commit finalizes a real Site Recovery failover to a selected recovery point. It is not the operation that clears a completed test failover drill or deletes its temporary replica. The item remains in the test cleanup state until the administrator uses Cleanup test failover and records completion in the supported drill workflow.

B:

Re-protect applies after a real failover is committed, to restore disaster-recovery replication in the reverse direction. A test failover only boots a temporary VM in a test network without changing the protected production VM, so it does not require reverse replication. The pending task is cleanup of the temporary drill resources.

D:

Disabling replication removes the production VM from Site Recovery protection and would undermine rather than complete the business-continuity drill. Site Recovery provides an explicit cleanup operation to delete only resources created for test failover, without interrupting protection of the source. Source disk deletion is destructive and contrary to the case.

Question 885

A region-wide East US outage has made a company's production order-processing Azure VMs unreachable. Their Site Recovery replicated items in West US are healthy and an approved incident commander has authorized a REAL disaster recovery cutover now. No planned source-side shutdown is possible. What is the appropriate Site Recovery operation?

  1. Run Test failover into an isolated test network and treat the test VMs as the committed production workload without performing a real failover.
  2. Run only Re-protect toward East US while the source is unavailable; this automatically starts the West US workload without selecting a recovery point.
  3. Initiate an unplanned Site Recovery failover to an eligible West US recovery point, verify the recovered application and connectivity, and commit after the checks.
  4. Perform a planned failover requiring a clean shutdown and final synchronization of the currently unreachable East US source VMs.

Explanation

Correct Answer

C:

An unplanned failover starts the pre-replicated workload in the target region when a planned source shutdown is unavailable. Choose an appropriate point, validate network/application state and then commit the recovery point under the incident procedure.

Incorrect Answers

A:

Test failover is a non-disruptive drill that uses an isolated environment and is cleaned up afterward. It is not the real recovery action needed to route production service to the replica VMs during an outage.

B:

Re-protect reverses replication direction after an actual failover has been committed. It is not the command to bring up a secondary service from healthy replicas during an ongoing primary-region disaster.

D:

Planned failover assumes the source is reachable so the final synchronization and controlled shutdown can be performed. A fully unavailable source region makes that workflow unsuitable for the stated active outage.

Question 886

A protected Azure VM must fail over from an unavailable primary region to its Site Recovery secondary region during an outage. The incident commander prioritizes the shortest time to bring up the secondary VM (lowest recovery time objective), accepts using the most recently ALREADY PROCESSED recovery point, and will separately report any recovery-point age against the business RPO. Which Azure-to-Azure Site Recovery failover recovery-point choice best meets this objective?

  1. Select Latest and promise it cannot add any processing time and guarantees zero data loss for all writes made before the region went offline.
  2. Select Latest app-consistent because it is always the newest replicated recovery point and necessarily starts faster than the latest processed point.
  3. Select a Custom recovery point from an arbitrarily old timestamp and treat the selected timestamp as proof that no production data can be lost.
  4. Select Latest processed: Site Recovery uses its most recently processed recovery point without spending failover time processing unprocessed replicated data; verify its timestamp and the recovered application.

Explanation

Correct Answer

D:

Microsoft Learn specifies that Latest processed uses the most recently processed Site Recovery recovery point and spends no time processing unprocessed replicated data, providing a low recovery time objective. It still requires checking the actual recovery-point timestamp and validating the recovered VM and workload; low RTO does not by itself promise zero RPO or application consistency.

Incorrect Answers

A:

Microsoft differentiates Latest from Latest processed. Latest can process data already sent to Site Recovery before creating a recovery point, which may improve the data recency but can require additional processing time. It does not prove synchronous zero data loss for an unavailable source region. The case explicitly prioritizes minimal RTO using the latest ALREADY PROCESSED point.

B:

Latest app-consistent uses an available application-consistent recovery point when enabled, which might be older than the latest processed point. Application consistency is important to test where required, but it is not an unconditional low-RTO setting and is not necessarily the newest point. The commander has specified the most recent already processed point and prioritizes rapid recovery.

C:

A custom recovery point (where available) is used for a deliberate point-in-time recovery decision, not as a guarantee of freshness or zero loss. Choosing an older arbitrary timestamp may worsen RPO, and the timestamp must be assessed explicitly against business tolerance. The documented low-RTO recovery-point option is Latest processed.

Question 887

The payroll VM has continuous Azure Site Recovery protection from East US to West US. A quarterly drill must prove the recovery VM can boot and resolve test-only DNS within West US `vnet-dr-test`, which has no peering or routes to production. Payroll users must remain on the existing East US VM. When launching the DR drill, what network-related Site Recovery choice provides that isolation?

  1. Use Planned failover to the normal West US production VNet; a planned production switchover is necessary to choose a network for the drill.
  2. Start Site Recovery Test failover and explicitly select isolated `vnet-dr-test` as the test failover network; validate the VM and application there without redirecting production users.
  3. Start Unplanned failover to the secondary region's production VNet, then permanently commit the new VM so that the drill appears in production monitoring.
  4. Restore an Azure VM Backup point over the source VM's current OS disk and create a test VNet afterward to isolate the replaced source.

Explanation

Correct Answer

B:

Test failover lets an operator choose a designated test VNet for the recovered replica while source replication and production service remain active. Using the unpeered `vnet-dr-test` validates startup and DNS without establishing routes to the live workload; the drill can later be cleaned up separately.

Incorrect Answers

A:

Planned failover is a real operational cutover; it is not required to create a test copy on the isolated network. Selecting the production VNet would defeat the stated isolation goal even if the recovery VM booted.

C:

Unplanned failover and commit are for real disaster recovery, not a test of isolated VNet DNS. Publishing a permanently recovered production VM would violate the requirement to leave East US users and workload unchanged.

D:

An Azure Backup original-location restore changes the source VM rather than using Site Recovery's non-disruptive replica test. Creating a test network later cannot reverse that overwrite or demonstrate the target DR VNet selection.

Question 888

After a real Azure Site Recovery failover, the recovered application VMs boot in the target region. Before committing the chosen recovery point and directing production users there, which verification is most important?

  1. Commit immediately without testing service endpoints, because VM boot status guarantees the application is usable.
  2. Delete the replicated VMs in the source region before confirming client access to the recovered service.
  3. Validate application health, target VNet/subnet/DNS and data consistency; then commit the supported failover recovery point after stakeholder confirmation.
  4. Run only the test-failover cleanup procedure on the newly recovered production VMs as a substitute for validation.

Explanation

Correct Answer

C:

Service and network validation before commit ensures the selected recovery point is usable; committing typically removes the option to change the recovery point.

Incorrect Answers

A:

VM power-on alone does not establish that application listeners, identity dependencies or required target-region routes are functional.

B:

Deleting source infrastructure before validating the target introduces avoidable risk and does not establish correct failover.

D:

Test-failover cleanup is for isolated rehearsal resources and is not the correct validation/commit path for real production failover.

Question 889

Azure Site Recovery has completed and committed an Azure-to-Azure failover from the primary region to the secondary region. The application is now running on the secondary VMs. The primary region is reachable again, and the team wants to establish reverse replication before any planned failback. Which Site Recovery operation should be started?

  1. Start another unplanned failover immediately, before replicating any secondary-region changes back to the primary region.
  2. Run Re-protect on the committed failed-over VMs, verifying the secondary-to-primary replication settings and progress.
  3. Change the public DNS record to the primary IP and assume DNS replication synchronizes the secondary VM disks.
  4. Run a test failover to an isolated test network and treat it as production reverse replication.

Explanation

Correct Answer

B:

After committing the first Azure-to-Azure failover, Microsoft documents the Re-protect operation to reverse the replication direction from secondary to primary. The operator must confirm the target recovery region and synchronization state before undertaking a later failback.

Incorrect Answers

A:

Unplanned failover is used to move services during a failure and may select an older recovery point; it does not prepare the running secondary VMs to replicate their updated data back to primary. A new failover without reverse replication risks data loss or an invalid recovery sequence.

C:

DNS changes influence where clients connect; they do not establish data replication between Azure regions. Pointing clients back to primary before its VMs are synchronized could route traffic to stale services.

D:

Test failover validates recoverability in an isolated environment without changing the protected production replication flow. It does not replace Re-protect to synchronize live secondary VMs back to primary.

Question 890

After a genuine and committed Azure-to-Azure Site Recovery failover, billing services have run in West US for four days. East US is healthy again. The team has already completed Re-protect from West US back to East US, and reverse replication is Healthy with current data. The owner approves returning production to East US with a controlled cutover. Which operation should follow?

  1. Perform the supported planned failback/failover toward East US using synchronized reverse replication, validate the original-region service and redirect client traffic; then re-establish DR protection.
  2. Start Re-protect from West US again and assume it switches production clients to East US without a separate failover operation.
  3. Update public DNS to the old East US address immediately and skip bringing up or validating the recovered primary VMs.
  4. Run only a Test failover into an isolated East US test VNet and call the test-copy deployment the permanent production failback.

Explanation

Correct Answer

A:

Once reverse replication is healthy and authorized, a controlled planned failover/failback brings up the recovered original-region workload. Verify applications and client networking before traffic cutover, commit as supported and re-establish ongoing secondary-region protection.

Incorrect Answers

B:

Re-protect is already complete in the scenario; it prepares replication direction and does not by itself initiate the operational return to the original production region. The next step is a supported planned recovery cutover.

C:

DNS changes alone cannot create or validate the target-region machines or their application state. Sending users to an old endpoint before failback would risk downtime or stale data even when reverse replication is healthy.

D:

Test failover creates an isolated rehearsal workload and is cleaned up later. It doesn't commit the real primary-region return or restore the intended production replication direction.