How can the administrator create a blacklist/allowlist of IPs supplementing IP reputation?

• A. Create a data set for IPv4 address matching
• B. Enable MAC-based Forwarding
• C. Create several simple Access Control List policies
• D. Creating a blocklist or allowlist of IPs using a policy data set by using IP reputation.

Answer: (D)

You implement a blacklist/allowlist that works in harmony with IP reputation by using a policy data set that lists the IPs to block or allow, and then apply that data set in a policy tied to the IP reputation evaluation. The idea is to complement reputation scores with explicit, administrator-defined IP lists. You create a data set containing the IP addresses you want to block or permit, build a policy that checks the source IP against this set, and then define the action (block or allow) based on the match. This lets you override or reinforce reputation signals with precise controls—for example, allow traffic from a known trusted IP even if its reputation score is borderline, or block a high-risk IP despite a neutral reputation.

Why this is the best fit: it directly provides a mechanism to maintain and enforce explicit IP lists while also leveraging IP reputation, giving you both dynamic risk signals and static, administrator-defined controls in a single policy.

Why the other approaches don’t fit as well: enabling MAC-based Forwarding is about layer-2 behavior and doesn’t address IP reputation or IP-based access control. Creating a data set for IPv4 address matching is related but incomplete without a policy that uses IP reputation to decide actions. Creating several simple ACL policies can enforce blocks/allows, but they’re less centralized and harder to maintain compared with a single policy data set that works alongside IP reputation.