Using an operating system and file management

The governing concept is safe account removal and data preservation. A user account may contain documents, photographs, settings, or work that other people still need. Before deletion, identify important data, back it up, and transfer it to an authorised location; then confirm that no required files remain. Therefore option D is correct. Monitor colour and mouse speed are irrelevant, and a printer queue does not protect the account’s stored files.

The governing concept is privacy and access control on a shared computer. A personal account separates one user’s files and permissions from other users, while saving work correctly and logging out prevents the next person from accessing an open session. Therefore option A is the safest practice. Sharing passwords removes accountability, a public folder exposes private files, and minimising a window does not close the session or protect data.

The governing concept is the separation between a data file and its associated application. Uninstalling the application may remove the program and its file association, but it does not normally erase the separately stored document. Without a compatible application, the file may remain visible yet fail to open or display correctly. Therefore option A is correct; automatic deletion, size doubling, and conversion into RAM are not normal consequences.

The governing concept is permission-based access control. Read permission allows a user to open and inspect a file, whereas write or modify permission is required to change and save its contents. The described behaviour therefore indicates read access without write access, making option B correct. A long name or small size does not normally determine editing rights, and monitor resolution affects display quality rather than authorisation.

The governing concept is change tracking. Version history stores identifiable earlier states of a document, often with times or authors, so a user can inspect what changed and restore an earlier state after an accidental or incorrect edit. Therefore option A is correct. It does not increase storage capacity, accelerate booting, or make files public, so B, C, and D are distractors.

The governing concept is process scheduling and processor sharing. If one process occupies the CPU for too long without yielding, the scheduler may give other processes fewer opportunities to run. This causes poor responsiveness, longer waiting time, and possible starvation. Therefore, option D is correct; the other options describe unrelated effects on files, storage, or monitor hardware.

A root directory is the top-level starting point of a storage volume or file-system hierarchy. A full or absolute path can be traced from this root through each folder until it reaches the file, making the location independent of the user’s current folder. Option A is correct. The root does not compress, encrypt, or convert the file.

The governing idea is path resolution. A relative path describes a route to a file beginning from the current working directory, such as a child folder or a parent indicated by “..”. Its meaning can change when the starting directory changes. Option B is correct; storage size, modification date, and monitor resolution do not determine a relative path.

In a file system, a directory entry connects a human-readable file name with information used to locate and manage the file. Depending on the system, it may reference storage blocks and include attributes such as type or permissions; it does not normally contain the entire content. Thus option C is correct, while the other choices are unrelated or overly narrow.

The governing concept is that file size measures the quantity of stored bytes, not the exact values or order of those bytes. For example, two text files can each contain 100 bytes while containing different words. Therefore option B is correct. Equal size does not prove identical content; corruption is not necessary, and the operating system normally reports the stored size correctly. A checksum or direct comparison is better for checking equality.

The governing concept is access control through file permissions. Execute permission allows the operating system to start a suitable executable file or script, subject to other requirements such as a valid format. Option C is correct. Read permission concerns viewing data, write permission concerns changing data, and neither renaming nor compression is the meaning of execute permission.

The governing security principle is least privilege: each account should receive only the access needed to complete its assigned work. Option D is correct because it limits the possible damage from mistakes, malware, or unauthorized actions. Full administration, public files, and removing passwords increase exposure rather than reduce it. A standard account is normally preferable for routine tasks.

The governing concept is the separation between identity and access rights. Ownership records which user or group is associated with controlling a file, while permissions specify actions such as reading, writing, or executing it. Option A is correct. Ownership does not itself describe file size or automatically change content, and ownership and permissions need not be identical.

The governing concept is permission-based access control. Read access allows a user to list or open permitted existing files, but changing contents, creating files, deleting items, changing permissions, or taking ownership normally requires additional rights. Therefore option B is correct. The word “generally” recognizes that exact behavior can depend on the operating system and separate permissions.

The governing reliability concept is that a backup is useful only when its data can actually be recovered. A restoration test can reveal missing files, corruption, incompatible software, incorrect credentials, or an incomplete backup chain. Option C is correct. File-name length, monitor display, and the permanence of main memory do not determine whether restoration will succeed.

The governing concept is differential storage of changes over time. An incremental backup copies files changed since the immediately preceding backup, whether that earlier backup was full or incremental. Option D is correct. It usually saves time and storage compared with making a full copy each time, but restoring may require the relevant full backup and every required incremental backup in sequence.

The governing concept is two-way synchronization, in which additions, edits, and deletions are treated as changes to be propagated between linked locations. Therefore option A is correct: deleting an item in one location may cause the service to delete its synchronized copy elsewhere. This behavior depends on the service’s settings and is why synchronization should not automatically be treated as an independent backup.

The governing concept is preserving multiple historical states of a file. Version history records earlier saved versions, so a user can inspect changes and restore an earlier state after an accidental edit, deletion, or unwanted revision. Option B is correct. It does not increase hardware memory, automatically change the file format, or affect processor temperature; it is a recovery feature related to, but distinct from, a normal backup.

The governing collaboration concept is version control. When users edit separate copies, both may change the same paragraph, table, or setting in different ways. Combining the copies can create conflicting edits, duplicated content, or uncertainty about which version should be kept. Option C is correct. Monitor resolution, zero file size, and erasing the operating system are not normal consequences of merging document versions.

The governing concept is metadata-based indexing: the system stores descriptive details such as a file name, type, date, size, location, and sometimes content keywords in a searchable index. When a user searches, these details help locate matching files quickly without examining every file from the beginning. Therefore, option D is correct. Indexing does not permanently delete files, encrypt every file, or increase physical storage capacity; it mainly improves retrieval speed.

The governing concept is transfer integrity. A progress bar may reach the end even when a connection error, incomplete write, or corrupted data has occurred. Opening the destination file checks usability, while comparing its size or checksum with the source gives stronger evidence that the contents match. Thus option A is correct. Deleting the source before verification risks permanent data loss, and shutting down or merely watching the display proves less.