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 plant control dashboard suddenly resolves its vendor's legitimate name to a new address serving a counterfeit login page. Endpoint DNS cache entries differ from the approved resolver, and there is no scheduled migration. Which threat best fits?
Altered DNS answers can send users to a malicious host even when they type the legitimate vendor name. Divergent cache values and a fake login page support redirection as a working hypothesis. The team should validate resolver sources, clear poisoned entries and preserve DNS query evidence while isolating affected sessions.
Certificate renewal may change presented credentials or trust status without requiring a hostname to resolve to an attacker-controlled address. The central anomaly is the unexpected name-to-address mapping. Treating it as a routine TLS lifecycle event leaves the redirection unexplained.
Split-horizon DNS can legitimately supply different answers to internal and external clients, but such changes require approved resolver configuration and known endpoint identities. The case instead reports an unplanned address change, a counterfeit sign-in page and client cache values inconsistent with the approved resolver. Those observations support DNS manipulation, not a verified planned internal-zone policy.
A legitimate DNS failover would require change approval, authenticated endpoint ownership and validated records. The scenario supplies no scheduled migration, shows a counterfeit login page and notes disagreement with the approved resolver. Successful HTTPS navigation alone cannot establish that a new address belongs to the vendor. Treating that event as routine failover would ignore potential poisoned resolution and credential capture.
Customers at a retailer connect to a Wi-Fi SSID matching the store's official guest network, but the BSSID is unrecognized and browser certificate warnings appear. Staff have not approved a proxy change. What is the most plausible attack?
An attacker can imitate a familiar SSID using a different access point and entice devices to connect. The unknown BSSID and certificate warnings support investigation of a rogue network and possible interception. The store should compare radio scans with approved access points and instruct customers not to bypass certificate alerts.
An approved proxy change should have a record, a known destination and predictable certificate behavior. Unrecognized radio identifiers and unexpected warnings are not proof of legitimate change. The retailer should not normalize trust failures without validating the actual wireless infrastructure.
Multiple authorized access points can share one SSID, so an unfamiliar BSSID should be checked against the managed inventory rather than automatically condemned. But the scenario states that staff did not approve the change and that certificate warnings appeared. Those combined indicators make a rogue lookalike access point more plausible than assuming a sanctioned installation solely from its advertised SSID.
DNS manipulation could send customers to a counterfeit page, but it would not by itself account for clients associating with an unfamiliar physical access-point identifier. The duplicate SSID and unrecognized BSSID call for wireless-controller and radio investigation. Certificate warnings add further concern about on-path interception, although the team should still confirm the rogue device and traffic path.
A SaaS platform sees identical short-lived bearer tokens used from two unrelated devices within one minute. The legitimate user is active on only one; the second device performs unauthorized downloads. Which attack hypothesis best matches?
Bearer tokens generally confer session authority to the possessor until expiration or revocation under their scope. Use from an unexpected device can therefore indicate token theft and replay. The platform should revoke affected sessions, examine exfiltration paths and evaluate binding or additional risk checks for sensitive downloads. Investigators should compare token issuance and refresh events with the second device, then revoke the affected session if theft is corroborated.
A legitimate user may have multiple SSO sessions, but the observed second device is unrelated to the user and performs unauthorized downloads with an identical bearer token. That combination supports suspected token theft or replay. Session logs, device binding and token issuer records should be correlated; simply calling all concurrent logins routine would ignore the unauthorized action.
A bearer token generally authorizes whoever possesses it for permitted actions; cryptographic validation does not prove that the presenting device is the one originally authenticated. The unexplained duplicate token and unauthorized download are evidence of possible replay. Defenses may include short lifetimes, token binding where available and rapid revocation after confirmed theft.
Independent logins normally create distinguishable issuance or session records even when the same user is involved. The exact token match is an important anomaly and should be verified before labeling it harmless. A malicious second device using the captured bearer token is a plausible explanation, whereas an unsupported logging-artifact assumption would delay containment.
A bank logs a high-value transfer request from a victim's authenticated browser after the user visits an unrelated webpage. The transfer endpoint accepted the request without checking a CSRF token; no shell command was executed. Which interpretation is most accurate?
CSRF exploits a browser's tendency to send relevant session credentials with a cross-site request when defenses are insufficient. The missing anti-CSRF validation helps explain how an attacker-triggered transfer reached the application. SameSite controls, origin checks and action-specific tokens can help, but authorization and user intent still require validation. A valid cookie may travel with the forged request even though the bank-origin application never executed attacker script; that separation distinguishes this from XSS.
That mechanism would involve an application constructing an operating-system command from untrusted request data. The described event instead uses a victim’s already authenticated browser to send a transfer request without an appropriate anti-CSRF check. The absence of shell execution makes command injection the wrong classification even though both attacks may involve application inputs.
Malicious JavaScript on an attacker-controlled site can cause a browser to send cross-origin requests without executing script inside the bank’s own trusted origin. That is consistent with CSRF when the bank accepts a state-changing request based only on session authority. XSS would require attacker code executing in the bank-origin page, a different trust-boundary failure not established here.
A browser can attach session credentials to an induced request without the account holder knowingly authorizing a transfer. Authentication of the session is not proof of user intent for each state-changing operation. The bank should validate a suitable anti-CSRF control, origin and transaction authorization rather than assuming a valid cookie eliminates forged-request risk.
A manufacturer tests a legacy image processor and observes crashes with oversized image dimensions. A scanner claims remote code execution is already confirmed. No instruction-pointer control or exploit has been demonstrated. What report is defensible?
Crashes on malformed input can indicate an out-of-bounds condition, but controlled code execution requires further technical proof. The team should preserve reproducible inputs, crash traces and version information while isolating risky testing. Reporting the distinction supports remediation without overclaiming a compromise that has not been observed.
A remotely reproducible crash can be a serious availability issue and may indicate memory corruption, but it does not itself prove control of the instruction pointer or arbitrary code execution. The manufacturer needs a crash dump, affected instruction context and controlled exploitability analysis before escalating the finding to confirmed RCE.
Lack of a demonstrated exploit does not establish harmlessness. Repeated crashes under attacker-influenced input merit investigation for out-of-bounds access, denial of service, and possible exploitable corruption. The responsible conclusion is a suspected weakness with an unresolved exploitability claim, not premature dismissal or certainty.
An application crash can be a reliability defect, denial-of-service vector, or sign of a deeper memory-safety weakness. The oversized input is a legitimate test lead that should be reproduced and analyzed with crash diagnostics. Dismissing it as an expected rejection without investigating the failure is as unjustified as claiming remote code execution without exploit evidence. The report must distinguish observable crash from demonstrated exploitability.
After normal login to a hospital's scheduling service, an account suddenly acquires administrator rights via an undocumented group membership change. Which evidence would best support privilege escalation rather than a normal authorized role update?
A previously low-privilege account gaining administrative membership without a linked approval creates a strong escalation indicator. Correlating group-change logs, actor identity and session timing helps distinguish authorized provisioning from abuse. Investigators should protect those audit records and check what elevated actions followed. Evaluate whether the role was temporary or persisted.
Routine login time does not establish whether later privilege changes were authorized. A valid session can be misused after sign-in. The review must examine who altered the entitlement and under what approval, not infer safety from normal business hours.
Operating-system licensing is not evidence of authorization for an administrator role. A compliant endpoint can still be used for credential abuse or misconfiguration. The privilege transition should be validated against the identity lifecycle and change records.
Authentication shows a session was established; it does not authorize all subsequent permissions. Unexpected privilege elevation still requires a valid approval context and event correlation, especially where the new rights exceed the role’s normal scope. Treating the original login as universal approval would conceal escalation indicators.
A university file-download endpoint should permit access only within /public/reports/. Web logs contain requests with repeated ../ segments seeking /etc/passwd, and successful responses have not yet been verified. What attack behavior is shown?
Traversal exploits unsafe path handling to request files outside a permitted directory. Logs showing ../ sequences and a sensitive target support identifying the attempt, though they do not prove that the application served the file. The university should test canonical path enforcement and inspect response records before declaring data exposure.
Parent-directory markers can have a normal programming meaning, but in a constrained download path they may indicate attempts to reach unintended files. The targeted operating-system path strengthens the suspicious interpretation. Familiar URL syntax does not make an out-of-scope read request authorized.
Some request filters normalize paths before access checks, but parent-directory traversal sequences can be used to escape the intended directory when a handler resolves them unsafely. Their presence in logs demonstrates an attempt even though success is not yet proven. Calling the sequence harmless simply because normalization is possible would ignore the adversarial request target and the need to validate actual file-path containment.
Password spraying would generate distributed login attempts, often with repeated passwords against many accounts. The example instead probes file paths through a download endpoint. Authentication monitoring may matter elsewhere, but it does not explain requests for /etc/passwd via traversal syntax.
An identity provider records 100 accounts receiving one failed login each from distributed IP addresses, followed by a second round using the same candidate password. Another account suffers 400 rapid attempts from one IP. Which classification best fits?
Broad low-frequency guesses across many accounts fit password spraying and can evade per-account lockout thresholds. Hundreds of rapid guesses on one account fit concentrated brute-force behavior. The identity team should correlate source networks and outcomes, then apply risk-based protection without treating all failed logins as confirmed compromise. A rate limit per account alone may miss distributed spraying, while per-source controls can miss proxies; detection should correlate both account spread and repeated secret patterns.
Credential stuffing is usually characterized by replaying previously exposed username-password combinations. Distributed source addresses alone cannot establish that mechanism. The same candidate password sprayed across many accounts is a more specific clue to password spraying, while concentrated guesses against a single account resemble brute-force attempts. Analysts should correlate attempted secrets and account distribution rather than IP count alone.
Spraying typically tests a small set of passwords against many accounts, often at controlled rates, while brute force concentrates guesses on a particular target. This option reverses those patterns. Rate and distribution across identities are the essential distinguishing evidence in the logs.
The first series distributes a small number of guesses across many identities, which is characteristic of password spraying. A concentrated burst directed at one account is the more typical brute-force profile. This option reverses the meanings of target distribution and attack rate, which are more informative than the total number of failed requests alone.
A certificate service sees an audit claim that two different files share the same hash digest. Separately, TLS traces show clients being forced from a strong protocol to an obsolete one. Which TWO assessments are technically accurate? Select TWO answers.
A TLS downgrade is assessed from the versions offered, selected and permitted by each endpoint, with attention to whether a network adversary influenced negotiation. A file-hash collision is a different cryptographic property: distinct inputs with the same output under one defined digest algorithm. The analyst should check the handshake trace and server minimum-version policy, rather than infer a protocol downgrade from a matching file digest or certificate status.
For a genuine collision, verify that two byte-distinct inputs produce exactly the same digest under the same specified hash algorithm and processing rules. Merely seeing identical values in a dashboard could be caused by a copied file, reporting error or different digest configuration. Even a real collision does not by itself prove an intentional birthday-search attack; that attribution needs evidence of deliberately constructed alternatives and the threat context.
Different names do not establish different bytes, and a shared reported value may reflect a logging error or use of different algorithms. Even a validated collision does not by itself prove which collision-finding technique or adversary was involved. Verify the inputs, algorithm and digests before attributing an intentional birthday attack.
File digest equality and TLS parameter negotiation are independent observations. A real downgrade is established by supported protocol traces, endpoint settings and unexpected fallback behavior, not by a report about document hashes. Combining them without a causal link would misclassify the attack and impede both cryptographic investigations.
Revocation checks describe the validity status of an identified certificate, whereas collision testing compares the output of a particular hash algorithm on two distinct inputs. They can both arise in a PKI environment, but a revocation event does not show matching file digests. The certificate service must test each claim with its own evidence.
A security analyst sees a user account signing in from Karachi and then five minutes later from a European cloud address. The user is working from home with an approved VPN exit there. What is the best handling of this 'impossible travel' alert?
IP geolocation can reflect a VPN or proxy endpoint rather than the person's physical location. Matching the approved exit, enrolled device and session timeline can explain apparent travel without dismissing real compromise. A risk-based review should preserve evidence and investigate if other session indicators contradict the benign explanation.
The short interval is suspicious only if the two geographic readings represent distinct physical locations. A legitimate tunnel can make one session appear to originate far from the user. The analyst should correlate session and device identifiers with the VPN exit before deciding whether containment or credential recovery is warranted.
A broad ASN exception could conceal unrelated attacker infrastructure hosted by the same provider. Even a known VPN gateway should be matched to the organization’s configured exit endpoints and actual session records. Scoped context-aware rules can reduce false positives without granting unreviewed traffic permanent trust.
An authentic VPN explanation for one event does not prove that all subsequent sign-ins from unusual locations will be benign. Credentials and devices can later be compromised. Tuning should account for verified VPN addresses and session identifiers while retaining alerts when evidence no longer matches the trusted pattern.
An industrial operator's account becomes locked after several failed attempts, but access logs show a simultaneous successful session using a valid refresh token from an unfamiliar workstation. Which investigation is most urgent?
A valid refresh token can survive password failures and may allow continued access from a compromised device. The operator should examine token issuance, device trust and recent privileged actions, then invalidate suspicious sessions. Incident response must treat lockout and session authority as separate controls. Compare the recorded refresh event with user and device attestations.
A password reset does not universally invalidate previously issued sessions or refresh tokens; behavior depends on the identity provider and session configuration. The observed successful token session after a lockout is the immediate risk. Responders should enumerate and revoke suspect sessions through supported controls and verify access stopped.
A valid token signature establishes that the token was issued by a trusted service and not trivially altered; it does not prove the holder remains authorized. An unfamiliar workstation can replay a stolen token while the original account is locked. The industrial operator must correlate device, issuance and session evidence before clearing it.
Restoring sign-in functionality does not address a concurrent session that may be using stolen credentials. Waiting for routine review can prolong access to industrial resources. Session invalidation and an immediate check of token use are more important than a successful normal login test in the current evidence.
Please check your mailbox for a message from support@examlabs.com and follow the directions.