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 78 Discussion

Actual exam question for Cisco's 300-910 exam
Question #: 78
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:

Sharmaine
4 months ago
I'm just glad they didn't include an option to 'run all the tests manually' - that would be the ultimate facepalm moment.
upvoted 0 times
...
Joseph
4 months ago
Haha, I bet the person who wrote option D has never actually worked on a real-world CI/CD setup before. C is the obvious choice to improve the workflow here.
upvoted 0 times
Rozella
3 months ago
Totally, manual unit tests by developers can slow down the process and introduce human error.
upvoted 0 times
...
Sue
4 months ago
Exactly, it's all about catching issues early to ensure a smooth deployment to production.
upvoted 0 times
...
Denae
4 months ago
Yeah, running unit tests before build and stage testing would help catch issues earlier in the process.
upvoted 0 times
...
Weldon
4 months ago
I agree, option C is definitely the best choice to improve the CI/CD pipeline.
upvoted 0 times
...
...
Rosenda
5 months ago
I'm surprised D is even an option. Developers running their own tests? That's just asking for trouble. C is clearly the right answer to tighten up this CI/CD pipeline.
upvoted 0 times
...
Lucina
5 months ago
I agree with Mayra, option C can help in identifying and fixing bugs sooner.
upvoted 0 times
...
Mayra
5 months ago
But running unit tests before build and stage testing can catch issues earlier in the process.
upvoted 0 times
...
Emerson
5 months ago
I agree, C is the way to go. Automating the unit tests upfront saves time and resources down the line. No need for manual QA steps in the staging environment.
upvoted 0 times
Jerry
3 months ago
B) Operations must test in another environment before production
upvoted 0 times
...
Margery
3 months ago
C) Run unit tests before build and stage testing
upvoted 0 times
...
Julieta
3 months ago
A) QA must also run the tests manually in the staging environment
upvoted 0 times
...
Gabriele
3 months ago
B) Operations must test in another environment before production
upvoted 0 times
...
Davida
3 months ago
A) QA must also run the tests manually in the staging environment
upvoted 0 times
...
Krissy
3 months ago
C) Run unit tests before build and stage testing
upvoted 0 times
...
...
Harris
5 months ago
Option C seems like the best choice here. Running unit tests before the build and staging tests ensures the code is validated earlier in the pipeline, catching issues sooner.
upvoted 0 times
Ronny
4 months ago
Definitely, it helps in ensuring the code quality and reducing the chances of errors in the later stages.
upvoted 0 times
...
Josue
4 months ago
I agree, running unit tests before build and staging testing is crucial for catching issues early on.
upvoted 0 times
...
...
Marti
5 months ago
I disagree, I believe option B is more efficient.
upvoted 0 times
...
Mayra
6 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