Praxis Academy

Salesforce Certified Platform Administrator II practice exam

The real exam has 60 questions, lasts 105 minutes and needs 65% to pass. Start with a free 20-question diagnostic, no account needed.

Start the free diagnostic

Exam sections and weights

Sample questions

In an org where the Opportunity OWD is Private, sales reps say they can view opportunities they do not own, even though no explicit sharing rule exists. The admin confirms 'Grant Access Using Hierarchies' is turned on. What best accounts for this access?

  1. With 'Grant Access Using Hierarchies' enabled, users in roles above a record's owner automatically receive at least read access to the records owned by users beneath them. (Answer)
    Correct. The role hierarchy passes record visibility upward, so users in higher roles see records owned by subordinates despite the Private OWD.
  2. During org setup, a manual sharing rule was generated automatically that gives every internal user read access.
    Incorrect. Setting up an org never creates manual sharing automatically, so this is not where the access comes from.
  3. When no sharing rule exists, Opportunity records fall back to Public Read/Write, which overrides the Private OWD.
    Incorrect. The absence of sharing rules does not change the OWD; the Private setting remains in effect.
  4. The reps' profiles include the 'View All Data' system permission, which takes precedence over the OWD.
    Incorrect. 'View All Data' would grant visibility, but the admin traced the access to 'Grant Access Using Hierarchies', not to a profile permission.

In a master-detail relationship, what happens to the related detail records when someone deletes the master record?

  1. The system blocks the delete until the admin manually removes every related detail record.
    Incorrect. The master delete is not blocked; the details are removed automatically through cascade delete.
  2. The detail records are automatically moved to a default master record chosen by the admin.
    Incorrect. Master-detail has no concept of reparenting to a default master; cascade delete always applies.
  3. All related detail records are automatically cascade-deleted along with the master record, and both master and detail records are placed in the Recycle Bin. (Answer)
    Correct. Deleting the master removes its details as well, and the whole set lands in the Recycle Bin and can be restored together.
  4. The detail records stay in the system as unrelated, orphaned records with a blank relationship field.
    Incorrect. Orphaned details are possible with lookups, not master-detail, where cascade delete is mandatory.

Compliance needs two years of history on configuration changes made by an automated integration user, but the Setup Audit Trail only goes back 180 days. How should the admin meet the two-year retention requirement?

  1. Turn on the Salesforce Shield Event Monitoring add-on, which rebuilds audit data for the previous 2 years.
    Incorrect. Event Monitoring records activity only from the time it is enabled; it cannot recreate past setup changes.
  2. Buy the Field Audit Trail add-on in Salesforce Shield to lengthen Setup Audit Trail retention to 2 years.
    Incorrect. Field Audit Trail lengthens field history retention (up to 10 years), not Setup Audit Trail retention.
  3. Build a scheduled Flow that copies Setup Audit Trail data into a custom object every day, accumulating two years of history from now on.
    Incorrect. A flow would only help going forward, cannot recover older history, and does not answer the current request.
  4. Export the Setup Audit Trail on a regular schedule (at least every 180 days) with the Download Now button or the API, and keep the CSV files in an external archive for long-term retention. (Answer)
    Correct. With only 180 days kept natively, scheduled exports archived outside Salesforce are the standard way to retain audit data long term.

Questions are original and follow the official exam guide. Praxis Academy is not affiliated with Salesforce, Inc.