You want to manage infrastructure across Google Cloud and AWS with a single tool. Which option best supports this goal?
Think about which tool supports multiple clouds natively.
Terraform supports many cloud providers including Google Cloud and AWS, making it suitable for multi-cloud management. Deployment Manager is specific to Google Cloud only.
You want to keep track of your infrastructure changes and state securely. Which tool automatically manages state remotely by default?
Consider how each tool handles the record of deployed resources.
Terraform uses state files to track infrastructure and supports remote backends like Google Cloud Storage for secure state management. Deployment Manager does not use state files in the same way.
You need to securely manage sensitive data like API keys in your infrastructure code. Which option correctly describes the best practice?
Think about how to avoid exposing secrets in code repositories.
Terraform can integrate with Google Secret Manager to securely reference secrets without exposing them in code. Deployment Manager does not provide built-in secret management and embedding secrets in YAML is insecure.
You want to reuse infrastructure code components across projects. Which tool provides better support for modular and reusable code?
Consider which tool has built-in features for code reuse and sharing.
Terraform has a robust module system that allows packaging infrastructure code for reuse and sharing. Deployment Manager uses templates but its reuse capabilities are limited compared to Terraform modules.
You want to detect when infrastructure changes outside your code happen (drift). Which tool provides built-in drift detection and how does it behave?
Think about how each tool compares actual resources to declared code.
Terraform compares the current infrastructure state with the saved state file during planning and alerts users to drift. Deployment Manager lacks automatic drift detection and requires manual checks.