The correct answers are C. Custom object, D. Apex class, and E. Custom field.
Change sets are used to move metadata between related Salesforce environments, such as sandbox and production. Salesforce documentation confirms that change sets can migrate components such as custom objects, custom fields, and Apex classes. Salesforce also notes that custom fields can be migrated individually in a change set.
A). Web-to-lead is not one of the common metadata components normally selected as an item in this exam context. B. Standard fields are standard Salesforce metadata and are not moved like custom fields in change sets.

The correct answer is A. Import Wizard.
Cloud Kicks needs to insert 25,000 records and use deduplication for a custom object. Salesforce Trailhead states that the Data Import Wizard can import data into custom objects and supports up to 50,000 records at a time, so 25,000 records fits within the Import Wizard limit.
Salesforce Help also states that the Data Import Wizard prevents duplicate custom object records by matching records against fields such as the custom object name or Salesforce ID.
B). Data Loader is not the best answer because Data Loader is better for larger or automated loads, but this question specifically requires deduplication and only 25,000 records. C. Lightning Object Creator creates objects from spreadsheets; it is not the correct deduplication import tool. D. Schema Builder is for creating and viewing data models, not importing records.

The correct answer is C. Custom object with Master-detail field to Opportunity.
AW Computing needs many help requests related to one Opportunity, so the help request should be a custom child object under Opportunity. Because the Opportunity page must show the most recent request date, the app builder needs a Roll-Up Summary field on Opportunity using MAX on the request date field.
Salesforce roll-up summary fields work on the master side of a master-detail relationship, and MAX can be used for date/date-time fields.
A is backward because the master-detail field belongs on the child object, not Opportunity.
B and D use lookup relationships, which do not support standard roll-up summary fields.

Current Salesforce documentation makes C the correct answer. Salesforce Help states that to enforce validation rules during Lead conversion, the Require Validation for Converted Leads setting must be enabled under Lead Settings. If it is disabled, validation automation that would otherwise protect the resulting Account, Contact, or Opportunity can be bypassed during conversion. Therefore, missing information on Accounts created through Lead conversion indicates that this Lead setting has not been enabled. The PDF answer key marks D, but that answer does not accurately identify the configuration responsible for the behavior. Lead validation rules do not universally "fail" during conversion; the behavior is controlled by the conversion-validation setting. Salesforce ' s April 2026 documentation explicitly instructs administrators to enable Require Validation for Converted Leads to enforce these rules.

The correct answer is A. Add the field to the custom report type field layout.
The report already exists: Position with or without Applicants Report. The issue is not that reporting is disabled for the object; the issue is that the new Applicant field is not available as a column in that custom report type. For custom report types, fields available to report builders are controlled by the custom report type field layout. Salesforce's documentation for adding fields to a custom report type directs admins to open the report type and use Edit Layout to add the missing fields.
B is incorrect because field-level security can hide a field from a user, but the troubleshooting step for a field missing from a custom report type column list is to add it to the custom report type layout.
C is incorrect because the report type already exists and is being used.
D is incorrect because the field data type was already assigned when the field was created.