Free Salesforce Platform Foundations Practice Test Questions

Explanation:

To identify contacts that have had interactions with their company, the most reliable method is to check for activities related to that contact. In Salesforce, an activity can be a task, event, or email. The last related activity date field specifically tracks the most recent date a task, event, or call was logged against a contact. This field is the direct indicator of interaction.

A. Look at the contact's Last Modified Date: The Last Modified Date indicates the last time any field on the contact record was changed. This could be due to a data update, a workflow rule, or any other modification—not necessarily an interaction with the company.

B. Look at the active field: There is no standard field called "active" on a contact record that tracks interaction. While a custom "active" checkbox could be created, it would not be a standard or reliable way to track all interactions.

References:
Salesforce Help: "Contact Fields" The standard fields on the Contact object are documented here, including the purpose of fields like LastActivityDate (which is the API name for "last related activity date"). This field is specifically designed to show the last time a contact had an activity logged.

Explanation:

Option A (Correct) – The AppExchange is Salesforce's official marketplace for third-party and Salesforce-built apps. Here, associates (even non-admins) can:
Browse apps by category.
Read detailed descriptions, reviews, and ratings.
Check compatibility and features before recommending an app.

Option B (Incorrect) – Trailhead is for learning Salesforce concepts (e.g., modules, trails) but does not list or review specific apps for business needs.

Option C (Incorrect) – Global Search helps find records or setup items within an org but cannot provide app details like AppExchange.

Reference:
AppExchange Homepage

Explanation:

The question likely refers to the maximum number of rows that can be displayed in a Salesforce report or list view, as this is a common context in the Salesforce Platform Foundations exam. In Salesforce, the maximum number of records (rows) that can be displayed in a report or list view is 2,000 when viewed in the user interface. This limit ensures performance and usability in the Salesforce platform.

Option A: 2,000
Salesforce imposes a limit of 2,000 rows for records displayed in the user interface for reports and list views. This applies to the standard report results page or list view page in Lightning Experience or Classic. If a report or list view returns more than 2,000 records, users can export the full dataset (up to 50,000 rows for reports in some cases, depending on the export format) or use filters to narrow the displayed results.
Why this is correct: The 2,000-row limit is a well-documented Salesforce constraint for the UI display of reports and list views, making this the correct answer for the context of the question.

Option B: 5,000
The number 5,000 does not correspond to any standard Salesforce limit for displaying rows in reports or list views. It may be confused with other Salesforce limits, such as the maximum number of records returned by a SOQL query in certain contexts (e.g., Apex governor limits), but it is not relevant to the display of rows in the UI.
Why this is incorrect: There is no 5,000-row display limit in Salesforce for reports or list views.

Option C: 3,000
The number 3,000 is not a standard limit for displaying rows in Salesforce reports or list views. It does not align with any documented Salesforce UI display constraints.
Why this is incorrect: Similar to 5,000, the 3,000-row option does not match Salesforce’s display limits.

Contextual Notes:
The question is somewhat ambiguous without specifying whether it refers to reports, list views, or another context (e.g., SOQL query results, Visualforce pages, or Data Loader exports). However, in the Salesforce Platform Foundations exam, questions about “rows displayed” typically refer to the UI limits for reports or list views, where 2,000 is the standard maximum.
If the question pertains to a different context (e.g., exporting reports, SOQL queries, or custom development), the limits may vary:

Report Exports: Up to 50,000 rows can be exported in certain formats (e.g., CSV), but the UI display is still capped at 2,000.
List Views: Display up to 2,000 records in the UI, though more records can be retrieved with filters or API queries.
SOQL Queries: In Apex, the default query limit is 50,000 records, but this is not about “displayed” rows in the UI.

Since the question specifies “rows will display,” the 2,000-row limit for UI display is the most applicable.

Reference:
Salesforce Help Documentation: Report Performance and Limits – States that the Salesforce UI displays up to 2,000 records for reports.
Trailhead Module: Reports & Dashboards for Lightning Experience – Covers report creation and display limits, including the 2,000-row UI cap.
Salesforce Help Documentation: List View Limits – Confirms that list views display up to 2,000 records in the UI.

Explanation:

The goal is to allow a user to see only contacts from a specific city in the "New This Week" list view without affecting what other users see. The best approach is to clone the existing list view, give it a new name, and add a filter for the specific city, ensuring the cloned list view is only visible to the user. This preserves the original list view for other users and meets the user’s specific needs.

Option A: Change the permissions so they can only see records from the specific city.
Changing permissions, such as through profiles, permission sets, or sharing rules, would restrict the user’s access to records at the object or record level across the entire Salesforce org. For example, modifying sharing rules to limit access to contacts from a specific city would affect the user’s access to all contact records, not just the "New This Week" list view. Additionally, this could inadvertently restrict access to other records and would not preserve the original list view for other users.
Why this is incorrect: Changing permissions is a broad, system-wide change that goes beyond modifying a single list view and could disrupt the user’s access to other necessary records. It also doesn’t ensure the original list view remains unchanged for others.

Option B: Clone the list view with a new name, and filter by the specific city.
In Salesforce, a user can clone an existing list view (e.g., "New This Week") and create a new list view with a different name. The user can then add a filter to show only contacts from the specific city (e.g., City = "San Francisco"). When cloning, the user can set the visibility of the new list view to “Only I can see this list view” (private), ensuring that other users continue to see the original "New This Week" list view unchanged. This approach is declarative, user-specific, and does not require administrative privileges or impact other users.
Why this is correct: Cloning the list view allows the user to create a personalized view with the desired filter while preserving the original list view for everyone else, directly addressing the requirement.

Option C: Build a private report for contacts that is filtered by the specific city.
Creating a private report filtered by the specific city would allow the user to view contacts from that city, and setting the report’s folder visibility to private would ensure only the user can access it. However, reports are separate from list views and serve a different purpose (e.g., for analysis or exporting data). A report does not integrate with the "New This Week" list view or provide the same interactive, record-level navigation experience as a list view. Additionally, reports require users to navigate to the Reports tab, which is less seamless than modifying the list view directly.
Why this is incorrect: While a private report achieves the goal of showing filtered data to the user, it does not modify or interact with the "New This Week" list view, which is the focus of the question.

Additional Notes:
List View Visibility: When cloning a list view, Salesforce allows users to set visibility to “Only I can see this list view” (private), “All users can see this list view,” or “Share with specific groups.” Choosing the private option ensures the new list view is user-specific.
Permissions Consideration: The user must have the ability to create and save list views for the Contact object, which is typically allowed for users with Read access to Contacts unless restricted by their profile or permissions.

Reference:
Salesforce Help Documentation: Create and Customize List Views – Explains how to clone and customize list views, including setting filters and visibility.
Trailhead Module: Data Management – Covers list views and how to create user-specific views without impacting others.
Salesforce Help Documentation: Reports and Dashboards – Describes reports, which are distinct from list views and less relevant for this use case.
Trailhead Module: Salesforce Platform Basics – Discusses user interface customization, including list views.