Tüm alıştırma soruları

1198 soru

Soru 281Soru

You are designing a disaster recovery (DR) solution for a critical financial application migrating to Azure. The application database has the following requirements:
- Employs native cross-database queries and relies heavily on SQL Server Agent jobs.
- Requires database replication between East US (primary) and West US (secondary).
- The write workload must connect via a single endpoint that remains unchanged during a failover.
- Reporting applications must run read-only queries against the secondary region using a dedicated endpoint.
- All database traffic must remain within private virtual networks without traversing the public internet.

Which database configuration should you recommend to meet these requirements?

Cevabı ve açıklamayı göster

Cevap: Deploy a primary Azure SQL Managed Instance in East US and a secondary Azure SQL Managed Instance in West US. Configure an Auto-Failover Group between the instances and connect the application using the failover group's read-write and read-only listener endpoints.

Cevap

Deploy a primary Azure SQL Managed Instance in East US and a secondary Azure SQL Managed Instance in West US. Configure an Auto-Failover Group between the instances and connect the application using the failover group's read-write and read-only listener endpoints.
The correct solution involves deploying Azure SQL Managed Instance in both regions and linking them via an Auto-Failover Group. SQL Managed Instance provides the necessary SQL Server features (SQL Server Agent and cross-database queries) required for legacy application migration. The Auto-Failover Group supplies a read-write listener endpoint and a read-only listener endpoint, satisfying the requirement for an unchanged client connection string for writes and a dedicated endpoint for reporting workloads. Because SQL Managed Instances are deployed directly within Azure Virtual Networks, the entire configuration maintains private network isolation.

Adım Adım Çözüm

1
Evaluate application requirements for database features.
The requirement for native cross-database queries and SQL Server Agent jobs rules out Azure SQL Database (Single Database or Elastic Pool) and points to Azure SQL Managed Instance or SQL Server on Azure VMs.
Azure SQL Database does not support these features natively.
2
Evaluate endpoint requirements for HA/DR.
The requirement for a single unchanged endpoint for writes and a dedicated endpoint for reads points to Auto-Failover Groups, which provide read-write and read-only listener endpoints.
Active geo-replication or SQL VM configurations without additional routing components (like distributed network names or load balancers) do not natively offer these endpoints without connection string changes.
3
Assess storage performance constraints.
Standard HDD is rejected for hosting transaction logs.
Database transaction logs require low-latency and high-IOPS storage (Premium SSD or Ultra Disk) to function correctly under production workloads.

Anahtar Kavram

Selecting the correct Azure relational database service and configuring high availability/disaster recovery with Auto-Failover Groups to support legacy SQL Server features and read-scale listeners over private networks.
Tahmini Süre:3m 0s
Soru 282Soru

A software development company is designing a security and access control strategy for an Azure Storage account named devlogs. You must design a solution that meets the following requirements:

1. A team of five internal security auditors must be granted temporary access to read audit logs in a specific blob container for 90 days. The solution must support immediate revocation of this access.
2. A database administrator must be able to manage the storage account configurations, but only when actively performing scheduled maintenance tasks. This administrative access must not be permanently active.
3. Access configuration must follow the principle of least privilege and minimize administrative overhead.

Which two actions should you include in the design?

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

Cevabı ve açıklamayı göster

Cevap: Configure a Microsoft Entra Privileged Identity Management (PIM) eligible role assignment for the database administrator.; Create a stored access policy on the container, and generate a service shared access signature (SAS) token associated with the policy.

Cevap

To secure access, you should configure a Microsoft Entra Privileged Identity Management (PIM) eligible role assignment for the database administrator, and create a stored access policy on the container to generate an associated service shared access signature (SAS) token.
To fulfill the database administrator requirement, configuring an eligible role assignment in Microsoft Entra Privileged Identity Management (PIM) ensures the administrator must explicitly activate the role for a limited time when performing maintenance, avoiding permanently active administrative rights. To fulfill the auditor requirement, a stored access policy controls the service SAS token's validity and allows immediate revocation by modifying or deleting the policy, avoiding storage key rotation.

Adım Adım Çözüm

1
Analyze the database administrator's administrative access requirement.
The database administrator needs scheduled, temporary access to manage storage account configurations.
Using Microsoft Entra Privileged Identity Management (PIM) with an eligible assignment ensures that the role is only active when needed (just-in-time) rather than permanently active, satisfying the principle of least privilege.
2
Analyze the security auditors' temporary access requirement.
The auditors need read-only access to a specific container for 90 days, with the ability to revoke access immediately.
A stored access policy defined on the container allows you to control the start time, expiry time, and permissions of a service SAS token. Deleting or modifying the policy immediately revokes the SAS token's access without rotating storage account keys.
3
Evaluate the incorrect options against security best practices.
Direct RBAC assignments, permanently active PIM roles, and ad-hoc SAS tokens are ruled out.
Direct RBAC assignments increase administrative overhead; active PIM assignments grant persistent administrative rights; ad-hoc SAS tokens cannot be revoked individually without rotating storage keys.

Anahtar Kavram

Implementing least privilege and dynamic access control for Azure Storage resources using Stored Access Policies and Privileged Identity Management (PIM).
Soru 283Soru

You are designing an Azure Backup solution for a suite of critical Azure Virtual Machines hosting a high-performance SAP HANA database. The solution must satisfy the following requirements:
- Back up the virtual machines 22 times per day to protect against database transaction losses.
- Retain the local instant recovery snapshots on the virtual machines' managed disks for 1414 days to allow quick operational restores.
- Protect the backup data against regional disasters by replicating it to a secondary paired region, allowing recovery even if the primary region is completely unavailable.

Which of the following configuration options must you include in your backup design? (Select TWO)

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

Cevabı ve açıklamayı göster

Cevap: Configure a Recovery Services Vault with Geo-Redundant Storage (GRS) and enable Cross-Region Restore (CRR).; Create an Enhanced backup policy with a twice-daily backup schedule and set the instant restore retention to 1414 days.

Cevap

To meet the requirements, the design must use a Recovery Services Vault configured with Geo-Redundant Storage (GRS) and Cross-Region Restore (CRR) enabled, combined with an Enhanced backup policy scheduled for twice-daily backups and 1414 days of instant restore retention.
The correct strategy requires configuring a Recovery Services Vault with Geo-Redundant Storage (GRS) and enabling Cross-Region Restore (CRR) to satisfy regional resilience and failover capabilities. Additionally, an Enhanced backup policy must be configured because a Standard policy cannot support the required twice-daily backup schedule or the 1414 days of instant restore snapshot retention.

Adım Adım Çözüm

1
Evaluate the backup frequency and operational recovery requirements.
The requirements dictate twice-daily backups and local snapshot retention of 1414 days.
This determines whether a Standard or Enhanced backup policy is needed based on policy limits.
2
Select the appropriate backup policy type.
Select an Enhanced backup policy.
Standard backup policies support only one backup per day and limit instant recovery retention to between 11 and 55 days, whereas Enhanced policies support multiple daily backups and up to 3030 days of instant recovery retention.
3
Determine the vault storage redundancy and restore features.
Configure a Recovery Services Vault with Geo-Redundant Storage (GRS) and enable Cross-Region Restore (CRR).
GRS ensures replication to the paired region, and CRR allows immediate restore operations in the secondary region if the primary region goes offline.

Anahtar Kavram

Azure VM Backup Policy Tiers and Vault Redundancy Configurations
Soru 284Soru

An organization is designing a backup solution for business-critical Azure Virtual Machines hosting an enterprise database. The solution must meet the following requirements:

* Daily backups must be retained for a minimum of 3030 days.
* Restore operations for any backup up to 1414 days old must be performed as an 'Instant Restore' to meet strict Recovery Time Objective (RTO) targets.
* Backups must remain available even in the event of a regional datacenter disaster.

Which two configurations should you include in the backup design to meet the requirements?

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

Cevabı ve açıklamayı göster

Cevap: Configure an Enhanced backup policy and set the snapshot retention for instant restore to 1414 days.; Create a Recovery Services vault and configure its storage replication to Geo-Redundant Storage (GRS).

Cevap

Configure an Enhanced backup policy with 1414 days of snapshot retention for instant restore, and create a Recovery Services vault configured with Geo-Redundant Storage (GRS).
The correct design requires a Recovery Services vault configured with GRS to ensure regional resilience, and an Enhanced backup policy configured with 1414 days of snapshot retention to support instant restore for that duration, as Standard policies only support up to 55 days.

Adım Adım Çözüm

1
Identify the vault type required for Azure Virtual Machine backups.
Azure VMs must be backed up to a Recovery Services vault, not a Backup vault.
Azure Backup uses Recovery Services vaults for VM backups, whereas Backup vaults are used for operational backups of other resource types.
2
Determine the storage redundancy type needed to protect against regional disasters.
Configure the vault with Geo-Redundant Storage (GRS).
GRS replicates backup data to a secondary paired region, ensuring availability during a regional disaster.
3
Analyze the policy type needed to support a 1414-day instant restore requirement.
Select an Enhanced backup policy and set instant restore retention to 1414 days.
Standard backup policies only support a maximum of 55 days for instant restore snapshot retention, while Enhanced backup policies support up to 3030 days.

Anahtar Kavram

Azure VM backup policy configuration, vault selection, and storage redundancy options.
Tahmini Süre:2m 0s
Soru 285Soru

A company plans to migrate two on-premises SQL Server databases to Azure. The databases have the following requirements:

* Database 1: Supports a legacy human resources application that requires SQL Server Agent, Common Language Runtime (CLR) integration, and cross-database queries.
* Database 2: Supports a lightweight web API that has highly unpredictable traffic patterns, requiring automatic scaling of compute resources and a cost model where compute is billed per second of active usage.

The migration strategy must minimize administrative overhead for managing operating systems and database software updates.

Which two Azure SQL deployment options should you recommend? (Choose two.)

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

Cevabı ve açıklamayı göster

Cevap: Azure SQL Managed Instance for Database 1; Azure SQL Database serverless for Database 2

Cevap

Azure SQL Managed Instance for Database 1 and Azure SQL Database serverless for Database 2
Recommending Azure SQL Managed Instance for the legacy HR database is correct because it supports the required instance-level features (SQL Server Agent, CLR, cross-database queries) while acting as a fully managed PaaS service that automates software updates and patching. Recommending Azure SQL Database serverless for the web API is correct because it dynamically scales compute based on workload demand and offers per-second billing, which aligns with unpredictable traffic patterns and reduces idle costs.

Adım Adım Çözüm

1
Evaluate the database engine feature requirements for Database 1.
Database 1 requires SQL Server Agent, CLR integration, and cross-database queries. These are instance-level SQL features.
Identifying these requirements eliminates Azure SQL Database single database, which does not support these instance-level legacy features.
2
Apply the administrative constraint to the deployment options for Database 1.
Azure SQL Managed Instance is chosen over SQL Server on Azure Virtual Machines.
The scenario requires minimizing administration overhead for operating systems and software updates. Azure VMs (IaaS) require manual OS and SQL patching, while Managed Instance (PaaS) manages updates automatically.
3
Evaluate the workload characteristics and billing requirements for Database 2.
Database 2 requires automatic compute scaling and per-second billing due to unpredictable traffic.
Azure SQL Database serverless provides automatic scaling of compute and charges for CPU and memory used per second, making it the most cost-effective solution.

Anahtar Kavram

Selecting appropriate Azure SQL services based on legacy feature requirements, administrative constraints, and workload behavior.
Soru 286Soru

Aetheris Biotech is designing an identity and access management strategy for its Microsoft Entra ID tenant to comply with new pharmaceutical data protection standards. The cloud architecture team has identified four distinct security requirements for different groups of users and applications. Match each security and compliance requirement on the left to the most appropriate Microsoft Entra ID Conditional Access configuration or feature on the right that achieves the requirement with the least administrative effort.

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

Öğeler

Require external consultants to perform MFA and accept a data-sharing agreement every 30 days when accessing internal research portals.
Enforce MFA for all off-site employee connections, while excluding requests that originate from the corporate headquarters' public IP addresses.
Prevent access to the sensitive drug-formulation database if Entra ID detects abnormal sign-in patterns, such as travel to an unexpected location.
Ensure administrators can only manage Azure resources if they are using a corporate-managed device that is registered and marked as healthy.

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

The correct matches align each security requirement to its respective Microsoft Entra ID Conditional Access control. Specifically: external consultants re-verifying every 30 days maps to sign-in frequency and terms of use; enforcing MFA except for physical office IPs maps to location conditions with named location exclusions; preventing access on abnormal sign-in patterns maps to high sign-in risk condition; and requiring managed healthy devices maps to device compliance grant control.
Each business requirement correlates directly with a built-in Conditional Access capability: periodic re-validation uses Sign-in frequency and Terms of Use; office network bypass uses Named Location exclusions; abnormal behavior blocks use high sign-in risk evaluation; and managed/healthy devices utilize the device compliance grant control.

Adım Adım Çözüm

1
Map the requirement for external consultants re-authenticating and signing an agreement every 30 days.
This requires session duration limits (Sign-in frequency) and legal/policy acceptance (Terms of Use).
Sign-in frequency controls how often a user must sign in again, and Terms of Use ensures compliance agreements are accepted.
2
Map the requirement for enforcing MFA off-site but bypassing it on-site.
This requires location conditions using Named Locations as an exclusion.
Named Locations define trusted IP ranges, and excluding these ranges from the MFA policy allows seamless on-premises access.
3
Map the requirement for blocking access due to abnormal travel and sign-in behavior.
This requires configuring a Sign-in risk level policy targeting High risk.
Microsoft Entra ID Protection calculates real-time sign-in risk (such as atypical travel), which can be evaluated in Conditional Access policies to block access.
4
Map the requirement for administrative device health and management.
This requires device compliance or hybrid joined grant controls.
Requiring a device to be marked as compliant ensures the device meets organization health policies before allowing access.

Anahtar Kavram

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

A multinational e-commerce company uses an Azure General Purpose v2 (GPv2) storage account to store product catalog images. The account is configured with Read-Access Geo-Zone-Redundant Storage (RA-GZRS). The primary region is East US (which supports availability zones) and the secondary paired region is West US (which does not support availability zones for standard GPv2 storage accounts).

The company's application is designed with a connection string that reads from the primary endpoint (catalog.blob.core.windows.net) and automatically falls back to the read-only secondary endpoint (catalog-secondary.blob.core.windows.net) if a primary read request fails.

A major disaster causes a complete outage of the East US region. The operations team initiates a customer-managed failover for the storage account. The last sync time reported prior to the outage was 8 minutes ago.

What is the state of the storage account and the application endpoints after the failover completes?

Cevabı ve açıklamayı göster

Cevap: The storage account redundancy is converted to Locally Redundant Storage (LRS) in West US. The primary endpoint resolves to West US, and the secondary endpoint is no longer accessible.

Cevap

The storage account redundancy is converted to Locally Redundant Storage (LRS) in West US, the primary endpoint resolves to West US, and the secondary endpoint is no longer accessible.
When a customer-managed failover is initiated for an RA-GZRS storage account, the account is converted to a locally redundant tier in the secondary region. Because the target region (West US) does not support Availability Zones for standard storage accounts, the redundancy is converted to Locally Redundant Storage (LRS) rather than Zone-Redundant Storage (ZRS). Additionally, the DNS record for the primary endpoint is updated to resolve to the new primary region (West US), while the secondary endpoint is retired and becomes inaccessible since the account is no longer geo-replicated.

Adım Adım Çözüm

1
Determine the impact of customer-managed failover on storage redundancy configuration.
The storage account loses its geo-redundant capability (GZRS/RA-GZRS) and is converted to a local redundancy tier in the secondary region.
Failover changes the primary location of the storage account to the secondary region, which strips the geo-replication configuration.
2
Evaluate availability zone support in the secondary region (West US) for standard GPv2 storage accounts.
West US does not support availability zones. Therefore, the account cannot be converted to Zone-Redundant Storage (ZRS).
If the secondary region does not support availability zones, a GZRS storage account is converted to LRS instead of ZRS during failover.
3
Analyze endpoint DNS behavior after the failover completes.
The primary endpoint (catalog.blob.core.windows.net) DNS record is updated to point to the West US region. The secondary endpoint (catalog-secondary.blob.core.windows.net) is removed.
The former secondary region becomes the new primary region, and because the account is no longer geo-replicated, the read-only secondary endpoint is disabled.

Anahtar Kavram

Azure Storage customer-managed failover mechanics and regional feature availability constraints.
Soru 288Soru

You are designing a backup solution for Azure Virtual Machines that host a critical business application. The design must meet the following requirements:
- Backups must be recoverable even if the primary Azure region experiences a complete disaster.
- Recent backups from the last 5 days must be available for fast recovery directly from local snapshots without vault latency.
- Backups must be retained for a total of 5 years to meet regulatory compliance.

Which two configurations should you include in the backup design? Select 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); A backup policy with instant restore retention set to 5 days and vault retention set to 5 years

Cevap

To meet the requirements, the design must include a Recovery Services vault configured with Geo-Redundant Storage (GRS) and a backup policy with instant restore retention set to 5 days and vault retention set to 5 years.
The correct configurations involve using a Recovery Services vault with Geo-Redundant Storage (GRS) and setting up a backup policy with a 5-day instant restore retention alongside a 5-year vault retention. GRS replicates data to a secondary region to survive regional disasters. Instant restore keeps snapshots locally for quick recovery, but since it is limited to a maximum of 5 days, the remaining 5 years of retention must be kept in the vault standard tier.

Adım Adım Çözüm

1
Select the appropriate vault storage redundancy to meet the disaster recovery requirement.
Choose Geo-Redundant Storage (GRS) to replicate backups to a secondary region.
Locally Redundant Storage (LRS) only protects against failures within a single datacenter, whereas GRS protects against a complete regional disaster.
2
Determine the retention settings for fast recovery and compliance.
Configure instant restore retention to 5 days, and vault-tier retention to 5 years.
Instant restore keeps snapshots local for fast restore up to 5 days, but long-term compliance retention (5 years) must be offloaded to the vault tier because instant restore cannot exceed 5 days.

Anahtar Kavram

Designing Azure Backup solutions with appropriate vault redundancy and policy retention configuration.
Soru 289Soru

A media production company stores high-value, pre-release film assets in an Azure Blob Storage container named `pre-release-footage`. You must design an access control solution that meets the following requirements:
1. Internal media editors must be allowed to modify the storage account's networking configurations and manage access keys, but only during scheduled maintenance windows. Their elevated access must require justification and automatically expire after 2 hours.
2. An external post-production vendor must be granted read-only access to a specific folder within `pre-release-footage` for exactly 30 days. If the vendor's access credentials are leaked, security administrators must be able to immediately revoke access for this vendor without rotating the storage account access keys or affecting other active tokens.
3. Access privileges must be granted to Microsoft Entra security groups rather than individual user accounts to ensure scalable management.

Which access control and security design should you recommend?

Cevabı ve açıklamayı göster

Cevap: Create an Entra ID security group for the media editors and configure an eligible role assignment in Privileged Identity Management (PIM) for the Storage Account Contributor role with a 2-hour activation limit. For the post-production vendor, configure a Stored Access Policy on the container and generate a Service SAS token associated with that policy.

Cevap

Create a Microsoft Entra ID security group for the media editors and configure an eligible role assignment in Privileged Identity Management (PIM) for the Storage Account Contributor role with a 2-hour activation limit. For the post-production vendor, configure a Stored Access Policy on the container and generate a Service SAS token associated with that policy.
The correct design uses a Microsoft Entra security group with an eligible role assignment in Privileged Identity Management (PIM) to grant just-in-time access that requires activation and expires after 2 hours. For the partner access, configuring a Stored Access Policy on the container and generating a Service SAS token associated with that policy allows administrators to immediately revoke access by deleting or modifying the policy, without rotating storage keys or affecting other tokens.

Adım Adım Çözüm

1
Configure role delegation for internal editors.
Create a security group containing the internal editors and define an eligible role assignment for Storage Account Contributor in Privileged Identity Management (PIM) with a 2-hour activation limit.
This provides just-in-time (JIT) access that requires justification, enforces the 2-hour duration limit, and follows group-based role assignments rather than individual mappings.
2
Configure the token-based access mechanism for the external vendor.
Define a Stored Access Policy on the target container and generate a Service SAS token linked to this policy.
Associating the Service SAS with a Stored Access Policy allows administrators to revoke access immediately by deleting or modifying the policy on the container, avoiding key rotation.
3
Ensure all identity requirements align with best practices.
Verify that no roles are assigned directly to individual users and no ad-hoc SAS tokens are used.
This guarantees compliance with scalability, governance, and auditability requirements.

Anahtar Kavram

Data Storage Security and Access Control
Tahmini Süre:2m 30s
Soru 290Soru

A media production agency is designing a secure storage solution on Azure to allow external freelance animators to upload raw rendering files to a specific Blob storage container named raw-renders. The access must meet the following requirements:

1. The animators must only have access to the raw-renders container for a maximum of 30 days.
2. The security team must be able to instantly revoke access to the container in the event of a credential leak, without rotating the storage account access keys or impacting other applications.
3. Access must be granted with the minimum necessary permissions.

Which of the following access control strategies should you recommend?

Cevabı ve açıklamayı göster

Cevap: Generate a Service Shared Access Signature (SAS) token associated with a Stored Access Policy defined on the raw-renders container.

Cevap

Generate a Service Shared Access Signature (SAS) token associated with a Stored Access Policy defined on the container.
Generating a Service SAS token associated with a Stored Access Policy is correct because Stored Access Policies provide a way to revoke or change the permissions of issued SAS tokens. Since the SAS token is tied to the policy, deleting or modifying the policy immediately invalidates the SAS token without needing to rotate the storage account's master access keys.

Adım Adım Çözüm

1
Analyze the requirements for access delegation, lifetime restriction, and instant revocation without key rotation.
Identified that ad-hoc SAS is insufficient because it cannot be revoked without rotating storage account keys, and direct user RBAC or permanently active PIM configurations violate other access governance rules.
Establishing the security boundary and constraints helps narrow down the acceptable mechanisms for Azure Blob Storage access.
2
Evaluate the capabilities of Stored Access Policies on Azure Blob Storage containers.
Determined that a Stored Access Policy can group constraints (permissions, start/expiry time) and allows instant revocation by modifying or deleting the policy.
A Service SAS inherits constraints from the Stored Access Policy, making the policy a centralized control point for revocation.
3
Select the option that utilizes a Stored Access Policy to bind the SAS token.
Selected the option to generate a Service SAS associated with a Stored Access Policy.
This strategy satisfies the 30-day access window, ensures least privilege, and allows instant revocation without rotating the primary/secondary keys of the storage account.

Anahtar Kavram

Stored Access Policies provide a way to group constraints and manage permissions for container-level Service Shared Access Signatures, allowing easy revocation.
Soru 291Soru

A company plans to deploy a new application that stores user profile photos in an Azure Blob Storage account. The architecture design requires the storage solution to remain available if a single datacenter within the primary region suffers a complete outage. The design does not require replication to a secondary region, and the company wants to minimize storage costs. Which redundancy option should you recommend for the storage account?

Cevabı ve açıklamayı göster

Cevap: Zone-redundant storage (ZRS)

Cevap

Zone-redundant storage (ZRS) is the recommended option because it replicates data synchronously across three availability zones in the primary region, protecting against datacenter outages without the cost of regional replication.
Zone-redundant storage (ZRS) replicates data synchronously across three Azure availability zones in the primary region. This ensures that the data remains available even if a single datacenter (zone) experiences a complete outage, without incurring the higher cost of geo-replication.

Adım Adım Çözüm

1
Identify the availability requirement.
The storage must survive a single datacenter outage within the primary region.
To determine the minimum scope of redundancy needed (zonal vs local).
2
Identify the regional replication constraint.
Replication to a secondary region is not required.
To rule out more expensive geo-redundant options (GRS, GZRS, RA-GRS).
3
Select the option that meets both constraints at the lowest cost.
Zone-redundant storage (ZRS) meets the requirements.
ZRS replicates across availability zones within a single region, surviving datacenter failures with lower cost than geo-redundant storage.

Anahtar Kavram

Selecting the appropriate Azure storage redundancy level (LRS vs. ZRS vs. GRS) based on availability requirements and cost constraints.
Tahmini Süre:1m 0s
Soru 292Soru

An organization is designing a high availability and disaster recovery (HA/DR) solution for a retail application database layer that is migrating to Azure. The database workload depends on SQL Server Agent for scheduled data-aggregation tasks and requires cross-database queries. The solution must meet the following requirements:
- Recover from a regional outage automatically with a Recovery Time Objective (RTO) of less than 1 hour.
- Maintain a single connection string for the application tier that does not require modification during a regional failover.
- Allow read-heavy reporting applications to query the secondary replica in the secondary region to reduce query impact on the primary database.

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

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

Cevabı ve açıklamayı göster

Cevap: Deploy the databases to Azure SQL Managed Instance.; Create a Failover Group between the primary and secondary Azure SQL Managed Instances, and configure the reporting application to use the read-only listener endpoint.

Cevap

Deploy the databases to Azure SQL Managed Instance, and create a Failover Group between the primary and secondary Azure SQL Managed Instances, configuring the reporting application to use the read-only listener endpoint.
The correct design employs Azure SQL Managed Instance because the application relies on SQL Server Agent and cross-database queries, which are not natively supported by Azure SQL Database. To automate failover and prevent client-side configuration changes, a Failover Group must be used. The Failover Group includes a read-write listener that stays active during failover, and a read-only listener that routes reporting traffic to the secondary instance in the disaster recovery region.

Adım Adım Çözüm

1
Analyze the application's database compatibility requirements.
Identify that SQL Server Agent and cross-database queries are required. This rules out Azure SQL Database Single Database and Elastic Pools, pointing to Azure SQL Managed Instance as the correct platform.
Choosing the correct deployment option ensures legacy application features work without rewrite overhead.
2
Evaluate the disaster recovery failover automation and endpoint requirements.
Determine that a Failover Group is required because it supports automatic failover and provides a DNS listener endpoint to avoid application connection string changes.
Active Geo-Replication only supports manual failover and lacks unified listener endpoints for failovers.
3
Address the read-scale offloading requirements for reporting workloads.
Point the reporting application to the read-only listener of the Failover Group to target the secondary replica in the failover region.
Using the read-only listener endpoint guarantees that reporting queries are routed to the secondary replica, reducing the workload on the primary instance.

Anahtar Kavram

Designing relational database high availability and disaster recovery in Azure requires aligning database engine compatibility with replication capabilities such as Failover Groups.
Soru 293Soru

A medical research facility is deploying a genomic data analysis application on Azure. The application utilizes a combination of virtual machine-based analytics engines and a shared storage platform. The storage infrastructure must satisfy the following constraints:

* The analytics database requires high-performance write operations for transient scratch space, needing sub-millisecond latencies.
* A shared file storage system must support POSIX-compliant file access over NFS for multiple Linux-based compute nodes, with high throughput and resiliency against local datacenter zone outages.
* Temporary datasets must be shared with external research teams via pre-signed URLs. The facility must be able to invalidate these URLs immediately if a security anomaly is detected, without affecting other shared datasets.

Which TWO of the following configurations should you recommend in the storage architecture design? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Provision Ultra Disk storage for the database transient scratch space.; Deploy a Premium tier Azure Files share configured with NFS and Zone-Redundant Storage (ZRS).

Cevap

Provision Ultra Disk storage for the database transient scratch space and deploy a Premium tier Azure Files share configured with NFS and Zone-Redundant Storage (ZRS).
The correct configurations are to provision Ultra Disk storage for the database scratch space and to deploy a Premium tier Azure Files share with NFS and ZRS. Ultra Disk is the only selected storage option that guarantees the required sub-millisecond write latencies. Premium tier Azure Files supports NFS v4.1 and can be deployed with ZRS, satisfying the requirements for POSIX compliance, NFS access, and zone outage resiliency. Stored access policies must be utilized to manage SAS tokens to support instant revocation.

Adım Adım Çözüm

1
Analyze the database scratch space requirements.
Identify that sub-millisecond latency is required, which narrows the disk storage selection to Ultra Disk or Premium SSD v2.
Standard SSD and Standard HDD disks cannot meet the strict sub-millisecond latency demands of high-performance database workloads.
2
Analyze the shared file storage requirements.
Identify that POSIX-compliant NFS file access with zone resiliency is required, directing the selection to Premium tier Azure Files with Zone-Redundant Storage (ZRS).
Standard tier Azure Files does not support NFS. Premium tier Azure Files supports NFS and can be provisioned with ZRS to sustain a zone failure.
3
Analyze the blob sharing and revocation requirements.
Determine that SAS tokens must be managed using stored access policies to allow immediate, individual revocation without key rotation.
Ad-hoc SAS tokens generated directly from the storage account key cannot be revoked individually without rotating the entire storage account key.

Anahtar Kavram

Selecting appropriate Azure storage service tiers, disk types, redundancy configurations, and security access policies to meet strict latency, protocol, availability, and revocation requirements.
Soru 294Soru

You are designing a globally distributed package delivery tracking application. The solution has the following requirements:
- Save package telemetry (JSON documents) in an Azure Cosmos DB for NoSQL database. The data must be partitioned to prevent hot partitions and scale horizontally. Telemetry contains PackageIdPackageId (GUID), LogisticsHubIdLogisticsHubId (10 unique values), and DestinationCountryDestinationCountry (190 unique values).
- Replicate the database to three regions (East US, West Europe, and East Asia) with multi-region writes enabled to ensure sub-10 ms10\text{ ms} read/write latency.
- Store high-resolution photos of delivered packages (up to 5 MB5\text{ MB} each) in an Azure Blob Storage account. The photo storage must survive regional outages and allow read access from a secondary region if the primary region fails.

Which two configurations should you include in the design?

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

Cevabı ve açıklamayı göster

Cevap: Partition the Azure Cosmos DB container using PackageId.; Configure the Azure Blob Storage account to use Read-Access Geo-Redundant Storage (RA-GRS).

Cevap

The correct design configurations are partitioning the Azure Cosmos DB container using PackageId and configuring the Azure Blob Storage account to use Read-Access Geo-Redundant Storage (RA-GRS).
Partitioning by PackageId ensures that Cosmos DB workloads are distributed evenly across physical partitions because PackageId has high cardinality. Selecting Read-Access Geo-Redundant Storage (RA-GRS) for the Blob Storage account ensures that files are replicated across regions and remain readable even if the primary region goes offline.

Adım Adım Çözüm

1
Analyze the Cosmos DB partitioning requirements.
Determine that PackageId (GUID) has high cardinality, whereas LogisticsHubId (10 values) has extremely low cardinality.
Using a high-cardinality partition key distributes requests evenly and prevents hot partitions.
2
Analyze the Blob Storage replication and availability requirements.
Determine that the storage account must survive a regional outage and allow read access from a secondary region.
Read-Access Geo-Redundant Storage (RA-GRS) provides geo-redundancy and exposes a read-only endpoint in the secondary region.

Anahtar Kavram

Azure Cosmos DB partition key selection for scalability and Azure Storage redundancy configuration for regional disaster recovery.
Soru 295Soru

You are designing a backup solution for a production SAP HANA database running on an Azure virtual machine. The solution must satisfy the following requirements:
- Retain weekly full backups for 365 days.
- Ensure backup data is resilient to a primary region outage.
- Enable database restoration to a secondary paired region with minimal delay in the event of a primary region disaster.

Which backup configuration should you recommend?

Cevabı ve açıklamayı göster

Cevap: A Recovery Services vault configured with Geo-Redundant Storage (GRS) and Cross-Region Restore (CRR) enabled.

Cevap

A Recovery Services vault configured with Geo-Redundant Storage (GRS) and Cross-Region Restore (CRR) enabled.
The correct configuration leverages a Recovery Services vault, which is the required vault type for SAP HANA on Azure VMs. Using Geo-Redundant Storage (GRS) with Cross-Region Restore (CRR) enabled ensures the backups are replicated to the secondary paired region and can be restored there even if the primary region experiences a complete outage.

Adım Adım Çözüm

1
Determine the required vault type for the workload.
SAP HANA databases running on Azure VMs must be backed up using a Recovery Services vault rather than a Backup vault.
Azure Backup categorizes workloads; databases on virtual machines are supported under Recovery Services vaults.
2
Select the appropriate storage redundancy and recovery configuration to survive a regional outage.
Configure the vault storage with Geo-Redundant Storage (GRS) and enable Cross-Region Restore (CRR).
GRS replicates data to a paired region, and CRR allows you to restore backup data in the secondary region even when the primary region is healthy or degraded.
3
Configure the backup retention policy parameters.
Set the vault-tier retention to 365 days and ensure the local instant restore snapshot retention is kept within the default limit (1-5 days).
Long-term retention must be configured on the vault tier, as instant restore snapshots cannot exceed the maximum supported limits (up to 30 days for enhanced policies).

Anahtar Kavram

Selecting the correct vault type and replication architecture to support disaster recovery for database workloads on Azure VMs.
Tahmini Süre:1m 30s
Soru 296Soru

You are designing a disaster recovery solution for an application that uses an Azure SQL Database. The solution must support automatic failover to a secondary Azure region in the event of a primary region outage. The application must be able to reconnect to the database after failover without any changes to its connection string. Which solution should you recommend?

Cevabı ve açıklamayı göster

Cevap: Azure SQL Database Failover Groups

Cevap

Azure SQL Database Failover Groups
The correct option is Azure SQL Database Failover Groups because they enable automatic failover of a group of databases to a secondary region and provide a listener endpoint. This allows the application to connect using the same connection string regardless of which region is hosting the primary database.

Adım Adım Çözüm

1
Analyze the automatic failover requirement.
The database must support automatic failover to a secondary region during a regional outage.
This rules out solutions requiring manual failover or those limited to a single region.
2
Analyze the connection string requirement.
The application must connect using a single, unchanging connection string.
This requires a listener endpoint that redirects traffic automatically, which is a feature of failover groups.

Anahtar Kavram

Azure SQL Database Failover Groups provide a read-write listener endpoint that remains constant, automatically routing application traffic to the active primary database in the event of a failover to the secondary region.
Tahmini Süre:1m 0s
Soru 297Soru

A healthcare provider requires a business continuity strategy for an electronic health record (EHR) database migrating to Azure. The database workload has the following requirements:

* It must support legacy cross-database queries and execute SQL Server Agent jobs for nightly aggregation tasks.
* It must survive a regional outage with a Recovery Time Objective (RTO) of 11 hour and a Recovery Point Objective (RPO) of 55 seconds.
* Failover to the secondary region (West US) must occur automatically, using a single connection endpoint that redirects write traffic without requiring application configuration updates.
* Read-only analytical queries must be offloaded to the secondary region.

You plan to implement Azure SQL Managed Instances in East US (primary) and West US (secondary).

Which of the following configuration actions must you perform to satisfy these requirements? (Select 22.)

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

Cevabı ve açıklamayı göster

Cevap: Establish virtual network peering or a VPN connection between the virtual networks of the primary and secondary instances, and configure a failover group.; Manually recreate and synchronize the required SQL Server Agent jobs on the secondary instance.

Cevap

To meet the requirements, you must establish network connectivity (VNet peering or VPN) between the virtual networks of the primary and secondary instances to configure a failover group, and manually recreate and synchronize the SQL Server Agent jobs on the secondary instance.
Establishing virtual network connectivity via peering or VPN is a mandatory prerequisite for setting up a failover group between two Azure SQL Managed Instances. The failover group provides automatic failover and a read-write listener that redirects traffic without connection string changes. Because system databases (including msdb) are not replicated by the failover group, SQL Server Agent jobs must be manually recreated on the secondary instance to ensure they run after a failover.

Adım Adım Çözüm

1
Determine the relational database deployment tier based on legacy requirements.
Select Azure SQL Managed Instance.
The database requires cross-database queries and SQL Server Agent jobs, which are supported in Managed Instance but not in standard Azure SQL Database offerings.
2
Design the network connectivity required for database replication.
Plan virtual network peering or a VPN connection between the virtual networks in East US and West US.
Failover groups for Azure SQL Managed Instance require bidirectional network communication between the instances.
3
Design the cross-region database failover mechanism.
Configure a failover group containing the user databases.
Failover groups provide automatic failover, meet the RTO/RPO limits, and expose a single read-write listener endpoint to abstract connection changes.
4
Design the synchronization plan for scheduled operations.
Deploy identical SQL Server Agent jobs on the secondary instance.
System databases like msdb are not replicated by the failover group, meaning agent jobs must be manually maintained on the secondary server to run after failover.

Anahtar Kavram

Azure SQL Managed Instance HA/DR design using failover groups, virtual network requirements, and handling non-replicated system metadata like SQL Server Agent jobs.
Soru 298Soru

A company is planning a new deployment of a relational database for a corporate application. The database solution must satisfy the following requirements:
* Support the execution of SQL Server Agent jobs and native cross-database queries.
* Provide a fully managed platform to minimize administrative overhead for operating system and database patching.
* Guarantee that in the event of a regional outage, database failover to a secondary region is automated with a single connection endpoint.

Which database solution and configuration should the company select?

Cevabı ve açıklamayı göster

Cevap: Azure SQL Database Managed Instance configured with an auto-failover group

Cevap

Azure SQL Database Managed Instance configured with an auto-failover group
The correct solution uses Azure SQL Database Managed Instance configured with an auto-failover group. Managed Instance is a fully managed service that supports SQL Server Agent and cross-database queries. Auto-failover groups enable automatic failover to a secondary region and provide a single read-write listener endpoint.

Adım Adım Çözüm

1
Analyze database feature requirements
Azure SQL Database Managed Instance and SQL Server on Azure VMs support SQL Server Agent and cross-database queries, while Azure SQL Database single database does not.
To narrow down candidate services based on features.
2
Analyze administrative overhead requirements
Azure SQL Database Managed Instance is a fully managed PaaS solution, whereas SQL Server on Azure VMs is IaaS and requires manual patching.
To satisfy the requirement of minimizing administrative patching overhead.
3
Analyze high availability and disaster recovery requirements
Auto-failover groups provide automatic failover and a single listener endpoint, whereas active geo-replication requires manual failover.
To satisfy the requirement of automatic failover with a single connection endpoint.

Anahtar Kavram

Relational database service selection and high availability design in Azure
Soru 299Soru

You are designing a backup solution for a fleet of critical Azure Virtual Machines hosting an enterprise resource planning (ERP) application. The solution must meet the following requirements:
- Restore requests for data deleted within the last 1414 days must be completed in under 1010 minutes using local snapshots.
- The backup schedule must achieve a Recovery Point Objective (RPO) of 1212 hours.
- In the event of a complete primary region outage, administrators must be able to immediately initiate restores of the virtual machines in the secondary paired region.
- The storage redundancy configuration must survive a primary region disaster.

Which vault configuration and backup policy design should you recommend to meet these requirements?

Cevabı ve açıklamayı göster

Cevap: A Recovery Services vault with Geo-Redundant Storage (GRS) and Cross Region Restore (CRR) enabled, using an Enhanced backup policy configured for a twice-daily schedule and 1414 days of instant restore retention.

Cevap

The correct configuration is a Recovery Services vault with Geo-Redundant Storage (GRS) and Cross Region Restore (CRR) enabled, using an Enhanced backup policy configured for a twice-daily schedule and 1414 days of instant restore retention.
The correct configuration uses a Recovery Services vault with GRS and CRR enabled, along with an Enhanced backup policy. The Enhanced backup policy is necessary to support multiple backups per day (achieving the 1212-hour RPO) and to extend the instant restore snapshot retention beyond the Standard policy's 55-day limit to the required 1414 days. Enacting GRS with CRR ensures that recovery points are immediately accessible for restore operations in the secondary paired region during a primary region failure.

Adım Adım Çözüm

1
Determine the backup policy type based on the RPO and snapshot retention requirements.
An Enhanced backup policy is required.
The Standard policy only supports daily backups and a maximum of 55 days of snapshot-level (instant restore) retention. The requirements specify a 1212-hour RPO (requiring multiple backups per day) and a 1414-day instant restore window.
2
Determine the vault storage redundancy type based on disaster recovery requirements.
Geo-Redundant Storage (GRS) is required.
Locally Redundant Storage (LRS) does not protect against a regional disaster, as it stores data within a single region.
3
Evaluate the secondary region access requirements.
Cross Region Restore (CRR) must be enabled on the GRS vault.
Standard GRS without CRR only allows restores in the secondary region after Microsoft initiates a failover. CRR allows administrators to immediately perform restores in the secondary region at any time.

Anahtar Kavram

Azure VM Backup Policies (Standard vs. Enhanced) and Vault Redundancy (GRS with CRR)
Soru 300Soru

CloudFin Associates is designing a hybrid identity and access management solution for their Microsoft Entra ID tenant. The organization requires that:

1. Users must sign in to cloud services using their on-premises Active Directory Domain Services (AD DS) passwords.
2. In the event of an on-premises datacenter outage, users must still be able to authenticate to cloud services without administrative intervention.
3. Administrative overhead and infrastructure complexity must be minimized.
4. Multi-factor authentication (MFA) must be enforced for all administrative roles, while ensuring that the organization does not get locked out of the tenant in an emergency.

Which of the following authentication and access control designs should you recommend?

Cevabı ve açıklamayı göster

Cevap: Implement Password Hash Synchronization (PHS) as the hybrid identity solution, deploy a Conditional Access policy enforcing multi-factor authentication for all administrators, and exclude a dedicated emergency access account from the policy.

Cevap

Implement Password Hash Synchronization (PHS) as the hybrid identity solution, deploy a Conditional Access policy enforcing multi-factor authentication for all administrators, and exclude a dedicated emergency access account from the policy.
The correct design uses Password Hash Synchronization (PHS) combined with a Conditional Access policy that enforces MFA for administrative roles while excluding a dedicated emergency access account. PHS requires the least on-premises infrastructure and ensures users can sign in using their synchronized passwords even if the on-premises servers go offline. Excluding the emergency access account ensures recovery capability in the event of an MFA failure.

Adım Adım Çözüm

1
Evaluate the hybrid authentication methods based on availability and overhead requirements.
Password Hash Synchronization (PHS) is selected over Active Directory Federation Services (AD FS) because it has the lowest infrastructure complexity, requires no on-premises servers to perform cloud login validation, and continues to function if the on-premises datacenter goes offline.
This satisfies the requirements for minimizing administrative overhead and ensuring business continuity during an on-premises outage.
2
Determine the access security strategy for administrator accounts.
A Conditional Access policy is designed to enforce multi-factor authentication (MFA) for all administrative roles.
This satisfies the security requirement to enforce MFA for administrative access.
3
Ensure emergency access capability to prevent lockout.
Exclude a dedicated emergency access (break-glass) account from the administrator MFA policy.
This aligns with Microsoft best practices to prevent tenant lockout in case of MFA provider service disruptions.

Anahtar Kavram

Microsoft Entra ID hybrid authentication and Conditional Access design
Tahmini Süre:1m 30s
ÖncekiSayfa 15 / 60Sonraki