The correct answer is B. Geolocation.
Salesforce geolocation fields are used to identify locations using latitude and longitude and can support distance calculations.
Because Universal Containers delivers containers to remote construction sites and customers provide crossroads or location markers, the app builder should use a Geolocation field to capture location-based information rather than a number, reference, or external lookup field.
Why others are incorrect:
A). Number stores numeric values only.
C). Reference is not the correct field type for capturing physical location.
D). External Lookup is used to relate Salesforce records to external object records, not to store site location details.

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 correct answer is A. A hyperlink to the parent Account of the parent Opportunity.
A formula field can use cross-object references to parent records, and Salesforce states that cross-object formulas can reference fields from objects up to 10 relationships away. Since Opportunity Product relates to Opportunity, and Opportunity relates to Account, a formula on Opportunity Product can reference the parent Opportunity's Account.
Salesforce also supports the HYPERLINK() formula function, which creates a clickable link from specified link text to a specified URL. So a formula field can be configured to create a hyperlink to the Account record related to the parent Opportunity.
B is incorrect because formula field data types do not include Rich Text Area as a formula return type.
C is incorrect because Salesforce restricts formulas from using long text area, encrypted, or Description fields.
D is not the best verified answer because large cross-object concatenations can run into formula relationship, size, or complexity limits, while the clearly supported Platform App Builder use case here is the cross-object HYPERLINK formula.

Flow Trigger Explorer is specifically designed to manage the execution sequence of record-triggered flows for the same object and trigger category. Salesforce documents that changing a flow ' s order in Flow Trigger Explorer changes its Trigger Order value, and that this value determines the sequence in which applicable flows execute. Therefore, the discount calculation flow should receive the earlier/lower trigger order and the notification flow the later order. This preserves separate flows while guaranteeing deterministic sequencing.
An asynchronous path does not provide the same explicit ordering contract. A zero-minute scheduled path unnecessarily changes transaction timing. Combining both flows violates the stated ownership requirement and is not necessary because Salesforce provides native trigger-order controls. The correct Platform App Builder solution is therefore Flow Trigger Explorer.

The correct answer is C. To make a Contact's Twitter profile available in the Salesforce mobile app, the app builder should add the Twitter component to the mobile Lightning record page. Salesforce guidance states that to make Twitter accessible on Account or Contact record pages and in the Salesforce mobile app, add the Twitter component in Lightning App Builder.
Why others are incorrect:
A is wrong because mobile navigation is for navigation items, not displaying a Contact Twitter profile.
B is unnecessary because Salesforce provides the component declaratively.
D may show a link, but it does not provide the standard Twitter profile component experience.