When a requirement involves storing configuration or "secret" data that needs to vary based on the specific user or profile, Hierarchy Custom Settings (Option C) are the correct choice. Unlike Custom Metadata (Option B), which is available to the entire organization regardless of the user, Hierarchy Custom Settings use a built-in logic to provide values based on the "most specific" level defined.
The hierarchy follows a specific order: User > Profile > Organization. If a secret key is defined at the User level, that value is returned for that specific user. If not, the system looks for a value defined at the user's Profile level, and finally falls back to the Organization-wide default. This allows a developer to store sensitive keys or flags and restrict or vary them dynamically based on the current user's identity.
Custom Metadata is better suited for application-wide configurations that need to be deployable via packages, but it lacks the granular per-user/per-profile override capability inherent to Hierarchy Custom Settings. Static Resources (Option A) are public to anyone with access to the resource, and Cookies (Option D) are stored on the client side, making them insecure for "secret" data. Therefore, Custom Settings provide the best balance of security and hierarchical flexibility for this use case.

5
The iss6ue described is a direct result of how Salesforce treats data during sandbox refreshes and unit testing.
Custom Settings (both List and Hierarchy) store their information as data records. By default, sandbox refreshes do not include data records from Production unless it is a Full Sandbox. Furthermore, Apex unit tests are isolated from organization data; they cannot "see" Custom Setting records unless the records are explicitly created within the test or the @isTest(SeeAllData=true) annotation is used (which is a poor practice).
Custom Metadata (Option C) solves this by treating configuration records as metadata rather than data.
Because they are metadata, the records are automatically included in every sandbox refresh and are deployable via Change Sets or the Salesforce CLI. Most importantly, Custom Metadata is visible to Apex unit tests without needing to create setup data or bypass test isolation. This ensures that configuration-dependent logic remains consistent across all environments and that tests pass reliably after a refresh. Replacing Custom Settings with Custom Metadata is the modern Salesforce standard for environment-independent configuration management.

To perform historical auditing and analysis of user behavior-such as tracking the last login time-Salesforce provides Event Monitoring (Option C). This feature captures a wide range of "Event Types," including logins, logouts, URI (page) clicks, and API calls.
These events are stored in EventLogFile objects. Each day, Salesforce generates log files for the previous day's activity. A developer can query these files or use tools like the Salesforce Event Log File Browser to see a comprehensive history of user logins. This is the correct choice when real-time alerts are not necessary and the goal is to analyze patterns over time.
Option A refers to Change Data Capture, which is for tracking record changes, not user sessions. Option B is for the standard Salesforce Calendar. Option D (Developer Log) is used for debugging Apex and system execution in the short term and does not provide a reliable or long-term history of user login events. Event Monitoring provides the high-fidelity audit trail required for compliance and security analysis.

This query requires a specific understanding of how Salesforce handles old records. Salesforce "archives" Tasks that are older than 365 days to maintain performance. These archived records are not returned by standard SOQL queries.
To include archived records in a query, the developer must use the ALL ROWS keywords at the end of the query. However, ALL ROWS also returns records that are in the Recycle Bin (deleted records). To satisfy the requirement of "including archived" but "excluding deleted," the developer simply needs to rely on the fact that standard WHERE clause filters apply to the results of ALL ROWS.
Option B is the most accurate. In SOQL, isDeleted=false is implicit unless you are specifically looking for deleted records. The crucial part is the ALL ROWS keyword which brings the archived tasks into scope.
Options A and D are incorrect because isArchived=true would only return the archived tasks and exclude those that are not yet archived. Option C is redundant because isDeleted=false is the default behavior. The syntax => in the prompt options is also technically a typo for >=. Option B represents the standard way to query across the "active" and "archived" boundary while ignoring the Recycle Bin.

When a Visualforce page is slow because it attempts to load a massive dataset all at once, the bottleneck is often the time taken by the controller constructor to query and process those records before the page can even begin to render. Lazy Loading (Option B) is a strategy where the developer avoids loading all data during the initial page initialization.
Instead of querying 10,000 records in the constructor, the developer can load only the structural elements of the page first. Then, using an action method (triggered by <apex:actionFunction> or a window.onload script), the data is fetched in the background. This allows the user to see the page layout immediately while the data
"populates" shortly after. This significantly improves the Time to First Byte (TTFB) and the perceived performance of the page.
Option A (transient) is excellent for reducing the View State size and speeding up postbacks (button clicks), but it does not inherently speed up the initial load time of a large dataset. Option C (JavaScript processing) can help but doesn't solve the data retrieval bottleneck. Option D (actionPoller) is used for periodic updates and is not an efficient way to load an initial large dataset. Lazy loading ensures that the "heavy lifting" is decoupled from the initial page load, providing a more responsive experience.