In a Dataflow Gen2 Diagram, after selecting FactSales and adding dimGeography, what should you do to retain all rows in FactSales and include geography where available?

In a Dataflow Gen2 Diagram, after selecting FactSales and adding dimGeography, what should you do to retain all rows in FactSales and include geography where available?

• A. Use Merge queries as new transformation with join kind Left outer and FactSales as the left table and dimGeography as the right table
• B. Use Merge queries as new transformation with join kind Inner
• C. Use Append queries
• D. Use Union queries

Answer: (B)

When you want to bring in related geography data for each sales record but still keep every sales row, you perform a merge with a left outer join. The left side is the broader FactSales table, and the right side is dimGeography. A left outer join returns all rows from FactSales and attaches matching geography information when a key matches; if there’s no geography for a sale, the geography columns are left null but the sale row remains. This exactly matches the goal of retaining all FactSales rows while including geography where available. Using an inner join would drop sales records that don’t have a geography match, which isn’t what you want here. Append or Union would not align geography data to the existing sales rows at all; they would just stack datasets or combine rows without adding the geography attributes to each sale.

When you want to bring in related geography data for each sales record but still keep every sales row, you perform a merge with a left outer join. The left side is the broader FactSales table, and the right side is dimGeography. A left outer join returns all rows from FactSales and attaches matching geography information when a key matches; if there’s no geography for a sale, the geography columns are left null but the sale row remains. This exactly matches the goal of retaining all FactSales rows while including geography where available.

Using an inner join would drop sales records that don’t have a geography match, which isn’t what you want here. Append or Union would not align geography data to the existing sales rows at all; they would just stack datasets or combine rows without adding the geography attributes to each sale.