A Left Join (also known as a Left Outer Join) is the correct choice for this scenario. This join type returns all records from the left table (Table A) and the matched records from the right table (Table B). If a row in Table A does not have a corresponding match in Table B, the columns from Table B will be filled with NULL values in the result set. This precisely meets the requirement to include all rows from the first table and only matching rows from the second.

A. Outer: This term is ambiguous. It could refer to a Left Outer, Right Outer, or Full Outer Join. A Full Outer Join would incorrectly include all non-matching rows from Table B as well.

C. Inner: An Inner Join returns only the rows where the join condition is met in both tables. This would exclude any rows from Table A that do not have a match in Table B.

1. SAP Help Portal, SAP SuccessFactors HXM Suite, Report - Canvas Designer Guide (2H 2023): In the section "Join Types in Detailed Reporting", the guide defines a Left Outer Join as: "Select all rows from the left table and only those rows from the right table where the joined fields are equal." This directly supports the selection of Left Join to include all rows from the first table (Table A).

2. SAP Help Portal, SAP SuccessFactors HXM Suite, Integration Center Guide (2H 2023): When configuring joins in the Integration Center's query builder, the behavior of a Left Outer Join is described as returning all records from the primary (left) entity and matching records from the secondary (right) entity, which aligns with the question's requirement.

3. Silberschatz, A., Korth, H. F., & Sudarshan, S. (2020). Database System Concepts (7th ed.). McGraw-Hill. Chapter 4, "Intermediate SQL," section 4.2.2 "Outer Joins," explains that a left outer join "preserves tuples from the relation named before (to the left of) the left outer join operation," which is the standard academic definition matching the scenario.