A company hosts several write-intensive applications. These applications use a MySQL database that runs on a single Amazon EC2 instance. The company asks a SysOps administrator to implement a highly available database solution that is ideal for multi-tenant workloads.
Which solution should the SysOps administrator implement to meet these requirements?
The best solution for a company that hosts write-intensive applications and requires a highly available database solution ideal for multi-tenant workloads is to migrate the database to an Amazon Aurora multi-master DB cluster. Aurora multi-master allows multiple instances to write to the database simultaneously, providing both high availability and write scalability. This setup is particularly beneficial for multi-tenant applications where different tenants might have varying write demands, ensuring continuous availability and performance under heavy loads.
https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-multi-master.html#aurora-multi-master-overview Multi-master clusters are best suited for segmented workloads, such as for multitenant applications.
question is deprecated, there is no multi-master mode in aurora mysql anymore
Ans: C Ref: https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-multi-master.html#aurora-multi-master-overview
multi-master = multi-tenant workload
multi-tenant workload Answer: C
C. Migrate the database to an Amazon Aurora multi-master DB cluster: Amazon Aurora multi-master enables multiple instances to write to the database simultaneously. This can provide high availability and fault tolerance, making it suitable for write-intensive workloads. It supports read and write operations across multiple instances, which is beneficial for multi-tenant workloads where different tenants may have different write patterns.
Question's keyword 'write-intense' . Answer's keyword 'multi-master' , then choose Answer C.
B not C because C. Migrate the database to an Amazon Aurora multi-master DB cluster. While this provides high availability and is designed for write-intensive workloads, it's generally more complex and may be more costly. It's suitable for specific use cases where you need write scaling across multiple masters, which might not be necessary here.