Your development team is using Cloud Build to promote a Node.js application built on App Engine from your staging environment to production. The application relies on several directories of photos sto

Question

Options

• AManually copy the photos to webphotos-prod.
• BAdd a startup script in the application's app.yami file to move the photos from webphotos-staging
• CAdd a build step in the cloudbuild.yaml file before the promotion step with the arguments:
• DAdd a build step in the cloudbuild.yaml file before the promotion step with the arguments:

• A
  4% (1)
• B
  8% (2)
• C
  71% (17)
• D
  17% (4)

Explanation

Adding a build step to cloudbuild.yaml integrates the photo copy directly into the CI/CD pipeline, automating it as part of every promotion. Choice C uses gsutil (the Cloud Storage CLI) as a Cloud Build step - specifically with rsync or cp arguments - to copy the photos from webphotos-staging to webphotos-prod before the App Engine promotion step. This ensures the photos are always in sync before the new app version goes live. Choice A (manual copy) is not automated. Choice B (startup script in app.yaml) runs when the app starts, not during the build/promotion phase, and is not designed for data migration. Choice D likely uses incorrect or less appropriate arguments than Choice C (e.g., wrong flags or command structure for this use case).

No community discussion yet for this question.