A managed package is designed for distributable Salesforce solutions whose components can be maintained and upgraded by the package provider. Salesforce states that managed packages provide fully upgradeable application resources, and AgentExchange guidance distinguishes them from unmanaged packages by specifically noting that providers can automatically upgrade managed solutions. This makes a managed package appropriate when Universal Containers wants a complete preconfigured application while minimizing ongoing manual maintenance. An unmanaged package provides editable components but does not have the same provider-managed upgrade mechanism; receiving a newer unmanaged version generally requires replacement or reinstallation. A change set transfers metadata between related Salesforce orgs and is not an AgentExchange distribution package. A data kit is not the package type used to deliver an upgradeable Salesforce application.

The correct answer is D.
Universal Containers wants the Account Region value to appear on related Contact records and stay in sync whenever the Account value changes. A cross-object formula field on Contact is the best declarative solution because it dynamically references the parent Account field. Salesforce Trailhead explains that a cross-object formula can pull information from a parent object through a lookup relationship, such as showing Account information on Contact.
Because Account Region is a picklist, the formula must convert the picklist value to text using the TEXT() function. Trailhead gives the same pattern with Account Industry on Contact: TEXT(Account.Industry) .
B is incorrect because ISPICKVAL() checks whether a picklist equals a specific text value and returns true
/false; it does not display the picklist value.
A and C are incorrect because creating a copied field and trying to update it through a relationship is unnecessary when a formula field can stay synchronized automatically.

Resource is specifically intended for approvers that must be resolved dynamically at runtime. Salesforce ' s Flow Approval Process documentation defines Resource as an approver type that references a variable containing a user ' s username, a public group ' s API name, or a queue ' s API name. At runtime, the associated orchestration resolves the value and determines the appropriate assignee. Therefore, the app builder should store the dynamically determined username in a text variable and select that resource in the approval step. Selecting User would require choosing a predetermined user while designing the approval process, which does not satisfy the runtime requirement. Queue similarly identifies a configured queue rather than dynamically resolving an individual user. A Formula cannot directly substitute for the Approver Type configuration specified by Salesforce ' s Flow Approval Process model.

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.

Change sets can be exchanged only between deployment-connected organizations, such as a production org and its own sandboxes. UMS Logistics is a separate production organization and has no deployment relationship with the UMS source environment, so an outbound change set cannot be sent there. Salesforce documents unmanaged packages as a mechanism for packaging metadata components in a source org, uploading the package, obtaining an installation URL, and installing those components into another Salesforce organization. A managed package is intended primarily for distributed applications requiring namespace and provider-controlled versioning, such as commercial AppExchange solutions, and is unnecessary for this evaluation transfer. A sandbox likewise cannot be refreshed from an unrelated organization ' s Developer sandbox. Therefore, the appropriate deployment vehicle is an unmanaged package installed through its generated URL.