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 data-center loading entrance faces a straight public access road. The facility must reduce the risk of a vehicle ramming the equipment building while keeping a marked fire lane usable. Which physical protection is most appropriate?
Engineered vehicle barriers block or redirect an approaching vehicle before it reaches critical equipment. Selecting rated bollards and locating them around a verified fire lane addresses both the physical attack and emergency-access requirements. The design should reference site approach geometry and rescue-vehicle clearance rather than using arbitrary decorative posts. Facilities staff should confirm barrier certification and emergency-vehicle turning radius with the appropriate physical security and safety teams.
An automated gate can block vehicle entry under normal conditions, so it appears to mitigate the approach risk. However, placing a locked barrier across the designated fire lane without verified emergency release and apparatus clearance can obstruct first responders. The proposed arrangement conflicts with the explicit emergency route requirement; impact-rated barriers located outside that route address both needs.
Posts can look like crash barriers, but decorative steelwork does not establish a tested level of vehicle-impact resistance. An unanchored or inadequately spaced post may fail under a hostile vehicle load. The data center should require a certified barrier design matched to likely approach conditions, while preserving the approved fire lane and accessible routes.
Speed control and warning signs may reduce accidental driving risk and improve ordinary loading traffic, but they do not reliably stop a deliberate vehicle-ramming attack. The straight approach still exposes critical equipment to impact. Physical barriers with a suitable tested performance rating provide protection even when a driver ignores posted instructions.
A hospital’s records server room uses badge-only access. Security cameras show that an unauthorized visitor sometimes enters directly behind an authorized technician without presenting credentials. Which modification most directly reduces this TAILGATING exposure?
A properly configured access vestibule or mantrap regulates person-by-person entry rather than merely checking the first badge. It addresses the observed gap between the authorized user and the unverified follower. Emergency exits and accessibility requirements must be included so that stronger physical access does not create a life-safety hazard. The hospital should verify that the vestibule cannot be bypassed during normal entries while emergency evacuation remains possible.
Monthly reports can expose anomalies after the unauthorized person has already entered, but they do not stop a follower passing through an open door. Badge-only records may also misrepresent the event as a single authorized entry. The required change is to the entry process itself, not only its subsequent review.
Anti-passback can discourage credential reuse in the wrong entry sequence, but it cannot count people following a legitimately badged technician through an open door. The scenario documents physical tailgating, so a one-person entry mechanism or staffed verification is needed in addition to badge sequence controls.
Stronger workstation authentication can reduce misuse after someone reaches a computer, but it does not stop an unauthorized person entering the server room. The visitor might tamper with equipment or observe sensitive operations without logging into any account. The control must address the physical entry event directly.
A retail distribution center has a camera blind spot in a narrow storeroom corridor. Forklift vibration and moving air create frequent false alarms. Which conclusion about adding MICROWAVE or ULTRASONIC motion sensors is most defensible?
A site trial comparing movement coverage, adjacent-zone leakage and sensitivity to actual forklift operations is the right decision framework. Microwave and ultrasonic sensors use different physical principles, so their practical performance depends on layout and device selection. Testing allows the team to close the camera blind spot without generating an unmanageable number of false alarms. The final alert policy should distinguish genuine intrusion from routine forklift movement using measurable acceptance criteria.
Ultrasonic sensing depends on reflected acoustic energy and the geometry and surfaces of the actual room. Advertised range alone does not prove suitable coverage in a corridor affected by vibration and air movement, so this choice skips the site tests needed to balance intrusion detection against false alarms.
A dual-technology device may reduce some single-sensor false alarms, but factory settings cannot establish reliability for this particular corridor. Moving air, mechanical vibration and nearby forklift movement can change performance after installation. A controlled site trial with intrusion and normal-operations tests is necessary to tune the technology and establish acceptable false-alarm rates.
A longer nominal detection range may increase unwanted coverage outside the intended corridor or respond to movement through certain materials. The security outcome depends on appropriate zone placement and alert quality, not simply advertised distance. The site should assess detection reliability versus false positives.
A warehouse monitors an exterior fence line and a nearby loading platform. Security wants to tell whether motion was detected across the field of view or a person actually stepped onto a particular mat. Which pairing is correct?
Infrared sensing can detect changes associated with motion or thermal patterns within the sensor’s coverage, while a pressure mat responds when weight or force is applied directly to it. The devices therefore provide different spatial evidence: motion in an area versus contact at a defined location. Placement and false-positive testing remain essential. Correlating independent sensor events with timestamps can clarify whether movement in a monitored region led to actual platform contact.
A passive infrared detector observes changing radiation within its coverage and does not measure the applied force or exact contact location on the floor. A pressure mat reacts to weight where it is physically installed, not motion across the whole corridor. This reverses the two forms of evidence the security team needs to distinguish.
Correlated events can improve an investigation, but a motion detector does not identify a human or prove contact with a specific floor location. A PIR alarm could have been generated by someone passing nearby without stepping on the mat. Individual attribution requires separate access credentials or reliable identity evidence, and force sensing requires an actual mat event.
A moving warm body can affect an infrared sensor without touching the platform mat. Even a carefully aligned coverage zone only estimates presence or motion; it does not demonstrate applied pressure on a specified surface. The requested distinction requires independent contact evidence from the pressure mat rather than drawing a force conclusion from radiation measurements.
A hybrid SaaS provider already operates one isolated honeypot server. The security team wants to study an attacker’s movement among several deliberately vulnerable-looking hosts without exposing real tenant workloads. What does a HONEYNET offer beyond the single honeypot?
A honeynet provides multiple connected decoy systems with monitoring, allowing defenders to observe sequences of attempted compromise, pivoting and discovery that one isolated host cannot fully show. The provider must isolate the deception subnet from customer resources and constrain egress to avoid becoming an attack launch point. It is useful research and detection infrastructure. Production-facing traffic should be continuously monitored to confirm that the decoy network remains logically and operationally separate.
A honeynet can help detect or understand an attack but does not automatically block every production lateral movement path. Attackers may never interact with the deception environment. Segmentation, identity enforcement and telemetry controls still protect real workloads; the honeynet adds observation rather than absolute prevention.
Decoy servers do not grant or revoke legitimate customer access. They cannot replace application authorization, federation or privileged-account controls. Treating a deception network as an IAM solution confuses observing malicious behavior with enforcing normal user permissions. A decoy network does not maintain the production account directory or calculate per-user permissions.
Allowing unrestricted outbound traffic from deliberately tempting decoys would create risk to the provider and external parties. A well-designed honeynet uses strong isolation and egress controls so observed attacker behavior does not become a route to compromise production services or third-party systems.
A research lab wants TWO decoys: one should trigger when someone reads a marked confidential-looking file, and the other when a planted API credential is used. Which TWO placements match those goals? Select TWO answers.
A honeyfile is intentionally crafted to appear valuable but serves as a decoy, so reading or copying it can create an alert without exposing real research. The document share must have audit coverage and the file should contain no sensitive production content. This choice is tailored to the requested read-access signal. The lab should verify that an authorized reference test triggers the alert without granting anyone access to real confidential files.
A honeytoken credential is a planted secret that should have no legitimate operational use. An attempted authentication with it is therefore a meaningful indicator of misuse, distinct from merely opening a decoy file. Alerting on token use provides the lab with a separate signal about credential collection or replay. Any token-trigger event should include attempted target, time and source to support investigation without exposing valid credentials.
A warning label may deter or direct legitimate readers, but it cannot by itself report an unauthorized read event. The lab explicitly wants monitored decoy actions, so it needs audited file access and token-use instrumentation rather than signage alone. A warning remains valuable as a supplement, but it cannot report which confidential-looking document was actually opened.
Exposing a real API credential would introduce an actual security vulnerability, not a controlled deception measure. The credential could be reused against the service and harm production data. A honeytoken must be nonproduction or otherwise safely isolated so that its use is detectable without granting sensitive access.
Disabling logging removes the observation mechanism that gives honeypots and honeytokens their value. Without recorded reads and authentication attempts, investigators would not know which decoys were accessed. Lower monitoring overhead does not satisfy the required detection objectives. The researchers would lose both baselines and forensic context needed to distinguish genuine deception hits from errors.
A finance department uses a nightly service to send signed reports. The scheduler runs under a shared human username and password. Which change best distinguishes SERVICE authentication from human authentication?
A dedicated workload identity supports attribution, scoped authorization, rotation and revocation without borrowing an employee’s personal credentials. Certificates or managed workload tokens can authenticate the sending service through a machine-appropriate trust mechanism. Its permissions should be limited to the scheduled reports rather than inheriting broad human-user access. Identity ownership should survive staff turnover, with documented key rotation and a method to disable just the scheduled workload.
A descriptive label and more frequent rotation do not establish an independent non-human identity or separate the scheduled job from individual staff credentials. The service still inherits a shared interactive account, with weak attribution and employee-lifecycle dependencies; it should authenticate as its own narrowly scoped workload.
Manual human login is inappropriate for an unattended nightly process and may cause reports to fail when staff are absent. It also keeps the automation dependent on a person’s lifecycle and permissions. Workload authentication should be managed independently of individual employee accounts.
A nominally separate scheduler identity is useful, but publishing its live secret broadly and omitting rotation undermines the intended workload boundary. The same secret could be reused after staff departures, and activity could be difficult to attribute to controlled service execution. Machine credentials should be narrowly accessible, rotated and revoked under service ownership rather than copied into general documentation.
A branch office has encrypted a customer database, but it performs no integrity checks and has never tested restoration. What does the deployment demonstrate about the CIA triad?
Encryption is primarily a confidentiality measure for the stored records. Integrity may require authenticated encryption, hashes with suitable trust assumptions, signatures or database validation, while availability needs tested backups, redundancy and recovery planning. The missing checks and restore tests are precisely why one deployed control should not be reported as complete CIA coverage. A restore exercise should also verify retained keys and transaction consistency so backups do not merely exist on paper.
Encryption can prevent unauthorized interpretation of stored data when keys and implementation are protected, but ordinary encryption alone does not prove that all records are unaltered or always accessible. Backups can fail or keys can be lost. The other CIA objectives require additional safeguards.
Authenticated encryption may detect unauthorized ciphertext changes, but it cannot guarantee that the database remains available during hardware loss or that the organization can reconstruct files and keys. The scenario explicitly lacks tested recovery, which must be demonstrated independently of the storage encryption mode.
Reading ciphertext says nothing about whether the underlying record remained unchanged. Some encryption mechanisms include authentication, but the scenario specifies no integrity checks. Merely storing ciphertext cannot establish a trustworthy modification history or detect corruption. This is why verified integrity evidence must be separate from storage format or visibility of bytes.
During maintenance, a hospital plans to change an access-control rule shared by clinical and administrative applications. Before deployment, what change-management evidence is most important?
A single controlled record links accountable ownership, affected stakeholders, foreseeable clinical impacts, testing and a backout path. The maintenance window and stakeholder signoff reduce unexpected service disruption when a shared rule changes. These are predeployment safeguards, not paperwork to assemble only after the rule causes a problem. The record should describe measurable business acceptance checks, including successful access by both clinical and administrative applications.
The network owner can authorize a technical implementation within their role, but the rule also protects clinical workflows. The team needs impacted stakeholder approval and business-service dependency checks before changing shared access. A ticket signed only by the implementer may not reveal clinical patient-care risks or the need to reverse the rule if essential application traffic fails.
A successful ping can show limited connectivity after the edit, but not that authenticated clinical and administrative application transactions work. It also does not demonstrate a usable rollback. A change touching both services needs a tested backout and acceptance criteria tied to real workflows, not one low-level network signal obtained after the change.
Similarity of addresses does not prove that the applications, maintenance window or business risk are unchanged. New dependencies or clinical schedules can alter the consequences of a shared rule. The current proposal still needs named ownership, relevant stakeholders, a documented impact assessment and a recoverable backout path before production changes.
A retailer is rolling out a new endpoint security agent to 600 franchise terminals. A pilot shows that one model repeatedly loses access to payment readers after installation. What should be a defined BACKOUT criterion?
The pilot provides a repeatable acceptance failure for a business-critical payment peripheral. A predefined backout can halt wider deployment and restore the last known-good agent state for affected terminals, followed by verification that payments work. This is a concrete, test-driven rollback trigger. The team should preserve the exact failing reader model and transaction logs for the vendor before attempting another staged rollout.
A fleet-wide percentage threshold is too late for a pilot that already demonstrates loss of a payment-critical function on a known device model. A suitable backout criterion should stop expansion on the measured acceptance failure before introducing unnecessary checkout outages across additional franchises.
Staged rollout to proven-compatible models may be a defensible separate plan, but the scenario asks for the actual backout threshold on the model that already fails payment-reader acceptance. Leaving those terminals in a known-bad state until a monthly review extends a critical sales outage. The immediate criterion should trigger recovery to a last-known-good configuration for affected pilot devices.
An approved temporary exception can be appropriate when it maintains safe function, but hiding the specific alert does not restore the payment reader. It may make rollout dashboards appear healthy while transactions fail. The pilot should fail acceptance and back out affected installs; only after a vendor fix is tested should the team retry the rollout.
A logistics warehouse has a small maintenance window. A new authentication gateway requires a service restart, while warehouse scanners cannot be offline during active shipping. Which TWO actions best manage the change? Select TWO answers.
Mapping scanner dependencies makes the operational impact visible before a shared authentication service is restarted. Using a verified low-activity window and owner approval reduces disruption while retaining the ability to serve legitimate warehouse access. A calendar time without actual dependency analysis would not be enough. Operations should verify actual scanner traffic patterns and shipping cutoffs, rather than guessing that midnight is a universally safe window.
A recoverable prechange configuration and tested rollback allow the team to undo a gateway change when scanners cannot authenticate. Monitoring immediately after restart checks that the critical workflow actually functions, rather than equating service startup with successful business operations. These steps complement scheduling and stakeholder coordination. Post-change acceptance should include a real scanner login and transaction, not just a green service-status indicator.
General vendor release notes cannot establish how this warehouse’s scanners depend on the authentication gateway. Even a technically sound upgrade can interrupt a local integration or running shipping shift. The team should verify dependency traffic, obtain operational approval and choose a window based on actual scanning activity rather than the vendor’s generic confidence.
A saved configuration is useful, yet a failed restart may also involve service state, credentials and dependent scanner behavior. Untested rollback may not recover business operation under time pressure. The warehouse needs a practical, verified backout procedure and post-change authentication checks, not merely a stored configuration file.
A low-activity window helps with availability, but the change can still break scanner authentication after the gateway service appears healthy. Without notification, acceptance checks and an accountable owner, failures may be discovered only during shipping. The two correct answers combine dependency-aware scheduling with tested rollback and operational monitoring.
Please check your mailbox for a message from support@examlabs.com and follow the directions.