A company is developing software for a brake-by-wire system. They have a tight schedule and want to reduce testing time while ensuring that the generated code is correct. Which approach is most effective?

Use manual code inspection instead of dynamic testing

Use back-to-back testing to compare model and code, then perform integration testing

Skip back-to-back testing and rely on unit testing of the code

Perform only integration testing without model-code comparison

In back-to-back testing, how are discrepancies between model and code outputs typically evaluated?

By manually inspecting the code to see if it matches the model.

By comparing the outputs against predefined tolerance limits.

By running the model and code on different test cases and comparing the results.

By checking if the code compiles without errors.

What is the primary purpose of back-to-back testing in automotive software development?

To verify that the generated code behaves consistently with the simulation model from which it was derived.

To validate that the software meets all customer requirements and functional specifications.

To check the code for compliance with coding standards and static analysis rules.

To test the software on the target hardware to verify performance and timing constraints.

How does back-to-back testing compare the behavior of a simulation model with the behavior of the generated code?

By comparing the model's documentation with the code's comments.

By running the model in real-time on the target hardware and observing its behavior.

By reviewing the code line-by-line against the model's block diagram.

By running the same test cases on both the model and the code and comparing the outputs.

Where in the automotive software test process is back-to-back testing typically performed?

During system integration testing, to verify the entire vehicle system.

During maintenance, to check for regressions after a software update.

After code generation, to verify that the generated code matches the model.

Before model creation, to validate the requirements.

Certified Tester Automotive Software Tester

Domain 4Objective 3

Back-to-Back-Testing CT-AUT Practice Questions (Page 3)

Part of the Automotive-specific static and dynamic test techniques domain, which makes up ~20% of our current practice bank. ISTQB does not publish an official question count, but from its 60-minute exam (~25–40 total, ~5–8 in this domain), expect 1–1 from this objective — we provide 18 practice questions to prepare you well beyond it. (estimate)

18questions here

4free pages

5concepts

Questions 11–15

11expert · hard
A company is developing software for a brake-by-wire system. They have a tight schedule and want to reduce testing time while ensuring that the generated code is correct. Which approach is most effective?
Select an answer first
12foundation · easy
In back-to-back testing, how are discrepancies between model and code outputs typically evaluated?
Select an answer first
13foundation · easy
What is the primary purpose of back-to-back testing in automotive software development?
Select an answer first
14foundation · easy
How does back-to-back testing compare the behavior of a simulation model with the behavior of the generated code?
Select an answer first
15foundation · easy
Where in the automotive software test process is back-to-back testing typically performed?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to CT-AUT

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by ISTQB. “CT-AUT” is a trademark of its owner, used for identification only.