Explanation:
The correct answer is B because the Rolling Update feature allows for controlled updates to a subset of instances, ensuring high availability and the ability to rollback if issues arise. This method is preferred for its automation and minimal manual intervention, aligning with best practices for managing instance groups. Options A, C, and D are less optimal as they either require manual setup, do not directly support rollback functionality, or are not designed for seamless deployment and scaling.
Ultimate access to all questions.
No comments yet.
For an application distributed across a large managed instance group, what is the best method to implement a backup/rollback plan?
A
Schedule a cron job to take snapshots of each instance in the group.
B
Use the Rolling Update feature to deploy/roll back versions with different managed instance group templates.
C
Have each instance write critical application data to a Cloud Storage bucket.
D
Use the managed instance group snapshot function that is included in Compute Engine.