As a Solutions Architect for an e-commerce company, you are asked to improve the overall performance of an application that is behind Amazon API Gateway. You also need to protect the backend system and the application from traffic spikes.What is the optimal solution that you would recommend?Enable caching and WAF (Web Application Firewall)Enable caching and set throttling limits.Enable API Gateway to automatically scale and set throttling limitsEnable caching and scale API gateway services.
Question
As a Solutions Architect for an e-commerce company, you are asked to improve the overall performance of an application that is behind Amazon API Gateway. You also need to protect the backend system and the application from traffic spikes.What is the optimal solution that you would recommend?Enable caching and WAF (Web Application Firewall)Enable caching and set throttling limits.Enable API Gateway to automatically scale and set throttling limitsEnable caching and scale API gateway services.
Solution
The optimal solution I would recommend is to enable caching and set throttling limits.
Here's why:
-
Enable Caching: Caching can improve the performance of your application by storing responses from your backend system. When the same request is made, instead of forwarding the request to the backend, API Gateway can return the cached response, reducing the latency and load on your backend system.
-
Set Throttling Limits: Throttling limits can protect your backend system from traffic spikes. By setting a limit on the number of requests that can be made in a given time period, you can prevent your backend system from being overwhelmed by too many requests at once.
While enabling API Gateway to automatically scale and using a Web Application Firewall (WAF) can also be beneficial, they are not necessarily the optimal solution in this case. Auto-scaling can help handle increased traffic, but it doesn't protect against sudden traffic spikes the way throttling does. A WAF can protect against certain types of attacks, but it doesn't improve performance in the way that caching does.
Similar Questions
You are consulting for a company that promotes large musical events. They are going to announce a concert of a well known artist and expect a 10 fold increase in requests to their service. The service is based on API Gateway triggering a series of Lambda functions and an Amazon Relational Database Service (Amazon RDS) Database for persistent storage.What suggestions would you make for cost effective scaling?Set Lambda provisioned concurrency to a value that meets your cost targetEnable API Gateway caching to reduce backend invocationsScale the Amazon RDS instance up during the peak request periodUse API Keys to rate limit incoming user requests
Your company wants to expose their services to external developers as public APIs. They want to do this for monetization, visibility and engagement that results in growth. They also want to throttle requests to those APIs based on defined limits and quotas.What service would you suggest to meet the requirements?AWS AppSyncApplication Load BalancerAmazon API GatewayLambda Function URL
Which of the following statements are correct regarding Amazon API Gateway? (Select two)Question 62AnswerA.Amazon API Gateway does not yet support API result cachingB.API Gateway can be configured to send data directly to Amazon Kinesis Data StreamC.If an API response is served by the cached data, it is not considered an API call for billing purposesD.Amazon API Gateway creates RESTful APIs, Storage Gateway creates WebSocket APIsE. Amazon API Gateway can call an AWS Lambda function to create the front door of a serverless application
As a Solution Architect working for an online gaming company, you have been informed the player feedback system is slow to respond during peak periods. The feedback is reviewed weekly by the game developers. The current system submits the feedback to an Amazon API Gateway which invokes a Lambda function to first validate and then store the review in a Amazon DynamoDB table. This table has been configured with provisioned capacity.What suggestion would you offer to remove the players wait time?Enable API caching and payload compression in Amazon API GatewayIncrease the Lambda functions memory configuration so that it can process each client request faster.Change Amazon DynamoDB from provisioned capacity to on-demand allowing the table to scale up to handle any increases in demand.Insert an Amazon Simple Queue Service queue between the API Gateway and Lambda function. Use Lambda's native SQS poller to read off the queue. Refactor the Lambda function to handle the new event object.
Your company has a serverless application with Amazon API Gateway and AWS Lambda having both read, as well as, write APIs. The developers make frequent changes to the Lambda code and run load tests on the application after every change. The regular load testing has resulted in a spike in the cost.What are the best practices and cost savings options available on their Lambda compute usage? (Select TWO)Changing Lambda code does not necessarily require load testing. Unit and integration tests are sufficient.User reserve concurrency for the lambda functions and set the concurrency to a lower value.Use compute savings plan for lambda (discounted Savings Plans rates of up to 17% for a 1 or 3 year term, up to the commitment level.)Use Amazon EC2 instead of lambda.Use caching on Amazon API Gateway.
Upgrade your grade with Knowee
Get personalized homework help. Review tough concepts in more detail, or go deeper into your topic by exploring other relevant questions.