You save $69.98
SY0-701 Premium Bundle
- Premium File 1044 Questions & Answers
- Last Update: Nov 18, 2026
- Training Course 167 Lectures
- Study Guide 1003 Pages
You save $69.98
A remote-work gateway unexpectedly shows an administrative SSH port open to every internet address while HTTPS access is restricted to approved networks. Which closure should the team prioritize?
An internet-facing administrative service increases brute-force and exploit exposure even when its transport is encrypted. The security team should verify whether SSH is needed, then disable it publicly or restrict it to approved management sources and strong authentication. This reduces the actual exposed attack surface without unnecessarily disabling user-facing remote work.
Shutting down all websites is unrelated to the specific unexpected administrative service and would disrupt legitimate business operations. A targeted configuration correction is more appropriate when the evidence identifies one excessive ingress permission. Broad outages should not substitute for precise service inventory.
Encryption protects the connection content but does not remove credential guessing, authorization failures or software vulnerabilities in the service. Public availability increases the set of potential adversaries who can interact with SSH. Strong authentication and narrow source access remain important.
DNS is a foundational dependency for locating legitimate services. Blocking it indiscriminately may break remote access without correcting the public SSH rule. The team should focus on the exposed management port and validate dependencies before making unrelated network changes.
Ten new branch routers arrive with a factory login printed in their quick-start guides. The operations team plans to deploy them unchanged and rotate passwords later. Which issue should be corrected before deployment?
Factory credentials may be identical across a product line and are often published openly, making them unsafe for operational deployment. Unique secrets or strong supported authentication, limited management networks and verified configuration checks should precede production connectivity. Credential rotation plans matter, but postponing the first replacement leaves an avoidable attack window.
Management-network isolation reduces reachable attackers, but it does not make the factory password secret. A compromised authorized workstation or a technician with management access could still use the published value. The devices need unique managed credentials as well as a restricted management path before deployment. Network location alone is not an identity check.
Changing the account label does not protect a still-known credential if the device also accepts its original administrative login or recovery mode. Before commissioning, the operator should replace default secrets and validate actual authentication restrictions, not postpone their removal for administrative convenience.
Central multifactor authentication is worthwhile, but it protects only the portal path where it is enforced. A separately accessible local or emergency administrator account with a known factory password remains a bypass. The team must inventory and harden every management entry point, including console and recovery modes, rather than equating portal security with device credential security.
A power utility uses a managed service provider to maintain remote gateways. An MSP technician's account is compromised and used to access multiple customer segments. Which initial vector best describes the shared exposure?
MSP support identities often have sensitive connectivity and privileges across clients. Compromise of such an identity can turn an authorized supplier relationship into a shared route for malicious access. Customers should examine least privilege, session attribution, strong authentication and isolation of each tenant's administrative path. Incident scoping should examine every tenant reachable with the stolen MSP role, not assume the impact ended at the first alert. Separately revoking that role can preserve unrelated support service while reducing cross-customer exposure.
The incident involves remote authenticated access rather than physical entry at multiple facilities. Badge logs may be useful if local access occurred, but the described pivot uses the managed provider's credentials. The initial trust crossing is between supplier management systems and customer networks.
A compromised update pipeline would be another plausible supplier-origin attack vector, but no altered firmware or device update is described here. The observed cross-customer entry path is reuse of a compromised technician identity through existing remote-management trust. Investigators should distinguish authenticated administrative sessions from unauthorized software distribution, because containment and tenant isolation differ for each mechanism.
Supplier ownership of an account does not make its use automatically safe. The scenario specifies unauthorized use after compromise and cross-customer access. Trust in the provider should prompt evidence review and containment, not unconditional acceptance of its sessions.
A retailer's third-party inventory software starts installing an unsigned replacement module after the supplier's update server was accessed by an attacker. The supplier also misses a promised support response deadline. Which event indicates a cyber supply-chain compromise rather than merely contractual failure?
An attacker controlling the supplier's update path can deliver malicious artifacts through a normally trusted channel. The unsigned replacement and compromised server directly affect software provenance and endpoint execution. The retailer should stop deployment, compare signatures or trusted hashes, and coordinate incident containment separately from SLA enforcement.
Slow support response may violate a service-level agreement but does not by itself show that software integrity or distribution was attacked. Contract performance and technical supply-chain trust are different issues. The retailer needs update artifact evidence for the latter.
A delayed update can violate a service-level commitment while preserving the authenticity and integrity of the delivered artifact. Valid provenance and unchanged release content would not independently show that an attacker modified the software. The critical difference in the case is the compromised supplier update infrastructure distributing an untrusted replacement module; that is a technical supply-chain event, not just a missed delivery date.
A new contact or service desk route can affect responsiveness and contractual expectations, but does not itself indicate tampering with delivered code. The described malicious module distributed through a compromised update system is the supply-chain integrity event. It needs artifact containment and provenance verification, not just account-management reconciliation.
An accounts-payable clerk receives an email appearing in a real supplier conversation that changes only the bank account for a pending invoice. The message originates from a recently added forwarding rule in the supplier mailbox. What is the most likely social-engineering attack?
Hijacked mailbox access and conversation context make a fraudulent payment change look routine. The abnormal forwarding rule and changed beneficiary are classic business-email compromise indicators. The clerk should confirm banking instructions through an independently known supplier contact and preserve full message headers before any funds are sent.
An attacker may spoof a vendor using a similar domain and separately request a bank-detail change, but the current evidence points to a real supplier conversation and a forwarding rule inside that mailbox. Those signs support account or conversation compromise rather than purely external domain imitation. Header analysis should still verify the sending infrastructure; a generic lookalike-domain theory cannot explain the account-rule evidence by itself.
Existing conversation context can make fraudulent instructions look credible, especially after a mailbox is hijacked or forwarding rules are changed. A changed beneficiary is a high-impact payment exception and should be verified through a separately known vendor contact. The supporting mailbox-rule anomaly makes unquestioned legitimacy a poor conclusion even if every other line of the invoice is unchanged.
Payroll deposit mistakes affect employee payment details, but the described message changes a supplier's invoice destination and arises from a suspicious supplier mailbox forwarding rule. There is no payroll change record or employee account update. Identifying the correct payment workflow matters so the company freezes the affected supplier remittance and verifies it through the supplier's trusted financial contact.
A bank call center receives a voice call from someone claiming to be IT asking staff to read out one-time codes. A second employee receives a text asking for the same code at a lookalike bank domain. Which TWO classifications are correct? Select TWO answers.
Vishing employs voice communication and an authority pretext to manipulate recipients into sharing secrets or taking actions. A callback to a published, independently known help-desk number can challenge the claimed identity. One-time codes should not be read to unsolicited callers simply because they know the employee's name. The caller’s familiarity with a legitimate employee or internal department does not establish possession of a trusted channel. The bank should distinguish the call recording from authenticated help-desk ticket evidence before any reset.
Smishing uses SMS or similar text messages to create a deceptive login or verification flow. A lookalike bank domain can capture credentials and one-time codes. Reporting the message and navigating to the bank through a known channel are appropriate, rather than following the supplied link. An attacker-controlled SMS domain can also harvest current one-time codes during the short window when they remain valid. Reporting the sender, link and time helps fraud investigators search for related sign-in attempts without exposing the code.
The suspicious link and code request make the communication a phishing attempt, but its delivery channel is SMS rather than electronic mail. Channel classification matters because the investigator may need mobile message evidence and carrier reporting rather than mailbox logs alone. A text-delivered credential lure is specifically smishing even when its landing page resembles an email phishing site.
A claimed IT role is a common authority pretext, not proof that the voice caller is legitimate. Asking employees to disclose one-time codes over an unexpected call is consistent with vishing and should trigger independent callback verification. The bank must treat both channels as potentially hostile rather than granting voice callers automatic authority.
Credential stuffing involves trying known account credential pairs against login services, typically at scale. The described text instead persuades one recipient to enter a code at a lookalike domain, which is smishing. A one-time code may be stolen as a result, but theft by social deception does not itself establish automated reuse of leaked passwords.
Staff at a manufacturing supplier regularly visit an external engineering standards portal. After that legitimate portal is compromised, several visitors receive malicious browser redirects. What technique best fits this pattern?
A watering hole places malicious content on a website that a target community is likely to visit as part of normal work. The compromised standards portal attracts the supplier's engineers without individually emailing them. Responders should inspect portal traffic and browser artifacts while coordinating cleanup with its operator.
Targeted phishing could also lure engineers to a malicious destination, but the scenario says the actual third-party portal was compromised and staff visited it through ordinary routines. That distinction matters: the attackers seeded a frequently visited site rather than contacting each employee. Investigation should therefore include the portal compromise and legitimate visitor traffic.
A honeynet is a defender-operated set of decoy systems for observation. The standards portal is a real business resource altered by attackers to reach visitors. No controlled deception environment or deliberate defensive lure is involved in this scenario.
Router theft would produce different physical evidence and possible network disruption. The case instead shows legitimate browsing followed by malicious redirects from a third-party site. Treating it as a physical attack would fail to address the compromised web delivery channel.
A hospital user receives an email appearing to come from its benefits provider. The sender domain is bennef1ts-example.test while the actual provider uses benefits-example.test. Which interpretation best separates the visible tactic?
The altered letters and substituted digit create a lookalike domain that mimics the provider's identity. That supports both typosquatting as the naming tactic and brand impersonation as the social lure. The hospital should inspect full headers, reporting records and links before employees enter benefits credentials. A successful SPF or DKIM result for a domain controlled by the attacker would not prove that the domain belongs to the real benefits vendor. The analyst must validate the exact expected sender organization and any changed payment or login destination.
Similar typography and spelling do not establish domain ownership or authorization. Attackers can register nearly identical names and add convincing visual branding. Staff must verify the exact organizational domain rather than relying on a cursory glance at a familiar-looking sender.
DNS resolution and possession of a certificate show control of a particular domain, not authorization to impersonate the real benefits provider. The altered spelling is evidence of possible deceptive registration, and ownership should be checked against the provider through a separate trusted channel.
DNS can resolve domains controlled by attackers as reliably as legitimate ones. Successful resolution only shows that a record exists and can be reached. It does not certify brand ownership, business authority or safety of a website linked from an email.
A campus discussion board spreads an unsupported claim that emergency IT updates are spyware, urging students to disable protection before connecting to the university network. No software exploit is attached. How should the security team characterize the risk?
Deceptive claims can persuade people to disable safeguards or avoid updates, thereby weakening security even without malicious code. The organization should counter the claim with verifiable patch information and clear guidance. Manipulated user decisions are a social-engineering risk distinct from direct exploitation of a software flaw.
A buffer overflow requires a particular memory-safety failure and relevant executable input. The observation only reports misleading textual assertions, with no crash or vulnerable code path. The absence of an attached exploit does not eliminate social harm, but it does not establish memory corruption.
Popularity is not evidence of technical correctness or official authority. Repeated sharing may amplify a false claim. Students should confirm updates through the university's signed or authenticated security notices rather than treating community reposts as patch verification.
An authenticated and approved change notice would be evidence of a legitimate operational direction, not anonymous unsupported public discussion urging staff to disable protection. The risk in the case is false messaging influencing user behavior; no signed official instruction or validated emergency change is described. Source authenticity must be checked independently of popularity.
During a security test on managed desktops, an EDR alert records a process using an operating-system API to write bytes into another running process before starting a remote thread. A separate app crashes when an input exceeds its stack buffer. Which interpretation is accurate?
Creating execution in another process after writing to its memory is characteristic of process injection. An oversized input causing a stack-related crash may suggest memory corruption but does not alone prove exploitability. The analyst should collect call traces, crash dumps and affected binaries, keeping the two mechanisms distinct.
A cross-process write followed by remote thread creation supports an injection hypothesis, whereas an oversized input and a crash implicate a separate memory-safety failure. Both involve memory, but neither mechanism proves the other, so a single undifferentiated classification would obscure the necessary forensic tests.
Process memory and firmware storage are different attack surfaces. Remote thread creation in a running user or system process does not demonstrate writing boot firmware or persistent device code. Firmware modification would require separate flash events, integrity deviations or platform evidence.
Two different endpoint observations can both be real. A buffer crash in one program says nothing about the legitimacy of a separately logged cross-process write. Dismissing either requires correlation and testing of each event, not assuming that one finding negates the other.
A utility's maintenance program verifies that a configuration file is safe, waits for an operator prompt, then reopens the same pathname. Between the check and its later use, an unprivileged account can replace a symbolic link. What vulnerability is present?
A race arises because validation and subsequent use are separate operations on a mutable name. An attacker may redirect that name after the check, causing the privileged program to open another object. The fix should employ atomic or handle-based access with appropriate permission checks, not simply a longer wait.
Key exhaustion concerns a cryptographic or key-management design and is unrelated to a mutable symbolic link. The file path may change even if no encryption is involved. The utility should investigate filesystem identity and permissions rather than rotate unrelated credentials.
DNS poisoning changes hostname resolution, whereas the example concerns a local path, symlink and process timing. There is no domain-name lookup in the described sequence. Network DNS controls would not remove the check-use gap in the maintenance program.
A CA chain validates certificate identity, not the identity of a local file object reopened after a delay. The observed race can occur on systems without TLS certificates. Time in the vulnerability name refers to operation ordering, not certificate timestamps.
Please check your mailbox for a message from support@examlabs.com and follow the directions.