NCP-GENL study plan
NCP-GENL · Give each week a clear focus.
8 weeks · About 6 hours per week
Installation and Configuration
Install the NCP-GENL reference stack from a clean host and record every prompt, default, and package dependency in a build log
Configure hostname, timezone, NTP, and static addressing so the node survives a reboot without manual fixes
Map each installation parameter to the configuration file or CLI flag that controls it, and note which values are safe to change post-install
Write a one-page pre-install checklist a colleague could follow to reproduce your node identically
Your checkpoint
A numbered install runbook plus a filled-in configuration matrix (parameter, file, default, chosen value, rationale) covering at least 15 settings
Installation and Configuration & Networking Fundamentals
Harden the freshly installed node by disabling unused services and verifying the resulting open ports
Configure interface bonding or VLAN tagging and confirm the change with link and route inspection
Trace the path of a packet from the node to an external host using routing table and neighbor cache output
Diagnose three deliberately broken network configurations and document the symptom-to-cause mapping
Your checkpoint
A before/after port and interface report showing the hardened state and a troubleshooting log of the three injected faults with root causes
Networking Fundamentals
Subnet a given address block into at least four usable networks and verify reachability between them
Configure static routes on the node and explain when each route is selected over the default gateway
Resolve names through both local hosts entries and a DNS server, then force a fallback to prove precedence order
Capture and interpret traffic for a single client-server exchange at the packet level
Your checkpoint
A subnetting worksheet with the four networks, plus a packet capture annotated to show the handshake, DNS query, and response
Storage and File Systems
Create, mount, and persist at least three file systems of different types across a reboot
Extend a volume online and confirm the new capacity is visible to the file system without downtime
Set and audit permissions, ownership, and default ACLs on a shared directory used by two groups
Identify and reclaim space consumed by deleted-but-open files and oversized logs
Your checkpoint
A storage lab report containing mount tables before and after, capacity evidence for the online extension, and an ACL test matrix of allowed and denied operations
Security and Access Control
Enforce least privilege by creating role-scoped accounts and proving each role can and cannot do its intended actions
Configure key-based authentication and disable password logins, then verify the lockout
Apply file-system and service-level access controls and test them from an unprivileged context
Review audit output to confirm privileged actions are recorded with the acting identity
Your checkpoint
An access control test matrix (role, action, expected result, observed result) with audit excerpts proving privileged actions were logged
Monitoring and Troubleshooting
Instrument the node with metrics and log collection and confirm data reaches the collection point
Build two alert rules, one for resource saturation and one for service availability, and trigger each on purpose
Work a simulated incident from alert to resolution using a written triage sequence
Distinguish a resource-exhaustion symptom from its underlying cause in at least two scenarios
Your checkpoint
A runbook entry per alert containing trigger condition, first three diagnostic commands, and escalation criteria, plus an incident timeline for the simulated outage
Automation and Scripting
Automate the week 1 install steps in an idempotent script that converges on rerun without manual edits
Parameterize the script so the same code provisions two differently sized nodes from variables alone
Add error handling and dry-run output so a failed step halts cleanly and reports the failing stage
Store the script in version control with a README describing inputs, outputs, and rollback
Your checkpoint
A version-controlled idempotent provisioning script that builds two node variants from one codebase, demonstrated by a second-run diff showing no changes
Installation and Configuration & Networking Fundamentals & Storage and File Systems & Security and Access Control & Monitoring and Troubleshooting & Automation and Scripting
Rebuild the full environment from scratch using only your own runbook and automation, timing the process
Close every gap found during the rebuild by correcting the runbook or script, not by ad hoc fixes
Take two timed mixed-domain practice sets and convert each wrong answer into a one-line rule you can recall
Re-verify the weakest two domains against your original notes and update them where understanding shifted
Your checkpoint
A clean rebuild completed inside your target time with a corrections log listing each gap, the fix applied, and the domain it belongs to
Milestones
Week 2: You can rebuild the base node from your own runbook without consulting external documentation, and you can name the config file behind every setting you changed
Week 4: You can subnet an arbitrary block on paper, explain route selection for a given destination, and add capacity to a live volume without data loss
Week 6: You can take a fired alert from notification to root cause using only commands you can write from memory, and state which domain the fault belongs to
Week 8: A full rebuild from scratch succeeds on the first attempt within your time target, and your practice-set accuracy is at or above 80% in every domain