A customer deployed an application on Compute Engine that takes advantage of the elastic nature of cloud computing. How can you work with Infrastructure Operations Engineers to best ensure that…

Question

Options

• ABuild new base images when patches are available, and use a CI/CD pipeline to rebuild VMs,
• BFederate a Domain Controller into Compute Engine, and roll out weekly patches via Group Policy
• CUse Deployment Manager to provision updated VMs into new serving Instance Groups (IGs).
• DReboot all VMs during the weekly maintenance window and allow the StartUp Script to download

• A
  55% (17)
• B
  6% (2)
• C
  26% (8)
• D
  13% (4)

Explanation

In an elastic cloud environment, the best practice is immutable infrastructure: when a new OS patch is released, build a new golden VM image with the patch applied and use a CI/CD pipeline to roll out new VM instances from that updated image, then decommission old ones. This ensures consistency, auditability, and repeatability. Option B (federating a Domain Controller for Group Policy) brings an on-premises patching approach to the cloud, which adds complexity and is not idiomatic. Option C (Deployment Manager) can provision VMs but is not a patching strategy by itself. Option D (rebooting VMs and relying on a startup script to download patches) is unreliable and not consistent with immutable infrastructure principles - it patches in-place rather than replacing images.

No community discussion yet for this question.