An administrator is having difficulties with an AirWatch Cloud Connector (ACC) server connecting to an AirWatch Cloud Messaging (AWCM) server for authentication. The administrator has confirmed…

Question

Options

• AHost File
• BVAMI configuration
• CWindows Version
• DWindows Registry

• A
  80% (32)
• B
  3% (1)
• C
  10% (4)
• D
  8% (3)

Explanation

Option A (Host File) is correct because the hosts file on the local ACC machine takes precedence over DNS resolution. Even though DNS records are correct and resolvable from a different machine, a stale or incorrect entry in the ACC's local hosts file would cause it to resolve the AWCM server's hostname to the wrong IP address - silently bypassing DNS entirely and breaking authentication.

Option B (VAMI configuration) is wrong because VAMI (VMware Appliance Management Interface) manages virtual appliance settings and has no bearing on hostname resolution for this connectivity issue.

Option C (Windows Version) is wrong because the OS version does not selectively affect name resolution for a single destination; it would cause broader, more generalized network problems rather than this targeted symptom.

Option D (Windows Registry) is wrong because while the Registry contains some network settings, it is not the authoritative location for hostname-to-IP overrides - the hosts file is, and it is the first place to check when a remote target is reachable elsewhere but not locally.

Memory tip: When DNS works everywhere else but not on the problem machine, think "local override" - the hosts file is the classic culprit because it silently overrides DNS only on the machine where it lives.

No community discussion yet for this question.