Which set of actions will meet these requirements?
Take a snapshot of the instance in the us-west-2 Region. Create a new instance from the snapshot in the ap-southeast-1 Region. Reconfigure the ap- southeast-1 front-end dashboard to access this instance.
Create an RDS read replica in the ap-southeast-1 Region from the primary RDS DB instance in the us-west-2 Region. Reconfigure the ap-southeast-1 front- end dashboard to access this instance.
Create a new RDS instance in the ap-southeast-1 Region. Use AWS DMS and change data capture (CDC) to update the new instance in the ap-southeast-1 Region. Reconfigure the ap-southeast-1 front-end dashboard to access this instance.
Create an RDS read replica in the us-west-2 Region where the primary instance resides. Create a read replica in the ap-southeast-1 Region from the read replica located on the us-west-2 Region. Reconfigure the ap-southeast-1 front-end dashboard to access this instance.
Explanations:
Taking a snapshot and creating a new instance from it does not provide real-time data synchronization between the us-west-2 Region and ap-southeast-1 Region, leading to stale data in the dashboard.
Creating an RDS read replica in the ap-southeast-1 Region allows the front end in Singapore to access the replica, providing a low-latency connection to the database. The replica will remain in sync with the primary database in us-west-2.
Using AWS DMS with CDC to replicate data to a new RDS instance is a complex approach that is typically used for migrations or large-scale database updates, not for real-time application performance.
Creating a read replica in the us-west-2 Region and then creating a read replica in ap-southeast-1 from that replica adds unnecessary complexity and does not solve the issue of performance by providing a direct low-latency replica in Singapore.