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

Questions 11–15

1. 11foundation · easy

   What do 'environment' rules in MISRA-C:2012 primarily address?

   • AThe development environment, such as the IDE used.
   • BThe interaction between the C code and the compiler or runtime environment.
   • CThe physical environment in which the vehicle operates.
   • DThe testing environment, such as the hardware-in-the-loop setup.
   Reveal Solution Discussion Select an answer first
2. 12foundation · easy

   What is a typical element of a MISRA-C:2012 deviation record?

   • AThe name of the developer who wrote the code.
   • BThe number of lines of code in the file.
   • CThe rationale for the deviation and the risk assessment.
   • DThe compiler version used to build the code.
   Reveal Solution Discussion Select an answer first
4. 13foundation · easy

   Which of the following is a main rule category in MISRA-C:2012?

   • ARules for the linker script.
   • BRules for the C preprocessor.
   • CRules for the debugger configuration.
   • DRules for the operating system interface.
   Reveal Solution Discussion Select an answer first
5. 14foundation · easy

   What is the potential impact of a MISRA-C:2012 violation that involves an implicit type conversion?

   • AIt is only a style issue and does not affect behavior.
   • BIt can lead to unexpected behavior due to loss of precision or sign changes.
   • CIt has no impact on safety or reliability.
   • DIt only affects the performance of the code, not its correctness.
   Reveal Solution Discussion Select an answer first
6. 15application · medium

   A static analysis tool reports a violation of a MISRA-C:2012 rule that is classified as 'undecidable'. The tester needs to determine if the violation is real. What is the most appropriate action?

   • AAsk the developer to rewrite the code to avoid the rule, regardless of the finding's validity.
   • BTrust the tool's output, as static analysis tools are designed to be accurate.
   • CDisable the rule in the tool configuration to avoid false positives.
   • DManually review the code to verify the violation, using the tool's output as a hint.
   Reveal Solution Discussion Select an answer first