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

Amazon S3 is the natural long-term storage service for terabytes of images and videos because it scales massively and integrates directly withAmazon SageMaker AIfor machine learning workflows. UsingS3 Intelligent-Tieringhelps optimize storage cost automatically when access patterns vary over time. AWS recommends Intelligent-Tiering when access frequency changes or is unpredictable, because the service automatically moves objects between tiers while keeping them available. The alternatives introduce extra file system copies and additional cost or use a notebook instance as a storage endpoint, which is not a scalable long-term ingestion design. Therefore, S3 with direct SageMaker integration and Intelligent-Tiering is the most scalable and cost-conscious solution. (AWS Documentation)

============

AWS DataSync is the best fit because it is a managed service designed for repeated data movement between supported storage systems, includingAmazon S3andAmazon EFS. AWS documents that DataSync tasks can be configured to transferonly data that has changedby using theCHANGEDtransfer mode , which matches the overwrite-if-changed requirement. That removes the need to build custom synchronization code with Lambda or EC2. DataSync also has native support for S3 locations and EFS locations, so it directly covers both destinations in the question. Option A is therefore the lowest-overhead and most maintainable solution.

============

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.

For application access to AWS services from ECS tasks, the correct identity is the ECS task role. AWS separates the task execution role, which is mainly for pulling images and sending logs, from the task role, which is used by the application code running inside the container. Because the application itself needs to read from S3, the least-effort and most secure design is to grant the necessary S3 permissions directly to the task role. Using IAM users and access keys would introduce unnecessary credential management and reduce security. Therefore, assigning the required S3 permissions to the task role is the proper AWS best-practice solution.

============