LPI 102-500 Practice Test 11
Question 100
During an LPIC-1 practice lab, the operator encounters this condition: An operator pipes a filename list into a while read loop and expects variables changed inside a subshell to be available afterwards. Which THREE elements together give the appropriate corrective action, direct diagnostic evidence and observable acceptance result? Select THREE answers.
- Feed literal backslashes and spaced lines through a test input, compare the resulting strings, and inspect whether a pipeline created a subshell.
- Test against filenames with spaces and glob characters, inspect quoted expansions and use a shell-safe enumeration in a throwaway directory.
- Use IFS= read -r within an appropriately redirected loop to preserve literal input and design variable state without relying on a pipeline subshell.
- Each input record retains intended characters and the final aggregation is available in the process where it is needed.
- Maintain approved default dotfiles and directory templates under /etc/skel and use the appropriate account-creation option to populate new home directories.
- Assume ordinary `read` always preserves backslashes and whitespace and that variables modified in any piped loop persist in the parent shell.
Explanation
Correct Answers
A:Most direct verification evidence: Feed literal backslashes and spaced lines through a test input, compare the resulting strings, and inspect whether a pipeline created a subshell. Linux principle: read -r avoids backslash escape processing, an empty IFS can preserve leading and trailing whitespace, and shell pipeline subshells may isolate assignments.
C:Recommended administrative action: Use IFS= read -r within an appropriately redirected loop to preserve literal input and design variable state without relying on a pipeline subshell. Linux principle: read -r avoids backslash escape processing, an empty IFS can preserve leading and trailing whitespace, and shell pipeline subshells may isolate assignments.
D:Observable acceptance criterion: Each input record retains intended characters and the final aggregation is available in the process where it is needed. Linux principle: read -r avoids backslash escape processing, an empty IFS can preserve leading and trailing whitespace, and shell pipeline subshells may isolate assignments.
Incorrect Answers
B:This alternative addresses Quoting expansions in file-processing loops, not the specific issue of Reading input line by line and preserving backslashes: Test against filenames with spaces and glob characters, inspect quoted expansions and use a shell-safe enumeration in a throwaway directory. Linux principle: read -r avoids backslash escape processing, an empty IFS can preserve leading and trailing whitespace, and shell pipeline subshells may isolate assignments. Appropriate response: Use IFS= read -r within an appropriately redirected loop to preserve literal input and design variable state without relying on a pipeline subshell. Root-cause evidence: Feed literal backslashes and spaced lines through a test input, compare the resulting strings, and inspect whether a pipeline created a subshell. Independent acceptance: Each input record retains intended characters and the final aggregation is available in the process where it is needed.
E:This alternative addresses Account skeleton directory and default dotfiles, not the specific issue of Reading input line by line and preserving backslashes: Maintain approved default dotfiles and directory templates under /etc/skel and use the appropriate account-creation option to populate new home directories.
F:This shortcut is unsafe for the present Linux issue: Assume ordinary `read` always preserves backslashes and whitespace and that variables modified in any piped loop persist in the parent shell. read -r avoids backslash escape processing, an empty IFS can preserve leading and trailing whitespace, and shell pipeline subshells may isolate assignments.
Question 101
A helpdesk escalation describes this Linux behavior: A technician exports DISPLAY=:0 on a different host and a remote X client fails because the local display is neither reachable nor authorized. Which administrative step is the MOST appropriate way to resolve this issue? Select ONE best answer.
- Distinguish the display manager that provides graphical login, the window manager that arranges application windows and the desktop environment supplying session tools; repair the failing layer.
- Use a deliberate DISPLAY target and suitable X11 cookie-based authorization with xauth or properly restricted SSH X11 forwarding instead of unrestricted xhost access.
- Set xhost + permanently and assume DISPLAY refers to secure authorization rather than merely selecting an X server endpoint.
- Enable suitable assistive tools such as a screen reader, large-print or high-contrast theme and Sticky Keys or on-screen keyboard according to actual user needs.
Explanation
Correct Answer
B:Recommended administrative action: Use a deliberate DISPLAY target and suitable X11 cookie-based authorization with xauth or properly restricted SSH X11 forwarding instead of unrestricted xhost access.
Incorrect Answers
A:This alternative addresses Display managers, window managers and desktop sessions, not the specific issue of X11 display authorization and remote applications: Distinguish the display manager that provides graphical login, the window manager that arranges application windows and the desktop environment supplying session tools; repair the failing layer. Linux principle: An X server accepts graphical client connections subject to transport reachability and authorization; DISPLAY alone does not grant permission and xhost + weakens access control. Appropriate response: Use a deliberate DISPLAY target and suitable X11 cookie-based authorization with xauth or properly restricted SSH X11 forwarding instead of unrestricted xhost access. Root-cause evidence: Inspect DISPLAY and xauth entries, identify server hostname or SSH forwarding endpoint, and test authorized versus denied clients. Independent acceptance: Only intended users can open remote graphical applications on the chosen display and unauthorized X clients cannot connect.
C:That option would set xhost + permanently and assume DISPLAY refers to secure authorization rather than merely selecting an X server endpoint, but it addresses a different concern. An X server accepts graphical client connections subject to transport reachability and authorization; DISPLAY alone does not grant permission and xhost + weakens access control.
D:That option would enable suitable assistive tools such as a screen reader, large-print or high-contrast theme and Sticky Keys or on-screen keyboard according to actual user needs, but it addresses a different concern. An X server accepts graphical client connections subject to transport reachability and authorization; DISPLAY alone does not grant permission and xhost + weakens access control.
Question 102
An operations handoff identifies this problem: A technician exports DISPLAY=:0 on a different host and a remote X client fails because the local display is neither reachable nor authorized. Which Linux behavior or technical principle BEST explains why the issue occurs? Select ONE best answer.
- An X server accepts graphical client connections subject to transport reachability and authorization; DISPLAY alone does not grant permission and xhost + weakens access control.
- Xorg provides an X11 server with file-based configuration overrides; Wayland sessions use a different display architecture and may not honor Xorg driver configuration.
- Set xhost + permanently and assume DISPLAY refers to secure authorization rather than merely selecting an X server endpoint.
- Accessibility mechanisms include visual, auditory and keyboard interaction aids, and individual accommodations are not interchangeable.
Explanation
Correct Answer
A:Relevant Linux operating principle: An X server accepts graphical client connections subject to transport reachability and authorization; DISPLAY alone does not grant permission and xhost + weakens access control.
Incorrect Answers
B:This alternative addresses Xorg configuration overrides and Wayland awareness, not the specific issue of X11 display authorization and remote applications: Xorg provides an X11 server with file-based configuration overrides; Wayland sessions use a different display architecture and may not honor Xorg driver configuration. Linux principle: An X server accepts graphical client connections subject to transport reachability and authorization; DISPLAY alone does not grant permission and xhost + weakens access control. Appropriate response: Use a deliberate DISPLAY target and suitable X11 cookie-based authorization with xauth or properly restricted SSH X11 forwarding instead of unrestricted xhost access. Root-cause evidence: Inspect DISPLAY and xauth entries, identify server hostname or SSH forwarding endpoint, and test authorized versus denied clients. Independent acceptance: Only intended users can open remote graphical applications on the chosen display and unauthorized X clients cannot connect.
C:That option would set xhost + permanently and assume DISPLAY refers to secure authorization rather than merely selecting an X server endpoint, but it addresses a different concern. Appropriate response: Use a deliberate DISPLAY target and suitable X11 cookie-based authorization with xauth or properly restricted SSH X11 forwarding instead of unrestricted xhost access.
D:This alternative addresses Accessibility screen reading and keyboard interaction, not the specific issue of X11 display authorization and remote applications: Accessibility mechanisms include visual, auditory and keyboard interaction aids, and individual accommodations are not interchangeable. Linux principle: An X server accepts graphical client connections subject to transport reachability and authorization; DISPLAY alone does not grant permission and xhost + weakens access control. Appropriate response: Use a deliberate DISPLAY target and suitable X11 cookie-based authorization with xauth or properly restricted SSH X11 forwarding instead of unrestricted xhost access. Root-cause evidence: Inspect DISPLAY and xauth entries, identify server hostname or SSH forwarding endpoint, and test authorized versus denied clients. Independent acceptance: Only intended users can open remote graphical applications on the chosen display and unauthorized X clients cannot connect.
Question 103
A team maintaining a Linux host reports: A technician exports DISPLAY=:0 on a different host and a remote X client fails because the local display is neither reachable nor authorized. Which evidence or command result MOST directly tests the suspected root cause? Select ONE best answer.
- Set xhost + permanently and assume DISPLAY refers to secure authorization rather than merely selecting an X server endpoint.
- Inspect DISPLAY and xauth entries, identify server hostname or SSH forwarding endpoint, and test authorized versus denied clients.
- Inspect accessibility configuration, demonstrate a screen reader and key combination, and ask the affected user to complete a representative task.
- Check the session type, Xorg log or configuration fragments, effective keyboard layout and results after restarting an appropriate test session.
Explanation
Correct Answer
B:Most direct verification evidence: Inspect DISPLAY and xauth entries, identify server hostname or SSH forwarding endpoint, and test authorized versus denied clients.
Incorrect Answers
A:This shortcut is unsafe for the present Linux issue: Set xhost + permanently and assume DISPLAY refers to secure authorization rather than merely selecting an X server endpoint. It cannot establish a safe correction.
C:That option would inspect accessibility configuration, demonstrate a screen reader and key combination, and ask the affected user to complete a representative task, but it addresses a different concern. An X server accepts graphical client connections subject to transport reachability and authorization; DISPLAY alone does not grant permission and xhost + weakens access control.
D:That option would check the session type, Xorg log or configuration fragments, effective keyboard layout and results after restarting an appropriate test session, but it addresses a different concern. An X server accepts graphical client connections subject to transport reachability and authorization; DISPLAY alone does not grant permission and xhost + weakens access control.
Question 104
While verifying a Linux change request, an engineer finds: A technician exports DISPLAY=:0 on a different host and a remote X client fails because the local display is neither reachable nor authorized. Which observed outcome BEST confirms a successful and properly scoped correction? Select ONE best answer.
- The user can independently navigate and complete the workflow through the chosen assistive technology without requiring unsupported input actions.
- Set xhost + permanently and assume DISPLAY refers to secure authorization rather than merely selecting an X server endpoint.
- Only intended users can open remote graphical applications on the chosen display and unauthorized X clients cannot connect.
- The chosen desktop or remote session operates for authorized users with the expected persistence and acceptable resource use.
Explanation
Correct Answer
C:Observable acceptance criterion: Only intended users can open remote graphical applications on the chosen display and unauthorized X clients cannot connect.
Incorrect Answers
A:This alternative addresses Accessibility screen reading and keyboard interaction, not the specific issue of X11 display authorization and remote applications: The user can independently navigate and complete the workflow through the chosen assistive technology without requiring unsupported input actions. Linux principle: An X server accepts graphical client connections subject to transport reachability and authorization; DISPLAY alone does not grant permission and xhost + weakens access control. Appropriate response: Use a deliberate DISPLAY target and suitable X11 cookie-based authorization with xauth or properly restricted SSH X11 forwarding instead of unrestricted xhost access. Root-cause evidence: Inspect DISPLAY and xauth entries, identify server hostname or SSH forwarding endpoint, and test authorized versus denied clients. Independent acceptance: Only intended users can open remote graphical applications on the chosen display and unauthorized X clients cannot connect.
B:This shortcut is unsafe for the present Linux issue: Set xhost + permanently and assume DISPLAY refers to secure authorization rather than merely selecting an X server endpoint. An X server accepts graphical client connections subject to transport reachability and authorization; DISPLAY alone does not grant permission and xhost + weakens access control.
D:This alternative addresses Graphical desktop families and remote desktop protocols, not the specific issue of X11 display authorization and remote applications: The chosen desktop or remote session operates for authorized users with the expected persistence and acceptable resource use. Linux principle: An X server accepts graphical client connections subject to transport reachability and authorization; DISPLAY alone does not grant permission and xhost + weakens access control. Appropriate response: Use a deliberate DISPLAY target and suitable X11 cookie-based authorization with xauth or properly restricted SSH X11 forwarding instead of unrestricted xhost access. Root-cause evidence: Inspect DISPLAY and xauth entries, identify server hostname or SSH forwarding endpoint, and test authorized versus denied clients. Independent acceptance: Only intended users can open remote graphical applications on the chosen display and unauthorized X clients cannot connect.
Question 105
A Linux administrator investigates the following system incident: A technician exports DISPLAY=:0 on a different host and a remote X client fails because the local display is neither reachable nor authorized. Which misleading assumption MOST directly contributes to this failure and should be rejected? Select ONE best answer.
- Treat the window manager as the same program as the graphical login manager and expect installing a desktop theme to repair a failed login service.
- Assume every Linux GUI is an Xorg server and that an Xorg configuration fragment necessarily controls a Wayland compositor.
- Assume all graphical desktops are GNOME and that remote X11 application forwarding is identical to a full persistent VNC desktop session.
- Set xhost + permanently and assume DISPLAY refers to secure authorization rather than merely selecting an X server endpoint.
Explanation
Correct Answer
D:Reject this specific misconception: Set xhost + permanently and assume DISPLAY refers to secure authorization rather than merely selecting an X server endpoint. It incorrectly assumes behavior that conflicts with the observed Linux conditions.
Incorrect Answers
A:That option would treat the window manager as the same program as the graphical login manager and expect installing a desktop theme to repair a failed login service, but it addresses a different concern. An X server accepts graphical client connections subject to transport reachability and authorization; DISPLAY alone does not grant permission and xhost + weakens access control.
B:That option would assume every Linux GUI is an Xorg server and that an Xorg configuration fragment necessarily controls a Wayland compositor, but it addresses a different concern. An X server accepts graphical client connections subject to transport reachability and authorization; DISPLAY alone does not grant permission and xhost + weakens access control.
C:That option would assume all graphical desktops are GNOME and that remote X11 application forwarding is identical to a full persistent VNC desktop session, but it addresses a different concern. An X server accepts graphical client connections subject to transport reachability and authorization; DISPLAY alone does not grant permission and xhost + weakens access control.
Question 106
On a production Linux workstation or server, a technician observes: A shared workstation runs xhost + to solve a temporary remote GUI problem and unintentionally permits broad X server access. Which administrative step is the MOST appropriate way to resolve this issue? Select ONE best answer.
- Set xhost + permanently and assume DISPLAY refers to secure authorization rather than merely selecting an X server endpoint.
- Identify the active graphical protocol and configure supported Xorg input overrides in the appropriate X configuration location or use the Wayland compositor's supported setting path.
- Use a deliberate DISPLAY target and suitable X11 cookie-based authorization with xauth or properly restricted SSH X11 forwarding instead of unrestricted xhost access.
- Distinguish the display manager that provides graphical login, the window manager that arranges application windows and the desktop environment supplying session tools; repair the failing layer.
Explanation
Correct Answer
C:Recommended administrative action: Use a deliberate DISPLAY target and suitable X11 cookie-based authorization with xauth or properly restricted SSH X11 forwarding instead of unrestricted xhost access. An X server accepts graphical client connections subject to transport reachability and authorization; DISPLAY alone does not grant permission and xhost + weakens access control.
Incorrect Answers
A:This shortcut is unsafe for the present Linux issue: Set xhost + permanently and assume DISPLAY refers to secure authorization rather than merely selecting an X server endpoint. An X server accepts graphical client connections subject to transport reachability and authorization; DISPLAY alone does not grant permission and xhost + weakens access control.
B:That option would identify the active graphical protocol and configure supported Xorg input overrides in the appropriate X configuration location or use the Wayland compositor's supported setting path, but it addresses a different concern. An X server accepts graphical client connections subject to transport reachability and authorization; DISPLAY alone does not grant permission and xhost + weakens access control.
D:This alternative addresses Display managers, window managers and desktop sessions, not the specific issue of X11 display authorization and remote applications: Distinguish the display manager that provides graphical login, the window manager that arranges application windows and the desktop environment supplying session tools; repair the failing layer. Linux principle: An X server accepts graphical client connections subject to transport reachability and authorization; DISPLAY alone does not grant permission and xhost + weakens access control. Appropriate response: Use a deliberate DISPLAY target and suitable X11 cookie-based authorization with xauth or properly restricted SSH X11 forwarding instead of unrestricted xhost access. Root-cause evidence: Inspect DISPLAY and xauth entries, identify server hostname or SSH forwarding endpoint, and test authorized versus denied clients. Independent acceptance: Only intended users can open remote graphical applications on the chosen display and unauthorized X clients cannot connect.
Question 107
During an LPIC-1 practice lab, the operator encounters this condition: A shared workstation runs xhost + to solve a temporary remote GUI problem and unintentionally permits broad X server access. Which Linux behavior or technical principle BEST explains why the issue occurs? Select ONE best answer.
- Set xhost + permanently and assume DISPLAY refers to secure authorization rather than merely selecting an X server endpoint.
- An X server accepts graphical client connections subject to transport reachability and authorization; DISPLAY alone does not grant permission and xhost + weakens access control.
- Desktop environments are replaceable collections of applications and session components; X11 forwarding and remote desktop protocols serve different access models.
- Xorg provides an X11 server with file-based configuration overrides; Wayland sessions use a different display architecture and may not honor Xorg driver configuration.
Explanation
Correct Answer
B:Relevant Linux operating principle: An X server accepts graphical client connections subject to transport reachability and authorization; DISPLAY alone does not grant permission and xhost + weakens access control.
Incorrect Answers
A:This shortcut is unsafe for the present Linux issue: Set xhost + permanently and assume DISPLAY refers to secure authorization rather than merely selecting an X server endpoint. It cannot establish a safe correction. Linux principle: An X server accepts graphical client connections subject to transport reachability and authorization; DISPLAY alone does not grant permission and xhost + weakens access control.
C:This alternative addresses Graphical desktop families and remote desktop protocols, not the specific issue of X11 display authorization and remote applications: Desktop environments are replaceable collections of applications and session components; X11 forwarding and remote desktop protocols serve different access models. Linux principle: An X server accepts graphical client connections subject to transport reachability and authorization; DISPLAY alone does not grant permission and xhost + weakens access control. Appropriate response: Use a deliberate DISPLAY target and suitable X11 cookie-based authorization with xauth or properly restricted SSH X11 forwarding instead of unrestricted xhost access. Root-cause evidence: Inspect DISPLAY and xauth entries, identify server hostname or SSH forwarding endpoint, and test authorized versus denied clients. Independent acceptance: Only intended users can open remote graphical applications on the chosen display and unauthorized X clients cannot connect.
D:This alternative addresses Xorg configuration overrides and Wayland awareness, not the specific issue of X11 display authorization and remote applications: Xorg provides an X11 server with file-based configuration overrides; Wayland sessions use a different display architecture and may not honor Xorg driver configuration. Linux principle: An X server accepts graphical client connections subject to transport reachability and authorization; DISPLAY alone does not grant permission and xhost + weakens access control. Appropriate response: Use a deliberate DISPLAY target and suitable X11 cookie-based authorization with xauth or properly restricted SSH X11 forwarding instead of unrestricted xhost access. Root-cause evidence: Inspect DISPLAY and xauth entries, identify server hostname or SSH forwarding endpoint, and test authorized versus denied clients. Independent acceptance: Only intended users can open remote graphical applications on the chosen display and unauthorized X clients cannot connect.
Question 108
A helpdesk escalation describes this Linux behavior: A shared workstation runs xhost + to solve a temporary remote GUI problem and unintentionally permits broad X server access. Which evidence or command result MOST directly tests the suspected root cause? Select ONE best answer.
- Inspect the installed session and remote service capabilities, test authentication and reconnection, and verify responsiveness under expected bandwidth.
- Inspect DISPLAY and xauth entries, identify server hostname or SSH forwarding endpoint, and test authorized versus denied clients.
- Set xhost + permanently and assume DISPLAY refers to secure authorization rather than merely selecting an X server endpoint.
- Inspect the enabled graphical login service, session files, login logs and active window manager, and attempt both local login and manual session startup.
Explanation
Correct Answer
B:Most direct verification evidence: Inspect DISPLAY and xauth entries, identify server hostname or SSH forwarding endpoint, and test authorized versus denied clients. An X server accepts graphical client connections subject to transport reachability and authorization; DISPLAY alone does not grant permission and xhost + weakens access control.
Incorrect Answers
A:That option would inspect the installed session and remote service capabilities, test authentication and reconnection, and verify responsiveness under expected bandwidth, but it addresses a different concern. An X server accepts graphical client connections subject to transport reachability and authorization; DISPLAY alone does not grant permission and xhost + weakens access control.
C:This shortcut is unsafe for the present Linux issue: Set xhost + permanently and assume DISPLAY refers to secure authorization rather than merely selecting an X server endpoint. It cannot establish a safe correction. Linux principle: An X server accepts graphical client connections subject to transport reachability and authorization; DISPLAY alone does not grant permission and xhost + weakens access control. Appropriate response: Use a deliberate DISPLAY target and suitable X11 cookie-based authorization with xauth or properly restricted SSH X11 forwarding instead of unrestricted xhost access. Root-cause evidence: Inspect DISPLAY and xauth entries, identify server hostname or SSH forwarding endpoint, and test authorized versus denied clients. Independent acceptance: Only intended users can open remote graphical applications on the chosen display and unauthorized X clients cannot connect.
D:That option would inspect the enabled graphical login service, session files, login logs and active window manager, and attempt both local login and manual session startup, but it addresses a different concern. An X server accepts graphical client connections subject to transport reachability and authorization; DISPLAY alone does not grant permission and xhost + weakens access control.
Question 109
An operations handoff identifies this problem: A shared workstation runs xhost + to solve a temporary remote GUI problem and unintentionally permits broad X server access. Which observed outcome BEST confirms a successful and properly scoped correction? Select ONE best answer.
- Set xhost + permanently and assume DISPLAY refers to secure authorization rather than merely selecting an X server endpoint.
- Only intended users can open remote graphical applications on the chosen display and unauthorized X clients cannot connect.
- The user can independently navigate and complete the workflow through the chosen assistive technology without requiring unsupported input actions.
- The login greeter starts reliably and the chosen session manages windows correctly without conflating the two roles.
Explanation
Correct Answer
B:Observable acceptance criterion: Only intended users can open remote graphical applications on the chosen display and unauthorized X clients cannot connect. An X server accepts graphical client connections subject to transport reachability and authorization; DISPLAY alone does not grant permission and xhost + weakens access control.
Incorrect Answers
A:This shortcut is unsafe for the present Linux issue: Set xhost + permanently and assume DISPLAY refers to secure authorization rather than merely selecting an X server endpoint. An X server accepts graphical client connections subject to transport reachability and authorization; DISPLAY alone does not grant permission and xhost + weakens access control.
C:This alternative addresses Accessibility screen reading and keyboard interaction, not the specific issue of X11 display authorization and remote applications: The user can independently navigate and complete the workflow through the chosen assistive technology without requiring unsupported input actions. Linux principle: An X server accepts graphical client connections subject to transport reachability and authorization; DISPLAY alone does not grant permission and xhost + weakens access control. Appropriate response: Use a deliberate DISPLAY target and suitable X11 cookie-based authorization with xauth or properly restricted SSH X11 forwarding instead of unrestricted xhost access. Root-cause evidence: Inspect DISPLAY and xauth entries, identify server hostname or SSH forwarding endpoint, and test authorized versus denied clients. Independent acceptance: Only intended users can open remote graphical applications on the chosen display and unauthorized X clients cannot connect.
D:This alternative addresses Display managers, window managers and desktop sessions, not the specific issue of X11 display authorization and remote applications: The login greeter starts reliably and the chosen session manages windows correctly without conflating the two roles. Linux principle: An X server accepts graphical client connections subject to transport reachability and authorization; DISPLAY alone does not grant permission and xhost + weakens access control. Appropriate response: Use a deliberate DISPLAY target and suitable X11 cookie-based authorization with xauth or properly restricted SSH X11 forwarding instead of unrestricted xhost access. Root-cause evidence: Inspect DISPLAY and xauth entries, identify server hostname or SSH forwarding endpoint, and test authorized versus denied clients. Independent acceptance: Only intended users can open remote graphical applications on the chosen display and unauthorized X clients cannot connect.
Question 110
A team maintaining a Linux host reports: A shared workstation runs xhost + to solve a temporary remote GUI problem and unintentionally permits broad X server access. Which TWO complementary steps provide the best corrective action and its most direct diagnostic verification? Select TWO answers.
- Set xhost + permanently and assume DISPLAY refers to secure authorization rather than merely selecting an X server endpoint.
- Use a deliberate DISPLAY target and suitable X11 cookie-based authorization with xauth or properly restricted SSH X11 forwarding instead of unrestricted xhost access.
- Inspect the enabled graphical login service, session files, login logs and active window manager, and attempt both local login and manual session startup.
- Enable suitable assistive tools such as a screen reader, large-print or high-contrast theme and Sticky Keys or on-screen keyboard according to actual user needs.
- Inspect DISPLAY and xauth entries, identify server hostname or SSH forwarding endpoint, and test authorized versus denied clients.
Explanation
Correct Answers
B:Recommended administrative action: Use a deliberate DISPLAY target and suitable X11 cookie-based authorization with xauth or properly restricted SSH X11 forwarding instead of unrestricted xhost access. Linux principle: An X server accepts graphical client connections subject to transport reachability and authorization; DISPLAY alone does not grant permission and xhost + weakens access control.
E:Most direct verification evidence: Inspect DISPLAY and xauth entries, identify server hostname or SSH forwarding endpoint, and test authorized versus denied clients. Linux principle: An X server accepts graphical client connections subject to transport reachability and authorization; DISPLAY alone does not grant permission and xhost + weakens access control.
Incorrect Answers
A:This shortcut is unsafe for the present Linux issue: Set xhost + permanently and assume DISPLAY refers to secure authorization rather than merely selecting an X server endpoint. An X server accepts graphical client connections subject to transport reachability and authorization; DISPLAY alone does not grant permission and xhost + weakens access control.
C:This alternative addresses Display managers, window managers and desktop sessions, not the specific issue of X11 display authorization and remote applications: Inspect the enabled graphical login service, session files, login logs and active window manager, and attempt both local login and manual session startup.
D:This alternative addresses Accessibility screen reading and keyboard interaction, not the specific issue of X11 display authorization and remote applications: Enable suitable assistive tools such as a screen reader, large-print or high-contrast theme and Sticky Keys or on-screen keyboard according to actual user needs.