SalesForce Certified Advanced Administrator (CRT-211) Certified Advanced Administrator Free Practice Test — 30 Questions
This practice bank exercises the critical thinking and technical decision-making expected of a Salesforce Advanced Administrator. Questions span data retrieval via REST and SOAP APIs, security through sharing settings and permission sets, deployment strategies using Change Sets and metadata-driven design, and system performance monitoring. You will analyze trade-offs between efficiency and correctness, apply governance limits, and configure automation like workflow rules and validation rules. The scenarios require you to choose the best approach from multiple plausible options, reinforcing the principles of scalable, secure, and maintainable Salesforce administration.
What this SalesForce Certified Advanced Administrator (CRT-211) Certified Advanced Administrator practice set measures
This is an analysis of the practice bank, not a claim about the vendor's live exam blueprint. Use it to identify the knowledge, judgment, and recall patterns exercised here, then verify your coverage against the current official exam guide.
Data Integration and Query Optimization
Efficient data retrieval is central to Salesforce integration. Administrators must balance API limits with the need to fetch related records. Relationship queries (parent-to-child subqueries) reduce API calls. SOQL filters like LAST_N_DAYS and boolean fields must use proper syntax—for example, `IsActive = true` not `= 'true'`. When using REST or SOAP APIs, the query endpoint with a well-formed SOQL statement is preferred over retrieving all records and filtering client-side. Governor limits restrict the number of records returned per call and total API requests in a 24-hour period. Understanding these constraints ensures reliable integrations.
- Use relationship queries to fetch parent and child records in one call.
- Always apply filters in SOQL (e.g., LastModifiedDate, IsActive) to minimize data transfer.
- SOQL boolean fields should be compared to true/false without quotes.
- Prefer the /query endpoint for complex filtering; avoid post-retrieval filtering.
- Be mindful of the 24-hour API call limit and the 10,000 record retrieval limit per query.
Security, Sharing, and Access Control
Salesforce's sharing model determines record visibility. Organization-Wide Defaults (OWD) set the baseline; when set to Private, manual sharing or sharing rules grant additional access. Permission sets extend profile permissions without changing profiles. Report access depends on both the report's sharing setting (Public vs Private) and the underlying data's sharing rules. Troubleshooting report access involves checking OWD, sharing rules, and permission sets. For collaboration, manual sharing is effective for one-off access, while sharing rules automate access based on roles or criteria. The correct answer often emphasizes verifying sharing settings before other steps.
- OWD to Private means users see only records they own; sharing rules grant broader access.
- Manual sharing provides ad-hoc access; sharing rules automate based on criteria.
- Report sharing must be set to Public to allow all users to view it, but data access still depends on record sharing.
- Permission sets can grant access to reports and fields beyond profile permissions.
- When users cannot see reports, first review the custom object sharing settings and ensure proper sharing rules exist.
Deployment, Customization, and Metadata
Deploying changes across environments requires managing dependencies. Change Sets allow moving components from source to target org, but all dependent components must be included in the same Change Set to avoid errors. Metadata-driven development—using Custom Metadata Types—enables flexible configuration without code changes. When merging department-specific data models, a unified data model with standardized objects and training minimizes disruption and improves reporting. Custom objects should be designed with future adaptability in mind, leveraging metadata for behavior rather than hard-coded logic.
- Include all dependent components (objects, fields, Apex) in one Change Set to avoid deployment failures.
- Custom Metadata Types allow dynamic configuration changes without Apex or deployment.
- A unified data model standardizes objects across departments, improving consistency and cross-functional reporting.
- Avoid hard-coding logic; use metadata to define structure and behavior for easier future updates.
- Training users on new data models reduces resistance and ensures adoption.
Reporting, Automation, and Change Management
Effective reporting uses summary reports grouped by relevant dimensions (e.g., sales rep, region) with summary fields (total, average, count). Filters must be applied to include only closed-won opportunities with specific date ranges and deal sizes. Workflow rules automate actions based on criteria; for inactive leads, combine status change, score threshold, and last activity date conditions. Validation rules enforce data quality, and multiple failing rules block the record and display all error messages. Change management emphasizes early and continuous stakeholder engagement to mitigate resistance and ensure successful adoption.
- Summary reports with grouping and summary fields provide aggregated insights; use filters to narrow scope.
- Workflow rule criteria can combine multiple conditions (status, score, date) to trigger email alerts.
- Validation rules are evaluated on save; all failed rules produce error messages, blocking the record.
- Change management success depends on involving stakeholders early, gathering feedback, and providing training.
- Einstein Lead Scoring leverages historical data for predictive lead conversion ranking, automating lead prioritization.
Practice SalesForce Certified Advanced Administrator (CRT-211) Certified Advanced Administrator with real flashcards
Read the prompt, commit to an answer, then flip the card. Move through the deck at your own pace and repeat any topic that does not come back quickly.
Card 1 of 20
1 reviewed this session
Static practice bank
Start the 30-question diagnostic
The complete question bank is embedded in this pre-rendered page. There is no database request or second content download when you begin.
A company is integrating its Salesforce instance with an external application using the Salesforce REST API. The external application needs to retrieve a list of all active accounts and their associated contacts. The developer decides to use a combination of SOQL queries and REST API calls. Which approach should the developer take to ensure efficient data retrieval while adhering to Salesforce API limits?
Study workflow
Turn one SalesForce Certified Advanced Administrator (CRT-211) Certified Advanced Administrator attempt into a study plan
- 1
Troubleshoot Report Access Issues
First, verify the user has the necessary permission sets and profile permissions to view the report. Next, check the report's sharing setting (Public vs Private). If the report is Private, the owner must share it. Then, review the underlying custom object's OWD and sharing rules. Finally, confirm that sharing rules grant access to the user's role or group. Use the 'Sharing' button on the object to audit access.
- 2
Deploy a Feature Using Change Sets
In the source org, create an outbound Change Set and add all components that the feature requires, including custom objects, fields, Apex classes, and any dependencies like permission sets or page layouts. Ensure no component is omitted—dependencies must be included in the same Change Set. Upload the Change Set to the target org. In the target org, validate the deployment first, then deploy. Monitor for errors; if any, add missing components and retry.
- 3
Create a Summary Report for Sales Performance
From the Reports tab, create a new 'Summary' report on the Opportunities object. Add a grouping by 'Owner' or 'Sales Representative' (if a custom field). Add columns for Amount, Expected Revenue, etc. Use summary fields to calculate Total Revenue, Average Deal Size, and Record Count. Apply filters: Stage = 'Closed Won', Close Date = 'Last 3 Months', and Amount > 5000. Save and run.
- 4
Implement Dynamic Resource Allocation in Multi-Tenant Setup
Configure the platform to use elastic resource pooling (e.g., Salesforce's multi-tenant infrastructure automatically handles this). For custom clouds, implement a resource scheduler that monitors tenant usage in real time. Set thresholds so that no single tenant can exceed a percentage of total capacity. Use data isolation (org-level security) to prevent cross-tenant data access. Test under peak load to verify performance.
- 5
Set Up a Manual Sharing Rule for a Specific Record
Navigate to the record (e.g., Account) that needs sharing. Click the 'Sharing' button. In the sharing list, click 'Add'. Choose the user or group to share with (e.g., Sales Manager). Select the access level (Read Only or Read/Write). Optionally set a reason. Click 'Save'. The shared user will now see the record even if OWD is Private.
FAQ
Questions about this exam practice page
Clear boundaries on what the bank covers, how to use it, and where official vendor information still matters.
What is the difference between manual sharing and sharing rules?+
Manual sharing allows record owners to grant access to specific users or groups on a per-record basis. Sharing rules automate access for multiple records based on criteria (e.g., role hierarchy) and are set by administrators. Manual sharing is for one-off access; sharing rules ensure consistent access patterns.
How does Einstein Lead Scoring work?+
Einstein Lead Scoring uses predictive analytics on historical lead conversion data to assign a score (0–100) indicating likelihood to convert. It automatically identifies top influencers, such as lead source or industry. The score is updated in real time as new data arrives, helping sales teams prioritize leads.
What are the best practices for using SOQL with the REST API?+
Use the /query endpoint with a SOQL query that filters and orders data server-side. Include relationship subqueries to fetch related records in one call. Apply filters like LastModifiedDate to limit results. Avoid retrieving all records and filtering client-side. Respect governor limits on query rows (max 10,000 initially, 50,000 with queryMore).
Why should dependent components be included in the same Change Set?+
Change Sets deploy components sequentially; if a component references another not yet deployed, it fails. Including all dependencies ensures the target environment has them before they are needed. This avoids validation errors and partial deployments. Always check component dependencies via Setup auditing tools before uploading.
What should I check first when users cannot access a report?+
First, confirm the user has a permission set or profile that grants 'View Reports' access. Then inspect the report's sharing setting: if it's Private, only the owner and users with 'Modify All Data' can see it. Finally, verify the underlying data (e.g., custom object) sharing settings allow the user to see the source records.
Build the next review session
Browse another free bank or use the study strategy guide to turn your misses into spaced review.