Pass the Google Cloud Certified Professional-Cloud-Architect Questions and answers with ExamsMirror

According to Google Cloud Compute Engine documentation, Spot VMs (formerly Preemptible VMs) are the most cost-effective choice for fault-tolerant, batch processing workloads. Since Altostrat’s jobs are "not time-critical" and can "tolerate occasional interruptions," Spot VMs offer a significant discount—typically 60-91%—compared to standard on-demand prices.

The "Reliability and cost management" priority mentioned in the executive statement is directly addressed by utilizing the spare capacity that Spot VMs provide. While these instances can be reclaimed by Google Cloud at any time (preempted) with a 30-second notice, Altostrat’s batch processing architecture (likely running on GKE or managed instance groups) can automatically reschedule these tasks when capacity becomes available again.

Option A (Reserved instances) requires a long-term commitment (1 or 3 years) and is better suited for predictable, constant workloads, not fluctuating batch jobs. Option C (Standard VMs) is unnecessarily expensive for workloads that do not require 100% uptime. Option D (Cloud Run functions) is excellent for event-driven, short-lived tasks but can become more expensive than Spot VMs for heavy, long-running batch computational demands. By leveraging Spot VMs, Altostrat achieves its goal of optimizing cloud storage and compute costs while maintaining the scalability required for its vast media library.

https://cloud.google.com/storage/docs/locations

Capacity planning, TCO calculations, opex/capex allocation From the case study, it can conclude that Management (CXO) all concern rapid provision of resources (infrastructure) for growing as well as cost management, such as Cost optimization in Infrastructure, trade up front capital expenditures (Capex) for ongoing operating expenditures (Opex), and Total cost of ownership (TCO)

Coldline Storage is the best choice for data that you plan to access at most once a year, due to its slightly lower availability, 90-day minimum storage duration, costs for data access, and higher per-operation costs. For example:

Cold Data Storage - Infrequently accessed data, such as data stored for legal or regulatory reasons, can be stored at low cost as Coldline Storage, and be available when you need it.

Disaster recovery - In the event of a disaster recovery event, recovery time is key. Cloud Storage provides low latency access to data stored as Coldline Storage.

https://cloud.google.com/endpoints/docs/openapi/about-cloud-endpoints?hl=en_US &_ga=2.21787131.-1712523161.1522785064

https://cloud.google.com/endpoints/docs/openapi/architecture-overview

https://cloud.google.com/storage/docs/gsutil/commands/test

Develop, deploy, protect and monitor your APIs with Google Cloud Endpoints. Using an Open API Specification or one of our API frameworks, Cloud Endpoints gives you the tools you need for every phase of API development.

From scenario:

Business Requirements

Decrease unplanned vehicle downtime to less than 1 week, without increasing the cost of carrying surplus inventory

Support the dealer network with more data on how their customers use their equipment to better position new products and services

Have the ability to partner with different companies – especially with seed and fertilizer suppliers in the fast-growing agricultural business – to create compelling joint offerings for their customers.

https://cloud.google.com/solutions/iot/

https://cloud.google.com/solutions/designing-conne cted-vehicle-platform

https://cloud.google.com/solutions/designing-connected-vehicle- platform#data_ingestion

http://www.eweek.com/big-data-and-analytics/google-touts-value-of-cloud-iot-core-for-analyzing-conne cted-car-data

https://cloud.goog le.com/solutions/iot/

The push endpoint can be a load balancer.

A container cluster can be used.

Cloud Pub/Sub for Stream Analytics

https://cloud.google.com/solutions/data-lifecycle-cloud-platform

https://cloud.google.com/solutions/designing-connected-vehicle-platform

The Avro binary format is the preferred format for loading compressed data. Avro data is faster to load because the data can be read in parallel, even when the data blocks are compressed.

Cloud Storage supports streaming transfers with the gsutil tool or boto library, based on HTTP chunked transfer encoding. Streaming data lets you stream data to and from your Cloud Storage account as soon as it becomes available without requiring that the data be first saved to a separate file. Streaming transfers are useful if you have a process that generates data and you do not want to buffer it locally before uploading it, or if you want to send the result from a computational pipeline directly into Cloud Storage.

According to the Google Cloud Architecture Framework: Performance Excellence, Local SSDs are the optimal choice for "scratch" space, temporary files, and workloads requiring the lowest possible latency and highest IOPS. Unlike Persistent Disks (Option C) or Filestore (Option B), which are network-attached, Local SSDs are physically attached to the server that hosts the virtual machine instance.

This physical proximity eliminates network latency, providing sub-millisecond access times which are critical for "frequently accessed and modified" temporary files during AI training and inference. For generative AI, where data shuffling and checkpointing are intensive, the high throughput of Local SSDs prevents the storage layer from becoming a bottleneck for the expensive GPU/TPU accelerators.

While the data on Local SSDs is ephemeral (lost if the VM is deleted or undergoes certain maintenance events), this perfectly matches Cymbal's requirement for "temporary files." Furthermore, Local SSDs can be more cost-effective than provisioning high-performance Persistent Disks of equivalent speed, as their performance is not tied to the disk size. Cloud Storage (Option A) is unsuitable for this specific use case due to the significantly higher latency of object-based storage compared to block-based local storage.