100% Latest & Updated Microsoft PL-200 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 70
An app maker creates a table named Project but an unrelated ISV already has a Project table under a different publisher. Which THREE steps are justified for a complete controlled response? Select THREE.
- Examine table schema names in the solution and confirm forms and lookups point to the intended logical name.
- Select the correct table by logical name and use a distinct publisher prefix for newly owned schema.
- Reimport the same external ID and confirm one row is updated rather than a second row created.
- Maintain a publisher-prefix and logical-name registry for solution components.
- Choose an appropriate supported decimal or currency precision and migrate existing values under a reviewed conversion plan.
- Flag virtual-table feature restrictions before promising native Dataverse auditing or search.
Explanation
Correct Answers
A:Examine table schema names in the solution and confirm forms and lookups point to the intended logical name. This is required evidence before closure.
B:Select the correct table by logical name and use a distinct publisher prefix for newly owned schema. This directly addresses: Reusing an ambiguous display label risks binding the wrong logical table to new components.
D:Maintain a publisher-prefix and logical-name registry for solution components. This reduces recurrence of: Reusing an ambiguous display label risks binding the wrong logical table to new components.
Incorrect Answers
C:This choice targets alternate key duplicate external id and leaves the described requirement unproven. The case calls for examine table schema names in the solution and confirm forms and lookups point to the intended logical name.
E:Applying this would shift attention to currency precision concern without testing the actual fault. Reusing an ambiguous display label risks binding the wrong logical table to new components.
F:That approach is designed for virtual-table auditing request: Dataverse virtual tables do not support ordinary local row auditing. The present case instead involves reusing an ambiguous display label risks binding the wrong logical table to new components.
Question 71
Users can search Contacts but not the newly added custom Asset table even though records exist and role read access is correct. Which underlying design issue accounts for the observed behavior?
- The new table has not been enabled or indexed for Dataverse search.
- The matching criteria are not selective enough to identify actual duplicate identities.
- The ingestion process lacks a stable key and upsert-style matching strategy.
- A draft or disabled duplicate rule will not enforce the intended import detection.
Explanation
Correct Answer
A:Enable the Asset table for Dataverse search and configure its searchable fields, then allow indexing time. The observed cause is: The new table has not been enabled or indexed for Dataverse search.
Incorrect Answers
B:This choice targets duplicate policy false positives and leaves the described requirement unproven. The case calls for the new table has not been enabled or indexed for Dataverse search.
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 the new table has not been enabled or indexed for Dataverse search.
D:This would respond to a different requirement (duplicate-contact imports). It does not establish the needed result here: the new table has not been enabled or indexed for Dataverse search.
Question 72
Users can search Contacts but not the newly added custom Asset table even though records exist and role read access is correct. Which targeted change best addresses this requirement?
- Map stable unique customer keys or alternate keys rather than ambiguous display labels.
- Enable the Asset table for Dataverse search and configure its searchable fields, then allow indexing time.
- Enable environment auditing where needed and the table and applicable column auditing settings.
- Import and reconcile customers first, then orders using stable mapped relationship keys.
Explanation
Correct Answer
B:Enable the Asset table for Dataverse search and configure its searchable fields, then allow indexing time. This addresses: The new table has not been enabled or indexed for Dataverse search.
Incorrect Answers
A:The proposed step addresses import lookup label ambiguity, not the constraint in this scenario. The decisive issue is that the new table has not been enabled or indexed for Dataverse search.
C:This would respond to a different requirement (audit history missing updates). It does not establish the needed result here: enable the Asset table for Dataverse search and configure its searchable fields, then allow indexing time.
D:That approach is designed for lookup data import order: Child records arrive before their parent keys exist in Dataverse. The present case instead involves the new table has not been enabled or indexed for Dataverse search.
Question 73
Users can search Contacts but not the newly added custom Asset table even though records exist and role read access is correct. What test would most clearly distinguish a successful fix from a superficial change?
- Verify imported order records resolve to expected customer IDs for the two namesakes.
- Sample order records after import and verify their customer lookups resolve to correct parent rows.
- Modify the contract status under a test user and verify the actor, timestamp and old/new values are recorded.
- Search for a unique asset identifier and confirm expected results after indexing completes.
Explanation
Correct Answer
D:Search for a unique asset identifier and confirm expected results after indexing completes. This tests actual behavior, not just configuration presence.
Incorrect Answers
A:This would respond to a different requirement (import lookup label ambiguity). It does not establish the needed result here: search for a unique asset identifier and confirm expected results after indexing completes.
B:That choice can be relevant to lookup data import order, but its assumptions are absent from this case. Here the direct discriminating test is search for a unique asset identifier and confirm expected results after indexing completes.
C:The proposed step addresses audit history missing updates, not the constraint in this scenario. The decisive issue is that the new table has not been enabled or indexed for Dataverse search.
Question 74
Users can search Contacts but not the newly added custom Asset table even though records exist and role read access is correct. Which governance practice most directly protects this requirement over time?
- Define deterministic matching keys and preimport duplicate reports for recurring data loads.
- Require unique external IDs in integration contracts.
- Measure match precision and false-positive rates before publishing duplicate rules.
- Include search eligibility and indexing behavior in table rollout acceptance tests.
Explanation
Correct Answer
D:Include search eligibility and indexing behavior in table rollout acceptance tests. This helps prevent recurrence of: The new table has not been enabled or indexed for Dataverse search.
Incorrect Answers
A:That choice can be relevant to duplicate-contact imports, but its assumptions are absent from this case. Here the direct recurrence control is include search eligibility and indexing behavior in table rollout acceptance tests.
B:Applying this would shift attention to import lookup label ambiguity without testing the actual fault. The new table has not been enabled or indexed for Dataverse search.
C:The proposed step addresses duplicate policy false positives, not the constraint in this scenario. The decisive issue is that the new table has not been enabled or indexed for Dataverse search.
Question 75
Users can search Contacts but not the newly added custom Asset table even though records exist and role read access is correct. Which TWO choices form a coherent fix-and-validation response? Select TWO.
- Sample order records after import and verify their customer lookups resolve to correct parent rows.
- Enable environment auditing where needed and the table and applicable column auditing settings.
- Enable the Asset table for Dataverse search and configure its searchable fields, then allow indexing time.
- Establish dependency ordering and reconciliation reports for multi-table migrations.
- Search for a unique asset identifier and confirm expected results after indexing completes.
Explanation
Correct Answers
C:Enable the Asset table for Dataverse search and configure its searchable fields, then allow indexing time. This directly addresses: The new table has not been enabled or indexed for Dataverse search.
E:Search for a unique asset identifier and confirm expected results after indexing completes. This is required evidence before closure.
Incorrect Answers
A:Applying this would shift attention to lookup data import order without testing the actual fault. The new table has not been enabled or indexed for Dataverse search.
B:That choice can be relevant to audit history missing updates, but its assumptions are absent from this case. Here the direct corrective action is enable the Asset table for Dataverse search and configure its searchable fields, then allow indexing time.
D:This choice targets lookup data import order and leaves the described requirement unproven. The case calls for include search eligibility and indexing behavior in table rollout acceptance tests.
Question 76
Audit logs contain account creation but no changes to a sensitive contract-status column. Which explanation best fits the described evidence?
- The matching criteria are not selective enough to identify actual duplicate identities.
- Auditing was not enabled for the relevant table and column change path.
- A draft or disabled duplicate rule will not enforce the intended import detection.
- Child records arrive before their parent keys exist in Dataverse.
Explanation
Correct Answer
B:Enable environment auditing where needed and the table and applicable column auditing settings. The observed cause is: Auditing was not enabled for the relevant table and column change path.
Incorrect Answers
A:That approach is designed for duplicate policy false positives: The matching criteria are not selective enough to identify actual duplicate identities. The present case instead involves auditing was not enabled for the relevant table and column change path.
C:This choice targets duplicate-contact imports and leaves the described requirement unproven. The case calls for auditing was not enabled for the relevant table and column change path.
D:Applying this would shift attention to lookup data import order without testing the actual fault. Auditing was not enabled for the relevant table and column change path.
Question 77
Audit logs contain account creation but no changes to a sensitive contract-status column. Which implementation decision best fixes the stated problem?
- Import and reconcile customers first, then orders using stable mapped relationship keys.
- Enable duplicate detection at the required levels and publish the appropriate rule before controlled import.
- Revise the rule to use stronger identifiers and test expected near matches and nonmatches.
- Enable environment auditing where needed and the table and applicable column auditing settings.
Explanation
Correct Answer
D:Enable environment auditing where needed and the table and applicable column auditing settings. This addresses: Auditing was not enabled for the relevant table and column change path.
Incorrect Answers
A:This would respond to a different requirement (lookup data import order). It does not establish the needed result here: enable environment auditing where needed and the table and applicable column auditing settings.
B:That approach is designed for duplicate-contact imports: A draft or disabled duplicate rule will not enforce the intended import detection. The present case instead involves auditing was not enabled for the relevant table and column change path.
C:This choice targets duplicate policy false positives and leaves the described requirement unproven. The case calls for enable environment auditing where needed and the table and applicable column auditing settings.
Question 78
Audit logs contain account creation but no changes to a sensitive contract-status column. Which observation would confirm the proposed design works as intended?
- 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.
- Compare dry-run counts and IDs against retention exclusions before a limited controlled delete.
- Modify the contract status under a test user and verify the actor, timestamp and old/new values are recorded.
Explanation
Correct Answer
D:Modify the contract status under a test user and verify the actor, timestamp and old/new values are recorded. 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 auditing was not enabled for the relevant table and column change path.
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 auditing was not enabled for the relevant table and column change path.
C:This would respond to a different requirement (bulk deletion safety). It does not establish the needed result here: modify the contract status under a test user and verify the actor, timestamp and old/new values are recorded.
Question 79
Audit logs contain account creation but no changes to a sensitive contract-status column. Which preventive practice best reduces recurrence of this issue?
- Require query review and recoverability assessment for scheduled bulk operations.
- Require unique external IDs in integration contracts.
- Include audit enablement and retention decisions in the compliance control checklist.
- Measure match precision and false-positive rates before publishing duplicate rules.
Explanation
Correct Answer
C:Include audit enablement and retention decisions in the compliance control checklist. This helps prevent recurrence of: Auditing was not enabled for the relevant table and column change path.
Incorrect Answers
A:This would respond to a different requirement (bulk deletion safety). It does not establish the needed result here: include audit enablement and retention decisions in the compliance control checklist.
B:The proposed step addresses import lookup label ambiguity, not the constraint in this scenario. The decisive issue is that auditing was not enabled for the relevant table and column change path.
D:That choice can be relevant to duplicate policy false positives, but its assumptions are absent from this case. Here the direct recurrence control is include audit enablement and retention decisions in the compliance control checklist.
Question 80
Audit logs contain account creation but no changes to a sensitive contract-status column. Which THREE choices combine the needed correction, a meaningful test and a preventive control? Select THREE.
- Define deterministic matching keys and preimport duplicate reports for recurring data loads.
- Modify the contract status under a test user and verify the actor, timestamp and old/new values are recorded.
- Enable environment auditing where needed and the table and applicable column auditing settings.
- Run a duplicate-detection job or controlled import and verify matching identifier rows are flagged for review.
- Include audit enablement and retention decisions in the compliance control checklist.
- Map stable unique customer keys or alternate keys rather than ambiguous display labels.
Explanation
Correct Answers
B:Modify the contract status under a test user and verify the actor, timestamp and old/new values are recorded. This is required evidence before closure.
C:Enable environment auditing where needed and the table and applicable column auditing settings. This directly addresses: Auditing was not enabled for the relevant table and column change path.
E:Include audit enablement and retention decisions in the compliance control checklist. This reduces recurrence of: Auditing was not enabled for the relevant table and column change path.
Incorrect Answers
A:Applying this would shift attention to duplicate-contact imports without testing the actual fault. Auditing was not enabled for the relevant table and column change path.
D:That choice can be relevant to duplicate-contact imports, but its assumptions are absent from this case. Here the direct discriminating test is modify the contract status under a test user and verify the actor, timestamp and old/new values are recorded.
F:The proposed step addresses import lookup label ambiguity, not the constraint in this scenario. The decisive issue is that auditing was not enabled for the relevant table and column change path.
Microsoft Power Platform Functional Consultant (PL-200) Practice Tests