How should the administrator configure Prisma Cloud Compute to satisfy this requirement? Container policy and set the policy effect to alert. the effect to block. set the effect to prevent. to…

Question

Options

• AChoose "copy into rule" for any Container, set www.evil-url.com as a blocklisted DNS name in the Container policy and set the policy effect to alert.
• BSet www.evil-url.com as a blocklisted DNS name in the default Container runtime policy, and set the effect to block.
• CChoose "copy into rule" for any Container, set www.evil-url.com as a blocklisted DNS name, and set the effect to prevent.
• DSet www.evil-url.com as a blocklisted DNS name in the default Container policy and set the effect to prevent.

• A
  2% (1)
• B
  6% (3)
• C
  2% (1)
• D
  89% (42)

Explanation

The correct approach is to add 'www.evil-url.com' as a blocklisted DNS name directly in the default Container runtime policy and set the effect to 'prevent'. The 'prevent' effect actively blocks the DNS resolution at runtime (stopping the container from connecting to the domain), whereas 'alert' (A) only logs the event and 'block' (B) is not a valid Container runtime policy effect for DNS. 'Copy into rule' (A, C) creates a new rule from an existing one and is unnecessary when modifying the default policy directly. Using 'prevent' in the default policy (D) ensures the widest enforcement coverage without additional rule management.

No community discussion yet for this question.