Course description and requirements
This proposed course develops practical knowledge of infrastructure operations through guided instruction, supervised technical exercises, troubleshooting and documented projects.
Course code: OPS-201 | Duration: 12 weeks | Workload: approximately 8–10 hours/week | Total: approximately 96–120 hours
Prerequisites: Linux, networking and virtualization basics
Delivery: Planned online lessons, virtual laboratories, graded assessments and instructor feedback.
Status: In development; not open for enrollment.
Learning outcomes
- Explain the technical principles covered in the course
- Configure and troubleshoot relevant systems in an authorized lab
- Apply safe operational practices and document results
- Evaluate a working implementation against defined requirements
- Communicate findings in a professional technical report
Detailed 12-week teaching plan
Week 1: Infrastructure documentation
Lesson: Study the concepts, terminology, configuration steps, common failure modes and operational considerations for this topic.
Practical lab: Build or configure a relevant component in an isolated test environment; capture configuration details and verify the result.
Evidence: Submit a lab record containing the objective, steps, results, troubleshooting notes and a short reflection.
Week 2: Asset inventory
Lesson: Study the concepts, terminology, configuration steps, common failure modes and operational considerations for this topic.
Practical lab: Build or configure a relevant component in an isolated test environment; capture configuration details and verify the result.
Evidence: Submit a lab record containing the objective, steps, results, troubleshooting notes and a short reflection.
Week 3: Service monitoring
Lesson: Study the concepts, terminology, configuration steps, common failure modes and operational considerations for this topic.
Practical lab: Build or configure a relevant component in an isolated test environment; capture configuration details and verify the result.
Evidence: Submit a lab record containing the objective, steps, results, troubleshooting notes and a short reflection.
Week 4: Metrics and alerts
Lesson: Study the concepts, terminology, configuration steps, common failure modes and operational considerations for this topic.
Practical lab: Build or configure a relevant component in an isolated test environment; capture configuration details and verify the result.
Evidence: Submit a lab record containing the objective, steps, results, troubleshooting notes and a short reflection.
Week 5: System logs
Lesson: Study the concepts, terminology, configuration steps, common failure modes and operational considerations for this topic.
Practical lab: Build or configure a relevant component in an isolated test environment; capture configuration details and verify the result.
Evidence: Submit a lab record containing the objective, steps, results, troubleshooting notes and a short reflection.
Week 6: Patch management
Lesson: Study the concepts, terminology, configuration steps, common failure modes and operational considerations for this topic.
Practical lab: Build or configure a relevant component in an isolated test environment; capture configuration details and verify the result.
Evidence: Submit a lab record containing the objective, steps, results, troubleshooting notes and a short reflection.
Week 7: Access control
Lesson: Study the concepts, terminology, configuration steps, common failure modes and operational considerations for this topic.
Practical lab: Build or configure a relevant component in an isolated test environment; capture configuration details and verify the result.
Evidence: Submit a lab record containing the objective, steps, results, troubleshooting notes and a short reflection.
Week 8: Backup strategy
Lesson: Study the concepts, terminology, configuration steps, common failure modes and operational considerations for this topic.
Practical lab: Build or configure a relevant component in an isolated test environment; capture configuration details and verify the result.
Evidence: Submit a lab record containing the objective, steps, results, troubleshooting notes and a short reflection.
Week 9: Disaster recovery
Lesson: Study the concepts, terminology, configuration steps, common failure modes and operational considerations for this topic.
Practical lab: Build or configure a relevant component in an isolated test environment; capture configuration details and verify the result.
Evidence: Submit a lab record containing the objective, steps, results, troubleshooting notes and a short reflection.
Week 10: Incident response
Lesson: Study the concepts, terminology, configuration steps, common failure modes and operational considerations for this topic.
Practical lab: Build or configure a relevant component in an isolated test environment; capture configuration details and verify the result.
Evidence: Submit a lab record containing the objective, steps, results, troubleshooting notes and a short reflection.
Week 11: Capacity planning
Lesson: Study the concepts, terminology, configuration steps, common failure modes and operational considerations for this topic.
Practical lab: Build or configure a relevant component in an isolated test environment; capture configuration details and verify the result.
Evidence: Submit a lab record containing the objective, steps, results, troubleshooting notes and a short reflection.
Week 12: Operations capstone
Lesson: Study the concepts, terminology, configuration steps, common failure modes and operational considerations for this topic.
Practical lab: Build or configure a relevant component in an isolated test environment; capture configuration details and verify the result.
Evidence: Submit a lab record containing the objective, steps, results, troubleshooting notes and a short reflection.
Five graded practical assignments
Assignment 1 — Week 2: Asset inventory
Task: Complete a practical implementation or investigation related to asset inventory. Document the requirements, approach, evidence of operation, test results and any problems encountered.
Submission: Technical report, configuration evidence and supporting files where applicable.
Marking: Technical accuracy 40%, verification 25%, documentation 25%, safe practice 10%.
Assignment 2 — Week 4: Metrics and alerts
Task: Complete a practical implementation or investigation related to metrics and alerts. Document the requirements, approach, evidence of operation, test results and any problems encountered.
Submission: Technical report, configuration evidence and supporting files where applicable.
Marking: Technical accuracy 40%, verification 25%, documentation 25%, safe practice 10%.
Assignment 3 — Week 5: System logs
Task: Complete a practical implementation or investigation related to system logs. Document the requirements, approach, evidence of operation, test results and any problems encountered.
Submission: Technical report, configuration evidence and supporting files where applicable.
Marking: Technical accuracy 40%, verification 25%, documentation 25%, safe practice 10%.
Assignment 4 — Week 8: Backup strategy
Task: Complete a practical implementation or investigation related to backup strategy. Document the requirements, approach, evidence of operation, test results and any problems encountered.
Submission: Technical report, configuration evidence and supporting files where applicable.
Marking: Technical accuracy 40%, verification 25%, documentation 25%, safe practice 10%.
Assignment 5 — Week 10: Incident response
Task: Complete a practical implementation or investigation related to incident response. Document the requirements, approach, evidence of operation, test results and any problems encountered.
Submission: Technical report, configuration evidence and supporting files where applicable.
Marking: Technical accuracy 40%, verification 25%, documentation 25%, safe practice 10%.
Midterm examination — Week 6
Proposed format: 90 minutes; multiple-choice, short-answer and scenario questions based on Weeks 1–5.
Skills assessed: Technical terminology, configuration decisions, troubleshooting and safe practice.
Actual exam questions, answer keys and marking guidance will be prepared in the instructor-only Moodle question bank.
Final examination — Week 12
Proposed format: 120 minutes; cumulative knowledge questions, troubleshooting scenarios and technical interpretation covering the full course.
Exam delivery, identity verification, accessibility accommodations and academic integrity procedures must be finalized before student assessment begins.
Capstone project
Project brief: Operate a small virtual lab with monitoring, backup, incident records and a recovery test.
Deliverables: Design plan, implementation evidence, testing checklist, results, troubleshooting record and final technical report.
Rubric: Design 20%, implementation 35%, testing 25%, documentation 20%.
Proposed grading
- Weekly quizzes — 10%
- Five practical assignments and labs — 25%
- Midterm examination — 20%
- Final examination — 20%
- Capstone project — 25%
Student preparation
A computer capable of running virtual machines or accessing an approved remote lab is recommended. Some courses may require additional RAM, storage, networking equipment or licensed software. Course-specific minimum requirements and accessible alternatives will be published before delivery.
All security testing must be limited to systems owned by the student or explicitly authorized for testing.
Academic status
This page describes a proposed curriculum. Instructors, tuition, assessment dates, enrollment and any required regulatory approvals are not yet established. No academic credit or professional certification is promised.