D. No need to 2 record types.

Yeah the correct answer is D., just focus on one word for one record type both teams are using the same records

D is the answer. Create 1 record type. Field view depends on the assigned profile (via View Field Accessibility) and is displayed in one of the 2-page layouts...

D is the answer. Field view depends on the assigned profile (via View Field Accessibility) and is displayed in one of the 2-page layouts...

Changing my answer to D. Even though it's not the minimum configuration to meet the requirement, It is what I would most likely do. I think SpritiualBeing is correct. "...using one record type because it is same records - create two different page layout and assign it to the different profiles." Two profiles, simply so you can assign two different layouts to prevent both teams from having to see all possible fields. It wasn't actually a requirement, but most likely what the question/statement is implying.

A. One profile, one record type, one page layout. Nothing in the question suggests there are any security requirements needed for the two teams, so one profile will do. If there was an implication, then D would meet the minimum requirement. Since there is only one profile, there is no need to create am additional record type and therefore no need to create a second page layout tied to a different profile and record type. Both teams access the same object and the page layout can be configured to contain all fields necessary for both teams. That is the minimum needed to meet the requirements.

There is nothing in the question which suggests that the 2 teams need or use more than 1 record-type.

Correct answer is D. Both teams interact with the "same records". This statement simply takes two record types out from the equation, while all the other arguments here are also true

No need for 02 record types! D is right

D is correct Page Layouts => Page Layouts determine which fields are displayed to your users on a record. They allow you to add fields, sections, links, custom buttons, and a few other features. Record Types => Record Types let you offer different business processes, picklist values, and Page Layouts to different users.

I know there isn't a selection with no record types. However, what is the use of the record type here? We can create 2 profiles and two Page Layouts on the same object and share the fields. Add whatever fields needed to either page layout.

One record type is enough.

Correct answer should be D. Because: 1. The App Builder can create all 15 fields for the account object, then 2. Create two profiles, then 3. using one record type because it is same records - create two different page layout and assign it to the different profiles.

Answer C is correct because both teams serves different purpose so two profiles, two record types and two page-layout is the right fit.

D is correct

D - Can remove fields from page layout and use FLS to hide the fields via profile.

The answer is C. 2x Profiles + 2x Record Types + 2x Page Layouts for future expandability and scalability. Many of you has blind sight for future needs. BTW, the standard Account object alone has more than 10x standard fields already.