A lead engineer wrote a custom tool that deploys virtual machines in the legacy data center. He wants to migrate the custom tool to the new cloud environment.
You want to advocate for the adoption of Google Cloud Deployment Manager.
What are two business risks of migrating to Cloud Deployment Manager? (Choose two.)
One business risk of migrating to Cloud Deployment Manager is that its APIs could be deprecated in the future. This deprecation could make it difficult to maintain and update the tool, potentially causing disruptions or requiring additional resources to find or develop an alternative solution. Another business risk is that Cloud Deployment Manager is unfamiliar to the company's engineers. This lack of familiarity could slow down the migration process and lead to increased costs and delays as the engineers need to spend time and resources learning how to use the new tool effectively.
E. Cloud Deployment Manager can be used to permanently delete cloud resources F. Cloud Deployment Manager only supports automation of Google Cloud resources
Yup, E + F. In GCP documentation it states as a warning note that deletion made through Deployment Manager scripts cannot be undone, if devs are not well trained a human errors can impact Business
F is not a risk, it is a limitation of solution. Risk is something that is not known for sure and is manageable (risk can be mitigated, avoided). You cannot manage the limitation of solution. You can use it with this limitation or not and you know it in advance.
Advocating to adopt Google Cloud Deployment Manager will become a risk if the lead engineer or other business need ask for use other cloud platform.
C and F- make sense to me
I think this is right. the key of the question is "business risks".
yes, C and F right
C - Makes sense, because company engineer may take longer to develop, so more cost and more 'time-to-market' Reg F: Can I pls ask how does business care whether you are Google Cloud Resources or legacy data center tools, as long as it servs business requirement? So I'm leaning towards E, as the engineers are still in the process of learning CDM and may accidently delete VMs bringing down the entire application.
Forgot to mention, once determined as "risks", the mitigation actions below can be followed: C: Train the existing resources, Hire an experienced personnel E: Peer Reviews, QA, thorough testing etc.
Whizlabs has this question on their practice tests and they say EF (can delete and only works for GCP). It's not relevant if they don't know the tool yet because they can learn something new.
I didn't quite understand the meaning of the question. Will the custom tool be replaced by the deployment manager (which will therefore use yaml or python models) or will it be maintained and will have to interact with it (via API)?
CF - Correct https://encore.dev/resources/google-cloud-deployment-manager Drawbacks Learning Curve: Can be challenging for new users, particularly those not familiar with YAML. Vendor Lock-in: Confined exclusively to GCP, hindering a multi-cloud strategy. Less Community Support: May lack extensive community support compared to some alternatives.
According to Google Bard AI: The two business risks of migrating to Cloud Deployment Manager are B. Cloud Deployment Manager APIs could be deprecated in the future and C. Cloud Deployment Manager is unfamiliar to the company's engineers. B --> This could make it difficult to maintain and update the tool, and could also prevent the company from taking advantage of new features that are added to Cloud Deployment Manager. C --> a business risk because it will require the company to invest time and resources in training its engineers how to use the tool. This could slow down the migration process, and could also make it more difficult for the company to adapt to new changes in the tool.
Since business risks are mentioned. C. Training resources will be a cost and untrained resources might cause unnecessary issues costing the business. F. Since the current tool is developed in house and used on premise its not clear if its used for GCP only. GCP deployment manager is only for GCP resources.
All solutions can be deprecated, even GCP. So we are talking about current business risks, so for me work C and F
for me C and F
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.
Cloud Deployment Manager Drawbacks - Learning Curve: Can be challenging for new users, particularly those not familiar with YAML. - Vendor Lock-in: Confined exclusively to GCP, hindering a multi-cloud strategy. - Less Community Support: May lack extensive community support compared to some alternatives.
we are considering business risks
I would go with c and f
It can't be C because if Cloud Deployment Manager is unfamiliar to the company's engineers, they have to learn it.
Well that's why it's a risk. C is definitely one of the answers.
It's about business risk.
B: Cloud deployment manager is being deprecated. F: Mentions on-premise resources and managing GCP which will make cloud deployment manager not the best tool for this.
Chat GPT tells me B and C and it gets it right maybe 98% of the time so far. It seems nobody on this discussion can agree on an answer but if we're going to look at keywords of the questions and over-scrutinize them, then yes, risk is a key word and I don't see F as a risk. E is a risk but not even remotely unique to this situation. C is a mild risk but really the only one that makes sense in light of eliminating the others. B is definitely a risk... but then it also isn't unique to this service so we're back at the same issue with E. This question is garbage.