Platform Administrator II Advanced Practice Exam: Hard Questions 2025

A global sales org uses a record-triggered Flow on Opportunity to create multiple related Records (Tasks, renewal child Opportunities, and a custom object) whenever Stage changes to Closed Won. Users report intermittent errors that some related records are missing, especially when Opportunities are updated by integrations that also update many fields at once. The admin confirms there are multiple automations on Opportunity (Workflow field updates, a Process, and another Flow) and that some updates cause recursion. What is the best approach to make the automation reliable and prevent partial processing?

An admin must automate entitlement assignment: when a Case is created from Email-to-Case, if the Contact has an active Support Contract (custom object) and the Case Type is 'Technical', assign Entitlement A; otherwise assign Entitlement B. The Support Contract lookup is on Contact, not Case, and support contracts can change. The org receives 20,000 cases/day. The solution must be bulk-safe, minimize queries, and ensure correct entitlement even when Contact is added to the Case after creation. What should the admin implement?

A complex Lead routing process uses an autolaunched Flow invoked from multiple places (record-triggered flow, quick action, and an API integration). It writes debug logs to a custom object and sometimes fails with an unhandled fault when a referenced user is inactive. The business wants: (1) the Lead save must not fail, (2) routing must be attempted, (3) failures should be reported to a queue with enough detail to reprocess. What design best meets these requirements?

A company uses Account Teams and Opportunity Teams. They want: (1) Partner users to see only Opportunities where their partner account is on the Opportunity Team, (2) internal users to keep existing access through role hierarchy, and (3) prevent partner users from gaining access through Account ownership or sharing rules. The org currently has Private OWD for Opportunities and uses sharing rules for internal collaboration. What should the admin do?

An admin is troubleshooting why users in a custom permission set can still export report data that includes sensitive fields. The org uses field-level security to hide the fields from most users, but some users can still see them in reports and API extracts. The requirement is to restrict both UI and API access and ensure reports respect the restriction without creating separate report types per audience. What should the admin implement?

A regulated business needs to allow Customer Community users to create Cases and view only their own Cases, but internal agents must be able to see all Cases for an Account. Additionally, community users must not be able to infer whether other Cases exist (no search visibility, no list view access). Which configuration best meets the requirement?

A data migration loads 5 million historical Tasks related to Contacts and Opportunities. After the load, users complain that Activity-related dashboards and reports are slow, and some report results appear inconsistent when filtering by date ranges. The admin discovers that many Tasks have missing ActivityDate values and are instead populated only in CreatedDate, and that reports use relative date filters on ActivityDate. What is the best remediation strategy that preserves reporting accuracy and improves usability without rewriting every report?

Sales leadership wants a report showing each Account’s latest Opportunity Close Date and Amount for Closed Won deals, plus a count of open Opportunities, all in one view. They also need to filter by Account Owner and region. The admin tried a summary report with cross filters but cannot get the 'latest won deal details' at the Account level without duplicates. What is the best solution using declarative analytics features?

A large enterprise has 1,200 validation rules across multiple objects and frequent complaints that simple updates fail with confusing error messages. The admin must reduce support tickets by improving maintainability and troubleshooting, but cannot weaken data quality controls. Which approach is most effective?

After deploying changes, users report that creating Contacts sometimes fails with 'insufficient access rights on cross-reference id' when selecting an Account. The admin notices: (1) Accounts are Private OWD, (2) a new Contact trigger-like automation (Flow) creates a related custom object record tied to the Account, and (3) the error occurs only for users who can create Contacts but do not have access to the selected Account (they are entering new contacts from an external list). The business requires that users can create Contacts related to Accounts they don’t own, but should not gain read access to Account details beyond what’s necessary. What is the best fix?