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

Cisco Exam 300-730 Topic 6 Question 83 Discussion

Actual exam question for Cisco's 300-730 exam
Question #: 83
Topic #: 6
[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 Nickolas at Apr 09, 2024, 01:33 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel
Verlene
4 months ago
I think D) Define the path to the individual webpage that uses HTTPS may also be a valid configuration.
upvoted 0 times
...
Kelvin
4 months ago
I agree with using the website certificate common name makes more sense.
upvoted 0 times
...
Tamar
4 months ago
I disagree, I believe the answer is B) Use the FQDN including the subdomain for the website.
upvoted 0 times
...
Van
4 months ago
I think the correct answer is C) Use the subject common name from the website certificate.
upvoted 0 times
...
Armando
4 months ago
I think D) Define the path to the individual webpage that uses HTTPS may also be a valid configuration.
upvoted 0 times
...
Chaya
4 months ago
I agree with Lavonna, using the website certificate common name makes more sense.
upvoted 0 times
...
Theresia
5 months ago
I disagree, I believe the answer is B) Use the FQDN including the subdomain for the website.
upvoted 0 times
...
Lavonna
5 months ago
I think the correct answer is C) Use the subject common name from the website certificate.
upvoted 0 times
...
Elli
6 months ago
You guys are overthinking this. Just put 'HTTPS' in the protocol field and call it a day. Easy peasy!
upvoted 0 times
...
Huey
6 months ago
Ah, I see what you're saying. But wouldn't that only work if you're trying to match a specific webpage? If you want to match all HTTPS traffic for the site, I think the FQDN is still the way to go.
upvoted 0 times
...
Chana
6 months ago
You make a good point, but I'm not convinced. What if the website has multiple subdomains or a wildcard certificate? I think using the subject common name from the website certificate would be more reliable.
upvoted 0 times
...
Nu
6 months ago
Hmm, I'm not so sure about that. I was leaning towards D) Define the path to the individual webpage that uses HTTPS. That seems like it would be the most specific way to target the HTTPS traffic.
upvoted 0 times
...
Gearldine
6 months ago
I'm not sure about that. Wouldn't the FQDN, including the subdomain, be a better way to match the HTTPS traffic? I mean, that's how the website is actually addressed, right?
upvoted 0 times
...
Elouise
6 months ago
Hmm, this is an interesting one. I think the key here is to specify the protocol to match HTTPS traffic. So, I'd go with option A.
upvoted 0 times
...
Eden
6 months ago
Nah, I don't think that's right. I'd go with C) Use the subject common name from the website certificate. That way, it would match the specific certificate being used for the HTTPS traffic.
upvoted 0 times
...
Francoise
6 months ago
Really? I was thinking B) Use the FQDN including the subdomain for the website. That way, it would match the entire domain, including any subdomains that use HTTPS.
upvoted 0 times
...
Harley
6 months ago
I think the answer is A) Specify the protocol to match (HTTP or HTTPS). That seems like the most straightforward way to ensure the object matches HTTPS traffic.
upvoted 0 times
Elvera
5 months ago
I think specifying the protocol is the way to go. It covers all HTTPS traffic.
upvoted 0 times
...
Kenia
5 months ago
But what about using the subject common name from the website certificate? Wouldn't that be more specific?
upvoted 0 times
...
Kendra
5 months ago
Yes, I agree. Choosing the protocol seems like the most direct method.
upvoted 0 times
...
Jenelle
5 months ago
Exactly, specifying the protocol is crucial for accurate traffic matching.
upvoted 0 times
...
Juliana
5 months ago
That makes sense. It's important to specify the protocol to ensure it matches the right traffic.
upvoted 0 times
...
Norah
5 months ago
Yes, A) Specify the protocol to match would be the correct answer for matching HTTPS traffic.
upvoted 0 times
...
Jerilyn
5 months ago
D) Define the path to the individual webpage that uses HTTPS.
upvoted 0 times
...
Murray
5 months ago
C) Use the subject common name from the website certificate.
upvoted 0 times
...
Refugia
5 months ago
B) Use the FQDN including the subdomain for the website.
upvoted 0 times
...
Essie
5 months ago
A) Specify the protocol to match (HTTP or HTTPS).
upvoted 0 times
...
...
Tashia
6 months ago
Hmm, this question seems a bit tricky. I'm not sure if I fully understand how to configure the URL object for HTTPS traffic on Cisco FMC.
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