CompTIA Security+ SY0-701 Practice Test 8
Question 70
An Internet-accessible ERP system runs a component whose vendor support has ended. The supplier will issue no more patches, and the organization has no compensating access controls in place. What fact makes this exposure especially concerning?
- The organization maintains a current inventory entry for the ERP asset
- The application host is in a locked server rack
- The remotely reachable component can no longer receive vendor security fixes
- A recent TLS certificate renewal did not alter the application version
Explanation
Correct Answer
C:End of vendor support means newly discovered weaknesses in this ERP component may receive no vendor-supplied remediation. Since the service remains reachable from the Internet, adversaries can potentially probe it remotely and exploit known or emerging flaws over a long period. The organization should prioritize supported replacement or isolation, restrict necessary access through controlled gateways, and monitor for exploitation as interim risk treatment. None of those compensations makes unsupported software intrinsically safe. The attack-surface concern is the combination of remote reachability and lack of a reliable patch path, rather than the presence of a hardware lock or inventory entry.
Incorrect Answers
A:An asset inventory helps security staff identify ownership, dependencies, and affected technology, which is positive for vulnerability management. Merely recording an unsupported application does not eliminate its vulnerabilities, but inventory completeness is not the risk-increasing factor sought. The decisive problem is unpatchable remotely reachable code. Inventory provides the visibility needed to plan isolation, replacement, or temporary controls.
B:A locked rack can reduce physical tampering and unauthorized console access. It cannot prevent an Internet-based attacker from sending requests to a vulnerable ERP service. Physical security remains useful in depth, but this incident concerns remotely accessible software that will not receive future security patches. Protecting the room does not shrink the publicly exposed application interface.
D:Renewing a TLS certificate improves certificate validity for the transport connection, but it does not remediate application vulnerabilities in an unsupported ERP component. The unchanged application version is relevant because the software remains obsolete; the act of certificate renewal is not the source of the increased risk. Confidential encrypted traffic can still deliver malicious requests to a vulnerable service. Component lifecycle and exposure need direct remediation.
Question 71
A security scan finds TCP 3389 reachable from the public Internet on a file server whose remote-desktop service should be used only by internal administrators. Which change most directly reduces the exposed attack surface?
- Log more public RDP sign-in failures without filtering the destination
- Require MFA but leave the unnecessary public listener reachable to anyone
- Remove Internet reachability and require access through an approved restricted management path
- Slow connections to the publicly exposed RDP service with a rate limiter
Explanation
Correct Answer
C:Removing public TCP 3389 exposure eliminates a direct Internet path to a service that has no legitimate external audience. Administrators can instead connect through a hardened VPN, zero-trust administrative gateway, or bastion with strong authentication and granular authorization. Firewall policy should constrain source identities and routes; the service should also be patched and monitored. This reduces opportunities for protocol probing and credential attacks before they reach the destination host. The distinction is between reducing the exposed interface itself and merely making an exposed interface harder to abuse. Both can matter, but eliminating unnecessary reachability directly answers the question.
Incorrect Answers
A:Authentication logs help reveal guessing and support incident investigation, but collecting more failed attempts does not prevent unsolicited connections from reaching the RDP listener. Vulnerability probes and some protocol attacks can still target the exposed service. The requirement is attack-surface reduction, meaning the unnecessary externally reachable interface should be closed or isolated. Detection remains a supporting layer.
B:MFA is valuable for protecting administrator sign-ins, especially against stolen passwords. However, a publicly reachable RDP listener still exposes a service endpoint to Internet scanning, denial of service, and potentially vulnerabilities before authentication. The server is supposed to be managed internally, so public access is unnecessary. MFA should accompany a restricted management route rather than justify retaining broad Internet reachability.
D:Rate limiting may slow repetitive connection attempts or lessen a narrow form of brute-force activity. It does not remove the public listener, so attackers can still probe the RDP protocol or exploit an unpatched weakness. Because the service is used only for internal maintenance, the stronger measure is to block Internet access entirely and route administration through controlled channels. Rate limiting is not a substitute for the missing boundary.
Question 72
An audit reveals that a branch router still accepts its factory administrator password. Its web management console is reachable from a vendor-maintenance laptop on the office network. What remediation should be prioritized?
- Replace the default credentials and limit management access to approved administrative hosts
- Enable HTTPS administration but keep the factory password unchanged
- Increase log-retention capacity without modifying the login settings
- Deploy a second router using the same factory credentials for redundancy
Explanation
Correct Answer
A:Factory defaults are widely documented and can be exploited by anyone who reaches the management interface. Changing them to a unique strong secret removes a predictable authentication weakness, while restricting management traffic to approved hosts or a protected management network reduces who can attempt access. Named administrator accounts, MFA through a gateway where supported, and logging further improve accountability. This combination addresses both the credential and reachability aspects described. A locked office does not guarantee trust for every contractor laptop. Remediation should include checking whether the default credentials were already used, reviewing configuration integrity, and storing updated secrets securely.
Incorrect Answers
B:HTTPS can encrypt management traffic and validate the device endpoint when certificates are properly checked. But keeping a factory password means an adversary who reaches the interface can still authenticate with publicly known credentials. Transport confidentiality does not replace credential hygiene. Both secure management protocols and a strong unique authentication mechanism are needed, along with limiting access to the console.
C:Longer log retention can help reconstruct suspicious router sessions after the fact, but it does not stop someone from using a known default password. The weakness is immediate and preventable through credential changes and management-plane isolation. Logging is valuable supporting evidence; it should not be the sole response to an exposed administrative interface with predictable credentials.
D:A second router can improve availability if failover is configured correctly, but duplicating factory credentials creates another vulnerable management endpoint. Redundancy does not automatically improve confidentiality or authorization. Both devices would need hardened administrator access before being placed into service. The problem is unsafe defaults, not insufficient hardware capacity or a single point of network failure.
Question 73
A warehouse inventory scanner automatically pairs over Bluetooth without authenticating the handheld device. Visitors standing nearby can initiate pairing while scanners handle shipment data. Which initial attack surface should the team address?
- Bluetooth radio jamming that prevents existing trusted scanner connections
- Deliberate interference that disconnects scanners but does not authenticate a new handheld
- A compromised WPA passphrase on a separate corporate Wi-Fi SSID
- Untrusted local wireless connections enabled by insecure Bluetooth pairing
Explanation
Correct Answer
D:The scanner exposes a Bluetooth pairing interface that nearby people can reach without proving they are authorized handheld devices. An attacker could attempt to connect or interact with shipment workflows through that trust boundary. Requiring authenticated pairing, using supported secure pairing modes, limiting discovery windows, and reviewing device permissions reduce exposure. Physical proximity narrows the attack radius compared with Internet services, but visitors are explicitly inside that radius. Inventory devices should also be managed and updated to address protocol implementation flaws. The defining weakness is accepting an unauthenticated local radio connection, not an email, Wi-Fi, or backup issue.
Incorrect Answers
A:Radio jamming can interrupt the availability of Bluetooth communication, causing established scanners to lose their data link. It does not explain why an untrusted handheld can form a new pairing relationship without presenting any acceptable identity proof. The stem is about an authorization and pairing trust boundary, not simply failed communication. Detecting interference may help warehouse availability, but enforcing authenticated pairing and limiting discoverability address the specified connection risk.
B:An attacker could attempt to disrupt scanner connectivity through interference or connection flooding, making loss of service a plausible wireless threat. However, the question states that nearby visitors can successfully pair an arbitrary handheld because the pairing process omits authentication. A denial-of-service pattern does not account for unauthorized trust establishment. The central issue is accepting a new local Bluetooth peer without validating its identity or approval.
C:Wi-Fi uses different association and encryption mechanisms from Bluetooth. Even a securely configured corporate WLAN cannot automatically protect a Bluetooth pairing process that trusts unknown nearby devices. The stem identifies the exposed Bluetooth interface directly. Treating the event as a WPA passphrase failure would target a separate SSID and leave the vulnerable local wireless pairing mode unchanged.
Question 74
Employees in a biotechnology company routinely read a niche industry journal. Attackers compromise the journal's website and insert malicious code targeted at those repeat visitors, hoping to infect their company devices. What technique is most accurately described?
- Watering-hole attack against a site frequently visited by the intended victims
- Password spraying one common guess across many corporate accounts
- Direct phishing emails with an attachment sent to named employees
- An internal asset-discovery scan performed by company administrators
Explanation
Correct Answer
A:A watering-hole campaign compromises a website or service the target population is likely to visit, allowing the attacker to reach victims through their established browsing habits. The journal is not necessarily malicious by design; attackers have altered its content to exploit visitors. This differs from sending a targeted message to each employee or trying credentials against login services. Defensive measures include patched browsers, web filtering, isolation of risky content, threat hunting around visits to the compromised site, and careful incident scoping. The important clue is attacker control of a trusted meeting place used by the intended group rather than direct delivery to each person's inbox.
Incorrect Answers
B:Password spraying tests one or a few candidate passwords against many accounts, seeking to avoid lockout thresholds while gaining credential access. The described attack uses code hosted on an industry website; no authentication guessing across user accounts is shown. Both could target the same company, but the technical vector and evidence are different. Web-content compromise is the operative factor.
C:Direct phishing would involve messages sent to employees containing a lure, attachment, or link. The scenario instead says employees visit the journal as part of their normal routine and encounter inserted code there. An attacker could also email the journal's link, but that is not required for a watering-hole operation. The compromised shared website is the initial delivery surface here.
D:Authorized asset discovery inventories systems and network exposure for defensive purposes. It does not insert malicious code into an external journal or target ordinary readers for infection. The fact that employees repeatedly visit a site supplies the adversary's targeting opportunity, not evidence of a routine security scan. The operation is adversarial website compromise rather than internal maintenance.
Question 75
A vendor's legitimate accounts portal uses payables-example.com. An employee follows a link to payables-examp1e.com, with the letter 'l' replaced by the numeral '1', and submits credentials to a copied login page. Which technique is driving the deception?
- Typosquatting or a look-alike domain intended to mislead users
- Credential stuffing with previously stolen username-password pairs
- Network traffic flooding to deny access to the legitimate portal
- Router firmware downgrade to a vulnerable release
Explanation
Correct Answer
A:The attacker registered or used a visually similar domain in which one character resembles the original name. That look-alike address can trick users into treating a fraudulent page as the supplier's real login service. This is a typosquatting or deceptive-domain technique, and the cloned page then harvests credentials. The essential evidence is the domain spelling itself, not repeated login attempts. Users and protective tools should check full hostnames, use verified bookmarks, and avoid entering credentials after unexpected redirects. Domain monitoring and phishing-resistant sign-in methods can reduce risk, but even strong authentication should be accompanied by trusted navigation to the correct site.
Incorrect Answers
B:Credential stuffing uses collections of known username-password pairs to attempt sign-ins at other services. Here the attacker presents a fake site and persuades a user to type credentials voluntarily. The credentials might later be used for stuffing or account takeover, but that would be a subsequent phase. The original lure depends on a deceptive hostname and credential harvesting, not on automated reuse of an existing breach database.
C:Denial of service overwhelms a service or its supporting infrastructure so authorized users cannot access it. The false portal in the scenario is accepting credentials and trying to resemble the real vendor, not saturating the real website with traffic. A look-alike address can create fraud even when the legitimate service remains fully available. Availability attacks are therefore not the distinguishing mechanism.
D:Firmware rollback changes a network device to an older software version, potentially reintroducing vulnerabilities. The question describes no router administration or software downgrade. The security boundary being crossed is a user's trust in a visually deceptive web address. A firmware operation would be unrelated to the copied login page unless additional facts established an entirely separate attack.
Question 76
A payroll clerk receives an email apparently from the chief financial officer instructing an immediate supplier bank-account change. Sender authentication fails and the request bypasses the approved call-back verification process. What is the best working classification?
- A verified, routine supplier banking update
- A fake login page whose primary purpose is credential harvesting
- An approved emergency transfer backed by a verified executive signature
- Business email compromise using executive impersonation to redirect payment
Explanation
Correct Answer
D:Business email compromise commonly impersonates an executive, supplier, or other trusted business party to induce fraudulent financial actions. The forged CFO instruction tries to bypass bank-change controls and redirect payment to an attacker-controlled account. Failed sender authentication is an important technical indicator, but operational verification of the beneficiary is also essential because some attacks originate from genuinely compromised mailboxes. The payroll clerk should stop the transaction and confirm through established independent contact information, not reply to the suspicious message. The defining combination is executive identity impersonation through email and a financial instruction outside normal authorization procedures, not a simple credential-harvesting webpage.
Incorrect Answers
A:A legitimate bank-account update requires the supplier's verified instruction and the company's authorized payment-change workflow. Here the apparent CFO identity fails message authentication and asks staff to bypass established verification. Those are strong red flags rather than proof of an approved supplier change. The organization should use a known telephone number or vendor record to verify any banking instructions independently of the suspicious message.
B:Credential-harvesting phishing typically lures recipients to a fake login service or asks them to disclose account secrets. The email described seeks a changed destination for a payment, not a password or session code. Both are social engineering and could coexist in more complex campaigns, but the stated business objective is payment redirection. Classification should reflect the action the attacker is trying to induce.
C:A verified executive authorization would come through an approved signing or payment workflow and would not require bypassing required callbacks without documented exception approval. Failed sender authentication undermines the claimed identity. An attacker can copy a title, sender display name, or message style; those are not sufficient proof of authority. The case includes no valid digital signature or independent confirmation.
Question 77
An attacker calls an employee, claims to be from internal IT, and invents an imminent company-wide outage. The caller insists the employee must disclose a recovery code immediately, though no incident notice exists. What social-engineering mechanism creates the apparent authority?
- A verified operational outage bulletin sent through an approved channel
- Spoofing caller-ID metadata without the invented outage narrative
- Pretexting using a fabricated support emergency to obtain a secret
- Replaying previously stolen authentication data without inventing a support incident
Explanation
Correct Answer
C:Pretexting is the creation of a plausible fabricated situation or identity to induce the target to take an unsafe action. The caller poses as IT and claims an urgent widespread outage, using time pressure to get a recovery code that would not normally be disclosed. The attack also uses the voice channel, but the requested element is the invented support emergency rather than merely the existence of a phone call. The employee should verify through a known service-desk number or trusted internal incident channel and never read active recovery or MFA secrets to an unsolicited caller. The absence of an official outage notice helps expose the pretext.
Incorrect Answers
A:A verified operational bulletin would originate from a known source and provide actionable service information, not request secret authentication codes from an arbitrary caller. In this case the employee has no corroborating notice, and the story is invented. The attacker is using an impersonated role and urgent narrative to manipulate behavior. The distinction is between independently authenticated operational communication and a fabricated premise.
B:A forged caller-ID display can make a call appear to come from an internal support number and can strengthen a social-engineering attempt. Caller-ID spoofing alone does not explain the specific authority story in the question: the intruder invents a looming organization-wide outage and uses that fabricated situation to demand a recovery code. The manipulated narrative is the pretext; a telephone-number spoof could be an additional aid, but it is not the requested mechanism.
D:Replay attacks present previously captured authentication material to a service in the hope that it remains accepted, for example when a protocol lacks suitable replay protection. Nothing in the question says the attacker already possesses a valid code or is submitting old traffic. The attacker is speaking directly to a user, manufacturing an emergency, and trying to obtain a current secret. The evidence supports a social-engineering pretext rather than a protocol replay failure.
Question 78
A customer searches for a company's support portal and opens a sponsored result using copied branding and login fields. The page is hosted on an unrelated attacker-controlled domain, not a one-character typo of the authentic hostname, and forwards submitted passwords to the attacker. Which threat is most directly present?
- A DNS service outage preventing the legitimate portal from loading
- An authorized test portal that uses synthetic credentials and does not forward real passwords
- A script injection on the genuine support domain that steals credentials without creating a lookalike site
- Brand impersonation through a credential-harvesting fake site
Explanation
Correct Answer
D:The attacker has cloned recognizable branding and a login experience to persuade customers that a malicious domain is the legitimate support portal. Once credentials are entered, the page sends them to the attacker, making this brand impersonation combined with credential harvesting. Search-result placement or advertising may help lure visitors, but the central evidence is the mismatch between the claimed company identity and actual domain ownership. Customers should navigate from verified bookmarks or known official links, and the organization can monitor deceptive domains, seek takedowns, and use phishing-resistant authentication. This is not merely a DNS outage because the fraudulent site actively collects secrets.
Incorrect Answers
A:A DNS outage usually stops a name from resolving or directs users to an unavailable service. The user in this case reaches a functional page that deliberately copies a company's identity and collects passwords. The problem is not simply failed name resolution; the attacker has built an impersonation destination. DNS protection may reduce some redirection risks, but it does not automatically establish a page's legitimacy.
B:Security teams sometimes operate realistic training pages that imitate a production login interface, but an authorized exercise would use an approved destination and carefully controlled handling of synthetic or protected test credentials. The question instead states that a page on an unfamiliar domain forwards customer passwords to an attacker. The actual harmful behavior is credential collection through brand impersonation. Calling that an approved test would disregard both the unauthorized destination and exfiltration.
C:A genuine support portal can suffer script injection and leak session information even if its domain and branding are authentic. That would be a different web compromise requiring investigation of the legitimate application. In this case the customer visits a separate, attacker-controlled domain that mimics the company’s interface and forwards submitted credentials. The decisive deception is the fake site’s claimed identity rather than injection into the real site.
Question 79
A legitimate software supplier distributes a signed update through its usual channel. Investigators discover that attackers compromised the supplier's build process and inserted a backdoor before the update was packaged. Customers installed the update normally. Which delivery vector was exploited?
- The vendor's trusted software-update supply chain
- A phishing attachment sent directly to individual customer mailboxes
- A direct exploit against each customer's public web server
- DNS redirection to a separate unofficial download mirror
Explanation
Correct Answer
A:The malicious code entered through the supplier's normal build and distribution process, so customers received a trusted-looking update containing an attacker-added backdoor. This is a software supply-chain compromise: the adversary attacks a dependency or producer that downstream organizations trust. A valid-looking package signature does not establish that the source or build pipeline was uncompromised before signing. Defenses include controlled builds, protected signing keys, dependency review, provenance evidence, staged rollout, and runtime monitoring, but no single control guarantees prevention. The crucial distinction is that the malware crossed into customers through an authorized update workflow, not through a separate email lure or untrusted mirror.
Incorrect Answers
B:Email attachments are a common malware delivery path, but the scenario does not describe customer employees opening unsolicited messages. They installed a routine supplier update through the established channel. The compromise was upstream of the recipients, which changes both investigation scope and remediation priorities. Searching only mail gateways could miss similarly affected customers who downloaded the same backdoored package.
C:A direct web-service exploit would require attackers to target a vulnerability on each customer's public-facing application. Here customers became compromised by running software received from their supplier, with the malicious code inserted before distribution. The installation route may bypass controls focused on inbound traffic because the payload arrives through a trusted maintenance action. The initial vector is supply chain, not direct exploitation of each public endpoint.
D:DNS redirection to an unofficial mirror can trick users into downloading unauthorized installers. The stem specifically says customers used the supplier's normal signed update channel and that its build process had already been compromised. Even if DNS were perfectly configured, the malicious package would remain inside that legitimate channel. The correct root delivery path is the poisoned supplier update process.
Question 80
A managed service provider holds privileged remote-administration access to dozens of customers. An attacker compromises one MSP administrator account and uses the existing management platform to enter multiple customer tenants. What property made this breach unusually broad?
- A single-customer delegated administrator role with no permissions in other client tenants
- Improving endpoint antivirus on the MSP administrator's workstation alone
- A centralized monitoring console that aggregates alerts but cannot administer customer systems
- The MSP's inherited privileged reach across multiple downstream environments
Explanation
Correct Answer
D:A managed provider often maintains trusted administrative paths into many client environments. When one MSP identity is compromised, those existing permissions can let an intruder move rapidly across otherwise separate customers without exploiting each customer's public perimeter. That concentration of privileged reach is the scaling factor. Customers and providers should limit roles and tenant scope, use strong MFA and just-in-time elevation, review delegated access, log cross-tenant actions, and promptly revoke compromised sessions. Segregating customer administration can reduce blast radius. The lesson is not that remote management is inherently unsafe, but that shared or overbroad third-party privileges create correlated risk across many environments.
Incorrect Answers
A:A tightly scoped delegated role would limit the consequences of one stolen MSP account to a particular customer rather than creating broad multi-tenant reach. The observed compromise affected many customers because the abused management identity already had privileged access across them. Physical security at the data centers may still be important, but the decisive blast-radius factor is authorization inheritance. Per-customer isolation and just-in-time grants would reduce that shared exposure.
B:Endpoint hardening is important because administrator workstations are attractive targets. Yet merely patching one machine after credential compromise does not remove unused access grants, excessive tenant reach, or stale sessions across customers. The scenario asks what made the incident scalable: the management identity's cross-customer privileges. Strong endpoint security is one preventive layer, not the underlying blast-radius explanation.
C:A common monitoring console can receive events from many tenants and may create confidentiality issues if its own access is weak. Receiving alerts, however, is not equivalent to possessing privileged remote-administration rights in each customer environment. The attacker used an MSP management account to enter multiple tenants and act through its existing administrative permissions. The relevant multiplier is cross-customer privilege, not merely the existence of a centralized observability service.