Universal Containers has three separate lines of business. Each line has specific fields that must be displayed to users. However, the fields needed…

The requirement involves two distinct layers of customization. First, there are three separate lines of business, each with its own specific processes and data needs. This is the primary function of Record Types, which allow for different business processes, picklist values, and page layout assignments. Second, within each line of business, the sales and service teams require different views of the data. This is addressed by Page Layouts, which control the fields, sections, and related lists on a record's detail page. By creating three record types (one for each business line) and then assigning two different page layouts (one for sales, one for service) to the appropriate user profiles for each of those record types, the administrator can precisely meet the requirements.

A. Create two record types, each with 3 page layouts.

This configuration does not align with the stated requirement for three separate lines of business.

B. Create one record type with six Page Layouts.

Using a single record type fails to separate the distinct business processes and picklist values for the three different lines of business.

D. Create six record types, each with 1 page layout.

This is overly complex. The difference between sales and service team views is a user interface distinction, best handled by page layouts, not separate business processes requiring new record types.

1. Salesforce Help Documentation, "Create Record Types": "Record types let you offer different business processes, picklist values, and page layouts to different users. You might create record types to differentiate your regular sales deals from your professional services engagements, offering different picklist values for each." This supports using record types for different lines of business.

2. Salesforce Help Documentation, "Assign Page Layouts to Profiles or Record Types": "After you create or edit a page layout, specify which users see it. A user’s profile determines which page layout they see. In addition, if your organization uses record types for an object, the combination of the user’s profile and the record type determine which page layout is displayed." This confirms that a unique page layout can be assigned based on the combination of a profile (e.g., Sales User) and a record type (e.g., Business Line A).

3. Trailhead, "Data Modeling" Module, "Customize Record Details with Page Layouts" Unit: "When you have record types for an object, you can also assign a page layout to a specific record type. For example, the page layout for a new account that’s a technology partner can be different from a new account that’s a supplier." This directly illustrates the principle of assigning different page layouts based on record types.