Пример запроса (первая клетка). System одинаковый во всех запросах прогона, user — свой вопрос для каждой клетки:
| Клетка | Тема | Утверждение | Ответ |
Результат | Обоснование |
T01-L1 4.02 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 (e.g., $var) and additional escape sequences, while single-quoted strings do not, so they are processed differently, not just at a different speed.
Raw{"answer": "no", "explanation": "Double-quoted strings support variable interpolation (e.g., $var) and additional escape sequences, while single-quoted strings do not, so they are processed differently, not just at a different speed."} | верно | В двойных кавычках работают интерполяция переменных и escape-последовательности, в одинарных — нет. |
T01-L2 2.38 c | Syntax and operators | The ?? operator follows isset semantics and raises no warnings for undefined variables. | «yes» Пояснение: The null coalescing operator ?? in PHP evaluates its left operand using the same logic as isset(), so it silently skips undefined variables and does not trigger any notice or warning.
Raw{"answer": "yes", "explanation": "The null coalescing operator ?? in PHP evaluates its left operand using the same logic as isset(), so it silently skips undefined variables and does not trigger any notice or warning."} | верно | ?? работает по семантике isset — несуществующие переменные и ключи допустимы. |
T01-L3 0.99 c | Syntax and operators | What will this print: echo 'a', 'b'; | «ab» Пояснение: In PHP, echo can take multiple comma-separated arguments, which are concatenated and printed in order without any separator.
Raw{"answer": "ab", "explanation": "In PHP, echo can take multiple comma-separated arguments, which are concatenated and printed in order without any separator."} | верно | echo принимает список аргументов: ab. |
T01-L4 1.6 c | Syntax and operators | print returns the value 1 and can be used inside an expression. | «no» Пояснение: In PHP, print is a language construct (not a function) that does not return any value (it returns null) and cannot be used inside an expression.
Raw{"answer": "no", "explanation": "In PHP, print is a language construct (not a function) that does not return any value (it returns null) and cannot be used inside an expression."} | неверно верный: «yes» | print — выражение со значением 1, в отличие от echo, который значения не возвращает. |
T01-L5 1.44 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.08 c | Syntax and operators | In PHP 8, the concatenation operator (.) has lower precedence than addition and subtraction. | «yes» Пояснение: In PHP, the concatenation operator (.) has lower precedence than + and -, so an expression like 1 + 2 . 3 is evaluated as (1 + 2) . 3, yielding '33'.
Raw{"answer": "yes", "explanation": "In PHP, the concatenation operator (.) has lower precedence than + and -, so an expression like 1 + 2 . 3 is evaluated as (1 + 2) . 3, yielding '33'."} | верно | С PHP 8 (RFC concat precedence) '.' имеет приоритет ниже арифметики: 'сумма: ' . 2 + 3 → 'сумма: 5' (в PHP 7 было иначе). |
T01-L7 1.63 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 is evaluated as 2 ** (3 ** 2) = 2 ** 9 = 512, not (2 ** 3) ** 2 = 64.
Raw{"answer": "no", "explanation": "In PHP, the ** operator is right-associative, so 2 ** 3 ** 2 is evaluated as 2 ** (3 ** 2) = 2 ** 9 = 512, not (2 ** 3) ** 2 = 64."} | верно | ** право-ассоциативен: 2 ** (3 ** 2) = 2 ** 9 = 512. |
T01-L8 11.36 c | Syntax and operators | What string will this print: echo 'sum: ' . 2 + 3; (PHP 8)? | «sum: 5» Пояснение: In PHP, the additive operator `+` has higher precedence than string concatenation `.`.
Raw{"answer": "sum: 5", "explanation": "In PHP, the additive operator `+` has higher precedence than string concatenation `.`."} | верно | Парная к verify-клетке про приоритет: 'сумма: 5'. |
T02-L1 2.26 c | Types and comparisons | With strict comparison (===), arrays are considered equal regardless of element order. | «no» Пояснение: In PHP, strict comparison (===) requires arrays to have the same key/value pairs in the same order, so element order matters; it is loose comparison (==) that ignores order.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "In PHP, strict comparison (===) requires arrays to have the same key/value pairs in the same order, so element order matters; it is loose comparison (==) that ignores order." ⏎ } | верно | === для массивов требует совпадения и значений, и их порядка. |
T02-L2 1.58 c | Types and comparisons | The comparison 0 == false returns false because it is a strict comparison. | «no» Пояснение: 0 == false actually returns true in PHP, and == is a loose (not strict) comparison operator.
Raw{"answer": "no", "explanation": "0 == false actually returns true in PHP, and == is a loose (not strict) comparison operator."} | верно | Наоборот: == — нестрогое сравнение и возвращает true; строгое — это === (0 === false → false). |
T02-L3 3.58 c | Types and comparisons | In PHP 8, the expression "abc" == 0 returns true. | «no» Пояснение: In PHP 8, a non-numeric string is no longer cast to 0 when loosely compared to an integer; instead the integer is cast to a string, making the comparison "abc" == "0" which is false.
Raw{"answer": "no", "explanation": "In PHP 8, a non-numeric string is no longer cast to 0 when loosely compared to an integer; instead the integer is cast to a string, making the comparison \"abc\" == \"0\" which is false."} | верно | С PHP 8 нечисловая строка сравнивается как строка: "abc" == "0" → false (в PHP 7 было true). |
T02-L4 1.29 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, so null is loosely equal to all three simultaneously.
Raw{"answer": "yes", "explanation": "In PHP, null == 0, null == \"\", and null == false all evaluate to true, so null is loosely equal to all three simultaneously."} | верно | null == 0, null == "" и null == false — все true. |
T02-L5 1.91 c | Types and comparisons | What does the expression (int) '42abc' return? | «42» Пояснение: When casting a string to int in PHP, only the leading numeric portion is converted, so '42abc' becomes 42.
Raw{"answer": 42, "explanation": "When casting a string to int in PHP, only the leading numeric portion is converted, so '42abc' becomes 42."} | верно | Ведущая числовая часть: 42, без ошибок и warning. |
T02-L6 1.04 c | Types and comparisons | What does the expression '5' + 5 return? | «10» Пояснение: In PHP, the numeric string '5' is automatically cast to the integer 5, so the addition results in 10.
Raw{"answer": 10, "explanation": "In PHP, the numeric string '5' is automatically cast to the integer 5, so the addition results in 10."} | верно | Числовая строка приводится: int 10. |
T02-L7 1.76 c | Types and comparisons | When cast to string, false becomes "0". | «no» Пояснение: In PHP, (string) false results in an empty string (""), not "0"; the integer 0 is what becomes "0" when cast to a string.
Raw{"answer": "no", "explanation": "In PHP, (string) false results in an empty string (\"\"), not \"0\"; the integer 0 is what becomes \"0\" when cast to a string."} | верно | false → "", true → "1". |
T02-L8 3.05 c | Types and comparisons | The comparison 0.1 + 0.2 === 0.3 returns false. | «yes» Пояснение: Due to IEEE 754 floating-point imprecision, 0.1 + 0.2 equals 0.30000000000000004, which is not strictly equal to 0.3, so === returns false.
Raw{"answer": "yes", "explanation": "Due to IEEE 754 floating-point imprecision, 0.1 + 0.2 equals 0.30000000000000004, which is not strictly equal to 0.3, so === returns false."} | верно | Двоичная погрешность float: 0.1 + 0.2 = 0.30000000000000004. |
T03-L1 1.57 c | Strings | strrev() correctly reverses a UTF-8 string. | «no» Пояснение: strrev() operates on individual bytes, not on UTF-8 code points, so it will corrupt multi-byte UTF-8 characters.
Raw{"answer": "no", "explanation": "strrev() operates on individual bytes, not on UTF-8 code points, so it will corrupt multi-byte UTF-8 characters."} | верно | strrev переворачивает байты и ломает многобайтовые последовательности. |
T03-L2 0.9 c | Strings | str_contains('Hello world', 'world') returns true. | «yes» Пояснение: str_contains('Hello world', 'world') returns true because 'world' is a substring of 'Hello world'.
Raw{"answer": "yes", "explanation": "str_contains('Hello world', 'world') returns true because 'world' is a substring of 'Hello world'."} | верно | str_contains с PHP 8.0 проверяет вхождение подстроки. |
T03-L3 1.21 c | Strings | str_pad() can pad a string on the right side only. | «no» Пояснение: str_pad() can pad a string on the right, left, or both sides using the STR_PAD_RIGHT, STR_PAD_LEFT, or STR_PAD_BOTH constants.
Raw{"answer": "no", "explanation": "str_pad() can pad a string on the right, left, or both sides using the STR_PAD_RIGHT, STR_PAD_LEFT, or STR_PAD_BOTH constants."} | верно | STR_PAD_LEFT / STR_PAD_BOTH меняют сторону дополнения. |
T03-L4 1.56 c | Strings | By default trim() strips only spaces, leaving tabs and newlines intact. | «no» Пояснение: By default, trim() strips all whitespace characters (space, tab, newline, carriage return, vertical tab, and form feed), not just spaces.
Raw{"answer": "no", "explanation": "By default, trim() strips all whitespace characters (space, tab, newline, carriage return, vertical tab, and form feed), not just spaces."} | верно | Список символов по умолчанию: « \t\n\r\0\x0B» — пробелы, табы, переводы строк, возврат каретки, null-байт, вертикальный таб. Проверено php -r. |
T03-L5 1.91 c | Strings | How many BYTES does strlen('héllo') return for a UTF-8 string? | «6» Пояснение: In UTF-8, 'h', 'l', 'l', and 'o' are 1 byte each, while 'é' (U+00E9) is encoded as 2 bytes, giving a total of 6 bytes.
Raw{"answer": 6, "explanation": "In UTF-8, 'h', 'l', 'l', and 'o' are 1 byte each, while 'é' (U+00E9) is encoded as 2 bytes, giving a total of 6 bytes."} | верно | 6 букв по 2 байта: 12. |
T03-L6 1.69 c | Strings | What does substr('abcdef', -3) return? | «def» Пояснение: With a negative start index of -3, substr counts from the end of the string, returning the last 3 characters 'def'.
Raw{"answer": "def", "explanation": "With a negative start index of -3, substr counts from the end of the string, returning the last 3 characters 'def'."} | верно | Отрицательное смещение — с конца: def. |
T03-L7 1.18 c | Strings | ucfirst() modifies the string passed to it in place. | «no» Пояснение: In PHP, strings are passed by value, and ucfirst() returns a new string rather than modifying the original in place; you must reassign the result to see the change.
Raw{"answer": "no", "explanation": "In PHP, strings are passed by value, and ucfirst() returns a new string rather than modifying the original in place; you must reassign the result to see the change."} | верно | Строки неизменяемы; ucfirst возвращает новую строку. |
T03-L8 1.7 c | Strings | Variable interpolation works in heredoc but not in nowdoc. | «yes» Пояснение: Heredoc interpolates variables (e.g., $var) in the body, while nowdoc treats the body as literal strings with no interpolation.
Raw{"answer": "yes", "explanation": "Heredoc interpolates variables (e.g., $var) in the body, while nowdoc treats the body as literal strings with no interpolation."} | верно | Nowdoc — «одинарные кавычки» в тройном синтаксисе: текст как есть. |
T04-L1 1.67 c | Arrays | The sort() function preserves the key-to-value association of the array. | «no» Пояснение: The sort() function reindexes the array with numeric keys 0, 1, 2, ...; it does not preserve key-to-value associations (use asort() for that instead).
Raw{"answer": "no", "explanation": "The sort() function reindexes the array with numeric keys 0, 1, 2, ...; it does not preserve key-to-value associations (use asort() for that instead)."} | верно | sort перенумеровывает ключи; связь сохраняет asort. |
T04-L2 1.16 c | Arrays | The string key '5' in an array is stored as the integer 5. | «yes» Пояснение: In PHP, string keys that consist solely of digits are automatically cast to integers, so '5' becomes the integer key 5.
Raw{"answer": "yes", "explanation": "In PHP, string keys that consist solely of digits are automatically cast to integers, so '5' becomes the integer key 5."} | верно | Каноничные десятичные строковые ключи приводятся к int. |
T04-L3 1.34 c | Arrays | The in_array() function uses strict comparison (===) by default. | «no» Пояснение: in_array() uses loose comparison (==) by default; strict comparison (===) is only used when the third parameter $strict is set to true.
Raw{"answer":"no","explanation":"in_array() uses loose comparison (==) by default; strict comparison (===) is only used when the third parameter $strict is set to true."} | верно | По умолчанию сравнение нестрогое; строгое — третий аргумент true. |
T04-L4 3.09 c | Arrays | Without a callback, array_filter() removes all "empty" (falsy) elements from the array. | «yes» Пояснение: When no callback is provided, array_filter() removes all elements that evaluate to false (i.e., 0, 0.0, '', null, [], false).
Raw{"answer": "yes", "explanation": "When no callback is provided, array_filter() removes all elements that evaluate to false (i.e., 0, 0.0, '', null, [], false)."} | верно | Убирает 0, "", null, false и пустые массивы. |
T04-L5 1.18 c | Arrays | By default, array_slice() preserves the original numeric keys of the array. | «no» Пояснение: By default, the preserve_keys parameter of array_slice() is false, so the keys are renumbered starting from 0.
Raw{"answer": "no", "explanation": "By default, the preserve_keys parameter of array_slice() is false, so the keys are renumbered starting from 0."} | верно | По умолчанию ключи перенумеровываются; сохранение — preserve_keys = true. |
T04-L6 1.44 c | Arrays | What does array_slice([10, 20, 30, 40], 1, 2) return? | «[20, 30]» Пояснение: array_slice starts at offset 1 (value 20) and takes 2 elements, returning the sub-array [20, 30].
Raw{"answer": "[20, 30]", "explanation": "array_slice starts at offset 1 (value 20) and takes 2 elements, returning the sub-array [20, 30]."} | верно | [20,30]; ключи перенумеровываются. |
T04-L7 1.82 c | Arrays | How many elements will count(['a' => 1] + ['a' => 9, 'b' => 2]) return? | «2» Пояснение: The + operator gives precedence to the left array, so 'a' => 9 is ignored and only 'b' => 2 is added, resulting in ['a' => 1, 'b' => 2].
Raw{"answer": 2, "explanation": "The + operator gives precedence to the left array, so 'a' => 9 is ignored and only 'b' => 2 is added, resulting in ['a' => 1, 'b' => 2]."} | верно | Оператор + : по ключу 'a' побеждает левый; итого 2. |
T04-L8 1.12 c | Arrays | Since PHP 8.1, the spread operator [...$a, ...$b] supports arrays with string keys. | «yes» Пояснение: Since PHP 8.1, the spread operator can be used with associative arrays (string keys), not just numeric-indexed arrays.
Raw{"answer": "yes", "explanation": "Since PHP 8.1, the spread operator can be used with associative arrays (string keys), not just numeric-indexed arrays."} | верно | В 8.0 — только числовые ключи; 8.1 снял ограничение. |
T05-L1 1.62 c | Functions and closures | Named arguments cannot be combined with argument unpacking ...$args in a single call. | «yes» Пояснение: PHP does not allow mixing named arguments (e.g. name: 'value') with argument unpacking (e.g. ...$args) in the same function call.
Raw{"answer": "yes", "explanation": "PHP does not allow mixing named arguments (e.g. name: 'value') with argument unpacking (e.g. ...$args) in the same function call."} | неверно верный: «no» | Можно: f(...$args, имя: значение). Нельзя только позиционный аргумент после распаковки. |
T05-L2 1.24 c | Functions and closures | An anonymous function without use sees variables from the outer scope. | «no» Пояснение: In PHP, a closure (anonymous function) without the use keyword does not capture any variables from the enclosing scope; you must explicitly use use to bring outer variables into the closure.
Raw{"answer": "no", "explanation": "In PHP, a closure (anonymous function) without the use keyword does not capture any variables from the enclosing scope; you must explicitly use use to bring outer variables into the closure."} | верно | Без use внешние переменные недоступны; авто-захват только у fn. |
T05-L3 1.72 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 call (1, 2, 3), regardless of how many are declared in the signature.
Raw{"answer": 3, "explanation": "func_num_args() returns the number of arguments actually passed to the function, which is 3 in this call (1, 2, 3), regardless of how many are declared in the signature."} | верно | Считает переданные аргументы: 3. |
T05-L4 2.36 c | Functions and closures | The body of an arrow function fn may consist of several expressions in curly braces. | «no» Пояснение: The body of a PHP arrow function (fn) must be a single expression following the `=>` operator, and does not use curly braces or allow multiple statements.
Raw{"answer": "no", "explanation": "The body of a PHP arrow function (fn) must be a single expression following the `=>` operator, and does not use curly braces or allow multiple statements."} | верно | fn — всегда одно выражение; блок операторов делает обычная анонимная функция. |
T05-L5 3.05 c | Functions and closures | An arrow function fn captures outer variables by reference (lazily, at use time). | «no» Пояснение: PHP arrow functions (fn) capture outer variables by value eagerly at definition time, not by reference lazily.
Raw{"answer": "no", "explanation": "PHP arrow functions (fn) capture outer variables by value eagerly at definition time, not by reference lazily."} | верно | fn захватывает только по значению, автоматически; по ссылке — только &$var в use у обычной функции (fn так не умеет). |
T05-L6 2.25 c | Functions and closures | A closure declared as static function () {} does not capture $this. | «yes» Пояснение: In PHP, a static closure cannot access the $this variable from the enclosing class scope, so it does not capture $this.
Raw{"answer": "yes", "explanation": "In PHP, a static closure cannot access the $this variable from the enclosing class scope, so it does not capture $this."} | верно | static-замыкание отвязано от объекта: $this внутри недоступен. |
T05-L7 2.06 c | Functions and closures | What will this print: $x = 5; $f = function () use ($x) { return $x; }; $x = 7; echo $f(); | «5» Пояснение: The use ($x) clause captures the value of $x by value at closure creation time, so changing $x to 7 afterward does not affect the closure's captured variable, which still holds 5.
Raw{"answer": 5, "explanation": "The use ($x) clause captures the value of $x by value at closure creation time, so changing $x to 7 afterward does not affect the closure's captured variable, which still holds 5."} | верно | use захватывает по значению в момент создания: 5. |
T05-L8 1.39 c | Functions and closures | In weak typing mode (without strict_types), passing the string "5" to an int parameter is allowed. | «yes» Пояснение: In weak typing mode (without strict_types), PHP automatically converts the numeric string "5" to the integer 5 when passing it to an int parameter.
Raw{"answer": "yes", "explanation": "In weak typing mode (without strict_types), PHP automatically converts the numeric string \"5\" to the integer 5 when passing it to an int parameter."} | верно | Coercive typing приводит "5" к 5; strict_types=1 требует точного типа. |
T06-L1 1.25 c | OOP: classes and inheritance | PHP supports constructor property promotion: public function __construct(private int $x) {}. | «yes» Пояснение: Constructor property promotion with visibility modifiers like `private` was introduced in PHP 8.0.
Raw{"answer": "yes", "explanation": "Constructor property promotion with visibility modifiers like `private` was introduced in PHP 8.0."} | верно | С PHP 8.0 параметр с модификатором создаёт свойство и присваивание. |
T06-L2 0.77 c | OOP: classes and inheritance | Which keyword prevents a method from being overridden in subclasses? | «final» Пояснение: In PHP, the 'final' keyword prevents a method from being overridden in subclasses.
Raw{"answer": "final", "explanation": "In PHP, the 'final' keyword prevents a method from being overridden in subclasses."} | верно | final. |
T06-L3 0.86 c | OOP: classes and inheritance | A method declared final cannot be overridden in a subclass. | «yes» Пояснение: In PHP, a method declared with the `final` keyword cannot be overridden in a subclass.
Raw{"answer": "yes", "explanation": "In PHP, a method declared with the `final` keyword cannot be overridden in a subclass."} | верно | final запрещает переопределение метода и наследование класса. |
T06-L4 1.25 c | OOP: classes and inheritance | Parent properties with private visibility are accessible in a subclass. | «no» Пояснение: Private properties in PHP are accessible only within the class where they are defined; a subclass cannot access the parent's private properties (unlike protected properties).
Raw{"answer": "no", "explanation": "Private properties in PHP are accessible only within the class where they are defined; a subclass cannot access the parent's private properties (unlike protected properties)."} | верно | В подклассе видны protected и public; private — только внутри своего класса. |
T06-L5 2.63 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» Пояснение: In PHP, get_class() on an anonymous class instance returns a string like "class\x00/file.php:12", so the part before the NUL byte is simply "class".
Raw{"answer": "class", "explanation": "In PHP, get_class() on an anonymous class instance returns a string like \"class\\x00/file.php:12\", so the part before the NUL byte is simply \"class\"."} | неверно верный: «class@anonymous» | get_class анонимного класса печатает class@anonymous\0<файл>:<строка>$n; короткая форма — часть до NUL-байта. Проверено php -r (hex). |
T06-L6 1.89 c | OOP: classes and inheritance | A private parent method is not part of the inheritance contract: a child may declare a method with the same name and any visibility. | «yes» Пояснение: Private methods are hidden from child classes and do not form part of the inheritance contract, so a child class is free to define a method of the same name with any visibility.
Raw{"answer": "yes", "explanation": "Private methods are hidden from child classes and do not form part of the inheritance contract, so a child class is free to define a method of the same name with any visibility."} | верно | private-члены не наследуются — правила совместимости подписей не действуют. |
T06-L7 3.03 c | OOP: classes and inheritance | The magic method __get() is called only for non-existent properties. | «yes» Пояснение: The __get() magic method is only invoked when you attempt to access a property that has not been set or declared in the object, i.e., a non-existent property.
Raw{"answer": "yes", "explanation": "The __get() magic method is only invoked when you attempt to access a property that has not been set or declared in the object, i.e., a non-existent property."} | неверно верный: «no» | __get срабатывает и для существующих, но недоступных (private/protected извне). |
T06-L8 1.45 c | OOP: classes and inheritance | What does reassigning a readonly property throw — Exception or Error? | «error» Пояснение: Reassigning a readonly property in PHP 8.1+ throws a TypeError, which is a subclass of Error, not Exception.
Raw{"answer": "Error", "explanation": "Reassigning a readonly property in PHP 8.1+ throws a TypeError, which is a subclass of Error, not Exception."} | верно | Error (readonly с 8.1); оговорка: в __clone() переинициализация допустима (8.3+). |
T07-L1 1.41 c | Interfaces, traits, enum | An interface can declare constants. | «yes» Пояснение: In PHP, interfaces can declare constants, which are implicitly public and must be assigned a constant expression.
Raw{"answer":"yes","explanation":"In PHP, interfaces can declare constants, which are implicitly public and must be assigned a constant expression."} | верно | Константы интерфейса наследуются реализациями. |
T07-L2 0.62 c | Interfaces, traits, enum | Which operator checks whether an object is an instance of a class or interface? | «instanceof» Пояснение: The instanceof operator returns true if the object is an instance of the specified class or interface.
Raw{"answer": "instanceof", "explanation": "The instanceof operator returns true if the object is an instance of the specified class or interface."} | верно | instanceof. |
T07-L3 2.63 c | Interfaces, traits, enum | An interface can declare static methods. | «no» Пояснение: In PHP, interfaces can only declare abstract method signatures and constants; they cannot declare static methods.
Raw{"answer": "no", "explanation": "In PHP, interfaces can only declare abstract method signatures and constants; they cannot declare static methods."} | неверно верный: «yes» | Реализация обязана дать статический метод с той же сигнатурой. |
T07-L4 1.35 c | Interfaces, traits, enum | The instanceof operator only checks class inheritance: it ignores interfaces. | «no» Пояснение: The instanceof operator checks both class inheritance and interface implementation, so it does not ignore interfaces.
Raw{"answer": "no", "explanation": "The instanceof operator checks both class inheritance and interface implementation, so it does not ignore interfaces."} | верно | instanceof возвращает true и для интерфейсов объекта. |
T07-L5 2.05 c | Interfaces, traits, enum | An interface method may have a default implementation, like a trait method. | «no» Пояснение: In PHP, interfaces can only declare method signatures (abstract methods) without any method body, so they cannot provide default implementations like traits can.
Raw{"answer": "no", "explanation": "In PHP, interfaces can only declare method signatures (abstract methods) without any method body, so they cannot provide default implementations like traits can."} | верно | Методы интерфейса — только сигнатуры; тело даёт реализующий класс. |
T07-L6 3.71 c | Interfaces, traits, enum | An abstract method in an abstract class may have protected visibility. | «yes» Пояснение: In PHP, abstract methods can be declared as either public or protected, so a protected abstract method in an abstract class is perfectly valid.
Raw{"answer": "yes", "explanation": "In PHP, abstract methods can be declared as either public or protected, so a protected abstract method in an abstract class is perfectly valid."} | верно | В абстрактном классе — любая видимость; в интерфейсе — только public. |
T07-L7 1.04 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 this enum has 3 cases (A, B, and C).
Raw{"answer": 3, "explanation": "Foo::cases() returns an array containing all enum cases, and this enum has 3 cases (A, B, and C)."} | верно | Статический метод cases(): 3. |
T07-L8 0.98 c | Interfaces, traits, enum | A trait can declare constants. | «yes» Пояснение: In PHP, traits can declare constants using the `const` keyword, just like classes can.
Raw{"answer": "yes", "explanation": "In PHP, traits can declare constants using the `const` keyword, just like classes can."} | верно | С PHP 8.2 трейты могут объявлять константы (RFC constants_in_traits); до 8.2 — нет. |
T08-L1 2.72 c | Exceptions and errors | The Throwable interface is a common ancestor of both Exception and Error. | «no» Пояснение: Throwable is an abstract class in PHP, not an interface, so calling it 'The Throwable interface' makes the statement false.
Raw{"answer": "no", "explanation": "Throwable is an abstract class in PHP, not an interface, so calling it 'The Throwable interface' makes the statement false."} | неверно верный: «yes» | Иерархия с PHP 7: Throwable → Exception и Throwable → Error. |
T08-L2 2.5 c | Exceptions and errors | A catch (Exception $e) block will also catch TypeError, because TypeError ultimately inherits from Exception. | «no» Пояснение: TypeError inherits from Error (not Exception); both Exception and Error extend Throwable, so catching Exception will not catch TypeError.
Raw{"answer": "no", "explanation": "TypeError inherits from Error (not Exception); both Exception and Error extend Throwable, so catching Exception will not catch TypeError."} | верно | TypeError наследуется от Error; catch (Exception) его не ловит. |
T08-L3 1.45 c | Exceptions and errors | The @ operator suppresses exceptions too. | «no» Пояснение: In PHP, the @ operator suppresses errors, warnings, notices, and deprecations, but it does not suppress exceptions, which are handled through try/catch and set_exception_handler().
Raw{"answer": "no", "explanation": "In PHP, the @ operator suppresses errors, warnings, notices, and deprecations, but it does not suppress exceptions, which are handled through try/catch and set_exception_handler()."} | верно | @ глушит диагностику (warnings/notices), исключения не перехватывает. |
T08-L4 2.11 c | Exceptions and errors | What error class does intdiv(5, 0) throw? | «divisionbyzeroerror» Пояснение: In PHP 8.0+, calling intdiv(5, 0) throws a DivisionByZeroError, which extends ArithmeticException.
Raw{"answer": "DivisionByZeroError", "explanation": "In PHP 8.0+, calling intdiv(5, 0) throws a DivisionByZeroError, which extends ArithmeticException."} | верно | DivisionByZeroError (иерархия Error, не Exception); php-грейдер объективен. |
T08-L5 1.63 c | Exceptions and errors | The finally block runs only if the exception was caught by a catch block. | «no» Пояснение: The finally block executes regardless of whether an exception was thrown and caught; it runs after the try block completes, whether or not an exception occurred or was handled.
Raw{"answer": "no", "explanation": "The finally block executes regardless of whether an exception was thrown and caught; it runs after the try block completes, whether or not an exception occurred or was handled."} | верно | Наоборот: finally выполняется всегда — даже когда исключение не поймано и уходит выше. Проверено php -r. |
T08-L6 3.3 c | Exceptions and errors | An exception thrown inside a finally block has no effect on the result of the try block. | «no» Пояснение: An exception thrown inside a finally block does have an effect; it propagates outward and replaces any exception already being handled by the catch block.
Raw{"answer": "no", "explanation": "An exception thrown inside a finally block does have an effect; it propagates outward and replaces any exception already being handled by the catch block."} | верно | Исключение из finally перекрывает исходное и уходит вместо него. |
T08-L7 1.26 c | Exceptions and errors | What does the expression (bool) new Exception('x') return? | «yes» Пояснение: In PHP, casting any non-null object to a boolean always yields true, and new Exception('x') produces a valid non-null object.
Raw{"answer": "yes", "explanation": "In PHP, casting any non-null object to a boolean always yields true, and new Exception('x') produces a valid non-null object."} | верно | Любой объект при приведении к bool — true. Формы ответа: true или да. |
T08-L8 1.41 c | Exceptions and errors | Functions registered via register_shutdown_function() run when exit is called. | «yes» Пояснение: register_shutdown_function() callbacks are executed on normal termination, which includes when exit() or die() is called.
Raw{"answer":"yes","explanation":"register_shutdown_function() callbacks are executed on normal termination, which includes when exit() or die() is called."} | верно | exit завершает скрипт, но shutdown-функции отрабатывают. |
T09-L1 1.47 c | Namespaces and autoloading | The use App\Service\Mailer; statement itself loads the class file. | «no» Пояснение: The 'use' statement is only a namespace alias that changes how a class name is resolved; the actual class file is not loaded until the class is first referenced (e.g., instantiated or called).
Raw{"answer": "no", "explanation": "The 'use' statement is only a namespace alias that changes how a class name is resolved; the actual class file is not loaded until the class is first referenced (e.g., instantiated or called)."} | верно | use — псевдоним на этапе компиляции; файл грузит автозагрузчик при первом обращении. |
T09-L2 1.55 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 you use the syntax 'use function Namespace\FunctionName;' whereas 'use const' is for importing constants.
Raw{"answer": "function", "explanation": "In PHP, to import a function you use the syntax 'use function Namespace\\FunctionName;' whereas 'use const' is for importing constants."} | верно | use function ...; (и use const для констант). |
T09-L3 1.94 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» Пояснение: Under PSR-4, the namespace part after 'App\' (i.e. Controller\Api) plus the class name becomes the relative file path: src/Controller/Api/UserController.php.
Raw{"answer": "Controller/Api/UserController.php", "explanation": "Under PSR-4, the namespace part after 'App\\' (i.e. Controller\\Api) plus the class name becomes the relative file path: src/Controller/Api/UserController.php."} | верно | Остаток имени после префикса, \ → /. |
T09-L4 1.4 c | Namespaces and autoloading | Including vendor/autoload.php registers autoloaders via spl_autoload_register(). | «yes» Пояснение: Composer-generated vendor/autoload.php calls spl_autoload_register() to attach its classmap and PSR-4 autoloader callbacks.
Raw{"answer": "yes", "explanation": "Composer-generated vendor/autoload.php calls spl_autoload_register() to attach its classmap and PSR-4 autoloader callbacks."} | верно | Composer ставит автозагрузчик именно на spl_autoload_register. |
T09-L5 1.1 c | Namespaces and autoloading | The magic constant __NAMESPACE__ contains the name of the current namespace. | «yes» Пояснение: __NAMESPACE__ is a magic constant introduced in PHP 5.3 that returns the name of the current namespace, or an empty string if there is no namespace.
Raw{"answer": "yes", "explanation": "__NAMESPACE__ is a magic constant introduced in PHP 5.3 that returns the name of the current namespace, or an empty string if there is no namespace."} | верно | В корневом пространстве — пустая строка. |
T09-L6 2.05 c | Namespaces and autoloading | An unqualified class name (without a leading \) in new is resolved from the global root. | «no» Пояснение: An unqualified class name is resolved relative to the current namespace (and the autoloader), not directly from the global root; a leading backslash is required to reference the global namespace.
Raw{"answer":"no","explanation":"An unqualified class name is resolved relative to the current namespace (and the autoloader), not directly from the global root; a leading backslash is required to reference the global namespace."} | верно | Резолвится относительно текущего namespace (с учётом импортов). |
T09-L7 1.6 c | Namespaces and autoloading | With the PSR-4 mapping "App\ → src/", the class App\Model\User lives in the file src/Model/User.php. | «yes» Пояснение: In PSR-4, the namespace 'App\' maps to 'src/', and the remaining sub-namespace 'Model\User' translates to the relative path 'Model/User.php' inside that directory, resulting in src/Model/User.php.
Raw{"answer": "yes", "explanation": "In PSR-4, the namespace 'App\\' maps to 'src/', and the remaining sub-namespace 'Model\\User' translates to the relative path 'Model/User.php' inside that directory, resulting in src/Model/User.php."} | верно | Остаток имени после префикса переносится в путь как есть. |
T09-L8 1.52 c | Namespaces and autoloading | A use statement may be written inside a function body — the import then applies to that function only. | «yes» Пояснение: In PHP, a `use` statement can be placed inside a function or method body to import a class, and the import is scoped to that function/method only.
Raw{"answer":"yes","explanation":"In PHP, a `use` statement can be placed inside a function or method body to import a class, and the import is scoped to that function/method only."} | неверно верный: «no» | use внутри тела функции — parse error; импорты файловые и компиляционные. |
T10-L1 1.39 c | References and scope | Arrays are copied on assignment rather than passed by reference. | «yes» Пояснение: In PHP, array assignment creates a copy of the array (copy-on-write internally), so the two variables hold independent data unless explicitly passed by reference with the & operator.
Raw{"answer": "yes", "explanation": "In PHP, array assignment creates a copy of the array (copy-on-write internally), so the two variables hold independent data unless explicitly passed by reference with the & operator."} | верно | Присваивание массива — копия (в движке — copy-on-write). |
T10-L2 0.81 c | References and scope | What will this print: $a = [1, 2]; $b = $a; $b[] = 3; echo count($a); | «2» Пояснение: PHP uses copy-on-write, so modifying $b does not affect $a, which remains [1, 2].
Raw{"answer": 2, "explanation": "PHP uses copy-on-write, so modifying $b does not affect $a, which remains [1, 2]."} | верно | Присваивание — копия: в $a по-прежнему 2 элемента. |
T10-L3 1.29 c | References and scope | Inside a function, user-defined global variables are inaccessible without global, $GLOBALS, or passing them as parameters. | «yes» Пояснение: In PHP, variables defined in the global scope are not visible inside functions by default; you must use `global`, `$GLOBALS`, or pass them as parameters to access them within a function.
Raw{"answer": "yes", "explanation": "In PHP, variables defined in the global scope are not visible inside functions by default; you must use `global`, `$GLOBALS`, or pass them as parameters to access them within a function."} | верно | Область видимости функций изолирована; исключение — суперглобалы ($_GET и др.). |
T10-L4 2.83 c | References and scope | unset($GLOBALS['x']) inside a function removes the global variable only for that function. | «no» Пояснение: $GLOBALS is a super-global array that directly references the global scope, so unset($GLOBALS['x']) permanently removes the global variable from the entire global scope, not just the current function's execution.
Raw{"answer": "no", "explanation": "$GLOBALS is a super-global array that directly references the global scope, so unset($GLOBALS['x']) permanently removes the global variable from the entire global scope, not just the current function's execution."} | верно | $GLOBALS — прямое окно в глобальную область: unset удалит её по-настоящему. |
T10-L5 0.9 c | References and scope | What will this print: function inc(&$x) { $x++; } $n = 5; inc($n); echo $n; | «6» Пояснение: The function inc takes $x by reference, so $n is incremented from 5 to 6.
Raw{"answer": "6", "explanation": "The function inc takes $x by reference, so $n is incremented from 5 to 6."} | верно | Ссылка меняет оригинал: 6. |
T10-L6 3.21 c | References and scope | A foreach over an array (by value) works with the "live" array: changes to the array inside the loop are visible in the same pass. | «no» Пояснение: In PHP, foreach by value iterates over a snapshot (copy) of the array taken at loop start, so modifications to the array during the same pass (e.g., appending elements) are not visible to the loop.
Raw{"answer":"no","explanation":"In PHP, foreach by value iterates over a snapshot (copy) of the array taken at loop start, so modifications to the array during the same pass (e.g., appending elements) are not visible to the loop."} | верно | По значению foreach итерирует копию-снимок. |
T10-L7 1.43 c | References and scope | A static property belongs to each instance separately: changes in one object are not visible in others. | «no» Пояснение: Static properties are shared among all instances of a class; changes made through one object are visible to all other objects of the same class.
Raw{"answer": "no", "explanation": "Static properties are shared among all instances of a class; changes made through one object are visible to all other objects of the same class."} | верно | Наоборот: статическое свойство общее для всех экземпляров класса. Проверено php -r. |
T10-L8 2.37 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 automatically cast to integers (true becomes 1, false becomes 0), so the key is stored as an integer, not as a bool.
Raw{"answer":"no","explanation":"In PHP, boolean array keys are automatically cast to integers (true becomes 1, false becomes 0), so the key is stored as an integer, not as a bool."} | верно | Булев ключ приводится к int: true → 1, false → 0. |
T11-L1 1.99 c | Generators, iterators, SPL | Inside a generator, return with a value can be used, and it becomes available via $gen->getReturn(). | «yes» Пояснение: In PHP 7.3+, a return statement with a value inside a generator function sets the generator's return value, which can be accessed via the getReturn() method on the Generator object.
Raw{"answer": "yes", "explanation": "In PHP 7.3+, a return statement with a value inside a generator function sets the generator's return value, which can be accessed via the getReturn() method on the Generator object."} | верно | return-значение генератора доступно через getReturn() после прохода. |
T11-L2 3.43 c | Generators, iterators, SPL | A fully consumed generator can be rewound with rewind() and traversed again. | «yes» Пояснение: In PHP, once a generator is fully exhausted, calling rewind() on it resets it to the beginning, allowing it to be traversed again with next().
Raw{"answer": "yes", "explanation": "In PHP, once a generator is fully exhausted, calling rewind() on it resets it to the beginning, allowing it to be traversed again with next()."} | неверно верный: «no» | Генератор одноразовый: rewind после начала итерации бросает Exception. |
T11-L3 1.51 c | Generators, iterators, SPL | The yield from construct delegates traversal to another generator or iterable. | «yes» Пояснение: The yield from construct in PHP delegates traversal to another generator or Traversable iterable, yielding its values as if they were part of the outer generator.
Raw{"answer": "yes", "explanation": "The yield from construct in PHP delegates traversal to another generator or Traversable iterable, yielding its values as if they were part of the outer generator."} | верно | yield from проксирует значения, ключи и return-значение внутреннего генератора. |
T11-L4 1.24 c | Generators, iterators, SPL | What does get_class(g()) return for function g() { yield 1; }? | «generator» Пояснение: Calling a PHP generator function returns a Generator object, so get_class() on the result of g() returns the string "Generator".
Raw{"answer": "Generator", "explanation": "Calling a PHP generator function returns a Generator object, so get_class() on the result of g() returns the string \"Generator\"."} | верно | Функция с yield возвращает Generator. |
T11-L5 2.05 c | Generators, iterators, SPL | How many elements will count(iterator_to_array((function () { yield from [1, 2, 3]; })())) return? | «3» Пояснение: yield from [1, 2, 3] yields the three elements 1, 2, and 3, which iterator_to_array() converts into an array of three elements, so count() returns 3.
Raw{"answer": 3, "explanation": "yield from [1, 2, 3] yields the three elements 1, 2, and 3, which iterator_to_array() converts into an array of three elements, so count() returns 3."} | верно | yield from делегирует все 3 элемента. |
T11-L6 1.56 c | Generators, iterators, SPL | The SplStack class implements a FIFO queue. | «no» Пояснение: SplStack implements a LIFO (Last-In, First-Out) stack, not a FIFO (First-In, First-Out) queue; the SPL class for a FIFO queue is SplQueue.
Raw{"answer":"no","explanation":"SplStack implements a LIFO (Last-In, First-Out) stack, not a FIFO (First-In, First-Out) queue; the SPL class for a FIFO queue is SplQueue."} | верно | SplStack — стек LIFO; очередь FIFO — SplQueue. |
T11-L7 1.0 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 implements the Iterator interface and allows you to wrap and traverse an array element by element.
Raw{"answer": "yes", "explanation": "ArrayIterator is a built-in PHP class that implements the Iterator interface and allows you to wrap and traverse an array element by element."} | верно | Объектная обёртка над массивом. |
T11-L8 0.96 c | Generators, iterators, SPL | An ArrayObject instance cannot be traversed with foreach. | «no» Пояснение: ArrayObject implements the Iterator interface and can be traversed with foreach.
Raw{"answer": "no", "explanation": "ArrayObject implements the Iterator interface and can be traversed with foreach."} | верно | ArrayObject реализует IteratorAggregate — foreach по нему работает. |
T12-L1 1.83 c | Configuration and security | password_hash() generates a salt automatically — passing one separately is not needed. | «yes» Пояснение: password_hash() generates a cryptographically random salt automatically and embeds it in the returned hash, so you never need to supply a salt separately.
Raw{"answer":"yes","explanation":"password_hash() generates a cryptographically random salt automatically and embeds it in the returned hash, so you never need to supply a salt separately."} | верно | Соль встраивается в строку результата; параметр salt устарел. |
T12-L2 1.68 c | Configuration and security | In PHP 8, PASSWORD_DEFAULT is md5 with an automatically added salt. | «no» Пояснение: PASSWORD_DEFAULT in PHP 8 is an alias for PASSWORD_BCRYPT, not MD5.
Raw{"answer": "no", "explanation": "PASSWORD_DEFAULT in PHP 8 is an alias for PASSWORD_BCRYPT, not MD5."} | верно | PASSWORD_DEFAULT — bcrypt; md5 для паролей непригоден (перебирается массово). |
T12-L3 1.8 c | Configuration and security | What does password_verify('secret', password_hash('secret', PASSWORD_DEFAULT)) return? | «true» Пояснение: password_hash() creates a hash of 'secret' and password_verify() confirms the plaintext matches that hash, returning the boolean true.
Raw{"answer": "true", "explanation": "password_hash() creates a hash of 'secret' and password_verify() confirms the plaintext matches that hash, returning the boolean true."} | верно | Соль и хеш в одной строке: true (форма ответа: true или да). |
T12-L4 1.15 c | Configuration and security | strip_tags() protects against SQL injection. | «no» Пояснение: strip_tags() removes HTML tags to prevent XSS attacks, not SQL injection, which is protected by prepared statements or proper escaping.
Raw{"answer":"no","explanation":"strip_tags() removes HTML tags to prevent XSS attacks, not SQL injection, which is protected by prepared statements or proper escaping."} | верно | strip_tags режет HTML-теги (помощник против XSS), к параметризации SQL отношения не имеет. |
T12-L5 1.3 c | Configuration and security | session_regenerate_id() is used to protect against session fixation upon user login. | «yes» Пояснение: session_regenerate_id() is the recommended PHP method to mitigate session fixation attacks by issuing a new session ID after a user logs in, invalidating any previously known session ID an attacker may have captured.
Raw{"answer": "yes", "explanation": "session_regenerate_id() is the recommended PHP method to mitigate session fixation attacks by issuing a new session ID after a user logs in, invalidating any previously known session ID an attacker may have captured."} | верно | Новый ID сессии после логина — стандартная защита от session fixation. |
T12-L6 1.01 c | Configuration and security | Which built-in function returns the SAPI name (e.g., cli)? | «php_sapi_name» Пояснение: The php_sapi_name() function returns the name of the loaded SAPI module, such as 'cli', 'apache2handler', or 'fpm'.
Raw{"answer": "php_sapi_name", "explanation": "The php_sapi_name() function returns the name of the loaded SAPI module, such as 'cli', 'apache2handler', or 'fpm'."} | верно | php_sapi_name(). |
T12-L7 2.61 c | Configuration and security | session_destroy() deletes session data on the server but not the cookie in the user's browser. | «yes» Пояснение: session_destroy() only removes the session data stored on the server side; the session cookie persists in the user's browser unless explicitly deleted (e.g., via setcookie() with a past expiration).
Raw{"answer": "yes", "explanation": "session_destroy() only removes the session data stored on the server side; the session cookie persists in the user's browser unless explicitly deleted (e.g., via setcookie() with a past expiration)."} | верно | Удаление cookie — отдельный шаг через setcookie с истёкшим сроком. |
T12-L8 1.07 c | Configuration and security | Without calling session_start(), the $_SESSION array is automatically populated with session data. | «no» Пояснение: You must explicitly call session_start() before $_SESSION is available and populated with session data.
Raw{"answer": "no", "explanation": "You must explicitly call session_start() before $_SESSION is available and populated with session data."} | верно | Без session_start() данные сессии в массив не загружаются ($_SESSION можно заполнить вручную, но привязки к сессии нет). |
VC-L1 5.01 c | PHP 8.4–8.5 | In which PHP version was the array_find() function introduced? | «no» Пояснение: There is no built-in PHP function called array_find(); the closest equivalent is array_search(), so it was never introduced.
Raw{"answer": "no", "explanation": "There is no built-in PHP function called array_find(); the closest equivalent is array_search(), so it was never introduced."} | неверно верный: «8.4» | PHP 8.4 (RFC array_find). |
VC-L2 2.32 c | PHP 8.4–8.5 | Property hooks (get/set right in the property declaration) landed in PHP 8.4. | «yes» Пояснение: Property hooks (get/set defined directly in the property declaration) were indeed introduced in PHP 8.4.
Raw{"answer": "yes", "explanation": "Property hooks (get/set defined directly in the property declaration) were indeed introduced in PHP 8.4."} | верно | Property hooks — PHP 8.4 (ноябрь 2024). |
VC-L3 2.49 c | PHP 8.4–8.5 | Asymmetric visibility (public private(set) string $name) appeared in PHP 8.4. | «yes» Пояснение: PHP 8.4 introduced asymmetric visibility for properties, allowing syntax like public private(set) string $name to restrict writing to private scope while keeping reads public.
Raw{"answer": "yes", "explanation": "PHP 8.4 introduced asymmetric visibility for properties, allowing syntax like public private(set) string $name to restrict writing to private scope while keeping reads public."} | верно | Asymmetric visibility v2 — PHP 8.4. |
VC-L4 4.94 c | PHP 8.4–8.5 | In which PHP version was the #[\NoDiscard] attribute introduced? Answer with the version number. | «does not exist» Пояснение: The #[\NoDiscard] attribute is not a recognized PHP attribute in any released PHP version.
Raw{"answer": "does not exist", "explanation": "The #[\\NoDiscard] attribute is not a recognized PHP attribute in any released PHP version."} | неверно верный: «8.5» | #[\NoDiscard] — PHP 8.5 (marking return values as important). |
VC-L5 1.01 c | PHP 8.4–8.5 | In which PHP version did the pipe operator |> first appear? Answer with the version number. | «8.1» Пояснение: The pipe operator |>, used to pipe values between functions, was introduced in PHP 8.1.
Raw{"answer": "8.1", "explanation": "The pipe operator |>, used to pipe values between functions, was introduced in PHP 8.1."} | неверно верный: «8.5» | Pipe operator — PHP 8.5 (2025). |
VC-L6 3.34 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 'clone-with' syntax clone($obj, ['x' => 1]) does not exist in any version of PHP; clone is a unary operator that only takes an object operand and no associative array argument.
Raw{"answer": "no", "explanation": "The 'clone-with' syntax clone($obj, ['x' => 1]) does not exist in any version of PHP; clone is a unary operator that only takes an object operand and no associative array argument."} | неверно верный: «8.5» | Clone with v2 — PHP 8.5. |
VC-L7 5.55 c | PHP 8.4–8.5 | In which PHP version were the array_first() and array_last() functions introduced? | «none – array_first() and array_last() are not built-in php functions in any version» Пояснение: PHP has never included array_first() or array_last() as standard library functions; equivalent functionality is typically achieved with array_slice(), array_values(), or custom helper functions.
Raw{"answer": "None – array_first() and array_last() are not built-in PHP functions in any version", "explanation": "PHP has never included array_first() or array_last() as standard library functions; equivalent functionality is typically achieved with array_slice(), array_values(), or custom helper functions."} | неверно верный: «8.5» | PHP 8.5. |
VC-L8 7.61 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. | «no» Пояснение: RFC 'Partial Function Application v2' does not appear to have been adopted into any PHP version as of 2026-11-07; no such accepted RFC exists in the PHP roadmap.
Raw{"answer":"no","explanation":"RFC 'Partial Function Application v2' does not appear to have been adopted into any PHP version as of 2026-11-07; no such accepted RFC exists in the PHP roadmap."} | неверно верный: «8.6» | PFA v2 принят 05.12.2025 (33-0-0), реализован в PHP 8.6. |
VF-L1 4.12 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.1» Пояснение: The clamp_v2 RFC was accepted and the clamp() function was implemented in PHP 8.1.
Raw{"answer":"8.1","explanation":"The clamp_v2 RFC was accepted and the clamp() function was implemented in PHP 8.1."} | неверно верный: «8.6» | По данным владельца (wiki.php.net/rfc): clamp_v2 — 8.6; clamp() в 8.5.11 отсутствует (косвенное подтверждение). Дата-якорь делает клетку монотонной. |
VF-L2 1.91 c | PHP: 8.6+ and the future | RFC Context Managers v2 has already been adopted in PHP (as of 2026-11-07). | «no» Пояснение: Context Managers are a Python concept; PHP has no 'Context Managers v2' RFC, and no such feature exists in PHP's RFC process.
Raw{"answer": "no", "explanation": "Context Managers are a Python concept; PHP has no 'Context Managers v2' RFC, and no such feature exists in PHP's RFC process."} | верно | На 06.11.2026 — в обсуждении (создан 2026-10-23); не принят. |
VF-L3 4.52 c | PHP: 8.6+ and the future | RFC Bound-Erased Generic Types (generics) was declined in 2026. | «no» Пояснение: There is no PHP RFC by the name 'Bound-Erased Generic Types' that was declined in 2026; this does not correspond to a known PHP RFC.
Raw{"answer": "no", "explanation": "There is no PHP RFC by the name 'Bound-Erased Generic Types' that was declined in 2026; this does not correspond to a known PHP RFC."} | неверно верный: «yes» | Голосование завершилось 2026-06-28: отклонён (wiki.php.net/rfc). |
VF-L4 3.46 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» Пояснение: No PHP RFC enabling ZTS (Zend Thread Safety) as the default build has been accepted; the default PHP build remains non-ZTS (single-threaded) for performance reasons.
Raw{"answer": "no", "explanation": "No PHP RFC enabling ZTS (Zend Thread Safety) as the default build has been accepted; the default PHP build remains non-ZTS (single-threaded) for performance reasons."} | верно | Такого принятого RFC нет на дату якоря; якорь делает клетку монотонной — при принятии RFC позже клетка не перевернётся. |
VF-L5 3.67 c | PHP: 8.6+ and the future | As of PHP 8.5, generics (parameterized types) are still absent. | «yes» Пояснение: PHP has not introduced parameterized types (generics) in any released version, including PHP 8.5, though it does support type hints and docblock annotations.
Raw{"answer": "yes", "explanation": "PHP has not introduced parameterized types (generics) in any released version, including PHP 8.5, though it does support type hints and docblock annotations."} | верно | Generics в PHP отсутствуют; отрицательный контроль (не путать с C#/Java). |
VF-L6 10.13 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). | «no» Пояснение: PHP follows an annual minor release cycle, so if PHP 8.5 is the latest stable in November 2026, PHP 8.6 would not have a GA date just 12 days later; it would be expected around November 2027.
Raw{"answer": "no", "explanation": "PHP follows an annual minor release cycle, so if PHP 8.5 is the latest stable in November 2026, PHP 8.6 would not have a GA date just 12 days later; it would be expected around November 2027."} | неверно верный: «yes» | 8.5 — релиз осени 2025; 8.6 GA 19.11.2026 (wiki.php.net/todo/php86). Дата снимка — 06.11.2026. |
VF-L7 2.74 c | PHP: 8.6+ and the future | The PHP 6 branch never shipped: after PHP 5.6 came PHP 7.0 directly. | «yes» Пояснение: The PHP 6 branch was never released as a stable version; its work was carried forward and eventually shipped as PHP 7.0, so PHP 5.6 was followed directly by PHP 7.0 in the stable release lineage.
Raw{"answer": "yes", "explanation": "The PHP 6 branch was never released as a stable version; its work was carried forward and eventually shipped as PHP 7.0, so PHP 5.6 was followed directly by PHP 7.0 in the stable release lineage."} | верно | Исторический факт: ветка 6 не была релизнута. |
VF-L8 2.18 c | PHP: 8.6+ and the future | The RFC adding the #[\Deprecated] attribute to the core was adopted. | «yes» Пояснение: The RFC to add the #[\Deprecated] attribute to PHP core was adopted and included in PHP 8.4.
Raw{"answer": "yes", "explanation": "The RFC to add the #[\\Deprecated] attribute to PHP core was adopted and included in PHP 8.4."} | верно | #[\Deprecated] — принят, реализован в PHP 8.4. |
T25-L1 1.67 c | Clean architecture | The dependency rule of clean and onion architecture: inner layers know nothing about outer ones — dependencies point toward the center. | «yes» Пояснение: In both clean and onion architecture, dependencies point inward toward the core, and inner layers must not depend on outer layers.
Raw{"answer": "yes", "explanation": "In both clean and onion architecture, dependencies point inward toward the core, and inner layers must not depend on outer layers."} | верно | Чистая (Robert C. Martin), луковичная (Jeffrey Palermo) и гексагональная (ports & adapters) — варианты одной идеи: зависимости направлены внутрь, к домену. Слоями в проекте следит deptrac. |
T25-L2 1.77 c | Clean architecture | Domain entities import neither Doctrine nor Symfony — only the language and, possibly, the standard library. | «yes» Пояснение: In DDD, the domain layer must be free of external dependencies; it should depend only on the language itself (and possibly the standard library), never on infrastructure such as Doctrine or Symfony.
Raw{"answer": "yes", "explanation": "In DDD, the domain layer must be free of external dependencies; it should depend only on the language itself (and possibly the standard library), never on infrastructure such as Doctrine or Symfony."} | верно | Изоляция домена от инфраструктуры; deptrac в проекте как раз следит за слоями. |
T25-L3 2.5 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/view layer, not the business-logic layer; they call use cases but that does not make them part of the business-logic layer — the business logic resides within the use cases themselves.
Raw{"answer": "no", "explanation": "Controllers and Twig templates belong to the presentation/view layer, not the business-logic layer; they call use cases but that does not make them part of the business-logic layer — the business logic resides within the use cases themselves."} | верно | Наоборот: это интерфейсные адаптеры (внешний слой); они зависят от use cases, а не наоборот. |
T25-L4 0.98 c | Clean architecture | What sits at the very center of the onion architecture? | «domain layer» Пояснение: In the Onion Architecture, the innermost layer at the very center is the Domain Layer, which contains the core business rules and logic independent of any framework or infrastructure details.
Raw{"answer": "Domain Layer", "explanation": "In the Onion Architecture, the innermost layer at the very center is the Domain Layer, which contains the core business rules and logic independent of any framework or infrastructure details."} | неверно верный: «domain model» | Центральное кольцо — Domain Model: сущности и бизнес-правила без зависимостей; далее Domain Services → Application Services → Infrastructure/UI/Tests (Palermo). |
T25-L5 1.58 c | Clean architecture | Layer boundary violations can be caught automatically: a layer-dependency analyzer (e.g. deptrac) fails on a forbidden call. | «yes» Пояснение: deptrac is a static-analysis tool that automatically detects forbidden cross-layer calls and fails the build, enabling layer boundary violations to be caught automatically in CI/CD pipelines.
Raw{"answer": "yes", "explanation": "deptrac is a static-analysis tool that automatically detects forbidden cross-layer calls and fails the build, enabling layer boundary violations to be caught automatically in CI/CD pipelines."} | верно | depfile.yaml в проекте TasK: CI проверяет правила слоёв на каждом пайплайне. |
T25-L6 3.1 c | Clean architecture | A use case (interactor) may accept an HTTP request or an EntityManager as arguments — it is simpler that way. | «no» Пояснение: A use case should remain decoupled from transport and persistence layers; accepting an HTTP Request or an EntityManager couples it to framework-specific infrastructure, making it harder to test and reuse.
Raw{"answer":"no","explanation":"A use case should remain decoupled from transport and persistence layers; accepting an HTTP Request or an EntityManager couples it to framework-specific infrastructure, making it harder to test and reuse."} | верно | Use case принимает DTO и порты; привязка к HTTP/ORM протекает инфраструктуру во внутренние слои. |
T25-L7 1.38 c | Clean architecture | What is the component called that provides a collection of aggregates/entities while hiding the storage mechanism behind an interface? | «repository» Пояснение: A Repository is a domain layer component that acts as an in-memory collection of aggregates/entities while abstracting the storage mechanism (database, file, etc.) behind an interface.
Raw{"answer": "Repository", "explanation": "A Repository is a domain layer component that acts as an in-memory collection of aggregates/entities while abstracting the storage mechanism (database, file, etc.) behind an interface."} | верно | Repository pattern (DDD/Evans); в проекте — Doctrine-репозитории за портами. |
T25-L8 2.63 c | Clean architecture | In clean architecture, swapping PostgreSQL for another database touches only the outer layer — the domain and use cases stay unchanged. | «yes» Пояснение: In clean architecture, the database is an infrastructure concern at the outermost layer, so the domain and use cases remain decoupled and unaffected by swapping PostgreSQL for another database.
Raw{"answer": "yes", "explanation": "In clean architecture, the database is an infrastructure concern at the outermost layer, so the domain and use cases remain decoupled and unaffected by swapping PostgreSQL for another database."} | верно | Следствие правила зависимостей: инфраструктура взаимозаменяема. |
T26-L1 1.99 c | DDD | In DDD, an aggregate is just another name for a database table. | «no» Пояснение: An aggregate is a domain-level boundary of consistency (a cluster of entities/value objects around an aggregate root), not a physical database table; the mapping between the two is an implementation concern.
Raw{"answer": "no", "explanation": "An aggregate is a domain-level boundary of consistency (a cluster of entities/value objects around an aggregate root), not a physical database table; the mapping between the two is an implementation concern."} | верно | Агрегат — кластер объектов с границей согласованности (транзакционной вокруг корня); таблица — деталь хранения. |
T26-L2 1.54 c | DDD | A Value Object is immutable and compared by the values of its fields, not by identity. | «yes» Пояснение: A Value Object is by definition immutable and its equality is determined by comparing its field values rather than object identity (reference equality).
Raw{"answer": "yes", "explanation": "A Value Object is by definition immutable and its equality is determined by comparing its field values rather than object identity (reference equality)."} | верно | Классика Evans: Money, Email; равенство структурное. |
T26-L3 0.8 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 external entry point of an aggregate, through which all modifications to the aggregate must be made.
Raw{"answer": "Aggregate Root", "explanation": "In Domain-Driven Design, the Aggregate Root is the single external entry point of an aggregate, through which all modifications to the aggregate must be made."} | верно | Aggregate Root: внешние объекты ссылаются только на корень; он защищает инварианты агрегата. |
T26-L4 1.43 c | DDD | In DDD, a repository is declared for an aggregate (its root), not for every entity. | «yes» Пояснение: In DDD, a repository is associated with an aggregate root, which serves as the boundary for persisting and loading the entire aggregate, rather than being created for each individual entity within it.
Raw{"answer": "yes", "explanation": "In DDD, a repository is associated with an aggregate root, which serves as the boundary for persisting and loading the entire aggregate, rather than being created for each individual entity within it."} | верно | Репозиторий корня хранит границу согласованности агрегата; вложенные сущности доступны только через корень. |
T26-L5 1.77 c | DDD | Ubiquitous language is the model's shared language common to developers and domain experts. | «yes» Пояснение: In Domain-Driven Design, Ubiquitous Language is indeed the shared vocabulary used by both developers and domain experts that permeates the model and all communications.
Raw{"answer":"yes","explanation":"In Domain-Driven Design, Ubiquitous Language is indeed the shared vocabulary used by both developers and domain experts that permeates the model and all communications."} | верно | Evans: язык из требований переходит в имена классов и методов. |
T26-L6 7.88 c | DDD | What is the boundary called within which a model and its language are consistent, while outside the same words mean other models? | «domain» Пояснение: In model theory, the domain (or universe of discourse) is the boundary within which a structure/model consistently interprets the language, while in other domains the same symbols are interpreted differently.
Raw{"answer": "domain", "explanation": "In model theory, the domain (or universe of discourse) is the boundary within which a structure/model consistently interprets the language, while in other domains the same symbols are interpreted differently."} | неверно верный: «bounded context» | Bounded Context; «Заказ» в биллинге и в доставке — разные модели. |
T26-L7 1.83 c | DDD | An anemic model (objects with only getters/setters, logic in services) is the recommended DDD style. | «no» Пояснение: DDD advocates for a rich domain model where business logic and invariants are encapsulated within domain objects, rather than an anemic model where logic is pushed into separate service classes.
Raw{"answer": "no", "explanation": "DDD advocates for a rich domain model where business logic and invariants are encapsulated within domain objects, rather than an anemic model where logic is pushed into separate service classes."} | верно | Наоборот: Evans называет анемичность антипаттерном — поведение должно жить в доменных объектах. |
T26-L8 2.27 c | DDD | Bounded context means each context has its own model: the same concept in different contexts is a different class. | «yes» Пояснение: In Domain-Driven Design, a bounded context is a clearly defined boundary within which a specific model is valid, allowing the same concept to be represented as a different class with different attributes in each context.
Raw{"answer": "yes", "explanation": "In Domain-Driven Design, a bounded context is a clearly defined boundary within which a specific model is valid, allowing the same concept to be represented as a different class with different attributes in each context."} | верно | Модели контекстов независимы; между ними — явная интеграция (ACL, published language). |
T13-L1 1.16 c | Symfony | Services in the Symfony DI container are created lazily by default — on first use. | «yes» Пояснение: Symfony's DI container stores service definitions (factories) by default and instantiates a service only when it is first requested via get(), making it lazy by default.
Raw{"answer":"yes","explanation":"Symfony's DI container stores service definitions (factories) by default and instantiates a service only when it is first requested via get(), making it lazy by default."} | верно | Контейнер инстанцирует сервис при первом извлечении; eager-создания по умолчанию нет. |
T13-L2 3.96 c | Symfony | Which Symfony console command lists all registered routes? | «php bin/console routing» Пояснение: This Symfony console command displays a list of all registered routes in the application.
Raw{"answer": "php bin/console routing", "explanation": "This Symfony console command displays a list of all registered routes in the application."} | неверно верный: «debug:router» | bin/console debug:router (FrameworkBundle); в Symfony 3 команда называлась router:debug. |
T13-L3 1.52 c | Symfony | Symfony autowiring requires manually declaring every service in services.yaml. | «no» Пояснение: Symfony autowiring automatically detects and registers services without requiring manual declarations in services.yaml for every single service.
Raw{"answer": "no", "explanation": "Symfony autowiring automatically detects and registers services without requiring manual declarations in services.yaml for every single service."} | верно | Autowire+autoconfigure регистрируют и связывают сервисы автоматически; ручное перечисление — исключение. |
T13-L4 2.67 c | Symfony | Twig templates are compiled into PHP classes and cached between requests. | «yes» Пояснение: Twig compiles templates into PHP classes (extending Twig\Template) and caches the compiled output in a cache directory between requests.
Raw{"answer": "yes", "explanation": "Twig compiles templates into PHP classes (extending Twig\\Template) and caches the compiled output in a cache directory between requests."} | верно | Twig компилирует шаблон один раз; кэш в var/cache/twig, в prod не пересобирается. |
T13-L5 1.9 c | Symfony | In the Symfony dev environment the DI container is rebuilt only after tracked files change, not on every request. | «yes» Пояснение: In Symfony's development environment, the container is cached after the first compilation and only rebuilt when tracked files (e.g., classes, configuration) are detected to have changed, rather than on every request.
Raw{"answer": "yes", "explanation": "In Symfony's development environment, the container is cached after the first compilation and only rebuilt when tracked files (e.g., classes, configuration) are detected to have changed, rather than on every request."} | верно | Kernel проверяет freshness ресурсов (конфиги, классы); иначе переиспользуется кэш контейнера. |
T13-L6 0.99 c | Symfony | Which environment variable selects the active Symfony environment (dev/prod)? | «symfony_env» Пояснение: The SYMFONY_ENV environment variable is used to select the active Symfony environment (e.g., dev, prod, test).
Raw{"answer": "SYMFONY_ENV", "explanation": "The SYMFONY_ENV environment variable is used to select the active Symfony environment (e.g., dev, prod, test)."} | неверно верный: «app_env» | APP_ENV в .env; APP_DEBUG — отдельный флаг отладки. |
T13-L7 1.32 c | Symfony | A controller method can be private — Symfony routing works with any method of the class. | «no» Пояснение: In Symfony, routed controller methods must be public; the framework invokes them via reflection which requires public visibility, so private methods cannot be used as action methods.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "In Symfony, routed controller methods must be public; the framework invokes them via reflection which requires public visibility, so private methods cannot be used as action methods." ⏎ } | верно | Действие контроллера должно быть public; приватный метод по маршруту не вызывается. |
T13-L8 2.6 c | Symfony | Event subscribers always receive events before listeners, because the interface gives them priority. | «no» Пояснение: PHP does not have a built-in event system that grants inherent priority to subscribers over listeners; in frameworks like Symfony, dispatch order is determined by numerical priority values, not by the interface type.
Raw{"answer": "no", "explanation": "PHP does not have a built-in event system that grants inherent priority to subscribers over listeners; in frameworks like Symfony, dispatch order is determined by numerical priority values, not by the interface type."} | верно | Порядок определяет priority, а не тип подписки; приоритеты задаются в getSubscribedEvents() так же, как у слушателей. |
T22-L1 2.38 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» Пояснение: The deprecated guard system (GuardedUser, GuardedSession, etc.) was removed in Symfony 6.0, leaving AuthenticatorInterface and related classes as the authentication foundation.
Raw{"answer": "yes", "explanation": "The deprecated guard system (GuardedUser, GuardedSession, etc.) was removed in Symfony 6.0, leaving AuthenticatorInterface and related classes as the authentication foundation."} | верно | Guard объявлен устаревшим в 5.3 и удалён в 6.0; в проекте symfony/security-bundle 8.1. |
T22-L2 1.41 c | Symfony: Security and forms | Which Symfony attribute checks a role/permission right on a controller method (403 without it)? | «isgranted» Пояснение: The Symfony #[IsGranted] attribute checks for a permission or role on a controller method, returning a 403 Forbidden if the user does not have the required right.
Raw{"answer": "IsGranted", "explanation": "The Symfony #[IsGranted] attribute checks for a permission or role on a controller method, returning a 403 Forbidden if the user does not have the required right."} | верно | #[IsGranted('ROLE_ADMIN')]; атрибут из symfony/security-http. |
T22-L3 9.45 c | Symfony: Security and forms | Voters are Symfony's mechanism for checking access to a specific object: isGranted('EDIT', $post). | «no» Пояснение: isGranted('EDIT', $post) with an object argument is the Access Control List (ACL) pattern in Symfony; voters are a separate authorization mechanism that implement VoterInterface and handle decisions through their own logic.
Raw{"answer": "no", "explanation": "isGranted('EDIT', $post) with an object argument is the Access Control List (ACL) pattern in Symfony; voters are a separate authorization mechanism that implement VoterInterface and handle decisions through their own logic."} | неверно верный: «yes» | VoterInterface->vote(); docs Symfony — Voters. |
T22-L4 7.96 c | Symfony: Security and forms | In modern Symfony (7+) validation constraints are declared as PHP attributes (#[Assert\NotBlank]); doctrine annotations are no longer supported. | «yes» Пояснение: In Symfony 7+ (backed by Doctrine 3.0), validation constraints are written with PHP attributes like #[Assert\NotBlank], and Doctrine annotations have been removed entirely in favor of PHP attributes.
Raw{"answer": "yes", "explanation": "In Symfony 7+ (backed by Doctrine 3.0), validation constraints are written with PHP attributes like #[Assert\\NotBlank], and Doctrine annotations have been removed entirely in favor of PHP attributes."} | верно | Докблок-аннотации удалены в Symfony 7.0; стандарт — атрибуты. В проекте symfony/validator 8.1. |
T22-L5 1.91 c | Symfony: Security and forms | CSRF protection of Symfony forms is enabled by default: the form validates the token on submission. | «yes» Пояснение: Symfony's Form component automatically includes and validates a CsrfToken field on submission by default.
Raw{"answer":"yes","explanation":"Symfony's Form component automatically includes and validates a CsrfToken field on submission by default."} | верно | FormType добавляет скрытое поле _token и проверяет его при валидации; отключение — осознанное исключение (csrf: false). |
T22-L6 1.29 c | Symfony: Security and forms | Form validation in Symfony runs server-side even if the client-side (HTML5) checks passed. | «yes» Пояснение: Symfony always performs server-side validation via the Validator component when a form is submitted, regardless of whether HTML5 client-side checks passed.
Raw{"answer": "yes", "explanation": "Symfony always performs server-side validation via the Validator component when a form is submitted, regardless of whether HTML5 client-side checks passed."} | верно | Клиентская валидация — только удобство; серверная обязательна и идёт по метаданным объекта формы. |
T22-L7 0.61 c | Symfony: Security and forms | Which Symfony maker command generates a form class (FormType)? | «make:form» Пояснение: The Symfony MakerBundle command 'make:form' generates a new FormType class.
Raw{"answer": "make:form", "explanation": "The Symfony MakerBundle command 'make:form' generates a new FormType class."} | верно | bin/console make:form (symfony/maker-bundle — в проекте). |
T22-L8 1.79 c | Symfony: Security and forms | Symfony stores the user's password in the session in plain text. | «no» Пояснение: Symfony does not store the password in the session; it only stores the user's identity (e.g., username, email) after successful authentication, while the actual password is never placed in the session.
Raw{"answer": "no", "explanation": "Symfony does not store the password in the session; it only stores the user's identity (e.g., username, email) after successful authentication, while the actual password is never placed in the session."} | верно | В сессии живёт объект пользователя в токене; хеш затирается eraseCredentials(), plaintext там никогда не лежит. |
T23-L1 1.39 c | Symfony: configuration and services | Symfony bundle configuration lives in config/packages — one file per bundle or topic. | «yes» Пояснение: In modern Symfony projects, bundle and component configuration files are placed in the config/packages directory, typically one file per bundle or topic (e.g., twig.yaml, security.yaml, doctrine.yaml).
Raw{"answer": "yes", "explanation": "In modern Symfony projects, bundle and component configuration files are placed in the config/packages directory, typically one file per bundle or topic (e.g., twig.yaml, security.yaml, doctrine.yaml)."} | верно | Стандартная структура (config/packages/*.yaml); перегрузка — config/packages/<env>. |
T23-L2 1.4 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 standard convention: a committed .env file holds harmless dev defaults, while .env.local (git-ignored) holds sensitive secrets.
Raw{"answer": "yes", "explanation": "This is a standard convention: a committed .env file holds harmless dev defaults, while .env.local (git-ignored) holds sensitive secrets."} | верно | symfony/dotenv: .env — общий безопасный набор значений; локальные секреты — .env.local (gitignored) или secrets-хранилище. |
T23-L3 1.13 c | Symfony: configuration and services | Which Symfony command lists the container's registered services and their aliases? | «debug:container» Пояснение: The Symfony command debug:container displays the container's registered services and their aliases.
Raw{"answer": "debug:container", "explanation": "The Symfony command debug:container displays the container's registered services and their aliases."} | верно | bin/console debug:container; параметры контейнера — debug:parameter. |
T23-L4 2.79 c | Symfony: configuration and services | The Symfony container allows changing parameters at runtime: $container->setParameter() works from a controller. | «no» Пояснение: The Symfony container's parameters are set during container compilation (via the ContainerBuilder), and once the container is finalized (as it is in a controller), setParameter() is not a supported runtime operation.
Raw{"answer": "no", "explanation": "The Symfony container's parameters are set during container compilation (via the ContainerBuilder), and once the container is finalized (as it is in a controller), setParameter() is not a supported runtime operation."} | верно | Контейнер компилируется и замораживается; runtime-значения — только через переменные окружения. |
T23-L5 1.14 c | Symfony: configuration and services | By default, Symfony services are public (public: true) — you can fetch them directly from the container. | «no» Пояснение: By default, Symfony services are private (public: false), so they cannot be fetched directly from the container unless explicitly marked as public: true.
Raw{"answer":"no","explanation":"By default, Symfony services are private (public: false), so they cannot be fetched directly from the container unless explicitly marked as public: true."} | верно | С Symfony 4.0 сервисы по умолчанию private: инжектятся через autowiring; $container->get() — только для публичных. |
T23-L6 1.27 c | Symfony: configuration and services | Without a config file in config/packages a bundle will not work — configuration is mandatory for every bundle. | «no» Пояснение: Configuration is not mandatory for every bundle; many bundles work fine without any configuration in config/packages, relying on sensible defaults or being self-contained.
Raw{"answer": "no", "explanation": "Configuration is not mandatory for every bundle; many bundles work fine without any configuration in config/packages, relying on sensible defaults or being self-contained."} | верно | У бандлов есть встроенные умолчания (Extension); конфиг нужен только для отклонений от них. |
T23-L7 1.93 c | Symfony: configuration and services | Environment variable values are injected into services.yaml using the %env(VAR)% syntax. | «yes» Пояснение: In Symfony, the %env(VAR)% parameter resolver is used to inject environment variable values into configuration files such as services.yaml.
Raw{"answer": "yes", "explanation": "In Symfony, the %env(VAR)% parameter resolver is used to inject environment variable values into configuration files such as services.yaml."} | верно | %env(...)% резолвится в рантайме env-процессорами; docs — Env Var Processors. |
T23-L8 0.98 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 enables debug mode, which activates the web profiler and Twig debugging features.
Raw{"answer": "APP_DEBUG", "explanation": "The APP_DEBUG environment variable in Symfony enables debug mode, which activates the web profiler and Twig debugging features."} | верно | APP_DEBUG=1 (в .env dev-окружения); окружение выбирает APP_ENV — см. T13-L6. |
T16-L1 1.24 c | Symfony: Messenger | A single message in Symfony Messenger can only have one handler. | «no» Пояснение: A single message in Symfony Messenger can be handled by multiple handlers; any number of listeners/handlers can be registered for the same message class, and they will all be invoked when that message is dispatched.
Raw{"answer": "no", "explanation": "A single message in Symfony Messenger can be handled by multiple handlers; any number of listeners/handlers can be registered for the same message class, and they will all be invoked when that message is dispatched."} | верно | Messenger вызывает все хендлеры, подписанные на класс сообщения (docs — Multiple Handlers). |
T16-L2 1.6 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 within the same request cycle by calling the handler directly; it does not put the message into a queue for a separate worker to consume.
Raw{"answer":"no","explanation":"The sync transport processes the message immediately within the same request cycle by calling the handler directly; it does not put the message into a queue for a separate worker to consume."} | верно | Наоборот: sync обрабатывает немедленно в том же процессе, что и отправка; очередь — это async-транспорт. |
T16-L3 1.15 c | Symfony: Messenger | Which console command starts the worker that processes Messenger queue messages? | «bin/console messenger:consume» Пояснение: The messenger:consume command starts a Symfony Messenger worker that polls and processes messages from the configured transport.
Raw{"answer": "bin/console messenger:consume", "explanation": "The messenger:consume command starts a Symfony Messenger worker that polls and processes messages from the configured transport."} | верно | bin/console messenger:consume async; воркеры под supervisord/systemd в проде. |
T16-L4 1.42 c | Symfony: Messenger | Retries for failed messages (retry_strategy) are configured per Messenger transport. | «yes» Пояснение: In Symfony Messenger, the retry strategy options (such as num_retries, backoff, time_limit, and max_delay) are defined at the transport level in the configuration, not per individual message.
Raw{"answer": "yes", "explanation": "In Symfony Messenger, the retry strategy options (such as num_retries, backoff, time_limit, and max_delay) are defined at the transport level in the configuration, not per individual message."} | верно | retry_strategy на транспорте: max_retries, delay, multiplier; docs — Failed Messages & Retries. |
T16-L5 5.67 c | Symfony: Messenger | By default, Messenger serializes messages to JSON. | «yes» Пояснение: Symfony Messenger uses JSON encoding (application/json) as the default serializer for messages sent over the transport.
Raw{"answer": "yes", "explanation": "Symfony Messenger uses JSON encoding (application/json) as the default serializer for messages sent over the transport."} | неверно верный: «no» | Дефолтный сериализатор — PhpSerializer (serialize()); JSON-сериализатор включается отдельно. |
T16-L6 5.37 c | Symfony: Messenger | Symfony Scheduler produces messages on a schedule and dispatches them through Messenger. | «no» Пояснение: Symfony Scheduler schedules the execution of tasks (callbacks or commands) at defined intervals; it does not specifically produce and dispatch Messenger messages.
Raw{"answer":"no","explanation":"Symfony Scheduler schedules the execution of tasks (callbacks or commands) at defined intervals; it does not specifically produce and dispatch Messenger messages."} | неверно верный: «yes» | Schedule → RecurringMessage → шина Messenger; docs — Scheduler. |
T16-L7 1.56 c | Symfony: Messenger | Which built-in Messenger transport stores messages in database tables via Doctrine? | «db» Пояснение: In Symfony Messenger, the 'db' transport persists messages to database tables managed by Doctrine ORM.
Raw{"answer": "db", "explanation": "In Symfony Messenger, the 'db' transport persists messages to database tables managed by Doctrine ORM."} | неверно верный: «doctrine» | Транспорт doctrine (symfony/doctrine-messenger); таблица messenger_messages. В проекте стоит amqp-messenger + doctrine-messenger. |
T16-L8 1.25 c | Symfony: Messenger | The Messenger pipeline can be extended with custom middleware, placed before or after the built-in ones. | «yes» Пояснение: Symfony's Messenger pipeline supports registering custom middleware with 'after' and 'before' options to interleave them with built-in middleware in the chain.
Raw{"answer": "yes", "explanation": "Symfony's Messenger pipeline supports registering custom middleware with 'after' and 'before' options to interleave them with built-in middleware in the chain."} | верно | messenger.bus.*.middleware в yaml; docs — Middleware. |
T28-L1 5.99 c | Symfony: versions | Symfony major releases come every two years, minor ones every six months (in May and November). | «no» Пояснение: Symfony major releases have historically been annual (not biennial), and minor releases occur in April and November (not May and November).
Raw{"answer": "no", "explanation": "Symfony major releases have historically been annual (not biennial), and minor releases occur in April and November (not May and November)."} | неверно верный: «yes» | Стандартный релизный цикл: 8.0 — ноябрь 2025, 8.1 — май 2026, 8.2 — ноябрь 2026. |
T28-L2 2.17 c | Symfony: versions | What is the minimum PHP version required by Symfony 8? | «8.2» Пояснение: Symfony 8 requires a minimum PHP version of 8.2, following the pattern of each major version raising the minimum PHP requirement.
Raw{"answer": "8.2", "explanation": "Symfony 8 requires a minimum PHP version of 8.2, following the pattern of each major version raising the minimum PHP requirement."} | неверно верный: «8.4» | Symfony 8.0 поднял требование до PHP >= 8.4.1 (в vendor проекта: "php": ">=8.4.1"). |
T28-L3 1.94 c | Symfony: versions | Symfony 7.0 kept support for docblock annotations (validation, routes). | «no» Пояснение: Symfony 7.0 removed support for docblock annotations; PHP attributes (introduced as the replacement in Symfony 6.x) are the only supported way to define routes, validation, and similar metadata.
Raw{"answer": "no", "explanation": "Symfony 7.0 removed support for docblock annotations; PHP attributes (introduced as the replacement in Symfony 6.x) are the only supported way to define routes, validation, and similar metadata."} | верно | Наоборот: в 7.0 аннотации удалены — только PHP-атрибуты (#[Route], #[Assert\NotBlank]). |
T28-L4 3.13 c | Symfony: versions | AssetMapper manages CSS/JS without node or webpack — via importmap.php. | «yes» Пояснение: AssetMapper is a PHP library that provides a lightweight, Node/webpack-free approach to managing CSS and JS assets using an importmap.php file.
Raw{"answer": "yes", "explanation": "AssetMapper is a PHP library that provides a lightweight, Node/webpack-free approach to managing CSS and JS assets using an importmap.php file."} | верно | symfony/asset-mapper (с 6.3, стандарт с 7.x); в проекте — importmap.php в корне и asset-mapper 8.1. |
T28-L5 4.36 c | Symfony: versions | Symfony 6.4 is a regular release without long-term support. | «no» Пояснение: Symfony 6.4 is an even-minor release, which qualifies for long-term support (LTS) with 3 years of bug fixes, not a regular release without long-term support.
Raw{"answer": "no", "explanation": "Symfony 6.4 is an even-minor release, which qualifies for long-term support (LTS) with 3 years of bug fixes, not a regular release without long-term support."} | верно | Наоборот: 6.4 — LTS (расширенная поддержка); LTS выходит вместе с очередным мажором (6.4 — вместе с 7.0). |
T28-L6 2.46 c | Symfony: versions | When moving to a new Symfony major version, deprecations of the previous branch keep working — major releases do not remove them. | «no» Пояснение: Major Symfony releases remove deprecations introduced in the previous major version (e.g., 5.x deprecations are removed in 6.x), which is the entire purpose of the deprecation cycle.
Raw{"answer": "no", "explanation": "Major Symfony releases remove deprecations introduced in the previous major version (e.g., 5.x deprecations are removed in 6.x), which is the entire purpose of the deprecation cycle."} | верно | Наоборот: мажорный релиз удаляет всё устаревшее (7.0 убрал деприкейшены 6.x, 8.0 — 7.x). |
T28-L7 1.43 c | Symfony: versions | Every Symfony major release is accompanied by an UPGRADE guide listing the changes. | «yes» Пояснение: Symfony publishes an UPGRADE guide (UPGRADE.md) with each major release documenting breaking changes and deprecations.
Raw{"answer": "yes", "explanation": "Symfony publishes an UPGRADE guide (UPGRADE.md) with each major release documenting breaking changes and deprecations."} | верно | UPGRADE-7.0.md, UPGRADE-8.0.md в репозитории symfony/symfony. |
T28-L8 4.71 c | Symfony: versions | Which Symfony component manages assets and the importmap without node/webpack? | «assetmapper» Пояснение: The Symfony AssetMapper component (introduced in Symfony 7.1) manages static assets and generates importmaps in pure PHP without requiring Node.js or Webpack.
Raw{"answer": "AssetMapper", "explanation": "The Symfony AssetMapper component (introduced in Symfony 7.1) manages static assets and generates importmaps in pure PHP without requiring Node.js or Webpack."} | верно | symfony/asset-mapper 8.1 — в проекте. |
T29-L1 6.18 c | Symfony: 8.2 and beyond | As of 2026-11-07, Symfony 8.2 has already been released. | «no» Пояснение: Following Symfony's standard release cycle (major versions in November, minor versions in May), Symfony 8.2 would be expected around May 2027, so it would not yet be released as of November 7, 2026.
Raw{"answer": "no", "explanation": "Following Symfony's standard release cycle (major versions in November, minor versions in May), Symfony 8.2 would be expected around May 2027, so it would not yet be released as of November 7, 2026."} | верно | Наоборот: 8.2 ещё не выпущена — релиз в конце ноября 2026; последняя стабильная — 8.1. |
T29-L2 9.53 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, November 2026 would be Symfony 8.0 (a major release), not 8.2; Symfony 8.2 would be scheduled for November 2027.
Raw{"answer":"no","explanation":"Following the six-month cycle, November 2026 would be Symfony 8.0 (a major release), not 8.2; Symfony 8.2 would be scheduled for November 2027."} | неверно верный: «yes» | Политика релизов: 8.1 — май 2026, 8.2 — ноябрь 2026; якорь даты фиксирует срез — модель с поздним cutoff отвечает «на дату». |
T29-L3 3.1 c | Symfony: 8.2 and beyond | Which Symfony version comes after 8.1 (as of 2026-11-07)? | «8.2» Пояснение: Symfony follows a predictable minor release cycle, so the next version after 8.1 is 8.2.
Raw{"answer": "8.2", "explanation": "Symfony follows a predictable minor release cycle, so the next version after 8.1 is 8.2."} | верно | 8.2 — следующий минорный релиз (ноябрь 2026); после его выхода проект переходит с 8.1.* на 8.2.*. |
T29-L4 4.2 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 does not exist (as of current releases, the latest is 7.x), and even major Symfony releases follow deprecation cycles with migration tools rather than requiring a complete rewrite of applications.
Raw{"answer": "no", "explanation": "Symfony 8.2 does not exist (as of current releases, the latest is 7.x), and even major Symfony releases follow deprecation cycles with migration tools rather than requiring a complete rewrite of applications."} | верно | Наоборот: 8.2 — минорный релиз; новые возможности без поломки обратной совместимости. Мажор — 9.0. |
T29-L5 2.51 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 maintains backward compatibility between major releases, so code written for 8.1 should run correctly in 8.2 without modifications.
Raw{"answer": "yes", "explanation": "PHP maintains backward compatibility between major releases, so code written for 8.1 should run correctly in 8.2 without modifications."} | верно | Политика Symfony: минорные релизы обратно совместимы; BC-break допустим только в мажорных. |
T29-L6 2.31 c | Symfony: 8.2 and beyond | Which minor version of the 8.x branch is released last, before Symfony 9.0? | «8.4» Пояснение: Symfony 8.4 is the final minor release of the 8.x branch before Symfony 9.0 is released.
Raw{"answer":"8.4","explanation":"Symfony 8.4 is the final minor release of the 8.x branch before Symfony 9.0 is released."} | верно | По циклу: 8.2 (ноя 2026), 8.3 (май 2027), 8.4 (ноя 2027, вместе с 9.0) — как 6.4 выходила вместе с 7.0. |
T29-L7 4.35 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 minor releases within the same major version do not jump PHP requirements by several versions; Symfony 8.2 would continue to require the PHP version established for Symfony 8.0 (PHP 8.1), not PHP 8.5.
Raw{"answer": "no", "explanation": "Symfony minor releases within the same major version do not jump PHP requirements by several versions; Symfony 8.2 would continue to require the PHP version established for Symfony 8.0 (PHP 8.1), not PHP 8.5."} | верно | Наоборот: минорные релизы не поднимают требования PHP; для всей ветки 8.x остаётся PHP >= 8.4. |
T29-L8 3.2 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 are removed in the next major version, so deprecations added in the 8.x branch will be removed in Symfony 9.0 and not before.
Raw{"answer": "yes", "explanation": "Symfony's deprecation policy states that deprecations introduced in a major version are removed in the next major version, so deprecations added in the 8.x branch will be removed in Symfony 9.0 and not before."} | верно | Политика: деприкейшены живут до следующего мажора; 9.0 — ноябрь 2027. |
T21-L1 1.84 c | Twig | Inside {{ }}, Twig allows calling arbitrary PHP code directly. | «no» Пояснение: Twig's {{ }} expressions use a restricted template language and do not allow arbitrary PHP code to be written directly in templates, which is a security measure to separate logic from presentation.
Raw{"answer": "no", "explanation": "Twig's {{ }} expressions use a restricted template language and do not allow arbitrary PHP code to be written directly in templates, which is a security measure to separate logic from presentation."} | верно | Twig — DSL: только разрешённые окружением функции/фильтры; произвольный PHP не исполняется. |
T21-L2 0.93 c | Twig | By default, Twig auto-escapes printed variables. | «yes» Пояснение: Since Twig 1.12, autoescaping is enabled by default for all template output, which prevents XSS attacks.
Raw{"answer": "yes", "explanation": "Since Twig 1.12, autoescaping is enabled by default for all template output, which prevents XSS attacks."} | верно | Autoescape включён по умолчанию; {{ '<b>' }} → <b>. Проверено на Twig 3.30. |
T21-L3 1.49 c | Twig | The Twig |e filter escapes a string for safe output in an HTML context. | «yes» Пояснение: The Twig |e (escape) filter defaults to escaping output for an HTML context, though it can also target other contexts like 'js', 'css', or 'xml' when specified.
Raw{"answer": "yes", "explanation": "The Twig |e (escape) filter defaults to escaping output for an HTML context, though it can also target other contexts like 'js', 'css', or 'xml' when specified."} | верно | |e ('html') по умолчанию; есть контексты js/url/css. От SQL-инъекций он не защищает — это задача подготовленных запросов Doctrine. |
T21-L4 1.45 c | Twig | Which filter from twig/intl-extra formats a number according to a locale? | «intlnumberformat» Пояснение: The intlnumberformat filter from twig/intl-extra formats a number according to a locale.
Raw{"answer": "intlnumberformat", "explanation": "The intlnumberformat filter from twig/intl-extra formats a number according to a locale."} | неверно верный: «format_number» | |format_number(locale=...) из IntlExtension (twig/intl-extra есть в проекте). Проверено на Twig 3.30: 12345.6 → 12 345,6 (ru). |
T21-L5 1.78 c | Twig | The |raw filter disables auto-escaping for the value. | «yes» Пояснение: In Laravel's Blade templates, the {raw} filter (e.g., {{ $value|raw }}) bypasses the default htmlspecialchars auto-escaping, rendering the value as raw HTML.
Raw{"answer": "yes", "explanation": "In Laravel's Blade templates, the {raw} filter (e.g., {{ $value|raw }}) bypasses the default htmlspecialchars auto-escaping, rendering the value as raw HTML."} | верно | {{ x|raw }} выводит HTML как есть; опасно с пользовательскими данными. Проверено на Twig 3.30. |
T21-L6 1.14 c | Twig | In Twig, {{ }} prints an expression value, while {% %} executes tags — conditions, loops, set. | «yes» Пояснение: In Twig, {{ }} outputs an expression's value to the template, while {% %} is used for executing control-structure tags such as if, for, and set.
Raw{"answer": "yes", "explanation": "In Twig, {{ }} outputs an expression's value to the template, while {% %} is used for executing control-structure tags such as if, for, and set."} | верно | Два блока синтаксиса Twig: вывод (echo) против логики. |
T21-L7 1.42 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 inside a template using the {% set %} tag, so values are not limited to what the controller passes in.
Raw{"answer": "no", "explanation": "Twig allows you to declare variables inside a template using the {% set %} tag, so values are not limited to what the controller passes in."} | верно | {% set y = ... %} объявляет переменную в шаблоне. Проверено на Twig 3.30. |
T21-L8 0.68 c | Twig | Which Twig function dumps the debug structure of a variable (array, object)? | «dump()» Пояснение: The dump() function in Twig outputs a debug representation of a variable, showing its type and contents.
Raw{"answer": "dump()", "explanation": "The dump() function in Twig outputs a debug representation of a variable, showing its type and contents."} | верно | {{ dump(x) }} (DebugExtension; в Symfony доступна в dev-окружении). |
T24-L1 1.23 c | Bootstrap | Bootstrap is a CSS/JS library of ready-made UI components, not an SPA framework. | «yes» Пояснение: Bootstrap is a front-end UI component library (CSS, JS, Sass), not a single-page application (SPA) framework like React, Angular, or Vue.
Raw{"answer":"yes","explanation":"Bootstrap is a front-end UI component library (CSS, JS, Sass), not a single-page application (SPA) framework like React, Angular, or Vue."} | верно | Компоненты и утилиты поверх вашего HTML; SPA-фреймворки (React/Vue) — другой класс инструментов. В проекте vendored 5.3.3. |
T24-L2 3.07 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 container with a fixed max-width at each breakpoint (auto below the smallest breakpoint and fixed max-width at each larger breakpoint).
Raw{"answer":"container","explanation":"The .container class in Bootstrap provides a responsive container with a fixed max-width at each breakpoint (auto below the smallest breakpoint and fixed max-width at each larger breakpoint)."} | верно | .container (фиксированная макс-ширина по брейкпоинтам) vs .container-fluid (на всю ширину). |
T24-L3 2.4 c | Bootstrap | The Bootstrap grid is built on CSS floats and splits a row into 16 columns. | «no» Пояснение: The Bootstrap grid splits a row into 12 columns, not 16, and modern versions (Bootstrap 4/5) use Flexbox rather than CSS floats.
Raw{"answer": "no", "explanation": "The Bootstrap grid splits a row into 12 columns, not 16, and modern versions (Bootstrap 4/5) use Flexbox rather than CSS floats."} | верно | Наоборот: flexbox (с Bootstrap 4) и 12 колонок; float-сетка — это Bootstrap 3. |
T24-L4 3.25 c | Bootstrap | Bootstrap's named breakpoints (the infix used in class names) are sm, md, lg, xl, xxl — five of them. | «yes» Пояснение: In Bootstrap 4 and 5, there are five named breakpoints used as class-name infixes: sm, md, lg, xl, and xxl.
Raw{"answer":"yes","explanation":"In Bootstrap 4 and 5, there are five named breakpoints used as class-name infixes: sm, md, lg, xl, and xxl."} | верно | Тиров всего шесть: xs (без инфикса) + пять именованных (576/768/992/1200/1400 px). |
T24-L5 5.45 c | Bootstrap | Utilities like .mt-3 or .px-2 use the spacing scale: the number is a multiple of $spacer. | «yes» Пояснение: In Tailwind CSS, spacing utilities like .mt-3 and .px-2 are generated from the spacing scale, where the number corresponds to a value in that scale (typically a multiple of the base unit, 0.25rem).
Raw{"answer": "yes", "explanation": "In Tailwind CSS, spacing utilities like .mt-3 and .px-2 are generated from the spacing scale, where the number corresponds to a value in that scale (typically a multiple of the base unit, 0.25rem)."} | неверно верный: «no» | Spacing utilities; $spacer = 1rem. |
T24-L6 1.65 c | Bootstrap | Which Bootstrap 5 data attribute enables an interactive component (e.g. dropdown) on an element? | «data-bs-toggle» Пояснение: In Bootstrap 5, the data-bs-toggle attribute is the primary data attribute that enables interactive components such as dropdowns, modals, offcanvas, and tabs on an element.
Raw{"answer": "data-bs-toggle", "explanation": "In Bootstrap 5, the data-bs-toggle attribute is the primary data attribute that enables interactive components such as dropdowns, modals, offcanvas, and tabs on an element."} | верно | data-bs-toggle="dropdown" и т.п.; в Bootstrap 4 атрибут назывался data-toggle. |
T24-L7 0.98 c | Bootstrap | Bootstrap 5 components work without jQuery — in plain vanilla JS. | «yes» Пояснение: Bootstrap 5 dropped its jQuery dependency and implements its interactive components using vanilla JavaScript.
Raw{"answer":"yes","explanation":"Bootstrap 5 dropped its jQuery dependency and implements its interactive components using vanilla JavaScript."} | верно | jQuery удалён в Bootstrap 5.0: data-bs-* атрибуты и JS API. В проекте vendored 5.3.3. |
T24-L8 9.62 c | Bootstrap | Dark mode in Bootstrap is enabled with a .dark class on the root element. | «no» Пояснение: In Bootstrap 5, dark mode is enabled by adding the data-bs-theme="dark" attribute to the <body> element, not by adding a .dark class to the root (<html>) element.
Raw{"answer": "no", "explanation": "In Bootstrap 5, dark mode is enabled by adding the data-bs-theme=\"dark\" attribute to the <body> element, not by adding a .dark class to the root (<html>) element."} | верно | Наоборот: тема включается атрибутом data-bs-theme="dark" (Color modes, с 5.3); класса .dark не существует. В проекте 5.3.3. |
T14-L1 1.3 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 database tables; you must manually run schema generation commands (e.g., doctrine:schema:generate or doctrine:mapping:info) to create the corresponding tables.
Raw{"answer": "no", "explanation": "Doctrine ORM does not automatically create database tables; you must manually run schema generation commands (e.g., doctrine:schema:generate or doctrine:mapping:info) to create the corresponding tables."} | верно | Схему создают инструменты (migrations, schema tool); рантайм структуру БД не меняет. |
T14-L2 1.34 c | Doctrine | Which EntityManager method marks a new object as managed without executing SQL until flush()? | «persist» Пояснение: EntityManager::persist() adds a new object to the Unit of Work (marks it managed) without issuing SQL; the INSERT is only executed on flush().
Raw{"answer": "persist", "explanation": "EntityManager::persist() adds a new object to the Unit of Work (marks it managed) without issuing SQL; the INSERT is only executed on flush()."} | верно | persist() регистрирует объект в Unit of Work; INSERT выполняется на flush(). |
T14-L3 1.56 c | Doctrine | In Doctrine ORM 3, the EntityManager::merge() method exists and makes the passed object managed. | «yes» Пояснение: In Doctrine ORM 3, EntityManager::merge() is a persistent method that makes a passed entity managed (either new/transient or detached), placing it under the EntityManager's control.
Raw{"answer": "yes", "explanation": "In Doctrine ORM 3, EntityManager::merge() is a persistent method that makes a passed entity managed (either new/transient or detached), placing it under the EntityManager's control."} | неверно верный: «no» | В ORM 3 merge() удалён (в vendor проекта 3.7.6 метода нет); в Doctrine 2.x merge() возвращал управляемую копию. Версия зафиксирована — ORM 3. |
T14-L4 1.36 c | Doctrine | DQL queries are written in terms of entities and their fields, not tables and columns. | «yes» Пояснение: DQL (Doctrine Query Language) is an object-oriented query language that references entity classes and their mapped properties rather than underlying database tables and columns.
Raw{"answer": "yes", "explanation": "DQL (Doctrine Query Language) is an object-oriented query language that references entity classes and their mapped properties rather than underlying database tables and columns."} | верно | Doctrine транслирует DQL в SQL; docs — DQL (Doctrine Query Language). |
T14-L5 0.89 c | Doctrine | What does $repository->find(999) return when no record with id 999 exists? | «null» Пояснение: In PHP repository patterns, the find() method returns null when no record matching the given id exists.
Raw{"answer": "null", "explanation": "In PHP repository patterns, the find() method returns null when no record matching the given id exists."} | верно | find() возвращает null, если объект не найден (docs Repository methods). |
T14-L6 3.6 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 every request; you must explicitly call $entityManager->flush() (or rely on a custom service/strategy) to persist changes.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "DoctrineBundle does not automatically call flush() at the end of every request; you must explicitly call $entityManager->flush() (or rely on a custom service/strategy) to persist changes." ⏎ } | верно | Авто-flush нет — flush() зовёт разработчик; незакрытая транзакция в конце запроса откатывается. |
T14-L7 2.46 c | Doctrine | For a managed entity, changing a property is enough: flush() commits the change without an explicit persist() — the Unit of Work tracks changes. | «yes» Пояснение: Once an entity is managed, the Unit of Work performs change detection on flush(), so you only need to modify the property and call flush() without calling persist() again.
Raw{"answer": "yes", "explanation": "Once an entity is managed, the Unit of Work performs change detection on flush(), so you only need to modify the property and call flush() without calling persist() again."} | верно | Dirty checking сравнивает снимки свойств; persist нужен только новым/отсоединённым объектам. |
T14-L8 1.45 c | Doctrine | remove() executes the SQL DELETE immediately, without waiting for flush(). | «no» Пояснение: remove() only marks the entity as pending deletion; the SQL DELETE is issued when flush() is called.
Raw{"answer":"no","explanation":"remove() only marks the entity as pending deletion; the SQL DELETE is issued when flush() is called."} | верно | remove() планирует удаление в Unit of Work; DELETE выполняется на flush() (docs — Deleting Objects). |
T15-L1 1.93 c | PostgreSQL | PostgreSQL uses MVCC, therefore readers block writers and writers block readers. | «no» Пояснение: MVCC in PostgreSQL is specifically designed so that readers do NOT block writers and writers do NOT block readers; that is the whole point of multi-version concurrency control.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "MVCC in PostgreSQL is specifically designed so that readers do NOT block writers and writers do NOT block readers; that is the whole point of multi-version concurrency control." ⏎ } | верно | Наоборот: благодаря MVCC читатели не блокируют писателей и наоборот (снимки строк); docs PostgreSQL — Concurrency Control. |
T15-L2 1.37 c | PostgreSQL | Which SQL command shows a query's execution plan without executing the query? | «explain» Пояснение: The EXPLAIN SQL command displays the query execution plan (such as the optimizer's chosen strategy) without actually running the query.
Raw{"answer": "EXPLAIN", "explanation": "The EXPLAIN SQL command displays the query execution plan (such as the optimizer's chosen strategy) without actually running the query."} | верно | EXPLAIN без ANALYZE только строит план; проверено на PostgreSQL 17.7. |
T15-L3 2.21 c | PostgreSQL | SERIAL and GENERATED ... AS IDENTITY are just two names for the same mechanism. | «no» Пояснение: SERIAL is a PostgreSQL-specific convenience type that creates a sequence-backed column with NOT NULL, while GENERATED AS IDENTITY is the standard SQL mechanism with different behavioral semantics (e.g., GENERATED ALWAYS prevents explicit inserts). They are not the same mechanism.
Raw{"answer": "no", "explanation": "SERIAL is a PostgreSQL-specific convenience type that creates a sequence-backed column with NOT NULL, while GENERATED AS IDENTITY is the standard SQL mechanism with different behavioral semantics (e.g., GENERATED ALWAYS prevents explicit inserts). They are not the same mechanism."} | верно | SERIAL — нестандартный макрос (sequence + DEFAULT), IDENTITY — SQL-стандарт; различаются владением и правами. Оба есть в PG 17 (проверено). |
T15-L4 2.11 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 NULL values as distinct from each other, so multiple rows are allowed to have NULL in the constrained column.
Raw{"answer": "no", "explanation": "In PostgreSQL, by default a UNIQUE constraint treats NULL values as distinct from each other, so multiple rows are allowed to have NULL in the constrained column."} | верно | Наоборот: NULLS DISTINCT по умолчанию — несколько NULL допустимы; NULLS NOT DISTINCT — опция с PG 15. Проверено на PG 17.7. |
T15-L5 0.8 c | PostgreSQL | Which PostgreSQL aggregate function concatenates strings with a separator? | «string_agg» Пояснение: string_agg(expression, delimiter) is the PostgreSQL aggregate function that concatenates strings with a specified separator.
Raw{"answer": "string_agg", "explanation": "string_agg(expression, delimiter) is the PostgreSQL aggregate function that concatenates strings with a specified separator."} | верно | string_agg(значение, разделитель); проверено на PostgreSQL 17.7. |
T15-L6 1.93 c | PostgreSQL | Plain VACUUM returns the space occupied by dead tuples to the operating system. | «no» Пояснение: Plain VACUUM reclaims dead-tuple space for reuse within the table but does not return it to the operating system; only VACUUM FULL does that by rewriting the table.
Raw{"answer": "no", "explanation": "Plain VACUUM reclaims dead-tuple space for reuse within the table but does not return it to the operating system; only VACUUM FULL does that by rewriting the table."} | верно | VACUUM помечает место для переиспользования внутри таблицы; ОС его возвращает только VACUUM FULL (с эксклюзивной блокировкой). |
T15-L7 1.12 c | PostgreSQL | Which keyword in a window function definition partitions rows into groups the function is computed over? | «partition by» Пояснение: In SQL window function definitions, the PARTITION BY clause divides the rows into groups (partitions) over which the window function is computed.
Raw{"answer": "PARTITION BY", "explanation": "In SQL window function definitions, the PARTITION BY clause divides the rows into groups (partitions) over which the window function is computed."} | верно | OVER (PARTITION BY ...); проверено на PostgreSQL 17.7. |
T15-L8 2.04 c | PostgreSQL | The READ COMMITTED isolation level protects against non-repeatable reads. | «no» Пояснение: READ COMMITTED only prevents dirty reads; it does not protect against non-repeatable reads, which requires at least the REPEATABLE READ isolation level.
Raw{"answer": "no", "explanation": "READ COMMITTED only prevents dirty reads; it does not protect against non-repeatable reads, which requires at least the REPEATABLE READ isolation level."} | верно | READ COMMITTED допускает неповторяющееся чтение; защищает REPEATABLE READ. Проверено: SHOW transaction_isolation → read committed. |
T17-L1 1.12 c | PostgreSQL: transactions and indexes | By default, PostgreSQL wraps each single SQL statement in its own implicit transaction (autocommit). | «yes» Пояснение: In PostgreSQL, autocommit is enabled by default, so each individual SQL statement is executed within its own implicit transaction that is automatically committed.
Raw{"answer": "yes", "explanation": "In PostgreSQL, autocommit is enabled by default, so each individual SQL statement is executed within its own implicit transaction that is automatically committed."} | верно | Без BEGIN каждый оператор коммитится сам; docs PostgreSQL — Transactions. Проверено на PG 17. |
T17-L2 0.58 c | PostgreSQL: transactions and indexes | Which SQL command ends a transaction, committing all its changes? | «commit» Пояснение: COMMIT is the SQL command that finalizes and persists all changes made within a transaction, ending the transaction block.
Raw{"answer": "COMMIT", "explanation": "COMMIT is the SQL command that finalizes and persists all changes made within a transaction, ending the transaction block."} | верно | COMMIT (END — синоним). Проверено на PG 17. |
T17-L3 1.45 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 statement type that filters on an indexed column, including UPDATE and DELETE, not just SELECT.
Raw{"answer": "yes", "explanation": "Indexes help locate rows quickly for any statement type that filters on an indexed column, including UPDATE and DELETE, not just SELECT."} | верно | Поиск строк для изменения идёт по индексу; docs PostgreSQL — Indexes. |
T17-L4 1.33 c | PostgreSQL: transactions and indexes | To roll back part of the statements inside a transaction, PostgreSQL uses SAVEPOINT. | «yes» Пояснение: PostgreSQL uses SAVEPOINT to create a checkpoint within a transaction, allowing you to roll back only the statements executed after that point using ROLLBACK TO <savepoint_name> while preserving the earlier committed work.
Raw{"answer": "yes", "explanation": "PostgreSQL uses SAVEPOINT to create a checkpoint within a transaction, allowing you to roll back only the statements executed after that point using ROLLBACK TO <savepoint_name> while preserving the earlier committed work."} | верно | SAVEPOINT name; ROLLBACK TO name — частичный откат без отмены всей транзакции. Проверено на PG 17. |
T17-L5 1.46 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 statistics, unlike plain EXPLAIN which only shows the estimated plan without execution.
Raw{"answer": "no", "explanation": "EXPLAIN ANALYZE actually executes the query to collect real timing and statistics, unlike plain EXPLAIN which only shows the estimated plan without execution."} | верно | Наоборот: ANALYZE реально выполняет запрос (с побочными эффектами!) и показывает фактические времена узлов; план без выполнения — plain EXPLAIN. |
T17-L6 0.87 c | PostgreSQL: transactions and indexes | Which PostgreSQL extension adds vector types and indexes for embedding search? | «pgvector» Пояснение: pgvector is a PostgreSQL extension that provides a vector data type and index methods (like GIN and GiST) for performing similarity searches on embeddings.
Raw{"answer": "pgvector", "explanation": "pgvector is a PostgreSQL extension that provides a vector data type and index methods (like GIN and GiST) for performing similarity searches on embeddings."} | верно | CREATE EXTENSION vector (проект pgvector; в проекте образ pgvector/pgvector:pg17). |
T17-L7 1.08 c | PostgreSQL: transactions and indexes | A partial index (CREATE INDEX ... WHERE ...) is built only over rows satisfying the condition. | «yes» Пояснение: A partial index only indexes rows that satisfy the WHERE clause condition, which reduces the index size and can improve query performance.
Raw{"answer":"yes","explanation":"A partial index only indexes rows that satisfy the WHERE clause condition, which reduces the index size and can improve query performance."} | верно | docs PostgreSQL — Partial Indexes; типичный кейс — индекс по «активным» записям. |
T17-L8 3.57 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 predicate locking (locking on the range of rows a query could match) rather than simply locking the specific rows a transaction reads in its snapshot.
Raw{"answer": "no", "explanation": "PostgreSQL's SERIALIZABLE level uses predicate locking (locking on the range of rows a query could match) rather than simply locking the specific rows a transaction reads in its snapshot."} | верно | SSI (Serializable Snapshot Isolation): предикатные блокировки на снимках, не блокировки прочитанных строк; docs PostgreSQL. |
T19-L1 0.91 c | HTTP and REST API | HTTP status 201 means the request resulted in a new resource being created. | «yes» Пояснение: HTTP status 201 'Created' indicates that the request successfully resulted in the creation of a new resource.
Raw{"answer": "yes", "explanation": "HTTP status 201 'Created' indicates that the request successfully resulted in the creation of a new resource."} | верно | 201 Created; обычно на POST, часто с Location; RFC 9110. |
T19-L2 0.96 c | HTTP and REST API | Which HTTP status means a successful request with an empty response body (e.g. after DELETE)? | «204» Пояснение: HTTP status 204 (No Content) indicates a successful response with an empty body, commonly used after a DELETE request.
Raw{"answer": 204, "explanation": "HTTP status 204 (No Content) indicates a successful response with an empty body, commonly used after a DELETE request."} | верно | 204 No Content; RFC 9110. |
T19-L3 2.89 c | HTTP and REST API | The DELETE method is idempotent per the HTTP specification: repeating the request for the same resource does not change the outcome. | «yes» Пояснение: Per the HTTP specification (RFC 7231), DELETE is defined as idempotent: repeating the same DELETE request does not produce a different result from issuing it once (subsequent calls simply find nothing to delete).
Raw{"answer": "yes", "explanation": "Per the HTTP specification (RFC 7231), DELETE is defined as idempotent: repeating the same DELETE request does not produce a different result from issuing it once (subsequent calls simply find nothing to delete)."} | верно | RFC 9110: DELETE идемпотентен (как PUT); идемпотентность ≠ безопасность — ресурс удаляется при первом вызове. |
T19-L4 2.65 c | HTTP and REST API | The Access-Control-Allow-Origin header is sent by the client so that the server agrees to accept requests from another origin. | «no» Пояснение: The Access-Control-Allow-Origin header is sent by the server in the response to inform the browser that the client at a given origin is allowed to read the response, not sent by the client to the server.
Raw{"answer":"no","explanation":"The Access-Control-Allow-Origin header is sent by the server in the response to inform the browser that the client at a given origin is allowed to read the response, not sent by the client to the server."} | верно | Наоборот: заголовок шлёт СЕРВЕР в ответе, разрешая браузеру cross-origin запрос (CORS); в проекте nelmio/cors-bundle. |
T19-L5 1.23 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 is specifically designed to inform a client that it has made too many requests within a specified time frame, indicating a rate limit has been exceeded.
Raw{"answer": "yes", "explanation": "HTTP status 429 Too Many Requests is specifically designed to inform a client that it has made too many requests within a specified time frame, indicating a rate limit has been exceeded."} | верно | 429 (+ Retry-After); RFC 6585. В проекте symfony/rate-limiter. |
T19-L6 1.4 c | HTTP and REST API | 5xx codes mean a client error, while 4xx means a server-side error. | «no» Пояснение: The statement reverses the roles: 4xx codes indicate client errors (e.g., 404 Not Found) and 5xx codes indicate server errors (e.g., 500 Internal Server Error).
Raw{"answer": "no", "explanation": "The statement reverses the roles: 4xx codes indicate client errors (e.g., 404 Not Found) and 5xx codes indicate server errors (e.g., 500 Internal Server Error)."} | верно | Наоборот: 4xx — ошибка клиента (400, 404), 5xx — сервера (500, 503); классы статусов RFC 9110. |
T19-L7 0.55 c | HTTP and REST API | Which HTTP header indicates the MIME type of the request or response body? | «content-type» Пояснение: The Content-Type HTTP header specifies the MIME type of the request or response body.
Raw{"answer": "Content-Type", "explanation": "The Content-Type HTTP header specifies the MIME type of the request or response body."} | верно | Content-Type: application/json и т.п. |
T19-L8 1.83 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 definition, whereas PUT (per RFC 7231) is required to be idempotent.
Raw{"answer":"yes","explanation":"RFC 5789 explicitly states that PATCH is not idempotent by definition, whereas PUT (per RFC 7231) is required to be idempotent."} | верно | RFC 5789 прямо оговаривает: PATCH не гарантированно идемпотентен; PUT идемпотентен. |
T20-L1 3.08 c | Security and OAuth | Checking a password by comparing its hash to the stored hash with a plain == is sufficient. | «no» Пояснение: The == operator is not timing-safe, so it is vulnerable to timing attacks; you should use hash_equals() instead to perform a constant-time comparison.
Raw{"answer": "no", "explanation": "The == operator is not timing-safe, so it is vulnerable to timing attacks; you should use hash_equals() instead to perform a constant-time comparison."} | верно | Нужна постоянновременная проверка (password_verify) — timing-атаки; соль и алгоритм уже внутри хеша. |
T20-L2 1.84 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» Пояснение: This accurately describes the standard CSRF token mechanism: the server generates and binds a token to the session, and then validates it on the server side for state-changing (unsafe) requests such as POST, PUT, and DELETE.
Raw{"answer": "yes", "explanation": "This accurately describes the standard CSRF token mechanism: the server generates and binds a token to the session, and then validates it on the server side for state-changing (unsafe) requests such as POST, PUT, and DELETE."} | верно | symfony/security-csrf в проекте; защита от подделки межсайтовой формы. |
T20-L3 0.7 c | Security and OAuth | Which HTTP header enables the CSP (Content Security Policy) policy? | «content-security-policy» Пояснение: The Content-Security-Policy HTTP header is used to specify allowed sources for the content a browser should load from, thereby enabling CSP.
Raw{"answer":"Content-Security-Policy","explanation":"The Content-Security-Policy HTTP header is used to specify allowed sources for the content a browser should load from, thereby enabling CSP."} | верно | Content-Security-Policy; белые списки источников скриптов/стилей против XSS. |
T20-L4 2.64 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 (not an authentication protocol), and the access token grants access to protected resources rather than identifying the user; identity claims are carried by an ID token in OpenID Connect.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "OAuth 2.0 is an authorization protocol (not an authentication protocol), and the access token grants access to protected resources rather than identifying the user; identity claims are carried by an ID token in OpenID Connect." ⏎ } | верно | OAuth 2.0 — авторизация/делегирование доступа; аутентификацию добавляет OpenID Connect. В проекте knpuniversity/oauth2-client-bundle (yandex/github/google). |
T20-L5 1.9 c | Security and OAuth | XSS is prevented by validating input on the server before writing it to the database. | «no» Пояснение: Validating input before storing it does not prevent XSS; the key defense is encoding/escaping output when it is rendered to the browser.
Raw{"answer": "no", "explanation": "Validating input before storing it does not prevent XSS; the key defense is encoding/escaping output when it is rendered to the browser."} | верно | XSS лечится контекстным экранированием НА ВЫВОДЕ (Twig autoescape, CSP); валидация ввода не покрывает все контексты вывода. |
T20-L6 1.73 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? | «authorization code (code)» Пояснение: In the OAuth 2.0 authorization code flow, the authorization endpoint redirects the user back to the redirect_uri with a query parameter named 'code', which is the authorization code that the client exchanges at the token endpoint for an access token.
Raw{"answer": "authorization code (code)", "explanation": "In the OAuth 2.0 authorization code flow, the authorization endpoint redirects the user back to the redirect_uri with a query parameter named 'code', which is the authorization code that the client exchanges at the token endpoint for an access token."} | верно | Параметр code; обмен на токен POST-ом на /token с client_secret. |
T20-L7 1.44 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 have a longer expiration than access tokens and enable you to request a new access token without requiring the user to log in again.
Raw{"answer":"yes","explanation":"Refresh tokens are designed to have a longer expiration than access tokens and enable you to request a new access token without requiring the user to log in again."} | верно | Стандартная схема OAuth/OIDC: короткий access + длинный refresh. |
T20-L8 1.99 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 so it can be retrieved when verifying a password.
Raw{"answer": "no", "explanation": "A salt does not need to be secret; it is typically stored alongside the hash so it can be retrieved when verifying a password."} | верно | Соль хранится открыто (password_hash включает её в строку хеша); секретность соли не нужна. |
T18-L1 1.33 c | Testing: PHPUnit | PHPUnit runs test methods of any class — extending TestCase is not required. | «no» Пояснение: PHPUnit only discovers and executes test methods in classes that extend PHPUnit\Framework\TestCase (or a subclass thereof).
Raw{"answer": "no", "explanation": "PHPUnit only discovers and executes test methods in classes that extend PHPUnit\\Framework\\TestCase (or a subclass thereof)."} | верно | Тестом считается метод класса, наследующего TestCase (PHPUnit 10). |
T18-L2 2.25 c | Testing: PHPUnit | In PHPUnit, setUp() runs once before all tests of the class. | «no» Пояснение: setUp() runs before each individual test method in the class, not once before all tests; that is the role of setUpBeforeClass().
Raw{"answer": "no", "explanation": "setUp() runs before each individual test method in the class, not once before all tests; that is the role of setUpBeforeClass()."} | верно | setUp() — перед КАЖДЫМ тестом; один раз на класс — setUpBeforeClass(). Проверено живым счётчиком на PHPUnit 10.5. |
T18-L3 2.25 c | Testing: PHPUnit | A data provider lets a test run with exactly one set of arguments. | «no» Пояснение: A data provider is designed to supply multiple sets of arguments so that a test can be run with each set, not just exactly one.
Raw{"answer": "no", "explanation": "A data provider is designed to supply multiple sets of arguments so that a test can be run with each set, not just exactly one."} | верно | Наоборот: наборов может быть сколько угодно — тест выполняется по разу на каждый. Проверено на PHPUnit 10.5 (#[DataProvider]). |
T18-L4 1.19 c | Testing: PHPUnit | Which PHPUnit method declares an expectation that an exception of a given class is thrown? | «expectexception» Пояснение: In PHPUnit, $this->expectException(ClassName::class) declares the expectation that a specific exception class will be thrown during the test.
Raw{"answer": "expectException", "explanation": "In PHPUnit, $this->expectException(ClassName::class) declares the expectation that a specific exception class will be thrown during the test."} | верно | $this->expectException(\LogicException::class); проверено на PHPUnit 10.5. |
T18-L5 1.92 c | Testing: PHPUnit | In PHPUnit, a stub verifies which methods were called on it, while a mock only returns data. | «no» Пояснение: The statement has it backwards: a stub returns predetermined data, while a mock verifies which methods were called with what arguments.
Raw{"answer": "no", "explanation": "The statement has it backwards: a stub returns predetermined data, while a mock verifies which methods were called with what arguments."} | верно | Наоборот: стаб подставляет данные, мок проверяет взаимодействия (createStub/createMock); docs PHPUnit — Test Doubles. |
T18-L6 1.35 c | Testing: PHPUnit | In PHPUnit 10+, the recommended way to pass data to a test is the #[DataProvider] attribute (the @dataProvider annotation is deprecated). | «yes» Пояснение: In PHPUnit 10+, the #[DataProvider] attribute is the recommended approach, and the legacy @dataProvider docblock annotation has been deprecated.
Raw{"answer": "yes", "explanation": "In PHPUnit 10+, the #[DataProvider] attribute is the recommended approach, and the legacy @dataProvider docblock annotation has been deprecated."} | верно | Аннотация ещё парсится в PHPUnit 10/11 (AnnotationParser в 10.5.66), удаление — в 12; атрибут — стандарт. |
T18-L7 1.72 c | Testing: PHPUnit | PHPUnit does not allow one test to depend on the result of another. | «no» Пояснение: PHPUnit provides methods like dependsOnTestClass(), dependsOnTestMethod(), and the @depends annotation to make one test depend on another, so it does allow test dependencies.
Raw{"answer": "no", "explanation": "PHPUnit provides methods like dependsOnTestClass(), dependsOnTestMethod(), and the @depends annotation to make one test depend on another, so it does allow test dependencies."} | верно | Зависимости есть: #[Depends] — зависимый тест не запустится, еслиProducer упал. |
T18-L8 0.96 c | Testing: PHPUnit | Which PHPUnit command-line option makes tests run in random order? | «--shuffle» Пояснение: The --shuffle PHPUnit CLI option randomizes the order in which tests are executed.
Raw{"answer": "--shuffle", "explanation": "The --shuffle PHPUnit CLI option randomizes the order in which tests are executed."} | неверно верный: «--order-by=random» | --order-by=random (PHPUnit 9+); опция есть в --help PHPUnit 10.5 (проектная). |
T01-L9 3.62 c | Syntax and operators | What does this code output?
```php
echo intdiv(7, 2) . intdiv(-7, 2);
``` | «3-3» Пояснение: intdiv truncates toward zero, so intdiv(7,2)=3 and intdiv(-7,2)=-3, concatenated as the string "3-3".
Raw{"answer": "3-3", "explanation": "intdiv truncates toward zero, so intdiv(7,2)=3 and intdiv(-7,2)=-3, concatenated as the string \"3-3\"."} | верно | intdiv truncates toward zero: intdiv(-7, 2) = -3, not -4. |
T01-L10 1.73 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 the expression is parsed as -(3 ** 2) which equals -9, not (-3) ** 2.
Raw{"answer": -9, "explanation": "In PHP, the exponentiation operator ** has higher precedence than the unary minus, so the expression is parsed as -(3 ** 2) which equals -9, not (-3) ** 2."} | верно | ** is right-associative and binds tighter than unary minus: -(3²). |
T02-L9 4.2 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 casts them to numbers (10 == 10) and the comparison is true, making the ternary output 'true'.
Raw{"answer": "true", "explanation": "Both '1e1' and '10' are numeric strings, so PHP casts them to numbers (10 == 10) and the comparison is true, making the ternary output 'true'."} | верно | Both strings are numeric — compared as numbers: 10 == 10. |
T02-L10 6.05 c | Types and comparisons | What does this code output?
```php
switch ('a') {
case 0: echo 'zero'; break;
default: echo 'other';
}
``` | «zero» Пояснение: In PHP's loose comparison, the non-numeric string 'a' is cast to the integer 0, so it matches case 0.
Raw{"answer": "zero", "explanation": "In PHP's loose comparison, the non-numeric string 'a' is cast to the integer 0, so it matches case 0."} | неверно верный: «other» | PHP 8: 'a' == 0 → false (used to be true) — default fires. |
T03-L9 3.65 c | Strings | What does this code output?
```php
echo strtr('abc', ['a' => '1', 'ab' => '2']);
``` | «2c» Пояснение: strtr uses the longest matching array key first, so "ab" is replaced by "2".
Raw{"answer": "2c", "explanation": "strtr uses the longest matching array key first, so \"ab\" is replaced by \"2\"."} | верно | strtr with an array prefers the longest matching key. |
T03-L10 6.13 c | Strings | What does this code output?
```php
echo '[' . substr('hello', -10) . ']';
``` | «[hello]» Пояснение: When the negative offset -10 exceeds the length of the string 'hello' (5 chars), PHP clamps the start position to 0, so substr returns the entire string 'hello'.
Raw{"answer": "[hello]", "explanation": "When the negative offset -10 exceeds the length of the string 'hello' (5 chars), PHP clamps the start position to 0, so substr returns the entire string 'hello'."} | верно | A negative start beyond the string is clamped to the beginning. |
T04-L9 1.85 c | Arrays | What does this code output?
```php
$a = ['k' => 1, 'n' => 2];
$b = ['k' => 9, 'm' => 3];
echo implode(',', array_keys($a + $b));
``` | «k,n,m» Пояснение: The + operator merges arrays, keeping $a's value for duplicate key 'k', so array_keys returns [k, n, m].
Raw```json ⏎ {"answer": "k,n,m", "explanation": "The + operator merges arrays, keeping $a's value for duplicate key 'k', so array_keys returns [k, n, m]."} ⏎ ``` | верно | The + operator: on duplicate string keys the left array wins. |
T04-L10 4.08 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» Пояснение: After sorting by the third element (index 2) ascending, the array becomes [[2,'y',1],[1,'x',2],[3,'z',2]], and array_column with key 1 extracts ['y','x','z'], which implode with '' produces 'yxz'.
Raw{"answer": "yxz", "explanation": "After sorting by the third element (index 2) ascending, the array becomes [[2,'y',1],[1,'x',2],[3,'z',2]], and array_column with key 1 extracts ['y','x','z'], which implode with '' produces 'yxz'."} | верно | Sorts are stable since 8.0: x and z keep their order on a tie. |
T05-L10 2.19 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» Пояснение: Named arguments via the spread operator match by parameter name, so $a=5 and $b=1, giving 5-1=4.
Raw```json ⏎ {"answer": 4, "explanation": "Named arguments via the spread operator match by parameter name, so $a=5 and $b=1, giving 5-1=4."} ⏎ ``` | верно | String keys of a spread array become named arguments. |
T05-L9 17.14 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 callable captures the P object reference, so reassigning $p to null does not affect it; calling $f() still returns $this->v which is 3.
Raw{ ⏎ "answer": "3", ⏎ "explanation": "The callable captures the P object reference, so reassigning $p to null does not affect it; calling $f() still returns $this->v which is 3." ⏎ } | верно | First-class callable syntax binds $this at creation time. |
T06-L9 0.98 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 resolves to the late static bound class, which is B, the actual class of the instance.
Raw{"answer": "B", "explanation": "static::class resolves to the late static bound class, which is B, the actual class of the instance."} | верно | Late static binding: static::class is the receiver's class. |
T06-L10 14.67 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 property setter multiplies the assigned value by 2, so setting $c->x = 5 stores 10, which is then echoed.
Raw{"answer": 10, "explanation": "The property setter multiplies the assigned value by 2, so setting $c->x = 5 stores 10, which is then echoed."} | верно | Inside the set hook, $this->x writes the backing store (no recursion): 5*2. |
T07-L9 2.25 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 resolves f() to TB's version (returns 'B'), and TA::f as g aliases TA's f to g (returns 'A').
Raw{"answer": "BA", "explanation": "TB::f insteadof TA resolves f() to TB's version (returns 'B'), and TA::f as g aliases TA's f to g (returns 'A')."} | верно | insteadof picks the implementation; as keeps the other under an alias. |
T07-L10 1.79 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» Пояснение: In PHP, each class that uses a trait gets its own separate copy of the trait's static properties, so setting CX::$n does not affect CY::$n which remains 0.
Raw{"answer": "0", "explanation": "In PHP, each class that uses a trait gets its own separate copy of the trait's static properties, so setting CX::$n does not affect CY::$n which remains 0."} | верно | A trait's static property is copied into each consuming class. |
T08-L10 2.44 c | Exceptions and errors | What does this code output?
```php
function f(): int
{
try { return 1; } finally { return 2; }
}
echo f();
``` | «1» Пояснение: In PHP, a return statement inside a finally block does not override the return value from the try block; the function returns 1.
Raw```json ⏎ {"answer": 1, "explanation": "In PHP, a return statement inside a finally block does not override the return value from the try block; the function returns 1."} ⏎ ``` | неверно верный: «2» | A return in finally overrides the return from try. |
T08-L9 2.48 c | Exceptions and errors | What does this code output?
```php
try {
try {
throw new RuntimeException('first');
} finally {
throw new LogicException('second');
}
} catch (LogicException $e) {
echo $e->getMessage();
}
``` | «second» Пояснение: The LogicException('second') thrown in the finally block replaces the RuntimeException('first') and is caught by the outer catch(LogicException) block.
Raw```json ⏎ {"answer": "second", "explanation": "The LogicException('second') thrown in the finally block replaces the RuntimeException('first') and is caught by the outer catch(LogicException) block."} ⏎ ``` | верно | An exception from finally replaces the in-flight one — the last thrown is caught. |
T09-L9 5.62 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» Пояснение: Within namespace N, the use statement aliases App\Foo as Baz, so Baz::class resolves to 'App\Foo', while \Baz::class (global namespace) resolves to 'Baz'.
Raw{"answer":"App\\Foo|Baz","explanation":"Within namespace N, the use statement aliases App\\Foo as Baz, so Baz::class resolves to 'App\\Foo', while \\Baz::class (global namespace) resolves to 'Baz'."} | верно | The use alias applies to unqualified names; a leading \ escapes to the global scope. |
T09-L10 19.01 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') searches only the global namespace for a class literally named 'Foo' (it is not prefixed with the current namespace), so it returns false; class_exists('Ns\Foo') finds the class, returning true, producing the concatenation 'no' . 'yes'.
Raw```json ⏎ {"answer": "noyes", "explanation": "class_exists('Foo') searches only the global namespace for a class literally named 'Foo' (it is not prefixed with the current namespace), so it returns false; class_exists('Ns\\Foo') finds the class, returning true, producing the concatenation 'no' . 'yes'."} ⏎ ``` | верно | Dynamic names are not resolved against the namespace — 'Foo' is the global class. |
T10-L9 1.8 c | References and scope | What does this code output?
```php
$a = [1, 2, 3];
foreach ($a as &$v) {}
$v = 99;
echo implode(',', $a);
``` | «1,2,99» Пояснение: The foreach loop creates $v as a reference to the last element of $a, so assigning $v = 99 changes the last element to 99.
Raw{"answer":"1,2,99","explanation":"The foreach loop creates $v as a reference to the last element of $a, so assigning $v = 99 changes the last element to 99."} | верно | After a by-ref foreach, $v remains a reference to the last element. |
T10-L10 3.18 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 are shared across all instances of the class where they are declared; since B extends A and does not redeclare $n, both $a and $b share the same static counter, so three calls to inc() (two calls before echo, one in echo) produce 3.
Raw{"answer": 3, "explanation": "Static variables are shared across all instances of the class where they are declared; since B extends A and does not redeclare $n, both $a and $b share the same static counter, so three calls to inc() (two calls before echo, one in echo) produce 3."} | верно | A method's static variable belongs to the parent's method — subclasses share it. |
T11-L9 16.58 c | Generators, iterators, SPL | What does this code output?
```php
function g(): Generator
{
$x = yield 1;
return $x + 1;
}
$g = g();
$g->send(10);
echo $g->getReturn();
``` | «—» Пояснение: The single send(10) call only resumes the generator to the yield point (assigning $x=10), but the generator is still paused and has not executed the return statement, so getReturn() returns null, which echoes as an empty string.
Raw```json ⏎ {"answer": "", "explanation": "The single send(10) call only resumes the generator to the yield point (assigning $x=10), but the generator is still paused and has not executed the return statement, so getReturn() returns null, which echoes as an empty string."} ⏎ ``` | неверно верный: «11» | send() resumes the generator: $x = 10, return 10+1. |
T11-L10 2.84 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 inner() delegates and yields 1 and 2, then captures inner's return value 'ok' into $r, which is yielded last, producing [1, 2, 'ok'] that implode joins into '1,2,ok'.
Raw{"answer": "1,2,ok", "explanation": "yield from inner() delegates and yields 1 and 2, then captures inner's return value 'ok' into $r, which is yielded last, producing [1, 2, 'ok'] that implode joins into '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 2.16 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 when the hash cost (4) matches the requested cost (4), and true when the requested cost (5) is higher than the hash cost (4).
Raw{"answer": "noyes", "explanation": "password_needs_rehash returns false when the hash cost (4) matches the requested cost (4), and true when the requested cost (5) is higher than the hash cost (4)."} | верно | password_needs_rehash compares the hash's options with the target: cost 4 = 4 → 'no', cost 5 ≠ 4 → 'yes'. |
T12-L10 12.58 c | Configuration and security | What does this code output on PHP 8.5?
```php
echo (E_ALL & 2048) === 0 ? 'strict-out' : 'strict-in';
``` | «strict-in» Пояснение: E_PARSE equals 2048 and is always part of E_ALL, so (E_ALL & 2048) === 0 is false, meaning 'strict-in' is echoed.
Raw{ ⏎ "answer": "strict-in", ⏎ "explanation": "E_PARSE equals 2048 and is always part of E_ALL, so (E_ALL & 2048) === 0 is false, meaning 'strict-in' is echoed." ⏎ } | неверно верный: «strict-out» | Since PHP 8.4, E_STRICT is out of E_ALL: the 2048 bit is unset → 'strict-out' (2048 is the historical E_STRICT bit). |
T13-L9 1.82 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::create() normalizes the HTTP_X_TOKEN header to x-token, and headers->get() performs a case-insensitive lookup, so X-Token successfully retrieves 'abc'.
Raw{"answer": "mapped", "explanation": "Symfony's Request::create() normalizes the HTTP_X_TOKEN header to x-token, and headers->get() performs a case-insensitive lookup, so X-Token successfully retrieves '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.65 c | Symfony | What does this code output?
```php
use Symfony\Component\EventDispatcher\EventDispatcher;
use Symfony\Contracts\EventDispatcher\Event;
$d = new EventDispatcher();
$out = '';
$d->addListener('e', function () use (&$out) { $out .= 'B'; }, 10);
$d->addListener('e', function () use (&$out) { $out .= 'A'; });
$d->addListener('e', function () use (&$out) { $out .= 'C'; }, 5);
$d->dispatch(new Event(), 'e');
echo $out;
``` | «bca» Пояснение: Symfony's EventDispatcher calls listeners in descending order of priority (10, 5, 0), so the listeners append B, C, and A in that order.
Raw{"answer": "BCA", "explanation": "Symfony's EventDispatcher calls listeners in descending order of priority (10, 5, 0), so the listeners append B, C, and A in that order."} | верно | Listeners run by descending priority: 10 (B), 5 (C), 0 (A). |
T14-L10 3.58 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» Пояснение: After flush, the entity is cached in the EntityManager's identity map (first-level cache), so both find() calls return the exact same object instance.
Raw{"answer": "same", "explanation": "After flush, the entity is cached in the EntityManager's identity map (first-level cache), so both find() calls return the exact same object instance."} | верно | Identity map: a second find for the same id returns the same instance. |
T14-L9 4.16 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» Пояснение: persist() adds the entity to the Unit of Work's pending inserts without executing SQL; remove() before flush() cancels the pending insert, so flush() issues no INSERT, leaving the users table empty.
Raw{"answer": "0", "explanation": "persist() adds the entity to the Unit of Work's pending inserts without executing SQL; remove() before flush() cancels the pending insert, so flush() issues no INSERT, leaving the users table empty."} | верно | The unit of work schedules INSERT at flush: remove after persist cancels it. |
T15-L10 1.7 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 with values 1 and NULL it returns 1.
Raw{"answer": 1, "explanation": "COUNT(x) counts only non-NULL values in column x, so with values 1 and NULL it returns 1."} | верно | count(column) skips NULLs; count(*) would return 2. |
T15-L9 2.75 c | PostgreSQL | What does this SQL query return (PostgreSQL 17)?
```sql
CREATE TEMP TABLE t (id int, x int);
INSERT INTO t VALUES (1, 10), (2, 20), (3, 30);
SELECT string_agg(s::text, ',' ORDER BY id) FROM (
SELECT id, sum(x) OVER (ORDER BY id) AS s FROM t
) q;
``` | «10,30,60» Пояснение: The window function sum(x) OVER (ORDER BY id) produces running sums 10, 30, 60, which string_agg then joins with commas into the single string '10,30,60'.
Raw{"answer":"10,30,60","explanation":"The window function sum(x) OVER (ORDER BY id) produces running sums 10, 30, 60, which string_agg then joins with commas into the single string '10,30,60'."} | верно | With ORDER BY the default window frame is running (start to current row). |
T16-L9 4.8 c | Symfony: Messenger | What does this code output?
```php
use Symfony\Component\Messenger\MessageBus;
use Symfony\Component\Messenger\Middleware\MiddlewareInterface;
use Symfony\Component\Messenger\Middleware\StackInterface;
use Symfony\Component\Messenger\Envelope;
final class Trace implements MiddlewareInterface
{
public function __construct(private string $tag) {}
public function handle(Envelope $e, StackInterface $stack): Envelope
{
echo $this->tag;
return $stack->next()->handle($e, $stack);
}
}
$bus = new MessageBus([new Trace('M1'), new Trace('M2')]);
$bus->dispatch(new Envelope(new stdClass()));
``` | «m1m2» Пояснение: The middleware stack processes middlewares in order (M1 then M2), each echoing its tag before delegating to the next, so the output is "M1M2".
Raw{"answer":"M1M2","explanation":"The middleware stack processes middlewares in order (M1 then M2), each echoing its tag before delegating to the next, so the output is \"M1M2\"."} | верно | The first-added middleware runs first (outermost). |
T16-L10 3.28 c | Symfony: Messenger | What does this code output?
```php
use Symfony\Component\Messenger\MessageBus;
use Symfony\Component\Messenger\Middleware\HandleMessageMiddleware;
use Symfony\Component\Messenger\Handler\HandlersLocator;
use Symfony\Component\Messenger\Handler\HandlerDescriptor;
use Symfony\Component\Messenger\Envelope;
class Ping {}
$n = 0;
$d1 = new HandlerDescriptor(function (Ping $m) use (&$n) { $n += 1; }, ['alias' => 'h1']);
$d2 = new HandlerDescriptor(function (Ping $m) use (&$n) { $n += 10; }, ['alias' => 'h2']);
$bus = new MessageBus([
new HandleMessageMiddleware(new HandlersLocator([Ping::class => [$d1, $d2]])),
]);
$bus->dispatch(new Envelope(new Ping()));
echo $n;
``` | «11» Пояснение: The HandleMessageMiddleware with a HandlersLocator calling all registered handlers for the message type executes both closures, incrementing $n by 1 and then by 10, resulting in 11.
Raw{"answer": "11", "explanation": "The HandleMessageMiddleware with a HandlersLocator calling all registered handlers for the message type executes both closures, incrementing $n by 1 and then by 10, resulting in 11."} | верно | All registered handlers of the message run: 1 + 10 = 11. |
T17-L9 2.04 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 INSERT is skipped due to the unique index with ON CONFLICT DO NOTHING, leaving only one row, so count(*) returns 1.
Raw{"answer": 1, "explanation": "The first INSERT succeeds, the second INSERT is skipped due to the unique index with ON CONFLICT DO NOTHING, leaving only one row, so count(*) returns 1."} | верно | ON CONFLICT DO NOTHING skips the duplicate: one insert. |
T17-L10 2.42 c | PostgreSQL: transactions and indexes | What does this sequence of psql commands output?
```sql
BEGIN;
CREATE TEMP TABLE t (a int, UNIQUE (a) DEFERRABLE INITIALLY DEFERRED);
INSERT INTO t VALUES (1);
INSERT INTO t VALUES (1);
SELECT count(*) FROM t;
``` | «2» Пояснение: The UNIQUE constraint is DEFERRABLE INITIALLY DEFERRED, so the uniqueness check is delayed until COMMIT; both duplicate inserts succeed within the transaction, so count(*) returns 2.
Raw{"answer": 2, "explanation": "The UNIQUE constraint is DEFERRABLE INITIALLY DEFERRED, so the uniqueness check is delayed until COMMIT; both duplicate inserts succeed within the transaction, so count(*) returns 2."} | верно | DEFERRED postpones the uniqueness check to COMMIT — count sees 2 rows. |
T18-L9 4.33 c | Testing: PHPUnit | How many tests will this command run?
```php
use PHPUnit\Framework\TestCase;
use PHPUnit\Framework\Attributes\DataProvider;
final class CalcTest extends TestCase
{
public static function prov(): array
{
return [[1], [2], [3]];
}
#[DataProvider('prov')]
public function test_sum(int $x): void
{
$this->assertTrue($x > 0);
}
#[DataProvider('prov')]
public function test_sum_abs(int $x): void
{
$this->assertTrue($x > 0);
}
public function test_other(): void
{
$this->assertTrue(true);
}
}
```
Command: `phpunit CalcTest.php --filter test_sum` (PHPUnit 10.5) | «6» Пояснение: The --filter test_sum matches both test_sum and test_sum_abs (substring match), each with 3 data provider datasets, for a total of 6 test cases.
Raw```json ⏎ {"answer": 6, "explanation": "The --filter test_sum matches both test_sum and test_sum_abs (substring match), each with 3 data provider datasets, for a total of 6 test cases."} ⏎ ``` | верно | --filter is a substring match: test_sum also matches test_sum_abs (3+3 datasets). |
T18-L10 1.82 c | Testing: PHPUnit | How many tests will this command run, and how many of them will fail? Answer with two comma-separated numbers (ran, failed).
```php
use PHPUnit\Framework\TestCase;
use PHPUnit\Framework\Attributes\DataProvider;
final class Calc2Test extends TestCase
{
public function prov(): array
{
return [[1], [-1]];
}
#[DataProvider('prov')]
public function test_x(int $x): void
{
$this->assertTrue($x > 0);
}
}
```
Command: `phpunit Calc2Test.php` (PHPUnit 10.5) | «2,1» Пояснение: The DataProvider supplies two datasets ([1] and [-1]), so test_x runs twice; only the run with -1 fails the assertTrue(-1 > 0) assertion.
Raw{"answer":"2,1","explanation":"The DataProvider supplies two datasets ([1] and [-1]), so test_x runs twice; only the run with -1 fails the assertTrue(-1 > 0) assertion."} | верно | 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 1.0 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 tells curl to send data in the request body, which implies a POST HTTP method.
Raw{"answer": "POST", "explanation": "The -d flag tells curl to send data in the request body, which implies a POST HTTP method."} | верно | -d/-F switches curl to POST by default. |
T19-L10 1.55 c | HTTP and REST API | Which HTTP method does this command send?
```bash
curl -s -G -d 'a=1' http://demo.local/api
``` | «get» Пояснение: The -G flag tells curl to use the GET method and append the -d data as a query string, making it a GET request instead of a POST.
Raw{"answer": "GET", "explanation": "The -G flag tells curl to use the GET method and append the -d data as a query string, making it a GET request instead of a POST."} | верно | -G turns -d data into the query string; the method stays GET. |
T20-L9 4.03 c | Security and OAuth | A client hits the token endpoint (RFC 6749) with a non-existent client_id. What value of the error field does the endpoint return? | «invalid_client» Пояснение: Per RFC 6749 Section 5.3, when the client identification fails (i.e., the client_id does not match a registered client), the token endpoint returns the error 'invalid_client' along with HTTP 401.
Raw{"answer": "invalid_client", "explanation": "Per RFC 6749 Section 5.3, when the client identification fails (i.e., the client_id does not match a registered client), the token endpoint returns the error 'invalid_client' along with HTTP 401."} | верно | Unknown client → invalid_client (RFC 6749 §5.2). |
T20-L10 2.75 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? | «query string» Пояснение: In the OAuth 2.0 implicit flow (response_type=token), the authorization server appends the access_token as a query parameter (e.g., ?access_token=...) to the redirect_uri.
Raw{"answer": "query string", "explanation": "In the OAuth 2.0 implicit flow (response_type=token), the authorization server appends the access_token as a query parameter (e.g., ?access_token=...) to the redirect_uri."} | неверно верный: «fragment» | The implicit flow passes the token in the URL fragment (#) — it never reaches the server. |
T21-L9 23.54 c | Twig | What does this Twig template output?
```twig
{{ false|default(2) * 3 }}
``` | «6» Пояснение: In Twig, the default filter treats false as an 'empty' value (per documentation: 'Empty includes: null, false, empty array, empty string'), so false|default(2) evaluates to 2, and 2 * 3 = 6.
Raw{"answer": 6, "explanation": "In Twig, the default filter treats false as an 'empty' value (per documentation: 'Empty includes: null, false, empty array, empty string'), so false|default(2) evaluates to 2, and 2 * 3 = 6."} | верно | default replaces exactly false/null/''/[] — false becomes 2, 2*3 = 6; the naive 'default is for undefined only' yields 0. |
T21-L10 9.21 c | Twig | What exception class does render() of this template throw?
```twig
{{ 'a' ~ 1 + 2 }}
``` | «twig\runtimeexception» Пояснение: The expression parses as ('a' ~ 1) + 2 due to ~ having higher precedence than +, resulting in 'a1' + 2, which attempts numeric addition on a non-numeric string and throws Twig\RuntimeException.
Raw{ ⏎ "answer": "Twig\\RuntimeException", ⏎ "explanation": "The expression parses as ('a' ~ 1) + 2 due to ~ having higher precedence than +, resulting in 'a1' + 2, which attempts numeric addition on a non-numeric string and throws Twig\\RuntimeException." ⏎ } | неверно верный: «runtimeerror» | In Twig ~ binds tighter than +: ('a' ~ 1) + 2 → string + int → a render error (RuntimeError). |
T22-L9 11.18 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 array [''] is not considered blank by Symfony's NotBlank constraint (it is a non-empty array), so no violations are produced.
Raw```json ⏎ {"answer": 0, "explanation": "The array [''] is not considered blank by Symfony's NotBlank constraint (it is a non-empty array), so no violations are produced."} ⏎ ``` | верно | NotBlank treats null, '', [] as blank — the array [''] is not blank. |
T22-L10 9.67 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» Пояснение: The code creates a TextType form via Symfony's form factory; since TextType has no built-in validators, isValid() returns true, so the ternary echoes 'valid'.
Raw{"answer": "valid", "explanation": "The code creates a TextType form via Symfony's form factory; since TextType has no built-in validators, isValid() returns true, so the ternary echoes 'valid'."} | неверно верный: «symfony\component\form\exception\logicexception» | isValid() on a non-submitted form throws LogicException, it does not return false. |
T23-L9 3.48 c | Symfony: configuration and services | What does this code output?
```php
use Symfony\Component\DependencyInjection\ContainerBuilder;
$c = new ContainerBuilder();
$c->register('a', stdClass::class)->setPublic(true);
$c->compile();
echo spl_object_id($c->get('a')) === spl_object_id($c->get('a')) ? 'same' : 'diff';
``` | «same» Пояснение: After compile(), the container caches the resolved service instance, so both calls to get('a') return the same stdClass object.
Raw{"answer":"same","explanation":"After compile(), the container caches the resolved service instance, so both calls to get('a') return the same stdClass object."} | верно | Container services are shared: two get() calls yield one instance. |
T23-L10 3.34 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!» Пояснение: The parameter resolver resolves %name% to 'Bob' and %greeting% to 'hi Bob', then appends the literal '!', resulting in 'hi Bob!'.
Raw{"answer": "hi Bob!", "explanation": "The parameter resolver resolves %name% to 'Bob' and %greeting% to 'hi Bob', then appends the literal '!', resulting in 'hi Bob!'."} | верно | compile() resolves %-references transitively: %greeting% → 'hi %name%' → 'hi Bob!', the answer assembles over two hops. |
T24-L9 3.34 c | Bootstrap | What is the max-width of .container in Bootstrap 5.3 at a 992px viewport? | «960» Пояснение: In Bootstrap 5.3, the .container class applies max-width: 960px at the @media (min-width: 992px) breakpoint, which is active at a 992px viewport.
Raw{"answer": 960, "explanation": "In Bootstrap 5.3, the .container class applies max-width: 960px at the @media (min-width: 992px) breakpoint, which is active at a 992px viewport."} | верно | 5.x container widths: 540/720/960/1140/1320 (sm–xxl); 992 → 960px. |
T24-L10 3.76 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 is defined after .text-primary, so with equal specificity it wins the cascade.
Raw{"answer": "text-danger", "explanation": "In Bootstrap 5.3's generated CSS, .text-danger is defined after .text-primary, so with equal specificity it wins the cascade."} | верно | Specificity ties — the later rule wins: text-danger is declared after text-primary. |
T25-L9 2.25 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. It uses App\Application\PlaceOrder (Domain→Application violation) and App\Infrastructure\Db (Domain→Infrastructure violation), totaling 2 violations.
Raw```json ⏎ {"answer": 2, "explanation": "The class is in the Domain layer, which may only depend on Domain. It uses App\\Application\\PlaceOrder (Domain→Application violation) and App\\Infrastructure\\Db (Domain→Infrastructure violation), totaling 2 violations."} ⏎ ``` | верно | Domain may depend only on Domain: PlaceOrder (Application) + Db (Infrastructure) = 2. |
T25-L10 3.53 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» Пояснение: BillingService is in the Domain layer and depends on Application\PlaceOrder (1 violation) and Infrastructure\Db and Infrastructure\Logger (2 violations), all of which violate the rule that Domain may only depend on Domain.
Raw{"answer": 3, "explanation": "BillingService is in the Domain layer and depends on Application\\PlaceOrder (1 violation) and Infrastructure\\Db and Infrastructure\\Logger (2 violations), all of which violate the rule that Domain may only depend on Domain."} | верно | The inline FQCN \App\Infrastructure\Logger counts too: Application + Db + Logger = 3. |
T26-L10 1.49 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->amount is 10 and $c->amount is 15 (10+5), so the concatenation outputs 10,15.
Raw{"answer": "10,15", "explanation": "$a->amount is 10 and $c->amount is 15 (10+5), so the concatenation outputs 10,15."} | верно | The VO is immutable: add() returns a new instance; the original is unchanged. |
T26-L9 2.25 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» Пояснение: remove('a') throws DomainException when only one item remains, so unset is never reached and the item stays in the array.
Raw{"answer": 1, "explanation": "remove('a') throws DomainException when only one item remains, so unset is never reached and the item stays in the array."} | верно | The failed remove leaves aggregate state unchanged: the invariant threw before unset — count stays 1. |
VC-L9 0.74 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 its hi() method, which returns the string 'hi', then echoes it.
Raw{"answer": "hi", "explanation": "The code instantiates class C and calls its hi() method, which returns the string 'hi', then echoes it."} | верно | Since 8.4, new in a method chain works without wrapping parentheses. |
VC-L10 3.1 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 object is initially uninitialized (prints 'yes'), then accessing $o->v triggers the materialization callback which sets v=21 and initializes the object (prints 'no').
Raw{"answer":"yesno","explanation":"The lazy ghost object is initially uninitialized (prints 'yes'), then accessing $o->v triggers the materialization callback which sets v=21 and initializes 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 3.14 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» Пояснение: AbstractGuardAuthenticator was removed in Symfony 6.0, so it does not exist in Symfony 8.1 and class_exists() returns false.
Raw{"answer": "no", "explanation": "AbstractGuardAuthenticator was removed in Symfony 6.0, so it does not exist in Symfony 8.1 and class_exists() returns false."} | верно | Guard authentication was removed in Symfony 7.0 — the class is gone in 8.1. |
T28-L10 7.73 c | Symfony: versions | The project was upgraded from Symfony 6.4 to 8.1. What does this code output on 8.1?
```php
echo class_exists(\Symfony\Component\Routing\Loader\AnnotationClassLoader::class)
? 'yes' : 'no';
echo class_exists(\Symfony\Component\Routing\Loader\AttributeClassLoader::class)
? 'yes' : 'no';
``` | «no yes» Пояснение: In Symfony 8.1, AnnotationClassLoader was removed (it was deprecated since 4.1 and scheduled for removal), while AttributeClassLoader remains the current routing loader, so the first check is false and the second is true.
Raw{"answer": "no yes", "explanation": "In Symfony 8.1, AnnotationClassLoader was removed (it was deprecated since 4.1 and scheduled for removal), while AttributeClassLoader remains the current routing loader, so the first check is false and the second is true."} | неверно верный: «noyes» | Annotation loaders were removed in 7.0; only attribute loaders remain (Annotation→Attribute). |