CompTIA Security+ SY0-701 Practice Test 11
Question 100
A company discovers that a service API token with production privileges was committed to a publicly readable repository. The same bearer token is accepted by three different production environments. Which exposure creates the largest immediate security concern?
- An unrelated web login that permits passwords without MFA
- An expired service certificate that may interrupt TLS connections but does not invalidate a leaked API token
- A reusable leaked credential that grants access across multiple environments
- A public API specification that contains no usable secret
Explanation
Correct Answer
C:A bearer token acts as proof of authority for anyone who possesses it, so public repository exposure can immediately enable unauthorized API calls. Reuse across three production environments multiplies the potential blast radius and makes one accidental commit a cross-system security event. The team should revoke or rotate the token everywhere it is trusted, inspect access logs for abuse, remove secrets from development workflows, and replace shared privileges with separate least-privilege credentials. Deleting the latest repository line is insufficient because commit history, forks, and caches can retain copies. The central weakness is leaked reusable secret material, not merely publication of API documentation or a separate authentication weakness.
Incorrect Answers
A:An interactive login without MFA can present significant identity risk, but it does not explain the disclosed bearer token that already grants production API privileges. An attacker using a valid service token may not need to interact with that login at all. The immediate response should address the actual exposed secret and its cross-environment reach, while reviewing MFA gaps as a separate hardening concern.
B:An expired TLS certificate may prevent clients from establishing a properly validated encrypted session and therefore creates a service-availability or trust problem. It does not automatically revoke a separate bearer token copied from public source control. The token in the question remains accepted across three production environments and grants live API privileges to its possessor. The direct high-impact risk is secret compromise and cross-environment reuse, which require prompt revocation and scoped replacement.
D:API documentation may reveal endpoint names and supported operations, but it does not necessarily provide authority to perform them. Publishing an interface description is not equivalent to disclosing a live privileged token. The question expressly identifies a credential accepted in multiple environments, which an attacker could use immediately. Protecting and rotating that secret is more urgent than hiding ordinary public API specifications.
Question 101
The SIEM records roughly 8,000 failed passwords against one administrator account over ten minutes. The requests submit different candidate passwords while no other identities are targeted. Which attack technique is most consistent with the pattern?
- Online brute-force guessing concentrated on one account
- Password spraying one common secret across many employee accounts
- Reusing a previously captured valid authentication session
- Credential stuffing with a previously breached password reused against the administrator account
Explanation
Correct Answer
A:Brute-force password guessing systematically tries many candidate secrets for a target identity until one works or the service blocks further attempts. The logs show thousands of distinct passwords directed at the same administrator account, which is the distinguishing distribution. A per-account rate limiter, strong MFA, lockout safeguards designed against denial of service, and investigation of source telemetry can reduce risk. The large request count matters because it demonstrates automated guessing, but the number of targeted accounts is what differentiates this from password spraying. The investigator should confirm the pattern rather than assume successful compromise merely because attempts were numerous.
Incorrect Answers
B:Password spraying spreads one or a few likely passwords across many usernames to reduce per-account attempt volume and avoid simple lockouts. Here the traffic concentrates on one administrator identity and varies the passwords thousands of times. That is the opposite target distribution. A spraying detection rule focused on breadth across accounts might miss this concentrated guessing campaign if the two patterns are not distinguished.
C:Session replay uses captured authentication material such as an unexpired token or replayable challenge response. It does not require trying thousands of different password candidates. The logs indicate repeated failed login attempts with varying submitted passwords, not reuse of one previously valid session. The investigation should use authentication-field evidence to classify the mechanism rather than equating all suspicious logins with replay.
D:Credential stuffing tests password pairs already obtained from another exposure, sometimes against one valuable administrator. That could produce suspicious authentication traffic, so it is a relevant alternative. The SIEM instead records thousands of distinct candidate passwords for the same username, with no known breached secret being replayed. This distribution supports online password guessing rather than reuse of a preexisting valid credential. Investigators should verify request patterns and sources rather than infer stuffing merely from high attempt volume.
Question 102
An identity platform sees a single weak password attempted once against 1,400 different employees in one hour. Attackers limit attempts per account to avoid lockout thresholds. What attack pattern should the SOC identify?
- Password spraying against many identities with a small password set
- Brute-force guessing thousands of passwords for one user
- Replay of a captured authentication token from a previous session
- Offline dictionary cracking of a stolen password-hash database
Explanation
Correct Answer
A:Password spraying applies one or a few likely passwords across many accounts instead of exhausting guesses against a single identity. The log pattern—one candidate per employee, broad user coverage, and low volume per account—is designed to bypass basic account-lockout thresholds. Analysts should correlate the shared password pattern, source networks, and temporal clustering across users, while accounting for legitimate bulk-service failures. Defensive measures include strong MFA, blocked common passwords, behavior-based detection, and limits that consider distributed attempts. This is different from a brute-force attack targeting one identity, which would show many distinct guesses for that account rather than breadth across the employee population.
Incorrect Answers
B:Brute force against a single account concentrates many candidate strings on one username. The observed requests instead fan out across 1,400 users with only one password attempt each. That pattern reduces the likelihood that any one account crosses a conventional lockout threshold. The key evidence is the horizontal distribution of attempts, not the total count alone.
C:Replay requires a captured credential artifact or authentication exchange that can be resubmitted. The logs describe active password trials against many separate accounts, not a reused session token. A valid replayed token might generate successful access without password guessing. To classify this incident, the SOC should focus on the single password candidate reused broadly rather than infer capture of an existing session.
D:Offline cracking happens when attackers possess copied password hashes and test guesses locally without sending each candidate to the organization's sign-in endpoint. Here the identity platform observes 1,400 online login attempts, directly establishing an interactive authentication campaign. Attackers could use breached passwords as candidates, but the observed technique is online spraying, not local hash computation.
Question 103
A cloud identity service flags a user for successful sign-ins from Singapore and Toronto five minutes apart. The organization also uses a corporate secure-web gateway that can route nearby endpoints through distant egress IP addresses. What is the defensible initial interpretation?
- Mark the event as proven account takeover based solely on the city names
- Treat it as a risk signal requiring comparison with gateway egress, device, and session evidence
- Disable impossible-travel detection for anyone using the secure-web gateway
- Reclassify both successful sign-ins as authentication failures because their locations conflict
Explanation
Correct Answer
B:Impossible travel is a useful anomaly indicator because two geographically distant sign-ins within minutes are unlikely to represent physical movement by one user. But a corporate gateway can make a legitimate user's network egress appear in different countries, so analysts should correlate the events with proxy logs, endpoint identifiers, token activity, sign-in risk, and authentication method. Depending on those findings, they may challenge, limit, or revoke affected sessions. The correct approach avoids both premature certainty and wholesale dismissal. A high-fidelity alert should consider known proxy infrastructure while still investigating unexpected devices and anomalous token usage. This is risk-based triage rather than automatic attribution.
Incorrect Answers
A:Geolocation reflects the apparent network address and may not correspond to the user's physical position. A secure-web gateway, VPN, mobile carrier, or geolocation database error can produce distant-looking sign-ins from one legitimate device. The timing is suspicious, but location alone does not prove credential theft. A confirmed-compromise label requires corroborating details such as session identity, device changes, MFA context, or evidence of malicious activity.
C:An approved proxy may explain some apparently impossible travel, but excluding all proxy users from analysis would create a blind spot that attackers could exploit. A compromised session can also originate through a legitimate proxy or a new untrusted endpoint. The detection should use proxy-aware enrichment and additional risk signals, not permanently exempt a large user population. The evidence still merits reasonable investigation.
D:A successful authentication event remains successful even if its apparent locations look inconsistent. Changing the log outcome would distort the incident timeline and prevent reliable correlation with resource access. The concern is whether one or both successful sessions were authorized, not whether the identity platform actually denied them. Investigators should preserve the event result and attach a separate risk assessment.
Question 104
A laptop suddenly rewrites thousands of shared office documents into unreadable encrypted forms, deletes accessible originals, and displays a message demanding payment for recovery. Which malicious behavior is most clearly present?
- Destructive wiper malware that overwrites business files without offering payment-based recovery
- Ransomware encrypting files to coerce payment
- Scareware that displays a fraudulent recovery demand while leaving the underlying documents readable
- A scheduled encrypted-backup integrity check
Explanation
Correct Answer
B:Ransomware commonly encrypts or otherwise renders business files inaccessible and demands payment for decryption or restoration. The rapid multi-file changes, loss of usable originals, and explicit payment notice together support that classification. Responders should isolate the affected host, preserve volatile and persistent evidence as appropriate, and investigate whether credentials or network shares enabled further spread. Restoring from tested backups can reduce availability loss, but the organization must also assess whether data was exfiltrated and avoid trusting an attacker-provided recovery tool without evaluation. The distinction is that unauthorized encryption here serves extortion, not legitimate confidentiality protection or routine storage management.
Incorrect Answers
A:Wiper malware intentionally destroys accessible data and can cause a similar sudden loss of documents, so it deserves consideration when many files become unreadable. Its defining objective is destruction, however, not a coordinated encryption-and-payment workflow. This workstation displays a demand for money in exchange for recovery after systematically encrypting files and deleting originals. Those connected observations better support ransomware. Responders should still determine whether the claimed decryption capability is real and whether additional destructive payloads are present.
C:Scareware can intimidate users with fabricated infection or payment notices, and an attacker may imitate a ransomware screen without changing any stored files. Here the files were actually rewritten into unreadable encrypted forms, and accessible originals were removed before the demand appeared. The observed data transformation makes this more than a deceptive pop-up. Analysts should corroborate encrypted file structure and process history while containing the host; a visual warning alone would not justify the same conclusion.
D:Backup verification tests whether stored protected copies can be read or restored, ideally without destructively replacing live originals. A normal encrypted backup process protects a separate recoverable copy and does not demand cryptocurrency from staff. The laptop's widespread destructive document changes are unrelated to checking backup integrity. Investigators should treat the event as active malicious modification, not a routine validation task.
Question 105
A user installs software advertised as a routine device updater. It actually opens an unauthorized remote shell to an attacker but does not automatically infect other endpoints. Which malware category most closely describes it?
- A self-propagating worm that spreads without user interaction
- A Trojan horse disguised as legitimate software
- Adware that installs unwanted advertising extensions but does not open an unauthorized remote command channel
- A legitimate remote-support agent installed with documented consent and a named authorized support session
Explanation
Correct Answer
B:A Trojan masquerades as useful or legitimate software while performing unauthorized activity after execution. In this case the updater story persuades the user to install the file, after which it opens a backdoor shell. That deception describes the malware category more directly than worm behavior because there is no autonomous spread. Investigators should identify how the installer was obtained, preserve indicators, isolate the host, and assess remote-shell actions and persistence. Code signing or attractive branding alone would not guarantee legitimacy if a distribution channel or signing key were compromised. The security-relevant mechanism is trust abuse at installation coupled with malicious functionality hidden behind a benign appearance.
Incorrect Answers
A:A worm's distinguishing behavior is autonomous propagation between systems, often exploiting reachable services. This program was installed after a user believed it was a legitimate updater, and the stem says it does not replicate to other hosts on its own. The remote shell is malicious, but the delivery disguise and lack of self-propagation support a Trojan classification instead. A Trojan can still be distributed widely by other means.
C:Adware may arrive bundled with an apparently useful installer and can violate user expectations by changing browser settings or displaying intrusive advertisements. It is a plausible unwanted-software category, but advertising is not the decisive malicious function in this scenario. The installed updater opens a remote shell for an attacker, and the harmless update story was the delivery deception. Because the question asks for the disguised delivery category, a Trojan is more precise than adware lacking that unauthorized remote-control behavior.
D:Remote-support software can provide command-line or desktop access for approved administration, making it superficially similar to a backdoor once network connectivity is observed. The difference is authorization and transparency. The user installed a supposed routine device updater, not an approved remote-support client, and an attacker receives an undisclosed shell. No accountable technician, approved service request, or consent exists. The tool's stated purpose and hidden remote access support a deceptive Trojan rather than a sanctioned support session.
Question 106
An executable appears on hundreds of vulnerable endpoints within minutes. Packet captures show that infected systems scan other hosts and exploit the same service flaw to install themselves without users opening files. What behavior is demonstrated?
- A document macro limited to manual opening by each victim
- A file-infecting virus that requires each victim to execute an infected binary before spreading
- Worm-like autonomous network propagation
- An approved endpoint-management push of an update
Explanation
Correct Answer
C:A worm can spread from an infected system to other vulnerable hosts without needing each user to run a separate installer. The captures show exactly that progression: scanning for reachable targets, exploiting a service, and installing a new copy that repeats the cycle. This mechanism can produce rapid lateral movement or Internet-wide outbreaks if vulnerable networks are poorly segmented. Mitigations include patching the abused service, limiting unnecessary reachability, isolating infected hosts, and monitoring propagation traffic. The attack may also carry other malicious payloads, but autonomous replication is the observed behavior that distinguishes a worm from a Trojan distributed manually or an approved software rollout.
Incorrect Answers
A:A macro triggered by a user opening a document does not by itself account for continuous scanning and exploitation of new hosts without user participation. The scenario specifically rules out manual installation and identifies infected systems as sources of further infection. Such independent propagation is the crucial distinction from a single malicious attachment or document payload.
B:A virus can copy its code into other executables and may spread when users exchange or launch contaminated programs. That mechanism can lead to many infected endpoints, making it a credible malware alternative. The captured traffic shows autonomous scanning and exploitation by already infected machines, without each new user opening a file. Those self-propagating network actions are the distinguishing worm behavior. The incident team should examine exploit traffic and vulnerable services rather than assume every infection required a local program launch.
D:Centralized endpoint management can deploy software to many hosts, but an authorized rollout has a known management controller, change records, and policy-defined targets. The stem describes compromised endpoints independently probing and exploiting other machines. That self-directed exploitation is inconsistent with a normal signed deployment. Responders should avoid confusing high-volume host changes with benign orchestration when network traces clearly reveal exploit-driven propagation.
Question 107
An employee installs an unfamiliar browser extension. Without disclosure or consent, it collects visited URLs and periodically uploads browsing history to an external server that is not part of company monitoring. Which behavior is indicated?
- Approved corporate browser-security telemetry
- A transparent user-approved analytics extension
- Crash diagnostics limited to anonymous browser version data
- Spyware collecting and exfiltrating browsing information
Explanation
Correct Answer
D:Spyware monitors a user's activity without appropriate authorization and transfers the collected information for the operator's benefit. The extension's secret recording of visited URLs and scheduled upload to an unapproved server demonstrate surveillance and exfiltration rather than ordinary diagnostics. Responders should identify affected browsers, remove the extension through managed controls, inspect requested permissions and possible credential exposure, and determine what information was sent. Browser-extension policies can restrict installation sources and permissions. The central inference is behavioral: the software is gathering private activity data covertly, regardless of whether it arrived as a seemingly harmless convenience extension.
Incorrect Answers
A:Legitimate enterprise telemetry generally flows to approved monitoring infrastructure under defined policies and purpose limitations. This extension sends browsing history to an unknown outside endpoint without disclosure or authorization. It therefore lacks the characteristics of sanctioned monitoring, even though both can collect activity data. The difference is consent, ownership, destination, and purpose.
B:A user-approved analytics extension discloses what data it collects, seeks relevant permissions, and provides an understandable purpose. The scenario explicitly says the collection was undisclosed and not authorized. A user clicking Install is not necessarily informed consent for secret exfiltration of visited URLs. The suspicious destination and hidden behavior support spyware rather than approved analytics.
C:Crash diagnostics may send limited technical data, such as application versions, stack traces, or anonymized error counts, to help troubleshoot reliability. The extension captures users' visited pages and periodically exports browsing history, which exceeds the described diagnostic scope. The data type is significant because browsing history can expose sensitive work patterns and confidential destinations even without capturing page contents.
Question 108
Endpoint telemetry reveals a previously unknown background process that installs keyboard hooks, captures typed characters, and transmits collected text to an unapproved Internet host. Which activity should analysts investigate first?
- Encryption of the device's entire disk volume
- Browser credential theft from stored profile databases without intercepting live keystrokes
- Clipboard monitoring that copies recently pasted secrets without recording keyboard input
- Unauthorized keylogging or keystroke collection
Explanation
Correct Answer
D:Keyloggers collect keystrokes and may transmit them to an attacker to capture passwords, messages, and other sensitive user input. Here the process explicitly registers keyboard hooks and forwards typed characters to an unauthorized destination, matching that behavior. Investigators should preserve relevant telemetry, examine persistence and outbound connections, scope potential credential exposure, and isolate the endpoint when appropriate. Some accessibility or remote-support tools legitimately observe input under authorization, so the lack of consent and suspicious external recipient matter. The direct concern is covert collection of input, not ordinary system monitoring or encryption.
Incorrect Answers
A:Full-disk encryption protects data at rest and does not need to capture every keystroke or transmit it to an unknown host. A legitimate encryption agent may prompt for a recovery key during setup but should not silently export typed text. The observed hooks and outbound uploads indicate a surveillance mechanism rather than normal disk confidentiality protection. Investigators should treat the process as a potential credential-theft risk.
B:Malware can steal saved browser passwords, cookies, and authentication tokens directly from a user profile without registering a keyboard hook. That technique also creates credential risk and may upload sensitive data to an external server. In the observed event, however, the process intercepts characters while they are typed and transmits those captured characters. The live input-hook evidence is much more specific to keylogging than theft from existing credential stores. Responders should investigate both if other telemetry appears, but the question asks about the demonstrated behavior.
C:Clipboard surveillance can capture passwords, cryptocurrency addresses, or confidential text when a user copies and pastes them. It is a realistic endpoint spying capability and may also generate suspicious outbound uploads. The process here explicitly installs keyboard hooks and collects typed characters as they occur. No clipboard-read API or paste-event evidence is described. Keylogging is therefore the directly observed mechanism, while clipboard monitoring would require a different telemetry chain. Investigators should not treat every form of input theft as proof of the same sensor behavior.
Question 109
A departing employee places a malicious script on a shared server. The script stays dormant until the date listed in an HR termination record, when it automatically deletes project folders. Which malware mechanism explains the delayed activation?
- A worm that constantly scans for new devices
- A logic bomb activated by a programmed condition
- An approved daily backup scheduled by operations
- A scheduled malicious command that executes immediately on every server startup rather than waiting for an HR condition
Explanation
Correct Answer
B:A logic bomb is malicious code arranged to execute when a specified event, date, or condition becomes true. The termination-date trigger connects the destructive deletion to the employee's future employment state, making it a conditional payload rather than continuously active malware. A date-triggered bomb may evade casual testing because nothing harmful occurs before the trigger. Defenders should review scheduled tasks and scripts, limit write permissions, protect backups, and correlate changes with personnel offboarding. The technical indicator is the condition-controlled release of destructive behavior. Establishing who installed the script and whether other triggers exist requires separate investigation.
Incorrect Answers
A:A network worm is distinguished by self-propagation into other systems. The malicious script here is already present and waits for a particular HR-related condition before destructive execution. No autonomous scanning or spreading is described. The delayed activation might be part of a larger attack, but the specific triggering mechanism is conditional logic rather than replication.
C:A legitimate scheduled backup copies or preserves data to enable recovery, and its timing should be part of an approved operational policy. This script instead deletes shared folders when an employment-related condition matches. Scheduling alone is not enough to label an action a backup. Its purpose, authorization, and destructive effect distinguish malicious conditional execution from routine recovery preparation.
D:Startup persistence can cause destructive commands to run whenever a machine boots, and scheduled tasks are common ways to maintain malicious code. That pattern does not fit the stated activation condition. This script remains inactive until a termination date recorded in human-resources data, then deletes project folders. The dependency on a future condition is what makes it a logic bomb, even if a scheduler or background service is used to test that condition. Trigger semantics distinguish the mechanisms.
Question 110
Following a reboot, an unsigned driver reinstalls privileged hooks that hide malicious processes from common management tools. Ordinary users cannot see the persistence mechanism. Which category best describes the attacker's capability?
- Rootkit-like stealth and persistence at an elevated layer
- Ordinary user-level startup persistence through a registered login task that remains visible to process tools
- Process-name masquerading by a user-mode executable without hiding kernel-visible process records
- An encrypted mail attachment that has not yet arrived
Explanation
Correct Answer
A:Rootkit techniques conceal unauthorized components by manipulating privileged interfaces, system views, or low-level hooks. The driver described here persists after reboot and hides processes from common tools, both consistent with stealth functionality intended to protect an intruder's foothold. Detecting such behavior may require trusted offline analysis, kernel telemetry, integrity measurements, and comparison against known-good system state because compromised tools may present misleading views. A rootkit is primarily defined by concealment and privilege, not necessarily a particular propagation method. Responders should avoid assuming that a clean ordinary process list proves the host is safe when the mechanism can influence those observations.
Incorrect Answers
B:An attacker may keep malware running after reboot by placing a user-mode task in a login autostart location. That is genuine persistence, so it competes with the rootkit diagnosis. It does not, by itself, install an unsigned privileged driver or hide running processes from ordinary management utilities. The telemetry shows elevated hooks that selectively conceal malicious processes after restart. Those stealth functions at a privileged layer are the distinguishing rootkit-like capability, not merely whether the malware launches automatically.
C:Process masquerading uses a plausible filename or icon to make malicious activity look routine in process lists. It is a real stealth tactic, but name deception alone does not alter the operating system's privileged process-enumeration behavior. The question describes a driver reinstalling privileged hooks and hiding processes from standard tools. That points to a rootkit-like mechanism operating at a deeper layer. Analysts should compare trusted offline or protected telemetry with ordinary user-mode process listings before assuming a name change explains the missing entries.
D:An encrypted email attachment awaiting delivery is a potential future payload, not an installed driver already executing after reboot. The described malware is active on the host and affecting process visibility. Its behavior is not defined by message transport or attachment protection. The relevant category is stealthy privileged persistence rather than a dormant inbound file.