Tüm alıştırma soruları

1198 soru

Soru 321Soru

An enterprise is designing a modern data platform on Azure to process and analyze telemetry data. The design must meet the following requirements:
- Data analysts must perform ad-hoc, exploratory queries directly against raw CSV and JSON files stored in the data lake, paying only for the queries run.
- The data storage solution must remain resilient and available even in the event of a primary datacenter outage within the region.
- Shared Access Signatures (SAS) provided to external partners must be easily revocable at any time without rotating the storage account access keys.

Which of the following architectural recommendations should you include in the design? (Select TWO).

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

Cevabı ve açıklamayı göster

Cevap: Provision Azure Synapse Analytics serverless SQL pools to query the raw CSV and JSON files directly in the data lake.; Configure the Azure Data Lake Storage Gen2 account to use Geo-Redundant Storage (GRS) and associate all Shared Access Signatures with stored access policies.

Cevap

Use Azure Synapse Analytics serverless SQL pools for ad-hoc queries, and configure Azure Data Lake Storage Gen2 with Geo-Redundant Storage (GRS) and stored access policies for SAS delegation.
The correct recommendations are to use serverless SQL pools for querying the data lake directly on an ad-hoc basis, and to use Geo-Redundant Storage (GRS) with stored access policies. Serverless SQL pools charge based on data processed, avoiding idle compute costs. GRS provides regional disaster resilience, and stored access policies allow SAS tokens to be revoked easily without changing the root keys.

Adım Adım Çözüm

1
Evaluate the ad-hoc query requirements against Azure Synapse options.
Identify that serverless SQL pools are ideal for ad-hoc queries on raw files because they run on-demand and charge only per query, whereas dedicated SQL pools incur persistent costs.
To satisfy the requirement of minimal overhead and pay-per-query model for ad-hoc exploration.
2
Evaluate redundancy options for regional disaster resilience.
Determine that Geo-Redundant Storage (GRS) replicates data across regions to protect against regional outages, whereas Locally Redundant Storage (LRS) only replicates within a single datacenter.
To satisfy the requirement of surviving a primary datacenter outage.
3
Evaluate security requirements for SAS token revocation.
Identify that associating SAS tokens with a stored access policy allows instant revocation by deleting or modifying the policy, avoiding the need to rotate primary/secondary keys.
To satisfy the requirement of revoking access keys without rotating the storage account access keys.

Anahtar Kavram

Designing data integration and analytical storage requires matching query models (serverless vs. dedicated) to usage patterns, and configuring storage redundancy and access control policies to meet resilience and security requirements.
Soru 322Soru

A logistics company is designing a multi-region architecture for storing shipment images using Azure Block Blobs. To ensure high availability, the application must be able to write new images to the storage endpoints in both the primary and secondary Azure regions simultaneously. A junior architect suggests configuring the storage account with Read-Access Geo-Redundant Storage (RA-GRS). Why is this suggestion invalid?

Cevabı ve açıklamayı göster

Cevap: Read-Access Geo-Redundant Storage (RA-GRS) only allows read-only access to the secondary region, and write operations can only be performed on the primary region.

Cevap

Read-Access Geo-Redundant Storage (RA-GRS) only allows read-only access to the secondary region, and write operations can only be performed on the primary region.
The correct answer is correct because RA-GRS provides read-only access to the secondary endpoint. It does not support active-active multi-region write operations. All write operations must be sent to the primary endpoint.

Adım Adım Çözüm

1
Analyze the technical requirement for the storage solution.
The application must write data directly and simultaneously to storage accounts in both the primary and secondary regions (active-active configuration).
This establishes the requirement for write capabilities on the secondary region.
2
Evaluate the capabilities of Read-Access Geo-Redundant Storage (RA-GRS).
RA-GRS replicates data to a secondary region, providing a secondary endpoint, but that endpoint is read-only.
This determines whether RA-GRS meets the write requirement.
3
Select the correct explanation for why the proposal is invalid.
The suggestion is invalid because the secondary region's endpoint in RA-GRS is read-only, preventing the required active-active writes.
This identifies the limitation that invalidates the architect's proposal.

Anahtar Kavram

Read-Access Geo-Redundant Storage (RA-GRS) provides read-only access to the secondary region's endpoint; it does not support active-active write access across regions.
Tahmini Süre:1m 0s
Soru 323Soru

You are designing a disaster recovery solution for a web application database in Azure. The database is currently deployed as an Azure SQL Database. The disaster recovery design must support automatic failover to a secondary region and allow the application to connect using a single read-write connection string that remains unchanged after a failover event. Which two actions should you include in the design? (Select two.)

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

Cevabı ve açıklamayı göster

Cevap: Create a failover group that includes the primary database and a secondary database in a paired region.; Configure the application to connect to the database using the read-write listener endpoint of the failover group.

Cevap

Create a failover group that includes the primary database and a secondary database in a paired region, and configure the application to connect to the database using the read-write listener endpoint of the failover group.
To support automatic failover and maintain a single connection string, the architecture must utilize a failover group. The failover group replicates databases to a secondary region and exposes a read-write listener endpoint. The application connects to this listener, which automatically routes traffic to the active primary region without requiring client updates during a failover.

Adım Adım Çözüm

1
Analyze the business continuity requirements for the Azure SQL Database workload.
Identify that the solution must provide automatic cross-region failover and use an unchanging connection string.
This establishes that manual failover models like standalone active geo-replication will not satisfy the connection string constancy requirement.
2
Design the replication and failover architecture.
Select Azure SQL Database failover groups to group the primary and secondary databases across regions.
Failover groups automate the regional failover process and provide a single read-write listener endpoint.
3
Configure client connectivity to use the listener endpoint.
Point the application's connection string to the failover group's read-write listener.
This ensures client connections are transparently redirected to the new primary server during a failover event.

Anahtar Kavram

Azure SQL Database failover groups manage replication, automatic failover, and client connection routing across regions via listener endpoints.
Soru 324Soru

You are designing the storage architecture for an enterprise modernization project. You need to match the application workloads and migration requirements to the most appropriate Azure Cosmos DB API. To answer, match each workload scenario on the left with its corresponding Azure Cosmos DB API on the right.

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

Öğeler

A modernized e-commerce shopping cart service requiring JSON document storage, SQL-like querying over hierarchical data, and enterprise-grade multi-region writes.
A real-time fraud detection engine that models and queries highly connected multi-hop relationships and dependency networks among entities.
A migration of a legacy wide-column telemetry database that executes Cassandra Query Language (CQL) queries, requiring minimal codebase changes.
A customer profile database migration from an on-premises database that uses native BSON serialization and requires compatibility with existing MongoDB driver libraries.

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

Match the e-commerce shopping cart to API for NoSQL, the fraud detection engine to API for Gremlin, the wide-column telemetry database to API for Cassandra, and the customer profile database to API for MongoDB.
The correct matches align the workload patterns and migration specifications to their respective Azure Cosmos DB API wire protocols: native SQL queries on JSON documents map to API for NoSQL; graph and relationship traversals map to API for Gremlin; wide-column CQL workloads map to API for Cassandra; and BSON-based document workloads map to API for MongoDB.

Adım Adım Çözüm

1
Analyze the shopping cart requirement
Requires JSON document storage and SQL-like querying. This maps directly to the native Azure Cosmos DB API for NoSQL.
API for NoSQL is designed for native SQL-like queries over JSON documents.
2
Analyze the fraud detection requirement
Requires modeling multi-hop relationships and dependency networks. This maps to graph database structures supported by the API for Gremlin.
Gremlin is the graph-traversal standard supported by Cosmos DB.
3
Analyze the legacy wide-column telemetry requirement
Requires CQL query execution and wide-column compatibility. This maps to the API for Cassandra.
API for Cassandra provides CQL wire protocol compatibility.
4
Analyze the customer profile migration requirement
Requires BSON serialization and compatibility with existing MongoDB drivers. This maps to the API for MongoDB.
API for MongoDB implements the MongoDB wire protocol.

Anahtar Kavram

Azure Cosmos DB API selection based on workload characteristics and migration requirements.
Tahmini Süre:2m 0s
Soru 325Soru

Meridian Retail is designing an identity security strategy for its Microsoft Entra ID tenant. You are configuring a Conditional Access policy that enforces multi-factor authentication (MFA) for all directory administrators. The design must prevent administrative lockout in the event of an Azure MFA service outage or policy misconfiguration. Which strategy should you include in the design?

Cevabı ve açıklamayı göster

Cevap: Exclude a dedicated, cloud-only emergency access account from the Conditional Access policy.

Cevap

Exclude a dedicated, cloud-only emergency access account from the Conditional Access policy.
Excluding a dedicated, cloud-only emergency access account from the Conditional Access policy is a Microsoft best practice. In the event of an MFA service outage or policy misconfiguration, this excluded account can be used to log in and modify or disable the problematic policy.

Adım Adım Çözüm

1
Analyze the lockout risk requirement.
Identify that a tenant-wide Conditional Access policy enforcing MFA could lock out all administrators if a misconfiguration occurs or the MFA service experiences an outage.
To design a resilient authentication system, you must plan for contingency access.
2
Select the correct mitigation strategy.
Exclude a dedicated, highly secure, cloud-only administrative account (emergency or break-glass account) from the policy.
Excluding an account allows it to bypass the policy and serve as a recovery mechanism in emergencies.
3
Evaluate and discard incorrect alternatives.
Confirm that omitting exclusions, using permanently active PIM assignments, or introducing complex AD FS federation do not safely resolve the lockout concern and violate best practices.
This ensures the final solution adheres to Microsoft's identity design guidelines.

Anahtar Kavram

Microsoft Entra ID emergency access accounts and Conditional Access policy exclusions
Soru 326Soru

A retail company stores point-of-sale (POS) transaction audit logs in an Azure Blob Storage container named pos-audit-logs. A third-party auditing firm requires temporary read access to this container. You must design an access control solution that meets the following security requirements:

- Access must be limited to a specific 30-day auditing window.
- The security team must be able to revoke the access immediately in the event of a credential compromise, without affecting other integrations that rely on the storage account keys.
- The external auditors must be granted only the minimum required permissions.

Which access control strategy should you recommend?

Cevabı ve açıklamayı göster

Cevap: Create a Stored Access Policy on the container and generate a Shared Access Signature (SAS) token associated with that policy.

Cevap

Create a Stored Access Policy on the container and generate a Shared Access Signature (SAS) token associated with that policy.
The correct solution is to use a Stored Access Policy on the container and issue a SAS token linked to that policy. A Stored Access Policy provides a management layer on the storage container. By changing the policy parameters or deleting the policy itself, the associated SAS token is immediately invalidated, providing a reliable revocation mechanism. This satisfies the requirement to terminate access in the event of a compromise without rotating the storage account keys, which would affect other integrations.

Adım Adım Çözüm

1
Analyze the requirement for temporary access revocation without key rotation.
Identified that ad-hoc Shared Access Signatures (SAS) require key rotation for revocation, which would disrupt other integrations. A Stored Access Policy must be used to enable individual SAS token revocation.
Stored Access Policies allow changing parameters or deleting the policy, which instantly invalidates all associated SAS tokens without modifying storage account keys.
2
Determine the appropriate security principal and assignment methodology.
Ruled out direct RBAC assignments to individual users and permanent PIM role assignments.
Direct assignments to individuals violate group governance best practices, and permanent PIM assignments violate just-in-time access principles.
3
Synthesize the requirements into a unified access control recommendation.
Recommended a container-level Stored Access Policy combined with an associated SAS token.
This strategy satisfies the 30-day time window, guarantees immediate revocation capability, and adheres to the principle of least privilege.

Anahtar Kavram

Stored Access Policies provide a way to group shared access signatures and provide additional constraints, including the ability to revoke them immediately without rotating storage account keys.
Soru 327Soru

You are designing a disaster recovery solution for an Azure virtual machine (VM) that runs a database workload. The VM has a single Premium SSD data disk with a constant write churn rate of 25 MB/s25\text{ MB/s}. The solution must replicate the VM to a secondary Azure region and support a Recovery Point Objective (RPO) of 15 minutes. Which replication option should you select to meet these requirements?

Cevabı ve açıklamayı göster

Cevap: Azure Site Recovery with high-churn replication enabled

Cevap

Azure Site Recovery with high-churn replication enabled
The correct option is Azure Site Recovery with high-churn replication enabled. Standard Azure Site Recovery replication has a write churn limit of 20 MB/s20\text{ MB/s} per Premium SSD disk. To support a disk with a churn rate of 25 MB/s25\text{ MB/s} and maintain a low RPO, high-churn replication must be enabled, which increases the supported limit up to 100 MB/s100\text{ MB/s} per disk.

Adım Adım Çözüm

1
Evaluate the workload limits against replication capabilities.
The workload has a write churn rate of 25 MB/s25\text{ MB/s} on a single Premium SSD.
Determining write churn is necessary because Azure Site Recovery enforces limits per disk based on the replication policy.
2
Compare replication tiers in Azure Site Recovery.
Standard replication supports up to 20 MB/s20\text{ MB/s} per Premium SSD disk, whereas high-churn replication supports up to 100 MB/s100\text{ MB/s} per disk.
Identifying the limits ensures the selected replication method can sustain the write volume without lagging.
3
Select the option that meets the RPO and replication constraints.
Azure Site Recovery with high-churn replication enabled is selected.
This configuration safely handles the 25 MB/s25\text{ MB/s} write churn and supports the low RPO requirement.

Anahtar Kavram

Azure Site Recovery Write Churn Limits
Tahmini Süre:1m 0s
Soru 328Soru

An organization is designing a relational database solution in Azure to support a new large-scale analytics platform. The solution must meet the following requirements:
- Support a database size that is projected to grow to 35 TB35\text{ TB}.
- Ensure database backups are completed in under 15 minutes15\text{ minutes} regardless of the database volume size.
- Minimize database administrative and management overhead by using a fully managed Platform as a Service (PaaS) solution.
- Support up to 44 read-only replicas to offload reporting workloads.

Which Azure SQL database deployment option should you recommend?

Cevabı ve açıklamayı göster

Cevap: Azure SQL Database Hyperscale

Cevap

Azure SQL Database Hyperscale
Azure SQL Database Hyperscale is the only fully managed PaaS solution that supports database sizes up to 100 TB100\text{ TB}, allows instantaneous backups via file-snapshot technology regardless of database size, and supports up to 44 read-only replicas to offload read workloads.

Adım Adım Çözüm

1
Analyze storage capacity and scaling requirements.
The database size is projected to reach 35 TB35\text{ TB}, which exceeds the standard capacity limits of Azure SQL Database General Purpose (4 TB4\text{ TB}) and Azure SQL Managed Instance (16 TB16\text{ TB}).
This rules out General Purpose databases and standard Managed Instance options.
2
Analyze operational performance and backup constraints.
The requirement states that backups must complete in under 15 minutes15\text{ minutes} regardless of size. Traditional backup methods depend on size, but Azure SQL Database Hyperscale uses storage snapshots to perform instantaneous backups.
This confirms that Hyperscale satisfies the backup timing constraint for large database sizes.
3
Evaluate the management model constraint.
A PaaS solution is required to minimize management overhead. While SQL Server on Azure Virtual Machines can support 35 TB35\text{ TB} databases, it is an IaaS solution that requires significant administrative effort for OS and database management.
This rules out SQL Server on Azure Virtual Machines and leaves Azure SQL Database Hyperscale as the only option that satisfies all storage, management, replication, and backup requirements.

Anahtar Kavram

Azure SQL Database service tiers and scaling limits
Tahmini Süre:2m 0s
Soru 329Soru

An enterprise is designing a secure storage solution on Azure to hold sensitive transaction logs in a Blob Storage container. The logs contain highly confidential financial records. You need to design the access control strategy to meet the following security requirements:

- A team of external auditors must be granted temporary read access to the logs for a maximum duration of 4 hours per session, and this access must be immediately revocable in the event of a suspected security breach.
- A team of internal storage administrators requires privileged access to manage the storage container, but their permissions must not be permanently active and must require activation through Microsoft Entra Privileged Identity Management (PIM).
- Permissions must be managed at scale, avoiding direct assignment of role privileges to individual user identities.

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

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

Cevabı ve açıklamayı göster

Cevap: Configure a stored access policy on the blob container, and generate Shared Access Signature (SAS) tokens associated with this policy for the external auditors.; Create a Microsoft Entra ID security group, assign the Storage Blob Data Reader role to the group, and configure Privileged Identity Management (PIM) for Groups to make the storage administrators eligible for the group.

Cevap

Configure a stored access policy on the blob container for the external auditors' SAS tokens, and create a Microsoft Entra ID security group with PIM for Groups eligibility for the storage administrators.
Using a stored access policy enables immediate revocation of the associated SAS tokens by modifying the policy, meeting the requirements of the external auditors. PIM for Groups allows storage administrators to activate their access just-in-time, and utilizing a security group avoids direct RBAC assignments to individual users.

Adım Adım Çözüm

1
Evaluate the requirement for temporary, revocable access for external auditors.
Determine that ad-hoc SAS tokens do not support granular, immediate revocation without key rotation, which affects all users. A stored access policy provides the required control.
Stored access policies allow immediate revocation of associated SAS tokens by altering or deleting the policy.
2
Evaluate the requirement for privileged access for internal administrators.
Determine that administrators must not have permanently active roles and must use PIM.
Microsoft Entra PIM allows roles to be configured as eligible rather than permanently active, providing just-in-time access.
3
Evaluate the scalability requirement for administrative access.
Determine that direct role assignments to individual users must be avoided in favor of group-based management.
Assigning RBAC roles to security groups rather than individual users aligns with the principle of least privilege and simplifies governance.

Anahtar Kavram

Azure storage security requires combining network controls, identity-based RBAC, and granular token lifecycles. For JIT administrative access, PIM for Groups is standard practice, while stored access policies are essential for revocable SAS token management.
Tahmini Süre:2m 0s
Soru 330Soru

A retail company is planning the high availability and disaster recovery strategy for its new customer feedback system. The system's relational database will be hosted on Azure SQL Database. The operations team has specified that if the primary region experiences an outage, database failover to the secondary region must happen automatically. Additionally, the application must connect using a read-write listener that automatically routes traffic to the active primary region without updating connection strings. Which feature should be implemented to satisfy these requirements?

Cevabı ve açıklamayı göster

Cevap: Auto-failover groups

Cevap

Auto-failover groups
The correct option is Auto-failover groups. This feature provides a group of databases managed collectively that can failover automatically to another Azure region. It also provides read-write and read-only listener endpoints that remain unchanged during failover, allowing the application to connect seamlessly.

Adım Adım Çözüm

1
Analyze the requirements for high availability and disaster recovery.
The solution requires automatic database failover to a secondary region and a single connection endpoint that remains constant during failover.
This eliminates options that require manual intervention or manual redirection of the application connection string.
2
Evaluate the capabilities of Azure SQL Database features.
Auto-failover groups offer both automatic failover capabilities and read-write/read-only listener endpoints that route traffic to the active database server.
Active geo-replication is designed for manual failover and does not support listener endpoints directly.

Anahtar Kavram

Azure SQL Database Auto-failover groups provide automated cross-region database recovery and listener endpoints.
Soru 331Soru

An organization stores application log files in an Azure Blob Storage container. The logs are frequently accessed for the first 30 days. After 30 days, the logs are rarely accessed but must be available for immediate, sub-second retrieval to support troubleshooting. The logs must be retained for a total of 365 days and then removed to minimize storage costs. Which two actions should you include in the Azure Blob Storage lifecycle management policy to meet these requirements at the lowest cost? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Transition the blobs to the Cool tier 30 days after creation; Delete the blobs 365 days after creation

Cevap

Transitioning the blobs to the Cool tier after 30 days and deleting the blobs after 365 days.
Transitioning the blobs to the Cool tier 30 days after creation meets the requirement for lower-cost storage of rarely accessed data while maintaining sub-second retrieval times. Deleting the blobs 365 days after creation satisfies the regulatory requirement to keep logs for 365 days and then remove them to minimize storage costs.

Adım Adım Çözüm

1
Analyze the access frequency and retrieval latency requirements for the first stage.
The logs are frequently accessed for the first 30 days (Hot tier) and then rarely accessed but require immediate, sub-second retrieval. This matches the Cool tier characteristics.
The Cool tier offers lower storage costs than the Hot tier while maintaining sub-second retrieval times.
2
Evaluate the suitability of the Archive tier for the 30-day transition.
The Archive tier has retrieval latencies of several hours, which violates the requirement for immediate, sub-second troubleshooting access.
Data in the Archive tier is offline and must be rehydrated before it can be read.
3
Determine the action required at the end of the retention period.
The logs must be retained for a total of 365 days and then removed.
A delete action in the lifecycle policy 365 days after creation will remove the blobs to minimize costs.

Anahtar Kavram

Azure Blob Storage lifecycle management policy rules for tiering and deletion based on latency requirements.
Tahmini Süre:1m 30s
Soru 332Soru

An energy company is designing a security and access control solution for wind turbine telemetry logs stored in an Azure Blob Storage container named telemetry-logs. The solution must meet the following requirements:
- External wind farm maintenance contractors must be granted read-only access to the telemetry-logs container for a maximum of 24 hours.
- You must be able to immediately revoke the contractors' access before the 24-hour window expires, without changing the storage account key or impacting other active access tokens.
- Internal infrastructure engineers must be granted administrative access to manage the storage settings only when performing scheduled maintenance tasks, and their access must be audited and automatically expire.
Which two security controls should you recommend to meet the requirements? (Select two.)

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

Cevabı ve açıklamayı göster

Cevap: Create a stored access policy on the telemetry-logs container and generate a Shared Access Signature (SAS) token associated with the policy for the contractors.; Configure Microsoft Entra Privileged Identity Management (PIM) and assign the infrastructure engineers as eligible for the Storage Account Contributor role.

Cevap

Create a stored access policy on the telemetry-logs container and generate a Shared Access Signature (SAS) token associated with the policy for the contractors, and configure Microsoft Entra Privileged Identity Management (PIM) and assign the infrastructure engineers as eligible for the Storage Account Contributor role.
The correct recommendations are using a stored access policy for the SAS tokens and using Microsoft Entra Privileged Identity Management (PIM) with eligible role assignments. The stored access policy allows individual revocation of the generated SAS token without rotating the storage keys. PIM eligible role assignments ensure infrastructure engineers can only activate the Storage Account Contributor role when performing maintenance, ensuring auditing and automatic expiration of their administrative permissions.

Adım Adım Çözüm

1
Analyze the access and revocation requirements for external contractors.
Identify that a stored access policy is required because it allows revocation of the associated Shared Access Signature (SAS) tokens by modifying or deleting the policy.
Ad-hoc SAS tokens cannot be revoked individually; revoking them requires rotating the storage account keys, which would affect other active SAS tokens and violate the scenario constraints.
2
Analyze the access and lifecycle requirements for internal infrastructure engineers.
Determine that Microsoft Entra Privileged Identity Management (PIM) is required, specifically using eligible assignments.
Eligible assignments allow engineers to request activation of the administrative role only when needed (just-in-time) for a limited duration, requiring approval and generating audit logs.

Anahtar Kavram

Data Storage Security and Access Control using Stored Access Policies and Privileged Identity Management (PIM)
Soru 333Soru

A global maritime shipping logistics company is designing the disaster recovery architecture for its core vessel dispatch system. The database layer is deployed on an Azure SQL Managed Instance in the North Europe region.

The company has the following requirements for the disaster recovery site in the West Europe region:
- The Recovery Time Objective (RTO) must be less than 10 seconds.
- The Recovery Point Objective (RPO) must be less than 5 seconds.
- Client applications must connect using a single, unchanging connection string that automatically handles failovers.
- Read-heavy reporting queries must be automatically offloaded to the secondary replica.
- All database replication traffic must remain completely private and isolated from the public internet.

Which two components should you include in the relational database design to meet the requirements? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Configure an auto-failover group containing the primary and secondary Azure SQL Managed Instances, and route read-write traffic through the primary listener endpoint.; Establish a Global Virtual Network Peering between the virtual networks hosting the primary and secondary Azure SQL Managed Instances.

Cevap

Configure an auto-failover group containing the primary and secondary Azure SQL Managed Instances, and route read-write traffic through the primary listener endpoint; and establish a Global Virtual Network Peering between the virtual networks hosting the primary and secondary Azure SQL Managed Instances.
The combination of configuring an auto-failover group and establishing Global VNet Peering meets all the requirements. The auto-failover group provides the required RTO and RPO targets, along with a single listener endpoint that routes write operations to the active primary replica without client configuration. Since Azure SQL Managed Instance is deployed within a private subnet of a virtual network, Global VNet Peering connects the primary and secondary networks privately, ensuring that replication traffic remains isolated from the public internet.

Adım Adım Çözüm

1
Determine the relational database tier and feature support.
Identify that the workload uses Azure SQL Managed Instance, which does not support active geo-replication but natively supports auto-failover groups for disaster recovery and automated failover.
This establishes the baseline HA/DR technology aligned with the resource SKU.
2
Select the appropriate routing mechanism for client connection persistence.
Incorporate the auto-failover group's read-write listener endpoint in the design.
This guarantees a single connection string for the client applications that persists across failover events without code or configuration updates.
3
Design the network path between the two regional instances.
Select Global VNet Peering to connect the primary virtual network in North Europe with the secondary virtual network in West Europe.
Azure SQL Managed Instance is isolated within a virtual network subnet, so a private network routing path is required to secure replication traffic without exposing endpoints to the public internet.

Anahtar Kavram

Cross-region disaster recovery and network routing for Azure SQL Managed Instance using failover groups and Global VNet Peering.
Soru 334Soru

You are designing the data storage architecture for a global multiplayer online game. The game requires a database to store player session state and real-time match telemetry.

The database tier must meet the following requirements:
- Support a write-heavy workload with an 80:2080:20 write-to-read ratio.
- Provide sub-10 ms10\text{ ms} write latency for session updates.
- Achieve a recovery point objective (RPO=0RPO = 0) guaranteeing zero data loss in the event of a regional datacenter outage.
- Store cold telemetry data older than 3030 days in Azure Blob Storage, ensuring the archived data also survives a regional datacenter outage.
- Secure client-side telemetry uploads to the archive storage using Shared Access Signatures (SAS) that can be immediately revoked if client credentials are compromised.

You have the following data fields for partitioning the database:
- `gameRegion` (55 distinct values)
- `tenantId` (1212 distinct values)
- `playerId` (millions of unique values, uniformly distributed)
- `sessionType` (44 distinct values)

Which architecture should you recommend?

Cevabı ve açıklamayı göster

Cevap: Partition the Cosmos DB container using playerId. Configure the Cosmos DB account to use Strong consistency with a secondary read region. Configure the archive storage account with Geo-redundant storage (GRS). Secure client-side uploads by generating Shared Access Signatures (SAS) associated with a Stored Access Policy.

Cevap

Partition the Cosmos DB container using playerId, configure Strong consistency, use Geo-redundant storage (GRS) for blob archives, and secure client-side uploads with SAS tokens associated with a Stored Access Policy.
The correct design partitions the Cosmos DB container using a high-cardinality key like playerId to ensure even distribution of writes and reads, preventing hot partitions. To achieve zero data loss (RPO=0RPO = 0) in a regional disaster, the Cosmos DB account must use Strong consistency. For the archive Blob Storage, Geo-redundant storage (GRS) ensures survival during a regional disaster by replicating data to a secondary region. Finally, generating Shared Access Signatures (SAS) associated with a Stored Access Policy allows the tokens to be revoked instantly by modifying or deleting the policy, meeting the security requirement.

Adım Adım Çözüm

1
Select the database partition key that prevents hot partitions under high write load.
Choose playerId as the partition key.
Since the workload is write-heavy and playerId has millions of unique, uniformly distributed values, it provides high cardinality, ensuring that writes are distributed evenly across physical partitions and preventing hot partition bottlenecks.
2
Configure the consistency level to meet the zero data loss requirement.
Select Strong consistency with a secondary geo-replicated region.
To guarantee a recovery point objective of zero (RPO=0RPO = 0) in the event of a regional outage, write replication must be synchronous, which is only guaranteed by Strong consistency.
3
Select the appropriate redundancy tier for the archive storage.
Choose Geo-redundant storage (GRS) for the Blob Storage account.
GRS replicates data to a secondary region geographically distant from the primary region, ensuring the archived data survives a regional datacenter disaster.
4
Design the client-side token authorization and revocation mechanism.
Implement SAS tokens associated with a Stored Access Policy.
Ad-hoc SAS tokens cannot be revoked individually without rotating the storage account's master keys. Associating SAS tokens with a Stored Access Policy allows instantaneous revocation by simply deleting or updating the policy on the container.

Anahtar Kavram

Azure Cosmos DB partitioning, consistency levels, and Azure Storage redundancy and security configuration.
Soru 335Soru

A company plans to migrate an on-premises database environment to Azure. The environment contains multiple databases that require the execution of native cross-database queries using three-part names. In addition, the databases rely heavily on SQL Server Agent for scheduled ETL processes.

Which two database options should you recommend to support this migration? (Select two.)

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

Cevabı ve açıklamayı göster

Cevap: Azure SQL Managed Instance; SQL Server on Azure Virtual Machines

Cevap

Azure SQL Managed Instance and SQL Server on Azure Virtual Machines are the correct options.
Azure SQL Managed Instance and SQL Server on Azure Virtual Machines both support SQL Server Agent and native cross-database queries using three-part names because they provide instance-level SQL Server features. Managed Instance offers these capabilities with the benefits of a fully managed service (PaaS), while SQL Server on Azure VMs provides a complete SQL Server environment in an infrastructure-as-a-service (IaaS) model.

Adım Adım Çözüm

1
Analyze the technical requirements of the migration: SQL Server Agent and native cross-database queries using three-part names.
These are instance-level features of SQL Server.
Knowing that these are instance-level features helps eliminate options that only operate at the database level.
2
Evaluate the capabilities of Azure SQL Database offerings (single database and elastic pools).
Azure SQL Database does not natively support SQL Server Agent or native cross-database queries using three-part names.
Azure SQL Database is a database-scoped service and does not support these instance-level capabilities.
3
Evaluate the capabilities of Azure SQL Managed Instance and SQL Server on Azure VMs.
Both offerings provide instance-scoped database engines that support SQL Server Agent and cross-database queries.
Azure SQL Managed Instance provides near-complete compatibility with SQL Server, and SQL Server on Azure VMs runs a full SQL Server instance.

Anahtar Kavram

Instance-level vs. database-level feature compatibility in Azure SQL options
Tahmini Süre:2m 0s
Soru 336Soru

A financial services company is migrating an on-premises database workload to Azure Virtual Machines. You are designing the storage configuration for the database transaction logs, which require consistent high write throughput and single-digit millisecond latency. The storage design must also ensure that the database remains operational even if a single datacenter within the target Azure region experiences a power failure. Which storage option should you recommend?

Cevabı ve açıklamayı göster

Cevap: Premium SSD Managed Disks configured with Zone-Redundant Storage (ZRS)

Cevap

Premium SSD Managed Disks configured with Zone-Redundant Storage (ZRS)
The correct option is Premium SSD Managed Disks configured with Zone-Redundant Storage (ZRS). Database transaction logs are highly sensitive to latency and write performance, necessitating Premium SSD storage to guarantee single-digit millisecond latencies and high throughput. Furthermore, to survive the outage of a single datacenter (which corresponds to an Azure Availability Zone) without losing access to data, the disks must use Zone-Redundant Storage (ZRS) to replicate data synchronously across multiple zones in the region.

Adım Adım Çözüm

1
Analyze the performance requirements of the workload.
The workload is a database transaction log requiring consistent high write throughput and single-digit millisecond latency.
This performance tier requires at least Premium SSD (or Premium SSD v2/Ultra Disk) because Standard SSD and Standard HDD do not offer the necessary IOPS, throughput, or latency guarantees.
2
Analyze the high availability and resiliency requirements.
The storage solution must remain operational during a single datacenter (zone) power failure.
This requirement mandates Zone-Redundant Storage (ZRS), which replicates data synchronously across three availability zones in the region. Locally Redundant Storage (LRS) only replicates within a single datacenter and is insufficient.
3
Combine performance and redundancy requirements to select the optimal disk configuration.
Premium SSD Managed Disks with Zone-Redundant Storage (ZRS) meets both the latency/throughput needs and the zone outage resiliency requirements.
Selecting Premium SSD ensures database logs perform optimally, and ZRS ensures zone-level redundancy.

Anahtar Kavram

Selecting Azure Managed Disk tiers and redundancy configurations based on workload performance and high availability requirements.
Tahmini Süre:1m 30s
Soru 337Soru

An organization is designing a shared storage solution for a critical financial transaction processing application hosted on Azure Virtual Machines. The application requires a shared file system that can deliver consistent sub-millisecond latency for metadata and file operations. To meet high availability requirements, the storage must survive the failure of an entire availability zone within the primary region without any data loss and without manual intervention. Additionally, the solution must replicate data to a secondary region for disaster recovery purposes. Which storage configuration should you recommend?

Cevabı ve açıklamayı göster

Cevap: Premium Azure Files configured with Zone-Redundant Storage (ZRS), using Azure File Sync or an automated sync tool to replicate files to a secondary Premium file share.

Cevap

Premium Azure Files configured with Zone-Redundant Storage (ZRS), using Azure File Sync or an automated sync tool to replicate files to a secondary Premium file share.
The correct configuration is to use Premium Azure Files with Zone-Redundant Storage (ZRS) coupled with an external replication mechanism like Azure File Sync. Premium Azure Files is necessary to meet the sub-millisecond latency requirements. Because the Premium tier of Azure Files supports only LRS and ZRS replication natively, any disaster recovery strategy to a secondary region must be implemented using tools like Azure File Sync, AzCopy, or Azure Backup rather than native GRS/GZRS storage replication. ZRS ensures that the storage continues to operate seamlessly if a single availability zone fails in the primary region.

Adım Adım Çözüm

1
Analyze the performance requirements.
The requirement for consistent sub-millisecond latency for shared file operations necessitates the Premium performance tier of Azure Files, which is backed by SSD storage.
Standard Azure Files is backed by HDDs and cannot satisfy the low latency requirements.
2
Evaluate high availability and zone redundancy requirements in the primary region.
To survive the failure of an entire availability zone without manual intervention or data loss, the storage must use Zone-Redundant Storage (ZRS). Locally Redundant Storage (LRS) is insufficient.
ZRS replicates data synchronously across three availability zones in the primary region, providing zone-level fault tolerance.
3
Assess replication limits for Premium Azure Files.
Premium Azure Files only supports LRS and ZRS. It does not support native geo-redundancy options like GRS, GZRS, or RA-GZRS.
To achieve regional disaster recovery, a multi-region replication strategy must be built on top of ZRS using helper tools such as Azure File Sync, AzCopy, or Azure Backup.

Anahtar Kavram

Azure Files redundancy capabilities and performance tier limitations
Soru 338Soru

A financial services company is designing a new analytical data platform on Azure to query historical audit logs. The audit logs are stored in Parquet format in an Azure Data Lake Storage Gen2 account.

The platform must meet the following requirements:
- Volume: 80 TB80\text{ TB} of data is currently stored, growing by 2 TB2\text{ TB} per month.
- Velocity: Batch uploads occur once every week.
- Query Latency and Pattern: Data analysts run highly complex, ad-hoc exploratory queries to investigate anomalies. These queries occur irregularly, and the system may remain idle for several days.
- Resilience: The data must remain available even during a complete regional datacenter outage.
- Security: Access to the data lake must be delegated to external audit teams via Shared Access Signatures (SAS) that can be immediately revoked if security policies are violated.

You need to recommend the storage configuration and the query engine for the platform.

Which two components should you include in the recommendation? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: An Azure Synapse Analytics serverless SQL pool to query the Parquet files directly in the data lake.; A storage account configured for Geo-zone-redundant storage (GZRS) with access granted via Shared Access Signatures (SAS) that reference a stored access policy.

Cevap

The platform should include an Azure Synapse Analytics serverless SQL pool to execute ad-hoc queries, and a storage account configured for Geo-zone-redundant storage (GZRS) with access granted via Shared Access Signatures (SAS) referencing a stored access policy.
The correct recommendation consists of using an Azure Synapse Analytics serverless SQL pool and configuring the storage account for Geo-zone-redundant storage (GZRS) using Shared Access Signatures (SAS) associated with a stored access policy. A serverless SQL pool is optimal for ad-hoc, infrequent queries on data lake files because you only pay per query, avoiding idle costs. GZRS provides resilience against both zone and regional failures by replicating data across zones and to a secondary region. Associating the SAS with a stored access policy allows the administrator to revoke access immediately by modifying or deleting the policy.

Adım Adım Çözüm

1
Analyze the query pattern to choose the optimal query engine.
Serverless SQL pools are selected because the queries are ad-hoc, irregular, and the platform remains idle for days. This eliminates the persistent costs associated with running a dedicated SQL pool cluster when idle.
Dedicated SQL pools run continuously and incur significant costs even when idle, making them unsuitable for sporadic exploratory query workloads.
2
Evaluate the storage redundancy requirement to ensure availability during regional outages.
Geo-zone-redundant storage (GZRS) is selected. GZRS replicates data across three availability zones in the primary region and to a secondary region, providing protection against a regional disaster.
Locally redundant storage only replicates data within a single datacenter and cannot survive a regional outage.
3
Determine the secure access method that allows immediate revocation.
Shared Access Signatures (SAS) referencing a stored access policy are chosen over ad-hoc SAS tokens with long lifetimes.
Ad-hoc SAS tokens cannot be revoked individually without rotating the storage account keys. Referencing a stored access policy allows immediate revocation by deleting or modifying the policy.

Anahtar Kavram

Selecting the optimal query compute engine, storage redundancy, and access delegation mechanisms in Azure to balance cost, resilience, and security.
Soru 339Soru

An organization is designing an identity security strategy using Microsoft Entra ID. You need to match the specific security and access requirements to the correct Microsoft Entra ID Authentication or Conditional Access feature. How should you match the requirements to the appropriate features?

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

Öğeler

Prevent users on unmanaged personal devices from downloading, printing, or syncing files when accessing SharePoint Online.
Enforce the use of phishing-resistant authentication methods, such as FIDO2 security keys, when administrators access the Azure portal.
Force users to re-authenticate if their active session is older than 8 hours when they access a critical financial application.
Block access to all cloud applications if a user's sign-in pattern matches real-time anomalous detection patterns indicative of a compromised session.

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

Preventing downloads on unmanaged devices matches the app-enforced restrictions session control. Enforcing phishing-resistant methods for administrators matches the authentication strengths grant control. Forcing re-authentication after 8 hours matches the sign-in frequency session control. Blocking access for anomalous sign-ins matches the Entra ID Protection sign-in risk-based policy.
Matching the security requirements to their respective Microsoft Entra features relies on understanding the differentiation between session controls, grant controls, and risk-based policy options. App-enforced restrictions are designed for session-level controls in SharePoint/Exchange. Authentication strengths provide granular MFA requirements. Sign-in frequency manages the session lifetime. Sign-in risk policies evaluate live, dynamic threats.

Adım Adım Çözüm

1
Analyze the requirement for unmanaged personal devices accessing SharePoint Online.
Identified that restricting down-level actions (download, print, sync) requires the cloud application to receive device status from Entra ID and enforce those restrictions, which is configured via Conditional Access session controls using app-enforced restrictions.
This is a typical use case for SharePoint Online and Exchange Online integrations with Conditional Access.
2
Analyze the requirement to restrict administrative access to phishing-resistant MFA methods.
Identified that Conditional Access grant controls natively support authentication strengths to enforce specific MFA combinations (e.g., phishing-resistant MFA including FIDO2 or Windows Hello for Business).
Standard MFA options allow less secure methods like SMS, so authentication strengths are needed to restrict to phishing-resistant methods.
3
Analyze the requirement for forcing re-authentication after 8 hours.
Identified that the sign-in frequency session control in Conditional Access allows specifying a time interval after which a user must sign in again.
This configuration manages session lifetimes for high-value applications.
4
Analyze the requirement to block anomalous sign-in attempts indicating a compromised session.
Identified that real-time anomalous sign-in detection requires Entra ID Protection (formerly Azure AD Identity Protection) sign-in risk-based policy to evaluate the sign-in risk and apply block or MFA controls.
Conditional Access policies can consume sign-in risk signals from Microsoft Entra ID Protection to dynamically block access.

Anahtar Kavram

Microsoft Entra ID offers advanced authentication capabilities and Conditional Access policies, including session controls, authentication strengths, and risk-based integrations, to implement a Zero Trust access security model.
Soru 340Soru

You are designing a disaster recovery solution to Azure for an on-premises VMware virtual machine that hosts a financial database. The source environment has a 10 Gbps10\text{ Gbps} ExpressRoute connection to Azure.

The virtual machine has the following specifications:
- Operating system disk: 80 GB80\text{ GB} size, 4 MB/s4\text{ MB/s} average write churn
- Database log disk: 500 GB500\text{ GB} size, 35 MB/s35\text{ MB/s} average write churn
- Recovery Point Objective (RPO) goal: 15 minutes15\text{ minutes}
- Recovery Time Objective (RTO) goal: 4 hours4\text{ hours}

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

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

Cevabı ve açıklamayı göster

Cevap: Replicate the operating system disk to Azure by using Azure Site Recovery.; Exclude the database log disk from Azure Site Recovery replication and protect the database workload by using SQL Server native replication.

Cevap

The correct actions are to replicate the operating system disk to Azure by using Azure Site Recovery, and to exclude the database log disk from Azure Site Recovery replication while using SQL Server native replication to protect the database workload.
Replicating the operating system disk via Azure Site Recovery is supported because its write churn of 4 MB/s4\text{ MB/s} is below the 10 MB/s10\text{ MB/s} limit. Excluding the database log disk and using SQL Server native replication is required because the database log disk's write churn of 35 MB/s35\text{ MB/s} exceeds the supported replication limits of Azure Site Recovery.

Adım Adım Çözüm

1
Analyze the write churn of each disk on the source virtual machine.
The operating system disk has a write churn of 4 MB/s4\text{ MB/s}, and the database log disk has a write churn of 35 MB/s35\text{ MB/s}.
Identifying individual disk churn rates is necessary to check them against Azure Site Recovery limits.
2
Compare the disk churn rates against the Azure Site Recovery limits for on-premises VMware virtual machines.
The operating system disk churn (4 MB/s4\text{ MB/s}) is below the 10 MB/s10\text{ MB/s} limit, while the database log disk churn (35 MB/s35\text{ MB/s}) exceeds the 10 MB/s10\text{ MB/s} limit.
Azure Site Recovery replication will fail if a disk's write churn exceeds its supported threshold.
3
Design the disaster recovery replication strategy for the workload.
Use Azure Site Recovery to replicate the supported operating system disk, exclude the high-churn database log disk, and configure SQL Server native replication at the application layer to protect the database database files and log files.
This hybrid approach avoids Azure Site Recovery limits while ensuring all parts of the VM are protected within the 15 minutes15\text{ minutes} RPO.

Anahtar Kavram

Azure Site Recovery write churn limits and alternative replication strategies for high-churn database workloads.
Tahmini Süre:1m 0s
ÖncekiSayfa 17 / 60Sonraki
Tüm alıştırma soruları — Microsoft Azure Solutions Architect (AZ-305) | Examkin