SC-500
Free SC-500 practice questions
10 questions from our SC-500 practice tests, each with the correct answer and a written explanation. Read them with the answers shown, or switch to quiz mode and answer first.
Question 1 of 10, Manage identity, access, and governance
Platform engineers need Owner on the Production subscription only while they fix incidents. Requirements: no standing access, activation must last no longer than four hours, and each activation must include a justification and a ticket number. What should you do?
- AAdd the engineers to a group with a permanent Owner assignment and use a Conditional Access policy with a four-hour sign-in frequency on the Azure management app
- BCreate an eligible PIM assignment for Owner on the subscription, then set maximum activation duration to four hours and require justification and ticket information Correct answer
- CCreate a custom role that copies Owner permissions, assign it at the subscription scope, and apply an Azure Policy assignment that audits changes made outside business hours
- DAssign the engineers Owner as an active time-bound assignment in Azure RBAC that expires after four hours and is renewed by the service desk for each new incident
Answer and explanation: PIM for Azure resources supports eligible assignments with role settings for maximum activation duration, required justification and required ticket information, which meets every requirement. Manually renewed time-bound active assignments still create periods of standing access and add service desk overhead. A sign-in frequency only forces reauthentication; the permanent Owner assignment remains standing access. A copied custom role is still a standing assignment, and an audit policy does not limit when the permissions can be used.
Question 2 of 10, Manage identity, access, and governance
Investigation shows an unknown multitenant app was granted delegated Mail.Read and Files.Read.All by 40 users through user consent. You must stop the app from accessing data immediately while keeping evidence for the investigation. What should you do first?
- ADisable sign-in for the app's enterprise application by setting Enabled for users to sign-in to No and revoke its grants Correct answer
- BDelete the app registration from your tenant so that the client secret becomes invalid and all issued access tokens stop working
- CBlock the 40 users with a Conditional Access policy until each of them resets the password and re-registers MFA methods
- DAdd the application's publisher domain to the tenant's blocked senders list in Exchange Online Protection settings
Answer and explanation: The malicious multitenant app is represented locally by a service principal; disabling sign-in for it stops new tokens and revoking its delegated grants removes consented access, while the object and audit trail remain for investigation. There is no app registration in your tenant for another tenant's app, and its secret lives in the attacker's tenant. Blocking the users disrupts them while the app keeps any already-issued refresh capability through other consenting users. Email blocking does not affect OAuth token issuance.
Question 3 of 10, Manage identity, access, and governance. Choose 2.
A recent review shows that 14 users hold Owner on the Finance subscription even though most only deploy resources. You need to reduce overprivileged access with Azure RBAC and keep it reduced. Which two actions should you take? (Choose two.)
- AAssign the deployers the User Access Administrator role so they can grant themselves Contributor whenever required
- BConvert remaining Owner assignments to eligible assignments in PIM and schedule recurring access reviews for the role Correct answer
- CApply a CanNotDelete lock to the Finance subscription so that Owner holders cannot remove role assignments
- DReplace the Owner assignments for deployers with Contributor or a narrower built-in role at the resource group scope Correct answer
- ECreate a classic co-administrator assignment for each deployer to separate service management from Azure RBAC
Answer and explanation: Downgrading deployers to Contributor or a narrower role at a smaller scope removes unneeded privileges, and moving the remaining Owners to eligible PIM assignments with recurring access reviews prevents standing privilege from creeping back. User Access Administrator lets users grant themselves roles, which increases risk. A CanNotDelete lock protects resources from deletion but does not reduce the permissions owners hold. Classic administrator roles are retired and do not provide least privilege.
Question 4 of 10, Secure storage, databases, and networking
A storage account's firewall allows only selected virtual networks. A specific Azure Synapse Analytics workspace in another subscription must read data through its managed identity, but you must not allow every Azure service in the tenant. What should you configure?
- AAn IP network rule containing the public IP ranges of the Synapse service tag for that Azure region
- BA resource instance rule in the storage firewall that names the Synapse workspace's resource ID and tenant Correct answer
- CA virtual network rule for the managed virtual network of the Synapse workspace, using a service endpoint
- DThe exception Allow Azure services on the trusted services list to access this storage account in the networking blade
Answer and explanation: Resource instance rules allow a specific Azure resource instance, identified by resource ID, to reach the account through its managed identity even when the firewall is restrictive. The trusted services exception is broader, allowing all instances of trusted services in the tenant. Synapse managed virtual networks are not customer VNets that you can add as service endpoint rules. Service tag IP ranges are shared by all customers of the service and are not usable as storage IP rules for Azure services.
Question 5 of 10, Secure storage, databases, and networking
Storage accounts hold files with credit card numbers. The SOC wants Defender for Storage alerts on accounts with sensitive data to be prioritized, and to see sensitivity context in each alert. Which Defender for Storage feature should you enable?
- ABlob versioning together with change feed, so investigators can see which versions contained card numbers
- BMicrosoft Purview sensitivity labels in the storage account, which apply encryption to files with card numbers
- CSensitive data threat detection, which uses data discovery to add sensitivity context to alerts and attack paths Correct answer
- DActivity monitoring with default anomaly detection, which already classifies files by their content during every read
Answer and explanation: Sensitive data threat detection in Defender for Storage discovers sensitive information types in the account and enriches alerts with that context so the SOC can prioritize them. Basic activity monitoring detects anomalies but does not classify content. Versioning and change feed provide history, not sensitivity classification. Sensitivity labels are applied to documents in Microsoft 365 workloads and do not provide threat detection context for storage alerts.
Question 6 of 10, Secure storage, databases, and networking
You must send audit events from an Azure SQL Managed Instance to a Log Analytics workspace so the SOC can query them alongside other logs. Which configuration achieves this?
- AEnable server-level auditing on the managed instance in the portal with Log Analytics as the target, in the same way as SQL Database
- BEnable Defender for SQL on the instance, which forwards audit records to the workspace selected for Defender for Cloud
- CCreate a server audit TO URL that points to a storage account, then connect that storage account to the workspace
- DCreate a diagnostic setting for SQLSecurityAuditEvents to the workspace, then create a server audit TO EXTERNAL_MONITOR Correct answer
Answer and explanation: For SQL Managed Instance, audit logs reach Log Analytics through a diagnostic setting for the SQLSecurityAuditEvents category combined with a server audit created with T-SQL that targets EXTERNAL_MONITOR, plus a server audit specification. Defender for SQL does not forward audit records. The SQL Database server-level auditing blade does not apply to managed instances in the same way. An audit TO URL writes files to storage, which Log Analytics cannot ingest just by connecting the account.
Question 7 of 10, Secure compute
The CISO asks which users are pasting sensitive information such as customer account numbers into Microsoft 365 Copilot and into consumer generative AI websites, and wants recommended policies to reduce the risk. Which Microsoft Purview capability should you start with?
- AMicrosoft Purview Information Barriers between the departments that handle customer account numbers
- BMicrosoft Purview eDiscovery (Premium) with a case that holds all mailboxes containing Copilot interactions
- CData Security Posture Management for AI in Microsoft Purview, using its reports and one-click policies Correct answer
- DMicrosoft Purview Communication Compliance with a policy that detects offensive language in Teams chats
Answer and explanation: DSPM for AI in Microsoft Purview surfaces sensitive data in prompts and responses for Copilot and third-party AI apps, shows which users are involved, and offers recommended one-click policies such as DLP and Insider Risk Management. Communication Compliance can review messages but the described policy targets offensive language. eDiscovery preserves and searches content for legal matters rather than assessing AI risk. Information Barriers restrict communication between groups and do not monitor AI usage.
Question 8 of 10, Secure compute
A legal department site is correctly permissioned for 200 lawyers, but leadership does not want its documents surfaced in Microsoft 365 Copilot responses or organization-wide search for anyone who has not visited the site. Lawyers must keep normal access. What should you configure?
- ARestricted Content Discovery on the site, which keeps permissions but excludes the content from Copilot and org-wide search Correct answer
- BRestricted SharePoint Search for the tenant, with an allowed list of up to 100 sites that does not include the legal department site
- CRemove the lawyers from the site and grant access only through sharing links that expire after one day
- DApply a retention label to every document so that Copilot ignores files subject to a retention policy for legal hold
Answer and explanation: Restricted Content Discovery is a site-level setting that stops the site's content from being surfaced by Copilot and organization-wide search while leaving permissions unchanged, so lawyers keep working normally. Expiring links disrupt legitimate access. Retention labels govern retention and deletion, not Copilot grounding. Restricted SharePoint Search is a tenant-wide temporary allow list that limits search to curated sites for everyone, which is far broader than needed.
Question 9 of 10, Manage and monitor security posture
By default, too many users can run prompts in Security Copilot. Security wants only members of the SOC-Analysts group to use it, and only the security leads to change settings and plugins. How should you configure roles?
- ARemove Everyone from the Copilot contributor role, add SOC-Analysts as contributors and security leads as owners Correct answer
- BCreate a Conditional Access policy that blocks Security Copilot for everyone except the SOC-Analysts group
- CAssign SOC-Analysts the Security Reader role in Microsoft Entra ID, which is the only role Copilot checks
- DAssign SOC-Analysts the Copilot owner role and remove the Global Administrators from all of the Security Copilot roles
Answer and explanation: Security Copilot uses Copilot owner and Copilot contributor roles; by default Everyone may be a contributor, so you remove it, add the SOC group as contributors and make the leads owners. Making analysts owners grants them settings control. Entra Security Reader is not the only role that matters, and contributors also need access to the underlying data through their own roles. Conditional Access governs sign-in conditions, not Copilot role-based permissions.
Question 10 of 10, Manage and monitor security posture
A test subscription produces thousands of low-severity vulnerability findings from Defender Vulnerability Management that the team has accepted as risk. Those findings must not affect secure score, while high and critical findings must still appear. What should you configure?
- AA suppression rule for all Defender for Servers alerts generated on the test subscription's VMs
- BA rule to disable specific vulnerability findings, filtered on severity Low for the test subscription Correct answer
- CAn Azure Policy exemption for the whole subscription with the waiver category for all recommendations
- DRemove the Defender for Servers plan from the test subscription so that no findings of any severity are generated
Answer and explanation: Defender for Cloud lets you create rules that disable vulnerability findings by criteria such as severity or CVE, so the accepted low-severity findings stop affecting the recommendation and secure score while others remain. A subscription-wide policy exemption would hide every recommendation. Alert suppression rules apply to security alerts, not vulnerability findings. Removing the plan eliminates all vulnerability coverage, including high and critical.