Tüm alıştırma soruları

1252 soru

Soru 881Soru

An administrator is deploying an Azure Application Gateway v2 (Standard_v2 SKU) in Subnet-GW within VNet-Hub to host two secure websites: partners.contoso.com and internal.contoso.com. Both sites must share the same public IP address on the gateway. The configuration requirements are:

1. partners.contoso.com requires end-to-end SSL encryption. The backend pool contains virtual machines in VNet-Spoke1 (peered to VNet-Hub) defined by FQDNs registered in a private DNS zone named private.contoso.com. These virtual machines use self-signed certificates.
2. internal.contoso.com requires SSL termination at the gateway. The backend pool consists of Azure App Service instances. Requests to internal.contoso.com/images/* must be routed to an Azure Storage account static website.
3. The gateway subnet must be secured using a Network Security Group (NSG) and allow management traffic.

Which of the following configurations must be implemented to meet these requirements?

Cevabı ve açıklamayı göster

Cevap: Configure two multi-site HTTPS listeners: one for partners.contoso.com and one for internal.contoso.com. For partners.contoso.com, create a basic routing rule to the VM backend pool, set the backend protocol to HTTPS, upload the self-signed certificate (.cer) as a Trusted Root Certificate, and link VNet-Hub to the private.contoso.com private DNS zone. For internal.contoso.com, create a path-based routing rule with a default target pointing to the App Service backend pool, set the backend protocol to HTTP, enable host header override in the HTTP settings, and define a path map for /images/* pointing to the storage account backend pool. Apply an NSG to Subnet-GW with an inbound rule allowing GatewayManager traffic on ports 6520065200-6553565535 at priority 100100.

Cevap

The correct configuration requires configuring two multi-site HTTPS listeners, linking VNet-Hub to the private DNS zone, overriding the backend host name for the App Service pool, using HTTPS with a Trusted Root Certificate for the VM pool, and applying a high-precedence inbound NSG rule on Subnet-GW allowing GatewayManager traffic.
The correct configuration addresses all requirements: (1) multi-site listeners are used for hosting multiple domains on the same IP and port; (2) VNet-Hub is linked to the private DNS zone so the gateway can resolve the VM backend pool's FQDNs; (3) backend HTTP settings use HTTPS with a Trusted Root Certificate for the VM pool, and HTTP with host header override for the multi-tenant App Service; (4) a path-based routing rule is configured for the site requiring path mapping; (5) the NSG allows GatewayManager traffic on ports 6520065200-6553565535 with higher precedence (lower priority number) than any deny rule.

Adım Adım Çözüm

1
Configure listeners for multi-site hosting.
Two multi-site HTTPS listeners are created on port 443443, one with host name partners.contoso.com and the other with internal.contoso.com, allowing them to share the same public IP address.
Basic listeners cannot differentiate traffic based on host headers, so multi-site listeners are required to host multiple domains on the same IP and port.
2
Configure DNS resolution for the gateway.
VNet-Hub (where the Application Gateway is deployed) is linked to the private DNS zone private.contoso.com.
The Application Gateway must resolve the FQDNs of the backend VMs. Linking only the spoke VNet would prevent the gateway in the hub VNet from performing resolution.
3
Configure backend settings for both pools.
The VM backend settings use HTTPS with the uploaded self-signed root certificate, while the App Service backend settings use HTTP and enable the override host name setting.
End-to-end SSL requires HTTPS backend settings. Self-signed certificates require a Trusted Root Certificate to be uploaded for verification. App Service requires host name override because it is a multi-tenant service.
4
Configure routing rules.
A basic routing rule links partners.contoso.com to the VM pool. A path-based routing rule links internal.contoso.com to the App Service pool by default, with a path map routing /images/* to the storage account.
Path-based routing is required to separate traffic based on URL subpaths, while basic routing is sufficient for single-target domains.
5
Secure the subnet using NSG rules.
An NSG is applied to Subnet-GW with an inbound rule allowing ports 6520065200-6553565535 from the GatewayManager service tag, set at priority 100100.
Azure Application Gateway v2 requires communication with the Gateway Manager. The rule must have higher precedence (lower priority number) than any custom deny rules to avoid blocking management traffic.

Anahtar Kavram

Azure Application Gateway v2 configuration including multi-site listeners, path-based routing, backend certificate trust, DNS resolution dependencies, and subnet NSG requirements.
Tahmini Süre:3m 0s
Soru 882Soru

An organization requires the deployment of three independent workloads using Azure Container Instances (ACI). Which container restart policy should be matched to each workload scenario to align with the specified operational requirements?

Soldaki öğeye tıklayın, sonra eşleşen sağdaki öğeye tıklayın

Öğeler

A telemetry collector that continuously listens for incoming IoT device data and must automatically recover if the container agent experiences a fault.
A daily data validation utility that executes a check, reports status, and must restart only if the validation run terminates with an error code.
A data migration script designed to perform a one-time database schema upgrade and must not run again under any circumstances after its execution completes.

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

Match the telemetry collector to 'Restart policy set to Always', the daily data validation utility to 'Restart policy set to OnFailure', and the data migration script to 'Restart policy set to Never'.
Matching the continuous telemetry collector with the Always restart policy ensures it recovers from faults. Matching the daily validation utility with the OnFailure policy ensures it completes once successfully but retries if it fails. Matching the database schema upgrade with the Never policy prevents unintended execution attempts.

Adım Adım Çözüm

1
Evaluate the telemetry collector requirements.
The workload is continuous and requires high availability, needing recovery from any unexpected exits or faults.
For workloads that must run indefinitely, the Always restart policy is the correct choice because it restarts the container regardless of the exit code.
2
Evaluate the daily data validation utility requirements.
The utility is a run-to-completion task that should only restart if it terminates with an error code, and must remain stopped on successful completion.
The OnFailure restart policy restarts the container only when the process exits with a non-zero code, preventing duplicate executions upon success.
3
Evaluate the data migration script requirements.
The script runs once and must never execute again under any circumstances, even if it fails.
The Never restart policy disables all automated restarts, preventing a failed or succeeded migration script from running a second time.

Anahtar Kavram

Azure Container Instances (ACI) supports three restart policies: Always, OnFailure, and Never. Always is for continuous services, OnFailure is for run-to-completion tasks that need retry logic on error, and Never is for one-time tasks that must not run again.
Soru 883Soru

You plan to configure a public Azure Load Balancer named LB1 using the Standard SKU.

You have three virtual machines named VM1, VM2, and VM3 in the same virtual network. The virtual machines are standalone instances and are not configured in any availability set.

The public IP configurations for the virtual machines are as follows:
- VM1 has a Standard SKU public IP address associated with its network interface.
- VM2 has a Basic SKU public IP address associated with its network interface.
- VM3 does not have a public IP address associated with its network interface.

You need to ensure that you can add VM1, VM2, and VM3 to the backend pool of LB1.

Which two actions should you perform? Each correct answer presents a complete solution.

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: Upgrade the public IP address of VM2 to the Standard SKU.; Disassociate the public IP address from VM2.

Cevap

To add VM1, VM2, and VM3 to the backend pool of the Standard SKU Load Balancer, you must either upgrade the public IP address of VM2 to the Standard SKU or disassociate the public IP address from VM2.
The correct options are upgrading the public IP of the incompatible virtual machine to the Standard SKU, and disassociating the public IP address from that virtual machine. A Standard Load Balancer requires that all virtual machines in its backend pool either have no public IP address or use Standard SKU public IP addresses. Because the virtual machines are standalone, using a Standard Load Balancer is mandatory. Upgrading the public IP to Standard SKU or disassociating the public IP address from the incompatible virtual machine satisfies this requirement, enabling all three virtual machines to be placed in the backend pool.

Adım Adım Çözüm

1
Analyze the load balancer SKU and backend VM topology constraints.
Since VM1, VM2, and VM3 are standalone virtual machines not associated with an availability set, a Basic SKU load balancer cannot be used. A Standard SKU load balancer is required to load balance multiple standalone VMs.
Basic SKU load balancers restrict backend pool members to a single availability set or virtual machine scale set, whereas Standard SKU load balancers support any virtual machines in a single virtual network.
2
Identify public IP address SKU restrictions for the Standard Load Balancer backend pool.
All virtual machines in the backend pool of a Standard Load Balancer must either have Standard SKU public IP addresses or no public IP addresses associated with their network interfaces. Basic SKU public IPs are incompatible.
Mixing Basic SKU public IP resources with Standard SKU load balancing resources is not supported by Azure's resource SKU rules.
3
Evaluate the state of VM2 and determine correct remediation steps.
VM2 currently has a Basic SKU public IP address. To make VM2 compatible, you can either upgrade its public IP to a Standard SKU or remove the public IP entirely by disassociating it.
Both methods eliminate the Basic SKU public IP conflict on the network interface of VM2, allowing all three virtual machines to be added to the Standard Load Balancer backend pool.

Anahtar Kavram

Azure Load Balancer SKU compatibility rules require that all virtual machines in the backend pool of a Standard Load Balancer use Standard SKU public IP addresses or have no public IP address, and standalone virtual machines cannot be grouped in a Basic Load Balancer backend pool.
Tahmini Süre:2m 0s
Soru 884Soru

An administrator needs to analyze diagnostic logs for several Azure Key Vaults. The logs are collected in a Log Analytics workspace named LogsWS.

The administrator wants to retrieve the total number of operations for each Key Vault resource over the past 24 hours, grouped by the operation name.

Which Kusto Query Language (KQL) query should the administrator execute to achieve this objective?

Cevabı ve açıklamayı göster

Cevap: AzureDiagnostics
| where TimeGenerated > ago(24h)
| where ResourceProvider == "MICROSOFT.KEYVAULT"
| summarize count() by Resource, OperationName

Cevap

The KQL query that filters by TimeGenerated and ResourceProvider before aggregating counts using the summarize operator.
The correct query evaluates the filters before summarizing the results. This represents syntactically correct KQL and respects the pipeline mechanism where columns are stripped after summarization.

Adım Adım Çözüm

1
Filter the dataset by time range to reduce the amount of data processed early in the query pipeline.
Filters records to only those within the last 24 hours.
In KQL, filtering by TimeGenerated as early as possible optimizes performance.
2
Filter records by ResourceProvider to isolate Key Vault diagnostic events.
Only rows associated with the MICROSOFT.KEYVAULT provider are kept.
This ensures the query only groups operations relevant to the targeted service type.
3
Summarize the events by grouping them by Resource and OperationName, calculating the count of events for each group.
The final output projects the Resource, OperationName, and the counted events.
The summarize operator reshapes the output schema, removing all unreferenced columns such as TimeGenerated from the pipeline.

Anahtar Kavram

Kusto Query Language pipeline execution flow and schema transformation behavior.
Soru 885Soru

An administrator is planning the deployment of a new web application to Azure App Service. The application must meet the following requirements:
- Support scaling out to at least 10 instances.
- Enable integration with an Azure Virtual Network (VNet) to access backend resources securely.
- Support deployment slots to enable staging and testing before production swaps.
- Minimize hosting costs.

Which of the following configurations should the administrator select? (Select TWO.)

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: The Standard (S1) pricing tier for the App Service plan; A maximum of 5 deployment slots

Cevap

To meet the requirements at the lowest cost, the administrator should select the Standard (S1) pricing tier for the App Service plan and configure a maximum of 5 deployment slots.
The Standard (S1) pricing tier is the most cost-effective tier that provides VNet integration, support for 10 scale-out instances, and deployment slots. Because the Standard tier is used, the application is limited to a maximum of 5 deployment slots, which fulfills the deployment slot requirement without needing the more expensive Premium tier.

Adım Adım Çözüm

1
Evaluate the VNet integration and deployment slot requirements against the available tiers.
The Basic (B1) tier is eliminated because it lacks support for both VNet integration and deployment slots.
Basic tier plans do not support advanced networking or staging slots.
2
Evaluate the scale-out requirement of 10 instances.
The Standard (S1) tier supports up to 10 instances, while Premium tiers support 30 or more instances. Both meet the scale-out requirement.
Standard tier offers exactly the 10 scale-out instances required by the workload.
3
Compare the Standard (S1) and Premium (P1v3) tiers for cost-effectiveness and slot limitations.
The Standard (S1) tier is selected because it is more cost-effective than Premium. Standard tier supports a maximum of 5 deployment slots, which satisfies the staging requirement.
Standard (S1) is the lowest cost tier that meets all criteria, and it enforces a limit of 5 deployment slots.

Anahtar Kavram

Azure App Service Plan pricing tiers and feature capability mapping
Tahmini Süre:1m 30s
Soru 886Soru

An administrator needs to recover specific configuration files from a backup of a Linux virtual machine named `vm-prod-lnx`. The virtual machine's storage layout uses Logical Volume Manager (LVM) across multiple managed disks.

The administrator downloads the Item-Level Recovery (ILR) script from the Recovery Services vault and attempts to execute it directly on `vm-prod-lnx` to mount the recovery point. However, the script fails to mount the logical volumes because of a volume group name and UUID conflict with the active system.

What should the administrator do to retrieve the required configuration files?

Cevabı ve açıklamayı göster

Cevap: Run the recovery script on a separate Linux virtual machine deployed in the same virtual network, mount the volumes, and transfer the files to `vm-prod-lnx`.

Cevap

Run the recovery script on a separate Linux virtual machine deployed in the same virtual network, mount the volumes, and transfer the files to the original virtual machine.
Running the recovery script on a separate Linux helper virtual machine is the recommended approach when LVM volume group conflicts prevent mounting on the original VM. Because the helper VM does not have the same volume group names or UUIDs active, the script can mount the disks without conflict, allowing the administrator to copy the desired files back to the original VM.

Adım Adım Çözüm

1
Identify the restore requirements.
The target is individual file recovery (Item-Level Recovery) rather than a full virtual machine restore.
This avoids unnecessary downtime and potential data loss associated with full virtual machine replacement.
2
Analyze the cause of the LVM volume group conflict.
The script fails on the original virtual machine because the backup disks contain identical LVM volume group names and UUIDs as the active system.
Operating systems cannot mount two different LVM volume groups with identical metadata simultaneously.
3
Select a compatible helper environment.
A separate Linux virtual machine in the same virtual network is selected to execute the recovery script.
A separate virtual machine prevents LVM naming conflicts and natively supports Linux filesystems, which is not possible on a Windows helper VM.
4
Execute the script and copy files.
The script mounts the backup disks as local drives on the helper virtual machine, enabling file transfer via secure network protocols.
This completes the recovery of the specific files with zero downtime for the primary virtual machine.

Anahtar Kavram

Azure Backup Item-Level Recovery (ILR) for Linux VMs with LVM requires a helper VM when volume group conflicts occur.
Tahmini Süre:2m 0s
Soru 887Soru

An organization is deploying an Azure Application Gateway v2 to load balance traffic across a pool of backend web servers. The security policy requires end-to-end TLS encryption. The backend servers use certificates issued by an internal enterprise Certification Authority (CA). You need to configure the Application Gateway to support this configuration. In which order should you perform the configuration steps?

Öğeleri doğru sıraya koymak için sürükleyin

Cevabı ve açıklamayı göster

Cevap

The correct sequence is: Export the public root certificate of the internal enterprise CA as a Base-64 encoded .cer file; Create a backend pool containing the FQDNs or IP addresses of the backend web servers; Create backend settings configured for HTTPS on port 443 and upload the exported root certificate (.cer); Upload the frontend certificate as a .pfx file to configure an HTTPS listener; and Create a request routing rule to link the HTTPS listener, the backend pool, and the backend settings.
The correct sequence begins with exporting the public root certificate from the enterprise CA (.cer format). This certificate is a dependency for configuring backend settings. Once the backend pool is established, the backend settings can be created with the uploaded root certificate to enable secure communication with backend servers. Next, the frontend HTTPS listener is configured with the frontend certificate (.pfx format). Finally, a request routing rule is created to tie all these components together. This sequence respects all configuration dependencies in Azure.

Adım Adım Çözüm

1
Export the public root certificate of the internal enterprise CA.
A Base-64 encoded .cer file containing the public root certificate is generated.
For Application Gateway v2 to trust certificates signed by an internal enterprise CA, the root CA certificate must be uploaded to the gateway. This requires first exporting it in the supported .cer format.
2
Create a backend pool with the backend servers.
A backend pool is defined with backend targets.
The backend pool is a prerequisite component for routing rules and represents the backend servers running the applications.
3
Create backend settings with HTTPS and the uploaded root certificate.
Backend settings are configured to communicate with the backend servers securely.
The backend settings define how traffic is forwarded to the backend. Uploading the trusted root certificate is mandatory for HTTPS on v2 SKU when using non-well-known CA certificates.
4
Upload the frontend certificate (.pfx) and create an HTTPS listener.
An HTTPS listener is established on the frontend IP address.
The listener requires a certificate containing the private key (.pfx format) to decrypt incoming secure traffic from clients.
5
Create a request routing rule.
A routing rule is created associating the listener, backend pool, and backend settings.
The routing rule binds the frontend listener to the backend settings and backend pool, completing the logical flow of traffic through the gateway.

Anahtar Kavram

End-to-end TLS configuration with custom/private CA on Azure Application Gateway v2
Tahmini Süre:3m 0s
Soru 888Soru

An administrator is configuring connectivity in an Azure subscription. The environment contains the following resources in the East US region:

* VNet-Hub (10.150.0.0/1610.150.0.0/16): Contains a subnet named GatewaySubnet with an active Virtual Network Gateway, and a subnet named Subnet-Hub containing a virtual machine named VM-Hub.
* VNet-SpokeA (10.160.0.0/1610.160.0.0/16): Contains a subnet named Subnet-A containing a virtual machine named VM-SpokeA.
* VNet-SpokeB (10.170.0.0/1610.170.0.0/16): Contains a subnet named Subnet-B containing a virtual machine named VM-SpokeB.

The administrator configures virtual network peering between VNet-Hub and VNet-SpokeA, and between VNet-Hub and VNet-SpokeB. No direct peering exists between VNet-SpokeA and VNet-SpokeB.

You need to ensure that VM-SpokeA can communicate with an on-premises network connected via the Virtual Network Gateway in VNet-Hub.

Which of the following configuration settings must be enabled on the virtual network peering links to meet this requirement? Select two.

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: Enable Allow gateway transit on the peering link from VNet-Hub to VNet-SpokeA.; Enable Use remote gateways on the peering link from VNet-SpokeA to VNet-Hub.

Cevap

To allow communication between the spoke virtual network and the on-premises network, you must enable 'Allow gateway transit' on the peering link from the hub virtual network to the spoke virtual network, and enable 'Use remote gateways' on the peering link from the spoke virtual network to the hub virtual network.
To establish connectivity between a virtual machine in a spoke virtual network and an on-premises network through a gateway in a hub virtual network, two peering configurations are required: 'Allow gateway transit' must be enabled on the peering link from the hub virtual network to the spoke virtual network, and 'Use remote gateways' must be enabled on the peering link from the spoke virtual network to the hub virtual network.

Adım Adım Çözüm

1
Configure the peering link from the hub virtual network (VNet-Hub) to the spoke virtual network (VNet-SpokeA).
The 'Allow gateway transit' option is enabled.
This allows the hub virtual network to share its gateway with the spoke virtual network.
2
Configure the peering link from the spoke virtual network (VNet-SpokeA) to the hub virtual network (VNet-Hub).
The 'Use remote gateways' option is enabled.
This allows the spoke virtual network to route traffic to the gateway in the hub virtual network.

Anahtar Kavram

Gateway transit in virtual network peering allows a peered virtual network to use the virtual network gateway in the hub virtual network to connect to on-premises networks.
Soru 889Soru

You are configuring a public Azure Load Balancer to distribute traffic to two virtual machines, VM-App1 and VM-App2. The virtual machines are deployed in different Availability Zones (Zone 1 and Zone 2) within the same Azure region. You need to ensure the load balancer can route traffic to both virtual machines. Which two configurations must you select to support this architecture?

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: Deploy the load balancer using the Standard SKU.; Configure the frontend IP address using a Standard SKU public IP.

Cevap

Deploy the load balancer using the Standard SKU and configure the frontend IP address using a Standard SKU public IP.
To distribute traffic to virtual machines located in different Availability Zones, a Standard SKU load balancer must be deployed because the Basic SKU load balancer does not support zonal or zone-redundant backend pools. Additionally, the public IP address associated with the frontend of a Standard SKU load balancer must also be of the Standard SKU, as SKU alignment between the load balancer and the frontend public IP is not permitted.

Adım Adım Çözüm

1
Analyze the virtual machine layout and zone configuration.
The target virtual machines VM-App1 and VM-App2 are deployed in different Availability Zones (Zone 1 and Zone 2).
Azure Load Balancers have different capability boundaries depending on the SKU selected.
2
Determine the required Load Balancer SKU.
A Standard SKU load balancer is required.
Basic SKU load balancers do not support backend pool members spanning multiple Availability Zones. Only the Standard SKU load balancer supports zonal and zone-redundant backend pool configurations.
3
Determine the required Public IP SKU.
A Standard SKU public IP address is required.
The SKU of the public IP address must match the SKU of the load balancer. Since a Standard SKU load balancer is required, the frontend public IP configuration must use a Standard SKU public IP.

Anahtar Kavram

Azure Load Balancer SKU features and IP compatibility
Soru 890Soru

You are configuring diagnostic settings for a set of Azure virtual machines and Key Vaults. Match each Azure Monitor diagnostic destination on the left to its corresponding primary administrative use case on the right.

Soldaki öğeye tıklayın, sonra eşleşen sağdaki öğeye tıklayın

Öğeler

Log Analytics workspace
Azure Storage account
Azure Event Hubs

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

Log Analytics workspace matches with performing interactive KQL log analysis; Azure Storage account matches with storing data for long-term compliance retention; Azure Event Hubs matches with streaming diagnostic data immediately to external SIEM systems.
Log Analytics is used for interactive KQL analysis, Azure Storage accounts are used for cost-effective long-term storage, and Azure Event Hubs are used for streaming data to external systems.

Adım Adım Çözüm

1
Identify the primary capabilities of a Log Analytics workspace.
It supports interactive log analysis, alerting, and KQL queries.
This links it to the requirement for running query-based analytics.
2
Evaluate the storage requirements and costs for long-term data retention.
An Azure Storage account is the standard, lowest-cost destination for cold data storage.
This links the storage account destination to long-term archiving.
3
Determine how to ingest Azure diagnostics into external monitoring tools.
Azure Event Hubs acts as an event ingestion service that streams data out of Azure.
This links the Event Hub destination to real-time integration with external SIEM systems.

Anahtar Kavram

Azure Monitor diagnostic settings destination routing rules
Soru 891Soru

An administrator needs to configure secure data plane access to an Azure Storage Queue named incoming-orders-queue for an application registered as a service principal named OrderProcessorSP. The application must be able to read, peek, and delete messages from the queue during execution, but it must not be able to send new messages or manage the queue structure. Following the principle of least privilege, which Azure role-based access control (RBAC) role should the administrator assign to OrderProcessorSP?

Cevabı ve açıklamayı göster

Cevap: Storage Queue Data Message Processor

Cevap

Storage Queue Data Message Processor
The correct role is Storage Queue Data Message Processor. This built-in Azure RBAC role allows an identity to read, peek, and delete messages from a queue, which is exactly the set of permissions required for a message processor application. It adheres to the principle of least privilege by not permitting message generation (sending) or queue management operations.

Adım Adım Çözüm

1
Analyze the access requirement
The application needs to read, peek, and delete messages, but not send messages or manage queues.
This establishes the minimum permissions needed to comply with the principle of least privilege.
2
Differentiate control plane and data plane roles
Standard subscription or resource group roles like Reader do not grant data plane access to storage queue content.
Azure Storage separates control plane access (managing resources) from data plane access (accessing the data within the resources).
3
Evaluate storage-specific data plane roles
Storage Queue Data Message Processor grants read/peek/delete message permissions, which matches the processing needs perfectly without additional write or admin rights.
Matching the requirements to the most restrictive built-in role ensures least privilege access.

Anahtar Kavram

Selecting the least-privilege Azure built-in RBAC role for data plane operations in Azure Storage queues.
Tahmini Süre:1m 30s
Soru 892Soru

An enterprise cloud infrastructure is configured with the following hierarchy:

- Management Group: `Corp-MG`
- Subscription: `Sub-Production`
- Resource Group: `RG-AppStore`
- Resource Group: `RG-DataStore`

You are tasked with assigning Azure Role-Based Access Control (RBAC) roles to security groups to align with the principle of least privilege. Match each security group to the correct Azure RBAC role and scope assignment based on their technical requirements.

Soldaki öğeye tıklayın, sonra eşleşen sağdaki öğeye tıklayın

Öğeler

GroupA: Must be able to create and manage all resources within `RG-AppStore`, but must not be able to modify resource configurations in `RG-DataStore` or delegate access to other users.
GroupB: Must be able to view all resource configurations across all subscriptions under `Corp-MG` and create support requests for any issues, but must not be able to modify any resources.
GroupC: Must be able to manage user access, assign RBAC roles, and manage resource locks across the entire `Sub-Production` subscription, without having permissions to modify the virtual machines or databases directly.

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

GroupA matches the Contributor role at the `RG-AppStore` scope. GroupB matches the Reader and Support Request Contributor roles at the `Corp-MG` scope. GroupC matches the User Access Administrator role at the `Sub-Production` scope.
The correct mapping assigns the minimum required role (Contributor, Reader + Support Request Contributor, or User Access Administrator) at the narrowest scope that covers the requirement (resource group, management group, or subscription, respectively).

Adım Adım Çözüm

1
Determine the role and scope for GroupA.
Contributor role at the `RG-AppStore` scope.
GroupA needs resource management capabilities within a single resource group but no delegation rights, which corresponds to the Contributor role restricted to `RG-AppStore`.
2
Determine the role and scope for GroupB.
Reader and Support Request Contributor roles at the `Corp-MG` scope.
GroupB needs read access across all subscriptions under the management group and the ability to submit support tickets, which requires Reader and Support Request Contributor roles applied at the management group (`Corp-MG`) scope for inheritance.
3
Determine the role and scope for GroupC.
User Access Administrator role at the `Sub-Production` scope.
GroupC needs to manage role assignments and locks at the subscription level without resource modification permissions, which maps to User Access Administrator at the `Sub-Production` scope.

Anahtar Kavram

Assigning Azure RBAC roles at various scopes based on the principle of least privilege.
Tahmini Süre:2m 0s
Soru 893Soru

You are planning the IP addressing scheme for a new Azure virtual network named `vnet-logistics` that has an address space of 172.20.0.0/21172.20.0.0/21. You need to create two subnets to meet the following requirements:

- A subnet for Azure Bastion that supports the minimum required subnet prefix size.
- A subnet named `snet-db` that must support at least 1111 database servers.

You must minimize the number of IP addresses allocated to both subnets to conserve the address space for future expansion.

Which two of the following subnet configurations should you implement? (Select two.)

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: A subnet named `AzureBastionSubnet` with an address space of 172.20.1.0/26172.20.1.0/26; A subnet named `snet-db` with an address space of 172.20.2.0/28172.20.2.0/28

Cevap

The correct configurations are a subnet named `AzureBastionSubnet` with an address space of 172.20.1.0/26172.20.1.0/26, and a subnet named `snet-db` with an address space of 172.20.2.0/28172.20.2.0/28.
The correct subnet configurations are the subnet named `AzureBastionSubnet` with a /26/26 prefix and the subnet named `snet-db` with a /28/28 prefix. Azure Bastion enforces a strict naming requirement of `AzureBastionSubnet` and a minimum prefix size of `/26`. For the database subnet, hosting 1111 servers requires at least 1616 total IP addresses because Azure reserves 5 IP addresses in every subnet. A /28/28 prefix provides exactly 1616 addresses, leaving 1111 usable, which satisfies the host requirement while minimizing address space consumption.

Adım Adım Çözüm

1
Determine the naming and sizing requirements for the Azure Bastion subnet.
Azure Bastion requires a dedicated subnet named exactly `AzureBastionSubnet` with a minimum prefix size of `/26` (6464 IP addresses). Therefore, `AzureBastionSubnet` with a /26/26 prefix is required.
Azure enforces strict naming and a minimum prefix size of `/26` for Bastion deployments.
2
Calculate the required number of IP addresses for the database subnet.
To support 1111 database servers, we must account for the 5 IP addresses reserved by Azure in every subnet. The total required IP addresses is 11+5=1611 + 5 = 16.
Azure reserves the first four IP addresses and the last IP address (broadcast) in every subnet.
3
Determine the smallest subnet prefix that can accommodate at least 1616 total IP addresses.
A /28/28 prefix provides exactly 1616 IP addresses (23228=162^{32-28} = 16), which results in 165=1116 - 5 = 11 usable IP addresses. A /29/29 prefix only provides 88 total IP addresses (33 usable). Therefore, `snet-db` must use a /28/28 prefix.
Using a /28/28 prefix minimizes the allocated address space while still satisfying the requirement for 1111 usable host addresses.

Anahtar Kavram

Subnet sizing and naming requirements in Azure, including reserved IP addresses and service-specific subnet constraints.
Soru 894Soru

An organization deploys a new compliance auditing environment. The deployment contains an Azure resource group named rg-audit-compliance. Inside the resource group, the operations team creates an Azure Storage account named saauditlogs and an Azure Key Vault named kvauditkeys.

To meet compliance requirements, the team performs the following actions:
1. Applies a resource tag named RegulatoryCompliance: PCI-DSS to rg-audit-compliance.
2. Applies a CanNotDelete resource lock named lock-rg-delete to rg-audit-compliance.

Which of the following statements regarding the governance and lock behaviors of these resources are correct?

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: The saauditlogs storage account does not automatically inherit the RegulatoryCompliance: PCI-DSS tag.; The CanNotDelete lock applied to rg-audit-compliance prevents the deletion of saauditlogs.

Cevap

The correct statements are that the saauditlogs storage account does not automatically inherit the RegulatoryCompliance: PCI-DSS tag, and the CanNotDelete lock applied to rg-audit-compliance prevents the deletion of saauditlogs.
The correct statements are that tags are not inherited from resource groups to resources, and resource locks are inherited from the resource group scope to child resources. This ensures tag inheritance does not happen automatically, while lock inheritance prevents deletion of the storage account.

Adım Adım Çözüm

1
Evaluate tag inheritance behavior in Azure.
Tags applied at the resource group level are not inherited by resources within that resource group. Therefore, saauditlogs does not inherit the RegulatoryCompliance: PCI-DSS tag.
Azure Resource Manager does not automatically propagate tags from resource groups to child resources.
2
Evaluate resource lock inheritance behavior in Azure.
Locks applied at the resource group level are inherited by all resources within that group. A CanNotDelete lock on rg-audit-compliance applies to saauditlogs.
Azure Resource Manager propagates resource locks down the resource hierarchy (Subscription -> Resource Group -> Resource).
3
Verify if RBAC roles can bypass resource locks.
Resource locks block operations for all users and roles, including subscription Owners and User Access Administrators.
Locks enforce restriction at the resource level, requiring the lock itself to be deleted by an authorized user before the restricted operation can proceed.

Anahtar Kavram

Azure resource tags do not inherit automatically, whereas resource locks inherit down the resource hierarchy and restrict actions for all users regardless of their RBAC roles.
Tahmini Süre:1m 30s
Soru 895Soru

You have an Azure subscription containing a resource group named `rg-analytics` and an Azure Storage account named `streports2026`. Inside the storage account, you have a blob container named `auditlogs`.

A team of internal auditors belongs to a Microsoft Entra ID group named `Audit-Team-Group`. The auditors need to upload and read blobs in the `auditlogs` container. They must also be able to browse to the container using the Azure Portal. The solution must follow the principle of least privilege.

To configure the required access, which of the following role assignments should you perform? (Select two.)

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: Assign the Reader role to Audit-Team-Group at the streports2026 storage account scope.; Assign the Storage Blob Data Contributor role to Audit-Team-Group at the auditlogs container scope.

Cevap

Assign the Reader role to Audit-Team-Group at the streports2026 storage account scope, and assign the Storage Blob Data Contributor role to Audit-Team-Group at the auditlogs container scope.
To access blob data using Microsoft Entra ID authentication in the Azure Portal, security principals require both control plane access to view the storage account and data plane access to read and write the blobs. Assigning the Reader role at the storage account scope provides portal navigation capabilities, while assigning the Storage Blob Data Contributor role at the container scope provides the necessary data plane access under the principle of least privilege.

Adım Adım Çözüm

1
Determine the data plane role required for reading and writing (uploading) blobs.
The Storage Blob Data Contributor role is selected at the container scope to grant read and write access to blobs while adhering to least privilege.
This role is required to perform data plane actions such as uploading and reading blobs.
2
Determine the role required to navigate the Azure Portal to the storage account.
The Reader role is selected at the storage account scope.
Users accessing storage via the Azure Portal need a control-plane role (such as Reader) at the storage account scope to locate and navigate to the resource in the portal interface.

Anahtar Kavram

Azure RBAC split between control plane and data plane for Azure Storage when using Microsoft Entra ID authentication in the Azure Portal.
Soru 896Soru

An administrator is configuring access control and monitoring for an Azure subscription. The subscription contains a Log Analytics workspace named Workspace1 that collects logs from virtual machines and Azure SQL databases.

You need to configure Workspace1 and write a Kusto Query Language (KQL) query to meet the following requirements:
- Ensure that database administrators can view diagnostic logs only for their SQL databases. They must not have access to any other logs stored in Workspace1.
- Retrieve SQL database diagnostic logs from the AzureDiagnostics table where the execution duration of a query is greater than 5 seconds.
- Sort the query results to show the longest-running queries first.

Which three options should you select to meet the requirements?

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: Configure Workspace1 to use the "Use resource or workspace permissions" access control mode.; Assign the Reader role to the database administrators on the resource groups containing the SQL databases.; Run the KQL query: AzureDiagnostics | where ResourceProvider == "MICROSOFT.SQL" and DurationMs > 5000 | sort by DurationMs desc

Cevap

To meet the requirements, you must configure Workspace1 to use resource-context permissions, assign the Reader role to database administrators at the resource group level of the SQL databases, and use a KQL query with the 'where' operator and 'sort by' descending.
Enabling 'Use resource or workspace permissions' combined with assigning Reader permissions at the resource level allows resource-context access, which scopes log visibility to only the SQL databases. The correct KQL query uses the 'where' operator to filter records and 'sort by' with the descending modifier to order results by the longest execution times.

Adım Adım Çözüm

1
Configure workspace access control.
Setting Workspace1 to 'Use resource or workspace permissions' enables resource-context access, meaning permissions are evaluated at the resource level.
This allows users to view logs for only the resources they have access to, satisfying the privacy requirement.
2
Assign RBAC roles at the resource scope.
Assigning the Reader role to database administrators on the resource groups containing the SQL databases.
This gives them permission to access the SQL database resources and their associated logs, without granting access to the entire Log Analytics workspace.
3
Write and refine the KQL query.
Querying the AzureDiagnostics table filtering by ResourceProvider and DurationMs, then sorting descending.
KQL requires the 'where' operator for filtering and the 'sort by' or 'order by' operator for sorting. The 'filter' operator is invalid syntax.

Anahtar Kavram

Log Analytics Workspace access modes (workspace-context vs. resource-context) and basic KQL query syntax.
Soru 897Soru

An organization has an Azure virtual network named VNet-Prod (10.10.0.0/1610.10.0.0/16) with three subnets: Web-Subnet (10.10.1.0/2410.10.1.0/24), App-Subnet (10.10.2.0/2410.10.2.0/24), and Sec-Subnet (10.10.3.0/2410.10.3.0/24). A Network Virtual Appliance (NVA) named NVA-Sec (10.10.3.1010.10.3.10) is deployed in Sec-Subnet. A route table named RT-Web is associated with Web-Subnet. Currently, RT-Web contains the following user-defined routes:

- Route A: Destination 10.10.2.0/2410.10.2.0/24, Next hop type: Virtual appliance, Next hop IP address: 10.10.3.1010.10.3.10
- Route B: Destination 10.10.2.0/2510.10.2.0/25, Next hop type: Virtual network
- Route C: Destination 0.0.0.0/00.0.0.0/0, Next hop type: Internet

You notice that traffic from Web-Subnet destined for servers in App-Subnet with IP addresses from 10.10.2.110.10.2.1 to 10.10.2.5010.10.2.50 is bypassing NVA-Sec and communicating directly. You need to ensure that all traffic from Web-Subnet to App-Subnet is routed through NVA-Sec and successfully forwarded by the appliance. Which two actions should you perform? (Select two.)

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: Delete Route B from the RT-Web route table.; Enable IP forwarding on the virtual network interface of NVA-Sec.

Cevap

Delete Route B from the RT-Web route table and enable IP forwarding on the virtual network interface of NVA-Sec.
Deleting Route B removes the more specific /25/25 route which was matching the 10.10.2.110.10.2.1 to 10.10.2.5010.10.2.50 destination range and routing it directly. Once deleted, Route A (10.10.2.0/2410.10.2.0/24) becomes the longest prefix match, sending all App-Subnet traffic to the NVA's IP. Additionally, IP forwarding must be enabled on the NVA's virtual network interface so that Azure does not drop transit packets.

Adım Adım Çözüm

1
Analyze why traffic to 10.10.2.110.10.2.1 through 10.10.2.5010.10.2.50 bypasses the NVA.
Identify that 10.10.2.110.10.2.1 through 10.10.2.5010.10.2.50 fall within the range of Route B (10.10.2.0/2510.10.2.0/25). Due to Longest Prefix Match (LPM), Route B (/25/25 prefix) takes precedence over Route A (/24/24 prefix). Therefore, traffic to these IPs bypasses the NVA and goes directly via the Virtual Network.
Azure route selection logic always selects the route with the longest matching prefix.
2
Remove the bypassing route to force all traffic to Route A.
Delete Route B from the RT-Web route table. This leaves Route A (10.10.2.0/2410.10.2.0/24) as the longest matching route for all destinations in App-Subnet.
Without the /25/25 route, the /24/24 user-defined route is matched, redirecting all App-Subnet traffic to the NVA.
3
Configure the NVA to allow routing of transit traffic.
Enable IP forwarding on the virtual network interface of NVA-Sec.
By default, Azure drops packets not addressed to the receiving network interface. Enabling IP forwarding allows the NVA to route transit traffic.

Anahtar Kavram

Azure routes traffic using the Longest Prefix Match (LPM) rule. User-defined routes override system routes of the same prefix length, but a more specific route (longer prefix) always wins. Additionally, virtual network interfaces in Azure drop packets not addressed to themselves unless IP forwarding is explicitly enabled.
Tahmini Süre:1m 30s
Soru 898Soru

You have an Azure virtual machine named VM1 that is backed up to a Recovery Services vault. A critical operating system corruption occurs, and VM1 fails to boot. You need to restore VM1 from a backup. The restored virtual machine must retain the original resource ID, network interface cards (NICs), and IP configurations of VM1. Which restore option should you select?

Cevabı ve açıklamayı göster

Cevap: Replace existing

Cevap

Replace existing
The correct option is 'Replace existing'. When restoring an Azure VM using Azure Backup, the 'Replace existing' option is designed to swap the corrupted disks of the existing VM with the disks from the selected restore point. This process preserves the VM's hardware configuration, resource ID, network interface cards (NICs), and IP configurations.

Adım Adım Çözüm

1
Identify the primary requirement: restore a corrupted, non-bootable VM while retaining its original identity and network configuration (resource ID, NICs, IP addresses).
Requires a restore method that keeps the existing VM configuration shell intact.
Creating a new VM changes these configurations, whereas restoring disks requires manual rebuilding.
2
Evaluate the Azure VM restore options: 'Create new', 'Replace existing', and 'Restore disks'.
The 'Replace existing' option swaps the OS and data disks on the current VM with those from the restore point, keeping all metadata and network interfaces unchanged.
This directly satisfies the requirement with minimal administrative effort and zero configuration drift.

Anahtar Kavram

Azure VM restore options allow administrators to choose between creating a new VM, replacing disks on the existing VM, or restoring VHDs to a storage account. To retain the exact virtual machine shell (resource ID, NICs, and IPs), the 'Replace existing' option must be used.
Soru 899Soru

An administrator is configuring security for an internal web server named `Server1` (private IP address 10.1.1.410.1.1.4) using an Azure Firewall. The administrator creates a Destination Network Address Translation (DNAT) rule that translates incoming HTTP traffic from the firewall's public IP address (40.120.50.1040.120.50.10) on port 8080 to `Server1` on port 8080. The administrator must block traffic from a specific external IP address (198.51.100.25198.51.100.25) to `Server1` while continuing to allow HTTP traffic from all other internet sources. Which configuration should the administrator add to the Azure Firewall?

Cevabı ve açıklamayı göster

Cevap: A Network rule with Action: Deny, Source: 198.51.100.25198.51.100.25, Destination: 10.1.1.410.1.1.4, Destination Port: 8080

Cevap

A Network rule with Action: Deny, Source: 198.51.100.25198.51.100.25, Destination: 10.1.1.410.1.1.4, Destination Port: 8080
The correct configuration is to add a Deny Network rule targeting the server's private IP address (10.1.1.410.1.1.4). When inbound traffic matches a DNAT rule on Azure Firewall, the destination IP address is translated to the private IP address of the backend server. The firewall then evaluates Network rules against the translated packet. To block traffic from a specific source, the Deny Network rule must specify the post-translation destination IP (10.1.1.410.1.1.4).

Adım Adım Çözüm

1
Analyze the rule processing order of Azure Firewall for incoming traffic.
Azure Firewall processes DNAT rules first, before evaluating Network and Application rules.
Understanding the sequence ensures that we account for destination IP translation prior to subsequent filter evaluations.
2
Determine the state of the packet when it is evaluated by Network rules.
The packet's destination IP address is translated from the public IP (40.120.50.1040.120.50.10) to the server's private IP (10.1.1.410.1.1.4).
Since DNAT occurs first, any following Network rules will see the translated private IP address as the destination.
3
Configure the Network rule to override the implicit allow rule created by the DNAT match.
Add a Network rule with Action: Deny, targeting the source IP 198.51.100.25198.51.100.25 and the post-translation destination IP 10.1.1.410.1.1.4.
An explicit Deny Network rule matches the post-translation destination and successfully drops the traffic before it reaches the backend.

Anahtar Kavram

Azure Firewall processes DNAT rules first, and subsequent Network rules are evaluated against the translated (private) destination IP address rather than the original public IP address.
Soru 900Soru

You have an Azure subscription that contains a Log Analytics workspace named Workspace1. You need to ensure that Workspace1 stops accepting data and stops incurring charges for the rest of the day if the volume of ingested data in a single day reaches 10 GB. What should you configure in Workspace1?

Cevabı ve açıklamayı göster

Cevap: A daily cap of 10 GB

Cevap

A daily cap of 10 GB
Configuring a daily cap of 10 GB on the Log Analytics workspace is the correct solution. Once the daily cap is met, the workspace stops accepting new data for the remainder of the UTC day, preventing additional ingestion charges.

Adım Adım Çözüm

1
Analyze the requirement to halt data ingestion and prevent billing charges when a specific data volume threshold is reached in a Log Analytics workspace.
Identify that the configuration must apply directly to data ingestion volume on the workspace level.
This helps narrow down settings applicable directly to the Log Analytics workspace rather than subscription or alert configurations.
2
Evaluate the workspace-level features in Azure.
Select 'daily cap' as the feature designed to manage data ingestion limits and halt ingestion to prevent extra costs.
The daily cap setting specifically stops data ingestion for the rest of the day once the limit is reached.

Anahtar Kavram

Configuring a daily cap in a Log Analytics workspace to control costs and limit daily data ingestion.
ÖncekiSayfa 45 / 63Sonraki
Tüm alıştırma soruları — Microsoft Azure Administrator (AZ-104) | Examkin