102-500 · Question #28
The X11 configuration file xorg.conf is grouped into section. How is the content of the section represented? SectionName
The correct answer is C. It is placed between a line containing Section "SectionName" and a line containing EndSection. Option C is correct because xorg.conf uses a block syntax where each section opens with Section "SectionName" on its own line and closes with EndSection - for example, Section "Device" ... EndSection. This is the actual format used by the X.Org Server configuration file, and…
Question
Options
- AIt is placed in curly brackets as in Section SectionName {...}.
- BIt is placed between the tags <Section name="SectionName"> and </Section>.
- CIt is placed between a line containing Section "SectionName" and a line containing EndSection.
- DIt is placed after the row [SectionName].
- EIt is placed after an initial unindented Section "SectionName" and must be indented by exactly
How the community answered
(49 responses)- A14% (7)
- B8% (4)
- C71% (35)
- D2% (1)
- E4% (2)
Explanation
Option C is correct because xorg.conf uses a block syntax where each section opens with Section "SectionName" on its own line and closes with EndSection - for example, Section "Device" ... EndSection. This is the actual format used by the X.Org Server configuration file, and it's consistent across all section types (Monitor, Screen, InputDevice, etc.).
Why the distractors are wrong:
- A - Curly brackets
{}are used in languages like C or CSS, not xorg.conf. - B - XML-style tags (
<Section>) belong to markup languages; xorg.conf predates and does not use XML. - D - Square bracket headers like
[SectionName]are the INI file format (used by systemd units, Windows.inifiles, etc.), not xorg.conf. - E - While indentation is conventional inside sections, it is not required by the parser; the section boundary is defined by the
Section/EndSectionkeywords, not by indentation.
Memory tip: Think of xorg.conf sections like a book with chapters - Section "Name" is the chapter title and EndSection is the chapter's closing page. The keyword pair wraps the content, making C the only option that describes an opening and a closing boundary.
Topics
Community Discussion
No community discussion yet for this question.