BS Information Technology · DevOps & Automation

Unit 6: Infrastructure as Code MCQs

50 solved multiple choice questions with answers and short explanations.

Q1. Which statement best describes Infrastructure as Code Concepts in Infrastructure as Code? Context: BS Information Technology / DevOps & Automation / Infrastructure as Code.

  1. AIt applies only to visual interface design.
  2. BIt should be understood through its function, dependencies, configuration, and effect on the wider IT service.
  3. CIt is only a naming convention and has no operational effect.
  4. DIt guarantees unlimited capacity without dependencies.
Show answer
Answer: B. It should be understood through its function, dependencies, configuration, and effect on the wider IT service.DevOps & Automation → Infrastructure as Code → Infrastructure as Code Concepts: It should be understood through its function, dependencies, configuration, and effect on the wider IT service.
Report a mistake

Q2. What is the main purpose of Infrastructure as Code Concepts in an Information Technology environment? Context: BS Information Technology / DevOps & Automation / Infrastructure as Code.

  1. AIt eliminates the need for business requirements.
  2. BIts sole purpose is to maximize hardware count.
  3. CIt guarantees security without controls or monitoring.
  4. DIt supports a defined business or technical service while meeting operational, security, and performance requirements.
Show answer
Answer: D. It supports a defined business or technical service while meeting operational, security, and performance requirements.DevOps & Automation → Infrastructure as Code → Infrastructure as Code Concepts: It supports a defined business or technical service while meeting operational, security, and performance requirements.
Report a mistake

Q3. An IT team is working with Infrastructure as Code Concepts. Which action is most appropriate? Context: BS Information Technology / DevOps & Automation / Infrastructure as Code.

  1. ASkip verification because successful installation proves correctness.
  2. BConfirm requirements and dependencies, apply the change in a controlled manner, and verify the resulting service.
  3. CChange production immediately without checking dependencies.
  4. DChoose a solution only because it is newest.
Show answer
Answer: B. Confirm requirements and dependencies, apply the change in a controlled manner, and verify the resulting service.DevOps & Automation → Infrastructure as Code → Infrastructure as Code Concepts: Confirm requirements and dependencies, apply the change in a controlled manner, and verify the resulting service.
Report a mistake

Q4. Which approach best supports correct configuration or implementation of Infrastructure as Code Concepts? Context: BS Information Technology / DevOps & Automation / Infrastructure as Code.

  1. AUse undocumented defaults in every environment.
  2. BChange several unrelated settings at once and avoid recording them.
  3. CAssume configuration is correct whenever the service starts.
  4. DUse documented requirements and baselines, make controlled changes, and validate the configuration afterward.
Show answer
Answer: D. Use documented requirements and baselines, make controlled changes, and validate the configuration afterward.DevOps & Automation → Infrastructure as Code → Infrastructure as Code Concepts: Use documented requirements and baselines, make controlled changes, and validate the configuration afterward.
Report a mistake

Q5. Which consideration is most important when securing or controlling Infrastructure as Code Concepts? Context: BS Information Technology / DevOps & Automation / Infrastructure as Code.

  1. AUse the same shared credential for every service.
  2. BApply least privilege, secure configuration, appropriate authentication, and monitoring according to the risk.
  3. CGive all users administrator privileges to avoid access problems.
  4. DDisable logging so attackers cannot see logs.
Show answer
Answer: B. Apply least privilege, secure configuration, appropriate authentication, and monitoring according to the risk.DevOps & Automation → Infrastructure as Code → Infrastructure as Code Concepts: Apply least privilege, secure configuration, appropriate authentication, and monitoring according to the risk.
Report a mistake

Q6. Which practice best improves reliability when using Infrastructure as Code Concepts? Context: BS Information Technology / DevOps & Automation / Infrastructure as Code.

  1. AAvoid monitoring to reduce system load.
  2. BDepend on one component and never test recovery.
  3. CTreat backups as unnecessary when storage is new.
  4. DUse monitoring, redundancy or recovery controls where appropriate, and test expected failure scenarios.
Show answer
Answer: D. Use monitoring, redundancy or recovery controls where appropriate, and test expected failure scenarios.DevOps & Automation → Infrastructure as Code → Infrastructure as Code Concepts: Use monitoring, redundancy or recovery controls where appropriate, and test expected failure scenarios.
Report a mistake

Q7. When troubleshooting Infrastructure as Code Concepts, what should be done first? Context: BS Information Technology / DevOps & Automation / Infrastructure as Code.

  1. AIgnore logs because they cannot assist diagnosis.
  2. BEstablish the symptoms and scope, collect evidence, then test the most plausible causes systematically.
  3. CReplace multiple components before collecting evidence.
  4. DAssume the first suspected cause is correct.
Show answer
Answer: B. Establish the symptoms and scope, collect evidence, then test the most plausible causes systematically.DevOps & Automation → Infrastructure as Code → Infrastructure as Code Concepts: Establish the symptoms and scope, collect evidence, then test the most plausible causes systematically.
Report a mistake

Q8. Which evidence best demonstrates that Infrastructure as Code Concepts is operating as intended? Context: BS Information Technology / DevOps & Automation / Infrastructure as Code.

  1. ARely only on a verbal statement that the system looks fine.
  2. BCount documentation pages regardless of service behavior.
  3. CUse an unrelated metric because it is easy to obtain.
  4. DUse logs, tests, service metrics, or monitoring data tied directly to the stated requirement or objective.
Show answer
Answer: D. Use logs, tests, service metrics, or monitoring data tied directly to the stated requirement or objective.DevOps & Automation → Infrastructure as Code → Infrastructure as Code Concepts: Use logs, tests, service metrics, or monitoring data tied directly to the stated requirement or objective.
Report a mistake

Q9. Which trade-off should be evaluated when selecting or scaling Infrastructure as Code Concepts? Context: BS Information Technology / DevOps & Automation / Infrastructure as Code.

  1. AOperational complexity never affects technology selection.
  2. BBalance performance, availability, security, cost, scalability, and operational complexity.
  3. CAlways maximize one metric and ignore all other constraints.
  4. DOnly purchase price matters in every IT decision.
Show answer
Answer: B. Balance performance, availability, security, cost, scalability, and operational complexity.DevOps & Automation → Infrastructure as Code → Infrastructure as Code Concepts: Balance performance, availability, security, cost, scalability, and operational complexity.
Report a mistake

Q10. Which example best represents professional practice involving Infrastructure as Code Concepts? Context: BS Information Technology / DevOps & Automation / Infrastructure as Code.

  1. AMake untracked production changes whenever convenient.
  2. BAvoid documentation and post-change verification.
  3. CUse personal preference instead of requirements and evidence.
  4. DDocument the objective, implement through controlled procedures, verify the outcome, and retain evidence.
Show answer
Answer: D. Document the objective, implement through controlled procedures, verify the outcome, and retain evidence.DevOps & Automation → Infrastructure as Code → Infrastructure as Code Concepts: Document the objective, implement through controlled procedures, verify the outcome, and retain evidence.
Report a mistake

Q11. Which statement best describes Infrastructure as Code Components in Infrastructure as Code? Context: BS Information Technology / DevOps & Automation / Infrastructure as Code.

  1. AIt is only a naming convention and has no operational effect.
  2. BIt guarantees unlimited capacity without dependencies.
  3. CIt applies only to visual interface design.
  4. DIt should be understood through its function, dependencies, configuration, and effect on the wider IT service.
Show answer
Answer: D. It should be understood through its function, dependencies, configuration, and effect on the wider IT service.DevOps & Automation → Infrastructure as Code → Infrastructure as Code Components: It should be understood through its function, dependencies, configuration, and effect on the wider IT service.
Report a mistake

Q12. What is the main purpose of Infrastructure as Code Components in an Information Technology environment? Context: BS Information Technology / DevOps & Automation / Infrastructure as Code.

  1. AIt guarantees security without controls or monitoring.
  2. BIt supports a defined business or technical service while meeting operational, security, and performance requirements.
  3. CIt eliminates the need for business requirements.
  4. DIts sole purpose is to maximize hardware count.
Show answer
Answer: B. It supports a defined business or technical service while meeting operational, security, and performance requirements.DevOps & Automation → Infrastructure as Code → Infrastructure as Code Components: It supports a defined business or technical service while meeting operational, security, and performance requirements.
Report a mistake

Q13. An IT team is working with Infrastructure as Code Components. Which action is most appropriate? Context: BS Information Technology / DevOps & Automation / Infrastructure as Code.

  1. AChange production immediately without checking dependencies.
  2. BChoose a solution only because it is newest.
  3. CSkip verification because successful installation proves correctness.
  4. DConfirm requirements and dependencies, apply the change in a controlled manner, and verify the resulting service.
Show answer
Answer: D. Confirm requirements and dependencies, apply the change in a controlled manner, and verify the resulting service.DevOps & Automation → Infrastructure as Code → Infrastructure as Code Components: Confirm requirements and dependencies, apply the change in a controlled manner, and verify the resulting service.
Report a mistake

Q14. Which approach best supports correct configuration or implementation of Infrastructure as Code Components? Context: BS Information Technology / DevOps & Automation / Infrastructure as Code.

  1. AAssume configuration is correct whenever the service starts.
  2. BUse documented requirements and baselines, make controlled changes, and validate the configuration afterward.
  3. CUse undocumented defaults in every environment.
  4. DChange several unrelated settings at once and avoid recording them.
Show answer
Answer: B. Use documented requirements and baselines, make controlled changes, and validate the configuration afterward.DevOps & Automation → Infrastructure as Code → Infrastructure as Code Components: Use documented requirements and baselines, make controlled changes, and validate the configuration afterward.
Report a mistake

Q15. Which consideration is most important when securing or controlling Infrastructure as Code Components? Context: BS Information Technology / DevOps & Automation / Infrastructure as Code.

  1. AGive all users administrator privileges to avoid access problems.
  2. BDisable logging so attackers cannot see logs.
  3. CUse the same shared credential for every service.
  4. DApply least privilege, secure configuration, appropriate authentication, and monitoring according to the risk.
Show answer
Answer: D. Apply least privilege, secure configuration, appropriate authentication, and monitoring according to the risk.DevOps & Automation → Infrastructure as Code → Infrastructure as Code Components: Apply least privilege, secure configuration, appropriate authentication, and monitoring according to the risk.
Report a mistake

Q16. Which practice best improves reliability when using Infrastructure as Code Components? Context: BS Information Technology / DevOps & Automation / Infrastructure as Code.

  1. ATreat backups as unnecessary when storage is new.
  2. BUse monitoring, redundancy or recovery controls where appropriate, and test expected failure scenarios.
  3. CAvoid monitoring to reduce system load.
  4. DDepend on one component and never test recovery.
Show answer
Answer: B. Use monitoring, redundancy or recovery controls where appropriate, and test expected failure scenarios.DevOps & Automation → Infrastructure as Code → Infrastructure as Code Components: Use monitoring, redundancy or recovery controls where appropriate, and test expected failure scenarios.
Report a mistake

Q17. When troubleshooting Infrastructure as Code Components, what should be done first? Context: BS Information Technology / DevOps & Automation / Infrastructure as Code.

  1. AReplace multiple components before collecting evidence.
  2. BAssume the first suspected cause is correct.
  3. CIgnore logs because they cannot assist diagnosis.
  4. DEstablish the symptoms and scope, collect evidence, then test the most plausible causes systematically.
Show answer
Answer: D. Establish the symptoms and scope, collect evidence, then test the most plausible causes systematically.DevOps & Automation → Infrastructure as Code → Infrastructure as Code Components: Establish the symptoms and scope, collect evidence, then test the most plausible causes systematically.
Report a mistake

Q18. Which evidence best demonstrates that Infrastructure as Code Components is operating as intended? Context: BS Information Technology / DevOps & Automation / Infrastructure as Code.

  1. AUse an unrelated metric because it is easy to obtain.
  2. BUse logs, tests, service metrics, or monitoring data tied directly to the stated requirement or objective.
  3. CRely only on a verbal statement that the system looks fine.
  4. DCount documentation pages regardless of service behavior.
Show answer
Answer: B. Use logs, tests, service metrics, or monitoring data tied directly to the stated requirement or objective.DevOps & Automation → Infrastructure as Code → Infrastructure as Code Components: Use logs, tests, service metrics, or monitoring data tied directly to the stated requirement or objective.
Report a mistake

Q19. Which trade-off should be evaluated when selecting or scaling Infrastructure as Code Components? Context: BS Information Technology / DevOps & Automation / Infrastructure as Code.

  1. AAlways maximize one metric and ignore all other constraints.
  2. BOnly purchase price matters in every IT decision.
  3. COperational complexity never affects technology selection.
  4. DBalance performance, availability, security, cost, scalability, and operational complexity.
Show answer
Answer: D. Balance performance, availability, security, cost, scalability, and operational complexity.DevOps & Automation → Infrastructure as Code → Infrastructure as Code Components: Balance performance, availability, security, cost, scalability, and operational complexity.
Report a mistake

Q20. Which example best represents professional practice involving Infrastructure as Code Components? Context: BS Information Technology / DevOps & Automation / Infrastructure as Code.

  1. AUse personal preference instead of requirements and evidence.
  2. BDocument the objective, implement through controlled procedures, verify the outcome, and retain evidence.
  3. CMake untracked production changes whenever convenient.
  4. DAvoid documentation and post-change verification.
Show answer
Answer: B. Document the objective, implement through controlled procedures, verify the outcome, and retain evidence.DevOps & Automation → Infrastructure as Code → Infrastructure as Code Components: Document the objective, implement through controlled procedures, verify the outcome, and retain evidence.
Report a mistake

Q21. Which statement best describes Infrastructure as Code Configuration in Infrastructure as Code? Context: BS Information Technology / DevOps & Automation / Infrastructure as Code.

  1. AIt applies only to visual interface design.
  2. BIt should be understood through its function, dependencies, configuration, and effect on the wider IT service.
  3. CIt is only a naming convention and has no operational effect.
  4. DIt guarantees unlimited capacity without dependencies.
Show answer
Answer: B. It should be understood through its function, dependencies, configuration, and effect on the wider IT service.DevOps & Automation → Infrastructure as Code → Infrastructure as Code Configuration: It should be understood through its function, dependencies, configuration, and effect on the wider IT service.
Report a mistake

Q22. What is the main purpose of Infrastructure as Code Configuration in an Information Technology environment? Context: BS Information Technology / DevOps & Automation / Infrastructure as Code.

  1. AIt eliminates the need for business requirements.
  2. BIts sole purpose is to maximize hardware count.
  3. CIt guarantees security without controls or monitoring.
  4. DIt supports a defined business or technical service while meeting operational, security, and performance requirements.
Show answer
Answer: D. It supports a defined business or technical service while meeting operational, security, and performance requirements.DevOps & Automation → Infrastructure as Code → Infrastructure as Code Configuration: It supports a defined business or technical service while meeting operational, security, and performance requirements.
Report a mistake

Q23. An IT team is working with Infrastructure as Code Configuration. Which action is most appropriate? Context: BS Information Technology / DevOps & Automation / Infrastructure as Code.

  1. ASkip verification because successful installation proves correctness.
  2. BConfirm requirements and dependencies, apply the change in a controlled manner, and verify the resulting service.
  3. CChange production immediately without checking dependencies.
  4. DChoose a solution only because it is newest.
Show answer
Answer: B. Confirm requirements and dependencies, apply the change in a controlled manner, and verify the resulting service.DevOps & Automation → Infrastructure as Code → Infrastructure as Code Configuration: Confirm requirements and dependencies, apply the change in a controlled manner, and verify the resulting service.
Report a mistake

Q24. Which approach best supports correct configuration or implementation of Infrastructure as Code Configuration? Context: BS Information Technology / DevOps & Automation / Infrastructure as Code.

  1. AUse undocumented defaults in every environment.
  2. BChange several unrelated settings at once and avoid recording them.
  3. CAssume configuration is correct whenever the service starts.
  4. DUse documented requirements and baselines, make controlled changes, and validate the configuration afterward.
Show answer
Answer: D. Use documented requirements and baselines, make controlled changes, and validate the configuration afterward.DevOps & Automation → Infrastructure as Code → Infrastructure as Code Configuration: Use documented requirements and baselines, make controlled changes, and validate the configuration afterward.
Report a mistake

Q25. Which consideration is most important when securing or controlling Infrastructure as Code Configuration? Context: BS Information Technology / DevOps & Automation / Infrastructure as Code.

  1. AUse the same shared credential for every service.
  2. BApply least privilege, secure configuration, appropriate authentication, and monitoring according to the risk.
  3. CGive all users administrator privileges to avoid access problems.
  4. DDisable logging so attackers cannot see logs.
Show answer
Answer: B. Apply least privilege, secure configuration, appropriate authentication, and monitoring according to the risk.DevOps & Automation → Infrastructure as Code → Infrastructure as Code Configuration: Apply least privilege, secure configuration, appropriate authentication, and monitoring according to the risk.
Report a mistake

Q26. Which practice best improves reliability when using Infrastructure as Code Configuration? Context: BS Information Technology / DevOps & Automation / Infrastructure as Code.

  1. AAvoid monitoring to reduce system load.
  2. BDepend on one component and never test recovery.
  3. CTreat backups as unnecessary when storage is new.
  4. DUse monitoring, redundancy or recovery controls where appropriate, and test expected failure scenarios.
Show answer
Answer: D. Use monitoring, redundancy or recovery controls where appropriate, and test expected failure scenarios.DevOps & Automation → Infrastructure as Code → Infrastructure as Code Configuration: Use monitoring, redundancy or recovery controls where appropriate, and test expected failure scenarios.
Report a mistake

Q27. When troubleshooting Infrastructure as Code Configuration, what should be done first? Context: BS Information Technology / DevOps & Automation / Infrastructure as Code.

  1. AIgnore logs because they cannot assist diagnosis.
  2. BEstablish the symptoms and scope, collect evidence, then test the most plausible causes systematically.
  3. CReplace multiple components before collecting evidence.
  4. DAssume the first suspected cause is correct.
Show answer
Answer: B. Establish the symptoms and scope, collect evidence, then test the most plausible causes systematically.DevOps & Automation → Infrastructure as Code → Infrastructure as Code Configuration: Establish the symptoms and scope, collect evidence, then test the most plausible causes systematically.
Report a mistake

Q28. Which evidence best demonstrates that Infrastructure as Code Configuration is operating as intended? Context: BS Information Technology / DevOps & Automation / Infrastructure as Code.

  1. ARely only on a verbal statement that the system looks fine.
  2. BCount documentation pages regardless of service behavior.
  3. CUse an unrelated metric because it is easy to obtain.
  4. DUse logs, tests, service metrics, or monitoring data tied directly to the stated requirement or objective.
Show answer
Answer: D. Use logs, tests, service metrics, or monitoring data tied directly to the stated requirement or objective.DevOps & Automation → Infrastructure as Code → Infrastructure as Code Configuration: Use logs, tests, service metrics, or monitoring data tied directly to the stated requirement or objective.
Report a mistake

Q29. Which trade-off should be evaluated when selecting or scaling Infrastructure as Code Configuration? Context: BS Information Technology / DevOps & Automation / Infrastructure as Code.

  1. AOperational complexity never affects technology selection.
  2. BBalance performance, availability, security, cost, scalability, and operational complexity.
  3. CAlways maximize one metric and ignore all other constraints.
  4. DOnly purchase price matters in every IT decision.
Show answer
Answer: B. Balance performance, availability, security, cost, scalability, and operational complexity.DevOps & Automation → Infrastructure as Code → Infrastructure as Code Configuration: Balance performance, availability, security, cost, scalability, and operational complexity.
Report a mistake

Q30. Which example best represents professional practice involving Infrastructure as Code Configuration? Context: BS Information Technology / DevOps & Automation / Infrastructure as Code.

  1. AMake untracked production changes whenever convenient.
  2. BAvoid documentation and post-change verification.
  3. CUse personal preference instead of requirements and evidence.
  4. DDocument the objective, implement through controlled procedures, verify the outcome, and retain evidence.
Show answer
Answer: D. Document the objective, implement through controlled procedures, verify the outcome, and retain evidence.DevOps & Automation → Infrastructure as Code → Infrastructure as Code Configuration: Document the objective, implement through controlled procedures, verify the outcome, and retain evidence.
Report a mistake

Q31. Which statement best describes Infrastructure as Code Evaluation in Infrastructure as Code? Context: BS Information Technology / DevOps & Automation / Infrastructure as Code.

  1. AIt is only a naming convention and has no operational effect.
  2. BIt guarantees unlimited capacity without dependencies.
  3. CIt applies only to visual interface design.
  4. DIt should be understood through its function, dependencies, configuration, and effect on the wider IT service.
Show answer
Answer: D. It should be understood through its function, dependencies, configuration, and effect on the wider IT service.DevOps & Automation → Infrastructure as Code → Infrastructure as Code Evaluation: It should be understood through its function, dependencies, configuration, and effect on the wider IT service.
Report a mistake

Q32. What is the main purpose of Infrastructure as Code Evaluation in an Information Technology environment? Context: BS Information Technology / DevOps & Automation / Infrastructure as Code.

  1. AIt guarantees security without controls or monitoring.
  2. BIt supports a defined business or technical service while meeting operational, security, and performance requirements.
  3. CIt eliminates the need for business requirements.
  4. DIts sole purpose is to maximize hardware count.
Show answer
Answer: B. It supports a defined business or technical service while meeting operational, security, and performance requirements.DevOps & Automation → Infrastructure as Code → Infrastructure as Code Evaluation: It supports a defined business or technical service while meeting operational, security, and performance requirements.
Report a mistake

Q33. An IT team is working with Infrastructure as Code Evaluation. Which action is most appropriate? Context: BS Information Technology / DevOps & Automation / Infrastructure as Code.

  1. AChange production immediately without checking dependencies.
  2. BChoose a solution only because it is newest.
  3. CSkip verification because successful installation proves correctness.
  4. DConfirm requirements and dependencies, apply the change in a controlled manner, and verify the resulting service.
Show answer
Answer: D. Confirm requirements and dependencies, apply the change in a controlled manner, and verify the resulting service.DevOps & Automation → Infrastructure as Code → Infrastructure as Code Evaluation: Confirm requirements and dependencies, apply the change in a controlled manner, and verify the resulting service.
Report a mistake

Q34. Which approach best supports correct configuration or implementation of Infrastructure as Code Evaluation? Context: BS Information Technology / DevOps & Automation / Infrastructure as Code.

  1. AAssume configuration is correct whenever the service starts.
  2. BUse documented requirements and baselines, make controlled changes, and validate the configuration afterward.
  3. CUse undocumented defaults in every environment.
  4. DChange several unrelated settings at once and avoid recording them.
Show answer
Answer: B. Use documented requirements and baselines, make controlled changes, and validate the configuration afterward.DevOps & Automation → Infrastructure as Code → Infrastructure as Code Evaluation: Use documented requirements and baselines, make controlled changes, and validate the configuration afterward.
Report a mistake

Q35. Which consideration is most important when securing or controlling Infrastructure as Code Evaluation? Context: BS Information Technology / DevOps & Automation / Infrastructure as Code.

  1. AGive all users administrator privileges to avoid access problems.
  2. BDisable logging so attackers cannot see logs.
  3. CUse the same shared credential for every service.
  4. DApply least privilege, secure configuration, appropriate authentication, and monitoring according to the risk.
Show answer
Answer: D. Apply least privilege, secure configuration, appropriate authentication, and monitoring according to the risk.DevOps & Automation → Infrastructure as Code → Infrastructure as Code Evaluation: Apply least privilege, secure configuration, appropriate authentication, and monitoring according to the risk.
Report a mistake

Q36. Which practice best improves reliability when using Infrastructure as Code Evaluation? Context: BS Information Technology / DevOps & Automation / Infrastructure as Code.

  1. ATreat backups as unnecessary when storage is new.
  2. BUse monitoring, redundancy or recovery controls where appropriate, and test expected failure scenarios.
  3. CAvoid monitoring to reduce system load.
  4. DDepend on one component and never test recovery.
Show answer
Answer: B. Use monitoring, redundancy or recovery controls where appropriate, and test expected failure scenarios.DevOps & Automation → Infrastructure as Code → Infrastructure as Code Evaluation: Use monitoring, redundancy or recovery controls where appropriate, and test expected failure scenarios.
Report a mistake

Q37. When troubleshooting Infrastructure as Code Evaluation, what should be done first? Context: BS Information Technology / DevOps & Automation / Infrastructure as Code.

  1. AReplace multiple components before collecting evidence.
  2. BAssume the first suspected cause is correct.
  3. CIgnore logs because they cannot assist diagnosis.
  4. DEstablish the symptoms and scope, collect evidence, then test the most plausible causes systematically.
Show answer
Answer: D. Establish the symptoms and scope, collect evidence, then test the most plausible causes systematically.DevOps & Automation → Infrastructure as Code → Infrastructure as Code Evaluation: Establish the symptoms and scope, collect evidence, then test the most plausible causes systematically.
Report a mistake

Q38. Which evidence best demonstrates that Infrastructure as Code Evaluation is operating as intended? Context: BS Information Technology / DevOps & Automation / Infrastructure as Code.

  1. AUse an unrelated metric because it is easy to obtain.
  2. BUse logs, tests, service metrics, or monitoring data tied directly to the stated requirement or objective.
  3. CRely only on a verbal statement that the system looks fine.
  4. DCount documentation pages regardless of service behavior.
Show answer
Answer: B. Use logs, tests, service metrics, or monitoring data tied directly to the stated requirement or objective.DevOps & Automation → Infrastructure as Code → Infrastructure as Code Evaluation: Use logs, tests, service metrics, or monitoring data tied directly to the stated requirement or objective.
Report a mistake

Q39. Which trade-off should be evaluated when selecting or scaling Infrastructure as Code Evaluation? Context: BS Information Technology / DevOps & Automation / Infrastructure as Code.

  1. AAlways maximize one metric and ignore all other constraints.
  2. BOnly purchase price matters in every IT decision.
  3. COperational complexity never affects technology selection.
  4. DBalance performance, availability, security, cost, scalability, and operational complexity.
Show answer
Answer: D. Balance performance, availability, security, cost, scalability, and operational complexity.DevOps & Automation → Infrastructure as Code → Infrastructure as Code Evaluation: Balance performance, availability, security, cost, scalability, and operational complexity.
Report a mistake

Q40. Which example best represents professional practice involving Infrastructure as Code Evaluation? Context: BS Information Technology / DevOps & Automation / Infrastructure as Code.

  1. AUse personal preference instead of requirements and evidence.
  2. BDocument the objective, implement through controlled procedures, verify the outcome, and retain evidence.
  3. CMake untracked production changes whenever convenient.
  4. DAvoid documentation and post-change verification.
Show answer
Answer: B. Document the objective, implement through controlled procedures, verify the outcome, and retain evidence.DevOps & Automation → Infrastructure as Code → Infrastructure as Code Evaluation: Document the objective, implement through controlled procedures, verify the outcome, and retain evidence.
Report a mistake

Q41. Which statement best describes Infrastructure as Code Applications in Infrastructure as Code? Context: BS Information Technology / DevOps & Automation / Infrastructure as Code.

  1. AIt applies only to visual interface design.
  2. BIt should be understood through its function, dependencies, configuration, and effect on the wider IT service.
  3. CIt is only a naming convention and has no operational effect.
  4. DIt guarantees unlimited capacity without dependencies.
Show answer
Answer: B. It should be understood through its function, dependencies, configuration, and effect on the wider IT service.DevOps & Automation → Infrastructure as Code → Infrastructure as Code Applications: It should be understood through its function, dependencies, configuration, and effect on the wider IT service.
Report a mistake

Q42. What is the main purpose of Infrastructure as Code Applications in an Information Technology environment? Context: BS Information Technology / DevOps & Automation / Infrastructure as Code.

  1. AIt eliminates the need for business requirements.
  2. BIts sole purpose is to maximize hardware count.
  3. CIt guarantees security without controls or monitoring.
  4. DIt supports a defined business or technical service while meeting operational, security, and performance requirements.
Show answer
Answer: D. It supports a defined business or technical service while meeting operational, security, and performance requirements.DevOps & Automation → Infrastructure as Code → Infrastructure as Code Applications: It supports a defined business or technical service while meeting operational, security, and performance requirements.
Report a mistake

Q43. An IT team is working with Infrastructure as Code Applications. Which action is most appropriate? Context: BS Information Technology / DevOps & Automation / Infrastructure as Code.

  1. ASkip verification because successful installation proves correctness.
  2. BConfirm requirements and dependencies, apply the change in a controlled manner, and verify the resulting service.
  3. CChange production immediately without checking dependencies.
  4. DChoose a solution only because it is newest.
Show answer
Answer: B. Confirm requirements and dependencies, apply the change in a controlled manner, and verify the resulting service.DevOps & Automation → Infrastructure as Code → Infrastructure as Code Applications: Confirm requirements and dependencies, apply the change in a controlled manner, and verify the resulting service.
Report a mistake

Q44. Which approach best supports correct configuration or implementation of Infrastructure as Code Applications? Context: BS Information Technology / DevOps & Automation / Infrastructure as Code.

  1. AUse undocumented defaults in every environment.
  2. BChange several unrelated settings at once and avoid recording them.
  3. CAssume configuration is correct whenever the service starts.
  4. DUse documented requirements and baselines, make controlled changes, and validate the configuration afterward.
Show answer
Answer: D. Use documented requirements and baselines, make controlled changes, and validate the configuration afterward.DevOps & Automation → Infrastructure as Code → Infrastructure as Code Applications: Use documented requirements and baselines, make controlled changes, and validate the configuration afterward.
Report a mistake

Q45. Which consideration is most important when securing or controlling Infrastructure as Code Applications? Context: BS Information Technology / DevOps & Automation / Infrastructure as Code.

  1. AUse the same shared credential for every service.
  2. BApply least privilege, secure configuration, appropriate authentication, and monitoring according to the risk.
  3. CGive all users administrator privileges to avoid access problems.
  4. DDisable logging so attackers cannot see logs.
Show answer
Answer: B. Apply least privilege, secure configuration, appropriate authentication, and monitoring according to the risk.DevOps & Automation → Infrastructure as Code → Infrastructure as Code Applications: Apply least privilege, secure configuration, appropriate authentication, and monitoring according to the risk.
Report a mistake

Q46. Which practice best improves reliability when using Infrastructure as Code Applications? Context: BS Information Technology / DevOps & Automation / Infrastructure as Code.

  1. AAvoid monitoring to reduce system load.
  2. BDepend on one component and never test recovery.
  3. CTreat backups as unnecessary when storage is new.
  4. DUse monitoring, redundancy or recovery controls where appropriate, and test expected failure scenarios.
Show answer
Answer: D. Use monitoring, redundancy or recovery controls where appropriate, and test expected failure scenarios.DevOps & Automation → Infrastructure as Code → Infrastructure as Code Applications: Use monitoring, redundancy or recovery controls where appropriate, and test expected failure scenarios.
Report a mistake

Q47. When troubleshooting Infrastructure as Code Applications, what should be done first? Context: BS Information Technology / DevOps & Automation / Infrastructure as Code.

  1. AIgnore logs because they cannot assist diagnosis.
  2. BEstablish the symptoms and scope, collect evidence, then test the most plausible causes systematically.
  3. CReplace multiple components before collecting evidence.
  4. DAssume the first suspected cause is correct.
Show answer
Answer: B. Establish the symptoms and scope, collect evidence, then test the most plausible causes systematically.DevOps & Automation → Infrastructure as Code → Infrastructure as Code Applications: Establish the symptoms and scope, collect evidence, then test the most plausible causes systematically.
Report a mistake

Q48. Which evidence best demonstrates that Infrastructure as Code Applications is operating as intended? Context: BS Information Technology / DevOps & Automation / Infrastructure as Code.

  1. ARely only on a verbal statement that the system looks fine.
  2. BCount documentation pages regardless of service behavior.
  3. CUse an unrelated metric because it is easy to obtain.
  4. DUse logs, tests, service metrics, or monitoring data tied directly to the stated requirement or objective.
Show answer
Answer: D. Use logs, tests, service metrics, or monitoring data tied directly to the stated requirement or objective.DevOps & Automation → Infrastructure as Code → Infrastructure as Code Applications: Use logs, tests, service metrics, or monitoring data tied directly to the stated requirement or objective.
Report a mistake

Q49. Which trade-off should be evaluated when selecting or scaling Infrastructure as Code Applications? Context: BS Information Technology / DevOps & Automation / Infrastructure as Code.

  1. AOperational complexity never affects technology selection.
  2. BBalance performance, availability, security, cost, scalability, and operational complexity.
  3. CAlways maximize one metric and ignore all other constraints.
  4. DOnly purchase price matters in every IT decision.
Show answer
Answer: B. Balance performance, availability, security, cost, scalability, and operational complexity.DevOps & Automation → Infrastructure as Code → Infrastructure as Code Applications: Balance performance, availability, security, cost, scalability, and operational complexity.
Report a mistake

Q50. Which example best represents professional practice involving Infrastructure as Code Applications? Context: BS Information Technology / DevOps & Automation / Infrastructure as Code.

  1. AMake untracked production changes whenever convenient.
  2. BAvoid documentation and post-change verification.
  3. CUse personal preference instead of requirements and evidence.
  4. DDocument the objective, implement through controlled procedures, verify the outcome, and retain evidence.
Show answer
Answer: D. Document the objective, implement through controlled procedures, verify the outcome, and retain evidence.DevOps & Automation → Infrastructure as Code → Infrastructure as Code Applications: Document the objective, implement through controlled procedures, verify the outcome, and retain evidence.
Report a mistake