Which of the following components is NOT typically part of the AutoCAD 3D workspace setup?
Think about which tool is limited to 2D and not specifically part of 3D navigation or visualization.
The Layer Properties Manager manages layers but is not exclusive to 3D workspace setup; it manages both 2D and 3D layers. However, the option says 'for managing 2D layers only' which is incorrect in the context of 3D workspace setup.
Given a table Objects3D with columns Length, Width, and Height, which DAX measure correctly calculates the total volume of all objects?
Remember to multiply dimensions row by row before summing.
Option A correctly multiplies Length, Width, and Height for each row and then sums the results. Option A multiplies sums which is mathematically incorrect for total volume. Option A uses SUM on a calculated expression which is invalid. Option A nests SUM inside SUMX incorrectly.
You want to create a dashboard showing how many hours users spend in different 3D workspace modes (e.g., Wireframe, Shaded, Realistic) over a month. Which visualization type is best to clearly show trends and comparisons?
Think about showing changes over time and comparing categories.
A stacked area chart effectively shows how hours spent in each mode change over days and allows easy comparison. Pie charts show proportions but not trends. Scatter plots are not ideal for categorical modes. KPI cards show only totals, not trends or breakdowns.
You have two tables: Users (UserID, Name) and WorkspaceSessions (SessionID, UserID, Mode, DurationHours). To analyze total hours per user per mode, what is the best data modeling approach?
Think about how to connect user info with session data properly.
Option B correctly creates a relationship on UserID to connect user details with session data, enabling aggregation by user and mode. Option B loses normalization and can cause redundancy. Option B ignores user details. Option B tries to relate unrelated columns causing errors.
A DAX measure to calculate total hours spent in 'Shaded' mode is:
Shaded Hours = CALCULATE(SUM(WorkspaceSessions[DurationHours]), WorkspaceSessions[Mode] = "Shaded")
However, the report shows zero hours even though data exists. What is the cause?
Check how filters are applied inside CALCULATE.
In DAX, filter conditions inside CALCULATE can be written directly as column = value expressions and do not need to be wrapped in FILTER. The syntax WorkspaceSessions[Mode] = "Shaded" is valid and commonly used. The issue is likely elsewhere.