Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Cisco Exam 300-730 Topic 3 Question 81 Discussion

Actual exam question for Cisco's 300-730 exam
Question #: 81
Topic #: 3
[All 300-730 Questions]

A network administrator wants to block traffic to a known malware site at https:/www.badsite.com and all subdomains while ensuring no packets from any internal client are sent to that site. Which type of policy must the network administrator use to accomplish this goal?

Show Suggested Answer Hide Answer

Contribute your Thoughts:

Murray
6 months ago
So it seems like the best option is indeed B) Prefilter policy for blocking traffic to a known malware site.
upvoted 0 times
...
Deja
6 months ago
That's true, but DNS policy only prevents the DNS resolution of the domain, not the actual traffic to the site.
upvoted 0 times
...
Elizabeth
6 months ago
I think C) DNS policy could also work to block traffic by inspecting and modifying DNS requests.
upvoted 0 times
...
Murray
6 months ago
Hmm, that makes sense. Prefilter policy allows for fast actions on traffic before access control.
upvoted 0 times
...
Deja
6 months ago
Actually, I believe the correct answer is B) Prefilter policy.
upvoted 0 times
...
Murray
6 months ago
I think the answer is A) Access Control policy with URL filtering.
upvoted 0 times
...
Derrick
6 months ago
Prefilter policy does not support URL filtering, so it may not be the best option in this case.
upvoted 0 times
...
Ressie
7 months ago
But what about Prefilter policy? It allows fast actions on traffic before it reaches the Access Control policy.
upvoted 0 times
...
Marvel
7 months ago
I agree with Derrick. Using URL filtering will effectively block access to the known malware site.
upvoted 0 times
...
Derrick
7 months ago
I think the network administrator should use Access Control policy with URL filtering to block traffic to the malware site.
upvoted 0 times
...
Valentine
8 months ago
I'm with you guys. Prefilter policy is the clear winner here. Though, I have to say, I'm a little disappointed that the malware site is called 'badsite.com'. That's just so on the nose, you know?
upvoted 0 times
...
Krissy
8 months ago
You know, I was initially leaning towards the DNS policy option, but then I realized that wouldn't actually prevent the clients from accessing the site if they knew the IP address. Prefilter policy is definitely the way to go.
upvoted 0 times
...
Ellsworth
8 months ago
Yeah, I agree with Charolette. Prefilter policy is the way to go here. It's a lot simpler than trying to use a DNS policy or SSL policy, which wouldn't really address the core issue.
upvoted 0 times
...
Charolette
8 months ago
Hmm, this question seems pretty straightforward. I think the answer is B) Prefilter policy. It allows you to drop traffic based on IP addresses or domains, which is exactly what the network administrator needs to block that malware site.
upvoted 0 times
Bok
7 months ago
Agreed, it's important for network administrators to understand the capabilities of each policy to make the right choice.
upvoted 0 times
...
Daniel
8 months ago
Good point. Prefilter policy is the most suitable option in this scenario.
upvoted 0 times
...
Shannan
8 months ago
And it doesn't support URL filtering, so it's important to choose the right policy for the specific task.
upvoted 0 times
...
Sue
8 months ago
Prefilter policy is like a first line of defense before traffic goes through the Access Control policy.
upvoted 0 times
...
Barrett
8 months ago
Exactly, it's a good way to prevent any packets from internal clients reaching the malicious site.
upvoted 0 times
...
Emeline
8 months ago
That makes sense. Prefilter policy can quickly drop traffic based on simple criteria like IP addresses or domains.
upvoted 0 times
...
Xochitl
8 months ago
I agree, B) Prefilter policy is the right choice for blocking traffic to the known malware site and its subdomains.
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