Salesforce Certified Platform Development Lifecycle and Deployment Architect (Plat-Arch-202) Exam - Topic 3 Question 36 Discussion
Salesforce Certified Platform Development Lifecycle and Deployment Architect (Plat-Arch-202) Exam - Topic 3 Question 36 Discussion
There are many types of quality assurance techniques that can help minimize defects in software projects.Which two techniques should an architect recommend, for Universal Containers to incorporate into its overall CI/CD pipeline?Choose 2 answers
D) Static code quality analysis
A) Business verification testing
B) Stress testing
C) Automated browser testing
Salesforce Certified Platform Development Lifecycle and Deployment Architect (Plat-Arch-202) Exam - Topic 3 Question 36 Discussion
Actual exam question for
Salesforce's
Salesforce Certified Platform Development Lifecycle and Deployment Architect (Plat-Arch-202) exam
I feel like business verification testing is more about ensuring requirements are met rather than minimizing defects. I’d probably go with static code analysis and automated browser testing.
Stress testing sounds familiar, but I’m not convinced it fits into a CI/CD pipeline as well as the others. I might lean towards automated testing instead.
I'm not entirely sure, but I think static code quality analysis helps identify potential bugs before they become a problem. Maybe that’s one of the answers?
Business verification testing and stress testing - those are the two that come to mind for me. The question is asking about techniques to minimize defects, so those seem like good options to recommend.
Okay, I've got this. Automated browser testing and static code quality analysis are two key techniques that can help catch defects early in the development process. I'll make sure to select those.
Hmm, I'm a bit unsure about this. I know we covered quality assurance in class, but I'm having trouble remembering the specific techniques that would work best in a CI/CD pipeline.
I remember practicing a similar question where we discussed how unknown devices should be handled, and I think it had to do with rejecting them or dropping connections.
Hmm, I'm not totally sure about this one. The wording is a bit vague, and I'm not confident I have enough background knowledge to nail the right answer. I'll have to think it through carefully.
Ooh, look at us, the software quality assurance experts! I'm feelin' C and D, like the rest of the gang. Though I do wonder if they have a 'Jokester' testing technique hidden in there somewhere...
Business verification testing? What is this, a test for my entrepreneurial skills? I'll stick with the good old C and D, thank you very much. Automated browser testing and static code analysis - the dynamic duo of defect minimization!
Stress testing, huh? Sounds like a party! But I think I'll go with C and D as well. Gotta make sure that code is as clean as a whistle before it hits production, am I right?
Ah, the age-old question of how to minimize defects in software projects. Looks like the architect needs to recommend some solid techniques from this list. I'm going with C and D - automated browser testing and static code quality analysis. Can't go wrong with those!
Lashunda
6 months agoChristene
6 months agoMattie
7 months agoTambra
7 months agoKenia
7 months agoShelia
7 months agoShaunna
8 months agoErick
8 months agoDelmy
8 months agoEdelmira
8 months agoSunshine
8 months agoAlica
8 months agoAmos
8 months agoAja
8 months agoMaia
8 months agoEmeline
8 months agoLeonora
8 months agoDorethea
1 year agoLigia
12 months agoDeeanna
1 year agoIola
1 year agoTruman
1 year agoDona
1 year agoDominga
1 year agoCarlton
1 year agoRicarda
1 year agoAnnmarie
1 year agoVallie
1 year agoHillary
1 year agoTijuana
1 year agoDelisa
1 year agoTiera
1 year agoMarguerita
1 year agoCaren
1 year ago