Пример запроса (первая клетка). System одинаковый во всех запросах прогона, user — свой вопрос для каждой клетки:
| Клетка | Тема | Утверждение | Ответ |
Результат | Обоснование |
T01-L1 4.26 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 escape sequences like \n, \t, while single-quoted strings only recognize \\ and \' as escapes, so the processing is fundamentally different, not just a speed difference.
Raw{"answer": "no", "explanation": "Double-quoted strings support variable interpolation and escape sequences like \\n, \\t, while single-quoted strings only recognize \\\\ and \\' as escapes, so the processing is fundamentally different, not just a speed difference."} | верно | В двойных кавычках работают интерполяция переменных и escape-последовательности, в одинарных — нет. |
T01-L2 1.97 c | Syntax and operators | The ?? operator follows isset semantics and raises no warnings for undefined variables. | «yes» Пояснение: The null coalescing operator (??) is equivalent to isset($var) ? $var : default and does not trigger warnings or notices for undefined variables, unlike the plain ternary operator.
Raw{"answer": "yes", "explanation": "The null coalescing operator (??) is equivalent to isset($var) ? $var : default and does not trigger warnings or notices for undefined variables, unlike the plain ternary operator."} | верно | ?? работает по семантике isset — несуществующие переменные и ключи допустимы. |
T01-L3 0.7 c | Syntax and operators | What will this print: echo 'a', 'b'; | «ab» Пояснение: In PHP, echo can take multiple arguments separated by commas and concatenates them, printing 'ab'.
Raw{"answer": "ab", "explanation": "In PHP, echo can take multiple arguments separated by commas and concatenates them, printing 'ab'."} | верно | echo принимает список аргументов: ab. |
T01-L4 5.0 c | Syntax and operators | print returns the value 1 and can be used inside an expression. | «no» Пояснение: While print does return the value 1, it is a language construct (not a function), so it cannot be used inside an expression (e.g., you cannot write echo 2 * print "hello";).
Raw{"answer": "no", "explanation": "While print does return the value 1, it is a language construct (not a function), so it cannot be used inside an expression (e.g., you cannot write echo 2 * print \"hello\";)."} | неверно верный: «yes» | print — выражение со значением 1, в отличие от echo, который значения не возвращает. |
T01-L5 1.41 c | Syntax and operators | The ?: (elvis) operator returns its left operand when it is falsy. | «no» Пояснение: The elvis operator (?:) returns the left operand when it is truthy, and the right operand (default) when it is falsy.
Raw{"answer": "no", "explanation": "The elvis operator (?:) returns the left operand when it is truthy, and the right operand (default) when it is falsy."} | верно | Наоборот: $a ?: $b возвращает $a, если он истинный, иначе $b. |
T01-L6 3.53 c | Syntax and operators | In PHP 8, the concatenation operator (.) has lower precedence than addition and subtraction. | «yes» Пояснение: In PHP's operator precedence table, the concatenation operator (.) ranks below + and -, so arithmetic is evaluated before concatenation.
Raw{"answer": "yes", "explanation": "In PHP's operator precedence table, the concatenation operator (.) ranks below + and -, so arithmetic is evaluated before concatenation."} | верно | С PHP 8 (RFC concat precedence) '.' имеет приоритет ниже арифметики: 'сумма: ' . 2 + 3 → 'сумма: 5' (в PHP 7 было иначе). |
T01-L7 0.94 c | Syntax and operators | The expression 2 ** 3 ** 2 in PHP evaluates as (2 ** 3) ** 2, that is, 64. | «no» Пояснение: In PHP, the ** operator is right-associative, so 2 ** 3 ** 2 evaluates as 2 ** (3 ** 2) = 2 ** 9 = 512, not 64.
Raw{"answer": "no", "explanation": "In PHP, the ** operator is right-associative, so 2 ** 3 ** 2 evaluates as 2 ** (3 ** 2) = 2 ** 9 = 512, not 64."} | верно | ** право-ассоциативен: 2 ** (3 ** 2) = 2 ** 9 = 512. |
T01-L8 2.0 c | Syntax and operators | What string will this print: echo 'sum: ' . 2 + 3; (PHP 8)? | «3» Пояснение: Concatenation '.' has higher precedence than '+', so it parses as ('sum: ' . 2) + 3, which becomes 'sum: 2' + 3; the non-numeric string casts to 0, yielding 0 + 3 = 3.
Raw{"answer": 3, "explanation": "Concatenation '.' has higher precedence than '+', so it parses as ('sum: ' . 2) + 3, which becomes 'sum: 2' + 3; the non-numeric string casts to 0, yielding 0 + 3 = 3."} | неверно верный: «sum: 5» | Парная к verify-клетке про приоритет: 'сумма: 5'. |
T02-L1 1.75 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 and same types; only == ignores order.
Raw{"answer": "no", "explanation": "With ===, arrays must have the same key/value pairs in the same order and same types; only == ignores order."} | верно | === для массивов требует совпадения и значений, и их порядка. |
T02-L2 1.29 c | Types and comparisons | The comparison 0 == false returns false because it is a strict comparison. | «no» Пояснение: 0 == false returns true (not false), and == is a loose (non-strict) comparison, not a strict one.
Raw{"answer": "no", "explanation": "0 == false returns true (not false), and == is a loose (non-strict) comparison, not a strict one."} | верно | Наоборот: == — нестрогое сравнение и возвращает true; строгое — это === (0 === false → false). |
T02-L3 2.51 c | Types and comparisons | In PHP 8, the expression "abc" == 0 returns true. | «no» Пояснение: In PHP 8, a non-numeric string like "abc" is compared as a string, so 0 is cast to "0" and "abc" != "0", yielding false.
Raw{"answer": "no", "explanation": "In PHP 8, a non-numeric string like \"abc\" is compared as a string, so 0 is cast to \"0\" and \"abc\" != \"0\", yielding false."} | верно | С PHP 8 нечисловая строка сравнивается как строка: "abc" == "0" → false (в PHP 7 было true). |
T02-L4 0.86 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.26 c | Types and comparisons | What does the expression (int) '42abc' return? | «42» Пояснение: PHP casts a string to int by reading the numeric prefix from the left until it hits a non-numeric character, so '42abc' becomes 42.
Raw{"answer": 42, "explanation": "PHP casts a string to int by reading the numeric prefix from the left until it hits a non-numeric character, so '42abc' becomes 42."} | верно | Ведущая числовая часть: 42, без ошибок и warning. |
T02-L6 0.82 c | Types and comparisons | What does the expression '5' + 5 return? | «10» Пояснение: In PHP, the numeric string '5' is coerced to integer 5, so 5 + 5 equals 10.
Raw{"answer": 10, "explanation": "In PHP, the numeric string '5' is coerced to integer 5, so 5 + 5 equals 10."} | верно | Числовая строка приводится: int 10. |
T02-L7 1.1 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"; it is 0 (integer) that becomes "0" when cast to string.
Raw{"answer": "no", "explanation": "In PHP, casting false to a string results in an empty string \"\", not \"0\"; it is 0 (integer) that becomes \"0\" when cast to string."} | верно | false → "", true → "1". |
T02-L8 1.94 c | Types and comparisons | The comparison 0.1 + 0.2 === 0.3 returns false. | «yes» Пояснение: Due to floating-point precision, 0.1 + 0.2 evaluates to 0.30000000000000004, which is not strictly equal to 0.3, so === returns false.
Raw{"answer": "yes", "explanation": "Due to floating-point precision, 0.1 + 0.2 evaluates to 0.30000000000000004, which is not strictly equal to 0.3, so === returns false."} | верно | Двоичная погрешность float: 0.1 + 0.2 = 0.30000000000000004. |
T03-L1 1.5 c | Strings | strrev() correctly reverses a UTF-8 string. | «no» Пояснение: strrev() reverses a string byte-by-byte, which corrupts multi-byte UTF-8 characters; mb_strrev() or similar is needed for proper UTF-8 reversal.
Raw{"answer": "no", "explanation": "strrev() reverses a string byte-by-byte, which corrupts multi-byte UTF-8 characters; mb_strrev() or similar is needed for proper UTF-8 reversal."} | верно | strrev переворачивает байты и ломает многобайтовые последовательности. |
T03-L2 0.78 c | Strings | str_contains('Hello world', 'world') returns true. | «yes» Пояснение: str_contains() checks if the needle 'world' exists within the haystack 'Hello world', which it does, so it returns true.
Raw{"answer": "yes", "explanation": "str_contains() checks if the needle 'world' exists within the haystack 'Hello world', which it does, so it returns true."} | верно | str_contains с PHP 8.0 проверяет вхождение подстроки. |
T03-L3 1.06 c | Strings | str_pad() can pad a string on the right side only. | «no» Пояснение: str_pad() can pad on the right, left, or both sides via the pad_type parameter (STR_PAD_RIGHT, STR_PAD_LEFT, STR_PAD_BOTH).
Raw{"answer": "no", "explanation": "str_pad() can pad on the right, left, or both sides via the pad_type parameter (STR_PAD_RIGHT, STR_PAD_LEFT, STR_PAD_BOTH)."} | верно | STR_PAD_LEFT / STR_PAD_BOTH меняют сторону дополнения. |
T03-L4 1.17 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"), not just spaces.
Raw{"answer": "no", "explanation": "By default, trim() strips spaces, tabs, newlines, carriage returns, null bytes, and vertical tabs (\" \\t\\n\\r\\0\\x0B\"), not just spaces."} | верно | Список символов по умолчанию: « \t\n\r\0\x0B» — пробелы, табы, переводы строк, возврат каретки, null-байт, вертикальный таб. Проверено php -r. |
T03-L5 1.19 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) while 'h', 'l', 'l', 'o' are each 1 byte, giving a total of 6 bytes.
Raw{"answer": 6, "explanation": "In UTF-8, 'é' is encoded as 2 bytes (0xC3 0xA9) while 'h', 'l', 'l', 'o' are each 1 byte, giving a total of 6 bytes."} | верно | 6 букв по 2 байта: 12. |
T03-L6 0.97 c | Strings | What does substr('abcdef', -3) return? | «def» Пояснение: substr with a negative start position (-3) begins 3 characters from the end of the string, returning the last 3 characters 'def'.
Raw{"answer": "def", "explanation": "substr with a negative start position (-3) begins 3 characters from the end of the string, returning the last 3 characters 'def'."} | верно | Отрицательное смещение — с конца: def. |
T03-L7 1.02 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 (PHP strings are passed by value).
Raw{"answer": "no", "explanation": "ucfirst() returns a new string with the first character uppercased; it does not modify the original string in place (PHP strings are passed by value)."} | верно | Строки неизменяемы; ucfirst возвращает новую строку. |
T03-L8 1.08 c | Strings | Variable interpolation works in heredoc but not in nowdoc. | «yes» Пояснение: Heredoc supports variable interpolation (like double-quoted strings), while nowdoc (quoted delimiter) treats the content as a single-quoted string, so variables are not interpolated.
Raw{"answer": "yes", "explanation": "Heredoc supports variable interpolation (like double-quoted strings), while nowdoc (quoted delimiter) treats the content as a single-quoted string, so variables are not interpolated."} | верно | Nowdoc — «одинарные кавычки» в тройном синтаксисе: текст как есть. |
T04-L1 0.92 c | Arrays | The sort() function preserves the key-to-value association of the array. | «no» Пояснение: PHP's sort() reindexes the array numerically and does not preserve key-to-value associations; asort() is the function that does.
Raw{"answer": "no", "explanation": "PHP's sort() reindexes the array numerically and does not preserve key-to-value associations; asort() is the function that does."} | верно | sort перенумеровывает ключи; связь сохраняет asort. |
T04-L2 0.87 c | Arrays | The string key '5' in an array is stored as the integer 5. | «yes» Пояснение: In PHP, numeric string keys like '5' are automatically cast to integer 5 when used as array keys.
Raw{"answer": "yes", "explanation": "In PHP, numeric string keys like '5' are automatically cast to integer 5 when used as array keys."} | верно | Каноничные десятичные строковые ключи приводятся к int. |
T04-L3 0.9 c | Arrays | The in_array() function uses strict comparison (===) by default. | «no» Пояснение: The third parameter $strict in in_array() defaults to false, meaning it uses loose comparison (==) by default, not strict (===).
Raw{"answer": "no", "explanation": "The third parameter $strict in in_array() defaults to false, meaning it uses loose comparison (==) by default, not strict (===)."} | верно | По умолчанию сравнение нестрогое; строгое — третий аргумент true. |
T04-L4 2.47 c | Arrays | Without a callback, array_filter() removes all "empty" (falsy) elements from the array. | «yes» Пояснение: Without a callback, array_filter() removes all falsy values (false, 0, 0.0, '', '0', null, []) from the array.
Raw{"answer": "yes", "explanation": "Without a callback, array_filter() removes all falsy values (false, 0, 0.0, '', '0', null, []) from the array."} | верно | Убирает 0, "", null, false и пустые массивы. |
T04-L5 1.29 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, meaning the array is re-indexed with sequential integer keys starting at 0.
Raw{"answer": "no", "explanation": "The $preserve_keys parameter of array_slice() defaults to false, meaning the array is re-indexed with sequential integer keys starting at 0."} | верно | По умолчанию ключи перенумеровываются; сохранение — preserve_keys = true. |
T04-L6 1.15 c | Arrays | What does array_slice([10, 20, 30, 40], 1, 2) return? | «[20, 30]» Пояснение: array_slice with offset 1 and length 2 extracts elements at indices 1 and 2, which are 20 and 30.
Raw{"answer": "[20, 30]", "explanation": "array_slice with offset 1 and length 2 extracts elements at indices 1 and 2, which are 20 and 30."} | верно | [20,30]; ключи перенумеровываются. |
T04-L7 1.34 c | Arrays | How many elements will count(['a' => 1] + ['a' => 9, 'b' => 2]) return? | «2» Пояснение: The + operator keeps left-hand keys on conflict, so 'a'=>1 is preserved and 'b'=>2 is added, giving a 2-element array.
Raw{"answer": 2, "explanation": "The + operator keeps left-hand keys on conflict, so 'a'=>1 is preserved and 'b'=>2 is added, giving a 2-element array."} | верно | Оператор + : по ключу 'a' побеждает левый; итого 2. |
T04-L8 4.65 c | Arrays | Since PHP 8.1, the spread operator [...$a, ...$b] supports arrays with string keys. | «no» Пояснение: In PHP 8.1, the array spread operator in array literals only supports integer keys; spreading an array with string keys throws a TypeError.
Raw{"answer": "no", "explanation": "In PHP 8.1, the array spread operator in array literals only supports integer keys; spreading an array with string keys throws a TypeError."} | неверно верный: «yes» | В 8.0 — только числовые ключи; 8.1 снял ограничение. |
T05-L1 4.06 c | Functions and closures | Named arguments cannot be combined with argument unpacking ...$args in a single call. | «no» Пояснение: PHP does allow combining named arguments with argument unpacking (...$args) in the same function call, as long as the rules about argument ordering are respected.
Raw{"answer": "no", "explanation": "PHP does allow combining named arguments with argument unpacking (...$args) in the same function call, as long as the rules about argument ordering are respected."} | верно | Можно: f(...$args, имя: значение). Нельзя только позиционный аргумент после распаковки. |
T05-L2 1.47 c | Functions and closures | An anonymous function without use sees variables from the outer scope. | «no» Пояснение: In PHP, a closure (anonymous function) has its own scope and cannot access outer variables unless they are explicitly imported with the `use` keyword.
Raw{"answer": "no", "explanation": "In PHP, a closure (anonymous function) has its own scope and cannot access outer variables unless they are explicitly imported with the `use` keyword."} | верно | Без use внешние переменные недоступны; авто-захват только у fn. |
T05-L3 1.46 c | Functions and closures | What will func_num_args() return inside function f($a) { return func_num_args(); } when called as f(1, 2, 3)? | «3» Пояснение: func_num_args() returns the number of arguments actually passed to the function call, regardless of the number of declared parameters, so f(1, 2, 3) passes 3 arguments.
Raw{"answer": 3, "explanation": "func_num_args() returns the number of arguments actually passed to the function call, regardless of the number of declared parameters, so f(1, 2, 3) passes 3 arguments."} | верно | Считает переданные аргументы: 3. |
T05-L4 1.56 c | Functions and closures | The body of an arrow function fn may consist of several expressions in curly braces. | «no» Пояснение: An arrow function (fn) in PHP has a single-expression body introduced by '=>' and does not use curly braces; multiple statements require a regular closure with a block body.
Raw{"answer": "no", "explanation": "An arrow function (fn) in PHP has a single-expression body introduced by '=>' and does not use curly braces; multiple statements require a regular closure with a block body."} | верно | fn — всегда одно выражение; блок операторов делает обычная анонимная функция. |
T05-L5 1.85 c | Functions and closures | An arrow function fn captures outer variables by reference (lazily, at use time). | «no» Пояснение: PHP arrow functions (fn) automatically capture outer variables by value at the point of definition, not by reference and not lazily at use time.
Raw{"answer": "no", "explanation": "PHP arrow functions (fn) automatically capture outer variables by value at the point of definition, not by reference and not lazily at use time."} | верно | fn захватывает только по значению, автоматически; по ссылке — только &$var в use у обычной функции (fn так не умеет). |
T05-L6 1.02 c | Functions and closures | A closure declared as static function () {} does not capture $this. | «yes» Пояснение: A static closure in PHP is not bound to the current object, so $this is not available inside it.
Raw{"answer": "yes", "explanation": "A static closure in PHP is not bound to the current object, so $this is not available inside it."} | верно | static-замыкание отвязано от объекта: $this внутри недоступен. |
T05-L7 1.31 c | Functions and closures | What will this print: $x = 5; $f = function () use ($x) { return $x; }; $x = 7; echo $f(); | «5» Пояснение: The closure captures $x by value (not by reference) at the time of definition, so it retains the original value of 5 even after $x is reassigned to 7.
Raw{"answer": 5, "explanation": "The closure captures $x by value (not by reference) at the time of definition, so it retains the original value of 5 even after $x is reassigned to 7."} | верно | use захватывает по значению в момент создания: 5. |
T05-L8 1.2 c | Functions and closures | In weak typing mode (without strict_types), passing the string "5" to an int parameter is allowed. | «yes» Пояснение: In PHP's default weak typing mode (without declare(strict_types=1)), the string "5" is automatically coerced to the integer 5 when passed to an int parameter, so it is allowed.
Raw{"answer": "yes", "explanation": "In PHP's default weak typing mode (without declare(strict_types=1)), the string \"5\" is automatically coerced to the integer 5 when passed to an int parameter, so it is allowed."} | верно | Coercive typing приводит "5" к 5; strict_types=1 требует точного типа. |
T06-L1 1.09 c | OOP: classes and inheritance | PHP supports constructor property promotion: public function __construct(private int $x) {}. | «yes» Пояснение: PHP 8.0 introduced constructor property promotion, allowing properties to be declared directly in constructor parameters with visibility modifiers and types.
Raw{"answer": "yes", "explanation": "PHP 8.0 introduced constructor property promotion, allowing properties to be declared directly in constructor parameters with visibility modifiers and types."} | верно | С PHP 8.0 параметр с модификатором создаёт свойство и присваивание. |
T06-L2 0.6 c | OOP: classes and inheritance | Which keyword prevents a method from being overridden in subclasses? | «final» Пояснение: In PHP, the 'final' keyword before a method declaration prevents that method from being overridden in subclasses.
Raw{"answer": "final", "explanation": "In PHP, the 'final' keyword before a method declaration prevents that method from being overridden in subclasses."} | верно | final. |
T06-L3 0.67 c | OOP: classes and inheritance | A method declared final cannot be overridden in a subclass. | «yes» Пояснение: In PHP, the final keyword prevents a method from being overridden in any subclass.
Raw{"answer": "yes", "explanation": "In PHP, the final keyword prevents a method from being overridden in any subclass."} | верно | final запрещает переопределение метода и наследование класса. |
T06-L4 0.74 c | OOP: classes and inheritance | Parent properties with private visibility are accessible in a subclass. | «no» Пояснение: In PHP, private properties are only accessible within the class that declares them and are not visible to subclasses (unlike protected properties).
Raw{"answer": "no", "explanation": "In PHP, private properties are only accessible within the class that declares them and are not visible to subclasses (unlike protected properties)."} | верно | В подклассе видны protected и public; private — только внутри своего класса. |
T06-L5 4.19 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 are named 'class@anonymous' followed by a NUL byte and the file path/line number, so the part before the NUL byte is 'class@anonymous'.
Raw{"answer": "class@anonymous", "explanation": "Anonymous classes in PHP are named 'class@anonymous' followed by a NUL byte and the file path/line number, so the part before the NUL byte is 'class@anonymous'."} | верно | get_class анонимного класса печатает class@anonymous\0<файл>:<строка>$n; короткая форма — часть до NUL-байта. Проверено php -r (hex). |
T06-L6 1.47 c | OOP: classes and inheritance | A private parent method is not part of the inheritance contract: a child may declare a method with the same name and any visibility. | «yes» Пояснение: In PHP, private methods are not visible to child classes, so a child can freely redeclare a method with the same name at any visibility level without conflict.
Raw{"answer": "yes", "explanation": "In PHP, private methods are not visible to child classes, so a child can freely redeclare a method with the same name at any visibility level without conflict."} | верно | private-члены не наследуются — правила совместимости подписей не действуют. |
T06-L7 1.35 c | OOP: classes and inheritance | The magic method __get() is called only for non-existent properties. | «no» Пояснение: __get() is also called for inaccessible (private or protected) properties, not only for non-existent ones.
Raw{"answer": "no", "explanation": "__get() is also called for inaccessible (private or protected) properties, not only for non-existent ones."} | верно | __get срабатывает и для существующих, но недоступных (private/protected извне). |
T06-L8 1.52 c | OOP: classes and inheritance | What does reassigning a readonly property throw — Exception or Error? | «error» Пояснение: Reassigning a readonly property in PHP throws an \Error (not an \Exception), with a message like 'readonly property … may not be written'.
Raw{"answer": "Error", "explanation": "Reassigning a readonly property in PHP throws an \\Error (not an \\Exception), with a message like 'readonly property … may not be written'."} | верно | Error (readonly с 8.1); оговорка: в __clone() переинициализация допустима (8.3+). |
T07-L1 1.0 c | Interfaces, traits, enum | An interface can declare constants. | «yes» Пояснение: PHP interfaces can declare constants (since PHP 5.0), which are implicitly public and final, and can be accessed via the interface name.
Raw{"answer": "yes", "explanation": "PHP interfaces can declare constants (since PHP 5.0), which are implicitly public and final, and can be accessed via the interface name."} | верно | Константы интерфейса наследуются реализациями. |
T07-L2 0.67 c | Interfaces, traits, enum | Which operator checks whether an object is an instance of a class or interface? | «instanceof» Пояснение: In PHP, the 'instanceof' operator checks whether an object is an instance of a particular class or implements a particular interface.
Raw{"answer": "instanceof", "explanation": "In PHP, the 'instanceof' operator checks whether an object is an instance of a particular class or implements a particular interface."} | верно | instanceof. |
T07-L3 1.62 c | Interfaces, traits, enum | An interface can declare static methods. | «yes» Пояснение: PHP interfaces can declare static (abstract) methods, which implementing classes must also define as static.
Raw{"answer": "yes", "explanation": "PHP interfaces can declare static (abstract) methods, which implementing classes must also define as static."} | верно | Реализация обязана дать статический метод с той же сигнатурой. |
T07-L4 1.08 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 implementations, so an object can be instanceof an interface it implements.
Raw{"answer": "no", "explanation": "PHP's instanceof operator checks both class inheritance and interface implementations, so an object can be instanceof an interface it implements."} | верно | instanceof возвращает true и для интерфейсов объекта. |
T07-L5 2.08 c | Interfaces, traits, enum | An interface method may have a default implementation, like a trait method. | «no» Пояснение: In PHP, interface methods are abstract and cannot have a body/implementation, whereas trait methods can have a concrete default implementation.
Raw{"answer": "no", "explanation": "In PHP, interface methods are abstract and cannot have a body/implementation, whereas trait methods can have a concrete default implementation."} | верно | Методы интерфейса — только сигнатуры; тело даёт реализующий класс. |
T07-L6 1.01 c | Interfaces, traits, enum | An abstract method in an abstract class may have protected visibility. | «yes» Пояснение: In PHP, abstract methods can have public, protected, or final visibility; only private is disallowed.
Raw{"answer": "yes", "explanation": "In PHP, abstract methods can have public, protected, or final visibility; only private is disallowed."} | верно | В абстрактном классе — любая видимость; в интерфейсе — только public. |
T07-L7 0.83 c | Interfaces, traits, enum | How many elements will Foo::cases() return for enum Foo { case A; case B; case C; }? | «3» Пояснение: Enum::cases() returns an array containing all defined cases, and Foo has three cases: A, B, and C.
Raw{"answer": 3, "explanation": "Enum::cases() returns an array containing all defined cases, and Foo has three cases: A, B, and C."} | верно | Статический метод cases(): 3. |
T07-L8 2.3 c | Interfaces, traits, enum | A trait can declare constants. | «yes» Пояснение: Since PHP 8.3, traits can declare constants, which can be accessed via the class that uses the trait.
Raw{"answer": "yes", "explanation": "Since PHP 8.3, traits can declare constants, which can be accessed via the class that uses the trait."} | верно | С PHP 8.2 трейты могут объявлять константы (RFC constants_in_traits); до 8.2 — нет. |
T08-L1 0.64 c | Exceptions and errors | The Throwable interface is a common ancestor of both Exception and Error. | «yes» Пояснение: In PHP 7+, the Throwable interface is implemented by both Exception and Error, making it their common ancestor.
Raw{"answer": "yes", "explanation": "In PHP 7+, the Throwable interface is implemented by both Exception and Error, making it their common ancestor."} | верно | Иерархия с PHP 7: Throwable → Exception и Throwable → Error. |
T08-L2 1.64 c | Exceptions and errors | A catch (Exception $e) block will also catch TypeError, because TypeError ultimately inherits from Exception. | «no» Пояснение: In PHP, TypeError extends Error (not Exception); both Exception and Error implement Throwable, so catching Exception does not catch TypeError.
Raw{"answer": "no", "explanation": "In PHP, TypeError extends Error (not Exception); both Exception and Error implement Throwable, so catching Exception does not catch TypeError."} | верно | TypeError наследуется от Error; catch (Exception) его не ловит. |
T08-L3 2.1 c | Exceptions and errors | The @ operator suppresses exceptions too. | «no» Пояснение: The @ operator only suppresses error reporting (notices, warnings, etc.); exceptions still propagate normally unless caught by try/catch.
Raw{"answer": "no", "explanation": "The @ operator only suppresses error reporting (notices, warnings, etc.); exceptions still propagate normally unless caught by try/catch."} | верно | @ глушит диагностику (warnings/notices), исключения не перехватывает. |
T08-L4 2.72 c | Exceptions and errors | What error class does intdiv(5, 0) throw? | «arithmeticerror» Пояснение: intdiv(5, 0) throws an ArithmeticError (a subclass of Error) when the divisor is zero.
Raw{"answer": "ArithmeticError", "explanation": "intdiv(5, 0) throws an ArithmeticError (a subclass of Error) when the divisor is zero."} | неверно верный: «divisionbyzeroerror» | DivisionByZeroError (иерархия Error, не Exception); php-грейдер объективен. |
T08-L5 1.01 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, caught, or not; it always executes.
Raw{"answer": "no", "explanation": "The finally block runs regardless of whether an exception was thrown, caught, or not; it always executes."} | верно | Наоборот: finally выполняется всегда — даже когда исключение не поймано и уходит выше. Проверено php -r. |
T08-L6 5.0 c | Exceptions and errors | An exception thrown inside a finally block has no effect on the result of the try block. | «no» Пояснение: In PHP, an exception thrown in a finally block overrides the normal completion or the caught exception, so it does affect the observable result of the try-catch-finally construct.
Raw{"answer": "no", "explanation": "In PHP, an exception thrown in a finally block overrides the normal completion or the caught exception, so it does affect the observable result of the try-catch-finally construct."} | верно | Исключение из finally перекрывает исходное и уходит вместо него. |
T08-L7 1.39 c | Exceptions and errors | What does the expression (bool) new Exception('x') return? | «yes» Пояснение: In PHP, any object instance (including a new Exception) is truthy when cast to bool, so (bool) new Exception('x') returns true.
Raw{"answer": "yes", "explanation": "In PHP, any object instance (including a new Exception) is truthy when cast to bool, so (bool) new Exception('x') returns true."} | верно | Любой объект при приведении к bool — true. Формы ответа: true или да. |
T08-L8 2.68 c | Exceptions and errors | Functions registered via register_shutdown_function() run when exit is called. | «yes» Пояснение: Functions registered with register_shutdown_function() are executed during the script shutdown phase, which is triggered by exit(), normal script completion, or fatal errors.
Raw{"answer": "yes", "explanation": "Functions registered with register_shutdown_function() are executed during the script shutdown phase, which is triggered by exit(), normal script completion, or fatal errors."} | верно | exit завершает скрипт, но shutdown-функции отрабатывают. |
T09-L1 1.04 c | Namespaces and autoloading | The use App\Service\Mailer; statement itself loads the class file. | «no» Пояснение: The use statement only creates an alias at compile time; the class file is actually loaded (via autoload) when the class is first referenced.
Raw{"answer": "no", "explanation": "The use statement only creates an alias at compile time; the class file is actually loaded (via autoload) when the class is first referenced."} | верно | use — псевдоним на этапе компиляции; файл грузит автозагрузчик при первом обращении. |
T09-L2 1.18 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 via a use statement, you write 'use function Namespace\functionName;' using the keyword 'function'.
Raw{"answer": "function", "explanation": "In PHP, to import a function via a use statement, you write 'use function Namespace\\functionName;' using the keyword 'function'."} | верно | use function ...; (и use const для констант). |
T09-L3 1.56 c | Namespaces and autoloading | Into which file (path from src/) does the PSR-4 mapping "App\ → src/" place the class App\Controller\Api\UserController? | «controller/api/usercontroller.php» Пояснение: PSR-4 strips the 'App\' prefix, converts the remaining namespace separators (\) to directory separators (/), and appends .php, yielding src/Controller/Api/UserController.php.
Raw{"answer": "Controller/Api/UserController.php", "explanation": "PSR-4 strips the 'App\\' prefix, converts the remaining namespace separators (\\) to directory separators (/), and appends .php, yielding src/Controller/Api/UserController.php."} | верно | Остаток имени после префикса, \ → /. |
T09-L4 0.98 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 ClassLoader for automatic class loading.
Raw{"answer": "yes", "explanation": "Composer's vendor/autoload.php ultimately calls spl_autoload_register() to register its ClassLoader for automatic class loading."} | верно | Composer ставит автозагрузчик именно на spl_autoload_register. |
T09-L5 0.78 c | Namespaces and autoloading | The magic constant __NAMESPACE__ contains the name of the current namespace. | «yes» Пояснение: __NAMESPACE__ is a PHP magic constant that returns the name of the current namespace (or an empty string for the global namespace).
Raw{"answer": "yes", "explanation": "__NAMESPACE__ is a PHP magic constant that returns the name of the current namespace (or an empty string for the global namespace)."} | верно | В корневом пространстве — пустая строка. |
T09-L6 1.59 c | Namespaces and autoloading | An unqualified class name (without a leading \) in new is resolved from the global root. | «no» Пояснение: An unqualified class name in `new` is resolved relative to the current namespace, not the global root; a leading backslash is required to resolve from the global root.
Raw{"answer": "no", "explanation": "An unqualified class name in `new` is resolved relative to the current namespace, not the global root; a leading backslash is required to resolve from the global root."} | верно | Резолвится относительно текущего namespace (с учётом импортов). |
T09-L7 1.2 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 sub-namespace Model\User to the relative path Model/User.php under the base directory src/, giving src/Model/User.php.
Raw{"answer": "yes", "explanation": "PSR-4 maps the sub-namespace Model\\User to the relative path Model/User.php under the base directory src/, giving src/Model/User.php."} | верно | Остаток имени после префикса переносится в путь как есть. |
T09-L8 1.22 c | Namespaces and autoloading | A use statement may be written inside a function body — the import then applies to that function only. | «yes» Пояснение: PHP allows use statements inside a function body, and the alias/import is scoped only to that function's block.
Raw{"answer": "yes", "explanation": "PHP allows use statements inside a function body, and the alias/import is scoped only to that function's block."} | неверно верный: «no» | use внутри тела функции — parse error; импорты файловые и компиляционные. |
T10-L1 1.13 c | References and scope | Arrays are copied on assignment rather than passed by reference. | «yes» Пояснение: In PHP, arrays are copied on assignment (copy-on-write), meaning each variable holds its own independent copy rather than a reference to the same data.
Raw{"answer": "yes", "explanation": "In PHP, arrays are copied on assignment (copy-on-write), meaning each variable holds its own independent copy rather than a reference to the same data."} | верно | Присваивание массива — копия (в движке — copy-on-write). |
T10-L2 0.98 c | References and scope | What will this print: $a = [1, 2]; $b = $a; $b[] = 3; echo count($a); | «2» Пояснение: In PHP, arrays are copied by value on assignment, so modifying $b does not affect $a, which still contains [1, 2].
Raw{"answer": 2, "explanation": "In PHP, arrays are copied by value on assignment, so modifying $b does not affect $a, which still contains [1, 2]."} | верно | Присваивание — копия: в $a по-прежнему 2 элемента. |
T10-L3 0.8 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 visible inside functions unless explicitly brought in via the global keyword, $GLOBALS array, or passed as parameters.
Raw{"answer": "yes", "explanation": "In PHP, variables in the global scope are not visible inside functions unless explicitly brought in via the global keyword, $GLOBALS array, or passed as parameters."} | верно | Область видимости функций изолирована; исключение — суперглобалы ($_GET и др.). |
T10-L4 1.39 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 variable from the global scope entirely, not just for that function's scope.
Raw{"answer": "no", "explanation": "unset($GLOBALS['x']) inside a function removes the variable from the global scope entirely, not just for that function's scope."} | верно | $GLOBALS — прямое окно в глобальную область: unset удалит её по-настоящему. |
T10-L5 0.8 c | References and scope | What will this print: function inc(&$x) { $x++; } $n = 5; inc($n); echo $n; | «6» Пояснение: The function modifies $n by reference, incrementing it from 5 to 6, so echo $n prints 6.
Raw{"answer": 6, "explanation": "The function modifies $n by reference, incrementing it from 5 to 6, so echo $n prints 6."} | верно | Ссылка меняет оригинал: 6. |
T10-L6 2.68 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» Пояснение: PHP's foreach iterates over a snapshot of the array taken at the start of the loop, so adding, removing, or reordering elements inside the loop does not affect the current iteration.
Raw{"answer": "no", "explanation": "PHP's foreach iterates over a snapshot of the array taken at the start of the loop, so adding, removing, or reordering elements inside the loop does not affect the current iteration."} | верно | По значению foreach итерирует копию-снимок. |
T10-L7 1.0 c | References and scope | A static property belongs to each instance separately: changes in one object are not visible in others. | «no» Пояснение: A static property belongs to the class itself and is shared across all instances, so changes in one object are visible in others; instance (non-static) properties are the ones that belong to each object separately.
Raw{"answer": "no", "explanation": "A static property belongs to the class itself and is shared across all instances, so changes in one object are visible in others; instance (non-static) properties are the ones that belong to each object separately."} | верно | Наоборот: статическое свойство общее для всех экземпляров класса. Проверено php -r. |
T10-L8 1.3 c | References and scope | An array can have a boolean key true, and it will be stored as bool. | «no» Пояснение: In PHP, boolean keys like true are cast to integers (true becomes 1, false becomes 0) and stored as integers, not as booleans.
Raw{"answer": "no", "explanation": "In PHP, boolean keys like true are cast to integers (true becomes 1, false becomes 0) and stored as integers, not as booleans."} | верно | Булев ключ приводится к int: true → 1, false → 0. |
T11-L1 1.43 c | Generators, iterators, SPL | Inside a generator, return with a value can be used, and it becomes available via $gen->getReturn(). | «yes» Пояснение: Since PHP 5.5, a generator can use return with a value, and that value is accessible via the Generator::getReturn() method after the generator completes.
Raw{"answer": "yes", "explanation": "Since PHP 5.5, a generator can use return with a value, and that value is accessible via the Generator::getReturn() method after the generator completes."} | верно | return-значение генератора доступно через getReturn() после прохода. |
T11-L2 1.81 c | Generators, iterators, SPL | A fully consumed generator can be rewound with rewind() and traversed again. | «no» Пояснение: In PHP, generators are one-shot iterators; once fully consumed, calling rewind() throws a RuntimeException and the generator cannot be traversed again.
Raw{"answer": "no", "explanation": "In PHP, generators are one-shot iterators; once fully consumed, calling rewind() throws a RuntimeException and the generator cannot be traversed again."} | верно | Генератор одноразовый: rewind после начала итерации бросает Exception. |
T11-L3 1.83 c | Generators, iterators, SPL | The yield from construct delegates traversal to another generator or iterable. | «yes» Пояснение: The yield from construct (in Python) does indeed delegate iteration/traversal to another generator or any iterable.
Raw{"answer": "yes", "explanation": "The yield from construct (in Python) does indeed delegate iteration/traversal to another generator or any iterable."} | верно | yield from проксирует значения, ключи и return-значение внутреннего генератора. |
T11-L4 1.0 c | Generators, iterators, SPL | What does get_class(g()) return for function g() { yield 1; }? | «generator» Пояснение: Calling a generator function returns an instance of the built-in Generator class, so get_class() on it returns the string 'Generator'.
Raw{"answer": "Generator", "explanation": "Calling a generator function returns an instance of the built-in Generator class, so get_class() on it returns the string 'Generator'."} | верно | Функция с yield возвращает Generator. |
T11-L5 1.23 c | Generators, iterators, SPL | How many elements will count(iterator_to_array((function () { yield from [1, 2, 3]; })())) return? | «3» Пояснение: The generator yields 1, 2, 3 from the array [1, 2, 3], iterator_to_array converts it to a 3-element array, and count returns 3.
Raw{"answer": 3, "explanation": "The generator yields 1, 2, 3 from the array [1, 2, 3], iterator_to_array converts it to a 3-element array, and count returns 3."} | верно | yield from делегирует все 3 элемента. |
T11-L6 0.56 c | Generators, iterators, SPL | The SplStack class implements a FIFO queue. | «no» Пояснение: SplStack implements a LIFO (Last In, First Out) stack, while a FIFO queue is implemented by SplQueue.
Raw{"answer": "no", "explanation": "SplStack implements a LIFO (Last In, First Out) stack, while a FIFO queue is implemented by SplQueue."} | верно | SplStack — стек LIFO; очередь FIFO — SplQueue. |
T11-L7 0.81 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 for traversal.
Raw{"answer": "yes", "explanation": "ArrayIterator is a built-in PHP class that wraps an array and implements the Iterator interface for traversal."} | верно | Объектная обёртка над массивом. |
T11-L8 0.91 c | Generators, iterators, SPL | An ArrayObject instance cannot be traversed with foreach. | «no» Пояснение: ArrayObject implements IteratorAggregate, so it can be traversed with foreach.
Raw{"answer": "no", "explanation": "ArrayObject implements IteratorAggregate, so it can be traversed with foreach."} | верно | ArrayObject реализует IteratorAggregate — foreach по нему работает. |
T12-L1 1.1 c | Configuration and security | password_hash() generates a salt automatically — passing one separately is not needed. | «yes» Пояснение: password_hash() internally generates a random salt and embeds it in the returned hash string; there is no separate salt parameter to pass.
Raw{"answer": "yes", "explanation": "password_hash() internally generates a random salt and embeds it in the returned hash string; there is no separate salt parameter to pass."} | верно | Соль встраивается в строку результата; параметр salt устарел. |
T12-L2 1.47 c | Configuration and security | In PHP 8, PASSWORD_DEFAULT is md5 with an automatically added salt. | «no» Пояснение: In PHP 8, PASSWORD_DEFAULT is PASSWORD_BCRYPT (or PASSWORD_ARGON2ID in PHP 8.4), not MD5.
Raw{"answer": "no", "explanation": "In PHP 8, PASSWORD_DEFAULT is PASSWORD_BCRYPT (or PASSWORD_ARGON2ID in PHP 8.4), not MD5."} | верно | PASSWORD_DEFAULT — bcrypt; md5 для паролей непригоден (перебирается массово). |
T12-L3 0.87 c | Configuration and security | What does password_verify('secret', password_hash('secret', PASSWORD_DEFAULT)) return? | «yes» Пояснение: password_verify returns true when the plaintext password matches the hash, which it does here since both use 'secret'.
Raw{"answer": "yes", "explanation": "password_verify returns true when the plaintext password matches the hash, which it does here since both use 'secret'."} | верно | Соль и хеш в одной строке: true (форма ответа: true или да). |
T12-L4 0.97 c | Configuration and security | strip_tags() protects against SQL injection. | «no» Пояснение: strip_tags() removes HTML and PHP tags to help mitigate XSS, but SQL injection is prevented by prepared statements/parameterized queries, not by stripping HTML tags.
Raw{"answer": "no", "explanation": "strip_tags() removes HTML and PHP tags to help mitigate XSS, but SQL injection is prevented by prepared statements/parameterized queries, not by stripping HTML tags."} | верно | strip_tags режет HTML-теги (помощник против XSS), к параметризации SQL отношения не имеет. |
T12-L5 1.12 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, preventing an attacker from exploiting a known (fixed) session ID after a user logs in.
Raw{"answer": "yes", "explanation": "session_regenerate_id() replaces the current session ID with a new one, preventing an attacker from exploiting a known (fixed) session ID after a user logs in."} | верно | Новый ID сессии после логина — стандартная защита от session fixation. |
T12-L6 1.4 c | Configuration and security | Which built-in function returns the SAPI name (e.g., cli)? | «php_sapi_name()» Пояснение: php_sapi_name() is the built-in PHP function that returns the current SAPI module name as a string (e.g., 'cli', 'fpm-fcgi').
Raw{"answer": "php_sapi_name()", "explanation": "php_sapi_name() is the built-in PHP function that returns the current SAPI module name as a string (e.g., 'cli', 'fpm-fcgi')."} | верно | php_sapi_name(). |
T12-L7 1.24 c | Configuration and security | session_destroy() deletes session data on the server but not the cookie in the user's browser. | «yes» Пояснение: session_destroy() only removes the session data on the server; the PHPSESSID cookie in the browser must be manually expired (e.g., via setcookie) to be removed.
Raw{"answer": "yes", "explanation": "session_destroy() only removes the session data on the server; the PHPSESSID cookie in the browser must be manually expired (e.g., via setcookie) to be removed."} | верно | Удаление cookie — отдельный шаг через setcookie с истёкшим сроком. |
T12-L8 1.12 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, $_SESSION remains an empty array.
Raw{"answer": "no", "explanation": "The $_SESSION array is only populated with session data after session_start() is called; without it, $_SESSION remains an empty array."} | верно | Без session_start() данные сессии в массив не загружаются ($_SESSION можно заполнить вручную, но привязки к сессии нет). |
VC-L1 1.27 c | PHP 8.4–8.5 | In which PHP version was the array_find() function introduced? | «8.3» Пояснение: The array_find() function, which returns the first element matching a callback (similar to JavaScript's Array.find()), was introduced in PHP 8.3.
Raw{"answer": "8.3", "explanation": "The array_find() function, which returns the first element matching a callback (similar to JavaScript's Array.find()), was introduced in PHP 8.3."} | неверно верный: «8.4» | PHP 8.4 (RFC array_find). |
VC-L2 1.23 c | PHP 8.4–8.5 | Property hooks (get/set right in the property declaration) landed in PHP 8.4. | «yes» Пояснение: Property hooks (get/set/unset defined inline in a property declaration) were introduced as a major new feature in PHP 8.4.
Raw{"answer": "yes", "explanation": "Property hooks (get/set/unset defined inline in a property declaration) were introduced as a major new feature in PHP 8.4."} | верно | Property hooks — PHP 8.4 (ноябрь 2024). |
VC-L3 1.28 c | PHP 8.4–8.5 | Asymmetric visibility (public private(set) string $name) appeared in PHP 8.4. | «yes» Пояснение: PHP 8.4 introduced asymmetric visibility, allowing properties to have different read and write access levels (e.g., public private(set) string $name).
Raw{"answer": "yes", "explanation": "PHP 8.4 introduced asymmetric visibility, allowing properties to have different read and write access levels (e.g., public private(set) string $name)."} | верно | Asymmetric visibility v2 — PHP 8.4. |
VC-L4 3.16 c | PHP 8.4–8.5 | In which PHP version was the #[\NoDiscard] attribute introduced? Answer with the version number. | «8.4» Пояснение: The #[\NoDiscard] attribute was introduced in PHP 8.4 to signal that a function's return value should not be discarded by the caller.
Raw{"answer": 8.4, "explanation": "The #[\\NoDiscard] attribute was introduced in PHP 8.4 to signal that a function's return value should not be discarded by the caller."} | неверно верный: «8.5» | #[\NoDiscard] — PHP 8.5 (marking return values as important). |
VC-L5 5.57 c | PHP 8.4–8.5 | In which PHP version did the pipe operator |> first appear? Answer with the version number. | «8.4» Пояснение: The pipe operator |> was introduced in PHP 8.4 as part of the language's continued evolution with new syntactic features.
Raw{"answer": "8.4", "explanation": "The pipe operator |> was introduced in PHP 8.4 as part of the language's continued evolution with new syntactic features."} | неверно верный: «8.5» | Pipe operator — PHP 8.5 (2025). |
VC-L6 1.5 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' feature (e.g., clone $obj with ['x' => 1]) was introduced in PHP 8.4.
Raw{"answer": "8.4", "explanation": "The 'Clone with' feature (e.g., clone $obj with ['x' => 1]) was introduced in PHP 8.4."} | неверно верный: «8.5» | Clone with v2 — PHP 8.5. |
VC-L7 2.38 c | PHP 8.4–8.5 | In which PHP version were the array_first() and array_last() functions introduced? | «8.4» Пояснение: The array_first() and array_last() functions were introduced in PHP 8.4 as part of the new set of array helper functions.
Raw{"answer": "8.4", "explanation": "The array_first() and array_last() functions were introduced in PHP 8.4 as part of the new set of array helper functions."} | неверно верный: «8.5» | PHP 8.5. |
VC-L8 5.5 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.02 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 as part of the clamp_v2 RFC.
Raw{"answer": "8.4", "explanation": "The clamp() function was introduced in PHP 8.4 as part of the clamp_v2 RFC."} | неверно верный: «8.6» | По данным владельца (wiki.php.net/rfc): clamp_v2 — 8.6; clamp() в 8.5.11 отсутствует (косвенное подтверждение). Дата-якорь делает клетку монотонной. |
VF-L2 2.17 c | PHP: 8.6+ and the future | RFC Context Managers v2 has already been adopted in PHP (as of 2026-11-07). | «no» Пояснение: There is no adopted PHP RFC called 'Context Managers v2'; it appears to be a fabricated or non-existent RFC in the PHP standards process.
Raw{"answer": "no", "explanation": "There is no adopted PHP RFC called 'Context Managers v2'; it appears to be a fabricated or non-existent RFC in the PHP standards process."} | верно | На 06.11.2026 — в обсуждении (создан 2026-10-23); не принят. |
VF-L3 4.29 c | PHP: 8.6+ and the future | RFC Bound-Erased Generic Types (generics) was declined in 2026. | «yes» Пояснение: The PHP RFC for Bound-Erased Generic Types (generics) was voted down and declined, meaning PHP still lacks built-in generics support.
Raw{"answer": "yes", "explanation": "The PHP RFC for Bound-Erased Generic Types (generics) was voted down and declined, meaning PHP still lacks built-in generics support."} | верно | Голосование завершилось 2026-06-28: отклонён (wiki.php.net/rfc). |
VF-L4 3.43 c | PHP: 8.6+ and the future | As of 2026-11-07, the RFC enabling multithreading (ZTS) by default has already been accepted in PHP. | «no» Пояснение: As of late 2026, PHP has not accepted an RFC to make ZTS (Zend Thread Safe) the default build type; NTS remains the default while ZTS is available as an option.
Raw{"answer": "no", "explanation": "As of late 2026, PHP has not accepted an RFC to make ZTS (Zend Thread Safe) the default build type; NTS remains the default while ZTS is available as an option."} | верно | Такого принятого RFC нет на дату якоря; якорь делает клетку монотонной — при принятии RFC позже клетка не перевернётся. |
VF-L5 1.72 c | PHP: 8.6+ and the future | As of PHP 8.5, generics (parameterized types) are still absent. | «yes» Пояснение: PHP has never shipped engine-level generics; even as of PHP 8.5, parameterized types remain absent (only docblock @template hints exist for static analysis).
Raw{"answer": "yes", "explanation": "PHP has never shipped engine-level generics; even as of PHP 8.5, parameterized types remain absent (only docblock @template hints exist for static analysis)."} | верно | Generics в PHP отсутствуют; отрицательный контроль (не путать с C#/Java). |
VF-L6 2.87 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 an annual November release cycle; PHP 8.5 was released in November 2025 and PHP 8.6 GA is scheduled for November 19, 2026, so as of November 7, 2026, 8.5 is indeed the latest stable.
Raw{"answer": "yes", "explanation": "PHP follows an annual November release cycle; PHP 8.5 was released in November 2025 and PHP 8.6 GA is scheduled for November 19, 2026, so as of November 7, 2026, 8.5 is indeed the latest stable."} | верно | 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 the 5.x line (ending at 5.6) to 7.0 in December 2015; no PHP 6 was ever released.
Raw{"answer": "yes", "explanation": "PHP went directly from the 5.x line (ending at 5.6) to 7.0 in December 2015; no PHP 6 was ever released."} | верно | Исторический факт: ветка 6 не была релизнута. |
VF-L8 5.43 c | PHP: 8.6+ and the future | The RFC adding the #[\Deprecated] attribute to the core was adopted. | «no» Пояснение: The RFC for a built-in #[\Deprecated] attribute was proposed but was rejected (not adopted) during the PHP RFC voting process.
Raw{"answer": "no", "explanation": "The RFC for a built-in #[\\Deprecated] attribute was proposed but was rejected (not adopted) during the PHP RFC voting process."} | неверно верный: «yes» | #[\Deprecated] — принят, реализован в PHP 8.4. |
T25-L1 1.48 c | Clean architecture | The dependency rule of clean and onion architecture: inner layers know nothing about outer ones — dependencies point toward the center. | «yes» Пояснение: In Clean/Onion Architecture, the dependency rule dictates that inner layers (domain) must not depend on outer layers (framework, UI, DB); all dependencies point inward toward the core business logic.
Raw{"answer": "yes", "explanation": "In Clean/Onion Architecture, the dependency rule dictates that inner layers (domain) must not depend on outer layers (framework, UI, DB); all dependencies point inward toward the core business logic."} | верно | Чистая (Robert C. Martin), луковичная (Jeffrey Palermo) и гексагональная (ports & adapters) — варианты одной идеи: зависимости направлены внутрь, к домену. Слоями в проекте следит deptrac. |
T25-L2 1.16 c | Clean architecture | Domain entities import neither Doctrine nor Symfony — only the language and, possibly, the standard library. | «yes» Пояснение: In DDD/clean architecture, domain entities are pure PHP objects that depend only on the language and possibly the standard library, not on Doctrine or Symfony.
Raw{"answer": "yes", "explanation": "In DDD/clean architecture, domain entities are pure PHP objects that depend only on the language and possibly the standard library, not on Doctrine or Symfony."} | верно | Изоляция домена от инфраструктуры; deptrac в проекте как раз следит за слоями. |
T25-L3 1.72 c | Clean architecture | Controllers and Twig templates belong to the business-logic layer because they are the ones calling use cases. | «no» Пояснение: Controllers and Twig templates belong to the presentation/view layer; the fact that they call use cases makes them clients of the business-logic layer, not part of it.
Raw{"answer": "no", "explanation": "Controllers and Twig templates belong to the presentation/view layer; the fact that they call use cases makes them clients of the business-logic layer, not part of it."} | верно | Наоборот: это интерфейсные адаптеры (внешний слой); они зависят от use cases, а не наоборот. |
T25-L4 1.75 c | Clean architecture | What sits at the very center of the onion architecture? | «domain» Пояснение: In onion architecture, the Domain (enterprise business rules) sits at the very center, surrounded by Application and Delivery layers.
Raw{"answer": "Domain", "explanation": "In onion architecture, the Domain (enterprise business rules) sits at the very center, surrounded by Application and Delivery layers."} | неверно верный: «domain model» | Центральное кольцо — Domain Model: сущности и бизнес-правила без зависимостей; далее Domain Services → Application Services → Infrastructure/UI/Tests (Palermo). |
T25-L5 1.17 c | Clean architecture | Layer boundary violations can be caught automatically: a layer-dependency analyzer (e.g. deptrac) fails on a forbidden call. | «yes» Пояснение: Tools like deptrac (Dependency and Layer Rules Checker) automatically enforce predefined layer-dependency rules and report failures when a forbidden cross-layer call is detected.
Raw{"answer": "yes", "explanation": "Tools like deptrac (Dependency and Layer Rules Checker) automatically enforce predefined layer-dependency rules and report failures when a forbidden cross-layer call is detected."} | верно | depfile.yaml в проекте TasK: CI проверяет правила слоёв на каждом пайплайне. |
T25-L6 2.06 c | Clean architecture | A use case (interactor) may accept an HTTP request or an EntityManager as arguments — it is simpler that way. | «no» Пояснение: In Clean Architecture, use cases (interactors) should be framework-agnostic and depend on domain objects and repository interfaces, not on infrastructure-specific types like HTTP requests or EntityManagers, to keep them testable and decoupled.
Raw{"answer": "no", "explanation": "In Clean Architecture, use cases (interactors) should be framework-agnostic and depend on domain objects and repository interfaces, not on infrastructure-specific types like HTTP requests or EntityManagers, to keep them testable and decoupled."} | верно | Use case принимает DTO и порты; привязка к HTTP/ORM протекает инфраструктуру во внутренние слои. |
T25-L7 0.88 c | Clean architecture | What is the component called that provides a collection of aggregates/entities while hiding the storage mechanism behind an interface? | «repository» Пояснение: A Repository pattern component provides a collection of aggregates/entities and abstracts the underlying storage mechanism behind an interface.
Raw{"answer": "Repository", "explanation": "A Repository pattern component provides a collection of aggregates/entities and abstracts the underlying storage mechanism behind an interface."} | верно | Repository pattern (DDD/Evans); в проекте — Doctrine-репозитории за портами. |
T25-L8 1.98 c | Clean architecture | In clean architecture, swapping PostgreSQL for another database touches only the outer layer — the domain and use cases stay unchanged. | «yes» Пояснение: In clean architecture, the database is an outer infrastructure detail; the domain and use cases depend only on abstractions (e.g., repository interfaces), so swapping the DB engine requires changes only in the adapter/infrastructure layer.
Raw{"answer": "yes", "explanation": "In clean architecture, the database is an outer infrastructure detail; the domain and use cases depend only on abstractions (e.g., repository interfaces), so swapping the DB engine requires changes only in the adapter/infrastructure layer."} | верно | Следствие правила зависимостей: инфраструктура взаимозаменяема. |
T26-L1 1.37 c | DDD | In DDD, an aggregate is just another name for a database table. | «no» Пояснение: In DDD, an aggregate is a domain-level cluster of entities and value objects with a defined consistency boundary; it is a business concept, not a technical one like a database table (an aggregate may map to one or many tables).
Raw{"answer": "no", "explanation": "In DDD, an aggregate is a domain-level cluster of entities and value objects with a defined consistency boundary; it is a business concept, not a technical one like a database table (an aggregate may map to one or many tables)."} | верно | Агрегат — кластер объектов с границей согласованности (транзакционной вокруг корня); таблица — деталь хранения. |
T26-L2 1.1 c | DDD | A Value Object is immutable and compared by the values of its fields, not by identity. | «yes» Пояснение: Value Objects are immutable and define equality by their field values rather than by a unique identity, which is the defining characteristic that distinguishes them from Entities in DDD.
Raw{"answer": "yes", "explanation": "Value Objects are immutable and define equality by their field values rather than by a unique identity, which is the defining characteristic that distinguishes them from Entities in DDD."} | верно | Классика Evans: Money, Email; равенство структурное. |
T26-L3 1.41 c | DDD | What is the single external entry point of an aggregate, through which all changes must go, called? | «root» Пояснение: In Domain-Driven Design, the Aggregate Root is the single entry point through which all changes to the aggregate must be made.
Raw{"answer": "Root", "explanation": "In Domain-Driven Design, the Aggregate Root is the single entry point through which all changes to the aggregate must be made."} | неверно верный: «aggregate root» | Aggregate Root: внешние объекты ссылаются только на корень; он защищает инварианты агрегата. |
T26-L4 1.27 c | DDD | In DDD, a repository is declared for an aggregate (its root), not for every entity. | «yes» Пояснение: In DDD, a repository is defined for the Aggregate Root to encapsulate access to the entire aggregate, rather than creating separate repositories for each entity within it.
Raw{"answer": "yes", "explanation": "In DDD, a repository is defined for the Aggregate Root to encapsulate access to the entire aggregate, rather than creating separate repositories for each entity within it."} | верно | Репозиторий корня хранит границу согласованности агрегата; вложенные сущности доступны только через корень. |
T26-L5 1.08 c | DDD | Ubiquitous language is the model's shared language common to developers and domain experts. | «yes» Пояснение: Ubiquitous language, a key concept in Domain-Driven Design, is the shared vocabulary used consistently by both developers and domain experts to ensure clear communication and alignment between the model and the business domain.
Raw{"answer": "yes", "explanation": "Ubiquitous language, a key concept in Domain-Driven Design, is the shared vocabulary used consistently by both developers and domain experts to ensure clear communication and alignment between the model and the business domain."} | верно | Evans: язык из требований переходит в имена классов и методов. |
T26-L6 4.95 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 or context within which a model and its language maintain consistent meaning, while outside it the same symbols may refer to different models.
Raw{"answer": "frame", "explanation": "A frame is the boundary or context within which a model and its language maintain consistent meaning, while outside it the same symbols may refer to different models."} | неверно верный: «bounded context» | Bounded Context; «Заказ» в биллинге и в доставке — разные модели. |
T26-L7 1.19 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 entities and aggregates encapsulate both state and business logic, rather than an anemic model that delegates all behavior to external services.
Raw{"answer": "no", "explanation": "DDD recommends a rich domain model where entities and aggregates encapsulate both state and business logic, rather than an anemic model that delegates all behavior to external services."} | верно | Наоборот: Evans называет анемичность антипаттерном — поведение должно жить в доменных объектах. |
T26-L8 1.88 c | DDD | Bounded context means each context has its own model: the same concept in different contexts is a different class. | «yes» Пояснение: In Domain-Driven Design, a Bounded Context explicitly limits a model to a particular purpose, so the same real-world concept (e.g., 'Product') is represented by a different class in each context with potentially different attributes and behaviors.
Raw{"answer": "yes", "explanation": "In Domain-Driven Design, a Bounded Context explicitly limits a model to a particular purpose, so the same real-world concept (e.g., 'Product') is represented by a different class in each context with potentially different attributes and behaviors."} | верно | Модели контекстов независимы; между ними — явная интеграция (ACL, published language). |
T13-L1 1.0 c | Symfony | Services in the Symfony DI container are created lazily by default — on first use. | «yes» Пояснение: Symfony's DI container does not instantiate services until they are first requested, making lazy creation the default behavior.
Raw{"answer": "yes", "explanation": "Symfony's DI container does not instantiate services until they are first requested, making lazy creation the default behavior."} | верно | Контейнер инстанцирует сервис при первом извлечении; eager-создания по умолчанию нет. |
T13-L2 0.59 c | Symfony | Which Symfony console command lists all registered routes? | «debug:router» Пояснение: The Symfony console command 'debug:router' lists all registered routes in the application.
Raw{"answer": "debug:router", "explanation": "The Symfony console command 'debug:router' lists all registered routes in the application."} | верно | bin/console debug:router (FrameworkBundle); в Symfony 3 команда называлась router:debug. |
T13-L3 1.02 c | Symfony | Symfony autowiring requires manually declaring every service in services.yaml. | «no» Пояснение: Autowiring in Symfony automatically resolves dependencies via type hints, so you do not need to manually declare every service in services.yaml.
Raw{"answer": "no", "explanation": "Autowiring in Symfony automatically resolves dependencies via type hints, so you do not need to manually declare every service in services.yaml."} | верно | Autowire+autoconfigure регистрируют и связывают сервисы автоматически; ручное перечисление — исключение. |
T13-L4 1.32 c | Symfony | Twig templates are compiled into PHP classes and cached between requests. | «yes» Пояснение: Twig compiles templates into PHP classes and stores them in a cache directory, so subsequent requests reuse the cached compiled class instead of recompiling.
Raw{"answer": "yes", "explanation": "Twig compiles templates into PHP classes and stores them in a cache directory, so subsequent requests reuse the cached compiled class instead of recompiling."} | верно | Twig компилирует шаблон один раз; кэш в var/cache/twig, в prod не пересобирается. |
T13-L5 1.59 c | Symfony | In the Symfony dev environment the DI container is rebuilt only after tracked files change, not on every request. | «yes» Пояснение: In Symfony's dev environment, the DI container is compiled and cached; it is only rebuilt when tracked files (services, configs, etc.) have changed, not on every request.
Raw{"answer": "yes", "explanation": "In Symfony's dev environment, the DI container is compiled and cached; it is only rebuilt when tracked files (services, configs, etc.) have changed, not on every request."} | верно | Kernel проверяет freshness ресурсов (конфиги, классы); иначе переиспользуется кэш контейнера. |
T13-L6 1.23 c | Symfony | Which environment variable selects the active Symfony environment (dev/prod)? | «app_env» Пояснение: In Symfony, the APP_ENV environment variable selects the active environment (e.g., dev, prod, test).
Raw{"answer": "APP_ENV", "explanation": "In Symfony, the APP_ENV environment variable selects the active environment (e.g., dev, prod, test)."} | верно | APP_ENV в .env; APP_DEBUG — отдельный флаг отладки. |
T13-L7 5.93 c | Symfony | A controller method can be private — Symfony routing works with any method of the class. | «no» Пояснение: Symfony controller action methods must be public; the routing/ControllerResolver expects to invoke them as public methods, so private (or protected) actions will not work with standard routing.
Raw{"answer": "no", "explanation": "Symfony controller action methods must be public; the routing/ControllerResolver expects to invoke them as public methods, so private (or protected) actions will not work with standard routing."} | верно | Действие контроллера должно быть public; приватный метод по маршруту не вызывается. |
T13-L8 1.74 c | Symfony | Event subscribers always receive events before listeners, because the interface gives them priority. | «no» Пояснение: Priority is determined by the integer priority value assigned to each listener/subscriber, not by whether it's registered as a subscriber or a listener; a subscriber can have lower priority than a regular listener.
Raw{"answer": "no", "explanation": "Priority is determined by the integer priority value assigned to each listener/subscriber, not by whether it's registered as a subscriber or a listener; a subscriber can have lower priority than a regular listener."} | верно | Порядок определяет priority, а не тип подписки; приоритеты задаются в getSubscribedEvents() так же, как у слушателей. |
T22-L1 1.66 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 system entirely, and authentication is now built around the new AuthenticatorInterface-based system introduced in Symfony 5.3.
Raw{"answer": "yes", "explanation": "Symfony 6.0 removed the legacy guard system entirely, and authentication is now built around the new AuthenticatorInterface-based system introduced in Symfony 5.3."} | верно | Guard объявлен устаревшим в 5.3 и удалён в 6.0; в проекте symfony/security-bundle 8.1. |
T22-L2 1.32 c | Symfony: Security and forms | Which Symfony attribute checks a role/permission right on a controller method (403 without it)? | «isgranted» Пояснение: The Symfony #[IsGranted] attribute checks a role or permission on a controller method and throws AccessDeniedException (403) if the user lacks the required grant.
Raw{"answer": "IsGranted", "explanation": "The Symfony #[IsGranted] attribute checks a role or permission on a controller method and throws AccessDeniedException (403) if the user lacks the required grant."} | верно | #[IsGranted('ROLE_ADMIN')]; атрибут из symfony/security-http. |
T22-L3 1.88 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 built-in mechanism for object-level access control, used via isGranted('EDIT', $post) to check permissions on a specific object instance.
Raw{"answer": "yes", "explanation": "Symfony Voters are the built-in mechanism for object-level access control, used via isGranted('EDIT', $post) to check permissions on a specific object instance."} | верно | VoterInterface->vote(); docs Symfony — Voters. |
T22-L4 3.58 c | Symfony: Security and forms | In modern Symfony (7+) validation constraints are declared as PHP attributes (#[Assert\NotBlank]); doctrine annotations are no longer supported. | «yes» Пояснение: In Symfony 7 the Doctrine Annotations component was removed; validation constraints in PHP code must now use PHP 8 attributes (e.g. #[Assert\NotBlank]) instead of the old @Assert\NotBlank annotation syntax.
Raw{"answer": "yes", "explanation": "In Symfony 7 the Doctrine Annotations component was removed; validation constraints in PHP code must now use PHP 8 attributes (e.g. #[Assert\\NotBlank]) instead of the old @Assert\\NotBlank annotation syntax."} | верно | Докблок-аннотации удалены в Symfony 7.0; стандарт — атрибуты. В проекте symfony/validator 8.1. |
T22-L5 1.05 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 'csrf_protection' form option defaults to true), automatically adding and validating a token on submission.
Raw{"answer": "yes", "explanation": "Symfony's Form component has CSRF protection enabled by default (the 'csrf_protection' form option defaults to true), automatically adding and validating a token on submission."} | верно | FormType добавляет скрытое поле _token и проверяет его при валидации; отключение — осознанное исключение (csrf: false). |
T22-L6 1.44 c | Symfony: Security and forms | Form validation in Symfony runs server-side even if the client-side (HTML5) checks passed. | «yes» Пояснение: Symfony always performs server-side form validation independently of any client-side HTML5 checks; passing client-side validation does not skip the server-side validation.
Raw{"answer": "yes", "explanation": "Symfony always performs server-side form validation independently of any client-side HTML5 checks; passing client-side validation does not skip the server-side validation."} | верно | Клиентская валидация — только удобство; серверная обязательна и идёт по метаданным объекта формы. |
T22-L7 0.87 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 for building forms.
Raw{"answer": "make:form", "explanation": "The Symfony MakerBundle command `make:form` generates a FormType class for building forms."} | верно | bin/console make:form (symfony/maker-bundle — в проекте). |
T22-L8 1.24 c | Symfony: Security and forms | Symfony stores the user's password in the session in plain text. | «no» Пояснение: Symfony stores the user's identity (e.g., user ID) in the session, not the password; passwords are hashed (e.g., bcrypt, Argon2) and kept in the database.
Raw{"answer": "no", "explanation": "Symfony stores the user's identity (e.g., user ID) in the session, not the password; passwords are hashed (e.g., bcrypt, Argon2) and kept in the database."} | верно | В сессии живёт объект пользователя в токене; хеш затирается 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 Symfony Flex projects, bundle and topic-specific configuration files are stored in config/packages/, with one YAML file per bundle or concern (e.g., framework.yaml, doctrine.yaml).
Raw{"answer": "yes", "explanation": "In Symfony Flex projects, bundle and topic-specific configuration files are stored in config/packages/, with one YAML file per bundle or concern (e.g., framework.yaml, doctrine.yaml)."} | верно | Стандартная структура (config/packages/*.yaml); перегрузка — config/packages/<env>. |
T23-L2 2.32 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 (and general Dotenv) convention: .env with dev defaults is committed, while .env.local (or .env.local.php) holds real secrets and is added to .gitignore.
Raw{"answer": "yes", "explanation": "This is the standard Symfony (and general Dotenv) convention: .env with dev defaults is committed, while .env.local (or .env.local.php) holds real secrets and is added to .gitignore."} | верно | symfony/dotenv: .env — общий безопасный набор значений; локальные секреты — .env.local (gitignored) или secrets-хранилище. |
T23-L3 1.96 c | Symfony: configuration and services | Which Symfony command lists the container's registered services and their aliases? | «debug:container» Пояснение: The Symfony command 'debug:container' (also known as 'container:debug' in older versions) lists all registered services and their aliases in the service container.
Raw{"answer": "debug:container", "explanation": "The Symfony command 'debug:container' (also known as 'container:debug' in older versions) lists all registered services and their aliases in the service container."} | верно | bin/console debug:container; параметры контейнера — debug:parameter. |
T23-L4 3.79 c | Symfony: configuration and services | The Symfony container allows changing parameters at runtime: $container->setParameter() works from a controller. | «yes» Пояснение: Container::setParameter() simply writes to the internal $parameters array without checking the frozen state, so calling it from a controller at runtime does update the parameter (though it's generally considered an anti-pattern).
Raw{"answer": "yes", "explanation": "Container::setParameter() simply writes to the internal $parameters array without checking the frozen state, so calling it from a controller at runtime does update the parameter (though it's generally considered an anti-pattern)."} | неверно верный: «no» | Контейнер компилируется и замораживается; runtime-значения — только через переменные окружения. |
T23-L5 2.26 c | Symfony: configuration and services | By default, Symfony services are public (public: true) — you can fetch them directly from the container. | «no» Пояснение: Since Symfony 4.0, services are private by default (public: false); they must be explicitly marked public to be fetched directly from the container.
Raw{"answer": "no", "explanation": "Since Symfony 4.0, services are private by default (public: false); they must be explicitly marked public to be fetched directly from the container."} | верно | С Symfony 4.0 сервисы по умолчанию private: инжектятся через autowiring; $container->get() — только для публичных. |
T23-L6 1.2 c | Symfony: configuration and services | Without a config file in config/packages a bundle will not work — configuration is mandatory for every bundle. | «no» Пояснение: Bundles in Symfony can work with their default configuration; a config file in config/packages is only needed if you want to customize the bundle's settings.
Raw{"answer": "no", "explanation": "Bundles in Symfony can work with their default configuration; a config file in config/packages is only needed if you want to customize the bundle's settings."} | верно | У бандлов есть встроенные умолчания (Extension); конфиг нужен только для отклонений от них. |
T23-L7 1.16 c | Symfony: configuration and services | Environment variable values are injected into services.yaml using the %env(VAR)% syntax. | «yes» Пояснение: Symfony uses the %env(VAR)% syntax in configuration files like services.yaml to inject environment variable values into service definitions.
Raw{"answer": "yes", "explanation": "Symfony uses the %env(VAR)% syntax in configuration files like services.yaml to inject environment variable values into service definitions."} | верно | %env(...)% резолвится в рантайме env-процессорами; docs — Env Var Processors. |
T23-L8 0.76 c | Symfony: configuration and services | Which Symfony environment variable enables debug mode (affects the profiler and Twig debugging)? | «app_debug» Пояснение: The APP_DEBUG environment variable in .env file controls Symfony's debug mode, enabling the profiler and Twig debugging features when set to true.
Raw{"answer": "APP_DEBUG", "explanation": "The APP_DEBUG environment variable in .env file controls Symfony's debug mode, enabling the profiler and Twig debugging features when set to true."} | верно | APP_DEBUG=1 (в .env dev-окружения); окружение выбирает APP_ENV — см. T13-L6. |
T16-L1 2.81 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; you can configure routing to dispatch a message to more than one handler.
Raw{"answer": "no", "explanation": "Symfony Messenger allows multiple handlers to be registered for the same message; you can configure routing to dispatch a message to more than one handler."} | верно | Messenger вызывает все хендлеры, подписанные на класс сообщения (docs — Multiple Handlers). |
T16-L2 1.14 c | Symfony: Messenger | The sync transport in Messenger queues the message for a worker, just like async. | «no» Пояснение: The sync transport dispatches the message immediately to a listener in the same process without any queue or worker; it does not queue the message at all.
Raw{"answer": "no", "explanation": "The sync transport dispatches the message immediately to a listener in the same process without any queue or worker; it does not queue the message at all."} | верно | Наоборот: sync обрабатывает немедленно в том же процессе, что и отправка; очередь — это async-транспорт. |
T16-L3 0.81 c | Symfony: Messenger | Which console command starts the worker that processes Messenger queue messages? | «messenger:consume» Пояснение: In Symfony, the 'bin/console messenger:consume' command starts the worker that processes Messenger queue messages.
Raw{"answer": "messenger:consume", "explanation": "In Symfony, the 'bin/console messenger:consume' command starts the worker that processes Messenger queue messages."} | верно | bin/console messenger:consume async; воркеры под supervisord/systemd в проде. |
T16-L4 1.23 c | Symfony: Messenger | Retries for failed messages (retry_strategy) are configured per Messenger transport. | «yes» Пояснение: In Symfony Messenger, the retry_strategy (max_retries, delay, multiplier, max_delay) is configured per individual transport in the framework messenger configuration.
Raw{"answer": "yes", "explanation": "In Symfony Messenger, the retry_strategy (max_retries, delay, multiplier, max_delay) is configured per individual transport in the framework messenger configuration."} | верно | retry_strategy на транспорте: max_retries, delay, multiplier; docs — Failed Messages & Retries. |
T16-L5 1.3 c | Symfony: Messenger | By default, Messenger serializes messages to JSON. | «yes» Пояснение: Symfony Messenger's default serializer uses JSON as the encoding format out of the box.
Raw{"answer": "yes", "explanation": "Symfony Messenger's default serializer uses JSON as the encoding format out of the box."} | неверно верный: «no» | Дефолтный сериализатор — PhpSerializer (serialize()); JSON-сериализатор включается отдельно. |
T16-L6 0.95 c | Symfony: Messenger | Symfony Scheduler produces messages on a schedule and dispatches them through Messenger. | «yes» Пояснение: Symfony Scheduler is designed to produce and dispatch messages on a recurring schedule through the Symfony Messenger component.
Raw{"answer": "yes", "explanation": "Symfony Scheduler is designed to produce and dispatch messages on a recurring schedule through the Symfony Messenger component."} | верно | Schedule → RecurringMessage → шина Messenger; docs — Scheduler. |
T16-L7 0.79 c | Symfony: Messenger | Which built-in Messenger transport stores messages in database tables via Doctrine? | «doctrine» Пояснение: Symfony Messenger's doctrine transport stores messages in database tables managed by Doctrine ORM.
Raw{"answer": "doctrine", "explanation": "Symfony Messenger's doctrine transport stores messages in database tables managed by Doctrine ORM."} | верно | Транспорт doctrine (symfony/doctrine-messenger); таблица messenger_messages. В проекте стоит amqp-messenger + doctrine-messenger. |
T16-L8 1.22 c | Symfony: Messenger | The Messenger pipeline can be extended with custom middleware, placed before or after the built-in ones. | «yes» Пояснение: Symfony Messenger's middleware pipeline is extensible; custom middleware can be registered and positioned before or after the built-in middleware via configuration.
Raw{"answer": "yes", "explanation": "Symfony Messenger's middleware pipeline is extensible; custom middleware can be registered and positioned before or after the built-in middleware via configuration."} | верно | messenger.bus.*.middleware в yaml; docs — Middleware. |
T28-L1 4.05 c | Symfony: versions | Symfony major releases come every two years, minor ones every six months (in May and November). | «yes» Пояснение: Symfony follows a schedule where major versions are released approximately every two years (in November), and minor releases occur every six months in May and November.
Raw{"answer": "yes", "explanation": "Symfony follows a schedule where major versions are released approximately every two years (in November), and minor releases occur every six months in May and November."} | верно | Стандартный релизный цикл: 8.0 — ноябрь 2025, 8.1 — май 2026, 8.2 — ноябрь 2026. |
T28-L2 1.86 c | Symfony: versions | What is the minimum PHP version required by Symfony 8? | «8.4» Пояснение: Symfony 8 requires a minimum PHP version of 8.4.
Raw{"answer": "8.4", "explanation": "Symfony 8 requires a minimum PHP version of 8.4."} | верно | Symfony 8.0 поднял требование до PHP >= 8.4.1 (в vendor проекта: "php": ">=8.4.1"). |
T28-L3 4.31 c | Symfony: versions | Symfony 7.0 kept support for docblock annotations (validation, routes). | «yes» Пояснение: Symfony 7.0 still supports docblock annotations (e.g. @Route, @Assert) though they are deprecated in favor of PHP 8 attributes; full removal is planned for Symfony 8.0.
Raw{"answer": "yes", "explanation": "Symfony 7.0 still supports docblock annotations (e.g. @Route, @Assert) though they are deprecated in favor of PHP 8 attributes; full removal is planned for Symfony 8.0."} | неверно верный: «no» | Наоборот: в 7.0 аннотации удалены — только PHP-атрибуты (#[Route], #[Assert\NotBlank]). |
T28-L4 1.4 c | Symfony: versions | AssetMapper manages CSS/JS without node or webpack — via importmap.php. | «yes» Пояснение: Symfony's AssetMapper component manages CSS/JS assets without requiring Node.js or webpack, using an importmap.php (or importmap.json) file to define asset imports and mappings.
Raw{"answer": "yes", "explanation": "Symfony's AssetMapper component manages CSS/JS assets without requiring Node.js or webpack, using an importmap.php (or importmap.json) file to define asset imports and mappings."} | верно | symfony/asset-mapper (с 6.3, стандарт с 7.x); в проекте — importmap.php в корне и asset-mapper 8.1. |
T28-L5 1.28 c | Symfony: versions | Symfony 6.4 is a regular release without long-term support. | «no» Пояснение: Symfony 6.4 is an LTS (Long-Term Support) release with 2 years of bug fixes and 4 years of security fixes, as even minor versions are LTS.
Raw{"answer": "no", "explanation": "Symfony 6.4 is an LTS (Long-Term Support) release with 2 years of bug fixes and 4 years of security fixes, as even minor versions are LTS."} | верно | Наоборот: 6.4 — LTS (расширенная поддержка); LTS выходит вместе с очередным мажором (6.4 — вместе с 7.0). |
T28-L6 2.17 c | Symfony: versions | When moving to a new Symfony major version, deprecations of the previous branch keep working — major releases do not remove them. | «no» Пояснение: In Symfony, deprecations introduced in a major version are removed in the next major version, so moving to a new major release does remove the previous branch's deprecations.
Raw{"answer": "no", "explanation": "In Symfony, deprecations introduced in a major version are removed in the next major version, so moving to a new major release does remove the previous branch's deprecations."} | верно | Наоборот: мажорный релиз удаляет всё устаревшее (7.0 убрал деприкейшены 6.x, 8.0 — 7.x). |
T28-L7 1.39 c | Symfony: versions | Every Symfony major release is accompanied by an UPGRADE guide listing the changes. | «yes» Пояснение: Symfony ships an UPGRADE-<major>.<minor>.md file with each major release documenting breaking changes and deprecations.
Raw{"answer": "yes", "explanation": "Symfony ships an UPGRADE-<major>.<minor>.md file with each major release documenting breaking changes and deprecations."} | верно | UPGRADE-7.0.md, UPGRADE-8.0.md в репозитории symfony/symfony. |
T28-L8 1.63 c | Symfony: versions | Which Symfony component manages assets and the importmap without node/webpack? | «assetmapper» Пояснение: Symfony's AssetMapper component (introduced in Symfony 6.4/7.0) manages assets and importmaps natively without requiring Node.js or webpack.
Raw{"answer": "AssetMapper", "explanation": "Symfony's AssetMapper component (introduced in Symfony 6.4/7.0) manages assets and importmaps natively without requiring Node.js or webpack."} | верно | symfony/asset-mapper 8.1 — в проекте. |
T29-L1 3.31 c | Symfony: 8.2 and beyond | As of 2026-11-07, Symfony 8.2 has already been released. | «yes» Пояснение: Symfony 8.0 was released in November 2025, and minor versions follow monthly, so 8.2 would have been released well before November 2026.
Raw{"answer": "yes", "explanation": "Symfony 8.0 was released in November 2025, and minor versions follow monthly, so 8.2 would have been released well before November 2026."} | неверно верный: «no» | Наоборот: 8.2 ещё не выпущена — релиз в конце ноября 2026; последняя стабильная — 8.1. |
T29-L2 5.41 c | Symfony: 8.2 and beyond | As of 2026-11-07, Symfony 8.2 is scheduled for November 2026, following the usual six-month cycle. | «yes» Пояснение: Symfony follows a six-month release cycle with even minor versions in November, so 8.2 would indeed be scheduled for November 2026.
Raw{"answer": "yes", "explanation": "Symfony follows a six-month release cycle with even minor versions in November, so 8.2 would indeed be scheduled for November 2026."} | верно | Политика релизов: 8.1 — май 2026, 8.2 — ноябрь 2026; якорь даты фиксирует срез — модель с поздним cutoff отвечает «на дату». |
T29-L3 2.22 c | Symfony: 8.2 and beyond | Which Symfony version comes after 8.1 (as of 2026-11-07)? | «8.2» Пояснение: Following Symfony's release cadence (X.0 in November, X.1 in May, X.2 in November), the version after 8.1 (May 2026) is 8.2 (November 2026).
Raw{"answer": "8.2", "explanation": "Following Symfony's release cadence (X.0 in November, X.1 in May, X.2 in November), the version after 8.1 (May 2026) is 8.2 (November 2026)."} | верно | 8.2 — следующий минорный релиз (ноябрь 2026); после его выхода проект переходит с 8.1.* на 8.2.*. |
T29-L4 2.98 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 (patch-level) release within the 8.x major line, so it is backward-compatible and does not require rewriting; only major releases (e.g., 8.0) can introduce breaking changes.
Raw{"answer": "no", "explanation": "Symfony 8.2 is a minor (patch-level) release within the 8.x major line, so it is backward-compatible and does not require rewriting; only major releases (e.g., 8.0) can introduce breaking changes."} | верно | Наоборот: 8.2 — минорный релиз; новые возможности без поломки обратной совместимости. Мажор — 9.0. |
T29-L5 3.05 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» Пояснение: Within the same major version (8.x), PHP follows backward compatibility: minor releases (8.1 → 8.2) add new features without removing or altering existing behavior, so no code changes are required.
Raw{"answer": "yes", "explanation": "Within the same major version (8.x), PHP follows backward compatibility: minor releases (8.1 → 8.2) add new features without removing or altering existing behavior, so no code changes are required."} | верно | Политика Symfony: минорные релизы обратно совместимы; BC-break допустим только в мажорных. |
T29-L6 2.72 c | Symfony: 8.2 and beyond | Which minor version of the 8.x branch is released last, before Symfony 9.0? | «8.4» Пояснение: Symfony follows a pattern of releasing minor versions .0 through .4 per major branch, so the last minor version of 8.x before 9.0 is 8.4.
Raw{"answer": "8.4", "explanation": "Symfony follows a pattern of releasing minor versions .0 through .4 per major branch, so the last minor version of 8.x before 9.0 is 8.4."} | верно | По циклу: 8.2 (ноя 2026), 8.3 (май 2027), 8.4 (ноя 2027, вместе с 9.0) — как 6.4 выходила вместе с 7.0. |
T29-L7 5.04 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's minimum PHP version is typically set at the major-version level (e.g., Symfony 8.0), and minor releases like 8.2 maintain that same baseline; it is not certain that 8.2 specifically bumps the requirement to PHP 8.5.
Raw{"answer": "no", "explanation": "Symfony's minimum PHP version is typically set at the major-version level (e.g., Symfony 8.0), and minor releases like 8.2 maintain that same baseline; it is not certain that 8.2 specifically bumps the requirement to PHP 8.5."} | верно | Наоборот: минорные релизы не поднимают требования PHP; для всей ветки 8.x остаётся PHP >= 8.4. |
T29-L8 3.54 c | Symfony: 8.2 and beyond | Deprecations added in the 8.x branch will not be removed before Symfony 9.0. | «yes» Пояснение: Symfony's deprecation policy guarantees that deprecations introduced in a given major version (8.x) are only removed in the next major version (9.0), so they persist throughout all 8.x releases.
Raw{"answer": "yes", "explanation": "Symfony's deprecation policy guarantees that deprecations introduced in a given major version (8.x) are only removed in the next major version (9.0), so they persist throughout all 8.x releases."} | верно | Политика: деприкейшены живут до следующего мажора; 9.0 — ноябрь 2027. |
T21-L1 1.47 c | Twig | Inside {{ }}, Twig allows calling arbitrary PHP code directly. | «no» Пояснение: Twig's {{ }} block uses its own templating expression language (variables, filters, operators), not raw/arbitrary PHP code.
Raw{"answer": "no", "explanation": "Twig's {{ }} block uses its own templating expression language (variables, filters, operators), not raw/arbitrary PHP code."} | верно | Twig — DSL: только разрешённые окружением функции/фильтры; произвольный PHP не исполняется. |
T21-L2 0.79 c | Twig | By default, Twig auto-escapes printed variables. | «yes» Пояснение: Twig enables auto-escaping with the 'html' strategy by default, so printed variables are HTML-escaped to prevent XSS attacks.
Raw{"answer": "yes", "explanation": "Twig enables auto-escaping with the 'html' strategy by default, so printed variables are HTML-escaped to prevent XSS attacks."} | верно | Autoescape включён по умолчанию; {{ '<b>' }} → <b>. Проверено на Twig 3.30. |
T21-L3 0.91 c | Twig | The Twig |e filter escapes a string for safe output in an HTML context. | «yes» Пояснение: The Twig |e (escape) filter defaults to escaping for the HTML context using htmlspecialchars with ENT_QUOTES.
Raw{"answer": "yes", "explanation": "The Twig |e (escape) filter defaults to escaping for the HTML context using htmlspecialchars with ENT_QUOTES."} | верно | |e ('html') по умолчанию; есть контексты js/url/css. От SQL-инъекций он не защищает — это задача подготовленных запросов Doctrine. |
T21-L4 1.7 c | Twig | Which filter from twig/intl-extra formats a number according to a locale? | «number_format» Пояснение: The twig/intl-extra package provides the number_format filter which uses PHP's intl extension to format a number according to a given locale.
Raw{"answer": "number_format", "explanation": "The twig/intl-extra package provides the number_format filter which uses PHP's intl extension 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.93 c | Twig | The |raw filter disables auto-escaping for the value. | «yes» Пояснение: In Twig (the template engine commonly used with PHP), the |raw filter outputs a value without auto-escaping, treating it as safe HTML.
Raw{"answer": "yes", "explanation": "In Twig (the template engine commonly used with PHP), the |raw filter outputs a value without auto-escaping, treating it as safe HTML."} | верно | {{ x|raw }} выводит HTML как есть; опасно с пользовательскими данными. Проверено на Twig 3.30. |
T21-L6 1.12 c | Twig | In Twig, {{ }} prints an expression value, while {% %} executes tags — conditions, loops, set. | «yes» Пояснение: In Twig, double curly braces {{ }} output/echo an expression's value, while percent braces {% %} execute structural tags such as if, for, and set.
Raw{"answer": "yes", "explanation": "In Twig, double curly braces {{ }} output/echo an expression's value, while percent braces {% %} execute structural tags such as if, for, and set."} | верно | Два блока синтаксиса Twig: вывод (echo) против логики. |
T21-L7 0.96 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' %}, so values do not exclusively come from the controller.
Raw{"answer": "no", "explanation": "Twig allows you to declare variables inside a template using the {% set %} tag, e.g. {% set foo = 'bar' %}, so values do not exclusively come from the controller."} | верно | {% set y = ... %} объявляет переменную в шаблоне. Проверено на Twig 3.30. |
T21-L8 0.73 c | Twig | Which Twig function dumps the debug structure of a variable (array, object)? | «dump» Пояснение: The Twig function 'dump()' outputs the debug structure of a variable such as an array or object.
Raw{"answer": "dump", "explanation": "The Twig function 'dump()' outputs the debug structure of a variable such as an array or object."} | верно | {{ dump(x) }} (DebugExtension; в Symfony доступна в dev-окружении). |
T24-L1 0.85 c | Bootstrap | Bootstrap is a CSS/JS library of ready-made UI components, not an SPA framework. | «yes» Пояснение: Bootstrap is a CSS framework with optional JS plugins providing pre-built UI components; it is not an SPA framework like React, Angular, or Vue.
Raw{"answer": "yes", "explanation": "Bootstrap is a CSS framework with optional JS plugins providing pre-built UI components; it is not an SPA framework like React, Angular, or Vue."} | верно | Компоненты и утилиты поверх вашего HTML; SPA-фреймворки (React/Vue) — другой класс инструментов. В проекте vendored 5.3.3. |
T24-L2 1.04 c | Bootstrap | Which Bootstrap class gives a responsive container with a fixed max width per breakpoint? | «container» Пояснение: The Bootstrap 'container' class provides a responsive fixed-width container that has a max-width that changes at each breakpoint (e.g., 720px at md, 960px at lg, 1140px at xl).
Raw{"answer": "container", "explanation": "The Bootstrap 'container' class provides a responsive fixed-width container that has a max-width that changes at each breakpoint (e.g., 720px at md, 960px at lg, 1140px at xl)."} | верно | .container (фиксированная макс-ширина по брейкпоинтам) vs .container-fluid (на всю ширину). |
T24-L3 1.42 c | Bootstrap | The Bootstrap grid is built on CSS floats and splits a row into 16 columns. | «no» Пояснение: The Bootstrap grid splits a row into 12 columns, not 16 (and modern Bootstrap versions use Flexbox rather than CSS floats).
Raw{"answer": "no", "explanation": "The Bootstrap grid splits a row into 12 columns, not 16 (and modern Bootstrap versions use Flexbox rather than CSS floats)."} | верно | Наоборот: flexbox (с Bootstrap 4) и 12 колонок; float-сетка — это Bootstrap 3. |
T24-L4 2.84 c | Bootstrap | Bootstrap's named breakpoints (the infix used in class names) are sm, md, lg, xl, xxl — five of them. | «yes» Пояснение: In Bootstrap 5, the breakpoint infixes used in class names are sm, md, lg, xl, and xxl (xs is the base and requires no infix), making exactly five.
Raw{"answer": "yes", "explanation": "In Bootstrap 5, the breakpoint infixes used in class names are sm, md, lg, xl, and xxl (xs is the base and requires no infix), making exactly five."} | верно | Тиров всего шесть: xs (без инфикса) + пять именованных (576/768/992/1200/1400 px). |
T24-L5 4.45 c | Bootstrap | Utilities like .mt-3 or .px-2 use the spacing scale: the number is a multiple of $spacer. | «yes» Пояснение: In Bootstrap's spacing system, utility classes like .mt-3 or .px-2 generate values that are the numeric suffix multiplied by $spacer (e.g., .mt-3 = 3 * $spacer).
Raw{"answer": "yes", "explanation": "In Bootstrap's spacing system, utility classes like .mt-3 or .px-2 generate values that are the numeric suffix multiplied by $spacer (e.g., .mt-3 = 3 * $spacer)."} | неверно верный: «no» | Spacing utilities; $spacer = 1rem. |
T24-L6 0.88 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 collapses on an element.
Raw{"answer": "data-bs-toggle", "explanation": "In Bootstrap 5, the data-bs-toggle attribute is used to enable interactive components such as dropdowns, tooltips, popovers, and collapses on an element."} | верно | data-bs-toggle="dropdown" и т.п.; в Bootstrap 4 атрибут назывался data-toggle. |
T24-L7 0.71 c | Bootstrap | Bootstrap 5 components work without jQuery — in plain vanilla JS. | «yes» Пояснение: Bootstrap 5 dropped its jQuery dependency and all components are built with plain vanilla JavaScript.
Raw{"answer": "yes", "explanation": "Bootstrap 5 dropped its jQuery dependency and all components are built with plain vanilla JavaScript."} | верно | jQuery удалён в Bootstrap 5.0: data-bs-* атрибуты и JS API. В проекте vendored 5.3.3. |
T24-L8 1.12 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.08 c | Doctrine | Doctrine ORM creates database tables on the fly the first time an entity is used at runtime. | «no» Пояснение: Doctrine ORM does not automatically create tables at runtime; you must explicitly run a schema tool or migration command (e.g., doctrine:schema:create or doctrine:migrations:migrate) to create the database tables.
Raw{"answer": "no", "explanation": "Doctrine ORM does not automatically create tables at runtime; you must explicitly run a schema tool or migration command (e.g., doctrine:schema:create or doctrine:migrations:migrate) to create the database tables."} | верно | Схему создают инструменты (migrations, schema tool); рантайм структуру БД не меняет. |
T14-L2 1.07 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 (persistent) and schedules an INSERT to be executed only when flush() is called.
Raw{"answer": "persist", "explanation": "EntityManager::persist() marks a new entity as managed (persistent) and schedules an INSERT to be executed only when flush() is called."} | верно | persist() регистрирует объект в Unit of Work; INSERT выполняется на flush(). |
T14-L3 5.41 c | Doctrine | In Doctrine ORM 3, the EntityManager::merge() method exists and makes the passed object managed. | «no» Пояснение: EntityManager::merge() does exist in Doctrine ORM 3, but it returns a new managed copy rather than making the passed (detached) object itself managed; the original object remains detached.
Raw{"answer": "no", "explanation": "EntityManager::merge() does exist in Doctrine ORM 3, but it returns a new managed copy rather than making the passed (detached) object itself managed; the original object remains detached."} | верно | В ORM 3 merge() удалён (в vendor проекта 3.7.6 метода нет); в Doctrine 2.x merge() возвращал управляемую копию. Версия зафиксирована — ORM 3. |
T14-L4 0.96 c | Doctrine | DQL queries are written in terms of entities and their fields, not tables and columns. | «yes» Пояснение: DQL (Doctrine Query Language) operates at the entity level, referencing entity classes and their properties rather than raw database tables and columns.
Raw{"answer": "yes", "explanation": "DQL (Doctrine Query Language) operates at the entity level, referencing entity classes and their properties rather than raw database tables and columns."} | верно | Doctrine транслирует DQL в SQL; docs — DQL (Doctrine Query Language). |
T14-L5 0.64 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 is found.
Raw{"answer": "null", "explanation": "Doctrine's Repository::find() method returns null when no entity with the given ID is found."} | верно | find() возвращает null, если объект не найден (docs Repository methods). |
T14-L6 1.58 c | Doctrine | DoctrineBundle in Symfony automatically calls flush() at the end of every request. | «no» Пояснение: DoctrineBundle in Symfony calls EntityManager::close() at the end of a request to release the connection, but it does NOT automatically call flush(); you must call flush() explicitly in your code.
Raw{"answer": "no", "explanation": "DoctrineBundle in Symfony calls EntityManager::close() at the end of a request to release the connection, but it does NOT automatically call flush(); you must call flush() explicitly in your code."} | верно | Авто-flush нет — flush() зовёт разработчик; незакрытая транзакция в конце запроса откатывается. |
T14-L7 1.65 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 automatically detects property changes on managed entities via change-set computation, so flush() alone commits them without needing a redundant persist() call.
Raw{"answer": "yes", "explanation": "The Unit of Work automatically detects property changes on managed entities via change-set computation, so flush() alone commits them without needing a redundant persist() call."} | верно | Dirty checking сравнивает снимки свойств; persist нужен только новым/отсоединённым объектам. |
T14-L8 1.13 c | Doctrine | remove() executes the SQL DELETE immediately, without waiting for flush(). | «no» Пояснение: Doctrine's remove() only schedules the entity for deletion in the UnitOfWork; the actual SQL DELETE is executed when flush() is called.
Raw{"answer": "no", "explanation": "Doctrine's remove() only schedules the entity for deletion in the UnitOfWork; the actual SQL DELETE is executed when flush() is called."} | верно | remove() планирует удаление в Unit of Work; DELETE выполняется на flush() (docs — Deleting Objects). |
T15-L1 1.42 c | PostgreSQL | PostgreSQL uses MVCC, therefore readers block writers and writers block readers. | «no» Пояснение: MVCC in PostgreSQL allows readers and writers to operate concurrently without blocking each other; readers see a snapshot of the data and writers create new row versions, so they do not block one another.
Raw{"answer": "no", "explanation": "MVCC in PostgreSQL allows readers and writers to operate concurrently without blocking each other; readers see a snapshot of the data and writers create new row versions, so they do not block one another."} | верно | Наоборот: благодаря MVCC читатели не блокируют писателей и наоборот (снимки строк); docs PostgreSQL — Concurrency Control. |
T15-L2 0.92 c | PostgreSQL | Which SQL command shows a query's execution plan without executing the query? | «explain» Пояснение: The EXPLAIN command displays a query's execution plan (table access methods, indexes used, join order) without actually running the query.
Raw{"answer": "EXPLAIN", "explanation": "The EXPLAIN command displays a query's execution plan (table access methods, indexes used, join order) without actually running the query."} | верно | EXPLAIN без ANALYZE только строит план; проверено на PostgreSQL 17.7. |
T15-L3 3.08 c | PostgreSQL | SERIAL and GENERATED ... AS IDENTITY are just two names for the same mechanism. | «no» Пояснение: SERIAL is a PostgreSQL-specific convenience macro that creates a separate sequence, a column, a default expression, and an ownership link, while GENERATED AS IDENTITY is a distinct SQL-standard mechanism with its own rules (e.g., GENERATED BY DEFAULT/ALWAYS, ALTER IDENTITY, DROP IDENTITY); they are similar in purpose but not the same mechanism.
Raw{"answer": "no", "explanation": "SERIAL is a PostgreSQL-specific convenience macro that creates a separate sequence, a column, a default expression, and an ownership link, while GENERATED AS IDENTITY is a distinct SQL-standard mechanism with its own rules (e.g., GENERATED BY DEFAULT/ALWAYS, ALTER IDENTITY, DROP IDENTITY); they are similar in purpose but not the same mechanism."} | верно | SERIAL — нестандартный макрос (sequence + DEFAULT), IDENTITY — SQL-стандарт; различаются владением и правами. Оба есть в PG 17 (проверено). |
T15-L4 1.8 c | PostgreSQL | By default, a PostgreSQL UNIQUE constraint allows only one row with NULL in the column. | «no» Пояснение: In PostgreSQL, a UNIQUE constraint treats NULLs as distinct values, so multiple rows can have NULL in the constrained column by default.
Raw{"answer": "no", "explanation": "In PostgreSQL, a UNIQUE constraint treats NULLs as distinct values, so multiple rows can have NULL in the constrained column by default."} | верно | Наоборот: NULLS DISTINCT по умолчанию — несколько NULL допустимы; NULLS NOT DISTINCT — опция с PG 15. Проверено на PG 17.7. |
T15-L5 0.81 c | PostgreSQL | Which PostgreSQL aggregate function concatenates strings with a separator? | «string_agg» Пояснение: PostgreSQL's string_agg() aggregate function concatenates string values with a specified separator, e.g. string_agg(col, ',').
Raw{"answer": "string_agg", "explanation": "PostgreSQL's string_agg() aggregate function concatenates string values with a specified separator, e.g. string_agg(col, ',')."} | верно | string_agg(значение, разделитель); проверено на PostgreSQL 17.7. |
T15-L6 1.57 c | PostgreSQL | Plain VACUUM returns the space occupied by dead tuples to the operating system. | «no» Пояснение: Plain VACUUM only marks dead tuple space as reusable within the table file; it is VACUUM FULL that rewrites the table and returns space to the operating system.
Raw{"answer": "no", "explanation": "Plain VACUUM only marks dead tuple space as reusable within the table file; it is VACUUM FULL that rewrites the table and returns space to the operating system."} | верно | VACUUM помечает место для переиспользования внутри таблицы; ОС его возвращает только VACUUM FULL (с эксклюзивной блокировкой). |
T15-L7 0.75 c | PostgreSQL | Which keyword in a window function definition partitions rows into groups the function is computed over? | «partition by» Пояснение: In SQL window functions, the PARTITION BY clause divides rows into groups over which the window function is computed.
Raw{"answer": "PARTITION BY", "explanation": "In SQL window functions, the PARTITION BY clause divides rows into groups over which the window function is computed."} | верно | OVER (PARTITION BY ...); проверено на PostgreSQL 17.7. |
T15-L8 1.2 c | PostgreSQL | The READ COMMITTED isolation level protects against non-repeatable reads. | «no» Пояснение: READ COMMITTED only protects against dirty reads; non-repeatable reads are protected by the REPEATABLE READ isolation level and above.
Raw{"answer": "no", "explanation": "READ COMMITTED only protects against dirty reads; non-repeatable reads are protected by the REPEATABLE READ isolation level and above."} | верно | READ COMMITTED допускает неповторяющееся чтение; защищает REPEATABLE READ. Проверено: SHOW transaction_isolation → read committed. |
T17-L1 1.04 c | PostgreSQL: transactions and indexes | By default, PostgreSQL wraps each single SQL statement in its own implicit transaction (autocommit). | «yes» Пояснение: PostgreSQL operates in autocommit mode by default, meaning each individual SQL statement is automatically committed as its own implicit transaction unless explicitly wrapped in BEGIN/COMMIT.
Raw{"answer": "yes", "explanation": "PostgreSQL operates in autocommit mode by default, meaning each individual SQL statement is automatically committed as its own implicit transaction unless explicitly wrapped in BEGIN/COMMIT."} | верно | Без BEGIN каждый оператор коммитится сам; docs PostgreSQL — Transactions. Проверено на PG 17. |
T17-L2 0.42 c | PostgreSQL: transactions and indexes | Which SQL command ends a transaction, committing all its changes? | «commit» Пояснение: The COMMIT SQL command ends a transaction by permanently saving all changes made within it.
Raw{"answer": "COMMIT", "explanation": "The COMMIT SQL command ends a transaction by permanently saving all changes made within it."} | верно | COMMIT (END — синоним). Проверено на PG 17. |
T17-L3 1.24 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 are used to quickly locate rows, so UPDATE and DELETE statements with a WHERE clause on an indexed column also benefit from the index, not just SELECT.
Raw{"answer": "yes", "explanation": "Indexes are used to quickly locate rows, so UPDATE and DELETE statements with a WHERE clause on an indexed column also benefit from the index, not just SELECT."} | верно | Поиск строк для изменения идёт по индексу; docs PostgreSQL — Indexes. |
T17-L4 1.19 c | PostgreSQL: transactions and indexes | To roll back part of the statements inside a transaction, PostgreSQL uses SAVEPOINT. | «yes» Пояснение: SAVEPOINT allows rolling back to a specific point within a transaction, undoing only the statements after that point while preserving earlier ones.
Raw{"answer": "yes", "explanation": "SAVEPOINT allows rolling back to a specific point within a transaction, undoing only the statements after that point while preserving earlier ones."} | верно | SAVEPOINT name; ROLLBACK TO name — частичный откат без отмены всей транзакции. Проверено на PG 17. |
T17-L5 1.36 c | PostgreSQL: transactions and indexes | EXPLAIN ANALYZE shows the query plan without executing the query. | «no» Пояснение: EXPLAIN ANALYZE actually executes the query to collect real performance statistics; plain EXPLAIN (without ANALYZE) shows the plan without executing.
Raw{"answer": "no", "explanation": "EXPLAIN ANALYZE actually executes the query to collect real performance statistics; plain EXPLAIN (without ANALYZE) shows the plan without executing."} | верно | Наоборот: ANALYZE реально выполняет запрос (с побочными эффектами!) и показывает фактические времена узлов; план без выполнения — plain EXPLAIN. |
T17-L6 0.79 c | PostgreSQL: transactions and indexes | Which PostgreSQL extension adds vector types and indexes for embedding search? | «pgvector» Пояснение: pgvector is a PostgreSQL extension that adds a vector data type and index types (IVFFlat, HNSW) for efficient embedding similarity search.
Raw{"answer": "pgvector", "explanation": "pgvector is a PostgreSQL extension that adds a vector data type and index types (IVFFlat, HNSW) for efficient embedding similarity search."} | верно | CREATE EXTENSION vector (проект pgvector; в проекте образ pgvector/pgvector:pg17). |
T17-L7 1.44 c | PostgreSQL: transactions and indexes | A partial index (CREATE INDEX ... WHERE ...) is built only over rows satisfying the condition. | «yes» Пояснение: A partial index (CREATE INDEX ... WHERE ...) in PostgreSQL indexes only those rows that satisfy the given WHERE condition, leaving the other rows out of the index.
Raw{"answer": "yes", "explanation": "A partial index (CREATE INDEX ... WHERE ...) in PostgreSQL indexes only those rows that satisfy the given WHERE condition, leaving the other rows out of the index."} | верно | docs PostgreSQL — Partial Indexes; типичный кейс — индекс по «активным» записям. |
T17-L8 1.72 c | PostgreSQL: transactions and indexes | The SERIALIZABLE level in PostgreSQL is implemented by locking the rows a transaction reads. | «no» Пояснение: PostgreSQL implements SERIALIZABLE via Serializable Snapshot Isolation (SSI) with predicate locking and post-hoc conflict detection, not by locking the rows a transaction reads (that is SQL Server's approach).
Raw{"answer": "no", "explanation": "PostgreSQL implements SERIALIZABLE via Serializable Snapshot Isolation (SSI) with predicate locking and post-hoc conflict detection, not by locking the rows a transaction reads (that is SQL Server's approach)."} | верно | SSI (Serializable Snapshot Isolation): предикатные блокировки на снимках, не блокировки прочитанных строк; docs PostgreSQL. |
T19-L1 0.91 c | HTTP and REST API | HTTP status 201 means the request resulted in a new resource being created. | «yes» Пояснение: HTTP 201 'Created' is returned when a request has been fulfilled and a new resource has been created, typically in response to a POST request.
Raw{"answer": "yes", "explanation": "HTTP 201 'Created' is returned when a request has been fulfilled and a new resource has been created, typically in response to a POST request."} | верно | 201 Created; обычно на POST, часто с Location; RFC 9110. |
T19-L2 1.22 c | HTTP and REST API | Which HTTP status means a successful request with an empty response body (e.g. after DELETE)? | «204» Пояснение: HTTP 204 'No Content' indicates a successful request with no response body, commonly used after DELETE operations.
Raw{"answer": 204, "explanation": "HTTP 204 'No Content' indicates a successful request with no response body, commonly used after DELETE operations."} | верно | 204 No Content; RFC 9110. |
T19-L3 4.78 c | HTTP and REST API | The DELETE method is idempotent per the HTTP specification: repeating the request for the same resource does not change the outcome. | «yes» Пояснение: RFC 9110 explicitly lists DELETE among the idempotent methods, meaning repeated identical DELETE requests have the same intended effect on the server as a single request.
Raw{"answer": "yes", "explanation": "RFC 9110 explicitly lists DELETE among the idempotent methods, meaning repeated identical DELETE requests have the same intended effect on the server as a single request."} | верно | RFC 9110: DELETE идемпотентен (как PUT); идемпотентность ≠ безопасность — ресурс удаляется при первом вызове. |
T19-L4 1.03 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 origin is permitted 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 origin is permitted to access the resource, not by the client."} | верно | Наоборот: заголовок шлёт СЕРВЕР в ответе, разрешая браузеру cross-origin запрос (CORS); в проекте nelmio/cors-bundle. |
T19-L5 1.1 c | HTTP and REST API | Status 429 Too Many Requests is used when a client exceeds a rate limit. | «yes» Пояснение: HTTP 429 Too Many Requests was defined in RFC 6585 specifically to indicate that the client has sent too many requests in a given time frame, i.e., it exceeded a rate limit.
Raw{"answer": "yes", "explanation": "HTTP 429 Too Many Requests was defined in RFC 6585 specifically to indicate that the client has sent too many requests in a given time frame, i.e., it exceeded a rate limit."} | верно | 429 (+ Retry-After); RFC 6585. В проекте symfony/rate-limiter. |
T19-L6 0.89 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.55 c | HTTP and REST API | Which HTTP header indicates the MIME type of the request or response body? | «content-type» Пояснение: The Content-Type HTTP header specifies the MIME type (media type) of the request or response body.
Raw{"answer": "Content-Type", "explanation": "The Content-Type HTTP header specifies the MIME type (media type) of the request or response body."} | верно | Content-Type: application/json и т.п. |
T19-L8 1.41 c | HTTP and REST API | PATCH is not required to be idempotent per RFC 5789, unlike PUT. | «yes» Пояснение: RFC 5789 explicitly states that PATCH is not idempotent by default, whereas PUT (defined in RFC 7231) is required to be idempotent.
Raw{"answer": "yes", "explanation": "RFC 5789 explicitly states that PATCH is not idempotent by default, whereas PUT (defined in RFC 7231) is required to be idempotent."} | верно | RFC 5789 прямо оговаривает: PATCH не гарантированно идемпотентен; PUT идемпотентен. |
T20-L1 1.75 c | Security and OAuth | Checking a password by comparing its hash to the stored hash with a plain == is sufficient. | «no» Пояснение: Using plain == is insufficient; you should use hash_equals() for a constant-time comparison (or at least ===) to avoid type-juggling and timing attacks.
Raw{"answer": "no", "explanation": "Using plain == is insufficient; you should use hash_equals() for a constant-time comparison (or at least ===) to avoid type-juggling and timing attacks."} | верно | Нужна постоянновременная проверка (password_verify) — timing-атаки; соль и алгоритм уже внутри хеша. |
T20-L2 1.32 c | Security and OAuth | A CSRF token is issued by the server (bound to the session) and verified server-side on unsafe requests (POST etc.). | «yes» Пояснение: CSRF tokens are generated by the server, tied to the user's session, and validated server-side on state-changing requests like POST to prevent forged cross-origin requests.
Raw{"answer": "yes", "explanation": "CSRF tokens are generated by the server, tied to the user's session, and validated server-side on state-changing requests like POST to prevent forged cross-origin requests."} | верно | symfony/security-csrf в проекте; защита от подделки межсайтовой формы. |
T20-L3 0.66 c | Security and OAuth | Which HTTP header enables the CSP (Content Security Policy) policy? | «content-security-policy» Пояснение: The Content-Security-Policy HTTP header is used to specify which sources of content are trusted by the browser, enabling CSP protection.
Raw{"answer": "Content-Security-Policy", "explanation": "The Content-Security-Policy HTTP header is used to specify which sources of content are trusted by the browser, enabling CSP protection."} | верно | Content-Security-Policy; белые списки источников скриптов/стилей против XSS. |
T20-L4 1.74 c | Security and OAuth | OAuth 2.0 is an authentication protocol: the access token tells you who the user is. | «no» Пояснение: OAuth 2.0 is an authorization protocol, not an authentication protocol; the access token grants permission to access resources, while it is the ID token (from OpenID Connect) that identifies who the user is.
Raw{"answer": "no", "explanation": "OAuth 2.0 is an authorization protocol, not an authentication protocol; the access token grants permission to access resources, while it is the ID token (from OpenID Connect) that identifies who the user is."} | верно | OAuth 2.0 — авторизация/делегирование доступа; аутентификацию добавляет OpenID Connect. В проекте knpuniversity/oauth2-client-bundle (yandex/github/google). |
T20-L5 1.67 c | Security and OAuth | XSS is prevented by validating input on the server before writing it to the database. | «no» Пояснение: XSS is primarily an output-side vulnerability prevented by encoding/escaping data when rendering it in the response, not by validating input before storing it in the database.
Raw{"answer": "no", "explanation": "XSS is primarily an output-side vulnerability prevented by encoding/escaping data when rendering it in the response, not by validating input before storing it in the database."} | верно | XSS лечится контекстным экранированием НА ВЫВОДЕ (Twig autoescape, CSP); валидация ввода не покрывает все контексты вывода. |
T20-L6 1.02 c | Security and OAuth | In the OAuth 2.0 authorization code flow, which parameter arrives at the redirect_uri and is exchanged for an access token? | «code» Пояснение: In the OAuth 2.0 authorization code flow, the authorization server redirects the user back to the redirect_uri with a 'code' parameter (the authorization code), which the client then exchanges for an access token.
Raw{"answer": "code", "explanation": "In the OAuth 2.0 authorization code flow, the authorization server redirects the user back to the redirect_uri with a 'code' parameter (the authorization code), which the client then exchanges for an access token."} | верно | Параметр code; обмен на токен POST-ом на /token с client_secret. |
T20-L7 0.84 c | Security and OAuth | A refresh token lives longer than an access token and allows obtaining a new access token without the user logging in again. | «yes» Пояснение: A refresh token has a longer expiration than an access token and is specifically designed to obtain new access tokens without requiring the user to re-authenticate.
Raw{"answer": "yes", "explanation": "A refresh token has a longer expiration than an access token and is specifically designed to obtain new access tokens without requiring the user to re-authenticate."} | верно | Стандартная схема OAuth/OIDC: короткий access + длинный refresh. |
T20-L8 1.52 c | Security and OAuth | A password salt must be kept secret: without it the hash cannot be verified. | «no» Пояснение: A salt does not need to be secret; it is typically stored alongside the hash and its purpose is uniqueness per user, not secrecy.
Raw{"answer": "no", "explanation": "A salt does not need to be secret; it is typically stored alongside the hash and its purpose is uniqueness per user, not secrecy."} | верно | Соль хранится открыто (password_hash включает её в строку хеша); секретность соли не нужна. |
T18-L1 0.87 c | Testing: PHPUnit | PHPUnit runs test methods of any class — extending TestCase is not required. | «no» Пояснение: PHPUnit requires test classes to extend PHPUnit\Framework\TestCase in order to be discovered and executed.
Raw{"answer": "no", "explanation": "PHPUnit requires test classes to extend PHPUnit\\Framework\\TestCase in order to be discovered and executed."} | верно | Тестом считается метод класса, наследующего 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 individual test method; setUpBeforeClass() is the one that runs once before all tests in the class.
Raw{"answer": "no", "explanation": "setUp() runs before each individual test method; setUpBeforeClass() is the one that runs once before all tests in the class."} | верно | setUp() — перед КАЖДЫМ тестом; один раз на класс — setUpBeforeClass(). Проверено живым счётчиком на PHPUnit 10.5. |
T18-L3 0.85 c | Testing: PHPUnit | A data provider lets a test run with exactly one set of arguments. | «no» Пояснение: A data provider is specifically designed to supply multiple sets of arguments so the same test method runs multiple times with different inputs.
Raw{"answer": "no", "explanation": "A data provider is specifically designed to supply multiple sets of arguments so the same test method runs multiple times with different inputs."} | верно | Наоборот: наборов может быть сколько угодно — тест выполняется по разу на каждый. Проверено на PHPUnit 10.5 (#[DataProvider]). |
T18-L4 0.76 c | Testing: PHPUnit | Which PHPUnit method declares an expectation that an exception of a given class is thrown? | «expectexception» Пояснение: PHPUnit's expectException() method declares an expectation that an exception of the given class will be thrown during test execution.
Raw{"answer": "expectException", "explanation": "PHPUnit's expectException() method declares an expectation that an exception of the given class will be thrown during test execution."} | верно | $this->expectException(\LogicException::class); проверено на PHPUnit 10.5. |
T18-L5 1.48 c | Testing: PHPUnit | In PHPUnit, a stub verifies which methods were called on it, while a mock only returns data. | «no» Пояснение: It's the opposite: a stub only returns predefined data, while a mock both returns data and verifies (records/sets expectations on) which methods were called.
Raw{"answer": "no", "explanation": "It's the opposite: a stub only returns predefined data, while a mock both returns data and verifies (records/sets expectations on) which methods were called."} | верно | Наоборот: стаб подставляет данные, мок проверяет взаимодействия (createStub/createMock); docs PHPUnit — Test Doubles. |
T18-L6 1.76 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+, docblock annotations like @dataProvider are deprecated in favor of PHP 8 attributes such as #[DataProvider].
Raw{"answer": "yes", "explanation": "In PHPUnit 10+, docblock annotations like @dataProvider are deprecated in favor of PHP 8 attributes such as #[DataProvider]."} | верно | Аннотация ещё парсится в PHPUnit 10/11 (AnnotationParser в 10.5.66), удаление — в 12; атрибут — стандарт. |
T18-L7 1.19 c | Testing: PHPUnit | PHPUnit does not allow one test to depend on the result of another. | «no» Пояснение: PHPUnit does allow test dependencies via the @depends annotation or the depend() method, letting one test use the return value of another.
Raw{"answer": "no", "explanation": "PHPUnit does allow test dependencies via the @depends annotation or the depend() method, letting one test use the return value of another."} | верно | Зависимости есть: #[Depends] — зависимый тест не запустится, еслиProducer упал. |
T18-L8 0.82 c | Testing: PHPUnit | Which PHPUnit command-line option makes tests run in random order? | «--random-order» Пояснение: The --random-order PHPUnit CLI option shuffles test execution order.
Raw{"answer": "--random-order", "explanation": "The --random-order PHPUnit CLI option shuffles test execution order."} | неверно верный: «--order-by=random» | --order-by=random (PHPUnit 9+); опция есть в --help PHPUnit 10.5 (проектная). |
T01-L9 3.7 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 (truncates toward zero), and the dot operator concatenates them into the string '3-3'.
Raw{"answer": "3-3", "explanation": "intdiv(7,2) returns 3 and intdiv(-7,2) returns -3 (truncates toward zero), and the dot operator concatenates them into the string '3-3'."} | верно | intdiv truncates toward zero: intdiv(-7, 2) = -3, not -4. |
T01-L10 1.84 c | Syntax and operators | What does this code output?
```php
echo -3 ** 2;
``` | «-9» Пояснение: In PHP, the ** operator has higher precedence than unary minus, so -3 ** 2 is parsed as -(3 ** 2) = -9.
Raw{"answer": -9, "explanation": "In PHP, the ** operator has higher precedence than unary minus, so -3 ** 2 is parsed as -(3 ** 2) = -9."} | верно | ** is right-associative and binds tighter than unary minus: -(3²). |
T02-L9 1.32 c | Types and comparisons | What does this code output?
```php
echo '1e1' == '10' ? 'true' : 'false';
``` | «true» Пояснение: Both '1e1' and '10' are numeric strings, so PHP compares them numerically: 1e1 (which equals 10) == 10 is true, so 'true' is echoed.
Raw{"answer": "true", "explanation": "Both '1e1' and '10' are numeric strings, so PHP compares them numerically: 1e1 (which equals 10) == 10 is true, so 'true' is echoed."} | верно | Both strings are numeric — compared as numbers: 10 == 10. |
T02-L10 2.32 c | Types and comparisons | What does this code output?
```php
switch ('a') {
case 0: echo 'zero'; break;
default: echo 'other';
}
``` | «zero» Пояснение: PHP's switch uses loose comparison (==), and 'a' == 0 evaluates to true because the non-numeric string 'a' is cast to the integer 0.
Raw{"answer": "zero", "explanation": "PHP's switch uses loose comparison (==), and 'a' == 0 evaluates to true because the non-numeric string 'a' is cast to the integer 0."} | неверно верный: «other» | PHP 8: 'a' == 0 → false (used to be true) — default fires. |
T03-L9 3.02 c | Strings | What does this code output?
```php
echo strtr('abc', ['a' => '1', 'ab' => '2']);
``` | «2c» Пояснение: strtr with an array replaces keys longest-first, so 'ab' is matched before 'a', resulting in '2c'.
Raw{"answer": "2c", "explanation": "strtr with an array replaces keys longest-first, so 'ab' is matched before 'a', resulting in '2c'."} | верно | strtr with an array prefers the longest matching key. |
T03-L10 3.2 c | Strings | What does this code output?
```php
echo '[' . substr('hello', -10) . ']';
``` | «[]» Пояснение: substr('hello', -10) returns an empty string because the absolute value of the start position (10) exceeds the string length (5), so the output is just the brackets '[]'.
Raw{"answer": "[]", "explanation": "substr('hello', -10) returns an empty string because the absolute value of the start position (10) exceeds the string length (5), so the output is just the brackets '[]'."} | неверно верный: «[hello]» | A negative start beyond the string is clamped to the beginning. |
T04-L9 1.57 c | Arrays | What does this code output?
```php
$a = ['k' => 1, 'n' => 2];
$b = ['k' => 9, 'm' => 3];
echo implode(',', array_keys($a + $b));
``` | «k,n,m» Пояснение: The array union operator (+) keeps $a's values for duplicate keys and appends $b's unique keys, so array_keys gives ['k','n','m'] which implode joins as 'k,n,m'.
Raw{"answer": "k,n,m", "explanation": "The array union operator (+) keeps $a's values for duplicate keys and appends $b's unique keys, so array_keys gives ['k','n','m'] which implode joins as 'k,n,m'."} | верно | The + operator: on duplicate string keys the left array wins. |
T04-L10 2.32 c | Arrays | What does this code output?
```php
$a = [[1, 'x', 2], [2, 'y', 1], [3, 'z', 2]];
usort($a, fn($p, $q) => $p[2] <=> $q[2]);
echo implode('', array_column($a, 1));
``` | «yxz» Пояснение: The array is sorted by the third element (index 2): [2,'y',1] (1), [1,'x',2] (2), [3,'z',2] (2), then array_column extracts index 1 giving ['y','x','z'], which implode concatenates to 'yxz'.
Raw{"answer": "yxz", "explanation": "The array is sorted by the third element (index 2): [2,'y',1] (1), [1,'x',2] (2), [3,'z',2] (2), then array_column extracts index 1 giving ['y','x','z'], which implode concatenates to 'yxz'."} | верно | Sorts are stable since 8.0: x and z keep their order on a tie. |
T05-L10 4.3 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» Пояснение: Spreading a named array maps values by key to parameters, so $a=5 and $b=1, and f returns 5-1=4.
Raw{"answer": 4, "explanation": "Spreading a named array maps values by key to parameters, so $a=5 and $b=1, and f returns 5-1=4."} | верно | String keys of a spread array become named arguments. |
T05-L9 5.38 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» Пояснение: First-class callable syntax $p->g(...) creates a Closure that captures the object reference; setting $p=null afterward doesn't affect the closure, so $f() still calls g() on the original object, returning the private $v which is 3.
Raw{"answer": 3, "explanation": "First-class callable syntax $p->g(...) creates a Closure that captures the object reference; setting $p=null afterward doesn't affect the closure, so $f() still calls g() on the original object, returning the private $v which is 3."} | верно | First-class callable syntax binds $this at creation time. |
T06-L9 0.97 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, so it returns the name of the class the object was instantiated from, which is B.
Raw{"answer": "B", "explanation": "static::class uses late static binding, so it returns the name of the class the object was instantiated from, which is B."} | верно | Late static binding: static::class is the receiver's class. |
T06-L10 7.75 c | OOP: classes and inheritance | What does this code output on PHP 8.5?
```php
class C
{
public int $x = 0 {
set { $this->x = $value * 2; }
}
}
$c = new C;
$c->x = 5;
echo $c->x;
``` | «10» Пояснение: The set hook multiplies the assigned value by 2 (5*2=10), storing 10 as the backing value; no get hook is defined, so reading the property returns 10.
Raw{"answer": 10, "explanation": "The set hook multiplies the assigned value by 2 (5*2=10), storing 10 as the backing value; no get hook is defined, so reading the property returns 10."} | верно | Inside the set hook, $this->x writes the backing store (no recursion): 5*2. |
T07-L9 1.46 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 means f() returns 'B', and TA::f as g aliases it so g() returns 'A', giving concatenation 'BA'.
Raw{"answer": "BA", "explanation": "TB::f insteadof TA means f() returns 'B', and TA::f as g aliases it so g() returns 'A', giving concatenation 'BA'."} | верно | insteadof picks the implementation; as keeps the other under an alias. |
T07-L10 1.33 c | Interfaces, traits, enum | What does this code output?
```php
trait Counter
{
public static int $n = 0;
}
class CX { use Counter; }
class CY { use Counter; }
CX::$n = 1;
echo CY::$n;
``` | «0» Пояснение: Each class that uses a trait gets its own independent copy of the static property, so modifying CX::$n does not affect CY::$n.
Raw{"answer": 0, "explanation": "Each class that uses a trait gets its own independent copy of the static property, so modifying CX::$n does not affect CY::$n."} | верно | A trait's static property is copied into each consuming class. |
T08-L10 0.82 c | Exceptions and errors | What does this code output?
```php
function f(): int
{
try { return 1; } finally { return 2; }
}
echo f();
``` | «2» Пояснение: In PHP, when both try and finally blocks contain return statements, the return value from the finally block overrides the one from the try block, so the function returns 2.
Raw{"answer": 2, "explanation": "In PHP, when both try and finally blocks contain return statements, the return value from the finally block overrides the one from the try block, so the function returns 2."} | верно | A return in finally overrides the return from try. |
T08-L9 1.27 c | Exceptions and errors | What does this code output?
```php
try {
try {
throw new RuntimeException('first');
} finally {
throw new LogicException('second');
}
} catch (LogicException $e) {
echo $e->getMessage();
}
``` | «second» Пояснение: When a finally block throws an exception, it replaces the original exception, so the LogicException('second') propagates and is caught by the outer catch.
Raw{"answer": "second", "explanation": "When a finally block throws an exception, it 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.42 c | Namespaces and autoloading | What does this code output?
```php
namespace N;
use App\Foo as Baz;
echo Baz::class . '|' . \Baz::class;
``` | «app\foo|baz» Пояснение: Baz::class resolves to App\Foo due to the use alias, while \Baz::class refers to the global namespace class Baz.
Raw{"answer": "App\\Foo|Baz", "explanation": "Baz::class resolves to App\\Foo due to the use alias, while \\Baz::class refers to the global namespace class Baz."} | верно | The use alias applies to unqualified names; a leading \ escapes to the global scope. |
T09-L10 3.04 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 the global class Foo which doesn't exist (the class is Ns\Foo), while class_exists('Ns\Foo') finds the class defined in the Ns namespace.
Raw{"answer": "noyes", "explanation": "class_exists('Foo') looks for the global class Foo which doesn't exist (the class is Ns\\Foo), while class_exists('Ns\\Foo') finds the class defined in the Ns namespace."} | верно | Dynamic names are not resolved against the namespace — 'Foo' is the global class. |
T10-L9 1.32 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» Пояснение: foreach by reference leaves $v as a reference to the last element, so $v=99 modifies $a[2] to 99.
Raw{"answer": "1,2,99", "explanation": "foreach by reference leaves $v as a reference to the last element, so $v=99 modifies $a[2] to 99."} | верно | After a by-ref foreach, $v remains a reference to the last element. |
T10-L10 3.61 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» Пояснение: Since B does not override inc(), both $a->inc() and $b->inc() call the same method with the same static variable: 1, 2, then 3.
Raw{"answer": 3, "explanation": "Since B does not override inc(), both $a->inc() and $b->inc() call the same method with the same static variable: 1, 2, then 3."} | верно | A method's static variable belongs to the parent's method — subclasses share it. |
T11-L9 1.56 c | Generators, iterators, SPL | What does this code output?
```php
function g(): Generator
{
$x = yield 1;
return $x + 1;
}
$g = g();
$g->send(10);
echo $g->getReturn();
``` | «11» Пояснение: send(10) assigns 10 to $x, then the generator returns $x + 1 = 11, which is retrieved by getReturn().
Raw{"answer": 11, "explanation": "send(10) assigns 10 to $x, then the generator returns $x + 1 = 11, which is retrieved by getReturn()."} | верно | send() resumes the generator: $x = 10, return 10+1. |
T11-L10 1.65 c | Generators, iterators, SPL | What does this code output?
```php
function inner(): Generator
{
yield 1;
yield 2;
return 'ok';
}
function outer(): Generator
{
$r = yield from inner();
yield $r;
}
echo implode(',', iterator_to_array(outer()));
``` | «1,2,ok» Пояснение: yield from inner() delegates yielding of 1 and 2, captures inner's return value 'ok' into $r, then outer yields $r, so iterator_to_array produces [1, 2, 'ok'] and implode gives '1,2,ok'.
Raw{"answer": "1,2,ok", "explanation": "yield from inner() delegates yielding of 1 and 2, captures inner's return value 'ok' into $r, then outer yields $r, so iterator_to_array produces [1, 2, 'ok'] and implode gives '1,2,ok'."} | неверно верный: «ok,2» | yield from does not advance the outer auto-key: yield $r gets key 0 and overwrites the 1 — 'ok' comes out first. |
T12-L9 1.3 c | Configuration and security | What does this code output?
```php
$hash = password_hash('x', PASSWORD_BCRYPT, ['cost' => 4]);
echo password_needs_rehash($hash, PASSWORD_BCRYPT, ['cost' => 4]) ? 'yes' : 'no';
echo password_needs_rehash($hash, PASSWORD_BCRYPT, ['cost' => 5]) ? 'yes' : 'no';
``` | «noyes» Пояснение: The first call checks if a cost-4 hash needs rehashing at cost 4 (no), the second checks at cost 5 (yes), so the output is 'noyes'.
Raw{"answer": "noyes", "explanation": "The first call checks if a cost-4 hash needs rehashing at cost 4 (no), the second checks at cost 5 (yes), so the output is 'noyes'."} | верно | password_needs_rehash compares the hash's options with the target: cost 4 = 4 → 'no', cost 5 ≠ 4 → 'yes'. |
T12-L10 4.48 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» Пояснение: E_STRICT (2048) was removed from E_ALL starting in PHP 8.4, so in PHP 8.5 the bitwise AND yields 0, making the condition true.
Raw{"answer": "strict-out", "explanation": "E_STRICT (2048) was removed from E_ALL starting in PHP 8.4, so in PHP 8.5 the bitwise AND yields 0, making the condition true."} | верно | Since PHP 8.4, E_STRICT is out of E_ALL: the 2048 bit is unset → 'strict-out' (2048 is the historical E_STRICT bit). |
T13-L9 2.93 c | Symfony | What does this code output?
```php
use Symfony\Component\HttpFoundation\Request;
$r = Request::create('/demo', 'GET', [], [], [], ['HTTP_X_TOKEN' => 'abc']);
echo $r->headers->get('X-Token') === 'abc' ? 'mapped' : 'missing';
``` | «mapped» Пояснение: Symfony's Request::create maps the HTTP_X_TOKEN server variable to the header 'x-token', and HeaderBag::get() is case-insensitive, so get('X-Token') returns 'abc', making the strict comparison true.
Raw{"answer": "mapped", "explanation": "Symfony's Request::create maps the HTTP_X_TOKEN server variable to the header 'x-token', and HeaderBag::get() is case-insensitive, so get('X-Token') returns 'abc', making the strict comparison true."} | верно | 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.03 c | Symfony | What does this code output?
```php
use Symfony\Component\EventDispatcher\EventDispatcher;
use Symfony\Contracts\EventDispatcher\Event;
$d = new EventDispatcher();
$out = '';
$d->addListener('e', function () use (&$out) { $out .= 'B'; }, 10);
$d->addListener('e', function () use (&$out) { $out .= 'A'; });
$d->addListener('e', function () use (&$out) { $out .= 'C'; }, 5);
$d->dispatch(new Event(), 'e');
echo $out;
``` | «bca» Пояснение: Listeners are invoked in descending priority order: B (10), C (5), A (0 default), so the output is 'BCA'.
Raw{"answer": "BCA", "explanation": "Listeners are invoked in descending priority order: B (10), C (5), A (0 default), so the output is 'BCA'."} | верно | Listeners run by descending priority: 10 (B), 5 (C), 0 (A). |
T14-L10 2.12 c | Doctrine | Given: Doctrine ORM 3, an EntityManager on in-memory SQLite, entity User with an auto-increment primary key. The users table is empty. What does this code output?
```php
$u = new User(name: 'A');
$em->persist($u);
$em->flush();
$a = $em->find(User::class, $u->getId());
$b = $em->find(User::class, $u->getId());
echo spl_object_id($a) === spl_object_id($b) ? 'same' : 'diff';
``` | «same» Пояснение: Doctrine's UnitOfWork maintains an identity map, so repeated find() calls with the same identifier return the same object instance rather than creating new ones.
Raw{"answer": "same", "explanation": "Doctrine's UnitOfWork maintains an identity map, so repeated find() calls with the same identifier return the same object instance rather than creating new ones."} | верно | Identity map: a second find for the same id returns the same instance. |
T14-L9 3.97 c | Doctrine | Given: Doctrine ORM 3, an EntityManager on in-memory SQLite, entity User with an auto-increment primary key. The users table is empty. What does this code output?
```php
$u = new User(name: 'B');
$em->persist($u);
$em->remove($u);
$em->flush();
echo count($em->getConnection()->fetchAllAssociative('SELECT * FROM users'));
``` | «0» Пояснение: When an entity is persisted and then removed before any flush, Doctrine cancels the pending INSERT during flush and issues no DELETE (the row was never in the DB), leaving the table empty.
Raw{"answer": 0, "explanation": "When an entity is persisted and then removed before any flush, Doctrine cancels the pending INSERT during flush and issues no DELETE (the row was never in the DB), leaving the table empty."} | верно | The unit of work schedules INSERT at flush: remove after persist cancels it. |
T15-L10 1.08 c | PostgreSQL | What does this SQL query return (PostgreSQL 17)?
```sql
CREATE TEMP TABLE t (x int);
INSERT INTO t VALUES (1), (NULL);
SELECT count(x) FROM t;
``` | «1» Пояснение: COUNT(x) counts only non-NULL values in column x; there is one row with value 1 and one row with NULL, so the result is 1.
Raw{"answer": 1, "explanation": "COUNT(x) counts only non-NULL values in column x; there is one row with value 1 and one row with NULL, so the result is 1."} | верно | count(column) skips NULLs; count(*) would return 2. |
T15-L9 1.55 c | PostgreSQL | What does this SQL query return (PostgreSQL 17)?
```sql
CREATE TEMP TABLE t (id int, x int);
INSERT INTO t VALUES (1, 10), (2, 20), (3, 30);
SELECT string_agg(s::text, ',' ORDER BY id) FROM (
SELECT id, sum(x) OVER (ORDER BY id) AS s FROM t
) q;
``` | «10,30,60» Пояснение: The window function computes running sums (10, 30, 60), and string_agg concatenates them with commas in id order.
Raw{"answer": "10,30,60", "explanation": "The window function computes running sums (10, 30, 60), and string_agg concatenates them with commas in id order."} | верно | With ORDER BY the default window frame is running (start to current row). |
T16-L9 4.95 c | Symfony: Messenger | What does this code output?
```php
use Symfony\Component\Messenger\MessageBus;
use Symfony\Component\Messenger\Middleware\MiddlewareInterface;
use Symfony\Component\Messenger\Middleware\StackInterface;
use Symfony\Component\Messenger\Envelope;
final class Trace implements MiddlewareInterface
{
public function __construct(private string $tag) {}
public function handle(Envelope $e, StackInterface $stack): Envelope
{
echo $this->tag;
return $stack->next()->handle($e, $stack);
}
}
$bus = new MessageBus([new Trace('M1'), new Trace('M2')]);
$bus->dispatch(new Envelope(new stdClass()));
``` | «m1m2» Пояснение: The middleware stack processes Trace('M1') first (echoes 'M1'), then passes to Trace('M2') (echoes 'M2'), which passes to the default last handler, so the concatenated output is 'M1M2'.
Raw{"answer": "M1M2", "explanation": "The middleware stack processes Trace('M1') first (echoes 'M1'), then passes to Trace('M2') (echoes 'M2'), which passes to the default last handler, so the concatenated output is 'M1M2'."} | верно | The first-added middleware runs first (outermost). |
T16-L10 3.98 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 in the HandlersLocator for the given message type, so both closures execute: $n += 1 then $n += 10, giving 11.
Raw{"answer": 11, "explanation": "HandleMessageMiddleware calls all handlers in the HandlersLocator for the given 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.23 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 hits the unique constraint and is skipped due to ON CONFLICT DO NOTHING, leaving exactly one row.
Raw{"answer": 1, "explanation": "The first INSERT succeeds, the second hits the unique constraint and is skipped due to ON CONFLICT DO NOTHING, leaving exactly one row."} | верно | ON CONFLICT DO NOTHING skips the duplicate: one insert. |
T17-L10 1.65 c | PostgreSQL: transactions and indexes | What does this sequence of psql commands output?
```sql
BEGIN;
CREATE TEMP TABLE t (a int, UNIQUE (a) DEFERRABLE INITIALLY DEFERRED);
INSERT INTO t VALUES (1);
INSERT INTO t VALUES (1);
SELECT count(*) FROM t;
``` | «2» Пояснение: The UNIQUE constraint is DEFERRABLE INITIALLY DEFERRED, so it is only checked at transaction end, allowing both duplicate inserts to succeed within the transaction.
Raw{"answer": 2, "explanation": "The UNIQUE constraint is DEFERRABLE INITIALLY DEFERRED, so it is only checked at transaction end, allowing both duplicate inserts to succeed within the transaction."} | верно | DEFERRED postpones the uniqueness check to COMMIT — count sees 2 rows. |
T18-L9 2.8 c | Testing: PHPUnit | How many tests will this command run?
```php
use PHPUnit\Framework\TestCase;
use PHPUnit\Framework\Attributes\DataProvider;
final class CalcTest extends TestCase
{
public static function prov(): array
{
return [[1], [2], [3]];
}
#[DataProvider('prov')]
public function test_sum(int $x): void
{
$this->assertTrue($x > 0);
}
#[DataProvider('prov')]
public function test_sum_abs(int $x): void
{
$this->assertTrue($x > 0);
}
public function test_other(): void
{
$this->assertTrue(true);
}
}
```
Command: `phpunit CalcTest.php --filter test_sum` (PHPUnit 10.5) | «6» Пояснение: The --filter test_sum regex matches both test_sum (3 data sets) and test_sum_abs (3 data sets), totaling 6 tests.
Raw{"answer": 6, "explanation": "The --filter test_sum regex 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.57 c | Testing: PHPUnit | How many tests will this command run, and how many of them will fail? Answer with two comma-separated numbers (ran, failed).
```php
use PHPUnit\Framework\TestCase;
use PHPUnit\Framework\Attributes\DataProvider;
final class Calc2Test extends TestCase
{
public function prov(): array
{
return [[1], [-1]];
}
#[DataProvider('prov')]
public function test_x(int $x): void
{
$this->assertTrue($x > 0);
}
}
```
Command: `phpunit Calc2Test.php` (PHPUnit 10.5) | «2, 1» Пояснение: The DataProvider supplies two datasets ([1] and [-1]), so two tests run; the second one fails because -1 > 0 is false.
Raw{"answer": "2, 1", "explanation": "The DataProvider supplies two datasets ([1] and [-1]), so two tests run; the second one 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.89 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 automatically sets the HTTP method to POST when no explicit method is specified.
Raw{"answer": "POST", "explanation": "The -d flag in curl automatically sets the HTTP method to POST when no explicit method is specified."} | верно | -d/-F switches curl to POST by default. |
T19-L10 1.4 c | HTTP and REST API | Which HTTP method does this command send?
```bash
curl -s -G -d 'a=1' http://demo.local/api
``` | «get» Пояснение: The -G flag forces curl to use the GET method, appending -d data as a query string to the URL instead of sending a POST body.
Raw{"answer": "GET", "explanation": "The -G flag forces curl to use the GET method, appending -d data as a query string to the URL instead of sending a POST body."} | верно | -G turns -d data into the query string; the method stays GET. |
T20-L9 1.58 c | Security and OAuth | A client hits the token endpoint (RFC 6749) with a non-existent client_id. What value of the error field does the endpoint return? | «invalid_client» Пояснение: Per RFC 6749 Section 5.2, when the client authentication fails (e.g., non-existent client_id), the token endpoint returns the error value 'invalid_client'.
Raw{"answer": "invalid_client", "explanation": "Per RFC 6749 Section 5.2, when the client authentication fails (e.g., non-existent client_id), the token endpoint returns the error value 'invalid_client'."} | верно | Unknown client → invalid_client (RFC 6749 §5.2). |
T20-L10 1.13 c | Security and OAuth | OAuth 2.0: the client started the flow with response_type=token. In which part of the redirect_uri does the authorization server pass the access_token? | «fragment» Пояснение: In the OAuth 2.0 implicit flow (response_type=token), the access token is returned in the URI fragment (after '#') of the redirect_uri, not in the query string, to avoid exposing it in server logs.
Raw{"answer": "fragment", "explanation": "In the OAuth 2.0 implicit flow (response_type=token), the access token is returned in the URI fragment (after '#') of the redirect_uri, not in the query string, to avoid exposing it in server logs."} | верно | The implicit flow passes the token in the URL fragment (#) — it never reaches the server. |
T21-L9 1.09 c | Twig | What does this Twig template output?
```twig
{{ false|default(2) * 3 }}
``` | «0» Пояснение: The default filter only replaces null/undefined values, so false is kept, and false * 3 equals 0.
Raw{"answer": 0, "explanation": "The default filter only replaces null/undefined values, so false is kept, and false * 3 equals 0."} | неверно верный: «6» | default replaces exactly false/null/''/[] — false becomes 2, 2*3 = 6; the naive 'default is for undefined only' yields 0. |
T21-L10 8.05 c | Twig | What exception class does render() of this template throw?
```twig
{{ 'a' ~ 1 + 2 }}
``` | «a3» Пояснение: In Twig, the '+' operator has higher precedence than '~', so 'a' ~ 1 + 2 is parsed as 'a' ~ (1+2) = 'a' ~ 3 = 'a3', which renders successfully without throwing an exception.
Raw{"answer": "a3", "explanation": "In Twig, the '+' operator has higher precedence than '~', so 'a' ~ 1 + 2 is parsed as 'a' ~ (1+2) = 'a' ~ 3 = 'a3', which renders successfully without throwing an exception."} | неверно верный: «runtimeerror» | In Twig ~ binds tighter than +: ('a' ~ 1) + 2 → string + int → a render error (RuntimeError). |
T22-L9 4.84 c | Symfony: Security and forms | What does this code output?
```php
use Symfony\Component\Validator\Validation;
use Symfony\Component\Validator\Constraints as Assert;
$v = Validation::createValidator();
echo count($v->validate([''], [new Assert\NotBlank()]));
``` | «0» Пояснение: The value [''] is an array with one element, and Assert\NotBlank only considers an array blank if it is empty (count === 0), so no violations are found.
Raw{"answer": 0, "explanation": "The value [''] is an array with one element, and Assert\\NotBlank only considers an array blank if it is empty (count === 0), so no violations are found."} | верно | NotBlank treats null, '', [] as blank — the array [''] is not blank. |
T22-L10 2.33 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);
}
``` | «symfony\component\form\exception\logicexception» Пояснение: Calling isValid() on a Symfony form that has not been submitted throws a LogicException, which is caught and its class name is echoed.
Raw{"answer": "Symfony\\Component\\Form\\Exception\\LogicException", "explanation": "Calling isValid() on a Symfony form that has not been submitted throws a LogicException, which is caught and its class name is echoed."} | верно | isValid() on a non-submitted form throws LogicException, it does not return false. |
T23-L9 1.23 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 DI container services are singletons by default, so calling get('a') twice returns the same stdClass instance.
Raw{"answer": "same", "explanation": "Symfony DI container services are singletons by default, so calling get('a') twice returns the same stdClass instance."} | верно | Container services are shared: two get() calls yield one instance. |
T23-L10 21.43 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');
``` | «%greeting!%» Пояснение: The parameter reference pattern %name% expects a valid parameter name; since '!' is not a valid parameter name character, the reference %greeting!% does not resolve to the defined parameter 'greeting', so the string is left unchanged.
Raw{"answer": "%greeting!%", "explanation": "The parameter reference pattern %name% expects a valid parameter name; since '!' is not a valid parameter name character, the reference %greeting!% does not resolve to the defined parameter 'greeting', so the string is left unchanged."} | неверно верный: «hi bob!» | compile() resolves %-references transitively: %greeting% → 'hi %name%' → 'hi Bob!', the answer assembles over two hops. |
T24-L9 1.17 c | Bootstrap | What is the max-width of .container in Bootstrap 5.3 at a 992px viewport? | «960px» Пояснение: In Bootstrap 5.3, at the 992px (lg) breakpoint, the .container max-width is 960px.
Raw{"answer": "960px", "explanation": "In Bootstrap 5.3, at the 992px (lg) breakpoint, the .container max-width is 960px."} | верно | 5.x container widths: 540/720/960/1140/1320 (sm–xxl); 992 → 960px. |
T24-L10 1.95 c | Bootstrap | Which utility sets the text color in Bootstrap 5.3 for `<p class="text-danger text-primary">…</p>`? Answer with the winning class name. | «text-danger» Пояснение: In Bootstrap 5.3's CSS, text-danger is declared after text-primary, so with equal specificity it wins the cascade.
Raw{"answer": "text-danger", "explanation": "In Bootstrap 5.3's CSS, text-danger is declared after text-primary, so with equal specificity it wins the cascade."} | верно | Specificity ties — the later rule wins: text-danger is declared after text-primary. |
T25-L9 1.44 c | Clean architecture | Layers: Domain, Application, Infrastructure. Deptrac rules: Application → Domain; Infrastructure → Domain, Application; Domain → Domain only.
How many violations will deptrac report for this class?
```php
namespace App\Domain;
use App\Application\PlaceOrder;
use App\Infrastructure\Db;
class OrderService
{
public function __construct(
private PlaceOrder $handler,
private Db $db,
) {}
}
``` | «2» Пояснение: The Domain class depends on both Application (PlaceOrder) and Infrastructure (Db), but Domain is only allowed to depend on Domain, so both are violations.
Raw{"answer": 2, "explanation": "The Domain class depends on both Application (PlaceOrder) and Infrastructure (Db), but Domain is only allowed to depend on Domain, so both are violations."} | верно | Domain may depend only on Domain: PlaceOrder (Application) + Db (Infrastructure) = 2. |
T25-L10 1.23 c | Clean architecture | Layers: Domain, Application, Infrastructure. Deptrac rules: Application → Domain; Infrastructure → Domain, Application; Domain → Domain only.
How many violations will deptrac report for this class?
```php
namespace App\Domain;
use App\Application\PlaceOrder;
use App\Infrastructure\Db;
class BillingService
{
public function __construct(
private PlaceOrder $handler,
private Db $db,
private \App\Infrastructure\Logger $logger,
) {}
}
``` | «3» Пояснение: The Domain class depends on Application (PlaceOrder) and Infrastructure (Db, Logger), but Domain is only allowed to depend on Domain, giving 3 violations.
Raw{"answer": 3, "explanation": "The Domain class depends on Application (PlaceOrder) and Infrastructure (Db, Logger), but Domain is only allowed to depend on Domain, giving 3 violations."} | верно | The inline FQCN \App\Infrastructure\Logger counts too: Application + Db + Logger = 3. |
T26-L10 1.26 c | DDD | What does this code output?
```php
final class Money
{
public function __construct(public readonly int $amount) {}
public function add(Money $o): Money
{
return new self($this->amount + $o->amount);
}
}
$a = new Money(10);
$c = $a->add(new Money(5));
echo $a->amount . ',' . $c->amount;
``` | «10,15» Пояснение: $a->amount is 10 and $c->amount is 10+5=15, so the concatenated string is '10,15'.
Raw{"answer": "10,15", "explanation": "$a->amount is 10 and $c->amount is 10+5=15, so the concatenated string is '10,15'."} | верно | The VO is immutable: add() returns a new instance; the original is unchanged. |
T26-L9 1.34 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 'a' remains in the array and count() returns 1.
Raw{"answer": 1, "explanation": "The remove() method throws a DomainException before unsetting the item, so 'a' remains in the array and count() returns 1."} | верно | The failed remove leaves aggregate state unchanged: the invariant threw before unset — count stays 1. |
VC-L9 3.57 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 hi() which returns the string 'hi', and echoes it.
Raw{"answer": "hi", "explanation": "The code instantiates class C, calls hi() which returns the string 'hi', and echoes it."} | верно | Since 8.4, new in a method chain works without wrapping parentheses. |
VC-L10 5.83 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» Пояснение: After newLazyGhost the object is uninitialized (prints 'yes'); accessing $o->v triggers the initialization callback, so the second check prints 'no'.
Raw{"answer": "yesno", "explanation": "After newLazyGhost the object is uninitialized (prints 'yes'); accessing $o->v triggers the initialization callback, so the second check prints 'no'."} | верно | newLazyGhost (8.4): the object stays lazy until first access — reading a property initializes it and clears the flag. |
T28-L9 1.3 c | Symfony: versions | The project was upgraded from Symfony 6.4 to 8.1. What does this code output on 8.1?
```php
echo class_exists(\Symfony\Component\Security\Guard\AbstractGuardAuthenticator::class)
? 'yes' : 'no';
``` | «no» Пояснение: The Security Guard component (including AbstractGuardAuthenticator) was removed in Symfony 6.0, so it does not exist in 8.1.
Raw{"answer": "no", "explanation": "The Security Guard component (including AbstractGuardAuthenticator) was removed in Symfony 6.0, so it does not exist in 8.1."} | верно | Guard authentication was removed in Symfony 7.0 — the class is gone in 8.1. |
T28-L10 1.77 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.1), while AttributeClassLoader (introduced in 6.1) still exists in 8.1.
Raw{"answer": "noyes", "explanation": "AnnotationClassLoader was removed in Symfony 7.0 (deprecated in 6.1), while AttributeClassLoader (introduced in 6.1) still exists in 8.1."} | верно | Annotation loaders were removed in 7.0; only attribute loaders remain (Annotation→Attribute). |