Process Builder is an automation tool that allows you to create processes that perform actions based on criteria that you specify. You can use Process Builder to update fields on related records when a record is created or updated. To meet the requirement of updating the parent object Referral when the Referral Date field is updated on the custom object Referral Source, you need to create a process that triggers when a Referral Source record is updated, checks if the Referral Date field has changed, and updates the Referral Date field on the related Referral record. References: https://help.salesforce.com/s/articleView?id=sf.
process_overview.htm&type=5

Component visibility allows you to restrict the visibility of a related list based on a permission set.
References: https://help.salesforce.com/s/articleView?id=sf.dynamic_forms_component_visibility.
htm&type=5

Recurring tasks are tasks that repeat at regular intervals, such as daily, weekly, monthly, etc. They can be created by users who have the permission to create recurring tasks, which can be enabled by administrators in the user profile settings. Flow, workflow rule, and recurring activities are not valid options for creating recurring tasks in Salesforce. References: https://help.salesforce.com/s/articleView?id=sf.tasks_recurring.
htm&type=5

The User Licenses related list in Company Information shows the types of licenses that have been purchased for an org and how many are available or used. It also shows the expiration date of each license type if applicable. This information can help administrators plan for license purchases and manage user access.
Searching for license types in setup does not show how many licenses have been purchased or how many are available or used. User Management settings in setup does not show license information either, but rather settings related to user login, session, identity, etc. Usage-based entitlement related list in company information shows information about usage-based licenses such as API requests or sandboxes, but not user licenses. References: https://help.salesforce.com/s/articleView?id=sf.users_understanding_license_types.
htm&type=5

The contact hierarchy is a feature that allows users to view contacts related to an account in a hierarchical tree structure based on their role or position within the account. The contact hierarchy respects record-level access by user, meaning that users can see only those contacts that they have access to based on their profile permissions and sharing settings. The other options are incorrect because contact hierarchy is not limited to
3,000 contacts at one time (it can display up to 5,000 contacts), customizing hierarchy columns does not change the recently viewed contacts list view (it only affects how contacts are displayed in the hierarchy), and sharing settings are not ignored by contacts displayed in the contact hierarchy (they determine which contacts are visible to users). References: https://help.salesforce.com/s/articleView?id=sf.contacts_hierarchy.
htm&type=5