Google Professional Cloud Architect
Get started today
Ultimate access to all questions.
Mountkirk Games, a company that makes online, session-based, multiplayer games for mobile platforms, is building a new popular game. They plan to deploy the game's backend on Google Compute Engine for streaming metrics, intensive analytics, autoscaling, and NoSQL database integration. Developers and testers can access each other's environments and resources, but not staging or production resources. The staging environment needs access to some production services. What should you do to isolate development environments from staging and production?
Mountkirk Games, a company that makes online, session-based, multiplayer games for mobile platforms, is building a new popular game. They plan to deploy the game's backend on Google Compute Engine for streaming metrics, intensive analytics, autoscaling, and NoSQL database integration. Developers and testers can access each other's environments and resources, but not staging or production resources. The staging environment needs access to some production services. What should you do to isolate development environments from staging and production?
Explanation:
The correct answer is D: Create one project for development, a second for staging and a third for production. This approach adheres to the best practices for environment separation, ensuring isolation between environments. By creating separate projects for development, staging, and production, you can enforce access controls more effectively, thereby providing the necessary isolation. Furthermore, this method simplifies the management of permissions and resource allocation between different environments. Although option A could work, it is not considered a best practice as combining staging and production resources in the same project could lead to potential risks and conflicts.