Q: 2
You are implementing a medallion architecture in a Fabric lakehouse. You plan to create a dimension table that will contain the following columns: • ID • CustomerCode • CustomerName • CustomerAddress • CustomerLocation • ValidFrom • ValidTo You need to ensure that the table supports the analysis of historical sales data by customer location at the time of each sale Which type of slowly changing dimension (SCD) should you use?
Options
Discussion
A . You need to keep the full change history for customer locations so sales can be analyzed based on where the customer was when each sale occurred. D only gives you a limited snapshot, easy to overlook that. Agree?
These SCD types always get confusing with Microsoft wording, is D (Type 3) ever enough for historic location like this?
Nah, it isn't C here, since that'd only handle current values and lose the change history. A is the one that captures every location update for proper historical analysis. Type 3 (D) might look tempting but only stores limited previous states. Pretty sure it's A unless I'm missing some new Fabric twist.
Its A
A tbh
A , Microsoft loves asking about SCD types in these Fabric scenarios. Full history needed because analysis is at sale time.
A , D only handles partial history and you'd lose accurate past location data for each sale. Trap for sure.
A , D is a common mistake for limited history but here you actually need all changes for analysis.
For me, A, had something similar in a mock. ValidFrom and ValidTo columns point to Type 2 SCD.
A is wrong, it’s definitely not D. Pretty sure it should be A here.
Be respectful. No spam.