100% Latest & Updated Microsoft PL-200 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 10
Each supplier may participate in many purchasing groups, and each group has many suppliers; the existing lookup allows only one group per supplier. Select THREE case-specific measures covering remediation, proof and longer-term prevention.
- Change external values and prove the displayed derived value updates through the chosen supported integration.
- Model supplier–group membership with a many-to-many relationship or an explicit junction table if membership needs attributes.
- Associate two suppliers with two groups and confirm reciprocal membership without overwriting a previous association.
- Choose the correct Dataverse date/time behavior for the business meaning and normalize reporting boundaries.
- Govern the choice taxonomy and retire ad-hoc text values after a validated migration.
- Document cardinality and decide early whether the association requires its own status or effective-date columns.
Explanation
Correct Answers
B:Model supplier–group membership with a many-to-many relationship or an explicit junction table if membership needs attributes. This directly addresses: The one-to-many lookup cannot represent both sides having multiple memberships.
C:Associate two suppliers with two groups and confirm reciprocal membership without overwriting a previous association. This is required evidence before closure.
F:Document cardinality and decide early whether the association requires its own status or effective-date columns. This reduces recurrence of: The one-to-many lookup cannot represent both sides having multiple memberships.
Incorrect Answers
A:This choice targets computed field external source and leaves the described requirement unproven. The case calls for associate two suppliers with two groups and confirm reciprocal membership without overwriting a previous association.
D:Applying this would shift attention to timezone date reporting without testing the actual fault. The one-to-many lookup cannot represent both sides having multiple memberships.
E:That approach is designed for choice value normalization: An unconstrained text column allows synonymous labels that are not one controlled classification. The present case instead involves the one-to-many lookup cannot represent both sides having multiple memberships.
Question 11
Customer records have active contracts, but staff must never delete a customer while its contracts remain; a parental cascade currently removes the contracts. Which underlying design issue accounts for the observed behavior?
- Reusing an ambiguous display label risks binding the wrong logical table to new components.
- The account total is denormalized and updated only by users, so related-order changes are missed.
- The column was not added as a required solution component before export.
- Delete cascade is configured to remove related rows instead of blocking deletion.
Explanation
Correct Answer
D:Configure the relationship's delete behavior as Restrict and retain contract ownership. The observed cause is: Delete cascade is configured to remove related rows instead of blocking deletion.
Incorrect Answers
A:This would respond to a different requirement (table naming collision). It does not establish the needed result here: delete cascade is configured to remove related rows instead of blocking deletion.
B:This choice targets rollup child totals and leaves the described requirement unproven. The case calls for delete cascade is configured to remove related rows instead of blocking deletion.
C:That approach is designed for solution component missing column: The column was not added as a required solution component before export. The present case instead involves delete cascade is configured to remove related rows instead of blocking deletion.
Question 12
Customer records have active contracts, but staff must never delete a customer while its contracts remain; a parental cascade currently removes the contracts. Which implementation decision best fixes the stated problem?
- Configure the relationship's delete behavior as Restrict and retain contract ownership.
- Choose the correct Dataverse date/time behavior for the business meaning and normalize reporting boundaries.
- Evaluate a Dataverse virtual table backed by a supported external data provider and document its feature limitations.
- Keep audit events in the underlying source or persist audit-relevant transactions in a supported local Dataverse table.
Explanation
Correct Answer
A:Configure the relationship's delete behavior as Restrict and retain contract ownership. This addresses: Delete cascade is configured to remove related rows instead of blocking deletion.
Incorrect Answers
B:This would respond to a different requirement (timezone date reporting). It does not establish the needed result here: configure the relationship's delete behavior as Restrict and retain contract ownership.
C:That approach is designed for external read-only price catalog: A local imported table creates a second stale copy of externally owned records. The present case instead involves delete cascade is configured to remove related rows instead of blocking deletion.
D:The proposed step addresses virtual-table auditing request, not the constraint in this scenario. The decisive issue is that delete cascade is configured to remove related rows instead of blocking deletion.
Question 13
Customer records have active contracts, but staff must never delete a customer while its contracts remain; a parental cascade currently removes the contracts. Which acceptance check should the team use?
- Set known expiry dates and compare the resulting value with hand-calculated expected days.
- Attempt to delete a customer with contracts and confirm the operation is denied while contracts remain intact.
- Review the same stored instant for users in two time zones and confirm the report follows the defined date rule.
- Add and edit related orders, force or await the rollup recalculation and compare with the expected sum.
Explanation
Correct Answer
B:Attempt to delete a customer with contracts and confirm the operation is denied while contracts remain intact. This tests actual behavior, not just configuration presence.
Incorrect Answers
A:The proposed step addresses formula per-row calculation, not the constraint in this scenario. The decisive issue is that delete cascade is configured to remove related rows instead of blocking deletion.
C:That choice can be relevant to timezone date reporting, but its assumptions are absent from this case. Here the direct discriminating test is attempt to delete a customer with contracts and confirm the operation is denied while contracts remain intact.
D:This would respond to a different requirement (rollup child totals). It does not establish the needed result here: attempt to delete a customer with contracts and confirm the operation is denied while contracts remain intact.
Question 14
Customer records have active contracts, but staff must never delete a customer while its contracts remain; a parental cascade currently removes the contracts. Which governance practice most directly protects this requirement over time?
- Govern alternate-key uniqueness and monitor integration reconciliation failures.
- Document rollup refresh behavior and test edge cases such as filters and deleted children.
- Identify virtual-table calculation restrictions in the data model review.
- Include referential-delete behavior in solution design review and destructive-operation tests.
Explanation
Correct Answer
D:Include referential-delete behavior in solution design review and destructive-operation tests. This helps prevent recurrence of: Delete cascade is configured to remove related rows instead of blocking deletion.
Incorrect Answers
A:Applying this would shift attention to alternate key duplicate external id without testing the actual fault. Delete cascade is configured to remove related rows instead of blocking deletion.
B:That choice can be relevant to rollup child totals, but its assumptions are absent from this case. Here the direct recurrence control is include referential-delete behavior in solution design review and destructive-operation tests.
C:The proposed step addresses computed field external source, not the constraint in this scenario. The decisive issue is that delete cascade is configured to remove related rows instead of blocking deletion.
Question 15
Customer records have active contracts, but staff must never delete a customer while its contracts remain; a parental cascade currently removes the contracts. Which TWO measures together implement the targeted correction and verify its result? Select TWO.
- Model supplier–group membership with a many-to-many relationship or an explicit junction table if membership needs attributes.
- Distinguish optional references from required references before configuring relationship actions.
- Configure the relationship's delete behavior as Restrict and retain contract ownership.
- Set known expiry dates and compare the resulting value with hand-calculated expected days.
- Attempt to delete a customer with contracts and confirm the operation is denied while contracts remain intact.
Explanation
Correct Answers
C:Configure the relationship's delete behavior as Restrict and retain contract ownership. This directly addresses: Delete cascade is configured to remove related rows instead of blocking deletion.
E:Attempt to delete a customer with contracts and confirm the operation is denied while contracts remain intact. This is required evidence before closure.
Incorrect Answers
A:That choice can be relevant to supplier multiparty membership, but its assumptions are absent from this case. Here the direct corrective action is configure the relationship's delete behavior as Restrict and retain contract ownership.
B:This choice targets account removal without child deletion and leaves the described requirement unproven. The case calls for include referential-delete behavior in solution design review and destructive-operation tests.
D:Applying this would shift attention to formula per-row calculation without testing the actual fault. Delete cascade is configured to remove related rows instead of blocking deletion.
Question 16
An imported account is obsolete, but associated draft inquiries must survive without pointing to the removed account. What mechanism should the consultant identify before making changes?
- A text field cannot enforce a referential link to the parent account row.
- The relationship's delete behavior would delete the inquiries along with the account.
- The column was not added as a required solution component before export.
- Manually entered derived values become stale and violate a single source of truth.
Explanation
Correct Answer
B:Use Remove Link for the delete action on an optional lookup so the inquiries remain with an empty parent reference. The observed cause is: The relationship's delete behavior would delete the inquiries along with the account.
Incorrect Answers
A:Applying this would shift attention to account–contact one-to-many without testing the actual fault. The relationship's delete behavior would delete the inquiries along with the account.
C:This choice targets solution component missing column and leaves the described requirement unproven. The case calls for the relationship's delete behavior would delete the inquiries along with the account.
D:That approach is designed for formula per-row calculation: Manually entered derived values become stale and violate a single source of truth. The present case instead involves the relationship's delete behavior would delete the inquiries along with the account.
Question 17
An imported account is obsolete, but associated draft inquiries must survive without pointing to the removed account. What should the consultant configure to correct the observed behavior?
- Use Remove Link for the delete action on an optional lookup so the inquiries remain with an empty parent reference.
- Choose an appropriate supported decimal or currency precision and migrate existing values under a reviewed conversion plan.
- Add the intended column and dependencies to the source solution and export a new version for deployment.
- Model supplier–group membership with a many-to-many relationship or an explicit junction table if membership needs attributes.
Explanation
Correct Answer
A:Use Remove Link for the delete action on an optional lookup so the inquiries remain with an empty parent reference. This addresses: The relationship's delete behavior would delete the inquiries along with the account.
Incorrect Answers
B:This choice targets currency precision concern and leaves the described requirement unproven. The case calls for use Remove Link for the delete action on an optional lookup so the inquiries remain with an empty parent reference.
C:This would respond to a different requirement (solution component missing column). It does not establish the needed result here: use Remove Link for the delete action on an optional lookup so the inquiries remain with an empty parent reference.
D:That approach is designed for supplier multiparty membership: The one-to-many lookup cannot represent both sides having multiple memberships. The present case instead involves the relationship's delete behavior would delete the inquiries along with the account.
Question 18
An imported account is obsolete, but associated draft inquiries must survive without pointing to the removed account. Which validation would demonstrate that the intended result has been achieved?
- Review the same stored instant for users in two time zones and confirm the report follows the defined date rule.
- Import to a clean test environment and inspect the table schema for the exact expected column logical name.
- Delete the test parent and confirm related inquiries still exist and their account lookups are cleared.
- Reimport the same external ID and confirm one row is updated rather than a second row created.
Explanation
Correct Answer
C:Delete the test parent and confirm related inquiries still exist and their account lookups are cleared. This tests actual behavior, not just configuration presence.
Incorrect Answers
A:That approach is designed for timezone date reporting: User-local timezone conversion changes the displayed calendar date across time zones. The present case instead involves the relationship's delete behavior would delete the inquiries along with the account.
B:This would respond to a different requirement (solution component missing column). It does not establish the needed result here: delete the test parent and confirm related inquiries still exist and their account lookups are cleared.
D:The proposed step addresses alternate key duplicate external id, not the constraint in this scenario. The decisive issue is that the relationship's delete behavior would delete the inquiries along with the account.
Question 19
An imported account is obsolete, but associated draft inquiries must survive without pointing to the removed account. What repeatable design control fits the root cause?
- Flag virtual-table feature restrictions before promising native Dataverse auditing or search.
- Identify virtual-table calculation restrictions in the data model review.
- Distinguish optional references from required references before configuring relationship actions.
- Specify numeric precision and rounding rules with finance stakeholders before schema creation.
Explanation
Correct Answer
C:Distinguish optional references from required references before configuring relationship actions. This helps prevent recurrence of: The relationship's delete behavior would delete the inquiries along with the account.
Incorrect Answers
A:That choice can be relevant to virtual-table auditing request, but its assumptions are absent from this case. Here the direct recurrence control is distinguish optional references from required references before configuring relationship actions.
B:The proposed step addresses computed field external source, not the constraint in this scenario. The decisive issue is that the relationship's delete behavior would delete the inquiries along with the account.
D:This would respond to a different requirement (currency precision concern). It does not establish the needed result here: distinguish optional references from required references before configuring relationship actions.
Question 20
An imported account is obsolete, but associated draft inquiries must survive without pointing to the removed account. Which THREE steps are justified for a complete controlled response? Select THREE.
- Create contacts for two accounts and verify each lookup resolves to exactly one account while an account can display multiple related contacts.
- Document cardinality and decide early whether the association requires its own status or effective-date columns.
- Use Remove Link for the delete action on an optional lookup so the inquiries remain with an empty parent reference.
- Delete the test parent and confirm related inquiries still exist and their account lookups are cleared.
- Distinguish optional references from required references before configuring relationship actions.
- Add the intended column and dependencies to the source solution and export a new version for deployment.
Explanation
Correct Answers
C:Use Remove Link for the delete action on an optional lookup so the inquiries remain with an empty parent reference. This directly addresses: The relationship's delete behavior would delete the inquiries along with the account.
D:Delete the test parent and confirm related inquiries still exist and their account lookups are cleared. This is required evidence before closure.
E:Distinguish optional references from required references before configuring relationship actions. This reduces recurrence of: The relationship's delete behavior would delete the inquiries along with the account.
Incorrect Answers
A:That choice can be relevant to account–contact one-to-many, but its assumptions are absent from this case. Here the direct discriminating test is delete the test parent and confirm related inquiries still exist and their account lookups are cleared.
B:Applying this would shift attention to supplier multiparty membership without testing the actual fault. The relationship's delete behavior would delete the inquiries along with the account.
F:The proposed step addresses solution component missing column, not the constraint in this scenario. The decisive issue is that the relationship's delete behavior would delete the inquiries along with the account.
Microsoft Power Platform Functional Consultant (PL-200) Practice Tests