Пример запроса (первая клетка). System одинаковый во всех запросах прогона, user — свой вопрос для каждой клетки:
| Клетка | Тема | Утверждение | Ответ |
Результат | Обоснование |
T01-L1 4.0 c | Syntax and operators | Double-quoted and single-quoted strings are processed identically; the difference is only in speed. | «no» Пояснение: Double-quoted strings support variable interpolation and more escape sequences (e.g. \n, \t), while single-quoted strings do not interpolate variables and only recognize \\ and \'. The difference is not just speed.
Raw{"answer": "no", "explanation": "Double-quoted strings support variable interpolation and more escape sequences (e.g. \\n, \\t), while single-quoted strings do not interpolate variables and only recognize \\\\ and \\'. The difference is not just speed."} | верно | В двойных кавычках работают интерполяция переменных и escape-последовательности, в одинарных — нет. |
T01-L2 1.33 c | Syntax and operators | The ?? operator follows isset semantics and raises no warnings for undefined variables. | «yes» Пояснение: The null coalescing operator (??) is syntactic sugar for isset($var) ? $var : default, so it checks with isset() semantics and produces no warnings or notices for undefined variables or array keys.
Raw{"answer": "yes", "explanation": "The null coalescing operator (??) is syntactic sugar for isset($var) ? $var : default, so it checks with isset() semantics and produces no warnings or notices for undefined variables or array keys."} | верно | ?? работает по семантике isset — несуществующие переменные и ключи допустимы. |
T01-L3 0.65 c | Syntax and operators | What will this print: echo 'a', 'b'; | «ab» Пояснение: PHP's echo statement accepts multiple comma-separated arguments and concatenates them in output.
Raw{"answer": "ab", "explanation": "PHP's echo statement accepts multiple comma-separated arguments and concatenates them in output."} | верно | echo принимает список аргументов: ab. |
T01-L4 1.64 c | Syntax and operators | print returns the value 1 and can be used inside an expression. | «no» Пояснение: While print does evaluate to 1, it is a language construct and cannot be used inside an expression (e.g., $x = print 'hello' is a syntax error).
Raw{"answer": "no", "explanation": "While print does evaluate to 1, it is a language construct and cannot be used inside an expression (e.g., $x = print 'hello' is a syntax error)."} | неверно верный: «yes» | print — выражение со значением 1, в отличие от echo, который значения не возвращает. |
T01-L5 1.16 c | Syntax and operators | The ?: (elvis) operator returns its left operand when it is falsy. | «no» Пояснение: The elvis operator ($a ?: $b) returns the left operand when it is truthy, not falsy; when falsy, it returns the right operand.
Raw{"answer": "no", "explanation": "The elvis operator ($a ?: $b) returns the left operand when it is truthy, not falsy; when falsy, it returns the right operand."} | верно | Наоборот: $a ?: $b возвращает $a, если он истинный, иначе $b. |
T01-L6 1.68 c | Syntax and operators | In PHP 8, the concatenation operator (.) has lower precedence than addition and subtraction. | «yes» Пояснение: In PHP, addition and subtraction have higher precedence than concatenation, so in an expression like 5 + 3 . 2, the addition is evaluated first.
Raw{"answer": "yes", "explanation": "In PHP, addition and subtraction have higher precedence than concatenation, so in an expression like 5 + 3 . 2, the addition is evaluated first."} | верно | С PHP 8 (RFC concat precedence) '.' имеет приоритет ниже арифметики: 'сумма: ' . 2 + 3 → 'сумма: 5' (в PHP 7 было иначе). |
T01-L7 0.93 c | Syntax and operators | The expression 2 ** 3 ** 2 in PHP evaluates as (2 ** 3) ** 2, that is, 64. | «no» Пояснение: The ** operator in PHP is right-associative, so 2 ** 3 ** 2 evaluates as 2 ** (3 ** 2) = 2 ** 9 = 512.
Raw{"answer": "no", "explanation": "The ** operator in PHP is right-associative, so 2 ** 3 ** 2 evaluates as 2 ** (3 ** 2) = 2 ** 9 = 512."} | верно | ** право-ассоциативен: 2 ** (3 ** 2) = 2 ** 9 = 512. |
T01-L8 1.64 c | Syntax and operators | What string will this print: echo 'sum: ' . 2 + 3; (PHP 8)? | «3» Пояснение: Concatenation (.) has higher precedence than addition (+), so it's parsed as ('sum: ' . 2) + 3, which becomes 'sum: 2' + 3; the non-numeric string casts to 0, giving 0 + 3 = 3.
Raw{"answer": 3, "explanation": "Concatenation (.) has higher precedence than addition (+), so it's parsed as ('sum: ' . 2) + 3, which becomes 'sum: 2' + 3; the non-numeric string casts to 0, giving 0 + 3 = 3."} | неверно верный: «sum: 5» | Парная к verify-клетке про приоритет: 'сумма: 5'. |
T02-L1 1.54 c | Types and comparisons | With strict comparison (===), arrays are considered equal regardless of element order. | «no» Пояснение: With ===, arrays must have the same key/value pairs in the same order; == is the operator that ignores order.
Raw{"answer": "no", "explanation": "With ===, arrays must have the same key/value pairs in the same order; == is the operator that ignores order."} | верно | === для массивов требует совпадения и значений, и их порядка. |
T02-L2 1.19 c | Types and comparisons | The comparison 0 == false returns false because it is a strict comparison. | «no» Пояснение: 0 == false actually returns true (not false), and == is a loose comparison, not a strict one; strict comparison is ===.
Raw{"answer": "no", "explanation": "0 == false actually returns true (not false), and == is a loose comparison, not a strict one; strict comparison is ===."} | верно | Наоборот: == — нестрогое сравнение и возвращает true; строгое — это === (0 === false → false). |
T02-L3 1.37 c | Types and comparisons | In PHP 8, the expression "abc" == 0 returns true. | «no» Пояснение: In PHP 8, comparing a non-numeric string to an integer with == converts the integer to a string, so 'abc' == 0 becomes 'abc' == '0', which is false.
Raw{"answer":"no","explanation":"In PHP 8, comparing a non-numeric string to an integer with == converts the integer to a string, so 'abc' == 0 becomes 'abc' == '0', which is false."} | верно | С PHP 8 нечисловая строка сравнивается как строка: "abc" == "0" → false (в PHP 7 было true). |
T02-L4 1.11 c | Types and comparisons | Under loose comparison, null equals 0, the empty string, and false at the same time. | «yes» Пояснение: In PHP, null == 0, null == '', and null == false all evaluate to true under loose comparison.
Raw{"answer": "yes", "explanation": "In PHP, null == 0, null == '', and null == false all evaluate to true under loose comparison."} | верно | null == 0, null == "" и null == false — все true. |
T02-L5 0.93 c | Types and comparisons | What does the expression (int) '42abc' return? | «42» Пояснение: PHP casts a string to int by reading from the start until a non-numeric character is encountered, so '42abc' becomes 42.
Raw{"answer": 42, "explanation": "PHP casts a string to int by reading from the start until a non-numeric character is encountered, so '42abc' becomes 42."} | верно | Ведущая числовая часть: 42, без ошибок и warning. |
T02-L6 0.7 c | Types and comparisons | What does the expression '5' + 5 return? | «10» Пояснение: In PHP, the numeric string '5' is cast to an integer when used with the + operator, resulting in 5 + 5 = 10.
Raw{"answer": 10, "explanation": "In PHP, the numeric string '5' is cast to an integer when used with the + operator, resulting in 5 + 5 = 10."} | верно | Числовая строка приводится: int 10. |
T02-L7 0.99 c | Types and comparisons | When cast to string, false becomes "0". | «no» Пояснение: In PHP, casting false to a string produces an empty string "", not "0".
Raw{"answer": "no", "explanation": "In PHP, casting false to a string produces an empty string \"\", not \"0\"."} | верно | false → "", true → "1". |
T02-L8 3.11 c | Types and comparisons | The comparison 0.1 + 0.2 === 0.3 returns false. | «yes» Пояснение: Due to IEEE 754 floating-point precision, 0.1 + 0.2 does not exactly equal 0.3, so strict comparison (===) returns false.
Raw{"answer": "yes", "explanation": "Due to IEEE 754 floating-point precision, 0.1 + 0.2 does not exactly equal 0.3, so strict comparison (===) returns false."} | верно | Двоичная погрешность float: 0.1 + 0.2 = 0.30000000000000004. |
T03-L1 1.15 c | Strings | strrev() correctly reverses a UTF-8 string. | «no» Пояснение: strrev() reverses a string byte by byte, which breaks multi-byte UTF-8 characters (e.g., accented letters, CJK, emoji) into invalid sequences.
Raw{"answer":"no","explanation":"strrev() reverses a string byte by byte, which breaks multi-byte UTF-8 characters (e.g., accented letters, CJK, emoji) into invalid sequences."} | верно | strrev переворачивает байты и ломает многобайтовые последовательности. |
T03-L2 0.68 c | Strings | str_contains('Hello world', 'world') returns true. | «yes» Пояснение: str_contains() checks if the needle 'world' is found within the haystack 'Hello world', which it is, so it returns true.
Raw{"answer": "yes", "explanation": "str_contains() checks if the needle 'world' is found within the haystack 'Hello world', which it is, so it returns true."} | верно | str_contains с PHP 8.0 проверяет вхождение подстроки. |
T03-L3 0.67 c | Strings | str_pad() can pad a string on the right side only. | «no» Пояснение: str_pad() supports STR_PAD_RIGHT, STR_PAD_LEFT, and STR_PAD_BOTH via its $pad_type parameter.
Raw{"answer": "no", "explanation": "str_pad() supports STR_PAD_RIGHT, STR_PAD_LEFT, and STR_PAD_BOTH via its $pad_type parameter."} | верно | STR_PAD_LEFT / STR_PAD_BOTH меняют сторону дополнения. |
T03-L4 1.15 c | Strings | By default trim() strips only spaces, leaving tabs and newlines intact. | «no» Пояснение: By default, trim() removes spaces, tabs, newlines, carriage returns, null bytes, and vertical tabs (" \t\n\r\0\x0B"), not just spaces.
Raw{"answer": "no", "explanation": "By default, trim() removes spaces, tabs, newlines, carriage returns, null bytes, and vertical tabs (\" \\t\\n\\r\\0\\x0B\"), not just spaces."} | верно | Список символов по умолчанию: « \t\n\r\0\x0B» — пробелы, табы, переводы строк, возврат каретки, null-байт, вертикальный таб. Проверено php -r. |
T03-L5 1.09 c | Strings | How many BYTES does strlen('héllo') return for a UTF-8 string? | «6» Пояснение: In UTF-8, 'é' is 2 bytes, while 'h', 'l', 'l', 'o' are each 1 byte, giving a total of 6 bytes.
Raw{"answer": 6, "explanation": "In UTF-8, 'é' is 2 bytes, while 'h', 'l', 'l', 'o' are each 1 byte, giving a total of 6 bytes."} | верно | 6 букв по 2 байта: 12. |
T03-L6 0.87 c | Strings | What does substr('abcdef', -3) return? | «def» Пояснение: substr with start position -3 extracts the last 3 characters of the string.
Raw{"answer": "def", "explanation": "substr with start position -3 extracts the last 3 characters of the string."} | верно | Отрицательное смещение — с конца: def. |
T03-L7 0.77 c | Strings | ucfirst() modifies the string passed to it in place. | «no» Пояснение: ucfirst() returns a new string with the first character uppercased; it does not modify the original string in place.
Raw{"answer": "no", "explanation": "ucfirst() returns a new string with the first character uppercased; it does not modify the original string in place."} | верно | Строки неизменяемы; ucfirst возвращает новую строку. |
T03-L8 0.93 c | Strings | Variable interpolation works in heredoc but not in nowdoc. | «yes» Пояснение: Heredoc supports variable interpolation while nowdoc treats the content as a plain string with no interpolation.
Raw{"answer": "yes", "explanation": "Heredoc supports variable interpolation while nowdoc treats the content as a plain string with no interpolation."} | верно | Nowdoc — «одинарные кавычки» в тройном синтаксисе: текст как есть. |
T04-L1 0.82 c | Arrays | The sort() function preserves the key-to-value association of the array. | «no» Пояснение: sort() reindexes the array with numeric keys starting from 0, discarding original key associations; use asort() to preserve them.
Raw{"answer": "no", "explanation": "sort() reindexes the array with numeric keys starting from 0, discarding original key associations; use asort() to preserve them."} | верно | sort перенумеровывает ключи; связь сохраняет asort. |
T04-L2 0.84 c | Arrays | The string key '5' in an array is stored as the integer 5. | «yes» Пояснение: In PHP, string keys that represent valid integers (like '5') are automatically cast to integer keys.
Raw{"answer": "yes", "explanation": "In PHP, string keys that represent valid integers (like '5') are automatically cast to integer keys."} | верно | Каноничные десятичные строковые ключи приводятся к int. |
T04-L3 0.78 c | Arrays | The in_array() function uses strict comparison (===) by default. | «no» Пояснение: in_array() uses loose comparison (==) by default; you must pass true as the third argument to enable strict comparison (===).
Raw{"answer": "no", "explanation": "in_array() uses loose comparison (==) by default; you must pass true as the third argument to enable strict comparison (===)."} | верно | По умолчанию сравнение нестрогое; строгое — третий аргумент true. |
T04-L4 0.89 c | Arrays | Without a callback, array_filter() removes all "empty" (falsy) elements from the array. | «yes» Пояснение: Without a callback, array_filter() removes elements that are falsy: 0, 0.0, '0', '', null, false, and empty arrays.
Raw{"answer": "yes", "explanation": "Without a callback, array_filter() removes elements that are falsy: 0, 0.0, '0', '', null, false, and empty arrays."} | верно | Убирает 0, "", null, false и пустые массивы. |
T04-L5 0.91 c | Arrays | By default, array_slice() preserves the original numeric keys of the array. | «no» Пояснение: The $preserve_keys parameter defaults to false, so array_slice() reindexes keys by default.
Raw{"answer": "no", "explanation": "The $preserve_keys parameter defaults to false, so array_slice() reindexes keys by default."} | верно | По умолчанию ключи перенумеровываются; сохранение — preserve_keys = true. |
T04-L6 1.02 c | Arrays | What does array_slice([10, 20, 30, 40], 1, 2) return? | «[20, 30]» Пояснение: array_slice starts at index 1 (value 20) and takes 2 elements, returning the subarray [20, 30].
Raw{"answer": "[20, 30]", "explanation": "array_slice starts at index 1 (value 20) and takes 2 elements, returning the subarray [20, 30]."} | верно | [20,30]; ключи перенумеровываются. |
T04-L7 1.3 c | Arrays | How many elements will count(['a' => 1] + ['a' => 9, 'b' => 2]) return? | «2» Пояснение: The + operator keeps the left array's value for duplicate keys ('a' => 1) and adds new keys from the right ('b' => 2), resulting in a 2-element array.
Raw{"answer": 2, "explanation": "The + operator keeps the left array's value for duplicate keys ('a' => 1) and adds new keys from the right ('b' => 2), resulting in a 2-element array."} | верно | Оператор + : по ключу 'a' побеждает левый; итого 2. |
T04-L8 1.52 c | Arrays | Since PHP 8.1, the spread operator [...$a, ...$b] supports arrays with string keys. | «yes» Пояснение: PHP 8.1 introduced the spread operator in array literals, which supports both integer and string keys.
Raw{"answer": "yes", "explanation": "PHP 8.1 introduced the spread operator in array literals, which supports both integer and string keys."} | верно | В 8.0 — только числовые ключи; 8.1 снял ограничение. |
T05-L1 5.41 c | Functions and closures | Named arguments cannot be combined with argument unpacking ...$args in a single call. | «no» Пояснение: In PHP 8.0+, named arguments can be combined with argument unpacking as long as the named arguments appear before the unpacking (e.g., foo(a: 1, ...$args) is valid).
Raw```json ⏎ {"answer": "no", "explanation": "In PHP 8.0+, named arguments can be combined with argument unpacking as long as the named arguments appear before the unpacking (e.g., foo(a: 1, ...$args) is valid)."} ⏎ ``` | верно | Можно: f(...$args, имя: значение). Нельзя только позиционный аргумент после распаковки. |
T05-L2 0.99 c | Functions and closures | An anonymous function without use sees variables from the outer scope. | «no» Пояснение: In PHP, closures do not automatically capture outer scope variables; you must explicitly use the 'use' keyword to import them.
Raw{"answer": "no", "explanation": "In PHP, closures do not automatically capture outer scope variables; you must explicitly use the 'use' keyword to import them."} | верно | Без use внешние переменные недоступны; авто-захват только у fn. |
T05-L3 0.95 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 call, which is 3 (1, 2, 3), regardless of how many parameters are declared.
Raw{"answer": 3, "explanation": "func_num_args() returns the number of arguments actually passed to the function call, which is 3 (1, 2, 3), regardless of how many parameters are declared."} | верно | Считает переданные аргументы: 3. |
T05-L4 1.06 c | Functions and closures | The body of an arrow function fn may consist of several expressions in curly braces. | «no» Пояснение: An arrow function (fn) body consists of a single expression after =>, not multiple expressions in curly braces.
Raw{"answer": "no", "explanation": "An arrow function (fn) body consists of a single expression after =>, not multiple expressions in curly braces."} | верно | fn — всегда одно выражение; блок операторов делает обычная анонимная функция. |
T05-L5 1.58 c | Functions and closures | An arrow function fn captures outer variables by reference (lazily, at use time). | «no» Пояснение: PHP arrow functions (fn) automatically capture outer variables by value, not by reference.
Raw{"answer":"no","explanation":"PHP arrow functions (fn) automatically capture outer variables by value, not by reference."} | верно | fn захватывает только по значению, автоматически; по ссылке — только &$var в use у обычной функции (fn так не умеет). |
T05-L6 0.83 c | Functions and closures | A closure declared as static function () {} does not capture $this. | «yes» Пояснение: A static closure in PHP is not bound to the current object scope, so it has no access to $this.
Raw{"answer": "yes", "explanation": "A static closure in PHP is not bound to the current object scope, so it has no access to $this."} | верно | static-замыкание отвязано от объекта: $this внутри недоступен. |
T05-L7 1.26 c | Functions and closures | What will this print: $x = 5; $f = function () use ($x) { return $x; }; $x = 7; echo $f(); | «5» Пояснение: The closure captures $x by value (5) at creation time; changing the outer $x to 7 afterward does not affect the captured copy.
Raw{"answer": 5, "explanation": "The closure captures $x by value (5) at creation time; changing the outer $x to 7 afterward does not affect the captured copy."} | верно | use захватывает по значению в момент создания: 5. |
T05-L8 1.06 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=1), PHP will coerce the string '5' to the integer 5 when it's passed to an int-typed parameter.
Raw{"answer": "yes", "explanation": "In weak typing mode (without strict_types=1), PHP will coerce the string '5' to the integer 5 when it's passed to an int-typed parameter."} | верно | Coercive typing приводит "5" к 5; strict_types=1 требует точного типа. |
T06-L1 0.79 c | OOP: classes and inheritance | PHP supports constructor property promotion: public function __construct(private int $x) {}. | «yes» Пояснение: Constructor property promotion was introduced in PHP 8.0, allowing properties to be declared directly in constructor parameters.
Raw{"answer": "yes", "explanation": "Constructor property promotion was introduced in PHP 8.0, allowing properties to be declared directly in constructor parameters."} | верно | С PHP 8.0 параметр с модификатором создаёт свойство и присваивание. |
T06-L2 0.64 c | OOP: classes and inheritance | Which keyword prevents a method from being overridden in subclasses? | «final» Пояснение: In PHP, the 'final' keyword before a method declaration prevents that method from being overridden in any subclass.
Raw{"answer": "final", "explanation": "In PHP, the 'final' keyword before a method declaration prevents that method from being overridden in any subclass."} | верно | final. |
T06-L3 0.64 c | OOP: classes and inheritance | A method declared final cannot be overridden in a subclass. | «yes» Пояснение: In PHP, the `final` keyword prevents a method from being overridden in a subclass.
Raw{"answer": "yes", "explanation": "In PHP, the `final` keyword prevents a method from being overridden in a subclass."} | верно | final запрещает переопределение метода и наследование класса. |
T06-L4 0.64 c | OOP: classes and inheritance | Parent properties with private visibility are accessible in a subclass. | «no» Пояснение: Private properties in PHP are only accessible within the class that defines them, not in subclasses; only public and protected properties are accessible in subclasses.
Raw{"answer": "no", "explanation": "Private properties in PHP are only accessible within the class that defines them, not in subclasses; only public and protected properties are accessible in subclasses."} | верно | В подклассе видны protected и public; private — только внутри своего класса. |
T06-L5 2.32 c | OOP: classes and inheritance | What does get_class(new class {}) return? Answer with the part of the name before the NUL byte (without the file path). | «class@anonymous» Пояснение: Anonymous classes in PHP get a generated name in the format class@anonymous/path/to/file.php:line\0suffix, so the part before the NUL byte without the file path is 'class@anonymous'.
Raw{"answer": "class@anonymous", "explanation": "Anonymous classes in PHP get a generated name in the format class@anonymous/path/to/file.php:line\\0suffix, so the part before the NUL byte without the file path is 'class@anonymous'."} | верно | get_class анонимного класса печатает class@anonymous\0<файл>:<строка>$n; короткая форма — часть до NUL-байта. Проверено php -r (hex). |
T06-L6 1.48 c | OOP: classes and inheritance | A private parent method is not part of the inheritance contract: a child may declare a method with the same name and any visibility. | «yes» Пояснение: In PHP, private methods are not inherited and are invisible to child classes, so a child is free to declare a method with the same name and any visibility level without conflict.
Raw{"answer": "yes", "explanation": "In PHP, private methods are not inherited and are invisible to child classes, so a child is free to declare a method with the same name and any visibility level without conflict."} | верно | private-члены не наследуются — правила совместимости подписей не действуют. |
T06-L7 1.17 c | OOP: classes and inheritance | The magic method __get() is called only for non-existent properties. | «no» Пояснение: __get() is called for inaccessible properties, which includes both non-existent properties AND properties declared as private or protected.
Raw{"answer": "no", "explanation": "__get() is called for inaccessible properties, which includes both non-existent properties AND properties declared as private or protected."} | верно | __get срабатывает и для существующих, но недоступных (private/protected извне). |
T06-L8 2.14 c | OOP: classes and inheritance | What does reassigning a readonly property throw — Exception or Error? | «error» Пояснение: Reassigning a readonly property in PHP throws an Error (not an Exception).
Raw{"answer": "Error", "explanation": "Reassigning a readonly property in PHP throws an Error (not an Exception)."} | верно | Error (readonly с 8.1); оговорка: в __clone() переинициализация допустима (8.3+). |
T07-L1 0.56 c | Interfaces, traits, enum | An interface can declare constants. | «yes» Пояснение: PHP interfaces can declare constants, which are always public and immutable.
Raw{"answer": "yes", "explanation": "PHP interfaces can declare constants, which are always public and immutable."} | верно | Константы интерфейса наследуются реализациями. |
T07-L2 0.42 c | Interfaces, traits, enum | Which operator checks whether an object is an instance of a class or interface? | «instanceof» Пояснение: The instanceof operator in PHP checks whether an object is an instance of a specific class or implements a specific interface.
Raw{"answer": "instanceof", "explanation": "The instanceof operator in PHP checks whether an object is an instance of a specific class or implements a specific interface."} | верно | instanceof. |
T07-L3 2.91 c | Interfaces, traits, enum | An interface can declare static methods. | «no» Пояснение: PHP does not allow interfaces to declare static methods; attempting to do so results in a fatal error.
Raw{"answer": "no", "explanation": "PHP does not allow interfaces to declare static methods; attempting to do so results in a fatal error."} | неверно верный: «yes» | Реализация обязана дать статический метод с той же сигнатурой. |
T07-L4 1.09 c | Interfaces, traits, enum | The instanceof operator only checks class inheritance: it ignores interfaces. | «no» Пояснение: The instanceof operator in PHP checks both class inheritance and interface implementation; it returns true if the object is an instance of a class or implements an interface.
Raw{"answer": "no", "explanation": "The instanceof operator in PHP checks both class inheritance and interface implementation; it returns true if the object is an instance of a class or implements an interface."} | верно | instanceof возвращает true и для интерфейсов объекта. |
T07-L5 1.01 c | Interfaces, traits, enum | An interface method may have a default implementation, like a trait method. | «no» Пояснение: In PHP, interface methods are always abstract and cannot have a body/implementation, unlike trait methods which can provide concrete implementations.
Raw{"answer": "no", "explanation": "In PHP, interface methods are always abstract and cannot have a body/implementation, unlike trait methods which can provide concrete implementations."} | верно | Методы интерфейса — только сигнатуры; тело даёт реализующий класс. |
T07-L6 0.77 c | Interfaces, traits, enum | An abstract method in an abstract class may have protected visibility. | «yes» Пояснение: In PHP, abstract methods can be declared as public or protected, but not private.
Raw{"answer": "yes", "explanation": "In PHP, abstract methods can be declared as public or protected, but not private."} | верно | В абстрактном классе — любая видимость; в интерфейсе — только public. |
T07-L7 0.72 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 three enum cases: A, B, and C.
Raw{"answer": 3, "explanation": "Foo::cases() returns an array containing all three enum cases: A, B, and C."} | верно | Статический метод cases(): 3. |
T07-L8 0.76 c | Interfaces, traits, enum | A trait can declare constants. | «yes» Пояснение: PHP traits can declare constants, methods, and properties (with some restrictions).
Raw{"answer": "yes", "explanation": "PHP traits can declare constants, methods, and properties (with some restrictions)."} | верно | С PHP 8.2 трейты могут объявлять константы (RFC constants_in_traits); до 8.2 — нет. |
T08-L1 0.68 c | Exceptions and errors | The Throwable interface is a common ancestor of both Exception and Error. | «yes» Пояснение: In PHP 7+, both Exception and Error implement the Throwable interface, making it their common ancestor.
Raw{"answer": "yes", "explanation": "In PHP 7+, both Exception and Error implement the Throwable interface, making it their common ancestor."} | верно | Иерархия с PHP 7: Throwable → Exception и Throwable → Error. |
T08-L2 1.27 c | Exceptions and errors | A catch (Exception $e) block will also catch TypeError, because TypeError ultimately inherits from Exception. | «no» Пояснение: TypeError extends Error, not Exception; both Exception and Error are siblings under Throwable, so catching Exception will not catch TypeError.
Raw{"answer": "no", "explanation": "TypeError extends Error, not Exception; both Exception and Error are siblings under Throwable, so catching Exception will not catch TypeError."} | верно | TypeError наследуется от Error; catch (Exception) его не ловит. |
T08-L3 1.11 c | Exceptions and errors | The @ operator suppresses exceptions too. | «no» Пояснение: The @ operator only suppresses errors (warnings, notices, etc.) via the error reporting mechanism; it does not catch or suppress exceptions.
Raw{"answer": "no", "explanation": "The @ operator only suppresses errors (warnings, notices, etc.) via the error reporting mechanism; it does not catch or suppress exceptions."} | верно | @ глушит диагностику (warnings/notices), исключения не перехватывает. |
T08-L4 0.87 c | Exceptions and errors | What error class does intdiv(5, 0) throw? | «divisionbyzeroerror» Пояснение: intdiv(5, 0) throws a DivisionByZeroError exception because integer division by zero is undefined.
Raw{"answer": "DivisionByZeroError", "explanation": "intdiv(5, 0) throws a DivisionByZeroError exception because integer division by zero is undefined."} | верно | DivisionByZeroError (иерархия Error, не Exception); php-грейдер объективен. |
T08-L5 0.94 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 or caught; it always runs.
Raw{"answer": "no", "explanation": "The finally block executes regardless of whether an exception was thrown or caught; it always runs."} | верно | Наоборот: finally выполняется всегда — даже когда исключение не поймано и уходит выше. Проверено php -r. |
T08-L6 1.53 c | Exceptions and errors | An exception thrown inside a finally block has no effect on the result of the try block. | «no» Пояснение: An exception thrown in a finally block replaces (overrides) any exception being propagated from the try block.
Raw{"answer": "no", "explanation": "An exception thrown in a finally block replaces (overrides) any exception being propagated from the try block."} | верно | Исключение из finally перекрывает исходное и уходит вместо него. |
T08-L7 0.84 c | Exceptions and errors | What does the expression (bool) new Exception('x') return? | «yes» Пояснение: In PHP, casting any object to bool always returns true, as objects are truthy values.
Raw{"answer": "yes", "explanation": "In PHP, casting any object to bool always returns true, as objects are truthy values."} | верно | Любой объект при приведении к bool — true. Формы ответа: true или да. |
T08-L8 1.01 c | Exceptions and errors | Functions registered via register_shutdown_function() run when exit is called. | «yes» Пояснение: Shutdown functions registered with register_shutdown_function() are executed when the script terminates, including when exit() or die() is called.
Raw{"answer": "yes", "explanation": "Shutdown functions registered with register_shutdown_function() are executed when the script terminates, including when exit() or die() is called."} | верно | exit завершает скрипт, но shutdown-функции отрабатывают. |
T09-L1 1.08 c | Namespaces and autoloading | The use App\Service\Mailer; statement itself loads the class file. | «no» Пояснение: The use statement is a compile-time alias that does not load the class file; the file is loaded by the autoloader only when the class is actually used at runtime.
Raw{"answer": "no", "explanation": "The use statement is a compile-time alias that does not load the class file; the file is loaded by the autoloader only when the class is actually used at runtime."} | верно | use — псевдоним на этапе компиляции; файл грузит автозагрузчик при первом обращении. |
T09-L2 1.08 c | Namespaces and autoloading | What follows use to import a function (not a class): the word function or const? | «function» Пояснение: In PHP, the 'use' statement imports a function using the 'function' keyword (e.g., use ns\function foo); 'const' is used for importing constants.
Raw{"answer": "function", "explanation": "In PHP, the 'use' statement imports a function using the 'function' keyword (e.g., use ns\\function foo); 'const' is used for importing constants."} | верно | use function ...; (и use const для констант). |
T09-L3 1.95 c | Namespaces and autoloading | Into which file (path from src/) does the PSR-4 mapping "App\ → src/" place the class App\Controller\Api\UserController? | «src/controller/api/usercontroller.php» Пояснение: PSR-4 strips the 'App\' prefix, converts remaining namespace separators to directory slashes, and appends .php to the class name under the base path src/.
Raw{"answer": "src/Controller/Api/UserController.php", "explanation": "PSR-4 strips the 'App\\' prefix, converts remaining namespace separators to directory slashes, and appends .php to the class name under the base path src/."} | верно | Остаток имени после префикса, \ → /. |
T09-L4 0.89 c | Namespaces and autoloading | Including vendor/autoload.php registers autoloaders via spl_autoload_register(). | «yes» Пояснение: Composer's vendor/autoload.php instantiates a ClassLoader and calls register(), which internally uses spl_autoload_register() to add the autoloader to the stack.
Raw{"answer": "yes", "explanation": "Composer's vendor/autoload.php instantiates a ClassLoader and calls register(), which internally uses spl_autoload_register() to add the autoloader to the stack."} | верно | Composer ставит автозагрузчик именно на spl_autoload_register. |
T09-L5 0.7 c | Namespaces and autoloading | The magic constant __NAMESPACE__ contains the name of the current namespace. | «yes» Пояснение: __NAMESPACE__ is a PHP magic constant that returns the name of the current namespace (or an empty string if in the global namespace).
Raw{"answer": "yes", "explanation": "__NAMESPACE__ is a PHP magic constant that returns the name of the current namespace (or an empty string if in the global namespace)."} | верно | В корневом пространстве — пустая строка. |
T09-L6 1.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 in a 'new' expression is resolved relative to the current namespace, not from the global root; a leading backslash is needed for global resolution.
Raw{"answer":"no","explanation":"An unqualified class name in a 'new' expression is resolved relative to the current namespace, not from the global root; a leading backslash is needed for global resolution."} | верно | Резолвится относительно текущего namespace (с учётом импортов). |
T09-L7 1.1 c | Namespaces and autoloading | With the PSR-4 mapping "App\ → src/", the class App\Model\User lives in the file src/Model/User.php. | «yes» Пояснение: PSR-4 strips the registered prefix 'App\', converts the remaining 'Model\User' to 'Model/User.php', and prepends the base directory 'src/', yielding 'src/Model/User.php'.
Raw{"answer": "yes", "explanation": "PSR-4 strips the registered prefix 'App\\', converts the remaining 'Model\\User' to 'Model/User.php', and prepends the base directory 'src/', yielding 'src/Model/User.php'."} | верно | Остаток имени после префикса переносится в путь как есть. |
T09-L8 1.66 c | Namespaces and autoloading | A use statement may be written inside a function body — the import then applies to that function only. | «no» Пояснение: In PHP, namespace 'use' import statements are only allowed at the top level of a file (or within a namespace block), not inside a function body.
Raw{"answer": "no", "explanation": "In PHP, namespace 'use' import statements are only allowed at the top level of a file (or within a namespace block), not inside a function body."} | верно | use внутри тела функции — parse error; импорты файловые и компиляционные. |
T10-L1 1.17 c | References and scope | Arrays are copied on assignment rather than passed by reference. | «yes» Пояснение: In PHP, arrays are value types and are copied on assignment by default (using copy-on-write internally), not passed by reference unless explicitly using the & operator.
Raw{"answer": "yes", "explanation": "In PHP, arrays are value types and are copied on assignment by default (using copy-on-write internally), not passed by reference unless explicitly using the & operator."} | верно | Присваивание массива — копия (в движке — copy-on-write). |
T10-L2 1.12 c | References and scope | What will this print: $a = [1, 2]; $b = $a; $b[] = 3; echo count($a); | «2» Пояснение: PHP arrays are copied by value, so modifying $b does not affect $a, which still contains 2 elements.
Raw{"answer": 2, "explanation": "PHP arrays are copied by value, so modifying $b does not affect $a, which still contains 2 elements."} | верно | Присваивание — копия: в $a по-прежнему 2 элемента. |
T10-L3 1.15 c | References and scope | Inside a function, user-defined global variables are inaccessible without global, $GLOBALS, or passing them as parameters. | «yes» Пояснение: In PHP, user-defined global variables are not in scope inside functions; they must be accessed via the global keyword, $GLOBALS, or passed as parameters.
Raw{"answer": "yes", "explanation": "In PHP, user-defined global variables are not in scope inside functions; they must be accessed via the global keyword, $GLOBALS, or passed as parameters."} | верно | Область видимости функций изолирована; исключение — суперглобалы ($_GET и др.). |
T10-L4 1.56 c | References and scope | unset($GLOBALS['x']) inside a function removes the global variable only for that function. | «no» Пояснение: $GLOBALS contains references to global variables, so unset($GLOBALS['x']) removes the global variable entirely, not just within the current function scope.
Raw{"answer": "no", "explanation": "$GLOBALS contains references to global variables, so unset($GLOBALS['x']) removes the global variable entirely, not just within the current function scope."} | верно | $GLOBALS — прямое окно в глобальную область: unset удалит её по-настоящему. |
T10-L5 0.98 c | References and scope | What will this print: function inc(&$x) { $x++; } $n = 5; inc($n); echo $n; | «6» Пояснение: The parameter is passed by reference, so the increment inside the function modifies $n directly, changing it from 5 to 6.
Raw{"answer": 6, "explanation": "The parameter is passed by reference, so the increment inside the function modifies $n directly, changing it from 5 to 6."} | верно | Ссылка меняет оригинал: 6. |
T10-L6 2.01 c | References and scope | A foreach over an array (by value) works with the "live" array: changes to the array inside the loop are visible in the same pass. | «no» Пояснение: A foreach by value iterates over a copy of the array, so modifications to the original array inside the loop are not reflected in the current iteration.
Raw{"answer": "no", "explanation": "A foreach by value iterates over a copy of the array, so modifications to the original array inside the loop are not reflected in the current iteration."} | верно | По значению foreach итерирует копию-снимок. |
T10-L7 0.72 c | References and scope | A static property belongs to each instance separately: changes in one object are not visible in others. | «no» Пояснение: A static property belongs to the class, not to individual instances, so all objects share the same value and changes are visible across all instances.
Raw{"answer": "no", "explanation": "A static property belongs to the class, not to individual instances, so all objects share the same value and changes are visible across all instances."} | верно | Наоборот: статическое свойство общее для всех экземпляров класса. Проверено php -r. |
T10-L8 0.93 c | References and scope | An array can have a boolean key true, and it will be stored as bool. | «no» Пояснение: In PHP, boolean keys in arrays are cast to integers: true becomes 1 and false becomes 0, so they are stored as int, not bool.
Raw{"answer": "no", "explanation": "In PHP, boolean keys in arrays are cast to integers: true becomes 1 and false becomes 0, so they are stored as int, not bool."} | верно | Булев ключ приводится к int: true → 1, false → 0. |
T11-L1 2.34 c | Generators, iterators, SPL | Inside a generator, return with a value can be used, and it becomes available via $gen->getReturn(). | «yes» Пояснение: Since PHP 8.2, a generator's return value can be retrieved via the Generator::getReturn() method.
Raw```json ⏎ {"answer": "yes", "explanation": "Since PHP 8.2, a generator's return value can be retrieved via the Generator::getReturn() method."} ⏎ ``` | верно | return-значение генератора доступно через getReturn() после прохода. |
T11-L2 1.18 c | Generators, iterators, SPL | A fully consumed generator can be rewound with rewind() and traversed again. | «no» Пояснение: PHP generators are one-shot iterators; once fully consumed, calling rewind() on them throws a RuntimeException ('Generator already executed') and they cannot be traversed again.
Raw{"answer": "no", "explanation": "PHP generators are one-shot iterators; once fully consumed, calling rewind() on them throws a RuntimeException ('Generator already executed') and they cannot be traversed again."} | верно | Генератор одноразовый: rewind после начала итерации бросает Exception. |
T11-L3 1.04 c | Generators, iterators, SPL | The yield from construct delegates traversal to another generator or iterable. | «yes» Пояснение: yield from is a Python construct that delegates iteration to another iterable or generator, forwarding all its yielded values.
Raw{"answer": "yes", "explanation": "yield from is a Python construct that delegates iteration to another iterable or generator, forwarding all its yielded values."} | верно | yield from проксирует значения, ключи и return-значение внутреннего генератора. |
T11-L4 0.87 c | Generators, iterators, SPL | What does get_class(g()) return for function g() { yield 1; }? | «generator» Пояснение: Calling a generator function returns a Generator object, so get_class() returns the string 'Generator'.
Raw{"answer": "Generator", "explanation": "Calling a generator function returns a Generator object, so get_class() returns the string 'Generator'."} | верно | Функция с yield возвращает Generator. |
T11-L5 1.17 c | Generators, iterators, SPL | How many elements will count(iterator_to_array((function () { yield from [1, 2, 3]; })())) return? | «3» Пояснение: The generator yields 1, 2, 3 from the array, iterator_to_array converts it to an array with 3 elements, and count returns 3.
Raw{"answer": 3, "explanation": "The generator yields 1, 2, 3 from the array, iterator_to_array converts it to an array with 3 elements, and count returns 3."} | верно | yield from делегирует все 3 элемента. |
T11-L6 0.74 c | Generators, iterators, SPL | The SplStack class implements a FIFO queue. | «no» Пояснение: SplStack implements a LIFO (Last In, First Out) stack, not a FIFO queue.
Raw{"answer": "no", "explanation": "SplStack implements a LIFO (Last In, First Out) stack, not a FIFO queue."} | верно | SplStack — стек LIFO; очередь FIFO — SplQueue. |
T11-L7 0.78 c | Generators, iterators, SPL | ArrayIterator allows wrapping an array and traversing it via the Iterator interface. | «yes» Пояснение: ArrayIterator is a built-in PHP class that wraps an array and implements the Iterator interface, enabling traversal via foreach, current(), next(), key(), valid(), and rewind().
Raw{"answer": "yes", "explanation": "ArrayIterator is a built-in PHP class that wraps an array and implements the Iterator interface, enabling traversal via foreach, current(), next(), key(), valid(), and rewind()."} | верно | Объектная обёртка над массивом. |
T11-L8 0.64 c | Generators, iterators, SPL | An ArrayObject instance cannot be traversed with foreach. | «no» Пояснение: ArrayObject implements Traversable (IteratorAggregate), so it can be traversed with foreach.
Raw{"answer": "no", "explanation": "ArrayObject implements Traversable (IteratorAggregate), so it can be traversed with foreach."} | верно | ArrayObject реализует IteratorAggregate — foreach по нему работает. |
T12-L1 0.75 c | Configuration and security | password_hash() generates a salt automatically — passing one separately is not needed. | «yes» Пояснение: password_hash() automatically generates a random salt and embeds it in the resulting hash string; there is no parameter to supply one manually.
Raw{"answer": "yes", "explanation": "password_hash() automatically generates a random salt and embeds it in the resulting hash string; there is no parameter to supply one manually."} | верно | Соль встраивается в строку результата; параметр salt устарел. |
T12-L2 1.64 c | Configuration and security | In PHP 8, PASSWORD_DEFAULT is md5 with an automatically added salt. | «no» Пояснение: PASSWORD_DEFAULT in PHP 8 is bcrypt (PASSWORD_BCRYPT), not md5.
Raw{"answer": "no", "explanation": "PASSWORD_DEFAULT in PHP 8 is bcrypt (PASSWORD_BCRYPT), not md5."} | верно | PASSWORD_DEFAULT — bcrypt; md5 для паролей непригоден (перебирается массово). |
T12-L3 0.85 c | Configuration and security | What does password_verify('secret', password_hash('secret', PASSWORD_DEFAULT)) return? | «true» Пояснение: password_verify() returns true when the plaintext matches the hash generated by password_hash().
Raw{"answer": true, "explanation": "password_verify() returns true when the plaintext matches the hash generated by password_hash()."} | верно | Соль и хеш в одной строке: true (форма ответа: true или да). |
T12-L4 1.15 c | Configuration and security | strip_tags() protects against SQL injection. | «no» Пояснение: strip_tags() removes HTML/PHP tags and has nothing to do with SQL injection; protecting against SQL injection requires parameterized queries or proper escaping.
Raw{"answer": "no", "explanation": "strip_tags() removes HTML/PHP tags and has nothing to do with SQL injection; protecting against SQL injection requires parameterized queries or proper escaping."} | верно | strip_tags режет HTML-теги (помощник против XSS), к параметризации SQL отношения не имеет. |
T12-L5 1.28 c | Configuration and security | session_regenerate_id() is used to protect against session fixation upon user login. | «yes» Пояснение: session_regenerate_id() generates a new session ID, invalidating any previously known ID, which is the standard defense against session fixation attacks typically called upon user login.
Raw{"answer": "yes", "explanation": "session_regenerate_id() generates a new session ID, invalidating any previously known ID, which is the standard defense against session fixation attacks typically called upon user login."} | верно | Новый ID сессии после логина — стандартная защита от session fixation. |
T12-L6 0.85 c | Configuration and security | Which built-in function returns the SAPI name (e.g., cli)? | «php_sapi_name» Пояснение: php_sapi_name() is the built-in PHP function that returns the current SAPI module name, such as 'cli' or 'fpm-fcgi'.
Raw{"answer": "php_sapi_name", "explanation": "php_sapi_name() is the built-in PHP function that returns the current SAPI module name, such as 'cli' or 'fpm-fcgi'."} | верно | php_sapi_name(). |
T12-L7 1.22 c | Configuration and security | session_destroy() deletes session data on the server but not the cookie in the user's browser. | «yes» Пояснение: session_destroy() only removes the session data on the server; the session cookie in the browser must be manually deleted with setcookie() using a past expiry time.
Raw{"answer": "yes", "explanation": "session_destroy() only removes the session data on the server; the session cookie in the browser must be manually deleted with setcookie() using a past expiry time."} | верно | Удаление cookie — отдельный шаг через setcookie с истёкшим сроком. |
T12-L8 0.95 c | Configuration and security | Without calling session_start(), the $_SESSION array is automatically populated with session data. | «no» Пояснение: The $_SESSION array is only populated with session data after session_start() is explicitly called; without it, $_SESSION is either undefined or empty.
Raw{"answer": "no", "explanation": "The $_SESSION array is only populated with session data after session_start() is explicitly called; without it, $_SESSION is either undefined or empty."} | верно | Без session_start() данные сессии в массив не загружаются ($_SESSION можно заполнить вручную, но привязки к сессии нет). |
VC-L1 1.97 c | PHP 8.4–8.5 | In which PHP version was the array_find() function introduced? | «8.4» Пояснение: The array_find() function was introduced in PHP 8.4 as part of the 'Add array_find and array_find_key' RFC.
Raw{"answer": 8.4, "explanation": "The array_find() function was introduced in PHP 8.4 as part of the 'Add array_find and array_find_key' RFC."} | верно | PHP 8.4 (RFC array_find). |
VC-L2 1.27 c | PHP 8.4–8.5 | Property hooks (get/set right in the property declaration) landed in PHP 8.4. | «yes» Пояснение: PHP 8.4 introduced property hooks, allowing get and set logic to be declared directly in the property definition.
Raw{"answer": "yes", "explanation": "PHP 8.4 introduced property hooks, allowing get and set logic to be declared directly in the property definition."} | верно | Property hooks — PHP 8.4 (ноябрь 2024). |
VC-L3 0.91 c | PHP 8.4–8.5 | Asymmetric visibility (public private(set) string $name) appeared in PHP 8.4. | «yes» Пояснение: Asymmetric visibility (e.g. public private(set) string $name) was introduced in PHP 8.4.
Raw{"answer": "yes", "explanation": "Asymmetric visibility (e.g. public private(set) string $name) was introduced in PHP 8.4."} | верно | Asymmetric visibility v2 — PHP 8.4. |
VC-L4 4.64 c | PHP 8.4–8.5 | In which PHP version was the #[\NoDiscard] attribute introduced? Answer with the version number. | «not introduced» Пояснение: The #[\NoDiscard] attribute does not exist in any released PHP version.
Raw{"answer": "not introduced", "explanation": "The #[\\NoDiscard] attribute does not exist in any released PHP version."} | неверно верный: «8.5» | #[\NoDiscard] — PHP 8.5 (marking return values as important). |
VC-L5 0.78 c | PHP 8.4–8.5 | In which PHP version did the pipe operator |> first appear? Answer with the version number. | «8.4» Пояснение: The pipe operator |> was introduced in PHP 8.4.
Raw{"answer": "8.4", "explanation": "The pipe operator |> was introduced in PHP 8.4."} | неверно верный: «8.5» | Pipe operator — PHP 8.5 (2025). |
VC-L6 1.95 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» Пояснение: No such 'clone-with' syntax exists in any released PHP version.
Raw{"answer": "no", "explanation": "No such 'clone-with' syntax exists in any released PHP version."} | неверно верный: «8.5» | Clone with v2 — PHP 8.5. |
VC-L7 2.88 c | PHP 8.4–8.5 | In which PHP version were the array_first() and array_last() functions introduced? | «not introduced» Пояснение: array_first() and array_last() are not built-in PHP functions in any released version.
Raw{"answer": "not introduced", "explanation": "array_first() and array_last() are not built-in PHP functions in any released version."} | неверно верный: «8.5» | PHP 8.5. |
VC-L8 4.05 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. | «i don't know» Пояснение: I am not aware of an RFC called 'Partial Function Application v2' being adopted into any PHP version as of my knowledge cutoff.
Raw{"answer": "I don't know", "explanation": "I am not aware of an RFC called 'Partial Function Application v2' being adopted into any PHP version as of my knowledge cutoff."} | неверно верный: «8.6» | PFA v2 принят 05.12.2025 (33-0-0), реализован в PHP 8.6. |
VF-L1 1.21 c | PHP: 8.6+ and the future | For which PHP version was the RFC clamp_v2 (the clamp() function) implemented, as of 2026-11-07? Answer with the version number. | «8.4» Пояснение: The clamp_v2 RFC was accepted and implemented in PHP 8.4.
Raw{"answer": "8.4", "explanation": "The clamp_v2 RFC was accepted and implemented in PHP 8.4."} | неверно верный: «8.6» | По данным владельца (wiki.php.net/rfc): clamp_v2 — 8.6; clamp() в 8.5.11 отсутствует (косвенное подтверждение). Дата-якорь делает клетку монотонной. |
VF-L2 1.93 c | PHP: 8.6+ and the future | RFC Context Managers v2 has already been adopted in PHP (as of 2026-11-07). | «no» Пояснение: There is no known 'Context Managers v2' RFC that has been adopted in PHP.
Raw{"answer": "no", "explanation": "There is no known 'Context Managers v2' RFC that has been adopted in PHP."} | верно | На 06.11.2026 — в обсуждении (создан 2026-10-23); не принят. |
VF-L3 2.7 c | PHP: 8.6+ and the future | RFC Bound-Erased Generic Types (generics) was declined in 2026. | «yes» Пояснение: The Bound-Erased Generic Types (generics) RFC was voted on by the PHP internals group and was declined.
Raw```json ⏎ {"answer": "yes", "explanation": "The Bound-Erased Generic Types (generics) RFC was voted on by the PHP internals group and was declined."} ⏎ ``` | верно | Голосование завершилось 2026-06-28: отклонён (wiki.php.net/rfc). |
VF-L4 1.82 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 RFC making ZTS (Zend Thread Safety) the default build has been accepted in PHP; the default remains NTS.
Raw{"answer": "no", "explanation": "No RFC making ZTS (Zend Thread Safety) the default build has been accepted in PHP; the default remains NTS."} | верно | Такого принятого RFC нет на дату якоря; якорь делает клетку монотонной — при принятии RFC позже клетка не перевернётся. |
VF-L5 1.28 c | PHP: 8.6+ and the future | As of PHP 8.5, generics (parameterized types) are still absent. | «yes» Пояснение: PHP has never included built-in generics (parameterized types), and none are planned for PHP 8.5.
Raw{"answer": "yes", "explanation": "PHP has never included built-in generics (parameterized types), and none are planned for PHP 8.5."} | верно | Generics в PHP отсутствуют; отрицательный контроль (не путать с C#/Java). |
VF-L6 2.43 c | PHP: 8.6+ and the future | As of 2026-11-07, the latest stable PHP version is 8.5, and PHP 8.6 has not been released yet (GA — 2026-11-19). | «yes» Пояснение: PHP releases a new minor version each November; PHP 8.5 was released in November 2025, so as of November 7, 2026, it is the latest stable, with PHP 8.6 scheduled for November 19, 2026.
Raw{"answer": "yes", "explanation": "PHP releases a new minor version each November; PHP 8.5 was released in November 2025, so as of November 7, 2026, it is the latest stable, with PHP 8.6 scheduled for November 19, 2026."} | верно | 8.5 — релиз осени 2025; 8.6 GA 19.11.2026 (wiki.php.net/todo/php86). Дата снимка — 06.11.2026. |
VF-L7 1.11 c | PHP: 8.6+ and the future | The PHP 6 branch never shipped: after PHP 5.6 came PHP 7.0 directly. | «yes» Пояснение: PHP 6 was a planned major version that was abandoned; its work was folded into PHP 7.0, which released directly after PHP 5.6.
Raw{"answer": "yes", "explanation": "PHP 6 was a planned major version that was abandoned; its work was folded into PHP 7.0, which released directly after PHP 5.6."} | верно | Исторический факт: ветка 6 не была релизнута. |
VF-L8 1.74 c | PHP: 8.6+ and the future | The RFC adding the #[\Deprecated] attribute to the core was adopted. | «no» Пояснение: The RFC to add a built-in #[\Deprecated] attribute to PHP core was rejected and not adopted.
Raw{"answer": "no", "explanation": "The RFC to add a built-in #[\\Deprecated] attribute to PHP core was rejected and not adopted."} | неверно верный: «yes» | #[\Deprecated] — принят, реализован в PHP 8.4. |
T25-L1 1.28 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 must point inward toward the center; inner layers are unaware of and do not depend on outer layers.
Raw{"answer": "yes", "explanation": "In both Clean and Onion architecture, dependencies must point inward toward the center; inner layers are unaware of and do not depend on outer layers."} | верно | Чистая (Robert C. Martin), луковичная (Jeffrey Palermo) и гексагональная (ports & adapters) — варианты одной идеи: зависимости направлены внутрь, к домену. Слоями в проекте следит deptrac. |
T25-L2 0.97 c | Clean architecture | Domain entities import neither Doctrine nor Symfony — only the language and, possibly, the standard library. | «yes» Пояснение: Domain entities should be pure PHP classes free of framework and ORM dependencies, relying only on the language and possibly the standard library (SPL).
Raw{"answer": "yes", "explanation": "Domain entities should be pure PHP classes free of framework and ORM dependencies, relying only on the language and possibly the standard library (SPL)."} | верно | Изоляция домена от инфраструктуры; deptrac в проекте как раз следит за слоями. |
T25-L3 1.29 c | Clean architecture | Controllers and Twig templates belong to the business-logic layer because they are the ones calling use cases. | «no» Пояснение: Controllers and Twig templates belong to the presentation (interface) layer; the business-logic layer contains the use cases and domain entities themselves.
Raw{"answer": "no", "explanation": "Controllers and Twig templates belong to the presentation (interface) layer; the business-logic layer contains the use cases and domain entities themselves."} | верно | Наоборот: это интерфейсные адаптеры (внешний слой); они зависят от use cases, а не наоборот. |
T25-L4 1.35 c | Clean architecture | What sits at the very center of the onion architecture? | «entity» Пояснение: In the onion architecture, the Entity (core domain business logic) sits at the very center, with layers of application services, adapters, and infrastructure wrapping around it.
Raw{"answer": "Entity", "explanation": "In the onion architecture, the Entity (core domain business logic) sits at the very center, with layers of application services, adapters, and infrastructure wrapping around it."} | неверно верный: «domain model» | Центральное кольцо — Domain Model: сущности и бизнес-правила без зависимостей; далее Domain Services → Application Services → Infrastructure/UI/Tests (Palermo). |
T25-L5 1.03 c | Clean architecture | Layer boundary violations can be caught automatically: a layer-dependency analyzer (e.g. deptrac) fails on a forbidden call. | «yes» Пояснение: Deptrac and similar tools define layer rules and will fail the build when a forbidden cross-layer dependency is detected.
Raw{"answer": "yes", "explanation": "Deptrac and similar tools define layer rules and will fail the build when a forbidden cross-layer dependency is detected."} | верно | depfile.yaml в проекте TasK: CI проверяет правила слоёв на каждом пайплайне. |
T25-L6 1.86 c | Clean architecture | A use case (interactor) may accept an HTTP request or an EntityManager as arguments — it is simpler that way. | «no» Пояснение: A use case (interactor) should depend on abstractions (e.g., repository interfaces), not on concrete framework/infrastructure objects like an HTTP request or an EntityManager, to remain decoupled and testable.
Raw{"answer": "no", "explanation": "A use case (interactor) should depend on abstractions (e.g., repository interfaces), not on concrete framework/infrastructure objects like an HTTP request or an EntityManager, to remain decoupled and testable."} | верно | Use case принимает DTO и порты; привязка к HTTP/ORM протекает инфраструктуру во внутренние слои. |
T25-L7 0.91 c | Clean architecture | What is the component called that provides a collection of aggregates/entities while hiding the storage mechanism behind an interface? | «repository» Пояснение: The Repository pattern provides a collection of aggregates/entities and abstracts the storage mechanism behind an interface.
Raw{"answer": "Repository", "explanation": "The Repository pattern provides a collection of aggregates/entities and abstracts the storage mechanism behind an interface."} | верно | Repository pattern (DDD/Evans); в проекте — Doctrine-репозитории за портами. |
T25-L8 2.14 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 domain and use cases depend only on abstractions (e.g., repository interfaces), so changing the database driver affects only the outermost infrastructure layer.
Raw{"answer": "yes", "explanation": "In clean architecture, the domain and use cases depend only on abstractions (e.g., repository interfaces), so changing the database driver affects only the outermost infrastructure layer."} | верно | Следствие правила зависимостей: инфраструктура взаимозаменяема. |
T26-L1 1.16 c | DDD | In DDD, an aggregate is just another name for a database table. | «no» Пояснение: An aggregate is a domain-level cluster of entities and value objects treated as a unit of consistency, not a database table — it can span multiple tables or share tables with other aggregates.
Raw{"answer": "no", "explanation": "An aggregate is a domain-level cluster of entities and value objects treated as a unit of consistency, not a database table — it can span multiple tables or share tables with other aggregates."} | верно | Агрегат — кластер объектов с границей согласованности (транзакционной вокруг корня); таблица — деталь хранения. |
T26-L2 1.11 c | DDD | A Value Object is immutable and compared by the values of its fields, not by identity. | «yes» Пояснение: Value Objects are defined by their attributes, are immutable, and equality is determined by comparing field values rather than object identity.
Raw{"answer": "yes", "explanation": "Value Objects are defined by their attributes, are immutable, and equality is determined by comparing field values rather than object identity."} | верно | Классика Evans: Money, Email; равенство структурное. |
T26-L3 0.86 c | DDD | What is the single external entry point of an aggregate, through which all changes must go, called? | «aggregate root» Пояснение: In Domain-Driven Design, the Aggregate Root is the single entry point of an aggregate, and all external changes must go through it to maintain invariants.
Raw{"answer": "Aggregate Root", "explanation": "In Domain-Driven Design, the Aggregate Root is the single entry point of an aggregate, and all external changes must go through it to maintain invariants."} | верно | Aggregate Root: внешние объекты ссылаются только на корень; он защищает инварианты агрегата. |
T26-L4 0.99 c | DDD | In DDD, a repository is declared for an aggregate (its root), not for every entity. | «yes» Пояснение: In DDD, a Repository is defined per Aggregate (root), ensuring encapsulation and invariant enforcement within the aggregate boundary.
Raw{"answer": "yes", "explanation": "In DDD, a Repository is defined per Aggregate (root), ensuring encapsulation and invariant enforcement within the aggregate boundary."} | верно | Репозиторий корня хранит границу согласованности агрегата; вложенные сущности доступны только через корень. |
T26-L5 0.87 c | DDD | Ubiquitous language is the model's shared language common to developers and domain experts. | «yes» Пояснение: In Domain-Driven Design, the Ubiquitous Language is the shared vocabulary used consistently by both developers and domain experts in code, documentation, and conversation.
Raw{"answer": "yes", "explanation": "In Domain-Driven Design, the Ubiquitous Language is the shared vocabulary used consistently by both developers and domain experts in code, documentation, and conversation."} | верно | Evans: язык из требований переходит в имена классов и методов. |
T26-L6 3.42 c | DDD | What is the boundary called within which a model and its language are consistent, while outside the same words mean other models? | «frame» Пояснение: A frame is the boundary within which a model and its language are self-consistent, while outside it the same words can refer to different models or meanings.
Raw{"answer": "frame", "explanation": "A frame is the boundary within which a model and its language are self-consistent, while outside it the same words can refer to different models or meanings."} | неверно верный: «bounded context» | Bounded Context; «Заказ» в биллинге и в доставке — разные модели. |
T26-L7 1.18 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 lives inside entities and aggregates, not in external services; anemic models are considered an anti-pattern in DDD.
Raw{"answer": "no", "explanation": "DDD advocates for a rich domain model where business logic lives inside entities and aggregates, not in external services; anemic models are considered an anti-pattern in DDD."} | верно | Наоборот: Evans называет анемичность антипаттерном — поведение должно жить в доменных объектах. |
T26-L8 1.39 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 ensures that each context maintains its own model, so the same real-world concept (e.g., 'Product') is represented as a distinct class with its own meaning in each context.
Raw{"answer": "yes", "explanation": "In Domain-Driven Design, a Bounded Context ensures that each context maintains its own model, so the same real-world concept (e.g., 'Product') is represented as a distinct class with its own meaning in each context."} | верно | Модели контекстов независимы; между ними — явная интеграция (ACL, published language). |
T13-L1 1.49 c | Symfony | Services in the Symfony DI container are created lazily by default — on first use. | «yes» Пояснение: Symfony's DI container instantiates services only when they are first requested via get(), not eagerly at boot time.
Raw{"answer": "yes", "explanation": "Symfony's DI container instantiates services only when they are first requested via get(), not eagerly at boot time."} | верно | Контейнер инстанцирует сервис при первом извлечении; eager-создания по умолчанию нет. |
T13-L2 1.3 c | Symfony | Which Symfony console command lists all registered routes? | «debug:router» Пояснение: The Symfony console command to list all registered routes is 'bin/console debug:router'.
Raw{"answer": "debug:router", "explanation": "The Symfony console command to list all registered routes is 'bin/console debug:router'."} | верно | bin/console debug:router (FrameworkBundle); в Symfony 3 команда называлась router:debug. |
T13-L3 1.68 c | Symfony | Symfony autowiring requires manually declaring every service in services.yaml. | «no» Пояснение: Autowiring in Symfony automatically resolves dependencies based on type hints, so services do not need to be manually declared in services.yaml.
Raw{"answer": "no", "explanation": "Autowiring in Symfony automatically resolves dependencies based on type hints, so services do not need to be manually declared in services.yaml."} | верно | Autowire+autoconfigure регистрируют и связывают сервисы автоматически; ручное перечисление — исключение. |
T13-L4 1.04 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 to avoid recompilation on subsequent requests.
Raw{"answer": "yes", "explanation": "Twig compiles templates into PHP classes (extending Twig\\Template) and caches the compiled output to avoid recompilation on subsequent requests."} | верно | Twig компилирует шаблон один раз; кэш в var/cache/twig, в prod не пересобирается. |
T13-L5 1.23 c | Symfony | In the Symfony dev environment the DI container is rebuilt only after tracked files change, not on every request. | «yes» Пояснение: In the dev environment, Symfony caches the compiled container and only rebuilds it when tracked files (config, classes, etc.) have changed, not on every request.
Raw{"answer": "yes", "explanation": "In the dev environment, Symfony caches the compiled container and only rebuilds it when tracked files (config, classes, etc.) have changed, not on every request."} | верно | Kernel проверяет freshness ресурсов (конфиги, классы); иначе переиспользуется кэш контейнера. |
T13-L6 0.95 c | Symfony | Which environment variable selects the active Symfony environment (dev/prod)? | «app_env» Пояснение: The APP_ENV environment variable is used by Symfony to select the active environment (e.g., dev, prod, test).
Raw{"answer": "APP_ENV", "explanation": "The APP_ENV environment variable is used by Symfony to select the active environment (e.g., dev, prod, test)."} | верно | APP_ENV в .env; APP_DEBUG — отдельный флаг отладки. |
T13-L7 0.76 c | Symfony | A controller method can be private — Symfony routing works with any method of the class. | «no» Пояснение: Symfony controller methods must be public; private or protected methods cannot be used as route targets.
Raw{"answer": "no", "explanation": "Symfony controller methods must be public; private or protected methods cannot be used as route targets."} | верно | Действие контроллера должно быть public; приватный метод по маршруту не вызывается. |
T13-L8 1.56 c | Symfony | Event subscribers always receive events before listeners, because the interface gives them priority. | «no» Пояснение: Event subscribers and listeners are dispatched based on their assigned priority (or registration order if equal); subscribers have no inherent priority over listeners.
Raw{"answer": "no", "explanation": "Event subscribers and listeners are dispatched based on their assigned priority (or registration order if equal); subscribers have no inherent priority over listeners."} | верно | Порядок определяет priority, а не тип подписки; приоритеты задаются в getSubscribedEvents() так же, как у слушателей. |
T22-L1 1.12 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 old guard system was deprecated in Symfony 5.3 and fully removed in Symfony 6.0, leaving AuthenticatorInterface as the sole authentication mechanism.
Raw{"answer": "yes", "explanation": "The old guard system was deprecated in Symfony 5.3 and fully removed in Symfony 6.0, leaving AuthenticatorInterface as the sole authentication mechanism."} | верно | Guard объявлен устаревшим в 5.3 и удалён в 6.0; в проекте symfony/security-bundle 8.1. |
T22-L2 1.9 c | Symfony: Security and forms | Which Symfony attribute checks a role/permission right on a controller method (403 without it)? | «isgranted» Пояснение: The #[IsGranted] attribute in Symfony checks if the current user has a specific role or permission, returning a 403 Forbidden if not.
Raw{"answer": "IsGranted", "explanation": "The #[IsGranted] attribute in Symfony checks if the current user has a specific role or permission, returning a 403 Forbidden if not."} | верно | #[IsGranted('ROLE_ADMIN')]; атрибут из symfony/security-http. |
T22-L3 1.07 c | Symfony: Security and forms | Voters are Symfony's mechanism for checking access to a specific object: isGranted('EDIT', $post). | «yes» Пояснение: Voters in Symfony are the mechanism for object-level access control, used with isGranted() to check permissions on specific objects like $post.
Raw{"answer": "yes", "explanation": "Voters in Symfony are the mechanism for object-level access control, used with isGranted() to check permissions on specific objects like $post."} | верно | VoterInterface->vote(); docs Symfony — Voters. |
T22-L4 1.56 c | Symfony: Security and forms | In modern Symfony (7+) validation constraints are declared as PHP attributes (#[Assert\NotBlank]); doctrine annotations are no longer supported. | «yes» Пояснение: Symfony 7 removed support for doctrine/annotations, so validation constraints must now be declared using native PHP 8 attributes like #[Assert\NotBlank].
Raw{"answer": "yes", "explanation": "Symfony 7 removed support for doctrine/annotations, so validation constraints must now be declared using native PHP 8 attributes like #[Assert\\NotBlank]."} | верно | Докблок-аннотации удалены в Symfony 7.0; стандарт — атрибуты. В проекте symfony/validator 8.1. |
T22-L5 0.93 c | Symfony: Security and forms | CSRF protection of Symfony forms is enabled by default: the form validates the token on submission. | «yes» Пояснение: Symfony forms include a CSRF token by default and validate it on submission unless explicitly disabled via framework config.
Raw{"answer": "yes", "explanation": "Symfony forms include a CSRF token by default and validate it on submission unless explicitly disabled via framework config."} | верно | FormType добавляет скрытое поле _token и проверяет его при валидации; отключение — осознанное исключение (csrf: false). |
T22-L6 1.0 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 using its Validation component; HTML5 client-side checks are merely a UX convenience and can be bypassed.
Raw{"answer": "yes", "explanation": "Symfony always performs server-side validation using its Validation component; HTML5 client-side checks are merely a UX convenience and can be bypassed."} | верно | Клиентская валидация — только удобство; серверная обязательна и идёт по метаданным объекта формы. |
T22-L7 0.51 c | Symfony: Security and forms | Which Symfony maker command generates a form class (FormType)? | «make:form» Пояснение: The Symfony MakerBundle command `make:form` generates a FormType class.
Raw{"answer": "make:form", "explanation": "The Symfony MakerBundle command `make:form` generates a FormType class."} | верно | bin/console make:form (symfony/maker-bundle — в проекте). |
T22-L8 1.09 c | Symfony: Security and forms | Symfony stores the user's password in the session in plain text. | «no» Пояснение: Symfony never stores passwords in plain text in the session; passwords are hashed (e.g., with bcrypt or Argon2) and stored in the database, while the session only holds the user identifier and authentication token.
Raw{"answer": "no", "explanation": "Symfony never stores passwords in plain text in the session; passwords are hashed (e.g., with bcrypt or Argon2) and stored in the database, while the session only holds the user identifier and authentication token."} | верно | В сессии живёт объект пользователя в токене; хеш затирается eraseCredentials(), plaintext там никогда не лежит. |
T23-L1 0.93 c | Symfony: configuration and services | Symfony bundle configuration lives in config/packages — one file per bundle or topic. | «yes» Пояснение: In modern Symfony, bundle configurations are conventionally placed in config/packages/ with one file per bundle or topic (e.g., framework.yaml, doctrine.yaml).
Raw{"answer": "yes", "explanation": "In modern Symfony, bundle configurations are conventionally placed in config/packages/ with one file per bundle or topic (e.g., framework.yaml, doctrine.yaml)."} | верно | Стандартная структура (config/packages/*.yaml); перегрузка — config/packages/<env>. |
T23-L2 2.11 c | Symfony: configuration and services | The .env file with dev defaults is committed to the repository, while real secrets live in the non-committed .env.local. | «yes» Пояснение: This is a common pattern (e.g., in Symfony) where .env holds safe dev defaults committed to git, while .env.local holds real secrets and is gitignored.
Raw{"answer": "yes", "explanation": "This is a common pattern (e.g., in Symfony) where .env holds safe dev defaults committed to git, while .env.local holds real secrets and is gitignored."} | верно | symfony/dotenv: .env — общий безопасный набор значений; локальные секреты — .env.local (gitignored) или secrets-хранилище. |
T23-L3 0.57 c | Symfony: configuration and services | Which Symfony command lists the container's registered services and their aliases? | «debug:container» Пояснение: The Symfony console command `debug:container` lists all registered services and their aliases in the dependency injection container.
Raw{"answer": "debug:container", "explanation": "The Symfony console command `debug:container` lists all registered services and their aliases in the dependency injection container."} | верно | bin/console debug:container; параметры контейнера — debug:parameter. |
T23-L4 2.17 c | Symfony: configuration and services | The Symfony container allows changing parameters at runtime: $container->setParameter() works from a controller. | «no» Пояснение: At runtime the container is compiled and immutable; setParameter() is only available on the ContainerBuilder during the build phase, not on the runtime Container instance.
Raw{"answer": "no", "explanation": "At runtime the container is compiled and immutable; setParameter() is only available on the ContainerBuilder during the build phase, not on the runtime Container instance."} | верно | Контейнер компилируется и замораживается; runtime-значения — только через переменные окружения. |
T23-L5 0.66 c | Symfony: configuration and services | By default, Symfony services are public (public: true) — you can fetch them directly from the container. | «no» Пояснение: Since Symfony 4.0, services are private by default (public: false); you must explicitly set public: true to fetch them from the container.
Raw{"answer": "no", "explanation": "Since Symfony 4.0, services are private by default (public: false); you must explicitly set public: true to fetch them from the container."} | верно | С Symfony 4.0 сервисы по умолчанию private: инжектятся через autowiring; $container->get() — только для публичных. |
T23-L6 0.77 c | Symfony: configuration and services | Without a config file in config/packages a bundle will not work — configuration is mandatory for every bundle. | «no» Пояснение: Many bundles in Symfony work perfectly fine without a configuration file in config/packages, as they provide sensible defaults and configuration is not mandatory for every bundle.
Raw{"answer": "no", "explanation": "Many bundles in Symfony work perfectly fine without a configuration file in config/packages, as they provide sensible defaults and configuration is not mandatory for every bundle."} | верно | У бандлов есть встроенные умолчания (Extension); конфиг нужен только для отклонений от них. |
T23-L7 0.66 c | Symfony: configuration and services | Environment variable values are injected into services.yaml using the %env(VAR)% syntax. | «yes» Пояснение: In Symfony, environment variables are injected into configuration files like services.yaml using the %env(VAR)% syntax.
Raw{"answer": "yes", "explanation": "In Symfony, environment variables are injected into configuration files like services.yaml using the %env(VAR)% syntax."} | верно | %env(...)% резолвится в рантайме env-процессорами; docs — Env Var Processors. |
T23-L8 0.76 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 controls Symfony's debug mode, enabling the profiler and Twig debug features.
Raw{"answer": "APP_DEBUG", "explanation": "The APP_DEBUG environment variable controls Symfony's debug mode, enabling the profiler and Twig debug features."} | верно | APP_DEBUG=1 (в .env dev-окружения); окружение выбирает APP_ENV — см. T13-L6. |
T16-L1 1.12 c | Symfony: Messenger | A single message in Symfony Messenger can only have one handler. | «no» Пояснение: Symfony Messenger allows multiple handlers to be registered for the same message class, and all of them will be called in order.
Raw{"answer": "no", "explanation": "Symfony Messenger allows multiple handlers to be registered for the same message class, and all of them will be called in order."} | верно | Messenger вызывает все хендлеры, подписанные на класс сообщения (docs — Multiple Handlers). |
T16-L2 1.06 c | Symfony: Messenger | The sync transport in Messenger queues the message for a worker, just like async. | «no» Пояснение: The sync transport handles the message immediately in the same process without queuing it for a worker.
Raw{"answer": "no", "explanation": "The sync transport handles the message immediately in the same process without queuing it for a worker."} | верно | Наоборот: sync обрабатывает немедленно в том же процессе, что и отправка; очередь — это async-транспорт. |
T16-L3 0.53 c | Symfony: Messenger | Which console command starts the worker that processes Messenger queue messages? | «messenger:consume» Пояснение: The Symfony Messenger command to start a worker that processes queued messages is messenger:consume.
Raw{"answer": "messenger:consume", "explanation": "The Symfony Messenger command to start a worker that processes queued messages is messenger:consume."} | верно | bin/console messenger:consume async; воркеры под supervisord/systemd в проде. |
T16-L4 1.24 c | Symfony: Messenger | Retries for failed messages (retry_strategy) are configured per Messenger transport. | «no» Пояснение: The retry_strategy is configured at the message bus level (under messenger.buses), not per transport.
Raw{"answer": "no", "explanation": "The retry_strategy is configured at the message bus level (under messenger.buses), not per transport."} | неверно верный: «yes» | retry_strategy на транспорте: max_retries, delay, multiplier; docs — Failed Messages & Retries. |
T16-L5 0.86 c | Symfony: Messenger | By default, Messenger serializes messages to JSON. | «yes» Пояснение: Symfony Messenger's default serializer is JsonSerializer, which serializes messages to JSON by default.
Raw{"answer": "yes", "explanation": "Symfony Messenger's default serializer is JsonSerializer, which serializes messages to JSON by default."} | неверно верный: «no» | Дефолтный сериализатор — PhpSerializer (serialize()); JSON-сериализатор включается отдельно. |
T16-L6 1.15 c | Symfony: Messenger | Symfony Scheduler produces messages on a schedule and dispatches them through Messenger. | «yes» Пояснение: Symfony Scheduler schedules tasks (including message objects) and dispatches them through the Messenger component when their time comes.
Raw{"answer": "yes", "explanation": "Symfony Scheduler schedules tasks (including message objects) and dispatches them through the Messenger component when their time comes."} | верно | Schedule → RecurringMessage → шина Messenger; docs — Scheduler. |
T16-L7 0.83 c | Symfony: Messenger | Which built-in Messenger transport stores messages in database tables via Doctrine? | «doctrine» Пояснение: The doctrine transport in Symfony Messenger stores messages in database tables using Doctrine ORM/DBAL.
Raw{"answer": "doctrine", "explanation": "The doctrine transport in Symfony Messenger stores messages in database tables using Doctrine ORM/DBAL."} | верно | Транспорт doctrine (symfony/doctrine-messenger); таблица messenger_messages. В проекте стоит amqp-messenger + doctrine-messenger. |
T16-L8 1.27 c | Symfony: Messenger | The Messenger pipeline can be extended with custom middleware, placed before or after the built-in ones. | «yes» Пояснение: The Messenger pipeline (e.g., in Laravel) is extensible and allows adding custom middleware at any position, before or after built-in ones.
Raw{"answer": "yes", "explanation": "The Messenger pipeline (e.g., in Laravel) is extensible and allows adding custom middleware at any position, before or after built-in ones."} | верно | messenger.bus.*.middleware в yaml; docs — Middleware. |
T28-L1 1.21 c | Symfony: versions | Symfony major releases come every two years, minor ones every six months (in May and November). | «yes» Пояснение: Symfony releases minor versions every six months (May and November) and major versions every two years (November).
Raw{"answer": "yes", "explanation": "Symfony releases minor versions every six months (May and November) and major versions every two years (November)."} | верно | Стандартный релизный цикл: 8.0 — ноябрь 2025, 8.1 — май 2026, 8.2 — ноябрь 2026. |
T28-L2 1.91 c | Symfony: versions | What is the minimum PHP version required by Symfony 8? | «8.4» Пояснение: Symfony 8 requires a minimum PHP version of 8.4, following Symfony's pattern of requiring the two most recent PHP stable versions at release time.
Raw{"answer": "8.4", "explanation": "Symfony 8 requires a minimum PHP version of 8.4, following Symfony's pattern of requiring the two most recent PHP stable versions at release time."} | верно | Symfony 8.0 поднял требование до PHP >= 8.4.1 (в vendor проекта: "php": ">=8.4.1"). |
T28-L3 1.11 c | Symfony: versions | Symfony 7.0 kept support for docblock annotations (validation, routes). | «no» Пояснение: Symfony 7.0 removed support for docblock annotations; PHP 8 attributes are the only supported way to define validation rules, routes, etc.
Raw{"answer": "no", "explanation": "Symfony 7.0 removed support for docblock annotations; PHP 8 attributes are the only supported way to define validation rules, routes, etc."} | верно | Наоборот: в 7.0 аннотации удалены — только PHP-атрибуты (#[Route], #[Assert\NotBlank]). |
T28-L4 1.08 c | Symfony: versions | AssetMapper manages CSS/JS without node or webpack — via importmap.php. | «yes» Пояснение: Symfony's AssetMapper component manages CSS/JS assets without Node.js or Webpack, using an importmap.php file to define asset imports.
Raw{"answer": "yes", "explanation": "Symfony's AssetMapper component manages CSS/JS assets without Node.js or Webpack, using an importmap.php file to define asset imports."} | верно | symfony/asset-mapper (с 6.3, стандарт с 7.x); в проекте — importmap.php в корне и asset-mapper 8.1. |
T28-L5 1.18 c | Symfony: versions | Symfony 6.4 is a regular release without long-term support. | «no» Пояснение: Symfony 6.4 is a Long-Term Support (LTS) release, with bug fixes until November 2025 and security fixes until November 2027.
Raw{"answer": "no", "explanation": "Symfony 6.4 is a Long-Term Support (LTS) release, with bug fixes until November 2025 and security fixes until November 2027."} | верно | Наоборот: 6.4 — LTS (расширенная поддержка); LTS выходит вместе с очередным мажором (6.4 — вместе с 7.0). |
T28-L6 1.28 c | Symfony: versions | When moving to a new Symfony major version, deprecations of the previous branch keep working — major releases do not remove them. | «no» Пояснение: In Symfony, deprecated features are removed in the next major version; that is the entire purpose of the deprecation cycle.
Raw{"answer": "no", "explanation": "In Symfony, deprecated features are removed in the next major version; that is the entire purpose of the deprecation cycle."} | верно | Наоборот: мажорный релиз удаляет всё устаревшее (7.0 убрал деприкейшены 6.x, 8.0 — 7.x). |
T28-L7 1.17 c | Symfony: versions | Every Symfony major release is accompanied by an UPGRADE guide listing the changes. | «yes» Пояснение: Each Symfony major release includes an UPGRADE-X.Y file in the repository documenting breaking changes, removed deprecations, and other migrations.
Raw{"answer": "yes", "explanation": "Each Symfony major release includes an UPGRADE-X.Y file in the repository documenting breaking changes, removed deprecations, and other migrations."} | верно | UPGRADE-7.0.md, UPGRADE-8.0.md в репозитории symfony/symfony. |
T28-L8 0.88 c | Symfony: versions | Which Symfony component manages assets and the importmap without node/webpack? | «assetmapper» Пояснение: Symfony's AssetMapper component (introduced in 6.4) manages assets and import maps without requiring Node.js or webpack.
Raw{"answer": "AssetMapper", "explanation": "Symfony's AssetMapper component (introduced in 6.4) manages assets and import maps without requiring Node.js or webpack."} | верно | symfony/asset-mapper 8.1 — в проекте. |
T29-L1 7.24 c | Symfony: 8.2 and beyond | As of 2026-11-07, Symfony 8.2 has already been released. | «no» Пояснение: Symfony 8.2 is a November 2026 release (8.0 in Nov 2025, 8.1 in May 2026, 8.2 in Nov 2026), so it would not have been released yet as of November 7, 2026.
Raw```json ⏎ {"answer": "no", "explanation": "Symfony 8.2 is a November 2026 release (8.0 in Nov 2025, 8.1 in May 2026, 8.2 in Nov 2026), so it would not have been released yet as of November 7, 2026."} ⏎ ``` | верно | Наоборот: 8.2 ещё не выпущена — релиз в конце ноября 2026; последняя стабильная — 8.1. |
T29-L2 1.58 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. | «yes» Пояснение: Symfony releases minor versions every six months (May and November), so 8.0 (Nov 2025), 8.1 (May 2026), and 8.2 (Nov 2026) follows the standard cycle.
Raw{"answer": "yes", "explanation": "Symfony releases minor versions every six months (May and November), so 8.0 (Nov 2025), 8.1 (May 2026), and 8.2 (Nov 2026) follows the standard cycle."} | верно | Политика релизов: 8.1 — май 2026, 8.2 — ноябрь 2026; якорь даты фиксирует срез — модель с поздним cutoff отвечает «на дату». |
T29-L3 1.05 c | Symfony: 8.2 and beyond | Which Symfony version comes after 8.1 (as of 2026-11-07)? | «8.2» Пояснение: Symfony releases minor versions every 6 months, so 8.2 follows 8.1.
Raw{"answer": "8.2", "explanation": "Symfony releases minor versions every 6 months, so 8.2 follows 8.1."} | верно | 8.2 — следующий минорный релиз (ноябрь 2026); после его выхода проект переходит с 8.1.* на 8.2.*. |
T29-L4 2.3 c | Symfony: 8.2 and beyond | Symfony 8.2 is a major release requiring applications to be rewritten for new APIs. | «no» Пояснение: Symfony 8.2 would be a minor release (not major), and Symfony's major releases follow a deprecation policy rather than requiring full rewrites.
Raw{"answer": "no", "explanation": "Symfony 8.2 would be a minor release (not major), and Symfony's major releases follow a deprecation policy rather than requiring full rewrites."} | верно | Наоборот: 8.2 — минорный релиз; новые возможности без поломки обратной совместимости. Мажор — 9.0. |
T29-L5 3.26 c | Symfony: 8.2 and beyond | Updating within a major branch (8.1 → 8.2) should not require code changes — backward compatibility is preserved. | «no» Пояснение: In PHP, each x.y release (e.g., 8.1 → 8.2) is considered a major release, and backward compatibility is NOT guaranteed; deprecated features can be removed and new deprecations are introduced between these versions.
Raw{"answer": "no", "explanation": "In PHP, each x.y release (e.g., 8.1 → 8.2) is considered a major release, and backward compatibility is NOT guaranteed; deprecated features can be removed and new deprecations are introduced between these versions."} | неверно верный: «yes» | Политика Symfony: минорные релизы обратно совместимы; BC-break допустим только в мажорных. |
T29-L6 4.26 c | Symfony: 8.2 and beyond | Which minor version of the 8.x branch is released last, before Symfony 9.0? | «8.4» Пояснение: Symfony follows a pattern where each major branch ends at .4 (the LTS version), so the last 8.x release before 9.0 is 8.4.
Raw```json ⏎ {"answer": "8.4", "explanation": "Symfony follows a pattern where each major branch ends at .4 (the LTS version), so the last 8.x release before 9.0 is 8.4."} ⏎ ``` | верно | По циклу: 8.2 (ноя 2026), 8.3 (май 2027), 8.4 (ноя 2027, вместе с 9.0) — как 6.4 выходила вместе с 7.0. |
T29-L7 4.09 c | Symfony: 8.2 and beyond | Symfony 8.2 will require PHP 8.5 — you would have to upgrade PHP along with it. | «no» Пояснение: Symfony 8.x is expected to require PHP 8.4 as its minimum, not PHP 8.5.
Raw{"answer": "no", "explanation": "Symfony 8.x is expected to require PHP 8.4 as its minimum, not PHP 8.5."} | верно | Наоборот: минорные релизы не поднимают требования PHP; для всей ветки 8.x остаётся PHP >= 8.4. |
T29-L8 1.53 c | Symfony: 8.2 and beyond | Deprecations added in the 8.x branch will not be removed before Symfony 9.0. | «yes» Пояснение: Symfony's policy is that deprecations introduced in a major version (8.x) are removed in the next major version (9.0), so they will not be removed before 9.0.
Raw{"answer": "yes", "explanation": "Symfony's policy is that deprecations introduced in a major version (8.x) are removed in the next major version (9.0), so they will not be removed before 9.0."} | верно | Политика: деприкейшены живут до следующего мажора; 9.0 — ноябрь 2027. |
T21-L1 1.43 c | Twig | Inside {{ }}, Twig allows calling arbitrary PHP code directly. | «no» Пояснение: Twig's {{ }} syntax only supports Twig's own expressions (variables, filters, functions, operators), not arbitrary PHP code.
Raw{"answer": "no", "explanation": "Twig's {{ }} syntax only supports Twig's own expressions (variables, filters, functions, operators), not arbitrary PHP code."} | верно | Twig — DSL: только разрешённые окружением функции/фильтры; произвольный PHP не исполняется. |
T21-L2 0.75 c | Twig | By default, Twig auto-escapes printed variables. | «yes» Пояснение: Twig has auto-escaping enabled by default with the 'html' strategy to prevent XSS attacks.
Raw{"answer": "yes", "explanation": "Twig has auto-escaping enabled by default with the 'html' strategy to prevent XSS attacks."} | верно | Autoescape включён по умолчанию; {{ '<b>' }} → <b>. Проверено на Twig 3.30. |
T21-L3 1.15 c | Twig | The Twig |e filter escapes a string for safe output in an HTML context. | «yes» Пояснение: The |e filter in Twig applies HTML escaping (equivalent to htmlspecialchars with ENT_QUOTES) by default to prevent XSS attacks.
Raw{"answer": "yes", "explanation": "The |e filter in Twig applies HTML escaping (equivalent to htmlspecialchars with ENT_QUOTES) by default to prevent XSS attacks."} | верно | |e ('html') по умолчанию; есть контексты js/url/css. От SQL-инъекций он не защищает — это задача подготовленных запросов Doctrine. |
T21-L4 1.34 c | Twig | Which filter from twig/intl-extra formats a number according to a locale? | «localizednumber» Пояснение: The twig/intl-extra package provides the localizednumber filter which formats a number according to a given locale.
Raw{"answer": "localizednumber", "explanation": "The twig/intl-extra package provides the localizednumber filter which formats a number according to a given locale."} | неверно верный: «format_number» | |format_number(locale=...) из IntlExtension (twig/intl-extra есть в проекте). Проверено на Twig 3.30: 12345.6 → 12 345,6 (ru). |
T21-L5 1.37 c | Twig | The |raw filter disables auto-escaping for the value. | «yes» Пояснение: The |raw filter (used in Twig and similar templating engines) marks a value as safe, bypassing automatic HTML escaping.
Raw{"answer": "yes", "explanation": "The |raw filter (used in Twig and similar templating engines) marks a value as safe, bypassing automatic HTML escaping."} | верно | {{ 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, double curly braces {{ }} output the result of an expression, while percent braces {% %} execute control-structure tags like if, for, set, etc.
Raw{"answer": "yes", "explanation": "In Twig, double curly braces {{ }} output the result of an expression, while percent braces {% %} execute control-structure tags like if, for, set, etc."} | верно | Два блока синтаксиса Twig: вывод (echo) против логики. |
T21-L7 0.86 c | Twig | In Twig you cannot declare a variable inside a template — values only come from the controller. | «no» Пояснение: Twig allows you to set variables inside a template using the {% set %} tag, e.g. {% set foo = 'bar' %}.
Raw{"answer": "no", "explanation": "Twig allows you to set variables inside a template using the {% set %} tag, e.g. {% set foo = 'bar' %}."} | верно | {% set y = ... %} объявляет переменную в шаблоне. Проверено на Twig 3.30. |
T21-L8 0.77 c | Twig | Which Twig function dumps the debug structure of a variable (array, object)? | «dump» Пояснение: The Twig function dump() outputs the debug structure of a variable (array, object, etc.), typically using var_dump under the hood.
Raw{"answer": "dump", "explanation": "The Twig function dump() outputs the debug structure of a variable (array, object, etc.), typically using var_dump under the hood."} | верно | {{ dump(x) }} (DebugExtension; в Symfony доступна в dev-окружении). |
T24-L1 0.89 c | Bootstrap | Bootstrap is a CSS/JS library of ready-made UI components, not an SPA framework. | «yes» Пояснение: Bootstrap is a front-end CSS/JS framework providing ready-made UI components and utilities, not an SPA framework like React, Angular, or Vue.
Raw{"answer": "yes", "explanation": "Bootstrap is a front-end CSS/JS framework providing ready-made UI components and utilities, not an SPA framework like React, Angular, or Vue."} | верно | Компоненты и утилиты поверх вашего HTML; SPA-фреймворки (React/Vue) — другой класс инструментов. В проекте vendored 5.3.3. |
T24-L2 0.97 c | Bootstrap | Which Bootstrap class gives a responsive container with a fixed max width per breakpoint? | «container» Пояснение: The .container class in Bootstrap provides a responsive fixed-width container with a max-width that changes at each breakpoint.
Raw{"answer": "container", "explanation": "The .container class in Bootstrap provides a responsive fixed-width container with a max-width that changes at each breakpoint."} | верно | .container (фиксированная макс-ширина по брейкпоинтам) vs .container-fluid (на всю ширину). |
T24-L3 1.02 c | Bootstrap | The Bootstrap grid is built on CSS floats and splits a row into 16 columns. | «no» Пояснение: The Bootstrap grid is built on Flexbox (not CSS floats) and splits a row into 12 columns (not 16).
Raw{"answer": "no", "explanation": "The Bootstrap grid is built on Flexbox (not CSS floats) and splits a row into 12 columns (not 16)."} | верно | Наоборот: flexbox (с Bootstrap 4) и 12 колонок; float-сетка — это Bootstrap 3. |
T24-L4 1.25 c | Bootstrap | Bootstrap's named breakpoints (the infix used in class names) are sm, md, lg, xl, xxl — five of them. | «yes» Пояснение: Bootstrap 5 defines exactly five named breakpoints (sm, md, lg, xl, xxl) that can be used as infixes in utility and grid class names.
Raw{"answer": "yes", "explanation": "Bootstrap 5 defines exactly five named breakpoints (sm, md, lg, xl, xxl) that can be used as infixes in utility and grid class names."} | верно | Тиров всего шесть: xs (без инфикса) + пять именованных (576/768/992/1200/1400 px). |
T24-L5 2.29 c | Bootstrap | Utilities like .mt-3 or .px-2 use the spacing scale: the number is a multiple of $spacer. | «no» Пояснение: The spacing scale is not a direct linear multiple of $spacer; for example, .mt-1 equals $spacer * 0.25 and .mt-3 equals $spacer * 1, so the number does not correspond to a simple multiple.
Raw{"answer": "no", "explanation": "The spacing scale is not a direct linear multiple of $spacer; for example, .mt-1 equals $spacer * 0.25 and .mt-3 equals $spacer * 1, so the number does not correspond to a simple multiple."} | верно | Spacing utilities; $spacer = 1rem. |
T24-L6 0.8 c | Bootstrap | Which Bootstrap 5 data attribute enables an interactive component (e.g. dropdown) on an element? | «data-bs-toggle» Пояснение: In Bootstrap 5, the data-bs-toggle attribute is used to enable interactive components such as dropdowns, modals, and collapses on an element.
Raw{"answer": "data-bs-toggle", "explanation": "In Bootstrap 5, the data-bs-toggle attribute is used to enable interactive components such as dropdowns, modals, and collapses on an element."} | верно | data-bs-toggle="dropdown" и т.п.; в Bootstrap 4 атрибут назывался data-toggle. |
T24-L7 0.79 c | Bootstrap | Bootstrap 5 components work without jQuery — in plain vanilla JS. | «yes» Пояснение: Bootstrap 5 dropped its jQuery dependency and uses vanilla JavaScript for all its interactive components.
Raw{"answer": "yes", "explanation": "Bootstrap 5 dropped its jQuery dependency and uses vanilla JavaScript for all its interactive components."} | верно | jQuery удалён в Bootstrap 5.0: data-bs-* атрибуты и JS API. В проекте vendored 5.3.3. |
T24-L8 1.15 c | Bootstrap | Dark mode in Bootstrap is enabled with a .dark class on the root element. | «no» Пояснение: Bootstrap 5 enables dark mode via the data-bs-theme="dark" attribute on the <html> element, not a .dark class.
Raw{"answer": "no", "explanation": "Bootstrap 5 enables dark mode via the data-bs-theme=\"dark\" attribute on the <html> element, not a .dark class."} | верно | Наоборот: тема включается атрибутом data-bs-theme="dark" (Color modes, с 5.3); класса .dark не существует. В проекте 5.3.3. |
T14-L1 1.24 c | Doctrine | Doctrine ORM creates database tables on the fly the first time an entity is used at runtime. | «no» Пояснение: Doctrine ORM does not auto-create tables; you must explicitly run schema commands or migrations to create/update database tables.
Raw{"answer": "no", "explanation": "Doctrine ORM does not auto-create tables; you must explicitly run schema commands or migrations to create/update database tables."} | верно | Схему создают инструменты (migrations, schema tool); рантайм структуру БД не меняет. |
T14-L2 0.69 c | Doctrine | Which EntityManager method marks a new object as managed without executing SQL until flush()? | «persist()» Пояснение: EntityManager::persist() marks a new entity as managed, deferring the actual SQL INSERT until flush() is called.
Raw{"answer": "persist()", "explanation": "EntityManager::persist() marks a new entity as managed, deferring the actual SQL INSERT until flush() is called."} | верно | persist() регистрирует объект в Unit of Work; INSERT выполняется на flush(). |
T14-L3 2.73 c | Doctrine | In Doctrine ORM 3, the EntityManager::merge() method exists and makes the passed object managed. | «no» Пояснение: EntityManager::merge() returns a managed *copy* of the passed entity; the original detached object itself is not made managed.
Raw{"answer": "no", "explanation": "EntityManager::merge() returns a managed *copy* of the passed entity; the original detached object itself is not made managed."} | верно | В ORM 3 merge() удалён (в vendor проекта 3.7.6 метода нет); в Doctrine 2.x merge() возвращал управляемую копию. Версия зафиксирована — ORM 3. |
T14-L4 0.93 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 operates on entity names and their properties, abstracting away the underlying table and column structure.
Raw{"answer": "yes", "explanation": "DQL (Doctrine Query Language) is an object-oriented query language that operates on entity names and their properties, abstracting away the underlying table and column structure."} | верно | Doctrine транслирует DQL в SQL; docs — DQL (Doctrine Query Language). |
T14-L5 0.66 c | Doctrine | What does $repository->find(999) return when no record with id 999 exists? | «null» Пояснение: Doctrine's EntityRepository::find() returns null when no entity with the given ID is found.
Raw{"answer": "null", "explanation": "Doctrine's EntityRepository::find() returns null when no entity with the given ID is found."} | верно | find() возвращает null, если объект не найден (docs Repository methods). |
T14-L6 1.38 c | Doctrine | DoctrineBundle in Symfony automatically calls flush() at the end of every request. | «no» Пояснение: DoctrineBundle does not automatically call flush(); it only commits or rolls back the transaction at the end of the request, so the developer must explicitly call flush() to persist changes.
Raw{"answer": "no", "explanation": "DoctrineBundle does not automatically call flush(); it only commits or rolls back the transaction at the end of the request, so the developer must explicitly call flush() to persist changes."} | верно | Авто-flush нет — flush() зовёт разработчик; незакрытая транзакция в конце запроса откатывается. |
T14-L7 1.32 c | Doctrine | For a managed entity, changing a property is enough: flush() commits the change without an explicit persist() — the Unit of Work tracks changes. | «yes» Пояснение: The Unit of Work tracks managed entities and detects property changes on flush(), so no explicit persist() is needed for already-managed entities.
Raw{"answer": "yes", "explanation": "The Unit of Work tracks managed entities and detects property changes on flush(), so no explicit persist() is needed for already-managed entities."} | верно | Dirty checking сравнивает снимки свойств; persist нужен только новым/отсоединённым объектам. |
T14-L8 1.02 c | Doctrine | remove() executes the SQL DELETE immediately, without waiting for flush(). | «no» Пояснение: remove() only schedules the entity for deletion in the UnitOfWork; the actual SQL DELETE is executed when flush() is called.
Raw{"answer": "no", "explanation": "remove() only schedules the entity for deletion in the UnitOfWork; the actual SQL DELETE is executed when flush() is called."} | верно | remove() планирует удаление в Unit of Work; DELETE выполняется на flush() (docs — Deleting Objects). |
T15-L1 0.98 c | PostgreSQL | PostgreSQL uses MVCC, therefore readers block writers and writers block readers. | «no» Пояснение: MVCC is specifically designed so that readers do NOT block writers and writers do NOT block readers; that's the entire purpose of multi-version concurrency control.
Raw{"answer": "no", "explanation": "MVCC is specifically designed so that readers do NOT block writers and writers do NOT block readers; that's the entire purpose of multi-version concurrency control."} | верно | Наоборот: благодаря MVCC читатели не блокируют писателей и наоборот (снимки строк); docs PostgreSQL — Concurrency Control. |
T15-L2 0.8 c | PostgreSQL | Which SQL command shows a query's execution plan without executing the query? | «explain» Пояснение: The EXPLAIN command displays the query execution plan without actually running the query.
Raw{"answer": "EXPLAIN", "explanation": "The EXPLAIN command displays the query execution plan without actually running the query."} | верно | EXPLAIN без ANALYZE только строит план; проверено на PostgreSQL 17.7. |
T15-L3 2.33 c | PostgreSQL | SERIAL and GENERATED ... AS IDENTITY are just two names for the same mechanism. | «no» Пояснение: SERIAL is syntactic sugar that creates a separate sequence object and sets it as the column's default, while GENERATED ... AS IDENTITY is a SQL-standard built-in identity column mechanism with different internal behavior (e.g., tied to the column, supports GENERATED ALWAYS/BY DEFAULT, and cannot be independently dropped as a standalone object).
Raw{"answer": "no", "explanation": "SERIAL is syntactic sugar that creates a separate sequence object and sets it as the column's default, while GENERATED ... AS IDENTITY is a SQL-standard built-in identity column mechanism with different internal behavior (e.g., tied to the column, supports GENERATED ALWAYS/BY DEFAULT, and cannot be independently dropped as a standalone object)."} | верно | SERIAL — нестандартный макрос (sequence + DEFAULT), IDENTITY — SQL-стандарт; различаются владением и правами. Оба есть в PG 17 (проверено). |
T15-L4 1.05 c | PostgreSQL | By default, a PostgreSQL UNIQUE constraint allows only one row with NULL in the column. | «no» Пояснение: In PostgreSQL, NULL values are considered distinct from each other, so a UNIQUE constraint allows multiple rows to have NULL in the column.
Raw{"answer": "no", "explanation": "In PostgreSQL, NULL values are considered distinct from each other, so a UNIQUE constraint allows multiple rows to have NULL in the column."} | верно | Наоборот: NULLS DISTINCT по умолчанию — несколько NULL допустимы; NULLS NOT DISTINCT — опция с PG 15. Проверено на PG 17.7. |
T15-L5 0.55 c | PostgreSQL | Which PostgreSQL aggregate function concatenates strings with a separator? | «string_agg» Пояснение: PostgreSQL's string_agg(expression, delimiter) aggregate function concatenates string values with a specified separator.
Raw{"answer": "string_agg", "explanation": "PostgreSQL's string_agg(expression, delimiter) aggregate function concatenates string values with a specified separator."} | верно | string_agg(значение, разделитель); проверено на PostgreSQL 17.7. |
T15-L6 1.24 c | PostgreSQL | Plain VACUUM returns the space occupied by dead tuples to the operating system. | «no» Пояснение: Plain VACUUM reclaims space for internal reuse by the database but does not return it to the operating system; VACUUM FULL is needed for that.
Raw{"answer": "no", "explanation": "Plain VACUUM reclaims space for internal reuse by the database but does not return it to the operating system; VACUUM FULL is needed for that."} | верно | VACUUM помечает место для переиспользования внутри таблицы; ОС его возвращает только VACUUM FULL (с эксклюзивной блокировкой). |
T15-L7 0.67 c | PostgreSQL | Which keyword in a window function definition partitions rows into groups the function is computed over? | «partition» Пояснение: The PARTITION BY clause in a window function definition divides rows into groups over which the function is computed.
Raw{"answer": "PARTITION", "explanation": "The PARTITION BY clause in a window function definition divides rows into groups over which the function is computed."} | неверно верный: «partition by» | OVER (PARTITION BY ...); проверено на PostgreSQL 17.7. |
T15-L8 1.11 c | PostgreSQL | The READ COMMITTED isolation level protects against non-repeatable reads. | «no» Пояснение: READ COMMITTED only prevents dirty reads; non-repeatable reads are prevented by the REPEATABLE READ isolation level.
Raw{"answer": "no", "explanation": "READ COMMITTED only prevents dirty reads; non-repeatable reads are prevented by the REPEATABLE READ isolation level."} | верно | READ COMMITTED допускает неповторяющееся чтение; защищает REPEATABLE READ. Проверено: SHOW transaction_isolation → read committed. |
T17-L1 1.07 c | PostgreSQL: transactions and indexes | By default, PostgreSQL wraps each single SQL statement in its own implicit transaction (autocommit). | «yes» Пояснение: By default, PostgreSQL operates in autocommit mode, where each SQL statement is automatically committed upon completion, effectively wrapping each statement in its own implicit transaction.
Raw{"answer": "yes", "explanation": "By default, PostgreSQL operates in autocommit mode, where each SQL statement is automatically committed upon completion, effectively wrapping each statement in its own implicit transaction."} | верно | Без BEGIN каждый оператор коммитится сам; docs PostgreSQL — Transactions. Проверено на PG 17. |
T17-L2 0.43 c | PostgreSQL: transactions and indexes | Which SQL command ends a transaction, committing all its changes? | «commit» Пояснение: The COMMIT statement ends a database transaction, permanently saving all changes made within it.
Raw{"answer": "COMMIT", "explanation": "The COMMIT statement ends a database transaction, permanently saving all changes made within it."} | верно | COMMIT (END — синоним). Проверено на PG 17. |
T17-L3 0.94 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 the database engine locate rows quickly, which benefits SELECT, UPDATE, and DELETE queries that filter on indexed columns.
Raw{"answer": "yes", "explanation": "Indexes help the database engine locate rows quickly, which benefits SELECT, UPDATE, and DELETE queries that filter on indexed columns."} | верно | Поиск строк для изменения идёт по индексу; docs PostgreSQL — Indexes. |
T17-L4 0.87 c | PostgreSQL: transactions and indexes | To roll back part of the statements inside a transaction, PostgreSQL uses SAVEPOINT. | «yes» Пояснение: SAVEPOINT in PostgreSQL allows rolling back to a specific point within a transaction, undoing only the statements executed after that savepoint.
Raw{"answer": "yes", "explanation": "SAVEPOINT in PostgreSQL allows rolling back to a specific point within a transaction, undoing only the statements executed after that savepoint."} | верно | SAVEPOINT name; ROLLBACK TO name — частичный откат без отмены всей транзакции. Проверено на PG 17. |
T17-L5 0.98 c | PostgreSQL: transactions and indexes | EXPLAIN ANALYZE shows the query plan without executing the query. | «no» Пояснение: EXPLAIN ANALYZE actually executes the query and reports real execution times and row counts; plain EXPLAIN shows the plan without executing.
Raw{"answer": "no", "explanation": "EXPLAIN ANALYZE actually executes the query and reports real execution times and row counts; plain EXPLAIN shows the plan without executing."} | верно | Наоборот: ANALYZE реально выполняет запрос (с побочными эффектами!) и показывает фактические времена узлов; план без выполнения — plain EXPLAIN. |
T17-L6 0.64 c | PostgreSQL: transactions and indexes | Which PostgreSQL extension adds vector types and indexes for embedding search? | «pgvector» Пояснение: pgvector is a PostgreSQL extension that adds a vector data type and index support for similarity search on embeddings.
Raw{"answer": "pgvector", "explanation": "pgvector is a PostgreSQL extension that adds a vector data type and index support for similarity search on embeddings."} | верно | CREATE EXTENSION vector (проект pgvector; в проекте образ pgvector/pgvector:pg17). |
T17-L7 0.87 c | PostgreSQL: transactions and indexes | A partial index (CREATE INDEX ... WHERE ...) is built only over rows satisfying the condition. | «yes» Пояснение: A partial index (CREATE INDEX ... WHERE ...) only includes rows that satisfy the specified condition, reducing index size and improving query performance for targeted lookups.
Raw{"answer": "yes", "explanation": "A partial index (CREATE INDEX ... WHERE ...) only includes rows that satisfy the specified condition, reducing index size and improving query performance for targeted lookups."} | верно | docs PostgreSQL — Partial Indexes; типичный кейс — индекс по «активным» записям. |
T17-L8 1.36 c | PostgreSQL: transactions and indexes | The SERIALIZABLE level in PostgreSQL is implemented by locking the rows a transaction reads. | «no» Пояснение: PostgreSQL implements SERIALIZABLE using Serializable Snapshot Isolation (SSI), which detects and aborts conflicting transactions via dependency tracking, not by locking read rows.
Raw{"answer": "no", "explanation": "PostgreSQL implements SERIALIZABLE using Serializable Snapshot Isolation (SSI), which detects and aborts conflicting transactions via dependency tracking, not by locking read rows."} | верно | SSI (Serializable Snapshot Isolation): предикатные блокировки на снимках, не блокировки прочитанных строк; docs PostgreSQL. |
T19-L1 0.77 c | HTTP and REST API | HTTP status 201 means the request resulted in a new resource being created. | «yes» Пояснение: HTTP 201 'Created' indicates that the request was successful and a new resource was created as a result.
Raw{"answer": "yes", "explanation": "HTTP 201 'Created' indicates that the request was successful and a new resource was created as a result."} | верно | 201 Created; обычно на POST, часто с Location; RFC 9110. |
T19-L2 1.06 c | HTTP and REST API | Which HTTP status means a successful request with an empty response body (e.g. after DELETE)? | «204» Пояснение: HTTP 204 No Content indicates a successful request with no response body, commonly used after DELETE operations.
Raw{"answer": 204, "explanation": "HTTP 204 No Content indicates a successful request with no response body, commonly used after DELETE operations."} | верно | 204 No Content; RFC 9110. |
T19-L3 8.66 c | HTTP and REST API | The DELETE method is idempotent per the HTTP specification: repeating the request for the same resource does not change the outcome. | «yes» Пояснение: RFC 9110 (HTTP Semantics) classifies DELETE as an idempotent method: repeating the request for the same resource does not produce a different outcome than the first request.
Raw```json ⏎ {"answer": "yes", "explanation": "RFC 9110 (HTTP Semantics) classifies DELETE as an idempotent method: repeating the request for the same resource does not produce a different outcome than the first request."} ⏎ ``` | верно | RFC 9110: DELETE идемпотентен (как PUT); идемпотентность ≠ безопасность — ресурс удаляется при первом вызове. |
T19-L4 0.88 c | HTTP and REST API | The Access-Control-Allow-Origin header is sent by the client so that the server agrees to accept requests from another origin. | «no» Пояснение: The Access-Control-Allow-Origin header is sent by the server, not the client, to indicate which origin is permitted to access the resource.
Raw{"answer": "no", "explanation": "The Access-Control-Allow-Origin header is sent by the server, not the client, to indicate which origin is permitted to access the resource."} | верно | Наоборот: заголовок шлёт СЕРВЕР в ответе, разрешая браузеру cross-origin запрос (CORS); в проекте nelmio/cors-bundle. |
T19-L5 0.91 c | HTTP and REST API | Status 429 Too Many Requests is used when a client exceeds a rate limit. | «yes» Пояснение: HTTP 429 Too Many Requests is specifically defined in RFC 6585 to indicate that a client has exceeded the allowed rate limit.
Raw{"answer": "yes", "explanation": "HTTP 429 Too Many Requests is specifically defined in RFC 6585 to indicate that a client has exceeded the allowed rate limit."} | верно | 429 (+ Retry-After); RFC 6585. В проекте symfony/rate-limiter. |
T19-L6 0.8 c | HTTP and REST API | 5xx codes mean a client error, while 4xx means a server-side error. | «no» Пояснение: It's the opposite: 4xx codes indicate client errors and 5xx codes indicate server-side errors.
Raw{"answer": "no", "explanation": "It's the opposite: 4xx codes indicate client errors and 5xx codes indicate server-side errors."} | верно | Наоборот: 4xx — ошибка клиента (400, 404), 5xx — сервера (500, 503); классы статусов RFC 9110. |
T19-L7 0.42 c | HTTP and REST API | Which HTTP header indicates the MIME type of the request or response body? | «content-type» Пояснение: The Content-Type 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.26 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, while PUT is defined as idempotent in RFC 7231.
Raw{"answer": "yes", "explanation": "RFC 5789 explicitly states that PATCH is not idempotent, while PUT is defined as idempotent in RFC 7231."} | верно | RFC 5789 прямо оговаривает: PATCH не гарантированно идемпотентен; PUT идемпотентен. |
T20-L1 1.02 c | Security and OAuth | Checking a password by comparing its hash to the stored hash with a plain == is sufficient. | «no» Пояснение: Using == is vulnerable to timing attacks; you should use hash_equals() or password_verify() for constant-time comparison.
Raw```json ⏎ {"answer": "no", "explanation": "Using == is vulnerable to timing attacks; you should use hash_equals() or password_verify() for constant-time comparison."} ⏎ ``` | верно | Нужна постоянновременная проверка (password_verify) — timing-атаки; соль и алгоритм уже внутри хеша. |
T20-L2 0.69 c | Security and OAuth | A CSRF token is issued by the server (bound to the session) and verified server-side on unsafe requests (POST etc.). | «yes» Пояснение: CSRF tokens are server-issued, session-bound, and verified server-side on state-changing requests like POST.
Raw{"answer": "yes", "explanation": "CSRF tokens are server-issued, session-bound, and verified server-side on state-changing requests like POST."} | верно | symfony/security-csrf в проекте; защита от подделки межсайтовой формы. |
T20-L3 0.77 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 which resources are allowed to load and execute on the page.
Raw{"answer": "Content-Security-Policy", "explanation": "The Content-Security-Policy HTTP header is used to specify which resources are allowed to load and execute on the page."} | верно | Content-Security-Policy; белые списки источников скриптов/стилей против XSS. |
T20-L4 1.05 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; the access token grants permission to access resources but does not identify who the user is.
Raw{"answer": "no", "explanation": "OAuth 2.0 is an authorization protocol, not an authentication protocol; the access token grants permission to access resources but does not identify who the user is."} | верно | OAuth 2.0 — авторизация/делегирование доступа; аутентификацию добавляет OpenID Connect. В проекте knpuniversity/oauth2-client-bundle (yandex/github/google). |
T20-L5 1.29 c | Security and OAuth | XSS is prevented by validating input on the server before writing it to the database. | «no» Пояснение: XSS is prevented by output encoding (context-aware encoding) at the point of output, not by input validation or sanitization before storing in the database.
Raw{"answer": "no", "explanation": "XSS is prevented by output encoding (context-aware encoding) at the point of output, not by input validation or sanitization before storing in the database."} | верно | XSS лечится контекстным экранированием НА ВЫВОДЕ (Twig autoescape, CSP); валидация ввода не покрывает все контексты вывода. |
T20-L6 0.76 c | Security and OAuth | In the OAuth 2.0 authorization code flow, which parameter arrives at the redirect_uri and is exchanged for an access token? | «code» Пояснение: In the OAuth 2.0 authorization code flow, the 'code' parameter is appended to the redirect_uri and then exchanged at the token endpoint for an access token.
Raw{"answer": "code", "explanation": "In the OAuth 2.0 authorization code flow, the 'code' parameter is appended to the redirect_uri and then exchanged at the token endpoint for an access token."} | верно | Параметр code; обмен на токен POST-ом на /token с client_secret. |
T20-L7 0.65 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» Пояснение: A refresh token is designed to have a longer lifespan than an access token and is used to obtain a new access token without requiring the user to authenticate again.
Raw{"answer": "yes", "explanation": "A refresh token is designed to have a longer lifespan than an access token and is used to obtain a new access token without requiring the user to authenticate again."} | верно | Стандартная схема OAuth/OIDC: короткий access + длинный refresh. |
T20-L8 1.42 c | Security and OAuth | A password salt must be kept secret: without it the hash cannot be verified. | «no» Пояснение: A salt is not secret; it is typically stored alongside the hash. Its purpose is to prevent rainbow table attacks by ensuring identical passwords produce different hashes, not to add secrecy.
Raw{"answer": "no", "explanation": "A salt is not secret; it is typically stored alongside the hash. Its purpose is to prevent rainbow table attacks by ensuring identical passwords produce different hashes, not to add secrecy."} | верно | Соль хранится открыто (password_hash включает её в строку хеша); секретность соли не нужна. |
T18-L1 1.69 c | Testing: PHPUnit | PHPUnit runs test methods of any class — extending TestCase is not required. | «no» Пояснение: PHPUnit requires test classes to extend PHPUnit\Framework\TestCase to be recognized and executed.
Raw{"answer": "no", "explanation": "PHPUnit requires test classes to extend PHPUnit\\Framework\\TestCase to be recognized and executed."} | верно | Тестом считается метод класса, наследующего TestCase (PHPUnit 10). |
T18-L2 0.75 c | Testing: PHPUnit | In PHPUnit, setUp() runs once before all tests of the class. | «no» Пояснение: setUp() runs before each test method; setUpBeforeClass() (static) is what runs once before all tests.
Raw{"answer": "no", "explanation": "setUp() runs before each test method; setUpBeforeClass() (static) is what runs once before all tests."} | верно | setUp() — перед КАЖДЫМ тестом; один раз на класс — setUpBeforeClass(). Проверено живым счётчиком на PHPUnit 10.5. |
T18-L3 0.85 c | Testing: PHPUnit | A data provider lets a test run with exactly one set of arguments. | «no» Пояснение: A data provider is specifically designed to let a test run multiple times with different sets of arguments.
Raw{"answer": "no", "explanation": "A data provider is specifically designed to let a test run multiple times with different sets of arguments."} | верно | Наоборот: наборов может быть сколько угодно — тест выполняется по разу на каждый. Проверено на PHPUnit 10.5 (#[DataProvider]). |
T18-L4 0.94 c | Testing: PHPUnit | Which PHPUnit method declares an expectation that an exception of a given class is thrown? | «expectexception» Пояснение: PHPUnit's expectException() method declares that an exception of the specified class is expected to be thrown.
Raw{"answer": "expectException", "explanation": "PHPUnit's expectException() method declares that an exception of the specified class is expected to be thrown."} | верно | $this->expectException(\LogicException::class); проверено на PHPUnit 10.5. |
T18-L5 0.9 c | Testing: PHPUnit | In PHPUnit, a stub verifies which methods were called on it, while a mock only returns data. | «no» Пояснение: The definitions are reversed: a stub returns pre-programmed data, while a mock verifies that expected method calls were made.
Raw{"answer": "no", "explanation": "The definitions are reversed: a stub returns pre-programmed data, while a mock verifies that expected method calls were made."} | верно | Наоборот: стаб подставляет данные, мок проверяет взаимодействия (createStub/createMock); docs PHPUnit — Test Doubles. |
T18-L6 0.89 c | Testing: PHPUnit | In PHPUnit 10+, the recommended way to pass data to a test is the #[DataProvider] attribute (the @dataProvider annotation is deprecated). | «yes» Пояснение: PHPUnit 10 introduced PHP attributes as the replacement for docblock annotations, making #[DataProvider] the recommended way over the deprecated @dataProvider annotation.
Raw{"answer": "yes", "explanation": "PHPUnit 10 introduced PHP attributes as the replacement for docblock annotations, making #[DataProvider] the recommended way over the deprecated @dataProvider annotation."} | верно | Аннотация ещё парсится в PHPUnit 10/11 (AnnotationParser в 10.5.66), удаление — в 12; атрибут — стандарт. |
T18-L7 0.87 c | Testing: PHPUnit | PHPUnit does not allow one test to depend on the result of another. | «no» Пояснение: PHPUnit does allow test dependencies via the @depends annotation or the depends() method, which passes the result of one test as a parameter to another.
Raw{"answer": "no", "explanation": "PHPUnit does allow test dependencies via the @depends annotation or the depends() method, which passes the result of one test as a parameter to another."} | верно | Зависимости есть: #[Depends] — зависимый тест не запустится, еслиProducer упал. |
T18-L8 1.56 c | Testing: PHPUnit | Which PHPUnit command-line option makes tests run in random order? | «--random-order» Пояснение: The --random-order option in PHPUnit causes tests to be executed in a random order.
Raw{"answer": "--random-order", "explanation": "The --random-order option in PHPUnit causes tests to be executed in a random order."} | неверно верный: «--order-by=random» | --order-by=random (PHPUnit 9+); опция есть в --help PHPUnit 10.5 (проектная). |
T01-L9 3.81 c | Syntax and operators | What does this code output?
```php
echo intdiv(7, 2) . intdiv(-7, 2);
``` | «3-3» Пояснение: intdiv(7,2) returns 3 and intdiv(-7,2) returns -3 (truncation toward zero), concatenated as a string gives '3-3'.
Raw{"answer": "3-3", "explanation": "intdiv(7,2) returns 3 and intdiv(-7,2) returns -3 (truncation toward zero), concatenated as a string gives '3-3'."} | верно | intdiv truncates toward zero: intdiv(-7, 2) = -3, not -4. |
T01-L10 0.95 c | Syntax and operators | What does this code output?
```php
echo -3 ** 2;
``` | «-9» Пояснение: In PHP, the ** operator has higher precedence than unary minus, so -3 ** 2 is parsed as -(3**2) = -9.
Raw{"answer": -9, "explanation": "In PHP, the ** operator has higher precedence than unary minus, so -3 ** 2 is parsed as -(3**2) = -9."} | верно | ** is right-associative and binds tighter than unary minus: -(3²). |
T02-L9 4.79 c | Types and comparisons | What does this code output?
```php
echo '1e1' == '10' ? 'true' : 'false';
``` | «false» Пояснение: In PHP 8+, comparing two strings with == performs a string comparison, and '1e1' !== '10' as strings.
Raw```json ⏎ {"answer": "false", "explanation": "In PHP 8+, comparing two strings with == performs a string comparison, and '1e1' !== '10' as strings."} ⏎ ``` | неверно верный: «true» | Both strings are numeric — compared as numbers: 10 == 10. |
T02-L10 2.55 c | Types and comparisons | What does this code output?
```php
switch ('a') {
case 0: echo 'zero'; break;
default: echo 'other';
}
``` | «other» Пояснение: In PHP 8, the loose comparison 'a' == 0 is false (non-numeric string vs integer 0), so the switch falls through to the default case.
Raw```json ⏎ {"answer": "other", "explanation": "In PHP 8, the loose comparison 'a' == 0 is false (non-numeric string vs integer 0), so the switch falls through to the default case."} ⏎ ``` | верно | PHP 8: 'a' == 0 → false (used to be true) — default fires. |
T03-L9 1.33 c | Strings | What does this code output?
```php
echo strtr('abc', ['a' => '1', 'ab' => '2']);
``` | «2c» Пояснение: strtr with an array replaces the longest matching key first, so 'ab' is replaced by '2' before 'a' is considered, yielding '2c'.
Raw{"answer": "2c", "explanation": "strtr with an array replaces the longest matching key first, so 'ab' is replaced by '2' before 'a' is considered, yielding '2c'."} | верно | strtr with an array prefers the longest matching key. |
T03-L10 2.34 c | Strings | What does this code output?
```php
echo '[' . substr('hello', -10) . ']';
``` | «[]» Пояснение: substr('hello', -10) returns an empty string because -10 is beyond the start of the 5-character string, so the result is just the brackets with nothing inside.
Raw{"answer": "[]", "explanation": "substr('hello', -10) returns an empty string because -10 is beyond the start of the 5-character string, so the result is just the brackets with nothing inside."} | неверно верный: «[hello]» | A negative start beyond the string is clamped to the beginning. |
T04-L9 1.57 c | Arrays | What does this code output?
```php
$a = ['k' => 1, 'n' => 2];
$b = ['k' => 9, 'm' => 3];
echo implode(',', array_keys($a + $b));
``` | «k,n,m» Пояснение: The union operator (+) keeps left array's values for duplicate keys and appends right array's new keys, resulting in keys ['k','n','m'].
Raw{"answer": "k,n,m", "explanation": "The union operator (+) keeps left array's values for duplicate keys and appends right array's new keys, resulting in keys ['k','n','m']."} | верно | The + operator: on duplicate string keys the left array wins. |
T04-L10 2.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» Пояснение: The array is sorted by the third element (1, 2, 2), then column index 1 is extracted and concatenated: 'y' + 'x' + 'z' = 'yxz'.
Raw```json ⏎ {"answer": "yxz", "explanation": "The array is sorted by the third element (1, 2, 2), then column index 1 is extracted and concatenated: 'y' + 'x' + 'z' = 'yxz'."} ⏎ ``` | верно | Sorts are stable since 8.0: x and z keep their order on a tie. |
T05-L10 1.32 c | Functions and closures | What does this code output?
```php
function f(int $a, int $b): int
{
return $a - $b;
}
echo f(...['b' => 1, 'a' => 5]);
``` | «4» Пояснение: The spread operator with string keys assigns values by parameter name, so $a=5 and $b=1, giving 5-1=4.
Raw{"answer": 4, "explanation": "The spread operator with string keys assigns values by parameter name, so $a=5 and $b=1, giving 5-1=4."} | верно | String keys of a spread array become named arguments. |
T05-L9 4.9 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 $f holds a reference to object $p, so even after $p is set to null, the object is still alive and g() returns the private property value 3.
Raw```json ⏎ {"answer": 3, "explanation": "The callable $f holds a reference to object $p, so even after $p is set to null, the object is still alive and g() returns the private property value 3."} ⏎ ``` | верно | First-class callable syntax binds $this at creation time. |
T06-L9 0.96 c | OOP: classes and inheritance | What does this code output?
```php
class A
{
public function who(): string { return static::class; }
}
class B extends A {}
echo (new B)->who();
``` | «b» Пояснение: static::class uses late static binding and returns the class of the object instance (B), not the class where the method is defined (A).
Raw{"answer": "B", "explanation": "static::class uses late static binding and returns the class of the object instance (B), not the class where the method is defined (A)."} | верно | Late static binding: static::class is the receiver's class. |
T06-L10 9.59 c | OOP: classes and inheritance | What does this code output on PHP 8.5?
```php
class C
{
public int $x = 0 {
set { $this->x = $value * 2; }
}
}
$c = new C;
$c->x = 5;
echo $c->x;
``` | «10» Пояснение: The set hook is invoked with $value=5, stores 5*2=10 in the backing store (assignments within the hook don't re-trigger it), so echo outputs 10.
Raw```json ⏎ {"answer": 10, "explanation": "The set hook is invoked with $value=5, stores 5*2=10 in the backing store (assignments within the hook don't re-trigger it), so echo outputs 10."} ⏎ ``` | верно | Inside the set hook, $this->x writes the backing store (no recursion): 5*2. |
T07-L9 1.33 c | Interfaces, traits, enum | What does this code output?
```php
trait TA
{
public function f(): string { return 'A'; }
}
trait TB
{
public function f(): string { return 'B'; }
}
class TC
{
use TA, TB { TB::f insteadof TA; TA::f as g; }
}
echo (new TC)->f() . (new TC)->g();
``` | «ba» Пояснение: TB::f insteadof TA makes f() return 'B', and TA::f as g aliases TA's f as g() returning 'A', so the concatenation is 'BA'.
Raw{"answer": "BA", "explanation": "TB::f insteadof TA makes f() return 'B', and TA::f as g aliases TA's f as g() returning 'A', so the concatenation is 'BA'."} | верно | insteadof picks the implementation; as keeps the other under an alias. |
T07-L10 1.43 c | Interfaces, traits, enum | What does this code output?
```php
trait Counter
{
public static int $n = 0;
}
class CX { use Counter; }
class CY { use Counter; }
CX::$n = 1;
echo CY::$n;
``` | «0» Пояснение: Each class using a trait gets its own independent copy of static properties, so CX's modification does not affect CY's $n which remains 0.
Raw{"answer": 0, "explanation": "Each class using a trait gets its own independent copy of static properties, so CX's modification does not affect CY's $n which remains 0."} | верно | A trait's static property is copied into each consuming class. |
T08-L10 0.99 c | Exceptions and errors | What does this code output?
```php
function f(): int
{
try { return 1; } finally { return 2; }
}
echo f();
``` | «2» Пояснение: A return statement in a finally block overrides any return in the try block, so the function returns 2.
Raw```json ⏎ {"answer": 2, "explanation": "A return statement in a finally block overrides any return in the try block, so the function returns 2."} ⏎ ``` | верно | A return in finally overrides the return from try. |
T08-L9 1.23 c | Exceptions and errors | What does this code output?
```php
try {
try {
throw new RuntimeException('first');
} finally {
throw new LogicException('second');
}
} catch (LogicException $e) {
echo $e->getMessage();
}
``` | «second» Пояснение: The finally block throws a LogicException which replaces the original RuntimeException, and the outer catch catches the LogicException and prints its message 'second'.
Raw{"answer": "second", "explanation": "The finally block throws a LogicException which replaces the original RuntimeException, and the outer catch catches the LogicException and prints its message 'second'."} | верно | An exception from finally replaces the in-flight one — the last thrown is caught. |
T09-L9 1.39 c | Namespaces and autoloading | What does this code output?
```php
namespace N;
use App\Foo as Baz;
echo Baz::class . '|' . \Baz::class;
``` | «app\foo|baz» Пояснение: Baz::class resolves via the use alias to App\Foo, while \Baz::class refers to the global namespace class Baz, giving the string 'App\Foo|Baz'.
Raw{"answer": "App\\Foo|Baz", "explanation": "Baz::class resolves via the use alias to App\\Foo, while \\Baz::class refers to the global namespace class Baz, giving the string 'App\\Foo|Baz'."} | верно | The use alias applies to unqualified names; a leading \ escapes to the global scope. |
T09-L10 1.53 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') checks the global namespace (false → 'no'), while class_exists('Ns\Foo') checks the correct namespace (true → 'yes').
Raw{"answer": "noyes", "explanation": "class_exists('Foo') checks the global namespace (false → 'no'), while class_exists('Ns\\Foo') checks the correct namespace (true → 'yes')."} | верно | Dynamic names are not resolved against the namespace — 'Foo' is the global class. |
T10-L9 1.2 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 by reference leaves $v still referencing the last element of $a, so assigning 99 to $v modifies $a[2].
Raw{"answer": "1,2,99", "explanation": "The foreach by reference leaves $v still referencing the last element of $a, so assigning 99 to $v modifies $a[2]."} | верно | After a by-ref foreach, $v remains a reference to the last element. |
T10-L10 1.85 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 (and subclasses that don't override the method), so $n is incremented three times total, and the last call returns 3.
Raw{"answer": 3, "explanation": "Static variables are shared across all instances of the class (and subclasses that don't override the method), so $n is incremented three times total, and the last call returns 3."} | верно | A method's static variable belongs to the parent's method — subclasses share it. |
T11-L9 1.52 c | Generators, iterators, SPL | What does this code output?
```php
function g(): Generator
{
$x = yield 1;
return $x + 1;
}
$g = g();
$g->send(10);
echo $g->getReturn();
``` | «11» Пояснение: send(10) assigns 10 to $x (the result of yield 1), then return $x + 1 returns 11, which getReturn() outputs.
Raw```json ⏎ {"answer": 11, "explanation": "send(10) assigns 10 to $x (the result of yield 1), then return $x + 1 returns 11, which getReturn() outputs."} ⏎ ``` | верно | send() resumes the generator: $x = 10, return 10+1. |
T11-L10 1.64 c | Generators, iterators, SPL | What does this code output?
```php
function inner(): Generator
{
yield 1;
yield 2;
return 'ok';
}
function outer(): Generator
{
$r = yield from inner();
yield $r;
}
echo implode(',', iterator_to_array(outer()));
``` | «1,2,ok» Пояснение: yield from delegates to inner() yielding 1 and 2, captures the return value 'ok' into $r, then yields it, giving [1, 2, 'ok'] which implode joins to '1,2,ok'.
Raw{"answer":"1,2,ok","explanation":"yield from delegates to inner() yielding 1 and 2, captures the return value 'ok' into $r, then yields it, giving [1, 2, 'ok'] which implode joins to '1,2,ok'."} | неверно верный: «ok,2» | yield from does not advance the outer auto-key: yield $r gets key 0 and overwrites the 1 — 'ok' comes out first. |
T12-L9 1.54 c | Configuration and security | What does this code output?
```php
$hash = password_hash('x', PASSWORD_BCRYPT, ['cost' => 4]);
echo password_needs_rehash($hash, PASSWORD_BCRYPT, ['cost' => 4]) ? 'yes' : 'no';
echo password_needs_rehash($hash, PASSWORD_BCRYPT, ['cost' => 5]) ? 'yes' : 'no';
``` | «noyes» Пояснение: The first call returns false because the hash already uses cost 4, and the second returns true because cost 5 differs from the hash's cost of 4.
Raw{"answer": "noyes", "explanation": "The first call returns false because the hash already uses cost 4, and the second returns true because cost 5 differs from the hash's cost of 4."} | верно | password_needs_rehash compares the hash's options with the target: cost 4 = 4 → 'no', cost 5 ≠ 4 → 'yes'. |
T12-L10 3.27 c | Configuration and security | What does this code output on PHP 8.5?
```php
echo (E_ALL & 2048) === 0 ? 'strict-out' : 'strict-in';
``` | «strict-out» Пояснение: In PHP 8.5, E_STRICT (2048) is no longer included in E_ALL, so the bitwise AND yields 0.
Raw{"answer": "strict-out", "explanation": "In PHP 8.5, E_STRICT (2048) is no longer included in E_ALL, so the bitwise AND yields 0."} | верно | 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 3.78 c | Symfony | What does this code output?
```php
use Symfony\Component\HttpFoundation\Request;
$r = Request::create('/demo', 'GET', [], [], [], ['HTTP_X_TOKEN' => 'abc']);
echo $r->headers->get('X-Token') === 'abc' ? 'mapped' : 'missing';
``` | «mapped» Пояснение: Symfony's HeaderBag strips the HTTP_ prefix and normalizes underscores to dashes, so HTTP_X_TOKEN becomes X-TOKEN, and get() is case-insensitive, so 'X-Token' resolves to the stored value 'abc'.
Raw```json ⏎ {"answer": "mapped", "explanation": "Symfony's HeaderBag strips the HTTP_ prefix and normalizes underscores to dashes, so HTTP_X_TOKEN becomes X-TOKEN, and get() is case-insensitive, so 'X-Token' resolves to the stored value '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.16 c | Symfony | What does this code output?
```php
use Symfony\Component\EventDispatcher\EventDispatcher;
use Symfony\Contracts\EventDispatcher\Event;
$d = new EventDispatcher();
$out = '';
$d->addListener('e', function () use (&$out) { $out .= 'B'; }, 10);
$d->addListener('e', function () use (&$out) { $out .= 'A'; });
$d->addListener('e', function () use (&$out) { $out .= 'C'; }, 5);
$d->dispatch(new Event(), 'e');
echo $out;
``` | «bca» Пояснение: Symfony EventDispatcher calls listeners in descending priority order: 10 (B), 5 (C), 0 (A).
Raw{"answer": "BCA", "explanation": "Symfony EventDispatcher calls listeners in descending priority order: 10 (B), 5 (C), 0 (A)."} | верно | Listeners run by descending priority: 10 (B), 5 (C), 0 (A). |
T14-L10 1.95 c | Doctrine | Given: Doctrine ORM 3, an EntityManager on in-memory SQLite, entity User with an auto-increment primary key. The users table is empty. What does this code output?
```php
$u = new User(name: 'A');
$em->persist($u);
$em->flush();
$a = $em->find(User::class, $u->getId());
$b = $em->find(User::class, $u->getId());
echo spl_object_id($a) === spl_object_id($b) ? 'same' : 'diff';
``` | «same» Пояснение: Doctrine ORM's identity map ensures that find() returns the same object instance for an already-managed entity, so both $a and $b are the identical PHP object.
Raw{"answer": "same", "explanation": "Doctrine ORM's identity map ensures that find() returns the same object instance for an already-managed entity, so both $a and $b are the identical PHP object."} | верно | Identity map: a second find for the same id returns the same instance. |
T14-L9 2.77 c | Doctrine | Given: Doctrine ORM 3, an EntityManager on in-memory SQLite, entity User with an auto-increment primary key. The users table is empty. What does this code output?
```php
$u = new User(name: 'B');
$em->persist($u);
$em->remove($u);
$em->flush();
echo count($em->getConnection()->fetchAllAssociative('SELECT * FROM users'));
``` | «0» Пояснение: When an entity is persisted and then removed before flush, the UnitOfWork cancels the pending INSERT entirely, so no row is ever written to the database.
Raw{"answer": 0, "explanation": "When an entity is persisted and then removed before flush, the UnitOfWork cancels the pending INSERT entirely, so no row is ever written to the database."} | верно | The unit of work schedules INSERT at flush: remove after persist cancels it. |
T15-L10 1.1 c | PostgreSQL | What does this SQL query return (PostgreSQL 17)?
```sql
CREATE TEMP TABLE t (x int);
INSERT INTO t VALUES (1), (NULL);
SELECT count(x) FROM t;
``` | «1» Пояснение: COUNT(x) counts only non-NULL values in column x, so it returns 1 (the NULL row is excluded).
Raw{"answer": 1, "explanation": "COUNT(x) counts only non-NULL values in column x, so it returns 1 (the NULL row is excluded)."} | верно | count(column) skips NULLs; count(*) would return 2. |
T15-L9 1.45 c | PostgreSQL | What does this SQL query return (PostgreSQL 17)?
```sql
CREATE TEMP TABLE t (id int, x int);
INSERT INTO t VALUES (1, 10), (2, 20), (3, 30);
SELECT string_agg(s::text, ',' ORDER BY id) FROM (
SELECT id, sum(x) OVER (ORDER BY id) AS s FROM t
) q;
``` | «10,30,60» Пояснение: The window function computes a running sum (10, 30, 60) and string_agg concatenates them in id order.
Raw```json ⏎ {"answer": "10,30,60", "explanation": "The window function computes a running sum (10, 30, 60) and string_agg concatenates them in id order."} ⏎ ``` | верно | With ORDER BY the default window frame is running (start to current row). |
T16-L9 11.19 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 executes in order: M1 echoes 'M1' and delegates to M2, which echoes 'M2' and delegates to the terminal handler; the output is the concatenation of both tags.
Raw```json ⏎ {"answer": "M1M2", "explanation": "The middleware stack executes in order: M1 echoes 'M1' and delegates to M2, which echoes 'M2' and delegates to the terminal handler; the output is the concatenation of both tags."} ⏎ ``` | верно | The first-added middleware runs first (outermost). |
T16-L10 2.07 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» Пояснение: Both handlers are called sequentially: $n increments by 1 then by 10, resulting in 11.
Raw```json ⏎ {"answer": 11, "explanation": "Both handlers are called sequentially: $n increments by 1 then by 10, resulting in 11."} ⏎ ``` | верно | All registered handlers of the message run: 1 + 10 = 11. |
T17-L9 1.34 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 adds a row, the second INSERT hits the unique index conflict and does nothing, so count(*) returns 1.
Raw{"answer": 1, "explanation": "The first INSERT adds a row, the second INSERT hits the unique index conflict and does nothing, so count(*) returns 1."} | верно | ON CONFLICT DO NOTHING skips the duplicate: one insert. |
T17-L10 1.8 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 uniqueness is only checked at COMMIT time, allowing both duplicate inserts to succeed within the transaction.
Raw{"answer": 2, "explanation": "The UNIQUE constraint is DEFERRABLE INITIALLY DEFERRED, so uniqueness is only checked at COMMIT time, allowing both duplicate inserts to succeed within the transaction."} | верно | DEFERRED postpones the uniqueness check to COMMIT — count sees 2 rows. |
T18-L9 1.85 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 regex matches both test_sum (3 data set entries) and test_sum_abs (3 data set entries), totaling 6 tests.
Raw```json ⏎ {"answer": 6, "explanation": "The --filter test_sum regex matches both test_sum (3 data set entries) and test_sum_abs (3 data set entries), totaling 6 tests."} ⏎ ``` | верно | --filter is a substring match: test_sum also matches test_sum_abs (3+3 datasets). |
T18-L10 1.28 c | Testing: PHPUnit | How many tests will this command run, and how many of them will fail? Answer with two comma-separated numbers (ran, failed).
```php
use PHPUnit\Framework\TestCase;
use PHPUnit\Framework\Attributes\DataProvider;
final class Calc2Test extends TestCase
{
public function prov(): array
{
return [[1], [-1]];
}
#[DataProvider('prov')]
public function test_x(int $x): void
{
$this->assertTrue($x > 0);
}
}
```
Command: `phpunit Calc2Test.php` (PHPUnit 10.5) | «2,1» Пояснение: The data provider supplies two datasets ([1] and [-1]); test_x(1) passes (1>0 is true) and test_x(-1) fails (-1>0 is false).
Raw{"answer":"2,1","explanation":"The data provider supplies two datasets ([1] and [-1]); test_x(1) passes (1>0 is true) and test_x(-1) fails (-1>0 is false)."} | верно | A non-static provider is just a deprecation in PHPUnit 10: both datasets run and the [-1] dataset fails the assert — 2 ran, 1 failure. |
T19-L9 0.75 c | HTTP and REST API | Which HTTP method does this command send?
```bash
curl -s -d 'a=1' http://demo.local/api
``` | «post» Пояснение: The -d flag in curl sends data in the request body and automatically sets the HTTP method to POST.
Raw{"answer": "POST", "explanation": "The -d flag in curl sends data in the request body and automatically sets the HTTP method to POST."} | верно | -d/-F switches curl to POST by default. |
T19-L10 1.2 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 combined with -d tells curl to send the data as a query string using the GET method instead of the default POST.
Raw{"answer": "GET", "explanation": "The -G flag combined with -d tells curl to send the data as a query string using the GET method instead of the default POST."} | верно | -G turns -d data into the query string; the method stays GET. |
T20-L9 1.4 c | Security and OAuth | A client hits the token endpoint (RFC 6749) with a non-existent client_id. What value of the error field does the endpoint return? | «invalid_client» Пояснение: RFC 6749 Section 5.2 defines 'invalid_client' as the error returned when the client does not exist or cannot be authenticated.
Raw{"answer": "invalid_client", "explanation": "RFC 6749 Section 5.2 defines 'invalid_client' as the error returned when the client does not exist or cannot be authenticated."} | верно | Unknown client → invalid_client (RFC 6749 §5.2). |
T20-L10 1.03 c | Security and OAuth | OAuth 2.0: the client started the flow with response_type=token. In which part of the redirect_uri does the authorization server pass the access_token? | «fragment» Пояснение: In the OAuth 2.0 implicit flow (response_type=token), the access token is returned in the URI fragment (after #) of the redirect_uri, not in the query string.
Raw{"answer": "fragment", "explanation": "In the OAuth 2.0 implicit flow (response_type=token), the access token is returned in the URI fragment (after #) of the redirect_uri, not in the query string."} | верно | The implicit flow passes the token in the URL fragment (#) — it never reaches the server. |
T21-L9 2.21 c | Twig | What does this Twig template output?
```twig
{{ false|default(2) * 3 }}
``` | «0» Пояснение: The default filter only triggers on null/undefined values, so false passes through unchanged, and false * 3 evaluates to 0 in PHP.
Raw```json ⏎ {"answer": 0, "explanation": "The default filter only triggers on null/undefined values, so false passes through unchanged, and false * 3 evaluates to 0 in PHP."} ⏎ ``` | неверно верный: «6» | default replaces exactly false/null/''/[] — false becomes 2, 2*3 = 6; the naive 'default is for undefined only' yields 0. |
T21-L10 1.83 c | Twig | What exception class does render() of this template throw?
```twig
{{ 'a' ~ 1 + 2 }}
``` | «a3» Пояснение: In Twig, the + operator has higher precedence than ~, so it parses as 'a' ~ (1+2) = 'a' ~ 3 = 'a3'.
Raw{"answer": "a3", "explanation": "In Twig, the + operator has higher precedence than ~, so it parses as 'a' ~ (1+2) = 'a' ~ 3 = 'a3'."} | неверно верный: «runtimeerror» | In Twig ~ binds tighter than +: ('a' ~ 1) + 2 → string + int → a render error (RuntimeError). |
T22-L9 2.79 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 [''] has count 1, so it is not blank; the NotBlank constraint passes, resulting in 0 violations.
Raw{"answer": 0, "explanation": "The array [''] has count 1, so it is not blank; the NotBlank constraint passes, resulting in 0 violations."} | верно | NotBlank treats null, '', [] as blank — the array [''] is not blank. |
T22-L10 4.81 c | Symfony: Security and forms | What does this code output?
```php
use Symfony\Component\Form\Forms;
use Symfony\Component\Form\Extension\Core\Type\TextType;
$factory = Forms::createFormFactoryBuilder()->getFormFactory();
$form = $factory->create(TextType::class);
try {
echo $form->isValid() ? 'valid' : 'invalid';
} catch (Throwable $e) {
echo get_class($e);
}
``` | «invalid» Пояснение: A TextType form defaults to required=true, so an unsubmitted (empty) form has a validation error, making isValid() return false.
Raw```json ⏎ {"answer": "invalid", "explanation": "A TextType form defaults to required=true, so an unsubmitted (empty) form has a validation error, making isValid() return false."} ⏎ ``` | неверно верный: «symfony\component\form\exception\logicexception» | isValid() on a non-submitted form throws LogicException, it does not return false. |
T23-L9 1.47 c | Symfony: configuration and services | What does this code output?
```php
use Symfony\Component\DependencyInjection\ContainerBuilder;
$c = new ContainerBuilder();
$c->register('a', stdClass::class)->setPublic(true);
$c->compile();
echo spl_object_id($c->get('a')) === spl_object_id($c->get('a')) ? 'same' : 'diff';
``` | «same» Пояснение: Symfony's DI container caches service instances after compilation, so repeated get() calls return the same object.
Raw```json ⏎ {"answer": "same", "explanation": "Symfony's DI container caches service instances after compilation, so repeated get() calls return the same object."} ⏎ ``` | верно | Container services are shared: two get() calls yield one instance. |
T23-L10 1.27 c | Symfony: configuration and services | What does this code output?
```php
use Symfony\Component\DependencyInjection\ContainerBuilder;
$c = new ContainerBuilder();
$c->setParameter('name', 'Bob');
$c->setParameter('greeting', 'hi %name%');
$c->setParameter('message', '%greeting%!');
$c->compile();
echo $c->getParameter('message');
``` | «hi bob!» Пояснение: During compile(), Symfony resolves parameter references recursively: %name% becomes 'Bob', %greeting% becomes 'hi Bob', and %greeting%! becomes 'hi Bob!'.
Raw{"answer": "hi Bob!", "explanation": "During compile(), Symfony resolves parameter references recursively: %name% becomes 'Bob', %greeting% becomes 'hi Bob', and %greeting%! becomes 'hi Bob!'."} | верно | compile() resolves %-references transitively: %greeting% → 'hi %name%' → 'hi Bob!', the answer assembles over two hops. |
T24-L9 1.14 c | Bootstrap | What is the max-width of .container in Bootstrap 5.3 at a 992px viewport? | «960» Пояснение: In Bootstrap 5.3, at the lg breakpoint (≥992px), the .container has a max-width of 960px.
Raw{"answer": 960, "explanation": "In Bootstrap 5.3, at the lg breakpoint (≥992px), the .container has a max-width of 960px."} | верно | 5.x container widths: 540/720/960/1140/1320 (sm–xxl); 992 → 960px. |
T24-L10 8.26 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» Пояснение: Both classes have the same specificity, so the one appearing later in the compiled Bootstrap CSS wins; .text-danger is defined after .text-primary in the utility order.
Raw```json ⏎ {"answer": "text-danger", "explanation": "Both classes have the same specificity, so the one appearing later in the compiled Bootstrap CSS wins; .text-danger is defined after .text-primary in the utility order."} ⏎ ``` | верно | Specificity ties — the later rule wins: text-danger is declared after text-primary. |
T25-L9 1.12 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; using Application\PlaceOrder and Infrastructure\Db are both violations.
Raw{"answer": 2, "explanation": "The class is in the Domain layer, which may only depend on Domain; using Application\\PlaceOrder and Infrastructure\\Db are both violations."} | верно | Domain may depend only on Domain: PlaceOrder (Application) + Db (Infrastructure) = 2. |
T25-L10 1.57 c | Clean architecture | Layers: Domain, Application, Infrastructure. Deptrac rules: Application → Domain; Infrastructure → Domain, Application; Domain → Domain only.
How many violations will deptrac report for this class?
```php
namespace App\Domain;
use App\Application\PlaceOrder;
use App\Infrastructure\Db;
class BillingService
{
public function __construct(
private PlaceOrder $handler,
private Db $db,
private \App\Infrastructure\Logger $logger,
) {}
}
``` | «3» Пояснение: The Domain-layer class BillingService depends on Application (PlaceOrder) and Infrastructure (Db, Logger), which are all three violations since Domain may only depend on Domain.
Raw```json ⏎ {"answer": 3, "explanation": "The Domain-layer class BillingService depends on Application (PlaceOrder) and Infrastructure (Db, Logger), which are all three violations since Domain may only depend on Domain."} ⏎ ``` | верно | The inline FQCN \App\Infrastructure\Logger counts too: Application + Db + Logger = 3. |
T26-L10 1.23 c | DDD | What does this code output?
```php
final class Money
{
public function __construct(public readonly int $amount) {}
public function add(Money $o): Money
{
return new self($this->amount + $o->amount);
}
}
$a = new Money(10);
$c = $a->add(new Money(5));
echo $a->amount . ',' . $c->amount;
``` | «10,15» Пояснение: $a has amount 10, and $c is a new Money object with 10+5=15, so the output is '10,15'.
Raw{"answer": "10,15", "explanation": "$a has amount 10, and $c is a new Money object with 10+5=15, so the output is '10,15'."} | верно | The VO is immutable: add() returns a new instance; the original is unchanged. |
T26-L9 1.43 c | DDD | What does this code output?
```php
final class Order
{
private array $items = [];
public function add(string $sku): void
{
$this->items[$sku] = true;
}
public function count(): int
{
return count($this->items);
}
public function remove(string $sku): void
{
if (count($this->items) === 1) {
throw new DomainException('last item');
}
unset($this->items[$sku]);
}
}
$o = new Order;
$o->add('a');
try {
$o->remove('a');
} catch (DomainException) {
}
echo $o->count();
``` | «1» Пояснение: The remove() method throws DomainException before unset() is reached because count is 1, so the item is never removed and count() still returns 1.
Raw{"answer": 1, "explanation": "The remove() method throws DomainException before unset() is reached because count is 1, so the item is never removed and count() still returns 1."} | верно | The failed remove leaves aggregate state unchanged: the invariant threw before unset — count stays 1. |
VC-L9 0.73 c | PHP 8.4–8.5 | What does this code output on PHP 8.5?
```php
class C
{
public function hi(): string { return 'hi'; }
}
echo new C()->hi();
``` | «hi» Пояснение: The code instantiates class C and calls hi() which returns the string 'hi', which is then echoed.
Raw{"answer": "hi", "explanation": "The code instantiates class C and calls hi() which returns the string 'hi', which is then echoed."} | верно | Since 8.4, new in a method chain works without wrapping parentheses. |
VC-L10 1.55 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» Пояснение: Before property access the lazy ghost is uninitialized (yes), and after accessing $o->v the callback runs and the object becomes initialized (no).
Raw{"answer": "yesno", "explanation": "Before property access the lazy ghost is uninitialized (yes), and after accessing $o->v the callback runs and the object becomes initialized (no)."} | верно | newLazyGhost (8.4): the object stays lazy until first access — reading a property initializes it and clears the flag. |
T28-L9 1.22 c | Symfony: versions | The project was upgraded from Symfony 6.4 to 8.1. What does this code output on 8.1?
```php
echo class_exists(\Symfony\Component\Security\Guard\AbstractGuardAuthenticator::class)
? 'yes' : 'no';
``` | «no» Пояснение: The Guard authentication system, including AbstractGuardAuthenticator, was removed in Symfony 6.0, so it does not exist in Symfony 8.1.
Raw```json ⏎ {"answer": "no", "explanation": "The Guard authentication system, including AbstractGuardAuthenticator, was removed in Symfony 6.0, so it does not exist in Symfony 8.1."} ⏎ ``` | верно | Guard authentication was removed in Symfony 7.0 — the class is gone in 8.1. |
T28-L10 2.36 c | Symfony: versions | The project was upgraded from Symfony 6.4 to 8.1. What does this code output on 8.1?
```php
echo class_exists(\Symfony\Component\Routing\Loader\AnnotationClassLoader::class)
? 'yes' : 'no';
echo class_exists(\Symfony\Component\Routing\Loader\AttributeClassLoader::class)
? 'yes' : 'no';
``` | «noyes» Пояснение: AnnotationClassLoader was removed in Symfony 7.0 (replaced by AttributeClassLoader), so on 8.1 it no longer exists (no), while AttributeClassLoader does exist (yes), concatenating to 'noyes'.
Raw{"answer": "noyes", "explanation": "AnnotationClassLoader was removed in Symfony 7.0 (replaced by AttributeClassLoader), so on 8.1 it no longer exists (no), while AttributeClassLoader does exist (yes), concatenating to 'noyes'."} | верно | Annotation loaders were removed in 7.0; only attribute loaders remain (Annotation→Attribute). |