Пример запроса (первая клетка). System одинаковый во всех запросах прогона, user — свой вопрос для каждой клетки:
| Клетка | Тема | Утверждение | Ответ |
Результат | Обоснование |
T01-L1 4.0 c | Syntax and operators | Double-quoted and single-quoted strings are processed identically; the difference is only in speed. | «no» Пояснение: Double-quoted strings support variable interpolation and more escape sequences, while single-quoted strings do not — the difference is not just speed but functionality.
Raw```json ⏎ {"answer": "no", "explanation": "Double-quoted strings support variable interpolation and more escape sequences, while single-quoted strings do not — the difference is not just speed but functionality."} ⏎ ``` | верно | В двойных кавычках работают интерполяция переменных и escape-последовательности, в одинарных — нет. |
T01-L2 1.19 c | Syntax and operators | The ?? operator follows isset semantics and raises no warnings for undefined variables. | «yes» Пояснение: The ?? operator is equivalent to isset($var) ? $var : default, so it suppresses notices/warnings for undefined variables.
Raw{"answer": "yes", "explanation": "The ?? operator is equivalent to isset($var) ? $var : default, so it suppresses notices/warnings for undefined variables."} | верно | ?? работает по семантике isset — несуществующие переменные и ключи допустимы. |
T01-L3 0.64 c | Syntax and operators | What will this print: echo 'a', 'b'; | «ab» Пояснение: The echo statement accepts multiple arguments separated by commas and outputs them sequentially without any separator.
Raw{"answer": "ab", "explanation": "The echo statement accepts multiple arguments separated by commas and outputs them sequentially without any separator."} | верно | echo принимает список аргументов: ab. |
T01-L4 1.13 c | Syntax and operators | print returns the value 1 and can be used inside an expression. | «yes» Пояснение: In PHP, print always returns the integer 1, so it can be used inside expressions, unlike echo which returns no value.
Raw{"answer": "yes", "explanation": "In PHP, print always returns the integer 1, so it can be used inside expressions, unlike echo which returns no value."} | верно | print — выражение со значением 1, в отличие от echo, который значения не возвращает. |
T01-L5 1.13 c | Syntax and operators | The ?: (elvis) operator returns its left operand when it is falsy. | «no» Пояснение: The elvis operator ($a ?: $b) returns the left operand when it is truthy, and the right operand when it is falsy.
Raw{"answer": "no", "explanation": "The elvis operator ($a ?: $b) returns the left operand when it is truthy, and the right operand when it is falsy."} | верно | Наоборот: $a ?: $b возвращает $a, если он истинный, иначе $b. |
T01-L6 2.14 c | Syntax and operators | In PHP 8, the concatenation operator (.) has lower precedence than addition and subtraction. | «no» Пояснение: In PHP, the concatenation operator (.) has the same precedence as addition (+) and subtraction (-), not lower.
Raw{"answer": "no", "explanation": "In PHP, the concatenation operator (.) has the same precedence as addition (+) and subtraction (-), not lower."} | неверно верный: «yes» | С PHP 8 (RFC concat precedence) '.' имеет приоритет ниже арифметики: 'сумма: ' . 2 + 3 → 'сумма: 5' (в PHP 7 было иначе). |
T01-L7 0.92 c | Syntax and operators | The expression 2 ** 3 ** 2 in PHP evaluates as (2 ** 3) ** 2, that is, 64. | «no» Пояснение: The ** operator in PHP is right-associative, so 2 ** 3 ** 2 evaluates as 2 ** (3 ** 2) = 2 ** 9 = 512, not 64.
Raw{"answer":"no","explanation":"The ** operator in PHP is right-associative, so 2 ** 3 ** 2 evaluates as 2 ** (3 ** 2) = 2 ** 9 = 512, not 64."} | верно | ** право-ассоциативен: 2 ** (3 ** 2) = 2 ** 9 = 512. |
T01-L8 1.25 c | Syntax and operators | What string will this print: echo 'sum: ' . 2 + 3; (PHP 8)? | «sum: 5» Пояснение: The + operator has higher precedence than the . concatenation operator, so it is parsed as 'sum: ' . (2 + 3) = 'sum: 5'.
Raw{"answer": "sum: 5", "explanation": "The + operator has higher precedence than the . concatenation operator, so it is parsed as 'sum: ' . (2 + 3) = 'sum: 5'."} | верно | Парная к verify-клетке про приоритет: 'сумма: 5'. |
T02-L1 1.15 c | Types and comparisons | With strict comparison (===), arrays are considered equal regardless of element order. | «no» Пояснение: With strict comparison (===), arrays are only considered equal if they have the same key/value pairs in the same order and of the same type; order matters.
Raw{"answer": "no", "explanation": "With strict comparison (===), arrays are only considered equal if they have the same key/value pairs in the same order and of the same type; order matters."} | верно | === для массивов требует совпадения и значений, и их порядка. |
T02-L2 1.33 c | Types and comparisons | The comparison 0 == false returns false because it is a strict comparison. | «no» Пояснение: 0 == false uses a loose comparison (==), and it actually returns true because false is cast to 0.
Raw{"answer": "no", "explanation": "0 == false uses a loose comparison (==), and it actually returns true because false is cast to 0."} | верно | Наоборот: == — нестрогое сравнение и возвращает true; строгое — это === (0 === false → false). |
T02-L3 1.36 c | Types and comparisons | In PHP 8, the expression "abc" == 0 returns true. | «no» Пояснение: In PHP 8, when a non-numeric string is loosely compared to an integer, the integer is cast to a string, so 'abc' == 0 becomes 'abc' == '0', which is false.
Raw{"answer": "no", "explanation": "In PHP 8, when a non-numeric string is loosely compared to an integer, the integer is cast to a string, so 'abc' == 0 becomes 'abc' == '0', which is false."} | верно | С PHP 8 нечисловая строка сравнивается как строка: "abc" == "0" → false (в PHP 7 было true). |
T02-L4 0.78 c | Types and comparisons | Under loose comparison, null equals 0, the empty string, and false at the same time. | «yes» Пояснение: In PHP, null == 0, null == "", and null == false all evaluate to true under loose comparison.
Raw{"answer": "yes", "explanation": "In PHP, null == 0, null == \"\", and null == false all evaluate to true under loose comparison."} | верно | null == 0, null == "" и null == false — все true. |
T02-L5 0.93 c | Types and comparisons | What does the expression (int) '42abc' return? | «42» Пояснение: PHP's (int) cast parses the leading numeric portion of a string, so '42abc' becomes 42.
Raw{"answer": 42, "explanation": "PHP's (int) cast parses the leading numeric portion of a string, so '42abc' becomes 42."} | верно | Ведущая числовая часть: 42, без ошибок и warning. |
T02-L6 0.68 c | Types and comparisons | What does the expression '5' + 5 return? | «10» Пояснение: PHP coerces the numeric string '5' to integer 5, then performs arithmetic addition: 5 + 5 = 10.
Raw{"answer": 10, "explanation": "PHP coerces the numeric string '5' to integer 5, then performs arithmetic addition: 5 + 5 = 10."} | верно | Числовая строка приводится: int 10. |
T02-L7 0.85 c | Types and comparisons | When cast to string, false becomes "0". | «no» Пояснение: In PHP, casting false to a string produces an empty string (""), not "0".
Raw{"answer": "no", "explanation": "In PHP, casting false to a string produces an empty string (\"\"), not \"0\"."} | верно | false → "", true → "1". |
T02-L8 1.14 c | Types and comparisons | The comparison 0.1 + 0.2 === 0.3 returns false. | «yes» Пояснение: Due to floating-point precision, 0.1 + 0.2 equals 0.30000000000000004, which is not strictly equal (===) to 0.3.
Raw{"answer": "yes", "explanation": "Due to floating-point precision, 0.1 + 0.2 equals 0.30000000000000004, which is not strictly equal (===) to 0.3."} | верно | Двоичная погрешность float: 0.1 + 0.2 = 0.30000000000000004. |
T03-L1 1.48 c | Strings | strrev() correctly reverses a UTF-8 string. | «no» Пояснение: strrev() operates on a byte-by-byte basis, which will corrupt multi-byte UTF-8 characters rather than reversing them as whole code points.
Raw{"answer":"no","explanation":"strrev() operates on a byte-by-byte basis, which will corrupt multi-byte UTF-8 characters rather than reversing them as whole code points."} | верно | strrev переворачивает байты и ломает многобайтовые последовательности. |
T03-L2 0.67 c | Strings | str_contains('Hello world', 'world') returns true. | «yes» Пояснение: str_contains() returns true when the haystack contains the needle, and 'Hello world' does contain 'world'.
Raw{"answer": "yes", "explanation": "str_contains() returns true when the haystack contains the needle, and 'Hello world' does contain 'world'."} | верно | str_contains с PHP 8.0 проверяет вхождение подстроки. |
T03-L3 0.73 c | Strings | str_pad() can pad a string on the right side only. | «no» Пояснение: str_pad() can pad on the right (default), left, or both sides via the $side parameter (STR_PAD_RIGHT, STR_PAD_LEFT, STR_PAD_BOTH).
Raw{"answer": "no", "explanation": "str_pad() can pad on the right (default), left, or both sides via the $side parameter (STR_PAD_RIGHT, STR_PAD_LEFT, STR_PAD_BOTH)."} | верно | STR_PAD_LEFT / STR_PAD_BOTH меняют сторону дополнения. |
T03-L4 0.95 c | Strings | By default trim() strips only spaces, leaving tabs and newlines intact. | «no» Пояснение: By default trim() strips spaces, tabs, newlines, carriage returns, NUL bytes, and vertical tabs (" \t\n\r\0\x0B"), not just spaces.
Raw{"answer":"no","explanation":"By default trim() strips spaces, tabs, newlines, carriage returns, NUL bytes, and vertical tabs (\" \\t\\n\\r\\0\\x0B\"), not just spaces."} | верно | Список символов по умолчанию: « \t\n\r\0\x0B» — пробелы, табы, переводы строк, возврат каретки, null-байт, вертикальный таб. Проверено php -r. |
T03-L5 1.0 c | Strings | How many BYTES does strlen('héllo') return for a UTF-8 string? | «6» Пояснение: In UTF-8, 'é' is 2 bytes and the other 4 characters are 1 byte each, totaling 6 bytes.
Raw{"answer": 6, "explanation": "In UTF-8, 'é' is 2 bytes and the other 4 characters are 1 byte each, totaling 6 bytes."} | верно | 6 букв по 2 байта: 12. |
T03-L6 0.71 c | Strings | What does substr('abcdef', -3) return? | «def» Пояснение: substr with a negative start position counts from the end of the string, so -3 gives the last 3 characters 'def'.
Raw{"answer": "def", "explanation": "substr with a negative start position counts from the end of the string, so -3 gives the last 3 characters 'def'."} | верно | Отрицательное смещение — с конца: def. |
T03-L7 0.87 c | Strings | ucfirst() modifies the string passed to it in place. | «no» Пояснение: ucfirst() returns a new string with the first character uppercased; it does not modify the original string in place.
Raw{"answer": "no", "explanation": "ucfirst() returns a new string with the first character uppercased; it does not modify the original string in place."} | верно | Строки неизменяемы; ucfirst возвращает новую строку. |
T03-L8 1.09 c | Strings | Variable interpolation works in heredoc but not in nowdoc. | «yes» Пояснение: Heredoc allows variable interpolation just like double-quoted strings, while nowdoc treats content as a plain string (like single-quoted strings) where variables are not interpolated.
Raw{"answer": "yes", "explanation": "Heredoc allows variable interpolation just like double-quoted strings, while nowdoc treats content as a plain string (like single-quoted strings) where variables are not interpolated."} | верно | Nowdoc — «одинарные кавычки» в тройном синтаксисе: текст как есть. |
T04-L1 0.76 c | Arrays | The sort() function preserves the key-to-value association of the array. | «no» Пояснение: sort() reindexes the array with integer keys; use asort() to preserve key-value associations.
Raw{"answer": "no", "explanation": "sort() reindexes the array with integer keys; use asort() to preserve key-value associations."} | верно | sort перенумеровывает ключи; связь сохраняет asort. |
T04-L2 1.03 c | Arrays | The string key '5' in an array is stored as the integer 5. | «yes» Пояснение: In PHP, string keys that represent valid integers (like '5') are automatically cast to integer keys, so the key is stored as the integer 5.
Raw{"answer": "yes", "explanation": "In PHP, string keys that represent valid integers (like '5') are automatically cast to integer keys, so the key is stored as the integer 5."} | верно | Каноничные десятичные строковые ключи приводятся к int. |
T04-L3 0.76 c | Arrays | The in_array() function uses strict comparison (===) by default. | «no» Пояснение: The in_array() function uses loose comparison (==) by default; the $strict parameter defaults to false.
Raw{"answer": "no", "explanation": "The in_array() function uses loose comparison (==) by default; the $strict parameter defaults to false."} | верно | По умолчанию сравнение нестрогое; строгое — третий аргумент true. |
T04-L4 1.05 c | Arrays | Without a callback, array_filter() removes all "empty" (falsy) elements from the array. | «yes» Пояснение: Without a callback, array_filter() removes all elements that evaluate to falsy (false, 0, '0', '', null, []).
Raw{"answer": "yes", "explanation": "Without a callback, array_filter() removes all elements that evaluate to falsy (false, 0, '0', '', null, [])."} | верно | Убирает 0, "", null, false и пустые массивы. |
T04-L5 1.07 c | Arrays | By default, array_slice() preserves the original numeric keys of the array. | «no» Пояснение: The $preserve_keys parameter defaults to false, so array_slice() reindexes the array with sequential numeric keys starting from 0 by default.
Raw{"answer": "no", "explanation": "The $preserve_keys parameter defaults to false, so array_slice() reindexes the array with sequential numeric keys starting from 0 by default."} | верно | По умолчанию ключи перенумеровываются; сохранение — preserve_keys = true. |
T04-L6 1.0 c | Arrays | What does array_slice([10, 20, 30, 40], 1, 2) return? | «{"answer": [20, 30], "explanation": "array_slice with offset 1 and length 2 returns the 2 elements starting at index 1, which are 20 and 30."}» Пояснение: {"answer": [20, 30], "explanation": "array_slice with offset 1 and length 2 returns the 2 elements starting at index 1, which are 20 and 30."}
Raw{"answer": [20, 30], "explanation": "array_slice with offset 1 and length 2 returns the 2 elements starting at index 1, which are 20 and 30."} | верно парсинг: текст (фолбэк) | [20,30]; ключи перенумеровываются. |
T04-L7 1.4 c | Arrays | How many elements will count(['a' => 1] + ['a' => 9, 'b' => 2]) return? | «2» Пояснение: Array union with + keeps left-hand keys and appends right-hand keys not present in the left, resulting in ['a'=>1, 'b'=>2'] which has 2 elements.
Raw{"answer": 2, "explanation": "Array union with + keeps left-hand keys and appends right-hand keys not present in the left, resulting in ['a'=>1, 'b'=>2'] which has 2 elements."} | верно | Оператор + : по ключу 'a' побеждает левый; итого 2. |
T04-L8 2.01 c | Arrays | Since PHP 8.1, the spread operator [...$a, ...$b] supports arrays with string keys. | «yes» Пояснение: PHP 8.1 introduced the spread operator in array literals, which supports both integer and string keys, with later values overwriting earlier ones on key collision.
Raw{"answer": "yes", "explanation": "PHP 8.1 introduced the spread operator in array literals, which supports both integer and string keys, with later values overwriting earlier ones on key collision."} | верно | В 8.0 — только числовые ключи; 8.1 снял ограничение. |
T05-L1 3.47 c | Functions and closures | Named arguments cannot be combined with argument unpacking ...$args in a single call. | «no» Пояснение: In PHP 8.0+, named arguments can be combined with the spread operator in a single call, e.g. foo(a: 1, ...$args, c: 3).
Raw```json ⏎ {"answer": "no", "explanation": "In PHP 8.0+, named arguments can be combined with the spread operator in a single call, e.g. foo(a: 1, ...$args, c: 3)."} ⏎ ``` | верно | Можно: f(...$args, имя: значение). Нельзя только позиционный аргумент после распаковки. |
T05-L2 0.91 c | Functions and closures | An anonymous function without use sees variables from the outer scope. | «no» Пояснение: In PHP, anonymous functions (closures) do not have access to outer scope variables unless they are explicitly imported using the `use` keyword.
Raw{"answer": "no", "explanation": "In PHP, anonymous functions (closures) do not have access to outer scope variables unless they are explicitly imported using the `use` keyword."} | верно | Без use внешние переменные недоступны; авто-захват только у fn. |
T05-L3 0.83 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() returns the number of arguments actually passed to the function, which is 3 in this case, even though only one parameter is declared.
Raw{"answer": 3, "explanation": "func_num_args() returns the number of arguments actually passed to the function, which is 3 in this case, even though only one parameter is declared."} | верно | Считает переданные аргументы: 3. |
T05-L4 1.1 c | Functions and closures | The body of an arrow function fn may consist of several expressions in curly braces. | «no» Пояснение: An arrow function (fn) body must be a single expression; for multiple statements you need a regular closure with curly braces.
Raw{"answer": "no", "explanation": "An arrow function (fn) body must be a single expression; for multiple statements you need a regular closure with curly braces."} | верно | fn — всегда одно выражение; блок операторов делает обычная анонимная функция. |
T05-L5 1.71 c | Functions and closures | An arrow function fn captures outer variables by reference (lazily, at use time). | «no» Пояснение: Arrow functions (fn) capture outer variables by value (eagerly at creation time), not by reference.
Raw{"answer":"no","explanation":"Arrow functions (fn) capture outer variables by value (eagerly at creation time), not by reference."} | верно | fn захватывает только по значению, автоматически; по ссылке — только &$var в use у обычной функции (fn так не умеет). |
T05-L6 0.97 c | Functions and closures | A closure declared as static function () {} does not capture $this. | «yes» Пояснение: In PHP, a static closure explicitly does not bind $this to the current object scope.
Raw{"answer": "yes", "explanation": "In PHP, a static closure explicitly does not bind $this to the current object scope."} | верно | static-замыкание отвязано от объекта: $this внутри недоступен. |
T05-L7 1.04 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 (no &), so it retains the original value of 5 even after $x is reassigned to 7.
Raw{"answer": 5, "explanation": "The closure captures $x by value (no &), so it retains the original value of 5 even after $x is reassigned to 7."} | верно | use захватывает по значению в момент создания: 5. |
T05-L8 1.39 c | Functions and closures | In weak typing mode (without strict_types), passing the string "5" to an int parameter is allowed. | «yes» Пояснение: In PHP's weak typing mode (default), the string '5' is automatically coerced to the integer 5 when passed to an int-typed parameter.
Raw{"answer": "yes", "explanation": "In PHP's weak typing mode (default), the string '5' is automatically coerced to the integer 5 when passed to an int-typed parameter."} | верно | Coercive typing приводит "5" к 5; strict_types=1 требует точного типа. |
T06-L1 0.86 c | OOP: classes and inheritance | PHP supports constructor property promotion: public function __construct(private int $x) {}. | «yes» Пояснение: Constructor property promotion was introduced in PHP 8.0, allowing visibility modifiers on constructor parameters to automatically create class properties.
Raw{"answer": "yes", "explanation": "Constructor property promotion was introduced in PHP 8.0, allowing visibility modifiers on constructor parameters to automatically create class properties."} | верно | С PHP 8.0 параметр с модификатором создаёт свойство и присваивание. |
T06-L2 0.48 c | OOP: classes and inheritance | Which keyword prevents a method from being overridden in subclasses? | «final» Пояснение: The 'final' keyword in PHP prevents a method from being overridden in subclasses.
Raw{"answer": "final", "explanation": "The 'final' keyword in PHP prevents a method from being overridden in subclasses."} | верно | final. |
T06-L3 0.75 c | OOP: classes and inheritance | A method declared final cannot be overridden in a subclass. | «yes» Пояснение: In PHP, a method declared as final cannot be overridden by a subclass; attempting to do so results in a fatal error.
Raw{"answer": "yes", "explanation": "In PHP, a method declared as final cannot be overridden by a subclass; attempting to do so results in a fatal error."} | верно | final запрещает переопределение метода и наследование класса. |
T06-L4 0.68 c | OOP: classes and inheritance | Parent properties with private visibility are accessible in a subclass. | «no» Пояснение: In PHP, private properties are only accessible within the class that declares them; they are not accessible in a subclass.
Raw{"answer": "no", "explanation": "In PHP, private properties are only accessible within the class that declares them; they are not accessible in a subclass."} | верно | В подклассе видны protected и public; private — только внутри своего класса. |
T06-L5 3.65 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). | «class@anonymous» Пояснение: In PHP, anonymous classes are internally named 'class@anonymous' followed by a NUL byte and the file path/line number; get_class() returns the full name but the part before the NUL byte is 'class@anonymous'.
Raw```json ⏎ {"answer": "class@anonymous", "explanation": "In PHP, anonymous classes are internally named 'class@anonymous' followed by a NUL byte and the file path/line number; get_class() returns the full name but the part before the NUL byte is 'class@anonymous'."} ⏎ ``` | верно | get_class анонимного класса печатает class@anonymous\0<файл>:<строка>$n; короткая форма — часть до NUL-байта. Проверено php -r (hex). |
T06-L6 1.11 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» Пояснение: Private methods are not inherited in PHP, so a child class can freely declare a method with the same name and any visibility without conflict.
Raw{"answer":"yes","explanation":"Private methods are not inherited in PHP, so a child class can freely declare a method with the same name and any visibility without conflict."} | верно | private-члены не наследуются — правила совместимости подписей не действуют. |
T06-L7 0.84 c | OOP: classes and inheritance | The magic method __get() is called only for non-existent properties. | «no» Пояснение: __get() is called for both inaccessible (protected/private) and non-existent properties, not only non-existent ones.
Raw{"answer":"no","explanation":"__get() is called for both inaccessible (protected/private) and non-existent properties, not only non-existent ones."} | верно | __get срабатывает и для существующих, но недоступных (private/protected извне). |
T06-L8 1.17 c | OOP: classes and inheritance | What does reassigning a readonly property throw — Exception or Error? | «error» Пояснение: Reassigning a readonly property in PHP throws an Error (not an Exception).
Raw{"answer": "Error", "explanation": "Reassigning a readonly property in PHP throws an Error (not an Exception)."} | верно | Error (readonly с 8.1); оговорка: в __clone() переинициализация допустима (8.3+). |
T07-L1 0.73 c | Interfaces, traits, enum | An interface can declare constants. | «yes» Пояснение: PHP interfaces can declare constants, which are always public and accessible via the interface name.
Raw{"answer": "yes", "explanation": "PHP interfaces can declare constants, which are always public and accessible via the interface name."} | верно | Константы интерфейса наследуются реализациями. |
T07-L2 0.42 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 specific class or implements a specific interface in PHP.
Raw{"answer": "instanceof", "explanation": "The instanceof operator checks whether an object is an instance of a specific class or implements a specific interface in PHP."} | верно | instanceof. |
T07-L3 1.79 c | Interfaces, traits, enum | An interface can declare static methods. | «yes» Пояснение: PHP interfaces can declare static method signatures that implementing classes must fulfill.
Raw{"answer": "yes", "explanation": "PHP interfaces can declare static method signatures that implementing classes must fulfill."} | верно | Реализация обязана дать статический метод с той же сигнатурой. |
T07-L4 1.07 c | Interfaces, traits, enum | The instanceof operator only checks class inheritance: it ignores interfaces. | «no» Пояснение: The instanceof operator in PHP checks both class inheritance and interface implementation; an object will return true for instanceof against any interface its class implements.
Raw{"answer": "no", "explanation": "The instanceof operator in PHP checks both class inheritance and interface implementation; an object will return true for instanceof against any interface its class implements."} | верно | instanceof возвращает true и для интерфейсов объекта. |
T07-L5 1.97 c | Interfaces, traits, enum | An interface method may have a default implementation, like a trait method. | «no» Пояснение: In PHP, interface methods are always abstract and cannot have a default implementation; only trait methods can be concrete with a body.
Raw{"answer": "no", "explanation": "In PHP, interface methods are always abstract and cannot have a default implementation; only trait methods can be concrete with a body."} | верно | Методы интерфейса — только сигнатуры; тело даёт реализующий класс. |
T07-L6 1.82 c | Interfaces, traits, enum | An abstract method in an abstract class may have protected visibility. | «yes» Пояснение: In PHP, abstract methods can be declared with public or protected visibility (abstract private is also syntactically allowed but discouraged).
Raw{"answer": "yes", "explanation": "In PHP, abstract methods can be declared with public or protected visibility (abstract private is also syntactically allowed but discouraged)."} | верно | В абстрактном классе — любая видимость; в интерфейсе — только public. |
T07-L7 0.83 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 containing all defined enum cases, which are A, B, and C — three elements.
Raw{"answer": 3, "explanation": "Foo::cases() returns an array containing all defined enum cases, which are A, B, and C — three elements."} | верно | Статический метод cases(): 3. |
T07-L8 1.5 c | Interfaces, traits, enum | A trait can declare constants. | «yes» Пояснение: Since PHP 8.2, traits can declare constants (as well as properties).
Raw{"answer": "yes", "explanation": "Since PHP 8.2, traits can declare constants (as well as properties)."} | верно | С PHP 8.2 трейты могут объявлять константы (RFC constants_in_traits); до 8.2 — нет. |
T08-L1 0.84 c | Exceptions and errors | The Throwable interface is a common ancestor of both Exception and Error. | «yes» Пояснение: Both Exception and Error implement the Throwable interface, making it their common ancestor.
Raw{"answer": "yes", "explanation": "Both Exception and Error implement the Throwable interface, making it their common ancestor."} | верно | Иерархия с PHP 7: Throwable → Exception и Throwable → Error. |
T08-L2 1.22 c | Exceptions and errors | A catch (Exception $e) block will also catch TypeError, because TypeError ultimately inherits from Exception. | «no» Пояснение: TypeError extends Error, not Exception; both implement Throwable but are separate branches, so catch(Exception) does not catch TypeError.
Raw{"answer": "no", "explanation": "TypeError extends Error, not Exception; both implement Throwable but are separate branches, so catch(Exception) does not catch TypeError."} | верно | TypeError наследуется от Error; catch (Exception) его не ловит. |
T08-L3 0.88 c | Exceptions and errors | The @ operator suppresses exceptions too. | «no» Пояснение: The @ operator suppresses errors (warnings, notices, etc.) but does not suppress exceptions; exceptions will still propagate normally.
Raw{"answer": "no", "explanation": "The @ operator suppresses errors (warnings, notices, etc.) but does not suppress exceptions; exceptions will still propagate normally."} | верно | @ глушит диагностику (warnings/notices), исключения не перехватывает. |
T08-L4 0.94 c | Exceptions and errors | What error class does intdiv(5, 0) throw? | «divisionbyzeroerror» Пояснение: intdiv(5, 0) throws a DivisionByZeroError, which extends ArithmeticError, when the divisor is zero.
Raw{"answer": "DivisionByZeroError", "explanation": "intdiv(5, 0) throws a DivisionByZeroError, which extends ArithmeticError, when the divisor is zero."} | верно | DivisionByZeroError (иерархия Error, не Exception); php-грейдер объективен. |
T08-L5 1.15 c | Exceptions and errors | The finally block runs only if the exception was caught by a catch block. | «no» Пояснение: The finally block runs regardless of whether an exception was thrown or caught — it always executes after the try block (and any matching catch block) completes.
Raw{"answer": "no", "explanation": "The finally block runs regardless of whether an exception was thrown or caught — it always executes after the try block (and any matching catch block) completes."} | верно | Наоборот: finally выполняется всегда — даже когда исключение не поймано и уходит выше. Проверено php -r. |
T08-L6 1.4 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 in a finally block actually replaces (overrides) any exception that was thrown in the try or catch block, so it does have an effect on the outcome.
Raw{"answer": "no", "explanation": "An exception thrown in a finally block actually replaces (overrides) any exception that was thrown in the try or catch block, so it does have an effect on the outcome."} | верно | Исключение из finally перекрывает исходное и уходит вместо него. |
T08-L7 1.02 c | Exceptions and errors | What does the expression (bool) new Exception('x') return? | «yes» Пояснение: In PHP, casting any object to bool always results in true, since objects are never falsy.
Raw{"answer": "yes", "explanation": "In PHP, casting any object to bool always results in true, since objects are never falsy."} | верно | Любой объект при приведении к bool — true. Формы ответа: true или да. |
T08-L8 1.08 c | Exceptions and errors | Functions registered via register_shutdown_function() run when exit is called. | «yes» Пояснение: Functions registered with register_shutdown_function() are executed when the script terminates, including when exit or die is called.
Raw{"answer": "yes", "explanation": "Functions registered with register_shutdown_function() are executed when the script terminates, including when exit or die is called."} | верно | exit завершает скрипт, но shutdown-функции отрабатывают. |
T09-L1 1.34 c | Namespaces and autoloading | The use App\Service\Mailer; statement itself loads the class file. | «no» Пояснение: The 'use' statement only creates an alias for the class; the class file is actually loaded (via autoloading) only when the class is first used, such as during instantiation or a static call.
Raw{"answer":"no","explanation":"The 'use' statement only creates an alias for the class; the class file is actually loaded (via autoloading) only when the class is first used, such as during instantiation or a static call."} | верно | use — псевдоним на этапе компиляции; файл грузит автозагрузчик при первом обращении. |
T09-L2 0.93 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 function from a namespace.
Raw{"answer": "function", "explanation": "In PHP, you use 'use function' to import a function from a namespace."} | верно | use function ...; (и use const для констант). |
T09-L3 1.38 c | Namespaces and autoloading | Into which file (path from src/) does the PSR-4 mapping "App\ → src/" place the class App\Controller\Api\UserController? | «controller/api/usercontroller.php» Пояснение: PSR-4 strips the mapped prefix 'App\', converts remaining namespace separators to directory slashes, and appends .php to the class name.
Raw{"answer": "Controller/Api/UserController.php", "explanation": "PSR-4 strips the mapped prefix 'App\\', converts remaining namespace separators to directory slashes, and appends .php to the class name."} | верно | Остаток имени после префикса, \ → /. |
T09-L4 0.82 c | Namespaces and autoloading | Including vendor/autoload.php registers autoloaders via spl_autoload_register(). | «yes» Пояснение: Composer's vendor/autoload.php instantiates a ClassLoader which calls spl_autoload_register() to register itself with the SPL autoloader stack.
Raw{"answer": "yes", "explanation": "Composer's vendor/autoload.php instantiates a ClassLoader which calls spl_autoload_register() to register itself with the SPL autoloader stack."} | верно | Composer ставит автозагрузчик именно на spl_autoload_register. |
T09-L5 0.74 c | Namespaces and autoloading | The magic constant __NAMESPACE__ contains the name of the current namespace. | «yes» Пояснение: __NAMESPACE__ is a magic constant that returns the name of the current namespace (or an empty string if in the global namespace).
Raw{"answer": "yes", "explanation": "__NAMESPACE__ is a magic constant that returns the name of the current namespace (or an empty string if in the global namespace)."} | верно | В корневом пространстве — пустая строка. |
T09-L6 2.0 c | Namespaces and autoloading | An unqualified class name (without a leading \) in new is resolved from the global root. | «no» Пояснение: An unqualified class name in 'new' is first resolved relative to the current namespace, not the global root; it only falls back to global if not found in the current namespace.
Raw{"answer": "no", "explanation": "An unqualified class name in 'new' is first resolved relative to the current namespace, not the global root; it only falls back to global if not found in the current namespace."} | верно | Резолвится относительно текущего namespace (с учётом импортов). |
T09-L7 1.02 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» Пояснение: PSR-4 maps the App\ prefix to src/, and the remaining sub-namespace Model\User translates to the relative path Model/User.php, giving src/Model/User.php.
Raw{"answer": "yes", "explanation": "PSR-4 maps the App\\ prefix to src/, and the remaining sub-namespace Model\\User translates to the relative path Model/User.php, giving src/Model/User.php."} | верно | Остаток имени после префикса переносится в путь как есть. |
T09-L8 1.31 c | Namespaces and autoloading | A use statement may be written inside a function body — the import then applies to that function only. | «yes» Пояснение: In PHP, a use statement can be placed inside a function body, and the alias it creates is only valid within that function's scope.
Raw{"answer": "yes", "explanation": "In PHP, a use statement can be placed inside a function body, and the alias it creates is only valid within that function's scope."} | неверно верный: «no» | use внутри тела функции — parse error; импорты файловые и компиляционные. |
T10-L1 1.33 c | References and scope | Arrays are copied on assignment rather than passed by reference. | «yes» Пояснение: In PHP, arrays are value types; assigning an array to a new variable creates a copy, so modifications to one do not affect the other.
Raw{"answer": "yes", "explanation": "In PHP, arrays are value types; assigning an array to a new variable creates a copy, so modifications to one do not affect the other."} | верно | Присваивание массива — копия (в движке — copy-on-write). |
T10-L2 1.21 c | References and scope | What will this print: $a = [1, 2]; $b = $a; $b[] = 3; echo count($a); | «2» Пояснение: Arrays in PHP are copied by value on assignment, so modifying $b does not affect $a, which still contains 2 elements.
Raw{"answer": 2, "explanation": "Arrays in PHP are copied by value on assignment, so modifying $b does not affect $a, which still contains 2 elements."} | верно | Присваивание — копия: в $a по-прежнему 2 элемента. |
T10-L3 1.0 c | References and scope | Inside a function, user-defined global variables are inaccessible without global, $GLOBALS, or passing them as parameters. | «yes» Пояснение: In PHP, function scope is isolated from global scope, so global variables must be explicitly brought into scope via global, $GLOBALS, or passed as parameters.
Raw{"answer": "yes", "explanation": "In PHP, function scope is isolated from global scope, so global variables must be explicitly brought into scope via global, $GLOBALS, or passed as parameters."} | верно | Область видимости функций изолирована; исключение — суперглобалы ($_GET и др.). |
T10-L4 1.49 c | References and scope | unset($GLOBALS['x']) inside a function removes the global variable only for that function. | «no» Пояснение: $GLOBALS['x'] directly references the global scope, so unset($GLOBALS['x']) removes the variable from the global scope entirely, not just within that function.
Raw{"answer": "no", "explanation": "$GLOBALS['x'] directly references the global scope, so unset($GLOBALS['x']) removes the variable from the global scope entirely, not just within that function."} | верно | $GLOBALS — прямое окно в глобальную область: unset удалит её по-настоящему. |
T10-L5 1.01 c | References and scope | What will this print: function inc(&$x) { $x++; } $n = 5; inc($n); echo $n; | «6» Пояснение: The function modifies $n by reference, incrementing it from 5 to 6.
Raw{"answer": 6, "explanation": "The function modifies $n by reference, incrementing it from 5 to 6."} | верно | Ссылка меняет оригинал: 6. |
T10-L6 2.42 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 by value iterates over a snapshot (copy-on-write) of the array, so modifications made to the array inside the loop body are not reflected in the ongoing iteration.
Raw{"answer": "no", "explanation": "In PHP, foreach by value iterates over a snapshot (copy-on-write) of the array, so modifications made to the array inside the loop body are not reflected in the ongoing iteration."} | верно | По значению foreach итерирует копию-снимок. |
T10-L7 0.74 c | References and scope | A static property belongs to each instance separately: changes in one object are not visible in others. | «no» Пояснение: A static property belongs to the class itself, not to any individual instance, so all instances share the same value and changes are visible across all objects.
Raw{"answer": "no", "explanation": "A static property belongs to the class itself, not to any individual instance, so all instances share the same value and changes are visible across all objects."} | верно | Наоборот: статическое свойство общее для всех экземпляров класса. Проверено php -r. |
T10-L8 0.9 c | References and scope | An array can have a boolean key true, and it will be stored as bool. | «no» Пояснение: In PHP, boolean keys are cast to integers: true becomes 1 and false becomes 0.
Raw{"answer": "no", "explanation": "In PHP, boolean keys are cast to integers: true becomes 1 and false becomes 0."} | верно | Булев ключ приводится к int: true → 1, false → 0. |
T11-L1 1.36 c | Generators, iterators, SPL | Inside a generator, return with a value can be used, and it becomes available via $gen->getReturn(). | «yes» Пояснение: Since PHP 7.0, you can use a return statement with a value inside a generator, and retrieve it via the Generator object's getReturn() method after the generator is complete.
Raw{"answer": "yes", "explanation": "Since PHP 7.0, you can use a return statement with a value inside a generator, and retrieve it via the Generator object's getReturn() method after the generator is complete."} | верно | return-значение генератора доступно через getReturn() после прохода. |
T11-L2 1.22 c | Generators, iterators, SPL | A fully consumed generator can be rewound with rewind() and traversed again. | «no» Пояснение: A PHP generator's rewind() is a no-op; once fully consumed, you must call the generator function again to get a fresh iterator.
Raw{"answer": "no", "explanation": "A PHP generator's rewind() is a no-op; once fully consumed, you must call the generator function again to get a fresh iterator."} | верно | Генератор одноразовый: rewind после начала итерации бросает Exception. |
T11-L3 0.91 c | Generators, iterators, SPL | The yield from construct delegates traversal to another generator or iterable. | «yes» Пояснение: In PHP 7.0+, `yield from` delegates traversal to another generator or iterable, flattening nested iteration.
Raw{"answer": "yes", "explanation": "In PHP 7.0+, `yield from` delegates traversal to another generator or iterable, flattening nested iteration."} | верно | yield from проксирует значения, ключи и return-значение внутреннего генератора. |
T11-L4 0.7 c | Generators, iterators, SPL | What does get_class(g()) return for function g() { yield 1; }? | «generator» Пояснение: Calling a generator function (one containing yield) returns a Generator object, so get_class() on it returns 'Generator'.
Raw{"answer": "Generator", "explanation": "Calling a generator function (one containing yield) returns a Generator object, so get_class() on it returns 'Generator'."} | верно | Функция с yield возвращает Generator. |
T11-L5 1.17 c | Generators, iterators, SPL | How many elements will count(iterator_to_array((function () { yield from [1, 2, 3]; })())) return? | «3» Пояснение: The generator yields 1, 2, 3; iterator_to_array converts it to [1, 2, 3]; count returns 3.
Raw{"answer": 3, "explanation": "The generator yields 1, 2, 3; iterator_to_array converts it to [1, 2, 3]; count returns 3."} | верно | yield from делегирует все 3 элемента. |
T11-L6 0.61 c | Generators, iterators, SPL | The SplStack class implements a FIFO queue. | «no» Пояснение: SplStack implements a LIFO (Last In, First Out) stack, while SplQueue implements a FIFO queue.
Raw{"answer": "no", "explanation": "SplStack implements a LIFO (Last In, First Out) stack, while SplQueue implements a FIFO queue."} | верно | SplStack — стек LIFO; очередь FIFO — SplQueue. |
T11-L7 0.78 c | Generators, iterators, SPL | ArrayIterator allows wrapping an array and traversing it via the Iterator interface. | «yes» Пояснение: ArrayIterator is a built-in PHP class that wraps an array and implements the Iterator interface, allowing traversal via current(), next(), key(), valid(), and rewind().
Raw{"answer": "yes", "explanation": "ArrayIterator is a built-in PHP class that wraps an array and implements the Iterator interface, allowing traversal via current(), next(), key(), valid(), and rewind()."} | верно | Объектная обёртка над массивом. |
T11-L8 0.72 c | Generators, iterators, SPL | An ArrayObject instance cannot be traversed with foreach. | «no» Пояснение: ArrayObject implements IteratorAggregate, so it can be traversed with foreach.
Raw{"answer": "no", "explanation": "ArrayObject implements IteratorAggregate, so it can be traversed with foreach."} | верно | ArrayObject реализует IteratorAggregate — foreach по нему работает. |
T12-L1 1.1 c | Configuration and security | password_hash() generates a salt automatically — passing one separately is not needed. | «yes» Пояснение: password_hash() automatically generates and embeds a random salt into the returned hash string; no separate salt parameter is needed.
Raw{"answer": "yes", "explanation": "password_hash() automatically generates and embeds a random salt into the returned hash string; no separate salt parameter is needed."} | верно | Соль встраивается в строку результата; параметр salt устарел. |
T12-L2 1.36 c | Configuration and security | In PHP 8, PASSWORD_DEFAULT is md5 with an automatically added salt. | «no» Пояснение: In PHP 8, PASSWORD_DEFAULT is Argon2id (PASSWORD_ARGON2ID), not md5.
Raw{"answer": "no", "explanation": "In PHP 8, PASSWORD_DEFAULT is Argon2id (PASSWORD_ARGON2ID), not md5."} | верно | PASSWORD_DEFAULT — bcrypt; md5 для паролей непригоден (перебирается массово). |
T12-L3 0.99 c | Configuration and security | What does password_verify('secret', password_hash('secret', PASSWORD_DEFAULT)) return? | «yes» Пояснение: password_verify() returns true when the plain-text password matches the hash, which it does here since both use 'secret'.
Raw{"answer": "yes", "explanation": "password_verify() returns true when the plain-text password matches the hash, which it does here since both use 'secret'."} | верно | Соль и хеш в одной строке: true (форма ответа: true или да). |
T12-L4 0.92 c | Configuration and security | strip_tags() protects against SQL injection. | «no» Пояснение: strip_tags() removes HTML/PHP tags from a string; SQL injection is prevented by prepared statements or parameterized queries, not by stripping tags.
Raw{"answer": "no", "explanation": "strip_tags() removes HTML/PHP tags from a string; SQL injection is prevented by prepared statements or parameterized queries, not by stripping tags."} | верно | strip_tags режет HTML-теги (помощник против XSS), к параметризации SQL отношения не имеет. |
T12-L5 0.95 c | Configuration and security | session_regenerate_id() is used to protect against session fixation upon user login. | «yes» Пояснение: session_regenerate_id() generates a new session ID while preserving session data, which is the standard defense against session fixation attacks after a user's authentication state changes.
Raw{"answer": "yes", "explanation": "session_regenerate_id() generates a new session ID while preserving session data, which is the standard defense against session fixation attacks after a user's authentication state changes."} | верно | Новый ID сессии после логина — стандартная защита от session fixation. |
T12-L6 0.79 c | Configuration and security | Which built-in function returns the SAPI name (e.g., cli)? | «php_sapi_name» Пояснение: php_sapi_name() is the built-in PHP function that returns the current SAPI module name, such as 'cli', 'apache2', or 'fpm-fcgi'.
Raw{"answer": "php_sapi_name", "explanation": "php_sapi_name() is the built-in PHP function that returns the current SAPI module name, such as 'cli', 'apache2', or 'fpm-fcgi'."} | верно | php_sapi_name(). |
T12-L7 0.97 c | Configuration and security | session_destroy() deletes session data on the server but not the cookie in the user's browser. | «yes» Пояснение: session_destroy() only removes the session data on the server; the session cookie in the browser persists unless explicitly deleted with setcookie() using a past expiration time.
Raw{"answer": "yes", "explanation": "session_destroy() only removes the session data on the server; the session cookie in the browser persists unless explicitly deleted with setcookie() using a past expiration time."} | верно | Удаление cookie — отдельный шаг через setcookie с истёкшим сроком. |
T12-L8 1.08 c | Configuration and security | Without calling session_start(), the $_SESSION array is automatically populated with session data. | «no» Пояснение: The $_SESSION array is only populated with session data after session_start() is called, which initializes the session and loads stored data into $_SESSION.
Raw{"answer": "no", "explanation": "The $_SESSION array is only populated with session data after session_start() is called, which initializes the session and loads stored data into $_SESSION."} | верно | Без session_start() данные сессии в массив не загружаются ($_SESSION можно заполнить вручную, но привязки к сессии нет). |
VC-L1 0.72 c | PHP 8.4–8.5 | In which PHP version was the array_find() function introduced? | «8.1» Пояснение: The array_find() function was introduced in PHP 8.1 as part of the higher-order array functions.
Raw{"answer": 8.1, "explanation": "The array_find() function was introduced in PHP 8.1 as part of the higher-order array functions."} | неверно верный: «8.4» | PHP 8.4 (RFC array_find). |
VC-L2 1.12 c | PHP 8.4–8.5 | Property hooks (get/set right in the property declaration) landed in PHP 8.4. | «yes» Пояснение: Property hooks (get/set defined inline on a property declaration) were indeed introduced in PHP 8.4.
Raw{"answer": "yes", "explanation": "Property hooks (get/set defined inline on a property declaration) were indeed introduced in PHP 8.4."} | верно | Property hooks — PHP 8.4 (ноябрь 2024). |
VC-L3 0.99 c | PHP 8.4–8.5 | Asymmetric visibility (public private(set) string $name) appeared in PHP 8.4. | «yes» Пояснение: Asymmetric visibility (e.g. public private(set) string $name) is a feature introduced in PHP 8.4, allowing different read and write visibility levels for properties.
Raw{"answer": "yes", "explanation": "Asymmetric visibility (e.g. public private(set) string $name) is a feature introduced in PHP 8.4, allowing different read and write visibility levels for properties."} | верно | Asymmetric visibility v2 — PHP 8.4. |
VC-L4 1.17 c | PHP 8.4–8.5 | In which PHP version was the #[\NoDiscard] attribute introduced? Answer with the version number. | «8.4» Пояснение: The #[\NoDiscard] attribute was introduced in PHP 8.4 to warn developers when a function's return value is discarded.
Raw{"answer": 8.4, "explanation": "The #[\\NoDiscard] attribute was introduced in PHP 8.4 to warn developers when a function's return value is discarded."} | неверно верный: «8.5» | #[\NoDiscard] — PHP 8.5 (marking return values as important). |
VC-L5 5.17 c | PHP 8.4–8.5 | In which PHP version did the pipe operator |> first appear? Answer with the version number. | «8.4» Пояснение: The pipe operator |> was introduced in PHP 8.4.
Raw{"answer": 8.4, "explanation": "The pipe operator |> was introduced in PHP 8.4."} | неверно верный: «8.5» | Pipe operator — PHP 8.5 (2025). |
VC-L6 0.86 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.4» Пояснение: The clone-with syntax (clone($obj, ['x' => 1]) was introduced in PHP 8.4.
Raw```json ⏎ {"answer": "8.4", "explanation": "The clone-with syntax (clone($obj, ['x' => 1]) was introduced in PHP 8.4."} ⏎ ``` | неверно верный: «8.5» | Clone with v2 — PHP 8.5. |
VC-L7 1.52 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 3.66 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. | «8.5» Пояснение: The RFC Partial Function Application v2 was adopted for PHP 8.5.
Raw```json ⏎ {"answer": "8.5", "explanation": "The RFC Partial Function Application v2 was adopted for PHP 8.5."} ⏎ ``` | неверно верный: «8.6» | PFA v2 принят 05.12.2025 (33-0-0), реализован в PHP 8.6. |
VF-L1 0.9 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.4» Пояснение: The RFC clamp_v2 was accepted and the clamp() function was implemented in PHP 8.4.
Raw{"answer": "8.4", "explanation": "The RFC clamp_v2 was accepted and the clamp() function was implemented in PHP 8.4."} | неверно верный: «8.6» | По данным владельца (wiki.php.net/rfc): clamp_v2 — 8.6; clamp() в 8.5.11 отсутствует (косвенное подтверждение). Дата-якорь делает клетку монотонной. |
VF-L2 4.0 c | PHP: 8.6+ and the future | RFC Context Managers v2 has already been adopted in PHP (as of 2026-11-07). | «no» Пояснение: As of late 2026, the Context Managers v2 RFC had not yet been fully adopted into PHP; it was still in the proposal or voting stage.
Raw```json ⏎ {"answer": "no", "explanation": "As of late 2026, the Context Managers v2 RFC had not yet been fully adopted into PHP; it was still in the proposal or voting stage."} ⏎ ``` | верно | На 06.11.2026 — в обсуждении (создан 2026-10-23); не принят. |
VF-L3 2.84 c | PHP: 8.6+ and the future | RFC Bound-Erased Generic Types (generics) was declined in 2026. | «no» Пояснение: The Generic Types (Bound-Erased Generic Types) RFC was accepted in 2024 for PHP 8.4, not declined in 2026.
Raw{"answer": "no", "explanation": "The Generic Types (Bound-Erased Generic Types) RFC was accepted in 2024 for PHP 8.4, not declined in 2026."} | неверно верный: «yes» | Голосование завершилось 2026-06-28: отклонён (wiki.php.net/rfc). |
VF-L4 3.74 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» Пояснение: An RFC to make the Zend Thread Safe (ZTS) build the default in PHP was accepted as part of the PHP 9.0 development cycle, ahead of the 2026-11-07 date.
Raw{"answer": "yes", "explanation": "An RFC to make the Zend Thread Safe (ZTS) build the default in PHP was accepted as part of the PHP 9.0 development cycle, ahead of the 2026-11-07 date."} | неверно верный: «no» | Такого принятого RFC нет на дату якоря; якорь делает клетку монотонной — при принятии RFC позже клетка не перевернётся. |
VF-L5 1.53 c | PHP: 8.6+ and the future | As of PHP 8.5, generics (parameterized types) are still absent. | «yes» Пояснение: Despite long-standing discussions and RFCs, PHP has not shipped generics (parameterized types) as of PHP 8.5.
Raw{"answer": "yes", "explanation": "Despite long-standing discussions and RFCs, PHP has not shipped generics (parameterized types) as of PHP 8.5."} | верно | Generics в PHP отсутствуют; отрицательный контроль (не путать с C#/Java). |
VF-L6 2.24 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» Пояснение: PHP follows a yearly release cycle in mid-to-late November, so as of 2026-11-07 the latest stable would be 8.5 (released Nov 2025), with 8.6 scheduled for GA on 2026-11-19.
Raw{"answer": "yes", "explanation": "PHP follows a yearly release cycle in mid-to-late November, so as of 2026-11-07 the latest stable would be 8.5 (released Nov 2025), with 8.6 scheduled for GA on 2026-11-19."} | верно | 8.5 — релиз осени 2025; 8.6 GA 19.11.2026 (wiki.php.net/todo/php86). Дата снимка — 06.11.2026. |
VF-L7 1.12 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 planned but never released; the version numbering went directly from PHP 5.6 to PHP 7.0 in December 2015.
Raw{"answer": "yes", "explanation": "PHP 6 was planned but never released; the version numbering went directly from PHP 5.6 to PHP 7.0 in December 2015."} | верно | Исторический факт: ветка 6 не была релизнута. |
VF-L8 2.21 c | PHP: 8.6+ and the future | The RFC adding the #[\Deprecated] attribute to the core was adopted. | «no» Пояснение: The RFC for the #[\Deprecated] attribute was voted on for PHP 8.4 but was not adopted (it failed to reach the required two-thirds majority).
Raw{"answer": "no", "explanation": "The RFC for the #[\\Deprecated] attribute was voted on for PHP 8.4 but was not adopted (it failed to reach the required two-thirds majority)."} | неверно верный: «yes» | #[\Deprecated] — принят, реализован в PHP 8.4. |
T25-L1 1.19 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/onion architecture, the dependency rule mandates that dependencies always point inward (toward the domain core), so inner layers have no knowledge of outer layers.
Raw{"answer": "yes", "explanation": "In clean/onion architecture, the dependency rule mandates that dependencies always point inward (toward the domain core), so inner layers have no knowledge of outer layers."} | верно | Чистая (Robert C. Martin), луковичная (Jeffrey Palermo) и гексагональная (ports & adapters) — варианты одной идеи: зависимости направлены внутрь, к домену. Слоями в проекте следит deptrac. |
T25-L2 1.12 c | Clean architecture | Domain entities import neither Doctrine nor Symfony — only the language and, possibly, the standard library. | «yes» Пояснение: In DDD and clean architecture, domain entities should be pure PHP classes with no framework or ORM dependencies, relying only on the language and standard library.
Raw{"answer": "yes", "explanation": "In DDD and clean architecture, domain entities should be pure PHP classes with no framework or ORM dependencies, relying only on the language and standard library."} | верно | Изоляция домена от инфраструктуры; deptrac в проекте как раз следит за слоями. |
T25-L3 1.12 c | Clean architecture | Controllers and Twig templates belong to the business-logic layer because they are the ones calling use cases. | «no» Пояснение: Controllers and Twig templates belong to the presentation (interface) layer; they call use cases but are not part of the business-logic layer.
Raw{"answer": "no", "explanation": "Controllers and Twig templates belong to the presentation (interface) layer; they call use cases but are not part of the business-logic layer."} | верно | Наоборот: это интерфейсные адаптеры (внешний слой); они зависят от use cases, а не наоборот. |
T25-L4 1.4 c | Clean architecture | What sits at the very center of the onion architecture? | «enterprise business rules» Пояснение: In the onion (clean) architecture, the innermost layer contains the enterprise business rules and domain entities, which have no dependencies on any outer layers.
Raw{"answer": "Enterprise Business Rules", "explanation": "In the onion (clean) architecture, the innermost layer contains the enterprise business rules and domain entities, which have no dependencies on any outer layers."} | неверно верный: «domain model» | Центральное кольцо — Domain Model: сущности и бизнес-правила без зависимостей; далее Domain Services → Application Services → Infrastructure/UI/Tests (Palermo). |
T25-L5 1.07 c | Clean architecture | Layer boundary violations can be caught automatically: a layer-dependency analyzer (e.g. deptrac) fails on a forbidden call. | «yes» Пояснение: Deptrac and similar layer-dependency analyzers can be configured with forbidden layer dependencies and will fail the build when a violation is detected, enabling automated detection of layer boundary violations.
Raw{"answer": "yes", "explanation": "Deptrac and similar layer-dependency analyzers can be configured with forbidden layer dependencies and will fail the build when a violation is detected, enabling automated detection of layer boundary violations."} | верно | depfile.yaml в проекте TasK: CI проверяет правила слоёв на каждом пайплайне. |
T25-L6 2.57 c | Clean architecture | A use case (interactor) may accept an HTTP request or an EntityManager as arguments — it is simpler that way. | «no» Пояснение: A use case (interactor) should accept domain-level data (DTOs, arrays) rather than infrastructure objects like HTTP requests or EntityManagers, to maintain separation of concerns and testability.
Raw{"answer": "no", "explanation": "A use case (interactor) should accept domain-level data (DTOs, arrays) rather than infrastructure objects like HTTP requests or EntityManagers, to maintain separation of concerns and testability."} | верно | Use case принимает DTO и порты; привязка к HTTP/ORM протекает инфраструктуру во внутренние слои. |
T25-L7 1.09 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 provides a collection-like interface for accessing domain entities/aggregates while abstracting the underlying storage mechanism.
Raw{"answer": "Repository", "explanation": "The Repository pattern provides a collection-like interface for accessing domain entities/aggregates while abstracting the underlying storage mechanism."} | верно | Repository pattern (DDD/Evans); в проекте — Doctrine-репозитории за портами. |
T25-L8 2.06 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, the database is an infrastructure concern in the outermost layer; the domain and use cases depend only on abstractions (interfaces/ports), so swapping the database engine requires changes only in the outermost layer.
Raw{"answer": "yes", "explanation": "In Clean Architecture, the database is an infrastructure concern in the outermost layer; the domain and use cases depend only on abstractions (interfaces/ports), so swapping the database engine requires changes only in the outermost layer."} | верно | Следствие правила зависимостей: инфраструктура взаимозаменяема. |
T26-L1 1.48 c | DDD | In DDD, an aggregate is just another name for a database table. | «no» Пояснение: An aggregate is a cluster of domain objects (entities and value objects) treated as a single unit for consistency, and it can span multiple tables or be part of one table — it is a domain-level concept, not a synonym for a database table.
Raw{"answer": "no", "explanation": "An aggregate is a cluster of domain objects (entities and value objects) treated as a single unit for consistency, and it can span multiple tables or be part of one table — it is a domain-level concept, not a synonym for a database table."} | верно | Агрегат — кластер объектов с границей согласованности (транзакционной вокруг корня); таблица — деталь хранения. |
T26-L2 0.8 c | DDD | A Value Object is immutable and compared by the values of its fields, not by identity. | «yes» Пояснение: By definition in DDD, Value Objects are immutable and use value-based equality rather than reference identity.
Raw{"answer": "yes", "explanation": "By definition in DDD, Value Objects are immutable and use value-based equality rather than reference identity."} | верно | Классика Evans: Money, Email; равенство структурное. |
T26-L3 0.93 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 is the single entry point through which all changes to an aggregate must pass.
Raw{"answer": "Aggregate Root", "explanation": "In Domain-Driven Design, the Aggregate Root is the single entry point through which all changes to an aggregate must pass."} | верно | Aggregate Root: внешние объекты ссылаются только на корень; он защищает инварианты агрегата. |
T26-L4 1.11 c | DDD | In DDD, a repository is declared for an aggregate (its root), not for every entity. | «yes» Пояснение: In DDD, repositories are declared for aggregate roots only, as they define the consistency boundary; entities within an aggregate are accessed through the root.
Raw{"answer": "yes", "explanation": "In DDD, repositories are declared for aggregate roots only, as they define the consistency boundary; entities within an aggregate are accessed through the root."} | верно | Репозиторий корня хранит границу согласованности агрегата; вложенные сущности доступны только через корень. |
T26-L5 0.95 c | DDD | Ubiquitous language is the model's shared language common to developers and domain experts. | «yes» Пояснение: Ubiquitous Language is a Domain-Driven Design concept defined as the shared vocabulary used consistently by both developers and domain experts.
Raw{"answer": "yes", "explanation": "Ubiquitous Language is a Domain-Driven Design concept defined as the shared vocabulary used consistently by both developers and domain experts."} | верно | Evans: язык из требований переходит в имена классов и методов. |
T26-L6 3.7 c | DDD | What is the boundary called within which a model and its language are consistent, while outside the same words mean other models? | «frame» Пояснение: A frame is the conceptual boundary within which a model and its language maintain consistent meaning, while outside it the same terms may refer to different models.
Raw```json ⏎ {"answer": "frame", "explanation": "A frame is the conceptual boundary within which a model and its language maintain consistent meaning, while outside it the same terms may refer to different models."} ⏎ ``` | неверно верный: «bounded context» | Bounded Context; «Заказ» в биллинге и в доставке — разные модели. |
T26-L7 1.38 c | DDD | An anemic model (objects with only getters/setters, logic in services) is the recommended DDD style. | «no» Пояснение: DDD recommends rich domain models where entities and value objects encapsulate business logic, not anemic models with logic in services.
Raw{"answer": "no", "explanation": "DDD recommends rich domain models where entities and value objects encapsulate business logic, not anemic models with logic in services."} | верно | Наоборот: Evans называет анемичность антипаттерном — поведение должно жить в доменных объектах. |
T26-L8 1.47 c | DDD | Bounded context means each context has its own model: the same concept in different contexts is a different class. | «yes» Пояснение: In DDD, a bounded context has its own model, and the same real-world concept can be represented by different classes with different attributes and behaviors in different contexts.
Raw{"answer": "yes", "explanation": "In DDD, a bounded context has its own model, and the same real-world concept can be represented by different classes with different attributes and behaviors in different contexts."} | верно | Модели контекстов независимы; между ними — явная интеграция (ACL, published language). |
T13-L1 0.89 c | Symfony | Services in the Symfony DI container are created lazily by default — on first use. | «yes» Пояснение: Symfony's DI container instantiates services lazily, meaning they are only created when first requested rather than at container build time.
Raw{"answer": "yes", "explanation": "Symfony's DI container instantiates services lazily, meaning they are only created when first requested rather than at container build time."} | верно | Контейнер инстанцирует сервис при первом извлечении; eager-создания по умолчанию нет. |
T13-L2 0.86 c | Symfony | Which Symfony console command lists all registered routes? | «debug:router» Пояснение: The Symfony console command 'debug:router' lists all registered routes in the application.
Raw{"answer": "debug:router", "explanation": "The Symfony console command 'debug:router' lists all registered routes in the application."} | верно | bin/console debug:router (FrameworkBundle); в Symfony 3 команда называлась router:debug. |
T13-L3 1.19 c | Symfony | Symfony autowiring requires manually declaring every service in services.yaml. | «no» Пояснение: Autowiring automatically resolves dependencies via type-hints, so you do not need to manually declare every service or its dependencies in services.yaml.
Raw{"answer": "no", "explanation": "Autowiring automatically resolves dependencies via type-hints, so you do not need to manually declare every service or its dependencies in services.yaml."} | верно | Autowire+autoconfigure регистрируют и связывают сервисы автоматически; ручное перечисление — исключение. |
T13-L4 1.76 c | Symfony | Twig templates are compiled into PHP classes and cached between requests. | «yes» Пояснение: Twig compiles templates into PHP classes that extend \Twig\Template and caches them as PHP files for reuse between requests.
Raw{"answer": "yes", "explanation": "Twig compiles templates into PHP classes that extend \\Twig\\Template and caches them as PHP files for reuse between requests."} | верно | Twig компилирует шаблон один раз; кэш в var/cache/twig, в prod не пересобирается. |
T13-L5 1.21 c | Symfony | In the Symfony dev environment the DI container is rebuilt only after tracked files change, not on every request. | «yes» Пояснение: Symfony's dev environment caches the compiled DI container and only rebuilds it when tracked files (config, classes, etc.) have been modified, not on every request.
Raw{"answer": "yes", "explanation": "Symfony's dev environment caches the compiled DI container and only rebuilds it when tracked files (config, classes, etc.) have been modified, not on every request."} | верно | Kernel проверяет freshness ресурсов (конфиги, классы); иначе переиспользуется кэш контейнера. |
T13-L6 0.84 c | Symfony | Which environment variable selects the active Symfony environment (dev/prod)? | «app_env» Пояснение: The APP_ENV environment variable is used to select the active Symfony environment (e.g., dev, prod, test) in modern Symfony versions (5+).
Raw{"answer": "APP_ENV", "explanation": "The APP_ENV environment variable is used to select the active Symfony environment (e.g., dev, prod, test) in modern Symfony versions (5+)."} | верно | APP_ENV в .env; APP_DEBUG — отдельный флаг отладки. |
T13-L7 3.92 c | Symfony | A controller method can be private — Symfony routing works with any method of the class. | «no» Пояснение: Symfony's controller resolver invokes the method via an array callable from outside the class, so a private method will throw a 'Call to private method' error; the method must be public (or at least protected/visible to the caller).
Raw{"answer": "no", "explanation": "Symfony's controller resolver invokes the method via an array callable from outside the class, so a private method will throw a 'Call to private method' error; the method must be public (or at least protected/visible to the caller)."} | верно | Действие контроллера должно быть public; приватный метод по маршруту не вызывается. |
T13-L8 2.28 c | Symfony | Event subscribers always receive events before listeners, because the interface gives them priority. | «no» Пояснение: Priority is determined by the numeric priority value assigned to each handler, not by whether it is registered as a subscriber or a listener; the subscriber interface does not grant inherent priority.
Raw```json ⏎ {"answer": "no", "explanation": "Priority is determined by the numeric priority value assigned to each handler, not by whether it is registered as a subscriber or a listener; the subscriber interface does not grant inherent priority."} ⏎ ``` | верно | Порядок определяет priority, а не тип подписки; приоритеты задаются в getSubscribedEvents() так же, как у слушателей. |
T22-L1 1.25 c | Symfony: Security and forms | In modern Symfony (6.0+) authentication is built on authenticator classes (AuthenticatorInterface); the old guard system has been removed. | «yes» Пояснение: Symfony 5.3 deprecated the guard system and Symfony 6.0 removed it, replacing it with the new authenticator-based system built on AuthenticatorInterface.
Raw{"answer": "yes", "explanation": "Symfony 5.3 deprecated the guard system and Symfony 6.0 removed it, replacing it with the new authenticator-based system built on AuthenticatorInterface."} | верно | Guard объявлен устаревшим в 5.3 и удалён в 6.0; в проекте symfony/security-bundle 8.1. |
T22-L2 1.18 c | Symfony: Security and forms | Which Symfony attribute checks a role/permission right on a controller method (403 without it)? | «isgranted» Пояснение: The #[IsGranted] attribute in Symfony checks if the user has a specified role or permission on a controller method, throwing AccessDeniedException (403) if not.
Raw{"answer": "IsGranted", "explanation": "The #[IsGranted] attribute in Symfony checks if the user has a specified role or permission on a controller method, throwing AccessDeniedException (403) if not."} | верно | #[IsGranted('ROLE_ADMIN')]; атрибут из symfony/security-http. |
T22-L3 1.25 c | Symfony: Security and forms | Voters are Symfony's mechanism for checking access to a specific object: isGranted('EDIT', $post). | «yes» Пояснение: Voters in Symfony are the mechanism for object-level security checks, allowing you to use isGranted('EDIT', $post) to check access to a specific object.
Raw{"answer": "yes", "explanation": "Voters in Symfony are the mechanism for object-level security checks, allowing you to use isGranted('EDIT', $post) to check access to a specific object."} | верно | VoterInterface->vote(); docs Symfony — Voters. |
T22-L4 4.22 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» Пояснение: In Symfony 7+, PHP attributes (#[Assert\NotBlank]) are the standard way to declare validation constraints, while doctrine/annotations is deprecated in favor of native PHP attributes.
Raw{"answer": "yes", "explanation": "In Symfony 7+, PHP attributes (#[Assert\\NotBlank]) are the standard way to declare validation constraints, while doctrine/annotations is deprecated in favor of native PHP attributes."} | верно | Докблок-аннотации удалены в Symfony 7.0; стандарт — атрибуты. В проекте symfony/validator 8.1. |
T22-L5 0.96 c | Symfony: Security and forms | CSRF protection of Symfony forms is enabled by default: the form validates the token on submission. | «yes» Пояснение: Since Symfony 3.3, CSRF protection is enabled by default for all forms; a hidden token field is added and validated automatically on submission unless explicitly disabled.
Raw{"answer": "yes", "explanation": "Since Symfony 3.3, CSRF protection is enabled by default for all forms; a hidden token field is added and validated automatically on submission unless explicitly disabled."} | верно | FormType добавляет скрытое поле _token и проверяет его при валидации; отключение — осознанное исключение (csrf: false). |
T22-L6 1.12 c | Symfony: Security and forms | Form validation in Symfony runs server-side even if the client-side (HTML5) checks passed. | «yes» Пояснение: Symfony always performs server-side form validation on submission; client-side HTML5 checks are merely a UX convenience and do not replace server-side validation.
Raw```json ⏎ {"answer": "yes", "explanation": "Symfony always performs server-side form validation on submission; client-side HTML5 checks are merely a UX convenience and do not replace server-side validation."} ⏎ ``` | верно | Клиентская валидация — только удобство; серверная обязательна и идёт по метаданным объекта формы. |
T22-L7 0.51 c | Symfony: Security and forms | Which Symfony maker command generates a form class (FormType)? | «make:form» Пояснение: The Symfony MakerBundle command 'make:form' generates a FormType class.
Raw{"answer": "make:form", "explanation": "The Symfony MakerBundle command 'make:form' generates a FormType class."} | верно | bin/console make:form (symfony/maker-bundle — в проекте). |
T22-L8 1.05 c | Symfony: Security and forms | Symfony stores the user's password in the session in plain text. | «no» Пояснение: Symfony hashes passwords (e.g., with bcrypt or argon2) and stores the hash, not the plain-text password, in the session or database.
Raw{"answer": "no", "explanation": "Symfony hashes passwords (e.g., with bcrypt or argon2) and stores the hash, not the plain-text password, in the session or database."} | верно | В сессии живёт объект пользователя в токене; хеш затирается eraseCredentials(), plaintext там никогда не лежит. |
T23-L1 0.97 c | Symfony: configuration and services | Symfony bundle configuration lives in config/packages — one file per bundle or topic. | «yes» Пояснение: Symfony's convention (since Flex/4.x) is to place each bundle's configuration in its own YAML file under config/packages/.
Raw{"answer": "yes", "explanation": "Symfony's convention (since Flex/4.x) is to place each bundle's configuration in its own YAML file under config/packages/."} | верно | Стандартная структура (config/packages/*.yaml); перегрузка — config/packages/<env>. |
T23-L2 3.5 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» Пояснение: This is the standard pattern (e.g., in Symfony) where .env holds non-sensitive dev defaults committed to VCS, while .env.local holds real secrets and is git-ignored.
Raw{"answer": "yes", "explanation": "This is the standard pattern (e.g., in Symfony) where .env holds non-sensitive dev defaults committed to VCS, while .env.local holds real secrets and is git-ignored."} | верно | symfony/dotenv: .env — общий безопасный набор значений; локальные секреты — .env.local (gitignored) или secrets-хранилище. |
T23-L3 1.33 c | Symfony: configuration and services | Which Symfony command lists the container's registered services and their aliases? | «debug:services» Пояснение: The Symfony command 'debug:services' lists all registered services and their aliases in the service container.
Raw{"answer": "debug:services", "explanation": "The Symfony command 'debug:services' lists all registered services and their aliases in the service container."} | неверно верный: «debug:container» | bin/console debug:container; параметры контейнера — debug:parameter. |
T23-L4 3.92 c | Symfony: configuration and services | The Symfony container allows changing parameters at runtime: $container->setParameter() works from a controller. | «yes» Пояснение: The Container class exposes setParameter() as a public method that stores the value at runtime, so calling it from a controller is valid (though it won't affect already-instantiated services).
Raw```json ⏎ {"answer": "yes", "explanation": "The Container class exposes setParameter() as a public method that stores the value at runtime, so calling it from a controller is valid (though it won't affect already-instantiated services)."} ⏎ ``` | неверно верный: «no» | Контейнер компилируется и замораживается; runtime-значения — только через переменные окружения. |
T23-L5 1.0 c | Symfony: configuration and services | By default, Symfony services are public (public: true) — you can fetch them directly from the container. | «no» Пояснение: Since Symfony 4.1, services are private by default and can only be fetched from the container if they are explicitly set as public or used as a controller, event listener, etc.
Raw{"answer": "no", "explanation": "Since Symfony 4.1, services are private by default and can only be fetched from the container if they are explicitly set as public or used as a controller, event listener, etc."} | верно | С Symfony 4.0 сервисы по умолчанию private: инжектятся через autowiring; $container->get() — только для публичных. |
T23-L6 1.18 c | Symfony: configuration and services | Without a config file in config/packages a bundle will not work — configuration is mandatory for every bundle. | «no» Пояснение: Many Symfony bundles work out of the box without any configuration file in config/packages; configuration is only needed for bundles that require specific settings.
Raw{"answer": "no", "explanation": "Many Symfony bundles work out of the box without any configuration file in config/packages; configuration is only needed for bundles that require specific settings."} | верно | У бандлов есть встроенные умолчания (Extension); конфиг нужен только для отклонений от них. |
T23-L7 0.76 c | Symfony: configuration and services | Environment variable values are injected into services.yaml using the %env(VAR)% syntax. | «yes» Пояснение: Symfony uses the %env(VAR_NAME)% syntax to inject environment variable values into configuration files like services.yaml.
Raw{"answer": "yes", "explanation": "Symfony uses the %env(VAR_NAME)% syntax to inject environment variable values into configuration files like services.yaml."} | верно | %env(...)% резолвится в рантайме env-процессорами; docs — Env Var Processors. |
T23-L8 0.85 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 in Symfony controls whether debug mode is enabled, which activates the profiler and Twig debugging features.
Raw{"answer": "APP_DEBUG", "explanation": "The APP_DEBUG environment variable in Symfony controls whether debug mode is enabled, which activates the profiler and Twig debugging features."} | верно | APP_DEBUG=1 (в .env dev-окружения); окружение выбирает APP_ENV — см. T13-L6. |
T16-L1 1.56 c | Symfony: Messenger | A single message in Symfony Messenger can only have one handler. | «no» Пояснение: Symfony Messenger allows multiple handlers to be registered for the same message class, and all matching handlers will be executed.
Raw{"answer": "no", "explanation": "Symfony Messenger allows multiple handlers to be registered for the same message class, and all matching handlers will be executed."} | верно | Messenger вызывает все хендлеры, подписанные на класс сообщения (docs — Multiple Handlers). |
T16-L2 1.06 c | Symfony: Messenger | The sync transport in Messenger queues the message for a worker, just like async. | «no» Пояснение: The sync transport dispatches the message immediately and calls the handler in the same process without queuing it for a worker.
Raw{"answer": "no", "explanation": "The sync transport dispatches the message immediately and calls the handler in the same process without queuing it for a worker."} | верно | Наоборот: sync обрабатывает немедленно в том же процессе, что и отправка; очередь — это async-транспорт. |
T16-L3 0.72 c | Symfony: Messenger | Which console command starts the worker that processes Messenger queue messages? | «messenger:consume» Пояснение: The Symfony Messenger command 'messenger:consume' starts the worker that processes queued messages.
Raw{"answer": "messenger:consume", "explanation": "The Symfony Messenger command 'messenger:consume' starts the worker that processes queued messages."} | верно | bin/console messenger:consume async; воркеры под supervisord/systemd в проде. |
T16-L4 1.74 c | Symfony: Messenger | Retries for failed messages (retry_strategy) are configured per Messenger transport. | «no» Пояснение: The retry_strategy (max_retries, delay, multiplier, max_delay) is configured per Messenger bus, not per transport.
Raw```json ⏎ {"answer": "no", "explanation": "The retry_strategy (max_retries, delay, multiplier, max_delay) is configured per Messenger bus, not per transport."} ⏎ ``` | неверно верный: «yes» | retry_strategy на транспорте: max_retries, delay, multiplier; docs — Failed Messages & Retries. |
T16-L5 1.43 c | Symfony: Messenger | By default, Messenger serializes messages to JSON. | «yes» Пояснение: Symfony Messenger uses the Symfony Serializer component by default, which serializes messages to JSON format.
Raw{"answer": "yes", "explanation": "Symfony Messenger uses the Symfony Serializer component by default, which serializes messages to JSON format."} | неверно верный: «no» | Дефолтный сериализатор — PhpSerializer (serialize()); JSON-сериализатор включается отдельно. |
T16-L6 2.39 c | Symfony: Messenger | Symfony Scheduler produces messages on a schedule and dispatches them through Messenger. | «yes» Пояснение: Symfony Scheduler schedules tasks to run at defined intervals and integrates with Messenger to dispatch messages to the message bus on that schedule.
Raw{"answer": "yes", "explanation": "Symfony Scheduler schedules tasks to run at defined intervals and integrates with Messenger to dispatch messages to the message bus on that schedule."} | верно | Schedule → RecurringMessage → шина Messenger; docs — Scheduler. |
T16-L7 0.82 c | Symfony: Messenger | Which built-in Messenger transport stores messages in database tables via Doctrine? | «doctrine» Пояснение: Symfony Messenger's doctrine transport stores messages in database tables using Doctrine ORM/DBAL.
Raw{"answer": "doctrine", "explanation": "Symfony Messenger's doctrine transport stores messages in database tables using Doctrine ORM/DBAL."} | верно | Транспорт doctrine (symfony/doctrine-messenger); таблица messenger_messages. В проекте стоит amqp-messenger + doctrine-messenger. |
T16-L8 1.61 c | Symfony: Messenger | The Messenger pipeline can be extended with custom middleware, placed before or after the built-in ones. | «yes» Пояснение: Laravel's Messenger allows you to add custom middleware to the pipeline and control their order relative to built-in ones.
Raw{"answer": "yes", "explanation": "Laravel's Messenger allows you to add custom middleware to the pipeline and control their order relative to built-in ones."} | верно | messenger.bus.*.middleware в yaml; docs — Middleware. |
T28-L1 3.12 c | Symfony: versions | Symfony major releases come every two years, minor ones every six months (in May and November). | «yes» Пояснение: Symfony's official documentation states that releases come every 6 months (May and November), with a major version every 2 years.
Raw```json ⏎ {"answer": "yes", "explanation": "Symfony's official documentation states that releases come every 6 months (May and November), with a major version every 2 years."} ⏎ ``` | верно | Стандартный релизный цикл: 8.0 — ноябрь 2025, 8.1 — май 2026, 8.2 — ноябрь 2026. |
T28-L2 1.24 c | Symfony: versions | What is the minimum PHP version required by Symfony 8? | «8.4» Пояснение: Symfony 8 requires a minimum PHP version of 8.4.
Raw{"answer": "8.4", "explanation": "Symfony 8 requires a minimum PHP version of 8.4."} | верно | Symfony 8.0 поднял требование до PHP >= 8.4.1 (в vendor проекта: "php": ">=8.4.1"). |
T28-L3 3.49 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 PHP 8 attributes; annotation-based routing and validation loaders were deprecated in 6.4 and removed in 7.0.
Raw```json ⏎ {"answer": "no", "explanation": "Symfony 7.0 removed support for docblock annotations in favor of PHP 8 attributes; annotation-based routing and validation loaders were deprecated in 6.4 and removed in 7.0."} ⏎ ``` | верно | Наоборот: в 7.0 аннотации удалены — только PHP-атрибуты (#[Route], #[Assert\NotBlank]). |
T28-L4 0.9 c | Symfony: versions | AssetMapper manages CSS/JS without node or webpack — via importmap.php. | «yes» Пояснение: AssetMapper is a Symfony component that handles CSS/JS asset management without requiring Node.js or Webpack, using importmap.php for module resolution.
Raw{"answer": "yes", "explanation": "AssetMapper is a Symfony component that handles CSS/JS asset management without requiring Node.js or Webpack, using importmap.php for module resolution."} | верно | symfony/asset-mapper (с 6.3, стандарт с 7.x); в проекте — importmap.php в корне и asset-mapper 8.1. |
T28-L5 1.28 c | Symfony: versions | Symfony 6.4 is a regular release without long-term support. | «no» Пояснение: Symfony 6.4 is a Long-Term Support (LTS) release, supported until November 2027.
Raw{"answer": "no", "explanation": "Symfony 6.4 is a Long-Term Support (LTS) release, supported until November 2027."} | верно | Наоборот: 6.4 — LTS (расширенная поддержка); LTS выходит вместе с очередным мажором (6.4 — вместе с 7.0). |
T28-L6 1.34 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» Пояснение: Symfony major versions remove deprecations introduced in the previous major version; that is precisely the purpose of a major release.
Raw{"answer": "no", "explanation": "Symfony major versions remove deprecations introduced in the previous major version; that is precisely the purpose of a major release."} | верно | Наоборот: мажорный релиз удаляет всё устаревшее (7.0 убрал деприкейшены 6.x, 8.0 — 7.x). |
T28-L7 1.05 c | Symfony: versions | Every Symfony major release is accompanied by an UPGRADE guide listing the changes. | «yes» Пояснение: Each Symfony major release includes UPGRADE guide files (both per-component and a global one) that document breaking changes and deprecations.
Raw{"answer": "yes", "explanation": "Each Symfony major release includes UPGRADE guide files (both per-component and a global one) that document breaking changes and deprecations."} | верно | UPGRADE-7.0.md, UPGRADE-8.0.md в репозитории symfony/symfony. |
T28-L8 3.66 c | Symfony: versions | Which Symfony component manages assets and the importmap without node/webpack? | «asset mapper» Пояснение: The Symfony Asset Mapper component (symfony/asset-mapper, introduced in Symfony 6.3) manages assets and importmaps without requiring Node.js or Webpack.
Raw{"answer": "Asset Mapper", "explanation": "The Symfony Asset Mapper component (symfony/asset-mapper, introduced in Symfony 6.3) manages assets and importmaps without requiring Node.js or Webpack."} | верно | symfony/asset-mapper 8.1 — в проекте. |
T29-L1 4.96 c | Symfony: 8.2 and beyond | As of 2026-11-07, Symfony 8.2 has already been released. | «no» Пояснение: Symfony minor releases (x.2) typically ship at the end of November, so as of November 7, 2026, Symfony 8.2 would not yet have been released.
Raw```json ⏎ {"answer": "no", "explanation": "Symfony minor releases (x.2) typically ship at the end of November, so as of November 7, 2026, Symfony 8.2 would not yet have been released."} ⏎ ``` | верно | Наоборот: 8.2 ещё не выпущена — релиз в конце ноября 2026; последняя стабильная — 8.1. |
T29-L2 7.04 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» Пояснение: Following the six-month cycle from Symfony 7.0 (May 2024), Symfony 8.0 is expected in November 2026, not 8.2; 8.2 would be around November 2027.
Raw```json ⏎ {"answer": "no", "explanation": "Following the six-month cycle from Symfony 7.0 (May 2024), Symfony 8.0 is expected in November 2026, not 8.2; 8.2 would be around November 2027."} ⏎ ``` | неверно верный: «yes» | Политика релизов: 8.1 — май 2026, 8.2 — ноябрь 2026; якорь даты фиксирует срез — модель с поздним cutoff отвечает «на дату». |
T29-L3 2.11 c | Symfony: 8.2 and beyond | Which Symfony version comes after 8.1 (as of 2026-11-07)? | «8.2» Пояснение: Symfony releases minor versions every six months; after 8.1 (May 2026) comes 8.2 (November 2026).
Raw{"answer": "8.2", "explanation": "Symfony releases minor versions every six months; after 8.1 (May 2026) comes 8.2 (November 2026)."} | верно | 8.2 — следующий минорный релиз (ноябрь 2026); после его выхода проект переходит с 8.1.* на 8.2.*. |
T29-L4 3.14 c | Symfony: 8.2 and beyond | Symfony 8.2 is a major release requiring applications to be rewritten for new APIs. | «no» Пояснение: Symfony 8.2 would be a minor release (8.x line), not a major one; major releases are denoted by X.0 versions, and even those require migration rather than a full rewrite.
Raw```json ⏎ {"answer": "no", "explanation": "Symfony 8.2 would be a minor release (8.x line), not a major one; major releases are denoted by X.0 versions, and even those require migration rather than a full rewrite."} ⏎ ``` | верно | Наоборот: 8.2 — минорный релиз; новые возможности без поломки обратной совместимости. Мажор — 9.0. |
T29-L5 1.62 c | Symfony: 8.2 and beyond | Updating within a major branch (8.1 → 8.2) should not require code changes — backward compatibility is preserved. | «yes» Пояснение: PHP follows a policy where minor version upgrades within the same major version (e.g., 8.1 to 8.2) maintain backward compatibility and should not require code changes.
Raw{"answer": "yes", "explanation": "PHP follows a policy where minor version upgrades within the same major version (e.g., 8.1 to 8.2) maintain backward compatibility and should not require code changes."} | верно | Политика Symfony: минорные релизы обратно совместимы; BC-break допустим только в мажорных. |
T29-L6 5.55 c | Symfony: 8.2 and beyond | Which minor version of the 8.x branch is released last, before Symfony 9.0? | «8.4» Пояснение: Following Symfony's established pattern (4.4, 5.4, 6.4, 7.4), the last minor release of the 8.x branch before Symfony 9.0 is 8.4.
Raw```json ⏎ {"answer": "8.4", "explanation": "Following Symfony's established pattern (4.4, 5.4, 6.4, 7.4), the last minor release of the 8.x branch before Symfony 9.0 is 8.4."} ⏎ ``` | верно | По циклу: 8.2 (ноя 2026), 8.3 (май 2027), 8.4 (ноя 2027, вместе с 9.0) — как 6.4 выходила вместе с 7.0. |
T29-L7 3.44 c | Symfony: 8.2 and beyond | Symfony 8.2 will require PHP 8.5 — you would have to upgrade PHP along with it. | «no» Пояснение: Symfony 8.x is expected to require PHP 8.4 as its minimum version, not PHP 8.5; minor versions like 8.2 don't typically raise the minimum PHP requirement beyond what the major version set.
Raw{"answer": "no", "explanation": "Symfony 8.x is expected to require PHP 8.4 as its minimum version, not PHP 8.5; minor versions like 8.2 don't typically raise the minimum PHP requirement beyond what the major version set."} | верно | Наоборот: минорные релизы не поднимают требования PHP; для всей ветки 8.x остаётся PHP >= 8.4. |
T29-L8 2.29 c | Symfony: 8.2 and beyond | Deprecations added in the 8.x branch will not be removed before Symfony 9.0. | «yes» Пояснение: Per Symfony's deprecation policy, deprecations introduced in a major version (8.x) are removed in the next major version (9.0), so they are not removed before 9.0.
Raw```json ⏎ {"answer": "yes", "explanation": "Per Symfony's deprecation policy, deprecations introduced in a major version (8.x) are removed in the next major version (9.0), so they are not removed before 9.0."} ⏎ ``` | верно | Политика: деприкейшены живут до следующего мажора; 9.0 — ноябрь 2027. |
T21-L1 2.15 c | Twig | Inside {{ }}, Twig allows calling arbitrary PHP code directly. | «no» Пояснение: Twig's {{ }} allows variables, operators, filters, Twig functions, and method calls on objects, but arbitrary PHP functions/code cannot be called directly without a Twig extension.
Raw{"answer": "no", "explanation": "Twig's {{ }} allows variables, operators, filters, Twig functions, and method calls on objects, but arbitrary PHP functions/code cannot be called directly without a Twig extension."} | верно | Twig — DSL: только разрешённые окружением функции/фильтры; произвольный PHP не исполняется. |
T21-L2 1.1 c | Twig | By default, Twig auto-escapes printed variables. | «yes» Пояснение: Twig enables auto-escaping with the 'html' strategy by default, so variables printed with {{ }} are HTML-escaped unless explicitly marked safe.
Raw{"answer": "yes", "explanation": "Twig enables auto-escaping with the 'html' strategy by default, so variables printed with {{ }} are HTML-escaped unless explicitly marked safe."} | верно | Autoescape включён по умолчанию; {{ '<b>' }} → <b>. Проверено на Twig 3.30. |
T21-L3 1.06 c | Twig | The Twig |e filter escapes a string for safe output in an HTML context. | «yes» Пояснение: The |e (escape) filter in Twig defaults to HTML context escaping, converting characters like <, >, &, ' and " to their HTML entities.
Raw{"answer": "yes", "explanation": "The |e (escape) filter in Twig defaults to HTML context escaping, converting characters like <, >, &, ' and \" to their HTML entities."} | верно | |e ('html') по умолчанию; есть контексты js/url/css. От SQL-инъекций он не защищает — это задача подготовленных запросов Doctrine. |
T21-L4 1.99 c | Twig | Which filter from twig/intl-extra formats a number according to a locale? | «localizednumber» Пояснение: The twig/intl-extra package provides the 'localizednumber' filter which formats a number according to a locale using the intl extension.
Raw{"answer": "localizednumber", "explanation": "The twig/intl-extra package provides the 'localizednumber' filter which formats a number according to a locale using the intl extension."} | неверно верный: «format_number» | |format_number(locale=...) из IntlExtension (twig/intl-extra есть в проекте). Проверено на Twig 3.30: 12345.6 → 12 345,6 (ru). |
T21-L5 3.51 c | Twig | The |raw filter disables auto-escaping for the value. | «yes» Пояснение: The |raw filter (as used in Twig and similar templating engines) outputs a value without auto-escaping, allowing raw HTML to be rendered.
Raw{"answer": "yes", "explanation": "The |raw filter (as used in Twig and similar templating engines) outputs a value without auto-escaping, allowing raw HTML to be rendered."} | верно | {{ x|raw }} выводит HTML как есть; опасно с пользовательскими данными. Проверено на Twig 3.30. |
T21-L6 0.93 c | Twig | In Twig, {{ }} prints an expression value, while {% %} executes tags — conditions, loops, set. | «yes» Пояснение: In Twig, {{ }} outputs expression values, while {% %} is used for control structures like if, for, and set.
Raw{"answer": "yes", "explanation": "In Twig, {{ }} outputs expression values, while {% %} is used for control structures like if, for, and set."} | верно | Два блока синтаксиса Twig: вывод (echo) против логики. |
T21-L7 0.82 c | Twig | In Twig you cannot declare a variable inside a template — values only come from the controller. | «no» Пояснение: Twig allows declaring variables inside templates using the `set` tag, e.g. `{% set foo = 'bar' %}`.
Raw{"answer": "no", "explanation": "Twig allows declaring variables inside templates using the `set` tag, e.g. `{% set foo = 'bar' %}`."} | верно | {% set y = ... %} объявляет переменную в шаблоне. Проверено на Twig 3.30. |
T21-L8 0.7 c | Twig | Which Twig function dumps the debug structure of a variable (array, object)? | «dump» Пояснение: The dump() function in Twig is used to display the debug structure of a variable, provided by the Twig Debug extension.
Raw{"answer": "dump", "explanation": "The dump() function in Twig is used to display the debug structure of a variable, provided by the Twig Debug extension."} | верно | {{ dump(x) }} (DebugExtension; в Symfony доступна в dev-окружении). |
T24-L1 1.04 c | Bootstrap | Bootstrap is a CSS/JS library of ready-made UI components, not an SPA framework. | «yes» Пояснение: Bootstrap is a front-end CSS/JS library providing pre-built UI components (grid, navbar, modal, etc.), not an SPA framework like React or Angular.
Raw{"answer": "yes", "explanation": "Bootstrap is a front-end CSS/JS library providing pre-built UI components (grid, navbar, modal, etc.), not an SPA framework like React or Angular."} | верно | Компоненты и утилиты поверх вашего HTML; SPA-фреймворки (React/Vue) — другой класс инструментов. В проекте vendored 5.3.3. |
T24-L2 1.12 c | Bootstrap | Which Bootstrap class gives a responsive container with a fixed max width per breakpoint? | «container» Пояснение: The .container class in Bootstrap provides a responsive fixed-width container with a max-width that changes at each breakpoint.
Raw{"answer": "container", "explanation": "The .container class in Bootstrap provides a responsive fixed-width container with a max-width that changes at each breakpoint."} | верно | .container (фиксированная макс-ширина по брейкпоинтам) vs .container-fluid (на всю ширину). |
T24-L3 1.12 c | Bootstrap | The Bootstrap grid is built on CSS floats and splits a row into 16 columns. | «no» Пояснение: The Bootstrap grid splits a row into 12 columns (not 16), and modern versions (Bootstrap 4+) use Flexbox rather than CSS floats.
Raw{"answer": "no", "explanation": "The Bootstrap grid splits a row into 12 columns (not 16), and modern versions (Bootstrap 4+) use Flexbox rather than CSS floats."} | верно | Наоборот: flexbox (с Bootstrap 4) и 12 колонок; float-сетка — это Bootstrap 3. |
T24-L4 0.93 c | Bootstrap | Bootstrap's named breakpoints (the infix used in class names) are sm, md, lg, xl, xxl — five of them. | «yes» Пояснение: Bootstrap 5 defines exactly five breakpoints: sm, md, lg, xl, and xxl.
Raw{"answer": "yes", "explanation": "Bootstrap 5 defines exactly five breakpoints: sm, md, lg, xl, and xxl."} | верно | Тиров всего шесть: xs (без инфикса) + пять именованных (576/768/992/1200/1400 px). |
T24-L5 3.08 c | Bootstrap | Utilities like .mt-3 or .px-2 use the spacing scale: the number is a multiple of $spacer. | «no» Пояснение: The numbers in classes like .mt-3 do not represent direct multiples of $spacer; for example, .mt-1 equals $spacer/4 and .mt-3 equals $spacer, not 3×$spacer.
Raw```json ⏎ {"answer": "no", "explanation": "The numbers in classes like .mt-3 do not represent direct multiples of $spacer; for example, .mt-1 equals $spacer/4 and .mt-3 equals $spacer, not 3×$spacer."} ⏎ ``` | верно | Spacing utilities; $spacer = 1rem. |
T24-L6 0.93 c | Bootstrap | Which Bootstrap 5 data attribute enables an interactive component (e.g. dropdown) on an element? | «data-bs-toggle» Пояснение: In Bootstrap 5, the data-bs-toggle attribute is used to enable interactive components such as dropdowns, tooltips, and popovers.
Raw{"answer": "data-bs-toggle", "explanation": "In Bootstrap 5, the data-bs-toggle attribute is used to enable interactive components such as dropdowns, tooltips, and popovers."} | верно | data-bs-toggle="dropdown" и т.п.; в Bootstrap 4 атрибут назывался data-toggle. |
T24-L7 0.88 c | Bootstrap | Bootstrap 5 components work without jQuery — in plain vanilla JS. | «yes» Пояснение: Bootstrap 5 dropped its jQuery dependency and all interactive components are now built with vanilla JavaScript.
Raw{"answer": "yes", "explanation": "Bootstrap 5 dropped its jQuery dependency and all interactive components are now built with vanilla JavaScript."} | верно | jQuery удалён в Bootstrap 5.0: data-bs-* атрибуты и JS API. В проекте vendored 5.3.3. |
T24-L8 1.19 c | Bootstrap | Dark mode in Bootstrap is enabled with a .dark class on the root element. | «no» Пояснение: In Bootstrap 5, dark mode is enabled by adding data-bs-theme="dark" to the <html> element, not a .dark class.
Raw{"answer": "no", "explanation": "In Bootstrap 5, dark mode is enabled by adding data-bs-theme=\"dark\" to the <html> element, not a .dark class."} | верно | Наоборот: тема включается атрибутом data-bs-theme="dark" (Color modes, с 5.3); класса .dark не существует. В проекте 5.3.3. |
T14-L1 1.19 c | Doctrine | Doctrine ORM creates database tables on the fly the first time an entity is used at runtime. | «no» Пояснение: Doctrine ORM does not automatically create tables at runtime; you must explicitly run schema creation commands or migrations to create the database tables.
Raw{"answer": "no", "explanation": "Doctrine ORM does not automatically create tables at runtime; you must explicitly run schema creation commands or migrations to create the database tables."} | верно | Схему создают инструменты (migrations, schema tool); рантайм структуру БД не меняет. |
T14-L2 0.66 c | Doctrine | Which EntityManager method marks a new object as managed without executing SQL until flush()? | «persist()» Пояснение: EntityManager::persist() marks an entity as managed, deferring the actual INSERT SQL until flush() is called.
Raw{"answer": "persist()", "explanation": "EntityManager::persist() marks an entity as managed, deferring the actual INSERT SQL until flush() is called."} | верно | persist() регистрирует объект в Unit of Work; INSERT выполняется на flush(). |
T14-L3 1.81 c | Doctrine | In Doctrine ORM 3, the EntityManager::merge() method exists and makes the passed object managed. | «no» Пояснение: In Doctrine ORM 3, EntityManager::merge() was removed (it was deprecated in ORM 2); the method no longer exists.
Raw{"answer": "no", "explanation": "In Doctrine ORM 3, EntityManager::merge() was removed (it was deprecated in ORM 2); the method no longer exists."} | верно | В ORM 3 merge() удалён (в vendor проекта 3.7.6 метода нет); в Doctrine 2.x merge() возвращал управляемую копию. Версия зафиксирована — ORM 3. |
T14-L4 1.03 c | Doctrine | DQL queries are written in terms of entities and their fields, not tables and columns. | «yes» Пояснение: DQL operates at the object model level, using entity class names and their mapped fields rather than raw table and column names.
Raw{"answer": "yes", "explanation": "DQL operates at the object model level, using entity class names and their mapped fields rather than raw table and column names."} | верно | Doctrine транслирует DQL в SQL; docs — DQL (Doctrine Query Language). |
T14-L5 0.9 c | Doctrine | What does $repository->find(999) return when no record with id 999 exists? | «null» Пояснение: Doctrine's Repository::find() returns null when no entity with the given ID exists.
Raw{"answer": "null", "explanation": "Doctrine's Repository::find() returns null when no entity with the given ID exists."} | верно | find() возвращает null, если объект не найден (docs Repository methods). |
T14-L6 2.32 c | Doctrine | DoctrineBundle in Symfony automatically calls flush() at the end of every request. | «no» Пояснение: DoctrineBundle does not automatically call flush() at the end of a request; you must explicitly call $entityManager->flush() to persist changes.
Raw{"answer": "no", "explanation": "DoctrineBundle does not automatically call flush() at the end of a request; you must explicitly call $entityManager->flush() to persist changes."} | верно | Авто-flush нет — flush() зовёт разработчик; незакрытая транзакция в конце запроса откатывается. |
T14-L7 1.46 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» Пояснение: The Unit of Work tracks changes to managed entities by comparing their current state against a snapshot, so flush() alone is sufficient to commit modifications without calling persist() again.
Raw{"answer": "yes", "explanation": "The Unit of Work tracks changes to managed entities by comparing their current state against a snapshot, so flush() alone is sufficient to commit modifications without calling persist() again."} | верно | Dirty checking сравнивает снимки свойств; persist нужен только новым/отсоединённым объектам. |
T14-L8 0.86 c | Doctrine | remove() executes the SQL DELETE immediately, without waiting for flush(). | «no» Пояснение: remove() only marks the entity for deletion in the UnitOfWork; the actual SQL DELETE is executed on flush().
Raw{"answer": "no", "explanation": "remove() only marks the entity for deletion in the UnitOfWork; the actual SQL DELETE is executed on flush()."} | верно | remove() планирует удаление в Unit of Work; DELETE выполняется на flush() (docs — Deleting Objects). |
T15-L1 1.03 c | PostgreSQL | PostgreSQL uses MVCC, therefore readers block writers and writers block readers. | «no» Пояснение: MVCC's entire purpose is to allow readers and writers to proceed concurrently without blocking each other; each transaction sees a consistent snapshot of the data.
Raw{"answer": "no", "explanation": "MVCC's entire purpose is to allow readers and writers to proceed concurrently without blocking each other; each transaction sees a consistent snapshot of the data."} | верно | Наоборот: благодаря MVCC читатели не блокируют писателей и наоборот (снимки строк); docs PostgreSQL — Concurrency Control. |
T15-L2 0.63 c | PostgreSQL | Which SQL command shows a query's execution plan without executing the query? | «explain» Пояснение: The EXPLAIN command displays the query execution plan without actually executing the query.
Raw{"answer": "EXPLAIN", "explanation": "The EXPLAIN command displays the query execution plan without actually executing the query."} | верно | EXPLAIN без ANALYZE только строит план; проверено на PostgreSQL 17.7. |
T15-L3 2.05 c | PostgreSQL | SERIAL and GENERATED ... AS IDENTITY are just two names for the same mechanism. | «no» Пояснение: While both involve sequences under the hood, SERIAL creates an explicit sequence object separate from the column, whereas GENERATED AS IDENTITY uses an internal mechanism where the sequence is implicitly tied to the column and they behave differently in edge cases like dropping the column.
Raw{"answer":"no","explanation":"While both involve sequences under the hood, SERIAL creates an explicit sequence object separate from the column, whereas GENERATED AS IDENTITY uses an internal mechanism where the sequence is implicitly tied to the column and they behave differently in edge cases like dropping the column."} | верно | SERIAL — нестандартный макрос (sequence + DEFAULT), IDENTITY — SQL-стандарт; различаются владением и правами. Оба есть в PG 17 (проверено). |
T15-L4 1.29 c | PostgreSQL | By default, a PostgreSQL UNIQUE constraint allows only one row with NULL in the column. | «no» Пояснение: In PostgreSQL, NULL values are considered distinct from each other by default, so a UNIQUE constraint allows multiple rows with NULL in that column.
Raw{"answer": "no", "explanation": "In PostgreSQL, NULL values are considered distinct from each other by default, so a UNIQUE constraint allows multiple rows with NULL in that column."} | верно | Наоборот: NULLS DISTINCT по умолчанию — несколько NULL допустимы; NULLS NOT DISTINCT — опция с PG 15. Проверено на PG 17.7. |
T15-L5 0.42 c | PostgreSQL | Which PostgreSQL aggregate function concatenates strings with a separator? | «string_agg» Пояснение: string_agg(expression, delimiter) is the PostgreSQL aggregate function that concatenates strings with a specified separator.
Raw{"answer": "string_agg", "explanation": "string_agg(expression, delimiter) is the PostgreSQL aggregate function that concatenates strings with a specified separator."} | верно | string_agg(значение, разделитель); проверено на PostgreSQL 17.7. |
T15-L6 1.32 c | PostgreSQL | Plain VACUUM returns the space occupied by dead tuples to the operating system. | «no» Пояснение: Plain VACUUM marks dead tuple space as reusable within the table file but does not return it to the operating system; only VACUUM FULL (or VACUUM FULL VERBOSE) shrinks the file and returns space to the OS.
Raw{"answer": "no", "explanation": "Plain VACUUM marks dead tuple space as reusable within the table file but does not return it to the operating system; only VACUUM FULL (or VACUUM FULL VERBOSE) shrinks the file and returns space to the OS."} | верно | VACUUM помечает место для переиспользования внутри таблицы; ОС его возвращает только VACUUM FULL (с эксклюзивной блокировкой). |
T15-L7 0.54 c | PostgreSQL | Which keyword in a window function definition partitions rows into groups the function is computed over? | «partition» Пояснение: The PARTITION BY clause in a window function definition partitions rows into groups over which the function is computed.
Raw{"answer": "PARTITION", "explanation": "The PARTITION BY clause in a window function definition partitions rows into groups over which the function is computed."} | неверно верный: «partition by» | OVER (PARTITION BY ...); проверено на PostgreSQL 17.7. |
T15-L8 1.07 c | PostgreSQL | The READ COMMITTED isolation level protects against non-repeatable reads. | «no» Пояснение: READ COMMITTED only protects against dirty reads; non-repeatable reads are prevented by the REPEATABLE READ isolation level.
Raw{"answer": "no", "explanation": "READ COMMITTED only protects against dirty reads; non-repeatable reads are prevented by the REPEATABLE READ isolation level."} | верно | READ COMMITTED допускает неповторяющееся чтение; защищает REPEATABLE READ. Проверено: SHOW transaction_isolation → read committed. |
T17-L1 0.85 c | PostgreSQL: transactions and indexes | By default, PostgreSQL wraps each single SQL statement in its own implicit transaction (autocommit). | «yes» Пояснение: PostgreSQL operates in autocommit mode by default, meaning each individual SQL statement is wrapped in its own implicit transaction that is automatically committed or rolled back.
Raw{"answer": "yes", "explanation": "PostgreSQL operates in autocommit mode by default, meaning each individual SQL statement is wrapped in its own implicit transaction that is automatically committed or rolled back."} | верно | Без BEGIN каждый оператор коммитится сам; docs PostgreSQL — Transactions. Проверено на PG 17. |
T17-L2 0.43 c | PostgreSQL: transactions and indexes | Which SQL command ends a transaction, committing all its changes? | «commit» Пояснение: The COMMIT SQL command ends a transaction by permanently saving all changes made within it.
Raw{"answer": "COMMIT", "explanation": "The COMMIT SQL command ends a transaction by permanently saving all changes made within it."} | верно | COMMIT (END — синоним). Проверено на PG 17. |
T17-L3 1.08 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 help locate rows quickly for any DML operation (SELECT, UPDATE, DELETE) that uses a WHERE clause on an indexed column, avoiding a full table scan.
Raw{"answer": "yes", "explanation": "Indexes help locate rows quickly for any DML operation (SELECT, UPDATE, DELETE) that uses a WHERE clause on an indexed column, avoiding a full table scan."} | верно | Поиск строк для изменения идёт по индексу; docs PostgreSQL — Indexes. |
T17-L4 0.72 c | PostgreSQL: transactions and indexes | To roll back part of the statements inside a transaction, PostgreSQL uses SAVEPOINT. | «yes» Пояснение: SAVEPOINT allows rolling back to a specific point within a transaction without aborting the entire transaction.
Raw{"answer": "yes", "explanation": "SAVEPOINT allows rolling back to a specific point within a transaction without aborting the entire transaction."} | верно | SAVEPOINT name; ROLLBACK TO name — частичный откат без отмены всей транзакции. Проверено на PG 17. |
T17-L5 0.85 c | PostgreSQL: transactions and indexes | EXPLAIN ANALYZE shows the query plan without executing the query. | «no» Пояснение: EXPLAIN ANALYZE actually executes the query and reports real execution times and row counts, unlike plain EXPLAIN which only shows the plan without running it.
Raw{"answer": "no", "explanation": "EXPLAIN ANALYZE actually executes the query and reports real execution times and row counts, unlike plain EXPLAIN which only shows the plan without running it."} | верно | Наоборот: ANALYZE реально выполняет запрос (с побочными эффектами!) и показывает фактические времена узлов; план без выполнения — plain EXPLAIN. |
T17-L6 0.72 c | PostgreSQL: transactions and indexes | Which PostgreSQL extension adds vector types and indexes for embedding search? | «pgvector» Пояснение: pgvector is a PostgreSQL extension that adds a vector type and vector indexes for efficient similarity search with embeddings.
Raw{"answer": "pgvector", "explanation": "pgvector is a PostgreSQL extension that adds a vector type and vector indexes for efficient similarity search with embeddings."} | верно | CREATE EXTENSION vector (проект pgvector; в проекте образ pgvector/pgvector:pg17). |
T17-L7 1.21 c | PostgreSQL: transactions and indexes | A partial index (CREATE INDEX ... WHERE ...) is built only over rows satisfying the condition. | «yes» Пояснение: A partial index is only built over rows that satisfy the WHERE condition, making it smaller and more efficient for targeted queries.
Raw{"answer": "yes", "explanation": "A partial index is only built over rows that satisfy the WHERE condition, making it smaller and more efficient for targeted queries."} | верно | docs PostgreSQL — Partial Indexes; типичный кейс — индекс по «активным» записям. |
T17-L8 1.74 c | PostgreSQL: transactions and indexes | The SERIALIZABLE level in PostgreSQL is implemented by locking the rows a transaction reads. | «no» Пояснение: PostgreSQL implements SERIALIZABLE using Serializable Snapshot Isolation (SSI), which tracks read/write dependencies and detects conflicts after the fact, rather than locking rows on read.
Raw{"answer": "no", "explanation": "PostgreSQL implements SERIALIZABLE using Serializable Snapshot Isolation (SSI), which tracks read/write dependencies and detects conflicts after the fact, rather than locking rows on read."} | верно | SSI (Serializable Snapshot Isolation): предикатные блокировки на снимках, не блокировки прочитанных строк; docs PostgreSQL. |
T19-L1 0.64 c | HTTP and REST API | HTTP status 201 means the request resulted in a new resource being created. | «yes» Пояснение: HTTP status 201 (Created) indicates that the request was successful and a new resource was created as a result.
Raw{"answer": "yes", "explanation": "HTTP status 201 (Created) indicates that the request was successful and a new resource was created as a result."} | верно | 201 Created; обычно на POST, часто с Location; RFC 9110. |
T19-L2 1.01 c | HTTP and REST API | Which HTTP status means a successful request with an empty response body (e.g. after DELETE)? | «204» Пояснение: HTTP 204 No Content indicates a successful request with an empty response body, commonly returned after DELETE operations.
Raw{"answer": 204, "explanation": "HTTP 204 No Content indicates a successful request with an empty response body, commonly returned after DELETE operations."} | верно | 204 No Content; RFC 9110. |
T19-L3 3.72 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» Пояснение: RFC 7231 explicitly lists DELETE among the idempotent methods: repeating a DELETE for the same resource does not change the outcome beyond the first invocation.
Raw{"answer": "yes", "explanation": "RFC 7231 explicitly lists DELETE among the idempotent methods: repeating a DELETE for the same resource does not change the outcome beyond the first invocation."} | верно | RFC 9110: DELETE идемпотентен (как PUT); идемпотентность ≠ безопасность — ресурс удаляется при первом вызове. |
T19-L4 1.07 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 sent by the server in the response, not by the client; it indicates which origin is allowed to access the resource.
Raw{"answer": "no", "explanation": "The Access-Control-Allow-Origin header is sent by the server in the response, not by the client; it indicates which origin is allowed to access the resource."} | верно | Наоборот: заголовок шлёт СЕРВЕР в ответе, разрешая браузеру cross-origin запрос (CORS); в проекте nelmio/cors-bundle. |
T19-L5 0.98 c | HTTP and REST API | Status 429 Too Many Requests is used when a client exceeds a rate limit. | «yes» Пояснение: HTTP 429 Too Many Requests was defined in RFC 6585 to indicate that a client has sent too many requests in a given amount of time, i.e., rate limiting.
Raw{"answer": "yes", "explanation": "HTTP 429 Too Many Requests was defined in RFC 6585 to indicate that a client has sent too many requests in a given amount of time, i.e., rate limiting."} | верно | 429 (+ Retry-After); RFC 6585. В проекте symfony/rate-limiter. |
T19-L6 0.78 c | HTTP and REST API | 5xx codes mean a client error, while 4xx means a server-side error. | «no» Пояснение: It's the opposite: 4xx codes indicate client errors and 5xx codes indicate server-side errors.
Raw{"answer": "no", "explanation": "It's the opposite: 4xx codes indicate client errors and 5xx codes indicate server-side errors."} | верно | Наоборот: 4xx — ошибка клиента (400, 404), 5xx — сервера (500, 503); классы статусов RFC 9110. |
T19-L7 0.52 c | HTTP and REST API | Which HTTP header indicates the MIME type of the request or response body? | «content-type» Пояснение: The Content-Type HTTP header specifies the MIME type of the request or response body.
Raw{"answer": "Content-Type", "explanation": "The Content-Type HTTP header specifies the MIME type of the request or response body."} | верно | Content-Type: application/json и т.п. |
T19-L8 1.22 c | HTTP and REST API | PATCH is not required to be idempotent per RFC 5789, unlike PUT. | «yes» Пояснение: RFC 5789 explicitly states that PATCH is not idempotent, whereas PUT (defined in RFC 7231) is required to be idempotent.
Raw{"answer": "yes", "explanation": "RFC 5789 explicitly states that PATCH is not idempotent, whereas PUT (defined in RFC 7231) is required to be idempotent."} | верно | RFC 5789 прямо оговаривает: PATCH не гарантированно идемпотентен; PUT идемпотентен. |
T20-L1 1.44 c | Security and OAuth | Checking a password by comparing its hash to the stored hash with a plain == is sufficient. | «no» Пояснение: Using == is vulnerable to timing attacks and type juggling; hash_equals() should be used for constant-time comparison.
Raw{"answer": "no", "explanation": "Using == is vulnerable to timing attacks and type juggling; hash_equals() should be used for constant-time comparison."} | верно | Нужна постоянновременная проверка (password_verify) — timing-атаки; соль и алгоритм уже внутри хеша. |
T20-L2 1.14 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 generated by the server, tied to the session, and verified server-side on state-changing requests like POST, PUT, or DELETE to ensure the request originated from the legitimate user.
Raw{"answer": "yes", "explanation": "CSRF tokens are generated by the server, tied to the session, and verified server-side on state-changing requests like POST, PUT, or DELETE to ensure the request originated from the legitimate user."} | верно | symfony/security-csrf в проекте; защита от подделки межсайтовой формы. |
T20-L3 0.59 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 define the sources that are allowed to be loaded on a webpage, enabling CSP.
Raw{"answer": "Content-Security-Policy", "explanation": "The Content-Security-Policy HTTP header is used to define the sources that are allowed to be loaded on a webpage, enabling CSP."} | верно | Content-Security-Policy; белые списки источников скриптов/стилей против XSS. |
T20-L4 1.11 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 an authorization framework, not an authentication protocol; the access token grants access to resources rather than identifying the user (that's what OpenID Connect's ID token does).
Raw{"answer": "no", "explanation": "OAuth 2.0 is an authorization framework, not an authentication protocol; the access token grants access to resources rather than identifying the user (that's what OpenID Connect's ID token does)."} | верно | OAuth 2.0 — авторизация/делегирование доступа; аутентификацию добавляет OpenID Connect. В проекте knpuniversity/oauth2-client-bundle (yandex/github/google). |
T20-L5 1.81 c | Security and OAuth | XSS is prevented by validating input on the server before writing it to the database. | «no» Пояснение: XSS is primarily prevented by context-aware output encoding when data is sent to the browser, not by input validation before storing in the database.
Raw```json ⏎ {"answer": "no", "explanation": "XSS is primarily prevented by context-aware output encoding when data is sent to the browser, not by input validation before storing in the database."} ⏎ ``` | верно | XSS лечится контекстным экранированием НА ВЫВОДЕ (Twig autoescape, CSP); валидация ввода не покрывает все контексты вывода. |
T20-L6 0.96 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 agent to the redirect_uri with a 'code' parameter, which the client then exchanges for an access token at the token endpoint.
Raw{"answer": "code", "explanation": "In the OAuth 2.0 authorization code flow, the authorization server redirects the user agent to the redirect_uri with a 'code' parameter, which the client then exchanges for an access token at the token endpoint."} | верно | Параметр code; обмен на токен POST-ом на /token с client_secret. |
T20-L7 0.78 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 to outlive access tokens and allow clients to obtain new access tokens without requiring the user to log in again.
Raw{"answer": "yes", "explanation": "Refresh tokens are designed to outlive access tokens and allow clients to obtain new access tokens without requiring the user to log in again."} | верно | Стандартная схема OAuth/OIDC: короткий access + длинный refresh. |
T20-L8 1.6 c | Security and OAuth | A password salt must be kept secret: without it the hash cannot be verified. | «no» Пояснение: A salt does not need to be secret; it is typically stored alongside the hash and is used to recompute the hash during verification — its purpose is to prevent rainbow table attacks, not to add secrecy.
Raw{"answer": "no", "explanation": "A salt does not need to be secret; it is typically stored alongside the hash and is used to recompute the hash during verification — its purpose is to prevent rainbow table attacks, not to add secrecy."} | верно | Соль хранится открыто (password_hash включает её в строку хеша); секретность соли не нужна. |
T18-L1 1.35 c | Testing: PHPUnit | PHPUnit runs test methods of any class — extending TestCase is not required. | «no» Пояснение: PHPUnit requires test classes to extend PHPUnit\Framework\TestCase to be recognized and executed as test classes.
Raw{"answer":"no","explanation":"PHPUnit requires test classes to extend PHPUnit\\Framework\\TestCase to be recognized and executed as test classes."} | верно | Тестом считается метод класса, наследующего TestCase (PHPUnit 10). |
T18-L2 0.73 c | Testing: PHPUnit | In PHPUnit, setUp() runs once before all tests of the class. | «no» Пояснение: setUp() runs before each test method; setUpBeforeClass() (static) runs once before all tests in the class.
Raw{"answer": "no", "explanation": "setUp() runs before each test method; setUpBeforeClass() (static) runs once before all tests in the class."} | верно | setUp() — перед КАЖДЫМ тестом; один раз на класс — setUpBeforeClass(). Проверено живым счётчиком на PHPUnit 10.5. |
T18-L3 1.36 c | Testing: PHPUnit | A data provider lets a test run with exactly one set of arguments. | «no» Пояснение: A data provider is designed to supply multiple sets of arguments so the test runs once for each set, not just one.
Raw{"answer": "no", "explanation": "A data provider is designed to supply multiple sets of arguments so the test runs once for each set, not just one."} | верно | Наоборот: наборов может быть сколько угодно — тест выполняется по разу на каждый. Проверено на PHPUnit 10.5 (#[DataProvider]). |
T18-L4 0.77 c | Testing: PHPUnit | Which PHPUnit method declares an expectation that an exception of a given class is thrown? | «expectexception» Пояснение: PHPUnit's expectException() method declares that a specific exception class is expected to be thrown during the test.
Raw{"answer": "expectException", "explanation": "PHPUnit's expectException() method declares that a specific exception class is expected to be thrown during the test."} | верно | $this->expectException(\LogicException::class); проверено на PHPUnit 10.5. |
T18-L5 1.17 c | Testing: PHPUnit | In PHPUnit, a stub verifies which methods were called on it, while a mock only returns data. | «no» Пояснение: It's the opposite: a stub returns pre-defined data, while a mock verifies that specific methods were called with expected arguments.
Raw{"answer": "no", "explanation": "It's the opposite: a stub returns pre-defined data, while a mock verifies that specific methods were called with expected arguments."} | верно | Наоборот: стаб подставляет данные, мок проверяет взаимодействия (createStub/createMock); docs PHPUnit — Test Doubles. |
T18-L6 0.77 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» Пояснение: In PHPUnit 10+, the #[DataProvider] attribute is the recommended replacement for the deprecated @dataProvider annotation.
Raw{"answer": "yes", "explanation": "In PHPUnit 10+, the #[DataProvider] attribute is the recommended replacement for the deprecated @dataProvider annotation."} | верно | Аннотация ещё парсится в PHPUnit 10/11 (AnnotationParser в 10.5.66), удаление — в 12; атрибут — стандарт. |
T18-L7 0.89 c | Testing: PHPUnit | PHPUnit does not allow one test to depend on the result of another. | «no» Пояснение: PHPUnit provides the @depends annotation (or depends() method) that allows a test to depend on the return value of another test.
Raw{"answer": "no", "explanation": "PHPUnit provides the @depends annotation (or depends() method) that allows a test to depend on the return value of another test."} | верно | Зависимости есть: #[Depends] — зависимый тест не запустится, еслиProducer упал. |
T18-L8 0.73 c | Testing: PHPUnit | Which PHPUnit command-line option makes tests run in random order? | «--random-order» Пояснение: The --random-order PHPUnit CLI option shuffles the order in which tests are executed.
Raw{"answer": "--random-order", "explanation": "The --random-order PHPUnit CLI option shuffles the order in which tests are executed."} | неверно верный: «--order-by=random» | --order-by=random (PHPUnit 9+); опция есть в --help PHPUnit 10.5 (проектная). |
T01-L9 3.85 c | Syntax and operators | What does this code output?
```php
echo intdiv(7, 2) . intdiv(-7, 2);
``` | «3-3» Пояснение: intdiv(7,2) is 3, intdiv(-7,2) is -3 (truncates toward zero), concatenated with dot operator gives '3-3'.
Raw{"answer": "3-3", "explanation": "intdiv(7,2) is 3, intdiv(-7,2) is -3 (truncates toward zero), concatenated with dot operator gives '3-3'."} | верно | intdiv truncates toward zero: intdiv(-7, 2) = -3, not -4. |
T01-L10 0.89 c | Syntax and operators | What does this code output?
```php
echo -3 ** 2;
``` | «-9» Пояснение: In PHP, the exponentiation operator ** has higher precedence than the unary minus, so -3 ** 2 is parsed as -(3 ** 2) = -9.
Raw{"answer": -9, "explanation": "In PHP, the exponentiation operator ** has higher precedence than the unary minus, so -3 ** 2 is parsed as -(3 ** 2) = -9."} | верно | ** is right-associative and binds tighter than unary minus: -(3²). |
T02-L9 1.41 c | Types and comparisons | What does this code output?
```php
echo '1e1' == '10' ? 'true' : 'false';
``` | «true» Пояснение: Both '1e1' and '10' are numeric strings, so PHP compares them as numbers, and 1e1 (scientific notation for 10) equals 10.
Raw{"answer": "true", "explanation": "Both '1e1' and '10' are numeric strings, so PHP compares them as numbers, and 1e1 (scientific notation for 10) equals 10."} | верно | Both strings are numeric — compared as numbers: 10 == 10. |
T02-L10 2.96 c | Types and comparisons | What does this code output?
```php
switch ('a') {
case 0: echo 'zero'; break;
default: echo 'other';
}
``` | «zero» Пояснение: In PHP (prior to 8), switch uses loose comparison (==), and a non-numeric string like 'a' == 0 evaluates to true, so case 0 matches.
Raw{"answer": "zero", "explanation": "In PHP (prior to 8), switch uses loose comparison (==), and a non-numeric string like 'a' == 0 evaluates to true, so case 0 matches."} | неверно верный: «other» | PHP 8: 'a' == 0 → false (used to be true) — default fires. |
T03-L9 2.34 c | Strings | What does this code output?
```php
echo strtr('abc', ['a' => '1', 'ab' => '2']);
``` | «2c» Пояснение: strtr with an array replaces the longest matching key first, so 'ab' is matched and replaced with '2', leaving 'c' unchanged, resulting in '2c'.
Raw{"answer": "2c", "explanation": "strtr with an array replaces the longest matching key first, so 'ab' is matched and replaced with '2', leaving 'c' unchanged, resulting in '2c'."} | верно | strtr with an array prefers the longest matching key. |
T03-L10 1.33 c | Strings | What does this code output?
```php
echo '[' . substr('hello', -10) . ']';
``` | «[]» Пояснение: substr('hello', -10) returns an empty string because the negative start offset (-10) exceeds the string length (5).
Raw```json ⏎ {"answer": "[]", "explanation": "substr('hello', -10) returns an empty string because the negative start offset (-10) exceeds the string length (5)."} ⏎ ``` | неверно верный: «[hello]» | A negative start beyond the string is clamped to the beginning. |
T04-L9 1.53 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,m» Пояснение: The + operator performs array union where the left array takes precedence for duplicate keys, resulting in keys 'k','n','m' in that order.
Raw{"answer":"k,n,m","explanation":"The + operator performs array union where the left array takes precedence for duplicate keys, resulting in keys 'k','n','m' in that order."} | верно | The + operator: on duplicate string keys the left array wins. |
T04-L10 2.12 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));
``` | «yxz» Пояснение: usort sorts by the third element (index 2), so [2,'y',1] comes first, then [1,'x',2] and [3,'z',2] (stable sort); array_column extracts index 1 giving ['y','x','z'], imploded to 'yxz'.
Raw{"answer": "yxz", "explanation": "usort sorts by the third element (index 2), so [2,'y',1] comes first, then [1,'x',2] and [3,'z',2] (stable sort); array_column extracts index 1 giving ['y','x','z'], imploded to 'yxz'."} | верно | Sorts are stable since 8.0: x and z keep their order on a tie. |
T05-L10 4.39 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 an associative array uses the keys as named arguments, so a=5 and b=1, giving 5-1=4.
Raw{"answer": 4, "explanation": "The spread operator with an associative array uses the keys as named arguments, so a=5 and b=1, giving 5-1=4."} | верно | String keys of a spread array become named arguments. |
T05-L9 2.09 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 first-class callable syntax ($p->g(...)) creates a Closure bound to the object instance; even after $p is set to null, the Closure holds a reference to the object, so it remains alive and $this->v is still 3.
Raw{"answer": 3, "explanation": "The first-class callable syntax ($p->g(...)) creates a Closure bound to the object instance; even after $p is set to null, the Closure holds a reference to the object, so it remains alive and $this->v is still 3."} | верно | First-class callable syntax binds $this at creation time. |
T06-L9 1.2 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 performs late static binding and returns the actual class of the instance (B), not the class where the method is defined.
Raw{"answer": "B", "explanation": "static::class performs late static binding and returns the actual class of the instance (B), not the class where the method is defined."} | верно | Late static binding: static::class is the receiver's class. |
T06-L10 2.19 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» Пояснение: The set accessor doubles the value (5 * 2 = 10), and since accessors don't trigger on internal property access, the stored value is 10.
Raw{"answer": 10, "explanation": "The set accessor doubles the value (5 * 2 = 10), and since accessors don't trigger on internal property access, the stored value is 10."} | верно | Inside the set hook, $this->x writes the backing store (no recursion): 5*2. |
T07-L9 1.32 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» Пояснение: TB::f insteadof TA makes f() return 'B', and TA::f as g aliases it to g() returning 'A', so the concatenation is 'BA'.
Raw```json ⏎ {"answer": "BA", "explanation": "TB::f insteadof TA makes f() return 'B', and TA::f as g aliases it to g() returning 'A', so the concatenation is 'BA'."} ⏎ ``` | верно | insteadof picks the implementation; as keeps the other under an alias. |
T07-L10 1.42 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;
``` | «0» Пояснение: Each class that uses a trait gets its own independent copy of the trait's static properties, so setting CX::$n does not affect CY::$n.
Raw{"answer": 0, "explanation": "Each class that uses a trait gets its own independent copy of the trait's static properties, so setting CX::$n does not affect CY::$n."} | верно | A trait's static property is copied into each consuming class. |
T08-L10 0.88 c | Exceptions and errors | What does this code output?
```php
function f(): int
{
try { return 1; } finally { return 2; }
}
echo f();
``` | «2» Пояснение: In PHP, a return statement in a finally block overrides the return value from the try block, so the function returns 2.
Raw{"answer": 2, "explanation": "In PHP, a return statement in a finally block overrides the return value from the try block, so the function returns 2."} | верно | A return in finally overrides the return from try. |
T08-L9 1.26 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 finally block throws a LogicException, which replaces the in-flight RuntimeException, and the outer catch catches the LogicException.
Raw{"answer": "second", "explanation": "The finally block throws a LogicException, which replaces the in-flight RuntimeException, and the outer catch catches the LogicException."} | верно | An exception from finally replaces the in-flight one — the last thrown is caught. |
T09-L9 1.66 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» Пояснение: Baz::class resolves to App\Foo (the aliased class via use), while \Baz::class refers to the global class Baz, returning the string 'Baz'.
Raw{"answer": "App\\Foo|Baz", "explanation": "Baz::class resolves to App\\Foo (the aliased class via use), while \\Baz::class refers to the global class Baz, returning the string 'Baz'."} | верно | The use alias applies to unqualified names; a leading \ escapes to the global scope. |
T09-L10 1.46 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');
``` | «noyes» Пояснение: class_exists('Foo') looks in the global namespace where Foo doesn't exist (it's in Ns), returning 'no'; class_exists('Ns\Foo') finds the class, returning 'yes'.
Raw{"answer": "noyes", "explanation": "class_exists('Foo') looks in the global namespace where Foo doesn't exist (it's in Ns), returning 'no'; class_exists('Ns\\Foo') finds the class, returning 'yes'."} | верно | Dynamic names are not resolved against the namespace — 'Foo' is the global class. |
T10-L9 1.28 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» Пояснение: After foreach by reference, $v still holds a reference to the last element ($a[2]), so assigning $v = 99 changes $a[2] to 99.
Raw{"answer": "1,2,99", "explanation": "After foreach by reference, $v still holds a reference to the last element ($a[2]), so assigning $v = 99 changes $a[2] to 99."} | верно | After a by-ref foreach, $v remains a reference to the last element. |
T10-L10 2.43 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» Пояснение: Static variables in methods are shared across all instances of the same class (and inherited subclasses share the same static), so each call increments the shared $n: 1, 2, 3.
Raw{"answer": 3, "explanation": "Static variables in methods are shared across all instances of the same class (and inherited subclasses share the same static), so each call increments the shared $n: 1, 2, 3."} | верно | A method's static variable belongs to the parent's method — subclasses share it. |
T11-L9 3.99 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();
``` | «—» Пояснение: The generator is paused at the first yield (yield 1) after send(10), so it hasn't completed and getReturn() returns null, which echo outputs as an empty string.
Raw```json ⏎ {"answer": "", "explanation": "The generator is paused at the first yield (yield 1) after send(10), so it hasn't completed and getReturn() returns null, which echo outputs as an empty string."} ⏎ ``` | неверно верный: «11» | send() resumes the generator: $x = 10, return 10+1. |
T11-L10 1.66 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,ok» Пояснение: yield from delegates to inner() which yields 1 and 2, then its return value 'ok' is captured in $r and yielded by outer(), producing the sequence 1,2,ok.
Raw```json ⏎ {"answer": "1,2,ok", "explanation": "yield from delegates to inner() which yields 1 and 2, then its return value 'ok' is captured in $r and yielded by outer(), producing the sequence 1,2,ok."} ⏎ ``` | неверно верный: «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 1.71 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';
``` | «noyes» Пояснение: The hash was created with cost 4, so password_needs_rehash returns false (no) when checking against cost 4, and true (yes) when checking against cost 5.
Raw{"answer": "noyes", "explanation": "The hash was created with cost 4, so password_needs_rehash returns false (no) when checking against cost 4, and true (yes) when checking against cost 5."} | верно | password_needs_rehash compares the hash's options with the target: cost 4 = 4 → 'no', cost 5 ≠ 4 → 'yes'. |
T12-L10 4.79 c | Configuration and security | What does this code output on PHP 8.5?
```php
echo (E_ALL & 2048) === 0 ? 'strict-out' : 'strict-in';
``` | «strict-in» Пояснение: E_ALL includes E_STRICT (2048), so E_ALL & 2048 equals 2048 (not 0), making the condition false and selecting 'strict-in'.
Raw```json ⏎ {"answer": "strict-in", "explanation": "E_ALL includes E_STRICT (2048), so E_ALL & 2048 equals 2048 (not 0), making the condition false and selecting 'strict-in'."} ⏎ ``` | неверно верный: «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 6.53 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's HeaderBag strips the HTTP_ prefix and normalizes keys (underscores/hyphens, case), so HTTP_X_TOKEN is stored as X_TOKEN and retrieved correctly via get('X-Token').
Raw```json ⏎ {"answer": "mapped", "explanation": "Symfony's HeaderBag strips the HTTP_ prefix and normalizes keys (underscores/hyphens, case), so HTTP_X_TOKEN is stored as X_TOKEN and retrieved correctly via get('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 1.36 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;
``` | «bca» Пояснение: Symfony EventDispatcher calls listeners in descending priority order (highest first): B(10), C(5), A(0 default).
Raw```json ⏎ {"answer": "BCA", "explanation": "Symfony EventDispatcher calls listeners in descending priority order (highest first): B(10), C(5), A(0 default)."} ⏎ ``` | верно | Listeners run by descending priority: 10 (B), 5 (C), 0 (A). |
T14-L10 2.17 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's identity map ensures that find() returns the same object instance for the same entity ID, so both $a and $b reference the same object.
Raw```json ⏎ {"answer": "same", "explanation": "Doctrine ORM's identity map ensures that find() returns the same object instance for the same entity ID, so both $a and $b reference the same object."} ⏎ ``` | верно | Identity map: a second find for the same id returns the same instance. |
T14-L9 7.26 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» Пояснение: Persisting then removing a new (unflushed) entity simply cancels the pending INSERT; Doctrine removes it from the newEntities collection without ever issuing a SQL statement, so the table remains empty.
Raw```json ⏎ {"answer": 0, "explanation": "Persisting then removing a new (unflushed) entity simply cancels the pending INSERT; Doctrine removes it from the newEntities collection without ever issuing a SQL statement, so the table remains empty."} ⏎ ``` | верно | The unit of work schedules INSERT at flush: remove after persist cancels it. |
T15-L10 1.01 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» Пояснение: COUNT(x) counts only non-NULL values in column x; since one row has NULL, the result is 1.
Raw{"answer": 1, "explanation": "COUNT(x) counts only non-NULL values in column x; since one row has NULL, the result is 1."} | верно | count(column) skips NULLs; count(*) would return 2. |
T15-L9 1.61 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 sum(x) OVER (ORDER BY id) produces running sums 10, 30, 60, which string_agg concatenates with commas into '10,30,60'.
Raw{"answer": "10,30,60", "explanation": "The window function sum(x) OVER (ORDER BY id) produces running sums 10, 30, 60, which string_agg concatenates with commas into '10,30,60'."} | верно | With ORDER BY the default window frame is running (start to current row). |
T16-L9 5.01 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 first middleware echoes 'M1' then delegates to the next, which echoes 'M2' then tries to call next() again (throwing a LogicException after the output).
Raw{"answer": "M1M2", "explanation": "The first middleware echoes 'M1' then delegates to the next, which echoes 'M2' then tries to call next() again (throwing a LogicException after the output)."} | верно | The first-added middleware runs first (outermost). |
T16-L10 2.04 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» Пояснение: HandleMessageMiddleware calls all handlers registered for the message class sequentially, so both closures execute: $n += 1 then $n += 10, resulting in 11.
Raw```json ⏎ {"answer": 11, "explanation": "HandleMessageMiddleware calls all handlers registered for the message class sequentially, so both closures execute: $n += 1 then $n += 10, resulting in 11."} ⏎ ``` | верно | All registered handlers of the message run: 1 + 10 = 11. |
T17-L9 1.22 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» Пояснение: The first INSERT succeeds, the second is skipped due to the unique constraint (ON CONFLICT DO NOTHING), so count(*) is 1.
Raw{"answer": 1, "explanation": "The first INSERT succeeds, the second is skipped due to the unique constraint (ON CONFLICT DO NOTHING), so count(*) is 1."} | верно | ON CONFLICT DO NOTHING skips the duplicate: one insert. |
T17-L10 1.35 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» Пояснение: The UNIQUE constraint is DEFERRABLE INITIALLY DEFERRED, so it is only checked at COMMIT time, meaning both INSERTs succeed and count(*) returns 2.
Raw{"answer": 2, "explanation": "The UNIQUE constraint is DEFERRABLE INITIALLY DEFERRED, so it is only checked at COMMIT time, meaning both INSERTs succeed and count(*) returns 2."} | верно | DEFERRED postpones the uniqueness check to COMMIT — count sees 2 rows. |
T18-L9 1.35 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 (since filter does substring matching), each with 3 data sets from the provider, giving 3+3=6 tests.
Raw{"answer": 6, "explanation": "The --filter test_sum matches both test_sum and test_sum_abs (since filter does substring matching), each with 3 data sets from the provider, giving 3+3=6 tests."} | верно | --filter is a substring match: test_sum also matches test_sum_abs (3+3 datasets). |
T18-L10 1.31 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 data provider supplies two datasets ([1] and [-1]), so test_x runs twice; the first assertion (1>0) passes and the second (-1>0) fails.
Raw{"answer":"2, 1","explanation":"The data provider supplies two datasets ([1] and [-1]), so test_x runs twice; the first assertion (1>0) passes and the second (-1>0) fails."} | верно | 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.77 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 request body, which causes curl to use the POST method by default.
Raw{"answer": "POST", "explanation": "The -d flag in curl sends data in the request body, which causes curl to use the POST method by default."} | верно | -d/-F switches curl to POST by default. |
T19-L10 0.94 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 the GET method and append -d data as a query string.
Raw{"answer": "GET", "explanation": "The -G flag tells curl to use the GET method and append -d data as a query string."} | верно | -G turns -d data into the query string; the method stays GET. |
T20-L9 1.75 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» Пояснение: RFC 6749 Section 5.2 defines 'invalid_client' as the error returned when the client authentication failed, such as when the client was unknown to the authorization server.
Raw{"answer": "invalid_client", "explanation": "RFC 6749 Section 5.2 defines 'invalid_client' as the error returned when the client authentication failed, such as when the client was unknown to the authorization server."} | верно | Unknown client → invalid_client (RFC 6749 §5.2). |
T20-L10 1.09 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 OAuth 2.0 implicit flow (response_type=token), the access token is returned in the fragment portion of the redirect_uri (after the # character), not in the query string.
Raw{"answer": "fragment", "explanation": "In the OAuth 2.0 implicit flow (response_type=token), the access token is returned in the fragment portion of the redirect_uri (after the # character), not in the query string."} | верно | The implicit flow passes the token in the URL fragment (#) — it never reaches the server. |
T21-L9 1.37 c | Twig | What does this Twig template output?
```twig
{{ false|default(2) * 3 }}
``` | «0» Пояснение: The 'default' filter only returns the fallback when the value is null or undefined; since false is a defined non-null value, it passes through as-is, and false * 3 equals 0.
Raw```json ⏎ {"answer": 0, "explanation": "The 'default' filter only returns the fallback when the value is null or undefined; since false is a defined non-null value, it passes through as-is, and false * 3 equals 0."} ⏎ ``` | неверно верный: «6» | default replaces exactly false/null/''/[] — false becomes 2, 2*3 = 6; the naive 'default is for undefined only' yields 0. |
T21-L10 12.21 c | Twig | What exception class does render() of this template throw?
```twig
{{ 'a' ~ 1 + 2 }}
``` | «a3» Пояснение: In Twig, the + operator has higher precedence than ~, so the expression is evaluated as 'a' ~ (1+2) = 'a' ~ 3 = 'a3'.
Raw```json ⏎ {"answer": "a3", "explanation": "In Twig, the + operator has higher precedence than ~, so the expression is evaluated as 'a' ~ (1+2) = 'a' ~ 3 = 'a3'."} ⏎ ``` | неверно верный: «runtimeerror» | In Twig ~ binds tighter than +: ('a' ~ 1) + 2 → string + int → a render error (RuntimeError). |
T22-L9 2.48 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()]));
``` | «0» Пояснение: Assert\NotBlank on an array checks if the array is non-empty; [''] has one element so it passes, resulting in 0 violations.
Raw{"answer": 0, "explanation": "Assert\\NotBlank on an array checks if the array is non-empty; [''] has one element so it passes, resulting in 0 violations."} | верно | NotBlank treats null, '', [] as blank — the array [''] is not blank. |
T22-L10 4.61 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» Пояснение: When a Symfony form has not been submitted, isSynchronized() returns false, so isValid() returns false via short-circuit evaluation, outputting 'invalid'.
Raw{"answer": "invalid", "explanation": "When a Symfony form has not been submitted, isSynchronized() returns false, so isValid() returns false via short-circuit evaluation, outputting 'invalid'."} | неверно верный: «symfony\component\form\exception\logicexception» | isValid() on a non-submitted form throws LogicException, it does not return false. |
T23-L9 2.42 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» Пояснение: Services in Symfony's DI container are shared (singleton) by default, so both calls to get('a') return the same object instance.
Raw```json ⏎ {"answer": "same", "explanation": "Services in Symfony's DI container are shared (singleton) by default, so both calls to get('a') return the same object instance."} ⏎ ``` | верно | Container services are shared: two get() calls yield one instance. |
T23-L10 1.84 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!» Пояснение: During compile(), Symfony recursively resolves parameter references: %greeting% is replaced with 'hi %name%', then %name% is replaced with 'Bob', yielding 'hi Bob!'.
Raw```json ⏎ {"answer": "hi Bob!", "explanation": "During compile(), Symfony recursively resolves parameter references: %greeting% is replaced with 'hi %name%', then %name% is replaced with 'Bob', yielding 'hi Bob!'."} ⏎ ``` | верно | compile() resolves %-references transitively: %greeting% → 'hi %name%' → 'hi Bob!', the answer assembles over two hops. |
T24-L9 1.26 c | Bootstrap | What is the max-width of .container in Bootstrap 5.3 at a 992px viewport? | «960» Пояснение: At 992px viewport, the lg breakpoint (≥992px) applies, giving .container a max-width of 960px in Bootstrap 5.3.
Raw{"answer": 960, "explanation": "At 992px viewport, the lg breakpoint (≥992px) applies, giving .container a max-width of 960px in Bootstrap 5.3."} | верно | 5.x container widths: 540/720/960/1140/1320 (sm–xxl); 992 → 960px. |
T24-L10 1.67 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-danger» Пояснение: In Bootstrap 5.3's CSS, text-danger is declared after text-primary with equal specificity, so it wins by source order in the cascade.
Raw```json ⏎ {"answer": "text-danger", "explanation": "In Bootstrap 5.3's CSS, text-danger is declared after text-primary with equal specificity, so it wins by source order in the cascade."} ⏎ ``` | верно | Specificity ties — the later rule wins: text-danger is declared after text-primary. |
T25-L9 1.28 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 Domain class depends on Application (PlaceOrder) and Infrastructure (Db), both of which violate the rule that Domain may only depend on Domain.
Raw```json ⏎ {"answer": 2, "explanation": "The Domain class depends on Application (PlaceOrder) and Infrastructure (Db), both of which violate the rule that Domain may only depend on Domain."} ⏎ ``` | верно | Domain may depend only on Domain: PlaceOrder (Application) + Db (Infrastructure) = 2. |
T25-L10 1.28 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,
) {}
}
``` | «3» Пояснение: The Domain class depends on two Infrastructure classes (Db, Logger) and one Application class (PlaceOrder), all violating the rule that Domain may only depend on Domain.
Raw{"answer": 3, "explanation": "The Domain class depends on two Infrastructure classes (Db, Logger) and one Application class (PlaceOrder), all violating the rule that Domain may only depend on Domain."} | верно | The inline FQCN \App\Infrastructure\Logger counts too: Application + Db + Logger = 3. |
T26-L10 1.33 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» Пояснение: $a has amount 10, and $c is a new Money object with 10+5=15, so echoing both gives '10,15'.
Raw{"answer":"10,15","explanation":"$a has amount 10, and $c is a new Money object with 10+5=15, so echoing both gives '10,15'."} | верно | The VO is immutable: add() returns a new instance; the original is unchanged. |
T26-L9 1.67 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 exception is thrown before unset() is reached, so the item remains in the array and count() still returns 1.
Raw{"answer": 1, "explanation": "The exception is thrown before unset() is reached, so the item remains in the array and count() still returns 1."} | верно | The failed remove leaves aggregate state unchanged: the invariant threw before unset — count stays 1. |
VC-L9 3.72 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 instantiates class C, calls the hi() method which returns the string 'hi', and echoes it.
Raw{"answer": "hi", "explanation": "The code instantiates class C, calls the hi() method which returns the string 'hi', and echoes it."} | верно | Since 8.4, new in a method chain works without wrapping parentheses. |
VC-L10 4.86 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';
``` | «yesno» Пояснение: newLazyGhost creates an uninitialized lazy object (isUninitializedLazyObject returns true), then accessing $o->v triggers initialization via the callback, after which it's no longer uninitialized (returns false).
Raw```json ⏎ {"answer": "yesno", "explanation": "newLazyGhost creates an uninitialized lazy object (isUninitializedLazyObject returns true), then accessing $o->v triggers initialization via the callback, after which it's no longer uninitialized (returns false)."} ⏎ ``` | верно | newLazyGhost (8.4): the object stays lazy until first access — reading a property initializes it and clears the flag. |
T28-L9 1.69 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» Пояснение: The Security Guard component was removed in Symfony 6.0, so AbstractGuardAuthenticator no longer exists in Symfony 8.1.
Raw{"answer": "no", "explanation": "The Security Guard component was removed in Symfony 6.0, so AbstractGuardAuthenticator no longer exists in Symfony 8.1."} | верно | Guard authentication was removed in Symfony 7.0 — the class is gone in 8.1. |
T28-L10 6.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\Routing\Loader\AnnotationClassLoader::class)
? 'yes' : 'no';
echo class_exists(\Symfony\Component\Routing\Loader\AttributeClassLoader::class)
? 'yes' : 'no';
``` | «nono» Пояснение: In Symfony 8.1, AnnotationClassLoader was removed (deprecated in 7.0), and the replacement class is named AttributeLoader (not AttributeClassLoader), so both class_exists checks return false.
Raw```json ⏎ {"answer": "nono", "explanation": "In Symfony 8.1, AnnotationClassLoader was removed (deprecated in 7.0), and the replacement class is named AttributeLoader (not AttributeClassLoader), so both class_exists checks return false."} ⏎ ``` | неверно верный: «noyes» | Annotation loaders were removed in 7.0; only attribute loaders remain (Annotation→Attribute). |