Refer to the Exhibit Practice Questions

The program will display an error message.

Why it fails: An empty INPUT response returns a null or empty string, which BASIC accepts without raising a runtime error. Error messages arise from type mismatches or invalid numeric conversions, not blank string entry, so this option misreads how the INPUT statement handles an empty response.

The program will prompt for input again.

Why it fails: Pressing Enter without a name submits an empty string, which the program accepts as valid input rather than looping. It is tempting to assume validation logic exists, but BASIC's INPUT statement stores the blank value and execution continues to the next line without re-prompting.

The program will end with no output.

Why it fails: Pressing Enter supplies an empty string, which the program accepts as valid input rather than terminating. Program termination would follow an explicit END or STOP statement, or an unrecoverable runtime error, not an empty INPUT response, so this outcome misreads how BASIC handles blank entries.

Ring

Why it fails: In a ring, each node depends on its neighbours, so one cable or node failure can disrupt the entire loop unless dual rings are used. It tempts because ring topologies offer predictable performance, and would be correct where deterministic throughput matters more than isolating a single cable fault.

Bus

Why it fails: A bus topology shares one backbone, so a single cable break can isolate multiple devices or the whole segment, failing the resilience requirement. It tempts because it is cheap and simple for small offices, and would suit a scenario prioritising low cabling cost over fault isolation.

Mesh

Why it fails: A mesh topology requires each device to maintain multiple direct links to others, creating excessive cabling and configuration overhead for a 20-device network. This fails the stem’s need for easy troubleshooting, as tracing faults across numerous interconnections is cumbersome. The option is tempting because mesh offers high resilience to cable failures, and in a critical data-centre environment where maximum redundancy is essential, it would be the correct choice.

Network outage

Why it fails: A network outage would not generate the local hardware error shown in the exhibit. It is tempting because connectivity faults commonly cause failures, and would be correct if the exhibit showed failed pings, unreachable shares or missing network adapters rather than the displayed fault.

Power supply failure

Why it fails: A failed power supply produces no boot at all, so the exhibit's specific error could not appear. It is tempting because power faults are a common hardware cause of startup failures, and would be the answer where the device is completely dead with no display output.

Bad memory stick

Why it fails: Faulty memory typically triggers beep codes, POST failures or blue screens, not the error the exhibit displays. It is tempting because RAM faults are a frequent hardware cause, and would be correct if the exhibit showed memory-test failures or random crashes rather than the shown message.

Ring

Why it fails: Ring topology passes data token-style around a single closed loop, so one break or node failure can disrupt the whole segment; a small office sharing files needs a central switch, making star the efficient fit. Ring suits token-passing networks where deterministic access matters.

Bus

Why it fails: A bus topology shares one backbone cable, so a single break or fault disrupts every connected device, and performance degrades as collisions rise with each added node. It suits small, temporary or legacy coaxial networks where cost matters and few devices connect. Here, the building's employees need reliable, scalable file sharing, which a star topology's central switch provides.

Mesh

Why it fails: Mesh requires every node to interconnect directly, so a small office LAN would need cabling or wireless links between all endpoints, multiplying cost and configuration effort for no gain. It is tempting because mesh delivers path redundancy and fault tolerance, making it the right choice for wide-area backbones or networks where a single link failure must not isolate sites.

End the process immediately

Why it fails: Ending svchost.exe immediately can crash dependent services and destabilise Windows, since svchost hosts multiple shared services. It is tempting as a quick fix for high CPU, and would be appropriate only after identifying the specific hosted service and confirming it is safe to stop.

Increase virtual memory

Why it fails: Increasing virtual memory does not reduce CPU consumed by svchost; it addresses paging pressure, not processor load. It is tempting because high CPU often accompanies memory exhaustion, and would be correct if the exhibit showed sustained hard page faults and low available memory rather than CPU saturation.

Update Windows

Why it fails: Updating Windows does not address the currently spiking svchost process; the exhibit's specific process and service must be identified first. It is tempting because patching resolves known svchost-related bugs, and would be right if the exhibit showed an outdated, unpatched system with a documented svchost defect.

A virus infected the system

Why it fails: Virus infection is recorded by antimalware products under their own event sources and IDs, not the system log entry shown. It tempts because unexpected shutdowns can result from malware, but the exhibit's source and event code indicate a normal system operation.

A software update was installed

Why it fails: Software update installation is logged by Windows Update or the installer service with distinct event IDs, not the entry shown. It tempts because updates often trigger restarts, but the exhibit's specific source and code identify the logged action directly.

A scheduled restart took place

Why it fails: A scheduled restart is logged by the Task Scheduler or Windows Update service, not by the shutdown/restart event codes shown in the exhibit. It tempts because restarts do generate event entries, but the specific source and event ID in the exhibit identify a different cause.

Ring

Why it fails: Ring wiring connects each device to two neighbours in a closed loop, so no single central cable carries all traffic. It is tempting as a topology that also uses shared cabling, and it would be correct where deterministic token passing around a loop is required.

Star

Why it fails: A star topology links every device to a central switch or hub, not to a single shared cable, so it fails the scenario's bus requirement. It is tempting because star is the dominant modern LAN layout, and it would be correct where centralised switching and per-device fault isolation are wanted.

Mesh

Why it fails: Mesh interconnects nodes via multiple redundant paths between devices, with no single central cable. It is tempting because mesh offers high resilience, and it would be correct where fault tolerance and path redundancy matter more than simple shared-medium wiring.

The DNS server is not configured

Why it fails: A missing DNS server would prevent name resolution, yet the exhibit already lists a DNS address, so this is not the fault. DNS configuration is the correct focus when pings to IP addresses succeed but hostnames fail to resolve.

The IP address is invalid

Why it fails: The address shown is a valid, properly formed host address within its subnet, so it is not invalid. An invalid address would be malformed, out of range, or a network or broadcast value; that scenario arises when static configuration is mistyped.

The subnet mask is incorrect

Why it fails: An incorrect subnet mask would misplace the host within its network, but the exhibit shows the address and mask consistent with the gateway, so local routing still functions. Mask errors typically manifest as reachability failures to specific subnets, not total internet loss.

6

Why it fails: The exhibit's loop terminates before reaching 6, so this value is never printed as the final output. It tempts because 6 is the loop's upper bound, and candidates assume the counter reaches its limit; that would hold only if the condition used an inclusive comparison rather than stopping earlier.

10

Why it fails: The exhibit's loop or counter terminates before reaching ten, so the final printed value differs. Ten tempts as the obvious round endpoint of a counting sequence, but the actual last output depends on the loop's increment and stopping condition shown in the exhibit.

1

Why it fails: The exhibit's final printed value is not 1; the counter has already advanced past its starting value by the last iteration. It tempts because 1 is the initialisation value, and candidates assume the loop resets or prints its seed; that would apply only if the exhibit printed before incrementing.

IPv4 address

Why it fails: An incorrect IPv4 address would prevent all connectivity, including access by IP address, so it cannot explain name-only failure. The option tempts because IP misconfiguration commonly causes browsing problems, but the symptom of working IP access points specifically to DNS resolution, not addressing.

Subnet mask

Why it fails: A wrong subnet mask breaks local subnet routing, yet the host still reaches the default gateway and resolves names via DNS, so domain browsing would work. Mask errors typically cause partial connectivity failures, not name-only failure. The symptom points to DNS resolution, making the DNS server address the incorrect setting.

DHCP enabled

Why it fails: DHCP being enabled or disabled affects how the host obtains an address, not whether domain names resolve; a valid lease still permits IP-based access. The option tempts because DHCP supplies DNS server addresses, but the stem shows IP connectivity already works, isolating the fault to DNS configuration.

The server name is hardcoded.

Why it fails: A hardcoded server name is a maintainability and portability weakness, not an exploitable vulnerability; it exposes no credential or data. It is tempting because hardcoding looks like poor hygiene, and it would be the correct finding where the name embeds an internal hostname that aids reconnaissance.

The log level is set to Debug.

Why it fails: Debug logging records verbose internals, but it only becomes the top concern when it writes credentials, tokens or personal data to readable logs. It is tempting because debug output looks risky, and it would be correct where the exhibit shows secrets being logged in plaintext.

The database name is SalesDB.

Why it fails: A database name such as SalesDB is ordinary configuration metadata and discloses nothing sensitive on its own. It is tempting because descriptive names hint at data content, and it would be the correct concern where the name itself leaks regulated data categories or credentials to unauthenticated users.

File sharing over SMB

Why it fails: SMB file sharing uses TCP 445 (or legacy 139), never 443, so this PID's encrypted session cannot be SMB traffic. It is tempting because SMB also carries file transfers over TCP, and would fit a connection to an internal file server on port 445.

Remote Desktop Protocol (RDP) session

Why it fails: RDP listens on TCP 3389, not 443, so an established port 443 connection is not an RDP session. Port 443 indicates TLS, typically HTTPS browsing or an encrypted application session. RDP would be the likely purpose had the remote port been 3389.

Email submission (SMTP)

Why it fails: SMTP submission runs on ports 587 or 25, so port 443 cannot be email submission. It is tempting because SMTP also uses TCP and carries user data outward, and would be the answer for a connection to a mail relay on port 587.

Ring topology

Why it fails: A ring topology passes frames node to node around a closed loop, so a single failed device or link breaks the ring and disrupts the whole network unless a dual-ring or bypass mechanism exists. It is tempting because rings give deterministic, orderly access, and it would be correct for token-passing networks such as FDDI.

Bus topology

Why it fails: A bus topology uses a shared backbone cable, so a break in that backbone or its terminators halts all communication, not just the failed device. It is tempting because bus networks are cheap and simple to cable, and it would be correct for a small legacy network where every node taps one common medium.

Mesh topology

Why it fails: A full mesh connects every device directly to every other, with no central switch; each node needs multiple interfaces and links. It is tempting because mesh offers redundant paths and high fault tolerance, and it would be correct where resilience matters more than cabling cost, such as a WAN core.

The path rule for C:\Program Files is too broad.

Why it fails: A broad C:\Program Files path rule governs executables in that directory only; it cannot deny execution from D:\Apps. It is tempting because overly permissive path rules are a genuine AppLocker misconfiguration, but the fault here lies with the rule covering the custom application's own location.

The publisher rule is incorrect.

Why it fails: Publisher rules match signed binaries by certificate attributes; an incorrect publisher rule would affect only signed applications matching that certificate, not an unsigned custom app in D:\Apps. It is tempting because publisher rules are the recommended AppLocker approach for signed software, but they are irrelevant to this path-based failure.

The enforcement mode is set to Enforce, blocking all unlisted apps.

Why it fails: Enforce mode applies the configured rules rather than blocking everything unlisted; a rule permitting D:\Apps may simply be absent, which is why the app fails. It is tempting because AppLocker's enforcement modes govern whether rules are audited or applied, and Enforce is the correct setting once rules are validated.

Duplicate IP address on the network

Why it fails: A duplicate IP address causes intermittent or total loss of connectivity, affecting IP-based access too, so it cannot produce the reported name-only failure. It is tempting because duplicates generate confusing intermittent symptoms, and it would be correct if the user's address conflicted with another host.

Incorrect default gateway

Why it fails: A wrong default gateway blocks all off-subnet traffic, including the direct IP access the user still has, so it cannot explain name-only failure. It is tempting because gateway faults do break connectivity, and it would be correct if the user could reach nothing beyond the local subnet.

Incorrect subnet mask

Why it fails: An incorrect subnet mask misclassifies local versus remote destinations, breaking IP-address access as well, so it cannot leave direct IP browsing working. It is tempting because mask errors cause partial reachability, and it would be correct if some subnets were unreachable while others responded.