A company recently set up Amazon GuardDuty and is receiving a high number of findings from IP addresses within the company. A security engineer has verified that these IP addresses are trusted and…

Question

Options

• ACreate a plaintext configuration file that contains the trusted IP addresses.
• BCreate a JSON configuration file that contains the trusted IP addresses.
• CUpload the configuration file directly to GuardDuty.
• DUpload the configuration file to Amazon S3. Add a new trusted IP list to GuardDuty that points to
• EManually copy and paste the configuration file data into the trusted IP list in GuardDuty.

• A
  16% (5)
• B
  3% (1)
• C
  6% (2)
• D
  75% (24)

Explanation

Important note: The stated correct answer of D and E appears to be an error in this question. Based on AWS documentation, the actual correct answers are A and D.

Amazon GuardDuty's trusted IP list feature requires a plaintext (.txt) file - one IP address or CIDR range per line - making A correct. That file must then be uploaded to an S3 bucket, and GuardDuty is configured with a trusted IP list that points to that S3 object URL, making D correct.

Why the other options are wrong:

• B is wrong because GuardDuty does not accept JSON format for trusted IP lists - only plaintext.
• C is wrong because GuardDuty has no direct file upload mechanism; the file must reside in S3 and be referenced by URL.
• E is wrong because GuardDuty has no "paste IP addresses" UI field - the only supported workflow is via an S3-hosted file.

Memory tip: Think of it as a two-step process - "Make a list, store it in S3". GuardDuty is read-only from S3; it never accepts files directly or inline data. If a question option skips the S3 step or uses a non-plaintext format, eliminate it.

No community discussion yet for this question.