Generative AI Leader Practice Question: Business Strategies for Generative AI Solutions
A company has been using an on-premises ML infrastructure for generative AI and wants to migrate to Google Cloud. They have a pipeline that fine-tunes a large language model weekly using a proprietary dataset. The migration must minimize downtime and data transfer costs. Which approach best addresses these requirements?
⚠ Common exam trap
Test-takers frequently assume full data migration (e.g., Cloud Storage Transfer Service) is necessary, overlooking incremental sync capabilities of Vertex AI Managed Datasets with BigQuery, which directly addresses cost and downtime minimization.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use Vertex AI Pipelines to orchestrate the fine-tuning process, and use Vertex AI Managed Datasets to incrementally sync new data with BigQuery as the source.
Vertex AI Pipelines provides a managed, serverless orchestration service that can run the weekly fine-tuning workflow with minimal operational overhead, while Vertex AI Managed Datasets can incrementally sync new data from BigQuery, reducing data transfer costs by avoiding full dataset copies. This combination minimizes downtime because the pipeline can be triggered on a schedule without manual intervention, and incremental syncs avoid re-transferring the entire proprietary dataset each week.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Use Vertex AI Pipelines to orchestrate the fine-tuning process, and use Vertex AI Managed Datasets to incrementally sync new data with BigQuery as the source.
Why this is correct
Vertex AI Pipelines offers a managed orchestration service that can schedule the weekly fine-tuning workflow with minimal operational overhead. Combined with Vertex AI Managed Datasets, which incrementally sync new data from BigQuery, this approach reduces data transfer costs by avoiding full dataset copies and minimizes downtime by enabling automated, scheduled execution without manual intervention.
- ✗
Use AutoML to train a new model directly from the dataset without fine-tuning.
Why it's wrong here
AutoML is designed for training models from scratch with automated hyperparameter tuning and architecture search, not for fine-tuning an existing large language model. It would not leverage the proprietary dataset or the base model, resulting in a fundamentally different approach that does not meet the requirement of fine-tuning the existing LLM.
- ✗
Deploy the existing pipeline on a Google Kubernetes Engine cluster and use Google Cloud Filestore for shared storage.
Why it's wrong here
Deploying the existing pipeline on Google Kubernetes Engine with Filestore for shared storage requires significant operational overhead for cluster management and storage scaling. While possible, it does not provide the incremental sync capability of Vertex AI Managed Datasets, leading to higher data transfer costs and potential downtime during full data migrations. This is not the most optimized solution for minimizing downtime and cost.
- ✗
Use Cloud Storage Transfer Service to move all data to Cloud Storage, then set up a Vertex AI custom training job to run the fine-tuning.
Why it's wrong here
Cloud Storage Transfer Service is intended for one-time or scheduled batch transfers of data to Cloud Storage. It would require a full initial data transfer, incurring high costs and potential downtime, and does not natively support incremental syncing of new data for weekly fine-tuning. This approach lacks the integration with BigQuery and the incremental capabilities that Vertex AI Managed Datasets provide.
Quick reference
Cloud Service Model Comparison
| Model | You Manage | Provider Manages | Examples |
|---|---|---|---|
| IaaS | OS, runtime, apps, data | Hardware, hypervisor, networking | EC2, Azure VMs, GCP Compute Engine |
| PaaS | Apps and data | OS, runtime, middleware, hardware | Elastic Beanstalk, Azure App Service |
| SaaS | Data and settings only | Everything else | Microsoft 365, Salesforce, Workday |
| FaaS / Serverless | Function code only | Infra, scaling, runtime | Lambda, Azure Functions, Cloud Run |
| CaaS | Containers and apps | Kubernetes, OS, hardware | EKS, AKS, GKE |
Go deeper
Related to this question
About these practice questions
One of 1,008 original Generative AI Leader practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This Generative AI Leader practice question is part of Courseiva's free Google Cloud certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the Generative AI Leader exam.