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 Exam CIS-Discovery 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:

Louann
8 days ago
I think it might be a combination of both wrong credentials and incorrect Datasource Precedence.
upvoted 0 times
...
Bettye
10 days 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
10 days ago
I believe it could also be due to incorrect Datasource Precedence.
upvoted 0 times
...
Rodolfo
11 days 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
...
Nana
21 days 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
Weldon
3 days ago
B) Logical or physical firewall preventing connectivity
upvoted 0 times
...
Freeman
8 days ago
A) Process Classifier incorrectly configured
upvoted 0 times
...
...
Marla
27 days ago
I agree with Merilyn, it's likely wrong credentials.
upvoted 0 times
...
Gerald
28 days 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
30 days ago
I think it could mean wrong credentials.
upvoted 0 times
...
Rosio
1 months 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
Melodie
5 days ago
Yeah, firewalls can be a pain sometimes.
upvoted 0 times
...
Ammie
17 days ago
I agree, but I lean towards B) Logical or physical firewall preventing connectivity.
upvoted 0 times
...
Francine
18 days ago
I think it could be A) Process Classifier incorrectly configured.
upvoted 0 times
...
...

Save Cancel