Exam Professional Cloud Architect All Questions

View all questions & answers for the Professional Cloud Architect exam

Exam Professional Cloud Architect topic 5 question 5 discussion

Actual exam question from Google's Professional Cloud Architect

Question #: 5
Topic #: 5

[All Professional Cloud Architect Questions]

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?

A. Create a project for development and test and another for staging and production
B. Create a network for development and test and another for staging and production
C. Create one subnetwork for development and another for staging and production
D. Create one project for development, a second for staging and a third for production

Show Suggested Answer

Suggested Answer: D 🗳️

by shandy at Nov. 27, 2019, 2:13 a.m.

Comments

Submit Cancel

shandy

Highly Voted 5 years, 8 months ago

Correct Answer is D. https://cloud.google.com/appengine/docs/standard/php/creating-separate-dev-environments

upvoted 52 times

nitinz

4 years, 5 months ago

it is A

upvoted 6 times

...

tartar

4 years, 11 months ago

D is ok

upvoted 9 times

tartar

4 years, 11 months ago

not D, A

upvoted 15 times

ACE_ASPIRE

3 years, 10 months ago

hey man...it should be D...

upvoted 2 times

KOERA99

3 years, 9 months ago

It's D!!!!

upvoted 2 times

...

Wonka

3 years, 6 months ago

its standard but look at requirement given here

upvoted 1 times

...

euclid

Highly Voted 5 years, 7 months ago

Correct is A

upvoted 48 times

walkwolf3

3 years, 6 months ago

D In the requirement, the staging environment needs access to production, not the other way around. Answer A could allow staging and production to access each other. In answer D, staging and production are in different project, you can limit the access from either side. So D is correct.

upvoted 22 times

Ishu_awsguy

2 years, 10 months ago

Best approach is D. A will also work based on question requirement

upvoted 4 times

...

hogtrough

3 years, 6 months ago

End goal is to separate dev from staging/production. Putting staging/production in same project fits the requirements. Further effort would be required to change access between Staging and Production projects that is out of scope of question. It is not best practice, but fits requirements of question.

upvoted 8 times

Wonka

3 years, 6 months ago

yes and there is no mention of test environment in option D.

upvoted 5 times

...

TiagoM

4 years, 3 months ago

"The staging environment needs access to some services from production" Its not the best practice, but A has less effort

upvoted 8 times

...

army234

4 years, 4 months ago

Incorrect. Not a best practice to have Staging and Prod resources in the same project. D is correct

upvoted 9 times

Wonka

3 years, 6 months ago

by standard it is absolutely incorrect but here it is requirement. will you still separate it out?

upvoted 2 times

...

AWS56

5 years, 6 months ago

Agree with A

upvoted 5 times

...

michelgrolet

Most Recent 5 months, 4 weeks ago

Selected Answer: D

Separation of concerns ! Correct answer is D.

upvoted 2 times

...

Rajarshi_Bhattacharyya

6 months ago

Selected Answer: A

Correct answer should be A

upvoted 2 times

...

task_7

7 months, 2 weeks ago

Selected Answer: A

D doesn't include test

upvoted 1 times

...

nhatne

1 year, 1 month ago

Selected Answer: D

better to separate each environment, why have to merge them?

upvoted 3 times

...

dija123

1 year, 3 months ago

Selected Answer: A

We have to follow the case requirements not the best practices.

upvoted 2 times

...

yas_cloud

1 year, 4 months ago

I guess this is a tie up between best practices vs what this org (Mountkirk) demands. If this was a standard question on how to setup each env, then answer D fits. But for this use case, seems like A fits the bill. Further more, if all environments/projects are within same org setup, then resources can still be accesses across.

upvoted 2 times

...

lanjr01

1 year, 5 months ago

Answer is D: Question asked is - "What should you do to isolate development environments from staging and production?". If the question meant to include "Test Environment", the question would have looked like this - "What should you do to isolate development & test environments from staging and production?" but that is not the case so the only logical answer will be to vote D.

upvoted 1 times

...

Roro_Brother

1 year, 7 months ago

Selected Answer: D

Definitively D

upvoted 3 times

...

thewalker

1 year, 8 months ago

Selected Answer: D

D repeatable and configurable mechanism - so a network each for dev/test, staging and prod is ideal. But as this option is not there I am choosing D - each one having a project.

upvoted 2 times

...

Ahmed_Safwat

1 year, 8 months ago

Selected Answer: D

D is ok

upvoted 2 times

...

BisoWafik

1 year, 8 months ago

Selected Answer: D

as per conventional best practices.

upvoted 2 times

...

Sarin

1 year, 9 months ago

Selected Answer: A

Although D is follows industry standards its an incomplete answer, it does not say anything about test. A is a much complete answer

upvoted 4 times

...

CyanideX

1 year, 9 months ago

Selected Answer: D

D for sure

upvoted 2 times

...

CyanideX

1 year, 9 months ago

Selected Answer: D

D for me.

upvoted 2 times

...

b6f53d8

1 year, 9 months ago

I think it is B, because you can create separate project for each environment (Test, dev, stage, prod) and connect to right network. You can use firewall rules to set communication between stage and prod.

upvoted 1 times

...

Load full discussion...