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

Questions 6–10

1. 6expert · hard

   A static analysis tool reports a violation of a MISRA-C:2012 rule that is classified as 'undecidable'. The tool's output includes a confidence level of 50%. The team is under time pressure to release. The tester must decide how to handle the finding. What is the most appropriate action?

   • ADisable the rule in the tool configuration to avoid future false positives.
   • BPerform a manual review of the code to determine if the violation is real, and document the outcome.
   • CAsk the developer to rewrite the code to avoid the rule, regardless of the finding's validity.
   • DMark the finding as a false positive and close it, since the tool is not certain.
   Reveal Solution Discussion Select an answer first
2. 7foundation · easy

   When interpreting the output of a static analysis tool for MISRA-C:2012, what should a tester do with a reported violation?

   • AAutomatically accept all reports as true violations and fix them.
   • BReview the violation to determine if it is a true positive or a false positive.
   • CRun the tool again with different settings until the violation disappears.
   • DIgnore the reports and rely on manual code review only.
   Reveal Solution Discussion Select an answer first
4. 8foundation · easy

   What is the primary purpose of the MISRA-C:2012 guidelines in the context of automotive software development?

   • ATo provide a formal specification for the C programming language that compilers must implement to be certified for automotive use.
   • BTo define the functional safety requirements for automotive electronic control units (ECUs).
   • CTo replace the C language with a safer alternative for all automotive software development.
   • DTo define a set of coding standards that help avoid undefined, unspecified, and implementation-defined behavior in C code, thereby improving safety and reliability.
   Reveal Solution Discussion Select an answer first
5. 9foundation · easy

   How is the MISRA-C:2012 document structured?

   • AIt is organized by severity level, with each rule assigned to a specific safety integrity level.
   • BIt is divided into two main parts: directives and rules, with rules further categorized by topic.
   • CIt is a single list of numbered rules without any further categorization.
   • DIt is structured as a set of chapters, each corresponding to a different programming language feature.
   Reveal Solution Discussion Select an answer first
6. 10foundation · easy

   What is the purpose of documenting a deviation from a MISRA-C:2012 rule?

   • ATo provide a formal record of why the deviation is necessary and how the risk is mitigated.
   • BTo allow developers to bypass rules without any oversight.
   • CTo provide a way to ignore rules that are inconvenient.
   • DTo track how many rules are violated in the codebase.
   Reveal Solution Discussion Select an answer first