ACME Corporation employees access critical business web applications through CyberArk Identity. You notice a constant high volume of unauthorized traffic from 103.1.200.0/24 trying to gain access to…

Question

Options

• ALogin to in to the CyberArk Identity Admin portal and define the IP range of 103 1 200 0/24 into the ACME Corporation IP range.
• BLog in to the CyberArk Identity Admin portal and define the IP range of 103 1 200 0/24 into the blocked IP range.
• CImplement device trust through the Windows Cloud Agent.
• DImplement zero trust through the App Gateway.

• A
  3% (2)
• B
  93% (57)
• C
  2% (1)
• D
  2% (1)

Explanation

Blocking the malicious subnet 103.1.200.0/24 by adding it to the blocked IP range in CyberArk Identity directly addresses the unauthorized traffic - any request from that range is rejected before authentication is even attempted, immediately reducing the attack surface without impacting legitimate users.

Why the distractors are wrong:

• A is the opposite of what's needed: adding 103.1.200.0/24 to the allowed/corporate IP range would grant that malicious subnet access, not restrict it.
• C (Windows Cloud Agent / device trust) validates whether a device is managed/compliant - it doesn't block traffic by IP source, so the unwanted subnet could still attempt access.
• D (App Gateway / zero trust) is an architectural control for securing app access, not a targeted IP block mechanism for the Identity portal itself.

Memory tip: Think of it as a bouncer list - blocked IP range = deny list. The attacker's subnet goes on the deny list. Adding it to the corporate range (A) would be like putting the attacker on the VIP guest list instead.

No community discussion yet for this question.