Microsoft Updated SC-500 Exam Questions and Answers by herbert

Inventory cleanup: Remove the seed and remove the assets discovered by using that seed; Finding suppression: Mark the observations as non-applicable

When a seed domain is no longer owned, the clean inventory action is to remove the seed and remove assets discovered from that seed. Leaving those assets as dependencies or merely labeling them would keep stale assets in the inventory. For findings that do not apply to confirmed inventory, marking the observations as non-applicable prevents them from influencing finding counts while retaining the operational history needed for audit and review. For this domain, least privilege means granting only the required data operation or allowing only the required network flow. The correct response avoids shared keys, broad peering, general contributor roles, or log-only controls when the scenario demands prevention, routing, event triggering, or account-specific configuration. The result is a direct exam-style implementation choice: it changes the required security behavior without relying on unrelated monitoring, manual cleanup, or excessive privilege. Official Microsoft source/topic: SC-500 Study Guide > Defender EASM; Microsoft Learn > inventory and observation state management.

==============================================================

Defender CSPM identifies secrets such as plaintext connection strings and SSH keys on machines through agentless machine scanning. If those secrets are not being identified, the missing capability is the agentless scan feature. The Sentinel data connector only forwards alerts and posture data, the Azure Monitor Agent collects telemetry, and Defender for Key Vault protects vault access; none of those scan VM disks for exposed secrets. The posture and monitoring objective focuses on turning security data into usable operational outcomes. The correct answer either collects the right signal, grants the right security-operations role, or automates incident handling at the correct layer. Distractors often provide dashboards, queries, or broad permissions, but those do not create the requested workflow or least-privilege security capability. The result is a direct exam-style implementation choice: it changes the required security behavior without relying on unrelated monitoring, manual cleanup, or excessive privilege. Official Microsoft source/topic: SC-500 Study Guide > scan for secrets by Defender CSPM; Microsoft Learn > agentless scanning for machines.

==============================================================

Statement

Answer

A container in the storage account can be configured for anonymous read access.

No

A resource in the subnet specified by subnetResourceId can access the storage account.

Yes

A client connection that originates from an unlisted public IP address and uses TLS 1.2 can access the storage account.

No

The first statement is No because allowBlobPublicAccess: false disables anonymous blob access at the storage-account level . Microsoft states that this setting overrides container-level configuration, so an individual container cannot subsequently be configured to permit anonymous read access.

The second statement is Yes . The networkAcls configuration sets defaultAction: ' Deny ' , but the virtualNetworkRules collection explicitly includes the subnet represented by subnetResourceId. A virtual network rule is an Allow rule for the referenced subnet, so resources using that authorized subnet path can reach the storage account while other networks remain blocked. Microsoft documents that access can be restricted to specifically authorized virtual-network subnets.

The third statement is No . minimumTlsVersion: ' TLS1_2 ' only establishes the minimum acceptable TLS protocol; it does not bypass network ACLs. Because the source public IP is not listed and defaultAction is Deny, the connection is blocked even though it uses TLS 1.2. The AzureServices bypass applies only to eligible trusted Azure services, not arbitrary public clients.

This directly maps to the SC-500 objective Implement security for storage accounts , including Azure Storage firewall rules and access controls.