Пример запроса (первая клетка). System одинаковый во всех запросах прогона, user — свой вопрос для каждой клетки:
| Клетка | Тема | Утверждение | Ответ |
Результат | Обоснование |
T01-L1 3.93 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 (\n, \t, etc.), while single-quoted strings only recognize \\ and \', so they are processed differently, not just at different speeds.
Raw```json ⏎ {"answer": "no", "explanation": "Double-quoted strings support variable interpolation and more escape sequences (\\n, \\t, etc.), while single-quoted strings only recognize \\\\ and \\', so they are processed differently, not just at different speeds."} ⏎ ``` | верно | В двойных кавычках работают интерполяция переменных и escape-последовательности, в одинарных — нет. |
T01-L2 1.21 c | Syntax and operators | The ?? operator follows isset semantics and raises no warnings for undefined variables. | «yes» Пояснение: The ?? (null coalescing) operator is equivalent to isset($var) ? $var : default, so it safely handles undefined variables without raising warnings.
Raw{"answer": "yes", "explanation": "The ?? (null coalescing) operator is equivalent to isset($var) ? $var : default, so it safely handles undefined variables without raising warnings."} | верно | ?? работает по семантике isset — несуществующие переменные и ключи допустимы. |
T01-L3 0.66 c | Syntax and operators | What will this print: echo 'a', 'b'; | «ab» Пояснение: PHP's echo statement accepts multiple comma-separated arguments and outputs them concatenated together without any separator.
Raw{"answer": "ab", "explanation": "PHP's echo statement accepts multiple comma-separated arguments and outputs them concatenated together without any separator."} | верно | echo принимает список аргументов: ab. |
T01-L4 1.42 c | Syntax and operators | print returns the value 1 and can be used inside an expression. | «yes» Пояснение: In PHP, print is a language construct that outputs a string and always returns the integer 1, so it can be used within expressions.
Raw{"answer": "yes", "explanation": "In PHP, print is a language construct that outputs a string and always returns the integer 1, so it can be used within expressions."} | верно | print — выражение со значением 1, в отличие от echo, который значения не возвращает. |
T01-L5 1.07 c | Syntax and operators | The ?: (elvis) operator returns its left operand when it is falsy. | «no» Пояснение: The Elvis operator returns its left operand when it is truthy, and its right operand when it is falsy.
Raw{"answer": "no", "explanation": "The Elvis operator returns its left operand when it is truthy, and its right operand when it is falsy."} | верно | Наоборот: $a ?: $b возвращает $a, если он истинный, иначе $b. |
T01-L6 2.13 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; they are all at the same level in the precedence table.
Raw{"answer": "no", "explanation": "In PHP, the concatenation operator (.) has the same precedence as addition and subtraction; they are all at the same level in the precedence table."} | неверно верный: «yes» | С PHP 8 (RFC concat precedence) '.' имеет приоритет ниже арифметики: 'сумма: ' . 2 + 3 → 'сумма: 5' (в PHP 7 было иначе). |
T01-L7 0.94 c | Syntax and operators | The expression 2 ** 3 ** 2 in PHP evaluates as (2 ** 3) ** 2, that is, 64. | «no» Пояснение: In PHP, the ** operator is right-associative, so 2 ** 3 ** 2 evaluates as 2 ** (3 ** 2) = 2 ** 9 = 512, not 64.
Raw{"answer":"no","explanation":"In PHP, the ** operator 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.27 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's evaluated as 'sum: ' . (2 + 3) = 'sum: 5'.
Raw{"answer": "sum: 5", "explanation": "The + operator has higher precedence than the . (concatenation) operator, so it's evaluated as 'sum: ' . (2 + 3) = 'sum: 5'."} | верно | Парная к verify-клетке про приоритет: 'сумма: 5'. |
T02-L1 1.1 c | Types and comparisons | With strict comparison (===), arrays are considered equal regardless of element order. | «no» Пояснение: With ===, arrays must have the same key/value pairs in the same order to be considered equal.
Raw{"answer": "no", "explanation": "With ===, arrays must have the same key/value pairs in the same order to be considered equal."} | верно | === для массивов требует совпадения и значений, и их порядка. |
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 (non-strict) comparison and actually returns true, since false is cast to 0.
Raw{"answer":"no","explanation":"0 == false uses a loose (non-strict) comparison and actually returns true, since false is cast to 0."} | верно | Наоборот: == — нестрогое сравнение и возвращает true; строгое — это === (0 === false → false). |
T02-L3 1.24 c | Types and comparisons | In PHP 8, the expression "abc" == 0 returns true. | «no» Пояснение: In PHP 8, comparing a non-numeric string to an integer casts the integer to a string, so 'abc' == 0 becomes 'abc' == '0', which is false.
Raw{"answer": "no", "explanation": "In PHP 8, comparing a non-numeric string to an integer casts the integer to a string, so 'abc' == 0 becomes 'abc' == '0', which is false."} | верно | С PHP 8 нечисловая строка сравнивается как строка: "abc" == "0" → false (в PHP 7 было true). |
T02-L4 1.77 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.94 c | Types and comparisons | What does the expression (int) '42abc' return? | «42» Пояснение: PHP's (int) cast parses the leading numeric portion of a string and ignores the trailing non-numeric characters, so '42abc' becomes 42.
Raw{"answer": 42, "explanation": "PHP's (int) cast parses the leading numeric portion of a string and ignores the trailing non-numeric characters, so '42abc' becomes 42."} | верно | Ведущая числовая часть: 42, без ошибок и warning. |
T02-L6 0.64 c | Types and comparisons | What does the expression '5' + 5 return? | «10» Пояснение: PHP coerces the string '5' to the integer 5, then performs numeric addition: 5 + 5 = 10.
Raw{"answer": 10, "explanation": "PHP coerces the string '5' to the integer 5, then performs numeric addition: 5 + 5 = 10."} | верно | Числовая строка приводится: int 10. |
T02-L7 0.89 c | Types and comparisons | When cast to string, false becomes "0". | «no» Пояснение: In PHP, casting false to a string results in an empty string "", not "0".
Raw{"answer": "no", "explanation": "In PHP, casting false to a string results in an empty string \"\", not \"0\"."} | верно | false → "", true → "1". |
T02-L8 1.24 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 identical to 0.3, so === returns false.
Raw{"answer":"yes","explanation":"Due to floating-point precision, 0.1 + 0.2 equals 0.30000000000000004, which is not identical to 0.3, so === returns false."} | верно | Двоичная погрешность float: 0.1 + 0.2 = 0.30000000000000004. |
T03-L1 1.2 c | Strings | strrev() correctly reverses a UTF-8 string. | «no» Пояснение: strrev() operates at the byte level, so it reverses individual bytes rather than multi-byte UTF-8 characters, producing a garbled result.
Raw{"answer":"no","explanation":"strrev() operates at the byte level, so it reverses individual bytes rather than multi-byte UTF-8 characters, producing a garbled result."} | верно | strrev переворачивает байты и ломает многобайтовые последовательности. |
T03-L2 0.92 c | Strings | str_contains('Hello world', 'world') returns true. | «yes» Пояснение: str_contains('Hello world', 'world') does return true because 'world' is a substring of 'Hello world'.
Raw{"answer": "yes", "explanation": "str_contains('Hello world', 'world') does return true because 'world' is a substring of 'Hello 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() supports STR_PAD_RIGHT, STR_PAD_LEFT, and STR_PAD_BOTH as the pad_type parameter.
Raw{"answer": "no", "explanation": "str_pad() supports STR_PAD_RIGHT, STR_PAD_LEFT, and STR_PAD_BOTH as the pad_type parameter."} | верно | STR_PAD_LEFT / STR_PAD_BOTH меняют сторону дополнения. |
T03-L4 1.1 c | Strings | By default trim() strips only spaces, leaving tabs and newlines intact. | «no» Пояснение: By default, trim() strips spaces, tabs, newlines, carriage returns, null bytes, and vertical tabs — not just spaces.
Raw{"answer": "no", "explanation": "By default, trim() strips spaces, tabs, newlines, carriage returns, null bytes, and vertical tabs — not just spaces."} | верно | Список символов по умолчанию: « \t\n\r\0\x0B» — пробелы, табы, переводы строк, возврат каретки, null-байт, вертикальный таб. Проверено php -r. |
T03-L5 1.19 c | Strings | How many BYTES does strlen('héllo') return for a UTF-8 string? | «6» Пояснение: strlen() counts bytes; 'é' is 2 bytes in UTF-8, so 'h' + 'é' + 'l' + 'l' + 'o' = 1+2+1+1+1 = 6 bytes.
Raw{"answer": 6, "explanation": "strlen() counts bytes; 'é' is 2 bytes in UTF-8, so 'h' + 'é' + 'l' + 'l' + 'o' = 1+2+1+1+1 = 6 bytes."} | верно | 6 букв по 2 байта: 12. |
T03-L6 0.85 c | Strings | What does substr('abcdef', -3) return? | «def» Пояснение: substr with a negative offset counts from the end of the string, so -3 returns the last 3 characters 'def'.
Raw{"answer": "def", "explanation": "substr with a negative offset counts from the end of the string, so -3 returns the last 3 characters 'def'."} | верно | Отрицательное смещение — с конца: def. |
T03-L7 0.95 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.18 c | Strings | Variable interpolation works in heredoc but not in nowdoc. | «yes» Пояснение: Heredoc supports variable interpolation like double-quoted strings, while nowdoc (identifier in single quotes) treats content as a plain string with no interpolation.
Raw{"answer": "yes", "explanation": "Heredoc supports variable interpolation like double-quoted strings, while nowdoc (identifier in single quotes) treats content as a plain string with no interpolation."} | верно | Nowdoc — «одинарные кавычки» в тройном синтаксисе: текст как есть. |
T04-L1 0.91 c | Arrays | The sort() function preserves the key-to-value association of the array. | «no» Пояснение: The sort() function re-indexes the array numerically and does not preserve key-to-value associations; use asort() for that.
Raw{"answer": "no", "explanation": "The sort() function re-indexes the array numerically and does not preserve key-to-value associations; use asort() for that."} | верно | sort перенумеровывает ключи; связь сохраняет asort. |
T04-L2 0.82 c | Arrays | The string key '5' in an array is stored as the integer 5. | «yes» Пояснение: PHP automatically converts string keys that represent valid integers (like '5') to their integer equivalent (5) when used as array keys.
Raw{"answer": "yes", "explanation": "PHP automatically converts string keys that represent valid integers (like '5') to their integer equivalent (5) when used as array keys."} | верно | Каноничные десятичные строковые ключи приводятся к int. |
T04-L3 0.83 c | Arrays | The in_array() function uses strict comparison (===) by default. | «no» Пояснение: in_array() uses loose comparison (==) by default; the third parameter must be set to true to enable strict comparison (===).
Raw{"answer": "no", "explanation": "in_array() uses loose comparison (==) by default; the third parameter must be set to true to enable strict comparison (===)."} | верно | По умолчанию сравнение нестрогое; строгое — третий аргумент true. |
T04-L4 0.87 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 (0, '0', '', null, false, [], 0.0).
Raw{"answer": "yes", "explanation": "Without a callback, array_filter() removes all elements that evaluate to falsy (0, '0', '', null, false, [], 0.0)."} | верно | Убирает 0, "", null, false и пустые массивы. |
T04-L5 1.08 c | Arrays | By default, array_slice() preserves the original numeric keys of the array. | «no» Пояснение: The preserve_keys parameter of array_slice() defaults to false, so keys are reindexed by default.
Raw{"answer": "no", "explanation": "The preserve_keys parameter of array_slice() defaults to false, so keys are reindexed by default."} | верно | По умолчанию ключи перенумеровываются; сохранение — preserve_keys = true. |
T04-L6 1.25 c | Arrays | What does array_slice([10, 20, 30, 40], 1, 2) return? | «[20, 30]» Пояснение: array_slice extracts 2 elements starting at offset 1, giving the sub-array [20, 30].
Raw{"answer": "[20, 30]", "explanation": "array_slice extracts 2 elements starting at offset 1, giving the sub-array [20, 30]."} | верно | [20,30]; ключи перенумеровываются. |
T04-L7 1.46 c | Arrays | How many elements will count(['a' => 1] + ['a' => 9, 'b' => 2]) return? | «2» Пояснение: The array union (+) keeps the left value for duplicate keys ('a' => 1) and appends new keys from the right ('b' => 2), resulting in 2 elements.
Raw{"answer": 2, "explanation": "The array union (+) keeps the left value for duplicate keys ('a' => 1) and appends new keys from the right ('b' => 2), resulting in 2 elements."} | верно | Оператор + : по ключу 'a' побеждает левый; итого 2. |
T04-L8 1.23 c | Arrays | Since PHP 8.1, the spread operator [...$a, ...$b] supports arrays with string keys. | «yes» Пояснение: PHP 8.1 extended the array spread operator to support arrays with string keys, which previously (since 7.4) only worked with integer-keyed arrays.
Raw{"answer": "yes", "explanation": "PHP 8.1 extended the array spread operator to support arrays with string keys, which previously (since 7.4) only worked with integer-keyed arrays."} | верно | В 8.0 — только числовые ключи; 8.1 снял ограничение. |
T05-L1 2.29 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 argument unpacking in a single call, as long as the named arguments appear before the ...$args unpacking (e.g., func(name: value, ...$args)).
Raw{"answer": "no", "explanation": "In PHP 8.0+, named arguments can be combined with argument unpacking in a single call, as long as the named arguments appear before the ...$args unpacking (e.g., func(name: value, ...$args))."} | верно | Можно: f(...$args, имя: значение). Нельзя только позиционный аргумент после распаковки. |
T05-L2 1.36 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 via 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 via the 'use' keyword."} | верно | Без use внешние переменные недоступны; авто-захват только у fn. |
T05-L3 0.87 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, regardless of the declared parameter count.
Raw{"answer": 3, "explanation": "func_num_args() returns the number of arguments actually passed to the function, which is 3 in this case, regardless of the declared parameter count."} | верно | Считает переданные аргументы: 3. |
T05-L4 1.36 c | Functions and closures | The body of an arrow function fn may consist of several expressions in curly braces. | «no» Пояснение: An arrow function (fn) in PHP has exactly a single expression as its body (e.g., fn($x) => $x * 2), not multiple expressions in curly braces.
Raw{"answer": "no", "explanation": "An arrow function (fn) in PHP has exactly a single expression as its body (e.g., fn($x) => $x * 2), not multiple expressions in curly braces."} | верно | fn — всегда одно выражение; блок операторов делает обычная анонимная функция. |
T05-L5 1.59 c | Functions and closures | An arrow function fn captures outer variables by reference (lazily, at use time). | «no» Пояснение: Arrow functions (fn) in PHP capture outer variables by value (eagerly at definition time), not by reference or lazily at use time.
Raw{"answer": "no", "explanation": "Arrow functions (fn) in PHP capture outer variables by value (eagerly at definition time), not by reference or lazily at use time."} | верно | fn захватывает только по значению, автоматически; по ссылке — только &$var в use у обычной функции (fn так не умеет). |
T05-L6 1.15 c | Functions and closures | A closure declared as static function () {} does not capture $this. | «yes» Пояснение: A static closure in PHP explicitly opts out of binding $this, so it does not capture the current object context.
Raw{"answer": "yes", "explanation": "A static closure in PHP explicitly opts out of binding $this, so it does not capture the current object context."} | верно | static-замыкание отвязано от объекта: $this внутри недоступен. |
T05-L7 1.35 c | Functions and closures | What will this print: $x = 5; $f = function () use ($x) { return $x; }; $x = 7; echo $f(); | «5» Пояснение: The closure uses 'use ($x)' which captures the value of $x by value at the time of closure creation, so it remains 5 even after $x is reassigned to 7.
Raw{"answer": 5, "explanation": "The closure uses 'use ($x)' which captures the value of $x by value at the time of closure creation, so it remains 5 even after $x is reassigned to 7."} | верно | use захватывает по значению в момент создания: 5. |
T05-L8 1.51 c | Functions and closures | In weak typing mode (without strict_types), passing the string "5" to an int parameter is allowed. | «yes» Пояснение: In weak typing mode (coercive mode), PHP will automatically coerce the numeric string '5' to the integer 5 when passed to a parameter with an int type hint.
Raw{"answer": "yes", "explanation": "In weak typing mode (coercive mode), PHP will automatically coerce the numeric string '5' to the integer 5 when passed to a parameter with an int type hint."} | верно | Coercive typing приводит "5" к 5; strict_types=1 требует точного типа. |
T06-L1 0.91 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 properties to be declared and assigned directly in constructor parameters.
Raw{"answer": "yes", "explanation": "Constructor property promotion was introduced in PHP 8.0, allowing properties to be declared and assigned directly in constructor parameters."} | верно | С 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.67 c | OOP: classes and inheritance | A method declared final cannot be overridden in a subclass. | «yes» Пояснение: In PHP, a final method cannot be overridden by a subclass; attempting to do so will result in a fatal error.
Raw{"answer": "yes", "explanation": "In PHP, a final method cannot be overridden by a subclass; attempting to do so will result in a fatal error."} | верно | final запрещает переопределение метода и наследование класса. |
T06-L4 0.67 c | OOP: classes and inheritance | Parent properties with private visibility are accessible in a subclass. | «no» Пояснение: Private properties are only accessible within the class where they are defined, not in subclasses.
Raw{"answer": "no", "explanation": "Private properties are only accessible within the class where they are defined, not in subclasses."} | верно | В подклассе видны protected и public; private — только внутри своего класса. |
T06-L5 2.47 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, get_class() on an anonymous class returns 'class@anonymous' followed by a NUL byte and then the file path/line number.
Raw{"answer": "class@anonymous", "explanation": "In PHP, get_class() on an anonymous class returns 'class@anonymous' followed by a NUL byte and then the file path/line number."} | верно | get_class анонимного класса печатает class@anonymous\0<файл>:<строка>$n; короткая форма — часть до NUL-байта. Проверено php -r (hex). |
T06-L6 1.47 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» Пояснение: In PHP, private methods are not visible to child classes, so they don't form part of the inheritance contract and the child is free to declare a same-named method with any visibility.
Raw{"answer": "yes", "explanation": "In PHP, private methods are not visible to child classes, so they don't form part of the inheritance contract and the child is free to declare a same-named method with any visibility."} | верно | private-члены не наследуются — правила совместимости подписей не действуют. |
T06-L7 1.02 c | OOP: classes and inheritance | The magic method __get() is called only for non-existent properties. | «no» Пояснение: __get() is also called when reading inaccessible (protected or private) properties, not just non-existent ones.
Raw{"answer": "no", "explanation": "__get() is also called when reading inaccessible (protected or private) properties, not just non-existent ones."} | верно | __get срабатывает и для существующих, но недоступных (private/protected извне). |
T06-L8 0.95 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.64 c | Interfaces, traits, enum | An interface can declare constants. | «yes» Пояснение: PHP interfaces are allowed to declare constants, which are always public and can be accessed via the interface name.
Raw{"answer": "yes", "explanation": "PHP interfaces are allowed to declare constants, which are always public and can be accessed via the interface name."} | верно | Константы интерфейса наследуются реализациями. |
T07-L2 0.46 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.
Raw{"answer": "instanceof", "explanation": "The instanceof operator checks whether an object is an instance of a specific class or implements a specific interface."} | верно | instanceof. |
T07-L3 0.72 c | Interfaces, traits, enum | An interface can declare static methods. | «yes» Пояснение: Since PHP 8.0, interfaces can declare static methods.
Raw{"answer": "yes", "explanation": "Since PHP 8.0, interfaces can declare static methods."} | верно | Реализация обязана дать статический метод с той же сигнатурой. |
T07-L4 0.6 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.
Raw{"answer": "no", "explanation": "The instanceof operator in PHP checks both class inheritance and interface implementation."} | верно | instanceof возвращает true и для интерфейсов объекта. |
T07-L5 1.43 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 traits and abstract classes can provide method bodies.
Raw{"answer": "no", "explanation": "In PHP, interface methods are always abstract and cannot have a default implementation; only traits and abstract classes can provide method bodies."} | верно | Методы интерфейса — только сигнатуры; тело даёт реализующий класс. |
T07-L6 1.21 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, protected, or even private visibility.
Raw{"answer": "yes", "explanation": "In PHP, abstract methods can be declared with public, protected, or even private visibility."} | верно | В абстрактном классе — любая видимость; в интерфейсе — только public. |
T07-L7 0.81 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 enum cases, and there are exactly 3 defined: A, B, and C.
Raw{"answer": 3, "explanation": "Foo::cases() returns an array containing all enum cases, and there are exactly 3 defined: A, B, and C."} | верно | Статический метод cases(): 3. |
T07-L8 2.02 c | Interfaces, traits, enum | A trait can declare constants. | «yes» Пояснение: In PHP, traits can declare constants in addition to methods and properties.
Raw{"answer": "yes", "explanation": "In PHP, traits can declare constants in addition to methods and properties."} | верно | С PHP 8.2 трейты могут объявлять константы (RFC constants_in_traits); до 8.2 — нет. |
T08-L1 0.75 c | Exceptions and errors | The Throwable interface is a common ancestor of both Exception and Error. | «yes» Пояснение: In PHP, both Exception and Error implement the Throwable interface, making it their common ancestor.
Raw{"answer": "yes", "explanation": "In PHP, both Exception and Error implement the Throwable interface, making it their common ancestor."} | верно | Иерархия с PHP 7: Throwable → Exception и Throwable → Error. |
T08-L2 1.05 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 Exception and Error separately implement Throwable, so they are in different hierarchies.
Raw{"answer": "no", "explanation": "TypeError extends Error, not Exception; both Exception and Error separately implement Throwable, so they are in different hierarchies."} | верно | TypeError наследуется от Error; catch (Exception) его не ловит. |
T08-L3 1.27 c | Exceptions and errors | The @ operator suppresses exceptions too. | «no» Пояснение: The @ operator only suppresses errors/warnings/notices, not exceptions; exceptions still propagate normally.
Raw{"answer": "no", "explanation": "The @ operator only suppresses errors/warnings/notices, not exceptions; exceptions still propagate normally."} | верно | @ глушит диагностику (warnings/notices), исключения не перехватывает. |
T08-L4 1.92 c | Exceptions and errors | What error class does intdiv(5, 0) throw? | «arithmeticerror» Пояснение: intdiv() throws an ArithmeticError when the divisor is zero.
Raw{"answer": "ArithmeticError", "explanation": "intdiv() throws an ArithmeticError when the divisor is zero."} | неверно верный: «divisionbyzeroerror» | DivisionByZeroError (иерархия Error, не Exception); php-грейдер объективен. |
T08-L5 1.37 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/catch blocks.
Raw{"answer": "no", "explanation": "The finally block runs regardless of whether an exception was thrown or caught; it always executes after the try/catch blocks."} | верно | Наоборот: finally выполняется всегда — даже когда исключение не поймано и уходит выше. Проверено php -r. |
T08-L6 1.39 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 overrides the exception from the try/catch block, becoming the exception that propagates outward.
Raw{"answer": "no", "explanation": "An exception thrown in a finally block overrides the exception from the try/catch block, becoming the exception that propagates outward."} | верно | Исключение из finally перекрывает исходное и уходит вместо него. |
T08-L7 0.97 c | Exceptions and errors | What does the expression (bool) new Exception('x') return? | «yes» Пояснение: In PHP, any object is always truthy when cast to boolean, so (bool) new Exception('x') returns true.
Raw{"answer": "yes", "explanation": "In PHP, any object is always truthy when cast to boolean, so (bool) new Exception('x') returns true."} | верно | Любой объект при приведении к bool — true. Формы ответа: true или да. |
T08-L8 1.13 c | Exceptions and errors | Functions registered via register_shutdown_function() run when exit is called. | «yes» Пояснение: Shutdown functions registered via register_shutdown_function() are executed during the script shutdown phase, which is triggered by exit, die, normal script completion, or a fatal error.
Raw{"answer": "yes", "explanation": "Shutdown functions registered via register_shutdown_function() are executed during the script shutdown phase, which is triggered by exit, die, normal script completion, or a fatal error."} | верно | exit завершает скрипт, но shutdown-функции отрабатывают. |
T09-L1 1.17 c | Namespaces and autoloading | The use App\Service\Mailer; statement itself loads the class file. | «no» Пояснение: The use statement is merely an alias declaration at compile time; the class file is actually loaded only when the class is first used (e.g., instantiated), triggering the autoloader.
Raw{"answer": "no", "explanation": "The use statement is merely an alias declaration at compile time; the class file is actually loaded only when the class is first used (e.g., instantiated), triggering the autoloader."} | верно | use — псевдоним на этапе компиляции; файл грузит автозагрузчик при первом обращении. |
T09-L2 0.73 c | Namespaces and autoloading | What follows use to import a function (not a class): the word function or const? | «function» Пояснение: In PHP, to import a function from a namespace you use 'use function Namespace\functionName;'.
Raw{"answer": "function", "explanation": "In PHP, to import a function from a namespace you use 'use function Namespace\\functionName;'."} | верно | use function ...; (и use const для констант). |
T09-L3 1.2 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 App\ prefix, converts remaining namespace separators to directory separators, and appends .php, yielding Controller/Api/UserController.php relative to src/.
Raw{"answer": "Controller/Api/UserController.php", "explanation": "PSR-4 strips the App\\ prefix, converts remaining namespace separators to directory separators, and appends .php, yielding Controller/Api/UserController.php relative to src/."} | верно | Остаток имени после префикса, \ → /. |
T09-L4 0.92 c | Namespaces and autoloading | Including vendor/autoload.php registers autoloaders via spl_autoload_register(). | «yes» Пояснение: Composer's vendor/autoload.php internally calls spl_autoload_register() to register the ClassLoader for automatic class loading.
Raw{"answer": "yes", "explanation": "Composer's vendor/autoload.php internally calls spl_autoload_register() to register the ClassLoader for automatic class loading."} | верно | Composer ставит автозагрузчик именно на spl_autoload_register. |
T09-L5 0.84 c | Namespaces and autoloading | The magic constant __NAMESPACE__ contains the name of the current namespace. | «yes» Пояснение: __NAMESPACE__ is a PHP magic constant that returns the name of the current namespace as a string (or an empty string in the global namespace).
Raw{"answer": "yes", "explanation": "__NAMESPACE__ is a PHP magic constant that returns the name of the current namespace as a string (or an empty string in the global namespace)."} | верно | В корневом пространстве — пустая строка. |
T09-L6 1.22 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 resolved relative to the current namespace, not the global root; a leading backslash is needed for global root resolution.
Raw{"answer": "no", "explanation": "An unqualified class name in 'new' is resolved relative to the current namespace, not the global root; a leading backslash is needed for global root resolution."} | верно | Резолвится относительно текущего namespace (с учётом импортов). |
T09-L7 1.05 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 strips the prefix App\, converts the remaining Model\User to Model/User, appends .php, and prepends the base path src/.
Raw{"answer": "yes", "explanation": "PSR-4 strips the prefix App\\, converts the remaining Model\\User to Model/User, appends .php, and prepends the base path src/."} | верно | Остаток имени после префикса переносится в путь как есть. |
T09-L8 1.23 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 for namespaces can be declared inside a function body, and the alias then applies only within that function's scope.
Raw{"answer": "yes", "explanation": "In PHP, a use statement for namespaces can be declared inside a function body, and the alias then applies only within that function's scope."} | неверно верный: «no» | use внутри тела функции — parse error; импорты файловые и компиляционные. |
T10-L1 0.93 c | References and scope | Arrays are copied on assignment rather than passed by reference. | «yes» Пояснение: In PHP, arrays are copied by value on assignment (using copy-on-write internally for efficiency), not passed by reference.
Raw{"answer": "yes", "explanation": "In PHP, arrays are copied by value on assignment (using copy-on-write internally for efficiency), not passed by reference."} | верно | Присваивание массива — копия (в движке — copy-on-write). |
T10-L2 1.14 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, so modifying $b does not affect $a, which still has 2 elements.
Raw{"answer": 2, "explanation": "Arrays in PHP are copied by value, so modifying $b does not affect $a, which still has 2 elements."} | верно | Присваивание — копия: в $a по-прежнему 2 элемента. |
T10-L3 1.32 c | References and scope | Inside a function, user-defined global variables are inaccessible without global, $GLOBALS, or passing them as parameters. | «yes» Пояснение: In PHP, user-defined global variables are not in scope inside a function unless accessed via the global keyword, $GLOBALS array, or passed as parameters.
Raw{"answer": "yes", "explanation": "In PHP, user-defined global variables are not in scope inside a function unless accessed via the global keyword, $GLOBALS array, or passed as parameters."} | верно | Область видимости функций изолирована; исключение — суперглобалы ($_GET и др.). |
T10-L4 1.61 c | References and scope | unset($GLOBALS['x']) inside a function removes the global variable only for that function. | «no» Пояснение: $GLOBALS is a reference to the actual global symbol table, so unset($GLOBALS['x']) removes the variable from the global scope entirely, not just for that function.
Raw{"answer": "no", "explanation": "$GLOBALS is a reference to the actual global symbol table, so unset($GLOBALS['x']) removes the variable from the global scope entirely, not just for that function."} | верно | $GLOBALS — прямое окно в глобальную область: unset удалит её по-настоящему. |
T10-L5 0.78 c | References and scope | What will this print: function inc(&$x) { $x++; } $n = 5; inc($n); echo $n; | «6» Пояснение: The parameter is passed by reference (&$x), so incrementing $x inside the function also increments $n, making it 6.
Raw{"answer": 6, "explanation": "The parameter is passed by reference (&$x), so incrementing $x inside the function also increments $n, making it 6."} | верно | Ссылка меняет оригинал: 6. |
T10-L6 1.81 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» Пояснение: A foreach by value iterates over an internal copy of the array, so modifications to the original array inside the loop body do not affect the current iteration.
Raw{"answer": "no", "explanation": "A foreach by value iterates over an internal copy of the array, so modifications to the original array inside the loop body do not affect the current iteration."} | верно | По значению foreach итерирует копию-снимок. |
T10-L7 0.83 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 and is shared across all instances, so changes are visible through every instance.
Raw{"answer": "no", "explanation": "A static property belongs to the class itself and is shared across all instances, so changes are visible through every instance."} | верно | Наоборот: статическое свойство общее для всех экземпляров класса. Проверено php -r. |
T10-L8 0.84 c | References and scope | An array can have a boolean key true, and it will be stored as bool. | «no» Пояснение: In PHP, boolean array keys are cast to integers: true becomes 1 and false becomes 0, so the key is stored as an int, not a bool.
Raw{"answer": "no", "explanation": "In PHP, boolean array keys are cast to integers: true becomes 1 and false becomes 0, so the key is stored as an int, not a bool."} | верно | Булев ключ приводится к int: true → 1, false → 0. |
T11-L1 1.27 c | Generators, iterators, SPL | Inside a generator, return with a value can be used, and it becomes available via $gen->getReturn(). | «yes» Пояснение: In PHP, a generator's `return` value (not yielded) is stored internally and can be retrieved after exhaustion via $gen->getReturn().
Raw{"answer": "yes", "explanation": "In PHP, a generator's `return` value (not yielded) is stored internally and can be retrieved after exhaustion via $gen->getReturn()."} | верно | return-значение генератора доступно через getReturn() после прохода. |
T11-L2 1.26 c | Generators, iterators, SPL | A fully consumed generator can be rewound with rewind() and traversed again. | «yes» Пояснение: PHP's Generator objects implement the Iterator interface, and calling rewind() resets a fully consumed generator back to its initial state so it can be iterated again.
Raw{"answer": "yes", "explanation": "PHP's Generator objects implement the Iterator interface, and calling rewind() resets a fully consumed generator back to its initial state so it can be iterated again."} | неверно верный: «no» | Генератор одноразовый: rewind после начала итерации бросает Exception. |
T11-L3 2.27 c | Generators, iterators, SPL | The yield from construct delegates traversal to another generator or iterable. | «no» Пояснение: PHP has a `yield` keyword for generators but no `yield from` construct; that is a Python feature.
Raw{"answer": "no", "explanation": "PHP has a `yield` keyword for generators but no `yield from` construct; that is a Python feature."} | неверно верный: «yes» | yield from проксирует значения, ключи и return-значение внутреннего генератора. |
T11-L4 1.12 c | Generators, iterators, SPL | What does get_class(g()) return for function g() { yield 1; }? | «generator» Пояснение: Calling a generator function returns an instance of the built-in Generator class, so get_class() returns the string 'Generator'.
Raw{"answer": "Generator", "explanation": "Calling a generator function returns an instance of the built-in Generator class, so get_class() returns the string 'Generator'."} | верно | Функция с yield возвращает Generator. |
T11-L5 1.53 c | Generators, iterators, SPL | How many elements will count(iterator_to_array((function () { yield from [1, 2, 3]; })())) return? | «3» Пояснение: The generator yields 3 values (1, 2, 3), iterator_to_array produces an array with 3 elements, and count returns 3.
Raw```json ⏎ {"answer": 3, "explanation": "The generator yields 3 values (1, 2, 3), iterator_to_array produces an array with 3 elements, and count returns 3."} ⏎ ``` | верно | yield from делегирует все 3 элемента. |
T11-L6 0.68 c | Generators, iterators, SPL | The SplStack class implements a FIFO queue. | «no» Пояснение: SplStack implements a LIFO (Last-In, First-Out) stack, not a FIFO queue; SplQueue is the class that implements a FIFO queue.
Raw{"answer": "no", "explanation": "SplStack implements a LIFO (Last-In, First-Out) stack, not a FIFO queue; SplQueue is the class that implements a FIFO queue."} | верно | SplStack — стек LIFO; очередь FIFO — SplQueue. |
T11-L7 0.8 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(), key(), next(), rewind(), and valid().
Raw{"answer": "yes", "explanation": "ArrayIterator is a built-in PHP class that wraps an array and implements the Iterator interface, allowing traversal via current(), key(), next(), rewind(), and valid()."} | верно | Объектная обёртка над массивом. |
T11-L8 0.75 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 0.75 c | Configuration and security | password_hash() generates a salt automatically — passing one separately is not needed. | «yes» Пояснение: password_hash() internally generates a random salt and embeds it in the resulting hash string; there is no parameter to pass one manually.
Raw{"answer": "yes", "explanation": "password_hash() internally generates a random salt and embeds it in the resulting hash string; there is no parameter to pass one manually."} | верно | Соль встраивается в строку результата; параметр salt устарел. |
T12-L2 1.0 c | Configuration and security | In PHP 8, PASSWORD_DEFAULT is md5 with an automatically added salt. | «no» Пояснение: In PHP 8, PASSWORD_DEFAULT is bcrypt (PASSWORD_BCRYPT), not md5.
Raw{"answer":"no","explanation":"In PHP 8, PASSWORD_DEFAULT is bcrypt (PASSWORD_BCRYPT), not md5."} | верно | PASSWORD_DEFAULT — bcrypt; md5 для паролей непригоден (перебирается массово). |
T12-L3 0.76 c | Configuration and security | What does password_verify('secret', password_hash('secret', PASSWORD_DEFAULT)) return? | «yes» Пояснение: password_verify() returns true because the plaintext 'secret' matches the hash generated from 'secret'.
Raw{"answer": "yes", "explanation": "password_verify() returns true because the plaintext 'secret' matches the hash generated from 'secret'."} | верно | Соль и хеш в одной строке: true (форма ответа: true или да). |
T12-L4 1.02 c | Configuration and security | strip_tags() protects against SQL injection. | «no» Пояснение: strip_tags() removes HTML/PHP tags to help mitigate XSS, but SQL injection is prevented by prepared statements or parameterized queries, not by stripping tags.
Raw{"answer": "no", "explanation": "strip_tags() removes HTML/PHP tags to help mitigate XSS, but SQL injection is prevented by prepared statements or parameterized queries, not by stripping tags."} | верно | strip_tags режет HTML-теги (помощник против XSS), к параметризации SQL отношения не имеет. |
T12-L5 1.01 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, typically called upon login.
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, typically called upon login."} | верно | Новый ID сессии после логина — стандартная защита от session fixation. |
T12-L6 0.9 c | Configuration and security | Which built-in function returns the SAPI name (e.g., cli)? | «php_sapi_name()» Пояснение: php_sapi_name() returns the current SAPI module name, such as 'cli', 'apache2', or 'fpm-fcgi'.
Raw{"answer": "php_sapi_name()", "explanation": "php_sapi_name() returns the current SAPI module name, such as 'cli', 'apache2', or 'fpm-fcgi'."} | верно | php_sapi_name(). |
T12-L7 1.16 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 session data on the server side; the PHPSESSID cookie in the browser remains until it expires or is explicitly deleted with setcookie().
Raw{"answer": "yes", "explanation": "session_destroy() only removes session data on the server side; the PHPSESSID cookie in the browser remains until it expires or is explicitly deleted with setcookie()."} | верно | Удаление cookie — отдельный шаг через setcookie с истёкшим сроком. |
T12-L8 1.06 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; without it, it remains an empty array.
Raw{"answer": "no", "explanation": "The $_SESSION array is only populated with session data after session_start() is called; without it, it remains an empty array."} | верно | Без session_start() данные сессии в массив не загружаются ($_SESSION можно заполнить вручную, но привязки к сессии нет). |
VC-L1 0.92 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 new array helper functions.
Raw{"answer": "8.1", "explanation": "The array_find() function was introduced in PHP 8.1 as part of the new array helper functions."} | неверно верный: «8.4» | PHP 8.4 (RFC array_find). |
VC-L2 0.82 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, update) were a major new feature introduced in PHP 8.4.
Raw{"answer": "yes", "explanation": "Property hooks (get, set, update) were a major new feature introduced in PHP 8.4."} | верно | Property hooks — PHP 8.4 (ноябрь 2024). |
VC-L3 0.88 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) was introduced in PHP 8.4.
Raw{"answer": "yes", "explanation": "Asymmetric visibility (e.g., public private(set) string $name) was introduced in PHP 8.4."} | верно | Asymmetric visibility v2 — PHP 8.4. |
VC-L4 1.06 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 help developers remember to use the return values of functions.
Raw{"answer": "8.4", "explanation": "The #[\\NoDiscard] attribute was introduced in PHP 8.4 to help developers remember to use the return values of functions."} | неверно верный: «8.5» | #[\NoDiscard] — PHP 8.5 (marking return values as important). |
VC-L5 3.1 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, allowing function calls to be chained in a readable pipeline style.
Raw```json ⏎ {"answer": "8.4", "explanation": "The pipe operator |> was introduced in PHP 8.4, allowing function calls to be chained in a readable pipeline style."} ⏎ ``` | неверно верный: «8.5» | Pipe operator — PHP 8.5 (2025). |
VC-L6 7.0 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. | «no» Пояснение: The syntax clone($obj, ['x' => 1]) is not a feature implemented in any released PHP version; clone in PHP has always been the unary operator clone $obj.
Raw{"answer": "no", "explanation": "The syntax clone($obj, ['x' => 1]) is not a feature implemented in any released PHP version; clone in PHP has always been the unary operator clone $obj."} | неверно верный: «8.5» | Clone with v2 — PHP 8.5. |
VC-L7 1.84 c | PHP 8.4–8.5 | In which PHP version were the array_first() and array_last() functions introduced? | «8.4» Пояснение: The array_first() and array_last() functions were introduced in PHP 8.4 as part of a new set of array helper functions.
Raw{"answer": 8.4, "explanation": "The array_first() and array_last() functions were introduced in PHP 8.4 as part of a new set of array helper functions."} | неверно верный: «8.5» | PHP 8.5. |
VC-L8 2.19 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{"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.96 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 clamp() function was implemented in PHP 8.4 via the RFC clamp_v2.
Raw{"answer": "8.4", "explanation": "The clamp() function was implemented in PHP 8.4 via the RFC clamp_v2."} | неверно верный: «8.6» | По данным владельца (wiki.php.net/rfc): clamp_v2 — 8.6; clamp() в 8.5.11 отсутствует (косвенное подтверждение). Дата-якорь делает клетку монотонной. |
VF-L2 2.68 c | PHP: 8.6+ and the future | RFC Context Managers v2 has already been adopted in PHP (as of 2026-11-07). | «yes» Пояснение: The Context Manager v2 RFC was accepted for PHP 8.5 (released late 2025), so it is already adopted by November 2026.
Raw{"answer": "yes", "explanation": "The Context Manager v2 RFC was accepted for PHP 8.5 (released late 2025), so it is already adopted by November 2026."} | неверно верный: «no» | На 06.11.2026 — в обсуждении (создан 2026-10-23); не принят. |
VF-L3 2.08 c | PHP: 8.6+ and the future | RFC Bound-Erased Generic Types (generics) was declined in 2026. | «no» Пояснение: The RFC for Bound-Erased Generic Types was declined in 2024 (during the PHP 8.4 voting cycle), not in 2026.
Raw{"answer": "no", "explanation": "The RFC for Bound-Erased Generic Types was declined in 2024 (during the PHP 8.4 voting cycle), not in 2026."} | неверно верный: «yes» | Голосование завершилось 2026-06-28: отклонён (wiki.php.net/rfc). |
VF-L4 4.0 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. | «no» Пояснение: While PHP has offered a ZTS (Zend Thread Safe) build for years, the RFC to make ZTS the default build has not been accepted; PHP still defaults to NTS (Non-Thread Safe) builds.
Raw{"answer": "no", "explanation": "While PHP has offered a ZTS (Zend Thread Safe) build for years, the RFC to make ZTS the default build has not been accepted; PHP still defaults to NTS (Non-Thread Safe) builds."} | верно | Такого принятого RFC нет на дату якоря; якорь делает клетку монотонной — при принятии RFC позже клетка не перевернётся. |
VF-L5 1.78 c | PHP: 8.6+ and the future | As of PHP 8.5, generics (parameterized types) are still absent. | «yes» Пояснение: As of PHP 8.5, native generics (parameterized types) have not been implemented; PHP still relies on documentation and static analysis tools to express generic type intentions.
Raw{"answer": "yes", "explanation": "As of PHP 8.5, native generics (parameterized types) have not been implemented; PHP still relies on documentation and static analysis tools to express generic type intentions."} | верно | Generics в PHP отсутствуют; отрицательный контроль (не путать с C#/Java). |
VF-L6 2.18 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 roughly annual November release cycle, so PHP 8.5 would have been released in November 2025 and PHP 8.6's GA would come in November 2026, making 8.5 the latest stable as of 2026-11-07.
Raw{"answer": "yes", "explanation": "PHP follows a roughly annual November release cycle, so PHP 8.5 would have been released in November 2025 and PHP 8.6's GA would come in November 2026, making 8.5 the latest stable as of 2026-11-07."} | верно | 8.5 — релиз осени 2025; 8.6 GA 19.11.2026 (wiki.php.net/todo/php86). Дата снимка — 06.11.2026. |
VF-L7 0.99 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; PHP 7.0 followed PHP 5.6 directly.
Raw{"answer": "yes", "explanation": "PHP 6 was planned but never released; PHP 7.0 followed PHP 5.6 directly."} | верно | Исторический факт: ветка 6 не была релизнута. |
VF-L8 1.78 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 rejected during the voting phase and was not adopted into PHP core.
Raw{"answer": "no", "explanation": "The RFC for the #[\\Deprecated] attribute was rejected during the voting phase and was not adopted into PHP core."} | неверно верный: «yes» | #[\Deprecated] — принят, реализован в PHP 8.4. |
T25-L1 0.85 c | Clean architecture | The dependency rule of clean and onion architecture: inner layers know nothing about outer ones — dependencies point toward the center. | «yes» Пояснение: The dependency rule in clean/onion architecture mandates that dependencies point inward toward the domain, so inner layers have no knowledge of outer layers.
Raw{"answer": "yes", "explanation": "The dependency rule in clean/onion architecture mandates that dependencies point inward toward the domain, so inner layers have no knowledge of outer layers."} | верно | Чистая (Robert C. Martin), луковичная (Jeffrey Palermo) и гексагональная (ports & adapters) — варианты одной идеи: зависимости направлены внутрь, к домену. Слоями в проекте следит deptrac. |
T25-L2 2.09 c | Clean architecture | Domain entities import neither Doctrine nor Symfony — only the language and, possibly, the standard library. | «yes» Пояснение: In clean architecture/DDD, domain entities should be pure PHP classes with no dependency on frameworks like Doctrine or Symfony, relying only on the language and possibly the standard library.
Raw{"answer": "yes", "explanation": "In clean architecture/DDD, domain entities should be pure PHP classes with no dependency on frameworks like Doctrine or Symfony, relying only on the language and possibly the standard library."} | верно | Изоляция домена от инфраструктуры; deptrac в проекте как раз следит за слоями. |
T25-L3 1.91 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 (web) layer, not the business-logic layer; they simply delegate to use cases which live in the application/domain layer.
Raw{"answer": "no", "explanation": "Controllers and Twig templates belong to the presentation (web) layer, not the business-logic layer; they simply delegate to use cases which live in the application/domain layer."} | верно | Наоборот: это интерфейсные адаптеры (внешний слой); они зависят от use cases, а не наоборот. |
T25-L4 1.45 c | Clean architecture | What sits at the very center of the onion architecture? | «entity» Пояснение: In onion architecture, the innermost layer contains the core domain entities, which hold the most critical business rules and logic.
Raw{"answer": "Entity", "explanation": "In onion architecture, the innermost layer contains the core domain entities, which hold the most critical business rules and logic."} | неверно верный: «domain model» | Центральное кольцо — Domain Model: сущности и бизнес-правила без зависимостей; далее Domain Services → Application Services → Infrastructure/UI/Tests (Palermo). |
T25-L5 0.97 c | Clean architecture | Layer boundary violations can be caught automatically: a layer-dependency analyzer (e.g. deptrac) fails on a forbidden call. | «yes» Пояснение: Tools like deptrac enforce layer dependency rules and report/fail on forbidden cross-layer calls automatically.
Raw{"answer": "yes", "explanation": "Tools like deptrac enforce layer dependency rules and report/fail on forbidden cross-layer calls automatically."} | верно | depfile.yaml в проекте TasK: CI проверяет правила слоёв на каждом пайплайне. |
T25-L6 1.81 c | Clean architecture | A use case (interactor) may accept an HTTP request or an EntityManager as arguments — it is simpler that way. | «no» Пояснение: In clean architecture, a use case should depend on abstractions (e.g., a command object, a repository interface), not on concrete infrastructure like an HTTP request or an EntityManager.
Raw{"answer": "no", "explanation": "In clean architecture, a use case should depend on abstractions (e.g., a command object, a repository interface), not on concrete infrastructure like an HTTP request or an EntityManager."} | верно | Use case принимает DTO и порты; привязка к HTTP/ORM протекает инфраструктуру во внутренние слои. |
T25-L7 0.93 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 of aggregates/entities while abstracting the underlying storage mechanism behind an interface.
Raw{"answer": "Repository", "explanation": "The Repository pattern provides a collection of aggregates/entities while abstracting the underlying storage mechanism behind an interface."} | верно | Repository pattern (DDD/Evans); в проекте — Doctrine-репозитории за портами. |
T25-L8 1.91 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 a detail of the outermost layer (frameworks & drivers); use cases depend only on an interface (e.g., a repository port), so swapping the database only affects the adapter implementation.
Raw{"answer": "yes", "explanation": "In Clean Architecture, the database is a detail of the outermost layer (frameworks & drivers); use cases depend only on an interface (e.g., a repository port), so swapping the database only affects the adapter implementation."} | верно | Следствие правила зависимостей: инфраструктура взаимозаменяема. |
T26-L1 1.34 c | DDD | In DDD, an aggregate is just another name for a database table. | «no» Пояснение: In DDD, an aggregate is a cluster of domain objects treated as a unit with a root entity that enforces invariants; it is a conceptual boundary, not a one-to-one mapping to a database table.
Raw{"answer": "no", "explanation": "In DDD, an aggregate is a cluster of domain objects treated as a unit with a root entity that enforces invariants; it is a conceptual boundary, not a one-to-one mapping to a database table."} | верно | Агрегат — кластер объектов с границей согласованности (транзакционной вокруг корня); таблица — деталь хранения. |
T26-L2 0.83 c | DDD | A Value Object is immutable and compared by the values of its fields, not by identity. | «yes» Пояснение: In DDD, a Value Object is defined as being immutable and determined by its attribute values rather than by a unique identity.
Raw{"answer": "yes", "explanation": "In DDD, a Value Object is defined as being immutable and determined by its attribute values rather than by a unique identity."} | верно | Классика Evans: Money, Email; равенство структурное. |
T26-L3 0.81 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 of an aggregate through which all external changes must pass.
Raw{"answer": "Aggregate Root", "explanation": "In Domain-Driven Design, the Aggregate Root is the single entry point of an aggregate through which all external changes must pass."} | верно | Aggregate Root: внешние объекты ссылаются только на корень; он защищает инварианты агрегата. |
T26-L4 1.2 c | DDD | In DDD, a repository is declared for an aggregate (its root), not for every entity. | «yes» Пояснение: In DDD, a repository is defined per Aggregate (root), encapsulating access to all entities within that aggregate, rather than creating a separate repository for each individual entity.
Raw{"answer": "yes", "explanation": "In DDD, a repository is defined per Aggregate (root), encapsulating access to all entities within that aggregate, rather than creating a separate repository for each individual entity."} | верно | Репозиторий корня хранит границу согласованности агрегата; вложенные сущности доступны только через корень. |
T26-L5 1.0 c | DDD | Ubiquitous language is the model's shared language common to developers and domain experts. | «yes» Пояснение: Ubiquitous Language, as defined in Domain-Driven Design, is a shared language between developers and domain experts to ensure the model's terms align with domain terminology.
Raw{"answer": "yes", "explanation": "Ubiquitous Language, as defined in Domain-Driven Design, is a shared language between developers and domain experts to ensure the model's terms align with domain terminology."} | верно | Evans: язык из требований переходит в имена классов и методов. |
T26-L6 4.57 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 boundary within which a model and its language are self-consistent, while outside it the same words can refer to different models or meanings.
Raw```json ⏎ {"answer": "frame", "explanation": "A frame is the boundary within which a model and its language are self-consistent, while outside it the same words can refer to different models or meanings."} ⏎ ``` | неверно верный: «bounded context» | Bounded Context; «Заказ» в биллинге и в доставке — разные модели. |
T26-L7 1.33 c | DDD | An anemic model (objects with only getters/setters, logic in services) is the recommended DDD style. | «no» Пояснение: DDD recommends a rich domain model where objects encapsulate both state and behavior; the anemic model (logic in services) is considered an anti-pattern in DDD.
Raw{"answer": "no", "explanation": "DDD recommends a rich domain model where objects encapsulate both state and behavior; the anemic model (logic in services) is considered an anti-pattern in DDD."} | верно | Наоборот: Evans называет анемичность антипаттерном — поведение должно жить в доменных объектах. |
T26-L8 1.51 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 ensures that each context has its own domain model, so the same real-world concept (e.g., 'Product') can be modeled as different classes with different attributes and behaviors in different contexts.
Raw{"answer": "yes", "explanation": "In DDD, a Bounded Context ensures that each context has its own domain model, so the same real-world concept (e.g., 'Product') can be modeled as different classes with different attributes and behaviors in different contexts."} | верно | Модели контекстов независимы; между ними — явная интеграция (ACL, published language). |
T13-L1 1.08 c | Symfony | Services in the Symfony DI container are created lazily by default — on first use. | «yes» Пояснение: Symfony's DI container instantiates services lazily, only when they are first requested, rather than eagerly at container build time.
Raw{"answer": "yes", "explanation": "Symfony's DI container instantiates services lazily, only when they are first requested, rather than eagerly at container build time."} | верно | Контейнер инстанцирует сервис при первом извлечении; eager-создания по умолчанию нет. |
T13-L2 0.56 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.3 c | Symfony | Symfony autowiring requires manually declaring every service in services.yaml. | «no» Пояснение: The whole point of autowiring is that dependencies are resolved automatically by type-hinting, so you don't need to manually declare every service in services.yaml.
Raw{"answer": "no", "explanation": "The whole point of autowiring is that dependencies are resolved automatically by type-hinting, so you don't need to manually declare every service in services.yaml."} | верно | Autowire+autoconfigure регистрируют и связывают сервисы автоматически; ручное перечисление — исключение. |
T13-L4 1.07 c | Symfony | Twig templates are compiled into PHP classes and cached between requests. | «yes» Пояснение: Twig compiles templates into PHP classes and caches them (typically in the filesystem) to avoid recompilation on subsequent requests.
Raw{"answer": "yes", "explanation": "Twig compiles templates into PHP classes and caches them (typically in the filesystem) to avoid recompilation on subsequent requests."} | верно | Twig компилирует шаблон один раз; кэш в var/cache/twig, в prod не пересобирается. |
T13-L5 1.17 c | Symfony | In the Symfony dev environment the DI container is rebuilt only after tracked files change, not on every request. | «yes» Пояснение: In the Symfony dev environment, the DI container is cached and only rebuilt when tracked files (e.g., service configs, class definitions) are detected as changed.
Raw{"answer": "yes", "explanation": "In the Symfony dev environment, the DI container is cached and only rebuilt when tracked files (e.g., service configs, class definitions) are detected as changed."} | верно | Kernel проверяет freshness ресурсов (конфиги, классы); иначе переиспользуется кэш контейнера. |
T13-L6 0.84 c | Symfony | Which environment variable selects the active Symfony environment (dev/prod)? | «app_env» Пояснение: Since Symfony 5.1, the APP_ENV environment variable is used to select the active environment (dev/prod/test).
Raw{"answer": "APP_ENV", "explanation": "Since Symfony 5.1, the APP_ENV environment variable is used to select the active environment (dev/prod/test)."} | верно | APP_ENV в .env; APP_DEBUG — отдельный флаг отладки. |
T13-L7 1.63 c | Symfony | A controller method can be private — Symfony routing works with any method of the class. | «no» Пояснение: Symfony controller methods must be public because the controller resolver invokes them from outside the class using reflection.
Raw{"answer": "no", "explanation": "Symfony controller methods must be public because the controller resolver invokes them from outside the class using reflection."} | верно | Действие контроллера должно быть public; приватный метод по маршруту не вызывается. |
T13-L8 2.0 c | Symfony | Event subscribers always receive events before listeners, because the interface gives them priority. | «no» Пояснение: Subscribers are just a convenience for registering multiple listeners at once; once registered, both subscribers and listeners are subject to the same priority system with no inherent priority advantage for subscribers.
Raw{"answer": "no", "explanation": "Subscribers are just a convenience for registering multiple listeners at once; once registered, both subscribers and listeners are subject to the same priority system with no inherent priority advantage for subscribers."} | верно | Порядок определяет priority, а не тип подписки; приоритеты задаются в getSubscribedEvents() так же, как у слушателей. |
T22-L1 1.6 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» Пояснение: In Symfony 6.0 the old Guard system (GuardAuthenticationHandler, GuardAuthenticatorHandler, etc.) was removed, and authentication is fully based on classes implementing AuthenticatorInterface.
Raw{"answer": "yes", "explanation": "In Symfony 6.0 the old Guard system (GuardAuthenticationHandler, GuardAuthenticatorHandler, etc.) was removed, and authentication is fully based on classes implementing AuthenticatorInterface."} | верно | Guard объявлен устаревшим в 5.3 и удалён в 6.0; в проекте symfony/security-bundle 8.1. |
T22-L2 0.98 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 a role or permission on a controller method and returns a 403 Forbidden response if the user doesn't have the required access.
Raw{"answer": "IsGranted", "explanation": "The #[IsGranted] attribute in Symfony checks a role or permission on a controller method and returns a 403 Forbidden response if the user doesn't have the required access."} | верно | #[IsGranted('ROLE_ADMIN')]; атрибут из symfony/security-http. |
T22-L3 0.97 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 defining custom access rules, including object-level permissions like isGranted('EDIT', $post).
Raw{"answer": "yes", "explanation": "Voters in Symfony are the mechanism for defining custom access rules, including object-level permissions like isGranted('EDIT', $post)."} | верно | VoterInterface->vote(); docs Symfony — Voters. |
T22-L4 4.46 c | Symfony: Security and forms | In modern Symfony (7+) validation constraints are declared as PHP attributes (#[Assert\NotBlank]); doctrine annotations are no longer supported. | «no» Пояснение: While PHP attributes are the recommended approach in Symfony 7+, doctrine annotations are still supported (deprecated but functional) if the doctrine/annotations package is installed.
Raw```json ⏎ {"answer": "no", "explanation": "While PHP attributes are the recommended approach in Symfony 7+, doctrine annotations are still supported (deprecated but functional) if the doctrine/annotations package is installed."} ⏎ ``` | неверно верный: «yes» | Докблок-аннотации удалены в Symfony 7.0; стандарт — атрибуты. В проекте symfony/validator 8.1. |
T22-L5 1.06 c | Symfony: Security and forms | CSRF protection of Symfony forms is enabled by default: the form validates the token on submission. | «yes» Пояснение: Symfony forms have CSRF protection enabled by default; a token is automatically generated and validated on submission unless explicitly disabled.
Raw{"answer": "yes", "explanation": "Symfony forms have CSRF protection enabled by default; a token is automatically generated and validated on submission unless explicitly disabled."} | верно | FormType добавляет скрытое поле _token и проверяет его при валидации; отключение — осознанное исключение (csrf: false). |
T22-L6 1.32 c | Symfony: Security and forms | Form validation in Symfony runs server-side even if the client-side (HTML5) checks passed. | «yes» Пояснение: Symfony always validates forms server-side upon submission; client-side HTML5 validation is only a UX layer and is never relied upon as the sole validation mechanism.
Raw{"answer": "yes", "explanation": "Symfony always validates forms server-side upon submission; client-side HTML5 validation is only a UX layer and is never relied upon as the sole validation mechanism."} | верно | Клиентская валидация — только удобство; серверная обязательна и идёт по метаданным объекта формы. |
T22-L7 0.47 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.57 c | Symfony: Security and forms | Symfony stores the user's password in the session in plain text. | «no» Пояснение: Symfony stores the user's identity (e.g., user ID or username) in the session, not the password; the password is only used for comparison during authentication and is never persisted in the session.
Raw```json ⏎ {"answer": "no", "explanation": "Symfony stores the user's identity (e.g., user ID or username) in the session, not the password; the password is only used for comparison during authentication and is never persisted in the session."} ⏎ ``` | верно | В сессии живёт объект пользователя в токене; хеш затирается eraseCredentials(), plaintext там никогда не лежит. |
T23-L1 1.13 c | Symfony: configuration and services | Symfony bundle configuration lives in config/packages — one file per bundle or topic. | «yes» Пояснение: In modern Symfony (4+/Flex), bundle configurations are stored in config/packages/ with one file per bundle or topic (e.g., doctrine.yaml, twig.yaml).
Raw{"answer": "yes", "explanation": "In modern Symfony (4+/Flex), bundle configurations are stored in config/packages/ with one file per bundle or topic (e.g., doctrine.yaml, twig.yaml)."} | верно | Стандартная структура (config/packages/*.yaml); перегрузка — config/packages/<env>. |
T23-L2 1.49 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 a common best practice pattern (used in Laravel, Symfony, etc.) where .env holds safe dev defaults committed to the repo, and .env.local holds real secrets that are git-ignored.
Raw```json ⏎ {"answer": "yes", "explanation": "This is a common best practice pattern (used in Laravel, Symfony, etc.) where .env holds safe dev defaults committed to the repo, and .env.local holds real secrets that are git-ignored."} ⏎ ``` | верно | symfony/dotenv: .env — общий безопасный набор значений; локальные секреты — .env.local (gitignored) или secrets-хранилище. |
T23-L3 0.87 c | Symfony: configuration and services | Which Symfony command lists the container's registered services and their aliases? | «debug:container» Пояснение: The Symfony command 'debug:container' lists all registered services and their aliases in the service container.
Raw{"answer": "debug:container", "explanation": "The Symfony command 'debug:container' lists all registered services and their aliases in the service container."} | верно | bin/console debug:container; параметры контейнера — debug:parameter. |
T23-L4 1.28 c | Symfony: configuration and services | The Symfony container allows changing parameters at runtime: $container->setParameter() works from a controller. | «yes» Пояснение: Symfony's container is a runtime object, so setParameter() can be called at any time during the request lifecycle to modify parameters.
Raw{"answer": "yes", "explanation": "Symfony's container is a runtime object, so setParameter() can be called at any time during the request lifecycle to modify parameters."} | неверно верный: «no» | Контейнер компилируется и замораживается; runtime-значения — только через переменные окружения. |
T23-L5 0.93 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.3, services are private by default and cannot be fetched directly from the container unless explicitly marked public: true.
Raw{"answer": "no", "explanation": "Since Symfony 4.3, services are private by default and cannot be fetched directly from the container unless explicitly marked public: true."} | верно | С Symfony 4.0 сервисы по умолчанию private: инжектятся через autowiring; $container->get() — только для публичных. |
T23-L6 1.44 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 bundles work perfectly fine without a configuration file in config/packages, as they rely on sensible defaults.
Raw```json ⏎ {"answer": "no", "explanation": "Many bundles work perfectly fine without a configuration file in config/packages, as they rely on sensible defaults."} ⏎ ``` | верно | У бандлов есть встроенные умолчания (Extension); конфиг нужен только для отклонений от них. |
T23-L7 0.85 c | Symfony: configuration and services | Environment variable values are injected into services.yaml using the %env(VAR)% syntax. | «yes» Пояснение: In Symfony, environment variables are referenced in YAML configuration files using the %env(VAR)% syntax, e.g. %env(DATABASE_URL)%.
Raw{"answer": "yes", "explanation": "In Symfony, environment variables are referenced in YAML configuration files using the %env(VAR)% syntax, e.g. %env(DATABASE_URL)%."} | верно | %env(...)% резолвится в рантайме env-процессорами; docs — Env Var Processors. |
T23-L8 0.77 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, affecting the profiler and Twig debugging.
Raw{"answer": "APP_DEBUG", "explanation": "The APP_DEBUG environment variable in Symfony controls whether debug mode is enabled, affecting the profiler and Twig debugging."} | верно | APP_DEBUG=1 (в .env dev-окружения); окружение выбирает APP_ENV — см. T13-L6. |
T16-L1 1.09 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, and all of them will be invoked when the message is dispatched.
Raw{"answer": "no", "explanation": "Symfony Messenger allows multiple handlers to be registered for the same message, and all of them will be invoked when the message is dispatched."} | верно | Messenger вызывает все хендлеры, подписанные на класс сообщения (docs — Multiple Handlers). |
T16-L2 1.32 c | Symfony: Messenger | The sync transport in Messenger queues the message for a worker, just like async. | «no» Пояснение: The sync transport processes the message immediately in the same process by calling the handler directly, without queueing it for a worker.
Raw{"answer": "no", "explanation": "The sync transport processes the message immediately in the same process by calling the handler directly, without queueing it for a worker."} | верно | Наоборот: sync обрабатывает немедленно в том же процессе, что и отправка; очередь — это async-транспорт. |
T16-L3 0.67 c | Symfony: Messenger | Which console command starts the worker that processes Messenger queue messages? | «messenger:consume» Пояснение: In Symfony, the command `php bin/console messenger:consume` starts the worker that consumes and processes messages from the Messenger queue.
Raw{"answer": "messenger:consume", "explanation": "In Symfony, the command `php bin/console messenger:consume` starts the worker that consumes and processes messages from the Messenger queue."} | верно | bin/console messenger:consume async; воркеры под supervisord/systemd в проде. |
T16-L4 1.1 c | Symfony: Messenger | Retries for failed messages (retry_strategy) are configured per Messenger transport. | «yes» Пояснение: In Symfony Messenger, the retry_strategy (max_retries, delay, multiplier) is configured per transport in the framework configuration.
Raw{"answer": "yes", "explanation": "In Symfony Messenger, the retry_strategy (max_retries, delay, multiplier) is configured per transport in the framework configuration."} | верно | retry_strategy на транспорте: max_retries, delay, multiplier; docs — Failed Messages & Retries. |
T16-L5 1.41 c | Symfony: Messenger | By default, Messenger serializes messages to JSON. | «yes» Пояснение: Symfony Messenger uses the Symfony Serializer with JSON as the default serialization format.
Raw{"answer": "yes", "explanation": "Symfony Messenger uses the Symfony Serializer with JSON as the default serialization format."} | неверно верный: «no» | Дефолтный сериализатор — PhpSerializer (serialize()); JSON-сериализатор включается отдельно. |
T16-L6 4.19 c | Symfony: Messenger | Symfony Scheduler produces messages on a schedule and dispatches them through Messenger. | «yes» Пояснение: Symfony Scheduler is designed to define tasks on a schedule, and the typical pattern is to dispatch those tasks as messages through the Messenger component.
Raw```json ⏎ {"answer": "yes", "explanation": "Symfony Scheduler is designed to define tasks on a schedule, and the typical pattern is to dispatch those tasks as messages through the Messenger component."} ⏎ ``` | верно | Schedule → RecurringMessage → шина Messenger; docs — Scheduler. |
T16-L7 0.78 c | Symfony: Messenger | Which built-in Messenger transport stores messages in database tables via Doctrine? | «doctrine» Пояснение: The doctrine transport in Symfony Messenger persists messages in database tables using Doctrine DBAL.
Raw{"answer": "doctrine", "explanation": "The doctrine transport in Symfony Messenger persists messages in database tables using Doctrine DBAL."} | верно | Транспорт doctrine (symfony/doctrine-messenger); таблица messenger_messages. В проекте стоит amqp-messenger + doctrine-messenger. |
T16-L8 1.01 c | Symfony: Messenger | The Messenger pipeline can be extended with custom middleware, placed before or after the built-in ones. | «yes» Пояснение: Symfony Messenger allows you to add custom middleware and position them before, after, or at the end of the built-in middleware pipeline using the 'before', 'after', or 'append' options in the transport configuration.
Raw{"answer": "yes", "explanation": "Symfony Messenger allows you to add custom middleware and position them before, after, or at the end of the built-in middleware pipeline using the 'before', 'after', or 'append' options in the transport configuration."} | верно | messenger.bus.*.middleware в yaml; docs — Middleware. |
T28-L1 1.76 c | Symfony: versions | Symfony major releases come every two years, minor ones every six months (in May and November). | «no» Пояснение: Symfony major releases come every year (in November), while LTS versions come every two years; minor releases do come every six months in May and November.
Raw```json ⏎ {"answer": "no", "explanation": "Symfony major releases come every year (in November), while LTS versions come every two years; minor releases do come every six months in May and November."} ⏎ ``` | неверно верный: «yes» | Стандартный релизный цикл: 8.0 — ноябрь 2025, 8.1 — май 2026, 8.2 — ноябрь 2026. |
T28-L2 2.05 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, following the pattern of increasing the minimum PHP requirement with each major release.
Raw```json ⏎ {"answer": "8.4", "explanation": "Symfony 8 requires a minimum PHP version of 8.4, following the pattern of increasing the minimum PHP requirement with each major release."} ⏎ ``` | верно | Symfony 8.0 поднял требование до PHP >= 8.4.1 (в vendor проекта: "php": ">=8.4.1"). |
T28-L3 1.32 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; annotations were deprecated in 6.0 and removed in 7.0.
Raw{"answer": "no", "explanation": "Symfony 7.0 removed support for docblock annotations in favor of PHP 8 attributes; annotations were deprecated in 6.0 and removed in 7.0."} | верно | Наоборот: в 7.0 аннотации удалены — только PHP-атрибуты (#[Route], #[Assert\NotBlank]). |
T28-L4 1.19 c | Symfony: versions | AssetMapper manages CSS/JS without node or webpack — via importmap.php. | «yes» Пояснение: Symfony's AssetMapper manages CSS and JS assets using importmap.php without requiring Node.js or webpack.
Raw{"answer": "yes", "explanation": "Symfony's AssetMapper manages CSS and JS assets using importmap.php without requiring Node.js or webpack."} | верно | symfony/asset-mapper (с 6.3, стандарт с 7.x); в проекте — importmap.php в корне и asset-mapper 8.1. |
T28-L5 1.17 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, not a regular release without long-term support.
Raw{"answer": "no", "explanation": "Symfony 6.4 is a Long-Term Support (LTS) release, not a regular release without long-term support."} | верно | Наоборот: 6.4 — LTS (расширенная поддержка); LTS выходит вместе с очередным мажором (6.4 — вместе с 7.0). |
T28-L6 2.06 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» Пояснение: In Symfony's policy, features deprecated in a given version (e.g., 4.4) are typically removed in the next major version (e.g., 5.0), so major releases do remove deprecations from the previous branch.
Raw```json ⏎ {"answer": "no", "explanation": "In Symfony's policy, features deprecated in a given version (e.g., 4.4) are typically removed in the next major version (e.g., 5.0), so major releases do remove deprecations from the previous branch."} ⏎ ``` | верно | Наоборот: мажорный релиз удаляет всё устаревшее (7.0 убрал деприкейшены 6.x, 8.0 — 7.x). |
T28-L7 2.62 c | Symfony: versions | Every Symfony major release is accompanied by an UPGRADE guide listing the changes. | «yes» Пояснение: Symfony provides UPGRADE-*.md files (e.g., UPGRADE-5.0.md, UPGRADE-6.0.md) for each major release documenting the changes.
Raw{"answer": "yes", "explanation": "Symfony provides UPGRADE-*.md files (e.g., UPGRADE-5.0.md, UPGRADE-6.0.md) for each major release documenting the changes."} | верно | UPGRADE-7.0.md, UPGRADE-8.0.md в репозитории symfony/symfony. |
T28-L8 1.37 c | Symfony: versions | Which Symfony component manages assets and the importmap without node/webpack? | «assetmapper» Пояснение: Symfony's AssetMapper component (introduced in 6.4/7.0) manages frontend assets and importmaps without requiring Node.js or webpack.
Raw{"answer": "AssetMapper", "explanation": "Symfony's AssetMapper component (introduced in 6.4/7.0) manages frontend assets and importmaps without requiring Node.js or webpack."} | верно | symfony/asset-mapper 8.1 — в проекте. |
T29-L1 7.18 c | Symfony: 8.2 and beyond | As of 2026-11-07, Symfony 8.2 has already been released. | «no» Пояснение: Following Symfony's release cycle, Symfony 8.0 would be released around November 2026, meaning 8.2 would not come until mid-2027 at the earliest.
Raw```json ⏎ {"answer": "no", "explanation": "Following Symfony's release cycle, Symfony 8.0 would be released around November 2026, meaning 8.2 would not come until mid-2027 at the earliest."} ⏎ ``` | верно | Наоборот: 8.2 ещё не выпущена — релиз в конце ноября 2026; последняя стабильная — 8.1. |
T29-L2 6.51 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 scheduled for 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 scheduled for November 2026, not 8.2; 8.2 would be around November 2027."} ⏎ ``` | неверно верный: «yes» | Политика релизов: 8.1 — май 2026, 8.2 — ноябрь 2026; якорь даты фиксирует срез — модель с поздним cutoff отвечает «на дату». |
T29-L3 1.3 c | Symfony: 8.2 and beyond | Which Symfony version comes after 8.1 (as of 2026-11-07)? | «8.2» Пояснение: Symfony versions increment the minor number sequentially, so 8.2 follows 8.1.
Raw{"answer": "8.2", "explanation": "Symfony versions increment the minor number sequentially, so 8.2 follows 8.1."} | верно | 8.2 — следующий минорный релиз (ноябрь 2026); после его выхода проект переходит с 8.1.* на 8.2.*. |
T29-L4 2.17 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 is a minor release (the second digit), not a major one; minor releases are backward-compatible and do not require rewriting applications.
Raw{"answer": "no", "explanation": "Symfony 8.2 is a minor release (the second digit), not a major one; minor releases are backward-compatible and do not require rewriting applications."} | верно | Наоборот: 8.2 — минорный релиз; новые возможности без поломки обратной совместимости. Мажор — 9.0. |
T29-L5 1.31 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's backward compatibility promise guarantees that no code changes are needed when moving between minor versions within the same major version (e.g., 8.1 → 8.2).
Raw{"answer": "yes", "explanation": "PHP's backward compatibility promise guarantees that no code changes are needed when moving between minor versions within the same major version (e.g., 8.1 → 8.2)."} | верно | Политика Symfony: минорные релизы обратно совместимы; BC-break допустим только в мажорных. |
T29-L6 2.42 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 pattern where each major branch (4.x, 5.x, 6.x, 7.x) has minor versions up to .4, the 8.x branch would end at 8.4 before 9.0.
Raw{"answer": 8.4, "explanation": "Following Symfony's pattern where each major branch (4.x, 5.x, 6.x, 7.x) has minor versions up to .4, the 8.x branch would end at 8.4 before 9.0."} | верно | По циклу: 8.2 (ноя 2026), 8.3 (май 2027), 8.4 (ноя 2027, вместе с 9.0) — как 6.4 выходила вместе с 7.0. |
T29-L7 2.89 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 version numbers and PHP version numbers do not correspond; there is no established rule that Symfony 8.2 would specifically require PHP 8.5.
Raw{"answer": "no", "explanation": "Symfony version numbers and PHP version numbers do not correspond; there is no established rule that Symfony 8.2 would specifically require PHP 8.5."} | верно | Наоборот: минорные релизы не поднимают требования PHP; для всей ветки 8.x остаётся PHP >= 8.4. |
T29-L8 1.43 c | Symfony: 8.2 and beyond | Deprecations added in the 8.x branch will not be removed before Symfony 9.0. | «yes» Пояснение: Symfony's deprecation policy states that deprecations introduced in a major version (8.x) are removed in the next major version (9.0), so they will not be removed before 9.0.
Raw{"answer": "yes", "explanation": "Symfony's deprecation policy states that deprecations introduced in a major version (8.x) are removed in the next major version (9.0), so they will not be removed before 9.0."} | верно | Политика: деприкейшены живут до следующего мажора; 9.0 — ноябрь 2027. |
T21-L1 1.73 c | Twig | Inside {{ }}, Twig allows calling arbitrary PHP code directly. | «no» Пояснение: Inside {{ }} you can only use Twig's own expression language (variables, filters, operators, method calls via dot notation), not arbitrary PHP code.
Raw{"answer": "no", "explanation": "Inside {{ }} you can only use Twig's own expression language (variables, filters, operators, method calls via dot notation), not arbitrary PHP code."} | верно | Twig — DSL: только разрешённые окружением функции/фильтры; произвольный PHP не исполняется. |
T21-L2 0.94 c | Twig | By default, Twig auto-escapes printed variables. | «yes» Пояснение: Twig auto-escapes output by default using the HTML escaping strategy to prevent XSS attacks.
Raw{"answer": "yes", "explanation": "Twig auto-escapes output by default using the HTML escaping strategy to prevent XSS attacks."} | верно | Autoescape включён по умолчанию; {{ '<b>' }} → <b>. Проверено на Twig 3.30. |
T21-L3 0.84 c | Twig | The Twig |e filter escapes a string for safe output in an HTML context. | «yes» Пояснение: The Twig |e filter (alias for |escape) escapes a string for safe HTML output by default using htmlspecialchars with ENT_QUOTES.
Raw{"answer": "yes", "explanation": "The Twig |e filter (alias for |escape) escapes a string for safe HTML output by default using htmlspecialchars with ENT_QUOTES."} | верно | |e ('html') по умолчанию; есть контексты js/url/css. От SQL-инъекций он не защищает — это задача подготовленных запросов Doctrine. |
T21-L4 1.18 c | Twig | Which filter from twig/intl-extra formats a number according to a locale? | «locale_number_format» Пояснение: The twig/intl-extra package provides the locale_number_format filter, which formats a number according to a given locale using the ICU library.
Raw{"answer": "locale_number_format", "explanation": "The twig/intl-extra package provides the locale_number_format filter, which formats a number according to a given locale using the ICU library."} | неверно верный: «format_number» | |format_number(locale=...) из IntlExtension (twig/intl-extra есть в проекте). Проверено на Twig 3.30: 12345.6 → 12 345,6 (ru). |
T21-L5 1.24 c | Twig | The |raw filter disables auto-escaping for the value. | «yes» Пояснение: In Laravel Blade, the |raw filter (equivalent to using {!! !!}) outputs the value without applying htmlspecialchars, thus disabling auto-escaping.
Raw{"answer": "yes", "explanation": "In Laravel Blade, the |raw filter (equivalent to using {!! !!}) outputs the value without applying htmlspecialchars, thus disabling auto-escaping."} | верно | {{ x|raw }} выводит HTML как есть; опасно с пользовательскими данными. Проверено на Twig 3.30. |
T21-L6 1.12 c | Twig | In Twig, {{ }} prints an expression value, while {% %} executes tags — conditions, loops, set. | «yes» Пояснение: In Twig, double curly braces {{ }} are used to output/echo expression values, while percent braces {% %} are used for control structures like loops, conditions, and setting variables.
Raw{"answer": "yes", "explanation": "In Twig, double curly braces {{ }} are used to output/echo expression values, while percent braces {% %} are used for control structures like loops, conditions, and setting variables."} | верно | Два блока синтаксиса Twig: вывод (echo) против логики. |
T21-L7 0.72 c | Twig | In Twig you cannot declare a variable inside a template — values only come from the controller. | «no» Пояснение: Twig allows you to declare variables within a template using the {% set %} tag.
Raw{"answer": "no", "explanation": "Twig allows you to declare variables within a template using the {% set %} tag."} | верно | {% set y = ... %} объявляет переменную в шаблоне. Проверено на Twig 3.30. |
T21-L8 0.7 c | Twig | Which Twig function dumps the debug structure of a variable (array, object)? | «dump» Пояснение: Twig's dump() function outputs a debug structure of a variable, similar to PHP's var_dump().
Raw{"answer": "dump", "explanation": "Twig's dump() function outputs a debug structure of a variable, similar to PHP's var_dump()."} | верно | {{ dump(x) }} (DebugExtension; в Symfony доступна в dev-окружении). |
T24-L1 1.01 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 framework providing pre-built UI components (grid, modals, navbars, etc.), not an SPA framework like React, Angular, or Vue.
Raw{"answer": "yes", "explanation": "Bootstrap is a front-end CSS/JS framework providing pre-built UI components (grid, modals, navbars, etc.), not an SPA framework like React, Angular, or Vue."} | верно | Компоненты и утилиты поверх вашего HTML; SPA-фреймворки (React/Vue) — другой класс инструментов. В проекте vendored 5.3.3. |
T24-L2 0.9 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.21 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 Bootstrap 4+ uses Flexbox rather than CSS floats.
Raw{"answer": "no", "explanation": "The Bootstrap grid splits a row into 12 columns, not 16, and Bootstrap 4+ uses Flexbox rather than CSS floats."} | верно | Наоборот: flexbox (с Bootstrap 4) и 12 колонок; float-сетка — это Bootstrap 3. |
T24-L4 1.23 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 named breakpoints with class-name infixes: sm, md, lg, xl, and xxl.
Raw{"answer": "yes", "explanation": "Bootstrap 5 defines exactly five named breakpoints with class-name infixes: sm, md, lg, xl, and xxl."} | верно | Тиров всего шесть: xs (без инфикса) + пять именованных (576/768/992/1200/1400 px). |
T24-L5 3.65 c | Bootstrap | Utilities like .mt-3 or .px-2 use the spacing scale: the number is a multiple of $spacer. | «no» Пояснение: The spacing utilities use a predefined scale (e.g., .mt-1 = 0.25rem, .mt-2 = 0.5rem, .mt-3 = 1rem) that is not simply $spacer multiplied by the number; the formula in Bootstrap 4 is $spacer * $num / 4, so the values are not direct multiples of $spacer.
Raw{"answer": "no", "explanation": "The spacing utilities use a predefined scale (e.g., .mt-1 = 0.25rem, .mt-2 = 0.5rem, .mt-3 = 1rem) that is not simply $spacer multiplied by the number; the formula in Bootstrap 4 is $spacer * $num / 4, so the values are not direct multiples of $spacer."} | верно | Spacing utilities; $spacer = 1rem. |
T24-L6 0.94 c | Bootstrap | Which Bootstrap 5 data attribute enables an interactive component (e.g. dropdown) on an element? | «data-bs-toggle» Пояснение: In Bootstrap 5, data-bs-toggle is the attribute that enables interactive components such as dropdowns, tooltips, and popovers on an element.
Raw{"answer": "data-bs-toggle", "explanation": "In Bootstrap 5, data-bs-toggle is the attribute that enables interactive components such as dropdowns, tooltips, and popovers on an element."} | верно | data-bs-toggle="dropdown" и т.п.; в Bootstrap 4 атрибут назывался data-toggle. |
T24-L7 0.73 c | Bootstrap | Bootstrap 5 components work without jQuery — in plain vanilla JS. | «yes» Пояснение: Bootstrap 5 removed the jQuery dependency and all its interactive components (dropdowns, modals, tooltips, etc.) are built with plain vanilla JavaScript (ES6+).
Raw{"answer": "yes", "explanation": "Bootstrap 5 removed the jQuery dependency and all its interactive components (dropdowns, modals, tooltips, etc.) are built with plain vanilla JavaScript (ES6+)."} | верно | jQuery удалён в Bootstrap 5.0: data-bs-* атрибуты и JS API. В проекте vendored 5.3.3. |
T24-L8 1.07 c | Bootstrap | Dark mode in Bootstrap is enabled with a .dark class on the root element. | «no» Пояснение: In Bootstrap 5, dark mode is enabled with the data-bs-theme="dark" attribute on the root element, not a .dark class.
Raw{"answer":"no","explanation":"In Bootstrap 5, dark mode is enabled with the data-bs-theme=\"dark\" attribute on the root element, not a .dark class."} | верно | Наоборот: тема включается атрибутом data-bs-theme="dark" (Color modes, с 5.3); класса .dark не существует. В проекте 5.3.3. |
T14-L1 1.12 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 tools or migrations to create or update database tables.
Raw{"answer": "no", "explanation": "Doctrine ORM does not automatically create tables at runtime; you must explicitly run schema tools or migrations to create or update database tables."} | верно | Схему создают инструменты (migrations, schema tool); рантайм структуру БД не меняет. |
T14-L2 0.71 c | Doctrine | Which EntityManager method marks a new object as managed without executing SQL until flush()? | «persist» Пояснение: EntityManager::persist() marks a new entity as managed and schedules it for insertion, but no SQL is executed until flush() is called.
Raw{"answer": "persist", "explanation": "EntityManager::persist() marks a new entity as managed and schedules it for insertion, but no SQL is executed until flush() is called."} | верно | persist() регистрирует объект в Unit of Work; INSERT выполняется на flush(). |
T14-L3 1.73 c | Doctrine | In Doctrine ORM 3, the EntityManager::merge() method exists and makes the passed object managed. | «no» Пояснение: EntityManager::merge() returns a new managed copy of the detached entity; the originally passed object itself remains detached.
Raw```json ⏎ {"answer": "no", "explanation": "EntityManager::merge() returns a new managed copy of the detached entity; the originally passed object itself remains detached."} ⏎ ``` | верно | В ORM 3 merge() удалён (в vendor проекта 3.7.6 метода нет); в Doctrine 2.x merge() возвращал управляемую копию. Версия зафиксирована — ORM 3. |
T14-L4 1.08 c | Doctrine | DQL queries are written in terms of entities and their fields, not tables and columns. | «yes» Пояснение: DQL (Doctrine Query Language) operates at the entity level, referencing entity names and their fields rather than raw table and column names.
Raw{"answer": "yes", "explanation": "DQL (Doctrine Query Language) operates at the entity level, referencing entity names and their fields rather than raw table and column names."} | верно | Doctrine транслирует DQL в SQL; docs — DQL (Doctrine Query Language). |
T14-L5 1.03 c | Doctrine | What does $repository->find(999) return when no record with id 999 exists? | «null» Пояснение: In Doctrine ORM and most PHP repositories, the find() method returns null when no record with the given ID exists.
Raw{"answer": "null", "explanation": "In Doctrine ORM and most PHP repositories, the find() method returns null when no record with the given ID exists."} | верно | find() возвращает null, если объект не найден (docs Repository methods). |
T14-L6 1.29 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() yourself (the old auto_commit option was deprecated and removed).
Raw{"answer": "no", "explanation": "DoctrineBundle does not automatically call flush() at the end of a request; you must explicitly call $entityManager->flush() yourself (the old auto_commit option was deprecated and removed)."} | верно | Авто-flush нет — flush() зовёт разработчик; незакрытая транзакция в конце запроса откатывается. |
T14-L7 1.58 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 performs change detection on all managed entities at flush() time, so property modifications on managed entities are committed without needing an explicit persist() call.
Raw{"answer": "yes", "explanation": "The Unit of Work performs change detection on all managed entities at flush() time, so property modifications on managed entities are committed without needing an explicit persist() call."} | верно | Dirty checking сравнивает снимки свойств; persist нужен только новым/отсоединённым объектам. |
T14-L8 1.0 c | Doctrine | remove() executes the SQL DELETE immediately, without waiting for flush(). | «no» Пояснение: remove() only marks the entity as scheduled for deletion in the UnitOfWork; the actual SQL DELETE is executed when flush() is called.
Raw{"answer": "no", "explanation": "remove() only marks the entity as scheduled for deletion in the UnitOfWork; the actual SQL DELETE is executed when flush() is called."} | верно | remove() планирует удаление в Unit of Work; DELETE выполняется на flush() (docs — Deleting Objects). |
T15-L1 1.19 c | PostgreSQL | PostgreSQL uses MVCC, therefore readers block writers and writers block readers. | «no» Пояснение: MVCC's purpose is the opposite: readers do not block writers and writers do not block readers, as each transaction sees its own version of the data.
Raw{"answer": "no", "explanation": "MVCC's purpose is the opposite: readers do not block writers and writers do not block readers, as each transaction sees its own version of the data."} | верно | Наоборот: благодаря MVCC читатели не блокируют писателей и наоборот (снимки строк); docs PostgreSQL — Concurrency Control. |
T15-L2 0.82 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 running the query.
Raw{"answer": "EXPLAIN", "explanation": "The EXPLAIN command displays the query execution plan without actually running the query."} | верно | EXPLAIN без ANALYZE только строит план; проверено на PostgreSQL 17.7. |
T15-L3 3.07 c | PostgreSQL | SERIAL and GENERATED ... AS IDENTITY are just two names for the same mechanism. | «no» Пояснение: While both use sequences under the hood, SERIAL is a PostgreSQL-specific shorthand that creates a separate sequence object with ownership, whereas GENERATED AS IDENTITY is a SQL-standard column property with different management semantics (e.g., the sequence is tied to the column and dropped with it, supports GENERATED ALWAYS/BY DEFAULT, and is modified via ALTER COLUMN ... IDENTITY).
Raw{"answer":"no","explanation":"While both use sequences under the hood, SERIAL is a PostgreSQL-specific shorthand that creates a separate sequence object with ownership, whereas GENERATED AS IDENTITY is a SQL-standard column property with different management semantics (e.g., the sequence is tied to the column and dropped with it, supports GENERATED ALWAYS/BY DEFAULT, and is modified via ALTER COLUMN ... IDENTITY)."} | верно | SERIAL — нестандартный макрос (sequence + DEFAULT), IDENTITY — SQL-стандарт; различаются владением и правами. Оба есть в PG 17 (проверено). |
T15-L4 1.46 c | PostgreSQL | By default, a PostgreSQL UNIQUE constraint allows only one row with NULL in the column. | «no» Пояснение: In PostgreSQL, by default, a UNIQUE constraint treats NULLs as distinct from each other, allowing multiple rows with NULL in that column.
Raw```json ⏎ {"answer": "no", "explanation": "In PostgreSQL, by default, a UNIQUE constraint treats NULLs as distinct from each other, allowing multiple rows with NULL in that column."} ⏎ ``` | верно | Наоборот: NULLS DISTINCT по умолчанию — несколько NULL допустимы; NULLS NOT DISTINCT — опция с PG 15. Проверено на PG 17.7. |
T15-L5 0.41 c | PostgreSQL | Which PostgreSQL aggregate function concatenates strings with a separator? | «string_agg» Пояснение: STRING_AGG is the PostgreSQL aggregate function that concatenates strings with a specified separator.
Raw{"answer": "STRING_AGG", "explanation": "STRING_AGG is the PostgreSQL aggregate function that concatenates strings with a specified separator."} | верно | string_agg(значение, разделитель); проверено на PostgreSQL 17.7. |
T15-L6 1.35 c | PostgreSQL | Plain VACUUM returns the space occupied by dead tuples to the operating system. | «no» Пояснение: Plain VACUUM makes space reusable within the table but does not shrink the file; VACUUM FULL returns space to the operating system.
Raw{"answer": "no", "explanation": "Plain VACUUM makes space reusable within the table but does not shrink the file; VACUUM FULL returns space to the operating system."} | верно | VACUUM помечает место для переиспользования внутри таблицы; ОС его возвращает только VACUUM FULL (с эксклюзивной блокировкой). |
T15-L7 0.59 c | PostgreSQL | Which keyword in a window function definition partitions rows into groups the function is computed over? | «partition by» Пояснение: The PARTITION BY clause in a window function definition divides rows into groups over which the function is computed.
Raw{"answer": "PARTITION BY", "explanation": "The PARTITION BY clause in a window function definition divides rows into groups over which the function is computed."} | верно | OVER (PARTITION BY ...); проверено на PostgreSQL 17.7. |
T15-L8 1.13 c | PostgreSQL | The READ COMMITTED isolation level protects against non-repeatable reads. | «no» Пояснение: READ COMMITTED only protects against dirty reads; non-repeatable reads are protected at the REPEATABLE READ level or higher.
Raw{"answer":"no","explanation":"READ COMMITTED only protects against dirty reads; non-repeatable reads are protected at the REPEATABLE READ level or higher."} | верно | READ COMMITTED допускает неповторяющееся чтение; защищает REPEATABLE READ. Проверено: SHOW transaction_isolation → read committed. |
T17-L1 0.92 c | PostgreSQL: transactions and indexes | By default, PostgreSQL wraps each single SQL statement in its own implicit transaction (autocommit). | «yes» Пояснение: PostgreSQL defaults to autocommit mode, where each SQL statement is automatically committed upon completion unless an explicit transaction block (BEGIN/COMMIT) is used.
Raw{"answer": "yes", "explanation": "PostgreSQL defaults to autocommit mode, where each SQL statement is automatically committed upon completion unless an explicit transaction block (BEGIN/COMMIT) is used."} | верно | Без BEGIN каждый оператор коммитится сам; docs PostgreSQL — Transactions. Проверено на PG 17. |
T17-L2 0.45 c | PostgreSQL: transactions and indexes | Which SQL command ends a transaction, committing all its changes? | «commit» Пояснение: The COMMIT SQL command ends a transaction and permanently saves all changes made within it.
Raw{"answer": "COMMIT", "explanation": "The COMMIT SQL command ends a transaction and permanently saves all changes made within it."} | верно | COMMIT (END — синоним). Проверено на PG 17. |
T17-L3 1.06 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) whose WHERE clause references the indexed column.
Raw```json ⏎ {"answer": "yes", "explanation": "Indexes help locate rows quickly for any DML operation (SELECT, UPDATE, DELETE) whose WHERE clause references the indexed column."} ⏎ ``` | верно | Поиск строк для изменения идёт по индексу; 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 you to roll back to a specific point within a transaction without aborting the entire transaction.
Raw{"answer": "yes", "explanation": "SAVEPOINT allows you to roll back to a specific point within a transaction without aborting the entire transaction."} | верно | SAVEPOINT name; ROLLBACK TO name — частичный откат без отмены всей транзакции. Проверено на PG 17. |
T17-L5 0.89 c | PostgreSQL: transactions and indexes | EXPLAIN ANALYZE shows the query plan without executing the query. | «no» Пояснение: EXPLAIN ANALYZE actually executes the query to collect real timing and row-count statistics, unlike plain EXPLAIN which only shows the plan without execution.
Raw{"answer": "no", "explanation": "EXPLAIN ANALYZE actually executes the query to collect real timing and row-count statistics, unlike plain EXPLAIN which only shows the plan without execution."} | верно | Наоборот: ANALYZE реально выполняет запрос (с побочными эффектами!) и показывает фактические времена узлов; план без выполнения — plain EXPLAIN. |
T17-L6 0.69 c | PostgreSQL: transactions and indexes | Which PostgreSQL extension adds vector types and indexes for embedding search? | «pgvector» Пояснение: pgvector is the PostgreSQL extension that adds a vector data type and efficient indexing for similarity search on embeddings.
Raw{"answer": "pgvector", "explanation": "pgvector is the PostgreSQL extension that adds a vector data type and efficient indexing for similarity search on embeddings."} | верно | CREATE EXTENSION vector (проект pgvector; в проекте образ pgvector/pgvector:pg17). |
T17-L7 0.76 c | PostgreSQL: transactions and indexes | A partial index (CREATE INDEX ... WHERE ...) is built only over rows satisfying the condition. | «yes» Пояснение: A partial index (CREATE INDEX ... WHERE ...) in PostgreSQL is indeed built only over rows that satisfy the given condition.
Raw{"answer": "yes", "explanation": "A partial index (CREATE INDEX ... WHERE ...) in PostgreSQL is indeed built only over rows that satisfy the given condition."} | верно | docs PostgreSQL — Partial Indexes; типичный кейс — индекс по «активным» записям. |
T17-L8 2.04 c | PostgreSQL: transactions and indexes | The SERIALIZABLE level in PostgreSQL is implemented by locking the rows a transaction reads. | «no» Пояснение: PostgreSQL's SERIALIZABLE level uses Serializability Checking (SSI), an optimistic approach that detects conflicts at commit time, rather than locking all read rows (which is how SQL Server implements it).
Raw{"answer": "no", "explanation": "PostgreSQL's SERIALIZABLE level uses Serializability Checking (SSI), an optimistic approach that detects conflicts at commit time, rather than locking all read rows (which is how SQL Server implements it)."} | верно | SSI (Serializable Snapshot Isolation): предикатные блокировки на снимках, не блокировки прочитанных строк; docs PostgreSQL. |
T19-L1 0.62 c | HTTP and REST API | HTTP status 201 means the request resulted in a new resource being created. | «yes» Пояснение: HTTP 201 Created indicates that the request was successful and a new resource has been created as a result.
Raw{"answer": "yes", "explanation": "HTTP 201 Created indicates that the request was successful and a new resource has been created as a result."} | верно | 201 Created; обычно на POST, часто с Location; RFC 9110. |
T19-L2 0.93 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 used after DELETE operations.
Raw{"answer": 204, "explanation": "HTTP 204 No Content indicates a successful request with an empty response body, commonly used after DELETE operations."} | верно | 204 No Content; RFC 9110. |
T19-L3 3.15 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. | «no» Пояснение: Per RFC 7231/9110, DELETE is not listed among the idempotent methods (which are GET, HEAD, OPTIONS, PUT, TRACE); it is intentionally left open whether repeated DELETEs have the same effect.
Raw{"answer": "no", "explanation": "Per RFC 7231/9110, DELETE is not listed among the idempotent methods (which are GET, HEAD, OPTIONS, PUT, TRACE); it is intentionally left open whether repeated DELETEs have the same effect."} | неверно верный: «yes» | RFC 9110: DELETE идемпотентен (как PUT); идемпотентность ≠ безопасность — ресурс удаляется при первом вызове. |
T19-L4 1.1 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, not the client; the client sends the Origin header instead.
Raw{"answer": "no", "explanation": "The Access-Control-Allow-Origin header is sent by the server, not the client; the client sends the Origin header instead."} | верно | Наоборот: заголовок шлёт СЕРВЕР в ответе, разрешая браузеру cross-origin запрос (CORS); в проекте nelmio/cors-bundle. |
T19-L5 0.99 c | HTTP and REST API | Status 429 Too Many Requests is used when a client exceeds a rate limit. | «yes» Пояснение: HTTP status 429 Too Many Requests was defined in RFC 6585 specifically for rate limiting scenarios where a client has sent too many requests in a given time frame.
Raw{"answer": "yes", "explanation": "HTTP status 429 Too Many Requests was defined in RFC 6585 specifically for rate limiting scenarios where a client has sent too many requests in a given time frame."} | верно | 429 (+ Retry-After); RFC 6585. В проекте symfony/rate-limiter. |
T19-L6 0.91 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.42 c | HTTP and REST API | Which HTTP header indicates the MIME type of the request or response body? | «content-type» Пояснение: The Content-Type header specifies the MIME type of the request or response body.
Raw{"answer": "Content-Type", "explanation": "The Content-Type header specifies the MIME type of the request or response body."} | верно | Content-Type: application/json и т.п. |
T19-L8 1.21 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 by default, whereas PUT is idempotent per RFC 7231.
Raw{"answer": "yes", "explanation": "RFC 5789 explicitly states that PATCH is not idempotent by default, whereas PUT is idempotent per RFC 7231."} | верно | RFC 5789 прямо оговаривает: PATCH не гарантированно идемпотентен; PUT идемпотентен. |
T20-L1 1.28 c | Security and OAuth | Checking a password by comparing its hash to the stored hash with a plain == is sufficient. | «no» Пояснение: Using == for hash comparison is vulnerable to timing attacks; hash_equals() should be used instead as it performs a constant-time comparison.
Raw{"answer": "no", "explanation": "Using == for hash comparison is vulnerable to timing attacks; hash_equals() should be used instead as it performs a constant-time comparison."} | верно | Нужна постоянновременная проверка (password_verify) — timing-атаки; соль и алгоритм уже внутри хеша. |
T20-L2 1.13 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 and stored server-side (typically in the session), included in forms/requests, and validated by the server on state-changing (unsafe) requests like POST, PUT, DELETE.
Raw{"answer": "yes", "explanation": "CSRF tokens are generated and stored server-side (typically in the session), included in forms/requests, and validated by the server on state-changing (unsafe) requests like POST, PUT, DELETE."} | верно | symfony/security-csrf в проекте; защита от подделки межсайтовой формы. |
T20-L3 0.6 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 declare which resources are allowed to load and execute on a web page.
Raw{"answer": "Content-Security-Policy", "explanation": "The Content-Security-Policy HTTP header is used to declare which resources are allowed to load and execute on a web page."} | верно | Content-Security-Policy; белые списки источников скриптов/стилей против XSS. |
T20-L4 1.59 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 protocol (granting access to resources), not an authentication protocol; authentication is added by OpenID Connect via the ID token.
Raw```json ⏎ {"answer": "no", "explanation": "OAuth 2.0 is an authorization protocol (granting access to resources), not an authentication protocol; authentication is added by OpenID Connect via the ID token."} ⏎ ``` | верно | OAuth 2.0 — авторизация/делегирование доступа; аутентификацию добавляет OpenID Connect. В проекте knpuniversity/oauth2-client-bundle (yandex/github/google). |
T20-L5 2.07 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 encoding/escaping output when rendering it in HTML (e.g., htmlspecialchars), not by validating input before storing it in the database.
Raw```json ⏎ {"answer": "no", "explanation": "XSS is primarily prevented by encoding/escaping output when rendering it in HTML (e.g., htmlspecialchars), not by validating input before storing it in the database."} ⏎ ``` | верно | XSS лечится контекстным экранированием НА ВЫВОДЕ (Twig autoescape, CSP); валидация ввода не покрывает все контексты вывода. |
T20-L6 0.87 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 'code' parameter is returned to the redirect_uri and then exchanged for an access token at the token endpoint.
Raw{"answer": "code", "explanation": "In the OAuth 2.0 authorization code flow, the 'code' parameter is returned to the redirect_uri and then exchanged for an access token at the token endpoint."} | верно | Параметр code; обмен на токен POST-ом на /token с client_secret. |
T20-L7 0.7 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 enable users to obtain new access tokens without re-authenticating.
Raw{"answer": "yes", "explanation": "Refresh tokens are designed to outlive access tokens and enable users to obtain new access tokens without re-authenticating."} | верно | Стандартная схема OAuth/OIDC: короткий access + длинный refresh. |
T20-L8 1.53 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 (e.g., in a database). Its purpose is to ensure identical passwords produce different hashes, defeating precomputed rainbow tables, not to add secrecy.
Raw{"answer": "no", "explanation": "A salt does not need to be secret; it is typically stored alongside the hash (e.g., in a database). Its purpose is to ensure identical passwords produce different hashes, defeating precomputed rainbow tables, not to add secrecy."} | верно | Соль хранится открыто (password_hash включает её в строку хеша); секретность соли не нужна. |
T18-L1 1.36 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 in order to recognize and execute their test methods.
Raw{"answer": "no", "explanation": "PHPUnit requires test classes to extend PHPUnit\\Framework\\TestCase in order to recognize and execute their test methods."} | верно | Тестом считается метод класса, наследующего TestCase (PHPUnit 10). |
T18-L2 0.89 c | Testing: PHPUnit | In PHPUnit, setUp() runs once before all tests of the class. | «no» Пояснение: setUp() runs before each test method; setUpBeforeClass() is the one that runs once before all tests in the class.
Raw{"answer": "no", "explanation": "setUp() runs before each test method; setUpBeforeClass() is the one that runs once before all tests in the class."} | верно | setUp() — перед КАЖДЫМ тестом; один раз на класс — setUpBeforeClass(). Проверено живым счётчиком на PHPUnit 10.5. |
T18-L3 0.87 c | Testing: PHPUnit | A data provider lets a test run with exactly one set of arguments. | «no» Пояснение: A data provider allows a test to run with multiple sets of arguments, not just one.
Raw{"answer": "no", "explanation": "A data provider allows a test to run with multiple sets of arguments, not just one."} | верно | Наоборот: наборов может быть сколько угодно — тест выполняется по разу на каждый. Проверено на PHPUnit 10.5 (#[DataProvider]). |
T18-L4 0.65 c | Testing: PHPUnit | Which PHPUnit method declares an expectation that an exception of a given class is thrown? | «expectexception» Пояснение: PHPUnit's expectException() method declares an expectation that an exception of the given class will be thrown during the test.
Raw{"answer": "expectException", "explanation": "PHPUnit's expectException() method declares an expectation that an exception of the given class will be thrown during the test."} | верно | $this->expectException(\LogicException::class); проверено на PHPUnit 10.5. |
T18-L5 1.28 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 only returns pre-programmed data, while a mock also verifies that certain methods were called with expected arguments.
Raw{"answer": "no", "explanation": "It's the opposite: a stub only returns pre-programmed data, while a mock also verifies that certain methods were called with expected arguments."} | верно | Наоборот: стаб подставляет данные, мок проверяет взаимодействия (createStub/createMock); docs PHPUnit — Test Doubles. |
T18-L6 0.81 c | Testing: PHPUnit | In PHPUnit 10+, the recommended way to pass data to a test is the #[DataProvider] attribute (the @dataProvider annotation is deprecated). | «yes» Пояснение: PHPUnit 10+ recommends using the #[DataProvider] PHP attribute over the deprecated @dataProvider docblock annotation.
Raw{"answer": "yes", "explanation": "PHPUnit 10+ recommends using the #[DataProvider] PHP attribute over the deprecated @dataProvider docblock annotation."} | верно | Аннотация ещё парсится в PHPUnit 10/11 (AnnotationParser в 10.5.66), удаление — в 12; атрибут — стандарт. |
T18-L7 1.0 c | Testing: PHPUnit | PHPUnit does not allow one test to depend on the result of another. | «no» Пояснение: PHPUnit supports test dependencies via the @depends annotation (or #[Depends] attribute in PHPUnit 10+), allowing a test to receive and use the result of another test.
Raw{"answer": "no", "explanation": "PHPUnit supports test dependencies via the @depends annotation (or #[Depends] attribute in PHPUnit 10+), allowing a test to receive and use the result of another test."} | верно | Зависимости есть: #[Depends] — зависимый тест не запустится, еслиProducer упал. |
T18-L8 1.07 c | Testing: PHPUnit | Which PHPUnit command-line option makes tests run in random order? | «--order-by=random» Пояснение: PHPUnit's --order-by=random flag shuffles the test execution order to help identify order-dependent tests.
Raw{"answer": "--order-by=random", "explanation": "PHPUnit's --order-by=random flag shuffles the test execution order to help identify order-dependent tests."} | верно | --order-by=random (PHPUnit 9+); опция есть в --help PHPUnit 10.5 (проектная). |
T01-L9 3.89 c | Syntax and operators | What does this code output?
```php
echo intdiv(7, 2) . intdiv(-7, 2);
``` | «3-3» Пояснение: intdiv(7,2) returns 3 and intdiv(-7,2) returns -3 (truncation toward zero), concatenated as string '3-3'.
Raw{"answer": "3-3", "explanation": "intdiv(7,2) returns 3 and intdiv(-7,2) returns -3 (truncation toward zero), concatenated as string '3-3'."} | верно | intdiv truncates toward zero: intdiv(-7, 2) = -3, not -4. |
T01-L10 0.87 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 evaluated as -(3 ** 2) = -9.
Raw{"answer": -9, "explanation": "In PHP, the exponentiation operator ** has higher precedence than the unary minus, so -3 ** 2 is evaluated as -(3 ** 2) = -9."} | верно | ** is right-associative and binds tighter than unary minus: -(3²). |
T02-L9 0.92 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 numerically: 10 == 10 is true.
Raw{"answer": "true", "explanation": "Both '1e1' and '10' are numeric strings, so PHP compares them numerically: 10 == 10 is true."} | верно | Both strings are numeric — compared as numbers: 10 == 10. |
T02-L10 2.57 c | Types and comparisons | What does this code output?
```php
switch ('a') {
case 0: echo 'zero'; break;
default: echo 'other';
}
``` | «other» Пояснение: In PHP 8+, comparing the string 'a' with integer 0 casts the integer to a string ('a' == '0'), which is false, so the default case is reached.
Raw{"answer": "other", "explanation": "In PHP 8+, comparing the string 'a' with integer 0 casts the integer to a string ('a' == '0'), which is false, so the default case is reached."} | верно | PHP 8: 'a' == 0 → false (used to be true) — default fires. |
T03-L9 1.83 c | Strings | What does this code output?
```php
echo strtr('abc', ['a' => '1', 'ab' => '2']);
``` | «2c» Пояснение: strtr with an array replaces longest keys first: 'ab' (length 2) matches before 'a' (length 1), so 'ab'→'2' is applied to 'abc' yielding '2c'.
Raw{"answer": "2c", "explanation": "strtr with an array replaces longest keys first: 'ab' (length 2) matches before 'a' (length 1), so 'ab'→'2' is applied to 'abc' yielding '2c'."} | верно | strtr with an array prefers the longest matching key. |
T03-L10 2.13 c | Strings | What does this code output?
```php
echo '[' . substr('hello', -10) . ']';
``` | «[]» Пояснение: substr('hello', -10) with start -10 exceeds the string length of 5, so in PHP 7.1+ it returns an empty string, giving output '[]'.
Raw{"answer": "[]", "explanation": "substr('hello', -10) with start -10 exceeds the string length of 5, so in PHP 7.1+ it returns an empty string, giving output '[]'."} | неверно верный: «[hello]» | A negative start beyond the string is clamped to the beginning. |
T04-L9 1.61 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 union operator (+) keeps keys from the left array and adds non-duplicate keys from the right, resulting in keys k, n, m.
Raw{"answer": "k,n,m", "explanation": "The union operator (+) keeps keys from the left array and adds non-duplicate keys from the right, resulting in keys k, n, m."} | верно | The + operator: on duplicate string keys the left array wins. |
T04-L10 2.22 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 ascending (1,2,2), then array_column extracts index 1 giving 'y','x','z', which implode concatenates to 'yxz'.
Raw```json ⏎ {"answer": "yxz", "explanation": "usort sorts by the third element ascending (1,2,2), then array_column extracts index 1 giving 'y','x','z', which implode concatenates to 'yxz'."} ⏎ ``` | верно | Sorts are stable since 8.0: x and z keep their order on a tie. |
T05-L10 4.04 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 splat operator with an associative array expands to named arguments, so $a=5 and $b=1, giving 5-1=4.
Raw{"answer": 4, "explanation": "The splat operator with an associative array expands to named arguments, so $a=5 and $b=1, giving 5-1=4."} | верно | String keys of a spread array become named arguments. |
T05-L9 2.22 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 $p->g(...) captures the object reference at creation time, so setting $p = null does not affect the closure; it still calls g() on the original object and returns 3.
Raw{"answer": 3, "explanation": "The first-class callable $p->g(...) captures the object reference at creation time, so setting $p = null does not affect the closure; it still calls g() on the original object and returns 3."} | верно | First-class callable syntax binds $this at creation time. |
T06-L9 1.0 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 uses late static binding, returning the name of the class that was actually instantiated (B), not the class where the method is defined (A).
Raw{"answer": "B", "explanation": "static::class uses late static binding, returning the name of the class that was actually instantiated (B), not the class where the method is defined (A)."} | верно | Late static binding: static::class is the receiver's class. |
T06-L10 2.8 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 hook assigns $value * 2 directly to storage (without re-triggering itself), so the property holds 10.
Raw{"answer": 10, "explanation": "The set hook assigns $value * 2 directly to storage (without re-triggering itself), so the property holds 10."} | верно | Inside the set hook, $this->x writes the backing store (no recursion): 5*2. |
T07-L9 1.3 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 TA's f() as 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 TA's f() as g() returning 'A', so the concatenation is 'BA'."} ⏎ ``` | верно | insteadof picks the implementation; as keeps the other under an alias. |
T07-L10 1.75 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 static properties, so modifying CX::$n does not affect CY::$n.
Raw```json ⏎ {"answer": 0, "explanation": "Each class that uses a trait gets its own independent copy of the static properties, so modifying CX::$n does not affect CY::$n."} ⏎ ``` | верно | A trait's static property is copied into each consuming class. |
T08-L10 1.0 c | Exceptions and errors | What does this code output?
```php
function f(): int
{
try { return 1; } finally { return 2; }
}
echo f();
``` | «2» Пояснение: A return statement in a finally block overrides the return in the try block, so the function returns 2.
Raw{"answer": 2, "explanation": "A return statement in a finally block overrides the return in the try block, so the function returns 2."} | верно | A return in finally overrides the return from try. |
T08-L9 1.39 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» Пояснение: When a new exception is thrown in a finally block, it replaces the original exception being propagated, so the LogicException('second') is caught by the outer catch.
Raw{"answer":"second","explanation":"When a new exception is thrown in a finally block, it replaces the original exception being propagated, so the LogicException('second') is caught by the outer catch."} | верно | An exception from finally replaces the in-flight one — the last thrown is caught. |
T09-L9 1.46 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 the aliased class App\Foo, while \Baz::class resolves to the global Baz class name as a string.
Raw```json ⏎ {"answer": "App\\Foo|Baz", "explanation": "Baz::class resolves to the aliased class App\\Foo, while \\Baz::class resolves to the global Baz class name as a string."} ⏎ ``` | верно | The use alias applies to unqualified names; a leading \ escapes to the global scope. |
T09-L10 1.84 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 for a global class 'Foo' which doesn't exist (returns 'no'), while class_exists('Ns\Foo') finds the class defined in the Ns namespace (returns 'yes').
Raw{"answer": "noyes", "explanation": "class_exists('Foo') looks for a global class 'Foo' which doesn't exist (returns 'no'), while class_exists('Ns\\Foo') finds the class defined in the Ns namespace (returns 'yes')."} | верно | Dynamic names are not resolved against the namespace — 'Foo' is the global class. |
T10-L9 1.24 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 a foreach by reference, $v still holds a reference to the last element, so assigning 99 to $v changes the last element of the array.
Raw{"answer": "1,2,99", "explanation": "After a foreach by reference, $v still holds a reference to the last element, so assigning 99 to $v changes the last element of the array."} | верно | After a by-ref foreach, $v remains a reference to the last element. |
T10-L10 2.02 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 per-class; since B inherits inc() from A, all instances share the same static $n, which increments to 1, 2, 3 across the three calls.
Raw```php ⏎ {"answer": 3, "explanation": "Static variables in methods are shared per-class; since B inherits inc() from A, all instances share the same static $n, which increments to 1, 2, 3 across the three calls."} ⏎ ``` | верно | A method's static variable belongs to the parent's method — subclasses share it. |
T11-L9 5.98 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();
``` | «—» Пояснение: After send(10), the generator is still suspended at the yield point and not finished, so getReturn() returns null, which echoes as an empty string.
Raw```json ⏎ {"answer": "", "explanation": "After send(10), the generator is still suspended at the yield point and not finished, so getReturn() returns null, which echoes as an empty string."} ⏎ ``` | неверно верный: «11» | send() resumes the generator: $x = 10, return 10+1. |
T11-L10 2.36 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, then 2, then returns 'ok' which is assigned to $r and yielded by outer(), so the sequence is 1, 2, 'ok'.
Raw```json ⏎ {"answer": "1,2,ok", "explanation": "yield from delegates to inner() which yields 1, then 2, then returns 'ok' which is assigned to $r and yielded by outer(), so the sequence is 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.81 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» Пояснение: password_needs_rehash returns false (no) when cost matches (4=4) and true (yes) when cost differs (4≠5).
Raw{"answer": "noyes", "explanation": "password_needs_rehash returns false (no) when cost matches (4=4) and true (yes) when cost differs (4≠5)."} | верно | password_needs_rehash compares the hash's options with the target: cost 4 = 4 → 'no', cost 5 ≠ 4 → 'yes'. |
T12-L10 4.36 c | Configuration and security | What does this code output on PHP 8.5?
```php
echo (E_ALL & 2048) === 0 ? 'strict-out' : 'strict-in';
``` | «strict-out» Пояснение: Since PHP 8.0, E_ALL no longer includes the E_STRICT bit (2048), so E_ALL & 2048 equals 0, making the condition true.
Raw```json ⏎ {"answer": "strict-out", "explanation": "Since PHP 8.0, E_ALL no longer includes the E_STRICT bit (2048), so E_ALL & 2048 equals 0, making the condition true."} ⏎ ``` | верно | 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 2.65 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 Request extracts HTTP_X_TOKEN from server variables into the headers bag as X-Token, so get('X-Token') returns 'abc'.
Raw```json ⏎ {"answer": "mapped", "explanation": "Symfony's Request extracts HTTP_X_TOKEN from server variables into the headers bag as X-Token, so get('X-Token') returns 'abc'."} ⏎ ``` | верно | 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.3 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» Пояснение: Listeners are called in descending priority order: priority 10 (B), priority 5 (C), priority 0 (A).
Raw```json ⏎ {"answer": "BCA", "explanation": "Listeners are called in descending priority order: priority 10 (B), priority 5 (C), priority 0 (A)."} ⏎ ``` | верно | Listeners run by descending priority: 10 (B), 5 (C), 0 (A). |
T14-L10 2.0 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's find() checks the identity map first, so the second call returns the exact same object instance already in memory.
Raw{"answer": "same", "explanation": "Doctrine's find() checks the identity map first, so the second call returns the exact same object instance already in memory."} | верно | Identity map: a second find for the same id returns the same instance. |
T14-L9 6.83 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» Пояснение: When an entity is persisted and then removed before flush, Doctrine removes it from the insert schedule (since it was never in the DB, no DELETE is issued either), so no row is created.
Raw```json ⏎ {"answer": 0, "explanation": "When an entity is persisted and then removed before flush, Doctrine removes it from the insert schedule (since it was never in the DB, no DELETE is issued either), so no row is created."} ⏎ ``` | верно | The unit of work schedules INSERT at flush: remove after persist cancels it. |
T15-L10 1.09 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, so it returns 1 (excluding the NULL row).
Raw{"answer": 1, "explanation": "COUNT(x) counts only non-NULL values in column x, so it returns 1 (excluding the NULL row)."} | верно | count(column) skips NULLs; count(*) would return 2. |
T15-L9 1.54 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 totals 10, 30, 60, and string_agg concatenates them with commas in id order.
Raw{"answer": "10,30,60", "explanation": "The window function sum(x) OVER (ORDER BY id) produces running totals 10, 30, 60, and string_agg concatenates them with commas in id order."} | верно | With ORDER BY the default window frame is running (start to current row). |
T16-L9 1.61 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» Пояснение: Symfony Messenger middleware executes in order (M1 first, then M2), each echoing its tag before passing to the next in the stack.
Raw{"answer": "M1M2", "explanation": "Symfony Messenger middleware executes in order (M1 first, then M2), each echoing its tag before passing to the next in the stack."} | верно | The first-added middleware runs first (outermost). |
T16-L10 3.93 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;
``` | «1» Пояснение: HandleMessageMiddleware only invokes the first handler in the array for the given message class, so only d1 (which adds 1) is called.
Raw```json ⏎ {"answer": 1, "explanation": "HandleMessageMiddleware only invokes the first handler in the array for the given message class, so only d1 (which adds 1) is called."} ⏎ ``` | неверно верный: «11» | All registered handlers of the message run: 1 + 10 = 11. |
T17-L9 1.35 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 with ON CONFLICT DO NOTHING, leaving exactly 1 row.
Raw```json ⏎ {"answer": 1, "explanation": "The first INSERT succeeds, the second is skipped due to the unique constraint with ON CONFLICT DO NOTHING, leaving exactly 1 row."} ⏎ ``` | верно | ON CONFLICT DO NOTHING skips the duplicate: one insert. |
T17-L10 1.74 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» Пояснение: With DEFERRABLE INITIALLY DEFERRED, the unique constraint is only checked at COMMIT, so both INSERTs succeed within the transaction, giving a count of 2.
Raw```json ⏎ {"answer": 2, "explanation": "With DEFERRABLE INITIALLY DEFERRED, the unique constraint is only checked at COMMIT, so both INSERTs succeed within the transaction, giving a count of 2."} ⏎ ``` | верно | DEFERRED postpones the uniqueness check to COMMIT — count sees 2 rows. |
T18-L9 1.67 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 (3 data sets) and test_sum_abs (3 data sets) as it's a regex substring match, totaling 6 tests.
Raw```json ⏎ {"answer": 6, "explanation": "The --filter test_sum matches both test_sum (3 data sets) and test_sum_abs (3 data sets) as it's a regex substring match, totaling 6 tests."} ⏎ ``` | верно | --filter is a substring match: test_sum also matches test_sum_abs (3+3 datasets). |
T18-L10 1.38 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]); the test passes for x=1 but fails for x=-1 since -1 > 0 is false.
Raw{"answer": "2, 1", "explanation": "The data provider supplies two datasets ([1] and [-1]); the test passes for x=1 but fails for x=-1 since -1 > 0 is false."} | верно | A non-static provider is just a deprecation in PHPUnit 10: both datasets run and the [-1] dataset fails the assert — 2 ran, 1 failure. |
T19-L9 0.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 causes it to send data in the request body, which automatically sets the HTTP method to POST.
Raw{"answer": "POST", "explanation": "The -d flag in curl causes it to send data in the request body, which automatically sets the HTTP method to POST."} | верно | -d/-F switches curl to POST by default. |
T19-L10 1.32 c | HTTP and REST API | Which HTTP method does this command send?
```bash
curl -s -G -d 'a=1' http://demo.local/api
``` | «get» Пояснение: The -G flag forces curl to use the GET method, appending the -d data as a query string to the URL.
Raw{"answer": "GET", "explanation": "The -G flag forces curl to use the GET method, appending the -d data as a query string to the URL."} | верно | -G turns -d data into the query string; the method stays GET. |
T20-L9 1.72 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? | «unauthorized_client» Пояснение: Per RFC 6749 Section 5.2, when the client is not recognized or not authorized, the token endpoint returns the error value 'unauthorized_client'.
Raw{"answer": "unauthorized_client", "explanation": "Per RFC 6749 Section 5.2, when the client is not recognized or not authorized, the token endpoint returns the error value 'unauthorized_client'."} | неверно верный: «invalid_client» | Unknown client → invalid_client (RFC 6749 §5.2). |
T20-L10 0.96 c | Security and OAuth | OAuth 2.0: the client started the flow with response_type=token. In which part of the redirect_uri does the authorization server pass the access_token? | «fragment» Пояснение: In the implicit flow (response_type=token), the access token is returned in the fragment part of the redirect_uri (after #), not in the query string.
Raw{"answer": "fragment", "explanation": "In the implicit flow (response_type=token), the access token is returned in the fragment part of the redirect_uri (after #), not in the query string."} | верно | The implicit flow passes the token in the URL fragment (#) — it never reaches the server. |
T21-L9 1.26 c | Twig | What does this Twig template output?
```twig
{{ false|default(2) * 3 }}
``` | «0» Пояснение: The default filter only replaces null/undefined values, so false|default(2) returns false, and false * 3 evaluates to 0 in Twig/PHP.
Raw{"answer": 0, "explanation": "The default filter only replaces null/undefined values, so false|default(2) returns false, and false * 3 evaluates to 0 in Twig/PHP."} | неверно верный: «6» | default replaces exactly false/null/''/[] — false becomes 2, 2*3 = 6; the naive 'default is for undefined only' yields 0. |
T21-L10 1.01 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 1+2 is evaluated first to give 3, then 'a' is concatenated with 3 to produce 'a3'.
Raw{"answer": "a3", "explanation": "In Twig, the + operator has higher precedence than ~, so 1+2 is evaluated first to give 3, then 'a' is concatenated with 3 to produce 'a3'."} | неверно верный: «runtimeerror» | In Twig ~ binds tighter than +: ('a' ~ 1) + 2 → string + int → a render error (RuntimeError). |
T22-L9 8.12 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» Пояснение: The value [''] is an array (not null, not scalar, and (string)[''] casts to 'Array' which is not empty after trim), so NotBlank passes with no violations.
Raw```json ⏎ {"answer": 0, "explanation": "The value [''] is an array (not null, not scalar, and (string)[''] casts to 'Array' which is not empty after trim), so NotBlank passes with no violations."} ⏎ ``` | верно | NotBlank treats null, '', [] as blank — the array [''] is not blank. |
T22-L10 3.83 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);
}
``` | «valid» Пояснение: Calling isValid() on an unsubmitted form triggers submit(null), and a TextType form with no validation constraints is valid with null data.
Raw```json ⏎ {"answer": "valid", "explanation": "Calling isValid() on an unsubmitted form triggers submit(null), and a TextType form with no validation constraints is valid with null data."} ⏎ ``` | неверно верный: «symfony\component\form\exception\logicexception» | isValid() on a non-submitted form throws LogicException, it does not return false. |
T23-L9 1.6 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» Пояснение: Symfony's DI container caches service instances by default (singleton pattern), so calling get('a') twice returns the same object.
Raw```json ⏎ {"answer": "same", "explanation": "Symfony's DI container caches service instances by default (singleton pattern), so calling get('a') twice returns the same object."} ⏎ ``` | верно | Container services are shared: two get() calls yield one instance. |
T23-L10 1.53 c | Symfony: configuration and services | What does this code output?
```php
use Symfony\Component\DependencyInjection\ContainerBuilder;
$c = new ContainerBuilder();
$c->setParameter('name', 'Bob');
$c->setParameter('greeting', 'hi %name%');
$c->setParameter('message', '%greeting%!');
$c->compile();
echo $c->getParameter('message');
``` | «hi bob!» Пояснение: Symfony's container resolves nested parameter references during compile, so %greeting% expands to 'hi %name%' which further expands to 'hi Bob', giving 'hi Bob!'.
Raw```json ⏎ {"answer": "hi Bob!", "explanation": "Symfony's container resolves nested parameter references during compile, so %greeting% expands to 'hi %name%' which further expands to 'hi Bob', giving 'hi Bob!'."} ⏎ ``` | верно | compile() resolves %-references transitively: %greeting% → 'hi %name%' → 'hi Bob!', the answer assembles over two hops. |
T24-L9 1.13 c | Bootstrap | What is the max-width of .container in Bootstrap 5.3 at a 992px viewport? | «960» Пояснение: At a 992px viewport, the lg breakpoint (≥992px) applies, which sets .container max-width to 960px in Bootstrap 5.3.
Raw{"answer": 960, "explanation": "At a 992px viewport, the lg breakpoint (≥992px) applies, which sets .container max-width to 960px in Bootstrap 5.3."} | верно | 5.x container widths: 540/720/960/1140/1320 (sm–xxl); 992 → 960px. |
T24-L10 6.64 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 generated CSS, .text-danger appears after .text-primary (following the $theme-colors map order: primary, secondary, success, danger, warning, info), so with equal specificity, .text-danger wins.
Raw```json ⏎ {"answer": "text-danger", "explanation": "In Bootstrap 5.3's generated CSS, .text-danger appears after .text-primary (following the $theme-colors map order: primary, secondary, success, danger, warning, info), so with equal specificity, .text-danger wins."} ⏎ ``` | верно | Specificity ties — the later rule wins: text-danger is declared after text-primary. |
T25-L9 1.58 c | Clean architecture | Layers: Domain, Application, Infrastructure. Deptrac rules: Application → Domain; Infrastructure → Domain, Application; Domain → Domain only.
How many violations will deptrac report for this class?
```php
namespace App\Domain;
use App\Application\PlaceOrder;
use App\Infrastructure\Db;
class OrderService
{
public function __construct(
private PlaceOrder $handler,
private Db $db,
) {}
}
``` | «2» Пояснение: The class is in the Domain layer, which may only depend on Domain, but it depends on Application (PlaceOrder) and Infrastructure (Db), giving 2 violations.
Raw```json ⏎ {"answer": 2, "explanation": "The class is in the Domain layer, which may only depend on Domain, but it depends on Application (PlaceOrder) and Infrastructure (Db), giving 2 violations."} ⏎ ``` | верно | Domain may depend only on Domain: PlaceOrder (Application) + Db (Infrastructure) = 2. |
T25-L10 1.47 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» Пояснение: Domain can only depend on Domain, but BillingService (Domain) depends on Application\PlaceOrder, Infrastructure\Db, and Infrastructure\Logger — three violations.
Raw```json ⏎ {"answer": 3, "explanation": "Domain can only depend on Domain, but BillingService (Domain) depends on Application\\PlaceOrder, Infrastructure\\Db, and Infrastructure\\Logger — three violations."} ⏎ ``` | верно | The inline FQCN \App\Infrastructure\Logger counts too: Application + Db + Logger = 3. |
T26-L10 1.44 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 created by adding 10+5=15, so the echo outputs '10,15'.
Raw{"answer": "10,15", "explanation": "$a has amount 10, and $c is a new Money object created by adding 10+5=15, so the echo outputs '10,15'."} | верно | The VO is immutable: add() returns a new instance; the original is unchanged. |
T26-L9 1.21 c | DDD | What does this code output?
```php
final class Order
{
private array $items = [];
public function add(string $sku): void
{
$this->items[$sku] = true;
}
public function count(): int
{
return count($this->items);
}
public function remove(string $sku): void
{
if (count($this->items) === 1) {
throw new DomainException('last item');
}
unset($this->items[$sku]);
}
}
$o = new Order;
$o->add('a');
try {
$o->remove('a');
} catch (DomainException) {
}
echo $o->count();
``` | «1» Пояснение: The remove() method throws a DomainException when count is 1, before calling unset(), so the item 'a' is never removed and count() still returns 1.
Raw{"answer": 1, "explanation": "The remove() method throws a DomainException when count is 1, before calling unset(), so the item 'a' is never removed and count() still returns 1."} | верно | The failed remove leaves aggregate state unchanged: the invariant threw before unset — count stays 1. |
VC-L9 4.11 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 and calls hi() which returns the string 'hi', which is then echoed.
Raw{"answer": "hi", "explanation": "The code instantiates class C and calls hi() which returns the string 'hi', which is then echoed."} | верно | Since 8.4, new in a method chain works without wrapping parentheses. |
VC-L10 4.97 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» Пояснение: The lazy ghost is uninitialized before property access (prints 'yes'), then accessing $o->v triggers initialization and materializes the object (prints 'no').
Raw{"answer": "yesno", "explanation": "The lazy ghost is uninitialized before property access (prints 'yes'), then accessing $o->v triggers initialization and materializes the object (prints 'no')."} | верно | newLazyGhost (8.4): the object stays lazy until first access — reading a property initializes it and clears the flag. |
T28-L9 0.84 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 Guard authentication system was removed in Symfony 6.0, so AbstractGuardAuthenticator does not exist in 8.1.
Raw{"answer": "no", "explanation": "The Guard authentication system was removed in Symfony 6.0, so AbstractGuardAuthenticator does not exist in 8.1."} | верно | Guard authentication was removed in Symfony 7.0 — the class is gone in 8.1. |
T28-L10 2.42 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';
``` | «noyes» Пояснение: AnnotationClassLoader was deprecated in 6.1 and removed in 7.0, while AttributeClassLoader (the replacement) exists in all modern Symfony versions.
Raw```json ⏎ {"answer": "noyes", "explanation": "AnnotationClassLoader was deprecated in 6.1 and removed in 7.0, while AttributeClassLoader (the replacement) exists in all modern Symfony versions."} ⏎ ``` | верно | Annotation loaders were removed in 7.0; only attribute loaders remain (Annotation→Attribute). |