BS Cyber Security · Cloud Security

Unit 2: Shared Responsibility MCQs

50 solved multiple choice questions with answers and short explanations.

Q1. Which statement best describes Shared Responsibility Concepts within Shared Responsibility? Context: BS Cyber Security / Cloud Security / Shared Responsibility.

  1. AIt can be evaluated without considering threats or assets.
  2. BIt should be understood through its security objective, threat model, controls, assumptions, and operational context.
  3. CIt is only a visual design preference with no security effect.
  4. DIt guarantees complete security once installed.
Show answer
Answer: B. It should be understood through its security objective, threat model, controls, assumptions, and operational context.Cloud Security → Shared Responsibility → Shared Responsibility Concepts: It should be understood through its security objective, threat model, controls, assumptions, and operational context.
Report a mistake

Q2. What is the primary defensive goal when applying Shared Responsibility Concepts? Context: BS Cyber Security / Cloud Security / Shared Responsibility.

  1. AMaximize restrictions even if essential services stop working.
  2. BRemove all monitoring so security events remain hidden.
  3. CAssume every system is secure unless an incident occurs.
  4. DReduce relevant risk while preserving required confidentiality, integrity, availability, accountability, and business function.
Show answer
Answer: D. Reduce relevant risk while preserving required confidentiality, integrity, availability, accountability, and business function.Cloud Security → Shared Responsibility → Shared Responsibility Concepts: Reduce relevant risk while preserving required confidentiality, integrity, availability, accountability, and business function.
Report a mistake

Q3. A security team is working with Shared Responsibility Concepts. Which action is most appropriate? Context: BS Cyber Security / Cloud Security / Shared Responsibility.

  1. AAvoid documenting actions so the assessment is faster.
  2. BConfirm authorization and scope, collect appropriate evidence, apply the approved method, and document the result.
  3. CTest any external system without permission.
  4. DExpand the scope whenever an interesting target appears.
Show answer
Answer: B. Confirm authorization and scope, collect appropriate evidence, apply the approved method, and document the result.Cloud Security → Shared Responsibility → Shared Responsibility Concepts: Confirm authorization and scope, collect appropriate evidence, apply the approved method, and document the result.
Report a mistake

Q4. Which approach best supports risk-aware use of Shared Responsibility Concepts? Context: BS Cyber Security / Cloud Security / Shared Responsibility.

  1. AChoose controls before identifying assets or threats.
  2. BTreat every weakness as having identical impact.
  3. CIgnore likelihood and business context entirely.
  4. DIdentify assets, threats, vulnerabilities, likelihood, and impact before selecting proportionate treatment.
Show answer
Answer: D. Identify assets, threats, vulnerabilities, likelihood, and impact before selecting proportionate treatment.Cloud Security → Shared Responsibility → Shared Responsibility Concepts: Identify assets, threats, vulnerabilities, likelihood, and impact before selecting proportionate treatment.
Report a mistake

Q5. Which principle should guide the selection of controls for Shared Responsibility Concepts? Context: BS Cyber Security / Cloud Security / Shared Responsibility.

  1. ADisable logging to improve apparent performance.
  2. BChoose controls that address the identified risk and can be implemented, monitored, and reviewed.
  3. CSelect controls solely because they are expensive.
  4. DGive every user maximum privilege to reduce support calls.
Show answer
Answer: B. Choose controls that address the identified risk and can be implemented, monitored, and reviewed.Cloud Security → Shared Responsibility → Shared Responsibility Concepts: Choose controls that address the identified risk and can be implemented, monitored, and reviewed.
Report a mistake

Q6. Which evidence best supports an assessment involving Shared Responsibility Concepts? Context: BS Cyber Security / Cloud Security / Shared Responsibility.

  1. ARely only on an unsupported opinion.
  2. BUse unrelated metrics because they are easy to collect.
  3. CAssume a tool result is correct without context or verification.
  4. DUse reproducible logs, measurements, test results, configurations, or artifacts that are directly relevant to the claim.
Show answer
Answer: D. Use reproducible logs, measurements, test results, configurations, or artifacts that are directly relevant to the claim.Cloud Security → Shared Responsibility → Shared Responsibility Concepts: Use reproducible logs, measurements, test results, configurations, or artifacts that are directly relevant to the claim.
Report a mistake

Q7. If a weakness related to Shared Responsibility Concepts is identified, what is the most appropriate next step? Context: BS Cyber Security / Cloud Security / Shared Responsibility.

  1. AMake uncontrolled changes without determining scope.
  2. BAssess severity and scope, preserve necessary evidence, apply authorized remediation, and verify the fix.
  3. CPublicly disclose sensitive details before containment.
  4. DDelete all evidence immediately.
Show answer
Answer: B. Assess severity and scope, preserve necessary evidence, apply authorized remediation, and verify the fix.Cloud Security → Shared Responsibility → Shared Responsibility Concepts: Assess severity and scope, preserve necessary evidence, apply authorized remediation, and verify the fix.
Report a mistake

Q8. How should a team validate that measures involving Shared Responsibility Concepts are effective? Context: BS Cyber Security / Cloud Security / Shared Responsibility.

  1. AAssume a control works because it was purchased.
  2. BSkip testing after configuration changes.
  3. CMeasure success only by the number of security tools installed.
  4. DTest against defined security requirements and expected threat scenarios, then review measurable results.
Show answer
Answer: D. Test against defined security requirements and expected threat scenarios, then review measurable results.Cloud Security → Shared Responsibility → Shared Responsibility Concepts: Test against defined security requirements and expected threat scenarios, then review measurable results.
Report a mistake

Q9. Which trade-off should be considered when designing or operating Shared Responsibility Concepts? Context: BS Cyber Security / Cloud Security / Shared Responsibility.

  1. ATreat cost and maintainability as irrelevant.
  2. BBalance risk reduction with usability, performance, cost, privacy, maintainability, and operational needs.
  3. CIgnore usability and operations in every security decision.
  4. DAlways maximize complexity regardless of risk.
Show answer
Answer: B. Balance risk reduction with usability, performance, cost, privacy, maintainability, and operational needs.Cloud Security → Shared Responsibility → Shared Responsibility Concepts: Balance risk reduction with usability, performance, cost, privacy, maintainability, and operational needs.
Report a mistake

Q10. Which practice best reflects responsible professional handling of Shared Responsibility Concepts? Context: BS Cyber Security / Cloud Security / Shared Responsibility.

  1. AAccess systems beyond the approved scope.
  2. BRetain sensitive data indefinitely without need.
  3. CShare discovered credentials with unrelated people.
  4. DOperate only with proper authorization, minimize unnecessary access, protect sensitive information, and document actions.
Show answer
Answer: D. Operate only with proper authorization, minimize unnecessary access, protect sensitive information, and document actions.Cloud Security → Shared Responsibility → Shared Responsibility Concepts: Operate only with proper authorization, minimize unnecessary access, protect sensitive information, and document actions.
Report a mistake

Q11. Which statement best describes Shared Responsibility Principles within Shared Responsibility? Context: BS Cyber Security / Cloud Security / Shared Responsibility.

  1. AIt is only a visual design preference with no security effect.
  2. BIt guarantees complete security once installed.
  3. CIt can be evaluated without considering threats or assets.
  4. DIt should be understood through its security objective, threat model, controls, assumptions, and operational context.
Show answer
Answer: D. It should be understood through its security objective, threat model, controls, assumptions, and operational context.Cloud Security → Shared Responsibility → Shared Responsibility Principles: It should be understood through its security objective, threat model, controls, assumptions, and operational context.
Report a mistake

Q12. What is the primary defensive goal when applying Shared Responsibility Principles? Context: BS Cyber Security / Cloud Security / Shared Responsibility.

  1. AAssume every system is secure unless an incident occurs.
  2. BReduce relevant risk while preserving required confidentiality, integrity, availability, accountability, and business function.
  3. CMaximize restrictions even if essential services stop working.
  4. DRemove all monitoring so security events remain hidden.
Show answer
Answer: B. Reduce relevant risk while preserving required confidentiality, integrity, availability, accountability, and business function.Cloud Security → Shared Responsibility → Shared Responsibility Principles: Reduce relevant risk while preserving required confidentiality, integrity, availability, accountability, and business function.
Report a mistake

Q13. A security team is working with Shared Responsibility Principles. Which action is most appropriate? Context: BS Cyber Security / Cloud Security / Shared Responsibility.

  1. ATest any external system without permission.
  2. BExpand the scope whenever an interesting target appears.
  3. CAvoid documenting actions so the assessment is faster.
  4. DConfirm authorization and scope, collect appropriate evidence, apply the approved method, and document the result.
Show answer
Answer: D. Confirm authorization and scope, collect appropriate evidence, apply the approved method, and document the result.Cloud Security → Shared Responsibility → Shared Responsibility Principles: Confirm authorization and scope, collect appropriate evidence, apply the approved method, and document the result.
Report a mistake

Q14. Which approach best supports risk-aware use of Shared Responsibility Principles? Context: BS Cyber Security / Cloud Security / Shared Responsibility.

  1. AIgnore likelihood and business context entirely.
  2. BIdentify assets, threats, vulnerabilities, likelihood, and impact before selecting proportionate treatment.
  3. CChoose controls before identifying assets or threats.
  4. DTreat every weakness as having identical impact.
Show answer
Answer: B. Identify assets, threats, vulnerabilities, likelihood, and impact before selecting proportionate treatment.Cloud Security → Shared Responsibility → Shared Responsibility Principles: Identify assets, threats, vulnerabilities, likelihood, and impact before selecting proportionate treatment.
Report a mistake

Q15. Which principle should guide the selection of controls for Shared Responsibility Principles? Context: BS Cyber Security / Cloud Security / Shared Responsibility.

  1. ASelect controls solely because they are expensive.
  2. BGive every user maximum privilege to reduce support calls.
  3. CDisable logging to improve apparent performance.
  4. DChoose controls that address the identified risk and can be implemented, monitored, and reviewed.
Show answer
Answer: D. Choose controls that address the identified risk and can be implemented, monitored, and reviewed.Cloud Security → Shared Responsibility → Shared Responsibility Principles: Choose controls that address the identified risk and can be implemented, monitored, and reviewed.
Report a mistake

Q16. Which evidence best supports an assessment involving Shared Responsibility Principles? Context: BS Cyber Security / Cloud Security / Shared Responsibility.

  1. AAssume a tool result is correct without context or verification.
  2. BUse reproducible logs, measurements, test results, configurations, or artifacts that are directly relevant to the claim.
  3. CRely only on an unsupported opinion.
  4. DUse unrelated metrics because they are easy to collect.
Show answer
Answer: B. Use reproducible logs, measurements, test results, configurations, or artifacts that are directly relevant to the claim.Cloud Security → Shared Responsibility → Shared Responsibility Principles: Use reproducible logs, measurements, test results, configurations, or artifacts that are directly relevant to the claim.
Report a mistake

Q17. If a weakness related to Shared Responsibility Principles is identified, what is the most appropriate next step? Context: BS Cyber Security / Cloud Security / Shared Responsibility.

  1. APublicly disclose sensitive details before containment.
  2. BDelete all evidence immediately.
  3. CMake uncontrolled changes without determining scope.
  4. DAssess severity and scope, preserve necessary evidence, apply authorized remediation, and verify the fix.
Show answer
Answer: D. Assess severity and scope, preserve necessary evidence, apply authorized remediation, and verify the fix.Cloud Security → Shared Responsibility → Shared Responsibility Principles: Assess severity and scope, preserve necessary evidence, apply authorized remediation, and verify the fix.
Report a mistake

Q18. How should a team validate that measures involving Shared Responsibility Principles are effective? Context: BS Cyber Security / Cloud Security / Shared Responsibility.

  1. AMeasure success only by the number of security tools installed.
  2. BTest against defined security requirements and expected threat scenarios, then review measurable results.
  3. CAssume a control works because it was purchased.
  4. DSkip testing after configuration changes.
Show answer
Answer: B. Test against defined security requirements and expected threat scenarios, then review measurable results.Cloud Security → Shared Responsibility → Shared Responsibility Principles: Test against defined security requirements and expected threat scenarios, then review measurable results.
Report a mistake

Q19. Which trade-off should be considered when designing or operating Shared Responsibility Principles? Context: BS Cyber Security / Cloud Security / Shared Responsibility.

  1. AIgnore usability and operations in every security decision.
  2. BAlways maximize complexity regardless of risk.
  3. CTreat cost and maintainability as irrelevant.
  4. DBalance risk reduction with usability, performance, cost, privacy, maintainability, and operational needs.
Show answer
Answer: D. Balance risk reduction with usability, performance, cost, privacy, maintainability, and operational needs.Cloud Security → Shared Responsibility → Shared Responsibility Principles: Balance risk reduction with usability, performance, cost, privacy, maintainability, and operational needs.
Report a mistake

Q20. Which practice best reflects responsible professional handling of Shared Responsibility Principles? Context: BS Cyber Security / Cloud Security / Shared Responsibility.

  1. AShare discovered credentials with unrelated people.
  2. BOperate only with proper authorization, minimize unnecessary access, protect sensitive information, and document actions.
  3. CAccess systems beyond the approved scope.
  4. DRetain sensitive data indefinitely without need.
Show answer
Answer: B. Operate only with proper authorization, minimize unnecessary access, protect sensitive information, and document actions.Cloud Security → Shared Responsibility → Shared Responsibility Principles: Operate only with proper authorization, minimize unnecessary access, protect sensitive information, and document actions.
Report a mistake

Q21. Which statement best describes Shared Responsibility Controls within Shared Responsibility? Context: BS Cyber Security / Cloud Security / Shared Responsibility.

  1. AIt can be evaluated without considering threats or assets.
  2. BIt should be understood through its security objective, threat model, controls, assumptions, and operational context.
  3. CIt is only a visual design preference with no security effect.
  4. DIt guarantees complete security once installed.
Show answer
Answer: B. It should be understood through its security objective, threat model, controls, assumptions, and operational context.Cloud Security → Shared Responsibility → Shared Responsibility Controls: It should be understood through its security objective, threat model, controls, assumptions, and operational context.
Report a mistake

Q22. What is the primary defensive goal when applying Shared Responsibility Controls? Context: BS Cyber Security / Cloud Security / Shared Responsibility.

  1. AMaximize restrictions even if essential services stop working.
  2. BRemove all monitoring so security events remain hidden.
  3. CAssume every system is secure unless an incident occurs.
  4. DReduce relevant risk while preserving required confidentiality, integrity, availability, accountability, and business function.
Show answer
Answer: D. Reduce relevant risk while preserving required confidentiality, integrity, availability, accountability, and business function.Cloud Security → Shared Responsibility → Shared Responsibility Controls: Reduce relevant risk while preserving required confidentiality, integrity, availability, accountability, and business function.
Report a mistake

Q23. A security team is working with Shared Responsibility Controls. Which action is most appropriate? Context: BS Cyber Security / Cloud Security / Shared Responsibility.

  1. AAvoid documenting actions so the assessment is faster.
  2. BConfirm authorization and scope, collect appropriate evidence, apply the approved method, and document the result.
  3. CTest any external system without permission.
  4. DExpand the scope whenever an interesting target appears.
Show answer
Answer: B. Confirm authorization and scope, collect appropriate evidence, apply the approved method, and document the result.Cloud Security → Shared Responsibility → Shared Responsibility Controls: Confirm authorization and scope, collect appropriate evidence, apply the approved method, and document the result.
Report a mistake

Q24. Which approach best supports risk-aware use of Shared Responsibility Controls? Context: BS Cyber Security / Cloud Security / Shared Responsibility.

  1. AChoose controls before identifying assets or threats.
  2. BTreat every weakness as having identical impact.
  3. CIgnore likelihood and business context entirely.
  4. DIdentify assets, threats, vulnerabilities, likelihood, and impact before selecting proportionate treatment.
Show answer
Answer: D. Identify assets, threats, vulnerabilities, likelihood, and impact before selecting proportionate treatment.Cloud Security → Shared Responsibility → Shared Responsibility Controls: Identify assets, threats, vulnerabilities, likelihood, and impact before selecting proportionate treatment.
Report a mistake

Q25. Which principle should guide the selection of controls for Shared Responsibility Controls? Context: BS Cyber Security / Cloud Security / Shared Responsibility.

  1. ADisable logging to improve apparent performance.
  2. BChoose controls that address the identified risk and can be implemented, monitored, and reviewed.
  3. CSelect controls solely because they are expensive.
  4. DGive every user maximum privilege to reduce support calls.
Show answer
Answer: B. Choose controls that address the identified risk and can be implemented, monitored, and reviewed.Cloud Security → Shared Responsibility → Shared Responsibility Controls: Choose controls that address the identified risk and can be implemented, monitored, and reviewed.
Report a mistake

Q26. Which evidence best supports an assessment involving Shared Responsibility Controls? Context: BS Cyber Security / Cloud Security / Shared Responsibility.

  1. ARely only on an unsupported opinion.
  2. BUse unrelated metrics because they are easy to collect.
  3. CAssume a tool result is correct without context or verification.
  4. DUse reproducible logs, measurements, test results, configurations, or artifacts that are directly relevant to the claim.
Show answer
Answer: D. Use reproducible logs, measurements, test results, configurations, or artifacts that are directly relevant to the claim.Cloud Security → Shared Responsibility → Shared Responsibility Controls: Use reproducible logs, measurements, test results, configurations, or artifacts that are directly relevant to the claim.
Report a mistake

Q27. If a weakness related to Shared Responsibility Controls is identified, what is the most appropriate next step? Context: BS Cyber Security / Cloud Security / Shared Responsibility.

  1. AMake uncontrolled changes without determining scope.
  2. BAssess severity and scope, preserve necessary evidence, apply authorized remediation, and verify the fix.
  3. CPublicly disclose sensitive details before containment.
  4. DDelete all evidence immediately.
Show answer
Answer: B. Assess severity and scope, preserve necessary evidence, apply authorized remediation, and verify the fix.Cloud Security → Shared Responsibility → Shared Responsibility Controls: Assess severity and scope, preserve necessary evidence, apply authorized remediation, and verify the fix.
Report a mistake

Q28. How should a team validate that measures involving Shared Responsibility Controls are effective? Context: BS Cyber Security / Cloud Security / Shared Responsibility.

  1. AAssume a control works because it was purchased.
  2. BSkip testing after configuration changes.
  3. CMeasure success only by the number of security tools installed.
  4. DTest against defined security requirements and expected threat scenarios, then review measurable results.
Show answer
Answer: D. Test against defined security requirements and expected threat scenarios, then review measurable results.Cloud Security → Shared Responsibility → Shared Responsibility Controls: Test against defined security requirements and expected threat scenarios, then review measurable results.
Report a mistake

Q29. Which trade-off should be considered when designing or operating Shared Responsibility Controls? Context: BS Cyber Security / Cloud Security / Shared Responsibility.

  1. ATreat cost and maintainability as irrelevant.
  2. BBalance risk reduction with usability, performance, cost, privacy, maintainability, and operational needs.
  3. CIgnore usability and operations in every security decision.
  4. DAlways maximize complexity regardless of risk.
Show answer
Answer: B. Balance risk reduction with usability, performance, cost, privacy, maintainability, and operational needs.Cloud Security → Shared Responsibility → Shared Responsibility Controls: Balance risk reduction with usability, performance, cost, privacy, maintainability, and operational needs.
Report a mistake

Q30. Which practice best reflects responsible professional handling of Shared Responsibility Controls? Context: BS Cyber Security / Cloud Security / Shared Responsibility.

  1. AAccess systems beyond the approved scope.
  2. BRetain sensitive data indefinitely without need.
  3. CShare discovered credentials with unrelated people.
  4. DOperate only with proper authorization, minimize unnecessary access, protect sensitive information, and document actions.
Show answer
Answer: D. Operate only with proper authorization, minimize unnecessary access, protect sensitive information, and document actions.Cloud Security → Shared Responsibility → Shared Responsibility Controls: Operate only with proper authorization, minimize unnecessary access, protect sensitive information, and document actions.
Report a mistake

Q31. Which statement best describes Shared Responsibility Analysis within Shared Responsibility? Context: BS Cyber Security / Cloud Security / Shared Responsibility.

  1. AIt is only a visual design preference with no security effect.
  2. BIt guarantees complete security once installed.
  3. CIt can be evaluated without considering threats or assets.
  4. DIt should be understood through its security objective, threat model, controls, assumptions, and operational context.
Show answer
Answer: D. It should be understood through its security objective, threat model, controls, assumptions, and operational context.Cloud Security → Shared Responsibility → Shared Responsibility Analysis: It should be understood through its security objective, threat model, controls, assumptions, and operational context.
Report a mistake

Q32. What is the primary defensive goal when applying Shared Responsibility Analysis? Context: BS Cyber Security / Cloud Security / Shared Responsibility.

  1. AAssume every system is secure unless an incident occurs.
  2. BReduce relevant risk while preserving required confidentiality, integrity, availability, accountability, and business function.
  3. CMaximize restrictions even if essential services stop working.
  4. DRemove all monitoring so security events remain hidden.
Show answer
Answer: B. Reduce relevant risk while preserving required confidentiality, integrity, availability, accountability, and business function.Cloud Security → Shared Responsibility → Shared Responsibility Analysis: Reduce relevant risk while preserving required confidentiality, integrity, availability, accountability, and business function.
Report a mistake

Q33. A security team is working with Shared Responsibility Analysis. Which action is most appropriate? Context: BS Cyber Security / Cloud Security / Shared Responsibility.

  1. ATest any external system without permission.
  2. BExpand the scope whenever an interesting target appears.
  3. CAvoid documenting actions so the assessment is faster.
  4. DConfirm authorization and scope, collect appropriate evidence, apply the approved method, and document the result.
Show answer
Answer: D. Confirm authorization and scope, collect appropriate evidence, apply the approved method, and document the result.Cloud Security → Shared Responsibility → Shared Responsibility Analysis: Confirm authorization and scope, collect appropriate evidence, apply the approved method, and document the result.
Report a mistake

Q34. Which approach best supports risk-aware use of Shared Responsibility Analysis? Context: BS Cyber Security / Cloud Security / Shared Responsibility.

  1. AIgnore likelihood and business context entirely.
  2. BIdentify assets, threats, vulnerabilities, likelihood, and impact before selecting proportionate treatment.
  3. CChoose controls before identifying assets or threats.
  4. DTreat every weakness as having identical impact.
Show answer
Answer: B. Identify assets, threats, vulnerabilities, likelihood, and impact before selecting proportionate treatment.Cloud Security → Shared Responsibility → Shared Responsibility Analysis: Identify assets, threats, vulnerabilities, likelihood, and impact before selecting proportionate treatment.
Report a mistake

Q35. Which principle should guide the selection of controls for Shared Responsibility Analysis? Context: BS Cyber Security / Cloud Security / Shared Responsibility.

  1. ASelect controls solely because they are expensive.
  2. BGive every user maximum privilege to reduce support calls.
  3. CDisable logging to improve apparent performance.
  4. DChoose controls that address the identified risk and can be implemented, monitored, and reviewed.
Show answer
Answer: D. Choose controls that address the identified risk and can be implemented, monitored, and reviewed.Cloud Security → Shared Responsibility → Shared Responsibility Analysis: Choose controls that address the identified risk and can be implemented, monitored, and reviewed.
Report a mistake

Q36. Which evidence best supports an assessment involving Shared Responsibility Analysis? Context: BS Cyber Security / Cloud Security / Shared Responsibility.

  1. AAssume a tool result is correct without context or verification.
  2. BUse reproducible logs, measurements, test results, configurations, or artifacts that are directly relevant to the claim.
  3. CRely only on an unsupported opinion.
  4. DUse unrelated metrics because they are easy to collect.
Show answer
Answer: B. Use reproducible logs, measurements, test results, configurations, or artifacts that are directly relevant to the claim.Cloud Security → Shared Responsibility → Shared Responsibility Analysis: Use reproducible logs, measurements, test results, configurations, or artifacts that are directly relevant to the claim.
Report a mistake

Q37. If a weakness related to Shared Responsibility Analysis is identified, what is the most appropriate next step? Context: BS Cyber Security / Cloud Security / Shared Responsibility.

  1. APublicly disclose sensitive details before containment.
  2. BDelete all evidence immediately.
  3. CMake uncontrolled changes without determining scope.
  4. DAssess severity and scope, preserve necessary evidence, apply authorized remediation, and verify the fix.
Show answer
Answer: D. Assess severity and scope, preserve necessary evidence, apply authorized remediation, and verify the fix.Cloud Security → Shared Responsibility → Shared Responsibility Analysis: Assess severity and scope, preserve necessary evidence, apply authorized remediation, and verify the fix.
Report a mistake

Q38. How should a team validate that measures involving Shared Responsibility Analysis are effective? Context: BS Cyber Security / Cloud Security / Shared Responsibility.

  1. AMeasure success only by the number of security tools installed.
  2. BTest against defined security requirements and expected threat scenarios, then review measurable results.
  3. CAssume a control works because it was purchased.
  4. DSkip testing after configuration changes.
Show answer
Answer: B. Test against defined security requirements and expected threat scenarios, then review measurable results.Cloud Security → Shared Responsibility → Shared Responsibility Analysis: Test against defined security requirements and expected threat scenarios, then review measurable results.
Report a mistake

Q39. Which trade-off should be considered when designing or operating Shared Responsibility Analysis? Context: BS Cyber Security / Cloud Security / Shared Responsibility.

  1. AIgnore usability and operations in every security decision.
  2. BAlways maximize complexity regardless of risk.
  3. CTreat cost and maintainability as irrelevant.
  4. DBalance risk reduction with usability, performance, cost, privacy, maintainability, and operational needs.
Show answer
Answer: D. Balance risk reduction with usability, performance, cost, privacy, maintainability, and operational needs.Cloud Security → Shared Responsibility → Shared Responsibility Analysis: Balance risk reduction with usability, performance, cost, privacy, maintainability, and operational needs.
Report a mistake

Q40. Which practice best reflects responsible professional handling of Shared Responsibility Analysis? Context: BS Cyber Security / Cloud Security / Shared Responsibility.

  1. AShare discovered credentials with unrelated people.
  2. BOperate only with proper authorization, minimize unnecessary access, protect sensitive information, and document actions.
  3. CAccess systems beyond the approved scope.
  4. DRetain sensitive data indefinitely without need.
Show answer
Answer: B. Operate only with proper authorization, minimize unnecessary access, protect sensitive information, and document actions.Cloud Security → Shared Responsibility → Shared Responsibility Analysis: Operate only with proper authorization, minimize unnecessary access, protect sensitive information, and document actions.
Report a mistake

Q41. Which statement best describes Shared Responsibility Applications within Shared Responsibility? Context: BS Cyber Security / Cloud Security / Shared Responsibility.

  1. AIt can be evaluated without considering threats or assets.
  2. BIt should be understood through its security objective, threat model, controls, assumptions, and operational context.
  3. CIt is only a visual design preference with no security effect.
  4. DIt guarantees complete security once installed.
Show answer
Answer: B. It should be understood through its security objective, threat model, controls, assumptions, and operational context.Cloud Security → Shared Responsibility → Shared Responsibility Applications: It should be understood through its security objective, threat model, controls, assumptions, and operational context.
Report a mistake

Q42. What is the primary defensive goal when applying Shared Responsibility Applications? Context: BS Cyber Security / Cloud Security / Shared Responsibility.

  1. AMaximize restrictions even if essential services stop working.
  2. BRemove all monitoring so security events remain hidden.
  3. CAssume every system is secure unless an incident occurs.
  4. DReduce relevant risk while preserving required confidentiality, integrity, availability, accountability, and business function.
Show answer
Answer: D. Reduce relevant risk while preserving required confidentiality, integrity, availability, accountability, and business function.Cloud Security → Shared Responsibility → Shared Responsibility Applications: Reduce relevant risk while preserving required confidentiality, integrity, availability, accountability, and business function.
Report a mistake

Q43. A security team is working with Shared Responsibility Applications. Which action is most appropriate? Context: BS Cyber Security / Cloud Security / Shared Responsibility.

  1. AAvoid documenting actions so the assessment is faster.
  2. BConfirm authorization and scope, collect appropriate evidence, apply the approved method, and document the result.
  3. CTest any external system without permission.
  4. DExpand the scope whenever an interesting target appears.
Show answer
Answer: B. Confirm authorization and scope, collect appropriate evidence, apply the approved method, and document the result.Cloud Security → Shared Responsibility → Shared Responsibility Applications: Confirm authorization and scope, collect appropriate evidence, apply the approved method, and document the result.
Report a mistake

Q44. Which approach best supports risk-aware use of Shared Responsibility Applications? Context: BS Cyber Security / Cloud Security / Shared Responsibility.

  1. AChoose controls before identifying assets or threats.
  2. BTreat every weakness as having identical impact.
  3. CIgnore likelihood and business context entirely.
  4. DIdentify assets, threats, vulnerabilities, likelihood, and impact before selecting proportionate treatment.
Show answer
Answer: D. Identify assets, threats, vulnerabilities, likelihood, and impact before selecting proportionate treatment.Cloud Security → Shared Responsibility → Shared Responsibility Applications: Identify assets, threats, vulnerabilities, likelihood, and impact before selecting proportionate treatment.
Report a mistake

Q45. Which principle should guide the selection of controls for Shared Responsibility Applications? Context: BS Cyber Security / Cloud Security / Shared Responsibility.

  1. ADisable logging to improve apparent performance.
  2. BChoose controls that address the identified risk and can be implemented, monitored, and reviewed.
  3. CSelect controls solely because they are expensive.
  4. DGive every user maximum privilege to reduce support calls.
Show answer
Answer: B. Choose controls that address the identified risk and can be implemented, monitored, and reviewed.Cloud Security → Shared Responsibility → Shared Responsibility Applications: Choose controls that address the identified risk and can be implemented, monitored, and reviewed.
Report a mistake

Q46. Which evidence best supports an assessment involving Shared Responsibility Applications? Context: BS Cyber Security / Cloud Security / Shared Responsibility.

  1. ARely only on an unsupported opinion.
  2. BUse unrelated metrics because they are easy to collect.
  3. CAssume a tool result is correct without context or verification.
  4. DUse reproducible logs, measurements, test results, configurations, or artifacts that are directly relevant to the claim.
Show answer
Answer: D. Use reproducible logs, measurements, test results, configurations, or artifacts that are directly relevant to the claim.Cloud Security → Shared Responsibility → Shared Responsibility Applications: Use reproducible logs, measurements, test results, configurations, or artifacts that are directly relevant to the claim.
Report a mistake

Q47. If a weakness related to Shared Responsibility Applications is identified, what is the most appropriate next step? Context: BS Cyber Security / Cloud Security / Shared Responsibility.

  1. AMake uncontrolled changes without determining scope.
  2. BAssess severity and scope, preserve necessary evidence, apply authorized remediation, and verify the fix.
  3. CPublicly disclose sensitive details before containment.
  4. DDelete all evidence immediately.
Show answer
Answer: B. Assess severity and scope, preserve necessary evidence, apply authorized remediation, and verify the fix.Cloud Security → Shared Responsibility → Shared Responsibility Applications: Assess severity and scope, preserve necessary evidence, apply authorized remediation, and verify the fix.
Report a mistake

Q48. How should a team validate that measures involving Shared Responsibility Applications are effective? Context: BS Cyber Security / Cloud Security / Shared Responsibility.

  1. AAssume a control works because it was purchased.
  2. BSkip testing after configuration changes.
  3. CMeasure success only by the number of security tools installed.
  4. DTest against defined security requirements and expected threat scenarios, then review measurable results.
Show answer
Answer: D. Test against defined security requirements and expected threat scenarios, then review measurable results.Cloud Security → Shared Responsibility → Shared Responsibility Applications: Test against defined security requirements and expected threat scenarios, then review measurable results.
Report a mistake

Q49. Which trade-off should be considered when designing or operating Shared Responsibility Applications? Context: BS Cyber Security / Cloud Security / Shared Responsibility.

  1. ATreat cost and maintainability as irrelevant.
  2. BBalance risk reduction with usability, performance, cost, privacy, maintainability, and operational needs.
  3. CIgnore usability and operations in every security decision.
  4. DAlways maximize complexity regardless of risk.
Show answer
Answer: B. Balance risk reduction with usability, performance, cost, privacy, maintainability, and operational needs.Cloud Security → Shared Responsibility → Shared Responsibility Applications: Balance risk reduction with usability, performance, cost, privacy, maintainability, and operational needs.
Report a mistake

Q50. Which practice best reflects responsible professional handling of Shared Responsibility Applications? Context: BS Cyber Security / Cloud Security / Shared Responsibility.

  1. AAccess systems beyond the approved scope.
  2. BRetain sensitive data indefinitely without need.
  3. CShare discovered credentials with unrelated people.
  4. DOperate only with proper authorization, minimize unnecessary access, protect sensitive information, and document actions.
Show answer
Answer: D. Operate only with proper authorization, minimize unnecessary access, protect sensitive information, and document actions.Cloud Security → Shared Responsibility → Shared Responsibility Applications: Operate only with proper authorization, minimize unnecessary access, protect sensitive information, and document actions.
Report a mistake