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.)

Migrating to Cloud Deployment Manager introduces the risk of unfamiliarity among engineers, requiring training and a learning curve, which can impact productivity and project timelines. Additionally, Cloud Deployment Manager is designed specifically for Google Cloud resources. If the company has a hybrid cloud strategy or uses other cloud providers, this tool will not automate those non-Google Cloud resources, necessitating separate automation solutions and increasing management complexity. The other options are less direct business risks: "Cloud Deployment Manager uses Python" is incorrect; it uses YAML for configuration and Jinja2 or Python for templates, but the language itself isn't a business risk. "Cloud Deployment Manager APIs could be deprecated in the future" is a general risk for any cloud service, not specific to Deployment Manager as a unique business risk. "Cloud Deployment Manager requires a Google APIs service account to run" is a standard operational requirement, not a business risk. "Cloud Deployment Manager can be used to permanently delete cloud resources" is a feature of infrastructure-as-code tools, requiring proper access controls, not an inherent business risk of adoption.