Applications and Software practice questions

Archive

Why it fails: The Archive attribute merely flags a file as changed since the last backup, so backup software knows what to copy; it imposes no write protection whatsoever. It is tempting because it appears in the same attributes list as Read-only, but it serves backup tracking, not accidental modification prevention.

System

Why it fails: The System attribute marks a file as required by the operating system, which is why Windows hides it and warns before deletion; it does not block modification. It is tempting because system files are protected in practise, but that protection comes from permissions, not the attribute itself.

Hidden

Why it fails: The Hidden attribute only removes the file from default directory listings; anyone who enables viewing of hidden files can still modify or delete it freely. It is tempting because hidden files feel protected, but concealment is not access control — Read-only is what blocks writes.

Slack

Why it fails: Slack is a proprietary team messaging and chat platform; it does not host corporate email mailboxes or provide document editing and storage. It is tempting because it enables cloud-based collaboration across devices, but the scenario requires email and document collaboration, which Slack does not deliver.

Microsoft 365

Why it fails: Microsoft 365 can be cloud-based but the question asks for the category, not a specific product. However, Google Workspace is explicitly a web-based productivity suite.

Zoom

Why it fails: Zoom provides video conferencing, not email or document collaboration, so it cannot host mailboxes or shared files accessed via browser. It is tempting because Zoom is cloud-based and browser-accessible, making it the right choice for virtual meetings, webinars or remote team calls.

Slack

Why it fails: Slack provides channels, messaging and file sharing, but no word processor, spreadsheet engine or mailbox. It is tempting because it is cloud-based and supports real-time collaboration, which suits team communication and integrations, not document authoring or email, so it fails the suite requirement.

Microsoft 365

Why it fails: Microsoft 365 does offer cloud-based apps, but the question specifically highlights real-time collaboration, which is a hallmark of Google Workspace.

Zoom

Why it fails: Zoom delivers video meetings, webinars and chat, but no word processing, spreadsheet or email client. It is tempting because it is cloud-based and enables real-time collaboration, which suits virtual meetings and screen sharing, not document creation or mailboxes, so it misses the suite requirement.

Open source

Why it fails: Open source grants rights to use, modify and redistribute source code freely; it does not impose a 30-day expiry requiring payment afterwards. It is tempting because free-of-charge downloads are often open source, and would be correct if the licence permitted perpetual unrestricted use.

Freeware

Why it fails: Freeware grants unlimited use at no cost, with no expiry or payment trigger, so it cannot describe a 30-day trial that then demands payment. It is tempting because freeware is also downloaded free of charge, but the defining axis is permanence versus time-limited evaluation.

Shareware

Why it fails: Shareware often has limited features or a trial period, but the term 'trial' is more specific here.

/home/user/Report.docx

Why it fails: A leading forward slash denotes an absolute path from the filesystem root, so it resolves identically regardless of the current working directory. It is tempting because Unix users habitually type such paths, but relative paths are resolved against the present working directory instead.

C:\Users\Report.docx

Why it fails: This is an absolute path starting with a drive letter.

\\Server\Share\Report.docx

Why it fails: A UNC path beginning with a double backslash is absolute, anchored to a named server and share rather than the current directory. It is tempting because network paths feel contextual, but they resolve identically from any working directory, which is the defining property of an absolute path.

Compile

Why it fails: Compile is not a Git command; it typically refers to converting source code into executable code.

Increase

Why it fails: Git has no "increase" operation; its commands are verbs like commit, push, pull, branch and merge. The term tempts because version numbers increment, but that is semantic versioning, not a Git action. Increase belongs to arithmetic or counter contexts, not version control.

Push

Why it fails: Push is also a Git operation, but it is not selected as one of the two correct answers in this context.

INSERT (OrderID, CustomerID, OrderDate, TotalAmount) INTO Orders VALUES (1, 101, '2023-01-15', 50.00)

Why it fails: Incorrect. The column list must come after the table name, not before INTO. Correct syntax: INSERT INTO Orders (OrderID, ...) VALUES (...).

INSERT Orders VALUES (1, 101, '2023-01-15', 50.00)

Why it fails: Incorrect. The keyword INTO is required. Correct syntax: INSERT INTO Orders VALUES (...).

Shareware

Why it fails: Shareware is a proprietary distribution method permitting trial use before payment; source code stays closed. Open-source licences such as MIT, Apache 2.0 or GPL grant rights to inspect, modify and redistribute source code. Shareware would be correct if the question asked about try-before-you-buy distribution models.

Commercial license

Why it fails: A commercial licence is proprietary, granting usage rights under restrictive terms while withholding source code. Open-source licences such as MIT, Apache 2.0 or GPL explicitly permit source inspection, modification and redistribution. Commercial licensing would be the answer if the question asked how vendors restrict and monetise proprietary software.

Freemium

Why it fails: Freemium is a commercial distribution model offering a free tier with paid premium features; it grants no source-code rights. Open-source licences such as MIT, Apache 2.0 or GPL explicitly permit use, modification and redistribution of source code. Freemium would be the answer if the question asked about software monetisation strategies.

Boolean

Why it fails: Boolean is for true/false values, not numbers.

Character

Why it fails: Character is for single characters like 'a', not numbers.

String

Why it fails: String is for text, not numeric values.

An open source license delivered only as compiled binary files

Why it fails: Open source licensing does allow free use, but the scenario specifically describes a commercial productivity suite purchased once. Restricting delivery to compiled binaries also removes the source code access that defines open source distribution, so this choice misrepresents both the licensing model and the delivery method the owner is seeking.

A subscription license delivered through a cloud-based service

Why it fails: A subscription license requires ongoing periodic payments to keep the software usable, which directly conflicts with the owner's goal of avoiding recurring fees. Although cloud delivery would eliminate physical media, the continuing cost and the dependency on an active subscription make this model unsuitable for a business that wants indefinite use after one payment.

A site license delivered on a single shared network drive

Why it fails: A site license does cover many machines under one agreement, but it is typically a recurring or annually renewed arrangement rather than a single indefinite payment, and the scenario does not mention a central network share. Placing the installer on a shared drive is a deployment detail, not a licensing model that guarantees indefinite use.

LDAP

Why it fails: LDAP (Lightweight Directory Access Protocol) is used to access and maintain directory services, such as looking up contact information. It does not handle email retrieval or synchronization. While it can be used for address book lookups, it does not download email messages or synchronize mailboxes, so it is irrelevant to the user's scenario.

SMTP

Why it fails: SMTP (Simple Mail Transfer Protocol) is used for sending outgoing email, not for retrieving or synchronizing incoming messages. It does not download email to a client or manage mailbox synchronization. While essential for sending mail, it does not address the user's need to download and synchronize email across devices, so it is not a correct choice.

POP3

Why it fails: POP3 (Post Office Protocol version 3) downloads email from the server to a single device and typically deletes messages from the server. This means the mailbox is not synchronized across multiple devices; other devices would not see the same messages. While it stores email locally, it fails the requirement for synchronization across devices, making it unsuitable for this scenario.

A Type 2 hypervisor and a virtual hard disk

Why it fails: A Type 2 hypervisor is appropriate for desktop virtualization, and a virtual hard disk stores the guest OS. However, a virtual hard disk alone does not provide internet access or file sharing with the host. Networking requires a virtual network adapter, so this pair is incomplete for the stated requirements.

A Type 1 hypervisor and a physical network switch

Why it fails: A Type 1 hypervisor runs directly on hardware, typically in data centers, not as an application on a desktop OS. A physical network switch is not needed for a single desktop VM. This combination does not match the scenario of running a VM on a Windows 10 Pro desktop for testing.

A guest OS and a USB flash drive

Why it fails: A guest OS is installed inside the VM, but it is not a component that is installed and configured to provide networking and file sharing. A USB flash drive can transfer files manually but does not provide internet access. This pair does not satisfy the connectivity and sharing requirements.

.msi

Why it fails: The .msi extension denotes a Windows Installer package, which macOS cannot execute natively. macOS installer packages use .pkg, so this option would only be right when deploying software to Windows endpoints through Group Policy or similar tooling.

.exe

Why it fails: .exe is the Windows executable format, which macOS does not use for installer packages. It is tempting because .exe files are commonly downloaded installers, but macOS packages use .pkg or .dmg; .exe would not run natively on macOS without emulation or translation layers.

.dmg

Why it fails: .dmg is a macOS disk image used for distributing applications, not the installer package format itself. It is tempting because .dmg files are ubiquitous macOS downloads, but the question asks for the installer package extension, which is .pkg; a .dmg typically contains an app or a .pkg inside.

.dmg and .pkg

Why it fails: Linux distributions package software as .deb (Debian/Ubuntu) or .rpm (RHEL/Fedora) archives, not .dmg or .pkg. Those Apple formats are tempting because they are the standard installers on macOS, so they would be correct for a macOS question rather than this Linux one.

.app and .apk

Why it fails: Linux uses .deb and .rpm packages; .app is a macOS application bundle and .apk is an Android package. Both are tempting because they are genuine install formats on their own platforms, but neither is executed by Linux package managers such as apt or dnf.

.exe and .msi

Why it fails: Linux installs via .deb and .rpm packages; .exe and .msi are Windows executables and installer databases. They are tempting because they are the most familiar installer types, and would be correct for a Windows question, but Linux does not natively run them.

Manual installation

Why it fails: Manual installation requires a technician to click through setup on each machine, so it cannot run unattended across 50 computers. It is tempting because it gives full control and suits one-off installs or troubleshooting, but the scenario demands no user interaction, which unattended deployment provides.

Installation from an app store

Why it fails: App stores typically prompt for user sign-in and confirmation per device, so they cannot install silently across 50 machines. They are tempting because they simplify licensing and updates for individual users, but they lack the centralised, non-interactive deployment mechanism this scenario requires.

Trial installation

Why it fails: A trial installation is time-limited software evaluation, not a deployment method, so it cannot install a full product unattended on 50 computers. It is tempting because trials install quickly for testing, but the scenario needs a repeatable silent deployment, not temporary evaluation software.

Compiled language

Why it fails: Python executes directly through an interpreter without a separate compilation step, so classifying it as compiled contradicts the scenario. It is tempting because compiled languages also produce runnable programs; it would be correct for languages such as C or Go, where source is translated to machine code before execution.

Markup language

Why it fails: Markup languages such as HTML or XML describe document structure and presentation; they contain no executable logic, so Python cannot be one. It is tempting because both are text-based languages; it would be correct when the code defines tags and formatting rather than performing computation or control flow.

Query language

Why it fails: Query languages such as SQL retrieve or manipulate data held in databases; they do not implement general-purpose program logic, so Python is not one. It is tempting because both are interpreted; it would be correct when the code issues statements against a data store rather than building applications.

Apple Safari

Why it fails: Safari is a genuine web browser, so it cannot be the item that is not one. It is tempting to select because it ships only on Apple platforms, which can make it feel like a system component rather than standalone software, but it renders web pages and would be correct if the question asked for a browser bundled with macOS or iOS.

Mozilla Firefox

Why it fails: Firefox is a genuine web browser, so it cannot be the item that is not one. It is tempting to select because it is developed by a non-profit foundation rather than a large platform vendor, which can make it seem unlike mainstream browsers, but it renders web pages and would be correct if the question asked for an open-source browser.

Google Chrome

Why it fails: Chrome is a genuine web browser, so it cannot be the item that is not one. It is tempting to select because Google is primarily known for search and cloud services, which can obscure that Chrome itself is browser software, but it renders web pages and would be correct if the question asked for a Chromium-based browser.

An application that runs only on mobile devices

Why it fails: A web application is delivered over HTTP/HTTPS and accessed through a browser, so restricting it to mobile devices describes a native mobile app instead. It is tempting because many web apps are consumed on phones, yet browser-based delivery across any platform is the defining characteristic.

An application installed locally that has direct hardware access

Why it fails: Local installation with direct hardware access describes a native desktop application, which runs against the operating system's APIs rather than being delivered over HTTP and rendered by a browser. A web application is accessed via a browser over a network. This option would fit a compiled program needing device drivers or filesystem privileges.

An application that connects services using APIs

Why it fails: API connectivity describes service-to-service integration or a microservices architecture, not the defining characteristic of a web application, which is browser-delivered content over HTTP. Many web applications call APIs, but that is incidental. This option would suit a question about how distributed systems or middleware components communicate.

Commercial

Why it fails: A commercial licence is sold outright; it does not itself grant a time-limited trial before purchase. It tempts because trial software is often commercially licensed, but the defining mechanism here is the expiry-gated evaluation period, which names the trial licence.

Freeware

Why it fails: Freeware is distributed at no cost with no expiry, so it never converts to a paid purchase. It tempts because freeware is also zero-price, but the stem's limited-time-before-purchase mechanism is the defining feature of trial or evaluation licensing.

Open source

Why it fails: Open source concerns source code availability and modification rights, not time-limited usage. A trial licence grants use for a set period before purchase, so the stem describes a trial, not open source. Open source would be correct where users may freely inspect, modify and redistribute the code.

Merge

Why it fails: Merge combines divergent branch histories into one, creating a merge commit rather than capturing the working tree's current state. It is tempting because it records repository changes, but the snapshot operation is commit, which saves staged changes as a new point in history.

Push

Why it fails: Push uploads local commits to a remote repository; it transfers existing snapshots rather than creating one. It is tempting because it updates the repository, but the snapshot itself is produced by commit, which records staged changes locally before any push occurs.

Branch

Why it fails: Branch creates a movable pointer to a commit, enabling parallel lines of development, but it stores no snapshot of changes. It is tempting because branches track work, yet the snapshot operation is commit, which captures the staged state as a new object in history.