Free SC-500 Exam Braindumps
Implementing End-to-End Security Controls for Cloud and AI Workloads Questions 1–3 (page: 15)

Updated On: 23-Oct-2026
View Related Case Study

You need to implement the planned changes for sql1.
Which storage accounts can you use?

  1. storage1 only
  2. storage3 only
  3. storage1 and storage3 only
  4. storage2, storage3, and storage4 only
  5. storage1, storage2, storage3, and storage4

Answer(s): A

Explanation:

Scenario:
Planned changes: Configure auditing for sql1 by using the Azure portal and store audit logs in a centralized location.
Sql1 is an Azure SQL server in the West US region
Storage1 is Standard account in West US.
Storage2 is Block blobs Premium account in East US.
Storage3 is File shares Premium account in East US.
Storage4 is Page blobs Premium account in East US.
--
Auditing can be configured only on Storage1.Azure SQL Auditing requires general-purpose Standard storage accounts configured for Block Blobs. Premium storage accounts and other blob types (such as Page Blobs or File Shares) do not support the auditing destination requirements.
Here is the breakdown of why only Storage1 works:
Storage1: Supported. It is a Standard general-purpose account.
Storage2: Not supported. It uses Premium block blobs.
Storage3: Not supported. It is a File shares account.
Storage4: Not supported. It uses Premium page blobs.


Reference:

https://learn.microsoft.com/en-us/azure/azure-sql/managed-instance/auditing-configure



View Related Case Study

You need to configure Microsoft Sentinel to meet the technical requirements.
To what should you set Analytics retention for DnsEvents?

  1. 2 years
  2. 12 years
  3. 180 days
  4. 1 year
  5. 6 years

Answer(s): A

Explanation:

In Microsoft Sentinel, the data in the Analytics tier (the "hot" tier for real-time analytics and high-performance querying) has a maximum interactive retention period of two years. It defaults to 90 days, but can be extended up to two years with a prorated long-term retention charge.
Scenario:
Existing Environment. Microsoft Sentinel configuration
Contoso has a Microsoft Sentinel workspace that contains the following tables.

Technical requirements:
Configure Microsoft Sentinel to retain data for the maximum supported duration without changing the tier.
References:
https://learn.microsoft.com/en-us/azure/sentinel/manage-data-overview


Reference:

References:
https://learn.microsoft.com/en-us/azure/sentinel/manage-data-overview



View Related Case Study

You need to implement the planned change for SQLdb1.
Which two actions should you perform? Each correct answer presents part of the solution.
Note: Each correct selection is worth one point.

  1. Create a compliance policy.
  2. Configure Microsoft Entra authentication for SQLServer1.
  3. Create a Conditional Access policy.
  4. Configure Federated client identity for SQLdb1.
  5. Configure a user-assigned managed identity for SQLdb1

Answer(s): B,C

Explanation:

Microsoft Entra authentication must be configured for SQLServer1 so database administrators can authenticate to Azure SQL Database by using Microsoft Entra identities. A Conditional Access policy can then target Azure SQL Database and require multifactor authentication when administrators connect to SQLdb1.


Reference:

https://learn.microsoft.com/en-us/azure/azure-sql/database/authentication-aad-configure?view=azu resql&tabs=azure-portal https://learn.microsoft.com/en-us/azure/azure-sql/database/conditional-access-configure?view=azuresql



View Related Case Study

You need to implement the planned change for storage2. The solution must meet the technical requirements for storage encryption.
What should you do?

  1. Enable purge protection for storage2.
  2. Create an encryption scope in storage2.
  3. Configure storage2 to use an account encryption key.
  4. Assign an Azure role-based access control (Azure RBAC) role to storage2.

Answer(s): C

Explanation:

Because storage2 must support Azure Table storage, it must be created to use an encryption key scoped to the storage account. Azure Table storage can then be encrypted by using a Fabrikam-managed customer-managed key. Encryption scopes apply to Blob storage and do not meet the requirement for Table storage encryption.


Reference:

https://learn.microsoft.com/en-us/azure/storage/common/account-encryption-key-create?tabs=portal https://learn.microsoft.com/en-us/azure/storage/blobs/encryption-scope-overview



View Related Case Study

You need to implement the planned change for WAF1. The solution must minimize administrative effort.
What should you do?

  1. Create an Azure policy.
  2. Modify the Bot Manager 1.1 rule set.
  3. Add a custom rule.
  4. Modify the Azure-managed DRS.

Answer(s): C

Explanation:

To implement location-based rate limiting rules on an Azure Web Application Firewall (WAF) using the Bot Manager 1.1 and Default Rule Set (DRS), you must create a custom rule with a rule type set to "Rate limit" and configure a "Geo location" match condition.
Scenario:
Sub1 has an Azure Web Application Firewall (WAF) named WAF1 that has the following types of rule sets: Bot Manager 1.1, Azure-managed Default Rule Set (DRS)
For WAF1, implement rate limiting rules based on the request location.


Reference:

https://learn.microsoft.com/en-us/azure/web-application-firewall/ag/rate-limiting-overview



Viewing page 15 of 43
Viewing questions 71 - 75 out of 207 questions


Post your Comments and Discuss Microsoft SC-500 exam prep with other Community members:

AI Tutor AI Tutor 👋 I’m here to help!