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
Mail Us support@pass4success.com
Location PL
Mob_nav_barsMENU

Cisco Exam 300-730 Topic 4 Question 95 Discussion

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

An engineer is creating an URL object on Cisco FMC. How must it be configured so that the object will match for HTTPS traffic in an access control policy?

Show Suggested Answer Hide Answer
Suggested Answer: B

Use the FQDN including the subdomain for the website.According to the Firepower Management Center Configuration Guide, Version 6.61, when you create a URL object, you must use the fully qualified domain name (FQDN) of the website, including any subdomains, and omit the protocol prefix (HTTP or HTTPS). For example, to match www.example.com, you must enter www.example.com as the URL object value, not http://www.example.com or https://www.example.com. The system automatically matches both HTTP and HTTPS traffic for the same FQDN. Specifying the protocol to match (HTTP or HTTPS) is not required and will result in an invalid URL object. Using the subject common name from the website certificate or defining the path to the individual webpage that uses HTTPS are not supported options for URL objects.


by Rodney at Sep 14, 2024, 11:37 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel
Virgina
2 months ago
Hmm, I'm torn between A and B. Gotta love the FQDN, but protocol matching is the safest bet in my opinion.
upvoted 0 times
Valene
1 months ago
A) Specify the protocol to match (HTTP or HTTPS).
upvoted 0 times
...
Delmy
2 months ago
I agree, protocol matching is the safest option.
upvoted 0 times
...
Louisa
2 months ago
B) Use the FQDN including the subdomain for the website.
upvoted 0 times
...
Markus
2 months ago
A) Specify the protocol to match (HTTP or HTTPS).
upvoted 0 times
...
...
Theresia
2 months ago
I believe using the subject common name from the website certificate could also be a valid option for matching HTTPS traffic.
upvoted 0 times
...
Renato
2 months ago
Haha, option D is a classic. Defining the path to a specific webpage? That's like trying to catch a fly with chopsticks!
upvoted 0 times
Samira
1 months ago
Luann: Yeah, it would be a lot of work to define paths for every single webpage using HTTPS.
upvoted 0 times
...
Arlette
1 months ago
Option D does seem a bit too specific. It might not be practical in most cases.
upvoted 0 times
...
Luann
2 months ago
I agree, it covers all HTTPS traffic for that website.
upvoted 0 times
...
Ma
2 months ago
Option B seems like the best choice. Using the FQDN including the subdomain is more general.
upvoted 0 times
...
...
Tresa
2 months ago
I think option C is the way to go. Using the subject common name from the website certificate seems like the most reliable approach.
upvoted 0 times
Isreal
2 months ago
C) Use the subject common name from the website certificate.
upvoted 0 times
...
Joana
2 months ago
B) Use the FQDN including the subdomain for the website.
upvoted 0 times
...
Nida
2 months ago
A) Specify the protocol to match (HTTP or HTTPS).
upvoted 0 times
...
...
Alison
3 months ago
I agree with Pearly. Using the protocol to match HTTPS makes sense for matching HTTPS traffic.
upvoted 0 times
...
Sonia
3 months ago
The correct answer is A. Specifying the protocol to match is the key to ensuring the URL object matches HTTPS traffic.
upvoted 0 times
Carman
2 months ago
That makes sense, specifying the protocol is important for matching HTTPS traffic.
upvoted 0 times
...
Terrilyn
3 months ago
I think the answer is A) Specify the protocol to match (HTTP or HTTPS).
upvoted 0 times
...
...
Pearly
3 months ago
I think the URL object should be configured with the protocol to match HTTPS.
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