Using BigQuery can get expensive if you have somehow check the logs for anomalies.
https://cloud.google.com/blog/products/management-tools/automate-your-response-to-a-cloud- logging-event

C - Is a business risk because the lead engineer / engineers will need to learn a new tool.
F - If the company decide to move infra to Azure, AWS or VMware for example, they can't use Cloud Deployment Manager templates, where Terraform would work across different platforms (better business case).
https://cloud.google.com/deployment-manager/docs/deployments/deleting-deployments

There is no explicit command for rolling back an update to a previous version, but if you decide to roll back an update (either a fully committed update or a canary update), you can do so by making a new update request and passing in the instance template that you want to roll back to.
https://cloud.google.com/compute/docs/instance-groups/rolling-out-updates-to-managed- instance-groups#rolling_back_an_update

https://cloud.google.com/sql/docs/mysql/connect-kubernetes-
engine#providing_the_service_account_to_the_proxy

Use multiple network interfaces when an individual instance needs access to more than one VPC network, but you don't want to connect both networks directly.
https://cloud.google.com/vpc/docs/multiple-interfaces-concepts