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 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.
A government web service is supposed to enforce a standardized security baseline, but one administrator disables audit logging on several instances to reduce storage cost. Which approach most directly prevents unreviewed configuration drift?
A versioned baseline can define required audit settings and detect or remediate deviations from approved state. Exceptions should be traceable, especially when storage concerns need legitimate alternatives. The agency should monitor compliance and investigate repeated drift rather than rely on configuration snapshots taken once. Review exception expiry explicitly.
Emergency actions sometimes require an expedited workflow, but post-hoc tickets alone cannot detect whether audit logging remains disabled on each instance. Without desired-state comparison, configuration drift may persist after the emergency ends. Baseline-as-code, change approval and periodic or continuous enforcement make deviations visible and subject to authorized remediation.
Aggregate event volume can look healthy even when one important service stops forwarding security logs. A large system may produce enough background records to conceal an unmonitored instance. The program needs per-asset configuration checks against a versioned baseline and alerting on specific disabled controls, not only broad activity-count trends.
A risk owner may legitimately revise retention or storage design, but changes to required audit collection must be deployed consistently and tested. Untracked manual exceptions can leave some systems without essential evidence and with no accountable restoration date. A governed baseline with time-limited exception handling is the mechanism that prevents unauthorized configuration divergence.
A remote support company retires an old server that previously stored customer credentials. The administrator plans to switch it off and sell the disks without sanitization. What decommissioning requirement matters most?
Decommissioning should include inventory, key or credential revocation, approved sanitization and proof that the method was effective for the media type. SSDs and encrypted drives may require different procedures. The company should retain disposal evidence and check that retired server identities cannot still access production resources.
Resale does not require exposing customer credentials to the buyer. A hardware test can be performed using clean test media. Keeping sensitive disks readable creates a direct residual disclosure risk after the company loses control of the equipment.
Removing shortcuts changes the user interface, not the underlying stored records. Files and credential stores may remain fully recoverable. Secure disposal must address actual data persistence and relevant storage technology.
Hostnames are labels and do not erase storage blocks or revoke credentials. A buyer with direct disk access may recover data regardless of what the machine was called. Decommissioning is a data and identity lifecycle activity, not a naming exercise.
A logistics center commissions replacement access-point controllers using an automated factory-reset process. A test replacement rejoins the warehouse network with a published factory administrator password before the provisioning job rotates it. Which SECURE BOOTSTRAP change best closes that recurring default-credential window?
The provisioning sequence should initially quarantine a factory-reset or replacement controller on a limited setup path. It must assign unique controlled authentication, restrict management reachability and test that published factory credentials no longer work before production joining. This prevents a recurring bootstrap gap rather than fixing only the original deployment. Asset records and recovery procedures should show which controller received each credential.
A scheduled scan can identify a misconfigured replacement eventually, but it leaves a window when a known factory password is valid and reachable from ordinary devices. A compromised warehouse workstation could exploit that interval before the scan. Secure onboarding should prevent production exposure until credential rotation and management-plane controls are verified for each newly reset controller.
Central dashboard restrictions do not necessarily cover a device’s own local management interface during initial startup. The test demonstrated that the published factory password is accepted while the replacement is already reachable. The security boundary must cover the pre-commissioning interval and all local entry points, not merely a portal that administrators use after the device becomes operational.
A stronger shared secret is still a fleet-wide credential whose compromise exposes multiple controllers and weakens attribution. Putting it in a widely used runbook may further broaden access. Replacement speed can be preserved through automated unique-secret issuance and a secured recovery process, instead of substituting another common password for the factory default.
A chemical plant has more than thirty network services enabled on an aging control gateway. Only two documented data feeds are needed by operations. Which change most effectively reduces the attack surface without disrupting the process?
Service enumeration, flow measurement and staged disablement can shrink network exposure while preserving the two essential feeds. Approval and rollback mitigate the risk of changing a sensitive gateway. Successful post-change tests should confirm both feed values and timing, not merely that the device responds to ping.
Broad shutdown can interrupt safety and telemetry functions in an industrial control environment. The gateway's two approved feeds are known dependencies that need preservation. Inventory, a staged maintenance window and post-change tests let the plant reduce unnecessary exposure without learning about critical dependencies from an outage.
Segmentation can restrict some paths, but any allowed maintenance host or compromised neighbor can still interact with unnecessary listeners. Attack surface reduction means removing unused services as well as controlling reachable interfaces. The plant should validate actual dependencies and disable extra protocols rather than rely exclusively on VLAN membership.
A perimeter firewall may reduce remote reachability, but it cannot establish that unnecessary local listeners are safe or that maintenance paths are narrow. A marketing warranty is not a service-by-service security test. The plant should verify which two feeds are required and disable the rest after safe testing.
A retailer has endpoints that download invoice attachments and communicate with a central payment platform. Which TWO safeguards provide complementary protection at the HOST boundary? Select TWO answers.
A host firewall limits inbound and outbound paths to the services the device needs, reducing the ways malware can communicate or spread. Its protection complements process-aware endpoint detection. The retailer should verify that necessary payment and update services remain reachable while unauthorized destinations are denied. Retest after agent policy changes. Test the host firewall from a permitted payment destination and an unapproved peer to confirm the narrowly specified service routes are really enforced.
Endpoint protection can observe or block suspicious execution, persistence and malicious file behavior on the terminal itself. It reduces risks that network filtering may miss, particularly when a malicious attachment executes locally. Policy and alerts should be tuned to preserve legitimate checkout functions. Analysts should review any prevention alerts associated with payment applications. Endpoint monitoring should identify suspicious child processes launched by invoice viewers even when the network connection uses approved payment ports.
A perimeter firewall can reduce unauthorized network paths into the payment service, but it is not a substitute for endpoint behavior controls on laptops that open invoice attachments. The malicious program can still execute locally and access user files. The scenario asks for complementary HOST-level protections: restricted host connections and process detection or prevention.
Backend access logs can help investigate which requests reached the payment platform, but they cannot reliably reveal local malware execution, script behavior or dropped connections on the cashier terminal. Losing endpoint events creates a visibility gap exactly where attachment-borne threats begin. The endpoint should retain focused process monitoring alongside a narrow host firewall.
Delayed archive scanning may discover a malicious attachment for later investigation, yet the risky local execution can already have occurred. It is also a separate service control rather than protection at the host execution boundary. Endpoint behavior prevention and local network policy provide the immediate complementary defenses sought for cashier devices.
An e-commerce service depends on a legacy server that cannot be patched for another quarter. The team considers host intrusion prevention while planning a replacement. Which deployment is most defensible?
A targeted HIPS rule can block observed exploitation behavior in a vulnerable legacy service without editing its unsupported application. Because this host cannot be patched immediately, test the rule against legitimate transactions and watch for false positives, crashes and bypass paths. Retain logs showing which actions were denied and review the exposure at an agreed date. HIPS is a compensating measure, not a repair of the underlying code flaw, so replacement or supported patching still remains necessary.
Detection-only operation can provide valuable visibility into attacks against an unpatchable service, but it does not prevent exploitation before staff respond. The option also wrongly claims full protection while the underlying vulnerability remains. An appropriate temporary HIPS policy should be tested for safe blocking where possible and its residual gaps tracked until the server can be replaced.
Network signatures can block some external exploit attempts, but they are not an installed host IPS and may miss local execution, encrypted traffic or alternate attack routes. The server is still unpatched and needs layered controls. The scenario specifically asks for defensible host intrusion prevention with compatibility tests and documented limits rather than labeling a network sensor as host protection.
A broad untested prevention rule may disrupt critical application functions while the original software vulnerability remains. An interim HIPS control should be targeted, validated against known exploit behavior and operational workflows, with the residual exposure and replacement plan documented.
A company operates virtual machines on a public IaaS platform. Its provider patches physical hypervisors, but a customer engineer leaves a guest management port open to the internet. Under shared responsibility, who should correct the exposed guest configuration?
In IaaS, customers commonly retain responsibility for guest operating-system configuration, hosted application security and IAM policies. The exposed management port should be closed or tightly scoped, and historical access reviewed. A responsibility matrix makes the boundary clear without shifting an internal configuration error to the provider.
Provider management of physical infrastructure does not usually include every customer-created guest rule. The host can be patched while guest services remain publicly reachable. The company must distinguish provider-controlled layers from resource settings it manages within the IaaS account.
Hypervisor patching is typically a provider responsibility in IaaS, but that does not transfer customer-defined guest-network access policy to the provider. The company remains responsible for verifying its instance security-group or guest firewall settings and closing the unintended administrative path.
Provider segmentation can protect the underlying infrastructure, but it does not automatically restrict guest-level management services that the customer explicitly exposed to the internet. The same IaaS deployment can have a well-maintained hypervisor and an unsafe guest policy. Responsibility follows the particular control plane and configuration, not merely where the virtual machine is hosted.
A warehouse replaces an on-premises sensor database with a managed database service. Previously its staff patched the operating system; now the provider handles database-host maintenance. Which responsibility remains with the warehouse?
Managed hosting transfers much of platform maintenance to the provider but typically leaves the customer responsible for appropriate data and user permissions. The warehouse should configure record access and review key ownership and retention. A change in hosting model does not make internal role governance disappear.
A managed database provider normally retains responsibility for its host operating system and platform maintenance; customers do not patch its physical hosts directly. The warehouse remains responsible for customer-controlled data access, retention and encryption settings under the agreed service model. Attempting host administration crosses the provider-managed boundary.
Provider certifications can support assurance about infrastructure controls within their scope, but they do not validate customer-defined roles or account assignments. A database can be well maintained while customer IAM grants remain excessive. The warehouse needs its own entitlement and data-protection review.
Encryption at rest helps limit exposure of raw storage but does not replace authorization for legitimate database APIs or deletion schedules. Customer-controlled users could still retrieve or retain sensitive records improperly. Role scoping, key choices and retention remain relevant customer duties even when host patching is outsourced.
A factory sends machine telemetry from an OT network to a cloud analytics environment operated by another business unit. Engineers propose using the same unrestricted service account on both sides. What architecture concern is most significant?
A broad shared account can carry an intrusion from less trusted analytics into the production environment. Scoped service identities, one-way or brokered data flows and access logs constrain that risk. The factory should document which telemetry may leave OT and what remote commands are prohibited, preserving safe operations.
TLS can protect traffic in transit but does not decide whether a workload is entitled to access every controller and cloud API. Sharing a broad identity across OT and analytics extends compromise impact across administrative boundaries, so encryption cannot replace scoped authorization and segmentation.
Unified logging can improve incident correlation but it does not limit the shared identity that has excessive access on both sides of the boundary. The architecture must reduce the actual permissions and trust reachability, not rely on observation after an unauthorized call.
HTTPS can protect a connection but does not show which identities, datasets and administrative domains it crosses. Diagrams and responsibility records remain needed to assess authorization and dependency. Encrypted traffic can still carry overly privileged commands if the application design permits them.
A city emergency-alert website is hosted by a contractor. Its content delivery network, DNS provider and authentication service each have different outage histories. The city has a 30-minute recovery target. What should its architecture review prioritize?
Enumerating DNS, identity, CDN and hosting dependencies reveals single points of failure and recovery bottlenecks. The city should test alternate paths and ownership for each service against the 30-minute target. Contractual assurances matter, but only integrated evidence demonstrates whether residents can receive alerts during outages. The recovery exercise should include a failure of each external dependency in turn, including an identity outage that prevents operators from publishing a new alert. Service-level promises alone are not evidence that the full chain meets the public emergency objective.
A hosting SLA may be necessary contractual evidence, but it does not establish the availability of independently operated DNS, identity and content-delivery services. A failure of any dependency can block emergency communication even if compute infrastructure remains up. The city must test end-to-end recovery against the 30-minute objective.
A hosting service can meet its own SLA while separate DNS or identity components prevent alerts from reaching residents. An isolated vendor promise is not an end-to-end recovery guarantee. Dependencies need measurable tests under the city's operational conditions.
Vendor elimination is not always feasible or safer; in-house services can also fail. The city needs an architecture that accounts for supplier boundaries and resilience, possibly through redundant providers. A blanket ban does not establish how the alert service survives faults.
Please check your mailbox for a message from support@examlabs.com and follow the directions.