Exam Professional Cloud Architect topic 1 question 30 discussion

E. Cloud Deployment Manager can be used to permanently delete cloud resources F. Cloud Deployment Manager only supports automation of Google Cloud resources

C and F- make sense to me

So the aim solution should turn on "Business risk" A : no technical requirement B : as any COTS C : yes, so setting up the system can take time, and time is money, so business risk D : technical requirement, as for other IaC tool E : if the system is definitevely deleted, money is lost and bad reputation F : that's a fact, a limitation Futhermore when there is risk actions could be taken to mitigate them C : train people, hire experience ones E : code reviews, CI/CD... So C&E is the good couple

Definition of risk: "the possibility of something bad happening" A. is a fact B. Cloud Deployment Manager APIs could be deprecated in the future - part of it was already deprecated, see https://cloud.google.com/deployment-manager/docs/deprecations/composite-types, Deprecation is always a business risk for cloud services. There is some probability and if it happens, it will cost time and money to resolve. C. if it's true, it's a fact D. that's false, see example deployment without service account https://cloud.google.com/deployment-manager/docs/manage-cloud-resources-deployment E. Cloud Deployment Manager can be used to permanently delete cloud resources - there's a probability (hint: "can") that this causes some bad things to happen F. maybe that was a fact when the question was written, using 3rd party APIs is in beta now https://cloud.google.com/deployment-manager/docs/configuration/type-providers/process-adding-api

These are the business risks

I will go for CF

My answer is BF and aligns with similar arguments as those presented by @Choopaower B: This option can be deprecated, as the custom tool has been used for a long time. F: Cloud Deployment Manager only supports automation for Google Cloud resources, not custom resources as often happens in On-Premise environments. C is not a business risk. It is a technical risk. Their engineers may not know it yet, but they can learn.

B and C are the business risks, rest of the options are technical limitations. B. Cloud Deployment Manager APIs could be deprecated in the future C. Cloud Deployment Manager is unfamiliar to the company's engineers The other options might present technical challenges or considerations but are not necessarily business risks. For example: A is more about the programming language used. D is about the service account requirement. E is a capability that, if misused, could cause issues but is not inherently a business risk. F limits scope but isn't a direct business risk.

the right answers are C & E C: because the engineers are dealing with legacy technologies E: Cloud Deployment Manager has the ability to delete resources

I guess everyone agree on C, the debate is between B and F. Before I start, I need to stress on the word "Business" not "Technical" risks, we need to take this in our minds. B: Cloud Deployment Manager APIs could be deprecated in the future >> this is not a risk at all as the APIs cannot be changed without an announcement and also there is a backward compatibility to prevent such issues, this is something that is tackled a decade ago in all cloud providers. F: Cloud Deployment Manager only supports automation of Google Cloud >> Indeed this is a business risk, as the question didn't mention explicitly that the customer is using only GCP, they left it vague by saying "new cloud environment", so we have to assume that it is multi-cloud strategy including On-premise BTW ( Hybrid-Cloud as well ), so we need a tool that can handle deployments on all of those targets. Based on all of that, I recommend ( C & F )

C and F right

BF are correct

E and F

B. Cloud Deployment Manager APIs could be deprecated in the future: There's always a risk that APIs and tools can be deprecated or replaced with new versions. This could impact the long-term stability of your deployment process if the APIs used by Cloud Deployment Manager are deprecated and require migration to new APIs. C. Cloud Deployment Manager is unfamiliar to the company's engineers: If the company's engineers are not familiar with Cloud Deployment Manager, there could be a learning curve and potential delays during the migration process. Training and adaptation time could affect productivity and introduce risks associated with potential mistakes or inefficiencies during the transition.

B. Cloud deployment manager is being deprecated. F. Cloud Deployment Manager only supports automation of Google Cloud resources The question is about business risks - it's not about technical risks A C D E options are technical aspects of the Deployment manager

Should be B & C

My answer is BC. I think the correct answers should be related to the engineer's custom tool. The choices should answer the question "Why should we migrate Lead Engineer's tool to the new cloud environment". It's tried and tested Custom Tool versus the new Deployment Manager. B, because it can be deprecated, custom tool has been used for a long time. C, because their engineers don't know it yet.