100% Latest & Updated Microsoft PL-200 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 160
An audit feature records old values of a highly sensitive field, but retention requirements prohibit indefinite historical exposure. Which THREE choices combine the needed correction, a meaningful test and a preventive control? Select THREE.
- Use an owner team with appropriate privileges and assign eligible cases to the team.
- Include audit data in privacy impact and retention reviews.
- Try creating an order with the target role and ensure unrelated tables do not become editable.
- Inspect audit visibility for nonprivileged users and verify purging obeys retention controls.
- Treat directory group ownership and periodic access review as part of the authorization design.
- Restrict audit-log access and configure supported retention/deletion aligned with the approved policy.
Explanation
Correct Answers
B:Include audit data in privacy impact and retention reviews. This reduces recurrence of: Capturing change history without a defined retention and access policy creates its own exposure.
D:Inspect audit visibility for nonprivileged users and verify purging obeys retention controls. This is required evidence before closure.
F:Restrict audit-log access and configure supported retention/deletion aligned with the approved policy. This directly addresses: Capturing change history without a defined retention and access policy creates its own exposure.
Incorrect Answers
A:Applying this would shift attention to teams owning cases without testing the actual fault. Capturing change history without a defined retention and access policy creates its own exposure.
C:This choice targets role privilege for create and leaves the described requirement unproven. The case calls for inspect audit visibility for nonprivileged users and verify purging obeys retention controls.
E:That approach is designed for entra group membership changes: A manually maintained team can lag behind the identity source and retain stale members. The present case instead involves capturing change history without a defined retention and access policy creates its own exposure.
Question 161
An account shared with a temporary advisor unexpectedly exposes all its related cases. What mechanism should the consultant identify before making changes?
- A flat role with organization-wide privileges would disclose peers' cases beyond the chain of command.
- The base role's business-unit depth does not extend to the cross-unit record.
- Relationship Share cascade is granting related-row access through the parent share.
- The account has far more privileges than its operation requires.
Explanation
Correct Answer
C:Disable or narrow the relevant Share cascade for cases with independent confidentiality. The observed cause is: Relationship Share cascade is granting related-row access through the parent share.
Incorrect Answers
A:This would respond to a different requirement (manager hierarchy visibility). It does not establish the needed result here: relationship Share cascade is granting related-row access through the parent share.
B:This choice targets cross-business-unit approval and leaves the described requirement unproven. The case calls for relationship Share cascade is granting related-row access through the parent share.
D:That approach is designed for service account overprivilege: The account has far more privileges than its operation requires. The present case instead involves relationship Share cascade is granting related-row access through the parent share.
Question 162
An account shared with a temporary advisor unexpectedly exposes all its related cases. What should the consultant configure to correct the observed behavior?
- Disable or narrow the relevant Share cascade for cases with independent confidentiality.
- Restrict audit-log access and configure supported retention/deletion aligned with the approved policy.
- Enable column security and assign a column-security profile with appropriate read and update permissions.
- Assign a narrowly scoped custom security role and test required connector operations under that identity.
Explanation
Correct Answer
A:Disable or narrow the relevant Share cascade for cases with independent confidentiality. This addresses: Relationship Share cascade is granting related-row access through the parent share.
Incorrect Answers
B:The proposed step addresses audit sensitive data retention, not the constraint in this scenario. The decisive issue is that relationship Share cascade is granting related-row access through the parent share.
C:This would respond to a different requirement (sensitive salary column). It does not establish the needed result here: disable or narrow the relevant Share cascade for cases with independent confidentiality.
D:That approach is designed for service account overprivilege: The account has far more privileges than its operation requires. The present case instead involves relationship Share cascade is granting related-row access through the parent share.
Question 163
An account shared with a temporary advisor unexpectedly exposes all its related cases. What test would most clearly distinguish a successful fix from a superficial change?
- Try direct record access and search as the test user to verify both enforce the same permission boundary.
- Test salary visibility and edit rights as HR, non-HR and administrator users using actual records.
- Execute create/update/read tests for the integration while verifying unrelated privileged actions are denied.
- Share a test account and verify related private cases are not automatically readable.
Explanation
Correct Answer
D:Share a test account and verify related private cases are not automatically readable. This tests actual behavior, not just configuration presence.
Incorrect Answers
A:That choice can be relevant to search index leakage test, but its assumptions are absent from this case. Here the direct discriminating test is share a test account and verify related private cases are not automatically readable.
B:The proposed step addresses sensitive salary column, not the constraint in this scenario. The decisive issue is that relationship Share cascade is granting related-row access through the parent share.
C:This would respond to a different requirement (service account overprivilege). It does not establish the needed result here: share a test account and verify related private cases are not automatically readable.
Question 164
An account shared with a temporary advisor unexpectedly exposes all its related cases. Which preventive practice best reduces recurrence of this issue?
- Never rely on interface hiding as a substitute for server-side privileges.
- Choose ownership model at design time because it constrains later security options.
- Add ownership reconciliation to bulk transition runbooks.
- Include relationship cascades in security reviews for temporary collaboration.
Explanation
Correct Answer
D:Include relationship cascades in security reviews for temporary collaboration. This helps prevent recurrence of: Relationship Share cascade is granting related-row access through the parent share.
Incorrect Answers
A:The proposed step addresses search index leakage test, not the constraint in this scenario. The decisive issue is that relationship Share cascade is granting related-row access through the parent share.
B:That choice can be relevant to table ownership mismatch, but its assumptions are absent from this case. Here the direct recurrence control is include relationship cascades in security reviews for temporary collaboration.
C:Applying this would shift attention to record owner versus team confusion without testing the actual fault. Relationship Share cascade is granting related-row access through the parent share.
Question 165
An account shared with a temporary advisor unexpectedly exposes all its related cases. Which TWO measures together implement the targeted correction and verify its result? Select TWO.
- Assign a narrowly scoped custom security role and test required connector operations under that identity.
- Share a test account and verify related private cases are not automatically readable.
- Disable or narrow the relevant Share cascade for cases with independent confidentiality.
- Execute create/update/read tests for the integration while verifying unrelated privileged actions are denied.
- Document hierarchy depth and review changes in reporting structure against access policies.
Explanation
Correct Answers
B:Share a test account and verify related private cases are not automatically readable. This is required evidence before closure.
C:Disable or narrow the relevant Share cascade for cases with independent confidentiality. This directly addresses: Relationship Share cascade is granting related-row access through the parent share.
Incorrect Answers
A:That choice can be relevant to service account overprivilege, but its assumptions are absent from this case. Here the direct corrective action is disable or narrow the relevant Share cascade for cases with independent confidentiality.
D:Applying this would shift attention to service account overprivilege without testing the actual fault. Relationship Share cascade is granting related-row access through the parent share.
E:This choice targets manager hierarchy visibility and leaves the described requirement unproven. The case calls for include relationship cascades in security reviews for temporary collaboration.
Question 166
Two customers share the same display name; a CSV uses only names to populate Order customer lookups. Which explanation best fits the described evidence?
- The bulk deletion scope is too broad and would remove records under retention hold.
- Text display names are not unique identifiers and can resolve to the wrong related customer.
- The matching criteria are not selective enough to identify actual duplicate identities.
- The new table has not been enabled or indexed for Dataverse search.
Explanation
Correct Answer
B:Map stable unique customer keys or alternate keys rather than ambiguous display labels. The observed cause is: Text display names are not unique identifiers and can resolve to the wrong related customer.
Incorrect Answers
A:That approach is designed for bulk deletion safety: The bulk deletion scope is too broad and would remove records under retention hold. The present case instead involves text display names are not unique identifiers and can resolve to the wrong related customer.
C:Applying this would shift attention to duplicate policy false positives without testing the actual fault. Text display names are not unique identifiers and can resolve to the wrong related customer.
D:This choice targets dataverse search disabled table and leaves the described requirement unproven. The case calls for text display names are not unique identifiers and can resolve to the wrong related customer.
Question 167
Two customers share the same display name; a CSV uses only names to populate Order customer lookups. What should the consultant configure to correct the observed behavior?
- Enable the Asset table for Dataverse search and configure its searchable fields, then allow indexing time.
- Refine and validate the deletion query, exclude retained records and obtain approval before execution.
- Map a supported alternate key and configure an idempotent update/upsert approach in the ingestion process.
- Map stable unique customer keys or alternate keys rather than ambiguous display labels.
Explanation
Correct Answer
D:Map stable unique customer keys or alternate keys rather than ambiguous display labels. This addresses: Text display names are not unique identifiers and can resolve to the wrong related customer.
Incorrect Answers
A:This choice targets dataverse search disabled table and leaves the described requirement unproven. The case calls for map stable unique customer keys or alternate keys rather than ambiguous display labels.
B:This would respond to a different requirement (bulk deletion safety). It does not establish the needed result here: map stable unique customer keys or alternate keys rather than ambiguous display labels.
C:That approach is designed for dataflow incremental updates: The ingestion process lacks a stable key and upsert-style matching strategy. The present case instead involves text display names are not unique identifiers and can resolve to the wrong related customer.
Question 168
Two customers share the same display name; a CSV uses only names to populate Order customer lookups. Which validation would demonstrate that the intended result has been achieved?
- Submit two different contacts from the same city and confirm they are not erroneously flagged.
- Search for a unique asset identifier and confirm expected results after indexing completes.
- Verify imported order records resolve to expected customer IDs for the two namesakes.
- Compare dry-run counts and IDs against retention exclusions before a limited controlled delete.
Explanation
Correct Answer
C:Verify imported order records resolve to expected customer IDs for the two namesakes. This tests actual behavior, not just configuration presence.
Incorrect Answers
A:The proposed step addresses duplicate policy false positives, not the constraint in this scenario. The decisive issue is that text display names are not unique identifiers and can resolve to the wrong related customer.
B:That approach is designed for dataverse search disabled table: The new table has not been enabled or indexed for Dataverse search. The present case instead involves text display names are not unique identifiers and can resolve to the wrong related customer.
D:This would respond to a different requirement (bulk deletion safety). It does not establish the needed result here: verify imported order records resolve to expected customer IDs for the two namesakes.
Question 169
Two customers share the same display name; a CSV uses only names to populate Order customer lookups. Which preventive practice best reduces recurrence of this issue?
- Design imports to be repeatable and monitor unmatched keys and duplicate rates.
- Measure match precision and false-positive rates before publishing duplicate rules.
- Define deterministic matching keys and preimport duplicate reports for recurring data loads.
- Require unique external IDs in integration contracts.
Explanation
Correct Answer
D:Require unique external IDs in integration contracts. This helps prevent recurrence of: Text display names are not unique identifiers and can resolve to the wrong related customer.
Incorrect Answers
A:The proposed step addresses dataflow incremental updates, not the constraint in this scenario. The decisive issue is that text display names are not unique identifiers and can resolve to the wrong related customer.
B:This would respond to a different requirement (duplicate policy false positives). It does not establish the needed result here: require unique external IDs in integration contracts.
C:That choice can be relevant to duplicate-contact imports, but its assumptions are absent from this case. Here the direct recurrence control is require unique external IDs in integration contracts.
Question 170
Two customers share the same display name; a CSV uses only names to populate Order customer lookups. Which THREE steps are justified for a complete controlled response? Select THREE.
- Verify imported order records resolve to expected customer IDs for the two namesakes.
- Enable environment auditing where needed and the table and applicable column auditing settings.
- Submit two different contacts from the same city and confirm they are not erroneously flagged.
- Map stable unique customer keys or alternate keys rather than ambiguous display labels.
- Include search eligibility and indexing behavior in table rollout acceptance tests.
- Require unique external IDs in integration contracts.
Explanation
Correct Answers
A:Verify imported order records resolve to expected customer IDs for the two namesakes. This is required evidence before closure.
D:Map stable unique customer keys or alternate keys rather than ambiguous display labels. This directly addresses: Text display names are not unique identifiers and can resolve to the wrong related customer.
F:Require unique external IDs in integration contracts. This reduces recurrence of: Text display names are not unique identifiers and can resolve to the wrong related customer.
Incorrect Answers
B:The proposed step addresses audit history missing updates, not the constraint in this scenario. The decisive issue is that text display names are not unique identifiers and can resolve to the wrong related customer.
C:That choice can be relevant to duplicate policy false positives, but its assumptions are absent from this case. Here the direct discriminating test is verify imported order records resolve to expected customer IDs for the two namesakes.
E:Applying this would shift attention to dataverse search disabled table without testing the actual fault. Text display names are not unique identifiers and can resolve to the wrong related customer.
Microsoft Power Platform Functional Consultant (PL-200) Practice Tests