100% Latest & Updated Microsoft PL-200 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 100
A nightly ETL re-creates existing products instead of updating changed product attributes, creating duplicates. Select THREE case-specific measures covering remediation, proof and longer-term prevention.
- Sample order records after import and verify their customer lookups resolve to correct parent rows.
- Require unique external IDs in integration contracts.
- Map a supported alternate key and configure an idempotent update/upsert approach in the ingestion process.
- Revise the rule to use stronger identifiers and test expected near matches and nonmatches.
- Re-run the same input and verify row counts stay stable while modified attributes update correctly.
- Design imports to be repeatable and monitor unmatched keys and duplicate rates.
Explanation
Correct Answers
C:Map a supported alternate key and configure an idempotent update/upsert approach in the ingestion process. This directly addresses: The ingestion process lacks a stable key and upsert-style matching strategy.
E:Re-run the same input and verify row counts stay stable while modified attributes update correctly. This is required evidence before closure.
F:Design imports to be repeatable and monitor unmatched keys and duplicate rates. This reduces recurrence of: The ingestion process lacks a stable key and upsert-style matching strategy.
Incorrect Answers
A:This choice targets lookup data import order and leaves the described requirement unproven. The case calls for re-run the same input and verify row counts stay stable while modified attributes update correctly.
B:That approach is designed for import lookup label ambiguity: Text display names are not unique identifiers and can resolve to the wrong related customer. The present case instead involves the ingestion process lacks a stable key and upsert-style matching strategy.
D:Applying this would shift attention to duplicate policy false positives without testing the actual fault. The ingestion process lacks a stable key and upsert-style matching strategy.
Question 101
Branch staff should read only their own branch's cases, but assigned security roles give organization-wide read access. Which underlying design issue accounts for the observed behavior?
- Capturing change history without a defined retention and access policy creates its own exposure.
- Role membership and row ownership are separate state; adding a user to a team does not transfer existing row owners.
- The selected ownership type introduces row ownership behavior that is not needed for global reference data.
- Organization-level privilege depth overrides the intended branch visibility boundary.
Explanation
Correct Answer
D:Reduce the relevant Read privilege depth and align record ownership and business units to the approved scope. The observed cause is: Organization-level privilege depth overrides the intended branch visibility boundary.
Incorrect Answers
A:This choice targets audit sensitive data retention and leaves the described requirement unproven. The case calls for organization-level privilege depth overrides the intended branch visibility boundary.
B:This would respond to a different requirement (record owner versus team confusion). It does not establish the needed result here: organization-level privilege depth overrides the intended branch visibility boundary.
C:That approach is designed for table ownership mismatch: The selected ownership type introduces row ownership behavior that is not needed for global reference data. The present case instead involves organization-level privilege depth overrides the intended branch visibility boundary.
Question 102
Branch staff should read only their own branch's cases, but assigned security roles give organization-wide read access. What should the consultant configure to correct the observed behavior?
- Reduce the relevant Read privilege depth and align record ownership and business units to the approved scope.
- Add the authorized user or group to the correct column-security profile with Read permission.
- Add Create at the narrowest appropriate depth and confirm any required related-table privileges.
- Share only the approved row with the investigator or qualifying team using limited privileges.
Explanation
Correct Answer
A:Reduce the relevant Read privilege depth and align record ownership and business units to the approved scope. This addresses: Organization-level privilege depth overrides the intended branch visibility boundary.
Incorrect Answers
B:The proposed step addresses column profile no permission, not the constraint in this scenario. The decisive issue is that organization-level privilege depth overrides the intended branch visibility boundary.
C:This would respond to a different requirement (role privilege for create). It does not establish the needed result here: reduce the relevant Read privilege depth and align record ownership and business units to the approved scope.
D:That approach is designed for sharing one exceptional row: Expanding the investigator's table privilege depth grants excessive unrelated access. The present case instead involves organization-level privilege depth overrides the intended branch visibility boundary.
Question 103
Branch staff should read only their own branch's cases, but assigned security roles give organization-wide read access. Which validation would demonstrate that the intended result has been achieved?
- Execute create/update/read tests for the integration while verifying unrelated privileged actions are denied.
- Verify Tax ID is visible to authorized users and still protected from unauthorized users.
- Log in as users from two branches and verify each sees only the permitted case rows.
- Share a test account and verify related private cases are not automatically readable.
Explanation
Correct Answer
C:Log in as users from two branches and verify each sees only the permitted case rows. This tests actual behavior, not just configuration presence.
Incorrect Answers
A:This would respond to a different requirement (service account overprivilege). It does not establish the needed result here: log in as users from two branches and verify each sees only the permitted case rows.
B:The proposed step addresses column profile no permission, not the constraint in this scenario. The decisive issue is that organization-level privilege depth overrides the intended branch visibility boundary.
D:That choice can be relevant to relationship cascade sharing, but its assumptions are absent from this case. Here the direct discriminating test is log in as users from two branches and verify each sees only the permitted case rows.
Question 104
Branch staff should read only their own branch's cases, but assigned security roles give organization-wide read access. What enduring control should be added to prevent this class of failure?
- Test privilege depth with representative users whenever organizational boundaries change.
- Include audit data in privacy impact and retention reviews.
- Treat directory group ownership and periodic access review as part of the authorization design.
- Record purpose, expiry and revocation for exceptional row shares.
Explanation
Correct Answer
A:Test privilege depth with representative users whenever organizational boundaries change. This helps prevent recurrence of: Organization-level privilege depth overrides the intended branch visibility boundary.
Incorrect Answers
B:That choice can be relevant to audit sensitive data retention, but its assumptions are absent from this case. Here the direct recurrence control is test privilege depth with representative users whenever organizational boundaries change.
C:The proposed step addresses entra group membership changes, not the constraint in this scenario. The decisive issue is that organization-level privilege depth overrides the intended branch visibility boundary.
D:Applying this would shift attention to sharing one exceptional row without testing the actual fault. Organization-level privilege depth overrides the intended branch visibility boundary.
Question 105
Branch staff should read only their own branch's cases, but assigned security roles give organization-wide read access. Which TWO choices form a coherent fix-and-validation response? Select TWO.
- Build approval assignments and time-bounded row sharing into workflow design.
- Log in as users from two branches and verify each sees only the permitted case rows.
- Use an owner team with appropriate privileges and assign eligible cases to the team.
- Try creating an order with the target role and ensure unrelated tables do not become editable.
- Reduce the relevant Read privilege depth and align record ownership and business units to the approved scope.
Explanation
Correct Answers
B:Log in as users from two branches and verify each sees only the permitted case rows. This is required evidence before closure.
E:Reduce the relevant Read privilege depth and align record ownership and business units to the approved scope. This directly addresses: Organization-level privilege depth overrides the intended branch visibility boundary.
Incorrect Answers
A:This choice targets cross-business-unit approval and leaves the described requirement unproven. The case calls for test privilege depth with representative users whenever organizational boundaries change.
C:That choice can be relevant to teams owning cases, but its assumptions are absent from this case. Here the direct corrective action is reduce the relevant Read privilege depth and align record ownership and business units to the approved scope.
D:Applying this would shift attention to role privilege for create without testing the actual fault. Organization-level privilege depth overrides the intended branch visibility boundary.
Question 106
Users can read Orders but receive insufficient privilege errors when creating an Order record. Which underlying design issue accounts for the observed behavior?
- Role membership and row ownership are separate state; adding a user to a team does not transfer existing row owners.
- Their security role grants Read but lacks a sufficient Create privilege for the Order table.
- The account has far more privileges than its operation requires.
- Capturing change history without a defined retention and access policy creates its own exposure.
Explanation
Correct Answer
B:Add Create at the narrowest appropriate depth and confirm any required related-table privileges. The observed cause is: Their security role grants Read but lacks a sufficient Create privilege for the Order table.
Incorrect Answers
A:That approach is designed for record owner versus team confusion: Role membership and row ownership are separate state; adding a user to a team does not transfer existing row owners. The present case instead involves their security role grants Read but lacks a sufficient Create privilege for the Order table.
C:This choice targets service account overprivilege and leaves the described requirement unproven. The case calls for their security role grants Read but lacks a sufficient Create privilege for the Order table.
D:Applying this would shift attention to audit sensitive data retention without testing the actual fault. Their security role grants Read but lacks a sufficient Create privilege for the Order table.
Question 107
Users can read Orders but receive insufficient privilege errors when creating an Order record. What should the consultant configure to correct the observed behavior?
- Disable or narrow the relevant Share cascade for cases with independent confidentiality.
- Assign a narrowly scoped custom security role and test required connector operations under that identity.
- Add Create at the narrowest appropriate depth and confirm any required related-table privileges.
- Use a supported Microsoft Entra ID group team with roles aligned to the directory group.
Explanation
Correct Answer
C:Add Create at the narrowest appropriate depth and confirm any required related-table privileges. This addresses: Their security role grants Read but lacks a sufficient Create privilege for the Order table.
Incorrect Answers
A:This would respond to a different requirement (relationship cascade sharing). It does not establish the needed result here: add Create at the narrowest appropriate depth and confirm any required related-table privileges.
B:That approach is designed for service account overprivilege: The account has far more privileges than its operation requires. The present case instead involves their security role grants Read but lacks a sufficient Create privilege for the Order table.
D:This choice targets entra group membership changes and leaves the described requirement unproven. The case calls for add Create at the narrowest appropriate depth and confirm any required related-table privileges.
Question 108
Users can read Orders but receive insufficient privilege errors when creating an Order record. Which observation would confirm the proposed design works as intended?
- Confirm access to the one record and denial to comparable unshared vendor records.
- Verify Tax ID is visible to authorized users and still protected from unauthorized users.
- Try creating an order with the target role and ensure unrelated tables do not become editable.
- Test salary visibility and edit rights as HR, non-HR and administrator users using actual records.
Explanation
Correct Answer
C:Try creating an order with the target role and ensure unrelated tables do not become editable. This tests actual behavior, not just configuration presence.
Incorrect Answers
A:That approach is designed for sharing one exceptional row: Expanding the investigator's table privilege depth grants excessive unrelated access. The present case instead involves their security role grants Read but lacks a sufficient Create privilege for the Order table.
B:The proposed step addresses column profile no permission, not the constraint in this scenario. The decisive issue is that their security role grants Read but lacks a sufficient Create privilege for the Order table.
D:This would respond to a different requirement (sensitive salary column). It does not establish the needed result here: try creating an order with the target role and ensure unrelated tables do not become editable.
Question 109
Users can read Orders but receive insufficient privilege errors when creating an Order record. What repeatable design control fits the root cause?
- Include audit data in privacy impact and retention reviews.
- Document hierarchy depth and review changes in reporting structure against access policies.
- Treat directory group ownership and periodic access review as part of the authorization design.
- Use least-privilege role matrices and test create/read/write/delete separately.
Explanation
Correct Answer
D:Use least-privilege role matrices and test create/read/write/delete separately. This helps prevent recurrence of: Their security role grants Read but lacks a sufficient Create privilege for the Order table.
Incorrect Answers
A:This would respond to a different requirement (audit sensitive data retention). It does not establish the needed result here: use least-privilege role matrices and test create/read/write/delete separately.
B:That choice can be relevant to manager hierarchy visibility, but its assumptions are absent from this case. Here the direct recurrence control is use least-privilege role matrices and test create/read/write/delete separately.
C:The proposed step addresses entra group membership changes, not the constraint in this scenario. The decisive issue is that their security role grants Read but lacks a sufficient Create privilege for the Order table.
Question 110
Users can read Orders but receive insufficient privilege errors when creating an Order record. Which THREE choices combine the needed correction, a meaningful test and a preventive control? Select THREE.
- Restrict audit-log access and configure supported retention/deletion aligned with the approved policy.
- Add Create at the narrowest appropriate depth and confirm any required related-table privileges.
- Try creating an order with the target role and ensure unrelated tables do not become editable.
- Apply data classification and column-security reviews to sensitive fields.
- Remove a pilot user from the directory group and verify effective Dataverse access updates after propagation.
- Use least-privilege role matrices and test create/read/write/delete separately.
Explanation
Correct Answers
B:Add Create at the narrowest appropriate depth and confirm any required related-table privileges. This directly addresses: Their security role grants Read but lacks a sufficient Create privilege for the Order table.
C:Try creating an order with the target role and ensure unrelated tables do not become editable. This is required evidence before closure.
F:Use least-privilege role matrices and test create/read/write/delete separately. This reduces recurrence of: Their security role grants Read but lacks a sufficient Create privilege for the Order table.
Incorrect Answers
A:The proposed step addresses audit sensitive data retention, not the constraint in this scenario. The decisive issue is that their security role grants Read but lacks a sufficient Create privilege for the Order table.
D:Applying this would shift attention to sensitive salary column without testing the actual fault. Their security role grants Read but lacks a sufficient Create privilege for the Order table.
E:That choice can be relevant to entra group membership changes, but its assumptions are absent from this case. Here the direct discriminating test is try creating an order with the target role and ensure unrelated tables do not become editable.
Microsoft Power Platform Functional Consultant (PL-200) Practice Tests