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
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.
A retailer's monitoring system blocks traffic to a known malicious domain but also reports a burst of audit events outside the configured schedule. Which interpretation best avoids overclaiming?
Multiple anomalies justify investigation but need interpretation against baselines, host context and enforcement results. Blocking an outbound attempt may mean the control worked; unusual logs might indicate attack activity, a schedule change or failure. Correlation should distinguish observed events from unverified causes before classifying the incident.
A firewall or DNS block establishes an attempted communication, but not execution of a specific malicious payload. The audit burst may be related or independent. The retailer should correlate endpoint processes, content, authentication and timing before claiming a successful ransomware incident. A blocked destination alone cannot identify malware family.
The blocked domain is a meaningful clue, but unusual log timing can reveal retries, compromised logging or a separate administrative issue. Dismissing it prematurely loses context. Analysts should review clocks, event sources, endpoint processes and policy changes to determine whether the two indicators share a cause.
Security updates can generate additional events, but their presence must be established from actual maintenance logs and schedules. The scenario specifically says the activity fell outside expected timing. Treating a possible benign explanation as proven would risk overlooking attempts to manipulate logging or unusual user activity.
An e-commerce platform has a 20-minute gap in its security logs during a suspicious deployment. An administrator argues that missing entries prove an attacker deliberately erased them. Which conclusion is best?
Missing telemetry can result from routine ingestion failures or an attacker intentionally disabling collection. Cross-checking endpoint sources, collector health, network flows, time stamps and deployment changes can distinguish these causes. The platform should preserve the uncertainty rather than assigning malicious intent before the supporting evidence exists.
A deployment coinciding with a logging gap does not prove either deliberate deletion or that pipeline failure is impossible. Ingestion health, clock offsets, endpoint logs and collection queues must be checked to distinguish technical interruption from attacker suppression; temporal proximity alone does not settle the cause.
Absence of a record is not equivalent to absence of activity when the monitoring path may have failed. Users and attackers can still perform operations during a collector outage. Other telemetry may reconstruct the missing time interval.
A service can remain available while security logging fails, creating blind spots for later investigation. Continued storefront operation does not verify integrity of its audit trail. The team should repair collection and determine whether relevant changes occurred while logs were absent.
A distribution depot runs public information kiosks on a business VLAN and critical conveyor controllers on an OT network. One kiosk is compromised but still needs a status API used for shipping updates. What segmentation change best limits lateral movement?
A restricted boundary permits the specific data exchange needed by shipping while blocking arbitrary commands to controllers. Firewall rules, application mediation and tests from compromised-kiosk segments can demonstrate that lateral paths are closed. The gateway should permit only authenticated status requests and log anomalous attempts. A mediation service can expose the limited status information without granting a kiosk general routing or control privileges. Test denial of controller administration and unrelated OT protocols from the compromised kiosk to demonstrate the boundary’s actual effect.
Shared organizational ownership does not imply equal trust between public kiosks and industrial controllers. Broad OT reachability gives a compromised kiosk an unnecessary path to safety-critical systems. Connectivity should reflect verified service dependencies rather than organizational location.
Complete disconnection might stop one route but would also prevent required shipping status flows. The business need can be met with a controlled narrow interface. A design should avoid unnecessary outages while still isolating controller access from untrusted public-facing devices.
Warning text informs legitimate users but cannot stop malware running on the kiosk from sending network packets. The demonstrated threat depends on connectivity and authorization, not user awareness alone. A technical segmentation policy is needed to enforce the trust distinction.
A water utility's access list denies every connection from contractor networks, but one maintenance vendor needs a read-only telemetry feed from a single server. Which ACL adjustment best follows least privilege?
A precise source, destination, protocol and service rule provides the requested maintenance data without opening unrelated controllers. The utility should verify the source identity and test that unintended paths remain blocked. Read-only application access must also be enforced at the service layer, not assumed from network permissions.
Authenticated VPN access identifies an allowed source population but does not justify every destination that happens to expose the protocol. The scenario names one read-only server. Broader reach could expose controllers and other sensitive devices, so the ACL should be restricted by source, destination and service together.
Application authorization is valuable but should not replace a network boundary when contractor access needs only one endpoint. A compromised vendor workstation could probe or attack other services reachable on the management VLAN. Defense in depth and least privilege favor exact destination and protocol filtering.
Source-IP scoping is useful, but it covers only one dimension of the permission. Allowing all controllers exceeds the stated need and could compromise OT process integrity through an unexpected service behavior. The access policy must identify the single authorized server as well as the approved source and protocol.
A retail store's point-of-sale terminals should only run a signed sales application and approved updater. Malware frequently arrives as unfamiliar executables from removable drives. Which safeguard directly constrains executable launch?
Application allow-listing blocks binaries that are not approved by policy, narrowing the execution surface on fixed-function terminals. Publisher and hash rules require maintenance as updates change. Testing the signed updater and exception handling preserves sales continuity while preventing unknown removable-media programs from running. Record policy denials during deployment.
Detection can help an analyst investigate an unauthorized process after or while it runs, but an alert-only policy does not prevent that executable from launching. Malware from removable media could act before the SOC responds. The fixed-function terminals need an enforced launch authorization policy for the approved sales application and updater, with detection as a supporting layer.
Signature scanning can stop known malware, but an unrecognized executable may still run because the configuration defaults to allowing anything not detected. The requested safeguard must enforce an explicit allow-list at execution time, not rely exclusively on signatures of previously seen threats. This distinction is important for unknown programs copied from removable media to a retail terminal.
A valid signature verifies a relationship with a signing key and can detect post-signing modification, but it does not make all signed software authorized for point-of-sale terminals. Trusted publishers may sign unrelated applications, and compromised signing keys can exist. Effective allow-listing must constrain approved identities or known artifacts according to the business function, rather than accept every generally trusted signature.
An online shop processes customer-uploaded PDF invoices in an untrusted document renderer. Management wants to avoid disconnecting the whole checkout network whenever a malformed file arrives. Which mitigation is best?
Confining the renderer limits what it can read, write and contact if its parser is exploited. A separate sandbox can keep checkout availability while untrusted documents are processed, subject to resource and escape controls. The shop should verify the renderer cannot access payment credentials or unrestricted network services.
Removing active scripts and checking names are worthwhile input controls, yet a malformed document can still exploit the underlying parser or renderer. Sharing the privileged payment process preserves the highest-impact escape path. The requirement is a containment boundary around untrusted parsing, not merely front-end filtering.
Containerization without restricted mounts, identity and network access does not provide the requested isolation from payment records. Antivirus coverage may miss a new parser exploit or malicious file read. The sandbox must enforce least privilege and distinct trust boundaries, not rely on the container label alone.
A dedicated host helps separate workloads physically or virtually, but a broadly privileged credential can reconnect the renderer to the sensitive payment environment. Compromise of the document service would then expose database administration despite host separation. Isolation must encompass identity, storage mounts and permitted network paths.
A bank must continue exchanging daily documents with a partner, but its old plaintext protocol has a critical known flaw and no patch is yet available. Which immediate action best mitigates the exposure while preserving the business transaction?
Removing the vulnerable endpoint from reachability closes that specific path while a validated secure channel preserves partner operations. The bank should verify compatibility, logging and rollback before switching. The partner's authenticated transfer tests should confirm that documents arrive correctly without exposing the deprecated protocol. Audit external reachability after cutover.
Source allow-listing reduces reachable clients but does not correct the protocol's known flaw or protect document confidentiality against exposure on the path. A compromised partner host could still exploit the legacy endpoint. The bank has a usable secure alternate transfer path, so disabling the affected public service is preferable.
Better passwords and monitoring may make some account attacks harder to conduct, but they do not provide transport confidentiality or remove the known flaw in the protocol. The business needs both continued document exchange and reduced exposure. A tested encrypted replacement is a more complete temporary mitigation.
An unauthenticated link may restore file availability while exposing confidential financial documents to anyone who obtains the URL. Replacing one insecure protocol with an ungoverned sharing path is not an acceptable risk reduction. The bank should use a tested authenticated, encrypted alternate workflow under change control.
A design supplier uploads restricted prototype files to object storage administered by an external manufacturing partner. Staff laptops use disk encryption and the upload connection uses authenticated TLS, but the partner's cloud administrators can access stored objects. Which TWO additional measures best protect confidentiality at this remaining storage trust boundary? Select TWO answers.
Separating key custody from the external storage operator prevents an administrator of the partner's object store from obtaining both ciphertext and the means to decrypt it. The supplier should define authorized recipients, rotation, recovery and audit controls in its own key-management system. Access testing should include a partner-admin account to verify that it cannot request decryption even though it can operate the storage service.
Encrypting the restricted prototype before it leaves the supplier's trusted application limits exposure to storage operators who do not possess the decryption key. It changes which party can see the content at rest in the partner's environment. This is not merely adding more transport encryption to an already protected connection. The supplier should verify that plaintext previews, metadata and temporary files are not inadvertently uploaded alongside encrypted objects.
Versioning and retention policies help recover from deletion, accidental overwrites or some ransomware behavior, which are availability and integrity concerns. They do not hide file contents from a storage administrator who already has read permissions. The supplier needs client-side encryption and separate control of keys to address the specified confidentiality requirement. These recovery features can complement, not replace, encryption.
Server-side encryption can protect against some storage-media theft and infrastructure failures, but this option leaves key control with the very administrators whose access the supplier seeks to restrict. If they are allowed to decrypt on behalf of the service, it does not establish confidentiality against them. It may remain a useful additional layer, but not the decisive protection at the stated trust boundary.
TLS protects files while they travel between endpoints, but its session protection generally ends once the receiving service stores the decrypted upload. An authorized administrator of that storage service may still read the resulting object. The scenario explicitly says transport is already protected and asks for confidentiality against storage-side administration. More trust in the network tunnel does not solve that key-custody problem.
A hospital contractor needs administrator access to update one imaging archive server for three hours. The vendor requests permanent domain-wide administrative permissions for convenience. What control best reduces misuse risk?
Just-enough and just-in-time privileges give the contractor the access needed for the specified maintenance without standing authority over other systems. Approval, session recording and automatic expiry provide accountability. The hospital should verify the temporary role closes and credentials are revoked when the three-hour window ends. The hospital should tie activation to the change ticket and vendor identity, and compare the session commands with the authorized server task. A narrow network path does not help if the temporary role itself retains unrelated domain permissions.
A nondisclosure agreement defines legal obligations but does not reduce privileges or shorten the attack window. Permanent domain-wide access exposes unrelated hospital systems. The contract is not a substitute for technical least-privilege enforcement.
Shared administrator accounts undermine individual attribution and may be used outside the intended work. Annual rotation leaves a long exposure period. Dedicated scoped credentials are more appropriate for vendor work, especially when patient information and clinical availability are involved.
Troubleshooting confidentiality does not justify suppressing all privileged session records. Sensitive details can be handled under retention and access policies while still preserving security oversight. The hospital needs attributable evidence if the server configuration changes unexpectedly.
A university cannot replace an unpatchable lab controller this semester. It isolates the controller behind an ACL and claims the compensating control is 'effective forever' without observing traffic. What ongoing assurance is needed?
Compensating safeguards require evidence of operation, not just approval at installation. Monitoring expected and unexpected traffic, verifying deny behavior and reviewing rule changes can reveal erosion of isolation. The university should track a replacement milestone because monitoring does not eliminate the controller's original vulnerability. Document each test result.
A versioned configuration review can reveal unauthorized edits, but it does not by itself prove that the active enforcement plane implements the intended rule or that traffic cannot bypass it. The legacy controller needs end-to-end checks from denied networks and monitoring of actual permitted flows. Reviewing a document is necessary governance evidence, not complete ongoing technical assurance.
A diagram communicates intended control placement but cannot prove the live ACL continues to enforce it after later changes. Configuration drift or routing modifications may create unintended access. Operational telemetry and targeted testing are needed to verify actual behavior.
An IDS can provide useful detective evidence but may miss attempts and cannot prove an ACL blocks every unapproved source. Attackers might avoid triggering signatures or use a new path created by a routing change. Effective compensating assurance combines monitoring with controlled deny-path tests and review of actual rule implementation while the controller remains unpatchable.
Please check your mailbox for a message from support@examlabs.com and follow the directions.