Exam PL-600 All Questions

View all questions & answers for the PL-600 exam

Exam PL-600 topic 2 question 4 discussion

Actual exam question from Microsoft's PL-600

Question #: 4
Topic #: 2

You are designing the data model for a school. The school wants to track students' enrollments in courses.
The system must meet the following requirements:
✑ Track the courses in which each student is enrolled.
✑ Track the students that are enrolled in each course.
Track dates when each student enrolled in each course and the person who approved the enrollment.

✑ Allow users to create a report that details which students are enrolled in which courses.
You need to recommend a data model that will fit the school's requirements.
Which logical model should you recommend?
A.

B.

C.

D.

Show Suggested Answer

Suggested Answer: A
Need a relationship table.
N:N (Many-to-Many): A table relationship that depends on a special Relationship table, sometimes called an Intersect table, so that many rows of one table can be related to many rows of another table.
When viewing rows of either table in a N:N relationship you can see a list of any rows of the other table that are related to it.
Reference:
https://docs.microsoft.com/en-us/powerapps/maker/data-platform/create-edit-entity-relationships

by N8n0z at May 15, 2021, 3:08 p.m.

Comments

Submit Cancel

N8n0z

Highly Voted 3 years, 8 months ago

A is correct. Definitely needs an intersect table to store the enrollment date and the person and still relate the student to the course

upvoted 65 times

meg111111111111

1 year, 9 months ago

Agreed, best practice for the intersect

upvoted 1 times

...

AL14NWUK

2 years, 10 months ago

Created and Created by fields ?

upvoted 1 times

...

Hostt93

Most Recent 1 year, 2 months ago

The solution is incorrect, so you got 1 enrollment to many students? this seems wrong to me. None of the answers is correct.

upvoted 2 times

AleMar153

1 year, 1 month ago

it's the opposite: one student can have different enrollment

upvoted 2 times

...

Acrious

1 year, 6 months ago

A is the correct answer, as it requires additional fields that cannot be added to an N:N invisible intersect table.

upvoted 3 times

...

radityoardi

2 years, 6 months ago

Essentially A and B are both correct. In Dataverse, many-to-many relationships will create an intermediate table in between.

upvoted 1 times

dlnuser

1 year, 11 months ago

The intermediate table is hidden and cannot be consulted from within the Dataverse app. B is also assuming a scenario where the person who approves the enrollment will also be the one to approve the enrollment, but that is not necessarily true. Additional fields cannot be added into the hidden relationship table and the hidden relationship table cannot be edited directly by users.

upvoted 1 times

...

SaschaB

2 years, 3 months ago

Not wrong but it saysspecifically that we need to track approval and dates. That's not possible with automatic N:N.

upvoted 1 times

...

m3ngi3

2 years, 5 months ago

Agree but the default (hidden) intersect table does not contain additional data... if we create the intersect table ourselves we can add additional data like the enrollment date

upvoted 3 times

...