which column in the Employee table should you create a unique constraint?

You administer a Microsoft SQL Server 2012 database. The database contains a table named Employee.
Part of the Employee table is shown in the exhibit.

Confidential information about the employees is stored in a separate table named EmployeeData. One
record exists within EmployeeData for each record in the Employee table. You need to assign the
appropriate constraints and table properties to ensure data integrity and visibility. On which column in
the Employee table should you create a unique constraint?

You administer a Microsoft SQL Server 2012 database. The database contains a table named Employee.
Part of the Employee table is shown in the exhibit.

Confidential information about the employees is stored in a separate table named EmployeeData. One
record exists within EmployeeData for each record in the Employee table. You need to assign the
appropriate constraints and table properties to ensure data integrity and visibility. On which column in
the Employee table should you create a unique constraint?

A.
DateHired

B.
DepartmentID

C.
EmployeelD

D.
EmployeeNum

E.
FirstName

F.
JobTitle

G.
LastName

H.
MiddleName

I.
ReportsToID



Leave a Reply 6

Your email address will not be published. Required fields are marked *


Greg

Greg

I would say C – EmployeeID is correct

Prabh

Prabh

I think this question is for 70-461

M

M

doesn’t mean it won’t appear in 463

Aakash

Aakash

Primary Key is already unique, so I believe EmployeeNum is correct answer.

jin

jin

agree with Aakash