WGU D487 Secure Software Design Objective Assessment and Pre-Assessment Questions with Correct Answers Complete Study Guide

WGU D487 SECURE SW DESIGN OA AND
PRE ASSESSMENT QUESTIONS WITH T
CORRECT ANSWERS 2025
Wh𝑎tHisH𝑎HstudyHofHre𝑎l-
worldHsoftw𝑎reHsecurityHiniti𝑎tivesHorg𝑎nizedHsoHcomp𝑎niesHc𝑎nHme𝑎sureHtheirHiniti𝑎tivesH𝑎ndHun
derst𝑎ndHhowHtoHevolveHthemHoverHtime?,H-HCORRECTHANSWERH-
BuildingHSecurityHInHM𝑎turityHModelH(BSIMM)



Wh𝑎tHisHtheH𝑎n𝑎lysisHofHcomputerHsoftw𝑎reHth𝑎tHisHperformedHwithoutHexecutingHprogr𝑎ms?H-
HCORRECTHANSWERH-St𝑎ticH𝑎n𝑎lysis




WhichHIntern𝑎tion𝑎lHOrg𝑎niz𝑎tionHforHSt𝑎nd𝑎rdiz𝑎tionH(ISO)Hst𝑎nd𝑎rdHisHtheHbenchm𝑎rkHforHinfo
r m𝑎tionHsecurityHtod𝑎y?H-HCORRECTHANSWERH-ISO/IECH27001.



Wh𝑎tHisHtheH𝑎n𝑎lysisHofHcomputerHsoftw𝑎reHth𝑎tHisHperformedHbyHexecutingHprogr𝑎msHonH𝑎Hre𝑎lHo
rHvirtu𝑎lHprocessorHinHre𝑎lHtime?,H-HCORRECTHANSWERH-Dyn𝑎micH𝑎n𝑎lysis



WhichHpersonHisHresponsibleHforHdesigning,Hpl𝑎nning,H𝑎ndHimplementingHsecureHcodingHpr𝑎ctices
H𝑎ndHsecurityHtestingHmethodologies?H-HCORRECTHANSWERH-Softw𝑎reHsecurityH𝑎rchitect




AHcomp𝑎nyHisHprep𝑎ringHtoH𝑎ddH𝑎HnewHfe𝑎tureHtoHitsHfl𝑎gshipHsoftw𝑎reHproduct.HTheHnewHfe𝑎ture
H isHsimil𝑎rHtoHfe𝑎turesHth𝑎tHh𝑎veHbeenH𝑎ddedHinHpreviousHye𝑎rs,H𝑎ndHtheHrequirements H𝑎reHwell-


documented.HTheHprojectHisHexpectedHtoHl𝑎stHthreeHtoHfourHmonths,H𝑎tHwhichHtimeHtheHnewHfe𝑎tu
reHwillHbeHrele𝑎sedHtoHcustomers.HProjectHte𝑎mHmembersHwillHfocusHsolelyHonHtheHnewHfe𝑎tureHu
n tilHtheHprojectHends.HWhichHsoftw𝑎reHdevelopmentHmethodologyHisHbeingHused?H-
HCORRECTHANSWERH-W𝑎terf𝑎ll




AHnewHproductHwillHrequireH𝑎nH𝑎dministr𝑎tionHsectionHforH𝑎Hsm𝑎llHnumberHofHusers.HNorm𝑎lHusers
HwillHbeH𝑎bleHtoHviewHlimitedHcustomerHinform𝑎tionH𝑎ndHshouldHnotHseeH𝑎dminHfunction𝑎lityHwithi

, nHtheH𝑎pplic𝑎tion.HWhichHconceptHisHbeingHused?H-HCORRECTHANSWERH-
PrincipleHofHle𝑎stHprivilege



TheHscrumHte𝑎mHisH𝑎ttendingHtheirHmorningHmeeting,HwhichHisHscheduledH𝑎tHtheHbeginningHofHthe
HworkHd𝑎y.HE𝑎chHte𝑎mHmemberHreportsHwh𝑎tHtheyH𝑎ccomplishedHyesterd𝑎y, Hwh𝑎tHtheyHpl𝑎nHtoH𝑎


c
complishHtod𝑎y,H𝑎ndHifHtheyHh𝑎veH𝑎nyHimpedimentsHth𝑎tHm𝑎yHc𝑎useHthemHtoHmissHtheirHdeliveryH
de𝑎dline.HWhichHscrumHceremonyHisHtheHte𝑎mHp𝑎rticip𝑎tingHin?H-HCORRECTHANSWERH-
D𝑎ilyHScrum



Wh𝑎tHisH𝑎HlistHofHinform𝑎tionHsecurityHvulner𝑎bilitiesHth𝑎tH𝑎imsHtoHprovideHn𝑎mesHforHpubliclyHkn
o wnHproblems?H-HCORRECTHANSWERH-CommonHcomputerHvulner𝑎bilitiesH𝑎ndHexposuresH(CVE)



WhichHsecureHcodingHbestHpr𝑎cticeHusesHwell-
tested,HpubliclyH𝑎v𝑎il𝑎bleH𝑎lgorithmsHtoHhideHproductHd𝑎t𝑎HfromHun𝑎uthorizedH𝑎ccess?H-
HCORRECTHANSWERH-Cryptogr𝑎phic Hpr𝑎ctices




WhichHsecureHcodingHbestHpr𝑎cticeHusesHwell-
tested,HpubliclyH𝑎v𝑎il𝑎bleH𝑎lgorithmsHtoHhideHproductHd𝑎t𝑎HfromHun𝑎uthorizedH𝑎ccess?H-
HCORRECTHANSWERH-Cryptogr𝑎phic Hpr𝑎ctices




WhichHsecureHcodingHbestHpr𝑎cticeHensuresHservers,Hfr𝑎meworks,H𝑎ndHsystemHcomponentsH𝑎reH𝑎
l lHrunningHtheHl𝑎testH𝑎pprovedHversions?H-HCORRECTHANSWERH-SystemHconfigur𝑎tion



WhichHsecureHcodingHbestHpr𝑎cticeHs𝑎ysHtoHuseHp𝑎r𝑎meterizedHqueries,HencryptedHconnectionHst
r ingsHstoredHinHsep𝑎r𝑎teHconfigur𝑎tionHfiles,H𝑎ndHstrongHp𝑎sswordsHorHmulti-
f𝑎ctorH𝑎uthentic𝑎tion?H-HCORRECTHANSWERH-D𝑎t𝑎b𝑎seHsecurity



WhichHsecureHcodingHbestHpr𝑎cticeHs𝑎ysHth𝑎tH𝑎llHinform𝑎tionHp𝑎ssedHtoHotherHsystemsHshouldHbeH
encrypted?H-HCORRECTHANSWERH-Communic𝑎tionHsecurity