LX0-104 · Question #185
After an administrator added comments to each line of the ACLs in slapd.conf, the ACLs ceased to function properly. What is the most likely cause of this?
The correct answer is A. Comments cannot be used anywhere in an ACL block.. Adding comments directly within each line of an ACL block in slapd.conf will likely break the ACLs because comments are generally not allowed mid-line within configuration directives in OpenLDAP ACLs.
Question
Options
- AComments cannot be used anywhere in an ACL block.
- BThe comments were not added using the semi-colon (;) character.
- CComments cannot be used in the slapd.conf file.
- DThe comments were not added using the pound (#) character.
How the community answered
(27 responses)- A70% (19)
- B15% (4)
- C11% (3)
- D4% (1)
Why each option
Adding comments directly within each line of an ACL block in `slapd.conf` will likely break the ACLs because comments are generally not allowed mid-line within configuration directives in OpenLDAP ACLs.
OpenLDAP's slapd.conf typically expects ACL rules to be parsed without inline comments, meaning comments placed at the end of a by clause line or within the ACL directive itself will be interpreted as part of the rule, causing syntax errors and preventing the ACLs from functioning.
OpenLDAP slapd.conf uses the pound (#) character for comments, not the semi-colon (;).
Comments can be used in slapd.conf, but their placement is critical; they must be on separate lines or at the beginning of a line, not inline within directive parameters, especially within ACLs.
The pound (#) character is the correct character for comments in slapd.conf; therefore, this statement suggests the administrator used the wrong character, which contradicts the premise that comments were added but broke the ACLs.
Concept tested: OpenLDAP slapd.conf ACL comment syntax
Source: https://www.openldap.org/doc/admin24/slapdconf.html
Topics
Community Discussion
No community discussion yet for this question.