(You are migrating your company's on-premises compute resources to Google Cloud. You need to deploy batch processing jobs that run every night. The jobs require significant CPU and memory for several hours but can tolerate interruptions. You must ensure that the deployment is cost-effective. What should you do?)
Spot VMs (formerly known as preemptible VMs) are Compute Engine virtual machine instances that are available at a much lower price than standard Compute Engine instances. However, Compute Engine might preempt (stop) these instances if it needs to reclaim those resources for other tasks. This makes Spot VMs ideal for batch processing jobs that are fault-tolerant and can handle interruptions, as they can be restarted when resources become available again. This directly addresses the requirement for a cost-effective solution for interruptible workloads.
Option A: While containerization offers portability and consistency, it doesn't inherently provide cost savings for compute resources. You would still need to choose a cost-effective underlying compute option.
Option B: Custom machine types allow you to tailor the CPU and memory configuration of your VMs, which can optimize costs to some extent by avoiding over-provisioning. However, they don't offer the significant cost reduction that Spot VMs provide.
Option C: The M1 machine series is a specific family of Compute Engine instances optimized for memory-intensive workloads. While potentially suitable for the job's requirements, it doesn't inherently address the cost-effectiveness requirement as directly as Spot VMs, which are priced lower regardless of the machine series.
Reference to Google Cloud Certified - Associate Cloud Engineer Documents:
The concept and use cases for Spot VMs are explicitly covered in the Compute Engine section of the Google Cloud documentation, which is a key area for the Associate Cloud Engineer certification. The cost savings and suitability for fault-tolerant workloads are highlighted as primary benefits.
Your team is building a website that handles votes from a large user population. The incoming votes will arrive at various rates. You want to optimize the storage and processing of the votes. What should you do?
Pub/Sub is a scalable and reliable messaging service that can handle large volumes of data from different sources at different rates. It allows you to decouple the producers and consumers of the data, and provides a durable and persistent storage for the messages until they are delivered. Cloud Functions is a serverless platform that can execute code in response to events, such as messages published to a Pub/Sub topic. It can scale automatically based on the load, and you only pay for the resources you use. By using Pub/Sub and Cloud Functions, you can optimize the storage and processing of the votes, as you can handle the variable rates of incoming votes, process them in real time or near real time, and avoid managing servers or VMs.Reference:
Pub/Sub documentation
Cloud Functions documentation
Choosing a messaging service for Google Cloud
Your development team needs a new Jenkins server for their project. You need to deploy the server using the fewest steps possible. What should you do?
Your company uses Pub/Sub for event-driven workloads. You have a subscription named email-updates attached to the new-orders topic. You need to fetch and acknowledge waiting messages from this subscription. What should you do?
The goal is to pull (fetch) messages from a subscription and acknowledge them.
The gcloud pubsub subscriptions **pull** command retrieves messages from a specified subscription.
The --auto-ack flag instructs the command to automatically acknowledge the messages after they are successfully retrieved, combining the two required actions into one command.
'Pulls one or more messages from the specified subscription. To acknowledge the pulled messages, use the --auto-ack flag.'
You have an application that uses Cloud Spanner as a backend database. The application has a very predictable traffic pattern. You want to automatically scale up or down the number of Spanner nodes depending on traffic. What should you do?
As to mexblood1's point, CPU utilization is a recommended proxy for traffic when it comes to Cloud Spanner. See: Alerts for high CPU utilization The following table specifies our recommendations for maximum CPU usage for both single-region and multi-region instances. These numbers are to ensure that your instance has enough compute capacity to continue to serve your traffic in the event of the loss of an entire zone (for single-region instances) or an entire region (for multi-region instances). -https://cloud.google.com/spanner/docs/cpu-utilization
Margaret Anderson
1 day agoNancy Campbell
29 days agoKenneth Cooper
1 month agoMark Anderson
2 months agoJason Moore
2 months agoRonald Rivera
3 months agoKevin Nguyen
2 months agoSharon Nelson
2 months agoHeather Lewis
3 months agoGerald Jones
3 months agoFrank Reed
3 months agoDaniel Gonzalez
3 months agoKristel
4 months agoVerona
4 months agoLynelle
4 months agoShalon
5 months agoWhitley
5 months agoKristeen
5 months agoMeghan
5 months agoAlberto
6 months agoDominga
6 months agoGladys
6 months agoMi
6 months agoTrina
7 months agoJose
7 months agoLavonne
7 months agoStefan
7 months agoHoa
8 months agoKiley
8 months agoAbraham
8 months agoWalker
8 months agoCecily
9 months agoCarlene
9 months agoJohnetta
9 months agoMalinda
9 months agoTalia
10 months agoGianna
10 months agoMuriel
10 months agoAdaline
10 months agoTien
10 months agoMicah
11 months agoMargurite
11 months agoKarima
1 year agoMauricio
1 year agoPeter
1 year agoDevon
1 year agoStaci
1 year agoShelia
1 year agoAvery
1 year agoRoselle
1 year agoLuisa
1 year agoLeonida
1 year agoKati
1 year agoSheldon
1 year agoGerald
1 year agoTwanna
2 years agoTambra
2 years agoRoyal
2 years agoDelmy
2 years agoLorrine
2 years agoLoreta
2 years agoArlyne
2 years agoKristofer
2 years agoKeneth
2 years agoErasmo
2 years agoSkye
2 years agoClaribel
2 years agoGolda
2 years agoBrinda
2 years agoErick
2 years agoYvonne
2 years agoBette
2 years agoTennie
2 years agoBev
2 years agoLashaunda
2 years agoMerlyn
2 years agoJunita
2 years agoMadonna
2 years agoKeneth
2 years agoGregoria
2 years agoMabel
2 years agoBrittni
2 years agoCharlesetta
2 years agowibimosentrau
2 years ago