01. A company publicly invites outside security researchers to look for vulnerabilities in its website. It pays a reward for each valid finding that is reported responsibly.
What is this arrangement called?
a) A penetration test
b) Fuzz testing
c) A bug bounty program
d) A red team
02. A DAST scan of an online banking application reports few issues. The team then notices that the scanner never reached any of the account pages behind the login screen.
Which change lets the scanner test those pages?
a) Run the scan against the production site instead of staging, so that the real pages are tested
b) Configure the scan with valid test login credentials
c) Add a SAST scan of the login page's source code to the same stage of the pipeline
d) Increase the scanner's threads so that its crawler covers more pages in the time allowed
03. A development team receives the report from a penetration test of its web application.
What should each finding in a useful report contain?
a) The exploit code, packaged so the team can rerun each attack
b) A single pass or fail result for the application
c) Evidence and steps to reproduce it, its risk rating, and remediation guidance
d) A list of the tools used, the hours each one ran, the testers' names, and the dates of each test session
04. A pre-release VAPT finds a critical, easily exploitable authentication bypass in a release candidate that is due to go live tomorrow.
What should the team do?
a) Release to production, then run a full DAST scan there to confirm whether the bypass is real
b) Release on schedule, record the finding as an accepted risk, and fix it in the next planned sprint
c) Fix and retest it before the release goes live
d) Release on schedule, and rely on RASP in production to block attempts to exploit the bypass
05. A retailer wants to learn that its checkout is broken before customers complain, even at night when few people are shopping. It schedules scripts that log in, add an item, and complete a test purchase against production every few minutes.
Which practice is the retailer using?
a) Regression testing, which reruns existing tests after a code change
b) Synthetic monitoring, which runs scripted user journeys against production on a schedule
c) Load testing, which simulates heavy traffic in a test environment
d) Real user monitoring, which measures actual visitors' sessions
06. A team starts threat modeling by drawing how data moves between the browser, the web server, a payment service, and the database.
Why does this diagram help the team find threats?
a) It records which developer owns each component and its data
b) It shows the order in which components are deployed by the pipeline
c) It lists the known vulnerabilities in each component, with their severity scores and their fixes
d) It shows where data crosses trust boundaries, which is where threats are looked for
07. A team's SAST scan of its web application's source code reports no issues. After the application goes live on the staging server, a security tester finds that its pages are sent without the required security headers and that the server lists the contents of its folders to any visitor.
Which test is designed to catch this class of issue, and why did SAST miss it?
a) IAST during unit tests on the build server, since its agent watches code from inside the application
b) DAST, because these issues show up in the running, configured server, which SAST never sees
c) Unit tests, which check each function's output
d) SCA, because the headers and folder listings come from libraries with known flaws
08. An automated DAST scan of a web application reports no issues. A later penetration test finds an SQL injection flaw on a page that the scan had tested.
What is the scan's miss called?
a) A false positive, a reported issue that turns out not to be a real problem
b) A true negative, a correct result that no issue exists
c) An accepted risk, a known flaw left unfixed
d) A false negative, a real flaw the test failed to report
09. While investigating an incident, a team combines logs from a firewall, a web server, and a database. The events appear in the wrong order because each system's clock shows a slightly different time.
Which practice prevents this problem?
a) A more detailed logging level on the database server
b) Clock synchronization across systems using NTP
c) SIEM thresholds for failed logins
d) Log rotation with a fixed retention period on each system
10. While planning a new password-reset feature, a team writes stories such as "an attacker requests resets for thousands of accounts to lock users out" next to the normal user stories.
What are these stories called, and how are they used?
a) User acceptance criteria, which business users review, approve, and sign off before release
b) Incident reports, which record attacks that already occurred in production
c) Abuse cases, which describe how an attacker could misuse the feature and become security requirements and tests
d) Risk transfers, which move the cost of an attack to an insurer