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.
Question
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.
Solution
The best solution to remove the player's wait time would be to insert an Amazon Simple Queue Service (SQS) queue between the API Gateway and Lambda function. This is because the current bottleneck seems to be the Lambda function processing and validating the feedback before storing it in the DynamoDB table.
By using an SQS queue, the feedback can be immediately returned to the player after it is submitted, and the Lambda function can then process the feedback from the SQS queue at its own pace. This would remove the need for the player to wait for the feedback to be processed.
Additionally, refactoring the Lambda function to handle the new event object from the SQS queue would allow for more efficient processing of the feedback.
While the other solutions might also improve performance, they do not address the fundamental issue of the player having to wait for the feedback to be processed. For example, enabling API caching and payload compression in Amazon API Gateway might speed up the API, but it would not reduce the processing time of the Lambda function. Similarly, increasing the Lambda function's memory configuration might make it faster, but it would not eliminate the wait time for the player.
Finally, changing Amazon DynamoDB from provisioned capacity to on-demand might allow the table to scale up to handle increases in demand, but it would not reduce the time it takes for the Lambda function to process and validate the feedback.
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
weather-tracking application is built using Amazon DynamoDB. The performance of the application has been consistently good. But lately, the team has realized that during holidays and travel seasons, the load on the application is high and the read requests consume most of the database resources, thereby drastically increasing the overall application latency. Which feature/service will help resolve this issue?Question 63Answera.Amazon CloudFrontb.Amazon DynamoDB Acceleratorc.Amazon DynamoDB Regulatord.Amazon ElastiCache
A Company is designing a high availability solution for a customer. This customer's requirements are that their application needs to be able to handle an unexpected amount of load and allow site visitors to read data from a DynamoDB table, which contains the results of an online polling system. Given this information, what would be the best and most cost-saving method for architecting and developing this application?Select one:a. Use the JavaScript SDK and build a static HTML page, hosted inside of an Amazon S3bucket; use CloudFront and Route 53 to serve the website, which uses JavaScript client-sidelanguage to communicate with DynamoDBb. Create a CloudFront distribution that serves the HTML web page, but send the visitors to an Auto Scaling ELB application pointing to EC2 instances c. Create a Lambda script, which pulls the most recent DynamoDB polling results and creates a custom HTML page, inside of Amazon S3 and use CloudFront and Route 53 to servethe static websited. Deploy an Auto Scaling application with Elastic Load Balancer pointing to EC2 instances that use a server-side SDK to communicate with the DynamoDB table
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.
An organization developed serverless applications by using an event driven architecture (Amazon API Gateway, AWS Lambda). When launched in production, customers complained about slow response during the morning peak hours. Developers pointed out it is related to AWS Lambda cold starts. On average, the development team estimated there will be 100 concurrent users.How do you mitigate the AWS Lambda cold starts?Prevent AWS Lambda cold starts by increasing the service limits.Prevent AWS Lambda cold start with the Amazon CloudWatch Metrics to schedule events on morning hours.Prevent AWS Lambda cold starts with Lambda provisioned concurrency.Prevent AWS Lambda cold starts with Lambda reserved concurrency.
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.