Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.You have an Azure key vault named KeyVault1 that contains secrets.You have a Fabric workspace named Workspace1. Workspace contains a notebook named Notebook1 that performs the following tasks:-Loads stage data to the target tables in a lakehouse-Triggers the refresh of a semantic modelYou plan to add functionality to Notebook1 that will use the Fabric API to monitor the semantic model refreshes.You need to retrieve the registered application ID and secret from KeyVault1 to generate the authentication token.Solution: You use the following code segment:Use notebookutils.credentials.putSecret and specify the key vault URL and the name of a linked service.Does this meet the goal?
Answer(s): B
Correct: * You use the following code segment:Use notebookutils.credentials.getSecret and specify the key vault URL and key vault secret.[Use getSecret, key vault URL, and key vault secret]Incorrect:* You use the following code segment:Use notebookutils.credentials.putSecret and specify the key vault URL and key vault secret.[Not putsecret]* You use the following code segment:Use notebookutils.credentials.putSecret and specify the key vault URL and the name of a linked service.[Not putsecret]* You use the following code segment:Use notebookutils.credentials.getSecret and specify the key vault URL and the name of a linked service.[not name of linked service]Note: Help on module notebookutils.credentials in notebookutils:NAME notebookutils.credentials - Utility for credentials operations in FabricFUNCTIONS getSecret(akvName, secret) -> str Gets a secret from the given Azure Key Vault. :param akvName: The name of the Azure Key Vault. :param secret: The name of the secret. :return: The secret value.notebookutils.credentials.getSecret('https://<name>.vault.azure.net/', 'secret name')
https://learn.microsoft.com/en-us/fabric/data-engineering/notebook-utilities
You have a Fabric workspace named Workspace1 that uses version control. Workspace1 and Azure DevOps are integrated.In Azure DevOps, developers create a branch named Branch1 to test extract, transform, and load (ETL) updates.You need to connect Workspace1 to Branch1. The solution must ensure that all the existing content in Branch1 is available in Workspace1.What should you do?
To connect your new Azure DevOps branch to your Microsoft Fabric workspace while ensuring all existing ETL updates are preserved and visible, you must update the Workspace Settings.The correct method is to manually switch the branch in the Workspace settings and Sync [better than the suggested Commit] the content Step-by-Step Connection Process Follow these steps to link your existing ETL test branch to your Fabric workspace: 1. Open Workspace Settings Navigate to your target Fabric workspace. Select Workspace settings (cog icon).2. Access Git Integration Go to the Git integration tab. Verify the Organization, Project, and Repository match your Azure DevOps setup.3. Switch the Branch Locate the Branch dropdown menu. Select the new branch you created for ETL updates.4. Connect and Sync Click Connect. Fabric will detect a mismatch between the workspace and the branch. Choose the option to Sync from Git to Workspace.Incorrect: [Not A] You must select the new branch.[Not C] To connect your new Azure DevOps branch to your Microsoft Fabric workspace while ensuring all existing ETL updates are preserved and visible, you must update the Workspace Settings.[Not D] The "Branch out to new workspace" feature is designed for a different workflow: Purpose: It creates a new branch and a new workspace simultaneously.Conflict: Since your branch already exists in Azure DevOps, using this feature would attempt to create a duplicate or result in an error. Outcome: To use existing content, you must use the Git Integration settings to point the workspace to the existing remote branch.
https://learn.microsoft.com/en-us/fabric/cicd/git-integration/manage-branches
HOTSPOT (Drag and Drop is not supported) (Drag and Drop is not supported)You have a Fabric workspace.You plan to deploy two Apache Spark environments that will each contain one of the following notebooks:-Notebook1: A data ingestion notebook that will run as a scheduled Spark job-Notebook2: An ad hoc notebook for interactive data analysis that will be used by a team of analysts and data scientistsYou need to configure the Spark environments to meet the following requirements:-For the environment that contains Notebook1, minimize compute costs.-For the environment that contains Notebook2, support multiple concurrent users.What should you use for each environment? 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 custom Spark pool that has a single small node and high concurrency mode enabled. Environment for Notebook1To deploy an Apache Spark environment in Microsoft Fabric that minimizes compute costs while meeting your requirements, follow these steps to configure a custom Spark pool with a single small node and enable high concurrency mode. 1. Create the Custom Spark Pool Custom pools allow you to define specific node sizes to match your budget and workload.2. Configure the Environment Environments act as reusable containers for Spark settings, including the pool and concurrency options.3. Enable High Concurrency Mode High concurrency allows multiple notebooks to share a single Spark session, which is significantly cheaper than starting a new session for every job.4. Deploy and Schedule the NotebookBox 2: A starter pool Environment for Notebook2To deploy an Apache Spark environment in Microsoft Fabric that supports multiple concurrent users for interactive analysis using a starter pool, follow these steps:1. Configure the Workspace for Starter Pools By default, Microsoft Fabric workspaces use Starter Pools. These pools are pre-configured, "always-on" clusters that provide fast session startup (5-10 seconds) compared to custom pools.2. Enable High Concurrency Mode To allow multiple users or multiple notebooks to share a single Spark session efficiently, you must enable High Concurrency Mode. This reduces the overhead of starting new sessions for every user.3. Create and Attach a Notebook Once the workspace is configured, create the ad-hoc notebook for your analysts.
https://blog.fabric.microsoft.com/sv-se/blog/announcing-general-availability-of-high-concurrency-mode-for-notebooks-in-pipelines/ https://learn.microsoft.com/en-us/fabric/data-engineering/configure-starter-pools
You have a Fabric workspace named Workspace1 that contains a lakehouse named Lakehouse1.You perform the following actions:-Connect Workspace1 to a Git repository and select the main branch.-Create a new branch named feature1 and modify Lakehouse1.-Merge the changes from feature1 into the main branch.You need to ensure that the changes are available in Workspace1. The solution must minimize changes to Workspace1.What should you do?
In a Microsoft Fabric workspace integrated with Git, once you have merged changes into the main branch via your Git provider (such as Azure DevOps or GitHub), the workspace does not automatically reflect those changes.To synchronize the workspace with the updated main branch while minimizing manual rework, you should follow these steps from the workspace: Open Source Control: Select the Source control icon at the top of the workspace.Navigate to Updates: In the Source control pane, select the Updates tab. This tab displays a list of all items that have been modified, added, or deleted in the Git branch since the last sync.Sync Changes: Select Update all to apply the changes to the workspace.
https://data-marc.com/2024/06/25/fabric-git-branching-with-the-new-branch-out-option-how-it-works-and-what-you-should-keep-in-mind
HOTSPOT (Drag and Drop is not supported) (Drag and Drop is not supported)You have a Fabric warehouse named Warehouse1 that contains a table named Table1. Table1 contains the following columns that store string values: ● FirstName ● Phone ● EmailYou have two Microsoft Entra security groups named Group1 and Group2. The members of both groups can query Table1 and see full values for FirstName, Phone, and Email.You need to configure Table1 to meet the following requirements: ● The members of Group1 must see masked values for Phone, showing only the last three characters of each phone number. ● The Group1 members must see unmasked values for FirstName. ● The members of Group2 must see unmasked values for all the columns. ● The solution must use Fabric warehouse-supported permissions and T-SQL.What should you configure? To answer, select the appropriate options in the answer area.Note: Each correct selection is worth one pointHot Area:
Box 1: partial() The partial() function (also referred to as a custom string mask) is the correct masking function to use.To show only the last three characters of a phone number while masking the rest, you define the column with a T-SQL MASKED WITH clause using partial(0, 'string_padding', 3).Box 2: UNMASK at the database scope To allow the members of Group2 to see unmasked values for all columns, you must grant them the UNMASK permission using T-SQL.You can grant this permission to Group2 at either the table scope or the entire database level:Table-level scope (Recommended for precision): GRANT UNMASK ON dbo.YourTableName TO [Group2];Database-level scope: GRANT UNMASK TO [Group2];Incorrect: UNMASK on Table1(FirstName)Would unmask only this one specific column.
https://learn.microsoft.com/en-us/sql/relational-databases/security/dynamic-data-masking
Post your Comments and Discuss Microsoft DP-700 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 DP-700 content, but please register or login to continue.