You have a Microsoft Dataverse instance named dv1 and an Azure Cosmos DB database named db1.You need to develop a solution to update db1 automatically when a record is updated in dv1. The solution must minimize development effort.What should you include in the solution?
Answer(s): D
Step 1: Azure Connectors, Connect to Microsoft Dataverse from workflows in Azure Logic Apps To create and run automated workflows that create and manage rows in your Microsoft Dataverse database, you can use Azure Logic Apps and the Microsoft Dataverse connector. These workflows can create rows, update rows, and perform other operations. *You can also get information from your Dataverse database and make the output available for other actions to use in your workflows*. For example, when a row is added, updated, or deleted in your Dataverse database, you can send an email by using the Office 365 Outlook connector.Step 2: Azure Connectors, Process and create Azure Cosmos DB documents using Azure Logic Apps From your workflow in Azure Logic Apps, you can connect to Azure Cosmos DB and work with documents by using the Azure Cosmos DB connector. This connector provides triggers and actions that your workflow can use for Azure Cosmos DB operations. For example, actions include creating or updating, reading, querying, and deleting documents.Add Azure Cosmos DB actionIn Azure Logic Apps, an action is a step in your workflow that follows a trigger or another action. The Azure Cosmos DB connector offers actions for both the Logic App (Consumption) and Logic App (Standard) resource types.
HOTSPOT (Drag and Drop is not supported)You have an Azure subscription that contains an Azure Data Lake Storage Gen2 account named storage1. Storage1 contains semi-structured sales data in Parquet files.You ingest, transform, analyze, and visualize the sales data daily. During the transformations, the data is referenced against Microsoft Dataverse and consumed by Microsoft Power BI.You need to deploy a new a data integration and analysis solution in Microsoft Fabric. The solution must meet the following requirements:Minimize the duplication of data.Minimize how long it takes to generate reports in Power BI.What should you use to reference the Dataverse data and consume the transformed data from Power BI? To answer, select the appropriate options in the answer area.Note: Each correct selection is worth one point.Hot Area:
Answer(s): A
Box 1: A OneLake shortcutReference the Dataverse dataLink your Dataverse environment to Microsoft Fabric and unlock deep insightsWith shortcuts from Dataverse directly into OneLake, your data stays in Dataverse while authorized users get to work with data in Fabric.Box 2: A SQL analytics endpointConsume the transformed data from Power BIWork with Dataverse data and generate Power BI reportsYou can work with Dataverse data in Fabric and generate reports in Power BI.Work with Dataverse data in FabricYou can view the Azure Synapse Analytics lakehouse, SQL endpoint, and the default dataset generated by Dataverse in the Fabric workspaceWhen you select Link to Microsoft Fabric, a Dataverse generated Azure Synapse Analytics lakehouse opens. You can go to other Fabric features and work with Fabric and Power BI.Explore the Dataverse generated Azure Synapse Analytics lakehouse The tables you selected are added to the Azure Synapse Analytics lakehouse and displayed in Power BI as shown below. These tables are linked to your Power Platform environment using Dataverse shortcuts. As data changes in Dataverse, the Dataverse shortcuts in Fabric reflect the latest data.Note that Dataverse manages these shortcuts. You shouldn’t delete or remove these shortcuts in Fabric. If you accidentally delete a link, you can go to the Azure Synapse Link for Dataverse area in Power Apps and select Refresh Fabric links to re-create the links.
https://learn.microsoft.com/en-us/power-apps/maker/data-platform/azure-synapse-link-view-in-fabric
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 the event of a zone outage.Costs must be minimized.Which deployment option should you use?
To design a highly available Azure SQL database that meets the specific requirements:Failover without any data loss: The Business Critical tier in Azure SQL Database uses a high availability model with synchronous data replication to multiple replicas, ensuring zero data loss during failover. This is essential for your requirement of no data loss.Available during a zone outage: The Business Critical service tier supports Zone Redundant Configuration, allowing you to place replicas in different availability zones, ensuring the database remains available even if a zone experiences an outage.Cost minimization: While Azure SQL Database Business Critical is more expensive than other options like Standard or Hyperscale, it offers a balance between high availability and the required zero data loss. Other options like Managed Instance Business Critical would be more costly because of additional features beyond what’s needed here, such as more extensive SQL Server instance-level features.Here’s why other options don’t fit as well:Azure SQL Managed Instance Business Critical: This also offers zero data loss and high availability, but it is costlier than the standalone Azure SQL Database.Azure SQL Database Standard: This is a lower-cost option but doesn’t guarantee zero data loss or provide zone redundancy.Azure SQL Database Hyperscale: Hyperscale is designed for massive scale but doesn’t natively support zone redundancy or zero-data-loss failover as well as Business Critical.
HOTSPOT (Drag and Drop is not supported)You have an on-premises Microsoft SQL Server database named DB1.You have an Azure subscription.You need to migrate DB1 to an Azure SQL managed instance. The solution must meet the following requirements:Support offloading read-only workloads to secondary replicas.Provide resiliency in the event of an Azure region outage.Support up to 16 TB of storage.Minimize costs.Which service tier and feature should you include in the solution? To answer, select the appropriate options in the answer area.Note: Each correct selection is worth one point.Hot Area:
To meet the requirements for migrating DB1 to an Azure SQL Managed Instance, the following service tier and feature should be selected:Service Tier – Business CriticalThe Business Critical tier allows for read scale-out, enabling offloading of read-only workloads to secondary replicas. It also provides high availability with replication across multiple zones and support for up to 16 TB of storage. This ensures resiliency in case of a region outage, as needed in the solution.Feature – Failover groupA Failover group provides automatic failover of a managed instance between different regions, ensuring that the solution remains available in the event of an Azure region outage. It supports geo-replication and enhances disaster recovery capabilities, which aligns with the resiliency requirement.
HOTSPOT (Drag and Drop is not supported)You have an Azure subscription.You plan to deploy an app that requires an Azure Data Lake Storage Gen2 account.You need to recommend which settings to modify during the storage account deployment. The solution must ensure that the data in the account is protected if an attacker gains access to the physical disk that stores the data.Which two settings should you recommend? To answer, select the appropriate settings in the answer area.Note: Each correct selection is worth one point.Hot Area:
Box 1: Infrastructure encryptionEnable infrastructure encryption for double encryption of data Infrastructure encryption can be enabled for the entire storage account, or for an encryption scope within an account. When infrastructure encryption is enabled for a storage account or an encryption scope, data is encrypted twice – once at the service level and once at the infrastructure level – with two different encryption algorithms and two different keys.Double encryption of Azure Storage data protects against a scenario where one of the encryption algorithms or keys might be compromised. In this scenario, the additional layer of encryption continues to protect your data.Box 2: Allow access fromWe see: Allow access from: All networkIn Firewalls and virtual networks set Allow access from: to Allow public access from specific virtual networks and IP addresses.Under Exception, check Allow trusted Microsoft services to bypass this firewall.NoteYou can also set Allow access from: to Allow public access from all networks.
https://learn.microsoft.com/en-us/azure/storage/common/infrastructure-encryption-enable https://learn.microsoft.com/en-us/azure/databricks/connect/storage/tutorial-azure-storage
Post your Comments and Discuss Microsoft AZ-305 exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the AZ-305 content, but please register or login to continue.