最新的Microsoft Implementing Analytics Solutions Using Microsoft Fabric (DP-600 Korean Version) - DP-600 Korean免費考試真題

說明：（僅 PDFExamDumps 成員可見）

說明：（僅 PDFExamDumps 成員可見）

說明：（僅 PDFExamDumps 成員可見）

說明：（僅 PDFExamDumps 成員可見）

Explanation:

Comprehensive Detailed Explanation
We are tasked with writing a T-SQL query to denormalize the tables Employee and Contract in a Fabric warehouse.
Requirements Breakdown
Include attributes from matching rows in the Contract table
This means we must join Employee and Contract on EmployeeID .
Ensure that all rows from the Employee table are preserved
This requires a LEFT OUTER JOIN from Employee to Contract. If an employee has no contract, we still want the employee record included.
Return the total number of employees per contract type for all contract types that have more than two employees This means we need to:
Group by ContractType
Count distinct EmployeeID
Filter groups where that count > 2.
To filter aggregated results, we use HAVING , not WHERE.
Completed Query
WITH result AS (
SELECT
e.EmployeeID,
e.EmployeeName,
e.EmployeePosition,
c.ContractType,
c.StartDate
FROM Employee AS e
LEFT OUTER JOIN Contract AS c
ON c.EmployeeID = e.EmployeeID
)
SELECT
ContractType,
COUNT ( DISTINCT EmployeeID) AS TotalEmployees
FROM result
GROUP BY ContractType
HAVING COUNT ( DISTINCT EmployeeID) > 2 ;
Why This is Correct
LEFT OUTER JOIN ensures all employees are included, regardless of contracts.
HAVING allows filtering aggregated groups by employee counts.
The query returns ContractType , StartDate (as requested in denormalization), and aggregated employee counts.
References
T-SQL JOINs in Microsoft Fabric
Aggregate functions and HAVING clause
Denormalization best practices in Fabric warehouses

Explanation:

Explanation:

Step 1 - Read the Parquet file into a DataFrame
df = spark.read.parquet( " abfss://[email protected]/files/sales.parquet " ) This correctly loads the Parquet data into Spark.
Step 2 - Write into the Lakehouse as a managed table
If we want the result to be registered as a Lakehouse table and automatically appear in Lakehouse Explorer, we must:
Write the data in delta format (because Fabric Lakehouse tables are Delta tables ).
Save the table under the tables folder, not files .
So the correct code is:
df.write.mode( " overwrite " ). format ( " delta " ).saveAsTable( " tables/sales " ) Format: delta SaveAsTable Path: tables/sales References:
Lakehouse tables in Microsoft Fabric
Save DataFrame as Delta Table in Spark
# Answer Selection:
First dropdown # delta
Second dropdown # tables/sales

說明：（僅 PDFExamDumps 成員可見）

說明：（僅 PDFExamDumps 成員可見）

說明：（僅 PDFExamDumps 成員可見）

說明：（僅 PDFExamDumps 成員可見）

說明：（僅 PDFExamDumps 成員可見）

Explanation:
Comprehensive Detailed Explanation
When assigning permissions to roles in a Fabric workspace for analytics workloads, you must align permissions with the responsibilities and tools typically used by each persona:
1. Data Engineers
Their primary tasks include building and transforming data pipelines, as well as making datasets usable by others.
The appropriate permission is Build Reports on the default dataset , because this allows them to create and manage reports using the curated semantic model while preparing data for analysts and scientists.
2. Data Analysts
Analysts work heavily with Apache Spark for exploratory analysis, cleansing, and shaping data.
The correct permission is Read All Apache Spark , as this grants them the ability to query and analyze Spark- based data directly without elevated permissions that are unnecessary for their role.
3. Data Scientists
Data scientists often use SQL analytics endpoints to run queries, train models, and integrate data into machine learning workflows.
The correct permission is Read All SQL analytics endpoint data , since it enables direct programmatic access to the SQL endpoint, which is needed for advanced modeling and experimentation.
Summary of Selections:
DataEngineers # Build Reports on the default dataset
DataAnalysts # Read All Apache Spark
DataScientists # Read All SQL analytics endpoint data
References (Microsoft Fabric - DP-600 exam scope):
Workspace roles and permissions in Microsoft Fabric
SQL analytics endpoint in Fabric
Apache Spark in Microsoft Fabric

Explanation:

The relationship between OrderItem and Product must be based on: Both the CompanyID and the ProductID columns The Company entity must be: Denormalized into the Customer and Product entities In a dimensional model, the relationships are typically based on foreign key constraints between the fact table (OrderItem) and dimension tables (Product, Customer, Date). Since CompanyID is present in both the OrderItem and Product tables, it acts as a foreign key in the relationship. Similarly, ProductID is a foreign key that relates these two tables. To enable analysis by date, product, and customer, the Company entity would need to be denormalized into the Customer and Product entities to ensure that the relevant company information is available within those dimensions for querying and reporting purposes.
References =
Dimensional modeling
Star schema design