-
Category: CSAP – Continuous Improvement for Existing Solutions – review mode 1
updated 2 weeks, 2 days ago
2 Members
·
2
Posts
-
Question:
An international foreign exchange company has a serverless forex trading application that was built using AWS SAM and is hosted on AWS Serverless Application Repository. They have millions of users worldwide who use their online portal 24/7 to trade currencies. However, they are receiving a lot of complaints that it takes a few minutes for their users to log in to their portal lately, including occasional HTTP 504 errors. As the Solutions Architect, you are tasked to optimize the system and to significantly reduce the time to log in to improve the customers’ satisfaction.
Which of the following should you implement in order to improve the performance of the application with minimal cost? (Select TWO.)
Deploy your application to multiple AWS regions to accommodate your users around the world. Set up a Route 53 record with latency routing policy to route incoming traffic to the region that provides the best latency to the user.
Set up multiple and geographically disperse VPCs to various AWS regions then create a transit VPC to connect all of your resources. Deploy the Lambda function in each region using AWS SAM, in order to handle the requests faster.
Increase the cache hit ratio of your CloudFront distribution by configuring your origin to add a Cache-Control max-age directive to your objects, and specify the longest practical value for max-age.
Use Lambda@Edge to allow your Lambda functions to customize content that CloudFront delivers and to execute the authentication process in AWS locations closer to the users.
Set up an origin failover by creating an origin group with two origins. Specify one as the primary origin and the other as the second origin which CloudFront automatically switches to when the primary origin returns specific HTTP status code failure responses.
I chose use lambda@edge and increase teh cache hit ratio with cloudfront.
It’s necessary improve performance and reducing costs.
Set up origin failover for me it’s related to Disaster Recover(Availability) and no performance.
-
Hello Marcos Daniel Santos,
Thank you for reaching out and for sharing your reasoning.In this scenario, Lambda@Edge is indeed a correct choice because it allows authentication logic to run at AWS edge locations closer to users, which helps reduce login latency without requiring additional regional deployments. However, increasing the CloudFront cache hit ratio does not address the root issue, as login and authentication requests are dynamic and user-specific, and therefore are typically not cacheable by CloudFront.
Regarding origin failover, while it is commonly associated with availability and disaster recovery, it also directly impacts perceived performance in this case. The HTTP 504 errors indicate that the origin is timing out, causing users to wait longer or retry their login attempts.
By configuring a CloudFront origin group with failover, CloudFront can automatically route requests to a healthy origin when the primary origin is unresponsive, reducing timeouts and improving the overall login experience. This approach improves both reliability and user-perceived performance with minimal additional cost, which aligns with the requirements of the question.
If you have any further questions or need additional clarification, feel free to reach out anytime.
Cheers,
Irene @ Tutorials Dojo
Log in to reply.