The operating system provides services that applications use to manage processes, memory, files and devices. A process is a running program with allocated resources. Installing an application adds a tool to the environment; installing a system prepares the foundation that manages many tools. Users and their permissions determine which operations they can perform on files and settings. The usefulness of the whole depends on the task and the person using it.

In a virtual machine, a hypervisor supplies virtual hardware to a guest system within a host. The host supplies real resources: allocated RAM and storage do not appear from nowhere. Seeing two desktops does not mean having two independent physical computers. An installation image is the source medium; the virtual disk is the installation destination. Identify both and verify compatible architecture before continuing. Virtual practice still depends on its host computer and requires a recovery plan of its own.

A reproducible installation begins with purpose, requirements, origin and destination. The image must come from the official project and match the prepared architecture and version: ARM and x86 are not interchangeable because their desktops look similar. Integrity checks establish that the file matches the published reference; provenance also requires the appropriate distribution channel. The teacher selects image, hypervisor and resources for the available computers, without requiring installation on personal devices.

Before changing storage, identify the name, size and function of the authorised destination and the planned recovery mechanism. The teacher verifies that destination before erasing or partitioning. Record relevant decisions such as language, accessibility and working account, rather than every installer message. Giving the guest more memory may harm the host if it is left without resources. Acceptance includes starting the installed system, signing in, saving, restarting and retrieving a file. Seeing the installer or a desktop alone does not establish these checks.

An account identifies a working context and brings together permissions to act. A standard account supports ordinary tasks; administration has greater reach over the system. Least privilege means granting only the permissions needed for a purpose. Elevating privileges for an authorised operation does not mean keeping them throughout the session. Sharing one account across every function makes changes harder to attribute and access harder to control.

Reading, editing, commenting and executing are not equivalent actions, and availability depends on the system and tool. In a folder, reading permits consultation; writing may permit changes; execution has a specific meaning for system files and directories. Shared documents add their own roles, such as viewer or commenter. Define owner, audience and purpose before configuring them. Hiding a file does not necessarily prevent access. Use another prepared account to test each role: the author’s access does not demonstrate the reviewer’s. The policy should allow collaboration without unnecessary exposure.

Maintenance keeps an environment usable and reduces known problems. Distinguish operating-system, application and available protection updates: checking one does not establish the others. Consult status and origin, prepare recovery and verify the outcome. A pending-update notice does not mean installation is complete. Restarting may be part of the process, but final verification should include an ordinary task to detect unwanted effects.

Authentication checks a claimed identity through the service’s mechanisms. Long, unique credentials and an additional factor where available reduce certain risks, but do not replace protection of an open session. Practice uses fictional accounts and secrets; the record describes configuration and verification without copying their values. Review protection tools compatible with the system and school policy: installing several from doubtful sources may create problems. Record status, action, date and planned frequency. Signing out on shared computers and checking what remains accessible are also maintenance tasks.

File organisation makes work easier to find; a backup allows preserved information to be recovered after an incident. These related functions require different decisions. The Sources, Editable work and Exports folders separate materials by function, while names and versions identify their contents. The backup plan states what is preserved, where, how often and how it is restored. Its usefulness depends on the required information surviving: a copy in another folder on the same disk may help after accidental editing, but not after loss of that entire storage device.

This dependency also explains the differences between mechanisms. A snapshot records a virtual-machine state according to the hypervisor and configured disks; it may depend on the same host, and restoring it may undo later changes. History preserves particular document versions without necessarily covering the whole system. Synchronisation keeps locations related and may propagate a deletion. The available protection is therefore understood by connecting each mechanism with the anticipated failure and its actual recovery options.

Restoration checks this relationship using a fictional file with known content. Recovering it to another destination while preserving the original allows expectation and outcome to be compared without destroying valid work. Opening the file and recognising its version establishes more than seeing an icon: it verifies usable content. The conclusion identifies which incident the test covers and which dependencies remain untested.

A personal learning environment, or PLE, connects resources, tools, people and procedures that make learning possible. Its organisation follows a pathway: a question leads to searching for information; selection preserves what is relevant; creation applies learning, and review helps improve it. Sharing connects this work with other people. A list of applications therefore does not describe the environment on its own. The map shows how these functions relate and what each resource contributes to the process.

A specific question guides source selection. Authorship, purpose, date, version and evidence help establish whether information suits the working environment. A primary source directly documents a procedure, while an educational explanation may help make sense of it. Both functions are useful, although two pages repeating the same origin do not automatically provide two independent checks. Similarly, an old tutorial may explain a stable concept while showing menus that no longer match the version in use.

Archiving sources with context makes it possible to learn from them again. Each record preserves the link, claim used, limitation and a retrievable location; this reveals why the resource was chosen and when it should be reviewed. A01 begins with two compared sources, and the collection expands to three. The PLE demonstrates its usefulness when it enables a source to be retrieved, applied to a task and reviewed with others, without adding unnecessary accounts or personal data.

A reproducible guide preserves prerequisites, decisions, actions and expected results. It explains each step’s function so different menus can be accommodated without changing the purpose. “Configure the usual settings” cannot be repeated. A screenshot supports instructions but needs text and must exclude personal accounts, secrets and unnecessary identifiers. Documentation connects the installed system with permissions, maintenance, backup and the learning environment, rather than presenting isolated tasks.

Testing with another pair starts from a known prepared state. If a prerequisite or permission is missing, record the difficulty and improve the guide before repeating. A01 contains the minimal installation, save test and initial checks actually performed; A02 demonstrates the complete configuration, restart, permissions, maintenance and restoration with verified content. Each member retrieves a personal-learning-environment resource and explains its usefulness. Practice and review belong to these two submissions. Distinguish physical execution, operations within a virtual machine and actions only represented by simulated material.