Preparing Practice Exam…
Please wait a moment while the system generates the exam questions, answers, and study session.
Please wait a moment while the system generates the exam questions, answers, and study session.
Question 49 of 63
Free Preview · 63 of 210 · questions 1–63 of 210 are free. Sign up free to sync your progress across devices.
Select one answer.
Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.
Correct Answer: D. A GPU-accelerated video rendering platform that retrieves and stores videos in a storage bucket. Why D is suitable for Preemptible VMs: Preemptible VMs (now called Spot VMs) are significantly cheaper (up to 80% discount) but can be terminated by Google at any time with only 30 seconds notice.
✅ Batch processing workload - perfect for preemptible VMs ✅ Stateless: Input from bucket, output to bucket ✅ Fault-tolerant: Can restart failed rendering jobs ✅ Job-based: Each video render is independent ✅ Interruptible: Can checkpoint progress or restart ✅ Cost-sensitive: GPU instances are expensive, 80% savings significant ✅ Not time-critical: Rendering can be queued/retried ✅ Perfect fit for preemptible VMs
Caches are stateless and disposable. If a cache instance is preempted, the data is simply loaded again from the primary data store (e.g., database) when requested, causing a slight latency spike but no Video rendering is a long-running, stateful batch job (the rendering progress). While the final output is safe in a storage bucket, preemption would waste significant GPU time and money by forcing the entire rendering job (or a large portion of it) to restart from the last checkpoint, minimizing the intended cost savings.