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
During a compliance review, a cloud operator describes a nightly backup restoration as a 'preventive access-control' safeguard. The reviewer wants the control inventory to reflect what the safeguard actually does. What is the most accurate classification?
Restoration is designed to recover data and service availability after an incident, so it belongs primarily to corrective or recovery safeguards. Backups can reduce consequences but do not directly decide whether a user may access a cloud resource. The inventory should not mistake resilience capability for a preventive access-control mechanism. A successful restoration test should be documented as recovery assurance rather than a false statement that unauthorized access has been blocked.
A restore test can provide valuable evidence about backup health, which is a detection or assurance benefit. The core function of restoring backup data, however, is returning a damaged or unavailable service to operation. It does not detect and reject unauthorized access in real time.
Approval of a backup policy is managerial, but the operative technical activity has a different purpose. The inventory must distinguish governance ownership from control effects. Calling every approved safeguard managerial would conceal whether the measure prevents, detects or corrects a technical failure.
Effective recoverability may influence attacker expectations, but deterrence is not the primary design mechanism of a backup restore. It does not display a warning or make an attacker stop immediately; it helps the organization repair effects when availability or integrity has already been compromised.
A hospital uses break-glass emergency access to patient charts during an identity-provider outage. Which configuration best balances the confidentiality and availability needs without making the emergency account permanently unrestricted?
A scoped break-glass role restores medically necessary availability when the normal identity path fails, while activation records and auditing keep confidentiality risks visible. Time limits, least privilege and post-incident review discourage inappropriate use. The design explicitly addresses both CIA properties instead of optimizing only one at the expense of patient care. After service restoration, the hospital should reconcile break-glass events against actual patient-care emergencies and close exceptional access.
A continuously available shared identity with no logging removes attribution and makes misuse difficult to detect. It favors convenience over confidentiality and cannot demonstrate why an emergency chart was accessed. The problem requires time-bounded access and accountability even when normal identity infrastructure is degraded.
Blocking all emergency chart access may preserve confidentiality, but it can prevent clinicians from obtaining information needed for urgent care. That is an unacceptable availability loss in this scenario. An emergency mechanism should be narrowly designed and controlled rather than treating all downtime as a reason to deny clinical access.
An alert does not establish that every employee needs every patient record. Blanket privileges widen the exposed information set and could continue after the emergency. Appropriate break-glass access must be tied to specific roles, logged activation and an actual availability event, not an arbitrary monitoring signal.
A retailer receives inventory files from disconnected franchise systems and needs to detect accidental or malicious alteration between export and import. Which mechanism provides the strongest evidence of content integrity and sender authenticity?
A signature binds a digest of the transferred content to a private key and can be verified against the corresponding trusted public key. A changed file causes signature verification to fail, and certificate or key validation supports the claimed sender identity. The receiver must still protect the trusted key material and reject verification failures. The receiver must validate both the file digest and the signer trust chain, not simply accept any signature field in a transferred file.
Encryption protects readability against observers but is not automatically proof that contents were unmodified or who generated them. Some authenticated encryption modes add integrity, but the option explicitly omits validation. Under the stated export/import workflow, a verifiable signature addresses both the modification and sender-authenticity requirements.
File names and timestamps can be altered without changing file content and are not a cryptographic integrity check. An attacker or faulty automation could preserve the expected naming convention while replacing records. Such metadata may aid operational tracing but cannot establish that bytes match an authentic sender-approved export.
Compression mainly reduces file size and may include error checks for accidental corruption. It is not a sender authentication mechanism and is not designed to prevent intentional replacement by an adversary. A valid archive can still contain altered inventory records; content signatures are the relevant security evidence.
An unattended warehouse terminal is used by different employees. An audit event says 'employee ID 217 was permitted to change pallet routing' but does not show how the user proved identity. Which AAA step is missing from that evidence?
Authentication verifies a claimed identity through an accepted factor or mechanism. A username or employee identifier is an assertion, not proof by itself. The investigator needs evidence such as successful credential verification, badge/PIN control, or another authenticated session before treating employee 217 as the real operator. The warehouse should correlate the operator badge or multifactor result with the session that actually performed the routing change.
Authorization determines what an identified principal is permitted to do. The log explicitly says routing changes were permitted, which is evidence about a permission decision. What is missing is the proof that the operator presenting the identity was genuinely that employee.
Accounting means recording attributable activities for audit or billing. The event itself is an accounting record, albeit potentially incomplete. The scenario asks what cannot be established about identity proof before the routing change, so logging alone cannot resolve that missing element.
Availability is part of the CIA model, not one of the three AAA functions. The event does not describe a service outage or access continuity requirement. Confusing AAA with CIA would miss the evidentiary distinction between identifying an account and authenticating the human using it.
Two administrators share a service console. A customer later disputes whether a privileged settings change was approved and executed by a particular administrator. Which TWO records are most important for NON-REPUDIATION? Select TWO answers.
Authenticated, tamper-evident events with trustworthy times tie the execution to an individual session and a specific configuration change. Combining those records with signed approval evidence separates who authorized work from who performed it. A plain mutable log or an unverified timestamp would provide weaker protection against later denial. Clock synchronization and protected log retention make the execution evidence more credible when the disputed change is reconstructed later.
An individually attributable digital signature provides stronger evidence that the named approver endorsed the specific change record. The signature must be verified using a trustworthy key relationship and an intact document, because any signature is only as reliable as its key ownership. This directly addresses the later dispute about authorization. Approvers should retain control of signing credentials so a shared account cannot sign on behalf of an absent manager.
An unsigned screenshot shows a later system state without proving when, by whom, or under whose authority the setting changed. It may help compare configurations, but it is easy to detach from the actual decision and execution sequence at issue in the dispute.
A shared administrator username does not distinguish which individual carried out an action. It may show that the account was used, but its attribution is ambiguous if multiple people know the credentials. Non-repudiation requires stronger identity binding and integrity evidence than a common account name alone.
A roster can indicate who might have had access to the console, but it does not show who approved or performed this particular change. Presence on a team is circumstantial information, not an attributable signed authorization or protected execution trail.
A university research lab reports that its policy requires quarterly access reviews, but the last two quarters show no completed review records. What should the gap analysis primarily conclude?
Gap analysis explicitly compares the required state, quarterly access reviews, against actual practice, where two periods lack evidence. Identifying the responsible owner, missed periods and completion checks enables practical remediation. The policy is the baseline; the missing reviews are a control-performance gap requiring action and measurable follow-up. The lab should record the corrective review completion dates and sample whether excessive research privileges were actually removed.
The scenario already states that a review policy exists, so the missing element is not the initial policy itself. Rewriting the document without making reviews happen would leave the same control gap. The assessment should compare desired operating state against the observed evidence of execution.
There is no evidence that periodic access attestation has become obsolete. An existing policy that is not followed can increase residual risk, especially for confidential research datasets. Declaring the control unnecessary merely because records are absent confuses failure to perform a requirement with evidence that the requirement is invalid.
Recommunicating an existing policy can increase awareness, but it does not supply the missing evidence that quarterly reviews actually occurred. The gap concerns observable execution; the lab needs a catch-up attestation, accountable owners, review records and a sustained process rather than an unsupported assumption of compliance.
In a Zero Trust network, a central service evaluates user risk and access policy, while a gateway actually permits or denies the requested connection. Which description correctly separates the policy engine from the enforcement point?
The policy engine makes a decision based on identity, context and policy; the policy enforcement point applies that permit/deny result at the resource boundary. This separates centralized decision logic from data-plane traffic handling. The gateway should not silently treat access as trusted just because the request comes from a familiar network segment. The enforcement point must also fail in a documented manner if its control-plane decision source becomes unreachable.
Gateways can apply enforcement rules but do not necessarily own the organizational access-policy decision. In the given design, the central service evaluates identity and risk, while the gateway acts on the result. Reversing those roles would make the control-plane and data-plane responsibilities unclear.
An engine may indirectly cause a session to be allowed or denied, but its described role is evaluating policy rather than controlling physical ports in isolation. Risk context is central to adaptive access decisions. Treating it as a port-management appliance misses the reason to use the central decision service.
Zero Trust avoids granting implicit trust solely because a request originates on a private or corporate network. A known IP range can still contain compromised endpoints or misused identities. Omitting both policy evaluation and enforcement removes the controls that make each access request conditional on identity and context.
A regional office uses an adaptive Zero Trust access policy. A staff member signs in from an enrolled laptop but suddenly requests a sensitive financial report from a high-risk location. What is the most appropriate ADAPTIVE-IDENTITY response?
The engine can raise assurance requirements or limit the requested report access based on the user, endpoint and unusual location. A step-up authenticator, risk-based restriction or refusal may be appropriate under the documented policy. This avoids assuming inherent trust while still allowing legitimate staff to satisfy higher assurance when warranted. Repeated anomalous requests should be logged with the policy outcome so the office can distinguish user travel from account misuse.
Enrollment and an earlier MFA event are useful assurance signals, but they do not establish that the current access request is still acceptable. Device theft, session replay, or changed location can elevate risk after authentication. Retaining the prior permit without reevaluating context fails the adaptive requirement for a newly sensitive report request.
More detailed monitoring may help investigate the location change, but it is detective evidence rather than an adaptive decision on this particular access request. The financial report remains sensitive even when the laptop was previously enrolled. Policy must evaluate current risk and conditionally challenge or restrict the request before allowing protected data to leave the service.
A sign-in risk score describes conditions at a particular time and cannot automatically cover later changes. The scenario explicitly supplies a higher-risk location for the report access. Using only the cached decision would miss the need to reevaluate or step up protection before permitting this sensitive resource.
A factory has an old production network and a new analytics VLAN. Engineers assume that any computer on the analytics VLAN may contact every controller because both networks are 'inside' the plant. What is the principal Zero Trust weakness?
Location on an internal VLAN is being treated as permission to reach sensitive controllers. That creates an implicit trust zone that a compromised analytics endpoint could abuse. Zero Trust requires policy-based, context-aware authorization at the boundary, even when both sides are nominally part of the same organization. An approved controller-to-analytics flow should be tested explicitly instead of assuming every device behind the plant firewall is equally trustworthy.
Mutual TLS can authenticate endpoints and protect traffic, but a valid device certificate does not establish permission for every operational controller. A compromised or overprivileged analytics service could still reach sensitive systems. The factory must evaluate individual source-to-resource permissions and restrict the pathways actually needed for analytics, rather than elevating transport authentication into blanket authorization.
An architecture diagram can document intended flows but does not enforce the decision when a new analytics endpoint connects. The access boundary needs effective controls, such as source/workload identity and narrowly permitted controller destinations. A stale diagram is particularly weak evidence if real switch and firewall configuration permits unintended traffic.
Physical isolation may be an appropriate high-assurance solution in some industrial settings, but the scenario does not require eliminating every data connection. That response could disrupt useful monitoring and introduce its own removable-media risks. Zero Trust primarily calls for explicit policy and least-privilege enforcement at the requested boundary, not an unconditional air gap.
A municipal agency permits access to a protected service after a valid Zero Trust sign-in. Ten minutes later, the policy engine receives a high-confidence signal that the same device is compromised while an active session is still downloading documents. What should the policy enforcement point do when the new policy decision explicitly denies further access?
Once the policy engine determines that the device exceeds allowed risk, the enforcement point must apply that decision at the protected resource boundary. Depending on the architecture, it can deny further requests, revoke a session-specific authorization, or terminate the active path. Logging the change supports incident triage and later verification. This tests mid-session enforcement after changed risk, not merely knowledge of which component originally makes policy decisions.
An initial successful login does not guarantee that risk remains acceptable for the lifetime of a session. A newly compromised endpoint can begin abusing existing authorization after authentication. Delaying action until the next scheduled identity review ignores the specific updated deny decision and permits continued access to protected files. The enforcement mechanism must be capable of changing traffic handling when the policy source supplies a new decision.
The enforcement component applies access decisions; it is not authorized to rewrite the agency's risk policy when a dangerous session is detected. Silently weakening the threshold would create an exception for other users and defeat the purpose of continuous evaluation. An availability concern should be handled through documented policy and incident response, not an unauthorized control-plane change.
Network location does not prove that a device remains uncompromised. Permanent internal-address exceptions allow stolen sessions to bypass later signals and put sensitive resources at risk. Recording a username without restricting resource actions does not implement the engine's explicit deny decision. Zero Trust access must depend on current evaluated context and effective enforcement.
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.
Please check your mailbox for a message from support@examlabs.com and follow the directions.