Ugh. I hate questionnaires like this. Question 5 is misleading because in conflates different types of aliasing. Please forget that question and the stated true answer.

For the others, you seem to have bad intuition about how code behaves in multiple languages.

• Question 2 is False because that's an array of pointers not numbers.
• Question 8 is valid C pointer arithmetic and assigns 20 to the variable a through it's reference.
• Question 9: the code tells you what it does, I have no idea why you thought it would print Error here.

My guess is that you do not have a strong internal model of what programming languages do when presented with weird or unnatural code. This is typically a sign that you only learnt programming as a way to express "sane" programs, but never had to deal with edge cases in the languages themselves.

You're not alone in that. I've had a discussion with several senior coders about whether x is guaranteed to be initialised in the following example, and we had to resort to the C++ standard to settle it. (I leave the answer for the peanut gallery to find):

class A {
  struct B {
    uint32_t x;
  };
  B b[5];
  public: A() {}
}
A* a = new A();

In any case, unless you specifically want to get into compilers, language design or code reviews and auditing, I wouldn't take the results of this test seriously. If you still want to get a better intuition about what languages do, you'll have to get into the mindset of not guessing what something will do, but to actually check with the language specification, and to explore the myriad of weird things that happen if you do that. Maybe watch the wat video as a starting point.