Exam PL-200 All Questions

View all questions & answers for the PL-200 exam

Exam PL-200 topic 7 question 2 discussion

Actual exam question from Microsoft's PL-200

Question #: 2
Topic #: 7

HOTSPOT -
You need to resolve the issue reported by substitute employees after they are assigned service requests.
How should you configure the system? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
Hot Area:

Show Suggested Answer

Suggested Answer:

Box 1: Service Request 1:N Qualification
When users go on vacation, all their outstanding Service Request records are assigned to a substitute employee. The substitute employees are unable to see all the qualifications related to their service requests.

Box 2: Cascade All -
Cascade All - Perform the action on all referencing table records associated with the referenced table record.
Reference:
https://docs.microsoft.com/en-us/power-apps/developer/data-platform/configure-entity-relationship-cascading-behavior

by niel93 at Sept. 24, 2022, 9:43 p.m.

Comments

Submit Cancel

niel93

Highly Voted 2 years, 9 months ago

This question was on Sept 24th Scored 712 Selected the same answer

upvoted 8 times

...

Mayah974

Highly Voted 1 year, 11 months ago

This question was on July 7th Score 806 1- service request 1:N qualification 2- cascade all

upvoted 5 times

...

gina_the_boss

Most Recent 5 months, 1 week ago

Where did they get the reasoning provided in the Suggested answer? Was it part of the original question or what? There's not enough info in the question to conclusively say whether: Relationship should be 1:N or N:N - Both could be right Cascading rule should be: Cascade All or Cascade None.

upvoted 1 times

...

HaileleoulG

12 months ago

Correct

upvoted 1 times

...

jkaur

1 year, 2 months ago

correct

upvoted 2 times

...

charles879987

2 years, 1 month ago

on may 2023 exam

upvoted 3 times

...

Ikhalil

2 years, 3 months ago

Relationship 1- service request 1:N qualification Cascading rule 2- cascade all

upvoted 3 times

...

RICHARDALEX007

2 years, 3 months ago

On exam March 2023

upvoted 1 times

...

RichXP

2 years, 5 months ago

N:N, one service request (like background check for xxx) may have multiple qualifications (like education, work location, address, credit) one qualification (like xxx's address) may associate with multiple service requests (banks, hiring companies) 2nd Q: cascade none. If you want delete one service request, should just leave linked qualifications alone

upvoted 2 times

SeniorFC001

2 years, 2 months ago

Valid line of thinking BUT It never mentions that Qualification records are RE-USED for multiple Service Requests. So the assumption is that they are not. It says Clients enter their data in a website, which then uses a service account to create the records in the Dataverse database. Never says there is some sort of complex previous Service Request / Qualification re-use mechanism in place. Furthermore it explicitly states: In the rare event that results are questioned (by the client), a new service request is created and verified independently of the previous work that took place. INDEPENDENTLY OF PREVIOUS WORK - so again assumption is that a brand new Service Request and Qualification records are always created. Also if you don't use Cascade All then there is no way (mentioned in the answer) to fix the issue of users not being able to see Qualification records.

upvoted 5 times

...

Newb007

2 years, 3 months ago

Casacade None?..... Try reading this again... it's cascade all.. must be "When users go on vacation, all their outstanding Service Request records are assigned to a substitute employee. The substitute employees are unable to see all the qualifications related to their service requests." Assign Records via Cascade All

upvoted 4 times

...

Zackfactor

2 years, 4 months ago

Can you please explain why N:N because the essays says a service request can have 1 or more qualification records associated with it.

upvoted 2 times

...

charthouse

1 year, 8 months ago

I initially thought 'Cascade None' for the same reason. Then I realised that cascading behaviour in Dataverse doesn't just apply to deleting records, but also to assigning, sharing, merging, etc. In which case, 'Cascade All' is correct. See https://learn.microsoft.com/en-us/power-apps/developer/data-platform/configure-entity-relationship-cascading-behavior#using-sdk-for-net-to-configure-cascading-behavior

upvoted 1 times

...