McAfee-Secured Website

Exam Bundle

Exam Code: CAS-005

Exam Name CompTIA SecurityX

Certification Provider: CompTIA

Corresponding Certification: CASP

CompTIA CAS-005 Bundle $44.99

100% CompTIA CAS-005 Guaranteed Success With Testking Training Materials

Get Real CAS-005 Exam Questions & Expert Verified Answers as Experienced on the Real Exam!

  • Questions & Answers

    CAS-005 Questions & Answers

    482 Questions & Answers

    The ultimate exam preparation tool, Questions & Answers mirrors the actual CAS-005 exam while allowing you to hone and measure every aspect of your test-taking ability.

  • CAS-005 Video Course

    CAS-005 Video Course

    180 Video Lectures

    CAS-005 Video Course is developed by CompTIA Professionals to help you pass the CAS-005 exam.

    Description

    This course will improve your knowledge and skills required to pass CompTIA SecurityX exam.
  • Study Guide

    CAS-005 Study Guide

    903 PDF Pages

    Developed by industry experts, this 903-page guide spells out in painstaking detail all of the information you need to ace CAS-005 exam.

CompTIA SecurityX (CAS-005) Practice Tests

Satisfaction Guaranteed

Money Back Guarantee

Testking provides hassle-free money back guarantee with our products. That is because we have 100% trust in the abilities of our professional and experience product team, and our record is a proof of that.

99.6% PASS RATE
Total Cost: $194.97
Bundle Price: $149.98

Purchase Individually

  • Questions & Answers

    Questions & Answers

    482 Questions

    $124.99
  • CAS-005 Video Course

    Video Course

    180 Video Lectures

    $39.99
  • Study Guide

    Study Guide

    903 PDF Pages

    $29.99

CompTIA CAS-005 Practice Test 16

Question 150

After the team responds to the following issue, which finding best demonstrates the desired security outcome? A research laboratory's remote access design ignores loss of the identity provider during a crisis.

  1. An authorized resilience drill grants temporary emergency access without leaving standing broadly privileged credentials.
  2. A simulated abusive client receives controlled limits without degrading other authorized tenants.
  3. An exercise demonstrates documented recovery behavior under regional loss within authorized cost and sovereignty limits.
  4. A test spray of prompts is rate limited and privileged access demands phishing-resistant proof.

Explanation

Correct Answer

A:

This is direct test evidence of the control objective in the case: A research laboratory's remote access design ignores loss of the identity provider during a crisis. It demonstrates that the proposed response, establish a narrowly scoped, audited break-glass recovery mechanism independent of routine federation., produces the measurable result an authorized resilience drill grants temporary emergency access without leaving standing broadly privileged credentials. The observation tests a relevant security outcome rather than an unrelated control or reporting activity.

Incorrect Answers

B:

For the issue “A research laboratory's remote access design ignores loss of the identity provider during a crisis”, measuring “A simulated abusive client receives controlled limits without degrading other authorized tenants.” would validate “A financial API gateway authenticates users but does not throttle partner API calls, allowing one tenant to exhaust service workers” instead of the required control effect: an authorized resilience drill grants temporary emergency access without leaving standing broadly privileged credentials.

C:

“Compare cross-region and independent-provider resiliency options, including replicated state and operating complexity” should produce “An exercise demonstrates documented recovery behavior under regional loss within authorized cost and sovereignty limits” in its own test case. The present requirement is instead checked by “An authorized resilience drill grants temporary emergency access without leaving standing broadly privileged credentials”, which validates “Establish a narrowly scoped, audited break-glass recovery mechanism independent of routine federation” rather than the alternate control.

D:

Observation “A test spray of prompts is rate limited and privileged access demands phishing-resistant proof.” would be useful for “An application uses push MFA with unlimited retries after repeated suspicious prompts and a possible fatigue attack”, but it does not prove that the response to “A research laboratory's remote access design ignores loss of the identity provider during a crisis” achieved the relevant outcome, an authorized resilience drill grants temporary emergency access without leaving standing broadly privileged credentials.

Question 151

A cross-functional security group is considering a decision: A product team runs SAST only after release candidates are frozen, leaving no time to fix critical defects. What is the most appropriate control or investigation response?

  1. Define emergency patch exceptions retaining minimum signed approvals and automated critical security gates.
  2. Integrate identity and workload audit logs with central correlation and retention matching the incident scope.
  3. Integrate SAST at pull request review with triage thresholds and appropriate exception approvals.
  4. Integrate sensitive-data checks into build artifacts, seed-data handling, and lifecycle disposal.

Explanation

Correct Answer

C:

Integrate SAST at pull request review with triage thresholds and appropriate exception approvals. The acceptance check is that a deliberately vulnerable test change is flagged before merge with a tracked disposition. That outcome checks whether the requirement is met, rather than treating completion of a security task as proof of effectiveness.

Incorrect Answers

A:

The option “Define emergency patch exceptions retaining minimum signed approvals and automated critical security gates.” assumes an issue like “A developer disables branch protection to hotfix a critical issue, bypassing mandatory code review and automated security tests”, not the specific observed weakness “A product team runs SAST only after release candidates are frozen, leaving no time to fix critical defects”; it leaves the evidence goal unmet: a deliberately vulnerable test change is flagged before merge with a tracked disposition.

B:

“Integrate identity and workload audit logs with central correlation and retention matching the incident scope” addresses “A bank has EDR on laptops but no telemetry from its cloud workload identity provider during account compromise investigations”, with “A test anomalous cloud login is attributable across user, device, and application records” as its acceptance test. Here the specific problem is “A cross-functional security group is considering a decision: A product team runs SAST only after release candidates are frozen, leaving no time to fix critical defects”: it requires “Integrate SAST at pull request review with triage thresholds and appropriate exception approvals” and evidence that “A deliberately vulnerable test change is flagged before merge with a tracked disposition”.

D:

Although “Integrate sensitive-data checks into build artifacts, seed-data handling, and lifecycle disposal.” is a reasonable response to “A SaaS application has a compliance rule to erase user data, but archived deployment images still contain seeded production records”, this case instead concerns “A product team runs SAST only after release candidates are frozen, leaving no time to fix critical defects”, for which success requires that a deliberately vulnerable test change is flagged before merge with a tracked disposition.

Question 152

Which test or documented result best shows that the underlying issue was properly addressed? A product team runs SAST only after release candidates are frozen, leaving no time to fix critical defects.

  1. A deliberately vulnerable test change is flagged before merge with a tracked disposition.
  2. Valid clients accept authorized hostnames and reject the deliberately mismatched certificate.
  3. A known vulnerable base-layer package triggers a pre-deployment remediation gate.
  4. A deliberately unsafe redirect change fails before production deployment.

Explanation

Correct Answer

A:

This is direct test evidence of the control objective in the case: A product team runs SAST only after release candidates are frozen, leaving no time to fix critical defects. It demonstrates that the proposed response, integrate SAST at pull request review with triage thresholds and appropriate exception approvals., produces the measurable result a deliberately vulnerable test change is flagged before merge with a tracked disposition. The observation tests a relevant security outcome rather than an unrelated control or reporting activity.

Incorrect Answers

B:

In “An enterprise faces this security constraint: A certificate authority issues server certificates without consistent hostname extension profiles, causing different clients to accept mismatched endpoints”, “Valid clients accept authorized hostnames and reject the deliberately mismatched certificate” is the acceptance signal for “Enforce certificate templates with correct subject alternative names and usage constraints”. The required proof for the selected response “Integrate SAST at pull request review with triage thresholds and appropriate exception approvals” is “A deliberately vulnerable test change is flagged before merge with a tracked disposition”.

C:

In the problem “A product team runs SAST only after release candidates are frozen, leaving no time to fix critical defects”, evidence “A known vulnerable base-layer package triggers a pre-deployment remediation gate.” is not decisive because it tests “An application uses dynamic code scanning but never tests vulnerable open-source libraries in container base images”; the requested validation is a deliberately vulnerable test change is flagged before merge with a tracked disposition.

D:

For the issue “A product team runs SAST only after release candidates are frozen, leaving no time to fix critical defects”, measuring “A deliberately unsafe redirect change fails before production deployment.” would validate “A testing team frequently skips security regression on minor user-interface updates, accidentally reintroducing unsafe redirect handling” instead of the required control effect: a deliberately vulnerable test change is flagged before merge with a tracked disposition.

Question 153

In a control effectiveness review, the issue is: A CI pipeline imports dependencies without a software bill of materials or cryptographic provenance. Which intervention is most defensible for the situation?

  1. Generate and verify SBOMs and signed build attestations during trusted pipeline execution.
  2. Establish controlled build environments, source integrity checks, and cryptographically signed deployment artifacts.
  3. Require manufacturer-signed firmware verification and approved chain-of-custody checks at receiving.
  4. Verify trusted metadata origin and signing certificates before applying federation changes.

Explanation

Correct Answer

A:

Generate and verify SBOMs and signed build attestations during trusted pipeline execution. The acceptance check is that a release artifact can be traced to source, dependency versions, builder identity, and verified signatures. That outcome checks whether the requirement is met, rather than treating completion of a security task as proof of effectiveness.

Incorrect Answers

B:

Although “Establish controlled build environments, source integrity checks, and cryptographically signed deployment artifacts.” is a reasonable response to “A cloud-native project deploys to production from developers' workstations without reproducible builders”, this case instead concerns “A CI pipeline imports dependencies without a software bill of materials or cryptographic provenance”, for which success requires that a release artifact can be traced to source, dependency versions, builder identity, and verified signatures.

C:

The option “Require manufacturer-signed firmware verification and approved chain-of-custody checks at receiving.” assumes an issue like “A supplier offers preloaded network hardware whose firmware integrity cannot be independently validated”, not the specific observed weakness “A CI pipeline imports dependencies without a software bill of materials or cryptographic provenance”; it leaves the evidence goal unmet: a release artifact can be traced to source, dependency versions, builder identity, and verified signatures.

D:

“Tampered metadata is rejected and a legitimate scheduled rollover is audited and accepted” would be meaningful evidence for “Verify trusted metadata origin and signing certificates before applying federation changes” in the case “An external partner's federation metadata changes, but trust is updated by copying the partner's unsigned emailed XML”. It does not replace “Generate and verify SBOMs and signed build attestations during trusted pipeline execution” to correct “A CI pipeline imports dependencies without a software bill of materials or cryptographic provenance” and verify “A release artifact can be traced to source, dependency versions, builder identity, and verified signatures”.

Question 154

A follow-up assurance review considers this problem: A CI pipeline imports dependencies without a software bill of materials or cryptographic provenance. Which outcome best shows the intended improvement?

  1. A deliberately unsafe redirect change fails before production deployment.
  2. A release artifact can be traced to source, dependency versions, builder identity, and verified signatures.
  3. Production accepts only artifacts whose build provenance and signatures validate.
  4. An unsigned or altered image fails admission while the verified release is deployed.

Explanation

Correct Answer

B:

This is direct test evidence of the control objective in the case: A CI pipeline imports dependencies without a software bill of materials or cryptographic provenance. It demonstrates that the proposed response, generate and verify SBOMs and signed build attestations during trusted pipeline execution., produces the measurable result a release artifact can be traced to source, dependency versions, builder identity, and verified signatures. The observation tests a relevant security outcome rather than an unrelated control or reporting activity.

Incorrect Answers

A:

In the problem “A CI pipeline imports dependencies without a software bill of materials or cryptographic provenance”, evidence “A deliberately unsafe redirect change fails before production deployment.” is not decisive because it tests “A testing team frequently skips security regression on minor user-interface updates, accidentally reintroducing unsafe redirect handling”; the requested validation is a release artifact can be traced to source, dependency versions, builder identity, and verified signatures.

C:

“Establish controlled build environments, source integrity checks, and cryptographically signed deployment artifacts” should produce “Production accepts only artifacts whose build provenance and signatures validate” in its own test case. The present requirement is instead checked by “A release artifact can be traced to source, dependency versions, builder identity, and verified signatures”, which validates “Generate and verify SBOMs and signed build attestations during trusted pipeline execution” rather than the alternate control.

D:

Observation “An unsigned or altered image fails admission while the verified release is deployed.” would be useful for “A container deployment uses a publicly accessible image registry with no signature verification in production admission”, but it does not prove that the response to “A CI pipeline imports dependencies without a software bill of materials or cryptographic provenance” achieved the relevant outcome, a release artifact can be traced to source, dependency versions, builder identity, and verified signatures.

Question 155

A security architect is asked to resolve this problem: A medical IoT application has security requirements only as general text with no testable authorization behavior. Select the MOST directly relevant action.

  1. Add unit and adversarial security regression tests that fail on forbidden object types or execution.
  2. Implement server-side object-level authorization checks with automated cross-user negative tests.
  3. Express security requirements as verifiable misuse and access-control acceptance criteria in design and tests.
  4. Design 802.1X certificate- or identity-backed access with separate guest policy enforcement.

Explanation

Correct Answer

C:

Express security requirements as verifiable misuse and access-control acceptance criteria in design and tests. The acceptance check is that an unauthorized role fails a documented negative test and the control maps to its original requirement. That outcome checks whether the requirement is met, rather than treating completion of a security task as proof of effectiveness.

Incorrect Answers

A:

The option “Add unit and adversarial security regression tests that fail on forbidden object types or execution.” assumes an issue like “A code reviewer finds unsafe deserialization in a critical service but only a documentation ticket is created”, not the specific observed weakness “A medical IoT application has security requirements only as general text with no testable authorization behavior”; it leaves the evidence goal unmet: an unauthorized role fails a documented negative test and the control maps to its original requirement.

B:

The proposal “Implement server-side object-level authorization checks with automated cross-user negative tests” manages “An enterprise faces this security constraint: A product's code review finds missing authorization on resource APIs, but a general security awareness course is proposed as remediation”, where successful operation means “A user cannot read another tenant's resource using a modified identifier”. The present issue instead needs “Express security requirements as verifiable misuse and access-control acceptance criteria in design and tests” to establish “An unauthorized role fails a documented negative test and the control maps to its original requirement”.

D:

Although “Design 802.1X certificate- or identity-backed access with separate guest policy enforcement.” is a reasonable response to “A corporate Wi-Fi onboarding program uses one shared password for staff and visitors, defeating individual accountability”, this case instead concerns “A medical IoT application has security requirements only as general text with no testable authorization behavior”, for which success requires that an unauthorized role fails a documented negative test and the control maps to its original requirement.

Question 156

After the team responds to the following issue, which finding best demonstrates the desired security outcome? A medical IoT application has security requirements only as general text with no testable authorization behavior.

  1. A crafted event cannot invoke unauthorized actions and vulnerable package versions are detected in the build.
  2. An unauthorized role fails a documented negative test and the control maps to its original requirement.
  3. A deliberately unsafe redirect change fails before production deployment.
  4. A tampered firmware image fails device attestation and the receipt is quarantined.

Explanation

Correct Answer

B:

This is direct test evidence of the control objective in the case: A medical IoT application has security requirements only as general text with no testable authorization behavior. It demonstrates that the proposed response, express security requirements as verifiable misuse and access-control acceptance criteria in design and tests., produces the measurable result an unauthorized role fails a documented negative test and the control maps to its original requirement. The observation tests a relevant security outcome rather than an unrelated control or reporting activity.

Incorrect Answers

A:

“A crafted event cannot invoke unauthorized actions and vulnerable package versions are detected in the build” would verify “Model event input validation, dependency risk, IAM scope, and downstream resource access for the function” for the situation “An enterprise faces this security constraint: A software team assumes a serverless function cannot be attacked because it has no managed operating system”. Here the required evidence is “An unauthorized role fails a documented negative test and the control maps to its original requirement” after “Express security requirements as verifiable misuse and access-control acceptance criteria in design and tests”; the alternative observation does not test that control.

C:

In the problem “A medical IoT application has security requirements only as general text with no testable authorization behavior”, evidence “A deliberately unsafe redirect change fails before production deployment.” is not decisive because it tests “A testing team frequently skips security regression on minor user-interface updates, accidentally reintroducing unsafe redirect handling”; the requested validation is an unauthorized role fails a documented negative test and the control maps to its original requirement.

D:

For the issue “A medical IoT application has security requirements only as general text with no testable authorization behavior”, measuring “A tampered firmware image fails device attestation and the receipt is quarantined.” would validate “A supplier offers preloaded network hardware whose firmware integrity cannot be independently validated” instead of the required control effect: an unauthorized role fails a documented negative test and the control maps to its original requirement.

Question 157

A senior engineer examines the following finding: A developer disables branch protection to hotfix a critical issue, bypassing mandatory code review and automated security tests. Which action most directly addresses the requirement?

  1. Define emergency patch exceptions retaining minimum signed approvals and automated critical security gates.
  2. Generate and verify SBOMs and signed build attestations during trusted pipeline execution.
  3. Design an explicit fail-secure authorization fallback with documented availability exceptions for safe public functions.
  4. Include targeted security regression checks in automated pipelines based on changed components and threat coverage.

Explanation

Correct Answer

A:

Define emergency patch exceptions retaining minimum signed approvals and automated critical security gates. The acceptance check is that the emergency release preserves traceable approval and demonstrates key security checks before deployment. That outcome checks whether the requirement is met, rather than treating completion of a security task as proof of effectiveness.

Incorrect Answers

B:

Although “Generate and verify SBOMs and signed build attestations during trusted pipeline execution.” is a reasonable response to “A CI pipeline imports dependencies without a software bill of materials or cryptographic provenance”, this case instead concerns “A developer disables branch protection to hotfix a critical issue, bypassing mandatory code review and automated security tests”, for which success requires that the emergency release preserves traceable approval and demonstrates key security checks before deployment.

C:

The option “Design an explicit fail-secure authorization fallback with documented availability exceptions for safe public functions.” assumes an issue like “An organization deploys a policy decision point but leaves enforcement points accepting requests when the decision service is unavailable”, not the specific observed weakness “A developer disables branch protection to hotfix a critical issue, bypassing mandatory code review and automated security tests”; it leaves the evidence goal unmet: the emergency release preserves traceable approval and demonstrates key security checks before deployment.

D:

“A deliberately unsafe redirect change fails before production deployment” would be meaningful evidence for “Include targeted security regression checks in automated pipelines based on changed components and threat coverage” in the case “A testing team frequently skips security regression on minor user-interface updates, accidentally reintroducing unsafe redirect handling”. It does not replace “Define emergency patch exceptions retaining minimum signed approvals and automated critical security gates” to correct “A developer disables branch protection to hotfix a critical issue, bypassing mandatory code review and automated security tests” and verify “The emergency release preserves traceable approval and demonstrates key security checks before deployment”.

Question 158

Which test or documented result best shows that the underlying issue was properly addressed? A developer disables branch protection to hotfix a critical issue, bypassing mandatory code review and automated security tests.

  1. An unsigned or altered image fails admission while the verified release is deployed.
  2. The emergency release preserves traceable approval and demonstrates key security checks before deployment.
  3. A release artifact can be traced to source, dependency versions, builder identity, and verified signatures.
  4. A known vulnerable base-layer package triggers a pre-deployment remediation gate.

Explanation

Correct Answer

B:

This is direct test evidence of the control objective in the case: A developer disables branch protection to hotfix a critical issue, bypassing mandatory code review and automated security tests. It demonstrates that the proposed response, define emergency patch exceptions retaining minimum signed approvals and automated critical security gates., produces the measurable result the emergency release preserves traceable approval and demonstrates key security checks before deployment. The observation tests a relevant security outcome rather than an unrelated control or reporting activity.

Incorrect Answers

A:

In the problem “A developer disables branch protection to hotfix a critical issue, bypassing mandatory code review and automated security tests”, evidence “An unsigned or altered image fails admission while the verified release is deployed.” is not decisive because it tests “A container deployment uses a publicly accessible image registry with no signature verification in production admission”; the requested validation is the emergency release preserves traceable approval and demonstrates key security checks before deployment.

C:

“Generate and verify SBOMs and signed build attestations during trusted pipeline execution” should produce “A release artifact can be traced to source, dependency versions, builder identity, and verified signatures” in its own test case. The present requirement is instead checked by “The emergency release preserves traceable approval and demonstrates key security checks before deployment”, which validates “Define emergency patch exceptions retaining minimum signed approvals and automated critical security gates” rather than the alternate control.

D:

Observation “A known vulnerable base-layer package triggers a pre-deployment remediation gate.” would be useful for “An application uses dynamic code scanning but never tests vulnerable open-source libraries in container base images”, but it does not prove that the response to “A developer disables branch protection to hotfix a critical issue, bypassing mandatory code review and automated security tests” achieved the relevant outcome, the emergency release preserves traceable approval and demonstrates key security checks before deployment.

Question 159

An enterprise faces this security constraint: A supplier offers preloaded network hardware whose firmware integrity cannot be independently validated. Which proposal best addresses the stated risk?

  1. Require manufacturer-signed firmware verification and approved chain-of-custody checks at receiving.
  2. Establish controlled build environments, source integrity checks, and cryptographically signed deployment artifacts.
  3. Add location constraints and approved region policies to deployment and data replication workflows.
  4. Implement server-side object-level authorization checks with automated cross-user negative tests.

Explanation

Correct Answer

A:

Require manufacturer-signed firmware verification and approved chain-of-custody checks at receiving. The acceptance check is that a tampered firmware image fails device attestation and the receipt is quarantined. That outcome checks whether the requirement is met, rather than treating completion of a security task as proof of effectiveness.

Incorrect Answers

B:

“Production accepts only artifacts whose build provenance and signatures validate” would be meaningful evidence for “Establish controlled build environments, source integrity checks, and cryptographically signed deployment artifacts” in the case “A cloud-native project deploys to production from developers' workstations without reproducible builders”. It does not replace “Require manufacturer-signed firmware verification and approved chain-of-custody checks at receiving” to correct “An enterprise faces this security constraint: A supplier offers preloaded network hardware whose firmware integrity cannot be independently validated” and verify “A tampered firmware image fails device attestation and the receipt is quarantined”.

C:

For “A cloud team stores application data in a region that meets latency requirements but breaches the signed customer residency agreement”, “Add location constraints and approved region policies to deployment and data replication workflows” has a clear validation signal: “A deployment to a disallowed region fails policy evaluation and permitted replicas stay within contract scope”. But “An enterprise faces this security constraint: A supplier offers preloaded network hardware whose firmware integrity cannot be independently validated” calls for “Require manufacturer-signed firmware verification and approved chain-of-custody checks at receiving”; the other intervention cannot demonstrate “A tampered firmware image fails device attestation and the receipt is quarantined”.

D:

Although “Implement server-side object-level authorization checks with automated cross-user negative tests.” is a reasonable response to “A product's code review finds missing authorization on resource APIs, but a general security awareness course is proposed as remediation”, this case instead concerns “A supplier offers preloaded network hardware whose firmware integrity cannot be independently validated”, for which success requires that a tampered firmware image fails device attestation and the receipt is quarantined.

Question 160

A follow-up assurance review considers this problem: A supplier offers preloaded network hardware whose firmware integrity cannot be independently validated. Which outcome best shows the intended improvement?

  1. A deliberately unsafe redirect change fails before production deployment.
  2. An unauthorized role fails a documented negative test and the control maps to its original requirement.
  3. A tampered firmware image fails device attestation and the receipt is quarantined.
  4. An unsigned or altered image fails admission while the verified release is deployed.

Explanation

Correct Answer

C:

This is direct test evidence of the control objective in the case: A supplier offers preloaded network hardware whose firmware integrity cannot be independently validated. It demonstrates that the proposed response, require manufacturer-signed firmware verification and approved chain-of-custody checks at receiving., produces the measurable result a tampered firmware image fails device attestation and the receipt is quarantined. The observation tests a relevant security outcome rather than an unrelated control or reporting activity.

Incorrect Answers

A:

In “A testing team frequently skips security regression on minor user-interface updates, accidentally reintroducing unsafe redirect handling”, “A deliberately unsafe redirect change fails before production deployment” is the acceptance signal for “Include targeted security regression checks in automated pipelines based on changed components and threat coverage”. The required proof for the selected response “Require manufacturer-signed firmware verification and approved chain-of-custody checks at receiving” is “A tampered firmware image fails device attestation and the receipt is quarantined”.

B:

Observation “An unauthorized role fails a documented negative test and the control maps to its original requirement.” would be useful for “A medical IoT application has security requirements only as general text with no testable authorization behavior”, but it does not prove that the response to “A supplier offers preloaded network hardware whose firmware integrity cannot be independently validated” achieved the relevant outcome, a tampered firmware image fails device attestation and the receipt is quarantined.

D:

For the issue “A supplier offers preloaded network hardware whose firmware integrity cannot be independently validated”, measuring “An unsigned or altered image fails admission while the verified release is deployed.” would validate “A container deployment uses a publicly accessible image registry with no signature verification in production admission” instead of the required control effect: a tampered firmware image fails device attestation and the receipt is quarantined.