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 military contractor classifies files under centrally controlled secrecy labels. Individual file owners cannot override the label hierarchy. Which model is best illustrated?
MAC uses centrally defined labels and authorization relationships that users cannot arbitrarily change. That fits the contractor's classified files and controlled access rules. Administrators should validate label assignment and effective clearance, not rely on informal sharing practices. Under MAC, labels and policy determine access regardless of a data owner's discretionary preference to share the file.
Discretionary access control permits an owner to exercise sharing authority, which conflicts with the stipulated central secrecy hierarchy that owners cannot override. A trustworthy recipient or familiar colleague is not automatically cleared for the file's label. The contractor requires system-enforced classification relationships rather than decisions based solely on the owner's preference.
Department-based roles may reduce excessive access but do not capture the mandatory comparison between centrally assigned file labels and approved clearance or compartments. An employee in the same department can still lack authorization for highly restricted material. The model described is centrally enforced label-based policy, not a department membership check alone.
Attribute-based decisions can enforce security when attributes are trustworthy, but a requester-controlled clearance claim would undermine the central label hierarchy. The contractor explicitly denies owners and ordinary users authority to alter the enforced classification relationship. MAC requires appropriately assigned, protected subject and object labels under a system policy, not self-attested elevation.
A hospital restricts routine maintenance accounts to weekday evenings, but emergency clinicians may need a separate break-glass path at any hour. Which design is most appropriate?
Conditional access can enforce authorized time windows for routine administration, reducing standing exposure. Emergency care needs a distinct tightly scoped path with activation evidence and review. Keeping the two roles separate preserves both operational availability and accountability. Test the exception process during a genuine out-of-hours incident and ensure break-glass events receive retrospective review.
After-action approval can provide an audit record but does not enforce the defined weekday evening maintenance window. Leaving standing administrator privileges active for all on-call staff expands exposure far beyond emergency care needs. A separate, time-limited break-glass process can provide emergency access without weakening normal maintenance-role restrictions.
An emergency clinician may need access outside the routine engineering schedule. Reusing the restricted maintenance window could delay life-critical treatment until an ordinary change-approval process runs. The hospital should engineer an explicitly authorized, auditable emergency workflow instead of forcing clinical break-glass requests through a technician scheduling rule.
Verifying the person helps, but an unrestricted role with no event evidence lacks safeguards against misuse of sensitive clinical records. Logging and scoped emergency authorization can be designed to avoid excessive delay, while retaining the ability to investigate unusual access later. Strong identity proof alone does not replace accountable activation and retrospective review.
A finance system requires phishing-resistant authentication for remote administrators. Staff currently enter a password and SMS code at an ordinary webpage. Which upgrade most directly reduces adversary-in-the-middle phishing?
WebAuthn/FIDO2 credentials are cryptographically bound to the legitimate relying party origin when implemented correctly, resisting many phishing proxy attacks. The finance team should test enrollment, recovery and administrator device lifecycle. A security key still needs appropriate access authorization after authentication. Origin binding and possession of a hardware authenticator reduce exposure to credential relay through a lookalike login page. Disable phishable legacy fallback routes for privileged access or the attacker can simply choose the weaker method instead.
A push prompt can be convenient and may improve some authentication properties, but a phished password or adversary-in-the-middle session can still induce the victim to approve an attacker’s login. Push fatigue and ambiguous prompts create additional risk. Origin-bound FIDO2 authentication ties the cryptographic response to the relying party, directly addressing credential relay.
Certificate authentication can help verify managed devices, but the unrestricted phishable fallback leaves the privileged portal vulnerable to the same password-and-OTP relay it had before. Attackers can deliberately choose the weaker authentication path. A phishing-resistant upgrade must protect every allowed privileged sign-in path, including recovery and alternate devices.
Time-based authenticator codes can improve some threats compared with SMS, but a reverse-proxy phishing site can still relay the entered code and seize a live session. The requirement is phishing resistance against adversary-in-the-middle attacks. Origin-bound FIDO2/passkey authentication binds the response to the legitimate relying-party origin instead.
A biometric gate accepts fingerprints for clinical staff. Its fallback process gives anyone a shared PIN when fingerprint capture fails. Which risk is most relevant to recovery design?
An individually managed recovery token or supervised identity proofing can restore access while retaining accountability. The hospital should limit exceptions, record their use and re-enroll affected users. This balances emergency availability with the intended identity assurance. A reset should require another validated factor or accountable human review before a new authenticator replaces the lost one.
A log tied only to a common PIN cannot reliably identify which clinician entered the area. False rejects warrant a safe recovery workflow, but that workflow must establish individual identity and record who approved it. Shared secrets defeat the accountability the biometric gate was meant to provide.
A supervisor check may add oversight, but a static shared PIN still makes the access event hard to attribute to one person. A safer fallback can issue individually tracked credentials after identity verification with expiry and audit records. Approval should not be confused with cryptographic attribution.
Help-desk recovery can be a legitimate fallback if it verifies identity and records approvals, but a reusable shared code tied only to an easily obtained employee number undermines accountability. A biometric false reject should lead to a controlled alternate authentication path, not a transferable PIN anyone can request.
A company redesigns password policy after employees complain that mandatory monthly changes cause sticky-note reuse. Which policy should it evaluate in line with modern risk controls?
The policy should prioritize hard-to-guess secrets and block known compromised or common values while supporting password-manager use and usable account recovery. NIST SP 800-63B-4 specifies a minimum of 15 characters for single-factor passwords and at least eight for passwords used only as part of multifactor authentication. It prohibits arbitrary periodic password changes and requires changes on evidence of compromise; any organization-specific exception must be explained against the applicable requirements. This directly reduces the sticky-note and predictable-reset behavior described by employees.
NIST SP 800-63B-4 requires at least fifteen characters for single-factor passwords and rejects mandatory composition rules as the default defense. Eight characters can be acceptable for passwords used only within a multifactor authentication process under its conditions, but the option explicitly applies to single-factor accounts. Compromised-password screening remains important.
Predictable edits to known breached passwords can remain susceptible to guessing, and a punctuation requirement is not a substitute for checking the resulting value against a blocklist. The organization should screen entire proposed passwords and require replacement when they are known compromised, rather than assuming one added character restores secrecy.
Frequent arbitrary resets can encourage predictable changes and unsafe storage without addressing passwords already revealed in breaches. Under current NIST verifier guidance, routine periodic changes are prohibited absent evidence of compromise, and known compromised values must be rejected. This choice combines the least useful parts of rotation with weaker password screening.
A company introduces passkeys but still has legacy applications with password accounts. Staff use a password manager whose emergency recovery secrets are stored in an unapproved team chat. What should the migration plan address?
Passwordless migration is gradual; residual secrets and recovery paths remain security-sensitive. Centralized vault recovery should use restricted custodians, strong authentication and a tested process. The company should also inventory legacy accounts so they are not silently left with unmanaged passwords. Migration should verify that each legacy account has a safe fallback before the organization removes the corresponding password-authentication path.
Passkeys can reduce phishing risk for supported services but do not retroactively replace passwords used by legacy applications. An unapproved chat may expose recovery material that unlocks many accounts. The migration needs secure custody, identity-proofed recovery and staged deprovisioning of old login paths rather than leaving shared secrets openly accessible.
Disabling recovery may remove one abuse path but can strand legitimate users and create pressure for informal administrative bypasses. A controlled process can verify identity and restore access with strong safeguards and logging. The scenario asks how to migrate while retaining secure operational access, not how to make recoverability impossible.
A shared authenticator cannot reliably attribute access to a particular employee and creates a common account-takeover target. Passkey enrollment should bind credentials to the intended user and relying party. The organization also still needs to protect the separate recovery secrets that remain in its legacy password-manager workflow.
A data-center administrator needs production database privileges only during an approved incident. The current shared root password is stored in a team wiki. Which privileged access design is better?
PAM can constrain who obtains privileged authority, when and for how long, while recording session activity. Short-lived grants reduce standing exposure and make incident access traceable. The data-center team should test emergency access and revocation after an incident closes. Vault checkout and session records should allow investigators to link a privileged action to one approved operator and permitted maintenance window. The vault should revoke elevation promptly at incident closure and retain recordings or audit identifiers sufficient to trace what the administrator actually changed.
Encrypting the wiki improves storage protection but leaves a broadly readable standing root secret that can be copied and reused outside an approved incident. Approval comments do not establish attribution of every privileged session or revoke access when the incident ends. A privileged-access vault should issue bounded grants and maintain individually attributable checkout or session records.
Frequent rotation reduces the period during which an old value remains usable, but distributing one current root password preserves shared-account anonymity and broad exposure. A copied secret can still be reused by anyone in the channel. The requirement is incident-specific privileged access with identity attribution, limited duration and controlled checkout, not merely a new shared secret.
Individual identities improve attribution compared with a shared root password, but permanent elevated privileges create unnecessary exposure between incidents. A compromised on-call account could administer production when no authorized response is underway. Just-in-time elevation and scoped session duration meet the stated episodic need while preserving accountability through the vault.
A new contractor joins an IT operations team. An automated workflow grants repository access but sometimes fails to revoke access when the contract ends. Which automation design best addresses both lifecycle events?
Identity lifecycle automation should be triggered by trustworthy source events and independently verify that target permissions changed. Sponsors define the legitimate scope, while exception alerts catch failed tasks. This reduces stale access without relying entirely on silent scheduled scripts. The system should record when a sponsor's approval expires and verify that downstream repository permissions were actually withdrawn.
Automatic provisioning solves only half of the lifecycle problem. The scenario already documents missed terminations, so another manual reminder without authoritative end dates and verification can leave access active. A robust automation workflow needs a reliable termination event, proof of revocation and alerting when the expected action fails.
Timed revocation is helpful, but the organization needs attribution for when access was granted, altered and removed. Removing the records would conceal unauthorized privilege changes and make reconciliation impossible. A dependable lifecycle workflow both enforces the action and preserves evidence of its completion and any exceptions.
Periodic attestation is a useful detective complement, but it should not replace prompt deprovisioning when an authoritative termination event exists. Leaving credentials valid for weeks increases the exposure window. The automation must trigger revocation when the relationship ends and report failures for follow-up.
A hospital automates disabling a vulnerable laboratory service when an exploit alert reaches high confidence. The service may also support a clinical device. Which automation is safest?
Automated containment can reduce attack dwell time but must consider clinical dependencies. Conditional triggers, service inventory, guarded actions and rollback can prevent unnecessary patient impact. The hospital should rehearse representative alerts and verify both security effect and business continuity. Before disabling a dependent service, the automation must verify that the trigger matches the allowed containment policy and rollback criteria.
A shared service name does not establish that every instance is independently safe to disable. Clinical devices may rely on one location or protocol path, and blanket shutdown could interrupt treatment. Even high-confidence exploitation evidence should trigger a tested, scoped containment workflow that checks dependencies and coordinates with responsible clinicians before broad disablement.
Broad standing administrative privileges turn the orchestration system into a dangerous shared control point if its token or playbook is compromised. Logging may help detect abuse afterward but does not constrain the actions possible with the credential. The workflow needs narrowly scoped permissions, approved triggers, protection of secrets and validated rollback for clinical dependencies.
Automation can respond quickly but also creates outage risk when a shared clinical dependency is involved. A safe workflow evaluates event confidence, process safety, approved fallback paths and recovery steps before taking a high-impact action instead of treating every early alert as a verified exploit.
An endpoint rule sends an incident ticket whenever the same malware hash is observed. A widespread detection event creates 2,000 identical tickets in ten minutes. Which automation change best reduces duplication without losing scope?
A stable deduplication key and aggregation window can group related events without discarding device-level evidence. The SOC can prioritize the incident and track remediation for each host. Escalation should still occur when a new high-risk behavior emerges. The record should preserve each host's evidence and chronology while preventing hundreds of near-identical tickets from overwhelming responders.
Suppressing all events can hide real infections and spread. The goal is reducing ticket duplication while preserving the ability to track impacted assets. Incident scope should remain visible. Waiting for malicious events to disappear leaves compromised endpoints active; deduplication should improve triage rather than suppress detection.
Device identifiers are essential for assigning containment and verifying recovery. Removing them would make even a single consolidated ticket less actionable. Deduplication should retain source context. Removing affected device identifiers prevents responders from deciding which assets need investigation or containment.
Historical incidents help detect recurrence and prove closure. Deleting them would weaken trend analysis and investigations. Ticket noise should be addressed through correlation rather than evidence destruction. Prior history can show recurring infections and failed remediation; erasing it destroys useful evidence about patterns and ownership.
A SOC automation rule sees a low-severity antivirus alert and a confirmed privileged login from an unknown device within one minute. Which escalation design is best?
Correlation provides a stronger case for timely response than either event alone. A human can validate the host, account and timing before disruptive steps. The ticket should include evidence links, severity rationale and proposed containment boundaries. The escalation record should explain which corroborated events raised the confidence level so the responder can challenge the alert if needed.
One uncertain endpoint signal may not warrant immediate isolation, but its proximity to a privileged login from an unknown device changes the combined risk. Correlation can reveal account misuse that neither event proves on its own. The SOC should examine device identity and timing and route the enriched case to a responder rather than suppress cross-signal investigation.
The combined event deserves timely triage, but automatic mass account shutdown based on one identity’s suspicious activity would disrupt unrelated users. A better escalation sends corroborated context and a prioritized investigation to an authorized responder before taking broad high-impact action.
Successful authentication supports that some factors were accepted, not that the device or session is safe. A stolen session, compromised endpoint or coerced factor can coincide with unusual host behavior. The automation should retain both observations and escalate the combined context for human validation, rather than allow authentication success to override other threat indicators.
Please check your mailbox for a message from support@examlabs.com and follow the directions.