Question 310
Security issues are repeatedly found only after releases, and the team wants automated checks on each proposed code change. Which software-delivery security measure best matches this need?
- Dynamic application security testing
- Software supply-chain signing
- Security testing in CI pipeline
- Secret scanning in source control
- Static application security testing
Explanation
Correct Answer
C:CI integration runs suitable security tests during development and blocks or flags changes based on defined policy. Review is still needed for complex findings.
Incorrect Answers
A:DAST probes live application behavior through its interface and can reveal exploitable runtime conditions; it handles runtime black-box web probing, while the decisive evidence in the question is repeatable pre-merge security checks.
B:Artifact signing binds an artifact digest to a trusted signer or provenance, supporting integrity checks at deployment; this characterizes authentication of build artifacts before release, whereas the reported condition is repeatable pre-merge security checks.
D:Secret scanning detects credential-like values in commits and repositories; it handles detection of committed authentication secrets, while the decisive evidence in the question is repeatable pre-merge security checks.
E:SAST examines code or intermediate representations for vulnerability patterns for situations characterized by source-oriented flaw detection before runtime; the case points instead to repeatable pre-merge security checks.
Question 311
Two internal APIs need assurance of each other's identity, not merely encryption from server to client. Which application account or secret-handling control best resolves the issue?
- Secrets vault integration
- Server-side authorization checks
- OAuth scope minimization
- Service-to-service mutual TLS
Explanation
Correct Answer
D:mTLS authenticates both peers with certificates and protects transport under a configured trust model. Certificate lifecycle matters.
Incorrect Answers
A:A secret manager centralizes sensitive values and controls retrieval through identity and audit; it handles managed storage and retrieval of service secrets, while the decisive evidence in the question is authenticated identities on both API peers.
B:Object-level authorization verifies each requester's rights to the specific resource; that is relevant to resource ownership checks on every API request but does not directly account for authenticated identities on both API peers.
C:Narrow OAuth scopes restrict what a token can request in a setting defined by reducing permitted delegated API operations; the observed issue is authenticated identities on both API peers.
Question 312
A third-party app receives a broad API token although its business task only needs read access to one dataset. Which application account or secret-handling control best resolves the issue?
- Server-side authorization checks
- Service-to-service mutual TLS
- OAuth scope minimization
- Secrets vault integration
Explanation
Correct Answer
C:Narrow OAuth scopes restrict what a token can request. Backend authorization must still enforce resource-level access.
Incorrect Answers
A:Object-level authorization verifies each requester's rights to the specific resource; that is relevant to resource ownership checks on every API request but does not directly account for reducing permitted delegated API operations.
B:mTLS authenticates both peers with certificates and protects transport under a configured trust model; the operational difference is authenticated identities on both API peers versus the scenario's reducing permitted delegated API operations.
D:A secret manager centralizes sensitive values and controls retrieval through identity and audit; this characterizes managed storage and retrieval of service secrets, whereas the reported condition is reducing permitted delegated API operations.
Question 313
Deployment scripts contain database passwords in plaintext environment files accessible to many engineers. Which application account or secret-handling control best resolves the issue?
- Secrets vault integration
- OAuth scope minimization
- Service-to-service mutual TLS
- Short-lived access tokens
Explanation
Correct Answer
A:A secret manager centralizes sensitive values and controls retrieval through identity and audit. Rotation and runtime handling remain important.
Incorrect Answers
B:Narrow OAuth scopes restrict what a token can request; its distinguishing scope is reducing permitted delegated API operations, not the reported managed storage and retrieval of service secrets.
C:mTLS authenticates both peers with certificates and protects transport under a configured trust model; that is relevant to authenticated identities on both API peers but does not directly account for managed storage and retrieval of service secrets.
D:Short token lifetimes limit the time a captured bearer token can be replayed when the underlying evidence concerns reducing replay lifetime of API credentials rather than the stated managed storage and retrieval of service secrets.
Question 314
Stolen API tokens remain valid for months, allowing extended reuse after an initial compromise. Which application account or secret-handling control best resolves the issue?
- OAuth scope minimization
- Short-lived access tokens
- Server-side authorization checks
- Service-to-service mutual TLS
Explanation
Correct Answer
B:Short token lifetimes limit the time a captured bearer token can be replayed. Refresh-token controls and revocation design are also needed.
Incorrect Answers
A:Narrow OAuth scopes restrict what a token can request; its distinguishing scope is reducing permitted delegated API operations, not the reported reducing replay lifetime of API credentials.
C:Object-level authorization verifies each requester's rights to the specific resource; its distinguishing scope is resource ownership checks on every API request, not the reported reducing replay lifetime of API credentials.
D:mTLS authenticates both peers with certificates and protects transport under a configured trust model; it handles authenticated identities on both API peers, while the decisive evidence in the question is reducing replay lifetime of API credentials.
Question 315
A customer changes an object identifier in an API request and retrieves another tenant's document despite being signed in. Which application account or secret-handling control best resolves the issue?
- Short-lived access tokens
- Service-to-service mutual TLS
- Secrets vault integration
- Server-side authorization checks
- OAuth scope minimization
Explanation
Correct Answer
D:Object-level authorization verifies each requester's rights to the specific resource. Authentication alone does not enforce tenant boundaries.
Incorrect Answers
A:Short token lifetimes limit the time a captured bearer token can be replayed; this characterizes reducing replay lifetime of API credentials, whereas the reported condition is resource ownership checks on every API request.
B:mTLS authenticates both peers with certificates and protects transport under a configured trust model when analysts encounter authenticated identities on both API peers; this question instead describes resource ownership checks on every API request.
C:A secret manager centralizes sensitive values and controls retrieval through identity and audit; the operational difference is managed storage and retrieval of service secrets versus the scenario's resource ownership checks on every API request.
E:Narrow OAuth scopes restrict what a token can request for the specific concern of reducing permitted delegated API operations, not the requirement involving resource ownership checks on every API request.
Question 316
A database snapshot stored on an unattended backup drive must remain confidential even if the drive is physically stolen. Which data protection approach meets the information's lifecycle need?
- Encryption in transit
- Database column masking
- Data loss prevention
- Encryption at rest
Explanation
Correct Answer
D:At-rest encryption protects stored ciphertext against unauthorized offline access when keys remain secure. It does not prevent misuse by authorized running services.
Incorrect Answers
A:Transport encryption such as TLS protects data while crossing network links in a setting defined by confidentiality and integrity across network path; the observed issue is confidentiality of stored backup contents.
B:Masking obscures specified fields in a presented view according to access context; this characterizes limited exposure of sensitive field values, whereas the reported condition is confidentiality of stored backup contents.
C:DLP policies recognize sensitive information and govern transfers across channels such as mail, endpoints and storage; its distinguishing scope is controls on outbound sensitive documents, not the reported confidentiality of stored backup contents.
Question 317
A financial report moves between application servers over a shared network and must resist interception and alteration in transit. Which data protection approach meets the information's lifecycle need?
- Data loss prevention
- Tokenization
- Encryption in transit
- Encryption at rest
Explanation
Correct Answer
C:Transport encryption such as TLS protects data while crossing network links. Endpoints must verify peer identity and handle keys securely.
Incorrect Answers
A:DLP policies recognize sensitive information and govern transfers across channels such as mail, endpoints and storage in a setting defined by controls on outbound sensitive documents; the observed issue is confidentiality and integrity across network path.
B:Tokenization replaces sensitive values with references mapped in a protected system; this characterizes surrogate references for payment data, whereas the reported condition is confidentiality and integrity across network path.
D:At-rest encryption protects stored ciphertext against unauthorized offline access when keys remain secure; its distinguishing scope is confidentiality of stored backup contents, not the reported confidentiality and integrity across network path.
Question 318
Support agents need to view a customer record but should see only the last four digits of a sensitive identifier. Which data protection approach meets the information's lifecycle need?
- Data loss prevention
- Database column masking
- Tokenization
- Encryption in transit
Explanation
Correct Answer
B:Masking obscures specified fields in a presented view according to access context. It is not equivalent to strong encryption of the underlying column.
Incorrect Answers
A:DLP policies recognize sensitive information and govern transfers across channels such as mail, endpoints and storage; its distinguishing scope is controls on outbound sensitive documents, not the reported limited exposure of sensitive field values.
C:Tokenization replaces sensitive values with references mapped in a protected system; the operational difference is surrogate references for payment data versus the scenario's limited exposure of sensitive field values.
D:Transport encryption such as TLS protects data while crossing network links; the operational difference is confidentiality and integrity across network path versus the scenario's limited exposure of sensitive field values.
Question 319
A billing system wants to substitute card account numbers with non-sensitive references while the original values remain in a controlled vault. Which data protection approach meets the information's lifecycle need?
- Tokenization
- Encryption at rest
- Encryption in transit
- Database column masking
Explanation
Correct Answer
A:Tokenization replaces sensitive values with references mapped in a protected system. Compromise of the token alone should not reveal original data.
Incorrect Answers
B:At-rest encryption protects stored ciphertext against unauthorized offline access when keys remain secure; its distinguishing scope is confidentiality of stored backup contents, not the reported surrogate references for payment data.
C:Transport encryption such as TLS protects data while crossing network links; the operational difference is confidentiality and integrity across network path versus the scenario's surrogate references for payment data.
D:Masking obscures specified fields in a presented view according to access context when analysts encounter limited exposure of sensitive field values; this question instead describes surrogate references for payment data.
Question 320
Employees attach confidential spreadsheets to personal email and the organization needs content-aware detection and blocking. Which data protection approach meets the information's lifecycle need?
- Encryption in transit
- Tokenization
- Database column masking
- Data loss prevention
- Encryption at rest
Explanation
Correct Answer
D:DLP policies recognize sensitive information and govern transfers across channels such as mail, endpoints and storage. Classification accuracy influences results.
Incorrect Answers
A:Transport encryption such as TLS protects data while crossing network links when the underlying evidence concerns confidentiality and integrity across network path rather than the stated controls on outbound sensitive documents.
B:Tokenization replaces sensitive values with references mapped in a protected system for the specific concern of surrogate references for payment data, not the requirement involving controls on outbound sensitive documents.
C:Masking obscures specified fields in a presented view according to access context when analysts encounter limited exposure of sensitive field values; this question instead describes controls on outbound sensitive documents.
E:At-rest encryption protects stored ciphertext against unauthorized offline access when keys remain secure; the operational difference is confidentiality of stored backup contents versus the scenario's controls on outbound sensitive documents.