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

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

Question #: 60
Topic #: 3

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

Universal Containers is building a custom application on the Force.com platform. There is a budget and release date that has been set by the board of directors, but the application must meet the requirements that will be submitted and voted on by a public user community. What is the risk associated with the scenario?

AThe requirements should not be solicited by an external community

BThe project is not using the Waterfall methodology

CThe project is not using an Agile methodology

DThe requirements are unknown and the release date has been set.

Show Suggested Answer

Suggested Answer: D

by Carlton at May 02, 2025, 08:22 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:

Submit Cancel

Gracia

2 months ago

Totally agree, external community input can be risky!

upvoted 0 times

...

Kristian

2 months ago

Wait, can they really set a release date without clear requirements?

upvoted 0 times

...

Junita

3 months ago

I think they should have gone Agile for this project.

upvoted 0 times

...

Lizbeth

3 months ago

The requirements are definitely unknown with a set release date.

upvoted 0 times

...

Aja

3 months ago

Not sure if the Waterfall method is the issue here.

upvoted 0 times

...

Luther

3 months ago

I think the main risk is that the requirements are unknown while the deadline is fixed. That seems like a recipe for disaster!

upvoted 0 times

...

Clement

3 months ago

I feel like we talked about Agile vs. Waterfall methodologies, but I'm not clear on how that applies here.

upvoted 0 times

...

Kiley

4 months ago

I’m not entirely sure, but I think the risk might be related to the unknown requirements. That sounds familiar from practice questions.

upvoted 0 times

...

Corrinne

4 months ago

I remember discussing how setting a release date without clear requirements can lead to major issues.

upvoted 0 times

...

Lavonna

4 months ago

This is a good one. I think I know where the risk lies, but I want to double-check my reasoning before selecting an answer.

upvoted 0 times

...

Antonio

4 months ago

Okay, I've got a few ideas on this. Gonna jot down some notes and see if I can identify the biggest risk factor.

upvoted 0 times

...

Jacquelyne

4 months ago

Hmm, not sure I fully understand the scenario. I'll need to re-read the question and think through the potential risks.

upvoted 0 times

...

Nenita

5 months ago

The key here is understanding the relationship between the public community, the requirements, and the fixed budget and timeline. Gotta be strategic in my approach.

upvoted 0 times

...

Valene

5 months ago

This seems like a tricky one. I'll need to think through the different risks carefully.

upvoted 0 times

...

Daron

8 months ago

I'm going with D too. Trying to build an app without knowing what the users want, while being on a tight deadline? That's like trying to bake a cake without a recipe - it's not gonna end well!

upvoted 0 times

Chaya

7 months ago

User 2: I agree, it's like shooting in the dark. We need those requirements to guide us.

upvoted 0 times

...

Jean

8 months ago

User 1: I think D is the biggest risk here. How can you build something without knowing what the users want?

upvoted 0 times

...

Alba

8 months ago

D is the way to go here. Unknown requirements and a set release date? That's a disaster waiting to happen. Might as well just roll the dice and see what comes up!

upvoted 0 times

...

Shawnda

8 months ago

I'm going with D as well. Trying to build an app without clear requirements and a fixed deadline? That's a recipe for disaster. Might as well just throw darts at a board to decide the features.

upvoted 0 times

Magda

7 months ago

I'm going with D as well. Trying to build an app without clear requirements and a fixed deadline? That's a recipe for disaster. Might as well just throw darts at a board to decide the features.

upvoted 0 times

...

Johnna

7 months ago

D) The requirements are unknown and the release date has been set.

upvoted 0 times

...

Mike

7 months ago

B) The project is not using the Waterfall methodology

upvoted 0 times

...

Eve

8 months ago

A) The requirements should not be solicited by an external community

upvoted 0 times

...

Reid

9 months ago

I think not involving the external community in gathering requirements could also be a risk, as their input could be valuable.

upvoted 0 times

...

Allene

9 months ago

I believe using an Agile methodology could help mitigate this risk by allowing for flexibility in requirements.

upvoted 0 times

...

Rosio

9 months ago

Hmm, I think the correct answer is D. If the requirements are unknown and the release date has been set, that's definitely a huge risk. That's like trying to hit a moving target while blindfolded!

upvoted 0 times