Which solution will meet these requirements?
Create an Amazon Route 53 alias failover routing policy with values for AWS IoT Core data endpoints in both Regions Migrate data to Amazon Aurora global tables.
Create a domain configuration for AWS IoT Core in each Region. Create an Amazon Route 53 latency-based routing policy. Use AWS IoT Core data endpoints in both Regions as values. Migrate the data to Amazon MemoryDB for Redis and configure cross-Region replication.
Create a domain configuration for AWS IoT Core in each Region. Create an Amazon Route 53 health check that evaluates domain configuration health. Create a failover routing policy with values for the domain name from the AWS IoT Core domain configurations. Update the DynamoDB table to a global table.
Create an Amazon Route 53 latency-based routing policy. Use AWS IoT Core data endpoints in both Regions as values. Configure DynamoDB streams and cross-Region data replication.
Explanations:
While using Amazon Route 53 for failover routing can help direct traffic to the appropriate AWS IoT Core endpoint, migrating data to Amazon Aurora global tables is not suitable since the requirement is to use DynamoDB for storage. Additionally, Aurora global tables are not designed for time series data ingestion in the same way as DynamoDB.
This option suggests using Amazon MemoryDB for Redis with cross-Region replication, which is not relevant for time series data from sensors. Also, MemoryDB is not a suitable replacement for DynamoDB in this context, and the use of latency-based routing does not address the need for failover capabilities effectively.
This option correctly establishes a domain configuration for AWS IoT Core in each region, which is necessary for redundancy. By creating a failover routing policy based on health checks, it ensures that data ingestion can switch to the secondary region seamlessly. Additionally, updating DynamoDB to a global table allows for data to be stored across multiple regions, ensuring business continuity.
While using latency-based routing could direct data ingestion, the option does not provide a failover solution as required for business continuity. DynamoDB streams and cross-Region replication would not suffice for ensuring that data ingestion can continue in the event of a failure, especially since it does not mention any mechanism to handle failover effectively.
I evaluate that the answer is:
Create a domain configuration for AWS IoT Core in each Region. Create an Amazon Route 53 health check that evaluates domain configuration health. Create a failover routing policy with values for the domain name from the AWS IoT Core domain configurations. Update the DynamoDB table to a global table.