Valid Professional-Cloud-Architect Dumps shared by ExamDiscuss.com for Helping Passing Professional-Cloud-Architect Exam! ExamDiscuss.com now offer the newest Professional-Cloud-Architect exam dumps, the ExamDiscuss.com Professional-Cloud-Architect exam questions have been updated and answers have been corrected get the newest ExamDiscuss.com Professional-Cloud-Architect dumps with Test Engine here:
For this question, refer to the Mountkirk Games case study Mountkirk Games needs to create a repeatable and configurable mechanism for deploying isolated application environments. Developers and testers can access each other's environments and resources, but they cannot access staging or production resources. The staging environment needs access to some services from production. What should you do to isolate development environments from staging and production?
Correct Answer: D
Topic 1, Mountkirk Games Case Study Company Overview Mountkirk Games makes online, session-based. multiplayer games for the most popular mobile platforms. Company Background Mountkirk Games builds all of their games with some server-side integration and has historically used cloud providers to lease physical servers. A few of their games were more popular than expected, and they had problems scaling their application servers, MySQL databases, and analytics tools. Mountkirk's current model is to write game statistics to files and send them through an ETL tool that loads them into a centralized MySQL database for reporting. Solution Concept Mountkirk Games is building a new game, which they expect to be very popular. They plan to deploy the game's backend on Google Compute Engine so they can capture streaming metrics, run intensive analytics and take advantage of its autoscaling server environment and integrate with a managed NoSQL database. Technical Requirements Requirements for Game Backend Platform 1. Dynamically scale up or down based on game activity. 2. Connect to a managed NoSQL database service. 3. Run customized Linx distro. Requirements for Game Analytics Platform 1. Dynamically scale up or down based on game activity. 2. Process incoming data on the fly directly from the game servers. 3. Process data that arrives late because of slow mobile networks. 4. Allow SQL queries to access at least 10 TB of historical data. 5. Process files that are regularly uploaded by users' mobile devices. 6. Use only fully managed services CEO Statement Our last successful game did not scale well with our previous cloud provider, resuming in lower user adoption and affecting the game's reputation. Our investors want more key performance indicators (KPIs) to evaluate the speed and stability of the game, as well as other metrics that provide deeper insight into usage patterns so we can adapt the gams to target users. CTO Statement Our current technology stack cannot provide the scale we need, so we want to replace MySQL and move to an environment that provides autoscaling, low latency load balancing, and frees us up from managing physical servers. CFO Statement We are not capturing enough user demographic data usage metrics, and other KPIs. As a result, we do not engage the right users. We are not confident that our marketing is targeting the right users, and we are not selling enough premium Blast-Ups inside the games, which dramatically impacts our revenue.
Recent Comments (The most recent comments are at the top.)
if stage and production are in the same project, stage would be able to access all services of production, instead of only "some"
jay - Aug 19, 2018
I think D. You should never have staging and production in the save environment. Best practice is to always keep production separate. Staging can use resources in production via peering/vpn.
sridhar anchoori - Jul 06, 2018
I agree with the option A , Developers and testers must be able to access each other‘s environment, so should be part of the same project (unless Peering is configured between the 2 networks within different projects)
testtaker - Jun 16, 2018
D I disagree. You need only 3 projects to isolate dev/stage/prod upon 4 users.
Roger - Jun 12, 2018
Agree with Robert. Has to be projects to isolate properly. And want to point out "The staging environment needs access to some services from production."... so it has to be A, not D.
Robert - Jun 05, 2018
A - for fully isolated environment without accessing not only network related resources you need projects.
Recent Comments (The most recent comments are at the top.)
https://cloud.google.com/docs/enterprise/best-practices-for-enterprise-organizations#use_projects_to_fully_isolate_resources states that isolation happens through projects, so we are set on A and D. As the Q states "The staging environment needs access to some services from production." we have to have those together in one project, we have to choose A as the correct answer.
if stage and production are in the same project, stage would be able to access all services of production, instead of only "some"
I think D. You should never have staging and production in the save environment. Best practice is to always keep production separate. Staging can use resources in production via peering/vpn.
I agree with the option A , Developers and testers must be able to access each other‘s environment, so should be part of the same project (unless Peering is configured between the 2 networks within different projects)
D
I disagree. You need only 3 projects to isolate dev/stage/prod upon 4 users.
Agree with Robert. Has to be projects to isolate properly.
And want to point out "The staging environment needs access to some services from production."... so it has to be A, not D.
A - for fully isolated environment without accessing not only network related resources you need projects.