Free and Premium Microsoft SC-500 Dumps Questions Answers

Add a custom WAF rule. The planned change requires WAF1 to implement rate limiting based on the geographic location of incoming requests. Azure Web Application Firewall supports this combination directly through custom rate-limit rules.

Microsoft documents that Application Gateway WAF rate-limit rules can group requests by GeoLocation, where requests are categorized based on the geographic location derived from the client IP address. The rule can then apply the configured rate threshold independently to traffic originating from each geographic location. Microsoft Learn Azure WAF custom rules also support the GeoMatch operator, which evaluates requests according to their country or region of origin. Microsoft Learn

This makes a single custom rule the most direct and administratively efficient implementation.

The Azure-managed Default Rule Set (DRS) provides predefined protections against common web application attacks, such as injection and protocol attacks; it is not where custom geographic rate limits are defined. Bot Manager 1.1 identifies and handles automated bot traffic but is not the appropriate mechanism for general location-based rate limiting. Azure Policy can enforce configuration standards across resources but does not itself process web requests or impose per-location request thresholds.

Therefore, configure a custom rate-limit rule with geographic matching/grouping.

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

Choose Admin1 because the planned Defender for Cloud change is to enable the NIST SP 800-53 Rev. 5 regulatory compliance standard for Sub1. Defender for Cloud implements regulatory compliance standards through Azure Policy initiatives, and assigning a new standard requires permissions to create or manage policy assignments.

Microsoft states that assigning a regulatory compliance standard requires Owner or Policy Contributor permissions at the relevant scope. Microsoft Learn Admin1 has the Resource Policy Contributor Azure role on Sub1, which provides the policy-management permissions required to assign policy initiatives and therefore supports enabling the NIST standard without granting broader resource-management permissions.

Admin2 has User Access Administrator, which manages Azure RBAC assignments but does not provide the policy-management permissions required for this operation. Admin3 has Contributor, which can manage Azure resources but is restricted from performing certain Microsoft.Authorization operations, including policy assignment operations needed here. Admin4 is a Global Administrator in Microsoft Entra but has no Azure role assignment for Sub1; Microsoft Entra directory administration does not automatically provide subscription-level Defender for Cloud policy-management rights.

Because Admin1 already has the specific policy-management role required for the change, selecting Admin1 satisfies both the functional requirement and the principle of least privilege.

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

The first step is to enable a system-assigned managed identity on VM1. The scenario requires VM1 to read data from storage1 and also specifies that when VM1 is deleted, the permissions associated with VM1 must effectively cease automatically.

A system-assigned managed identity has a one-to-one lifecycle relationship with the Azure resource to which it belongs. Microsoft explicitly states that when the associated resource is deleted, its system-assigned managed identity is automatically deleted from Microsoft Entra ID. In contrast, a user-assigned identity such as ID1 exists independently and remains after the VM is deleted. Microsoft Learn

After enabling the identity, the appropriate storage data-plane role—such as Storage Blob Data Reader when VM1 requires read access to blobs—can be granted to VM1 ' s managed identity at the required scope. Microsoft documents this exact pattern for a Windows VM accessing Azure Storage: enable its managed identity and assign Storage Blob Data Reader to that identity. Microsoft Learn

Federated credentials are unnecessary for a VM ' s native managed identity. Assigning ID1 would violate the lifecycle requirement because ID1 is user-assigned and survives VM1 deletion. A role assignment cannot be created for VM1 ' s system identity until that identity exists.

Therefore, first enable VM1 ' s system-assigned managed identity.

For AKS1, assign the AcrPull role on Registry1. AcrPull provides the permissions required to download container images from an Azure Container Registry without granting permissions to push, modify, or delete images. Microsoft documents that when AKS is integrated with an Azure Container Registry, the appropriate pull-only role is assigned to the AKS identity used for image pulls. This satisfies the explicit requirement that AKS1 must only be able to pull images and follows least privilege. Microsoft Learn

For ID1, assign AcrPush. Microsoft defines AcrPush as the built-in Azure RBAC role for identities that require both push and pull permissions on a non-ABAC-enabled Azure Container Registry. It therefore allows ID1 to upload container images and retrieve existing images from Registry1 without granting broad resource-management capabilities such as Contributor or Owner. Microsoft Learn

Contributor and Owner would grant substantially more Azure management permissions than required. Reader does not provide container image pull/push data-plane permissions.

Storage2 must be configured to use an account encryption key. The planned storage account must support Azure Table storage, while the technical requirement specifies that all storage data must be encrypted using Fabrikam-managed keys, meaning customer-managed keys (CMKs).

Azure Storage treats Table and Queue encryption differently from Blob Storage and Azure Files. Microsoft states that to encrypt Table Storage or Queue Storage with a customer-managed key, the storage account must be configured at creation time to use an encryption key scoped to the account rather than the default service-scoped key. After creation, this setting cannot be changed. Microsoft Learn

An encryption scope does not solve this requirement because encryption scopes apply to Blob Storage containers and individual blobs, not Azure Table data. Microsoft Learn

An Azure RBAC assignment may later be required so that the storage account ' s managed identity can access the customer-managed key in Key Vault, but it does not itself configure Table Storage to support account-level CMK encryption. Purge protection applies to Azure Key Vault rather than storage2.

Therefore, when storage2 is created, configure Table Storage to use the account encryption key.

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

Encryption type

ExpressRoute circuits

Layer 2 encryption

ER3 and ER4 only

Layer 3 encryption

ER1, ER2, ER3, and ER4

For Layer 2 encryption, Azure ExpressRoute uses MACsec (Media Access Control Security). Microsoft states that MACsec is available for ExpressRoute Direct connections because customers have dedicated physical ports connecting their edge routers directly to Microsoft Enterprise Edge routers. Therefore, both ER3 (ExpressRoute Direct) and ER4 (ExpressRoute Metro Direct) can use MACsec. Provider-based ExpressRoute circuits such as ER1 and ER2 do not expose dedicated ExpressRoute Direct ports to the customer and therefore do not support this native Layer 2 MACsec capability. Microsoft Learn

For Layer 3 encryption, ExpressRoute can use IPsec over ExpressRoute private peering. Unlike MACsec, IPsec is an end-to-end network-layer encryption mechanism and is not dependent on ExpressRoute Direct physical ports. Microsoft states that IPsec over ExpressRoute works with any ExpressRoute circuit, allowing encrypted connectivity between the on-premises network and Azure over private peering.

The technical requirement states that all outbound traffic from the function apps to the on-premises network must use ExpressRoute circuits. To accomplish this, the Function App hosting plan must support outbound virtual network integration, because the application must send outbound traffic into an Azure virtual network from which routes learned through or directed toward the ExpressRoute gateway can reach the on-premises environment.

Fa1, which uses the Flex Consumption plan, supports virtual network integration. Microsoft documents that Flex Consumption provides outbound virtual network connectivity and can therefore reach resources accessible through the integrated virtual network. Microsoft Learn

Fa3, which uses a Dedicated App Service plan, also supports outbound virtual network integration. Microsoft further documents that VNet-integrated Functions can have outbound traffic affected by BGP routes learned from an ExpressRoute gateway, and route tables can direct traffic through that gateway. Microsoft Learn

Fa2, however, uses the legacy Consumption plan, which does not support outbound virtual network integration. Consequently, it cannot meet the requirement to route its outbound on-premises traffic through ExpressRoute using this architecture. Microsoft Learn

Therefore, only Fa1 and Fa3 support the required networking configuration.

To add the network interface of a virtual machine named VM1 to an application security group named ASG1, you can follow these steps:

In the Azure portal, search for and select the virtual machine named VM1.

In the left pane, select Networking.

In the Networking pane, select the network interface that you want to add to the application security group named ASG1.

In the network interface pane, select Application security groups.

In the Application security groups pane, select Add.

In the Add application security group pane, select the application security group named ASG1.

Select Save.

You can find more information on this topic in the following Microsoft documentation: Add a network interface to an application security group using the Azure portal.

To ensure that only devices connected to a 131-107.0.0/16 subnet can access data in the rg1lod28681041 Azure Storage account, you can follow these steps:

In the Azure portal, search for and select the storage account named rg1lod28681041.

In the left pane, select Firewalls and virtual networks.

In the Firewalls and virtual networks pane, select Selected networks.

In the Selected networks pane, select Add existing virtual network.

In the Add existing virtual network pane, select the virtual network that contains the 131-107.0.0/16 subnet.

Select Add.

To configure Azure to allow RDP connections from the Internet to a virtual machine named VM1, you can follow the steps below:

Create a new inbound security rule in the network security group (NSG) that is associated with the virtual network subnet that contains VM1. The rule should allow RDP traffic from the Internet to the virtual network subnet. You can use the Azure portal, Azure PowerShell, or Azure CLI to create the rule.

Configure the network security group (NSG) to associate it with the virtual network subnet that contains VM1.

Configure the virtual machine to allow RDP traffic. You can use the Azure portal, Azure PowerShell, or Azure CLI to configure the virtual machine.

To minimize the attack surface of VM1, you can use the following best practices:

Use a strong password for the local administrator account on the virtual machine.

Use Network Security Groups (NSGs) to restrict traffic to only the necessary ports and protocols.

Use Azure Security Center to monitor and protect your virtual machines.

To email an alert to a user named adminl@contoso.com if the average CPU usage of a virtual machine named VM1 is greater than 70 percent for a period of 15 minutes, you can follow these steps:

In the Azure portal, search for and select the virtual machine named VM1.

In the left pane, select Alerts.

Select New alert rule.

In the New alert rule pane, enter the following information:

Name: Enter a name for the alert rule.

Description: Enter a description for the alert rule.

Condition: Select Metric measurement.

Resource: Select the virtual machine named VM1.

Metric: Select Percentage CPU.

Operator: Select Greater than.

Threshold: Enter 70.

Aggregation type: Select Average.

Period: Select 15 minutes.

In the Actions pane, select Add action group.

In the Add action group pane, enter the following information:

Name: Enter a name for the action group.

Short name: Enter a short name for the action group.

Email recipient: Enter the email address of the user you want to receive the alert. For example, adminl@contoso.com.

Select OK.

To ensure that the rg1lod28681041n1 Azure Storage account is encrypted by using a key stored in the KeyVault28681041 Azure key vault, you can follow these steps:

In the Azure portal, search for and select the storage account named rg1lod28681041n1.

In the left pane, select Encryption.

In the Encryption pane, select Customer-managed key.

In the Customer-managed key pane, select Select from Key Vault.

In the Select from Key Vault pane, enter the following information:

Key vault: Select the KeyVault28681041 Azure key vault.

Key: Select the key you want to use.

Select Save.

To collect all the audit failure data from the security log of a virtual machine named VM1 to an Azure Storage account, you can follow these steps:

In the Azure portal, search for and select the virtual machine named VM1.

In the left pane, select Diagnostic settings.

Select Add diagnostic setting.

In the Add diagnostic setting pane, enter the following information:

Name: Enter a name for the diagnostic setting.

Destination: Select Storage account.

Storage account: Select the storage account you want to use.

Logs: Select Windows Event Logs.

Categories: Select Security.

Event types: Select Audit Failure.

Select Save.

To create a new Azure AD directory named 28681041.onmicrosoft.com that contains a new user named user1@28681041.onmicrosoft.com, you can follow these steps:

In the Azure portal, search for and select Azure Active Directory.

In the left pane, select Domains.

Select Add domain.

In the Add a custom domain pane, enter the following information:

Domain name: Enter the domain name you want to use. For example, 28681041.onmicrosoft.com.

Add domain: Select Add domain.

In the left pane, select Users.

Select New user.

In the New user pane, enter the following information:

User name: Enter the user name you want to use. For example, user1@28681041.onmicrosoft.com.

Name: Enter the name of the user.

Password: Enter a password for the user.

Groups: Select the groups you want the user to be a member of.

Select Create.

You can find more information on these topics in the following Microsoft documentation:

Add a custom domain name to Azure Active Directory

Create a new user in your organization - Azure Active Directory

To prevent HTTP connections to the rg1lod28681041n1 Azure Storage account, you can follow these steps:

In the Azure portal, search for and select the storage account named rg1lod28681041n1.

In the left pane, select Firewalls and virtual networks.

In the Firewalls and virtual networks pane, select Selected networks.

In the Selected networks pane, select Add existing virtual network.

In the Add existing virtual network pane, select the virtual network that does not allow HTTP connections.

Select Add.

To register App28681041 to Azure AD and generate a password for it, you can follow these steps:

In the Azure portal, search for and select Azure Active Directory.

In the left pane, select App registrations.

Select New registration.

In the Register an application pane, enter the following information:

Name: App28681041

Supported account types: Select the appropriate account types for your scenario.

Redirect URI: Leave this field blank.

Select Register.

In the App registrations pane, select the newly created App28681041 application.

In the left pane, select Certificates & secrets.

Select New client secret.

In the Add a client secret pane, enter the following information:

Description: Enter a description for the client secret.

Expires: Select an appropriate expiration date for the client secret.

Select Add.

In the Certificates & secrets pane, copy the value of the newly created client secret.

You can find more information on this topic in the following Microsoft documentation: Quickstart: Register an application with the Microsoft identity platform.

To ensure that a user named user2-28681041 can manage the properties of the virtual machines in the RG1lod28681041 resource group using the principle of least privilege, you can follow these steps:

In the Azure portal, search for and select the resource group named RG1lod28681041.

In the left pane, select Access control (IAM).

Select Add.

In the Add role assignment pane, enter the following information:

Role: Select the appropriate role for your scenario. For example, Virtual Machine Contributor.

Assign access to: Select User, group, or service principal.

Select: Enter the name of the user you want to assign the role to. For example, user2-28681041.

Select Save.

An app consent policy allows the tenant to define which delegated permissions are considered low risk and may be consented to by users. Higher-privilege permissions can remain subject to admin consent. Tenant-wide admin consent would approve App1 broadly rather than creating an ongoing policy boundary. Application assignments and PIM role assignments control user access or privileged roles, not delegated permission consent behavior. 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 > app consent settings; Microsoft Learn > app consent policies.

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

The automatically applied security policy is the Microsoft cloud security benchmark (MCSB). MCSB is Microsoft ' s default security standard for Defender for Cloud and provides the baseline security controls and recommendations used to assess Azure resources. Microsoft explicitly identifies the MCSB initiative as the Defender for Cloud default policy initiative. Microsoft Learn

Microsoft also documents that when Defender for Cloud is enabled for an Azure subscription, Foundational CSPM includes regulatory compliance with the Microsoft cloud security benchmark, along with recommendations, secure score, inventory, and other foundational posture-management capabilities. Microsoft Learn

The MCSB standard is designed as a cloud-focused security framework that maps Microsoft security controls to widely recognized frameworks and best practices. It serves as the default foundation for Defender for Cloud recommendations and can apply across Azure and supported multicloud environments. Microsoft has historically documented MCSB as being automatically assigned when environments are onboarded to Defender for Cloud. Microsoft Learn

Standards such as PCI DSS, ISO/IEC 27001, and the CIS Microsoft Azure Foundations Benchmark are additional regulatory or compliance standards that administrators can assign according to organizational requirements. They are not the default Defender for Cloud policy automatically applied simply because Defender CSPM is enabled.

Therefore:

Correct answer: C. Microsoft cloud security benchmark (MCSB)

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

A Sentinel playbook is an Azure Logic Apps workflow used to automate response actions. For an unsupported external ITSM system, a playbook can call the system API and create a ticket when a new incident is generated. Workbooks visualize data, watchlists enrich detections, and analytics rules generate alerts or incidents. None of those directly integrate with a custom ITSM endpoint in the same way a playbook does. In Microsoft Sentinel and Defender scenarios, collection, detection, investigation, and automation are separate functions. The selected answer maps to the function requested by the question rather than a neighboring capability. This is why analytics, hunting, workbooks, connectors, automation rules, and playbooks must not be treated as interchangeable. 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 > Sentinel automation rules and playbooks; Microsoft Learn > playbooks for incident response.

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

First, create a private endpoint for KV1. A private endpoint creates a network interface with a private IP address inside the selected virtual network. With the appropriate Azure Private DNS configuration, the normal Key Vault hostname resolves to that private IP from VNet1, allowing App1 to communicate with KV1 through Azure Private Link instead of the public network path.

Second, disable public access on KV1. Microsoft states that when Key Vault public network access is disabled, public data-plane connections are rejected and the vault is accessible through private endpoints instead. This directly fulfills the requirement that requests from outside the private network path be denied. Microsoft Learn

An access policy controls authorization to Key Vault data, such as whether an identity can retrieve secrets or perform key operations. It does not provide the required network isolation. In this scenario, App1 already accesses the secrets, so the missing controls are specifically network controls.

Adding App1 ' s public IP addresses would also retain public network connectivity, which conflicts with the requirement to use a private address and block outside requests.

Statement

Answer

User2 can connect to

No

User3 can connect to

Yes

User1 can connect to

No

Microsoft Entra Private Access applies access at the application-segment level, and an application segment is defined by attributes including the destination FQDN or IP address and the destination port. Users must be assigned to the corresponding enterprise application to access its defined segments. Microsoft specifically documents that Private Access supports precise per-app segmentation using FQDNs, IP addresses, ports, and user/group assignments.

User2 = No. User2 is assigned only to App2, which permits 10.20.30.40 on port 8443. without an explicit port uses HTTPS default TCP 443, so it does not match App2 ' s segment.

User3 = Yes. User3 is assigned to App1, whose wildcard FQDN *.corp.contoso.com on port 443 matches intranet.corp.contoso.com. Microsoft supports wildcard FQDN segments such as *.contoso.com with explicitly configured ports.

User1 = No. Although intranet.corp.contoso.com matches App1 ' s wildcard FQDN, User1 is authorized only for port 443. Specifying :8443 causes the connection to fall outside App1 ' s configured segment.

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.

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

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.

Assign Logic App Contributor to User1 at the RG1 scope. Microsoft Sentinel playbooks are implemented as Azure Logic Apps, and Microsoft documents that the Logic App Contributor role is the role that permits a user to create, edit, and manage logic apps/playbooks. Because App1 already exists in RG1 and User1 needs to add or manage it as a Sentinel playbook, this is the least-privileged role among the available choices. Microsoft Learn

The scope should be RG1, not the entire subscription. Granting the role at Sub1 would provide unnecessary permissions over logic apps in other resource groups and would violate least privilege.

Logic App Operator is insufficient because it allows a user to read, enable, disable, and run certain logic-app operations, but it does not permit editing or managing the workflow as required for playbook configuration. Microsoft Learn

Microsoft Sentinel Contributor provides permissions to manage Sentinel resources and can attach playbooks to analytics or automation rules, but it does not provide the underlying permissions required to edit/manage the Logic App resource itself. Microsoft explicitly lists Logic App Contributor for creating or editing playbooks

Comprehensive and Detailed 150 to 250 words of Explanation From [Cloud and AI Security Engineer/Course Guide/topics]:

Create an Azure role assignment for the AKS service principal at the Azure Container Registry scope. The automatically generated AKS service principal already provides the Microsoft Entra identity used by the cluster. What it still requires is authorization to perform the necessary operations against the target registry.

Microsoft documents that when an existing service principal needs access to an Azure Container Registry, you grant that access by creating an Azure RBAC role assignment for the service principal. For a registry using the traditional RBAC Registry Permissions model, AKS image-pull access is normally provided by assigning the AcrPull role at the registry scope. Microsoft Learn

Current Azure Container Registry configurations can also use the newer RBAC + ABAC repository-permissions model. In that model, the corresponding least-privilege pull role is Container Registry Repository Reader, rather than AcrPull. The principle remains the same: the AKS identity must receive an appropriate role assignment on the registry. Microsoft Learn

A Microsoft Entra user or group is unnecessary because the cluster already has a service principal. A Key Vault secret is also unnecessary for Azure RBAC authorization.

Correct answer: C. a role assignment

Filtering must happen before data is written to the Log Analytics workspace. With Azure Monitor Agent, Syslog collection is governed by data collection rules, and DCR transformations or filtering can reduce ingestion before records reach the workspace. An ASIM parser normalizes queried data after ingestion, an analytics rule detects conditions after data exists, and a table-level transformation is not the primary collection control for Linux Syslog from AMA in this scenario. 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 > Syslog event collection; Microsoft Learn > data collection rules for Azure Monitor Agent.

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

All four resources fall within Microsoft Defender for Cloud ' s protection or posture-management coverage.

VM1 can receive workload protection through Microsoft Defender for Servers, including endpoint protection, vulnerability assessment, and other server security capabilities. storage1 can use Microsoft Defender for Storage, while Vault1 can use Microsoft Defender for Key Vault for detection of suspicious or anomalous access to Key Vault resources.

VNET1 is also within Defender for Cloud ' s security-posture coverage. Defender for Cloud continuously analyzes Azure networking resources and generates recommendations addressing security issues such as overly permissive network access, missing network security controls, and potentially unsafe configurations. Microsoft explicitly documents an inventory and recommendation experience for networking resources. Microsoft Learn

This distinction is important: VNet1 doesn ' t have a standalone “Defender for Virtual Networks” workload plan comparable to Defender for Servers, but it is still assessed and protected through Defender for Cloud ' s CSPM and network-security recommendation capabilities.

Therefore, all resources shown can participate in Defender for Cloud security protection or posture management.

Statement

Answer

From VM2, you can create a container in storage1.

Yes

From VM1, you can upload data to the blob storage of storage1.

Yes

From VM2, you can upload data to the blob storage of storage1.

Yes

All three statements are Yes because Private1 provides private connectivity to the Blob service of storage1 by assigning it a private IP address from VNet1. Microsoft states that applications within the virtual network can access Azure Storage through a private endpoint using the same storage endpoint and authorization mechanisms, with traffic remaining on the Microsoft backbone. Microsoft Learn

The crucial point is the NSG rule whose destination is the Storage service tag. Azure service tags represent Microsoft-managed IP address prefixes for Azure services. The private endpoint, however, is reached through its private VNet IP address, so traffic to Private1 doesn ' t match the Storage service-tag destination used by the Deny rule. It instead follows normal private VNet routing. Microsoft Learn

VM1 can therefore reach the blob endpoint directly from Subnet1. VM2 can also reach it because Private1 is accessible from clients elsewhere in the same VNet; the private endpoint doesn ' t limit usage to the subnet in which its NIC resides. Creating a blob container and uploading blobs both use the blob sub-resource, which is precisely the resource targeted by Private1. Correct DNS resolution must map the storage Blob FQDN to the private endpoint IP.

The relevant configuration area is Protocols + ciphers. SSL 3.0 is a transport-security protocol, not a certificate configuration. Azure API Management exposes protocol settings for communication between the gateway and clients and between the gateway and backend services. Microsoft documents that protocol configuration is performed from the API Management instance under Security > Protocols + ciphers, where supported frontend and backend protocols can be managed. Microsoft Learn

Microsoft ' s API Management PowerShell documentation specifically recognizes Ssl30 as a configurable backend protocol and frontend protocol setting, confirming that SSL 3.0 belongs to the protocol configuration rather than the Certificates blade. Microsoft Learn

Adding a certificate does not enable a particular SSL/TLS protocol; certificates establish server or client identity and participate in TLS authentication. An API tag only organizes APIs and has no transport-security effect. Changing the pricing tier is also not the first action required merely to locate the SSL protocol setting.

One important operational point is that SSL 3.0 is obsolete and cryptographically unsafe. Microsoft recommends TLS 1.2 or later, and current Azure security guidance treats SSL 3.0, TLS 1.0, and TLS 1.1 as deprecated protocols. The question, however, asks specifically where to configure the requested protocol.

Correct answer: C. From Protocols + ciphers, select a backend protocol.

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