Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Salesforce Exam ADX-201 Topic 10 Question 70 Discussion

Actual exam question for Salesforce's ADX-201 exam
Question #: 70
Topic #: 10
[All ADX-201 Questions]

Cloud Kicks (CK) needs a new sales application. The administrator there is an application package on the AppExchange and wants to begin testing it in a sandbox to see If it addresses CK's needs.

What are two considerations when installing a managed package in a sandbox?

Choose 2 answers.

Show Suggested Answer Hide Answer
Suggested Answer: B, D

Two considerations when installing a managed package in a sandbox are:

The installation link has to be modified to test.salesforce.com, because the default installation link points to login.salesforce.com which is for production orgs. To install a package in a sandbox org, the administrator has to replace login with test in the installation URL before clicking it.

The package will be removed any time the sandbox is refreshed, because refreshing a sandbox replaces its current data and metadata with those from its source org. If the source org does not have the package installed, then the sandbox will lose it after refresh. Any metadata changes to the package do not have to be recreated in production, because they are preserved during upgrades unless overwritten by the package developer. Install for Admins Only is not the only install option available; there are also Install for All Users and Install for Specific Profiles options. Reference: https://help.salesforce.com/s/articleView?id=sf.distribution_installing_packages.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.data_sandbox_implementation_tips.htm&type=5


Contribute your Thoughts:

Winifred
3 months ago
I see your points, but I believe option C is also significant. We should remember that Install for Admins Only will be the only option available.
upvoted 0 times
...
Natalie
3 months ago
This is a classic case of 'read the fine print'. A and D are the obvious choices here. Unless CK wants to be rebuilding their package from scratch every time the sandbox refreshes.
upvoted 0 times
Barbra
1 months ago
D) The package will be removed any time the sandbox is refreshed.
upvoted 0 times
...
Sylvie
2 months ago
A) Any metadata changes to the package have to be recreated in production.
upvoted 0 times
...
...
Ty
3 months ago
I agree with Karrie, but I also think option D is crucial. We need to be aware that the package will be removed when the sandbox is refreshed.
upvoted 0 times
...
Krissy
3 months ago
I hope CK is not using a sandbox that's been sitting around since the 90s. The 'test.saiesiorcc.com' link sounds like something straight out of the Stone Age.
upvoted 0 times
...
Rene
3 months ago
B is just ridiculous. Who would ever need to modify the installation link just to test in a sandbox? C is also a bit off - there are more install options than just 'Install for Admins Only'.
upvoted 0 times
Casandra
2 months ago
Yeah, there are definitely more install options available than just 'Install for Admins Only'.
upvoted 0 times
...
Lavera
2 months ago
I agree, modifying the installation link seems unnecessary.
upvoted 0 times
...
...
Karrie
3 months ago
I think option A is important because we need to ensure any changes are replicated in production.
upvoted 0 times
...
Alline
3 months ago
A and D are definitely the correct answers. You don't want to be making metadata changes in the sandbox and then having to redo them in production, and the package will get wiped out with a sandbox refresh. Easy peasy.
upvoted 0 times
Santos
3 months ago
That makes sense. It's important to keep that in mind when testing out new applications in a sandbox environment.
upvoted 0 times
...
Mose
3 months ago
A and D are definitely the correct answers. You don't want to be making metadata changes in the sandbox and then having to redo them in production, and the package will get wiped out with a sandbox refresh. Easy peasy.
upvoted 0 times
...
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77