CloudEndure - AWS Disaster Recovery - Technical Training

When is the best time to conduct disaster recovery testing?

• immediately before a disaster

• immediately after a disaster

• no testing is necessary

• periodically

what is the easiest way to determine if your tested machines are healthy?

• All machines have undergone initial sync

• The green line to the left of machine name

• No machine undergoing lag

• All machines showing “Tested Recently”

What occurs after adding a machine to the CloudEndure user console?

• immediate data migration

• Failover

• Fallback

• Initial sync

Which of the following are NOT part of the three initial sync steps?

• Booting the replication server

• Creating firewall rules

• Continues data replication

• Create staging disk

What can you use to manage large workloads?

• Workload manager

• Launch plans

• Server migrator

• Recovery plans

What settings can you edit after performing the Prepare for Failback action?

• Network settings and Failover settings

• Blueprint settings and Launch Settings

• Failback settings and Back to Normal Settings

• Agent installation settings and Data Replication settings

How can you contact support?

• By contacting your Solution Architect

• Through the AWS Support Center

• By emailing CloudEndure directly at the support email address

• No support is offered for CloudEndure Disaster Recovery

What do you need to do to install the Cloudendure agent on a linux machine?

• Run only the executable command

• Run only the grep command

• Run the grep and executable command

• Run the download and executable commands

What action do you need to perform independently outside the CloudEndure console during a failover process?

• Redirect traffic from the primary site to the disaster recovery site

• Start the initial sync process through the API commands

• Establish connectivity by redirecting traffic to replication server

• Force the machine into lag by re-installing agents

Why are recovery points important?

• They allow you to quickly bypass replication lag issues

• They allow you to launch multiple target machines at once

• They allow you to recover your machines faster

• They allow you to pick the exact snapshots of your machines that you want to failover to