What are the main differences between creating a macro and an access policy in VPE? (Select all that apply)

Question

Options

• AMacros are used for load balancing settings, while access policies handle authentication.
• BMacros are used to combine multiple VPE objects for reuse, while access policies enforce security
• CMacros are used for customizing the logon page, while access policies control resource access.
• DMacros are used to configure variable assignments, while access policies define ACL rules.

• A
  4% (2)
• B
  89% (50)
• C
  7% (4)

Explanation

In F5 BIG-IP's Visual Policy Editor (APM), macros are modular, reusable sub-routines - they bundle multiple VPE actions (like variable assignments, auth checks, etc.) into a single callable block that can be inserted into many policies without duplication. Access policies are the top-level enforcement layer that defines the full authentication/authorization flow, including ACL rules that determine what resources a session can reach. This makes B correct (macros = reusable object bundles; policies = security enforcement) and D correct because variable assignment actions are a common macro use case, while ACL rules live in access policies to gate resource access.

Why the distractors fail:

• A is wrong because load balancing belongs to LTM (Local Traffic Manager), not VPE macros at all.
• C is wrong because logon page customization is handled through APM's Customization editor, not macros - and access policies govern far more than just resource access.

Memory tip: Think of a macro as a function in code - you write it once and call it anywhere. The access policy is the main program that runs it and ultimately decides: "Can this user go through?" If a concept sounds like it belongs in LTM (load balancing) or a UI editor (logon pages), it's almost certainly a distractor.

No community discussion yet for this question.