Tüm alıştırma soruları

1198 soru

Soru 141Soru

An organization is planning the migration of an on-premises database to Azure. The database currently supports a critical business application and has the following requirements:
- It must support SQL Server Agent for scheduled T-SQL maintenance jobs.
- It must allow cross-database queries using three-part names across multiple databases.
- The deployment must reside within a delegated subnet of an Azure Virtual Network for secure private connectivity.
- The administrative overhead of managing the host operating system, patching, and backups must be minimized.
- The backup strategy must guarantee that data remains recoverable even in the event of a complete primary Azure datacenter outage.

Which database solution should you recommend?

Cevabı ve açıklamayı göster

Cevap: Azure SQL Managed Instance with geo-redundant backup storage

Cevap

Azure SQL Managed Instance with geo-redundant backup storage
The correct answer is Azure SQL Managed Instance with geo-redundant backup storage. This solution satisfies all criteria: it is a fully managed database service (PaaS) that minimizes administrative overhead, supports SQL Server Agent and cross-database queries natively, supports virtual network integration via a delegated subnet, and replicates backups to a paired region using geo-redundant storage (GRS) to survive a primary datacenter outage.

Adım Adım Çözüm

1
Identify feature compatibility requirements
The application requires SQL Server Agent and cross-database queries, which narrows the choices to Azure SQL Managed Instance and SQL Server on Azure VMs.
Azure SQL Database single database does not support these native SQL Server features.
2
Evaluate administrative overhead constraints
Azure SQL Managed Instance is selected over SQL Server on Azure VMs.
The requirement states that the administrative overhead of managing host operating systems, patching, and backups must be minimized.
3
Determine the backup redundancy level
Configure the managed instance with geo-redundant backup storage (GRS).
The database backups must survive a primary Azure datacenter outage, which rules out locally redundant storage (LRS).

Anahtar Kavram

Selecting Azure SQL relational database tiers and backup options based on feature requirements and operational overhead
Soru 142Soru

You are designing the storage configuration for a high-performance transactional database hosted on Azure Virtual Machines. The database has the following requirements:

- The transaction log volume must support up to 8,000 IOPS8,000\text{ IOPS} and 200 MB/s200\text{ MB/s} throughput with consistent sub-millisecond latency.
- You must be able to scale the log volume's IOPS and throughput dynamically during peak processing windows without restarting the virtual machine or detaching the disk.
- Database backups must survive a localized datacenter outage within the primary region without incurring the high latency or costs of cross-region replication during recovery operations.

Which storage configuration should you recommend to meet these requirements?

Cevabı ve açıklamayı göster

Cevap: Premium SSD v2 for the transaction log volume, and Zone-Redundant Storage (ZRS) for the backups

Cevap

Premium SSD v2 for the transaction log volume, and Zone-Redundant Storage (ZRS) for the backups
The combination of Premium SSD v2 and Zone-Redundant Storage (ZRS) meets all constraints. Premium SSD v2 is designed for sub-millisecond disk latency and supports independent, online adjustments to capacity, IOPS, and throughput without VM downtime. Zone-Redundant Storage replicates backup data synchronously across three availability zones in the primary region, ensuring survival of a localized datacenter outage while avoiding the high latency of restoring from a secondary region.

Adım Adım Çözüm

1
Analyze the performance, latency, and scaling requirements for the transaction log volume.
The workload demands sub-millisecond latency and the ability to scale up to 8,000 IOPS8,000\text{ IOPS} and 200 MB/s200\text{ MB/s} throughput online without virtual machine downtime.
This rules out Standard SSD due to performance constraints, and Premium SSD (v1) because it requires offline operations (disk detachment or VM deallocation) to change provisioned IOPS or throughput.
2
Evaluate the backup storage options based on regional availability and recovery latency requirements.
The backups must survive a localized datacenter (availability zone) outage while keeping recovery latency minimal by avoiding cross-region data transfer.
This eliminates Locally Redundant Storage (LRS), which is vulnerable to datacenter failures, and Geo-Redundant Storage (GRS), which replicates across regions and introduces significant cross-region recovery latency.
3
Select the optimal combination of storage services that satisfies both conditions at the lowest complexity and cost.
Premium SSD v2 satisfies the transactional logging needs (supporting sub-millisecond latency and online performance scaling), while Zone-Redundant Storage (ZRS) provides zone-level resilience for backups within the same region.
Premium SSD v2 offers the exact performance profile needed at a lower price point than Ultra Disk, and ZRS keeps recovery traffic local to the primary region.

Anahtar Kavram

Selecting Azure disk tiers for sub-millisecond latency and dynamic performance scaling, combined with regional replication levels (ZRS) for zone-resilience without cross-region overhead.
Tahmini Süre:2m 0s
Soru 143Soru

You are designing an identity governance and privileged access solution for a large Azure enterprise environment. The environment has the following requirements:

* A team of tier-2 cloud engineers must be able to manage role assignments on a critical subscription, but only when actively performing scheduled maintenance.
* To maintain a clear audit trail and ease of administration, individual user accounts must not be assigned roles directly.
* All administrative activations must require multi-factor authentication (MFA) and administrative approval.
* The organization's emergency access (glass-breaker) account must be protected from accidental lockout during a Microsoft Entra ID authentication outage.

Which design recommendation should you include in the identity governance strategy to meet these requirements?

Cevabı ve açıklamayı göster

Cevap: Configure a Microsoft Entra ID security group, make the cloud engineers eligible members of the group using Privileged Identity Management (PIM) for Groups, and assign the group the User Access Administrator role on the subscription. Exclude the emergency access account from the Conditional Access policy that enforces MFA for administrative roles.

Cevap

Configure a Microsoft Entra ID security group, make the cloud engineers eligible members of the group using Privileged Identity Management (PIM) for Groups, and assign the group the User Access Administrator role on the subscription. Exclude the emergency access account from the Conditional Access policy that enforces MFA for administrative roles.
The correct recommendation implements group-based access control using PIM for Groups to make engineers eligible, ensuring that they must activate their membership using MFA and approval only when needed. It also ensures the emergency access account is excluded from CA MFA policies to mitigate lockout risks during an identity provider outage.

Adım Adım Çözüm

1
Select the target identity container for the engineering team.
A Microsoft Entra ID security group is chosen instead of individual assignments.
This satisfies the requirement that individual user accounts must not be assigned roles directly, aligning with enterprise governance best practices.
2
Configure the privileged access method for the security group.
Use Privileged Identity Management (PIM) for Groups to make the engineers eligible members.
Eligible membership allows engineers to request elevation dynamically, supporting MFA and manager approval workflows prior to activation.
3
Define the emergency access policy exemptions.
Exclude the emergency access (glass-breaker) account from the Conditional Access MFA policy.
This protects the organization from administrative lockout if the Entra ID authentication or MFA services experience an outage.

Anahtar Kavram

Designing secure administrative access using Privileged Identity Management (PIM) for Groups alongside appropriate Conditional Access exclusions for emergency accounts.
Tahmini Süre:2m 0s
Soru 144Soru

An enterprise is migrating an on-premises transactional database to an Azure Virtual Machine. You are designing the storage architecture to meet the following requirements:

- Transaction Logs: The drive hosting the database transaction logs must support at least 25,00025,000 IOPS and deliver sub-millisecond write latency.
- Database Backups: Backups must be stored in Azure Blob Storage and remain available even in the event of a complete regional outage of the primary Azure region.
- Auditor Access: An external auditing firm requires access to download specific backup files for a period of 1414 days. You must be able to immediately revoke this access at any point during the 1414 days without affecting other clients or rotating the storage account access keys.

Which storage design should you recommend?

Cevabı ve açıklamayı göster

Cevap: Provision a Premium SSD disk for the transaction logs. Store the backups in a Geo-Redundant Storage (GRS) Blob storage account. Configure a Shared Access Signature (SAS) associated with a stored access policy for the auditor.

Cevap

Provision a Premium SSD disk for the transaction logs, store backups in a Geo-Redundant Storage (GRS) Blob storage account, and configure a Shared Access Signature (SAS) associated with a stored access policy for the auditor.
The solution that combines Premium SSD, Geo-Redundant Storage (GRS), and a SAS token associated with a stored access policy is correct. Premium SSD provides the necessary IOPS and sub-millisecond write latency for database transaction logs. GRS replicates backup data to a secondary Azure region to survive a primary regional disaster. Linking the auditor's SAS token to a stored access policy enables administrators to instantly revoke access by deleting or altering the policy, without modifying the storage account keys or disrupting other applications.

Adım Adım Çözüm

1
Evaluate the database transaction logs' performance and latency needs.
Determine that magnetic storage (Standard HDD) is unsuitable, and Premium SSD, Premium SSD v2, or Ultra Disk is required to guarantee at least 25,00025,000 IOPS and sub-millisecond write latency.
Standard HDD/SSD tiers cannot provide high IOPS alongside consistent sub-millisecond write performance.
2
Determine the redundancy level required to survive a complete regional outage.
Select Geo-Redundant Storage (GRS) or Geo-Zone-Redundant Storage (GZRS) for the backups.
Locally Redundant Storage (LRS) and Zone-Redundant Storage (ZRS) only replicate data within the primary region and would be lost if the entire region failed.
3
Analyze the access control and revocation requirements for the external auditor.
Choose a Shared Access Signature (SAS) linked to a Stored Access Policy.
An ad-hoc SAS cannot be revoked without rotating storage account keys. Associating the SAS with a stored access policy allows revocation by simply deleting or updating the policy on the container.

Anahtar Kavram

Selecting appropriate Azure disk tiers for performance, configuring storage replication for regional disaster recovery, and securing blob access using delegable and revocable stored access policies.

Alternatif Yöntem

Instead of Premium SSD, you could also use Ultra Disk for the transaction logs to achieve sub-millisecond latency, but Premium SSD remains a valid and cost-effective choice for meeting the specified 25,00025,000 IOPS requirement.
Tahmini Süre:3m 0s
Soru 145Soru

A manufacturing enterprise is designing a monitoring and log routing architecture for its workloads deployed across the West US 3 and West Europe regions. The design must satisfy the following constraints:
- All application logs generated in the West Europe region must reside in Europe to comply with local data sovereignty regulations.
- Operations team members who only manage West US 3 resources must only be allowed to view logs originating from those West US 3 resources.
- High-priority security alerts must be streamed in near real-time to a third-party Security Information and Event Management (SIEM) system.
- The deployment and maintenance of diagnostic settings should be automated.

Which two of the following components should you include in the design? (Select two.)

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

Cevabı ve açıklamayı göster

Cevap: A Log Analytics workspace in West Europe and a Log Analytics workspace in West US 3; An Azure Event Hubs namespace to stream log data to the third-party SIEM

Cevap

A Log Analytics workspace in West Europe and a Log Analytics workspace in West US 3, along with an Azure Event Hubs namespace to stream log data to the third-party SIEM.
The correct architecture requires a multi-workspace approach (a Log Analytics workspace in West Europe and another in West US 3) to comply with data sovereignty guidelines that mandate European logs remain in Europe. Additionally, an Azure Event Hubs namespace is required to handle near real-time streaming of security alerts to an external SIEM system.

Adım Adım Çözüm

1
Address data sovereignty requirements.
Identify that a dedicated Log Analytics workspace must be provisioned in West Europe to keep European log data within Europe, and a separate workspace in West US 3.
Data residency regulations prevent sending West Europe log data to a US-based workspace.
2
Determine the streaming mechanism for the third-party SIEM.
Include Azure Event Hubs in the architecture to act as an ingestion point for near real-time log streaming.
Event Hubs is the standard Azure component for streaming logs to external SIEM systems in near real-time.
3
Evaluate access and governance configuration.
Ensure security groups are used for RBAC assignment, and rely on DeployIfNotExists policies to automate diagnostic configurations.
This aligns with governance best practices and minimizes administrative overhead.

Anahtar Kavram

Designing compliant, regional log routing using separate Log Analytics workspaces for data residency and utilizing Event Hubs for real-time external log integration.
Tahmini Süre:2m 0s
Soru 146Soru

A company named Kusto Corp has a multi-subscription Azure environment managed under a single management group named Kusto-Global. The company wants to enforce database security. Specifically, all Azure SQL databases in all subscriptions must have vulnerability assessment scanning enabled. If a SQL database is deployed without a vulnerability assessment configuration, the system must automatically deploy the configuration after the database is created, using a specific storage account for scan results. Additionally, the security team wants to exempt a subscription named Kusto-Sandbox, which is under Kusto-Global, from this compliance requirement. You need to design an Azure Policy solution that meets these requirements with the least administrative overhead. Which Azure Policy configuration should you recommend?

Cevabı ve açıklamayı göster

Cevap: Assign a policy using the DeployIfNotExists effect at the Kusto-Global management group scope, and configure the Kusto-Sandbox subscription as an exclusion (notScopes).

Cevap

Assign a policy using the DeployIfNotExists effect at the Kusto-Global management group scope, and configure the Kusto-Sandbox subscription as an exclusion (notScopes).
The correct configuration uses the DeployIfNotExists effect because enabling vulnerability assessment requires deploying a nested resource (the settings and storage account target) if it does not already exist. Assigning the policy at the management group level with the sandbox subscription defined in the notScopes property ensures the policy inherits across all other subscriptions while exempting the sandbox, minimizing administrative overhead.

Adım Adım Çözüm

1
Determine the required policy effect based on the remediation needs.
The requirement calls for automatic post-deployment configuration of vulnerability assessment settings when they are missing. This is a complex template deployment of a dependent resource rather than a simple property modification. Therefore, the DeployIfNotExists effect is required.
DeployIfNotExists allows automatic remediation of nested or dependent resources by deploying a templates-based configuration post-deployment.
2
Determine the assignment scope and exclusion model.
Assign the policy at the parent management group (Kusto-Global) and configure Kusto-Sandbox in the exclusion list (notScopes).
This leverages inheritance to apply the policy to all production subscriptions while exempting the sandbox subscription, minimizing administrative overhead.

Anahtar Kavram

Azure Policy effects and scope exclusion management in management group hierarchies.
Soru 147Soru

An organization plans to migrate an on-premises ERP application and its SQL Server database to Azure. The migration must meet the following requirements:
- Support SQL Server Agent jobs for internal database maintenance.
- Enable cross-database queries between databases hosted on the same instance.
- Minimize administrative effort for database host patching, operating system management, and backups.
- Provide automatic failover to a secondary Azure region with a single write listener endpoint in the event of a regional outage.

Which two technologies should you recommend to meet these requirements? (Select two.)

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

Cevabı ve açıklamayı göster

Cevap: Azure SQL Managed Instance; Failover groups

Cevap

Azure SQL Managed Instance and Failover groups
Azure SQL Managed Instance provides the required native SQL Server Agent and cross-database query support within a fully managed PaaS framework, minimizing administrative overhead. Failover groups provide the replication and automatic failover mechanism to a secondary region while presenting a single connection listener endpoint to client applications.

Adım Adım Çözüm

1
Analyze database compatibility requirements.
SQL Server Agent and cross-database queries are required. This rules out Azure SQL Database single database and elastic pool options, pointing to SQL Server on Azure VM or Azure SQL Managed Instance.
Azure SQL Database single database options do not natively support SQL Server Agent or cross-database queries.
2
Analyze administrative overhead constraints.
SQL Server on Azure VM is ruled out because it requires managing OS patching, virtual machines, and backup agents.
Azure SQL Managed Instance is a PaaS service that minimizes host management and patching effort while retaining legacy compatibility features.
3
Determine the regional failover and connectivity architecture.
Failover groups are selected to manage geo-replication and automatic failover with a single connection listener.
Failover groups provide automatic group failover and DNS listener redirection across Azure SQL Managed Instances in different regions.

Anahtar Kavram

Selecting and configuring Relational Data Storage Solutions in Azure based on compatibility, management overhead, and regional failover requirements.
Soru 148Soru

A logistics company plans to migrate an on-premises SQL Server database system to Azure. The migration must meet the following requirements:

* Support scheduled data aggregation jobs using SQL Server Agent.
* Enable cross-database queries using three-part names across multiple databases on the same instance.
* Ensure the database is natively deployed within a private virtual network subnet with no public endpoints.
* Minimize administrative effort for managing operating system patching and physical storage.

Which database solution should you recommend?

Cevabı ve açıklamayı göster

Cevap: Azure SQL Database Managed Instance

Cevap

Azure SQL Database Managed Instance
Azure SQL Database Managed Instance is the correct choice because it is a fully managed (PaaS) relational database service that supports SQL Server Agent, native virtual network integration, and cross-database queries. This fulfills all technical requirements while minimizing the administrative overhead associated with managing the underlying operating system and hardware.

Adım Adım Çözüm

1
Analyze compatibility requirements
SQL Server Agent and native cross-database queries with three-part names require either SQL Server on Azure Virtual Machines or Azure SQL Database Managed Instance.
Azure SQL Database (single database or elastic pools) does not natively support SQL Server Agent or standard three-part cross-database queries.
2
Evaluate network isolation requirements
Both Azure SQL Database Managed Instance and SQL Server on Azure VMs support native deployment into a private virtual network subnet.
This requirement rules out standard Azure SQL Database deployments that rely on public endpoints unless private endpoints are configured, but Managed Instance natively deploys into a delegated subnet.
3
Assess administrative effort limits
Azure SQL Database Managed Instance is a platform-as-a-service (PaaS) offering, whereas SQL Server on Azure VMs is infrastructure-as-a-service (IaaS).
Because the scenario specifies minimizing administrative effort for OS patching and physical storage, Managed Instance is the best fit as a PaaS option.

Anahtar Kavram

Relational Data Storage Solutions selection based on feature compatibility and administrative effort
Soru 149Soru

An organization is designing a shared storage solution for a financial reporting application hosted on Azure Virtual Machines. The application has the following requirements:
- Concurrent access from multiple VMs using the SMB protocol.
- High-throughput, sub-millisecond latencies for metadata operations.
- Maximum resilience against localized datacenter outages within the primary Azure region.
- Access to the storage must be secured using Shared Access Signatures (SAS) that can be instantly revoked if compromised, without rotating the storage account keys.

Which storage configuration should you recommend?

Cevabı ve açıklamayı göster

Cevap: Premium Azure Files share with Zone-Redundant Storage (ZRS), secured using SAS tokens associated with a stored access policy

Cevap

Premium Azure Files share with Zone-Redundant Storage (ZRS), secured using SAS tokens associated with a stored access policy
The correct configuration uses Premium Azure Files with Zone-Redundant Storage (ZRS) and SAS tokens tied to a stored access policy. Premium Azure Files guarantees sub-millisecond latency for metadata-heavy operations. ZRS replicates data across three availability zones within the primary region, providing high availability against datacenter failures. Stored access policies allow granular control and immediate revocation of SAS tokens without rotating the storage account keys.

Adım Adım Çözüm

1
Determine the storage type and protocol required.
Azure Files is selected because the application requires shared file storage with concurrent SMB protocol access from multiple virtual machines.
Azure Files natively supports SMB, whereas block storage like Azure Managed Disks requires a cluster manager to share volumes, and Azure Blob storage primarily uses REST/NFS.
2
Determine the performance tier and redundancy configuration.
Premium tier is chosen for sub-millisecond metadata latency. ZRS (Zone-Redundant Storage) is chosen to survive a localized datacenter (Availability Zone) outage.
Standard tier does not guarantee sub-millisecond metadata latency. LRS only replicates data within a single datacenter and cannot survive a zone failure.
3
Select the security configuration that allows instant revocation of access.
SAS tokens associated with a stored access policy are chosen.
Ad-hoc SAS tokens cannot be revoked individually; revoking them requires rotating the storage account keys, which would disrupt all other clients. A stored access policy can be deleted or modified to instantly revoke associated SAS tokens.

Anahtar Kavram

Selecting the correct Azure Files tier, redundancy model, and access security configuration to meet performance, high availability, and compliance requirements.
Soru 150Soru

An enterprise is planning to migrate a mission-critical on-premises SQL Server database to Azure. The database has the following requirements:

* Must support legacy features including SQL Server Agent jobs, cross-database queries, and Common Language Runtime (CLR) integration.
* Must support read scale-out to offload reporting workloads to a read-only replica in the primary region.
* Must support automated cross-region failover to a secondary Azure region.
* Must minimize administrative effort for operating system and database engine updates.

Which two components should you include in the recommendation?

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

Cevabı ve açıklamayı göster

Cevap: Azure SQL Managed Instance in the Business Critical service tier; An auto-failover group

Cevap

Azure SQL Managed Instance in the Business Critical service tier and an auto-failover group
To support legacy features like SQL Server Agent, CLR, and cross-database queries while minimizing administrative overhead, Azure SQL Managed Instance is the correct deployment choice. Specifically, the Business Critical service tier is required to support read scale-out for offloading reporting workloads. To achieve automated cross-region failover, an auto-failover group must be configured.

Adım Adım Çözüm

1
Identify the relational database features required by the legacy workload: SQL Server Agent jobs, cross-database queries, and CLR integration.
Azure SQL Database (single database/elastic pool) is ruled out because it does not natively support SQL Server Agent, cross-database queries, or CLR. Only Azure SQL Managed Instance and SQL Server on Azure VMs support these features.
Managed Instance provides near 100% compatibility with the on-premises SQL Server database engine.
2
Analyze the administrative effort constraint: minimize operating system and database engine updates.
SQL Server on Azure VMs is ruled out because it requires manual or semi-automated management of the underlying OS and SQL Server patching.
Azure SQL Managed Instance is a fully managed Platform as a Service (PaaS) that handles OS and database patching automatically.
3
Evaluate the read scale-out and regional disaster recovery requirements: read scale-out in the primary region, and automated cross-region failover.
Select Azure SQL Managed Instance in the Business Critical tier (which includes a free, built-in read-only replica for read scale-out) and configure an auto-failover group to enable automated replication and failover to a secondary region.
General Purpose tier does not support read scale-out, whereas Business Critical does. Auto-failover groups provide the required regional failover capabilities.

Anahtar Kavram

Selecting the appropriate Azure SQL relational database deployment option based on legacy feature compatibility, administrative overhead, and high availability/disaster recovery requirements.
Tahmini Süre:3m 0s
Soru 151Soru

Aventis Logistics is designing a hybrid identity solution to integrate their on-premises Active Directory Domain Services (AD DS) forest of 6,200 users with a Microsoft Entra ID tenant. The design must satisfy the following requirements:
- Users must be able to sign in to Azure resources using their current on-premises passwords.
- Users must be able to perform self-service password resets from the cloud, and these updates must immediately synchronize back to the on-premises directory.
- The sign-in service must remain operational for users even if the network link between the on-premises datacenter and Azure is temporarily offline.
- On-premises server infrastructure and administrative overhead must be minimized.
Which two components should you include in the hybrid identity design? (Select two.)

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

Cevabı ve açıklamayı göster

Cevap: Password Hash Synchronization (PHS) as the hybrid identity authentication method; Microsoft Entra self-service password reset (SSPR) with password writeback enabled

Cevap

Password Hash Synchronization (PHS) as the hybrid identity authentication method and Microsoft Entra self-service password reset (SSPR) with password writeback enabled
Password Hash Synchronization (PHS) is the correct authentication method because it processes authentication requests in the cloud, enabling users to log in even when the network connection to the on-premises environment is disconnected, while requiring the least administrative and server footprint. Enabling Microsoft Entra SSPR with password writeback satisfies the constraint to allow users to reset their passwords in Microsoft Entra ID and sync those modifications back to the local Active Directory Domain Services.

Adım Adım Çözüm

1
Analyze authentication business continuity requirements.
Identify that only Password Hash Synchronization (PHS) stores a representation of user passwords in the cloud, allowing authentication to proceed during a network outage between the on-premises datacenter and Azure. Pass-Through Authentication (PTA) and federation depend on live on-premises communication.
To satisfy the requirement that sign-in remains functional during network disconnects.
2
Analyze on-premises infrastructure footprint requirements.
Confirm that PHS requires only Microsoft Entra Connect agents and has the lowest infrastructure footprint compared to PTA and AD FS. AD FS requires complex on-premises federation and proxy deployments.
To ensure the solution minimizes on-premises infrastructure and administrative overhead.
3
Address the self-service password reset and writeback requirements.
Integrate Microsoft Entra self-service password reset (SSPR) with password writeback enabled to write cloud-based password resets back to the on-premises AD DS.
To meet the self-service password reset and bidirectional synchronization requirements.

Anahtar Kavram

Selecting and designing hybrid identity authentication and password management features based on availability, infrastructure footprint, and synchronization constraints.
Soru 152Soru

An organization is deploying a globally distributed multiplayer game. You are designing the Azure Cosmos DB NoSQL API account to store player profile data. The database must replicate data between East US and West US to support a read/write ratio of 70%70\% reads and 30%30\% writes. The architecture requires a 99.999%99.999\% availability SLA for both read and write operations. The player profile documents contain a unique `playerId`, a `countryCode` (with 55 possible values), and a `lastLoginTimestamp`.

Which two options should you include in the design to meet the SLA and performance requirements? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Enable write operations in multiple regions for the database account.; Configure playerId as the partition key for the player profile container.

Cevap

Configure write operations in multiple regions and choose playerId as the partition key.
To achieve a 99.999%99.999\% write availability SLA in Azure Cosmos DB, the database account must be configured with write operations enabled in multiple regions. Additionally, to maintain high performance and prevent hot partitions under write load, the partition key must have high cardinality. Since playerId is unique for each player, it serves as an excellent partition key to distribute database operations evenly.

Adım Adım Çözüm

1
Analyze availability requirements.
The target SLA is 99.999%99.999\% for both reads and writes.
Azure Cosmos DB requires multi-region writes to guarantee a 99.999%99.999\% write availability SLA.
2
Select a partition key based on cardinality.
playerId is selected over countryCode.
A high-cardinality partition key like playerId prevents hot partitions by distributing requests evenly across logical partitions.

Anahtar Kavram

Azure Cosmos DB high availability configuration and partition key design.
Soru 153Soru

An enterprise is designing a secure identity and access management infrastructure. You are tasked with mapping specific access control requirements to their corresponding Microsoft Entra ID or Conditional Access configuration. Match each requirement on the left to the most appropriate configuration on the right to satisfy the requirement.

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

Öğeler

Ensure that external consultants can only access corporate web apps from compliant devices or trusted locations, and force them to re-authenticate after 4 hours of inactivity.
Require administrative users to use FIDO2 security keys to manage Azure resources, and grant them high-privilege roles only for a maximum duration of 8 hours upon manager approval.
Guarantee that the tenant remains manageable if a major service outage affects Entra MFA, while ensuring any sign-in by these recovery accounts is immediately notified to security operations.
Detect when an employee's password has been leaked on the dark web and immediately prevent them from signing in until an administrator resets their password.

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

Match the external consultant session timeout to the Conditional Access policy with grant and session controls; the administrative FIDO2 and PIM role activation to the PIM role settings combined with CA authentication strengths; the tenant management resilience to the emergency access accounts excluded from CA policies and monitored; and the leaked password detection to the Microsoft Entra ID Protection User risk policy.
The requirement for external consultant session limits maps to Conditional Access session controls. Enforcing phishing-resistant MFA and approval-based elevation maps to Privileged Identity Management (PIM) integrated with CA authentication strengths. Tenant resiliency during MFA outages maps to emergency access accounts excluded from CA policies. Automated blocking for leaked credentials maps to the Microsoft Entra ID Protection User risk policy.

Adım Adım Çözüm

1
Analyze requirement for external consultants.
Identified the need for conditional access based on device compliance/location and session expiration (4-hour frequency limit).
Enforcing location/compliance and a 4-hour timeout requires a Conditional Access policy using both grant and session controls.
2
Analyze requirement for developer administrative access.
Identified the need for phishing-resistant MFA (FIDO2) and approval-based, time-bound privilege activation.
FIDO2 authentication strength is enforced via Conditional Access, and temporary, approved role assignment is managed via Microsoft Entra Privileged Identity Management (PIM).
3
Analyze requirement for emergency lockout resilience.
Identified the need for emergency access (break-glass) accounts that bypass CA policies, coupled with alert monitoring.
Excluding emergency accounts from CA prevents lockout during MFA outages, and monitoring their login activity via Azure Monitor ensures security visibility.
4
Analyze requirement for dark web credential leaks.
Identified the need to block compromised users immediately.
Microsoft Entra ID Protection detects leaked credentials as high user risk, triggering the configured User risk policy to block access.

Anahtar Kavram

Microsoft Entra ID Authentication and Conditional Access
Tahmini Süre:3m 0s
Soru 154Soru

An organization named CloudVibe is designing a governance strategy for its Azure subscriptions. The subscriptions are organized under a single management group named CloudVibe-MG.

The organization has the following compliance and security requirements:
- Automatically enable Azure Backup for all new virtual machines deployed to the production subscription. If a virtual machine is deployed without a backup configuration, the backup must be configured automatically without manual intervention.
- Prevent developers from creating public IP addresses in the development subscription.

You need to recommend the Azure Policy configurations to meet these requirements.

Which two policy configurations should you include in the design?

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

Cevabı ve açıklamayı göster

Cevap: An Azure Policy assignment at the production subscription scope using a policy definition with the DeployIfNotExists effect to enable backup.; An Azure Policy assignment at the development subscription scope using a policy definition with the Deny effect to block public IP addresses.

Cevap

The correct configurations are to assign a policy definition with the DeployIfNotExists effect to the production subscription to enable backup, and to assign a policy definition with the Deny effect to the development subscription to block public IP addresses.
The correct answer combines DeployIfNotExists for automated backup deployment and Deny to block the creation of public IP addresses. DeployIfNotExists evaluates a resource and deploys a template (like a backup association) if it is missing, satisfying the first requirement. The Deny effect blocks the creation or update of resources that do not match the policy criteria, satisfying the second requirement to prevent public IP address creation in the development subscription.

Adım Adım Çözüm

1
Analyze the backup requirement.
The requirement specifies that Azure Backup must be enabled automatically if a VM is deployed without it, with no manual intervention. This implies automatic remediation.
Automatic remediation of missing resource configurations requires the DeployIfNotExists (DINE) effect, which deploys the required backup configuration resource. The Modify effect can only alter resource fields/tags but cannot perform resource deployments.
2
Analyze the public IP prevention requirement.
The requirement states that developers must be prevented from creating public IP addresses in the development subscription.
To block or prevent the creation of non-compliant resources, the Deny effect is the correct choice. The Audit effect only flags non-compliance after deployment but does not block the creation.
3
Select the correct scopes for the policy assignments.
Assign the DeployIfNotExists backup policy to the production subscription, and the Deny public IP policy to the development subscription.
Targeting the specific subscription scopes ensures that the policies only apply to their respective environments without affecting other subscriptions under the management group.

Anahtar Kavram

Azure Policy effects (DeployIfNotExists and Deny) are used to enforce compliance by automatically remediating missing configurations or blocking the creation of prohibited resources.
Soru 155Soru

An organization is designing the storage infrastructure for a mission-critical financial application hosted on Azure Virtual Machines. The application requires a database data drive that must support at least 15,00015,000 IOPS and sub-millisecond write latency. The database files must survive a storage zone failure. Additionally, you must provide secure, temporary, write-only access to specific database backup blobs for external auditors, and this access must be easily revocable at any time. Which two configurations should you include in the storage design? (Select two.)

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

Cevabı ve açıklamayı göster

Cevap: Configure the database data drive using Premium SSD v2 managed disks with zone-redundant storage (ZRS).; Generate a Shared Access Signature (SAS) token that is associated with a Stored Access Policy.

Cevap

Configure the database data drive using Premium SSD v2 managed disks with zone-redundant storage (ZRS), and generate a Shared Access Signature (SAS) token associated with a Stored Access Policy.
Premium SSD v2 managed disks support zone-redundant storage (ZRS) while delivering the required 15,00015,000 IOPS and sub-millisecond latency. Additionally, associating the SAS token with a Stored Access Policy provides the ability to revoke access immediately by deleting or modifying the policy.

Adım Adım Çözüm

1
Analyze database performance and redundancy needs.
The application requires at least 15,00015,000 IOPS, sub-millisecond latency, and protection against zone outages. This rules out Standard SSDs (insufficient performance) and Ultra Disks (lack ZRS support). Premium SSD v2 supports ZRS and can meet the performance requirements.
Choosing the correct disk type ensures both high-performance SLAs and zone-level resilience are met simultaneously.
2
Analyze security and revocation requirements for external access.
Temporary access must be write-only and easily revocable. An ad-hoc SAS token defined in the URI cannot be revoked without rotating delegation keys. A SAS token linked to a Stored Access Policy can be revoked instantly by removing or altering the policy.
Associating SAS tokens with Stored Access Policies is the standard Azure best practice for managing and revoking external access without disrupting other operations.

Anahtar Kavram

Selecting high-performance Azure disk types that support zone-redundant storage (ZRS), and implementing revocable blob access using Shared Access Signatures (SAS) associated with Stored Access Policies.
Soru 156Soru

An organization plans to migrate two on-premises SQL Server databases to Azure. The migration must meet the following requirements:

* Database 1: Requires native SQL Server Agent jobs and cross-database queries. The organization wants to minimize administrative overhead, including operating system patching.
* Database 2: Requires access to the underlying operating system to run a proprietary third-party compliance agent. The database transaction log files require high-throughput and low-latency storage.

Which two database solutions should you include in the design?

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

Cevabı ve açıklamayı göster

Cevap: Azure SQL Managed Instance for Database 1; SQL Server on Azure Virtual Machines with Premium SSD storage for Database 2

Cevap

Azure SQL Managed Instance for Database 1, and SQL Server on Azure Virtual Machines with Premium SSD storage for Database 2
Azure SQL Managed Instance is the correct choice for Database 1 because it supports instance-level features such as SQL Server Agent and cross-database queries while eliminating the overhead of OS management. SQL Server on Azure VMs with Premium SSD is the correct choice for Database 2 because it provides full control over the underlying OS to install third-party agents, and Premium SSD storage delivers the low latency and high performance required for database transaction logs.

Adım Adım Çözüm

1
Analyze the requirements for Database 1.
Database 1 requires SQL Server Agent and cross-database queries, combined with reduced OS management overhead.
These parameters point to Azure SQL Managed Instance, which is a fully managed PaaS solution supporting these instance-scoped features.
2
Analyze the requirements for Database 2.
Database 2 requires direct OS access for third-party tools and high-performance storage for log files.
Direct OS access requires SQL Server on Azure VMs (IaaS). Transaction logs require Premium SSD or Ultra disk for low latency and high throughput.
3
Evaluate the options and select the correct match.
Azure SQL Managed Instance is selected for Database 1, and SQL Server on Azure VMs with Premium SSD is selected for Database 2.
This setup correctly satisfies both the OS access restriction and the database capability constraints.

Anahtar Kavram

Selecting the appropriate Azure SQL deployment option (PaaS vs. IaaS) and storage tier based on operational, feature, and performance requirements.
Soru 157Soru

A financial services provider is planning to transition a localized underwriting database to Microsoft Azure. The database deployment must satisfy the following constraints:

* Support the execution of complex SQL Server Integration Services (SSIS) packages scheduled via SQL Server Agent.
* Permit the execution of cross-database queries across two distinct schemas within the same relational engine.
* Ensure direct connectivity via virtual network (VNet) delegation for private communication.
* Reduce administrative overhead associated with operating system patching and storage management.

Which database solution should you recommend?

Cevabı ve açıklamayı göster

Cevap: Azure SQL Managed Instance

Cevap

Azure SQL Managed Instance
Azure SQL Managed Instance satisfies all defined constraints. It is a fully managed PaaS solution that eliminates operating system patching overhead. It supports SQL Server Agent, cross-database queries within the same instance, and native virtual network (VNet) delegation, which aligns perfectly with the requirements.

Adım Adım Çözüm

1
Analyze the application compatibility requirements.
The requirements for SQL Server Agent and cross-database queries rule out Azure SQL Database single database and elastic pools.
Azure SQL Database single database and elastic pools do not support SQL Server Agent or three-part name cross-database queries natively.
2
Evaluate the administrative overhead constraints.
The requirement to reduce administrative overhead for OS patching and storage management rules out SQL Server on Azure Virtual Machines.
SQL Server on Azure VMs is an IaaS service, leaving the responsibility of OS and SQL Server patching to the administrator.
3
Verify networking requirements for the remaining option.
Azure SQL Managed Instance supports native VNet delegation, ensuring private communication.
Azure SQL Managed Instance is designed for secure, private VNet injection.

Anahtar Kavram

Azure SQL service selection based on SQL Server feature compatibility, administrative overhead, and network security constraints.
Soru 158Soru

Tailwind Traders is designing an identity security strategy for its Microsoft Entra ID tenant. The organization plans to implement a Conditional Access policy that requires Multi-Factor Authentication (MFA) for all users when accessing Azure management portals. The architect must ensure that administrators do not get locked out of the tenant if there is an outage of the MFA service or if the policy is misconfigured. Which of the following configurations should the architect include in the security design?

Cevabı ve açıklamayı göster

Cevap: Create a dedicated, cloud-only emergency access account that is excluded from the Conditional Access policy.

Cevap

Create a dedicated, cloud-only emergency access account that is excluded from the Conditional Access policy.
The correct configuration is to create a dedicated, cloud-only emergency access account that is excluded from the Conditional Access policy. Microsoft best practices recommend having at least two emergency access accounts that are excluded from Conditional Access policies to prevent lockout during service outages or policy misconfigurations.

Adım Adım Çözüm

1
Identify the risk of tenant-wide lockout when requiring MFA via Conditional Access policies.
Recognized that policy misconfigurations or MFA service outages can prevent all administrators from authenticating.
Establishing a mitigation path is necessary to maintain tenant management access under failure conditions.
2
Select the appropriate mitigation mechanism according to Microsoft best practices.
Determine that creating a dedicated, cloud-only emergency access account (break-glass account) is the standard method.
Cloud-only accounts do not rely on on-premises sync, and separating them from standard policies avoids policy-induced lockouts.
3
Exclude the emergency access account from all tenant-wide Conditional Access MFA policies.
The break-glass account is excluded from the policy scope, ensuring it can log in using password-only credentials during emergencies.
This exclusion prevents the account from being blocked by the very policy or service outage that caused the lockout.

Anahtar Kavram

Microsoft Entra ID emergency access accounts are critical for preventing tenant lockout when designing Conditional Access policies.
Soru 159Soru

An educational technology provider is designing a monitoring and audit log routing architecture for its multi-tenant platform. You need to match each workload telemetry source or monitoring requirement to its most appropriate Azure destination or storage configuration to optimize cost, performance, and capability.

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

Öğeler

Microsoft Entra ID sign-in logs that must be sent to an external, third-party SIEM system
Virtual machine boot diagnostics screenshots and serial logs that are rarely accessed
Subscription-level deployment and management events that must be kept for 90 days at zero extra cost
Container performance metrics and console logs that require complex correlation using Kusto Query Language (KQL)

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

The correct matches are: Microsoft Entra ID sign-in logs match with Azure Event Hubs; Virtual machine boot diagnostics match with Azure Storage account; Subscription-level events match with Azure Activity Log default store; Container logs requiring KQL match with Azure Log Analytics workspace.
The solution correctly pairs each monitoring telemetry source with the destination that matches its functional and cost constraints. Third-party SIEM integration is achieved via Azure Event Hubs. Boot diagnostics utilize Azure Storage for cost-effective unstructured storage. Activity logs are kept in their default store for 90 days for free. Container logs requiring complex queries are routed to a Log Analytics workspace.

Adım Adım Çözüm

1
Analyze the real-time external integration requirement.
Streaming logs to a third-party SIEM requires a message ingestion service, making Azure Event Hubs the correct choice.
Azure Event Hubs serves as the standard pipeline for forwarding log data to non-Azure monitoring systems.
2
Determine the lowest-cost option for boot diagnostics.
Boot diagnostics consist of screenshots and serial console text, which are stored as unstructured files in an Azure Storage account.
Using a Log Analytics workspace for boot diagnostics would incur unnecessary ingestion and retention costs.
3
Evaluate the subscription audit log retention constraint.
The Azure Activity Log platform store keeps the last 90 days of management events free of charge.
Since the requirement is 90 days of history at zero extra cost, routing them to another workspace or storage account is unnecessary.
4
Identify the target for KQL querying and metrics analytics.
A Log Analytics workspace is required to run KQL queries.
KQL is the query language for Azure Monitor Logs stored within Log Analytics workspaces.

Anahtar Kavram

Selecting log routing destinations based on query, cost, retention, and integration requirements.
Soru 160Soru

A company named Solis Energy is designing a governance strategy for its Azure subscriptions. The subscriptions are organized under a parent management group named Solis-Production.

The company has the following requirements:
1. All newly deployed virtual machines must have the Azure Monitor Dependency Agent installed automatically.
2. Virtual machines deployed in a specific subscription named Solis-DevTest, which is nested under Solis-Production, must not have the agent installed to minimize costs.
3. The solution must minimize administrative overhead.

Which Azure Policy design should you recommend?

Cevabı ve açıklamayı göster

Cevap: Assign an Azure Policy containing a DeployIfNotExists effect at the Solis-Production management group scope, and configure the Solis-DevTest subscription in the notScopes property of the assignment.

Cevap

Assign an Azure Policy containing a DeployIfNotExists effect at the Solis-Production management group scope, and configure the Solis-DevTest subscription in the notScopes property of the assignment.
The DeployIfNotExists effect is designed to deploy a template (such as a VM extension) if it does not exist when a resource is created or updated. Assigning the policy at the management group level ensures inheritance across all nested subscriptions. Using the notScopes property in the assignment is the standard method to exclude specific scopes (like the Solis-DevTest subscription) from the policy's effect without needing to manage multiple separate assignments, thereby minimizing administrative overhead.

Adım Adım Çözüm

1
Identify the policy effect that can automatically deploy resources or extensions.
The DeployIfNotExists effect is selected because it enables automatic deployment of the Dependency Agent extension when a virtual machine is created or updated.
To satisfy the requirement of automatic installation of the agent without blocking VM deployment.
2
Determine the optimal scope and exclusion mechanism.
Assign the policy at the Solis-Production management group scope and list the Solis-DevTest subscription in the notScopes (exclusions) property of the assignment.
To apply the policy to all subscriptions under the management group while cleanly excluding the DevTest subscription with minimal administrative overhead.

Anahtar Kavram

Azure Policy effects and assignment scope exclusions
ÖncekiSayfa 8 / 60Sonraki
Tüm alıştırma soruları — Microsoft Azure Solutions Architect (AZ-305) | Examkin