You are working as an AWS consultant for a Bio-technology company that is working on Human genome data processing. They are using HDFS to process a large amount of data. They plan to migrate these systems to AWS EC2, where 50 x EC2 C5 instances will be used to compute data. This is a critical project where any failure will result in huge financial loss. The company is seeking your recommendation for the best solution to avoid correlated failures. Which ways can be used to limit the impact of any Hardware failure in this scenario? (Select TWO)

Answer options:

A.Use AWS CLI to deploy EC2 instance in the Partitioned Placement group.
B.Use AWS CLI to deploy EC2 instance in the Cluster Placement group.
C.Use AWS CLI to deploy EC2 instances in multiple Regions.
D.Use AWS Console to deploy EC2 instance in Partitioned Placement group.

Correct Answer – A and D
Launching EC2 in the Placement group is possible using both CLI and Console.
Firstly, a Rack server is a computer dedicated to use as a server and designed to be installed in a framework called a rack. Each rack has its own network and power source.
In the Partition Placement group, each logical partition within the placement group has its own set of racks. If a rack fails (hardware failure), it may affect multiple instances on that rack within that logical partition. So, if you have replication in other partitions, then your data will be safe. This will be good for Big data applications like HDFS, HBase, Cassandra, Kafka, or any other fault-tolerant system. This placement group strikes a balance between High Performance and High Availability.
A partition placement group can have partitions in multiple Availability Zones in the same Region. A partition placement group can have a maximum of seven partitions per Availability Zone. The number of instances that can be launched into a partition placement group is limited only by the limits of your account.
Option B is incorrect because all instances are placed within a rack in the Cluster Placement group. If the rack fails (hardware failure), all instances fail at the same time. This is ideal for High-Performance applications.
Option C is incorrect because the impact can be reduced using multiple "availability zones" instead of "regions".
For more information on Placement Groups, refer to the following URL-
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/placement-groups.html