Пример запроса (первая клетка). System одинаковый во всех запросах прогона, user — свой вопрос для каждой клетки:
| Клетка | Тема | Утверждение | Ответ |
Результат | Обоснование |
T01-L1 2.37 c | Syntax and operators | Double-quoted and single-quoted strings are processed identically; the difference is only in speed. | «no» Пояснение: Single-quoted strings are not processed identically to double-quoted strings because double-quoted strings support variable interpolation and escape sequences, which single-quoted strings do not.
Raw{ ⏎ "answer": "false", ⏎ "explanation": "Single-quoted strings are not processed identically to double-quoted strings because double-quoted strings support variable interpolation and escape sequences, which single-quoted strings do not." ⏎ } | верно | В двойных кавычках работают интерполяция переменных и escape-последовательности, в одинарных — нет. |
T01-L2 0.47 c | Syntax and operators | The ?? operator follows isset semantics and raises no warnings for undefined variables. | «yes» Пояснение: The null coalescing operator (??) returns the right operand if the left is null or unset, and it explicitly avoids raising any warnings for undefined variables or null values.
Raw{"answer": "yes", "explanation": "The null coalescing operator (??) returns the right operand if the left is null or unset, and it explicitly avoids raising any warnings for undefined variables or null values."} | верно | ?? работает по семантике isset — несуществующие переменные и ключи допустимы. |
T01-L3 0.35 c | Syntax and operators | What will this print: echo 'a', 'b'; | «ab» Пояснение: The comma operator in an echo statement allows multiple string arguments to be printed consecutively.
Raw{ ⏎ "answer": "ab", ⏎ "explanation": "The comma operator in an echo statement allows multiple string arguments to be printed consecutively." ⏎ } | верно | echo принимает список аргументов: ab. |
T01-L4 0.48 c | Syntax and operators | print returns the value 1 and can be used inside an expression. | «no» Пояснение: In PHP, the `print` keyword returns the integer 1 and is not a function, so it cannot be used inside expressions (such as inside another function call or as an operand in an expression).
Raw{"answer": "no", "explanation": "In PHP, the `print` keyword returns the integer 1 and is not a function, so it cannot be used inside expressions (such as inside another function call or as an operand in an expression)."} | неверно верный: «yes» | print — выражение со значением 1, в отличие от echo, который значения не возвращает. |
T01-L5 0.34 c | Syntax and operators | The ?: (elvis) operator returns its left operand when it is falsy. | «no» Пояснение: The Elvis operator returns its left operand when it is truthy (not null), and otherwise returns its right operand.
Raw{"answer": "no", "explanation": "The Elvis operator returns its left operand when it is truthy (not null), and otherwise returns its right operand."} | верно | Наоборот: $a ?: $b возвращает $a, если он истинный, иначе $b. |
T01-L6 0.22 c | Syntax and operators | In PHP 8, the concatenation operator (.) has lower precedence than addition and subtraction. | «yes» Пояснение: ",
"expression": "true"
}
Raw{ ⏎ "answer": "yes", ⏎ "expression": "true" ⏎ } | верно | С PHP 8 (RFC concat precedence) '.' имеет приоритет ниже арифметики: 'сумма: ' . 2 + 3 → 'сумма: 5' (в PHP 7 было иначе). |
T01-L7 0.61 c | Syntax and operators | The expression 2 ** 3 ** 2 in PHP evaluates as (2 ** 3) ** 2, that is, 64. | «no» Пояснение: In PHP, the exponentiation operator (**), like in most programming languages, is right-associative, so 2 ** 3 ** 2 is evaluated as 2 ** (3 ** 2), which is 2 ** 9, equal to 512.
Raw{"answer": "no", "explanation": "In PHP, the exponentiation operator (**), like in most programming languages, is right-associative, so 2 ** 3 ** 2 is evaluated as 2 ** (3 ** 2), which is 2 ** 9, equal to 512."} | верно | ** право-ассоциативен: 2 ** (3 ** 2) = 2 ** 9 = 512. |
T01-L8 0.94 c | Syntax and operators | What string will this print: echo 'sum: ' . 2 + 3; (PHP 8)? | «sum: 2» Пояснение: In PHP, the dot concatenation operator (. ) has higher precedence than the plus operator (+), so the expression is evaluated as ('sum: ' . 2) + 3, which results in the string 'sum: 23' after the integer 3 is concatenated via type juggling, but wait: actually, string + int is not string concatenation; it's addition. Let me re-evaluate.
Raw{ ⏎ "answer": "sum: 2", ⏎ "explanation": "In PHP, the dot concatenation operator (. ) has higher precedence than the plus operator (+), so the expression is evaluated as ('sum: ' . 2) + 3, which results in the string 'sum: 23' after the integer 3 is concatenated via type juggling, but wait: actually, string + int is not string concatenation; it's addition. Let me re-evaluate." ⏎ } | неверно верный: «sum: 5» | Парная к verify-клетке про приоритет: 'сумма: 5'. |
T02-L1 0.44 c | Types and comparisons | With strict comparison (===), arrays are considered equal regardless of element order. | «no» Пояснение: Strict comparison (===) for arrays requires both the same number of elements and the same key/value pairs in the same order.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "Strict comparison (===) for arrays requires both the same number of elements and the same key/value pairs in the same order." ⏎ } | верно | === для массивов требует совпадения и значений, и их порядка. |
T02-L2 0.41 c | Types and comparisons | The comparison 0 == false returns false because it is a strict comparison. | «no» Пояснение: The == operator performs loose comparison, and in PHP 0 == false evaluates to true because 0 is converted to false.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "The == operator performs loose comparison, and in PHP 0 == false evaluates to true because 0 is converted to false." ⏎ } | верно | Наоборот: == — нестрогое сравнение и возвращает true; строгое — это === (0 === false → false). |
T02-L3 0.43 c | Types and comparisons | In PHP 8, the expression "abc" == 0 returns true. | «no» Пояснение: In PHP 8, loose comparisons between a string and 0 no longer return true; "abc" is no longer cast to 0.
Raw```json ⏎ {"answer": "no", "explanation": "In PHP 8, loose comparisons between a string and 0 no longer return true; \"abc\" is no longer cast to 0."} ⏎ ``` | верно | С PHP 8 нечисловая строка сравнивается как строка: "abc" == "0" → false (в PHP 7 было true). |
T02-L4 0.32 c | Types and comparisons | Under loose comparison, null equals 0, the empty string, and false at the same time. | «no» Пояснение: While null loosely equals false, it does not equal the empty string (null == "" is false).
Raw{"answer": "no", "explanation": "While null loosely equals false, it does not equal the empty string (null == \"\" is false)."} | неверно верный: «yes» | null == 0, null == "" и null == false — все true. |
T02-L5 0.43 c | Types and comparisons | What does the expression (int) '42abc' return? | «42» Пояснение: In PHP, casting a string to int parses the leading numeric portion until it encounters a non-numeric character, so '42abc' becomes 42.
Raw{"answer": 42, "explanation": "In PHP, casting a string to int parses the leading numeric portion until it encounters a non-numeric character, so '42abc' becomes 42."} | верно | Ведущая числовая часть: 42, без ошибок и warning. |
T02-L6 0.36 c | Types and comparisons | What does the expression '5' + 5 return? | «10» Пояснение: The string '5' is automatically coerced to the integer 5, so the addition results in 10.
Raw{"answer": 10, "explanation": "The string '5' is automatically coerced to the integer 5, so the addition results in 10."} | верно | Числовая строка приводится: int 10. |
T02-L7 0.41 c | Types and comparisons | When cast to string, false becomes "0". | «yes» Пояснение: In PHP, when the boolean false is explicitly cast to a string, it results in the empty string "" (zero-length string), not "0".
Raw{"answer": "yes", "explanation": "In PHP, when the boolean false is explicitly cast to a string, it results in the empty string \"\" (zero-length string), not \"0\"."} | неверно верный: «no» | false → "", true → "1". |
T02-L8 0.67 c | Types and comparisons | The comparison 0.1 + 0.2 === 0.3 returns false. | «yes» Пояснение: In PHP, the expression 0.1 + 0.2 results in the floating-point value 0.30000000000000004, which is not strictly identical (===) to the floating-point constant 0.3.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "In PHP, the expression 0.1 + 0.2 results in the floating-point value 0.30000000000000004, which is not strictly identical (===) to the floating-point constant 0.3." ⏎ } | верно | Двоичная погрешность float: 0.1 + 0.2 = 0.30000000000000004. |
T03-L1 0.43 c | Strings | strrev() correctly reverses a UTF-8 string. | «no» Пояснение: strrev() reverses a byte string, so it corrupts multi-byte UTF-8 sequences; use mb_strrev() for UTF-8 instead.
Raw{"answer": "no", "explanation": "strrev() reverses a byte string, so it corrupts multi-byte UTF-8 sequences; use mb_strrev() for UTF-8 instead."} | верно | strrev переворачивает байты и ломает многобайтовые последовательности. |
T03-L2 0.34 c | Strings | str_contains('Hello world', 'world') returns true. | «yes» Пояснение: The str_contains function checks if the needle 'world' exists in the haystack 'Hello world', which it does.
Raw{"answer": "yes", "explanation": "The str_contains function checks if the needle 'world' exists in the haystack 'Hello world', which it does."} | верно | str_contains с PHP 8.0 проверяет вхождение подстроки. |
T03-L3 0.37 c | Strings | str_pad() can pad a string on the right side only. | «no» Пояснение: str_pad() can pad the string on either the right or the left side using the $type parameter.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "str_pad() can pad the string on either the right or the left side using the $type parameter." ⏎ } | верно | STR_PAD_LEFT / STR_PAD_BOTH меняют сторону дополнения. |
T03-L4 0.31 c | Strings | By default trim() strips only spaces, leaving tabs and newlines intact. | «no» Пояснение: By default, trim() strips all whitespace characters, including spaces, tabs, and newlines.
Raw{"answer": "false", "explanation": "By default, trim() strips all whitespace characters, including spaces, tabs, and newlines."} | верно | Список символов по умолчанию: « \t\n\r\0\x0B» — пробелы, табы, переводы строк, возврат каретки, null-байт, вертикальный таб. Проверено php -r. |
T03-L5 0.42 c | Strings | How many BYTES does strlen('héllo') return for a UTF-8 string? | «6» Пояснение: The character 'é' in UTF-8 is encoded as 2 bytes, while the other four ASCII characters each occupy 1 byte, totaling 6 bytes.
Raw{"answer": 6, "explanation": "The character 'é' in UTF-8 is encoded as 2 bytes, while the other four ASCII characters each occupy 1 byte, totaling 6 bytes."} | верно | 6 букв по 2 байта: 12. |
T03-L6 0.37 c | Strings | What does substr('abcdef', -3) return? | «def» Пояснение: substr with a negative start value counts backwards from the end of the string, returning the last 3 characters.
Raw{"answer": "def", "explanation": "substr with a negative start value counts backwards from the end of the string, returning the last 3 characters."} | верно | Отрицательное смещение — с конца: def. |
T03-L7 0.36 c | Strings | ucfirst() modifies the string passed to it in place. | «no» Пояснение: In PHP, strings are values, so functions like ucfirst() return a modified copy rather than modifying the original string in place.
Raw{"answer": "no", "explanation": "In PHP, strings are values, so functions like ucfirst() return a modified copy rather than modifying the original string in place."} | верно | Строки неизменяемы; ucfirst возвращает новую строку. |
T03-L8 0.42 c | Strings | Variable interpolation works in heredoc but not in nowdoc. | «yes» Пояснение: Heredoc variables are interpolated like double-quoted strings, while nowdoc variables are not interpolated and must start with the dollar sign immediately after the opening marker.
Raw{"answer": "yes", "explanation": "Heredoc variables are interpolated like double-quoted strings, while nowdoc variables are not interpolated and must start with the dollar sign immediately after the opening marker."} | верно | Nowdoc — «одинарные кавычки» в тройном синтаксисе: текст как есть. |
T04-L1 0.4 c | Arrays | The sort() function preserves the key-to-value association of the array. | «no» Пояснение: The sort() function reindexes the array with integer keys starting from 0, thus destroying the original key-to-value associations.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "The sort() function reindexes the array with integer keys starting from 0, thus destroying the original key-to-value associations." ⏎ } | верно | sort перенумеровывает ключи; связь сохраняет asort. |
T04-L2 0.29 c | Arrays | The string key '5' in an array is stored as the integer 5. | «yes» Пояснение: PHP automatically casts string keys that represent integers into their integer equivalents when stored in arrays.
Raw{"answer": "yes", "explanation": "PHP automatically casts string keys that represent integers into their integer equivalents when stored in arrays."} | верно | Каноничные десятичные строковые ключи приводятся к int. |
T04-L3 0.41 c | Arrays | The in_array() function uses strict comparison (===) by default. | «no» Пояснение: The in_array() function uses non-strict comparison (==) by default, and a third boolean parameter can be set to true to enable strict comparison.
Raw{"answer": "no", "explanation": "The in_array() function uses non-strict comparison (==) by default, and a third boolean parameter can be set to true to enable strict comparison."} | верно | По умолчанию сравнение нестрогое; строгое — третий аргумент true. |
T04-L4 0.5 c | Arrays | Without a callback, array_filter() removes all "empty" (falsy) elements from the array. | «yes» Пояснение: array_filter() without a callback function removes all elements with a falsy value, such as 0, 0.0, false, empty strings, null, and empty arrays.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "array_filter() without a callback function removes all elements with a falsy value, such as 0, 0.0, false, empty strings, null, and empty arrays." ⏎ } | верно | Убирает 0, "", null, false и пустые массивы. |
T04-L5 0.32 c | Arrays | By default, array_slice() preserves the original numeric keys of the array. | «yes» Пояснение: By default, array_slice() preserves the keys of the array when slicing it.
Raw{"answer": "yes", "explanation": "By default, array_slice() preserves the keys of the array when slicing it."} | неверно верный: «no» | По умолчанию ключи перенумеровываются; сохранение — preserve_keys = true. |
T04-L6 0.41 c | Arrays | What does array_slice([10, 20, 30, 40], 1, 2) return? | «{"answer": [20, 30], "explanation": "array_slice returns a subarray starting at offset 1 with length 2, which yields [20, 30]."}» Пояснение: {"answer": [20, 30], "explanation": "array_slice returns a subarray starting at offset 1 with length 2, which yields [20, 30]."}
Raw{"answer": [20, 30], "explanation": "array_slice returns a subarray starting at offset 1 with length 2, which yields [20, 30]."} | верно парсинг: текст (фолбэк) | [20,30]; ключи перенумеровываются. |
T04-L7 0.55 c | Arrays | How many elements will count(['a' => 1] + ['a' => 9, 'b' => 2]) return? | «2» Пояснение: The '+' operator combines arrays without overwriting existing keys, so key 'a' is kept from the first array and key 'b' is added from the second, resulting in two elements.
Raw```json ⏎ {"answer": 2, "explanation": "The '+' operator combines arrays without overwriting existing keys, so key 'a' is kept from the first array and key 'b' is added from the second, resulting in two elements."} ⏎ ``` | верно | Оператор + : по ключу 'a' побеждает левый; итого 2. |
T04-L8 0.51 c | Arrays | Since PHP 8.1, the spread operator [...$a, ...$b] supports arrays with string keys. | «yes» Пояснение: Since PHP 8.1, the spread operator can be used with associative arrays (arrays with string keys) in array literals and function arguments.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "Since PHP 8.1, the spread operator can be used with associative arrays (arrays with string keys) in array literals and function arguments." ⏎ } ⏎ ``` | верно | В 8.0 — только числовые ключи; 8.1 снял ограничение. |
T05-L1 0.41 c | Functions and closures | Named arguments cannot be combined with argument unpacking ...$args in a single call. | «no» Пояснение: In PHP 8.0 and later, named arguments can be used together with argument unpacking (spread operator) in a function call.
Raw{"answer": "false", "explanation": "In PHP 8.0 and later, named arguments can be used together with argument unpacking (spread operator) in a function call."} | верно | Можно: f(...$args, имя: значение). Нельзя только позиционный аргумент после распаковки. |
T05-L2 0.38 c | Functions and closures | An anonymous function without use sees variables from the outer scope. | «yes» Пояснение: In PHP, an anonymous function without a 'use' declaration is dynamically scoped by default and can access variables from the scope where it is defined.
Raw{"answer": "yes", "explanation": "In PHP, an anonymous function without a 'use' declaration is dynamically scoped by default and can access variables from the scope where it is defined."} | неверно верный: «no» | Без use внешние переменные недоступны; авто-захват только у fn. |
T05-L3 0.43 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)? | «1» Пояснение: The function f declares exactly one parameter, $a, and func_num_args() counts only the arguments passed to the function's parameter list, so it returns 1.
Raw{"answer": 1, "explanation": "The function f declares exactly one parameter, $a, and func_num_args() counts only the arguments passed to the function's parameter list, so it returns 1."} | неверно верный: «3» | Считает переданные аргументы: 3. |
T05-L4 0.35 c | Functions and closures | The body of an arrow function fn may consist of several expressions in curly braces. | «no» Пояснение: Arrow function bodies that use curly braces must contain exactly one return statement, not multiple arbitrary expressions.
Raw{"answer": "no", "explanation": "Arrow function bodies that use curly braces must contain exactly one return statement, not multiple arbitrary expressions."} | верно | fn — всегда одно выражение; блок операторов делает обычная анонимная функция. |
T05-L5 0.36 c | Functions and closures | An arrow function fn captures outer variables by reference (lazily, at use time). | «no» Пояснение: Arrow functions in PHP capture the values of local and global variables by value at the time the function is defined, not by reference.
Raw{"answer": "no", "explanation": "Arrow functions in PHP capture the values of local and global variables by value at the time the function is defined, not by reference."} | верно | fn захватывает только по значению, автоматически; по ссылке — только &$var в use у обычной функции (fn так не умеет). |
T05-L6 0.34 c | Functions and closures | A closure declared as static function () {} does not capture $this. | «yes» Пояснение: A static closure does not have access to $this, so it does not capture it.
Raw```json ⏎ {"answer": "yes", "explanation": "A static closure does not have access to $this, so it does not capture it."} ⏎ ``` | верно | static-замыкание отвязано от объекта: $this внутри недоступен. |
T05-L7 0.42 c | Functions and closures | What will this print: $x = 5; $f = function () use ($x) { return $x; }; $x = 7; echo $f(); | «5» Пояснение: The use keyword captures the value of $x at the time the closure is created, so the closure always returns 5 regardless of the later assignment to $x.
Raw{"answer": "5", "explanation": "The use keyword captures the value of $x at the time the closure is created, so the closure always returns 5 regardless of the later assignment to $x."} | верно | use захватывает по значению в момент создания: 5. |
T05-L8 0.39 c | Functions and closures | In weak typing mode (without strict_types), passing the string "5" to an int parameter is allowed. | «yes» Пояснение: In PHP weak typing mode, numeric strings like "5" are implicitly coerced to integers when passed to int parameters.
Raw{"answer": "yes", "explanation": "In PHP weak typing mode, numeric strings like \"5\" are implicitly coerced to integers when passed to int parameters."} | верно | Coercive typing приводит "5" к 5; strict_types=1 требует точного типа. |
T06-L1 0.4 c | OOP: classes and inheritance | PHP supports constructor property promotion: public function __construct(private int $x) {}. | «yes» Пояснение: PHP 8.0 introduced constructor property promotion, which allows defining class properties directly within the constructor's parameter list while also assigning the parameter values to them.
Raw{"answer": "yes", "explanation": "PHP 8.0 introduced constructor property promotion, which allows defining class properties directly within the constructor's parameter list while also assigning the parameter values to them."} | верно | С PHP 8.0 параметр с модификатором создаёт свойство и присваивание. |
T06-L2 0.37 c | OOP: classes and inheritance | Which keyword prevents a method from being overridden in subclasses? | «final» Пояснение: In PHP, the 'final' keyword prevents a method from being overridden in any of its subclasses.
Raw{ ⏎ "answer": "final", ⏎ "explanation": "In PHP, the 'final' keyword prevents a method from being overridden in any of its subclasses." ⏎ } | верно | final. |
T06-L3 0.34 c | OOP: classes and inheritance | A method declared final cannot be overridden in a subclass. | «yes» Пояснение: In PHP, marking a method as final prevents it from being overridden in derived classes.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "In PHP, marking a method as final prevents it from being overridden in derived classes." ⏎ } | верно | final запрещает переопределение метода и наследование класса. |
T06-L4 0.35 c | OOP: classes and inheritance | Parent properties with private visibility are accessible in a subclass. | «no» Пояснение: Private properties declared in a parent class are not accessible within the methods of a subclass.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "Private properties declared in a parent class are not accessible within the methods of a subclass." ⏎ } | верно | В подклассе видны protected и public; private — только внутри своего класса. |
T06-L5 0.36 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 classes in PHP are internally named 'class', and get_class() returns that name.
Raw{ ⏎ "answer": "class", ⏎ "explanation": "Anonymous classes in PHP are internally named 'class', and get_class() returns that name." ⏎ } | неверно верный: «class@anonymous» | get_class анонимного класса печатает class@anonymous\0<файл>:<строка>$n; короткая форма — часть до NUL-байта. Проверено php -r (hex). |
T06-L6 0.53 c | OOP: classes and inheritance | A private parent method is not part of the inheritance contract: a child may declare a method with the same name and any visibility. | «yes» Пояснение: Private methods are not inherited by child classes, so a child class can declare a method with the same name using any visibility without affecting the parent's contract.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "Private methods are not inherited by child classes, so a child class can declare a method with the same name using any visibility without affecting the parent's contract." ⏎ } ⏎ ``` | верно | private-члены не наследуются — правила совместимости подписей не действуют. |
T06-L7 0.42 c | OOP: classes and inheritance | The magic method __get() is called only for non-existent properties. | «yes» Пояснение: PHP's __get() magic method is triggered only when an attempt is made to access a property that is undefined or inaccessible on the object.
Raw{"answer": "yes", "explanation": "PHP's __get() magic method is triggered only when an attempt is made to access a property that is undefined or inaccessible on the object."} | неверно верный: «no» | __get срабатывает и для существующих, но недоступных (private/protected извне). |
T06-L8 0.3 c | OOP: classes and inheritance | What does reassigning a readonly property throw — Exception or Error? | «error» Пояснение: Reassigning a readonly property in PHP 8.1+ throws an Error.
Raw{"answer": "Error", "explanation": "Reassigning a readonly property in PHP 8.1+ throws an Error."} | верно | Error (readonly с 8.1); оговорка: в __clone() переинициализация допустима (8.3+). |
T07-L1 0.31 c | Interfaces, traits, enum | An interface can declare constants. | «yes» Пояснение: In PHP, interfaces can define public constants using the const keyword.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "In PHP, interfaces can define public constants using the const keyword." ⏎ } | верно | Константы интерфейса наследуются реализациями. |
T07-L2 0.35 c | Interfaces, traits, enum | Which operator checks whether an object is an instance of a class or interface? | «instanceof» Пояснение: The instanceof operator checks if a variable is an instance of a specific class or interface.
Raw{ ⏎ "answer": "instanceof", ⏎ "explanation": "The instanceof operator checks if a variable is an instance of a specific class or interface." ⏎ } | верно | instanceof. |
T07-L3 0.28 c | Interfaces, traits, enum | An interface can declare static methods. | «yes» Пояснение: As of PHP 8.1, interfaces can declare abstract static methods.
Raw{"answer": "yes", "explanation": "As of PHP 8.1, interfaces can declare abstract static methods."} | верно | Реализация обязана дать статический метод с той же сигнатурой. |
T07-L4 0.33 c | Interfaces, traits, enum | The instanceof operator only checks class inheritance: it ignores interfaces. | «no» Пояснение: The instanceof operator in PHP checks whether an object is an instance of a given class or implements a given interface.
Raw{"answer": "no", "explanation": "The instanceof operator in PHP checks whether an object is an instance of a given class or implements a given interface."} | верно | instanceof возвращает true и для интерфейсов объекта. |
T07-L5 0.36 c | Interfaces, traits, enum | An interface method may have a default implementation, like a trait method. | «no» Пояснение: In PHP, interface methods are abstract and cannot have a default implementation, whereas trait methods can.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "In PHP, interface methods are abstract and cannot have a default implementation, whereas trait methods can." ⏎ } | верно | Методы интерфейса — только сигнатуры; тело даёт реализующий класс. |
T07-L6 0.45 c | Interfaces, traits, enum | An abstract method in an abstract class may have protected visibility. | «yes» Пояснение: Abstract methods in PHP can be declared with public, protected, or private visibility, though only public and protected are typically inherited and implementable by child classes.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Abstract methods in PHP can be declared with public, protected, or private visibility, though only public and protected are typically inherited and implementable by child classes." ⏎ } | верно | В абстрактном классе — любая видимость; в интерфейсе — только public. |
T07-L7 0.33 c | Interfaces, traits, enum | How many elements will Foo::cases() return for enum Foo { case A; case B; case C; }? | «3» Пояснение: The Foo::cases() method returns all 3 defined enum cases: A, B, and C.
Raw{"answer": 3, "explanation": "The Foo::cases() method returns all 3 defined enum cases: A, B, and C."} | верно | Статический метод cases(): 3. |
T07-L8 0.28 c | Interfaces, traits, enum | A trait can declare constants. | «yes» Пояснение: Traits in PHP have supported the declaration of constants since PHP 5.3.
Raw{"answer": "yes", "explanation": "Traits in PHP have supported the declaration of constants since PHP 5.3."} | верно | С PHP 8.2 трейты могут объявлять константы (RFC constants_in_traits); до 8.2 — нет. |
T08-L1 0.35 c | Exceptions and errors | The Throwable interface is a common ancestor of both Exception and Error. | «yes» Пояснение: In PHP, the Throwable interface is the top-level interface that both Exception and Error classes implement, making it their common ancestor.
Raw{"answer": "yes", "explanation": "In PHP, the Throwable interface is the top-level interface that both Exception and Error classes implement, making it their common ancestor."} | верно | Иерархия с PHP 7: Throwable → Exception и Throwable → Error. |
T08-L2 0.34 c | Exceptions and errors | A catch (Exception $e) block will also catch TypeError, because TypeError ultimately inherits from Exception. | «no» Пояснение: TypeError is a subclass of Error, not Exception, so it is not caught by a catch block specifically for Exception.
Raw{"answer": "no", "explanation": "TypeError is a subclass of Error, not Exception, so it is not caught by a catch block specifically for Exception."} | верно | TypeError наследуется от Error; catch (Exception) его не ловит. |
T08-L3 0.26 c | Exceptions and errors | The @ operator suppresses exceptions too. | «yes» Пояснение: The @ operator suppresses all warnings, notices, and exceptions.
Raw{"answer": "yes", "explanation": "The @ operator suppresses all warnings, notices, and exceptions."} | неверно верный: «no» | @ глушит диагностику (warnings/notices), исключения не перехватывает. |
T08-L4 0.35 c | Exceptions and errors | What error class does intdiv(5, 0) throw? | «divisionbyzeroerror» Пояснение: In PHP 8+, attempting integer division by zero throws a DivisionByZeroError.
Raw{ ⏎ "answer": "DivisionByZeroError", ⏎ "explanation": "In PHP 8+, attempting integer division by zero throws a DivisionByZeroError." ⏎ } | верно | DivisionByZeroError (иерархия Error, не Exception); php-грейдер объективен. |
T08-L5 0.33 c | Exceptions and errors | The finally block runs only if the exception was caught by a catch block. | «no» Пояснение: The finally block always executes, regardless of whether an exception was thrown and caught.
Raw```json ⏎ {"answer": "no", "explanation": "The finally block always executes, regardless of whether an exception was thrown and caught."} ⏎ ``` | верно | Наоборот: finally выполняется всегда — даже когда исключение не поймано и уходит выше. Проверено php -r. |
T08-L6 0.44 c | Exceptions and errors | An exception thrown inside a finally block has no effect on the result of the try block. | «no» Пояснение: An exception thrown inside a finally block does affect the result by replacing the original exception or propagating a new one, thereby altering the final outcome.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "An exception thrown inside a finally block does affect the result by replacing the original exception or propagating a new one, thereby altering the final outcome." ⏎ } | верно | Исключение из finally перекрывает исходное и уходит вместо него. |
T08-L7 0.61 c | Exceptions and errors | What does the expression (bool) new Exception('x') return? | «no» Пояснение: Casting an object to bool in PHP returns false (no), since non-empty objects are truthy only if they are instances of the Throwable interface or have a __toString method, but an Exception object cast to bool generally evaluates to false in this context.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "Casting an object to bool in PHP returns false (no), since non-empty objects are truthy only if they are instances of the Throwable interface or have a __toString method, but an Exception object cast to bool generally evaluates to false in this context." ⏎ } | неверно верный: «true» | Любой объект при приведении к bool — true. Формы ответа: true или да. |
T08-L8 0.52 c | Exceptions and errors | Functions registered via register_shutdown_function() run when exit is called. | «no» Пояснение: Functions registered via register_shutdown_function() run when the script execution ends normally or abnormally (including fatal errors), but they do not run if the script is terminated by calling exit().
Raw{ ⏎ "answer": "no", ⏎ "explanation": "Functions registered via register_shutdown_function() run when the script execution ends normally or abnormally (including fatal errors), but they do not run if the script is terminated by calling exit()." ⏎ } | неверно верный: «yes» | exit завершает скрипт, но shutdown-функции отрабатывают. |
T09-L1 0.38 c | Namespaces and autoloading | The use App\Service\Mailer; statement itself loads the class file. | «yes» Пояснение: The 'use' statement in PHP is a compile-time construct that loads the class file immediately when encountered during the compilation phase of the script.
Raw{"answer": "yes", "explanation": "The 'use' statement in PHP is a compile-time construct that loads the class file immediately when encountered during the compilation phase of the script."} | неверно верный: «no» | use — псевдоним на этапе компиляции; файл грузит автозагрузчик при первом обращении. |
T09-L2 0.35 c | Namespaces and autoloading | What follows use to import a function (not a class): the word function or const? | «function» Пояснение: In PHP, the 'function' keyword is used to import a function, whereas 'const' is used for constants.
Raw{"answer": "function", "explanation": "In PHP, the 'function' keyword is used to import a function, whereas 'const' is used for constants."} | верно | use function ...; (и use const для констант). |
T09-L3 0.38 c | Namespaces and autoloading | Into which file (path from src/) does the PSR-4 mapping "App\ → src/" place the class App\Controller\Api\UserController? | «src/controller/api/usercontroller.php» Пояснение: PSR-4 replaces namespace separators with directory separators and appends .php to the class name.
Raw{"answer": "src/Controller/Api/UserController.php", "explanation": "PSR-4 replaces namespace separators with directory separators and appends .php to the class name."} | верно | Остаток имени после префикса, \ → /. |
T09-L4 0.44 c | Namespaces and autoloading | Including vendor/autoload.php registers autoloaders via spl_autoload_register(). | «yes» Пояснение: Including vendor/autoload.php typically triggers composer's autoload files which register autoloader callbacks using spl_autoload_register() to map class names to their file paths.
Raw{"answer": "yes", "explanation": "Including vendor/autoload.php typically triggers composer's autoload files which register autoloader callbacks using spl_autoload_register() to map class names to their file paths."} | верно | Composer ставит автозагрузчик именно на spl_autoload_register. |
T09-L5 0.37 c | Namespaces and autoloading | The magic constant __NAMESPACE__ contains the name of the current namespace. | «yes» Пояснение: The __NAMESPACE__ magic constant indeed expands to the name of the namespace in which the code is declared.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "The __NAMESPACE__ magic constant indeed expands to the name of the namespace in which the code is declared." ⏎ } | верно | В корневом пространстве — пустая строка. |
T09-L6 0.43 c | Namespaces and autoloading | An unqualified class name (without a leading \) in new is resolved from the global root. | «yes» Пояснение: In PHP, an unqualified class name inside a method of a non-global class is resolved in the current namespace, not the global root.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "In PHP, an unqualified class name inside a method of a non-global class is resolved in the current namespace, not the global root." ⏎ } | неверно верный: «no» | Резолвится относительно текущего namespace (с учётом импортов). |
T09-L7 0.46 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 uses directory separation to replace namespace backslashes, so App\Model\User maps to src/Model/User.php.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "PSR-4 uses directory separation to replace namespace backslashes, so App\\Model\\User maps to src/Model/User.php." ⏎ } ⏎ ``` | верно | Остаток имени после префикса переносится в путь как есть. |
T09-L8 0.49 c | Namespaces and autoloading | A use statement may be written inside a function body — the import then applies to that function only. | «no» Пояснение: In PHP, a use statement must be declared in the global scope or as a class constant/import, and cannot be written inside a function body to limit its scope to that function.
Raw{"answer": "no", "explanation": "In PHP, a use statement must be declared in the global scope or as a class constant/import, and cannot be written inside a function body to limit its scope to that function."} | верно | use внутри тела функции — parse error; импорты файловые и компиляционные. |
T10-L1 0.35 c | References and scope | Arrays are copied on assignment rather than passed by reference. | «no» Пояснение: PHP uses copy-on-write semantics, so arrays are copied on assignment rather than passed by reference, meaning this statement is true.
Raw{"answer": "no", "explanation": "PHP uses copy-on-write semantics, so arrays are copied on assignment rather than passed by reference, meaning this statement is true."} | неверно верный: «yes» | Присваивание массива — копия (в движке — copy-on-write). |
T10-L2 0.5 c | References and scope | What will this print: $a = [1, 2]; $b = $a; $b[] = 3; echo count($a); | «2» Пояснение: PHP arrays are passed by value, so modifying $b[] = 3 does not affect $a, which still contains only 1 and 2.
Raw```json ⏎ { ⏎ "answer": 2, ⏎ "explanation": "PHP arrays are passed by value, so modifying $b[] = 3 does not affect $a, which still contains only 1 and 2." ⏎ } ⏎ ``` | верно | Присваивание — копия: в $a по-прежнему 2 элемента. |
T10-L3 0.44 c | References and scope | Inside a function, user-defined global variables are inaccessible without global, $GLOBALS, or passing them as parameters. | «yes» Пояснение: Variables defined in the global scope are not accessible within a function's local scope unless explicitly declared with 'global' or accessed via the $GLOBALS superglobal.
Raw{"answer": "yes", "explanation": "Variables defined in the global scope are not accessible within a function's local scope unless explicitly declared with 'global' or accessed via the $GLOBALS superglobal."} | верно | Область видимости функций изолирована; исключение — суперглобалы ($_GET и др.). |
T10-L4 0.45 c | References and scope | unset($GLOBALS['x']) inside a function removes the global variable only for that function. | «no» Пояснение: unset() inside a function will actually remove the global variable from the global scope, not just for that function, as long as you are accessing the global scope through the $GLOBALS array.
Raw{"answer": "no", "explanation": "unset() inside a function will actually remove the global variable from the global scope, not just for that function, as long as you are accessing the global scope through the $GLOBALS array."} | верно | $GLOBALS — прямое окно в глобальную область: unset удалит её по-настоящему. |
T10-L5 0.42 c | References and scope | What will this print: function inc(&$x) { $x++; } $n = 5; inc($n); echo $n; | «6» Пояснение: The function inc() modifies the variable $n by reference, incrementing it from 5 to 6 before the echo statement.
Raw{ ⏎ "answer": 6, ⏎ "explanation": "The function inc() modifies the variable $n by reference, incrementing it from 5 to 6 before the echo statement." ⏎ } | верно | Ссылка меняет оригинал: 6. |
T10-L6 0.44 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` iterates over a copy of the array, so modifications to the array inside the loop do not affect the current iteration pass.
Raw{"answer": "no", "explanation": "In PHP, `foreach` iterates over a copy of the array, so modifications to the array inside the loop do not affect the current iteration pass."} | верно | По значению foreach итерирует копию-снимок. |
T10-L7 0.42 c | References and scope | A static property belongs to each instance separately: changes in one object are not visible in others. | «no» Пояснение: Static properties belong to the class itself, not individual instances, so changes made through one object are visible to all other objects of that class.
Raw{"answer": "no", "explanation": "Static properties belong to the class itself, not individual instances, so changes made through one object are visible to all other objects of that class."} | верно | Наоборот: статическое свойство общее для всех экземпляров класса. Проверено php -r. |
T10-L8 0.36 c | References and scope | An array can have a boolean key true, and it will be stored as bool. | «no» Пояснение: Boolean keys are cast to integers (false to 0, true to 1) when used as array keys in PHP.
Raw{"answer": "no", "explanation": "Boolean keys are cast to integers (false to 0, true to 1) when used as array keys in PHP."} | верно | Булев ключ приводится к int: true → 1, false → 0. |
T11-L1 0.43 c | Generators, iterators, SPL | Inside a generator, return with a value can be used, and it becomes available via $gen->getReturn(). | «yes» Пояснение: Since PHP 7.2, generators support return values that can be retrieved via the GeneratorInterface's getReturn() method after the generator is exhausted or terminated by return.
Raw{"answer": "yes", "explanation": "Since PHP 7.2, generators support return values that can be retrieved via the GeneratorInterface's getReturn() method after the generator is exhausted or terminated by return."} | верно | return-значение генератора доступно через getReturn() после прохода. |
T11-L2 0.42 c | Generators, iterators, SPL | A fully consumed generator can be rewound with rewind() and traversed again. | «yes» Пояснение: In PHP 8.2+, the rewind() function can be called on a generator to reset its state and allow it to be traversed from the beginning again.
Raw{"answer": "yes", "explanation": "In PHP 8.2+, the rewind() function can be called on a generator to reset its state and allow it to be traversed from the beginning again."} | неверно верный: «no» | Генератор одноразовый: rewind после начала итерации бросает Exception. |
T11-L3 0.33 c | Generators, iterators, SPL | The yield from construct delegates traversal to another generator or iterable. | «yes» Пояснение: The yield from syntax in PHP 5.5+ delegates the yielding process to another generator or iterable object.
Raw{"answer": "yes", "explanation": "The yield from syntax in PHP 5.5+ delegates the yielding process to another generator or iterable object."} | верно | yield from проксирует значения, ключи и return-значение внутреннего генератора. |
T11-L4 0.35 c | Generators, iterators, SPL | What does get_class(g()) return for function g() { yield 1; }? | «generator» Пояснение: Calling a generator function in PHP returns a Generator object, so get_class on it returns the class name 'Generator'.
Raw{"answer": "Generator", "explanation": "Calling a generator function in PHP returns a Generator object, so get_class on it returns the class name 'Generator'."} | верно | Функция с yield возвращает Generator. |
T11-L5 0.56 c | Generators, iterators, SPL | How many elements will count(iterator_to_array((function () { yield from [1, 2, 3]; })())) return? | «3» Пояснение: The closure yields three elements (1, 2, 3) via the yield from operator on the array [1, 2, 3], which iterator_to_array() collects into an array of 3 elements.
Raw```json ⏎ {"answer": "3", "explanation": "The closure yields three elements (1, 2, 3) via the yield from operator on the array [1, 2, 3], which iterator_to_array() collects into an array of 3 elements."} ⏎ ``` | верно | yield from делегирует все 3 элемента. |
T11-L6 0.33 c | Generators, iterators, SPL | The SplStack class implements a FIFO queue. | «no» Пояснение: SplStack implements a LIFO stack, while SplQueue implements a FIFO queue.
Raw{"answer": "no", "explanation": "SplStack implements a LIFO stack, while SplQueue implements a FIFO queue."} | верно | SplStack — стек LIFO; очередь FIFO — SplQueue. |
T11-L7 0.33 c | Generators, iterators, SPL | ArrayIterator allows wrapping an array and traversing it via the Iterator interface. | «yes» Пояснение: The ArrayIterator class is a built-in PHP class that implements the Iterator interface to wrap and traverse an array.
Raw{"answer": "yes", "explanation": "The ArrayIterator class is a built-in PHP class that implements the Iterator interface to wrap and traverse an array."} | верно | Объектная обёртка над массивом. |
T11-L8 0.39 c | Generators, iterators, SPL | An ArrayObject instance cannot be traversed with foreach. | «no» Пояснение: ArrayObject is implemented to support the Iterator and ArrayAccess interfaces, allowing it to be traversed directly using foreach.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "ArrayObject is implemented to support the Iterator and ArrayAccess interfaces, allowing it to be traversed directly using foreach." ⏎ } | верно | ArrayObject реализует IteratorAggregate — foreach по нему работает. |
T12-L1 0.4 c | Configuration and security | password_hash() generates a salt automatically — passing one separately is not needed. | «yes» Пояснение: password_hash() automatically generates and stores a unique salt for each password, so you do not need to provide a separate salt.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "password_hash() automatically generates and stores a unique salt for each password, so you do not need to provide a separate salt." ⏎ } | верно | Соль встраивается в строку результата; параметр salt устарел. |
T12-L2 0.34 c | Configuration and security | In PHP 8, PASSWORD_DEFAULT is md5 with an automatically added salt. | «no» Пояснение: PASSWORD_DEFAULT currently uses Argon2id (or bcrypt as a fallback), not md5.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "PASSWORD_DEFAULT currently uses Argon2id (or bcrypt as a fallback), not md5." ⏎ } | верно | PASSWORD_DEFAULT — bcrypt; md5 для паролей непригоден (перебирается массово). |
T12-L3 0.3 c | Configuration and security | What does password_verify('secret', password_hash('secret', PASSWORD_DEFAULT)) return? | «true» Пояснение: password_verify() returns a boolean, which is true when the password matches the hash.
Raw{"answer": "true", "explanation": "password_verify() returns a boolean, which is true when the password matches the hash."} | верно | Соль и хеш в одной строке: true (форма ответа: true или да). |
T12-L4 0.35 c | Configuration and security | strip_tags() protects against SQL injection. | «no» Пояснение: strip_tags() only removes or escapes HTML tags, not SQL-specific characters, so it does not protect against SQL injection.
Raw{"answer": "no", "explanation": "strip_tags() only removes or escapes HTML tags, not SQL-specific characters, so it does not protect against SQL injection."} | верно | strip_tags режет HTML-теги (помощник против XSS), к параметризации SQL отношения не имеет. |
T12-L5 0.34 c | Configuration and security | session_regenerate_id() is used to protect against session fixation upon user login. | «yes» Пояснение: session_regenerate_id() issues a new session identifier, invalidating the old one, which prevents session fixation attacks.
Raw{"answer": "yes", "explanation": "session_regenerate_id() issues a new session identifier, invalidating the old one, which prevents session fixation attacks."} | верно | Новый ID сессии после логина — стандартная защита от session fixation. |
T12-L6 0.47 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 name of the current SAPI (Server API), such as 'cli' or 'apache2handler'.
Raw{"answer": "php_sapi_name", "explanation": "php_sapi_name() is the built-in PHP function that returns the name of the current SAPI (Server API), such as 'cli' or 'apache2handler'."} | верно | php_sapi_name(). |
T12-L7 0.39 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 deletes the server-side session data; the client-side cookie must be manually deleted before the session is destroyed.
Raw{"answer": "yes", "explanation": "session_destroy() only deletes the server-side session data; the client-side cookie must be manually deleted before the session is destroyed."} | верно | Удаление cookie — отдельный шаг через setcookie с истёкшим сроком. |
T12-L8 0.32 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 to initialize the session.
Raw{"answer": "no", "explanation": "The $_SESSION array is only populated with session data after session_start() is called to initialize the session."} | верно | Без session_start() данные сессии в массив не загружаются ($_SESSION можно заполнить вручную, но привязки к сессии нет). |
VC-L1 0.26 c | PHP 8.4–8.5 | In which PHP version was the array_find() function introduced? | «false» Пояснение: There is no built-in array_find() function in PHP.
Raw{"answer": "false", "explanation": "There is no built-in array_find() function in PHP."} | неверно верный: «8.4» | PHP 8.4 (RFC array_find). |
VC-L2 0.63 c | PHP 8.4–8.5 | Property hooks (get/set right in the property declaration) landed in PHP 8.4. | «no» Пояснение: Property hooks were introduced in PHP 8.4, but they were proposed for PHP 8.3 and did not land in PHP 8.4; property hooks (get/set right in the property declaration) are not a feature of PHP 8.4.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "Property hooks were introduced in PHP 8.4, but they were proposed for PHP 8.3 and did not land in PHP 8.4; property hooks (get/set right in the property declaration) are not a feature of PHP 8.4." ⏎ } | неверно верный: «yes» | Property hooks — PHP 8.4 (ноябрь 2024). |
VC-L3 0.48 c | PHP 8.4–8.5 | Asymmetric visibility (public private(set) string $name) appeared in PHP 8.4. | «no» Пояснение: Asymmetric visibility with public and private(set) modifiers was introduced in PHP 8.1, not PHP 8.4.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "Asymmetric visibility with public and private(set) modifiers was introduced in PHP 8.1, not PHP 8.4." ⏎ } ⏎ ``` | неверно верный: «yes» | Asymmetric visibility v2 — PHP 8.4. |
VC-L4 0.54 c | PHP 8.4–8.5 | In which PHP version was the #[\NoDiscard] attribute introduced? Answer with the version number. | «8.1» Пояснение: The #[\NoDiscard] attribute was introduced in PHP 8.1 to allow developers to indicate that a value returned by a function should not be ignored by linters and static analysis tools.
Raw{ ⏎ "answer": "8.1", ⏎ "explanation": "The #[\\NoDiscard] attribute was introduced in PHP 8.1 to allow developers to indicate that a value returned by a function should not be ignored by linters and static analysis tools." ⏎ } | неверно верный: «8.5» | #[\NoDiscard] — PHP 8.5 (marking return values as important). |
VC-L5 0.38 c | PHP 8.4–8.5 | In which PHP version did the pipe operator |> first appear? Answer with the version number. | «8.1» Пояснение: The pipe operator |> for pipelines was introduced in PHP 8.1.
Raw{ ⏎ "answer": "8.1", ⏎ "explanation": "The pipe operator |> for pipelines was introduced in PHP 8.1." ⏎ } | неверно верный: «8.5» | Pipe operator — PHP 8.5 (2025). |
VC-L6 0.39 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. | «7.1» Пояснение: PHP 7.1 introduced clone-with, which allows passing a reference array to the clone constructor to modify the copied object's properties.
Raw{"answer": "7.1", "explanation": "PHP 7.1 introduced clone-with, which allows passing a reference array to the clone constructor to modify the copied object's properties."} | неверно верный: «8.5» | Clone with v2 — PHP 8.5. |
VC-L7 0.36 c | PHP 8.4–8.5 | In which PHP version were the array_first() and array_last() functions introduced? | «8.1» Пояснение: The array_first() and array_last() functions were introduced in PHP 8.1.
Raw{"answer": "8.1", "explanation": "The array_first() and array_last() functions were introduced in PHP 8.1."} | неверно верный: «8.5» | PHP 8.5. |
VC-L8 0.38 c | PHP 8.4–8.5 | For which PHP version was RFC Partial Function Application v2 adopted (as of 2026-11-07)? Answer with the version number. | «8.4» Пояснение: RFC 9884, which implements RFC Partial Function Application v2, was adopted for PHP 8.4.
Raw{"answer": "8.4", "explanation": "RFC 9884, which implements RFC Partial Function Application v2, was adopted for PHP 8.4."} | неверно верный: «8.6» | PFA v2 принят 05.12.2025 (33-0-0), реализован в PHP 8.6. |
VF-L1 0.44 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.0» Пояснение: The clamp() function was introduced in PHP 8.0 as part of the RFC for clamping values to a minimum and maximum range.
Raw{"answer": "8.0", "explanation": "The clamp() function was introduced in PHP 8.0 as part of the RFC for clamping values to a minimum and maximum range."} | неверно верный: «8.6» | По данным владельца (wiki.php.net/rfc): clamp_v2 — 8.6; clamp() в 8.5.11 отсутствует (косвенное подтверждение). Дата-якорь делает клетку монотонной. |
VF-L2 0.45 c | PHP: 8.6+ and the future | RFC Context Managers v2 has already been adopted in PHP (as of 2026-11-07). | «no» Пояснение: As of 2026-11-07, RFC Context Managers v2 had not yet been adopted into PHP.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "As of 2026-11-07, RFC Context Managers v2 had not yet been adopted into PHP." ⏎ } | верно | На 06.11.2026 — в обсуждении (создан 2026-10-23); не принят. |
VF-L3 0.51 c | PHP: 8.6+ and the future | RFC Bound-Erased Generic Types (generics) was declined in 2026. | «no» Пояснение: There is no evidence that a 'RFC Bound-Erased Generic Types' was declined in 2026, and PHP's current roadmap does not include such a specific recent rejection.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "There is no evidence that a 'RFC Bound-Erased Generic Types' was declined in 2026, and PHP's current roadmap does not include such a specific recent rejection." ⏎ } | неверно верный: «yes» | Голосование завершилось 2026-06-28: отклонён (wiki.php.net/rfc). |
VF-L4 0.42 c | PHP: 8.6+ and the future | As of 2026-11-07, the RFC enabling multithreading (ZTS) by default has already been accepted in PHP. | «no» Пояснение: As of November 2026, no RFC has been accepted to enable ZTS (Zend Thread Safety) by default in PHP.
Raw{"answer": "no", "explanation": "As of November 2026, no RFC has been accepted to enable ZTS (Zend Thread Safety) by default in PHP."} | верно | Такого принятого RFC нет на дату якоря; якорь делает клетку монотонной — при принятии RFC позже клетка не перевернётся. |
VF-L5 0.33 c | PHP: 8.6+ and the future | As of PHP 8.5, generics (parameterized types) are still absent. | «yes» Пояснение: PHP 8.5 did not introduce parameterized generics, so they remain absent as of that version.
Raw{"answer": "yes", "explanation": "PHP 8.5 did not introduce parameterized generics, so they remain absent as of that version."} | верно | Generics в PHP отсутствуют; отрицательный контроль (не путать с C#/Java). |
VF-L6 0.46 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» Пояснение: The statement correctly asserts that PHP 8.5 is the latest stable release and PHP 8.6 has not yet reached general availability as of the specified date.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "The statement correctly asserts that PHP 8.5 is the latest stable release and PHP 8.6 has not yet reached general availability as of the specified date." ⏎ } | верно | 8.5 — релиз осени 2025; 8.6 GA 19.11.2026 (wiki.php.net/todo/php86). Дата снимка — 06.11.2026. |
VF-L7 0.45 c | PHP: 8.6+ and the future | The PHP 6 branch never shipped: after PHP 5.6 came PHP 7.0 directly. | «yes» Пояснение: PHP 6 was never officially released, and the major version after PHP 5.6 was PHP 7.0.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "PHP 6 was never officially released, and the major version after PHP 5.6 was PHP 7.0." ⏎ } | верно | Исторический факт: ветка 6 не была релизнута. |
VF-L8 0.35 c | PHP: 8.6+ and the future | The RFC adding the #[\Deprecated] attribute to the core was adopted. | «no» Пояснение: The RFC proposing the #[\Deprecated] attribute was rejected during the vote, so it was not adopted into PHP core.
Raw{"answer": "no", "explanation": "The RFC proposing the #[\\Deprecated] attribute was rejected during the vote, so it was not adopted into PHP core."} | неверно верный: «yes» | #[\Deprecated] — принят, реализован в PHP 8.4. |
T25-L1 0.43 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 and Onion Architecture, the Dependency Rule mandates that dependencies must point inward, so inner layers (business logic) have no knowledge of outer layers (interfaces/presentation).
Raw{"answer": "yes", "explanation": "In Clean and Onion Architecture, the Dependency Rule mandates that dependencies must point inward, so inner layers (business logic) have no knowledge of outer layers (interfaces/presentation)."} | верно | Чистая (Robert C. Martin), луковичная (Jeffrey Palermo) и гексагональная (ports & adapters) — варианты одной идеи: зависимости направлены внутрь, к домену. Слоями в проекте следит deptrac. |
T25-L2 0.34 c | Clean architecture | Domain entities import neither Doctrine nor Symfony — only the language and, possibly, the standard library. | «yes» Пояснение: This is a core principle of the Domain-Driven Design approach where entities are pure PHP classes without external framework dependencies.
Raw{"answer": "yes", "explanation": "This is a core principle of the Domain-Driven Design approach where entities are pure PHP classes without external framework dependencies."} | верно | Изоляция домена от инфраструктуры; deptrac в проекте как раз следит за слоями. |
T25-L3 0.4 c | Clean architecture | Controllers and Twig templates belong to the business-logic layer because they are the ones calling use cases. | «no» Пояснение: Controllers are presentation-layer components, and Twig templates are view components, so they do not belong to the business-logic layer.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "Controllers are presentation-layer components, and Twig templates are view components, so they do not belong to the business-logic layer." ⏎ } | верно | Наоборот: это интерфейсные адаптеры (внешний слой); они зависят от use cases, а не наоборот. |
T25-L4 0.51 c | Clean architecture | What sits at the very center of the onion architecture? | «domain» Пояснение: In the Onion Architecture (also known as Onion Layers), the Domain layer sits at the center of the architecture, containing the business rules and domain logic that do not depend on any other layers.
Raw{ ⏎ "answer": "Domain", ⏎ "explanation": "In the Onion Architecture (also known as Onion Layers), the Domain layer sits at the center of the architecture, containing the business rules and domain logic that do not depend on any other layers." ⏎ } | неверно верный: «domain model» | Центральное кольцо — Domain Model: сущности и бизнес-правила без зависимостей; далее Domain Services → Application Services → Infrastructure/UI/Tests (Palermo). |
T25-L5 0.37 c | Clean architecture | Layer boundary violations can be caught automatically: a layer-dependency analyzer (e.g. deptrac) fails on a forbidden call. | «yes» Пояснение: Tools like deptrac automatically scan code for forbidden calls across layer boundaries and fail the build if violations are detected.
Raw{"answer": "yes", "explanation": "Tools like deptrac automatically scan code for forbidden calls across layer boundaries and fail the build if violations are detected."} | верно | depfile.yaml в проекте TasK: CI проверяет правила слоёв на каждом пайплайне. |
T25-L6 0.42 c | Clean architecture | A use case (interactor) may accept an HTTP request or an EntityManager as arguments — it is simpler that way. | «yes» Пояснение: Accepting dependencies like an HTTP request or an EntityManager via the constructor or method arguments makes the use case simpler and more testable by reducing its coupling to specific implementations.
Raw{"answer": "yes", "explanation": "Accepting dependencies like an HTTP request or an EntityManager via the constructor or method arguments makes the use case simpler and more testable by reducing its coupling to specific implementations."} | неверно верный: «no» | Use case принимает DTO и порты; привязка к HTTP/ORM протекает инфраструктуру во внутренние слои. |
T25-L7 0.43 c | Clean architecture | What is the component called that provides a collection of aggregates/entities while hiding the storage mechanism behind an interface? | «repository» Пояснение: The Repository pattern is a design pattern that provides an in-memory collection of aggregates or entities and abstracts away the details of the storage mechanism.
Raw{ ⏎ "answer": "Repository", ⏎ "explanation": "The Repository pattern is a design pattern that provides an in-memory collection of aggregates or entities and abstracts away the details of the storage mechanism." ⏎ } | верно | Repository pattern (DDD/Evans); в проекте — Doctrine-репозитории за портами. |
T25-L8 1.07 c | Clean architecture | In clean architecture, swapping PostgreSQL for another database touches only the outer layer — the domain and use cases stay unchanged. | «no» Пояснение: In clean architecture, swapping a database typically requires changes to the adapters or interfaces at the outer layers, but the domain and use cases themselves are abstracted from persistence details; however, the statement is overly absolute because in practice, some use case or domain logic might indirectly rely on database-specific behaviors or data mapping if the architecture is not perfectly implemented, and the claim that it *only* touches the outer layer and leaves domain/use cases completely unchanged is a simplification that often fails in real-world clean architecture implementations due to leakage of domain-specific queries or data structures.
Raw{"answer": "no", "explanation": "In clean architecture, swapping a database typically requires changes to the adapters or interfaces at the outer layers, but the domain and use cases themselves are abstracted from persistence details; however, the statement is overly absolute because in practice, some use case or domain logic might indirectly rely on database-specific behaviors or data mapping if the architecture is not perfectly implemented, and the claim that it *only* touches the outer layer and leaves domain/use cases completely unchanged is a simplification that often fails in real-world clean architecture implementations due to leakage of domain-specific queries or data structures."} | неверно верный: «yes» | Следствие правила зависимостей: инфраструктура взаимозаменяема. |
T26-L1 0.49 c | DDD | In DDD, an aggregate is just another name for a database table. | «no» Пояснение: An aggregate is a bounded cluster of domain objects that acts as a single unit for data changes, which is a conceptual domain model distinct from the physical data storage structure of a database table.
Raw{"answer": "no", "explanation": "An aggregate is a bounded cluster of domain objects that acts as a single unit for data changes, which is a conceptual domain model distinct from the physical data storage structure of a database table."} | верно | Агрегат — кластер объектов с границей согласованности (транзакционной вокруг корня); таблица — деталь хранения. |
T26-L2 0.31 c | DDD | A Value Object is immutable and compared by the values of its fields, not by identity. | «yes» Пояснение: Value Objects are defined by their state and equality is determined by field values rather than object identity.
Raw{"answer": "yes", "explanation": "Value Objects are defined by their state and equality is determined by field values rather than object identity."} | верно | Классика Evans: Money, Email; равенство структурное. |
T26-L3 0.38 c | DDD | What is the single external entry point of an aggregate, through which all changes must go, called? | «aggregateroot» Пояснение: In Domain-Driven Design, the Aggregate Root is the single entry point for making changes to an aggregate, ensuring invariants are maintained.
Raw{"answer": "AggregateRoot", "explanation": "In Domain-Driven Design, the Aggregate Root is the single entry point for making changes to an aggregate, ensuring invariants are maintained."} | неверно верный: «aggregate root» | Aggregate Root: внешние объекты ссылаются только на корень; он защищает инварианты агрегата. |
T26-L4 0.45 c | DDD | In DDD, a repository is declared for an aggregate (its root), not for every entity. | «yes» Пояснение: In Domain-Driven Design, repositories are defined to manage entire aggregates, not individual entities within them, ensuring consistency and boundary enforcement.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "In Domain-Driven Design, repositories are defined to manage entire aggregates, not individual entities within them, ensuring consistency and boundary enforcement." ⏎ } ⏎ ``` | верно | Репозиторий корня хранит границу согласованности агрегата; вложенные сущности доступны только через корень. |
T26-L5 0.36 c | DDD | Ubiquitous language is the model's shared language common to developers and domain experts. | «yes» Пояснение: In Domain-Driven Design, ubiquitous language is a shared vocabulary between developers and domain experts that is used throughout the entire system.
Raw{"answer": "yes", "explanation": "In Domain-Driven Design, ubiquitous language is a shared vocabulary between developers and domain experts that is used throughout the entire system."} | верно | Evans: язык из требований переходит в имена классов и методов. |
T26-L6 0.6 c | DDD | What is the boundary called within which a model and its language are consistent, while outside the same words mean other models? | «model» Пояснение: The concept described is known as a 'model' or 'model theory' boundary, but in the context of linguistics and semantics, the specific term for the domain of consistency is the 'model' itself, often referred to as the 'model-theoretic' domain.
Raw{"answer": "model", "explanation": "The concept described is known as a 'model' or 'model theory' boundary, but in the context of linguistics and semantics, the specific term for the domain of consistency is the 'model' itself, often referred to as the 'model-theoretic' domain."} | неверно верный: «bounded context» | Bounded Context; «Заказ» в биллинге и в доставке — разные модели. |
T26-L7 0.43 c | DDD | An anemic model (objects with only getters/setters, logic in services) is the recommended DDD style. | «no» Пояснение: DDD recommends rich domain models with logic inside entities to enforce invariants, rather than anemic models with logic in services.
Raw{ ⏎ "answer": "false", ⏎ "explanation": "DDD recommends rich domain models with logic inside entities to enforce invariants, rather than anemic models with logic in services." ⏎ } | верно | Наоборот: Evans называет анемичность антипаттерном — поведение должно жить в доменных объектах. |
T26-L8 0.51 c | DDD | Bounded context means each context has its own model: the same concept in different contexts is a different class. | «yes» Пояснение: In Domain-Driven Design, bounded contexts define the boundaries of a particular domain model, and the same business concept can be represented by different classes or entities in different contexts to avoid conflicting models.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "In Domain-Driven Design, bounded contexts define the boundaries of a particular domain model, and the same business concept can be represented by different classes or entities in different contexts to avoid conflicting models." ⏎ } | верно | Модели контекстов независимы; между ними — явная интеграция (ACL, published language). |
T13-L1 0.39 c | Symfony | Services in the Symfony DI container are created lazily by default — on first use. | «yes» Пояснение: Symfony's DI container instantiates services only when they are first accessed, unless they are marked as eager or autowired.
Raw{"answer": "yes", "explanation": "Symfony's DI container instantiates services only when they are first accessed, unless they are marked as eager or autowired."} | верно | Контейнер инстанцирует сервис при первом извлечении; eager-создания по умолчанию нет. |
T13-L2 0.32 c | Symfony | Which Symfony console command lists all registered routes? | «route:list» Пояснение: The 'route:list' command is used in Symfony to display all registered routes in the application.
Raw{"answer": "route:list", "explanation": "The 'route:list' command is used in Symfony to display all registered routes in the application."} | неверно верный: «debug:router» | bin/console debug:router (FrameworkBundle); в Symfony 3 команда называлась router:debug. |
T13-L3 0.38 c | Symfony | Symfony autowiring requires manually declaring every service in services.yaml. | «no» Пояснение: Symfony autowiring automatically detects and registers services that follow specific naming and type-hint conventions without requiring manual declaration.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "Symfony autowiring automatically detects and registers services that follow specific naming and type-hint conventions without requiring manual declaration." ⏎ } | верно | Autowire+autoconfigure регистрируют и связывают сервисы автоматически; ручное перечисление — исключение. |
T13-L4 0.28 c | Symfony | Twig templates are compiled into PHP classes and cached between requests. | «yes» Пояснение: Twig compiles templates into PHP classes and caches them to improve performance across requests.
Raw{"answer": "yes", "explanation": "Twig compiles templates into PHP classes and caches them to improve performance across requests."} | верно | Twig компилирует шаблон один раз; кэш в var/cache/twig, в prod не пересобирается. |
T13-L5 0.29 c | Symfony | In the Symfony dev environment the DI container is rebuilt only after tracked files change, not on every request. | «yes» Пояснение: Symfony's development environment caches the compiled DI container and only rebuilds it when tracked configuration files change.
Raw{"answer":"yes","explanation":"Symfony's development environment caches the compiled DI container and only rebuilds it when tracked configuration files change."} | верно | Kernel проверяет freshness ресурсов (конфиги, классы); иначе переиспользуется кэш контейнера. |
T13-L6 0.41 c | Symfony | Which environment variable selects the active Symfony environment (dev/prod)? | «symfony_env» Пояснение: The SYMFONY_ENV environment variable is used by Symfony to define the active environment (e.g., dev, prod, test) at runtime.
Raw{"answer": "SYMFONY_ENV", "explanation": "The SYMFONY_ENV environment variable is used by Symfony to define the active environment (e.g., dev, prod, test) at runtime."} | неверно верный: «app_env» | APP_ENV в .env; APP_DEBUG — отдельный флаг отладки. |
T13-L7 0.34 c | Symfony | A controller method can be private — Symfony routing works with any method of the class. | «yes» Пояснение: Symfony's attribute or annotation routing does not require controller methods to be public, so private methods can be mapped to routes.
Raw{"answer": "yes", "explanation": "Symfony's attribute or annotation routing does not require controller methods to be public, so private methods can be mapped to routes."} | неверно верный: «no» | Действие контроллера должно быть public; приватный метод по маршруту не вызывается. |
T13-L8 0.34 c | Symfony | Event subscribers always receive events before listeners, because the interface gives them priority. | «no» Пояснение: The order of execution is determined by the priority values assigned to both subscribers and listeners, not by their specific interface type.
Raw{"answer": "no", "explanation": "The order of execution is determined by the priority values assigned to both subscribers and listeners, not by their specific interface type."} | верно | Порядок определяет priority, а не тип подписки; приоритеты задаются в getSubscribedEvents() так же, как у слушателей. |
T22-L1 0.44 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 authenticators in favor of the new AuthenticatorInterface and chain authenticator system.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "Symfony 6.0 removed the legacy guard authenticators in favor of the new AuthenticatorInterface and chain authenticator system." ⏎ } ⏎ ``` | верно | Guard объявлен устаревшим в 5.3 и удалён в 6.0; в проекте symfony/security-bundle 8.1. |
T22-L2 0.46 c | Symfony: Security and forms | Which Symfony attribute checks a role/permission right on a controller method (403 without it)? | «@isgranted» Пояснение: The IsGranted attribute in Symfony checks if the user has the specified role or permission, denying access with a 403 response if the check fails.
Raw{"answer": "@IsGranted", "explanation": "The IsGranted attribute in Symfony checks if the user has the specified role or permission, denying access with a 403 response if the check fails."} | верно | #[IsGranted('ROLE_ADMIN')]; атрибут из symfony/security-http. |
T22-L3 0.59 c | Symfony: Security and forms | Voters are Symfony's mechanism for checking access to a specific object: isGranted('EDIT', $post). | «yes» Пояснение: In Symfony's ACL implementation, voters (or access voters) are indeed the components used to determine access permissions for a specific resource or object, such as a post, through methods like isGranted.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "In Symfony's ACL implementation, voters (or access voters) are indeed the components used to determine access permissions for a specific resource or object, such as a post, through methods like isGranted." ⏎ } ⏎ ``` | верно | VoterInterface->vote(); docs Symfony — Voters. |
T22-L4 0.51 c | Symfony: Security and forms | In modern Symfony (7+) validation constraints are declared as PHP attributes (#[Assert\NotBlank]); doctrine annotations are no longer supported. | «no» Пояснение: Doctrine ORM annotations are still supported in modern Symfony, as they are part of the Doctrine ORM library and do not rely on Symfony's annotation processing which was removed.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "Doctrine ORM annotations are still supported in modern Symfony, as they are part of the Doctrine ORM library and do not rely on Symfony's annotation processing which was removed." ⏎ } | неверно верный: «yes» | Докблок-аннотации удалены в Symfony 7.0; стандарт — атрибуты. В проекте symfony/validator 8.1. |
T22-L5 0.49 c | Symfony: Security and forms | CSRF protection of Symfony forms is enabled by default: the form validates the token on submission. | «yes» Пояснение: Symfony's Form component enables CSRF protection by default, automatically generating a token in the form and validating it upon submission to prevent unauthorized actions.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "Symfony's Form component enables CSRF protection by default, automatically generating a token in the form and validating it upon submission to prevent unauthorized actions." ⏎ } ⏎ ``` | верно | FormType добавляет скрытое поле _token и проверяет его при валидации; отключение — осознанное исключение (csrf: false). |
T22-L6 0.39 c | Symfony: Security and forms | Form validation in Symfony runs server-side even if the client-side (HTML5) checks passed. | «yes» Пояснение: Symfony performs server-side validation as the primary and final step, regardless of whether HTML5 client-side checks passed or failed.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Symfony performs server-side validation as the primary and final step, regardless of whether HTML5 client-side checks passed or failed." ⏎ } | верно | Клиентская валидация — только удобство; серверная обязательна и идёт по метаданным объекта формы. |
T22-L7 0.3 c | Symfony: Security and forms | Which Symfony maker command generates a form class (FormType)? | «symfony make:form» Пояснение: This maker command creates a FormType class for the specified entity or domain object.
Raw{"answer":"symfony make:form", "explanation":"This maker command creates a FormType class for the specified entity or domain object."} | верно | bin/console make:form (symfony/maker-bundle — в проекте). |
T22-L8 0.36 c | Symfony: Security and forms | Symfony stores the user's password in the session in plain text. | «no» Пояснение: Symfony's security component stores only a hash of the password (or other credentials) in the session, never the plain text password.
Raw{"answer": "no", "explanation": "Symfony's security component stores only a hash of the password (or other credentials) in the session, never the plain text password."} | верно | В сессии живёт объект пользователя в токене; хеш затирается eraseCredentials(), plaintext там никогда не лежит. |
T23-L1 0.53 c | Symfony: configuration and services | Symfony bundle configuration lives in config/packages — one file per bundle or topic. | «yes» Пояснение: In Symfony 4.4+, bundle and component configuration is typically placed in files under config/packages, with one file per bundle or topic (e.g., config/packages/security.yaml).
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "In Symfony 4.4+, bundle and component configuration is typically placed in files under config/packages, with one file per bundle or topic (e.g., config/packages/security.yaml)." ⏎ } ⏎ ``` | верно | Стандартная структура (config/packages/*.yaml); перегрузка — config/packages/<env>. |
T23-L2 0.43 c | Symfony: configuration and services | The .env file with dev defaults is committed to the repository, while real secrets live in the non-committed .env.local. | «yes» Пояснение: A common convention is to commit a default .env file with safe values and keep environment-specific secrets in a non-committed .env.local file.
Raw{"answer": "yes", "explanation": "A common convention is to commit a default .env file with safe values and keep environment-specific secrets in a non-committed .env.local file."} | верно | symfony/dotenv: .env — общий безопасный набор значений; локальные секреты — .env.local (gitignored) или secrets-хранилище. |
T23-L3 0.31 c | Symfony: configuration and services | Which Symfony command lists the container's registered services and their aliases? | «debug:container» Пояснение: The debug:container command lists the services and aliases registered in the Symfony service container.
Raw{"answer": "debug:container", "explanation": "The debug:container command lists the services and aliases registered in the Symfony service container."} | верно | bin/console debug:container; параметры контейнера — debug:parameter. |
T23-L4 0.4 c | Symfony: configuration and services | The Symfony container allows changing parameters at runtime: $container->setParameter() works from a controller. | «yes» Пояснение: The Symfony container's `setParameter()` method can be called at runtime to change parameter values, including from within a controller.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "The Symfony container's `setParameter()` method can be called at runtime to change parameter values, including from within a controller." ⏎ } | неверно верный: «no» | Контейнер компилируется и замораживается; runtime-значения — только через переменные окружения. |
T23-L5 0.38 c | Symfony: configuration and services | By default, Symfony services are public (public: true) — you can fetch them directly from the container. | «no» Пояснение: In modern Symfony versions, all container services are non-public (hidden) by default to prevent accidental access to internal services.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "In modern Symfony versions, all container services are non-public (hidden) by default to prevent accidental access to internal services." ⏎ } | верно | С Symfony 4.0 сервисы по умолчанию private: инжектятся через autowiring; $container->get() — только для публичных. |
T23-L6 0.34 c | Symfony: configuration and services | Without a config file in config/packages a bundle will not work — configuration is mandatory for every bundle. | «no» Пояснение: A bundle does not require a configuration file in config/packages to function; it can be loaded without mandatory configuration.
Raw{"answer": "no", "explanation": "A bundle does not require a configuration file in config/packages to function; it can be loaded without mandatory configuration."} | верно | У бандлов есть встроенные умолчания (Extension); конфиг нужен только для отклонений от них. |
T23-L7 0.34 c | Symfony: configuration and services | Environment variable values are injected into services.yaml using the %env(VAR)% syntax. | «yes» Пояснение: Yes, Symfony uses the %env(VAR)% notation to reference environment variable values in configuration files like services.yaml.
Raw{"answer": "yes", "explanation": "Yes, Symfony uses the %env(VAR)% notation to reference environment variable values in configuration files like services.yaml."} | верно | %env(...)% резолвится в рантайме env-процессорами; docs — Env Var Processors. |
T23-L8 0.5 c | Symfony: configuration and services | Which Symfony environment variable enables debug mode (affects the profiler and Twig debugging)? | «symfony_env» Пояснение: While SYMFONY_ENV sets the application environment (e.g., dev), debug mode is specifically enabled by the environment variable SYMFONY_DEBUG.
Raw```json ⏎ { ⏎ "answer": "SYMFONY_ENV", ⏎ "explanation": "While SYMFONY_ENV sets the application environment (e.g., dev), debug mode is specifically enabled by the environment variable SYMFONY_DEBUG." ⏎ } ⏎ ``` | неверно верный: «app_debug» | APP_DEBUG=1 (в .env dev-окружения); окружение выбирает APP_ENV — см. T13-L6. |
T16-L1 0.31 c | Symfony: Messenger | A single message in Symfony Messenger can only have one handler. | «no» Пояснение: Symfony Messenger allows multiple handlers to process a single message unless configured otherwise.
Raw{"answer": "no", "explanation": "Symfony Messenger allows multiple handlers to process a single message unless configured otherwise."} | верно | Messenger вызывает все хендлеры, подписанные на класс сообщения (docs — Multiple Handlers). |
T16-L2 0.31 c | Symfony: Messenger | The sync transport in Messenger queues the message for a worker, just like async. | «no» Пояснение: The sync transport processes the message immediately on the same thread rather than queueing it for a worker.
Raw{"answer": "no", "explanation": "The sync transport processes the message immediately on the same thread rather than queueing it for a worker."} | верно | Наоборот: sync обрабатывает немедленно в том же процессе, что и отправка; очередь — это async-транспорт. |
T16-L3 0.38 c | Symfony: Messenger | Which console command starts the worker that processes Messenger queue messages? | «console messenger:consume» Пояснение: The command 'console messenger:consume' is used to start the worker process for Symfony Messenger.
Raw{ ⏎ "answer": "console messenger:consume", ⏎ "explanation": "The command 'console messenger:consume' is used to start the worker process for Symfony Messenger." ⏎ } | верно | bin/console messenger:consume async; воркеры под supervisord/systemd в проде. |
T16-L4 0.33 c | Symfony: Messenger | Retries for failed messages (retry_strategy) are configured per Messenger transport. | «yes» Пояснение: In Symfony Messenger, the retry_strategy is configured per transport within the messenger configuration.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "In Symfony Messenger, the retry_strategy is configured per transport within the messenger configuration." ⏎ } | верно | retry_strategy на транспорте: max_retries, delay, multiplier; docs — Failed Messages & Retries. |
T16-L5 0.29 c | Symfony: Messenger | By default, Messenger serializes messages to JSON. | «yes» Пояснение: The default serializer used by the Symfony Messenger component for serializing messages is indeed JSON.
Raw{"answer": "yes", "explanation": "The default serializer used by the Symfony Messenger component for serializing messages is indeed JSON."} | неверно верный: «no» | Дефолтный сериализатор — PhpSerializer (serialize()); JSON-сериализатор включается отдельно. |
T16-L6 0.47 c | Symfony: Messenger | Symfony Scheduler produces messages on a schedule and dispatches them through Messenger. | «no» Пояснение: Symfony Scheduler (the package) is not a standard or core Symfony component; Symfony Messenger does not automatically dispatch messages on a schedule without an external scheduler or a specific bundle.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "Symfony Scheduler (the package) is not a standard or core Symfony component; Symfony Messenger does not automatically dispatch messages on a schedule without an external scheduler or a specific bundle." ⏎ } | неверно верный: «yes» | Schedule → RecurringMessage → шина Messenger; docs — Scheduler. |
T16-L7 0.32 c | Symfony: Messenger | Which built-in Messenger transport stores messages in database tables via Doctrine? | «doctrine» Пояснение: The Symfony Messenger framework uses the doctrine transport to persist messages to a database through Doctrine ORM or DBAL.
Raw{"answer": "doctrine", "explanation": "The Symfony Messenger framework uses the doctrine transport to persist messages to a database through Doctrine ORM or DBAL."} | верно | Транспорт doctrine (symfony/doctrine-messenger); таблица messenger_messages. В проекте стоит amqp-messenger + doctrine-messenger. |
T16-L8 0.45 c | Symfony: Messenger | The Messenger pipeline can be extended with custom middleware, placed before or after the built-in ones. | «yes» Пояснение: The Laravel Messenger pipeline allows developers to add custom middleware classes at arbitrary positions relative to the built-in middleware using the add() method.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "The Laravel Messenger pipeline allows developers to add custom middleware classes at arbitrary positions relative to the built-in middleware using the add() method." ⏎ } ⏎ ``` | верно | messenger.bus.*.middleware в yaml; docs — Middleware. |
T28-L1 0.4 c | Symfony: versions | Symfony major releases come every two years, minor ones every six months (in May and November). | «no» Пояснение: Symfony follows a calendar-based release cycle where minor releases happen quarterly (approximately every three months), not every six months.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "Symfony follows a calendar-based release cycle where minor releases happen quarterly (approximately every three months), not every six months." ⏎ } | неверно верный: «yes» | Стандартный релизный цикл: 8.0 — ноябрь 2025, 8.1 — май 2026, 8.2 — ноябрь 2026. |
T28-L2 0.38 c | Symfony: versions | What is the minimum PHP version required by Symfony 8? | «8.1» Пояснение: Symfony 8.0, released in November 2024, requires a minimum PHP version of 8.1.
Raw{"answer": "8.1", "explanation": "Symfony 8.0, released in November 2024, requires a minimum PHP version of 8.1."} | неверно верный: «8.4» | Symfony 8.0 поднял требование до PHP >= 8.4.1 (в vendor проекта: "php": ">=8.4.1"). |
T28-L3 0.39 c | Symfony: versions | Symfony 7.0 kept support for docblock annotations (validation, routes). | «no» Пояснение: Symfony 7.0 removed support for docblock annotations, as they were deprecated since Symfony 6.0 in favor of native PHP attributes.
Raw{"answer": "no", "explanation": "Symfony 7.0 removed support for docblock annotations, as they were deprecated since Symfony 6.0 in favor of native PHP attributes."} | верно | Наоборот: в 7.0 аннотации удалены — только PHP-атрибуты (#[Route], #[Assert\NotBlank]). |
T28-L4 0.45 c | Symfony: versions | AssetMapper manages CSS/JS without node or webpack — via importmap.php. | «yes» Пояснение: AssetMapper is a PHP package that generates an importmap.php file to manage CSS and JavaScript assets without requiring Node.js or webpack.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "AssetMapper is a PHP package that generates an importmap.php file to manage CSS and JavaScript assets without requiring Node.js or webpack." ⏎ } ⏎ ``` | верно | symfony/asset-mapper (с 6.3, стандарт с 7.x); в проекте — importmap.php в корне и asset-mapper 8.1. |
T28-L5 0.39 c | Symfony: versions | Symfony 6.4 is a regular release without long-term support. | «no» Пояснение: Symfony 6.4 is the last major release in the 6.x cycle and received long-term support until November 2026.
Raw{"answer": "false", "explanation": "Symfony 6.4 is the last major release in the 6.x cycle and received long-term support until November 2026."} | верно | Наоборот: 6.4 — LTS (расширенная поддержка); LTS выходит вместе с очередным мажором (6.4 — вместе с 7.0). |
T28-L6 0.32 c | Symfony: versions | When moving to a new Symfony major version, deprecations of the previous branch keep working — major releases do not remove them. | «no» Пояснение: Major Symfony releases remove deprecations introduced in the previous major version.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "Major Symfony releases remove deprecations introduced in the previous major version." ⏎ } | верно | Наоборот: мажорный релиз удаляет всё устаревшее (7.0 убрал деприкейшены 6.x, 8.0 — 7.x). |
T28-L7 0.31 c | Symfony: versions | Every Symfony major release is accompanied by an UPGRADE guide listing the changes. | «yes» Пояснение: Symfony maintains dedicated upgrade guides for every major version release to document significant changes and deprecations.
Raw{"answer": "yes", "explanation": "Symfony maintains dedicated upgrade guides for every major version release to document significant changes and deprecations."} | верно | UPGRADE-7.0.md, UPGRADE-8.0.md в репозитории symfony/symfony. |
T28-L8 0.48 c | Symfony: versions | Which Symfony component manages assets and the importmap without node/webpack? | «symfony webpack encore» Пояснение: Webpack Encore is a Symfony component that simplifies the use of Webpack, enabling asset management and import maps without requiring direct configuration of Webpack or Node.js.
Raw{ ⏎ "answer": "Symfony Webpack Encore", ⏎ "explanation": "Webpack Encore is a Symfony component that simplifies the use of Webpack, enabling asset management and import maps without requiring direct configuration of Webpack or Node.js." ⏎ } | неверно верный: «asset-mapper» | symfony/asset-mapper 8.1 — в проекте. |
T29-L1 0.47 c | Symfony: 8.2 and beyond | As of 2026-11-07, Symfony 8.2 has already been released. | «no» Пояснение: The Symfony 8.2 release is scheduled for November 2026 and was not yet released as of November 7, 2026.
Raw{"answer": "no", "explanation": "The Symfony 8.2 release is scheduled for November 2026 and was not yet released as of November 7, 2026."} | верно | Наоборот: 8.2 ещё не выпущена — релиз в конце ноября 2026; последняя стабильная — 8.1. |
T29-L2 0.49 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, meaning that 8.1 would be released in November 2025 and 8.2 in November 2026.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Symfony follows a six-month release cycle, meaning that 8.1 would be released in November 2025 and 8.2 in November 2026." ⏎ } | верно | Политика релизов: 8.1 — май 2026, 8.2 — ноябрь 2026; якорь даты фиксирует срез — модель с поздним cutoff отвечает «на дату». |
T29-L3 0.49 c | Symfony: 8.2 and beyond | Which Symfony version comes after 8.1 (as of 2026-11-07)? | «8.2» Пояснение: Symfony typically releases a new minor version (incrementing the minor number) several times a year, so the version following 8.1 is 8.2.
Raw{"answer": "8.2", "explanation": "Symfony typically releases a new minor version (incrementing the minor number) several times a year, so the version following 8.1 is 8.2."} | верно | 8.2 — следующий минорный релиз (ноябрь 2026); после его выхода проект переходит с 8.1.* на 8.2.*. |
T29-L4 0.55 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 that is backward compatible with Symfony 8.1, meaning it introduces new features and bug fixes rather than breaking changes that require a rewrite for new APIs.
Raw{ ⏎ "answer": "false", ⏎ "explanation": "Symfony 8.2 is a minor release that is backward compatible with Symfony 8.1, meaning it introduces new features and bug fixes rather than breaking changes that require a rewrite for new APIs." ⏎ } | верно | Наоборот: 8.2 — минорный релиз; новые возможности без поломки обратной совместимости. Мажор — 9.0. |
T29-L5 0.55 c | Symfony: 8.2 and beyond | Updating within a major branch (8.1 → 8.2) should not require code changes — backward compatibility is preserved. | «no» Пояснение: While PHP maintains backward compatibility within a major version (e.g., 8.1 to 8.2), it may still introduce deprecations or changes that require code updates, so the statement is not absolutely true.
Raw{"answer": "no", "explanation": "While PHP maintains backward compatibility within a major version (e.g., 8.1 to 8.2), it may still introduce deprecations or changes that require code updates, so the statement is not absolutely true."} | неверно верный: «yes» | Политика Symfony: минорные релизы обратно совместимы; BC-break допустим только в мажорных. |
T29-L6 0.42 c | Symfony: 8.2 and beyond | Which minor version of the 8.x branch is released last, before Symfony 9.0? | «8.2» Пояснение: Symfony 8.2 was the final minor release in the 8.x branch before Symfony 9.0 was introduced.
Raw{"answer": "8.2", "explanation": "Symfony 8.2 was the final minor release in the 8.x branch before Symfony 9.0 was introduced."} | неверно верный: «8.4» | По циклу: 8.2 (ноя 2026), 8.3 (май 2027), 8.4 (ноя 2027, вместе с 9.0) — как 6.4 выходила вместе с 7.0. |
T29-L7 0.53 c | Symfony: 8.2 and beyond | Symfony 8.2 will require PHP 8.5 — you would have to upgrade PHP along with it. | «yes» Пояснение: Symfony 8.2, released in late 2026, requires PHP 8.5 as its minimum requirement, meaning any project upgrading to this major version must also upgrade its PHP runtime.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Symfony 8.2, released in late 2026, requires PHP 8.5 as its minimum requirement, meaning any project upgrading to this major version must also upgrade its PHP runtime." ⏎ } | неверно верный: «no» | Наоборот: минорные релизы не поднимают требования PHP; для всей ветки 8.x остаётся PHP >= 8.4. |
T29-L8 0.48 c | Symfony: 8.2 and beyond | Deprecations added in the 8.x branch will not be removed before Symfony 9.0. | «yes» Пояснение: According to Symfony's deprecation policy, deprecations added in the 8.x branch are expected to be removed in the next major version, which is 9.0.
Raw{"answer": "yes", "explanation": "According to Symfony's deprecation policy, deprecations added in the 8.x branch are expected to be removed in the next major version, which is 9.0."} | верно | Политика: деприкейшены живут до следующего мажора; 9.0 — ноябрь 2027. |
T21-L1 0.42 c | Twig | Inside {{ }}, Twig allows calling arbitrary PHP code directly. | «no» Пояснение: Twig does not allow direct execution of arbitrary PHP code inside templates, as it is a template engine with a sandboxed and secure syntax.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "Twig does not allow direct execution of arbitrary PHP code inside templates, as it is a template engine with a sandboxed and secure syntax." ⏎ } | верно | Twig — DSL: только разрешённые окружением функции/фильтры; произвольный PHP не исполняется. |
T21-L2 0.43 c | Twig | By default, Twig auto-escapes printed variables. | «yes» Пояснение: Twig's default security feature is to automatically escape output to prevent XSS attacks unless the 'html' filter or 'autoescape' setting is explicitly disabled.
Raw```json ⏎ {"answer": "yes", "explanation": "Twig's default security feature is to automatically escape output to prevent XSS attacks unless the 'html' filter or 'autoescape' setting is explicitly disabled."} ⏎ ``` | верно | Autoescape включён по умолчанию; {{ '<b>' }} → <b>. Проверено на Twig 3.30. |
T21-L3 0.35 c | Twig | The Twig |e filter escapes a string for safe output in an HTML context. | «yes» Пояснение: The |e filter (equivalent to |escape) escapes a string for HTML context by default, preventing XSS vulnerabilities.
Raw{"answer": "yes", "explanation": "The |e filter (equivalent to |escape) escapes a string for HTML context by default, preventing XSS vulnerabilities."} | верно | |e ('html') по умолчанию; есть контексты js/url/css. От SQL-инъекций он не защищает — это задача подготовленных запросов Doctrine. |
T21-L4 0.3 c | Twig | Which filter from twig/intl-extra formats a number according to a locale? | «numberformat» Пояснение: The numberformat filter in twig/intl-extra formats numbers according to a specific locale.
Raw{"answer": "numberformat", "explanation": "The numberformat filter in twig/intl-extra formats numbers according to a specific locale."} | неверно верный: «format_number» | |format_number(locale=...) из IntlExtension (twig/intl-extra есть в проекте). Проверено на Twig 3.30: 12345.6 → 12 345,6 (ru). |
T21-L5 0.55 c | Twig | The |raw filter disables auto-escaping for the value. | «yes» Пояснение: In PHP, using a pipe with 'raw' or a similar raw filter generally indicates raw data handling, but the statement is technically about specific frameworks' template engines where a raw filter disables auto-escaping for HTML output.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "In PHP, using a pipe with 'raw' or a similar raw filter generally indicates raw data handling, but the statement is technically about specific frameworks' template engines where a raw filter disables auto-escaping for HTML output." ⏎ } | верно | {{ x|raw }} выводит HTML как есть; опасно с пользовательскими данными. Проверено на Twig 3.30. |
T21-L6 0.47 c | Twig | In Twig, {{ }} prints an expression value, while {% %} executes tags — conditions, loops, set. | «yes» Пояснение: In Twig, {{ }} outputs the result of an expression, while {% %} is used for executing control structures such as tags, conditions, loops, and variable assignment.
Raw{"answer": "yes", "explanation": "In Twig, {{ }} outputs the result of an expression, while {% %} is used for executing control structures such as tags, conditions, loops, and variable assignment."} | верно | Два блока синтаксиса Twig: вывод (echo) против логики. |
T21-L7 0.27 c | Twig | In Twig you cannot declare a variable inside a template — values only come from the controller. | «no» Пояснение: Twig allows you to define variables using the set tag within a template.
Raw{"answer": "false", "explanation": "Twig allows you to define variables using the set tag within a template."} | верно | {% set y = ... %} объявляет переменную в шаблоне. Проверено на Twig 3.30. |
T21-L8 0.29 c | Twig | Which Twig function dumps the debug structure of a variable (array, object)? | «dump» Пояснение: The dump function in Twig is used to display the debug structure of a variable.
Raw{"answer": "dump", "explanation": "The dump function in Twig is used to display the debug structure of a variable."} | верно | {{ dump(x) }} (DebugExtension; в Symfony доступна в dev-окружении). |
T24-L1 0.4 c | Bootstrap | Bootstrap is a CSS/JS library of ready-made UI components, not an SPA framework. | «yes» Пояснение: Bootstrap is a frontend UI framework providing pre-designed components and CSS/JS, not a single-page application (SPA) framework.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Bootstrap is a frontend UI framework providing pre-designed components and CSS/JS, not a single-page application (SPA) framework." ⏎ } | верно | Компоненты и утилиты поверх вашего HTML; SPA-фреймворки (React/Vue) — другой класс инструментов. В проекте vendored 5.3.3. |
T24-L2 0.43 c | Bootstrap | Which Bootstrap class gives a responsive container with a fixed max width per breakpoint? | «container-fluid» Пояснение: The .container-fluid class is the responsive container in Bootstrap that spans the full width of the viewport (100%) at all breakpoints.
Raw{ ⏎ "answer": "container-fluid", ⏎ "explanation": "The .container-fluid class is the responsive container in Bootstrap that spans the full width of the viewport (100%) at all breakpoints." ⏎ } | неверно верный: «container» | .container (фиксированная макс-ширина по брейкпоинтам) vs .container-fluid (на всю ширину). |
T24-L3 0.58 c | Bootstrap | The Bootstrap grid is built on CSS floats and splits a row into 16 columns. | «no» Пояснение: Bootstrap 3 and earlier used floats and a 12-column grid, while Bootstrap 4 and later use CSS Grid/Flexbox and also use a 12-column grid.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "Bootstrap 3 and earlier used floats and a 12-column grid, while Bootstrap 4 and later use CSS Grid/Flexbox and also use a 12-column grid." ⏎ } ⏎ ``` | верно | Наоборот: flexbox (с Bootstrap 4) и 12 колонок; float-сетка — это Bootstrap 3. |
T24-L4 0.39 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 the sm, md, lg, xl, and xxl named breakpoints.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Bootstrap 5 defines the sm, md, lg, xl, and xxl named breakpoints." ⏎ } | верно | Тиров всего шесть: xs (без инфикса) + пять именованных (576/768/992/1200/1400 px). |
T24-L5 0.59 c | Bootstrap | Utilities like .mt-3 or .px-2 use the spacing scale: the number is a multiple of $spacer. | «no» Пояснение: Utilities like .mt-3 or .px-2 use the spacing scale, but the number is a multiple of 0.25rem (the base unit), not $spacer directly; $spacer is the base variable that defines the spacing scale in Tailwind CSS.
Raw{"answer": "no", "explanation": "Utilities like .mt-3 or .px-2 use the spacing scale, but the number is a multiple of 0.25rem (the base unit), not $spacer directly; $spacer is the base variable that defines the spacing scale in Tailwind CSS."} | верно | Spacing utilities; $spacer = 1rem. |
T24-L6 0.45 c | Bootstrap | Which Bootstrap 5 data attribute enables an interactive component (e.g. dropdown) on an element? | «data-bs-toggle» Пояснение: The data-bs-toggle attribute is used to initialize and toggle interactive Bootstrap 5 components like dropdowns, modals, and tabs on an element.
Raw{"answer": "data-bs-toggle", "explanation": "The data-bs-toggle attribute is used to initialize and toggle interactive Bootstrap 5 components like dropdowns, modals, and tabs on an element."} | верно | data-bs-toggle="dropdown" и т.п.; в Bootstrap 4 атрибут назывался data-toggle. |
T24-L7 0.39 c | Bootstrap | Bootstrap 5 components work without jQuery — in plain vanilla JS. | «yes» Пояснение: Bootstrap 5 removed its dependency on jQuery and uses its own vanilla JavaScript for all interactive components.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Bootstrap 5 removed its dependency on jQuery and uses its own vanilla JavaScript for all interactive components." ⏎ } | верно | jQuery удалён в Bootstrap 5.0: data-bs-* атрибуты и JS API. В проекте vendored 5.3.3. |
T24-L8 0.41 c | Bootstrap | Dark mode in Bootstrap is enabled with a .dark class on the root element. | «yes» Пояснение: In Bootstrap 5, dark mode is enabled by adding the 'dark' class to the root element (usually the <body> or <html> tag).
Raw{"answer": "yes", "explanation": "In Bootstrap 5, dark mode is enabled by adding the 'dark' class to the root element (usually the <body> or <html> tag)."} | неверно верный: «no» | Наоборот: тема включается атрибутом data-bs-theme="dark" (Color modes, с 5.3); класса .dark не существует. В проекте 5.3.3. |
T14-L1 0.47 c | Doctrine | Doctrine ORM creates database tables on the fly the first time an entity is used at runtime. | «no» Пояснение: Doctrine ORM does not automatically create tables at runtime; you must run migrations (via Doctrine Migrations or Schematizer) to create or alter the database schema.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "Doctrine ORM does not automatically create tables at runtime; you must run migrations (via Doctrine Migrations or Schematizer) to create or alter the database schema." ⏎ } | верно | Схему создают инструменты (migrations, schema tool); рантайм структуру БД не меняет. |
T14-L2 0.4 c | Doctrine | Which EntityManager method marks a new object as managed without executing SQL until flush()? | «persist» Пояснение: The persist method adds a new entity to the managed state of the EntityManager, ensuring it is tracked and persisted on the next flush without executing SQL immediately.
Raw{"answer": "persist", "explanation": "The persist method adds a new entity to the managed state of the EntityManager, ensuring it is tracked and persisted on the next flush without executing SQL immediately."} | верно | persist() регистрирует объект в Unit of Work; INSERT выполняется на flush(). |
T14-L3 0.37 c | Doctrine | In Doctrine ORM 3, the EntityManager::merge() method exists and makes the passed object managed. | «yes» Пояснение: In Doctrine ORM 3, calling EntityManager::merge() on a detached or unmanaged entity makes it managed and returns the managed instance.
Raw{"answer": "yes", "explanation": "In Doctrine ORM 3, calling EntityManager::merge() on a detached or unmanaged entity makes it managed and returns the managed instance."} | неверно верный: «no» | В ORM 3 merge() удалён (в vendor проекта 3.7.6 метода нет); в Doctrine 2.x merge() возвращал управляемую копию. Версия зафиксирована — ORM 3. |
T14-L4 0.55 c | Doctrine | DQL queries are written in terms of entities and their fields, not tables and columns. | «yes» Пояснение: Data Query Language (DQL) is an object-oriented query language used in JPA that operates on entity classes and their member fields, abstracting away the underlying database table and column structures.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "Data Query Language (DQL) is an object-oriented query language used in JPA that operates on entity classes and their member fields, abstracting away the underlying database table and column structures." ⏎ } ⏎ ``` | верно | Doctrine транслирует DQL в SQL; docs — DQL (Doctrine Query Language). |
T14-L5 0.39 c | Doctrine | What does $repository->find(999) return when no record with id 999 exists? | «{» Пояснение: ,
"explanation": "In Doctrine, find() returns null when the entity with the given ID does not exist."
}
Raw{ ⏎ "answer": null, ⏎ "explanation": "In Doctrine, find() returns null when the entity with the given ID does not exist." ⏎ } | неверно верный: «null» парсинг: текст (фолбэк) | find() возвращает null, если объект не найден (docs Repository methods). |
T14-L6 0.41 c | Doctrine | DoctrineBundle in Symfony automatically calls flush() at the end of every request. | «yes» Пояснение: The DoctrineBundle automatically invokes the EntityManager's flush() method at the end of every request to persist changes made during the request cycle.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "The DoctrineBundle automatically invokes the EntityManager's flush() method at the end of every request to persist changes made during the request cycle." ⏎ } | неверно верный: «no» | Авто-flush нет — flush() зовёт разработчик; незакрытая транзакция в конце запроса откатывается. |
T14-L7 0.46 c | Doctrine | For a managed entity, changing a property is enough: flush() commits the change without an explicit persist() — the Unit of Work tracks changes. | «yes» Пояснение: In an ORM like Doctrine, a managed entity is already tracked by the Unit of Work, so modifying its properties and calling flush() is sufficient to persist changes without an explicit persist() call.
Raw{"answer": "yes", "explanation": "In an ORM like Doctrine, a managed entity is already tracked by the Unit of Work, so modifying its properties and calling flush() is sufficient to persist changes without an explicit persist() call."} | верно | Dirty checking сравнивает снимки свойств; persist нужен только новым/отсоединённым объектам. |
T14-L8 0.38 c | Doctrine | remove() executes the SQL DELETE immediately, without waiting for flush(). | «yes» Пояснение: The Doctrine EntityManager's remove() method immediately issues a DELETE SQL query to the database.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "The Doctrine EntityManager's remove() method immediately issues a DELETE SQL query to the database." ⏎ } | неверно верный: «no» | remove() планирует удаление в Unit of Work; DELETE выполняется на flush() (docs — Deleting Objects). |
T15-L1 0.4 c | PostgreSQL | PostgreSQL uses MVCC, therefore readers block writers and writers block readers. | «no» Пояснение: PostgreSQL's MVCC allows readers and writers to proceed concurrently without blocking each other, as readers see a snapshot of the database at their transaction start.
Raw{"answer": "no", "explanation": "PostgreSQL's MVCC allows readers and writers to proceed concurrently without blocking each other, as readers see a snapshot of the database at their transaction start."} | верно | Наоборот: благодаря MVCC читатели не блокируют писателей и наоборот (снимки строк); docs PostgreSQL — Concurrency Control. |
T15-L2 0.35 c | PostgreSQL | Which SQL command shows a query's execution plan without executing the query? | «explain» Пояснение: The EXPLAIN command analyzes and displays the execution plan of a query without running it.
Raw{ ⏎ "answer": "EXPLAIN", ⏎ "explanation": "The EXPLAIN command analyzes and displays the execution plan of a query without running it." ⏎ } | верно | EXPLAIN без ANALYZE только строит план; проверено на PostgreSQL 17.7. |
T15-L3 0.57 c | PostgreSQL | SERIAL and GENERATED ... AS IDENTITY are just two names for the same mechanism. | «yes» Пояснение: The SQL standard defines GENERATED ... AS IDENTITY as the canonical syntax for auto-incrementing identity columns, while SERIAL is a non-standard PostgreSQL shorthand that expands to a generated identity column with a specific sequence, making them functionally the same mechanism in that context.
Raw{"answer": "yes", "explanation": "The SQL standard defines GENERATED ... AS IDENTITY as the canonical syntax for auto-incrementing identity columns, while SERIAL is a non-standard PostgreSQL shorthand that expands to a generated identity column with a specific sequence, making them functionally the same mechanism in that context."} | неверно верный: «no» | SERIAL — нестандартный макрос (sequence + DEFAULT), IDENTITY — SQL-стандарт; различаются владением и правами. Оба есть в PG 17 (проверено). |
T15-L4 0.39 c | PostgreSQL | By default, a PostgreSQL UNIQUE constraint allows only one row with NULL in the column. | «no» Пояснение: PostgreSQL by default treats multiple NULL values as distinct, allowing multiple rows to satisfy a UNIQUE constraint when the column contains NULL.
Raw{"answer": "false", "explanation": "PostgreSQL by default treats multiple NULL values as distinct, allowing multiple rows to satisfy a UNIQUE constraint when the column contains NULL."} | верно | Наоборот: NULLS DISTINCT по умолчанию — несколько NULL допустимы; NULLS NOT DISTINCT — опция с PG 15. Проверено на PG 17.7. |
T15-L5 0.33 c | PostgreSQL | Which PostgreSQL aggregate function concatenates strings with a separator? | «string_agg» Пояснение: The string_agg function in PostgreSQL concatenates a list of strings into one, optionally using a specified separator.
Raw{"answer": "string_agg", "explanation": "The string_agg function in PostgreSQL concatenates a list of strings into one, optionally using a specified separator."} | верно | string_agg(значение, разделитель); проверено на PostgreSQL 17.7. |
T15-L6 0.45 c | PostgreSQL | Plain VACUUM returns the space occupied by dead tuples to the operating system. | «yes» Пояснение: In PostgreSQL, a simple VACUUM command reclaims space occupied by dead tuples from table files and returns that unused disk space to the operating system.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "In PostgreSQL, a simple VACUUM command reclaims space occupied by dead tuples from table files and returns that unused disk space to the operating system." ⏎ } | неверно верный: «no» | VACUUM помечает место для переиспользования внутри таблицы; ОС его возвращает только VACUUM FULL (с эксклюзивной блокировкой). |
T15-L7 0.33 c | PostgreSQL | Which keyword in a window function definition partitions rows into groups the function is computed over? | «partition by» Пояснение: The PARTITION BY clause defines how the result set is divided into groups for window function computation.
Raw{"answer": "PARTITION BY", "explanation": "The PARTITION BY clause defines how the result set is divided into groups for window function computation."} | верно | OVER (PARTITION BY ...); проверено на PostgreSQL 17.7. |
T15-L8 0.58 c | PostgreSQL | The READ COMMITTED isolation level protects against non-repeatable reads. | «yes» Пояснение: The READ COMMITTED isolation level is designed to ensure that each transaction only reads data that has been committed before the start of each individual statement, thereby protecting against non-repeatable reads where the same row could be read with different values across multiple statements within a single transaction.
Raw{"answer": "yes", "explanation": "The READ COMMITTED isolation level is designed to ensure that each transaction only reads data that has been committed before the start of each individual statement, thereby protecting against non-repeatable reads where the same row could be read with different values across multiple statements within a single transaction."} | неверно верный: «no» | READ COMMITTED допускает неповторяющееся чтение; защищает REPEATABLE READ. Проверено: SHOW transaction_isolation → read committed. |
T17-L1 0.5 c | PostgreSQL: transactions and indexes | By default, PostgreSQL wraps each single SQL statement in its own implicit transaction (autocommit). | «yes» Пояснение: PostgreSQL operates in autocommit mode by default, meaning each SQL statement is executed as its own separate transaction unless explicitly wrapped in a BEGIN...COMMIT block.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "PostgreSQL operates in autocommit mode by default, meaning each SQL statement is executed as its own separate transaction unless explicitly wrapped in a BEGIN...COMMIT block." ⏎ } | верно | Без BEGIN каждый оператор коммитится сам; docs PostgreSQL — Transactions. Проверено на PG 17. |
T17-L2 0.36 c | PostgreSQL: transactions and indexes | Which SQL command ends a transaction, committing all its changes? | «commit» Пояснение: The SQL command COMMIT is used to finalize and permanently save all changes made within a transaction.
Raw{ ⏎ "answer": "COMMIT", ⏎ "explanation": "The SQL command COMMIT is used to finalize and permanently save all changes made within a transaction." ⏎ } | верно | COMMIT (END — синоним). Проверено на PG 17. |
T17-L3 0.38 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 improve the performance of UPDATE and DELETE statements by allowing the database to quickly locate the rows to modify based on the indexed search criteria.
Raw{"answer": "yes", "explanation": "Indexes improve the performance of UPDATE and DELETE statements by allowing the database to quickly locate the rows to modify based on the indexed search criteria."} | верно | Поиск строк для изменения идёт по индексу; docs PostgreSQL — Indexes. |
T17-L4 0.49 c | PostgreSQL: transactions and indexes | To roll back part of the statements inside a transaction, PostgreSQL uses SAVEPOINT. | «yes» Пояснение: In PostgreSQL, SAVEPOINT creates a named savepoint within a transaction that allows you to roll back to that specific point using ROLLBACK TO SAVEPOINT.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "In PostgreSQL, SAVEPOINT creates a named savepoint within a transaction that allows you to roll back to that specific point using ROLLBACK TO SAVEPOINT." ⏎ } ⏎ ``` | верно | SAVEPOINT name; ROLLBACK TO name — частичный откат без отмены всей транзакции. Проверено на PG 17. |
T17-L5 0.39 c | PostgreSQL: transactions and indexes | EXPLAIN ANALYZE shows the query plan without executing the query. | «no» Пояснение: EXPLAIN ANALYZE actually executes the query to measure execution times and row counts, whereas a simple EXPLAIN only shows the plan without executing it.
Raw{"answer": "no", "explanation": "EXPLAIN ANALYZE actually executes the query to measure execution times and row counts, whereas a simple EXPLAIN only shows the plan without executing it."} | верно | Наоборот: ANALYZE реально выполняет запрос (с побочными эффектами!) и показывает фактические времена узлов; план без выполнения — plain EXPLAIN. |
T17-L6 0.31 c | PostgreSQL: transactions and indexes | Which PostgreSQL extension adds vector types and indexes for embedding search? | «pgvector» Пояснение: pgvector is a PostgreSQL extension that provides vector data types and index structures for embedding search.
Raw{"answer": "pgvector", "explanation": "pgvector is a PostgreSQL extension that provides vector data types and index structures for embedding search."} | верно | CREATE EXTENSION vector (проект pgvector; в проекте образ pgvector/pgvector:pg17). |
T17-L7 0.34 c | PostgreSQL: transactions and indexes | A partial index (CREATE INDEX ... WHERE ...) is built only over rows satisfying the condition. | «yes» Пояснение: Partial indexes in PostgreSQL are specifically designed to index only the subset of rows that satisfy the specified WHERE clause condition.
Raw{"answer": "yes", "explanation": "Partial indexes in PostgreSQL are specifically designed to index only the subset of rows that satisfy the specified WHERE clause condition."} | верно | docs PostgreSQL — Partial Indexes; типичный кейс — индекс по «активным» записям. |
T17-L8 0.41 c | PostgreSQL: transactions and indexes | The SERIALIZABLE level in PostgreSQL is implemented by locking the rows a transaction reads. | «yes» Пояснение: The SERIALIZABLE isolation level in PostgreSQL is implemented using snapshot isolation with additional checks, including locking or rechecking rows a transaction reads to ensure serializability.
Raw{"answer": "yes", "explanation": "The SERIALIZABLE isolation level in PostgreSQL is implemented using snapshot isolation with additional checks, including locking or rechecking rows a transaction reads to ensure serializability."} | неверно верный: «no» | SSI (Serializable Snapshot Isolation): предикатные блокировки на снимках, не блокировки прочитанных строк; docs PostgreSQL. |
T19-L1 0.34 c | HTTP and REST API | HTTP status 201 means the request resulted in a new resource being created. | «yes» Пояснение: HTTP status code 201 indicates that the request has successfully resulted in the creation of a new resource.
Raw{"answer": "yes", "explanation": "HTTP status code 201 indicates that the request has successfully resulted in the creation of a new resource."} | верно | 201 Created; обычно на POST, часто с Location; RFC 9110. |
T19-L2 0.37 c | HTTP and REST API | Which HTTP status means a successful request with an empty response body (e.g. after DELETE)? | «204 no content» Пояснение: HTTP 204 indicates success but the response body is empty by specification.
Raw{ ⏎ "answer": "204 No Content", ⏎ "explanation": "HTTP 204 indicates success but the response body is empty by specification." ⏎ } | верно | 204 No Content; RFC 9110. |
T19-L3 0.59 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. | «no» Пояснение: DELETE is generally considered idempotent in the sense that deleting the same resource again will result in a 404, but the HTTP specification does not explicitly define DELETE as idempotent; its idempotency can be implementation-dependent.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "DELETE is generally considered idempotent in the sense that deleting the same resource again will result in a 404, but the HTTP specification does not explicitly define DELETE as idempotent; its idempotency can be implementation-dependent." ⏎ } | неверно верный: «yes» | RFC 9110: DELETE идемпотентен (как PUT); идемпотентность ≠ безопасность — ресурс удаляется при первом вызове. |
T19-L4 0.42 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 to indicate which origins are permitted to make cross-origin requests, not by the client.
Raw{"answer": "no", "explanation": "The Access-Control-Allow-Origin header is sent by the server to indicate which origins are permitted to make cross-origin requests, not by the client."} | верно | Наоборот: заголовок шлёт СЕРВЕР в ответе, разрешая браузеру cross-origin запрос (CORS); в проекте nelmio/cors-bundle. |
T19-L5 0.4 c | HTTP and REST API | Status 429 Too Many Requests is used when a client exceeds a rate limit. | «yes» Пояснение: HTTP 429 is specifically used to inform the client that it has exceeded the allowed request rate, often accompanied by a Retry-After header.
Raw{"answer": "yes", "explanation": "HTTP 429 is specifically used to inform the client that it has exceeded the allowed request rate, often accompanied by a Retry-After header."} | верно | 429 (+ Retry-After); RFC 6585. В проекте symfony/rate-limiter. |
T19-L6 0.34 c | HTTP and REST API | 5xx codes mean a client error, while 4xx means a server-side error. | «no» Пояснение: 4xx codes indicate client errors, while 5xx codes indicate server errors.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "4xx codes indicate client errors, while 5xx codes indicate server errors." ⏎ } | верно | Наоборот: 4xx — ошибка клиента (400, 404), 5xx — сервера (500, 503); классы статусов RFC 9110. |
T19-L7 0.31 c | HTTP and REST API | Which HTTP header indicates the MIME type of the request or response body? | «content-type» Пояснение: The Content-Type header specifies the media type (MIME type) of the payload.
Raw{"answer": "Content-Type", "explanation": "The Content-Type header specifies the media type (MIME type) of the payload."} | верно | Content-Type: application/json и т.п. |
T19-L8 0.69 c | HTTP and REST API | PATCH is not required to be idempotent per RFC 5789, unlike PUT. | «no» Пояснение: RFC 7235 states that the PATCH method is NOT idempotent, whereas PUT is idempotent; the statement correctly identifies PATCH as non-idempotent, so the answer is 'true' if the statement says PATCH is not required to be idempotent.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "RFC 7235 states that the PATCH method is NOT idempotent, whereas PUT is idempotent; the statement correctly identifies PATCH as non-idempotent, so the answer is 'true' if the statement says PATCH is not required to be idempotent." ⏎ } ⏎ ``` | неверно верный: «yes» | RFC 5789 прямо оговаривает: PATCH не гарантированно идемпотентен; PUT идемпотентен. |
T20-L1 0.45 c | Security and OAuth | Checking a password by comparing its hash to the stored hash with a plain == is sufficient. | «no» Пояснение: Using plain == is vulnerable to timing attacks, which can leak information about the hash; a timing-safe comparison function like hash_equals() should be used instead.
Raw{"answer": "no", "explanation": "Using plain == is vulnerable to timing attacks, which can leak information about the hash; a timing-safe comparison function like hash_equals() should be used instead."} | верно | Нужна постоянновременная проверка (password_verify) — timing-атаки; соль и алгоритм уже внутри хеша. |
T20-L2 0.44 c | Security and OAuth | A CSRF token is issued by the server (bound to the session) and verified server-side on unsafe requests (POST etc.). | «yes» Пояснение: CSRF tokens are indeed issued by the server, bound to the user's session, and verified server-side to protect against cross-site request forgery attacks on state-changing requests.
Raw{"answer": "yes", "explanation": "CSRF tokens are indeed issued by the server, bound to the user's session, and verified server-side to protect against cross-site request forgery attacks on state-changing requests."} | верно | symfony/security-csrf в проекте; защита от подделки межсайтовой формы. |
T20-L3 0.43 c | Security and OAuth | Which HTTP header enables the CSP (Content Security Policy) policy? | «content-security-policy» Пояснение: The Content-Security-Policy header is the specific HTTP header used to declare the Content Security Policy for a web page.
Raw{"answer": "Content-Security-Policy", "explanation": "The Content-Security-Policy header is the specific HTTP header used to declare the Content Security Policy for a web page."} | верно | Content-Security-Policy; белые списки источников скриптов/стилей против XSS. |
T20-L4 0.41 c | Security and OAuth | OAuth 2.0 is an authentication protocol: the access token tells you who the user is. | «no» Пояснение: OAuth 2.0 is an authorization framework, not an authentication protocol, and access tokens grant access to specific resources rather than identifying who the user is.
Raw{"answer": "no", "explanation": "OAuth 2.0 is an authorization framework, not an authentication protocol, and access tokens grant access to specific resources rather than identifying who the user is."} | верно | OAuth 2.0 — авторизация/делегирование доступа; аутентификацию добавляет OpenID Connect. В проекте knpuniversity/oauth2-client-bundle (yandex/github/google). |
T20-L5 0.52 c | Security and OAuth | XSS is prevented by validating input on the server before writing it to the database. | «no» Пояснение: Validating input on the server is primarily a measure against SQL injection, and XSS is effectively prevented by output encoding when data is sent to the client, not just by server-side validation.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "Validating input on the server is primarily a measure against SQL injection, and XSS is effectively prevented by output encoding when data is sent to the client, not just by server-side validation." ⏎ } | верно | XSS лечится контекстным экранированием НА ВЫВОДЕ (Twig autoescape, CSP); валидация ввода не покрывает все контексты вывода. |
T20-L6 0.42 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» Пояснение: The authorization code is the temporary code passed to the redirect URI in the OAuth 2.0 authorization code flow, which is then exchanged for an access token.
Raw{"answer": "code", "explanation": "The authorization code is the temporary code passed to the redirect URI in the OAuth 2.0 authorization code flow, which is then exchanged for an access token."} | верно | Параметр code; обмен на токен POST-ом на /token с client_secret. |
T20-L7 0.38 c | Security and OAuth | A refresh token lives longer than an access token and allows obtaining a new access token without the user logging in again. | «yes» Пояснение: Refresh tokens are designed to have a longer expiry than access tokens and enable silent re-authentication without user input.
Raw{"answer": "yes", "explanation": "Refresh tokens are designed to have a longer expiry than access tokens and enable silent re-authentication without user input."} | верно | Стандартная схема OAuth/OIDC: короткий access + длинный refresh. |
T20-L8 0.38 c | Security and OAuth | A password salt must be kept secret: without it the hash cannot be verified. | «no» Пояснение: Salt is typically stored in the database alongside the hash to allow verification, but the hash algorithm and key (if any) should be secret.
Raw{"answer": "no", "explanation": "Salt is typically stored in the database alongside the hash to allow verification, but the hash algorithm and key (if any) should be secret."} | верно | Соль хранится открыто (password_hash включает её в строку хеша); секретность соли не нужна. |
T18-L1 0.36 c | Testing: PHPUnit | PHPUnit runs test methods of any class — extending TestCase is not required. | «no» Пояснение: PHPUnit test classes must extend TestCase (or a subclass) for its test methods to be recognized and executed.
Raw```json ⏎ {"answer": "false", "explanation": "PHPUnit test classes must extend TestCase (or a subclass) for its test methods to be recognized and executed."} ⏎ ``` | верно | Тестом считается метод класса, наследующего TestCase (PHPUnit 10). |
T18-L2 0.43 c | Testing: PHPUnit | In PHPUnit, setUp() runs once before all tests of the class. | «no» Пояснение: In PHPUnit, setUp() is called before each test method, not once for the entire class; setUpClass() is used for setup that runs once before the test class.
Raw{"answer": "no", "explanation": "In PHPUnit, setUp() is called before each test method, not once for the entire class; setUpClass() is used for setup that runs once before the test class."} | верно | setUp() — перед КАЖДЫМ тестом; один раз на класс — setUpBeforeClass(). Проверено живым счётчиком на PHPUnit 10.5. |
T18-L3 0.44 c | Testing: PHPUnit | A data provider lets a test run with exactly one set of arguments. | «yes» Пояснение: A data provider in PHPUnit can return multiple data sets, but when attached to a single test method, each test case is run independently with exactly one set of arguments from the provider.
Raw{"answer": "yes", "explanation": "A data provider in PHPUnit can return multiple data sets, but when attached to a single test method, each test case is run independently with exactly one set of arguments from the provider."} | неверно верный: «no» | Наоборот: наборов может быть сколько угодно — тест выполняется по разу на каждый. Проверено на PHPUnit 10.5 (#[DataProvider]). |
T18-L4 0.34 c | Testing: PHPUnit | Which PHPUnit method declares an expectation that an exception of a given class is thrown? | «expectexception» Пояснение: The expectException method in PHPUnit declares the expectation that a specific exception class is thrown during the execution of a test.
Raw{"answer": "expectException", "explanation": "The expectException method in PHPUnit declares the expectation that a specific exception class is thrown during the execution of a test."} | верно | $this->expectException(\LogicException::class); проверено на PHPUnit 10.5. |
T18-L5 0.4 c | Testing: PHPUnit | In PHPUnit, a stub verifies which methods were called on it, while a mock only returns data. | «no» Пояснение: A stub is used to return data when a method is called, whereas a mock verifies which methods were called and their arguments.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "A stub is used to return data when a method is called, whereas a mock verifies which methods were called and their arguments." ⏎ } | верно | Наоборот: стаб подставляет данные, мок проверяет взаимодействия (createStub/createMock); docs PHPUnit — Test Doubles. |
T18-L6 0.75 c | Testing: PHPUnit | In PHPUnit 10+, the recommended way to pass data to a test is the #[DataProvider] attribute (the @dataProvider annotation is deprecated). | «no» Пояснение: ", "explanation": "While the #[DataProvider] attribute is supported in PHPUnit 10+, the @dataProvider annotation is not deprecated; instead, the @dataProvider annotation is still valid and functional in PHPUnit 10, and the use of annotations in general has not been deprecated in PHPUnit 10 (annotations are planned to be removed in PHPUnit 11, not deprecated in PHPUnit 10)."
Raw{"answer": "no", "explanation": "While the #[DataProvider] attribute is supported in PHPUnit 10+, the @dataProvider annotation is not deprecated; instead, the @dataProvider annotation is still valid and functional in PHPUnit 10, and the use of annotations in general has not been deprecated in PHPUnit 10 (annotations are planned to be removed in PHPUnit 11, not deprecated in PHPUnit 10)." | неверно верный: «yes» парсинг: текст (фолбэк) | Аннотация ещё парсится в PHPUnit 10/11 (AnnotationParser в 10.5.66), удаление — в 12; атрибут — стандарт. |
T18-L7 0.4 c | Testing: PHPUnit | PHPUnit does not allow one test to depend on the result of another. | «yes» Пояснение: PHPUnit supports test dependencies using the @depends annotation or dependsOnMethods annotation, allowing one test to depend on the result of another.
Raw{"answer": "yes", "explanation": "PHPUnit supports test dependencies using the @depends annotation or dependsOnMethods annotation, allowing one test to depend on the result of another."} | неверно верный: «no» | Зависимости есть: #[Depends] — зависимый тест не запустится, еслиProducer упал. |
T18-L8 0.32 c | Testing: PHPUnit | Which PHPUnit command-line option makes tests run in random order? | «--randomly-order» Пояснение: The --randomly-order option is used to shuffle the order in which tests are executed.
Raw{"answer": "--randomly-order", "explanation": "The --randomly-order option is used to shuffle the order in which tests are executed."} | неверно верный: «--order-by=random» | --order-by=random (PHPUnit 9+); опция есть в --help PHPUnit 10.5 (проектная). |
T01-L9 2.47 c | Syntax and operators | What does this code output?
```php
echo intdiv(7, 2) . intdiv(-7, 2);
``` | «3-4» Пояснение: intdiv(7, 2) returns 3, intdiv(-7, 2) returns -4 (truncates toward negative infinity), and concatenating the integers '3' and '-4' gives the string '3-4'.
Raw{"answer": "3-4", "explanation": "intdiv(7, 2) returns 3, intdiv(-7, 2) returns -4 (truncates toward negative infinity), and concatenating the integers '3' and '-4' gives the string '3-4'."} | неверно верный: «3-3» | intdiv truncates toward zero: intdiv(-7, 2) = -3, not -4. |
T01-L10 0.36 c | Syntax and operators | What does this code output?
```php
echo -3 ** 2;
``` | «-9» Пояснение: The exponentiation operator has higher precedence than the unary minus, so it calculates -(3 ** 2).
Raw{"answer": -9, "explanation": "The exponentiation operator has higher precedence than the unary minus, so it calculates -(3 ** 2)."} | верно | ** is right-associative and binds tighter than unary minus: -(3²). |
T02-L9 0.5 c | Types and comparisons | What does this code output?
```php
echo '1e1' == '10' ? 'true' : 'false';
``` | «true» Пояснение: In PHP, the '1e1' string is cast to a float (10.0), which is loosely equal to the integer 10, so the ternary expression evaluates to 'true'.
Raw{"answer": "true", "explanation": "In PHP, the '1e1' string is cast to a float (10.0), which is loosely equal to the integer 10, so the ternary expression evaluates to 'true'."} | верно | Both strings are numeric — compared as numbers: 10 == 10. |
T02-L10 0.44 c | Types and comparisons | What does this code output?
```php
switch ('a') {
case 0: echo 'zero'; break;
default: echo 'other';
}
``` | «other» Пояснение: The switch compares 'a' with 0 using loose comparison (==), which is false, so the default case executes.
Raw{ ⏎ "answer": "other", ⏎ "explanation": "The switch compares 'a' with 0 using loose comparison (==), which is false, so the default case executes." ⏎ } | верно | PHP 8: 'a' == 0 → false (used to be true) — default fires. |
T03-L9 0.48 c | Strings | What does this code output?
```php
echo strtr('abc', ['a' => '1', 'ab' => '2']);
``` | «1bc» Пояснение: strtr scans for the longest matching key first, so 'ab' is replaced by '2' and the remaining 'c' is unchanged.
Raw```json ⏎ {"answer": "1bc", "explanation": "strtr scans for the longest matching key first, so 'ab' is replaced by '2' and the remaining 'c' is unchanged."} ⏎ ``` | неверно верный: «2c» | strtr with an array prefers the longest matching key. |
T03-L10 0.39 c | Strings | What does this code output?
```php
echo '[' . substr('hello', -10) . ']';
``` | «[hello]» Пояснение: substr('hello', -10) starts at position -10 (before the beginning) and returns the entire string 'hello'.
Raw{"answer": "[hello]", "explanation": "substr('hello', -10) starts at position -10 (before the beginning) and returns the entire string 'hello'."} | верно | A negative start beyond the string is clamped to the beginning. |
T04-L9 0.43 c | Arrays | What does this code output?
```php
$a = ['k' => 1, 'n' => 2];
$b = ['k' => 9, 'm' => 3];
echo implode(',', array_keys($a + $b));
``` | «k,n,m» Пояснение: The + operator merges arrays with $a's keys taking precedence, so the resulting keys are k, n, and m.
Raw{ ⏎ "answer": "k,n,m", ⏎ "explanation": "The + operator merges arrays with $a's keys taking precedence, so the resulting keys are k, n, and m." ⏎ } | верно | The + operator: on duplicate string keys the left array wins. |
T04-L10 0.5 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));
``` | «xyz» Пояснение: The arrays are sorted by their third element (all values are 2, so order remains unchanged), and then the second elements are concatenated into 'xyz'.
Raw{ ⏎ "answer": "xyz", ⏎ "explanation": "The arrays are sorted by their third element (all values are 2, so order remains unchanged), and then the second elements are concatenated into 'xyz'." ⏎ } | неверно верный: «yxz» | Sorts are stable since 8.0: x and z keep their order on a tie. |
T05-L10 0.52 c | Functions and closures | What does this code output?
```php
function f(int $a, int $b): int
{
return $a - $b;
}
echo f(...['b' => 1, 'a' => 5]);
``` | «4» Пояснение: The spread operator passes the array values as named arguments, so $a=5 and $b=1, making 5-1=4.
Raw```json ⏎ { ⏎ "answer": "4", ⏎ "explanation": "The spread operator passes the array values as named arguments, so $a=5 and $b=1, making 5-1=4." ⏎ } ⏎ ``` | верно | String keys of a spread array become named arguments. |
T05-L9 1.37 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 arrow function $f closes over $p by reference; however, when $f is called, $p has been set to null, so $p->g() would throw a fatal error... wait, let me re-examine: actually in PHP, when $p is reassigned to null, the closure still holds a reference to the old object if created with late binding... but closures in PHP use copy-on-write semantics for variables unless 'use' is specified... actually this closure does NOT use 'use', it just references $p from the outer scope, so when $p is reassigned, $f will see $p as null and throw an Error when calling ->g() on null.
Raw```json ⏎ {"answer": "3", "explanation": "The arrow function $f closes over $p by reference; however, when $f is called, $p has been set to null, so $p->g() would throw a fatal error... wait, let me re-examine: actually in PHP, when $p is reassigned to null, the closure still holds a reference to the old object if created with late binding... but closures in PHP use copy-on-write semantics for variables unless 'use' is specified... actually this closure does NOT use 'use', it just references $p from the outer scope, so when $p is reassigned, $f will see $p as null and throw an Error when calling ->g() on null."} ⏎ ``` | верно | First-class callable syntax binds $this at creation time. |
T06-L9 0.39 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 in a late-static-binding method returns the class where the method was ultimately invoked, which is B.
Raw{"answer": "B", "explanation": "static::class in a late-static-binding method returns the class where the method was ultimately invoked, which is B."} | верно | Late static binding: static::class is the receiver's class. |
T06-L10 0.51 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» Пояснение: PHP 8.5 introduced property hooks (set accessors), so the set hook multiplies 5 by 2, resulting in 10.
Raw{ ⏎ "answer": "10", ⏎ "explanation": "PHP 8.5 introduced property hooks (set accessors), so the set hook multiplies 5 by 2, resulting in 10." ⏎ } | верно | Inside the set hook, $this->x writes the backing store (no recursion): 5*2. |
T07-L9 0.57 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();
``` | «b» Пояснение: The conflict resolution syntax resolves the 'f' method to TB::f instead of TA::f, so calling f() returns 'B' and g() also returns 'B'.
Raw{ ⏎ "answer": "B", ⏎ "explanation": "The conflict resolution syntax resolves the 'f' method to TB::f instead of TA::f, so calling f() returns 'B' and g() also returns 'B'." ⏎ } | неверно верный: «ba» | insteadof picks the implementation; as keeps the other under an alias. |
T07-L10 0.51 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» Пояснение: A trait with static properties is aliased per class, so CX::$n and CY::$n are separate properties; changing CX::$n does not affect CY::$n which remains 0.
Raw{"answer": "0", "explanation": "A trait with static properties is aliased per class, so CX::$n and CY::$n are separate properties; changing CX::$n does not affect CY::$n which remains 0."} | верно | A trait's static property is copied into each consuming class. |
T08-L10 0.57 c | Exceptions and errors | What does this code output?
```php
function f(): int
{
try { return 1; } finally { return 2; }
}
echo f();
``` | «1» Пояснение: In PHP, a `finally` block with its own `return` does not override the value returned by a `try` block that already has a `return`, so the function returns 1.
Raw{ ⏎ "answer": 1, ⏎ "explanation": "In PHP, a `finally` block with its own `return` does not override the value returned by a `try` block that already has a `return`, so the function returns 1." ⏎ } | неверно верный: «2» | A return in finally overrides the return from try. |
T08-L9 0.44 c | Exceptions and errors | What does this code output?
```php
try {
try {
throw new RuntimeException('first');
} finally {
throw new LogicException('second');
}
} catch (LogicException $e) {
echo $e->getMessage();
}
``` | «second» Пояснение: The LogicException thrown in the finally block propagates to the outer catch block after the inner try block exits, causing it to be caught and printed.
Raw{"answer": "second", "explanation": "The LogicException thrown in the finally block propagates to the outer catch block after the inner try block exits, causing it to be caught and printed."} | верно | An exception from finally replaces the in-flight one — the last thrown is caught. |
T09-L9 0.4 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» Пояснение: The use alias maps to 'App\Foo', while the fully qualified name resolves to 'Baz'.
Raw{"answer": "App\\Foo|Baz", "explanation": "The use alias maps to 'App\\Foo', while the fully qualified name resolves to 'Baz'."} | верно | The use alias applies to unqualified names; a leading \ escapes to the global scope. |
T09-L10 0.51 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') returns false because the class Foo exists in Ns, but the fully-qualified name Ns\Foo matches the second check.
Raw```json ⏎ { ⏎ "answer": "noyes", ⏎ "explanation": "class_exists('Foo') returns false because the class Foo exists in Ns, but the fully-qualified name Ns\\Foo matches the second check." ⏎ } ⏎ ``` | верно | Dynamic names are not resolved against the namespace — 'Foo' is the global class. |
T10-L9 0.49 c | References and scope | What does this code output?
```php
$a = [1, 2, 3];
foreach ($a as &$v) {}
$v = 99;
echo implode(',', $a);
``` | «1,99,99» Пояснение: The foreach loop overwrites $a with references to the same array element, so all elements point to $v.
Raw{ ⏎ "answer": "1,99,99", ⏎ "explanation": "The foreach loop overwrites $a with references to the same array element, so all elements point to $v." ⏎ } | неверно верный: «1,2,99» | After a by-ref foreach, $v remains a reference to the last element. |
T10-L10 0.47 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 properties are shared per class, but the static $n variable is declared in class A, so both instances share the same counter, which becomes 3 after three calls.
Raw{"answer":"3","explanation":"Static properties are shared per class, but the static $n variable is declared in class A, so both instances share the same counter, which becomes 3 after three calls."} | верно | A method's static variable belongs to the parent's method — subclasses share it. |
T11-L9 0.59 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» Пояснение: Calling send(10) on the generator before the first yield executes resumes it, causing the yield 1 expression to be set to 10, which is then returned as $x + 1 = 11.
Raw{"answer": "11", "explanation": "Calling send(10) on the generator before the first yield executes resumes it, causing the yield 1 expression to be set to 10, which is then returned as $x + 1 = 11."} | верно | send() resumes the generator: $x = 10, return 10+1. |
T11-L10 0.49 c | Generators, iterators, SPL | What does this code output?
```php
function inner(): Generator
{
yield 1;
yield 2;
return 'ok';
}
function outer(): Generator
{
$r = yield from inner();
yield $r;
}
echo implode(',', iterator_to_array(outer()));
``` | «1,2,ok» Пояснение: yield from delegates the inner generator, yields 1 and 2, and $r receives the final return value 'ok' which is then yielded by outer().
Raw{"answer": "1,2,ok", "explanation": "yield from delegates the inner generator, yields 1 and 2, and $r receives the final return value 'ok' which is then yielded by outer()."} | неверно верный: «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 0.61 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';
``` | «yesno» Пояснение: The first call uses the same cost parameter as the hash was created, so it returns false; the second call requests a higher cost, so it returns true, producing the concatenated output 'yesno'.
Raw{ ⏎ "answer": "yesno", ⏎ "explanation": "The first call uses the same cost parameter as the hash was created, so it returns false; the second call requests a higher cost, so it returns true, producing the concatenated output 'yesno'." ⏎ } | неверно верный: «noyes» | password_needs_rehash compares the hash's options with the target: cost 4 = 4 → 'no', cost 5 ≠ 4 → 'yes'. |
T12-L10 0.58 c | Configuration and security | What does this code output on PHP 8.5?
```php
echo (E_ALL & 2048) === 0 ? 'strict-out' : 'strict-in';
``` | «strict-in» Пояснение: E_ALL (32767) & 2048 equals 2048, which is not 0, so the ternary evaluates to 'strict-in'.
Raw{ ⏎ "answer": "strict-in", ⏎ "explanation": "E_ALL (32767) & 2048 equals 2048, which is not 0, so the ternary evaluates to '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 0.55 c | Symfony | What does this code output?
```php
use Symfony\Component\HttpFoundation\Request;
$r = Request::create('/demo', 'GET', [], [], [], ['HTTP_X_TOKEN' => 'abc']);
echo $r->headers->get('X-Token') === 'abc' ? 'mapped' : 'missing';
``` | «mapped» Пояснение: Symfony's Request::create maps the HTTP_X_TOKEN header to the 'X-Token' header, and get('X-Token') returns 'abc', making the ternary condition true.
Raw{ ⏎ "answer": "mapped", ⏎ "explanation": "Symfony's Request::create maps the HTTP_X_TOKEN header to the 'X-Token' header, and get('X-Token') returns 'abc', making the ternary condition true." ⏎ } | верно | The literal comparison requires knowing the mapping: HttpFoundation turns HTTP_X_TOKEN into the X-Token header (case-insensitive); without it the answer is 'missing'. |
T13-L10 0.51 c | Symfony | What does this code output?
```php
use Symfony\Component\EventDispatcher\EventDispatcher;
use Symfony\Contracts\EventDispatcher\Event;
$d = new EventDispatcher();
$out = '';
$d->addListener('e', function () use (&$out) { $out .= 'B'; }, 10);
$d->addListener('e', function () use (&$out) { $out .= 'A'; });
$d->addListener('e', function () use (&$out) { $out .= 'C'; }, 5);
$d->dispatch(new Event(), 'e');
echo $out;
``` | «bca» Пояснение: Symfony's EventDispatcher sorts listeners by priority in descending order, so the priority 10 listener runs first, then the default priority 0 listener, then the priority 5 listener.
Raw{"answer": "BCA","explanation":"Symfony's EventDispatcher sorts listeners by priority in descending order, so the priority 10 listener runs first, then the default priority 0 listener, then the priority 5 listener."} | верно | Listeners run by descending priority: 10 (B), 5 (C), 0 (A). |
T14-L10 0.44 c | Doctrine | Given: Doctrine ORM 3, an EntityManager on in-memory SQLite, entity User with an auto-increment primary key. The users table is empty. What does this code output?
```php
$u = new User(name: 'A');
$em->persist($u);
$em->flush();
$a = $em->find(User::class, $u->getId());
$b = $em->find(User::class, $u->getId());
echo spl_object_id($a) === spl_object_id($b) ? 'same' : 'diff';
``` | «same» Пояснение: Doctrine's EntityManager uses an identity map so repeated find calls for the same entity return the same persistent object instance.
Raw```json ⏎ {"answer": "same", "explanation": "Doctrine's EntityManager uses an identity map so repeated find calls for the same entity return the same persistent object instance."} ⏎ ``` | верно | Identity map: a second find for the same id returns the same instance. |
T14-L9 0.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: 'B');
$em->persist($u);
$em->remove($u);
$em->flush();
echo count($em->getConnection()->fetchAllAssociative('SELECT * FROM users'));
``` | «0» Пояснение: Because the entity is persisted and then removed in the same unit of work before flushing, Doctrine never sends an INSERT to the database.
Raw{"answer": 0, "explanation": "Because the entity is persisted and then removed in the same unit of work before flushing, Doctrine never sends an INSERT to the database."} | верно | The unit of work schedules INSERT at flush: remove after persist cancels it. |
T15-L10 0.35 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() ignores NULL values, so it only counts the non-NULL value 1.
Raw{"answer": 1, "explanation": "COUNT() ignores NULL values, so it only counts the non-NULL value 1."} | верно | count(column) skips NULLs; count(*) would return 2. |
T15-L9 0.59 c | PostgreSQL | What does this SQL query return (PostgreSQL 17)?
```sql
CREATE TEMP TABLE t (id int, x int);
INSERT INTO t VALUES (1, 10), (2, 20), (3, 30);
SELECT string_agg(s::text, ',' ORDER BY id) FROM (
SELECT id, sum(x) OVER (ORDER BY id) AS s FROM t
) q;
``` | «10,30,60» Пояснение: The window function sum(x) OVER (ORDER BY id) produces cumulative sums 10, 30, 60 in id order, which string_agg then joins with commas.
Raw{ ⏎ "answer": "10,30,60", ⏎ "explanation": "The window function sum(x) OVER (ORDER BY id) produces cumulative sums 10, 30, 60 in id order, which string_agg then joins with commas." ⏎ } | верно | With ORDER BY the default window frame is running (start to current row). |
T16-L9 0.47 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» Пояснение: Symfony Messenger processes the middleware in the order they are added, so the first Trace echoes M1 and the next one echoes M2.
Raw{"answer": "M1M2", "explanation": "Symfony Messenger processes the middleware in the order they are added, so the first Trace echoes M1 and the next one echoes M2."} | верно | The first-added middleware runs first (outermost). |
T16-L10 0.52 c | Symfony: Messenger | What does this code output?
```php
use Symfony\Component\Messenger\MessageBus;
use Symfony\Component\Messenger\Middleware\HandleMessageMiddleware;
use Symfony\Component\Messenger\Handler\HandlersLocator;
use Symfony\Component\Messenger\Handler\HandlerDescriptor;
use Symfony\Component\Messenger\Envelope;
class Ping {}
$n = 0;
$d1 = new HandlerDescriptor(function (Ping $m) use (&$n) { $n += 1; }, ['alias' => 'h1']);
$d2 = new HandlerDescriptor(function (Ping $m) use (&$n) { $n += 10; }, ['alias' => 'h2']);
$bus = new MessageBus([
new HandleMessageMiddleware(new HandlersLocator([Ping::class => [$d1, $d2]])),
]);
$bus->dispatch(new Envelope(new Ping()));
echo $n;
``` | «11» Пояснение: The HandleMessageMiddleware invokes all registered handlers for the message class, so both handlers execute and the shared counter $n becomes 1 + 10.
Raw```json ⏎ {"answer": 11, "explanation": "The HandleMessageMiddleware invokes all registered handlers for the message class, so both handlers execute and the shared counter $n becomes 1 + 10."} ⏎ ``` | верно | All registered handlers of the message run: 1 + 10 = 11. |
T17-L9 0.46 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 ON CONFLICT DO NOTHING clause prevents duplicate key insertions due to the unique index, so only the first row is inserted.
Raw{ ⏎ "answer": 1, ⏎ "explanation": "The ON CONFLICT DO NOTHING clause prevents duplicate key insertions due to the unique index, so only the first row is inserted." ⏎ } | верно | ON CONFLICT DO NOTHING skips the duplicate: one insert. |
T17-L10 0.46 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 and initially deferred, duplicate inserts are allowed within the transaction and only checked at COMMIT, so the final SELECT returns 2.
Raw{"answer": 2, "explanation": "Because the unique constraint is deferrable and initially deferred, duplicate inserts are allowed within the transaction and only checked at COMMIT, so the final SELECT returns 2."} | верно | DEFERRED postpones the uniqueness check to COMMIT — count sees 2 rows. |
T18-L9 0.51 c | Testing: PHPUnit | How many tests will this command run?
```php
use PHPUnit\Framework\TestCase;
use PHPUnit\Framework\Attributes\DataProvider;
final class CalcTest extends TestCase
{
public static function prov(): array
{
return [[1], [2], [3]];
}
#[DataProvider('prov')]
public function test_sum(int $x): void
{
$this->assertTrue($x > 0);
}
#[DataProvider('prov')]
public function test_sum_abs(int $x): void
{
$this->assertTrue($x > 0);
}
public function test_other(): void
{
$this->assertTrue(true);
}
}
```
Command: `phpunit CalcTest.php --filter test_sum` (PHPUnit 10.5) | «6» Пояснение: The --filter test_sum matches both test_sum and test_sum_abs, each of which runs 3 times due to the DataProvider, for a total of 6 tests.
Raw{"answer": 6, "explanation": "The --filter test_sum matches both test_sum and test_sum_abs, each of which runs 3 times due to the DataProvider, for a total of 6 tests."} | верно | --filter is a substring match: test_sum also matches test_sum_abs (3+3 datasets). |
T18-L10 0.48 c | Testing: PHPUnit | How many tests will this command run, and how many of them will fail? Answer with two comma-separated numbers (ran, failed).
```php
use PHPUnit\Framework\TestCase;
use PHPUnit\Framework\Attributes\DataProvider;
final class Calc2Test extends TestCase
{
public function prov(): array
{
return [[1], [-1]];
}
#[DataProvider('prov')]
public function test_x(int $x): void
{
$this->assertTrue($x > 0);
}
}
```
Command: `phpunit Calc2Test.php` (PHPUnit 10.5) | «2, 1» Пояснение: The data provider supplies two datasets, so two tests run, and only the dataset with -1 fails the assertion.
Raw{ ⏎ "answer": "2, 1", ⏎ "explanation": "The data provider supplies two datasets, so two tests run, and only the dataset with -1 fails the assertion." ⏎ } | верно | A non-static provider is just a deprecation in PHPUnit 10: both datasets run and the [-1] dataset fails the assert — 2 ran, 1 failure. |
T19-L9 0.38 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 of the request, which triggers the HTTP POST method.
Raw{"answer": "POST", "explanation": "The -d flag in curl sends data in the body of the request, which triggers the HTTP POST method."} | верно | -d/-F switches curl to POST by default. |
T19-L10 0.41 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 encode the -d data into the URL query string and send it via a GET request.
Raw{ ⏎ "answer": "GET", ⏎ "explanation": "The -G flag tells curl to encode the -d data into the URL query string and send it via a GET request." ⏎ } | верно | -G turns -d data into the query string; the method stays GET. |
T20-L9 0.49 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» Пояснение: According to RFC 6749, the 'invalid_client' error code is returned when the client identifier is not recognized by the authorization server.
Raw{ ⏎ "answer": "invalid_client", ⏎ "explanation": "According to RFC 6749, the 'invalid_client' error code is returned when the client identifier is not recognized by the authorization server." ⏎ } | верно | Unknown client → invalid_client (RFC 6749 §5.2). |
T20-L10 0.45 c | Security and OAuth | OAuth 2.0: the client started the flow with response_type=token. In which part of the redirect_uri does the authorization server pass the access_token? | «query component» Пояснение: In the implicit flow, which uses response_type=token, the authorization server returns the access token and other tokens in the query component of the redirect_uri.
Raw{"answer": "query component", "explanation": "In the implicit flow, which uses response_type=token, the authorization server returns the access token and other tokens in the query component of the redirect_uri."} | неверно верный: «fragment» | The implicit flow passes the token in the URL fragment (#) — it never reaches the server. |
T21-L9 0.8 c | Twig | What does this Twig template output?
```twig
{{ false|default(2) * 3 }}
``` | «6» Пояснение: In Twig, the default filter only triggers when the value is false or null, but in this case the template directly evaluates false * 3, which is 0, so the default is not applied and the result is 0, but wait, actually in Twig false|default(2) would return 2, then 2*3=6.
Raw{ ⏎ "answer": 6, ⏎ "explanation": "In Twig, the default filter only triggers when the value is false or null, but in this case the template directly evaluates false * 3, which is 0, so the default is not applied and the result is 0, but wait, actually in Twig false|default(2) would return 2, then 2*3=6." ⏎ } | верно | default replaces exactly false/null/''/[] — false becomes 2, 2*3 = 6; the naive 'default is for undefined only' yields 0. |
T21-L10 0.48 c | Twig | What exception class does render() of this template throw?
```twig
{{ 'a' ~ 1 + 2 }}
``` | «twig\twigruntimeexception» Пояснение: The expression combines a string and an integer, which is not supported in Twig, causing the render() method to throw a Twig\TwigRuntimeException.
Raw{"answer": "Twig\\TwigRuntimeException", "explanation": "The expression combines a string and an integer, which is not supported in Twig, causing the render() method to throw a Twig\\TwigRuntimeException."} | неверно верный: «runtimeerror» | In Twig ~ binds tighter than +: ('a' ~ 1) + 2 → string + int → a render error (RuntimeError). |
T22-L9 0.48 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 Symfony validator does not trigger the NotBlank constraint on a value of empty string, resulting in no violations and a count of 0.
Raw{ ⏎ "answer": 0, ⏎ "explanation": "The Symfony validator does not trigger the NotBlank constraint on a value of empty string, resulting in no violations and a count of 0." ⏎ } | верно | NotBlank treats null, '', [] as blank — the array [''] is not blank. |
T22-L10 0.37 c | Symfony: Security and forms | What does this code output?
```php
use Symfony\Component\Form\Forms;
use Symfony\Component\Form\Extension\Core\Type\TextType;
$factory = Forms::createFormFactoryBuilder()->getFormFactory();
$form = $factory->create(TextType::class);
try {
echo $form->isValid() ? 'valid' : 'invalid';
} catch (Throwable $e) {
echo get_class($e);
}
``` | «valid» Пояснение: A form created without any data or validation rules is considered valid by default when isValid() is called.
Raw{"answer": "valid", "explanation": "A form created without any data or validation rules is considered valid by default when isValid() is called."} | неверно верный: «symfony\component\form\exception\logicexception» | isValid() on a non-submitted form throws LogicException, it does not return false. |
T23-L9 0.36 c | Symfony: configuration and services | What does this code output?
```php
use Symfony\Component\DependencyInjection\ContainerBuilder;
$c = new ContainerBuilder();
$c->register('a', stdClass::class)->setPublic(true);
$c->compile();
echo spl_object_id($c->get('a')) === spl_object_id($c->get('a')) ? 'same' : 'diff';
``` | «same» Пояснение: Symfony DI Container is an array of containers (array), so get() is an array of arrays.
Raw{"answer": "same", "explanation": "Symfony DI Container is an array of containers (array), so get() is an array of arrays."} | верно | Container services are shared: two get() calls yield one instance. |
T23-L10 0.55 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 container builder replaces %name% with 'Bob' and %greeting%! with the final value of 'greeting' (which is 'hi Bob') during compile.
Raw```json ⏎ { ⏎ "answer": "hi Bob", ⏎ "explanation": "Symfony's container builder replaces %name% with 'Bob' and %greeting%! with the final value of 'greeting' (which is 'hi Bob') during compile." ⏎ } ⏎ ``` | неверно верный: «hi bob!» | compile() resolves %-references transitively: %greeting% → 'hi %name%' → 'hi Bob!', the answer assembles over two hops. |
T24-L9 0.54 c | Bootstrap | What is the max-width of .container in Bootstrap 5.3 at a 992px viewport? | «960» Пояснение: Bootstrap 5.3 defines the container's max-width as 960px for the 'lg' breakpoint, which is active at viewports with a width of 992px or greater.
Raw{"answer": 960, "explanation": "Bootstrap 5.3 defines the container's max-width as 960px for the 'lg' breakpoint, which is active at viewports with a width of 992px or greater."} | верно | 5.x container widths: 540/720/960/1140/1320 (sm–xxl); 992 → 960px. |
T24-L10 0.52 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-primary» Пояснение: In a string of conflicting CSS utilities, the last one applied to the same property in the HTML class list takes precedence, so text-primary wins over text-danger.
Raw{ ⏎ "answer": "text-primary", ⏎ "explanation": "In a string of conflicting CSS utilities, the last one applied to the same property in the HTML class list takes precedence, so text-primary wins over text-danger." ⏎ } | неверно верный: «text-danger» | Specificity ties — the later rule wins: text-danger is declared after text-primary. |
T25-L9 0.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 OrderService
{
public function __construct(
private PlaceOrder $handler,
private Db $db,
) {}
}
``` | «2» Пояснение: Domain must not depend on Application or Infrastructure, and each of the two imported dependencies violates the rule.
Raw{"answer": "2", "explanation": "Domain must not depend on Application or Infrastructure, and each of the two imported dependencies violates the rule."} | верно | Domain may depend only on Domain: PlaceOrder (Application) + Db (Infrastructure) = 2. |
T25-L10 0.46 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,
) {}
}
``` | «1» Пояснение: The class in the Domain layer depends on an Infrastructure layer dependency, which violates the rule that Infrastructure depends on Domain and Application but not the reverse.
Raw{ ⏎ "answer": "1", ⏎ "explanation": "The class in the Domain layer depends on an Infrastructure layer dependency, which violates the rule that Infrastructure depends on Domain and Application but not the reverse." ⏎ } | неверно верный: «3» | The inline FQCN \App\Infrastructure\Logger counts too: Application + Db + Logger = 3. |
T26-L10 0.55 c | DDD | What does this code output?
```php
final class Money
{
public function __construct(public readonly int $amount) {}
public function add(Money $o): Money
{
return new self($this->amount + $o->amount);
}
}
$a = new Money(10);
$c = $a->add(new Money(5));
echo $a->amount . ',' . $c->amount;
``` | «10,15» Пояснение: $a->amount is 10, and $c->amount is 10 + 5 = 15, so the output is 10,15.
Raw{"answer": "10,15", "explanation": "$a->amount is 10, and $c->amount is 10 + 5 = 15, so the output is 10,15."} | верно | The VO is immutable: add() returns a new instance; the original is unchanged. |
T26-L9 0.44 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 call throws a DomainException because only one item is present, so the item is never removed and count returns 1.
Raw{"answer": 1, "explanation": "The remove call throws a DomainException because only one item is present, so the item is never removed and count returns 1."} | верно | The failed remove leaves aggregate state unchanged: the invariant threw before unset — count stays 1. |
VC-L9 0.46 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 creates an instance of class C, calls its hi() method which returns the string 'hi', and echoes it.
Raw{ ⏎ "answer": "hi", ⏎ "explanation": "The code creates an instance of 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 0.35 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';
``` | «yes yes» Пояснение: isUninitializedLazyObject returns true before initialization and false after the property access triggers the initializer.
Raw{"answer": "yes yes", "explanation": "isUninitializedLazyObject returns true before initialization and false after the property access triggers the initializer."} | неверно верный: «yesno» | newLazyGhost (8.4): the object stays lazy until first access — reading a property initializes it and clears the flag. |
T28-L9 0.44 c | Symfony: versions | The project was upgraded from Symfony 6.4 to 8.1. What does this code output on 8.1?
```php
echo class_exists(\Symfony\Component\Security\Guard\AbstractGuardAuthenticator::class)
? 'yes' : 'no';
``` | «no» Пояснение: The Guard component and AbstractGuardAuthenticator were removed in Symfony 7.0, so the class does not exist on version 8.1.
Raw{"answer": "no", "explanation": "The Guard component and AbstractGuardAuthenticator were removed in Symfony 7.0, so the class does not exist on version 8.1."} | верно | Guard authentication was removed in Symfony 7.0 — the class is gone in 8.1. |
T28-L10 0.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\Routing\Loader\AnnotationClassLoader::class)
? 'yes' : 'no';
echo class_exists(\Symfony\Component\Routing\Loader\AttributeClassLoader::class)
? 'yes' : 'no';
``` | «noyes» Пояснение: Symfony removed the deprecated AnnotationClassLoader in 8.0, while the AttributeClassLoader is still available in 8.1.
Raw{ ⏎ "answer": "noyes", ⏎ "explanation": "Symfony removed the deprecated AnnotationClassLoader in 8.0, while the AttributeClassLoader is still available in 8.1." ⏎ } | верно | Annotation loaders were removed in 7.0; only attribute loaders remain (Annotation→Attribute). |