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.

DAST tools operate as black-box testers against a running application, simulating external attacker behavior by sending crafted HTTP requests and observing responses to detect vulnerabilities such as reflected cross-site scripting, broken authentication, and injection flaws -- exactly matching Farah's scenario of testing a live staging instance without source code access.
SAST requires access to source code or binaries and analyzes them statically, which contradicts Farah's black-box, no-source-access constraint. SCA specifically targets known vulnerabilities in third-party and open-source dependencies rather than application logic flaws like XSS. Secret scanning searches repositories or file systems for exposed credentials, unrelated to runtime attacker-perspective testing. Since Farah needs external, black-box testing of a live application, DAST is the correct answer.

A service mesh such as Istio or Linkerd injects sidecar proxies alongside each microservice to transparently handle mutual TLS (mTLS) authentication and encryption between services, providing zero-trust, code-free security for service-to-service communication -- exactly what Bruno needs. A WAF at the ingress protects against attacks arriving from outside the cluster targeting the application layer (e.g., HTTP-based attacks), but it does not provide mutual authentication and encryption between internal microservices. A VPN between developer laptops secures remote access for individual engineers, unrelated to intra-cluster service communication.
Static application firewall rules are generally coarse network-layer controls that do not provide identity-based mutual authentication or automatic encryption without code changes. Since Bruno needs code-transparent mTLS between microservices, a service mesh is correct.

On Debian- and Ubuntu-based systems, ModSecurity for Apache is installed using the package libapache2- mod-security2. The correct command to install this package is sudo apt install libapache2-mod-security2 -y, where the -y flag automatically confirms installation prompts. The other options include invalid flags that are not recognized by the package manager and would result in command failure. Installing ModSecurity during the Operate and Monitor stage provides an additional layer of defense by inspecting incoming HTTP requests and blocking malicious traffic such as SQL injection, cross-site scripting, and protocol violations. A Web Application Firewall helps protect deployed applications from common attack vectors and supports defense- in-depth strategies in production environments.

To inspect mount propagation modes for Docker containers, Rockmond needs to list all container IDs and then inspect their configuration. The docker ps --quiet --all command outputs container IDs only, which are then passed to docker inspect using xargs. The --format option allows extraction of specific fields, such as mount propagation settings. Option C correctly uses valid flags (--quiet --all) and proper formatting syntax. Options A and D incorrectly use single hyphens, and option B omits the equals sign, which is required to display the propagation value. Inspecting mount propagation during the Operate and Monitor stage helps prevent unintended privilege escalation or data modification by other containers, aligning with container hardening best practices.