SAA-C03 Exam Dumps - AWS Certified Solutions Architect - Associate (SAA-C03)

The correct answer isAbecause the legacy mainframe requires asynchronous RESTful APIand the new service takes approximately3 minutesto complete each request. Among the choices,Amazon API Gateway REST APIis the appropriate option for exposing a synchronous REST endpoint to the mainframe. API Gateway REST APIs support longer integration timeouts than HTTP APIs, which makes them more suitable for workloads that take an extended time to process. The REST API can invoke an AWS Lambda function to execute the stock price calculation and return the result synchronously.

Option B is incorrect becauseAPI Gateway HTTP APIshave a shorter integration timeout and are not the best fit for a request that takes around 3 minutes. Option C is incorrect becauseWebSocket APIsare not RESTful and do not meet the requirement for synchronous REST-based integration with the mainframe. Option D is incorrect becauseLambda function URLsdo not provide the same API management features and are not the best choice for a long-running synchronous enterprise integration requirement of this kind.

AWS design guidance favors API Gateway when exposing managed APIs to external consumers. In this case, theREST APIoption best matches the requirement for synchronous RESTful access while supporting the longer processing duration. It also provides a managed front door for authentication, throttling, and operational control if the company needs those features later.

One note of honesty: some exam versions treat the REST API timeout detail as the deciding factor here. That is the key reasonREST APIis preferred overHTTP APIfor this question.

To upload photos to an S3 bucket using Amazon CloudFront with a custom domain name, the following components are required:

ACM in us-east-1 (Option A): When using CloudFront with HTTPS, the SSL/TLS certificate must be created in theus-east-1Region. AWS Certificate Manager (ACM) handles the provisioning, management, and renewal of public certificates, making this a cost-effective and low-maintenance solution.

S3 Transfer Acceleration (Option C): Transfer Acceleration allows faster uploads to S3 from CloudFront by routing traffic through AWS’s edge locations. This significantly speeds up the data upload process, especially for users that are geographically distant from the S3 bucket ' s region.

Option B (ACM in eu-west-1): CloudFront only supports certificates created in us-east-1.

Option D and E (OAC and website endpoint): These are not ideal for handling secure uploads or efficient data transfers in this case.

AWS References:

Using ACM with CloudFront

Amazon S3 Transfer Acceleration

A. ElastiCache:Provides in-memory caching, not suitable for persistent, scalable databases.

B. DynamoDB Streams + Lambda:Manages replication manually, increasing latency and operational complexity.

C. Aurora Global Database:Provides high availability but does not support active-active configuration.

D. DynamoDB Global Tables:Provides active-active configuration and sub-second RPO.

AWS WAF Bot Control is the best fit because the problem is abusive automated traffic submitting unnecessary requests and consuming compute resources. AWS documents that the Bot Control managed rule group is specifically designed to identify and manage bot traffic, including high-confidence bot signatures and common bot categories. This is more targeted than maintaining custom IP blocks and more directly aligned to the behavior described than general IP reputation controls. AWS Shield focuses on DDoS protection, not detailed application-layer bot categorization. Therefore, associating a WAF web ACL with the ALB and enabling Bot Control is the most appropriate solution.

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

AWS Transit Gateway simplifies network connectivity by acting as a hub that can connect VPCs and on-premises networks through VPN or Direct Connect. It provides scalability and reduces administrative overhead by eliminating the need to manage complex peering relationships as the number of accounts and VPCs grows.

The requirement is for astructured relational databasewith backups and scalable managed operations. Amazon RDS is the natural fit because it provides a managed relational database platform, and AWS documents that General Purpose SSD is recommended for new storage needs. AWS also documents that automated backups are enabled through the backup retention period parameter. Compared with self-managed EC2 databases, RDS reduces operational burden significantly. Aurora Serverless can be attractive, but for a general-purpose new application, standard RDS with GP SSD and automated backups is the more straightforward cost-conscious choice among the listed answers. Therefore, RDS with GP SSD storage and automated backups is the best match.

The least-privilege design is to create an IAM policy that explicitly lists the full ARNs of only the S3 buckets the application must access, then attach that policy to the ECS task role. The ECS task role provides AWS permissions directly to the application container, which is the correct identity boundary for ECS workloads. Attaching permissions to the instance role is broader because all tasks on the container instance could potentially inherit access through the EC2 host role. A wildcard ARN is not least privilege because it can unintentionally match extra buckets. Tag-based access can be useful in some ABAC designs, but the requirement is a specific group of buckets in one account and Region; explicit ARNs provide clearer least-privilege access.

Amazon SQS supports Interface VPC endpoints (AWS PrivateLink), enabling private connectivity from your VPC to SQS without using public IPs, traversing the public Internet, or requiring NAT/IGW. You can restrict access by attaching a queue resource policy that allows only the specific VPC endpoint and denies all other principals/paths, enforcing that all traffic stays on the AWS network. SSE-SQS (B) encrypts data at rest but does not influence network pathing. STS temporary credentials (C) handle authentication/authorization, not routing. VPC Flow Logs (D) are monitoring/visibility and do not prevent public egress. Creating an SQS VPC endpoint and tightening the queue policy satisfies the requirement of no public IP usage while maintaining secure, private access from serverless components in VPC subnets.