Object Manager and Lightning App Builder

The ampersand (&) operator is the correct operator used in Salesforce formula fields to concatenate text strings together. This is a fundamental concept in Salesforce formula writing.

For example, if you want to combine a First Name and Last Name field, you would write:
FirstName & ' ' & LastName

This would produce output like 'John Smith'.

The other answers are incorrect for the following reasons:

• The plus (+) operator in Salesforce formulas is used for mathematical addition of numeric values, not for text concatenation. Using + with text strings would result in an error.

• There is no concatenation (&&) operator in Salesforce. The double ampersand does not exist as a valid operator for string manipulation in formula fields.

• The pipe (|) operator is not used for text concatenation in Salesforce. Pipe characters are sometimes used in other programming contexts or as delimiters, but they are not a valid concatenation operator in Salesforce formula fields.

When an administrator converts a standard picklist field to use a Global Value Set, the field becomes linked to that centralized value set. This is the fundamental purpose of Global Value Sets - to provide a single, centralized location where picklist values can be managed and shared across multiple picklist fields on different objects.

Once converted, the picklist field no longer maintains its own independent list of values. Instead, it inherits and displays the values from the Global Value Set. Any future additions, modifications, or deletions to the picklist values must be performed at the Global Value Set level, and these changes will automatically propagate to all fields using that Global Value Set.

The other answers are incorrect for the following reasons:

• The option suggesting the field retains original values locally while synchronizing for backup is incorrect. There is no dual storage or backup synchronization mechanism. The field fully adopts the Global Value Set and does not maintain a separate local copy.

• The option about creating a copy and maintaining dual management capabilities is also incorrect. Converting to a Global Value Set is a one-way process that centralizes management. You cannot manage values both locally and globally for the same field.

• The option stating that the field loses all dependent picklist relationships and validation rules is incorrect. When converting to a Global Value Set, existing dependent picklist relationships and validation rules are preserved, assuming the values they reference still exist in the Global Value Set. Salesforce does not automatically delete these configurations during the conversion process.

When configuring a lookup relationship in Salesforce, administrators have three specific options for handling what happens when a parent record is deleted:

1. Clear the value of this field - This is the default behavior where the lookup field on the child record is simply cleared (set to null) when the parent record is deleted.

2. Don't allow deletion of the lookup record that's part of a lookup relationship - This prevents the parent record from being deleted if there are any child records referencing it.

3. Delete this record also - This cascade delete option removes the child record when the parent record is deleted.

These three options are configured individually for each lookup relationship, giving administrators granular control over deletion behavior.

The other answers are incorrect for the following reasons:

• The option describing cascading updates that modify field values when parent records are edited does not exist in Salesforce lookup relationship configuration. Lookup relationships don't have built-in cascading update functionality.

• There is no organization-wide default cascade behavior setting. Each lookup relationship is configured individually with its own deletion behavior, not a single uniform setting across all relationships.

• Automatic reparenting to transfer child records to a backup parent is not a feature available in Salesforce lookup relationships. When a parent is deleted, records can either be deleted, have the field cleared, or the deletion can be blocked - there is no automatic reassignment to another parent record.