Microsoft SC-300 Practice Test 70
Question 690
A query must count failed sign-ins per application in the past seven days. What KQL pattern fits?
- Summarize AADProvisioningLogs by Action and bin(TimeGenerated, 1d).
- Correlate the service principal actor identity with workload sign-in and ownership.
- Use SigninLogs filtered by time and failure status, summarized by AppDisplayName.
- Use summarize count() by AppDisplayName followed by sort by count descending.
Explanation
Correct Answer
C:Time filtering and summarize count() produce an app-level failure report.
Incorrect Answers
A:Time binning converts individual provisioning events into daily counts. This matters here because a query must count failed sign-ins per application in the past seven days. What KQL pattern fits.
B:Automated administrators may appear as application principals rather than people. This matters here because a query must count failed sign-ins per application in the past seven days. What KQL pattern fits.
D:Aggregation and sorting reveal which applications drive the most events. This matters here because a query must count failed sign-ins per application in the past seven days. What KQL pattern fits.
Question 691
A team needs to find unusually active administrative changes to user accounts. Which table and aggregation help?
- Query AuditLogs and summarize operations by initiator and target.
- Inspect the current table schema and actual column names before filtering.
- Use summarize count() by AppDisplayName followed by sort by count descending.
- Query AADProvisioningLogs or the current supported provisioning dataset.
Explanation
Correct Answer
A:AuditLogs captures directory actions rather than only user sign-in attempts.
Incorrect Answers
B:KQL queries must match the columns in the selected log table. This matters here because a team needs to find unusually active administrative changes to user accounts. Which table and aggregation help.
C:Aggregation and sorting reveal which applications drive the most events. This matters here because a team needs to find unusually active administrative changes to user accounts. Which table and aggregation help.
D:Provisioning telemetry records actions and failures that can be aggregated by app. This matters here because a team needs to find unusually active administrative changes to user accounts. Which table and aggregation help.
Question 692
A security engineer wants daily provisioning counts by operation type. What KQL structure fits?
- Use SigninLogs filtered by time and failure status, summarized by AppDisplayName.
- Query AuditLogs and summarize operations by initiator and target.
- Summarize AADProvisioningLogs by Action and bin(TimeGenerated, 1d).
- Open the event's Conditional Access details in sign-in logs.
Explanation
Correct Answer
C:Time binning converts individual provisioning events into daily counts. This matters here because a security engineer wants daily provisioning counts by operation type. What KQL structure fits.
Incorrect Answers
A:Time filtering and summarize count() produce an app-level failure report. This matters here because a security engineer wants daily provisioning counts by operation type. What KQL structure fits.
B:AuditLogs captures directory actions instead of only user sign-in attempts.
D:Sign-in diagnostics show applied and nonapplied Conditional Access controls. This matters here because a security engineer wants daily provisioning counts by operation type. What KQL structure fits.
Question 693
A SIEM query returns a column-not-found error for risk status. What should an analyst verify?
- Query SigninLogs with the appropriate risk state or risk level filter.
- Query AuditLogs and summarize operations by initiator and target.
- Inspect the current table schema and actual column names before filtering.
- Use summarize count() by AppDisplayName followed by sort by count descending.
Explanation
Correct Answer
C:KQL queries must match the columns in the selected log table. This matters here because a SIEM query returns a column-not-found error for risk status.
Incorrect Answers
A:Risk fields on sign-in telemetry identify events evaluated as suspicious.
B:AuditLogs captures directory actions rather than only user sign-in attempts. This matters here because a SIEM query returns a column-not-found error for risk status.
D:Aggregation and sorting reveal which applications drive the most events. This matters here because a SIEM query returns a column-not-found error for risk status.
Question 694
A report must show the highest-volume client applications first. What KQL step orders it?
- Use summarize count() by AppDisplayName followed by sort by count descending.
- Inspect the current table schema and actual column names before filtering.
- Inspect managed identity sign-in events where available.
- Use SigninLogs filtered by time and failure status, summarized by AppDisplayName.
Explanation
Correct Answer
A:Aggregation and sorting reveal which applications drive the most events. This matters here because a report must show the highest-volume client applications first. What KQL step orders it.
Incorrect Answers
B:KQL queries must match the columns in the selected log table. This matters here because a report must show the highest-volume client applications first. What KQL step orders it.
C:Managed identity log categories help investigate workload token acquisition. This matters here because a report must show the highest-volume client applications first. What KQL step orders it.
D:Time filtering and summarize count() produce an app-level failure report. This matters here because a report must show the highest-volume client applications first. What KQL step orders it.
Question 695
A team needs to count only risky sign-ins, not all directory audits. Which table and field category matter?
- Query AADProvisioningLogs or the current supported provisioning dataset.
- Query AuditLogs and summarize operations by initiator and target.
- Use SigninLogs filtered by time and failure status, summarized by AppDisplayName.
- Query SigninLogs with the appropriate risk state or risk level filter.
Explanation
Correct Answer
D:Risk fields on sign-in telemetry identify events evaluated as suspicious. This matters here because a team needs to count only risky sign-ins, not all directory audits. Which table and field category matter.
Incorrect Answers
A:Provisioning telemetry records actions and failures that can be aggregated by app. This matters here because a team needs to count only risky sign-ins, not all directory audits. Which table and field category matter.
B:AuditLogs captures directory actions rather than only user sign-in attempts. This matters here because a team needs to count only risky sign-ins, not all directory audits. Which table and field category matter.
C:Time filtering and summarize count() produce an app-level failure report. This matters here because a team needs to count only risky sign-ins, not all directory audits. Which table and field category matter.
Question 696
An identity architect wants a dashboard of user sign-in trends and failures across locations. What Entra tool fits?
- Review Microsoft Entra Identity Secure Score and its improvement actions.
- Configure diagnostic settings to send audit logs to an approved storage account.
- Use Microsoft Entra monitoring workbooks over the configured log data.
- Record the supported alternate-mitigation or third-party resolution status for the improvement action.
Explanation
Correct Answer
C:Workbooks visualize identity telemetry through reusable dashboards. This matters here because an identity architect wants a dashboard of user sign-in trends and failures across locations. What Entra tool fits.
Incorrect Answers
A:Identity Secure Score compares implemented configuration with recommended controls.
B:Storage sinks support governed retention for exported identity audit events. This matters here because an identity architect wants a dashboard of user sign-in trends and failures across locations. What Entra tool fits.
D:Recommendations can account for equivalent mitigations under the provided reporting workflow.
Question 697
A security lead wants actionable recommendations for improving tenant identity posture. Which assessment fits?
- Record the supported alternate-mitigation or third-party resolution status for the improvement action.
- Review Microsoft Entra Identity Secure Score and its improvement actions.
- Use Microsoft Entra monitoring workbooks over the configured log data.
- Filter AuditLogs by role management operations and target object.
Explanation
Correct Answer
B:Identity Secure Score compares implemented configuration with recommended controls. This matters here because a security lead wants actionable recommendations for improving tenant identity posture. Which assessment fits.
Incorrect Answers
A:Recommendations can account for equivalent mitigations under the provided reporting workflow. This matters here because a security lead wants actionable recommendations for improving tenant identity posture. Which assessment fits.
C:Workbooks visualize identity telemetry through reusable dashboards. This matters here because a security lead wants actionable recommendations for improving tenant identity posture. Which assessment fits.
D:Audit entries link role updates to actors and timestamps. This matters here because a security lead wants actionable recommendations for improving tenant identity posture. Which assessment fits.
Question 698
A score improves after a policy change, but leadership assumes no security risk remains. What caution is necessary?
- Query AuditLogs and summarize operations by initiator and target.
- Treat Identity Secure Score as a control-adoption indicator, not a breach probability.
- Record the supported alternate-mitigation or third-party resolution status for the improvement action.
- Use Microsoft Entra monitoring workbooks over the configured log data.
Explanation
Correct Answer
B:A higher score cannot guarantee protection against every attack. This matters here because a score improves after a policy change, but leadership assumes no security risk remains. What caution is necessary.
Incorrect Answers
A:AuditLogs captures directory actions rather than only user sign-in attempts. This matters here because a score improves after a policy change, but leadership assumes no security risk remains. What caution is necessary.
C:Recommendations can account for equivalent mitigations under the provided reporting workflow. This matters here because a score improves after a policy change, but leadership assumes no security risk remains. What caution is necessary.
D:Workbooks visualize identity telemetry through reusable dashboards. This alternative addresses an identity architect wants a dashboard of user sign-in trends and failures across locations. What Entra tool fits? It does not meet the specified case, which requires treat identity secure score as a control-adoption indicator, not a breach probability: A higher score cannot guarantee protection against every attack.
Question 699
An organization resolved a recommendation with a third-party control but the score doesn't reflect it. What workflow exists?
- Review Microsoft Entra Identity Secure Score and its improvement actions.
- Treat Identity Secure Score as a control-adoption indicator, not a breach probability.
- Record the supported alternate-mitigation or third-party resolution status for the improvement action.
- Review the license-dependent log retention period and any configured export.
Explanation
Correct Answer
C:Recommendations can account for equivalent mitigations under the provided reporting workflow. This matters here because an organization resolved a recommendation with a third-party control but the score doesn't reflect it. What workflow….
Incorrect Answers
A:Identity Secure Score compares implemented configuration with recommended controls. This matters here because an organization resolved a recommendation with a third-party control but the score doesn't reflect it. What workflow….
B:A higher score cannot guarantee protection against every attack. This matters here because an organization resolved a recommendation with a third-party control but the score doesn't reflect it. What workflow….
D:Portal log availability depends on retention and destination configuration. This matters here because an organization resolved a recommendation with a third-party control but the score doesn't reflect it. What workflow….
Question 700
A tenant wants to compare identity posture before and after a rollout. Which historical evidence helps?
- Select the AuditLogs category specifically in diagnostic settings.
- Review Identity Secure Score history and linked recommendation changes.
- Record the supported alternate-mitigation or third-party resolution status for the improvement action.
- Use Microsoft Entra monitoring workbooks over the configured log data.
Explanation
Correct Answer
B:Score history supports trend assessment over time instead of one snapshot. This matters here because a tenant wants to compare identity posture before and after a rollout. Which historical evidence helps.
Incorrect Answers
A:Diagnostic settings can independently select supported identity log categories. This matters here because a tenant wants to compare identity posture before and after a rollout. Which historical evidence helps.
C:Recommendations can account for equivalent mitigations under the provided reporting workflow. This matters here because a tenant wants to compare identity posture before and after a rollout. Which historical evidence helps.
D:Workbooks visualize identity telemetry through reusable dashboards. This matters here because a tenant wants to compare identity posture before and after a rollout. Which historical evidence helps.