117-202 · Question #303
Which Squid configuration keyword is used to define networks and times that the service may be accessed?
The correct answer is A. acl. Exam Questions, Study Guides, Practice Tests. Lead the way to help you pass any IT Certification exams, 100% Pass Guaranteed or Full Refund. Especially Cisco, CompTIA, Citrix, EMC, HP, Oracle, VMware, Juniper, Check Point, LPI, Nortel, EXIN and so on. Our Slogan: First Test…
Question
Options
- Aacl
- Ballow
- Chttp_allow
- Dpermit
How the community answered
(28 responses)- A86% (24)
- B4% (1)
- C7% (2)
- D4% (1)
Explanation
Exam Questions, Study Guides, Practice Tests. Lead the way to help you pass any IT Certification exams, 100% Pass Guaranteed or Full Refund. Especially Cisco, CompTIA, Citrix, EMC, HP, Oracle, VMware, Juniper, Check Point, LPI, Nortel, EXIN and so on. Our Slogan: First Test, First Pass. Help you to pass any IT Certification exams at the first try. You can reach us at any of the email addresses listed below. Any problems about IT certification or our products, you could rely upon us, we will give you satisfactory answers in 24 hours.
Topics
Community Discussion
9The answer is A, acl. The acl directive is how Squid defines named lists of networks, IP ranges, hostnames, times, and other criteria, and you then reference those ACL names in http_access allow or deny rules to actually control who gets through and when.
A is right. In Squid, "acl" is the keyword you use to define access control lists, which is how you declare things like source networks, destination domains, and time ranges. You then reference those ACL names in "http_access allow" or "http_access deny" rules to actually enforce them. The other options are not valid Squid directives, "allow" and "permit" are concepts from other tools like iptables or Cisco ACLs, and "http_allow" does not exist in Squid at all.
Good breakdown, and worth adding that the order of your http_access rules matters a lot in Squid since it processes them top to bottom and stops at the first match, so a broad deny placed above a specific allow will silently block traffic you actually intended to permit.
Right, acl is the keyword, it defines the objects that http_access rules then act on.
That clicked for me too, and I'd just add that the order of your http_access lines matters a lot, because Squid stops at the first one that matches and applies that allow or deny right there.
I actually looked at "allow" first because it sounds like what you would use to grant access, but then I remembered that "allow" is only half of it, you use it in an http_access rule after you define the network or time with acl. The acl keyword is what actually names and defines the thing, whether it is a network range, a time period, or a domain list, and without it the allow or deny has nothing to reference.
Nina nailed the separation of concerns there, the only thing I would add is that acl lines are purely declarative and order-independent among themselves, while the http_access lines that reference them are evaluated top-to-bottom and the first match wins, so the sequence of your allow and deny rules matters enormously even when your acl definitions are perfectly correct.
Honestly I keep coming back to B, allow, because that's literally the word you type when you're telling Squid to let traffic through, and it just makes logical sense that the keyword defining who gets access would be named after the action of allowing access. I've seen so many configs where allow is right there front and center doing the work, so I'm locking in B on this one and I feel pretty good about it going into test day.
Imani, the answer is A, src, because access control lists in Squid are defined in two separate steps, first you declare who with acl using the src type to match source IP ranges, then you permit or deny them with http_access allow or deny, so src is the keyword that actually identifies the clients, not the action taken on them.