Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Amazon SAA-C03 Exam - Topic 4 Question 69 Discussion

Actual exam question for Amazon's SAA-C03 exam
Question #: 69
Topic #: 4
[All SAA-C03 Questions]

A company runs an internet-facing web application on AWS and uses Amazon Route 53 with a public hosted zone.

The company wants to log DNS response codes to support future root cause analysis.

Which solution will meet these requirements?

Show Suggested Answer Hide Answer
Suggested Answer: A

To capture DNS query and response data, including response codes, Amazon Route 53 provides query logging, which is the most precise and AWS-supported solution for this requirement.

Option A enables Route 53 query logging, which records detailed information about DNS queries, such as the queried domain, record type, source IP, and DNS response code. These logs are delivered to Amazon CloudWatch Logs, where administrators can search, analyze, and retain them for forensic investigation and root cause analysis.

Option B is incorrect because AWS CloudTrail records API calls to AWS services, not DNS query traffic. Option C provides aggregated metrics (such as query counts and health checks) but does not include per-query response codes. Option D offers best-practice recommendations but does not collect or analyze DNS query data.

Therefore, A is the correct solution because Route 53 query logging provides the detailed, low-level DNS visibility required for troubleshooting and operational analysis.


Contribute your Thoughts:

0/2000 characters
Elouise
4 days ago
CloudWatch Logs is the way to go. Gotta love those detailed logs for debugging web app problems.
upvoted 0 times
...
Dion
10 days ago
Logging DNS response codes? Sounds like a real page-turner. I'll bring my coffee to the next root cause analysis meeting.
upvoted 0 times
...
Coletta
15 days ago
I'd recommend this solution. Logging DNS data in CloudWatch Logs is a no-brainer for this use case.
upvoted 0 times
...
Kimbery
20 days ago
Logging DNS response codes in CloudWatch Logs is a great way to troubleshoot issues with the web application.
upvoted 0 times
...
Cristy
25 days ago
Amazon CloudWatch Logs can be used to log DNS response codes from Route 53.
upvoted 0 times
...
Nu
1 month ago
I feel like we should also consider using CloudWatch for metrics, but I can't recall if it captures DNS response codes directly.
upvoted 0 times
...
Belen
1 month ago
There was a practice question about monitoring DNS queries; maybe we need to look into Route 53 query logging?
upvoted 0 times
...
Lauran
2 months ago
I remember something about using CloudTrail for logging, but I’m not clear if that applies to DNS response codes specifically.
upvoted 0 times
...
Huey
2 months ago
I think we might need to enable logging for Route 53, but I'm not entirely sure how to do that.
upvoted 0 times
...
Xochitl
2 months ago
Okay, I think I've got an idea. Since we're using Route 53, we could set up CloudWatch to monitor the DNS response codes and log them for future analysis. That seems like it would meet the requirements.
upvoted 0 times
...
Jovita
2 months ago
Alright, let's think this through. We need to log the DNS response codes, and we're using Route 53, so I'm thinking we might be able to use CloudWatch or another AWS logging service to capture that data.
upvoted 0 times
...
Fanny
3 months ago
Ah, I see. We're using Route 53 for DNS, so we'll need to find a way to capture the response codes from that service. I'm guessing there's an AWS service that can help with that.
upvoted 0 times
...
Ming
3 months ago
Okay, so we need to log DNS response codes for an internet-facing web app on AWS. I'm a bit unsure about the best way to approach this, but I'll try to think it through step-by-step.
upvoted 0 times
...
Pearline
3 months ago
Hmm, this seems like a straightforward question about logging DNS response codes. I think I'll start by considering the AWS services that could be used for this.
upvoted 0 times
...

Save Cancel