Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Cisco Exam 300-910 Topic 3 Question 80 Discussion

Actual exam question for Cisco's 300-910 exam
Question #: 80
Topic #: 3
[All 300-910 Questions]

An IT team at a SaaS company has this Cl/CD pipeline

Developers push code to the central repository by using Git.

The code is packaged and sent by an automated process to the staging environment where the tests are executed again automatically

If the automated tests pass in staging the code is pushed to production

Which change improves the Cl/CD pipeline?

Show Suggested Answer Hide Answer
Suggested Answer: C

Contribute your Thoughts:

Therese
4 months ago
Exactly, having developers run unit tests manually might slow down the process.
upvoted 0 times
...
Lindsey
4 months ago
I see your point, but having automated tests in staging already covers that aspect.
upvoted 0 times
...
Shawna
4 months ago
But wouldn't it be better if QA also runs the tests manually in the staging environment?
upvoted 0 times
...
Jesse
4 months ago
Haha, I bet the developers would love to skip the QA team and just test everything themselves. But that's a hard pass from me, my friend. Gotta keep those checks and balances in place.
upvoted 0 times
Noemi
4 months ago
Haha, I bet the developers would love to skip the QA team and just test everything themselves. But that's a hard pass from me, my friend. Gotta keep those checks and balances in place.
upvoted 0 times
...
Rebeca
4 months ago
C) Run unit tests before build and stage testing
upvoted 0 times
...
Fatima
4 months ago
C) Run unit tests before build and stage testing
upvoted 0 times
...
Henriette
4 months ago
B) Operations must test in another environment before production
upvoted 0 times
...
Felix
4 months ago
B) Operations must test in another environment before production
upvoted 0 times
...
Anglea
4 months ago
A) QA must also run the tests manually in the staging environment
upvoted 0 times
...
Solange
4 months ago
A) QA must also run the tests manually in the staging environment
upvoted 0 times
...
...
Therese
4 months ago
I agree with Lindsey, running unit tests before build and stage testing can catch issues early.
upvoted 0 times
...
Jerry
5 months ago
D) Developers running the unit tests manually instead of the QA team? That sounds like a recipe for disaster. Let's stick with the automated tests and keep the QA team involved.
upvoted 0 times
Lucina
3 months ago
C) Run unit tests before build and stage testing
upvoted 0 times
...
Pamella
3 months ago
B) Operations must test in another environment before production
upvoted 0 times
...
Linette
3 months ago
A) QA must also run the tests manually in the staging environment
upvoted 0 times
...
Nelida
3 months ago
C) Run unit tests before build and stage testing
upvoted 0 times
...
Rebecka
3 months ago
B) Operations must test in another environment before production
upvoted 0 times
...
Peggy
3 months ago
A) QA must also run the tests manually in the staging environment
upvoted 0 times
...
...
Salina
5 months ago
I agree with Rima. Running unit tests before the build and staging environment is a smart move to catch problems early. The less you have to worry about in later stages, the better.
upvoted 0 times
...
Rima
5 months ago
C) Run unit tests before build and stage testing seems like the best option to improve the CI/CD pipeline. Catching issues early on is key to a smooth deployment process.
upvoted 0 times
Blondell
4 months ago
Yes, it's important to have those checks in place to ensure a smooth deployment process.
upvoted 0 times
...
Tom
4 months ago
I agree, running unit tests before build and stage testing can definitely help catch issues early on.
upvoted 0 times
...
...
Lindsey
5 months ago
I think option C is the best choice.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77