Tüm alıştırma soruları

1198 soru

Soru 201Soru

A financial services company is designing the deployment of a relational database on Azure to store sensitive transaction logs. The database has the following requirements:
- The database must be deployed directly into a private subnet of an Azure Virtual Network (VNet) with no public IP address or public endpoints allowed.
- The system must run scheduled maintenance and data archival scripts natively using SQL Server Agent.
- The administrative team wants to minimize OS-level management tasks, such as patching and backups.

Which database solution should you recommend?

Cevabı ve açıklamayı göster

Cevap: Azure SQL Managed Instance

Cevap

Azure SQL Managed Instance
The correct solution is Azure SQL Managed Instance because it satisfies the VNet injection requirement (deploying directly into a private subnet), provides native support for SQL Server Agent to run scheduled scripts, and is a fully managed Platform-as-a-Service (PaaS) that handles operating system updates and automated backups.

Adım Adım Çözüm

1
Analyze the management overhead and hosting model requirements.
Identify that the solution must minimize OS-level management tasks, directing the choice toward a Platform-as-a-Service (PaaS) option like Azure SQL Database or Azure SQL Managed Instance rather than SQL Server on Azure VMs.
This narrows down the options to fully managed cloud database offerings.
2
Evaluate database feature requirements for scheduling.
Identify the requirement for native SQL Server Agent to run scheduled scripts.
Azure SQL Database (Single Database and Elastic Pool) does not support native SQL Server Agent, which requires either SQL Server on Azure VMs or Azure SQL Managed Instance.
3
Assess network isolation and configuration requirements.
Determine that Azure SQL Managed Instance supports direct deployment into a private subnet of a Virtual Network (VNet injection) and meets all the operational and feature requirements.
This confirms Azure SQL Managed Instance is the only service that satisfies all network, feature compatibility, and management constraints.

Anahtar Kavram

Selecting the appropriate Azure SQL deployment option based on SQL Server feature compatibility (SQL Server Agent), network isolation (VNet injection), and administrative overhead constraints.
Tahmini Süre:1m 30s
Soru 202Soru

You are designing an identity and access management solution for a company. Match each security requirement to the most appropriate Microsoft Entra ID or Conditional Access feature.

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

Öğeler

Require administrative users to request temporary elevation to active roles and verify their identity via MFA prior to managing Azure resources.
Bypass MFA requirements for users who are accessing cloud resources from the corporate office's public IP range.
Block access to cloud applications for users connecting from specific geographical locations outside of the corporate footprint.
Enforce multifactor authentication (MFA) only when a user's sign-in attempt shows a medium or high risk level.

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

The security requirements are mapped as follows: Role activation settings in Entra ID Privileged Identity Management (PIM) are used to enforce MFA and approval for temporary admin elevation. Trusted IP Named Locations in Conditional Access are used to bypass MFA for corporate networks. Geography-based Named Locations with block controls in Conditional Access are used to block access from unauthorized countries. Entra ID Protection Sign-in risk policies are used to enforce MFA dynamically based on sign-in risk levels.
The correct pairings align specific identity and security controls with Entra ID features. Enabling PIM role activation settings manages temporary admin privilege elevation. Marking corporate IP ranges as trusted Named Locations enables location-based MFA bypass in Conditional Access. Creating geographic Named Locations with block controls restricts unauthorized international sign-ins. Applying Entra ID Protection policies secures sign-ins based on calculated risk thresholds.

Adım Adım Çözüm

1
Analyze administrative elevation and MFA requirements.
Identify that temporary elevation and MFA before administrative actions map to Entra ID Privileged Identity Management (PIM).
PIM is designed to manage, control, and monitor access to important resources, including requiring approval and MFA for active role assignment.
2
Analyze trusted network bypass requirements.
Identify that bypassing MFA using corporate office IP ranges maps to Conditional Access with IP-based trusted Named Locations.
Conditional Access policies can exclude trusted locations (defined by IP ranges) from MFA requirements.
3
Analyze geographical restriction requirements.
Identify that blocking access from unauthorized countries maps to Conditional Access with geography-based Named Locations.
Geography-based Named Locations define country borders, which can be referenced in Conditional Access policies to deny or block access.
4
Analyze risk-based authentication requirements.
Identify that medium or high sign-in risk triggers map to Entra ID Protection policies.
Entra ID Protection evaluates sign-in telemetry and enforces controls like MFA or password changes based on user or sign-in risk levels.

Anahtar Kavram

Microsoft Entra ID Authentication and Conditional Access
Tahmini Süre:1m 30s
Soru 203Soru

A media streaming company is planning to migrate its on-premises backend relational databases to Azure. The migration involves two systems:

* System 1: A legacy content management system that relies on SQL Server Agent for scheduling metadata updates, requires SQL Server Common Language Runtime (CLR) integration, and requires cross-database transactions.
* System 2: An on-demand user analytics database that experiences highly unpredictable traffic spikes but is completely idle during off-peak hours. This database must remain highly available even if an entire Azure Availability Zone within the region experiences an outage.

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

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

Cevabı ve açıklamayı göster

Cevap: Azure SQL Managed Instance for System 1; Azure SQL Database Serverless with zone-redundant configuration for System 2

Cevap

The correct design includes Azure SQL Managed Instance for System 1 and Azure SQL Database Serverless with zone-redundant configuration for System 2.
The correct options are the recommendations for Azure SQL Managed Instance and Azure SQL Database Serverless with zone-redundancy. Azure SQL Managed Instance is designed for migrating on-premises SQL Server instances with minimal changes, supporting instance-level features like SQL Server Agent and CLR. Azure SQL Database Serverless satisfies the requirement to auto-scale and pause during inactive periods to minimize costs, and configuring it with zone-redundancy ensures high availability across zone failures.

Adım Adım Çözüm

1
Analyze System 1 requirements.
System 1 requires SQL Server Agent, CLR, and cross-database transactions.
These legacy features are not supported in Azure SQL Database single database or elastic pools, but are fully supported in Azure SQL Managed Instance.
2
Analyze System 2 requirements.
System 2 requires auto-scaling, auto-pausing (serverless compute tier), and resiliency to availability zone outages (zone-redundancy).
Azure SQL Database Serverless with zone-redundancy meets the auto-pause and zone-resiliency requirements.
3
Select the optimal options that minimize administrative overhead.
Azure SQL Managed Instance for System 1 and Azure SQL Database Serverless with zone-redundant configuration for System 2.
Both are platform-as-a-service (PaaS) offerings that satisfy all requirements with lower management overhead than SQL Server on Azure VMs.

Anahtar Kavram

Relational database tier selection and high availability design in Azure.
Soru 204Soru

A financial technology company is planning the security model for an Azure Storage account that holds sensitive transaction logs. The design must satisfy the following security requirements:

* Developers must only obtain administrative access to the storage account during active troubleshooting sessions, with all access requests requiring approval and auditing.
* An external compliance auditor requires read-only access to a specific container for 90 days, with the ability to revoke this access immediately at any time without changing account keys.
* Internal applications must be granted read access to the transaction logs using a scalable role assignment model that minimizes administrative overhead.

Which two security controls should you recommend to meet these requirements?

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

Cevabı ve açıklamayı göster

Cevap: Utilize a stored access policy on the container to generate and manage the Shared Access Signature (SAS) token for the external auditor.; Configure Azure AD Privileged Identity Management (PIM) to make the developer security group eligible for the Storage Account Contributor role.

Cevap

Utilize a stored access policy on the container to generate and manage the Shared Access Signature (SAS) token for the external auditor, and configure Azure AD Privileged Identity Management (PIM) to make the developer security group eligible for the Storage Account Contributor role.
The correct options are utilizing a stored access policy for SAS token management and configuring PIM eligible assignments for the developer group. A stored access policy provides fine-grained control and revocation capability over SAS tokens. PIM eligible assignments ensure that developers only obtain administrative privileges when they explicitly request activation during troubleshooting, which requires approval and generates audit logs.

Adım Adım Çözüm

1
Address the external auditor's temporary, revocable access requirement.
Identify that a stored access policy allows modification or revocation of the Shared Access Signature (SAS) token's permissions and expiration date without rotating the master storage account keys.
This directly satisfies the requirement for a 90-day revocable access window.
2
Address the developers' temporary administrative access requirement.
Select Microsoft Entra ID Privileged Identity Management (PIM) and configure eligible (just-in-time) assignments requiring approvals.
This satisfies the requirement that administrative access is only active during troubleshooting sessions and is fully audited.
3
Evaluate the scalability and administrative overhead of role assignments.
Discard options suggesting direct user-to-role assignment, ensuring RBAC is managed via groups or eligible PIM roles.
Direct assignments fail the best practice of scalable governance.

Anahtar Kavram

Data Storage Security and Access Control
Soru 205Soru

A multinational media production company is restructuring its delegation of administrative privileges in Azure for temporary regional media production teams. The design must satisfy the following security and compliance requirements:
- External production managers must only be granted administrative access to their respective regional subscription resources for the duration of a project, not exceeding 90 days.
- Activation of administrative access must require multi-factor authentication (MFA) and approval from the internal IT Security Lead.
- All administrative roles must be assigned using groups rather than individual user assignments to facilitate scalable auditing.
- External managers must not possess permanent active standing privileges.

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

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

Cevabı ve açıklamayı göster

Cevap: Assign the required Azure RBAC roles to a role-assignable Microsoft Entra group, and configure the external managers as eligible members of this group in Privileged Identity Management (PIM) for Groups.; Configure a PIM for Groups activation policy for the group that requires multi-factor authentication (MFA) and approval from the IT Security Lead.

Cevap

Assign the required Azure RBAC roles to a role-assignable group, configure the users as eligible in PIM for Groups, and define a PIM activation policy that enforces MFA and approval from the IT Security Lead.
To meet all constraints, you must design a solution using Privileged Identity Management (PIM) for Groups. By creating a role-assignable group and assigning the Azure RBAC roles to the group itself, you meet the group-based assignment requirement. By designating the external managers as eligible members, they do not have permanent standing access. To enforce the approval and MFA requirements, you must define an activation policy within PIM for Groups that triggers these checks upon membership activation.

Adım Adım Çözüm

1
Evaluate role assignment constraints.
Identified that roles must be assigned using groups rather than individual assignments to facilitate auditing.
This rules out direct assignment to user accounts in PIM for Azure Resources.
2
Address the requirement for no permanent active standing privileges.
Determine that external managers should be configured as eligible members rather than active members of the group.
Eligible membership ensures they only have access when they explicitly activate it, preventing permanent standing access.
3
Enforce JIT activation controls.
Configure a PIM for Groups activation policy to require MFA, justification, and IT Security Lead approval.
This satisfies the requirement that activation of administrative access must require MFA and approval before access is granted.

Anahtar Kavram

Privileged Identity Management (PIM) for Groups allows governance of role-assignable groups, enabling just-in-time elevation of group memberships that carry Azure RBAC roles without granting permanent standing access or violating group-based assignment best practices.
Soru 206Soru

An organization named CloudCrest Logistics is designing a secure hybrid identity and access control solution using Microsoft Entra ID. The solution must support synchronization of user identities from their on-premises Active Directory Domain Services (AD DS) environment. The organization has the following requirements:
- Users must be able to sign in using their on-premises passwords, and authentication must occur on-premises to satisfy regulatory compliance. If the on-premises connection fails, users must temporarily be able to sign in via cloud-based authentication as a backup.
- Multi-factor authentication (MFA) must be enforced for all users accessing the Azure portal, except for a dedicated glass-breaker emergency access account which must be excluded to prevent tenant lockout.

Which two configurations should you include in the design?

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

Cevabı ve açıklamayı göster

Cevap: Configure Microsoft Entra Connect to use Pass-through Authentication (PTA) as the primary sign-in method and enable Password Hash Synchronization (PHS) as a backup.; Configure a Conditional Access policy targeting the Microsoft Azure Management app that requires multi-factor authentication, and explicitly exclude a dedicated emergency access account from this policy.

Cevap

To meet the requirements, you should configure Pass-through Authentication (PTA) with Password Hash Synchronization (PHS) as a backup, and configure a Conditional Access policy requiring multi-factor authentication while excluding the emergency access account.
The correct configurations are to use Pass-through Authentication (PTA) with Password Hash Synchronization (PHS) as a backup, and to configure a Conditional Access policy requiring multi-factor authentication while excluding the emergency access account. PTA ensures on-premises authentication occurs for compliance, while enabling PHS as a backup allows users to authenticate in the cloud if the on-premises infrastructure is unavailable. Excluding the emergency access account from the MFA policy prevents tenant lockout in case of MFA service disruptions.

Adım Adım Çözüm

1
Analyze authentication requirements to determine the appropriate hybrid identity configuration.
Identify that Pass-through Authentication (PTA) provides on-premises validation to meet compliance, while Password Hash Synchronization (PHS) serves as a cloud-based backup.
Regulatory compliance requires on-premises password validation, but business continuity demands a cloud-based authentication backup during outages.
2
Analyze access control and resiliency requirements for administration.
Determine that a Conditional Access policy should enforce multi-factor authentication (MFA) for Azure portal access, with an exclusion rule for the emergency access account.
Excluding the emergency access account is a critical resiliency best practice to prevent permanent tenant lockout during MFA service disruptions.

Anahtar Kavram

Microsoft Entra ID hybrid authentication and Conditional Access design
Soru 207Soru

A pharmaceutical research firm is deploying a multi-region clinical data analysis platform inside a single Microsoft Entra tenant. The platform utilizes multiple Azure subscriptions. You must design an administrative access and resource compliance framework to meet the following requirements:
- A group of external audit partners needs read-only access to a specific resource group containing data processing logs.
- Internal platform engineers need the ability to perform high-privilege operations at the subscription root for ad-hoc emergency troubleshooting, but this access must not be permanently active.
- To maintain security standards, all newly provisioned virtual machines must automatically have the dependency agent installed without blocking deployment or requiring engineer intervention.

Which of the following configurations represents the most appropriate strategy to implement these requirements?

Cevabı ve açıklamayı göster

Cevap: Establish a Microsoft Entra ID security group for the audit partners and grant this group Reader permissions at the resource group level. Set up the troubleshooting permissions in Privileged Identity Management (PIM) so the platform engineers are eligible for just-in-time activation. Configure an Azure Policy with the DeployIfNotExists effect to automatically install the dependency agent on new virtual machines.

Cevap

Establish a Microsoft Entra ID security group for the audit partners and grant this group Reader permissions at the resource group level. Set up the troubleshooting permissions in Privileged Identity Management (PIM) so the platform engineers are eligible for just-in-time activation. Configure an Azure Policy with the DeployIfNotExists effect to automatically install the dependency agent on new virtual machines.
Assigning access to a security group rather than individuals simplifies administration and aligns with standard identity best practices. Using eligible PIM assignments ensures high-privilege access is restricted to on-demand, just-in-time activation, preventing persistent access vulnerabilities. The DeployIfNotExists policy effect automates the deployment of the dependency agent on new virtual machines without blocking user operations, which satisfies the continuous compliance requirement.

Adım Adım Çözüm

1
Identify the governance requirements for access delegation, privilege level, and resource compliance.
The audit partners need read access to a specific scope, the engineers need temporary root-level privileges, and new virtual machines require automatic agent installation.
Establishes a baseline for mapping requirements to Azure governance tools.
2
Evaluate the delegation method for the external audit partners.
The design must leverage a Microsoft Entra ID group mapped to the Reader role on the target resource group, avoiding direct user assignments.
Ensures compliance with group-based access control guidelines, reducing administrative overhead.
3
Determine the temporary privilege configuration for engineers and the automation method for agent installation.
Engineers must be configured as eligible in Privileged Identity Management (PIM), and the agent must be deployed using an Azure Policy with a DeployIfNotExists effect.
Maintains least privilege using just-in-time access and implements automated remediation rather than blocking deployments.

Anahtar Kavram

Azure RBAC, PIM JIT activation, and Azure Policy remediation effects represent key pillars of subscription governance.
Tahmini Süre:1m 30s
Soru 208Soru

You are designing the storage infrastructure for a hybrid application suite in Azure. The design must accommodate the following two data requirements:

1. Data Ingestion: An external service will write large volumes of telemetry data via REST APIs. This data must remain accessible even in the event of a complete Azure region outage.
2. Database Workspace: A transaction processing database hosted on Azure Virtual Machines requires high-throughput data volumes that can sustain at least 16,00016,000 IOPS and sub-millisecond latency.

Which two storage solutions should you recommend? (Select TWO).

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

Cevabı ve açıklamayı göster

Cevap: Azure Blob Storage configured with Geo-Redundant Storage (GRS); Premium SSD v2 Managed Disks

Cevap

Azure Blob Storage configured with Geo-Redundant Storage (GRS) and Premium SSD v2 Managed Disks
The correct storage solutions are Azure Blob Storage with Geo-Redundant Storage (GRS) and Premium SSD v2 Managed Disks. Azure Blob Storage with GRS ensures that the ingested telemetry remains available in the event of a primary region outage while supporting REST APIs. Premium SSD v2 Managed Disks provide the performance required by the database workspace, offering sub-millisecond latency and up to 80,00080,000 IOPS.

Adım Adım Çözüm

1
Analyze the ingestion requirement for the external service.
The requirement specifies REST API access and the ability to survive a complete regional outage.
Azure Blob Storage supports HTTP/REST endpoints. To protect against a regional outage, Geo-Redundant Storage (GRS) is necessary as it replicates data asynchronously to a paired secondary region.
2
Analyze the database performance requirement.
The database needs volumes that can support at least 16,00016,000 IOPS and maintain sub-millisecond latency.
Premium SSD v2 managed disks are designed for latency-sensitive, high-performance workloads, supporting up to 80,00080,000 IOPS and sub-millisecond response times.
3
Evaluate the non-compliant options.
LRS storage accounts and Standard SSD managed disks are eliminated due to lack of geo-redundancy and high latency/low IOPS respectively.
Eliminating invalid configurations ensures the final design meets both disaster recovery and performance specifications.

Anahtar Kavram

Selecting Azure storage and disk types based on regional redundancy needs and performance requirements.
Tahmini Süre:2m 0s
Soru 209Soru

Zephyr Logistics is designing a hybrid identity and multi-tenant collaboration solution. The company has an on-premises Active Directory Domain Services (AD DS) forest with 82008{}200 users. You are tasked with selecting the appropriate identity integration and collaboration technologies to satisfy the company's security, compliance, and availability requirements.

Match each business requirement on the left to the correct Microsoft Entra ID or hybrid identity technology on the right.

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

Öğeler

Authenticate users in the cloud even during an on-premises network outage, minimizing on-premises infrastructure.
Authenticate users against on-premises Active Directory in real-time without storing credential hashes in the cloud.
Authenticate users using existing on-premises smart cards, keeping all authentication policies within the corporate network perimeter.
Allow external partner users to securely access corporate applications using their own organizational identity providers.

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

Authenticate users in the cloud during outages matches Password Hash Synchronization (PHS). Authenticate users in real-time without cloud hashes matches Pass-through Authentication (PTA). Authenticate users using smart cards within the perimeter matches Active Directory Federation Services (AD FS). Allow partner users to access resources using their own identity provider matches Microsoft Entra B2B Collaboration.
The correct matches align each scenario with its primary architectural capability. Password Hash Synchronization (PHS) offers high availability by allowing Entra ID to authenticate users independently of on-premises connectivity. Pass-through Authentication (PTA) provides real-time local validation without storing hashes in the cloud. Active Directory Federation Services (AD FS) handles specialized on-premises authentication requirements like smart card/certificate validation and local perimeter policy enforcement. Microsoft Entra B2B Collaboration facilitates secure, external partner access by trusting their home identity provider.

Adım Adım Çözüm

1
Analyze the requirement for outage resilience and minimal on-premises footprint.
Password Hash Synchronization (PHS) is selected as it offloads authentication to Entra ID and has zero runtime dependency on the on-premises environment once synced.
This guarantees sign-in availability during network or on-premises server outages.
2
Analyze the requirement for real-time authentication without storing credential hashes in the cloud.
Pass-through Authentication (PTA) is selected because authentication requests are forwarded to local agents on-premises, and no credential hashes are stored in Microsoft Entra ID.
This satisfies strict organizational compliance rules that forbid cloud credential storage.
3
Analyze the requirement for on-premises smart card authentication and local policy management.
Active Directory Federation Services (AD FS) is selected because federation hands over the authentication handshake to the on-premises directory, permitting the use of smart cards and certificate-based auth.
This keeps authentication traffic and security policy enforcement within the corporate perimeter.
4
Analyze the requirement for partner collaboration using their own identity providers.
Microsoft Entra B2B Collaboration is selected as it allows guest users to use their existing external credentials to sign in, reducing administrative overhead.
This meets the multi-tenant collaboration requirements securely and efficiently.

Anahtar Kavram

Designing hybrid identity authentication methods (PHS, PTA, AD FS) and multi-tenant collaboration strategies (Entra B2B) based on availability, security, and administrative requirements.
Soru 210Soru

A healthcare organization is designing a shared storage solution to host sensitive patient records and medical imaging configuration files. The solution will support a clinical application running on multiple Azure Virtual Machines. The storage design must meet the following requirements:
- Allow simultaneous access from multiple Virtual Machines using the SMB protocol.
- Integrate with the organization's on-premises Active Directory Domain Services (AD DS) to enforce NTFS-grade access control lists (ACLs).
- Provide sub-millisecond latency for configuration file metadata operations.
- Ensure that the shared data remains available if a single datacenter zone within the primary Azure region goes offline.
- Ensure any external diagnostic services are granted access to specific files via a token that can be easily revoked immediately if compromised.

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 storage account that uses Zone-Redundant Storage (ZRS).; Create an Azure Files share in a Premium performance storage account.

Cevap

To meet the performance, availability, and protocol requirements, you must create a Premium performance storage account configured with Zone-Redundant Storage (ZRS), and host the share within it.
Creating a Premium performance storage account ensures that Azure Files can deliver the sub-millisecond latency required by the clinical application's metadata operations. Configuring the storage account with Zone-Redundant Storage (ZRS) ensures that the synchronous copies are spread across three distinct availability zones, allowing the share to remain fully operational if a single zone experiences an outage.

Adım Adım Çözüm

1
Evaluate protocol and performance requirements.
The requirement for SMB access, NTFS ACLs, and AD DS integration points to Azure Files. The requirement for sub-millisecond latency requires SSD-backed Premium Azure Files, as Standard Azure Files (HDD-based) does not guarantee this level of performance.
This narrows the service choice to Premium Azure Files.
2
Evaluate high availability and redundancy requirements.
The requirement to survive a datacenter zone outage necessitates Zone-Redundant Storage (ZRS). Locally Redundant Storage (LRS) is insufficient as it is confined to a single datacenter.
This determines the redundancy configuration for the storage account hosting the share.
3
Verify feature compatibility.
Azure Files Premium tier supports ZRS and integrates with on-premises AD DS for SMB access.
Ensures the selected components work together seamlessly.

Anahtar Kavram

Selecting appropriate performance tiers (Premium vs Standard) and redundancy configurations (ZRS vs LRS) for Azure Files workloads requiring domain-joined authentication and low latency.
Soru 211Soru

An organization named Contoso Pharmaceuticals is designing an identity security strategy for its Microsoft Entra ID tenant. The organization requires that all users with administrative roles use multi-factor authentication (MFA) when accessing the Azure portal. The organization also needs to ensure that administrators are not permanently locked out of the tenant in the event of a Microsoft Entra ID MFA service outage. Which design strategy should the architect recommend?

Cevabı ve açıklamayı göster

Cevap: Implement a Conditional Access policy requiring multi-factor authentication for all administrators, while explicitly excluding a dedicated, cloud-only emergency access account that is monitored for sign-in activity.

Cevap

Implement a Conditional Access policy requiring multi-factor authentication for all administrators, while explicitly excluding a dedicated, cloud-only emergency access account that is monitored for sign-in activity.
The correct strategy is to create a Conditional Access policy requiring MFA for all administrative roles, but explicitly exclude a dedicated emergency access (break-glass) account. This cloud-only account must bypass MFA so it remains accessible during an outage. Continuous monitoring and alerting must be configured to detect any sign-in attempts using this account, mitigating the risk of MFA bypass.

Adım Adım Çözüm

1
Analyze the tenant security requirements and the risk of administrator lockout due to MFA service outages or misconfigurations.
Identify that a fallback mechanism (break-glass account) is necessary to ensure administrative access is maintained.
Microsoft Entra ID Conditional Access policies apply to all targeted users unless explicitly excluded, which can lead to tenant lockout if MFA fails.
2
Design the emergency access account strategy.
Specify a dedicated, cloud-only account that does not sync from on-premises Active Directory and is excluded from the MFA Conditional Access policy.
Cloud-only accounts do not depend on on-premises sync health, and excluding them from the policy ensures they can authenticate without MFA during an outage.
3
Establish auditing and alert mechanisms for the emergency access account.
Configure Azure Monitor logs and Microsoft Entra ID alerts to trigger whenever the emergency access account is used to sign in.
Since the emergency access account bypasses MFA, its use must be highly restricted, audited, and monitored to prevent misuse.

Anahtar Kavram

Designing for resiliency in Microsoft Entra ID Authentication and Conditional Access by implementing monitored emergency access accounts.
Tahmini Süre:1m 30s
Soru 212Soru

A healthcare provider plans to share medical imaging files stored in an Azure Blob Storage container with an external research laboratory. The data sharing agreement specifies the following requirements:
- The laboratory must have read-only access for a duration of exactly 45 days.
- Access must be limited to the laboratory's public outbound IP address range.
- The provider must have the ability to revoke access immediately if a security breach is suspected, without regenerating the storage account keys or affecting other integrations.

Which access control method should you recommend to meet these requirements?

Cevabı ve açıklamayı göster

Cevap: Define a stored access policy on the container that specifies the read permission and expiration, and then generate a service SAS token that references this policy and contains the IP address restriction.

Cevap

Define a stored access policy on the container that specifies the read permission and expiration, and then generate a service SAS token that references this policy and contains the IP address restriction.
The correct option provides a secure way to manage temporary access. By defining the permissions (read) and duration (45 days) in a stored access policy, the administrator can revoke access instantly by modifying or deleting the policy without needing to regenerate the storage account keys. Adding the IP address constraint to the generated service SAS token ensures that access is restricted to the laboratory's specific network.

Adım Adım Çözüm

1
Analyze the requirements for access duration, revocation, and IP restriction.
The solution must support read-only permissions, a 45-day window, immediate revocation without key regeneration, and IP-based access limits.
This establishes the constraints that rule out ad-hoc SAS tokens and standard permanent RBAC assignments.
2
Evaluate the mechanism for instant revocation of Shared Access Signatures.
A stored access policy on the container can be deleted or modified, immediately invalidating any SAS tokens associated with it.
Ad-hoc SAS tokens cannot be revoked individually; only regenerating the storage account keys can revoke them, which violates the requirement to avoid impacting other integrations.
3
Determine where the IP address restriction should be applied.
The service SAS token generated from the stored access policy can include the allowed IP address range using the 'sip' parameter.
This satisfies the requirement to restrict access to the laboratory's public outbound IP range while keeping permissions managed by the stored policy.

Anahtar Kavram

Stored Access Policies vs. Ad-hoc SAS and RBAC for Secure Temporary Storage Access
Soru 213Soru

A global pharmaceutical corporation is designing an identity governance and privileged access solution to manage external clinical researchers who require temporary, administrative access to Azure Machine Learning workspaces in a production subscription. The researchers must only acquire permissions when active, and their access must be automatically re-evaluated monthly to ensure compliance with data protection laws. All administrative activities must require Multi-Factor Authentication (MFA), but the organization's break-glass emergency accounts must never be locked out by these requirements.

Which configuration should you recommend to meet these requirements with the least administrative overhead?

Cevabı ve açıklamayı göster

Cevap: Create a Microsoft Entra ID security group for the researchers, assign the group as eligible for the Contributor role in Privileged Identity Management (PIM) for Azure resources, require MFA during activation, configure a monthly PIM access review for the role assignment, and ensure the emergency access accounts are excluded from the tenant-wide Conditional Access policy that enforces MFA.

Cevap

Create a Microsoft Entra ID security group for the researchers, assign the group as eligible for the Contributor role in Privileged Identity Management (PIM) for Azure resources, require MFA during activation, configure a monthly PIM access review for the role assignment, and ensure the emergency access accounts are excluded from the tenant-wide Conditional Access policy that enforces MFA.
The correct configuration utilizes a security group for administrative tasks to minimize overhead. It configures the group assignment in PIM as eligible to guarantee just-in-time access, requires MFA during the activation flow to secure access, and runs monthly access reviews to fulfill compliance requirements. Finally, it excludes emergency access accounts from Conditional Access policies to prevent lockout.

Adım Adım Çözüm

1
Define a Microsoft Entra ID security group containing the clinical researchers.
A single administrative unit is created to represent the external researchers.
Assigning roles to groups instead of individual users is an Azure best practice for scalability and lower overhead.
2
Assign the security group as eligible for the required Contributor role in PIM for Azure resources.
Researchers do not have standing privileges and must request activation when they need to work.
This implements the principle of least privilege through just-in-time (JIT) access governance.
3
Configure the PIM role activation settings to require MFA and set up a monthly PIM access review.
Users are verified via MFA during JIT activation, and their eligibility is re-evaluated automatically on a monthly schedule.
This secures the JIT activation flow and meets compliance requirements by automating access reviews.
4
Exclude the emergency access (break-glass) accounts from tenant-wide Conditional Access policies that enforce MFA.
Emergency accounts can still sign in during an MFA service disruption.
Excluding emergency accounts from strict Conditional Access policies prevents tenant lockout during system failures.

Anahtar Kavram

Designing privileged access governance using Microsoft Entra Privileged Identity Management (PIM), group-based RBAC, and emergency account exclusions.
Tahmini Süre:2m 30s
Soru 214Soru

A company is designing a data analytics solution on Azure to support a team of data scientists who perform infrequent, ad-hoc exploratory queries on a 50 TB50\text{ TB} dataset stored in Azure Data Lake Storage Gen2. New data is loaded in batches every 6 hours6\text{ hours}, adding approximately 500 GB500\text{ GB} daily. The exploratory queries must execute within 30 seconds30\text{ seconds}. The entire architecture must remain resilient to a regional disaster, ensuring that both data and analytical query capabilities can be restored or accessed in a secondary region. Additionally, all access to the data lake must be secure, easily revocable, and audit-compliant, avoiding long-lived static credentials. You need to design the solution while minimizing operational overhead and idle resource costs. Which storage and analytical query configuration should you recommend?

Cevabı ve açıklamayı göster

Cevap: Azure Synapse Analytics serverless SQL pools querying Azure Data Lake Storage Gen2 configured with Geo-Redundant Storage (GRS), using Microsoft Entra ID integration for authentication.

Cevap

The configuration using Azure Synapse Analytics serverless SQL pools querying Azure Data Lake Storage Gen2 configured with Geo-Redundant Storage (GRS), using Microsoft Entra ID integration for authentication.
The configuration using serverless SQL pools with Geo-Redundant Storage (GRS) and Microsoft Entra ID meets all requirements. Serverless SQL pools provide an on-demand query engine that charges only for data processed, minimizing costs for infrequent ad-hoc queries. GRS ensures data is replicated to a secondary region to survive regional outages. Microsoft Entra ID integration ensures secure, identity-based access control without key management overhead.

Adım Adım Çözüm

1
Analyze the query frequency and cost tradeoffs.
The requirement specifies infrequent, ad-hoc queries. Dedicated resources (Dedicated SQL Pool) incur continuous idle costs, whereas serverless SQL pools charge per TB of data processed, aligning cost directly with usage.
To minimize idle resource costs and operational overhead.
2
Determine the storage redundancy model based on disaster recovery requirements.
Locally Redundant Storage (LRS) is restricted to a single region. Geo-Redundant Storage (GRS) replicates data asynchronously to a secondary region, ensuring disaster resilience.
To satisfy the requirement that the architecture must survive a regional outage.
3
Evaluate the authentication mechanism against security policies.
Microsoft Entra ID provides identity-based, auditable access control that is easily revocable. Long-lived SAS tokens represent a security vulnerability because they are static and hard to revoke.
To ensure audit compliance and avoid static long-lived credentials.

Anahtar Kavram

Selecting analytical query engines and storage redundancy configurations to balance disaster recovery, security compliance, and consumption-based cost models.
Soru 215Soru

An enterprise is planning to grant a third-party auditing firm temporary read-only access to financial reports stored in an Azure Blob Storage container for 14 days. The access must be easily revocable at any time during this period without affecting other storage access methods. Additionally, internal security administrators require temporary elevated access to manage the storage account settings, but only when actively performing audit tasks. Which of the following security and access control configurations 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 a Service Shared Access Signature (SAS) token associated with the policy for the external audit partners.; Configure Microsoft Entra Privileged Identity Management (PIM) to make the internal security administrators eligible for the Storage Blob Data Owner role.

Cevap

Configure a Stored Access Policy on the blob container and generate a Service Shared Access Signature (SAS) token associated with the policy for the external audit partners, and configure Microsoft Entra Privileged Identity Management (PIM) to make the internal security administrators eligible for the Storage Blob Data Owner role.
The correct solution involves using a Stored Access Policy paired with a Service SAS to facilitate instant revocation, and utilizing Microsoft Entra PIM with eligible role assignments to implement just-in-time access for internal administrators.

Adım Adım Çözüm

1
Evaluate the requirement for temporary, revocable access to the blob container for the external auditing firm.
Identify that using a Service SAS linked to a Stored Access Policy on the container allows instant revocation by changing or deleting the policy.
Ad-hoc SAS tokens cannot be individually revoked without rotating storage account keys, making a stored access policy necessary.
2
Evaluate the requirement for internal security administrators to have temporary elevated access to storage account settings.
Identify that Microsoft Entra Privileged Identity Management (PIM) should be configured to make the administrators eligible for the role rather than permanently assigned.
This enforces the principle of least privilege by requiring justification and approvals to activate the role for a limited time.

Anahtar Kavram

Securing data storage access using Stored Access Policies for SAS revocation and Microsoft Entra PIM for just-in-time administrative access control.
Tahmini Süre:2m 0s
Soru 216Soru

A company plans to migrate an on-premises inventory management database system to Azure. The system requires support for SQL Server Agent to run automated tasks and native cross-database queries. The database must remain highly available and survive the outage of an entire Azure availability zone. The company wants to minimize the administrative overhead of managing the underlying operating system, patching, and backups. Which Azure SQL deployment option should you choose?

Cevabı ve açıklamayı göster

Cevap: Azure SQL Managed Instance with zone redundancy

Cevap

Azure SQL Managed Instance with zone redundancy
The correct option is Azure SQL Managed Instance with zone redundancy because it satisfies the need for instance-level features (SQL Server Agent and cross-database queries) while minimizing administrative overhead by offering a fully managed PaaS model. Configuring it with zone redundancy ensures the database can survive an availability zone outage.

Adım Adım Çözüm

1
Evaluate feature requirements for SQL Server Agent and cross-database queries.
Identify that instance-level capabilities are required, which rules out Azure SQL Database single database and elastic pool.
Azure SQL Database single database and elastic pools do not natively support SQL Server Agent or cross-database queries.
2
Assess administrative overhead requirements.
Exclude SQL Server on Azure Virtual Machines.
SQL Server on Azure Virtual Machines is an IaaS option that requires the operations team to handle OS patching, database backups, and high availability, violating the requirement to minimize administrative overhead.
3
Verify high availability and zone resilience requirements.
Select Azure SQL Managed Instance configured with zone redundancy.
Azure SQL Managed Instance supports zone redundancy to ensure application uptime during an availability zone outage while providing fully managed backups and patching.

Anahtar Kavram

Selecting appropriate Azure SQL relational database deployment options based on legacy feature support, administrative overhead, and high availability constraints.
Tahmini Süre:1m 30s
Soru 217Soru

An organization named Apex Global Finance is designing a secure identity and access management solution using Microsoft Entra ID. The solution must meet the following requirements:
- Require multi-factor authentication (MFA) for all standard administrative users.
- Ensure that administrators only hold privileged permissions when they are actively performing administrative tasks.
- Minimize the risk of a tenant lockout if there is a widespread outage of the Azure MFA service.

Which two of the following configurations should you include in the identity design? (Select TWO).

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

Cevabı ve açıklamayı göster

Cevap: Create two cloud-only emergency access accounts that are explicitly excluded from all Conditional Access policies that require MFA.; Configure standard administrative accounts as eligible for roles in Microsoft Entra Privileged Identity Management (PIM).

Cevap

To secure the administrative access while preventing lockout and minimizing standing privileges, the solution must include: creating cloud-only emergency access accounts that are excluded from MFA Conditional Access policies, and configuring standard administrative accounts as eligible for roles in Privileged Identity Management (PIM).
Excluding cloud-only emergency access accounts from MFA requirements in Conditional Access policies ensures a path into the tenant if the MFA service is unavailable. Configuring standard administrative accounts as eligible in Privileged Identity Management (PIM) enforces just-in-time access, which ensures roles are only activated when administrative tasks are performed.

Adım Adım Çözüm

1
Evaluate the lockout mitigation requirement.
Identify the need for emergency access (glass-breaker) accounts that bypass MFA requirements to ensure entry during outages.
If an MFA service outage occurs and all accounts require MFA, administrators will be locked out. Excluding specific emergency accounts prevents this scenario.
2
Evaluate the requirement for dynamic privilege assignment.
Implement Privileged Identity Management (PIM) with eligible assignments rather than permanently active assignments.
Eligible assignments require administrators to explicitly activate their roles, providing permissions only when actively performing tasks (just-in-time access).

Anahtar Kavram

Microsoft Entra ID emergency access and just-in-time access strategies using Conditional Access exclusions and PIM eligible assignments.
Tahmini Süre:2m 0s
Soru 218Soru

An enterprise is designing a subscription governance and access model for a new business unit. The unit will use three Azure subscriptions managed under a single parent management group named Corp-Unit-MG.

You must meet the following requirements:
1. Allow a team of database administrators (DBAs) to manage all Azure SQL databases across all three subscriptions.
2. Ensure that any new Azure SQL Database deployed in these subscriptions is automatically configured to send diagnostic logs to a central Log Analytics workspace, without blocking deployment or requiring manual configuration by the DBAs.
3. Minimize administrative overhead and adhere to the principle of least privilege.

Which solution should you recommend?

Cevabı ve açıklamayı göster

Cevap: Create a Microsoft Entra ID security group containing all DBAs. Assign the SQL DB Contributor role to the group at the Corp-Unit-MG management group scope. Assign an Azure Policy with a DeployIfNotExists effect at the Corp-Unit-MG scope to deploy the database diagnostic settings.

Cevap

Create a Microsoft Entra ID security group containing all DBAs, assign the SQL DB Contributor role to the group at the management group scope, and assign a DeployIfNotExists Azure Policy at the management group scope to automatically deploy the database diagnostic settings.
The correct solution leverages a Microsoft Entra ID security group assigned the SQL DB Contributor role at the parent management group level, combined with a DeployIfNotExists Azure Policy. Using a security group simplifies identity lifecycle management, and assigning it at the management group scope ensures inheritance across all subscriptions. The DeployIfNotExists policy automatically configures diagnostic settings to send logs to the Log Analytics workspace upon creation without blocking the database deployment.

Adım Adım Çözüm

1
Select the appropriate RBAC identity assignment method.
Identify that the DBAs should be placed in a Microsoft Entra ID security group instead of assigning roles to individual accounts to minimize overhead.
Direct user assignments do not scale and violate Azure subscription governance best practices.
2
Determine the optimal RBAC scope and role.
Assign the SQL DB Contributor role to the security group at the parent management group (Corp-Unit-MG) scope.
Assigning at the management group level ensures automatic inheritance to all three subscriptions, and the SQL DB Contributor role enforces least privilege.
3
Identify the correct Azure Policy effect to enforce auditing.
Select the DeployIfNotExists policy effect instead of a Deny effect.
The DeployIfNotExists effect automatically applies the diagnostic settings during or after deployment without interrupting or blocking the deployment itself.

Anahtar Kavram

Azure RBAC inheritance and automated subscription governance using DeployIfNotExists policies.
Tahmini Süre:2m 0s
Soru 219Soru

You are designing the data tier for a global telemetry platform that tracks 500,000500,000 container shipments. Sensor devices upload high-frequency environmental metrics to Azure Blob Storage, while metadata and real-time alerts are stored in an Azure Cosmos DB for NoSQL database. The system requirements are:

- Ensure sub-10 ms10\text{ ms} write latencies for Cosmos DB across three regions (East US, West Europe, and East Asia) with a 99.999%99.999\% write availability SLA.
- Support regional failover without data loss for committed Cosmos DB transactions.
- Dynamically authorize device uploads to Azure Blob Storage securely, allowing token revocation if a device is compromised.
- Avoid performance bottlenecks or hot partitions in Cosmos DB during peak traffic.

Which database and storage configuration should you recommend?

Cevabı ve açıklamayı göster

Cevap: Enable multi-region writes in the Azure Cosmos DB account with Session consistency, using a synthetic partition key that combines the device identifier and date. For Azure Blob Storage, configure Geo-Redundant Storage (GRS) and delegate upload access using Shared Access Signatures (SAS) associated with a Stored Access Policy.

Cevap

Enable multi-region writes in the Azure Cosmos DB account with Session consistency, using a synthetic partition key that combines the device identifier and date. For Azure Blob Storage, configure Geo-Redundant Storage (GRS) and delegate upload access using Shared Access Signatures (SAS) associated with a Stored Access Policy.
The configuration using a synthetic partition key and a Stored Access Policy for SAS authorization is correct because multi-region write replication guarantees the sub-10ms write latency and the 99.999% SLA. Session consistency provides read-your-writes guarantees and is supported with multi-region writes. The synthetic partition key ensures high cardinality to prevent hot partitions, and the Stored Access Policy allows security administrators to immediately revoke SAS tokens if a device is compromised.

Adım Adım Çözüm

1
Analyze Azure Cosmos DB latency and consistency requirements for multi-region writes.
Confirming multi-region writes are enabled to meet sub-10ms write latency and 99.999% availability. Note that Strong and Bounded Staleness consistency levels are not supported in multi-region write configurations, making Session consistency the highest level that guarantees read-your-writes.
Ensures the database matches performance constraints while choosing the strongest supported consistency level.
2
Design the Cosmos DB partitioning strategy.
Rejecting low-cardinality keys like Region ID, and selecting a high-cardinality synthetic key (combining device ID and date).
Prevents hot partitions and distributes write request units evenly across physical partitions.
3
Select Blob Storage redundancy and security patterns.
Configuring Geo-Redundant Storage (GRS) to survive regional outages, and using Shared Access Signatures (SAS) bound to a Stored Access Policy.
Meets redundancy SLAs and allows revocation of SAS tokens by modifying or deleting the underlying Stored Access Policy if a device is compromised.

Anahtar Kavram

Azure Cosmos DB Multi-Region Consistency and Partitioning with Azure Storage SAS Security
Soru 220Soru

An enterprise operates a multi-subscription Azure environment managed under a single root management group. You are designing a security and governance solution for a team of database administrators (DBAs) and a compliance auditing team.

The DBAs must be able to create and modify Azure SQL databases, but they must be prevented from deleting databases or altering SQL Server firewall rules. Their access must be limited to their 8-hour shifts, require manager approval, and scale automatically without manual role assignments when new DBAs join the team.

The compliance auditing team requires that all SQL servers automatically configure diagnostic logging to a centralized storage account without blocking database creation operations.

Which governance and access control configuration should you recommend?

Cevabı ve açıklamayı göster

Cevap: Assign a custom Azure RBAC role with `Microsoft.Sql/servers/databases/*` in Actions and `Microsoft.Sql/servers/databases/delete` in NotActions to a Microsoft Entra security group. In Microsoft Entra Privileged Identity Management (PIM), make the group eligible for the role with a maximum activation duration of 8 hours and approval requirements. Assign an Azure Policy with the DeployIfNotExists effect at the root management group scope.

Cevap

Assign a custom Azure RBAC role restricting database deletion to a Microsoft Entra security group, configure that group as eligible in Microsoft Entra Privileged Identity Management (PIM) with approval and an 8-hour duration limit, and deploy an Azure Policy with the DeployIfNotExists effect at the root management group.
The correct solution uses a custom role to prevent database deletion, assigns it to a Microsoft Entra group to allow dynamic scalability as DBAs join, configures PIM eligibility for just-in-time access restricted to 8 hours with approval, and utilizes a DeployIfNotExists policy to automatically deploy diagnostics without interrupting resource provisioning.

Adım Adım Çözüm

1
Define a custom RBAC role.
A custom role is created with Actions permitting database management (e.g., `Microsoft.Sql/servers/databases/*`) and NotActions preventing deletion (e.g., `Microsoft.Sql/servers/databases/delete`). Firewalls cannot be modified as they require server-level permissions.
Built-in roles like SQL DB Contributor allow database deletion, violating the security requirement. A custom role enforces the principle of least privilege.
2
Determine the role assignment target.
The custom role is assigned to a Microsoft Entra security group at the root management group scope rather than to individual user accounts.
Direct user assignment introduces high administrative overhead and violates best practices for group-based access management.
3
Configure JIT access controls using Privileged Identity Management (PIM).
The security group's assignment to the role is defined as eligible, setting a maximum activation duration of 8 hours and requiring manager approval.
This implements shift-based access and satisfies just-in-time requirements, avoiding permanently active privileges.
4
Select the correct Azure Policy effect for diagnostic configurations.
Deploy an Azure Policy using the DeployIfNotExists effect to automatically configure diagnostic logs.
DeployIfNotExists remediates non-compliant resources after deployment without blocking resource creation, whereas a Deny policy would block the creation of the SQL server if the settings are missing in the initial request.

Anahtar Kavram

Azure RBAC, Entra PIM, and Azure Policy integration for subscription governance
ÖncekiSayfa 11 / 60Sonraki