nerdexam
Microsoft

PL-400 · Question #21

A travel company plans to track the address of places their clients visit in an entity named Destination. Client information is captured as contact records. Client records include links to the…

The correct answer is D. Create a 1:N relationship between the Contact system entity and the Rating entity. E. Create a mapping for the Destination - Rating relationship. F. Create a 1:N relationship between the Destination entity and the Rating entity. To expand the Rating entity so it links to both Contacts and Destinations (address-tracking entity), three steps are needed. D: Create a 1:N relationship between the Contact system entity and the Rating entity - this allows one Contact to be associated with many Rating records…

Submitted by weili_xi· Apr 18, 2026

Question

A travel company plans to track the address of places their clients visit in an entity named Destination. Client information is captured as contact records. Client records include links to the places that clients visit. The company must be able to link multiple rating records to the new address record. You find a custom Rating entity that is incomplete. You need to expand the Rating entity to include contact, address, and rating information in one place. Which three actions should you perform? Each correct answer presents part of the solution. NOTE: Each correct selection is worth one point.

Options

  • ACreate a 1:N relationship between the Contact system entity and the Address system entity
  • BCreate a mapping for the Contact - Rating relationship.
  • CCreate a 1:N relationship between the Address system entity and the Rating entity.
  • DCreate a 1:N relationship between the Contact system entity and the Rating entity.
  • ECreate a mapping for the Destination - Rating relationship.
  • FCreate a 1:N relationship between the Destination entity and the Rating entity.

How the community answered

(60 responses)
  • A
    7% (4)
  • B
    13% (8)
  • C
    3% (2)
  • D
    77% (46)

Explanation

To expand the Rating entity so it links to both Contacts and Destinations (address-tracking entity), three steps are needed. D: Create a 1:N relationship between the Contact system entity and the Rating entity - this allows one Contact to be associated with many Rating records. F: Create a 1:N relationship between the Destination entity and the Rating entity - this allows one Destination (address) to be linked to many Rating records, satisfying the requirement to link multiple ratings to an address. E: Create a mapping for the Destination-Rating relationship - mappings auto-populate fields when a new Rating is created from a Destination, maintaining data consistency. Option A is wrong because a Contact-to-Address system entity relationship is not what's being built. Option B (mapping for Contact-Rating) is not one of the three required steps. Option C uses the Address system entity instead of the custom Destination entity.

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full PL-400 Practice