You are designing a Microsoft Power Platform solution for an automobile parts manufacturer. You create the following tables: You need to recommend a relationship behavior. Which relationship behavior should you recommend?
It cannot be referential. The owner will only be inherited in a custom relationship. If you set the relationship to parental, related records will be deleted, too.
Correct answer is: Custom.
Configurable Cascading / Custom. Needed values are Assign:Cascade All & Delete:Remove Link. First requirement says associated records/parts need to be updated, so cascade makes sense. Deletion doesn’t say ‘prevent delete’ so it’s not restrict delete, remove link is the right choice.
Why Parental?
Ownership changes in the parent (Assembly) will cascade to the child (Parts).
Deletion behavior can be customized within a Parental relationship to not delete child records.
So, Parental gives you the flexibility to cascade ownership changes while preventing deletion of child records, making it the most appropriate single relationship behavior.
Tricky one, you have to read the question very carefully. The bit that almost got me through skipping over is that the owner of related records must be updated when the assembly does. So its B.
Custom because on topic 1 data need be updated, and topic 2 must be keeping existing on D365:
https://community.dynamics.com/365/sales/b/crminogic/posts/configure-rollup-view-for-activities-with-dynamics-crm-365
A, C and D cannot be correct (see https://learn.microsoft.com/en-us/power-apps/maker/data-platform/data-platform-entity-lookup#add-advanced-relationship-behavior).
So is must be B
Referential, Restrict Delete: In a referential, restrict delete relationship between two entities, you can navigate to any related records. Actions taken on the parent record will not be applied to the child record, but the parent record cannot be deleted while the child record exists. So, Answer is B.
No we are not looking for parental relationship. Its referential. Read the question again. Related records need to be updated, not child records. This tells me that the parts can be used in many assemblies, which means, the answer provided is correct. Answer is A
Configurable Cascading is required to achieve requirement
upvoted 1 times
...
...
This section is not available anymore. Please use the main Exam Page.PL-600 Exam Questions
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
alainle
Highly Voted 2 years, 1 month agoIcky
1 year, 11 months agoDrizzt1807
1 year, 10 months agomscert_iy
Highly Voted 1 year, 11 months agoHamed64
Most Recent 1 week, 4 days agoloftuscheek
3 months, 1 week agoapp2
6 months, 2 weeks agoAttendee1
7 months, 3 weeks agoOldHand1
11 months agoParth91
1 year, 1 month agobrmscertprep
1 year, 7 months agoAnon303
1 year, 9 months agoAlRe
1 year, 9 months agoAnon303
1 year, 9 months agoAnon303
1 year, 9 months agoAnon303
1 year, 9 months agoSumit_msp
1 year, 11 months agoIcky
1 year, 11 months agoDynamic_MD
2 years, 1 month agoDynamic_MD
2 years, 1 month ago