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

ServiceNow CIS-Discovery Exam - Topic 9 Question 74 Discussion

During the Port Scan phase what could the Warning level error "No results returned from probe." mean?
B) Logical or physical firewall preventing connectivity
A) Process Classifier incorrectly configured
C) Wrong credentials
D) Incorrect Datasource Precedence

ServiceNow CIS-Discovery Exam - Topic 9 Question 74 Discussion

Actual exam question for ServiceNow's CIS-Discovery exam
Question #: 74
Topic #: 9
[All CIS-Discovery Questions]

During the Port Scan phase what could the Warning level error "No results returned from probe." mean?

Show Suggested Answer Hide Answer
Suggested Answer: B

During the Port Scan phase in ServiceNow Discovery, the warning level error 'No results returned from probe' typically indicates a connectivity issue. This error often arises when a logical or physical firewall is blocking the connectivity between the MID Server and the target device. This prevents the probe from successfully scanning the ports and returning results. The other options, such as incorrect process classifier configuration, wrong credentials, or incorrect datasource precedence, would generally lead to different types of errors or issues in the discovery process. Reference = ServiceNow Discovery documentation, particularly the sections that deal with troubleshooting Port Scan issues and understanding common errors during Discovery phases.


Contribute your Thoughts:

0/2000 characters
Nan
8 months ago
Nah, I doubt it's the datasource precedence causing this.
upvoted 0 times
...
Charlette
8 months ago
Surprised that firewall settings can lead to no results!
upvoted 0 times
...
Lili
8 months ago
Definitely wrong credentials could cause that too.
upvoted 0 times
...
Ashlee
9 months ago
I think it's more about the process classifier being off.
upvoted 0 times
...
Karl
9 months ago
Could be a firewall issue blocking the probe.
upvoted 0 times
...
Portia
9 months ago
I'm torn between A and D; I recall something about datasource precedence affecting results, but I can't remember the specifics.
upvoted 0 times
...
Katie
9 months ago
I feel like I've seen a question similar to this before, and I think it was about firewall settings too, so B could be the right choice.
upvoted 0 times
...
King
9 months ago
I think "No results returned from probe" might relate to configuration issues, like option A, but I need to double-check my notes.
upvoted 0 times
...
Marshall
10 months ago
I remember studying that a firewall could block probes, so option B seems likely, but I'm not entirely sure.
upvoted 0 times
...
Kattie
10 months ago
This is a tricky one. I'm going to have to draw on my knowledge of port scanning and network troubleshooting to figure this out. I'll carefully consider each option and try to identify the most likely cause of the warning.
upvoted 0 times
...
Gail
10 months ago
Okay, I've got a strategy here. I'll eliminate the options that don't seem directly related to the port scan warning, like the wrong credentials. Then I'll focus on the more technical possibilities like the firewall or data source precedence.
upvoted 0 times
...
Jesus
10 months ago
Hmm, I'm not totally sure about this one. The options seem a bit technical, but I'll try to reason through it. Maybe it's a configuration issue or a firewall blocking the connection?
upvoted 0 times
...
Whitley
10 months ago
This seems like a straightforward question about port scanning. I'll carefully read through the options and think about what could cause a "No results returned from probe" warning.
upvoted 0 times
...
Louann
2 years ago
I think it might be a combination of both wrong credentials and incorrect Datasource Precedence.
upvoted 0 times
...
Bettye
2 years ago
I'm just going to close my eyes and point. This whole thing is a mystery to me anyway. Maybe I'll get lucky and hit the right answer.
upvoted 0 times
...
Salley
2 years ago
I believe it could also be due to incorrect Datasource Precedence.
upvoted 0 times
...
Rodolfo
2 years ago
I'm feeling pretty confident about C - wrong credentials. I mean, who hasn't forgotten their password at least once, am I right folks?
upvoted 0 times
Val
1 year ago
User 3: Maybe it's a combination of both B and C, firewall issues and wrong credentials could both be causing the error.
upvoted 0 times
...
Altha
1 year ago
User 2: I agree, it's important to check all possibilities before jumping to a conclusion.
upvoted 0 times
...
Katina
2 years ago
User 1: I think it could also be B - firewall issues can definitely cause that error.
upvoted 0 times
...
...
Nana
2 years ago
D has to be the answer. Incorrect Datasource Precedence is always the culprit, no matter what the problem is. Trust me, I'm an expert (in my own mind).
upvoted 0 times
Brendan
2 years ago
Incorrect Datasource Precedence is a common issue during Port Scan phase.
upvoted 0 times
...
Beckie
2 years ago
D) Incorrect Datasource Precedence
upvoted 0 times
...
Bettye
2 years ago
C) Wrong credentials
upvoted 0 times
...
Weldon
2 years ago
B) Logical or physical firewall preventing connectivity
upvoted 0 times
...
Freeman
2 years ago
A) Process Classifier incorrectly configured
upvoted 0 times
...
...
Marla
2 years ago
I agree with Merilyn, it's likely wrong credentials.
upvoted 0 times
...
Gerald
2 years ago
I'm going with A - the Process Classifier is probably not configured correctly. Who even sets these things up anyway?
upvoted 0 times
...
Merilyn
2 years ago
I think it could mean wrong credentials.
upvoted 0 times
...
Rosio
2 years ago
Hmm, I think it's B - a logical or physical firewall is preventing connectivity. Gotta love those pesky firewalls, am I right?
upvoted 0 times
Nathalie
2 years ago
Definitely, they can cause a lot of issues during scans.
upvoted 0 times
...
Melodie
2 years ago
Yeah, firewalls can be a pain sometimes.
upvoted 0 times
...
Ammie
2 years ago
I agree, but I lean towards B) Logical or physical firewall preventing connectivity.
upvoted 0 times
...
Francine
2 years ago
I think it could be A) Process Classifier incorrectly configured.
upvoted 0 times
...
...

Save Cancel