BS Cloud Computing · FinOps, Governance & Cloud Compliance

Unit 8: Compliance MCQs

50 solved multiple choice questions with answers and short explanations.

Q1. Which statement best describes Compliance Concepts within Compliance? Context: BS Cloud Computing / FinOps, Governance & Cloud Compliance / Compliance.

  1. AIt can be evaluated without considering failure or security boundaries.
  2. BIt should be understood through its service role, dependencies, configuration, failure modes, security boundaries, and operational context.
  3. CIt is only a billing label with no technical effect.
  4. DIt guarantees unlimited resources without dependencies.
Show answer
Answer: B. It should be understood through its service role, dependencies, configuration, failure modes, security boundaries, and operational context.FinOps, Governance & Cloud Compliance → Compliance → Compliance Concepts: It should be understood through its service role, dependencies, configuration, failure modes, security boundaries, and operational context.
Report a mistake

Q2. What is the primary purpose of Compliance Concepts in a cloud environment? Context: BS Cloud Computing / FinOps, Governance & Cloud Compliance / Compliance.

  1. AIts purpose is always to maximize the number of cloud services.
  2. BIt removes the need for capacity, security, and cost planning.
  3. CIt guarantees zero downtime regardless of architecture.
  4. DIt supports an elastic, manageable cloud service objective while meeting availability, security, performance, and cost requirements.
Show answer
Answer: D. It supports an elastic, manageable cloud service objective while meeting availability, security, performance, and cost requirements.FinOps, Governance & Cloud Compliance → Compliance → Compliance Concepts: It supports an elastic, manageable cloud service objective while meeting availability, security, performance, and cost requirements.
Report a mistake

Q3. A cloud team is working with Compliance Concepts. Which approach is most appropriate? Context: BS Cloud Computing / FinOps, Governance & Cloud Compliance / Compliance.

  1. ASkip validation because cloud services are automatically reliable.
  2. BDefine requirements and dependencies, use controlled automation, apply least privilege, and verify the deployed service with evidence.
  3. CMake manual production changes without recording them.
  4. DGive every operator administrator access for convenience.
Show answer
Answer: B. Define requirements and dependencies, use controlled automation, apply least privilege, and verify the deployed service with evidence.FinOps, Governance & Cloud Compliance → Compliance → Compliance Concepts: Define requirements and dependencies, use controlled automation, apply least privilege, and verify the deployed service with evidence.
Report a mistake

Q4. Which principle best supports sound design involving Compliance Concepts? Context: BS Cloud Computing / FinOps, Governance & Cloud Compliance / Compliance.

  1. APlace every component in one failure domain to simplify design.
  2. BAvoid monitoring to reduce cost.
  3. CCouple all services tightly so failures propagate consistently.
  4. DDesign for explicit requirements, loose coupling where appropriate, automation, observability, resilience, and predictable failure handling.
Show answer
Answer: D. Design for explicit requirements, loose coupling where appropriate, automation, observability, resilience, and predictable failure handling.FinOps, Governance & Cloud Compliance → Compliance → Compliance Concepts: Design for explicit requirements, loose coupling where appropriate, automation, observability, resilience, and predictable failure handling.
Report a mistake

Q5. Which security consideration is most important when applying Compliance Concepts? Context: BS Cloud Computing / FinOps, Governance & Cloud Compliance / Compliance.

  1. AStore secrets directly in public source repositories.
  2. BApply least privilege, strong identity controls, encryption where appropriate, secure configuration, logging, and shared-responsibility awareness.
  3. CUse shared administrator credentials for all workloads.
  4. DDisable audit logging to reduce storage use.
Show answer
Answer: B. Apply least privilege, strong identity controls, encryption where appropriate, secure configuration, logging, and shared-responsibility awareness.FinOps, Governance & Cloud Compliance → Compliance → Compliance Concepts: Apply least privilege, strong identity controls, encryption where appropriate, secure configuration, logging, and shared-responsibility awareness.
Report a mistake

Q6. Which practice best improves reliability for Compliance Concepts? Context: BS Cloud Computing / FinOps, Governance & Cloud Compliance / Compliance.

  1. ADepend on a single instance and never test recovery.
  2. BTreat backups as unnecessary for managed services.
  3. CIgnore capacity limits because cloud resources are infinite.
  4. DUse redundancy, health checks, automated recovery, capacity planning, backups where required, and tested failure procedures.
Show answer
Answer: D. Use redundancy, health checks, automated recovery, capacity planning, backups where required, and tested failure procedures.FinOps, Governance & Cloud Compliance → Compliance → Compliance Concepts: Use redundancy, health checks, automated recovery, capacity planning, backups where required, and tested failure procedures.
Report a mistake

Q7. Which operational approach is most appropriate for Compliance Concepts? Context: BS Cloud Computing / FinOps, Governance & Cloud Compliance / Compliance.

  1. AUse undocumented configurations unique to each deployment.
  2. BAutomate repeatable changes, monitor service health, retain logs and traces, manage configuration, and use controlled deployment procedures.
  3. CChange production manually and avoid version control.
  4. DSuppress alerts instead of fixing noisy monitoring.
Show answer
Answer: B. Automate repeatable changes, monitor service health, retain logs and traces, manage configuration, and use controlled deployment procedures.FinOps, Governance & Cloud Compliance → Compliance → Compliance Concepts: Automate repeatable changes, monitor service health, retain logs and traces, manage configuration, and use controlled deployment procedures.
Report a mistake

Q8. Which evidence best demonstrates that Compliance Concepts is working as intended? Context: BS Cloud Computing / FinOps, Governance & Cloud Compliance / Compliance.

  1. AAssume the service is healthy because deployment succeeded.
  2. BUse an unrelated metric because it is easy to collect.
  3. CRely only on a visual dashboard without defined thresholds.
  4. DUse metrics, logs, traces, configuration state, tests, and service-level measurements tied directly to requirements.
Show answer
Answer: D. Use metrics, logs, traces, configuration state, tests, and service-level measurements tied directly to requirements.FinOps, Governance & Cloud Compliance → Compliance → Compliance Concepts: Use metrics, logs, traces, configuration state, tests, and service-level measurements tied directly to requirements.
Report a mistake

Q9. Which trade-off should be assessed when selecting an approach to Compliance Concepts? Context: BS Cloud Computing / FinOps, Governance & Cloud Compliance / Compliance.

  1. AAlways maximize redundancy regardless of cost or requirement.
  2. BBalance availability, performance, security, cost, scalability, portability, and operational complexity.
  3. COnly lowest price matters in every cloud decision.
  4. DPortability and operational complexity never matter.
Show answer
Answer: B. Balance availability, performance, security, cost, scalability, portability, and operational complexity.FinOps, Governance & Cloud Compliance → Compliance → Compliance Concepts: Balance availability, performance, security, cost, scalability, portability, and operational complexity.
Report a mistake

Q10. Which practice best supports responsible governance of Compliance Concepts? Context: BS Cloud Computing / FinOps, Governance & Cloud Compliance / Compliance.

  1. AAllow untagged resources with no owner.
  2. BIgnore cost attribution because cloud billing is automatic.
  3. CPermit unrestricted changes without audit trails.
  4. DUse ownership, policies, tagging, access controls, cost accountability, compliance checks, and auditable change management.
Show answer
Answer: D. Use ownership, policies, tagging, access controls, cost accountability, compliance checks, and auditable change management.FinOps, Governance & Cloud Compliance → Compliance → Compliance Concepts: Use ownership, policies, tagging, access controls, cost accountability, compliance checks, and auditable change management.
Report a mistake

Q11. Which statement best describes Compliance Components within Compliance? Context: BS Cloud Computing / FinOps, Governance & Cloud Compliance / Compliance.

  1. AIt is only a billing label with no technical effect.
  2. BIt guarantees unlimited resources without dependencies.
  3. CIt can be evaluated without considering failure or security boundaries.
  4. DIt should be understood through its service role, dependencies, configuration, failure modes, security boundaries, and operational context.
Show answer
Answer: D. It should be understood through its service role, dependencies, configuration, failure modes, security boundaries, and operational context.FinOps, Governance & Cloud Compliance → Compliance → Compliance Components: It should be understood through its service role, dependencies, configuration, failure modes, security boundaries, and operational context.
Report a mistake

Q12. What is the primary purpose of Compliance Components in a cloud environment? Context: BS Cloud Computing / FinOps, Governance & Cloud Compliance / Compliance.

  1. AIt guarantees zero downtime regardless of architecture.
  2. BIt supports an elastic, manageable cloud service objective while meeting availability, security, performance, and cost requirements.
  3. CIts purpose is always to maximize the number of cloud services.
  4. DIt removes the need for capacity, security, and cost planning.
Show answer
Answer: B. It supports an elastic, manageable cloud service objective while meeting availability, security, performance, and cost requirements.FinOps, Governance & Cloud Compliance → Compliance → Compliance Components: It supports an elastic, manageable cloud service objective while meeting availability, security, performance, and cost requirements.
Report a mistake

Q13. A cloud team is working with Compliance Components. Which approach is most appropriate? Context: BS Cloud Computing / FinOps, Governance & Cloud Compliance / Compliance.

  1. AMake manual production changes without recording them.
  2. BGive every operator administrator access for convenience.
  3. CSkip validation because cloud services are automatically reliable.
  4. DDefine requirements and dependencies, use controlled automation, apply least privilege, and verify the deployed service with evidence.
Show answer
Answer: D. Define requirements and dependencies, use controlled automation, apply least privilege, and verify the deployed service with evidence.FinOps, Governance & Cloud Compliance → Compliance → Compliance Components: Define requirements and dependencies, use controlled automation, apply least privilege, and verify the deployed service with evidence.
Report a mistake

Q14. Which principle best supports sound design involving Compliance Components? Context: BS Cloud Computing / FinOps, Governance & Cloud Compliance / Compliance.

  1. ACouple all services tightly so failures propagate consistently.
  2. BDesign for explicit requirements, loose coupling where appropriate, automation, observability, resilience, and predictable failure handling.
  3. CPlace every component in one failure domain to simplify design.
  4. DAvoid monitoring to reduce cost.
Show answer
Answer: B. Design for explicit requirements, loose coupling where appropriate, automation, observability, resilience, and predictable failure handling.FinOps, Governance & Cloud Compliance → Compliance → Compliance Components: Design for explicit requirements, loose coupling where appropriate, automation, observability, resilience, and predictable failure handling.
Report a mistake

Q15. Which security consideration is most important when applying Compliance Components? Context: BS Cloud Computing / FinOps, Governance & Cloud Compliance / Compliance.

  1. AUse shared administrator credentials for all workloads.
  2. BDisable audit logging to reduce storage use.
  3. CStore secrets directly in public source repositories.
  4. DApply least privilege, strong identity controls, encryption where appropriate, secure configuration, logging, and shared-responsibility awareness.
Show answer
Answer: D. Apply least privilege, strong identity controls, encryption where appropriate, secure configuration, logging, and shared-responsibility awareness.FinOps, Governance & Cloud Compliance → Compliance → Compliance Components: Apply least privilege, strong identity controls, encryption where appropriate, secure configuration, logging, and shared-responsibility awareness.
Report a mistake

Q16. Which practice best improves reliability for Compliance Components? Context: BS Cloud Computing / FinOps, Governance & Cloud Compliance / Compliance.

  1. AIgnore capacity limits because cloud resources are infinite.
  2. BUse redundancy, health checks, automated recovery, capacity planning, backups where required, and tested failure procedures.
  3. CDepend on a single instance and never test recovery.
  4. DTreat backups as unnecessary for managed services.
Show answer
Answer: B. Use redundancy, health checks, automated recovery, capacity planning, backups where required, and tested failure procedures.FinOps, Governance & Cloud Compliance → Compliance → Compliance Components: Use redundancy, health checks, automated recovery, capacity planning, backups where required, and tested failure procedures.
Report a mistake

Q17. Which operational approach is most appropriate for Compliance Components? Context: BS Cloud Computing / FinOps, Governance & Cloud Compliance / Compliance.

  1. AChange production manually and avoid version control.
  2. BSuppress alerts instead of fixing noisy monitoring.
  3. CUse undocumented configurations unique to each deployment.
  4. DAutomate repeatable changes, monitor service health, retain logs and traces, manage configuration, and use controlled deployment procedures.
Show answer
Answer: D. Automate repeatable changes, monitor service health, retain logs and traces, manage configuration, and use controlled deployment procedures.FinOps, Governance & Cloud Compliance → Compliance → Compliance Components: Automate repeatable changes, monitor service health, retain logs and traces, manage configuration, and use controlled deployment procedures.
Report a mistake

Q18. Which evidence best demonstrates that Compliance Components is working as intended? Context: BS Cloud Computing / FinOps, Governance & Cloud Compliance / Compliance.

  1. ARely only on a visual dashboard without defined thresholds.
  2. BUse metrics, logs, traces, configuration state, tests, and service-level measurements tied directly to requirements.
  3. CAssume the service is healthy because deployment succeeded.
  4. DUse an unrelated metric because it is easy to collect.
Show answer
Answer: B. Use metrics, logs, traces, configuration state, tests, and service-level measurements tied directly to requirements.FinOps, Governance & Cloud Compliance → Compliance → Compliance Components: Use metrics, logs, traces, configuration state, tests, and service-level measurements tied directly to requirements.
Report a mistake

Q19. Which trade-off should be assessed when selecting an approach to Compliance Components? Context: BS Cloud Computing / FinOps, Governance & Cloud Compliance / Compliance.

  1. AOnly lowest price matters in every cloud decision.
  2. BPortability and operational complexity never matter.
  3. CAlways maximize redundancy regardless of cost or requirement.
  4. DBalance availability, performance, security, cost, scalability, portability, and operational complexity.
Show answer
Answer: D. Balance availability, performance, security, cost, scalability, portability, and operational complexity.FinOps, Governance & Cloud Compliance → Compliance → Compliance Components: Balance availability, performance, security, cost, scalability, portability, and operational complexity.
Report a mistake

Q20. Which practice best supports responsible governance of Compliance Components? Context: BS Cloud Computing / FinOps, Governance & Cloud Compliance / Compliance.

  1. APermit unrestricted changes without audit trails.
  2. BUse ownership, policies, tagging, access controls, cost accountability, compliance checks, and auditable change management.
  3. CAllow untagged resources with no owner.
  4. DIgnore cost attribution because cloud billing is automatic.
Show answer
Answer: B. Use ownership, policies, tagging, access controls, cost accountability, compliance checks, and auditable change management.FinOps, Governance & Cloud Compliance → Compliance → Compliance Components: Use ownership, policies, tagging, access controls, cost accountability, compliance checks, and auditable change management.
Report a mistake

Q21. Which statement best describes Compliance Configuration within Compliance? Context: BS Cloud Computing / FinOps, Governance & Cloud Compliance / Compliance.

  1. AIt can be evaluated without considering failure or security boundaries.
  2. BIt should be understood through its service role, dependencies, configuration, failure modes, security boundaries, and operational context.
  3. CIt is only a billing label with no technical effect.
  4. DIt guarantees unlimited resources without dependencies.
Show answer
Answer: B. It should be understood through its service role, dependencies, configuration, failure modes, security boundaries, and operational context.FinOps, Governance & Cloud Compliance → Compliance → Compliance Configuration: It should be understood through its service role, dependencies, configuration, failure modes, security boundaries, and operational context.
Report a mistake

Q22. What is the primary purpose of Compliance Configuration in a cloud environment? Context: BS Cloud Computing / FinOps, Governance & Cloud Compliance / Compliance.

  1. AIts purpose is always to maximize the number of cloud services.
  2. BIt removes the need for capacity, security, and cost planning.
  3. CIt guarantees zero downtime regardless of architecture.
  4. DIt supports an elastic, manageable cloud service objective while meeting availability, security, performance, and cost requirements.
Show answer
Answer: D. It supports an elastic, manageable cloud service objective while meeting availability, security, performance, and cost requirements.FinOps, Governance & Cloud Compliance → Compliance → Compliance Configuration: It supports an elastic, manageable cloud service objective while meeting availability, security, performance, and cost requirements.
Report a mistake

Q23. A cloud team is working with Compliance Configuration. Which approach is most appropriate? Context: BS Cloud Computing / FinOps, Governance & Cloud Compliance / Compliance.

  1. ASkip validation because cloud services are automatically reliable.
  2. BDefine requirements and dependencies, use controlled automation, apply least privilege, and verify the deployed service with evidence.
  3. CMake manual production changes without recording them.
  4. DGive every operator administrator access for convenience.
Show answer
Answer: B. Define requirements and dependencies, use controlled automation, apply least privilege, and verify the deployed service with evidence.FinOps, Governance & Cloud Compliance → Compliance → Compliance Configuration: Define requirements and dependencies, use controlled automation, apply least privilege, and verify the deployed service with evidence.
Report a mistake

Q24. Which principle best supports sound design involving Compliance Configuration? Context: BS Cloud Computing / FinOps, Governance & Cloud Compliance / Compliance.

  1. APlace every component in one failure domain to simplify design.
  2. BAvoid monitoring to reduce cost.
  3. CCouple all services tightly so failures propagate consistently.
  4. DDesign for explicit requirements, loose coupling where appropriate, automation, observability, resilience, and predictable failure handling.
Show answer
Answer: D. Design for explicit requirements, loose coupling where appropriate, automation, observability, resilience, and predictable failure handling.FinOps, Governance & Cloud Compliance → Compliance → Compliance Configuration: Design for explicit requirements, loose coupling where appropriate, automation, observability, resilience, and predictable failure handling.
Report a mistake

Q25. Which security consideration is most important when applying Compliance Configuration? Context: BS Cloud Computing / FinOps, Governance & Cloud Compliance / Compliance.

  1. AStore secrets directly in public source repositories.
  2. BApply least privilege, strong identity controls, encryption where appropriate, secure configuration, logging, and shared-responsibility awareness.
  3. CUse shared administrator credentials for all workloads.
  4. DDisable audit logging to reduce storage use.
Show answer
Answer: B. Apply least privilege, strong identity controls, encryption where appropriate, secure configuration, logging, and shared-responsibility awareness.FinOps, Governance & Cloud Compliance → Compliance → Compliance Configuration: Apply least privilege, strong identity controls, encryption where appropriate, secure configuration, logging, and shared-responsibility awareness.
Report a mistake

Q26. Which practice best improves reliability for Compliance Configuration? Context: BS Cloud Computing / FinOps, Governance & Cloud Compliance / Compliance.

  1. ADepend on a single instance and never test recovery.
  2. BTreat backups as unnecessary for managed services.
  3. CIgnore capacity limits because cloud resources are infinite.
  4. DUse redundancy, health checks, automated recovery, capacity planning, backups where required, and tested failure procedures.
Show answer
Answer: D. Use redundancy, health checks, automated recovery, capacity planning, backups where required, and tested failure procedures.FinOps, Governance & Cloud Compliance → Compliance → Compliance Configuration: Use redundancy, health checks, automated recovery, capacity planning, backups where required, and tested failure procedures.
Report a mistake

Q27. Which operational approach is most appropriate for Compliance Configuration? Context: BS Cloud Computing / FinOps, Governance & Cloud Compliance / Compliance.

  1. AUse undocumented configurations unique to each deployment.
  2. BAutomate repeatable changes, monitor service health, retain logs and traces, manage configuration, and use controlled deployment procedures.
  3. CChange production manually and avoid version control.
  4. DSuppress alerts instead of fixing noisy monitoring.
Show answer
Answer: B. Automate repeatable changes, monitor service health, retain logs and traces, manage configuration, and use controlled deployment procedures.FinOps, Governance & Cloud Compliance → Compliance → Compliance Configuration: Automate repeatable changes, monitor service health, retain logs and traces, manage configuration, and use controlled deployment procedures.
Report a mistake

Q28. Which evidence best demonstrates that Compliance Configuration is working as intended? Context: BS Cloud Computing / FinOps, Governance & Cloud Compliance / Compliance.

  1. AAssume the service is healthy because deployment succeeded.
  2. BUse an unrelated metric because it is easy to collect.
  3. CRely only on a visual dashboard without defined thresholds.
  4. DUse metrics, logs, traces, configuration state, tests, and service-level measurements tied directly to requirements.
Show answer
Answer: D. Use metrics, logs, traces, configuration state, tests, and service-level measurements tied directly to requirements.FinOps, Governance & Cloud Compliance → Compliance → Compliance Configuration: Use metrics, logs, traces, configuration state, tests, and service-level measurements tied directly to requirements.
Report a mistake

Q29. Which trade-off should be assessed when selecting an approach to Compliance Configuration? Context: BS Cloud Computing / FinOps, Governance & Cloud Compliance / Compliance.

  1. AAlways maximize redundancy regardless of cost or requirement.
  2. BBalance availability, performance, security, cost, scalability, portability, and operational complexity.
  3. COnly lowest price matters in every cloud decision.
  4. DPortability and operational complexity never matter.
Show answer
Answer: B. Balance availability, performance, security, cost, scalability, portability, and operational complexity.FinOps, Governance & Cloud Compliance → Compliance → Compliance Configuration: Balance availability, performance, security, cost, scalability, portability, and operational complexity.
Report a mistake

Q30. Which practice best supports responsible governance of Compliance Configuration? Context: BS Cloud Computing / FinOps, Governance & Cloud Compliance / Compliance.

  1. AAllow untagged resources with no owner.
  2. BIgnore cost attribution because cloud billing is automatic.
  3. CPermit unrestricted changes without audit trails.
  4. DUse ownership, policies, tagging, access controls, cost accountability, compliance checks, and auditable change management.
Show answer
Answer: D. Use ownership, policies, tagging, access controls, cost accountability, compliance checks, and auditable change management.FinOps, Governance & Cloud Compliance → Compliance → Compliance Configuration: Use ownership, policies, tagging, access controls, cost accountability, compliance checks, and auditable change management.
Report a mistake

Q31. Which statement best describes Compliance Evaluation within Compliance? Context: BS Cloud Computing / FinOps, Governance & Cloud Compliance / Compliance.

  1. AIt is only a billing label with no technical effect.
  2. BIt guarantees unlimited resources without dependencies.
  3. CIt can be evaluated without considering failure or security boundaries.
  4. DIt should be understood through its service role, dependencies, configuration, failure modes, security boundaries, and operational context.
Show answer
Answer: D. It should be understood through its service role, dependencies, configuration, failure modes, security boundaries, and operational context.FinOps, Governance & Cloud Compliance → Compliance → Compliance Evaluation: It should be understood through its service role, dependencies, configuration, failure modes, security boundaries, and operational context.
Report a mistake

Q32. What is the primary purpose of Compliance Evaluation in a cloud environment? Context: BS Cloud Computing / FinOps, Governance & Cloud Compliance / Compliance.

  1. AIt guarantees zero downtime regardless of architecture.
  2. BIt supports an elastic, manageable cloud service objective while meeting availability, security, performance, and cost requirements.
  3. CIts purpose is always to maximize the number of cloud services.
  4. DIt removes the need for capacity, security, and cost planning.
Show answer
Answer: B. It supports an elastic, manageable cloud service objective while meeting availability, security, performance, and cost requirements.FinOps, Governance & Cloud Compliance → Compliance → Compliance Evaluation: It supports an elastic, manageable cloud service objective while meeting availability, security, performance, and cost requirements.
Report a mistake

Q33. A cloud team is working with Compliance Evaluation. Which approach is most appropriate? Context: BS Cloud Computing / FinOps, Governance & Cloud Compliance / Compliance.

  1. AMake manual production changes without recording them.
  2. BGive every operator administrator access for convenience.
  3. CSkip validation because cloud services are automatically reliable.
  4. DDefine requirements and dependencies, use controlled automation, apply least privilege, and verify the deployed service with evidence.
Show answer
Answer: D. Define requirements and dependencies, use controlled automation, apply least privilege, and verify the deployed service with evidence.FinOps, Governance & Cloud Compliance → Compliance → Compliance Evaluation: Define requirements and dependencies, use controlled automation, apply least privilege, and verify the deployed service with evidence.
Report a mistake

Q34. Which principle best supports sound design involving Compliance Evaluation? Context: BS Cloud Computing / FinOps, Governance & Cloud Compliance / Compliance.

  1. ACouple all services tightly so failures propagate consistently.
  2. BDesign for explicit requirements, loose coupling where appropriate, automation, observability, resilience, and predictable failure handling.
  3. CPlace every component in one failure domain to simplify design.
  4. DAvoid monitoring to reduce cost.
Show answer
Answer: B. Design for explicit requirements, loose coupling where appropriate, automation, observability, resilience, and predictable failure handling.FinOps, Governance & Cloud Compliance → Compliance → Compliance Evaluation: Design for explicit requirements, loose coupling where appropriate, automation, observability, resilience, and predictable failure handling.
Report a mistake

Q35. Which security consideration is most important when applying Compliance Evaluation? Context: BS Cloud Computing / FinOps, Governance & Cloud Compliance / Compliance.

  1. AUse shared administrator credentials for all workloads.
  2. BDisable audit logging to reduce storage use.
  3. CStore secrets directly in public source repositories.
  4. DApply least privilege, strong identity controls, encryption where appropriate, secure configuration, logging, and shared-responsibility awareness.
Show answer
Answer: D. Apply least privilege, strong identity controls, encryption where appropriate, secure configuration, logging, and shared-responsibility awareness.FinOps, Governance & Cloud Compliance → Compliance → Compliance Evaluation: Apply least privilege, strong identity controls, encryption where appropriate, secure configuration, logging, and shared-responsibility awareness.
Report a mistake

Q36. Which practice best improves reliability for Compliance Evaluation? Context: BS Cloud Computing / FinOps, Governance & Cloud Compliance / Compliance.

  1. AIgnore capacity limits because cloud resources are infinite.
  2. BUse redundancy, health checks, automated recovery, capacity planning, backups where required, and tested failure procedures.
  3. CDepend on a single instance and never test recovery.
  4. DTreat backups as unnecessary for managed services.
Show answer
Answer: B. Use redundancy, health checks, automated recovery, capacity planning, backups where required, and tested failure procedures.FinOps, Governance & Cloud Compliance → Compliance → Compliance Evaluation: Use redundancy, health checks, automated recovery, capacity planning, backups where required, and tested failure procedures.
Report a mistake

Q37. Which operational approach is most appropriate for Compliance Evaluation? Context: BS Cloud Computing / FinOps, Governance & Cloud Compliance / Compliance.

  1. AChange production manually and avoid version control.
  2. BSuppress alerts instead of fixing noisy monitoring.
  3. CUse undocumented configurations unique to each deployment.
  4. DAutomate repeatable changes, monitor service health, retain logs and traces, manage configuration, and use controlled deployment procedures.
Show answer
Answer: D. Automate repeatable changes, monitor service health, retain logs and traces, manage configuration, and use controlled deployment procedures.FinOps, Governance & Cloud Compliance → Compliance → Compliance Evaluation: Automate repeatable changes, monitor service health, retain logs and traces, manage configuration, and use controlled deployment procedures.
Report a mistake

Q38. Which evidence best demonstrates that Compliance Evaluation is working as intended? Context: BS Cloud Computing / FinOps, Governance & Cloud Compliance / Compliance.

  1. ARely only on a visual dashboard without defined thresholds.
  2. BUse metrics, logs, traces, configuration state, tests, and service-level measurements tied directly to requirements.
  3. CAssume the service is healthy because deployment succeeded.
  4. DUse an unrelated metric because it is easy to collect.
Show answer
Answer: B. Use metrics, logs, traces, configuration state, tests, and service-level measurements tied directly to requirements.FinOps, Governance & Cloud Compliance → Compliance → Compliance Evaluation: Use metrics, logs, traces, configuration state, tests, and service-level measurements tied directly to requirements.
Report a mistake

Q39. Which trade-off should be assessed when selecting an approach to Compliance Evaluation? Context: BS Cloud Computing / FinOps, Governance & Cloud Compliance / Compliance.

  1. AOnly lowest price matters in every cloud decision.
  2. BPortability and operational complexity never matter.
  3. CAlways maximize redundancy regardless of cost or requirement.
  4. DBalance availability, performance, security, cost, scalability, portability, and operational complexity.
Show answer
Answer: D. Balance availability, performance, security, cost, scalability, portability, and operational complexity.FinOps, Governance & Cloud Compliance → Compliance → Compliance Evaluation: Balance availability, performance, security, cost, scalability, portability, and operational complexity.
Report a mistake

Q40. Which practice best supports responsible governance of Compliance Evaluation? Context: BS Cloud Computing / FinOps, Governance & Cloud Compliance / Compliance.

  1. APermit unrestricted changes without audit trails.
  2. BUse ownership, policies, tagging, access controls, cost accountability, compliance checks, and auditable change management.
  3. CAllow untagged resources with no owner.
  4. DIgnore cost attribution because cloud billing is automatic.
Show answer
Answer: B. Use ownership, policies, tagging, access controls, cost accountability, compliance checks, and auditable change management.FinOps, Governance & Cloud Compliance → Compliance → Compliance Evaluation: Use ownership, policies, tagging, access controls, cost accountability, compliance checks, and auditable change management.
Report a mistake

Q41. Which statement best describes Compliance Applications within Compliance? Context: BS Cloud Computing / FinOps, Governance & Cloud Compliance / Compliance.

  1. AIt can be evaluated without considering failure or security boundaries.
  2. BIt should be understood through its service role, dependencies, configuration, failure modes, security boundaries, and operational context.
  3. CIt is only a billing label with no technical effect.
  4. DIt guarantees unlimited resources without dependencies.
Show answer
Answer: B. It should be understood through its service role, dependencies, configuration, failure modes, security boundaries, and operational context.FinOps, Governance & Cloud Compliance → Compliance → Compliance Applications: It should be understood through its service role, dependencies, configuration, failure modes, security boundaries, and operational context.
Report a mistake

Q42. What is the primary purpose of Compliance Applications in a cloud environment? Context: BS Cloud Computing / FinOps, Governance & Cloud Compliance / Compliance.

  1. AIts purpose is always to maximize the number of cloud services.
  2. BIt removes the need for capacity, security, and cost planning.
  3. CIt guarantees zero downtime regardless of architecture.
  4. DIt supports an elastic, manageable cloud service objective while meeting availability, security, performance, and cost requirements.
Show answer
Answer: D. It supports an elastic, manageable cloud service objective while meeting availability, security, performance, and cost requirements.FinOps, Governance & Cloud Compliance → Compliance → Compliance Applications: It supports an elastic, manageable cloud service objective while meeting availability, security, performance, and cost requirements.
Report a mistake

Q43. A cloud team is working with Compliance Applications. Which approach is most appropriate? Context: BS Cloud Computing / FinOps, Governance & Cloud Compliance / Compliance.

  1. ASkip validation because cloud services are automatically reliable.
  2. BDefine requirements and dependencies, use controlled automation, apply least privilege, and verify the deployed service with evidence.
  3. CMake manual production changes without recording them.
  4. DGive every operator administrator access for convenience.
Show answer
Answer: B. Define requirements and dependencies, use controlled automation, apply least privilege, and verify the deployed service with evidence.FinOps, Governance & Cloud Compliance → Compliance → Compliance Applications: Define requirements and dependencies, use controlled automation, apply least privilege, and verify the deployed service with evidence.
Report a mistake

Q44. Which principle best supports sound design involving Compliance Applications? Context: BS Cloud Computing / FinOps, Governance & Cloud Compliance / Compliance.

  1. APlace every component in one failure domain to simplify design.
  2. BAvoid monitoring to reduce cost.
  3. CCouple all services tightly so failures propagate consistently.
  4. DDesign for explicit requirements, loose coupling where appropriate, automation, observability, resilience, and predictable failure handling.
Show answer
Answer: D. Design for explicit requirements, loose coupling where appropriate, automation, observability, resilience, and predictable failure handling.FinOps, Governance & Cloud Compliance → Compliance → Compliance Applications: Design for explicit requirements, loose coupling where appropriate, automation, observability, resilience, and predictable failure handling.
Report a mistake

Q45. Which security consideration is most important when applying Compliance Applications? Context: BS Cloud Computing / FinOps, Governance & Cloud Compliance / Compliance.

  1. AStore secrets directly in public source repositories.
  2. BApply least privilege, strong identity controls, encryption where appropriate, secure configuration, logging, and shared-responsibility awareness.
  3. CUse shared administrator credentials for all workloads.
  4. DDisable audit logging to reduce storage use.
Show answer
Answer: B. Apply least privilege, strong identity controls, encryption where appropriate, secure configuration, logging, and shared-responsibility awareness.FinOps, Governance & Cloud Compliance → Compliance → Compliance Applications: Apply least privilege, strong identity controls, encryption where appropriate, secure configuration, logging, and shared-responsibility awareness.
Report a mistake

Q46. Which practice best improves reliability for Compliance Applications? Context: BS Cloud Computing / FinOps, Governance & Cloud Compliance / Compliance.

  1. ADepend on a single instance and never test recovery.
  2. BTreat backups as unnecessary for managed services.
  3. CIgnore capacity limits because cloud resources are infinite.
  4. DUse redundancy, health checks, automated recovery, capacity planning, backups where required, and tested failure procedures.
Show answer
Answer: D. Use redundancy, health checks, automated recovery, capacity planning, backups where required, and tested failure procedures.FinOps, Governance & Cloud Compliance → Compliance → Compliance Applications: Use redundancy, health checks, automated recovery, capacity planning, backups where required, and tested failure procedures.
Report a mistake

Q47. Which operational approach is most appropriate for Compliance Applications? Context: BS Cloud Computing / FinOps, Governance & Cloud Compliance / Compliance.

  1. AUse undocumented configurations unique to each deployment.
  2. BAutomate repeatable changes, monitor service health, retain logs and traces, manage configuration, and use controlled deployment procedures.
  3. CChange production manually and avoid version control.
  4. DSuppress alerts instead of fixing noisy monitoring.
Show answer
Answer: B. Automate repeatable changes, monitor service health, retain logs and traces, manage configuration, and use controlled deployment procedures.FinOps, Governance & Cloud Compliance → Compliance → Compliance Applications: Automate repeatable changes, monitor service health, retain logs and traces, manage configuration, and use controlled deployment procedures.
Report a mistake

Q48. Which evidence best demonstrates that Compliance Applications is working as intended? Context: BS Cloud Computing / FinOps, Governance & Cloud Compliance / Compliance.

  1. AAssume the service is healthy because deployment succeeded.
  2. BUse an unrelated metric because it is easy to collect.
  3. CRely only on a visual dashboard without defined thresholds.
  4. DUse metrics, logs, traces, configuration state, tests, and service-level measurements tied directly to requirements.
Show answer
Answer: D. Use metrics, logs, traces, configuration state, tests, and service-level measurements tied directly to requirements.FinOps, Governance & Cloud Compliance → Compliance → Compliance Applications: Use metrics, logs, traces, configuration state, tests, and service-level measurements tied directly to requirements.
Report a mistake

Q49. Which trade-off should be assessed when selecting an approach to Compliance Applications? Context: BS Cloud Computing / FinOps, Governance & Cloud Compliance / Compliance.

  1. AAlways maximize redundancy regardless of cost or requirement.
  2. BBalance availability, performance, security, cost, scalability, portability, and operational complexity.
  3. COnly lowest price matters in every cloud decision.
  4. DPortability and operational complexity never matter.
Show answer
Answer: B. Balance availability, performance, security, cost, scalability, portability, and operational complexity.FinOps, Governance & Cloud Compliance → Compliance → Compliance Applications: Balance availability, performance, security, cost, scalability, portability, and operational complexity.
Report a mistake

Q50. Which practice best supports responsible governance of Compliance Applications? Context: BS Cloud Computing / FinOps, Governance & Cloud Compliance / Compliance.

  1. AAllow untagged resources with no owner.
  2. BIgnore cost attribution because cloud billing is automatic.
  3. CPermit unrestricted changes without audit trails.
  4. DUse ownership, policies, tagging, access controls, cost accountability, compliance checks, and auditable change management.
Show answer
Answer: D. Use ownership, policies, tagging, access controls, cost accountability, compliance checks, and auditable change management.FinOps, Governance & Cloud Compliance → Compliance → Compliance Applications: Use ownership, policies, tagging, access controls, cost accountability, compliance checks, and auditable change management.
Report a mistake