The correct answer is C. Compact layout.

Compact layouts control the key fields shown in the record highlights area at the top of a record, including in the Salesforce mobile app. Salesforce documentation states that compact layout fields populate the record highlights section at the top of record views in the Salesforce mobile app.

Why others are incorrect:

A. Mobile navigation controls navigation menu items, not fields on a record.

B. Record Detail component shows record fields but does not specifically place key fields at the top.

D. Object specific action is used for actions, not at-a-glance field display.

===========

The correct tool is Data Loader.

Cloud Kicks needs to insert over 1 million net new Account records. Salesforce Data Loader is the correct tool for large-volume imports because it supports bulk insert, update, delete, and export operations. Salesforce’s Data Loader documentation describes it as a client application for bulk data import and export, including inserting Salesforce records. Salesforce also distinguishes it from the Data Import Wizard, which is limited to smaller imports.

Why the other options are wrong:

Data Import Wizard is not suitable for over 1 million records because it is intended for much smaller imports. Schema Builder is for viewing and creating data model components, not loading a million records. Lightning Object Creator creates objects from spreadsheets, not mass-inserting large Account datasets into an existing model.

The Automation Lightning App ' s Monitor tab is Salesforce ' s centralized interface for examining failed and paused flow interviews. Salesforce states that the Monitor tab displays failed interviews, their error information, and details needed to determine why execution failed. From the failed interview details, an administrator can open the run in debug mode and inspect the execution information without requiring the user to reproduce the issue. This directly satisfies the requirement to troubleshoot intermittent production failures from historical flow runs. Option A focuses primarily on paused interviews and is not the current comprehensive monitoring experience. Apex Replay Debugger is intended for Apex debugging rather than declarative Flow execution. Running the flow manually as another user creates a new test execution rather than analyzing the specific production failures that already occurred.

The correct answers are C. The report is in the manager’s Private reports folder and D. The report does not have a chart.

The Report Chart component is used to display a chart from a report on a Lightning page. If the report has no chart, it cannot be used as a Report Chart component source. Salesforce documentation describes the Report Chart component as a way to include a chart from a report in a Lightning page.

The app builder also must have access to the report through report folder sharing. Reports saved in a user’s private report folder are not visible to other users unless moved/shared appropriately. Salesforce explains that reports are saved by default into private reports or dashboards folders unless a public/custom folder is selected.

A is incorrect because a report having no returned data does not stop the report from being selectable. B is incorrect because the app builder does not need to be the report creator; they need access to the report folder and the report must contain a chart.

===========

An input value from something outside the flow must be received through a Flow variable configured as Available for Input . Salesforce defines an input variable as a variable marked Available for Input that receives values from outside the flow. The app builder therefore creates a Variable resource, selects the required data type, and enables Available for Input under Availability Outside the Flow. The invoking Lightning component can then pass a value into that resource when the flow starts. $Record is a Flow global variable used in specific record contexts and does not replace a configurable external input parameter. Constants cannot receive changing runtime values because their values are fixed. Public component properties describe the LWC side but do not by themselves create a receiving Flow variable. Salesforce

================

The correct answers are C. External objects and D. Big objects.

External objects are suitable because they represent data stored outside Salesforce while still being accessible in Salesforce. Salesforce documentation explains that external objects behave similarly to custom objects, but the record data is stored outside the Salesforce org. External objects can also participate in lookup-style relationships, including external and indirect lookup relationships, and Salesforce Connect supports reports that include external objects.

Big objects are also suitable for archiving very large volumes of historical data on the Salesforce platform. Salesforce describes big objects as a way to store and manage massive amounts of data, including archived data from other objects. Big objects support querying through SOQL/API patterns, and Salesforce documentation also covers viewing big object data in reports and dashboards, commonly by using a working dataset for reportable subsets.

A is incorrect because “related objects” does not reduce Salesforce data storage.

B is incorrect because moving data into custom objects still consumes Salesforce data storage, so it does not solve the storage-limit issue.

===========

The correct answer is A. Allow Salesforce to import Contacts from mobile device Contact lists.

Salesforce supports importing contacts from a mobile device contact list into Salesforce from the Salesforce mobile app using Import from Device. Salesforce also notes that users need the permission Allow Salesforce to import Contacts from mobile device Contact lists to use this feature.

Why others are incorrect:

B only notifies users; it does not move phone contacts into Salesforce.

C helps users create/edit records offline in Salesforce, but it does not import contacts already entered in the phone’s contact list.

D is for account-contact relationship modeling, not mobile contact capture.

===========

The correct answer is C. Add the standard Chatter feed component.

To add Chatter feed functionality to a custom object Lightning record page, the app builder should use the standard Chatter component in Lightning App Builder. Salesforce documentation states that the Feed component was renamed Chatter in Lightning App Builder and is used to place the publisher and feed combination on a record page.

A is incorrect because no custom Chatter feed component is required. B is incorrect because related lists do not add the Chatter feed. D is incorrect because the standard Chatter component is already available; an AppExchange component is unnecessary.

===========

The correct answers are A. Tabs and B. Related record.

Tabs help create a more condensed Lightning record page by grouping information into separate tabbed sections instead of showing everything in one long page. Salesforce Lightning App Builder allows app builders to add, remove, reorder, and customize components on Lightning record pages.

Related Record is required because service agents want to modify the associated Contact and Account directly from the Case Lightning record page. Salesforce Help states that the Related Record component uses quick action metadata and requires an associated quick action to update records.

Why others are incorrect:

Path is used to guide users through stages or status values, not to edit related Account or Contact records.

Rich Text displays formatted guidance or static text; it does not provide editable related-record functionality.

The correct answer is A. A custom detail page link on the Contract object.

Users need access to the pricing guidelines document while viewing a Contract record. A custom detail page link can be added to an object’s page layout and used from the record detail page to open an internal document, external URL, intranet page, or other resource. Salesforce documentation confirms that custom buttons and links can be added to object and record detail pages to give users quick access to needed resources.

Since the document is needed while viewing the Contract, the link belongs on the Contract object, not the Account object.

===========