Explanation
Account and contact are two records that can be created when using the lead conversion process. The lead conversion process converts a lead into an account, a contact, and optionally, an opportunity. References:
https://help.salesforce.com/s/articleView?id=sf.convert_lead.htm&type=5

Explanation
Flow Builder is a tool that can be used to create an automated way to delete records based on field values.
Flow Builder can create flows that define the logic and actions for deleting records, such as finding records that match certain criteria and deleting them in bulk. Flows can be scheduled to run at regular intervals or triggered by other events or processes. References:
https://help.salesforce.com/s/articleView?id=sf.flow_builder.htm&type=5
https://help.salesforce.com/s/articleView?id=sf.flow_concepts_delete.htm&type=5

Explanation
An escalation rule is a tool that allows administrators to automatically escalate cases based on certain criteria and time triggers. For example, an escalation rule can change the owner of a case, send anemail notification, or update a field value when a case has been open for more than 7 days. An escalation rule consists of multiple rule entries that define the criteria and actions for each escalation scenario.
References:https://help.salesforce.com/s/articleView?id=sf.case_escalation.htm&type=5

Explanation
Email-to-Case allows you to create cases from incoming emails. You need to enable this feature and set up routing addresses and case creation settings.
References: https://help.salesforce.com/s/articleView?id=sf.customizesupport_email_to_case.htm&type=5

Explanation
Making a field universally required is a way to ensure that the field needs to be filled on every record; it prevents users from saving a record without entering a value in that field. It can be used to ensure that the billing system field needs to be filledon every invoice record by making it universally required in the field settings. Creating a process builder to set the field, defining an approval process for the child, or requiring the field on the record type are not ways to ensure that the field needsto be filled on every record; they either do not enforce data entry or only apply to certain scenarios or users.
References:https://help.salesforce.com/s/articleView?id=sf.customize_fields.htm&type=5