Correct answer: Use Cloud Build linked with a GitHub repository to trigger retraining when new code is pushed to the repository.
A Cloud Build trigger connected to your Git repository (for example, GitHub) starts a build only when new code is pushed, so retraining runs automatically (no manual intervention), only when the architecture actually changes (minimal compute cost), and the code is version-controlled in Git. Submitting jobs manually with gcloud requires intervention, Cloud Storage is not version control, and a daily Composer sensor adds cost and polling overhead.