Cloud-Digital-Leader Exam Dumps - Google Cloud Certified Questions and Answers

The correct answer is B. Back up data regularly. Here's why:

Context of the Question: The organization is concerned about data loss due to hardware failures or cyber-attacks and wants to restore their systems to a previous state in case of such events.

Google Cloud Product Relevance:

Backing up data regularly is the most effective way to ensure data can be restored in case of loss or damage. Regular backups create copies of data that can be stored separately from the main systems, ensuring that even if the primary data is lost or compromised, the backup can be used to restore it to a previous state.

Google Cloud offers several backup solutions, such as Cloud Storage for storing backups and Cloud SQL automated backups for database instances.

Why Not Other Options:

A. Use Cloud Monitoring: Cloud Monitoring helps observe and monitor the health and performance of applications and infrastructure but does not provide backup or data restoration capabilities.

C. Set service level objectives (SLOs): SLOs are targets for service availability and performance but do not directly help with data backup or recovery.

D. Enable autoscaling: Autoscaling helps automatically adjust resources to meet demand but does not protect against data loss or provide restoration capabilities.

Google Cloud Digital Leader References:

To understand more about backup strategies in Google Cloud, refer to Backup and DR (Disaster Recovery) documentation.

Cloud Vision API allows you to programmatically identify images, text, etc. in the document. This would be the best option.

https://cloud.google.com/vision

Cloud Bigtable

A fully managed, scalable NoSQL database service for large analytical and operational workloads with up to 99.999% availability.

- Consistent sub-10ms latency—handle millions of requests per second

- Ideal for use cases such as personalization, ad tech, fintech, digital media, and IoT

- Seamlessly scale to match your storage needs; no downtime during reconfiguration

- Designed with a storage engine for machine learning applications leading to better predictions

- Easily connect to Google Cloud services such as BigQuery or the Apache ecosystem

Preemptible instances function like normal instances but have the following limitations:

-> Compute Engine might stop preemptible instances at any time due to system events. The probability that Compute Engine will stop a preemptible instance for a system event is generally low, but might vary from day to day and from zone to zone depending on current conditions.

-> Compute Engine always stops preemptible instances after they run for 24 hours. Certain actions reset this 24-hour counter.

-> Preemptible instances are finite Compute Engine resources, so they might not always be available.

-> Preemptible instances can't live migrate to a regular VM instance, or be set to automatically restart when there is a maintenance event.

-> Due to the above limitations, preemptible instances are not covered by any Service Level Agreement (and, for clarity, are excluded from the Compute Engine SLA).

-> The Google Cloud Free Tier credits for Compute Engine do not apply to preemptible instances.

The Bare Metal solution is the recommended approach. You can deploy Oracle capabilities like clustered databases, replication, and all performance features at licensing costs that are similar to on-premise systems

https://cloud.google.com/architecture/migrating-bare-metal-workloads

Google Cloud Pub/Sub is a scalable, durable event ingestion and delivery system.

-> Pub/Sub allows services to communicate asynchronously, with latencies on the order of 100 milliseconds.

-> Pub/Sub is used for streaming analytics and data integration pipelines to ingest and distribute data. It is equally effective as messaging-oriented middleware for service integration or as a queue to parallelize tasks.

-> Pub/Sub enables you to create systems of event producers and consumers, called publishers and subscribers. Publishers communicate with subscribers asynchronously by broadcasting events, rather than by synchronous remote procedure calls (RPCs).

Reference link- https://cloud.google.com/pubsub/docs/overview

Using sync for new images implies that you will continue to use your onprem and keep synchronizing it forever, Sync just once for the old images, new images go directly to google cloud via pub/sub, and eventually get rid of the onprem.