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 hospital's server fleet was deployed from a hardened image, but later administrators manually changed services and firewall rules. A quarterly report shows several servers drifted from the approved build. What is the appropriate control?
A baseline must be measured against actual deployed state to detect unreviewed deviations. Configuration monitoring and controlled exceptions can distinguish justified local needs from unsafe drift. The hospital should validate correction plans with clinical owners so restoration of policy does not disrupt essential services. The drift report should identify whether a difference came from an authorized emergency change or an unexplained change before remediation is applied.
An automatically accepted current configuration can incorporate unsafe or unauthorized changes into the control standard. The baseline is supposed to express a reviewed required state, not mirror all observed drift. Each deviation needs impact assessment and either remediation or a documented, approved exception after operational testing.
Initial image compliance does not guarantee the fleet remains hardened after manual configuration changes. The scenario already reports live-server drift. Continuous or periodic comparison against a maintained baseline should detect changes throughout the server lifecycle, not just certify the image used at deployment.
Configuration enforcement can prevent drift, but a blanket rollback without dependency checks could interrupt important patient-care workflows. Some legitimate emergency changes may need temporary approval. A safe program assesses the specific variance and remediates through controlled change management while retaining evidence for exceptions.
A clinic allows staff-owned phones to receive emergency care notifications. Some devices are lost, yet emergency communication must continue. Which mobile-device management design best balances these needs?
MDM or suitable application management can enforce security posture, manage enrollment and protect organizational data on lost devices. Selective wipe and time-bounded emergency processes reduce risk without unnecessary personal-data destruction. The clinic should test that clinicians still receive urgent alerts during device replacement and identity outages.
An unmanaged application may keep sending notifications, but lost devices could retain sensitive patient information with no selective removal or oversight. The clinic should minimize protected data on endpoints and use a managed application container or equivalent safeguards. Emergency availability and confidentiality are both requirements, not alternatives where one can be ignored.
Full-device wipe can be disproportionate for personally owned devices and may deter enrollment, while an exclusive phone channel leaves emergency communications vulnerable to device loss. A documented BYOD design should prefer selective work-data protection when feasible and an alternate clinical access path during disruptions.
A known wireless network might simplify some access policies but could prevent clinicians from receiving critical alerts outside the building. The clinic specifically needs continuity when personal devices are unavailable or lost. Managed emergency access, selective remote wipe and fallback communication are more appropriate than replacing a confidentiality concern with an availability outage.
A university laboratory uses managed network switches. Administrators currently allow Telnet from every campus subnet and leave unused switch ports enabled. Which hardening set is most appropriate?
Encrypted management, narrow source access and unused-port controls reduce exposed switch functionality. The lab should preserve legitimate monitoring and verify that remote support still works through an approved path. Hardening should follow a maintained configuration baseline rather than ad hoc technician preference. Administrative reachability should be tested from the authorized jump network and a normal user subnet to prove both acceptance and isolation.
SSH can encrypt administrator sessions and remove Telnet’s plaintext exposure, but it does not address unnecessary reachability or unused access paths. Any compromised campus endpoint could still interact with switch management. The university needs a restricted administrative network and controls on unused ports alongside secure management protocols.
A vault improves password custody and accountability, but Telnet still transmits session data without the protection of an authenticated encrypted management protocol. Broad campus access compounds that weakness. The university should replace the insecure service, restrict trusted management origins and protect unused switch ports rather than treating vault usage as transport security.
Port lockdown reduces some physical attachment risk, but weak community credentials and plaintext Telnet leave the management plane susceptible to interception and misuse. The goal is comprehensive reduction of reachable management services, with authenticated encrypted administration and narrow source access. One sound control cannot compensate for leaving other high-risk management paths open.
A regional router must send monitoring data to a network management station while rejecting administrator sessions from ordinary user VLANs. Which policy best separates the functions?
A protected management path and explicit telemetry destination limit the control plane without losing essential health data. The team should verify protocol security, access lists and log integrity. This allows normal routing and monitoring while preventing unauthorized configuration attempts from user networks. The router should continue exporting required telemetry to the monitoring destination even though ordinary users cannot reach its administration interface.
User VLAN reachability is not justified by the existence of telemetry flows. Router administration is privileged and should be narrowly restricted. Broad access increases password attacks and exploitation opportunities from ordinary endpoints.
Removing monitoring can conceal outages and unauthorized configuration changes. The objective is separating who may administer the router from which telemetry can leave it. Properly designed observation does not require opening every management interface.
Shared broad credentials undermine least privilege and make event attribution difficult. Monitoring systems may need read-only access but not configuration authority. The router should have distinct identities and roles for each operational function.
A cloud team deploys a new application with one service account that can read secrets, change network rules and delete all storage snapshots. The service only needs to read two private objects. What hardening action is most appropriate?
A dedicated identity restricted to required object reads limits potential compromise impact. Network and snapshot administration should be separate, audited roles with stronger approval. The cloud team should test application functionality under the narrow grants and monitor attempts to use disallowed APIs. The new identity should be denied access to unrelated secrets and resources, and cloud audit logs should confirm the scoped role is used.
Duplicating excessive permissions across people increases the chance of misuse and makes ownership unclear. Developer convenience does not explain why a read-only application would need snapshot deletion. Roles should follow actual tasks rather than inherited blanket rights.
Exposing a privileged secret in startup code risks leakage through artifacts, logs or host compromise. It does not reduce the underlying role's excessive authority. Managed identities and secret lifecycle controls are a safer design.
Auditing can identify misuse after it occurs, but leaving unnecessary destructive privileges in place preserves the blast radius of a compromised workload identity. The application requires access to only two objects, so permissions must be reduced rather than treating event collection as a substitute for least privilege.
A chemical-processing line has an aging PLC whose firmware patch requires rebooting a safety-related controller. The vendor confirms a vulnerable service, but shutdown is not permitted during production. Which plan is safest?
Temporary isolation can reduce reachable attack surface until a controlled firmware change is feasible. OT engineers should verify functional dependencies and monitoring, then execute a tested maintenance plan with rollback or contingency where supported. The patch should be confirmed through post-change safety and security acceptance. Until the safe window, the plant should confirm segmentation actually blocks the vulnerable management service from untrusted sources and that emergency operator functions still work. After patching, compare controller behavior with safety acceptance criteria as well as software version.
A valid vendor signature helps establish update provenance but does not establish that a restart is safe during a live chemical process. Even an authentic firmware patch may reset communication or alter controller behavior. Process-safety engineers must test reboot effects, arrange approved protective conditions and schedule deployment during a verified maintenance window.
An unavailable patch window does not mean exposure must remain unrestricted. Narrow network paths and compensating safeguards can reduce risk while scheduling a safe update. Leaving all access open would increase attack opportunity during the delay.
An operator shift change is not necessarily a safe maintenance window for a running chemical process. Controller reboot impact, safety interlocks and recovery steps require plant-specific testing and coordinated shutdown approval; a convenient calendar interval cannot replace those constraints.
A factory mixes tiny embedded environmental sensors with more capable industrial IoT gateways. A proposed security agent consumes more memory than the smallest sensors have. What is the best hardening strategy?
Constrained sensors may require different controls from gateways capable of hosting endpoint agents. Secure boot or firmware verification, segmentation and inventory can provide protection without exhausting resources. The factory should test that monitoring and necessary sensor readings remain available under real operating conditions. A sensor without normal patch capabilities should be segmented and have a planned replacement path rather than simply inherit a workstation baseline.
An agent that cannot fit or meet timing constraints may break environmental monitoring or cause instability. A uniform policy should not ignore hardware limits. Equivalent security outcomes can require different technical mechanisms across device types.
Network segmentation is valuable when tiny devices cannot host a security agent, but it is only one layer. Unverified firmware updates and unused exposed management ports can still provide an attack route from permitted systems or during maintenance. The factory needs a device-specific baseline with supported patching, authentication and management restrictions alongside tested network isolation.
Removing features may reduce an agent footprint, but the devices have stated resource limits that can make even a reduced build unsafe or unstable. Hardening should use supported firmware assurance, network restrictions and gateway visibility unless a sensor-specific control is validated in a representative device.
A campus Wi-Fi deployment has complaints about connectivity in stairwells. The network team wants evidence about signal coverage and channel interference rather than guessing from user reports. What should it perform?
Site surveys produce evidence about RF propagation, dead zones, interference and roaming. Those observations support targeted access-point and channel changes while preserving secure authentication. The campus should retest stairwell routes with representative client devices after adjusting the design. A useful survey should include the weakest client models and their real application traffic, not just a phone's strong received-signal display.
Radio propagation varies with walls, stair geometry, client position and interference. A strong beacon near the access point does not establish usable coverage where people report trouble. A site survey must sample the affected location and observe signal quality, channel utilization and roaming, not infer performance from a convenient measurement point.
Higher power can improve some downlink measurements but may increase interference, asymmetry with client transmit power and poor roaming choices. RSSI alone does not characterize congestion or data quality. The campus should first measure noise, channel overlap and real client behavior before deciding which radio settings to change.
A channel plan may be a reasonable starting hypothesis, but its effectiveness depends on the surrounding RF environment and client behavior. Without a real survey, the team could leave co-channel interference or roaming gaps unresolved. Measurements should determine whether channel changes address the observed stairwell problem.
An emergency medical transport team pairs tablets with Bluetooth patient sensors, uses station Wi-Fi and relies on cellular fallback during transit. Which THREE controls support secure, available connectivity? Select THREE answers.
A managed cellular route maintains telemetry when station Wi-Fi is unavailable. Security policy must preserve authentication and data protection across network transitions, and device-management controls remain in effect. Handover testing should examine missed sensor messages and recovery, not only signal strength. Fallback tests should measure both reconnection time and the confidentiality of transmitted telemetry when the primary Wi-Fi network becomes unavailable.
Trusted Wi-Fi profiles and authentication help prevent association with rogue networks near stations. The configuration should define certificate validation and approved SSIDs where supported. Testing on actual tablets verifies that secure connectivity does not disrupt patient monitoring. The team should confirm that roaming between stations does not silently drop the device into a weaker security profile or unapproved network.
Restricting pairing limits impostor sensor connections and unauthorized local radio access. Approved device identities, pairing confirmation and logs help identify suspicious attempts. The team should verify that emergency replacement sensors can be enrolled through a controlled process without requiring indiscriminate pairing. Pairing controls should reject unexpected devices and retain a way to replace an authorized medical sensor without indefinite trust in its original identifier.
Some medical peripherals have limited user interfaces and may need special pairing accommodations, but choosing unauthenticated pairing for devices that can support stronger verification widens the impersonation risk. Bluetooth link encryption alone does not always prove the intended sensor was enrolled. Emergency replacements should use a controlled identity check and documented exception rather than blanket acceptance.
An SSID is a network name and can be impersonated by a rogue nearby access point. Omitting server identity validation in enterprise Wi-Fi onboarding can enable credential interception or a misleading association, even when the device is enrolled. Approved profiles should authenticate the expected network infrastructure rather than relying on the visible SSID string.
Availability is critical for emergency telemetry, but silently downgrading to plaintext can reveal patient data and allow on-path modification or impersonation. A failed secure connection should trigger bounded retry, secure queuing or an approved alternative protocol. Mobile fallback must preserve confidentiality and integrity as well as the ability to send urgent observations.
A company permits BYOD phones for customer support. An employee asks whether the organization must read all personal photos to protect business chat data. Which policy best balances privacy and security?
Containerization or managed-app policies can protect business content and selective wipe while respecting employee privacy. Clear consent, supported operating-system features and an exception process help maintain trust. The company should test work-data separation during device loss and employee departure. The corporate app should prevent unmanaged sharing and allow business data removal without wiping unrelated private family files.
Company data protection does not automatically justify inspecting personal media and unrelated applications on employee-owned devices. Broad data collection increases privacy exposure and may be disproportionate when a managed work profile can restrict corporate data, selectively erase work content and enforce account policies. The employer should use only permissions needed for the stated business risk and disclose them clearly.
Transport encryption protects supported network connections, but it does not stop an authorized app from exporting customer messages into an unmanaged personal storage or chat application. The BYOD policy needs a boundary around corporate data after it reaches the phone. Scoped application controls and selective wipe protect the work dataset without requiring access to employees' private photos.
Broad device-management authority may simplify whole-device control but conflicts with the stated BYOD privacy goal. Managed applications or work profiles can protect employer data and allow selective removal without granting routine access to banking, photo or other personal material.
A firm offers company-owned, personally enabled phones and a choose-your-own-device program limited to three approved models. What distinguishes COPE from CYOD for management planning?
COPE describes ownership and personal-use allowance, while CYOD describes a constrained selection model. Exact ownership under a CYOD program depends on the employer's policy. Security should document enrollment, support and data-wipe expectations for the chosen arrangement rather than infer them from acronyms alone. The procurement and management rules should define who owns the hardware and which personal activities are permitted before users enroll devices.
CYOD describes a selection model and does not independently define legal ownership or privacy terms. Some organizations provide devices, while others permit employee purchase under policy. Data collection and management scope must follow the actual enrollment contract and employment or privacy obligations, not an acronym assumption.
CYOD describes selection from approved models; it does not by itself prescribe who owns the device. COPE refers to a company-owned device with permitted personal use, so equating both with employee ownership loses the distinct administrative and privacy responsibilities the business must define.
A common management technology may support both programs, but ownership, personal privacy and separation of work data can differ. The firm should set enrollment, wipe and support boundaries based on its actual policy. Treating the acronyms as identical can expose personal content or leave corporate data unmanaged.
Please check your mailbox for a message from support@examlabs.com and follow the directions.