
Custom training on Gemini Enterprise Agent Platform (formerly Vertex AI) lets you bring your own training code and run it on managed Google Cloud infrastructure. You keep full control over the model architecture and training logic while Agent Platform handles orchestration, provisioning, and scaling underneath. On the Professional Machine Learning Engineer exam, custom training scenarios typically focus on choosing between serverless training and training clusters, then selecting the right container, compute, storage, and deployment options for the workload.
Agent Platform supports two ways to execute custom training jobs, and they reflect opposite approaches to compute management. Serverless training runs your job without requiring you to provision or manage any infrastructure. Your training code executes inside containers, and the job configuration lives in a worker pool spec object. That single spec object declares both the compute settings and the container specification, describing what machine to use and what image to run on it. Rather than creating or maintaining servers, you declare the hardware you need. Compute is provisioned on demand when the job starts and deleted once it finishes. Because you only pay while the job is actively running and nothing remains afterward to clean up, serverless training is the lower-cost default for most workloads.
Training clusters take the opposite approach by reserving a dedicated cluster of accelerators that remains allocated for your workload. That design fits large-scale or mission-critical jobs. Because capacity is reserved in advance, you get assured capacity and eliminate queue times so jobs start immediately. Without a reservation, a large job can sit waiting for accelerators to become available. Training clusters also automate the more complex operational parts of running dedicated hardware, including environment setup and hardware fault recovery to maximize continuous cluster uptime. On a long distributed training run, a single failed node would normally kill the job. A training cluster detects the failure and recovers the node so training continues without manual intervention.
In practice, we lean toward serverless training as the default whenever pay-as-you-go execution and zero infrastructure management are the priority. Training clusters become the better choice when a job is large enough or important enough that waiting on accelerator capacity or losing progress to hardware failures is not acceptable.
A custom training workflow starts by loading the raw input data. Agent Platform training jobs can read data from Cloud Storage, BigQuery, or a managed dataset stored inside Agent Platform.
Next comes the training script stage, where you define the model logic and package it for execution. Agent Platform gives you two container options depending on how much customization your code requires:
Once the training image is ready, you configure the compute environment and storage for the job. Each setting defines a specific layer of the execution environment:
After defining compute and storage, you pick the execution mode. Smaller jobs can run on a single VM, while large or complex jobs can be distributed across multiple VMs. On the Professional Machine Learning Engineer exam, matching the storage layer and execution mode to the size and distribution needs of the training job is a common architectural distinction.
When training completes, the resulting model can be pushed into the Agent Platform Model Registry, where model versions are tracked and managed. From the Model Registry, you can deploy the model to an endpoint, which creates an API you can call for real-time predictions. Taken together, the workflow gives you full flexibility over your training logic and execution environment while Google Cloud handles orchestration and scaling behind the scenes.
Our Professional Machine Learning Engineer course covers Agent Platform custom training jobs alongside Model Registry and endpoint deployment, with practice questions that drill these distinctions.