Free Salesforce CRT-450 Practice Exam with Questions & Answers | Set: 4

Name: How to Pass CRT-450 Exams
Brand: Examstrack
SKU: crt-450
Price: 42 USD
Availability: InStock

Questions 31

(Full question statement)

Universal Containers recently transitioned fromClassic to Lightning Experience. One of its business processes requirescertain values from the Opportunity objectto be sent via anHTTP REST calloutto itsexternal order management systemwhen the user presses a custom button on the Opportunity detail page.

Example fields:

Name

Amount

Account

Which two methods should the developer implement to fulfill the business requirement?

Choose 2 answers.

Options:

Create a customVisualforce quick actionthat performs the HTTP REST callout and use it on the Opportunity detail page.

Create anafter update triggeron the Opportunity object that calls a helper method using @future(callout=true) to perform the HTTP REST callout.

Create aLightning component quick actionthat performs the HTTP REST callout and use it on the Opportunity detail page.

Create aRemote Actionon the Opportunity object that executes an Apex immediate action to perform the HTTP REST callout whenever the Opportunity is updated.

Salesforce CRT-450 Premium Access

Marshall Hogan

16-May-2025

CRT-450 certification was a breeze with Examstrack. Best study guide and accurate dumps for a valid test experience.

Kathryn Rios

03-Jun-2025

Crushed CRT-450 using Examstrack's precise study materials. Their testing engine and questions answers guarantee real test success.

Israel Blackwell

19-Apr-2025

Thanks to Examstrack, aced CRT-450. Their study guide and real exam dumps are top-notch for ensuring a 100% valid test.

Questions 32

An Apex method, getAccounts, that returns a List of Accounts given a searchTerm, is available for Lightning Web Components to use.

What is the correct definition of a Lightning Web Component property that uses the getAccounts method?

Options:

@wire(getAccounts, { searchTerm: '$searchTerm' })

@track(getAccounts, '$searchTerm')

@wire(getAccounts, 'searchTerm: $searchTerm')

@wire(getAccounts, '$searchTerm')

Answer:

Explanation:

The correct syntax for using @wire to connect a Lightning Web Component property to an Apex method requires specifying the method and a configuration object that includes the reactive property prefixed with $. The correct usage is:

javascript

CopyEdit

@wire(getAccounts, { searchTerm: '$searchTerm' })

This correctly wires the reactive searchTerm property to the getAccounts method.

[Reference:, Wire a Property to an Apex Method, , To determine the correct definition of a Lightning Web Component (LWC) property that uses the getAccounts Apex method, we need to evaluate the syntax and usage of the @wire decorator in LWC, focusing on how it connects to Apex methods and passes parameters. Let’s analyze the problem and each option systematically, referencing Salesforce’s official Lightning Web Components Developer Guide., Understanding the Requirement:, Apex Method: The getAccounts method is an Apex method that returns a List and takes a parameter searchTerm. For an Apex method to be callable from an LWC, it must be annotated with @AuraEnabled(cacheable=true) (for @wire) and be static. The Lightning Web Components Developer Guide states: “To call an Apex method from a Lightning Web Component using @wire, the method must be static and annotated with @AuraEnabled(cacheable=true)” (Salesforce Lightning Web Components Developer Guide, Call Apex Methods)., LWC Property: The question asks for the correct definition of an LWC property that uses @wire to call getAccounts. The @wire decorator is used to wire a property or function to a data source, such as an Apex method, and can pass dynamic parameters., Parameter Passing: The searchTerm parameter must be passed dynamically to getAccounts, meaning its value comes from a reactive property (e.g., searchTerm) in the LWC. In LWC, reactive properties are tracked for changes, and the $ prefix is used to indicate reactivity in @wire parameters., LWC @wire Syntax:, The @wire decorator connects a property or function to a data source (e.g., an Apex method). When wiring to an Apex method, the syntax is: , javascript, Copy, @wire(apexMethod, { param1: '$property1', param2: '$property2' }), propertyName;, Apex Method Reference: The apexMethod is the imported Apex method (e.g., getAccounts imported from a controller)., Parameters: The second argument is an object mapping Apex method parameters to LWC properties. The $ prefix makes the property reactive, meaning the wired method re-invokes when the property changes. The Lightning Web Components Developer Guide explains: “Use the $ prefix in the parameters object to indicate a reactive property, so the wired method is called when the property’s value changes” (Salesforce Lightning Web Components Developer Guide, Pass Parameters to Apex Methods)., Result: The wired property receives an object with data (the Apex method’s return value) or error (if an error occurs)., Evaluating the Options:, A. @wire(getAccounts, { searchTerm: '$searchTerm' }) , Syntax: Uses @wire to call getAccounts and passes parameters as an object { searchTerm: '$searchTerm' }., Parameter Mapping: The searchTerm parameter of the getAccounts Apex method is mapped to the LWC’s searchTerm property. The $searchTerm syntax indicates that searchTerm is a reactive property, and getAccounts will be re-invoked if searchTerm changes., Correctness: This matches the standard LWC syntax for wiring an Apex method with parameters. The Lightning Web Components Developer Guide confirms: “Pass parameters to an Apex method as a JavaScript object, using the $ prefix for reactive properties” (Salesforce Lightning Web Components Developer Guide, Call Apex Methods)., Conclusion: Correct, as it uses the proper @wire syntax and parameter format., B. @track(getAccounts, '$searchTerm') , Syntax: Uses @track instead of @wire., Decorator: The @track decorator is used to make a property reactive, meaning the component re-renders when the property changes, but it does not wire the property to a data source like an Apex method. The Lightning Web Components Developer Guide states: “@track is used to mark a property as reactive for re-rendering, but it does not fetch data from a server” (Salesforce Lightning Web Components Developer Guide, Reactive Properties)., Parameter: Passing getAccounts and '$searchTerm' to @track is invalid, as @track does not accept arguments in this manner., Conclusion: Incorrect, as @track cannot be used to wire an Apex method., C. @wire(getAccounts, 'searchTerm: $searchTerm') , Syntax: Uses @wire to call getAccounts, but the parameters are passed as a string 'searchTerm: $searchTerm'., Parameter Format: The @wire decorator expects the second argument to be a JavaScript object (e.g., { searchTerm: '$searchTerm' }), not a string. The Lightning Web Components Developer Guide specifies: “The second argument to @wire for an Apex method must be an object mapping parameter names to values” (Salesforce Lightning Web Components Developer Guide, Pass Parameters to Apex Methods). Passing a string like 'searchTerm: $searchTerm' results in a runtime error or the Apex method not being called correctly., Conclusion: Incorrect, as the parameter format is invalid (string instead of an object)., D. @wire(getAccounts, '$searchTerm') , Syntax: Uses @wire to call getAccounts, but passes '$searchTerm' directly as a string, not as a parameter object., Parameter Format: The getAccounts method expects a parameter named searchTerm, so the correct format is { searchTerm: '$searchTerm' }. Passing '$searchTerm' as a single value does not map to the Apex method’s parameter name, causing the method to receive no value for searchTerm (or fail entirely). The Lightning Web Components Developer Guide notes: “Parameter names in the object must match the Apex method’s parameter names” (Salesforce Lightning Web Components Developer Guide, Call Apex Methods)., Conclusion: Incorrect, as the parameter is not passed as a properly formatted object mapping to the Apex method’s parameter., Why Option A is Correct:, Option A is correct because:, It uses the @wire decorator to properly connect the getAccounts Apex method to an LWC property., It passes the searchTerm parameter in the correct format: { searchTerm: '$searchTerm' }, mapping the Apex method’s parameter to the LWC’s reactive searchTerm property., The $searchTerm syntax ensures reactivity, so the getAccounts method is re-invoked when searchTerm changes, aligning with LWC best practices., This matches the standard syntax outlined in the Salesforce Lightning Web Components Developer Guide for wiring Apex methods with parameters., Example for Clarity:, Here’s how option A would be used in a complete LWC JavaScript file:, javascript, Copy, import { LightningElement, wire } from 'lwc';, import getAccounts from '@salesforce/apex/AccountController.getAccounts';, , export default class MyComponent extends LightningElement {, searchTerm = ''; // Reactive property for search term, , // Wire the getAccounts Apex method to a property, @wire(getAccounts, { searchTerm: '$searchTerm' }), accounts;, , // Example: Update searchTerm based on user input, handleSearchTermChange(event) {, this.searchTerm = event.target.value;, }, }, Apex Controller (for reference):, apex, Copy, public with sharing class AccountController {, @AuraEnabled(cacheable=true), public static List getAccounts(String searchTerm) {, return [SELECT Id, Name FROM Account WHERE Name LIKE :('%' + searchTerm + '%')];, }, }, Behavior: When searchTerm changes (e.g., due to user input), the @wire decorator re-invokes getAccounts with the new searchTerm value, and the accounts property receives the result (e.g., { data: [/* Account records */], error: undefined })., Handling Typos:, The options are syntactically correct in the provided image, with no typos to address. However, the options assume getAccounts is properly imported and defined in the Apex controller, which we infer based on the question’s context., The question’s phrasing is clear, and the options align with typical LWC syntax patterns., References:, Salesforce Lightning Web Components Developer Guide: , “Call Apex Methods” section: Details the use of @wire to call Apex methods, including parameter passing., “Pass Parameters to Apex Methods” section: Explains the { param: '$property' } syntax for reactive parameters., “Reactive Properties” section: Clarifies the role of @track (and why it’s not applicable here).(Available at: https://developer.salesforce.com/docs/component-library/documentation/en/lwc/), Salesforce Apex Developer Guide: , “AuraEnabled Annotation” section: Describes requirements for Apex methods to be callable from LWC (@AuraEnabled(cacheable=true)).(Available at: https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/), Platform Developer I Study Guide: , Section on “User Interface”: Covers building LWCs, including wiring Apex methods and handling reactivity.(Available at: https://trailhead.salesforce.com/en/content/learn/modules/platform-developer-i-certification-study-guide), , ]

Questions 33

A developer wrote Apex code that calls out to an external system using REST API.

How should a developer write the test to prove the code is working as intended?

Options:

Write a class that implements HTTPcalloutMock.

Write a class that extends webserviceloo.

Write a class that implements webservicemock.

Write a class that extends HTTPcalloutMock.

Questions 34

A developer created a new after insert trigger on the Lead object that creates Task records for each Lead.

After deploying to production, an existing outside integration that inserts Lead records in batches to Salesforce is occasionally reporting total batch failures being caused by the Task insert statement. This causes the integration process in the outside system to stop, requiring a manual restart.

Which change should the developer make to allow the integration to continue when some records in a batch cause failures due to the Task

insert statement, so that manual restarts are not needed?

Options:

Use the Database method with allow one set to false.

Deactivate the trigger before the integration runs.

Remove the Apex class from the integration user's profile.

Use a try-catch block after the insert statement.

Questions 35

A developer is integrating with a legacy on-premise SQL database.

What should the developer use to ensure the data being integrated is matched to the right records in Salesforce?

Options:

External Object

External ID field

Formula field

Lookup field

Questions 36

A Salesforce administrator used Flow Builder to create a flow named "accountOnboarding". The flow must be used inside an Aura component.

Which tag should a developer use to display the flow in the component?

Options:

lightning: flow

lightning-low

sure-flow

aura: flow

Questions 37

A developer needs to have records with specific field values in order to test a new Apex class.

What should the developer do to ensure the data is available to the test?

Options:

Use SOQL to query the org for the required data.

Use Test.loadData() and reference a CSV file in a static resource.

Use Anonymous Apex to create the required data.

Use Test. loadData() and reference a JSON file in Documents.

Questions 38

Provide question feedback here (optional):

CRT-450 Question 38

Based on this code, what is the value of x?

Options:

Questions 39

Which code in a Visualforce page and/or controller might present a security vulnerability?

Options:

<apex:outputText value="{!SCurrentPage.parameters.userInput}" />

<apex:outputText escape="false" value="{!sCurrentPage.parameters.userInput}" />

<apex:outputField value="{!ctrl.userInput}" rendered="{!isEditable}" />

<apex:outputField value="{!ctrl.userInput}" />

Answer:

Explanation:

Comprehensive and Detailed Explanation From Exact Extract:

To determine which Visualforce code snippet presents a security vulnerability, we need to evaluate each option for potential risks, such as cross-site scripting (XSS), based on Salesforce’s Visualforce security best practices. XSS vulnerabilities occur when user input is rendered on a page without proper sanitization, allowing malicious scripts to execute. Let’s analyze each option systematically, referencing Salesforce’s official documentation, particularly the Visualforce Developer Guide and Secure Coding Guidelines.

Understanding Visualforce Security:

Visualforce Components: Components like and <apex:outputField> are used to display data on a Visualforce page. Their behavior regarding HTML escaping (sanitizing output to prevent script injection) is critical to security.

XSS Vulnerability: XSS occurs when untrusted user input (e.g., from URL parameters or controller variables) is rendered as HTML without escaping special characters (e.g., <, >, &). The Visualforce Developer Guide states: “To prevent XSS, Visualforce automatically escapes output unless explicitly disabled, but developers must be cautious with user input” (Salesforce Visualforce Developer Guide, Secure Coding for Visualforce).

Key Security Features:

<apex:outputText>: By default, escapes HTML characters unless escape="false" is set.

<apex:outputField>: Automatically escapes output and is designed for bound fields, reducing XSS risk.

User input (e.g., ApexPages.currentPage().getParameters()) must be sanitized to prevent injection of scripts like <script>alert('hack');</script>.

Evaluating the Options:

A. <apex:outputText value="{!ApexPages.currentPage().getParameters().get('userInput')}" />

Component: Uses <apex:outputText> to display a URL parameter (userInput) accessed via ApexPages.currentPage().getParameters().get('userInput').

Escaping: The escape attribute is not specified, so <apex:outputText> defaults to escape="true". The Visualforce Developer Guide confirms: “The apex:outputText component escapes HTML characters by default, converting characters like < to < to prevent script execution” (Salesforce Visualforce Developer Guide, apex:outputText).

Security: Even though userInput is untrusted (coming from a URL parameter), the default escaping ensures that any malicious content (e.g., <script>alert('hack');</script>) is rendered as plain text (e.g., <script>alert('hack');</script>), preventing XSS.

Conclusion: Safe, as default escaping mitigates XSS risks.

Note on Typo: The question likely contains a typo in “SCurrentPage” (should be ApexPages.currentPage()). For analysis, we assume the correct syntax, as the intent is clear.

B. <apex:outputText escape="false" value="{!ApexPages.currentPage().getParameters().get('userInput')}" />

Component: Uses <apex:outputText> to display the userInput URL parameter.

Escaping: Explicitly sets escape="false", disabling HTML escaping. The Visualforce Developer Guide warns: “Setting escape=’false’ on apex:outputText allows unescaped output, which can lead to XSS vulnerabilities if the data is not sanitized” (Salesforce Visualforce Developer Guide, Secure Coding for Visualforce).

Security: With escape="false", any malicious input in userInput (e.g., <script>alert('hack');</script>) is rendered as executable HTML, enabling XSS. For example, a URL like ?userInput=<script>alert('hack');</script> would execute the script in the user’s browser. The Salesforce Secure Coding Guidelines explicitly state: “Avoid setting escape=’false’ on apex:outputText when rendering untrusted input, such as URL parameters” (Salesforce Secure Coding Guidelines, Cross-Site Scripting).

Conclusion: Presents a security vulnerability (XSS) due to disabled escaping with untrusted input.

Note on Typo: The question has a typo in “sCurrentPage” (should be ApexPages.currentPage()). We assume the correct syntax for analysis.

C. <apex:outputField value="{!ctrl.userInput}" rendered="{!isEditable}" />

Component: Uses <apex:outputField> to display a controller variable (ctrl.userInput), with a rendered attribute based on isEditable.

Escaping: <apex:outputField> is designed to display field values from sObjects and automatically escapes output to prevent XSS. The Visualforce Developer Guide states: “The apex:outputField component renders field data with automatic HTML escaping, ensuring safe output” (Salesforce Visualforce Developer Guide, apex:outputField). Even if ctrl.userInput contains malicious content, it’s rendered as plain text.

Security: The value attribute expects a field reference (e.g., {!object.FieldName}), but here it’s bound to a controller variable (ctrl.userInput). This is unconventional, as <apex:outputField> is typically used for sObject fields. However, even if ctrl.userInput is untrusted, the automatic escaping prevents XSS. The rendered attribute (isEditable) controls visibility and does not affect escaping.

Conclusion: Safe, as <apex:outputField> escapes output, though the usage is atypical.

Note on Typo: The question has a typo in the value attribute: “(!ctrl.userinput)” should be {!ctrl.userInput} (curly braces instead of parentheses), and “isfditable” should be isEditable. We assume the corrected syntax: <apex:outputField value="{!ctrl.userInput}" rendered="{!isEditable}" />.

D. <apex:outputField value="{!ctrl.userInput}" />

Component: Uses <apex:outputField> to display a controller variable (ctrl.userInput).

Escaping: As with option C, <apex:outputField> automatically escapes output, preventing XSS. The Visualforce Developer Guide confirms: “apex:outputField ensures safe rendering by escaping special characters” (Salesforce Visualforce Developer Guide, apex:outputField).

Security: Even if ctrl.userInput contains malicious content, it’s rendered as plain text, mitigating XSS risks. Like option C, using <apex:outputField> for a controller variable is unusual, but it does not introduce a vulnerability.

Conclusion: Safe, as <apex:outputField> escapes output.

Note on Typo: The question has a typo in the value attribute: “{'ctrl.userInput}” should be {!ctrl.userInput} (correct merge field syntax). We assume the corrected syntax: <apex:outputField value="{!ctrl.userInput}" />.

Why Option B is Correct:

Option B presents a security vulnerability because:

It uses <apex:outputText> with escape="false", disabling HTML escaping.

It renders untrusted user input (ApexPages.currentPage().getParameters().get('userInput')) directly, allowing malicious scripts to execute, which is a classic XSS vulnerability.

The Salesforce Secure Coding Guidelines explicitly warn against this practice: “Rendering unescaped user input, such as URL parameters, can allow attackers to inject scripts” (Salesforce Secure Coding Guidelines, Cross-Site Scripting).

The other options (A, C, D) either use default escaping (<apex:outputText> in A) or inherently safe components (<apex:outputField> in C and D), preventing XSS.

Handling Typos:

The question contains several typos, which were corrected for analysis:

Option A: “SCurrentPage” → ApexPages.currentPage().

Option B: “sCurrentPage” → ApexPages.currentPage().

Option C: “(!ctrl.userinput)” → {!ctrl.userInput}, “isfditable” → isEditable.

Option D: “{'ctrl.userInput}” → {!ctrl.userInput}.These corrections align with standard Visualforce and Apex syntax, ensuring the analysis reflects the intended functionality.

Example of the Vulnerability (Option B):

Consider a Visualforce page with option B’s code:

<apex:page>

<apex:outputText escape="false" value="{!ApexPages.currentPage().getParameters().get('userInput')}" />

</apex:page>

If a user accesses the page with a URL like:

<a href="https://example.salesforce.com/apex/MyPage?userInput=">https://example.salesforce.com/apex/MyPage?userInput= <script>alert('Hacked!');</script>

The script <script>alert('Hacked!');</script> is rendered as executable HTML, displaying an alert in the user’s browser, demonstrating an XSS attack. In contrast, option A (with default escaping) would render the script as plain text, preventing execution.

Mitigating the Vulnerability:

To fix option B, either:

Remove escape="false" to enable default escaping:

<apex:outputText value="{!ApexPages.currentPage().getParameters().get('userInput')}" />

Sanitize the input in the controller using methods like String.escapeHtml4():

public String getUserInput() {

String input = ApexPages.currentPage().getParameters().get('userInput');

return input != null ? String.escapeHtml4(input) : '';

}

<apex:outputText value="{!userInput}" />

The Visualforce Developer Guide recommends: “Sanitize untrusted input or rely on Visualforce’s built-in escaping to prevent XSS” (Salesforce Visualforce Developer Guide, Secure Coding for Visualforce).

[References:, Salesforce Visualforce Developer Guide: , “apex:outputText” section: Details default escaping and the escape attribute’s impact., “apex:outputField” section: Confirms automatic escaping for field output., “Secure Coding for Visualforce” section: Explains XSS prevention and best practices.(Available at: https://developer.salesforce.com/docs/atlas.en-us.pages.meta/pages/), Salesforce Secure Coding Guidelines: , “Cross-Site Scripting (XSS)” section: Warns against rendering unescaped user input and disabling escaping.(Available at: https://developer.salesforce.com/docs/atlas.en-us.secure_coding_guide.meta/secure_coding_guide/), Salesforce Apex Developer Guide: , “ApexPages Class” section: Describes ApexPages.currentPage().getParameters() for accessing URL parameters.(Available at: https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/), Platform Developer I Study Guide: , Section on “Salesforce Platform and Declarative Features”: Emphasizes secure Visualforce development and XSS prevention.(Available at: https://trailhead.salesforce.com/en/content/learn/modules/platform-developer-i-certification-study-guide), , , ]

Questions 40

A developer must provide custom user interfaces when users edit a Contact in either Salesforce Classic or Lightning Experience.

What should the developer use to override the Contact's Edit button and provide this functionality?

Options:

A Lightning component in Salesforce Classic and a Lightning component in Lightning Experience

A Lightning page in Salesforce Classic and a Visualforce page in Lightning Experience

A Visualforce page in Salesforce Classic and a Lightning page in Lightning Experience

A Visualforce page in Salesforce Classic and a Lightning component in Lightning Experience

Exam Code: CRT-450

Certification Provider: Salesforce

Exam Name: Salesforce Certified Platform Developer I (SP25)

Last Update: Jul 7, 2025

Questions: 204

How to Pass CRT-450 Exams

PDF + Testing Engine
~~$164.99~~ $66 Add to Cart

Testing Engine
~~$124.99~~ $50 Add to Cart

PDF (Q&A)
~~$104.99~~ $42 Add to Cart

Salesforce Related Exams

CPQ-201 - Salesforce CPQ Admin Essentials for New Administrators

CRT-261 - Salesforce Certified Service cloud consultant (SP25)

PDT-101 - Essentials of Pardot for Digital Marketers

Marketing-Cloud-Personalization - Marketing Cloud Personalization Accredited Professional Exam (SP25)

MuleSoft-Integration-Associate - Salesforce Certified MuleSoft Integration Associate (SP25) Exam

Marketing-Cloud-Advanced-Cross-Channel - SalesforceMarketing Cloud Advanced Cross ChannelExam

Salesforce-Marketing-Associate - Salesforce Certified Marketing AssociateExam

ADM-211 - Administration Essentials for Experienced Admin

Tableau-CRM-and-Einstein-Discovery-Consultant - Salesforce Tableau CRM Einstein Discovery Consultant (SP25)

Agentforce-Specialist - Salesforce Certified Agentforce Specialist

Service-Cloud-Consultant - Salesforce Certified Service cloud consultant (SP25)

Media-Cloud-Consultant - Salesforce Media Cloud Consultant Exam

CRT-402 - Certification Preparation for Platform App Builder (SP25)

OmniStudio-Developer - Salesforce Certified OmniStudio Developer (WI24)

Salesforce-Contact-Center - Salesforce Contact Center Accredited Professional Exam

Get Salesforce Full Access

Salesforce Free Exams
Examstrack provides free Salesforce exam prep materials and practice tests to support your Salesforce certification goals.

Summer Special 60% Discount Offer - Ends in 0d 00h 00m 00s - Coupon code: bestdeal

Navigation:

examstrack logo

Hot Vendors:

Free Salesforce CRT-450 Practice Exam with Questions & Answers | Set: 4

How to Pass CRT-450 Exams

Salesforce Related Exams

Salesforce Free Exams