exam questions

Exam PL-900 All Questions

View all questions & answers for the PL-900 exam

Exam PL-900 topic 1 question 125 discussion

Actual exam question from Microsoft's PL-900
Question #: 125
Topic #: 1
[All PL-900 Questions]

DRAG DROP -
A medical office has a model-driven app that uses Microsoft Dataverse.
You plan to create a screen that allows users to capture information about doctors. The screen must provide users the ability to enter or select the following information:
✑ a place to enter doctor profile data that is not part of the account table or the contact table
✑ a place to enter the doctor's specialty in the profile form
✑ a column for insurance with the ability to pick one of 10 different insurance companies
You need to store the captured data in Common Data Service.
What should you use to store the data? To answer, drag the appropriate components to the correct requirements. Each component may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content.
NOTE: Each correct selection is worth one point.
Select and Place:

Show Suggested Answer Hide Answer
Suggested Answer:

Comments

Chosen Answer:
This is a voting comment (?). It is better to Upvote an existing comment if you don't have anything to add.
Switch to a voting comment New
CaneCorso
Highly Voted 3 years, 4 months ago
I think this should be: Entity (because question says it cannot be part of Account or Contact table) Field Option Set (because question says be able to pick from 10 insurance companies)
upvoted 76 times
MayaYao
1 year, 7 months ago
The first answer should be record. The keyword is "additional'.
upvoted 1 times
...
Gill
3 years ago
This is a very poor question - not only because it is still using the old terminology. The additional profile data could be entity or record - since records live in entities. The speciality could be field or option set - a lookup field is probably the best selection, but option set could work The insurance company could also be a field - free text or lookup - or an option set
upvoted 6 times
...
...
Jaykins
Highly Voted 3 years, 5 months ago
to store a new doctor profile, - this should be record (this is because it will take more than one field to store all the info about one doctor) 2. to store the doctor's specialty - this should be Field instead. (because it is one column or field that will hold that info amongst the doctors record) 3. Option set or (choice) new term for Option set
upvoted 31 times
ExamCert2022
3 years, 1 month ago
This is the choice and is correct for anybody knows SQL, even with basic SQL knowledge.
upvoted 2 times
...
Moiz1031
1 year, 7 months ago
for (a) question states the functional capability that allow user to enter profile information, in that sense entity is the container that can be used to implement this capability. Record is not the capability rather the outcome of the entity.So, Entity should be the right choice.
upvoted 1 times
...
...
COOKIE1901
Most Recent 4 months, 3 weeks ago
Store additional doctor profile data: Entity: Create a new entity to store the doctor profile data that is not part of the account table or the contact table. Store information about the doctor’s specialty: Field: Add a new field within the entity to capture the doctor’s specialty. Select an insurance company: Option set: Use an option set to allow users to pick one of the 10 different insurance companies.
upvoted 2 times
...
kishore1980
11 months, 4 weeks ago
1. Record 2. Field 3. Option
upvoted 1 times
...
AsuraX
12 months ago
My understanding: 1. Entity - Store additional doctor profile data. Entity is "A set of records used to store data" and in question there is "a place to enter doctor profile data that is not part of the account table or the contact table". So we need a separate place to store set of records. Even if we write all new data in one Record, this Record can not be part of existing tables, according to question. So I go with Entity. 2. Field - Store information about the doctor's speciality In question there is "a place to enter the doctor's specialty in the profile form". So each doctor have only ONE speciality and this data can be a part of existing tables. Record could be used (A record contains one or more categories of information), but you must always pick THE BEST option. So Field will be enough. 3. Option set - Select an insurance company According to question "a column for insurance with the ability to pick one of 10 different insurance companies". So, we have to prepare predefined list of options. So Option Set is the only pick.
upvoted 4 times
...
rmeng
1 year, 2 months ago
Store additional doctor profile data. -> Entity Store information about the doctor’s specialty. -> Field Select an insurance company. -> Option set
upvoted 7 times
...
Moiz1031
1 year, 5 months ago
For A I would create a new entity as the question says that the doctor profile is not part of either account or contact table. I would later create 1:N relationship b/w Doctor Profile and Contact entity.
upvoted 1 times
...
SHNH
2 years ago
Field/Record/Option Set
upvoted 2 times
...
Riyad795
2 years, 1 month ago
On Exam 12/16/2022. I passed with 896.
upvoted 3 times
...
Libertoo
2 years, 5 months ago
1. Field: Note that the question is on additional doctor profile data. Doctor's profile already exists as a record. You may only add fields to that record. He is not a new doctor. 2. Record. In a relational database this will be an ENTITY related to the doctor's profile with the Doctor's unique identity (Primary Key). But notice that the question says 'a place to enter the doctor's specialty in the profile form'. In System Analysis and Design, this is an area/block on a form/screen dedicated to capturing or maintaining doctor's specialty information which could be one or more fields (Record) that completely describes a doctor's specialty. 3. Option Set. Remember 'a column for insurance with the ability to pick one of 10 different insurance companies'. 10 is total no. in the Option Set simple.
upvoted 4 times
...
Libertoo
2 years, 5 months ago
1. Field: Note that the question is on additional doctor profile data. Doctor's profile already exists as a record. You may only add fields to that record. He is not a new doctor. 2. Record. In a relational database this will be an ENTITY related to the doctor's profile with the Doctor's unique identity (Primary Key). But notice that the question says 'a place to enter the doctor's specialty in the profile form'. In System Analysis and Design, and area/block on a form/screen dedicated to capturing or maintaining doctor's specialty information which could be one or more fields (Record) that completely describes a doctor's specialty 3. Option Set. Remember 'a column for insurance with the ability to pick one of 10 different insurance companies'. 10 is total no. in the Option Set simple.
upvoted 1 times
...
Rawat76
2 years, 5 months ago
no one knows what is the correct answer. This site is not reliable
upvoted 13 times
...
Akraios
2 years, 6 months ago
Considering these are all old terms (see here https://docs.microsoft.com/en-us/power-apps/maker/data-platform/data-platform-intro#terminology-updates), I would go for: Record (aka Row) Field (aka column) Optionset (Aka Choice)
upvoted 8 times
...
pgchand
2 years, 7 months ago
Question has "what should you use to store data" hence i go for Entity, Field and Record
upvoted 1 times
pgchand
2 years, 7 months ago
Sorry last one is Option set
upvoted 1 times
...
...
dsofzju
2 years, 7 months ago
Additional doctor profile data should be stored in Account or Contact table, therefore it should be filed(s) However, specialty is also additional info about the doctor and can also be stored as field in Account or Contact table. If so, the question needn't explicitly describe Specialty besides additional info. So I guess, the question means another table only used for doctor's specialty. Then a record makes sense. It is really hard to understand PL900 questions wording...Sounds like the guy who made these questions has a lot hidden information in his mind but he is reluctant to write them out assuming everyone knows his intention.
upvoted 1 times
dsofzju
2 years, 7 months ago
well, I just review the questions many times and changed my mind. Doctor is an entity, therefore there should be a table for this entity. Additional info out of Account or Contact should be stored here, so a record is used. Specialty should be a field of this table.
upvoted 1 times
...
...
Contactfornitish
2 years, 10 months ago
In exam today 11/04/2022 Record - 'Additional' doctor profile data, can't be entity Field - Single text Option Set - Optional data
upvoted 5 times
...
Timian
2 years, 10 months ago
Field - you can add a field/column to a table in the CDS/Dataverse since it doesn't exist in the account or contact table Record - The User table tom the CDS/Dataverse has a "Skills" column so you can add the specialty to that column, which is part of the doctor's record. Keep in mind you're using the CDS/Dataverse so all tables are available to use Option Set - because you're providing options
upvoted 1 times
...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel
Loading ...
exam
Someone Bought Contributor Access for:
SY0-701
London, 1 minute ago