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

Actual exam question for Salesforce's Salesforce Certified Platform Development Lifecycle and Deployment Architect (Plat-Arch-202) exam

Question #: 31
Topic #: 7

[All Salesforce Certified Platform Development Lifecycle and Deployment Architect (Plat-Arch-202) Questions]

Universal Containers has three types of releases in their release management strategy: daily, minor (monthly), and major (quarterly). A user has requested a new report to support an urgent client request. What release strategy would an Architect recommend?

AUtilize the major release process to create the report directly in production bypassing the full sandbox.

BUtilize the minor release process to create the report directly in production bypassing the full sandbox.

CUtilize the major release process to create the report in a full sandbox and then deploy it to production.

DUtilize the daily release process to create the report directly in a full sandbox and then deploy it to production.

Show Suggested Answer

Suggested Answer: C

by Nicolette at Mar 09, 2024, 05:14 AM

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:

Submit Cancel

Cora

5 months ago

Not sure about bypassing the sandbox, seems risky!

upvoted 0 times

...

Bethanie

5 months ago

Totally agree, daily is best for quick turnarounds.

upvoted 0 times

...

Delsie

5 months ago

Surprised they’d consider major releases for something urgent!

upvoted 0 times

...

Alida

5 months ago

I think minor releases are more appropriate for this.

upvoted 0 times

...

Kristeen

6 months ago

Daily releases are the way to go for urgent requests!

upvoted 0 times

...

Gennie

6 months ago

I thought major releases were for bigger changes, so I’m not sure if that’s the right choice here. Daily seems more appropriate, but I need to double-check the guidelines.

upvoted 0 times

...

Wenona

6 months ago

I’m leaning towards option D, but I’m a bit confused about whether creating the report in a full sandbox first is necessary for urgent requests.

upvoted 0 times

...

Rolland

6 months ago

I remember practicing a similar question where we had to decide between major and minor releases. I feel like minor might take too long for urgent needs.

upvoted 0 times

...

Frederick

6 months ago

I think the daily release process might be the best option since it allows for quick changes, but I'm not entirely sure if that's the right approach for an urgent request.

upvoted 0 times

...

Xochitl

6 months ago

This is a great question to test our understanding of release management. I'll need to carefully consider the tradeoffs between speed, risk, and process for each option.

upvoted 0 times

...

Micheline

6 months ago

I've got a good handle on release management, so I think I can tackle this one. The key will be balancing the urgency of the request with the need for proper testing and deployment processes.

upvoted 0 times

...

Miesha

6 months ago

Okay, let's see. Since this is an urgent client request, I'm thinking the daily or minor release process might be the best approach to get it done quickly. But I'll need to double-check the details.

upvoted 0 times

...

Jacinta

6 months ago

Hmm, I'm a bit unsure about this one. I'll need to review the release management details to make sure I understand the differences between the options.

upvoted 0 times

...

Theron

6 months ago

This seems like a tricky one. I'll need to think carefully about the release management strategy and how it applies to this urgent client request.

upvoted 0 times

...

Filiberto

7 months ago

Okay, I've got this. The team should be using lead time, throughput, and due date performance to track their Kanban project. Those are the core Kanban metrics that will give them a good handle on their workflow and delivery.

upvoted 0 times

...

Darrin

7 months ago

I'm a bit unsure about this one. I'll need to make sure I understand the concepts of OAuth secrets and IAM registration before I can confidently select an answer.

upvoted 0 times

...

Nancey

7 months ago

Ah, this is a classic SQL question. The answer is definitely C. DROP TABLE is the way to go for deleting a table from your database.

upvoted 0 times

...

Claribel

7 months ago

Hmm, I'm a bit confused. I thought the primary key could be null and changeable, but I guess that's not the case. I'll have to review my notes on primary keys again.

upvoted 0 times

...

Rory

11 months ago

I hear the client's request is for a report that automatically generates cat GIFs. Gotta love those urgent priorities!

upvoted 0 times

Gwenn

10 months ago

That sounds like a fun request! Hopefully the report with cat GIFs can be created smoothly.

upvoted 0 times

...

Xuan

10 months ago

C) Utilize the major release process to create the report in a full sandbox and then deploy it to production.

upvoted 0 times

...

Noble

11 months ago

A) Utilize the major release process to create the report in a full sandbox and then deploy it to production.

upvoted 0 times

...

Glory

12 months ago

Hmm, daily release process, huh? That's a bold move, but I like it! D seems like the fastest way to get this report out there. As long as the sandbox testing is thorough, why not go for it?

upvoted 0 times

...

Terry

12 months ago

I'm with Phil on this one. Skipping the sandbox is a big no-no, even if it's an urgent request. C is the safest option.

upvoted 0 times

Anjelica

10 months ago

Skipping the sandbox can cause more issues in the long run.

upvoted 0 times

...

Letha

10 months ago

Yeah, it's important to follow the release process.

upvoted 0 times

...

Lorrine

11 months ago

I agree, C is definitely the safest option.

upvoted 0 times

...

Phil

12 months ago

Bypassing the sandbox? No way, that's a recipe for disaster! C is the way to go - use the major release process and make sure it's fully tested before deploying to production.

upvoted 0 times

Ernest

11 months ago

Definitely don't want to risk breaking anything in production. C is the way to go.

upvoted 0 times

...

Theron

11 months ago

Yeah, major release process ensures thorough testing before going live.

upvoted 0 times

...

Skye

11 months ago

I agree, bypassing the sandbox is risky. C sounds like the safest option.

upvoted 0 times

...

Brandee

1 year ago

I disagree. I think option D is better because it allows for quicker deployment and testing in a full sandbox.

upvoted 0 times

...

Billye

1 year ago

I agree with Anglea. Using the major release process ensures proper testing in a full sandbox before deploying to production.

upvoted 0 times

...

Anastacia

1 year ago

Wow, a new report for an urgent client request? I'd go with option D - the daily release process seems like the best way to get it done quickly without skipping the full sandbox.

upvoted 0 times