certified-advanced-administrator Sample Questions & Answers

This is the standard Salesforce solution. A Matching Rule defines how duplicates are identified (e.g., based on email and name). A Duplicate Rule then uses the matching rule to specify what happens when a duplicate is detected, such as alerting the user or blocking the record creation. Duplicate rules can be configured to apply to different operations, including manual creation and imports.

This statement is false. If a process is configured to run only when a record is created, its scheduled actions will remain in the queue even if the record is later edited to no longer meet the criteria. To have the system re-evaluate the criteria and potentially remove the scheduled action, the process must be configured to run when a record is 'created or edited'.

When deploying Apex code to a sandbox or production environment, Salesforce runs all Apex tests in the target org. The deployment will fail if the overall code coverage in the target org, including the new code, is less than 75%. This is a common cause for deployment failures involving Apex.

Joined Reports are specifically designed to display data from different report types in separate blocks within a single report. This scenario requires one block for a Campaign report (using a cross-filter) and a second block for a Lead report. Only a Joined Report can combine these unrelated data sets into one view.

Salesforce Content uses a specific permission model based on library membership. The administrator should first add the 'Legal Team' to the library. Then, to grant specific delete rights, they must create a custom library permission that includes the 'Delete Content' privilege. This custom permission can then be assigned to the specific Contract Manager users within that library, while other legal team members get a more restrictive permission (like Author or Viewer).

A custom object can have a maximum of two master-detail relationships. The scenario already describes one master-detail relationship where 'Project' is the master to 'Milestone'. Because an object can only be the master in two master-detail relationships, and it is the master to Milestone, it can only be the master in one more. However, the question asks for additional master-detail relationships on the project object, implying it would be the detail. Since it is already a master, it cannot also be the detail in a new master-detail relationship if it already has child records.

This is a classic access control scenario. The user's profile grants them object-level permission to 'Edit' Opportunities, which makes the 'Edit' button visible. However, the Organization-Wide Default (OWD) is Read-Only, and because the user is not the owner, they need a sharing rule (or manual share) to grant them record-level write access. Without it, the system correctly prevents the save action with an error.

The correct design is to create a distinct Entitlement Process for each support level ('Gold' and 'Silver'). Within each process, the administrator can define specific milestones. Crucially, different Business Hours can be associated with each Entitlement Process, ensuring that the milestone countdown for 'Silver' customers only occurs during their 12/5 support window, while the 'Gold' customers' clock runs 24/7.

This specific option in the Custom Report Type setup creates a left outer join. It ensures that all records from the primary object (Accounts) are included in the report, and it will show related Opportunity data only where it exists. This perfectly matches the requirement to see all Accounts, both with and without Opportunities.

A Lookup Filter is the ideal declarative tool for this. It restricts the valid records that can be selected in a lookup field based on criteria on the related object. By creating a filter on the Position lookup that requires 'Position: Status EQUALS Open', the administrator ensures users can only select and save valid records, improving both data quality and user experience.