Question

Difficulty: Very hardIdentify design principles of the AWS Cloud

A gaming company is designing a global multiplayer game backend on AWS. The backend must handle highly volatile traffic spikes, process game logs for analytics, and update player profiles without causing game-play interruption if any downstream reporting service experiences an outage. The engineering team wants to strictly adhere to the AWS Cloud design principles of loose coupling and elasticity. Which of the following design choices should the company implement to meet these requirements? (Select TWO.)

  1. Implement an Amazon EventBridge event bus to route game events asynchronously to decoupled downstream services, such as analytics and leaderboards.Answer
  2. Deploy the game session manager using an Auto Scaling group of Amazon EC2 instances that scales dynamically based on real-time player connection metrics.Answer
  3. C
    Run the matchmaking, logging, and leaderboard logic as a single monolithic service on a single high-capacity Amazon EC2 instance to eliminate network communication overhead.
  4. D
    Configure the matchmaking service to write data directly and synchronously to the local storage of the analytics server before finalizing player matches.
  5. E
    Maintain a fixed, maximum-capacity database fleet to ensure the application can handle extreme peak loads without the need to dynamically provision resources.

Answer

Implementing an Amazon EventBridge event bus to route game events asynchronously to decoupled downstream services, and deploying the game session manager using an Auto Scaling group of Amazon EC2 instances that scales dynamically based on real-time player connection metrics.
The correct design choices are routing events asynchronously via Amazon EventBridge and scaling the session manager dynamically with an Auto Scaling group. Asynchronous routing decouples independent components so that a failure in one does not cascade. Dynamic scaling ensures elasticity by automatically provisioning resources to match real-time demand.

Step-by-Step Solution

1
Analyze the architectural requirements for loose coupling to prevent downstream outages from disrupting the main gameplay loop.
Determine that communication between the core game session manager and downstream services (analytics and leaderboards) must be asynchronous and event-driven.
Asynchronous routing prevents cascading failures and decouples the services, satisfying the loose coupling principle.
2
Analyze the architectural requirements for elasticity to handle volatile traffic spikes efficiently.
Determine that compute resource capacity must scale dynamically in response to real-time load, rather than using fixed pre-provisioned assets.
Dynamic scaling aligns resource consumption and costs with actual demand, satisfying the elasticity principle.
3
Evaluate the choices to identify correct implementations and eliminate anti-patterns.
Identify Amazon EventBridge asynchronous routing and Auto Scaling group deployment as correct answers. Monolithic consolidation, synchronous writes, and fixed-capacity fleets are flagged as violations of AWS design principles.
This isolates the options that demonstrate loose coupling and elasticity.

Key Concept

AWS Cloud Design Principles: Loose Coupling and Elasticity
Rate this question