If a table has a concatenated primary key (Col_A, Col_B) and is a clustered index where each column is a foreign key from another parent table, would it be necessary to create nonclustered indexes on each individual key (one on Col_A and another on Col_B)? Or, would SQL Server use the clustered index of this table when joined to the child table efficiently?