Microsoft Practice Questions, Discussions & Exam Topics by our Authors

You need to recommend a solution to generate a monthly report of all the new Azure Resource Manager (ARM) resource deployments in your Azure s...

To generate a monthly report of all the new Azure Resource Manager (ARM) resource deployments in your Azure subscription, the ideal solution must capture and provide information about resource deployment events such as resource creation, modification, and deletion. Let's review the options: A) Azure Monitor Action Groups - Explanation: Action Groups in Azure Monitor are used to trigger actions based on alerts (e.g., send emails, invoke functions). They are not designed to generate reports or log resource creation activities. - Why Rejected: Action Groups are useful for triggering notifications or workflows but do not provide an automated way to retrieve detailed information on resource deployments. - Scenario for Use: You could use Action Groups after a log is generated to alert administrators about certain activities or issues but not for generating a report of deployments. B) Azure Arc - Explanation: Azure Arc is a service that extends Azure management to on-premises, multicloud, and edge environments. It enables you to manage resources that are outside the Azure data centers, such as on-premises servers or Kubernetes clusters. - Why Rejected: Azure Arc doesn't provide direct insights or reporting for ARM resource deployments in your Azure subscription. It's intended for managing hybrid or multi-cloud environments and not for logging or tracking resource creation. - Scenario for Use: You could use Azure Arc for managing hybrid resources or non-Azure re...

Author: ElectricLionX · Last updated Jul 28, 2026

DRAG DROP - You have an Azure AD tenant that contains an administrative unit named MarketingAU. MarketingAU contains 100 users. You create two users named User1 and User2. You need to ensure that the users can perform the following actions in MarketingAU: * User1 must be able to create user accounts. * User2 must be able to reset user passwords. Which role should you assign to each user? To answer, drag the appropriate roles to the corr...

Author: Charlotte · Last updated Jul 28, 2026

You need to recommend a solution to generate a monthly report of all the new Azure Resource Manager (ARM) resource deployments in your Azure s...

To generate a monthly report of all the new Azure Resource Manager (ARM) resource deployments in your Azure subscription, the ideal solution should provide detailed logs of resource management activities such as resource creation, updates, and deletions. Let's review the options: A) Azure Arc - Explanation: Azure Arc is a solution that extends Azure management to on-premises, multicloud, and edge environments. It allows you to manage resources outside of Azure but does not specifically focus on tracking or reporting Azure resource deployments. - Why Rejected: Azure Arc is not designed for tracking or reporting Azure resource management activities within an Azure subscription. It is used for hybrid or multicloud scenarios, which is not the requirement in this case. - Scenario for Use: Use Azure Arc when you want to extend Azure management to non-Azure resources or manage hybrid environments but not for resource deployment reporting. B) Azure Log Analytics - Explanation: Azure Log Analytics is a service that collects and analyzes log data from various Azure resources. It allows you to query logs related to Azure activity, including ARM resource deployments, by integrating with the Azure Activity Log. - Why Selected: Log Analytics can integrate with the Azure Activity Log and provide powerful query capabilities to generate custom reports. It can be used to track and report on ARM resource deployments, making it an ideal choice for generating monthly reports. - Scenario for Use: Use Azure Log Analytics when you need to collect, query, and analyze logs from multiple Azure resources, including the Activity Log, to generate detailed reports on resource deployments. C) Application Insights - Explanation: App...

Author: Liam · Last updated Jul 28, 2026

SNAPSHOT - You are designing an app that will be hosted on Azure virtual machines that run Ubuntu. The app will use a third-party email service to send email messages to users. The third-party email service requires that the app authenticate by using an API key. You need to recommend an Azure Key Vault solution for storing and accessing the API key. The solution must minimize administrative effort. ...

Author: Harper · Last updated Jul 28, 2026

DRAG DROP - You have two app registrations named App1 and App2 in Azure AD. App1 supports role-based access control (RBAC) and includes a role named Writer. You need to ensure that when App2 authenticates to access App1, the tokens issued by Azure AD include the Writer role claim. Which blade should you use to modify each app registration? To answer, drag the appropriate blades to the correct app registrations. Eac...

Author: VioletCheetah55 · Last updated Jul 28, 2026

You need to recommend a solution to generate a monthly report of all the new Azure Resource Manager (ARM) resource deployments in your Azure s...

To generate a monthly report of all new Azure Resource Manager (ARM) resource deployments in your Azure subscription, we need a solution that can track and log the creation of resources over time and provide reporting capabilities. Analysis of the options: 1. Application Insights: - Purpose: Application Insights is primarily focused on monitoring the performance, availability, and usage of web applications, including logging and telemetry data from apps. While it can collect some Azure resource telemetry, it is not designed to track ARM resource deployments or resource creation activities. - Reason for rejection: Application Insights is not tailored for resource management and deployment logging. It’s more appropriate for application-level diagnostics rather than resource-level insights. - Scenario it can be used: Application Insights is ideal for monitoring web applications or custom applications deployed in Azure but not suitable for resource deployment logging. 2. Azure Arc: - Purpose: Azure Arc extends Azure management and governance to resources outside Azure, including on-premises, multi-cloud, or edge environments. It allows Azure services to be extended to non-Azure resources. - Reason for rejection: While Azure Arc is great for managing resources that are outside of Azure, it is not directly designed to log or track ARM resource deployments within Azure itself. - Scenario it can be used: Azure Arc is appropriate when managing hybrid or multi-cloud environments, but it doesn't provide the native logging and reporting capabilities for Azure ARM resource deployments. 3. Azure Log Analytics: - Purpose: Azure Log Analytics is part of Azure Monitor and allows you to collect and analyze log data from various A...

Author: Olivia Johnson · Last updated Jul 28, 2026

You have an Azure subscription. You plan to deploy a monitoring solution that will include the following: * Azure Monitor Network Insights * Application Insights * Microsoft Sentinel * VM insights The monitoring solution ...

To determine the minimum number of Azure Monitor workspaces required for the solution, let's first break down the components: Components and their requirements: 1. Azure Monitor Network Insights: - Requirement: Azure Monitor Network Insights uses Azure Monitor Logs for gathering and analyzing data. It typically relies on a Log Analytics workspace for storing the logs and metrics related to network resources. 2. Application Insights: - Requirement: Application Insights is used to monitor and analyze the performance of applications. It stores its telemetry data in a separate Application Insights resource but can integrate with Log Analytics workspaces if needed for advanced querying. 3. Microsoft Sentinel: - Requirement: Microsoft Sentinel is a security information and event management (SIEM) solution that collects data from various sources and integrates directly with Log Analytics workspaces. 4. VM Insights: - Requirement: VM Insights is a solution within Azure Monitor that provides monitoring capabilities for virtual machines. It stores data in a Log Analytics workspace for analyzing metrics, logs, and performance data. Key Factors in Reasoning: - Azure Monitor Workspaces: A Log Analytics workspace is typically used for storing logs, metrics, and data from various monitoring services (including Network Insights, Microsoft Sentinel, and VM Insights). Application Insights also integrates with Log Analytics workspace...

Author: Benjamin · Last updated Jul 28, 2026

You need to recommend a solution to generate a monthly report of all the new Azure Resource Manager (ARM) resource deployments in your Azure s...

To generate a monthly report of all new Azure Resource Manager (ARM) resource deployments in your Azure subscription, we need a solution that can track resource creation activities and generate reports from that data. Let’s evaluate the given options: 1. Application Insights: - Purpose: Application Insights is used primarily for monitoring application performance, availability, and user behavior. It collects telemetry data from web applications and services but is not specifically designed to track or report on Azure resource deployments. - Reason for rejection: Application Insights focuses on application-level metrics and diagnostics, not on the management or tracking of Azure resource deployments. Therefore, it's not suitable for generating reports on ARM resource creation. - Scenario it can be used: It's ideal for tracking application performance or usage metrics, but not for tracking resource creation activities in Azure. 2. Azure Analysis Services: - Purpose: Azure Analysis Services is an enterprise-grade analytics solution that provides data modeling capabilities for large datasets. It integrates well with Power BI and other reporting tools to generate business intelligence reports. - Reason for rejection: Azure Analysis Services is not designed for tracking resource deployments or logs. It’s a powerful tool for data modeling and reporting, but it requires data from other sources (like logs) to generate reports. It doesn't track Azure resource creation out of the box. - Scenario it can be used: Azure Analysis Services is suited for business intelligence and data analytics but not for direct tracking of Azure resource activities. 3. Azure Advisor: - Purpose: Azure Advisor provides personali...

Author: Aditya · Last updated Jul 28, 2026

SNAPSHOT - Case Study - This is a case study. Case studies are not timed separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided. To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other questions in this case study. At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next section of the exam. After you begin a new section, you cannot return to this section. To start the case study - To display the first question in this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. If the case study has an All Information tab, note that the information displayed is identical to the information dis...

Author: Vivaan · Last updated Jul 28, 2026

You have an Azure subscription that contains 10 web apps. The apps are integrated with Azure AD and are accessed by users on different project teams. The users frequently move between projects. You need to recommend an access management solution for the web apps. The solution must meet the following requirements: * The users must only have access to the app of the project to which they are assigned currently. * Project managers must verify which users have access to their project's app and remove users t...

To recommend an access management solution for the web apps based on the given requirements, let’s evaluate each option: 1. Azure AD Identity Protection: - Purpose: Azure AD Identity Protection helps to detect potential vulnerabilities and risks in user accounts, including risky sign-ins, and provides conditional access policies to mitigate those risks. - Reason for rejection: While Azure AD Identity Protection can detect risky sign-ins and enforce security measures, it does not directly address the requirements for managing access based on project assignments, verifying user access, or automating access review processes. - Scenario it can be used: Identity Protection is best used for detecting and mitigating risks related to compromised or at-risk accounts but does not meet the specific needs of access management and access reviews outlined in this scenario. 2. Microsoft Defender for Identity: - Purpose: Microsoft Defender for Identity focuses on protecting against advanced threats and monitoring identity-based activities, such as suspicious user behavior or potential security threats. - Reason for rejection: Similar to Azure AD Identity Protection, Defender for Identity is more focused on security incidents and threat detection. It doesn't provide the specific tools to manage and review user access to apps or automate regular access verifications for project teams. - Scenario it can be used: It is suited for security-focused identity protection but not for managing access to specific web apps or ensuring regular access reviews for project teams. 3. Microsoft Entra Permissions Management: - Purpose: Microsoft Entra Permissions Management allows you to manage and govern permissions across cloud environments, including managing access to resources, identifying who has access to what, and enforcing least-privilege access policies. - Reason for rejection: While this solution offers robust permission management, it does not directly automate user access reviews or provide the a...

Author: Sara · Last updated Jul 28, 2026

SNAPSHOT - You have an Azure subscription that contains 50 Azure SQL databases. You create an Azure Resource Manager (ARM) template named Template1 that enables Transparent Data Encryption (TDE). You need to create an Azure Policy definition named Policy1 that will use Template1 to enable TDE for any noncompliant Azure SQL databases. ...

Author: ShadowWolf101 · Last updated Jul 28, 2026

You have an Azure subscription. The subscription contains a tiered app named App1 that is distributed across multiple containers hosted in Azure Container Instances. You need to deploy an Azure Monitor monitoring solution for App. The solution must meet the following requirements: * Support using synthetic transact...

To meet the requirements of deploying an Azure Monitor monitoring solution for App1, a tiered app distributed across multiple containers, let's break down the options provided: Key Requirements: 1. Support using synthetic transaction monitoring to monitor traffic between the App1 components. - Synthetic transaction monitoring involves simulating user actions (or traffic) to validate the availability and performance of an app or its components. 2. Minimize development effort. - The solution should be easy to deploy and integrate with minimal custom code or heavy configuration. Options Breakdown: A) Network Insights: - Purpose: Network Insights provides visibility into network traffic and allows for diagnostics of issues related to networking and connectivity between Azure resources. - Rejection Reason: Network Insights focuses on network-level insights and traffic analysis, but it does not offer synthetic transaction monitoring. It would not fulfill the requirement of monitoring traffic between the app components at an application level. B) Application Insights: - Purpose: Application Insights is designed for application performance monitoring. It provides features like telemetry collection, monitoring requests, dependencies, and performance. It supports synthetic transaction monitoring via Application Insights Availability Tests, where you can simulate user traffic to test the availability and response time of application components. - Why Selected: Application Insights is the best fit because it supports synthetic transaction monitoring, which ...

Author: Zara · Last updated Jul 28, 2026

SNAPSHOT - You have an Azure subscription that contains the resources shown in the following table: Log files from App1 are registered to App1Logs. An average of 120 GB of log data is ingested per day. You configure an Azure Monitor alert that will be triggered if the App1 logs contain error messages. You need to minimize the Log Analytics costs associated with App1. The solution must meet the following requirements: * Ensure that all the log files from App1 are ingested to App1Logs. * Minimize the im...

Author: Noah · Last updated Jul 28, 2026

You have 12 Azure subscriptions and three projects. Each project uses resources across multiple subscriptions. You need to use Microsoft Cost Management to monitor costs on a per project basis. The solution must minimize administrative effort. Which two components should you incl...

To monitor costs on a per-project basis in Microsoft Cost Management with minimal administrative effort, we need to focus on a solution that enables cost tracking across multiple subscriptions and projects while reducing manual configuration. Let’s analyze each option and see how it can contribute to this goal. Key Requirements: 1. Monitor costs per project: The solution needs to track costs associated with each project, which spans across multiple Azure subscriptions. 2. Minimize administrative effort: The solution should simplify the monitoring process with minimal configuration and ongoing maintenance. Option Breakdown: A) Budgets: - Purpose: Budgets in Azure Cost Management allow you to define cost thresholds and monitor spending against those budgets. Budgets can be set at the subscription level or resource group level, and they help track and manage spending efficiently. - Why Selected: Budgets allow for tracking costs across subscriptions, and you can assign budgets to specific projects. While budgets themselves are not directly tied to "projects" in the traditional sense, you can associate them with resource groups or specific subscriptions related to each project, enabling cost tracking per project. - Why Not Rejected: Budgets are a core part of cost management and tracking. They are essential for the requirement of monitoring costs across multiple subscriptions. They can be customized for each project, reducing administrative overhead. B) Resource Tags: - Purpose: Tags allow you to label resources with key-value pairs. By tagging resources (e.g., with a tag for project names), you can filter and analyze costs related to specific projects or departments. - Why Selected: Using resource tags enables cost tracking on a per-project basis. You can tag all resources under a project with a common tag and then filter the costs in Cost Management by these tags. This approach minimizes administrative overhead because you only need to set the tags once when the resources are created or updated. - Why Not Rejected: Tags are a low-effort and scalable solution for associating resources with projects. Once applied, costs can easily be tracked per project through Cost Management by filtering based on these tags. C) Custom Role-Base...

Author: Vivaan · Last updated Jul 28, 2026

SNAPSHOT - You have an Azure subscription that contains multiple storage accounts. You assign Azure Policy definitions to the storage accounts. You need to recommend a solution to meet the following requirements: * Trigger on-demand Azure Policy compliance scans. * Raise Azure Monitor non-compliance alerts by querying logs collected by Log Analytics. W...

Author: John · Last updated Jul 28, 2026

SNAPSHOT - You have an Azure subscription. You plan to deploy five storage accounts that will store block blobs and five storage accounts that will host file shares. The file shares will be accessed by using the SMB protocol. You need to recommend an access authorization solution for the storage accounts. The solution must meet the following requirements: * Maximize security. * Prevent the use of shared keys. * Whenever possi...

Author: Sofia · Last updated Jul 28, 2026

SNAPSHOT - You have an Azure subscription. The subscription contains 100 virtual machines that run Windows Server 2022 and have the Azure Monitor Agent installed. You need to recommend a solution that meets the following requirements: * Forwards JSON-formatted logs from the virtual machines to a Log Analytics workspace * Transforms the logs and stores the data in a table in the Log Analytics...

Author: Charlotte · Last updated Jul 28, 2026

SNAPSHOT - You have five Azure subscriptions. Each subscription is linked to a separate Azure AD tenant and contains virtual machines that run Windows Server 2022. You plan to collect Windows security events from the virtual machines and send them to a single Log Analytics workspace. You need to recommend a solution that meets the following requirements: * Collects event logs from multiple subscriptions * Supports the use of data collection rules (DC...

Author: Suresh · Last updated Jul 28, 2026

You have 100 servers that run Windows Server 2012 R2 and host Microsoft SQL Server 2014 instances. The instances host databases that have the following characteristics: * Stored procedures are implemented by using CLR. * The largest database is currently 3 TB. None of the databases will ever exceed 4 TB. You plan to move all the data from SQL Server to Azure. You need to recommend a service to host the databases. The solution must meet the following requirements: * Whenever possible, minimize management overhead for the migrated da...

Key Requirements: 1. Minimize management overhead: The goal is to choose a service that reduces the administrative burden after migration. 2. Azure Active Directory (Azure AD) authentication: Users must be able to authenticate using Azure AD credentials, which is a core part of Azure's identity and access management. 3. Minimize database changes: The migration should require minimal changes to the current database setup and structure. Solution Options: A) Azure SQL Database Elastic Pools: - Azure SQL Database Elastic Pools are used for managing a collection of databases that share resources like CPU and memory. This is ideal for situations where there are multiple databases with variable usage patterns. - However, Elastic Pools are designed for smaller, multi-database scenarios with databases that have differing performance needs, and they may not be ideal for large, individual databases like the ones in this case (with the largest being 3 TB). - Additionally, Azure AD authentication is supported with Azure SQL Database, but Elastic Pools are more suited for smaller, lighter databases and are not optimized for very large databases like the 3 TB size described. - Rejected: It doesn't fully meet the performance needs for databases of the size described. B) Azure SQL Managed Instance: - Azure SQL Managed Instance is a fully managed service that offers near-complete compatibility with SQL Server. It supports many of the same features and capabilities, such as CLR stored procedures (which are a part of the requirement), and has Azure AD authentication support. - Managed instances allow for minimal changes when migrating from on-premises SQL Server to the cloud, as they are designed to be highly compatible with on-premises SQL Server deployments. - Large Database Support: SQL Managed Instances can handle databases larger than 4 TB, and the largest database here is 3 TB, making it a good fit. - Minimized Management Overhead: Managed Instances provide an almost "lift-and-shift" experience for SQL Server databases, grea...

Author: Akash · Last updated Jul 28, 2026

You have an Azure subscription that contains an Azure Blob Storage account named store1. You have an on-premises file server named Server1 that runs Windows Server 2016. Server1 stores 500 GB of company files. You need to store a copy of the company files from Server1 in store1. Which two possible Az...

Problem Breakdown: You need to copy 500 GB of company files from an on-premises file server (Server1) to an Azure Blob Storage account (store1). The goal is to find Azure services that will allow for this data transfer. Option Evaluation: A) Azure Logic Apps Integration Account: - Azure Logic Apps allows for the automation of workflows and the integration of services. It can help automate tasks between different services but is not designed for large-scale data transfers like the one required for transferring 500 GB of files from an on-premises file server to Azure Blob Storage. - Integration accounts in Azure Logic Apps help store and manage configuration for integration workflows, but they are not optimized for large file transfers. - Rejected: This is not ideal for copying a large number of files to Blob Storage. B) Azure Import/Export Job: - Azure Import/Export allows you to transfer large amounts of data to Azure Blob Storage via physical disks. However, this method is designed for scenarios where transferring the data over the network would be too slow or impractical. You would physically ship hard drives to Azure for importing the data into Blob Storage. - Use Case: This option is ideal for transferring large volumes of data when you cannot easily transfer the data over the internet. While it's an option, it is typically used when network speeds are not sufficient for the volume of data. - Accepted: This is a valid option for the large data transfer if network-based transfer is too slow or impractical. C) Azure Data Factory: - Azure Data Factory (ADF) is a fully managed service for data integration and transformation. ADF can be used to copy data from on-premises systems to Azure Blob Storage efficiently and supports large-scale data movements, including scheduling and monitoring. - Use Case: ADF provides a scalable solution...

Author: Ethan · Last updated Jul 28, 2026

You have an Azure subscription that contains two applications named App1 and App2. App1 is a sales processing application. When a transaction in App1 requires shipping, a message is added to an Azure Storage account queue, and then App2 listens to the queue for relevant transactions. In the future, additional applications will be added that will process some of the shipping requests based on the specific details of the transactions...

In this scenario, the goal is to allow multiple applications to process the same transaction details from the queue. Given that multiple applications may need to listen to these messages, we need a solution that supports multiple consumers. Let’s analyze each option: A) One Azure Data Factory pipeline Azure Data Factory is primarily used for orchestrating and automating data workflows across different data sources. While it’s good for managing data pipelines and ETL tasks, it is not designed for real-time message processing or handling messages that need to be processed by multiple applications simultaneously. Additionally, it would introduce unnecessary complexity for this use case. Rejected: Azure Data Factory is not designed for event-driven architectures, which is essential for this scenario. B) Multiple storage account queues While multiple storage queues can be used for this purpose, they lack built-in features for broadcasting the same message to multiple consumers. In this scenario, if each new application needs to consume the same message from the queue, managing multiple queues and ensuring the right application is listening to the right queue becomes cumbersome. Additionally, it is difficult to scale this solution as the number of applications grows. Rejected: Multiple queues would create more complexity and won't scale efficiently as you add more consumers. C)...

Author: Noah · Last updated Jul 28, 2026

SNAPSHOT - You need to design a storage solution for an app that will store large amounts of frequently used data. The solution must meet the following requirements: * Maximize data throughput. * Prevent the modification of data for one year. * Minimize latency for read and write operations. Which Azure Storage account type and storage s...

Author: Liam · Last updated Jul 28, 2026

SNAPSHOT - You have an Azure subscription that contains the storage accounts shown in the following table. You plan to implement two new apps that have the requirements shown in the following table. Which storage accounts should you recommend using for each app? To a...

Author: Ava · Last updated Jul 28, 2026

You are designing an application that will be hosted in Azure. The application will host video files that range from 50 MB to 12 GB. The application will use certificate-based authentication and will be available to users on the internet. You need to recommend a storage option for the vid...

To determine the best storage option for hosting video files in Azure, let's break down the requirements and evaluate each option: Key Requirements: 1. Video files ranging from 50 MB to 12 GB: These files are large, so the storage solution must be optimized for handling large file sizes. 2. Fast read performance: The solution should provide fast access to video files, ensuring minimal latency for video playback or downloads. 3. Minimized storage costs: Since these are large files, cost optimization is important for storing and retrieving them. --- Evaluating the Options: A) Azure Files: - Azure Files is a managed file share service in the cloud using the SMB (Server Message Block) protocol. It is best suited for scenarios where you need to share files across applications or between virtual machines. - Pros: - Suitable for lift-and-shift scenarios (migrating file shares to the cloud). - Can integrate with applications that use file system APIs. - Cons: - Not optimized for large, unstructured data like video files. - Higher storage costs compared to Blob Storage, especially for large files. - Slower performance compared to Blob Storage for large media files. Rejected: Azure Files is not ideal for hosting video files due to performance and cost concerns. B) Azure Data Lake Storage Gen2: - Azure Data Lake Storage Gen2 is optimized for big data analytics and works with hierarchical namespace and high throughput. - Pros: - Excellent for large datasets and big data workloads. - Supports efficient analytics and data processing. - Cons: - It is designed for analytics workloads rather than serving media like videos. - Higher complexity and may not be necessary for a simple video hosting scenario. Rejected: Azure Data Lake Storage is over-engineered for video hosting and is bett...

Author: Sophia Clark · Last updated Jul 28, 2026

You are designing a SQL database solution. The solution will include 20 databases that will be 20 GB each and have varying usage patterns. You need to recommend a database platform to host the databases. The solution must meet the following requirements: * The solution must meet a Service Level Agreement (SLA) of 99.99% uptime. * The compute resources allocated to the da...

To determine the best database platform for hosting the 20 databases while meeting the specified requirements, let's analyze each option based on key factors like uptime, scalability, compute cost optimization, and overall suitability for the workload. Requirements: 1. 99.99% uptime: The solution must ensure high availability, so we need to focus on platforms that offer built-in uptime guarantees. 2. Dynamic scalability of compute resources: The solution must allow compute resources to scale automatically based on workload demands. 3. Reserved capacity for cost minimization: Reserved capacity will help reduce compute charges and make the solution more cost-effective. 4. Varying usage patterns: The databases will have different usage patterns, meaning we need flexibility to manage performance and cost across different databases. --- Evaluating the Options: A) An elastic pool that contains 20 Azure SQL databases: - Elastic Pools in Azure SQL Database allow multiple databases to share a set of compute resources, which is ideal for databases with varying usage patterns. The databases can scale dynamically within the pool based on demand. - Pros: - High availability: Azure SQL Database guarantees 99.99% uptime, which meets the SLA requirement. - Dynamic scalability: Compute resources can scale dynamically within the pool, allowing each database to use the required resources without over-provisioning. - Reserved capacity: You can use reserved capacity to reduce compute charges, as resources in elastic pools can be reserved for a longer period at a reduced rate. - Cost-effective: Since the databases are in a pool, the cost is shared across them, making this solution cost-effective, especially when workloads are variable. - Cons: - May require tuning for performance depending on the specific usage patterns of each database, but it is highly flexible. Selected: This option is a good fit for the given requirements because it supports dynamic scaling, high availability, and cost optimization with reserved capacity. It's ideal for multiple databases with varying usage patterns. B) 20 databases on a Microsoft SQL server that runs on an Azure virtual machine in an availability set: - Azure Virtual Machines can run SQL Server, and placing the VMs in an availability set ensures high availability, meeting the 99.99% uptime requirement. - Pros: - High availability: The availability set ensures that VMs are spread across fault domains, which provides redundancy and uptime guarantees. - Customizability: Full control over SQL Server configurations, performance, and compute resources. - Cons: - No dynamic scaling: Scaling compute resources would require manual intervention or reconfiguration of the virtual machine, which is not as dynamic as other cloud-native options. - Higher cost: Running multiple VMs can be more expensive than using a fully managed service like Azure SQL Database, especially ...

Author: Liam · Last updated Jul 28, 2026

SNAPSHOT - You have an on-premises database that you plan to migrate to Azure. You need to design the database architecture to meet the following requirements: * Support scaling up and down. * Support geo-redundant backups. * Support a database of up to 75 TB. * Be optimized for online transaction processing (OLTP). What should ...

Author: Ming · Last updated Jul 28, 2026

You are planning an Azure IoT Hub solution that will include 50,000 IoT devices. Each device will stream data, including temperature, device ID, and time data. Approximately 50,000 records will be written every second. The data will be visualized in near real time. You need to recommend a service to store and query the dat...

To store and query the data from 50,000 IoT devices that stream data such as temperature, device ID, and time, we need to choose services that can handle high throughput, support near real-time data ingestion, and offer efficient querying. Let’s analyze each option. Evaluation of Possible Solutions: A) Azure Table Storage - Data Model: Azure Table Storage is a NoSQL key-value store that provides a scalable and inexpensive way to store large amounts of unstructured data. - Throughput: It can support high throughput, but it does not have built-in support for complex querying or analytics. - Querying: It supports basic queries (e.g., querying by partition key and row key), but it’s not ideal for time-series data or advanced querying needs like range queries over time. - Why rejected: While it could technically handle the high throughput and store the data, it lacks advanced querying capabilities for time-series analysis and is not optimized for real-time data visualization. It would require custom solutions for these use cases. B) Azure Event Grid - Event-Driven: Azure Event Grid is an event routing service that allows event-driven architecture and can route events to different endpoints, but it is not a data storage service. - Data Storage: Event Grid is not used for storing data but for event-driven scenarios. It can trigger downstream processes but does not store or query data itself. - Why rejected: Event Grid is not designed for data storage or querying; it is better suited for event management and triggering actions in response to events. C) Azure Cosmos DB SQL API - Data Model: Cosmos DB is a globally distributed, multi-model database service that supports SQL-based querying via the SQL API. - Throu...

Author: Sara · Last updated Jul 28, 2026

You are designing an application that will aggregate content for users. You need to recommend a database solution for the application. The solution must meet the following requirements: * Support SQL commands. * Support multi-mast...

To design an application that aggregates content for users and meets the requirements of supporting SQL commands, multi-master writes, and guaranteeing low-latency read operations, let's evaluate each option: Requirements: - Support SQL commands: The solution must be able to execute SQL queries. - Support multi-master writes: The solution must support writes across multiple locations simultaneously. - Guarantee low-latency read operations: The database must provide fast read operations, ideally in a global context. Evaluation of Possible Solutions: A) Azure Cosmos DB SQL API - SQL Support: Cosmos DB with the SQL API supports a subset of SQL-like queries, but it is not a full relational database and does not support all SQL commands. - Multi-master Writes: Cosmos DB is designed to support multi-master writes, allowing writes to be made from multiple locations across the globe simultaneously. It’s highly available and distributed. - Low-Latency Reads: Cosmos DB guarantees low-latency read operations with its globally distributed architecture, allowing data to be cached and read from the nearest location. - Why selected: Cosmos DB supports SQL-like commands, multi-master writes, and low-latency reads. It is ideal for globally distributed applications that require fast, low-latency reads and support multi-master writes. B) Azure SQL Database that uses Active Geo-Replication - SQL Support: Azure SQL Database supports full SQL commands, making it a good fit for this requirement. - Multi-master Writes: Active geo-replication in Azure SQL Database supports read-only replicas in different regions, but it does not support multi-master writes (i.e., it doesn’t allow writes to occur in multiple locations simultaneously). It only supports writes in the primary region, which limits its applicability for multi-master writes. - Low-Latency Reads: Geo-replication helps with low-latency reads from read replicas, but since writes are limited to the primary region, this ...

Author: Ava · Last updated Jul 28, 2026

SNAPSHOT - You have an Azure subscription that contains the SQL servers on Azure shown in the following table. The subscription contains the storage accounts shown in the following table. You create the Azure SQL databases shown in the following table. For each of the following state...

Author: Sam · Last updated Jul 28, 2026

DRAG DROP - You plan to import data from your on-premises environment to Azure. The data is shown in the following table. What should you recommend using to migrate the data? To answer, drag the appropriate tools to the correct data sources. Each tool may be used once, more than once, or not at all. You may n...

Author: Mia · Last updated Jul 28, 2026

You store web access logs data in Azure Blob Storage. You plan to generate monthly reports from the access logs. You need to recommend an automated process to upload the data to A...

To generate monthly reports from Azure Blob Storage and upload the access logs data to Azure SQL Database, an automated process is required that can handle scheduled tasks and data transformations. Let’s analyze each option: A) Microsoft SQL Server Migration Assistant (SSMA) - Overview: SSMA is a tool designed for migrating databases from different database systems to SQL Server or Azure SQL Database. It supports converting schemas, data, and objects from supported sources like Oracle, MySQL, and others. - Rejection Reason: SSMA is not an ideal solution for automating the process of uploading data from Azure Blob Storage to Azure SQL Database. It is a one-time migration tool and not designed for regular, automated transfers, especially for ongoing tasks like monthly uploads. - Use case: Useful when migrating from another database to SQL Server or Azure SQL Database, but not for ongoing data uploads or scheduled processes. B) Data Migration Assistant (DMA) - Overview: DMA is used to assess the readiness of a database for migration to SQL Server or Azure SQL Database. It helps to identify potential compatibility issues but does not facilitate the transfer of actual data. - Rejection Reason: Like SSMA, DMA is more about assessing migration readiness rather than transferring data regularly. It is not designed for automating the process of monthly data uploads. - Use case: Best suited for assessing the migration process, but not for automating data uploads or transfers. C) AzCopy - Overview: AzCopy is a command-line tool used for cop...

Author: Kai99 · Last updated Jul 28, 2026

You have an Azure subscription. Your on-premises network contains a file server named Server1. Server1 stores 5 TB of company files that are accessed rarely. You plan to copy the files to Azure Storage. You need to implement a storage solution for the files that meets the following requirements: * The files must be available within 24 hours of being requested. * Storage costs must b...

To select the appropriate storage solutions, let's analyze the requirements and available options: Requirements: - Availability: The files must be accessible within 24 hours upon request. - Cost efficiency: Storage costs must be minimized, meaning we should consider using the lower-cost storage tiers for infrequently accessed data. Let's go through each option: A) Create an Azure Blob Storage account that is configured for the Cool default access tier. Create a blob container, copy the files to the blob container, and set each file to the Archive access tier. - Analysis: The Cool access tier is designed for infrequently accessed data, which is a good fit for the files. However, the Archive access tier is designed for very rarely accessed data, where retrieval times could take hours to days. This violates the requirement of having files available within 24 hours. - Rejection Reason: Archive tier does not meet the 24-hour access requirement. It is meant for data that can tolerate longer retrieval times, typically 1-2 hours or more. - Use case: Not suitable due to access delay concerns. B) Create a general-purpose v1 storage account. Create a blob container and copy the files to the blob container. - Analysis: General-purpose v1 storage accounts are now outdated and lack many features and optimizations available in the general-purpose v2 accounts. Furthermore, the storage costs for v1 accounts are higher, and they don’t offer as much flexibility with access tiers. - Rejection Reason: General-purpose v1 accounts are not cost-effective compared to the newer v2 accounts, and they lack the enhanced features required for this scenario. - Use case: Not suitable due to outdated features and higher costs. C) Create a general-purpose v2 storage account that is configured for the Cool default access tier. Create a file share in the storage account and copy the files to the file share. - Analysis: A general-purpose v2 storage account supports both Blob and File storage and allows better flexibility with access tiers. The Cool tier is suitable for infrequently accessed data. However, using a file share is more appropriate for scenarios where SMB or NFS access is required. Since the goal is to minimize storage costs and access rarely, a blob container in...

Author: NebulaEagle11 · Last updated Jul 28, 2026

You have an app named App1 that uses two on-premises Microsoft SQL Server databases named DB1 and DB2. You plan to migrate DB1 and DB2 to Azure You need to recommend an Azure solution to host DB1 and DB2. The solution must meet the following requirements: * Support server-side...

Analysis of the Requirements: The solution must meet these two primary requirements: 1. Support server-side transactions across DB1 and DB2: This means the solution needs to allow transactions that span both databases on the same server or instance. 2. Minimize administrative effort to update the solution: The solution should be easy to maintain and update without requiring extensive manual intervention. Let's evaluate each option: A) Two Azure SQL databases in an elastic pool - Overview: An elastic pool allows multiple Azure SQL databases to share resources like CPU, memory, and storage within a defined resource pool. Each database is independent but can scale based on demand. - Rejection Reason: While elastic pools are cost-effective for managing multiple databases, they do not support server-side transactions across databases. Transactions spanning databases within an elastic pool are not natively supported by Azure SQL Database. The databases in an elastic pool are isolated from one another, meaning cross-database transactions are not possible. - Use case: Elastic pools are ideal for databases with varying usage patterns, but they are not suitable for scenarios requiring server-side transactions across databases. B) Two databases on the same Azure SQL managed instance - Overview: An Azure SQL Managed Instance provides a fully managed SQL Server instance with SQL Server features, including support for cross-database transactions. Managed instances support a broader set of SQL Server features compared to individual Azure SQL Databases, including support for server-level operations like linked servers and cross-database transactions. - Selection Reason: This is the ideal option for the requirements because: - It supports server-side transactions across multiple databases (DB1 and DB2) since both databases reside within the same SQL Managed Instance. - Azure SQL Managed Instances are fully managed by Microsoft, which minimizes administrative overhead for updates, backups, and maintenance tasks. - Use case: This solution is best when there...

Author: Rahul · Last updated Jul 28, 2026

You need to design a highly available Azure SQL database that meets the following requirements: * Failover between replicas of the database must occur without any data loss. * The database must remain available in th...

Requirements: - Failover without data loss: The solution should support automatic failover with no data loss, which implies synchronous replication. - Availability during zone outages: The database must remain available even during a zone outage, which requires zone-redundant or multi-region support. - Cost minimization: The solution should minimize costs while meeting the above requirements. Let's evaluate each option: A) Azure SQL Database Hyperscale - Overview: Azure SQL Database Hyperscale is a high-performance tier that supports large-scale databases with auto-scaling of compute and storage. It provides zone-redundant replicas and automatic failover between replicas. - Selection Reason: Hyperscale provides zone-redundant replicas and automatic failover, ensuring that the database remains available even during zone outages. It also supports no data loss during failover because of the synchronous replication between replicas. However, it can be more expensive compared to other options due to its high scalability and performance features. - Use case: This option would be ideal for high-performance and large-scale database requirements but may be more expensive than needed for cost-sensitive scenarios. B) Azure SQL Database Premium - Overview: The Premium tier in Azure SQL Database provides high-performance storage, low-latency data access, and high availability with auto-failover groups. It can support multi-region configurations for availability during zone or regional outages. - Selection Reason: The Premium tier supports high availability with auto-failover and no data loss between replicas, especially in a zone-redundant configuration. It ensures that the database remains available even during zone outages. However, the Premium tier is typically more expensive compared to the standard or general-purpose tiers. - Rejection Reason: While it meets all the requirements for high availability and no data loss, the Premium tier is costly, and the solution could be overkill if the goal is to minimize costs. - Use case: Best for enterprise-level applications requiring high availability, performance, and minimal latency, but ...

Author: Maya · Last updated Jul 28, 2026

SNAPSHOT - You are planning an Azure Storage solution for sensitive data. The data will be accessed daily. The dataset is less than 10 GB. You need to recommend a storage solution that meets the following requirements: * All the data written to storage must be retained for five years. * Once the data is written, the data can only be read. Modifications and deletion must be prevented. * After five years, the data can be deleted, but never modifi...

Author: Mia · Last updated Jul 28, 2026

SNAPSHOT - You are designing a data storage solution to support reporting. The solution will ingest high volumes of data in the JSON format by using Azure Event Hubs. As the data arrives, Event Hubs will write the data to storage. The solution must meet the following requirements: * Organize data in directories by date and time. * Allow stored data to be queried directly, transformed into summarized tables, and then stored in a data warehouse. * Ensure that the data warehouse can store 50 TB of relational data and support be...

Author: Olivia · Last updated Jul 28, 2026

You have an app named App1 that uses an on-premises Microsoft SQL Server database named DB1. You plan to migrate DB1 to an Azure SQL managed instance. You need to enable customer managed Transparent Data Encryption (TDE) for the instance. The solution must maxim...

Analysis of the Requirement: You are migrating a database (DB1) to an Azure SQL managed instance and need to enable customer-managed Transparent Data Encryption (TDE) to maximize encryption strength. The goal is to choose the most secure encryption algorithm and key length for TDE. Key Factors for Selection: 1. Transparent Data Encryption (TDE) is designed to protect the database files at rest by encrypting the data with an encryption key. When using customer-managed TDE, you manage the keys rather than relying on Azure's default encryption. 2. Encryption Algorithm: You are selecting the encryption algorithm and key length that will be used for the TDE protector. 3. Strength of Encryption: Generally, stronger encryption algorithms or longer key lengths provide better security but might have a performance trade-off. 4. Recommendation: Azure SQL Managed Instance supports a RSA key or AES encryption for TDE. Among the key options, RSA and AES algorithms are both supported, but the key length and algorithm strength vary. Breakdown of Options: - Option A: RSA 3072 - RSA with 3072-bit key is a very secure encryption key. It provides a strong level of encryption while maintaining a good balance of security and performance. - However, compared to 4096-bit RSA, 3072-bit is a slightly weaker encryption. It is still considered secure but would not provide the maximum encryption strength. - Option B: AES 256 - AES 256-bit encryption is one of the most secure symmetric encryption algorithms available. AE...

Author: Isabella · Last updated Jul 28, 2026

You are planning an Azure IoT Hub solution that will include 50,000 IoT devices. Each device will stream data, including temperature, device ID, and time data. Approximately 50,000 records will be written every second. The data will be visualized in near real time. You need to recommend a service to store and query the data....

Analysis of the Requirements: - You are dealing with an IoT solution where 50,000 devices are streaming data, including temperature, device ID, and time, resulting in 50,000 records per second. - The data will need to be visualized in near real-time. - The solution requires efficient data storage and querying capabilities to handle high ingestion rates and enable real-time access for visualization. Breakdown of the Options: 1. Option A: Azure Table Storage - Azure Table Storage is a NoSQL service that can store large amounts of structured data in the form of key-value pairs. However, it's designed for simple storage and basic querying, not for handling real-time analytics or high-throughput data. - Table Storage is not optimized for time-series data or real-time visualization, and it does not support advanced querying capabilities like range queries on time data, which are critical in this scenario for efficient visualization of time-series data. - Rejected: While Azure Table Storage can store data, it’s not ideal for real-time querying or time-series data that needs to be visualized frequently. 2. Option B: Azure Event Grid - Azure Event Grid is an event routing service that allows for event-driven architecture but does not store data. It’s designed for event handling rather than data storage and querying. - It is used to route events (like device-generated data) to other services but doesn't provide storage or querying capabilities for the data. - Rejected: Event Grid does not fit the requirement for storing and querying the data itself, as it’s focused on event routing. 3. Option C: Azure Cos...

Author: Sofia · Last updated Jul 28, 2026

SNAPSHOT - You are planning an Azure Storage solution for sensitive data. The data will be accessed daily. The dataset is less than 10 GB. You need to recommend a storage solution that meets the following requirements: * All the data written to storage must be retained for five years. * Once the data is written, the data can only be read. Modifications and deletion must be prevented. * After five years, the data can be deleted, but never ...

Author: Sofia · Last updated Jul 28, 2026

SNAPSHOT - You are designing a data analytics solution that will use Azure Synapse and Azure Data Lake Storage Gen2. You need to recommend Azure Synapse pools to meet the following requirements: * Ingest data from Data Lake Storage into hash-distributed tables. * Implement query, and update data in Delta Lake. What should yo...

Author: Lina Zhang · Last updated Jul 28, 2026

You have an on-premises storage solution. You need to migrate the solution to Azure. The solution must support Hadoop Di...

To migrate an on-premises storage solution to Azure that needs to support the Hadoop Distributed File System (HDFS), let's evaluate each of the given options based on key factors such as compatibility with HDFS, scalability, performance, and data management features. A) Azure Data Lake Storage Gen2 - Supports HDFS: Azure Data Lake Storage Gen2 is built on top of Azure Blob Storage and provides HDFS compatibility. This allows the Hadoop ecosystem to use the same APIs for data storage and access, making it a strong fit for big data workloads like Hadoop. - Scalability and Performance: Data Lake Gen2 offers high scalability and performance with built-in hierarchical namespace support, optimized for big data analytics workloads. - Use Case: Ideal for scenarios where big data workloads (like Hadoop or Spark) require scalable storage and HDFS compatibility in Azure. Key Strengths: - Direct support for HDFS - Scalable and optimized for big data - Integrated with Azure analytics services like HDInsight, Databricks, and others B) Azure NetApp Files - Supports HDFS: Azure NetApp Files is a powerful, high-performance file storage service, but it does not natively support HDFS. - Use Case: It's ideal for applications that require high-performance file shares (like NFS or SMB), but it doesn't cater to the needs of Hadoop workloads, which require a distributed file system like HDFS. Key Strengths: - High performance for specific workloads like NFS...

Author: Ishaan · Last updated Jul 28, 2026

DRAG DROP - You have an on-premises app named App1. Customers use App1 to manage digital images. You plan to migrate App1 to Azure. You need to recommend a data storage solution for App1. The solution must meet the following image storage requirements: * Encrypt images at rest. * Allow files up to 50 MB. * Manage access to the images by using Azure Web Application Firewall (WAF) on Azure Front Door. The solution must meet the following customer account requirements: * Support automatic scale out of the storage. * Maintain the availability of App1 if a datacenter fails. * Support reading and writing data from multiple Azure regions. Which service should you include ...

Author: Sara · Last updated Jul 28, 2026

You are designing an application that will aggregate content for users. You need to recommend a database solution for the application. The solution must meet the following requirements: * Support SQL commands. * Support multi-mast...

Requirement Analysis: Let's go through the requirements and match them with the most appropriate solution: 1. Support SQL commands: The solution must support SQL queries to interact with the database. 2. Support multi-master writes: This means the database should support writing to multiple locations concurrently, allowing updates from multiple regions or nodes simultaneously. 3. Guarantee low-latency read operations: The solution should be optimized for fast read operations, ensuring low-latency performance. Option Evaluation: A) Azure Cosmos DB for NoSQL: - Supports SQL commands: Azure Cosmos DB supports SQL-like queries, but it's fundamentally a NoSQL database designed for key-value and document-based data models. Although you can use SQL syntax, it's not a traditional SQL relational database. - Multi-master writes: Azure Cosmos DB provides multi-master write support. This is one of its key features, allowing writes to multiple regions with automatic conflict resolution. - Low-latency read operations: Cosmos DB is specifically designed to guarantee low-latency reads, especially when the database is distributed across multiple regions. Conclusion: While Azure Cosmos DB excels at low-latency reads and multi-master writes, it doesn't fully support traditional SQL commands (it uses SQL-like queries), so it doesn’t entirely meet the requirement for SQL support. B) Azure SQL Database that uses active geo-replication: - Supports SQL commands: Azure SQL Database fully supports SQL commands as it's a relational database. - Multi-master writes: Azure SQL Database using active geo-replication does not support multi-master writes. It only supports one writable primary database and multiple read-only replicas in other regions. - Low-latency read operations: This solution provides low-latency reads, but since the write operat...

Author: BlazingPhoenix22 · Last updated Jul 28, 2026

You plan to migrate on-premises MySQL databases to Azure Database for MySQL Flexible Server. You need to recommend a solution for the Azure Database for MySQL Flexible Server configuration. The solution must meet the following requirements: * The databases ...

Requirements: 1. Databases must be accessible if a datacenter fails: This implies that the solution must provide high availability or a failover capability. 2. Costs must be minimized: The solution should be cost-effective, minimizing unnecessary overhead while meeting the other requirements. Evaluation of Options: A) Burstable: - High Availability: The Burstable compute tier in Azure Database for MySQL Flexible Server does not offer the high availability feature out of the box. It is designed for low-cost, low-performance needs, where workloads are expected to have variable CPU usage (bursting). - Cost: The Burstable tier is the least expensive option in terms of compute resources, which may seem cost-effective at first glance. - Use case: This tier is ideal for development or test environments, or very light workloads that do not require high availability or constant performance. Conclusion: While Burstable is cost-effective, it does not meet the requirement for high availability or datacenter failover. Therefore, it is not a suitable option for this scenario. B) General Purpose: - High Availability: The General Purpose tier supports high availability (HA) configurations with automatic failover, which ensures that databases remain accessible if a datacenter fails. - Cost: The General Purpose tier is more cost-effective than the Memory Optimized tier and is designed to provide a balanced solution with sufficient performance for most production workloads. It offers a good balance between cost and reliability. - Use case: This tier is ideal for most g...

Author: Isabella · Last updated Jul 28, 2026

You are designing an app that will use Azure Cosmos DB to collate sales from multiple countries. You need to recommend an API for the app. The solution must meet the following requirements: * Support SQL queries. * Su...

Requirements: 1. Support SQL queries: The app needs to support relational queries using SQL. 2. Support geo-replication: The solution must allow data to be replicated across multiple regions for availability and resilience. 3. Store and access data relationally: The solution should be able to store data in a relational model, where tables and relationships are used. Evaluation of Options: A) Apache Cassandra: - SQL queries: Apache Cassandra does not support traditional SQL queries. It uses a query language called CQL (Cassandra Query Language), which is similar to SQL in syntax, but it is designed specifically for Cassandra's NoSQL data model and does not support relational queries in the same way as traditional relational databases. - Geo-replication: Cassandra natively supports geo-replication, and it can automatically replicate data across multiple regions. - Relational data: Cassandra is a NoSQL database designed for highly scalable, distributed systems. It does not store data relationally and lacks support for the features typically associated with relational databases, such as joins, foreign keys, and normalization. Conclusion: While Apache Cassandra supports geo-replication, it does not meet the requirement for relational data storage or SQL queries. Therefore, it is not a suitable choice for this app. B) PostgreSQL: - SQL queries: PostgreSQL is a relational database that fully supports SQL queries, making it an excellent fit for applications that need to perform relational data operations. - Geo-replication: PostgreSQL, when used with Azure Database for PostgreSQL, can support geo-replication via features such as read replicas in different regions, but native cross-region replication is not as seamless as some other solutions (e.g., Cosmos DB's multi-region support). - Relational data: PostgreSQL is a relational database, so it supports relational data storage, with tables, constraints, joins, and other relational features. Conclusion: PostgreSQL supports SQL queries and relational data but does not natively offer as seamless a geo-replication solution as Cosmos DB, esp...

Author: Lina Zhang · Last updated Jul 28, 2026

SNAPSHOT - You have an app that generates 50,000 events daily. You plan to stream the events to an Azure event hub and use Event Hubs Capture to implement cold path processing of the events. The output of Event Hubs Capture will be consumed by a reporting system. You need to identify which type of Azure storage must be provisioned to support Event Hubs Capture, and which inbound data format th...

Author: Mia · Last updated Jul 28, 2026

You have the resources shown in the following table. CDB1 hosts a container that stores continuously updated operational data. You are designing a solution that will use AS1 to analyze the operational data daily. You need to recommend a solution to analyze the d...

To design a solution that will analyze operational data daily without affecting the performance of the operational data store (CDB1), let's review each option and its suitability based on the key requirements. Key Requirements: 1. Data Analysis: The solution should support daily analysis of continuously updated operational data. 2. Minimize Performance Impact: The solution must not negatively impact the performance of the operational data store (CDB1), meaning that the analysis should be decoupled from the operational store. Review of Each Option: Option A: Azure Data Factory with Azure Cosmos DB and Azure Synapse Analytics connectors - Azure Data Factory (ADF) is used to orchestrate and automate data movement. It can connect to various data sources and perform ETL (Extract, Transform, Load) operations. - However, Azure Data Factory is mainly used for data movement and transformation and typically requires data to be moved from the source to a destination. This can result in data duplication and might affect the performance of the operational data store (CDB1) during the data transfer process. - This option is not ideal because it involves moving data out of CDB1, potentially affecting performance. Option B: Azure Synapse Analytics with PolyBase data loading - Azure Synapse Analytics allows for large-scale data analytics, but using PolyBase to load data from Azure Cosmos DB (CDB1) into Synapse Analytics would typically involve querying data and copying it into a staging area. - PolyBase is a good choice for loading large datasets from various sources into Synapse, but this process may involve significant data movement and impact the performance of CDB1. - This opti...

Author: Kunal · Last updated Jul 28, 2026

SNAPSHOT - You have an Azure subscription. The subscription contains an Azure SQL managed instance that stores employee details, including social security numbers and phone numbers. You need to configure the managed instance to meet the following requirements: * The helpdesk team must see only the last four digits of an employee's phone number. * Cloud administrators must be prevented from seeing the employee's social security...

Author: Joseph · Last updated Jul 28, 2026

You plan to use an Azure Storage account to store data assets. You need to recommend a solution that meets the following requirements: * Supports immutable storage * Disables anonymous access to the storage account * Supports a...

To meet the requirements outlined for the Azure Storage account, let's break down each option and its capabilities based on the given criteria: Requirements: 1. Supports immutable storage: The solution should allow for data to be stored in an immutable state, meaning the data cannot be modified or deleted within a set retention period. 2. Disables anonymous access: The solution should prevent any anonymous (unauthenticated) access to the data stored in the account. 3. Supports access control list (ACL)-based Azure AD permissions: The solution should support granular permissions through ACLs in Azure AD, allowing for fine-grained access control to data. Option A: Azure Files - Immutable storage: Azure Files supports Share snapshots and Azure File Share soft delete but does not have full support for immutable storage policies like retention immutability, which is required for certain regulatory compliance scenarios. - Disables anonymous access: Azure Files supports disabling anonymous access by requiring authentication via Azure AD or other mechanisms. - Supports ACL-based Azure AD permissions: Azure Files supports ACLs via Azure Active Directory (Azure AD) authentication, making it capable of handling permissions at the file and share level. Azure Files is not the best option here because it does not fully support the requirement for immutable storage. Option B: Azure Data Lake Storage - Immutable storage: Azure Data Lake Storage (ADLS) can support immutability via Time-Based Retention policies, which make it suitable for scenarios requiring data retention. It can support immutability features like immutable blob storage. - Disables anonymous access: ADLS can restrict anonymous access by using Azure AD-based authentication and access control, aligning well with the requirement. - Supports ACL-based Azure AD permissions: Azure Data Lake Storage supports ACLs at the file and folder levels using Azure AD, offering fine-grained access control. Azure Data Lake Storage...

Author: Ming88 · Last updated Jul 28, 2026

SNAPSHOT - You are designing a storage solution that will ingest, store, and analyze petabytes (PBs) of structured, semi-structured, and unstructured text data. The analyzed data will be offloaded to Azure Data Lake Storage Gen2 for long-term retention. You need to recommend a storage and analytics solution that meets the following requirements: * Stores the processed data * Provides interactive analytics * Supports manual scaling, built-in au...

Author: Aria · Last updated Jul 28, 2026