Platform-App-Builder Practice Test Questions

Explanation:

Why these are correct
A. Send an email alert. Process Builder can invoke Email Alerts as an action.
B. Update a related record. You can use Update Records to update one or more records related to the record that started the process.
E. Create a child record. Process Builder can Create a Record (e.g., a child record) with field values you set or pull from related records.

Why the others are wrong
C. Send an outbound message. Outbound Messages are supported by Workflow, Approval Processes, and Flow—not Process Builder.
D. Delete a related record. Process Builder has no Delete Records action (deletes are supported in Flow, not PB).

Explanation:

Properly installing managed packages helps prevent conflicts with customizations made by customers and partners by ensuring that the components within the package are isolated from other custom code or configurations in the org. The key functionality used to achieve this is the Namespace. A namespace is a unique identifier assigned to a managed package by its developer, which prefixes all components (e.g., custom objects, fields, classes) in the package. This prevents naming collisions with existing customizations or other packages, as the namespace ensures that all package elements are distinctly scoped (e.g., namespace__Object__c vs. a custom Object__c).

Why not the other options?
A. Description:
The description field in a package is a text area used to provide information about the package’s purpose or contents. It does not provide any functionality to prevent conflicts or manage package installation, making it irrelevant to this context.
B. Allow sharing:
"Allow sharing" is not a standard package setup option in Salesforce. Sharing settings relate to record-level access (e.g., organization-wide defaults or sharing rules) and are not a feature of package installation or conflict prevention.
C. Help setting:
"Help setting" is not a recognized term in Salesforce package management. It might be a misinterpretation, but no such functionality exists to configure packages or prevent conflicts during installation.

Additional Notes:
When installing a managed package, the namespace is automatically applied, and users cannot modify the package’s components directly, further reducing the risk of customization conflicts. The current date and time (04:01 PM PKT, Tuesday, September 16, 2025) is noted, but it does not impact the answer, which is based on static Salesforce functionality.

References:
Salesforce Help: Managed Packages (Explains namespaces and their role in conflict prevention).
Salesforce Trailhead: Package Basics (Covers namespace usage in managed packages).
Salesforce Developer Documentation: Namespace Prefixes (Details how namespaces isolate components).

Explanation:

Optimizing the mobile experience in the Salesforce mobile app requires focusing on efficiency, performance, and user-friendly design. Here’s why these options are correct:
Why A is Correct: Global Actions are accessible from the mobile navigation menu and provide quick access to common tasks (e.g., logging a call, creating a record). This reduces the number of clicks needed to perform vital functions, streamlining the mobile user experience.
Why C is Correct: Minimizing formula fields and lookup fields on page layouts improves mobile performance. Formula fields require server-side calculation, and lookup fields may trigger additional queries, both of which can slow down page load times on mobile devices with potentially slower network connections.
Why E is Correct: The compact layout is a mobile-specific feature that controls which fields appear in key areas of the mobile app, such as search results and the record header. Placing the most important fields (e.g., Name, Status, Phone) here ensures users can quickly access critical information without scrolling or navigating deeply into the record.

Why B is Incorrect: Default field values are actually beneficial for mobile users because they reduce data entry effort. Pre-populating fields (e.g., setting a default status) saves time and minimizes typing on mobile devices, which is a best practice for mobile optimization.
Why D is Incorrect: Salesforce does not allow creating layouts specific to phone operating systems (e.g., iOS vs. Android). Instead, you create Lightning Page layouts that are responsive and automatically adapt to different mobile devices. Customizing layouts per OS is unnecessary and not supported.

Reference:
Salesforce Help Articles:
"Optimize Your Org for the Mobile App" (best practices for performance and usability).
"Compact Layouts" (for highlighting key fields).
"Actions Overview" (for using global and object-specific actions to streamline tasks).

Explanation:

Salesforce has daily email limits for mass email functionality, especially in Enterprise and Professional Editions. These limits are designed to prevent spam and ensure system performance. For Northern Trail Outfitters to regularly email 7,000 contacts, they need a scalable, compliant solution.
The best approach is to use a third-party email marketing app from the AppExchange, such as:
Marketing Cloud Account Engagement (Pardot)
Mailchimp for Salesforce
Campaign Monitor
SendGrid
These tools offer:
High-volume email capabilities
Compliance with anti-spam laws
Tracking and analytics
Seamless integration with Salesforce

❌ Why the other options don’t work:
A. Request Salesforce increase the number of maximum daily emails
❌ Rarely granted and not scalable for regular mass emails
B. Develop Apex code and custom component
❌ Violates email limits and best practices; not recommended for bulk email
D. Export to CSV and use external email client
❌ Manual, error-prone, and lacks integration, tracking, and compliance features

🔗 Reference:
Mass Email Limits – Salesforce Help
AppExchange Email Apps

Explanation:

A. Global actions can be accessed anywhere actions are pages, feed and Chatter groups.
The key benefit of a global action is its universal accessibility. Unlike an object-specific action that only appears on a particular object's record page, a global action can be placed in various locations. On mobile, this includes the action bar that appears on many pages, allowing users to send an email without navigating to a specific Lead, Contact, or Account record.

Incorrect answers

B. Salesforce Lightning Component Library houses existing global actions prebuilt for use.
The Lightning Component Library is for prebuilt components, not prebuilt actions. While there are standard actions, the library is not the repository for managing them.

C. The global action's layout automatically clones the default page layout.
Global actions have their own dedicated page layouts that are configured independently of an object's page layout. This allows the app builder to create a simplified, mobile-friendly layout with only the necessary fields, which is often a different configuration than the default page layout.

D. Global actions are record-specific and are available when searching that particular object.
This describes an object-specific action, not a global one. Global actions are not tied to a single record or object. They are available across multiple objects or even when not on a record page at all, such as on the Home page.

Explanation:

The requirements are to automate a welcome email with a customized survey, do it quickly, and maintain full customization capabilities. Here's why Flow is the best choice:
Why B is Correct:
Salesforce Flow is a powerful declarative automation tool that allows an App Builder to build complex processes quickly without code. It can:
Trigger automatically when a new client record is created (e.g., from a record-triggered flow).
Fully customize the email content and include a link to the survey.
Create the survey itself using a Screen Flow, which can be fully customized with questions, conditional logic, and data capture. The flow can then send the survey via email or present it directly in the Salesforce UI.
Meet the tight deadline because it avoids the time-consuming process of writing, testing, and deploying code.

Why A is Incorrect:
While working with a developer to create custom Apex code and a Lightning Web Component would provide full customization, it would not meet the requirement of having "very little time to build the solution from scratch." Custom development is inherently slower than declarative tools like Flow for this type of task.
Why C is Incorrect:
A managed package from AppExchange often restricts customization. You typically cannot modify its code or core functionality. While it might save time, it would likely prevent the "fully customize" requirement, as you are limited to the configuration options the package provides.
Why D is Incorrect:
An unmanaged package is essentially a bundle of metadata that is installed into your org and becomes editable. While it allows for programmatic development and full customization, it is not a "quick" solution. The App Builder would still need to understand, modify, and potentially debug the package's components to meet the exact requirements, which could be time-consuming.

Reference:
Salesforce Help Article: "Automate Complex Business Processes with Flow." Flow is designed specifically for App Builders to create customized, automated processes quickly and declaratively, making it the ideal tool for this scenario.

Explanation:

Why: Change sets move metadata only (reports, fields, objects, etc.), not the underlying record data. If your UAT org doesn’t have sample Opportunity (or related) data—or if sharing/visibility differs—the report will return no rows.

Why the others are wrong:
A. Reports don’t require SFDX to deploy.
B. Reports don’t need to be manually re-created; they can be deployed via change sets.
C. Change sets can’t include data at all.

Reference:
Salesforce docs on Change Sets note they deploy customizations (metadata), not data (records).

Explanation:

The sales team at Universal Containers receives approximately 800 leads daily from the marketing team, with the potential for duplicates since the list is sent in full each morning without prior deduplication. The Data Import Wizard is the most suitable tool for importing these leads into Salesforce while preventing duplicates:

B. Data Import Wizard:
The Data Import Wizard is a browser-based, declarative tool designed for importing up to 50,000 records (well above the 800 daily limit) and includes a deduplication feature. It can match leads based on standard fields like Email, Lead Owner, or Company Name (configurable during import) and prevent duplicate entries by either skipping existing records or updating them. This tool is user-friendly, requires no additional setup beyond enabling it in Setup, and aligns with the app builder’s focus on low-code solutions.

Why not the other options?
A. Dataloaderio:
"Dataloaderio" appears to be a typo or misreference (possibly intended as "Data Loader IO," a third-party tool). Data Loader IO is a cloud-based data loader with deduplication capabilities, but it is not a native Salesforce tool and requires a subscription, additional configuration, and potentially more technical expertise, making it less ideal for this scenario.
C. Data Loader:
Data Loader is a desktop tool for bulk imports (up to 5 million records) and supports deduplication via upsert operations with external IDs or matching fields. However, it requires more technical setup (e.g., CSV configuration, command-line or UI use) and is better suited for larger, more complex imports or automated processes, not the daily 800-lead task manageable by the Wizard.
D. Manual entry:
Manually entering 800 leads daily is impractical due to time constraints and human error risk. It lacks automation or deduplication features, making it unsuitable for this volume and requirement.

Implementation Notes:
Enable the Data Import Wizard via Setup > Data Import Wizard.
Upload the lead CSV file, select "Leads" as the object, and choose the deduplication option (e.g., match by Email).
Review and adjust mappings, then run the import to skip or update duplicates.
Schedule a daily process if needed, though manual upload per morning suffices for this volume.

References:
Salesforce Help: Data Import Wizard (Details deduplication and usage for leads).
Salesforce Trailhead: Import Data (Covers Wizard vs. Loader for small imports).
Salesforce Help: Prevent Duplicates During Import.

Explanation:

The Lightning Record Page is designed to display all the details of a single record. The Record Detail component is the primary component responsible for rendering the fields from the page layout.

Why C is Correct: The Record Detail component is built to show all the fields that are configured in the record's page layout. It provides a comprehensive view of the record's data, organized according to the layout sections (e.g., Details, Related Lists). This is the standard component for viewing the complete set of fields on a record page.

Why A is Incorrect: The Highlights Panel is designed to show a subset of key fields at the top of the record page for quick reference. It does not display all fields from the page layout; it only shows the fields that are specifically assigned to it.

Why B is Incorrect: The Recommendations component is part of Salesforce's Einstein AI features. It provides intelligent suggestions (e.g., next best actions) based on the record data, but it does not display the record's fields.

Why D is Incorrect: The Path component is a guidance tool that shows the stage of a record in a process (e.g., a sales process). It helps users understand what step comes next but does not display the record's field data.

Reference:
Salesforce Help Article: "Add Components to Lightning Pages." The Record Detail component is explicitly described as the component that "displays fields from the page layout associated with the record."

Explanation:

B. Update the account search layouts search results columns displayed. When multiple accounts have similar names, adding additional columns to the search results page can help users differentiate between them. For example, including the Billing City, Phone Number, or Account Number in the search results provides more context and helps the user quickly identify the correct record.
C. Update the account search layouts search filter fields. By adding additional fields to the search filter layout, users can narrow their search results using criteria other than just the company name. This is crucial when the company names are similar. For instance, an app builder could add filters for "Billing City" or "Industry" to help users find the correct account more efficiently.

Incorrect answers
A. Update the account search layout’s view filter settings. This is not a standard configuration option for search layouts. View filters are typically associated with list views, not the search results themselves.
D. Update the account search layouts accounts tab columns displayed. While this does affect the "Recently Viewed" list on the Accounts tab, it does not directly impact the search results page shown after a user performs a search. This is a subtle but important distinction.