Microsoft SC-500 Cloud and AI Security Engineer 1-10

表示モード
画像位置
文字位置
理解度の自動記録
STATUS FILTER

Choose confidence levels to display

Loading...
Q1SC-500
Scope of auditing

Destination for audit logs

Show answer
Correct answer: Enable it on each server or instance / Log Analytics workspace

When auditing is enabled at the server or instance level, the audit settings are applied collectively to all databases beneath it, so there is no need to repeat individual configuration as databases are added later, which keeps the management burden low.
In addition, when the audit logs are sent to a Log Analytics workspace, audit data from multiple resources can be stored centrally and searched and analyzed with KQL in Azure Monitor Logs.
Event Hubs is well suited to streaming to external systems, but it is not a destination for analyzing directly with KQL.
A Storage account is well suited to long-term retention, but Log Analytics is the best fit for the requirement of centralized analysis with KQL.
Auditing policy at the server and database levels
Set up auditing for Azure SQL Database and Azure Synapse Analytics

Q2SC-500
Show answer
Correct answer: A. Content filtering and safety evaluation

Content filtering is a capability that analyzes the input to the AI and the generated output to detect or block harmful content such as violence, sexual content, self-harm, and hate.
In addition, safety evaluation lets you continuously measure the degree of harmfulness and policy violations in the responses of a generative AI application.
Increasing the context window relates to the amount of information that can be processed, adding GPUs relates to performance, and virtual networks relate to isolating and protecting communications, but none of these directly assess the safety of the generated content itself.
With Microsoft, you can use Azure AI Content Safety to detect harmfulness in user-generated and AI-generated content.
What is Azure AI Content Safety?
Risk and safety evaluators

Q3SC-500
Show answer
Correct answer: C. Validate input and restrict access to tools.

Prompt injection is an attack that uses malicious input to manipulate the model’s instructions and behavior, causing it to misuse connected data and tools.
Therefore, it is important not to trust external input and to detect malicious instructions with validation and capabilities such as Prompt Shields.
Furthermore, in case an attack slips past detection, limiting the tools the AI can call and their execution permissions to the minimum necessary reduces the impact.
Disabling logging reduces investigative capability, and trusting responses unconditionally is dangerous.
The temperature parameter adjusts the diversity of the output and is not a countermeasure against attacks.
Prompt Shields
Artificial intelligence security

Q4SC-500
Show answer
Correct answer: A. A playbook

A Microsoft Sentinel playbook is an automated workflow built on Azure Logic Apps.
Triggered by a new incident, it can call the API of an external ITSM system or an available Logic Apps connector to automatically create a service ticket.
Even if there is no packaged Microsoft Sentinel solution for the target ITSM product, integration is possible as a custom workflow.
In practice, you also configure an automation rule that runs the playbook when an incident is created.
A workbook is for visualization, a watchlist is for managing reference data, and an analytics rule is a capability for detecting threats and generating alerts and incidents, so they are not suited to creating tickets in an external system.
Automate threat response with playbooks in Microsoft Sentinel
Azure Logic Apps for Microsoft Sentinel playbooks

Q5SC-500

Drag each option to the matching requirement’s drop zone, or tap to place it. Click a filled zone to send it back. (The same option may be used more than once.)

Require assignment to the enterprise application
IP access restrictions
Local authentication
Microsoft identity provider
Role-based access control (RBAC) assignment
Tenant-wide admin consent
Authentication method
Access control method
Show answer
Correct answer: Authentication method -> Microsoft identity provider / Access control method -> Require assignment to the enterprise application

For App2, configure the Microsoft identity provider as the identity provider for built-in authentication, and authenticate users with Microsoft Entra ID.
In addition, when you set “Assignment required?” to Yes on the corresponding enterprise application, only explicitly assigned users or groups can sign in and obtain an access token.
IP access restrictions is a capability that controls the source network of connections, and it does not control whether individual users or groups can use the app.
RBAC is a mechanism for granting management permissions on Azure resources, and it does not apply to controlling app usage as required here.
Authentication and authorization in Azure App Service and Azure Functions
Restrict a Microsoft Entra app to a set of users

Q6SC-500
Show answer
Correct answer: D. Owners only at tenant scope

When you set the users who can manage tenant-scope custom plugins to owners only, contributors can no longer add or manage plugins used across the organization.
Meanwhile, the user-scope setting is not changed, so contributors can continue to create and manage custom plugins for use in their own sessions.
Option B restricts even user-scope permissions, which violates the requirement.
Option A continues to allow contributors to manage plugins organization-wide, and option C specifies only user scope, so it cannot restrict tenant-wide management permissions.
In official Microsoft documentation, the product name Microsoft Security Copilot is still in use.
Manage plugins in Microsoft Security Copilot
Manage plugins and agents in Microsoft Security Copilot

Q7SC-500
Ports exposed on the public IP address of CG1

Network endpoint for App1

Show answer
Correct answer: Port 443 only / Port 5000 on localhost

To prevent external clients from connecting to port 5000, expose only port 443 on the public IP address of the container group.
Containers within the same Azure Container Instances container group share the same host and network namespace, so they can communicate with each other over localhost even on ports that are not exposed externally.
Therefore, specify localhost:5000 as the endpoint for App1 to connect to container2.
Using cg1.contoso.com:5000 would require exposing the port on the public side, which fails to meet the requirement of preventing external access.
Azure Container Instances is still the official service name.
Container groups in Azure Container Instances
Tutorial: Deploy a multi-container group using a Resource Manager template

Q8SC-500
Show answer
Correct answer: B. Role-based access control (RBAC) roles

With Azure RBAC, you can assign to users, groups, service principals, and others only the permissions needed, by specifying resources and scopes.
Therefore, granting the minimum built-in or custom role that corresponds to the developer’s work achieves least privilege.
Azure Policy exclusions define what is excluded from policy enforcement, and are not a mechanism for granting access rights.
Resource locks prevent accidental deletion or changes, and management groups hierarchically organize subscriptions, but neither controls individual access permissions.
Note that the latest Microsoft Learn uses Microsoft Foundry as the name of a related platform, and Azure RBAC continues to be used for individual access management to Azure OpenAI.
Role-based access control for Azure OpenAI Service
Azure built-in roles

Q9SC-500
Show answer
Correct answer: B. Privileged Identity Management (PIM)

With Microsoft Entra Privileged Identity Management (PIM), you can register administrators as eligible users for Azure roles and have them activate a role for a limited period only when needed.
The main benefit is that it reduces standing privileges and grants access rights Just-In-Time for only the time needed.
Also, at activation you can require multifactor authentication, approval, and a justification to strictly control the use of privileges.
Dynamic groups are for attribute-based membership management, access packages are for requesting access to resources and lifecycle management, and self-service password reset is for account recovery, so they are not suited to this requirement.
The product name is still Microsoft Entra Privileged Identity Management.
What is Microsoft Entra Privileged Identity Management?
Eligible and time-bound role assignments in Azure RBAC

Q10SC-500
Show answer
Correct answer: D. Assign the Storage File Data Privileged Reader role to the managed identity of App1.

For App1 to read Azure Files without holding an access key, use the managed identity as a security principal in Microsoft Entra ID and grant an Azure RBAC data access role.
Assigning the Storage File Data Privileged Reader role to the managed identity of App1 enables read access using OAuth.
Option A continues to use keys, and option B only disables key authentication without granting permissions.
Option C is a setting that changes the default authentication method in the Azure portal, and it does not grant App1 access rights.
Note that the current name of Azure AD is Microsoft Entra ID.
Assign share-level permissions to an Azure file share