You are a developer working with the CI/CD team to troubleshoot a new feature that your team introduced. The CI/CD team used HashiCorp Packer to create a new Compute Engine image from your…

Question

Options

• ACreate a new feature branch, and ask the build team to rebuild the image.
• BShut down the deployed virtual machine, export the disk, and then mount the disk locally to
• CInstall Packer locally, build the Compute Engine image locally, and then run it in your personal
• DCheck Compute Engine OS logs using the serial port, and check the Cloud Logging logs to

• A
  4% (1)
• B
  8% (2)
• C
  77% (20)
• D
  12% (3)

Explanation

Building the Compute Engine image locally using Packer against your development branch gives you a reproducible, isolated environment to iteratively debug the build and boot process without impacting the shared CI/CD pipeline or requiring the CI/CD team's involvement. You can make quick changes and test boots locally. Option A (creating a new feature branch and asking the CI/CD team to rebuild) does not help you investigate the root cause. Option B (exporting and mounting the disk) is operationally complex and may not reveal build-time issues. Option D (serial port and Cloud Logging) is useful for diagnosing a running instance's boot failure, but since the image itself is the artifact under investigation, rebuilding locally to reproduce and fix the issue is the more actionable approach.

No community discussion yet for this question.