This selects whether the 802.1X RADIUS client contacts its configured authentication servers strictly in priority order or spreads requests across them via load balancing. Switching from priority to loadBalance changes which field (the per-server priority value) actually governs traffic, so an admin who only tunes priority values while this is set to loadBalance won't see the ordering behavior they expect. For example, a campus with one primary and one backup RADIUS server would normally leave this at priority(1) so the backup is only used when the primary times out, rather than loadBalance(2) which would send some fraction of requests to the backup even while the primary is healthy.