Sqreen provides runtime application self-protection (RASP) capabilities that allow teams to detect and respond to security threats in real time. Sqreen uses a structured automation mechanism called a playbook to define how security events are handled. A playbook consists of three key components: a trigger that detects suspicious or malicious behavior, a security response that defines what action Sqreen should take (such as blocking a request or flagging an attack), and a notification that sends alerts to external systems like Slack. The term "cookbook" is not used in Sqreen's alerting and response model, making options A and B incorrect. Option C incorrectly uses the phrase "Alert a response" instead of "security response," which does not accurately describe Sqreen's configuration model. By using playbooks, Sqreen enables automated detection, response, and team notification during the Operate and Monitor stage, ensuring rapid awareness and collaboration when security incidents occur.

Kubernetes clusters are managed and inspected using the kubectl command-line tool. To verify whether a Kubernetes cluster is functioning correctly, administrators commonly run kubectl version to confirm that both the client and server components are reachable and operational. This is followed by kubectl cluster-info, which displays information about the cluster's control plane and core services. These commands together confirm API server availability, cluster connectivity, and basic health status. The other options list invalid command names such as kube, kubernetes, or kube- etcd, which are not used for standard cluster validation. Performing these checks during the Operate and Monitor stage helps quickly identify whether application issues stem from cluster-level problems or application-level misconfigurations. This supports faster troubleshooting and more reliable production operations.

Secrets management tools such as HashiCorp Vault, AWS Secrets Manager, or Azure Key Vault are purpose-built to securely store, dynamically generate, rotate, and control access to sensitive credentials like API keys, database passwords, and certificates, removing the need to hardcode them into source code or pipeline configuration files. This directly matches Camila's requirement for automatic rotation and fine-grained access policies. A static code analyzer scans source code for vulnerabilities but does not manage or store secrets. A container registry stores and distributes container images, unrelated to credential management. A load balancer distributes network traffic across servers and has no role in secrets handling. Since Camila needs centralized, rotatable, access-controlled secret storage, a secrets management tool is correct.

Conjur policies define access controls, authentication rules, and secret variables, and they must be loaded into the correct policy branch. The conjur policy load command uses the -b flag to specify the policy branch and the -f flag to specify the policy file. To load a policy into the root branch, the correct command is conjur policy load -b root -f <file-name>. Options that reverse or misuse these flags are invalid and would either fail or load the policy incorrectly. Loading policies correctly during the Build and Test stage ensures that Jenkins pipelines can securely access secrets at runtime, enforcing centralized secret management, least-privilege access, and compliance with security requirements.

SLSA is a security framework specifically designed to protect the software supply chain by defining a set of increasing levels of build integrity requirements, including provenance generation, tamper-resistant build pipelines, and cryptographic attestations that let consumers verify how, where, and from what source an artifact was built. This directly addresses Hassan's need for tamper-evidence and origin verification between CI and the artifact repository. The OWASP Top 10 catalogs common web application vulnerability categories but does not define supply-chain build integrity controls. CIS Benchmarks provide configuration hardening guidance for operating systems and platforms, not build provenance. MITRE ATT&CK is a knowledge base of adversary tactics and techniques used for threat intelligence and detection engineering, not artifact integrity. Because Hassan specifically needs tamper resistance and provenance verification for build artifacts, SLSA is correct.