A company's production application runs online transaction processing (OLTP) transactions on an Amazon RDS MySQL DB instance The company is launching a new reporting tool that will access the same data The reporting tool must be highly available and not impact the performance of the production application.
How can this be achieved?

• A.Create hourly snapshots of the production RDS DB instance
• B.Create a Multi-AZ RDS Read Replica of the production RDS DB instance
• C.Create multiple RDS Read Replicas of the production RDS DB instance Place the Read Replicas in an Auto Scaling group
• D.Create a Single-AZ RDS Read Replica of the production RDS DB instance Create a second Single-AZ RDS Read Replica from the replica

Comment: *

Name: *

Email: *

Verification: *

A company has created an isolated backup of its environment in another Region The application is running in warm standby mode and is fronted by an Application Load Balancer (ALB) The current failover process is manual and requires updating a DNS alias record to point to the secondary ALB in another Region What should a solutions architect do to automate the failover process?

• A.Enable an ALB health check
• B.Create conditional forwarding rules on Amazon Route 53 pointing to an internal BIND DNS server
• C.Create a CNAME record on Amazon Route 53 pointing to the ALB endpoint.
• D.Enable an Amazon Route 53 health check

Comment: *

Name: *

Email: *

Verification: *

A company is processing data on a daily basis. The results of the operations are stored in an Amazon S3 bucket analyzed daily for one week and then must remain immediately accessible for occasional analysis What is the MOST cost-effective storage solution alternative to the current configuration?

• A.Configure a lifecycle policy to transition the objects to Amazon S3 Glacier after 30 days
• B.Configure a lifecycle policy to transition the objects to Amazon S3 Standard-Infrequent Access (S3 Standard-IA) after 30 days
• C.Configure a lifecycle policy to transition the objects to Amazon S3 One Zone-Infrequent Access (S3 One Zone-IA) after 30 days
• D.Configure a lifecycle policy to delete the objects after 30 days.

Comment: *

Name: *

Email: *

Verification: *

A solutions architect is tasked with transferring 750 TB of data from a network-attached file system located at a branch office to Amazon S3 Glacier The solution must avoid saturating the branch office's low-bandwidth internet connection
What is the MOST cost-effective solution1?

• A.Mount the network-attached file system to Amazon S3 and copy the files directly. Create a lifecycle policy to transition the S3 objects to Amazon S3 Glacier
• B.Create a site-to-site VPN tunnel to an Amazon S3 bucket and transfer the files directly Create a bucket policy to enforce a VPC endpoint
• C.Order 10 AWS Snowball appliances and select an S3 Glacier vault as the destination Create a bucket policy to enforce a VPC endpoint
• D.Order 10 AWS Snowball appliances and select an Amazon S3 bucket as the destination Create a lifecycle policy to transition the S3 objects to Amazon S3 Glacier

Comment: *

Name: *

Email: *

Verification: *

A company's application is running on Amazon EC2 instances within an Auto Scaling group behind an Elastic Load Balancer Based on the application's history, the company anticipates a spike in traffic during a holiday each year A solutions architect must design a strategy to ensure that the Auto Scaling group proactively increases capacity to minimize any performance impact on application users Which solution will meet these requirements?

• A.Create an Amazon CloudWatch alarm to scale up the EC2 instances when CPU utilization exceeds 90%
• B.Create a recurring scheduled action to scale up the Auto Scaling group before the expected period of peak demand
• C.Increase the minimum and maximum number of EC2 instances in the Auto Scaling group during the peak demand period
• D.Configure an Amazon Simple Notification Service (Amazon SNS) notification to send alerts when there are auto scaling EC2_INSTANCE_LAUNCH events

Correct Answer: B

Explanation
You can take advantage of the safety and reliability of geographic redundancy by spanning your Auto Scaling group across multiple Availability Zones within a Region and then attaching a load balancer to distribute incoming traffic across those zones. Incoming traffic is distributed equally across all Availability Zones enabled for your load balancer.
Note
An Auto Scaling group can contain Amazon EC2 instances from multiple Availability Zones within the same Region. However, an Auto Scaling group can't contain instances from multiple Regions.
When one Availability Zone becomes unhealthy or unavailable, Amazon EC2 Auto Scaling launches new instances in an unaffected zone. When the unhealthy Availability Zone returns to a healthy state, Amazon EC2 Auto Scaling automatically redistributes the application instances evenly across all of the zones for your Auto Scaling group. Amazon EC2 Auto Scaling does this by attempting to launch new instances in the Availability Zone with the fewest instances. If the attempt fails, however, Amazon EC2 Auto Scaling attempts to launch in other Availability Zones until it succeeds.
You can expand the availability of your scaled and load-balanced application by adding an Availability Zone to your Auto Scaling group and then enabling that zone for your load balancer. After you've enabled the new Availability Zone, the load balancer begins to route traffic equally among all the enabled zones.
High Availability (Multi-AZ) for Amazon RDS
Amazon RDS provides high availability and failover support for DB instances using Multi-AZ deployments.
Amazon RDS uses several different technologies to provide failover support. Multi-AZ deployments for MariaDB, MySQL, Oracle, and PostgreSQL DB instances use Amazon's failover technology. SQL Server DB instances use SQL Server Database Mirroring (DBM) or Always On Availability Groups (AGs).
In a Multi-AZ deployment, Amazon RDS automatically provisions and maintains a synchronous standby replica in a different Availability Zone. The primary DB instance is synchronously replicated across Availability Zones to a standby replica to provide data redundancy, eliminate I/O freezes, and minimize latency spikes during system backups. Running a DB instance with high availability can enhance availability during planned system maintenance, and help protect your databases against DB instance failure and Availability Zone disruption. For more information on Availability Zones, see Regions, Availability Zones, and Local Zones

https://docs.aws.amazon.com/autoscaling/ec2/userguide/as-add-availability-zone.html
https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Concepts.MultiAZ.html

Comment: *

Name: *

Email: *

Verification: *