MENU
Scanning application code for security vulnerabilities is an important step in which aspect of the Continuous Delivery Pipeline?
38 comments · newest first
CA
Carry
10 months ago
Scanning code? Seems like it should be in all stages, right?
VI
Vi
10 months ago
Wait, are we sure it's not Continuous Exploration?
JU
Junita
10 months ago
Totally agree, CI is where vulnerabilities get caught early.
PA
Paulina
11 months ago
It's definitely part of Continuous Integration!
KI
Kimbery
11 months ago
I thought it was more about Continuous Deployment.
ER
Erasmo
11 months ago
I'm leaning towards Continuous Integration too. It makes sense to catch vulnerabilities early in the development process before moving on to deployment.
YU
Yun
11 months ago
I feel like it could also tie into Continuous Exploration since that phase involves understanding requirements, but I really can't recall clearly.
BE
Belen
11 months ago
I remember a practice question that mentioned security checks being crucial before deployment. So, maybe it relates to Continuous Deployment?
AL
Alisha
12 months ago
I think scanning for vulnerabilities is part of Continuous Integration, but I'm not completely sure. It seems like it fits there since it's about integrating code regularly.
RO
Ronny
12 months ago
I feel pretty confident about this one. Scanning for security vulnerabilities is a key part of the Continuous Integration stage, where the code is integrated and tested before being deployed. That's the stage that's most relevant to this question.
BU
Bulah
12 months ago
I'm a little confused by the wording of this question. Is it asking about the specific stage of the pipeline where security scanning happens, or is it just looking for the general aspect of the pipeline that this activity is associated with? I'll have to re-read it a few times to make sure I understand what they're asking.
QU
Quentin
1 year ago
Okay, I've got this. Scanning for security vulnerabilities is part of the Continuous Integration stage, where the code is built, tested, and checked for issues before being deployed. That's the stage that's most relevant here.
NA
Nada
1 year ago
Hmm, I'm a bit unsure about this one. I know the Continuous Delivery Pipeline has different stages, but I'm not entirely sure which one would be the best fit for this scenario. I'll have to think it through carefully.
RE
Renato
1 year ago
This seems like a straightforward question about the Continuous Delivery Pipeline. I'll think through the different stages and try to identify which one is most relevant for scanning application code for security vulnerabilities.
AL
Alex
1 year ago
Continuous Deployment, eh? Nah, I'm gonna have to go with D. Gotta make sure my code is locked down tight before it goes live, you know?
LO
Lonny
1 year ago
D) Yeah, security is key in the Continuous Integration phase.
AN
Anna
1 year ago
D) Gotta make sure my code is locked down tight before it goes live.
NA
Nathan
1 year ago
D) Continuous Integration
GO
Goldie
1 year ago
C) Release on Demand
OL
Olene
1 year ago
B) Continuous Deployment
LA
Lauran
1 year ago
A) Continuous Exploration
AH
Ahmed
1 year ago
Ooh, security vulnerabilities? Better catch those buggers before they cause any trouble! I'm going with D, Continuous Integration. Seems like the best way to stay on top of things.
TA
Tamie
1 year ago
But wouldn't it also be important in Continuous Integration to catch issues early on?
JE
Jennie
1 year ago
Haha, this one's a no-brainer! Scanning for security issues is all about that Continuous Integration, my dude. D all the way.
AN
Annelle
1 year ago
Continuous Integration is key to catching any security issues early in the development process.
LA
Lashaunda
1 year ago
I agree, it's an essential step to ensure the code is secure before moving forward.
CR
Cristal
1 year ago
Definitely, scanning for security vulnerabilities is crucial in Continuous Integration.
LE
Leeann
1 year ago
I agree with Berry, it helps ensure the code is secure before deployment.
CE
Cecilia
1 year ago
Scanning for vulnerabilities? Gotta keep those hackers out of my code, am I right? I'll go with D, Continuous Integration. Seems like the logical choice to me.
ST
Stefan
1 year ago
User 4: Agreed, it's better to be safe than sorry when it comes to code security.
HE
Heidy
1 year ago
User 3: Continuous Integration is key for security, can't risk any breaches.
CA
Cary
1 year ago
User 2: Definitely, it's all about catching those vulnerabilities early on.
MI
Misty
1 year ago
User 1: Yeah, keeping hackers out is crucial. I agree, Continuous Integration is the way to go.
LA
Lashanda
1 year ago
Continuous Integration is key for ensuring code quality and security.
KR
Kristal
1 year ago
I think Continuous Integration is the best option for scanning code for security vulnerabilities.
DO
Donette
1 year ago
Continuous Integration is definitely important for catching vulnerabilities early on.
TR
Tricia
1 year ago
I agree, keeping hackers out is crucial. I also think Continuous Integration is the right choice.
BE
Berry
2 years ago
I think scanning for security vulnerabilities is important in Continuous Deployment.