All practice questions

Match each traffic routing and failover requirement with the most appropriate Azure load balancing or traffic routing service configuration. Each service configuration may be used once, more than once, or not at all.

An organization is designing a hybrid identity and security strategy for Microsoft Entra ID. You need to match each technical requirement to the most appropriate Microsoft Entra ID authentication method or Conditional Access control. Match each requirement on the left to the correct feature on the right.

An enterprise is designing a centralized monitoring and log routing architecture for its Azure environment. The architecture must accommodate various auditing, security, and networking logs while satisfying constraints around operational cost, real-time analysis, administrative access control, and long-term retention.

Match each log routing requirement scenario on the left with the most appropriate Azure destination or architectural configuration on the right.

You are designing a log routing and monitoring strategy for an Azure infrastructure solution. Match each Azure destination to its primary use case.

You are designing a centralized monitoring and log routing architecture for an enterprise with multiple Azure subscriptions. You need to map each corporate log management requirement to its optimal Azure service architecture. Each configuration must satisfy the constraints while minimizing administrative overhead and cost.

Match each operational requirement on the left to the most appropriate Azure architecture design on the right.

An enterprise is designing a centralized monitoring and log routing architecture for its Azure environment. The architecture must accommodate several workloads with distinct security, compliance, and retention constraints. Match each operational log routing requirement on the left with its most appropriate Azure routing and destination configuration on the right.

An organization is designing a monitoring solution for its Azure environment. Match each Azure Monitor data type or source to its primary description.

You are designing a monitoring and log routing architecture for a large Azure enterprise environment. You need to route different types of Azure logs and metrics to the appropriate destinations to meet specific operational and compliance requirements.

Which destination should you match with each log source to meet the requirements?

An enterprise is designing a comprehensive monitoring and log routing architecture to support workloads across multiple Azure regions. Match each specific logging requirement to its correct Azure architectural design configuration.

A financial services firm is designing a secure identity infrastructure. The lead architect must map specific security compliance requirements to the correct Microsoft Entra ID and Conditional Access features. Match each requirement to the appropriate Microsoft Entra ID or Conditional Access feature.

You are designing a hybrid identity and multi-tenant solution for a company named ZenithLogix. The company has an on-premises Active Directory Domain Services (AD DS) forest and a Microsoft Entra ID tenant. You need to select the appropriate identity feature or sync method to meet each of the following business and security requirements:

- Ensure that users can authenticate to cloud services even during an on-premises network or power outage.
- Enforce on-premises account restrictions (such as logon hours) in real-time for cloud authentication without deploying Active Directory Federation Services (AD FS).
- Allow guest users from a trusted partner company to log in to corporate resources using their own corporate Microsoft Entra tenant credentials.
- Enable users who reset their passwords in Microsoft Entra ID to have the changes immediately reflected in the on-premises AD DS.

Match each requirement on the left to the correct identity solution on the right.

Aetheris Dynamics is designing a hybrid identity and multi-tenant architecture to integrate four newly acquired business units (BU1, BU2, BU3, and BU4). You must match each business unit's technical requirements to the appropriate Microsoft Entra ID implementation.

- BU1 requires that users authenticate directly against the on-premises Active Directory Domain Services (AD DS) domain controllers. Authentication must happen on-premises to enforce local login hour restrictions without the complexity of Active Directory Federation Services (AD FS). The solution must remain available if a single on-premises server hosting the synchronization agent fails.
- BU2 requires the highest level of business continuity for authentication, allowing users to sign in to cloud services even during an on-premises network outage. Additionally, users must be able to change their passwords in the cloud, which must immediately update on-premises AD DS.
- BU3 has a security policy that strictly prohibits on-premises user password hashes or credentials from ever being stored in the cloud. User authentication must be federated, utilizing existing on-premises smart card infrastructure, and must support complex multi-factor authentication (MFA) policies managed entirely on-premises.
- BU4 needs to allow external contractors, who manage their own identity providers, to access specific Azure resources. Access must be restricted to a pre-defined duration, and the contractors must be automatically removed when their contract ends.

Match each business unit to the correct hybrid identity or multi-tenant solution component.

Your organization, Tailwind Traders, is designing a hybrid and multi-tenant identity solution to integrate several business units and external partners with Microsoft Entra ID. You need to match the specific business requirement on the left to the correct Microsoft Entra identity technology or configuration on the right to achieve a secure, resilient, and highly automated architecture.

An organization is designing a security and access control strategy for its Microsoft Entra ID tenant to protect sensitive cloud resources and workloads. The security team has defined several key access requirements for their environment. Match each security requirement to the corresponding Microsoft Entra ID or Conditional Access feature that best satisfies it.

Your enterprise is designing a monitoring and log routing solution. You need to match each monitoring requirement to the correct Azure service or configuration that satisfies the requirement at the lowest cost and complexity.

Match each log routing requirement on the left to its most appropriate Azure resource or configuration on the right.

An organization is migrating several legacy workloads to Azure and plans to use Azure Cosmos DB. You need to recommend the appropriate Azure Cosmos DB API for each workload based on their technical requirements.

Match each workload pattern to its corresponding Azure Cosmos DB API.

A global financial enterprise is designing a hybrid identity and access management solution using Microsoft Entra ID. You need to align specific security and authentication requirements with the appropriate Microsoft Entra ID feature or Conditional Access configuration.

Match each security requirement on the left to its corresponding feature or configuration on the right. (Each option on the right may be used once, more than once, or not at all.)

An organization is designing a security and identity infrastructure solution using Microsoft Entra ID. Match each organization's technical or security requirement to the most appropriate Microsoft Entra ID authentication method or Conditional Access feature.

You are designing a global database solution using Azure Cosmos DB. You need to match the specific application requirements on the left to the appropriate Azure Cosmos DB consistency level on the right that meets those requirements with the lowest latency and highest availability.

NexaHealth is designing an identity and security strategy using Microsoft Entra ID. You need to match each technical requirement to the most appropriate Microsoft Entra ID or Conditional Access feature. Drag the appropriate feature from the column on the right to the matching requirement on the left.