Explanation:
The requirement is to initiate an automatic daily backup of the Salesforce org. Salesforce does not provide a native "automatic daily backup" feature that creates a full point-in-time restore capability. While various tools exist for data extraction, a true backup solution requires specialized third-party applications that offer automated scheduling, versioning, and comprehensive metadata + data backup. These are typically found on the AppExchange.

Correct Option:

C. AppExchange package
Third-party backup solutions (like OwnBackup, Spanning, or Salesforce Backup) are available as managed packages on the AppExchange. These tools are specifically designed to provide automated daily backups with full point-in-time recovery. They offer scheduling, incremental backups, and comprehensive protection for both data and metadata, which is exactly what Northern Trail Outfitters requires for a reliable daily backup strategy.

Incorrect Option:

A. Refresh full copy sandbox
Refreshing a full copy sandbox creates a copy of your production org at a specific point in time but is a manual process, not an automatic daily backup. Sandboxes are intended for development and testing, not for backup purposes. Additionally, frequent refreshes are disruptive to development teams and do not provide incremental or versioned backups.

B. Data Export Service
The Data Export Service (Weekly Export Service) allows scheduling weekly or monthly exports of data, not daily. It also requires manual re-enablement every 6 months. More importantly, it only exports data (not metadata) and does not provide point-in-time restore capabilities. This service is not suitable for daily automated backups.

D. Report export
Report exports simply extract data based on report criteria into a file format like CSV or Excel. This is a manual, ad-hoc process that extracts only a subset of data based on report filters. It does not provide full org data backup, cannot be automated to run daily, and includes no metadata or restore functionality.

Reference:
Salesforce Help: "Salesforce Backup and Restore" – Salesforce AppExchange: Search for "Backup" solutions. Trailhead: "Salesforce Data Backup and Restore" module. Also refer to Salesforce documentation on "Weekly Data Export Service" limitations regarding schedule frequency and metadata exclusion.

Explanation:

This question tests understanding of Salesforce data access and visibility controls. When the Organization-Wide Default (OWD) is set to Private, users can only see records they own. To extend access to users in different role hierarchy branches without changing the OWD, a targeted sharing solution is required.

✔️ Correct Option:

A. Sharing Rules
When OWD is set to Private, Sharing Rules are the correct tool to extend record visibility beyond the role hierarchy. They allow admins to grant access to specific groups or roles — in this case, giving the marketing team read or read/write access to accounts owned by the sales team. This works perfectly when both teams are in separate hierarchy branches.

❌ Incorrect Options:

B. Public Groups
Public Groups are used to organize users for easier management, but they do not grant record access on their own. They must be combined with Sharing Rules to extend visibility. Simply creating a Public Group for marketing or sales does not automatically allow marketing to see sales-owned Account records.

C. Aliases
Aliases in Salesforce are short unique identifiers assigned to users for system use — such as in email templates or list views. They have no role in controlling record-level visibility or access. This option is entirely unrelated to sharing or data access management between teams or roles.

D. Assignment Rules
Assignment Rules are used to automatically assign records (like Cases or Leads) to specific users or queues based on defined criteria. They control ownership assignment, not record visibility. They do not extend read or write access to users who do not own the records, so they cannot solve this requirement.

🔧 Reference:
→ Salesforce Help – Sharing Rules
Confirms that Sharing Rules extend access to records when OWD is restrictive and users are in different role hierarchy branches.

→ Salesforce Help – Organization-Wide Sharing Defaults
Confirms that Private OWD restricts visibility to record owners only, and Sharing Rules are the mechanism to broaden access selectively.

Explanation:

This question tests knowledge of Salesforce Service Cloud components that provide guided processes for agents. The company needs a checklist to ensure consistent case servicing, which requires a component that displays guided steps, flows, and actions for service agents working on cases.

✔️ Option B (Correct):
The Actions & Recommendations component displays flows, quick actions, and recommendations directly on Case records, providing agents with a guided checklist of mandatory steps to complete when servicing cases. Salesforce Flow for Service creates automated, guided to-do lists that ensure consistent customer service experiences. The component shows which steps are mandatory (marked with an asterisk) and walks agents through multiple-step procedures, directly addressing the inconsistent service complaints.

❌ Option A (Incorrect):
"Business component" is not a specific Salesforce Lightning component. This is a generic, vague term that doesn't refer to any actual Salesforce feature. There is no standard Lightning component called "Business component" in the Salesforce component library, making this option invalid and unable to implement any checklist functionality for case servicing.

❌ Option C (Incorrect):
The Activity Timeline component displays past and upcoming activities (tasks, events, calls, emails) related to a record in chronological order. It shows what has been done and what's scheduled, but it doesn't provide a guided checklist or enforce mandatory steps. Activity Timeline is for tracking history and future activities, not for guiding agents through standardized service processes.

❌ Option D (Incorrect):
The Highlights Panel component displays key field values and important information at the top of a record page, such as status, priority, or custom fields. It provides a quick overview of record data but doesn't offer guided checklists, step-by-step procedures, or mandatory action enforcement. It's for displaying static information, not for guiding agents through service processes.

🔧 Reference:
→ Improve Case Management with Salesforce Flow – Trailhead
Confirms that Actions & Recommendations component provides automated, guided to-do lists for service agents to ensure consistent case handling.

→ Use the List in the Actions & Recommendations Component – Salesforce Help
Confirms the Actions & Recommendations component walks users through multiple-step procedures and shows mandatory steps for case servicing.

Explanation:

This question tests your understanding of the deployment lifecycle in Salesforce, specifically using Change Sets. It evaluates your knowledge of where to track the real-time progress, validation results, and overall eligibility of a metadata package after deployment or validation has begun.

✅ Correct Option:

✅ C. Deployment Status
The Deployment Status page in the target (Production) organization is the central hub for monitoring deployments. When you validate or deploy an inbound change set, this page shows real-time progress, tells you whether the deployment succeeded or failed, and lists specific apex test or metadata errors that need to be resolved.

❌ Incorrect options:

❌ A. Deployment Settings
The Deployment Settings page is used to establish and authorize deployment connections between organizations (such as authorizing a sandbox to send changes to Production). While it is necessary to set up the connection pipeline, it does not show whether a specific change set is ready or cleared to deploy.

❌ B. Inbound Change Sets
The Inbound Change Sets page displays the list of change sets that have been successfully uploaded from a source sandbox. While you use this page to initiate the "Validate" or "Deploy" actions, the actual verification of the system's ability to complete that deployment is tracked on the Deployment Status page.

❌ D. Inbound Change Sets
(Note: This option is a duplicate of Option B in the original question prompt). As stated above, the Inbound Change Sets page serves as the landing destination to receive and open the package, but it does not act as the engine that monitors validation success or deployment execution state.

🔧 Reference:
→ Salesforce Help: Monitor Deployments confirms that the Deployment Status page is used to check the progress and verify the validation success of metadata deployments.

Explanation:

This question tests knowledge of Salesforce mobile app customization and user experience optimization. Salesforce provides flexible mobile navigation and Lightning App Builder capabilities to tailor experiences for different user groups. Custom mobile menus and custom app pages help improve usability and productivity for field sales reps.

🟢 Correct Option:

C. Set up different mobile menu configurations for different types of users.
Salesforce allows administrators to customize navigation menus for mobile users. Different user groups can receive tailored menu options based on their job responsibilities, helping reduce clutter and improving efficiency while working in the Salesforce mobile app.

🟢 Correct Option:

D. Create a custom app page and assign to the mobile menu.
Custom Lightning app pages can be created with Lightning App Builder and added to the Salesforce mobile navigation menu. This provides users with quick access to important dashboards, records, or productivity tools directly from mobile devices.

🔴 Incorrect Options:

A. Allow mobile users to support Account Upstream Agent Closets.
This is not a valid Salesforce mobile app customization feature. The wording does not correspond to a supported mobile productivity or navigation capability within Salesforce.

B. Include Today as a guide from in line size.
This option does not describe a valid Salesforce mobile configuration feature. Salesforce mobile enhancements are handled through navigation menus, Lightning pages, actions, and mobile settings rather than this functionality.

🔧 Reference:
⇒ Salesforce Mobile Navigation Documentation
Confirms that Salesforce mobile navigation menus can be customized for users.

⇒ Lightning App Builder Documentation
Explains how custom Lightning pages can be created and used in Salesforce apps, including mobile experiences.