https://medium.com/google-cloud/how-to-deploy-cassandra-and-connect-on-google-cloud-platform-with-a- few-clicks-11ee3d7001d1
https://cloud.google.com/blog/products/databases/open-source-cassandra-now-managed-on-google-cloud
https://cloud.google.com/marketplace
You can deploy Cassandra as a Service, called Astra, on the Google Cloud Marketplace. Not only do you get a unified bill for all GCP services, your Developers can now create Cassandra clusters on Google Cloud in minutes and build applications with Cassandra as a database as a service without the operational overhead of managing Cassandra

Cloud Run takes any container images and pairs great with the container ecosystem: Cloud Build, Artifact Registry, Docker. ... No infrastructure to manage: once deployed, Cloud Run manages your services so you can sleep well. Fast autoscaling. Cloud Run automatically scales up or down from zero to N depending on traffic.
https://cloud.google.com/run

as the instances (normal or preemptible) would be terminated and relaunched if the health check fails either due to application not configured properly or the instances firewall do not allow health check to happen.
GCP provides health check systems that connect to virtual machine (VM) instances on a configurable, periodic basis. Each connection attempt is called a probe. GCP records the success or failure of each probe.
Health checks and load balancers work together. Based on a configurable number of sequential successful or failed probes, GCP computes an overall health state for each VM in the load balancer. VMs that respond successfully for the configured number of times are considered healthy. VMs that fail to respond successfully for a separate number of times are unhealthy.
GCP uses the overall health state of each VM to determine its eligibility for receiving new requests. In addition to being able to configure probe frequency and health state thresholds, you can configure the criteria that define a successful probe.

The most secure method and Google-recommended practice for local testing of service account permissions is Service Account Impersonation , as it avoids the security risk of managing physical key files.
* Option A (Impersonation): This method allows your user credentials to temporarily act as the service account. It is keyless , meaning no service account key needs to be created, downloaded, or stored, which is the cornerstone of secure credential management on Google Cloud.
Reference: Google Cloud Documentation - Best practices for using service accounts :
" Avoid creating service account keys. Service account keys pose a security risk. If a service account key is compromised, an attacker can use it to gain access to Google Cloud resources. Instead, use service account impersonation or workload identity federation. " Reference: Google Cloud Documentation - Service Account Impersonation (Overview) :
" This is useful for testing permissions... but you want to avoid creating and downloading a service account key . "

The correct answer is B because Cloud Storage is the appropriate Google-managed object storage service for durable document storage, and Object Lifecycle Management can automatically transition objects to a lower-cost storage class after a defined age. The documents are frequently accessed for the first six months, so keeping them initially in Standard storage is reasonable. After six months, the documents are retained mainly for audit purposes, making Coldline more cost-effective for infrequently accessed data. Option A is backward because Standard is the higher-access storage class, not the archive target. Filestore is a managed file system, not the best low-cost object archive for invoices. Moving data manually or through Filestore adds unnecessary operational overhead.