BS Computer Engineering · Discrete Structures

Unit 10: Discrete Probability MCQs

50 solved multiple choice questions with answers and short explanations.

Q1. Which statement best describes Discrete Probability Concepts within Discrete Probability? Context: BS Computer Engineering / Discrete Structures / Discrete Probability.

  1. AIt can be evaluated without knowing any constraints or operating conditions.
  2. BIt should be understood through its governing principles, interfaces, constraints, inputs, outputs, and role in the overall system.
  3. CIt is only a naming convention with no effect on system behavior.
  4. DIt guarantees correct operation without considering interfaces.
Show answer
Answer: B. It should be understood through its governing principles, interfaces, constraints, inputs, outputs, and role in the overall system.Discrete Structures → Discrete Probability → Discrete Probability Concepts: It should be understood through its governing principles, interfaces, constraints, inputs, outputs, and role in the overall system.
Report a mistake

Q2. What is the primary engineering purpose of Discrete Probability Concepts? Context: BS Computer Engineering / Discrete Structures / Discrete Probability.

  1. AIts sole purpose is to maximize component count.
  2. BIt removes the need for requirements and verification.
  3. CIt guarantees maximum performance regardless of power or cost.
  4. DIt supports a defined hardware, software, signal, control, or system objective while satisfying engineering constraints.
Show answer
Answer: D. It supports a defined hardware, software, signal, control, or system objective while satisfying engineering constraints.Discrete Structures → Discrete Probability → Discrete Probability Concepts: It supports a defined hardware, software, signal, control, or system objective while satisfying engineering constraints.
Report a mistake

Q3. A computer-engineering team is working with Discrete Probability Concepts. Which approach is most appropriate? Context: BS Computer Engineering / Discrete Structures / Discrete Probability.

  1. ASkip verification once the design compiles or powers on.
  2. BDefine requirements and interfaces, analyze constraints, implement the selected approach, and verify the resulting behavior.
  3. CSelect components before defining requirements.
  4. DIgnore hardware-software interfaces because they are independent.
Show answer
Answer: B. Define requirements and interfaces, analyze constraints, implement the selected approach, and verify the resulting behavior.Discrete Structures → Discrete Probability → Discrete Probability Concepts: Define requirements and interfaces, analyze constraints, implement the selected approach, and verify the resulting behavior.
Report a mistake

Q4. Which principle best supports correct analysis of Discrete Probability Concepts? Context: BS Computer Engineering / Discrete Structures / Discrete Probability.

  1. AUse equations without checking their assumptions.
  2. BIgnore units and boundary conditions when calculations appear reasonable.
  3. CChoose the result that looks familiar instead of validating the model.
  4. DUse an appropriate model, identify assumptions and boundary conditions, and apply the relevant engineering relationships consistently.
Show answer
Answer: D. Use an appropriate model, identify assumptions and boundary conditions, and apply the relevant engineering relationships consistently.Discrete Structures → Discrete Probability → Discrete Probability Concepts: Use an appropriate model, identify assumptions and boundary conditions, and apply the relevant engineering relationships consistently.
Report a mistake

Q5. Which consideration is most important when designing a solution involving Discrete Probability Concepts? Context: BS Computer Engineering / Discrete Structures / Discrete Probability.

  1. AChoose the most complex architecture even when requirements are simple.
  2. BBalance functional requirements with timing, power, cost, reliability, complexity, safety, and interface constraints.
  3. CAlways maximize clock rate regardless of power and reliability.
  4. DIgnore interfaces if each component works independently.
Show answer
Answer: B. Balance functional requirements with timing, power, cost, reliability, complexity, safety, and interface constraints.Discrete Structures → Discrete Probability → Discrete Probability Concepts: Balance functional requirements with timing, power, cost, reliability, complexity, safety, and interface constraints.
Report a mistake

Q6. How should an engineer verify work involving Discrete Probability Concepts? Context: BS Computer Engineering / Discrete Structures / Discrete Probability.

  1. AAssume simulation alone proves every physical implementation.
  2. BTest only the easiest operating condition.
  3. CTreat successful compilation as complete system validation.
  4. DTest against explicit requirements using measurements, simulation, analysis, or reproducible experiments appropriate to the system.
Show answer
Answer: D. Test against explicit requirements using measurements, simulation, analysis, or reproducible experiments appropriate to the system.Discrete Structures → Discrete Probability → Discrete Probability Concepts: Test against explicit requirements using measurements, simulation, analysis, or reproducible experiments appropriate to the system.
Report a mistake

Q7. When a problem involving Discrete Probability Concepts occurs, what should be done first? Context: BS Computer Engineering / Discrete Structures / Discrete Probability.

  1. AIgnore measurements because troubleshooting should rely on intuition.
  2. BEstablish the symptoms and scope, collect measurements or traces, then isolate likely causes systematically.
  3. CReplace several components before collecting evidence.
  4. DAssume the first suspected cause is correct.
Show answer
Answer: B. Establish the symptoms and scope, collect measurements or traces, then isolate likely causes systematically.Discrete Structures → Discrete Probability → Discrete Probability Concepts: Establish the symptoms and scope, collect measurements or traces, then isolate likely causes systematically.
Report a mistake

Q8. Which evidence best supports a performance assessment involving Discrete Probability Concepts? Context: BS Computer Engineering / Discrete Structures / Discrete Probability.

  1. AUse an unrelated metric because it is easy to measure.
  2. BReport a single number without operating conditions.
  3. CAssume theoretical peak performance equals sustained system performance.
  4. DUse relevant measured or simulated metrics tied to requirements, under clearly stated operating conditions.
Show answer
Answer: D. Use relevant measured or simulated metrics tied to requirements, under clearly stated operating conditions.Discrete Structures → Discrete Probability → Discrete Probability Concepts: Use relevant measured or simulated metrics tied to requirements, under clearly stated operating conditions.
Report a mistake

Q9. Which trade-off should be considered when selecting an approach to Discrete Probability Concepts? Context: BS Computer Engineering / Discrete Structures / Discrete Probability.

  1. AImplementation complexity has no effect on reliability or schedule.
  2. BBalance performance with power, cost, area, latency, reliability, maintainability, and implementation complexity.
  3. COnly maximum speed matters in every design.
  4. DPower and cost never affect architecture decisions.
Show answer
Answer: B. Balance performance with power, cost, area, latency, reliability, maintainability, and implementation complexity.Discrete Structures → Discrete Probability → Discrete Probability Concepts: Balance performance with power, cost, area, latency, reliability, maintainability, and implementation complexity.
Report a mistake

Q10. Which example best represents disciplined engineering practice involving Discrete Probability Concepts? Context: BS Computer Engineering / Discrete Structures / Discrete Probability.

  1. AMake undocumented hardware changes during testing.
  2. BModify multiple interfaces simultaneously without isolation.
  3. CUse personal preference instead of requirements and evidence.
  4. DDocument requirements and assumptions, use controlled design changes, verify interfaces, and retain test evidence.
Show answer
Answer: D. Document requirements and assumptions, use controlled design changes, verify interfaces, and retain test evidence.Discrete Structures → Discrete Probability → Discrete Probability Concepts: Document requirements and assumptions, use controlled design changes, verify interfaces, and retain test evidence.
Report a mistake

Q11. Which statement best describes Discrete Probability Principles within Discrete Probability? Context: BS Computer Engineering / Discrete Structures / Discrete Probability.

  1. AIt is only a naming convention with no effect on system behavior.
  2. BIt guarantees correct operation without considering interfaces.
  3. CIt can be evaluated without knowing any constraints or operating conditions.
  4. DIt should be understood through its governing principles, interfaces, constraints, inputs, outputs, and role in the overall system.
Show answer
Answer: D. It should be understood through its governing principles, interfaces, constraints, inputs, outputs, and role in the overall system.Discrete Structures → Discrete Probability → Discrete Probability Principles: It should be understood through its governing principles, interfaces, constraints, inputs, outputs, and role in the overall system.
Report a mistake

Q12. What is the primary engineering purpose of Discrete Probability Principles? Context: BS Computer Engineering / Discrete Structures / Discrete Probability.

  1. AIt guarantees maximum performance regardless of power or cost.
  2. BIt supports a defined hardware, software, signal, control, or system objective while satisfying engineering constraints.
  3. CIts sole purpose is to maximize component count.
  4. DIt removes the need for requirements and verification.
Show answer
Answer: B. It supports a defined hardware, software, signal, control, or system objective while satisfying engineering constraints.Discrete Structures → Discrete Probability → Discrete Probability Principles: It supports a defined hardware, software, signal, control, or system objective while satisfying engineering constraints.
Report a mistake

Q13. A computer-engineering team is working with Discrete Probability Principles. Which approach is most appropriate? Context: BS Computer Engineering / Discrete Structures / Discrete Probability.

  1. ASelect components before defining requirements.
  2. BIgnore hardware-software interfaces because they are independent.
  3. CSkip verification once the design compiles or powers on.
  4. DDefine requirements and interfaces, analyze constraints, implement the selected approach, and verify the resulting behavior.
Show answer
Answer: D. Define requirements and interfaces, analyze constraints, implement the selected approach, and verify the resulting behavior.Discrete Structures → Discrete Probability → Discrete Probability Principles: Define requirements and interfaces, analyze constraints, implement the selected approach, and verify the resulting behavior.
Report a mistake

Q14. Which principle best supports correct analysis of Discrete Probability Principles? Context: BS Computer Engineering / Discrete Structures / Discrete Probability.

  1. AChoose the result that looks familiar instead of validating the model.
  2. BUse an appropriate model, identify assumptions and boundary conditions, and apply the relevant engineering relationships consistently.
  3. CUse equations without checking their assumptions.
  4. DIgnore units and boundary conditions when calculations appear reasonable.
Show answer
Answer: B. Use an appropriate model, identify assumptions and boundary conditions, and apply the relevant engineering relationships consistently.Discrete Structures → Discrete Probability → Discrete Probability Principles: Use an appropriate model, identify assumptions and boundary conditions, and apply the relevant engineering relationships consistently.
Report a mistake

Q15. Which consideration is most important when designing a solution involving Discrete Probability Principles? Context: BS Computer Engineering / Discrete Structures / Discrete Probability.

  1. AAlways maximize clock rate regardless of power and reliability.
  2. BIgnore interfaces if each component works independently.
  3. CChoose the most complex architecture even when requirements are simple.
  4. DBalance functional requirements with timing, power, cost, reliability, complexity, safety, and interface constraints.
Show answer
Answer: D. Balance functional requirements with timing, power, cost, reliability, complexity, safety, and interface constraints.Discrete Structures → Discrete Probability → Discrete Probability Principles: Balance functional requirements with timing, power, cost, reliability, complexity, safety, and interface constraints.
Report a mistake

Q16. How should an engineer verify work involving Discrete Probability Principles? Context: BS Computer Engineering / Discrete Structures / Discrete Probability.

  1. ATreat successful compilation as complete system validation.
  2. BTest against explicit requirements using measurements, simulation, analysis, or reproducible experiments appropriate to the system.
  3. CAssume simulation alone proves every physical implementation.
  4. DTest only the easiest operating condition.
Show answer
Answer: B. Test against explicit requirements using measurements, simulation, analysis, or reproducible experiments appropriate to the system.Discrete Structures → Discrete Probability → Discrete Probability Principles: Test against explicit requirements using measurements, simulation, analysis, or reproducible experiments appropriate to the system.
Report a mistake

Q17. When a problem involving Discrete Probability Principles occurs, what should be done first? Context: BS Computer Engineering / Discrete Structures / Discrete Probability.

  1. AReplace several components before collecting evidence.
  2. BAssume the first suspected cause is correct.
  3. CIgnore measurements because troubleshooting should rely on intuition.
  4. DEstablish the symptoms and scope, collect measurements or traces, then isolate likely causes systematically.
Show answer
Answer: D. Establish the symptoms and scope, collect measurements or traces, then isolate likely causes systematically.Discrete Structures → Discrete Probability → Discrete Probability Principles: Establish the symptoms and scope, collect measurements or traces, then isolate likely causes systematically.
Report a mistake

Q18. Which evidence best supports a performance assessment involving Discrete Probability Principles? Context: BS Computer Engineering / Discrete Structures / Discrete Probability.

  1. AAssume theoretical peak performance equals sustained system performance.
  2. BUse relevant measured or simulated metrics tied to requirements, under clearly stated operating conditions.
  3. CUse an unrelated metric because it is easy to measure.
  4. DReport a single number without operating conditions.
Show answer
Answer: B. Use relevant measured or simulated metrics tied to requirements, under clearly stated operating conditions.Discrete Structures → Discrete Probability → Discrete Probability Principles: Use relevant measured or simulated metrics tied to requirements, under clearly stated operating conditions.
Report a mistake

Q19. Which trade-off should be considered when selecting an approach to Discrete Probability Principles? Context: BS Computer Engineering / Discrete Structures / Discrete Probability.

  1. AOnly maximum speed matters in every design.
  2. BPower and cost never affect architecture decisions.
  3. CImplementation complexity has no effect on reliability or schedule.
  4. DBalance performance with power, cost, area, latency, reliability, maintainability, and implementation complexity.
Show answer
Answer: D. Balance performance with power, cost, area, latency, reliability, maintainability, and implementation complexity.Discrete Structures → Discrete Probability → Discrete Probability Principles: Balance performance with power, cost, area, latency, reliability, maintainability, and implementation complexity.
Report a mistake

Q20. Which example best represents disciplined engineering practice involving Discrete Probability Principles? Context: BS Computer Engineering / Discrete Structures / Discrete Probability.

  1. AUse personal preference instead of requirements and evidence.
  2. BDocument requirements and assumptions, use controlled design changes, verify interfaces, and retain test evidence.
  3. CMake undocumented hardware changes during testing.
  4. DModify multiple interfaces simultaneously without isolation.
Show answer
Answer: B. Document requirements and assumptions, use controlled design changes, verify interfaces, and retain test evidence.Discrete Structures → Discrete Probability → Discrete Probability Principles: Document requirements and assumptions, use controlled design changes, verify interfaces, and retain test evidence.
Report a mistake

Q21. Which statement best describes Discrete Probability Analysis within Discrete Probability? Context: BS Computer Engineering / Discrete Structures / Discrete Probability.

  1. AIt can be evaluated without knowing any constraints or operating conditions.
  2. BIt should be understood through its governing principles, interfaces, constraints, inputs, outputs, and role in the overall system.
  3. CIt is only a naming convention with no effect on system behavior.
  4. DIt guarantees correct operation without considering interfaces.
Show answer
Answer: B. It should be understood through its governing principles, interfaces, constraints, inputs, outputs, and role in the overall system.Discrete Structures → Discrete Probability → Discrete Probability Analysis: It should be understood through its governing principles, interfaces, constraints, inputs, outputs, and role in the overall system.
Report a mistake

Q22. What is the primary engineering purpose of Discrete Probability Analysis? Context: BS Computer Engineering / Discrete Structures / Discrete Probability.

  1. AIts sole purpose is to maximize component count.
  2. BIt removes the need for requirements and verification.
  3. CIt guarantees maximum performance regardless of power or cost.
  4. DIt supports a defined hardware, software, signal, control, or system objective while satisfying engineering constraints.
Show answer
Answer: D. It supports a defined hardware, software, signal, control, or system objective while satisfying engineering constraints.Discrete Structures → Discrete Probability → Discrete Probability Analysis: It supports a defined hardware, software, signal, control, or system objective while satisfying engineering constraints.
Report a mistake

Q23. A computer-engineering team is working with Discrete Probability Analysis. Which approach is most appropriate? Context: BS Computer Engineering / Discrete Structures / Discrete Probability.

  1. ASkip verification once the design compiles or powers on.
  2. BDefine requirements and interfaces, analyze constraints, implement the selected approach, and verify the resulting behavior.
  3. CSelect components before defining requirements.
  4. DIgnore hardware-software interfaces because they are independent.
Show answer
Answer: B. Define requirements and interfaces, analyze constraints, implement the selected approach, and verify the resulting behavior.Discrete Structures → Discrete Probability → Discrete Probability Analysis: Define requirements and interfaces, analyze constraints, implement the selected approach, and verify the resulting behavior.
Report a mistake

Q24. Which principle best supports correct analysis of Discrete Probability Analysis? Context: BS Computer Engineering / Discrete Structures / Discrete Probability.

  1. AUse equations without checking their assumptions.
  2. BIgnore units and boundary conditions when calculations appear reasonable.
  3. CChoose the result that looks familiar instead of validating the model.
  4. DUse an appropriate model, identify assumptions and boundary conditions, and apply the relevant engineering relationships consistently.
Show answer
Answer: D. Use an appropriate model, identify assumptions and boundary conditions, and apply the relevant engineering relationships consistently.Discrete Structures → Discrete Probability → Discrete Probability Analysis: Use an appropriate model, identify assumptions and boundary conditions, and apply the relevant engineering relationships consistently.
Report a mistake

Q25. Which consideration is most important when designing a solution involving Discrete Probability Analysis? Context: BS Computer Engineering / Discrete Structures / Discrete Probability.

  1. AChoose the most complex architecture even when requirements are simple.
  2. BBalance functional requirements with timing, power, cost, reliability, complexity, safety, and interface constraints.
  3. CAlways maximize clock rate regardless of power and reliability.
  4. DIgnore interfaces if each component works independently.
Show answer
Answer: B. Balance functional requirements with timing, power, cost, reliability, complexity, safety, and interface constraints.Discrete Structures → Discrete Probability → Discrete Probability Analysis: Balance functional requirements with timing, power, cost, reliability, complexity, safety, and interface constraints.
Report a mistake

Q26. How should an engineer verify work involving Discrete Probability Analysis? Context: BS Computer Engineering / Discrete Structures / Discrete Probability.

  1. AAssume simulation alone proves every physical implementation.
  2. BTest only the easiest operating condition.
  3. CTreat successful compilation as complete system validation.
  4. DTest against explicit requirements using measurements, simulation, analysis, or reproducible experiments appropriate to the system.
Show answer
Answer: D. Test against explicit requirements using measurements, simulation, analysis, or reproducible experiments appropriate to the system.Discrete Structures → Discrete Probability → Discrete Probability Analysis: Test against explicit requirements using measurements, simulation, analysis, or reproducible experiments appropriate to the system.
Report a mistake

Q27. When a problem involving Discrete Probability Analysis occurs, what should be done first? Context: BS Computer Engineering / Discrete Structures / Discrete Probability.

  1. AIgnore measurements because troubleshooting should rely on intuition.
  2. BEstablish the symptoms and scope, collect measurements or traces, then isolate likely causes systematically.
  3. CReplace several components before collecting evidence.
  4. DAssume the first suspected cause is correct.
Show answer
Answer: B. Establish the symptoms and scope, collect measurements or traces, then isolate likely causes systematically.Discrete Structures → Discrete Probability → Discrete Probability Analysis: Establish the symptoms and scope, collect measurements or traces, then isolate likely causes systematically.
Report a mistake

Q28. Which evidence best supports a performance assessment involving Discrete Probability Analysis? Context: BS Computer Engineering / Discrete Structures / Discrete Probability.

  1. AUse an unrelated metric because it is easy to measure.
  2. BReport a single number without operating conditions.
  3. CAssume theoretical peak performance equals sustained system performance.
  4. DUse relevant measured or simulated metrics tied to requirements, under clearly stated operating conditions.
Show answer
Answer: D. Use relevant measured or simulated metrics tied to requirements, under clearly stated operating conditions.Discrete Structures → Discrete Probability → Discrete Probability Analysis: Use relevant measured or simulated metrics tied to requirements, under clearly stated operating conditions.
Report a mistake

Q29. Which trade-off should be considered when selecting an approach to Discrete Probability Analysis? Context: BS Computer Engineering / Discrete Structures / Discrete Probability.

  1. AImplementation complexity has no effect on reliability or schedule.
  2. BBalance performance with power, cost, area, latency, reliability, maintainability, and implementation complexity.
  3. COnly maximum speed matters in every design.
  4. DPower and cost never affect architecture decisions.
Show answer
Answer: B. Balance performance with power, cost, area, latency, reliability, maintainability, and implementation complexity.Discrete Structures → Discrete Probability → Discrete Probability Analysis: Balance performance with power, cost, area, latency, reliability, maintainability, and implementation complexity.
Report a mistake

Q30. Which example best represents disciplined engineering practice involving Discrete Probability Analysis? Context: BS Computer Engineering / Discrete Structures / Discrete Probability.

  1. AMake undocumented hardware changes during testing.
  2. BModify multiple interfaces simultaneously without isolation.
  3. CUse personal preference instead of requirements and evidence.
  4. DDocument requirements and assumptions, use controlled design changes, verify interfaces, and retain test evidence.
Show answer
Answer: D. Document requirements and assumptions, use controlled design changes, verify interfaces, and retain test evidence.Discrete Structures → Discrete Probability → Discrete Probability Analysis: Document requirements and assumptions, use controlled design changes, verify interfaces, and retain test evidence.
Report a mistake

Q31. Which statement best describes Discrete Probability Design within Discrete Probability? Context: BS Computer Engineering / Discrete Structures / Discrete Probability.

  1. AIt is only a naming convention with no effect on system behavior.
  2. BIt guarantees correct operation without considering interfaces.
  3. CIt can be evaluated without knowing any constraints or operating conditions.
  4. DIt should be understood through its governing principles, interfaces, constraints, inputs, outputs, and role in the overall system.
Show answer
Answer: D. It should be understood through its governing principles, interfaces, constraints, inputs, outputs, and role in the overall system.Discrete Structures → Discrete Probability → Discrete Probability Design: It should be understood through its governing principles, interfaces, constraints, inputs, outputs, and role in the overall system.
Report a mistake

Q32. What is the primary engineering purpose of Discrete Probability Design? Context: BS Computer Engineering / Discrete Structures / Discrete Probability.

  1. AIt guarantees maximum performance regardless of power or cost.
  2. BIt supports a defined hardware, software, signal, control, or system objective while satisfying engineering constraints.
  3. CIts sole purpose is to maximize component count.
  4. DIt removes the need for requirements and verification.
Show answer
Answer: B. It supports a defined hardware, software, signal, control, or system objective while satisfying engineering constraints.Discrete Structures → Discrete Probability → Discrete Probability Design: It supports a defined hardware, software, signal, control, or system objective while satisfying engineering constraints.
Report a mistake

Q33. A computer-engineering team is working with Discrete Probability Design. Which approach is most appropriate? Context: BS Computer Engineering / Discrete Structures / Discrete Probability.

  1. ASelect components before defining requirements.
  2. BIgnore hardware-software interfaces because they are independent.
  3. CSkip verification once the design compiles or powers on.
  4. DDefine requirements and interfaces, analyze constraints, implement the selected approach, and verify the resulting behavior.
Show answer
Answer: D. Define requirements and interfaces, analyze constraints, implement the selected approach, and verify the resulting behavior.Discrete Structures → Discrete Probability → Discrete Probability Design: Define requirements and interfaces, analyze constraints, implement the selected approach, and verify the resulting behavior.
Report a mistake

Q34. Which principle best supports correct analysis of Discrete Probability Design? Context: BS Computer Engineering / Discrete Structures / Discrete Probability.

  1. AChoose the result that looks familiar instead of validating the model.
  2. BUse an appropriate model, identify assumptions and boundary conditions, and apply the relevant engineering relationships consistently.
  3. CUse equations without checking their assumptions.
  4. DIgnore units and boundary conditions when calculations appear reasonable.
Show answer
Answer: B. Use an appropriate model, identify assumptions and boundary conditions, and apply the relevant engineering relationships consistently.Discrete Structures → Discrete Probability → Discrete Probability Design: Use an appropriate model, identify assumptions and boundary conditions, and apply the relevant engineering relationships consistently.
Report a mistake

Q35. Which consideration is most important when designing a solution involving Discrete Probability Design? Context: BS Computer Engineering / Discrete Structures / Discrete Probability.

  1. AAlways maximize clock rate regardless of power and reliability.
  2. BIgnore interfaces if each component works independently.
  3. CChoose the most complex architecture even when requirements are simple.
  4. DBalance functional requirements with timing, power, cost, reliability, complexity, safety, and interface constraints.
Show answer
Answer: D. Balance functional requirements with timing, power, cost, reliability, complexity, safety, and interface constraints.Discrete Structures → Discrete Probability → Discrete Probability Design: Balance functional requirements with timing, power, cost, reliability, complexity, safety, and interface constraints.
Report a mistake

Q36. How should an engineer verify work involving Discrete Probability Design? Context: BS Computer Engineering / Discrete Structures / Discrete Probability.

  1. ATreat successful compilation as complete system validation.
  2. BTest against explicit requirements using measurements, simulation, analysis, or reproducible experiments appropriate to the system.
  3. CAssume simulation alone proves every physical implementation.
  4. DTest only the easiest operating condition.
Show answer
Answer: B. Test against explicit requirements using measurements, simulation, analysis, or reproducible experiments appropriate to the system.Discrete Structures → Discrete Probability → Discrete Probability Design: Test against explicit requirements using measurements, simulation, analysis, or reproducible experiments appropriate to the system.
Report a mistake

Q37. When a problem involving Discrete Probability Design occurs, what should be done first? Context: BS Computer Engineering / Discrete Structures / Discrete Probability.

  1. AReplace several components before collecting evidence.
  2. BAssume the first suspected cause is correct.
  3. CIgnore measurements because troubleshooting should rely on intuition.
  4. DEstablish the symptoms and scope, collect measurements or traces, then isolate likely causes systematically.
Show answer
Answer: D. Establish the symptoms and scope, collect measurements or traces, then isolate likely causes systematically.Discrete Structures → Discrete Probability → Discrete Probability Design: Establish the symptoms and scope, collect measurements or traces, then isolate likely causes systematically.
Report a mistake

Q38. Which evidence best supports a performance assessment involving Discrete Probability Design? Context: BS Computer Engineering / Discrete Structures / Discrete Probability.

  1. AAssume theoretical peak performance equals sustained system performance.
  2. BUse relevant measured or simulated metrics tied to requirements, under clearly stated operating conditions.
  3. CUse an unrelated metric because it is easy to measure.
  4. DReport a single number without operating conditions.
Show answer
Answer: B. Use relevant measured or simulated metrics tied to requirements, under clearly stated operating conditions.Discrete Structures → Discrete Probability → Discrete Probability Design: Use relevant measured or simulated metrics tied to requirements, under clearly stated operating conditions.
Report a mistake

Q39. Which trade-off should be considered when selecting an approach to Discrete Probability Design? Context: BS Computer Engineering / Discrete Structures / Discrete Probability.

  1. AOnly maximum speed matters in every design.
  2. BPower and cost never affect architecture decisions.
  3. CImplementation complexity has no effect on reliability or schedule.
  4. DBalance performance with power, cost, area, latency, reliability, maintainability, and implementation complexity.
Show answer
Answer: D. Balance performance with power, cost, area, latency, reliability, maintainability, and implementation complexity.Discrete Structures → Discrete Probability → Discrete Probability Design: Balance performance with power, cost, area, latency, reliability, maintainability, and implementation complexity.
Report a mistake

Q40. Which example best represents disciplined engineering practice involving Discrete Probability Design? Context: BS Computer Engineering / Discrete Structures / Discrete Probability.

  1. AUse personal preference instead of requirements and evidence.
  2. BDocument requirements and assumptions, use controlled design changes, verify interfaces, and retain test evidence.
  3. CMake undocumented hardware changes during testing.
  4. DModify multiple interfaces simultaneously without isolation.
Show answer
Answer: B. Document requirements and assumptions, use controlled design changes, verify interfaces, and retain test evidence.Discrete Structures → Discrete Probability → Discrete Probability Design: Document requirements and assumptions, use controlled design changes, verify interfaces, and retain test evidence.
Report a mistake

Q41. Which statement best describes Discrete Probability Applications within Discrete Probability? Context: BS Computer Engineering / Discrete Structures / Discrete Probability.

  1. AIt can be evaluated without knowing any constraints or operating conditions.
  2. BIt should be understood through its governing principles, interfaces, constraints, inputs, outputs, and role in the overall system.
  3. CIt is only a naming convention with no effect on system behavior.
  4. DIt guarantees correct operation without considering interfaces.
Show answer
Answer: B. It should be understood through its governing principles, interfaces, constraints, inputs, outputs, and role in the overall system.Discrete Structures → Discrete Probability → Discrete Probability Applications: It should be understood through its governing principles, interfaces, constraints, inputs, outputs, and role in the overall system.
Report a mistake

Q42. What is the primary engineering purpose of Discrete Probability Applications? Context: BS Computer Engineering / Discrete Structures / Discrete Probability.

  1. AIts sole purpose is to maximize component count.
  2. BIt removes the need for requirements and verification.
  3. CIt guarantees maximum performance regardless of power or cost.
  4. DIt supports a defined hardware, software, signal, control, or system objective while satisfying engineering constraints.
Show answer
Answer: D. It supports a defined hardware, software, signal, control, or system objective while satisfying engineering constraints.Discrete Structures → Discrete Probability → Discrete Probability Applications: It supports a defined hardware, software, signal, control, or system objective while satisfying engineering constraints.
Report a mistake

Q43. A computer-engineering team is working with Discrete Probability Applications. Which approach is most appropriate? Context: BS Computer Engineering / Discrete Structures / Discrete Probability.

  1. ASkip verification once the design compiles or powers on.
  2. BDefine requirements and interfaces, analyze constraints, implement the selected approach, and verify the resulting behavior.
  3. CSelect components before defining requirements.
  4. DIgnore hardware-software interfaces because they are independent.
Show answer
Answer: B. Define requirements and interfaces, analyze constraints, implement the selected approach, and verify the resulting behavior.Discrete Structures → Discrete Probability → Discrete Probability Applications: Define requirements and interfaces, analyze constraints, implement the selected approach, and verify the resulting behavior.
Report a mistake

Q44. Which principle best supports correct analysis of Discrete Probability Applications? Context: BS Computer Engineering / Discrete Structures / Discrete Probability.

  1. AUse equations without checking their assumptions.
  2. BIgnore units and boundary conditions when calculations appear reasonable.
  3. CChoose the result that looks familiar instead of validating the model.
  4. DUse an appropriate model, identify assumptions and boundary conditions, and apply the relevant engineering relationships consistently.
Show answer
Answer: D. Use an appropriate model, identify assumptions and boundary conditions, and apply the relevant engineering relationships consistently.Discrete Structures → Discrete Probability → Discrete Probability Applications: Use an appropriate model, identify assumptions and boundary conditions, and apply the relevant engineering relationships consistently.
Report a mistake

Q45. Which consideration is most important when designing a solution involving Discrete Probability Applications? Context: BS Computer Engineering / Discrete Structures / Discrete Probability.

  1. AChoose the most complex architecture even when requirements are simple.
  2. BBalance functional requirements with timing, power, cost, reliability, complexity, safety, and interface constraints.
  3. CAlways maximize clock rate regardless of power and reliability.
  4. DIgnore interfaces if each component works independently.
Show answer
Answer: B. Balance functional requirements with timing, power, cost, reliability, complexity, safety, and interface constraints.Discrete Structures → Discrete Probability → Discrete Probability Applications: Balance functional requirements with timing, power, cost, reliability, complexity, safety, and interface constraints.
Report a mistake

Q46. How should an engineer verify work involving Discrete Probability Applications? Context: BS Computer Engineering / Discrete Structures / Discrete Probability.

  1. AAssume simulation alone proves every physical implementation.
  2. BTest only the easiest operating condition.
  3. CTreat successful compilation as complete system validation.
  4. DTest against explicit requirements using measurements, simulation, analysis, or reproducible experiments appropriate to the system.
Show answer
Answer: D. Test against explicit requirements using measurements, simulation, analysis, or reproducible experiments appropriate to the system.Discrete Structures → Discrete Probability → Discrete Probability Applications: Test against explicit requirements using measurements, simulation, analysis, or reproducible experiments appropriate to the system.
Report a mistake

Q47. When a problem involving Discrete Probability Applications occurs, what should be done first? Context: BS Computer Engineering / Discrete Structures / Discrete Probability.

  1. AIgnore measurements because troubleshooting should rely on intuition.
  2. BEstablish the symptoms and scope, collect measurements or traces, then isolate likely causes systematically.
  3. CReplace several components before collecting evidence.
  4. DAssume the first suspected cause is correct.
Show answer
Answer: B. Establish the symptoms and scope, collect measurements or traces, then isolate likely causes systematically.Discrete Structures → Discrete Probability → Discrete Probability Applications: Establish the symptoms and scope, collect measurements or traces, then isolate likely causes systematically.
Report a mistake

Q48. Which evidence best supports a performance assessment involving Discrete Probability Applications? Context: BS Computer Engineering / Discrete Structures / Discrete Probability.

  1. AUse an unrelated metric because it is easy to measure.
  2. BReport a single number without operating conditions.
  3. CAssume theoretical peak performance equals sustained system performance.
  4. DUse relevant measured or simulated metrics tied to requirements, under clearly stated operating conditions.
Show answer
Answer: D. Use relevant measured or simulated metrics tied to requirements, under clearly stated operating conditions.Discrete Structures → Discrete Probability → Discrete Probability Applications: Use relevant measured or simulated metrics tied to requirements, under clearly stated operating conditions.
Report a mistake

Q49. Which trade-off should be considered when selecting an approach to Discrete Probability Applications? Context: BS Computer Engineering / Discrete Structures / Discrete Probability.

  1. AImplementation complexity has no effect on reliability or schedule.
  2. BBalance performance with power, cost, area, latency, reliability, maintainability, and implementation complexity.
  3. COnly maximum speed matters in every design.
  4. DPower and cost never affect architecture decisions.
Show answer
Answer: B. Balance performance with power, cost, area, latency, reliability, maintainability, and implementation complexity.Discrete Structures → Discrete Probability → Discrete Probability Applications: Balance performance with power, cost, area, latency, reliability, maintainability, and implementation complexity.
Report a mistake

Q50. Which example best represents disciplined engineering practice involving Discrete Probability Applications? Context: BS Computer Engineering / Discrete Structures / Discrete Probability.

  1. AMake undocumented hardware changes during testing.
  2. BModify multiple interfaces simultaneously without isolation.
  3. CUse personal preference instead of requirements and evidence.
  4. DDocument requirements and assumptions, use controlled design changes, verify interfaces, and retain test evidence.
Show answer
Answer: D. Document requirements and assumptions, use controlled design changes, verify interfaces, and retain test evidence.Discrete Structures → Discrete Probability → Discrete Probability Applications: Document requirements and assumptions, use controlled design changes, verify interfaces, and retain test evidence.
Report a mistake