CompTIA Security+ SY0-701 Practice Test 44
Question 430
Two breaches affect different organizations. One attacker silently maintains access to a strategic aerospace laboratory and exports future propulsion designs without making demands. Another group encrypts a variety of retailers' systems and publishes payment instructions with deadlines. Which comparison most accurately describes their evidenced objectives?
- Both operations are security-awareness tests because the attackers used computer accounts
- The laboratory theft must be financially motivated because every intrusion primarily seeks direct payment
- The first incident shows intelligence collection, while the second most directly shows financial extortion
- Ransomware against commercial victims is necessarily political espionage rather than a profit-seeking operation
Explanation
Correct Answer
C:The aerospace attack prioritizes discreet access and acquisition of sensitive technical knowledge, supporting an espionage objective. The retailers face encryption plus explicit deadlines and payment instructions, which supports extortion for revenue. Either campaign could have secondary purposes, and the actor's nationality cannot be inferred with certainty from a motive alone. Nevertheless, evidence-based classification guides monitoring, response and risk communication: look for persistence and exfiltration in the first case, and contain propagation, preserve backups and address coercive demands in the second. The comparison is about observed goals, not a claim that every espionage event is state-directed.
Incorrect Answers
A:A legitimate exercise requires scope, rules of engagement and authorization. Covert extraction of strategic plans and coercive encryption with payment demands are not evidence of consent. The distinction being tested is attacker objective; mislabeling real compromise as training would delay incident response and obscure the very different recovery and disclosure needs.
B:Intellectual property can have monetary value, but silent sustained collection of aerospace plans without any payment mechanism primarily resembles espionage or strategic intelligence gathering. Analysts should classify what the operational evidence supports instead of assuming all attacks share the same direct financial motive. Attribution to a particular government also remains a separate question.
D:An attack against businesses is not automatically intelligence collection. Payment demands and broad coercive encryption are direct indicators of financial extortion, even if the attackers also stole files. Political or state-linked motives require additional signals, such as a sustained strategic target set or credible independent intelligence, rather than the simple fact that the victims operate companies.
Question 431
During a regional dispute, one group replaces a city council's public homepage with protest slogans. At a separate site, a different group changes industrial controller values until machinery overheats and production halts. An executive calls both events 'website vandalism.' Which threat-impact distinction should the security lead make?
- Both incidents affect only appearance and have no plausible service or physical consequences
- Ideological website defacement differs from sabotage of operational technology that can damage equipment and disrupt safety
- Neither incident requires investigation because visible slogans provide complete forensic attribution
- Industrial controller manipulation is harmless unless the attacker also publishes a message
Explanation
Correct Answer
B:Defacement with slogans often seeks visible ideological messaging and may fit a hacktivist pattern, although attribution still needs evidence. Unauthorized controller changes that overheat machinery are potentially destructive operational sabotage, regardless of whether any political message appears. Incident priorities must therefore differ: the plant requires safety coordination, validated process state, controlled isolation and evidence preservation; the website requires integrity restoration and investigation of web access. A protest motive does not erase technical impact, and industrial sabotage can occur without publicity. The correct distinction considers both the actor's apparent goal and the business or physical consequences.
Incorrect Answers
A:A public website can experience reputational harm or temporary unavailability through defacement, while altered industrial control signals may produce physical or safety effects. Treating both as cosmetic misses the operational risk of overheating equipment. Controls and recovery plans should reflect the affected asset and consequences rather than lumping dissimilar attacks under one label.
C:Slogans do not reliably identify the operator; impersonation and false flags remain possible. Nor does a visible web change rule out additional compromise. Both systems merit forensic analysis of access, persistence and affected services, with the industrial incident requiring heightened operational safety coordination beyond ordinary website restoration. Responder priorities must include affected services and any unsafe controller state even when a protest message is visible.
D:Manipulating industrial setpoints can cause real physical and availability consequences without a public declaration. The threat is the unauthorized change and its effect on machinery, not whether the attacker issues a manifesto. Requiring a message before classifying sabotage would ignore actual controller evidence and could delay emergency containment. Independent process readings and controller logs can establish harmful intervention without any public-facing statement from an attacker.
Question 432
A large university sees daily port scans originating from disposable cloud hosts. Several produce no successful logins and appear to use an easily available scanning script, yet senior managers want to describe each source as a sophisticated state actor in the risk register. How should the SOC report these observations?
- Assign nation-state attribution to all cloud scanners because their IP addresses are hosted externally
- Describe observed scanning behavior and evaluate capability, persistence and intent before claiming a sophisticated actor
- Discard every scan as harmless because commodity tools are publicly downloadable
- Publish names of alleged operators without comparing infrastructure and independent intelligence
Explanation
Correct Answer
B:Security reporting should separate confirmed facts—scan frequency, targeted ports, follow-on authentication attempts and any exploitation—from inferences about the operator's resources and intentions. Public scanning tools do not by themselves prove advanced tradecraft, and even simple reconnaissance can precede serious compromise. Analysts should inspect persistence, tailored payloads, credential activity and corroborated intelligence, clearly stating confidence and uncertainty. Defensive action such as tightening exposed services can proceed without a named adversary. This produces an auditable risk assessment rather than exaggerating all routine Internet noise into nation-state activity or dismissing signals merely because a common script was used.
Incorrect Answers
A:A cloud address identifies a service location, not the organization operating a scan or its objective. Both inexperienced individuals and well-resourced groups can rent infrastructure and use the same utilities. Assigning state attribution from hosting alone would turn a common observable event into an unsupported conclusion and distort resource prioritization.
C:Routine scanning has varying levels of risk. A publicly available tool can be used by a careless hobbyist, a criminal or an advanced team, and an exposed critical service may still be vulnerable. Ignoring all attempts would discard useful attack-surface telemetry and miss a progression from reconnaissance to authentication or exploitation.
D:Public attribution requires more than a source IP or familiar scanning fingerprint. False or premature naming can misinform stakeholders and interfere with incident handling. Analysts should preserve raw telemetry and look for independent corroboration before identifying a group, even when leadership asks for a simple, confident threat label. Public labels should reflect corroborated findings and their confidence rather than leadership's preferred narrative.
Question 433
The finance department wants to deploy a browser extension that formats exported invoices. Its manifest requests permission to read and modify content on every website, including an authenticated payroll dashboard. The extension appears in a popular browser store and has a verified publisher badge. What risk should endpoint administrators evaluate before permitting deployment?
- Approve the extension if deployment is centrally managed through the corporate browser policy, without limiting its permitted websites.
- Rely on the publisher’s valid package signature and verified storefront badge as sufficient authorization for all-site page access.
- Test that the extension formats sample invoices correctly and approve it without evaluating access to unrelated payroll pages.
- The extension could read or manipulate protected page content under the employee's authenticated browser session
Explanation
Correct Answer
D:Broad read-and-modify permissions can expose payroll identifiers, session-visible values or page actions even without a downloaded executable outside the browser. The threat is that the extension runs with access to an authenticated browsing context and may manipulate what the user sees or submits. Administrators should restrict extensions by allowlist, require narrowly scoped host permissions, assess publisher controls and monitor changes to extension updates. Signing or a store badge can inform trust but is not proof that requested privileges are necessary or safe. A formatting extension should not ordinarily need access to every corporate website.
Incorrect Answers
A:Centralized browser management helps administrators select packages, maintain versions, and remove unsafe extensions quickly. But the installed extension still receives the broad host permissions described in its manifest, including visibility into payroll web pages. Distribution control does not limit what the extension can inspect once a user is authenticated. A host-permission review and narrower scopes remain necessary even for centrally deployed software.
B:Signatures can provide integrity and publisher attribution for an extension package, and a verified listing improves supply-chain confidence. Neither mechanism restricts runtime permission to read or modify web content in authenticated payroll tabs. An authorized publisher can also request capabilities that exceed a user’s business need. Administrators must examine host permissions and data-handling behavior rather than treating package authenticity as least privilege.
C:Functional testing establishes that the tool performs its intended invoice-formatting task, which is necessary for business acceptance. It does not show what data a broadly privileged extension can read from other websites under the same browser identity. The requested manifest allows access to payroll content, a separate confidentiality and manipulation risk. Security acceptance needs permission scope and trust-boundary testing, not just a successful invoice-formatting demonstration.
Question 434
A university employee finds a poster beside the new badge reader instructing staff to scan a QR code and 'renew access.' The code opens a login page with campus colors, but the browser address is not part of the university's approved identity domains. The visitor is asked for a password and a one-time passcode. Which attack explanation best fits the evidence?
- A trustworthy login because the counterfeit page presents a valid HTTPS certificate
- Authorized badge enrollment because printed notices inside a building are approved by facilities
- QR-code phishing that routes users to an impersonated identity page to capture credentials
- Normal TLS certificate maintenance that cannot expose account passwords
Explanation
Correct Answer
C:A QR code is being used as the lure and transport to a deceptive login page outside the institution's trusted domain. The page impersonates the university and asks for both a password and a one-time code, suggesting a credential-harvesting or real-time account takeover attempt. The employee should stop, report the poster and use a previously known enrollment channel to confirm any requirement. Security can remove the physical lure, examine the destination and check whether others submitted secrets. HTTPS transport may still be present, so domain identity and business context are more discriminating than the padlock alone.
Incorrect Answers
A:A valid HTTPS certificate can prove that the browser has an encrypted connection to the domain shown in its address bar. It does not prove the domain belongs to the university or that the page is authorized. Attackers routinely obtain certificates for lookalike domains; relying on the lock icon ignores the unrecognized identity endpoint and requests for credentials.
B:Physical placement does not establish organizational approval. An attacker may paste posters over authentic notices or exploit busy entryways. Enrollment should be verified through an established university channel or official application. Staff should not trust a request for one-time codes merely because the QR code is near a legitimate access-control device.
D:Certificate maintenance normally involves renewing or deploying certificates on established services, not collecting individual passwords through an unexpected external site. The request for a personal one-time passcode and a mismatched domain are direct social-engineering indicators. Treating the page as routine maintenance would fail to address potential credential theft. The spoofed campus color scheme and external login domain make the account-harvesting risk concrete.
Question 435
A medical-device company signs release installers after a CI pipeline finishes. Investigators learn that an attacker gained administrative access to a build runner, replaced a compiled component before packaging, and caused a malicious but validly signed installer to reach customers. The signed file was not modified during transport. Which trust boundary failed at the earliest decisive point?
- Integrity and isolation of the build environment before the legitimate signing process accepted its output
- Rely on the valid publisher signature and a clean endpoint antivirus scan to approve the compromised release
- Increase HTTPS transport requirements and add a second download mirror while leaving build-runner privileges unchanged
- Release-checksum calculation, because recomputing a hash after signing could always distinguish approved code from malicious signed code
Explanation
Correct Answer
A:The attacker controlled the build runner before the organization generated and signed the final artifact. That compromised execution environment produced malicious content which the legitimate release process then authenticated as an organizational build. Protecting runner administration, isolating ephemeral jobs, constraining package dependencies and validating artifact provenance before signing address the earliest broken trust boundary. Signing should operate on independently verified build outputs with controlled approval, not assume that a build agent is trustworthy simply because the pipeline succeeded. The signature still helps detect tampering after publication, but it cannot retroactively establish that an already compromised build was benign. The entry point is upstream software-supply-chain integrity, not the customer's last-mile download path.
Incorrect Answers
B:A verified signature confirms that the package matches what the authorized signing key signed, not that the build runner was uncompromised before signing. Endpoint scanning can detect some known malicious patterns but is not a substitute for trustworthy build provenance. The attacker changed the component upstream, so both controls may accept the altered signed file. The required investigation concerns build isolation, artifact integrity and signing approval gates before the release was produced.
C:Transport encryption and redundant mirrors help prevent in-transit alteration and improve distribution reliability. But the malicious component was inserted on an administrator-controlled runner before the legitimate signing step, and the installer remained unchanged during delivery. Stronger TLS settings would faithfully distribute the same compromised artifact. Repair must address the earlier trust boundary by protecting build identities, source-to-artifact provenance and approval of the input to signing.
D:A checksum can reveal changes when compared against a trusted, independently obtained reference digest. If both the installer and its published checksum originate from the same compromised pipeline, their values may agree even though the artifact is malicious. Recomputing the hash after the organization has signed a tainted release provides no independent assertion that the build followed approved source or dependencies. Verified build provenance and separated signing approval offer stronger evidence about the earliest compromise point.
Question 436
A hotel chain's headquarters uses an enterprise Wi-Fi SSID named HQ-Staff. Employees report a second HQ-Staff network whose signal is unusually strong near a public café, and phones that join it show a custom login form asking for their corporate passwords. Network operations confirms the access point is not managed by the company. Which technique is most likely?
- A sanctioned captive-portal change, because the SSID text matches the employee network
- A normal wireless upgrade that cannot impersonate authentication simply by duplicating an SSID
- An evil-twin access point impersonating the corporate network to harvest user credentials
- An authorized roaming enterprise access point using a managed certificate profile and the official corporate enrollment service
Explanation
Correct Answer
C:An evil twin advertises a familiar network name while operating as a separate malicious access point. Victims may join it automatically or be lured by signal strength, after which a fake captive portal requests credentials. The hotel should identify and remove or report the rogue transmitter, enforce enterprise Wi-Fi authentication with validated server certificates, and instruct staff not to enter company secrets into unsolicited portals. Review whether credentials were submitted and revoke exposed sessions if necessary. The technique is about network impersonation and phishing, not storage or database availability. Merely matching an SSID is never adequate identity verification.
Incorrect Answers
A:The SSID is a public network identifier that nearby access points can advertise. Matching text does not authenticate the hardware or prove that the login page is controlled by the hotel chain. The unapproved nearby transmitter and request for employee passwords are stronger evidence than a familiar network name; operations should verify trusted wireless identity independently.
B:Wireless upgrades require approved change records and managed access points. A copied SSID can entice clients into associating with an adversary-controlled network, especially when device configurations lack strong server certificate validation. Treating the name as proof of a legitimate WPA or infrastructure transition misses the credential-collection page and unauthorized physical transmitter.
D:A legitimate roaming enterprise access point could broadcast the same company SSID in another location, so the matching name and strong radio signal alone are not proof of malice. The decisive facts are that network operations does not manage this device and its custom portal asks for corporate passwords. An approved enterprise access point would participate in authenticated network management and established enrollment, not present an unknown password-collection page.
Question 437
A payroll assistant receives a text under the familiar sender name of the company's courier. It claims a package will be destroyed unless a small fee is paid through a shortened link within ten minutes. Security training warns that sender identifiers and links can be spoofed. What verification method minimizes the risk of acting on a forged message?
- Reply to the message with the one-time code delivered to the assistant's phone so the courier can verify the account
- Check shipment status through the courier's official app or a previously saved, independently entered web address
- Trust the sender label because SMS systems prevent attackers from copying a known sender name
- Follow the shortened URL and decide whether to pay solely from the browser's HTTPS padlock
Explanation
Correct Answer
B:An independent, previously trusted application or address breaks the attacker's control of the link and sender label. The assistant can inspect known shipment records without opening the text's shortened destination or submitting credentials there. If no shipment is listed, the message should be reported and ignored. This method addresses spoofing and URL redirection rather than relying on message appearance. A real courier may send legitimate reminders, so verification is preferable to assuming every delivery notice is malicious. The key security decision is to establish a separate trusted channel before paying or sharing personal information.
Incorrect Answers
A:A one-time code may be an authentication secret intended for a legitimate service, not a courier identity challenge. Sending it in response to an untrusted text can help attackers take over an unrelated account. The assistant should not validate a suspicious sender by providing additional credentials through the same potentially compromised communication channel.
C:SMS sender names are not reliable proof of origin; presentation mechanisms vary by carrier and threat actors can spoof or abuse them. A matching label makes an attack more believable but does not validate the payment demand. Trusting it without independent verification would allow a familiar name to override the suspicious urgency and redirected payment site.
D:HTTPS can encrypt the connection to the host shown in the address bar, including an attacker-controlled site. A short URL also conceals the final domain until it is followed. A padlock cannot establish that the courier sent the message or that the requested fee is genuine; the known official app is the safer independent source.
Question 438
A travel-booking API accepts a URL and generates a preview by fetching it from a backend server. An attacker supplies an address that resolves to the cloud instance metadata interface. The fetch retrieves temporary service-role credentials, which the API exposes in its preview response. Which weakness connects the public preview feature to privileged cloud credentials?
- Cross-site scripting in the attacker's browser, because the user interface executes a downloaded script
- Server-side request forgery allowing the backend to contact a sensitive internal metadata endpoint
- A redirect that only moves the external visitor to a public news site
- An object-level authorization check on normal customer reservations
Explanation
Correct Answer
B:Server-side request forgery occurs when an application fetches an attacker-chosen resource without restricting reachable destinations. In this case the backend can reach the cloud metadata interface and accidentally returns temporary role credentials, crossing from an untrusted URL parameter into a privileged infrastructure service. Mitigations include strict destination allowlisting, DNS and redirect revalidation, blocking link-local metadata destinations, using hardened metadata service controls and minimizing the instance role's permissions. Rotate exposed credentials and review cloud audit logs for their use. The technical problem is not that the attacker has a cloud identity initially; it is that the server acts as an unintended request proxy.
Incorrect Answers
A:Cross-site scripting involves untrusted content executing in a user's browser under a page origin. Here the important HTTP request originates from the backend preview service and reaches a network endpoint unavailable directly to an external user. The boundary failure concerns server-initiated requests, not merely client-side code execution or a malicious rendered preview.
C:An ordinary open redirect sends a client to another destination but does not necessarily make the backend read and return sensitive metadata. The preview server itself initiated a fetch to an internal endpoint and exposed its contents. That combination is essential to the observed credential leak and differentiates this event from a simple client-side navigation problem.
D:Insecure direct-object reference permits accessing another object's data by manipulating identifiers without proper authorization. The attacker did not guess a booking reference or bypass a normal customer-object check. Instead, arbitrary URL fetching reached a privileged cloud endpoint; object-level API permissions would not directly close that network request primitive. The exposed information consists of metadata credentials, not another passenger's booking object.
Question 439
A customer is already signed in to a financial portal. A promotional website overlays a large invisible iframe containing the portal's account-settings screen and aligns a hidden approval button underneath a visible 'claim voucher' control. The customer clicks the visible area and unknowingly changes an account setting. What technique best explains the manipulation?
- Credential stuffing that uses stolen password pairs to authenticate to unrelated accounts
- DNS cache poisoning that replaces the portal domain's resolved server address
- Business email compromise that directs the finance team to change a vendor bank account
- Clickjacking through UI redressing of an authenticated page inside a deceptive frame
Explanation
Correct Answer
D:Clickjacking, also called UI redressing, causes a user to click elements of a legitimate page without realizing that those elements are present beneath deceptive content. Because the victim is already authenticated to the finance portal, the click can submit a state-changing request with the existing session. Defensive measures include the Content-Security-Policy frame-ancestors directive or suitable X-Frame-Options restrictions, plus confirmation or reauthentication for sensitive actions. CSRF tokens alone may not stop a click performed through a legitimately rendered framed interface. The attack exploits how an authorized application is embedded and presented, not a stolen password or forged DNS answer.
Incorrect Answers
A:Credential stuffing involves replaying previously exposed login pairs against accounts and depends on authentication attempts. Here the legitimate customer is already signed in, and the attacker leverages the existing browser session rather than presenting stolen credentials. The click is redirected to a hidden interface control, making user-interface deception the relevant mechanism.
B:DNS poisoning changes resolution information and may redirect a hostname to the attacker's infrastructure. The portal's legitimate page is actually present inside a frame in this case, and the attacker's main power comes from overlaying controls. There is no evidence that DNS entries or name-resolution caches were altered. The recorded hostname and address resolution remain consistent with the legitimate service.
C:A business email compromise typically uses fraudulent messages or an attacker-controlled mailbox to request a payment or banking change. The victim in this scenario is misled by a graphical page overlay, not an email instruction from an impersonated executive. Although both may cause unauthorized settings changes, their delivery and protective controls differ.
Question 440
A third-party monitoring company uses a single shared integration password for service accounts at six independent clients. An attacker compromises the monitoring company and extracts that password, then logs into every customer's telemetry dashboard. Each customer otherwise has a separate network perimeter. Which design decision most directly multiplied the damage?
- Per-customer unique service identities constrained to their respective monitoring functions
- A missing TLS certificate on one dashboard, regardless of whether credentials were reused
- Using the same powerful service credential across distinct customer trust boundaries
- A vendor certificate that expired on the same day at all six independent organizations
Explanation
Correct Answer
C:Credential reuse made one supplier breach an authentication compromise for six separate customer environments. A shared powerful account crosses administrative and legal trust boundaries, so a single stolen secret defeats perimeter separation at every accepting service. Replace it with unique per-customer, narrowly scoped machine identities, individually rotated secrets or short-lived credentials, and centralized monitoring that can attribute actions to a particular integration. All customers should revoke the reused secret and review access logs for misuse. The lesson concerns blast-radius design: valid authentication is not safe when credential scope and reuse let one compromise spread across independent tenants.
Incorrect Answers
A:Distinct identities and secrets per customer would limit the reach of a stolen password to whichever account was compromised, subject to each account's scopes. They are a standard risk-reducing architecture, not the defect observed. The failure is the opposite: one secret was accepted by several otherwise isolated client environments. Distinct client identities would also make incident scoping and credential rotation more tractable.
B:TLS protects credentials and application data while a connection traverses a network, but the scenario identifies a password stolen at the supplier and reused across customers. Even perfect HTTPS transport would not prevent use of an already extracted valid secret. The risk requires credential and trust-boundary isolation in addition to transport security.
D:An expired certificate can cause handshake failures or trust warnings, but it does not independently reveal the same valid service password at multiple companies. There is no certificate-theft indicator in the facts. The attack succeeds through reuse of a stolen identity secret, not a synchronized certificate-expiration event. Revoking and segregating the shared integration secret is therefore a more direct containment action.