Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Amazon Exam DOP-C01 Topic 9 Question 94 Discussion

Actual exam question for Amazon's DOP-C01 exam
Question #: 94
Topic #: 9
[All DOP-C01 Questions]

A company's legacy application uses IAM user credentials to access resources in the company's AWS Organizations organization. A DevOps engineer needs to ensure new IAM users cannot be created unless the employee creating the IAM user is on an exception list.

Which solution will meet these requirements?

Show Suggested Answer Hide Answer
Suggested Answer: B

Contribute your Thoughts:

Glory
6 months ago
Option C is interesting, but wouldn't it be simpler to just use an SCP to deny the IAM user creation action altogether? Less code to maintain, you know?
upvoted 0 times
...
Casandra
6 months ago
Haha, I'm picturing the non-exception list users trying to create IAM users and just getting a big fat 'DENIED!' Error message. Option B for the win!
upvoted 0 times
...
Rosenda
6 months ago
I agree with Genevive. Option D looks like the most flexible and dynamic solution. Plus, deleting the user if they're not on the exception list is a nice touch.
upvoted 0 times
Clarinda
5 months ago
Yeah, I agree. It seems like the most efficient solution.
upvoted 0 times
...
Myrtie
5 months ago
I think option D is the best choice here.
upvoted 0 times
...
...
Genevive
6 months ago
Hmm, I'm not sure about Option B. Wouldn't it be better to use an EventBridge rule to catch the IAM user creation event and handle it dynamically? That way, we don't have to maintain a static exception list.
upvoted 0 times
Kayleigh
5 months ago
I also think Option C is the way to go. It provides a more flexible solution for handling IAM user creation.
upvoted 0 times
...
Zena
5 months ago
A: Exactly, it would save us time and make the process more efficient.
upvoted 0 times
...
Vanda
5 months ago
B: Yeah, that could be a more dynamic solution. We wouldn't have to manually update the exception list.
upvoted 0 times
...
Yolando
6 months ago
A: I think Option C could work well. Using EventBridge to check against an exception list sounds like a good idea.
upvoted 0 times
...
Otis
6 months ago
I agree, Otis. Option C seems like a more dynamic approach compared to maintaining a static exception list with Option B.
upvoted 0 times
...
Antione
6 months ago
I think Option C might be a good solution. Using EventBridge to check against an exception list sounds efficient.
upvoted 0 times
...
...
Josphine
6 months ago
I disagree, I believe option A is better as it specifically denies the creation of access keys for IAM users not on the exception list.
upvoted 0 times
...
Juliann
6 months ago
Option B seems like the way to go. We need to explicitly deny IAM user creation for non-exception list users, and that's exactly what this option does.
upvoted 0 times
Blythe
5 months ago
I agree, Option B is the most suitable solution for ensuring new IAM users cannot be created unless the employee is on the exception list.
upvoted 0 times
...
Malcom
5 months ago
Definitely, Option B is the way to go to meet the requirements and maintain security in the legacy application.
upvoted 0 times
...
Juliana
5 months ago
Option B is the best choice. It explicitly denies IAM user creation for non-exception list users.
upvoted 0 times
...
Hoa
5 months ago
I agree, Option B is the most secure way to ensure new IAM users cannot be created without being on the exception list.
upvoted 0 times
...
Arlene
5 months ago
Option B is the best choice. It explicitly denies IAM user creation for non-exception list users.
upvoted 0 times
...
Ocie
6 months ago
I agree, we need to deny IAM user creation for non-exception list users.
upvoted 0 times
...
Edmond
6 months ago
I think option B is the best choice here.
upvoted 0 times
...
...
Terry
6 months ago
I think option B is the best solution because it explicitly denies the creation of IAM users unless they are on the exception list.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77