Tüm alıştırma soruları

1198 soru

Soru 881Soru

A logistics company requires an external customs broker to upload shipping manifests to a specific Azure Blob Storage container named 'customs-docs' for a period of 90 days. The access method must satisfy the following requirements:
- Access must be limited strictly to the 'customs-docs' container.
- If the broker's contract is terminated early, access must be immediately revocable without changing storage account access keys or impacting other applications.
- The customs broker must not be required to authenticate via Microsoft Entra ID.

Which of the following access control methods should you implement?

Cevabı ve açıklamayı göster

Cevap: A service Shared Access Signature (SAS) token generated from a stored access policy on the container

Cevap

A service Shared Access Signature (SAS) token generated from a stored access policy on the container
The correct option provides a secure way to delegate container-scoped access to external entities without Entra ID authentication. By linking the service SAS token to a stored access policy, administrators can immediately revoke access by modifying or deleting the policy on the container. This does not require rotating the storage account keys, avoiding disruption to other applications.

Adım Adım Çözüm

1
Determine the authentication mechanism
Since the external broker cannot use Microsoft Entra ID, Entra-based authentication (RBAC and PIM) is ruled out, pointing to Shared Access Signatures (SAS).
The scenario requires that the partner does not authenticate via Microsoft Entra ID.
2
Select the appropriate SAS type and scoping
Identify that a service SAS can be scoped to a single container ('customs-docs'), unlike an account SAS.
Access must be limited strictly to the container level.
3
Determine revocation strategy
Link the service SAS to a stored access policy rather than creating an ad-hoc SAS.
Stored access policies allow immediate revocation of the SAS by deleting or modifying the policy, whereas ad-hoc SAS tokens require rotating the storage account key to revoke, affecting other services.

Anahtar Kavram

Stored Access Policies vs. Ad-hoc SAS for Container Security and Revokability
Soru 882Soru

An enterprise named Vertex Holdings has an on-premises Active Directory Domain Services (AD DS) forest with 8,500 users. You are designing a hybrid identity solution to integrate the on-premises environment with a new Microsoft Entra ID tenant.

The solution must meet the following requirements:
- Users must be able to sign in to cloud services using their on-premises credentials.
- Users must be able to sign in even if the on-premises network connection or on-premises domain controllers are temporarily unavailable.
- Users must be allowed to reset their own passwords in the cloud, and these changes must immediately synchronize back to the on-premises AD DS.
- You must minimize on-premises infrastructure requirements and administrative overhead.

Which two actions should you include in the design to meet these requirements? (Select two.)

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

Cevabı ve açıklamayı göster

Cevap: Install Microsoft Entra Connect on-premises and configure Password Hash Synchronization (PHS).; Enable Password Writeback in Microsoft Entra Connect and configure Self-Service Password Reset (SSPR) in the Microsoft Entra tenant.

Cevap

To meet the requirements, you must deploy Microsoft Entra Connect with Password Hash Synchronization (PHS) to ensure authentication during on-premises outages, and enable Password Writeback with Self-Service Password Reset (SSPR) to allow password resets to synchronize back to the on-premises Active Directory.
Implementing Password Hash Synchronization (PHS) copies password hashes to Microsoft Entra ID, allowing authentication requests to be handled entirely in the cloud, which satisfies the business continuity requirement during on-premises outages. Enabling Password Writeback in Microsoft Entra Connect coupled with Self-Service Password Reset (SSPR) allows users to reset their passwords in the cloud and writes those changes back to the on-premises Active Directory Domain Services (AD DS) immediately.

Adım Adım Çözüm

1
Evaluate hybrid identity authentication synchronization options for business continuity.
Select Password Hash Synchronization (PHS).
PHS stores password hashes in the cloud, allowing authentication to succeed even if the on-premises connection is lost, unlike Pass-through Authentication or Active Directory Federation Services.
2
Evaluate self-service password reset and synchronization requirements.
Configure SSPR in Entra ID and enable Password Writeback in Microsoft Entra Connect.
SSPR allows cloud-based password resets, and Password Writeback ensures those updates are immediately synchronized back to the on-premises Active Directory.
3
Assess operational simplicity and minimize local footprint.
Avoid deploying AD FS or on-premises federation servers.
PHS requires only the Entra Connect sync engine, minimizing infrastructure and operational overhead.

Anahtar Kavram

Selecting the optimal hybrid identity authentication method (PHS vs. PTA vs. AD FS) based on business continuity, on-premises infrastructure constraints, and self-service password writeback capabilities.
Soru 883Soru

A company needs to grant an external consultancy temporary read-only access to a specific container in an Azure Storage account. The access must be valid for 14 days, and the security team must be able to revoke this access immediately if a security anomaly is detected. Which two security controls should you recommend? (Select two.)

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

Cevabı ve açıklamayı göster

Cevap: Create a stored access policy on the blob container.; Generate a service Shared Access Signature (SAS) associated with the stored access policy.

Cevap

To support immediate revocation and temporary access, you should create a stored access policy on the container and generate a service Shared Access Signature (SAS) associated with that policy.
To satisfy the security and revocation requirements, a stored access policy should be created on the blob container, and a service SAS should be generated that references this policy. This structure allows the administrator to revoke the SAS immediately by deleting or altering the stored access policy on the server side without changing the storage account keys.

Adım Adım Çözüm

1
Define a stored access policy on the target blob container.
A policy is created containing the permissions and a 14-day validity window.
Stored access policies group SAS constraints and allow them to be altered or revoked after the SAS is issued.
2
Generate a service SAS referencing the stored access policy.
A SAS token is generated that points to the stored access policy.
This links the token lifetime and permissions to the policy, enabling immediate revocation by modifying or deleting the policy.

Anahtar Kavram

Stored Access Policies for SAS Revocation
Tahmini Süre:1m 0s
Soru 884Soru

An organization plans to migrate an on-premises line-of-business application to Azure. The application currently runs on a cluster of VMware vSphere virtual machines (VMs) and connects to a Microsoft SQL Server database cluster. The database relies on SQL Server Agent jobs and performs cross-database queries. The organization needs to discover server dependencies, analyze database compatibility with Azure SQL deployment options, and plan the migration strategy. Which two actions should you include in the migration assessment strategy? (Choose two.)

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

Cevabı ve açıklamayı göster

Cevap: Deploy the Azure Migrate appliance in the VMware environment to perform discovery and enable agentless dependency mapping.; Run the Azure Migrate database assessment to evaluate compatibility and target sizing for Azure SQL Managed Instance.

Cevap

The correct actions are deploying the Azure Migrate appliance to perform agentless dependency mapping and running the Azure Migrate database assessment to evaluate compatibility with Azure SQL Managed Instance.
Deploying the Azure Migrate appliance for agentless dependency mapping allows for the discovery and visualization of network dependencies between virtual machines, ensuring that all components of the application are migrated together. Running the database assessment specifically for Azure SQL Managed Instance evaluates compatibility and sizing for a target that supports the on-premises database's SQL Server Agent and cross-database queries.

Adım Adım Çözüm

1
Identify the migration requirements and technical constraints for the databases and applications.
The application relies on SQL Server features including SQL Server Agent and cross-database queries, which require Azure SQL Managed Instance rather than Azure SQL Database single database.
Choosing the wrong database target tier causes migration compatibility issues and application failure.
2
Select the appropriate tools to assess dependencies and database readiness.
Deploying the Azure Migrate appliance enables discovery and agentless dependency mapping. Evaluating database compatibility with Azure Migrate database assessment checks for SQL Managed Instance compatibility.
Dependency analysis ensures grouped workloads are migrated together to prevent latency, and database assessment validates feature support before migration.

Anahtar Kavram

Azure Migrate assessment strategy involves using the Azure Migrate appliance for VM discovery and dependency mapping, combined with database compatibility analysis to align database features (e.g., cross-database queries, SQL Server Agent) with the correct target tier (Azure SQL Managed Instance).
Tahmini Süre:2m 0s
Soru 885Soru

You are designing the storage infrastructure for a business-critical SQL Server database running on an Azure Virtual Machine. The database transaction logs require a dedicated disk that supports up to 5,0005,000 IOPS and sub-millisecond latency. The architecture must survive a zone failure in the primary region. Additionally, database backup exports must be securely stored in an Azure Blob Storage container and accessed by a third-party auditing application using a Shared Access Signature (SAS) token that can be revoked immediately if compromised.

Which storage configuration should you recommend?

Cevabı ve açıklamayı göster

Cevap: Configure the transaction log drive on Premium SSD managed disks using Zone-Redundant Storage (ZRS). Store the backup exports in a Blob Storage container and authorize the auditing application using a SAS token associated with a stored access policy.

Cevap

Configure the transaction log drive on Premium SSD managed disks using Zone-Redundant Storage (ZRS). Store the backup exports in a Blob Storage container and authorize the auditing application using a SAS token associated with a stored access policy.
The correct configuration uses Premium SSD to meet the IOPS and latency requirements of database transaction logs, employs Zone-Redundant Storage (ZRS) to ensure zone resiliency, and utilizes a stored access policy for the SAS token to allow immediate revocation.

Adım Adım Çözüm

1
Analyze the performance requirements for the transaction log drive.
The workload requires 5,0005,000 IOPS and sub-millisecond latency. This points to Premium SSD or Ultra Disk, eliminating Standard SSD.
Database transaction logs are write-intensive and sensitive to write latency.
2
Evaluate the resiliency requirement for the disk.
The architecture must survive a zone failure, meaning the disks must use Zone-Redundant Storage (ZRS). Locally Redundant Storage (LRS) is insufficient.
ZRS replicates data across three availability zones in the primary region.
3
Determine the secure access method for Blob Storage with instant revocation capabilities.
To revoke a SAS token immediately without regenerating the storage account keys, the SAS must be associated with a stored access policy.
An ad-hoc SAS token cannot be revoked unless the storage account keys are rotated, which breaks all other SAS tokens signed with the same key.

Anahtar Kavram

Azure managed disk performance tiers, zone redundancy, and stored access policies for secure SAS token revocation.
Tahmini Süre:1m 30s
Soru 886Soru

You are designing a globally distributed data storage solution for a delivery tracking platform. The solution has the following requirements:
- A NoSQL database must store real-time package delivery telemetry. The telemetry ingestion is write-heavy (70%70\% writes, 30%30\% reads) with an expected load of millions of updates daily.
- The telemetry database must support a 99.999%99.999\% read and write availability SLA and sub-10 ms10\text{ ms} latency.
- Delivery confirmation images must be stored in object storage. External delivery agents must be granted temporary access to upload confirmation images directly to the storage.
- The entire solution must be resilient to regional datacenter outages.

Which of the following configurations should you select to meet these requirements? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Configure Azure Cosmos DB with multi-region writes enabled across the target regions, and use OrderId as the partition key for the telemetry container.; Configure Azure Blob Storage with Geo-Zone-Redundant Storage (GZRS) and generate short-lived Shared Access Signature (SAS) tokens associated with a Stored Access Policy for image uploads.

Cevap

Configure Azure Cosmos DB with multi-region writes enabled across the target regions, and use OrderId as the partition key for the telemetry container; and configure Azure Blob Storage with Geo-Zone-Redundant Storage (GZRS) and generate short-lived Shared Access Signature (SAS) tokens associated with a Stored Access Policy for image uploads.
Enabling multi-region writes for Azure Cosmos DB is required to meet the 99.999%99.999\% write availability SLA, and using a high-cardinality partition key like OrderId prevents hot partitions under write-heavy workloads. For Blob Storage, using Geo-Zone-Redundant Storage (GZRS) ensures data is resilient against regional datacenter outages, and using short-lived SAS tokens with stored access policies aligns with security best practices.

Adım Adım Çözüm

1
Analyze Azure Cosmos DB availability and latency requirements.
To achieve a 99.999%99.999\% write availability SLA, multi-region writes (multi-master) must be enabled. Single-region writes only offer up to 99.99%99.99\% write availability.
Establishing high write availability requires active-active write regions.
2
Determine the partition key for the write-heavy Cosmos DB container.
A high-cardinality key such as OrderId must be selected. Using a low-cardinality key like StoreId or DeliveryStatus would result in uneven partition sizes and hot physical partitions.
Ensuring horizontal scalability and preventing partition throughput limits.
3
Select the redundancy tier for the delivery confirmation images in Azure Blob Storage.
Geo-Zone-Redundant Storage (GZRS) is required because it protects against regional outages by replicating data across zones in the primary region and geo-replicating it to a secondary region. Locally Redundant Storage (LRS) is vulnerable to regional outages.
Meeting the regional disaster resilience requirement.
4
Define the secure access mechanism for external agents uploading images.
Short-lived Shared Access Signature (SAS) tokens associated with a Stored Access Policy should be used. Long-lived SAS tokens defined directly in the URI are insecure and difficult to revoke.
Ensuring secure, delegable access that adheres to the principle of least privilege.

Anahtar Kavram

Azure Cosmos DB partition key selection, multi-region write scalability, and Azure Blob Storage disaster resilience and security.
Soru 887Soru

A global healthcare research institution plans to store clinical trial genomic datasets in an Azure Blob Storage account named genomedata. You are designing a security and access control strategy to meet the following requirements:
1. External pharmaceutical research partners must be granted temporary, read-only access to specific blobs in a container named trial-results.
2. Access for partners must be restricted to a specific IP address range and must support immediate revocation before the planned 7-day expiration period.
3. Storage administrators must manage these access policies following the principle of least privilege, ensuring that administrator roles can only be activated for a maximum of 4 hours at a time and require manager approval.
4. Access permissions must not be assigned directly to individual admin accounts to ensure scalable governance.

Which three actions should you include in the storage security design? (Select THREE.)

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

Cevabı ve açıklamayı göster

Cevap: Create a Stored Access Policy on the trial-results container, and generate a Service Shared Access Signature (SAS) that references this policy and specifies the allowed IP address range.; Create a Microsoft Entra ID security group for administrators, and configure a Privileged Identity Management (PIM) eligible role assignment for this group to the Storage Account Contributor role.; Configure the Privileged Identity Management (PIM) role settings for the Storage Account Contributor role to require manager approval and enforce a maximum activation duration of 4 hours.

Cevap

To meet the security objectives, you must create a Stored Access Policy on the trial-results container to generate a Service SAS with IP restrictions, create a Microsoft Entra ID security group for administrators with an eligible PIM role assignment, and configure PIM activation settings to require approval and limit duration to 4 hours.
To secure external partner access with immediate revocation capability, you must generate a Service SAS associated with a Stored Access Policy. This allows you to invalidate the SAS instantly by deleting or modifying the policy. For administrative access, following the principle of least privilege requires combining Microsoft Entra ID security groups (avoiding direct RBAC assignments) with Privileged Identity Management (PIM) eligible assignments. Setting the PIM role settings to require approval and limiting the activation window to 4 hours satisfies the operational control requirements.

Adım Adım Çözüm

1
Address partner access and revocation requirements.
Create a Stored Access Policy on the trial-results container and generate a Service SAS that references this policy and includes the allowed IP range.
Stored Access Policies allow you to change the expiration time or delete the policy to instantly invalidate any associated SAS tokens. Ad-hoc SAS tokens cannot be revoked individually without rotating the storage keys.
2
Design group-based access control for administrative tasks.
Create a Microsoft Entra ID security group for administrators and configure eligibility in Privileged Identity Management (PIM) to the Storage Account Contributor role.
Assigning RBAC roles to security groups rather than individual users ensures scalable governance, while PIM eligibility enables just-in-time access elevation.
3
Enforce limits on administrative access duration and authorization.
Configure PIM role settings to require manager approval and restrict the maximum activation duration to 4 hours.
This satisfies the policy of least privilege and prevents administrators from possessing standing, high-privilege access.

Anahtar Kavram

Securing storage account access using Stored Access Policies combined with Microsoft Entra ID security groups and Privileged Identity Management (PIM) for administrative access control.
Soru 888Soru

An enterprise database hosting platform is migrating its critical transactional database to Azure Virtual Machines. The virtual machines are deployed in a high-availability configuration across multiple Availability Zones in a single Azure region.

The database transaction log drive requires a storage solution that meets the following requirements:
- Must sustain at least 12,00012,000 IOPS.
- Must provide consistent low latency.
- Must remain online and accessible to virtual machines in another availability zone if the primary availability zone suffers a complete power outage.

Which storage configuration should you recommend?

Cevabı ve açıklamayı göster

Cevap: Premium SSD managed disks configured with Zone-Redundant Storage (ZRS)

Cevap

Premium SSD managed disks configured with Zone-Redundant Storage (ZRS)
The correct option is the one specifying Premium SSD managed disks with Zone-Redundant Storage (ZRS). Premium SSDs can meet the 12,00012,000 IOPS requirement with consistent low latency, and ZRS replicates the data across three availability zones in the region, ensuring access is maintained if the primary zone fails.

Adım Adım Çözüm

1
Analyze the availability requirements.
The storage must survive a complete zone outage and be accessible in another zone.
This eliminates any disk options that only support Locally Redundant Storage (LRS).
2
Evaluate the redundancy capabilities of Azure disk types.
Ultra Disk and Premium SSD v2 only support LRS, whereas Premium SSD and Standard SSD support Zone-Redundant Storage (ZRS).
Knowing which disk types support ZRS narrows down the candidate disks to Premium SSD and Standard SSD.
3
Evaluate the performance requirements of the database transaction log.
The log requires at least 12,00012,000 IOPS and consistent low latency. Standard SSD supports a maximum of 6,0006,000 IOPS and lacks low-latency guarantees, while Premium SSD can provision up to 20,00020,000 IOPS (depending on disk size) with single-digit millisecond latency.
Premium SSD with ZRS is the only option that satisfies both the 12,00012,000 IOPS performance threshold and the zone-redundancy availability requirement.

Anahtar Kavram

Selecting Azure managed disk types and redundancy configurations based on performance and zonal availability requirements.
Tahmini Süre:2m 0s
Soru 889Soru

You are designing a backup solution for critical Azure Virtual Machines. The solution must meet the following requirements:
1. Backups must be protected against a regional outage of the primary Azure region.
2. You must be able to perform instant restores of the virtual machines from local snapshots for the last 2 days.
3. You must retain the backup data in the vault for a total of 30 days.

Which configuration should you recommend?

Cevabı ve açıklamayı göster

Cevap: A Recovery Services vault configured with Geo-redundant storage (GRS), with the backup policy set to 2 days of instant restore retention and 30 days of vault retention.

Cevap

A Recovery Services vault configured with Geo-redundant storage (GRS), with the backup policy set to 2 days of instant restore retention and 30 days of vault retention.
The correct configuration uses a Recovery Services vault with Geo-redundant storage (GRS) to provide regional resilience, combined with a backup policy that keeps local instant restore snapshots for 2 days and retains vault recovery points for 30 days.

Adım Adım Çözüm

1
Determine the required vault redundancy to protect against a regional outage.
Identify that Geo-redundant storage (GRS) is required, which replicates data to a secondary region, whereas Locally-redundant storage (LRS) is insufficient.
GRS ensures high availability and disaster recovery across regions, meeting the first requirement.
2
Determine the instant restore retention configuration.
Set the instant restore snapshot retention to 2 days.
This satisfies the requirement to perform instant restores from local snapshots for the last 2 days, and conforms to the Azure VM backup policy limit where instant restore retention is capped between 1 and 5 days.
3
Determine the long-term vault retention configuration.
Set the vault retention to 30 days.
This ensures recovery points are kept in the vault for the full 30-day period as required.

Anahtar Kavram

Azure VM Backup policy configuration and vault storage redundancy design.
Soru 890Soru

You are designing the security and access control architecture for an Azure Storage account named mfgtelemetry. The storage account contains two blob containers: firmware-updates and telemetry-logs.

You need to recommend a solution that meets the following security requirements:
- Internal operational administrators must have temporary, request-based read and write access to firmware-updates. Access must require approval, expire automatically, and be fully audited.
- An external partner must be granted read-only access to telemetry-logs. This access must be restricted to the partner's public IP range, must expire within 24 hours, and must support immediate revocation without rotating the storage account access keys or impacting other active access tokens.
- Administrative overhead must be minimized.

Which solution should you recommend?

Cevabı ve açıklamayı göster

Cevap: Configure Microsoft Entra Privileged Identity Management (PIM) to assign a security group containing the administrators as eligible for the Storage Blob Data Contributor role on the firmware-updates container. Create a stored access policy on the telemetry-logs container, and generate a service Shared Access Signature (SAS) linked to this policy with IP restrictions and a 24-hour expiration.

Cevap

Configure Microsoft Entra Privileged Identity Management (PIM) to assign a security group containing the administrators as eligible for the Storage Blob Data Contributor role on the firmware-updates container, and use a service SAS associated with a Stored Access Policy for the external partner.
To satisfy the requirements for the administrators, using Microsoft Entra Privileged Identity Management (PIM) with an eligible assignment for a security group is the best practice. This enables just-in-time (JIT) access that requires approval, has a limited duration, and logs all activations for auditing. To satisfy the requirements for the external partner, generating a service Shared Access Signature (SAS) associated with a Stored Access Policy (SAP) allows you to specify permissions, IP limits, and expiration. If the token is compromised, you can delete or modify the Stored Access Policy to instantly revoke access without rotating the primary/secondary keys of the storage account, which would disrupt other integrations.

Adım Adım Çözüm

1
Analyze the access control requirements for the internal operational administrators.
Identified that they require temporary, request-based, approved, and audited read-write access.
This matches Microsoft Entra Privileged Identity Management (PIM) with eligible role assignments using security groups for scalable governance.
2
Analyze the access requirements for the external partner.
Identified that they need read-only access restricted by IP, expiring in 24 hours, and requiring immediate individual revocation support without key rotation.
A Service SAS linked to a Stored Access Policy (SAP) is required because changing or deleting the SAP immediately revokes the SAS without affecting other keys or tokens.
3
Synthesize the two requirements to select the correct architectural combination.
The correct solution must use PIM group-based eligible assignment for administrators and a Stored Access Policy-backed Service SAS for the partner.
Other options use active PIM assignments (violating JIT approval), direct RBAC assignments (violating group governance), or ad-hoc SAS (violating keyless revocation).

Anahtar Kavram

Designing secure access control using Azure RBAC, PIM, and Stored Access Policies
Soru 891Soru

An organization stores 25 GB25\text{ GB} of sales log files in CSV format within an Azure Data Lake Storage Gen2 account. Data analysts need to run occasional, ad-hoc SQL queries against these files to inspect anomalies. You need to recommend an Azure Synapse Analytics query solution that minimizes costs by ensuring there are no ongoing compute charges when queries are not executing. Which resource type should you recommend?

Cevabı ve açıklamayı göster

Cevap: Serverless SQL pools

Cevap

Serverless SQL pools
The correct option is Serverless SQL pools. They are specifically designed for ad-hoc, exploratory queries on files stored in Azure Storage. Since there are no provisioned resources, charges are based strictly on the volume of data processed by each query, resulting in zero costs during idle periods.

Adım Adım Çözüm

1
Analyze the requirements for data querying and cost optimization.
The scenario requires querying CSV data in Azure Data Lake Storage Gen2 without paying for idle compute time.
This establishes the need for an on-demand, serverless query model instead of a provisioned database cluster.
2
Compare the cost models of the query options.
Serverless SQL pools charge only per TB of data processed, whereas dedicated SQL pools charge per hour of provisioned resources.
Choosing the serverless model ensures no ongoing costs are incurred when analysts are not running queries.

Anahtar Kavram

Selecting serverless vs dedicated analytics compute models in Azure Synapse
Soru 892Soru

An organization deploys a critical application that uses a single database on Azure SQL Database. The disaster recovery requirements specify that:

- In the event of a regional outage, the database must fail over to a secondary Azure region automatically.
- The application must reconnect automatically without needing any modifications to its connection strings.

Which Azure SQL Database feature should you recommend to meet these requirements?

Cevabı ve açıklamayı göster

Cevap: Auto-failover groups

Cevap

Auto-failover groups
The correct answer is Auto-failover groups because they support automatic failover policies for groups of databases to a secondary region and expose a single read-write listener endpoint. This listener automatically routes application traffic to the active primary database, avoiding the need to change connection strings during a failover.

Adım Adım Çözüm

1
Analyze the disaster recovery requirements for the Azure SQL Database.
Identify that both cross-region automatic failover and seamless connection redirection are required.
This determines which database high availability and disaster recovery feature is necessary.
2
Evaluate the database features against the connection string requirement.
Auto-failover groups provide a read-write listener endpoint that redirects connections automatically, whereas Active geo-replication requires manual updates to connection strings.
This distinguishes between the two primary cross-region database replication features.
3
Evaluate the database features against the automatic failover requirement.
Auto-failover groups support automatic failover policies managed by Azure, whereas Active geo-replication only supports manual failover.
This confirms that Auto-failover groups meet all constraints.

Anahtar Kavram

Azure SQL Database Auto-Failover Groups provide automatic cross-region failover and read-write listeners that prevent the need to update application connection strings during a failover.
Soru 893Soru

You are designing an Azure Backup solution for a critical application hosted on Azure Virtual Machines. The solution must satisfy the following requirements:

* For any data loss events occurring within the last 77 days, virtual machine restoration must be performed with the absolute minimum recovery time objective (RTO).
* Backups must be resilient to regional disasters, with the capability to initiate restores in the secondary paired region at any time, regardless of the primary region's status.
* Monthly backups must be kept for 33 years at the lowest possible storage cost.

Which two configuration options should you include in the backup design? (Select TWO)

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

Cevabı ve açıklamayı göster

Cevap: Configure the backup policy with an instant restore snapshot retention of 77 days.; Enable Cross-Region Restore (CRR) on a Recovery Services vault configured with Geo-Redundant Storage (GRS).

Cevap

Configure the backup policy with an instant restore snapshot retention of 77 days, and enable Cross-Region Restore (CRR) on a Recovery Services vault configured with Geo-Redundant Storage (GRS).
To achieve the lowest possible RTO for the last 77 days, the backup policy must keep the snapshots locally in the source resource group by extending the instant restore snapshot retention to 77 days. To allow restoration in the secondary region at any time regardless of the primary region's status, Cross-Region Restore (CRR) must be enabled on a Geo-Redundant Storage (GRS) vault.

Adım Adım Çözüm

1
Analyze the recovery time objective (RTO) requirement for the 77-day window.
Identify that local snapshots (Instant Restore) must be retained for 77 days to bypass vault rehydration/transfer latency.
By default, instant restore snapshots are kept for 22 days. Extending this to 77 days ensures that restores within this period do not pull data from the vault, minimizing recovery time.
2
Analyze the regional disaster recovery and replication requirements.
Determine that the vault needs Geo-Redundant Storage (GRS) with Cross-Region Restore (CRR) enabled.
Standard GRS only allows restores in the secondary region after Microsoft declares a disaster. CRR allows the customer to perform restores in the secondary region at any time.
3
Analyze the cost optimization requirement for long-term monthly backups.
Identify that monthly backups can be moved to the Vault-archive tier.
The Vault-archive tier is ideal for long-term retention of monthly and yearly backups, where recovery time is less critical and data must be kept for at least 180180 days.

Anahtar Kavram

Designing Azure Backup policies for low RTO (using extended Instant Restore snapshot retention) and configuring vaults for cross-region recoverability (using GRS with Cross-Region Restore).
Soru 894Soru

An organization is designing a high availability and disaster recovery solution for a web application that uses Azure SQL Database. The solution must support automatic failover to a secondary Azure region, provide a single connection endpoint for the application, and allow read-scale operations in the secondary region. Which two features or capabilities should you recommend to meet these requirements? (Select two.)

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

Cevabı ve açıklamayı göster

Cevap: Auto-failover groups; The read-only listener endpoint of the auto-failover group

Cevap

To meet the requirements, you should recommend using auto-failover groups and the read-only listener endpoint of the auto-failover group.
Auto-failover groups allow you to manage the replication and failover of a group of databases on a logical server to another Azure region. They provide automatic failover capabilities and include a single read-write listener endpoint as well as a read-only listener endpoint. Using the read-only listener endpoint allows the application to route read-only workloads to the secondary database without changing connection strings during a failover.

Adım Adım Çözüm

1
Analyze the high availability and disaster recovery requirements of the application.
The requirements specify automatic failover to a secondary region, a single connection endpoint, and read-scale operations.
Understanding the requirements helps filter out options that do not support automatic failover or listener endpoints.
2
Evaluate Azure SQL Database features that support multi-region disaster recovery and automatic failover.
Auto-failover groups support automatic failover and provide write and read-only listener endpoints. Active geo-replication only supports manual failover and does not provide listener endpoints.
This distinguishes between the capabilities of auto-failover groups and active geo-replication to satisfy the single endpoint and automatic failover requirements.
3
Identify the specific features needed to connect the application and leverage the secondary database for read-only workloads.
Use the read-only listener endpoint of the auto-failover group to route read-only traffic to the secondary region.
The read-only listener endpoint satisfies the read-scale requirement while maintaining a single endpoint.

Anahtar Kavram

Designing relational database high availability and disaster recovery in Azure SQL Database using auto-failover groups.
Soru 895Soru

A healthcare organization is onboarding a team of four external security audit consultants to perform a two-week assessment of critical Azure subscription resources. The consultants require temporary, time-bound administrative access to the resources. To comply with security policies, the consultants must only have access when actively performing audit tasks, all role elevations must require multi-factor authentication (MFA), and administrative overhead must be minimized. The organization also needs to ensure that emergency access break-glass accounts are never locked out of the tenant by any Conditional Access policies enforced during role activation. Which of the following designs should you recommend to meet these requirements?

Cevabı ve açıklamayı göster

Cevap: Create a Microsoft Entra security group for the consultants. In Microsoft Entra Privileged Identity Management (PIM) for Azure resources, assign the security group as eligible for the required RBAC roles. Configure the PIM role settings to require MFA upon activation, and exclude emergency access accounts from any Conditional Access policies requiring MFA.

Cevap

Create a Microsoft Entra security group for the consultants, assign the group as eligible for the RBAC roles in PIM, configure PIM to require MFA upon activation, and exclude emergency access accounts from Conditional Access MFA policies.
The correct option correctly applies governance best practices by utilizing a security group to manage the external consultants, assigning the group as eligible in Privileged Identity Management (PIM) for just-in-time access, enforcing MFA at activation, and protecting tenant access by excluding emergency accounts from MFA policies.

Adım Adım Çözüm

1
Determine the optimal identity delegation structure to minimize management overhead.
Identify that assigning roles to a Microsoft Entra security group is more scalable and manageable than assigning roles to four individual accounts.
Grouping users allows for centralized administration of access membership without modifying Azure RBAC role assignments.
2
Select the appropriate assignment type in Privileged Identity Management (PIM) to meet the JIT and auditing requirements.
Configure the group with eligible assignments in PIM rather than active or permanent assignments.
Eligible assignments require users to explicitly activate the role when needed, supporting just-in-time (JIT) access and logging elevation events.
3
Establish MFA enforcement while maintaining tenant availability safeguards.
Enable MFA in the PIM role activation settings and ensure emergency access break-glass accounts are excluded from Conditional Access policies.
Excluding emergency accounts prevents tenant lockout in case of MFA outages or misconfigurations.

Anahtar Kavram

Privileged Identity Management (PIM) allows just-in-time role activation for groups, enhancing security posture while avoiding direct user assignments and mitigating lockout risks.
Tahmini Süre:1m 30s
Soru 896Soru

An educational institution is restructuring its Azure administration model. The institution needs to delegate temporary access to a team of eight junior DevOps engineers who require the Subscription Contributor role to perform deployment tasks. The design must satisfy the following security and governance requirements:

- The junior DevOps engineers must only have administrative permissions when actively working on scheduled deployments.
- Administrative access must be managed using a group-based model to minimize administrative overhead.
- Multi-Factor Authentication (MFA) must be enforced for all administrative tasks.
- Two dedicated emergency-access (break-glass) accounts must be exempt from tenant lockout risks and maintain access if MFA services are unavailable.

Which two actions should you include in the identity and governance design? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Assign the Subscription Contributor role to a Microsoft Entra ID group containing the DevOps engineers as an eligible assignment in Privileged Identity Management (PIM) for Azure resources.; Exclude the two emergency access accounts from the Conditional Access policy that enforces Multi-Factor Authentication (MFA) for administrative roles.

Cevap

Assign the Subscription Contributor role to a Microsoft Entra ID group as eligible in Privileged Identity Management (PIM) and exclude emergency access accounts from the Multi-Factor Authentication (MFA) Conditional Access policy.
The correct design utilizes group-based role assignments in Privileged Identity Management (PIM) to minimize administrative overhead while requiring just-in-time activation to align with the principle of least privilege. Additionally, the emergency access (break-glass) accounts must be excluded from Conditional Access policies enforcing Multi-Factor Authentication (MFA) to prevent tenant lockout during an MFA service outage.

Adım Adım Çözüm

1
Group the junior DevOps engineers into a Microsoft Entra ID security group.
Provides a single administrative boundary for role management, avoiding direct user assignments.
Simplifies management and adheres to administrative scaling best practices.
2
Configure the security group with an eligible role assignment for the Subscription Contributor role in Privileged Identity Management (PIM) for Azure resources.
Enables just-in-time (JIT) role activation, ensuring permissions are only active during scheduled deployments.
Meets the requirement for temporary access and least privilege.
3
Exclude the two dedicated emergency-access accounts from the Conditional Access policy that enforces MFA for administrative access.
Guarantees access to the Azure tenant even if MFA services are completely unavailable.
Protects against tenant lockout, satisfying the break-glass configuration best practices.

Anahtar Kavram

Privileged Identity Management (PIM) and emergency access governance
Soru 897Soru

You are designing a backup solution for an Azure virtual machine. The solution must meet the following requirements:
- Backups must be available in a secondary region to protect against a primary region outage.
- You must be able to perform instant recovery from snapshots for up to 14 days.

Which two configurations should you choose? (Choose two.)

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

Cevabı ve açıklamayı göster

Cevap: A Recovery Services vault configured with Geo-Redundant Storage (GRS) and Cross-Region Restore (CRR) enabled; An Enhanced backup policy with the instant restore retention set to 14 days

Cevap

A Recovery Services vault configured with Geo-Redundant Storage (GRS) and Cross-Region Restore (CRR) enabled, and an Enhanced backup policy with the instant restore retention set to 14 days
To satisfy the requirements, you must use a Recovery Services vault configured with Geo-Redundant Storage (GRS) and Cross-Region Restore (CRR) enabled to ensure availability in the secondary region. Additionally, because the Standard backup policy subtype only supports up to 5 days of instant restore retention, you must use the Enhanced backup policy subtype to set the instant restore snapshot retention to 14 days.

Adım Adım Çözüm

1
Determine the vault type and redundancy configuration required for regional resilience.
Identify that a Recovery Services vault with Geo-Redundant Storage (GRS) and Cross-Region Restore (CRR) enabled is required to access backups in the secondary region during a primary region outage.
Locally Redundant Storage (LRS) does not replicate outside the primary region.
2
Determine the policy subtype needed to support the instant recovery snapshot duration.
Identify that the Enhanced backup policy subtype is required because the Standard policy limits instant recovery snapshot retention to 5 days, whereas the requirements call for 14 days.
The Standard policy subtype has a hard limit of 5 days for instant restore snapshot retention.

Anahtar Kavram

Selecting appropriate Azure Backup vault redundancy and policy subtypes (Standard vs. Enhanced) to satisfy regional disaster recovery and long-term instant restore requirements.
Soru 898Soru

An energy utility company is designing an identity governance and privileged access strategy for its production Azure subscription. The subscription contains critical infrastructure resources. The design must meet the following requirements:
- Provide just-in-time (JIT) administrative access for the network operations team.
- Require multi-factor authentication (MFA) and manager approval for JIT role activation.
- Ensure that administrative permissions are governed at a group level rather than assigned to individual accounts.
- Maintain a recovery path using emergency access (break-glass) accounts that can bypass MFA in case of a tenant-wide identity outage.

Which design strategy should you recommend to meet these requirements?

Cevabı ve açıklamayı göster

Cevap: Create a Microsoft Entra ID security group for the operations team, assign this group as eligible for the required Azure RBAC roles in Privileged Identity Management (PIM) with MFA and approval required for activation, and exclude the emergency access accounts from the Conditional Access MFA policies.

Cevap

Create a Microsoft Entra ID security group for the operations team, assign this group as eligible for the required Azure RBAC roles in Privileged Identity Management (PIM) with MFA and approval required for activation, and exclude the emergency access accounts from the Conditional Access MFA policies.
The correct strategy leverages group-based assignments for scalable security, uses Privileged Identity Management (PIM) to ensure role assignments are eligible rather than permanently active, and properly excludes emergency accounts from MFA requirements to secure a recovery route during tenant-wide MFA outages.

Adım Adım Çözüm

1
Select the correct identity governance container to minimize management overhead.
Create a Microsoft Entra ID security group rather than assigning permissions to individual users.
Assigning permissions to individual users does not scale and violates administrative governance best practices.
2
Determine the assignment type in Microsoft Entra Privileged Identity Management (PIM).
Configure the group role assignment as 'eligible' instead of 'active'.
Eligible assignments allow the operations team to activate the role only when needed, enforcing the principle of least privilege.
3
Define the requirements for activating the eligible role assignment in PIM.
Require multi-factor authentication (MFA), justification, and manager approval for activation.
This guarantees that administrative activities are audited, justified, and approved prior to access elevation.
4
Configure the Conditional Access policy for emergency scenarios.
Exclude the emergency access (break-glass) accounts from MFA-enforcing Conditional Access policies.
Excluding emergency accounts prevents a lockout scenario if there is a regional or tenant-wide MFA provider outage.

Anahtar Kavram

Combining group-based RBAC assignment, Privileged Identity Management (PIM) eligibility settings, and Conditional Access exclusions for emergency accounts.
Soru 899Soru

A company is planning to migrate an on-premises enterprise resource planning (ERP) application to Azure. The application's database layer has the following requirements:
- Must support SQL Server Agent jobs and cross-database queries.
- Must achieve a Recovery Point Objective (RPO) of less than 5 seconds and a Recovery Time Objective (RTO) of less than 30 seconds.
- In the event of a regional disaster, database failover to the secondary region must happen automatically.
- Reporting workloads in the secondary region must run on a read-only replica and must automatically route to the active replica's secondary endpoint without application connection string modifications during failover.
- All network traffic between the database replicas must remain isolated from the public internet.

Which database configuration should you recommend?

Cevabı ve açıklamayı göster

Cevap: Deploy two Azure SQL Managed Instances in different regions, establish virtual network peering between their virtual networks, and configure a failover group. Route database traffic using the failover group's read-write and read-only listener endpoints.

Cevap

Deploy two Azure SQL Managed Instances in different regions, establish virtual network peering between their virtual networks, and configure a failover group. Route database traffic using the failover group's read-write and read-only listener endpoints.
The correct option satisfies all constraints by using Azure SQL Managed Instance, which supports instance-level features such as SQL Server Agent and cross-database queries. By utilizing virtual network peering, the replication traffic remains isolated from the public internet. Failover groups support automatic failover to meet the low RTO and RPO, and they provide read-write and read-only listener endpoints, eliminating the need to update application connection strings during a failover event.

Adım Adım Çözüm

1
Determine database engine compatibility requirements.
The application requires SQL Server Agent and cross-database queries. This rules out Azure SQL Database (Single Database and Elastic Pools) and points to Azure SQL Managed Instance or SQL Server on Azure VMs.
Choosing the correct deployment model is critical to support legacy on-premises SQL Server features.
2
Evaluate high availability and disaster recovery mechanisms.
To meet an RPO of < 5 seconds and an RTO of < 30 seconds with automatic failover and read-only routing that does not require connection string updates, Azure SQL Managed Instance failover groups are the ideal solution. Active geo-replication requires manual failover, which violates the automatic failover constraint.
Failover groups provide read-write and read-only listener endpoints that point dynamically to the current primary and secondary regions.
3
Select the networking topology for data replication.
Configure virtual network (VNet) peering between the VNets of the primary and secondary Azure SQL Managed Instances.
This guarantees that the replication traffic traverses the Microsoft backbone network privately and remains completely isolated from the public internet.

Anahtar Kavram

Relational Database High Availability and Disaster Recovery using Azure SQL Managed Instance Failover Groups
Soru 900Soru

An enterprise is designing a telemetry analytics platform on Azure to ingest and store clickstream logs from regional applications. The platform must meet the following requirements:

* Storage and Volume: Ingest and store 15 TB15\text{ TB} of historical logs in CSV format within a hierarchical namespace storage account, with a nightly batch pipeline appending 200 GB200\text{ GB} of new data at a rate of 10 MB/s10\text{ MB/s}.
* Exploratory Queries: Enable data analysts to run ad-hoc, exploratory SQL queries on the raw files with a target query latency of under 15 seconds15\text{ seconds}. Compute cost must only be incurred during query execution.
* Resilience: The underlying storage must remain available for read access during a primary Azure region outage.
* Security: Grant third-party partners read-only access to a specific directory in the data lake, with the ability to instantly revoke access if credentials are compromised.

Which storage configuration, analytics service, and authorization mechanism should you recommend to meet these requirements?

Cevabı ve açıklamayı göster

Cevap: Configure the storage account to use Read-Access Geo-Redundant Storage (RA-GRS). Deploy Azure Synapse Analytics serverless SQL pools to query the CSV files. Generate Shared Access Signatures (SAS) linked to a Stored Access Policy for external partners.

Cevap

Configure the storage account to use Read-Access Geo-Redundant Storage (RA-GRS). Deploy Azure Synapse Analytics serverless SQL pools to query the CSV files. Generate Shared Access Signatures (SAS) linked to a Stored Access Policy for external partners.
The correct answer combines Read-Access Geo-Redundant Storage (RA-GRS) to ensure regional read-resilience, Azure Synapse Analytics serverless SQL pools to support cost-effective ad-hoc SQL queries on raw CSV files in Azure Data Lake Storage Gen2, and Shared Access Signatures (SAS) linked to a Stored Access Policy to enable immediate revocation of third-party access.

Adım Adım Çözüm

1
Identify the storage configuration that meets the resilience requirements.
Read-Access Geo-Redundant Storage (RA-GRS) is selected.
RA-GRS replicates data to a secondary region and allows read access to the secondary endpoint during a primary region outage, satisfying the resilience SLA, whereas Locally Redundant Storage (LRS) is vulnerable to regional outages.
2
Determine the correct analytics service that satisfies the cost and query requirements.
Azure Synapse Analytics serverless SQL pool is selected.
Serverless SQL pools allow running ad-hoc T-SQL queries directly against CSV files in the data lake, and costs are calculated based on the data processed rather than active server time, eliminating idle compute costs.
3
Select the secure authorization mechanism for external partners.
Shared Access Signatures (SAS) linked to a Stored Access Policy are selected.
Linking the SAS to a Stored Access Policy allows administrators to revoke access immediately by deleting or modifying the policy, whereas standard SAS tokens with the expiry embedded in the URI cannot be revoked without rotating the storage account keys.

Anahtar Kavram

Designing resilient, cost-effective, and secure analytical storage solutions in Azure.
Tahmini Süre:2m 0s
ÖncekiSayfa 45 / 60Sonraki
Tüm alıştırma soruları — Microsoft Azure Solutions Architect (AZ-305) | Examkin