5V0-62.22 · Question #49
After introducing an additional AWCM server (for a total of two), enrollments have periodically started to fail. While testing, the administrator notices that when https//awcm.awmdm…
The correct answer is B. AWCM Persistence is not correctly configured. The misconfiguration that would be causing this behavior is AWCM Persistence is not correctly configured. AWCM Persistence is a setting that ensures that devices maintain a consistent connection with the same AWCM server in a load-balanced environment. If AWCM Persistence is…
Question
After introducing an additional AWCM server (for a total of two), enrollments have periodically started to fail. While testing, the administrator notices that when https//awcm.awmdm com;2001/awcm/statistics?awcmsessionid-12345 is accessed, the user is consistently bounced between both AWCM nodes Which misconfiguration would be causing this behavior?
Options
- AAWCM offloading is not property configured.
- BAWCM Persistence is not correctly configured.
- CWCM secure channel certificate is not installed.
- DAWCM ports are not opened to the new AWCM server.
How the community answered
(17 responses)- A18% (3)
- B47% (8)
- C6% (1)
- D29% (5)
Explanation
The misconfiguration that would be causing this behavior is AWCM Persistence is not correctly configured. AWCM Persistence is a setting that ensures that devices maintain a consistent connection with the same AWCM server in a load-balanced environment. If AWCM Persistence is not correctly configured, devices may be bounced between different AWCM servers and cause enrollment failures or communication errors. The administrator should check and configure AWCM Persistence properly.
Topics
Community Discussion
No community discussion yet for this question.