PG Diploma in IT Infrastructure Management

1. Make the network plan visible

Staff and guest devices connect through their own VLANs. A lab router connects those segments to the server VLAN under the access plan below. All addresses and accounts belong to this fictional example.

• Match each device address, subnet and gateway to its segment before checking a route between segments.
• Record name resolution separately from reaching the intended service: a resolved name alone does not demonstrate working access.
• Compare a permitted staff request and a denied guest request with the same stated access plan.

Curriculum connection: Networking Fundamentals & CCNA Foundations · Routing & Switching with Cisco IOS · Network Security

2. Write the access and service matrix

Set the expected result before checking an operation. A blocked guest request and a refused reader edit can both be intended results, for different reasons.

• Read the project folder

  Source / account

  staff-pc · lab-reader

  Expected result

  Allow

  Sample observation to record

  The sample account opens the project file and reads its contents.

• Edit the project folder

  Source / account

  staff-pc · lab-reader

  Expected result

  Deny

  Sample observation to record

  A write attempt is refused; the sample file remains unchanged.

• Read and edit the project folder

  Source / account

  staff-pc · lab-editor

  Expected result

  Allow

  Sample observation to record

  A permitted edit can be saved and reopened under the intended account.

• Reach the project file service

  Source / account

  guest-pc

  Expected result

  Deny

  Sample observation to record

  The service request is blocked by the example network policy; this is different from an account-level write refusal.

• Resolve files.lab.test using 10.20.30.20

  Source / account

  staff-pc

  Expected result

  Allow

  Sample observation to record

  The sample lookup returns 10.20.30.10; file access still has its own check.

Curriculum connection: Linux System Administration · Windows Server & Active Directory · Network Security

4. Show what recovery actually checked

In this example, a maintenance change leaves the file service unavailable. The recovery record keeps the VM checkpoint, file backup and service checks separate.

VM inventory

file-vm on the server segment, address 10.20.30.10; record its virtual network, storage and allocated resources.

VM checkpoint

before-maintenance — a recorded snapshot checkpoint, separate from the file backup below.

File backup

project-copy-A — a sample backup containing project-notes.txt with the baseline text “Draft A”.

Recovery destination

An isolated disposable recovery VM; preserve the original sample and its evidence for comparison.

1. 1. Capture the problem

   Record the sample service state, affected resource and most recent change.

   Keep as evidence: Keep the initial observation alongside the expected service and access matrix.

2. 2. Check the recovered copy

   Restore the sample file backup into the disposable recovery environment and inspect the result.

   Keep as evidence: Record the backup identifier, restored file and its “Draft A” contents. A VM starting is a separate observation.

3. 3. Retest service and access

   Check the service state and repeat the intended reader/editor checks on the recovered copy.

   Keep as evidence: Keep read, write and denied-write observations separately; inspect the preserved file after each check.

4. 4. Write the handover

   Explain what was restored, which checks support recovery and what remains to be tested.

   Keep as evidence: Keep the recovery sequence and remaining questions with the original fault record.

Curriculum connection: Linux System Administration · Windows Server & Active Directory · Virtualization with VMware

5. Build a handover someone else can follow

Bring the plan and observations together. Use these outputs to explore which part of infrastructure work interests you: networks, systems, security, virtualization or cloud planning.

• Network and addressing pack

  Example output: A topology, subnet/VLAN table and intended paths between devices.

  Review it: Another learner can trace a staff request from its workstation to the named server and identify the gateway at each segment.

  Curriculum connection: Networking Fundamentals & CCNA Foundations · Routing & Switching with Cisco IOS

• Accounts and services pack

  Example output: A fictional user/group matrix, service list and expected permissions.

  Review it: Read, edit and denied access have distinct evidence; service reachability is not treated as proof of permission.

  Curriculum connection: Linux System Administration · Windows Server & Active Directory

• Security findings note

  Example output: A scoped lab finding with a relevant sample packet observation, expected policy and next check.

  Review it: Separate what was observed from a proposed cause. Tie each proposed correction to an observation and a later retest.

  Curriculum connection: Network Security · Ethical Hacking & Vulnerability Assessment

• VM and recovery record

  Example output: A VM inventory, separate checkpoint/backup identifiers and the restore-check sequence.

  Review it: Explain which evidence demonstrates restored file contents, running services and intended access.

  Curriculum connection: Virtualization with VMware · Windows Server & Active Directory

• Cloud planning sketch

  Example output: A paper plan placing the example compute, storage, networking and identity requirements against the ITIM cloud module.

  Review it: Explain the IaaS/PaaS/SaaS choice and which access or migration questions the plan needs to answer.

  Curriculum connection: Cloud Computing — AWS & Azure

• Integrated lab handover

  Example output: One index connecting the plan, access tests, fault reasoning and recovery records.

  Review it: Every claimed result points to a sample observation; unresolved questions remain visible for the next learner.

  Curriculum connection: Capstone & Placement Prep