CompTIA
Checkpoint
ISC
HP
Dell
EC-Council
EXIN
Fortinet
ITIL®
Juniper
PMI
Microsoft
VMware
Avaya
Google
Salesforce
Amazon
Palo Alto Networks
Certiport
ISC2
All Vendors
  2. Home
  3. Exams
  4. Google
  5. CLOUD-DIGITAL-LEADER

Free CLOUD-DIGITAL-LEADER Exam Braindumps (page: 30)

Page 29 of 104
PDF with 411 Questions

Your customer is making a decision on whether to move to Google Cloud. Their key concern is about 10,000 VMs that are part of their IT infrastructure used across more than 110 applications. They are apprehensive of too many changes at this stage. They want to get to Google Cloud in the easiest way possible with minimal disruption.
What option would you recommend for them?

  1. Use Migrate for Anthos
  2. Lift and shift the VMs to serverless options like App Engine Flex.
  3. Re-architect on-prem to use Kubernetes and then slowly extend and bridge the on-prem data center to the Google Cloud data center.
  4. Use Migrate for Compute

Answer(s): D

Explanation:

Migrate for Compute Engine's advanced replication migration technology copies instance data to Google Cloud in the background with no interruptions to the source workload that's running.



https://cloud.google.com/migrate/compute-engine



You are leading projects in an IT services company. Your customer's project requires analyzing im- ages. They have many 10s of 1000s of raw images that they have made available to you. Your small technology team needs to build a machine learning model. The images are unlabeled. You don't have the people or the capacity to label the images.
What is your approach?

  1. Look for open-source labeled images that closely resemble the given images.
  2. Request data labeling service from Google.
  3. Tell the customer it is their duty to label the images.
  4. Hire temporary workers who can quickly label the images.

Answer(s): C

Explanation:

Google's Data Labeling Service lets you work with human labelers to generate highly accurate labels for a collection of data that you can use in machine learning models.


Reference:

-> https://cloud.google.com/vertex-ai/docs/datasets/data-labeling-job -> https://cloud.google.com/ai-platform/data-labeling/docs



You are working with the head of the IT team and planning the move of computing systems. The questionnaire indicates that they have a reporting application that runs almost 24 hours every day of the week.
When there is extra load, it queues up the processing and executes tasks when there is less demand.
Which of these compute options would you recommend for them?

  1. Use a serverless option - App Engine Standard for Flex
  2. Use a server-based option - Compute Engine.
  3. Use a serverless option - Cloud Functions
  4. Serverless option - Cloud Run

Answer(s): C

Explanation:

- Because Compute Engine VMs are the preferred compute option as they are long-running.



With respect to the Core Feature of Standby Instances of Cloud SQL which one of the options is correct.?

  1. The standby instance is used in high availability to replace the primary instance when failover occurs. The standby instance appears in the Google Cloud Console but does not get billed.
    When failover occurs, connections to the primary instance need to be manually transferred to the standby instance.
  2. The standby instance is used in high availability to replace the primary instance when failover occurs. The standby instance appears in the Google Cloud Console but does not get billed.
    When failover occurs, connections to the primary instance are automatically transferred to the standby instance.
  3. The standby instance is used in high availability to replace the primary instance when failover occurs. The standby instance doesn't appear in the Google Cloud Console.
    When failover occurs, connections to the primary instance are automati-cally transferred to the standby instance.
  4. None of the Above.

Answer(s): C

Explanation:

The standby instance is used in high availability to replace the primary instance when failover occurs. The standby instance doesn't appear in the Google Cloud Console.
When failover occurs, connections to the primary instance are automatically transferred to the standby instance.

Cloud SQL Key Terms:

Cloud SQL instance
A Cloud SQL instance corresponds to one virtual machine (VM). The VM includes the database instance and accompanying software containers to keep the database instance up and running.
Database instance
A database instance is the set of software and files that operate the databases: MySQL, PostgreSQL or SQL Server.
High availability
Cloud SQL instances using high availability (HA) provide greater reliability than non-HA instances. HA in Cloud SQL works by having two synchronized instances: a primary instance and a standby instance. Each instance has exactly one VM. Each instance is in a different zone in the same region.
Failover
A failover is when Cloud SQL switches serving from the original primary instance to the standby instance.
Autofailover is a mechanism that automatically triggers failover when a Cloud SQL instance didn't issue a heartbeat in the previous interval.
Standby instances
The standby instance is used in high availability to replace the primary instance when failover occurs. The standby instance doesn't appear in the Google Cloud Console.
When failover occurs, connections to the primary instance are automatically transferred to the standby instance.
Clone
When you clone a Cloud SQL instance, you create a new instance that is a copy of the source instance, but is completely independent. After cloning is complete, changes to the source instance are not reflected in the clone, and changes in the clone are not reflected in the source instance.
Replication
Replication is the ability to create copies of a Cloud SQL instance or an on-premises database, and offload work to the copies. The main reason for using replication is to scale the use of data in a database without degrading performance on the primary instance.
Read replica
The read replica is an exact copy of the primary instance. Data and other changes on the primary instance are updated in almost real time on the read replica. Send your write transactions to the primary instance, and your read requests to the read replica. The read replica processes queries, read requests, and analytics traffic, thus reducing the load on the primary instance.
Source server
Replication copies transactions from a primary instance to one or more read replicas. The primary instance is also called the source server. The source server can be a Cloud SQL primary instance, or a server outside of Google Cloud, such as an on-premises server or a server running in a different cloud. If the source server is outside of Google Cloud, we call it Replication from an external server.
Cloud SQL Auth proxy client
The Cloud SQL Auth proxy client is open source software maintained by Cloud SQL. It connects to a companion process, the Cloud SQL Auth proxy server, running on your Cloud SQL instance. You run the Cloud SQL Auth proxy client on your own servers. The Cloud SQL Auth proxy client can be used to establish a secure SSL/TLS connection to the database instance, and/or to avoid having to open the firewall. Authentication is done through Identity and Access Management (IAM).






Post your Comments and Discuss Google CLOUD-DIGITAL-LEADER exam with other Community members:

CLOUD-DIGITAL-LEADER Discussions & Posts