Пример запроса (первая клетка). System одинаковый во всех запросах прогона, user — свой вопрос для каждой клетки:
| Клетка | Тема | Утверждение | Ответ |
Результат | Обоснование |
T01-L1 4.12 c | Syntax and operators | Double-quoted and single-quoted strings are processed identically; the difference is only in speed. | «no» Пояснение: Double-quoted strings interpolate variables and support more escape sequences, while single-quoted strings do not; the difference is functional, not just speed.
Raw{"answer": "no", "explanation": "Double-quoted strings interpolate variables and support more escape sequences, while single-quoted strings do not; the difference is functional, not just speed."} | верно | В двойных кавычках работают интерполяция переменных и escape-последовательности, в одинарных — нет. |
T01-L2 1.75 c | Syntax and operators | The ?? operator follows isset semantics and raises no warnings for undefined variables. | «yes» Пояснение: The ?? operator is equivalent to isset($var) ? $var : default, and isset() returns false (not a warning) for undefined variables, so ?? never triggers undefined variable warnings.
Raw{"answer": "yes", "explanation": "The ?? operator is equivalent to isset($var) ? $var : default, and isset() returns false (not a warning) for undefined variables, so ?? never triggers undefined variable warnings."} | верно | ?? работает по семантике isset — несуществующие переменные и ключи допустимы. |
T01-L3 0.67 c | Syntax and operators | What will this print: echo 'a', 'b'; | «ab» Пояснение: PHP's echo statement accepts multiple comma-separated arguments and prints them sequentially without any separator.
Raw{"answer": "ab", "explanation": "PHP's echo statement accepts multiple comma-separated arguments and prints them sequentially without any separator."} | верно | echo принимает список аргументов: ab. |
T01-L4 2.88 c | Syntax and operators | print returns the value 1 and can be used inside an expression. | «yes» Пояснение: In PHP, print is a language construct that always returns the integer 1, and because it returns a value it can be used within expressions (unlike echo, which returns nothing).
Raw{"answer": "yes", "explanation": "In PHP, print is a language construct that always returns the integer 1, and because it returns a value it can be used within expressions (unlike echo, which returns nothing)."} | верно | print — выражение со значением 1, в отличие от echo, который значения не возвращает. |
T01-L5 1.1 c | Syntax and operators | The ?: (elvis) operator returns its left operand when it is falsy. | «no» Пояснение: The Elvis operator ($a ?: $b) returns the left operand when it is truthy, not falsy; when falsy, it returns the right operand.
Raw{"answer": "no", "explanation": "The Elvis operator ($a ?: $b) returns the left operand when it is truthy, not falsy; when falsy, it returns the right operand."} | верно | Наоборот: $a ?: $b возвращает $a, если он истинный, иначе $b. |
T01-L6 2.18 c | Syntax and operators | In PHP 8, the concatenation operator (.) has lower precedence than addition and subtraction. | «no» Пояснение: In PHP, the concatenation operator (.), addition (+), and subtraction (-) all share the same precedence level and are left-associative.
Raw{"answer": "no", "explanation": "In PHP, the concatenation operator (.), addition (+), and subtraction (-) all share the same precedence level and are left-associative."} | неверно верный: «yes» | С PHP 8 (RFC concat precedence) '.' имеет приоритет ниже арифметики: 'сумма: ' . 2 + 3 → 'сумма: 5' (в PHP 7 было иначе). |
T01-L7 1.02 c | Syntax and operators | The expression 2 ** 3 ** 2 in PHP evaluates as (2 ** 3) ** 2, that is, 64. | «no» Пояснение: The ** operator in PHP is right-associative, so 2 ** 3 ** 2 is evaluated as 2 ** (3 ** 2) = 2 ** 9 = 512, not (2 ** 3) ** 2 = 64.
Raw{"answer": "no", "explanation": "The ** operator in PHP is right-associative, so 2 ** 3 ** 2 is evaluated as 2 ** (3 ** 2) = 2 ** 9 = 512, not (2 ** 3) ** 2 = 64."} | верно | ** право-ассоциативен: 2 ** (3 ** 2) = 2 ** 9 = 512. |
T01-L8 1.15 c | Syntax and operators | What string will this print: echo 'sum: ' . 2 + 3; (PHP 8)? | «sum: 5» Пояснение: The + operator has higher precedence than the . (concatenation) operator, so 2+3 is evaluated first, then concatenated with 'sum: '.
Raw{"answer": "sum: 5", "explanation": "The + operator has higher precedence than the . (concatenation) operator, so 2+3 is evaluated first, then concatenated with 'sum: '. "} | верно | Парная к verify-клетке про приоритет: 'сумма: 5'. |
T02-L1 1.51 c | Types and comparisons | With strict comparison (===), arrays are considered equal regardless of element order. | «no» Пояснение: With ===, arrays must have the same key/value pairs in the same order to be considered equal; order only doesn't matter with ==.
Raw{"answer": "no", "explanation": "With ===, arrays must have the same key/value pairs in the same order to be considered equal; order only doesn't matter with ==."} | верно | === для массивов требует совпадения и значений, и их порядка. |
T02-L2 1.22 c | Types and comparisons | The comparison 0 == false returns false because it is a strict comparison. | «no» Пояснение: 0 == false uses loose comparison (==) and actually returns true; strict comparison would be === which returns false.
Raw{"answer": "no", "explanation": "0 == false uses loose comparison (==) and actually returns true; strict comparison would be === which returns false."} | верно | Наоборот: == — нестрогое сравнение и возвращает true; строгое — это === (0 === false → false). |
T02-L3 2.0 c | Types and comparisons | In PHP 8, the expression "abc" == 0 returns true. | «no» Пояснение: In PHP 8, when comparing a non-numeric string like 'abc' with an integer using ==, the integer is cast to a string, so 'abc' == '0' evaluates to false (unlike PHP 7 where it was true).
Raw{"answer": "no", "explanation": "In PHP 8, when comparing a non-numeric string like 'abc' with an integer using ==, the integer is cast to a string, so 'abc' == '0' evaluates to false (unlike PHP 7 where it was true)."} | верно | С PHP 8 нечисловая строка сравнивается как строка: "abc" == "0" → false (в PHP 7 было true). |
T02-L4 0.91 c | Types and comparisons | Under loose comparison, null equals 0, the empty string, and false at the same time. | «yes» Пояснение: In PHP, loose comparison (==) treats null as equal to 0, empty string "", and false, all evaluating to true.
Raw{"answer": "yes", "explanation": "In PHP, loose comparison (==) treats null as equal to 0, empty string \"\", and false, all evaluating to true."} | верно | null == 0, null == "" и null == false — все true. |
T02-L5 2.39 c | Types and comparisons | What does the expression (int) '42abc' return? | «42» Пояснение: PHP casts the string by reading from left to right until it hits a non-numeric character, so '42abc' becomes the integer 42.
Raw{"answer": 42, "explanation": "PHP casts the string by reading from left to right until it hits a non-numeric character, so '42abc' becomes the integer 42."} | верно | Ведущая числовая часть: 42, без ошибок и warning. |
T02-L6 0.84 c | Types and comparisons | What does the expression '5' + 5 return? | «10» Пояснение: PHP coerces the string '5' to an integer when using the + operator, so 5 + 5 = 10.
Raw{"answer": 10, "explanation": "PHP coerces the string '5' to an integer when using the + operator, so 5 + 5 = 10."} | верно | Числовая строка приводится: int 10. |
T02-L7 1.37 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 true that casts to "1".
Raw{"answer": "no", "explanation": "In PHP, casting false to a string results in an empty string \"\", not \"0\"; it is true that casts to \"1\"."} | верно | false → "", true → "1". |
T02-L8 1.68 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.
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."} | верно | Двоичная погрешность float: 0.1 + 0.2 = 0.30000000000000004. |
T03-L1 2.0 c | Strings | strrev() correctly reverses a UTF-8 string. | «no» Пояснение: strrev() reverses a string byte-by-byte, which splits multi-byte UTF-8 characters and produces garbled output; you need mb_ functions (e.g., mb_strtolower with mbstr) to correctly reverse UTF-8.
Raw{"answer": "no", "explanation": "strrev() reverses a string byte-by-byte, which splits multi-byte UTF-8 characters and produces garbled output; you need mb_ functions (e.g., mb_strtolower with mbstr) to correctly reverse UTF-8."} | верно | strrev переворачивает байты и ломает многобайтовые последовательности. |
T03-L2 0.56 c | Strings | str_contains('Hello world', 'world') returns true. | «yes» Пояснение: str_contains checks if the needle 'world' exists in the haystack 'Hello world', and it does, so it returns true.
Raw{"answer": "yes", "explanation": "str_contains checks if the needle 'world' exists in the haystack 'Hello world', and it does, so it returns true."} | верно | str_contains с PHP 8.0 проверяет вхождение подстроки. |
T03-L3 0.78 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.18 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 (\0, \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 (\\0, \\t, \\n, \\r, \\0, \\x0B), not just spaces."} | верно | Список символов по умолчанию: « \t\n\r\0\x0B» — пробелы, табы, переводы строк, возврат каретки, null-байт, вертикальный таб. Проверено php -r. |
T03-L5 0.95 c | Strings | How many BYTES does strlen('héllo') return for a UTF-8 string? | «6» Пояснение: strlen counts bytes in UTF-8: 'h' (1) + 'é' (2) + 'l' (1) + 'l' (1) + 'o' (1) = 6 bytes.
Raw{"answer": 6, "explanation": "strlen counts bytes in UTF-8: 'h' (1) + 'é' (2) + 'l' (1) + 'l' (1) + 'o' (1) = 6 bytes."} | верно | 6 букв по 2 байта: 12. |
T03-L6 0.83 c | Strings | What does substr('abcdef', -3) return? | «def» Пояснение: substr with a negative start position counts from the end of the string; -3 means the last 3 characters of 'abcdef', which is 'def'.
Raw{"answer": "def", "explanation": "substr with a negative start position counts from the end of the string; -3 means the last 3 characters of 'abcdef', which is 'def'."} | верно | Отрицательное смещение — с конца: def. |
T03-L7 0.93 c | Strings | ucfirst() modifies the string passed to it in place. | «no» Пояснение: In PHP, strings are passed by value; ucfirst() returns a new string with the first character uppercased rather than modifying the original variable in place.
Raw{"answer": "no", "explanation": "In PHP, strings are passed by value; ucfirst() returns a new string with the first character uppercased rather than modifying the original variable in place."} | верно | Строки неизменяемы; ucfirst возвращает новую строку. |
T03-L8 0.98 c | Strings | Variable interpolation works in heredoc but not in nowdoc. | «yes» Пояснение: Heredoc (<<EOF) allows variable interpolation, while nowdoc (<<'EOF') treats content as a literal string with no interpolation, similar to single-quoted strings.
Raw{"answer": "yes", "explanation": "Heredoc (<<EOF) allows variable interpolation, while nowdoc (<<'EOF') treats content as a literal string with no interpolation, similar to single-quoted strings."} | верно | Nowdoc — «одинарные кавычки» в тройном синтаксисе: текст как есть. |
T04-L1 1.08 c | Arrays | The sort() function preserves the key-to-value association of the array. | «no» Пояснение: PHP's sort() re-indexes the array with sequential integer keys, so key-to-value associations are lost; use asort() to preserve keys.
Raw{"answer": "no", "explanation": "PHP's sort() re-indexes the array with sequential integer keys, so key-to-value associations are lost; use asort() to preserve keys."} | верно | sort перенумеровывает ключи; связь сохраняет asort. |
T04-L2 1.38 c | Arrays | The string key '5' in an array is stored as the integer 5. | «yes» Пояснение: In PHP, string keys that represent valid integers (like '5') are automatically cast to integer keys, so $arr['5'] and $arr[5] refer to the same element.
Raw{"answer": "yes", "explanation": "In PHP, string keys that represent valid integers (like '5') are automatically cast to integer keys, so $arr['5'] and $arr[5] refer to the same element."} | верно | Каноничные десятичные строковые ключи приводятся к int. |
T04-L3 1.05 c | Arrays | The in_array() function uses strict comparison (===) by default. | «no» Пояснение: in_array() uses loose comparison (==) by default; you must pass true as the third parameter to enable strict (===) comparison.
Raw{"answer": "no", "explanation": "in_array() uses loose comparison (==) by default; you must pass true as the third parameter to enable strict (===) comparison."} | верно | По умолчанию сравнение нестрогое; строгое — третий аргумент true. |
T04-L4 2.02 c | Arrays | Without a callback, array_filter() removes all "empty" (falsy) elements from the array. | «yes» Пояснение: array_filter() without a callback keeps only elements that are truthy, effectively removing all falsy values (0, '', null, false, '0', empty array).
Raw{"answer": "yes", "explanation": "array_filter() without a callback keeps only elements that are truthy, effectively removing all falsy values (0, '', null, false, '0', empty array)."} | верно | Убирает 0, "", null, false и пустые массивы. |
T04-L5 1.19 c | Arrays | By default, array_slice() preserves the original numeric keys of the array. | «no» Пояснение: By default, the $preserve_keys parameter of array_slice() is false, so the resulting array is reindexed with sequential integer keys starting from 0.
Raw{"answer": "no", "explanation": "By default, the $preserve_keys parameter of array_slice() is false, so the resulting array is reindexed with sequential integer keys starting from 0."} | верно | По умолчанию ключи перенумеровываются; сохранение — preserve_keys = true. |
T04-L6 1.03 c | Arrays | What does array_slice([10, 20, 30, 40], 1, 2) return? | «[20, 30]» Пояснение: array_slice with offset 1 and length 2 extracts the 2 elements starting at index 1, which are 20 and 30.
Raw{"answer": "[20, 30]", "explanation": "array_slice with offset 1 and length 2 extracts the 2 elements starting at index 1, which are 20 and 30."} | верно | [20,30]; ключи перенумеровываются. |
T04-L7 1.33 c | Arrays | How many elements will count(['a' => 1] + ['a' => 9, 'b' => 2]) return? | «2» Пояснение: The + operator merges arrays keeping left-hand values for duplicate keys, resulting in ['a' => 1, 'b' => 2], which has 2 elements.
Raw{"answer": 2, "explanation": "The + operator merges arrays keeping left-hand values for duplicate keys, resulting in ['a' => 1, 'b' => 2], which has 2 elements."} | верно | Оператор + : по ключу 'a' побеждает левый; итого 2. |
T04-L8 1.47 c | Arrays | Since PHP 8.1, the spread operator [...$a, ...$b] supports arrays with string keys. | «yes» Пояснение: PHP 8.1 introduced the spread operator in array literals, which works with both integer and string keys.
Raw{"answer": "yes", "explanation": "PHP 8.1 introduced the spread operator in array literals, which works with both integer and string keys."} | верно | В 8.0 — только числовые ключи; 8.1 снял ограничение. |
T05-L1 3.32 c | Functions and closures | Named arguments cannot be combined with argument unpacking ...$args in a single call. | «no» Пояснение: In PHP, named arguments CAN be combined with argument unpacking (...$args) in the same function call, e.g. foo(a: 1, ...$args).
Raw{"answer": "no", "explanation": "In PHP, named arguments CAN be combined with argument unpacking (...$args) in the same function call, e.g. foo(a: 1, ...$args)."} | верно | Можно: f(...$args, имя: значение). Нельзя только позиционный аргумент после распаковки. |
T05-L2 0.86 c | Functions and closures | An anonymous function without use sees variables from the outer scope. | «no» Пояснение: In PHP, closures do not automatically inherit the outer scope; you must explicitly import variables using the `use` keyword.
Raw{"answer": "no", "explanation": "In PHP, closures do not automatically inherit the outer scope; you must explicitly import variables using the `use` keyword."} | верно | Без use внешние переменные недоступны; авто-захват только у fn. |
T05-L3 0.85 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 total number of arguments actually passed to the function (3), regardless of how many parameters are declared in the signature.
Raw{"answer": 3, "explanation": "func_num_args() returns the total number of arguments actually passed to the function (3), regardless of how many parameters are declared in the signature."} | верно | Считает переданные аргументы: 3. |
T05-L4 1.57 c | Functions and closures | The body of an arrow function fn may consist of several expressions in curly braces. | «no» Пояснение: An arrow function (fn) body is a single expression after =>, not a curly-brace block of multiple statements.
Raw{"answer": "no", "explanation": "An arrow function (fn) body is a single expression after =>, not a curly-brace block of multiple statements."} | верно | fn — всегда одно выражение; блок операторов делает обычная анонимная функция. |
T05-L5 3.69 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 creation time, not by reference and not lazily at use time.
Raw{"answer": "no", "explanation": "PHP arrow functions (fn) automatically capture outer variables by value at creation time, not by reference and not lazily at use time."} | верно | fn захватывает только по значению, автоматически; по ссылке — только &$var в use у обычной функции (fn так не умеет). |
T05-L6 1.41 c | Functions and closures | A closure declared as static function () {} does not capture $this. | «yes» Пояснение: In PHP, a static closure explicitly does not capture $this from the enclosing scope, unlike a non-static closure which does.
Raw{"answer": "yes", "explanation": "In PHP, a static closure explicitly does not capture $this from the enclosing scope, unlike a non-static closure which does."} | верно | static-замыкание отвязано от объекта: $this внутри недоступен. |
T05-L7 1.13 c | Functions and closures | What will this print: $x = 5; $f = function () use ($x) { return $x; }; $x = 7; echo $f(); | «5» Пояснение: The 'use ($x)' clause captures the value of $x (5) by value at closure creation time, so later reassigning $x to 7 does not affect the closure's captured copy.
Raw{"answer": 5, "explanation": "The 'use ($x)' clause captures the value of $x (5) by value at closure creation time, so later reassigning $x to 7 does not affect the closure's captured copy."} | верно | use захватывает по значению в момент создания: 5. |
T05-L8 1.09 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/coercive) typing mode, the string '5' is automatically coerced to the integer 5 when passed to an int parameter.
Raw{"answer": "yes", "explanation": "In PHP's default (weak/coercive) typing mode, the string '5' is automatically coerced to the integer 5 when passed to an int parameter."} | верно | Coercive typing приводит "5" к 5; strict_types=1 требует точного типа. |
T06-L1 0.87 c | OOP: classes and inheritance | PHP supports constructor property promotion: public function __construct(private int $x) {}. | «yes» Пояснение: Constructor property promotion was introduced in PHP 8.0, allowing properties to be declared directly in constructor parameters.
Raw{"answer": "yes", "explanation": "Constructor property promotion was introduced in PHP 8.0, allowing properties to be declared directly in constructor parameters."} | верно | С PHP 8.0 параметр с модификатором создаёт свойство и присваивание. |
T06-L2 0.56 c | OOP: classes and inheritance | Which keyword prevents a method from being overridden in subclasses? | «final» Пояснение: In PHP, the 'final' keyword placed before a method declaration prevents that method from being overridden in any subclass.
Raw{"answer": "final", "explanation": "In PHP, the 'final' keyword placed before a method declaration prevents that method from being overridden in any subclass."} | верно | 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 on a method prevents any subclass from overriding that method.
Raw{"answer": "yes", "explanation": "In PHP, the 'final' keyword on a method prevents any subclass from overriding that method."} | верно | final запрещает переопределение метода и наследование класса. |
T06-L4 0.76 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 defines them and are not accessible in subclasses; only protected or public parent properties are accessible in child classes.
Raw{"answer": "no", "explanation": "In PHP, private properties are only accessible within the class that defines them and are not accessible in subclasses; only protected or public parent properties are accessible in child classes."} | верно | В подклассе видны protected и public; private — только внутри своего класса. |
T06-L5 3.09 c | OOP: classes and inheritance | What does get_class(new class {}) return? Answer with the part of the name before the NUL byte (without the file path). | «class@anonymous» Пояснение: In PHP, get_class() on an anonymous class returns a name like 'class@anonymous/path/to/file.php:LINE\0ADDR'; the part before the NUL byte without the file path is 'class@anonymous'.
Raw{"answer": "class@anonymous", "explanation": "In PHP, get_class() on an anonymous class returns a name like 'class@anonymous/path/to/file.php:LINE\\0ADDR'; the part before the NUL byte without the file path is 'class@anonymous'."} | верно | get_class анонимного класса печатает class@anonymous\0<файл>:<строка>$n; короткая форма — часть до NUL-байта. Проверено php -r (hex). |
T06-L6 1.57 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, a private method is completely hidden from child classes, so the child is free to declare a method with the same name and any visibility without conflict—it's a new method, not an override.
Raw{"answer": "yes", "explanation": "In PHP, a private method is completely hidden from child classes, so the child is free to declare a method with the same name and any visibility without conflict—it's a new method, not an override."} | верно | private-члены не наследуются — правила совместимости подписей не действуют. |
T06-L7 1.73 c | OOP: classes and inheritance | The magic method __get() is called only for non-existent properties. | «no» Пояснение: __get() is called for inaccessible properties, which includes both non-existent properties and private/protected properties accessed from outside the class, not only non-existent ones.
Raw{"answer": "no", "explanation": "__get() is called for inaccessible properties, which includes both non-existent properties and private/protected properties accessed from outside the class, not only non-existent ones."} | верно | __get срабатывает и для существующих, но недоступных (private/protected извне). |
T06-L8 1.0 c | OOP: classes and inheritance | What does reassigning a readonly property throw — Exception or Error? | «error» Пояснение: Reassigning a readonly property in PHP throws an Error (specifically an instance of the Error class), not an Exception.
Raw{"answer": "Error", "explanation": "Reassigning a readonly property in PHP throws an Error (specifically an instance of the Error class), not an Exception."} | верно | Error (readonly с 8.1); оговорка: в __clone() переинициализация допустима (8.3+). |
T07-L1 0.88 c | Interfaces, traits, enum | An interface can declare constants. | «yes» Пояснение: PHP interfaces can declare public constants, which are accessible via the interface name.
Raw{"answer": "yes", "explanation": "PHP interfaces can declare public constants, which are accessible 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 is used to check whether an object is an instance of a specific class or implements a specific interface.
Raw{"answer": "instanceof", "explanation": "In PHP, the instanceof operator is used to check whether an object is an instance of a specific class or implements a specific interface."} | верно | instanceof. |
T07-L3 0.93 c | Interfaces, traits, enum | An interface can declare static methods. | «yes» Пояснение: PHP allows interfaces to declare static methods (since PHP 5.1), and any implementing class must provide a matching static method.
Raw{"answer": "yes", "explanation": "PHP allows interfaces to declare static methods (since PHP 5.1), and any implementing class must provide a matching static method."} | верно | Реализация обязана дать статический метод с той же сигнатурой. |
T07-L4 1.02 c | Interfaces, traits, enum | The instanceof operator only checks class inheritance: it ignores interfaces. | «no» Пояснение: PHP's instanceof operator checks both class inheritance and interface implementation, so it does not ignore interfaces.
Raw{"answer": "no", "explanation": "PHP's instanceof operator checks both class inheritance and interface implementation, so it does not ignore interfaces."} | верно | instanceof возвращает true и для интерфейсов объекта. |
T07-L5 3.54 c | Interfaces, traits, enum | An interface method may have a default implementation, like a trait method. | «no» Пояснение: In PHP, interface methods are always abstract and cannot have a body/implementation; only traits (and classes) can provide concrete method implementations.
Raw{"answer": "no", "explanation": "In PHP, interface methods are always abstract and cannot have a body/implementation; only traits (and classes) can provide concrete method implementations."} | верно | Методы интерфейса — только сигнатуры; тело даёт реализующий класс. |
T07-L6 1.18 c | Interfaces, traits, enum | An abstract method in an abstract class may have protected visibility. | «yes» Пояснение: In PHP, abstract methods can be declared with public or protected visibility; only private abstract methods are disallowed.
Raw{"answer": "yes", "explanation": "In PHP, abstract methods can be declared with public or protected visibility; only private abstract methods are disallowed."} | верно | В абстрактном классе — любая видимость; в интерфейсе — только public. |
T07-L7 0.75 c | Interfaces, traits, enum | How many elements will Foo::cases() return for enum Foo { case A; case B; case C; }? | «3» Пояснение: Foo::cases() returns an array containing all enum cases, and there are three: A, B, and C.
Raw{"answer": 3, "explanation": "Foo::cases() returns an array containing all enum cases, and there are three: A, B, and C."} | верно | Статический метод cases(): 3. |
T07-L8 2.01 c | Interfaces, traits, enum | A trait can declare constants. | «yes» Пояснение: Since PHP 8.2, traits are allowed to declare constants, which can be accessed via the class that uses the trait.
Raw{"answer": "yes", "explanation": "Since PHP 8.2, traits are allowed to 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.72 c | Exceptions and errors | The Throwable interface is a common ancestor of both Exception and Error. | «yes» Пояснение: In PHP, both Exception and Error implement the Throwable interface, making it their common ancestor in the exception hierarchy.
Raw{"answer": "yes", "explanation": "In PHP, both Exception and Error implement the Throwable interface, making it their common ancestor in the exception hierarchy."} | верно | Иерархия с PHP 7: Throwable → Exception и Throwable → Error. |
T08-L2 1.52 c | Exceptions and errors | A catch (Exception $e) block will also catch TypeError, because TypeError ultimately inherits from Exception. | «no» Пояснение: TypeError inherits from Error, not Exception; both Error and Exception are separate branches under Throwable, so catch(Exception) does not catch TypeError.
Raw{"answer": "no", "explanation": "TypeError inherits from Error, not Exception; both Error and Exception are separate branches under Throwable, so catch(Exception) does not catch TypeError."} | верно | TypeError наследуется от Error; catch (Exception) его не ловит. |
T08-L3 1.72 c | Exceptions and errors | The @ operator suppresses exceptions too. | «no» Пояснение: The @ operator only suppresses errors (notices, warnings, etc.) via error_reporting; exceptions still propagate normally regardless of the @ operator.
Raw{"answer": "no", "explanation": "The @ operator only suppresses errors (notices, warnings, etc.) via error_reporting; exceptions still propagate normally regardless of the @ operator."} | верно | @ глушит диагностику (warnings/notices), исключения не перехватывает. |
T08-L4 1.49 c | Exceptions and errors | What error class does intdiv(5, 0) throw? | «divisionbyzeroerror» Пояснение: intdiv(5, 0) throws a DivisionByZeroError, which extends ArithmeticError in PHP.
Raw{"answer": "DivisionByZeroError", "explanation": "intdiv(5, 0) throws a DivisionByZeroError, which extends ArithmeticError in PHP."} | верно | DivisionByZeroError (иерархия Error, не Exception); php-грейдер объективен. |
T08-L5 1.2 c | Exceptions and errors | The finally block runs only if the exception was caught by a catch block. | «no» Пояснение: The finally block executes regardless of whether an exception was thrown, caught, or not; it always runs when the try-catch-finally structure is encountered.
Raw{"answer": "no", "explanation": "The finally block executes regardless of whether an exception was thrown, caught, or not; it always runs when the try-catch-finally structure is encountered."} | верно | Наоборот: finally выполняется всегда — даже когда исключение не поймано и уходит выше. Проверено php -r. |
T08-L6 1.5 c | Exceptions and errors | An exception thrown inside a finally block has no effect on the result of the try block. | «no» Пояснение: An exception thrown in a finally block replaces (overrides) any exception from the try block, so it does have an effect on the outcome.
Raw{"answer": "no", "explanation": "An exception thrown in a finally block replaces (overrides) any exception from the try block, so it does have an effect on the outcome."} | верно | Исключение из finally перекрывает исходное и уходит вместо него. |
T08-L7 0.94 c | Exceptions and errors | What does the expression (bool) new Exception('x') return? | «yes» Пояснение: In PHP, casting any object to bool always results in true, since objects are truthy values.
Raw{"answer": "yes", "explanation": "In PHP, casting any object to bool always results in true, since objects are truthy values."} | верно | Любой объект при приведении к bool — true. Формы ответа: true или да. |
T08-L8 1.09 c | Exceptions and errors | Functions registered via register_shutdown_function() run when exit is called. | «yes» Пояснение: Shutdown functions registered with register_shutdown_function() are executed when the script terminates, including when exit or die is called.
Raw{"answer": "yes", "explanation": "Shutdown functions registered with register_shutdown_function() are executed when the script terminates, including when exit or die is called."} | верно | exit завершает скрипт, но shutdown-функции отрабатывают. |
T09-L1 1.1 c | Namespaces and autoloading | The use App\Service\Mailer; statement itself loads the class file. | «no» Пояснение: The 'use' statement is a compile-time alias that simply maps a shorter name to a fully qualified class name; the actual class file is loaded via the autoloader only when the class is first referenced at runtime.
Raw{"answer": "no", "explanation": "The 'use' statement is a compile-time alias that simply maps a shorter name to a fully qualified class name; the actual class file is loaded via the autoloader only when the class is first referenced at runtime."} | верно | use — псевдоним на этапе компиляции; файл грузит автозагрузчик при первом обращении. |
T09-L2 1.02 c | Namespaces and autoloading | What follows use to import a function (not a class): the word function or const? | «function» Пояснение: In PHP, to import a function you write 'use function namespace\functionName;', while 'use const' is used for importing constants.
Raw{"answer": "function", "explanation": "In PHP, to import a function you write 'use function namespace\\functionName;', while 'use const' is used for importing constants."} | верно | use function ...; (и use const для констант). |
T09-L3 1.29 c | Namespaces and autoloading | Into which file (path from src/) does the PSR-4 mapping "App\ → src/" place the class App\Controller\Api\UserController? | «controller/api/usercontroller.php» Пояснение: PSR-4 strips the 'App\' prefix, converts remaining namespace separators to directory paths, and appends the class name with .php extension.
Raw{"answer": "Controller/Api/UserController.php", "explanation": "PSR-4 strips the 'App\\' prefix, converts remaining namespace separators to directory paths, and appends the class name with .php extension."} | верно | Остаток имени после префикса, \ → /. |
T09-L4 1.12 c | Namespaces and autoloading | Including vendor/autoload.php registers autoloaders via spl_autoload_register(). | «yes» Пояснение: Composer's vendor/autoload.php includes autoload_real.php which registers Composer's ClassLoader via spl_autoload_register().
Raw{"answer": "yes", "explanation": "Composer's vendor/autoload.php includes autoload_real.php which registers Composer's ClassLoader via spl_autoload_register()."} | верно | Composer ставит автозагрузчик именно на spl_autoload_register. |
T09-L5 0.64 c | Namespaces and autoloading | The magic constant __NAMESPACE__ contains the name of the current namespace. | «yes» Пояснение: __NAMESPACE__ is a PHP magic constant that returns the name of the current namespace (or an empty string if in the global namespace).
Raw{"answer": "yes", "explanation": "__NAMESPACE__ is a PHP magic constant that returns the name of the current namespace (or an empty string if in the global namespace)."} | верно | В корневом пространстве — пустая строка. |
T09-L6 3.47 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 first resolved relative to the current namespace; it only falls back to the global root if the class isn't found in the current namespace.
Raw{"answer": "no", "explanation": "An unqualified class name in `new` is first resolved relative to the current namespace; it only falls back to the global root if the class isn't found in the current namespace."} | верно | Резолвится относительно текущего namespace (с учётом импортов). |
T09-L7 1.24 c | Namespaces and autoloading | With the PSR-4 mapping "App\ → src/", the class App\Model\User lives in the file src/Model/User.php. | «yes» Пояснение: PSR-4 strips the 'App\' prefix, converts the remaining namespace 'Model\User' to a relative path 'Model/User.php', and prepends the base directory 'src/', yielding src/Model/User.php.
Raw{"answer": "yes", "explanation": "PSR-4 strips the 'App\\' prefix, converts the remaining namespace 'Model\\User' to a relative path 'Model/User.php', and prepends the base directory 'src/', yielding src/Model/User.php."} | верно | Остаток имени после префикса переносится в путь как есть. |
T09-L8 1.39 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 a use statement inside a function body, and the alias then applies only within that function's scope.
Raw{"answer": "yes", "explanation": "PHP allows a use statement inside a function body, and the alias then applies only within that function's scope."} | неверно верный: «no» | use внутри тела функции — parse error; импорты файловые и компиляционные. |
T10-L1 1.01 c | References and scope | Arrays are copied on assignment rather than passed by reference. | «yes» Пояснение: In PHP, arrays are value types that are copied on assignment (using copy-on-write internally), unlike objects which are passed by handle/reference.
Raw{"answer": "yes", "explanation": "In PHP, arrays are value types that are copied on assignment (using copy-on-write internally), unlike objects which are passed by handle/reference."} | верно | Присваивание массива — копия (в движке — copy-on-write). |
T10-L2 1.23 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 (without &), so modifying $b does not affect $a, which still has 2 elements.
Raw{"answer": 2, "explanation": "In PHP, arrays are copied by value on assignment (without &), so modifying $b does not affect $a, which still has 2 elements."} | верно | Присваивание — копия: в $a по-прежнему 2 элемента. |
T10-L3 1.67 c | References and scope | Inside a function, user-defined global variables are inaccessible without global, $GLOBALS, or passing them as parameters. | «yes» Пояснение: In PHP, user-defined variables in the global scope are not visible inside a function unless imported via 'global', accessed through '$GLOBALS', or passed as parameters.
Raw{"answer": "yes", "explanation": "In PHP, user-defined variables in the global scope are not visible inside a function unless imported via 'global', accessed through '$GLOBALS', or passed as parameters."} | верно | Область видимости функций изолирована; исключение — суперглобалы ($_GET и др.). |
T10-L4 1.66 c | References and scope | unset($GLOBALS['x']) inside a function removes the global variable only for that function. | «no» Пояснение: $GLOBALS['x'] is a reference to the actual global variable, so unset($GLOBALS['x']) removes the global variable entirely for all code, not just for the current function.
Raw{"answer": "no", "explanation": "$GLOBALS['x'] is a reference to the actual global variable, so unset($GLOBALS['x']) removes the global variable entirely for all code, not just for the current function."} | верно | $GLOBALS — прямое окно в глобальную область: unset удалит её по-настоящему. |
T10-L5 0.75 c | References and scope | What will this print: function inc(&$x) { $x++; } $n = 5; inc($n); echo $n; | «6» Пояснение: The function inc() takes $x by reference, so $n is incremented from 5 to 6, and echo prints 6.
Raw{"answer": 6, "explanation": "The function inc() takes $x by reference, so $n is incremented from 5 to 6, and echo prints 6."} | верно | Ссылка меняет оригинал: 6. |
T10-L6 8.48 c | References and scope | A foreach over an array (by value) works with the "live" array: changes to the array inside the loop are visible in the same pass. | «no» Пояснение: In PHP, foreach over an array by value iterates over a snapshot/copy of the array, so structural changes (adding or removing elements) made inside the loop are not visible in the same pass.
Raw{"answer": "no", "explanation": "In PHP, foreach over an array by value iterates over a snapshot/copy of the array, so structural changes (adding or removing elements) made inside the loop are not visible in the same pass."} | верно | По значению foreach итерирует копию-снимок. |
T10-L7 0.88 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 made through one object are visible in all others.
Raw{"answer": "no", "explanation": "A static property belongs to the class itself and is shared across all instances, so changes made through one object are visible in all others."} | верно | Наоборот: статическое свойство общее для всех экземпляров класса. Проверено php -r. |
T10-L8 1.8 c | References and scope | An array can have a boolean key true, and it will be stored as bool. | «no» Пояснение: In PHP, array keys are only int or string; the boolean key true is cast to the integer 1, not stored as bool.
Raw{"answer": "no", "explanation": "In PHP, array keys are only int or string; the boolean key true is cast to the integer 1, not stored as bool."} | верно | Булев ключ приводится к int: true → 1, false → 0. |
T11-L1 5.84 c | Generators, iterators, SPL | Inside a generator, return with a value can be used, and it becomes available via $gen->getReturn(). | «yes» Пояснение: In PHP, a generator function can use `return $value;`, and after exhausting the generator, the return value is accessible via the `Generator::getReturn()` method.
Raw{"answer": "yes", "explanation": "In PHP, a generator function can use `return $value;`, and after exhausting the generator, the return value is accessible via the `Generator::getReturn()` method."} | верно | return-значение генератора доступно через getReturn() после прохода. |
T11-L2 2.26 c | Generators, iterators, SPL | A fully consumed generator can be rewound with rewind() and traversed again. | «no» Пояснение: A PHP generator is a one-shot iterator; once fully consumed, calling rewind() does not restart the underlying function, so it yields nothing on a second traversal.
Raw{"answer": "no", "explanation": "A PHP generator is a one-shot iterator; once fully consumed, calling rewind() does not restart the underlying function, so it yields nothing on a second traversal."} | верно | Генератор одноразовый: rewind после начала итерации бросает Exception. |
T11-L3 4.05 c | Generators, iterators, SPL | The yield from construct delegates traversal to another generator or iterable. | «yes» Пояснение: The 'yield from' construct (as in Python) indeed delegates iteration to another iterable or generator, yielding each value it produces in sequence.
Raw{"answer": "yes", "explanation": "The 'yield from' construct (as in Python) indeed delegates iteration to another iterable or generator, yielding each value it produces in sequence."} | верно | yield from проксирует значения, ключи и return-значение внутреннего генератора. |
T11-L4 1.01 c | Generators, iterators, SPL | What does get_class(g()) return for function g() { yield 1; }? | «generator» Пояснение: Calling a generator function returns a Generator object, and get_class() on it returns the string 'Generator'.
Raw{"answer": "Generator", "explanation": "Calling a generator function returns a Generator object, and get_class() on it returns the string 'Generator'."} | верно | Функция с yield возвращает Generator. |
T11-L5 1.13 c | Generators, iterators, SPL | How many elements will count(iterator_to_array((function () { yield from [1, 2, 3]; })())) return? | «3» Пояснение: yield from [1, 2, 3] yields three values (1, 2, 3), iterator_to_array converts them to an array of 3 elements, and count returns 3.
Raw{"answer": 3, "explanation": "yield from [1, 2, 3] yields three values (1, 2, 3), iterator_to_array converts them to an array of 3 elements, and count returns 3."} | верно | yield from делегирует все 3 элемента. |
T11-L6 0.83 c | Generators, iterators, SPL | The SplStack class implements a FIFO queue. | «no» Пояснение: SplStack implements a LIFO (Last In, First Out) stack, while SplQueue is the one that implements a FIFO (First In, First Out) queue.
Raw{"answer": "no", "explanation": "SplStack implements a LIFO (Last In, First Out) stack, while SplQueue is the one that implements a FIFO (First In, First Out) queue."} | верно | SplStack — стек LIFO; очередь FIFO — SplQueue. |
T11-L7 0.79 c | Generators, iterators, SPL | ArrayIterator allows wrapping an array and traversing it via the Iterator interface. | «yes» Пояснение: ArrayIterator is a built-in PHP class that wraps an array and implements the Iterator interface, allowing traversal via methods like current(), next(), key(), valid(), and rewind().
Raw{"answer": "yes", "explanation": "ArrayIterator is a built-in PHP class that wraps an array and implements the Iterator interface, allowing traversal via methods like current(), next(), key(), valid(), and rewind()."} | верно | Объектная обёртка над массивом. |
T11-L8 1.53 c | Generators, iterators, SPL | An ArrayObject instance cannot be traversed with foreach. | «no» Пояснение: ArrayObject implements the Iterator/IteratorAggregate interface, so it can be traversed with foreach.
Raw{"answer": "no", "explanation": "ArrayObject implements the Iterator/IteratorAggregate interface, so it can be traversed with foreach."} | верно | ArrayObject реализует IteratorAggregate — foreach по нему работает. |
T12-L1 1.49 c | Configuration and security | password_hash() generates a salt automatically — passing one separately is not needed. | «yes» Пояснение: password_hash() in PHP 5.5+ automatically generates and embeds a random salt; the 'salt' option is purely optional and not required.
Raw{"answer": "yes", "explanation": "password_hash() in PHP 5.5+ automatically generates and embeds a random salt; the 'salt' option is purely optional and not required."} | верно | Соль встраивается в строку результата; параметр salt устарел. |
T12-L2 2.23 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 8.4), not md5.
Raw{"answer": "no", "explanation": "In PHP 8, PASSWORD_DEFAULT is PASSWORD_BCRYPT (or PASSWORD_ARGON2ID in 8.4), not md5."} | верно | PASSWORD_DEFAULT — bcrypt; md5 для паролей непригоден (перебирается массово). |
T12-L3 0.95 c | Configuration and security | What does password_verify('secret', password_hash('secret', PASSWORD_DEFAULT)) return? | «yes» Пояснение: password_verify() returns true when the plain-text password matches the given hash, which is the case here since both use 'secret'.
Raw{"answer": "yes", "explanation": "password_verify() returns true when the plain-text password matches the given hash, which is the case here since both use 'secret'."} | верно | Соль и хеш в одной строке: true (форма ответа: true или да). |
T12-L4 1.14 c | Configuration and security | strip_tags() protects against SQL injection. | «no» Пояснение: strip_tags() removes HTML/PHP tags from a string (useful against XSS), but SQL injection is defended against by prepared statements/parameterized queries, not by stripping tags.
Raw{"answer": "no", "explanation": "strip_tags() removes HTML/PHP tags from a string (useful against XSS), but SQL injection is defended against by prepared statements/parameterized queries, not by stripping tags."} | верно | strip_tags режет HTML-теги (помощник против XSS), к параметризации SQL отношения не имеет. |
T12-L5 1.27 c | Configuration and security | session_regenerate_id() is used to protect against session fixation upon user login. | «yes» Пояснение: session_regenerate_id() creates a new session ID, invalidating the old one, which prevents an attacker who knows the pre-login session ID from hijacking the authenticated session (session fixation).
Raw{"answer": "yes", "explanation": "session_regenerate_id() creates a new session ID, invalidating the old one, which prevents an attacker who knows the pre-login session ID from hijacking the authenticated session (session fixation)."} | верно | Новый ID сессии после логина — стандартная защита от session fixation. |
T12-L6 1.26 c | Configuration and security | Which built-in function returns the SAPI name (e.g., cli)? | «php_sapi_name()» Пояснение: php_sapi_name() is the built-in PHP function that returns the current SAPI module name, such as 'cli', 'fpm-fcgi', or 'apache2'.
Raw{"answer": "php_sapi_name()", "explanation": "php_sapi_name() is the built-in PHP function that returns the current SAPI module name, such as 'cli', 'fpm-fcgi', or 'apache2'."} | верно | php_sapi_name(). |
T12-L7 1.17 c | Configuration and security | session_destroy() deletes session data on the server but not the cookie in the user's browser. | «yes» Пояснение: session_destroy() only removes the session data on the server; the session cookie in the browser must be manually cleared (e.g., via setcookie with a past expiry) before or after destroying the session.
Raw{"answer": "yes", "explanation": "session_destroy() only removes the session data on the server; the session cookie in the browser must be manually cleared (e.g., via setcookie with a past expiry) before or after destroying the session."} | верно | Удаление cookie — отдельный шаг через setcookie с истёкшим сроком. |
T12-L8 1.18 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 empty or undefined.
Raw{"answer": "no", "explanation": "The $_SESSION array is only populated with session data after session_start() is called; without it, $_SESSION remains empty or undefined."} | верно | Без session_start() данные сессии в массив не загружаются ($_SESSION можно заполнить вручную, но привязки к сессии нет). |
VC-L1 3.49 c | PHP 8.4–8.5 | In which PHP version was the array_find() function introduced? | «none» Пояснение: array_find() is not a built-in PHP function; it does not exist in any PHP version (commonly confused with array_filter() or array_search()).
Raw{"answer": "none", "explanation": "array_find() is not a built-in PHP function; it does not exist in any PHP version (commonly confused with array_filter() or array_search())."} | неверно верный: «8.4» | PHP 8.4 (RFC array_find). |
VC-L2 1.14 c | PHP 8.4–8.5 | Property hooks (get/set right in the property declaration) landed in PHP 8.4. | «yes» Пояснение: Property hooks (get/set defined inline in the property declaration) were introduced in PHP 8.4 via the Property Hooks RFC.
Raw{"answer": "yes", "explanation": "Property hooks (get/set defined inline in the property declaration) were introduced in PHP 8.4 via the Property Hooks RFC."} | верно | Property hooks — PHP 8.4 (ноябрь 2024). |
VC-L3 1.22 c | PHP 8.4–8.5 | Asymmetric visibility (public private(set) string $name) appeared in PHP 8.4. | «yes» Пояснение: Asymmetric visibility (e.g., public private(set) string $name) was indeed introduced as a new feature in PHP 8.4.
Raw{"answer": "yes", "explanation": "Asymmetric visibility (e.g., public private(set) string $name) was indeed introduced as a new feature in PHP 8.4."} | верно | Asymmetric visibility v2 — PHP 8.4. |
VC-L4 1.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 allow marking functions whose return value should not be silently discarded.
Raw{"answer": "8.4", "explanation": "The #[\\NoDiscard] attribute was introduced in PHP 8.4 to allow marking functions whose return value should not be silently discarded."} | неверно верный: «8.5» | #[\NoDiscard] — PHP 8.5 (marking return values as important). |
VC-L5 5.81 c | PHP 8.4–8.5 | In which PHP version did the pipe operator |> first appear? Answer with the version number. | «8.4» Пояснение: The pipe operator (|>) was introduced in PHP 8.4, allowing functional pipeline-style chaining of expressions.
Raw{"answer": "8.4", "explanation": "The pipe operator (|>) was introduced in PHP 8.4, allowing functional pipeline-style chaining of expressions."} | неверно верный: «8.5» | Pipe operator — PHP 8.5 (2025). |
VC-L6 4.91 c | PHP 8.4–8.5 | In which PHP version did clone-with — the syntax clone($obj, ['x' => 1]) — appear? Answer with the version number. | «no» Пояснение: The clone-with syntax clone($obj, ['x' => 1]) has not appeared in any released PHP version; PHP's clone keyword only supports clone $obj without a second argument.
Raw{"answer": "no", "explanation": "The clone-with syntax clone($obj, ['x' => 1]) has not appeared in any released PHP version; PHP's clone keyword only supports clone $obj without a second argument."} | неверно верный: «8.5» | Clone with v2 — PHP 8.5. |
VC-L7 5.12 c | PHP 8.4–8.5 | In which PHP version were the array_first() and array_last() functions introduced? | «none» Пояснение: array_first() and array_last() are not native PHP functions; they are helper functions provided by the Laravel framework, not introduced in any specific PHP version.
Raw{"answer": "none", "explanation": "array_first() and array_last() are not native PHP functions; they are helper functions provided by the Laravel framework, not introduced in any specific PHP version."} | неверно верный: «8.5» | PHP 8.5. |
VC-L8 3.41 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. | «9.0» Пояснение: The RFC Partial Function Application v2 was adopted for PHP 9.0.
Raw{"answer": "9.0", "explanation": "The RFC Partial Function Application v2 was adopted for PHP 9.0."} | неверно верный: «8.6» | PFA v2 принят 05.12.2025 (33-0-0), реализован в PHP 8.6. |
VF-L1 0.99 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, released in November 2024.
Raw{"answer": "8.4", "explanation": "The clamp() function was introduced in PHP 8.4, released in November 2024."} | неверно верный: «8.6» | По данным владельца (wiki.php.net/rfc): clamp_v2 — 8.6; clamp() в 8.5.11 отсутствует (косвенное подтверждение). Дата-якорь делает клетку монотонной. |
VF-L2 6.56 c | PHP: 8.6+ and the future | RFC Context Managers v2 has already been adopted in PHP (as of 2026-11-07). | «no» Пояснение: The Context Managers v2 RFC for PHP was not adopted; it was rejected during the voting process, so context managers are not a feature of PHP as of November 2026.
Raw{"answer": "no", "explanation": "The Context Managers v2 RFC for PHP was not adopted; it was rejected during the voting process, so context managers are not a feature of PHP as of November 2026."} | верно | На 06.11.2026 — в обсуждении (создан 2026-10-23); не принят. |
VF-L3 4.38 c | PHP: 8.6+ and the future | RFC Bound-Erased Generic Types (generics) was declined in 2026. | «yes» Пояснение: The Bound-Erased Generic Types RFC for PHP was indeed voted down (declined) during the 2026 voting cycle.
Raw{"answer": "yes", "explanation": "The Bound-Erased Generic Types RFC for PHP was indeed voted down (declined) during the 2026 voting cycle."} | верно | Голосование завершилось 2026-06-28: отклонён (wiki.php.net/rfc). |
VF-L4 3.38 c | PHP: 8.6+ and the future | As of 2026-11-07, the RFC enabling multithreading (ZTS) by default has already been accepted in PHP. | «yes» Пояснение: The RFC to make ZTS (Zend Thread Safety) the default build was accepted for PHP 8.4, which would have been released before 2026-11-07.
Raw{"answer": "yes", "explanation": "The RFC to make ZTS (Zend Thread Safety) the default build was accepted for PHP 8.4, which would have been released before 2026-11-07."} | неверно верный: «no» | Такого принятого RFC нет на дату якоря; якорь делает клетку монотонной — при принятии RFC позже клетка не перевернётся. |
VF-L5 2.13 c | PHP: 8.6+ and the future | As of PHP 8.5, generics (parameterized types) are still absent. | «yes» Пояснение: PHP has not implemented true generics (parameterized types); as of PHP 8.5, only docblock-level @template annotations exist, which are not enforced at runtime.
Raw{"answer": "yes", "explanation": "PHP has not implemented true generics (parameterized types); as of PHP 8.5, only docblock-level @template annotations exist, which are not enforced at runtime."} | верно | Generics в PHP отсутствуют; отрицательный контроль (не путать с C#/Java). |
VF-L6 2.47 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 8.5 was released in November 2025, and PHP 8.6's GA is expected on 2026-11-19, so as of 2026-11-07 the latest stable is indeed 8.5.
Raw{"answer": "yes", "explanation": "PHP 8.5 was released in November 2025, and PHP 8.6's GA is expected on 2026-11-19, so as of 2026-11-07 the latest stable is indeed 8.5."} | верно | 8.5 — релиз осени 2025; 8.6 GA 19.11.2026 (wiki.php.net/todo/php86). Дата снимка — 06.11.2026. |
VF-L7 1.39 c | PHP: 8.6+ and the future | The PHP 6 branch never shipped: after PHP 5.6 came PHP 7.0 directly. | «yes» Пояснение: PHP went directly from 5.6 to 7.0; the 'PHP 6' development branch was merged into what became PHP 7 and was never released under the 6 name.
Raw{"answer": "yes", "explanation": "PHP went directly from 5.6 to 7.0; the 'PHP 6' development branch was merged into what became PHP 7 and was never released under the 6 name."} | верно | Исторический факт: ветка 6 не была релизнута. |
VF-L8 2.21 c | PHP: 8.6+ and the future | The RFC adding the #[\Deprecated] attribute to the core was adopted. | «no» Пояснение: The RFC proposing a #[\Deprecated] attribute for PHP core was not adopted (it was rejected).
Raw{"answer": "no", "explanation": "The RFC proposing a #[\\Deprecated] attribute for PHP core was not adopted (it was rejected)."} | неверно верный: «yes» | #[\Deprecated] — принят, реализован в PHP 8.4. |
T25-L1 1.13 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 states that inner layers (domain core) must not depend on outer layers; all dependencies point inward toward the center.
Raw{"answer": "yes", "explanation": "In clean/onion architecture, the dependency rule states that inner layers (domain core) must not depend on outer layers; all dependencies point inward toward the center."} | верно | Чистая (Robert C. Martin), луковичная (Jeffrey Palermo) и гексагональная (ports & adapters) — варианты одной идеи: зависимости направлены внутрь, к домену. Слоями в проекте следит deptrac. |
T25-L2 1.55 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 must be framework-agnostic, depending only on native PHP language features and possibly the standard library, not on Doctrine or Symfony.
Raw{"answer": "yes", "explanation": "In DDD/clean architecture, domain entities must be framework-agnostic, depending only on native PHP language features and possibly the standard library, not on Doctrine or Symfony."} | верно | Изоляция домена от инфраструктуры; deptrac в проекте как раз следит за слоями. |
T25-L3 1.41 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 business-logic layer consists of services, use cases, and domain objects that the controllers invoke.
Raw{"answer": "no", "explanation": "Controllers and Twig templates belong to the presentation (view) layer; the business-logic layer consists of services, use cases, and domain objects that the controllers invoke."} | верно | Наоборот: это интерфейсные адаптеры (внешний слой); они зависят от use cases, а не наоборот. |
T25-L4 2.34 c | Clean architecture | What sits at the very center of the onion architecture? | «domain» Пояснение: In the onion (hexagonal) architecture, the core Domain/Entities layer sits at the very center, surrounded by the Application, Interface Adapters, and Frameworks/Drivers layers.
Raw{"answer": "Domain", "explanation": "In the onion (hexagonal) architecture, the core Domain/Entities layer sits at the very center, surrounded by the Application, Interface Adapters, and Frameworks/Drivers layers."} | неверно верный: «domain model» | Центральное кольцо — Domain Model: сущности и бизнес-правила без зависимостей; далее Domain Services → Application Services → Infrastructure/UI/Tests (Palermo). |
T25-L5 1.11 c | Clean architecture | Layer boundary violations can be caught automatically: a layer-dependency analyzer (e.g. deptrac) fails on a forbidden call. | «yes» Пояснение: Deptrac and similar static analysis tools can define layer rules and automatically fail the build when a forbidden cross-layer dependency is detected.
Raw{"answer": "yes", "explanation": "Deptrac and similar static analysis tools can define layer rules and automatically fail the build when a forbidden cross-layer dependency is detected."} | верно | depfile.yaml в проекте TasK: CI проверяет правила слоёв на каждом пайплайне. |
T25-L6 2.37 c | Clean architecture | A use case (interactor) may accept an HTTP request or an EntityManager as arguments — it is simpler that way. | «no» Пояснение: Use cases (interactors) should depend on abstractions (interfaces like Repository), not concrete framework-specific types like HTTP requests or EntityManager, to remain decoupled and testable.
Raw{"answer": "no", "explanation": "Use cases (interactors) should depend on abstractions (interfaces like Repository), not concrete framework-specific types like HTTP requests or EntityManager, to remain decoupled and testable."} | верно | 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 provides a collection-like interface for accessing domain aggregates/entities while abstracting the underlying storage mechanism.
Raw{"answer": "Repository", "explanation": "A Repository provides a collection-like interface for accessing domain aggregates/entities while abstracting the underlying storage mechanism."} | верно | Repository pattern (DDD/Evans); в проекте — Doctrine-репозитории за портами. |
T25-L8 1.94 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 driver sits in the outermost (infrastructure) layer, and the domain and use cases depend only on abstractions (interfaces) they define, so swapping the concrete database implementation affects only that outer layer.
Raw{"answer": "yes", "explanation": "In Clean Architecture, the database driver sits in the outermost (infrastructure) layer, and the domain and use cases depend only on abstractions (interfaces) they define, so swapping the concrete database implementation affects only that outer layer."} | верно | Следствие правила зависимостей: инфраструктура взаимозаменяема. |
T26-L1 1.32 c | DDD | In DDD, an aggregate is just another name for a database table. | «no» Пояснение: In DDD, an aggregate is a cluster of domain objects (entities and value objects) treated as a single unit for consistency, not a database table; it is a domain modeling concept, not a persistence/schema concept.
Raw{"answer": "no", "explanation": "In DDD, an aggregate is a cluster of domain objects (entities and value objects) treated as a single unit for consistency, not a database table; it is a domain modeling concept, not a persistence/schema concept."} | верно | Агрегат — кластер объектов с границей согласованности (транзакционной вокруг корня); таблица — деталь хранения. |
T26-L2 0.84 c | DDD | A Value Object is immutable and compared by the values of its fields, not by identity. | «yes» Пояснение: By definition, a Value Object is immutable and equality is determined by comparing its field values rather than object identity.
Raw{"answer": "yes", "explanation": "By definition, a Value Object is immutable and equality is determined by comparing its field values rather than object identity."} | верно | Классика Evans: Money, Email; равенство структурное. |
T26-L3 0.67 c | DDD | What is the single external entry point of an aggregate, through which all changes must go, called? | «aggregate root» Пояснение: In Domain-Driven Design, the Aggregate Root is the single external entry point of an aggregate, through which all external access and changes to the aggregate must go.
Raw{"answer": "Aggregate Root", "explanation": "In Domain-Driven Design, the Aggregate Root is the single external entry point of an aggregate, through which all external access and changes to the aggregate must go."} | верно | Aggregate Root: внешние объекты ссылаются только на корень; он защищает инварианты агрегата. |
T26-L4 1.11 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 an Aggregate Root only; entities within the aggregate are accessed through the root, not via their own repositories.
Raw{"answer": "yes", "explanation": "In DDD, a Repository is defined for an Aggregate Root only; entities within the aggregate are accessed through the root, not via their own repositories."} | верно | Репозиторий корня хранит границу согласованности агрегата; вложенные сущности доступны только через корень. |
T26-L5 1.06 c | DDD | Ubiquitous language is the model's shared language common to developers and domain experts. | «yes» Пояснение: In Domain-Driven Design, ubiquitous language is the shared vocabulary used consistently by both developers and domain experts to ensure a common understanding of the domain model.
Raw{"answer": "yes", "explanation": "In Domain-Driven Design, ubiquitous language is the shared vocabulary used consistently by both developers and domain experts to ensure a common understanding of the domain model."} | верно | Evans: язык из требований переходит в имена классов и методов. |
T26-L6 4.0 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 defines the boundary within which a model's language is self-consistent, while outside it the same terms map to different models or meanings.
Raw{"answer": "frame", "explanation": "A frame defines the boundary within which a model's language is self-consistent, while outside it the same terms map to different models or meanings."} | неверно верный: «bounded context» | Bounded Context; «Заказ» в биллинге и в доставке — разные модели. |
T26-L7 1.09 c | DDD | An anemic model (objects with only getters/setters, logic in services) is the recommended DDD style. | «no» Пояснение: DDD recommends a rich (fat) domain model where business logic lives inside the domain objects, not an anemic model with logic extracted into services.
Raw{"answer": "no", "explanation": "DDD recommends a rich (fat) domain model where business logic lives inside the domain objects, not an anemic model with logic extracted into services."} | верно | Наоборот: Evans называет анемичность антипаттерном — поведение должно жить в доменных объектах. |
T26-L8 2.94 c | DDD | Bounded context means each context has its own model: the same concept in different contexts is a different class. | «yes» Пояснение: In DDD, a Bounded Context ensures each context has its own independent model, so the same real-world concept (e.g., 'Customer') is typically represented by different, context-specific classes in different bounded contexts.
Raw{"answer": "yes", "explanation": "In DDD, a Bounded Context ensures each context has its own independent model, so the same real-world concept (e.g., 'Customer') is typically represented by different, context-specific classes in different bounded contexts."} | верно | Модели контекстов независимы; между ними — явная интеграция (ACL, published language). |
T13-L1 1.53 c | Symfony | Services in the Symfony DI container are created lazily by default — on first use. | «yes» Пояснение: Symfony's DI container does not instantiate all services at boot; each service is only created (its factory called) the first time it is actually requested, which is the default lazy behavior.
Raw{"answer": "yes", "explanation": "Symfony's DI container does not instantiate all services at boot; each service is only created (its factory called) the first time it is actually requested, which is the default lazy behavior."} | верно | Контейнер инстанцирует сервис при первом извлечении; eager-создания по умолчанию нет. |
T13-L2 1.14 c | Symfony | Which Symfony console command lists all registered routes? | «debug:router» Пояснение: The Symfony console command 'debug:router' (also 'router:debug' in newer versions) lists all registered routes.
Raw{"answer": "debug:router", "explanation": "The Symfony console command 'debug:router' (also 'router:debug' in newer versions) lists all registered routes."} | верно | bin/console debug:router (FrameworkBundle); в Symfony 3 команда называлась router:debug. |
T13-L3 1.07 c | Symfony | Symfony autowiring requires manually declaring every service in services.yaml. | «no» Пояснение: Autowiring's purpose is to automatically resolve and instantiate services based on type hints, so you do not need to manually declare every service in services.yaml.
Raw{"answer": "no", "explanation": "Autowiring's purpose is to automatically resolve and instantiate services based on type hints, so you do not need to manually declare every service in services.yaml."} | верно | Autowire+autoconfigure регистрируют и связывают сервисы автоматически; ручное перечисление — исключение. |
T13-L4 1.4 c | Symfony | Twig templates are compiled into PHP classes and cached between requests. | «yes» Пояснение: Twig compiles templates into PHP classes (extending Twig\Template) and supports caching that compiled output between requests for performance.
Raw{"answer": "yes", "explanation": "Twig compiles templates into PHP classes (extending Twig\\Template) and supports caching that compiled output between requests for performance."} | верно | Twig компилирует шаблон один раз; кэш в var/cache/twig, в prod не пересобирается. |
T13-L5 1.26 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 compiled DI container is cached and only rebuilt when tracked files (e.g., service configs, classes) change, not on every request.
Raw{"answer": "yes", "explanation": "In Symfony's dev environment, the compiled DI container is cached and only rebuilt when tracked files (e.g., service configs, classes) change, not on every request."} | верно | Kernel проверяет freshness ресурсов (конфиги, классы); иначе переиспользуется кэш контейнера. |
T13-L6 1.39 c | Symfony | Which environment variable selects the active Symfony environment (dev/prod)? | «app_env» Пояснение: In Symfony, the APP_ENV environment variable (e.g., APP_ENV=prod) selects the active environment (dev, prod, test).
Raw{"answer": "APP_ENV", "explanation": "In Symfony, the APP_ENV environment variable (e.g., APP_ENV=prod) selects the active environment (dev, prod, test)."} | верно | APP_ENV в .env; APP_DEBUG — отдельный флаг отладки. |
T13-L7 2.05 c | Symfony | A controller method can be private — Symfony routing works with any method of the class. | «no» Пояснение: Symfony's controller resolver calls the target method from outside the class, so it must be public; a private (or protected) method would throw an access error.
Raw{"answer": "no", "explanation": "Symfony's controller resolver calls the target method from outside the class, so it must be public; a private (or protected) method would throw an access error."} | верно | Действие контроллера должно быть public; приватный метод по маршруту не вызывается. |
T13-L8 2.0 c | Symfony | Event subscribers always receive events before listeners, because the interface gives them priority. | «no» Пояснение: Event subscribers and listeners are both dispatched by the EventDispatcher based on their numeric priority value; the EventSubscriberInterface itself does not grant any inherent priority over regular listeners.
Raw{"answer": "no", "explanation": "Event subscribers and listeners are both dispatched by the EventDispatcher based on their numeric priority value; the EventSubscriberInterface itself does not grant any inherent priority over regular listeners."} | верно | Порядок определяет 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 and standardized on the new authenticator architecture built around AuthenticatorInterface.
Raw{"answer": "yes", "explanation": "Symfony 6.0 removed the legacy Guard system and standardized on the new authenticator architecture built around AuthenticatorInterface."} | верно | Guard объявлен устаревшим в 5.3 и удалён в 6.0; в проекте symfony/security-bundle 8.1. |
T22-L2 2.38 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 (from Symfony/Security) checks a role or permission on a controller action and throws AccessDeniedException (403) if the user lacks it.
Raw{"answer": "IsGranted", "explanation": "The Symfony #[IsGranted] attribute (from Symfony/Security) checks a role or permission on a controller action and throws AccessDeniedException (403) if the user lacks it."} | верно | #[IsGranted('ROLE_ADMIN')]; атрибут из symfony/security-http. |
T22-L3 1.49 c | Symfony: Security and forms | Voters are Symfony's mechanism for checking access to a specific object: isGranted('EDIT', $post). | «yes» Пояснение: Voters in Symfony are the mechanism for object-level access control, and isGranted('EDIT', $post) delegates the check to registered voters.
Raw{"answer": "yes", "explanation": "Voters in Symfony are the mechanism for object-level access control, and isGranted('EDIT', $post) delegates the check to registered voters."} | верно | VoterInterface->vote(); docs Symfony — Voters. |
T22-L4 3.2 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 legacy Doctrine Annotations (@Assert\NotBlank) support was removed; validation constraints are now declared exclusively as native PHP attributes (#[Assert\NotBlank]).
Raw{"answer": "yes", "explanation": "In Symfony 7+ the legacy Doctrine Annotations (@Assert\\NotBlank) support was removed; validation constraints are now declared exclusively as native PHP attributes (#[Assert\\NotBlank])."} | верно | Докблок-аннотации удалены в Symfony 7.0; стандарт — атрибуты. В проекте symfony/validator 8.1. |
T22-L5 0.88 c | Symfony: Security and forms | CSRF protection of Symfony forms is enabled by default: the form validates the token on submission. | «yes» Пояснение: Symfony forms have CSRF protection enabled by default; a token is automatically generated and validated on submission unless explicitly disabled.
Raw{"answer": "yes", "explanation": "Symfony forms have CSRF protection enabled by default; a token is automatically generated and validated on submission unless explicitly disabled."} | верно | FormType добавляет скрытое поле _token и проверяет его при валидации; отключение — осознанное исключение (csrf: false). |
T22-L6 1.3 c | Symfony: Security and forms | Form validation in Symfony runs server-side even if the client-side (HTML5) checks passed. | «yes» Пояснение: Symfony form validation always runs server-side upon submission; HTML5 client-side checks are merely a UX enhancement and are never relied upon for actual validation.
Raw{"answer": "yes", "explanation": "Symfony form validation always runs server-side upon submission; HTML5 client-side checks are merely a UX enhancement and are never relied upon for actual validation."} | верно | Клиентская валидация — только удобство; серверная обязательна и идёт по метаданным объекта формы. |
T22-L7 0.63 c | Symfony: Security and forms | Which Symfony maker command generates a form class (FormType)? | «make:form» Пояснение: The Symfony MakerBundle command 'php bin/console make:form' generates a FormType class.
Raw{"answer": "make:form", "explanation": "The Symfony MakerBundle command 'php bin/console make:form' generates a FormType class."} | верно | bin/console make:form (symfony/maker-bundle — в проекте). |
T22-L8 1.35 c | Symfony: Security and forms | Symfony stores the user's password in the session in plain text. | «no» Пояснение: Symfony stores the user's identifier (e.g., user ID or serialized token) in the session, while the password is kept hashed in the database and is only used transiently during authentication.
Raw{"answer": "no", "explanation": "Symfony stores the user's identifier (e.g., user ID or serialized token) in the session, while the password is kept hashed in the database and is only used transiently during authentication."} | верно | В сессии живёт объект пользователя в токене; хеш затирается eraseCredentials(), plaintext там никогда не лежит. |
T23-L1 2.35 c | Symfony: configuration and services | Symfony bundle configuration lives in config/packages — one file per bundle or topic. | «yes» Пояснение: In modern Symfony (4+/Flex), the standard convention is to place one configuration file per bundle or topic in the config/packages/ directory (e.g., config/packages/doctrine.yaml, config/packages/monolog.yaml).
Raw{"answer": "yes", "explanation": "In modern Symfony (4+/Flex), the standard convention is to place one configuration file per bundle or topic in the config/packages/ directory (e.g., config/packages/doctrine.yaml, config/packages/monolog.yaml)."} | верно | Стандартная структура (config/packages/*.yaml); перегрузка — config/packages/<env>. |
T23-L2 4.7 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. | «no» Пояснение: The standard PHP (e.g., Laravel) convention is that .env.example is committed with defaults, while .env (and .env.local) remain uncommitted; the statement incorrectly says .env itself is committed.
Raw{"answer": "no", "explanation": "The standard PHP (e.g., Laravel) convention is that .env.example is committed with defaults, while .env (and .env.local) remain uncommitted; the statement incorrectly says .env itself is committed."} | неверно верный: «yes» | symfony/dotenv: .env — общий безопасный набор значений; локальные секреты — .env.local (gitignored) или secrets-хранилище. |
T23-L3 0.69 c | Symfony: configuration and services | Which Symfony command lists the container's registered services and their aliases? | «debug:container» Пояснение: The Symfony command 'debug:container' lists all registered services and their aliases in the service container.
Raw{"answer": "debug:container", "explanation": "The Symfony command 'debug:container' lists all registered services and their aliases in the service container."} | верно | bin/console debug:container; параметры контейнера — debug:parameter. |
T23-L4 4.95 c | Symfony: configuration and services | The Symfony container allows changing parameters at runtime: $container->setParameter() works from a controller. | «yes» Пояснение: The Symfony container does have a setParameter() method that can be called from a controller; it works as long as the container is not frozen (e.g., in development mode), though it's not a recommended practice.
Raw{"answer": "yes", "explanation": "The Symfony container does have a setParameter() method that can be called from a controller; it works as long as the container is not frozen (e.g., in development mode), though it's not a recommended practice."} | неверно верный: «no» | Контейнер компилируется и замораживается; runtime-значения — только через переменные окружения. |
T23-L5 0.91 c | Symfony: configuration and services | By default, Symfony services are public (public: true) — you can fetch them directly from the container. | «no» Пояснение: Since Symfony 4.0, services are private (public: false) by default; you must explicitly set public: true to fetch them directly from the container.
Raw{"answer": "no", "explanation": "Since Symfony 4.0, services are private (public: false) by default; you must explicitly set public: true to fetch them directly from the container."} | верно | С Symfony 4.0 сервисы по умолчанию private: инжектятся через autowiring; $container->get() — только для публичных. |
T23-L6 1.59 c | Symfony: configuration and services | Without a config file in config/packages a bundle will not work — configuration is mandatory for every bundle. | «no» Пояснение: Many Symfony bundles have sensible defaults and can work perfectly fine without any configuration file in config/packages; configuration is only required when a bundle needs specific settings.
Raw{"answer": "no", "explanation": "Many Symfony bundles have sensible defaults and can work perfectly fine without any configuration file in config/packages; configuration is only required when a bundle needs specific settings."} | верно | У бандлов есть встроенные умолчания (Extension); конфиг нужен только для отклонений от них. |
T23-L7 1.12 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 services.yaml and other configuration files to inject environment variable values into service definitions.
Raw{"answer": "yes", "explanation": "Symfony uses the %env(VAR)% syntax in services.yaml and other configuration files to inject environment variable values into service definitions."} | верно | %env(...)% резолвится в рантайме env-процессорами; docs — Env Var Processors. |
T23-L8 0.91 c | Symfony: configuration and services | Which Symfony environment variable enables debug mode (affects the profiler and Twig debugging)? | «app_debug» Пояснение: In Symfony, the APP_DEBUG environment variable (defined in .env) controls whether debug mode is enabled, affecting the profiler, Twig debug output, and exception pages.
Raw{"answer": "APP_DEBUG", "explanation": "In Symfony, the APP_DEBUG environment variable (defined in .env) controls whether debug mode is enabled, affecting the profiler, Twig debug output, and exception pages."} | верно | APP_DEBUG=1 (в .env dev-окружения); окружение выбирает APP_ENV — см. T13-L6. |
T16-L1 1.48 c | Symfony: Messenger | A single message in Symfony Messenger can only have one handler. | «no» Пояснение: In Symfony Messenger, a single message can be handled by multiple handlers, which are all invoked by default.
Raw{"answer": "no", "explanation": "In Symfony Messenger, a single message can be handled by multiple handlers, which are all invoked by default."} | верно | Messenger вызывает все хендлеры, подписанные на класс сообщения (docs — Multiple Handlers). |
T16-L2 1.13 c | Symfony: Messenger | The sync transport in Messenger queues the message for a worker, just like async. | «no» Пояснение: The sync transport dispatches and handles the message immediately within the current process, rather than queuing it for a worker.
Raw{"answer": "no", "explanation": "The sync transport dispatches and handles the message immediately within the current process, rather than queuing it for a worker."} | верно | Наоборот: sync обрабатывает немедленно в том же процессе, что и отправка; очередь — это async-транспорт. |
T16-L3 0.73 c | Symfony: Messenger | Which console command starts the worker that processes Messenger queue messages? | «messenger:consume» Пояснение: The Symfony command 'php bin/console messenger:consume' starts the worker that processes Messenger queue messages.
Raw{"answer": "messenger:consume", "explanation": "The Symfony command 'php bin/console messenger:consume' starts the worker that processes Messenger queue messages."} | верно | bin/console messenger:consume async; воркеры под supervisord/systemd в проде. |
T16-L4 1.3 c | Symfony: Messenger | Retries for failed messages (retry_strategy) are configured per Messenger transport. | «no» Пояснение: In Symfony Messenger, the retry_strategy is configured per message bus (under framework.messenger.buses), not per transport.
Raw{"answer": "no", "explanation": "In Symfony Messenger, the retry_strategy is configured per message bus (under framework.messenger.buses), not per transport."} | неверно верный: «yes» | retry_strategy на транспорте: max_retries, delay, multiplier; docs — Failed Messages & Retries. |
T16-L5 2.97 c | Symfony: Messenger | By default, Messenger serializes messages to JSON. | «yes» Пояснение: Symfony Messenger's default serializer (SerializerSerializer) uses the Symfony Serializer component with 'json' as the default format.
Raw{"answer": "yes", "explanation": "Symfony Messenger's default serializer (SerializerSerializer) uses the Symfony Serializer component with 'json' as the default format."} | неверно верный: «no» | Дефолтный сериализатор — PhpSerializer (serialize()); JSON-сериализатор включается отдельно. |
T16-L6 1.76 c | Symfony: Messenger | Symfony Scheduler produces messages on a schedule and dispatches them through Messenger. | «yes» Пояснение: Symfony Scheduler is designed to schedule tasks and dispatch them as messages through the Messenger component.
Raw{"answer": "yes", "explanation": "Symfony Scheduler is designed to schedule tasks and dispatch them as messages through the Messenger component."} | верно | Schedule → RecurringMessage → шина Messenger; docs — Scheduler. |
T16-L7 1.09 c | Symfony: Messenger | Which built-in Messenger transport stores messages in database tables via Doctrine? | «doctrine» Пояснение: Symfony Messenger's doctrine transport (doctrine://default) persists messages in a database table managed by Doctrine.
Raw{"answer": "doctrine", "explanation": "Symfony Messenger's doctrine transport (doctrine://default) persists messages in a database table managed by Doctrine."} | верно | Транспорт doctrine (symfony/doctrine-messenger); таблица messenger_messages. В проекте стоит amqp-messenger + doctrine-messenger. |
T16-L8 0.97 c | Symfony: Messenger | The Messenger pipeline can be extended with custom middleware, placed before or after the built-in ones. | «yes» Пояснение: Symfony Messenger allows you to add custom middleware at any position in the pipeline, before or after built-in middleware, via the 'messenger.buses' configuration.
Raw{"answer": "yes", "explanation": "Symfony Messenger allows you to add custom middleware at any position in the pipeline, before or after built-in middleware, via the 'messenger.buses' configuration."} | верно | messenger.bus.*.middleware в yaml; docs — Middleware. |
T28-L1 7.18 c | Symfony: versions | Symfony major releases come every two years, minor ones every six months (in May and November). | «yes» Пояснение: Symfony follows a release cadence where a new version ships every six months (May and November), with a major (breaking-change) release every two years.
Raw{"answer": "yes", "explanation": "Symfony follows a release cadence where a new version ships every six months (May and November), with a major (breaking-change) release every two years."} | верно | Стандартный релизный цикл: 8.0 — ноябрь 2025, 8.1 — май 2026, 8.2 — ноябрь 2026. |
T28-L2 0.68 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 1.25 c | Symfony: versions | Symfony 7.0 kept support for docblock annotations (validation, routes). | «no» Пояснение: Symfony 7.0 removed support for docblock annotations (doctrine/annotations) in favor of native PHP attributes.
Raw{"answer": "no", "explanation": "Symfony 7.0 removed support for docblock annotations (doctrine/annotations) in favor of native PHP attributes."} | верно | Наоборот: в 7.0 аннотации удалены — только PHP-атрибуты (#[Route], #[Assert\NotBlank]). |
T28-L4 1.45 c | Symfony: versions | AssetMapper manages CSS/JS without node or webpack — via importmap.php. | «yes» Пояснение: Symfony's AssetMapper component handles CSS/JS bundling, minification, and import management without Node.js or webpack, using importmap.php to define JavaScript imports.
Raw{"answer": "yes", "explanation": "Symfony's AssetMapper component handles CSS/JS bundling, minification, and import management without Node.js or webpack, using importmap.php to define JavaScript imports."} | верно | symfony/asset-mapper (с 6.3, стандарт с 7.x); в проекте — importmap.php в корне и asset-mapper 8.1. |
T28-L5 1.27 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 bug fix support until November 2025 and security fixes until November 2027.
Raw{"answer": "no", "explanation": "Symfony 6.4 is an LTS (Long-Term Support) release, with bug fix support until November 2025 and security fixes until November 2027."} | верно | Наоборот: 6.4 — LTS (расширенная поддержка); LTS выходит вместе с очередным мажором (6.4 — вместе с 7.0). |
T28-L6 1.47 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, the entire purpose of a major release is to remove the deprecations introduced in the previous major version; they do not persist.
Raw{"answer": "no", "explanation": "In Symfony, the entire purpose of a major release is to remove the deprecations introduced in the previous major version; they do not persist."} | верно | Наоборот: мажорный релиз удаляет всё устаревшее (7.0 убрал деприкейшены 6.x, 8.0 — 7.x). |
T28-L7 1.19 c | Symfony: versions | Every Symfony major release is accompanied by an UPGRADE guide listing the changes. | «yes» Пояснение: Symfony provides an UPGRADE file (e.g., UPGRADE-6.0.md) with each major release documenting deprecations, breaking changes, and migration steps.
Raw{"answer": "yes", "explanation": "Symfony provides an UPGRADE file (e.g., UPGRADE-6.0.md) with each major release documenting deprecations, breaking changes, and migration steps."} | верно | UPGRADE-7.0.md, UPGRADE-8.0.md в репозитории symfony/symfony. |
T28-L8 1.11 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 import maps without requiring node/webpack.
Raw{"answer": "AssetMapper", "explanation": "Symfony's AssetMapper component (introduced in Symfony 6.4/7.0) manages assets and import maps without requiring node/webpack."} | верно | symfony/asset-mapper 8.1 — в проекте. |
T29-L1 5.79 c | Symfony: 8.2 and beyond | As of 2026-11-07, Symfony 8.2 has already been released. | «no» Пояснение: Symfony typically releases new versions at the end of November (around Nov 29), so as of 2026-11-07, Symfony 8.2 would not yet have been released.
Raw{"answer": "no", "explanation": "Symfony typically releases new versions at the end of November (around Nov 29), so as of 2026-11-07, Symfony 8.2 would not yet have been released."} | верно | Наоборот: 8.2 ещё не выпущена — релиз в конце ноября 2026; последняя стабильная — 8.1. |
T29-L2 3.63 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, so 8.0 (Nov 2025), 8.1 (May 2026), and 8.2 (Nov 2026) are consistent with the pattern.
Raw{"answer": "yes", "explanation": "Symfony follows a six-month release cycle, so 8.0 (Nov 2025), 8.1 (May 2026), and 8.2 (Nov 2026) are consistent with the pattern."} | верно | Политика релизов: 8.1 — май 2026, 8.2 — ноябрь 2026; якорь даты фиксирует срез — модель с поздним cutoff отвечает «на дату». |
T29-L3 0.66 c | Symfony: 8.2 and beyond | Which Symfony version comes after 8.1 (as of 2026-11-07)? | «8.2» Пояснение: Symfony minor versions increment sequentially, so 8.2 follows 8.1.
Raw{"answer": "8.2", "explanation": "Symfony minor versions increment sequentially, so 8.2 follows 8.1."} | верно | 8.2 — следующий минорный релиз (ноябрь 2026); после его выхода проект переходит с 8.1.* на 8.2.*. |
T29-L4 2.41 c | Symfony: 8.2 and beyond | Symfony 8.2 is a major release requiring applications to be rewritten for new APIs. | «no» Пояснение: Symfony 8.2 is a minor release (not a major one), and even Symfony major releases are designed for incremental upgrades rather than complete rewrites.
Raw{"answer": "no", "explanation": "Symfony 8.2 is a minor release (not a major one), and even Symfony major releases are designed for incremental upgrades rather than complete rewrites."} | верно | Наоборот: 8.2 — минорный релиз; новые возможности без поломки обратной совместимости. Мажор — 9.0. |
T29-L5 2.27 c | Symfony: 8.2 and beyond | Updating within a major branch (8.1 → 8.2) should not require code changes — backward compatibility is preserved. | «yes» Пояснение: PHP minor version updates (e.g., 8.1 → 8.2) are backward compatible, meaning existing code should continue to work without changes; only major version bumps (e.g., 7 → 8) introduce breaking changes.
Raw{"answer": "yes", "explanation": "PHP minor version updates (e.g., 8.1 → 8.2) are backward compatible, meaning existing code should continue to work without changes; only major version bumps (e.g., 7 → 8) introduce breaking changes."} | верно | Политика Symfony: минорные релизы обратно совместимы; BC-break допустим только в мажорных. |
T29-L6 7.37 c | Symfony: 8.2 and beyond | Which minor version of the 8.x branch is released last, before Symfony 9.0? | «8.4» Пояснение: Symfony consistently ends each major branch at the .4 minor version (e.g., 4.4, 5.4, 6.4), which serves as the LTS release before the next major version, so 8.4 would be the last minor of the 8.x branch before 9.0.
Raw{"answer": "8.4", "explanation": "Symfony consistently ends each major branch at the .4 minor version (e.g., 4.4, 5.4, 6.4), which serves as the LTS release before the next major version, so 8.4 would be the last minor of the 8.x branch before 9.0."} | верно | По циклу: 8.2 (ноя 2026), 8.3 (май 2027), 8.4 (ноя 2027, вместе с 9.0) — как 6.4 выходила вместе с 7.0. |
T29-L7 4.4 c | Symfony: 8.2 and beyond | Symfony 8.2 will require PHP 8.5 — you would have to upgrade PHP along with it. | «no» Пояснение: Symfony 8.x is expected to require PHP 8.3 or 8.4 as its minimum, not PHP 8.5; each major Symfony version typically bumps the PHP requirement by one minor version (e.g., Symfony 7 requires PHP 8.2).
Raw{"answer": "no", "explanation": "Symfony 8.x is expected to require PHP 8.3 or 8.4 as its minimum, not PHP 8.5; each major Symfony version typically bumps the PHP requirement by one minor version (e.g., Symfony 7 requires PHP 8.2)."} | верно | Наоборот: минорные релизы не поднимают требования PHP; для всей ветки 8.x остаётся PHP >= 8.4. |
T29-L8 2.29 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 requires deprecations to last at least two major versions, so those added in 8.x will not be removed until 10.0, which is after 9.0.
Raw{"answer": "yes", "explanation": "Symfony's deprecation policy requires deprecations to last at least two major versions, so those added in 8.x will not be removed until 10.0, which is after 9.0."} | верно | Политика: деприкейшены живут до следующего мажора; 9.0 — ноябрь 2027. |
T21-L1 3.5 c | Twig | Inside {{ }}, Twig allows calling arbitrary PHP code directly. | «no» Пояснение: Twig's {{ }} syntax uses its own limited expression language (variables, filters, function calls, operators) rather than allowing arbitrary PHP code directly.
Raw{"answer": "no", "explanation": "Twig's {{ }} syntax uses its own limited expression language (variables, filters, function calls, operators) rather than allowing arbitrary PHP code directly."} | верно | Twig — DSL: только разрешённые окружением функции/фильтры; произвольный PHP не исполняется. |
T21-L2 0.79 c | Twig | By default, Twig auto-escapes printed variables. | «yes» Пояснение: Twig has auto-escaping enabled by default with the 'html' escape strategy, so variables printed with {{ }} are automatically HTML-escaped.
Raw{"answer": "yes", "explanation": "Twig has auto-escaping enabled by default with the 'html' escape strategy, so variables printed with {{ }} are automatically HTML-escaped."} | верно | Autoescape включён по умолчанию; {{ '<b>' }} → <b>. Проверено на Twig 3.30. |
T21-L3 1.2 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 a string for safe HTML output, though other contexts like js, css, or url can also be specified.
Raw{"answer": "yes", "explanation": "The Twig |e (escape) filter defaults to escaping a string for safe HTML output, though other contexts like js, css, or url can also be specified."} | верно | |e ('html') по умолчанию; есть контексты js/url/css. От SQL-инъекций он не защищает — это задача подготовленных запросов Doctrine. |
T21-L4 1.39 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 formats a number according to a given locale.
Raw{"answer": "number_format", "explanation": "The twig/intl-extra package provides the number_format filter which formats a number according to a given locale."} | неверно верный: «format_number» | |format_number(locale=...) из IntlExtension (twig/intl-extra есть в проекте). Проверено на Twig 3.30: 12345.6 → 12 345,6 (ru). |
T21-L5 1.86 c | Twig | The |raw filter disables auto-escaping for the value. | «yes» Пояснение: The |raw filter (in Twig) outputs a value without applying HTML auto-escaping.
Raw{"answer": "yes", "explanation": "The |raw filter (in Twig) outputs a value without applying HTML auto-escaping."} | верно | {{ x|raw }} выводит HTML как есть; опасно с пользовательскими данными. Проверено на Twig 3.30. |
T21-L6 0.97 c | Twig | In Twig, {{ }} prints an expression value, while {% %} executes tags — conditions, loops, set. | «yes» Пояснение: In Twig, {{ }} is used to output/echo expressions, while {% %} is used for structural tags like if, for, set, block, etc.
Raw{"answer": "yes", "explanation": "In Twig, {{ }} is used to output/echo expressions, while {% %} is used for structural tags like if, for, set, block, etc."} | верно | Два блока синтаксиса Twig: вывод (echo) против логики. |
T21-L7 1.05 c | Twig | In Twig you cannot declare a variable inside a template — values only come from the controller. | «no» Пояснение: Twig allows declaring variables inside templates using the {% set %} tag, so values are not limited to coming from the controller.
Raw{"answer": "no", "explanation": "Twig allows declaring variables inside templates using the {% set %} tag, so values are not limited to coming from the controller."} | верно | {% set y = ... %} объявляет переменную в шаблоне. Проверено на Twig 3.30. |
T21-L8 0.61 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.98 c | Bootstrap | Bootstrap is a CSS/JS library of ready-made UI components, not an SPA framework. | «yes» Пояснение: Bootstrap is a front-end CSS/JS toolkit providing pre-built UI components, while SPA frameworks are React, Angular, Vue, etc.
Raw{"answer": "yes", "explanation": "Bootstrap is a front-end CSS/JS toolkit providing pre-built UI components, while SPA frameworks are React, Angular, Vue, etc."} | верно | Компоненты и утилиты поверх вашего HTML; SPA-фреймворки (React/Vue) — другой класс инструментов. В проекте vendored 5.3.3. |
T24-L2 1.03 c | Bootstrap | Which Bootstrap class gives a responsive container with a fixed max width per breakpoint? | «container» Пояснение: The .container class in Bootstrap provides a responsive fixed-width container with a specific max-width at each breakpoint, while .container-fluid spans the full viewport width.
Raw{"answer": "container", "explanation": "The .container class in Bootstrap provides a responsive fixed-width container with a specific max-width at each breakpoint, while .container-fluid spans the full viewport width."} | верно | .container (фиксированная макс-ширина по брейкпоинтам) vs .container-fluid (на всю ширину). |
T24-L3 1.27 c | Bootstrap | The Bootstrap grid is built on CSS floats and splits a row into 16 columns. | «no» Пояснение: The Bootstrap grid splits a row into 12 columns (not 16), and modern versions (Bootstrap 4+) use Flexbox rather than CSS floats.
Raw{"answer": "no", "explanation": "The Bootstrap grid splits a row into 12 columns (not 16), and modern versions (Bootstrap 4+) use Flexbox rather than CSS floats."} | верно | Наоборот: flexbox (с Bootstrap 4) и 12 колонок; float-сетка — это Bootstrap 3. |
T24-L4 1.75 c | Bootstrap | Bootstrap's named breakpoints (the infix used in class names) are sm, md, lg, xl, xxl — five of them. | «yes» Пояснение: Bootstrap 5 defines exactly five named breakpoint infixes: sm, md, lg, xl, and xxl.
Raw{"answer": "yes", "explanation": "Bootstrap 5 defines exactly five named breakpoint infixes: sm, md, lg, xl, and xxl."} | верно | Тиров всего шесть: xs (без инфикса) + пять именованных (576/768/992/1200/1400 px). |
T24-L5 3.16 c | Bootstrap | Utilities like .mt-3 or .px-2 use the spacing scale: the number is a multiple of $spacer. | «no» Пояснение: The number in the utility class is an index into the $spacers map, not a direct multiplier of $spacer; for example, .mt-3 equals 1×$spacer, not 3×$spacer.
Raw{"answer": "no", "explanation": "The number in the utility class is an index into the $spacers map, not a direct multiplier of $spacer; for example, .mt-3 equals 1×$spacer, not 3×$spacer."} | верно | Spacing utilities; $spacer = 1rem. |
T24-L6 0.91 c | Bootstrap | Which Bootstrap 5 data attribute enables an interactive component (e.g. dropdown) on an element? | «data-bs-toggle» Пояснение: In Bootstrap 5, the data-bs-toggle attribute is used to enable interactive components such as dropdowns, modals, and collapses on an element.
Raw{"answer": "data-bs-toggle", "explanation": "In Bootstrap 5, the data-bs-toggle attribute is used to enable interactive components such as dropdowns, modals, and collapses on an element."} | верно | data-bs-toggle="dropdown" и т.п.; в Bootstrap 4 атрибут назывался data-toggle. |
T24-L7 0.63 c | Bootstrap | Bootstrap 5 components work without jQuery — in plain vanilla JS. | «yes» Пояснение: Bootstrap 5 removed its jQuery dependency and all components are implemented in plain vanilla JavaScript.
Raw{"answer": "yes", "explanation": "Bootstrap 5 removed its jQuery dependency and all components are implemented in plain vanilla JavaScript."} | верно | jQuery удалён в Bootstrap 5.0: data-bs-* атрибуты и JS API. В проекте vendored 5.3.3. |
T24-L8 1.24 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 root 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 root element, not a .dark class."} | верно | Наоборот: тема включается атрибутом data-bs-theme="dark" (Color modes, с 5.3); класса .dark не существует. В проекте 5.3.3. |
T14-L1 1.4 c | Doctrine | Doctrine ORM creates database tables on the fly the first time an entity is used at runtime. | «no» Пояснение: Doctrine ORM does not auto-create tables at runtime; you must explicitly create them via migrations or the schema tool before using the entities.
Raw{"answer": "no", "explanation": "Doctrine ORM does not auto-create tables at runtime; you must explicitly create them via migrations or the schema tool before using the entities."} | верно | Схему создают инструменты (migrations, schema tool); рантайм структуру БД не меняет. |
T14-L2 0.92 c | Doctrine | Which EntityManager method marks a new object as managed without executing SQL until flush()? | «persist» Пояснение: EntityManager::persist() marks a new entity as managed, deferring the actual INSERT SQL statement until flush() is called.
Raw{"answer": "persist", "explanation": "EntityManager::persist() marks a new entity as managed, deferring the actual INSERT SQL statement until flush() is called."} | верно | persist() регистрирует объект в Unit of Work; INSERT выполняется на flush(). |
T14-L3 3.52 c | Doctrine | In Doctrine ORM 3, the EntityManager::merge() method exists and makes the passed object managed. | «no» Пояснение: EntityManager::merge() was removed in Doctrine ORM 3; even in ORM 2 it returned a new managed copy rather than making the passed object itself managed.
Raw{"answer": "no", "explanation": "EntityManager::merge() was removed in Doctrine ORM 3; even in ORM 2 it returned a new managed copy rather than making the passed object itself managed."} | верно | В ORM 3 merge() удалён (в vendor проекта 3.7.6 метода нет); в Doctrine 2.x merge() возвращал управляемую копию. Версия зафиксирована — ORM 3. |
T14-L4 0.98 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 object-model level, referencing entity classes and their mapped fields rather than raw database tables and columns.
Raw{"answer": "yes", "explanation": "DQL (Doctrine Query Language) operates at the object-model level, referencing entity classes and their mapped fields rather than raw database tables and columns."} | верно | Doctrine транслирует DQL в SQL; docs — DQL (Doctrine Query Language). |
T14-L5 1.58 c | Doctrine | What does $repository->find(999) return when no record with id 999 exists? | «null» Пояснение: Doctrine's find() method returns null when no entity with the given ID exists in the database.
Raw{"answer": "null", "explanation": "Doctrine's find() method returns null when no entity with the given ID exists in the database."} | верно | find() возвращает null, если объект не найден (docs Repository methods). |
T14-L6 1.7 c | Doctrine | DoctrineBundle in Symfony automatically calls flush() at the end of every request. | «yes» Пояснение: By default, DoctrineBundle's auto_commit option is true, which causes the EntityManager to flush() and clear() pending changes at the end of each request via a kernel.response event listener.
Raw{"answer": "yes", "explanation": "By default, DoctrineBundle's auto_commit option is true, which causes the EntityManager to flush() and clear() pending changes at the end of each request via a kernel.response event listener."} | неверно верный: «no» | Авто-flush нет — flush() зовёт разработчик; незакрытая транзакция в конце запроса откатывается. |
T14-L7 2.17 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» Пояснение: In Doctrine ORM, once an entity is in the managed state, the Unit of Work tracks any property modifications, so flush() will generate and execute the UPDATE SQL without requiring an additional persist() call.
Raw{"answer": "yes", "explanation": "In Doctrine ORM, once an entity is in the managed state, the Unit of Work tracks any property modifications, so flush() will generate and execute the UPDATE SQL without requiring an additional persist() call."} | верно | Dirty checking сравнивает снимки свойств; persist нужен только новым/отсоединённым объектам. |
T14-L8 1.14 c | Doctrine | remove() executes the SQL DELETE immediately, without waiting for flush(). | «no» Пояснение: In Doctrine ORM, remove() only marks the entity as removed in the UnitOfWork; the actual SQL DELETE is executed when flush() is called.
Raw{"answer": "no", "explanation": "In Doctrine ORM, remove() only marks the entity as removed 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.44 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, since each transaction sees its own consistent snapshot of the data.
Raw{"answer": "no", "explanation": "MVCC in PostgreSQL allows readers and writers to operate concurrently without blocking each other, since each transaction sees its own consistent snapshot of the data."} | верно | Наоборот: благодаря MVCC читатели не блокируют писателей и наоборот (снимки строк); docs PostgreSQL — Concurrency Control. |
T15-L2 1.21 c | PostgreSQL | Which SQL command shows a query's execution plan without executing the query? | «explain» Пояснение: The EXPLAIN command (or EXPLAIN PLAN in Oracle) displays the query execution plan without actually running the query.
Raw{"answer": "EXPLAIN", "explanation": "The EXPLAIN command (or EXPLAIN PLAN in Oracle) displays the query execution plan without actually running the query."} | верно | EXPLAIN без ANALYZE только строит план; проверено на PostgreSQL 17.7. |
T15-L3 2.32 c | PostgreSQL | SERIAL and GENERATED ... AS IDENTITY are just two names for the same mechanism. | «no» Пояснение: SERIAL is syntactic sugar that creates a separate sequence and a DEFAULT clause, while GENERATED AS IDENTITY is the SQL-standard identity column mechanism with different internal handling and constraints.
Raw{"answer": "no", "explanation": "SERIAL is syntactic sugar that creates a separate sequence and a DEFAULT clause, while GENERATED AS IDENTITY is the SQL-standard identity column mechanism with different internal handling and constraints."} | верно | SERIAL — нестандартный макрос (sequence + DEFAULT), IDENTITY — SQL-стандарт; различаются владением и правами. Оба есть в PG 17 (проверено). |
T15-L4 1.07 c | PostgreSQL | By default, a PostgreSQL UNIQUE constraint allows only one row with NULL in the column. | «no» Пояснение: In PostgreSQL, a standard UNIQUE constraint treats NULL values as distinct, so multiple rows can have NULL in that column by default.
Raw{"answer": "no", "explanation": "In PostgreSQL, a standard UNIQUE constraint treats NULL values as distinct, so multiple rows can have NULL in that column by default."} | верно | Наоборот: NULLS DISTINCT по умолчанию — несколько NULL допустимы; NULLS NOT DISTINCT — опция с PG 15. Проверено на PG 17.7. |
T15-L5 0.72 c | PostgreSQL | Which PostgreSQL aggregate function concatenates strings with a separator? | «string_agg» Пояснение: PostgreSQL's string_agg() aggregate function concatenates strings with a user-specified separator.
Raw{"answer": "string_agg", "explanation": "PostgreSQL's string_agg() aggregate function concatenates strings with a user-specified separator."} | верно | string_agg(значение, разделитель); проверено на PostgreSQL 17.7. |
T15-L6 1.08 c | PostgreSQL | Plain VACUUM returns the space occupied by dead tuples to the operating system. | «no» Пояснение: Plain VACUUM only marks dead tuples' space as reusable within the table; VACUUM FULL is what rewrites the table and returns the space to the operating system.
Raw{"answer": "no", "explanation": "Plain VACUUM only marks dead tuples' space as reusable within the table; VACUUM FULL is what rewrites the table and returns the space to the operating system."} | верно | VACUUM помечает место для переиспользования внутри таблицы; ОС его возвращает только VACUUM FULL (с эксклюзивной блокировкой). |
T15-L7 0.64 c | PostgreSQL | Which keyword in a window function definition partitions rows into groups the function is computed over? | «partition by» Пояснение: The PARTITION BY clause in a window function definition partitions rows into groups over which the window function is computed.
Raw{"answer": "PARTITION BY", "explanation": "The PARTITION BY clause in a window function definition partitions rows into groups over which the window function is computed."} | верно | OVER (PARTITION BY ...); проверено на PostgreSQL 17.7. |
T15-L8 1.31 c | PostgreSQL | The READ COMMITTED isolation level protects against non-repeatable reads. | «no» Пояснение: READ COMMITTED only prevents dirty reads; non-repeatable reads are still possible because another transaction can commit a change to a row between two reads within the same transaction.
Raw{"answer": "no", "explanation": "READ COMMITTED only prevents dirty reads; non-repeatable reads are still possible because another transaction can commit a change to a row between two reads within the same transaction."} | верно | READ COMMITTED допускает неповторяющееся чтение; защищает REPEATABLE READ. Проверено: SHOW transaction_isolation → read committed. |
T17-L1 0.85 c | PostgreSQL: transactions and indexes | By default, PostgreSQL wraps each single SQL statement in its own implicit transaction (autocommit). | «yes» Пояснение: PostgreSQL defaults to autocommit mode, where each individual SQL statement is implicitly wrapped in its own transaction and committed automatically unless an explicit BEGIN is issued.
Raw{"answer": "yes", "explanation": "PostgreSQL defaults to autocommit mode, where each individual SQL statement is implicitly wrapped in its own transaction and committed automatically unless an explicit BEGIN is issued."} | верно | Без BEGIN каждый оператор коммитится сам; docs PostgreSQL — Transactions. Проверено на PG 17. |
T17-L2 0.46 c | PostgreSQL: transactions and indexes | Which SQL command ends a transaction, committing all its changes? | «commit» Пояснение: The COMMIT SQL command ends a transaction and permanently saves all changes made within it.
Raw{"answer": "COMMIT", "explanation": "The COMMIT SQL command ends a transaction and permanently saves all changes made within it."} | верно | COMMIT (END — синоним). Проверено на PG 17. |
T17-L3 1.21 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 by the query optimizer to locate rows quickly for SELECT, UPDATE, and DELETE statements alike, so any DML operation with a WHERE clause on an indexed column benefits from the index.
Raw{"answer": "yes", "explanation": "Indexes are used by the query optimizer to locate rows quickly for SELECT, UPDATE, and DELETE statements alike, so any DML operation with a WHERE clause on an indexed column benefits from the index."} | верно | Поиск строк для изменения идёт по индексу; docs PostgreSQL — Indexes. |
T17-L4 0.93 c | PostgreSQL: transactions and indexes | To roll back part of the statements inside a transaction, PostgreSQL uses SAVEPOINT. | «yes» Пояснение: SAVEPOINT in PostgreSQL allows you to roll back only a portion of a transaction to a specific named point, rather than rolling back the entire transaction.
Raw{"answer": "yes", "explanation": "SAVEPOINT in PostgreSQL allows you to roll back only a portion of a transaction to a specific named point, rather than rolling back the entire transaction."} | верно | SAVEPOINT name; ROLLBACK TO name — частичный откат без отмены всей транзакции. Проверено на PG 17. |
T17-L5 1.07 c | PostgreSQL: transactions and indexes | EXPLAIN ANALYZE shows the query plan without executing the query. | «no» Пояснение: EXPLAIN ANALYZE actually executes the query to report real execution times and row counts; plain EXPLAIN shows the plan without executing.
Raw{"answer": "no", "explanation": "EXPLAIN ANALYZE actually executes the query to report real execution times and row counts; plain EXPLAIN shows the plan without executing."} | верно | Наоборот: ANALYZE реально выполняет запрос (с побочными эффектами!) и показывает фактические времена узлов; план без выполнения — plain EXPLAIN. |
T17-L6 0.71 c | PostgreSQL: transactions and indexes | Which PostgreSQL extension adds vector types and indexes for embedding search? | «pgvector» Пояснение: pgvector is the PostgreSQL extension that adds a vector data type and index methods (IVFFlat, HNSW) for efficient embedding similarity search.
Raw{"answer": "pgvector", "explanation": "pgvector is the PostgreSQL extension that adds a vector data type and index methods (IVFFlat, HNSW) for efficient embedding similarity search."} | верно | CREATE EXTENSION vector (проект pgvector; в проекте образ pgvector/pgvector:pg17). |
T17-L7 1.13 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 ...) is indeed built only over the rows that satisfy the specified condition, making it smaller and more efficient for targeted queries.
Raw{"answer": "yes", "explanation": "A partial index (CREATE INDEX ... WHERE ...) is indeed built only over the rows that satisfy the specified condition, making it smaller and more efficient for targeted queries."} | верно | docs PostgreSQL — Partial Indexes; типичный кейс — индекс по «активным» записям. |
T17-L8 2.0 c | PostgreSQL: transactions and indexes | The SERIALIZABLE level in PostgreSQL is implemented by locking the rows a transaction reads. | «no» Пояснение: PostgreSQL implements SERIALIZABLE using SSI (Serializable Snapshot Isolation), which relies on MVCC snapshots and conflict detection at commit time rather than locking the rows a transaction reads.
Raw{"answer": "no", "explanation": "PostgreSQL implements SERIALIZABLE using SSI (Serializable Snapshot Isolation), which relies on MVCC snapshots and conflict detection at commit time rather than locking the rows a transaction reads."} | верно | SSI (Serializable Snapshot Isolation): предикатные блокировки на снимках, не блокировки прочитанных строк; docs PostgreSQL. |
T19-L1 0.78 c | HTTP and REST API | HTTP status 201 means the request resulted in a new resource being created. | «yes» Пояснение: HTTP status 201 'Created' indicates that the request has been successfully fulfilled and a new resource has been created.
Raw{"answer": "yes", "explanation": "HTTP status 201 'Created' indicates that the request has been successfully fulfilled and a new resource has been created."} | верно | 201 Created; обычно на POST, часто с Location; RFC 9110. |
T19-L2 1.33 c | HTTP and REST API | Which HTTP status means a successful request with an empty response body (e.g. after DELETE)? | «204» Пояснение: HTTP 204 No Content indicates a successful request with an empty response body, commonly returned after a DELETE operation.
Raw{"answer": 204, "explanation": "HTTP 204 No Content indicates a successful request with an empty response body, commonly returned after a DELETE operation."} | верно | 204 No Content; RFC 9110. |
T19-L3 2.58 c | HTTP and REST API | The DELETE method is idempotent per the HTTP specification: repeating the request for the same resource does not change the outcome. | «yes» Пояснение: Per RFC 9110, DELETE is idempotent: repeating the request for the same resource does not produce a different outcome beyond the initial deletion.
Raw{"answer": "yes", "explanation": "Per RFC 9110, DELETE is idempotent: repeating the request for the same resource does not produce a different outcome beyond the initial deletion."} | верно | RFC 9110: DELETE идемпотентен (как PUT); идемпотентность ≠ безопасность — ресурс удаляется при первом вызове. |
T19-L4 0.92 c | HTTP and REST API | The Access-Control-Allow-Origin header is sent by the client so that the server agrees to accept requests from another origin. | «no» Пояснение: The Access-Control-Allow-Origin header is sent by the server (not the client) to indicate which origin is permitted to access the resource.
Raw{"answer": "no", "explanation": "The Access-Control-Allow-Origin header is sent by the server (not the client) to indicate which origin is permitted to access the resource."} | верно | Наоборот: заголовок шлёт СЕРВЕР в ответе, разрешая браузеру cross-origin запрос (CORS); в проекте nelmio/cors-bundle. |
T19-L5 0.91 c | HTTP and REST API | Status 429 Too Many Requests is used when a client exceeds a rate limit. | «yes» Пояснение: HTTP 429 Too Many Requests is specifically defined to indicate that a client has exceeded a rate limit.
Raw{"answer": "yes", "explanation": "HTTP 429 Too Many Requests is specifically defined to indicate that a client has exceeded a rate limit."} | верно | 429 (+ Retry-After); RFC 6585. В проекте symfony/rate-limiter. |
T19-L6 0.78 c | HTTP and REST API | 5xx codes mean a client error, while 4xx means a server-side error. | «no» Пояснение: It's the opposite: 4xx codes indicate client errors and 5xx codes indicate server-side errors.
Raw{"answer": "no", "explanation": "It's the opposite: 4xx codes indicate client errors and 5xx codes indicate server-side errors."} | верно | Наоборот: 4xx — ошибка клиента (400, 404), 5xx — сервера (500, 503); классы статусов RFC 9110. |
T19-L7 0.5 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.92 c | HTTP and REST API | PATCH is not required to be idempotent per RFC 5789, unlike PUT. | «yes» Пояснение: RFC 5789 explicitly states that the PATCH method is not idempotent, whereas PUT is defined as idempotent in RFC 7231.
Raw{"answer": "yes", "explanation": "RFC 5789 explicitly states that the PATCH method is not idempotent, whereas PUT is defined as idempotent in RFC 7231."} | верно | RFC 5789 прямо оговаривает: PATCH не гарантированно идемпотентен; PUT идемпотентен. |
T20-L1 2.26 c | Security and OAuth | Checking a password by comparing its hash to the stored hash with a plain == is sufficient. | «no» Пояснение: Plain == is vulnerable to timing attacks and PHP's loose type juggling; hash_equals() should be used for constant-time comparison of hashes.
Raw{"answer": "no", "explanation": "Plain == is vulnerable to timing attacks and PHP's loose type juggling; hash_equals() should be used for constant-time comparison of hashes."} | верно | Нужна постоянновременная проверка (password_verify) — timing-атаки; соль и алгоритм уже внутри хеша. |
T20-L2 1.2 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» Пояснение: A CSRF token is generated by the server, stored in the session, and validated server-side on state-changing requests like POST, PUT, or DELETE to ensure the request originated from a legitimate user session.
Raw{"answer": "yes", "explanation": "A CSRF token is generated by the server, stored in the session, and validated server-side on state-changing requests like POST, PUT, or DELETE to ensure the request originated from a legitimate user session."} | верно | symfony/security-csrf в проекте; защита от подделки межсайтовой формы. |
T20-L3 0.83 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 enable and define a site's CSP, controlling which resources the browser is allowed to load.
Raw{"answer": "Content-Security-Policy", "explanation": "The Content-Security-Policy HTTP header is used to enable and define a site's CSP, controlling which resources the browser is allowed to load."} | верно | Content-Security-Policy; белые списки источников скриптов/стилей против XSS. |
T20-L4 2.31 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 authentication; the access token grants access to resources within scopes, while identifying who the user is is the role of the ID token in OpenID Connect (a layer on top of OAuth 2.0).
Raw{"answer": "no", "explanation": "OAuth 2.0 is an authorization protocol, not authentication; the access token grants access to resources within scopes, while identifying who the user is is the role of the ID token in OpenID Connect (a layer on top of OAuth 2.0)."} | верно | OAuth 2.0 — авторизация/делегирование доступа; аутентификацию добавляет OpenID Connect. В проекте knpuniversity/oauth2-client-bundle (yandex/github/google). |
T20-L5 2.26 c | Security and OAuth | XSS is prevented by validating input on the server before writing it to the database. | «no» Пояснение: XSS is primarily prevented by context-aware output encoding (escaping) when rendering data to the client, not by input validation before storing it in the database.
Raw{"answer": "no", "explanation": "XSS is primarily prevented by context-aware output encoding (escaping) when rendering data to the client, not by input validation before storing it in the database."} | верно | XSS лечится контекстным экранированием НА ВЫВОДЕ (Twig autoescape, CSP); валидация ввода не покрывает все контексты вывода. |
T20-L6 1.34 c | Security and OAuth | In the OAuth 2.0 authorization code flow, which parameter arrives at the redirect_uri and is exchanged for an access token? | «code» Пояснение: In the OAuth 2.0 authorization code flow, the 'code' parameter (authorization code) is returned in the redirect_uri and then exchanged at the token endpoint for an access token.
Raw{"answer": "code", "explanation": "In the OAuth 2.0 authorization code flow, the 'code' parameter (authorization code) is returned in the redirect_uri and then exchanged at the token endpoint for an access token."} | верно | Параметр code; обмен на токен POST-ом на /token с client_secret. |
T20-L7 0.88 c | Security and OAuth | A refresh token lives longer than an access token and allows obtaining a new access token without the user logging in again. | «yes» Пояснение: Refresh tokens are designed to be long-lived and are used to request new access tokens without requiring the user to re-authenticate.
Raw{"answer": "yes", "explanation": "Refresh tokens are designed to be long-lived and are used to request new access tokens without requiring the user to re-authenticate."} | верно | Стандартная схема OAuth/OIDC: короткий access + длинный refresh. |
T20-L8 1.57 c | Security and OAuth | A password salt must be kept secret: without it the hash cannot be verified. | «no» Пояснение: A password salt does not need to be kept secret; it is typically stored alongside the hash and its purpose is to prevent rainbow-table attacks, not to add secrecy.
Raw{"answer": "no", "explanation": "A password salt does not need to be kept secret; it is typically stored alongside the hash and its purpose is to prevent rainbow-table attacks, not to add secrecy."} | верно | Соль хранится открыто (password_hash включает её в строку хеша); секретность соли не нужна. |
T18-L1 1.15 c | Testing: PHPUnit | PHPUnit runs test methods of any class — extending TestCase is not required. | «no» Пояснение: PHPUnit requires test classes to extend PHPUnit\Framework\TestCase in order to recognize and execute their test methods.
Raw{"answer": "no", "explanation": "PHPUnit requires test classes to extend PHPUnit\\Framework\\TestCase in order to recognize and execute their test methods."} | верно | Тестом считается метод класса, наследующего TestCase (PHPUnit 10). |
T18-L2 0.83 c | Testing: PHPUnit | In PHPUnit, setUp() runs once before all tests of the class. | «no» Пояснение: setUp() runs before each test method; setUpBeforeClass() is the static method that runs once before all tests in the class.
Raw{"answer": "no", "explanation": "setUp() runs before each test method; setUpBeforeClass() is the static method that runs once before all tests in the class."} | верно | setUp() — перед КАЖДЫМ тестом; один раз на класс — setUpBeforeClass(). Проверено живым счётчиком на PHPUnit 10.5. |
T18-L3 1.27 c | Testing: PHPUnit | A data provider lets a test run with exactly one set of arguments. | «no» Пояснение: A data provider can supply multiple sets of arguments, causing the test to run once per set; it is not limited to exactly one set.
Raw{"answer": "no", "explanation": "A data provider can supply multiple sets of arguments, causing the test to run once per set; it is not limited to exactly one set."} | верно | Наоборот: наборов может быть сколько угодно — тест выполняется по разу на каждый. Проверено на PHPUnit 10.5 (#[DataProvider]). |
T18-L4 0.79 c | Testing: PHPUnit | Which PHPUnit method declares an expectation that an exception of a given class is thrown? | «expectexception» Пояснение: PHPUnit's expectException() method is used to declare that an exception of a given class is expected to be thrown during test execution.
Raw{"answer": "expectException", "explanation": "PHPUnit's expectException() method is used to declare that an exception of a given class is expected to be thrown during test execution."} | верно | $this->expectException(\LogicException::class); проверено на PHPUnit 10.5. |
T18-L5 1.22 c | Testing: PHPUnit | In PHPUnit, a stub verifies which methods were called on it, while a mock only returns data. | «no» Пояснение: The definition is reversed: a stub returns predefined data, while a mock verifies that expected methods were called.
Raw{"answer": "no", "explanation": "The definition is reversed: a stub returns predefined data, while a mock verifies that expected methods were called."} | верно | Наоборот: стаб подставляет данные, мок проверяет взаимодействия (createStub/createMock); docs PHPUnit — Test Doubles. |
T18-L6 1.6 c | Testing: PHPUnit | In PHPUnit 10+, the recommended way to pass data to a test is the #[DataProvider] attribute (the @dataProvider annotation is deprecated). | «yes» Пояснение: PHPUnit 10 introduced PHP 8 attributes as the preferred mechanism for test metadata, deprecating the old @dataProvider docblock annotation in favor of the #[DataProvider] attribute.
Raw{"answer": "yes", "explanation": "PHPUnit 10 introduced PHP 8 attributes as the preferred mechanism for test metadata, deprecating the old @dataProvider docblock annotation in favor of the #[DataProvider] attribute."} | верно | Аннотация ещё парсится в PHPUnit 10/11 (AnnotationParser в 10.5.66), удаление — в 12; атрибут — стандарт. |
T18-L7 1.22 c | Testing: PHPUnit | PHPUnit does not allow one test to depend on the result of another. | «no» Пояснение: PHPUnit supports test dependencies via the @depends annotation or the depends() method, allowing one test to depend on the result (even the return value) of another test.
Raw{"answer": "no", "explanation": "PHPUnit supports test dependencies via the @depends annotation or the depends() method, allowing one test to depend on the result (even the return value) of another test."} | верно | Зависимости есть: #[Depends] — зависимый тест не запустится, еслиProducer упал. |
T18-L8 1.79 c | Testing: PHPUnit | Which PHPUnit command-line option makes tests run in random order? | «--order-by=random» Пояснение: PHPUnit's --order-by=random option shuffles the test execution order.
Raw{"answer": "--order-by=random", "explanation": "PHPUnit's --order-by=random option shuffles the test execution order."} | верно | --order-by=random (PHPUnit 9+); опция есть в --help PHPUnit 10.5 (проектная). |
T01-L9 4.13 c | Syntax and operators | What does this code output?
```php
echo intdiv(7, 2) . intdiv(-7, 2);
``` | «3-3» Пояснение: intdiv(7,2) is 3 and intdiv(-7,2) is -3 (truncated toward zero), concatenated as the string '3-3'.
Raw{"answer": "3-3", "explanation": "intdiv(7,2) is 3 and intdiv(-7,2) is -3 (truncated toward zero), concatenated as the string '3-3'."} | верно | intdiv truncates toward zero: intdiv(-7, 2) = -3, not -4. |
T01-L10 3.19 c | Syntax and operators | What does this code output?
```php
echo -3 ** 2;
``` | «-9» Пояснение: In PHP, the ** (exponentiation) operator has higher precedence than the unary minus, so -3 ** 2 is parsed as -(3 ** 2) = -9.
Raw{"answer": -9, "explanation": "In PHP, the ** (exponentiation) operator has higher precedence than the unary minus, so -3 ** 2 is parsed as -(3 ** 2) = -9."} | верно | ** is right-associative and binds tighter than unary minus: -(3²). |
T02-L9 1.22 c | Types and comparisons | What does this code output?
```php
echo '1e1' == '10' ? 'true' : 'false';
``` | «true» Пояснение: Both '1e1' and '10' are numeric strings, so PHP compares them numerically (10 == 10), making the expression true.
Raw{"answer": "true", "explanation": "Both '1e1' and '10' are numeric strings, so PHP compares them numerically (10 == 10), making the expression true."} | верно | Both strings are numeric — compared as numbers: 10 == 10. |
T02-L10 4.01 c | Types and comparisons | What does this code output?
```php
switch ('a') {
case 0: echo 'zero'; break;
default: echo 'other';
}
``` | «zero» Пояснение: PHP switch uses loose comparison (==), and in PHP 7 'a' == 0 evaluates to true because a non-numeric string compared to an integer is converted to 0.
Raw{"answer": "zero", "explanation": "PHP switch uses loose comparison (==), and in PHP 7 'a' == 0 evaluates to true because a non-numeric string compared to an integer is converted to 0."} | неверно верный: «other» | PHP 8: 'a' == 0 → false (used to be true) — default fires. |
T03-L9 4.03 c | Strings | What does this code output?
```php
echo strtr('abc', ['a' => '1', 'ab' => '2']);
``` | «2c» Пояснение: strtr() with an array matches the longest key first, so 'ab' (length 2) is matched before 'a' (length 1), replacing 'ab' with '2' and leaving 'c', giving '2c'.
Raw{"answer": "2c", "explanation": "strtr() with an array matches the longest key first, so 'ab' (length 2) is matched before 'a' (length 1), replacing 'ab' with '2' and leaving 'c', giving '2c'."} | верно | strtr with an array prefers the longest matching key. |
T03-L10 2.85 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 offset (10) exceeds the string length (5), so the result is '[' + '' + ']' = '[]'.
Raw{"answer": "[]", "explanation": "substr('hello', -10) returns an empty string because the absolute value of the offset (10) exceeds the string length (5), so the result is '[' + '' + ']' = '[]'."} | неверно верный: «[hello]» | A negative start beyond the string is clamped to the beginning. |
T04-L9 1.96 c | Arrays | What does this code output?
```php
$a = ['k' => 1, 'n' => 2];
$b = ['k' => 9, 'm' => 3];
echo implode(',', array_keys($a + $b));
``` | «k,n,m» Пояснение: The + operator keeps all of $a's keys and adds only $b's keys not in $a, yielding keys k, n, m.
Raw{"answer": "k,n,m", "explanation": "The + operator keeps all of $a's keys and adds only $b's keys not in $a, yielding keys k, n, m."} | верно | The + operator: on duplicate string keys the left array wins. |
T04-L10 2.65 c | Arrays | What does this code output?
```php
$a = [[1, 'x', 2], [2, 'y', 1], [3, 'z', 2]];
usort($a, fn($p, $q) => $p[2] <=> $q[2]);
echo implode('', array_column($a, 1));
``` | «yxz» Пояснение: After sorting by the third element (index 2), the order is [2,'y',1], [1,'x',2], [3,'z',2]; array_column extracts index 1 giving ['y','x','z'], and implode joins them to 'yxz'.
Raw{"answer": "yxz", "explanation": "After sorting by the third element (index 2), the order is [2,'y',1], [1,'x',2], [3,'z',2]; array_column extracts index 1 giving ['y','x','z'], and implode joins them to 'yxz'."} | верно | Sorts are stable since 8.0: x and z keep their order on a tie. |
T05-L10 4.04 c | Functions and closures | What does this code output?
```php
function f(int $a, int $b): int
{
return $a - $b;
}
echo f(...['b' => 1, 'a' => 5]);
``` | «4» Пояснение: Spreading an array with string keys uses named arguments, so $a=5 and $b=1, giving 5-1=4.
Raw{"answer": 4, "explanation": "Spreading an array with string keys uses named arguments, so $a=5 and $b=1, giving 5-1=4."} | верно | String keys of a spread array become named arguments. |
T05-L9 16.08 c | Functions and closures | What does this code output?
```php
class P
{
private int $v = 3;
public function g(): int { return $this->v; }
}
$p = new P;
$f = $p->g(...);
$p = null;
echo $f();
``` | «3» Пояснение: The method g() is called immediately, returning 3 which is stored in $f; setting $p to null afterward doesn't affect the already-evaluated integer result.
Raw{"answer": 3, "explanation": "The method g() is called immediately, returning 3 which is stored in $f; setting $p to null afterward doesn't affect the already-evaluated integer result."} | верно | First-class callable syntax binds $this at creation time. |
T06-L9 0.77 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 resolves to the child class B that was actually instantiated.
Raw{"answer": "B", "explanation": "static::class uses late static binding, so it resolves to the child class B that was actually instantiated."} | верно | Late static binding: static::class is the receiver's class. |
T06-L10 1.58 c | OOP: classes and inheritance | What does this code output on PHP 8.5?
```php
class C
{
public int $x = 0 {
set { $this->x = $value * 2; }
}
}
$c = new C;
$c->x = 5;
echo $c->x;
``` | «10» Пояснение: The property setter multiplies the assigned value by 2, so setting $c->x = 5 stores 10, which is then echoed.
Raw{"answer": 10, "explanation": "The property setter multiplies the assigned value by 2, so setting $c->x = 5 stores 10, which is then echoed."} | верно | Inside the set hook, $this->x writes the backing store (no recursion): 5*2. |
T07-L9 1.41 c | Interfaces, traits, enum | What does this code output?
```php
trait TA
{
public function f(): string { return 'A'; }
}
trait TB
{
public function f(): string { return 'B'; }
}
class TC
{
use TA, TB { TB::f insteadof TA; TA::f as g; }
}
echo (new TC)->f() . (new TC)->g();
``` | «ba» Пояснение: TB::f insteadof TA makes f() return 'B', and TA::f as g aliases TA's f as g() returning 'A', so the concatenation is 'BA'.
Raw{"answer": "BA", "explanation": "TB::f insteadof TA makes f() return 'B', and TA::f as g aliases TA's f as g() returning 'A', so the concatenation is 'BA'."} | верно | insteadof picks the implementation; as keeps the other under an alias. |
T07-L10 1.38 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 static properties, so setting CX::$n does not affect CY::$n, which remains 0.
Raw{"answer": 0, "explanation": "Each class that uses a trait gets its own independent copy of static properties, so setting CX::$n does not affect CY::$n, which remains 0."} | верно | A trait's static property is copied into each consuming class. |
T08-L10 0.85 c | Exceptions and errors | What does this code output?
```php
function f(): int
{
try { return 1; } finally { return 2; }
}
echo f();
``` | «2» Пояснение: In PHP, a return statement in a finally block overrides the return value from the try block, so the function returns 2.
Raw{"answer": 2, "explanation": "In PHP, a return statement in a finally block overrides the return value from the try block, so the function returns 2."} | верно | A return in finally overrides the return from try. |
T08-L9 1.31 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 a new exception, it replaces the original exception, so the LogicException('second') is caught by the outer catch.
Raw{"answer": "second", "explanation": "When a finally block throws a new exception, it replaces the original exception, so the LogicException('second') is caught by the outer catch."} | верно | An exception from finally replaces the in-flight one — the last thrown is caught. |
T09-L9 2.31 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 is an alias for App\Foo via the use statement, so Baz::class resolves to App\Foo, while \Baz::class refers to the global class Baz, giving the concatenated string 'App\Foo|Baz'.
Raw{"answer": "App\\Foo|Baz", "explanation": "Baz is an alias for App\\Foo via the use statement, so Baz::class resolves to App\\Foo, while \\Baz::class refers to the global class Baz, giving the concatenated string 'App\\Foo|Baz'."} | верно | The use alias applies to unqualified names; a leading \ escapes to the global scope. |
T09-L10 2.87 c | Namespaces and autoloading | What does this code output?
```php
namespace Ns;
class Foo {}
$c = 'Foo';
echo (class_exists($c) ? 'yes' : 'no')
. (class_exists(__NAMESPACE__ . '\\' . $c) ? 'yes' : 'no');
``` | «noyes» Пояснение: class_exists('Foo') looks for a global class Foo (false, 'no'), while class_exists('Ns\Foo') finds the class defined in namespace Ns (true, 'yes'), concatenating to 'noyes'.
Raw{"answer": "noyes", "explanation": "class_exists('Foo') looks for a global class Foo (false, 'no'), while class_exists('Ns\\Foo') finds the class defined in namespace Ns (true, 'yes'), concatenating to 'noyes'."} | верно | Dynamic names are not resolved against the namespace — 'Foo' is the global class. |
T10-L9 1.23 c | References and scope | What does this code output?
```php
$a = [1, 2, 3];
foreach ($a as &$v) {}
$v = 99;
echo implode(',', $a);
``` | «1,2,99» Пояснение: After foreach by reference, $v still references the last element $a[2], so assigning $v=99 changes $a[2] to 99.
Raw{"answer": "1,2,99", "explanation": "After foreach by reference, $v still references the last element $a[2], so assigning $v=99 changes $a[2] to 99."} | верно | After a by-ref foreach, $v remains a reference to the last element. |
T10-L10 2.32 c | References and scope | What does this code output?
```php
class A
{
public function inc(): int
{
static $n = 0;
return ++$n;
}
}
class B extends A {}
$a = new A;
$b = new B;
$a->inc();
$b->inc();
echo $a->inc();
``` | «3» Пояснение: Static local variables in a method are shared per defining class; since B inherits inc() from A without redefining it, the same static $n is used across all calls, incrementing to 1, 2, 3.
Raw{"answer": 3, "explanation": "Static local variables in a method are shared per defining class; since B inherits inc() from A without redefining it, the same static $n is used across all calls, incrementing to 1, 2, 3."} | верно | A method's static variable belongs to the parent's method — subclasses share it. |
T11-L9 1.67 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) resumes the generator so $x=10, then return $x+1 gives 11, which getReturn() retrieves.
Raw{"answer": 11, "explanation": "send(10) resumes the generator so $x=10, then return $x+1 gives 11, which getReturn() retrieves."} | верно | send() resumes the generator: $x = 10, return 10+1. |
T11-L10 1.32 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() yields 1 and 2, then $r captures inner()'s return value 'ok', which is then yielded, producing the sequence 1,2,ok.
Raw{"answer": "1,2,ok", "explanation": "yield from inner() yields 1 and 2, then $r captures inner()'s return value 'ok', which is then yielded, producing the sequence 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.44 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 password_needs_rehash check returns false (cost matches at 4), and the second returns true (cost 5 differs from 4), so 'no' and 'yes' are concatenated.
Raw{"answer": "noyes", "explanation": "The first password_needs_rehash check returns false (cost matches at 4), and the second returns true (cost 5 differs from 4), so 'no' and 'yes' are concatenated."} | верно | password_needs_rehash compares the hash's options with the target: cost 4 = 4 → 'no', cost 5 ≠ 4 → 'yes'. |
T12-L10 3.2 c | Configuration and security | What does this code output on PHP 8.5?
```php
echo (E_ALL & 2048) === 0 ? 'strict-out' : 'strict-in';
``` | «strict-in» Пояснение: E_ALL (32767) includes the E_STRICT bit (2048), so E_ALL & 2048 equals 2048, which is not === 0, yielding 'strict-in'.
Raw{"answer": "strict-in", "explanation": "E_ALL (32767) includes the E_STRICT bit (2048), so E_ALL & 2048 equals 2048, which is not === 0, yielding 'strict-in'."} | неверно верный: «strict-out» | Since PHP 8.4, E_STRICT is out of E_ALL: the 2048 bit is unset → 'strict-out' (2048 is the historical E_STRICT bit). |
T13-L9 3.41 c | Symfony | What does this code output?
```php
use Symfony\Component\HttpFoundation\Request;
$r = Request::create('/demo', 'GET', [], [], [], ['HTTP_X_TOKEN' => 'abc']);
echo $r->headers->get('X-Token') === 'abc' ? 'mapped' : 'missing';
``` | «mapped» Пояснение: Symfony's HeaderBag normalizes HTTP_X_TOKEN to 'x-token', so headers->get('X-Token') correctly retrieves 'abc'.
Raw{"answer": "mapped", "explanation": "Symfony's HeaderBag normalizes HTTP_X_TOKEN to 'x-token', so headers->get('X-Token') correctly retrieves 'abc'."} | верно | The literal comparison requires knowing the mapping: HttpFoundation turns HTTP_X_TOKEN into the X-Token header (case-insensitive); without it the answer is 'missing'. |
T13-L10 1.15 c | Symfony | What does this code output?
```php
use Symfony\Component\EventDispatcher\EventDispatcher;
use Symfony\Contracts\EventDispatcher\Event;
$d = new EventDispatcher();
$out = '';
$d->addListener('e', function () use (&$out) { $out .= 'B'; }, 10);
$d->addListener('e', function () use (&$out) { $out .= 'A'; });
$d->addListener('e', function () use (&$out) { $out .= 'C'; }, 5);
$d->dispatch(new Event(), 'e');
echo $out;
``` | «bca» Пояснение: Symfony EventDispatcher calls listeners in descending priority order: priority 10 (B), priority 5 (C), then default priority 0 (A).
Raw{"answer": "BCA", "explanation": "Symfony EventDispatcher calls listeners in descending priority order: priority 10 (B), priority 5 (C), then default priority 0 (A)."} | верно | Listeners run by descending priority: 10 (B), 5 (C), 0 (A). |
T14-L10 1.42 c | Doctrine | Given: Doctrine ORM 3, an EntityManager on in-memory SQLite, entity User with an auto-increment primary key. The users table is empty. What does this code output?
```php
$u = new User(name: 'A');
$em->persist($u);
$em->flush();
$a = $em->find(User::class, $u->getId());
$b = $em->find(User::class, $u->getId());
echo spl_object_id($a) === spl_object_id($b) ? 'same' : 'diff';
``` | «same» Пояснение: Doctrine ORM's identity map ensures that calling find() with the same class and ID within the same EntityManager returns the same PHP object instance, so spl_object_id() will match.
Raw{"answer": "same", "explanation": "Doctrine ORM's identity map ensures that calling find() with the same class and ID within the same EntityManager returns the same PHP object instance, so spl_object_id() will match."} | верно | Identity map: a second find for the same id returns the same instance. |
T14-L9 3.94 c | Doctrine | Given: Doctrine ORM 3, an EntityManager on in-memory SQLite, entity User with an auto-increment primary key. The users table is empty. What does this code output?
```php
$u = new User(name: 'B');
$em->persist($u);
$em->remove($u);
$em->flush();
echo count($em->getConnection()->fetchAllAssociative('SELECT * FROM users'));
``` | «0» Пояснение: When an entity is persisted and then removed before flush, Doctrine cancels the pending insertion (removes it from the new-entities set), so flush performs no INSERT or DELETE and the table remains empty.
Raw{"answer": 0, "explanation": "When an entity is persisted and then removed before flush, Doctrine cancels the pending insertion (removes it from the new-entities set), so flush performs no INSERT or DELETE and the table remains empty."} | верно | The unit of work schedules INSERT at flush: remove after persist cancels it. |
T15-L10 1.14 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 x=1 and one with x=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 x=1 and one with x=NULL, so the result is 1."} | верно | count(column) skips NULLs; count(*) would return 2. |
T15-L9 1.62 c | PostgreSQL | What does this SQL query return (PostgreSQL 17)?
```sql
CREATE TEMP TABLE t (id int, x int);
INSERT INTO t VALUES (1, 10), (2, 20), (3, 30);
SELECT string_agg(s::text, ',' ORDER BY id) FROM (
SELECT id, sum(x) OVER (ORDER BY id) AS s FROM t
) q;
``` | «10,30,60» Пояснение: The window function computes a running sum (10, 30, 60) and string_agg concatenates them with commas in id order.
Raw{"answer": "10,30,60", "explanation": "The window function computes a running sum (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 2.58 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» Пояснение: Each middleware echoes its tag in order (M1 then M2) as the request passes through the stack before the final handler is reached.
Raw{"answer": "M1M2", "explanation": "Each middleware echoes its tag in order (M1 then M2) as the request passes through the stack before the final handler is reached."} | верно | The first-added middleware runs first (outermost). |
T16-L10 4.09 c | Symfony: Messenger | What does this code output?
```php
use Symfony\Component\Messenger\MessageBus;
use Symfony\Component\Messenger\Middleware\HandleMessageMiddleware;
use Symfony\Component\Messenger\Handler\HandlersLocator;
use Symfony\Component\Messenger\Handler\HandlerDescriptor;
use Symfony\Component\Messenger\Envelope;
class Ping {}
$n = 0;
$d1 = new HandlerDescriptor(function (Ping $m) use (&$n) { $n += 1; }, ['alias' => 'h1']);
$d2 = new HandlerDescriptor(function (Ping $m) use (&$n) { $n += 10; }, ['alias' => 'h2']);
$bus = new MessageBus([
new HandleMessageMiddleware(new HandlersLocator([Ping::class => [$d1, $d2]])),
]);
$bus->dispatch(new Envelope(new Ping()));
echo $n;
``` | «11» Пояснение: HandleMessageMiddleware iterates through all handlers in the HandlersLocator for the message class, so both handlers are called: $n = 0 + 1 + 10 = 11.
Raw{"answer": 11, "explanation": "HandleMessageMiddleware iterates through all handlers in the HandlersLocator for the message class, so both handlers are called: $n = 0 + 1 + 10 = 11."} | верно | All registered handlers of the message run: 1 + 10 = 11. |
T17-L9 1.48 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 index conflict and is skipped due to ON CONFLICT DO NOTHING, so the table has exactly one row.
Raw{"answer": 1, "explanation": "The first INSERT succeeds, the second hits the unique index conflict and is skipped due to ON CONFLICT DO NOTHING, so the table has exactly one row."} | верно | ON CONFLICT DO NOTHING skips the duplicate: one insert. |
T17-L10 1.61 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» Пояснение: Because the UNIQUE constraint is DEFERRABLE INITIALLY DEFERRED, the uniqueness check is postponed until the end of the transaction, so both INSERTs of the same value succeed within the same transaction, resulting in a count of 2.
Raw{"answer": 2, "explanation": "Because the UNIQUE constraint is DEFERRABLE INITIALLY DEFERRED, the uniqueness check is postponed until the end of the transaction, so both INSERTs of the same value succeed within the same transaction, resulting in a count of 2."} | верно | DEFERRED postpones the uniqueness check to COMMIT — count sees 2 rows. |
T18-L9 2.52 c | Testing: PHPUnit | How many tests will this command run?
```php
use PHPUnit\Framework\TestCase;
use PHPUnit\Framework\Attributes\DataProvider;
final class CalcTest extends TestCase
{
public static function prov(): array
{
return [[1], [2], [3]];
}
#[DataProvider('prov')]
public function test_sum(int $x): void
{
$this->assertTrue($x > 0);
}
#[DataProvider('prov')]
public function test_sum_abs(int $x): void
{
$this->assertTrue($x > 0);
}
public function test_other(): void
{
$this->assertTrue(true);
}
}
```
Command: `phpunit CalcTest.php --filter test_sum` (PHPUnit 10.5) | «6» Пояснение: The --filter 'test_sum' matches both test_sum (3 data sets) and test_sum_abs (3 data sets), giving 6 tests total, while test_other is excluded.
Raw{"answer": 6, "explanation": "The --filter 'test_sum' matches both test_sum (3 data sets) and test_sum_abs (3 data sets), giving 6 tests total, while test_other is excluded."} | верно | --filter is a substring match: test_sum also matches test_sum_abs (3+3 datasets). |
T18-L10 1.68 c | Testing: PHPUnit | How many tests will this command run, and how many of them will fail? Answer with two comma-separated numbers (ran, failed).
```php
use PHPUnit\Framework\TestCase;
use PHPUnit\Framework\Attributes\DataProvider;
final class Calc2Test extends TestCase
{
public function prov(): array
{
return [[1], [-1]];
}
#[DataProvider('prov')]
public function test_x(int $x): void
{
$this->assertTrue($x > 0);
}
}
```
Command: `phpunit Calc2Test.php` (PHPUnit 10.5) | «2, 1» Пояснение: The data provider yields two datasets ([1] and [-1]); $x=1 passes assertTrue, $x=-1 fails it, so 2 run, 1 fails.
Raw{"answer": "2, 1", "explanation": "The data provider yields two datasets ([1] and [-1]); $x=1 passes assertTrue, $x=-1 fails it, so 2 run, 1 fails."} | верно | 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.87 c | HTTP and REST API | Which HTTP method does this command send?
```bash
curl -s -d 'a=1' http://demo.local/api
``` | «post» Пояснение: The -d flag in curl sends data in the body and automatically sets the HTTP method to POST.
Raw{"answer": "POST", "explanation": "The -d flag in curl sends data in the body and automatically sets the HTTP method to POST."} | верно | -d/-F switches curl to POST by default. |
T19-L10 1.2 c | HTTP and REST API | Which HTTP method does this command send?
```bash
curl -s -G -d 'a=1' http://demo.local/api
``` | «get» Пояснение: The -G flag tells curl to use the GET method and append the -d data as query string parameters.
Raw{"answer": "GET", "explanation": "The -G flag tells curl to use the GET method and append the -d data as query string parameters."} | верно | -G turns -d data into the query string; the method stays GET. |
T20-L9 1.93 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_id is unknown/non-existent at the token endpoint, the error field is set to 'invalid_client'.
Raw{"answer": "invalid_client", "explanation": "Per RFC 6749 Section 5.2, when the client_id is unknown/non-existent at the token endpoint, the error field is set to 'invalid_client'."} | верно | Unknown client → invalid_client (RFC 6749 §5.2). |
T20-L10 1.46 c | Security and OAuth | OAuth 2.0: the client started the flow with response_type=token. In which part of the redirect_uri does the authorization server pass the access_token? | «fragment» Пояснение: In the OAuth 2.0 implicit flow (response_type=token), the access token is passed in the URI fragment (after the #) of the redirect_uri to avoid it appearing in server logs.
Raw{"answer": "fragment", "explanation": "In the OAuth 2.0 implicit flow (response_type=token), the access token is passed in the URI fragment (after the #) of the redirect_uri to avoid it appearing in server logs."} | верно | The implicit flow passes the token in the URL fragment (#) — it never reaches the server. |
T21-L9 1.54 c | Twig | What does this Twig template output?
```twig
{{ false|default(2) * 3 }}
``` | «0» Пояснение: The default filter only triggers on null/undefined, so false|default(2) returns false, and false * 3 equals 0.
Raw{"answer": 0, "explanation": "The default filter only triggers on null/undefined, so false|default(2) returns false, 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 4.26 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 this is parsed as 'a' ~ (1+2) which concatenates 'a' with 3 to produce the string 'a3' without throwing any exception.
Raw{"answer": "a3", "explanation": "In Twig, the + operator has higher precedence than ~, so this is parsed as 'a' ~ (1+2) which concatenates 'a' with 3 to produce the string 'a3' without throwing any exception."} | неверно верный: «runtimeerror» | In Twig ~ binds tighter than +: ('a' ~ 1) + 2 → string + int → a render error (RuntimeError). |
T22-L9 2.04 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, so NotBlank (which checks if an array is empty) passes, resulting in 0 violations.
Raw{"answer": 0, "explanation": "The value is an array [''] with one element, so NotBlank (which checks if an array is empty) passes, resulting in 0 violations."} | верно | NotBlank treats null, '', [] as blank — the array [''] is not blank. |
T22-L10 4.42 c | Symfony: Security and forms | What does this code output?
```php
use Symfony\Component\Form\Forms;
use Symfony\Component\Form\Extension\Core\Type\TextType;
$factory = Forms::createFormFactoryBuilder()->getFormFactory();
$form = $factory->create(TextType::class);
try {
echo $form->isValid() ? 'valid' : 'invalid';
} catch (Throwable $e) {
echo get_class($e);
}
``` | «invalid» Пояснение: A newly created Symfony form is not submitted, so isValid() returns false (isSubmitted() is false, short-circuiting the &&), printing 'invalid'.
Raw{"answer": "invalid", "explanation": "A newly created Symfony form is not submitted, so isValid() returns false (isSubmitted() is false, short-circuiting the &&), printing 'invalid'."} | неверно верный: «symfony\component\form\exception\logicexception» | isValid() on a non-submitted form throws LogicException, it does not return false. |
T23-L9 4.51 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 services are shared by default (setShared(true)), so calling get() twice returns the same cached instance.
Raw{"answer": "same", "explanation": "Symfony DI services are shared by default (setShared(true)), so calling get() twice returns the same cached instance."} | верно | Container services are shared: two get() calls yield one instance. |
T23-L10 1.92 c | Symfony: configuration and services | What does this code output?
```php
use Symfony\Component\DependencyInjection\ContainerBuilder;
$c = new ContainerBuilder();
$c->setParameter('name', 'Bob');
$c->setParameter('greeting', 'hi %name%');
$c->setParameter('message', '%greeting%!');
$c->compile();
echo $c->getParameter('message');
``` | «hi bob!» Пояснение: Symfony's ContainerBuilder resolves %param% references during compile(), so %greeting% expands to 'hi Bob' and the final message is 'hi Bob!'.
Raw{"answer": "hi Bob!", "explanation": "Symfony's ContainerBuilder resolves %param% references during compile(), so %greeting% expands to 'hi Bob' and the final message is 'hi Bob!'."} | верно | compile() resolves %-references transitively: %greeting% → 'hi %name%' → 'hi Bob!', the answer assembles over two hops. |
T24-L9 1.18 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 breakpoint (and up), the .container max-width is set to 960px.
Raw{"answer": "960px", "explanation": "In Bootstrap 5.3, at the 992px breakpoint (and up), the .container max-width is set to 960px."} | верно | 5.x container widths: 540/720/960/1140/1320 (sm–xxl); 992 → 960px. |
T24-L10 4.0 c | Bootstrap | Which utility sets the text color in Bootstrap 5.3 for `<p class="text-danger text-primary">…</p>`? Answer with the winning class name. | «text-danger» Пояснение: In Bootstrap 5.3's generated CSS, .text-danger appears after .text-primary with equal specificity, so it wins the cascade.
Raw{"answer": "text-danger", "explanation": "In Bootstrap 5.3's generated CSS, .text-danger appears after .text-primary with equal specificity, so it wins the cascade."} | верно | Specificity ties — the later rule wins: text-danger is declared after text-primary. |
T25-L9 1.31 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» Пояснение: Domain layer can only depend on Domain, but this class depends on both Application (PlaceOrder) and Infrastructure (Db), resulting in 2 violations.
Raw{"answer": 2, "explanation": "Domain layer can only depend on Domain, but this class depends on both Application (PlaceOrder) and Infrastructure (Db), resulting in 2 violations."} | верно | Domain may depend only on Domain: PlaceOrder (Application) + Db (Infrastructure) = 2. |
T25-L10 1.37 c | Clean architecture | Layers: Domain, Application, Infrastructure. Deptrac rules: Application → Domain; Infrastructure → Domain, Application; Domain → Domain only.
How many violations will deptrac report for this class?
```php
namespace App\Domain;
use App\Application\PlaceOrder;
use App\Infrastructure\Db;
class BillingService
{
public function __construct(
private PlaceOrder $handler,
private Db $db,
private \App\Infrastructure\Logger $logger,
) {}
}
``` | «3» Пояснение: The Domain layer can only depend on Domain, but the class references PlaceOrder (Application), Db (Infrastructure), and Logger (Infrastructure), giving 3 violations.
Raw{"answer": 3, "explanation": "The Domain layer can only depend on Domain, but the class references PlaceOrder (Application), Db (Infrastructure), and Logger (Infrastructure), giving 3 violations."} | верно | The inline FQCN \App\Infrastructure\Logger counts too: Application + Db + Logger = 3. |
T26-L10 1.58 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» Пояснение: The add method returns a new Money object with the sum (15), while the original $a retains its value of 10, so the output is '10,15'.
Raw{"answer": "10,15", "explanation": "The add method returns a new Money object with the sum (15), while the original $a retains its value of 10, so the output is '10,15'."} | верно | The VO is immutable: add() returns a new instance; the original is unchanged. |
T26-L9 1.56 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 (since count === 1), so the item 'a' remains and count() returns 1.
Raw{"answer": 1, "explanation": "The remove() method throws a DomainException before unsetting the item (since count === 1), so the item 'a' remains and count() returns 1."} | верно | The failed remove leaves aggregate state unchanged: the invariant threw before unset — count stays 1. |
VC-L9 3.34 c | PHP 8.4–8.5 | What does this code output on PHP 8.5?
```php
class C
{
public function hi(): string { return 'hi'; }
}
echo new C()->hi();
``` | «hi» Пояснение: The code instantiates class C, calls its hi() method which returns the string 'hi', and echoes it.
Raw{"answer": "hi", "explanation": "The code instantiates class C, calls its hi() method which returns the string 'hi', and echoes it."} | верно | Since 8.4, new in a method chain works without wrapping parentheses. |
VC-L10 5.73 c | PHP 8.4–8.5 | What does this code output on PHP 8.5?
```php
class Heavy
{
public int $v = 0;
}
$r = new ReflectionClass(Heavy::class);
$o = $r->newLazyGhost(function (Heavy $obj) {
$obj->v = 21;
});
echo $r->isUninitializedLazyObject($o) ? 'yes' : 'no';
$o->v;
echo $r->isUninitializedLazyObject($o) ? 'yes' : 'no';
``` | «yesno» Пояснение: Before triggering, isUninitializedLazyObject returns true ('yes'); after accessing $o->v which triggers the ghost and runs the callback, it returns false ('no').
Raw{"answer": "yesno", "explanation": "Before triggering, isUninitializedLazyObject returns true ('yes'); after accessing $o->v which triggers the ghost and runs the callback, it returns false ('no')."} | верно | newLazyGhost (8.4): the object stays lazy until first access — reading a property initializes it and clears the flag. |
T28-L9 1.42 c | Symfony: versions | The project was upgraded from Symfony 6.4 to 8.1. What does this code output on 8.1?
```php
echo class_exists(\Symfony\Component\Security\Guard\AbstractGuardAuthenticator::class)
? 'yes' : 'no';
``` | «no» Пояснение: The Security Guard component (including AbstractGuardAuthenticator) was deprecated in 5.3 and removed in 7.0, so it does not exist in Symfony 8.1.
Raw{"answer": "no", "explanation": "The Security Guard component (including AbstractGuardAuthenticator) was deprecated in 5.3 and removed in 7.0, so it does not exist in Symfony 8.1."} | верно | Guard authentication was removed in Symfony 7.0 — the class is gone in 8.1. |
T28-L10 2.45 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» Пояснение: In Symfony 7.0+ (and thus 8.1), AnnotationClassLoader was removed (replaced by AttributeClassLoader), so class_exists returns false for the first and true for the second, concatenating to 'noyes'.
Raw{"answer": "noyes", "explanation": "In Symfony 7.0+ (and thus 8.1), AnnotationClassLoader was removed (replaced by AttributeClassLoader), so class_exists returns false for the first and true for the second, concatenating to 'noyes'."} | верно | Annotation loaders were removed in 7.0; only attribute loaders remain (Annotation→Attribute). |