$ Linux One Liners
Back to cert prep

Practice area

LFCS Operations and Deployment

Diagnose service state, logs, restarts, timers, and deployment symptoms from a command line.

Linux One Liners is an independent study and practice resource. It is not affiliated with, endorsed by, or approved by LPI, The Linux Foundation, CompTIA, or any certification provider. This site does not provide exam dumps or real exam questions.

Source status

Source status: Linux Foundation LFCS page verified June 30, 2026. LFCS is an online, proctored, performance-based command-line exam.

This page paraphrases study areas into command practice. It does not copy official objective text wholesale and is not an exam dump.

Plain-English goal

Practice area: operations and deployment. Exam/domain: LFCS.

read the situation

Command, output, and next step

Command anatomy

systemctl
systemctl
read service state and unit metadata
journalctl
read systemd logs
-u
scope logs to one unit when present
--since/-b
limit the time window
--no-pager
make output copyable in drills

Annotated output

nginx.service - A high performance web server
   Loaded: loaded (/lib/systemd/system/nginx.service; enabled)
   Active: failed (Result: exit-code) since Fri 2026-07-03 10:12:04 CDT
Jul 03 10:12:04 web01 nginx[2310]: nginx: [emerg] open() "/etc/nginx/nginx.conf" failed (13: Permission denied)

What to notice

Loaded
whether the unit file exists and is enabled
Active
current service state
Result
how systemd classified the failure
log message
the concrete file, port, user, or syntax cause

Safe vs unsafe move

Common wrong move

Restarting the service before reading the failing line.

Next safe command

nginx -t

Troubleshooting ladder

  1. Name the symptom.
  2. Inspect read-only state.
  3. Find the owner, service, file, device, mount, or route.
  4. Read the decisive output field.
  5. Choose the next narrow command.
  6. Avoid broad or destructive changes.
  7. Make the smallest justified change if required.
  8. Verify and record what changed.

How to get help

  1. Know the commandUse command --help, then man command for the full reference.
  2. Know the conceptUse apropos keyword or man -k keyword to discover command names.
  3. Maybe a shell builtinUse type command, command -V command, then help command.
  4. Service behaviorUse systemctl status service and journalctl -u service before restarting.
  5. Package ownershipUse dpkg -S, rpm -qf, or the distro package tool for the installed file.

performance practice

Timed task cards

LFCS-style practice should reward evidence, small changes, verification, and rollback thinking.

Timed task

Read-only proof task

Task: Prove the current operations and deployment state without changing it.

Time: 8 minutes

Allowed first commands: systemctl, journalctl, ss, curl

Pass: You identify the decisive field and can explain normal versus abnormal output.

Fail: You restart, delete, chmod, or edit before proving the state.

Timed task

Smallest safe change task

Task: Name the smallest justified change you would make after the evidence is clear.

Time: 10 minutes

Allowed first commands: status/log/readout command first, change command second

Pass: The change is scoped, reversible, and tied to one output field.

Fail: The change is broad, unverified, or unrelated to the evidence.

Timed task

Verify and rollback task

Task: State the verification command and rollback note for the task.

Time: 6 minutes

Allowed first commands: status, log, route, mount, permission, or package verification

Pass: You can show the before/after signal and explain rollback.

Fail: You cannot prove the task worked or cannot undo the change.

command families

Commands to practice

  • systemctl
  • journalctl
  • ss
  • curl

Related command pages

Related drills