Linux Essentials Certificate Exam, version 1.6 Free Practice Test — 30 Questions
This practice bank exercises foundational Linux administration skills, focusing on file permissions (chmod, chown, setgid, setuid, ACLs), secure privilege escalation with sudo, system monitoring (systemd, journalctl), process management, and troubleshooting methodologies. It also tests understanding of open-source licensing (GPL) and behavioral competencies like adaptability under pressure. The scenarios involve real-world tasks such as configuring shared directories, deploying security patches, diagnosing performance issues, and managing user access. Mastery of these topics is critical for the Linux Essentials Certificate Exam, version 1.6.
What this Linux Essentials Certificate Exam, version 1.6 practice set measures
This is an analysis of the practice bank, not a claim about the vendor's live exam blueprint. Use it to identify the knowledge, judgment, and recall patterns exercised here, then verify your coverage against the current official exam guide.
File Permissions and Ownership
This section covers the foundational Linux permission model using chmod, chown, and octal notation. It explores special bits like setgid and setuid for collaborative environments, Access Control Lists (ACLs) for granular control, and the sticky bit for shared directories. Scenarios test the ability to set permissions that balance security and collaboration, such as granting execute to owner, read to group, and no access to others (u=x,g=r,o=). Understanding these mechanisms is essential for restricting or allowing file access in multi-user systems.
- Octal permissions (e.g., 754, 600, 2770) map to specific owner/group/other rights.
- Setgid bit (g+s) on directories ensures new files inherit group ownership.
- ACLs with setfacl allow precise user/group permissions beyond standard triads.
- Sticky bit (1xxx) prevents users from deleting others' files in a shared directory.
Privilege Escalation and sudo
The sudo command is a key mechanism for delegating administrative tasks without sharing root passwords. The practice bank examines sudoers configurations that grant specific commands (e.g., restart services) while denying others. It also covers the distinction between reload and restart for services like sshd, and the use of NOPASSWD for non-interactive scripts. Understanding these concepts ensures secure privilege elevation and adherence to the principle of least privilege.
- Sudoers entries specify user, host, target user, and command list (e.g., 'kenji ALL=(ALL) NOPASSWD: /usr/sbin/service ...').
- Reloading a daemon (systemctl reload) reads config changes without interrupting active connections.
- Disabling root SSH login (PermitRootLogin no) forces use of sudo for admin tasks.
System Monitoring and Troubleshooting
Troubleshooting methodology is exercised through scenarios involving service degradation, kernel upgrades, and corrupted configuration files. Tools like top, htop, iostat, and journalctl are used to diagnose resource contention or log errors. The practice set emphasizes systematic analysis, such as checking service status with systemctl, then diving into real-time resource usage before making changes. Proper backup and rollback procedures are also tested to ensure minimal downtime during critical fixes.
- Journalctl -xe provides detailed, contextual systemd journal logs for recent events.
- Top/htop reveal CPU, memory, and I/O bottlenecks across processes.
- A methodical approach involves verifying service status, checking logs, then analyzing resource use.
Adaptability and Problem-Solving Under Pressure
Several questions assess behavioral competencies like handling ambiguous requirements, shifting priorities, and unexpected failures. Scenarios include deprecated utilities, concurrent outage and patch deployments, and untested deployments with tight windows. The correct approach prioritizes communication, incremental rollback planning, and seeking guidance when necessary. These scenarios mirror real-world admin challenges requiring flexibility and systematic decision-making.
- When a critical patch deployment conflicts with an outage, halt the patch, resolve the outage, then re-evaluate timeline.
- Open-source deprecation requires investigating maintained forks and bridging gaps with custom scripts.
- Untested security patches should be deployed during low traffic with a documented rollback plan.
Practice Linux Essentials Certificate Exam, version 1.6 with real flashcards
Read the prompt, commit to an answer, then flip the card. Move through the deck at your own pace and repeat any topic that does not come back quickly.
Card 1 of 20
1 reviewed this session
Static practice bank
Start the 30-question diagnostic
The complete question bank is embedded in this pre-rendered page. There is no database request or second content download when you begin.
Anya, a system administrator, is tasked with configuring a new shared project directory on a Linux server. This directory, located at `/srv/data/projects`, is intended exclusively for a developer named \'developerX\' to store and modify project files. It is critical that no other user on the system, whether in a specific group or not, can view, read, or write to this directory. Which command sequence would Anya use to ensure only \'developerX\' has full control over this directory and all other users are denied any access?
Study workflow
Turn one Linux Essentials Certificate Exam, version 1.6 attempt into a study plan
- 1
Set Up a Shared Directory with Setgid
Create the directory, change group ownership to the project group, then apply setgid using 'chmod g+s'. This ensures new files inherit the group. Set write and execute permissions for the group with 'chmod g+wx' to allow collaboration. Optionally add the sticky bit (chmod +t) to prevent file deletion by non-owners.
- 2
Grant Limited Sudo Access for Service Restarts
Edit /etc/sudoers with visudo. Add an entry like 'username ALL=(ALL) NOPASSWD: /usr/sbin/service apache2 restart, /usr/sbin/service mysql restart'. This allows the user to restart only those services without a password, restricting broader administrative commands.
- 3
Implement ACLs for Granular Permissions
Use setfacl to grant specific user or group permissions. For example, 'setfacl -m u:developer_group:rx /project/dir' adds read+execute for that group. Combine with the default ACL (-d) so new files inherit these permissions. Verify with getfacl.
- 4
Investigate Performance Degradation with Top and Journalctl
Run top or htop to identify high CPU/memory processes. Check systemd journal with 'journalctl -xe' for recent errors. For I/O analysis, use iostat. Correlate findings with application logs. Adjust resources by stopping non-essential services or tuning configurations.
- 5
Deploy a Critical Patch with Rollback Plan
Schedule a maintenance window during low traffic. Create a full system backup. Apply the patch using automation scripts. Test functionally after deployment. If errors occur, execute the pre-defined rollback (e.g., restore backup or revert package version). Communicate status to stakeholders.
FAQ
Questions about this exam practice page
Clear boundaries on what the bank covers, how to use it, and where official vendor information still matters.
What is the difference between chmod 754 and chmod 754 with setgid?+
chmod 754 sets owner rwx, group r-x, others r--. Adding setgid (chmod 2754) also sets the group-ID bit, so new files in the directory inherit the group. The octal 2 represents setgid.
How do I prevent a user from deleting other users' files in a shared directory?+
Set the sticky bit on the directory using 'chmod +t' (or octal 1xxx). Only file owners and root can delete or rename files. This is common on /tmp.
What is the purpose of the NOPASSWD tag in sudoers?+
NOPASSWD allows the user to execute the specified commands without entering a password. It is useful for scripts or automated tasks but should be used sparingly to maintain security.
How does journalctl -xe help in troubleshooting?+
journalctl -xe shows the last few log entries from the systemd journal with explanations and contextual data. It helps quickly identify errors or warnings related to recent system events.
What does the GPL-v3 require when distributing modified software?+
Under GPL-v3, you must make the source code of your modifications available under the same license to all recipients. This includes any combined work that uses GPL-licensed libraries, unless an exception applies.
Build the next review session
Browse another free bank or use the study strategy guide to turn your misses into spaced review.