Using an operating system and file management

The governing concept is copy verification and file integrity. A file appearing in the destination does not prove that every byte was transferred correctly. Compare the original and copied file sizes, retry the transfer if needed, and test whether the copy opens or passes an integrity check. Option C is therefore correct. Renaming cannot repair damaged contents, while monitor brightness and printer drivers are unrelated to the copied file’s internal data.

The governing concept is access control. Modify permission commonly allows a user to create, edit, rename, or delete files, whereas changing permissions is normally reserved for an owner or an administrator with full control. Therefore, option D best explains the situation. Option A would prevent deletion, option B would be read-only, and option C makes an unsupported ownership claim.

The governing concept is document version management. AutoSave records recent changes automatically, but it does not necessarily provide a way to return to every earlier state. Version history or a backup may preserve previous copies and allow restoration of an older correct version. Therefore option B is correct. Recycle Bin concerns deleted items, while screen lock and file filtering do not restore document content.

The governing concept is the undo-redo history maintained by an application during an editing session. Undo reverses a recent action, and Redo can normally restore it only while that session’s history remains available. Saving and closing often ends or clears that temporary history, so Redo may not be offered after reopening. Option C is correct; file name, RAM increase, and hidden status are unrelated.

The governing concept is password-based protection of archived data. Encryption or access protection requires the correct password before the archive can be opened or its contents extracted. If the password is forgotten, the archive file still remains on the storage device, but its contents may be inaccessible. Option D is correct. The archive does not become empty, and the monitor or file name is unaffected.

The governing concept is lossless data compression. Compression algorithms can represent repeated patterns more efficiently, so text, tables, and other repetitive data may become much smaller while retaining the original information. Therefore option A is the reasonable conclusion. A reduced size does not automatically prove corruption, and it has no necessary connection with the operating system or the file name.

The governing concept is moving data across storage volumes. When a cut-and-paste operation crosses drives, the system commonly copies the file to the destination and, after successful completion, deletes the original from the source drive. Thus option B best describes the technical result. Renaming, shortcut creation, and compression are different operations and are not required by moving a file.

The governing security concept is least privilege: a user should receive only the access needed to complete the assigned task. If the task requires one folder, permissions should be limited to that folder and should not provide broad control of the computer. Full control, removing passwords, or making files public increases exposure and violates secure access practice. Therefore, option A is correct.

The governing concept is permission inheritance in a parent-child folder structure. When inheritance is enabled, a subfolder or file can automatically receive access permissions from its parent folder, which simplifies administration but may also extend access farther than intended. Compression changes storage size, conversion changes format, and formatting prepares a disk. Thus, option B correctly names the process.

The governing concept is inheritance control. A subfolder commonly receives permissions from its parent, so making its access different may require disabling or breaking permission inheritance and then assigning explicit rights to the required users or groups. Changing an extension affects how a file is identified, emptying the Recycle Bin removes deleted items, and replacing a monitor has no permission effect. Therefore, option C is correct.

The governing concept is confidentiality through encryption. Encryption transforms readable data, called plaintext, into protected ciphertext that should be unintelligible without the appropriate key or password. This helps prevent an unauthorised person from understanding the file even if the file is copied or accessed. It does not necessarily reduce size, print the file, or rename it, so option D is correct.

The governing concept is key-dependent access control. An encrypted file can normally be read only after the correct encryption key, password, or recovery credential is supplied. If that key is lost and no valid recovery method exists, even the legitimate owner may be unable to decrypt and open the data. Losing a key does not decompress a file, damage a monitor, or improve operating-system speed. Therefore, option A is correct.

The governing concept is backup validation and restore testing. Creating a backup does not prove that every file was copied correctly or that the stored data can be restored. A backup may be corrupted, incomplete, inaccessible, or incompatible with the recovery process. Testing restoration reveals such problems before an emergency occurs. It does not guarantee success merely because it exists, nor does it rename files or reduce RAM; option B is correct.

The governing concept is synchronisation across connected devices. When synchronisation is active, a saved change on one device may be uploaded and then replicated to other devices using the same shared or cloud-managed file. Consequently, an incorrect edit can spread rather than remain local. It is not guaranteed that the file will be deleted, and printer operation is unrelated. Thus, option D is correct, while a separate backup may help recovery.

The governing concept is the different purpose of synchronisation and backup. Synchronisation keeps files or folders aligned across devices by propagating current changes, which can also spread mistakes. A backup creates a separate copy intended for recovery after deletion, corruption, or other loss. Therefore, option A gives the accurate distinction; the other options incorrectly describe unrelated effects on names, internet speed, or RAM.

The governing concept is version conflict during cloud synchronisation. If the offline copy and the cloud copy were changed separately, reconnecting may reveal different versions of the same file. The service may need to compare timestamps or edits and ask the user whether to keep, merge, or replace a version. Deletion is not inevitable, and monitor or operating-system changes are unrelated. Therefore, option B is correct.

A checksum is a calculated value representing a file’s contents. When the same file is checked again, its checksum should normally match the trusted value. If the size is unchanged but the checksum differs, the contents may have been altered, damaged, or affected by an incomplete transfer. Therefore, option C is correct; file name, monitor settings, or equal size do not prove file integrity.

The official checksum acts as an integrity reference for a download. A mismatch means that the file may have been corrupted during transfer, incompletely downloaded, or changed by an untrusted source. It should not be opened or executed. Stop using it, obtain a fresh copy from the official or otherwise trusted source, and verify the new checksum before use. Renaming it or disabling antivirus cannot repair its contents.

An operating system may lock a file while an application or background process is reading or writing it. Closing the program that uses the file releases that active handle and allows deletion to be attempted safely. Cutting power can cause data loss, emptying the Recycle Bin is unrelated, and changing the extension does not stop the process. Thus, option A follows normal file-management practice.

Closing an application window does not always terminate every process connected with it. A background process may still hold the file open, so the operating system continues to report a lock. The appropriate approach is to inspect the related process with a task-management tool, close it safely, and restart the system if necessary. Permanently deleting or formatting the disk is risky and unnecessary, while replacing a monitor is irrelevant.

Operating systems require available disk space for temporary files, caches, logs, virtual-memory support, updates, and routine operations. When free space becomes very low, updates may fail, applications may behave poorly, and overall performance can decline. Low space does not inherently change mouse colour, printer speed, or file-name length. Therefore, option D correctly describes the likely effects of insufficient storage.

If routine cleanup does not provide enough space, the next step is to inspect storage usage and locate large, unnecessary files such as obsolete downloads or duplicate media. Their importance should be checked, and important data should be backed up before deletion. Files that are still needed can be moved to reliable external storage. Password removal, extension changes, or deleting a mouse driver will not meaningfully solve low disk space.

Effective file organisation uses a meaningful hierarchy and consistent naming convention. Separate subfolders based on topic, date, project, or document type reduce the search area, while names containing useful details make sorting and identification easier. Giving every file the same name creates confusion, removing extensions hides type information, and hiding files does not improve maintenance. Thus, option C is the best organisational practice.

A filename alone is not a unique identity when duplicates exist. Reliable identification combines the folder path or location, modified date, file type or extension, and, when necessary, a preview or check of the contents. An icon colour, list position, or file size alone can be misleading because different files may share those properties. Therefore, option D provides the strongest basis for selecting the intended file.

The governing concept is meaningful file naming. A vague name does not describe the file’s subject, date, owner, or version, so locating the correct document becomes difficult when many files accumulate. It may also cause a person to open or edit the wrong version. Therefore, option B is correct. A name alone cannot automatically increase file size, delete a file, or consume RAM; those distractors describe unrelated system effects.