A company manages a multi-tenant environment in its VPC and has configured Amazon GuardDuty for the corresponding AWS account. The company sends all GuardDuty findings to AWS Security Hub.
Traffic from suspicious sources is generating a large number of findings. A DevOps engineer needs to implement a solution to automatically deny traffic across the entire VPC when GuardDuty discovers a new suspicious source.
Which solution will meet these requirements?
Suggested Answer: C
Get Premium DOP-C02 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
16 comments · newest first
CY
Cyril
11 months ago
I’m surprised there’s no direct integration for this!
WI
Willodean
11 months ago
Wait, can Lambda really handle this automatically?
FR
Freeman
11 months ago
A seems a bit complicated for just blocking traffic.
DA
Daniela
11 months ago
I think C is the best choice for a firewall approach.
GL
Glendora
12 months ago
Option B sounds solid for blocking traffic!
BE
Beatriz
12 months ago
I’m leaning towards option B, but I’m a bit uncertain about how the custom rule group would interact with GuardDuty findings.
ER
Erick
1 year ago
I feel like we practiced something similar, but I can't recall if creating a suppression rule in GuardDuty is the right approach here.
TE
Teri
1 year ago
I think option C with AWS Network Firewall sounds familiar. It might be a good way to handle traffic based on GuardDuty findings.
FI
Fidelia
1 year ago
I remember we discussed using AWS WAF for blocking traffic, but I'm not sure if it's the best fit for this scenario.
LA
Lashandra
1 year ago
I'm a bit confused by the different options here. They all seem to involve setting up some kind of automated response to the GuardDuty findings, but the details are a bit murky. I'll need to really dive into the specifics of each approach to figure out which one best meets the requirements.
HU
Hubert
1 year ago
Okay, I think I've got a handle on this. Option B looks like the way to go - using AWS WAF and a custom rule group to automatically block traffic from suspicious sources based on the GuardDuty findings. That seems like the most comprehensive and flexible solution.
CR
Cristy
1 year ago
Hmm, this is a tricky one. I'm not entirely sure which solution would be the best fit. I'll need to make sure I understand the requirements and the capabilities of each of the AWS services mentioned in the options.
DO
Dong
1 year ago
This looks like a straightforward question about implementing a security solution to automatically deny traffic from suspicious sources based on GuardDuty findings. I'll need to carefully review the options and think through the pros and cons of each approach.
JU
Julieta
1 year ago
Ah, I see what they're getting at. The correct answer has to be the one that best captures the essence of integrity.
DA
Davida
1 year ago
Okay, let's see. Continuous delivery, self-organization, value chain thinking, or welcoming change. I'm leaning towards continuous delivery, as that seems to be a key aspect of the DevOps approach. But I'll double-check my notes just to be sure.
ER
Erin
1 year ago
I'm not too confident on this one. The wording is a bit tricky, and I'm not totally clear on how variable costing differs from other cost accounting methods. I'll have to make an educated guess here.