What is the recommended scope for applying access profiles to ensure consistent policy enforcement across multiple virtual servers?

Question

Options

• AProfile scope
• BVirtual server scope
• CGlobal scope
• DTraffic group scope

• A
  7% (2)
• B
  10% (3)
• C
  79% (23)
• D
  3% (1)

Explanation

Global scope (option C) is correct because it enforces a single, unified access policy session across all virtual servers simultaneously - when a user authenticates, that session and its policy decisions apply everywhere, eliminating gaps or inconsistencies that arise from per-server enforcement.

Profile scope (A) is wrong because it limits enforcement to virtual servers sharing that specific profile, meaning different profiles can produce different policy outcomes - inconsistency by design. Virtual server scope (B) is wrong because it isolates each virtual server's session independently, so a user might face different (or no) enforcement depending on which server they hit. Traffic group scope (D) is wrong because traffic groups are a high-availability/failover concept for floating IP addresses, not an access policy enforcement boundary.

Memory tip: Think "Global = Guaranteed consistency." If you need the same rule everywhere, you need the highest level - Global scope reaches all virtual servers at once, the same way a global law applies to everyone rather than just one city.

No community discussion yet for this question.