ACCESS-DEF · Question #20
Your team is deploying endpoint authentication onto the corporate endpoints within an organization. Enrollment details include when the enrollment must be completed, and the enrollment code was sent…
The correct answer is A. Set maximum number of joinable endpoints to "unlimited". Option A is correct because enrollment codes in endpoint authentication systems often have a configurable cap on how many devices can use them - once that limit is hit, additional users attempting to enroll will simply be rejected. Setting the maximum joinable endpoints to…
Question
Options
- ASet maximum number of joinable endpoints to "unlimited".
- BSet Expiry Date to "Never".
- CSet the IP Address range to the user's home network range.
- DSet a description within the enrollment code.
- EReinstall Windows Device Trust.
How the community answered
(28 responses)- A71% (20)
- B18% (5)
- D7% (2)
- E4% (1)
Explanation
Option A is correct because enrollment codes in endpoint authentication systems often have a configurable cap on how many devices can use them - once that limit is hit, additional users attempting to enroll will simply be rejected. Setting the maximum joinable endpoints to "unlimited" removes this ceiling and allows all remaining users to complete enrollment successfully.
Option C is the second likely correct answer in a "choose two" scenario: if enrollment can occur remotely but the code is restricted to a specific IP range (e.g., the office subnet), home users will be blocked. Expanding or removing the IP restriction enables remote enrollment as intended.
Option B (Expiry Date → Never) is a distractor because the scenario tells us the enrollment has a required completion deadline - removing expiry would conflict with that policy and doesn't explain why current users are failing.
Option D (adding a description) is purely cosmetic metadata; it has no effect on whether a device can successfully authenticate or join.
Option E (reinstalling Windows Device Trust) is a last-resort client-side fix for an individual machine, not a scalable solution for many users failing enrollment simultaneously - it treats a symptom, not the root cause.
Memory tip: Think of the enrollment code as a "guest pass" - if it has a guest limit (max endpoints) or venue restriction (IP range), people get turned away at the door. Fix the pass policy, not the individual guests.
Topics
Community Discussion
No community discussion yet for this question.