Microsoft SC-300 Practice Test 5
Question 40
A team needs permission to read only application credentials metadata, with no matching built-in role. What approach minimizes privilege?
- Give every team member Application Administrator with tenant-wide scope because a read-only metadata task requires full application management.
- Assign Privileged Role Administrator so the team can change administrator eligibility while reading application credentials.
- Define and delegate a Microsoft Entra custom role with only supported credential-metadata read actions at the required scope.
- Inspect the built-in role name only and assume all credential metadata is readable without checking its actual permitted actions.
Explanation
Correct Answer
C:Inspect the supported directory resource actions and create a custom role containing only the read permissions required by the metadata task. Assign it at a supported minimal scope, then test that credential secrets and write actions remain inaccessible.
Incorrect Answers
A:Application Administrator grants broad ability to manage app registrations and credentials and is not an appropriate default for a metadata-only read task. Determine the narrowest supported resource action before granting access.
B:Privileged Role Administrator governs directory role assignment and PIM eligibility, not a narrowly authorized view of application credential metadata. Assigning it would expand privileged access without solving least-privilege application inspection.
D:Role display names are insufficient evidence of permissions. For a narrowly defined app metadata task, inspect the role definition's supported actions and scope before assigning anything, including a new custom role.
Question 41
An operator has a directory custom role but cannot change Azure subscription IAM. What explains the denial?
- Grant the operator Privileged Role Administrator, assuming it includes every Azure subscription access-assignment action.
- Grant a suitably scoped Azure RBAC access-administration role to perform subscription IAM changes.
- Change the Entra custom-role scope to an administrative unit and assume it now manages Azure subscription IAM.
- Add another Entra application-registration permission to the custom role without granting Azure RBAC privileges.
Explanation
Correct Answer
B:Microsoft Entra custom roles and Azure RBAC govern different resources and action namespaces. To change subscription access assignments, the operator needs an Azure role such as Role Based Access Control Administrator or User Access Administrator at the approved scope.
Incorrect Answers
A:Privileged Role Administrator manages Microsoft Entra directory privileged-role assignments, not Azure resource IAM by default. An Azure resource assignment requires a supported Azure RBAC role and scope.
C:An administrative unit controls supported Entra directory resource administration. It neither creates an Azure subscription role assignment nor changes which management-plane actions a directory role permits.
D:Application-registration permissions affect directory application objects. They do not supply Microsoft.Authorization/roleAssignments/write on an Azure subscription, so adding more application permissions would not resolve the IAM denial.
Question 42
A support user belongs to two role-assignable groups with eligible Microsoft Entra administrator roles. One role is activated for this hour; the other is not. How should current effective privileges be assessed?
- Treat all eligible roles in both groups as active for the entire day, regardless of activation status.
- Combine direct and group-derived active assignments at their scopes; treat unactivated PIM eligibility as potential rather than current privilege.
- Count only the first role-assignable group in the directory list and disregard the second role and its scope.
- Ignore both group-derived assignments because only individually assigned Entra roles can contribute to effective access.
Explanation
Correct Answer
B:Effective authority includes every active direct or group-derived role at its assigned scope. PIM eligibility can become authority only upon approved activation; here the second unactivated role must not be counted as already active.
Incorrect Answers
A:Eligibility grants a path to activate, not the permissions of an active role. Without completing required activation steps, the second eligible role does not confer those administrative actions.
C:Directory display ordering has no authorization meaning. A user may have more than one role and scope through several groups and direct assignments, and each active grant must be evaluated.
D:Microsoft Entra supports assigning supported roles to protected role-assignable groups. Active membership and role assignments through such groups can contribute to privileges; ignoring group-derived grants understates access.
Question 43
An operator sees that they are eligible for an Entra directory administrator role in PIM, but a privileged task still fails. No active assignment is shown for that role. What should they verify first?
- Check PIM activation status, approval requirements and the role assignment scope before retrying.
- Change the role display name to the built-in administrator title without activating it.
- Assign Azure subscription Owner to replace the unactivated Microsoft Entra directory role.
- Wait for the directory user display name to synchronize before activating or inspecting access.
Explanation
Correct Answer
A:An eligible role becomes usable only after activation and any required approval, MFA or justification. Confirm the target resource is within the granted role scope; visibility of the role alone does not mean it is currently effective.
Incorrect Answers
B:A role definition name is metadata; changing it does not activate an eligible assignment or widen its allowed actions. The user must satisfy the actual PIM activation workflow.
C:Azure Owner controls Azure resource administration rather than the relevant Entra directory action and would add excessive privilege. It does not automatically make an eligible Entra role active.
D:Updating a profile display name is unrelated to a role being eligible rather than active. The relevant diagnostic evidence is PIM activation status and the resource scope.
Question 44
A security team wants to audit which directory role grants a sensitive action. Where should it look?
- Create a new custom role and assume its display name tells reviewers which operations existing roles authorize.
- Inspect only Azure subscription Contributor assignments and infer all Microsoft Entra directory actions from them.
- Inspect the assigned Entra role definition for allowed resource actions, then check the principal and assignment scope.
- Use the primary UPN domain to decide which tenant role includes the sensitive operation.
Explanation
Correct Answer
C:Microsoft Entra role definitions list permitted directory actions, while assignments specify which principal receives those actions and at which supported scope. Inspecting both is necessary to connect the sensitive operation to an effective grant.
Incorrect Answers
A:Creating another role does not identify what an existing role actually permits. The investigator needs the definitions and assignments currently granting the sensitive action, not a speculative role label.
B:Azure subscription Contributor governs Azure resource management. Microsoft Entra role permission definitions use a separate authorization plane, so those assignments do not explain a sensitive Entra directory action.
D:The sign-in domain identifies a user namespace, not the permission set of their administrator roles. Role definitions and assignment scopes determine whether the action is authorized.
Question 45
A proposed custom Microsoft Entra role includes several app-registration permissions, but reviewers approved only the ability to update selected application credentials. What must change before assignment?
- Grant Global Administrator alongside the custom role so credentials can always be modified, regardless of approvals.
- Keep all excess permissions and document that the engineer intends to use only one action.
- Limit the custom role definition to the approved supported actions and assign it at the smallest applicable application scope.
- Assign the broad role permanently at tenant scope and rely on an annual access review to catch misuse.
Explanation
Correct Answer
C:The role definition must contain only permitted supported actions, and the role assignment should be scoped to the relevant application resources where supported. This enforces the approval rather than relying on policy promises.
Incorrect Answers
A:Global Administrator substantially widens effective rights and defeats the approval boundary. A custom role exists to delegate a narrower set of supported directory actions without tenant-wide administration.
B:An intention not to use surplus permissions is not a technical access control. An assigned principal can exercise every allowed role action within scope, even if some were not in the approval request.
D:Periodic reviews cannot undo overly broad standing permissions already granted. Apply least privilege to the definition and scope before the role becomes active.
Question 46
HR onboards a new employee who needs an Entra cloud-only identity. Which directory record is required?
- Create a workforce Member user object with an approved, unique UPN and supported initial authentication setup.
- Invite the new employee solely as an external B2B Guest and assume this is the normal internal HR onboarding identity.
- Create a security group named after the employee without creating an individual directory user object.
- Create a workload service principal in place of the employee so they can complete interactive workforce sign-in.
Explanation
Correct Answer
A:For a cloud-only employee, create a Microsoft Entra user with the appropriate Member identity, unique tenant-verified sign-in suffix and initial authentication settings. Subsequent licensing and group assignments are separate onboarding steps.
Incorrect Answers
B:B2B Guest invitations represent external collaborators using external identities. They are not the default replacement for creating the employee’s own cloud-only workforce account in this scenario.
C:A group organizes membership and entitlements but is not the employee’s authentication principal. Without a user object, the employee has no individual workforce sign-in identity.
D:A service principal represents an application or workload, not a person signing into workforce services. Substituting it for an employee also prevents normal per-person access accountability.
Question 47
A user is temporarily suspended after an incident and must not start new sign-ins. What account control applies?
- Block sign-in for the specific user account; separately revoke active sessions when immediate termination is required.
- Only remove the person from one Microsoft 365 group and assume all other enterprise app sessions stop.
- Change the user display name to Suspended but leave accountEnabled true and sessions intact.
- Delete all Microsoft Entra enterprise application registrations to prevent this employee from authenticating.
Explanation
Correct Answer
A:Blocking the affected account stops new sign-ins while preserving the user object. Existing tokens or sessions need separate revocation and workload-specific validation when incident containment requires immediate session termination.
Incorrect Answers
B:Group removal may revoke one set of entitlements after propagation but does not disable sign-in for the person’s other applications. The incident requirement targets the user account, not one group.
C:A display-name change is descriptive metadata, not an authentication policy. The user could continue to sign in because the account remains enabled and existing sessions are unaffected.
D:Deleting applications would interrupt other employees and systems and is not a targeted account control. Block the specific principal and handle sessions without destroying organizational application registrations.
Question 48
A departing employee must lose sign-in access immediately, but the organization needs to preserve and delegate their Exchange mailbox under the approved retention policy. What plan fits?
- Block the user’s sign-in, address existing sessions, and use the supported mailbox conversion/retention and licensing steps before deleting anything.
- Delete the Entra user and unassign every license first, assuming the mailbox remains available indefinitely without further action.
- Rename the departing user’s Entra display name and share their password with the successor to preserve access to past email.
- Move the user into a new security group and assume the group automatically becomes an Exchange shared mailbox with compliant retention.
Explanation
Correct Answer
A:Identity access termination and mailbox preservation are separate workflows. Block sign-in and sessions promptly, then follow Microsoft 365 guidance for mailbox conversion or retention, legal holds where applicable, and licensing conditions before any account removal.
Incorrect Answers
B:Deletion or immediate license removal can start data-retention and mailbox-deletion timelines. It is unsafe to assume the mailbox survives indefinitely without conversion or the proper retention and licensing controls.
C:A display name is not an access block and sharing credentials destroys individual accountability. Authorized successors should use delegated mailbox permissions after the former employee’s access is disabled.
D:Security-group membership alone does not convert a user mailbox into a shared mailbox or establish retention. Perform supported Exchange/Microsoft 365 administration and review the legal preservation requirements.
Question 49
A cloud-only employee has legally changed their surname, and HR wants their Microsoft Entra sign-in address to use the verified new UPN suffix. The display name has changed but login still uses the old identifier. What should be updated?
- Change only the account displayName again and assume the userPrincipalName always follows it automatically.
- Revoke every application assignment permanently instead of updating the employee’s sign-in name.
- Change the tenant-wide primary domain and assume this automatically rewrites that one existing user’s UPN.
- Update the userPrincipalName on the existing user object and assess downstream sign-in and application dependencies.
Explanation
Correct Answer
D:The existing cloud-only user can be updated to a unique UPN with an approved verified suffix. Review workloads or clients that depend on the old identifier and communicate the sign-in change.
Incorrect Answers
A:The display name shown to people is a different attribute from the UPN used for sign-in. Repeating a display-name edit does not update the existing account’s sign-in identifier.
B:Application assignment revocation would remove business access without fixing the account name. Keep the current user object and change the intended sign-in attribute while evaluating dependency impact.
C:Making a domain primary generally changes the default suffix for newly created users, not each existing UPN. The requested change is user-specific and should not alter tenant-wide naming.
Question 50
An employee works in Canada but lacks a usageLocation value. The team is preparing a Microsoft 365 product-license assignment that is regulated by geographic service availability. Which prerequisite matters?
- Set the user’s correct usageLocation (country or region) and verify the intended license and service plans are available there.
- Change the employee’s UPN suffix to a Canadian-looking domain because the sign-in address determines license geography.
- Grant Microsoft Entra Global Administrator to the user before assigning their ordinary productivity license.
- Set only the company-branding locale and assume localization establishes the user’s service availability region.
Explanation
Correct Answer
A:Microsoft 365 licensing checks service availability by user usage location. Set the employee’s actual country or region in the directory and resolve any plan restrictions before assignment; group-based licensing may otherwise inherit a tenant default.
Incorrect Answers
B:A sign-in domain identifies the user account and does not reliably encode where the employee consumes licensed services. Licensing uses usageLocation rather than inferring geography from the UPN suffix.
C:Administrative privileges are unrelated to ordinary entitlement assignment. Assigning Global Administrator would be excessive and would not supply the required geographic service-eligibility attribute.
D:Sign-in branding language changes the authentication experience, not licensing geography. Canadian French or English display language is not a substitute for the correct usageLocation value.