Exam PL-200 topic 1 question 62 discussion

Actual exam question from Microsoft's PL-200

Question #: 62
Topic #: 1

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.

After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.

A company uses a Dataverse environment. The environment is accessed from canvas and model-driven apps.

The Dataverse environment contains a table that has the following columns:

• Name
• Company
• Contacted On

The company requires that the table not contain any duplicate rows when users create data in the environment.

You need to implement a solution that meets the requirement.

Solution: Create an alternate key for the columns.

Does the solution meet the goal?

A. Yes
B. No

Show Suggested Answer

Suggested Answer: A 🗳️

by DaanEp at Jan. 24, 2024, 6:14 p.m.

Comments

Submit Cancel

iRoMeL

1 month, 1 week ago

Selected Answer: A

The correct answer is: ✅ A. Yes ⸻ ✅ Explanation: Alternate keys in Dataverse are used to enforce uniqueness constraints on one or more columns in a table. When you create an alternate key using columns like Name, Company, and Contacted On, Dataverse will prevent duplicate rows based on the combination of those column values. • This solution works at the platform level and is respected by both canvas apps and model-driven apps. • Alternate keys are also used for integration and can improve performance when querying records.

upvoted 1 times

...

JohnChung

8 months, 3 weeks ago

Selected Answer: A

An alternate key can ensure there is no duplicated record in a single table

upvoted 1 times

...

MrEz

10 months ago

you can make alternate keys with multiple fields name and company and contacted on. but there are 3 problems: we don't know if contacted on is date and time or date only. same name same date same company, e.g. 2 phone calls --> needs to be saved because one was in the morning and one was in the afternoon. :-) Name = standard field? like subject? if by chance the have the same topic and the user enters the same name. e.g. 2 different people call from the same company at the same time and the customer helpdesk agents enter 'super bowl ticket expiration' for name ... you are doomed. okay maybe name is fullname George W. Bush, working both (senior and junior) for Carlyle group and both have a scheduled call at 08:15 for the same company... but technically you can. yes we can.

upvoted 1 times

...

DaanEp

10 months, 3 weeks ago

Selected Answer: A

you want to ensure that there are no duplicate rows based on the "Name," "Company," and "Contacted On" columns. Creating an alternate key for these columns will enforce this uniqueness constraint, and users won't be able to insert rows with the same combination of values in these columns. So, the solution of creating an alternate key aligns with the goal of preventing duplicate rows, and it is a valid approach in Dataverse.

upvoted 1 times

...