Oracle Database Migration to High-Performance EC2 Instances

Answer: A.

Option A is CORRECT because the I family EC2 instance type provides SSD-backed instance storage optimized for low latency, high random I/O performance, and high IOPS performance.

Option B is incorrect because the P family EC2 instance type is general-purpose GPU instances.Additionally, p3.2xlarge is an EBS backed instance type.

Option C is incorrect because c5.xlarge is EBS backed compute-intensive workload EC2 instance type.

Option D is incorrect because this is not an EC2 instance type, but an RDS DB instance class.Also, the T family is EBS backed general purpose instance type.

If an instance type supports both EBS backed and local NVMe-based SSD storage, a quick method to identify if it is an SSD-backed EC2 type is to check if the identifier has a “d” in its name (e.g.

“c5” vs “c5d”).

Reference:

https://aws.amazon.com/ec2/instance-types/ https://docs.aws.amazon.com/whitepapers/latest/oracle-database-aws-best-practices/amazon-ec2-instance-type.html

The appropriate EC2 instance type for this scenario would be the i3.xlarge.

Explanation:

• Local SSD-backed EC2 instances are optimized for high I/O performance and low-latency data access.
• The i3.xlarge instance type is a high-performance instance type that is optimized for I/O-intensive workloads. It provides up to 10 Gbps of dedicated bandwidth to local SSD storage, and it supports up to 3.3 million IOPS and 16 TB of NVMe SSD storage.
• Oracle databases require high random I/O performance and high IOPS, which the i3.xlarge instance type can deliver.
• The p3.2xlarge instance type is optimized for machine learning workloads and provides GPU acceleration. It is not the best fit for Oracle database workloads.
• The c5.2xlarge instance type is optimized for compute-intensive workloads and provides high network bandwidth. It is not optimized for I/O-intensive workloads.
• The db.t3.large instance type is a burstable instance type that is optimized for database workloads. However, it does not provide the high I/O performance and IOPS that the i3.xlarge instance type can deliver.

Therefore, the correct answer is A. i3.xlarge.