MENU
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
Suggested Answer: C, D
Get Premium ADX-211 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
27 comments · newest first
CY
Cyndy
12 months ago
I thought you could just add everything in one go?
LI
Lino
12 months ago
Adding permissions is super important too!
EL
Elliot
12 months ago
Wait, are you saying to clone change sets? Seems risky.
JA
Jacquline
1 year ago
I agree, that's a must!
AR
Arthur
1 year ago
Definitely need to run deployment validations first!
MI
Miriam
1 year ago
I feel like we discussed that having only one component in a change set for a new record type might not be necessary. It seems a bit restrictive.
TA
Tasia
1 year ago
Cloning a change set to add forgotten components sounds familiar, but I’m not confident if it’s the best practice.
ST
Stefany
1 year ago
I’m not entirely sure, but I think adding permissions and access settings is also crucial for outbound change sets.
MO
Mohammad
1 year ago
I remember we talked about running deployment validations in the sandbox before uploading to production. That seems really important.
MA
Marguerita
1 year ago
Okay, I've got this. The key here is that the office manager wants to donate the old workstations, so the relevant standard is Device and Media Controls. That makes B the correct answer.
GL
Glenna
1 year ago
The question mentions the "VRP platform", so I'm guessing the shortcut might be different from the standard Ctrl+P. I'll have to read the options closely and see if any of them stand out as the VRP-specific method.
LO
Louis
1 year ago
This is a good one. I feel pretty confident that analyzing the emerging tech and related training needs is going to be the most comprehensive approach to get IT ready for the transformation. I'll select that option unless I see something that makes me think otherwise.
AL
Alaine
1 year ago
A) Clone a change set? Is that like using the 'Ctrl + C, Ctrl + V' method of software development? No wonder they call it a 'change set' and not a 'change set-and-forget-set'.
GE
Gerald
1 year ago
D? Seriously? Only one component in the change set? What is this, a kindergarten play? I'm going with C and D, the real pros' choices.
JO
Jospeh
1 year ago
B? What is this, amateur hour? Permissions and access settings? That's just asking for a security breach. C and D all the way, baby!
VI
Vicky
1 year ago
D) When deploying a new record type, ensure the new record type is the only component in the change set.
LA
Lamonica
1 year ago
C) Run deployment validations on the change set in the sandbox prior to uploading to production.
TO
Tomoko
1 year ago
A? Really? Cloning a change set? That's just asking for trouble. I'll stick with the tried and true C and D.
DE
Devorah
1 year ago
D) When deploying a new record type, ensure the new record type is the only component in the change set.
PE
Pearlene
1 year ago
C) Run deployment validations on the change set in the sandbox prior to uploading to production.
JO
Joanna
1 year ago
C and D are definitely the way to go. You don't want any hidden surprises in your change set, and validating before production is just common sense.
SH
Shasta
1 year ago
Adding permissions and access settings to outbound change sets is important to ensure a smooth deployment process.
SH
Shenika
1 year ago
Running deployment validations in the sandbox is crucial to catch any errors before deploying to production.
FR
Francesco
1 year ago
C and D are definitely the way to go. You don't want any hidden surprises in your change set, and validating before production is just common sense.
ME
Merilyn
2 years ago
I see your point, Antonette. But I believe B is also necessary to ensure proper permissions are set during deployment.
AN
Antonette
2 years ago
I agree with you, Stephanie. But I also think A is crucial to avoid missing any dependent components.
ST
Stephanie
2 years ago
I think C is important to make sure everything is validated before going to production.