Valid NCM-MCI-6.10 Dumps shared by EduDump.com for Helping Passing NCM-MCI-6.10 Exam! EduDump.com now offer the newest NCM-MCI-6.10 exam dumps, the EduDump.com NCM-MCI-6.10 exam questions have been updated and answers have been corrected get the newest EduDump.com NCM-MCI-6.10 dumps with Test Engine here:
Use Prism Element for this question. The Application team has a 3 tier application (App Server, Web Server, and Database Server) that is mission critical and requires as close to 0 RPO and RTO as possible with their current license level. The organization has 2 clusters, with one cluster (Cluster 1) being production and the other cluster (Cluster 2) being remote/DR. Cluster 2 should be able to fail back to Cluster 1. The connectivity between the two sites is >5ms and replication traffic should not use more than 10Mbps of bandwidth. The Application team requests a plan that includes the ability to go back 2 days locally, and 2 days remotely. The team also requests that all 3 VMs be treated as a single group and backed up collectively in a snapshot. The three VMs are: * Web-Prod * App-Prod * DB-Prod Use Task3 as part of the name for any objects created for this task. Note: VMs do NOT need to be powered on. You will need to use the 172.30.0.x IP addresses when configuring DR.
Correct Answer:
See the Explanation below for detailed answer. Explanation: Here is the step-by-step solution to configure Disaster Recovery from the Cluster 1 Prism Element interface. 1. Add Cluster 2 as a Remote Site First, you must register Cluster 2 as a DR target for Cluster 1. * From the Cluster 1 Prism Element dashboard, navigate to Data Protection from the main dropdown menu. * Click the Remote Site tab. * Click the + Remote Site button and select Physical Cluster. * In the "Name" field, enter Cluster2_DR_Task3. * In the "Address" field, enter the 172.30.0.x Virtual IP address of Cluster 2. * Click Save. The clusters will exchange credentials and connect. 2. Throttle Replication Bandwidth Next, apply the 10 Mbps bandwidth limit for traffic going to Cluster 2. * On the same Remote Site tab, select the newly created Cluster2_DR_Task3. * Click the Update button. * In the dialog, set the Bandwidth Limit to 10 Mbps. * Click Save. 3. Create the Protection Domain A Protection Domain (PD) is the top-level object that will manage the VMs and replication schedules. * In the Data Protection dashboard, click the Table tab. * Click the + Protection Domain button and select Async DR. * For the Name, enter App_PD_Task3. * Click Create. 4. Protect VMs in a Consistency Group Now you will add the three application VMs to the new Protection Domain as a single Consistency Group (CG). * You will be taken to the dashboard for the new App_PD_Task3. In the Entities panel, click the Protect Entities button. * In the "Protect Entities" dialog, search for and select the three VMs: * Web-Prod * App-Prod * DB-Prod * Click Next. * Select Create new consistency group and name it App_CG_Task3. * Click Protect. 5. Create the Replication Schedule Finally, configure the schedule to meet the RPO and retention requirements. * In the App_PD_Task3 dashboard, click the Schedules tab. * Click the + New Schedule button. * Remote Site: Select Cluster2_DR_Task3. * RPO (Repeat every): Select NearSync. Set the RPO to 1 minute. * Note: This is the lowest possible RPO for an Async (>5ms latency) connection, fulfilling the "as close to 0" requirement. * Local Retention: Set to 2 Days. * Remote Retention: Set to 2 Days. * Ensure the "Store snapshots for 2-way replication" checkbox is enabled to allow failback from Cluster 2. * Click Create Schedule.
