The app builder should use Web-to-Case to enable visitors to the website to open cases. Web-to-Case is a feature that allows users to create an HTML form that can be embedded into a public-facing website. When visitors fill out and submit the form, a new case is automatically created in Salesforce with the information from the form fields. Web-to-Case can also assign cases to queues or users based on predefined rules and criteria. Outbound message is not a valid tool, as it does not enable visitors to open cases. An outbound message is a type of workflow action that sends a secure XML message to a designated endpoint URL when a record meets certain criteria. An outbound message can be used to integrate Salesforce with external systems or applications. Screen flow is not a valid tool, as it does not enable visitors to open cases from a public- facing website. A screen flow is a type of flow that allows users to create an interactive guided process that can collect, display, and update data from multiple objects within Salesforce. A screen flow can be embedded into Lightning pages or Visualforce pages, but it cannot be exposed to unauthenticated users on a public website. Email-to-Case is not a valid tool, as it does not enable visitors to open cases from a website. Email-to- Case is a feature that allows users to create cases from email messages sent to a specific email address. Email- to-Case can also capture email attachments and thread information and associate them with the case.

When Cloud Kicks needs to calculate summaries from child objects of a standard object declaratively, a few key considerations about master-detail relationships come into play. Master-detail relationships are critical in Salesforce when working with roll-up summary fields, which allow you to calculate values from child records.
* Option B: An object can have up to two master-detail relationships.
* Salesforce allows an object to have two master-detail relationships. This is important because if you want to aggregate child record data using roll-up summary fields, you need to have a master- detail relationship in place. Each master-detail relationship links a child object to a parent, and you can create roll-up summary fields on the parent object to summarize the child record data.

The "Sharing" button should be added to the Account page layout to allow sales reps to view the sharing details of an account record. This button enables users to see how access to the record is granted via roles, groups, and manual sharing.
A: Sharing Hierarchy provides a view of the role hierarchy but does not specifically detail record access.
B: New Task is unrelated to sharing visibility.
D: "Fait" is not recognized in Salesforce context as a valid component or feature. Reference: Sharing an Account in Salesforce Help Documentation

To start tracking how many shoe subscriptions have been sold for each shoe catalog, a roll-up summary field should be created. A roll-up summary field calculates values from related records on a master-detail relationship. It can count, sum, min, or max numeric values from child records on a parent record.