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

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

Question #: 40
Topic #: 8

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

There has been an increase in the number of defects .Universal Containers (UC) found the root cause to be decreased in quality if code. Which two options can enforce code quality in UC's continuous integration process? Choose 2 answers

AIntroduce manual code review before deployment to the testing sandbox.

BIntroduce manual code review before deployment to the production org.

CIncrease the size of the testing team assigned to the project.

DIntroduce static code analysis before deployment to the testing sandbox.

Show Suggested Answer

Suggested Answer: A, D

by Adelina at Jun 28, 2024, 02:47 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

Hillary

3 months ago

Increasing the testing team? Not sure that solves the root issue.

upvoted 0 times

...

Mona

3 months ago

Definitely A and D! Can't skip on code quality.

upvoted 0 times

...

Luis

3 months ago

Wait, are we really relying on manual reviews? Seems risky.

upvoted 0 times

...

Gail

4 months ago

I think static code analysis is way more effective.

upvoted 0 times

...

Lonna

4 months ago

A manual code review before deployment is a must!

upvoted 0 times

...

Fernanda

4 months ago

I’m leaning towards manual code reviews before deployment to the testing sandbox, but I also think static analysis is a solid option too.

upvoted 0 times

...

Clemencia

4 months ago

I feel like increasing the testing team size might not directly improve code quality, but it could help with overall coverage.

upvoted 0 times

...

Cassandra

4 months ago

I think introducing static code analysis could really help catch issues early, but I can't recall if it was specifically mentioned for the testing sandbox.

upvoted 0 times

...

Luis

5 months ago

I remember discussing the importance of code reviews in our study group, but I'm not sure if manual reviews before production or testing are more effective.

upvoted 0 times

...

Earleen

5 months ago

Manual code review is always a good practice, but I'm not sure if that's the best approach for a continuous integration process. I'll have to weigh the pros and cons.

upvoted 0 times

...

Clorinda

5 months ago

Introducing static code analysis before the testing sandbox seems like a great way to catch issues early on. That's definitely one I'll consider.

upvoted 0 times

...

Claudio

5 months ago

Hmm, I'm a bit unsure about this one. I'll need to think through the different options and how they relate to enforcing code quality.

upvoted 0 times

...

Elke

5 months ago

This seems like a straightforward question. I'd focus on the two options that directly address code quality in the continuous integration process.

upvoted 0 times

...

Lilli

5 months ago

This seems straightforward - I think the answer is B, defining a TACACS server group for authentication in the switch configuration.

upvoted 0 times

...

Sylvie

5 months ago

Yeah, that makes sense to me. Without knowing the key actors and their needs, it would be hard to determine the right flow and acceptance criteria.

upvoted 0 times

...

Glendora

9 months ago

Option B for manual review before production is a no-go. I don't want my code to go through that much scrutiny!

upvoted 0 times

...

Karol

9 months ago

Haha, they should just throw the entire codebase into a black hole and start over! That'll solve the quality issues.

upvoted 0 times

...

Rosann

9 months ago

I don't think increasing the testing team size will really help with the root cause of decreased code quality. That's just treating the symptoms.

upvoted 0 times

Rozella

8 months ago

B) Introduce manual code review before deployment to the production org.

upvoted 0 times

...

Dacia

8 months ago

I agree, manual code review and static code analysis can help improve code quality.

upvoted 0 times

...

Val

8 months ago

D) Introduce static code analysis before deployment to the testing sandbox.

upvoted 0 times

...

Delmy

9 months ago

A) Introduce manual code review before deployment to the testing sandbox.

upvoted 0 times

...

Troy

10 months ago

I agree, and option D with static code analysis is also a great way to enforce code quality.

upvoted 0 times

Rosendo

8 months ago

Yes, static code analysis can catch potential issues early on.

upvoted 0 times

...

Venita

8 months ago

D) Introduce static code analysis before deployment to the testing sandbox.

upvoted 0 times

...

Nana

9 months ago

A) Introduce manual code review before deployment to the testing sandbox.

upvoted 0 times

...

Lonna

10 months ago

A manual code review before deployment to the testing sandbox seems like a good idea to catch issues early on.

upvoted 0 times

Larae

9 months ago

D) Introduce static code analysis before deployment to the testing sandbox.

upvoted 0 times

...

Junita

10 months ago

A) Introduce manual code review before deployment to the testing sandbox.

upvoted 0 times

...

Zona

11 months ago

Increasing the testing team size might help too, but I believe focusing on code review and analysis is more effective.

upvoted 0 times

...

Gladis

11 months ago

I agree with Jess. Manual code review and static code analysis are crucial in catching defects early.

upvoted 0 times

...

Jess

11 months ago

I think option A and D can help enforce code quality.

upvoted 0 times

...