Untitled Deck Flashcards

Question

UC has a requirement that an opportunity should have a field showing the value of its associated account's billing state. This value should not change after the opportunity has been created. Is there a recommended solution to configure this automated behavior? A. Formula field B. Apex C. Workflow D. Roll-up summary field

Answer 1

C, Apex. This is correct because Apex is a programming language that can perform complex logic and manipulate data in Salesforce. Apex can be used to create a trigger on the opportunity object that copies the value of the billing state from the related account record when the opportunity is created, and prevents it from being changed afterwards. The other options are not suitable for this requirement because they either cannot copy data from a related object (formula field, roll-up summary field) or cannot prevent data from being changed (workflow).

Answer 2

D, To create "with" or "without" reports on the new custom object, a custom report type is needed. A custom report type defines the relationship between one or more standard or custom objects for reporting purposes. It allows users to select which fields they want to display in their reports and filter by related objects.

Answer 3

C, To have automatic posts on a record whenever a travel request has been approved, feed tracking should be used. Feed tracking enables field updates to be displayed in the Chatter feed of a record or a user profile. Users can follow records or users to see updates in their own feed. Feed tracking can be enabled for standard or custom objects and selected fields.

Answer 4

C, To ensure that only the sales reps and their manager's executive can view the rep's evaluation record but the reps should not be able to view the executive comment field on their review, a private sharing model granting record access using hierarchy and field-level security should be used. A private sharing model means that only the owner of a record and users above them in the role hierarchy can view the record by default. Record access can be granted to other users using manual sharing, sharing rules, or Apex sharing. Field-level security controls which fields are visible or editable for different profiles or permission sets. Questions and Answers PDF 12/150

Answer 5

A, To start tracking how many shoe subscriptions have been sold for each shoe catalog, a roll-up summary field should be created. A roll-up summary field calculates values from related records on a master-detail relationship. It can count, sum, min, or max numeric values from child records on a parent record.

Answer 6

D, 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.

Answer 7

A, 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.

Answer 8

A, D, To calculate summaries from child objects of a standard object, an app builder should evaluate two considerations: An app builder is unable to change a look up to a master-detail relationship. A lookup relationship can only be converted to a master-detail relationship if the lookup field in all records contains a value. If some records have null values, then the conversion will fail. A value is required in all records of the lookup field prior to converting to a master-detail relationship. As mentioned above, a lookup field cannot have any null values before it can be converted to a master-detail relationship. Users will need to populate the lookup field with valid values for all records before attempting the conversion.

Answer 9

A, C, To display the actions on the Lightning record page, two components could be included on the layout: Highlights panel: The highlights panel displays key information and actions for a record based on the compact layout. Users can see and perform actions such as edit, clone, delete, follow, etc. from the highlights panel. [Source] Activities: The activities component displays tasks and events related to a record. Users can also create new tasks and events, log calls, send emails, and view past activities from this component.

Answer 10

A, If an employee attempts to edit the description field after submitting an opportunity for approval, they will be presented with a 'Record Lock' notification. This means that the record is locked for editing while it is in the approval process and only users with the "Modify All" permission or users above them in the role hierarchy can edit it. [Source]

Answer 11

D, Data is unable to be deployed with change sets. Change sets are used to deploy metadata components such as custom objects, fields, workflows, reports, etc. from one Salesforce org to another. However, change sets do not include any data or records from the source org. Users will need to use other tools such as Data Loader or Data Import Wizard to migrate data between orgs. [Source]

Answer 12

B, To connect Testimonial__c records with both the submitter's Contact record and Account record, an app builder should create a master-detail relationship from Testimonial__c to Account and a lookup relationship from Testimonial__c to Contact. A master-detail relationship creates a parent-child relationship between two objects and allows for roll-up summary fields, sharing settings, and cascading actions. A lookup relationship creates a loose association between two objects and allows users to relate records from one object to another. Source

Answer 13

C, To ensure that opportunities are submitted into the approval process when their close date is pushed more than 30 days, an app builder should use an automated process to submit the record for approval. An automated process can be created using tools such as Process Builder or Flow Builder, and it can define the criteria and actions for submitting a record for approval. [Source]

Answer 14

A, 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]

Answer 15

A, 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]

Answer 16

D, To provide a help guide to enable reps to easily get help where needed during the different sales processes, an app builder should recommend Path. Path is a component that displays the key fields and guidance for each stage of a sales process on an object's record page. Users can see where they are in the process, update the stage and fields, and access resources such as tips and links. [Source]

Answer 17

D, A record-triggered flow can be used to automate actions when a record is created or updated. In this case, a record-triggered flow can be configured to create a new opportunity and send an email to the contracts team when an opportunity is marked as closed won.

Answer 18

A, B, 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.

Answer 19

D, A flow is a powerful automation tool that can perform complex logic and data manipulation. A flow can be used to delete rejected quotes by using a record-triggered flow that runs when a quote is Questions and Answers PDF 20/150 updated, or by using a scheduled flow that runs at a specified time.

Answer 20

C, A roll-up summary field is a field that calculates values from related records. A roll-up summary field can be used to display the number of opportunities that are closed won with a close date within the last year on the account detail page by using a filter criteria on the field.

Answer 21

B, 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.

Answer 22

A, A summary report on the opportunity object should be created to add to the account page layout. A summary report groups rows of data by common values and allows users to create charts based on aggregate values. A summary report on the opportunity object can group opportunities by stage and display a chart of all related opportunities on the account detail page.

Answer 23

D, Process Builder is the best automation tool to complete this task. Process Builder can perform actions when a record is created or updated, and it can also schedule actions to execute at a later time. Process Builder can update a field, send an email, and call an outbound message as actions.

Answer 24

D, The formula that should be used to select the contact's preferred name for email communications is IF(NOT(BLANKVALUE(Nickname__c)),Nickname__c, FirstName). This formula checks if the Nickname__c field is blank or null, and if not, it returns the value of the Nickname__c field. Otherwise, it returns the value of the FirstName field.

Answer 25

C, D, 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.

Answer 26

B, C, The two reasons that could be preventing this relationship conversion are that there are already two Questions and Answers PDF 23/150 master-detail relationships on the Invoice Line Item and that Invoice Line Item records exist without having the Invoice lookup field populated. A custom object can have up to two master-detail relationships, so adding another one would exceed the limit. Also, a master-detail relationship requires that the detail records have a value in the master lookup field, so any records with a blank Invoice lookup field would prevent the conversion.

Answer 27

A, C, The two reasons to create an unmanaged package are to distribute open-source projects on the AppExchange and to deploy from a Developer Edition environment. An unmanaged package is a collection of components that can be installed in any Salesforce org but cannot be upgraded or controlled by the developer. An unmanaged package can be used to share open-source projects or to deploy components from a Developer Edition environment to another org.

Answer 28

B, The app builder should validate the inbound change set to ensure a smooth deployment to production. Validating an inbound change set allows the app builder to test whether the change set can be deployed without errors in the target org. Validating an inbound change set does not affect any data or metadata in the target org.

Answer 29

C, 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

Answer 30

D, Customers who are invited to Chatter groups can only interact with members of their groups. They cannot invite other members, @mention accounts, or request access to public groups

Answer 31

B, C, A flow or a process can be used to assign a permission set to new users. A flow can be triggered by a record change or an invocable action, while a process can launch a flow as an immediate or scheduled action

Answer 32

D, Sharing rules can be used to extend access to records owned by certain users or roles to other users or roles. In this case, a sharing rule can grant read-only or read/write access to sales-owned accounts to the marketing team

Answer 33

A, To configure a custom Lightning component for use in a record page, the app builder needs to edit a record page using the Lightning App Builder and drag the component onto the page. The Page Layout editor and the App Manager are not used for this purpose

Answer 34

C, A template for a new Lightning record page determines how the page is divided into regions. The template is responsive and will automatically adapt to the device being used to view the record page. The template can be changed after the initial save, and users do not need "View All Data" permissions for the object

Answer 35

B, C, Changing custom field types may result in data loss if the new field type is incompatible with the old one. For example, changing a text field to a number field may cause text values to be deleted. Field history tracking records value changes of 255 characters or less. If a rich text field value exceeds this limit, only the first 255 characters are tracked.

Answer 36

C, An indirect lookup relationship is a custom relationship between two objects that are linked by an external ID field. The external ID field must be a custom field on the parent object that has the "External ID" attribute enabled. The child object must be a standard or custom object that is on the detail side of a master-detail or lookup relationship.

Answer 37

C, Questions and Answers PDF 28/150 Workflows that cause each other to fire back and forth recursively can result in workflow limits errors. For example, if workflow A updates a field that triggers workflow B, and workflow B updates a field that triggers workflow A, this can create an infinite loop of workflows that exceed the maximum number of workflow time triggers per hour.

Answer 38

C, TEXT() is a formula function that converts a picklist value to text. This can be used to display the Type field from the parent object Galaxy on the child record Star. ISPICKVAL() is used to check if a picklist value is equal to a specified value. VALUE() is used to convert text that represents a number to a number. FIND() is used to locate one text string within another text string.

Answer 39

A, D, 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 and cannot be used with lookup relationships. An object can have up to 40 roll-up Questions and Answers PDF 29/150 summary fields, not 25. An object can have up to 25 relationship fields (master-detail or lookup), not 20.

Answer 40

A, C, 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.

Answer 41

C, A custom action on Account can be used to create additional accounts from a parent account record. A custom action can have predefined values for certain fields based on the parent record. A custom global action can be used to create records that do not have any relationship with other objects. A custom link on Account can be used to execute JavaScript or link to an external URL.

Answer 42

A, D, An external ID field can be a number field or a text field, but not a URL field or a phone field. A URL field is used to store web addresses and a phone field is used to store phone numbers. An external ID field is used to store unique identifiers from an external system and it can be used for upsert operations

Answer 43

A, The best way to implement this request is to create a Lightning Web Component that can fetch the real-time stock price from an external API and display it on the Account record page. Installing a solution from the AppExchange may not be feasible as it may not match the exact requirements or may have additional costs. Building a Flow that uses API calls may not be efficient as it may consume API limits and may not be able to update the stock price in real-time. Using a scheduled Apex job may not be suitable as it may not be able to run frequently enough to reflect the real-time stock price

Answer 44

B, The best type of sandbox for each team member to use is a developer sandbox. A developer sandbox is a copy of production that includes only the metadata, such as objects, fields, layouts, etc. It does not include any data, such as records or attachments. A developer sandbox is ideal for small projects that do not require data testing, such as developing new features or customizations. A developer sandbox has a storage limit of 200 MB and can be refreshed once per day. A developer sandbox is also cheaper than other types of sandboxes. A full sandbox is a copy of production that includes all the metadata and data. It is ideal for large projects that require data testing, such as performance testing or integration testing. A full sandbox has the same storage limit as production and can be refreshed every 29 days. A full sandbox is also the most expensive type of sandbox. A developer pro sandbox is similar to a developer sandbox, but it has a larger storage limit of 1 GB and can be refreshed every 5 days. It is ideal for projects that require some data testing, such as data migration or quality assurance testing. A partial sandbox is similar to a full sandbox, but it has a smaller storage Questions and Answers PDF 32/150 limit of 5 GB and can be refreshed every 5 days. It is ideal for projects that require selective data testing, such as user acceptance testing or staging testing

Answer 45

A, The best way to solve this problem is to filter components by device using Form Factor. Form Factor is an attribute that can be applied to components on a Lightning record page to control their visibility based on the device type, such as desktop, phone, or tablet. By using Form Factor, the app builder can hide some components that are not relevant for mobile users, such as charts or reports, and show only the components that are necessary for data entry, such as fields or actions. This way, the mobile users do not have to scroll through all the components and can enter data more easily. Reordering the fields may not solve the problem completely, as there may still be too many components on the page for mobile users. Updating the training documentation may not help either, as it does not address the root cause of the problem, which is the layout of the page. Deselecting the phone radio button on the Lightning record page assignment may not be desirable, as it will prevent mobile users from accessing the record page at all, which may affect their productivity and functionality.

Answer 46

A, D, Questions and Answers PDF 33/150 The two components that could be included on the layout to display the actions are the Highlights panel and the Path. The Highlights panel is a component that shows key information and actions for a record. It can display up to 10 actions from the Mobile & Lightning Actions section of the page layout. The Path is a component that shows the stages of a process, such as a sales process or a service process. It can display up to 5 actions from the Mobile & Lightning Actions section of the page layout. The Chatter and Activities components do not display actions from the Mobile & Lightning Actions section of the page layout. They display other types of actions, such as posting, commenting, liking, logging a call, creating a task, or sending an email.

Answer 47

A, C, 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

Answer 48

A, The correct validation rule formula to ensure that the Scheduled Ship Date field is properly filled out before setting the Opportunity to Closed Won is: OR(ISPICKVAL( StageName ,"Closed Won") && ( Scheduled_Ship_Date_cCloseDate)>14,ISBLANK(Scheduled_Ship_Date_c)) This formula checks two conditions: if the StageName is Closed Won and the Scheduled Ship Date is more than 14 days after the Close Date, or if the Scheduled Ship Date is blank. If either condition is true, the validation rule will fire and prevent saving the record. The other formulas are incorrect because they either use incorrect syntax (such as "=" instead of "," or missing parentheses) or incorrect logic (such as checking if the Scheduled Ship Date is less than 14 days after the Close Date)

Answer 49

A, The best solution to create a report to compare the number of support cases in each status and by priority is to use grouping. Grouping allows the app builder to summarize data by one or more fields, such as status and priority, and display them in rows and columns. Grouping also enables the app builder to use different chart types, such as stacked bar charts or matrix charts, to visualize the data. Bucket columns are not a suitable solution, as they are used to categorize data into predefined groups, such as high, medium, or low. Custom report types are not a suitable solution, as they are used to define the objects and fields available for a report, not how to display them. Filters are not a suitable solution, as they are used to limit the data shown in a report based on certain criteria, not how to compare them

Answer 50

A, The category that handles bug fixes and simple changes is minor. A minor release is a type of release that introduces small enhancements or fixes to existing functionality, such as correcting spelling errors or improving performance. A minor release usually has a low impact on users and does not require extensive testing or training. A patch release is a type of release that addresses critical issues or defects that affect the functionality or security of an application, such as fixing broken links or resolving vulnerabilities. A patch release usually has a high impact on users and requires immediate deployment. A major release is a type of release that introduces new functionality or features to an application, such as adding new objects or components or changing business processes. A major release usually has a high impact on users and requires extensive testing and training. A rollback is not a type of release, but an action that reverses a release that has been deployed to an environment, such as undoing changes or restoring previous versions. A rollback may be necessary if a release causes errors or issues that affect the functionality or performance of an application.

Answer 51

D, The functionality that should be used to set up packages is namespace. A namespace is a unique identifier that distinguishes one package from another and prevents naming conflicts with other packages or customizations. A namespace also allows developers to expose their code or components for use by other developers through APIs or web services. A description is not a functionality that should be used to set up packages, but a text field that provides information about the package contents or purpose. A description does not prevent conflicts with other packages or customizations. Allow sharing is not a functionality that should be used to set up packages, but a setting that controls whether users can share records owned by other users within their role hierarchy. Allow sharing does not prevent conflicts with other packages or customizations. Help setting is not a functionality that should be used to set up packages, but a setting that determines Questions and Answers PDF 36/150 whether users can access help documentation for standard Salesforce features or custom features within a package. Help setting does not prevent conflicts with other packages or customizations.

Answer 52

A, The best way to implement this requirement is to create a formula field on the Case object using the TEXT function. A formula field can display the value of another field from a related object, such as the Account object. The TEXT function can convert a picklist value into text, which can be displayed on the Case record. Creating a formula field on the Account object using the ISPICKVAL function is not a valid solution, as it does not show the value of Support Level on the Case record. The ISPICKVAL function is used to check if a picklist field has a certain value, not to display it. Creating a Process Builder and using a field update on the Case object is not an optimal solution, as it requires more configuration and maintenance than a formula field. A Process Builder may also introduce delays or errors in updating the field value. Creating a roll-up summary field using Support Level on the Account object is not a valid solution, as it does not show the value of Support Level on the Case record. A roll-up summary field is used to aggregate numeric values from child records, not to display picklist values.

Answer 53

A, D, Questions and Answers PDF 37/150 The two tools that an app builder could combine to display the number of open cases on the account page are Flow and Process Builder. Flow is a tool that allows the app builder to create a declarative automation that can query, manipulate, and display data from multiple objects. Process Builder is a tool that allows the app builder to create a trigger-based automation that can invoke a Flow when a record is created or updated. By using these two tools, the app builder can create a solution that can query the number of open cases for the account and parent account and display them on the account page using a screen element. Workflow is not a suitable tool, as it cannot query or display data from multiple objects. It can only perform actions such as field updates, email alerts, tasks, or outbound messages. Approval Process is not a suitable tool, as it is used to automate the approval of records based on certain criteria and predefined steps. It cannot query or display data from multiple objects.

Answer 54

B, C, 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.

Answer 55

B, The app builder should go to the Account object to build these new rollups. A roll-up summary field is a type of field that can aggregate numeric values from child records related to a parent record by a master-detail relationship. The app builder can create two roll-up summary fields on the Account object that count the number of open Opportunities and the number of won Opportunities related to each Account. Lightning App Builder is not a place where the app builder can build these new rollups. Lightning App Builder is a tool that allows the app builder to customize the layout and components of Lightning pages, such as record pages, home pages, or app pages. It cannot create new fields or relationships on objects. Lightning Object Creator is not a place where the app builder can build these new rollups. Lightning Object Creator is a tool that allows the app builder to create custom objects from spreadsheet data by uploading a file and mapping columns to fields. It cannot create roll-up summary fields or relationships on existing objects. Opportunity object is not a place where the app builder can build these new rollups. The Opportunity object is the child object in the relationship with the Account object, and roll-up summary fields can only be created on the parent object.

Answer 56

B, The app builder should recommend configuring Campaign Hierarchies and Campaign statistics to understand return on investment for the latest advertising buy. Campaign Hierarchies allow users to organize campaigns into parent-child relationships based on common goals or themes, such as product lines or marketing channels. Campaign statistics allow users to track and measure key Questions and Answers PDF 39/150 metrics for campaigns and campaign hierarchies, such as budgeted cost, actual cost, expected revenue, number of leads, number of contacts, etc. By using these features, users can calculate return on investment for each campaign and campaign hierarchy by comparing actual cost and expected revenue. Utilizing Account Hierarchies and Roll-Up Summary fields is not a valid recommendation, as it does not relate to campaigns or advertising buys. Account Hierarchies allow users to organize accounts into parent-child relationships based on business structure or affiliation, such as subsidiaries or partners. Roll-Up Summary fields allow users to aggregate numeric values from child records related to a parent record by a master-detail relationship. Running an opportunities pipeline report is not a valid recommendation, as it does not provide information about campaigns or advertising buys. An opportunities pipeline report shows the stages and amounts of opportunities in the sales process, such as prospecting, qualification, negotiation, etc. Changing to a public security model is not a valid recommendation, as it does not affect the ability to track and measure campaigns or advertising buys. A public security model is a type of organization- wide default that determines the baseline level of access that users have to records they do not own. A public security model grants all users read or read/write access to all records, regardless of ownership.

Answer 57

A, D, The two actions that an app builder should take to meet the requirements are: Implement a sharing rule. A sharing rule is a way to grant additional access to records based on certain criteria, such as record owner, role, profile, or field value. The app builder can create a sharing rule that grants read access to all accounts with the VIP Account field value to all users. This way, all users can view these accounts, but only the owners can edit them. Change organization-wide defaults. Organization-wide defaults are the baseline level of access that users have to records they do not own. The app builder can change the organization-wide default for accounts from Public Read Only to Private. This way, only the owners can view and edit their own accounts, unless additional access is granted by other means, such as sharing rules. Configuring a permission set is not a valid action, as it does not affect record-level access. A permission set is a way to grant additional permissions and access settings to users on top of their profile settings, such as object permissions, field permissions, app permissions, etc. Setting up an Account Team is not a valid action, as it does not restrict record-level access. An Account Team is a way to share an account and its related records with a group of users who work together on the account, such as sales reps, managers, or support agents. An Account Team grants Questions and Answers PDF 40/150 additional access to team members based on predefined roles and access levels.

Answer 58

B, The app builder should use Web-to-Case to enable visitors to the website to open cases. Web-to- Case is a feature that allows users to create an HTML form that can be embedded into a public-facing website. When visitors fill out and submit the form, a new case is automatically created in Salesforce with the information from the form fields. Web-to-Case can also assign cases to queues or users based on predefined rules and criteria. Outbound message is not a valid tool, as it does not enable visitors to open cases. An outbound message is a type of workflow action that sends a secure XML message to a designated endpoint URL when a record meets certain criteria. An outbound message can be used to integrate Salesforce with external systems or applications. Screen flow is not a valid tool, as it does not enable visitors to open cases from a public-facing website. A screen flow is a type of flow that allows users to create an interactive guided process that can collect, display, and update data from multiple objects within Salesforce. A screen flow can be embedded into Lightning pages or Visualforce pages, but it cannot be exposed to unauthenticated users on a public website. Email-to- Case is not a valid tool, as it does not enable visitors to open cases from a website. Email-to-Case is a feature that allows users to create cases from email messages sent to a specific email address. Email- to-Case can also capture email attachments and thread information and associate them with the case.

Answer 59

A, Questions and Answers PDF 41/150 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. Import Wizard 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.

Answer 60

B, C, 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, Questions and Answers PDF 42/150 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.

Answer 61

C, The app builder should use Sum as the type of summary in the roll-up summary field. A Sum type of summary allows the app builder to calculate the total value of a numeric field from the child records related to a parent record by a master-detail relationship. The app builder can create a roll-up summary field on the Account object that sums the Amount field from the won Opportunities related to each Account. Count is not a valid type of summary, as it does not calculate the total value of a numeric field. A Count type of summary allows the app builder to count the number of child records related to a parent record by a master-detail relationship. Max is not a valid type of summary, as it does not calculate the total value of a numeric field. A Max type of summary allows the app builder to display the largest value of a numeric or date field from the child records related to a parent record by a master-detail relationship. Min is not a valid type of summary, as it does not calculate the total value of a numeric field. A Min type of summary allows the app builder to display the smallest value of a numeric or date field from the child records related to a parent record by a master-detail relationship.

Answer 62

B, A permission set containing the salary record type and assigning it to the appropriate users would allow only those users to create salary applicant records, while still allowing all users to view all applicant records. This is the most granular and flexible way to meet the requirement

Answer 63

C, A validation rule can enforce process compliance by preventing users from saving records that do not meet certain criteria. In this case, a validation rule can prevent users from reverting to an earlier case status or leaving certain fields blank when specific case criteria are met

Answer 64

A, 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

Answer 65

D, Creating both customer and dealer as accounts, creating account teams on each account and associating the dealer records with the parent account would allow UC to track each customer and dealer separately, as well as their relationships and reps. Account hierarchy is not suitable for this scenario, as it is used to show the relationships among parent and child accounts within a single company

Answer 66

A, D, Big objects and external objects can be used to archive historical data and reduce data storage in Salesforce, while still allowing users to access the archived data using reports, queries, and lookups. Big objects store data within Salesforce, while external objects store data outside Salesforce and integrate it with Salesforce using an external data source

Answer 67

B, C, Updating the account search layouts search results columns displayed and updating the account search filter fields can improve an end user's search experience by showing more relevant Questions and Answers PDF 47/150 information and allowing more refined filtering. The view filter settings and the accounts tab columns displayed are not related to the search functionality

Answer 68

C, Creating a formula field on the Contact object and setting the value of the formula to TEXT(Account.Account_Region__c) would reflect the region of the related account on the contact record and stay in sync if the value changes on the account. This is the most efficient and maintainable way to meet the requirement. Creating a workflow rule or a picklist field would require additional configuration and complexity

Answer 69

D, Setting email deliverability to no access would prevent outbound email sends during testing in a sandbox. This would ensure that no emails are sent to any users or external email addresses from the sandbox. Setting email deliverability to system email only would still allow some emails to be sent, Questions and Answers PDF 48/150 such as password reset emails or new user emails. Configuring SMTP authentication or email relay would not affect email deliverability in a sandbox

Answer 70

B, A geolocation field can be used to capture the coordinates of a location in latitude and longitude. This field type can also be used in reports, formulas, validation rules, and Apex

Answer 71

D, A report type that is in a status of In Development is not available for users to select when creating a new report. The app builder needs to change the status to Deployed to make it visible to users

Answer 72

C, 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

Answer 73

D, Guided Action Flows on the record page can help service agents meet the requirement of confirming a user identity before providing support information over the phone. Guided Action Flows are a series of screens that guide agents through a predefined process, such as verifying user information, collecting case details, or resolving issues

Answer 74

A, B, To import opportunities with the proper country currency, the app builder needs to include the currency ISO code in all currency fields in the import file, and use Data Loader to import the records. Data Loader supports importing multiple currencies, while Import Wizard does not. The currency ISO code column in the import file specifies the currency for each record

Answer 75

C, Formulas cannot reference child records, only parent records. This is a limitation of formulas that could be causing the issue. To include data from related child records, the app builder could use roll- up summary fields or Apex triggers instead

Answer 76

A, D, Before replacing workflow rules and Apex triggers with Process Builders, the app builder should consider avoiding generating infinite loops and combining actions when possible. Infinite loops can occur when a process updates a record that causes another process to run on the same record, and so on. Combining actions can reduce the number of processes and improve performance and Questions and Answers PDF 51/150 maintainability

Answer 77

B, A quick action on the Account object can be used to create Opportunity records related to an Account. The quick action can pre-populate some fields based on the Account record, and also allow the user to input some fields. This would improve the process of creating Opportunity records

Answer 78

B, A custom button, a validation rule, and record types can be used to meet the requirement of hiding the convert button on leads until the lead status picklist is set to qualified. The custom button can replace the standard convert button and invoke a validation rule that checks the lead status. The record types can be used to assign different page layouts with different buttons for different lead statuses

Answer 79

C, D, All data should be backed up before converting a text field to a picklist, as some data may be lost or truncated during the conversion. Changing a field type will remove existing field history, as the history tracking values are not converted

Answer 80

A, D, Two reasons that can prevent an app builder from adding a custom component to the Lightning home page are if My Domain is not deployed, or if the component is tagged for record pages instead of home pages. My Domain must be deployed to add custom components to the page with the App Builder, as it enables Lightning components and other features. The component must be tagged for home pages in its configuration file, otherwise it will not show up in the App Builder for home pages

Answer 81

A, 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.

Answer 82

C, The best way to show Asset Inventory as a related list on Asset is to create a lookup relationship on Asset Inventory to Asset. This will allow one-to-many relationship between Asset and Asset Inventory, and display the related records on the Asset page layout. Questions and Answers PDF 55/150

Answer 83

A, C, 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.

Answer 84

D, 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.

Answer 85

A, The best feature to use to ensure consistent case priority entry is Path. Path allows users to see key fields and guidance for each stage of a process, such as a case lifecycle. Path can also enforce data quality by making certain fields required at each stage. See [this article] for more information on Path.

Answer 86

A, The best field type to use for the Planet Details field is Rich Text Area. This field type allows users to enter formatted text, images, and links. Long Text Area does not support images and links, Multi- Select Picklist does not allow text entry, and URL only allows a single web address.

Answer 87

D, The best way to configure Account sharing so that community users only see their own Account is to Questions and Answers PDF 57/150 set the account external OWD to private. This will restrict the access to Account records for external users based on the sharing rules and criteria. Creating an account record type, defining an owner- based sharing rule, or defining a permission set will not prevent community users from seeing other accounts.

Answer 88

A, B, The best actions to take to avoid creating duplicate leads when uploading a list of 400 leads are to utilize a Lead Matching Rule and corresponding Duplicate Rule to block newly created duplicate leads, and to upload the lead list using the import wizard and select a Matching type to prevent duplicate lead creation. The Lead Matching Rule defines the criteria for identifying duplicate leads, and the Duplicate Rule defines the actions to take when a duplicate is detected. The import wizard allows users to choose a Matching type based on the Lead Matching Rule and block or allow duplicates. Using Data Loader's update function or enabling Duplicate Matching in the Data Management section will not prevent duplicate lead creation.

Answer 89

C, The best Lightning component to add to the layout to display the 'New Task' custom action is Highlights panel. This component shows key information and actions for a record, such as its name, owner, and custom actions. Related record, related lists, and activities are not Lightning components that display custom actions. See [this article] for more information on Highlights panel.

Answer 90

D, The best solution to enable reps to see and access the most-used components from anywhere within the app without leaving the page they are working on is Utility bar. This is a footer that can be added to any Lightning app and can contain tools such as history, notes, or softphone. Favorites, home Questions and Answers PDF 59/150 page, and global actions are not solutions that provide access to components from anywhere within the app. See [this article] for more information on Utility bar.

Answer 91

B, 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. Questions and Answers PDF 60/150

Answer 92

A, D, The formula for creating a visual indicator flag on each case based on the case priority should use the IMAGE and CASE functions. The IMAGE function returns an image for a given URL, and the CASE function evaluates an expression and returns a value based on that expression. Option A and D use these functions correctly, while option B and C do not.

Answer 93

B, The most likely reason why users are unable to view the custom Lightning component on mobile devices is that the component has been developed for Desktop Pages only. Some components are not supported on mobile devices or have different behavior on mobile devices. An app builder should check the component documentation or metadata to see if it is compatible with mobile devices.

Answer 94

A, The best way to help the sales manager achieve their goal of reducing manual data entry from business cards is to research and evaluate data enrichment products on the AppExchange that can automate data entry. Data enrichment products can scan business cards, extract relevant information, and populate fields in Salesforce records. This can save time, improve data quality, and enhance productivity. Option B, C, and D are not effective solutions for this goal. Questions and Answers PDF 62/150

Answer 95

B, D, A formula field cannot be referenced by a roll-up summary field if it contains a cross-object field reference or a time-based function. A cross-object field reference is a reference to a field from a different object, such as Account. Name on a Contact object. A time-based function is a function that returns the current date or time, such as NOW() or TODAY(). Option A and C do not prevent a formula field from being referenced by a roll-up summary field.

Answer 96

D, 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.

Answer 97

A, A managed package from AppExchange is a custom solution that is developed by a third-party provider and can be installed in Salesforce. A managed package can be easily updated by the provider without affecting the existing functionality or customizations. This makes it suitable for the app builder's requirement of ease of updates. Option B, C, and D are not as easy to update as a managed package.

Answer 98

A, D, Sharing rules and manual sharing are two features that can extend record access beyond the organization-wide defaults. Sharing rules are automatic rules that grant access to groups of users based on certain criteria, such as role, public group, or territory. Manual sharing is a manual way of granting access to individual users or groups by the record owner or someone above them in the role hierarchy. Option B and C are not features that extend record access.

Answer 99

D, The app builder should add the fields to the page layout on the object to ensure users can access the new object and fields. The page layout determines which fields are visible and editable on the record Questions and Answers PDF 64/150 detail page. Option A, B, and C are not necessary for this purpose.

Answer 100

A, The new object should have a lookup relationship to the Opportunity object. A lookup relationship creates a link between two objects and allows related records to be viewed in a related list. This can be used to track installation information for each opportunity and give sales reps visibility of all the installations associated with their opportunities. Option B, C, and D are not appropriate for this requirement.

Answer 101

B, The app builder should use a global picklist value set to share the list of values for the Status field across each object. A global picklist value set is a set of values that can be used by multiple picklist fields on different objects. This can ensure data consistency and reduce maintenance efforts. Option A, C, and D are not features that can share picklist values across objects.

Answer 102

C, D, An app builder can go to two places to see a list of available custom Lightning components in their org: Lightning App Builder: This is a tool that allows an app builder to create and customize Lightning pages using drag-and-drop components. The app builder can see the list of custom Lightning components in the Custom section of the Lightning Components pane1. Lightning Components in Setup: This is a setup menu that allows an app builder to view, create, edit, and delete custom Lightning components in their org. The app builder can see the list of custom Lightning components in the Lightning Components section of the Setup menu2. Option A and B are Questions and Answers PDF 66/150 not places where an app builder can see a list of custom Lightning components.

Answer 103

D, The app builder should use the Path component to meet the requirement of tracking different fields at each stage of the Opportunity sales process. The Path component is a Lightning component that displays the key fields and guidance for each stage of a standard or custom picklist field, such as the Opportunity Stage field. The app builder can configure the Path component to show the fields that need to be filled out and provide recommendations and sales strategies for each stage3. Option A, B, and C are not configuration steps that can meet this requirement.

Answer 104

B, 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.

Answer 105

A, 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.

Answer 106

D, The app builder should recommend a workflow rule to automate this process. A workflow rule is a type of automation tool that can execute actions based on certain criteria. In this case, the workflow Questions and Answers PDF 68/150 rule can have a criterion that evaluates if the DoNotCall checkbox is checked on a Contact record, and then execute a field update action that sets the Phone field to null. Option A, B, and C are not automation tools that can perform this task.

Answer 107

B, D, 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.

Answer 108

C, The app builder should use Apex code to update a field on the parent record when a child record connected via lookup is deleted. Apex code is a programming language that allows developers to execute complex logic on the Salesforce platform. Apex code can be triggered by certain events, such as insert, update, delete, or undelete of records. In this case, the app builder can write an Apex trigger that runs after a child record is deleted and updates a field on the parent record accordingly. Option A, B, and D are not automation tools that can perform this task.

Answer 109

A, The app builder should create a new roll-up summary field called First Order Date, using Type MIN on the Opportunity Close Date with a filter where IsWon = TRUE. A roll-up summary field is a type of field that calculates values from related records and displays them on the parent record. In this case, the app builder can create a roll-up summary field on the Account object that calculates the minimum (earliest) value of the Opportunity Close Date field from the related opportunities where IsWon = TRUE. This will show when customers made their first purchase. Option B, C, and D are not correct ways to use a roll-up summary field to meet the requirement.

Answer 110

C, D, The app builder needs to do two steps to make the custom Lightning App available to the internal users at Universal Containers: Create a subdomain using My Domain: My Domain is a feature that allows an organization to set up a custom domain name for their Salesforce instance. This is required to use custom Lightning components and apps in Salesforce1. Build a Custom Tab for the app: A custom tab is a tab that displays any custom object or web page in Salesforce. This is required to make the custom Lightning App accessible from the navigation menu or app launcher2. Option A and B are not necessary steps to make the custom Lightning App available to the internal users.

Answer 111

A, 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.

Answer 112

D, The app builder needs to have NOT(ISBLANK([Lead].OwnerId)) in the criteria to ensure the process runs without error. This formula checks if the OwnerId field on the Lead object is not blank, which means that the lead is owned by a user or a queue. This will prevent the process from running on leads that are not owned by anyone, which could cause an error. Option A, B, and C are not formulas that can ensure the process runs without error.

Answer 113

C, The app builder should add the field to the custom report type field layout to troubleshoot this issue. A custom report type is a type of report that defines which objects and fields are available for reporting. The app builder can customize which fields are included in each custom report type by editing its field layout. If a new field is added to an object that is part of an unmanaged package, it will not be automatically added to the custom report type field layout. The app builder needs to manually add it to make it available as an option to add as a column in reports based on that custom report type. Option A, B, and D are not steps that can troubleshoot this issue.

Answer 114

B, The app builder should know that a field type change is included in the change set and that it can cause a delay in the deployment. A field type change is a change that modifies the data type of an existing field, such as changing a text field to a number field. A field type change can affect many aspects of Salesforce functionality, such as validation rules, formulas, workflows, reports, dashboards, and more. Therefore, deploying a change set that contains a field type change can take longer than usual and require more testing and verification. Option A, C, and D are not changes that can cause a delay in the deployment.

Answer 115

D, The app builder should create a sharing rule that grants the users Read/Write access to the Application records. A sharing rule is a type of rule that can extend record access to groups of users based on certain criteria. In this case, the app builder can create a sharing rule that grants Read/Write access to the Application object to the recruiters based on their role, public group, or queue. This will allow them to edit the Application records related to any Internship record, regardless of the ownership. Option A, B, and C are not ways to configure the proper access.

Answer 116

B, The app builder should use the CASESAFEID(Id) formula to create this new field. The CASESAFEID function returns the 18-digit case-insensitive version of the record ID, which is unique for each record in Salesforce. The 18-digit record ID is useful for exporting data to external systems that require case- sensitive IDs1. Option A, C, and D are not formulas that can return the 18-digit record ID.

Answer 117

B, The app builder should recommend UC use Salesforce Connect to access the assets in real-time data in Salesforce. Salesforce Connect is a feature that allows users to view, search, and modify data that is stored outside Salesforce, such as in an external system. Salesforce Connect uses external objects and external data sources to integrate data from various sources without copying or synchronizing it2. This can help UC access their assets in real-time without consuming data storage limits in Salesforce. Option A, C, and D are not features that can meet this requirement.

Answer 118

A, 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.

Answer 119

D, Questions and Answers PDF 75/150 The app builder should use a custom button and Flow to achieve the desired result. A custom button is a button that can invoke custom logic or actions when clicked by a user. A Flow is a type of automation tool that can guide users through a series of screens and perform actions based on user input. In this case, the app builder can create a custom button on the Account object that launches a Flow when clicked by a user. The Flow can display a popup window with questions for the user to answer and populate additional fields on the Account record based on the user input4. Option A, B, and C are not tools that can achieve this result.

Answer 120

A, C, The app builder should use two options to ensure all contracts route for the correct approval and also prevent the sales rep from making changes to the record while it is being approved: Create an approval process on the Contract object with criteria set on a second approval step set as 'Amount__c > 10,000' and set the approver as director. An approval process is a type of process that automates how Salesforce records are approved in an organization. An approval process can have multiple steps with different criteria and approvers. In this case, the app builder can create an approval process on the Contract object with two steps: one for the sales manager approval and one for the director approval if the contract amount is over $10,0001. Create a validation rule on the Contract object that prevents updates to the contract record while it is being reviewed. A validation rule is a type of rule that checks data quality by verifying that the data in a record meets certain standards before it can be saved. A validation rule can prevent users from making changes to a record that is in a certain status or stage. In this case, the app builder can create a validation rule on the Contract object that prevents updates to the contract record if its Approval Status field is not equal to Not Submitted2. Option B and D are not options that can ensure all contracts route for the correct approval and also prevent the sales rep from making changes to the record while it is being approved.

Answer 121

B, C, Questions and Answers PDF 77/150 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.

Answer 122

A, C, The app builder has two options available when defining an object-specific Create Record custom action: Pre-Defining field values on the target object. This means that the app builder can specify default values for certain fields on the target object when creating a new record using the custom action. Specifying the fields and layout of the action. This means that the app builder can choose which fields to include in the action and how they are arranged on the screen. Option B and D are not options available when defining an object-specific Create Record custom action.

Answer 123

C, The app builder would enable this ability in Chatter Settings. Chatter Settings is a setup menu that Questions and Answers PDF 78/150 allows an app builder to configure various aspects of Chatter functionality, such as feeds, groups, email notifications, and more. One of the options in Chatter Settings is Enable Approvals via Chatter, which allows users to approve or reject requests from their team via Chatter posts or comments. Option A, B, and D are not places where an app builder would enable this ability.

Answer 124

C, This formula concatenates the four custom fields for the Galactic Vendor's location into a single text value, separated by commas and spaces. The formula also uses the BR function to insert a line break after the second field, creating two lines of text. Option A, B, and D are not formulas that fulfill the requirement.

Answer 125

C, The primary object selection is locked once the custom report type has been saved. This means that the app builder cannot change the primary object later. The other options are not true.

Answer 126

B, C, 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 Questions and Answers PDF 80/150 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.

Answer 127

A, Making the Opportunity type a required field on the initial Opportunity page layout and using automation to fill in the type field to a record type is a way to limit the number of fields users are required to fill out when creating a new Opportunity. This way, the app builder can assign different page layouts for different record types based on the Opportunity type. The other options are not feasible or effective

Answer 128

A, C, 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 Questions and Answers PDF 81/150 requirement.

Answer 129

C, 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.

Answer 130

A, C, 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.

Answer 131

C, 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.

Answer 132

C, 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.

Answer 133

A, The app builder should recommend utilizing the manage assignments button to assign a permission set group and additional individual permission sets to each user. This way, the app builder can assign the five consistent permission sets to all users in one permission set group, and then assign additional permission sets to higher-level staff as needed. Option B is incorrect because it will not account for the varying levels of support staff and their different permission sets. Option C is incorrect because the Data Import Wizard cannot be used to assign permission sets or permission set groups to users. Option D is incorrect because the Data Loader cannot be used to assign permission set groups to users.

Answer 134

D, 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.

Answer 135

A, If the app builder tries to convert a preexisting long text area field to text area, preexisting information will truncate to the first 255 characters. This means that any information beyond 255 characters will be lost. Option B is incorrect because preexisting information will not remain if it was over 255 characters. Option C is incorrect because preexisting information will not cause an error message to pop up. Option D is incorrect because preexisting information in the field will not be completely lost, only truncated.

Answer 136

A, 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.

Answer 137

B, The app builder should recommend building a global action to create Contacts. A global action allows users to create records quickly from any page in Salesforce on their mobile devices. The app builder can also specify predefined values for some fields in the global action, such as Account Name or Phone Number, to make data entry easier for users. Option A is incorrect because customizing the mobile menu to move Contacts to the top does not help users create new contacts quickly or follow up later. Option C is incorrect because adding a compact layout to Contacts does not help users create new contacts quickly or follow up later, but rather shows them more fields on record detail pages or list views. Option D is incorrect because using Path and setting pre-defined values does not help users create new contacts quickly or follow up later, but rather guides them through different stages of a record.

Answer 138

A, C, The field attribute that should be selected are Unique and External ID. Unique means that the field will not allow duplicate values. External ID means that the field can be used as a foreign key for data imports and upserts. Option B is incorrect because Required means that the field must have a value and cannot be left blank, which is not necessary for this requirement. Option D is incorrect because Text (encrypted) means that the field will store sensitive data in an encrypted format, which is not necessary for this requirement.

Answer 139

A, C, 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.

Answer 140

A, The solution that the app builder should use to meet DreamHouse Realty's needs is Master-Detail Child Object. A master-detail relationship can be used to create a parent-child relationship between two objects, where the child records inherit the sharing and security settings of their parent record. The app builder can create a roll-up summary field on the parent object to calculate the highest value Questions and Answers PDF 87/150 of all child records. Option B is incorrect because Text Area (Long) is a field type that allows users to enter up to 131,072 characters on one line, which is not suitable for this requirement. Option C is incorrect because Multi-select Picklist is a field type that allows users to select multiple values from a predefined list, which is not suitable for this requirement. Option D is incorrect because Lookup Object is not a valid term, but rather Lookup Relationship, which is a type of relationship that links two objects together, but does not support roll-up summary fields.

Answer 141

D, 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 Questions and Answers PDF 88/150 best practice, as invocable processes are used to invoke other processes from within a process or a flow.

Answer 142

D, The feature that can be used to meet these requirements is two-step approval process. An approval process defines the steps and criteria for approving records. A two-step approval process requires two levels of approval before a record can be deleted. The app builder can configure an approval process for opportunities that requires sales reps to submit their delete requests for approval from their managers. Option A is incorrect because Process Builder with Submit for Approval action is not a valid feature, as Process Builder cannot submit records for approval. Option B is incorrect because Approval Process with a triggered Flow process is not a valid feature, as Approval Process cannot trigger Flow processes. Option C is incorrect because Approval Process with Time-Dependent Workflow action is not a valid feature, as Approval Process cannot use Time-Dependent Workflow actions.

Answer 143

D, The feature that the app builder should use to create easy access to the document is a custom detail page link on the Contract object. A custom detail page link is a type of custom button or link that can display a URL or execute JavaScript when clicked. The app builder can create a custom detail page link on the Contract object that displays the pricing guidelines document in a new window or tab. Questions and Answers PDF 89/150 Option A is incorrect because a quick action on the Contracts object is not suitable for this requirement, as quick actions are used to create or update records, log calls, send emails, or launch flows. Option B is incorrect because a quick action on the Account object is not suitable for this requirement, as quick actions are not related to the Contract object. Option C is incorrect because a custom detail page link on the Account object is not suitable for this requirement, as custom detail page links are not related to the Contract object.

Answer 144

D, C, 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.

Answer 145

C, The automation solution that would meet these requirements is Process Builder. Process Builder is a tool that can create and update records, send email alerts, submit records for approval, invoke flows, call Apex classes, and post to Chatter based on certain criteria and actions. The app builder can use Process Builder to create a process that starts when an opportunity is marked as closed won, creates a new opportunity record for the renewal with pre-populated fields, and sends an email alert to the contracts team. Option A is incorrect because an approval process is not suitable for this requirement, as approval processes are used to define the steps and criteria for approving records. Option B is incorrect because a validation rule is not suitable for this requirement, as validation rules are used to enforce data quality and prevent users from saving invalid records. Option D is incorrect because a workflow rule is not suitable for this requirement, as workflow rules are considered legacy tools and have limitations compared to Process Builder.

Answer 146

B, The feature that the app builder should use to solve this issue is component visibility filter. A component visibility filter is a setting that can be applied to a Lightning component on a record page to control when the component is hidden or displayed based on certain conditions. The app builder can use a component visibility filter to hide the component from users with a Marketing profile. Option A is incorrect because detail page layouts are not related to Lightning components, but rather the fields and related lists that appear on record detail pages. Option C is incorrect because field- level security is not related to Lightning components, but rather the access level of fields for different profiles or permission sets. Option D is incorrect because AppExchange is not related to Lightning components, but rather an online marketplace where users can find and install apps and components.

Answer 147

A, 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.

Answer 148

C, The steps that the app builder should take to meet these requirements are creating a Partial Copy Sandbox and using a sandbox template. A Partial Copy Sandbox can include data records, exclude confidential objects, and be refreshed weekly. A sandbox template can specify which objects and data are copied from the production org to the sandbox org. Option A is incorrect because creating a Full Sandbox and using a sandbox template is not necessary for this requirement, as Full Sandboxes copy all data and metadata from the production org and can only be refreshed every 29 days. Option B is incorrect because creating a Developer Pro Sandbox and scheduling Data Loader to download selected object data weekly is not feasible for this requirement, as Developer Pro Sandboxes do not include data records by default and Data Loader cannot be scheduled to run weekly. Option D is Questions and Answers PDF 92/150 incorrect because creating a Developer Sandbox and scheduling Data Loader to download selected object data weekly is not feasible for this requirement, as Developer Sandboxes do not include data records by default and Data Loader cannot be scheduled to run weekly.

Answer 149

B, The solution that should meet this requirement is updating the support team profile to remove the Bronze record type. This way, the support team users will not be able to create new cases with the Bronze record type, as it will not appear in their record type selection list. Option A is incorrect because updating the organization-wide defaults to private for Case does not affect the record type availability, but rather the record access level. Option C is incorrect because creating permission set group for Case that includes Platinum and Diamond record types does not prevent the support team users from creating new cases with the Bronze record type, as they may still have access to it through their profile. Option D is incorrect because making the record type hidden to support users and updating sharing roles to private does not prevent the support team users from creating new cases with the Bronze record type, as they may still have access to it through their profile.

Answer 150

A, The solution that the app builder should configure to meet these requirements is creating three lead record types each with its own page layout containing the relevant fields. This way, the app builder can customize the fields and sections that appear on each record type based on the source of the Questions and Answers PDF 93/150 lead. Option B is incorrect because creating a partner community and a record type for web and trade show leads does not address the requirement of collecting information that is unique to each type of lead, as partner community users may have different fields and layouts than internal users. Option C is incorrect because creating three sections on the lead layout and instructing users to collapse the non-relevant fields does not address the requirement of collecting information that is unique to each type of lead, as users may still see or enter data in the wrong fields. Option D is incorrect because creating custom page layouts for each type of lead only containing the relevant fields does not address the requirement of collecting information that is applicable to all sources, as users may miss some common fields.

Answer 151

A, 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.

Answer 152

C, The solution that an app builder should use for this request is a lookup field. A lookup field is a type of relationship field that links two objects together and allows users to select a record from another object. The app builder can create a lookup field on the account object that references the user object and allows users to assign a customer service manager (CSM) to the account. Option A is incorrect because a multi-select picklist field is not suitable for this request, as multi-select picklist fields allow users to select multiple values from a predefined list, not from another object. Option B is incorrect because a picklist field is not suitable for this request, as picklist fields allow users to select one value from a predefined list, not from another object. Option D is incorrect because a text field is not suitable for this request, as text fields allow users to enter any alphanumeric characters, not from another object.

Answer 153

A, The recommended solution to grant the customer service agent access to the field is creating a permission set that allows read-only access to the field via Field Level Security and assigning it to the agent. A permission set is a collection of settings and permissions that give users access to various tools and functions. Field Level Security (FLS) is a setting that controls the access level of fields for different profiles or permission sets. The app builder can create a permission set that grants read- only access to the custom field on the account object via FLS and assign it to the agent. Option B is incorrect because creating a new profile to allow for read-only access to the field via FLS and assigning it to the agent is not recommended, as profiles are used to define the baseline permissions and settings for a group of users, and creating multiple profiles for individual users can be hard to Questions and Answers PDF 95/150 maintain. Option C is incorrect because updating the Customer Service Profile already assigned to the agent to allow for read-only access to the field via FLS is not recommended, as this will affect all users who have the same profile, which may violate the security policy. Option D is incorrect because updating the custom field's FLS in setup to allow the agent read-only access to the field is not possible, as FLS can only be set at the profile or permission set level, not at the user level.

Answer 154

D, The solution that an app builder should use to meet this requirement is master-detail relationship. A master-detail relationship is a type of relationship that creates a parent-child relationship between two objects, where the child records inherit the sharing and security settings of their parent record. The app builder can create a master-detail relationship between Supplier__c and SupplierItem__c objects, where Supplier__c is the parent object and SupplierItem__c is the child object. This way, when a Supplier__c record is deleted, all related SupplierItem__c records are also deleted automatically. Option A is incorrect because many-to-many relationship is not suitable for this requirement, as many-to-many relationship allows two objects to be linked in both directions through a junction object, but does not support cascading delete. Option B is incorrect because indirect lookup relationship is not suitable for this requirement, as indirect lookup relationship allows an external object to link with another object using an external ID field, but does not support cascading delete. Option C is incorrect because hierarchical relationship is not suitable for this requirement, as hierarchical relationship allows users to use a lookup field that links an object with itself, but does not support cascading delete.

Answer 155

C, The full sandbox should be refreshed after each major release to production. This way, the full sandbox will have the most updated data and metadata from the production org, and can be used for final load and regression testing before the next release. Option A is incorrect because refreshing the full sandbox after user acceptance testing is complete is not necessary, as user acceptance testing can be done in the partial data sandbox or the production org. Option B is incorrect because refreshing the full sandbox after each push from the partial data sandbox is not necessary, as the full sandbox can receive configuration and code changes from the partial data sandbox without refreshing. Option D is incorrect because refreshing the full sandbox after a new user is added to production is not necessary, as adding a new user does not affect the data and metadata in the full sandbox.

Answer 156

D, The solution that an app builder should use to meet this requirement is creating a custom report type with converted leads as the primary object. A custom report type is a template that defines the objects and fields that are available for a report. The app builder can create a custom report type that has converted leads as the primary object and includes fields from related objects, such as accounts, contacts, and opportunities. This way, sales reps can create reports on converted leads and see their related information. Option A is incorrect because enabling preserve lead status in the lead conversion settings does not affect the reporting on converted leads, but rather allows users to retain the original lead status after conversion. Option B is incorrect because assigning the representative view and edit converted leads permission does not affect the reporting on converted leads, but rather allows users to view and edit converted lead records. Option C is incorrect because ensuring the representative has read access to the original lead records does not affect the reporting on converted leads, but rather allows users to view the original lead records.

Answer 157

A, D, Removing the Delete permission from the Shipper profile and using a permission set to remove the Delete permission are both valid ways to prevent users from deleting delivery records. Removing the delete button from the Delivery page layout will not prevent users from deleting records using other methods, such as list views or reports. Changing the organization-wide default of deliveries to Private will not affect the delete permission, but only the sharing settings.

Answer 158

D, 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.

Answer 159

D, 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.

Answer 160

B, Dynamic actions are a new feature that allow app builders to create custom buttons or actions that can call Lightning Web Components and display them conditionally based on field values or other criteria. Formula fields, AppExchange products, and custom links are not able to call Lightning Web Components.

Answer 161

A, B, AppExchange and Apex Code are two resources that can provide custom components for a Lightning app. AppExchange is a marketplace where developers can publish and sell their custom components or apps. Apex Code is a programming language that can be used to create custom components or logic for a Lightning app. Import Wizard and Visualforce are not resources for custom components, but tools for data import and web page development respectively.

Answer 162

C, 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.

Answer 163

A, Sales rep B has implicit access to the Account because of the manual sharing of the Opportunity. Implicit sharing grants access to parent records when a user has access to a child record. Sales rep B was not added to the Account team, sharing set is not applicable for private sharing model, and Account was not manually shared.

Answer 164

C, 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.

Answer 165

C, Sharing the dashboard folder with roles and subordinates of the US Sales Director and sharing the report folder with the role of US Sales Director will ensure that only the US sales directors can see the data in the component and view its source report, while all US sales reps can view the US Team dashboard. Making the US Sales Director the running user will show only his or her data in the component, not the whole team's data. Making the dashboard dynamic will show different data depending on who is viewing it, not based on their role. Sharing the dashboard with the public group US Sales Reps and sharing the dashboard source reports folder with the US Sales Director profile will not prevent other profiles from accessing the reports if they have access to the report folder.

Answer 166

B, 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.

Answer 167

D, All profiles will get access to the new field by default when it is created using Schema Builder. The app builder can modify the field-level security settings later to restrict access for certain profiles. Standard profiles, no profiles, and internal profiles are not correct options.

Answer 168

C, AppExchange is a marketplace where app builders can find prebuilt resources to help with migration and adoption projects. AppExchange offers apps, components, solutions, and consulting services that can assist with moving from Classic to Lightning Experience. Import Wizard, Lightning Object Creator, and Flow Builder are not sources of prebuilt resources, but tools for data import, object creation, and automation respectively. Questions and Answers PDF 103/150

Answer 169

A, 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.

Answer 170

C, 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.

Answer 171

B, 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.

Answer 172

D, 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 your package to install." Incorrect license types, package features not compatible, and object limits exceeded are not valid reasons for a package installation failure.

Answer 173

A, Approval Process is the feature that would be used to handle the requirement of signing off on major show retail deals with more than 30% discount. According to the Salesforce documentation, "An approval process automates how Salesforce records are approved in your org." Email Alert, Field Update, and Workflow Rule are actions that can be triggered by an approval process, but they are not features for handling approvals.

Answer 174

D, Lookup is the type of relationship that would be set up to meet the specification of pairing experienced Realtors with new Realtors. According to the Salesforce documentation, "A lookup relationship creates a loose association between objects. The lookup field allows users to select a record from another object." Indirect lookup is used for junction objects on different platforms. Many-to-many is not a type of relationship, but a result of using junction objects. Master-detail is used for creating parent-child relationships.

Answer 175

B, D, Using Process Builder on Opportunities and a Chatter post action, and enabling Feed Tracking on Opportunities are two configurations that an app builder can recommend to meet the requirement of notifying and tracking changes to an Opportunity Close Date. Process Builder can create a process that triggers a Chatter post action when the Close Date field is changed on an Opportunity. Feed Tracking can enable tracking of field history for the Close Date field on the Opportunity feed. Creating an Opportunity outbound message and activating Historical Trending for Opportunities are not valid configurations for this requirement.

Answer 176

B, Moving the reports from the Unfiled Public Reports folder and adding them to a new change set is what the app builder should do to deploy the reports to production. According to the Salesforce documentation, "Reports in the Unfiled Public Reports folder aren't available for deployment." Questions and Answers PDF 107/150 Moving the reports to the Untried Public Reports folder, recreating the reports in production, and adding the reports to an unmanaged package are not necessary or recommended actions.

Answer 177

D, Groups is available in the Chatter section of the navigation menu, not in the selected list for the navigation menu. According to the Salesforce documentation, "Groups appear in Chatter, not in Navigation Menu." Groups is not available in the recent section of the navigation menu, nor is it included in the Smart Search items but unavailable on the navigation menu. Groups is unavailable in the selected list for the navigation menu.

Answer 178

A, 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 is entered. 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.

Answer 179

A, Create a page layout with the field and use field-level security to hide the field from all other users is how the app builder should meet the requirement of making the comment field on Review private to anyone outside of HR department. Field-level security can control which profiles can view or edit a field on a record. Create an Apex sharing rule, create a sharing rule to share the field with VP of HR with Role and Subordinates, and create a page layout with the field for HR users and another page layout without the field for all other users are not valid or feasible solutions for this requirement. Questions and Answers PDF 109/150

Answer 180

B, 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.

Answer 181

C, Component visibility filter is the feature on the Lightning app builder that should be utilized to restrict a Lightning component to mobile app users. According to the Salesforce documentation, "Use component visibility filters to show or hide components on a record page based on field values or user profile." Chatter feed, highlights panel, and related list quick links are not features for controlling component visibility, but standard components that can be added to a record page.

Answer 182

B, C, Update the organization-wide defaults and create a criteria based sharing rule are two actions that an app builder should complete to implement the change of moving to a more restrictive sharing model while allowing the Sales team to access all account records with the sales record type. Updating the organization-wide defaults can set the baseline level of access for accounts, and creating a criteria based sharing rule can grant additional access based on record type. Updating the Sales profile and creating an owner-based sharing rule are not necessary or sufficient actions for this change.

Answer 183

D, Create a validation rule that uses the PRIORVALUE function is how an app builder can meet the requirement of preventing users from increasing the value of Estimated Hours after it is set. According to the Salesforce documentation, "PRIORVALUE returns the previous value of a field." The validation rule can compare the current value and the prior value of Estimated Hours and display an error message if the current value is greater than the prior value. Creating a formula default value for the custom field, creating a formula field that uses the PREVGROUPVAL function, and creating a validation rule that uses the ISCHANGED function are not valid or correct solutions for this Questions and Answers PDF 111/150 requirement.

Answer 184

A, Add the standard Chatter feed component is how an app builder can add the Chatter feed to a custom object record page. According to the Salesforce documentation, "The Chatter Feed component displays updates about records in your org." Add the standard related list component, add a custom Chatter feed component, and add the Chatter feed component from the AppExchange are not valid or necessary options.

Answer 185

C, Two Master-detail relationships on a new custom object is how an app builder should configure the data model to create a relationship between Contact and Solar Project objects where each Contact can be related to multiple Solar Project objects, and each Solar Project can have multiple Contacts associated with it. This is an example of a many-to-many relationship that requires a junction object with two master-detail relationships. One Master-detail relationship on Contact and one Master- detail relationship on Solar Project, two Lookup relationships on a new custom object, and one Lookup relationship on Contact and one Lookup relationship on Solar Project are not valid or correct ways to create a many-to-many relationship. Questions and Answers PDF 112/150

Answer 186

D, Create a custom action is the recommended solution to meet the requirement of creating additional accounts to form a hierarchy from a Parent Account record. According to the Salesforce documentation, "Actions let users quickly create or update records, log calls, send emails, and more, in the context of a particular object." A custom action can auto-populate fields based on the parent account and make it easier for users to create child accounts. Add Path on Account hierarchy, add a custom link on Account, and customize a Global Quick Action are not valid or feasible options.

Answer 187

B, C, Process Builder and Apex are two automation solutions that can meet the business requirements of summarizing the number of open and closed Cases related to an Account. Process Builder can create a process that updates the custom fields on Account based on changes in related Cases. Apex can write a trigger that performs the same logic using code. AppExchange and Workflow are not automation solutions for this requirement, but sources of apps or components and tools for creating workflow rules respectively.

Answer 188

C, Set the Organization-Wide Default to Private for accounts and create criteria-based sharing rules for each marketing team are the actions that can accomplish the requirement of restricting access to accounts based on region and role. Setting the Organization-Wide Default to Private will limit access to accounts to only owners and administrators. Creating criteria-based sharing rules will grant additional access to accounts based on region for each marketing team. Creating an Inside Sales Team profile with the "View All" setting for accounts will grant access to all accounts for the inside sales team. Update the Sales profile, update the organization-wide defaults to Public for accounts, create profiles for each marketing team, create permission sets for each marketing team, and create an Inside Sales Team role are not necessary or sufficient actions for this requirement.

Answer 189

C, Research and evaluate products available on AppExchange to send mass emails is the action that the app builder should take to meet the requirement of broadcasting an email to 7,000 contacts in Questions and Answers PDF 114/150 Salesforce on a regular basis. AppExchange is a marketplace where app builders can find products or solutions that can extend Salesforce functionality. There are many products on AppExchange that can send mass emails without hitting the Salesforce limit. Request Salesforce increase the number of maximum daily emails, develop Apex code and Lightning web component to send daily emails, and export Contacts to a CSV file and use an email client to send the emails are not valid or recommended actions.

Answer 190

B, Create a master-detail relationship between the parent and child object with a roll-up summary field that filters on the status field is the recommended method for the app builder to achieve the request of rolling up sales metrics to an opportunity for only Detailed.Sales__c records that have their picklist status set to Active. According to the Salesforce documentation, "Roll-up summary fields calculate values from related records, such as those in a master-detail relationship." A roll-up summary field can filter on a field value of the child records and sum up only those records that match the criteria. Utilize the AppExchange to download a third-party application that can roll up the sales dollars with the appropriate filter, create a lookup relationship between the parent and child object with a roll-up summary field that filters on the status field, and utilize Apex code to roll up the desired amounts are not valid or necessary methods for this request.

Answer 191

B, 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.

Answer 192

D, Create a master-detail relationship field on Applicant__c to Application__c is what the app builder should recommend to meet the requirements of allowing the same applicant to apply for multiple open positions using a single application. This will create a many-to-many relationship between Applicant__c and Open_Position__c using Application__c as a junction object. Create a master-detail relationship on Open_Position__c to Application__c, create a master-detail relationship field on Application__c to Open_Position__c, and create a lookup relationship field on Applicant__c to Application__c are not valid or correct ways to create a many-to-many relationship.

Answer 193

A, Questions and Answers PDF 116/150 Record-triggered flow is the automation tool that the app builder should use to best address all these requests of sending an email to the finance manager and creating a task for the sales manager when a new client is won. According to the Salesforce documentation, "Record-triggered flows automate processes for you. They start when a record is created or updated, or when a platform event occurs." A record-triggered flow can perform actions such as sending an email alert or creating a record based on criteria or conditions. Screen flow, Apex, and Approval process are not automation tools that can handle all these requests.

Answer 194

B, 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 on the account layout, and remove the Delete permission from the Sales Rep profile are not valid or sufficient solutions for this requirement.

Answer 195

A, C, A: Changing the Lead Matching Rule to 'Block on create' will directly prevent duplicates at the point of lead creation based on defined criteria. C: Changing the Lead Duplicate Rule to 'Bypass Sharing Rules' allows the system to compare leads across the entire organization regardless of the user's access level, which is crucial especially when OWD is set to 'Private'. Reference: Salesforce Help - Duplicate Management

Answer 196

A, The Compact Layout in Salesforce mobile app configuration determines the fields that appear at the top of the record in the mobile app, providing quick access to key information. Reference: Salesforce Help - Compact Layouts

Answer 197

A, An update record action with a related record component on the Opportunity layout allows users to edit related Account records directly. Questions and Answers PDF 119/150 Reference: Salesforce Help - Creating Quick Actions

Answer 198

C, Using 'Add Fields Related Via Lookup' in the report type configuration allows adding fields from the Account object to the Opportunity report, including the Account Rating. Reference: Salesforce Help - Custom Report Types

Answer 199

C, Partial Copy Sandboxes are ideal for testing and development purposes as they include a subset of production data and can be refreshed more frequently than Full Copy sandboxes. Reference: Salesforce Help - Types of Sandboxes

Answer 200

B, 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. Reference: Salesforce Help - External ID

Answer 201

D, Data Export Service is the appropriate tool for initiating scheduled or immediate backups of Salesforce data. Reference: Salesforce Help - Data Export Service

Answer 202

A, C, 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. Reference: Salesforce Help - External ID Fields

Answer 203

C, 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. Reference: [Salesforce Help - Roll-up Summary Fields](https://help.salesforce.com/s/articleView?id=sf.fields_about_roll_up up_summary_fields.htm&type=5)

Answer 204

D, 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. Reference: Salesforce Help - Account Hierarchies

Answer 205

A, A Scheduled Triggered flow can be used to increment a custom field on the Case object each time the case is reopened, effectively tracking the number of reopenings. Reference: Salesforce Help - Scheduled Flows

Answer 206

D, Updating the existing change set with the new changes and redeploying is the most efficient way to move the updated components to the Developer Pro Sandbox. Reference: Salesforce Help - Change Sets

Answer 207

D, An Approval Process is the appropriate functionality to ensure all free parts receive the marketing Questions and Answers PDF 124/150 director's sign-off. It allows for setting up a process for record approval. Reference: Salesforce Help - Approval Processes

Answer 208

A, 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. Reference: Salesforce Help - Permission Sets

Answer 209

B, C, To track the total number of trails associated with a park without writing code, the correct actions to take are: Use a roll-up summary field on the Park record to show the total number of Trails (B). Roll-up summary fields calculate and display a value in a master record based on the values of fields in a detail record. They are used to count, sum, average, or get the minimum/maximum of values in related detail records. Questions and Answers PDF 125/150 Use a master-detail relationship between the Park and Trail objects (C). Master-detail relationships are necessary for roll-up summary fields as they allow the master object to control certain behaviors of the detail object and summarize data from those detail records. A formula field (A) cannot dynamically count related records unless those records are linked via a master-detail relationship, and it cannot alone handle counts across related records without such a relationship. A lookup relationship (D) does not support roll-up summaries unless combined with additional tools like triggers or third-party apps, which involve coding or extra configuration outside standard object setup. For more details, refer to the Salesforce Help documentation on master-detail relationships and roll- up summary fields: Master-Detail Relationship: https://help.salesforce.com/articleView?id=relationships_considerations.htm&type=5 Roll-Up Summary Fields: https://help.salesforce.com/articleView?id=fields_about_roll_up_summary_fields.htm&type=5

Answer 210

B, The issue described occurs due to the settings in the master-detail relationship. Specifically: The Allow reparenting checkbox, Child records can be reparented to other parent records after they are created, is unchecked (B). This setting prevents changing the parent record (contact) of a child record (service plan) once it has been set. If 'Allow reparenting' is unchecked, it restricts the ability to change the associated contact, leading to the issue observed. The other options do not directly address the inability to change the associated contact on a service plan record. The 'Read Only' and 'Read/Write' settings (A and C) pertain to access rights to the detail records based on the master record's access but do not affect the ability to reparent a record. For a detailed understanding of master-detail relationships and their settings, including reparenting, see the Salesforce documentation on relationships: Master-Detail Relationships: https://help.salesforce.com/articleView?id=relationships_considerations.htm&type=5

Answer 211

B, To test code against a subset of production data under 5 GB and to refresh the sandbox environment weekly, the most suitable type of sandbox is: Partial Copy (B). A Partial Copy sandbox includes a copy of your production org's metadata and a subset of your production data as defined by the sandbox template. It allows up to 5 GB of data and can be refreshed every 5 days, making it ideal for scenarios where a representative sample of production data is needed for testing without the storage and refresh limitations of a Full Copy sandbox. Developer Pro (A) and Developer (D) sandboxes also allow for testing and development but do not include a subset of production data-they either have no data or only limited sample data. A Full Copy sandbox (C) provides a full replica of production data, far exceeding the 5 GB requirement and generally is refreshed less frequently due to larger data volume and longer copy times. Reference for sandbox types and their capabilities: Sandbox Types and Templates: https://help.salesforce.com/articleView?id=sf.data_sandbox_implementation_tips.htm&type=5 Questions and Answers PDF 128/150

Answer 212

A, To ensure process compliance where cases cannot revert to an earlier status and certain fields are required based on specific case criteria, the recommended solution is: Configure validation rules with help text (A). Validation rules enforce data integrity and business processes by preventing users from saving records if certain conditions are not met. For instance, a validation rule can prevent the status of a case from being changed back to an earlier status and can conditionally require fields based on other field values on the case. Dependent picklists (B) ensure field values depend on another field's value but do not enforce the inability to revert status. Approval processes (C) are used for step-by-step record approval and are not designed to prevent status reversion or conditionally require fields. Making fields required on the page layout (D) ensures they are always required when accessing the record through that layout but does not enforce conditional requirements based on other criteria. Reference for creating validation rules in Salesforce: Validation Rules: https://help.salesforce.com/articleView?id=sf.validation_rules.htm&type=5

Answer 213

B, Given the need to automate a welcome email including a customized survey with customization requirements and a tight timeline, the best approach is: Use Salesforce Flow to build the survey declaratively to meet the criteria and send it to the customer as an email (B). Flow is a powerful tool for automation in Salesforce, allowing the creation of complex workflows and user interactions without needing to write custom code. It can be used to build a survey and integrate it with email services for automated dispatch. Working with a developer to create custom Apex and LWC (A) might meet the criteria but would not align with the limited time frame. Managed (C) and unmanaged packages (D) from AppExchange can provide pre-built solutions, but they may not offer the needed customization or could require more setup time than building directly in Flow. Reference for automating processes with Salesforce Flow: Salesforce Flow: https://help.salesforce.com/articleView?id=sf.flow_considerations_design.htm&type=5

Answer 214

C, For an app builder who needs to ensure all fields from the page layout are visible on a Lightning Record Page after using the Lightning Object Creator, the correct component to use is: Record Detail (C). The Record Detail component automatically displays all fields that are included on the assigned page layout for the object. It is designed to reflect the layout configuration and is the simplest way to ensure all fields are presented as configured in the layout editor. Highlights Panel (A) is used primarily to display key fields at the top of the record page, providing a summary view rather than full field visibility. Recommendations (B) is used for displaying prompts or suggestions and does not display record fields. Path (D) is useful for displaying stages in a process (like sales stages or service processes) and does not show field data directly. Reference for setting up Lightning Record Pages and using components effectively: Lightning Record Pages: https://help.salesforce.com/articleView?id=sf.lightning_page_components.htm&type=5 Questions and Answers PDF 130/150

Answer 215

D, When creating a new field, if an app builder does not want the field to be automatically added to pre-existing custom report types, the step to take is: Deselect 'Add Field to Custom Report Types' (D). This option is available when creating or editing a custom field and ensures that the field is not automatically included in report types where 'Automatically add new custom fields to report type layouts' is enabled. Removing the field from page layouts (A) affects the visibility on record pages but not reports. Adjusting visibility (B) or setting read-only access (C) for report profiles affects user permissions to see the field in reports, but does not remove the field from report types if it was previously added. Reference for managing fields in custom report types: Custom Report Types and Fields: https://help.salesforce.com/articleView?id=reports_report_type_layouts.htm&type=5

Answer 216

B, For a formula to evaluate to true when the stage is set to "Negotiation/Review" and the close date is less than one week away, the correct formula is: Option B. This formula uses the ISPICKVAL function to check the text value of a picklist and compares the CloseDate to a week from today: AND( I AND( ISPICKVAL(StageName, "Negotiation/Review"), CloseDate - 7 < TODAY() )SPICKVAL(StageName, "Negotiation/Review"), CloseDate - 7 < TODAY() ) This formula checks that both conditions are met: it confirms the stage name is "Negotiation/Review" and that the CloseDate is within the next 7 days from the current date. Option A lacks the ISPICKVAL function necessary for evaluating picklist fields. Option C uses DAY(7) which is not a valid Salesforce formula expression. Option D also uses DAY(7) incorrectly and fails to use the ISPICKVAL function. Reference for creating formula fields in Salesforce: Formula Field Reference: https://help.salesforce.com/articleView?id=sf.customize_functions.htm&type=5

Answer 217

C, Formula fields in Salesforce can use various functions including text, mathematical, and logical functions to create simple or complex expressions. They can handle data from fields of the same record. Option C, "A combination of the Opportunity's Text and a Description fields," is a valid configuration for a formula field as it involves simple concatenation of text fields, which is supported. Options A, B, and D exceed the capabilities of formula fields: A: Hyperlinks to other objects using formula fields do not directly support navigation to parent records of a different object. B: Rich Text and HTML formatting are not supported in formula fields. D: Formula fields have limits in their complexity and field references which would make mixing Questions and Answers PDF 132/150 numerous fields from different related objects impractical and likely exceed formula size limits. Reference: Formula Field Overview on Salesforce Developer Guide

Answer 218

D, The "Accordion" Lightning component is designed to break up content into collapsible sections. This component would be suitable for managing the visibility of large numbers of fields by grouping them into separate tabs or sections that can expand and collapse. This makes navigation easier and declutters the interface. A: Highlights panel is used for displaying key record information at the top of the page and is not designed for managing multiple fields. B: Record detail displays all fields on a single layout, which does not suit the requirement to break up the fields. C: Field section does not exist as a standard Lightning component. Reference: Accordion Component in the Lightning Component Library

Answer 219

C, The "Sharing" button should be added to the Account page layout to allow sales reps to view the sharing details of an account record. This button enables users to see how access to the record is granted via roles, groups, and manual sharing. A: Sharing Hierarchy provides a view of the role hierarchy but does not specifically detail record Questions and Answers PDF 133/150 access. B: New Task is unrelated to sharing visibility. D: "Fait" is not recognized in Salesforce context as a valid component or feature. Reference: Sharing an Account in Salesforce Help Documentation

Answer 220

B, The best choice for capturing geographic location data, such as crossroads or location markers provided by customers, is the Geolocation field type. This field type stores latitude and longitude data, allowing accurate pinpointing of locations on a map. Geolocation fields are suitable for any application that needs to handle coordinates for mapping and proximity calculations. A: Number field is not specific enough for geographical coordinates. C: Reference fields link to other records, not geographical data. D: External Lookup is used to link to external objects, not for storing coordinates. Reference: Geolocation Custom Fields on Salesforce Help

Answer 221

C, An Approval Process is the appropriate feature to manage and enforce that new vendors accept terms on agreements before an opportunity can be closed. This process can be configured to require approvals from designated approvers when certain conditions are met, ensuring that all necessary agreements are in place and validated before proceeding. A: Email Alert cannot enforce acceptance of terms. Questions and Answers PDF 134/150 B: Dynamic Action primarily adjusts the user interface based on field values, not process management. D: Validation Rule only validates data entry and cannot handle complex conditional approvals. Reference: Approval Processes in Salesforce Documentation

Answer 222

D, The correct method to upgrade an unmanaged package that is installed in a production environment is to use the update link provided on the Installed Packages page. This process ensures that any modifications or additions in the package are properly integrated without the need to uninstall the previous version, thus preserving existing customizations and data. A: Uninstalling removes all associated data and customizations, which is not advisable. B: The Install Wizard is used for initial installations, not upgrades. C: Installing to a Developer org first is a testing step, not an upgrade path for production. Reference: Upgrading Unmanaged Packages on Salesforce Help

Answer 223

B, Criteria-based sharing rules are the best tool to use for automatically sharing records based on specific criteria, such as the opportunity type being "Service Agreement." This rule can share opportunities with all users in a particular role, such as the Service Manager role, when the criteria are met, thereby adhering to the private sharing model while still providing necessary access. A: Owner-based sharing rules focus on the record owner's role or group, not the record type. C: Apex sharing is used for more complex scenarios not easily handled by declarative sharing Questions and Answers PDF 135/150 settings. D: Manual sharing is not scalable or automatic. Reference: Using Criteria-Based Sharing Rules on Salesforce Help

Answer 224

A, D, Changing the data type of custom fields in Salesforce has specific limitations that need to be considered to ensure system integrity and prevent errors: A . It is not possible to change the data type of a formula field to any data type. Formula fields are calculated based on other field values and cannot be converted into a storage data type because they do not store data themselves. D . It is not possible to change the data type of a Text Area (Long) field to Text. Text Area (Long) fields support up to 131,072 characters, which far exceeds the 255 character limit of standard Text fields. Converting such a field to a smaller capacity field would potentially lead to data truncation or loss. For official guidance on data type changes, refer to Salesforce's Custom Field Considerations.

Answer 225

A, To display a weather map component on a Lightning record page conditionally: A . Component visibility should be used. This feature in the Lightning App Builder allows components on a Lightning page to be displayed based on specific criteria, such as field values or user attributes. Questions and Answers PDF 136/150 In this case, the app builder can set the visibility of the weather map component to only appear when a house is scheduled for a showing based on the relevant field values. For more details on setting up conditional component visibility, review the guide on Dynamic Lightning Pages.

Answer 226

B, To manage frequently changing picklist values effectively: B . Set up Global Values in Picklist Value Sets. This approach allows for centralized management of picklist values that can be reused across multiple fields and objects. By using global value sets, inactive values can be efficiently managed and deactivated without impacting fields that use these sets. For further information on managing picklists, check Salesforce's Picklist Management guide.

Answer 227

B, To import leads while preventing duplicates: B . Data Import Wizard is the appropriate tool. The Data Import Wizard in Salesforce includes functionality to check for duplicates based on matching records by certain criteria (like email or lead Questions and Answers PDF 137/150 ID) during the import process, thus preventing duplicate lead records from being created. More details on using the Data Import Wizard can be found in the Salesforce Data Import Wizard guide.

Answer 228

C, When attempting to change a master-detail relationship to a lookup relationship, Salesforce imposes specific restrictions to maintain data integrity: C . The Account record includes Parks roll-up summary fields. Master-detail relationships allow roll- up summary fields to aggregate data from child records onto the parent record. If any roll-up summary fields are present on the master object (Account in this case) that depend on the detail records (Parks), the relationship cannot be changed to lookup until these roll-up summary fields are removed. To resolve this, follow these steps: Identify and delete all roll-up summary fields on the Account object that reference the Park object. Convert the master-detail relationship to a lookup relationship. Recreate any necessary roll-ups using declarative tools like Process Builder or Flow if needed, as lookups do not support native roll-up summaries. For more guidance, review Salesforce's documentation on Changing Field Types.

Answer 229

B, To ensure data integrity where the Region field on the Contact object needs to be filled out conditionally based on the parent Account's status, a validation rule on the Contact is the most effective method: B . Create a validation rule on Contact. This rule can enforce that the Region field must be filled out for Contacts related to Accounts marked as 'High Priority'. Steps to create this validation rule: Navigate to Setup -> Object Manager -> Contact -> Validation Rules. Create a new validation rule. In the formula, use: AND( ISPICKVAL(Account.Customer_Status__c, 'High Priority'), ISBLANK(Region__c) ) ) Provide an error message to display when the rule is violated. Save and activate the rule. This validation rule checks that if a Contact is associated with an Account marked 'High Priority', the Region field cannot be blank. For further detail, Salesforce's Validation Rule Considerations provides additional guidance.

Answer 230

A, To create a custom object along with multiple fields and relationships efficiently from a single interface, the Schema Builder is the ideal tool: A . Schema Builder. This graphical tool provides a drag-and-drop interface for creating and modifying objects and fields in Salesforce, allowing for a visual layout of database schema. Steps to use Schema Builder: Go to Setup -> Schema Builder. Drag the 'Object' element into the schema area to create a new custom object. Define the object's properties (e.g., label, API name). Drag field elements like Text, Number, or Lookup into the object to create fields. Configure each field's properties according to your requirements. Questions and Answers PDF 139/150 Connect objects via lookup or master-detail relationships by dragging the relationship fields between them. Save the layout to create all elements in Salesforce. For more information, review Salesforce's Schema Builder documentation.

Answer 231

D, To ensure auditing users can access records in the Case_Issue__c junction object, the correct data permissions on related records must be established: D . Read-Only access on Case and Issue__c. Users need read-only access to both Case and Issue__c objects to view associated Case_Issue__c junction object records properly. This is because access to junction object records in Salesforce is determined by the user's access levels to the parent records in a relationship. Steps to configure access: Navigate to Setup -> Profiles or Permission Sets. Select the profile or permission set of the auditing users. Under Object Settings, adjust the permissions for Case and Issue__c to at least 'Read-Only'. Ensure that users have visibility to the Case_Issue__c object itself. This configuration allows users to view the details of cases and issues as they audit the junction object records.

Answer 232

C, To add components to the utility bar of an existing app: C . App Manager. This is where Salesforce apps are configured, including the utility bar which can house components like a chat tool, recent items list, or custom Lightning components. Steps to edit an app's utility bar: Navigate to Setup -> App Manager. Locate the desired app and click on the dropdown next to it -> select Edit. In the App Builder, navigate to the Utility Items tab. Click 'Add' to include new components to the utility bar. Configure the properties of the utility item as needed. Save the app configuration. For step-by-step instructions on modifying apps, see Salesforce's guide on Managing Apps in Lightning Experience.

Answer 233

D, For tracking whether contracts have been sent for Opportunities: D . Checkbox. This field type allows users to clearly indicate (Yes/No) whether a contract has been sent. This binary nature of checkboxes makes it simple to filter and report on Opportunities based on whether a contract was sent. Steps to configure this field: Navigate to Setup -> Object Manager -> Opportunity. Click Fields & Relationships -> New -> Checkbox. Define the field with a label (e.g., Contract Sent). Set the default value to false (unchecked). Add the field to the relevant page layouts. This setup facilitates accurate reporting and ensures that opportunities cannot be marked as "Closed Won" without indicating whether a contract was sent. For guidance on creating fields, see Salesforce's documentation on Custom Field Creation.

Answer 234

C, To restrict visibility of the Jupiter field on the Solar System object specifically to users with the Outer Planets profile: C . Field-level security (FLS). This allows the app builder to control access to fields based on user profiles. Steps to set up field-level security: Navigate to Setup -> Object Manager -> Solar System. Select Fields & Relationships -> Jupiter field. Click Field-Level Security. For all profiles except Outer Planets, set the Visible option to unchecked, ensuring these users cannot see the field. Questions and Answers PDF 142/150 For the Outer Planets profile, check Visible to grant access. This configuration ensures that only users with the Outer Planets profile can view the Jupiter field. For more information on field-level security, check Salesforce's guide on Field-Level Security.

Answer 235

A, To allow quick editing of a record's status and entering a due date from the record's feed in the Salesforce Mobile App: A . Custom action. This option enables users to perform specific tasks directly from the record page in the Salesforce Mobile App, such as editing fields. Steps to create a custom action: Navigate to Setup -> Object Manager -> select the relevant object. Click Buttons, Links, and Actions -> New Action. Set Action Type to 'Update a Record'. Configure the action layout to include the Status and Custom Due Date fields. Add the action to the Salesforce Mobile layout. This setup provides an efficient way for users to update key fields without navigating away from the record feed. For detailed setup instructions, see Salesforce's documentation on Creating Quick Actions.

Answer 236

B, C, For managers to respond to approval requests for opportunities above $50,000 in the Salesforce mobile app: B . In-App Notification: Managers receive notifications within the Salesforce mobile app when there is an approval request, allowing them to approve or reject directly from the notification. C . Record Detail: Managers can access the approval request directly from the Opportunity's detail page in the mobile app, where they can review and respond to the request. Steps to configure approval process notifications: Navigate to Setup -> Approval Processes -> select the relevant approval process. Ensure the process is active and configured to send notifications to approvers. Managers need to have the Salesforce mobile app configured to receive notifications. For best practices on managing approvals in Salesforce, see Approvals in Salesforce.

Answer 237

C, To manage field editability based on the opportunity status: C . Use field-level security on page layouts with record types to restrict editing fields. This combination allows for different layouts and editable fields based on the status of the record (e.g., closed or open). Steps to implement: Create or adjust record types for open and closed opportunities. For each record type, create a specific page layout. On the page layout for closed opportunities, set the majority of fields to read-only using field-level security, except for the 'Post-Close Follow-up Date' and 'Post-Close Follow-up Comments' fields. Assign the appropriate page layouts to the respective record types. Update profiles or permission sets to use these record types and page layouts accordingly. This setup ensures that sales reps can modify fields only when the opportunity is open, and the sales operations team can edit specific fields after closure. For more information on using record types and page layouts, check Salesforce's documentation on Record Types.

Answer 238

B, D, Questions and Answers PDF 145/150 To facilitate quick managerial sign-off on discounted opportunities: B . Dynamic Actions: Allows the display of specific actions on the Opportunity record page based on certain conditions, like the discount percentage. D . Approval Process: Configures a formal sign-off process for records meeting specific criteria, such as discount ranges between 20% to 30%. Steps to set up: Configure an approval process for opportunities where the discount is between 20% and 30%. Use Dynamic Actions to conditionally show the approval action directly on the Opportunity record page based on the discount percentage. This setup allows sales managers to efficiently review and approve discounted deals directly from the Opportunity record page. For guidance on setting up approval processes and dynamic actions, refer to Dynamic Actions in Salesforce.

Answer 239

B, The inability to create a Roll-Up Summary field in this context can be attributed to: B . The organization has Advanced Currency Management enabled. When Advanced Currency Management (ACM) is enabled, it affects how currency data is managed and aggregated, impacting the functionality of roll-up summary fields that involve currency amounts across different records. To address this limitation, consider using custom reporting or a custom solution like a trigger or a scheduled batch class to manually calculate and update the total. For more information on limitations with ACM, consult Salesforce's help article on Advanced Currency Management.

Answer 240

D, For automatically updating contact statuses when an account type changes: D . Record triggered flow. This type of automation can monitor changes in account types and accordingly update related records, such as contacts. Steps to implement: Navigate to Setup -> Flows. Create a new Flow and choose the record-triggered flow type. Configure the flow to trigger when the Account record is updated to 'Past-Customer'. Add an Update Records element to modify all related contacts, setting their status to 'Re-Market'. Activate the flow. This automation ensures that contact statuses are updated in real-time when their related account's type changes, maintaining data consistency and relevancy. For more on record-triggered flows, check out Salesforce's Record-Triggered Flows documentation.

Answer 241

B, For a customer service representative to collect information through a series of question prompts: B . Flow. Salesforce Flows allow for the creation of guided interactions that can prompt users for information in a step-by-step manner. Steps to create a flow for this purpose: Navigate to Setup -> Flows. Click on 'New Flow' and select a Screen Flow to interactively prompt users. Design the flow with Screen elements for each question. Add logic to process responses as necessary. Save and activate the flow. Embed or link the flow in a relevant location accessible to the service representative, such as on a record page or in the utility bar. Flows provide a flexible and powerful way to interactively gather and process customer data in real time. For detailed guidance on creating Flows, see Salesforce's Flow Builder documentation. Questions and Answers PDF 147/150

Answer 242

C, One of the limitations when using the Schema Builder for creating fields is: C . Cannot add fields to page layouts. While Schema Builder allows for easy visualization and creation of fields and objects, it does not support placing these fields onto specific page layouts directly from the Schema Builder interface. To place fields on page layouts, you need to: Navigate to Setup -> Object Manager -> select your object. Click on Page Layouts, choose the appropriate layout, and manually add the newly created fields. This step is necessary to ensure fields are visible and properly arranged on user interfaces. For more details, Salesforce's Schema Builder documentation outlines its capabilities and limitations.

Answer 243

C, To ensure sales reps input contacts into Salesforce rather than their personal devices: C . Enable offline create, edit, and delete in Salesforce for Android and iOS. This feature allows sales reps to enter contact information directly into the Salesforce Mobile App even when they are offline, which syncs back to Salesforce once connectivity is restored. Steps to enable offline capabilities: Navigate to Setup -> Mobile Administration -> Salesforce Mobile App -> Offline Settings. Configure offline settings to allow for creating, editing, and deleting records. Ensure that the Contact object is available for offline access. This functionality encourages reps to use Salesforce directly by mitigating connectivity constraints. Questions and Answers PDF 148/150 For implementation details, refer to Salesforce Mobile App Offline.

Answer 244

D, Upon adding a lookup field to Account from a custom object, Box: D. Accounts with Boxes. Salesforce automatically creates a new report type that reflects the relationship from the perspective of the parent object, in this case, Accounts, showing related Box records. This new report type enables users to create reports that list Accounts along with their associated Boxes, if any. For further understanding of report types and relationships, Salesforce's guide on Report Types provides comprehensive information on how these are structured following modifications to object relationships. Questions and Answers PDF 149/150 Questions and Answers PDF 150/150 Thank you for your visit.

Answer 245

Answer: B Questions and Answers PDF 106/150 Explanation: TODAY() is the function that should be used to return a date for calculating the difference between today and the date a marketing communication was sent. According to the Salesforce documentation, "TODAY() returns the current date as a Date value." DATETIMEVALUE() converts a text value into a Date/Time value. DATEVALUE() converts a Date/Time value into a Date value. NOW() returns the current Date/Time value. Question: 214

Answer 246

Answer: A, C, E Explanation: When activating a Lightning page from the Lightning App Builder, three options are available: Assign the page to a combination of apps and profiles. This option allows users to specify which apps and profiles will see the custom Lightning page instead of the default page. Make the page the org default. This option makes the custom Lightning page the default for all users in the org regardless of their app or profile. Make the page the default homepage for specific apps. This option allows users to set different homepages for different apps in Lightning Experience. [Source]

Answer 247

Answer: A, B, C Explanation: To deploy a new account detail page layout from sandbox to production, an app builder should include three components in the change set: Detail page layout: The page layout defines the arrangement of fields, buttons, related lists, and other components on a record detail or edit page. It also controls which fields are required or read- only for users. Source Custom fields: Custom fields are fields that are created by users to store additional information on standard or custom objects. Custom fields can have different data types, such as text, number, date, picklist, etc. Source Custom actions: Custom actions are actions that are created by users to extend the functionality of standard or custom objects. Custom actions can be global or object-specific, and they can invoke different tools such as Lightning components, Visualforce pages, flows, etc. [Source]

Answer 248

Answer: C Questions and Answers PDF 25/150 Explanation: One of the easiest ways to display real-time stock price for each account is to install a solution from the AppExchange, such as Stock Price Lightning Component3. This component can be added to any record page using the Lightning App Builder.

Answer 249

Answer: A, B, E Explanation: 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

Answer 250

Answer: A, C, D Explanation: Email alert, task, and invocable flow are three action types that can be used in an approval process. Email alert can send an email message to one or more recipients. Task can assign a task to a user or queue. Invocable flow can launch a flow that performs complex logic and actions

Answer 251

Answer: B, D Questions and Answers PDF 53/150 Explanation: Two conditions that can prevent inline editing on a list view are if the list view selected is the recently viewed list view, or if the list view contains more than one record type. The recently viewed list view does not support inline editing, as it is not based on a single object. The list view must have a single record type to enable inline editing, as different record types may have different fields and values

Answer 252

Answer: C Questions and Answers PDF 54/150 Explanation: Users will be unable to view the Account Interest records or the Interest records because they do not have read access to the Interest object. This is a standard behavior of Salesforce when a user does not have access to a related object

Answer 253

Answer: A Questions and Answers PDF 102/150 Explanation: 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

Untitled Deck Flashcards

(278 cards)