Palo Alto Networks Exam PCSAE Topic 1 Question 69 Discussion

Actual exam question for Palo Alto Networks's PCSAE exam

Question #: 69
Topic #: 1

An administrator has noticed that an incident fetch has failed, causing several internal workflows to be backed up. The administrator would like to receive notifications the next time the incident fetch fails.

How can they achieve this?

ACreate a custom playbook that sends an email each time the fetch fails.

BCreate a new integration that monitors the incident fetch and sends an email if the fetch fails.

CSchedule a job that runs and monitors incidents in XSOAR that will send an email if there are no new incidents.

DAdd a server config to notify when incident fetch fails.

Show Suggested Answer

Suggested Answer: B

by Malcolm at Apr 14, 2024, 11:28 PM

Limited Time Offer

25%

Off

Get Premium PCSAE Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Julio

29 days ago

Option E: Hire a team of carrier pigeons to manually deliver incident reports. Guaranteed to never fail, as long as the pigeons don't get distracted by breadcrumbs along the way.

upvoted 0 times

Nenita

8 days ago

D) Add a server config to notify when incident fetch fails.

upvoted 0 times

...

Pearlene

9 days ago

C) Schedule a job that runs and monitors incidents in XSOAR that will send an email if there are no new incidents.

upvoted 0 times

...

Dylan

14 days ago

B) Create a new integration that monitors the incident fetch and sends an email if the fetch fails.

upvoted 0 times

...

Lashaun

15 days ago

A) Create a custom playbook that sends an email each time the fetch fails.

upvoted 0 times

...

Carin

1 months ago

Hmm, Option A with the custom playbook sounds interesting. I'm always up for a bit of coding and customization. Although, I hope the playbook doesn't end up being more complex than the problem itself!

upvoted 0 times

...

Kayleigh

2 months ago

Option C is a bit overkill, don't you think? Scheduling a job to monitor incidents just to catch a failed fetch seems like a lot of work. I'd rather go with something more straightforward like Option B.

upvoted 0 times

Emmanuel

15 days ago

Yeah, Option C does seem like a lot of work compared to the other options. Option B is definitely more straightforward.

upvoted 0 times

...

Izetta

1 months ago

Creating a new integration to monitor the incident fetch and send an email if it fails sounds efficient.

upvoted 0 times

...

Kaitlyn

1 months ago

I agree, Option B seems like a more direct solution to the problem.

upvoted 0 times

...

Cassandra

2 months ago

I think Option D is the simplest solution. Just adding a server config to notify when the incident fetch fails seems like the easiest way to get the job done. Why complicate things with a custom playbook or integration?

upvoted 0 times

...

Stefania

2 months ago

Option B is the way to go. Creating a new integration to monitor the incident fetch is the most robust and flexible solution. I can customize the notifications and integration to fit our specific needs.

upvoted 0 times

Bettye

13 days ago

Let's go ahead and create the new integration to monitor the incident fetch and send notifications when needed.

upvoted 0 times

...

Devon

23 days ago

That sounds like a good plan. We should set up the new integration as soon as possible.

upvoted 0 times

...

Marylyn

1 months ago

I agree, with a new integration, we can customize the notifications to fit our specific needs.

upvoted 0 times

...

Rolland

2 months ago

Option B is the way to go. Creating a new integration to monitor the incident fetch is the most robust and flexible solution.

upvoted 0 times

...

Mari

2 months ago

I prefer option B, creating a new integration specifically for monitoring the incident fetch.

upvoted 0 times

...

Junita

2 months ago

I agree with Tommy, creating a custom playbook seems like the most direct way to get notifications.

upvoted 0 times

...

Tommy

3 months ago

I think option A sounds like a good solution.

upvoted 0 times

...