ThreatSpec is a command-line tool that follows standard Unix-style conventions, where commands are lowercase. To generate a threat model report after annotating source code, the correct command is threatspec report. Commands using incorrect casing or capitalization will fail because the CLI is case-sensitive. Options A, B, and C incorrectly capitalize either the command or the subcommand. Generating threat model reports during the Plan stage allows DevSecOps teams to continuously identify, document, and visualize security threats as the code evolves. This practice embeds threat modeling directly into the development lifecycle, enabling early risk identification and more secure system design decisions.

When configuring Burp Suite scans in Jenkins using an Execute shell build step, environment variables are often set or echoed so that subsequent scan steps can consume them. The echo command is used to output or define values in the shell context. In this case, echo BURP_SCAN_URL = http://target-website.com correctly defines the target URL for Burp Suite scanning. Commands like grep and cat are used for searching or displaying file contents and are not appropriate for setting scan parameters. The sudo command is unnecessary and incorrect in this context. Using the correct shell command ensures that Burp Suite receives the proper target information during the Build and Test stage, enabling accurate dynamic application security testing.

The description matches AWS BugBust, which AWS positions as a gamified, team-based bug fixing challenge rather than a classic external "bug bounty" for finding vulnerabilities in AWS itself.
The key hints are "fun-based solution for bashing bugs," "encouraging team building," and
"friendly competition," along with scoring points and awarding prizes. BugBust focuses on improving code quality by motivating developers to find and fix issues (often via static analysis findings) in languages like Java and Python. Participants earn points for remediations and compete on leaderboards, which aligns directly with Sarah "scored the highest points" and received a cash reward. The other names (BugFixer, BugFinder, BugHunt) are plausible- sounding but do not match the commonly referenced AWS gamified program described. In a DevSecOps context, this type of program supports culture by incentivizing secure coding habits, encouraging shared ownership of quality, and making remediation visible and rewarding across the engineering team.

IaC security scanning tools (such as Checkov, tfsec, or Terrascan) statically analyze Infrastructure as Code definitions like Terraform, CloudFormation, or ARM templates to identify misconfigurations -- such as publicly accessible storage buckets or overly permissive security group rules -- before any actual cloud resources are provisioned, matching Aiko's exact goal of pre-provisioning detection. DAST tests running applications, not declarative infrastructure definitions, and requires a live target. Penetration testing of live cloud resources occurs after resources already exist and are deployed, which contradicts Aiko's "before provisioned" requirement. Log aggregation collects and centralizes log data from running systems for analysis, unrelated to pre-deployment configuration scanning. Since Aiko wants to catch misconfigurations in Terraform files prior to provisioning, IaC security scanning is correct.