Question 350An eBPF sensor runs correctly on staging nodes but fails after a production kernel upgrade because the required event hooks differ. What operating policy most directly addresses repeat exposure? Include kernel upgrade compatibility tests in security sensor lifecycle management. Combine image admission gates with runtime monitoring for high-risk namespaces. Version source-specific timestamp and field extraction rules with regression test records. Track kernel compatibility and approved eBPF program versions in workload deployment policy. ExplanationCorrect Answer A:Include kernel upgrade compatibility tests in security sensor lifecycle management. This safeguard limits repeat failures because kernel-attached instrumentation depends on supported kernel APIs and installed agent capabilities. The direct correction remains: Validate agent and kernel compatibility before broad rollout and keep supported upgrade fallbacks. Other Answers B:Image scanning identifies known package risks; runtime signals reveal actual execution anomalies. The lasting safeguard is to include kernel upgrade compatibility tests in security sensor lifecycle management. C:Security correlation depends on authoritative event timestamps, not necessarily the collector arrival time. A more direct preventive measure is to include kernel upgrade compatibility tests in security sensor lifecycle management. D:eBPF can instrument supported kernel events with verified programs, reducing the need for invasive unrestricted tooling. A more direct preventive measure is to include kernel upgrade compatibility tests in security sensor lifecycle management.
Question 351A Terraform repository contains an unrestricted public ingress rule that CI applies to every newly deployed cloud database. Which control should the team implement for this scenario? Assign guest OS patching and application hardening to the customer team while verifying provider infrastructure commitments. Replace shared credentials with scoped workload identities and protected secret injection at runtime. Add dependency scanning, signed artifacts and an admission gate for approved image digests. Run infrastructure-as-code security checks before apply and require explicit approval for risky rule exceptions. ExplanationCorrect Answer D:Run infrastructure-as-code security checks before apply and require explicit approval for risky rule exceptions. This action specifically works because preventive IaC scanning catches misconfiguration before reproducible automation spreads it across environments. Verify with: Submit a test public-ingress rule and confirm the pipeline blocks plan approval with actionable output. Other Answers A:Under IaaS shared responsibility, the provider secures underlying infrastructure while customers generally manage guest workloads. The corrective action for this requirement is to run infrastructure-as-code security checks before apply and require explicit approval for risky rule exceptions. B:CI/CD security needs restricted credential exposure and short-lived authority across build and deployment tasks. The corrective action for this requirement is to run infrastructure-as-code security checks before apply and require explicit approval for risky rule exceptions. C:DevSecOps protects software supply chain integrity across code, build, artifact and release boundaries. The required change instead is to run infrastructure-as-code security checks before apply and require explicit approval for risky rule exceptions.
Question 352A Terraform repository contains an unrestricted public ingress rule that CI applies to every newly deployed cloud database. Which technical principle explains the recommended measure? Preventive IaC scanning catches misconfiguration before reproducible automation spreads it across environments. Under IaaS shared responsibility, the provider secures underlying infrastructure while customers generally manage guest workloads. CI/CD security needs restricted credential exposure and short-lived authority across build and deployment tasks. DevSecOps protects software supply chain integrity across code, build, artifact and release boundaries. ExplanationCorrect Answer A:Preventive IaC scanning catches misconfiguration before reproducible automation spreads it across environments. The practical corrective action is: Run infrastructure-as-code security checks before apply and require explicit approval for risky rule exceptions. Confirm it by: Submit a test public-ingress rule and confirm the pipeline blocks plan approval with actionable output. Other Answers B:Under IaaS shared responsibility, the provider secures underlying infrastructure while customers generally manage guest workloads. By contrast, preventive IaC scanning catches misconfiguration before reproducible automation spreads it across environments. C:CI/CD security needs restricted credential exposure and short-lived authority across build and deployment tasks. By contrast, preventive IaC scanning catches misconfiguration before reproducible automation spreads it across environments. D:DevSecOps protects software supply chain integrity across code, build, artifact and release boundaries. In the stated system, preventive IaC scanning catches misconfiguration before reproducible automation spreads it across environments.
Question 353A Terraform repository contains an unrestricted public ingress rule that CI applies to every newly deployed cloud database. What evidence directly verifies the intended result? Review guest OS patch status and cloud provider responsibility documents for a representative VM. Submit a test public-ingress rule and confirm the pipeline blocks plan approval with actionable output. Try deploying an unsigned test image and confirm the admission system rejects it while a signed release passes. Run a contractor-role test and confirm production secrets cannot be read or used to deploy. ExplanationCorrect Answer B:Submit a test public-ingress rule and confirm the pipeline blocks plan approval with actionable output. The evidence confirms the intended action: Run infrastructure-as-code security checks before apply and require explicit approval for risky rule exceptions. It matters because preventive IaC scanning catches misconfiguration before reproducible automation spreads it across environments. Other Answers A:Under IaaS shared responsibility, the provider secures underlying infrastructure while customers generally manage guest workloads. Proving this correction calls for a check to submit a test public-ingress rule and confirm the pipeline blocks plan approval with actionable output. C:DevSecOps protects software supply chain integrity across code, build, artifact and release boundaries. The relevant acceptance check is to submit a test public-ingress rule and confirm the pipeline blocks plan approval with actionable output. D:CI/CD security needs restricted credential exposure and short-lived authority across build and deployment tasks. Proving this correction calls for a check to submit a test public-ingress rule and confirm the pipeline blocks plan approval with actionable output.
Question 354A Terraform repository contains an unrestricted public ingress rule that CI applies to every newly deployed cloud database. What operating policy most directly addresses repeat exposure? Require SBOM/provenance evidence and a controlled registry trust policy for production images. Audit pipeline role bindings and rotate legacy long-lived release credentials. Maintain a shared-responsibility matrix for each purchased cloud service model. Maintain policy-as-code checks and regression cases in each reusable cloud module. ExplanationCorrect Answer D:Maintain policy-as-code checks and regression cases in each reusable cloud module. This safeguard limits repeat failures because preventive IaC scanning catches misconfiguration before reproducible automation spreads it across environments. The direct correction remains: Run infrastructure-as-code security checks before apply and require explicit approval for risky rule exceptions. Other Answers A:DevSecOps protects software supply chain integrity across code, build, artifact and release boundaries. A more direct preventive measure is to maintain policy-as-code checks and regression cases in each reusable cloud module. B:CI/CD security needs restricted credential exposure and short-lived authority across build and deployment tasks. The stronger recurring control is to maintain policy-as-code checks and regression cases in each reusable cloud module. C:Under IaaS shared responsibility, the provider secures underlying infrastructure while customers generally manage guest workloads. The stronger recurring control is to maintain policy-as-code checks and regression cases in each reusable cloud module.
Question 355A CI pipeline builds a container image using unknown dependencies and deploys it directly without verifying provenance. Which control should the team implement for this scenario? Run infrastructure-as-code security checks before apply and require explicit approval for risky rule exceptions. Add runtime workload behavior monitoring and response, not just static image vulnerability scanning. Replace shared credentials with scoped workload identities and protected secret injection at runtime. Add dependency scanning, signed artifacts and an admission gate for approved image digests. ExplanationCorrect Answer D:Add dependency scanning, signed artifacts and an admission gate for approved image digests. This action specifically works because devSecOps protects software supply chain integrity across code, build, artifact and release boundaries. Verify with: Try deploying an unsigned test image and confirm the admission system rejects it while a signed release passes. Other Answers A:Preventive IaC scanning catches misconfiguration before reproducible automation spreads it across environments. The required change instead is to add dependency scanning, signed artifacts and an admission gate for approved image digests. B:Image scanning identifies known package risks; runtime signals reveal actual execution anomalies. The required change instead is to add dependency scanning, signed artifacts and an admission gate for approved image digests. C:CI/CD security needs restricted credential exposure and short-lived authority across build and deployment tasks. The corrective action for this requirement is to add dependency scanning, signed artifacts and an admission gate for approved image digests.
Question 356A CI pipeline builds a container image using unknown dependencies and deploys it directly without verifying provenance. Which technical principle explains the recommended measure? Image scanning identifies known package risks; runtime signals reveal actual execution anomalies. Preventive IaC scanning catches misconfiguration before reproducible automation spreads it across environments. DevSecOps protects software supply chain integrity across code, build, artifact and release boundaries. CI/CD security needs restricted credential exposure and short-lived authority across build and deployment tasks. ExplanationCorrect Answer C:DevSecOps protects software supply chain integrity across code, build, artifact and release boundaries. The practical corrective action is: Add dependency scanning, signed artifacts and an admission gate for approved image digests. Confirm it by: Try deploying an unsigned test image and confirm the admission system rejects it while a signed release passes. Other Answers A:Image scanning identifies known package risks; runtime signals reveal actual execution anomalies. By contrast, devSecOps protects software supply chain integrity across code, build, artifact and release boundaries. B:Preventive IaC scanning catches misconfiguration before reproducible automation spreads it across environments. By contrast, devSecOps protects software supply chain integrity across code, build, artifact and release boundaries. D:CI/CD security needs restricted credential exposure and short-lived authority across build and deployment tasks. In the stated system, devSecOps protects software supply chain integrity across code, build, artifact and release boundaries.
Question 357A CI pipeline builds a container image using unknown dependencies and deploys it directly without verifying provenance. What evidence directly verifies the intended result? Try deploying an unsigned test image and confirm the admission system rejects it while a signed release passes. Submit a test public-ingress rule and confirm the pipeline blocks plan approval with actionable output. Run a harmless unauthorized process in a test pod and verify the expected detection and containment policy. Run a contractor-role test and confirm production secrets cannot be read or used to deploy. ExplanationCorrect Answer A:Try deploying an unsigned test image and confirm the admission system rejects it while a signed release passes. The evidence confirms the intended action: Add dependency scanning, signed artifacts and an admission gate for approved image digests. It matters because devSecOps protects software supply chain integrity across code, build, artifact and release boundaries. Other Answers B:Preventive IaC scanning catches misconfiguration before reproducible automation spreads it across environments. A more meaningful verification is to try deploying an unsigned test image and confirm the admission system rejects it while a signed release passes. C:Image scanning identifies known package risks; runtime signals reveal actual execution anomalies. A more meaningful verification is to try deploying an unsigned test image and confirm the admission system rejects it while a signed release passes. D:CI/CD security needs restricted credential exposure and short-lived authority across build and deployment tasks. The failure is checked more directly by a test to try deploying an unsigned test image and confirm the admission system rejects it while a signed release passes.
Question 358A CI pipeline builds a container image using unknown dependencies and deploys it directly without verifying provenance. What operating policy most directly addresses repeat exposure? Combine image admission gates with runtime monitoring for high-risk namespaces. Audit pipeline role bindings and rotate legacy long-lived release credentials. Require SBOM/provenance evidence and a controlled registry trust policy for production images. Maintain policy-as-code checks and regression cases in each reusable cloud module. ExplanationCorrect Answer C:Require SBOM/provenance evidence and a controlled registry trust policy for production images. This safeguard limits repeat failures because devSecOps protects software supply chain integrity across code, build, artifact and release boundaries. The direct correction remains: Add dependency scanning, signed artifacts and an admission gate for approved image digests. Other Answers A:Image scanning identifies known package risks; runtime signals reveal actual execution anomalies. Reducing this risk requires a practice to require SBOM/provenance evidence and a controlled registry trust policy for production images. B:CI/CD security needs restricted credential exposure and short-lived authority across build and deployment tasks. The lasting safeguard is to require SBOM/provenance evidence and a controlled registry trust policy for production images. D:Preventive IaC scanning catches misconfiguration before reproducible automation spreads it across environments. Reducing this risk requires a practice to require SBOM/provenance evidence and a controlled registry trust policy for production images.
Question 359A release team stores production container registry credentials in plain CI variables viewable by every contractor. Which control should the team implement for this scenario? Replace shared credentials with scoped workload identities and protected secret injection at runtime. Run infrastructure-as-code security checks before apply and require explicit approval for risky rule exceptions. Add dependency scanning, signed artifacts and an admission gate for approved image digests. Evaluate Cisco Multicloud Defense policy visibility and controlled enforcement across both cloud networks. ExplanationCorrect Answer A:Replace shared credentials with scoped workload identities and protected secret injection at runtime. This action specifically works because cI/CD security needs restricted credential exposure and short-lived authority across build and deployment tasks. Verify with: Run a contractor-role test and confirm production secrets cannot be read or used to deploy. Other Answers B:Preventive IaC scanning catches misconfiguration before reproducible automation spreads it across environments. A more relevant action is to replace shared credentials with scoped workload identities and protected secret injection at runtime. C:DevSecOps protects software supply chain integrity across code, build, artifact and release boundaries. A more relevant action is to replace shared credentials with scoped workload identities and protected secret injection at runtime. D:Multicloud network security needs shared visibility and policy context across different cloud control planes. The required change instead is to replace shared credentials with scoped workload identities and protected secret injection at runtime.
Question 360A release team stores production container registry credentials in plain CI variables viewable by every contractor. Which technical principle explains the recommended measure? Preventive IaC scanning catches misconfiguration before reproducible automation spreads it across environments. CI/CD security needs restricted credential exposure and short-lived authority across build and deployment tasks. Multicloud network security needs shared visibility and policy context across different cloud control planes. DevSecOps protects software supply chain integrity across code, build, artifact and release boundaries. ExplanationCorrect Answer B:CI/CD security needs restricted credential exposure and short-lived authority across build and deployment tasks. The practical corrective action is: Replace shared credentials with scoped workload identities and protected secret injection at runtime. Confirm it by: Run a contractor-role test and confirm production secrets cannot be read or used to deploy. Other Answers A:Preventive IaC scanning catches misconfiguration before reproducible automation spreads it across environments. In the stated system, CI/CD security needs restricted credential exposure and short-lived authority across build and deployment tasks. C:Multicloud network security needs shared visibility and policy context across different cloud control planes. In the stated system, CI/CD security needs restricted credential exposure and short-lived authority across build and deployment tasks. D:DevSecOps protects software supply chain integrity across code, build, artifact and release boundaries. In the stated system, CI/CD security needs restricted credential exposure and short-lived authority across build and deployment tasks.