BS Cloud Computing · Identity & Access Management

Unit 7: Single Sign On MCQs

50 solved multiple choice questions with answers and short explanations.

Q1. Which statement best describes Single Sign On Concepts within Single Sign On? Context: BS Cloud Computing / Identity & Access Management / Single Sign On.

  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.Identity & Access Management → Single Sign On → Single Sign On 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 Single Sign On Concepts in a cloud environment? Context: BS Cloud Computing / Identity & Access Management / Single Sign On.

  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.Identity & Access Management → Single Sign On → Single Sign On 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 Single Sign On Concepts. Which approach is most appropriate? Context: BS Cloud Computing / Identity & Access Management / Single Sign On.

  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.Identity & Access Management → Single Sign On → Single Sign On 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 Single Sign On Concepts? Context: BS Cloud Computing / Identity & Access Management / Single Sign On.

  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.Identity & Access Management → Single Sign On → Single Sign On 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 Single Sign On Concepts? Context: BS Cloud Computing / Identity & Access Management / Single Sign On.

  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.Identity & Access Management → Single Sign On → Single Sign On 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 Single Sign On Concepts? Context: BS Cloud Computing / Identity & Access Management / Single Sign On.

  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.Identity & Access Management → Single Sign On → Single Sign On 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 Single Sign On Concepts? Context: BS Cloud Computing / Identity & Access Management / Single Sign On.

  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.Identity & Access Management → Single Sign On → Single Sign On 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 Single Sign On Concepts is working as intended? Context: BS Cloud Computing / Identity & Access Management / Single Sign On.

  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.Identity & Access Management → Single Sign On → Single Sign On 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 Single Sign On Concepts? Context: BS Cloud Computing / Identity & Access Management / Single Sign On.

  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.Identity & Access Management → Single Sign On → Single Sign On Concepts: Balance availability, performance, security, cost, scalability, portability, and operational complexity.
Report a mistake

Q10. Which practice best supports responsible governance of Single Sign On Concepts? Context: BS Cloud Computing / Identity & Access Management / Single Sign On.

  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.Identity & Access Management → Single Sign On → Single Sign On Concepts: Use ownership, policies, tagging, access controls, cost accountability, compliance checks, and auditable change management.
Report a mistake

Q11. Which statement best describes Single Sign On Components within Single Sign On? Context: BS Cloud Computing / Identity & Access Management / Single Sign On.

  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.Identity & Access Management → Single Sign On → Single Sign On 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 Single Sign On Components in a cloud environment? Context: BS Cloud Computing / Identity & Access Management / Single Sign On.

  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.Identity & Access Management → Single Sign On → Single Sign On 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 Single Sign On Components. Which approach is most appropriate? Context: BS Cloud Computing / Identity & Access Management / Single Sign On.

  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.Identity & Access Management → Single Sign On → Single Sign On 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 Single Sign On Components? Context: BS Cloud Computing / Identity & Access Management / Single Sign On.

  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.Identity & Access Management → Single Sign On → Single Sign On 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 Single Sign On Components? Context: BS Cloud Computing / Identity & Access Management / Single Sign On.

  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.Identity & Access Management → Single Sign On → Single Sign On 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 Single Sign On Components? Context: BS Cloud Computing / Identity & Access Management / Single Sign On.

  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.Identity & Access Management → Single Sign On → Single Sign On 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 Single Sign On Components? Context: BS Cloud Computing / Identity & Access Management / Single Sign On.

  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.Identity & Access Management → Single Sign On → Single Sign On 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 Single Sign On Components is working as intended? Context: BS Cloud Computing / Identity & Access Management / Single Sign On.

  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.Identity & Access Management → Single Sign On → Single Sign On 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 Single Sign On Components? Context: BS Cloud Computing / Identity & Access Management / Single Sign On.

  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.Identity & Access Management → Single Sign On → Single Sign On Components: Balance availability, performance, security, cost, scalability, portability, and operational complexity.
Report a mistake

Q20. Which practice best supports responsible governance of Single Sign On Components? Context: BS Cloud Computing / Identity & Access Management / Single Sign On.

  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.Identity & Access Management → Single Sign On → Single Sign On Components: Use ownership, policies, tagging, access controls, cost accountability, compliance checks, and auditable change management.
Report a mistake

Q21. Which statement best describes Single Sign On Configuration within Single Sign On? Context: BS Cloud Computing / Identity & Access Management / Single Sign On.

  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.Identity & Access Management → Single Sign On → Single Sign On 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 Single Sign On Configuration in a cloud environment? Context: BS Cloud Computing / Identity & Access Management / Single Sign On.

  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.Identity & Access Management → Single Sign On → Single Sign On 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 Single Sign On Configuration. Which approach is most appropriate? Context: BS Cloud Computing / Identity & Access Management / Single Sign On.

  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.Identity & Access Management → Single Sign On → Single Sign On 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 Single Sign On Configuration? Context: BS Cloud Computing / Identity & Access Management / Single Sign On.

  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.Identity & Access Management → Single Sign On → Single Sign On 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 Single Sign On Configuration? Context: BS Cloud Computing / Identity & Access Management / Single Sign On.

  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.Identity & Access Management → Single Sign On → Single Sign On 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 Single Sign On Configuration? Context: BS Cloud Computing / Identity & Access Management / Single Sign On.

  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.Identity & Access Management → Single Sign On → Single Sign On 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 Single Sign On Configuration? Context: BS Cloud Computing / Identity & Access Management / Single Sign On.

  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.Identity & Access Management → Single Sign On → Single Sign On 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 Single Sign On Configuration is working as intended? Context: BS Cloud Computing / Identity & Access Management / Single Sign On.

  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.Identity & Access Management → Single Sign On → Single Sign On 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 Single Sign On Configuration? Context: BS Cloud Computing / Identity & Access Management / Single Sign On.

  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.Identity & Access Management → Single Sign On → Single Sign On Configuration: Balance availability, performance, security, cost, scalability, portability, and operational complexity.
Report a mistake

Q30. Which practice best supports responsible governance of Single Sign On Configuration? Context: BS Cloud Computing / Identity & Access Management / Single Sign On.

  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.Identity & Access Management → Single Sign On → Single Sign On Configuration: Use ownership, policies, tagging, access controls, cost accountability, compliance checks, and auditable change management.
Report a mistake

Q31. Which statement best describes Single Sign On Evaluation within Single Sign On? Context: BS Cloud Computing / Identity & Access Management / Single Sign On.

  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.Identity & Access Management → Single Sign On → Single Sign On 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 Single Sign On Evaluation in a cloud environment? Context: BS Cloud Computing / Identity & Access Management / Single Sign On.

  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.Identity & Access Management → Single Sign On → Single Sign On 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 Single Sign On Evaluation. Which approach is most appropriate? Context: BS Cloud Computing / Identity & Access Management / Single Sign On.

  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.Identity & Access Management → Single Sign On → Single Sign On 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 Single Sign On Evaluation? Context: BS Cloud Computing / Identity & Access Management / Single Sign On.

  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.Identity & Access Management → Single Sign On → Single Sign On 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 Single Sign On Evaluation? Context: BS Cloud Computing / Identity & Access Management / Single Sign On.

  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.Identity & Access Management → Single Sign On → Single Sign On 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 Single Sign On Evaluation? Context: BS Cloud Computing / Identity & Access Management / Single Sign On.

  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.Identity & Access Management → Single Sign On → Single Sign On 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 Single Sign On Evaluation? Context: BS Cloud Computing / Identity & Access Management / Single Sign On.

  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.Identity & Access Management → Single Sign On → Single Sign On 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 Single Sign On Evaluation is working as intended? Context: BS Cloud Computing / Identity & Access Management / Single Sign On.

  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.Identity & Access Management → Single Sign On → Single Sign On 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 Single Sign On Evaluation? Context: BS Cloud Computing / Identity & Access Management / Single Sign On.

  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.Identity & Access Management → Single Sign On → Single Sign On Evaluation: Balance availability, performance, security, cost, scalability, portability, and operational complexity.
Report a mistake

Q40. Which practice best supports responsible governance of Single Sign On Evaluation? Context: BS Cloud Computing / Identity & Access Management / Single Sign On.

  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.Identity & Access Management → Single Sign On → Single Sign On Evaluation: Use ownership, policies, tagging, access controls, cost accountability, compliance checks, and auditable change management.
Report a mistake

Q41. Which statement best describes Single Sign On Applications within Single Sign On? Context: BS Cloud Computing / Identity & Access Management / Single Sign On.

  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.Identity & Access Management → Single Sign On → Single Sign On 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 Single Sign On Applications in a cloud environment? Context: BS Cloud Computing / Identity & Access Management / Single Sign On.

  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.Identity & Access Management → Single Sign On → Single Sign On 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 Single Sign On Applications. Which approach is most appropriate? Context: BS Cloud Computing / Identity & Access Management / Single Sign On.

  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.Identity & Access Management → Single Sign On → Single Sign On 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 Single Sign On Applications? Context: BS Cloud Computing / Identity & Access Management / Single Sign On.

  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.Identity & Access Management → Single Sign On → Single Sign On 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 Single Sign On Applications? Context: BS Cloud Computing / Identity & Access Management / Single Sign On.

  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.Identity & Access Management → Single Sign On → Single Sign On 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 Single Sign On Applications? Context: BS Cloud Computing / Identity & Access Management / Single Sign On.

  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.Identity & Access Management → Single Sign On → Single Sign On 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 Single Sign On Applications? Context: BS Cloud Computing / Identity & Access Management / Single Sign On.

  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.Identity & Access Management → Single Sign On → Single Sign On 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 Single Sign On Applications is working as intended? Context: BS Cloud Computing / Identity & Access Management / Single Sign On.

  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.Identity & Access Management → Single Sign On → Single Sign On 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 Single Sign On Applications? Context: BS Cloud Computing / Identity & Access Management / Single Sign On.

  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.Identity & Access Management → Single Sign On → Single Sign On Applications: Balance availability, performance, security, cost, scalability, portability, and operational complexity.
Report a mistake

Q50. Which practice best supports responsible governance of Single Sign On Applications? Context: BS Cloud Computing / Identity & Access Management / Single Sign On.

  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.Identity & Access Management → Single Sign On → Single Sign On Applications: Use ownership, policies, tagging, access controls, cost accountability, compliance checks, and auditable change management.
Report a mistake