Answer-first summary for fast verification
Answer: Use Amazon CloudWatch to monitor the DMS task. Examine the CDCLatencySource metric to identify delays in the CDC from the source database.
Option D is CORRECT because using Amazon CloudWatch to monitor the DMS task and examining the CDCLatencySource metric will provide information about delays in the change data capture (CDC) process from the PostgreSQL source database. This metric specifically measures the time it takes for changes to be captured from the source database, which will help confirm if the PostgreSQL database is causing the high latency.
Author: Ritesh Yadav
Ultimate access to all questions.
Question 27/60
A company needs to send customer call data from its on-premises PostgreSQL database to AWS to generate near real-time insights. The solution must capture and load updates from operational data stores that run in the PostgreSQL database. The data changes continuously.
A data engineer configures an AWS Database Migration Service (AWS DMS) ongoing replication task. The task reads changes in near real time from the PostgreSQL source database transaction logs for each table. The task then sends the data to an Amazon Redshift cluster for processing.
The data engineer discovers latency issues during the change data capture (CDC) of the task. The data engineer thinks that the PostgreSQL source database is causing the high latency.
Which solution will confirm that the PostgreSQL database is the source of the high latency?
A
Use Amazon CloudWatch to monitor the DMS task. Examine the CDCIncomingChanges metric to identify delays in the CDC from the source database.
B
Verify that logical replication of the source database is configured in the postgresql.conf configuration file.
C
Enable Amazon CloudWatch Logs for the DMS endpoint of the source database. Check for error messages.
D
Use Amazon CloudWatch to monitor the DMS task. Examine the CDCLatencySource metric to identify delays in the CDC from the source database.
No comments yet.