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

To use Microsoft Authenticator as a primary authentication method , Group1 must be enabled for passwordless authentication . Passwordless phone sign-in allows users to authenticate directly by using Microsoft Authenticator instead of first supplying a password. Microsoft describes Authenticator passwordless sign-in as a primary sign-in method in which the user approves a number challenge and then completes biometric or PIN verification on the registered device.

The Microsoft Entra Authentication methods policy supports targeting specific users and groups and controlling whether they can use Authenticator for push MFA, passwordless authentication, or both . Enabling the passwordless mode for Group1 therefore directly meets the stated requirement.

Push authentication is primarily used as an MFA verification mechanism and does not by itself make Authenticator the user ' s primary authentication method. One-time passcodes are also verification codes used for MFA scenarios rather than passwordless primary sign-in. Revoking sessions simply forces users to authenticate again and does not enable a new authentication method.

The SC-500 study guide explicitly includes implementing and configuring authentication methods, including MFA and passwordless authentication , under the Manage identity, access, and governance domain.

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

To customize the baseline: Use Azure Machine Configuration; Set enforcement mode to: Apply and Autocorrect

Azure Machine Configuration is the correct mechanism for applying and customizing guest configuration baselines across Azure VMs and Azure Arc-enabled servers. It integrates with Azure Policy and can enforce configuration through assignment modes such as Apply and Autocorrect. This provides centralized compliance and automatic correction without building a separate configuration-management pipeline for Windows and Linux servers. The compute domain tests whether protection is applied before deployment, during runtime, or through posture assessment. The selected answer matches the phase described in the requirement. Detection-only tools are not acceptable when the requirement says prevent, and local installation methods are inferior when Defender for Cloud, Azure Policy, or Azure Machine Configuration can enforce the control centrally. 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 > Azure Machine Configuration; Microsoft Learn > assignment modes and remediation.

Microsoft Entra-only authentication at the logical server level disables SQL authentication for all databases on that server while leaving existing SQL principals in place. That matches the requirement to deny SQL authentication without removing legacy logins. Creating external-provider users adds Entra users; it does not block SQL logins. Conditional Access can govern Entra sign-ins but cannot disable SQL authentication. SQL Server Contributor is an Azure management role, not an authentication mode. The exam objective emphasizes practical identity enforcement rather than cosmetic configuration. A valid answer must identify who authenticates, what permission is granted, where the scope is applied, and whether the method continues to work without passwords or secrets. That is why the selected answer is preferred over broader administrative roles or unrelated access settings. 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 > Azure SQL platform security; Microsoft Learn > Microsoft Entra-only authentication.

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

A private endpoint is the appropriate mechanism because it exposes the Azure Storage service through a private IP address associated with Subnet1 . Private endpoints support Azure virtual network network policies, including network security groups (NSGs) . When private-endpoint network policies are enabled for the subnet, NSG rules can be applied to traffic destined for the private endpoint, allowing network access to be controlled through the NSG associated with Subnet1.

This differs materially from a service endpoint . Service endpoints continue to access Azure Storage through its public service endpoint and require service-side virtual network ACL/firewall configuration to restrict which subnets may access the storage account. Microsoft explicitly states that enabling a service endpoint alone is insufficient: the Azure service must also be configured with appropriate virtual-network access controls. Therefore, access would not be governed only by the NSG.

An Azure Private Link service is used to privately publish a customer-owned service, typically behind a load balancer; it is not required to consume Azure Storage privately. A UDR controls routing and does not establish private access to Storage.

For a complete private-access design, the storage account ' s public endpoint should also be restricted or disabled. Microsoft recommends private endpoints when private network access to Azure Storage is required.

Agent1: Delegated permissions; Agent2: Application permissions

Agent1 is interactive and acts for a signed-in user against that user’s mailbox, so delegated permissions are appropriate. Agent2 operates autonomously without a signed-in user; application permissions are the app-only model for Microsoft Graph access in that operating mode. Exchange Online permissions and Teams RSC can be valid in narrow service-specific designs, but the answer area asks for the general permission type aligned to interactive versus autonomous agents. The exam objective emphasizes practical identity enforcement rather than cosmetic configuration. A valid answer must identify who authenticates, what permission is granted, where the scope is applied, and whether the method continues to work without passwords or secrets. That is why the selected answer is preferred over broader administrative roles or unrelated access settings. 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 Entra Agent ID access; Microsoft Learn > delegated vs application permissions.

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

Virtual machine type

Plan

Windows Server

Microsoft Defender for Servers

Linux

Microsoft Defender for Servers

Microsoft Defender for Servers is the correct plan for both the Windows Server and Linux virtual machines because the requirement is to provide malware protection at the virtual-machine operating-system level . Defender for Servers protects both Windows and Linux VMs and integrates with Microsoft Defender for Endpoint to provide endpoint protection, including antimalware capabilities. Microsoft states that Defender for Servers supports Windows and Linux virtual machines across Azure and other supported environments.

For Linux systems, Defender for Servers deploys the Defender for Endpoint component that includes antimalware functionality. For Windows Server, Defender Antivirus is integrated with Defender for Endpoint and provides malware protection. In addition, Defender for Servers Plan 2 supports agentless malware scanning , which scans VM disks for malicious files without installing an additional scanning agent.

The fact that the Linux machines host databases does not make Microsoft Defender for Databases the correct answer. Defender for Databases protects supported database workloads against database-specific threats; it does not replace VM-level malware protection.

The SC-500 study guide places onboarding and configuring VMs with Defender for Servers under the Secure compute objective.

Defender for Storage malware scanning publishes scan result events that can be consumed by automation services. Azure Event Grid is the native event routing mechanism for storage and Defender for Storage scan outcomes, so it is the right trigger for remediation such as quarantine, delete, notification, or workflow invocation. Application Insights observes application telemetry, Event Hubs is mainly a streaming pipeline, and Azure Policy governs configuration compliance rather than reacting to individual malicious-file detections. 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 for Storage threat protection; Microsoft Learn > Malware scanning in Defender for Storage events.

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