nerdexam
Amazon

SAP-C02 · Question #595

A company has developed a mobile game. The backend for the game runs on several virtual machines located in an on-premises data center. The business logic is exposed using a REST API with multiple…

The correct answer is C. Implement the REST API using Amazon API Gateway. Run the business logic in AWS Lambda. The company needs to migrate a mobile game backend to AWS, handling varying load, resolving session data latency, and maintaining the existing REST API model.

Submitted by deeparc· Mar 6, 2026Design for New Solutions

Question

A company has developed a mobile game. The backend for the game runs on several virtual machines located in an on-premises data center. The business logic is exposed using a REST API with multiple functions. Player session data is stored in central file storage. Backend services use different API keys for throttling and to distinguish between live and test traffic. The load on the game backend varies throughout the day. During peak hours, the server capacity is not sufficient. There are also latency issues when fetching player session data. Management has asked a solutions architect to present a cloud architecture that can handle the game's varying load and provide low-latency data access. The API model should not be changed. Which solution meets these requirements?

Options

  • AImplement the REST API using a Network Load Balancer (NLB). Run the business logic on an
  • BImplement the REST API using an Application Load Balancer (ALB). Run the business logic in
  • CImplement the REST API using Amazon API Gateway. Run the business logic in AWS Lambda.
  • DImplement the REST API using AWS AppSync. Run the business logic in AWS Lambda. Store

How the community answered

(62 responses)
  • A
    10% (6)
  • B
    18% (11)
  • C
    68% (42)
  • D
    5% (3)

Why each option

The company needs to migrate a mobile game backend to AWS, handling varying load, resolving session data latency, and maintaining the existing REST API model.

AImplement the REST API using a Network Load Balancer (NLB). Run the business logic on an

A Network Load Balancer (NLB) is not ideal for complex REST API management, and Amazon EFS is not designed for the low-latency, high-throughput session data access required.

BImplement the REST API using an Application Load Balancer (ALB). Run the business logic in

While Amazon DynamoDB is high-performance, Amazon ElastiCache for Redis typically offers even lower latency for temporary session data, and Amazon API Gateway is generally more feature-rich for managing external REST APIs compared to just an ALB.

CImplement the REST API using Amazon API Gateway. Run the business logic in AWS Lambda.Correct

Amazon API Gateway can expose the existing REST API model, AWS Lambda provides automatic scaling for varying load without server management, and Amazon ElastiCache for Redis offers sub-millisecond latency for session data, directly addressing all requirements.

DImplement the REST API using AWS AppSync. Run the business logic in AWS Lambda. Store

AWS AppSync is a GraphQL service, which would fundamentally change the existing "REST API model," directly contradicting a core requirement of the problem.

Concept tested: Serverless architecture, API management, low-latency data storage, scaling

Source: https://docs.aws.amazon.com/apigateway/latest/developerguide/welcome.html

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full SAP-C02 Practice