Deal of The Day! 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 7 Question 57 Discussion

Actual exam question for Salesforce's ADX-201 exam
Question #: 57
Topic #: 7
[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:

Reta
3 months ago
Testing managed packages in a sandbox is a great idea, but you have to be careful about the implications. These considerations are really important to keep in mind.
upvoted 0 times
Teri
3 months ago
D) The package will be removed any time the sandbox is refreshed.
upvoted 0 times
...
Carissa
3 months ago
D) The package will be removed any time the sandbox is refreshed.
upvoted 0 times
...
Beckie
3 months ago
A) Any metadata changes to the package have to be recreated in production.
upvoted 0 times
...
Felicitas
3 months ago
A) Any metadata changes to the package have to be recreated in production.
upvoted 0 times
...
...
Casie
4 months ago
Haha, 'test.saiesiorcc.com'? Sounds like a typo, not a real consideration. Good thing Option B is not the correct answer!
upvoted 0 times
Minna
3 months ago
D) The package will be removed any time the sandbox is refreshed.
upvoted 0 times
...
Burma
3 months ago
A) Any metadata changes to the package have to be recreated in production.
upvoted 0 times
...
...
Lyla
4 months ago
I see both points. It's crucial to plan ahead for these scenarios. We should definitely keep these considerations in mind while testing the managed package in sandbox.
upvoted 0 times
...
Rupert
4 months ago
I think Option C is a bit misleading. The 'Install for Admins Only' option is not the only one available, just one of the choices.
upvoted 0 times
...
Dorothea
4 months ago
Option D is also important - the package will be removed when the sandbox is refreshed, so you need to be aware of that limitation.
upvoted 0 times
Julian
3 months ago
D) The package will be removed any time the sandbox is refreshed.
upvoted 0 times
...
Fernanda
4 months ago
A) Any metadata changes to the package have to be recreated in production.
upvoted 0 times
...
...
Margurite
4 months ago
Option A is correct, any metadata changes in the sandbox will need to be recreated in production. That's definitely a key consideration when testing managed packages.
upvoted 0 times
...
Tamie
4 months ago
I agree with Arlette, it's crucial to consider that. But I also think option D is important because we need to be aware that the package will be removed after sandbox refresh.
upvoted 0 times
...
Arlette
4 months ago
I think option A is important because we have to make sure any changes made in sandbox are replicated in production.
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