When working with custom fields in Looker, which of the following is correct?

Custom fields in Looker are versatile tools that allow users to create temporary fields based on existing data for analysis purposes. The ability to share custom fields with other users enhances collaboration within your organization by allowing different team members to utilize the same customized metrics or dimensions. This sharing capability facilitates a consistent analytical process and ensures that insights derived from data remain aligned across different users.

The alternative options do not accurately capture the functionalities of custom fields. For instance, while it is true that custom fields are not saved as permanent changes to the data model (which aligns with the notion of not being saved), it does not signify that they are unable to be stored for later use within a specific session or report. The requirement for custom fields to be solely numeric is also incorrect since they can be created using various data types, including strings and dates. Finally, the idea that custom fields only operate within individual Looks misrepresents their functionality, as they can also be used in dashboards and other types of analyses, extending well beyond just single Looks. Thus, the ability to share custom fields stands out as a significant and beneficial feature in Looker.