Exam SAP-C02 All QuestionsBrowse all questions from this exam
Go to Exam
Question 81

A company is building an electronic document management system in which users upload their documents. The application stack is entirely serverless and runs on AWS in the eu-central-1 Region. The system includes a web application that uses an Amazon CloudFront distribution for delivery with Amazon S3 as the origin. The web application communicates with Amazon API Gateway Regional endpoints. The API Gateway APIs call AWS Lambda functions that store metadata in an Amazon Aurora Serverless database and put the documents into an S3 bucket.

The company is growing steadily and has completed a proof of concept with its largest customer. The company must improve latency outside of Europe.

Which combination of actions will meet these requirements? (Choose two.)

    Correct Answer: A, C

    To improve latency for users outside of Europe, two main actions can be taken. First, enabling S3 Transfer Acceleration on the S3 bucket and using Transfer Acceleration signed URLs will speed up the upload of documents by utilizing Amazon CloudFront's globally distributed edge locations. This helps reduce latency by routing data through the AWS edge network, closer to users, before reaching the S3 bucket. Second, changing the API Gateway Regional endpoints to edge-optimized endpoints will improve latency by routing API requests to the nearest CloudFront Point of Presence, thereby reducing the time it takes for users' requests to reach the server and receive a response. These two measures directly address latency issues by leveraging AWS’s global infrastructure to bring data transfer and API processing closer to users, leading to notable performance improvements.

Discussion
masetromainOptions: AC

A and C are correct answers. A. Enable S3 Transfer Acceleration on the S3 bucket and ensure that the web application uses the Transfer Acceleration signed URLs will accelerate the uploads of documents to S3 bucket, this will help to reduce the latency for users outside of Europe. C. Change the API Gateway Regional endpoints to edge-optimized endpoints will help the company to improve the latency by caching the responses of the API Gateway closer to the users.

masetromain

B. Creating an accelerator in AWS Global Accelerator and attaching it to the CloudFront distribution will not help in this scenario as it only helps to route the traffic to the optimal endpoint based on the location of the user. D. Provisioning the entire stack in two other locations that are spread across the world and using global databases on the Aurora Serverless cluster will help to reduce the latency but it would be more complex to implement and manage. E. Adding an Amazon RDS proxy between the Lambda functions and the Aurora Serverless database will not help in this scenario because it is only used to improve connection management and load balancing for Amazon RDS databases, but not for Aurora Serverless databases.

masetromain

https://www.examtopics.com/discussions/amazon/view/69470-exam-aws-certified-solutions-architect-professional-topic-1/

Japanese1

Complexity is not evidence against option D. Furthermore, option D is correct because the question statement also suggests that costs can be incurred. On the other hand, A is not a method to eliminate geographical factors.

bcx

A is wrong because the users of S3 are the lambda functions, not the end user. "The API Gateway APIs call AWS Lambda functions that store metadata in an Amazon Aurora Serverless database and put the documents into an S3 bucket."

Sab

Users of S3 are not lambda, lambda is used only for writing to serverless database. Also, Aurora serverless global database only writes in one cluster and the other region cluster are used only for reads. So no matter from which location you upload, the metadata will be written to cluster in Central Europe . If it was Global DynnamoDB table then it could have helped to reduce latency.

ninomfr64

"web app uses CloudFront distribution for delivery with Amazon S3 as the origin" and "Lambda functions that store metadata in an Amazon Aurora Serverless database and put the documents into an S3 bucket" these 2 sentences let me think that users are not uploading via CluodFront into the S3 bucket at its origin, rather docs are uploaded from the Lambda

e4bc18e

A is wrong because why would you enable transfer acceleration when transfer acceleration uses the cloudfront distribution system. it makes no sense

chico2023Options: AC

Answer: A and C (over C and D which I also am inclined to). For me, the lack of a really clear direction like "What solution will provide the best latency improvement in a cost effective way", for example, opens the debate into two possible ways. I personally like the idea presented in C and D, but if I want to improve latency for users outside Europe, initially I would try to perform A and C. Simply because I am not sure which regions I am going to use. I know that it says "Provision the entire stack in two other locations that are spread across the world." But where, exactly? One in Sao Paulo and the other in Cape Town? How much will it improve for users in Auckland, if that's the case? There this great blog explaining S3 Transfer Acceleration with signed URLs and how they can improve latency. Have a look: https://www.blendedsoftware.com/articles/how-to-accelerate-file-uploads-with-aws-s-3/

failexamonlyOptions: AC

Aurora serverless does not support global database. search DB instance class requirements in https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-global-database-getting-started.html

bacharbhouri

it does in V2. [] https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-serverless-v2.html#aurora-serverless-v2.advantages : Using Aurora Serverless v2 - Advantages of Aurora Serverless v2

JMAN1Options: CD

Tricky Tricky. A. Enable S3 Transfer Acceleration on the S3 bucket. Ensure that the web application uses the Transfer Acceleration signed URLs. -> Wrong. No such thing like TA signed URLs. B. Create an accelerator in AWS Global Accelerator. Attach the accelerator to the CloudFront distribution. -> Wrong GA does not support CF. C. Change the API Gateway Regional endpoints to edge-optimized endpoints. D. Provision the entire stack in two other locations that are spread across the world. Use global databases on the Aurora Serverless cluster. E. Add an Amazon RDS proxy between the Lambda functions and the Aurora Serverless database. -> Wrong. It is not related with latency.

jpa8300

Yes there is, https://stackoverflow.com/questions/37437782/aws-transfer-acceleration-with-pre-signed-urls-using-javascript-sdk

JMAN1

Sorry. I was wrong. Answer is A C. serverless does not support global database and RDS proxy.

JMAN1

https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-serverless.html#aurora-serverless.limitations

bacharbhouri

it does in V2. [] https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-serverless-v2.html#aurora-serverless-v2.advantages : Using Aurora Serverless v2 - Advantages of Aurora Serverless v2

red_pandaOptions: AC

A and C for me are the correct answers. D is not so usefull as we are recreating the entire stack and increase a lot the costs. As first approach, A and C are the most appropriate

DgixOptions: AC

By elimination: B is pointless, as CF already does geo proximity. D is impossible as global DBs aren't supported by Aurora Serverless. E doesn't really help. Remaining: A and C, which are sensible and will do the trick.

gofavad926Options: AC

AC, s3 transfer acceleration + edge-optimised api gateway

ninomfr64Options: CD

This is tricky. Here is my take having in mind that the question is "The company must improve latency outside of Europe",. A = Transfer Acceleration improves upload/downlad time, but we have already CloudFront that can also be used to speedup upload. This will not further improve. Also I don't know how to combine TA with CF B = This will not help and also I don't know how to combine GA with CF C = correct D = correct E = RDS Proxy do not improve latency

djeong95

Looks like D is wrong because you don't use global databases on the Aurora Serverless cluster. That is just not a feature given by Aurora Serverless (even v2). However, it does support using Aurora Serverless in global databases. "The secondary clusters" in the link below is a reference to Aurora Global Database. https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-serverless-v2.how-it-works.html#aurora-serverless.ha:~:text=You%20can%20use%20Aurora%20Serverless%20v2%20capacity%20in%20the%20secondary%20clusters%20so%20they%27re%20ready%20to%20take%20over%20during%20disaster%20recovery.

djeong95

In addition, we are more likely to get latency from Lambda functions loading documents into S3 from API Gateway calls than we are from Lambda functions loading metadata into Aurora Serverless DB. https://aws.amazon.com/blogs/compute/uploading-large-objects-to-amazon-s3-using-multipart-upload-and-transfer-acceleration/

[Removed]Options: AC

A and C makes sense. A is clear as what masetromain has explained. C, An edge-optimized API endpoint typically routes requests to the nearest CloudFront Point of Presence (POP). It certaintly improve the latency of traffic originating from Europe as the traffic will now be directed to the nearest POP instead of the origin API Gateway.

uC6rW1aBOptions: AC

On a global scale, and particularly for users outside of Europe, the API Gateway and S3 access operations are the most likely components to introduce significant latency. For the API Gateway, changing from regional endpoints to edge-optimized endpoints would bring API calls closer to global users. For S3, enabling Transfer Acceleration would speed up the uploading and downloading of files. Therefore, based on the provided system overview, these two components are the most likely areas needing optimization to reduce latency.

GabehcoudOptions: CD

even though option D is complex, it would decrease the latency outside eu region.

gfhbox0083

A, C for sure. B is wrong; AWS Global Accelerator and Amazon CloudFront are separate services that use the AWS global network and its edge locations around the world. CloudFront improves performance for both cacheable content (such as images and videos) and dynamic content (such as API acceleration and dynamic site delivery). Global Accelerator improves performance for a wide range of applications over TCP or UDP by proxying packets at the edge to applications running in one or more AWS Regions. Global Accelerator is a good fit for non-HTTP use cases, such as gaming (UDP), IoT (MQTT), or Voice over IP, as well as for HTTP use cases that specifically require static IP addresses or deterministic, fast regional failover. Both services integrate with AWS Shield for DDoS protection.

severlightOptions: AC

see Sab answer

wookchan

"The company must improve latency outside of Europe." Then in where are you going to provision an additional stack? It only says "outside of Europe." USA? Asia? Where? You have to consider an overall latency. I'll go for AC

AMohanty

AD Issue is minimize latency for "users uploading documents" Its NOT an issue with the latency of website being delivered to the users. Global Accelerator - Is used to decrease latency in having the user request delivered using AWS backbone network to the point of Origin But it doesnt accelerate delivery of uploaded files into S3 .... so A is a better option. RDS Proxy is used to decrease the time in establishing the DB connectivity ... It keeps few DB connections on warm-by condition. Option D doesn't help in reducing cross-Region latency API Gateway edge point will reduce the latency in serving the website closer to ur location. But here question is about uploading document. Aurora Serverless Global - can be used for uploading meta-data reducing latency time.

nharaz

S3 Transfer Acceleration primarily improves upload speeds to an S3 bucket and doesn't significantly affect the latency of the web application itself.

CuteRunRunOptions: CD

I prefer CD. A is not right. You already get a cloudfront, what is the acceleration used for.

longns

in S3 hosted web application you upload directly to s3 using s3 url

ninomfr64

You can (and should) avoid enabling S3 web site hosting working with CloudFront. You can simply configure the S3 as the distribution origin