In the Salesforce mobile app, navigation depends on the Lightning app the user is using. Salesforce documentation states that mobile navigation items depend on the active Lightning app, and when a Lightning app is enabled for desktop and phone, the desktop navigation tabs sync to the mobile navigation menu. Salesforce also notes that different menu configurations cannot simply be set directly for different user types. Therefore, the correct design is to create separate Sales and Marketing Lightning apps with different navigation items, then assign access to the appropriate profiles.

The correct answer is C. Use Dynamic Forms to display the Years of Previous Experience field if Previous Experience is checked.
This is a conditional field-visibility requirement. Salesforce Dynamic Forms lets app builders manage fields and sections directly in Lightning App Builder and use visibility rules to show users only the fields they need, when they need them.
So the app builder can place the Years of Previous Experience field on the Dynamic Forms-enabled record page and set visibility so it displays only when Previous Experience = True.
A is unnecessary and overcomplicated.
B is incorrect because field dependencies apply to picklists, not checkbox-to-number visibility.
D is incorrect because Visualforce is unnecessary when Dynamic Forms provides a declarative solution.

The correct answer is D. Approval process with a record-triggered flow.
Salesforce does not provide a simple "approval before delete" button behavior by default. The practical declarative pattern is to use an Approval Process for manager permission and a record-triggered Flow to automate the submit/delete logic. Flow includes a Submit for Approval action for Classic Approval Processes and also supports deleting records through the Delete Records element.
Why not the others:
A two-step approval process only handles approval routing; it does not complete the deletion automation by itself. A scheduled path or schedule-triggered flow is not appropriate because this is based on a user's delete request, not a time-based batch process.

The correct answer is B. The Allow reparenting checkbox, Child records can be reparented to other parent records after they are created, is unchecked.
A service plan must be associated with one Contact, and users cannot change the Contact after the service plan is created. Since field access and validation rules are not the issue, the likely cause is a master-detail relationship where Allow reparenting is not enabled.
Salesforce documentation states that in master-detail relationships on custom objects, administrators can allow child records to be reparented by selecting Allow reparenting. If that option is not selected, users cannot change the parent record after the child record is created.
A and C relate to master-detail sharing settings, not changing the parent record. D is the opposite of the problem; if Allow reparenting were checked, users could change the parent Contact.

The correct answer is C.
The Lightning record page already supports both mobile and desktop, but the downloaded custom component is not visible on mobile. That points to the component itself, not the page activation. Lightning components must be configured to support the required form factors. Salesforce developer documentation explains that components can be configured for desktop form factor Large, phone form factor Small, or both.
So, if the AppExchange component was built only for desktop pages or only supports the large form factor, users cannot view it in the Salesforce mobile app.
A and D are incorrect because the issue is not page activation if the page already supports mobile and desktop. B is incorrect because the scenario states the record page supports both mobile app and desktop.