You save $69.98
SC-300 Premium Bundle
- Premium File 490 Questions & Answers
- Last Update: Nov 2, 2026
- Training Course 43 Lectures
- Study Guide 599 Pages
You save $69.98
Two identity controls must be deployed together. Task 1: An Azure function is frequently redeployed and its identity should be deleted automatically when that exact function resource is removed. Task 2: An OAuth investigation finds an app whose publisher and permission grants no longer match its approved risk profile. Which coordinated action is appropriate?
Step 1: A system-assigned identity shares its lifecycle with the resource and is removed when the resource is deleted. Step 2: An approved app catalog status does not guarantee that every future permission grant remains acceptable. Both verification checks are required: Removing the test function also removes its corresponding system-assigned identity principal; and The removed excessive permission no longer appears and the approved minimum access remains available.
The plan is partly correct, but Use appropriate delegated API permissions with the least scopes and consent allowed by the tenant is not the missing control. Instead, use: Use a system-assigned managed identity attached to the Azure function.
A system-assigned identity shares its lifecycle with the resource and is removed when the resource is deleted. The other proposed action (define supported app roles and assign the authorized users or groups to those roles on the enterprise application) addresses a different operation. An approved app catalog status does not guarantee that every future permission grant remains acceptable.
Both actions target other requirements: An interactive client signs in employees and calls an API on their behalf but has been configured with app-only access to all tenant data; A custom app requires application roles for employees but users receive no role claim after a group has been created. Neither completes the stated two-step design.
An identity project has two requirements. A: A reviewer denies an external guest's app access, and the team must ensure the guest does not regain the assignment through the same access package. B: A custom security attribute investigation needs audit records but the default audit category is not exposing the sensitive attribute details to the authorized analyst. Select exactly TWO changes that jointly satisfy them.
This implements requirement A. The entitlement system can reprovision access if its assignment remains active; removal must target the authoritative grant. Verify that the guest is excluded from package assignment and the app does not get re-provisioned.
This implements requirement B. Custom security attribute audit logs use restricted access to avoid leaking sensitive attribute assignments in ordinary directory audit reports. Verify that an authorized role reads the attribute-change event while a standard read-only identity analyst remains restricted.
Submitting or approving a request is not identical to completed delivery of each resource.
Manager-based review assignment scopes the decision to the responsible reporting relationship.
Access review recommendations can help reviewers prioritize accounts, but are not definitive authorization decisions.
After changing the environment to: Create a Defender for Cloud Apps activity policy with appropriate thresholds and notification recipients, auditors need to validate the original need: A company wants a policy alert when a SaaS account downloads an unusually large number of files in a short period. Which result demonstrates the intended behavior?
Activity policies evaluate supported cloud app telemetry and issue alerts for matching behaviors.
The Cloud app catalog provides risk and compliance context that can inform a sanctioning decision. Instead, this case needs to establish that A seeded excessive-download sequence produces the intended alert while a small normal download set does not.
App-only workload authorization uses a workload identity and permission grants rather than a personal user's delegated session. The suggested evidence belongs to a separate control. Here the test must show: A seeded excessive-download sequence produces the intended alert while a small normal download set does not.
SaaS activity detection and identity authentication evidence are separate telemetry sources needed for incident context. Instead, the required outcome is: A seeded excessive-download sequence produces the intended alert while a small normal download set does not.
The reviewed configuration is: Block the user from sign-in and revoke sessions while the incident team performs recovery. The original problem was: A compromised account must be prevented from initiating any new Microsoft Entra sign-ins, beyond the removal of one application assignment. What measured result confirms it works?
Blocking account sign-in is a tenant identity control whereas removing an individual app assignment is resource-specific.
Sign-in risk assesses a particular authentication event, not the overall ongoing compromise state of an identity. That observation verifies: A simulated risky sign-in reaches the extra control while a low-risk sign-in proceeds according to its normal policy. It does not prove the required result: The compromised test account is denied a fresh sign-in even to an unrelated application.
Certificate authentication relies on trusted certificate issuers and mappings, not merely upload of any client certificate. The suggested evidence belongs to a separate control. Here the test must show: The compromised test account is denied a fresh sign-in even to an unrelated application.
Windows Hello for Business uses device-bound keys or credentials and requires the trust configuration to match hybrid architecture. Instead, the required outcome is: The compromised test account is denied a fresh sign-in even to an unrelated application.
The organization must fix both requirements before signoff: (1) A new employee needs access only to a subset of apps but the admin proposes making that person a global administrator to obtain them; and (2) Cloud password resets must update the authoritative AD DS user password, not just the cloud-only account. Select the combined implementation.
Step 1: Resource access assignments and directory administration are separate privilege planes. Step 2: Password writeback sends supported cloud-initiated password changes to the local directory so cloud and domain credentials remain coordinated. Both verification checks are required: The employee opens the approved application but cannot change tenant-level security settings; and A test user resets the password in cloud SSPR and signs in on-premises with the new credential.
Password writeback sends supported cloud-initiated password changes to the local directory so cloud and domain credentials remain coordinated. The other proposed action (Configure the Microsoft Entra group creation settings and verify the delegated role exceptions before changing group owners) does not implement the first control. Resource access assignments and directory administration are separate privilege planes.
The plan is partly correct, but Verify the custom domain and configure it as the tenant's primary domain rather than bulk-editing existing accounts is not the missing control. Instead, use: Configure the supported password writeback capability and SSPR integration with required permissions.
Resource access assignments and directory administration are separate privilege planes. Password writeback sends supported cloud-initiated password changes to the local directory so cloud and domain credentials remain coordinated. The proposed steps (Configure the Microsoft Entra group creation settings and verify the delegated role exceptions before changing group owners; verify the custom domain and configure it as the tenant's primary domain rather than bulk-editing existing accounts) address other capabilities instead of this required pair.
Two identity controls must be deployed together. Task 1: An identity audit shows former contractors are still enabled even though their employment has ended and their group memberships were removed. Task 2: A contractor using a federation identity provider must sign into supported External ID collaboration flows that use SAML or WS-Federation. Which coordinated action is appropriate?
Step 1: Removing membership from one group does not necessarily disable authentication to other resources. Step 2: External federation configuration tells the resource tenant which external assertions may represent the invited identity. Both verification checks are required: The terminated test account cannot sign in after account disablement and remaining access is reviewed; and A permitted federated contractor completes the expected sign-in flow without creating an internal employee password.
Removing membership from one group does not necessarily disable authentication to other resources. External federation configuration tells the resource tenant which external assertions may represent the invited identity. The proposed steps (Assign the appropriate Microsoft Entra role as PIM eligible and require activation only for the maintenance window; update the cloud UPN through supported identity management and validate application mappings that use it) address other capabilities instead of this required pair.
Removing membership from one group does not necessarily disable authentication to other resources. The other proposed action (update the cloud UPN through supported identity management and validate application mappings that use it) addresses a different operation. External federation configuration tells the resource tenant which external assertions may represent the invited identity.
External federation configuration tells the resource tenant which external assertions may represent the invited identity. The other proposed action (Assign the appropriate Microsoft Entra role as PIM eligible and require activation only for the maintenance window) does not implement the first control. Removing membership from one group does not necessarily disable authentication to other resources.
An identity project has two requirements. A: A requester sees an access package but the request remains in Pending approval while an administrator assumes the resource assignment is already active. B: A tenant must retain access during an outage where normal PIM, MFA or mobile services are unavailable. Select exactly TWO changes that jointly satisfy them.
This implements requirement B. Emergency accounts provide a recovery path separate from ordinary daily elevated access while requiring exceptional safeguards. Verify that a documented recovery drill succeeds and alerts are generated for emergency-account use.
This implements requirement A. Submitting or approving a request is not identical to completed delivery of each resource. Verify that the audit distinguishes submitted, pending, approved, delivering and delivered states for the test request.
Resource membership can be granted by multiple paths, and access package assignments have their own lifecycle.
Entitlement management policies can provide time-limited assignments rather than permanent grants.
The entitlement system can reprovision access if its assignment remains active; removal must target the authoritative grant.
An enterprise requires a narrowly scoped remediation: A sensitive enterprise application should not be available to every tenant user simply because it is registered. What should the team implement to verify: An assigned user signs in and an unassigned test user is denied?
The enterprise application's assignment requirement limits which directory principals may sign in to that app. Require user assignment for the enterprise application and assign only authorized users or groups. The acceptance check is: An assigned user signs in and an unassigned test user is denied.
An app object defines the software registration while a service principal is its tenant-specific security instance. It does not resolve A sensitive enterprise application should not be available to every tenant user simply because it is registered.
Enterprise application management can be delegated without providing unrelated tenant-wide privileges. This does not address the actual issue: A sensitive enterprise application should not be available to every tenant user simply because it is registered.
User consent and privileged admin consent follow separate tenant consent policies and permission sensitivity. In the present case, however, the missing capability is: Require user assignment for the enterprise application and assign only authorized users or groups.
A security engineer has this implementation task: A high-risk newly discovered cloud application should be flagged as unsanctioned for the organization to enforce a controlled policy. Select the best technical action, with this acceptance test: The application appears as unsanctioned and the enabled enforcement channel applies the intended restriction.
Sanctioning classifies cloud app use; blocking may depend on supported endpoint or network enforcement integration. Mark the reviewed app unsanctioned and integrate the relevant enforcement path where supported. The acceptance check is: The application appears as unsanctioned and the enabled enforcement channel applies the intended restriction.
An approved app catalog status does not guarantee that every future permission grant remains acceptable. It is useful when: An OAuth investigation finds an app whose publisher and permission grants no longer match its approved risk profile. This question instead calls for: Mark the reviewed app unsanctioned and integrate the relevant enforcement path where supported.
The Cloud app catalog provides risk and compliance context that can inform a sanctioning decision. This does not address the actual issue: A high-risk newly discovered cloud application should be flagged as unsanctioned for the organization to enforce a controlled policy.
Application registration account-type configuration defines which directories and account classes can request sign-in. In the present case, however, the missing capability is: Mark the reviewed app unsanctioned and integrate the relevant enforcement path where supported.
An identity project has two requirements. A: An administrator is unsure whether report-only Conditional Access policies actually enforce restrictions while testing them. B: A workload identity with suspicious token activity should lose access to sensitive resources until it is remediated. Select exactly TWO changes that jointly satisfy them.
This implements requirement A. Report-only logs expected policy outcomes but do not themselves block the user's sign-in. Verify that a report-only test remains allowed with documented impact and enabling the same approved policy enforces it.
This implements requirement B. Workload identity risk-based enforcement differs from user-oriented sign-in risk MFA or password reset. Verify that the selected high-risk service principal is denied resource access while an unaffected service principal is allowed.
Sign-in frequency governs reauthentication behavior and is different from controlling how a password is initially created.
Number matching requires the user to enter the sign-in challenge rather than approving an unrelated push blindly.
What If simulates policy applicability without itself changing access rules or proving end-to-end app dependencies.
A Microsoft Entra rollout has two issues: first, Employees can reset passwords in the cloud but forgot to register sufficient alternate security information; second, Users can reach an internal app only by a fixed IP address yet the resource's private FQDN is being used in policy assignments. Which paired implementation meets both acceptance criteria?
Step 1: Self-service password reset depends on sufficient registered recovery methods and the user's enabled policy scope. Step 2: Private Access name resolution and forwarding depend on correctly describing the target resource, not only granting the user an app assignment. Both verification checks are required: A pilot user with registered methods completes SSPR while an unregistered user receives onboarding guidance; and Both the intended name and private destination resolve through the supported path for an approved device.
Self-service password reset depends on sufficient registered recovery methods and the user's enabled policy scope. Private Access name resolution and forwarding depend on correctly describing the target resource, not only granting the user an app assignment. The proposed steps (Use appropriate device filters and Conditional Access conditions validated against registration and compliance properties; revoke the user's active sign-in sessions and apply account or device containment as required by incident policy) address other capabilities instead of this required pair.
Self-service password reset depends on sufficient registered recovery methods and the user's enabled policy scope. The other proposed action (revoke the user's active sign-in sessions and apply account or device containment as required by incident policy) addresses a different operation. Private Access name resolution and forwarding depend on correctly describing the target resource, not only granting the user an app assignment.
Private Access name resolution and forwarding depend on correctly describing the target resource, not only granting the user an app assignment. The other proposed action (Use appropriate device filters and Conditional Access conditions validated against registration and compliance properties) does not implement the first control. Self-service password reset depends on sufficient registered recovery methods and the user's enabled policy scope.
Please check your mailbox for a message from support@examlabs.com and follow the directions.