MENU
You are creating an application lifecycle management process based on the Microsoft Security Development Lifecycle (SDL).
You need to recommend a security standard for onboarding applications to Azure. The standard will include recommendations for application design, development, and deployment
What should you include during the application design phase?
Suggested Answer: D
Get Premium SC-100 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
37 comments · newest first
SH
Shad
11 months ago
I disagree, software decomposition should be prioritized.
ED
Edison
11 months ago
Surprised that threat modeling isn't more widely used!
KE
Kerry
11 months ago
DAST is great, but not for design phase.
LA
Laticia
12 months ago
I think SAST is more important for early stages.
WA
Wayne
12 months ago
Definitely threat modeling is key!
AM
Amber
1 year ago
I feel like software decomposition could be important too, but I don't remember it being specifically tied to the design phase in our studies.
AN
Annett
1 year ago
I think threat modeling is definitely the right answer. We practiced a similar question where identifying potential threats early was emphasized.
PH
Phillip
1 year ago
I'm a bit unsure if SAST or DAST would be more relevant here. I think SAST is more for code analysis, but I can't recall if it fits in the design phase.
TI
Tish
1 year ago
I remember we discussed threat modeling as a key part of the design phase, especially using the Microsoft Threat Modeling Tool. It seems like a solid choice.
HO
Hoa
1 year ago
This is a tricky one. I'm leaning towards the threat modeling option, but I'm not 100% sure. I might need to review the SDL recommendations again to make sure I'm choosing the right security standard for the design phase.
EL
Ellen
1 year ago
Okay, I've got a strategy for this. Since the question is asking about the design phase, I think the best approach would be to recommend something that helps identify and address security risks upfront, before the application is built. The Microsoft Threat Modeling Tool seems like a good fit for that.
GA
Gary
1 year ago
This looks like a pretty straightforward question about security standards for Azure application onboarding. I think the key is to focus on the design phase and the recommendations that would be most relevant there.
LE
Levi
1 year ago
Hmm, I'm a bit unsure about this one. There are a few different security testing and modeling options mentioned, and I'm not sure which one would be the best fit for the application design phase specifically. I'll need to think this through carefully.
MA
Maddie
1 year ago
Hmm, I'm a bit unsure about this one. There are a few options that seem relevant, but I want to make sure I choose the two most critical ones.
AM
Amalia
1 year ago
I thought “all embedded/referred except” was a common configuration for exceptions, but I can't remember how it fits in with the others.
SA
Sage
1 year ago
Threat modeling? More like 'threat modeling, my friend!' *laughs and high-fives the room*
GE
Gerry
1 year ago
C) threat modeling by using the Microsoft Threat Modeling Tool
DO
Dorthy
1 year ago
B) dynamic application security testing (DAST) by using Veracode
AH
Ahmed
1 year ago
A) static application security testing (SAST) by using SonarQube
JO
Johnna
1 year ago
Hold up, software decomposition in Visual Studio Enterprise? That's more for architecture, not security. Threat modeling is the way to go here, my dudes.
LO
Loren
1 year ago
C) threat modeling by using the Microsoft Threat Modeling Tool
GE
German
1 year ago
B) dynamic application security testing (DAST) by using Veracode
QU
Queenie
1 year ago
A) static application security testing (SAST) by using SonarQube
AR
Aretha
2 years ago
SonarQube for SAST? Nah, that's for the coding phase. Threat modeling is where it's at for the design phase. *winks*
AL
Altha
1 year ago
C) threat modeling by using the Microsoft Threat Modeling Tool
GE
German
1 year ago
SonarQube is great for code analysis, but threat modeling is crucial for designing secure applications.
NE
Nelida
1 year ago
C) threat modeling by using the Microsoft Threat Modeling Tool
ED
Edna
1 year ago
A) static application security testing (SAST) by using SonarQube
DE
Detra
2 years ago
I agree, threat modeling is crucial for secure application design. It's a comprehensive way to assess potential threats and mitigate them proactively.
RO
Rory
2 years ago
I think software decomposition with Microsoft Visual Studio Enterprise should also be included for a comprehensive security standard.
FL
Flo
2 years ago
Threat modeling using the Microsoft Threat Modeling Tool seems like the right choice here. It helps identify potential security vulnerabilities early in the design phase.
DE
Desiree
1 year ago
User 4: I think threat modeling is more comprehensive in identifying security risks.
FE
Felice
1 year ago
User 3: What about static application security testing (SAST) by using SonarQube?
LE
Leonora
1 year ago
User 2: I agree, it helps identify potential security vulnerabilities early on.
HE
Herschel
1 year ago
User 1: I think we should include threat modeling using the Microsoft Threat Modeling Tool during the application design phase.
ER
Erick
2 years ago
I agree with Samira, threat modeling with the Microsoft Threat Modeling Tool is crucial for security.
SA
Samira
2 years ago
I think we should include threat modeling during the application design phase.