To communicate to the CK web service when a shoe's inventory has changed, an app builder should use an after-save record-triggered flow. An after-save record-triggered flow is a type of flow that runs after a record is saved and can perform actions such as updating related records, sending emails, calling external services, etc. An after-save record-triggered flow can use an Apex action to invoke a SOAP web service using a WSDL file. [Source]

To restrict visibility of the Jupiter field on the Solar System object specifically to users with the Outer Planets profile:
* C. Field-level security (FLS). This allows the app builder to control access to fields based on user profiles.
Steps to set up field-level security:
* Navigate to Setup # Object Manager # Solar System.
* Select Fields & Relationships # Jupiter field.
* Click Field-Level Security.
* For all profiles except Outer Planets, set the Visible option to unchecked, ensuring these users cannot see the field.
* For the Outer Planets profile, check Visible to grant access.
This configuration ensures that only users with the Outer Planets profile can view the Jupiter field.
For more information on field-level security, check Salesforce's guide on Field-Level Security.

It lacks setting up field-level security and adding fields to the page layout, so you have to choose the manual way of field creation. Adds another layer of risk with changes in Schema Builder since it is deployed in real- time.
Salesforce Schema Builder is a powerful tool for visualizing and creating objects, fields, and relationships in Salesforce, but it has certain limitations when building custom objects.
* Option B (Fields and relationships can be created, but they will be unable to add the fields to the page layout from the canvas): In Schema Builder, while you can create new custom objects, fields, and relationships, you cannot directly add fields to the page layout from within the Schema Builder interface. After creating a field, you need to navigate to the Page Layout Editor to manually place the new field on the layout.

Record-triggered flow is the automation tool that the app builder should use to best address all these requests of sending an email to the finance manager and creating a task for the sales manager when a new client is won. According to the Salesforce documentation, "Record-triggered flows automate processes for you. They start when a record is created or updated, or when a platform event occurs." A record-triggered flow can perform actions such as sending an email alert or creating a record based on criteria or conditions. Screen flow, Apex, and Approval process are not automation tools that can handle all these requests.

For reporting snapshots, the source report must be capable of grouping data, which is necessary for summarizing information at specific intervals. The acceptable formats for a source report in reporting snapshots are:
* Summary format (B). This format groups rows of data by one or more criteria and can perform calculations such as sum, average, etc., on another column at each group level.
* Matrix format (D). Similar to the summary format but arranges data in a grid format, allowing summarization by both rows and columns.
Tabular (A) and joined (C) formats are not suitable for reporting snapshots. Tabular reports do not include grouped or summarized data, and joined reports involve combining multiple report types, which are not compatible with how reporting snapshots need to structure data.
Reference for more information on reporting snapshots and report formats:
* Reporting Snapshots: https://help.salesforce.com/articleView?id=reports_snapshots.htm&type=5
* Report Formats: https://help.salesforce.com/articleView?id=reports_understanding_formats.
htm&type=5