312-97 Exam Preparation Material | EC-Council Certified DevSecOps Engineer (ECDE)

Explanation:
Jenkins automatically assigns a unique identifier to each build using the environment variable BUILD_ID.
When integrating OWASP ZAP with Jenkins, appending ${BUILD_ID} to output filenames or reports ensures that every scan result corresponds to a specific build execution. This avoids overwriting previous reports and allows traceability between build artifacts and security findings. Variables such as ${ZAPROXY_HOME} refer to installation paths, not build uniqueness, while ${Profile_ID} and ${zap_scan} are not standard Jenkins variables for uniquely identifying builds. Using ${BUILD_ID} supports better auditing, historical analysis, and correlation between detected vulnerabilities and the exact build in which they were found, which is critical during the Build and Test stage of a DevSecOps pipeline.

Explanation:
Jenkins exposes a predefined endpoint for receiving GitHub webhook events. This endpoint is /github-webhook/ and must be appended to the Jenkins base URL in the GitHub webhook configuration.
Option C correctly matches the required endpoint format. The other options use incorrect casing, separators, or naming conventions that Jenkins does not recognize. Correct webhook configuration ensures that Jenkins jobs are automatically triggered when code changes occur in GitHub repositories. This integration supports continuous integration and immediate feedback during the Code stage of the DevSecOps pipeline.

Explanation:
Cloning a GitHub repository requires the standard Git command git clone followed by the correct repository URL format. GitHub repositories are structured as https://github.com/USERNAME/REPOSITORY.git, where USERNAME represents the account or organization name and REPOSITORY represents the project name.
Option B follows this exact structure.
Options using github clone are invalid because github is not a Git CLI command.
Options that reverse the order of USERNAME and REPOSITORY do not match GitHub’s repository structure and will fail. Cloning repositories during the Code stage allows DevSecOps engineers to run static analysis, dependency scanning, and other security checks locally without modifying the original repository, supporting secure and controlled analysis workflows.

Explanation:
Burp Suite’s Out-of-band Application Security Testing (OAST)feature is designed to detect vulnerabilities that do not produce immediate or visible responses during standard scanning. OAST works by triggering interactions such as DNS or HTTP callbacks, which occur outside the normal request-response cycle. This capability enables detection of blind vulnerabilities like blind SQL injection and server-side request forgery. Because findings are based on confirmed external interactions, OAST significantly reduces false positives. The other options listed are not valid Burp Suite features. Integrating OAST during the Build and Test stage improves the accuracy of dynamic security testing and ensures deeper coverage of complex and hard-to-detect vulnerability classes before applications are released.

Explanation:
When integrating security controls at the CDN edge with AWS CloudFront, the typical deployment model uses Lambda@Edge, which allows code to execute at CloudFront edge locations on viewer request/response or origin request/response events. Deploying the tCell agent “as a CloudFormation stack” describes packaging the required AWS resources (IAM roles, functions, permissions, and CloudFront associations) into infrastructure-as-code, but the actual attachment point for CloudFront request/response processing is Lambda@Edge.
Option C correctly reflects this: “plugging into CloudFront through Lambda@Edge.” Standard Lambda functions run in regional AWS environments and cannot directly run at CloudFront edge locations in the same way; therefore, “CloudFront through Lambda Function” is not the best match for edge enforcement needs like CSP handling and redirect protections.
Options that claim “plugging into CloudFormation” misunderstand CloudFormation’s role: it deploys resources, but it is not the runtime integration point. Hence, CloudFront + Lambda@Edge is the correct deployment approach.