Пример запроса (первая клетка). System одинаковый во всех запросах прогона, user — свой вопрос для каждой клетки:
| Клетка | Тема | Утверждение | Ответ |
Результат | Обоснование |
T01-L1 2.3 c | Syntax and operators | Double-quoted and single-quoted strings are processed identically; the difference is only in speed. | «no» Пояснение: Single-quoted strings are not processed identically to double-quoted strings, as the latter supports variable interpolation and escape sequences while the former generally does not.
Raw{"answer": "no", "explanation": "Single-quoted strings are not processed identically to double-quoted strings, as the latter supports variable interpolation and escape sequences while the former generally does not."} | верно | В двойных кавычках работают интерполяция переменных и escape-последовательности, в одинарных — нет. |
T01-L2 0.42 c | Syntax and operators | The ?? operator follows isset semantics and raises no warnings for undefined variables. | «yes» Пояснение: The null coalescing operator (??) is designed to avoid undefined variable warnings by checking if a variable is defined and not null, returning the right operand otherwise.
Raw{"answer": "yes", "explanation": "The null coalescing operator (??) is designed to avoid undefined variable warnings by checking if a variable is defined and not null, returning the right operand otherwise."} | верно | ?? работает по семантике isset — несуществующие переменные и ключи допустимы. |
T01-L3 0.28 c | Syntax and operators | What will this print: echo 'a', 'b'; | «ab» Пояснение: The comma operator concatenates the two string arguments, producing 'ab'.
Raw{"answer": "ab", "explanation": "The comma operator concatenates the two string arguments, producing 'ab'."} | верно | echo принимает список аргументов: ab. |
T01-L4 0.43 c | Syntax and operators | print returns the value 1 and can be used inside an expression. | «no» Пояснение: The print statement in PHP returns the value 1, but it is a language construct (a statement) rather than a function, so it cannot be used directly inside expressions.
Raw{"answer": "no", "explanation": "The print statement in PHP returns the value 1, but it is a language construct (a statement) rather than a function, so it cannot be used directly inside expressions."} | неверно верный: «yes» | print — выражение со значением 1, в отличие от echo, который значения не возвращает. |
T01-L5 0.37 c | Syntax and operators | The ?: (elvis) operator returns its left operand when it is falsy. | «no» Пояснение: The Elvis operator returns its right operand when the left operand is falsy, and returns the left operand itself when it is truthy.
Raw{"answer": "no", "explanation": "The Elvis operator returns its right operand when the left operand is falsy, and returns the left operand itself when it is truthy."} | верно | Наоборот: $a ?: $b возвращает $a, если он истинный, иначе $b. |
T01-L6 0.42 c | Syntax and operators | In PHP 8, the concatenation operator (.) has lower precedence than addition and subtraction. | «no» Пояснение: In PHP, the concatenation operator (.) has lower precedence than the arithmetic operators like addition and subtraction, so the statement is true.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "In PHP, the concatenation operator (.) has lower precedence than the arithmetic operators like addition and subtraction, so the statement is true." ⏎ } | неверно верный: «yes» | С PHP 8 (RFC concat precedence) '.' имеет приоритет ниже арифметики: 'сумма: ' . 2 + 3 → 'сумма: 5' (в PHP 7 было иначе). |
T01-L7 0.66 c | Syntax and operators | The expression 2 ** 3 ** 2 in PHP evaluates as (2 ** 3) ** 2, that is, 64. | «no» Пояснение: In PHP, the exponentiation operator is right-associative, so 2 ** 3 ** 2 is evaluated as 2 ** (3 ** 2), which equals 2 ** 9, or 512, not 64.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "In PHP, the exponentiation operator is right-associative, so 2 ** 3 ** 2 is evaluated as 2 ** (3 ** 2), which equals 2 ** 9, or 512, not 64." ⏎ } ⏎ ``` | верно | ** право-ассоциативен: 2 ** (3 ** 2) = 2 ** 9 = 512. |
T01-L8 0.64 c | Syntax and operators | What string will this print: echo 'sum: ' . 2 + 3; (PHP 8)? | «sum: 3» Пояснение: Due to operator precedence, the concatenation operator (.) binds tighter than the addition operator (+), so PHP evaluates it as ('sum: ' . 2) + 3, which converts 'sum: 2' to 0, resulting in 3.
Raw{"answer": "sum: 3", "explanation": "Due to operator precedence, the concatenation operator (.) binds tighter than the addition operator (+), so PHP evaluates it as ('sum: ' . 2) + 3, which converts 'sum: 2' to 0, resulting in 3."} | неверно верный: «sum: 5» | Парная к verify-клетке про приоритет: 'сумма: 5'. |
T02-L1 0.39 c | Types and comparisons | With strict comparison (===), arrays are considered equal regardless of element order. | «no» Пояснение: Strict comparison of arrays requires identical keys and values in the same order.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "Strict comparison of arrays requires identical keys and values in the same order." ⏎ } ⏎ ``` | верно | === для массивов требует совпадения и значений, и их порядка. |
T02-L2 0.38 c | Types and comparisons | The comparison 0 == false returns false because it is a strict comparison. | «no» Пояснение: The equality operator (==) performs a loose comparison, so 0 == false returns true, not false.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "The equality operator (==) performs a loose comparison, so 0 == false returns true, not false." ⏎ } | верно | Наоборот: == — нестрогое сравнение и возвращает true; строгое — это === (0 === false → false). |
T02-L3 0.38 c | Types and comparisons | In PHP 8, the expression "abc" == 0 returns true. | «yes» Пояснение: In PHP 8, non-numeric strings are converted to 0 in loose equality comparisons, so "abc" == 0 returns true.
Raw{"answer": "yes", "explanation": "In PHP 8, non-numeric strings are converted to 0 in loose equality comparisons, so \"abc\" == 0 returns true."} | неверно верный: «no» | С PHP 8 нечисловая строка сравнивается как строка: "abc" == "0" → false (в PHP 7 было true). |
T02-L4 0.42 c | Types and comparisons | Under loose comparison, null equals 0, the empty string, and false at the same time. | «yes» Пояснение: In PHP, the loose equality operator (==) returns true when null is compared to 0, '', or false because they are all considered equivalent in this context.
Raw{"answer": "yes", "explanation": "In PHP, the loose equality operator (==) returns true when null is compared to 0, '', or false because they are all considered equivalent in this context."} | верно | null == 0, null == "" и null == false — все true. |
T02-L5 0.45 c | Types and comparisons | What does the expression (int) '42abc' return? | «42» Пояснение: In PHP, casting the string '42abc' to int extracts the leading numeric part '42' before the first non-numeric character.
Raw{ ⏎ "answer": 42, ⏎ "explanation": "In PHP, casting the string '42abc' to int extracts the leading numeric part '42' before the first non-numeric character." ⏎ } | верно | Ведущая числовая часть: 42, без ошибок и warning. |
T02-L6 0.41 c | Types and comparisons | What does the expression '5' + 5 return? | «10» Пояснение: PHP coerces the string '5' to the integer 5 and adds 5, resulting in 10.
Raw{ ⏎ "answer": 10, ⏎ "explanation": "PHP coerces the string '5' to the integer 5 and adds 5, resulting in 10." ⏎ } | верно | Числовая строка приводится: int 10. |
T02-L7 0.44 c | Types and comparisons | When cast to string, false becomes "0". | «yes» Пояснение: In PHP, the boolean value false is explicitly cast to the integer 0, and then to the string "0" when converted to a string.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "In PHP, the boolean value false is explicitly cast to the integer 0, and then to the string \"0\" when converted to a string." ⏎ } | неверно верный: «no» | false → "", true → "1". |
T02-L8 0.61 c | Types and comparisons | The comparison 0.1 + 0.2 === 0.3 returns false. | «yes» Пояснение: Due to floating-point precision issues, 0.1 + 0.2 results in 0.30000000000000004, so the strict comparison with 0.3 is false.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Due to floating-point precision issues, 0.1 + 0.2 results in 0.30000000000000004, so the strict comparison with 0.3 is false." ⏎ } | верно | Двоичная погрешность float: 0.1 + 0.2 = 0.30000000000000004. |
T03-L1 0.41 c | Strings | strrev() correctly reverses a UTF-8 string. | «no» Пояснение: strrev() operates on bytes, so it corrupts multi-byte UTF-8 characters by reversing their byte sequences instead of the logical characters.
Raw{"answer": "no", "explanation": "strrev() operates on bytes, so it corrupts multi-byte UTF-8 characters by reversing their byte sequences instead of the logical characters."} | верно | strrev переворачивает байты и ломает многобайтовые последовательности. |
T03-L2 0.35 c | Strings | str_contains('Hello world', 'world') returns true. | «yes» Пояснение: The str_contains function correctly returns true because the substring 'world' is present within the string 'Hello world'.
Raw{"answer": "yes", "explanation": "The str_contains function correctly returns true because the substring 'world' is present within the string 'Hello world'."} | верно | str_contains с PHP 8.0 проверяет вхождение подстроки. |
T03-L3 0.32 c | Strings | str_pad() can pad a string on the right side only. | «no» Пояснение: str_pad() can pad a string on either the right or the left side using its second parameter.
Raw{"answer": "no", "explanation": "str_pad() can pad a string on either the right or the left side using its second parameter."} | верно | STR_PAD_LEFT / STR_PAD_BOTH меняют сторону дополнения. |
T03-L4 0.4 c | Strings | By default trim() strips only spaces, leaving tabs and newlines intact. | «yes» Пояснение: The default character set for trim() is indeed only the space character, meaning it does not remove other whitespace like tabs or newlines without explicitly specifying them.
Raw{"answer": "yes", "explanation": "The default character set for trim() is indeed only the space character, meaning it does not remove other whitespace like tabs or newlines without explicitly specifying them."} | неверно верный: «no» | Список символов по умолчанию: « \t\n\r\0\x0B» — пробелы, табы, переводы строк, возврат каретки, null-байт, вертикальный таб. Проверено php -r. |
T03-L5 0.5 c | Strings | How many BYTES does strlen('héllo') return for a UTF-8 string? | «6» Пояснение: The character 'h', 'l', 'l', 'o' are each 1 byte (4 bytes), and 'é' in UTF-8 is encoded as 2 bytes, totaling 6 bytes.
Raw{"answer": 6, "explanation": "The character 'h', 'l', 'l', 'o' are each 1 byte (4 bytes), and 'é' in UTF-8 is encoded as 2 bytes, totaling 6 bytes."} | верно | 6 букв по 2 байта: 12. |
T03-L6 0.36 c | Strings | What does substr('abcdef', -3) return? | «def» Пояснение: The second argument -3 starts the substring 3 characters from the end of the string 'abcdef'.
Raw{"answer": "def", "explanation": "The second argument -3 starts the substring 3 characters from the end of the string 'abcdef'."} | верно | Отрицательное смещение — с конца: def. |
T03-L7 0.36 c | Strings | ucfirst() modifies the string passed to it in place. | «no» Пояснение: ucfirst() returns a modified copy of the string and does not modify the original variable in place.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "ucfirst() returns a modified copy of the string and does not modify the original variable in place." ⏎ } | верно | Строки неизменяемы; ucfirst возвращает новую строку. |
T03-L8 0.33 c | Strings | Variable interpolation works in heredoc but not in nowdoc. | «yes» Пояснение: Variable interpolation occurs in heredoc syntax, but not in nowdoc syntax.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Variable interpolation occurs in heredoc syntax, but not in nowdoc syntax." ⏎ } | верно | Nowdoc — «одинарные кавычки» в тройном синтаксисе: текст как есть. |
T04-L1 0.47 c | Arrays | The sort() function preserves the key-to-value association of the array. | «no» Пояснение: The sort() function reindexes the array keys from 0 to n-1, so it does not preserve the original key-to-value associations (as ksort() and uasort() do).
Raw{"answer": "no", "explanation": "The sort() function reindexes the array keys from 0 to n-1, so it does not preserve the original key-to-value associations (as ksort() and uasort() do)."} | верно | sort перенумеровывает ключи; связь сохраняет asort. |
T04-L2 0.36 c | Arrays | The string key '5' in an array is stored as the integer 5. | «yes» Пояснение: In PHP, numeric strings that can be cast to integers or floats are automatically converted to their numeric counterparts when used as array keys.
Raw{"answer": "yes", "explanation": "In PHP, numeric strings that can be cast to integers or floats are automatically converted to their numeric counterparts when used as array keys."} | верно | Каноничные десятичные строковые ключи приводятся к int. |
T04-L3 0.4 c | Arrays | The in_array() function uses strict comparison (===) by default. | «no» Пояснение: The third parameter $strict in in_array() defaults to false, meaning it uses a loose comparison (==) by default.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "The third parameter $strict in in_array() defaults to false, meaning it uses a loose comparison (==) by default." ⏎ } | верно | По умолчанию сравнение нестрогое; строгое — третий аргумент true. |
T04-L4 0.39 c | Arrays | Without a callback, array_filter() removes all "empty" (falsy) elements from the array. | «yes» Пояснение: By default, array_filter() removes elements where the value is considered falsy, such as 0, '0', '', null, or false.
Raw{"answer": "yes", "explanation": "By default, array_filter() removes elements where the value is considered falsy, such as 0, '0', '', null, or false."} | верно | Убирает 0, "", null, false и пустые массивы. |
T04-L5 0.36 c | Arrays | By default, array_slice() preserves the original numeric keys of the array. | «yes» Пояснение: By default, the preserve_keys argument is set to true, which means array_slice() preserves the original numeric keys of the array.
Raw{"answer": "yes", "explanation": "By default, the preserve_keys argument is set to true, which means array_slice() preserves the original numeric keys of the array."} | неверно верный: «no» | По умолчанию ключи перенумеровываются; сохранение — preserve_keys = true. |
T04-L6 0.57 c | Arrays | What does array_slice([10, 20, 30, 40], 1, 2) return? | «[20, 30]» Пояснение: array_slice starts at index 1 and takes 2 elements from the array [10, 20, 30, 40], resulting in [20, 30].
Raw{ ⏎ "answer": "[20, 30]", ⏎ "explanation": "array_slice starts at index 1 and takes 2 elements from the array [10, 20, 30, 40], resulting in [20, 30]." ⏎ } | верно | [20,30]; ключи перенумеровываются. |
T04-L7 0.52 c | Arrays | How many elements will count(['a' => 1] + ['a' => 9, 'b' => 2]) return? | «2» Пояснение: The '+' operator on arrays keeps elements from the left array for duplicate keys, so the result is ['a' => 1, 'b' => 2] which has 2 elements.
Raw{"answer": 2, "explanation": "The '+' operator on arrays keeps elements from the left array for duplicate keys, so the result is ['a' => 1, 'b' => 2] which has 2 elements."} | верно | Оператор + : по ключу 'a' побеждает левый; итого 2. |
T04-L8 0.43 c | Arrays | Since PHP 8.1, the spread operator [...$a, ...$b] supports arrays with string keys. | «yes» Пояснение: The spread operator in PHP 8.1 and later supports arrays with string keys, merging them and overwriting duplicates with the later array's values.
Raw{"answer": "yes", "explanation": "The spread operator in PHP 8.1 and later supports arrays with string keys, merging them and overwriting duplicates with the later array's values."} | верно | В 8.0 — только числовые ключи; 8.1 снял ограничение. |
T05-L1 0.36 c | Functions and closures | Named arguments cannot be combined with argument unpacking ...$args in a single call. | «no» Пояснение: In PHP, it is possible to combine named arguments and argument unpacking in the same function call.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "In PHP, it is possible to combine named arguments and argument unpacking in the same function call." ⏎ } | верно | Можно: f(...$args, имя: значение). Нельзя только позиционный аргумент после распаковки. |
T05-L2 0.47 c | Functions and closures | An anonymous function without use sees variables from the outer scope. | «no» Пояснение: Anonymous functions (closures) in PHP do not automatically have access to the outer scope's variables unless explicitly passed using the 'use' keyword.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "Anonymous functions (closures) in PHP do not automatically have access to the outer scope's variables unless explicitly passed using the 'use' keyword." ⏎ } ⏎ ``` | верно | Без use внешние переменные недоступны; авто-захват только у fn. |
T05-L3 0.44 c | Functions and closures | What will func_num_args() return inside function f($a) { return func_num_args(); } when called as f(1, 2, 3)? | «3» Пояснение: func_num_args() counts the number of arguments passed to a function, ignoring $a because it is an argument name, not a variable in scope.
Raw```json ⏎ {"answer": 3, "explanation": "func_num_args() counts the number of arguments passed to a function, ignoring $a because it is an argument name, not a variable in scope."} ⏎ ``` | верно | Считает переданные аргументы: 3. |
T05-L4 0.41 c | Functions and closures | The body of an arrow function fn may consist of several expressions in curly braces. | «yes» Пояснение: PHP arrow functions can contain a compound statement body enclosed in curly braces, allowing for multiple expressions or control structures.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "PHP arrow functions can contain a compound statement body enclosed in curly braces, allowing for multiple expressions or control structures." ⏎ } | неверно верный: «no» | fn — всегда одно выражение; блок операторов делает обычная анонимная функция. |
T05-L5 0.5 c | Functions and closures | An arrow function fn captures outer variables by reference (lazily, at use time). | «no» Пояснение: In PHP, arrow functions (the `fn` syntax introduced in PHP 8.0) capture outer variables by value, not by reference, and they do not use the `$this` variable of the enclosing scope.
Raw{"answer": "no", "explanation": "In PHP, arrow functions (the `fn` syntax introduced in PHP 8.0) capture outer variables by value, not by reference, and they do not use the `$this` variable of the enclosing scope."} | верно | fn захватывает только по значению, автоматически; по ссылке — только &$var в use у обычной функции (fn так не умеет). |
T05-L6 0.39 c | Functions and closures | A closure declared as static function () {} does not capture $this. | «yes» Пояснение: In PHP, static functions and static closures do not have access to the instance scope ($this).
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "In PHP, static functions and static closures do not have access to the instance scope ($this)." ⏎ } | верно | static-замыкание отвязано от объекта: $this внутри недоступен. |
T05-L7 0.39 c | Functions and closures | What will this print: $x = 5; $f = function () use ($x) { return $x; }; $x = 7; echo $f(); | «5» Пояснение: The closure captures $x by value at the time of creation, so it returns 5 even though $x was later changed to 7.
Raw{"answer": 5, "explanation": "The closure captures $x by value at the time of creation, so it returns 5 even though $x was later changed to 7."} | верно | use захватывает по значению в момент создания: 5. |
T05-L8 0.52 c | Functions and closures | In weak typing mode (without strict_types), passing the string "5" to an int parameter is allowed. | «yes» Пояснение: In weak typing mode, PHP allows type coercion, so the string '5' can be implicitly converted to an integer when passed to an int parameter.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "In weak typing mode, PHP allows type coercion, so the string '5' can be implicitly converted to an integer when passed to an int parameter." ⏎ } ⏎ ``` | верно | Coercive typing приводит "5" к 5; strict_types=1 требует точного типа. |
T06-L1 0.36 c | OOP: classes and inheritance | PHP supports constructor property promotion: public function __construct(private int $x) {}. | «yes» Пояснение: PHP 8.0 introduced constructor property promotion, which automatically creates a property when declared in the constructor signature.
Raw{"answer": "yes", "explanation": "PHP 8.0 introduced constructor property promotion, which automatically creates a property when declared in the constructor signature."} | верно | С PHP 8.0 параметр с модификатором создаёт свойство и присваивание. |
T06-L2 0.39 c | OOP: classes and inheritance | Which keyword prevents a method from being overridden in subclasses? | «final» Пояснение: In PHP, the 'final' keyword can be used before a class or method to prevent it from being inherited or overridden.
Raw{ ⏎ "answer": "final", ⏎ "explanation": "In PHP, the 'final' keyword can be used before a class or method to prevent it from being inherited or overridden." ⏎ } | верно | final. |
T06-L3 0.25 c | OOP: classes and inheritance | A method declared final cannot be overridden in a subclass. | «yes» Пояснение: A final method in PHP cannot be overridden by a subclass.
Raw{"answer": "yes", "explanation": "A final method in PHP cannot be overridden by a subclass."} | верно | final запрещает переопределение метода и наследование класса. |
T06-L4 0.3 c | OOP: classes and inheritance | Parent properties with private visibility are accessible in a subclass. | «no» Пояснение: Private properties are only accessible within the class they are declared in, not in subclasses.
Raw{"answer": "no", "explanation": "Private properties are only accessible within the class they are declared in, not in subclasses."} | верно | В подклассе видны protected и public; private — только внутри своего класса. |
T06-L5 0.42 c | OOP: classes and inheritance | What does get_class(new class {}) return? Answer with the part of the name before the NUL byte (without the file path). | «stdclass» Пояснение: Creating an anonymous class in PHP without a name defaults to the stdClass class, and get_class returns the class name as a string.
Raw{ ⏎ "answer": "stdClass", ⏎ "explanation": "Creating an anonymous class in PHP without a name defaults to the stdClass class, and get_class returns the class name as a string." ⏎ } | неверно верный: «class@anonymous» | get_class анонимного класса печатает class@anonymous\0<файл>:<строка>$n; короткая форма — часть до NUL-байта. Проверено php -r (hex). |
T06-L6 0.53 c | OOP: classes and inheritance | A private parent method is not part of the inheritance contract: a child may declare a method with the same name and any visibility. | «yes» Пояснение: Because private methods are not part of the public inheritance contract, a child class can declare a method with the same name without it overriding the parent's private method and with any visibility.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Because private methods are not part of the public inheritance contract, a child class can declare a method with the same name without it overriding the parent's private method and with any visibility." ⏎ } | верно | private-члены не наследуются — правила совместимости подписей не действуют. |
T06-L7 0.5 c | OOP: classes and inheritance | The magic method __get() is called only for non-existent properties. | «no» Пояснение: The magic method __get() is called when reading a property that is inaccessible (i.e., it does not exist or is inaccessible due to visibility), not just when it simply does not exist.
Raw{"answer": "no", "explanation": "The magic method __get() is called when reading a property that is inaccessible (i.e., it does not exist or is inaccessible due to visibility), not just when it simply does not exist."} | верно | __get срабатывает и для существующих, но недоступных (private/protected извне). |
T06-L8 0.58 c | OOP: classes and inheritance | What does reassigning a readonly property throw — Exception or Error? | «error» Пояснение: In PHP 8.1+, attempting to write to a readonly property throws a readonly property modification Error (a subclass of Error, specifically an "Error" type as in "Error: Cannot modify readonly property..."), rather than an Exception.
Raw{ ⏎ "answer": "Error", ⏎ "explanation": "In PHP 8.1+, attempting to write to a readonly property throws a readonly property modification Error (a subclass of Error, specifically an \"Error\" type as in \"Error: Cannot modify readonly property...\"), rather than an Exception." ⏎ } | верно | Error (readonly с 8.1); оговорка: в __clone() переинициализация допустима (8.3+). |
T07-L1 0.3 c | Interfaces, traits, enum | An interface can declare constants. | «yes» Пояснение: PHP interfaces can declare constants, which are implicitly public and immutable.
Raw{"answer": "yes", "explanation": "PHP interfaces can declare constants, which are implicitly public and immutable."} | верно | Константы интерфейса наследуются реализациями. |
T07-L2 0.37 c | Interfaces, traits, enum | Which operator checks whether an object is an instance of a class or interface? | «instanceof» Пояснение: The 'instanceof' operator checks whether an object is an instance of a class or interface.
Raw{ ⏎ "answer": "instanceof", ⏎ "explanation": "The 'instanceof' operator checks whether an object is an instance of a class or interface." ⏎ } | верно | instanceof. |
T07-L3 0.34 c | Interfaces, traits, enum | An interface can declare static methods. | «yes» Пояснение: PHP interfaces can declare static methods, though they do not have to be implemented in the same way as abstract classes.
Raw{"answer": "yes", "explanation": "PHP interfaces can declare static methods, though they do not have to be implemented in the same way as abstract classes."} | верно | Реализация обязана дать статический метод с той же сигнатурой. |
T07-L4 0.33 c | Interfaces, traits, enum | The instanceof operator only checks class inheritance: it ignores interfaces. | «no» Пояснение: The instanceof operator also returns true if the object is an instance of any of the interfaces implemented by its class.
Raw{"answer": "no", "explanation": "The instanceof operator also returns true if the object is an instance of any of the interfaces implemented by its class."} | верно | instanceof возвращает true и для интерфейсов объекта. |
T07-L5 0.33 c | Interfaces, traits, enum | An interface method may have a default implementation, like a trait method. | «no» Пояснение: In PHP, interface methods must be declared without a body (unimplemented), whereas traits can have default implementations.
Raw{"answer": "false", "explanation": "In PHP, interface methods must be declared without a body (unimplemented), whereas traits can have default implementations."} | верно | Методы интерфейса — только сигнатуры; тело даёт реализующий класс. |
T07-L6 0.29 c | Interfaces, traits, enum | An abstract method in an abstract class may have protected visibility. | «yes» Пояснение: Abstract methods in PHP can be declared with public or protected visibility, but not private.
Raw{"answer": "yes", "explanation": "Abstract methods in PHP can be declared with public or protected visibility, but not private."} | верно | В абстрактном классе — любая видимость; в интерфейсе — только public. |
T07-L7 0.36 c | Interfaces, traits, enum | How many elements will Foo::cases() return for enum Foo { case A; case B; case C; }? | «3» Пояснение: Foo::cases() returns an array of all enum cases, and the enum defines exactly 3 cases.
Raw{ ⏎ "answer": 3, ⏎ "explanation": "Foo::cases() returns an array of all enum cases, and the enum defines exactly 3 cases." ⏎ } | верно | Статический метод cases(): 3. |
T07-L8 0.4 c | Interfaces, traits, enum | A trait can declare constants. | «yes» Пояснение: Traits in PHP support the declaration of constants, which are accessible to any class that uses the trait.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Traits in PHP support the declaration of constants, which are accessible to any class that uses the trait." ⏎ } | верно | С PHP 8.2 трейты могут объявлять константы (RFC constants_in_traits); до 8.2 — нет. |
T08-L1 0.36 c | Exceptions and errors | The Throwable interface is a common ancestor of both Exception and Error. | «yes» Пояснение: In PHP 8.0 and later, the Throwable interface was introduced as the common ancestor for both Exception and Error classes.
Raw{"answer": "yes", "explanation": "In PHP 8.0 and later, the Throwable interface was introduced as the common ancestor for both Exception and Error classes."} | верно | Иерархия с PHP 7: Throwable → Exception и Throwable → Error. |
T08-L2 0.4 c | Exceptions and errors | A catch (Exception $e) block will also catch TypeError, because TypeError ultimately inherits from Exception. | «yes» Пояснение: In PHP, the built-in TypeError class extends RuntimeException, which in turn extends Exception, so a catch (Exception $e) block will catch TypeError.
Raw{"answer": "yes", "explanation": "In PHP, the built-in TypeError class extends RuntimeException, which in turn extends Exception, so a catch (Exception $e) block will catch TypeError."} | неверно верный: «no» | TypeError наследуется от Error; catch (Exception) его не ловит. |
T08-L3 0.41 c | Exceptions and errors | The @ operator suppresses exceptions too. | «no» Пояснение: The @ operator only suppresses non-fatal notices, warnings, and deprecations, but it does not suppress exceptions or fatal errors.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "The @ operator only suppresses non-fatal notices, warnings, and deprecations, but it does not suppress exceptions or fatal errors." ⏎ } | верно | @ глушит диагностику (warnings/notices), исключения не перехватывает. |
T08-L4 0.37 c | Exceptions and errors | What error class does intdiv(5, 0) throw? | «divisionbyzeroerror» Пояснение: In PHP, the intdiv() function throws a DivisionByZeroError when attempting to divide an integer by zero.
Raw{"answer": "DivisionByZeroError", "explanation": "In PHP, the intdiv() function throws a DivisionByZeroError when attempting to divide an integer by zero."} | верно | DivisionByZeroError (иерархия Error, не Exception); php-грейдер объективен. |
T08-L5 0.29 c | Exceptions and errors | The finally block runs only if the exception was caught by a catch block. | «no» Пояснение: In PHP, a finally block executes regardless of whether an exception was thrown or caught.
Raw{"answer": "no", "explanation": "In PHP, a finally block executes regardless of whether an exception was thrown or caught."} | верно | Наоборот: finally выполняется всегда — даже когда исключение не поймано и уходит выше. Проверено php -r. |
T08-L6 0.32 c | Exceptions and errors | An exception thrown inside a finally block has no effect on the result of the try block. | «no» Пояснение: An exception thrown inside a finally block will propagate and is not suppressed by the try block's result.
Raw{"answer": "false", "explanation": "An exception thrown inside a finally block will propagate and is not suppressed by the try block's result."} | верно | Исключение из finally перекрывает исходное и уходит вместо него. |
T08-L7 0.4 c | Exceptions and errors | What does the expression (bool) new Exception('x') return? | «yes» Пояснение: In PHP, any object instance is truthy when cast to a boolean, so (bool) new Exception('x') evaluates to true (yes).
Raw{"answer": "yes", "explanation": "In PHP, any object instance is truthy when cast to a boolean, so (bool) new Exception('x') evaluates to true (yes)."} | верно | Любой объект при приведении к bool — true. Формы ответа: true или да. |
T08-L8 0.42 c | Exceptions and errors | Functions registered via register_shutdown_function() run when exit is called. | «no» Пояснение: Functions registered via register_shutdown_function() run when the script ends, not specifically when exit() is called, which does not necessarily terminate the script execution in all contexts.
Raw{"answer": "no", "explanation": "Functions registered via register_shutdown_function() run when the script ends, not specifically when exit() is called, which does not necessarily terminate the script execution in all contexts."} | неверно верный: «yes» | exit завершает скрипт, но shutdown-функции отрабатывают. |
T09-L1 0.64 c | Namespaces and autoloading | The use App\Service\Mailer; statement itself loads the class file. | «no» Пояснение: The use statement is a compile-time aliasing directive that simply rebinds the class name, not a runtime autoload trigger; the class file is loaded only when the class is first actually referenced (e.g., instantiated or used) and PHP's autoloader is registered.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "The use statement is a compile-time aliasing directive that simply rebinds the class name, not a runtime autoload trigger; the class file is loaded only when the class is first actually referenced (e.g., instantiated or used) and PHP's autoloader is registered." ⏎ } | верно | use — псевдоним на этапе компиляции; файл грузит автозагрузчик при первом обращении. |
T09-L2 0.4 c | Namespaces and autoloading | What follows use to import a function (not a class): the word function or const? | «function» Пояснение: In PHP, you use `use function` to import a standalone function, while `use const` is used for constants.
Raw{"answer": "function", "explanation": "In PHP, you use `use function` to import a standalone function, while `use const` is used for constants."} | верно | use function ...; (и use const для констант). |
T09-L3 0.56 c | Namespaces and autoloading | Into which file (path from src/) does the PSR-4 mapping "App\ → src/" place the class App\Controller\Api\UserController? | «src/controller/api/usercontroller.php» Пояснение: PSR-4 mapping converts backslashes in the class name to directory separators, placing the fully qualified class App\Controller\Api\UserController into src/Controller/Api/UserController.php.
Raw{ ⏎ "answer": "src/Controller/Api/UserController.php", ⏎ "explanation": "PSR-4 mapping converts backslashes in the class name to directory separators, placing the fully qualified class App\\Controller\\Api\\UserController into src/Controller/Api/UserController.php." ⏎ } | верно | Остаток имени после префикса, \ → /. |
T09-L4 0.44 c | Namespaces and autoloading | Including vendor/autoload.php registers autoloaders via spl_autoload_register(). | «yes» Пояснение: Including vendor/autoload.php typically instantiates a Composer autoloader whose constructor calls spl_autoload_register() to attach the autoload callback to the SPL autoloader.
Raw{"answer": "yes", "explanation": "Including vendor/autoload.php typically instantiates a Composer autoloader whose constructor calls spl_autoload_register() to attach the autoload callback to the SPL autoloader."} | верно | Composer ставит автозагрузчик именно на spl_autoload_register. |
T09-L5 0.34 c | Namespaces and autoloading | The magic constant __NAMESPACE__ contains the name of the current namespace. | «yes» Пояснение: __NAMESPACE__ is a compile-time magic constant that expands to the string of the current namespace in which it is used.
Raw{"answer": "yes", "explanation": "__NAMESPACE__ is a compile-time magic constant that expands to the string of the current namespace in which it is used."} | верно | В корневом пространстве — пустая строка. |
T09-L6 0.5 c | Namespaces and autoloading | An unqualified class name (without a leading \) in new is resolved from the global root. | «yes» Пояснение: In PHP 5.3 and later, unqualified class names within a namespace are resolved by first checking the current namespace, and only falling back to the global root if the class is not found in the current namespace.
Raw{"answer": "yes", "explanation": "In PHP 5.3 and later, unqualified class names within a namespace are resolved by first checking the current namespace, and only falling back to the global root if the class is not found in the current namespace."} | неверно верный: «no» | Резолвится относительно текущего namespace (с учётом импортов). |
T09-L7 0.6 c | Namespaces and autoloading | With the PSR-4 mapping "App\ → src/", the class App\Model\User lives in the file src/Model/User.php. | «yes» Пояснение: Under PSR-4, each backslash in the fully qualified name maps to a directory separator, and the class name is converted to the corresponding file name, so App\Model\User maps to src/Model/User.php.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Under PSR-4, each backslash in the fully qualified name maps to a directory separator, and the class name is converted to the corresponding file name, so App\\Model\\User maps to src/Model/User.php." ⏎ } | верно | Остаток имени после префикса переносится в путь как есть. |
T09-L8 0.46 c | Namespaces and autoloading | A use statement may be written inside a function body — the import then applies to that function only. | «yes» Пояснение: The use statement can be declared inside a function or class method, and the import applies only to the scope where it is declared.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "The use statement can be declared inside a function or class method, and the import applies only to the scope where it is declared." ⏎ } | неверно верный: «no» | use внутри тела функции — parse error; импорты файловые и компиляционные. |
T10-L1 0.44 c | References and scope | Arrays are copied on assignment rather than passed by reference. | «yes» Пояснение: In PHP, arrays are value types, meaning assigning an array to another variable creates a copy of the data rather than creating a reference to the original.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "In PHP, arrays are value types, meaning assigning an array to another variable creates a copy of the data rather than creating a reference to the original." ⏎ } | верно | Присваивание массива — копия (в движке — copy-on-write). |
T10-L2 0.43 c | References and scope | What will this print: $a = [1, 2]; $b = $a; $b[] = 3; echo count($a); | «2» Пояснение: Arrays are passed by value in PHP, so $b is a separate copy and adding 3 to $b does not modify $a.
Raw{ ⏎ "answer": 2, ⏎ "explanation": "Arrays are passed by value in PHP, so $b is a separate copy and adding 3 to $b does not modify $a." ⏎ } | верно | Присваивание — копия: в $a по-прежнему 2 элемента. |
T10-L3 0.49 c | References and scope | Inside a function, user-defined global variables are inaccessible without global, $GLOBALS, or passing them as parameters. | «yes» Пояснение: In PHP, variables declared outside of functions are considered global and must be accessed within a function using the global keyword, the $GLOBALS superglobal array, or by passing them as parameters.
Raw{"answer": "yes", "explanation": "In PHP, variables declared outside of functions are considered global and must be accessed within a function using the global keyword, the $GLOBALS superglobal array, or by passing them as parameters."} | верно | Область видимости функций изолирована; исключение — суперглобалы ($_GET и др.). |
T10-L4 0.47 c | References and scope | unset($GLOBALS['x']) inside a function removes the global variable only for that function. | «no» Пояснение: The $GLOBALS superglobal is a reference to the global scope, so unsetting it from within a function permanently removes the variable from the global scope, not just from the current function's local scope.
Raw{"answer": "no", "explanation": "The $GLOBALS superglobal is a reference to the global scope, so unsetting it from within a function permanently removes the variable from the global scope, not just from the current function's local scope."} | верно | $GLOBALS — прямое окно в глобальную область: unset удалит её по-настоящему. |
T10-L5 0.34 c | References and scope | What will this print: function inc(&$x) { $x++; } $n = 5; inc($n); echo $n; | «6» Пояснение: The function inc modifies $x by reference, incrementing $n from 5 to 6 before echoing it.
Raw{"answer": 6, "explanation": "The function inc modifies $x by reference, incrementing $n from 5 to 6 before echoing it."} | верно | Ссылка меняет оригинал: 6. |
T10-L6 0.44 c | References and scope | A foreach over an array (by value) works with the "live" array: changes to the array inside the loop are visible in the same pass. | «no» Пояснение: In PHP, foreach iterates over a snapshot of the array by default, so modifications to the array during the loop are not visible within that same pass.
Raw{"answer": "no", "explanation": "In PHP, foreach iterates over a snapshot of the array by default, so modifications to the array during the loop are not visible within that same pass."} | верно | По значению foreach итерирует копию-снимок. |
T10-L7 0.44 c | References and scope | A static property belongs to each instance separately: changes in one object are not visible in others. | «no» Пояснение: Static properties belong to the class itself and are shared across all instances, so a change in one object is visible in others.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "Static properties belong to the class itself and are shared across all instances, so a change in one object is visible in others." ⏎ } | верно | Наоборот: статическое свойство общее для всех экземпляров класса. Проверено php -r. |
T10-L8 0.42 c | References and scope | An array can have a boolean key true, and it will be stored as bool. | «no» Пояснение: PHP casts the boolean value true to the integer 1, which then becomes the numeric string '1' when used as an array key.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "PHP casts the boolean value true to the integer 1, which then becomes the numeric string '1' when used as an array key." ⏎ } | верно | Булев ключ приводится к int: true → 1, false → 0. |
T11-L1 0.31 c | Generators, iterators, SPL | Inside a generator, return with a value can be used, and it becomes available via $gen->getReturn(). | «yes» Пояснение: Returning a value from a PHP generator makes it accessible via the Generator::getReturn() method.
Raw{"answer": "yes", "explanation": "Returning a value from a PHP generator makes it accessible via the Generator::getReturn() method."} | верно | return-значение генератора доступно через getReturn() после прохода. |
T11-L2 0.44 c | Generators, iterators, SPL | A fully consumed generator can be rewound with rewind() and traversed again. | «no» Пояснение: In PHP, once a generator is fully consumed, it is considered closed and cannot be rewound; rewind() throws a ValueError if called on a generator after it has been exhausted.
Raw{"answer": "no", "explanation": "In PHP, once a generator is fully consumed, it is considered closed and cannot be rewound; rewind() throws a ValueError if called on a generator after it has been exhausted."} | верно | Генератор одноразовый: rewind после начала итерации бросает Exception. |
T11-L3 0.34 c | Generators, iterators, SPL | The yield from construct delegates traversal to another generator or iterable. | «yes» Пояснение: The yield from construct in PHP delegates the iteration of a generator to another generator or iterable, effectively flattening the result.
Raw{"answer": "yes", "explanation": "The yield from construct in PHP delegates the iteration of a generator to another generator or iterable, effectively flattening the result."} | верно | yield from проксирует значения, ключи и return-значение внутреннего генератора. |
T11-L4 0.53 c | Generators, iterators, SPL | What does get_class(g()) return for function g() { yield 1; }? | «true» Пояснение: Since g() is a generator function, g() creates a Generator object, and get_class() on a Generator object returns the class name "true" (which is PHP's internal representation of a Generator object).
Raw```json ⏎ {"answer": "true", "explanation": "Since g() is a generator function, g() creates a Generator object, and get_class() on a Generator object returns the class name \"true\" (which is PHP's internal representation of a Generator object)."} ⏎ ``` | неверно верный: «generator» | Функция с yield возвращает Generator. |
T11-L5 0.41 c | Generators, iterators, SPL | How many elements will count(iterator_to_array((function () { yield from [1, 2, 3]; })())) return? | «3» Пояснение: iterator_to_array converts the yielded values 1, 2, and 3 into an array, resulting in three elements.
Raw{"answer": 3, "explanation": "iterator_to_array converts the yielded values 1, 2, and 3 into an array, resulting in three elements."} | верно | yield from делегирует все 3 элемента. |
T11-L6 0.44 c | Generators, iterators, SPL | The SplStack class implements a FIFO queue. | «no» Пояснение: The SplStack class implements a LIFO (Last-In, First-Out) stack, while the SplQueue class implements a FIFO queue.
Raw```json ⏎ {"answer": "no", "explanation": "The SplStack class implements a LIFO (Last-In, First-Out) stack, while the SplQueue class implements a FIFO queue."} ⏎ ``` | верно | SplStack — стек LIFO; очередь FIFO — SplQueue. |
T11-L7 0.35 c | Generators, iterators, SPL | ArrayIterator allows wrapping an array and traversing it via the Iterator interface. | «yes» Пояснение: ArrayIterator is a built-in class that implements the Iterator interface, allowing you to wrap an array and iterate over it.
Raw{"answer": "yes", "explanation": "ArrayIterator is a built-in class that implements the Iterator interface, allowing you to wrap an array and iterate over it."} | верно | Объектная обёртка над массивом. |
T11-L8 0.31 c | Generators, iterators, SPL | An ArrayObject instance cannot be traversed with foreach. | «no» Пояснение: ArrayObject inherits from SplObjectStorage and implements Traversable, so it can be used with foreach.
Raw{"answer": "no", "explanation": "ArrayObject inherits from SplObjectStorage and implements Traversable, so it can be used with foreach."} | верно | ArrayObject реализует IteratorAggregate — foreach по нему работает. |
T12-L1 0.32 c | Configuration and security | password_hash() generates a salt automatically — passing one separately is not needed. | «yes» Пояснение: The password_hash() function automatically generates and stores the salt, so providing a separate salt is not required.
Raw{"answer": "yes", "explanation": "The password_hash() function automatically generates and stores the salt, so providing a separate salt is not required."} | верно | Соль встраивается в строку результата; параметр salt устарел. |
T12-L2 0.34 c | Configuration and security | In PHP 8, PASSWORD_DEFAULT is md5 with an automatically added salt. | «no» Пояснение: PASSWORD_DEFAULT is currently bcrypt in PHP 8, not md5 with a salt.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "PASSWORD_DEFAULT is currently bcrypt in PHP 8, not md5 with a salt." ⏎ } | верно | PASSWORD_DEFAULT — bcrypt; md5 для паролей непригоден (перебирается массово). |
T12-L3 0.29 c | Configuration and security | What does password_verify('secret', password_hash('secret', PASSWORD_DEFAULT)) return? | «true» Пояснение: password_verify() returns true when the provided password matches the hash generated by password_hash().
Raw{"answer": true, "explanation": "password_verify() returns true when the provided password matches the hash generated by password_hash()."} | верно | Соль и хеш в одной строке: true (форма ответа: true или да). |
T12-L4 0.29 c | Configuration and security | strip_tags() protects against SQL injection. | «no» Пояснение: strip_tags() removes HTML tags and is used for XSS prevention, not SQL injection.
Raw{"answer": "no", "explanation": "strip_tags() removes HTML tags and is used for XSS prevention, not SQL injection."} | верно | strip_tags режет HTML-теги (помощник против XSS), к параметризации SQL отношения не имеет. |
T12-L5 0.45 c | Configuration and security | session_regenerate_id() is used to protect against session fixation upon user login. | «yes» Пояснение: session_regenerate_id() changes the session ID to make it difficult for an attacker to maintain access to the session, which is a standard method for mitigating session fixation attacks during login.
Raw{"answer": "yes", "explanation": "session_regenerate_id() changes the session ID to make it difficult for an attacker to maintain access to the session, which is a standard method for mitigating session fixation attacks during login."} | верно | Новый ID сессии после логина — стандартная защита от session fixation. |
T12-L6 0.45 c | Configuration and security | Which built-in function returns the SAPI name (e.g., cli)? | «php_sapi_name()» Пояснение: The function php_sapi_name() returns the name of the SAPI (Server Application Programming Interface) being used, such as "cli" or "fpm-fpm".
Raw{"answer":"php_sapi_name()","explanation":"The function php_sapi_name() returns the name of the SAPI (Server Application Programming Interface) being used, such as \"cli\" or \"fpm-fpm\"."} | верно | php_sapi_name(). |
T12-L7 0.49 c | Configuration and security | session_destroy() deletes session data on the server but not the cookie in the user's browser. | «yes» Пояснение: session_destroy() deletes the session data from the server, but it does not send a delete instruction to the client's browser to remove the session cookie, leaving the cookie in the browser intact.
Raw{"answer": "yes", "explanation": "session_destroy() deletes the session data from the server, but it does not send a delete instruction to the client's browser to remove the session cookie, leaving the cookie in the browser intact."} | верно | Удаление cookie — отдельный шаг через setcookie с истёкшим сроком. |
T12-L8 0.41 c | Configuration and security | Without calling session_start(), the $_SESSION array is automatically populated with session data. | «no» Пояснение: The $_SESSION array is empty or undefined until session_start() (or session_start() equivalent) is called to initialize the session.
Raw{ ⏎ "answer": "false", ⏎ "explanation": "The $_SESSION array is empty or undefined until session_start() (or session_start() equivalent) is called to initialize the session." ⏎ } | верно | Без session_start() данные сессии в массив не загружаются ($_SESSION можно заполнить вручную, но привязки к сессии нет). |
VC-L1 0.52 c | PHP 8.4–8.5 | In which PHP version was the array_find() function introduced? | «there is no array_find() function in php» Пояснение: array_find() does not exist in PHP; the closest built-in alternatives are array_search() for value lookup or usort()/array_map() patterns for custom search logic.
Raw{ ⏎ "answer": "There is no array_find() function in PHP", ⏎ "explanation": "array_find() does not exist in PHP; the closest built-in alternatives are array_search() for value lookup or usort()/array_map() patterns for custom search logic." ⏎ } | неверно верный: «8.4» | PHP 8.4 (RFC array_find). |
VC-L2 0.49 c | PHP 8.4–8.5 | Property hooks (get/set right in the property declaration) landed in PHP 8.4. | «yes» Пояснение: PHP 8.4 introduced property hooks, allowing you to define get and set logic directly in the property declaration using the { get } and { set } syntax.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "PHP 8.4 introduced property hooks, allowing you to define get and set logic directly in the property declaration using the { get } and { set } syntax." ⏎ } | верно | Property hooks — PHP 8.4 (ноябрь 2024). |
VC-L3 2.67 c | PHP 8.4–8.5 | Asymmetric visibility (public private(set) string $name) appeared in PHP 8.4. | «no» Пояснение: ' if the statement is true, or 'no' if false. The statement is true, so answer is 'yes'.\n\nCorrection: The question asks if the statement is True or False. The statement \"Asymmetric visibility ... appeared in PHP 8.4\" is a True statement. Therefore, the answer to the question \"True or false?\" is \"yes\" (meaning it is true).\n\nLet me double-check the instruction: \"For a 'True or false?' question, answer is 'yes' or 'no'\". Usually, \"True\" corresponds to \"yes\" and \"False\" to \"no\". Since the statement is true, the answer is yes.
Wait, looking at the previous thought process I was confused. Let's stick to the facts.
Fact: Asymmetric visibility was introduced in PHP 8.4.
Statement: Asymmetric visibility appeared in PHP 8.4.
Is the statement True or False? It is True.
Answer: yes."}
Raw{"answer": "no", "explanation": "Asymmetric visibility (e.g., public private(set) string $name) is a PHP 8.4 feature, so the statement that it appeared in PHP 8.4 is correct; however, the prompt asks "True or false?" regarding the statement that it appeared in 8.4, which is true. Wait, let me re-read: The statement is \"Asymmetric visibility... appeared in PHP 8.4.\" This statement is factually TRUE. So the answer to the True/False question should be 'yes' if the statement is true, or 'no' if false. The statement is true, so answer is 'yes'.\n\nCorrection: The question asks if the statement is True or False. The statement \"Asymmetric visibility ... appeared in PHP 8.4\" is a True statement. Therefore, the answer to the question \"True or false?\" is \"yes\" (meaning it is true).\n\nLet me double-check the instruction: \"For a 'True or false?' question, answer is 'yes' or 'no'\". Usually, \"True\" corresponds to \"yes\" and \"False\" to \"no\". Since the statement is true, the answer is yes. ⏎ ⏎ Wait, looking at the previous thought process I was confused. Let's stick to the facts. ⏎ Fact: Asymmetric visibility was introduced in PHP 8.4. ⏎ Statement: Asymmetric visibility appeared in PHP 8.4. ⏎ Is the statement True or False? It is True. ⏎ Answer: yes."} | неверно верный: «yes» парсинг: текст (фолбэк) | Asymmetric visibility v2 — PHP 8.4. |
VC-L4 0.47 c | PHP 8.4–8.5 | In which PHP version was the #[\NoDiscard] attribute introduced? Answer with the version number. | «8.0» Пояснение: The NoDiscard attribute was introduced in PHP 8.0 to allow developers to mark return values that must be used.
Raw{ ⏎ "answer": "8.0", ⏎ "explanation": "The NoDiscard attribute was introduced in PHP 8.0 to allow developers to mark return values that must be used." ⏎ } | неверно верный: «8.5» | #[\NoDiscard] — PHP 8.5 (marking return values as important). |
VC-L5 0.39 c | PHP 8.4–8.5 | In which PHP version did the pipe operator |> first appear? Answer with the version number. | «8.1» Пояснение: The pipe operator (|>) for the arrow functions was introduced as a PHP 8.1 feature.
Raw{ ⏎ "answer": 8.1, ⏎ "explanation": "The pipe operator (|>) for the arrow functions was introduced as a PHP 8.1 feature." ⏎ } | неверно верный: «8.5» | Pipe operator — PHP 8.5 (2025). |
VC-L6 0.4 c | PHP 8.4–8.5 | In which PHP version did clone-with — the syntax clone($obj, ['x' => 1]) — appear? Answer with the version number. | «8.1» Пояснение: The clone constructor parameter, which allows passing an array of property values to the clone constructor, was introduced in PHP 8.1.
Raw{"answer": "8.1", "explanation": "The clone constructor parameter, which allows passing an array of property values to the clone constructor, was introduced in PHP 8.1."} | неверно верный: «8.5» | Clone with v2 — PHP 8.5. |
VC-L7 0.36 c | PHP 8.4–8.5 | In which PHP version were the array_first() and array_last() functions introduced? | «7.3» Пояснение: The array_first() and array_last() functions were introduced in PHP 7.3.
Raw{"answer": "7.3", "explanation": "The array_first() and array_last() functions were introduced in PHP 7.3."} | неверно верный: «8.5» | PHP 8.5. |
VC-L8 0.34 c | PHP 8.4–8.5 | For which PHP version was RFC Partial Function Application v2 adopted (as of 2026-11-07)? Answer with the version number. | «7.4» Пояснение: RFC Partial Function Application v2 was adopted for PHP 7.4.
Raw```json ⏎ {"answer": "7.4", "explanation": "RFC Partial Function Application v2 was adopted for PHP 7.4."} ⏎ ``` | неверно верный: «8.6» | PFA v2 принят 05.12.2025 (33-0-0), реализован в PHP 8.6. |
VF-L1 0.38 c | PHP: 8.6+ and the future | For which PHP version was the RFC clamp_v2 (the clamp() function) implemented, as of 2026-11-07? Answer with the version number. | «8.0» Пояснение: The PHP RFC clamp_v2, which introduced the clamp() function, was accepted and implemented in PHP 8.0.
Raw{"answer": "8.0", "explanation": "The PHP RFC clamp_v2, which introduced the clamp() function, was accepted and implemented in PHP 8.0."} | неверно верный: «8.6» | По данным владельца (wiki.php.net/rfc): clamp_v2 — 8.6; clamp() в 8.5.11 отсутствует (косвенное подтверждение). Дата-якорь делает клетку монотонной. |
VF-L2 0.64 c | PHP: 8.6+ and the future | RFC Context Managers v2 has already been adopted in PHP (as of 2026-11-07). | «no» Пояснение: ", "explanation": "As of the current date in 2025, the "adopted" status of RFC 8508 for Context Managers is not officially confirmed in PHP 8.3/8.4, and the "v2" version is a hypothetical future specification."}
Raw{"answer": "no", "explanation": "As of the current date in 2025, the "adopted" status of RFC 8508 for Context Managers is not officially confirmed in PHP 8.3/8.4, and the "v2" version is a hypothetical future specification."} | верно парсинг: текст (фолбэк) | На 06.11.2026 — в обсуждении (создан 2026-10-23); не принят. |
VF-L3 0.48 c | PHP: 8.6+ and the future | RFC Bound-Erased Generic Types (generics) was declined in 2026. | «no» Пояснение: RFC Bound-Erased Generic Types was rejected during the PHP 8.4 era (not declined in 2026) and remains not part of PHP's roadmap.
Raw{"answer": "false", "explanation": "RFC Bound-Erased Generic Types was rejected during the PHP 8.4 era (not declined in 2026) and remains not part of PHP's roadmap."} | неверно верный: «yes» | Голосование завершилось 2026-06-28: отклонён (wiki.php.net/rfc). |
VF-L4 0.63 c | PHP: 8.6+ and the future | As of 2026-11-07, the RFC enabling multithreading (ZTS) by default has already been accepted in PHP. | «yes» Пояснение: PHP RFC 9675 (or similar recent proposals) and the broader PHP roadmap have indicated that ZTS will be enabled by default in future PHP versions, with PHP 8.3 already making it more common and PHP 9 expected to make it default by 2026.
Raw{"answer": "yes", "explanation": "PHP RFC 9675 (or similar recent proposals) and the broader PHP roadmap have indicated that ZTS will be enabled by default in future PHP versions, with PHP 8.3 already making it more common and PHP 9 expected to make it default by 2026."} | неверно верный: «no» | Такого принятого RFC нет на дату якоря; якорь делает клетку монотонной — при принятии RFC позже клетка не перевернётся. |
VF-L5 0.37 c | PHP: 8.6+ and the future | As of PHP 8.5, generics (parameterized types) are still absent. | «yes» Пояснение: PHP 8.5 does not include parameterized generics, which remain absent from the language as of that version.
Raw{"answer": "yes", "explanation": "PHP 8.5 does not include parameterized generics, which remain absent from the language as of that version."} | верно | Generics в PHP отсутствуют; отрицательный контроль (не путать с C#/Java). |
VF-L6 0.49 c | PHP: 8.6+ and the future | As of 2026-11-07, the latest stable PHP version is 8.5, and PHP 8.6 has not been released yet (GA — 2026-11-19). | «yes» Пояснение: As of November 2026, the latest stable PHP version is indeed 8.5, while PHP 8.6 was not yet released until later in November 2026.
Raw{"answer": "yes", "explanation": "As of November 2026, the latest stable PHP version is indeed 8.5, while PHP 8.6 was not yet released until later in November 2026."} | верно | 8.5 — релиз осени 2025; 8.6 GA 19.11.2026 (wiki.php.net/todo/php86). Дата снимка — 06.11.2026. |
VF-L7 0.44 c | PHP: 8.6+ and the future | The PHP 6 branch never shipped: after PHP 5.6 came PHP 7.0 directly. | «yes» Пояснение: PHP 6 was canceled to prioritize a major rewrite, and development jumped directly from 5.6 to 7.0.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "PHP 6 was canceled to prioritize a major rewrite, and development jumped directly from 5.6 to 7.0." ⏎ } | верно | Исторический факт: ветка 6 не была релизнута. |
VF-L8 0.39 c | PHP: 8.6+ and the future | The RFC adding the #[\Deprecated] attribute to the core was adopted. | «yes» Пояснение: RFC 9080 for the Deprecated Attribute was adopted and the attribute is available as part of PHP 8.2's core language features.
Raw{"answer": "yes", "explanation": "RFC 9080 for the Deprecated Attribute was adopted and the attribute is available as part of PHP 8.2's core language features."} | верно | #[\Deprecated] — принят, реализован в PHP 8.4. |
T25-L1 0.41 c | Clean architecture | The dependency rule of clean and onion architecture: inner layers know nothing about outer ones — dependencies point toward the center. | «yes» Пояснение: In clean and onion architectures, the dependency rule states that code can only depend inward (toward the core), meaning inner layers are agnostic to outer layers.
Raw{"answer": "yes", "explanation": "In clean and onion architectures, the dependency rule states that code can only depend inward (toward the core), meaning inner layers are agnostic to outer layers."} | верно | Чистая (Robert C. Martin), луковичная (Jeffrey Palermo) и гексагональная (ports & adapters) — варианты одной идеи: зависимости направлены внутрь, к домену. Слоями в проекте следит deptrac. |
T25-L2 0.41 c | Clean architecture | Domain entities import neither Doctrine nor Symfony — only the language and, possibly, the standard library. | «yes» Пояснение: This statement reflects a strict Domain-Driven Design principle where the Domain layer should remain independent of infrastructure frameworks like Doctrine or Symfony.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "This statement reflects a strict Domain-Driven Design principle where the Domain layer should remain independent of infrastructure frameworks like Doctrine or Symfony." ⏎ } | верно | Изоляция домена от инфраструктуры; deptrac в проекте как раз следит за слоями. |
T25-L3 0.37 c | Clean architecture | Controllers and Twig templates belong to the business-logic layer because they are the ones calling use cases. | «no» Пояснение: Controllers and templates belong to the presentation layer, while use cases belong to the business-logic layer.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "Controllers and templates belong to the presentation layer, while use cases belong to the business-logic layer." ⏎ } | верно | Наоборот: это интерфейсные адаптеры (внешний слой); они зависят от use cases, а не наоборот. |
T25-L4 0.43 c | Clean architecture | What sits at the very center of the onion architecture? | «domain» Пояснение: In onion architecture, the innermost layer contains the domain model, which is the core of the application and contains no dependencies on other layers.
Raw{ ⏎ "answer": "Domain", ⏎ "explanation": "In onion architecture, the innermost layer contains the domain model, which is the core of the application and contains no dependencies on other layers." ⏎ } | неверно верный: «domain model» | Центральное кольцо — Domain Model: сущности и бизнес-правила без зависимостей; далее Domain Services → Application Services → Infrastructure/UI/Tests (Palermo). |
T25-L5 0.4 c | Clean architecture | Layer boundary violations can be caught automatically: a layer-dependency analyzer (e.g. deptrac) fails on a forbidden call. | «yes» Пояснение: Tools like deptrac and phan are specifically designed to perform static analysis to detect and report architectural layer dependency violations.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Tools like deptrac and phan are specifically designed to perform static analysis to detect and report architectural layer dependency violations." ⏎ } | верно | depfile.yaml в проекте TasK: CI проверяет правила слоёв на каждом пайплайне. |
T25-L6 0.45 c | Clean architecture | A use case (interactor) may accept an HTTP request or an EntityManager as arguments — it is simpler that way. | «yes» Пояснение: It is generally simpler and more practical to inject dependencies like HTTP requests or EntityManagers into an interactor rather than constructing them internally, as this allows for easier testing and loose coupling.
Raw{"answer": "yes", "explanation": "It is generally simpler and more practical to inject dependencies like HTTP requests or EntityManagers into an interactor rather than constructing them internally, as this allows for easier testing and loose coupling."} | неверно верный: «no» | Use case принимает DTO и порты; привязка к HTTP/ORM протекает инфраструктуру во внутренние слои. |
T25-L7 0.44 c | Clean architecture | What is the component called that provides a collection of aggregates/entities while hiding the storage mechanism behind an interface? | «repository» Пояснение: The Repository pattern encapsulates the logic needed to obtain data objects from an abstract data source or object pool, hiding the storage mechanism behind an interface.
Raw{"answer": "Repository", "explanation": "The Repository pattern encapsulates the logic needed to obtain data objects from an abstract data source or object pool, hiding the storage mechanism behind an interface."} | верно | Repository pattern (DDD/Evans); в проекте — Doctrine-репозитории за портами. |
T25-L8 0.52 c | Clean architecture | In clean architecture, swapping PostgreSQL for another database touches only the outer layer — the domain and use cases stay unchanged. | «yes» Пояснение: In clean architecture, domain and use cases are independent of external infrastructure like databases, so swapping a database engine is handled by adapting the outer layer without altering the core.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "In clean architecture, domain and use cases are independent of external infrastructure like databases, so swapping a database engine is handled by adapting the outer layer without altering the core." ⏎ } | верно | Следствие правила зависимостей: инфраструктура взаимозаменяема. |
T26-L1 0.51 c | DDD | In DDD, an aggregate is just another name for a database table. | «no» Пояснение: An aggregate in DDD is a cluster of domain objects that share a common identity and can be modified as a single unit, which is conceptually broader and more complex than simply mapping to a database table.
Raw{"answer": "false", "explanation": "An aggregate in DDD is a cluster of domain objects that share a common identity and can be modified as a single unit, which is conceptually broader and more complex than simply mapping to a database table."} | верно | Агрегат — кластер объектов с границей согласованности (транзакционной вокруг корня); таблица — деталь хранения. |
T26-L2 0.33 c | DDD | A Value Object is immutable and compared by the values of its fields, not by identity. | «yes» Пояснение: Value objects are defined by their immutability and equality based on their field values rather than object identity.
Raw{"answer": "yes", "explanation": "Value objects are defined by their immutability and equality based on their field values rather than object identity."} | верно | Классика Evans: Money, Email; равенство структурное. |
T26-L3 0.39 c | DDD | What is the single external entry point of an aggregate, through which all changes must go, called? | «aggregate root» Пояснение: In Domain-Driven Design, the Aggregate Root serves as the single entry point for all interactions and modifications within an aggregate.
Raw{ ⏎ "answer": "Aggregate Root", ⏎ "explanation": "In Domain-Driven Design, the Aggregate Root serves as the single entry point for all interactions and modifications within an aggregate." ⏎ } | верно | Aggregate Root: внешние объекты ссылаются только на корень; он защищает инварианты агрегата. |
T26-L4 0.47 c | DDD | In DDD, a repository is declared for an aggregate (its root), not for every entity. | «yes» Пояснение: In DDD, the repository pattern is designed to manage the lifecycle and persistence of an aggregate, accessing its entities through the root aggregate.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "In DDD, the repository pattern is designed to manage the lifecycle and persistence of an aggregate, accessing its entities through the root aggregate." ⏎ } | верно | Репозиторий корня хранит границу согласованности агрегата; вложенные сущности доступны только через корень. |
T26-L5 0.36 c | DDD | Ubiquitous language is the model's shared language common to developers and domain experts. | «yes» Пояснение: In Domain-Driven Design, ubiquitous language ensures that the code, domain experts, and developers share the same terms and concepts.
Raw{"answer": "yes", "explanation": "In Domain-Driven Design, ubiquitous language ensures that the code, domain experts, and developers share the same terms and concepts."} | верно | Evans: язык из требований переходит в имена классов и методов. |
T26-L6 0.46 c | DDD | What is the boundary called within which a model and its language are consistent, while outside the same words mean other models? | «model» Пояснение: The term 'model' itself defines the boundary of consistency within a specific logical framework, where terms retain fixed meanings, unlike outside that framework where the same words may refer to different things.
Raw{"answer": "model", "explanation": "The term 'model' itself defines the boundary of consistency within a specific logical framework, where terms retain fixed meanings, unlike outside that framework where the same words may refer to different things."} | неверно верный: «bounded context» | Bounded Context; «Заказ» в биллинге и в доставке — разные модели. |
T26-L7 0.47 c | DDD | An anemic model (objects with only getters/setters, logic in services) is the recommended DDD style. | «no» Пояснение: In DDD, domain models are expected to encapsulate their invariants and behavior, so anemic models are generally considered an anti-pattern rather than the recommended style.
Raw{"answer": "no", "explanation": "In DDD, domain models are expected to encapsulate their invariants and behavior, so anemic models are generally considered an anti-pattern rather than the recommended style."} | верно | Наоборот: Evans называет анемичность антипаттерном — поведение должно жить в доменных объектах. |
T26-L8 0.54 c | DDD | Bounded context means each context has its own model: the same concept in different contexts is a different class. | «yes» Пояснение: In Domain-Driven Design, a bounded context defines a logical boundary where a particular domain model is valid and consistent, and the same concept (like 'Customer') can be modeled as a distinct class with different attributes and behaviors in different contexts.
Raw{"answer": "yes", "explanation": "In Domain-Driven Design, a bounded context defines a logical boundary where a particular domain model is valid and consistent, and the same concept (like 'Customer') can be modeled as a distinct class with different attributes and behaviors in different contexts."} | верно | Модели контекстов независимы; между ними — явная интеграция (ACL, published language). |
T13-L1 0.42 c | Symfony | Services in the Symfony DI container are created lazily by default — on first use. | «yes» Пояснение: Symfony's DI container uses lazy initialization, meaning services are typically instantiated only when they are first requested or injected.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Symfony's DI container uses lazy initialization, meaning services are typically instantiated only when they are first requested or injected." ⏎ } | верно | Контейнер инстанцирует сервис при первом извлечении; eager-создания по умолчанию нет. |
T13-L2 0.45 c | Symfony | Which Symfony console command lists all registered routes? | «symfony:routes» Пояснение: The Symfony command 'symfony:routes' (or 'console:routes' in older versions) lists all registered routes in the application.
Raw{ ⏎ "answer": "symfony:routes", ⏎ "explanation": "The Symfony command 'symfony:routes' (or 'console:routes' in older versions) lists all registered routes in the application." ⏎ } | неверно верный: «debug:router» | bin/console debug:router (FrameworkBundle); в Symfony 3 команда называлась router:debug. |
T13-L3 0.33 c | Symfony | Symfony autowiring requires manually declaring every service in services.yaml. | «no» Пояснение: Symfony's autowiring feature automatically detects and wires services based on type hints without manual declaration in services.yaml.
Raw{"answer": "no", "explanation": "Symfony's autowiring feature automatically detects and wires services based on type hints without manual declaration in services.yaml."} | верно | Autowire+autoconfigure регистрируют и связывают сервисы автоматически; ручное перечисление — исключение. |
T13-L4 0.37 c | Symfony | Twig templates are compiled into PHP classes and cached between requests. | «yes» Пояснение: Twig compiles templates into PHP classes and caches them on disk to avoid recompiling them on every request.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Twig compiles templates into PHP classes and caches them on disk to avoid recompiling them on every request." ⏎ } | верно | Twig компилирует шаблон один раз; кэш в var/cache/twig, в prod не пересобирается. |
T13-L5 0.39 c | Symfony | In the Symfony dev environment the DI container is rebuilt only after tracked files change, not on every request. | «yes» Пояснение: In the Symfony development environment, the container is cached and only rebuilt when tracked files change rather than on every request.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "In the Symfony development environment, the container is cached and only rebuilt when tracked files change rather than on every request." ⏎ } | верно | Kernel проверяет freshness ресурсов (конфиги, классы); иначе переиспользуется кэш контейнера. |
T13-L6 0.37 c | Symfony | Which environment variable selects the active Symfony environment (dev/prod)? | «symfony_env» Пояснение: The SYMFONY_ENV environment variable is used by Symfony to determine the active application environment, such as dev or prod.
Raw{"answer": "SYMFONY_ENV", "explanation": "The SYMFONY_ENV environment variable is used by Symfony to determine the active application environment, such as dev or prod."} | неверно верный: «app_env» | APP_ENV в .env; APP_DEBUG — отдельный флаг отладки. |
T13-L7 0.4 c | Symfony | A controller method can be private — Symfony routing works with any method of the class. | «no» Пояснение: Symfony routing requires controller methods to be public so the framework can invoke them externally via the HTTP dispatcher.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "Symfony routing requires controller methods to be public so the framework can invoke them externally via the HTTP dispatcher." ⏎ } ⏎ ``` | верно | Действие контроллера должно быть public; приватный метод по маршруту не вызывается. |
T13-L8 0.45 c | Symfony | Event subscribers always receive events before listeners, because the interface gives them priority. | «no» Пояснение: In PHP's observer pattern and Symfony's DispatchEvent system, subscribers and listeners are often treated as equivalent, and execution order is typically determined by priority levels rather than the type of registration.
Raw{"answer": "no", "explanation": "In PHP's observer pattern and Symfony's DispatchEvent system, subscribers and listeners are often treated as equivalent, and execution order is typically determined by priority levels rather than the type of registration."} | верно | Порядок определяет priority, а не тип подписки; приоритеты задаются в getSubscribedEvents() так же, как у слушателей. |
T22-L1 0.43 c | Symfony: Security and forms | In modern Symfony (6.0+) authentication is built on authenticator classes (AuthenticatorInterface); the old guard system has been removed. | «no» Пояснение: The legacy guard system was removed in Symfony 5.3, and the new Security component using AuthenticatorInterface is the standard in modern Symfony versions like 6.0+.
Raw{"answer": "no", "explanation": "The legacy guard system was removed in Symfony 5.3, and the new Security component using AuthenticatorInterface is the standard in modern Symfony versions like 6.0+."} | неверно верный: «yes» | Guard объявлен устаревшим в 5.3 и удалён в 6.0; в проекте symfony/security-bundle 8.1. |
T22-L2 0.36 c | Symfony: Security and forms | Which Symfony attribute checks a role/permission right on a controller method (403 without it)? | «isgranted» Пояснение: The isGranted attribute (from the security namespace) checks user permissions/roles on controller methods.
Raw{"answer": "isGranted", "explanation": "The isGranted attribute (from the security namespace) checks user permissions/roles on controller methods."} | верно | #[IsGranted('ROLE_ADMIN')]; атрибут из symfony/security-http. |
T22-L3 0.76 c | Symfony: Security and forms | Voters are Symfony's mechanism for checking access to a specific object: isGranted('EDIT', $post). | «no» Пояснение: Symfony uses Voter objects (which implement AccessVoterInterface) to check access to specific objects, but 'Voters' is not the specific mechanism name; the method is typically called via a custom AccessChecker or a Voter object directly, though the concept described is partially correct, the term 'Voters' as a mechanism is inaccurate in the context of the question's phrasing.
Raw{"answer": "no", "explanation": "Symfony uses Voter objects (which implement AccessVoterInterface) to check access to specific objects, but 'Voters' is not the specific mechanism name; the method is typically called via a custom AccessChecker or a Voter object directly, though the concept described is partially correct, the term 'Voters' as a mechanism is inaccurate in the context of the question's phrasing."} | неверно верный: «yes» | VoterInterface->vote(); docs Symfony — Voters. |
T22-L4 0.44 c | Symfony: Security and forms | In modern Symfony (7+) validation constraints are declared as PHP attributes (#[Assert\NotBlank]); doctrine annotations are no longer supported. | «yes» Пояснение: Symfony 6+ fully supports and recommends using PHP attributes for validation and Doctrine mapping, while legacy annotation support has been deprecated and removed in recent releases.
Raw{"answer": "yes", "explanation": "Symfony 6+ fully supports and recommends using PHP attributes for validation and Doctrine mapping, while legacy annotation support has been deprecated and removed in recent releases."} | верно | Докблок-аннотации удалены в Symfony 7.0; стандарт — атрибуты. В проекте symfony/validator 8.1. |
T22-L5 0.36 c | Symfony: Security and forms | CSRF protection of Symfony forms is enabled by default: the form validates the token on submission. | «yes» Пояснение: Symfony automatically generates and validates CSRF tokens for forms to protect against cross-site request forgery attacks.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Symfony automatically generates and validates CSRF tokens for forms to protect against cross-site request forgery attacks." ⏎ } | верно | FormType добавляет скрытое поле _token и проверяет его при валидации; отключение — осознанное исключение (csrf: false). |
T22-L6 0.4 c | Symfony: Security and forms | Form validation in Symfony runs server-side even if the client-side (HTML5) checks passed. | «yes» Пояснение: Symfony always validates user input on the server side to ensure data integrity and security, regardless of client-side HTML5 validation.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Symfony always validates user input on the server side to ensure data integrity and security, regardless of client-side HTML5 validation." ⏎ } | верно | Клиентская валидация — только удобство; серверная обязательна и идёт по метаданным объекта формы. |
T22-L7 0.38 c | Symfony: Security and forms | Which Symfony maker command generates a form class (FormType)? | «symfony maker:form» Пояснение: The 'symfony maker:form' command generates a custom form type class based on a model entity or existing class.
Raw{"answer": "symfony maker:form", "explanation": "The 'symfony maker:form' command generates a custom form type class based on a model entity or existing class."} | неверно верный: «make:form» | bin/console make:form (symfony/maker-bundle — в проекте). |
T22-L8 0.36 c | Symfony: Security and forms | Symfony stores the user's password in the session in plain text. | «no» Пояснение: Symfony stores only the hashed password in the database and never stores plain-text passwords in the session.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "Symfony stores only the hashed password in the database and never stores plain-text passwords in the session." ⏎ } | верно | В сессии живёт объект пользователя в токене; хеш затирается eraseCredentials(), plaintext там никогда не лежит. |
T23-L1 0.38 c | Symfony: configuration and services | Symfony bundle configuration lives in config/packages — one file per bundle or topic. | «yes» Пояснение: In Symfony, it is common convention to organize bundle configurations in the config/packages directory, often creating a dedicated file for each bundle or topic.
Raw{"answer": "yes", "explanation": "In Symfony, it is common convention to organize bundle configurations in the config/packages directory, often creating a dedicated file for each bundle or topic."} | верно | Стандартная структура (config/packages/*.yaml); перегрузка — config/packages/<env>. |
T23-L2 0.44 c | Symfony: configuration and services | The .env file with dev defaults is committed to the repository, while real secrets live in the non-committed .env.local. | «yes» Пояснение: A common best practice is to commit a .env.example or .env with safe defaults while keeping .env or .env.local with real secrets untracked via .gitignore.
Raw{"answer": "yes", "explanation": "A common best practice is to commit a .env.example or .env with safe defaults while keeping .env or .env.local with real secrets untracked via .gitignore."} | верно | symfony/dotenv: .env — общий безопасный набор значений; локальные секреты — .env.local (gitignored) или secrets-хранилище. |
T23-L3 0.36 c | Symfony: configuration and services | Which Symfony command lists the container's registered services and their aliases? | «bin/console debug:container» Пояснение: The debug:container command in Symfony lists the registered services and their aliases in the container.
Raw{"answer":"bin/console debug:container", "explanation":"The debug:container command in Symfony lists the registered services and their aliases in the container."} | верно | bin/console debug:container; параметры контейнера — debug:parameter. |
T23-L4 0.36 c | Symfony: configuration and services | The Symfony container allows changing parameters at runtime: $container->setParameter() works from a controller. | «yes» Пояснение: The Symfony container is mutable and supports setParameter() to update parameter values at runtime, even after the container has been initialized.
Raw{"answer": "yes", "explanation": "The Symfony container is mutable and supports setParameter() to update parameter values at runtime, even after the container has been initialized."} | неверно верный: «no» | Контейнер компилируется и замораживается; runtime-значения — только через переменные окружения. |
T23-L5 0.42 c | Symfony: configuration and services | By default, Symfony services are public (public: true) — you can fetch them directly from the container. | «no» Пояснение: In Symfony 3.4 and later, services are private by default and must be marked public to be fetched directly from the container.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "In Symfony 3.4 and later, services are private by default and must be marked public to be fetched directly from the container." ⏎ } | верно | С Symfony 4.0 сервисы по умолчанию private: инжектятся через autowiring; $container->get() — только для публичных. |
T23-L6 0.41 c | Symfony: configuration and services | Without a config file in config/packages a bundle will not work — configuration is mandatory for every bundle. | «no» Пояснение: Bundles in Symfony are optional regarding configuration; they can be registered without a dedicated config file and still function using their default settings or the framework's core configuration.
Raw{"answer": "no", "explanation": "Bundles in Symfony are optional regarding configuration; they can be registered without a dedicated config file and still function using their default settings or the framework's core configuration."} | верно | У бандлов есть встроенные умолчания (Extension); конфиг нужен только для отклонений от них. |
T23-L7 3.52 c | Symfony: configuration and services | Environment variable values are injected into services.yaml using the %env(VAR)% syntax. | «no» Пояснение: ", it means the statement is true. If I answer "no", it means false. The statement says "Environment variable values are injected into services.yaml using the %env(VAR)% syntax." This is a standard Symfony feature. So the answer should be "yes". Let me double check if there's any trap. Maybe the syntax is %env:VAR%? No, it's %env(VAR)%. Or maybe it requires the parameter to be defined in params.yaml first? Yes, but you can also define it inline in services.yaml. So the statement is generally true. I will go with "yes".", "explanation": "In Symfony, the %env(VAR)% placeholder syntax is the standard method for injecting environment variables into configuration files, including services.yaml."}
Raw{"answer": "no", "explanation": "In Symfony, environment variables are injected into YAML configuration files using the %env(VAR)% syntax only when the environment variable processor is properly configured and the parameter is defined, but the statement as a general rule about all services.yaml injections is misleading since the specific syntax depends on the context and setup; however, the primary reason this is false in a general exam context is that this syntax is used for parameters in general, not exclusively or universally as a standalone fact without context, but more likely, the question is a trick because in Symfony, you typically use %env(VAR)% inside *parameters.yaml* or directly, and it works in services.yaml, so it is actually TRUE. Wait, let me re-read. Symfony *does* allow %env(VAR)% in services.yaml. So why would it be false? Maybe the question implies it's the *only* way or something else. Let's reconsider. Actually, in Symfony, the correct syntax is indeed %env(VAR)%. So the statement is True. Let me check if there's any nuance. Some older versions or specific contexts might use different syntax, but in standard modern Symfony (3.3+), %env(VAR)% is the standard. I will answer True. Wait, the user asked "True or false?". If I answer "yes", it means the statement is true. If I answer "no", it means false. The statement says "Environment variable values are injected into services.yaml using the %env(VAR)% syntax." This is a standard Symfony feature. So the answer should be "yes". Let me double check if there's any trap. Maybe the syntax is %env:VAR%? No, it's %env(VAR)%. Or maybe it requires the parameter to be defined in params.yaml first? Yes, but you can also define it inline in services.yaml. So the statement is generally true. I will go with "yes".", "explanation": "In Symfony, the %env(VAR)% placeholder syntax is the standard method for injecting environment variables into configuration files, including services.yaml."} | неверно верный: «yes» парсинг: текст (фолбэк) | %env(...)% резолвится в рантайме env-процессорами; docs — Env Var Processors. |
T23-L8 0.47 c | Symfony: configuration and services | Which Symfony environment variable enables debug mode (affects the profiler and Twig debugging)? | «app_debug» Пояснение: The APP_DEBUG environment variable, typically set to true in the dev environment, enables debug mode which activates the profiler and Twig debugging features.
Raw{ ⏎ "answer": "APP_DEBUG", ⏎ "explanation": "The APP_DEBUG environment variable, typically set to true in the dev environment, enables debug mode which activates the profiler and Twig debugging features." ⏎ } | верно | APP_DEBUG=1 (в .env dev-окружения); окружение выбирает APP_ENV — см. T13-L6. |
T16-L1 0.45 c | Symfony: Messenger | A single message in Symfony Messenger can only have one handler. | «yes» Пояснение: In Symfony Messenger, a single message can be handled by multiple handlers registered for the same message class or by using transport options to fan out to multiple consumers.
Raw{"answer": "yes", "explanation": "In Symfony Messenger, a single message can be handled by multiple handlers registered for the same message class or by using transport options to fan out to multiple consumers."} | неверно верный: «no» | Messenger вызывает все хендлеры, подписанные на класс сообщения (docs — Multiple Handlers). |
T16-L2 0.47 c | Symfony: Messenger | The sync transport in Messenger queues the message for a worker, just like async. | «no» Пояснение: The sync transport in Symfony Messenger does not queue messages; it synchronously executes the message immediately within the same request cycle, whereas the async transport sends it to a transport that a separate worker consumes.
Raw{"answer": "no", "explanation": "The sync transport in Symfony Messenger does not queue messages; it synchronously executes the message immediately within the same request cycle, whereas the async transport sends it to a transport that a separate worker consumes."} | верно | Наоборот: sync обрабатывает немедленно в том же процессе, что и отправка; очередь — это async-транспорт. |
T16-L3 0.42 c | Symfony: Messenger | Which console command starts the worker that processes Messenger queue messages? | «bin/console messenger:consume» Пояснение: The messenger:consume command is used to start the worker that processes messages from the queue in Symfony Messenger.
Raw{ ⏎ "answer": "bin/console messenger:consume", ⏎ "explanation": "The messenger:consume command is used to start the worker that processes messages from the queue in Symfony Messenger." ⏎ } | верно | bin/console messenger:consume async; воркеры под supervisord/systemd в проде. |
T16-L4 0.26 c | Symfony: Messenger | Retries for failed messages (retry_strategy) are configured per Messenger transport. | «yes» Пояснение: Retry strategies are configured within the transport configuration in Symfony Messenger.
Raw{"answer": "yes", "explanation": "Retry strategies are configured within the transport configuration in Symfony Messenger."} | верно | retry_strategy на транспорте: max_retries, delay, multiplier; docs — Failed Messages & Retries. |
T16-L5 0.27 c | Symfony: Messenger | By default, Messenger serializes messages to JSON. | «yes» Пояснение: The default serializer used by the Symfony Messenger component is the JSONSerializer.
Raw{"answer": "yes", "explanation": "The default serializer used by the Symfony Messenger component is the JSONSerializer."} | неверно верный: «no» | Дефолтный сериализатор — PhpSerializer (serialize()); JSON-сериализатор включается отдельно. |
T16-L6 0.38 c | Symfony: Messenger | Symfony Scheduler produces messages on a schedule and dispatches them through Messenger. | «no» Пояснение: The Symfony Scheduler component is designed to execute arbitrary callbacks or commands, not specifically to produce and dispatch Messenger messages.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "The Symfony Scheduler component is designed to execute arbitrary callbacks or commands, not specifically to produce and dispatch Messenger messages." ⏎ } | неверно верный: «yes» | Schedule → RecurringMessage → шина Messenger; docs — Scheduler. |
T16-L7 0.3 c | Symfony: Messenger | Which built-in Messenger transport stores messages in database tables via Doctrine? | «doctrine» Пояснение: The Doctrine transport in Symfony Messenger uses database tables managed by Doctrine ORM to persist messages.
Raw{"answer": "doctrine", "explanation": "The Doctrine transport in Symfony Messenger uses database tables managed by Doctrine ORM to persist messages."} | верно | Транспорт doctrine (symfony/doctrine-messenger); таблица messenger_messages. В проекте стоит amqp-messenger + doctrine-messenger. |
T16-L8 0.37 c | Symfony: Messenger | The Messenger pipeline can be extended with custom middleware, placed before or after the built-in ones. | «yes» Пояснение: Laravel's Messenger pipeline supports custom middleware that can be inserted at specific positions to run before or after the built-in middleware classes.
Raw{"answer": "yes", "explanation": "Laravel's Messenger pipeline supports custom middleware that can be inserted at specific positions to run before or after the built-in middleware classes."} | верно | messenger.bus.*.middleware в yaml; docs — Middleware. |
T28-L1 0.67 c | Symfony: versions | Symfony major releases come every two years, minor ones every six months (in May and November). | «yes» Пояснение: Symfony follows a long-term support (LTS) strategy where major versions are released every two years (e.g., Symfony 4.4, 5.4, 6.4) and stable minor releases occur roughly every six months in May and November.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "Symfony follows a long-term support (LTS) strategy where major versions are released every two years (e.g., Symfony 4.4, 5.4, 6.4) and stable minor releases occur roughly every six months in May and November." ⏎ } ⏎ ``` | верно | Стандартный релизный цикл: 8.0 — ноябрь 2025, 8.1 — май 2026, 8.2 — ноябрь 2026. |
T28-L2 0.36 c | Symfony: versions | What is the minimum PHP version required by Symfony 8? | «8.1» Пояснение: Symfony 8 requires PHP 8.1 or higher.
Raw{ ⏎ "answer": "8.1", ⏎ "explanation": "Symfony 8 requires PHP 8.1 or higher." ⏎ } | неверно верный: «8.4» | Symfony 8.0 поднял требование до PHP >= 8.4.1 (в vendor проекта: "php": ">=8.4.1"). |
T28-L3 0.41 c | Symfony: versions | Symfony 7.0 kept support for docblock annotations (validation, routes). | «no» Пояснение: Symfony 7.0 removed support for docblock annotations in favor of attributes, which became mandatory in Symfony 6.0.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "Symfony 7.0 removed support for docblock annotations in favor of attributes, which became mandatory in Symfony 6.0." ⏎ } | верно | Наоборот: в 7.0 аннотации удалены — только PHP-атрибуты (#[Route], #[Assert\NotBlank]). |
T28-L4 0.44 c | Symfony: versions | AssetMapper manages CSS/JS without node or webpack — via importmap.php. | «yes» Пояснение: AssetMapper is a PHP library that dynamically generates an import map (importmap.php) to manage CSS and JavaScript assets without requiring Node.js or a build tool like webpack.
Raw{"answer": "yes", "explanation": "AssetMapper is a PHP library that dynamically generates an import map (importmap.php) to manage CSS and JavaScript assets without requiring Node.js or a build tool like webpack."} | верно | symfony/asset-mapper (с 6.3, стандарт с 7.x); в проекте — importmap.php в корне и asset-mapper 8.1. |
T28-L5 0.68 c | Symfony: versions | Symfony 6.4 is a regular release without long-term support. | «yes» Пояснение: Symfony 6.4 is a minor release that received standard support and is not designated as a Long-Term Support (LTS) release, unlike versions 6.0, 6.1, 6.2, 6.3, 6.4, and 6.5.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Symfony 6.4 is a minor release that received standard support and is not designated as a Long-Term Support (LTS) release, unlike versions 6.0, 6.1, 6.2, 6.3, 6.4, and 6.5." ⏎ } | неверно верный: «no» | Наоборот: 6.4 — LTS (расширенная поддержка); LTS выходит вместе с очередным мажором (6.4 — вместе с 7.0). |
T28-L6 0.38 c | Symfony: versions | When moving to a new Symfony major version, deprecations of the previous branch keep working — major releases do not remove them. | «no» Пояснение: Major Symfony releases remove the deprecations introduced in the previous major branch, so you must fix them before upgrading.
Raw{"answer": "no", "explanation": "Major Symfony releases remove the deprecations introduced in the previous major branch, so you must fix them before upgrading."} | верно | Наоборот: мажорный релиз удаляет всё устаревшее (7.0 убрал деприкейшены 6.x, 8.0 — 7.x). |
T28-L7 0.31 c | Symfony: versions | Every Symfony major release is accompanied by an UPGRADE guide listing the changes. | «yes» Пояснение: Symfony provides an UPGRADE guide for each major release to document breaking changes and new features.
Raw{"answer": "yes", "explanation": "Symfony provides an UPGRADE guide for each major release to document breaking changes and new features."} | верно | UPGRADE-7.0.md, UPGRADE-8.0.md в репозитории symfony/symfony. |
T28-L8 0.44 c | Symfony: versions | Which Symfony component manages assets and the importmap without node/webpack? | «webpack meta» Пояснение: The Webpack Meta component of Symfony is specifically designed to manage assets and generate or manage an importmap without the need for a build step like Node.js or Webpack.
Raw{"answer": "Webpack Meta", "explanation": "The Webpack Meta component of Symfony is specifically designed to manage assets and generate or manage an importmap without the need for a build step like Node.js or Webpack."} | неверно верный: «asset-mapper» | symfony/asset-mapper 8.1 — в проекте. |
T29-L1 0.41 c | Symfony: 8.2 and beyond | As of 2026-11-07, Symfony 8.2 has already been released. | «yes» Пояснение: Symfony 8.2 is scheduled to be released in November 2026 and is expected to be available by that date.
Raw{"answer": "yes", "explanation": "Symfony 8.2 is scheduled to be released in November 2026 and is expected to be available by that date."} | неверно верный: «no» | Наоборот: 8.2 ещё не выпущена — релиз в конце ноября 2026; последняя стабильная — 8.1. |
T29-L2 0.63 c | Symfony: 8.2 and beyond | As of 2026-11-07, Symfony 8.2 is scheduled for November 2026, following the usual six-month cycle. | «no» Пояснение: The statement is factually incorrect because Symfony follows a six-month release cycle where the major version number always matches the year's first two digits (e.g., 2.4, 4.2, 5.2), not a sequential versioning scheme like 8.2.
Raw{"answer": "no", "explanation": "The statement is factually incorrect because Symfony follows a six-month release cycle where the major version number always matches the year's first two digits (e.g., 2.4, 4.2, 5.2), not a sequential versioning scheme like 8.2."} | неверно верный: «yes» | Политика релизов: 8.1 — май 2026, 8.2 — ноябрь 2026; якорь даты фиксирует срез — модель с поздним cutoff отвечает «на дату». |
T29-L3 0.37 c | Symfony: 8.2 and beyond | Which Symfony version comes after 8.1 (as of 2026-11-07)? | «8.2» Пояснение: Symfony 8.1 is followed by 8.2 in the minor release sequence.
Raw{"answer": "8.2", "explanation": "Symfony 8.1 is followed by 8.2 in the minor release sequence."} | верно | 8.2 — следующий минорный релиз (ноябрь 2026); после его выхода проект переходит с 8.1.* на 8.2.*. |
T29-L4 0.46 c | Symfony: 8.2 and beyond | Symfony 8.2 is a major release requiring applications to be rewritten for new APIs. | «no» Пояснение: Symfony does not currently release major versions with the 2.x or 3.x numbering for its latest stable branch, and 8.2 is not an existing or announced major release version.
Raw{"answer": "no", "explanation": "Symfony does not currently release major versions with the 2.x or 3.x numbering for its latest stable branch, and 8.2 is not an existing or announced major release version."} | верно | Наоборот: 8.2 — минорный релиз; новые возможности без поломки обратной совместимости. Мажор — 9.0. |
T29-L5 0.49 c | Symfony: 8.2 and beyond | Updating within a major branch (8.1 → 8.2) should not require code changes — backward compatibility is preserved. | «no» Пояснение: While minor updates within a major branch preserve backward compatibility, moving from 8.1 to 8.2 crosses a major version boundary which can introduce breaking changes requiring code modifications.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "While minor updates within a major branch preserve backward compatibility, moving from 8.1 to 8.2 crosses a major version boundary which can introduce breaking changes requiring code modifications." ⏎ } | неверно верный: «yes» | Политика Symfony: минорные релизы обратно совместимы; BC-break допустим только в мажорных. |
T29-L6 0.48 c | Symfony: 8.2 and beyond | Which minor version of the 8.x branch is released last, before Symfony 9.0? | «8.3» Пояснение: Symfony 8.3 is the last minor version released in the 8.x branch before the release of Symfony 9.0.
Raw{ ⏎ "answer": "8.3", ⏎ "explanation": "Symfony 8.3 is the last minor version released in the 8.x branch before the release of Symfony 9.0." ⏎ } | неверно верный: «8.4» | По циклу: 8.2 (ноя 2026), 8.3 (май 2027), 8.4 (ноя 2027, вместе с 9.0) — как 6.4 выходила вместе с 7.0. |
T29-L7 0.48 c | Symfony: 8.2 and beyond | Symfony 8.2 will require PHP 8.5 — you would have to upgrade PHP along with it. | «yes» Пояснение: Symfony 8.x is the first major release to drop support for PHP 8.3 and 8.4, making PHP 8.5 the minimum required version.
Raw{"answer": "yes", "explanation": "Symfony 8.x is the first major release to drop support for PHP 8.3 and 8.4, making PHP 8.5 the minimum required version."} | неверно верный: «no» | Наоборот: минорные релизы не поднимают требования PHP; для всей ветки 8.x остаётся PHP >= 8.4. |
T29-L8 0.45 c | Symfony: 8.2 and beyond | Deprecations added in the 8.x branch will not be removed before Symfony 9.0. | «yes» Пояснение: Symfony follows a policy where deprecations introduced in a major version remain until the next major release, meaning 8.x deprecations will persist until Symfony 9.0.
Raw{"answer": "yes", "explanation": "Symfony follows a policy where deprecations introduced in a major version remain until the next major release, meaning 8.x deprecations will persist until Symfony 9.0."} | верно | Политика: деприкейшены живут до следующего мажора; 9.0 — ноябрь 2027. |
T21-L1 0.4 c | Twig | Inside {{ }}, Twig allows calling arbitrary PHP code directly. | «no» Пояснение: Twig does not allow calling arbitrary PHP code directly inside its expressions; it provides a restricted set of functions and operators designed to be safe and sandboxed.
Raw{"answer": "no", "explanation": "Twig does not allow calling arbitrary PHP code directly inside its expressions; it provides a restricted set of functions and operators designed to be safe and sandboxed."} | верно | Twig — DSL: только разрешённые окружением функции/фильтры; произвольный PHP не исполняется. |
T21-L2 0.39 c | Twig | By default, Twig auto-escapes printed variables. | «yes» Пояснение: By default, Twig has auto-escaping enabled, which safely encodes variables before printing them to prevent XSS attacks.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "By default, Twig has auto-escaping enabled, which safely encodes variables before printing them to prevent XSS attacks." ⏎ } | верно | Autoescape включён по умолчанию; {{ '<b>' }} → <b>. Проверено на Twig 3.30. |
T21-L3 0.41 c | Twig | The Twig |e filter escapes a string for safe output in an HTML context. | «yes» Пояснение: The Twig |e (or |escape) filter escapes a string to prevent XSS by converting special characters to HTML entities by default.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "The Twig |e (or |escape) filter escapes a string to prevent XSS by converting special characters to HTML entities by default." ⏎ } | верно | |e ('html') по умолчанию; есть контексты js/url/css. От SQL-инъекций он не защищает — это задача подготовленных запросов Doctrine. |
T21-L4 0.37 c | Twig | Which filter from twig/intl-extra formats a number according to a locale? | «locale» Пояснение: The `locale` filter in twig/intl-extra formats a number or date according to a specific locale.
Raw{ ⏎ "answer": "locale", ⏎ "explanation": "The `locale` filter in twig/intl-extra formats a number or date according to a specific locale." ⏎ } | неверно верный: «format_number» | |format_number(locale=...) из IntlExtension (twig/intl-extra есть в проекте). Проверено на Twig 3.30: 12345.6 → 12 345,6 (ru). |
T21-L5 0.44 c | Twig | The |raw filter disables auto-escaping for the value. | «no» Пояснение: The |raw filter does not exist in PHP's standard native filter set; it is a custom Laravel helper used in Blade templates, not a PHP filter.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "The |raw filter does not exist in PHP's standard native filter set; it is a custom Laravel helper used in Blade templates, not a PHP filter." ⏎ } | неверно верный: «yes» | {{ x|raw }} выводит HTML как есть; опасно с пользовательскими данными. Проверено на Twig 3.30. |
T21-L6 0.35 c | Twig | In Twig, {{ }} prints an expression value, while {% %} executes tags — conditions, loops, set. | «yes» Пояснение: {{ }} outputs the result of an expression, while {% %} executes template tags like if, for, and set.
Raw{"answer": "yes", "explanation": "{{ }} outputs the result of an expression, while {% %} executes template tags like if, for, and set."} | верно | Два блока синтаксиса Twig: вывод (echo) против логики. |
T21-L7 0.47 c | Twig | In Twig you cannot declare a variable inside a template — values only come from the controller. | «yes» Пояснение: While values typically come from the controller, Twig does allow you to declare variables inside a template using the `set` tag (e.g., `{% set x = 10 %}`).
Raw{"answer": "yes", "explanation": "While values typically come from the controller, Twig does allow you to declare variables inside a template using the `set` tag (e.g., `{% set x = 10 %}`)."} | неверно верный: «no» | {% set y = ... %} объявляет переменную в шаблоне. Проверено на Twig 3.30. |
T21-L8 0.35 c | Twig | Which Twig function dumps the debug structure of a variable (array, object)? | «dump()» Пояснение: The dump() function in Twig is used to output the debug structure of a variable, similar to var_dump in PHP.
Raw{"answer": "dump()", "explanation": "The dump() function in Twig is used to output the debug structure of a variable, similar to var_dump in PHP."} | верно | {{ dump(x) }} (DebugExtension; в Symfony доступна в dev-окружении). |
T24-L1 0.37 c | Bootstrap | Bootstrap is a CSS/JS library of ready-made UI components, not an SPA framework. | «yes» Пояснение: Bootstrap is a frontend library providing UI components and utilities, while SPA frameworks like React or Angular handle client-side routing and state management.
Raw{"answer": "yes", "explanation": "Bootstrap is a frontend library providing UI components and utilities, while SPA frameworks like React or Angular handle client-side routing and state management."} | верно | Компоненты и утилиты поверх вашего HTML; SPA-фреймворки (React/Vue) — другой класс инструментов. В проекте vendored 5.3.3. |
T24-L2 0.37 c | Bootstrap | Which Bootstrap class gives a responsive container with a fixed max width per breakpoint? | «container-fluid» Пояснение: The .container-fluid class provides a responsive container that expands to fill the viewport width with a fixed max-width at each breakpoint.
Raw{"answer": "container-fluid", "explanation": "The .container-fluid class provides a responsive container that expands to fill the viewport width with a fixed max-width at each breakpoint."} | неверно верный: «container» | .container (фиксированная макс-ширина по брейкпоинтам) vs .container-fluid (на всю ширину). |
T24-L3 0.41 c | Bootstrap | The Bootstrap grid is built on CSS floats and splits a row into 16 columns. | «no» Пояснение: Bootstrap 3 and later use a 12-column grid system, and the modern versions have transitioned from CSS floats to CSS Grid and Flexbox.
Raw{"answer": "no", "explanation": "Bootstrap 3 and later use a 12-column grid system, and the modern versions have transitioned from CSS floats to CSS Grid and Flexbox."} | верно | Наоборот: flexbox (с Bootstrap 4) и 12 колонок; float-сетка — это Bootstrap 3. |
T24-L4 0.43 c | Bootstrap | Bootstrap's named breakpoints (the infix used in class names) are sm, md, lg, xl, xxl — five of them. | «no» Пояснение: The base breakpoint xs is not used as an infix, so there are only four named breakpoints (sm, md, lg, xl/xxl depending on version).
Raw{"answer": "no", "explanation": "The base breakpoint xs is not used as an infix, so there are only four named breakpoints (sm, md, lg, xl/xxl depending on version)."} | неверно верный: «yes» | Тиров всего шесть: xs (без инфикса) + пять именованных (576/768/992/1200/1400 px). |
T24-L5 0.49 c | Bootstrap | Utilities like .mt-3 or .px-2 use the spacing scale: the number is a multiple of $spacer. | «yes» Пояснение: In utilities like .mt-3, the suffix number corresponds to a multiple of the configured $spacer value from the spacing scale.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "In utilities like .mt-3, the suffix number corresponds to a multiple of the configured $spacer value from the spacing scale." ⏎ } ⏎ ``` | неверно верный: «no» | Spacing utilities; $spacer = 1rem. |
T24-L6 0.38 c | Bootstrap | Which Bootstrap 5 data attribute enables an interactive component (e.g. dropdown) on an element? | «data-bs-toggle» Пояснение: The data-bs-toggle attribute is used in Bootstrap 5 to enable interactive components like dropdowns on an element.
Raw{"answer": "data-bs-toggle", "explanation": "The data-bs-toggle attribute is used in Bootstrap 5 to enable interactive components like dropdowns on an element."} | верно | data-bs-toggle="dropdown" и т.п.; в Bootstrap 4 атрибут назывался data-toggle. |
T24-L7 0.34 c | Bootstrap | Bootstrap 5 components work without jQuery — in plain vanilla JS. | «yes» Пояснение: Bootstrap 5 removed its dependency on jQuery and uses vanilla JavaScript along with its own custom event system to drive its components.
Raw{"answer": "yes", "explanation": "Bootstrap 5 removed its dependency on jQuery and uses vanilla JavaScript along with its own custom event system to drive its components."} | верно | jQuery удалён в Bootstrap 5.0: data-bs-* атрибуты и JS API. В проекте vendored 5.3.3. |
T24-L8 0.34 c | Bootstrap | Dark mode in Bootstrap is enabled with a .dark class on the root element. | «yes» Пояснение: In Bootstrap 5, dark mode is enabled by adding the 'dark' class to the html or body element.
Raw{"answer": "yes", "explanation": "In Bootstrap 5, dark mode is enabled by adding the 'dark' class to the html or body element."} | неверно верный: «no» | Наоборот: тема включается атрибутом data-bs-theme="dark" (Color modes, с 5.3); класса .dark не существует. В проекте 5.3.3. |
T14-L1 0.37 c | Doctrine | Doctrine ORM creates database tables on the fly the first time an entity is used at runtime. | «no» Пояснение: Doctrine ORM does not create database tables automatically; you must explicitly use the SchemaTool or migrations to create tables from the entity metadata.
Raw{"answer": "no", "explanation": "Doctrine ORM does not create database tables automatically; you must explicitly use the SchemaTool or migrations to create tables from the entity metadata."} | верно | Схему создают инструменты (migrations, schema tool); рантайм структуру БД не меняет. |
T14-L2 0.38 c | Doctrine | Which EntityManager method marks a new object as managed without executing SQL until flush()? | «persist()» Пояснение: The EntityManager::persist() method puts a new object into the managed state (the persistent lifecycle) without issuing SQL until flush() is called.
Raw{"answer": "persist()", "explanation": "The EntityManager::persist() method puts a new object into the managed state (the persistent lifecycle) without issuing SQL until flush() is called."} | верно | persist() регистрирует объект в Unit of Work; INSERT выполняется на flush(). |
T14-L3 0.32 c | Doctrine | In Doctrine ORM 3, the EntityManager::merge() method exists and makes the passed object managed. | «yes» Пояснение: The EntityManager::merge() method in Doctrine ORM 3 makes the passed entity managed by the EntityManager.
Raw{"answer": "yes", "explanation": "The EntityManager::merge() method in Doctrine ORM 3 makes the passed entity managed by the EntityManager."} | неверно верный: «no» | В ORM 3 merge() удалён (в vendor проекта 3.7.6 метода нет); в Doctrine 2.x merge() возвращал управляемую копию. Версия зафиксирована — ORM 3. |
T14-L4 0.48 c | Doctrine | DQL queries are written in terms of entities and their fields, not tables and columns. | «yes» Пояснение: ",
"explanation": "DQL (Domain Query Language) is an abstract language that operates on object-oriented domain models (entities and their fields), which is then translated by the persistence framework into SQL.
}
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "DQL (Domain Query Language) is an abstract language that operates on object-oriented domain models (entities and their fields), which is then translated by the persistence framework into SQL. ⏎ } | верно парсинг: текст (фолбэк) | Doctrine транслирует DQL в SQL; docs — DQL (Doctrine Query Language). |
T14-L5 0.38 c | Doctrine | What does $repository->find(999) return when no record with id 999 exists? | «null» Пояснение: When no matching record is found, the find method in Doctrine's ObjectRepository interface returns null by default.
Raw{ ⏎ "answer": "null", ⏎ "explanation": "When no matching record is found, the find method in Doctrine's ObjectRepository interface returns null by default." ⏎ } | верно | find() возвращает null, если объект не найден (docs Repository methods). |
T14-L6 0.41 c | Doctrine | DoctrineBundle in Symfony automatically calls flush() at the end of every request. | «no» Пояснение: Symfony does not automatically call flush at the end of every request; you must explicitly call it or configure the ORM to handle persistence as needed.
Raw{"answer": "false", "explanation": "Symfony does not automatically call flush at the end of every request; you must explicitly call it or configure the ORM to handle persistence as needed."} | верно | Авто-flush нет — flush() зовёт разработчик; незакрытая транзакция в конце запроса откатывается. |
T14-L7 0.42 c | Doctrine | For a managed entity, changing a property is enough: flush() commits the change without an explicit persist() — the Unit of Work tracks changes. | «yes» Пояснение: In Doctrine's Unit of Work, modifications to an already persisted entity are automatically detected, so calling flush() is sufficient to commit the changes without an explicit persist().
Raw{"answer": "yes", "explanation": "In Doctrine's Unit of Work, modifications to an already persisted entity are automatically detected, so calling flush() is sufficient to commit the changes without an explicit persist()."} | верно | Dirty checking сравнивает снимки свойств; persist нужен только новым/отсоединённым объектам. |
T14-L8 0.5 c | Doctrine | remove() executes the SQL DELETE immediately, without waiting for flush(). | «yes» Пояснение: ",
"explanation": "In Doctrine ORM, remove() is a method that marks an entity for deletion and executes the DELETE statement immediately without needing a flush().
"
}
```
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "In Doctrine ORM, remove() is a method that marks an entity for deletion and executes the DELETE statement immediately without needing a flush(). ⏎ " ⏎ } ⏎ ``` | неверно верный: «no» парсинг: текст (фолбэк) | remove() планирует удаление в Unit of Work; DELETE выполняется на flush() (docs — Deleting Objects). |
T15-L1 0.37 c | PostgreSQL | PostgreSQL uses MVCC, therefore readers block writers and writers block readers. | «no» Пояснение: PostgreSQL's MVCC allows readers and writers to operate concurrently without blocking each other, meaning readers do not block writers and vice versa.
Raw{"answer": "no", "explanation": "PostgreSQL's MVCC allows readers and writers to operate concurrently without blocking each other, meaning readers do not block writers and vice versa."} | верно | Наоборот: благодаря MVCC читатели не блокируют писателей и наоборот (снимки строк); docs PostgreSQL — Concurrency Control. |
T15-L2 0.31 c | PostgreSQL | Which SQL command shows a query's execution plan without executing the query? | «explain» Пояснение: The EXPLAIN command in SQL returns the execution plan of a query without actually running it.
Raw{"answer": "EXPLAIN", "explanation": "The EXPLAIN command in SQL returns the execution plan of a query without actually running it."} | верно | EXPLAIN без ANALYZE только строит план; проверено на PostgreSQL 17.7. |
T15-L3 0.46 c | PostgreSQL | SERIAL and GENERATED ... AS IDENTITY are just two names for the same mechanism. | «yes» Пояснение: In PostgreSQL, the SERIAL data type is syntactic sugar that creates a hidden sequence and uses an identity-like default mechanism, making it effectively equivalent to the explicit GENERATED AS IDENTITY column feature.
Raw{"answer": "yes", "explanation": "In PostgreSQL, the SERIAL data type is syntactic sugar that creates a hidden sequence and uses an identity-like default mechanism, making it effectively equivalent to the explicit GENERATED AS IDENTITY column feature."} | неверно верный: «no» | SERIAL — нестандартный макрос (sequence + DEFAULT), IDENTITY — SQL-стандарт; различаются владением и правами. Оба есть в PG 17 (проверено). |
T15-L4 0.42 c | PostgreSQL | By default, a PostgreSQL UNIQUE constraint allows only one row with NULL in the column. | «yes» Пояснение: In PostgreSQL, multiple rows with NULL values in a column are allowed to satisfy a UNIQUE constraint by default because NULL is considered not equal to any value, including itself.
Raw{"answer": "yes", "explanation": "In PostgreSQL, multiple rows with NULL values in a column are allowed to satisfy a UNIQUE constraint by default because NULL is considered not equal to any value, including itself."} | неверно верный: «no» | Наоборот: NULLS DISTINCT по умолчанию — несколько NULL допустимы; NULLS NOT DISTINCT — опция с PG 15. Проверено на PG 17.7. |
T15-L5 0.41 c | PostgreSQL | Which PostgreSQL aggregate function concatenates strings with a separator? | «string_agg» Пояснение: The string_agg() function is a PostgreSQL aggregate function used to concatenate strings, allowing an optional second argument to specify a custom separator between the concatenated values.
Raw{"answer": "string_agg", "explanation": "The string_agg() function is a PostgreSQL aggregate function used to concatenate strings, allowing an optional second argument to specify a custom separator between the concatenated values."} | верно | string_agg(значение, разделитель); проверено на PostgreSQL 17.7. |
T15-L6 0.36 c | PostgreSQL | Plain VACUUM returns the space occupied by dead tuples to the operating system. | «yes» Пояснение: A plain VACUUM command in PostgreSQL reclaims storage space used by dead tuples and returns that space to the operating system.
Raw{"answer": "yes", "explanation": "A plain VACUUM command in PostgreSQL reclaims storage space used by dead tuples and returns that space to the operating system."} | неверно верный: «no» | VACUUM помечает место для переиспользования внутри таблицы; ОС его возвращает только VACUUM FULL (с эксклюзивной блокировкой). |
T15-L7 0.42 c | PostgreSQL | Which keyword in a window function definition partitions rows into groups the function is computed over? | «partition by» Пояснение: The PARTITION BY clause is used in window function definitions to divide the result set of a query into groups called partitions over which the window function is calculated.
Raw{"answer": "PARTITION BY", "explanation": "The PARTITION BY clause is used in window function definitions to divide the result set of a query into groups called partitions over which the window function is calculated."} | верно | OVER (PARTITION BY ...); проверено на PostgreSQL 17.7. |
T15-L8 0.56 c | PostgreSQL | The READ COMMITTED isolation level protects against non-repeatable reads. | «yes» Пояснение: The READ COMMITTED isolation level prevents non-repeatable reads by ensuring that each statement in a transaction re-reads all data and that the result of repeated reads is consistent with the most recent committed version at the time of the read.
Raw{"answer": "yes", "explanation": "The READ COMMITTED isolation level prevents non-repeatable reads by ensuring that each statement in a transaction re-reads all data and that the result of repeated reads is consistent with the most recent committed version at the time of the read."} | неверно верный: «no» | READ COMMITTED допускает неповторяющееся чтение; защищает REPEATABLE READ. Проверено: SHOW transaction_isolation → read committed. |
T17-L1 0.35 c | PostgreSQL: transactions and indexes | By default, PostgreSQL wraps each single SQL statement in its own implicit transaction (autocommit). | «yes» Пояснение: In PostgreSQL, each individual SQL statement is executed within its own implicit transaction by default unless an explicit transaction block is initiated.
Raw{"answer": "yes", "explanation": "In PostgreSQL, each individual SQL statement is executed within its own implicit transaction by default unless an explicit transaction block is initiated."} | верно | Без BEGIN каждый оператор коммитится сам; docs PostgreSQL — Transactions. Проверено на PG 17. |
T17-L2 0.32 c | PostgreSQL: transactions and indexes | Which SQL command ends a transaction, committing all its changes? | «commit» Пояснение: The COMMIT command is the SQL statement used to save all changes made within a transaction to the database.
Raw{"answer": "COMMIT", "explanation": "The COMMIT command is the SQL statement used to save all changes made within a transaction to the database."} | верно | COMMIT (END — синоним). Проверено на PG 17. |
T17-L3 0.43 c | PostgreSQL: transactions and indexes | Indexes speed up more than SELECT: UPDATE and DELETE with a search on an indexed column benefit too. | «yes» Пояснение: Indexes speed up SELECT, UPDATE, and DELETE operations when the WHERE clause uses the indexed column, as they allow faster row location and filtering.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Indexes speed up SELECT, UPDATE, and DELETE operations when the WHERE clause uses the indexed column, as they allow faster row location and filtering." ⏎ } | верно | Поиск строк для изменения идёт по индексу; docs PostgreSQL — Indexes. |
T17-L4 0.44 c | PostgreSQL: transactions and indexes | To roll back part of the statements inside a transaction, PostgreSQL uses SAVEPOINT. | «yes» Пояснение: SAVEPOINT creates a named checkpoint within a transaction, allowing you to roll back only the most recent statements to that point without aborting the entire transaction.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "SAVEPOINT creates a named checkpoint within a transaction, allowing you to roll back only the most recent statements to that point without aborting the entire transaction." ⏎ } | верно | SAVEPOINT name; ROLLBACK TO name — частичный откат без отмены всей транзакции. Проверено на PG 17. |
T17-L5 0.35 c | PostgreSQL: transactions and indexes | EXPLAIN ANALYZE shows the query plan without executing the query. | «yes» Пояснение: EXPLAIN ANALYZE actually executes the query to gather real performance metrics while displaying the query plan.
Raw```json ⏎ {"answer": "yes", "explanation": "EXPLAIN ANALYZE actually executes the query to gather real performance metrics while displaying the query plan."} ⏎ ``` | неверно верный: «no» | Наоборот: ANALYZE реально выполняет запрос (с побочными эффектами!) и показывает фактические времена узлов; план без выполнения — plain EXPLAIN. |
T17-L6 0.38 c | PostgreSQL: transactions and indexes | Which PostgreSQL extension adds vector types and indexes for embedding search? | «pgvector» Пояснение: pgvector is the PostgreSQL extension that adds vector data types and supports indexing for vector similarity searches, commonly used for embedding-based AI applications.
Raw{"answer": "pgvector", "explanation": "pgvector is the PostgreSQL extension that adds vector data types and supports indexing for vector similarity searches, commonly used for embedding-based AI applications."} | верно | CREATE EXTENSION vector (проект pgvector; в проекте образ pgvector/pgvector:pg17). |
T17-L7 0.27 c | PostgreSQL: transactions and indexes | A partial index (CREATE INDEX ... WHERE ...) is built only over rows satisfying the condition. | «yes» Пояснение: Partial indexes only store data for rows that satisfy the specified WHERE condition.
Raw{"answer": "yes", "explanation": "Partial indexes only store data for rows that satisfy the specified WHERE condition."} | верно | docs PostgreSQL — Partial Indexes; типичный кейс — индекс по «активным» записям. |
T17-L8 0.39 c | PostgreSQL: transactions and indexes | The SERIALIZABLE level in PostgreSQL is implemented by locking the rows a transaction reads. | «no» Пояснение: The SERIALIZABLE level in PostgreSQL is implemented using snapshot isolation and detecting conflicts, not by locking the rows that a transaction reads.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "The SERIALIZABLE level in PostgreSQL is implemented using snapshot isolation and detecting conflicts, not by locking the rows that a transaction reads." ⏎ } | верно | SSI (Serializable Snapshot Isolation): предикатные блокировки на снимках, не блокировки прочитанных строк; docs PostgreSQL. |
T19-L1 0.37 c | HTTP and REST API | HTTP status 201 means the request resulted in a new resource being created. | «yes» Пояснение: HTTP status 201 indicates that the request was successful and a new resource has been created.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "HTTP status 201 indicates that the request was successful and a new resource has been created." ⏎ } | верно | 201 Created; обычно на POST, часто с Location; RFC 9110. |
T19-L2 0.33 c | HTTP and REST API | Which HTTP status means a successful request with an empty response body (e.g. after DELETE)? | «204» Пояснение: 204 No Content indicates a successful request with no response body.
Raw{ ⏎ "answer": 204, ⏎ "explanation": "204 No Content indicates a successful request with no response body." ⏎ } | верно | 204 No Content; RFC 9110. |
T19-L3 0.36 c | HTTP and REST API | The DELETE method is idempotent per the HTTP specification: repeating the request for the same resource does not change the outcome. | «yes» Пояснение: The HTTP specification defines the DELETE method as idempotent, meaning that repeated identical requests have the same effect as a single request.
Raw{"answer": "yes", "explanation": "The HTTP specification defines the DELETE method as idempotent, meaning that repeated identical requests have the same effect as a single request."} | верно | RFC 9110: DELETE идемпотентен (как PUT); идемпотентность ≠ безопасность — ресурс удаляется при первом вызове. |
T19-L4 0.35 c | HTTP and REST API | The Access-Control-Allow-Origin header is sent by the client so that the server agrees to accept requests from another origin. | «no» Пояснение: The Access-Control-Allow-Origin header is actually sent by the server to indicate whether it will accept requests from a specific origin.
Raw{"answer": "no", "explanation": "The Access-Control-Allow-Origin header is actually sent by the server to indicate whether it will accept requests from a specific origin."} | верно | Наоборот: заголовок шлёт СЕРВЕР в ответе, разрешая браузеру cross-origin запрос (CORS); в проекте nelmio/cors-bundle. |
T19-L5 0.32 c | HTTP and REST API | Status 429 Too Many Requests is used when a client exceeds a rate limit. | «yes» Пояснение: HTTP 429 is specifically designated for indicating that a client has exceeded the allowed rate of requests.
Raw{"answer": "yes", "explanation": "HTTP 429 is specifically designated for indicating that a client has exceeded the allowed rate of requests."} | верно | 429 (+ Retry-After); RFC 6585. В проекте symfony/rate-limiter. |
T19-L6 0.29 c | HTTP and REST API | 5xx codes mean a client error, while 4xx means a server-side error. | «no» Пояснение: 4xx codes indicate client errors, while 5xx codes indicate server errors.
Raw{"answer": "no", "explanation": "4xx codes indicate client errors, while 5xx codes indicate server errors."} | верно | Наоборот: 4xx — ошибка клиента (400, 404), 5xx — сервера (500, 503); классы статусов RFC 9110. |
T19-L7 0.29 c | HTTP and REST API | Which HTTP header indicates the MIME type of the request or response body? | «content-type» Пояснение: The Content-Type header specifies the media type of the request or response body.
Raw{"answer": "Content-Type", "explanation": "The Content-Type header specifies the media type of the request or response body."} | верно | Content-Type: application/json и т.п. |
T19-L8 0.37 c | HTTP and REST API | PATCH is not required to be idempotent per RFC 5789, unlike PUT. | «no» Пояснение: RFC 5789 explicitly defines PATCH as an idempotent method.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "RFC 5789 explicitly defines PATCH as an idempotent method." ⏎ } ⏎ ``` | неверно верный: «yes» | RFC 5789 прямо оговаривает: PATCH не гарантированно идемпотентен; PUT идемпотентен. |
T20-L1 0.51 c | Security and OAuth | Checking a password by comparing its hash to the stored hash with a plain == is sufficient. | «no» Пояснение: Using a standard string comparison (==) is not sufficient for password verification because it is not constant-time and is susceptible to timing attacks; you must use a dedicated timing-safe function like hash_equals().
Raw{ ⏎ "answer": "false", ⏎ "explanation": "Using a standard string comparison (==) is not sufficient for password verification because it is not constant-time and is susceptible to timing attacks; you must use a dedicated timing-safe function like hash_equals()." ⏎ } | верно | Нужна постоянновременная проверка (password_verify) — timing-атаки; соль и алгоритм уже внутри хеша. |
T20-L2 0.46 c | Security and OAuth | A CSRF token is issued by the server (bound to the session) and verified server-side on unsafe requests (POST etc.). | «yes» Пояснение: CSRF tokens are typically generated by the server, associated with the user's session, and validated server-side on state-changing requests to prevent cross-site request forgery.
Raw{"answer": "yes", "explanation": "CSRF tokens are typically generated by the server, associated with the user's session, and validated server-side on state-changing requests to prevent cross-site request forgery."} | верно | symfony/security-csrf в проекте; защита от подделки межсайтовой формы. |
T20-L3 0.39 c | Security and OAuth | Which HTTP header enables the CSP (Content Security Policy) policy? | «content-security-policy» Пояснение: The Content-Security-Policy HTTP header is used to specify the security rules that a web server enforces for the loading of a webpage.
Raw{"answer":"Content-Security-Policy","explanation":"The Content-Security-Policy HTTP header is used to specify the security rules that a web server enforces for the loading of a webpage."} | верно | Content-Security-Policy; белые списки источников скриптов/стилей против XSS. |
T20-L4 0.44 c | Security and OAuth | OAuth 2.0 is an authentication protocol: the access token tells you who the user is. | «no» Пояснение: OAuth 2.0 is primarily an authorization protocol for granting access to resources on behalf of a user, and the access token represents delegated permissions rather than identifying the user's identity.
Raw{"answer": "no", "explanation": "OAuth 2.0 is primarily an authorization protocol for granting access to resources on behalf of a user, and the access token represents delegated permissions rather than identifying the user's identity."} | верно | OAuth 2.0 — авторизация/делегирование доступа; аутентификацию добавляет OpenID Connect. В проекте knpuniversity/oauth2-client-bundle (yandex/github/google). |
T20-L5 0.34 c | Security and OAuth | XSS is prevented by validating input on the server before writing it to the database. | «no» Пояснение: XSS is prevented by output encoding at the point of use, not by server-side input validation before storing data.
Raw{"answer": "false", "explanation": "XSS is prevented by output encoding at the point of use, not by server-side input validation before storing data."} | верно | XSS лечится контекстным экранированием НА ВЫВОДЕ (Twig autoescape, CSP); валидация ввода не покрывает все контексты вывода. |
T20-L6 0.51 c | Security and OAuth | In the OAuth 2.0 authorization code flow, which parameter arrives at the redirect_uri and is exchanged for an access token? | «code» Пояснение: In the OAuth 2.0 authorization code flow, the authorization server redirects the user's browser to the redirect_uri with the authorization code parameter, which is then exchanged for an access token.
Raw{ ⏎ "answer": "code", ⏎ "explanation": "In the OAuth 2.0 authorization code flow, the authorization server redirects the user's browser to the redirect_uri with the authorization code parameter, which is then exchanged for an access token." ⏎ } | верно | Параметр code; обмен на токен POST-ом на /token с client_secret. |
T20-L7 0.43 c | Security and OAuth | A refresh token lives longer than an access token and allows obtaining a new access token without the user logging in again. | «yes» Пояснение: Refresh tokens are designed with a longer expiration than access tokens and are used to securely request a new access token without requiring the user to re-authenticate.
Raw{"answer": "yes", "explanation": "Refresh tokens are designed with a longer expiration than access tokens and are used to securely request a new access token without requiring the user to re-authenticate."} | верно | Стандартная схема OAuth/OIDC: короткий access + длинный refresh. |
T20-L8 0.43 c | Security and OAuth | A password salt must be kept secret: without it the hash cannot be verified. | «no» Пояснение: Password salts are typically stored in plain text alongside the hash (or in the database row) to enable verification; it is the password and the hash that must be kept secret.
Raw{"answer": "no", "explanation": "Password salts are typically stored in plain text alongside the hash (or in the database row) to enable verification; it is the password and the hash that must be kept secret."} | верно | Соль хранится открыто (password_hash включает её в строку хеша); секретность соли не нужна. |
T18-L1 0.34 c | Testing: PHPUnit | PHPUnit runs test methods of any class — extending TestCase is not required. | «no» Пояснение: PHPUnit test methods must be declared in classes that extend PHPUnit\Framework\TestCase to be recognized and executed as tests.
Raw{"answer": "no", "explanation": "PHPUnit test methods must be declared in classes that extend PHPUnit\\Framework\\TestCase to be recognized and executed as tests."} | верно | Тестом считается метод класса, наследующего TestCase (PHPUnit 10). |
T18-L2 0.4 c | Testing: PHPUnit | In PHPUnit, setUp() runs once before all tests of the class. | «no» Пояснение: setUp() (or setUpBeforeClass in newer contexts) runs before each individual test method, not just once per class.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "setUp() (or setUpBeforeClass in newer contexts) runs before each individual test method, not just once per class." ⏎ } | верно | setUp() — перед КАЖДЫМ тестом; один раз на класс — setUpBeforeClass(). Проверено живым счётчиком на PHPUnit 10.5. |
T18-L3 0.32 c | Testing: PHPUnit | A data provider lets a test run with exactly one set of arguments. | «no» Пояснение: A data provider in PHP's PHPUnit lets a test run with multiple sets of arguments, not just one.
Raw{"answer": "no", "explanation": "A data provider in PHP's PHPUnit lets a test run with multiple sets of arguments, not just one."} | верно | Наоборот: наборов может быть сколько угодно — тест выполняется по разу на каждый. Проверено на PHPUnit 10.5 (#[DataProvider]). |
T18-L4 0.39 c | Testing: PHPUnit | Which PHPUnit method declares an expectation that an exception of a given class is thrown? | «expectexception()» Пояснение: expectException() is the PHPUnit method used to declare an expectation for a specific exception class to be thrown during a test.
Raw{ ⏎ "answer": "expectException()", ⏎ "explanation": "expectException() is the PHPUnit method used to declare an expectation for a specific exception class to be thrown during a test." ⏎ } | верно | $this->expectException(\LogicException::class); проверено на PHPUnit 10.5. |
T18-L5 0.41 c | Testing: PHPUnit | In PHPUnit, a stub verifies which methods were called on it, while a mock only returns data. | «no» Пояснение: It is the opposite: a mock verifies which methods were called on it, while a stub simply returns predefined data without verifying calls.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "It is the opposite: a mock verifies which methods were called on it, while a stub simply returns predefined data without verifying calls." ⏎ } | верно | Наоборот: стаб подставляет данные, мок проверяет взаимодействия (createStub/createMock); docs PHPUnit — Test Doubles. |
T18-L6 0.38 c | Testing: PHPUnit | In PHPUnit 10+, the recommended way to pass data to a test is the #[DataProvider] attribute (the @dataProvider annotation is deprecated). | «yes» Пояснение: PHPUnit 10 deprecated annotations in favor of PHP 8 attributes, making #[DataProvider] the recommended approach.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "PHPUnit 10 deprecated annotations in favor of PHP 8 attributes, making #[DataProvider] the recommended approach." ⏎ } | верно | Аннотация ещё парсится в PHPUnit 10/11 (AnnotationParser в 10.5.66), удаление — в 12; атрибут — стандарт. |
T18-L7 0.42 c | Testing: PHPUnit | PHPUnit does not allow one test to depend on the result of another. | «no» Пояснение: PHPUnit provides mechanisms like setUp/tearDown and fixtures, but it does not have a built-in feature to make one test method depend on the output of another test method.
Raw{"answer": "no", "explanation": "PHPUnit provides mechanisms like setUp/tearDown and fixtures, but it does not have a built-in feature to make one test method depend on the output of another test method."} | верно | Зависимости есть: #[Depends] — зависимый тест не запустится, еслиProducer упал. |
T18-L8 0.27 c | Testing: PHPUnit | Which PHPUnit command-line option makes tests run in random order? | «--randomize» Пояснение: The --randomize flag shuffles the test cases before execution.
Raw{"answer": "--randomize", "explanation": "The --randomize flag shuffles the test cases before execution."} | неверно верный: «--order-by=random» | --order-by=random (PHPUnit 9+); опция есть в --help PHPUnit 10.5 (проектная). |
T01-L9 2.43 c | Syntax and operators | What does this code output?
```php
echo intdiv(7, 2) . intdiv(-7, 2);
``` | «3-4» Пояснение: intdiv(7,2) is 3 and intdiv(-7,2) truncates toward zero to -3, so the output is the string "3-4".
Raw{ ⏎ "answer": "3-4", ⏎ "explanation": "intdiv(7,2) is 3 and intdiv(-7,2) truncates toward zero to -3, so the output is the string \"3-4\"." ⏎ } | неверно верный: «3-3» | intdiv truncates toward zero: intdiv(-7, 2) = -3, not -4. |
T01-L10 0.5 c | Syntax and operators | What does this code output?
```php
echo -3 ** 2;
``` | «-9» Пояснение: The unary minus operator binds more tightly than the exponentiation operator in PHP, so the expression is evaluated as (-3) ** 2, which equals -9.
Raw{ ⏎ "answer": -9, ⏎ "explanation": "The unary minus operator binds more tightly than the exponentiation operator in PHP, so the expression is evaluated as (-3) ** 2, which equals -9." ⏎ } | верно | ** is right-associative and binds tighter than unary minus: -(3²). |
T02-L9 0.59 c | Types and comparisons | What does this code output?
```php
echo '1e1' == '10' ? 'true' : 'false';
``` | «true» Пояснение: In PHP, the string '1e1' is numerically equal to 10, so the loose comparison '1e1' == '10' evaluates to true, causing the ternary operator to output 'true'.
Raw{ ⏎ "answer": "true", ⏎ "explanation": "In PHP, the string '1e1' is numerically equal to 10, so the loose comparison '1e1' == '10' evaluates to true, causing the ternary operator to output 'true'." ⏎ } | верно | Both strings are numeric — compared as numbers: 10 == 10. |
T02-L10 0.42 c | Types and comparisons | What does this code output?
```php
switch ('a') {
case 0: echo 'zero'; break;
default: echo 'other';
}
``` | «other» Пояснение: PHP switch cases use loose comparison, so the string 'a' is not equal to 0, causing the default case to execute.
Raw{"answer": "other", "explanation": "PHP switch cases use loose comparison, so the string 'a' is not equal to 0, causing the default case to execute."} | верно | PHP 8: 'a' == 0 → false (used to be true) — default fires. |
T03-L9 0.41 c | Strings | What does this code output?
```php
echo strtr('abc', ['a' => '1', 'ab' => '2']);
``` | «1bc» Пояснение: strtr with an array performs multiple search-and-replace operations where 'a' is replaced by '1' first, leaving '1bc'.
Raw{"answer": "1bc", "explanation": "strtr with an array performs multiple search-and-replace operations where 'a' is replaced by '1' first, leaving '1bc'."} | неверно верный: «2c» | strtr with an array prefers the longest matching key. |
T03-L10 0.47 c | Strings | What does this code output?
```php
echo '[' . substr('hello', -10) . ']';
``` | «[hello]» Пояснение: substr('hello', -10) returns the whole string 'hello' because the length -10 is longer than the string, so it prepends '[' and appends ']'.
Raw{"answer": "[hello]", "explanation": "substr('hello', -10) returns the whole string 'hello' because the length -10 is longer than the string, so it prepends '[' and appends ']'."} | верно | A negative start beyond the string is clamped to the beginning. |
T04-L9 0.48 c | Arrays | What does this code output?
```php
$a = ['k' => 1, 'n' => 2];
$b = ['k' => 9, 'm' => 3];
echo implode(',', array_keys($a + $b));
``` | «k,n» Пояснение: The + operator keeps existing keys from the left array and adds only new keys from the right array, so the keys are 'k' and 'n'.
Raw{ ⏎ "answer": "k,n", ⏎ "explanation": "The + operator keeps existing keys from the left array and adds only new keys from the right array, so the keys are 'k' and 'n'." ⏎ } | неверно верный: «k,n,m» | The + operator: on duplicate string keys the left array wins. |
T04-L10 0.47 c | Arrays | What does this code output?
```php
$a = [[1, 'x', 2], [2, 'y', 1], [3, 'z', 2]];
usort($a, fn($p, $q) => $p[2] <=> $q[2]);
echo implode('', array_column($a, 1));
``` | «xzy» Пояснение: The code sorts the array by the third element (values 2,1,2) using a stable sort, then extracts the second element from each row.
Raw{"answer": "xzy", "explanation": "The code sorts the array by the third element (values 2,1,2) using a stable sort, then extracts the second element from each row."} | неверно верный: «yxz» | Sorts are stable since 8.0: x and z keep their order on a tie. |
T05-L10 0.57 c | Functions and closures | What does this code output?
```php
function f(int $a, int $b): int
{
return $a - $b;
}
echo f(...['b' => 1, 'a' => 5]);
``` | «4» Пояснение: The spread operator with named arguments unpacks 'a' and 'b' in the order they are defined in the function signature, resulting in f(5, 1) which outputs 4.
Raw{ ⏎ "answer": "4", ⏎ "explanation": "The spread operator with named arguments unpacks 'a' and 'b' in the order they are defined in the function signature, resulting in f(5, 1) which outputs 4." ⏎ } | верно | String keys of a spread array become named arguments. |
T05-L9 0.63 c | Functions and closures | What does this code output?
```php
class P
{
private int $v = 3;
public function g(): int { return $this->v; }
}
$p = new P;
$f = $p->g(...);
$p = null;
echo $f();
``` | «3» Пояснение: The function g() is bound to the P object instance at the time it is called, and the closure captures the object, so even after $p is set to null, the object remains alive and g() returns the value of $v, which is 3.
Raw{"answer": 3, "explanation": "The function g() is bound to the P object instance at the time it is called, and the closure captures the object, so even after $p is set to null, the object remains alive and g() returns the value of $v, which is 3."} | верно | First-class callable syntax binds $this at creation time. |
T06-L9 0.5 c | OOP: classes and inheritance | What does this code output?
```php
class A
{
public function who(): string { return static::class; }
}
class B extends A {}
echo (new B)->who();
``` | «b» Пояснение: static::class refers to the late static binding, which returns the class name where the method was actually called from, which is B.
Raw```json ⏎ { ⏎ "answer": "B", ⏎ "explanation": "static::class refers to the late static binding, which returns the class name where the method was actually called from, which is B." ⏎ } ⏎ ``` | верно | Late static binding: static::class is the receiver's class. |
T06-L10 0.4 c | OOP: classes and inheritance | What does this code output on PHP 8.5?
```php
class C
{
public int $x = 0 {
set { $this->x = $value * 2; }
}
}
$c = new C;
$c->x = 5;
echo $c->x;
``` | «10» Пояснение: PHP 8.5 introduced property hooks, so the setter doubles the value to 10 before storing it.
Raw{"answer": 10, "explanation": "PHP 8.5 introduced property hooks, so the setter doubles the value to 10 before storing it."} | верно | Inside the set hook, $this->x writes the backing store (no recursion): 5*2. |
T07-L9 0.59 c | Interfaces, traits, enum | What does this code output?
```php
trait TA
{
public function f(): string { return 'A'; }
}
trait TB
{
public function f(): string { return 'B'; }
}
class TC
{
use TA, TB { TB::f insteadof TA; TA::f as g; }
}
echo (new TC)->f() . (new TC)->g();
``` | «ba» Пояснение: The `TB::f insteadof TA` conflict resolution makes `f()` from trait `TB` take precedence, returning 'B', and `TA::f` is aliased as `g()` returning 'A'.
Raw{"answer": "BA", "explanation": "The `TB::f insteadof TA` conflict resolution makes `f()` from trait `TB` take precedence, returning 'B', and `TA::f` is aliased as `g()` returning 'A'."} | верно | insteadof picks the implementation; as keeps the other under an alias. |
T07-L10 0.46 c | Interfaces, traits, enum | What does this code output?
```php
trait Counter
{
public static int $n = 0;
}
class CX { use Counter; }
class CY { use Counter; }
CX::$n = 1;
echo CY::$n;
``` | «1» Пояснение: Static properties declared in a trait are shared across all classes that use it, so assigning CX::$n also updates CY::$n.
Raw{ ⏎ "answer": 1, ⏎ "explanation": "Static properties declared in a trait are shared across all classes that use it, so assigning CX::$n also updates CY::$n." ⏎ } | неверно верный: «0» | A trait's static property is copied into each consuming class. |
T08-L10 0.37 c | Exceptions and errors | What does this code output?
```php
function f(): int
{
try { return 1; } finally { return 2; }
}
echo f();
``` | «1» Пояснение: In PHP, a return statement in a try block is executed before any finally block, so the function returns 1.
Raw{"answer":"1","explanation":"In PHP, a return statement in a try block is executed before any finally block, so the function returns 1."} | неверно верный: «2» | A return in finally overrides the return from try. |
T08-L9 0.52 c | Exceptions and errors | What does this code output?
```php
try {
try {
throw new RuntimeException('first');
} finally {
throw new LogicException('second');
}
} catch (LogicException $e) {
echo $e->getMessage();
}
``` | «second» Пояснение: The RuntimeException is caught by the finally block, which throws a LogicException that propagates out of the inner try-finally and is caught by the outer catch block, echoing 'second'.
Raw{ ⏎ "answer": "second", ⏎ "explanation": "The RuntimeException is caught by the finally block, which throws a LogicException that propagates out of the inner try-finally and is caught by the outer catch block, echoing 'second'." ⏎ } | верно | An exception from finally replaces the in-flight one — the last thrown is caught. |
T09-L9 0.33 c | Namespaces and autoloading | What does this code output?
```php
namespace N;
use App\Foo as Baz;
echo Baz::class . '|' . \Baz::class;
``` | «app\foo|baz» Пояснение: The alias resolves to App\Foo, while the global name is Baz.
Raw{"answer":"App\\Foo|Baz","explanation":"The alias resolves to App\\Foo, while the global name is Baz."} | верно | The use alias applies to unqualified names; a leading \ escapes to the global scope. |
T09-L10 0.47 c | Namespaces and autoloading | What does this code output?
```php
namespace Ns;
class Foo {}
$c = 'Foo';
echo (class_exists($c) ? 'yes' : 'no')
. (class_exists(__NAMESPACE__ . '\\' . $c) ? 'yes' : 'no');
``` | «yes» Пояснение: class_exists('Foo') returns false, and class_exists('Ns\Foo') returns true, producing the concatenated string 'yes'.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "class_exists('Foo') returns false, and class_exists('Ns\\Foo') returns true, producing the concatenated string 'yes'." ⏎ } ⏎ ``` | неверно верный: «noyes» | Dynamic names are not resolved against the namespace — 'Foo' is the global class. |
T10-L9 0.68 c | References and scope | What does this code output?
```php
$a = [1, 2, 3];
foreach ($a as &$v) {}
$v = 99;
echo implode(',', $a);
``` | «1,2,99» Пояснение: The foreach loop with `&$v` makes $v a reference to each element of $a, and after the loop $v still references the last element, so assigning $v = 99 changes the third element of the array.
Raw```json ⏎ {"answer": "1,2,99", "explanation": "The foreach loop with `&$v` makes $v a reference to each element of $a, and after the loop $v still references the last element, so assigning $v = 99 changes the third element of the array."} ⏎ ``` | верно | After a by-ref foreach, $v remains a reference to the last element. |
T10-L10 0.48 c | References and scope | What does this code output?
```php
class A
{
public function inc(): int
{
static $n = 0;
return ++$n;
}
}
class B extends A {}
$a = new A;
$b = new B;
$a->inc();
$b->inc();
echo $a->inc();
``` | «3» Пояснение: The static variable is shared between all instances of A and B, so the first two calls return 1 and 2, and the third call returns 3.
Raw{"answer": 3, "explanation": "The static variable is shared between all instances of A and B, so the first two calls return 1 and 2, and the third call returns 3."} | верно | A method's static variable belongs to the parent's method — subclasses share it. |
T11-L9 0.46 c | Generators, iterators, SPL | What does this code output?
```php
function g(): Generator
{
$x = yield 1;
return $x + 1;
}
$g = g();
$g->send(10);
echo $g->getReturn();
``` | «11» Пояснение: The initial send(10) executes the generator up to the return statement, causing $x to be 10 and returning 11.
Raw{"answer": "11", "explanation": "The initial send(10) executes the generator up to the return statement, causing $x to be 10 and returning 11."} | верно | send() resumes the generator: $x = 10, return 10+1. |
T11-L10 0.49 c | Generators, iterators, SPL | What does this code output?
```php
function inner(): Generator
{
yield 1;
yield 2;
return 'ok';
}
function outer(): Generator
{
$r = yield from inner();
yield $r;
}
echo implode(',', iterator_to_array(outer()));
``` | «1,2» Пояснение: yield from forwards the yielded values of the inner generator to outer, so only 1 and 2 are yielded before the inner's return value is ignored by outer's subsequent yield.
Raw{"answer":"1,2", "explanation":"yield from forwards the yielded values of the inner generator to outer, so only 1 and 2 are yielded before the inner's return value is ignored by outer's subsequent yield."} | неверно верный: «ok,2» | yield from does not advance the outer auto-key: yield $r gets key 0 and overwrites the 1 — 'ok' comes out first. |
T12-L9 0.47 c | Configuration and security | What does this code output?
```php
$hash = password_hash('x', PASSWORD_BCRYPT, ['cost' => 4]);
echo password_needs_rehash($hash, PASSWORD_BCRYPT, ['cost' => 4]) ? 'yes' : 'no';
echo password_needs_rehash($hash, PASSWORD_BCRYPT, ['cost' => 5]) ? 'yes' : 'no';
``` | «no yes» Пояснение: The first call returns false because the password is already hashed with cost 4, while the second returns true because the desired cost is higher than the existing one.
Raw{"answer": "no yes", "explanation": "The first call returns false because the password is already hashed with cost 4, while the second returns true because the desired cost is higher than the existing one."} | неверно верный: «noyes» | password_needs_rehash compares the hash's options with the target: cost 4 = 4 → 'no', cost 5 ≠ 4 → 'yes'. |
T12-L10 0.64 c | Configuration and security | What does this code output on PHP 8.5?
```php
echo (E_ALL & 2048) === 0 ? 'strict-out' : 'strict-in';
``` | «strict-out» Пояснение: E_ALL is 32767, which is not a multiple of 2048, so (E_ALL & 2048) is not 0, thus the expression evaluates to 'strict-out'.
Raw```json ⏎ {"answer": "strict-out", "explanation": "E_ALL is 32767, which is not a multiple of 2048, so (E_ALL & 2048) is not 0, thus the expression evaluates to 'strict-out'."} ⏎ ``` | верно | Since PHP 8.4, E_STRICT is out of E_ALL: the 2048 bit is unset → 'strict-out' (2048 is the historical E_STRICT bit). |
T13-L9 0.4 c | Symfony | What does this code output?
```php
use Symfony\Component\HttpFoundation\Request;
$r = Request::create('/demo', 'GET', [], [], [], ['HTTP_X_TOKEN' => 'abc']);
echo $r->headers->get('X-Token') === 'abc' ? 'mapped' : 'missing';
``` | «mapped» Пояснение: Symfony normalizes the HTTP header name, so get('X-Token') returns the value 'abc' set as HTTP_X_TOKEN.
Raw{"answer":"mapped","explanation":"Symfony normalizes the HTTP header name, so get('X-Token') returns the value 'abc' set as HTTP_X_TOKEN."} | верно | The literal comparison requires knowing the mapping: HttpFoundation turns HTTP_X_TOKEN into the X-Token header (case-insensitive); without it the answer is 'missing'. |
T13-L10 0.55 c | Symfony | What does this code output?
```php
use Symfony\Component\EventDispatcher\EventDispatcher;
use Symfony\Contracts\EventDispatcher\Event;
$d = new EventDispatcher();
$out = '';
$d->addListener('e', function () use (&$out) { $out .= 'B'; }, 10);
$d->addListener('e', function () use (&$out) { $out .= 'A'; });
$d->addListener('e', function () use (&$out) { $out .= 'C'; }, 5);
$d->dispatch(new Event(), 'e');
echo $out;
``` | «cba» Пояснение: Listeners are called in descending order of their priority (default is 0), so C (5), B (10), then A (0) append to $out.
Raw{ ⏎ "answer": "CBA", ⏎ "explanation": "Listeners are called in descending order of their priority (default is 0), so C (5), B (10), then A (0) append to $out." ⏎ } | неверно верный: «bca» | Listeners run by descending priority: 10 (B), 5 (C), 0 (A). |
T14-L10 0.49 c | Doctrine | Given: Doctrine ORM 3, an EntityManager on in-memory SQLite, entity User with an auto-increment primary key. The users table is empty. What does this code output?
```php
$u = new User(name: 'A');
$em->persist($u);
$em->flush();
$a = $em->find(User::class, $u->getId());
$b = $em->find(User::class, $u->getId());
echo spl_object_id($a) === spl_object_id($b) ? 'same' : 'diff';
``` | «same» Пояснение: Doctrine ORM maintains a First Level Cache in the EntityManager, so both find() calls for the same identifier return the same persistent object instance.
Raw{ ⏎ "answer": "same", ⏎ "explanation": "Doctrine ORM maintains a First Level Cache in the EntityManager, so both find() calls for the same identifier return the same persistent object instance." ⏎ } | верно | Identity map: a second find for the same id returns the same instance. |
T14-L9 0.49 c | Doctrine | Given: Doctrine ORM 3, an EntityManager on in-memory SQLite, entity User with an auto-increment primary key. The users table is empty. What does this code output?
```php
$u = new User(name: 'B');
$em->persist($u);
$em->remove($u);
$em->flush();
echo count($em->getConnection()->fetchAllAssociative('SELECT * FROM users'));
``` | «0» Пояснение: The entity is persisted and then removed before the flush, so Doctrine does not execute an INSERT and the table remains empty.
Raw```json ⏎ { ⏎ "answer": 0, ⏎ "explanation": "The entity is persisted and then removed before the flush, so Doctrine does not execute an INSERT and the table remains empty." ⏎ } ⏎ ``` | верно | The unit of work schedules INSERT at flush: remove after persist cancels it. |
T15-L10 0.42 c | PostgreSQL | What does this SQL query return (PostgreSQL 17)?
```sql
CREATE TEMP TABLE t (x int);
INSERT INTO t VALUES (1), (NULL);
SELECT count(x) FROM t;
``` | «1» Пояснение: In PostgreSQL, COUNT(x) counts non-NULL values in column x, so with rows 1 and NULL it returns 1.
Raw{"answer": 1, "explanation": "In PostgreSQL, COUNT(x) counts non-NULL values in column x, so with rows 1 and NULL it returns 1."} | верно | count(column) skips NULLs; count(*) would return 2. |
T15-L9 0.45 c | PostgreSQL | What does this SQL query return (PostgreSQL 17)?
```sql
CREATE TEMP TABLE t (id int, x int);
INSERT INTO t VALUES (1, 10), (2, 20), (3, 30);
SELECT string_agg(s::text, ',' ORDER BY id) FROM (
SELECT id, sum(x) OVER (ORDER BY id) AS s FROM t
) q;
``` | «10,30,60» Пояснение: The window function sums x cumulatively (10, 30, 60) and string_agg joins them in that order.
Raw{"answer": "10,30,60", "explanation": "The window function sums x cumulatively (10, 30, 60) and string_agg joins them in that order."} | верно | With ORDER BY the default window frame is running (start to current row). |
T16-L9 0.48 c | Symfony: Messenger | What does this code output?
```php
use Symfony\Component\Messenger\MessageBus;
use Symfony\Component\Messenger\Middleware\MiddlewareInterface;
use Symfony\Component\Messenger\Middleware\StackInterface;
use Symfony\Component\Messenger\Envelope;
final class Trace implements MiddlewareInterface
{
public function __construct(private string $tag) {}
public function handle(Envelope $e, StackInterface $stack): Envelope
{
echo $this->tag;
return $stack->next()->handle($e, $stack);
}
}
$bus = new MessageBus([new Trace('M1'), new Trace('M2')]);
$bus->dispatch(new Envelope(new stdClass()));
``` | «m1m2» Пояснение: The middleware chain executes in the order given, so M1 echoes first, then M2, producing the concatenated string M1M2.
Raw{"answer": "M1M2", "explanation": "The middleware chain executes in the order given, so M1 echoes first, then M2, producing the concatenated string M1M2."} | верно | The first-added middleware runs first (outermost). |
T16-L10 0.7 c | Symfony: Messenger | What does this code output?
```php
use Symfony\Component\Messenger\MessageBus;
use Symfony\Component\Messenger\Middleware\HandleMessageMiddleware;
use Symfony\Component\Messenger\Handler\HandlersLocator;
use Symfony\Component\Messenger\Handler\HandlerDescriptor;
use Symfony\Component\Messenger\Envelope;
class Ping {}
$n = 0;
$d1 = new HandlerDescriptor(function (Ping $m) use (&$n) { $n += 1; }, ['alias' => 'h1']);
$d2 = new HandlerDescriptor(function (Ping $m) use (&$n) { $n += 10; }, ['alias' => 'h2']);
$bus = new MessageBus([
new HandleMessageMiddleware(new HandlersLocator([Ping::class => [$d1, $d2]])),
]);
$bus->dispatch(new Envelope(new Ping()));
echo $n;
``` | «11» Пояснение: HandlersLocator by default calls all registered handlers for a message type in the order they are provided, so both the first handler ($n += 1) and the second handler ($n += 10) execute, resulting in $n = 11.
Raw{ ⏎ "answer": 11, ⏎ "explanation": "HandlersLocator by default calls all registered handlers for a message type in the order they are provided, so both the first handler ($n += 1) and the second handler ($n += 10) execute, resulting in $n = 11." ⏎ } | верно | All registered handlers of the message run: 1 + 10 = 11. |
T17-L9 0.36 c | PostgreSQL: transactions and indexes | What does this SQL query return (PostgreSQL 17)?
```sql
CREATE TEMP TABLE t (a int);
CREATE UNIQUE INDEX ON t (a);
INSERT INTO t VALUES (1) ON CONFLICT DO NOTHING;
INSERT INTO t VALUES (1) ON CONFLICT DO NOTHING;
SELECT count(*) FROM t;
``` | «1» Пояснение: ON CONFLICT DO NOTHING suppresses the second duplicate insert, leaving one row in t.
Raw{"answer": 1, "explanation": "ON CONFLICT DO NOTHING suppresses the second duplicate insert, leaving one row in t."} | верно | ON CONFLICT DO NOTHING skips the duplicate: one insert. |
T17-L10 0.48 c | PostgreSQL: transactions and indexes | What does this sequence of psql commands output?
```sql
BEGIN;
CREATE TEMP TABLE t (a int, UNIQUE (a) DEFERRABLE INITIALLY DEFERRED);
INSERT INTO t VALUES (1);
INSERT INTO t VALUES (1);
SELECT count(*) FROM t;
``` | «2» Пояснение: A UNIQUE constraint that is DEFERRABLE INITIALLY DEFERRED is checked only at the end of the transaction, so both inserts succeed.
Raw{ ⏎ "answer": 2, ⏎ "explanation": "A UNIQUE constraint that is DEFERRABLE INITIALLY DEFERRED is checked only at the end of the transaction, so both inserts succeed." ⏎ } | верно | DEFERRED postpones the uniqueness check to COMMIT — count sees 2 rows. |
T18-L9 0.41 c | Testing: PHPUnit | How many tests will this command run?
```php
use PHPUnit\Framework\TestCase;
use PHPUnit\Framework\Attributes\DataProvider;
final class CalcTest extends TestCase
{
public static function prov(): array
{
return [[1], [2], [3]];
}
#[DataProvider('prov')]
public function test_sum(int $x): void
{
$this->assertTrue($x > 0);
}
#[DataProvider('prov')]
public function test_sum_abs(int $x): void
{
$this->assertTrue($x > 0);
}
public function test_other(): void
{
$this->assertTrue(true);
}
}
```
Command: `phpunit CalcTest.php --filter test_sum` (PHPUnit 10.5) | «6» Пояснение: The --filter test_sum matches both test_sum and test_sum_abs, and each has 3 data provider entries.
Raw{"answer": 6, "explanation": "The --filter test_sum matches both test_sum and test_sum_abs, and each has 3 data provider entries."} | верно | --filter is a substring match: test_sum also matches test_sum_abs (3+3 datasets). |
T18-L10 0.79 c | Testing: PHPUnit | How many tests will this command run, and how many of them will fail? Answer with two comma-separated numbers (ran, failed).
```php
use PHPUnit\Framework\TestCase;
use PHPUnit\Framework\Attributes\DataProvider;
final class Calc2Test extends TestCase
{
public function prov(): array
{
return [[1], [-1]];
}
#[DataProvider('prov')]
public function test_x(int $x): void
{
$this->assertTrue($x > 0);
}
}
```
Command: `phpunit Calc2Test.php` (PHPUnit 10.5) | «2, 1» Пояснение: The @DataProvider provides two datasets ([1] and [-1]), so two test cases are executed. The first dataset ($x = 1) passes because 1 > 0, while the second dataset ($x = -1) fails because -1 > 0 is false.
Raw```json ⏎ { ⏎ "answer": "2, 1", ⏎ "explanation": "The @DataProvider provides two datasets ([1] and [-1]), so two test cases are executed. The first dataset ($x = 1) passes because 1 > 0, while the second dataset ($x = -1) fails because -1 > 0 is false." ⏎ } ⏎ ``` | верно | A non-static provider is just a deprecation in PHPUnit 10: both datasets run and the [-1] dataset fails the assert — 2 ran, 1 failure. |
T19-L9 0.42 c | HTTP and REST API | Which HTTP method does this command send?
```bash
curl -s -d 'a=1' http://demo.local/api
``` | «post» Пояснение: The -d flag in curl sends data in the body, which by default triggers the HTTP POST method when no other method is specified.
Raw{"answer": "POST", "explanation": "The -d flag in curl sends data in the body, which by default triggers the HTTP POST method when no other method is specified."} | верно | -d/-F switches curl to POST by default. |
T19-L10 0.32 c | HTTP and REST API | Which HTTP method does this command send?
```bash
curl -s -G -d 'a=1' http://demo.local/api
``` | «get» Пояснение: The -G flag tells curl to use GET and put the data in the query string instead of the request body.
Raw{"answer":"GET","explanation":"The -G flag tells curl to use GET and put the data in the query string instead of the request body."} | верно | -G turns -d data into the query string; the method stays GET. |
T20-L9 0.49 c | Security and OAuth | A client hits the token endpoint (RFC 6749) with a non-existent client_id. What value of the error field does the endpoint return? | «invalid_client» Пояснение: Per RFC 6749 Section 5.2, if the client cannot be identified or is not registered, the authorization server MUST return the error 'invalid_client'.
Raw{"answer": "invalid_client", "explanation": "Per RFC 6749 Section 5.2, if the client cannot be identified or is not registered, the authorization server MUST return the error 'invalid_client'."} | верно | Unknown client → invalid_client (RFC 6749 §5.2). |
T20-L10 0.4 c | Security and OAuth | OAuth 2.0: the client started the flow with response_type=token. In which part of the redirect_uri does the authorization server pass the access_token? | «fragment» Пояснение: In the implicit grant flow, the authorization server passes the access token in the fragment part of the response to the redirect URI.
Raw{"answer": "fragment", "explanation": "In the implicit grant flow, the authorization server passes the access token in the fragment part of the response to the redirect URI."} | верно | The implicit flow passes the token in the URL fragment (#) — it never reaches the server. |
T21-L9 0.54 c | Twig | What does this Twig template output?
```twig
{{ false|default(2) * 3 }}
``` | «6» Пояснение: false is not null, so default(2) does not replace it, and false is coerced to the number 0, making the result 0 * 3 = 6.
Raw{ ⏎ "answer": 6, ⏎ "explanation": "false is not null, so default(2) does not replace it, and false is coerced to the number 0, making the result 0 * 3 = 6." ⏎ } | верно | default replaces exactly false/null/''/[] — false becomes 2, 2*3 = 6; the naive 'default is for undefined only' yields 0. |
T21-L10 0.58 c | Twig | What exception class does render() of this template throw?
```twig
{{ 'a' ~ 1 + 2 }}
``` | «twig\twigruntimeexception» Пояснение: In Twig, the concatenation operator ~ has lower precedence than arithmetic operators, so the expression is parsed as 'a' ~ (1 + 2), resulting in '3' and no exception being thrown.
Raw{ ⏎ "answer": "Twig\\TwigRuntimeException", ⏎ "explanation": "In Twig, the concatenation operator ~ has lower precedence than arithmetic operators, so the expression is parsed as 'a' ~ (1 + 2), resulting in '3' and no exception being thrown." ⏎ } | неверно верный: «runtimeerror» | In Twig ~ binds tighter than +: ('a' ~ 1) + 2 → string + int → a render error (RuntimeError). |
T22-L9 0.46 c | Symfony: Security and forms | What does this code output?
```php
use Symfony\Component\Validator\Validation;
use Symfony\Component\Validator\Constraints as Assert;
$v = Validation::createValidator();
echo count($v->validate([''], [new Assert\NotBlank()]));
``` | «1» Пояснение: The empty string '' fails the NotBlank constraint, so validate() returns one Violation and count() outputs 1.
Raw{ ⏎ "answer": "1", ⏎ "explanation": "The empty string '' fails the NotBlank constraint, so validate() returns one Violation and count() outputs 1." ⏎ } | неверно верный: «0» | NotBlank treats null, '', [] as blank — the array [''] is not blank. |
T22-L10 0.43 c | Symfony: Security and forms | What does this code output?
```php
use Symfony\Component\Form\Forms;
use Symfony\Component\Form\Extension\Core\Type\TextType;
$factory = Forms::createFormFactoryBuilder()->getFormFactory();
$form = $factory->create(TextType::class);
try {
echo $form->isValid() ? 'valid' : 'invalid';
} catch (Throwable $e) {
echo get_class($e);
}
``` | «invalid» Пояснение: A newly created form instance is considered invalid by default because it has no bound data or errors to report.
Raw{ ⏎ "answer": "invalid", ⏎ "explanation": "A newly created form instance is considered invalid by default because it has no bound data or errors to report." ⏎ } | неверно верный: «symfony\component\form\exception\logicexception» | isValid() on a non-submitted form throws LogicException, it does not return false. |
T23-L9 0.57 c | Symfony: configuration and services | What does this code output?
```php
use Symfony\Component\DependencyInjection\ContainerBuilder;
$c = new ContainerBuilder();
$c->register('a', stdClass::class)->setPublic(true);
$c->compile();
echo spl_object_id($c->get('a')) === spl_object_id($c->get('a')) ? 'same' : 'diff';
``` | «same» Пояснение: After compiling the container, the service 'a' is resolved into a single object instance and stored in the container, so subsequent calls to get('a') return the exact same object with the same spl_object_id.
Raw{"answer": "same", "explanation": "After compiling the container, the service 'a' is resolved into a single object instance and stored in the container, so subsequent calls to get('a') return the exact same object with the same spl_object_id."} | верно | Container services are shared: two get() calls yield one instance. |
T23-L10 0.57 c | Symfony: configuration and services | What does this code output?
```php
use Symfony\Component\DependencyInjection\ContainerBuilder;
$c = new ContainerBuilder();
$c->setParameter('name', 'Bob');
$c->setParameter('greeting', 'hi %name%');
$c->setParameter('message', '%greeting%!');
$c->compile();
echo $c->getParameter('message');
``` | «hi bob» Пояснение: Symfony's ContainerBuilder resolves %name% to 'Bob' in %greeting%, then %greeting% to 'hi Bob' in %message%, after the % character is escaped as %%.
Raw```json ⏎ {"answer": "hi Bob", "explanation": "Symfony's ContainerBuilder resolves %name% to 'Bob' in %greeting%, then %greeting% to 'hi Bob' in %message%, after the % character is escaped as %%."} ⏎ ``` | неверно верный: «hi bob!» | compile() resolves %-references transitively: %greeting% → 'hi %name%' → 'hi Bob!', the answer assembles over two hops. |
T24-L9 0.5 c | Bootstrap | What is the max-width of .container in Bootstrap 5.3 at a 992px viewport? | «776px» Пояснение: In Bootstrap 5.3, the .container's max-width at the 992px breakpoint is defined as 776px.
Raw{ ⏎ "answer": "776px", ⏎ "explanation": "In Bootstrap 5.3, the .container's max-width at the 992px breakpoint is defined as 776px." ⏎ } | неверно верный: «960» | 5.x container widths: 540/720/960/1140/1320 (sm–xxl); 992 → 960px. |
T24-L10 0.52 c | Bootstrap | Which utility sets the text color in Bootstrap 5.3 for `<p class="text-danger text-primary">…</p>`? Answer with the winning class name. | «text-primary» Пояснение: In CSS and Bootstrap's class-based styling, when multiple text color classes are applied to the same element, the last one in the class list generally takes precedence, making text-primary the winning utility.
Raw{"answer": "text-primary", "explanation": "In CSS and Bootstrap's class-based styling, when multiple text color classes are applied to the same element, the last one in the class list generally takes precedence, making text-primary the winning utility."} | неверно верный: «text-danger» | Specificity ties — the later rule wins: text-danger is declared after text-primary. |
T25-L9 0.49 c | Clean architecture | Layers: Domain, Application, Infrastructure. Deptrac rules: Application → Domain; Infrastructure → Domain, Application; Domain → Domain only.
How many violations will deptrac report for this class?
```php
namespace App\Domain;
use App\Application\PlaceOrder;
use App\Infrastructure\Db;
class OrderService
{
public function __construct(
private PlaceOrder $handler,
private Db $db,
) {}
}
``` | «2» Пояснение: The class is in the Domain layer and uses Application (PlaceOrder) and Infrastructure (Db), violating the rules that Domain must only reference Domain and that Infrastructure cannot reference Domain.
Raw{"answer": 2, "explanation": "The class is in the Domain layer and uses Application (PlaceOrder) and Infrastructure (Db), violating the rules that Domain must only reference Domain and that Infrastructure cannot reference Domain."} | верно | Domain may depend only on Domain: PlaceOrder (Application) + Db (Infrastructure) = 2. |
T25-L10 0.45 c | Clean architecture | Layers: Domain, Application, Infrastructure. Deptrac rules: Application → Domain; Infrastructure → Domain, Application; Domain → Domain only.
How many violations will deptrac report for this class?
```php
namespace App\Domain;
use App\Application\PlaceOrder;
use App\Infrastructure\Db;
class BillingService
{
public function __construct(
private PlaceOrder $handler,
private Db $db,
private \App\Infrastructure\Logger $logger,
) {}
}
``` | «2» Пояснение: The Domain class depends on two Infrastructure classes (Db and Logger), which are violations of the rule that Domain must only depend on Domain.
Raw{ ⏎ "answer": "2", ⏎ "explanation": "The Domain class depends on two Infrastructure classes (Db and Logger), which are violations of the rule that Domain must only depend on Domain." ⏎ } | неверно верный: «3» | The inline FQCN \App\Infrastructure\Logger counts too: Application + Db + Logger = 3. |
T26-L10 0.6 c | DDD | What does this code output?
```php
final class Money
{
public function __construct(public readonly int $amount) {}
public function add(Money $o): Money
{
return new self($this->amount + $o->amount);
}
}
$a = new Money(10);
$c = $a->add(new Money(5));
echo $a->amount . ',' . $c->amount;
``` | «10,15» Пояснение: The Money object uses a readonly public property, and the add method creates a new Money instance without modifying the original, so $a->amount is 10 and $c->amount is 15.
Raw{"answer": "10,15", "explanation": "The Money object uses a readonly public property, and the add method creates a new Money instance without modifying the original, so $a->amount is 10 and $c->amount is 15."} | верно | The VO is immutable: add() returns a new instance; the original is unchanged. |
T26-L9 0.46 c | DDD | What does this code output?
```php
final class Order
{
private array $items = [];
public function add(string $sku): void
{
$this->items[$sku] = true;
}
public function count(): int
{
return count($this->items);
}
public function remove(string $sku): void
{
if (count($this->items) === 1) {
throw new DomainException('last item');
}
unset($this->items[$sku]);
}
}
$o = new Order;
$o->add('a');
try {
$o->remove('a');
} catch (DomainException) {
}
echo $o->count();
``` | «1» Пояснение: The remove() method checks that the order has exactly one item and throws an exception, so the item is never removed and count() returns 1.
Raw{"answer": 1, "explanation": "The remove() method checks that the order has exactly one item and throws an exception, so the item is never removed and count() returns 1."} | верно | The failed remove leaves aggregate state unchanged: the invariant threw before unset — count stays 1. |
VC-L9 0.47 c | PHP 8.4–8.5 | What does this code output on PHP 8.5?
```php
class C
{
public function hi(): string { return 'hi'; }
}
echo new C()->hi();
``` | «hi» Пояснение: The code creates a new C instance and calls its hi() method, which returns the string 'hi', so echo outputs hi.
Raw{ ⏎ "answer": "hi", ⏎ "explanation": "The code creates a new C instance and calls its hi() method, which returns the string 'hi', so echo outputs hi." ⏎ } | верно | Since 8.4, new in a method chain works without wrapping parentheses. |
VC-L10 0.41 c | PHP 8.4–8.5 | What does this code output on PHP 8.5?
```php
class Heavy
{
public int $v = 0;
}
$r = new ReflectionClass(Heavy::class);
$o = $r->newLazyGhost(function (Heavy $obj) {
$obj->v = 21;
});
echo $r->isUninitializedLazyObject($o) ? 'yes' : 'no';
$o->v;
echo $r->isUninitializedLazyObject($o) ? 'yes' : 'no';
``` | «yes no» Пояснение: Initially, the lazy object is uninitialized and then becomes initialized after property access.
Raw```json ⏎ { ⏎ "answer": "yes\nno", ⏎ "explanation": "Initially, the lazy object is uninitialized and then becomes initialized after property access." ⏎ } ⏎ ``` | неверно верный: «yesno» | newLazyGhost (8.4): the object stays lazy until first access — reading a property initializes it and clears the flag. |
T28-L9 0.55 c | Symfony: versions | The project was upgraded from Symfony 6.4 to 8.1. What does this code output on 8.1?
```php
echo class_exists(\Symfony\Component\Security\Guard\AbstractGuardAuthenticator::class)
? 'yes' : 'no';
``` | «no» Пояснение: Symfony 8.1 removes the legacy Security Guard classes that were deprecated in 5.3 and removed in 7.0, so AbstractGuardAuthenticator no longer exists.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "Symfony 8.1 removes the legacy Security Guard classes that were deprecated in 5.3 and removed in 7.0, so AbstractGuardAuthenticator no longer exists." ⏎ } | верно | Guard authentication was removed in Symfony 7.0 — the class is gone in 8.1. |
T28-L10 0.48 c | Symfony: versions | The project was upgraded from Symfony 6.4 to 8.1. What does this code output on 8.1?
```php
echo class_exists(\Symfony\Component\Routing\Loader\AnnotationClassLoader::class)
? 'yes' : 'no';
echo class_exists(\Symfony\Component\Routing\Loader\AttributeClassLoader::class)
? 'yes' : 'no';
``` | «no» Пояснение: The AnnotationClassLoader class was removed in Symfony 7, so both class_exists checks return false in 8.1, outputting "no" followed by a newline from the first echo.
Raw{"answer": "no\n", "explanation": "The AnnotationClassLoader class was removed in Symfony 7, so both class_exists checks return false in 8.1, outputting \"no\" followed by a newline from the first echo."} | неверно верный: «noyes» | Annotation loaders were removed in 7.0; only attribute loaders remain (Annotation→Attribute). |