You are designing disaster recovery for a two-tier payroll application running on on-premises VMware hosts. You plan to use Azure Site Recovery (ASR) to replicate the database VM and the application VM to Azure. Requirements: you must be able to conduct a non-disruptive DR test in Azure without impacting on-premises workloads, and you must ensure the database VM starts before the application VM during failover. Which two actions should you implement in the Recovery Services vault? Choose two.

To ensure the database VM starts before the application VM during failover, you must create a recovery plan. Recovery plans allow you to group VMs and define the order in which they start, including adding pre- and post-failover actions. This directly addresses the requirement for ordered VM startup. To conduct a non-disruptive DR test without impacting on-premises workloads, you should run a Test Failover to an isolated Azure virtual network. Test Failover creates copies of the replicated VMs in Azure without affecting the ongoing replication or the on-premises production environment. Configuring network mapping for test failover ensures these test VMs connect to the correct isolated network. Using Planned Failover would involve shutting down the primary VMs, which violates the non-disruptive testing requirement. Enabling multi-VM consistency helps with data integrity but doesn't address the testing or startup order requirements. Triggering an Unplanned Failover is for actual disaster scenarios and would impact production if not carefully managed, and it doesn't offer the isolated testing environment needed.