Praxis Academy
Home › Platform App Builder › Salesforce Fundamentals

Platform App Builder practice questions: Salesforce Fundamentals

Salesforce Fundamentals is 18% of the Salesforce Certified Platform App Builder exam. It covers security model, org setup and AppExchange. Try these 5 free questions, then open each answer to see why every option is right or wrong.

01

A life sciences company stores sales rep performance scorecards in a custom object. Each scorecard must be visible only to the rep, the rep's manager, and the executives above that manager. Reps must also be blocked from seeing the executive comment fields on their own scorecard. What should the Platform App Builder do to satisfy both requirements?

  1. Set the sharing model to Private and grant record access through the hierarchy; control field visibility with record types and field-level security.
  2. Set the sharing model to Private and grant record access through custom settings; control field visibility with page layouts and field-level security.
  3. Set the sharing model to Private and grant record access through the hierarchy; control field visibility with field-level security.
  4. Set the sharing model to Private and grant record access through custom settings; control field visibility with record types and page layouts.
Show answer

Answer: C

A. Set the sharing model to Private and grant record access through the hierarchy; control field visibility with record types and field-level security.Incorrect. Record types drive picklist values and layout assignment; they do not secure field data.
B. Set the sharing model to Private and grant record access through custom settings; control field visibility with page layouts and field-level security.Incorrect. Custom settings hold configuration data and cannot share records.
C. Set the sharing model to Private and grant record access through the hierarchy; control field visibility with field-level security. ✓Correct. Private OWD plus hierarchy access covers managers and executives, and field-level security keeps the executive comments away from reps.
D. Set the sharing model to Private and grant record access through custom settings; control field visibility with record types and page layouts.Incorrect. Custom settings do not share records, and page layouts only hide fields visually; the data stays reachable through reports or the API.

Why: Two restrictions apply at once: the record must follow the reporting chain upward, and one field on it must stay hidden from the rep. A Private org-wide default starts with no access beyond the owner, and 'Grant Access Using Hierarchies' automatically opens each record to the users above the owner in the role hierarchy. Field-level security is the feature that actually hides a field from a profile or permission set, regardless of layout, reports or API. Reference: Organization-Wide Sharing Defaults

02

A custom Account field holds a customer's financial information, and only the finance team can access it. For special cases, the business wants one customer service agent on the Customer Service profile to have Read-Only access to that field. What is the recommended way to give this agent access?

  1. Edit the custom field's field-level security in Setup to grant the agent Read-Only access.
  2. Create a permission set that grants Read-Only field-level security on the field and assign it to the agent.
  3. Create a new profile that grants Read-Only field-level security on the field and assign it to the agent.
  4. Change the agent's existing Customer Service profile to grant Read-Only field-level security on the field.
Show answer

Answer: B

A. Edit the custom field's field-level security in Setup to grant the agent Read-Only access.Incorrect. Setting field accessibility in Setup works per profile, so every user on that profile would be affected.
B. Create a permission set that grants Read-Only field-level security on the field and assign it to the agent. ✓Correct. A permission set with Read-Only field-level security, assigned only to this agent, grants access to that one user.
C. Create a new profile that grants Read-Only field-level security on the field and assign it to the agent.Incorrect. Building a whole new profile for one field adds needless overhead compared with a permission set.
D. Change the agent's existing Customer Service profile to grant Read-Only field-level security on the field.Incorrect. Editing the Customer Service profile would expose the field to every agent who uses it.

Why: Only one person needs the field, so the change must not reach the other agents on the same profile. A permission set can give Read-Only field-level security on that single field and be assigned to that one agent. The base profile stays unchanged, which follows the least-privilege practice of handling exceptions through permission sets. Reference: Field Permissions

03

A company tracks internal projects in a custom Projects object, organized by department, with a Private organization-wide default. Employees must see all project records of their own department, and when someone transfers to another department, they must lose access to the former department's projects. Which approach meets these requirements?

  1. Build a criteria-based sharing rule on the Project's department that shares records with Public Groups.
  2. Build a criteria-based sharing rule on the Project's department that shares records with Permission Sets.
  3. Build a criteria-based sharing rule on the Project's department that shares records with Profiles.
  4. Build a criteria-based sharing rule on the Project's department that shares records with Account Teams.
Show answer

Answer: A

A. Build a criteria-based sharing rule on the Project's department that shares records with Public Groups. ✓Correct. Sharing by department to a department Public Group means access changes simply by moving users between groups.
B. Build a criteria-based sharing rule on the Project's department that shares records with Permission Sets.Incorrect. Sharing rules cannot share records with permission sets.
C. Build a criteria-based sharing rule on the Project's department that shares records with Profiles.Incorrect. Sharing rules cannot share records with profiles.
D. Build a criteria-based sharing rule on the Project's department that shares records with Account Teams.Incorrect. Account teams belong to Accounts and do not apply to a custom Project object.

Why: Access must follow the department value on the record and adjust cleanly when people move between departments. A criteria-based sharing rule opens every Project with a given department value to a target, and sharing rules can target Public Groups, roles or territories. One Public Group per department represents current membership, so moving a user from one group to another immediately swaps their access. Reference: Create Criteria-Based Sharing Rules

04

Field sales reps work in Salesforce from their phones. They need a fast way to add new contacts and come back later to fill in the remaining details. Which mobile solution should the Platform App Builder recommend for creating these contacts?

  1. Use Path with predefined values.
  2. Create a global action that creates Contacts.
  3. Add a compact layout to Contacts.
  4. Reorder the mobile menu so Contacts appears first.
Show answer

Answer: B

A. Use Path with predefined values.Incorrect. Path guides users through stages of an existing record; it does not speed up record creation.
B. Create a global action that creates Contacts. ✓Correct. A global Create Contact action with only a few fields lets reps add contacts quickly from anywhere in the app.
C. Add a compact layout to Contacts.Incorrect. Compact layouts set the fields shown in the record highlights; they do not create records.
D. Reorder the mobile menu so Contacts appears first.Incorrect. Changing menu order does not make creating contacts any faster.

Why: The need is quick record capture on mobile, with the rest of the data added later. A global action can create a Contact from anywhere in the Salesforce mobile app and can be limited to a few key fields, so reps save in seconds and complete the record later. Reference: Create Global Quick Actions

05

A company needs to send a recurring email blast to about 7,000 contacts stored in Salesforce, but the native mass email feature limits how many emails can go out per day. What should the Platform App Builder do?

  1. Ask Salesforce to raise the daily email maximum.
  2. Research and evaluate AppExchange products for sending mass emails.
  3. Export the Contacts to a CSV file and send the emails from an email client.
  4. Build Apex code and a Lightning web component that send the emails daily.
Show answer

Answer: B

A. Ask Salesforce to raise the daily email maximum.Incorrect. The mass email daily limit is fixed and is not raised on request.
B. Research and evaluate AppExchange products for sending mass emails. ✓Correct. AppExchange email and marketing products are designed for recurring high-volume sending.
C. Export the Contacts to a CSV file and send the emails from an email client.Incorrect. Sending from an email client loses tracking in Salesforce and adds compliance risk.
D. Build Apex code and a Lightning web component that send the emails daily.Incorrect. Custom code is still bound by email limits and adds maintenance.

Why: The daily mass email limit is a fixed platform limit, so the solution has to come from a tool built for bulk sending. For regular high-volume email, the standard recommendation is a dedicated email or marketing product (for example Marketing Cloud, Account Engagement or another AppExchange app) that handles bulk sending, deliverability and compliance. This avoids custom code written to work around a limit. Reference: Salesforce Mass Email Limits

Find out if you're ready to pass

Take the free Platform App Builder diagnostic: 20 questions, no account needed. Then unlock all 241 questions, full practice exams and the study guide.

Start the free diagnosticSee plans

Other sections of this exam