Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

VMware Exam 5V0-62.22 Topic 3 Question 31 Discussion

Actual exam question for VMware's 5V0-62.22 exam
Question #: 31
Topic #: 3
[All 5V0-62.22 Questions]

An administrator has mistakenly selected the prevent re-enrollment option when enterprise wiping a device that was intended to be re-enrolled. The administrator needs to remove this block and ensure that users are successful when they re-attempt enrollment

Which console page should be used to meet these goals?

Show Suggested Answer Hide Answer
Suggested Answer: B

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.


Contribute your Thoughts:

Wipe Log? Seriously? That's like asking a plumber to fix your TV. This is an enrollment issue, people, and the answer is right there in option A.
upvoted 0 times
...
Stephaine
7 days ago
Haha, Device Updates? What is this, a software update party? Nah, man, this is all about getting that enrollment back on track. Gotta be option A.
upvoted 0 times
...
Milly
11 days ago
I'm not sure, but I think Devices > Wipe Log could also be a potential option to consider for resolving this issue.
upvoted 0 times
...
Jettie
14 days ago
I agree with Jean. That option seems to be the most relevant for removing the prevent re-enrollment block.
upvoted 0 times
...
Jean
17 days ago
I think the correct console page is Devices > Lifecycle > Enrollment Status.
upvoted 0 times
...
Matt
18 days ago
Option B? Really? Device Events? That's for, you know, actual events, not fixing admin boo-boos. C'mon, this is clearly an Enrollment Status kind of situation.
upvoted 0 times
...
Karl
19 days ago
Ah, I think option A is the one we're looking for. The Enrollment Status page should let us remove that pesky 'prevent re-enrollment' block and get those users back on track.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77