You have a business-critical two-tier web app currently deployed in two AZs in a single region, using Elastic Load Balancing and Auto Scaling. The app depends on synchronous replication (very low latency connectivity) at the database layer. The application needs to remain fully available even if one application AZ goes off-line, and Auto Scaling cannot launch new instances in the remaining Availability Zones. How can the current architecture be enhanced to ensure this?
A. Deploy in two regions using Weighted Round Robin (WRR), with Auto Scaling minimums set for 50 percent peak load per Region.
B. Deploy in two regions using Weighted Round Robin (WRR), with Auto Scaling minimums set for 100 percent peak load per region.
C. Deploy in three Availability Zones, with Auto Scaling minimum set to handle 50 percent peak load per zone.
D. Deploy in three Availability Zones, with Auto Scaling minimum set to handle 33 percent peak load per zone.
Answer: C. Deploy in three Availability Zones, with Auto Scaling minimum set to handle 50 percent peak load per zone.
You might also like to view...
An existing server has three 1 TB 7200 RPM SATA drives and five empty drive bays. The network manager orders three 2 TB 5400 RPM SAS drives. The technician installs them properly, but when attempting to provision the drives, a message displays "Type mismatch". Which of the following is the reason for this error message?
A. There is a firmware mismatch on the hard drives B. the drives must be from the same manufacturer C. The drive sizes must match D. The SATA and SAS drives cannot be mixed
Which of the following would not return string::npos when used on the string s which contains "rack":
a. s.find_first_not_of( "crackling" ); b. s.find_first_not_of( "packrat" ); c. s.rfind( "car" ); d. s.find( "ack" );