Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Amazon SCS-C02 Exam - Topic 7 Question 4 Discussion

A company uses Amazon GuardDuty. The company's security team wants all High severity findings to automatically generate a ticket in a third-party ticketing system through email integration.Which solution will meet this requirement?
B) Create an Amazon Simple Notification Service (Amazon SNS) topic. Subscribe the third-party ticketing email system to the SNS topic. Create an Amazon EventBridge rule that includes an event pattern that matches High severity GuardDuty findings. Specify the SNS topic as the target for the EventBridge rule.
A) Create a verified identity for the third-party ticketing email system in Amazon Simple Email Service (Amazon SES). Create an Amazon EventBridge rule that includes an event pattern that matches High severity GuardDuty findings. Specify the SES identity as the target for the EventBridge rule.
C) Use the GuardDuty CreateFilter API operation to build a filter in GuardDuty to monitor for High severity findings. Export the results of the filter to an Amazon Simple Notification Service (Amazon SNS) topic. Subscribe the third-party ticketing email system to the SNS topic.
D) Use the GuardDuty CreateFilter API operation to build a filter in GuardDuty to monitor for High severity findings. Create an Amazon Simple Notification Service (Amazon SNS) topic. Subscribe the third-party ticketing email system to the SNS topic. Create an Amazon EventBridge rule that includes an event pattern that matches GuardDuty findings that are selected by the filter. Specify the SNS topic as the target for the EventBridge rule.

Amazon SCS-C02 Exam - Topic 7 Question 4 Discussion

Actual exam question for Amazon's SCS-C02 exam
Question #: 4
Topic #: 7
[All SCS-C02 Questions]

A company uses Amazon GuardDuty. The company's security team wants all High severity findings to automatically generate a ticket in a third-party ticketing system through email integration.

Which solution will meet this requirement?

Show Suggested Answer Hide Answer

Contribute your Thoughts:

0/2000 characters
Gilma
6 months ago
I disagree, C might be more efficient in the long run.
upvoted 0 times
...
Craig
7 months ago
Wait, can SES really handle that many emails? Sounds risky.
upvoted 0 times
...
Fausto
7 months ago
Definitely going with B, it’s straightforward!
upvoted 0 times
...
Walton
7 months ago
I think D is overcomplicated for this task.
upvoted 0 times
...
Lashanda
7 months ago
Option B seems like the simplest solution.
upvoted 0 times
...
Yolande
7 months ago
I feel like option A is too simple. It just uses SES directly, and I thought integrating with SNS was a better practice for notifications.
upvoted 0 times
...
Huey
8 months ago
I'm a bit confused about the difference between options B and D. Both mention SNS, but D seems more complex with the filter. Is that really necessary?
upvoted 0 times
...
Ming
8 months ago
I remember practicing a question similar to this, and I feel like using EventBridge with SNS is a common pattern for integrating services. So maybe B is the best choice?
upvoted 0 times
...
Herminia
8 months ago
I think option B sounds right since it mentions using SNS, which is often used for notifications. But I'm not entirely sure if it needs EventBridge too.
upvoted 0 times
...
Lisandra
8 months ago
I'm not too familiar with EventBridge, but I know it's a powerful service for event-driven architectures. I'll need to review the documentation to make sure I understand how to properly configure the event pattern and target.
upvoted 0 times
...
Curtis
8 months ago
Okay, let's see here. The key is to set up an EventBridge rule to capture the High severity GuardDuty findings and route them to the appropriate notification channel. I think option D looks like the most comprehensive solution.
upvoted 0 times
...
Shawana
8 months ago
Hmm, I'm a bit confused about the difference between using SES directly versus using SNS as an intermediary. I'll need to think through the pros and cons of each approach.
upvoted 0 times
...
Delmy
8 months ago
This looks like a straightforward question about integrating GuardDuty with a third-party ticketing system. I think I can handle this one.
upvoted 0 times
...
Ardella
8 months ago
This seems straightforward enough. I'm leaning towards option B - using SNS as the intermediary between GuardDuty and the ticketing system. That way, I can easily scale and add additional subscribers in the future if needed.
upvoted 0 times
...
Julie
8 months ago
I'm a little confused by the wording of the options. They all seem to be talking about the procurement process in some way. I'll have to re-read the question closely and think about which one specifically addresses contract changes.
upvoted 0 times
...
Chantay
8 months ago
Hmm, this seems like a tricky question. I'll need to think through the order carefully to get this right.
upvoted 0 times
...
Richelle
8 months ago
I'm pretty sure the answer is DTLS, since it's a secure protocol commonly used for control connections in SD-WAN.
upvoted 0 times
...

Save Cancel