While building an Enterprise profile for city finance laptops, which awareness-level setting must the technician expect to choose that Personal/PSK profiles do not use?
Select an answer to reveal the explanation.
Short Explanation
Enterprise profiles ask which EAP flavor you're speaking—TLS, PEAP, and friends—not just a hallway PSK. Personal stops at the shared passphrase. IBSS and WEP key indexes are not the finance laptop path.
Full Explanation
Building an Enterprise profile for city finance laptops requires selecting an EAP method and related credential or certificate settings for 802.1X. That EAP choice—and the identity or certificate material that accompanies it—is the awareness-level setting Personal/PSK profiles do not use. Personal profiles stop at a shared passphrase; Enterprise profiles must specify how 802.1X will authenticate to municipal RADIUS.
A single shared passphrase in the PSK field is the Personal-mode construct, not the distinguishing Enterprise setting. WEP key index rotation every Beacon interval is legacy WEP behavior unrelated to modern Enterprise profile construction for finance laptops. An IBSS channel list for peer-to-peer printer discovery addresses ad-hoc topology, not 802.1X Enterprise staff WLAN profiles.
Exam caveat: when a question contrasts Personal versus Enterprise client fields, look for EAP method and credentials as the Enterprise-only requirement. Operational check: open the finance laptop Enterprise profile, verify an approved EAP type (for example PEAP or EAP-TLS per city policy), confirm certificate or credential fields are populated, and test authentication against staging RADIUS.