The MISRA-C: 2012 Guidelines CT-AUT Practice Questions (Page 6)

Questions 26–30

1. 26expert · hard · select all that apply

   A project is implementing MISRA-C:2012 compliance. The team has a deviation process in place. Which of the following are essential elements of a valid deviation record? (Select all that apply.)

   • AA risk assessment showing the deviation is acceptable.
   • BThe compiler version used to build the code.
   • CA unique identifier for the deviation.
   • DA technical justification for why the rule cannot be followed.
   • EThe name of the developer who wrote the code.
   Check answers Discussion Select an answer first
2. 27foundation · easy

   Which of the following is a common MISRA-C:2012 violation?

   • ADeclaring a variable with a descriptive name.
   • BUsing comments to explain complex logic.
   • CUsing a for loop to iterate over an array.
   • DUsing a variable before it has been initialized.
   Reveal Solution Discussion Select an answer first
4. 28foundation · easy

   In which context are the MISRA-C:2012 guidelines most appropriately applied?

   • AFor C code used in safety-related systems, particularly in the automotive industry, but also applicable to other safety-critical domains.
   • BFor any C code, regardless of the application domain, as a general style guide.
   • COnly for code that is compiled with a specific certified compiler.
   • DOnly for code written in the C++ programming language.
   Reveal Solution Discussion Select an answer first
5. 29foundation · easy

   In MISRA-C:2012, what is the difference between a decidable and an undecidable rule?

   • ADecidable rules are only found in the appendix, while undecidable rules are in the main body.
   • BDecidable rules are mandatory, while undecidable rules are advisory.
   • CDecidable rules can be checked automatically by static analysis, while undecidable rules require human judgment.
   • DDecidable rules apply to the compiler, while undecidable rules apply to the source code.
   Reveal Solution Discussion Select an answer first
6. 30application · medium

   A static analysis tool reports a MISRA-C:2012 violation in a legacy module. The developer argues that the tool is wrong because the rule is 'undecidable' and cannot be checked automatically. The tester needs to respond appropriately. What should the tester do?

   • AImmediately escalate the issue to the safety manager, as any tool finding indicates a safety-critical defect.
   • BAccept the developer's argument and close the finding without further action.
   • CReview the tool's documentation to understand the rule's decidable status and the basis for the finding, then manually verify if needed.
   • DAsk the developer to rewrite the code to avoid the rule, regardless of the rule's decidable status.
   Reveal Solution Discussion Select an answer first