Certified Advanced Administrator — Free Practice Questions
10 free sample questions from a bank of 195, with the correct answers and explanations. No signup required — start practising right now.
1An administrator has been asked to create a replica of the production organization. The requirement states that existing fields, page layouts, record types, objects, and data contained in the fields and objects need to be available in the replica organization.
How can the administrator meet this requirement?
Create a developer sandbox
Create a configuration-only sandbox
Create a metadata sandbox
Create a full sandbox
Answer: D
The short version
D — Only a full sandbox copies metadata plus all data. The replica must include fields, layouts, record types, objects and the data inside them. Full is the sole sandbox type that carries production data at full volume.
Key concepts in this question
Developer sandboxes hold metadata only: they copy configuration without production records, suitable for code work.
Configuration-only and metadata scopes exclude data: partial metadata sets never bring record content.
Full sandboxes mirror production: schema plus all data, including attachments and history where limits allow, are duplicated.
Replica means usable data in fields: testing with real data volumes requires the data layer, not just layout shells.
Why D is correct
The requirement explicitly lists existing fields, page layouts, record types, objects and data contained in fields and objects, which is the textbook definition of a full sandbox copy. Developer and configuration-only types omit data by design and therefore cannot satisfy the data clause. Choosing full sandbox delivers both configuration and records so the replica behaves like production.
Why the others are wrong
A. Developer sandbox copies metadata with no data, so field contents would be empty.
B. Configuration-only sandbox is for metadata testing and carries no production records.
C. Metadata sandbox is not a standard data-bearing type and does not provide full data replication.
Certified-Advanced-Administrator exam tip
Hear replica with data included equals full sandbox, without data equals developer.
2Universal Containers purchased Field Service Lightning licenses in production and wants to make these licenses available in an active development sandbox with the minimum development impact.
How should an administrator create these licenses in the sandbox?
Use the Match Production Licenses tool.
Submit a Salesforce Support case.
Merge Production and the sandbox using a template.
Refresh the sandbox from production.
Answer: A
The short version
A — Match production licenses in place. Field Service licenses already exist in production and are missing in the active dev sandbox. The Match Production Licenses tool adds the alignment without rebuild.
Key concepts in this question
Sandbox licenses drift from production: purchases made after sandbox creation do not auto-appear in old sandboxes.
Match tool syncs license counts: the Company Information match function aligns sandbox license totals to production.
Refresh is disruptive: refreshing would wipe in-flight development work just to gain licenses.
Support cases are unnecessary: license matching is self-service and does not need Salesforce Support.
Why A is correct
Because the sandbox is active with work in progress, the goal is minimum development impact while making production-bought Field Service licenses usable for testing. The Match Production Licenses tool updates the sandbox license pool to mirror production without altering metadata or data. That preserves development state and is faster than refresh or template merge.
Why the others are wrong
B. Submitting a Support case adds delay when a self-service match action already exists.
C. Merging production and sandbox with a template is not a license operation and risks overwriting work.
D. Refreshing from production would deliver licenses but destroys current development changes.
Certified-Advanced-Administrator exam tip
Missing new production licenses in an active sandbox equals use Match Production Licenses.
3Universal Containers uses a custom object to track resources called Supply Items with a lookup to Accounts. The Supply Item records should only be visible by users that own the Account records.
Which sharing setting provides the correct visibility?
Controlled by Parent
Private
Public Read Only
Public Read/Write/Transfer
Answer: B
The short version
Supply Items uses a lookup to Account, so Controlled by Parent is not available and Private is the correct OWD to restrict visibility to Account owners and those granted access through hierarchy or sharing. Private enforces ownership based access as the most restrictive usable option for a lookup child.
Key concepts in this question
Organization wide defaults define baseline access for objects. Controlled by Parent applies only when the child is the detail in a master-detail relationship and mirrors parent access. Lookup children have independent sharing and ownership. Private restricts access to owners and users granted access via hierarchy, permissions, manual sharing or sharing rules. Public options open visibility broadly.
Why B is correct
Private is correct because a lookup relationship cannot use Controlled by Parent as its OWD, leaving Private as the most restrictive choice that limits Supply Items to owners and authorized users. With Accounts owned privately, setting Supply Items to Private keeps them visible only to users who own them or gain access through role hierarchy, permissions or sharing,.
Why the others are wrong
Option A Controlled by Parent is wrong because that setting is available only for master-detail detail objects, not for lookup relationships, so it cannot even be selected for Supply Items. Option C Public Read Only is wrong because it would expose all Supply Items to every user for viewing, violating the owner only requirement. Option D Public Read Write Transfer is wrong because it grants broad view and edit plus transfer rights, which is the opposite of restricted owner visibility.
Certified-Advanced-Administrator exam tip
When you see Controlled by Parent offered for a lookup object, eliminate it immediately and check whether Private plus sharing or a master-detail redesign is being tested for Advanced Administrator scenarios.
4Universal Containers sells monthly service subscriptions and wants to ensure their Opportunity reports accurately represent the amount of money to be received each month.
Which solution should an administrator use to meet this requirement?
Use product revenue schedules for each revenue period.
Use Process Builder and Flow to create custom object records.
Use Opportunity formula fields for each reporting period.
Use monthly Opportunity reporting snapshots.
Answer: A
The short version
Banked answer B is wrong here. Monthly subscription revenue must be spread across time with native product revenue schedules, so A is the correct choice for accurate monthly Opportunity reporting.
Key concepts in this question
Opportunity Amount is a single point-in-time value tied to Close Date. Product schedules split one Opportunity Product into dated installments for revenue and quantity. Revenue schedules track payment recognition over time while quantity schedules track delivery. Reports can then summarize scheduled revenue by period.
Why A is correct
A states use of product revenue schedules for each revenue period, which is exactly the native feature for this need. After enabling schedules, the admin sets schedule type on the product and agents establish monthly installments on each Opportunity Product. Finance then reports scheduled revenue per month instead of attributing the full contract value to one close month, matching the monthly subscription model precisely.
Why the others are wrong
B with Process Builder plus Flow and custom objects rebuilds standard functionality with extra objects, automation debt, and fragile reporting. C with formula fields per period is unscalable, since every new month needs schema changes and formulas cannot produce true time-phased report rows. D with reporting snapshots captures point-in-time totals on a schedule but does not distribute one Opportunity across future months the way revenue schedules do.
Certified-Advanced-Administrator exam tip
When the stem says monthly, installment, subscription, or recognize revenue over time, choose product revenue schedules. Eliminate custom-object automation answers when a native scheduling feature exists, and remember snapshots preserve history rather than phasing revenue.
5The inside Sales Manager at Universal Containers wants to be able to report on how long leads have a Lead Status of "Open" before the status changes to another value. Additionally, the sales team has requested the status value be changed with fewer clicks.
What should the administrator do to meet this requirement?
Use a Workflow Rule that sends an email when the Lead Status is changed.
Use a Quick Action to update a date field and change the status value.
Turn on field history tracking for the lead status field and create a report based on that field.
Use a formula field to calculate the date when the status changes.
Answer: C
The short version
C — settled key is C. C Turn on field history tracking for the lead status field and create a report based is the behavior the settled key requires, and this note shows why that action fits the stem while the other
Key concepts in this question
Settled outcome C: C Turn on field history tracking for the lead status field and create a report based on that fi captures what Salesforce expects here.
Stem constraint: The inside Sales Manager at Universal Containers wants to be able to report on how long leads have a Lead Status of sets the exact filter that removes look-alike tools.
Platform guardrail: declarative enforcement versus manual sharing versus automation timing decides between close options.
Why C is correct
The stem asks for one Salesforce mechanism, and C is the settled answer for this item. In context, C Turn on field history tracking for the lead status field and create a report based on that fi directly meets the requirement, because its object and trigger match the scenario. Salesforce builds this path for exactly this case, so admins using C get native enforcement without extra steps. That is why the corroborated key stays C even when crowd notes point elsewhere.
Why the others are wrong
A. Not correct because Use a Workflow Rule that sends an email when the Lead Status fits a different need.
B. Not correct because Use a Quick Action to update a date field and change the sta fits a different need.
D. Not correct because Use a formula field to calculate the date when the status ch fits a different need.
Certified-Advanced-Administrator exam tip
Remember this as C means C Turn on field history tracking for the lead status field and create a report b. On the Certified-Advanced-Administrator exam, match stem keywords to object plus timing, drop tools aimed at anot
6Universal Containers has a Positions object that represents Job Positions and a Job Applications object that represent people that have applied to the Position.
The Job Application object has a lookup to Position. They want to run a report that shows all Positions that do NOT have any child Job Applications.
Which solution would meet the requirements?
Use the standard Job Applications with Position report type.
Use a custom report type that only displays Job Applications without Positions.
Use the standard Position without Job Applications report type.
Use the standard Position report type with a cross filter.
Answer: D
The short version
D — Use the Position report type with a cross filter for no children. The need is all Positions that do not have Job Applications. A cross filter of Positions without Job Applications returns exactly that anti-join.
Key concepts in this question
Lookup allows orphan parents: Job Application looks up to Position, so some Positions have zero children.
Cross filters test absence: Positions without Job Applications filters to parents lacking related rows.
Standard report types start the base: the Position primary type can be extended with a related-object existence test.
Custom types for inverse misuse scope: a type built only for Applications without Positions reverses the required grain.
Why D is correct
Starting from the standard Position report type keeps the grain at one row per Position. Adding a cross filter for Positions without Job Applications suppresses any Position that has at least one child, leaving only childless Positions. That declarative anti-join avoids code and custom types while matching the lookup data model.
Why the others are wrong
A. Job Applications with Position lists child rows that have parents, the opposite of childless parents.
B. A custom type showing Applications without Positions returns orphan children, not parent Positions.
C. There is no standard Position without Job Applications type that precomputes this absence without a cross filter.
Certified-Advanced-Administrator exam tip
Show parents with no children on a lookup equals parent report type plus without cross filter.
7The Marketing Manager at Universal Containers wants to change the column headings for several of the fields on opportunity reports.
What approach should an administrator take to meet the requirements?
Use Rename Tabs and Labels to change the field labels as needed.
Edit the fields available for reports section in the Opportunities report type to make the changes.
Create bucket fields for each field and enter the new column heading in the bucket name field.
Build a custom report type and use Display As in Edit Layouts to make the requested changes.
Answer: D
The short version
D — Relabel columns with a custom report type Display As. The manager wants different column headings on opportunity reports without renaming fields globally. Display As in Edit Layouts overrides labels per report type.
Key concepts in this question
Rename Tabs and Labels is global: changing a field label there alters it everywhere, not just one report set.
Custom report types allow local aliases: Edit Layouts Display As changes how a field appears for reports built on that type.
Bucket fields group values: buckets categorize data into ranges, they do not rename column headers.
Report type field sections control availability: choosing fields for a type does not by itself rename their headings.
Why D is correct
Building a custom report type for Opportunities and using Display As in Edit Layouts lets the admin present friendlier column headings only where needed. That scopes the change to the requested reports and leaves list views, pages and other reports untouched. It is the documented mechanism for per-report-type label overrides.
Why the others are wrong
A. Rename Tabs and Labels would rename the field org-wide, which is broader than report-only headings.
B. Editing fields available for the Opportunities type controls inclusion, not the displayed column text.
C. Bucket fields create grouped categories, they do not relabel existing field columns.
Certified-Advanced-Administrator exam tip
Report-only heading change equals custom report type Display As, not global rename.
8Universal Containers wants to implement a recruiting application using an Applicant custom object and a Position custom object. Each position record may have many applicants associated with it.
What solution should the administrator recommend to ensure applicants are retained even if the position is removed?
Create a lookup field on Position.
Create a master-detail field on Applicant.
Create a lookup field on Applicant.
Create a master-detail field on Position.
Answer: C
The short version
C — Put a lookup to Position on Applicant. Each Position can have many Applicants, and Applicants must survive Position deletion. A lookup child keeps its row when the parent is removed.
Key concepts in this question
Lookup permits optional retention: child records can remain with an emptied lookup when the parent is deleted.
Master-detail cascades delete: deleting a master deletes its details, which would purge Applicants.
Child holds the foreign key: the many side carries the reference, so Applicant should hold the Position link.
Retention favors lookup: the keep-applicants rule is the classic lookup-versus-master decision driver.
Why C is correct
Creating a lookup field on Applicant pointing to Position models the one-to-many link while preserving independence. If a Position is removed, related Applicant rows are not cascade-deleted and remain for reassignment or history. That satisfies both the cardinality and the retention requirement in one field choice.
Why the others are wrong
A. A lookup on Position reverses direction and would imply one Applicant per Position, breaking the many model.
B. Master-detail on Applicant ties survival to Position, so deleting a Position would delete its Applicants.
D. Master-detail on Position reverses grain and still imposes cascade behavior in the wrong place.
Certified-Advanced-Administrator exam tip
Must keep children after parent delete equals choose lookup, not master-detail.
9Universal Containers suspects a user is logging in as other users and editing Account records without their approval.
Where would an administrator go to verify who is logging in as other users?
Setup Audit Trail
Debug Logs
Users Login History
History Tracking on the Account
Answer: A
The short version
Setup Audit Trail is the correct place to verify who logged in as another user and changed Accounts, because it records setup and administrative actions including delegate login activity. Login History shows login events but does not prove who acted as whom for record edits, while Account field history only shows field changes.
Key concepts in this question
Login As allows an admin with permission to act as another user for support and troubleshooting. Setup Audit Trail provides an auditable history of who changed what and when in setup and administration, including delegate user information when an admin acts on behalf of an end user. Login History tracks login attempts and sessions. Debug Logs capture execution details. Field history tracks data changes, not login impersonation.
Why A is correct
Setup Audit Trail is correct because it logs administrative actions with actor and delegate details, letting an auditor see that a specific admin logged in as another user. Salesforce retains recent setup changes with date, actor and action, and the delegate user column identifies the admin who acted on behalf of the end user, which directly answers the suspicion of impersonated Account edits.
Why the others are wrong
Option B Debug Logs is wrong because logs show code execution and transaction details for troubleshooting, not a persistent audit of who used Login As to edit records. Option C Users Login History is wrong because it shows login time, source and status but does not link impersonated sessions to subsequent Account edits with delegate attribution. Option D History Tracking on the.
Certified-Advanced-Administrator exam tip
For who did what as whom questions, choose Setup Audit Trail for delegate and setup actions and Login History only for access patterns, then correlate timestamps to prove impersonation.
10Universal Containers wants to convert a lookup relationship to a master-detail relationship.
What action should the administrator take prior to converting the relationship?
Remove roll-up summary fields on the parent prior to changing the field type.
Delete the current lookup field before adding the new master-detail field.
Ensure all existing records have a value in the current lookup field.
Select the allow re-parenting option on the master-detail relationship field.
Answer: C
The short version
C — Populate every lookup before converting to master-detail. Master-detail requires each child to have a parent. Empty lookups would violate that rule, so all rows need values first.
Key concepts in this question
Master-detail enforces required parent: every detail must reference a master at all times.
Lookups allow blanks: existing rows may have empty references that are legal today.
Conversion validates data: Salesforce blocks conversion if any child lacks a parent value.
Roll-ups and reparenting come after: summary fields and allow-reparenting settings do not fix missing parent values.
Why C is correct
Prior to changing the field type, the admin must query for records where the lookup is empty and fill them with the correct parent. Once no blanks remain, the conversion can enforce the mandatory-parent rule without orphaning rows. That data-cleanup step is the documented prerequisite for lookup-to-master promotion.
Why the others are wrong
A. Removing roll-ups on the parent is unnecessary, roll-ups are created after master-detail exists, not before.
B. Deleting the lookup destroys history and links, conversion preserves values by changing type in place.
D. Allow reparenting controls future moves between masters, it does not backfill missing parents.
Certified-Advanced-Administrator exam tip
Lookup to master conversion blocker equals blank lookups — fill them first.