Amazon Web Services Updated SAA-C03 Exam Questions and Answers by inayah

The correct answer isDbecause the application peak hours occur at thesame time each day, and the performance issue happens specifically at thestart of peak hours. This indicates that the company knows in advance when additional capacity will be needed. Ascheduled scaling policyis the most appropriate solution because it allows the Auto Scaling group to increase capacitybeforedemand rises, ensuring that instances are already launched and available when users begin accessing the application.

Dynamic scaling based on CPU or memory reacts onlyafterutilization increases. Because launching EC2 instances takes time, reactive scaling can lead to delays and degraded user experience at the beginning of peak periods. That directly matches the problem described in the question, where performance is slow at the start but normalizes later once capacity catches up. Scheduled scaling solves this by making capacity available proactively.

Option A is incorrect because an Application Load Balancer distributes traffic among existing instances but does not add capacity ahead of predictable demand. Option B is incorrect because Auto Scaling does not natively scale on memory utilization unless a custom metric is configured, and even then it would still be reactive rather than proactive. Option C is also incorrect because CPU-based dynamic scaling reacts after demand increases and therefore may not prevent the startup lag during peak traffic.

AWS design guidance recommends usingscheduled scalingwhen traffic patterns are predictable and occur at known times. This approach improves application responsiveness and user experience by making sure enough EC2 capacity is available before the workload surge begins.

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.

For latency-sensitive, globally distributed applications such as online gaming, minimizing network latency between users and application endpoints is critical. AWS Global Accelerator is designed specifically for this purpose. It uses the AWS global network and Anycast IP addresses to route user traffic to the closest healthy endpoint, reducing latency and improving performance for users worldwide.

Option C is the best solution because Global Accelerator directs traffic over the AWS backbone network instead of the public internet, which significantly reduces jitter and latency. It also provides built-in health checks and automatic failover, improving availability as the service expands globally. Importantly, Global Accelerator works seamlessly with existing Application Load Balancers, allowing the company to enhance performance without redesigning the application stack.

Option A (CloudFront) is optimized for caching static and cacheable content and is not ideal for real-time, stateful gaming traffic. Option B adds unnecessary API abstraction and additional latency. Option D introduces regional duplication and DNS-based routing, which is slower to react to network conditions and does not provide the same low-latency routing as Global Accelerator.

Therefore, C meets the requirement for global expansion with the least possible latency while maintaining a simple and highly performant architecture.

A. Mutual TLS:Provides secure communication but does not integrate with AWS credential exchange.

B. AWS Signature v4:Requires direct integration with AWS and is less secure for external systems.

C. Kerberos:Not natively supported for AWS API authentication.

D. IAM Roles Anywhere:Enables AWS API access using X.509 certificates without long-term credentials.