Platform App Builder Advanced Practice Exam: Hard Questions 2025

A support org uses Leads with Web-to-Lead and manual creation by reps. A new requirement states: when a Lead is created and the Email matches an existing Contact, automatically relate the Lead to the existing Account, prevent duplicate conversion, and route the Lead to the Account owner. The solution must avoid code and minimize false matches. What is the best approach?

An app uses a custom object Project__c with millions of records. Users frequently filter by Status__c and Region__c and sort by LastModifiedDate in list views. Reports must support historical trending by status changes. Performance has degraded, and some reports time out. Which design improves both reporting and list view performance while supporting historical analysis, without using code?

A recruiting app has Candidate__c and Interview__c (master-detail to Candidate). A Candidate can be deleted only if no Interviews exist AND the Candidate.Status__c is not "Hired". The business also needs an error message that is different depending on which condition fails. The solution must work for bulk deletes from list views and API integrations. What is the best declarative approach?

A sales org uses Opportunities with multiple record types. A new requirement: when Stage changes to "Closed Won", create a Renewal__c record for each OpportunityLineItem and copy a subset of fields. This must happen only once per Opportunity, must be resilient to users editing the Opportunity again, and must handle bulk updates from integrations. No code is allowed. Which solution best meets these requirements?

A company wants a guided, multi-step "New Customer Onboarding" experience that collects data across Account, Contact, and a custom object Onboarding_Task__c. Users must be able to save progress mid-way, resume later, and different user profiles should see different steps. The solution must be declarative and support conditional branching. What should an app builder implement?

A custom object Expense__c has an approval process. When an Expense is submitted, it should be locked. However, Finance users must still be able to edit only two fields: GL_Code__c and Approved_Amount__c, while all other fields remain read-only. The solution must be declarative and should not require cloning record types. What should be used?

A service team uses a custom app with Case and a custom object Troubleshooting_Step__c related to Case. Agents need a console-style workspace where: (1) key Case fields are editable without page reload, (2) related Troubleshooting steps are visible and editable inline, and (3) different sets of fields appear based on Case record type and status. Which UI architecture best satisfies the requirements with minimal custom development?

Users complain that a custom object’s Lightning record page is slow. The page contains multiple related lists, several rich text components, and embedded report charts. The admin confirms that most users only need a subset of the components depending on the record’s Status__c. What is the best optimization strategy without removing functionality?

A managed package cannot be used. An ISV-like internal team must deploy an app from a developer sandbox to production. The app includes custom objects, Flows, Lightning record pages, custom labels, and permission sets. Post-deployment, users must have access immediately, but the team wants to minimize risk of overwriting production changes to unrelated metadata. What is the safest deployment approach?

A production deployment includes a new required field and a validation rule on Opportunity that enforces the field when Stage = "Proposal/Price Quote" or later. Immediately after deployment, an integration that upserts Opportunities begins failing for early-stage records, even though they are in "Qualification". Investigation shows the integration user is setting StageName and CloseDate, and sometimes StageName updates lag behind other field updates. What is the best fix that preserves data quality and avoids code?