Pass the Microsoft Certified: Information Security Administrator Associate SC-500 Questions and answers with Dumpstech

User Access Administrator is the least-privilege Azure built-in role for managing role assignments without full resource ownership. Assigning it at the MG1 scope covers both Sub1 and Sub2 because management group scope flows down to child subscriptions. Contributor cannot assign Azure roles. Owner would work but grants more than role-assignment authority, violating least privilege. Assigning separately at each subscription adds unnecessary administration. For SC-500, the decisive distinction is whether the control authenticates an identity, grants authorization, or merely changes configuration visibility. The incorrect choices generally either grant excessive privilege, change the application model, or operate at the wrong scope. Microsoft expects the least-privilege identity path that satisfies the scenario without introducing shared secrets or unnecessary tenant-wide rights. 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 > manage Azure built-in role assignments; Microsoft Learn > User Access Administrator role.

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

Approval before elevation is implemented by requiring approval to activate the PIM role. Automatic removal after a fixed active period is controlled by the activation maximum duration. Expiring active or eligible assignments governs the assignment lifecycle, not the duration of each activation session. Requiring justification can improve audit quality, but it does not ensure that another administrator evaluates the request or that access ends after the configured active window. This domain is tested through precise scope control: tenant, subscription, resource, application, and data-plane authorization are not interchangeable. The correct choice applies the smallest identity or governance control that enforces the stated requirement. Options that only add users, create registrations, or provide broad administrator access fail because they do not directly enforce the requested access behavior. 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 > Privileged Identity Management; Microsoft Learn > configure role activation settings.

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

Use Azure Logic Apps to automate remediation actions when Defender for Storage detects malicious content. Microsoft documents an event-driven remediation pattern in which Defender for Storage malware scanning sends scan results through Azure Event Grid , and an Azure Logic App or Azure Function performs an automated response such as quarantining, deleting, moving, or otherwise handling a malicious blob . This enables near-real-time remediation rather than simply recording or reporting the detection.

A Log Analytics workspace is useful for retaining malware scan results for audit, compliance, and investigation, but it does not itself execute remediation actions. An alert rule can generate notifications based on detected conditions, but it is not the primary workflow engine for taking corrective action against infected blobs. Azure Policy can enforce Defender for Storage configuration at scale, such as ensuring malware scanning is enabled across storage accounts, but it does not perform per-detection malware remediation.

Therefore, the solution should include Azure Logic Apps , typically triggered through Event Grid, to implement the required automated response.

This aligns with the SC-500 objective Implement Defender for Storage threat protection configurations under Secure storage, databases, and networking.

The user can already sign in to Security Copilot, so the missing permission is not a Security Copilot role. The Sentinel plugin retrieves incidents from the Sentinel workspace and therefore requires the appropriate Microsoft Sentinel data-plane role. Microsoft Sentinel Reader at the Workspace1 scope is the least-privilege role for viewing incidents. Security Administrator, Azure Contributor, or Security Copilot Owner would grant broader permissions than required. 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 > Security Copilot plugins and Sentinel roles; Microsoft Learn > Microsoft Sentinel Reader role.

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

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.