Tüm alıştırma soruları

1198 soru

Soru 561Soru

EcoSphere Energy is designing a disaster recovery strategy for its energy consumption reporting application. The application stores monthly PDF reports in a general-purpose v2 Azure Storage account configured with Read-Access Geo-Redundant Storage (RA-GRS). During normal operations, the application writes reports to the primary region and reads them from both the primary and secondary regions.

During a prolonged outage in the primary region, the engineering team decides to initiate a customer-managed failover to the secondary region.

Which of the following describes the write capabilities and redundancy state of the storage account immediately after the customer-managed failover is completed?

Cevabı ve açıklamayı göster

Cevap: The storage account configuration is converted to locally redundant storage (LRS) in the new primary region, and write operations are supported at the new primary endpoint.

Cevap

The storage account configuration is converted to locally redundant storage (LRS) in the new primary region, and write operations are supported at the new primary endpoint.
When a customer-managed failover is initiated for an Azure Storage account configured with Read-Access Geo-Redundant Storage (RA-GRS), the secondary region is promoted to become the new primary region. Immediately after the failover is completed, the storage account's redundancy type is automatically converted to locally redundant storage (LRS), and write operations are enabled on the new primary endpoint. To restore geo-redundancy, the account must be manually reconfigured to GRS or RA-GRS.

Adım Adım Çözüm

1
Determine the write behavior of a geo-redundant storage account (GRS/RA-GRS) during normal operation versus outage situations.
Write operations are only allowed on the primary endpoint. The secondary endpoint is read-only (in RA-GRS) or inaccessible (in GRS) before failover.
Azure Storage accounts with geo-redundancy do not support active-active write configurations across primary and secondary endpoints.
2
Evaluate the state of the storage account immediately after a customer-managed failover is completed.
The secondary region's endpoint is promoted to become the new primary endpoint, enabling write operations, and the redundancy level changes to Locally Redundant Storage (LRS).
Initiating a failover updates the DNS records so that the secondary region acts as the primary, but replication to the old primary is stopped, making the storage account locally redundant in the new region.
3
Match the observed behavior with the correct system design options.
The correct option is the one stating the storage account transitions to LRS and supports write operations at the new primary endpoint.
This matches standard Azure Storage failover architecture mechanics.

Anahtar Kavram

Azure Storage Account Customer-Managed Failover Behavior
Soru 562Soru

An organization is designing a security and access control strategy for its Microsoft Entra ID tenant to protect cloud resources. You need to align the specific security requirements to the corresponding Microsoft Entra ID or Conditional Access features. Match each security requirement to the correct Microsoft Entra ID condition or session control.

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

Öğeler

Enforce a maximum session lifetime of 1 hour for high-privilege web access to the Azure portal.
Restrict downloading, printing, or syncing files from SharePoint Online when users connect from unmanaged personal devices.
Prompt for multi-factor authentication (MFA) only when Entra ID Protection flags a sign-in attempt as having anomalous telemetry.
Force a password change and require MFA when there is high confidence that a user's credentials have been leaked on the dark web.

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

Enforce session lifetime matches Sign-in frequency; restrict SharePoint downloads matches App-enforced restrictions; anomalous sign-in prompt matches Sign-in risk; password change for leaked credentials matches User risk.
The correct pairings map each technical requirement to the correct Entra ID capability. Enforcing a maximum session lifetime is configured via Sign-in frequency. Restricting file actions in SharePoint Online is handled by App-enforced restrictions. anomalous sign-in sessions are assessed using Sign-in risk, and leaked credentials represent identity compromise assessed via User risk.

Adım Adım Çözüm

1
Analyze session-related controls for active user connections.
The requirement to force re-authentication after a set time limit (1 hour) is addressed by the Sign-in frequency session control.
Sign-in frequency dictates the time frame before a user must sign in again to access the Azure portal or other apps.
2
Evaluate access limits for specific cloud applications on unmanaged devices.
Restricting downloading, printing, or syncing from SharePoint Online is addressed by App-enforced restrictions.
App-enforced restrictions allow Microsoft Entra ID to pass device compliance status to SharePoint Online, which then restricts file capabilities natively.
3
Differentiate between the two Microsoft Entra ID Protection risk conditions.
Real-time sign-in anomalies correspond to the Sign-in risk condition, while leaked credentials correspond to the User risk condition.
Sign-in risk looks at the specific login session telemetry (e.g., suspicious IPs), whereas User risk evaluates the health of the entire identity (e.g., dark web credential leaks).

Anahtar Kavram

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

A logistics company is designing an access and governance strategy for its telemetry processing workloads in Azure. The workloads run within a single subscription across multiple resource groups. You need to design a solution that delegates administrative access to a team of operations engineers to manage Network Security Groups (NSGs) and route tables in a dedicated networking resource group, while also enforcing temporary, audited access for senior administrators who require the Owner role at the subscription level. The solution must adhere to the principle of least privilege.

Which two actions should you include in the design?

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

Cevabı ve açıklamayı göster

Cevap: Create a Microsoft Entra ID group for the operations engineers and assign the Network Contributor role to the group at the resource group scope.; Configure Microsoft Entra Privileged Identity Management (PIM) to make the subscription Owner assignments eligible rather than active.

Cevap

Create a Microsoft Entra ID group for the operations engineers and assign the Network Contributor role to the group at the resource group scope; and configure Microsoft Entra Privileged Identity Management (PIM) to make the subscription Owner assignments eligible rather than active.
The correct options recommend creating a Microsoft Entra ID group for the operations engineers to assign the Network Contributor role at the resource group scope, and configuring Microsoft Entra Privileged Identity Management (PIM) to make the subscription Owner assignments eligible. Scoping the Network Contributor role to the resource group ensures least privilege, and group-based assignments ensure scalable identity lifecycle management. Making Owner assignments eligible in PIM ensures that senior administrators only hold high-privileged access when actively requested, justified, and audited, providing just-in-time (JIT) security.

Adım Adım Çözüm

1
Analyze delegation requirements for network operations.
Identify that operations engineers need to manage NSGs and route tables, which fits the Network Contributor role. Determine that permissions should be delegated at the resource group scope to adhere to least privilege.
Restricting role assignment to the resource group prevents the team from modifying resources in other resource groups.
2
Select the appropriate assignment target for the network role.
Determine that the Network Contributor role should be assigned to a Microsoft Entra ID group containing the operations engineers rather than directly to individuals.
Group-based role assignment aligns with Microsoft governance best practices and simplifies identity lifecycle management.
3
Analyze high-privileged access requirements for senior administrators.
Identify that the subscription Owner role should be assigned via Microsoft Entra Privileged Identity Management (PIM) with eligible assignments.
Using eligible assignments enforces just-in-time access, meaning users must explicitly activate the role for a limited time when needed, satisfying the requirement for temporary, audited access.

Anahtar Kavram

Azure RBAC best practices (group-based assignments and scoping) combined with just-in-time access management using Privileged Identity Management.
Soru 564Soru

A retail company stores transaction logs in an Azure General Purpose v2 (GPv2) storage account. The storage account is configured with Read-access geo-redundant storage (RA-GRS), with East US as the primary region and West US as the secondary region. To comply with regulatory audit requirements, the company's IT team plans to perform a disaster recovery drill by initiating a customer-managed failover of the storage account to the secondary region. Which two outcomes will occur once the failover is complete? (Select two.)

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

Cevabı ve açıklamayı göster

Cevap: The storage account's redundancy configuration is converted to locally-redundant storage (LRS).; The primary connection endpoints for the blob, file, queue, and table services remain unchanged.

Cevap

Once the customer-managed failover completes, the storage account's redundancy configuration is converted to locally-redundant storage (LRS), and the primary connection endpoints for the storage services remain unchanged.
When a customer-managed failover is initiated for an RA-GRS storage account, the secondary region becomes the new primary region, and the account type is automatically converted to LRS. Azure automatically updates the DNS settings so that the existing primary endpoints resolve to the new primary region, allowing applications using the primary connection strings to remain unchanged.

Adım Adım Çözüm

1
Analyze the customer-managed failover mechanism for Azure Storage.
Initiating a customer-managed failover promotes the secondary region (West US) to become the new primary region.
This is necessary to understand how the DNS and replication topologies change during a failover event.
2
Determine the post-failover redundancy state of the storage account.
The redundancy configuration of the storage account is changed to locally-redundant storage (LRS) in the new primary region.
Because replication is asynchronous, Azure converts the account to LRS to prevent automatic replication from overwriting data in the original primary region before the administrator decides to re-enable geo-redundancy.
3
Identify the endpoint behavior after the failover completes.
Azure updates DNS records to point the existing primary endpoints to the new primary region, leaving connection strings unchanged.
This ensures application continuity by preventing the need to reconfigure endpoints in connection strings.

Anahtar Kavram

Azure Storage customer-managed failover behavior and endpoint lifecycle.
Tahmini Süre:1m 30s
Soru 565Soru

Your company needs to host a serverless API endpoint that generates PDF reports. Each PDF generation request is CPU-intensive and takes up to 12 minutes to complete. The solution must scale dynamically and minimize administrative overhead. Which hosting option should you recommend?

Cevabı ve açıklamayı göster

Cevap: Azure Functions on a Premium plan

Cevap

Azure Functions on a Premium plan
Azure Functions Premium plan provides serverless scaling and low administrative overhead while allowing execution durations up to 30 minutes (or unbounded), which easily accommodates the 12-minute requirement.

Adım Adım Çözüm

1
Identify the execution duration requirement.
The requirement is 12 minutes of execution time.
Azure Functions Consumption plan has a 10-minute maximum limit, which rules it out.
2
Evaluate the administrative overhead constraints.
The solution must minimize administrative overhead and scale dynamically.
This rules out Azure Kubernetes Service (AKS) due to its high management complexity.
3
Evaluate workload reliability requirements.
API requests must run to completion reliably.
This rules out Spot VMs because they are subject to sudden eviction.

Anahtar Kavram

Selecting the appropriate serverless compute hosting model based on execution time limits, management overhead, and reliability.
Soru 566Soru

An enterprise is designing a global disaster recovery and traffic routing solution for a hybrid system deployed across the Azure East US region and an on-premises datacenter in Paris. The system contains the following workloads:

* Workload 1: A legacy inventory database application that communicates over TCP port 84438443. This workload requires global failover based on client proximity, but does not support HTTP protocols.
* Workload 2: A public-facing e-commerce web application (HTTPS) that requires SSL termination at the edge, URL path-based routing to different backend pools, and web application firewall (WAF) protection.

You need to design a routing and failover strategy that minimizes latency and meets all technical requirements. Which two actions should you include in the design?

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

Cevabı ve açıklamayı göster

Cevap: Deploy Azure Front Door to route traffic for Workload 2.; Deploy Azure Traffic Manager to route traffic for Workload 1.

Cevap

Deploy Azure Front Door to route traffic for Workload 2, and deploy Azure Traffic Manager to route traffic for Workload 1.
Deploying Azure Front Door for the e-commerce workload (Workload 2) meets the Layer 7 requirements (SSL termination, path-based routing, and WAF protection) using Anycast. Deploying Azure Traffic Manager for the database workload (Workload 1) allows routing of non-HTTP TCP traffic on port 8443 using DNS routing.

Adım Adım Çözüm

1
Analyze Workload 1 requirements.
Workload 1 uses a raw TCP protocol on port 84438443 and requires global proximity-based routing and failover.
Since Workload 1 is non-HTTP, any Layer 7 routing service (like Azure Front Door) is ruled out. A DNS-based routing solution like Azure Traffic Manager is required because it operates at the DNS layer and can route any protocol/port.
2
Analyze Workload 2 requirements.
Workload 2 requires SSL termination, WAF protection, and path-based routing for an HTTPS endpoint.
These are Layer 7 features. Azure Front Door is a global Layer 7 load balancer that utilizes Anycast DNS/routing to minimize latency, terminate SSL at the edge, apply WAF rules, and route traffic based on URL paths.
3
Compare and select the matching Azure services.
Azure Traffic Manager is selected for Workload 1, and Azure Front Door is selected for Workload 2.
This combination successfully meets all routing, protocol, security, and failover requirements while keeping latency minimal.

Anahtar Kavram

Selecting global traffic routing solutions based on protocol support (Layer 4/DNS vs. Layer 7 Anycast) and feature requirements (SSL offloading, WAF, and path-based routing).
Soru 567Soru

A financial services company hosts an accounting application on an Azure Virtual Machine. The virtual machine uses Premium SSD v2 managed disks for its database and log volumes. You must design an Azure Backup solution that meets the following requirements:

* Backups must be taken multiple times per day to achieve a low recovery point objective (RPO).
* Quick recovery from local snapshots must be available for any data lost within the last 5 days.
* Backups must be kept in vault storage for 365 days to meet regulatory compliance.

Which two configurations must you include in the backup policy design? (Select two.)

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

Cevabı ve açıklamayı göster

Cevap: Define the backup policy type as Enhanced.; Configure the instant restore retention to 5 days.

Cevap

To meet the requirements, the backup policy type must be defined as Enhanced and the instant restore retention must be configured to 5 days.
The correct configuration requires choosing the Enhanced policy type and setting the instant restore retention to 5 days. Premium SSD v2 disks are only supported by the Enhanced backup policy type, which also supports multiple backups per day. To achieve quick operational recovery from local snapshots, the instant restore retention must be aligned with the 5-day window.

Adım Adım Çözüm

1
Identify the disk tier and VM requirements.
The VM uses Premium SSD v2 managed disks and requires backups multiple times per day.
This determines which backup policy subtype is supported.
2
Select the appropriate backup policy type.
Select the Enhanced policy type.
Only the Enhanced policy type supports Premium SSD v2 managed disks and multiple daily backups.
3
Configure the local snapshot retention for fast recovery.
Set the instant restore retention to 5 days.
This keeps snapshots on the local disks for 5 days to facilitate quick recoveries under the low recovery time objective.

Anahtar Kavram

Azure Backup Enhanced policy capabilities and instant restore snapshot limits.
Soru 568Soru

A medical diagnostics company is designing a container-based data processing solution on Azure. The solution will process patient telemetry records from multiple regions. The solution must satisfy the following requirements:
- The data processing tasks are short-lived, containerized workloads that run to completion and execute only when new telemetry records arrive in an Azure Service Bus queue.
- The compute infrastructure must automatically scale to zero when the queue is empty, and scale out dynamically based on the queue depth using Kubernetes Event-driven Autoscaling (KEDA).
- Administrative overhead associated with managing virtual machines, orchestrator nodes, and host patching must be minimized.
- Compliance regulations dictate that patient telemetry logs must be stored and isolated within their respective geographical regions (Europe and North America).

Which two configurations should you include in the design?

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

Cevabı ve açıklamayı göster

Cevap: Azure Container Apps Jobs to host and execute the event-driven data processing tasks.; Two separate Log Analytics workspaces, one deployed in Europe and one in North America, to collect and isolate regional telemetry logs.

Cevap

The design should include Azure Container Apps Jobs to run the event-driven data processing tasks, and two separate Log Analytics workspaces (one in Europe and one in North America) to meet regional data sovereignty and isolation requirements.
The solution requires a serverless compute platform that runs containerized, short-lived, event-driven tasks to completion while minimizing operational overhead. Azure Container Apps Jobs natively support KEDA scaling, scale to zero, and offload host management. Additionally, regional data sovereignty rules require logs to be physically isolated and stored within their respective boundaries, necessitating two separate Log Analytics workspaces (one in Europe and one in North America).

Adım Adım Çözüm

1
Evaluate the compute options based on workload pattern and operational overhead constraints.
Identify that the workloads are short-lived, containerized tasks that run to completion and require KEDA. Azure Container Apps Jobs provide serverless execution with native KEDA triggers, eliminating node-level management compared to Azure Kubernetes Service (AKS).
This step eliminates options that introduce unnecessary management overhead like AKS.
2
Analyze the logging and regulatory requirements for data sovereignty.
Determine that telemetry logs must be physically stored and isolated in separate jurisdictions (Europe and North America). This requires deploying regional Log Analytics workspaces rather than a centralized one.
This step ensures compliance with data residency and sovereignty requirements.

Anahtar Kavram

Selecting serverless container services (Azure Container Apps Jobs) over full Kubernetes clusters (AKS) to reduce operational overhead for event-driven, short-lived tasks, and designing regional Log Analytics workspaces to satisfy regional data residency and compliance rules.
Tahmini Süre:3m 0s
Soru 569Soru

An online education provider is designing a telemetry storage solution using Azure Cosmos DB for NoSQL to record real-time progress events from students globally. The solution must handle a write-heavy workload (90%90\% writes, 10%10\% reads) with an ingestion rate of thousands of events per second. The database must be replicated across three Azure regions to guarantee a 99.999%99.999\% read and write availability SLA. The primary query pattern retrieves all activity logs for a specific course to generate completion reports. You need to design a storage and security configuration that prevents hot partitions, ensures write scalability, and complies with security best practices. Which configuration should you recommend?

Cevabı ve açıklamayı göster

Cevap: Select studentId as the partition key, and configure the Cosmos DB account with multi-region writes enabled across all three regions.

Cevap

Select studentId as the partition key, and configure the Cosmos DB account with multi-region writes enabled across all three regions.
Selecting the student ID as the partition key provides high cardinality, distributing the write workload evenly across physical partitions. This avoids hot partitions. Enabling multi-region writes satisfies the 99.999% write availability SLA by allowing local writes in all three regions.

Adım Adım Çözüm

1
Analyze availability and regional replication requirements.
A 99.999% availability SLA for both reads and writes requires Azure Cosmos DB to be configured with multi-region writes across the target regions.
Single-region or single-write-region configurations cannot guarantee 99.999% write availability during a regional outage.
2
Evaluate the partition key to ensure scale and avoid hot partitions.
Select studentId instead of courseId.
Since the workload is write-heavy and studentId has much higher cardinality than courseId, it distributes writes more evenly. CourseId would create hot partitions for popular courses.
3
Determine the correct authentication mechanism.
Avoid using Shared Access Signatures (SAS) which are not supported by Cosmos DB and present key rotation risks when configured with long lifetimes without a stored access policy.
Cosmos DB client writes should be authorized via Microsoft Entra ID or resource tokens, not long-lived SAS tokens.

Anahtar Kavram

Azure Cosmos DB partitioning strategies, multi-region write availability, and security access controls.
Tahmini Süre:1m 30s
Soru 570Soru

An administrator designs a virtual network named `vnet-corp-ops` with the address space 192.168.0.0/16192.168.0.0/16. The virtual network contains a subnet named `snet-application` (192.168.1.0/24192.168.1.0/24) and a security subnet named `snet-security` (192.168.2.0/24192.168.2.0/24). A network virtual appliance (NVA) is deployed in `snet-security` with the IP address 192.168.2.4192.168.2.4.

To inspect internal traffic, the administrator creates a route table and associates it with `snet-application`. The route table contains a user-defined route for the prefix 192.168.0.0/16192.168.0.0/16 with a next hop type of Virtual Appliance and the next hop IP address set to 192.168.2.4192.168.2.4.

How will Azure route traffic sent from a virtual machine in `snet-application` to a destination IP address of 192.168.3.10192.168.3.10?

Cevabı ve açıklamayı göster

Cevap: The traffic is forwarded to the network virtual appliance at 192.168.2.4192.168.2.4.

Cevap

The traffic is forwarded to the network virtual appliance at 192.168.2.4192.168.2.4.
The correct answer is correct because Azure routing rules dictate that when two routes have the same prefix length, a user-defined route takes precedence over the default system route. Therefore, the custom route directing traffic to the virtual appliance at 192.168.2.4192.168.2.4 is selected.

Adım Adım Çözüm

1
Identify the destination IP and find all matching routes in the route table associated with snet-application.
The destination IP 192.168.3.10192.168.3.10 matches both the default system route for the virtual network (192.168.0.0/16192.168.0.0/16) and the user-defined route (192.168.0.0/16192.168.0.0/16).
Azure evaluates routes by comparing the destination IP against the prefixes of all active routes.
2
Apply the longest prefix match rule to determine if one route is more specific.
Both matching routes have the same prefix length of /16/16.
If one route had a longer prefix, it would be selected immediately. Since they are identical, prefix length does not break the tie.
3
Apply Azure route source priority rules to resolve identical prefix matches.
The user-defined route is selected over the default system route.
Azure assigns higher priority to user-defined routes than to default system routes when prefix lengths are identical.

Anahtar Kavram

User-defined route precedence over default system routes
Soru 571Soru

An enterprise is designing a privileged access governance solution for its Azure environment. The solution must satisfy the following security and administrative requirements:

- Members of the operations team must only have permissions to manage virtual machines when performing scheduled maintenance tasks.
- Permissions to manage virtual machines must be assigned at scale to groups rather than to individual user accounts.
- Emergency access accounts must be protected from lockout risks associated with tenant-wide multi-factor authentication (MFA) policies.

Which two actions should you include in the design? (Choose two.)

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

Cevabı ve açıklamayı göster

Cevap: Configure the operations team members as eligible members of a Microsoft Entra group that is assigned the Virtual Machine Contributor role by using Privileged Identity Management (PIM) for Groups.; Exclude the emergency access accounts from the Conditional Access policies that require multi-factor authentication (MFA).

Cevap

To meet the requirements, you should configure the operations team members as eligible members of a Microsoft Entra group that is assigned the Virtual Machine Contributor role by using Privileged Identity Management (PIM) for Groups, and exclude the emergency access accounts from the Conditional Access policies that require multi-factor authentication (MFA).
Configuring operations team members as eligible group members in PIM for Groups ensures that they only gain the Virtual Machine Contributor role on-demand, which adheres to the principle of least privilege and just-in-time access. Furthermore, excluding emergency access accounts from MFA Conditional Access policies ensures that these accounts remain accessible during a tenant-wide identity outage or MFA service disruption.

Adım Adım Çözüm

1
Analyze group governance requirements
Determine that managing individual permissions directly is inefficient at scale, necessitating group-based assignments.
Ensures that administrative actions are centralized and audit logs remain manageable.
2
Design just-in-time access controls
Use Privileged Identity Management (PIM) for Groups to configure eligibility rules for the operations team group.
Ensures users only activate their group membership when performing maintenance tasks, eliminating standing access.
3
Ensure high availability of emergency accounts
Identify policies that enforce MFA and configure exclusions for designated emergency access accounts.
Prevents administrative lockouts during MFA outages or sync issues.

Anahtar Kavram

Privileged access management using group-based PIM eligibility and emergency account lockout prevention.
Soru 572Soru

A financial services company is designing a subscription governance strategy for its transaction auditing platform. The auditing application runs across multiple resource groups within a dedicated Azure subscription. External audit administrators must be allowed to review resource configurations and database settings for a maximum of 8 hours during quarterly audit windows. To satisfy compliance, the solution must adhere to the principle of least privilege, minimize administrative overhead, and prevent permanent permission assignments. Which of the following designs best meets these requirements?

Cevabı ve açıklamayı göster

Cevap: Create a Microsoft Entra security group containing the audit administrators. Assign the Reader role to the group at the subscription scope, and configure Microsoft Entra Privileged Identity Management (PIM) to make the users eligible for membership in this group.

Cevap

Create a Microsoft Entra security group containing the audit administrators. Assign the Reader role to the group at the subscription scope, and configure Microsoft Entra Privileged Identity Management (PIM) to make the users eligible for membership in this group.
The correct design uses a Microsoft Entra security group to assign the Reader role at the subscription scope, which simplifies administrative overhead and ensures scalability. By configuring Microsoft Entra Privileged Identity Management (PIM) to make users eligible for group membership, the organization enforces just-in-time access, satisfying the requirement to prevent permanent permissions while restricting the access duration.

Adım Adım Çözüm

1
Analyze governance requirements and identify the identity container to use.
Identify that permissions should be assigned to a Microsoft Entra security group rather than individual user accounts to ensure scalable governance and minimal administrative overhead.
Direct user assignments violate Azure RBAC best practices and increase administrative complexity.
2
Determine the correct role and scope to enforce least privilege.
Select the Reader role at the subscription scope to allow viewing resource configurations and database settings without granting write or delete permissions.
The Reader role is the least privileged built-in role that satisfies the read-only requirement at the subscription scope.
3
Evaluate the mechanism for time-limited, non-permanent access control.
Utilize Microsoft Entra Privileged Identity Management (PIM) to make the audit administrators eligible for the group membership during the audit window.
PIM ensures just-in-time activation with a maximum duration constraint, ensuring that the permissions are not permanently active.

Anahtar Kavram

Azure RBAC and Subscription Governance utilizing Microsoft Entra groups and PIM
Soru 573Soru

A marine logistics company is designing a storage solution for real-time cargo container tracking data. The data is stored in an Azure General Purpose v2 (GPv2) storage account. The design must satisfy the following requirements:

- The data must survive a regional disaster and remain available for read-only reporting in the secondary region without initiating a failover.
- The storage system in the primary region must tolerate the loss of an entire datacenter zone without data loss or service disruption.
- Tracking reports must be generated instantly, requiring sub-second retrieval times for all data stored in the account.

Which storage configuration should you recommend?

Cevabı ve açıklamayı göster

Cevap: Read-access geo-zone-redundant storage (RA-GZRS) using the Hot access tier

Cevap

Read-access geo-zone-redundant storage (RA-GZRS) using the Hot access tier
Read-access geo-zone-redundant storage (RA-GZRS) replicates data synchronously across three availability zones in the primary region, ensuring protection against zone outages. It also replicates data asynchronously to a secondary region and enables read access to the secondary endpoint. Using the Hot access tier ensures that tracking reports can be generated instantly with sub-second retrieval latency.

Adım Adım Çözüm

1
Analyze the availability zone and regional recovery constraints.
The primary region requires zone-level resilience (ZRS) and the secondary region requires read-access geo-redundancy (RA-GRS/RA-GZRS), leading to RA-GZRS.
To determine the minimal redundancy tier that satisfies both zone-redundancy and cross-region read requirements.
2
Evaluate write capability requirements on the secondary endpoint.
The secondary endpoint is read-only; active-active write configurations are unsupported for geo-redundant storage.
To rule out configurations that incorrectly assume write capabilities on the secondary region.
3
Determine the correct storage access tier based on retrieval latency requirements.
Sub-second retrieval requires Hot or Cool access tiers; Archive tier is excluded due to rehydration delays.
To select an online access tier that meets the performance requirements of the reporting application.

Anahtar Kavram

Selecting the optimal Azure Storage redundancy tier (RA-GZRS) and access tier (Hot) based on zonal/regional availability and performance requirements.
Soru 574Soru

An organization is modernizing its application portfolio and migrating multiple databases to Azure Cosmos DB. You need to recommend the appropriate Azure Cosmos DB API for each application workload. Match each application workload description to its correct Azure Cosmos DB API.

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

Öğeler

A social networking application that needs to store and analyze complex relationships, user connections, and interest graphs using graph traversal queries.
An industrial IoT monitoring system that migrates an on-premises wide-column database and requires compatibility with existing Cassandra Query Language (CQL) drivers.
A content management system storing semi-structured article data that must integrate seamlessly with existing MongoDB drivers and aggregation pipelines.
A new cloud-native transactional order processing service that requires optimal performance, low latency, and querying using SQL syntax.

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

Match the social networking graph application with Azure Cosmos DB for Apache Gremlin, the industrial IoT Cassandra-based telemetry database with Azure Cosmos DB for Apache Cassandra, the MongoDB-compatible content management system with Azure Cosmos DB for MongoDB, and the new cloud-native SQL-queried order processing service with Azure Cosmos DB for NoSQL.
Azure Cosmos DB provides API compatibility with MongoDB, Cassandra, Gremlin, and Table, alongside its native NoSQL API. Matching each workload ensures database migration and feature compatibility: Gremlin for graph workloads, Cassandra for wide-column/CQL workloads, MongoDB for BSON document workloads, and NoSQL for new JSON/SQL-queried workloads.

Adım Adım Çözüm

1
Analyze the social networking graph requirement.
Identified the need to store entities and complex relationships (graph data) and perform traversals, which points to a graph database API.
Azure Cosmos DB for Apache Gremlin is the specific API for graph databases.
2
Analyze the industrial IoT migration requirement.
Identified the need for CQL compatibility and wide-column store support.
Azure Cosmos DB for Apache Cassandra provides compatibility with CQL and Cassandra drivers.
3
Analyze the content management system migration requirement.
Identified the requirement for MongoDB driver and aggregation pipeline compatibility.
Azure Cosmos DB for MongoDB is compatible with the MongoDB wire protocol.
4
Analyze the new cloud-native order processing service requirement.
Identified a new application needing standard SQL querying and optimal performance on Cosmos DB.
Azure Cosmos DB for NoSQL is the native API and uses SQL querying, offering the best integration and performance for new workloads.

Anahtar Kavram

Selecting the appropriate Azure Cosmos DB API based on database compatibility and application requirements.
Soru 575Soru

A financial services company is designing a storage solution to host shared configuration files for a containerized trading application. The application requires SMB file shares with sub-millisecond latency and high IOPS. The storage solution must remain available if a single availability zone in the primary region fails. Additionally, the company requires disaster recovery capabilities to recover the files in a secondary Azure region with a Recovery Point Objective (RPO) of 24 hours. You plan to use Azure File Sync to replicate files to the secondary region. Which redundancy configuration should you select for the primary Azure storage account to meet these requirements?

Cevabı ve açıklamayı göster

Cevap: Zone-redundant storage (ZRS)

Cevap

Zone-redundant storage (ZRS) in a Premium file share (FileStorage) account combined with Azure File Sync for regional replication.
The correct option stating Zone-redundant storage (ZRS) is correct because the performance requirements (sub-millisecond latency and high IOPS for SMB) dictate the use of Premium Azure Files. Premium file shares are hosted in FileStorage accounts, which only support LRS and ZRS redundancy options. To satisfy the high availability requirement of surviving a zone outage, ZRS is required because it replicates data synchronously across three availability zones. The regional recovery requirement is fulfilled by replicating data to the secondary region using Azure File Sync, which easily accommodates the relaxed 24-hour RPO constraint.

Adım Adım Çözüm

1
Determine the required performance tier based on latency and protocol requirements.
The application requires SMB file shares with sub-millisecond latency and high IOPS, which mandates the use of Premium Azure Files (FileStorage account type) instead of the Standard tier.
Standard storage accounts do not guarantee sub-millisecond latency for file shares.
2
Identify the available redundancy options for the selected performance tier.
Premium file shares only support Locally-redundant storage (LRS) and Zone-redundant storage (ZRS) options.
Native geo-redundant options (GRS, GZRS, RA-GRS, RA-GZRS) are not supported for the FileStorage account type.
3
Evaluate the resiliency requirement against the available options.
To survive the failure of a single availability zone in the primary region, Zone-redundant storage (ZRS) must be selected.
LRS does not protect against zone-level failures, whereas ZRS synchronously replicates data across three zones.
4
Ensure the disaster recovery requirement is satisfied by the architecture.
The 24-hour RPO for regional disaster recovery is met by configuring Azure File Sync to replicate files from the primary ZRS Premium file share to the secondary region.
Since native geo-replication is unsupported for Premium file shares, an external replication mechanism like Azure File Sync is necessary to meet the DR requirements.

Anahtar Kavram

Azure Storage account type features and limitations regarding redundancy tiers, specifically that Premium File Shares (FileStorage) support only LRS and ZRS, requiring application-level or auxiliary replication tools (such as Azure File Sync) to achieve regional disaster recovery.
Soru 576Soru

An enterprise designs a disaster recovery (DR) solution for a critical financial application hosted on Azure virtual machines (VMs) in the East US region, with West US as the target DR region.

The application architecture consists of:
* Two application tier VMs (AppVM1AppVM1 and AppVM2AppVM2). Each VM has a write churn rate of 1 MB/s1\text{ MB/s}.
* Two database tier VMs (DBVM1DBVM1 and DBVM2DBVM2) running SQL Server. Each database VM has three Premium SSD disks: a data disk with 8 MB/s8\text{ MB/s} write churn, a transaction log disk with 25 MB/s25\text{ MB/s} write churn, and a TempDB disk with 15 MB/s15\text{ MB/s} write churn.

The business requirements specify:
* The application tier requires a Recovery Point Objective (RPO) of 2 hours2\text{ hours} and a Recovery Time Objective (RTO) of 4 hours4\text{ hours}.
* The database tier requires an RPO of 10 seconds10\text{ seconds} and an RTO of 10 minutes10\text{ minutes}.

Which two actions should you include in the disaster recovery design?

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

Cevabı ve açıklamayı göster

Cevap: Replicate the application tier VMs (AppVM1 and AppVM2) to the West US region by using Azure Site Recovery.; Configure SQL Server Always On Availability Groups to replicate the databases from the East US region to target SQL Server VMs in the West US region.

Cevap

Replicating the application tier VMs with Azure Site Recovery and configuring SQL Server Always On Availability Groups for the database tier.
The correct design uses Azure Site Recovery to replicate the application VMs since their RPO and churn fit within ASR's capability envelope. For the database tier, native SQL Server Always On Availability Groups are required because the 10-second10\text{-second} RPO cannot be met by ASR, and the transaction log disk's write churn of 25 MB/s25\text{ MB/s} exceeds standard ASR limits.

Adım Adım Çözüm

1
Analyze the database tier constraints.
The database VMs require a 10-second RPO and have a transaction log write churn of 25 MB/s25\text{ MB/s}.
Identify if Azure Site Recovery can support the database tier requirements.
2
Evaluate Azure Site Recovery limits and capabilities.
Azure Site Recovery cannot support a 10-second RPO (standard RPO is higher) and the 25 MB/s25\text{ MB/s} log disk write churn exceeds the standard Premium SSD per-disk replication limit of 10 MB/s10\text{ MB/s}. Thus, ASR cannot be used for the database tier.
Compare database requirements against Azure Site Recovery service limitations.
3
Select database-native replication tools.
SQL Server Always On Availability Groups should be configured for the database tier to achieve near-real-time asynchronous replication and support the 10-second RPO.
Meet database RPO and bypass Azure Site Recovery write churn constraints.
4
Evaluate the application tier constraints.
The application tier requires a 2-hour RPO and has 1 MB/s1\text{ MB/s} write churn, which is well within Azure Site Recovery thresholds.
Determine the appropriate DR mechanism for the application tier VMs.

Anahtar Kavram

Designing hybrid replication strategies using Azure Site Recovery and database-native replication tools based on write churn limits and RPO constraints.
Soru 577Soru

You are designing the hosting infrastructure for a new, simple containerized web application. The application needs to scale dynamically based on incoming HTTP traffic, and the development team wants to minimize operational overhead. Which two Azure compute options should you recommend? (Select two.)

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

Cevabı ve açıklamayı göster

Cevap: Azure Container Apps; Azure App Service (Web App for Containers)

Cevap

Azure Container Apps and Azure App Service (Web App for Containers) are the correct options to host the application.
Azure Container Apps and Azure App Service (Web App for Containers) are the correct options because they are fully managed platform offerings that require minimal operational overhead and support automatic, dynamic scaling based on HTTP traffic. This matches the requirements of hosting a simple containerized web application with low administrative effort.

Adım Adım Çözüm

1
Analyze the application hosting requirements.
The application is a simple, single containerized web app requiring dynamic scaling based on HTTP traffic and minimal operational overhead.
This establishes the criteria for evaluating the compute services.
2
Evaluate the overhead and capabilities of each service option.
Azure Container Apps and Azure App Service are both fully managed PaaS/serverless offerings that require minimal configuration and automatically handle HTTP-based scaling. Azure Kubernetes Service (AKS) introduces complex Kubernetes cluster management overhead. Azure Functions on a Consumption plan is designed for short-lived, event-driven functions and has execution timeout limits that make it unsuitable for persistent web applications.
This filters out high-overhead and functionally constrained options.
3
Select the two options that best match the criteria.
Azure Container Apps and Azure App Service (Web App for Containers) are selected.
Both satisfy the operational simplicity and HTTP-based scaling requirements.

Anahtar Kavram

Selecting appropriate managed container hosting options in Azure to minimize operational overhead.
Soru 578Soru

An enterprise designs a virtual network named `vnet-sea-prod` (172.20.0.0/16172.20.0.0/16) to host a two-tier application. The virtual network contains the following subnets:

* `snet-app` (172.20.1.0/24172.20.1.0/24) containing application servers
* `snet-data` (172.20.2.0/24172.20.2.0/24) containing database servers
* `snet-shared` (172.20.10.0/24172.20.10.0/24) containing a virtual firewall appliance with the IP address 172.20.10.4172.20.10.4

The company's security policy requires that all traffic originating from the application servers in `snet-app` and destined for the database servers in `snet-data` must be inspected by the firewall. However, virtual machines within `snet-app` must be able to communicate directly with each other without routing through the firewall.

You need to design a routing solution that meets these requirements.

Which route should you add to a route table associated with `snet-app`?

Cevabı ve açıklamayı göster

Cevap: A route with the destination prefix 172.20.2.0/24172.20.2.0/24 and next hop type Virtual appliance pointing to 172.20.10.4172.20.10.4

Cevap

A route with the destination prefix 172.20.2.0/24172.20.2.0/24 and next hop type Virtual appliance pointing to 172.20.10.4172.20.10.4
The correct route uses the destination prefix 172.20.2.0/24172.20.2.0/24. Because this prefix is more specific than the default local virtual network route of 172.20.0.0/16172.20.0.0/16, traffic from the application subnet destined for the database subnet will be directed to the firewall. Since there is no user-defined route for the application subnet itself (172.20.1.0/24172.20.1.0/24), traffic between servers in the same subnet will continue to use the system route and flow directly without hitting the firewall, satisfying both requirements.

Adım Adım Çözüm

1
Analyze Azure's routing evaluation order.
Azure routes traffic based on the Longest Prefix Match (LPM) algorithm and evaluates User-Defined Routes (UDRs) before default system routes of the same prefix length.
To determine how traffic will flow, we must identify the most specific prefix match in the route table for each target destination.
2
Define the rule for traffic going from the application subnet to the database subnet.
A route targeting 172.20.2.0/24172.20.2.0/24 with the next hop of the firewall (172.20.10.4172.20.10.4) is more specific than the default 172.20.0.0/16172.20.0.0/16 system route. Traffic to the database subnet will successfully go through the firewall.
This satisfies the security requirement to inspect app-to-database traffic.
3
Verify that intra-subnet communication is not impacted.
Intra-subnet traffic (destined for 172.20.1.0/24172.20.1.0/24) will not match the new 172.20.2.0/24172.20.2.0/24 route. Instead, it falls back to the default local system route (172.20.0.0/16172.20.0.0/16 -> Local), routing directly within the subnet.
This satisfies the requirement that VMs in the application subnet must communicate directly without traversing the firewall.

Anahtar Kavram

Azure User-Defined Routes (UDR) override system routes and are evaluated using Longest Prefix Match (LPM). To steer traffic between specific subnets without disrupting intra-subnet traffic, UDRs should specify the exact destination subnet range rather than the entire virtual network prefix.
Soru 579Soru

An enterprise is designing a hub-and-spoke virtual network topology in Azure. The hub virtual network, `vnet-weur-hub` (address space: 10.10.0.0/1610.10.0.0/16), contains:
- An internal Azure Standard Load Balancer with a frontend IP address of 10.10.1.10010.10.1.100 that balances traffic across an active-active pair of network virtual appliances (NVAs).
- An Azure ExpressRoute Gateway in the `GatewaySubnet` (10.10.3.0/2410.10.3.0/24) connected to an on-premises network that advertises the IP prefix 172.16.0.0/12172.16.0.0/12.

The spoke virtual network, `vnet-prod-spoke` (address space: 10.20.0.0/1610.20.0.0/16), is peered with `vnet-weur-hub` with gateway transit enabled on the hub and remote gateway usage enabled on the spoke. The spoke virtual network contains two subnets:
- `snet-web` (10.20.1.0/2410.20.1.0/24)
- `snet-data` (10.20.2.0/2410.20.2.0/24)

You need to design a routing solution for the virtual machines in `snet-web` to satisfy the following requirements:
- All outbound traffic to the internet must pass through the NVAs for security inspection.
- Traffic to the on-premises network must bypass the NVAs and route directly through the ExpressRoute Gateway.
- Traffic between `snet-web` and `snet-data` must remain internal to the spoke virtual network and must not transit the hub or the NVAs.
- The design must minimize administrative overhead and avoid configuring redundant route entries.

Which three configuration actions should you include in the design? (Select three.)

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

Cevabı ve açıklamayı göster

Cevap: Create a custom route table and associate it with `snet-web`.; In the custom route table, add a route for 0.0.0.0/00.0.0.0/0 with the next hop type of Virtual Appliance and the next hop IP address set to 10.10.1.10010.10.1.100.; Enable gateway route propagation on the custom route table.

Cevap

To meet the requirements, you should create a custom route table, associate it with the web subnet, add a user-defined route for the default route pointing to the internal load balancer IP, and ensure that gateway route propagation is enabled on the route table.
To route internet-bound traffic through the firewalls, a custom route table must be created and associated with the web subnet containing a default route (0.0.0.0/00.0.0.0/0) pointing to the internal load balancer's frontend IP. By enabling gateway route propagation, the subnet automatically learns the on-premises route (172.16.0.0/12172.16.0.0/12) via the ExpressRoute Gateway. Because of the Longest Prefix Match rule, traffic destined for the on-premises network matches the more specific propagated route and bypasses the NVAs. Meanwhile, intra-virtual-network traffic matches the system-defined local route (10.20.0.0/1610.20.0.0/16 -> Local), which is also more specific than the default route, ensuring that communication between the subnets remains local.

Adım Adım Çözüm

1
Create a custom route table and associate it with the target subnet.
The subnet is prepared to accept user-defined routes that override default Azure system routing.
This allows applying custom routing rules specifically to the web subnet.
2
Add a user-defined route for the prefix 0.0.0.0/00.0.0.0/0 with the next hop type of Virtual Appliance pointing to the internal load balancer's frontend IP (10.10.1.10010.10.1.100).
All traffic not matching a more specific route is sent to the load-balanced NVAs.
This ensures that internet-bound traffic is inspected by the firewalls in a highly available active-active configuration.
3
Ensure gateway route propagation is enabled on the custom route table.
The subnet automatically inherits the 172.16.0.0/12172.16.0.0/12 route from the ExpressRoute Gateway.
By the Longest Prefix Match (LPM) rule, traffic destined for the on-premises network (172.16.0.0/12172.16.0.0/12) matches the propagated route rather than the default route (0.0.0.0/00.0.0.0/0), routing directly to the gateway and bypassing the NVAs without administrative overhead.
4
Leave the local virtual network prefix route (10.20.0.0/1610.20.0.0/16 -> Local) as a system route without overriding it.
Intra-virtual-network traffic between the web and data subnets remains direct and does not transit the hub.
The system local route is more specific than the default route, ensuring local direct routing is maintained.

Anahtar Kavram

Interaction of User-Defined Routes (UDRs), system-defined routes, and BGP-propagated routes using Longest Prefix Match (LPM).
Soru 580Soru

An organization uses an Azure Data Lake Storage Gen2 (ADLS Gen2) account with hierarchical namespace enabled to store transaction logs. You need to configure a lifecycle management policy to meet the following requirements:
- The logs must support high-throughput, sub-second read and write access for the first 30 days after creation.
- From day 31 through day 180, logs are queried occasionally for auditing and must be available with sub-second retrieval latency.
- From day 181 through day 1,095 (3 years), the logs are kept strictly for regulatory compliance and are rarely accessed. A retrieval latency of up to 15 hours is acceptable.
- After 1,095 days, the logs can be safely deleted.
- Storage costs must be minimized.

Which two actions should you include in the lifecycle management policy?

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.; Transition the blobs to the Archive tier 180 days after creation.

Cevap

Transition the blobs to the Cool tier 30 days after creation, and transition the blobs to the Archive tier 180 days after creation.
Transitioning the blobs to the Cool tier 30 days after creation and transitioning them to the Archive tier 180 days after creation satisfies all latency and retention requirements at the lowest cost. The Cool tier preserves the required sub-second retrieval latency for auditing between days 31 and 180, while the Archive tier minimizes cost for the remaining compliance period where up to 15 hours of latency is acceptable.

Adım Adım Çözüm

1
Analyze the retrieval latency requirements for each phase.
Days 1 to 30 require the Hot tier (sub-second read/write). Days 31 to 180 require sub-second retrieval latency, meaning the data cannot be moved to the Archive tier yet. Days 181 to 1,095 allow up to 15 hours of latency, permitting the Archive tier.
Ensures the target storage tier for each lifecycle phase complies with access frequency and latency service level agreements.
2
Determine the cost-optimized transition schedule.
Transition to the Cool tier at day 30, which reduces storage costs while maintaining the required low latency. Transition to the Archive tier at day 180, which offers the lowest storage cost for the remainder of the compliance retention period.
Minimizes overall storage costs by moving the data to cooler tiers as soon as the latency requirements relax.
3
Validate the lifecycle policy against early deletion charges.
The blobs are kept in the Cool tier for 150 days (exceeding the 30-day minimum) and in the Archive tier for 915 days (exceeding the 180-day minimum) before deletion at day 1,095. No early deletion penalties are incurred.
Avoids unexpected billing overhead by ensuring the duration spent in each tier meets minimum retention constraints.

Anahtar Kavram

Data lifecycle management policies optimize storage costs by automatically transitioning blobs to cooler storage tiers or deleting them based on age, while aligning with retrieval latency and retention requirements.
ÖncekiSayfa 29 / 60Sonraki