Master the Salesforce Certified Platform Developer I (WI24) CRT-450 Exam with Confidence!

 Validation rules and record-triggered flows are two declarative options for building out the business logic layer of a Salesforce application. Validation rules allow the developer to define criteria and error messages to prevent invalid data from being saved1. Record-triggered flows allow the developer to automate actions based on changes in records, such as creating, updating, or deleting related records2. Both of these options can be configured and maintained by a Salesforce administrator without writing code. References:

• Validation Rules, Trailhead module
• Record-Triggered Automation, Trailhead module

The with sharing keyword on the class declaration enforces the sharing rules that apply to the current user. This means that the user can only see and modify the records that they have access to based on the organization-wide defaults, role hierarchy, sharing rules, manual sharing, teams, and territories. The without sharing keyword, on the other hand, ignores the sharing rules and allows the user to access all records, regardless of ownership or sharing settings. This can pose a security risk and should be used with caution. The schema describe calls and the UserInfo Apex class do not directly affect the sharing rules, but rather provide information about the object and field permissions, and the user’s profile and role, respectively. These can be used to check the user’s access level, but not to enforce the sharing rules on the custom search tool. References:

• Apex Developer Guide: Using the with sharing, without sharing, and inherited sharing Keywords, pages 13-14
• Trailhead: Platform Developer I Certification Study Guide: Apex Basics and Database, unit 3

The correct answer is option C. The Lightning code segment that should be written to declare dependencies on a Lightning component, c:accountList, that is used in a Visualforce page is:

This code segment uses the ltng:require tag, which is a base Lightning component that allows you to load external JavaScript libraries and stylesheets in your Lightning components. The scripts attribute specifies the name and path of the JavaScript file that is uploaded as a static resource. The afterScriptsLoaded attribute specifies the name of the client-side controller action that is called after the scripts are loaded. This way, you can ensure that the c:accountList component has access to the JavaScript library that it depends on.

The other options are not valid code segments for declaring dependencies on a Lightning component. Option A uses the ltng:dependency tag, which is used to declare dependencies between Lightning components, not between a Lightning component and a JavaScript library. Option B uses the ltng:include tag, which is not a valid tag in the Lightning component framework. Option D uses the ltng:import tag, which is also not a valid tag in the Lightning component framework.

References: ltng:require - documentation, Using External JavaScript Libraries, Prepare for Your Salesforce Platform Developer I Credential

 To mark each Account in a List as either Active or Inactive based on the LastModified field value being more than 90 days, the developer should use a for loop, with an if/else statement inside. This technique allows the developer to iterate over the list of accounts, check the condition for each account, and update the field value accordingly. A switch statement is not suitable for this scenario, because it can only compare one expression with a set of constant values, not a range of values or a date calculation. An if/else statement without a for loop would not be able to process the entire list of accounts, only one account at a time.

References:

• : Loops
• : Switch Statements
• : If-Else Statements

The value of the count field after inserting an Account with an initial value of zero is 2, because both the trigger and the workflow rule will increment the count field by 1. The order of execution for this scenario is as follows:

• The Account record is inserted with a count value of 0.
• The system runs the before insert trigger, which increments the count value to 1.
• The system saves the record to the database, but does not commit yet.
• The system runs the after insert trigger, which does not affect the count value.
• The system executes the workflow rule, which increments the count value to 2.
• The system updates the record again with the new count value.
• The system commits the record to the database.

The field update in the workflow rule is configured to not re-evaluate workflow rules, which means that the workflow rule will not be triggered again by the second update. Therefore, the count value will remain 2.

References: Triggers and Order of Execution, Workflow Field Updates, Learn Salesforce Order of Execution

This code is vulnerable to a cross-site scripting (XSS) attack, because it takes user-supplied input and outputs it directly back to the user without escaping the XSS-vulnerable characters, such as <, >, ", ', and &. By setting the escape attribute to false, the developer disables the anti-XSS filter that is enabled by default for most Visualforce tags. An attacker can exploit this vulnerability by injecting malicious HTML or JavaScript code into the userInput parameter, which can then execute on the user’s browser and compromise their security or privacy. References:

• Cross Site Scripting (XSS)
• Security Tips for Apex and Visualforce Development
• Security Guidelines for Apex and Visualforce Development

 To satisfy the requirements, a developer should implement a flow and an invocable method. A flow is a declarative tool that allows you to automate business processes by collecting data and performing actions in your org or an external system1. An invocable method is a method that can be called by a flow, a process, or another Apex method2. By using a flow and an invocable method, the developer can achieve the following steps:

• Create a flow that guides the sales rep through the scripted steps with each new customer they create1.
• In the flow, use an Apex action to invoke an invocable method that calls the REST endpoint of UC’s ERP system and passes the customer information as a parameter23.
• In the invocable method, use the HttpRequest and HttpResponse classes to send a GET request to the REST endpoint and receive a response that contains the customer data4.
• In the invocable method, parse the response body and return the customer data as an output parameter to the flow24.
• In the flow, use a screen element to display the customer data to the sales rep if the customer exists in the ERP system1.

Using a future method or a trigger are not effective ways to satisfy the requirements. A future method is a method that runs in the background, asynchronously, after the current transaction finishes5. A trigger is a piece of Apex code that executes before or after a record is inserted, updated, deleted, or undeleted. Neither of these options can interact with the flow or the sales rep, and they are not suitable for calling a REST endpoint that requires a synchronous response5 . References: 1 Automate Your Business Processes with Flows | Salesforce Trailhead1, 2 InvocableMethod Annotation | Apex Developer Guide | Salesforce Developers2, 3 Call Apex Code from a Flow | Salesforce Trailhead3, 4 Apex REST Callouts | Apex Developer Guide | Salesforce Developers4, 5 Asynchronous Apex | Apex Developer Guide | Salesforce Developers5, Triggers | Apex Developer Guide | Salesforce Developers

The best way to declare maxAttempts to meet the requirements is to declare it as a private static variable on a helper class. This will ensure that the variable is initialized only once per Apex transaction, and that its value is preserved and shared across trigger executions. A private static variable is a variable that belongs to a class and not an instance, and that can only be accessed within the class. A helper class is a class that contains common methods or variables that can be used by other classes or triggers.

References: The use of private static variables and helper classes can be referenced in the Salesforce Platform Developer I learning documents, specifically in modules that cover Apex basics and triggers, such as:

• Apex Basics & Database
• Apex Triggers
• Apex Testing

SOSL and SOQL are two different types of search languages in Salesforce. SOSL is a programmatic way of performing a text-based search against the search index, while SOQL is the equivalent of a SELECT SQL statement and searches the org database1. The developer should consider the following factors when deciding between SOQL and SOSL2:

• The number of records to be returned: SOSL can return up to 2,000 records from multiple objects, while SOQL can return up to 50,000 records from a single object or from multiple objects that are related to one another1.
• The speed of text searches: SOSL is generally faster than SOQL for text searches, especially if the search expression uses a CONTAINS term. SOSL can tokenize multiple terms within a field and build a search index from this, which makes SOSL searches more efficient and relevant1.
• The knowledge of the object or field: SOSL is useful when the developer does not know which object or field the data resides in, and wants to retrieve data for a specific term across multiple objects and fields. SOQL is useful when the developer knows which objects the data resides in, and wants to retrieve data from a single object or from multiple objects that are related to one another1.
• The type of data to be retrieved: SOSL supports text, email, and phone fields, and can retrieve data that is in Chinese, Japanese, Korean, or Thai. SOQL supports number, date, or checkbox fields, and can retrieve data from big objects1. References:
• Introduction to SOQL and SOSL | SOQL and SOSL Reference | Salesforce Developers
• Difference between SOSL and SOQL search types - Salesforce

The correct answer is option B. Use Security.stripInaccessible to remove fields inaccessible to the current user. This method takes a list of records and an access type (READ, UPDATE, CREATE, or UPSERT) and returns a new list of records with the inaccessible fields removed. This way, the Lightning web component can display the records without throwing any errors due to field-level security.

Option A is incorrect because WITH SECURITY_ENFORCED is a SOQL clause that enforces field-level security on all fields in the query. If the query returns any fields that the user does not have access to, the query will throw an exception. This is not desirable for the Lightning web component, as it will prevent the component from displaying any records at all.

Option C is incorrect because Lightning Data Service is a layer of Lightning web components that provides access to Salesforce data and metadata, cache management, and data synchronization. However, Lightning Data Service does not automatically handle field-level security for the records it retrieves. The developer still needs to use Security.stripInaccessible or another method to remove the inaccessible fields.

Option D is incorrect because Lightning Locker Service is a security feature that isolates Lightning web components from each other and from the rest of the page. It does not enforce sharing rules or field-level security for the data that the components access.

References: Security.stripInaccessible (Apex Developer Guide)), WITH SECURITY_ENFORCED (Apex Developer Guide)), Lightning Data Service Basics (Trailhead)), Lightning Locker (Lightning Web Components Developer Guide))