SC-500 Exam Dumps - Microsoft Certified: Cloud and AI Security Engineer Associate

The protected resource is Azure Database for PostgreSQL, which is an open-source relational database service. Microsoft Defender for Open-Source Relational Databases is scoped to PostgreSQL and MySQL style services, so it satisfies the requirement without enabling broader plans. Defender for Azure SQL Databases applies to Azure SQL, Defender for SQL Servers on Machines applies to SQL Server on VMs or Arc-enabled machines, and Defender for Servers or Storage would charge for unrelated workloads. Microsoft platform security questions usually hinge on where enforcement occurs: at the resource, server, subnet, firewall policy, private endpoint, or subscription level. The selected answer uses the control plane that owns that enforcement point. Other options are rejected when they only log activity, broaden network access, or protect a different service category. 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 Databases; Microsoft Learn > Defender for open-source relational databases.

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

The security team needs impact and lateral-movement exposure for an abused service principal. Defender XDR attack paths show the identity blast radius by connecting permissions, exposed resources, and reachable assets. Advanced hunting and audit logs can provide raw evidence, but they require more manual analysis. AI Observability and incident review do not directly answer which resources are affected by identity abuse across the environment. 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 > analyze blast radius by using Defender XDR; Microsoft Learn > attack paths for identity risk.

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

Exposed ports on the public IP address of CG1: 443 only; Network endpoint for App1: localhost:5000

In an Azure Container Instances group with a public IP address, only the ports exposed on the container group public endpoint are reachable externally. The public exposed port should therefore be limited to 443. Containers inside the same container group can communicate with one another over localhost, so App1 can continue to reach container2 at localhost:5000 without exposing port 5000 publicly. 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 > Azure Container Instances security; Microsoft Learn > container group exposed ports and localhost communication.

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

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.

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

The first step is to create a custom log table in Workspace1 . Microsoft Sentinel uses the underlying Log Analytics workspace as its data platform. When ingesting security events that have a custom JSON schema, the destination table must exist so Azure Monitor can map and store the incoming fields correctly. Microsoft documentation for custom tables explicitly states that custom schemas are used for data that does not fit predefined Azure tables, and the table is created before configuring the collection flow that sends records to it.

For modern custom ingestion, a Data Collection Rule (DCR) defines how incoming records are collected, optionally transformed, and routed to the custom table. Microsoft also documents that a custom table receiving JSON data must exist before the corresponding DCR is created in applicable collection scenarios.

A diagnostic setting is intended primarily for supported Azure resource platform logs and is not the prerequisite for ingesting arbitrary SaaS JSON events. A built-in Sentinel connector would contradict the requirement to build a custom connector . An analytics rule is configured only after data is being ingested because it queries stored events to detect suspicious activity.

Therefore, preparing the workspace begins by defining the custom log table and schema that will receive the SaaS security data.

Assign Virtual Machine User Login to User1. Microsoft Entra authentication for supported Azure Arc-enabled Windows servers uses Azure RBAC to authorize RDP sign-in. Microsoft specifies two relevant roles: Virtual Machine Administrator Login , which provides administrator privileges, and Virtual Machine User Login , which provides standard user privileges. Because the requirement is only for User1 to sign in and explicitly requires least privilege , Virtual Machine User Login is the correct role.

Assigning Virtual Machine Administrator Login would also permit access, but it unnecessarily grants local administrative privileges and therefore violates least privilege. Adding User1 manually to the local Remote Desktop Users group is not the correct authorization model for Microsoft Entra-based Arc sign-in. Microsoft specifically requires the appropriate Azure login role and documents that manual local-group elevation is not the supported mechanism for authorizing Microsoft Entra sign-in.

A Conditional Access policy requiring MFA can impose an additional authentication condition, but it does not provide the underlying authorization required to log on to SRV1.

The SC-500 study guide places extending security controls to hybrid servers by using Azure Arc within the Secure compute domain.

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