CertifyDeckCargando contenido…
The official Microsoft Certified: Fabric Analytics Engineer Associate syllabus, organized by domain. Check off each point as you review it.
Inicia sesión para guardar tu progreso entre sesiones.
Implement security and governance
Workspace roles (Admin, Member, Contributor and Viewer) are assigned to users or groups and apply to every item. A user in several groups gets the highest role. Viewer reads content and data with T-SQL but has no Spark or write access; Contributor creates and runs items; Member also adds people; only Admin deletes the workspace and connects Git.
Sharing an item gives access to that item without a workspace role and always grants Read. You can add ReadData (T-SQL), ReadAll (Spark and OneLake), Build or Write on semantic models, and Share, which only passes on the sharer's own permissions. Permissions inherited from a workspace role cannot be removed on the item; for finer warehouse access, use GRANT.
Share items in Microsoft Fabric ↗Semantic model permissions ↗
In a warehouse, RLS uses CREATE SECURITY POLICY with inline table-valued functions, CLS uses GRANT on columns, and OLS uses GRANT, REVOKE and DENY. In semantic models, RLS and OLS are defined in roles and only affect Viewers. OneLake security grants Read by folder, table, row or column, with a DefaultReader role for users who have ReadAll.
Row-level security in Fabric Data Warehouse ↗OneLake security roles, permissions, and scopes ↗
Microsoft Purview sensitivity labels are applied from the item header or settings and require edit permissions. They can be inherited on creation, downstream (never overwriting manual labels or lowering restriction) and from sources in Import models. In the service they do not limit access unless a protection policy is used; encryption travels with supported exports.
Information protection in Fabric ↗Sensitivity label downstream inheritance in Power BI ↗
Endorsement helps people find trustworthy content through three badges. Anyone with write permissions can apply Promoted; Certified and Master data can be applied only by users authorized by the Fabric administrator, who also need write access. Everything except Power BI dashboards can be promoted or certified, and Master data applies only to items that hold data.
Maintain the analytics development lifecycle
Fabric Git integration works at workspace level: only a workspace admin connects it to or disconnects it from an Azure DevOps or GitHub branch, and you then commit workspace changes or update from the whole branch. Only item definitions are versioned, never data, and each developer can branch out to an own workspace to isolate development.
Basic concepts in Git integration ↗Get started with Git integration ↗
A Power BI project (PBIP) saves the report and semantic model as folders of Git-ready text files: definition.pbir references the model and the definition folder holds the model in TMDL. The default .gitignore excludes cache.abf and localSettings.json. Publishing from Power BI Desktop also sends the data cache, while Git and the APIs deploy only metadata.
Power BI Desktop projects ↗Power BI Desktop project semantic model folder ↗
A deployment pipeline assigns one workspace to each stage (Development, Test and Production by default) and copies metadata, not data, between paired items. Data source, parameter and default lakehouse rules are created in the target stage and apply at the next deployment. Deploying requires being a pipeline admin and at least a Contributor in both workspaces.
Impact analysis shows the items and workspaces that a change to an item might affect, as direct children or all downstream items, and lets you email their contacts with Notify contacts. It requires write permission on the item, and for data sources it shows only direct children. Lineage view doesn't show downstream items in other workspaces.
The XMLA endpoint exposes each workspace as an Analysis Services server: it is read-only by default and must be enabled for read-write on the capacity to deploy models, run TMSL or perform fine-grained partition refreshes. Contributors act as database admins, and data source credentials are set in the service, not through XMLA.
A .pbit template holds report pages, the model definition and queries but no data; opening it asks for parameters and the source. A .pbids file preconfigures one data source, without credentials, and can set Import or DirectQuery mode. A shared semantic model is reused through a live connection by authors who have Build permission.
Create and use report templates in Power BI Desktop ↗Build permission for shared semantic models ↗