Tüm alıştırma soruları

1252 soru

Soru 1181Soru

You manage a Premium storage account named saeastprod01 that hosts an SMB file share named sharesmbprod. The storage account has its firewall enabled, restricting access to selected networks. You need to configure Azure Backup using a Recovery Services vault named rsv-eastus-prod to back up the SMB file share.

Arrange the steps in the correct sequence to configure and run the first backup.

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

Cevabı ve açıklamayı göster

Cevap

Configure the storage account firewall to allow trusted Microsoft services, discover the storage account from the Recovery Services vault, select the SMB file share and associate a backup policy, and then enable the backup and trigger an on-demand backup.
To successfully configure and run a backup for an SMB file share in a firewalled Premium storage account, the network path must first be cleared by enabling the 'Allow trusted Microsoft services to access this storage account' bypass. Next, the storage account must be discovered from the Recovery Services vault. Then, the SMB file share is associated with a backup policy, and finally, the backup is enabled and triggered on-demand.

Adım Adım Çözüm

1
Modify the Premium storage account's network firewall settings.
The 'Allow trusted Microsoft services to access this storage account' setting is enabled.
Azure Backup requires this bypass to interact with the Premium storage account's SMB file share when firewalls are active.
2
Initiate backup configuration in the Recovery Services vault and select the Premium storage account.
The vault discovers the storage account.
The vault must establish a connection to the storage account before it can list the hosted file shares.
3
Select the SMB file share and associate a backup policy.
The backup policy configuration is linked to the SMB file share.
A backup policy is required to define how often backups are taken and how long recovery points are retained.
4
Enable the backup and run an on-demand backup.
The initial backup job starts and creates the first recovery point.
Enabling the backup registers the share for scheduled runs, and executing an on-demand backup ensures immediate protection.

Anahtar Kavram

Configuring Azure Backup for Azure Files SMB file shares behind a storage account firewall
Soru 1182Soru

Your company has a public website hosted externally with the domain name `www.contoso.com` and its DNS records managed in a public Azure DNS zone. You plan to configure split-horizon DNS by deploying an Azure Private DNS zone named `contoso.com` to resolve internal hostnames for virtual machines in a virtual network named `VNet1`. You must ensure that virtual machines in `VNet1` can resolve `www.contoso.com` without service interruption, and that new virtual machines deployed to `VNet1` automatically register their hostnames in the private DNS zone. In which sequence 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: first, create the Private DNS zone; second, manually create the public CNAME record in the private zone; third, link the virtual network with auto-registration enabled; and fourth, start the virtual machines to trigger automatic registration.
First, the Private DNS zone must be created. Second, the public CNAME record must be manually added to the private zone before linking to prevent name resolution outages for the public website. When a private DNS zone matches a public namespace, Azure DNS does not forward queries for missing records to the public zone. Third, the Virtual Network link to the target VNet must be established with auto-registration enabled. Finally, the virtual machines must be started so they can register their hostnames automatically upon network initialization.

Adım Adım Çözüm

1
Create the Private DNS zone named `contoso.com`.
The private namespace is established in Azure.
This is the prerequisite container for all private records and links.
2
Manually create the CNAME record for the public service `www` in the private DNS zone.
The private DNS zone now contains the pointer to the external endpoint.
This prevents service disruption because Azure DNS will not query public zones for any records under a namespace that has a linked private zone.
3
Create a Virtual Network link from the private DNS zone to `VNet1` and enable auto-registration.
The virtual network is now linked to the private DNS zone.
This enables name resolution within the virtual network and prepares the zone to accept automatic hostname registrations.
4
Start the virtual machines inside `VNet1`.
The virtual machines register their names in the private DNS zone.
The VMs trigger name registration upon startup when the virtual network link is already present.

Anahtar Kavram

In a split-horizon DNS deployment, Azure DNS resolves all queries for a namespace using the linked private DNS zone. If a record is not found in the private zone, Azure DNS does not fall back to the public DNS zone. Therefore, public records must be recreated in the private zone before linking it to the virtual network to avoid service disruption.
Soru 1183Soru

You have an Azure Bastion host named `bastion-corp-east` that is used to manage virtual machines. You must configure diagnostic logging for the Bastion host to meet the following requirements:

* Capture audit logs for all user remote sessions.
* Retain the session logs for 180 days.
* Ensure the logs can be queried directly using the Kusto Query Language (KQL).

Which diagnostic setting configuration should you implement?

Cevabı ve açıklamayı göster

Cevap: Create a diagnostic setting on `bastion-corp-east` that forwards the `BastionAuditLogs` category to a Log Analytics workspace, and set the data retention period of the workspace to 180 days.

Cevap

Create a diagnostic setting on `bastion-corp-east` that forwards the `BastionAuditLogs` category to a Log Analytics workspace, and set the data retention period of the workspace to 180 days.
The correct configuration forwards the `BastionAuditLogs` category to a Log Analytics workspace. This workspace natively supports Kusto Query Language (KQL) queries. The data retention period must be managed at the workspace level, which is set to 180 days.

Adım Adım Çözüm

1
Identify the correct log category for Azure Bastion session auditing.
The correct log category is `BastionAuditLogs`, which contains remote session connection details.
Tracking user remote sessions requires capturing audit logs rather than performance metrics (`AllMetrics`).
2
Identify the correct destination for querying logs with Kusto Query Language (KQL).
The destination must be a Log Analytics workspace.
Neither Azure Storage accounts nor Azure Event Hubs support direct, native KQL queries on stored log data.
3
Configure the retention settings for the collected logs.
Set the default data retention on the Log Analytics workspace to 180 days.
Diagnostic settings no longer support built-in retention configuration for storage destinations; retention must be configured on the destination workspace or storage account lifecycle policies.

Anahtar Kavram

Azure Monitor Diagnostic Settings routing and log categories for Azure Bastion, including destination-based retention policies.
Tahmini Süre:1m 30s
Soru 1184Soru

Your company has an Azure subscription named Sub-Ops-01 that contains the resources shown in the following table:

Resource GroupResource NameResource TypeRegion
RG-Core-ResourcesVM-HR-01Virtual MachineEast US
RG-Core-ResourcesVM-Finance-01Virtual MachineWest US 3
RG-Core-ResourcessahrdepotStorage Account (Azure Files)East US
RG-Backup-ResourcesRSV-EastRecovery Services VaultEast US
RG-Backup-ResourcesBV-EastBackup VaultEast US

You need to configure backup solutions for the resources using the existing vaults.

Which two configurations can you successfully implement? (Select two.)

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

Cevabı ve açıklamayı göster

Cevap: Back up VM-HR-01 to RSV-East.; Back up the Azure File shares in sahrdepot to RSV-East.

Cevap

The correct configurations are backing up VM-HR-01 to RSV-East, and backing up the Azure File shares in sahrdepot to RSV-East.
Configuring the backup of the virtual machine VM-HR-01 to RSV-East is correct because they reside in the same region (East US) and Recovery Services Vaults support virtual machine backups. Configuring the backup of the Azure File shares in sahrdepot to RSV-East is correct because they both reside in the same region and Recovery Services Vaults support Azure Files.

Adım Adım Çözüm

1
Determine regional and vault requirements for the virtual machine VM-HR-01.
VM-HR-01 resides in East US. Backing up an Azure VM requires a Recovery Services Vault in the same region.
Since RSV-East is a Recovery Services Vault in East US, backing up VM-HR-01 to RSV-East is a valid configuration.
2
Determine regional and vault requirements for the Azure File shares in sahrdepot.
sahrdepot resides in East US. Backing up Azure Files requires a Recovery Services Vault in the same region.
Since RSV-East is a Recovery Services Vault in East US, backing up the file shares in sahrdepot to RSV-East is a valid configuration.
3
Evaluate the invalid configurations for VM-Finance-01 and the Backup Vault.
VM-Finance-01 is in West US 3 and cannot be backed up to RSV-East due to the regional mismatch. The Azure File shares in sahrdepot cannot use BV-East because Backup Vaults do not support Azure Files backups.
Azure VM backups are restricted to the same region as the vault, and Backup Vaults support a different matrix of workloads (like Azure Disks and Blobs) compared to Recovery Services Vaults.

Anahtar Kavram

Recovery Services Vaults and Backup Vaults have distinct workload support matrices, and resource backups must align with the vault's region.
Tahmini Süre:1m 30s
Soru 1185Soru

An organization deploys a hub-and-spoke network topology in Azure containing three virtual networks:

* `VNet-Hub` (10.10.0.0/1610.10.0.0/16) containing a subnet with `VM-Hub` deployed.
* `VNet-SpokeA` (10.20.0.0/1610.20.0.0/16) containing a subnet with `VM-SpokeA` deployed.
* `VNet-SpokeB` (10.30.0.0/1610.30.0.0/16) containing a subnet with `VM-SpokeB` deployed.

Virtual network peering is configured between `VNet-Hub` and `VNet-SpokeA`, and between `VNet-Hub` and `VNet-SpokeB`. The settings 'Allow forwarded traffic', 'Use remote gateways', and 'Allow gateway transit' are currently left at their default values of disabled.

An administrator reports that `VM-SpokeA` cannot communicate with `VM-SpokeB` over the peered networks.

Which of the following actions should the administrator take to establish direct network connectivity between `VM-SpokeA` and `VM-SpokeB` with the minimum administrative effort?

Cevabı ve açıklamayı göster

Cevap: Create a virtual network peering directly between VNet-SpokeA and VNet-SpokeB.

Cevap

Create a virtual network peering directly between VNet-SpokeA and VNet-SpokeB.
The correct option is to create a direct virtual network peering between the two spokes. Because Azure virtual network peering is non-transitive, traffic cannot transit from one spoke to another via the hub without a router or gateway. A direct peering link is the most efficient solution because it requires no additional infrastructure or route tables.

Adım Adım Çözüm

1
Analyze the existing topology and identify the connectivity gap.
VM-SpokeA in VNet-SpokeA cannot reach VM-SpokeB in VNet-SpokeB because virtual network peering is non-transitive by default.
Before applying a fix, the administrator must confirm that traffic between two spoke networks cannot transit through a peered hub without an active routing mechanism (like a gateway or network virtual appliance).
2
Determine the path of least resistance to connect the two spoke VNets directly.
Since both spokes are in the same or peered regions, creating a direct virtual network peering link between VNet-SpokeA and VNet-SpokeB is the simplest, most performant solution.
Direct peering avoids the need to deploy and manage a hub routing appliance (NVA/Firewall) or write complex routing tables (UDRs).
3
Configure the bidirectional peering links between the spokes.
Establish peering from VNet-SpokeA to VNet-SpokeB, and VNet-SpokeB to VNet-SpokeA.
Virtual network peering must be configured in both directions to establish complete data plane connectivity.

Anahtar Kavram

Azure Virtual Network Peering is non-transitive. Spoke-to-spoke communication requires either a direct peering link between spokes or an intermediate routing appliance (NVA) in the hub coupled with custom route tables (UDRs).
Soru 1186Soru

You manage a Premium storage account named stcorpfiles01 in the East US 2 region. The storage account hosts an SMB file share named sharesmbcore and has its firewall configured to restrict access to selected virtual networks. You configure a Recovery Services vault named rsv-corp-backup in the same region to back up the file share. When you attempt to configure the backup, the operation fails because the vault cannot access the storage account. Which configuration is required on the storage account to resolve this issue?

Cevabı ve açıklamayı göster

Cevap: Enable the 'Allow trusted Microsoft services to access this storage account' bypass option under the Firewalls and virtual networks settings.

Cevap

Enable the 'Allow trusted Microsoft services to access this storage account' bypass option under the Firewalls and virtual networks settings.
The correct option is to enable the 'Allow trusted Microsoft services to access this storage account' bypass option. When an Azure Storage account firewall is enabled, Azure Backup requires this bypass to interact with the storage account and take the snapshots required for backing up the file shares.

Adım Adım Çözüm

1
Identify the cause of the backup failure.
The backup fails because the storage account firewall blocks incoming requests from the Recovery Services vault.
By default, when a storage account firewall is enabled, all external access is blocked unless specifically permitted.
2
Determine the correct bypass mechanism for Azure Backup.
Azure Backup is classified as a trusted Microsoft service.
Rather than allowing specific IP addresses or virtual networks, Azure provides a built-in exception setting for its own trusted services.
3
Configure the bypass option in the Azure portal or CLI.
The firewall allows the Recovery Services vault to orchestrate snapshots and perform backup tasks.
Enabling the 'Allow trusted Microsoft services...' exception resolves the connectivity issue while maintaining the firewall restriction for other network traffic.

Anahtar Kavram

Azure Files Backup and Restore
Tahmini Süre:1m 30s
Soru 1187Soru

An administrator is configuring connectivity for an Azure environment containing the following resources:
* `VNet-Hub` (10.100.0.0/1610.100.0.0/16) with a virtual network gateway and virtual machines deployed in its subnets.
* `VNet-SpokeA` (10.101.0.0/1610.101.0.0/16) with virtual machines deployed in its subnets.

You configure virtual network peering between `VNet-Hub` and `VNet-SpokeA`. Virtual machines in `VNet-SpokeA` must be able to use the virtual network gateway in `VNet-Hub` to communicate with an on-premises network.

Which of the following configuration settings must be enabled on the peerings to achieve this goal? (Select two.)

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

Cevabı ve açıklamayı göster

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

Cevap

Enable 'Allow gateway transit' on the peering configuration from VNet-Hub to VNet-SpokeA, and enable 'Use remote gateways' on the peering configuration from VNet-SpokeA to VNet-Hub.
To configure gateway transit across peered virtual networks, you must configure settings on both ends of the peering connection. The virtual network containing the gateway (VNet-Hub) must be configured to allow transit by enabling 'Allow gateway transit'. The virtual network that will use the gateway (VNet-SpokeA) must be configured to use the remote gateway by enabling 'Use remote gateways'.

Adım Adım Çözüm

1
Configure the hub-to-spoke peering direction settings.
The peering link from VNet-Hub to VNet-SpokeA is configured with 'Allow gateway transit' enabled.
This grants permission for the peered VNet-SpokeA to utilize the virtual network gateway hosted within VNet-Hub.
2
Configure the spoke-to-hub peering direction settings.
The peering link from VNet-SpokeA to VNet-Hub is configured with 'Use remote gateways' enabled.
This instructs VNet-SpokeA to route traffic destined for remote networks (like on-premises) via the gateway in VNet-Hub.

Anahtar Kavram

Virtual Network Peering Gateway Transit
Soru 1188Soru

You are setting up Azure Backup Reports to analyze the historical backup compliance of several workloads protected by multiple Recovery Services vaults. You need to ensure that the backup report data is populated and accessible for reporting via the Azure portal. Which of the following configuration actions should you perform? (Select two)

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

Cevabı ve açıklamayı göster

Cevap: Configure a diagnostic setting on each Recovery Services vault to route logs to a Log Analytics workspace.; Select the resource-specific log categories, including CoreBackup and AddonAzureBackupJobs, in the vault diagnostic settings.

Cevap

Configure a diagnostic setting on each Recovery Services vault to route logs to a Log Analytics workspace, and select the resource-specific log categories, including CoreBackup and AddonAzureBackupJobs, in the vault diagnostic settings.
To populate Azure Backup Reports, data must be sent from the Recovery Services vaults to a Log Analytics workspace. Configuring diagnostic settings on each vault to route logs to a Log Analytics workspace ensures the data is central and queryable. Selecting the resource-specific log categories (including CoreBackup and AddonAzureBackupJobs) sends the correct schema and operational events needed by the reporting interface.

Adım Adım Çözüm

1
Identify the data repository requirement for Azure Backup Reports.
Determine that Azure Backup Reports query diagnostic logs stored in a Log Analytics workspace.
Log Analytics workspace acts as the central storage repository that Backup Reports use to compile historical data.
2
Determine the source of the reporting data.
Identify that the Recovery Services vaults host the backup data, requiring diagnostic settings to be configured on the vaults themselves, not on the protected resources.
The vault tracks the job status, policies, and protected items, which are the metadata needed for reporting.
3
Select the appropriate log categories in the diagnostic settings.
Enable the resource-specific categories (like CoreBackup, AddonAzureBackupJobs, AddonAzureBackupPolicy, etc.) to feed data into the workspace.
Choosing these specific logs ensures that only the required backup metadata is sent, providing all necessary reporting data while managing ingestion costs.

Anahtar Kavram

Azure Backup Reports are populated by configuring Recovery Services vaults to send diagnostic logs (using resource-specific tables like CoreBackup and AddonAzureBackupJobs) to a Log Analytics workspace.
Soru 1189Soru

An administrator is configuring backups for the resources in an Azure subscription named Sub-CloudAdmin-Prod. The subscription contains the resources shown in the following table:

Resource NameResource TypeRegion
vm-billing-neVirtual machineNorth Europe
vm-shipping-weVirtual machineWest Europe
rsv-billing-neRecovery Services vaultNorth Europe
bv-shipping-weBackup vaultWest Europe
sa-shipping-dataStorage account (contains share-shipping)West Europe

The administrator needs to configure backups for vm-shipping-we and the Azure file share named share-shipping.

Which backup configuration should the administrator use?

Cevabı ve açıklamayı göster

Cevap: Create a new Recovery Services vault in West Europe, and configure it to back up both vm-shipping-we and share-shipping.

Cevap

Create a new Recovery Services vault in West Europe, and configure it to back up both vm-shipping-we and share-shipping.
To back up Azure Virtual Machines and Azure File Shares, a Recovery Services vault must be used. Additionally, the Recovery Services vault must be located in the same region as the source resources. Since both the virtual machine and the storage account containing the file share are in the West Europe region, a new Recovery Services vault must be created in West Europe to configure backups for both resources.

Adım Adım Çözüm

1
Identify the vault type required for each target resource.
Azure Virtual Machines and Azure File Shares both require a Recovery Services vault for backup configuration (Backup vaults support disks, blobs, and select databases).
Choosing the correct vault type is necessary because Backup vaults and Recovery Services vaults support distinct workloads.
2
Determine the regional constraints for the backup vault alignment.
The vault must reside in the same region as the target resources (West Europe for both vm-shipping-we and the storage account).
Azure Backup does not support backing up virtual machines or file shares to a Recovery Services vault located in a different region.
3
Select or create the appropriate vault in the target region.
Since the existing Recovery Services vault (rsv-billing-ne) is in North Europe and the existing Backup vault (bv-shipping-we) is of the wrong vault type, a new Recovery Services vault must be deployed in West Europe.
This satisfies both the regional constraint and the workload support matrix requirements for both resources.

Anahtar Kavram

Recovery Services vaults support virtual machine and file share backups, and must reside in the same region as the source resources.
Tahmini Süre:1m 30s
Soru 1190Soru

Your company is setting up a secure hybrid cloud environment in Azure. You have deployed a virtual network named `Prod-VNet-01` in the East US 2 region. The virtual network contains multiple virtual machines that host a line-of-business application.

You need to deploy Azure Bastion to enable secure administrative access to the virtual machines. You must ensure that the subnet used by Azure Bastion is secured with a Network Security Group (NSG) before the Bastion host starts receiving traffic.

Which three actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order.

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

Cevabı ve açıklamayı göster

Cevap

To configure Azure Bastion, first create a subnet named AzureBastionSubnet with an address prefix of /26/26. Next, create a Network Security Group (NSG) configured with the mandatory rules for Azure Bastion, and associate it with the AzureBastionSubnet. Finally, deploy the Azure Bastion host and associate it with the AzureBastionSubnet and a Standard SKU static public IP address.
To deploy Azure Bastion, you must follow a specific sequence. First, create a dedicated subnet named exactly AzureBastionSubnet with a prefix size of /26/26 or larger. Second, create a Network Security Group (NSG) with the correct rules and associate it with the AzureBastionSubnet. Third, deploy the Azure Bastion host and associate it with both the subnet and a Standard SKU static public IP address.

Adım Adım Çözüm

1
Create the AzureBastionSubnet subnet
A dedicated subnet named AzureBastionSubnet with a /26/26 prefix is created in the virtual network.
Azure Bastion requires a dedicated subnet named exactly AzureBastionSubnet with a prefix of /26/26 or larger.
2
Create and associate the NSG
An NSG with mandatory rules is associated with the AzureBastionSubnet.
The subnet must be secured with the correct NSG inbound/outbound rules before the Bastion host is deployed.
3
Deploy the Azure Bastion host
The Bastion host is provisioned using the subnet and a Standard SKU static public IP.
The Bastion host is the final resource deployed, binding the subnet and public IP together.

Anahtar Kavram

Deploying and securing Azure Bastion requires a dedicated subnet named AzureBastionSubnet of size /26/26 or larger, an associated NSG with mandatory rules, and a Standard SKU static public IP address.
Tahmini Süre:2m 0s
Soru 1191Soru

You have an Azure Application Gateway named `appgw-prod` that has Web Application Firewall (WAF) enabled.

You need to collect the WAF firewall logs to meet the following requirements:
- Run interactive KQL queries on the logs inside the Azure portal.
- Stream the logs to an external, third-party Security Information and Event Management (SIEM) system in real-time.

Which diagnostic settings configuration should you implement for `appgw-prod`?

Cevabı ve açıklamayı göster

Cevap: Create a single diagnostic setting. Select the `ApplicationGatewayFirewallLog` log category, and configure the destinations to send to both a Log Analytics workspace and an Event Hub.

Cevap

Create a single diagnostic setting. Select the ApplicationGatewayFirewallLog log category, and configure the destinations to send to both a Log Analytics workspace and an Event Hub.
To satisfy both requirements, the firewall logs must be sent to a Log Analytics workspace for interactive KQL querying and to an Event Hub for real-time streaming to a third-party SIEM. Azure Monitor diagnostic settings allow selecting multiple destinations within a single configuration.

Adım Adım Çözüm

1
Determine the destination needed for running interactive KQL queries.
Log Analytics workspace is identified as the required destination.
Only Log Analytics workspaces support native KQL queries in Azure Monitor.
2
Determine the destination needed for streaming logs to an external third-party SIEM in real-time.
Event Hub is identified as the required destination.
Event Hubs are designed to ingest and stream telemetry data to external systems in near real-time.
3
Configure the diagnostic setting on the Application Gateway resource.
A single diagnostic setting is created with the ApplicationGatewayFirewallLog category selected and both Log Analytics and Event Hub checked as destinations.
Azure diagnostic settings support sending selected log categories to multiple destinations simultaneously.

Anahtar Kavram

Azure Monitor diagnostic settings allow you to route resource logs to different destinations (Log Analytics workspaces, Storage accounts, Event Hubs, or partner solutions) depending on your querying, retention, and integration requirements.
Soru 1192Soru

An administrator configures three Azure virtual networks named `VNet1` (10.1.0.0/1610.1.0.0/16), `VNet2` (10.2.0.0/1610.2.0.0/16), and `VNet3` (10.3.0.0/1610.3.0.0/16). Virtual machines are deployed in the subnets of each virtual network to run active workloads. Peering is configured between `VNet1` and `VNet2`, and between `VNet2` and `VNet3`. The peering links have 'Allow forwarded traffic' enabled on both sides, but 'Allow gateway transit' and 'Use remote gateways' are disabled. No user-defined routes (UDRs) or virtual network gateways exist in any of the networks. Which of the following describes the network connectivity between the virtual machines?

Cevabı ve açıklamayı göster

Cevap: Virtual machines in `VNet1` can communicate with virtual machines in `VNet2`, and virtual machines in `VNet2` can communicate with virtual machines in `VNet3`, but virtual machines in `VNet1` and `VNet3` cannot communicate.

Cevap

Virtual machines in `VNet1` can communicate with virtual machines in `VNet2`, and virtual machines in `VNet2` can communicate with virtual machines in `VNet3`, but virtual machines in `VNet1` and `VNet3` cannot communicate.
The correct answer is correct because Azure Virtual Network Peering is strictly non-transitive. Direct peering connections allow virtual machines in VNet1 to talk to VNet2, and virtual machines in VNet2 to talk to VNet3, but do not allow traffic to flow from VNet1 through VNet2 to VNet3.

Adım Adım Çözüm

1
Analyze the virtual network peering topology.
Peering is configured between VNet1 and VNet2, and between VNet2 and VNet3. No direct peering exists between VNet1 and VNet3.
This establishes which direct network paths are configured.
2
Evaluate the transitivity rule of Azure Virtual Network Peering.
Virtual network peering is non-transitive by default. Traffic from VNet1 cannot transit through VNet2 to reach VNet3.
This determines if indirect communication is possible through peered networks.
3
Assess the configuration settings ('Allow forwarded traffic', 'Allow gateway transit', and 'Use remote gateways').
Since no gateway or virtual appliance is present, enabling 'Allow forwarded traffic' has no effect on transitivity, and gateway transit options cannot be used.
This rules out advanced transit features and confirms that VNet1 and VNet3 remain disconnected.

Anahtar Kavram

Azure Virtual Network Peering is non-transitive, meaning that traffic cannot transit through a peered virtual network to reach another peered network unless transit routing (via Network Virtual Appliances or Virtual Network Gateways) is explicitly configured.
Soru 1193Soru

An organization is designing a disaster recovery virtual network named `DR-VNet` with an address space of 172.16.0.0/16172.16.0.0/16. To allow administrators to securely connect to recovery virtual machines, the organization plans to deploy an Azure Bastion host. The administrator needs to create the dedicated subnet for Azure Bastion.

Which configuration must the administrator use for the new subnet?

Cevabı ve açıklamayı göster

Cevap: Subnet name: AzureBastionSubnet; Address space: 172.16.3.0/26172.16.3.0/26

Cevap

Subnet name: AzureBastionSubnet; Address space: 172.16.3.0/26172.16.3.0/26
The correct configuration uses the required name 'AzureBastionSubnet' and has an address block of 172.16.3.0/26172.16.3.0/26. This meets the mandatory platform constraints: the subnet name must match exactly, and the prefix must be /26/26 or larger (providing at least 64 addresses) to host the Azure Bastion resources.

Adım Adım Çözüm

1
Identify the mandatory subnet name constraint for Azure Bastion.
The dedicated subnet must be named exactly 'AzureBastionSubnet'.
Azure Bastion uses this specific name to bind the service to the network resource.
2
Identify the minimum subnet address block size constraint for Azure Bastion.
The subnet prefix must be /26/26 or larger (e.g., /26/26, /25/25, /24/24).
A minimum prefix of /26/26 provides 64 IP addresses, ensuring enough IP addresses are available for internal scaling and instance management.
3
Filter the options to find the configuration that meets both criteria.
The configuration with the subnet name 'AzureBastionSubnet' and the address block 172.16.3.0/26172.16.3.0/26 is selected.
It satisfies both the strict naming and minimum /26/26 sizing requirements.

Anahtar Kavram

Azure Bastion dedicated subnet naming and prefix size requirements
Tahmini Süre:1m 30s
Soru 1194Soru

An administrator is designing a monitoring strategy for several Azure resources. You need to route diagnostic logs to the appropriate destination based on the monitoring requirements.

Match each monitoring requirement to the correct Azure Monitor diagnostic setting destination.

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

Öğeler

Retain resource logs for 365365 days for compliance auditing at the lowest cost.
Perform complex query analysis and run KQL queries to correlate events across multiple resources.
Stream diagnostic data in real-time to a third-party Security Information and Event Management (SIEM) system.

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

Retaining logs for 365365 days at lowest cost matches the Azure Storage account. Performing complex KQL query analysis matches the Log Analytics workspace. Streaming diagnostic data to a third-party SIEM system matches the Azure Event Hubs namespace.
The correct pairings match each requirement to the primary purpose of the respective Azure resource: Azure Storage for low-cost long-term retention; Log Analytics workspace for KQL analysis; and Event Hubs for real-time external streaming.

Adım Adım Çözüm

1
Analyze the requirement for archiving logs for 365365 days at the lowest cost.
Identify that Azure Storage provides the cheapest long-term archival solution with lifecycle management rules.
Log Analytics and Event Hubs are more expensive for long-term storage and do not offer low-cost archival storage tiers.
2
Analyze the requirement to run interactive KQL queries across resources.
Identify that a Log Analytics workspace is the native repository in Azure Monitor designed for KQL queries, alerts, and dashboards.
Neither Storage Accounts nor Event Hubs natively support KQL querying.
3
Analyze the requirement to stream logs to a third-party SIEM in real-time.
Identify Event Hubs as the native broker for streaming data ingestion to external systems.
Storage accounts are pull/polling-based and Log Analytics is optimized for query-based analytics rather than real-time message streaming.

Anahtar Kavram

Azure Monitor Diagnostic Settings Destinations
Tahmini Süre:1m 30s
Soru 1195Soru

Your company has an Azure environment that contains the resources shown in the following table:

Resource NameResource TypeAzure RegionResource GroupSubscription
VM-Billing-01Virtual machineEast USRG-Finance-ProdSub-FinOps-Prod
VM-Tax-02Virtual machineWest USRG-Finance-ProdSub-FinOps-Prod
Share-LedgerAzure File ShareEast USRG-Finance-ProdSub-FinOps-Prod
Disk-ArchiveManaged diskWest USRG-Finance-ProdSub-FinOps-Prod

You also have the following vaults:
- A Recovery Services Vault named RSV-Finance-East located in the East US region.
- A Backup Vault named BV-Finance-West located in the West US region.

You need to configure backups for the resources using the existing vaults with the correct vault type and regional requirements.

Which two actions can you perform? (Select two options)

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

Cevabı ve açıklamayı göster

Cevap: Back up VM-Billing-01 and Share-Ledger to RSV-Finance-East.; Back up Disk-Archive to BV-Finance-West.

Cevap

The correct actions are to back up VM-Billing-01 and Share-Ledger to RSV-Finance-East, and to back up Disk-Archive to BV-Finance-West.
The actions to back up VM-Billing-01 and Share-Ledger to RSV-Finance-East, and to back up Disk-Archive to BV-Finance-West are correct. Recovery Services Vaults support Azure Virtual Machines and Azure File Shares, both of which align regionally with RSV-Finance-East in East US. Backup Vaults support Azure Managed Disks, which aligns with BV-Finance-West in West US.

Adım Adım Çözüm

1
Determine the support matrix for Recovery Services Vaults and Backup Vaults.
Recovery Services Vaults support Azure Virtual Machines and Azure Files (file shares). Backup Vaults support Azure Managed Disks.
This identifies which vault type is compatible with each resource.
2
Evaluate the regional constraints for each backup configuration.
Azure Virtual Machines, Azure Files, and Azure Managed Disks must be backed up to a vault located in the same region as the source resource.
Azure Backup requires the source resource and the backup vault to reside in the same Azure region.
3
Match the resources to the available vaults based on type and region constraints.
VM-Billing-01 (East US VM) and Share-Ledger (East US File Share) align with RSV-Finance-East (East US RSV). Disk-Archive (West US Managed Disk) aligns with BV-Finance-West (West US Backup Vault). VM-Tax-02 (West US VM) cannot align with RSV-Finance-East (East US RSV).
This determines the valid configuration actions that satisfy all constraints.

Anahtar Kavram

Azure Backup regional alignment and vault workload compatibility
Soru 1196Soru

An organization has multiple Recovery Services vaults in different regions. To enable centralized backup reporting, an administrator configures diagnostic settings on each vault to send data to a central Log Analytics workspace. When viewing the Backup Reports in the Azure Portal, the administrator notices that while the backup jobs, policies, and active alerts are fully populated, the reports contain no data regarding backup storage consumption or monthly storage trends. Which log category must the administrator add to the diagnostic settings of the Recovery Services vaults to resolve this issue?

Cevabı ve açıklamayı göster

Cevap: AddonBackupStorage

Cevap

AddonBackupStorage
The correct answer is the category that logs backup storage data. To populate the storage reports and view storage trends in Azure Backup Reports, the diagnostic settings of the Recovery Services Vaults must be configured to send the specific storage log category. Omitting this category prevents storage utilization and capacity planning data from reaching the Log Analytics workspace, while other reports (like jobs and policies) continue to function if their respective categories are enabled.

Adım Adım Çözüm

1
Identify the missing data type in the Azure Backup Reports dashboard.
The dashboard is missing backup storage consumption and monthly storage trends.
This indicates that the storage-related diagnostic logs are not being sent to the Log Analytics workspace.
2
Recall the Azure Backup resource-specific diagnostic log categories.
The categories include CoreBackup, AddonBackupJobs, AddonBackupAlerts, AddonBackupStorage, AddonBackupPolicy, AddonBackupProtectedInstance, and AddonBackupMetadata.
Each category routes specific diagnostic data to its corresponding Log Analytics table.
3
Select the log category that maps to storage consumption and trends.
The log category is AddonBackupStorage.
Enabling this category ensures that storage-related logs are collected, allowing the storage reports to display data.

Anahtar Kavram

Azure Backup diagnostic settings and Log Analytics integration for Backup Reports
Soru 1197Soru

An administrator is creating a custom Log Analytics query to report on failed backup jobs and identify the specific Azure virtual machines associated with those failures. The diagnostic settings on the Recovery Services Vaults are configured to use the resource-specific destination tables. Which two tables must the administrator query and join to retrieve this information? Select two.

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

Cevabı ve açıklamayı göster

Cevap: AddonBackupJobs; CoreBackup

Cevap

The correct tables are AddonBackupJobs and CoreBackup.
In resource-specific diagnostic mode, Azure Backup routes diagnostic logs to specialized tables. AddonBackupJobs stores status information and failure details for backup operations, while CoreBackup stores item-level metadata including resource names (such as virtual machines). Joining these tables on the unique identifier allows administrators to correlate failed jobs with their target resources.

Adım Adım Çözüm

1
Identify the diagnostic logging mode configured on the Recovery Services Vault.
The resource-specific mode is configured, which routes data to distinct, dedicated tables instead of a single generic table.
This determines which tables are available for querying within Log Analytics.
2
Locate the table containing job execution metadata and status.
AddonBackupJobs contains columns such as JobStatus, JobFailureCode, and BackupItemUniqueId.
To filter for failed backup jobs, the query must target the status records stored in this table.
3
Locate the table containing backup item configuration details and virtual machine metadata.
CoreBackup contains details such as BackupItemName, BackupItemType, and BackupItemUniqueId.
To retrieve the actual name of the virtual machine associated with the failed job, this table must be joined on the unique backup item identifier.

Anahtar Kavram

Azure Backup resource-specific diagnostics schema
Soru 1198Soru

An administrator is preparing to deploy Azure Bastion to secure administrative access to virtual machines in a virtual network named `TransitHub-VNet`. The virtual network has an address space of 10.200.0.0/1610.200.0.0/16.

Which of the following configuration settings must be applied to ensure a successful deployment and operation of the Azure Bastion host? (Select TWO)

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

Cevabı ve açıklamayı göster

Cevap: A subnet named AzureBastionSubnet with an address prefix of at least /26.; An inbound security rule in the Network Security Group (NSG) associated with the Bastion subnet that allows HTTPS traffic on port 443 from the GatewayManager service tag.

Cevap

To configure Azure Bastion, the subnet must be named exactly AzureBastionSubnet with a prefix of /26 or larger, and the associated Network Security Group (NSG) must allow inbound traffic on port 443 from the GatewayManager service tag.
The correct settings require creating a subnet named exactly AzureBastionSubnet with an address prefix of at least /26, and configuring the Network Security Group (NSG) to allow inbound traffic on port 443 from the GatewayManager service tag. The subnet naming and size are hard requirements for provisioning. Additionally, Gateway Manager communication is necessary for Bastion control plane operations.

Adım Adım Çözüm

1
Define the subnet configuration for Azure Bastion.
A subnet named exactly AzureBastionSubnet with an address prefix of /26 or larger is created.
Azure Bastion requires a dedicated subnet with this exact name and a minimum prefix size of /26 to accommodate scaling and administrative traffic.
2
Configure Network Security Group (NSG) inbound rules for the Bastion subnet.
An inbound rule allows HTTPS traffic on port 443 from the GatewayManager service tag.
Azure Gateway Manager needs to communicate with the Azure Bastion host on port 443 to manage deployment and operations.

Anahtar Kavram

Deploying Azure Bastion requires a dedicated subnet named AzureBastionSubnet (minimum /26 size) and specific NSG rules, including inbound traffic on port 443 from the GatewayManager service tag and outbound traffic to the Internet for health monitoring and diagnostics.
Soru 1199Soru

Your company plans to implement secure, browser-based administrative access to Azure virtual machines in a virtual network named `VNet-Corp-01`. The virtual network is configured with an address space of 10.50.0.0/1610.50.0.0/16. You need to create a dedicated subnet for the Azure Bastion resource. What is the correct subnet name and the minimum subnet mask required for this deployment?

Cevabı ve açıklamayı göster

Cevap: Subnet name: `AzureBastionSubnet`; minimum prefix size: /26/26

Cevap

The subnet name must be exactly AzureBastionSubnet, and the minimum prefix size must be /26.
The correct configuration requires the dedicated subnet to be named exactly 'AzureBastionSubnet' and to have a prefix length of /26 or larger. This ensures proper service mapping and sufficient IP allocation for the Bastion instance scaling.

Adım Adım Çözüm

1
Determine the required naming convention for the dedicated subnet.
The subnet must be named exactly `AzureBastionSubnet`.
Azure Bastion uses this specific name to bind the gateway resources and route traffic within the virtual network.
2
Identify the minimum address space prefix requirement for the Bastion subnet.
The subnet must have a subnet mask prefix of /26/26 or larger.
A prefix of /26/26 provides at least 64 IP addresses, which are necessary for Azure Bastion's platform management, scaling, and private endpoints.
3
Select the option that matches both naming and sizing constraints.
Select the subnet named `AzureBastionSubnet` with a minimum prefix size of /26/26.
This is the only configuration that satisfies all Azure platform deployment requirements.

Anahtar Kavram

Azure Bastion subnet requirements
Soru 1200Soru

You have an Azure Key Vault named `kv-finance`.

You need to configure diagnostic logging for `kv-finance` to satisfy the following requirements:
- All key vault access logs (`AuditEvent`) must be queryable using KQL.
- The logs must be archived for 365 days to meet compliance regulations.
- Storage costs for the archived logs must be minimized.

Which configuration should you implement?

Cevabı ve açıklamayı göster

Cevap: Create a single diagnostic setting on `kv-finance` to send `AuditEvent` logs to a Log Analytics workspace and an Azure Storage account. Configure a lifecycle management policy on the storage account to delete data after 365 days.

Cevap

Create a single diagnostic setting on the Key Vault to send the audit logs to both a Log Analytics workspace and an Azure Storage account, then configure a lifecycle management policy on the storage account to manage the 365-day retention.
The correct configuration uses a single diagnostic setting to send the logs to both the Log Analytics workspace (for queryability) and the Azure Storage account (for low-cost archiving). Since Azure Monitor diagnostic settings no longer support direct retention settings, configuring a lifecycle management policy on the storage account is the correct way to delete logs after 365 days.

Adım Adım Çözüm

1
Determine the logging requirements for KQL analysis.
Identify that logs must be sent to a Log Analytics workspace to enable KQL querying.
Log Analytics is the only Azure Monitor destination that supports running KQL queries directly on the diagnostic logs.
2
Determine the archiving and retention strategy.
Identify that logs must be sent to an Azure Storage account for long-term archiving to minimize costs, and that retention must be configured via storage lifecycle management.
Log Analytics retention is expensive for long-term archiving (365 days), and diagnostic settings have deprecated direct retention configurations. Azure Storage with lifecycle policies is the cost-effective and supported solution.
3
Select the correct diagnostic settings configuration.
Select the option that routes the logs to both destinations in a single diagnostic setting and uses storage lifecycle rules for retention.
This satisfies all requirements of queryability, retention duration, and cost minimization while aligning with current Azure capabilities.

Anahtar Kavram

Azure Monitor diagnostic settings support routing resource logs to multiple destinations, including Log Analytics workspaces for querying and Storage accounts for cost-effective long-term retention using lifecycle management rules.
ÖncekiSayfa 60 / 63Sonraki
Tüm alıştırma soruları — Microsoft Azure Administrator (AZ-104) | Examkin