Platform-App-Builder Salesforce Certified Platform App Builder (WI24) Questions and Answers

The two considerations that should be made are: The Star records are all required to have an existing value in their Galaxy field. This is a prerequisite for converting a lookup relationship to a master-detail relationship. A lookup relationship is an optional relationship that links two objects together, but does not enforce referential integrity or cascade delete. A master-detail relationship is a required relationship that links two objects together and enforces referential integrity and cascade delete. Toconvert a lookup relationship to a master-detail relationship, all child records must have a value in their lookup field that references an existing parent record. The Galaxy object has fewer than two existing master-detail relationships. This is another prerequisite for converting a lookup relationship to a master-detail relationship. An object can have up to two master-detail relationships with other objects and can act as both the parent and child in different relationships. To convert a lookup relationship to a master-detail relationship, the parent object must have fewer than two existing master-detail relationships with other objects. The Galaxy object is required to contain existing roll-up summary fields is not a valid consideration, as it is not related to converting a lookup relationship to a master-detail relationship. 

The Account record includes Invoice roll-up summary fields. This is correct because roll-up summary fields are only available on the master object in a master-detail relationship, and changing the field type to lookup would delete the roll-up summary fields

The three Salesforce functionalities that are ignored when processing field updates in workflow rules and approval processes are:

• Field-Level Security: This means that the field update will occur regardless of the user’s profile or permission set settings that determine whether they can see or edit the field1.
• Validation Rules: This means that the field update will bypass any validation rules that might otherwise prevent the record from being saved1.
• Decimal places and character limits: This means that the field update will round or truncate the value to fit the field’s format, without throwing an error

 The two considerations that an app builder should keep in mind during the deployment process using change sets are: Change sets do not include all components and may have to perform some changes manually. Change sets are a way to deploy metadata changes from one Salesforce org to another, but they do not support all types of components, such as reports, dashboards, email templates, etc. The app builder may have to use other methods, such as unmanaged packages or manual configuration, to deploy these components. Users should be logged out of production when receiving inbound change sets. This is a best practice to avoid any errors or conflicts that may occur when deploying changes to production. Users may be working on records or components that are being updated by the change set, which may cause data loss or inconsistency. Salesforce Connect does not automatically establish a link between environments. Salesforce Connect is a feature that allows users to access data from external sources without storing it in Salesforce. It does not have anything to do with deploying changes between Salesforce orgs. Transactions will not revert if the deployment errors. Transactions are units of work that are either completed entirely or not at all. If a deployment error occurs during a transaction, the transaction will be rolled back and no changes will be made to the target org. However, this does not mean that the source org will revert to its previous state before the deployment.

 NOT(ISBLANK(Job_Accepted__c)) && ISCHANGED(Hire_Date__c) is the validation formula that the app builder should use to meet the requirement of preventing changes to Hire Date after Job Accepted isentered. This formula will return TRUE if Job Accepted is not blank and Hire Date is changed, which will display an error message and prevent saving the record. The other formulas are not correct or valid.

Polls and Out of Office are two ways that CK can use Chatter to gather feedback and understand availability. Polls allow users to create surveys and collect opinions from other users. Out of Office lets users set a status message and an end date to inform others when they are away or busy. Streams and Topics are not related to the problem.

• Roll-up summary fields can be used to count the number of related open cases for an account, including those from parent accounts if the relationship allows roll-up summaries.References:
• [Salesforce Help - Roll-up Summary Fields](https://help.salesforce.com/s/articleView?id=sf.fields_about_roll_upup_summary_fields.htm&type=5)

A cross-object formula field is a formula field that references fields from another object. This can be used to display the value of the Account_Region__c field on Opportunities, as long as there is a relationship between the two objects. Option A, B, and C are not relevant for this requirement.

Schema Builder is a tool that presents a comprehensive view of all relationships in one place. It allows app builders to see how objects are connected and create new relationships. Lightning Object Creator, Object Manager, and Lightning Record Page are not tools for viewing relationships, but for creating objects, managing fields, and customizing record pages respectively.

Standard buttons can be overridden with a Visualforce page to provide custom functionality or user interface. For example, you can override the New button on an object to display a custom Visualforce page instead of the standard page layout3. Standard buttons that are not available for overrides can still be hidden on page layouts to prevent users from accessing them. For example, you can hide the Delete button on an object to prevent users from deleting records

The app builder should select Enhanced List for the Related List type for the Related List Lightning component. Enhanced List allows users to see ten fields and sort and wrap text on their Related Lists. Option B is incorrect because Basic List only allows users to see four fields and does not support sorting or wrapping text on their Related Lists. Option C is incorrect because ListView does not show Related Lists on record pages, but rather shows list views on object home pages or tabs. Option D is incorrect because List Class is not a valid Related List type.

The app builder should provision a Partial Data sandbox to the developer. A Partial Data sandbox can have up to 5 GB of data, which meets the requirement of having at least half a gigabyte of data. A Partial Data sandbox can also be refreshed every 5 days, which meets the requirement of refreshing after each three-day sprint. Option A is incorrect because a Developer sandbox can only have up to 200 MB of data, which does not meet the requirement. Option B is incorrect because a Full Copy sandbox can only be refreshed every 29 days, which does not meet the requirement. Option C is incorrect because a Developer Pro sandbox can only have up to 1 GB of data, which may not be enough for the requirement.

 The two recommended solutions for the app builder to give the users appropriate access are creating a criteria based sharing rule to all opportunities with the sales operations public group and adding a permission set with ‘View All" and ‘Modify All’’ opportunity permissions enabled. A criteria based sharing rule can grant read and write access to all opportunities that meet certain criteria to a specified group of users. A permission set can grant additional object-level permissions to users without changing their profiles. Option B is incorrect because adding a manual share for all opportunities with each user on the sales operations team is not scalable or maintainable. Option D is incorrect because creating a criteria-based sharing rule to share all opportunities with the sales operations private group is redundant, as private groups are used to manually share records with individual users or other groups.

The app builder should use two tools to automate this process:

• Process Builder: This is a type of automation tool that can execute actions based on certain criteria. In this case, the process builder can have a criteria that evaluates if an opportunity goes to the closed won stage, and then execute an action that posts a message to a Chatter group.
• Workflow: This is another type of automation tool that can execute actions based on certain criteria. In this case, the workflow can have a criteria that evaluates if an opportunity goes to the closed won stage, and then execute an action that posts a message to a Chatter group. Option A and C are not tools that can automate this process.

 The two features of Chatter that would meet CK’s business needs are: Set up new public Chatter groups. A public Chatter group is a way to create a collaborative space for users to share information, files, polls, and ideas around a common topic or interest. A public Chatter group can be joined by any user in the organization and can be seen by anyone who has access to Chatter. By setting up new public Chatter groups, CK can enable users to socialize and collaborate around customer accounts and discuss various topics. Use post action on the Account object. A post action is a type of quick action that allows users to create a post on a record’s feed or on their own feed. A post can include text, mentions, hashtags, topics, links, files, or images. By using post action on the Account object, CK can enable users to share updates, feedback, or questions about customer accounts and engage with other users who follow the accounts. Set up new private Chatter groups is not a valid feature, as it does not meet CK’s business needs. A private Chatter group is a way to create a collaborative space for users to share information, files, polls, and ideas around a confidential or sensitive topic or interest. A private Chatter group can only be joined by invitation and can only be seen by the group members. By setting up new private Chatter groups, CK would limit the visibility and accessibility of the conversations around customer accounts. Use Chatter actions to create tasks to complete is not a valid feature, as it does not meet CK’s business needs. A Chatter action is a type of quick action that allows users to create a task from a record’s feed or from their own feed. A task can include subject, due date, priority, status, assigned to, etc. By using Chatter actions to create tasks to complete, CK would enable users to track and manage their work related to customer accounts, but not to socialize and collaborate with other users.

The app builder should use Data Loader to quickly insert a list of over 60,000 net new Accounts. Data Loader is a tool that allows users to insert, update, delete, or export large amounts of data from Salesforce using CSV files or database connections. Data Loader can handle up to 5 million records at a time and supports features such as bulk API, batch operations, mapping files, etc. Data Loader is ideal for loading large data sets into Salesforce quickly and efficiently. Lightning Object Creator is not a valid tool, as it cannot insert data into existing objects. Lightning Object Creator is a tool that allows users to create custom objects from spreadsheet data by uploading a file and mapping columns to fields. It cannot load data into existing objects or handle more than 500 records at a time. ImportWizard is not a valid tool, as it cannot handle more than 50,000 records at a time. Import Wizard is a tool that allows users to insert, update, or delete data from Salesforce using CSV files or Excel files. Import Wizard supports standard objects and some custom objects and provides features such as field mapping, duplicate detection, data validation, etc. Import Wizard is ideal for loading small data sets into Salesforce with more control and accuracy.

• An update record action with a related record component on the Opportunity layout allows users to edit related Account records directly.References:
• Salesforce Help - Creating Quick Actions

Lightning Object Creator is a tool that allows app builders to create an object with fields and import data from a spreadsheet simultaneously. Import Wizard and Data Loader are tools for importing data into existing objects, not creating new objects. Schema Builder is a tool for creating and modifying objects and fields, but not importing data.

Create mobile navigation menus for both the sales and marketing profiles. This is correct because mobile navigation menus allow users to customize the items that appear in the navigation bar of the Salesforce mobile app, and they can be assigned to different profiles.

• A: Number fields and C: Text fields can be set as External IDs. These field types are suitable for housing unique identifiers from external systems.References:
• Salesforce Help - External ID Fields

The lead settings have an option to require validation for converted leads. If this option is unchecked, then the Account validation rules will not be enforced when a lead is converted to an Account. This could result in missing or incorrect information on the Account records

Roll-up summaries allow MAX, MIN, SUM, COUNT, and AVG functions on numeric fields from child records related by a master-detail relationship. Roll-up summaries are limited to master-detail relationships andcannot be used with lookup relationships. An object can have up to 40 roll-up summary fields, not 25. An object can have up to 25 relationship fields (master-detail or lookup), not 20.

The app builder should verify that there is an Apex test that provides test coverage for the Flow. An Apex test is a unit test that verifies the functionality and quality of Apex code. Apex tests are required to deploy any change that contains Apex code or references Apex code, such as an auto launched flow3. The app builder should ensure that there is an Apex test that covers at least 75% of the Flow logic before deploying it to production in an active state4. Option B, C, and D are not things that the app builder should take into consideration when planning the deployment.

The two options that the app builder should avoid to prevent recursion are setting a criteria node to No criteria-just execute the procedure and invocable processes. Setting a criteria node to No criteria-just execute the procedure means that the process will always execute the actions regardless of the record values, which can cause recursion if the process updates the same record that triggered it. Invocable processes are processes that can be invoked from another process or a flow, which can cause recursion if the invocable process updates the same record that triggered the parent process or flow. Option A is incorrect because IF statements are not an option in Process Builder, but rather a function that can be used in formulas or conditions. Option D is incorrect because the ISCHANGED function is not an option in Process Builder, but rather a function that can be used in formulas or conditions to check if a field value has changed.

 It will fail if there is a feature only available in the next version. According to the Salesforce documentation, “If your sandbox is on a newer version than your production org, you can’t deploy any components that are new in the sandbox version.” The change set components will not be upgraded to the next version in production, the change set will not be automatically deployed when production is upgraded, and the deployment is possible if there are no new features involved.

 The lookup relationship will need to be converted to a master-detail relationship before a roll-up summary field can be created. This is correct because roll-up summary fields are only available on the master object in a master-detail relationship, and a lookup relationship does not establish a parent-child hierarchy between the objects

• The deployed permission set will merge with the existing permission set in production, meaning changes made in the sandbox will be added to the existing permission set after deployment.References:
• Salesforce Help - Permission Sets

The app builder should consider two things before overriding standard buttons:

• Standard buttons can be overridden with a Visualforce page. A Visualforce page is a web page that displays custom user interface elements using Visualforce markup and Apex code. A Visualforce page can be used to override a standard button and provide custom functionality or logic3.
• Standard buttons that are not available for overrides can still be hidden on page layouts. A page layout is a layout that determines how fields, related lists, and buttons are arranged on a record detail or edit page. A page layout can be used to hide a standard button that cannot be overridden by removing it from the layout4. Option A and D are not things that the app builder should consider before overriding standard buttons.

A master-detail relationship between two objects automatically creates a report type that includes both objects. The app builder does not need to create a custom report type for this scenario. The report type will have the format of Parent object with Child object

Workflow rule and an outbound message or Process Builder and Apex Code are two ways to integrate Salesforce with an external web service. Workflow rule can define criteria and actions for triggering an outbound message, which is an XML message sent to a designated endpoint URL. Process Builder can invoke Apex Code, which is a programming language that can make callouts to external web services using HTTP requests. Flow Builder and an outbound message or Process Builder and an outbound message are not possible combinations.

The two steps that should be suggested to meet these requirements are to select insert null values in settings and to use Data Loader to update leads using the CSV file. Selecting insert null values in settings will allow Data Loader to overwrite existing values with null values. Data Loader is a tool that can import, export, update, or delete large amounts of data.

The validation rule should check if the user role is not Marketing, and if the Retail Opt In field has been changed to Yes. The ISCHANGED function returns true if the field value has been changed, and the ISPICKVAL function returns true if the field value matches a specified picklist value. 

To insert a list of 25,000 records using deduplication for the Race_Track__c custom object, an app builder should use Data Loader. Data Loader is a tool that allows users to insert, update, delete, or export large amounts of data in Salesforce. Data Loader can also perform deduplication by matching records based on external ID fields or Salesforce record IDs. [Source]

The app builder should use the Path feature to provide the functionality that the VP of Sales wants. The Path feature allows an app builder to create a visual representation of the stages in a business process, such as the Opportunity sales process. The app builder can also add key fields, guidance, and resources for each stage to help sales reps gather information and complete tasks4. Option A, C, and D are not features that can provide this functionality.

The import wizard only allows values to be imported into a dependent picklist if they match the appropriate controlling field. This ensures data integrity and prevents invalid values from being imported. Custom picklist fields can be either controlling or dependent fields. This allows the app builder to create custom dependencies between custom picklists. Checkbox fields can be controlling fields but not dependent fields. This allows the app builder to create dependencies based on checkbox values, such as true or false. Multi-select picklist fields can be dependent picklist fields but not controlling fields. This allows the app builder to create dependencies based on multiple values selected in a multi-select picklist field. Standard and custom picklist fields can be dependent fields, but not all standard picklist fields can be controlling fields. Some standard picklist fields, such as Lead Status or Opportunity Stage, cannot be controlling fields because they are used in other processes, such as lead conversion or sales path

Public group is the best option to route the approval request for overnight shipments. Public groups can include users, roles, or other groups. Queues are used to assign ownership of records to a group of users, not for approval processes. Hierarchy field and role are not flexible enough to include only the department members.

The setting for the visibility of custom tabs is default off for all users when they are deployed via change sets without including the profile settings or permission sets. This means that the custom tabs are not visible in any apps or navigation menus for any users unless they are manually added by each user or by an administrator3. Option B, C, and D are not correct settings for the visibility of custom tabs.

Configuring a validation rule to require a field for a specific record type is the best way to ensure that important fields are entered and formatted correctly. Updating the important fields to be required on the page layout will not prevent users from entering invalid data using other methods, such as data loader or quick actions. Making a formula field to check the format of the important fields will not prevent users from entering invalid data, but only display a message or an indicator. Creating a workflow rule to check the fields are formatted correctly will not prevent users from entering invalid data, but only trigger an action after the data is saved.

Set up a delegated approver for the manager is the recommended solution to ensure all of the appropriate deals are reviewed and the leaderboard is up to date. According to the Salesforce documentation, “A delegated approver can approve records that are submitted for approval by users below them in the role hierarchy.” Forwarding the approval request to the manager’s assistant, having the manager log on and reassign the approval request, and using Process Builder to assign a delegated approver are not valid or feasible options.

Create a Chatter stream. This is correct because a Chatter stream allows users to follow multiple records and people in one feed, and filter the feed by selecting a stream.

A flow is an application that automates a business process by collecting data and performing operations in your org or an external system. Flows can also manipulate data in your org by creating, updating, deleting, or submitting records for approval. You can use flows to update fields on related records when a certain event occurs, such as closing a work order. In this case, a flow can be used to update the last maintenance date field on the Asset record when a maintenance work order gets closed.

The best practice that the app builder should follow when building out automation is one record change process per object. A record change process is a type of process in Process Builder that starts when a record is created or updated. Having one record change process per object can avoid conflicts or errors when multiple processes try to update the same record at the same time. Option A is incorrect because one workflow rule per object is not a best practice, as workflow rules are considered legacy tools and have limitations compared to Process Builder. Option B is incorrect because one flow per object is not a best practice, as flows are more complex and require more resources than processes. Option C is incorrect because one invocable process per object is not a best practice, as invocable processes are used to invoke other processes from within a process or a flow.

Schema Builder is a tool that allows app builders to view and modify the data model of their Salesforce org. Some of the capabilities of Schema Builder are:

• Creating and editing custom objects and fields
• Creating and editing relationships between objects
• Showing selected objects on a page
• Editing custom settings

Schema Builder cannot be used to create a new record type or view page layouts in a new window.

The best way to calculate an overdue date that is two months after a task due date is to use a formula field with the ADDMONTHS() function. This function adds a specified number of months to a date value, and returns a new date value. See [this article] for more information on formula fields.

• Creating both customer and dealer as accounts, adding each rep as a contact on the corresponding account, and creating an account hierarchy provides a clear organizational structure and relationship between the entities.References:
• Salesforce Help - Account Hierarchies

The validation rule should be AND(ISNEW(), ISBLANK(Lead.Owner:User.Id)). This rule will prevent saving a new lead record if the owner is not a user. This will ensure that campaign members have a sales owner. Option A is incorrect because it will prevent saving any lead record if the owner is blank, which is not the requirement. Option B is incorrect because it will prevent saving an existing lead record if the owner is a queue, which is not the requirement. Option D is incorrect because it will prevent saving any lead record if the owner is a queue, which is not the requirement.

Historical data will be updated to 12:00 timestamp when changing a Date field to Date/Time field. According to the Salesforce documentation, “When you convert a Date field to Date/Time, Salesforce appends “12:00” to existing data in your records.” The change will not be instant, but will require some time for processing. The field name will not change unless specified by the app builder. Data loss will not be experienced, but data accuracy might be affected.

 Create a validation rule on the Account object is how the app builder can keep accounts with open opportunities from being deleted. According to the Salesforce documentation, “Validation rules verify that data entered by users in records meet the standards you specify before they can save it.” A validation rule can check if an account has any open opportunities and display an error message if someone tries to delete it. Create an Apex trigger on the Account object, remove the delete button onthe account layout, and remove the Delete permission from the Sales Rep profile are not valid or sufficient solutions for this requirement.

 A validation rule is a formula that evaluates the data in one or more fields and returns a value of “True” or “False”. Validation rules verify that the data a user enters in a record meets the standards you specify before the user can save the record. In this case, a validation rule can be used to check if the Expected_Close_Date_c field is populated before the Opportunity stage is set to qualified

The requirement can be met by using a combination of process builder and approval process. The process builder can be used to trigger the approval process when the close date is delayed by more than 60 days. The approval process can be configured to require unanimous approval from the manager and VP of sales.

The Owner field on the Master record determines the ownership and sharing access of the detail record in a master-detail relationship. According to the Salesforce documentation, “The detail record inherits the sharing and security settings of its master record.” The default owner is not set in the parent object’s settings, the Owner field on the Detail record does not exist, and the owner is not set independently on the detail object’s settings.

The app builder should create a master-detail relationship field on the gift card object to support the requirement. A master-detail relationship field creates a parent-child relationship between two objects, where the master record controls certain behaviors of the detail record. In this case, the Account object would be the master and the gift card object would be the detail. By creating a master-detail relationship field, the app builder can meet these requirements:

• Track the total number of gift cards opened and gift cards issued on an Account: This can be done by creating roll-up summary fields on the Account object that count or sum up the values from the gift card records related to each account.
• Permanently ensure the gift cards are unable to be moved across any other Account once it is created: This can be done by making the master-detail relationship field required on the gift card object, which means that every gift card record must be associated with an account record and cannot be changed once set. Option B, C, and D are not types of fields that can support this requirement.

To communicate to the CK web service when a shoe’s inventory has changed, an app builder should use an after-save record-triggered flow. An after-save record-triggered flow is a type of flow that runs after a record is saved and can perform actions such as updating related records, sending emails, calling external services, etc. An after-save record-triggered flow can use an Apex action to invoke a SOAP web service using a WSDL file. [Source]

To view a junction object record, a user must have at least read access to both master objects. This is because the junction object inherits the sharing and security settings from both master objects

• Creating a unique External ID field on the custom object and using Data Loader to upsert records prevents duplicates and ensures correct record updates by matching the unique ID.References:
• Salesforce Help - External ID

Escalation rules and Process Builder are two automation processes that can be used to send a notification when a case stays in the ‘’ new’’ status for more than four business hours. Escalation rules can define criteria and actions for escalating cases based on time or other factors. Process Builder can create a time-based action that triggers an email alert when the case status is ‘’ new’’ for more than four business hours. Flow Builder and Scheduled Apex are not necessary for this requirement.

 Partial Copy is the type of testing environment that the app builder should create to use a sandbox template for Accounts, Projects, and Project Milestones. According to the Salesforce documentation, “Partial Copy sandboxes copy your production org’s configuration (metadata) and some of your production org’s data as defined by a sandbox template.” Developer, Developer Pro, and Scratch Org are not types of testing environments that support sandbox templates.

Putting the SC in the role hierarchy above the technicians whose work orders they review will provide the required access, given a private data model. The role hierarchy determines how users can access records they do not own. Users at any given role level can view, edit, and report on all data owned by or shared with users below them in the role hierarchy.

LEFT(Account.Zip_Code_c, 5) is the correct formula to display only the first five digits of Zip Code from the parent Account. LEFT function returns the specified number of characters from the left side of a text string. Account.Zip_Code_c is the custom text field that stores the Zip Code on Account object. 5 is the number of characters to return from the left side of the Zip Code. The other options are not valid formulas or functions.

Changing the data type of a field used in an apex class from number to text will require the app builder to perform additional steps in order to retain existing functionalities. This is because changing the data type of a field may affect the apex code that references or manipulates the field value, and may cause compilation errors or unexpected results. The app builder will need to update the apex code to handle the new data type and ensure that the logic and calculations are still correct. Option B is incorrect because changing the data type of a field used in a report from a text to an encrypted field will not require additional steps, as encrypted fields can still be used in reports with some limitations. Option C is incorrect because changing the data type of a field used as an external id from number to text will not require additional steps, as external id fields can be either number or text. Option D is incorrect because changing the data type of a field used in lead conversion from number to text will not require additional steps, as lead conversion fields can be mapped regardless of their data types.

The email button item will not be visible on the Lightning record page if the page layout includes the case feed component or if the email button contains JavaScript. The case feed component replaces the standard buttons on the page layout with actions in the feed. The email button item will not work if it contains JavaScript because JavaScript buttons are not supported in Lightning Experience.

Feed Tracking is the Chatter feature that allows field value changes for certain fields to show up on Chatter. Thanks, Publisher Actions, and Topics are other Chatter features, but they do not relate to field value changes.

Approval process is the best way to automate travel requests based on internal policy. Approval process can define the steps, criteria, and actions for approving records. The app builder can create an approval process for travel requests that requires approval from managers or executives before they are submitted. Workflow rule, Process Builder, and Apex are not suitable for this requirement.

 Marking stage dependent fields as required on the Opportunity page layout is a good solution to improve efficiency and data quality, as it ensures that users enter the necessary information for each stage of the sales process. Adding a Path component with fields and instructions aligning to stages on the Opportunity is another good solution to improve efficiency and collaboration, as it provides guidance and best practices for users to move the Opportunity along the sales cycle. Using two Tabs components to separate record information from activities may not be an optimal solution, as it may reduce the visibility and accessibility of important data. Setting up an approval process requiring manager consent at each stage of the Opportunity may not be a feasible solution, as it may introduce unnecessary delays and complexity in the sales process

Apex unit test failures can cause a package installation to fail. According to the Salesforce documentation, “If your package contains Apex code, all tests must complete successfully for yourpackage to install.” Incorrect license types, package features not compatible, and object limits exceeded are not valid reasons for a package installation failure.

The feature that the app builder should use to allow users to create the opportunity is a quick action. A quick action is a type of custom button or link that can create or update records, log calls, send emails, or launch flows from a record page or a global menu. The app builder can create a quick action on the account object that creates an opportunity record with pre-populated fields. Option B is incorrect because a default action is not a valid term, but rather a standard action that appears on every record page by default, such as Edit or Delete. Option C is incorrect because a custom button is not suitable for this requirement, as custom buttons can only display a URL or execute JavaScript when clicked.Option D is incorrect because a custom link is not suitable for this requirement, as custom links can only display a URL or execute JavaScript when clicked.

The record will not save and the validation rule’s error message will be displayed because the field update will violate the validation rule. The validation rule will prevent the record from being saved if the Industry field is longer than 6 characters, and Technology is 10 characters long.

To show Component as a related list on Product, a lookup relationship on Component to Product should be created. A lookup relationship creates a loose association between two objects and allows users to relate records from one object to another. A lookup relationship also allows users to add the related list of the child object to the parent object’s page layout.

 Preexisting information will remain even if it was over 255 characters if the app builder tries to convert a preexisting long text area field to text area. However, users will not be able to edit or save records with more than 255 characters in that field until they reduce the number of characters. Preexisting information will not truncate, be lost, or cause an error message.

The Twitter component is a standard Lightning component that can be added to mobile view Lightning pages using the Lightning App Builder. It displays a contact’s Twitter profile and recent tweets

Schema Builder allows users to create custom objects, fields, and relationships using a drag-and-drop interface. However, one of the limitations of Schema Builder is that fields and relationships can be created, but they will be unable to add the fields to the page layout from the canvas. Users will need to go to the Lightning Object Manager or Setup to edit the page layout and add the fields.