An administrator configures a new destination list in Cisco Umbrella so that the organization can block specific domains for its devices. What should be done to ensure that all subdomains of domain.com are blocked?
A.
Configure the domain.com address in the block list.
B.
Configure the *.domain.com address in the block list.
C.
Configure the *.com address in the block list.
D.
Configure the *domain.com address in the block list.
it is actually A -> https://docs.umbrella.com/deployment-umbrella/docs/wild-cards
"Every domain in a block or allow destination list has an implied left side and right side wildcard"
ZeroCool is correct. Same link also states:
It is not possible to use an asterisk to wildcard a different part of the domain. The following will not work:
*.domain.com
subdomain.*.com
sub*.com
domain.*
Adding domain.com to an allow list results in requests to domain.com or its subdomains, such as www.domain.com, being allowed. The result is the same for blocklists.
I think it is A.
Always add domains in the format "domain.com" rather than www.domain.com to ensure *.domain.com is included (a wildcard is implicit). However, if you only wish to block subdomain.domain.com, then be more specific when you define the entry here.
Answer B is more accurate
To ensure that all subdomains of domain.com are blocked in Cisco Umbrella, the administrator should configure the *.domain.com address in the block list.
The asterisk (*) is a wildcard character that represents any string of characters, including subdomains. By using the wildcard character in the block list, any subdomain of domain.com will be blocked, including subdomains that do not exist yet.
If the administrator only configures the domain.com address in the block list, it will only block traffic to the root domain and not to any of its subdomains. Similarly, configuring the *.com address in the block list will block all traffic to any domain that ends with .com, not just domain.com and its subdomains. Configuring the *domain.com address in the block list will not have any effect, as it does not follow the correct syntax for blocking subdomains.
"Adding domain.com to an allow list results in requests to domain.com or its subdomains, such as www.domain.com, being allowed. The result is the same for blocklists."
A
What you cannot add to a destination list
1. You cannot add wildcards. A wildcard is implicit in the way DNS is structured, so adding a domain covers all of the subdomains and there is no reason to add *.domain.com to cover this.
https://support.umbrella.com/hc/en-us/articles/115006964927-Understanding-Destination-lists-supported-entries-and-error-messages
This section is not available anymore. Please use the main Exam Page.350-701 Exam Questions
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
zeroC00L
Highly Voted 3 years, 1 month agoaaInman
3 years, 1 month ago14LearningStuff
Highly Voted 3 years, 2 months agoPakawat
Most Recent 10 months, 4 weeks agoloser4fun
1 year, 7 months agoDorr20
1 year, 7 months agoiratus_umbra
1 year, 7 months agoEmlia1
1 year, 11 months agoureis
2 years agoJamesy
2 years, 1 month agomadcloud
2 years, 5 months agojaciro11
3 years agoMoII
2 years, 11 months agojohn_thomas
3 years agoSarbi
3 years, 2 months ago