MB-280 practice question 17 of 25

Your organization has customized Dynamics 365 Sales to allow sales users to create account plans on existing accounts. The Account table has a…

Full set: 121 questions
Your organization has customized Dynamics 365 Sales to allow sales users to create account plans on existing accounts. The Account table has a one-to-many relationship with the Custom Account Plan table. To comply with privacy laws, your organization needs to delete inactive account records after two (2) years. Some account managers noticed that when they delete accounts, linked account plans are also deleted. Account managers want to be able to use these account plans as references. You need to ensure that when accounts are deleted, the accounts plans are NOT deleted. Which type of behavior should you set on the delete action in the relationship between accounts and account plans?
Answer options
A: Cascade All
B: Cascade Active
C: Remove Link Correct answer
D: Restrict
Correct Answer:
C. Remove Link
Explanation

In a Dataverse one-to-many relationship, the Delete action can be configured so that child records are kept while the parent is removed. Setting Delete to Remove Link will delete the Account record but simply clear the Account lookup on every related Account Plan, so the plans remain available for later reference. Cascade All or Cascade Active would still delete plans; Restrict would block the account deletion entirely, violating the two-year-retention requirement. Therefore Remove Link is the only behavior that fulfils both privacy-driven deletion of Accounts and retention of Account Plans.

Why Incorrect

A. Cascade All – Deletes every account plan together with the account.
B. Cascade Active – Deletes only active account plans, still removing data that must be kept.
D. Restrict – Prevents deletion of any account that still has account plans, so privacy requirement cannot be met.

References

1. Microsoft Learn

“Define and enforce cascade behaviors in relationships

” Dataverse docs

section “Delete

” bullet “Remove link (formerly Cascade None).” https://learn.microsoft.com/power-apps/maker/data-platform/configure-entity-relationship#delete

2. Microsoft Power Platform Functional Consultant MB-260 Courseware

Module 3 “Model Data in Dataverse

” Lesson “Relationship behaviors

” pp. 8-9 (behavior tables show Remove Link retains child rows).

3. Dynamics 365 Customer Engagement SDK Help File

v9

“Configurable cascading

” Table 3 Delete behaviors

p. 89.

Scroll to Top