1. An organization is using Microsoft Fabric for its data analytics needs and wants to implement a robust monitoring solution. They need to track the performance and resource consumption of their Fabric capacities, identify bottlenecks, and optimize workload distribution across different engines (e.g., Spark, SQL, Power BI). Which built-in Fabric tool is specifically designed for these monitoring and optimization tasks?
Govern and administer Fabric (10-15%)
A.Microsoft Purview Data Map
B.Fabric Activity Log
C.Capacity Metrics app
D.Workspace Usage Metrics
Show answerAnswer
C. Capacity Metrics app
The Capacity Metrics app is a pre-built monitoring solution in Microsoft Fabric that provides detailed insights into the performance, resource utilization, and workload distribution of Fabric capacities, allowing administrators to identify bottlenecks and optimize their environment.
2. A data platform administrator is setting up a new Microsoft Fabric environment for a company that prioritizes data residency. They need to ensure that all data processed and stored within Fabric remains within a specific geographical region to comply with local regulations. Which setting or configuration is paramount to achieve this data residency requirement for all new Fabric workspaces and items?
Govern and administer Fabric (10-15%)
A.Setting the default storage account location in Azure.
B.Configuring workspace location during creation.
C.Selecting the Fabric capacity region.
D.Enforcing data residency via Azure Private Link.
Show answerAnswer
C. Selecting the Fabric capacity region.
The region of the assigned Fabric capacity directly dictates where all data processing and storage for workspaces linked to that capacity will occur. To ensure data residency, all capacities must be provisioned in the required geographical region.
3. A company is migrating its data analytics workloads to Microsoft Fabric. They have a strict policy that all sensitive data must be encrypted at rest using customer-managed keys (CMK) for enhanced security and compliance. How can the Fabric administrator ensure that all data stored in Fabric workspaces associated with a specific F-SKU capacity is encrypted using CMK?
Govern and administer Fabric (10-15%)
A.Configure CMK encryption at the individual Lakehouse or Data Warehouse item level.
B.Implement CMK encryption via Azure Policy assignments for Fabric resources.
C.Enable Azure Storage account CMK encryption for the underlying OneLake storage.
D.Assign an Azure Key Vault key to the Fabric capacity in the Admin portal.
Show answerAnswer
D. Assign an Azure Key Vault key to the Fabric capacity in the Admin portal.
Customer-managed keys (CMK) for Microsoft Fabric are configured at the capacity level. By assigning an Azure Key Vault key to a Fabric capacity in the Admin portal, all data stored within that capacity's OneLake storage will be encrypted using the specified CMK, fulfilling the requirement.
4. A data administrator needs to restrict the ability of users to create new workspaces in Microsoft Fabric. The goal is to centralize workspace creation through a dedicated team to ensure compliance with naming conventions, capacity assignments, and data governance policies. Which tenant setting should the administrator configure to achieve this?
Govern and administer Fabric (10-15%)
A.Allow users to create workspaces (new workspace experience)
B.Allow users to create apps
C.Allow users to create and use OneLake shortcuts
D.Allow users to create datasets
Show answerAnswer
A. Allow users to create workspaces (new workspace experience)
The 'Allow users to create workspaces (new workspace experience)' tenant setting directly controls whether individual users can create new workspaces in Microsoft Fabric. Disabling this setting or restricting it to specific security groups centralizes workspace creation.
5. A data analytics team has built several critical reports and dashboards in a Microsoft Fabric workspace. They want to ensure that these items remain available even if the underlying data sources or connected services experience temporary outages. They need a mechanism to quickly revert to a previous, stable state of these reports and dashboards if issues arise after a new deployment. Which Fabric feature should they primarily rely on for this recovery capability?
Govern and administer Fabric (10-15%)
A.Item-level sharing permissions
B.Git integration for version control
C.Deployment pipeline rollback
D.Workspace backup and restore
Show answerAnswer
B. Git integration for version control
Git integration provides robust version control for Fabric artifacts (like notebooks, report definitions, etc.), allowing teams to track changes, revert to previous versions, and manage development branches. This is crucial for quickly reverting reports and dashboards to a stable state after deployment issues.
6. A Microsoft Fabric administrator needs to ensure that all data engineers adhere to specific naming conventions for new Lakehouses created within their workspaces to maintain consistency and facilitate easier management. The administrator wants to enforce this policy automatically when a new Lakehouse is provisioned. Which approach should the administrator implement?
Govern and administer Fabric (10-15%)
A.Educate users and rely on manual review processes.
B.Implement Azure Policy definitions for Fabric Lakehouses.
C.Utilize a custom PowerShell script to validate names post-creation.
D.Configure a tenant setting for mandatory naming conventions.
Show answerAnswer
B. Implement Azure Policy definitions for Fabric Lakehouses.
Azure Policy is the correct tool for enforcing naming conventions and other governance rules on Azure resources, including Microsoft Fabric items like Lakehouses. It allows for automatic validation and enforcement during resource creation or update, preventing non-compliant resources from being deployed.
7. A Fabric administrator needs to ensure that all data engineers working on a project adhere to a specific set of coding standards for Python notebooks and Spark definitions. They also want to facilitate code reviews and ensure that only approved code changes are merged into the main development branch. Which Fabric feature, combined with an external service, is best suited to enforce these practices?
Govern and administer Fabric (10-15%)
A.Deployment pipelines with pre-deployment approvals
B.Git integration with Azure DevOps Pull Requests
C.Workspace roles with Contributor permissions
D.Capacity workload settings for Spark
Show answerAnswer
B. Git integration with Azure DevOps Pull Requests
Git integration allows Fabric workspaces to connect to Azure DevOps (or GitHub), enabling version control. Azure DevOps Pull Requests provide the mechanism for code reviews, enforcing coding standards, and requiring approvals before changes are merged into a main branch, ensuring only approved code proceeds.
8. A global manufacturing company uses Microsoft Fabric across several regions. They have a central data engineering team responsible for creating and maintaining core data models and pipelines, which are then deployed to regional workspaces. These regional workspaces are managed by local teams. The central team needs to ensure that changes to the core items are propagated consistently and reliably to all regional workspaces, with proper version control and approval workflows. Which Fabric feature is best suited for this scenario?
Govern and administer Fabric (10-15%)
A.Workspace sharing
B.PowerShell cmdlets for Fabric administration
C.Deployment pipelines
D.Git integration
Show answerAnswer
C. Deployment pipelines
Deployment pipelines in Microsoft Fabric are specifically designed for managing the lifecycle of Fabric items across different environments (e.g., development, test, production). They provide stages, deployment rules, and version control capabilities, making them ideal for consistent and controlled propagation of changes to regional workspaces.
9. A data platform team is managing a critical production Lakehouse in Microsoft Fabric. They need to implement a security measure that ensures data within the Lakehouse can only be accessed by specific service principals and users, even if they have broader permissions at the workspace level. This access control must be granular, applying directly to tables and files within the Lakehouse, and should respect column-level and row-level security definitions. Which security model should the team leverage?
Govern and administer Fabric (10-15%)
A.Role-level security (RLS) and object-level security (OLS) within the Lakehouse
B.Sensitivity labels from Microsoft Purview
C.Microsoft Entra ID (formerly Azure Active Directory) security groups for workspace access
D.Workspace roles and permissions
Show answerAnswer
A. Role-level security (RLS) and object-level security (OLS) within the Lakehouse
Role-level security (RLS) and object-level security (OLS) are implemented directly within the Lakehouse (typically through SQL endpoints or Spark tables) to provide granular access control to rows and columns, respectively. This overrides broader workspace permissions and is the correct approach for securing data within the Lakehouse itself.
10. A global company uses Microsoft Fabric for its analytics platform. Due to strict data governance requirements, they need to track all administrative and user activities within Fabric, such as workspace creation, item deletion, and permission changes. This information is crucial for security audits and compliance. Where should the administrator look to find a comprehensive record of these activities?
Govern and administer Fabric (10-15%)
A.Fabric Capacity Metrics app
B.Microsoft 365 Audit log
C.Azure Monitor activity log
D.Power BI activity log
Show answerAnswer
B. Microsoft 365 Audit log
Microsoft Fabric audit logs are integrated into the Microsoft 365 Audit log (formerly Unified Audit Log). This central log provides a comprehensive record of user and admin activities across Microsoft 365 services, including Fabric, making it the correct source for security audits and compliance.
11. A data analytics department has multiple teams, each working on distinct projects within Microsoft Fabric. They want to implement a solution where each team has its own isolated environment for development and testing, ensuring that changes made by one team do not accidentally affect another. Furthermore, they need a clear separation of billing for the compute resources consumed by each team. How should the Fabric administrator structure their environment to meet these requirements efficiently?
Govern and administer Fabric (10-15%)
A.Use deployment pipelines to isolate development efforts.
B.Create a single workspace for all teams and use item-level permissions.
C.Create separate workspaces for each team, each assigned to its own dedicated Fabric Capacity SKU.
D.Create separate workspaces for each team within a shared capacity.
Show answerAnswer
C. Create separate workspaces for each team, each assigned to its own dedicated Fabric Capacity SKU.
Creating separate workspaces for each team provides logical isolation. Assigning each workspace to its own dedicated Fabric Capacity SKU ensures complete resource isolation, preventing one team's activity from impacting another's performance, and enables accurate chargeback for compute resources, fulfilling all requirements.
12. A data engineering team is developing a critical data pipeline in a Microsoft Fabric workspace. They want to ensure that only authorized users can access the underlying data in the Lakehouse, and that specific columns containing personally identifiable information (PII) are completely hidden from certain roles, even if those roles have access to the table. Which security mechanism should be implemented for the PII columns?
Govern and administer Fabric (10-15%)
A.Object-Level Security (OLS)
B.Workspace item permissions
C.Dynamic Data Masking (DDM)
D.Row-Level Security (RLS)
Show answerAnswer
A. Object-Level Security (OLS)
Object-Level Security (OLS) is the appropriate mechanism to completely hide specific columns (or even tables) from unauthorized users or roles. Unlike RLS, which filters rows, OLS restricts access to entire objects, ensuring that PII columns are not even visible to those without the necessary permissions.
13. A data analytics team is developing several critical reports and dashboards within a Microsoft Fabric workspace. They need to ensure that specific sensitive datasets, which are used in these reports, are not accidentally shared publicly or with unauthorized external users, even if the workspace itself has broader sharing settings. Which Fabric feature should the team leverage to enforce this granular control?
Govern and administer Fabric (10-15%)
A.Workspace item sensitivity labels
B.Information protection policies
C.Item-level sharing permissions
D.Data loss prevention policies
Show answerAnswer
D. Data loss prevention policies
Data loss prevention (DLP) policies are designed to prevent sensitive information from being accidentally or intentionally shared outside of an organization or with unauthorized individuals. While sensitivity labels classify data, DLP policies enforce actions based on those classifications.
14. A data engineering team at a large enterprise is developing several data pipelines in Microsoft Fabric. They need to ensure that all workspaces adhere to specific organizational standards for data classification and sensitivity labels. Which Fabric feature should they leverage to enforce these standards consistently across all new and existing workspaces?
Govern and administer Fabric (10-15%)
A.Deployment pipelines
B.Data gateway configurations
C.Information protection policies
D.Workspace roles and permissions
Show answerAnswer
C. Information protection policies
Information protection policies, often integrated with Microsoft Purview, allow organizations to define and enforce data classification and sensitivity labels across Fabric items, ensuring compliance with organizational standards.
15. A data analytics team needs to integrate a Microsoft Fabric workspace with their existing version control system, Azure DevOps Git, to manage code for notebooks and data pipelines. They want to ensure that all changes are tracked, and a proper branching and merging workflow is followed before deploying to production. Which Fabric feature enables this integration?
Govern and administer Fabric (10-15%)
A.Azure Data Factory integration
B.Git integration for workspaces
C.PowerShell cmdlets for Fabric
D.Fabric deployment pipelines
Show answerAnswer
B. Git integration for workspaces
Fabric's Git integration feature allows workspaces to connect directly to Azure DevOps Git repositories. This enables developers to manage notebooks, data pipelines, and other code artifacts using standard Git workflows, including branching, committing, and pull requests, directly from within the Fabric environment.
16. A company is migrating its entire data estate to Microsoft Fabric. As part of their data governance strategy, they require that all data accessed by Fabric items (e.g., Lakehouses, Data Warehouses, Dataflows) must be encrypted both at rest and in transit. Which security feature is inherently provided by Microsoft Fabric to meet these encryption requirements without additional configuration by the user?
Govern and administer Fabric (10-15%)
A.Microsoft-managed encryption keys with TLS 1.2+ for in-transit data
B.Customer-managed keys (CMK) for data encryption
C.Azure Key Vault integration for secrets management
D.Always Encrypted for SQL endpoints
Show answerAnswer
A. Microsoft-managed encryption keys with TLS 1.2+ for in-transit data
Microsoft Fabric inherently encrypts all data at rest using Microsoft-managed keys (often leveraging Azure Storage Encryption) and encrypts all data in transit using industry-standard protocols like TLS 1.2 or higher. This is a baseline security feature provided by the service.
17. A data engineering team uses a Microsoft Fabric workspace for developing and testing new data pipelines. They frequently create and delete various items like Lakehouses, Notebooks, and Data Pipelines. To maintain an organized and clean workspace, the team wants to automatically remove items that have not been modified for 90 days. Which Fabric feature allows an administrator to configure this automated cleanup?
Govern and administer Fabric (10-15%)
A.Workspace retention policies
B.Data lifecycle management rules
C.Purview data retention labels
D.Item lifecycle policies
Show answerAnswer
D. Item lifecycle policies
Item lifecycle policies in Microsoft Fabric allow administrators to define rules for automatically managing the lifecycle of items within a workspace, including deletion based on inactivity or age, helping to maintain workspace hygiene.
18. A Microsoft Fabric administrator is responsible for managing multiple capacities across different environments (development, test, production). They need to ensure that the development environment capacity does not consume an excessive amount of resources, potentially impacting the test or production environments. The administrator wants to set a maximum resource usage limit specifically for the development capacity. Which Fabric feature enables this type of resource governance?
Govern and administer Fabric (10-15%)
A.Capacity workload settings
B.Fabric tenant settings
C.Workspace resource limits
D.Azure cost management budgets
Show answerAnswer
A. Capacity workload settings
Capacity workload settings in Microsoft Fabric allow administrators to allocate and limit the resources (compute units) for specific workload types (e.g., Data Engineering, Data Warehousing) within a given capacity. This enables fine-grained control over resource consumption and prevents one workload or environment from monopolizing resources.
19. A financial services company uses Microsoft Fabric for its analytics platform. Due to strict regulatory compliance, all data processing activities must be logged and audited for at least seven years. The company needs to monitor all user and system activities within Fabric, including item creation, modification, and access. Which Fabric monitoring capability should the administrator configure to meet this requirement?
Govern and administer Fabric (10-15%)
A.Audit logs in Microsoft Purview compliance portal
B.Power BI activity log connector
C.Capacity Metrics app
D.Workspace Usage Metrics
Show answerAnswer
A. Audit logs in Microsoft Purview compliance portal
Audit logs, accessible through the Microsoft Purview compliance portal, capture detailed user and admin activities across Microsoft 365 services, including Fabric. These logs are crucial for regulatory compliance and can be retained for extended periods.
20. A global conglomerate operates multiple subsidiaries, each with its own data governance requirements. They are implementing Microsoft Fabric and need to provision dedicated capacity for each subsidiary to ensure resource isolation and chargeback. Each subsidiary's capacity must be configured with specific region choices and workload settings to optimize for their unique data processing needs. Which capability within Microsoft Fabric allows for this granular management of dedicated resources?
Govern and administer Fabric (10-15%)
A.Power BI Embedded capacity
B.Fabric Capacity SKUs
C.Data gateway clusters
D.Workspace Premium features
Show answerAnswer
B. Fabric Capacity SKUs
Fabric Capacity SKUs (e.g., F2, F4, F8, etc.) represent dedicated compute resources that can be purchased, assigned to workspaces, and configured with specific regions and workload settings. This allows for resource isolation, chargeback, and granular control over performance and geographical data residency, perfectly matching the scenario's requirements.
21. A large enterprise uses Microsoft Fabric across multiple business units. Each business unit has its own dedicated workspace and needs to track the compute consumption of its Fabric items (e.g., Lakehouses, Data Warehouses, Notebooks) to allocate costs accurately. The central IT team needs a consolidated view of resource utilization across all business units. Which tool or method is BEST suited for this requirement?
Govern and administer Fabric (10-15%)
A.Analyzing Azure Monitor logs for Fabric
B.Reviewing workspace settings for capacity assignments
C.Querying the Fabric Activity Log
D.Monitoring the Fabric Capacity Metrics app
Show answerAnswer
D. Monitoring the Fabric Capacity Metrics app
The Fabric Capacity Metrics app is specifically designed to provide detailed insights into the compute utilization of Fabric capacities, allowing administrators to monitor workloads, track consumption by items and users, and identify opportunities for optimization and cost allocation.
22. A data platform administrator is setting up a new Microsoft Fabric environment. The organization requires that all new workspaces default to a specific set of data retention policies and sensitivity labels. They also want to restrict the types of data sources that can be connected to Fabric items globally. Which administrative setting in the Fabric Admin portal should the administrator configure to achieve these organization-wide defaults and restrictions?
Govern and administer Fabric (10-15%)
A.Capacity settings
B.User settings
C.Tenant settings
D.Workspace settings
Show answerAnswer
C. Tenant settings
Tenant settings in the Fabric Admin portal allow administrators to configure organization-wide policies and defaults, including data retention, sensitivity labels, and allowed data sources. These settings apply across all workspaces within the tenant.
23. A company is implementing a new data analytics solution in Microsoft Fabric. They want to ensure that access to sensitive data stored in a Lakehouse is restricted based on the user's department. Specifically, users from the 'Sales' department should only see sales-related data, and users from 'Marketing' should only see marketing-related data, even when accessing the same Lakehouse table. Which security mechanism in Fabric is MOST appropriate for this scenario?
Govern and administer Fabric (10-15%)
A.Microsoft Entra ID group assignments
B.Workspace roles and permissions
C.Object-Level Security (OLS)
D.Row-Level Security (RLS)
Show answerAnswer
D. Row-Level Security (RLS)
Row-Level Security (RLS) is designed to restrict access to specific rows in a table based on user identity or attributes (like department). This allows different users to see different subsets of data from the same table, which precisely matches the requirement.
24. A data analyst is building a dashboard in Power BI, connected to a SQL endpoint in a Microsoft Fabric Lakehouse. They need to display sales performance segmented by product category and region, with drill-down capabilities. Which type of visual best supports this hierarchical analysis and segmentation?
Explore and analyze data (15-20%)
A.Table visual
B.Card visual
C.Gauge visual
D.Matrix visual
Show answerAnswer
D. Matrix visual
A Matrix visual in Power BI is ideal for displaying data hierarchically across multiple dimensions (like product category and region) and aggregating measures. It supports drill-down/up functionality and allows for collapsing and expanding rows/columns, making it perfect for segmented hierarchical analysis.
25. A data analyst is working with a Spark Delta table `web_traffic` containing `user_id`, `page_id`, and `timestamp`. They need to identify the first `page_id` visited by each `user_id` on a given day. Which Spark SQL window function is most appropriate for this task?
Explore and analyze data (15-20%)
A.FIRST_VALUE(page_id) OVER (PARTITION BY user_id, date(timestamp) ORDER BY timestamp)
B.LAG(page_id, 1) OVER (PARTITION BY user_id, date(timestamp) ORDER BY timestamp)
C.ROW_NUMBER() OVER (PARTITION BY user_id, date(timestamp) ORDER BY timestamp)
D.NTH_VALUE(page_id, 1) OVER (PARTITION BY user_id, date(timestamp) ORDER BY timestamp)
Show answerAnswer
A. FIRST_VALUE(page_id) OVER (PARTITION BY user_id, date(timestamp) ORDER BY timestamp)
The `FIRST_VALUE()` window function is specifically designed to retrieve the value of an expression from the first row within its window frame. By partitioning by `user_id` and `date(timestamp)` and ordering by `timestamp`, it will correctly identify the `page_id` of the very first visit for each user on each day.
The Fabric Capacity Metrics app is a pre-built Power BI solution that provides administrators with detailed insights into the performance, resource utilization, and workload distribution of their Microsoft Fabric capacities.
Monitors CPU, memory, and other resource usage.
Shows consumption by different Fabric workloads (Spark, SQL, etc.).
Helps identify bottlenecks and optimize capacity settings.
The geographical region where a Microsoft Fabric capacity is provisioned, which dictates the physical location of all data processing and storage for workspaces and items assigned to that capacity.
Primary control for data residency in Fabric.
All associated workspaces and items inherit this region.
Customer-Managed Keys (CMK) in Microsoft Fabric allow organizations to use their own encryption keys from Azure Key Vault to encrypt data at rest within Fabric capacities, enhancing security and compliance.
Configured at the Fabric capacity level.
Uses Azure Key Vault for key management.
Encrypts all data at rest within the associated capacity.
This Microsoft Fabric tenant setting controls which users or security groups are permitted to create new workspaces, allowing for centralized governance of workspace provisioning.
Governs who can create new Fabric workspaces.
Found in the Fabric Admin Portal under Tenant Settings.
Can be set for the entire organization or specific security groups.
Microsoft Fabric's Git integration allows developers to connect workspaces to Azure DevOps Git repositories, enabling version control, collaborative development, and change tracking for Fabric items.
Azure Policy allows organizations to create, assign, and manage policies that enforce rules and effects over their Azure resources, including Microsoft Fabric items, ensuring compliance with organizational standards.
Enforces organizational standards and governance.
Can validate naming conventions, resource types, locations.
Applies at resource creation/update time to prevent non-compliance.
Integrating Microsoft Fabric with Git (e.g., Azure DevOps) and utilizing Pull Requests enables robust version control, collaborative code development, code reviews, and enforced merging policies for Fabric artifacts.
Connects Fabric workspaces to Git repositories.
Supports branching, committing, and merging.
Pull Requests facilitate code reviews and approval workflows.
Deployment pipelines in Microsoft Fabric streamline the development lifecycle by enabling content creators to develop, test, and deploy content across different environments (stages) with built-in governance.
Role-level security (RLS) and object-level security (OLS) in a Fabric Lakehouse allow for granular control over who can see which rows and columns of data, respectively, within tables.
RLS filters rows based on user identity.
OLS restricts access to specific columns or tables.
The Microsoft 365 Audit log is the centralized repository for auditing user and administrative activities across Microsoft 365 services, including all actions performed within Microsoft Fabric workspaces and items.
Records administrative and user activities.
Crucial for security audits and compliance.
Can be searched via the Microsoft Purview compliance portal.
Assigning dedicated Fabric Capacity SKUs to individual teams or projects allows for resource isolation, performance guarantees, and granular cost allocation (chargeback) within an organization.
Ensures performance isolation between teams.
Enables accurate cost tracking for each team's compute.
Provides dedicated compute resources for specific workloads.
Object-Level Security (OLS) is a data security feature that controls access to database objects like tables, columns, or views, restricting who can even see or reference these objects.
Restricts access to entire columns or tables.
Users without permission cannot see the protected object.
DLP policies are security measures that prevent sensitive data from leaving an organization's control or being shared with unauthorized entities, often by monitoring, identifying, and blocking data transfers.
Prevents unauthorized sharing of sensitive data.
Works by identifying and monitoring sensitive information.
Can be configured to block, warn, or audit sharing activities.
Microsoft Fabric provides inherent, baseline encryption for all data at rest and in transit, utilizing Microsoft-managed keys for storage and industry-standard protocols like TLS for network communication.
Data at rest is encrypted by default (Microsoft-managed keys).
Data in transit is encrypted by default (TLS 1.2+).
No user configuration required for baseline encryption.
Item lifecycle policies in Microsoft Fabric automate the management of workspace items, enabling actions like deletion based on conditions such as age or inactivity.
Automates item management in workspaces.
Can be configured based on last modified date or creation date.
Fabric Capacity Workload Settings allow administrators to control the maximum percentage of a Fabric capacity's resources that can be utilized by specific workload types (e.g., Data Engineering, Data Warehousing).
Allocates compute resources within a capacity.
Prevents resource contention between different workloads.
Configurable in the Fabric Admin Portal for each capacity.
Audit logs in Microsoft Fabric record user and system activities, crucial for security, compliance, and troubleshooting. They are typically accessed via the Microsoft Purview compliance portal.
Records actions like item creation, modification, access.
Essential for regulatory compliance (e.g., GDPR, HIPAA).
Tenant settings in the Microsoft Fabric Admin portal are global configurations that apply across all workspaces and users within an organization's Fabric tenant.
Control organization-wide policies and defaults.
Managed by Fabric administrators.
Affect aspects like security, data governance, and feature availability.
Row-Level Security (RLS) is a data security feature that restricts access to individual rows in a database table based on the execution context of the user, typically their identity or role.
The Power BI Matrix visual is a grid-like chart that supports displaying data across multiple dimensions with hierarchical row and column groupings, enabling drill-down capabilities and aggregated totals.
A Spark SQL window function that returns the value of the specified expression from the first row within its window frame, as defined by the PARTITION BY and ORDER BY clauses.
Retrieves the value from the first row of a window.
Requires `PARTITION BY` and `ORDER BY`.
Useful for finding initial states, first events, or starting values.
Delta Lake provides ACID (Atomicity, Consistency, Isolation, Durability) properties to data operations, ensuring reliability for data writes and reads, especially critical for streaming and concurrent workloads.
Questions are original practice items written to match the published exam objectives. Step2Study is not affiliated with or endorsed by any certification body.