Permission Sets are the appropriate mechanism for granting additional object and field access to users who perform a particular function without changing their base profiles. The app builder can create a permission set for hiring managers that grants the required access to JobApplication__c and Read access to the sensitive salary fields through field-level security. Salesforce specifically recommends permission sets and permission set groups rather than profiles for extending field permissions. Sharing Rules and organization-wide defaults govern record-level access; they do not make fields visible when field-level security hides them. Page Layouts control which fields are placed in the interface but cannot override field-level security. Because salary information represents restricted field-level data that only a designated functional group should see, Permission Sets provide the precise least-privilege solution.

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.

The correct answer is C. Research and evaluate data enrichment products on the AppExchange to automate data entry.
The sales manager wants reps to spend less time manually entering business-card information while maintaining data quality. Salesforce AppExchange is the correct place to evaluate packaged solutions that extend Salesforce functionality. Trailhead describes AppExchange as a place to find solutions for business needs, and AppExchange contains business-card scanning apps that can create or match Salesforce Leads, Contacts, and Accounts with reduced manual entry.
A does not automate data entry.
B is not the best fit because Flow cannot read business cards by itself.
D is incorrect because formula fields calculate values from existing data; they do not capture business-card information.

Actions and Related Records identifies an after-save record-triggered flow . Salesforce states that this optimization should be selected when automation must perform actions after the triggering record has been saved, including updating related records, creating records, and sending notifications or email. The flow can trigger when an Opportunity changes to Closed Won, reference the related Account and Account owner, perform any required related-record operation, and invoke the appropriate email action. Fast Field Updates is a before-save configuration optimized only for changing fields on the triggering record itself. A validation rule cannot invoke an autolaunched flow, and a Screen Flow requires user interaction. Because this automation requires post-save related-record processing and an email notification, D is the Salesforce- supported architecture.

The correct answer is C. Flow.
The requirement is to automatically delete rejected Quote records. Salesforce Flow is the correct declarative automation tool because Flow can identify records and delete them using the Delete Records element.
Why not the others:
Approval Process routes records for approval. Einstein Next Best Action recommends actions. Validation Rule prevents bad saves. None of those tools is designed to delete rejected child records automatically.