The correct place to verify whether a change set can be deployed is Inbound Change Sets in the target org, normally Production.
Salesforce guidance says that after uploading a change set from the source sandbox, the app builder goes to Setup → Inbound Change Sets, opens the change set awaiting deployment, and clicks Validate. Validation checks whether the deployment succeeds or fails before committing the changes.
A . Deployment Settings is mainly used to authorize deployment connections and allow inbound changes from another org. C. Deployment Status is used to monitor deployment progress/results, not to initiate validation of an inbound change set.

To display a weather map component only when a house is scheduled for a listing, the app builder should use Component Visibility in the Lightning App Builder.
Component visibility allows setting filters so components appear conditionally based on field values or other conditions.
Salesforce documentation states that conditional visibility rules control when a component is displayed dynamically on a Lightning page. (Salesforce Help) B . Field-level security controls access to fields, not component visibility.
C . Formula field only calculates values but does not control component display directly.
D . Sharing rules control record access, not UI components.

The correct solution is to configure validation rules with help text/error messaging.
Validation rules are the right tool because they evaluate record data before save and stop the save when the record does not meet the defined conditions. They can enforce that a Case status is not changed back to an earlier value by using formula logic such as PRIORVALUE() and picklist checks. They can also require certain fields only when specific Case criteria are met by checking whether those fields are blank under those conditions.
Why the other options are wrong:
Dependent picklists control valid picklist values, but they do not enforce status progression or conditional required fields across all save paths. Approval processes are not the best fit for real-time save validation. Page layout required fields are UI-level requirements and are not flexible enough for criteria-based enforcement.

The correct answer is B. Verify there is an Apex test that provides test coverage for the flow.
For deploying an active autolaunched flow to production, Salesforce requires flow test coverage. Salesforce documentation states that before deploying a process or autolaunched flow as active, the org must meet flow test coverage requirements, and Apex tests must cover active processes and active autolaunched flows.
A is not the main deployment consideration for making the flow active in production.
C is incorrect because Salesforce does not require 100% flow test coverage.
D is incorrect for this scenario because the requirement is to deploy it already active, not manually activate it after deployment.

The correct answers are C. Currency, D. Date, and E. Percent.
Salesforce roll-up summary fields support different field types depending on the summary operation. For SUM, Salesforce supports number, currency, and percent fields. For MIN and MAX, Salesforce supports number, currency, percent, date, and date/time fields. Therefore, from the options given, Currency, Date, and Percent are valid field types for roll-up summary calculations.
Checkbox is not a supported field type for roll-up summary aggregation. Time is not the intended supported option in this exam context.