Your company uses Microsoft Entra Connect to sync identities from an on-premises Active Directory. You have a user named 'User1' who exists in both environments, but they are not currently linked. You need to perform a 'soft-match' to link them. Which attribute must be identical on both the on-premises and cloud objects?
Entra Connect uses the primary SMTP address or the proxyAddresses attribute to perform a soft-match. If the SMTP address on-premises matches the 'mail' or 'proxyAddresses' attribute in Entra ID, the sync engine will link the two accounts, assuming no other hard-link (ImmutableID) is already present.
Why this answer
A soft-match in Microsoft Entra Connect links on-premises and cloud objects by comparing the primary SMTP address (proxyAddresses) and, optionally, the userPrincipalName. For a soft-match to succeed, the proxyAddresses attribute must be identical on both objects, as it is the primary anchor for matching.
Exam trap
SC-300 often tests the distinction between hard-match (ObjectGUID) and soft-match (proxyAddresses/UPN), causing candidates to select ObjectGUID incorrectly for soft-match scenarios.
How to eliminate wrong answers
Option A is wrong because ObjectGUID is used for hard-matching (via immutable ID) and is not the attribute for soft-match. Option B is wrong because DisplayName is not a unique or reliable matching attribute and is not used for soft-match. Option D is wrong because EmployeeID is not a default matching attribute for soft-match; it can be used for custom matching but requires configuration.