Ruankao Information System Operations Administrator (Junior) study plan

Diagram the composition of a computer system (CPU, memory hierarchy, bus, I/O, firmware/BIOS-UEFI) and explain how each layer affects operations work

Distinguish the roles of OS kernel, shell, system services and file systems, and list which operational tasks belong to each layer

Install a Linux distribution and a Windows Server evaluation build in virtual machines, then record the partitioning, driver and licensing choices made

Create local users and groups in both systems and set file permissions, verifying effective access with test accounts

Use at least four monitoring commands or tools (CPU, memory, disk, process) and interpret what each metric indicates about load

Configure disk partitioning, swap/pagefile sizing and file-system mount points on the lab server and justify each sizing decision

Write a shell script that rotates and compresses logs, schedules it with cron or Task Scheduler, and confirm it ran unattended

Diagnose three induced performance problems (CPU saturation, memory pressure, disk I/O wait) and document the metric evidence for each

Explain how a database engine uses memory, disk and connections so you can describe which server resources a slow query consumes

Produce a baseline performance record of the lab server taken at idle and under synthetic load

Configure IP addressing, subnet masks, gateways and static routes on two virtual routers or a simulated topology and verify reachability

Set up VLAN segmentation and an access control list, then prove permitted and denied traffic with test pings

Trace a simulated connectivity failure layer by layer (physical, link, IP, transport, application) and record the elimination order

Compare straight-through and crossover cabling, fiber vs. copper limits, and rack power/cooling requirements in a written summary

Build a troubleshooting checklist that maps common symptoms (no link, no route, DNS failure, port blocked) to first diagnostic commands

Install a relational database instance, create a schema with primary/foreign keys and load sample data

Write and run SELECT, INSERT, UPDATE, DELETE and JOIN statements, and explain what each does to the data

Perform a full backup and a point-in-time recovery into a separate instance, verifying row counts after restore

Create database accounts with least privilege, test that a restricted account is denied unauthorized operations, and document the grants

Draft an access control matrix for the lab environment covering OS accounts, database accounts and administrative roles

Design a 3-2-1 backup scheme for the lab server and state the RPO and RTO each tier supports

Execute and time a full restore drill from backup media, recording elapsed time against the stated RTO

Apply OS and application patches in a staged order (test then production) and record rollback steps for a failed patch

Configure antivirus or endpoint protection, run a scan, and document how a detected threat would be quarantined and reported

Write an incident response sequence for a suspected malware infection: contain, eradicate, recover, and lessons learned

Draft a business continuity and contingency plan section covering critical systems, dependencies and manual workarounds

Classify ten sample operational events into incident, problem, change or service request and justify each classification

Walk one change through a full change record: request, risk assessment, approval, implementation, verification and closure

Build a configuration item inventory linking at least five components (server, database, switch, application, backup job) and their relationships

Define service desk severity levels with target response and resolution times, and map escalation paths for each

Write an operations log entry template and complete three entries covering routine maintenance, an incident and a change

Summarize the compliance obligations that affect operations work: data protection, log retention, software licensing and privacy of personal data

Identify which ITIL practices (incident, problem, change, configuration, service level) apply to a given scenario and explain the fit

Work through two integrated case scenarios that combine monitoring, security and recovery decisions, and justify each action taken

Review your own lab documentation against a checklist of completeness (who, what, when, result, follow-up)

Re-test every weak area identified in earlier weeks and correct the notes that caused errors

Complete two timed full-length practice sets under exam conditions and score them by domain

Re-derive the key formulas and rules you must recall: subnetting, backup windows, RTO/RPO, severity levels, permission models

Condense each domain into a one-page summary sheet you can review in the final days

Simulate a full incident end to end (detect, diagnose, contain, recover, document) and time each stage