#Working in a Module

Opening a module takes you to the console, where you work on a real virtual machine. Your VM is a private clone of a known-good template. Treat it as you would a system you support.

#Stay within the briefing

The briefing defines the task. Changes outside that scope can cost points, even if the rubric does not name them.

• Do only what the briefing asks.
• Do not change passwords unless asked.
• Prefer changes you can undo; move files aside instead of deleting them.
• Do not weaken security settings you were not asked to change.
• Do not run system updates or upgrades. They can change the environment and waste time.
• Do not rely on automated scans. The module tests your troubleshooting skills.

#Your module's network

Your module has its own private network. No other student can see or reach its VMs.

Some modules have one VM; others have several, such as a client and server. All VMs start together and keep running while you work. Use Switch VM in the console menu to move between them.

The briefing explains each VM's role, addresses, and network layout. See Multi-VM Networking for connectivity details and Switching Between VMs for console behavior.