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
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Salesforce Certified Platform Development Lifecycle and Deployment Architect (Plat-Arch-202) Exam - Topic 5 Question 39 Discussion

Universal Containers has a complex deployment coming up. The deployment will include several Apex classes which depend on custom settings that hold important configuration. How should an Architect manage this deployment?
C) Create a custom metadata type and include this in your deployment to production
A) Script the deployment of all functionality via the Force.com Migration Tool
B) Manually deploy and populate custom settings in production using a change set
D) Manually deploy and populate the custom settings in production prior to the Apex Class deployment

Salesforce Certified Platform Development Lifecycle and Deployment Architect (Plat-Arch-202) Exam - Topic 5 Question 39 Discussion

Actual exam question for Salesforce's Salesforce Certified Platform Development Lifecycle and Deployment Architect (Plat-Arch-202) exam
Question #: 39
Topic #: 5
[All Salesforce Certified Platform Development Lifecycle and Deployment Architect (Plat-Arch-202) Questions]

Universal Containers has a complex deployment coming up. The deployment will include several Apex classes which depend on custom settings that hold important configuration. How should an Architect manage this deployment?

Show Suggested Answer Hide Answer
Suggested Answer: C

by Della at Jun 21, 2024, 05:17 PM

Limited Time Offer

25%

Off

Get Premium Salesforce Certified Platform Development Lifecycle and Deployment Architect (Plat-Arch-202) Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Refugia
9 months ago
Wait, can you really use custom metadata for this?
upvoted 0 times
...
Carry
10 months ago
D is a bit risky, better to script it all.
upvoted 0 times
...
Stephane
10 months ago
C sounds interesting, but is it really necessary?
upvoted 0 times
...
Florinda
10 months ago
I disagree, B seems safer for custom settings.
upvoted 0 times
...
Victor
10 months ago
A is the way to go, automation is key!
upvoted 0 times
...
Deane
10 months ago
I recall that manually populating custom settings can be error-prone. Option B seems risky, but I guess it might be necessary if the settings are complex.
upvoted 0 times
...
Melina
11 months ago
I think custom metadata types are a newer concept we learned about. Option C sounds interesting, but I’m not clear on how it would work with existing Apex classes.
upvoted 0 times
...
Yvonne
11 months ago
I feel like we practiced a similar question where scripting the deployment was emphasized. Option A could streamline the process, but I wonder if it covers the custom settings properly.
upvoted 0 times
...
Ahmed
11 months ago
I remember we discussed the importance of managing dependencies in deployments, especially with custom settings. I think option D makes sense, but I'm not entirely sure if it's the best approach.
upvoted 0 times
...
Kip
11 months ago
I'm a bit confused by the custom metadata type option. I'll need to research that a bit more to understand how it differs from the other choices. But I'm leaning towards option D as the safest bet.
upvoted 0 times
...
Narcisa
11 months ago
This seems straightforward to me. Scripting the entire deployment with the Migration Tool (option A) is probably the most reliable and efficient approach here.
upvoted 0 times
...
Garry
11 months ago
Okay, I think I've got a handle on this. The key is to make sure the custom settings are properly deployed and populated before the Apex classes that depend on them. I'll likely go with option C or D.
upvoted 0 times
...
Barrett
11 months ago
Hmm, I'm a bit unsure about this one. I'll need to review the details on custom settings and deployment options to decide the best approach.
upvoted 0 times
...
Daron
11 months ago
This looks like a tricky one. I'll need to think through the options carefully to make sure I understand the implications of each approach.
upvoted 0 times
...
Cristy
11 months ago
Hmm, I'm not totally sure about this one. The options don't seem to provide a lot of context, so I'll have to think it through carefully before selecting an answer.
upvoted 0 times
...
Rima
11 months ago
Okay, let me see here. I'm a bit confused about the requirements, but I'll try to break this down step-by-step.
upvoted 0 times
...
Goldie
1 year ago
Deployment headaches? More like deployment nightmares! Glad I'm not the one in charge of this. But hey, at least I'll get to watch the show from the sidelines!
upvoted 0 times
Rosamond
1 year ago
C) Create a custom metadata type and include this in your deployment to production
upvoted 0 times
...
Reid
1 year ago
B) Manually deploy and populate custom settings in production using a change set
upvoted 0 times
...
Marylyn
1 year ago
A) Script the deployment of all functionality via the Force.com Migration Tool
upvoted 0 times
...
...
Beatriz
1 year ago
Option B? Really? Are we living in the stone age? I'd rather use a carrier pigeon than a change set. C all the way, baby!
upvoted 0 times
...
Refugia
1 year ago
Ah, the age-old question of deployment woes. Option C sounds like the most efficient way to go. Less headaches, more productivity!
upvoted 0 times
...
Stephaine
1 year ago
You know, I once tried to manually deploy custom settings. Let's just say, it didn't end well. Option D is not for me, I'm sticking with C!
upvoted 0 times
...
Sherita
1 year ago
I'm not a fan of manual deployments, they're just too risky. I'd go with Option A and script the whole thing using the Migration Tool. Bulletproof!
upvoted 0 times
Jenise
1 year ago
Margo: Bulletproof solution for sure!
upvoted 0 times
...
Veronika
1 year ago
User 3: Definitely, using the Force.com Migration Tool is the way to go.
upvoted 0 times
...
Margo
1 year ago
User 2: Option A sounds like the safest bet, scripting the deployment.
upvoted 0 times
...
Marisha
1 year ago
User 1: I agree, manual deployments are too risky.
upvoted 0 times
...
...
Garry
1 year ago
Option C is the way to go! Creating a custom metadata type is the best approach to manage complex deployments with custom settings. Easy peasy!
upvoted 0 times
Glennis
1 year ago
C) Create a custom metadata type and include this in your deployment to production
upvoted 0 times
...
Luis
1 year ago
B) Manually deploy and populate custom settings in production using a change set
upvoted 0 times
...
Vashti
1 year ago
A) Script the deployment of all functionality via the Force.com Migration Tool
upvoted 0 times
...
...
Shayne
1 year ago
That's a good point, Adelle. Custom metadata types can definitely simplify the deployment process.
upvoted 0 times
...
Adelle
1 year ago
I disagree, I believe option C is better. Using custom metadata types can help manage configuration more effectively.
upvoted 0 times
...
Shayne
1 year ago
I think option A is the best choice. It's efficient and ensures everything is deployed correctly.
upvoted 0 times
...

Save Cancel