Example coursework · Independent teaching demonstrations
← All eight weeks · Course syllabus204 / WEEK 6 / a+ Cyber Foundations / Foundation curriculum v1.0
Linux systems and secure server basics
Monday, February 15, 2027 · 5:45–8:45 PM · America/Chicago
Use basic Linux evidence to explain account, permission and application-service protection.
HOW THIS MODULE FITS COURSE 204
CompTIA a+ Cyber
Use basic Linux evidence to explain account, permission and application-service protection.
Foundation curriculum: CompTIA a+ Cyber Foundation curriculum v1.0.
PREPARATION / DUE BEFORE CLASS
Review the lessons. Complete the handout.
Due Monday, February 15 before 5:45 PM. Read the assigned material, review assigned slides and fill out every handout response before arriving. This preparation is required for the opening quiz; it is not work to postpone until the hybrid deadline.
CompTIA a+ Cyber, public CompTIA curriculum v1.0 topic map: 7 — Linux application-server fundamentals. Read the corresponding licensed digital lessons and instructor handout before class. Exact lesson IDs, current licensed revision and any textbook edition must be verified in the instructor's account; no print ISBN is assumed.
Public topic map checked; licensed lesson IDs pendingPreparation checklist
- Read each assigned chapter actively: define unfamiliar terms and connect concepts to a support example.
- Review the assigned slides, diagrams and procedures; identify prerequisites for each chapter lab.
- Complete the handout in your own words with page or section references, a troubleshooting plan and two questions.
- Submit the graded handout before 5:45 PM and arrive with access to the authorized lab environment.
Week 6 preparation handout
Original preparation handout — week 6 Review CompTIA a+ Cyber topics 7: Linux application-server fundamentals. 1. Define five relevant terms in your own words with a beginner support example. 2. Explain the learning outcomes with licensed lesson or instructor reading references: Use basic Linux evidence to explain account, permission and application-service protection. 3. Answer the reading-check prompts with reasons: Explain ownership and permissions; identify a Linux evidence source; justify a least-privilege change. 4. Draw a simple workflow or topology and identify one safe support or protection decision. 5. List lab prerequisites, permissions, evidence, rollback and escalation boundaries. 6. Bring two questions. Complete all responses before Monday 5:45 PM.
This is a graded assignment within the 5% preparation/documentation category. Submit your completed responses as “Handout” below and bring them to class. Record chapter page or section references and your own explanations.
HYBRID / OUTSIDE OF CLASS
Your independent work
Due Sunday, February 21, 2027 at midnight, end of day.
The submission window ends Monday, February 22 at 12:00 AM America/Chicago. Monday class → following Sunday deadline.
1. Foundation practice — every week
Complete at least 45 foundation-level questions across assigned licensed lesson checks and an instructor-approved practice set. Identify the source, question count, result and corrections for three weak concepts. Clearly label remediation reattempts; these do not represent 45 unseen vendor questions. A dedicated MeasureUp product for this foundation course has not been verified; Network+ or Security+ practice is not automatically required.
2. Approved remote labs — graded assignments
Your weekly remote-lab portfolio is graded within the 20% lab category. The instructor assesses the work and evidence for each assigned lab; completion alone is not full credit.
Complete every approved remote-lab title assigned to this week. More than one lab may be required when several titles match the chapter material. Plan the assigned NETLAB work for the weekend after class. Reserve lab time early and allow time to troubleshoot, repeat steps and document results. Submit a remote-lab portfolio with a separate section and completion evidence for each assigned title.
Chapter/topic matching keywords: Linux account management permissions server logs. Only instructor-approved title matches below are assigned. If none are listed, the catalog match is pending; do not assume that an unrelated lab satisfies the requirement.
Beginner lab candidates — approval pending
Linux Account Management (basic ownership and permission checks)
These are instructor-scoped supplements from the available NDG networking/security libraries, not a verified dedicated a+ Network or a+ Cyber lab package. The instructor must approve installed access, difficulty and exact topic match. Licensed course labs may be assigned instead; submit each exact title in the graded remote-lab portfolio.
3. Reinforcement and reflection
Complete a minimum of 45 foundation-level review questions across instructor-assigned lesson checks and an approved practice set. Record count, source/lesson, results and corrections for three weak concepts. Reattempts are allowed only after explaining the correction and must be identified; 45 questions does not imply 45 unseen vendor questions. No dedicated MeasureUp product for CompTIA a+ Cyber has been verified. A Network+ or Security+ practice test is not automatically assigned to this beginner course. Complete each approved basic NETLAB+ or licensed course-lab title and submit a separate evidence section for each, including steps, interpreted results, troubleshooting and validation. Candidates: Linux Account Management (basic ownership and permission checks). Instructor must confirm installed access, level and topic scope. Submit a reflection and professional handoff by Sunday at end-of-day midnight. Reading/handouts are due before class; quizzes and classroom labs are supervised. Week 8 also requires the separately scheduled instructor final, not a certification exam.
Time and dedication
CompTIA a+ Cyber is one eight-week beginner foundation block. Plan 6–9 hours of independent reading, lesson review, handouts, practice questions, lab evidence and remediation weekly, plus the three-hour meeting (9–12 total). This college-style example expands the vendor's core topics with supervised practice and professional documentation; the estimate is not a vendor duration or a college credit-hour determination. No prior networking or cybersecurity job experience is assumed, but basic computer use and reliable access to the authorized lab environment are needed. Read before class, spread practice across the week and reserve weekend lab time. Taking both foundation examples at once would mean 18–24 total hours weekly and requires a conflict-free schedule arranged by the instructor.
IN CLASS ONLY / 5:45–8:45 PM
Prepare → Quiz → Chapter labs → Closeout
5:45–6:00 · Start-of-class quiz
Take the reading quiz at the beginning of class. Answer each prompt with a technical explanation; prompts are equally weighted.
Explain ownership and permissions; identify a Linux evidence source; justify a least-privilege change.
Use your preparation to explain the answer and the reason for it. Review missed concepts during closeout and add corrections to your study notes.
6:00–8:10 · Foundation lab workshop
This module currently has 2 lab activities, approximately 60 minutes each, excluding the 7:00–7:10 break. The instructor may scope the tasks and demonstrations to fit the session. Weeks may use one extended lab, two standard labs, or three to four short chapter activities.
Lab 1
Inspect test accounts and file permissions in an isolated Linux VM. Correct one instructor-authorized permission fixture and verify allowed and denied access without changing production files.
- Identify the support request, required outcome, authorized environment and safety or rollback precautions.
- Record the starting configuration and symptoms. Predict the expected result before changing anything.
- Perform the assigned procedure, capture relevant commands or settings, and troubleshoot unexpected results.
- Verify the outcome with a repeatable test. Submit your observations, evidence, explanation and a concise service handoff.
Lab 2
Inspect a test service's configuration and logs using approved commands. Identify excessive access or a service problem in supplied evidence and produce a concise recommendation and escalation record.
- Identify the support request, required outcome, authorized environment and safety or rollback precautions.
- Record the starting configuration and symptoms. Predict the expected result before changing anything.
- Perform the assigned procedure, capture relevant commands or settings, and troubleshoot unexpected results.
- Verify the outcome with a repeatable test. Submit your observations, evidence, explanation and a concise service handoff.
This is an original provisional sequence. Confirm chapter alignment and lab scope against the licensed text; the exact textbook lab sequence has not been extracted. In-class lab work and its evidence are completed in the supervised class period, not assigned as weekend hybrid work.
8:10–8:45 · Closeout lecture, Q&A and announcements
Debrief linux systems and secure server basics: explain one result, correct missed concepts, connect the activity to CompTIA Security+ readiness, answer questions and confirm next reading and Sunday deadline.
Connect lab results to certification concepts, resolve questions, review common errors, and confirm announcements, next week's reading and the hybrid deadline. Any make-up arrangements require instructor approval.
Assigned chapter slides and external resources
Licensed chapter PowerPoints and verified provider links are awaiting instructor setup. Sign in to access approved materials. Preparation prompts and original class activities are shown above.
Your submissions
Handout: before class. Quiz and classroom labs: in class only. Weekly practice, assigned remote-lab portfolio and reflection: the hybrid deadline shown above. These are separate requirements.
Sign in to submit work and view feedback.