Ursa Major Solar requires a new field called Planet Details on the Planet object, where users can write detailed descriptions that can include pictures and links. The Rich Text Area field type is the best fit for this requirement.
Option B (Rich Text Area): A Rich Text Area field allows users to enter text with formatting options such as bold, italics, bullets, and numbering. Additionally, it supports inserting images and hyperlinks, which matches the requirement of including pictures and links in the description.
Rich Text Area Fields
Option A (Long Text Area): A Long Text Area field allows for lengthy text input but does not support formatting or embedding of images and links, which are necessary in this case.
Option C (Multi-Select Picklist): A Multi-Select Picklist allows users to select multiple values from a list but is not suitable for detailed descriptions or embedding images and links.
Option D (URL): A URL field is used to store and display a link but does not support text input or embedding images.
In summary, the Rich Text Area field type should be used because it allows formatted text, images, and links, which are required for the Planet Details field.

The solution that should meet this requirement is updating the support team profile to remove the Bronze record type. This way, the support team users will not be able to create new cases with the Bronze record type, as it will not appear in their record type selection list. Option A is incorrect because updating the organization-wide defaults to private for Case does not affect the record type availability, but rather the record access level. Option C is incorrect because creating permission set group for Case that includes Platinum and Diamond record types does not prevent the support team users from creating new cases with the Bronze record type, as they may still have access to it through their profile. Option D is incorrect because making the record type hidden to support users and updating sharing roles to private does not prevent the support team users from creating new cases with the Bronze record type, as they may still have access to it through their profile.

Opportunities are in a master-detail-like relationship with Accounts (standard lookup behaves with special roll-up capabilities). Salesforce provides a standard roll-up summary feature on the Account object to count related Opportunities.
Why B (Roll-up Summary) is correct:Exact Extract:"Use a roll-up summary field to automatically display a value from related detail records on a master record. You can count related records, or calculate the sum, min, or max of a field on those records." - Salesforce Help | Roll-Up Summary FieldsOn Account, you can create a roll-up summary field to COUNT related Opportunities.
Why B (Roll-up Summary) is correct:Exact Extract:"Use a roll-up summary field to automatically display a value from related detail records on a master record. You can count related records, or calculate the sum, min, or max of a field on those records." - Salesforce Help | Roll-Up Summary FieldsOn Account, you can create a roll-up summary field to COUNT related Opportunities.
Why not A:Formula fields cannot count related records.
Why not C:AppExchange is not required; Salesforce provides native functionality.
Why not D:A lookup only links records-it does not perform aggregation.
Reference:
Salesforce Help | Roll-Up Summary Fields
Salesforce Platform App Builder Exam Guide | Data Modeling and Management

All profiles will get access to the new field by default when it is created using Schema Builder. The app builder can modify the field-level security settings later to restrict access for certain profiles. Standard profiles, no profiles, and internal profiles are not correct options.

Polls and Out of Office are two ways that CK can use Chatter to gather feedback and understand availability. Polls allow users to create surveys and collect opinions from other users. Out of Office lets users set a status message and an end date to inform others when they are away or busy. Streams and Topics are not related to the problem.