Free AWS DOP-C02 Actual Exam Questions - Question 6 Discussion

Question No. 6
A security team is concerned that a developer can unintentionally attach an Elastic IP address to an
Amazon EC2 instance in production. No developer should be allowed to attach an Elastic IP address
to an instance. The security team must be notified if any production server has an Elastic IP address
at any time
How can this task be automated'?
Select one option, then reveal solution.
US
NZ
Naveed Z.
2026-02-15

B imo, it combines permission denial with automated compliance checks and alerts.

0
NZ
Naveed Z.
2026-02-09

This is tricky but I’d go with C because it’s about removing permissions from developers completely, and the scheduled Lambda keeps checking for violations regularly. That double check feels safer than just relying on Config alerts. C

0
NZ
Naveed Z.
2026-02-09

D imo, because it adds an extra layer by using IAM roles with deny permissions on production instances themselves, not just the developers' groups. This means even if someone slips through the IAM group policies or uses a different identity, the instance’s role blocks the action. Plus, AWS Config can continuously monitor any Elastic IP association on those instances and send alerts, catching any accidental or unauthorized attachments. It seems more fail-safe than just relying on user-level permissions or scheduled Lambda checks.

0
IO
Irfan O.
2026-02-05

B, it covers prevention and real-time alerts based on production tags.

0
HU
Haris U.
2026-02-04

C imo works well too because it focuses on removing associate-address permissions from developers entirely, which is a straightforward way to prevent Elastic IP attachments. Plus, the scheduled Lambda checking production tags adds a second layer of detection, so even if something slips through, the security team gets notified. It’s a bit more hands-on than B but covers both prevention and alerting without relying solely on IAM policies with potentially complex scopes.

0
OM
Osama M.
2026-01-25

I’m not sure about D because IAM roles on instances don’t control who can attach Elastic IPs, right? Seems like denying permissions directly (like in B) makes more sense for stopping the action itself. Could be missing something?

0
OM
Osama M.
2026-01-17

B tbh makes the most sense since you can directly deny the permission and also have a Config rule for continuous compliance and alerting. Other options either miss one or the other part.

0
OM
Osama M.
2026-01-16

Maybe B

0