Asking and checking if the answer is correct
Congrats on getting something like this working! I obviously don't know anything about the background of the project, so keep in mind that while my feedback may be valuable, if it's just a small side project you might not want to overengineer it.
Regardless, here are some points for you to regard:

External scripts: While embedding scripts into the document directly is a slight performance gain, using an external script gives you the luxury of

Mixed languages: While mostly an oddity while reading, it's generally a bad user experience to have two languages mixed together. For concistency in terms of UX, I'd advise that you stick to either one.

Reducing duplicated code: When writing code, it's always nice that if you have to change something, you only have to change it in one place, instead of multiple. This makes your code less error prone to spontaneous changes made by you. Considering this, we could refactor the following:


let input = document.querySelector('input');
if (input.value === '17') {
    input.style.backgroundColor = 'green';
    document.querySelector('#A2').innerHTML = 'Правильно';
} else {
    input.style.backgroundColor = 'red';
    document.querySelector('#A2').innerHTML = 'Неправильно';
}

... into ...
const input = document.querySelector('input');
const answer = document.querySelector('#A2');

if (input.value === '17') {
    input.style.backgroundColor = 'green';
    answer.innerHTML = 'Правильно';
} else {
    input.style.backgroundColor = 'red';
    answer.innerHTML = 'Неправильно';
}


HTML cleanup: If you need to query the document to fetch elements, it's always good to be as explicit as possible. On one line you are querying for input, but what if the page contains multiple input elements later? You should try to get a consistent and explicit HTML structure going for the questions/answers (which also ties in with the point made later on below). An example could be this:

&lt;article id=&quot;q1&quot; class=&quot;question&quot;&gt;
    &lt;hr&gt;
    &lt;h3&gt;...&lt;/h3&gt;
    &lt;input type=&quot;text&quot;&gt;&lt;/input&gt;
    &lt;button class=&quot;check&quot;&gt;Check&lt;/button&gt;
    &lt;p class=&quot;answer&quot;&gt;...&lt;/p&gt;
&lt;/article&gt;

Each of the elements in this node can be uniquely identified simply by the fact that they are a child of the unique(!) question element with the ID &quot;q1&quot;. Queries that looked for input before would now look for #q1 &gt; input instead.
You could also try to remove redundant classes, unless they are used for styling. In the first question, there is one button with the &quot;correct&quot; class, with all others being &quot;incorrect&quot;. But the fact that every button that is not explicitely &quot;correct&quot; should be incorrect should be natural, hence you could consider removing these excessive classes.

The points mentioned above will probably increase the overall readability and maintainability of the project, but the biggest concern currently is the extendibility.
Look at it this way: Currently, every time you want to add a new question to the quiz, you need to modify your source code, mostly adding duplicated statements to check correct/incorrect answers. If you give your questions a more concrete structure, you could write reusable code, that is valid for any question that you add!
The exact implementation for this is up to you, but it could help to generate an object from an HTML node, grabbing the question title, description, answering possibilities (and the correct one obviously!) and setting up the question/answer handling.
Always remember: It's almost always better to have something that is extendible and/or scalable without having to modify the source code, just by modifying the markup or configuration.