An administrator is maintaining a Workspace ONE UEM cloud environment, and needs to secure the AirWatch Cloud Connector (ACC) instances with OS updates. What must the administrator do?

Question

Options

• AUpdate the ACC's servers one after the other.
• BUpdate the ACC's servers in parallel.
• CReinstall the AirWatch Cloud Connector instances.
• DManually reconfigure the loadbalancer fronting the ACC's and the update a ACC.

• A
  3% (1)
• B
  85% (28)
• C
  3% (1)
• D
  9% (3)

Explanation

Updating ACC instances in parallel (B) is correct because Workspace ONE UEM environments are designed with multiple ACC instances behind a load balancer for high availability. When you update in parallel, all instances are taken down and updated simultaneously - the load balancer detects they're unavailable and the SaaS backend queues requests, then resumes once all instances come back online. This avoids the split-brain scenario where instances running different versions coexist and potentially cause inconsistent behavior.

Why the distractors fail:

• A (one after the other): Sequential updates create a version mismatch window where one ACC runs the old OS and one runs the new, which can cause compatibility issues and unpredictable behavior across the ACC cluster.
• C (reinstall): Reinstallation is unnecessary and creates extra downtime; OS patching does not require removing and reconfiguring the ACC software.
• D (reconfigure load balancer first): The load balancer does not need manual reconfiguration - it automatically handles instance availability. Manually reconfiguring it adds unnecessary complexity and risk.

Memory tip: Think "parallel patch, parallel pain-free" - ACC instances are stateless connectors, so simultaneous downtime is safe and brief, whereas staggered updates introduce version drift that breaks cluster consistency.

No community discussion yet for this question.