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.)
Click on the arrows to vote for the correct answer
A. B. C. D. E. F.BF.
The correct answers are B and C.
B. Cloud Deployment Manager APIs could be deprecated in the future: There is always a risk that any technology may be deprecated in the future. Google could decide to discontinue the Cloud Deployment Manager APIs at some point, which could result in the need to rewrite scripts and automation workflows that rely on this tool. Therefore, this poses a business risk for the company that is considering adopting this tool.
C. Cloud Deployment Manager is unfamiliar to the company's engineers: The adoption of new technology requires a learning curve for the engineering team, which can lead to decreased productivity and increased costs due to the need for training. The unfamiliarity of Cloud Deployment Manager to the company's engineers is a business risk that needs to be considered before adopting it as the primary deployment tool.
The other options in the question are not valid business risks:
A. Cloud Deployment Manager uses Python: This is not a business risk but rather a technical detail of the tool.
D. Cloud Deployment Manager requires a Google APIs service account to run: This is not a business risk but rather a requirement for using the tool.
E. Cloud Deployment Manager can be used to permanently delete cloud resources: This is not a business risk of migrating to Cloud Deployment Manager, but rather a risk associated with the use of any tool that can delete cloud resources.
F. Cloud Deployment Manager only supports automation of Google Cloud resources: This is not a business risk but rather a limitation of the tool that needs to be taken into consideration while deciding whether to adopt it or not.