Data is unable to be deployed with change sets. Change sets are used to deploy metadata components such as custom objects, fields, workflows, reports, etc. from one Salesforce org to another. However, change sets do not include any data or records from the source org. Users will need to use other tools such as Data Loader or Data Import Wizard to migrate data between orgs. [Source]

The requirement specifies that when the Close Date is delayed by more than 60 days, the record must go through review by both the manager and VP of Sales - this implies an approval process or Flow-initiated approval is needed, not just a restriction.
Why B (Flow) is correct:A Record-Triggered Flow can be configured to detect when the Opportunity Close Date changes by more than 60 days and then automatically submit the record for approval.Exact Extract:"You can use a flow to automatically submit records for approval when they meet certain criteria." - Salesforce Help | Flow and Approval Processes Why C (Approval Process) is correct:The approval process enforces the review by both the manager and VP, ensuring a controlled approval sequence.Exact Extract:"An approval process automates how records are approved in Salesforce. Each approval process specifies the steps necessary for a record to be approved and who must approve it." - Salesforce Help | Approval ProcessesYou can configure multiple approvers and specify that both must approve ("Unanimous Approval").
Why not A (Validation Rule):A validation rule would only block saving but would not trigger a review or approval.
Why not D (Formula Field):Formula fields are read-only and cannot trigger workflow or approval actions directly.
Reference (Salesforce Platform App Builder documentation / Study Guide topics):
Salesforce Help | Flow Builder and Approval Processes
Salesforce Help | Approval Processes
Salesforce Platform App Builder Exam Guide | Business Logic and Process Automation

Changing custom field types may result in data loss if the new field type is incompatible with the old one. For example, changing a text field to a number field may cause text values to be deleted. Field history tracking records value changes of 255 characters or less. If a rich text field value exceeds this limit, only the first 255 characters are tracked.

When a master-detail relationship is created between two objects, Salesforce automatically creates a standard report type that allows users to report on the parent and child together.
Why A (Galaxy__c with Star__c) is correct:Exact Extract:"When you create a master-detail relationship, Salesforce automatically creates a primary report type that includes records from both the master and its detail." - Salesforce Help | Standard Report TypesTherefore, a "Galaxy__c with Star__c" report type is automatically generated, allowing users to create reports showing all child records (Star__c) related to each parent (Galaxy__c).
Why A (Galaxy__c with Star__c) is correct:Exact Extract:"When you create a master-detail relationship, Salesforce automatically creates a primary report type that includes records from both the master and its detail." - Salesforce Help | Standard Report TypesTherefore, a "Galaxy__c with Star__c" report type is automatically generated, allowing users to create reports showing all child records (Star__c) related to each parent (Galaxy__c).
Why not B:The parent-to-child relationship drives the report type. A "Star__c with Galaxy__c" type is not automatically created.
Why not C or D:Custom report types are only needed if you want to include additional related objects or modify relationships; Salesforce automatically provides one for master-detail pairs.
Reference:
Salesforce Help | Standard Report Types
Salesforce Platform App Builder Exam Guide | Data Modeling and Management

The app builder should recommend building a global action to create Contacts. A global action allows users to create records quickly from any page in Salesforce on their mobile devices. The app builder can also specify predefined values for some fields in the global action, such as Account Name or Phone Number, to make data entry easier for users. Option A is incorrect because customizing the mobile menu to move Contacts to the top does not help users create new contacts quickly or follow up later. Option C is incorrect because adding a compact layout to Contacts does not help users create new contacts quickly or follow up later, but rather shows them more fields on record detail pages or list views. Option D is incorrect because using Path and setting pre-defined values does not help users create new contacts quickly or follow up later, but rather guides them through different stages of a record.