Mountkirk Games makes online, session-based, multiplayer games for mobile platforms.
They have recently started expanding to other platforms after successfully migrating their on-premises environments to Google Cloud.
Their most recent endeavor is to create a retro-style first-person shooter (FPS) game that allows hundreds of simultaneous players to join a geo-specific digital arena from multiple platforms and locations.
A real-time digital banner will display a global leaderboard of all the top players across every active arena.
Solution concept - Mountkirk Games is building a new multiplayer game that they expect to be very popular.
They plan to deploy the game's backend on Google Kubernetes Engine so they can scale rapidly and use Google's global load balancer to route players to the closest regional game arenas.
In order to keep the global leader board in sync, they plan to use a multi-region Spanner cluster.
Existing technical environment - The existing environment was recently migrated to Google Cloud, and five games came across using lift-and-shift virtual machine migrations, with a few minor exceptions.
Each new game exists in an isolated Google Cloud project nested below a folder that maintains most of the permissions and network policies.
Legacy games with low traffic have been consolidated into a single project.
There are also separate environments for development and testing.
Business requirements -Support multiple gaming platforms.Support multiple regions.Support rapid iteration of game features.Minimize latency.Optimize for dynamic scaling.Use managed services and pooled resources.Minimize costs.
Technical requirements -Dynamically scale based on game activity.Publish scoring data on a near real-time global leaderboard.Store game activity logs in structured files for future analysis.Use GPU processing to render graphics server-side for multi-platform support.Support eventual migration of legacy games to this new platform.
Executive statement - Our last game was the first time we used Google Cloud, and it was a tremendous success.
We were able to analyze player behavior and game telemetry in ways that we never could before.
This success allowed us to bet on a full migration to the cloud and to start building all-new games using cloud-native design principles.
Click on the arrows to vote for the correct answer
A. B. C. D.C.
None of the provided answers directly address the business and technical requirements for the Mountkirk Games new multiplayer game.
Option A, "Configure an organizational policy which constrains where resources can be deployed", focuses on organizational control, which is not a requirement of the project.
Option B, "Configure IAM conditions to limit what resources can be configured", is too broad and does not address specific requirements.
Option C, "Configure the quotas for resources in the regions not being used to 0", is not a valid solution as the project requires multiple regions to be used.
Option D, "Configure a custom alert in Cloud Monitoring so you can disable resources as they are created in other regions", is not relevant to the requirements of the project. It is also not a recommended approach as it would not prevent the creation of resources in other regions but only alert when it happens.
To address the business and technical requirements of the project, Mountkirk Games should:
Use Google Kubernetes Engine (GKE) to deploy the game backend as it allows for rapid scaling, dynamic provisioning of resources, and efficient resource utilization.
Use Google's global load balancer to route players to the closest regional game arena, minimizing latency and improving player experience.
Use a multi-region Spanner cluster to keep the global leaderboard in sync.
Store game activity logs in structured files for future analysis, using Google Cloud Storage or a managed database service like BigQuery.
Use GPU processing to render graphics server-side for multi-platform support, using Google Cloud GPUs.
Use managed services and pooled resources, such as Google Cloud Functions or Google Cloud Run, to optimize resource utilization and minimize costs.
Eventually migrate legacy games to the new platform using a lift-and-shift approach or by gradually rewriting them using cloud-native design principles.
Therefore, none of the provided options is a valid solution for the business and technical requirements of Mountkirk Games new multiplayer game.