LCA ICT Specialism study materials
LCA ICT Specialism study resources

LCA ICT Specialism study plan

LCA ICT Specialism · Give each week a clear focus.

8 weeks · About 6 hours per week

Week 1

Linux Fundamentals and Command-Line Operations

  • Install a Linux distribution in a virtual machine and complete first boot, user creation, and package updates without notes

  • Navigate the filesystem using cd, ls, pwd, and find to locate at least ten specific files by name and by permission pattern

  • Demonstrate text-processing pipelines combining grep, sed, awk, sort, uniq, and cut on a log file to extract counts per source IP

  • Explain the difference between absolute and relative paths and correctly redirect stdout and stderr to separate files

  • Use man, --help, and apropos to answer five command-syntax questions you could not answer from memory

Your checkpoint

A one-page command cheat sheet in your own words covering 20 commands, each with a working example you actually ran, plus terminal transcripts proving the grep/awk pipeline produced correct per-IP counts

Week 2

Linux Fundamentals and Command-Line Operations

  • Manage files and directories with cp, mv, rm, mkdir, ln, and tar, including creating and restoring a compressed archive

  • Search and filter file content with grep using basic and extended regular expressions, including anchors and character classes

  • Edit files non-interactively with sed substitutions and confirm the change with diff

  • Set and interpret file permissions using chmod symbolic and octal modes and chown, then verify with ls -l

  • Schedule a recurring job with cron and confirm it executed by inspecting logs or output files

Your checkpoint

A shell script that archives a chosen directory with a timestamped tar.gz, logs the result, and is triggered by a cron entry; include the crontab line and the log output from two successful runs

Week 3

System and Process Management

  • Inspect running processes with ps, top, and pgrep and map parent-child relationships using pstree

  • Send signals with kill and pkill to terminate, pause, and resume a process, and explain SIGTERM versus SIGKILL

  • Start, stop, enable, and check a systemd service, then read its status and journal output

  • Adjust process priority with nice and renice and observe the effect on scheduling priority values

  • Identify which process is listening on a given port using ss or lsof and terminate it safely

Your checkpoint

A troubleshooting write-up of a deliberately broken service (bad ExecStart path) documenting the symptom, the commands used, the journal evidence, and the fix, with before-and-after systemctl status output

Week 4

System and Process Management & Storage, Filesystems, and Permissions

  • Create, format, mount, and unmount a new virtual disk and persist the mount in /etc/fstab

  • Check and repair filesystem consistency with fsck on an unmounted volume and interpret the exit codes

  • Monitor disk usage with df and du and locate the largest consumers in a directory tree

  • Explain inode exhaustion versus block exhaustion and demonstrate each condition

  • Apply special permission bits (setuid, setgid, sticky) and describe the security implication of each

Your checkpoint

A storage lab report showing a new volume mounted via fstab surviving a reboot, df and du output, and a written explanation of one inode-exhaustion test you reproduced

Week 5

Networking Concepts and Configuration

  • Configure a static IPv4 address, gateway, and DNS resolver on a Linux host and verify with ip addr and ip route

  • Test connectivity and name resolution with ping, traceroute, dig, and curl and interpret each output

  • Explain the TCP three-way handshake and identify which ports and protocols common services use

  • Use ss to list listening sockets and explain the difference between a listening and an established connection

  • Diagnose a name-resolution failure by distinguishing a DNS problem from a routing or firewall problem

Your checkpoint

A network diagnostic worksheet with five injected faults (wrong gateway, wrong DNS, closed port, bad route, firewall drop) each documented with the commands run, the evidence, and the corrected configuration

Week 6

Security Fundamentals and Access Control

  • Harden SSH by disabling root login and password authentication, then verify key-based access still works

  • Configure a host firewall to allow only required ports and prove blocked traffic is rejected

  • Create users and groups, apply least-privilege sudo rules via a drop-in file, and test the boundary

  • Audit file ownership and world-writable files and remediate the findings

  • Review authentication logs to identify failed login attempts and explain what each entry indicates

Your checkpoint

A security hardening checklist applied to your lab host, with command output proving each control is active and a short risk note for every setting changed

Week 7

Scripting and Automation & Cloud and Virtualization Basics

  • Write a Bash script that accepts arguments, validates input, uses conditionals and loops, and exits with meaningful status codes

  • Add error handling with set -euo pipefail and trap so the script cleans up on failure

  • Provision a cloud or local virtual machine from a script or CLI and capture the instance metadata

  • Explain the shared-responsibility boundary for a virtual machine and identify which layers you still secure

  • Take a snapshot or image of a virtual machine and restore it to a working state

Your checkpoint

A reusable provisioning script that creates a VM, applies baseline configuration, and writes a run log; include the script, the log, and evidence of a successful snapshot-and-restore cycle

Week 8

ICT Support, Troubleshooting, and Documentation

  • Diagnose a multi-fault scenario combining a service failure, a permission error, and a network misconfiguration using a structured method

  • Document the resolution in a ticket format with symptom, impact, investigation, root cause, fix, and prevention

  • Build a runbook for one recurring task so another technician could execute it unaided

  • Review your earlier deliverables against the exam objectives and list remaining weak areas with a remediation action for each

  • Complete a timed practice set covering all eight domains and record your score per domain

Your checkpoint

A portfolio bundle containing one full incident ticket with root cause analysis, one runbook, and a scored practice-set summary with a ranked remediation list

Milestones

Week 2: You can perform routine file, text, and permission operations from the command line without consulting notes for more than one minute per task

Week 4: You can manage processes and services and mount a persistent filesystem from scratch, explaining each step aloud as you go

Week 6: You can configure networking and apply baseline security hardening, and you correctly diagnose five injected network faults

Week 8: You score at least 75 percent overall on the timed practice set with no domain below 60 percent, and your portfolio contains a complete incident ticket and a runbook