Your company wants to track whether someone is present in a meeting room reserved for a scheduled meeting. There are 1000 meeting rooms across 5 offices on 3 continents. Each room is equipped with a motion sensor that reports its status every second. The data from the motion detector includes only a sensor ID and several different discrete items of information. Analysts will use this data, together with information about account owners and office locations. Which database type should you use?

• A. NoSQL
• B. Blobstore
• C. Flat file
• D. Relational

For this question, refer to the TerramEarth case study.
The TerramEarth development team wants to create an API to meet the company ' s business requirements.
You want the development team to focus their development effort on business value versus creating a custom framework. Which method should they use?

• A. Use Google Container Engine with a Django Python container. Focus on an API for the public.
• B. Use Google App Engine with Google Cloud Endpoints. Focus on an API for dealers and partners.
• C. Use Google App Engine with the Swagger (open API Specification) framework. Focus on an API for the public.
• D. Use Google App Engine with a JAX-RS Jersey Java-based framework. Focus on an API for the public.
• E. Use Google Container Engine with a Tomcat container with the Swagger (Open API Specification) framework. Focus on an API for dealers and partners.

For this question, refer to the Dress4Win case study.
As part of their new application experience, Dress4Wm allows customers to upload images of themselves.
The customer has exclusive control over who may view these images. Customers should be able to upload images with minimal latency and also be shown their images quickly on the main application page when they log in. Which configuration should Dress4Win use?

• A. Store image files in a Google Cloud Storage bucket. Use Google Cloud Datastore to maintain metadata that maps each customer ' s ID and their image files.
• B. Store image files in a Google Cloud Storage bucket. Add custom metadata to the uploaded images in Cloud Storage that contains the customer ' s unique ID.
• C. Use a distributed file system to store customers ' images. As storage needs increase, add more persistent disks and/or nodes. Use a Google Cloud SQL database to maintain metadata that maps each customer ' s ID to their image files.
• D. Use a distributed file system to store customers ' images. As storage needs increase, add more persistent disks and/or nodes. Assign each customer a unique ID, which sets each file ' s owner attribute, ensuring privacy of images.

Your ecommerce platform uses a regional Cloud SQL for PostgreSQL database to store critical order information. The business requests a recovery time objective (RTO) of less than 10 minutes and a recovery point objective (RPO) of 2 minutes to ensure business continuity in the event of a full regional outage. You need to design a disaster recovery strategy tor the Cloud SQL database that meets the business ' s strict RTO and RPO requirements. Your design must avoid operational complexity. What should you do?

• A. Use Database Migration Service to continuously replicate the database to another instance in a different region. In a disaster, redirect application traffic to the replica.
• B. Configure the primary instance for high availability (HA). In the event of a regional outage, trigger a failover to the standby instance.
• C. Schedule hourly automated backups of the Cloud SQL instance to a multi-regional Cloud Storage bucket. In a disaster, restore the latest backup to a new instance in a different region.
• D. Configure the Cloud SQL instance with a cross-region read replica. In a disaster, promote the read replica to a standalone, primary instance.

You manage a highly distributed, hybrid- and multi-cloud IT environment and your developers rely heavily on Prometheus for their workflows. You need a cloud-based, highly scalable, low-maintenance enterprise solution that supports Prometheus Query Language (PromQL) queries, quick metric viewing, and efficient issue diagnosis. What should you do?

• A. Deploy a Prometheus operator in your existing Kubernetes and Serverless setup across multi-cloud environments.
• B. Build a SaaS-based, Prometheus-compatible solution to display metrics for each cloud in a customizable way.
• C. Enable Google Cloud Managed Service for Prometheus to monitor and alert on your workloads at scale.
• D. Set up Cloud Monitoring as a single pane of glass across multi-cloud environments.