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: 49)

Page 48 of 104
PDF with 411 Questions

Your customer has a reporting tool that is only occasionally used by the leadership team. Usage of it is frequent - once a week, once a month, or once the quarter. They want to run this application in a cost-effective manner.
What are the compute options available on Google Cloud which would be suitable? (Choose Two answer)

  1. Cloud Run
  2. Cloud App Engine Standard
  3. Compute Engine
  4. Kubernetes Engine

Answer(s): A,B

Explanation:

Since the use of the tool is infrequent/intermittent, you can choose to compute options that are serverless. Both Cloud Run and Cloud App Engine Standard are serverless options that can shut down to zero. Since cost-effectiveness is a requirement, this will not cost anything during the periods it is not used.



You are working in a company where you need to store Terabytes of Image Data daily and process them e.g. Taking photos of the entire planet 24 hours every day with satellite and sending data to data centres to store and process it.
Which of the following would be the best combination for your infrastructure.

You are working in a company where you need to store Terabytes of Image Data daily and process them e.g. Taking photos of the entire planet 24 hours every day with satellite and sending data to data centres to store and process it.
Which of the following would be the best combination for your infrastructure.

  1. Bare Metal Solutions with Google Cloud Storage.
  2. Google Cloud Storage & Google Cloud Compute Engines
  3. Google Cloud Storage & Preemptible VMs.
  4. None of the Above

Answer(s): C

Explanation:

The above is a real world example of a company named Planet, where they sent around 80+ satellites to take pictures of earth every day, 24 hours. They run around 40,000 preemptible VMs concurrently.

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.

Reference link- https://cloud.google.com/compute/docs/instances/preemptible



DriveSuper Inc. teaches its clients to drive cars and bikes and helps them get their license. They are planning to build a mobile application where users can sign up, plan their schedules, and take stock of progress. They want the onboarding process to be smooth and frictionless, giving users a great experience from the get-go. They want this done as quickly as possible and not be expensive.
What is their best option on Google Cloud?

  1. Build the mobile app with Cloud SQL as the backend
  2. Build the mobile app with Cloud Storage as the backend
  3. Build the mobile application with Firebase as the backend
  4. Build the mobile app with Cloud Spanner as the backend

Answer(s): C

Explanation:

Firebase/Firestore is easy to build and is suitable for user information that could bvary in nature.



Which of the following is true while creating a boot persistent disk from a snapshot.

  1. You cannot apply a snapshot to an existing persistent disk, or apply a snapshot to persistent disks that belong to a different project than that snapshot.
  2. It is only possible to apply data from a snapshot when you first create a persistent disk.
  3. After you create a snapshot of a boot persistent disk, you can apply data from that snapshot to ne w persistent disks.
  4. All of the above.

Answer(s): D

Explanation:

When you create a virtual machine (VM) instance, you must also create a boot disk for the VM. You can use a public image, a custom image, or a snapshot that was taken from another boot disk.
When you create a boot disk, limit the disk size to 2 TB to account for the limitations of MBR partitioning. Compute Engine automatically creates a boot persistent disk when you create an instance. If you require additional data storage space for your instances, add one or more secondary instance storage options.
You might need to create a standalone boot persistent disk and attach it to an instance later, or resize a boot persistent disk to improve performance and add more space for additional applications or operating system files. That process is described in Add or resize a persistent disk. As a best practice, do not use regional persistent disks for boot disks. In a failover situation, they do not force-attach to a VM.

After you create a snapshot of a boot persistent disk, you can apply data from that snapshot to new persistent disks. It is only possible to apply data from a snapshot when you first create a persistent disk. You cannot apply a snapshot to an existing persistent disk, or apply a snapshot to persistent disks that belong to a different project than that snapshot.






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

CLOUD-DIGITAL-LEADER Discussions & Posts