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

Palo Alto Networks Exam PCNSA Topic 1 Question 83 Discussion

Actual exam question for Palo Alto Networks's PCNSA exam
Question #: 83
Topic #: 1
[All PCNSA Questions]

Which Security profile would you apply to identify infected hosts on the protected network using DNS traffic?

Show Suggested Answer Hide Answer
Suggested Answer: A

The show system fqdn command displays the FQDN objects configured on the firewall and their resolved IP addresses. This can help confirm if the FQDN objects are resolved correctly and if they match the expected traffic. A shadow rule is a rule that is never matched because a preceding rule covers the same traffic. If a shadow rule uses FQDN objects, it is possible that the FQDN objects are not resolved or have different IP addresses than the traffic, causing the rule to be ineffective.


Contribute your Thoughts:

Ivette
16 hours ago
D) antivirus, hands down. Gotta keep those viruses at bay and my network squeaky clean!
upvoted 0 times
...
Kimberely
2 days ago
C) anti-spyware, all the way! Can't have those sneaky spies snooping around my network.
upvoted 0 times
...
Omega
4 days ago
Definitely going with B) vulnerability protection. Gotta stop those pesky vulnerabilities in their tracks!
upvoted 0 times
...
Jenifer
12 days ago
Hmm, using DNS traffic to identify infected hosts? Sounds like a job for the 'DNS Whisperer' security profile.
upvoted 0 times
...
Andra
1 months ago
I'm not sure, but I think C) anti-spyware could also be a good option for this.
upvoted 0 times
...
Rosendo
1 months ago
I agree with Kara, antivirus makes sense for identifying infected hosts.
upvoted 0 times
...
Kara
1 months ago
I think the answer is D) antivirus.
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