Examtopics

コメント(8)

• 正解だと思う選択肢: D

  You can eliminate:

  B. Because the MIG needs to be updated immediately, which not what Opportunistic does C. Because max unavailable at 100% will cause downtime

  So that leaves A, and D.

  If you choose A. The MIG will spin up hundreds of new machines, to replace the existing one, and shutdown the old ones. This is the fastest method, but could be costly, or you could run into quota issues.

  If you choose D, the MIG will spin up 3 VMs at a time (maxSurge default to 3), and then it will bring up one at a time, as soon as more surge slots are available, so it wont be really that fast.

  I think D is the most sensible in this case.

  👍 4

  micoams2022/12/18
• 正解だと思う選択肢: B

  B is the answer.

  https://cloud.google.com/compute/docs/instance-groups/rolling-out-updates-to-managed-instance-groups#type Alternatively, if an automated update is potentially too disruptive, you can choose to perform an opportunistic update. The MIG applies an opportunistic update only when you manually initiate the update on selected instances or when new instances are created. New instances can be created when you or another service, such as an autoscaler, resizes the MIG. Compute Engine does not actively initiate requests to apply opportunistic updates on existing instances.

  👍 3

  zellck2022/12/16
• 正解だと思う選択肢: D

  Setting the "Minimum Wait time" to 0 seconds means that there is no delay in launching the new instances after the instance template is updated, allowing you to deploy the fix for the critical vulnerability immediately. On the other hand, setting the "Update mode to Opportunistic" would mean that the new instances are created at an opportune time and may result in a delay in deploying the fix. In this scenario, where a critical vulnerability needs to be fixed immediately, it's important to deploy the fix as soon as possible, making the "Minimum Wait time to 0 seconds" the better approach.

  👍 2

  mrvergara2023/02/03