Can I initiate a “forced failover” for my MySQL Multi-AZ DB Instance deployment?
A.
Only in certain regions
B.
Only in VPC
C.
Yes
D.
No
Can I initiate a "forced failover" for my MySQL Multi-AZ DB Instance deployment?
Can I initiate a “forced failover” for my MySQL Multi-AZ DB Instance deployment?
My choice is C
If your DB instance is a Multi-AZ deployment, you can force a failover from one availability zone to another when you select the Reboot option. When you force a failover of your DB instance, Amazon RDS automatically switches to a standby replica in another Availability Zone and updates the DNS record for the DB instance to point to the standby DB instance. As a result, you will need to clean up and re-establish any existing connections to your DB instance. Reboot with failover is beneficial when you want to simulate a failure of a DB instance for testing, or restore operations to the original AZ after a failover occurs.
Source: http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_RebootInstance.html
Yes JM. The option is C. There is no restriction for the failover.
C
C
https://aws.amazon.com/rds/faqs/
Answer is C
https://aws.amazon.com/rds/faqs/
Q: Can I initiate a “forced failover” for my Multi-AZ DB Instance deployment?
Amazon RDS will automatically failover without user intervention under a variety of failure conditions. In addition, Amazon RDS provides an option to initiate a failover when rebooting your instance. You can access this feature via the AWS Management Console or when using the RebootDBInstance API call.
A
Do you know one thing. For all the questions you are the only guy commenting wrong answer. I think you do not have any other work. Mmmmmmmaaaaaad.
please be sure before posting anything as it will confuse the others
He/she must be from Azure. kakaka
C.
Yes
c