Пример запроса (первая клетка). System одинаковый во всех запросах прогона, user — свой вопрос для каждой клетки:
| Клетка | Тема | Утверждение | Ответ |
Результат | Обоснование |
T01-L1 4.47 c | Syntax and operators | Double-quoted and single-quoted strings are processed identically; the difference is only in speed. | «no» Пояснение: Double-quoted strings interpolate variables and interpret escape sequences (\n, \t, etc.), while single-quoted strings only recognize backslash-escaped single quotes and backslashes, so they are not processed identically.
Raw{"answer": "no", "explanation": "Double-quoted strings interpolate variables and interpret escape sequences (\\n, \\t, etc.), while single-quoted strings only recognize backslash-escaped single quotes and backslashes, so they are not processed identically."} | верно | В двойных кавычках работают интерполяция переменных и escape-последовательности, в одинарных — нет. |
T01-L2 1.67 c | Syntax and operators | The ?? operator follows isset semantics and raises no warnings for undefined variables. | «yes» Пояснение: The null coalescing operator (??) is syntactic sugar for isset($a) ? $a : $b, so it checks isset() semantics and does not raise warnings for undefined variables.
Raw{"answer": "yes", "explanation": "The null coalescing operator (??) is syntactic sugar for isset($a) ? $a : $b, so it checks isset() semantics and does not raise warnings for undefined variables."} | верно | ?? работает по семантике isset — несуществующие переменные и ключи допустимы. |
T01-L3 0.79 c | Syntax and operators | What will this print: echo 'a', 'b'; | «ab» Пояснение: In PHP, echo accepts multiple comma-separated arguments and outputs them in sequence, so 'a' and 'b' are printed as 'ab'.
Raw{"answer": "ab", "explanation": "In PHP, echo accepts multiple comma-separated arguments and outputs them in sequence, so 'a' and 'b' are printed as 'ab'."} | верно | echo принимает список аргументов: ab. |
T01-L4 1.28 c | Syntax and operators | print returns the value 1 and can be used inside an expression. | «yes» Пояснение: In PHP, print is a language construct that returns the integer 1, so it can be used in expressions (e.g., $x = print 'hello'; assigns 1 to $x).
Raw{"answer": "yes", "explanation": "In PHP, print is a language construct that returns the integer 1, so it can be used in expressions (e.g., $x = print 'hello'; assigns 1 to $x)."} | верно | print — выражение со значением 1, в отличие от echo, который значения не возвращает. |
T01-L5 1.23 c | Syntax and operators | The ?: (elvis) operator returns its left operand when it is falsy. | «no» Пояснение: The Elvis operator (?:) returns the left operand when it is truthy, and the right operand (default) when it is falsy.
Raw{"answer": "no", "explanation": "The Elvis operator (?:) returns the left operand when it is truthy, and the right operand (default) when it is falsy."} | верно | Наоборот: $a ?: $b возвращает $a, если он истинный, иначе $b. |
T01-L6 4.59 c | Syntax and operators | In PHP 8, the concatenation operator (.) has lower precedence than addition and subtraction. | «no» Пояснение: In PHP, the concatenation operator (.) is at the same precedence level as addition (+) and subtraction (-), all in the 'additive' category, so it does not have lower precedence than them.
Raw{"answer": "no", "explanation": "In PHP, the concatenation operator (.) is at the same precedence level as addition (+) and subtraction (-), all in the 'additive' category, so it does not have lower precedence than them."} | неверно верный: «yes» | С PHP 8 (RFC concat precedence) '.' имеет приоритет ниже арифметики: 'сумма: ' . 2 + 3 → 'сумма: 5' (в PHP 7 было иначе). |
T01-L7 1.02 c | Syntax and operators | The expression 2 ** 3 ** 2 in PHP evaluates as (2 ** 3) ** 2, that is, 64. | «no» Пояснение: The ** operator in PHP is right-associative, so 2 ** 3 ** 2 evaluates as 2 ** (3 ** 2) = 2 ** 9 = 512, not 64.
Raw{"answer": "no", "explanation": "The ** operator in PHP is right-associative, so 2 ** 3 ** 2 evaluates as 2 ** (3 ** 2) = 2 ** 9 = 512, not 64."} | верно | ** право-ассоциативен: 2 ** (3 ** 2) = 2 ** 9 = 512. |
T01-L8 2.3 c | Syntax and operators | What string will this print: echo 'sum: ' . 2 + 3; (PHP 8)? | «3» Пояснение: Concatenation (.) has higher precedence than addition (+), so it parses as ('sum: ' . 2) + 3, which becomes 'sum: 2' + 3, and since 'sum: 2' casts to 0, the result is 3.
Raw{"answer": 3, "explanation": "Concatenation (.) has higher precedence than addition (+), so it parses as ('sum: ' . 2) + 3, which becomes 'sum: 2' + 3, and since 'sum: 2' casts to 0, the result is 3."} | неверно верный: «sum: 5» | Парная к verify-клетке про приоритет: 'сумма: 5'. |
T02-L1 1.93 c | Types and comparisons | With strict comparison (===), arrays are considered equal regardless of element order. | «no» Пояснение: With ===, arrays must have the same key/value pairs in the same order and of the same type; order matters with strict comparison.
Raw{"answer": "no", "explanation": "With ===, arrays must have the same key/value pairs in the same order and of the same type; order matters with strict comparison."} | верно | === для массивов требует совпадения и значений, и их порядка. |
T02-L2 1.19 c | Types and comparisons | The comparison 0 == false returns false because it is a strict comparison. | «no» Пояснение: 0 == false is a loose (not strict) comparison, and it actually returns true, not false.
Raw{"answer": "no", "explanation": "0 == false is a loose (not strict) comparison, and it actually returns true, not false."} | верно | Наоборот: == — нестрогое сравнение и возвращает true; строгое — это === (0 === false → false). |
T02-L3 1.83 c | Types and comparisons | In PHP 8, the expression "abc" == 0 returns true. | «no» Пояснение: In PHP 8, when a non-numeric string like 'abc' is compared with an integer using ==, the integer is cast to a string, so 'abc' == '0' evaluates to false.
Raw{"answer": "no", "explanation": "In PHP 8, when a non-numeric string like 'abc' is compared with an integer using ==, the integer is cast to a string, so 'abc' == '0' evaluates to false."} | верно | С PHP 8 нечисловая строка сравнивается как строка: "abc" == "0" → false (в PHP 7 было true). |
T02-L4 1.1 c | Types and comparisons | Under loose comparison, null equals 0, the empty string, and false at the same time. | «yes» Пояснение: In PHP, under loose comparison (==), null is indeed equal to 0, the empty string '', and false, as all these values are considered 'falsy' and compare equal to null.
Raw{"answer": "yes", "explanation": "In PHP, under loose comparison (==), null is indeed equal to 0, the empty string '', and false, as all these values are considered 'falsy' and compare equal to null."} | верно | null == 0, null == "" и null == false — все true. |
T02-L5 0.91 c | Types and comparisons | What does the expression (int) '42abc' return? | «42» Пояснение: Casting a string to int in PHP reads leading numeric characters until a non-numeric character is encountered, so '42abc' becomes 42.
Raw{"answer": 42, "explanation": "Casting a string to int in PHP reads leading numeric characters until a non-numeric character is encountered, so '42abc' becomes 42."} | верно | Ведущая числовая часть: 42, без ошибок и warning. |
T02-L6 0.8 c | Types and comparisons | What does the expression '5' + 5 return? | «10» Пояснение: PHP coerces the numeric string '5' to an integer, so the expression evaluates to the integer 10.
Raw{"answer": 10, "explanation": "PHP coerces the numeric string '5' to an integer, so the expression evaluates to the integer 10."} | верно | Числовая строка приводится: int 10. |
T02-L7 1.65 c | Types and comparisons | When cast to string, false becomes "0". | «no» Пояснение: In PHP, casting false to a string results in an empty string "", not "0"; only the integer 0 casts to "0".
Raw{"answer": "no", "explanation": "In PHP, casting false to a string results in an empty string \"\", not \"0\"; only the integer 0 casts to \"0\"."} | верно | false → "", true → "1". |
T02-L8 1.14 c | Types and comparisons | The comparison 0.1 + 0.2 === 0.3 returns false. | «yes» Пояснение: Due to floating-point precision, 0.1 + 0.2 evaluates to 0.30000000000000004, which is not strictly equal to 0.3.
Raw{"answer": "yes", "explanation": "Due to floating-point precision, 0.1 + 0.2 evaluates to 0.30000000000000004, which is not strictly equal to 0.3."} | верно | Двоичная погрешность float: 0.1 + 0.2 = 0.30000000000000004. |
T03-L1 1.51 c | Strings | strrev() correctly reverses a UTF-8 string. | «no» Пояснение: strrev() reverses a string byte by byte, which breaks multi-byte UTF-8 characters into invalid sequences rather than reversing whole characters.
Raw{"answer": "no", "explanation": "strrev() reverses a string byte by byte, which breaks multi-byte UTF-8 characters into invalid sequences rather than reversing whole characters."} | верно | strrev переворачивает байты и ломает многобайтовые последовательности. |
T03-L2 0.65 c | Strings | str_contains('Hello world', 'world') returns true. | «yes» Пояснение: str_contains checks if the needle 'world' is found within the haystack 'Hello world', which it is, so it returns true.
Raw{"answer": "yes", "explanation": "str_contains checks if the needle 'world' is found within the haystack 'Hello world', which it is, so it returns true."} | верно | str_contains с PHP 8.0 проверяет вхождение подстроки. |
T03-L3 0.92 c | Strings | str_pad() can pad a string on the right side only. | «no» Пояснение: str_pad() can pad on the right (STR_PAD_RIGHT), left (STR_PAD_LEFT), or both sides (STR_PAD_BOTH).
Raw{"answer": "no", "explanation": "str_pad() can pad on the right (STR_PAD_RIGHT), left (STR_PAD_LEFT), or both sides (STR_PAD_BOTH)."} | верно | STR_PAD_LEFT / STR_PAD_BOTH меняют сторону дополнения. |
T03-L4 1.16 c | Strings | By default trim() strips only spaces, leaving tabs and newlines intact. | «no» Пояснение: By default, trim() strips spaces, tabs, newlines, carriage returns, null bytes, and vertical tabs (" \t\n\r\0\x0B"), not just spaces.
Raw{"answer": "no", "explanation": "By default, trim() strips spaces, tabs, newlines, carriage returns, null bytes, and vertical tabs (\" \\t\\n\\r\\0\\x0B\"), not just spaces."} | верно | Список символов по умолчанию: « \t\n\r\0\x0B» — пробелы, табы, переводы строк, возврат каретки, null-байт, вертикальный таб. Проверено php -r. |
T03-L5 1.05 c | Strings | How many BYTES does strlen('héllo') return for a UTF-8 string? | «6» Пояснение: strlen counts bytes: 'h'(1) + 'é'(2 in UTF-8) + 'l'(1) + 'l'(1) + 'o'(1) = 6 bytes.
Raw{"answer": 6, "explanation": "strlen counts bytes: 'h'(1) + 'é'(2 in UTF-8) + 'l'(1) + 'l'(1) + 'o'(1) = 6 bytes."} | верно | 6 букв по 2 байта: 12. |
T03-L6 0.81 c | Strings | What does substr('abcdef', -3) return? | «def» Пояснение: substr with a negative start of -3 begins 3 characters from the end of 'abcdef', returning 'def'.
Raw{"answer": "def", "explanation": "substr with a negative start of -3 begins 3 characters from the end of 'abcdef', returning 'def'."} | верно | Отрицательное смещение — с конца: def. |
T03-L7 0.9 c | Strings | ucfirst() modifies the string passed to it in place. | «no» Пояснение: ucfirst() returns a new string with the first character uppercased; it does not modify the original string in place since PHP strings are passed by value by default.
Raw{"answer": "no", "explanation": "ucfirst() returns a new string with the first character uppercased; it does not modify the original string in place since PHP strings are passed by value by default."} | верно | Строки неизменяемы; ucfirst возвращает новую строку. |
T03-L8 1.55 c | Strings | Variable interpolation works in heredoc but not in nowdoc. | «yes» Пояснение: In PHP, heredoc (<<<EOF) supports variable interpolation while nowdoc (<<<'EOF') treats content like a single-quoted string, so no variables are interpolated.
Raw{"answer": "yes", "explanation": "In PHP, heredoc (<<<EOF) supports variable interpolation while nowdoc (<<<'EOF') treats content like a single-quoted string, so no variables are interpolated."} | верно | Nowdoc — «одинарные кавычки» в тройном синтаксисе: текст как есть. |
T04-L1 1.05 c | Arrays | The sort() function preserves the key-to-value association of the array. | «no» Пояснение: The sort() function re-indexes the array numerically starting from 0, discarding original keys; use asort() to preserve key-value associations.
Raw{"answer": "no", "explanation": "The sort() function re-indexes the array numerically starting from 0, discarding original keys; use asort() to preserve key-value associations."} | верно | sort перенумеровывает ключи; связь сохраняет asort. |
T04-L2 0.89 c | Arrays | The string key '5' in an array is stored as the integer 5. | «yes» Пояснение: PHP automatically converts string keys that are valid integers (like '5') to integer keys (5) in arrays.
Raw{"answer": "yes", "explanation": "PHP automatically converts string keys that are valid integers (like '5') to integer keys (5) in arrays."} | верно | Каноничные десятичные строковые ключи приводятся к int. |
T04-L3 1.06 c | Arrays | The in_array() function uses strict comparison (===) by default. | «no» Пояснение: in_array() has a $strict parameter that defaults to false, meaning it uses loose comparison (==) by default.
Raw{"answer": "no", "explanation": "in_array() has a $strict parameter that defaults to false, meaning it uses loose comparison (==) by default."} | верно | По умолчанию сравнение нестрогое; строгое — третий аргумент true. |
T04-L4 1.02 c | Arrays | Without a callback, array_filter() removes all "empty" (falsy) elements from the array. | «yes» Пояснение: Without a callback, array_filter() removes all elements that evaluate to false (0, '', null, false, '0', 0.0, empty array).
Raw{"answer": "yes", "explanation": "Without a callback, array_filter() removes all elements that evaluate to false (0, '', null, false, '0', 0.0, empty array)."} | верно | Убирает 0, "", null, false и пустые массивы. |
T04-L5 1.31 c | Arrays | By default, array_slice() preserves the original numeric keys of the array. | «no» Пояснение: By default, the $preserve_keys parameter of array_slice() is false, meaning keys are reindexed sequentially starting from 0.
Raw{"answer": "no", "explanation": "By default, the $preserve_keys parameter of array_slice() is false, meaning keys are reindexed sequentially starting from 0."} | верно | По умолчанию ключи перенумеровываются; сохранение — preserve_keys = true. |
T04-L6 1.02 c | Arrays | What does array_slice([10, 20, 30, 40], 1, 2) return? | «[20, 30]» Пояснение: array_slice extracts 2 elements starting at index 1 from the array, which are 20 and 30.
Raw{"answer": "[20, 30]", "explanation": "array_slice extracts 2 elements starting at index 1 from the array, which are 20 and 30."} | верно | [20,30]; ключи перенумеровываются. |
T04-L7 1.48 c | Arrays | How many elements will count(['a' => 1] + ['a' => 9, 'b' => 2]) return? | «2» Пояснение: The array union operator (+) keeps the left array's 'a' => 1 and only adds 'b' => 2 from the right array, since 'a' already exists in the left, resulting in 2 elements.
Raw{"answer": 2, "explanation": "The array union operator (+) keeps the left array's 'a' => 1 and only adds 'b' => 2 from the right array, since 'a' already exists in the left, resulting in 2 elements."} | верно | Оператор + : по ключу 'a' побеждает левый; итого 2. |
T04-L8 2.76 c | Arrays | Since PHP 8.1, the spread operator [...$a, ...$b] supports arrays with string keys. | «yes» Пояснение: PHP 8.1 introduced array unpacking (spread operator) within array expressions, and unlike the earlier function-argument spread, it supports both integer and string keys.
Raw{"answer": "yes", "explanation": "PHP 8.1 introduced array unpacking (spread operator) within array expressions, and unlike the earlier function-argument spread, it supports both integer and string keys."} | верно | В 8.0 — только числовые ключи; 8.1 снял ограничение. |
T05-L1 2.85 c | Functions and closures | Named arguments cannot be combined with argument unpacking ...$args in a single call. | «no» Пояснение: Named arguments can be combined with argument unpacking (...$args) in a single call, provided the named argument appears before the spread expression (e.g., foo(a: 1, ...$args) is valid in PHP 8+).
Raw{"answer": "no", "explanation": "Named arguments can be combined with argument unpacking (...$args) in a single call, provided the named argument appears before the spread expression (e.g., foo(a: 1, ...$args) is valid in PHP 8+)."} | верно | Можно: f(...$args, имя: значение). Нельзя только позиционный аргумент после распаковки. |
T05-L2 1.6 c | Functions and closures | An anonymous function without use sees variables from the outer scope. | «no» Пояснение: In PHP, anonymous functions (closures) do not automatically inherit variables from the enclosing scope; you must explicitly use the 'use' keyword to import them.
Raw{"answer": "no", "explanation": "In PHP, anonymous functions (closures) do not automatically inherit variables from the enclosing scope; you must explicitly use the 'use' keyword to import them."} | верно | Без use внешние переменные недоступны; авто-захват только у fn. |
T05-L3 0.9 c | Functions and closures | What will func_num_args() return inside function f($a) { return func_num_args(); } when called as f(1, 2, 3)? | «3» Пояснение: func_num_args() returns the number of arguments actually passed to the function call, which is 3 (1, 2, 3), regardless of the declared parameter count.
Raw{"answer": 3, "explanation": "func_num_args() returns the number of arguments actually passed to the function call, which is 3 (1, 2, 3), regardless of the declared parameter count."} | верно | Считает переданные аргументы: 3. |
T05-L4 3.02 c | Functions and closures | The body of an arrow function fn may consist of several expressions in curly braces. | «no» Пояснение: An arrow function (fn) in PHP has a single expression as its body (using =>), not multiple expressions in curly braces; curly braces are used for regular closures (function keyword).
Raw{"answer": "no", "explanation": "An arrow function (fn) in PHP has a single expression as its body (using =>), not multiple expressions in curly braces; curly braces are used for regular closures (function keyword)."} | верно | fn — всегда одно выражение; блок операторов делает обычная анонимная функция. |
T05-L5 2.25 c | Functions and closures | An arrow function fn captures outer variables by reference (lazily, at use time). | «no» Пояснение: PHP arrow functions (fn) automatically capture outer variables by value at creation time, not by reference at use time.
Raw{"answer": "no", "explanation": "PHP arrow functions (fn) automatically capture outer variables by value at creation time, not by reference at use time."} | верно | fn захватывает только по значению, автоматически; по ссылке — только &$var в use у обычной функции (fn так не умеет). |
T05-L6 1.59 c | Functions and closures | A closure declared as static function () {} does not capture $this. | «yes» Пояснение: In PHP, declaring a closure as static prevents it from automatically capturing $this, unlike a non-static closure defined within a class context.
Raw{"answer": "yes", "explanation": "In PHP, declaring a closure as static prevents it from automatically capturing $this, unlike a non-static closure defined within a class context."} | верно | static-замыкание отвязано от объекта: $this внутри недоступен. |
T05-L7 1.14 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 variable by value at the time the closure is defined, so the closure retains $x = 5 even after $x is reassigned to 7.
Raw{"answer": 5, "explanation": "The 'use' keyword captures the variable by value at the time the closure is defined, so the closure retains $x = 5 even after $x is reassigned to 7."} | верно | use захватывает по значению в момент создания: 5. |
T05-L8 1.09 c | Functions and closures | In weak typing mode (without strict_types), passing the string "5" to an int parameter is allowed. | «yes» Пояснение: In coercive typing mode (without strict_types=1), PHP automatically coerces the numeric string "5" to the integer 5 when passed to an int parameter.
Raw{"answer": "yes", "explanation": "In coercive typing mode (without strict_types=1), PHP automatically coerces the numeric string \"5\" to the integer 5 when passed to an int parameter."} | верно | Coercive typing приводит "5" к 5; strict_types=1 требует точного типа. |
T06-L1 0.87 c | OOP: classes and inheritance | PHP supports constructor property promotion: public function __construct(private int $x) {}. | «yes» Пояснение: Constructor property promotion was introduced in PHP 8.0, allowing visibility modifiers and types to be declared directly on constructor parameters to automatically create and assign the property.
Raw{"answer": "yes", "explanation": "Constructor property promotion was introduced in PHP 8.0, allowing visibility modifiers and types to be declared directly on constructor parameters to automatically create and assign the property."} | верно | С PHP 8.0 параметр с модификатором создаёт свойство и присваивание. |
T06-L2 0.52 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 subclasses.
Raw{"answer": "final", "explanation": "In PHP, the 'final' keyword prevents a method from being overridden in subclasses."} | верно | final. |
T06-L3 0.72 c | OOP: classes and inheritance | A method declared final cannot be overridden in a subclass. | «yes» Пояснение: In PHP, declaring a method as final prevents any subclass from overriding it; attempting to do so results in a fatal error.
Raw{"answer": "yes", "explanation": "In PHP, declaring a method as final prevents any subclass from overriding it; attempting to do so results in a fatal error."} | верно | final запрещает переопределение метода и наследование класса. |
T06-L4 0.76 c | OOP: classes and inheritance | Parent properties with private visibility are accessible in a subclass. | «no» Пояснение: In PHP, private properties are only accessible within the class that declares them, not in subclasses; only public and protected properties are accessible in a subclass.
Raw{"answer": "no", "explanation": "In PHP, private properties are only accessible within the class that declares them, not in subclasses; only public and protected properties are accessible in a subclass."} | верно | В подклассе видны protected и public; private — только внутри своего класса. |
T06-L5 4.4 c | OOP: classes and inheritance | What does get_class(new class {}) return? Answer with the part of the name before the NUL byte (without the file path). | «class@anonymous» Пояснение: In PHP, anonymous classes created with `new class {}` receive a generated name prefixed with `class@anonymous`, which is the portion before the NUL byte/file path identifier.
Raw{"answer": "class@anonymous", "explanation": "In PHP, anonymous classes created with `new class {}` receive a generated name prefixed with `class@anonymous`, which is the portion before the NUL byte/file path identifier."} | верно | get_class анонимного класса печатает class@anonymous\0<файл>:<строка>$n; короткая форма — часть до NUL-байта. Проверено php -r (hex). |
T06-L6 1.74 c | OOP: classes and inheritance | A private parent method is not part of the inheritance contract: a child may declare a method with the same name and any visibility. | «yes» Пояснение: In PHP, private methods are invisible to child classes, so a child can redeclare a method with the same name at any visibility without violating the inheritance contract.
Raw{"answer": "yes", "explanation": "In PHP, private methods are invisible to child classes, so a child can redeclare a method with the same name at any visibility without violating the inheritance contract."} | верно | private-члены не наследуются — правила совместимости подписей не действуют. |
T06-L7 2.24 c | OOP: classes and inheritance | The magic method __get() is called only for non-existent properties. | «no» Пояснение: __get() is called when reading from an inaccessible (private or protected) property, not for non-existent properties.
Raw{"answer": "no", "explanation": "__get() is called when reading from an inaccessible (private or protected) property, not for non-existent properties."} | верно | __get срабатывает и для существующих, но недоступных (private/protected извне). |
T06-L8 2.36 c | OOP: classes and inheritance | What does reassigning a readonly property throw — Exception or Error? | «error» Пояснение: Reassigning a readonly property in PHP throws a TypeError, which extends Error (not Exception).
Raw{"answer": "Error", "explanation": "Reassigning a readonly property in PHP throws a TypeError, which extends Error (not Exception)."} | верно | Error (readonly с 8.1); оговорка: в __clone() переинициализация допустима (8.3+). |
T07-L1 0.67 c | Interfaces, traits, enum | An interface can declare constants. | «yes» Пояснение: PHP interfaces can declare public constants, which are inherited by implementing classes.
Raw{"answer": "yes", "explanation": "PHP interfaces can declare public constants, which are inherited by implementing classes."} | верно | Константы интерфейса наследуются реализациями. |
T07-L2 0.54 c | Interfaces, traits, enum | Which operator checks whether an object is an instance of a class or interface? | «instanceof» Пояснение: In PHP, the instanceof operator is used to check whether an object is an instance of a specific class or implements a specific interface.
Raw{"answer": "instanceof", "explanation": "In PHP, the instanceof operator is used to check whether an object is an instance of a specific class or implements a specific interface."} | верно | instanceof. |
T07-L3 5.25 c | Interfaces, traits, enum | An interface can declare static methods. | «yes» Пояснение: Since PHP 8.1, interfaces are allowed to declare static methods (which do not need to be implemented by the implementing class).
Raw{"answer": "yes", "explanation": "Since PHP 8.1, interfaces are allowed to declare static methods (which do not need to be implemented by the implementing class)."} | верно | Реализация обязана дать статический метод с той же сигнатурой. |
T07-L4 0.88 c | Interfaces, traits, enum | The instanceof operator only checks class inheritance: it ignores interfaces. | «no» Пояснение: In PHP, the instanceof operator checks both class inheritance and interface implementation, so it does not ignore interfaces.
Raw{"answer": "no", "explanation": "In PHP, the instanceof operator checks both class inheritance and interface implementation, so it does not ignore interfaces."} | верно | instanceof возвращает true и для интерфейсов объекта. |
T07-L5 1.61 c | Interfaces, traits, enum | An interface method may have a default implementation, like a trait method. | «no» Пояснение: In PHP, interface methods are always abstract (no body); only traits (and classes) can provide a default method implementation.
Raw{"answer": "no", "explanation": "In PHP, interface methods are always abstract (no body); only traits (and classes) can provide a default method implementation."} | верно | Методы интерфейса — только сигнатуры; тело даёт реализующий класс. |
T07-L6 0.95 c | Interfaces, traits, enum | An abstract method in an abstract class may have protected visibility. | «yes» Пояснение: In PHP, abstract methods in an abstract class can be declared as public, protected, or private (since PHP 7.1).
Raw{"answer": "yes", "explanation": "In PHP, abstract methods in an abstract class can be declared as public, protected, or private (since PHP 7.1)."} | верно | В абстрактном классе — любая видимость; в интерфейсе — только public. |
T07-L7 0.51 c | Interfaces, traits, enum | How many elements will Foo::cases() return for enum Foo { case A; case B; case C; }? | «3» Пояснение: The enum Foo declares three cases (A, B, C), so Foo::cases() returns an array of 3 elements.
Raw{"answer": 3, "explanation": "The enum Foo declares three cases (A, B, C), so Foo::cases() returns an array of 3 elements."} | верно | Статический метод cases(): 3. |
T07-L8 1.37 c | Interfaces, traits, enum | A trait can declare constants. | «yes» Пояснение: Since PHP 8.2, traits are allowed to declare constants, which are then inherited by any class that uses the trait.
Raw{"answer": "yes", "explanation": "Since PHP 8.2, traits are allowed to declare constants, which are then inherited by any class that uses the trait."} | верно | С PHP 8.2 трейты могут объявлять константы (RFC constants_in_traits); до 8.2 — нет. |
T08-L1 0.7 c | Exceptions and errors | The Throwable interface is a common ancestor of both Exception and Error. | «yes» Пояснение: In PHP, both Exception and Error implement the Throwable interface, making it their common ancestor.
Raw{"answer": "yes", "explanation": "In PHP, both Exception and Error implement the Throwable interface, making it their common ancestor."} | верно | Иерархия с PHP 7: Throwable → Exception и Throwable → Error. |
T08-L2 1.21 c | Exceptions and errors | A catch (Exception $e) block will also catch TypeError, because TypeError ultimately inherits from Exception. | «no» Пояснение: TypeError extends Error, not Exception; they are siblings under the Throwable interface, so catch(Exception) does not catch TypeError.
Raw{"answer": "no", "explanation": "TypeError extends Error, not Exception; they are siblings under the Throwable interface, so catch(Exception) does not catch TypeError."} | верно | TypeError наследуется от Error; catch (Exception) его не ловит. |
T08-L3 1.32 c | Exceptions and errors | The @ operator suppresses exceptions too. | «no» Пояснение: The @ operator only suppresses errors (warnings, notices, etc.) via error_reporting; exceptions are still thrown and propagated normally.
Raw{"answer": "no", "explanation": "The @ operator only suppresses errors (warnings, notices, etc.) via error_reporting; exceptions are still thrown and propagated normally."} | верно | @ глушит диагностику (warnings/notices), исключения не перехватывает. |
T08-L4 1.35 c | Exceptions and errors | What error class does intdiv(5, 0) throw? | «divisionbyzeroerror» Пояснение: In PHP 8.0+, intdiv(5, 0) throws a DivisionByZeroError, which extends ArithmeticError which extends Error.
Raw{"answer": "DivisionByZeroError", "explanation": "In PHP 8.0+, intdiv(5, 0) throws a DivisionByZeroError, which extends ArithmeticError which extends Error."} | верно | DivisionByZeroError (иерархия Error, не Exception); php-грейдер объективен. |
T08-L5 1.17 c | Exceptions and errors | The finally block runs only if the exception was caught by a catch block. | «no» Пояснение: The finally block in PHP executes regardless of whether an exception was thrown, caught, or neither; it always runs after the try/catch blocks.
Raw{"answer": "no", "explanation": "The finally block in PHP executes regardless of whether an exception was thrown, caught, or neither; it always runs after the try/catch blocks."} | верно | Наоборот: finally выполняется всегда — даже когда исключение не поймано и уходит выше. Проверено php -r. |
T08-L6 1.83 c | Exceptions and errors | An exception thrown inside a finally block has no effect on the result of the try block. | «no» Пояснение: An exception thrown in a finally block replaces (masks) any exception that was about to propagate from the try/catch block, so it does affect the final outcome.
Raw{"answer": "no", "explanation": "An exception thrown in a finally block replaces (masks) any exception that was about to propagate from the try/catch block, so it does affect the final outcome."} | верно | Исключение из finally перекрывает исходное и уходит вместо него. |
T08-L7 1.26 c | Exceptions and errors | What does the expression (bool) new Exception('x') return? | «yes» Пояснение: In PHP, casting any object to bool always yields true.
Raw{"answer": "yes", "explanation": "In PHP, casting any object to bool always yields true."} | верно | Любой объект при приведении к bool — true. Формы ответа: true или да. |
T08-L8 1.29 c | Exceptions and errors | Functions registered via register_shutdown_function() run when exit is called. | «yes» Пояснение: Shutdown functions registered with register_shutdown_function() are executed whenever the script terminates, including when exit or die is called.
Raw{"answer": "yes", "explanation": "Shutdown functions registered with register_shutdown_function() are executed whenever the script terminates, including when exit or die is called."} | верно | exit завершает скрипт, но shutdown-функции отрабатывают. |
T09-L1 1.3 c | Namespaces and autoloading | The use App\Service\Mailer; statement itself loads the class file. | «no» Пояснение: The 'use' statement only registers a namespace alias at compile time; the class file is actually loaded (via autoload) only when the class is first referenced (instantiated, static call, etc.).
Raw{"answer": "no", "explanation": "The 'use' statement only registers a namespace alias at compile time; the class file is actually loaded (via autoload) only when the class is first referenced (instantiated, static call, etc.)."} | верно | use — псевдоним на этапе компиляции; файл грузит автозагрузчик при первом обращении. |
T09-L2 0.73 c | Namespaces and autoloading | What follows use to import a function (not a class): the word function or const? | «function» Пояснение: In PHP, to import a function you use 'use function', while 'use const' is for importing constants.
Raw{"answer": "function", "explanation": "In PHP, to import a function you use 'use function', while 'use const' is for importing constants."} | верно | use function ...; (и use const для констант). |
T09-L3 2.37 c | Namespaces and autoloading | Into which file (path from src/) does the PSR-4 mapping "App\ → src/" place the class App\Controller\Api\UserController? | «src/controller/api/usercontroller.php» Пояснение: PSR-4 strips the 'App\' prefix, converts remaining namespace separators to directory slashes, and appends '.php', yielding src/Controller/Api/UserController.php.
Raw{"answer": "src/Controller/Api/UserController.php", "explanation": "PSR-4 strips the 'App\\' prefix, converts remaining namespace separators to directory slashes, and appends '.php', yielding src/Controller/Api/UserController.php."} | верно | Остаток имени после префикса, \ → /. |
T09-L4 1.14 c | Namespaces and autoloading | Including vendor/autoload.php registers autoloaders via spl_autoload_register(). | «yes» Пояснение: Composer's vendor/autoload.php ultimately calls spl_autoload_register() to register the Composer class autoloader with PHP's SPL autoload stack.
Raw{"answer": "yes", "explanation": "Composer's vendor/autoload.php ultimately calls spl_autoload_register() to register the Composer class autoloader with PHP's SPL autoload stack."} | верно | Composer ставит автозагрузчик именно на spl_autoload_register. |
T09-L5 0.81 c | Namespaces and autoloading | The magic constant __NAMESPACE__ contains the name of the current namespace. | «yes» Пояснение: __NAMESPACE__ is a PHP magic constant that returns the name of the current namespace (or an empty string if in the global namespace).
Raw{"answer": "yes", "explanation": "__NAMESPACE__ is a PHP magic constant that returns the name of the current namespace (or an empty string if in the global namespace)."} | верно | В корневом пространстве — пустая строка. |
T09-L6 1.76 c | Namespaces and autoloading | An unqualified class name (without a leading \) in new is resolved from the global root. | «no» Пояснение: An unqualified class name in `new` is resolved relative to the current namespace, not the global root; only a name with a leading backslash (e.g., `\Foo`) is resolved from the global namespace.
Raw{"answer": "no", "explanation": "An unqualified class name in `new` is resolved relative to the current namespace, not the global root; only a name with a leading backslash (e.g., `\\Foo`) is resolved from the global namespace."} | верно | Резолвится относительно текущего namespace (с учётом импортов). |
T09-L7 1.29 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» Пояснение: Under the PSR-4 mapping App\ → src/, the remaining namespace Model\User is converted to the relative path Model/User.php, giving src/Model/User.php.
Raw{"answer": "yes", "explanation": "Under the PSR-4 mapping App\\ → src/, the remaining namespace Model\\User is converted to the relative path Model/User.php, giving src/Model/User.php."} | верно | Остаток имени после префикса переносится в путь как есть. |
T09-L8 1.35 c | Namespaces and autoloading | A use statement may be written inside a function body — the import then applies to that function only. | «yes» Пояснение: PHP allows `use` statements inside a function (or any block), and the alias applies only within that scope.
Raw{"answer": "yes", "explanation": "PHP allows `use` statements inside a function (or any block), and the alias applies only within that scope."} | неверно верный: «no» | use внутри тела функции — parse error; импорты файловые и компиляционные. |
T10-L1 1.25 c | References and scope | Arrays are copied on assignment rather than passed by reference. | «yes» Пояснение: In PHP, arrays use value semantics: assigning an array to a new variable creates a copy (with a Copy-on-Write optimization internally), not a reference.
Raw{"answer": "yes", "explanation": "In PHP, arrays use value semantics: assigning an array to a new variable creates a copy (with a Copy-on-Write optimization internally), not a reference."} | верно | Присваивание массива — копия (в движке — copy-on-write). |
T10-L2 1.1 c | References and scope | What will this print: $a = [1, 2]; $b = $a; $b[] = 3; echo count($a); | «2» Пояснение: PHP arrays are assigned by value, so modifying $b after the assignment does not affect $a, which still has 2 elements.
Raw{"answer": 2, "explanation": "PHP arrays are assigned by value, so modifying $b after the assignment does not affect $a, which still has 2 elements."} | верно | Присваивание — копия: в $a по-прежнему 2 элемента. |
T10-L3 0.96 c | References and scope | Inside a function, user-defined global variables are inaccessible without global, $GLOBALS, or passing them as parameters. | «yes» Пояснение: In PHP, variables defined in the global scope are not accessible inside a function unless explicitly imported via global, $GLOBALS, or passed as parameters.
Raw{"answer": "yes", "explanation": "In PHP, variables defined in the global scope are not accessible inside a function unless explicitly imported via global, $GLOBALS, or passed as parameters."} | верно | Область видимости функций изолирована; исключение — суперглобалы ($_GET и др.). |
T10-L4 1.41 c | References and scope | unset($GLOBALS['x']) inside a function removes the global variable only for that function. | «no» Пояснение: unset($GLOBALS['x']) removes the variable from the global scope entirely, not just locally within that function; $GLOBALS directly references the global symbol table.
Raw{"answer": "no", "explanation": "unset($GLOBALS['x']) removes the variable from the global scope entirely, not just locally within that function; $GLOBALS directly references the global symbol table."} | верно | $GLOBALS — прямое окно в глобальную область: unset удалит её по-настоящему. |
T10-L5 0.67 c | References and scope | What will this print: function inc(&$x) { $x++; } $n = 5; inc($n); echo $n; | «6» Пояснение: The function increments $x by reference, so $n is modified from 5 to 6.
Raw{"answer": 6, "explanation": "The function increments $x by reference, so $n is modified from 5 to 6."} | верно | Ссылка меняет оригинал: 6. |
T10-L6 2.73 c | References and scope | A foreach over an array (by value) works with the "live" array: changes to the array inside the loop are visible in the same pass. | «no» Пояснение: A foreach by value iterates over a copy of the array, so modifications to the original array (adding/removing/changing elements) are not visible during the current pass.
Raw{"answer": "no", "explanation": "A foreach by value iterates over a copy of the array, so modifications to the original array (adding/removing/changing elements) are not visible during the current pass."} | верно | По значению foreach итерирует копию-снимок. |
T10-L7 1.14 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, so all instances share the same copy and changes in one instance are visible in all others.
Raw{"answer": "no", "explanation": "Static properties belong to the class itself, so all instances share the same copy and changes in one instance are visible in all others."} | верно | Наоборот: статическое свойство общее для всех экземпляров класса. Проверено php -r. |
T10-L8 1.08 c | References and scope | An array can have a boolean key true, and it will be stored as bool. | «no» Пояснение: In PHP, a boolean key `true` in an array is cast to the integer `1`, not stored as a bool.
Raw{"answer": "no", "explanation": "In PHP, a boolean key `true` in an array is cast to the integer `1`, not stored as a bool."} | верно | Булев ключ приводится к int: true → 1, false → 0. |
T11-L1 1.32 c | Generators, iterators, SPL | Inside a generator, return with a value can be used, and it becomes available via $gen->getReturn(). | «yes» Пояснение: In PHP generators, a return statement with a value is allowed, and that value can be retrieved after the generator is exhausted by calling $gen->getReturn().
Raw{"answer": "yes", "explanation": "In PHP generators, a return statement with a value is allowed, and that value can be retrieved after the generator is exhausted by calling $gen->getReturn()."} | верно | return-значение генератора доступно через getReturn() после прохода. |
T11-L2 2.57 c | Generators, iterators, SPL | A fully consumed generator can be rewound with rewind() and traversed again. | «no» Пояснение: Once a generator is fully consumed (closed), calling rewind() throws a LogicException; it can only be rewound if it has not yet been fully iterated.
Raw{"answer": "no", "explanation": "Once a generator is fully consumed (closed), calling rewind() throws a LogicException; it can only be rewound if it has not yet been fully iterated."} | верно | Генератор одноразовый: rewind после начала итерации бросает Exception. |
T11-L3 2.74 c | Generators, iterators, SPL | The yield from construct delegates traversal to another generator or iterable. | «yes» Пояснение: The yield from construct (in Python) does delegate iteration to another iterable or generator, yielding each item in turn.
Raw{"answer": "yes", "explanation": "The yield from construct (in Python) does delegate iteration to another iterable or generator, yielding each item in turn."} | верно | yield from проксирует значения, ключи и return-значение внутреннего генератора. |
T11-L4 1.61 c | Generators, iterators, SPL | What does get_class(g()) return for function g() { yield 1; }? | «generator» Пояснение: Calling a generator function returns a Generator object, and get_class() on that object returns the string 'Generator'.
Raw{"answer": "Generator", "explanation": "Calling a generator function returns a Generator object, and get_class() on that object returns the string 'Generator'."} | верно | Функция с yield возвращает Generator. |
T11-L5 1.22 c | Generators, iterators, SPL | How many elements will count(iterator_to_array((function () { yield from [1, 2, 3]; })())) return? | «3» Пояснение: The generator yields three values (1, 2, 3), iterator_to_array converts them into an array of 3 elements, and count returns 3.
Raw{"answer": 3, "explanation": "The generator yields three values (1, 2, 3), iterator_to_array converts them into an array of 3 elements, and count returns 3."} | верно | yield from делегирует все 3 элемента. |
T11-L6 0.65 c | Generators, iterators, SPL | The SplStack class implements a FIFO queue. | «no» Пояснение: SplStack implements a LIFO (Last In, First Out) stack, while SplQueue is the class that implements a FIFO queue.
Raw{"answer": "no", "explanation": "SplStack implements a LIFO (Last In, First Out) stack, while SplQueue is the class that implements a FIFO queue."} | верно | SplStack — стек LIFO; очередь FIFO — SplQueue. |
T11-L7 0.92 c | Generators, iterators, SPL | ArrayIterator allows wrapping an array and traversing it via the Iterator interface. | «yes» Пояснение: ArrayIterator is an SPL class that wraps an array and implements the Iterator interface, allowing traversal via foreach or manual iterator methods.
Raw{"answer": "yes", "explanation": "ArrayIterator is an SPL class that wraps an array and implements the Iterator interface, allowing traversal via foreach or manual iterator methods."} | верно | Объектная обёртка над массивом. |
T11-L8 0.83 c | Generators, iterators, SPL | An ArrayObject instance cannot be traversed with foreach. | «no» Пояснение: ArrayObject implements IteratorAggregate, so it can be traversed with foreach.
Raw{"answer": "no", "explanation": "ArrayObject implements IteratorAggregate, so it can be traversed with foreach."} | верно | ArrayObject реализует IteratorAggregate — foreach по нему работает. |
T12-L1 0.89 c | Configuration and security | password_hash() generates a salt automatically — passing one separately is not needed. | «yes» Пояснение: PHP's password_hash() automatically generates and embeds a random salt in the resulting hash string, so no separate salt parameter is required.
Raw{"answer": "yes", "explanation": "PHP's password_hash() automatically generates and embeds a random salt in the resulting hash string, so no separate salt parameter is required."} | верно | Соль встраивается в строку результата; параметр salt устарел. |
T12-L2 1.98 c | Configuration and security | In PHP 8, PASSWORD_DEFAULT is md5 with an automatically added salt. | «no» Пояснение: In PHP 8, PASSWORD_DEFAULT is bcrypt (not md5); md5 is a simple cryptographic hash and is not used by PHP's password hashing functions.
Raw{"answer": "no", "explanation": "In PHP 8, PASSWORD_DEFAULT is bcrypt (not md5); md5 is a simple cryptographic hash and is not used by PHP's password hashing functions."} | верно | PASSWORD_DEFAULT — bcrypt; md5 для паролей непригоден (перебирается массово). |
T12-L3 0.86 c | Configuration and security | What does password_verify('secret', password_hash('secret', PASSWORD_DEFAULT)) return? | «yes» Пояснение: password_verify() returns true when the given password matches the stored hash, which it does here since both are 'secret'.
Raw{"answer": "yes", "explanation": "password_verify() returns true when the given password matches the stored hash, which it does here since both are 'secret'."} | верно | Соль и хеш в одной строке: true (форма ответа: true или да). |
T12-L4 1.15 c | Configuration and security | strip_tags() protects against SQL injection. | «no» Пояснение: strip_tags() only removes HTML/PHP tags from a string; SQL injection protection requires prepared statements or parameterized queries, not tag stripping.
Raw{"answer": "no", "explanation": "strip_tags() only removes HTML/PHP tags from a string; SQL injection protection requires prepared statements or parameterized queries, not tag stripping."} | верно | strip_tags режет HTML-теги (помощник против XSS), к параметризации SQL отношения не имеет. |
T12-L5 1.33 c | Configuration and security | session_regenerate_id() is used to protect against session fixation upon user login. | «yes» Пояснение: session_regenerate_id() generates a new session ID, invalidating the old one, which prevents an attacker from hijacking a session with a known ID (session fixation).
Raw{"answer": "yes", "explanation": "session_regenerate_id() generates a new session ID, invalidating the old one, which prevents an attacker from hijacking a session with a known ID (session fixation)."} | верно | Новый ID сессии после логина — стандартная защита от session fixation. |
T12-L6 1.13 c | Configuration and security | Which built-in function returns the SAPI name (e.g., cli)? | «php_sapi_name()» Пояснение: php_sapi_name() is the built-in PHP function that returns the current SAPI (Server API) name, such as 'cli', 'apache2', or 'fpm-fcgi'.
Raw{"answer": "php_sapi_name()", "explanation": "php_sapi_name() is the built-in PHP function that returns the current SAPI (Server API) name, such as 'cli', 'apache2', or 'fpm-fcgi'."} | верно | php_sapi_name(). |
T12-L7 1.6 c | Configuration and security | session_destroy() deletes session data on the server but not the cookie in the user's browser. | «yes» Пояснение: session_destroy() only removes the session data on the server; the session cookie in the browser must be deleted separately (e.g., via setcookie with a past expiration).
Raw{"answer": "yes", "explanation": "session_destroy() only removes the session data on the server; the session cookie in the browser must be deleted separately (e.g., via setcookie with a past expiration)."} | верно | Удаление cookie — отдельный шаг через setcookie с истёкшим сроком. |
T12-L8 0.95 c | Configuration and security | Without calling session_start(), the $_SESSION array is automatically populated with session data. | «no» Пояснение: In PHP, you must call session_start() before $_SESSION is populated with session data; without it, the array is either unavailable or empty.
Raw{"answer": "no", "explanation": "In PHP, you must call session_start() before $_SESSION is populated with session data; without it, the array is either unavailable or empty."} | верно | Без session_start() данные сессии в массив не загружаются ($_SESSION можно заполнить вручную, но привязки к сессии нет). |
VC-L1 6.42 c | PHP 8.4–8.5 | In which PHP version was the array_find() function introduced? | «8.4» Пояснение: array_find() is not a standard built-in PHP function; it was not officially introduced in any stable PHP version as of 8.4, making this likely a trick question, but 8.4 is the most recent version where new array helpers have been proposed.
Raw{"answer": "8.4", "explanation": "array_find() is not a standard built-in PHP function; it was not officially introduced in any stable PHP version as of 8.4, making this likely a trick question, but 8.4 is the most recent version where new array helpers have been proposed."} | верно | PHP 8.4 (RFC array_find). |
VC-L2 1.07 c | PHP 8.4–8.5 | Property hooks (get/set right in the property declaration) landed in PHP 8.4. | «yes» Пояснение: Property hooks (inline get/set accessors in property declarations) were introduced in PHP 8.4.
Raw{"answer": "yes", "explanation": "Property hooks (inline get/set accessors in property declarations) were introduced in PHP 8.4."} | верно | Property hooks — PHP 8.4 (ноябрь 2024). |
VC-L3 6.03 c | PHP 8.4–8.5 | Asymmetric visibility (public private(set) string $name) appeared in PHP 8.4. | «no» Пояснение: PHP 8.4 introduced property hooks (e.g., get/set on properties), but the specific asymmetric visibility syntax 'public private(set) string $name' was a separate proposal and is not the syntax adopted in PHP 8.4.
Raw{"answer": "no", "explanation": "PHP 8.4 introduced property hooks (e.g., get/set on properties), but the specific asymmetric visibility syntax 'public private(set) string $name' was a separate proposal and is not the syntax adopted in PHP 8.4."} | неверно верный: «yes» | Asymmetric visibility v2 — PHP 8.4. |
VC-L4 1.5 c | PHP 8.4–8.5 | In which PHP version was the #[\NoDiscard] attribute introduced? Answer with the version number. | «8.4» Пояснение: The #[\NoDiscard] attribute was introduced in PHP 8.4 to indicate that a function's return value should not be discarded.
Raw{"answer": 8.4, "explanation": "The #[\\NoDiscard] attribute was introduced in PHP 8.4 to indicate that a function's return value should not be discarded."} | неверно верный: «8.5» | #[\NoDiscard] — PHP 8.5 (marking return values as important). |
VC-L5 7.14 c | PHP 8.4–8.5 | In which PHP version did the pipe operator |> first appear? Answer with the version number. | «no» Пояснение: PHP does not have a pipe operator |>; the | symbol in PHP is the bitwise OR operator, and there is no dedicated |> pipe operator in any PHP version.
Raw{"answer": "no", "explanation": "PHP does not have a pipe operator |>; the | symbol in PHP is the bitwise OR operator, and there is no dedicated |> pipe operator in any PHP version."} | неверно верный: «8.5» | Pipe operator — PHP 8.5 (2025). |
VC-L6 1.67 c | PHP 8.4–8.5 | In which PHP version did clone-with — the syntax clone($obj, ['x' => 1]) — appear? Answer with the version number. | «8.4» Пояснение: The 'clone with' syntax, allowing property overrides during cloning (e.g., clone($obj, ['x' => 1])), was introduced in PHP 8.4.
Raw{"answer": "8.4", "explanation": "The 'clone with' syntax, allowing property overrides during cloning (e.g., clone($obj, ['x' => 1])), was introduced in PHP 8.4."} | неверно верный: «8.5» | Clone with v2 — PHP 8.5. |
VC-L7 4.12 c | PHP 8.4–8.5 | In which PHP version were the array_first() and array_last() functions introduced? | «never» Пояснение: array_first() and array_last() are not built-in PHP functions in any released version of PHP; they are typically custom helpers or part of frameworks like Laravel.
Raw{"answer": "never", "explanation": "array_first() and array_last() are not built-in PHP functions in any released version of PHP; they are typically custom helpers or part of frameworks like Laravel."} | неверно верный: «8.5» | PHP 8.5. |
VC-L8 1.82 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.5» Пояснение: The RFC Partial Function Application v2 was adopted for PHP 8.5.
Raw{"answer": "8.5", "explanation": "The RFC Partial Function Application v2 was adopted for PHP 8.5."} | неверно верный: «8.6» | PFA v2 принят 05.12.2025 (33-0-0), реализован в PHP 8.6. |
VF-L1 2.18 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. | «9» Пояснение: The RFC clamp_v2 introducing the clamp() function was accepted for PHP 9.0.
Raw{"answer": 9, "explanation": "The RFC clamp_v2 introducing the clamp() function was accepted for PHP 9.0."} | неверно верный: «8.6» | По данным владельца (wiki.php.net/rfc): clamp_v2 — 8.6; clamp() в 8.5.11 отсутствует (косвенное подтверждение). Дата-якорь делает клетку монотонной. |
VF-L2 5.35 c | PHP: 8.6+ and the future | RFC Context Managers v2 has already been adopted in PHP (as of 2026-11-07). | «no» Пояснение: As of November 2026, no RFC specifically named 'Context Managers v2' has been formally adopted into PHP; while context-like features (e.g., the with-expression in 8.4) exist, a dedicated 'Context Managers v2' RFC is not part of the adopted feature set.
Raw{"answer": "no", "explanation": "As of November 2026, no RFC specifically named 'Context Managers v2' has been formally adopted into PHP; while context-like features (e.g., the with-expression in 8.4) exist, a dedicated 'Context Managers v2' RFC is not part of the adopted feature set."} | верно | На 06.11.2026 — в обсуждении (создан 2026-10-23); не принят. |
VF-L3 4.24 c | PHP: 8.6+ and the future | RFC Bound-Erased Generic Types (generics) was declined in 2026. | «yes» Пояснение: The RFC for Bound-Erased Generic Types (generics) in PHP was voted down/declined in 2026.
Raw{"answer": "yes", "explanation": "The RFC for Bound-Erased Generic Types (generics) in PHP was voted down/declined in 2026."} | верно | Голосование завершилось 2026-06-28: отклонён (wiki.php.net/rfc). |
VF-L4 2.59 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 2026, PHP has not accepted an RFC making ZTS (Zend Thread Safety) the default build; NTS remains the standard distribution.
Raw{"answer": "no", "explanation": "As of 2026, PHP has not accepted an RFC making ZTS (Zend Thread Safety) the default build; NTS remains the standard distribution."} | верно | Такого принятого RFC нет на дату якоря; якорь делает клетку монотонной — при принятии RFC позже клетка не перевернётся. |
VF-L5 1.53 c | PHP: 8.6+ and the future | As of PHP 8.5, generics (parameterized types) are still absent. | «yes» Пояснение: PHP 8.5 does not include native generics or parameterized types; they remain absent from the language as of that version.
Raw{"answer": "yes", "explanation": "PHP 8.5 does not include native generics or parameterized types; they remain absent from the language as of that version."} | верно | Generics в PHP отсутствуют; отрицательный контроль (не путать с C#/Java). |
VF-L6 2.24 c | PHP: 8.6+ and the future | As of 2026-11-07, the latest stable PHP version is 8.5, and PHP 8.6 has not been released yet (GA — 2026-11-19). | «yes» Пояснение: PHP follows a yearly November release cycle, so PHP 8.5 (GA Nov 2025) is the latest stable version before PHP 8.6's scheduled GA on 2026-11-19.
Raw{"answer": "yes", "explanation": "PHP follows a yearly November release cycle, so PHP 8.5 (GA Nov 2025) is the latest stable version before PHP 8.6's scheduled GA on 2026-11-19."} | верно | 8.5 — релиз осени 2025; 8.6 GA 19.11.2026 (wiki.php.net/todo/php86). Дата снимка — 06.11.2026. |
VF-L7 1.66 c | PHP: 8.6+ and the future | The PHP 6 branch never shipped: after PHP 5.6 came PHP 7.0 directly. | «yes» Пояснение: PHP 6 was a development branch that never received a stable release; the next major version after PHP 5.6 was indeed PHP 7.0 (December 2015).
Raw{"answer": "yes", "explanation": "PHP 6 was a development branch that never received a stable release; the next major version after PHP 5.6 was indeed PHP 7.0 (December 2015)."} | верно | Исторический факт: ветка 6 не была релизнута. |
VF-L8 4.12 c | PHP: 8.6+ and the future | The RFC adding the #[\Deprecated] attribute to the core was adopted. | «no» Пояснение: The RFC proposing a built-in #[\Deprecated] attribute was discussed but not accepted into the PHP core.
Raw{"answer": "no", "explanation": "The RFC proposing a built-in #[\\Deprecated] attribute was discussed but not accepted into the PHP core."} | неверно верный: «yes» | #[\Deprecated] — принят, реализован в PHP 8.4. |
T25-L1 0.9 c | Clean architecture | The dependency rule of clean and onion architecture: inner layers know nothing about outer ones — dependencies point toward the center. | «yes» Пояснение: In clean/onion architecture, the dependency rule dictates that inner layers must not depend on outer layers; all dependencies point inward toward the core/domain.
Raw{"answer": "yes", "explanation": "In clean/onion architecture, the dependency rule dictates that inner layers must not depend on outer layers; all dependencies point inward toward the core/domain."} | верно | Чистая (Robert C. Martin), луковичная (Jeffrey Palermo) и гексагональная (ports & adapters) — варианты одной идеи: зависимости направлены внутрь, к домену. Слоями в проекте следит deptrac. |
T25-L2 1.26 c | Clean architecture | Domain entities import neither Doctrine nor Symfony — only the language and, possibly, the standard library. | «yes» Пояснение: In Domain-Driven Design, domain entities are pure PHP classes that depend only on the language itself and possibly the standard library, keeping them free of framework-specific dependencies like Doctrine or Symfony.
Raw{"answer": "yes", "explanation": "In Domain-Driven Design, domain entities are pure PHP classes that depend only on the language itself and possibly the standard library, keeping them free of framework-specific dependencies like Doctrine or Symfony."} | верно | Изоляция домена от инфраструктуры; deptrac в проекте как раз следит за слоями. |
T25-L3 1.49 c | Clean architecture | Controllers and Twig templates belong to the business-logic layer because they are the ones calling use cases. | «no» Пояснение: Controllers and Twig templates belong to the presentation (view) layer; they call use cases (application layer) but are not themselves part of the business-logic layer.
Raw{"answer": "no", "explanation": "Controllers and Twig templates belong to the presentation (view) layer; they call use cases (application layer) but are not themselves part of the business-logic layer."} | верно | Наоборот: это интерфейсные адаптеры (внешний слой); они зависят от use cases, а не наоборот. |
T25-L4 1.69 c | Clean architecture | What sits at the very center of the onion architecture? | «domain» Пояснение: In the onion architecture, the core domain model (entities and value objects) sits at the very center, surrounded by successive layers of services and adapters.
Raw{"answer": "Domain", "explanation": "In the onion architecture, the core domain model (entities and value objects) sits at the very center, surrounded by successive layers of services and adapters."} | неверно верный: «domain model» | Центральное кольцо — Domain Model: сущности и бизнес-правила без зависимостей; далее Domain Services → Application Services → Infrastructure/UI/Tests (Palermo). |
T25-L5 1.0 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 define allowed layer dependencies and automatically fail the build when a forbidden cross-layer call is detected.
Raw{"answer": "yes", "explanation": "Tools like deptrac define allowed layer dependencies and automatically fail the build when a forbidden cross-layer call is detected."} | верно | depfile.yaml в проекте TasK: CI проверяет правила слоёв на каждом пайплайне. |
T25-L6 1.84 c | Clean architecture | A use case (interactor) may accept an HTTP request or an EntityManager as arguments — it is simpler that way. | «no» Пояснение: In Clean/Hexagonal Architecture a use case should be framework-agnostic: it receives plain data (or value objects) and depends on abstractions (e.g., a Repository interface), not on concrete types like an HTTP Request or a Doctrine EntityManager.
Raw{"answer": "no", "explanation": "In Clean/Hexagonal Architecture a use case should be framework-agnostic: it receives plain data (or value objects) and depends on abstractions (e.g., a Repository interface), not on concrete types like an HTTP Request or a Doctrine EntityManager."} | верно | Use case принимает DTO и порты; привязка к HTTP/ORM протекает инфраструктуру во внутренние слои. |
T25-L7 0.97 c | Clean architecture | What is the component called that provides a collection of aggregates/entities while hiding the storage mechanism behind an interface? | «repository» Пояснение: A Repository provides a collection-like interface for accessing domain aggregates/entities while abstracting the underlying storage mechanism.
Raw{"answer": "Repository", "explanation": "A Repository provides a collection-like interface for accessing domain aggregates/entities while abstracting the underlying storage mechanism."} | верно | Repository pattern (DDD/Evans); в проекте — Doctrine-репозитории за портами. |
T25-L8 1.64 c | Clean architecture | In clean architecture, swapping PostgreSQL for another database touches only the outer layer — the domain and use cases stay unchanged. | «yes» Пояснение: In clean architecture, the database is an infrastructure concern; the domain and use cases depend only on abstractions (interfaces), so swapping the database only affects the outer infrastructure layer.
Raw{"answer": "yes", "explanation": "In clean architecture, the database is an infrastructure concern; the domain and use cases depend only on abstractions (interfaces), so swapping the database only affects the outer infrastructure layer."} | верно | Следствие правила зависимостей: инфраструктура взаимозаменяема. |
T26-L1 1.57 c | DDD | In DDD, an aggregate is just another name for a database table. | «no» Пояснение: In DDD, an aggregate is a cluster of domain objects (entities and value objects) treated as a consistency boundary, not a synonym for a database table; the mapping between them is an implementation detail.
Raw{"answer": "no", "explanation": "In DDD, an aggregate is a cluster of domain objects (entities and value objects) treated as a consistency boundary, not a synonym for a database table; the mapping between them is an implementation detail."} | верно | Агрегат — кластер объектов с границей согласованности (транзакционной вокруг корня); таблица — деталь хранения. |
T26-L2 1.11 c | DDD | A Value Object is immutable and compared by the values of its fields, not by identity. | «yes» Пояснение: In DDD, a Value Object is defined as immutable and uses value-based equality (field comparison) rather than reference-based identity.
Raw{"answer": "yes", "explanation": "In DDD, a Value Object is defined as immutable and uses value-based equality (field comparison) rather than reference-based identity."} | верно | Классика Evans: Money, Email; равенство структурное. |
T26-L3 0.88 c | DDD | What is the single external entry point of an aggregate, through which all changes must go, called? | «aggregate root» Пояснение: In Domain-Driven Design, the Aggregate Root is the single external entry point through which all changes to an aggregate must be made.
Raw{"answer": "Aggregate Root", "explanation": "In Domain-Driven Design, the Aggregate Root is the single external entry point through which all changes to an aggregate must be made."} | верно | Aggregate Root: внешние объекты ссылаются только на корень; он защищает инварианты агрегата. |
T26-L4 1.05 c | DDD | In DDD, a repository is declared for an aggregate (its root), not for every entity. | «yes» Пояснение: In DDD, a repository is defined for an Aggregate Root, treating the entire aggregate as a single consistency boundary, rather than creating separate repositories for each entity within the aggregate.
Raw{"answer": "yes", "explanation": "In DDD, a repository is defined for an Aggregate Root, treating the entire aggregate as a single consistency boundary, rather than creating separate repositories for each entity within the aggregate."} | верно | Репозиторий корня хранит границу согласованности агрегата; вложенные сущности доступны только через корень. |
T26-L5 0.82 c | DDD | Ubiquitous language is the model's shared language common to developers and domain experts. | «yes» Пояснение: Ubiquitous Language, a key DDD concept, is precisely the shared language between developers and domain experts used consistently in the model, code, and discussions.
Raw{"answer": "yes", "explanation": "Ubiquitous Language, a key DDD concept, is precisely the shared language between developers and domain experts used consistently in the model, code, and discussions."} | верно | Evans: язык из требований переходит в имена классов и методов. |
T26-L6 4.82 c | DDD | What is the boundary called within which a model and its language are consistent, while outside the same words mean other models? | «frame» Пояснение: A frame is the boundary within which a model and its language remain self-consistent, while outside it the same terms may refer to different models.
Raw{"answer": "frame", "explanation": "A frame is the boundary within which a model and its language remain self-consistent, while outside it the same terms may refer to different models."} | неверно верный: «bounded context» | Bounded Context; «Заказ» в биллинге и в доставке — разные модели. |
T26-L7 1.2 c | DDD | An anemic model (objects with only getters/setters, logic in services) is the recommended DDD style. | «no» Пояснение: DDD recommends a rich domain model where business logic and behavior are encapsulated within domain objects, not delegated to external service classes.
Raw{"answer": "no", "explanation": "DDD recommends a rich domain model where business logic and behavior are encapsulated within domain objects, not delegated to external service classes."} | верно | Наоборот: Evans называет анемичность антипаттерном — поведение должно жить в доменных объектах. |
T26-L8 1.52 c | DDD | Bounded context means each context has its own model: the same concept in different contexts is a different class. | «yes» Пояснение: In DDD, a Bounded Context ensures each context has its own model, so the same real-world concept is represented by different classes (with different attributes and behaviors) in different contexts.
Raw{"answer": "yes", "explanation": "In DDD, a Bounded Context ensures each context has its own model, so the same real-world concept is represented by different classes (with different attributes and behaviors) in different contexts."} | верно | Модели контекстов независимы; между ними — явная интеграция (ACL, published language). |
T13-L1 2.83 c | Symfony | Services in the Symfony DI container are created lazily by default — on first use. | «yes» Пояснение: Symfony's DI container instantiates services lazily by default, meaning a service object is only created the first time it is actually requested or injected.
Raw{"answer": "yes", "explanation": "Symfony's DI container instantiates services lazily by default, meaning a service object is only created the first time it is actually requested or injected."} | верно | Контейнер инстанцирует сервис при первом извлечении; eager-создания по умолчанию нет. |
T13-L2 1.45 c | Symfony | Which Symfony console command lists all registered routes? | «debug:router» Пояснение: The Symfony console command 'php bin/console debug:router' lists all registered routes with their methods, paths, and controllers.
Raw{"answer": "debug:router", "explanation": "The Symfony console command 'php bin/console debug:router' lists all registered routes with their methods, paths, and controllers."} | верно | bin/console debug:router (FrameworkBundle); в Symfony 3 команда называлась router:debug. |
T13-L3 1.11 c | Symfony | Symfony autowiring requires manually declaring every service in services.yaml. | «no» Пояснение: Autowiring automatically resolves dependencies via type hints, so services do not need to be manually declared in services.yaml.
Raw{"answer": "no", "explanation": "Autowiring automatically resolves dependencies via type hints, so services do not need to be manually declared in services.yaml."} | верно | Autowire+autoconfigure регистрируют и связывают сервисы автоматически; ручное перечисление — исключение. |
T13-L4 1.0 c | Symfony | Twig templates are compiled into PHP classes and cached between requests. | «yes» Пояснение: Twig compiles templates into PHP classes and stores them in a cache directory to avoid recompilation on subsequent requests.
Raw{"answer": "yes", "explanation": "Twig compiles templates into PHP classes and stores them in a cache directory to avoid recompilation on subsequent requests."} | верно | Twig компилирует шаблон один раз; кэш в var/cache/twig, в prod не пересобирается. |
T13-L5 1.92 c | Symfony | In the Symfony dev environment the DI container is rebuilt only after tracked files change, not on every request. | «yes» Пояснение: In Symfony dev, the compiled container is cached in var/cache/dev/ and is only recompiled when tracked files (e.g., service configs) have a newer timestamp than the cache; otherwise the cached container is reused on each request.
Raw{"answer": "yes", "explanation": "In Symfony dev, the compiled container is cached in var/cache/dev/ and is only recompiled when tracked files (e.g., service configs) have a newer timestamp than the cache; otherwise the cached container is reused on each request."} | верно | Kernel проверяет freshness ресурсов (конфиги, классы); иначе переиспользуется кэш контейнера. |
T13-L6 0.91 c | Symfony | Which environment variable selects the active Symfony environment (dev/prod)? | «app_env» Пояснение: The APP_ENV environment variable is used by Symfony to select the active environment (dev, prod, test).
Raw{"answer": "APP_ENV", "explanation": "The APP_ENV environment variable is used by Symfony to select the active environment (dev, prod, test)."} | верно | APP_ENV в .env; APP_DEBUG — отдельный флаг отладки. |
T13-L7 1.39 c | Symfony | A controller method can be private — Symfony routing works with any method of the class. | «no» Пояснение: In Symfony, the controller action method that a route points to must be public; private or protected methods cannot be called directly by the router/reflector.
Raw{"answer": "no", "explanation": "In Symfony, the controller action method that a route points to must be public; private or protected methods cannot be called directly by the router/reflector."} | верно | Действие контроллера должно быть public; приватный метод по маршруту не вызывается. |
T13-L8 2.55 c | Symfony | Event subscribers always receive events before listeners, because the interface gives them priority. | «no» Пояснение: In PHP event systems (e.g., Symfony), subscribers and listeners share the same dispatch queue; order is determined by priority and registration order, not by the subscriber interface itself.
Raw{"answer": "no", "explanation": "In PHP event systems (e.g., Symfony), subscribers and listeners share the same dispatch queue; order is determined by priority and registration order, not by the subscriber interface itself."} | верно | Порядок определяет priority, а не тип подписки; приоритеты задаются в getSubscribedEvents() так же, как у слушателей. |
T22-L1 2.58 c | Symfony: Security and forms | In modern Symfony (6.0+) authentication is built on authenticator classes (AuthenticatorInterface); the old guard system has been removed. | «yes» Пояснение: Symfony 6.0 removed the legacy guard authentication system; the modern approach uses custom authenticator classes implementing AuthenticatorInterface with Passport/Badge objects.
Raw{"answer": "yes", "explanation": "Symfony 6.0 removed the legacy guard authentication system; the modern approach uses custom authenticator classes implementing AuthenticatorInterface with Passport/Badge objects."} | верно | Guard объявлен устаревшим в 5.3 и удалён в 6.0; в проекте symfony/security-bundle 8.1. |
T22-L2 1.94 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 Security checks whether the current user has a specified role or permission on a controller method, and throws an AccessDeniedException (403) if not.
Raw{"answer": "IsGranted", "explanation": "The #[IsGranted] attribute in Symfony Security checks whether the current user has a specified role or permission on a controller method, and throws an AccessDeniedException (403) if not."} | верно | #[IsGranted('ROLE_ADMIN')]; атрибут из symfony/security-http. |
T22-L3 1.13 c | Symfony: Security and forms | Voters are Symfony's mechanism for checking access to a specific object: isGranted('EDIT', $post). | «yes» Пояснение: Symfony Voters are the built-in mechanism for object-level access control, used via isGranted('EDIT', $post) to check permissions against a specific object.
Raw{"answer": "yes", "explanation": "Symfony Voters are the built-in mechanism for object-level access control, used via isGranted('EDIT', $post) to check permissions against a specific object."} | верно | VoterInterface->vote(); docs Symfony — Voters. |
T22-L4 3.27 c | Symfony: Security and forms | In modern Symfony (7+) validation constraints are declared as PHP attributes (#[Assert\NotBlank]); doctrine annotations are no longer supported. | «yes» Пояснение: In Symfony 7 the Doctrine Annotations driver was removed, so validation constraints in code must be declared using PHP 8 attributes like #[Assert\NotBlank]; (XML/YAML mappings remain as alternatives, but the Doctrine Annotations format is gone).
Raw{"answer": "yes", "explanation": "In Symfony 7 the Doctrine Annotations driver was removed, so validation constraints in code must be declared using PHP 8 attributes like #[Assert\\NotBlank]; (XML/YAML mappings remain as alternatives, but the Doctrine Annotations format is gone)."} | верно | Докблок-аннотации удалены в Symfony 7.0; стандарт — атрибуты. В проекте symfony/validator 8.1. |
T22-L5 1.08 c | Symfony: Security and forms | CSRF protection of Symfony forms is enabled by default: the form validates the token on submission. | «yes» Пояснение: Symfony forms include a CSRF token field and validate it on submission by default; it can only be disabled by explicitly setting 'csrf_protection' => false.
Raw{"answer": "yes", "explanation": "Symfony forms include a CSRF token field and validate it on submission by default; it can only be disabled by explicitly setting 'csrf_protection' => false."} | верно | FormType добавляет скрытое поле _token и проверяет его при валидации; отключение — осознанное исключение (csrf: false). |
T22-L6 1.35 c | Symfony: Security and forms | Form validation in Symfony runs server-side even if the client-side (HTML5) checks passed. | «yes» Пояснение: Symfony's form validation (via constraints like NotBlank, Length, etc.) is always executed server-side upon submission, regardless of whether client-side HTML5 validation already passed; the server is the authoritative validator.
Raw{"answer": "yes", "explanation": "Symfony's form validation (via constraints like NotBlank, Length, etc.) is always executed server-side upon submission, regardless of whether client-side HTML5 validation already passed; the server is the authoritative validator."} | верно | Клиентская валидация — только удобство; серверная обязательна и идёт по метаданным объекта формы. |
T22-L7 0.9 c | Symfony: Security and forms | Which Symfony maker command generates a form class (FormType)? | «make:form» Пояснение: The Symfony MakerBundle command 'make:form' generates a FormType class for building forms.
Raw{"answer": "make:form", "explanation": "The Symfony MakerBundle command 'make:form' generates a FormType class for building forms."} | верно | bin/console make:form (symfony/maker-bundle — в проекте). |
T22-L8 1.1 c | Symfony: Security and forms | Symfony stores the user's password in the session in plain text. | «no» Пояснение: Symfony stores the user's identity (e.g., user ID and a token) in the session, not the password; the password is only hashed and kept in the database for comparison during authentication.
Raw{"answer": "no", "explanation": "Symfony stores the user's identity (e.g., user ID and a token) in the session, not the password; the password is only hashed and kept in the database for comparison during authentication."} | верно | В сессии живёт объект пользователя в токене; хеш затирается eraseCredentials(), plaintext там никогда не лежит. |
T23-L1 1.1 c | Symfony: configuration and services | Symfony bundle configuration lives in config/packages — one file per bundle or topic. | «yes» Пояснение: Symfony's recommended structure (especially with Symfony Flex) places each bundle's configuration in a separate YAML/XML/PHP file under config/packages/ (e.g., config/packages/doctrine.yaml).
Raw{"answer": "yes", "explanation": "Symfony's recommended structure (especially with Symfony Flex) places each bundle's configuration in a separate YAML/XML/PHP file under config/packages/ (e.g., config/packages/doctrine.yaml)."} | верно | Стандартная структура (config/packages/*.yaml); перегрузка — config/packages/<env>. |
T23-L2 1.22 c | Symfony: configuration and services | The .env file with dev defaults is committed to the repository, while real secrets live in the non-committed .env.local. | «yes» Пояснение: This is a standard convention: .env holds safe dev defaults committed to VCS, while .env.local holds real secrets and is gitignored.
Raw{"answer": "yes", "explanation": "This is a standard convention: .env holds safe dev defaults committed to VCS, while .env.local holds real secrets and is gitignored."} | верно | symfony/dotenv: .env — общий безопасный набор значений; локальные секреты — .env.local (gitignored) или secrets-хранилище. |
T23-L3 1.32 c | Symfony: configuration and services | Which Symfony command lists the container's registered services and their aliases? | «debug:container» Пояснение: The Symfony command 'debug:container' lists all registered services and their aliases in the service container.
Raw{"answer": "debug:container", "explanation": "The Symfony command 'debug:container' lists all registered services and their aliases in the service container."} | верно | bin/console debug:container; параметры контейнера — debug:parameter. |
T23-L4 4.06 c | Symfony: configuration and services | The Symfony container allows changing parameters at runtime: $container->setParameter() works from a controller. | «yes» Пояснение: Symfony's Container class exposes setParameter() which can be called at runtime from a controller, though it won't affect services whose parameters were already inlined during compilation.
Raw{"answer": "yes", "explanation": "Symfony's Container class exposes setParameter() which can be called at runtime from a controller, though it won't affect services whose parameters were already inlined during compilation."} | неверно верный: «no» | Контейнер компилируется и замораживается; runtime-значения — только через переменные окружения. |
T23-L5 1.28 c | Symfony: configuration and services | By default, Symfony services are public (public: true) — you can fetch them directly from the container. | «no» Пояснение: Since Symfony 4, services are private (public: false) by default, allowing the container to optimize by dropping unused services.
Raw{"answer": "no", "explanation": "Since Symfony 4, services are private (public: false) by default, allowing the container to optimize by dropping unused services."} | верно | С Symfony 4.0 сервисы по умолчанию private: инжектятся через autowiring; $container->get() — только для публичных. |
T23-L6 1.31 c | Symfony: configuration and services | Without a config file in config/packages a bundle will not work — configuration is mandatory for every bundle. | «no» Пояснение: Many Symfony bundles work perfectly fine without a config file in config/packages, as they provide sensible defaults built into the bundle itself.
Raw{"answer": "no", "explanation": "Many Symfony bundles work perfectly fine without a config file in config/packages, as they provide sensible defaults built into the bundle itself."} | верно | У бандлов есть встроенные умолчания (Extension); конфиг нужен только для отклонений от них. |
T23-L7 0.76 c | Symfony: configuration and services | Environment variable values are injected into services.yaml using the %env(VAR)% syntax. | «yes» Пояснение: In Symfony, the %env(VAR)% syntax is used in configuration files like services.yaml to reference environment variable values.
Raw{"answer": "yes", "explanation": "In Symfony, the %env(VAR)% syntax is used in configuration files like services.yaml to reference environment variable values."} | верно | %env(...)% резолвится в рантайме env-процессорами; docs — Env Var Processors. |
T23-L8 0.86 c | Symfony: configuration and services | Which Symfony environment variable enables debug mode (affects the profiler and Twig debugging)? | «app_debug» Пояснение: In Symfony, the APP_DEBUG environment variable (set to true/false in the .env file) enables or disables debug mode, which controls the profiler, Twig debug tools, and other development features.
Raw{"answer": "APP_DEBUG", "explanation": "In Symfony, the APP_DEBUG environment variable (set to true/false in the .env file) enables or disables debug mode, which controls the profiler, Twig debug tools, and other development features."} | верно | APP_DEBUG=1 (в .env dev-окружения); окружение выбирает APP_ENV — см. T13-L6. |
T16-L1 0.99 c | Symfony: Messenger | A single message in Symfony Messenger can only have one handler. | «no» Пояснение: Symfony Messenger supports assigning multiple handlers to a single message, which are executed in the order they are defined.
Raw{"answer": "no", "explanation": "Symfony Messenger supports assigning multiple handlers to a single message, which are executed in the order they are defined."} | верно | Messenger вызывает все хендлеры, подписанные на класс сообщения (docs — Multiple Handlers). |
T16-L2 1.06 c | Symfony: Messenger | The sync transport in Messenger queues the message for a worker, just like async. | «no» Пояснение: The sync transport dispatches and handles the message immediately in the current process, without queueing it for a separate worker.
Raw{"answer": "no", "explanation": "The sync transport dispatches and handles the message immediately in the current process, without queueing it for a separate worker."} | верно | Наоборот: sync обрабатывает немедленно в том же процессе, что и отправка; очередь — это async-транспорт. |
T16-L3 0.75 c | Symfony: Messenger | Which console command starts the worker that processes Messenger queue messages? | «messenger:consume» Пояснение: In Symfony, the command 'php bin/console messenger:consume' starts the worker that processes Messenger queue messages.
Raw{"answer": "messenger:consume", "explanation": "In Symfony, the command 'php bin/console messenger:consume' starts the worker that processes Messenger queue messages."} | верно | bin/console messenger:consume async; воркеры под supervisord/systemd в проде. |
T16-L4 2.24 c | Symfony: Messenger | Retries for failed messages (retry_strategy) are configured per Messenger transport. | «no» Пояснение: Retry strategies in Symfony Messenger are configured globally, per bus, or per message (via RetryStrategyInterface), not per transport.
Raw{"answer": "no", "explanation": "Retry strategies in Symfony Messenger are configured globally, per bus, or per message (via RetryStrategyInterface), not per transport."} | неверно верный: «yes» | retry_strategy на транспорте: max_retries, delay, multiplier; docs — Failed Messages & Retries. |
T16-L5 1.58 c | Symfony: Messenger | By default, Messenger serializes messages to JSON. | «yes» Пояснение: Symfony Messenger uses JSON as the default serialization format for messages when using transports.
Raw{"answer": "yes", "explanation": "Symfony Messenger uses JSON as the default serialization format for messages when using transports."} | неверно верный: «no» | Дефолтный сериализатор — PhpSerializer (serialize()); JSON-сериализатор включается отдельно. |
T16-L6 2.37 c | Symfony: Messenger | Symfony Scheduler produces messages on a schedule and dispatches them through Messenger. | «yes» Пояснение: Symfony Scheduler is designed to trigger scheduled tasks by dispatching messages through the Symfony Messenger component on defined schedules (e.g., cron expressions).
Raw{"answer": "yes", "explanation": "Symfony Scheduler is designed to trigger scheduled tasks by dispatching messages through the Symfony Messenger component on defined schedules (e.g., cron expressions)."} | верно | Schedule → RecurringMessage → шина Messenger; docs — Scheduler. |
T16-L7 0.98 c | Symfony: Messenger | Which built-in Messenger transport stores messages in database tables via Doctrine? | «doctrine» Пояснение: Symfony Messenger's built-in 'doctrine' transport uses Doctrine DBAL to store and retrieve messages in database tables.
Raw{"answer": "doctrine", "explanation": "Symfony Messenger's built-in 'doctrine' transport uses Doctrine DBAL to store and retrieve messages in database tables."} | верно | Транспорт doctrine (symfony/doctrine-messenger); таблица messenger_messages. В проекте стоит amqp-messenger + doctrine-messenger. |
T16-L8 1.06 c | Symfony: Messenger | The Messenger pipeline can be extended with custom middleware, placed before or after the built-in ones. | «yes» Пояснение: Symfony Messenger's pipeline is designed to be extensible, allowing developers to insert custom middleware before, after, or between the built-in middleware handlers.
Raw{"answer": "yes", "explanation": "Symfony Messenger's pipeline is designed to be extensible, allowing developers to insert custom middleware before, after, or between the built-in middleware handlers."} | верно | messenger.bus.*.middleware в yaml; docs — Middleware. |
T28-L1 1.33 c | Symfony: versions | Symfony major releases come every two years, minor ones every six months (in May and November). | «yes» Пояснение: Symfony major versions are released approximately every two years, and minor versions are released every six months in May and November.
Raw{"answer": "yes", "explanation": "Symfony major versions are released approximately every two years, and minor versions are released every six months in May and November."} | верно | Стандартный релизный цикл: 8.0 — ноябрь 2025, 8.1 — май 2026, 8.2 — ноябрь 2026. |
T28-L2 1.17 c | Symfony: versions | What is the minimum PHP version required by Symfony 8? | «8.4» Пояснение: Symfony 8 requires a minimum PHP version of 8.4.
Raw{"answer": 8.4, "explanation": "Symfony 8 requires a minimum PHP version of 8.4."} | верно | Symfony 8.0 поднял требование до PHP >= 8.4.1 (в vendor проекта: "php": ">=8.4.1"). |
T28-L3 1.76 c | Symfony: versions | Symfony 7.0 kept support for docblock annotations (validation, routes). | «no» Пояснение: Symfony 7.0 removed support for docblock annotations in favor of native PHP 8 attributes; annotations were deprecated in 6.4 and then removed in 7.0.
Raw{"answer": "no", "explanation": "Symfony 7.0 removed support for docblock annotations in favor of native PHP 8 attributes; annotations were deprecated in 6.4 and then removed in 7.0."} | верно | Наоборот: в 7.0 аннотации удалены — только PHP-атрибуты (#[Route], #[Assert\NotBlank]). |
T28-L4 1.52 c | Symfony: versions | AssetMapper manages CSS/JS without node or webpack — via importmap.php. | «yes» Пояснение: Symfony's AssetMapper component (introduced in 7.1) manages CSS and JS assets without requiring Node.js or Webpack, using an importmap.php (or importmap.json) file to define and track dependencies.
Raw{"answer": "yes", "explanation": "Symfony's AssetMapper component (introduced in 7.1) manages CSS and JS assets without requiring Node.js or Webpack, using an importmap.php (or importmap.json) file to define and track dependencies."} | верно | symfony/asset-mapper (с 6.3, стандарт с 7.x); в проекте — importmap.php в корне и asset-mapper 8.1. |
T28-L5 1.2 c | Symfony: versions | Symfony 6.4 is a regular release without long-term support. | «no» Пояснение: Symfony 6.4 is actually a Long-Term Support (LTS) release, not a regular short-support release.
Raw{"answer": "no", "explanation": "Symfony 6.4 is actually a Long-Term Support (LTS) release, not a regular short-support release."} | верно | Наоборот: 6.4 — LTS (расширенная поддержка); LTS выходит вместе с очередным мажором (6.4 — вместе с 7.0). |
T28-L6 5.1 c | Symfony: versions | When moving to a new Symfony major version, deprecations of the previous branch keep working — major releases do not remove them. | «yes» Пояснение: Symfony's deprecation policy keeps deprecated features working for at least one subsequent major version; a feature deprecated in 5.x is removed in 7.x, not 6.x.
Raw{"answer": "yes", "explanation": "Symfony's deprecation policy keeps deprecated features working for at least one subsequent major version; a feature deprecated in 5.x is removed in 7.x, not 6.x."} | неверно верный: «no» | Наоборот: мажорный релиз удаляет всё устаревшее (7.0 убрал деприкейшены 6.x, 8.0 — 7.x). |
T28-L7 1.41 c | Symfony: versions | Every Symfony major release is accompanied by an UPGRADE guide listing the changes. | «yes» Пояснение: Symfony consistently provides UPGRADE-*.md files in its repository documenting breaking changes and deprecations for each major release.
Raw{"answer": "yes", "explanation": "Symfony consistently provides UPGRADE-*.md files in its repository documenting breaking changes and deprecations for each major release."} | верно | UPGRADE-7.0.md, UPGRADE-8.0.md в репозитории symfony/symfony. |
T28-L8 1.5 c | Symfony: versions | Which Symfony component manages assets and the importmap without node/webpack? | «assetmapper» Пояснение: Symfony's AssetMapper component (introduced in Symfony 7.1) manages assets and import maps without requiring Node.js or webpack.
Raw{"answer": "AssetMapper", "explanation": "Symfony's AssetMapper component (introduced in Symfony 7.1) manages assets and import maps without requiring Node.js or webpack."} | верно | symfony/asset-mapper 8.1 — в проекте. |
T29-L1 6.66 c | Symfony: 8.2 and beyond | As of 2026-11-07, Symfony 8.2 has already been released. | «no» Пояснение: Symfony minor releases in the November cycle are typically made at the end of November (around the 28th-29th), so as of November 7, 2026, Symfony 8.2 would not yet have been released.
Raw{"answer": "no", "explanation": "Symfony minor releases in the November cycle are typically made at the end of November (around the 28th-29th), so as of November 7, 2026, Symfony 8.2 would not yet have been released."} | верно | Наоборот: 8.2 ещё не выпущена — релиз в конце ноября 2026; последняя стабильная — 8.1. |
T29-L2 3.15 c | Symfony: 8.2 and beyond | As of 2026-11-07, Symfony 8.2 is scheduled for November 2026, following the usual six-month cycle. | «yes» Пояснение: Symfony follows a six-month release cycle, so 8.0 (Nov 2025), 8.1 (May 2026), and 8.2 (Nov 2026) align with that schedule.
Raw{"answer": "yes", "explanation": "Symfony follows a six-month release cycle, so 8.0 (Nov 2025), 8.1 (May 2026), and 8.2 (Nov 2026) align with that schedule."} | верно | Политика релизов: 8.1 — май 2026, 8.2 — ноябрь 2026; якорь даты фиксирует срез — модель с поздним cutoff отвечает «на дату». |
T29-L3 1.16 c | Symfony: 8.2 and beyond | Which Symfony version comes after 8.1 (as of 2026-11-07)? | «8.2» Пояснение: Following standard semver and Symfony's release cycle, the version immediately after 8.1 is 8.2.
Raw{"answer": "8.2", "explanation": "Following standard semver and Symfony's release cycle, the version immediately after 8.1 is 8.2."} | верно | 8.2 — следующий минорный релиз (ноябрь 2026); после его выхода проект переходит с 8.1.* на 8.2.*. |
T29-L4 2.62 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 (the '.2' part) is a minor/patch release within the 8.x major line, and even major Symfony releases involve removing deprecated features rather than requiring a full rewrite of applications.
Raw{"answer": "no", "explanation": "Symfony 8.2 (the '.2' part) is a minor/patch release within the 8.x major line, and even major Symfony releases involve removing deprecated features rather than requiring a full rewrite of applications."} | верно | Наоборот: 8.2 — минорный релиз; новые возможности без поломки обратной совместимости. Мажор — 9.0. |
T29-L5 3.46 c | Symfony: 8.2 and beyond | Updating within a major branch (8.1 → 8.2) should not require code changes — backward compatibility is preserved. | «yes» Пояснение: PHP's backward-compatibility policy guarantees that no breaking changes are introduced within a major version (e.g., 8.x), so moving from 8.1 to 8.2 should not require code changes.
Raw{"answer": "yes", "explanation": "PHP's backward-compatibility policy guarantees that no breaking changes are introduced within a major version (e.g., 8.x), so moving from 8.1 to 8.2 should not require code changes."} | верно | Политика Symfony: минорные релизы обратно совместимы; BC-break допустим только в мажорных. |
T29-L6 1.49 c | Symfony: 8.2 and beyond | Which minor version of the 8.x branch is released last, before Symfony 9.0? | «8.4» Пояснение: Symfony 8.4 is the last minor (LTS) release in the 8.x branch before Symfony 9.0, following the pattern where .4 releases are the long-term support versions.
Raw{"answer": 8.4, "explanation": "Symfony 8.4 is the last minor (LTS) release in the 8.x branch before Symfony 9.0, following the pattern where .4 releases are the long-term support versions."} | верно | По циклу: 8.2 (ноя 2026), 8.3 (май 2027), 8.4 (ноя 2027, вместе с 9.0) — как 6.4 выходила вместе с 7.0. |
T29-L7 5.04 c | Symfony: 8.2 and beyond | Symfony 8.2 will require PHP 8.5 — you would have to upgrade PHP along with it. | «no» Пояснение: Symfony 8.2 is not yet an established release with a confirmed PHP 8.5 requirement; the actual minimum PHP version for that future release is not definitively set to 8.5.
Raw{"answer": "no", "explanation": "Symfony 8.2 is not yet an established release with a confirmed PHP 8.5 requirement; the actual minimum PHP version for that future release is not definitively set to 8.5."} | верно | Наоборот: минорные релизы не поднимают требования PHP; для всей ветки 8.x остаётся PHP >= 8.4. |
T29-L8 1.63 c | Symfony: 8.2 and beyond | Deprecations added in the 8.x branch will not be removed before Symfony 9.0. | «yes» Пояснение: Symfony's deprecation policy guarantees that deprecations introduced in a major branch (e.g., 8.x) will only be removed in the next major version (9.0), preserving backward compatibility within the same major release.
Raw{"answer": "yes", "explanation": "Symfony's deprecation policy guarantees that deprecations introduced in a major branch (e.g., 8.x) will only be removed in the next major version (9.0), preserving backward compatibility within the same major release."} | верно | Политика: деприкейшены живут до следующего мажора; 9.0 — ноябрь 2027. |
T21-L1 3.06 c | Twig | Inside {{ }}, Twig allows calling arbitrary PHP code directly. | «no» Пояснение: Inside {{ }}, Twig uses its own expression language (variables, filters, operators, method calls) rather than allowing arbitrary raw PHP code to be written directly.
Raw{"answer": "no", "explanation": "Inside {{ }}, Twig uses its own expression language (variables, filters, operators, method calls) rather than allowing arbitrary raw PHP code to be written directly."} | верно | Twig — DSL: только разрешённые окружением функции/фильтры; произвольный PHP не исполняется. |
T21-L2 0.87 c | Twig | By default, Twig auto-escapes printed variables. | «yes» Пояснение: Twig auto-escapes all output by default (using the 'html' escaping strategy) to protect against XSS attacks.
Raw{"answer": "yes", "explanation": "Twig auto-escapes all output by default (using the 'html' escaping strategy) to protect against XSS attacks."} | верно | Autoescape включён по умолчанию; {{ '<b>' }} → <b>. Проверено на Twig 3.30. |
T21-L3 0.83 c | Twig | The Twig |e filter escapes a string for safe output in an HTML context. | «yes» Пояснение: The Twig |e (escape) filter defaults to escaping a string for safe HTML output.
Raw{"answer": "yes", "explanation": "The Twig |e (escape) filter defaults to escaping a string for safe HTML output."} | верно | |e ('html') по умолчанию; есть контексты js/url/css. От SQL-инъекций он не защищает — это задача подготовленных запросов Doctrine. |
T21-L4 1.77 c | Twig | Which filter from twig/intl-extra formats a number according to a locale? | «number_format» Пояснение: The twig/intl-extra package provides the number_format filter which formats a number according to a given locale.
Raw{"answer": "number_format", "explanation": "The twig/intl-extra package provides the number_format filter which formats a number according to a given locale."} | неверно верный: «format_number» | |format_number(locale=...) из IntlExtension (twig/intl-extra есть в проекте). Проверено на Twig 3.30: 12345.6 → 12 345,6 (ru). |
T21-L5 1.47 c | Twig | The |raw filter disables auto-escaping for the value. | «yes» Пояснение: The |raw filter (as in Twig) marks a value as already safe, telling the templating engine to skip auto-escaping.
Raw{"answer": "yes", "explanation": "The |raw filter (as in Twig) marks a value as already safe, telling the templating engine to skip auto-escaping."} | верно | {{ x|raw }} выводит HTML как есть; опасно с пользовательскими данными. Проверено на Twig 3.30. |
T21-L6 1.09 c | Twig | In Twig, {{ }} prints an expression value, while {% %} executes tags — conditions, loops, set. | «yes» Пояснение: In Twig, {{ }} is the variable/output tag that prints an expression's value, while {% %} is the statement tag used for control structures like if, for, and set.
Raw{"answer": "yes", "explanation": "In Twig, {{ }} is the variable/output tag that prints an expression's value, while {% %} is the statement tag used for control structures like if, for, and set."} | верно | Два блока синтаксиса Twig: вывод (echo) против логики. |
T21-L7 1.16 c | Twig | In Twig you cannot declare a variable inside a template — values only come from the controller. | «no» Пояснение: Twig allows you to declare variables inside a template using the 'set' tag, e.g. {% set foo = 'bar' %}.
Raw{"answer": "no", "explanation": "Twig allows you to declare variables inside a template using the 'set' tag, e.g. {% set foo = 'bar' %}."} | верно | {% set y = ... %} объявляет переменную в шаблоне. Проверено на Twig 3.30. |
T21-L8 0.69 c | Twig | Which Twig function dumps the debug structure of a variable (array, object)? | «dump» Пояснение: Twig's built-in `dump()` function outputs a debug structure of a variable (array, object, etc.).
Raw{"answer": "dump", "explanation": "Twig's built-in `dump()` function outputs a debug structure of a variable (array, object, etc.)."} | верно | {{ dump(x) }} (DebugExtension; в Symfony доступна в dev-окружении). |
T24-L1 0.96 c | Bootstrap | Bootstrap is a CSS/JS library of ready-made UI components, not an SPA framework. | «yes» Пояснение: Bootstrap is a front-end CSS/JS library providing ready-made UI components (buttons, modals, navbars, etc.), not an SPA framework like React, Angular, or Vue.
Raw{"answer": "yes", "explanation": "Bootstrap is a front-end CSS/JS library providing ready-made UI components (buttons, modals, navbars, etc.), not an SPA framework like React, Angular, or Vue."} | верно | Компоненты и утилиты поверх вашего HTML; SPA-фреймворки (React/Vue) — другой класс инструментов. В проекте vendored 5.3.3. |
T24-L2 1.1 c | Bootstrap | Which Bootstrap class gives a responsive container with a fixed max width per breakpoint? | «container» Пояснение: The .container class in Bootstrap provides a responsive centered container with a fixed max-width that changes at each breakpoint, unlike .container-fluid which is always 100% width.
Raw{"answer": "container", "explanation": "The .container class in Bootstrap provides a responsive centered container with a fixed max-width that changes at each breakpoint, unlike .container-fluid which is always 100% width."} | верно | .container (фиксированная макс-ширина по брейкпоинтам) vs .container-fluid (на всю ширину). |
T24-L3 1.22 c | Bootstrap | The Bootstrap grid is built on CSS floats and splits a row into 16 columns. | «no» Пояснение: Bootstrap's grid splits a row into 12 columns (not 16), and modern Bootstrap (v4+) uses CSS Flexbox rather than floats.
Raw{"answer": "no", "explanation": "Bootstrap's grid splits a row into 12 columns (not 16), and modern Bootstrap (v4+) uses CSS Flexbox rather than floats."} | верно | Наоборот: flexbox (с Bootstrap 4) и 12 колонок; float-сетка — это Bootstrap 3. |
T24-L4 1.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 exactly five named breakpoints: sm (576px), md (768px), lg (992px), xl (1200px), and xxl (1400px).
Raw{"answer": "yes", "explanation": "Bootstrap 5 defines exactly five named breakpoints: sm (576px), md (768px), lg (992px), xl (1200px), and xxl (1400px)."} | верно | Тиров всего шесть: xs (без инфикса) + пять именованных (576/768/992/1200/1400 px). |
T24-L5 1.99 c | Bootstrap | Utilities like .mt-3 or .px-2 use the spacing scale: the number is a multiple of $spacer. | «yes» Пояснение: Spacing utilities like .mt-3 or .px-2 multiply the base spacing variable ($spacer) by the number in the class name.
Raw{"answer": "yes", "explanation": "Spacing utilities like .mt-3 or .px-2 multiply the base spacing variable ($spacer) by the number in the class name."} | неверно верный: «no» | Spacing utilities; $spacer = 1rem. |
T24-L6 0.83 c | Bootstrap | Which Bootstrap 5 data attribute enables an interactive component (e.g. dropdown) on an element? | «data-bs-toggle» Пояснение: In Bootstrap 5, the data-bs-toggle attribute is used to enable interactive components such as dropdowns, tooltips, and popovers on an element.
Raw{"answer": "data-bs-toggle", "explanation": "In Bootstrap 5, the data-bs-toggle attribute is used to enable interactive components such as dropdowns, tooltips, and popovers on an element."} | верно | data-bs-toggle="dropdown" и т.п.; в Bootstrap 4 атрибут назывался data-toggle. |
T24-L7 0.77 c | Bootstrap | Bootstrap 5 components work without jQuery — in plain vanilla JS. | «yes» Пояснение: Bootstrap 5 removed the jQuery dependency entirely; all its interactive components are implemented in plain vanilla JavaScript.
Raw{"answer": "yes", "explanation": "Bootstrap 5 removed the jQuery dependency entirely; all its interactive components are implemented in plain vanilla JavaScript."} | верно | jQuery удалён в Bootstrap 5.0: data-bs-* атрибуты и JS API. В проекте vendored 5.3.3. |
T24-L8 1.23 c | Bootstrap | Dark mode in Bootstrap is enabled with a .dark class on the root element. | «no» Пояснение: Bootstrap 5.3 enables dark mode with the data-bs-theme="dark" attribute on the <html> element, not a .dark class.
Raw{"answer": "no", "explanation": "Bootstrap 5.3 enables dark mode with the data-bs-theme=\"dark\" attribute on the <html> element, not a .dark class."} | верно | Наоборот: тема включается атрибутом data-bs-theme="dark" (Color modes, с 5.3); класса .dark не существует. В проекте 5.3.3. |
T14-L1 1.12 c | Doctrine | Doctrine ORM creates database tables on the fly the first time an entity is used at runtime. | «no» Пояснение: Doctrine ORM does not auto-create tables at runtime; you must explicitly generate the schema via schema-tool commands or migrations.
Raw{"answer": "no", "explanation": "Doctrine ORM does not auto-create tables at runtime; you must explicitly generate the schema via schema-tool commands or migrations."} | верно | Схему создают инструменты (migrations, schema tool); рантайм структуру БД не меняет. |
T14-L2 0.73 c | Doctrine | Which EntityManager method marks a new object as managed without executing SQL until flush()? | «persist» Пояснение: EntityManager::persist() marks a new entity as managed without executing SQL until flush() is called.
Raw{"answer": "persist", "explanation": "EntityManager::persist() marks a new entity as managed without executing SQL until flush() is called."} | верно | persist() регистрирует объект в Unit of Work; INSERT выполняется на flush(). |
T14-L3 1.8 c | Doctrine | In Doctrine ORM 3, the EntityManager::merge() method exists and makes the passed object managed. | «no» Пояснение: In Doctrine ORM 3, EntityManager::merge() was removed and replaced by EntityManager::toManaged().
Raw{"answer": "no", "explanation": "In Doctrine ORM 3, EntityManager::merge() was removed and replaced by EntityManager::toManaged()."} | верно | В ORM 3 merge() удалён (в vendor проекта 3.7.6 метода нет); в Doctrine 2.x merge() возвращал управляемую копию. Версия зафиксирована — ORM 3. |
T14-L4 0.98 c | Doctrine | DQL queries are written in terms of entities and their fields, not tables and columns. | «yes» Пояснение: DQL (Doctrine Query Language) operates at the object level, using entity class names and their mapped fields rather than raw database table and column names.
Raw{"answer": "yes", "explanation": "DQL (Doctrine Query Language) operates at the object level, using entity class names and their mapped fields rather than raw database table and column names."} | верно | Doctrine транслирует DQL в SQL; docs — DQL (Doctrine Query Language). |
T14-L5 1.16 c | Doctrine | What does $repository->find(999) return when no record with id 999 exists? | «null» Пояснение: In PHP (e.g., Doctrine/Symfony repositories), the find() method returns null when no entity matching the given ID is found.
Raw{"answer": "null", "explanation": "In PHP (e.g., Doctrine/Symfony repositories), the find() method returns null when no entity matching the given ID is found."} | верно | find() возвращает null, если объект не найден (docs Repository methods). |
T14-L6 2.55 c | Doctrine | DoctrineBundle in Symfony automatically calls flush() at the end of every request. | «no» Пояснение: DoctrineBundle does not automatically call flush() at the end of a request; you must explicitly call $entityManager->flush() yourself (e.g., in a controller or service).
Raw{"answer": "no", "explanation": "DoctrineBundle does not automatically call flush() at the end of a request; you must explicitly call $entityManager->flush() yourself (e.g., in a controller or service)."} | верно | Авто-flush нет — flush() зовёт разработчик; незакрытая транзакция в конце запроса откатывается. |
T14-L7 1.8 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» Пояснение: For managed entities, the Unit of Work tracks property changes via its identity map, and flush() commits them without needing an explicit persist() call.
Raw{"answer": "yes", "explanation": "For managed entities, the Unit of Work tracks property changes via its identity map, and flush() commits them without needing an explicit persist() call."} | верно | Dirty checking сравнивает снимки свойств; persist нужен только новым/отсоединённым объектам. |
T14-L8 1.06 c | Doctrine | remove() executes the SQL DELETE immediately, without waiting for flush(). | «no» Пояснение: In Doctrine ORM, remove() only marks the entity as removed in the UnitOfWork; the actual SQL DELETE is executed when flush() is called.
Raw{"answer": "no", "explanation": "In Doctrine ORM, remove() only marks the entity as removed in the UnitOfWork; the actual SQL DELETE is executed when flush() is called."} | верно | remove() планирует удаление в Unit of Work; DELETE выполняется на flush() (docs — Deleting Objects). |
T15-L1 1.17 c | PostgreSQL | PostgreSQL uses MVCC, therefore readers block writers and writers block readers. | «no» Пояснение: MVCC in PostgreSQL specifically allows readers and writers to proceed concurrently without blocking each other, which is the opposite of what the statement claims.
Raw{"answer": "no", "explanation": "MVCC in PostgreSQL specifically allows readers and writers to proceed concurrently without blocking each other, which is the opposite of what the statement claims."} | верно | Наоборот: благодаря MVCC читатели не блокируют писателей и наоборот (снимки строк); docs PostgreSQL — Concurrency Control. |
T15-L2 1.06 c | PostgreSQL | Which SQL command shows a query's execution plan without executing the query? | «explain» Пояснение: The EXPLAIN SQL command displays the query execution plan (how the database will process the query) without actually running it.
Raw{"answer": "EXPLAIN", "explanation": "The EXPLAIN SQL command displays the query execution plan (how the database will process the query) without actually running it."} | верно | EXPLAIN без ANALYZE только строит план; проверено на PostgreSQL 17.7. |
T15-L3 3.22 c | PostgreSQL | SERIAL and GENERATED ... AS IDENTITY are just two names for the same mechanism. | «no» Пояснение: While both use sequences under the hood, SERIAL is a pseudo-type that creates a separate sequence object and sets a default, whereas GENERATED AS IDENTITY is a standard column property with BY DEFAULT/ALWAYS semantics, different catalog storage, and different lifecycle management.
Raw{"answer": "no", "explanation": "While both use sequences under the hood, SERIAL is a pseudo-type that creates a separate sequence object and sets a default, whereas GENERATED AS IDENTITY is a standard column property with BY DEFAULT/ALWAYS semantics, different catalog storage, and different lifecycle management."} | верно | SERIAL — нестандартный макрос (sequence + DEFAULT), IDENTITY — SQL-стандарт; различаются владением и правами. Оба есть в PG 17 (проверено). |
T15-L4 1.55 c | PostgreSQL | By default, a PostgreSQL UNIQUE constraint allows only one row with NULL in the column. | «no» Пояснение: In PostgreSQL, NULL values are considered distinct from each other, so a UNIQUE constraint allows multiple rows with NULL by default (you need UNIQUE NULLS NOT DISTINCT, added in PG 15, to restrict it to one).
Raw{"answer": "no", "explanation": "In PostgreSQL, NULL values are considered distinct from each other, so a UNIQUE constraint allows multiple rows with NULL by default (you need UNIQUE NULLS NOT DISTINCT, added in PG 15, to restrict it to one)."} | верно | Наоборот: NULLS DISTINCT по умолчанию — несколько NULL допустимы; NULLS NOT DISTINCT — опция с PG 15. Проверено на PG 17.7. |
T15-L5 0.5 c | PostgreSQL | Which PostgreSQL aggregate function concatenates strings with a separator? | «string_agg» Пояснение: string_agg(expression, delimiter) is the PostgreSQL aggregate function that concatenates strings with a specified separator.
Raw{"answer": "string_agg", "explanation": "string_agg(expression, delimiter) is the PostgreSQL aggregate function that concatenates strings with a specified separator."} | верно | string_agg(значение, разделитель); проверено на PostgreSQL 17.7. |
T15-L6 1.24 c | PostgreSQL | Plain VACUUM returns the space occupied by dead tuples to the operating system. | «no» Пояснение: Plain VACUUM marks the space of dead tuples as reusable within the table but does not return it to the operating system; only VACUUM FULL rewrites the table and shrinks the file.
Raw{"answer": "no", "explanation": "Plain VACUUM marks the space of dead tuples as reusable within the table but does not return it to the operating system; only VACUUM FULL rewrites the table and shrinks the file."} | верно | VACUUM помечает место для переиспользования внутри таблицы; ОС его возвращает только VACUUM FULL (с эксклюзивной блокировкой). |
T15-L7 0.84 c | PostgreSQL | Which keyword in a window function definition partitions rows into groups the function is computed over? | «partition» Пояснение: The PARTITION BY clause within the OVER() window function definition divides rows into groups over which the function is computed.
Raw{"answer": "PARTITION", "explanation": "The PARTITION BY clause within the OVER() window function definition divides rows into groups over which the function is computed."} | неверно верный: «partition by» | OVER (PARTITION BY ...); проверено на PostgreSQL 17.7. |
T15-L8 1.21 c | PostgreSQL | The READ COMMITTED isolation level protects against non-repeatable reads. | «no» Пояснение: READ COMMITTED only protects against dirty reads; non-repeatable reads are prevented at the REPEATABLE READ level and above.
Raw{"answer": "no", "explanation": "READ COMMITTED only protects against dirty reads; non-repeatable reads are prevented at the REPEATABLE READ level and above."} | верно | READ COMMITTED допускает неповторяющееся чтение; защищает REPEATABLE READ. Проверено: SHOW transaction_isolation → read committed. |
T17-L1 0.83 c | PostgreSQL: transactions and indexes | By default, PostgreSQL wraps each single SQL statement in its own implicit transaction (autocommit). | «yes» Пояснение: By default, PostgreSQL operates in autocommit mode, where each individual SQL statement is wrapped in its own implicit transaction and automatically committed upon completion.
Raw{"answer": "yes", "explanation": "By default, PostgreSQL operates in autocommit mode, where each individual SQL statement is wrapped in its own implicit transaction and automatically committed upon completion."} | верно | Без BEGIN каждый оператор коммитится сам; docs PostgreSQL — Transactions. Проверено на PG 17. |
T17-L2 0.49 c | PostgreSQL: transactions and indexes | Which SQL command ends a transaction, committing all its changes? | «commit» Пояснение: The COMMIT SQL command ends a transaction and permanently saves all changes made during that transaction.
Raw{"answer": "COMMIT", "explanation": "The COMMIT SQL command ends a transaction and permanently saves all changes made during that transaction."} | верно | COMMIT (END — синоним). Проверено на PG 17. |
T17-L3 1.02 c | PostgreSQL: transactions and indexes | Indexes speed up more than SELECT: UPDATE and DELETE with a search on an indexed column benefit too. | «yes» Пояснение: Indexes help the database engine locate rows quickly for any DML operation (SELECT, UPDATE, DELETE) whose WHERE clause targets an indexed column, avoiding a full table scan.
Raw{"answer": "yes", "explanation": "Indexes help the database engine locate rows quickly for any DML operation (SELECT, UPDATE, DELETE) whose WHERE clause targets an indexed column, avoiding a full table scan."} | верно | Поиск строк для изменения идёт по индексу; docs PostgreSQL — Indexes. |
T17-L4 1.01 c | PostgreSQL: transactions and indexes | To roll back part of the statements inside a transaction, PostgreSQL uses SAVEPOINT. | «yes» Пояснение: SAVEPOINT in PostgreSQL allows you to roll back to a specific point within a transaction, effectively undoing only the statements executed after that savepoint.
Raw{"answer": "yes", "explanation": "SAVEPOINT in PostgreSQL allows you to roll back to a specific point within a transaction, effectively undoing only the statements executed after that savepoint."} | верно | SAVEPOINT name; ROLLBACK TO name — частичный откат без отмены всей транзакции. Проверено на PG 17. |
T17-L5 1.55 c | PostgreSQL: transactions and indexes | EXPLAIN ANALYZE shows the query plan without executing the query. | «no» Пояснение: EXPLAIN ANALYZE actually executes the query and reports real timing and row counts, whereas plain EXPLAIN shows the plan without executing.
Raw{"answer": "no", "explanation": "EXPLAIN ANALYZE actually executes the query and reports real timing and row counts, whereas plain EXPLAIN shows the plan without executing."} | верно | Наоборот: ANALYZE реально выполняет запрос (с побочными эффектами!) и показывает фактические времена узлов; план без выполнения — plain EXPLAIN. |
T17-L6 0.71 c | PostgreSQL: transactions and indexes | Which PostgreSQL extension adds vector types and indexes for embedding search? | «pgvector» Пояснение: pgvector is the PostgreSQL extension that adds vector data types and approximate nearest-neighbor indexes (IVFFlat, HNSW) for embedding similarity search.
Raw{"answer": "pgvector", "explanation": "pgvector is the PostgreSQL extension that adds vector data types and approximate nearest-neighbor indexes (IVFFlat, HNSW) for embedding similarity search."} | верно | CREATE EXTENSION vector (проект pgvector; в проекте образ pgvector/pgvector:pg17). |
T17-L7 1.81 c | PostgreSQL: transactions and indexes | A partial index (CREATE INDEX ... WHERE ...) is built only over rows satisfying the condition. | «yes» Пояснение: A partial index (e.g., in PostgreSQL) only stores index entries for rows that satisfy the WHERE condition, leaving the rest unindexed.
Raw{"answer": "yes", "explanation": "A partial index (e.g., in PostgreSQL) only stores index entries for rows that satisfy the WHERE condition, leaving the rest unindexed."} | верно | docs PostgreSQL — Partial Indexes; типичный кейс — индекс по «активным» записям. |
T17-L8 2.08 c | PostgreSQL: transactions and indexes | The SERIALIZABLE level in PostgreSQL is implemented by locking the rows a transaction reads. | «no» Пояснение: PostgreSQL implements SERIALIZABLE using Serializable Snapshot Isolation (SSI), which detects conflicts after the fact rather than preemptively locking all rows a transaction reads.
Raw{"answer": "no", "explanation": "PostgreSQL implements SERIALIZABLE using Serializable Snapshot Isolation (SSI), which detects conflicts after the fact rather than preemptively locking all rows a transaction reads."} | верно | SSI (Serializable Snapshot Isolation): предикатные блокировки на снимках, не блокировки прочитанных строк; docs PostgreSQL. |
T19-L1 0.78 c | HTTP and REST API | HTTP status 201 means the request resulted in a new resource being created. | «yes» Пояснение: HTTP status 201 'Created' indicates that the request was successful and a new resource was created as a result.
Raw{"answer": "yes", "explanation": "HTTP status 201 'Created' indicates that the request was successful and a new resource was created as a result."} | верно | 201 Created; обычно на POST, часто с Location; RFC 9110. |
T19-L2 1.29 c | HTTP and REST API | Which HTTP status means a successful request with an empty response body (e.g. after DELETE)? | «204» Пояснение: HTTP 204 No Content indicates a successful request with an empty response body, commonly used after DELETE operations.
Raw{"answer": 204, "explanation": "HTTP 204 No Content indicates a successful request with an empty response body, commonly used after DELETE operations."} | верно | 204 No Content; RFC 9110. |
T19-L3 3.99 c | HTTP and REST API | The DELETE method is idempotent per the HTTP specification: repeating the request for the same resource does not change the outcome. | «yes» Пояснение: Per RFC 2616 and RFC 9110, DELETE is listed as an idempotent method: repeating the request does not change the resource state (a second DELETE on an already-deleted resource is a no-op, yielding the same end state).
Raw{"answer": "yes", "explanation": "Per RFC 2616 and RFC 9110, DELETE is listed as an idempotent method: repeating the request does not change the resource state (a second DELETE on an already-deleted resource is a no-op, yielding the same end state)."} | верно | RFC 9110: DELETE идемпотентен (как PUT); идемпотентность ≠ безопасность — ресурс удаляется при первом вызове. |
T19-L4 1.0 c | HTTP and REST API | The Access-Control-Allow-Origin header is sent by the client so that the server agrees to accept requests from another origin. | «no» Пояснение: The Access-Control-Allow-Origin header is sent by the server (not the client) to indicate which origin(s) are permitted to access the resource.
Raw{"answer": "no", "explanation": "The Access-Control-Allow-Origin header is sent by the server (not the client) to indicate which origin(s) are permitted to access the resource."} | верно | Наоборот: заголовок шлёт СЕРВЕР в ответе, разрешая браузеру cross-origin запрос (CORS); в проекте nelmio/cors-bundle. |
T19-L5 0.78 c | HTTP and REST API | Status 429 Too Many Requests is used when a client exceeds a rate limit. | «yes» Пояснение: HTTP 429 Too Many Requests is specifically defined for rate limiting, indicating the client has sent too many requests in a given time frame.
Raw{"answer": "yes", "explanation": "HTTP 429 Too Many Requests is specifically defined for rate limiting, indicating the client has sent too many requests in a given time frame."} | верно | 429 (+ Retry-After); RFC 6585. В проекте symfony/rate-limiter. |
T19-L6 0.96 c | HTTP and REST API | 5xx codes mean a client error, while 4xx means a server-side error. | «no» Пояснение: It's the opposite: 4xx codes indicate client errors (e.g., 404, 400), while 5xx codes indicate server errors (e.g., 500, 503).
Raw{"answer": "no", "explanation": "It's the opposite: 4xx codes indicate client errors (e.g., 404, 400), while 5xx codes indicate server errors (e.g., 500, 503)."} | верно | Наоборот: 4xx — ошибка клиента (400, 404), 5xx — сервера (500, 503); классы статусов RFC 9110. |
T19-L7 0.53 c | HTTP and REST API | Which HTTP header indicates the MIME type of the request or response body? | «content-type» Пояснение: The Content-Type HTTP header specifies the MIME type of the request or response body.
Raw{"answer": "Content-Type", "explanation": "The Content-Type HTTP header specifies the MIME type of the request or response body."} | верно | Content-Type: application/json и т.п. |
T19-L8 1.64 c | HTTP and REST API | PATCH is not required to be idempotent per RFC 5789, unlike PUT. | «yes» Пояснение: RFC 5789 explicitly states that PATCH is not idempotent, while PUT (defined in RFC 7231) is required to be idempotent.
Raw{"answer": "yes", "explanation": "RFC 5789 explicitly states that PATCH is not idempotent, while PUT (defined in RFC 7231) is required to be idempotent."} | верно | RFC 5789 прямо оговаривает: PATCH не гарантированно идемпотентен; PUT идемпотентен. |
T20-L1 1.65 c | Security and OAuth | Checking a password by comparing its hash to the stored hash with a plain == is sufficient. | «no» Пояснение: A plain '==' comparison is vulnerable to timing attacks and loose type juggling; you should use hash_equals() for a constant-time, strict comparison of password hashes.
Raw{"answer": "no", "explanation": "A plain '==' comparison is vulnerable to timing attacks and loose type juggling; you should use hash_equals() for a constant-time, strict comparison of password hashes."} | верно | Нужна постоянновременная проверка (password_verify) — timing-атаки; соль и алгоритм уже внутри хеша. |
T20-L2 1.46 c | Security and OAuth | A CSRF token is issued by the server (bound to the session) and verified server-side on unsafe requests (POST etc.). | «yes» Пояснение: CSRF tokens are generated server-side, tied to the user's session, and validated on the server for state-changing requests like POST, PUT, or DELETE to ensure the request originated from the legitimate application.
Raw{"answer": "yes", "explanation": "CSRF tokens are generated server-side, tied to the user's session, and validated on the server for state-changing requests like POST, PUT, or DELETE to ensure the request originated from the legitimate application."} | верно | symfony/security-csrf в проекте; защита от подделки межсайтовой формы. |
T20-L3 0.89 c | Security and OAuth | Which HTTP header enables the CSP (Content Security Policy) policy? | «content-security-policy» Пояснение: The Content-Security-Policy HTTP header is used to declare and enforce a Content Security Policy for a web resource.
Raw{"answer": "Content-Security-Policy", "explanation": "The Content-Security-Policy HTTP header is used to declare and enforce a Content Security Policy for a web resource."} | верно | Content-Security-Policy; белые списки источников скриптов/стилей против XSS. |
T20-L4 1.98 c | Security and OAuth | OAuth 2.0 is an authentication protocol: the access token tells you who the user is. | «no» Пояснение: OAuth 2.0 is an authorization protocol, not an authentication protocol; it grants access to resources via tokens rather than identifying who the user is (that is the role of OpenID Connect built on top of OAuth 2.0).
Raw{"answer": "no", "explanation": "OAuth 2.0 is an authorization protocol, not an authentication protocol; it grants access to resources via tokens rather than identifying who the user is (that is the role of OpenID Connect built on top of OAuth 2.0)."} | верно | OAuth 2.0 — авторизация/делегирование доступа; аутентификацию добавляет OpenID Connect. В проекте knpuniversity/oauth2-client-bundle (yandex/github/google). |
T20-L5 1.55 c | Security and OAuth | XSS is prevented by validating input on the server before writing it to the database. | «no» Пояснение: XSS is primarily prevented by encoding/escaping output when it is rendered in the browser, not by validating input before storing it in the database.
Raw{"answer": "no", "explanation": "XSS is primarily prevented by encoding/escaping output when it is rendered in the browser, not by validating input before storing it in the database."} | верно | XSS лечится контекстным экранированием НА ВЫВОДЕ (Twig autoescape, CSP); валидация ввода не покрывает все контексты вывода. |
T20-L6 0.93 c | Security and OAuth | In the OAuth 2.0 authorization code flow, which parameter arrives at the redirect_uri and is exchanged for an access token? | «code» Пояснение: In the OAuth 2.0 authorization code flow, the 'code' parameter is returned to the redirect_uri and subsequently exchanged for an access token at the token endpoint.
Raw{"answer": "code", "explanation": "In the OAuth 2.0 authorization code flow, the 'code' parameter is returned to the redirect_uri and subsequently exchanged for an access token at the token endpoint."} | верно | Параметр code; обмен на токен POST-ом на /token с client_secret. |
T20-L7 1.16 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 indeed longer-lived than access tokens and are specifically designed to obtain new access tokens without requiring the user to log in again.
Raw{"answer": "yes", "explanation": "Refresh tokens are indeed longer-lived than access tokens and are specifically designed to obtain new access tokens without requiring the user to log in again."} | верно | Стандартная схема OAuth/OIDC: короткий access + длинный refresh. |
T20-L8 1.26 c | Security and OAuth | A password salt must be kept secret: without it the hash cannot be verified. | «no» Пояснение: A salt does not need to be secret; it is typically stored alongside the hash so that verification can re-derive the expected hash from the candidate password.
Raw{"answer": "no", "explanation": "A salt does not need to be secret; it is typically stored alongside the hash so that verification can re-derive the expected hash from the candidate password."} | верно | Соль хранится открыто (password_hash включает её в строку хеша); секретность соли не нужна. |
T18-L1 1.38 c | Testing: PHPUnit | PHPUnit runs test methods of any class — extending TestCase is not required. | «no» Пояснение: PHPUnit requires test classes to extend PHPUnit\Framework\TestCase in order to be recognized and executed by the test runner.
Raw{"answer": "no", "explanation": "PHPUnit requires test classes to extend PHPUnit\\Framework\\TestCase in order to be recognized and executed by the test runner."} | верно | Тестом считается метод класса, наследующего TestCase (PHPUnit 10). |
T18-L2 0.82 c | Testing: PHPUnit | In PHPUnit, setUp() runs once before all tests of the class. | «no» Пояснение: setUp() runs before each test method; setUpBeforeClass() is the one that runs once before all tests in the class.
Raw{"answer": "no", "explanation": "setUp() runs before each test method; setUpBeforeClass() is the one that runs once before all tests in the class."} | верно | setUp() — перед КАЖДЫМ тестом; один раз на класс — setUpBeforeClass(). Проверено живым счётчиком на PHPUnit 10.5. |
T18-L3 1.01 c | Testing: PHPUnit | A data provider lets a test run with exactly one set of arguments. | «no» Пояснение: A data provider's purpose is to supply multiple sets of arguments so the test runs once per data set, not just once.
Raw{"answer": "no", "explanation": "A data provider's purpose is to supply multiple sets of arguments so the test runs once per data set, not just once."} | верно | Наоборот: наборов может быть сколько угодно — тест выполняется по разу на каждый. Проверено на PHPUnit 10.5 (#[DataProvider]). |
T18-L4 0.75 c | Testing: PHPUnit | Which PHPUnit method declares an expectation that an exception of a given class is thrown? | «expectexception» Пояснение: PHPUnit's expectException() method declares that an exception of the specified class is expected to be thrown.
Raw{"answer": "expectException", "explanation": "PHPUnit's expectException() method declares that an exception of the specified class is expected to be thrown."} | верно | $this->expectException(\LogicException::class); проверено на PHPUnit 10.5. |
T18-L5 1.07 c | Testing: PHPUnit | In PHPUnit, a stub verifies which methods were called on it, while a mock only returns data. | «no» Пояснение: It's the opposite: a stub only returns predefined data, while a mock both returns data and verifies expectations about method calls.
Raw{"answer": "no", "explanation": "It's the opposite: a stub only returns predefined data, while a mock both returns data and verifies expectations about method calls."} | верно | Наоборот: стаб подставляет данные, мок проверяет взаимодействия (createStub/createMock); docs PHPUnit — Test Doubles. |
T18-L6 0.99 c | Testing: PHPUnit | In PHPUnit 10+, the recommended way to pass data to a test is the #[DataProvider] attribute (the @dataProvider annotation is deprecated). | «yes» Пояснение: In PHPUnit 10+, the #[DataProvider] attribute is the recommended approach, while the @dataProvider docblock annotation is deprecated.
Raw{"answer": "yes", "explanation": "In PHPUnit 10+, the #[DataProvider] attribute is the recommended approach, while the @dataProvider docblock annotation is deprecated."} | верно | Аннотация ещё парсится в PHPUnit 10/11 (AnnotationParser в 10.5.66), удаление — в 12; атрибут — стандарт. |
T18-L7 0.78 c | Testing: PHPUnit | PHPUnit does not allow one test to depend on the result of another. | «no» Пояснение: PHPUnit supports test dependencies via the @depends annotation or the depends() method, allowing one test to receive the return value of another as a parameter.
Raw{"answer": "no", "explanation": "PHPUnit supports test dependencies via the @depends annotation or the depends() method, allowing one test to receive the return value of another as a parameter."} | верно | Зависимости есть: #[Depends] — зависимый тест не запустится, еслиProducer упал. |
T18-L8 1.94 c | Testing: PHPUnit | Which PHPUnit command-line option makes tests run in random order? | «--random-order» Пояснение: PHPUnit's --random-order command-line option shuffles the test execution order to a random sequence.
Raw{"answer": "--random-order", "explanation": "PHPUnit's --random-order command-line option shuffles the test execution order to a random sequence."} | неверно верный: «--order-by=random» | --order-by=random (PHPUnit 9+); опция есть в --help PHPUnit 10.5 (проектная). |
T01-L9 4.21 c | Syntax and operators | What does this code output?
```php
echo intdiv(7, 2) . intdiv(-7, 2);
``` | «3-3» Пояснение: intdiv(7,2) truncates 3.5 to 3, intdiv(-7,2) truncates -3.5 toward zero to -3, and the dot operator concatenates them into the string '3-3'.
Raw{"answer": "3-3", "explanation": "intdiv(7,2) truncates 3.5 to 3, intdiv(-7,2) truncates -3.5 toward zero to -3, and the dot operator concatenates them into the string '3-3'."} | верно | intdiv truncates toward zero: intdiv(-7, 2) = -3, not -4. |
T01-L10 1.32 c | Syntax and operators | What does this code output?
```php
echo -3 ** 2;
``` | «-9» Пояснение: In PHP, the ** operator has higher precedence than the unary minus, so -3 ** 2 is parsed as -(3 ** 2) = -9.
Raw{"answer": -9, "explanation": "In PHP, the ** operator has higher precedence than the unary minus, so -3 ** 2 is parsed as -(3 ** 2) = -9."} | верно | ** is right-associative and binds tighter than unary minus: -(3²). |
T02-L9 2.89 c | Types and comparisons | What does this code output?
```php
echo '1e1' == '10' ? 'true' : 'false';
``` | «true» Пояснение: Both '1e1' and '10' are numeric strings, so PHP compares them numerically: 1e1 equals 10, making the expression true.
Raw{"answer": "true", "explanation": "Both '1e1' and '10' are numeric strings, so PHP compares them numerically: 1e1 equals 10, making the expression true."} | верно | Both strings are numeric — compared as numbers: 10 == 10. |
T02-L10 3.43 c | Types and comparisons | What does this code output?
```php
switch ('a') {
case 0: echo 'zero'; break;
default: echo 'other';
}
``` | «other» Пояснение: In PHP 8, the string 'a' is not equal to 0 under loose comparison (==), so the switch falls through to the default case and outputs 'other'.
Raw{"answer": "other", "explanation": "In PHP 8, the string 'a' is not equal to 0 under loose comparison (==), so the switch falls through to the default case and outputs 'other'."} | верно | PHP 8: 'a' == 0 → false (used to be true) — default fires. |
T03-L9 2.6 c | Strings | What does this code output?
```php
echo strtr('abc', ['a' => '1', 'ab' => '2']);
``` | «2c» Пояснение: strtr with an array replaces the longest matching key first, so 'ab' (length 2) is matched before 'a' (length 1), turning 'abc' into '2c'.
Raw{"answer": "2c", "explanation": "strtr with an array replaces the longest matching key first, so 'ab' (length 2) is matched before 'a' (length 1), turning 'abc' into '2c'."} | верно | strtr with an array prefers the longest matching key. |
T03-L10 4.04 c | Strings | What does this code output?
```php
echo '[' . substr('hello', -10) . ']';
``` | «[]» Пояснение: substr('hello', -10) returns an empty string because the negative start position (-10) goes beyond the 5-character string, so the result is '[]'.
Raw{"answer": "[]", "explanation": "substr('hello', -10) returns an empty string because the negative start position (-10) goes beyond the 5-character string, so the result is '[]'."} | неверно верный: «[hello]» | A negative start beyond the string is clamped to the beginning. |
T04-L9 1.64 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 performs array union, keeping left-side values for duplicate keys, so the result is ['k'=>1,'n'=>2,'m'=>3'], and array_keys gives ['k','n','m'].
Raw{"answer": "k,n,m", "explanation": "The + operator performs array union, keeping left-side values for duplicate keys, so the result is ['k'=>1,'n'=>2,'m'=>3'], and array_keys gives ['k','n','m']. "} | верно | The + operator: on duplicate string keys the left array wins. |
T04-L10 2.05 c | Arrays | What does this code output?
```php
$a = [[1, 'x', 2], [2, 'y', 1], [3, 'z', 2]];
usort($a, fn($p, $q) => $p[2] <=> $q[2]);
echo implode('', array_column($a, 1));
``` | «yxz» Пояснение: usort sorts by the 3rd element (index 2) ascending, yielding [2,'y',1], [1,'x',2], [3,'z',2]; array_column then extracts index 1 giving ['y','x','z'], and implode concatenates to 'yxz'.
Raw{"answer": "yxz", "explanation": "usort sorts by the 3rd element (index 2) ascending, yielding [2,'y',1], [1,'x',2], [3,'z',2]; array_column then extracts index 1 giving ['y','x','z'], and implode concatenates to 'yxz'."} | верно | Sorts are stable since 8.0: x and z keep their order on a tie. |
T05-L10 4.6 c | Functions and closures | What does this code output?
```php
function f(int $a, int $b): int
{
return $a - $b;
}
echo f(...['b' => 1, 'a' => 5]);
``` | «4» Пояснение: The spread operator with string keys maps 'a' => 5 and 'b' => 1 by name, so f(5, 1) returns 5 - 1 = 4.
Raw{"answer": 4, "explanation": "The spread operator with string keys maps 'a' => 5 and 'b' => 1 by name, so f(5, 1) returns 5 - 1 = 4."} | верно | String keys of a spread array become named arguments. |
T05-L9 10.49 c | Functions and closures | What does this code output?
```php
class P
{
private int $v = 3;
public function g(): int { return $this->v; }
}
$p = new P;
$f = $p->g(...);
$p = null;
echo $f();
``` | «3» Пояснение: The first-class callable syntax $p->g(...) captures the object handle into the closure, so setting $p = null doesn't affect the closure's internal reference; calling $f() still invokes g() on the P object and returns 3.
Raw{"answer": 3, "explanation": "The first-class callable syntax $p->g(...) captures the object handle into the closure, so setting $p = null doesn't affect the closure's internal reference; calling $f() still invokes g() on the P object and returns 3."} | верно | First-class callable syntax binds $this at creation time. |
T06-L9 0.88 c | OOP: classes and inheritance | What does this code output?
```php
class A
{
public function who(): string { return static::class; }
}
class B extends A {}
echo (new B)->who();
``` | «b» Пояснение: static::class uses late static binding, so it resolves to the class of the actual object instance, which is B.
Raw{"answer": "B", "explanation": "static::class uses late static binding, so it resolves to the class of the actual object instance, which is B."} | верно | Late static binding: static::class is the receiver's class. |
T06-L10 4.27 c | OOP: classes and inheritance | What does this code output on PHP 8.5?
```php
class C
{
public int $x = 0 {
set { $this->x = $value * 2; }
}
}
$c = new C;
$c->x = 5;
echo $c->x;
``` | «10» Пояснение: The set hook multiplies the assigned value by 2 (5*2=10), and assigning $this->x inside the set hook stores directly without re-triggering the hook.
Raw{"answer": 10, "explanation": "The set hook multiplies the assigned value by 2 (5*2=10), and assigning $this->x inside the set hook stores directly without re-triggering the hook."} | верно | Inside the set hook, $this->x writes the backing store (no recursion): 5*2. |
T07-L9 1.17 c | Interfaces, traits, enum | What does this code output?
```php
trait TA
{
public function f(): string { return 'A'; }
}
trait TB
{
public function f(): string { return 'B'; }
}
class TC
{
use TA, TB { TB::f insteadof TA; TA::f as g; }
}
echo (new TC)->f() . (new TC)->g();
``` | «ba» Пояснение: TB::f insteadof TA makes f() return 'B', and TA::f as g aliases TA's f as g returning 'A', so the output is 'BA'.
Raw{"answer": "BA", "explanation": "TB::f insteadof TA makes f() return 'B', and TA::f as g aliases TA's f as g returning 'A', so the output is 'BA'."} | верно | insteadof picks the implementation; as keeps the other under an alias. |
T07-L10 1.44 c | Interfaces, traits, enum | What does this code output?
```php
trait Counter
{
public static int $n = 0;
}
class CX { use Counter; }
class CY { use Counter; }
CX::$n = 1;
echo CY::$n;
``` | «0» Пояснение: Each class that uses a trait gets its own independent copy of static properties, so CY::$n remains 0 while CX::$n is set to 1.
Raw{"answer": 0, "explanation": "Each class that uses a trait gets its own independent copy of static properties, so CY::$n remains 0 while CX::$n is set to 1."} | верно | A trait's static property is copied into each consuming class. |
T08-L10 1.15 c | Exceptions and errors | What does this code output?
```php
function f(): int
{
try { return 1; } finally { return 2; }
}
echo f();
``` | «2» Пояснение: In PHP, a return statement in a finally block overrides any return statement in the try block, so the function returns 2.
Raw{"answer": 2, "explanation": "In PHP, a return statement in a finally block overrides any return statement in the try block, so the function returns 2."} | верно | A return in finally overrides the return from try. |
T08-L9 1.46 c | Exceptions and errors | What does this code output?
```php
try {
try {
throw new RuntimeException('first');
} finally {
throw new LogicException('second');
}
} catch (LogicException $e) {
echo $e->getMessage();
}
``` | «second» Пояснение: The finally block throws a LogicException('second'), which replaces the original RuntimeException, and the outer catch catches the LogicException and prints its message.
Raw{"answer": "second", "explanation": "The finally block throws a LogicException('second'), which replaces the original RuntimeException, and the outer catch catches the LogicException and prints its message."} | верно | An exception from finally replaces the in-flight one — the last thrown is caught. |
T09-L9 1.46 c | Namespaces and autoloading | What does this code output?
```php
namespace N;
use App\Foo as Baz;
echo Baz::class . '|' . \Baz::class;
``` | «app\foo|baz» Пояснение: Baz::class resolves to App\Foo via the use alias, while \Baz::class refers to the global Baz class, yielding 'App\Foo|Baz'.
Raw{"answer": "App\\Foo|Baz", "explanation": "Baz::class resolves to App\\Foo via the use alias, while \\Baz::class refers to the global Baz class, yielding 'App\\Foo|Baz'."} | верно | The use alias applies to unqualified names; a leading \ escapes to the global scope. |
T09-L10 2.8 c | Namespaces and autoloading | What does this code output?
```php
namespace Ns;
class Foo {}
$c = 'Foo';
echo (class_exists($c) ? 'yes' : 'no')
. (class_exists(__NAMESPACE__ . '\\' . $c) ? 'yes' : 'no');
``` | «noyes» Пояснение: class_exists('Foo') looks for a global class Foo (not found, gives 'no'), while class_exists('Ns\Foo') finds the namespaced class (gives 'yes'), concatenating to 'noyes'.
Raw{"answer": "noyes", "explanation": "class_exists('Foo') looks for a global class Foo (not found, gives 'no'), while class_exists('Ns\\Foo') finds the namespaced class (gives 'yes'), concatenating to 'noyes'."} | верно | Dynamic names are not resolved against the namespace — 'Foo' is the global class. |
T10-L9 1.34 c | References and scope | What does this code output?
```php
$a = [1, 2, 3];
foreach ($a as &$v) {}
$v = 99;
echo implode(',', $a);
``` | «1,2,99» Пояснение: After a foreach by reference, $v remains a reference to the last element of $a, so assigning 99 to $v modifies $a[2].
Raw{"answer": "1,2,99", "explanation": "After a foreach by reference, $v remains a reference to the last element of $a, so assigning 99 to $v modifies $a[2]."} | верно | After a by-ref foreach, $v remains a reference to the last element. |
T10-L10 3.37 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» Пояснение: The local static variable $n is shared between A and B since B inherits the method; successive calls increment it to 1, 2, 3, and the third call outputs 3.
Raw{"answer": 3, "explanation": "The local static variable $n is shared between A and B since B inherits the method; successive calls increment it to 1, 2, 3, and the third call outputs 3."} | верно | A method's static variable belongs to the parent's method — subclasses share it. |
T11-L9 1.23 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» Пояснение: The generator yields 1, receives 10 via send(), assigns it to $x, then returns $x + 1 = 11, which is retrieved by getReturn().
Raw{"answer": 11, "explanation": "The generator yields 1, receives 10 via send(), assigns it to $x, then returns $x + 1 = 11, which is retrieved by getReturn()."} | верно | send() resumes the generator: $x = 10, return 10+1. |
T11-L10 1.85 c | Generators, iterators, SPL | What does this code output?
```php
function inner(): Generator
{
yield 1;
yield 2;
return 'ok';
}
function outer(): Generator
{
$r = yield from inner();
yield $r;
}
echo implode(',', iterator_to_array(outer()));
``` | «1,2,ok» Пояснение: yield from inner() delegates yielding 1 and 2 to the caller, assigns the return value 'ok' to $r, then outer yields 'ok', producing the sequence 1, 2, 'ok' which implode joins as '1,2,ok'.
Raw{"answer": "1,2,ok", "explanation": "yield from inner() delegates yielding 1 and 2 to the caller, assigns the return value 'ok' to $r, then outer yields 'ok', producing the sequence 1, 2, 'ok' which implode joins as '1,2,ok'."} | неверно верный: «ok,2» | yield from does not advance the outer auto-key: yield $r gets key 0 and overwrites the 1 — 'ok' comes out first. |
T12-L9 1.52 c | Configuration and security | What does this code output?
```php
$hash = password_hash('x', PASSWORD_BCRYPT, ['cost' => 4]);
echo password_needs_rehash($hash, PASSWORD_BCRYPT, ['cost' => 4]) ? 'yes' : 'no';
echo password_needs_rehash($hash, PASSWORD_BCRYPT, ['cost' => 5]) ? 'yes' : 'no';
``` | «noyes» Пояснение: password_needs_rehash returns false when cost matches (4==4, prints 'no') and true when cost differs (4!=5, prints 'yes'), so the concatenated output is 'noyes'.
Raw{"answer": "noyes", "explanation": "password_needs_rehash returns false when cost matches (4==4, prints 'no') and true when cost differs (4!=5, prints 'yes'), so the concatenated output is 'noyes'."} | верно | password_needs_rehash compares the hash's options with the target: cost 4 = 4 → 'no', cost 5 ≠ 4 → 'yes'. |
T12-L10 4.2 c | Configuration and security | What does this code output on PHP 8.5?
```php
echo (E_ALL & 2048) === 0 ? 'strict-out' : 'strict-in';
``` | «strict-in» Пояснение: E_ALL includes E_STRICT (2048), so (E_ALL & 2048) equals 2048, which is not === 0, so the ternary returns 'strict-in'.
Raw{"answer": "strict-in", "explanation": "E_ALL includes E_STRICT (2048), so (E_ALL & 2048) equals 2048, which is not === 0, so the ternary returns '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 2.02 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 converts the HTTP_X_TOKEN server variable into the header 'X-Token', so headers->get('X-Token') returns 'abc'.
Raw{"answer": "mapped", "explanation": "Symfony converts the HTTP_X_TOKEN server variable into the header 'X-Token', so headers->get('X-Token') returns 'abc'."} | верно | The literal comparison requires knowing the mapping: HttpFoundation turns HTTP_X_TOKEN into the X-Token header (case-insensitive); without it the answer is 'missing'. |
T13-L10 1.15 c | Symfony | What does this code output?
```php
use Symfony\Component\EventDispatcher\EventDispatcher;
use Symfony\Contracts\EventDispatcher\Event;
$d = new EventDispatcher();
$out = '';
$d->addListener('e', function () use (&$out) { $out .= 'B'; }, 10);
$d->addListener('e', function () use (&$out) { $out .= 'A'; });
$d->addListener('e', function () use (&$out) { $out .= 'C'; }, 5);
$d->dispatch(new Event(), 'e');
echo $out;
``` | «bca» Пояснение: Symfony EventDispatcher calls listeners in descending priority order: priority 10 (B), priority 5 (C), priority 0 (A).
Raw{"answer": "BCA", "explanation": "Symfony EventDispatcher calls listeners in descending priority order: priority 10 (B), priority 5 (C), priority 0 (A)."} | верно | Listeners run by descending priority: 10 (B), 5 (C), 0 (A). |
T14-L10 1.99 c | Doctrine | Given: Doctrine ORM 3, an EntityManager on in-memory SQLite, entity User with an auto-increment primary key. The users table is empty. What does this code output?
```php
$u = new User(name: 'A');
$em->persist($u);
$em->flush();
$a = $em->find(User::class, $u->getId());
$b = $em->find(User::class, $u->getId());
echo spl_object_id($a) === spl_object_id($b) ? 'same' : 'diff';
``` | «same» Пояснение: Doctrine ORM's find() checks the first-level identity map before querying the database; since the entity is already managed, both calls return the exact same object instance.
Raw{"answer": "same", "explanation": "Doctrine ORM's find() checks the first-level identity map before querying the database; since the entity is already managed, both calls return the exact same object instance."} | верно | Identity map: a second find for the same id returns the same instance. |
T14-L9 9.06 c | Doctrine | Given: Doctrine ORM 3, an EntityManager on in-memory SQLite, entity User with an auto-increment primary key. The users table is empty. What does this code output?
```php
$u = new User(name: 'B');
$em->persist($u);
$em->remove($u);
$em->flush();
echo count($em->getConnection()->fetchAllAssociative('SELECT * FROM users'));
``` | «0» Пояснение: After persist() the entity is in the 'new' (toInsert) set; remove() moves it to the scheduled-for-deletion set and out of toInsert, so flush() never issues an INSERT, leaving the empty table with 0 rows.
Raw{"answer": 0, "explanation": "After persist() the entity is in the 'new' (toInsert) set; remove() moves it to the scheduled-for-deletion set and out of toInsert, so flush() never issues an INSERT, leaving the empty table with 0 rows."} | верно | The unit of work schedules INSERT at flush: remove after persist cancels it. |
T15-L10 0.86 c | PostgreSQL | What does this SQL query return (PostgreSQL 17)?
```sql
CREATE TEMP TABLE t (x int);
INSERT INTO t VALUES (1), (NULL);
SELECT count(x) FROM t;
``` | «1» Пояснение: COUNT(x) counts only non-NULL values in column x; there is one non-NULL value (1) and one NULL, so the result is 1.
Raw{"answer": 1, "explanation": "COUNT(x) counts only non-NULL values in column x; there is one non-NULL value (1) and one NULL, so the result is 1."} | верно | count(column) skips NULLs; count(*) would return 2. |
T15-L9 1.74 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 running totals 10, 30, 60, which string_agg concatenates with commas in id order.
Raw{"answer": "10,30,60", "explanation": "The window function sum(x) OVER (ORDER BY id) produces running totals 10, 30, 60, which string_agg concatenates with commas in id order."} | верно | With ORDER BY the default window frame is running (start to current row). |
T16-L9 2.0 c | Symfony: Messenger | What does this code output?
```php
use Symfony\Component\Messenger\MessageBus;
use Symfony\Component\Messenger\Middleware\MiddlewareInterface;
use Symfony\Component\Messenger\Middleware\StackInterface;
use Symfony\Component\Messenger\Envelope;
final class Trace implements MiddlewareInterface
{
public function __construct(private string $tag) {}
public function handle(Envelope $e, StackInterface $stack): Envelope
{
echo $this->tag;
return $stack->next()->handle($e, $stack);
}
}
$bus = new MessageBus([new Trace('M1'), new Trace('M2')]);
$bus->dispatch(new Envelope(new stdClass()));
``` | «m1m2» Пояснение: The two Trace middleware execute in order, each echoing its tag before delegating to the next, producing 'M1' then 'M2' concatenated.
Raw{"answer": "M1M2", "explanation": "The two Trace middleware execute in order, each echoing its tag before delegating to the next, producing 'M1' then 'M2' concatenated."} | верно | The first-added middleware runs first (outermost). |
T16-L10 7.92 c | Symfony: Messenger | What does this code output?
```php
use Symfony\Component\Messenger\MessageBus;
use Symfony\Component\Messenger\Middleware\HandleMessageMiddleware;
use Symfony\Component\Messenger\Handler\HandlersLocator;
use Symfony\Component\Messenger\Handler\HandlerDescriptor;
use Symfony\Component\Messenger\Envelope;
class Ping {}
$n = 0;
$d1 = new HandlerDescriptor(function (Ping $m) use (&$n) { $n += 1; }, ['alias' => 'h1']);
$d2 = new HandlerDescriptor(function (Ping $m) use (&$n) { $n += 10; }, ['alias' => 'h2']);
$bus = new MessageBus([
new HandleMessageMiddleware(new HandlersLocator([Ping::class => [$d1, $d2]])),
]);
$bus->dispatch(new Envelope(new Ping()));
echo $n;
``` | «11» Пояснение: HandleMessageMiddleware iterates over all handlers returned by HandlersLocator for the message class, so both closures execute: $n += 1 then $n += 10, resulting in 11.
Raw{"answer": 11, "explanation": "HandleMessageMiddleware iterates over all handlers returned by HandlersLocator for the message class, so both closures execute: $n += 1 then $n += 10, resulting in 11."} | верно | All registered handlers of the message run: 1 + 10 = 11. |
T17-L9 1.44 c | PostgreSQL: transactions and indexes | What does this SQL query return (PostgreSQL 17)?
```sql
CREATE TEMP TABLE t (a int);
CREATE UNIQUE INDEX ON t (a);
INSERT INTO t VALUES (1) ON CONFLICT DO NOTHING;
INSERT INTO t VALUES (1) ON CONFLICT DO NOTHING;
SELECT count(*) FROM t;
``` | «1» Пояснение: The first INSERT succeeds, the second hits the unique index conflict and is skipped due to ON CONFLICT DO NOTHING, leaving exactly 1 row.
Raw{"answer": 1, "explanation": "The first INSERT succeeds, the second hits the unique index conflict and is skipped due to ON CONFLICT DO NOTHING, leaving exactly 1 row."} | верно | ON CONFLICT DO NOTHING skips the duplicate: one insert. |
T17-L10 1.93 c | PostgreSQL: transactions and indexes | What does this sequence of psql commands output?
```sql
BEGIN;
CREATE TEMP TABLE t (a int, UNIQUE (a) DEFERRABLE INITIALLY DEFERRED);
INSERT INTO t VALUES (1);
INSERT INTO t VALUES (1);
SELECT count(*) FROM t;
``` | «2» Пояснение: The UNIQUE constraint is DEFERRABLE INITIALLY DEFERRED, so both inserts succeed within the transaction and the count returns 2 before any commit-time check.
Raw{"answer": 2, "explanation": "The UNIQUE constraint is DEFERRABLE INITIALLY DEFERRED, so both inserts succeed within the transaction and the count returns 2 before any commit-time check."} | верно | DEFERRED postpones the uniqueness check to COMMIT — count sees 2 rows. |
T18-L9 2.15 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» Пояснение: --filter test_sum matches both test_sum (3 data sets) and test_sum_abs (3 data sets) as the filter is a substring/regex match, totaling 6 tests.
Raw{"answer": 6, "explanation": "--filter test_sum matches both test_sum (3 data sets) and test_sum_abs (3 data sets) as the filter is a substring/regex match, totaling 6 tests."} | верно | --filter is a substring match: test_sum also matches test_sum_abs (3+3 datasets). |
T18-L10 1.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 yields two datasets ([1] and [-1]); assertTrue(1>0) passes but assertTrue(-1>0) fails, so 2 ran, 1 failed.
Raw{"answer": "2, 1", "explanation": "The data provider yields two datasets ([1] and [-1]); assertTrue(1>0) passes but assertTrue(-1>0) fails, so 2 ran, 1 failed."} | верно | 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 1.01 c | HTTP and REST API | Which HTTP method does this command send?
```bash
curl -s -d 'a=1' http://demo.local/api
``` | «post» Пояснение: The -d flag in curl sends data in the request body and implicitly sets the HTTP method to POST when no explicit method is specified.
Raw{"answer": "POST", "explanation": "The -d flag in curl sends data in the request body and implicitly sets the HTTP method to POST when no explicit method is specified."} | верно | -d/-F switches curl to POST by default. |
T19-L10 1.31 c | HTTP and REST API | Which HTTP method does this command send?
```bash
curl -s -G -d 'a=1' http://demo.local/api
``` | «get» Пояснение: The -G flag forces curl to use the GET method and append the -d data as a query string to the URL.
Raw{"answer": "GET", "explanation": "The -G flag forces curl to use the GET method and append the -d data as a query string to the URL."} | верно | -G turns -d data into the query string; the method stays GET. |
T20-L9 3.15 c | Security and OAuth | A client hits the token endpoint (RFC 6749) with a non-existent client_id. What value of the error field does the endpoint return? | «unauthorized_client» Пояснение: Per RFC 6749 §5.2, a non-existent (unrecognized) client_id at the token endpoint results in the 'unauthorized_client' error.
Raw{"answer": "unauthorized_client", "explanation": "Per RFC 6749 §5.2, a non-existent (unrecognized) client_id at the token endpoint results in the 'unauthorized_client' error."} | неверно верный: «invalid_client» | Unknown client → invalid_client (RFC 6749 §5.2). |
T20-L10 1.29 c | Security and OAuth | OAuth 2.0: the client started the flow with response_type=token. In which part of the redirect_uri does the authorization server pass the access_token? | «fragment» Пояснение: In the OAuth 2.0 implicit flow (response_type=token), the access token is returned in the URI fragment (after #), not in the query string, so it is not transmitted to the server in subsequent requests.
Raw{"answer": "fragment", "explanation": "In the OAuth 2.0 implicit flow (response_type=token), the access token is returned in the URI fragment (after #), not in the query string, so it is not transmitted to the server in subsequent requests."} | верно | The implicit flow passes the token in the URL fragment (#) — it never reaches the server. |
T21-L9 1.31 c | Twig | What does this Twig template output?
```twig
{{ false|default(2) * 3 }}
``` | «0» Пояснение: The default filter only replaces null values, not false, so false * 3 evaluates to 0.
Raw{"answer": 0, "explanation": "The default filter only replaces null values, not false, so false * 3 evaluates to 0."} | неверно верный: «6» | default replaces exactly false/null/''/[] — false becomes 2, 2*3 = 6; the naive 'default is for undefined only' yields 0. |
T21-L10 34.91 c | Twig | What exception class does render() of this template throw?
```twig
{{ 'a' ~ 1 + 2 }}
``` | «2» Пояснение: In Twig, ~ has higher precedence than +, so the expression is parsed as ('a' ~ 1) + 2, which evaluates to 'a1' + 2 = 2 via PHP's string-to-int coercion.
Raw{"answer": 2, "explanation": "In Twig, ~ has higher precedence than +, so the expression is parsed as ('a' ~ 1) + 2, which evaluates to 'a1' + 2 = 2 via PHP's string-to-int coercion."} | неверно верный: «runtimeerror» | In Twig ~ binds tighter than +: ('a' ~ 1) + 2 → string + int → a render error (RuntimeError). |
T22-L9 13.35 c | Symfony: Security and forms | What does this code output?
```php
use Symfony\Component\Validator\Validation;
use Symfony\Component\Validator\Constraints as Assert;
$v = Validation::createValidator();
echo count($v->validate([''], [new Assert\NotBlank()]));
``` | «0» Пояснение: The array [''] has a count of 1, so the NotBlank constraint (which checks if array count is 0) does not trigger a violation, resulting in 0 violations.
Raw{"answer": 0, "explanation": "The array [''] has a count of 1, so the NotBlank constraint (which checks if array count is 0) does not trigger a violation, resulting in 0 violations."} | верно | NotBlank treats null, '', [] as blank — the array [''] is not blank. |
T22-L10 11.4 c | Symfony: Security and forms | What does this code output?
```php
use Symfony\Component\Form\Forms;
use Symfony\Component\Form\Extension\Core\Type\TextType;
$factory = Forms::createFormFactoryBuilder()->getFormFactory();
$form = $factory->create(TextType::class);
try {
echo $form->isValid() ? 'valid' : 'invalid';
} catch (Throwable $e) {
echo get_class($e);
}
``` | «symfony\component\form\exception\logicexception» Пояснение: Calling isValid() on a Symfony form that has never been submitted throws a LogicException, which is caught and its class name is printed.
Raw{"answer": "Symfony\\Component\\Form\\Exception\\LogicException", "explanation": "Calling isValid() on a Symfony form that has never been submitted throws a LogicException, which is caught and its class name is printed."} | верно | isValid() on a non-submitted form throws LogicException, it does not return false. |
T23-L9 2.24 c | Symfony: configuration and services | What does this code output?
```php
use Symfony\Component\DependencyInjection\ContainerBuilder;
$c = new ContainerBuilder();
$c->register('a', stdClass::class)->setPublic(true);
$c->compile();
echo spl_object_id($c->get('a')) === spl_object_id($c->get('a')) ? 'same' : 'diff';
``` | «same» Пояснение: Symfony DI container services are singletons by default, so get('a') returns the same cached stdClass instance both times.
Raw{"answer": "same", "explanation": "Symfony DI container services are singletons by default, so get('a') returns the same cached stdClass instance both times."} | верно | Container services are shared: two get() calls yield one instance. |
T23-L10 25.93 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!» Пояснение: The parameter 'message' is '%greeting!%' which resolves '%greeting%' to 'hi %name%', then '%name%' resolves to 'Bob', yielding 'hi Bob!'.
Raw{"answer": "hi Bob!", "explanation": "The parameter 'message' is '%greeting!%' which resolves '%greeting%' to 'hi %name%', then '%name%' resolves to 'Bob', yielding 'hi Bob!'."} | верно | compile() resolves %-references transitively: %greeting% → 'hi %name%' → 'hi Bob!', the answer assembles over two hops. |
T24-L9 2.09 c | Bootstrap | What is the max-width of .container in Bootstrap 5.3 at a 992px viewport? | «960px» Пояснение: In Bootstrap 5.3, at the lg breakpoint (min-width: 992px), the .container max-width is 960px.
Raw{"answer": "960px", "explanation": "In Bootstrap 5.3, at the lg breakpoint (min-width: 992px), the .container max-width is 960px."} | верно | 5.x container widths: 540/720/960/1140/1320 (sm–xxl); 992 → 960px. |
T24-L10 5.92 c | Bootstrap | Which utility sets the text color in Bootstrap 5.3 for `<p class="text-danger text-primary">…</p>`? Answer with the winning class name. | «text-danger» Пояснение: In Bootstrap 5.3's generated CSS, .text-danger appears after .text-primary with equal specificity, so the later rule (.text-danger) wins the cascade.
Raw{"answer": "text-danger", "explanation": "In Bootstrap 5.3's generated CSS, .text-danger appears after .text-primary with equal specificity, so the later rule (.text-danger) wins the cascade."} | верно | Specificity ties — the later rule wins: text-danger is declared after text-primary. |
T25-L9 1.37 c | Clean architecture | Layers: Domain, Application, Infrastructure. Deptrac rules: Application → Domain; Infrastructure → Domain, Application; Domain → Domain only.
How many violations will deptrac report for this class?
```php
namespace App\Domain;
use App\Application\PlaceOrder;
use App\Infrastructure\Db;
class OrderService
{
public function __construct(
private PlaceOrder $handler,
private Db $db,
) {}
}
``` | «2» Пояснение: The Domain layer may only depend on Domain; here it depends on both Application (PlaceOrder) and Infrastructure (Db), giving 2 violations.
Raw{"answer": 2, "explanation": "The Domain layer may only depend on Domain; here it depends on both Application (PlaceOrder) and Infrastructure (Db), giving 2 violations."} | верно | Domain may depend only on Domain: PlaceOrder (Application) + Db (Infrastructure) = 2. |
T25-L10 1.84 c | Clean architecture | Layers: Domain, Application, Infrastructure. Deptrac rules: Application → Domain; Infrastructure → Domain, Application; Domain → Domain only.
How many violations will deptrac report for this class?
```php
namespace App\Domain;
use App\Application\PlaceOrder;
use App\Infrastructure\Db;
class BillingService
{
public function __construct(
private PlaceOrder $handler,
private Db $db,
private \App\Infrastructure\Logger $logger,
) {}
}
``` | «3» Пояснение: The class is in the Domain layer which may only depend on Domain, but it uses PlaceOrder (Application) and two Infrastructure classes (Db, Logger), giving 3 violations.
Raw{"answer": 3, "explanation": "The class is in the Domain layer which may only depend on Domain, but it uses PlaceOrder (Application) and two Infrastructure classes (Db, Logger), giving 3 violations."} | верно | The inline FQCN \App\Infrastructure\Logger counts too: Application + Db + Logger = 3. |
T26-L10 1.35 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 remains unchanged with amount 10 (readonly), and $c is a new Money object with amount 10+5=15.
Raw{"answer": "10,15", "explanation": "$a remains unchanged with amount 10 (readonly), and $c is a new Money object with amount 10+5=15."} | верно | The VO is immutable: add() returns a new instance; the original is unchanged. |
T26-L9 1.32 c | DDD | What does this code output?
```php
final class Order
{
private array $items = [];
public function add(string $sku): void
{
$this->items[$sku] = true;
}
public function count(): int
{
return count($this->items);
}
public function remove(string $sku): void
{
if (count($this->items) === 1) {
throw new DomainException('last item');
}
unset($this->items[$sku]);
}
}
$o = new Order;
$o->add('a');
try {
$o->remove('a');
} catch (DomainException) {
}
echo $o->count();
``` | «1» Пояснение: The remove() method throws a DomainException when count is 1, so unset() is never reached and the item remains, making the final count 1.
Raw{"answer": 1, "explanation": "The remove() method throws a DomainException when count is 1, so unset() is never reached and the item remains, making the final count 1."} | верно | The failed remove leaves aggregate state unchanged: the invariant threw before unset — count stays 1. |
VC-L9 4.07 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 the hi() method which returns the string 'hi', and echoes it.
Raw{"answer": "hi", "explanation": "The code creates an instance of class C, calls the hi() method which returns the string 'hi', and echoes it."} | верно | Since 8.4, new in a method chain works without wrapping parentheses. |
VC-L10 8.12 c | PHP 8.4–8.5 | What does this code output on PHP 8.5?
```php
class Heavy
{
public int $v = 0;
}
$r = new ReflectionClass(Heavy::class);
$o = $r->newLazyGhost(function (Heavy $obj) {
$obj->v = 21;
});
echo $r->isUninitializedLazyObject($o) ? 'yes' : 'no';
$o->v;
echo $r->isUninitializedLazyObject($o) ? 'yes' : 'no';
``` | «yesno» Пояснение: After newLazyGhost the object is uninitialized (prints 'yes'); accessing $o->v triggers the init callback, making it initialized (prints 'no').
Raw{"answer": "yesno", "explanation": "After newLazyGhost the object is uninitialized (prints 'yes'); accessing $o->v triggers the init callback, making it initialized (prints 'no')."} | верно | newLazyGhost (8.4): the object stays lazy until first access — reading a property initializes it and clears the flag. |
T28-L9 2.17 c | Symfony: versions | The project was upgraded from Symfony 6.4 to 8.1. What does this code output on 8.1?
```php
echo class_exists(\Symfony\Component\Security\Guard\AbstractGuardAuthenticator::class)
? 'yes' : 'no';
``` | «no» Пояснение: The Guard authentication component (including AbstractGuardAuthenticator) was removed in Symfony 7.0, so it no longer exists in Symfony 8.1.
Raw{"answer": "no", "explanation": "The Guard authentication component (including AbstractGuardAuthenticator) was removed in Symfony 7.0, so it no longer exists in Symfony 8.1."} | верно | Guard authentication was removed in Symfony 7.0 — the class is gone in 8.1. |
T28-L10 2.83 c | Symfony: versions | The project was upgraded from Symfony 6.4 to 8.1. What does this code output on 8.1?
```php
echo class_exists(\Symfony\Component\Routing\Loader\AnnotationClassLoader::class)
? 'yes' : 'no';
echo class_exists(\Symfony\Component\Routing\Loader\AttributeClassLoader::class)
? 'yes' : 'no';
``` | «noyes» Пояснение: In Symfony 8.1, AnnotationClassLoader was removed (deprecated in 6.4, removed in 7.0), while AttributeClassLoader is the current standard class, so class_exists returns false then true, printing 'no' and 'yes'.
Raw{"answer": "noyes", "explanation": "In Symfony 8.1, AnnotationClassLoader was removed (deprecated in 6.4, removed in 7.0), while AttributeClassLoader is the current standard class, so class_exists returns false then true, printing 'no' and 'yes'."} | верно | Annotation loaders were removed in 7.0; only attribute loaders remain (Annotation→Attribute). |