Microsoft SC-300 Practice Test 68
Question 670
A tenant's sign-in log query returns no data for the requested month. What retention issue should be checked?
- Open the event's Conditional Access details in sign-in logs.
- Inspect managed identity sign-in events where available.
- Review the license-dependent log retention period and any configured export.
- Check provisioning status and app assignment scoping separately.
Explanation
Correct Answer
C:Portal log availability depends on retention and destination configuration. This matters here because a tenant's sign-in log query returns no data for the requested month. What retention issue should be checked.
Incorrect Answers
A:Sign-in diagnostics show applied and nonapplied Conditional Access controls. This matters here because a tenant's sign-in log query returns no data for the requested month. What retention issue should be checked.
B:Managed identity log categories help investigate workload token acquisition. This matters here because a tenant's sign-in log query returns no data for the requested month. What retention issue should be checked.
D:Assignment alone does not guarantee the downstream SCIM account was created.
Question 671
A privileged admin changed a Conditional Access policy without a ticket. Which log records the configuration modification?
- Export audit logs through diagnostic settings to a governed retention destination.
- Review service principal sign-in logs.
- Find user invitation, update and deletion events in directory audit history.
- Review Microsoft Entra directory audit logs.
Explanation
Correct Answer
D:Audit logs record administrative changes to tenant objects and policies.
Incorrect Answers
A:External log sinks can retain evidence beyond the portal's built-in retention.
B:Application-only authentication events are separate from user interactive sign-ins. This matters here because a privileged admin changed a Conditional Access policy without a ticket. Which log records the configuration….
C:Guest object changes are recorded as directory operations.
Question 672
A user has unexpected membership in a sensitive group. What evidence can identify who added them?
- Correlate the service principal actor identity with workload sign-in and ownership.
- Find user invitation, update and deletion events in directory audit history.
- Inspect group membership change events in AuditLogs.
- Verify licensing required for provisioning log visibility.
Explanation
Correct Answer
C:Audit records contain the actor and target of directory group changes. This matters here because a user has unexpected membership in a sensitive group. What evidence can identify who added them.
Incorrect Answers
A:Automated administrators may appear as application principals rather than people.
B:Guest object changes are recorded as directory operations. This matters here because a user has unexpected membership in a sensitive group. What evidence can identify who added them.
D:Provisioning logging capabilities differ by Microsoft Entra license.
Question 673
An application acquired a new API permission last night. Which event source helps attribute it?
- Review audit events for application and consent grant changes.
- Filter AuditLogs by role management operations and target object.
- Use provisioning logs and connector credential test results.
- Inspect group membership change events in AuditLogs.
Explanation
Correct Answer
A:Directory audit logs preserve administrative changes to applications and permission grants. This matters here because an application acquired a new API permission last night. Which event source helps attribute it.
Incorrect Answers
B:Audit entries link role updates to actors and timestamps. This matters here because an application acquired a new API permission last night. Which event source helps attribute it.
C:Provisioning logs can reveal rejected downstream authentication.
D:Audit records contain the actor and target of directory group changes. This matters here because an application acquired a new API permission last night. Which event source helps attribute it.
Question 674
A tenant's audit log shows an operation but its actor is a service principal. What should investigators examine?
- Review audit events for application and consent grant changes.
- Correlate the service principal actor identity with workload sign-in and ownership.
- Use summarize count() by AppDisplayName followed by sort by count descending.
- Review Microsoft Entra directory audit logs.
Explanation
Correct Answer
B:Automated administrators may appear as application principals instead of people.
Incorrect Answers
A:Directory audit logs preserve administrative changes to applications and permission grants. This matters here because a tenant's audit log shows an operation but its actor is a service principal.
C:Aggregation and sorting reveal which applications drive the most events. This matters here because a tenant's audit log shows an operation but its actor is a service principal.
D:Audit logs record administrative changes to tenant objects and policies. This matters here because a tenant's audit log shows an operation but its actor is a service principal.
Question 675
An administrator wants to reconstruct a deleted guest user's lifecycle. What audit activity matters?
- Find user invitation, update and deletion events in directory audit history.
- Configure diagnostic settings to send audit logs to an approved storage account.
- Correlate the service principal actor identity with workload sign-in and ownership.
- Filter AuditLogs by role management operations and target object.
Explanation
Correct Answer
A:Guest object changes are recorded as directory operations. This matters here because an administrator wants to reconstruct a deleted guest user's lifecycle. What audit activity matters.
Incorrect Answers
B:Storage sinks support governed retention for exported identity audit events.
C:Automated administrators may appear as application principals rather than people. This matters here because an administrator wants to reconstruct a deleted guest user's lifecycle. What audit activity matters.
D:Audit entries link role updates to actors and timestamps. This matters here because an administrator wants to reconstruct a deleted guest user's lifecycle. What audit activity matters.
Question 676
A policy diff shows a role definition changed unexpectedly. What source supplies timing and initiator?
- Filter AuditLogs by role management operations and target object.
- Find user invitation, update and deletion events in directory audit history.
- Review Identity Secure Score history and linked recommendation changes.
- Review audit events for application and consent grant changes.
Explanation
Correct Answer
A:Audit entries link role updates to actors and timestamps. This matters here because a policy diff shows a role definition changed unexpectedly. What source supplies timing and initiator.
Incorrect Answers
B:Guest object changes are recorded as directory operations. This matters here because a policy diff shows a role definition changed unexpectedly. What source supplies timing and initiator.
C:Score history supports trend assessment over time instead of one snapshot.
D:Directory audit logs preserve administrative changes to applications and permission grants. This matters here because a policy diff shows a role definition changed unexpectedly. What source supplies timing and initiator.
Question 677
A security review needs to retain admin changes longer than the Entra portal's default period. What strategy applies?
- Export audit logs through diagnostic settings to a governed retention destination.
- Select the AuditLogs category specifically in diagnostic settings.
- Inspect group membership change events in AuditLogs.
- Find user invitation, update and deletion events in directory audit history.
Explanation
Correct Answer
A:External log sinks can retain evidence beyond the portal's built-in retention. This matters here because a security review needs to retain admin changes longer than the Entra portal's default period. What strategy applies.
Incorrect Answers
B:Diagnostic settings can independently select supported identity log categories.
C:Audit records contain the actor and target of directory group changes. This matters here because a security review needs to retain admin changes longer than the Entra portal's default period. What strategy applies.
D:Guest object changes are recorded as directory operations. This matters here because a security review needs to retain admin changes longer than the Entra portal's default period. What strategy applies.
Question 678
An SCIM connector created the wrong target user account. Which logs explain the mapping decision?
- Inspect provisioning deprovision events and scope filters.
- Query AADProvisioningLogs or the current supported provisioning dataset.
- Review Entra application provisioning logs for the affected source object.
- Export audit logs through diagnostic settings to a governed retention destination.
Explanation
Correct Answer
C:Provisioning logs show matching, mapping and target-account actions.
Incorrect Answers
A:Provisioning failures may arise from assignment scope or downstream API errors.
B:Provisioning telemetry records actions and failures that can be aggregated by app.
D:External log sinks can retain evidence beyond the portal's built-in retention. This matters here because an SCIM connector created the wrong target user account. Which logs explain the mapping decision.
Question 679
An HR source update did not disable a departing employee in the target SaaS. What should be investigated?
- Review audit events for application and consent grant changes.
- Review Entra application provisioning logs for the affected source object.
- Inspect provisioning deprovision events and scope filters.
- Query AADProvisioningLogs or the current supported provisioning dataset.
Explanation
Correct Answer
C:Provisioning failures may arise from assignment scope or downstream API errors. This matters here because an HR source update did not disable a departing employee in the target SaaS.
Incorrect Answers
A:Directory audit logs preserve administrative changes to applications and permission grants. This matters here because an HR source update did not disable a departing employee in the target SaaS.
B:Provisioning logs show matching, mapping and target-account actions. This matters here because an HR source update did not disable a departing employee in the target SaaS.
D:Provisioning telemetry records actions and failures that can be aggregated by app. This matters here because an HR source update did not disable a departing employee in the target SaaS.
Question 680
A scheduled provisioning job stops after rotating a service token. Where is evidence?
- Check provisioning status and app assignment scoping separately.
- Verify diagnostic settings category selection and workspace destination.
- Use provisioning logs and connector credential test results.
- Verify licensing required for provisioning log visibility.
Explanation
Correct Answer
C:Provisioning logs can reveal rejected downstream authentication. This matters here because a scheduled provisioning job stops after rotating a service token. Where is evidence.
Incorrect Answers
A:Assignment alone does not guarantee the downstream SCIM account was created. This matters here because a scheduled provisioning job stops after rotating a service token. Where is evidence.
B:Sign-in events require the proper log category routing.
D:Provisioning logging capabilities differ by Microsoft Entra license. This matters here because a scheduled provisioning job stops after rotating a service token. Where is evidence.