A. You need record type to control picklist values.

A. We need 3 record types (picklist values) each with own page layout (displayed fields). Though I don't get why separate profiles for each team. Single profile would work here.

A. Record types control the picklist values. Jason_R gave a good explanation why the other options are not as valid as A.

Jason_R has a well-written explanation. I would write the same.

A. With a custom project evaluation object, create separate record types with different picklist values and page layouts for each team. Create and assign separate profiles by team. Not B becuse page layouts alone don't control individual picklist values. Record types do. Not C because while that would work, it's overkill. The much simpler solution is A. Not D because permission sets alone don't control individual picklist values. Record types do.

A. Need to have seperated record types to have different picklist values.

A record types are needed

Selected Answer: A

def "A"

A is correct -

A is correct -

Why not D?! To me the requirement is to have different fields for the different teams, not different records for the different teams

Record types control picklist values

A is correct

A is correct

Use multiple business processes to display different picklist values according to each user’s profile. Use multiple business processes to track separate sales, support, and lead lifecycles. https://help.salesforce.com/s/articleView?id=sf.customize_recordtype.htm&type=5

A is the correct answer: https://help.salesforce.com/s/articleView?id=sf.users_profiles_record_types.htm&type=5