Salesforce Certified Platform Administrator II Advanced Practice Exam: Hard Questions 2025

A global manufacturer uses a custom object (Project__c) with Private OWD. Project records are owned by a PM, but multiple departments (Engineering, Finance, Legal) need access. Requirements: (1) Department access is determined by a Project Team child object (Project_Team__c) that relates Users to a Project with a Role__c picklist and Access_Level__c (Read/Read-Write). (2) Changes to team membership must grant/revoke access within minutes. (3) The security model must scale to 200k projects and frequent team changes. What is the best solution?

An org has a custom object (Inspection__c) with a lookup to Account. Inspectors should only see Inspections for Accounts assigned to them via a custom junction object (Account_Assignment__c) that relates User to Account. The org already uses Enterprise Territory Management (ETM) and Accounts are assigned to Territories. Inspectors are aligned to Territories, not individual Accounts, and alignment changes monthly. What is the most maintainable way to grant inspectors read access to Inspection__c records while minimizing custom code?

A company uses two Record Types on Opportunity: 'Direct' and 'Partner'. For Partner opportunities, Sales Ops wants Stage, Close Date, and Partner Account required, but only after the opportunity reaches Stage = 'Proposal'. Additionally, they want a different set of fields required when Stage = 'Negotiation' ONLY for Direct opportunities. The org is trying to reduce the number of page layouts. Which approach best meets the requirement with minimal layout sprawl and strong UX?

A custom object (Subscription__c) must relate to either an Account OR a Contact, but never both. The business also wants roll-up summaries on Account to count active subscriptions, and on Contact to count active subscriptions, without using code. Subscription__c currently uses two lookups: Account__c and Contact__c. What is the best design to meet all requirements?

A regulated customer needs to monitor whether any user exports report data containing PII fields. They already use Shield Event Monitoring. Requirements: (1) Identify the user, timestamp, report name/id, and whether export occurred (printable view, Excel, CSV). (2) Retain evidence for audits. (3) Provide a near-real-time alert to a security channel when exports happen from a specific folder. What is the best solution architecture?

Sales leadership reports that some opportunities are being credited to the wrong sales team after quarterly territory realignments. The org uses Enterprise Territory Management and has automation that stamps a custom field Current_Territory__c on Opportunity at creation time. They want historical accuracy for past quarters and accurate current reporting after realignment. Which approach best resolves the issue?

A Service org uses Case assignment rules and Omni-Channel. They added a flow that updates Case.Priority based on keywords found in Email-to-Case subject/body. After deployment, agents notice Cases sometimes route to the wrong queue because the routing configuration depends on Priority, and Priority is not always updated before routing occurs. How should an admin redesign to ensure correct routing deterministically?

A data team performs nightly upserts of 2 million Order__c records via an external integration. They see intermittent row lock errors and long processing times. Order__c has a master-detail to Account, multiple roll-up summaries on Account, and a record-triggered flow on Order__c that updates Account fields. What should an admin recommend to improve load performance and reduce locking while keeping data accurate?

Executives want a dashboard showing 'Net New ARR' by region with drill-down to the underlying Opportunity Products. Data model: Opportunity has multiple OpportunityLineItems; ARR is stored on each line item. Regions come from Enterprise Territory Management on the Account. Requirements: (1) Filter by Close Date range. (2) Show totals by region and product family. (3) Allow drill-down to the specific line items. What is the best reporting approach?

An org has multiple automations on Lead: a before-save flow normalizes phone/email, an after-save flow creates a Task for hot leads, and an assignment rule routes by Lead source. After adding a validation rule that blocks saving when Country is blank for certain sources, users report that sometimes Tasks are still created even though the Lead save fails. What is the most likely cause and best fix?