Пример запроса (первая клетка). System одинаковый во всех запросах прогона, user — свой вопрос для каждой клетки:
| Клетка | Тема | Утверждение | Ответ |
Результат | Обоснование |
T01-L1 4.11 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 only interpret \\ and \', so they are processed differently, not just at different speeds.
Raw{"answer": "no", "explanation": "Double-quoted strings support variable interpolation and more escape sequences (e.g., \\n, \\t), while single-quoted strings only interpret \\\\ and \\', so they are processed differently, not just at different speeds."} | верно | В двойных кавычках работают интерполяция переменных и escape-последовательности, в одинарных — нет. |
T01-L2 1.14 c | Syntax and operators | The ?? operator follows isset semantics and raises no warnings for undefined variables. | «yes» Пояснение: The ?? operator is equivalent to isset($a) ? $a : $b, so it checks with isset semantics and does not raise warnings for undefined variables.
Raw{"answer": "yes", "explanation": "The ?? operator is equivalent to isset($a) ? $a : $b, so it checks with isset semantics and does not raise warnings for undefined variables."} | верно | ?? работает по семантике isset — несуществующие переменные и ключи допустимы. |
T01-L3 0.62 c | Syntax and operators | What will this print: echo 'a', 'b'; | «ab» Пояснение: echo with multiple comma-separated arguments concatenates and outputs them in order, producing 'ab'.
Raw{"answer": "ab", "explanation": "echo with multiple comma-separated arguments concatenates and outputs them in order, producing 'ab'."} | верно | echo принимает список аргументов: ab. |
T01-L4 2.6 c | Syntax and operators | print returns the value 1 and can be used inside an expression. | «yes» Пояснение: In PHP, print is a language construct that always returns the integer 1, which allows it to be used inside expressions (unlike echo, which returns nothing).
Raw{"answer": "yes", "explanation": "In PHP, print is a language construct that always returns the integer 1, which allows it to be used inside expressions (unlike echo, which returns nothing)."} | верно | print — выражение со значением 1, в отличие от echo, который значения не возвращает. |
T01-L5 1.01 c | Syntax and operators | The ?: (elvis) operator returns its left operand when it is falsy. | «no» Пояснение: The Elvis operator (?:) returns its left operand when it is truthy, and the right operand when the left is falsy.
Raw{"answer":"no","explanation":"The Elvis operator (?:) returns its left operand when it is truthy, and the right operand when the left is falsy."} | верно | Наоборот: $a ?: $b возвращает $a, если он истинный, иначе $b. |
T01-L6 1.76 c | Syntax and operators | In PHP 8, the concatenation operator (.) has lower precedence than addition and subtraction. | «yes» Пояснение: In PHP's operator precedence, concatenation (.) ranks below addition/subtraction (+, -), so '1 + 2 . 3 + 4' evaluates as '(1+2) . (3+4)' = '37'.
Raw{"answer": "yes", "explanation": "In PHP's operator precedence, concatenation (.) ranks below addition/subtraction (+, -), so '1 + 2 . 3 + 4' evaluates as '(1+2) . (3+4)' = '37'."} | верно | С PHP 8 (RFC concat precedence) '.' имеет приоритет ниже арифметики: 'сумма: ' . 2 + 3 → 'сумма: 5' (в PHP 7 было иначе). |
T01-L7 0.91 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 is evaluated as 2 ** (3 ** 2) = 2 ** 9 = 512, not 64.
Raw{"answer":"no","explanation":"The ** operator in PHP is right-associative, so 2 ** 3 ** 2 is evaluated as 2 ** (3 ** 2) = 2 ** 9 = 512, not 64."} | верно | ** право-ассоциативен: 2 ** (3 ** 2) = 2 ** 9 = 512. |
T01-L8 3.62 c | Syntax and operators | What string will this print: echo 'sum: ' . 2 + 3; (PHP 8)? | «3» Пояснение: Concatenation and addition have the same precedence and are left-associative, so it evaluates as ('sum: ' . 2) + 3 = 'sum: 2' + 3, where the non-numeric string is converted to 0, yielding 0 + 3 = 3.
Raw```json ⏎ {"answer": 3, "explanation": "Concatenation and addition have the same precedence and are left-associative, so it evaluates as ('sum: ' . 2) + 3 = 'sum: 2' + 3, where the non-numeric string is converted to 0, yielding 0 + 3 = 3."} ⏎ ``` | неверно верный: «sum: 5» | Парная к verify-клетке про приоритет: 'сумма: 5'. |
T02-L1 1.11 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; only == ignores order.
Raw{"answer": "no", "explanation": "With ===, arrays must have the same key/value pairs in the same order; only == ignores order."} | верно | === для массивов требует совпадения и значений, и их порядка. |
T02-L2 1.47 c | Types and comparisons | The comparison 0 == false returns false because it is a strict comparison. | «no» Пояснение: 0 == false actually returns true, and == is a loose (not strict) comparison; false is cast to 0, making 0 == 0 true.
Raw{"answer":"no","explanation":"0 == false actually returns true, and == is a loose (not strict) comparison; false is cast to 0, making 0 == 0 true."} | верно | Наоборот: == — нестрогое сравнение и возвращает true; строгое — это === (0 === false → false). |
T02-L3 1.46 c | Types and comparisons | In PHP 8, the expression "abc" == 0 returns true. | «no» Пояснение: In PHP 8, when comparing a non-numeric string to an integer, the integer is cast to a string instead, so 'abc' == 0 becomes 'abc' == '0', which is false.
Raw{"answer": "no", "explanation": "In PHP 8, when comparing a non-numeric string to an integer, the integer is cast to a string instead, so 'abc' == 0 becomes 'abc' == '0', which is false."} | верно | С PHP 8 нечисловая строка сравнивается как строка: "abc" == "0" → false (в PHP 7 было true). |
T02-L4 1.58 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 1.12 c | Types and comparisons | What does the expression (int) '42abc' return? | «42» Пояснение: In PHP, casting a string to int with (int) parses the leading numeric portion and ignores trailing non-numeric characters, so '42abc' becomes 42.
Raw{"answer": 42, "explanation": "In PHP, casting a string to int with (int) parses the leading numeric portion and ignores trailing non-numeric characters, so '42abc' becomes 42."} | верно | Ведущая числовая часть: 42, без ошибок и warning. |
T02-L6 0.83 c | Types and comparisons | What does the expression '5' + 5 return? | «10» Пояснение: In PHP, the + operator with a numeric string and an integer performs arithmetic addition, converting '5' to the integer 5, so 5 + 5 = 10.
Raw{"answer": 10, "explanation": "In PHP, the + operator with a numeric string and an integer performs arithmetic addition, converting '5' to the integer 5, so 5 + 5 = 10."} | верно | Числовая строка приводится: int 10. |
T02-L7 0.93 c | Types and comparisons | When cast to string, false becomes "0". | «no» Пояснение: In PHP, casting false to a string results in an empty string (""), not "0".
Raw{"answer": "no", "explanation": "In PHP, casting false to a string results in an empty string (\"\"), not \"0\"."} | верно | false → "", true → "1". |
T02-L8 1.4 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 yields 0.30000000000000004, which is not strictly equal to 0.3.
Raw{"answer": "yes", "explanation": "Due to IEEE 754 floating-point precision, 0.1 + 0.2 yields 0.30000000000000004, which is not strictly equal to 0.3."} | верно | Двоичная погрешность float: 0.1 + 0.2 = 0.30000000000000004. |
T03-L1 1.27 c | Strings | strrev() correctly reverses a UTF-8 string. | «no» Пояснение: strrev() reverses bytes, not characters, so multi-byte UTF-8 characters get broken and reordered incorrectly.
Raw{"answer": "no", "explanation": "strrev() reverses bytes, not characters, so multi-byte UTF-8 characters get broken and reordered incorrectly."} | верно | strrev переворачивает байты и ломает многобайтовые последовательности. |
T03-L2 0.63 c | Strings | str_contains('Hello world', 'world') returns true. | «yes» Пояснение: str_contains() checks if the needle 'world' exists in the haystack 'Hello world', which it does, so it returns true.
Raw{"answer": "yes", "explanation": "str_contains() checks if the needle 'world' exists in the haystack 'Hello world', which it does, so it returns true."} | верно | str_contains с PHP 8.0 проверяет вхождение подстроки. |
T03-L3 0.77 c | Strings | str_pad() can pad a string on the right side only. | «no» Пояснение: str_pad() supports right, left, and both-side padding via the pad_type parameter (STR_PAD_RIGHT, STR_PAD_LEFT, STR_PAD_BOTH).
Raw{"answer": "no", "explanation": "str_pad() supports right, left, and both-side padding via the pad_type parameter (STR_PAD_RIGHT, STR_PAD_LEFT, STR_PAD_BOTH)."} | верно | STR_PAD_LEFT / STR_PAD_BOTH меняют сторону дополнения. |
T03-L4 1.09 c | Strings | By default trim() strips only spaces, leaving tabs and newlines intact. | «no» Пояснение: By default, trim() strips spaces, tabs, newlines, carriage returns, null bytes, and vertical tabs (" \t\n\r\0\x0B").
Raw{"answer": "no", "explanation": "By default, trim() strips spaces, tabs, newlines, carriage returns, null bytes, and vertical tabs (\" \\t\\n\\r\\0\\x0B\")."} | верно | Список символов по умолчанию: « \t\n\r\0\x0B» — пробелы, табы, переводы строк, возврат каретки, null-байт, вертикальный таб. Проверено php -r. |
T03-L5 1.05 c | Strings | How many BYTES does strlen('héllo') return for a UTF-8 string? | «6» Пояснение: In UTF-8, 'é' is encoded as 2 bytes (0xC3 0xA9), so the string 'héllo' is 1+2+1+1+1 = 6 bytes.
Raw{"answer": 6, "explanation": "In UTF-8, 'é' is encoded as 2 bytes (0xC3 0xA9), so the string 'héllo' is 1+2+1+1+1 = 6 bytes."} | верно | 6 букв по 2 байта: 12. |
T03-L6 0.93 c | Strings | What does substr('abcdef', -3) return? | «def» Пояснение: substr with a negative start position counts from the end of the string, so -3 starts at the 4th character 'd' and returns 'def'.
Raw{"answer": "def", "explanation": "substr with a negative start position counts from the end of the string, so -3 starts at the 4th character 'd' and returns 'def'."} | верно | Отрицательное смещение — с конца: def. |
T03-L7 0.91 c | Strings | ucfirst() modifies the string passed to it in place. | «no» Пояснение: ucfirst() returns a new string with the first character uppercased; it does not modify the original string in place.
Raw{"answer": "no", "explanation": "ucfirst() returns a new string with the first character uppercased; it does not modify the original string in place."} | верно | Строки неизменяемы; ucfirst возвращает новую строку. |
T03-L8 1.0 c | Strings | Variable interpolation works in heredoc but not in nowdoc. | «yes» Пояснение: Heredoc supports variable interpolation like double-quoted strings, while nowdoc (with single-quoted delimiter) does not, similar to single-quoted strings.
Raw{"answer": "yes", "explanation": "Heredoc supports variable interpolation like double-quoted strings, while nowdoc (with single-quoted delimiter) does not, similar to single-quoted strings."} | верно | Nowdoc — «одинарные кавычки» в тройном синтаксисе: текст как есть. |
T04-L1 1.02 c | Arrays | The sort() function preserves the key-to-value association of the array. | «no» Пояснение: sort() reindexes the array; asort() is the function that preserves key-to-value associations.
Raw{"answer": "no", "explanation": "sort() reindexes the array; asort() is the function that preserves key-to-value associations."} | верно | sort перенумеровывает ключи; связь сохраняет asort. |
T04-L2 1.04 c | Arrays | The string key '5' in an array is stored as the integer 5. | «yes» Пояснение: PHP automatically casts string keys that represent valid integers (like '5') to integer keys.
Raw{"answer": "yes", "explanation": "PHP automatically casts string keys that represent valid integers (like '5') to integer keys."} | верно | Каноничные десятичные строковые ключи приводятся к int. |
T04-L3 0.73 c | Arrays | The in_array() function uses strict comparison (===) by default. | «no» Пояснение: The strict parameter of in_array() defaults to false, meaning it uses loose comparison (==) by default.
Raw{"answer": "no", "explanation": "The strict parameter of in_array() defaults to false, meaning it uses loose comparison (==) by default."} | верно | По умолчанию сравнение нестрогое; строгое — третий аргумент true. |
T04-L4 1.1 c | Arrays | Without a callback, array_filter() removes all "empty" (falsy) elements from the array. | «yes» Пояснение: Without a callback, array_filter() removes elements that evaluate to false (0, '0', '', null, false, []), i.e. all falsy/empty values.
Raw{"answer": "yes", "explanation": "Without a callback, array_filter() removes elements that evaluate to false (0, '0', '', null, false, []), i.e. all falsy/empty values."} | верно | Убирает 0, "", null, false и пустые массивы. |
T04-L5 1.07 c | Arrays | By default, array_slice() preserves the original numeric keys of the array. | «no» Пояснение: The $preserve_keys parameter of array_slice() defaults to false, so by default it reindexes the array with new numeric keys starting from 0.
Raw{"answer": "no", "explanation": "The $preserve_keys parameter of array_slice() defaults to false, so by default it reindexes the array with new numeric keys starting from 0."} | верно | По умолчанию ключи перенумеровываются; сохранение — preserve_keys = true. |
T04-L6 1.11 c | Arrays | What does array_slice([10, 20, 30, 40], 1, 2) return? | «{"answer": [20, 30], "explanation": "array_slice with offset 1 and length 2 returns the second and third elements of the array."}» Пояснение: {"answer": [20, 30], "explanation": "array_slice with offset 1 and length 2 returns the second and third elements of the array."}
Raw{"answer": [20, 30], "explanation": "array_slice with offset 1 and length 2 returns the second and third elements of the array."} | верно парсинг: текст (фолбэк) | [20,30]; ключи перенумеровываются. |
T04-L7 1.3 c | Arrays | How many elements will count(['a' => 1] + ['a' => 9, 'b' => 2]) return? | «2» Пояснение: Array union keeps the left array's value for duplicate keys, so 'a'=>1 is retained and 'b'=>2 is added, giving 2 elements.
Raw{"answer": 2, "explanation": "Array union keeps the left array's value for duplicate keys, so 'a'=>1 is retained and 'b'=>2 is added, giving 2 elements."} | верно | Оператор + : по ключу 'a' побеждает левый; итого 2. |
T04-L8 3.18 c | Arrays | Since PHP 8.1, the spread operator [...$a, ...$b] supports arrays with string keys. | «yes» Пояснение: PHP 8.1 officially added support for string keys when using the spread operator in array literals, removing the previous deprecation notice.
Raw{"answer": "yes", "explanation": "PHP 8.1 officially added support for string keys when using the spread operator in array literals, removing the previous deprecation notice."} | верно | В 8.0 — только числовые ключи; 8.1 снял ограничение. |
T05-L1 1.8 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 (e.g., foo(a: 1, ...$args)).
Raw{"answer": "no", "explanation": "In PHP 8.0+, named arguments can be combined with argument unpacking (e.g., foo(a: 1, ...$args))."} | верно | Можно: f(...$args, имя: значение). Нельзя только позиционный аргумент после распаковки. |
T05-L2 1.42 c | Functions and closures | An anonymous function without use sees variables from the outer scope. | «no» Пояснение: In PHP, anonymous functions (closures) do not have access to outer scope variables unless explicitly imported with the 'use' keyword.
Raw{"answer": "no", "explanation": "In PHP, anonymous functions (closures) do not have access to outer scope variables unless explicitly imported with the 'use' keyword."} | верно | Без use внешние переменные недоступны; авто-захват только у fn. |
T05-L3 0.81 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 (3), not the number of declared parameters.
Raw{"answer": 3, "explanation": "func_num_args() returns the number of arguments actually passed to the function (3), not the number of declared parameters."} | верно | Считает переданные аргументы: 3. |
T05-L4 1.45 c | Functions and closures | The body of an arrow function fn may consist of several expressions in curly braces. | «no» Пояснение: Arrow functions (fn) in PHP have a single expression as their body using the => arrow, not a block of multiple statements in curly braces.
Raw{"answer": "no", "explanation": "Arrow functions (fn) in PHP have a single expression as their body using the => arrow, not a block of multiple statements in curly braces."} | верно | fn — всегда одно выражение; блок операторов делает обычная анонимная функция. |
T05-L5 1.41 c | Functions and closures | An arrow function fn captures outer variables by reference (lazily, at use time). | «no» Пояснение: Arrow functions (fn) in PHP capture outer variables by value at the time of creation, not by reference or lazily at use time.
Raw{"answer": "no", "explanation": "Arrow functions (fn) in PHP capture outer variables by value at the time of creation, not by reference or lazily at use time."} | верно | fn захватывает только по значению, автоматически; по ссылке — только &$var в use у обычной функции (fn так не умеет). |
T05-L6 0.83 c | Functions and closures | A closure declared as static function () {} does not capture $this. | «yes» Пояснение: In PHP, a static closure does not automatically capture $this from the enclosing scope, unlike a non-static closure which does.
Raw{"answer": "yes", "explanation": "In PHP, a static closure does not automatically capture $this from the enclosing scope, unlike a non-static closure which does."} | верно | static-замыкание отвязано от объекта: $this внутри недоступен. |
T05-L7 1.18 c | Functions and closures | What will this print: $x = 5; $f = function () use ($x) { return $x; }; $x = 7; echo $f(); | «5» Пояснение: The use() clause captures the variable by value (not by reference) at the time the closure is defined, so it retains the value 5 even after $x is reassigned to 7.
Raw{"answer": 5, "explanation": "The use() clause captures the variable by value (not by reference) at the time the closure is defined, so it retains the value 5 even after $x is reassigned to 7."} | верно | use захватывает по значению в момент создания: 5. |
T05-L8 1.03 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 (the default), PHP coerces numeric strings like '5' to int when passed to an int-typed parameter.
Raw{"answer": "yes", "explanation": "In weak typing mode (the default), PHP coerces numeric strings like '5' to int when passed to an int-typed parameter."} | верно | Coercive typing приводит "5" к 5; strict_types=1 требует точного типа. |
T06-L1 0.78 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 with visibility modifiers.
Raw{"answer": "yes", "explanation": "Constructor property promotion was introduced in PHP 8.0, allowing properties to be declared directly in constructor parameters with visibility modifiers."} | верно | С PHP 8.0 параметр с модификатором создаёт свойство и присваивание. |
T06-L2 0.56 c | OOP: classes and inheritance | Which keyword prevents a method from being overridden in subclasses? | «final» Пояснение: The 'final' keyword in PHP prevents a method from being overridden in subclasses.
Raw{"answer": "final", "explanation": "The 'final' keyword in PHP prevents a method from being overridden in subclasses."} | верно | final. |
T06-L3 0.74 c | OOP: classes and inheritance | A method declared final cannot be overridden in a subclass. | «yes» Пояснение: In PHP, declaring a method as final prevents any subclass from overriding it, and attempting to do so will result in a fatal error.
Raw{"answer": "yes", "explanation": "In PHP, declaring a method as final prevents any subclass from overriding it, and attempting to do so will result in a fatal error."} | верно | final запрещает переопределение метода и наследование класса. |
T06-L4 0.69 c | OOP: classes and inheritance | Parent properties with private visibility are accessible in a subclass. | «no» Пояснение: Private properties are only accessible within the class that defines them, not in subclasses. Only public and protected properties are accessible in child classes.
Raw{"answer": "no", "explanation": "Private properties are only accessible within the class that defines them, not in subclasses. Only public and protected properties are accessible in child classes."} | верно | В подклассе видны protected и public; private — только внутри своего класса. |
T06-L5 1.95 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 have a generated name of the form 'class@anonymous\0/file.php:line$0', so the part before the NUL byte is 'class@anonymous'.
Raw{"answer":"class@anonymous","explanation":"Anonymous classes in PHP have a generated name of the form 'class@anonymous\\0/file.php:line$0', so the part before the NUL byte is 'class@anonymous'."} | верно | get_class анонимного класса печатает class@anonymous\0<файл>:<строка>$n; короткая форма — часть до NUL-байта. Проверено php -r (hex). |
T06-L6 1.62 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 part of the inheritance contract, so a child class can declare a method with the same name and any visibility without conflict.
Raw{"answer": "yes", "explanation": "In PHP, private methods are not part of the inheritance contract, so a child class can declare a method with the same name and any visibility without conflict."} | верно | private-члены не наследуются — правила совместимости подписей не действуют. |
T06-L7 1.63 c | OOP: classes and inheritance | The magic method __get() is called only for non-existent properties. | «no» Пояснение: __get() is called for both non-existent properties and inaccessible (private/protected) properties accessed from outside the class.
Raw{"answer": "no", "explanation": "__get() is called for both non-existent properties and inaccessible (private/protected) properties accessed from outside the class."} | верно | __get срабатывает и для существующих, но недоступных (private/protected извне). |
T06-L8 1.0 c | OOP: classes and inheritance | What does reassigning a readonly property throw — Exception or Error? | «error» Пояснение: Reassigning a readonly property throws a TypeError, which is a subclass of Error, not Exception.
Raw```json ⏎ {"answer": "Error", "explanation": "Reassigning a readonly property throws a TypeError, which is a subclass of Error, not Exception."} ⏎ ``` | верно | Error (readonly с 8.1); оговорка: в __clone() переинициализация допустима (8.3+). |
T07-L1 0.71 c | Interfaces, traits, enum | An interface can declare constants. | «yes» Пояснение: PHP interfaces can declare constants, which are always public and accessible via the interface name.
Raw{"answer": "yes", "explanation": "PHP interfaces can declare constants, which are always public and accessible via the interface name."} | верно | Константы интерфейса наследуются реализациями. |
T07-L2 0.69 c | Interfaces, traits, enum | Which operator checks whether an object is an instance of a class or interface? | «instanceof» Пояснение: The instanceof operator checks whether an object is an instance of a particular class or implements a particular interface.
Raw{"answer": "instanceof", "explanation": "The instanceof operator checks whether an object is an instance of a particular class or implements a particular interface."} | верно | instanceof. |
T07-L3 1.69 c | Interfaces, traits, enum | An interface can declare static methods. | «yes» Пояснение: PHP interfaces can declare static methods; they are implicitly public and abstract, and the implementing class must provide a corresponding static method.
Raw{"answer": "yes", "explanation": "PHP interfaces can declare static methods; they are implicitly public and abstract, and the implementing class must provide a corresponding static method."} | верно | Реализация обязана дать статический метод с той же сигнатурой. |
T07-L4 0.65 c | Interfaces, traits, enum | The instanceof operator only checks class inheritance: it ignores interfaces. | «no» Пояснение: PHP's instanceof operator checks both class inheritance and interface implementation; it returns true if the object implements the given interface.
Raw{"answer": "no", "explanation": "PHP's instanceof operator checks both class inheritance and interface implementation; it returns true if the object implements the given interface."} | верно | instanceof возвращает true и для интерфейсов объекта. |
T07-L5 1.56 c | Interfaces, traits, enum | An interface method may have a default implementation, like a trait method. | «no» Пояснение: Interface methods in PHP are always abstract and cannot have a default implementation; only trait methods can have a concrete body.
Raw{"answer": "no", "explanation": "Interface methods in PHP are always abstract and cannot have a default implementation; only trait methods can have a concrete body."} | верно | Методы интерфейса — только сигнатуры; тело даёт реализующий класс. |
T07-L6 0.64 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.81 c | Interfaces, traits, enum | How many elements will Foo::cases() return for enum Foo { case A; case B; case C; }? | «3» Пояснение: Foo::cases() returns an array of all enum cases, and there are exactly three cases defined: A, B, and C.
Raw{"answer": 3, "explanation": "Foo::cases() returns an array of all enum cases, and there are exactly three cases defined: A, B, and C."} | верно | Статический метод cases(): 3. |
T07-L8 1.35 c | Interfaces, traits, enum | A trait can declare constants. | «yes» Пояснение: In PHP, traits can declare constants, which are then inherited by any class that uses the trait.
Raw{"answer": "yes", "explanation": "In PHP, traits can declare constants, which are then inherited by any class that uses the trait."} | верно | С PHP 8.2 трейты могут объявлять константы (RFC constants_in_traits); до 8.2 — нет. |
T08-L1 0.84 c | Exceptions and errors | The Throwable interface is a common ancestor of both Exception and Error. | «yes» Пояснение: In PHP, both Exception and Error implement the Throwable interface, making it their common ancestor in the type hierarchy.
Raw{"answer": "yes", "explanation": "In PHP, both Exception and Error implement the Throwable interface, making it their common ancestor in the type hierarchy."} | верно | Иерархия с PHP 7: Throwable → Exception и Throwable → Error. |
T08-L2 1.24 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; they are siblings under the Throwable interface, so catch(Exception) does not catch TypeError.
Raw```json ⏎ {"answer": "no", "explanation": "TypeError extends Error, not Exception; they are siblings under the Throwable interface, so catch(Exception) does not catch TypeError."} ⏎ ``` | верно | TypeError наследуется от Error; catch (Exception) его не ловит. |
T08-L3 1.06 c | Exceptions and errors | The @ operator suppresses exceptions too. | «no» Пояснение: The @ operator only suppresses errors (warnings, notices, etc.), not exceptions, which are thrown and caught via throw/try-catch.
Raw{"answer": "no", "explanation": "The @ operator only suppresses errors (warnings, notices, etc.), not exceptions, which are thrown and caught via throw/try-catch."} | верно | @ глушит диагностику (warnings/notices), исключения не перехватывает. |
T08-L4 1.0 c | Exceptions and errors | What error class does intdiv(5, 0) throw? | «divisionbyzeroerror» Пояснение: intdiv(5, 0) throws a DivisionByZeroError when the divisor is zero.
Raw{"answer": "DivisionByZeroError", "explanation": "intdiv(5, 0) throws a DivisionByZeroError when the divisor is zero."} | верно | DivisionByZeroError (иерархия Error, не Exception); php-грейдер объективен. |
T08-L5 0.97 c | Exceptions and errors | The finally block runs only if the exception was caught by a catch block. | «no» Пояснение: The finally block runs regardless of whether an exception was thrown or caught; it executes in all cases.
Raw{"answer": "no", "explanation": "The finally block runs regardless of whether an exception was thrown or caught; it executes in all cases."} | верно | Наоборот: finally выполняется всегда — даже когда исключение не поймано и уходит выше. Проверено php -r. |
T08-L6 1.98 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 will replace (mask) the exception from the try block and can also override a return value from the try block.
Raw```json ⏎ {"answer": "no", "explanation": "An exception thrown in a finally block will replace (mask) the exception from the try block and can also override a return value from the try block."} ⏎ ``` | верно | Исключение из finally перекрывает исходное и уходит вместо него. |
T08-L7 1.22 c | Exceptions and errors | What does the expression (bool) new Exception('x') return? | «yes» Пояснение: In PHP, any object cast to boolean always evaluates to true, including instances of Exception.
Raw{"answer": "yes", "explanation": "In PHP, any object cast to boolean always evaluates to true, including instances of Exception."} | верно | Любой объект при приведении к bool — true. Формы ответа: true или да. |
T08-L8 1.05 c | Exceptions and errors | Functions registered via register_shutdown_function() run when exit is called. | «yes» Пояснение: Shutdown functions registered via register_shutdown_function() are executed when the script terminates, including when exit or die is called.
Raw{"answer": "yes", "explanation": "Shutdown functions registered via register_shutdown_function() are executed when the script terminates, including when exit or die is called."} | верно | exit завершает скрипт, но shutdown-функции отрабатывают. |
T09-L1 1.13 c | Namespaces and autoloading | The use App\Service\Mailer; statement itself loads the class file. | «no» Пояснение: The use statement is a compile-time alias; the class file is only loaded when the class is actually referenced (e.g., instantiated), triggering the autoloader.
Raw{"answer":"no","explanation":"The use statement is a compile-time alias; the class file is only loaded when the class is actually referenced (e.g., instantiated), triggering the autoloader."} | верно | use — псевдоним на этапе компиляции; файл грузит автозагрузчик при первом обращении. |
T09-L2 0.91 c | Namespaces and autoloading | What follows use to import a function (not a class): the word function or const? | «function» Пояснение: In PHP, to import a function from a namespace you use 'use function', while 'use const' is for importing constants.
Raw{"answer": "function", "explanation": "In PHP, to import a function from a namespace you use 'use function', while 'use const' is for importing constants."} | верно | use function ...; (и use const для констант). |
T09-L3 1.78 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, yielding src/Controller/Api/UserController.php.
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, yielding src/Controller/Api/UserController.php."} | верно | Остаток имени после префикса, \ → /. |
T09-L4 0.92 c | Namespaces and autoloading | Including vendor/autoload.php registers autoloaders via spl_autoload_register(). | «yes» Пояснение: Composer's vendor/autoload.php ultimately calls spl_autoload_register() to register its autoloader function with PHP's SPL autoload mechanism.
Raw{"answer": "yes", "explanation": "Composer's vendor/autoload.php ultimately calls spl_autoload_register() to register its autoloader function with PHP's SPL autoload mechanism."} | верно | Composer ставит автозагрузчик именно на spl_autoload_register. |
T09-L5 0.79 c | Namespaces and autoloading | The magic constant __NAMESPACE__ contains the name of the current namespace. | «yes» Пояснение: __NAMESPACE__ is a magic constant available since PHP 5.3 that resolves to the current namespace name (or an empty string in the global namespace).
Raw{"answer": "yes", "explanation": "__NAMESPACE__ is a magic constant available since PHP 5.3 that resolves to the current namespace name (or an empty string in the global namespace)."} | верно | В корневом пространстве — пустая строка. |
T09-L6 1.46 c | Namespaces and autoloading | An unqualified class name (without a leading \) in new is resolved from the global root. | «no» Пояснение: An unqualified class name in 'new' is resolved from the current namespace, not the global root; a leading backslash is needed to resolve from the global root.
Raw{"answer": "no", "explanation": "An unqualified class name in 'new' is resolved from the current namespace, not the global root; a leading backslash is needed to resolve from the global root."} | верно | Резолвится относительно текущего namespace (с учётом импортов). |
T09-L7 1.19 c | Namespaces and autoloading | With the PSR-4 mapping "App\ → src/", the class App\Model\User lives in the file src/Model/User.php. | «yes» Пояснение: PSR-4 maps the base namespace 'App\' to 'src/', the sub-namespace 'Model' to a 'Model/' subdirectory, and the class name 'User' to 'User.php', resulting in 'src/Model/User.php'.
Raw{"answer": "yes", "explanation": "PSR-4 maps the base namespace 'App\\' to 'src/', the sub-namespace 'Model' to a 'Model/' subdirectory, and the class name 'User' to 'User.php', resulting in 'src/Model/User.php'."} | верно | Остаток имени после префикса переносится в путь как есть. |
T09-L8 2.89 c | Namespaces and autoloading | A use statement may be written inside a function body — the import then applies to that function only. | «no» Пояснение: While a use statement can syntactically be placed inside a function, it is a compile-time construct that still applies to the file scope, not just that function.
Raw```json ⏎ {"answer": "no", "explanation": "While a use statement can syntactically be placed inside a function, it is a compile-time construct that still applies to the file scope, not just that function."} ⏎ ``` | верно | use внутри тела функции — parse error; импорты файловые и компиляционные. |
T10-L1 1.39 c | References and scope | Arrays are copied on assignment rather than passed by reference. | «yes» Пояснение: In PHP, arrays are copied on assignment (using copy-on-write since PHP 5.3) and are passed by value by default in function calls unless explicitly passed by reference with &.
Raw{"answer": "yes", "explanation": "In PHP, arrays are copied on assignment (using copy-on-write since PHP 5.3) and are passed by value by default in function calls unless explicitly passed by reference with &."} | верно | Присваивание массива — копия (в движке — copy-on-write). |
T10-L2 1.25 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 has 2 elements.
Raw{"answer": 2, "explanation": "PHP arrays are copied by value, so modifying $b does not affect $a, which still has 2 elements."} | верно | Присваивание — копия: в $a по-прежнему 2 элемента. |
T10-L3 1.22 c | References and scope | Inside a function, user-defined global variables are inaccessible without global, $GLOBALS, or passing them as parameters. | «yes» Пояснение: In PHP, variables in the global scope are not accessible inside a function's local scope unless explicitly brought in via 'global', '$GLOBALS', or passed as parameters.
Raw{"answer": "yes", "explanation": "In PHP, variables in the global scope are not accessible inside a function's local scope unless explicitly brought in via 'global', '$GLOBALS', or passed as parameters."} | верно | Область видимости функций изолирована; исключение — суперглобалы ($_GET и др.). |
T10-L4 1.73 c | References and scope | unset($GLOBALS['x']) inside a function removes the global variable only for that function. | «no» Пояснение: unset($GLOBALS['x']) inside a function removes the global variable entirely (globally), not just for that function's scope, because $GLOBALS is a direct reference to the global variables array.
Raw{"answer": "no", "explanation": "unset($GLOBALS['x']) inside a function removes the global variable entirely (globally), not just for that function's scope, because $GLOBALS is a direct reference to the global variables array."} | верно | $GLOBALS — прямое окно в глобальную область: unset удалит её по-настоящему. |
T10-L5 0.78 c | References and scope | What will this print: function inc(&$x) { $x++; } $n = 5; inc($n); echo $n; | «6» Пояснение: The function increments $x by reference, so $n is modified from 5 to 6.
Raw{"answer": 6, "explanation": "The function increments $x by reference, so $n is modified from 5 to 6."} | верно | Ссылка меняет оригинал: 6. |
T10-L6 5.24 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 the array's elements as they existed at the start; newly added elements are not visited in the same pass, so it does not fully reflect live changes.
Raw{"answer": "no", "explanation": "A foreach by value iterates over the array's elements as they existed at the start; newly added elements are not visited in the same pass, so it does not fully reflect live changes."} | верно | По значению foreach итерирует копию-снимок. |
T10-L7 0.84 c | References and scope | A static property belongs to each instance separately: changes in one object are not visible in others. | «no» Пояснение: Static properties belong to the class, not to individual instances; all instances share the same static property and changes are visible across all of them.
Raw{"answer": "no", "explanation": "Static properties belong to the class, not to individual instances; all instances share the same static property and changes are visible across all of them."} | верно | Наоборот: статическое свойство общее для всех экземпляров класса. Проверено php -r. |
T10-L8 1.02 c | References and scope | An array can have a boolean key true, and it will be stored as bool. | «no» Пояснение: In PHP, boolean array keys are cast to integers (true becomes 1, false becomes 0), not stored as bool.
Raw{"answer": "no", "explanation": "In PHP, boolean array keys are cast to integers (true becomes 1, false becomes 0), not stored as bool."} | верно | Булев ключ приводится к int: true → 1, false → 0. |
T11-L1 1.16 c | Generators, iterators, SPL | Inside a generator, return with a value can be used, and it becomes available via $gen->getReturn(). | «yes» Пояснение: In PHP 5.5+, a generator can use `return` with a value, and it is accessible via `$gen->getReturn()` after the generator is fully iterated.
Raw{"answer": "yes", "explanation": "In PHP 5.5+, a generator can use `return` with a value, and it is accessible via `$gen->getReturn()` after the generator is fully iterated."} | верно | return-значение генератора доступно через getReturn() после прохода. |
T11-L2 2.51 c | Generators, iterators, SPL | A fully consumed generator can be rewound with rewind() and traversed again. | «no» Пояснение: Calling rewind() on a generator that has already been started (i.e., after the first next() call) throws a LogicException, so a fully consumed generator cannot be rewound and re-traversed.
Raw```json ⏎ {"answer": "no", "explanation": "Calling rewind() on a generator that has already been started (i.e., after the first next() call) throws a LogicException, so a fully consumed generator cannot be rewound and re-traversed."} ⏎ ``` | верно | Генератор одноразовый: rewind после начала итерации бросает Exception. |
T11-L3 2.12 c | Generators, iterators, SPL | The yield from construct delegates traversal to another generator or iterable. | «no» Пояснение: yield from is a Python construct; PHP only has yield, not yield from.
Raw{"answer": "no", "explanation": "yield from is a Python construct; PHP only has yield, not yield from."} | неверно верный: «yes» | yield from проксирует значения, ключи и return-значение внутреннего генератора. |
T11-L4 2.43 c | Generators, iterators, SPL | What does get_class(g()) return for function g() { yield 1; }? | «generator» Пояснение: A function containing a yield statement is a generator function, and calling it returns a Generator object, so get_class() returns the string 'Generator'.
Raw{"answer": "Generator", "explanation": "A function containing a yield statement is a generator function, and calling it returns a Generator object, so get_class() returns the string 'Generator'."} | верно | Функция с yield возвращает Generator. |
T11-L5 1.28 c | Generators, iterators, SPL | How many elements will count(iterator_to_array((function () { yield from [1, 2, 3]; })())) return? | «3» Пояснение: The generator yields three values (1, 2, 3), iterator_to_array converts it to a 3-element array, and count returns 3.
Raw{"answer": 3, "explanation": "The generator yields three values (1, 2, 3), iterator_to_array converts it to a 3-element array, and count returns 3."} | верно | yield from делегирует все 3 элемента. |
T11-L6 0.62 c | Generators, iterators, SPL | The SplStack class implements a FIFO queue. | «no» Пояснение: SplStack implements a LIFO (Last In, First Out) stack, not a FIFO queue; SplQueue is the one that implements a FIFO queue.
Raw{"answer": "no", "explanation": "SplStack implements a LIFO (Last In, First Out) stack, not a FIFO queue; SplQueue is the one that implements a FIFO queue."} | верно | SplStack — стек LIFO; очередь FIFO — SplQueue. |
T11-L7 0.97 c | Generators, iterators, SPL | ArrayIterator allows wrapping an array and traversing it via the Iterator interface. | «yes» Пояснение: ArrayIterator is a built-in PHP class that wraps an array and implements the Iterator interface, allowing traversal with foreach.
Raw{"answer": "yes", "explanation": "ArrayIterator is a built-in PHP class that wraps an array and implements the Iterator interface, allowing traversal with foreach."} | верно | Объектная обёртка над массивом. |
T11-L8 0.68 c | Generators, iterators, SPL | An ArrayObject instance cannot be traversed with foreach. | «no» Пояснение: ArrayObject implements the Iterator interface, which extends Traversable, so it can be traversed with foreach.
Raw{"answer": "no", "explanation": "ArrayObject implements the Iterator interface, which extends Traversable, so it can be traversed with foreach."} | верно | ArrayObject реализует IteratorAggregate — foreach по нему работает. |
T12-L1 0.92 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, so no separate salt parameter is needed.
Raw{"answer": "yes", "explanation": "password_hash() automatically generates a random salt and embeds it in the resulting hash string, so no separate salt parameter is needed."} | верно | Соль встраивается в строку результата; параметр salt устарел. |
T12-L2 0.78 c | Configuration and security | In PHP 8, PASSWORD_DEFAULT is md5 with an automatically added salt. | «no» Пояснение: PASSWORD_DEFAULT in PHP 8 is an alias for PASSWORD_BCRYPT, which uses the bcrypt algorithm, not md5.
Raw{"answer": "no", "explanation": "PASSWORD_DEFAULT in PHP 8 is an alias for PASSWORD_BCRYPT, which uses the bcrypt algorithm, not md5."} | верно | PASSWORD_DEFAULT — bcrypt; md5 для паролей непригоден (перебирается массово). |
T12-L3 0.91 c | Configuration and security | What does password_verify('secret', password_hash('secret', PASSWORD_DEFAULT)) return? | «true» Пояснение: password_verify checks if the given password matches the hash, and since the same string 'secret' was used to create the hash, it returns true.
Raw{"answer": true, "explanation": "password_verify checks if the given password matches the hash, and since the same string 'secret' was used to create the hash, it returns true."} | верно | Соль и хеш в одной строке: true (форма ответа: true или да). |
T12-L4 1.13 c | Configuration and security | strip_tags() protects against SQL injection. | «no» Пояснение: strip_tags() removes HTML/PHP tags and helps prevent XSS, but SQL injection is mitigated by prepared statements or proper escaping, not by stripping tags.
Raw{"answer": "no", "explanation": "strip_tags() removes HTML/PHP tags and helps prevent XSS, but SQL injection is mitigated by prepared statements or proper escaping, not by stripping tags."} | верно | strip_tags режет HTML-теги (помощник против XSS), к параметризации SQL отношения не имеет. |
T12-L5 1.2 c | Configuration and security | session_regenerate_id() is used to protect against session fixation upon user login. | «yes» Пояснение: session_regenerate_id() replaces the current session ID with a new one, which is the primary defense against session fixation attacks, typically called upon login when the session's privilege level changes.
Raw{"answer": "yes", "explanation": "session_regenerate_id() replaces the current session ID with a new one, which is the primary defense against session fixation attacks, typically called upon login when the session's privilege level changes."} | верно | Новый 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() returns the SAPI name of the current PHP interpreter, such as 'cli' or 'fpm-fcgi'.
Raw{"answer": "php_sapi_name", "explanation": "php_sapi_name() returns the SAPI name of the current PHP interpreter, such as 'cli' or 'fpm-fcgi'."} | верно | php_sapi_name(). |
T12-L7 1.26 c | Configuration and security | session_destroy() deletes session data on the server but not the cookie in the user's browser. | «yes» Пояснение: session_destroy() only removes the session data stored on the server; to clear the session cookie in the browser, you must separately call setcookie() with a past expiration time.
Raw{"answer": "yes", "explanation": "session_destroy() only removes the session data stored on the server; to clear the session cookie in the browser, you must separately call setcookie() with a past expiration time."} | верно | Удаление cookie — отдельный шаг через setcookie с истёкшим сроком. |
T12-L8 0.86 c | Configuration and security | Without calling session_start(), the $_SESSION array is automatically populated with session data. | «no» Пояснение: The $_SESSION array is only populated with session data after session_start() is called; without it, it remains empty.
Raw{"answer": "no", "explanation": "The $_SESSION array is only populated with session data after session_start() is called; without it, it remains empty."} | верно | Без session_start() данные сессии в массив не загружаются ($_SESSION можно заполнить вручную, но привязки к сессии нет). |
VC-L1 1.4 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 'Array find and find key' RFC.
Raw{"answer": "8.4", "explanation": "The array_find() function was introduced in PHP 8.4 as part of the 'Array find and find key' RFC."} | верно | PHP 8.4 (RFC array_find). |
VC-L2 1.19 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 accessors to be defined directly within the property declaration.
Raw{"answer": "yes", "explanation": "PHP 8.4 introduced property hooks, allowing get and set accessors to be defined directly within the property declaration."} | верно | Property hooks — PHP 8.4 (ноябрь 2024). |
VC-L3 1.08 c | PHP 8.4–8.5 | Asymmetric visibility (public private(set) string $name) appeared in PHP 8.4. | «yes» Пояснение: Asymmetric visibility (e.g., public private(set) string $name) is a new feature introduced in PHP 8.4, allowing different visibility for reading vs. writing a property.
Raw{"answer": "yes", "explanation": "Asymmetric visibility (e.g., public private(set) string $name) is a new feature introduced in PHP 8.4, allowing different visibility for reading vs. writing a property."} | верно | Asymmetric visibility v2 — PHP 8.4. |
VC-L4 1.38 c | PHP 8.4–8.5 | In which PHP version was the #[\NoDiscard] attribute introduced? Answer with the version number. | «8.4» Пояснение: The #[\NoDiscard] attribute was introduced in PHP 8.4, allowing developers to mark function return values that should not be silently discarded.
Raw{"answer": "8.4", "explanation": "The #[\\NoDiscard] attribute was introduced in PHP 8.4, allowing developers to mark function return values that should not be silently discarded."} | неверно верный: «8.5» | #[\NoDiscard] — PHP 8.5 (marking return values as important). |
VC-L5 4.95 c | PHP 8.4–8.5 | In which PHP version did the pipe operator |> first appear? Answer with the version number. | «not yet» Пояснение: The pipe operator (|>) is still an open RFC and has not been included in any stable PHP release as of PHP 8.4.
Raw{"answer": "not yet", "explanation": "The pipe operator (|>) is still an open RFC and has not been included in any stable PHP release as of PHP 8.4."} | неверно верный: «8.5» | Pipe operator — PHP 8.5 (2025). |
VC-L6 2.91 c | PHP 8.4–8.5 | In which PHP version did clone-with — the syntax clone($obj, ['x' => 1]) — appear? Answer with the version number. | «8.4» Пояснение: The 'Clone with' syntax (clone $obj with ['x' => 1]) was introduced in PHP 8.4.
Raw{"answer": "8.4", "explanation": "The 'Clone with' syntax (clone $obj with ['x' => 1]) was introduced in PHP 8.4."} | неверно верный: «8.5» | Clone with v2 — PHP 8.5. |
VC-L7 1.25 c | PHP 8.4–8.5 | In which PHP version were the array_first() and array_last() functions introduced? | «8.4» Пояснение: array_first() and array_last() were introduced in PHP 8.4.
Raw{"answer": "8.4", "explanation": "array_first() and array_last() were introduced in PHP 8.4."} | неверно верный: «8.5» | PHP 8.5. |
VC-L8 3.99 c | PHP 8.4–8.5 | For which PHP version was RFC Partial Function Application v2 adopted (as of 2026-11-07)? Answer with the version number. | «8.4» Пояснение: The RFC Partial Function Application v2 was adopted for PHP 8.4.
Raw{"answer": "8.4", "explanation": "The RFC Partial Function Application v2 was adopted for PHP 8.4."} | неверно верный: «8.6» | PFA v2 принят 05.12.2025 (33-0-0), реализован в PHP 8.6. |
VF-L1 1.08 c | PHP: 8.6+ and the future | For which PHP version was the RFC clamp_v2 (the clamp() function) implemented, as of 2026-11-07? Answer with the version number. | «8.4» Пояснение: The clamp() function was introduced in PHP 8.4 via the clamp_v2 RFC.
Raw{"answer": 8.4, "explanation": "The clamp() function was introduced in PHP 8.4 via the clamp_v2 RFC."} | неверно верный: «8.6» | По данным владельца (wiki.php.net/rfc): clamp_v2 — 8.6; clamp() в 8.5.11 отсутствует (косвенное подтверждение). Дата-якорь делает клетку монотонной. |
VF-L2 4.76 c | PHP: 8.6+ and the future | RFC Context Managers v2 has already been adopted in PHP (as of 2026-11-07). | «no» Пояснение: As of November 2026, the Context Managers v2 RFC has not yet been adopted into PHP; it remains in the proposal or voting stage.
Raw```json ⏎ {"answer": "no", "explanation": "As of November 2026, the Context Managers v2 RFC has not yet been adopted into PHP; it remains in the proposal or voting stage."} ⏎ ``` | верно | На 06.11.2026 — в обсуждении (создан 2026-10-23); не принят. |
VF-L3 2.48 c | PHP: 8.6+ and the future | RFC Bound-Erased Generic Types (generics) was declined in 2026. | «no» Пояснение: The Bound-Erased Generic Types (Generics) RFC was accepted for PHP 8.5, not declined.
Raw{"answer": "no", "explanation": "The Bound-Erased Generic Types (Generics) RFC was accepted for PHP 8.5, not declined."} | неверно верный: «yes» | Голосование завершилось 2026-06-28: отклонён (wiki.php.net/rfc). |
VF-L4 4.56 c | PHP: 8.6+ and the future | As of 2026-11-07, the RFC enabling multithreading (ZTS) by default has already been accepted in PHP. | «yes» Пояснение: An RFC to make ZTS (Zend Thread Safety) the default build mode in PHP was accepted, as the gap between NTS and ZTS builds had narrowed enough to make ZTS safe as the default.
Raw```json ⏎ {"answer": "yes", "explanation": "An RFC to make ZTS (Zend Thread Safety) the default build mode in PHP was accepted, as the gap between NTS and ZTS builds had narrowed enough to make ZTS safe as the default."} ⏎ ``` | неверно верный: «no» | Такого принятого RFC нет на дату якоря; якорь делает клетку монотонной — при принятии RFC позже клетка не перевернётся. |
VF-L5 1.73 c | PHP: 8.6+ and the future | As of PHP 8.5, generics (parameterized types) are still absent. | «yes» Пояснение: PHP 8.5 does not introduce native generics; parameterized types remain absent from the language spec.
Raw{"answer": "yes", "explanation": "PHP 8.5 does not introduce native generics; parameterized types remain absent from the language spec."} | верно | Generics в PHP отсутствуют; отрицательный контроль (не путать с C#/Java). |
VF-L6 2.24 c | PHP: 8.6+ and the future | As of 2026-11-07, the latest stable PHP version is 8.5, and PHP 8.6 has not been released yet (GA — 2026-11-19). | «yes» Пояснение: PHP follows a yearly release cycle in November; PHP 8.5 was released in November 2025 and PHP 8.6 is expected to go GA on 2026-11-19, so as of 2026-11-07, 8.5 is indeed the latest stable version.
Raw{"answer": "yes", "explanation": "PHP follows a yearly release cycle in November; PHP 8.5 was released in November 2025 and PHP 8.6 is expected to go GA on 2026-11-19, so as of 2026-11-07, 8.5 is indeed the latest stable version."} | верно | 8.5 — релиз осени 2025; 8.6 GA 19.11.2026 (wiki.php.net/todo/php86). Дата снимка — 06.11.2026. |
VF-L7 1.16 c | PHP: 8.6+ and the future | The PHP 6 branch never shipped: after PHP 5.6 came PHP 7.0 directly. | «yes» Пояснение: PHP went directly from 5.6 (released 2014) to 7.0 (released 2015), skipping the 6.x series entirely.
Raw{"answer": "yes", "explanation": "PHP went directly from 5.6 (released 2014) to 7.0 (released 2015), skipping the 6.x series entirely."} | верно | Исторический факт: ветка 6 не была релизнута. |
VF-L8 2.4 c | PHP: 8.6+ and the future | The RFC adding the #[\Deprecated] attribute to the core was adopted. | «no» Пояснение: The RFC for the #[\Deprecated] attribute was not accepted for PHP 8.4; it received a minority vote and was deferred.
Raw{"answer": "no", "explanation": "The RFC for the #[\\Deprecated] attribute was not accepted for PHP 8.4; it received a minority vote and was deferred."} | неверно верный: «yes» | #[\Deprecated] — принят, реализован в PHP 8.4. |
T25-L1 0.89 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, the Dependency Rule dictates that dependencies point only inward, so inner layers (domain/core) have no knowledge of outer layers (frameworks, UI, DB).
Raw{"answer": "yes", "explanation": "In both Clean and Onion architecture, the Dependency Rule dictates that dependencies point only inward, so inner layers (domain/core) have no knowledge of outer layers (frameworks, UI, DB)."} | верно | Чистая (Robert C. Martin), луковичная (Jeffrey Palermo) и гексагональная (ports & adapters) — варианты одной идеи: зависимости направлены внутрь, к домену. Слоями в проекте следит deptrac. |
T25-L2 1.1 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 objects with no framework dependencies (Doctrine, Symfony), keeping the domain layer decoupled from infrastructure concerns.
Raw{"answer": "yes", "explanation": "Domain entities should be pure PHP objects with no framework dependencies (Doctrine, Symfony), keeping the domain layer decoupled from infrastructure concerns."} | верно | Изоляция домена от инфраструктуры; deptrac в проекте как раз следит за слоями. |
T25-L3 1.24 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 (or interface) layer, not the business-logic layer; they call use cases but do not contain business logic themselves.
Raw{"answer": "no", "explanation": "Controllers and Twig templates belong to the presentation (or interface) layer, not the business-logic layer; they call use cases but do not contain business logic themselves."} | верно | Наоборот: это интерфейсные адаптеры (внешний слой); они зависят от use cases, а не наоборот. |
T25-L4 1.01 c | Clean architecture | What sits at the very center of the onion architecture? | «entity» Пояснение: In the onion architecture, the innermost layer at the center consists of the core domain entities and business rules.
Raw{"answer": "Entity", "explanation": "In the onion architecture, the innermost layer at the center consists of the core domain entities and business rules."} | неверно верный: «domain model» | Центральное кольцо — Domain Model: сущности и бизнес-правила без зависимостей; далее Domain Services → Application Services → Infrastructure/UI/Tests (Palermo). |
T25-L5 1.14 c | Clean architecture | Layer boundary violations can be caught automatically: a layer-dependency analyzer (e.g. deptrac) fails on a forbidden call. | «yes» Пояснение: Deptrac is a PHP static analysis tool that enforces layer dependency rules and fails the build when a forbidden cross-layer call is detected.
Raw{"answer":"yes","explanation":"Deptrac is a PHP static analysis tool that enforces layer dependency rules and fails the build when a forbidden cross-layer call is detected."} | верно | depfile.yaml в проекте TasK: CI проверяет правила слоёв на каждом пайплайне. |
T25-L6 2.3 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 be framework-agnostic: it should accept simple data/DTOs rather than an HTTP request, and depend on repository/gateway abstractions rather than a concrete EntityManager, keeping it decoupled from transport and infrastructure layers.
Raw{"answer": "no", "explanation": "A use case (interactor) should be framework-agnostic: it should accept simple data/DTOs rather than an HTTP request, and depend on repository/gateway abstractions rather than a concrete EntityManager, keeping it decoupled from transport and infrastructure layers."} | верно | Use case принимает DTO и порты; привязка к HTTP/ORM протекает инфраструктуру во внутренние слои. |
T25-L7 1.57 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 in DDD provides a collection-like interface for accessing domain aggregates/entities while abstracting the underlying storage mechanism.
Raw{"answer": "Repository", "explanation": "The Repository pattern in DDD provides a collection-like interface for accessing domain aggregates/entities while abstracting the underlying storage mechanism."} | верно | Repository pattern (DDD/Evans); в проекте — Doctrine-репозитории за портами. |
T25-L8 1.75 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 on abstractions (e.g., a Repository interface), so swapping the database only requires changing the concrete Repository implementation in the outer layers.
Raw{"answer": "yes", "explanation": "In Clean Architecture, the domain and use cases depend on abstractions (e.g., a Repository interface), so swapping the database only requires changing the concrete Repository implementation in the outer layers."} | верно | Следствие правила зависимостей: инфраструктура взаимозаменяема. |
T26-L1 1.21 c | DDD | In DDD, an aggregate is just another name for a database table. | «no» Пояснение: In DDD, an aggregate is a cluster of domain objects treated as a unit for business consistency; it is a domain concept, not a database table.
Raw{"answer": "no", "explanation": "In DDD, an aggregate is a cluster of domain objects treated as a unit for business consistency; it is a domain concept, not a database table."} | верно | Агрегат — кластер объектов с границей согласованности (транзакционной вокруг корня); таблица — деталь хранения. |
T26-L2 0.9 c | DDD | A Value Object is immutable and compared by the values of its fields, not by identity. | «yes» Пояснение: Value Objects are defined by their immutability and value-based equality, distinguishing them from entities which are identified by a unique identity.
Raw{"answer": "yes", "explanation": "Value Objects are defined by their immutability and value-based equality, distinguishing them from entities which are identified by a unique identity."} | верно | Классика Evans: Money, Email; равенство структурное. |
T26-L3 0.85 c | DDD | What is the single external entry point of an aggregate, through which all changes must go, called? | «aggregate root» Пояснение: In Domain-Driven Design, the Aggregate Root is the single external entry point through which all changes to the aggregate must pass.
Raw{"answer": "Aggregate Root", "explanation": "In Domain-Driven Design, the Aggregate Root is the single external entry point through which all changes to the aggregate must pass."} | верно | Aggregate Root: внешние объекты ссылаются только на корень; он защищает инварианты агрегата. |
T26-L4 1.02 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, and all entities within that aggregate are accessed through the root rather than having their own repositories.
Raw{"answer": "yes", "explanation": "In DDD, a repository is defined per aggregate root, and all entities within that aggregate are accessed through the root rather than having their own repositories."} | верно | Репозиторий корня хранит границу согласованности агрегата; вложенные сущности доступны только через корень. |
T26-L5 0.84 c | DDD | Ubiquitous language is the model's shared language common to developers and domain experts. | «yes» Пояснение: Ubiquitous Language is a DDD concept referring to the shared vocabulary consistently used by both developers and domain experts throughout the project.
Raw{"answer": "yes", "explanation": "Ubiquitous Language is a DDD concept referring to the shared vocabulary consistently used by both developers and domain experts throughout the project."} | верно | Evans: язык из требований переходит в имена классов и методов. |
T26-L6 2.31 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 terms refer to different models.
Raw{"answer": "frame", "explanation": "A frame is the boundary within which a model and its language are self-consistent, while outside it the same terms refer to different models."} | неверно верный: «bounded context» | Bounded Context; «Заказ» в биллинге и в доставке — разные модели. |
T26-L7 1.31 c | DDD | An anemic model (objects with only getters/setters, logic in services) is the recommended DDD style. | «no» Пояснение: DDD recommends a rich domain model where objects encapsulate both state and behavior; anemic models are considered an anti-pattern in DDD.
Raw{"answer": "no", "explanation": "DDD recommends a rich domain model where objects encapsulate both state and behavior; anemic models are considered an anti-pattern in DDD."} | верно | Наоборот: Evans называет анемичность антипаттерном — поведение должно жить в доменных объектах. |
T26-L8 2.0 c | DDD | Bounded context means each context has its own model: the same concept in different contexts is a different class. | «yes» Пояснение: In DDD, a Bounded Context defines a boundary where a model has a specific meaning, so the same real-world concept (e.g., 'Product') is typically modeled as a different class in each context with its own attributes and behaviors.
Raw{"answer":"yes","explanation":"In DDD, a Bounded Context defines a boundary where a model has a specific meaning, so the same real-world concept (e.g., 'Product') is typically modeled as a different class in each context with its own attributes and behaviors."} | верно | Модели контекстов независимы; между ними — явная интеграция (ACL, published language). |
T13-L1 0.9 c | Symfony | Services in the Symfony DI container are created lazily by default — on first use. | «yes» Пояснение: Symfony's DI container instantiates services lazily by default, only creating them when they are first requested.
Raw{"answer": "yes", "explanation": "Symfony's DI container instantiates services lazily by default, only creating them when they are first requested."} | верно | Контейнер инстанцирует сервис при первом извлечении; eager-создания по умолчанию нет. |
T13-L2 0.67 c | Symfony | Which Symfony console command lists all registered routes? | «debug:router» Пояснение: The Symfony console command 'debug:router' (or 'bin/console debug:router') lists all registered routes in the application.
Raw{"answer": "debug:router", "explanation": "The Symfony console command 'debug:router' (or 'bin/console debug:router') lists all registered routes in the application."} | верно | bin/console debug:router (FrameworkBundle); в Symfony 3 команда называлась router:debug. |
T13-L3 1.06 c | Symfony | Symfony autowiring requires manually declaring every service in services.yaml. | «no» Пояснение: Autowiring automatically resolves dependencies based on type hints, so services do not need to be manually declared in services.yaml.
Raw{"answer": "no", "explanation": "Autowiring automatically resolves dependencies based on type hints, so services do not need to be manually declared in services.yaml."} | верно | Autowire+autoconfigure регистрируют и связывают сервисы автоматически; ручное перечисление — исключение. |
T13-L4 0.96 c | Symfony | Twig templates are compiled into PHP classes and cached between requests. | «yes» Пояснение: Twig compiles templates into PHP classes that extend Twig\Template and caches them on disk to avoid recompilation on subsequent requests.
Raw{"answer": "yes", "explanation": "Twig compiles templates into PHP classes that extend Twig\\Template and caches them on disk to avoid recompilation on subsequent requests."} | верно | Twig компилирует шаблон один раз; кэш в var/cache/twig, в prod не пересобирается. |
T13-L5 1.44 c | Symfony | In the Symfony dev environment the DI container is rebuilt only after tracked files change, not on every request. | «yes» Пояснение: Symfony caches the compiled DI container and only rebuilds it when tracked files (configs, classes, etc.) are detected as changed, not on every request.
Raw{"answer": "yes", "explanation": "Symfony caches the compiled DI container and only rebuilds it when tracked files (configs, classes, etc.) are detected as changed, not on every request."} | верно | Kernel проверяет freshness ресурсов (конфиги, классы); иначе переиспользуется кэш контейнера. |
T13-L6 0.78 c | Symfony | Which environment variable selects the active Symfony environment (dev/prod)? | «app_env» Пояснение: The APP_ENV environment variable selects the active Symfony environment (e.g., dev, prod).
Raw{"answer": "APP_ENV", "explanation": "The APP_ENV environment variable selects the active Symfony environment (e.g., dev, prod)."} | верно | APP_ENV в .env; APP_DEBUG — отдельный флаг отладки. |
T13-L7 1.91 c | Symfony | A controller method can be private — Symfony routing works with any method of the class. | «no» Пояснение: Symfony's ControllerResolver requires controller action methods to be public; private methods are not callable from outside the class and will cause an error.
Raw{"answer": "no", "explanation": "Symfony's ControllerResolver requires controller action methods to be public; private methods are not callable from outside the class and will cause an error."} | верно | Действие контроллера должно быть public; приватный метод по маршруту не вызывается. |
T13-L8 2.07 c | Symfony | Event subscribers always receive events before listeners, because the interface gives them priority. | «no» Пояснение: Event subscribers are internally just a convenience for registering multiple listeners; they are ordered by the same priority/registration-order mechanism as regular listeners, with no inherent precedence.
Raw```json ⏎ {"answer": "no", "explanation": "Event subscribers are internally just a convenience for registering multiple listeners; they are ordered by the same priority/registration-order mechanism as regular listeners, with no inherent precedence."} ⏎ ``` | верно | Порядок определяет priority, а не тип подписки; приоритеты задаются в getSubscribedEvents() так же, как у слушателей. |
T22-L1 1.45 c | Symfony: Security and forms | In modern Symfony (6.0+) authentication is built on authenticator classes (AuthenticatorInterface); the old guard system has been removed. | «yes» Пояснение: Symfony 6.0 removed the legacy guard authentication system, which was deprecated in 5.3, and the new authentication system is built around AuthenticatorInterface (authenticator classes).
Raw{"answer": "yes", "explanation": "Symfony 6.0 removed the legacy guard authentication system, which was deprecated in 5.3, and the new authentication system is built around AuthenticatorInterface (authenticator classes)."} | верно | Guard объявлен устаревшим в 5.3 и удалён в 6.0; в проекте symfony/security-bundle 8.1. |
T22-L2 2.93 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 a user has a specific role or permission on a controller method, throwing a 403 AccessDeniedException if they don't.
Raw{"answer": "IsGranted", "explanation": "The #[IsGranted] attribute in Symfony checks if a user has a specific role or permission on a controller method, throwing a 403 AccessDeniedException if they don't."} | верно | #[IsGranted('ROLE_ADMIN')]; атрибут из symfony/security-http. |
T22-L3 1.14 c | Symfony: Security and forms | Voters are Symfony's mechanism for checking access to a specific object: isGranted('EDIT', $post). | «yes» Пояснение: Symfony Voters are the mechanism for checking access to a specific object, and isGranted('EDIT', $post) is the standard way to use them.
Raw{"answer": "yes", "explanation": "Symfony Voters are the mechanism for checking access to a specific object, and isGranted('EDIT', $post) is the standard way to use them."} | верно | VoterInterface->vote(); docs Symfony — Voters. |
T22-L4 2.45 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 requires PHP 8.2+ and uses native PHP attributes (#[Assert\NotBlank]) for validation; the doctrine/annotations package is no longer a framework dependency.
Raw{"answer": "yes", "explanation": "Symfony 7 requires PHP 8.2+ and uses native PHP attributes (#[Assert\NotBlank]) for validation; the doctrine/annotations package is no longer a framework dependency."} | верно | Докблок-аннотации удалены в Symfony 7.0; стандарт — атрибуты. В проекте symfony/validator 8.1. |
T22-L5 1.15 c | Symfony: Security and forms | CSRF protection of Symfony forms is enabled by default: the form validates the token on submission. | «yes» Пояснение: Symfony's Form component has CSRF protection enabled by default; the form automatically adds and validates a CSRF token on submission unless explicitly disabled.
Raw{"answer": "yes", "explanation": "Symfony's Form component has CSRF protection enabled by default; the form automatically adds and validates a CSRF token on submission unless explicitly disabled."} | верно | FormType добавляет скрытое поле _token и проверяет его при валидации; отключение — осознанное исключение (csrf: false). |
T22-L6 1.14 c | Symfony: Security and forms | Form validation in Symfony runs server-side even if the client-side (HTML5) checks passed. | «yes» Пояснение: Symfony's form validation is always executed server-side; HTML5 client-side validation is merely a UX convenience and does not replace Symfony's own validation process.
Raw{"answer": "yes", "explanation": "Symfony's form validation is always executed server-side; HTML5 client-side validation is merely a UX convenience and does not replace Symfony's own validation process."} | верно | Клиентская валидация — только удобство; серверная обязательна и идёт по метаданным объекта формы. |
T22-L7 0.93 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.62 c | Symfony: Security and forms | Symfony stores the user's password in the session in plain text. | «no» Пояснение: Symfony stores the user identifier and roles in the session, not the plain-text password; the password is only used to verify against the hashed value in the database during login.
Raw{"answer": "no", "explanation": "Symfony stores the user identifier and roles in the session, not the plain-text password; the password is only used to verify against the hashed value in the database during login."} | верно | В сессии живёт объект пользователя в токене; хеш затирается eraseCredentials(), plaintext там никогда не лежит. |
T23-L1 1.09 c | Symfony: configuration and services | Symfony bundle configuration lives in config/packages — one file per bundle or topic. | «yes» Пояснение: In modern Symfony, the convention is to place bundle and topic-specific configuration in config/packages/ with one YAML file per bundle or topic.
Raw{"answer": "yes", "explanation": "In modern Symfony, the convention is to place bundle and topic-specific configuration in config/packages/ with one YAML file per bundle or topic."} | верно | Стандартная структура (config/packages/*.yaml); перегрузка — config/packages/<env>. |
T23-L2 2.59 c | Symfony: configuration and services | The .env file with dev defaults is committed to the repository, while real secrets live in the non-committed .env.local. | «yes» Пояснение: This is the standard Symfony convention where .env contains default dev values committed to the repo, and .env.local holds local secrets and is gitignored.
Raw```json ⏎ {"answer": "yes", "explanation": "This is the standard Symfony convention where .env contains default dev values committed to the repo, and .env.local holds local secrets and is gitignored."} ⏎ ``` | верно | symfony/dotenv: .env — общий безопасный набор значений; локальные секреты — .env.local (gitignored) или secrets-хранилище. |
T23-L3 1.3 c | Symfony: configuration and services | Which Symfony command lists the container's registered services and their aliases? | «container:debug» Пояснение: The Symfony command 'container:debug' (alias 'debug:container') lists all services registered in the service container, including their aliases, tags, and visibility.
Raw{"answer": "container:debug", "explanation": "The Symfony command 'container:debug' (alias 'debug:container') lists all services registered in the service container, including their aliases, tags, and visibility."} | неверно верный: «debug:container» | bin/console debug:container; параметры контейнера — debug:parameter. |
T23-L4 3.39 c | Symfony: configuration and services | The Symfony container allows changing parameters at runtime: $container->setParameter() works from a controller. | «yes» Пояснение: The Container class has a setParameter() method that can be called from a controller to store a new value, which will be returned by subsequent getParameter() calls, though services that already received the parameter via compilation won't be affected.
Raw```json ⏎ {"answer": "yes", "explanation": "The Container class has a setParameter() method that can be called from a controller to store a new value, which will be returned by subsequent getParameter() calls, though services that already received the parameter via compilation won't be affected."} ⏎ ``` | неверно верный: «no» | Контейнер компилируется и замораживается; runtime-значения — только через переменные окружения. |
T23-L5 1.0 c | Symfony: configuration and services | By default, Symfony services are public (public: true) — you can fetch them directly from the container. | «no» Пояснение: Since Symfony 4.0, services are private (public: false) by default, allowing the container to optimize and remove unused services.
Raw{"answer": "no", "explanation": "Since Symfony 4.0, services are private (public: false) by default, allowing the container to optimize and remove unused services."} | верно | С Symfony 4.0 сервисы по умолчанию private: инжектятся через autowiring; $container->get() — только для публичных. |
T23-L6 1.05 c | Symfony: configuration and services | Without a config file in config/packages a bundle will not work — configuration is mandatory for every bundle. | «no» Пояснение: Most Symfony bundles work without a configuration file in config/packages because they ship with sensible defaults; configuration is optional, not mandatory.
Raw{"answer": "no", "explanation": "Most Symfony bundles work without a configuration file in config/packages because they ship with sensible defaults; configuration is optional, not mandatory."} | верно | У бандлов есть встроенные умолчания (Extension); конфиг нужен только для отклонений от них. |
T23-L7 0.73 c | Symfony: configuration and services | Environment variable values are injected into services.yaml using the %env(VAR)% syntax. | «yes» Пояснение: In Symfony, the %env(VAR_NAME)% syntax is the correct way to reference environment variables in YAML configuration files such as services.yaml.
Raw{"answer": "yes", "explanation": "In Symfony, the %env(VAR_NAME)% syntax is the correct way to reference environment variables in YAML configuration files such as services.yaml."} | верно | %env(...)% резолвится в рантайме env-процессорами; docs — Env Var Processors. |
T23-L8 1.29 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 whether Symfony runs in debug mode, enabling the profiler and Twig debug toolbar.
Raw{"answer": "APP_DEBUG", "explanation": "The APP_DEBUG environment variable controls whether Symfony runs in debug mode, enabling the profiler and Twig debug toolbar."} | верно | APP_DEBUG=1 (в .env dev-окружения); окружение выбирает APP_ENV — см. T13-L6. |
T16-L1 1.71 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 by default all matching handlers will be invoked.
Raw{"answer": "no", "explanation": "Symfony Messenger allows multiple handlers to be registered for the same message class, and by default all matching handlers will be invoked."} | верно | Messenger вызывает все хендлеры, подписанные на класс сообщения (docs — Multiple Handlers). |
T16-L2 1.12 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 within the same process without queueing it for a worker, unlike async transports.
Raw{"answer": "no", "explanation": "The sync transport handles the message immediately within the same process without queueing it for a worker, unlike async transports."} | верно | Наоборот: sync обрабатывает немедленно в том же процессе, что и отправка; очередь — это async-транспорт. |
T16-L3 0.62 c | Symfony: Messenger | Which console command starts the worker that processes Messenger queue messages? | «messenger:consume» Пояснение: In Symfony, the messenger:consume command starts the worker that processes messages from the Messenger queue/transport.
Raw{"answer": "messenger:consume", "explanation": "In Symfony, the messenger:consume command starts the worker that processes messages from the Messenger queue/transport."} | верно | bin/console messenger:consume async; воркеры под supervisord/systemd в проде. |
T16-L4 1.53 c | Symfony: Messenger | Retries for failed messages (retry_strategy) are configured per Messenger transport. | «no» Пояснение: The retry_strategy is configured globally in the framework config or per message via the envelope, not per transport.
Raw```json ⏎ {"answer": "no", "explanation": "The retry_strategy is configured globally in the framework config or per message via the envelope, not per transport."} ⏎ ``` | неверно верный: «yes» | retry_strategy на транспорте: max_retries, delay, multiplier; docs — Failed Messages & Retries. |
T16-L5 0.87 c | Symfony: Messenger | By default, Messenger serializes messages to JSON. | «yes» Пояснение: Symfony Messenger uses the SerializerMessageSerializer by default, which serializes messages to JSON format.
Raw{"answer": "yes", "explanation": "Symfony Messenger uses the SerializerMessageSerializer by default, which serializes messages to JSON format."} | неверно верный: «no» | Дефолтный сериализатор — PhpSerializer (serialize()); JSON-сериализатор включается отдельно. |
T16-L6 2.74 c | Symfony: Messenger | Symfony Scheduler produces messages on a schedule and dispatches them through Messenger. | «no» Пояснение: Symfony Scheduler schedules and executes tasks (e.g., method calls) at defined intervals; it does not inherently produce messages or dispatch them through Messenger, though it can be used in combination with Messenger.
Raw```json ⏎ {"answer": "no", "explanation": "Symfony Scheduler schedules and executes tasks (e.g., method calls) at defined intervals; it does not inherently produce messages or dispatch them through Messenger, though it can be used in combination with Messenger."} ⏎ ``` | неверно верный: «yes» | Schedule → RecurringMessage → шина Messenger; docs — Scheduler. |
T16-L7 0.73 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 via Doctrine ORM/DBAL.
Raw{"answer": "doctrine", "explanation": "The doctrine transport in Symfony Messenger stores messages in database tables via Doctrine ORM/DBAL."} | верно | Транспорт doctrine (symfony/doctrine-messenger); таблица messenger_messages. В проекте стоит amqp-messenger + doctrine-messenger. |
T16-L8 1.89 c | Symfony: Messenger | The Messenger pipeline can be extended with custom middleware, placed before or after the built-in ones. | «yes» Пояснение: Laravel's Messenger allows you to add custom middleware via the through() method on a command class, and you can order them before or after built-in middleware like authorization.
Raw{"answer": "yes", "explanation": "Laravel's Messenger allows you to add custom middleware via the through() method on a command class, and you can order them before or after built-in middleware like authorization."} | верно | messenger.bus.*.middleware в yaml; docs — Middleware. |
T28-L1 3.45 c | Symfony: versions | Symfony major releases come every two years, minor ones every six months (in May and November). | «no» Пояснение: Symfony major releases (e.g., 5.0, 6.0, 7.0) come approximately every year, not every two years; minor/feature releases do come every six months in May and November.
Raw```json ⏎ {"answer": "no", "explanation": "Symfony major releases (e.g., 5.0, 6.0, 7.0) come approximately every year, not every two years; minor/feature releases do come every six months in May and November."} ⏎ ``` | неверно верный: «yes» | Стандартный релизный цикл: 8.0 — ноябрь 2025, 8.1 — май 2026, 8.2 — ноябрь 2026. |
T28-L2 1.8 c | Symfony: versions | What is the minimum PHP version required by Symfony 8? | «8.4» Пояснение: Symfony 8 requires a minimum PHP version of 8.4.
Raw```json ⏎ {"answer": "8.4", "explanation": "Symfony 8 requires a minimum PHP version of 8.4."} ⏎ ``` | верно | Symfony 8.0 поднял требование до PHP >= 8.4.1 (в vendor проекта: "php": ">=8.4.1"). |
T28-L3 1.53 c | Symfony: versions | Symfony 7.0 kept support for docblock annotations (validation, routes). | «no» Пояснение: Symfony 7.0 removed support for docblock annotations, requiring the use of PHP attributes instead.
Raw{"answer": "no", "explanation": "Symfony 7.0 removed support for docblock annotations, requiring the use of PHP attributes instead."} | верно | Наоборот: в 7.0 аннотации удалены — только PHP-атрибуты (#[Route], #[Assert\NotBlank]). |
T28-L4 1.12 c | Symfony: versions | AssetMapper manages CSS/JS without node or webpack — via importmap.php. | «yes» Пояснение: Symfony's AssetMapper component manages CSS/JS assets using an importmap.php file and the browser's native import maps, eliminating the need for Node.js or webpack.
Raw{"answer": "yes", "explanation": "Symfony's AssetMapper component manages CSS/JS assets using an importmap.php file and the browser's native import maps, eliminating the need for Node.js or webpack."} | верно | symfony/asset-mapper (с 6.3, стандарт с 7.x); в проекте — importmap.php в корне и asset-mapper 8.1. |
T28-L5 1.26 c | Symfony: versions | Symfony 6.4 is a regular release without long-term support. | «no» Пояснение: Symfony 6.4 is actually a Long-Term Support (LTS) release, with support extending until November 2027.
Raw{"answer": "no", "explanation": "Symfony 6.4 is actually a Long-Term Support (LTS) release, with support extending until November 2027."} | верно | Наоборот: 6.4 — LTS (расширенная поддержка); LTS выходит вместе с очередным мажором (6.4 — вместе с 7.0). |
T28-L6 1.77 c | Symfony: versions | When moving to a new Symfony major version, deprecations of the previous branch keep working — major releases do not remove them. | «no» Пояснение: Symfony major releases are specifically where deprecations from the previous major version can be removed, as that's the allowed breaking change.
Raw{"answer": "no", "explanation": "Symfony major releases are specifically where deprecations from the previous major version can be removed, as that's the allowed breaking change."} | верно | Наоборот: мажорный релиз удаляет всё устаревшее (7.0 убрал деприкейшены 6.x, 8.0 — 7.x). |
T28-L7 0.76 c | Symfony: versions | Every Symfony major release is accompanied by an UPGRADE guide listing the changes. | «yes» Пояснение: Symfony has always included UPGRADE-*.md files in its repository documenting the changes between major versions.
Raw{"answer": "yes", "explanation": "Symfony has always included UPGRADE-*.md files in its repository documenting the changes between major versions."} | верно | UPGRADE-7.0.md, UPGRADE-8.0.md в репозитории symfony/symfony. |
T28-L8 1.76 c | Symfony: versions | Which Symfony component manages assets and the importmap without node/webpack? | «assetmapper» Пояснение: Symfony's AssetMapper component (introduced in 6.4/7.0) manages assets and works with ImportMaps without requiring Node.js or Webpack.
Raw{"answer": "AssetMapper", "explanation": "Symfony's AssetMapper component (introduced in 6.4/7.0) manages assets and works with ImportMaps without requiring Node.js or Webpack."} | верно | symfony/asset-mapper 8.1 — в проекте. |
T29-L1 9.73 c | Symfony: 8.2 and beyond | As of 2026-11-07, Symfony 8.2 has already been released. | «no» Пояснение: Following Symfony's 6-month release cadence, 8.0 would be released around May 2026 and 8.1 around November 2026, making 8.2 not expected until around May 2027.
Raw```json ⏎ {"answer": "no", "explanation": "Following Symfony's 6-month release cadence, 8.0 would be released around May 2026 and 8.1 around November 2026, making 8.2 not expected until around May 2027."} ⏎ ``` | верно | Наоборот: 8.2 ещё не выпущена — релиз в конце ноября 2026; последняя стабильная — 8.1. |
T29-L2 3.9 c | Symfony: 8.2 and beyond | As of 2026-11-07, Symfony 8.2 is scheduled for November 2026, following the usual six-month cycle. | «no» Пояснение: Following the six-month cycle, Symfony 8.0 would be released in November 2026, while 8.2 would be expected in November 2027.
Raw{"answer": "no", "explanation": "Following the six-month cycle, Symfony 8.0 would be released in November 2026, while 8.2 would be expected in November 2027."} | неверно верный: «yes» | Политика релизов: 8.1 — май 2026, 8.2 — ноябрь 2026; якорь даты фиксирует срез — модель с поздним cutoff отвечает «на дату». |
T29-L3 4.11 c | Symfony: 8.2 and beyond | Which Symfony version comes after 8.1 (as of 2026-11-07)? | «8.2» Пояснение: Symfony versions increment sequentially, so the version after 8.1 is 8.2.
Raw{"answer": 8.2, "explanation": "Symfony versions increment sequentially, so the version after 8.1 is 8.2."} | верно | 8.2 — следующий минорный релиз (ноябрь 2026); после его выхода проект переходит с 8.1.* на 8.2.*. |
T29-L4 1.76 c | Symfony: 8.2 and beyond | Symfony 8.2 is a major release requiring applications to be rewritten for new APIs. | «no» Пояснение: Symfony 8.2 is a minor release (major version 8, minor version 2), not a major release; major releases are indicated by the first number changing (e.g., 8.0), and even those don't typically require a full rewrite.
Raw{"answer": "no", "explanation": "Symfony 8.2 is a minor release (major version 8, minor version 2), not a major release; major releases are indicated by the first number changing (e.g., 8.0), and even those don't typically require a full rewrite."} | верно | Наоборот: 8.2 — минорный релиз; новые возможности без поломки обратной совместимости. Мажор — 9.0. |
T29-L5 2.53 c | Symfony: 8.2 and beyond | Updating within a major branch (8.1 → 8.2) should not require code changes — backward compatibility is preserved. | «yes» Пояснение: PHP's compatibility policy guarantees that minor version updates within the same major series (e.g., 8.1 → 8.2) are backward compatible, with breaking changes reserved only for major version bumps.
Raw```json ⏎ {"answer": "yes", "explanation": "PHP's compatibility policy guarantees that minor version updates within the same major series (e.g., 8.1 → 8.2) are backward compatible, with breaking changes reserved only for major version bumps."} ⏎ ``` | верно | Политика Symfony: минорные релизы обратно совместимы; BC-break допустим только в мажорных. |
T29-L6 6.16 c | Symfony: 8.2 and beyond | Which minor version of the 8.x branch is released last, before Symfony 9.0? | «8.4» Пояснение: Symfony releases minor versions every 6 months (May and November), and the last minor of each major branch is always .4, released in November alongside the next major version.
Raw```json ⏎ {"answer": "8.4", "explanation": "Symfony releases minor versions every 6 months (May and November), and the last minor of each major branch is always .4, released in November alongside the next major version."} ⏎ ``` | верно | По циклу: 8.2 (ноя 2026), 8.3 (май 2027), 8.4 (ноя 2027, вместе с 9.0) — как 6.4 выходила вместе с 7.0. |
T29-L7 2.49 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 (following the pattern of Symfony 7.x requiring PHP 8.2), not PHP 8.5.
Raw```json ⏎ {"answer": "no", "explanation": "Symfony 8.x is expected to require PHP 8.4 (following the pattern of Symfony 7.x requiring PHP 8.2), not PHP 8.5."} ⏎ ``` | верно | Наоборот: минорные релизы не поднимают требования PHP; для всей ветки 8.x остаётся PHP >= 8.4. |
T29-L8 1.9 c | Symfony: 8.2 and beyond | Deprecations added in the 8.x branch will not be removed before Symfony 9.0. | «yes» Пояснение: In Symfony, deprecations introduced in a minor version of the 8.x branch are kept throughout all 8.x releases and are only removed in the next major version, 9.0.
Raw{"answer": "yes", "explanation": "In Symfony, deprecations introduced in a minor version of the 8.x branch are kept throughout all 8.x releases and are only removed in the next major version, 9.0."} | верно | Политика: деприкейшены живут до следующего мажора; 9.0 — ноябрь 2027. |
T21-L1 1.93 c | Twig | Inside {{ }}, Twig allows calling arbitrary PHP code directly. | «no» Пояснение: Inside {{ }} Twig uses its own expression language (variables, operators, filters, built-in functions), not arbitrary PHP code.
Raw{"answer": "no", "explanation": "Inside {{ }} Twig uses its own expression language (variables, operators, filters, built-in functions), not arbitrary PHP code."} | верно | Twig — DSL: только разрешённые окружением функции/фильтры; произвольный PHP не исполняется. |
T21-L2 0.79 c | Twig | By default, Twig auto-escapes printed variables. | «yes» Пояснение: Twig enables auto-escaping by default with the 'html' strategy to prevent XSS attacks.
Raw{"answer": "yes", "explanation": "Twig enables auto-escaping by default with the 'html' strategy to prevent XSS attacks."} | верно | Autoescape включён по умолчанию; {{ '<b>' }} → <b>. Проверено на Twig 3.30. |
T21-L3 1.01 c | Twig | The Twig |e filter escapes a string for safe output in an HTML context. | «yes» Пояснение: The Twig |e (escape) filter by default escapes a string for safe HTML output, though other contexts like js, css, and url can also be specified.
Raw{"answer": "yes", "explanation": "The Twig |e (escape) filter by default escapes a string for safe HTML output, though other contexts like js, css, and url can also be specified."} | верно | |e ('html') по умолчанию; есть контексты js/url/css. От SQL-инъекций он не защищает — это задача подготовленных запросов Doctrine. |
T21-L4 1.95 c | Twig | Which filter from twig/intl-extra formats a number according to a locale? | «numberformat» Пояснение: The 'numberformat' filter in twig/intl-extra uses PHP's NumberFormatter to format a number according to a given locale.
Raw{"answer": "numberformat", "explanation": "The 'numberformat' filter in twig/intl-extra uses PHP's NumberFormatter to format 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.57 c | Twig | The |raw filter disables auto-escaping for the value. | «yes» Пояснение: The |raw filter marks a value as safe, telling the template engine (e.g., Twig) to output it without applying auto-escaping.
Raw{"answer": "yes", "explanation": "The |raw filter marks a value as safe, telling the template engine (e.g., Twig) to output it without applying auto-escaping."} | верно | {{ x|raw }} выводит HTML как есть; опасно с пользовательскими данными. Проверено на Twig 3.30. |
T21-L6 0.85 c | Twig | In Twig, {{ }} prints an expression value, while {% %} executes tags — conditions, loops, set. | «yes» Пояснение: In Twig, {{ }} outputs the result of an expression, while {% %} is used for structural tags like if, for, and set.
Raw{"answer": "yes", "explanation": "In Twig, {{ }} outputs the result of an expression, while {% %} is used for structural tags like if, for, and set."} | верно | Два блока синтаксиса Twig: вывод (echo) против логики. |
T21-L7 0.98 c | Twig | In Twig you cannot declare a variable inside a template — values only come from the controller. | «no» Пояснение: Twig allows you to declare variables inside a template using the 'set' tag, e.g. {% set foo = 'bar' %}.
Raw{"answer": "no", "explanation": "Twig allows you to declare variables inside a template using the 'set' tag, e.g. {% set foo = 'bar' %}."} | верно | {% set y = ... %} объявляет переменную в шаблоне. Проверено на Twig 3.30. |
T21-L8 0.7 c | Twig | Which Twig function dumps the debug structure of a variable (array, object)? | «dump» Пояснение: The Twig function 'dump()' is used to dump the debug structure of a variable (array, object, etc.).
Raw{"answer": "dump", "explanation": "The Twig function 'dump()' is used to dump the debug structure of a variable (array, object, etc.)."} | верно | {{ dump(x) }} (DebugExtension; в Symfony доступна в dev-окружении). |
T24-L1 1.05 c | Bootstrap | Bootstrap is a CSS/JS library of ready-made UI components, not an SPA framework. | «yes» Пояснение: Bootstrap is a front-end CSS/JS library providing pre-built UI components (navbar, modal, carousel, etc.), not an SPA framework like Angular or React.
Raw{"answer": "yes", "explanation": "Bootstrap is a front-end CSS/JS library providing pre-built UI components (navbar, modal, carousel, etc.), not an SPA framework like Angular or React."} | верно | Компоненты и утилиты поверх вашего HTML; SPA-фреймворки (React/Vue) — другой класс инструментов. В проекте vendored 5.3.3. |
T24-L2 0.96 c | Bootstrap | Which Bootstrap class gives a responsive container with a fixed max width per breakpoint? | «container» Пояснение: The .container class provides a responsive fixed-width container that adjusts its max-width at each breakpoint, while .container-fluid is full-width.
Raw{"answer": "container", "explanation": "The .container class provides a responsive fixed-width container that adjusts its max-width at each breakpoint, while .container-fluid is full-width."} | верно | .container (фиксированная макс-ширина по брейкпоинтам) vs .container-fluid (на всю ширину). |
T24-L3 1.14 c | Bootstrap | The Bootstrap grid is built on CSS floats and splits a row into 16 columns. | «no» Пояснение: The Bootstrap grid divides a row into 12 columns, not 16, and modern Bootstrap (v4+) uses Flexbox rather than CSS floats.
Raw{"answer": "no", "explanation": "The Bootstrap grid divides a row into 12 columns, not 16, and modern Bootstrap (v4+) uses Flexbox rather than CSS floats."} | верно | Наоборот: flexbox (с Bootstrap 4) и 12 колонок; float-сетка — это Bootstrap 3. |
T24-L4 1.11 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 breakpoint infixes: sm, md, lg, xl, and xxl.
Raw{"answer": "yes", "explanation": "Bootstrap 5 defines exactly five breakpoint infixes: sm, md, lg, xl, and xxl."} | верно | Тиров всего шесть: xs (без инфикса) + пять именованных (576/768/992/1200/1400 px). |
T24-L5 1.07 c | Bootstrap | Utilities like .mt-3 or .px-2 use the spacing scale: the number is a multiple of $spacer. | «yes» Пояснение: In Bootstrap, spacing utilities like .mt-3 or .px-2 multiply the $spacer variable by the number (e.g., $spacer * 3).
Raw{"answer": "yes", "explanation": "In Bootstrap, spacing utilities like .mt-3 or .px-2 multiply the $spacer variable by the number (e.g., $spacer * 3)."} | неверно верный: «no» | Spacing utilities; $spacer = 1rem. |
T24-L6 0.82 c | Bootstrap | Which Bootstrap 5 data attribute enables an interactive component (e.g. dropdown) on an element? | «data-bs-toggle» Пояснение: In Bootstrap 5, the data-bs-toggle attribute is used to enable interactive components such as dropdowns, tooltips, popovers, and collapse 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, tooltips, popovers, and collapse on an element."} | верно | data-bs-toggle="dropdown" и т.п.; в Bootstrap 4 атрибут назывался data-toggle. |
T24-L7 0.74 c | Bootstrap | Bootstrap 5 components work without jQuery — in plain vanilla JS. | «yes» Пояснение: Bootstrap 5 dropped its jQuery dependency and all its interactive components are built with vanilla JavaScript.
Raw{"answer": "yes", "explanation": "Bootstrap 5 dropped its jQuery dependency and all its interactive components are built with vanilla JavaScript."} | верно | jQuery удалён в Bootstrap 5.0: data-bs-* атрибуты и JS API. В проекте vendored 5.3.3. |
T24-L8 0.98 c | Bootstrap | Dark mode in Bootstrap is enabled with a .dark class on the root element. | «no» Пояснение: In Bootstrap 5, dark mode is enabled by adding the data-bs-theme="dark" attribute to the <html> element, not a .dark class.
Raw{"answer": "no", "explanation": "In Bootstrap 5, dark mode is enabled by adding the data-bs-theme=\"dark\" attribute to the <html> element, not a .dark class."} | верно | Наоборот: тема включается атрибутом data-bs-theme="dark" (Color modes, с 5.3); класса .dark не существует. В проекте 5.3.3. |
T14-L1 1.14 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 at runtime; you must use migrations or the schema-tool to create/update the database schema.
Raw{"answer": "no", "explanation": "Doctrine ORM does not auto-create tables at runtime; you must use migrations or the schema-tool to create/update the database schema."} | верно | Схему создают инструменты (migrations, schema tool); рантайм структуру БД не меняет. |
T14-L2 0.74 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 without executing SQL; the INSERT is deferred until flush() is called.
Raw{"answer": "persist", "explanation": "EntityManager::persist() marks a new entity as managed without executing SQL; the INSERT is deferred until flush() is called."} | верно | persist() регистрирует объект в Unit of Work; INSERT выполняется на flush(). |
T14-L3 2.35 c | Doctrine | In Doctrine ORM 3, the EntityManager::merge() method exists and makes the passed object managed. | «no» Пояснение: EntityManager::merge() returns a new managed copy of the entity; the originally passed object remains detached, not managed.
Raw```json ⏎ {"answer": "no", "explanation": "EntityManager::merge() returns a new managed copy of the entity; the originally passed object remains detached, not managed."} ⏎ ``` | верно | В ORM 3 merge() удалён (в vendor проекта 3.7.6 метода нет); в Doctrine 2.x merge() возвращал управляемую копию. Версия зафиксирована — ORM 3. |
T14-L4 0.94 c | Doctrine | DQL queries are written in terms of entities and their fields, not tables and columns. | «yes» Пояснение: DQL (Doctrine Query Language) is designed to query entities and their mapped fields, abstracting away the underlying database tables and columns.
Raw{"answer": "yes", "explanation": "DQL (Doctrine Query Language) is designed to query entities and their mapped fields, abstracting away the underlying database tables and columns."} | верно | Doctrine транслирует DQL в SQL; docs — DQL (Doctrine Query Language). |
T14-L5 0.79 c | Doctrine | What does $repository->find(999) return when no record with id 999 exists? | «null» Пояснение: Doctrine's repository find() method returns null when no entity with the given ID exists in the database.
Raw{"answer": "null", "explanation": "Doctrine's repository find() method returns null when no entity with the given ID exists in the database."} | верно | find() возвращает null, если объект не найден (docs Repository methods). |
T14-L6 1.72 c | Doctrine | DoctrineBundle in Symfony automatically calls flush() at the end of every request. | «no» Пояснение: DoctrineBundle does not automatically call flush() at the end of a request; you must explicitly call $entityManager->flush() in your code.
Raw{"answer": "no", "explanation": "DoctrineBundle does not automatically call flush() at the end of a request; you must explicitly call $entityManager->flush() in your code."} | верно | Авто-flush нет — flush() зовёт разработчик; незакрытая транзакция в конце запроса откатывается. |
T14-L7 1.57 c | Doctrine | For a managed entity, changing a property is enough: flush() commits the change without an explicit persist() — the Unit of Work tracks changes. | «yes» Пояснение: The Unit of Work performs dirty checking on all managed entities before flush(), so any property change on a managed entity is automatically detected and committed without needing an explicit persist() call.
Raw{"answer": "yes", "explanation": "The Unit of Work performs dirty checking on all managed entities before flush(), so any property change on a managed entity is automatically detected and committed without needing an explicit persist() call."} | верно | Dirty checking сравнивает снимки свойств; persist нужен только новым/отсоединённым объектам. |
T14-L8 0.95 c | Doctrine | remove() executes the SQL DELETE immediately, without waiting for flush(). | «no» Пояснение: In Doctrine ORM, remove() only marks the entity for deletion in the UnitOfWork; the actual SQL DELETE is executed when flush() is called.
Raw{"answer": "no", "explanation": "In Doctrine ORM, remove() only marks 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 1.12 c | PostgreSQL | PostgreSQL uses MVCC, therefore readers block writers and writers block readers. | «no» Пояснение: MVCC in PostgreSQL ensures that readers do NOT block writers and writers do NOT block readers, as each transaction sees its own snapshot of the data.
Raw{"answer": "no", "explanation": "MVCC in PostgreSQL ensures that readers do NOT block writers and writers do NOT block readers, as each transaction sees its own snapshot of the data."} | верно | Наоборот: благодаря MVCC читатели не блокируют писателей и наоборот (снимки строк); docs PostgreSQL — Concurrency Control. |
T15-L2 0.65 c | PostgreSQL | Which SQL command shows a query's execution plan without executing the query? | «explain» Пояснение: The EXPLAIN command in SQL shows the query execution plan without actually executing the query.
Raw{"answer": "EXPLAIN", "explanation": "The EXPLAIN command in SQL shows the query execution plan without actually executing the query."} | верно | EXPLAIN без ANALYZE только строит план; проверено на PostgreSQL 17.7. |
T15-L3 3.02 c | PostgreSQL | SERIAL and GENERATED ... AS IDENTITY are just two names for the same mechanism. | «no» Пояснение: SERIAL is a shortcut that creates a separate sequence and sets a column default, while GENERATED AS IDENTITY creates a true identity column with distinct SQL-standard semantics (e.g., OVERRIDING SYSTEM VALUE); they are related but different mechanisms.
Raw{"answer": "no", "explanation": "SERIAL is a shortcut that creates a separate sequence and sets a column default, while GENERATED AS IDENTITY creates a true identity column with distinct SQL-standard semantics (e.g., OVERRIDING SYSTEM VALUE); they are related but different mechanisms."} | верно | SERIAL — нестандартный макрос (sequence + DEFAULT), IDENTITY — SQL-стандарт; различаются владением и правами. Оба есть в PG 17 (проверено). |
T15-L4 1.58 c | PostgreSQL | By default, a PostgreSQL UNIQUE constraint allows only one row with NULL in the column. | «no» Пояснение: By default, PostgreSQL treats NULLs as distinct in UNIQUE constraints, so multiple rows can have NULL in the column.
Raw```json ⏎ {"answer": "no", "explanation": "By default, PostgreSQL treats NULLs as distinct in UNIQUE constraints, so multiple rows can have NULL in the column."} ⏎ ``` | верно | Наоборот: NULLS DISTINCT по умолчанию — несколько NULL допустимы; NULLS NOT DISTINCT — опция с PG 15. Проверено на PG 17.7. |
T15-L5 0.41 c | PostgreSQL | Which PostgreSQL aggregate function concatenates strings with a separator? | «string_agg» Пояснение: string_agg(expression, delimiter) is the PostgreSQL aggregate function that concatenates strings with a specified separator.
Raw{"answer": "string_agg", "explanation": "string_agg(expression, delimiter) is the PostgreSQL aggregate function that concatenates strings with a specified separator."} | верно | string_agg(значение, разделитель); проверено на PostgreSQL 17.7. |
T15-L6 1.27 c | PostgreSQL | Plain VACUUM returns the space occupied by dead tuples to the operating system. | «no» Пояснение: Plain VACUUM only marks space as reusable for future inserts within the same table; it does not return the space to the operating system (that requires VACUUM FULL).
Raw{"answer":"no","explanation":"Plain VACUUM only marks space as reusable for future inserts within the same table; it does not return the space to the operating system (that requires VACUUM FULL)."} | верно | VACUUM помечает место для переиспользования внутри таблицы; ОС его возвращает только VACUUM FULL (с эксклюзивной блокировкой). |
T15-L7 0.7 c | PostgreSQL | Which keyword in a window function definition partitions rows into groups the function is computed over? | «partition by» Пояснение: The PARTITION BY clause in a window function divides rows into groups over which the function is computed, similar to GROUP BY but without collapsing rows.
Raw{"answer": "PARTITION BY", "explanation": "The PARTITION BY clause in a window function divides rows into groups over which the function is computed, similar to GROUP BY but without collapsing rows."} | верно | OVER (PARTITION BY ...); проверено на PostgreSQL 17.7. |
T15-L8 1.42 c | PostgreSQL | The READ COMMITTED isolation level protects against non-repeatable reads. | «no» Пояснение: READ COMMITTED only prevents dirty reads; it does not protect against non-repeatable reads, which are prevented by REPEATABLE READ or higher.
Raw{"answer": "no", "explanation": "READ COMMITTED only prevents dirty reads; it does not protect against non-repeatable reads, which are prevented by REPEATABLE READ or higher."} | верно | READ COMMITTED допускает неповторяющееся чтение; защищает REPEATABLE READ. Проверено: SHOW transaction_isolation → read committed. |
T17-L1 0.69 c | PostgreSQL: transactions and indexes | By default, PostgreSQL wraps each single SQL statement in its own implicit transaction (autocommit). | «yes» Пояснение: By default, PostgreSQL runs in autocommit mode, where each SQL statement is automatically committed upon completion as its own implicit transaction.
Raw{"answer": "yes", "explanation": "By default, PostgreSQL runs in autocommit mode, where each SQL statement is automatically committed upon completion as its own implicit transaction."} | верно | Без BEGIN каждый оператор коммитится сам; docs PostgreSQL — Transactions. Проверено на PG 17. |
T17-L2 0.44 c | PostgreSQL: transactions and indexes | Which SQL command ends a transaction, committing all its changes? | «commit» Пояснение: The COMMIT SQL command permanently saves all changes made during the current transaction.
Raw{"answer": "COMMIT", "explanation": "The COMMIT SQL command permanently saves all changes made during the current transaction."} | верно | COMMIT (END — синоним). Проверено на PG 17. |
T17-L3 0.89 c | PostgreSQL: transactions and indexes | Indexes speed up more than SELECT: UPDATE and DELETE with a search on an indexed column benefit too. | «yes» Пояснение: Indexes speed up not only SELECT queries but also UPDATE and DELETE operations that filter on indexed columns, as the database can quickly locate the target rows.
Raw{"answer": "yes", "explanation": "Indexes speed up not only SELECT queries but also UPDATE and DELETE operations that filter on indexed columns, as the database can quickly locate the target rows."} | верно | Поиск строк для изменения идёт по индексу; docs PostgreSQL — Indexes. |
T17-L4 1.17 c | PostgreSQL: transactions and indexes | To roll back part of the statements inside a transaction, PostgreSQL uses SAVEPOINT. | «yes» Пояснение: SAVEPOINT allows you to roll back to a specific point within a transaction without aborting the entire transaction, effectively undoing only the statements after that savepoint.
Raw{"answer": "yes", "explanation": "SAVEPOINT allows you to roll back to a specific point within a transaction without aborting the entire transaction, effectively undoing only the statements after that savepoint."} | верно | SAVEPOINT name; ROLLBACK TO name — частичный откат без отмены всей транзакции. Проверено на PG 17. |
T17-L5 1.04 c | PostgreSQL: transactions and indexes | EXPLAIN ANALYZE shows the query plan without executing the query. | «no» Пояснение: EXPLAIN ANALYZE actually executes the query to gather real execution statistics, whereas plain EXPLAIN only shows the plan without executing.
Raw{"answer": "no", "explanation": "EXPLAIN ANALYZE actually executes the query to gather real execution statistics, whereas plain EXPLAIN only shows the plan without executing."} | верно | Наоборот: ANALYZE реально выполняет запрос (с побочными эффектами!) и показывает фактические времена узлов; план без выполнения — plain EXPLAIN. |
T17-L6 0.7 c | PostgreSQL: transactions and indexes | Which PostgreSQL extension adds vector types and indexes for embedding search? | «pgvector» Пояснение: pgvector is the PostgreSQL extension that adds vector types and indexes (IVFFlat, HNSW) for similarity search with embeddings.
Raw{"answer": "pgvector", "explanation": "pgvector is the PostgreSQL extension that adds vector types and indexes (IVFFlat, HNSW) for similarity search with embeddings."} | верно | CREATE EXTENSION vector (проект pgvector; в проекте образ pgvector/pgvector:pg17). |
T17-L7 0.91 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 stores index entries for rows that satisfy the specified condition, reducing index size and improving performance for queries targeting those rows.
Raw{"answer": "yes", "explanation": "A partial index (CREATE INDEX ... WHERE ...) only stores index entries for rows that satisfy the specified condition, reducing index size and improving performance for queries targeting those rows."} | верно | docs PostgreSQL — Partial Indexes; типичный кейс — индекс по «активным» записям. |
T17-L8 2.45 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 does not lock read rows but instead detects write-skew conflicts at commit time.
Raw{"answer": "no", "explanation": "PostgreSQL implements SERIALIZABLE using Serializable Snapshot Isolation (SSI), which does not lock read rows but instead detects write-skew conflicts at commit time."} | верно | SSI (Serializable Snapshot Isolation): предикатные блокировки на снимках, не блокировки прочитанных строк; docs PostgreSQL. |
T19-L1 0.75 c | HTTP and REST API | HTTP status 201 means the request resulted in a new resource being created. | «yes» Пояснение: HTTP 201 'Created' is the standard status code indicating that a new resource has been successfully created as a result of the request.
Raw{"answer": "yes", "explanation": "HTTP 201 'Created' is the standard status code indicating that a new resource has been successfully created as a result of the request."} | верно | 201 Created; обычно на POST, часто с Location; RFC 9110. |
T19-L2 1.04 c | HTTP and REST API | Which HTTP status means a successful request with an empty response body (e.g. after DELETE)? | «204» Пояснение: 204 No Content indicates a successful request with an empty response body, commonly returned after DELETE operations.
Raw{"answer": 204, "explanation": "204 No Content indicates a successful request with an empty response body, commonly returned after DELETE operations."} | верно | 204 No Content; RFC 9110. |
T19-L3 5.88 c | HTTP and REST API | The DELETE method is idempotent per the HTTP specification: repeating the request for the same resource does not change the outcome. | «yes» Пояснение: Per the HTTP specification (RFC 9110), DELETE is considered idempotent: repeating the same DELETE request has the same effect as a single request, as the resource is already removed after the first call.
Raw{"answer": "yes", "explanation": "Per the HTTP specification (RFC 9110), DELETE is considered idempotent: repeating the same DELETE request has the same effect as a single request, as the resource is already removed after the first call."} | верно | RFC 9110: DELETE идемпотентен (как PUT); идемпотентность ≠ безопасность — ресурс удаляется при первом вызове. |
T19-L4 1.06 c | HTTP and REST API | The Access-Control-Allow-Origin header is sent by the client so that the server agrees to accept requests from another origin. | «no» Пояснение: The Access-Control-Allow-Origin header is sent by the server (in the response) to indicate which origins are allowed to access the resource, not by the client.
Raw{"answer": "no", "explanation": "The Access-Control-Allow-Origin header is sent by the server (in the response) to indicate which origins are allowed to access the resource, not by the client."} | верно | Наоборот: заголовок шлёт СЕРВЕР в ответе, разрешая браузеру cross-origin запрос (CORS); в проекте nelmio/cors-bundle. |
T19-L5 0.85 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 defined in RFC 6585 specifically for rate limiting, indicating the client has sent too many requests in a given time frame.
Raw{"answer": "yes", "explanation": "HTTP 429 Too Many Requests is defined in RFC 6585 specifically for rate limiting, indicating the client has sent too many requests in a given time frame."} | верно | 429 (+ Retry-After); RFC 6585. В проекте symfony/rate-limiter. |
T19-L6 0.78 c | HTTP and REST API | 5xx codes mean a client error, while 4xx means a server-side error. | «no» Пояснение: It's the opposite: 4xx codes indicate client errors and 5xx codes indicate server-side errors.
Raw{"answer": "no", "explanation": "It's the opposite: 4xx codes indicate client errors and 5xx codes indicate server-side errors."} | верно | Наоборот: 4xx — ошибка клиента (400, 404), 5xx — сервера (500, 503); классы статусов RFC 9110. |
T19-L7 0.37 c | HTTP and REST API | Which HTTP header indicates the MIME type of the request or response body? | «content-type» Пояснение: The Content-Type header specifies the MIME type of the request or response body.
Raw{"answer": "Content-Type", "explanation": "The Content-Type header specifies the MIME type of the request or response body."} | верно | Content-Type: application/json и т.п. |
T19-L8 1.31 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 in general, while PUT is idempotent by definition per RFC 7231.
Raw{"answer": "yes", "explanation": "RFC 5789 explicitly states that PATCH is not idempotent in general, while PUT is idempotent by definition per RFC 7231."} | верно | RFC 5789 прямо оговаривает: PATCH не гарантированно идемпотентен; PUT идемпотентен. |
T20-L1 1.25 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; the correct approach is hash_equals() which performs a constant-time comparison.
Raw{"answer": "no", "explanation": "Using == is vulnerable to timing attacks; the correct approach is hash_equals() which performs a constant-time comparison."} | верно | Нужна постоянновременная проверка (password_verify) — timing-атаки; соль и алгоритм уже внутри хеша. |
T20-L2 0.97 c | Security and OAuth | A CSRF token is issued by the server (bound to the session) and verified server-side on unsafe requests (POST etc.). | «yes» Пояснение: CSRF tokens are generated server-side, tied to the user's session, and validated by the server on state-changing requests like POST, PUT, or DELETE.
Raw{"answer": "yes", "explanation": "CSRF tokens are generated server-side, tied to the user's session, and validated by the server on state-changing requests like POST, PUT, or DELETE."} | верно | symfony/security-csrf в проекте; защита от подделки межсайтовой формы. |
T20-L3 0.61 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 configure a CSP for a web page.
Raw{"answer": "Content-Security-Policy", "explanation": "The Content-Security-Policy HTTP header is used to configure a CSP for a web page."} | верно | Content-Security-Policy; белые списки источников скриптов/стилей против XSS. |
T20-L4 1.75 c | Security and OAuth | OAuth 2.0 is an authentication protocol: the access token tells you who the user is. | «no» Пояснение: OAuth 2.0 is an authorization framework, not an authentication protocol; the access token represents a set of permissions/scopes rather than user identity (that's OpenID Connect's role via the ID token).
Raw{"answer": "no", "explanation": "OAuth 2.0 is an authorization framework, not an authentication protocol; the access token represents a set of permissions/scopes rather than user identity (that's OpenID Connect's role via the ID token)."} | верно | OAuth 2.0 — авторизация/делегирование доступа; аутентификацию добавляет OpenID Connect. В проекте knpuniversity/oauth2-client-bundle (yandex/github/google). |
T20-L5 1.87 c | Security and OAuth | XSS is prevented by validating input on the server before writing it to the database. | «no» Пояснение: XSS is primarily prevented by context-aware output encoding when rendering data in the browser, not by input validation before storing it in the database.
Raw{"answer": "no", "explanation": "XSS is primarily prevented by context-aware output encoding when rendering data in the browser, not by input validation before storing it in the database."} | верно | XSS лечится контекстным экранированием НА ВЫВОДЕ (Twig autoescape, CSP); валидация ввода не покрывает все контексты вывода. |
T20-L6 1.12 c | Security and OAuth | In the OAuth 2.0 authorization code flow, which parameter arrives at the redirect_uri and is exchanged for an access token? | «code» Пояснение: In the OAuth 2.0 authorization code flow, the 'code' parameter is returned to the redirect_uri and is exchanged for an access token at the token endpoint.
Raw{"answer": "code", "explanation": "In the OAuth 2.0 authorization code flow, the 'code' parameter is returned to the redirect_uri and is exchanged for an access token at the token endpoint."} | верно | Параметр code; обмен на токен POST-ом на /token с client_secret. |
T20-L7 0.78 c | Security and OAuth | A refresh token lives longer than an access token and allows obtaining a new access token without the user logging in again. | «yes» Пояснение: Refresh tokens are designed to have a longer expiration than access tokens and are used to silently obtain new access tokens without requiring the user to re-authenticate.
Raw{"answer": "yes", "explanation": "Refresh tokens are designed to have a longer expiration than access tokens and are used to silently obtain new access tokens without requiring the user to re-authenticate."} | верно | Стандартная схема OAuth/OIDC: короткий access + длинный refresh. |
T20-L8 1.51 c | Security and OAuth | A password salt must be kept secret: without it the hash cannot be verified. | «no» Пояснение: A salt does not need to be secret; it is typically stored alongside the hash (e.g., embedded in bcrypt) so that the correct hash can be recomputed for verification.
Raw{"answer": "no", "explanation": "A salt does not need to be secret; it is typically stored alongside the hash (e.g., embedded in bcrypt) so that the correct hash can be recomputed for verification."} | верно | Соль хранится открыто (password_hash включает её в строку хеша); секретность соли не нужна. |
T18-L1 1.87 c | Testing: PHPUnit | PHPUnit runs test methods of any class — extending TestCase is not required. | «no» Пояснение: PHPUnit identifies test classes by checking that they extend PHPUnit\Framework\TestCase; without it, the class is not recognized as a test class.
Raw{"answer": "no", "explanation": "PHPUnit identifies test classes by checking that they extend PHPUnit\\Framework\\TestCase; without it, the class is not recognized as a test class."} | верно | Тестом считается метод класса, наследующего TestCase (PHPUnit 10). |
T18-L2 0.7 c | Testing: PHPUnit | In PHPUnit, setUp() runs once before all tests of the class. | «no» Пояснение: setUp() runs before each test method; setUpBeforeClass() is the static method that runs once before all tests in the class.
Raw{"answer": "no", "explanation": "setUp() runs before each test method; setUpBeforeClass() is the static method that runs once before all tests in the class."} | верно | setUp() — перед КАЖДЫМ тестом; один раз на класс — setUpBeforeClass(). Проверено живым счётчиком на PHPUnit 10.5. |
T18-L3 1.34 c | Testing: PHPUnit | A data provider lets a test run with exactly one set of arguments. | «no» Пояснение: A data provider allows a test to run with multiple (one or more) sets of arguments, not exactly one.
Raw{"answer": "no", "explanation": "A data provider allows a test to run with multiple (one or more) sets of arguments, not exactly one."} | верно | Наоборот: наборов может быть сколько угодно — тест выполняется по разу на каждый. Проверено на PHPUnit 10.5 (#[DataProvider]). |
T18-L4 0.74 c | Testing: PHPUnit | Which PHPUnit method declares an expectation that an exception of a given class is thrown? | «expectexception» Пояснение: In PHPUnit, $this->expectException(ClassName::class) is used to declare that an exception of the specified class is expected to be thrown.
Raw{"answer": "expectException", "explanation": "In PHPUnit, $this->expectException(ClassName::class) is used to declare that an exception of the specified class is expected to be thrown."} | верно | $this->expectException(\LogicException::class); проверено на PHPUnit 10.5. |
T18-L5 1.11 c | Testing: PHPUnit | In PHPUnit, a stub verifies which methods were called on it, while a mock only returns data. | «no» Пояснение: It's the opposite: a stub returns predefined data, while a mock verifies which methods were called (and can also return data).
Raw{"answer": "no", "explanation": "It's the opposite: a stub returns predefined data, while a mock verifies which methods were called (and can also return data)."} | верно | Наоборот: стаб подставляет данные, мок проверяет взаимодействия (createStub/createMock); docs PHPUnit — Test Doubles. |
T18-L6 0.97 c | Testing: PHPUnit | In PHPUnit 10+, the recommended way to pass data to a test is the #[DataProvider] attribute (the @dataProvider annotation is deprecated). | «yes» Пояснение: In PHPUnit 10+, the #[DataProvider] attribute is the recommended replacement for the deprecated @dataProvider doc-comment annotation.
Raw{"answer": "yes", "explanation": "In PHPUnit 10+, the #[DataProvider] attribute is the recommended replacement for the deprecated @dataProvider doc-comment annotation."} | верно | Аннотация ещё парсится в PHPUnit 10/11 (AnnotationParser в 10.5.66), удаление — в 12; атрибут — стандарт. |
T18-L7 0.89 c | Testing: PHPUnit | PHPUnit does not allow one test to depend on the result of another. | «no» Пояснение: PHPUnit supports test dependencies via the @depends annotation or the depends() method, allowing one test to receive the return value of another.
Raw{"answer": "no", "explanation": "PHPUnit supports test dependencies via the @depends annotation or the depends() method, allowing one test to receive the return value of another."} | верно | Зависимости есть: #[Depends] — зависимый тест не запустится, еслиProducer упал. |
T18-L8 1.19 c | Testing: PHPUnit | Which PHPUnit command-line option makes tests run in random order? | «--order-by=random» Пояснение: PHPUnit's --order-by=random option shuffles the test execution order randomly.
Raw{"answer": "--order-by=random", "explanation": "PHPUnit's --order-by=random option shuffles the test execution order randomly."} | верно | --order-by=random (PHPUnit 9+); опция есть в --help PHPUnit 10.5 (проектная). |
T01-L9 3.84 c | Syntax and operators | What does this code output?
```php
echo intdiv(7, 2) . intdiv(-7, 2);
``` | «3-3» Пояснение: intdiv(7,2) returns 3 and intdiv(-7,2) returns -3 (truncation toward zero), concatenated as string '3-3'.
Raw{"answer": "3-3", "explanation": "intdiv(7,2) returns 3 and intdiv(-7,2) returns -3 (truncation toward zero), concatenated as string '3-3'."} | верно | intdiv truncates toward zero: intdiv(-7, 2) = -3, not -4. |
T01-L10 0.89 c | Syntax and operators | What does this code output?
```php
echo -3 ** 2;
``` | «-9» Пояснение: In PHP, the exponentiation operator ** has higher precedence than unary minus, so -3 ** 2 is parsed as -(3**2) = -9.
Raw{"answer": -9, "explanation": "In PHP, the exponentiation 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 1.9 c | Types and comparisons | What does this code output?
```php
echo '1e1' == '10' ? 'true' : 'false';
``` | «false» Пояснение: In PHP, comparing two strings with == performs a string comparison, and '1e1' and '10' are different strings, so the result is false.
Raw{"answer": "false", "explanation": "In PHP, comparing two strings with == performs a string comparison, and '1e1' and '10' are different strings, so the result is false."} | неверно верный: «true» | Both strings are numeric — compared as numbers: 10 == 10. |
T02-L10 3.1 c | Types and comparisons | What does this code output?
```php
switch ('a') {
case 0: echo 'zero'; break;
default: echo 'other';
}
``` | «zero» Пояснение: In PHP 8, comparing a non-numeric string to an integer casts the string to int, so 'a' == 0 is true, matching case 0.
Raw{"answer": "zero", "explanation": "In PHP 8, comparing a non-numeric string to an integer casts the string to int, so 'a' == 0 is true, matching case 0."} | неверно верный: «other» | PHP 8: 'a' == 0 → false (used to be true) — default fires. |
T03-L9 1.94 c | Strings | What does this code output?
```php
echo strtr('abc', ['a' => '1', 'ab' => '2']);
``` | «2c» Пояснение: strtr with an array processes keys longest-first, so 'ab' is replaced with '2' first, then 'a' is searched in the remaining string '2c' but not found.
Raw{"answer": "2c", "explanation": "strtr with an array processes keys longest-first, so 'ab' is replaced with '2' first, then 'a' is searched in the remaining string '2c' but not found."} | верно | strtr with an array prefers the longest matching key. |
T03-L10 2.09 c | Strings | What does this code output?
```php
echo '[' . substr('hello', -10) . ']';
``` | «[]» Пояснение: substr('hello', -10) returns an empty string because the offset -10 goes beyond the start of a 5-character string, so the result is '[]'.
Raw{"answer": "[]", "explanation": "substr('hello', -10) returns an empty string because the offset -10 goes beyond the start of a 5-character string, so the result is '[]'."} | неверно верный: «[hello]» | A negative start beyond the string is clamped to the beginning. |
T04-L9 1.35 c | Arrays | What does this code output?
```php
$a = ['k' => 1, 'n' => 2];
$b = ['k' => 9, 'm' => 3];
echo implode(',', array_keys($a + $b));
``` | «k,n,m» Пояснение: The + operator merges arrays keeping left-side values for duplicate keys, resulting in keys k, n, m.
Raw{"answer": "k,n,m", "explanation": "The + operator merges arrays keeping left-side values for duplicate keys, resulting in keys k, n, m."} | верно | The + operator: on duplicate string keys the left array wins. |
T04-L10 2.61 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» Пояснение: Sorting by the third element gives [2,'y',1], [1,'x',2], [3,'z',2], then array_column extracts 'y','x','z' and implode joins them into 'yxz'.
Raw{"answer": "yxz", "explanation": "Sorting by the third element gives [2,'y',1], [1,'x',2], [3,'z',2], then array_column extracts 'y','x','z' and implode joins them into 'yxz'."} | верно | Sorts are stable since 8.0: x and z keep their order on a tie. |
T05-L10 4.31 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 maps values to named parameters: $a=5, $b=1, so the result is 5-1=4.
Raw{"answer": 4, "explanation": "The spread operator with string keys maps values to named parameters: $a=5, $b=1, so the result is 5-1=4."} | верно | String keys of a spread array become named arguments. |
T05-L9 2.72 c | Functions and closures | What does this code output?
```php
class P
{
private int $v = 3;
public function g(): int { return $this->v; }
}
$p = new P;
$f = $p->g(...);
$p = null;
echo $f();
``` | «3» Пояснение: The first-class callable $p->g(...) creates a closure bound to the object, so even after $p is set to null, the closure still holds a reference to the object and $this->v is still 3.
Raw```json ⏎ {"answer": 3, "explanation": "The first-class callable $p->g(...) creates a closure bound to the object, so even after $p is set to null, the closure still holds a reference to the object and $this->v is still 3."} ⏎ ``` | верно | First-class callable syntax binds $this at creation time. |
T06-L9 1.0 c | OOP: classes and inheritance | What does this code output?
```php
class A
{
public function who(): string { return static::class; }
}
class B extends A {}
echo (new B)->who();
``` | «b» Пояснение: static::class uses late static binding and returns the class name of the instance that was called, which is B.
Raw{"answer": "B", "explanation": "static::class uses late static binding and returns the class name of the instance that was called, which is B."} | верно | Late static binding: static::class is the receiver's class. |
T06-L10 8.56 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 setter hook doubles the value (5*2=10) and assigns it to the backing value via $this->x, which bypasses the hook; reading $c->x returns the backing value 10.
Raw```json ⏎ {"answer": 10, "explanation": "The setter hook doubles the value (5*2=10) and assigns it to the backing value via $this->x, which bypasses the hook; reading $c->x returns the backing value 10."} ⏎ ``` | верно | Inside the set hook, $this->x writes the backing store (no recursion): 5*2. |
T07-L9 1.22 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.89 c | Interfaces, traits, enum | What does this code output?
```php
trait Counter
{
public static int $n = 0;
}
class CX { use Counter; }
class CY { use Counter; }
CX::$n = 1;
echo CY::$n;
``` | «0» Пояснение: Each class that uses a trait gets its own independent copy of the trait's static properties, so setting CX::$n does not affect CY::$n.
Raw{"answer": 0, "explanation": "Each class that uses a trait gets its own independent copy of the trait's static properties, so setting CX::$n does not affect CY::$n."} | верно | A trait's static property is copied into each consuming class. |
T08-L10 1.26 c | Exceptions and errors | What does this code output?
```php
function f(): int
{
try { return 1; } finally { return 2; }
}
echo f();
``` | «2» Пояснение: In PHP, a return statement in a finally block overrides the return value from the try block, so the function returns 2.
Raw{"answer": 2, "explanation": "In PHP, a return statement in a finally block overrides the return value from the try block, so the function returns 2."} | верно | A return in finally overrides the return from try. |
T08-L9 1.39 c | Exceptions and errors | What does this code output?
```php
try {
try {
throw new RuntimeException('first');
} finally {
throw new LogicException('second');
}
} catch (LogicException $e) {
echo $e->getMessage();
}
``` | «second» Пояснение: Throwing a new exception in a finally block replaces the original exception, so the LogicException('second') propagates and is caught by the outer catch.
Raw{"answer": "second", "explanation": "Throwing a new exception in a finally block replaces the original exception, so the LogicException('second') propagates and is caught by the outer catch."} | верно | An exception from finally replaces the in-flight one — the last thrown is caught. |
T09-L9 1.51 c | Namespaces and autoloading | What does this code output?
```php
namespace N;
use App\Foo as Baz;
echo Baz::class . '|' . \Baz::class;
``` | «app\foo|baz» Пояснение: Baz::class resolves to the aliased App\Foo, while \Baz::class references the global namespace's Baz which has no alias, so it just outputs Baz.
Raw{"answer": "App\\Foo|Baz", "explanation": "Baz::class resolves to the aliased App\\Foo, while \\Baz::class references the global namespace's Baz which has no alias, so it just outputs Baz."} | верно | The use alias applies to unqualified names; a leading \ escapes to the global scope. |
T09-L10 1.78 c | Namespaces and autoloading | What does this code output?
```php
namespace Ns;
class Foo {}
$c = 'Foo';
echo (class_exists($c) ? 'yes' : 'no')
. (class_exists(__NAMESPACE__ . '\\' . $c) ? 'yes' : 'no');
``` | «noyes» Пояснение: class_exists('Foo') looks for a global class Foo (not found), while class_exists('Ns\Foo') finds the namespaced class Foo that was defined.
Raw{"answer": "noyes", "explanation": "class_exists('Foo') looks for a global class Foo (not found), while class_exists('Ns\\Foo') finds the namespaced class Foo that was defined."} | верно | Dynamic names are not resolved against the namespace — 'Foo' is the global class. |
T10-L9 1.46 c | References and scope | What does this code output?
```php
$a = [1, 2, 3];
foreach ($a as &$v) {}
$v = 99;
echo implode(',', $a);
``` | «1,2,99» Пояснение: After foreach by reference, $v is still a reference to the last element, so $v=99 modifies $a[2].
Raw{"answer": "1,2,99", "explanation": "After foreach by reference, $v is still a reference to the last element, so $v=99 modifies $a[2]."} | верно | After a by-ref foreach, $v remains a reference to the last element. |
T10-L10 1.81 c | References and scope | What does this code output?
```php
class A
{
public function inc(): int
{
static $n = 0;
return ++$n;
}
}
class B extends A {}
$a = new A;
$b = new B;
$a->inc();
$b->inc();
echo $a->inc();
``` | «3» Пояснение: Static variables in PHP methods are shared across the class hierarchy (parent and child share the same static variable), so each call increments the same counter: 1, 2, 3.
Raw{"answer": 3, "explanation": "Static variables in PHP methods are shared across the class hierarchy (parent and child share the same static variable), so each call increments the same counter: 1, 2, 3."} | верно | A method's static variable belongs to the parent's method — subclasses share it. |
T11-L9 1.42 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 $x=10, then return $x+1 returns 11, which getReturn() retrieves.
Raw{"answer": 11, "explanation": "send(10) assigns $x=10, then return $x+1 returns 11, which getReturn() retrieves."} | верно | 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 inner's yields (1, 2) to the caller and assigns inner's return value ('ok') to $r, which is then yielded as the third value.
Raw{"answer": "1,2,ok", "explanation": "yield from delegates inner's yields (1, 2) to the caller and assigns inner's return value ('ok') to $r, which is then yielded as the third value."} | неверно верный: «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.42 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 check returns false (cost 4 matches cost 4), outputting 'no'; the second returns true (cost 4 doesn't match cost 5), outputting 'yes'.
Raw{"answer": "noyes", "explanation": "The first check returns false (cost 4 matches cost 4), outputting 'no'; the second returns true (cost 4 doesn't match cost 5), outputting 'yes'."} | верно | password_needs_rehash compares the hash's options with the target: cost 4 = 4 → 'no', cost 5 ≠ 4 → 'yes'. |
T12-L10 6.18 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) was removed from E_ALL, so the bitwise AND yields 0, selecting 'strict-out'.
Raw{"answer": "strict-out", "explanation": "In PHP 8.5, E_STRICT (2048) was removed from E_ALL, so the bitwise AND yields 0, selecting 'strict-out'."} | верно | Since PHP 8.4, E_STRICT is out of E_ALL: the 2048 bit is unset → 'strict-out' (2048 is the historical E_STRICT bit). |
T13-L9 1.88 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 converts underscores to hyphens, so HTTP_X_TOKEN becomes X-Token and matches the get() call.
Raw{"answer": "mapped", "explanation": "Symfony's HeaderBag strips the HTTP_ prefix and converts underscores to hyphens, so HTTP_X_TOKEN becomes X-Token and matches the get() call."} | верно | 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.06 c | Symfony | What does this code output?
```php
use Symfony\Component\EventDispatcher\EventDispatcher;
use Symfony\Contracts\EventDispatcher\Event;
$d = new EventDispatcher();
$out = '';
$d->addListener('e', function () use (&$out) { $out .= 'B'; }, 10);
$d->addListener('e', function () use (&$out) { $out .= 'A'; });
$d->addListener('e', function () use (&$out) { $out .= 'C'; }, 5);
$d->dispatch(new Event(), 'e');
echo $out;
``` | «bca» Пояснение: Listeners execute in descending priority order: 10 (B), 5 (C), 0 (A).
Raw{"answer": "BCA", "explanation": "Listeners execute in descending priority order: 10 (B), 5 (C), 0 (A)."} | верно | Listeners run by descending priority: 10 (B), 5 (C), 0 (A). |
T14-L10 2.06 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 UnitOfWork identity map ensures that find() returns the same managed instance for a given identifier, so $a and $b are the same object.
Raw```json ⏎ {"answer": "same", "explanation": "Doctrine ORM's UnitOfWork identity map ensures that find() returns the same managed instance for a given identifier, so $a and $b are the same object."} ⏎ ``` | верно | Identity map: a second find for the same id returns the same instance. |
T14-L9 4.63 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 both persisted (new) and removed before flush, Doctrine's UnitOfWork cancels the insert — it removes the entity from the new-entities collection and does not issue an INSERT, so the table remains empty.
Raw```json ⏎ {"answer": 0, "explanation": "When an entity is both persisted (new) and removed before flush, Doctrine's UnitOfWork cancels the insert — it removes the entity from the new-entities collection and does not issue an INSERT, so the table remains empty."} ⏎ ``` | верно | The unit of work schedules INSERT at flush: remove after persist cancels it. |
T15-L10 0.76 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 non-NULL values in column x, so it returns 1 (only the value 1 is counted, NULL is excluded).
Raw{"answer": 1, "explanation": "COUNT(x) counts non-NULL values in column x, so it returns 1 (only the value 1 is counted, NULL is excluded)."} | верно | count(column) skips NULLs; count(*) would return 2. |
T15-L9 1.68 c | PostgreSQL | What does this SQL query return (PostgreSQL 17)?
```sql
CREATE TEMP TABLE t (id int, x int);
INSERT INTO t VALUES (1, 10), (2, 20), (3, 30);
SELECT string_agg(s::text, ',' ORDER BY id) FROM (
SELECT id, sum(x) OVER (ORDER BY id) AS s FROM t
) q;
``` | «10,30,60» Пояснение: The window function sum(x) OVER (ORDER BY id) produces a running sum (10, 30, 60), and string_agg concatenates them in id order.
Raw```json ⏎ {"answer": "10,30,60", "explanation": "The window function sum(x) OVER (ORDER BY id) produces 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 3.68 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 MessageBus dispatches through middleware in array order, so Trace('M1') echoes 'M1' first, then calls the next middleware Trace('M2') which echoes 'M2' before delegating to the final handler.
Raw{"answer": "M1M2", "explanation": "The MessageBus dispatches through middleware in array order, so Trace('M1') echoes 'M1' first, then calls the next middleware Trace('M2') which echoes 'M2' before delegating to the final handler."} | верно | The first-added middleware runs first (outermost). |
T16-L10 2.09 c | Symfony: Messenger | What does this code output?
```php
use Symfony\Component\Messenger\MessageBus;
use Symfony\Component\Messenger\Middleware\HandleMessageMiddleware;
use Symfony\Component\Messenger\Handler\HandlersLocator;
use Symfony\Component\Messenger\Handler\HandlerDescriptor;
use Symfony\Component\Messenger\Envelope;
class Ping {}
$n = 0;
$d1 = new HandlerDescriptor(function (Ping $m) use (&$n) { $n += 1; }, ['alias' => 'h1']);
$d2 = new HandlerDescriptor(function (Ping $m) use (&$n) { $n += 10; }, ['alias' => 'h2']);
$bus = new MessageBus([
new HandleMessageMiddleware(new HandlersLocator([Ping::class => [$d1, $d2]])),
]);
$bus->dispatch(new Envelope(new Ping()));
echo $n;
``` | «11» Пояснение: HandleMessageMiddleware calls all handlers registered for the message type, so both closures execute: $n += 1 then $n += 10, giving 11.
Raw```json ⏎ {"answer": 11, "explanation": "HandleMessageMiddleware calls all handlers registered for the message type, so both closures execute: $n += 1 then $n += 10, giving 11."} ⏎ ``` | верно | All registered handlers of the message run: 1 + 10 = 11. |
T17-L9 1.26 c | PostgreSQL: transactions and indexes | What does this SQL query return (PostgreSQL 17)?
```sql
CREATE TEMP TABLE t (a int);
CREATE UNIQUE INDEX ON t (a);
INSERT INTO t VALUES (1) ON CONFLICT DO NOTHING;
INSERT INTO t VALUES (1) ON CONFLICT DO NOTHING;
SELECT count(*) FROM t;
``` | «1» Пояснение: The first INSERT succeeds, the second is skipped due to the unique index conflict with ON CONFLICT DO NOTHING, so the table contains only one row.
Raw{"answer": 1, "explanation": "The first INSERT succeeds, the second is skipped due to the unique index conflict with ON CONFLICT DO NOTHING, so the table contains only one row."} | верно | ON CONFLICT DO NOTHING skips the duplicate: one insert. |
T17-L10 1.76 c | PostgreSQL: transactions and indexes | What does this sequence of psql commands output?
```sql
BEGIN;
CREATE TEMP TABLE t (a int, UNIQUE (a) DEFERRABLE INITIALLY DEFERRED);
INSERT INTO t VALUES (1);
INSERT INTO t VALUES (1);
SELECT count(*) FROM t;
``` | «2» Пояснение: The UNIQUE constraint is DEFERRABLE INITIALLY DEFERRED, so it is not checked until transaction end, allowing both inserts to succeed and the count to be 2.
Raw```json ⏎ {"answer": 2, "explanation": "The UNIQUE constraint is DEFERRABLE INITIALLY DEFERRED, so it is not checked until transaction end, allowing both inserts to succeed and the count to be 2."} ⏎ ``` | верно | DEFERRED postpones the uniqueness check to COMMIT — count sees 2 rows. |
T18-L9 2.62 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 is a regex that matches both test_sum (3 data sets) and test_sum_abs (3 data sets), totaling 6 tests.
Raw```json ⏎ {"answer": 6, "explanation": "The --filter test_sum is a regex that matches both test_sum (3 data sets) and test_sum_abs (3 data sets), totaling 6 tests."} ⏎ ``` | верно | --filter is a substring match: test_sum also matches test_sum_abs (3+3 datasets). |
T18-L10 1.32 c | Testing: PHPUnit | How many tests will this command run, and how many of them will fail? Answer with two comma-separated numbers (ran, failed).
```php
use PHPUnit\Framework\TestCase;
use PHPUnit\Framework\Attributes\DataProvider;
final class Calc2Test extends TestCase
{
public function prov(): array
{
return [[1], [-1]];
}
#[DataProvider('prov')]
public function test_x(int $x): void
{
$this->assertTrue($x > 0);
}
}
```
Command: `phpunit Calc2Test.php` (PHPUnit 10.5) | «2, 1» Пояснение: The DataProvider returns two rows ([1] and [-1]), so 2 tests run; test_x(-1) fails because -1 > 0 is false.
Raw{"answer": "2, 1", "explanation": "The DataProvider returns two rows ([1] and [-1]), so 2 tests run; test_x(-1) fails because -1 > 0 is false."} | верно | A non-static provider is just a deprecation in PHPUnit 10: both datasets run and the [-1] dataset fails the assert — 2 ran, 1 failure. |
T19-L9 0.73 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 switches the HTTP method to POST.
Raw{"answer": "POST", "explanation": "The -d flag in curl sends data in the request body and automatically switches the HTTP method to POST."} | верно | -d/-F switches curl to POST by default. |
T19-L10 1.12 c | HTTP and REST API | Which HTTP method does this command send?
```bash
curl -s -G -d 'a=1' http://demo.local/api
``` | «get» Пояснение: The -G flag tells curl to pass the -d data as a GET query string instead of a POST body.
Raw{"answer": "GET", "explanation": "The -G flag tells curl to pass the -d data as a GET query string instead of a POST body."} | верно | -G turns -d data into the query string; the method stays GET. |
T20-L9 2.0 c | Security and OAuth | A client hits the token endpoint (RFC 6749) with a non-existent client_id. What value of the error field does the endpoint return? | «unauthorized_client» Пояснение: RFC 6749 §5.2 specifies that when the client is not recognized (e.g., non-existent client_id), the token endpoint returns the error 'unauthorized_client'.
Raw{"answer": "unauthorized_client", "explanation": "RFC 6749 §5.2 specifies that when the client is not recognized (e.g., non-existent client_id), the token endpoint returns the error 'unauthorized_client'."} | неверно верный: «invalid_client» | Unknown client → invalid_client (RFC 6749 §5.2). |
T20-L10 1.32 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 passed in the fragment component (the part after #) of the redirect URI.
Raw{"answer": "fragment", "explanation": "In the OAuth 2.0 implicit flow (response_type=token), the access token is passed in the fragment component (the part after #) of the redirect URI."} | верно | The implicit flow passes the token in the URL fragment (#) — it never reaches the server. |
T21-L9 2.52 c | Twig | What does this Twig template output?
```twig
{{ false|default(2) * 3 }}
``` | «0» Пояснение: false is defined and not null, so default(2) returns false; then false * 3 evaluates to 0 * 3 = 0.
Raw```json ⏎ {"answer": 0, "explanation": "false is defined and not null, so default(2) returns false; then false * 3 evaluates to 0 * 3 = 0."} ⏎ ``` | неверно верный: «6» | default replaces exactly false/null/''/[] — false becomes 2, 2*3 = 6; the naive 'default is for undefined only' yields 0. |
T21-L10 5.34 c | Twig | What exception class does render() of this template throw?
```twig
{{ 'a' ~ 1 + 2 }}
``` | «a3» Пояснение: In Twig, the + operator has higher precedence than the ~ concatenation operator, so the expression is evaluated as 'a' ~ (1+2) = 'a' ~ 3 = 'a3'.
Raw```json ⏎ {"answer": "a3", "explanation": "In Twig, the + operator has higher precedence than the ~ concatenation operator, so the expression is evaluated as 'a' ~ (1+2) = 'a' ~ 3 = 'a3'."} ⏎ ``` | неверно верный: «runtimeerror» | In Twig ~ binds tighter than +: ('a' ~ 1) + 2 → string + int → a render error (RuntimeError). |
T22-L9 2.52 c | Symfony: Security and forms | What does this code output?
```php
use Symfony\Component\Validator\Validation;
use Symfony\Component\Validator\Constraints as Assert;
$v = Validation::createValidator();
echo count($v->validate([''], [new Assert\NotBlank()]));
``` | «0» Пояснение: The array [''] is not empty (it has one element), so the NotBlank constraint passes, resulting in zero violations.
Raw{"answer": 0, "explanation": "The array [''] is not empty (it has one element), so the NotBlank constraint passes, resulting in zero violations."} | верно | NotBlank treats null, '', [] as blank — the array [''] is not blank. |
T22-L10 1.61 c | Symfony: Security and forms | What does this code output?
```php
use Symfony\Component\Form\Forms;
use Symfony\Component\Form\Extension\Core\Type\TextType;
$factory = Forms::createFormFactoryBuilder()->getFormFactory();
$form = $factory->create(TextType::class);
try {
echo $form->isValid() ? 'valid' : 'invalid';
} catch (Throwable $e) {
echo get_class($e);
}
``` | «invalid» Пояснение: A Symfony form that has never been submitted returns false from isValid(), so the ternary outputs 'invalid'.
Raw{"answer": "invalid", "explanation": "A Symfony form that has never been submitted returns false from isValid(), so the ternary outputs 'invalid'."} | неверно верный: «symfony\component\form\exception\logicexception» | isValid() on a non-submitted form throws LogicException, it does not return false. |
T23-L9 1.49 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 ContainerBuilder caches public service instances, so repeated calls to get('a') return the same object.
Raw{"answer": "same", "explanation": "Symfony's ContainerBuilder caches public service instances, so repeated calls to get('a') return the same object."} | верно | Container services are shared: two get() calls yield one instance. |
T23-L10 2.32 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 nested %param% references in parameter values, so %name% becomes Bob and %greeting% becomes 'hi Bob', yielding 'hi Bob!'.
Raw{"answer": "hi Bob!", "explanation": "During compile(), Symfony resolves nested %param% references in parameter values, so %name% becomes Bob and %greeting% becomes 'hi Bob', yielding 'hi Bob!'."} | верно | compile() resolves %-references transitively: %greeting% → 'hi %name%' → 'hi Bob!', the answer assembles over two hops. |
T24-L9 1.3 c | Bootstrap | What is the max-width of .container in Bootstrap 5.3 at a 992px viewport? | «960» Пояснение: At the lg breakpoint (min-width: 992px), Bootstrap 5.3 sets .container max-width to 960px.
Raw{"answer": 960, "explanation": "At the lg breakpoint (min-width: 992px), Bootstrap 5.3 sets .container max-width to 960px."} | верно | 5.x container widths: 540/720/960/1140/1320 (sm–xxl); 992 → 960px. |
T24-L10 4.73 c | Bootstrap | Which utility sets the text color in Bootstrap 5.3 for `<p class="text-danger text-primary">…</p>`? Answer with the winning class name. | «text-danger» Пояснение: In Bootstrap 5.3's generated CSS, text-danger appears after text-primary in the stylesheet (order: primary, secondary, success, danger...), so with equal specificity the later rule wins.
Raw```json ⏎ {"answer": "text-danger", "explanation": "In Bootstrap 5.3's generated CSS, text-danger appears after text-primary in the stylesheet (order: primary, secondary, success, danger...), so with equal specificity the later rule wins."} ⏎ ``` | верно | Specificity ties — the later rule wins: text-danger is declared after text-primary. |
T25-L9 1.18 c | Clean architecture | Layers: Domain, Application, Infrastructure. Deptrac rules: Application → Domain; Infrastructure → Domain, Application; Domain → Domain only.
How many violations will deptrac report for this class?
```php
namespace App\Domain;
use App\Application\PlaceOrder;
use App\Infrastructure\Db;
class OrderService
{
public function __construct(
private PlaceOrder $handler,
private Db $db,
) {}
}
``` | «2» Пояснение: The Domain layer can only depend on Domain, but this class imports from Application (PlaceOrder) and Infrastructure (Db), giving 2 violations.
Raw```json ⏎ {"answer": 2, "explanation": "The Domain layer can only depend on Domain, but this class imports from Application (PlaceOrder) and Infrastructure (Db), giving 2 violations."} ⏎ ``` | верно | Domain may depend only on Domain: PlaceOrder (Application) + Db (Infrastructure) = 2. |
T25-L10 1.3 c | Clean architecture | Layers: Domain, Application, Infrastructure. Deptrac rules: Application → Domain; Infrastructure → Domain, Application; Domain → Domain only.
How many violations will deptrac report for this class?
```php
namespace App\Domain;
use App\Application\PlaceOrder;
use App\Infrastructure\Db;
class BillingService
{
public function __construct(
private PlaceOrder $handler,
private Db $db,
private \App\Infrastructure\Logger $logger,
) {}
}
``` | «3» Пояснение: BillingService is in the Domain layer, which may only depend on Domain, but it depends on Application (PlaceOrder) and Infrastructure (Db, Logger), giving 3 violations.
Raw{"answer": 3, "explanation": "BillingService is in the Domain layer, which may only depend on Domain, but it depends on Application (PlaceOrder) and Infrastructure (Db, Logger), giving 3 violations."} | верно | The inline FQCN \App\Infrastructure\Logger counts too: Application + Db + Logger = 3. |
T26-L10 1.29 c | DDD | What does this code output?
```php
final class Money
{
public function __construct(public readonly int $amount) {}
public function add(Money $o): Money
{
return new self($this->amount + $o->amount);
}
}
$a = new Money(10);
$c = $a->add(new Money(5));
echo $a->amount . ',' . $c->amount;
``` | «10,15» Пояснение: $a has amount 10, and $c is a new Money object created 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 created 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.26 c | DDD | What does this code output?
```php
final class Order
{
private array $items = [];
public function add(string $sku): void
{
$this->items[$sku] = true;
}
public function count(): int
{
return count($this->items);
}
public function remove(string $sku): void
{
if (count($this->items) === 1) {
throw new DomainException('last item');
}
unset($this->items[$sku]);
}
}
$o = new Order;
$o->add('a');
try {
$o->remove('a');
} catch (DomainException) {
}
echo $o->count();
``` | «1» Пояснение: The remove() method throws a DomainException before unsetting the item, so the item remains in the array and count() still returns 1.
Raw{"answer": 1, "explanation": "The remove() method throws a DomainException before unsetting the item, so the item remains in the array and count() still returns 1."} | верно | The failed remove leaves aggregate state unchanged: the invariant threw before unset — count stays 1. |
VC-L9 3.66 c | PHP 8.4–8.5 | What does this code output on PHP 8.5?
```php
class C
{
public function hi(): string { return 'hi'; }
}
echo new C()->hi();
``` | «hi» Пояснение: The code instantiates class C, calls its hi() method which returns the string 'hi', and echoes it.
Raw{"answer": "hi", "explanation": "The code instantiates class C, calls its hi() method which returns the string 'hi', and echoes it."} | верно | Since 8.4, new in a method chain works without wrapping parentheses. |
VC-L10 4.4 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 accessing $o->v, the lazy ghost is uninitialized (yes); after accessing $o->v, the initializer has been called and the object is no longer uninitialized (no).
Raw{"answer": "yesno", "explanation": "Before accessing $o->v, the lazy ghost is uninitialized (yes); after accessing $o->v, the initializer has been called and the object is no longer uninitialized (no)."} | верно | newLazyGhost (8.4): the object stays lazy until first access — reading a property initializes it and clears the flag. |
T28-L9 1.16 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 security component (Symfony\Component\Security\Guard) was removed in Symfony 7.0, so in 8.1 the class no longer exists and class_exists() returns false.
Raw{"answer": "no", "explanation": "The Guard security component (Symfony\\Component\\Security\\Guard) was removed in Symfony 7.0, so in 8.1 the class no longer exists and class_exists() returns false."} | верно | Guard authentication was removed in Symfony 7.0 — the class is gone in 8.1. |
T28-L10 1.74 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 (deprecated in 6.4), while AttributeClassLoader replaced it and exists in 8.1.
Raw```json ⏎ {"answer": "noyes", "explanation": "AnnotationClassLoader was removed in Symfony 7.0 (deprecated in 6.4), while AttributeClassLoader replaced it and exists in 8.1."} ⏎ ``` | верно | Annotation loaders were removed in 7.0; only attribute loaders remain (Annotation→Attribute). |