You need to share proposed infrastructure changes with your team following Google-recommended practices. What should you do?

Storing Deployment Manager templates in Cloud Source Repositories aligns with Google-recommended practices for infrastructure as code. This approach enables version control, collaboration, and an auditable history of infrastructure changes, which are crucial for managing complex cloud environments. Deployment Manager templates define infrastructure declaratively, ensuring consistency and repeatability. Cloud Source Repositories provide a secure and integrated platform for managing these templates. The other options are less suitable: Storing templates in a Cloud Storage bucket lacks version control and collaboration features inherent in a source code repository. Applying changes directly in a dev environment and saving gcloud command output describes the current state of resources, not the proposed changes in a declarative, version-controlled manner. This approach is not infrastructure as code and makes tracking and reverting changes difficult.