Salesforce-Certified-Administrator Practice Test Questions

Explanation:

Because Cases are related to Accounts via a lookup relationship, you cannot use a roll-up summary field (which only works on master-detail relationships). A record-triggered flow or Process Builder cannot execute on a defined schedule; they run only when records are created or updated. Instead, a scheduled flow (also called a schedule-triggered flow) allows you to run automation at specified intervals—every Friday evening in this scenario—to query all open Cases, group them by Account, count them, and then update each Account record with the calculated count. Scheduled flows are more scalable and efficient than repeatedly triggering on each Case change, especially when dealing with several hundred open Cases. They also supersede the older “Scheduled Paths” in Process Builder, offering greater performance and flexibility.

Explanation:

When users are only updating the Stage field, reducing page complexity speeds up their edits. Adding a Path component focuses attention on the Stage field by displaying it prominently at the top of the record page, guiding reps through key stages and required fields without navigating the full layout. Meanwhile, a simplified page layout that only includes essential fields and related lists minimizes load time and scrolling, so users can quickly save their changes. Although a Kanban view (option B) provides a board-style view of opportunities, it’s a list-view feature rather than editing the record page itself; an auto-launched flow (option C) would require users to trigger a separate flow, adding overhead rather than simplifying. Together, Path and a streamlined layout improve performance and user experience for routine Stage updates.

Explanation:

Einstein Opportunity Scoring analyzes historical opportunity data and identifies key factors that indicate a deal’s likelihood to close, assigning each opportunity a score and recommending focus areas. By highlighting high-probability deals and indicating at-risk opportunities, Sales reps can prioritize their pipeline more effectively and close more deals. Einstein Lead Scoring (option A) scores leads rather than open opportunities. Einstein Activity Capture (option C) syncs emails and events but doesn’t provide predictive insights on deal health. Einstein Search Personalization (option B) optimizes search results for individual users. Thus, Einstein Opportunity Scoring is the right tool to help Ursa Solar’s leadership and sales reps focus efforts on the most promising deals.

Security Health Check

Explanation:

Security Health Check analyzes your org’s security settings (including session settings, password policies, network access, and more) and compares them against the Salesforce Baseline Standard or a custom baseline. It highlights any settings that are less secure than recommended—such as session timeout, session fixation protection, or clickjack protection—and provides remediation steps. Field History Tracking (A) logs data changes, Setup Audit Trail (B) tracks metadata changes, and Organization-Wide Defaults (D) define record-level access; none evaluate session or security settings holistically. Therefore, the Security Health Check is the correct tool to identify and fix potential session vulnerabilities.

Only one theme can be active at a time, and a theme applies to the entire org.

Upto 150 custom themes can be created, modified, or cloned from the built-in themes.

Explanation:

When customizing org branding, remember that only one Lightning theme can be active at any moment and that it applies across Lightning Experience (including the mobile app); Classic uses its own styling. Administrators can create, modify, or clone up to 150 custom themes, providing flexibility for testing or seasonal branding updates. Although Chatter External Users and some community users see only certain default branding, this is less a general consideration for org-wide theming than the limits on active themes and creation capacity. Themes do not apply to Classic UI and aren’t limited to just the mobile app.

Record types

Explanation:

Salesforce prevents changing a picklist to a text field when that picklist is actively used by other metadata. Record types reference picklists to control which picklist values are available for different business processes. If a picklist field is assigned to one or more record types, you cannot change its type until you remove those references. Formula fields or Visualforce pages referencing the picklist would also block changes, but record types are the most common culprit when administrators see the “field is referenced somewhere else” message during a type change. Removing or updating record type assignments allows the conversion to proceed.

Explanation:

To enable customers to generate cases on their own, Web-to-Case embeds a form on your company website that captures case data directly into Salesforce. Email-to-Case processes inbound customer emails—each email creates a case automatically. Both solutions provide self-service entry points: Web-to-Case for form-based submissions and Email-to-Case for email requests. Case Escalation (B) and Case Queues (C) manage case processing within Salesforce but don’t enable external case creation. By combining Web-to-Case and Email-to-Case, DreamHouse Realty offers customers flexible, self-service options to log warranty issues.

Case Escalation Rule

Explanation:

Case Escalation Rules automatically monitor case age or inactivity and perform actions—such as sending email alerts—when cases exceed specified thresholds. You can configure an escalation rule entry to trigger two hours after case creation if there’s been no update, notifying the manager. Assignment Rules (A) run only on creation or reassignment, Omni-Channel Supervisor (C) provides monitoring dashboards, and formula fields (D) only display calculated values, not send notifications. Thus, setting up a Case Escalation Rule with a 2-hour escalation interval is the correct approach to alert managers of unattended cases.

Use the equals operator and {!$GlobalConstant.True} as the value.

Explanation:

In a screen flow, a Decision element evaluates flow variables or record data. For a checkbox field, the value is Boolean, so you must compare it to the global constant representing true or false. Using the equals operator with {!$GlobalConstant.True} correctly tests whether High_Value_Customer__c is checked. The “contains” operator isn’t appropriate for Boolean values, and you should not use the literal field label (“High Value Customer”) in the decision test. Therefore, configure the Decision’s criteria as High_Value_Customer__c Equals {!$GlobalConstant.True} to skip the first screen when the checkbox is checked.

Default Language

Currency Local

Explanation:

In Company Information, administrators set the Default Language—which defines the baseline UI language for users—and the Currency Locale, which determines number, date, and currency formats as well as default corporate currency. While Login Hours (A) and Password Policy (B) are defined under Security settings, they aren’t part of the Company Information section. Configuring the Default Language and Currency Locale ensures that new users inherit correct regional settings and that multi-currency orgs display values appropriately for global teams.