PLAT-ADMN-301 Practice Questions

To debug platform events in Apex code, you need to set a debug log on the Automated Process entity. This entity represents an automated process user that runs flows and processes in your org. By setting a debug log on this entity, you can capture the events that are published and consumed by your flow and Apex code, as well as any errors or exceptions that occur during the execution.
Reference: https://developer.salesforce.com/docs/atlas.enus.platform_events.meta/platform_events/platform_events_debug.htm https://help.salesforce.com/s/articleView?id=sf.code_add_users_debug_log.htm&type=5

When troubleshooting missing email alerts due to hitting daily limits, Email Logs provide the most comprehensive information about email delivery status, including failures due to limit exceptions. Email Logs show detailed records of all emails sent from Salesforce, including timestamps, recipients, status (sent/bounced/dropped), and specific error messages when limits are exceeded. This allows administrators to identify patterns, verify which emails were blocked due to limits, and determine when the limit was reached.

B. HTML Email Status Report only tracks HTML email template usage and performance metrics, not delivery limits or failures.
C. Notification Delivery Settings control how users receive notifications but don't provide logs or information about limit violations.
D. Outbound Messages are for workflow-based integrations to external systems, not email alerts to users.

1. Salesforce Help Documentation: "Monitor Email Logs" - Setup > Email Administration > Email Log Files, describes accessing detailed email delivery information including limit exceptions

2. Salesforce Administrator Guide: "Email Administration" - Chapter on Email Limits and Monitoring, pages 412-415

3. Salesforce Platform Limits Quick Reference: "Daily Email Limits" - Section 3.2, explains email limit monitoring through logs

4. Official Salesforce Trailhead: "Email Administration" module - Unit on Troubleshooting Email Delivery

5. Salesforce Setup Audit Trail Documentation: "Email Log Files" - Details the comprehensive tracking of email status and limit violations

This scenario requires modeling a one-to-many relationship and tracking changes. A custom object (C) is the best solution to store multiple form submissions related to a single parent record (e.g., Opportunity). Each time a client fills out the form, a new record is created on this custom object. This is a scalable and reportable data model. To meet the requirement to "see what changed from one submission to the next," Field History Tracking (D) should be enabled on the fields of this new custom object. This creates a related list that logs the date, time, user, and nature of any changes made to tracked fields on each submission record.

A. Add forms as attachments: Attachments are unstructured files (like PDFs or images). You cannot report on the data within them or easily compare field-level changes between versions.
B. Make custom fields: Adding over 30 fields directly to the parent object is not scalable for multiple submissions. It would require creating duplicate sets of fields, making reporting and management difficult.

1. Salesforce Help. (2024). Create a Custom Object. "Custom objects are the heart of any application. Custom objects let you store data that’s unique to your organization." This is used to model relationships like one-to-many.

2. Trailhead by Salesforce. (2024). Data Modeling module, Create Object Relationships unit. Explains how to use custom objects and lookup/master-detail relationships to model business processes where one record can be related to many other records.

3. Salesforce Help. (2024). Track Field History for Standard and Custom Objects. "You can select certain fields to track and display the field history in the History related list of an object... For each field, the history includes the date and time of the change, the user who made it, and the old and new values."

A master-detail relationship cannot be deleted if it is referenced by other components in Salesforce. A roll-up summary field on the master object (Races) is directly dependent on the master-detail relationship with the child object (Runners) to perform its calculation. To remove the master-detail relationship field, this dependency must be removed first. Therefore, the administrator must delete the roll-up summary field from the Races object before the system will allow the master-detail relationship field to be deleted.

A. Changing the field type to a Lookup is an alternative to deletion, not a prerequisite for it. This action also requires removing roll-up summary fields first.
B. 'Allow Reparenting' is a feature of the master-detail relationship that allows child records to be moved to a new parent; it does not remove dependencies.
C. Cascade deletion is an inherent property of a master-detail relationship. There is no standard setting to simply "uncheck" this behavior to enable field deletion.

1. Salesforce Help, Considerations for Relationships, Section: "Master-Detail Relationship Field". "You can’t delete a custom object or field if it’s referenced in a roll-up summary field."

2. Salesforce Object Reference Guide, Custom Field Attributes. This guide details the dependencies of field types, implicitly noting that components like roll-up summaries must be removed before the fields they reference can be deleted. (This concept is foundational and covered in object relationship documentation).

The user who creates a record is its owner and, by default, has full Create, Read, Update, Delete (CRUD) access. Therefore, the sales manager can edit the contact they created. Additionally, a user with the System Administrator profile has the "Modify All Data" permission, which grants them the ability to edit any record in the organization, regardless of sharing settings or ownership. The organization-wide default (OWD) settings for Account and Contact do not override the explicit permissions of the record owner or a System Administrator.

A. Users above the owner in the role hierarchy can gain edit access if "Grant Access Using Hierarchies" is enabled, but this is not guaranteed and isn't the most complete answer.
B. The OWD for Accounts is "Public Read Only," which prevents all users from editing accounts they don't own, and by extension, the contacts on those accounts.
C. Access is granted up the role hierarchy, not down. Users below the owner in the hierarchy do not inherit access to the owner's records.

1. Salesforce Help, Who Can See My Records?. This document explains that record owners can always view and edit their own records. See the section on "Record-Level Access".

2. Salesforce Help, Standard Profiles. The System Administrator profile description explicitly lists the "Modify All Data" permission, granting universal edit access.

3. Salesforce Help, Organization-Wide Sharing Defaults. This document explains that "Controlled by Parent" means a record's visibility is tied to the parent record's visibility.

The problem is specific to one user, even though others with the same profile and permissions are unaffected. This indicates the error is related to the user's specific context or the data they are processing. The most effective troubleshooting step is to replicate the exact scenario. The debug feature in Flow Builder allows an administrator to run the flow as the specific user experiencing the error. This provides a detailed log of the execution path and reveals the precise point of failure and the reason for the error within that user's context.

B. Grant the user more data access by moving them higher in the role hierarchy: This is a potential solution, not a troubleshooting step. It's poor practice to grant more access without first diagnosing the root cause of the error.
C. Change the flow to run as System Context Without Sharing - Access All Data: This bypasses user permissions entirely, which might mask the underlying problem and create security risks. It doesn't help identify the cause of the user-specific error.
D. Grant the user the Modify All permission to ensure they have full system access: This is an excessive and insecure way to solve a problem. It does not help in diagnosing the specific reason for the flow failure.

1. Salesforce Help, Debug a Flow in Flow Builder, "Debug a Flow". This document details the process: "As you build and iterate on a flow, test it to make sure that it works correctly... In Flow Builder, you can enter values for the flow’s input variables and see the debug details as the flow runs... You can even debug the flow as another user."

2. Salesforce Trailhead, Flow Builder, Unit: "Test Your Flow". This module explains the utility of the Debug button, including the option to "Run flow as another user."

The Setup Audit Trail is a feature that tracks the recent setup changes made by administrators in a Salesforce organization. This includes modifications to metadata such as creating or modifying custom fields, changing their data types, or adjusting page layouts. When a field's type is changed from text to text area, this is a metadata change, not a data change within a record. The Setup Audit Trail provides a chronological log of these administrative actions, showing who made the change, when it was made, and what was changed, making it the appropriate tool for this investigation.

A. Developer Console: This is an integrated development environment used for writing and debugging Apex code, SOQL queries, and Lightning components, not for auditing administrative setup changes.
B. Field History Tracking: This feature tracks changes to the values within specific fields on a record over time, not changes to the field's underlying metadata or properties.
C. Debug Log: This tool captures detailed information about specific transactions, such as Apex code execution and API calls, for troubleshooting purposes, not for tracking metadata modifications.

- Salesforce Help. (2023). Monitor Setup Changes with Setup Audit Trail. Salesforce. Retrieved from https://help.salesforce.com/s/articleView?id=sf.adminmonitorsetup.htm&type=5. (This document states, "Setup Audit Trail tracks the recent setup changes that you and other admins have made to your org... It lists the 20 most recent setup changes... including... Custom fields").

- Salesforce Developer Documentation. (2023). Audit Trail. Object Reference for Salesforce and Lightning Platform. Retrieved from https://developer.salesforce.com/docs/atlas.en-us.objectreference.meta/objectreference/sforceapiobjectssetuphistory.htm. (This describes the underlying SetupAuditTrail object available via the API, which powers the UI feature).

The requirement is to capture start and end dates for each specific service plan sold, which can vary per line item on a single opportunity. The Opportunity Product (OpportunityLineItem) object represents each product on an opportunity. Therefore, custom date fields for "Start Date" and "End Date" should be created on the Opportunity Product object. A validation rule on this same object can then enforce that these fields are populated, potentially triggering only for products in the "Service Plans" product family.

A. A validation rule on the Opportunity object would apply to the entire record, not to individual product line items, which is where the dates are needed.
B. Formula fields are read-only and calculate values automatically. They cannot be used to capture manually entered start and end dates for each service plan.
C. A price book is used to manage product pricing and cannot be used to capture custom data fields like term start and end dates.

1. Salesforce Help, "Products," Considerations for Creating Products. This documentation outlines that Opportunity Products (OpportunityLineItems) represent the individual items on an opportunity, which is the correct location for line-item-specific data.

2. Salesforce Help, "Validation Rules," Create a Validation Rule. This guide explains that validation rules verify that the data a user enters in a record meets the standards you specify. Placing this on the Opportunity Product object ensures data integrity for each line item.

Entitlement management is the Salesforce feature specifically designed to help you define, enforce, and track customer support levels as part of a service agreement. It includes features like service contracts, entitlements, and milestones to ensure customers receive the correct level of support. While a service contract is part of the solution, "entitlement management" represents the entire feature set needed to implement and manage the support eligibility described in the scenario. It allows administrators to specify the type and level of support a customer is eligible for.

B. Adding a service contract is a necessary step, but it only represents the agreement. Entitlements are needed to define the specific support levels.
C. Turning on Service Cloud is a prerequisite to access these features, but it is not the action that solves the specific business requirement.
D. Salesforce provides standard objects for this functionality. Building a custom object would be redundant and would not integrate with standard case processes.

1. Salesforce Help, Entitlement Management Concepts. Document ID: sf.entitlementsconcepts.htm. "Entitlements are units of customer support... Service contracts represent a customer support agreement between you and your customers. Entitlements help you determine if your customers are eligible for support."

2. Salesforce Trailhead, Entitlement Management. Module: Service Cloud Platform Basics. This module explains how entitlements, service contracts, and milestones work together to manage customer service levels.

Synonyms (B) allow customers to find articles using different terms that mean the same thing, significantly improving search results when customers use varied terminology. Promoting specific search terms (D) ensures that when customers search for particular keywords, certain articles appear prominently in results, directly improving the relevance and visibility of important content. These two features work together to enhance the customer's ability to find the right knowledge articles quickly and efficiently.

A. Global Search configuration affects object-level search scope, not article search term optimization.
C. Einstein Search requires specific licensing and is not a standard knowledge search enhancement feature.

1. Salesforce Help Documentation: "Set Up Synonyms for Article Searches" - Knowledge Article Search Configuration, Section 3.2

2. Salesforce Knowledge Implementation Guide: "Promoted Search Terms" - Chapter 7: Optimizing Article Discovery, Pages 142-145

3. Salesforce Administrator Guide: "Configure Knowledge Settings" - Knowledge Base Management, Section 4.5

4. Trailhead Module: "Knowledge Search Basics" - Unit 3: Enhancing Search Results

5. Salesforce Documentation: "Knowledge Article Search" - Search Configuration Options, Article ID: 000334521