Question 480
To stop clients spoofing upstream identity or forwarding headers, what would a application security engineer implement or use?
- Reverse-proxy header sanitization
- WAF TLS termination
- HTTP security headers
- WAF false-positive tuning
- WAF managed rule updates
Explanation
Correct Answer
A:A trusted proxy strips and regenerates sensitive headers before passing requests to application code; this mechanism directly supports the requirement to stop clients spoofing upstream identity or forwarding headers.
Incorrect Answers
B:The gateway needs approved key or termination capability and must resecure its upstream connection appropriately; a team would select it to inspect encrypted web requests at a designated application gateway, which does not provide the particular result to stop clients spoofing upstream identity or forwarding headers.
C:Security response headers affect browser enforcement and complement server-side authentication checks; its operational purpose is to instruct browsers to limit framing, content sourcing and transport downgrade, not to achieve the specific requirement to stop clients spoofing upstream identity or forwarding headers.
D:Rule exclusions or parameter scoping can preserve protection while handling known safe input patterns; applying it would serve stop a legitimate JSON API call being blocked by a broad rule without directly satisfying the goal to stop clients spoofing upstream identity or forwarding headers.
E:Rule maintenance reduces known-pattern gaps without providing a guarantee against application logic flaws; it addresses the different need to keep inspection signatures aligned with emerging web exploit patterns, leaving the requested ability to stop clients spoofing upstream identity or forwarding headers unresolved.
Question 481
To instruct browsers to limit framing, content sourcing and transport downgrade, which practice addresses that objective?
- WAF bot challenge
- WAF managed rule updates
- HTTP security headers
- WAF path allowlist
Explanation
Correct Answer
C:Security response headers affect browser enforcement and complement server-side authentication checks; it supplies the specific control needed to instruct browsers to limit framing, content sourcing and transport downgrade.
Incorrect Answers
A:Challenges and reputation signals increase bot friction while not establishing user authorization; it could help someone trying to differentiate automated credential attempts from normal user interactions, but the problem is instead to instruct browsers to limit framing, content sourcing and transport downgrade.
B:Rule maintenance reduces known-pattern gaps without providing a guarantee against application logic flaws; that is useful when the task is to keep inspection signatures aligned with emerging web exploit patterns, not the stated requirement to instruct browsers to limit framing, content sourcing and transport downgrade.
D:Explicit path controls reduce unwanted endpoint exposure at the application gateway; its operational purpose is to permit only documented routes into a restricted management web application, not to achieve the specific requirement to instruct browsers to limit framing, content sourcing and transport downgrade.
Question 482
To inspect encrypted web requests at a designated application gateway, which tool, policy, or technique is appropriate?
- WAF bot challenge
- WAF managed rule updates
- WAF false-positive tuning
- WAF TLS termination
Explanation
Correct Answer
D:The gateway needs approved key or termination capability and must resecure its upstream connection appropriately; that is why it addresses the operational task to inspect encrypted web requests at a designated application gateway.
Incorrect Answers
A:Challenges and reputation signals increase bot friction while not establishing user authorization; although relevant to differentiate automated credential attempts from normal user interactions, it does not by itself achieve the required task to inspect encrypted web requests at a designated application gateway.
B:Rule maintenance reduces known-pattern gaps without providing a guarantee against application logic flaws; it could help someone trying to keep inspection signatures aligned with emerging web exploit patterns, but the problem is instead to inspect encrypted web requests at a designated application gateway.
C:Rule exclusions or parameter scoping can preserve protection while handling known safe input patterns; that is useful when the task is to stop a legitimate JSON API call being blocked by a broad rule, not the stated requirement to inspect encrypted web requests at a designated application gateway.
Question 483
To require valid tokens before exposing business API operations, what safeguard would be most applicable?
- WAF managed rule updates
- API gateway authentication
- Reverse-proxy header sanitization
- WAF TLS termination
Explanation
Correct Answer
B:Gateway verification can reject unauthenticated calls but fine-grained business authorization remains essential; its relevant protective or investigative effect is to require valid tokens before exposing business API operations.
Incorrect Answers
A:Rule maintenance reduces known-pattern gaps without providing a guarantee against application logic flaws; the outcome it supports is to keep inspection signatures aligned with emerging web exploit patterns, whereas this scenario asks defenders to require valid tokens before exposing business API operations.
C:A trusted proxy strips and regenerates sensitive headers before passing requests to application code; it could help someone trying to stop clients spoofing upstream identity or forwarding headers, but the problem is instead to require valid tokens before exposing business API operations.
D:The gateway needs approved key or termination capability and must resecure its upstream connection appropriately; that is useful when the task is to inspect encrypted web requests at a designated application gateway, not the stated requirement to require valid tokens before exposing business API operations.
Question 484
To inspect encrypted web requests at a designated application gateway, to require valid tokens before exposing business API operations, and to keep inspection signatures aligned with emerging web exploit patterns, which THREE measures should the team select? Choose THREE.
- WAF managed rule updates
- WAF false-positive tuning
- WAF TLS termination
- HTTP security headers
- API gateway authentication
- Reverse-proxy header sanitization
Explanation
Correct Answers
A:Rule maintenance reduces known-pattern gaps without providing a guarantee against application logic flaws; its contribution to the combined design is specifically to keep inspection signatures aligned with emerging web exploit patterns.
C:The gateway needs approved key or termination capability and must resecure its upstream connection appropriately; its contribution to the combined design is specifically to inspect encrypted web requests at a designated application gateway.
E:Gateway verification can reject unauthenticated calls but fine-grained business authorization remains essential; its contribution to the combined design is specifically to require valid tokens before exposing business API operations.
Incorrect Answers
B:Rule exclusions or parameter scoping can preserve protection while handling known safe input patterns; the outcome it supports is to stop a legitimate JSON API call being blocked by a broad rule, whereas this scenario asks defenders to inspect encrypted web requests at a designated application gateway, to require valid tokens before exposing business API operations, and to keep inspection signatures aligned with emerging web exploit patterns.
D:Security response headers affect browser enforcement and complement server-side authentication checks; it could help someone trying to instruct browsers to limit framing, content sourcing and transport downgrade, but the problem is instead to inspect encrypted web requests at a designated application gateway, to require valid tokens before exposing business API operations, and to keep inspection signatures aligned with emerging web exploit patterns.
F:A trusted proxy strips and regenerates sensitive headers before passing requests to application code; a team would select it to stop clients spoofing upstream identity or forwarding headers, which does not provide the particular result to inspect encrypted web requests at a designated application gateway, to require valid tokens before exposing business API operations, and to keep inspection signatures aligned with emerging web exploit patterns.
Question 485
To find insecure source-code flows before an application is deployed, what is the relevant defensive action?
- Secrets scanning
- Dependency SBOM update
- DAST assessment
- Application log access controls
- SAST integration
Explanation
Correct Answer
E:Static analysis examines code structure and dependencies without needing live HTTP traffic; this choice fits the scenario because the team must find insecure source-code flows before an application is deployed.
Incorrect Answers
A:Precommit or pipeline scanning identifies high-risk credential strings before builds distribute them; the technique works for situations involving stop private API keys being committed into a source repository, rather than this need to find insecure source-code flows before an application is deployed.
B:Current component manifests enable affected-version lookup and faster exposure decisions; its mechanism supports identify new libraries introduced by a supplier's application revision, while the requested control must be able to find insecure source-code flows before an application is deployed.
C:Dynamic scanning evaluates reachable runtime behavior and depends on configured test coverage; the outcome it supports is to probe a running test web application for observable security weaknesses, whereas this scenario asks defenders to find insecure source-code flows before an application is deployed.
D:Least-privilege access to logs reduces secondary data exposure from diagnostic systems; although relevant to prevent developers from routinely reading production authentication secrets, it does not by itself achieve the required task to find insecure source-code flows before an application is deployed.
Question 486
To probe a running test web application for observable security weaknesses, which option most directly provides the capability?
- DAST assessment
- Secrets scanning
- Dependency SBOM update
- Application log access controls
Explanation
Correct Answer
A:Dynamic scanning evaluates reachable runtime behavior and depends on configured test coverage; this mechanism directly supports the requirement to probe a running test web application for observable security weaknesses.
Incorrect Answers
B:Precommit or pipeline scanning identifies high-risk credential strings before builds distribute them; the technique works for situations involving stop private API keys being committed into a source repository, rather than this need to probe a running test web application for observable security weaknesses.
C:Current component manifests enable affected-version lookup and faster exposure decisions; its mechanism supports identify new libraries introduced by a supplier's application revision, while the requested control must be able to probe a running test web application for observable security weaknesses.
D:Least-privilege access to logs reduces secondary data exposure from diagnostic systems; the outcome it supports is to prevent developers from routinely reading production authentication secrets, whereas this scenario asks defenders to probe a running test web application for observable security weaknesses.
Question 487
To stop private API keys being committed into a source repository, which control achieves the target outcome?
- DAST assessment
- Security regression tests
- Secrets scanning
- Application log access controls
Explanation
Correct Answer
C:Precommit or pipeline scanning identifies high-risk credential strings before builds distribute them; it supplies the specific control needed to stop private API keys being committed into a source repository.
Incorrect Answers
A:Dynamic scanning evaluates reachable runtime behavior and depends on configured test coverage; applying it would serve probe a running test web application for observable security weaknesses without directly satisfying the goal to stop private API keys being committed into a source repository.
B:Automated negative tests verify access restrictions after each relevant code change; it addresses the different need to ensure a previously repaired authorization bypass does not reappear, leaving the requested ability to stop private API keys being committed into a source repository unresolved.
D:Least-privilege access to logs reduces secondary data exposure from diagnostic systems; its mechanism supports prevent developers from routinely reading production authentication secrets, while the requested control must be able to stop private API keys being committed into a source repository.
Question 488
To ensure a previously repaired authorization bypass does not reappear, which solution should be adopted?
- Secure configuration externalization
- Application health monitoring
- Dependency SBOM update
- Security regression tests
Explanation
Correct Answer
D:Automated negative tests verify access restrictions after each relevant code change; that is why it addresses the operational task to ensure a previously repaired authorization bypass does not reappear.
Incorrect Answers
A:Secret managers and deployment injection separate environment credentials from application artifacts; its operational purpose is to avoid embedding database passwords in a compiled executable, not to achieve the specific requirement to ensure a previously repaired authorization bypass does not reappear.
B:Runtime telemetry links unusual failures to request context but needs correlation to establish malicious intent; applying it would serve detect a crash loop caused by an attempted malicious request sequence without directly satisfying the goal to ensure a previously repaired authorization bypass does not reappear.
C:Current component manifests enable affected-version lookup and faster exposure decisions; it addresses the different need to identify new libraries introduced by a supplier's application revision, leaving the requested ability to ensure a previously repaired authorization bypass does not reappear unresolved.
Question 489
To identify new libraries introduced by a supplier's application revision, which of the available controls is suitable?
- DAST assessment
- Application log access controls
- Dependency SBOM update
- SAST integration
Explanation
Correct Answer
C:Current component manifests enable affected-version lookup and faster exposure decisions; its relevant protective or investigative effect is to identify new libraries introduced by a supplier's application revision.
Incorrect Answers
A:Dynamic scanning evaluates reachable runtime behavior and depends on configured test coverage; a team would select it to probe a running test web application for observable security weaknesses, which does not provide the particular result to identify new libraries introduced by a supplier's application revision.
B:Least-privilege access to logs reduces secondary data exposure from diagnostic systems; its operational purpose is to prevent developers from routinely reading production authentication secrets, not to achieve the specific requirement to identify new libraries introduced by a supplier's application revision.
D:Static analysis examines code structure and dependencies without needing live HTTP traffic; it addresses the different need to find insecure source-code flows before an application is deployed, leaving the requested ability to identify new libraries introduced by a supplier's application revision unresolved.
Question 490
To prevent developers from routinely reading production authentication secrets, which option is the direct technical match?
- Secure configuration externalization
- Application log access controls
- Dependency SBOM update
- SAST integration
- Security regression tests
Explanation
Correct Answer
B:Least-privilege access to logs reduces secondary data exposure from diagnostic systems; the requested outcome is precisely to prevent developers from routinely reading production authentication secrets.
Incorrect Answers
A:Secret managers and deployment injection separate environment credentials from application artifacts; that is useful when the task is to avoid embedding database passwords in a compiled executable, not the stated requirement to prevent developers from routinely reading production authentication secrets.
C:Current component manifests enable affected-version lookup and faster exposure decisions; its operational purpose is to identify new libraries introduced by a supplier's application revision, not to achieve the specific requirement to prevent developers from routinely reading production authentication secrets.
D:Static analysis examines code structure and dependencies without needing live HTTP traffic; applying it would serve find insecure source-code flows before an application is deployed without directly satisfying the goal to prevent developers from routinely reading production authentication secrets.
E:Automated negative tests verify access restrictions after each relevant code change; it addresses the different need to ensure a previously repaired authorization bypass does not reappear, leaving the requested ability to prevent developers from routinely reading production authentication secrets unresolved.