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 SOC investigates a compromise spanning endpoints, email and cloud accounts. Its current EDR sees host processes but not mail-delivery or cloud-identity events. Which comparison of EDR and XDR is most useful?
XDR can link endpoint, identity, email and cloud signals to support broader investigations than one sensor type. The SOC should validate ingestion, timestamp consistency and response permissions. Cross-domain branding alone does not guarantee complete coverage or correct correlation. The combined view is valuable only when source coverage and alert correlation support the claims; the XDR label alone proves nothing.
A host process alert cannot establish what happened in an email gateway or cloud identity provider if those systems were never integrated. Endpoint evidence is valuable but has a different scope. A cross-domain investigation must verify that its telemetry connectors ingest, normalize and correlate the relevant event records.
Adding host telemetry can improve endpoint visibility, but two endpoint tools do not automatically provide cross-domain correlation. The incident spans email delivery and cloud sign-in activity that neither agent collects. XDR value depends on supported integrations and accurate joining of events rather than the number of installed endpoint products.
A common screen is not the same as unified detection context. When mail indicators cannot be joined with user and cloud-account activity, the team may miss the intrusion sequence despite viewing multiple lists. The SOC should validate entity mapping, timestamps, coverage gaps and response actions across integrated data sources.
A worker leaves a company on Friday afternoon. HR records the termination immediately, but the employee's VPN and payroll accounts remain active over the weekend. What identity-lifecycle control is missing?
HR termination should trigger disabling or revoking active identities, sessions, tokens and privileged roles across relevant systems. The company should verify completion and handle exceptions under approved ownership. Coordinated deprovisioning prevents departed staff from retaining unnecessary authorized-looking access. Deprovisioning should cover active sessions, delegated service access and external applications, not merely disable the employee's main directory username. The completion check must include already-issued sessions and service-specific grants, not only disabling the central directory username.
Revoking one access path closes only part of the former employee’s permissions. Payroll remains usable during the weekend despite an authoritative employment-status change, which defeats timely lifecycle control. Termination should trigger coordinated access removal across all affected services, with verification and accountable exception handling where technically necessary.
A periodic inventory can catch accounts missed by other processes, but it may leave a terminated employee’s VPN or payroll access live for months. The scenario gives an authoritative HR termination record that should trigger timely coordinated revocation. Quarterly checks are a backstop, not the primary joiner-mover-leaver enforcement workflow.
Password rotation alone may not invalidate existing sessions, refresh tokens or application-specific accounts. The departing employee could continue accessing protected resources through previously established authentication. Effective termination processing must identify the person’s dependent identities and revoke active authorization across target services, with completion evidence tied to the HR event.
A finance team performs quarterly access attestation. One employee can both post journal entries and approve the related audit review, even though policy requires separation of duties. What should the review owner do?
The periodic review provides evidence that one identity holds incompatible responsibilities. The owner should examine actual duties, remove unjustified access or track a properly approved compensating exception. Completion evidence should show permissions changed and the conflict was resolved or explicitly accepted. The owner should verify whether a temporary exception is still required and record its expiry rather than certifying incompatible access indefinitely.
Historical access approval does not guarantee compliance with current segregation-of-duties rules. Attestation should verify whether privileges are still necessary and permitted. Automatically renewing the conflict defeats its purpose. A grant's age does not justify it; a periodic review must evaluate current duties, the separation-of-duties rule and exceptions.
Expanding excessive privileges would spread the conflict across more accounts. Consistency is not security when the baseline violates separation-of-duties requirements. Each access role should reflect legitimate work. Uniformly spreading conflicting finance privileges would increase fraud exposure instead of resolving a detected entitlement problem.
Destroying review records removes accountability and may conceal misuse. Attestation evidence should be protected and retained according to policy. The appropriate response is correcting the finding, not erasing it. Deleting review results removes the evidence needed to show that inappropriate access was identified, escalated and corrected.
An IT technician asks for privileged access to an HR database using a new account created with a similar name to a departed manager. What should identity administration establish before issuing credentials?
Identity proofing establishes that the requester is the person or service being represented, while authorization verifies their role needs. A lookalike name is insufficient. The organization should validate sponsorship and avoid reusing identities that could inherit stale permissions. A known administrator sponsor should independently confirm the requester's actual role and need before the identity team issues privileged rights.
A similar name and a plausible internal email can support initial lookup, but they are not proof that the current requester is the departed manager or an authorized successor. Privileged issuance needs authoritative identity proofing, employment status and a documented role approval. Otherwise, an attacker or mistaken account could inherit high-risk HR database permissions.
An email address or familiar-looking username can be spoofed, misassigned or reused; neither establishes that an account should receive HR database privileges. Identity proofing and authoritative approval require independent checks. The technician’s urgency can change escalation priority, but it does not eliminate proofing and privileged role authorization.
Short-lived access reduces the time a credential can be abused, but even a brief elevated session can expose salary, medical or personnel data. Expiration does not establish who the applicant is or whether the access was approved. The administration process must validate identity and sponsorship before privilege activation, with duration controls applied afterward.
A company uses a cloud identity provider for staff sign-in to a third-party application. The application still maintains local emergency accounts. Which statement correctly describes federation?
Federation relies on explicit trust relationships and correctly validated claims, including issuer, audience and expiry where applicable. The relying party still controls access rights to its resources. Exception accounts should be scoped, monitored and not treated as unrestricted alternatives. The application must still evaluate whether the issued assertion applies to its audience and requested operation, not just recognize the issuing partner.
Sharing password verifiers or credentials creates another sensitive repository and undermines the desired federation trust boundary. SAML or OIDC-style federation normally lets an application accept a properly validated assertion or token from the IdP. The app still owns its local authorizations and must verify issuer, audience and other relevant claims.
A cryptographic signature alone does not grant every application permission. The application must verify the trusted issuer, intended audience, token lifetime and user authorization claims. Conflating identity authentication with administrator entitlement would allow excessive access even when federation signatures validate correctly.
Federation can coexist with tightly governed local break-glass access. Automatically removing every exception may destroy a critical recovery path in an outage. The company should decide emergency account need, scope, logging and rotation based on business continuity rather than treating federation as a prohibition on local identities.
A SaaS application accepts SAML assertions from an enterprise IdP. One assertion is validly signed but intended for a different application audience. What should the relying application do?
The relying party should check issuer trust, audience, timing and signature according to its federation policy. A mismatch means the token was not issued for this application even if otherwise genuine. Rejecting it limits cross-application token misuse and preserves the intended trust boundary. A correctly signed token intended for a different service is not permission to access the relying party that received it.
A valid issuer signature proves that a trusted identity provider signed the assertion, not that the assertion was issued for this application. Reusing an assertion intended for another service can cause cross-service token substitution. The relying party must check audience, recipient, timing and other required contextual conditions in addition to signature and issuer trust.
Account mapping can associate a federated identity with a local user, but it cannot transform an assertion for another service into a valid one for this application. The audience condition prevents cross-application replay even when the same employee is known to both services. Reject the mismatched assertion and investigate why the IdP issued it.
A different application accepting the assertion does not grant this relying party authorization to accept it. Such forwarding may also leak bearer assertions and increase replay risk. The receiving service must independently validate its own expected audience, recipient and other conditions before establishing any local session, not borrow another service’s decision.
An organization migrates support staff from an LDAP directory to cloud SSO using SAML. The relying application cannot find the required email attribute although the IdP says login succeeded. What should be reviewed?
LDAP stores directory attributes that may need transformation into SAML claim names and formats expected by a relying service. Mapping errors can cause an application to reject an otherwise authenticated user. The team should inspect schema configuration, avoid unnecessary claims and validate a test account. For the failing login, capture a sanitized SAML assertion and compare its attribute names, value formats, audience and issuer with the relying party’s configuration. A valid IdP session cannot compensate for a missing required claim.
A password reset may address a failed sign-in, but the scenario already says authentication succeeded at the identity provider. The relying application’s missing email field is an attribute-mapping or assertion-content issue. The team should inspect the claims the application actually received rather than changing credentials unrelated to the failure.
Stronger authentication can be useful independently, but it does not supply the email claim that the relying service expects. If the identity provider issued a valid assertion with an absent or differently named attribute, more MFA prompts will not correct the schema or claim mapping.
An expired assertion can cause separate SSO problems, but the reported failure concerns a required identity attribute that is absent despite successful authentication. Extending token validity cannot create a missing email claim and may prolong the exposure of a compromised assertion. The attribute schema must be tested directly.
A customer consents to a budgeting app reading transaction categories from a banking API. The app should not receive the customer's banking password or unlimited account administration. What OAuth principle is most relevant?
OAuth delegated authorization allows a customer to grant a third-party app limited API access without disclosing the banking password to that app. The resource server should validate an access token for the intended audience, granted scopes and expiration, rather than treat a sign-in assertion as unlimited permission. Revocation, consent records and narrowly permitted transaction-category reads help prevent the budgeting service from performing account administration or collecting unrelated data.
A token can avoid disclosing the customer's password yet still be dangerously overprivileged. Permanent administrative scope would let the app act far beyond the consented read-only category access, increasing damage after compromise. Delegated authorization must restrict requested resources and actions, support revocation and use appropriate token lifetimes rather than assuming every OAuth grant is automatically safe.
An OAuth client-credentials grant normally authorizes a client in its own right rather than representing a particular resource owner's delegated approval. Authenticating the budgeting service does not by itself prove that this bank customer consented to the proposed data access. A customer-delegated grant must be scoped, audience-bound and traceable to the customer's authorized resource permissions.
An ID token generally conveys authentication assertions to its intended client and audience; it should not be treated as delegated API authorization for transaction categories. The banking resource needs a scoped access token with appropriate audience, expiry and consent. Confusing token purposes can inadvertently grant access outside the customer’s approval.
A company has engineers, accountants and HR staff whose permissions follow stable job functions. Which access-control model simplifies consistent role assignment?
RBAC groups privileges into organizational roles that can be assigned and reviewed during employment changes. Engineers and accountants can receive different rights without configuring each user independently. The company should periodically inspect role composition and avoid accumulating excessive permissions. The role-to-entitlement mapping should be reviewed when an employee changes jobs so old privileges do not accumulate.
Unrestricted discretionary ownership expands access beyond job needs. Some systems support discretionary controls, but the stated stable workforce functions lend themselves to central role definitions. The company should not let every account administer every database.
Context attributes can strengthen access decisions, but this proposal omits the central requirement: permissions that consistently follow job responsibilities. It could grant access to someone in the right location using an approved device despite the wrong employment function. RBAC directly expresses stable roles and supports repeatable joiner/mover changes.
Physical or network location does not establish accounting or HR job authorization. A compromised device at headquarters could misuse such a rule. Permissions should follow approved responsibilities. Physical location is not evidence that a person has the job role needed to administer sensitive financial records.
A research laboratory permits access to a sensitive dataset only when the user is an approved investigator, the device is managed and the request occurs during the grant window. What policy model fits?
ABAC can express conditions based on an investigator's status, device posture, resource classification and requested time. The policy engine should verify claims and enforce decisions at access time. The lab should test edge cases such as expired grants and unmanaged devices, not simply assign a permanent role.
A file owner's arbitrary share choice would not reliably enforce required device and time conditions. The laboratory needs a central policy that evaluates several attributes. Discretionary sharing may be inappropriate for restricted research information.
An investigator role may be one useful attribute, but the case also requires managed-device assurance and a valid time window for every access. A standing role that ignores both conditions can allow unauthorized late or untrusted-device use. ABAC evaluates all applicable subject and contextual conditions together.
A permanent job role can address one dimension but would ignore the device and time constraints in the scenario. Role membership may contribute an attribute, yet dynamic evaluation is still necessary. The organization should not silently drop context rules.
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.
Please check your mailbox for a message from support@examlabs.com and follow the directions.