A network engineer lowered the TTL of several records in a public hosted zone for example.com to 60 seconds. The engineer wants to verify whether this change increased the number of DNS queries to Route 53 beyond expected levels by obtaining the query count for the example.com hosted zone. Which approach provides that information?

The correct approach is to use Amazon CloudWatch to access the AWS/Route 53 namespace and check the DNSQueries metric for the specific public hosted zone. Route 53 automatically publishes metrics for DNS queries to CloudWatch under the AWS/Route53 namespace, making this the most direct and efficient way to monitor query counts. The other options are incorrect because: Creating a new trail in AWS CloudTrail to include Route 53 data events is overly complex and not the primary method for monitoring query counts. CloudTrail focuses on API activity, not DNS query volume. Using the AWS/Route 53 Resolver namespace and checking the InboundQueryVolume metric is incorrect because this metric is for Route 53 Resolver endpoints, not for public hosted zones. Configuring logging to Amazon CloudWatch for the public hosted zone is a valid approach for detailed query analysis, but it requires additional setup and processing (metric filters) compared to the readily available DNSQueries metric in CloudWatch.