When configuring a change set, which two practices should an administrator adhere to in order to ensure a successful deployment to production?
Choose 2 answers
Two practices that the administrator should adhere to in order to ensure a successful deployment to production are:
Add permissions and access settings to outbound change sets in addition to the dependent component list. This can help avoid deployment errors or access issues caused by missing permissions or settings for the components in the change set. For example, if the change set includes a new custom object, the administrator should also include the object permissions, field-level security, page layouts, and record types for that object.
Run deployment validations on the change set in the sandbox prior to uploading to production. This can help test the change set for any errors or conflicts before deploying it to production. Deployment validations simulate the deployment without actually making any changes and report any issues or warnings.
The other two options are incorrect because:
Cloning a change set does not add forgotten dependent components to an uploaded change set. It only creates a copy of the existing change set that can be modified before uploading.
When deploying a new record type, it is not necessary to have it as the only component in the change set. It can be deployed along with other components as long as they are compatible and have the required dependencies.
What would prevent a user from syncing a quote with an opportunity?
Another quote is already synced with the opportunity will prevent a user from syncing a quote with an opportunity. Only one quote can be synced with an opportunity at a time. If a user tries to sync another quote, they will get an error message saying that the opportunity already has a synced quote. Reference: https://help.salesforce.com/s/articleView?id=sf.quotes_syncing.htm&type=5
The administrator at Ursa Major Solar has set up IT policies for all user passwords to be a minimum length of 3 characters and have an expiration period of 90 days. The security team recently decided that administrators of any system should have a 15-character minimum password with a 30-day expiration period.
Where should the administrator make this change?
Password Policies on the System Administrator profile is a feature that allows administrators to set different password requirements for users with different profiles. Password Policies can specify the minimum length, complexity, expiration period, history enforcement, lockout interval, and warning message for passwords. Password Policies can be used to enforce stricter password requirements for system administrators than for other users
An administrator at Cloud kicks recently built a screen flow in a sandbox that creates a case and follow-up task. When the flow runs in the sandbox, it works just as expected. When tested in production, the flow errors when creating the records.
Choose 2 answers
Opening the flow in Debug mode and running it as another user allows simulating how the flow behaves for different users with different permissions and settings. This can help identify any issues related to user
Cloud Kicks has o custom object called Membership Details that records information about customers' preferences for their memberships. Depending, on the membership level, different data needs to be displayed.
* when cue running user has the Market no profile, all data should be visible.
* When the running user has the Support profile, only the Support preference fields should be visible.
* Both Marketing and Support users should be able to report on all data.
How should the administrator deliver this solution?
Use Field-Level Security to control data access is how the administrator should deliver this solution. Field-Level Security is a way to restrict users' access to view or edit specific fields on an object based on their profile or permission set. Field-Level Security can be used to make fields visible or hidden, and editable or read-only for different users. By using Field-Level Security, the administrator can ensure that only Marketing users can see all data on the Membership Details object, while Support users can only see the Support preference fields.
Barrie
1 months agoWillodean
1 months agoJimmie
2 months agoGail
3 months agoBeatriz
3 months agoCathrine
3 months agoVivienne
5 months agoRicarda
5 months agoPatrick
5 months agoGail
6 months agoPhyliss
6 months agoTabetha
6 months agoRamonita
7 months agoDannie
7 months agoJolanda
7 months agoCarmen
7 months agoArdella
7 months agoAngelo
8 months agoBernardine
8 months agoJeannetta
8 months agoRaelene
8 months agoEmilio
8 months agoBeckie
9 months agoMerissa
9 months agoTrina
9 months agoMollie
9 months agoIsadora
9 months agoRosita
10 months agoBonita
10 months agoStephane
10 months agoJani
10 months agoNatalya
11 months agoMarg
11 months agoRaul
11 months agoYuette
11 months agoArt
1 years agoGlory
1 years agoDiane
1 years agoMarshall
1 years agoMinna
1 years agoSantos
1 years ago