Пример запроса (первая клетка). System одинаковый во всех запросах прогона, user — свой вопрос для каждой клетки:
| Клетка | Тема | Утверждение | Ответ |
Результат | Обоснование |
T01-L1 4.09 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 recognize more escape sequences (e.g., \n, \t, \"), while single-quoted strings only treat \\ and \' specially, so the processing is fundamentally different, not just a speed difference.
Raw{"answer": "no", "explanation": "Double-quoted strings interpolate variables and recognize more escape sequences (e.g., \\n, \\t, \\\"), while single-quoted strings only treat \\\\ and \\' specially, so the processing is fundamentally different, not just a speed difference."} | верно | В двойных кавычках работают интерполяция переменных и escape-последовательности, в одинарных — нет. |
T01-L2 1.45 c | Syntax and operators | The ?? operator follows isset semantics and raises no warnings for undefined variables. | «yes» Пояснение: The ?? operator is equivalent to isset($a) ? $a : $b, so it silently returns the fallback without triggering an 'Undefined variable' notice.
Raw{"answer": "yes", "explanation": "The ?? operator is equivalent to isset($a) ? $a : $b, so it silently returns the fallback without triggering an 'Undefined variable' notice."} | верно | ?? работает по семантике isset — несуществующие переменные и ключи допустимы. |
T01-L3 0.76 c | Syntax and operators | What will this print: echo 'a', 'b'; | «ab» Пояснение: In PHP, echo can take multiple comma-separated arguments and prints them concatenated without any separator, so 'a' and 'b' are printed as 'ab'.
Raw{"answer": "ab", "explanation": "In PHP, echo can take multiple comma-separated arguments and prints them concatenated without any separator, so 'a' and 'b' are printed as 'ab'."} | верно | echo принимает список аргументов: ab. |
T01-L4 2.66 c | Syntax and operators | print returns the value 1 and can be used inside an expression. | «no» Пояснение: While print does return 1, it is a language construct (not a function), so it cannot be used inside an expression.
Raw{"answer": "no", "explanation": "While print does return 1, it is a language construct (not a function), so it cannot be used inside an expression."} | неверно верный: «yes» | print — выражение со значением 1, в отличие от echo, который значения не возвращает. |
T01-L5 1.01 c | Syntax and operators | The ?: (elvis) operator returns its left operand when it is falsy. | «no» Пояснение: The Elvis operator ($a ?: $b) returns the left operand when it is truthy, not falsy; when it is falsy, it returns the right operand.
Raw{"answer": "no", "explanation": "The Elvis operator ($a ?: $b) returns the left operand when it is truthy, not falsy; when it is falsy, it returns the right operand."} | верно | Наоборот: $a ?: $b возвращает $a, если он истинный, иначе $b. |
T01-L6 1.55 c | Syntax and operators | In PHP 8, the concatenation operator (.) has lower precedence than addition and subtraction. | «yes» Пояснение: In PHP, the concatenation operator (.) has lower precedence than + and -, so expressions like $a + $b . $c are evaluated as ($a + $b) . $c.
Raw{"answer": "yes", "explanation": "In PHP, the concatenation operator (.) has lower precedence than + and -, so expressions like $a + $b . $c are evaluated as ($a + $b) . $c."} | верно | С PHP 8 (RFC concat precedence) '.' имеет приоритет ниже арифметики: 'сумма: ' . 2 + 3 → 'сумма: 5' (в PHP 7 было иначе). |
T01-L7 0.96 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 (2 ** 3) ** 2 = 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 (2 ** 3) ** 2 = 64."} | верно | ** право-ассоциативен: 2 ** (3 ** 2) = 2 ** 9 = 512. |
T01-L8 2.07 c | Syntax and operators | What string will this print: echo 'sum: ' . 2 + 3; (PHP 8)? | «3» Пояснение: Concatenation (.) has higher precedence than +, so it's parsed as ('sum: ' . 2) + 3, which becomes 'sum: 2' + 3, and since 'sum: 2' is not numeric it evaluates to 0, giving 0 + 3 = 3.
Raw{"answer": 3, "explanation": "Concatenation (.) has higher precedence than +, so it's parsed as ('sum: ' . 2) + 3, which becomes 'sum: 2' + 3, and since 'sum: 2' is not numeric it evaluates to 0, giving 0 + 3 = 3."} | неверно верный: «sum: 5» | Парная к verify-клетке про приоритет: 'сумма: 5'. |
T02-L1 1.41 c | Types and comparisons | With strict comparison (===), arrays are considered equal regardless of element order. | «no» Пояснение: With strict comparison (===), PHP requires arrays to have the same key/value pairs in the same order; order only doesn't matter with loose comparison (==).
Raw{"answer": "no", "explanation": "With strict comparison (===), PHP requires arrays to have the same key/value pairs in the same order; order only doesn't matter with loose comparison (==)."} | верно | === для массивов требует совпадения и значений, и их порядка. |
T02-L2 1.45 c | Types and comparisons | The comparison 0 == false returns false because it is a strict comparison. | «no» Пояснение: 0 == false uses loose (==) comparison and actually returns true, since both 0 and false evaluate to the same falsy value.
Raw{"answer": "no", "explanation": "0 == false uses loose (==) comparison and actually returns true, since both 0 and false evaluate to the same falsy value."} | верно | Наоборот: == — нестрогое сравнение и возвращает true; строгое — это === (0 === false → false). |
T02-L3 4.04 c | Types and comparisons | In PHP 8, the expression "abc" == 0 returns true. | «no» Пояснение: In PHP 8, comparing a non-numeric string to an integer falls back to string comparison, so 'abc' == '0' is false (unlike PHP 7 where 'abc' was cast to int 0).
Raw{"answer": "no", "explanation": "In PHP 8, comparing a non-numeric string to an integer falls back to string comparison, so 'abc' == '0' is false (unlike PHP 7 where 'abc' was cast to int 0)."} | верно | С PHP 8 нечисловая строка сравнивается как строка: "abc" == "0" → false (в PHP 7 было true). |
T02-L4 1.33 c | Types and comparisons | Under loose comparison, null equals 0, the empty string, and false at the same time. | «yes» Пояснение: In PHP loose comparison (==), null == 0, null == '', and null == false all evaluate to true.
Raw{"answer": "yes", "explanation": "In PHP loose comparison (==), null == 0, null == '', and null == false all evaluate to true."} | верно | null == 0, null == "" и null == false — все true. |
T02-L5 1.0 c | Types and comparisons | What does the expression (int) '42abc' return? | «42» Пояснение: PHP's (int) cast parses the leading numeric portion of the string and ignores the trailing non-numeric characters.
Raw{"answer": 42, "explanation": "PHP's (int) cast parses the leading numeric portion of the string and ignores the trailing non-numeric characters."} | верно | Ведущая числовая часть: 42, без ошибок и warning. |
T02-L6 0.59 c | Types and comparisons | What does the expression '5' + 5 return? | «10» Пояснение: PHP coerces the numeric string '5' to the integer 5, then performs arithmetic addition with 5, yielding 10.
Raw{"answer": 10, "explanation": "PHP coerces the numeric string '5' to the integer 5, then performs arithmetic addition with 5, yielding 10."} | верно | Числовая строка приводится: int 10. |
T02-L7 0.85 c | Types and comparisons | When cast to string, false becomes "0". | «no» Пояснение: In PHP, casting false to string results in an empty string "", not "0"; (string)false === "".
Raw{"answer": "no", "explanation": "In PHP, casting false to string results in an empty string \"\", not \"0\"; (string)false === \"\"."} | верно | false → "", true → "1". |
T02-L8 1.43 c | Types and comparisons | The comparison 0.1 + 0.2 === 0.3 returns false. | «yes» Пояснение: Due to IEEE 754 floating-point arithmetic, 0.1 + 0.2 evaluates to 0.30000000000000004, which is not strictly identical (===) to 0.3.
Raw{"answer": "yes", "explanation": "Due to IEEE 754 floating-point arithmetic, 0.1 + 0.2 evaluates to 0.30000000000000004, which is not strictly identical (===) to 0.3."} | верно | Двоичная погрешность float: 0.1 + 0.2 = 0.30000000000000004. |
T03-L1 1.46 c | Strings | strrev() correctly reverses a UTF-8 string. | «no» Пояснение: strrev() reverses a string byte-by-byte, which breaks multi-byte UTF-8 characters; mb_strrev() or similar multi-byte functions are needed for correct UTF-8 reversal.
Raw{"answer": "no", "explanation": "strrev() reverses a string byte-by-byte, which breaks multi-byte UTF-8 characters; mb_strrev() or similar multi-byte functions are needed for correct UTF-8 reversal."} | верно | strrev переворачивает байты и ломает многобайтовые последовательности. |
T03-L2 0.55 c | Strings | str_contains('Hello world', 'world') returns true. | «yes» Пояснение: The string 'world' is a substring of 'Hello world', so str_returns true.
Raw{"answer": "yes", "explanation": "The string 'world' is a substring of 'Hello world', so str_returns true."} | верно | str_contains с PHP 8.0 проверяет вхождение подстроки. |
T03-L3 1.05 c | Strings | str_pad() can pad a string on the right side only. | «no» Пояснение: str_pad() supports STR_PAD_RIGHT, STR_PAD_LEFT, and STR_PAD_BOTH via its $pad_type parameter, not just right-side padding.
Raw{"answer": "no", "explanation": "str_pad() supports STR_PAD_RIGHT, STR_PAD_LEFT, and STR_PAD_BOTH via its $pad_type parameter, not just right-side padding."} | верно | STR_PAD_LEFT / STR_PAD_BOTH меняют сторону дополнения. |
T03-L4 1.43 c | Strings | By default trim() strips only spaces, leaving tabs and newlines intact. | «no» Пояснение: By default, trim() strips spaces, tabs, newlines, carriage returns, NUL bytes, and vertical tabs (the character mask is " \t\n\r\0\v"), not just spaces.
Raw{"answer": "no", "explanation": "By default, trim() strips spaces, tabs, newlines, carriage returns, NUL bytes, and vertical tabs (the character mask is \" \\t\\n\\r\\0\\v\"), not just spaces."} | верно | Список символов по умолчанию: « \t\n\r\0\x0B» — пробелы, табы, переводы строк, возврат каретки, null-байт, вертикальный таб. Проверено php -r. |
T03-L5 1.23 c | Strings | How many BYTES does strlen('héllo') return for a UTF-8 string? | «6» Пояснение: strlen counts bytes; in UTF-8, 'é' is 2 bytes while the other 4 characters are 1 byte each, totaling 6.
Raw{"answer": 6, "explanation": "strlen counts bytes; in UTF-8, 'é' is 2 bytes while the other 4 characters are 1 byte each, totaling 6."} | верно | 6 букв по 2 байта: 12. |
T03-L6 0.89 c | Strings | What does substr('abcdef', -3) return? | «def» Пояснение: substr('abcdef', -3) starts at position -3 (the 3rd character from the end) and returns the remaining characters, which is 'def'.
Raw{"answer": "def", "explanation": "substr('abcdef', -3) starts at position -3 (the 3rd character from the end) and returns the remaining characters, which is 'def'."} | верно | Отрицательное смещение — с конца: def. |
T03-L7 0.81 c | Strings | ucfirst() modifies the string passed to it in place. | «no» Пояснение: ucfirst() returns a new string with the first character uppercased; it does not modify the original string in place (PHP strings are passed by value).
Raw{"answer": "no", "explanation": "ucfirst() returns a new string with the first character uppercased; it does not modify the original string in place (PHP strings are passed by value)."} | верно | Строки неизменяемы; ucfirst возвращает новую строку. |
T03-L8 1.16 c | Strings | Variable interpolation works in heredoc but not in nowdoc. | «yes» Пояснение: Heredoc (unlike nowdoc, which uses single quotes) allows variable interpolation; nowdoc treats its content as a literal string with no variable expansion.
Raw{"answer": "yes", "explanation": "Heredoc (unlike nowdoc, which uses single quotes) allows variable interpolation; nowdoc treats its content as a literal string with no variable expansion."} | верно | Nowdoc — «одинарные кавычки» в тройном синтаксисе: текст как есть. |
T04-L1 1.08 c | Arrays | The sort() function preserves the key-to-value association of the array. | «no» Пояснение: PHP's sort() re-indexes the array with sequential integer keys, discarding the original key associations; asort() is the function that preserves them.
Raw{"answer": "no", "explanation": "PHP's sort() re-indexes the array with sequential integer keys, discarding the original key associations; asort() is the function that preserves them."} | верно | sort перенумеровывает ключи; связь сохраняет asort. |
T04-L2 1.0 c | Arrays | The string key '5' in an array is stored as the integer 5. | «yes» Пояснение: In PHP, string keys that are valid integer representations (like '5') are automatically cast to integer keys when stored in an array.
Raw{"answer": "yes", "explanation": "In PHP, string keys that are valid integer representations (like '5') are automatically cast to integer keys when stored in an array."} | верно | Каноничные десятичные строковые ключи приводятся к int. |
T04-L3 0.94 c | Arrays | The in_array() function uses strict comparison (===) by default. | «no» Пояснение: in_array() defaults to $strict = false, meaning it uses loose comparison (==) unless the third parameter is explicitly set to true.
Raw{"answer": "no", "explanation": "in_array() defaults to $strict = false, meaning it uses loose comparison (==) unless the third parameter is explicitly set to true."} | верно | По умолчанию сравнение нестрогое; строгое — третий аргумент true. |
T04-L4 1.37 c | Arrays | Without a callback, array_filter() removes all "empty" (falsy) elements from the array. | «yes» Пояснение: Without a callback, array_filter() removes elements considered falsy: 0, 0.0, '', null, false, and '0'.
Raw{"answer": "yes", "explanation": "Without a callback, array_filter() removes elements considered falsy: 0, 0.0, '', null, false, and '0'."} | верно | Убирает 0, "", null, false и пустые массивы. |
T04-L5 1.31 c | Arrays | By default, array_slice() preserves the original numeric keys of the array. | «no» Пояснение: The $preserve_keys parameter of array_slice() defaults to false, so keys are reindexed by default.
Raw{"answer": "no", "explanation": "The $preserve_keys parameter of array_slice() defaults to false, so keys are reindexed by default."} | верно | По умолчанию ключи перенумеровываются; сохранение — preserve_keys = true. |
T04-L6 1.73 c | Arrays | What does array_slice([10, 20, 30, 40], 1, 2) return? | «[20, 30]» Пояснение: array_slice with offset 1 and length 2 extracts elements at index 1 and 2, which are 20 and 30.
Raw{"answer": "[20, 30]", "explanation": "array_slice with offset 1 and length 2 extracts elements at index 1 and 2, which are 20 and 30."} | верно | [20,30]; ключи перенумеровываются. |
T04-L7 1.39 c | Arrays | How many elements will count(['a' => 1] + ['a' => 9, 'b' => 2]) return? | «2» Пояснение: Array union (+) keeps left-side values for duplicate keys and adds right-side keys not present on the left, resulting in ['a'=>1, 'b'=>2'] which has 2 elements.
Raw{"answer": 2, "explanation": "Array union (+) keeps left-side values for duplicate keys and adds right-side keys not present on the left, resulting in ['a'=>1, 'b'=>2'] which has 2 elements."} | верно | Оператор + : по ключу 'a' побеждает левый; итого 2. |
T04-L8 1.9 c | Arrays | Since PHP 8.1, the spread operator [...$a, ...$b] supports arrays with string keys. | «yes» Пояснение: PHP 8.1 introduced the array spread syntax [...$a, ...$b] which supports both integer and string keys; duplicate string keys are resolved by the later value overwriting the earlier one.
Raw{"answer": "yes", "explanation": "PHP 8.1 introduced the array spread syntax [...$a, ...$b] which supports both integer and string keys; duplicate string keys are resolved by the later value overwriting the earlier one."} | верно | В 8.0 — только числовые ключи; 8.1 снял ограничение. |
T05-L1 4.42 c | Functions and closures | Named arguments cannot be combined with argument unpacking ...$args in a single call. | «no» Пояснение: In PHP 8.0+, named arguments and argument unpacking (...$args) can be freely combined in a single function call, e.g. foo(x: 1, ...$args).
Raw{"answer": "no", "explanation": "In PHP 8.0+, named arguments and argument unpacking (...$args) can be freely combined in a single function call, e.g. foo(x: 1, ...$args)."} | верно | Можно: f(...$args, имя: значение). Нельзя только позиционный аргумент после распаковки. |
T05-L2 1.11 c | Functions and closures | An anonymous function without use sees variables from the outer scope. | «no» Пояснение: In PHP, a closure must explicitly use the 'use' keyword to capture variables from the outer scope; without it, those variables are not accessible.
Raw{"answer": "no", "explanation": "In PHP, a closure must explicitly use the 'use' keyword to capture variables from the outer scope; without it, those variables are not accessible."} | верно | Без use внешние переменные недоступны; авто-захват только у fn. |
T05-L3 0.93 c | Functions and closures | What will func_num_args() return inside function f($a) { return func_num_args(); } when called as f(1, 2, 3)? | «3» Пояснение: func_num_args() returns the total number of arguments passed to the function call, which is 3, regardless of how many parameters are declared in the signature.
Raw{"answer": 3, "explanation": "func_num_args() returns the total number of arguments passed to the function call, which is 3, regardless of how many parameters are declared in the signature."} | верно | Считает переданные аргументы: 3. |
T05-L4 1.61 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 must have a single expression as its body (after =>), not multiple expressions in curly braces; that syntax belongs to regular closures.
Raw{"answer": "no", "explanation": "An arrow function (fn) in PHP must have a single expression as its body (after =>), not multiple expressions in curly braces; that syntax belongs to regular closures."} | верно | fn — всегда одно выражение; блок операторов делает обычная анонимная функция. |
T05-L5 10.83 c | Functions and closures | An arrow function fn captures outer variables by reference (lazily, at use time). | «yes» Пояснение: PHP arrow functions (fn) implicitly capture outer variables by value at call time (lazily), so they always see the current value of the variable when invoked, unlike regular closures which capture at definition time.
Raw{"answer": "yes", "explanation": "PHP arrow functions (fn) implicitly capture outer variables by value at call time (lazily), so they always see the current value of the variable when invoked, unlike regular closures which capture at definition time."} | неверно верный: «no» | fn захватывает только по значению, автоматически; по ссылке — только &$var в use у обычной функции (fn так не умеет). |
T05-L6 1.01 c | Functions and closures | A closure declared as static function () {} does not capture $this. | «yes» Пояснение: In PHP, a static closure (static function() {}) does not bind $this to the enclosing scope, so $this is unavailable inside it.
Raw{"answer": "yes", "explanation": "In PHP, a static closure (static function() {}) does not bind $this to the enclosing scope, so $this is unavailable inside it."} | верно | static-замыкание отвязано от объекта: $this внутри недоступен. |
T05-L7 1.23 c | Functions and closures | What will this print: $x = 5; $f = function () use ($x) { return $x; }; $x = 7; echo $f(); | «5» Пояснение: The use ($x) clause captures the value of $x (5) by value at closure creation time, so later reassigning $x to 7 does not affect the closure.
Raw{"answer": 5, "explanation": "The use ($x) clause captures the value of $x (5) by value at closure creation time, so later reassigning $x to 7 does not affect the closure."} | верно | use захватывает по значению в момент создания: 5. |
T05-L8 0.96 c | Functions and closures | In weak typing mode (without strict_types), passing the string "5" to an int parameter is allowed. | «yes» Пояснение: In PHP's default weak typing mode, the string '5' is automatically coerced to the integer 5 when passed to an int-typed parameter.
Raw{"answer": "yes", "explanation": "In PHP's default weak typing mode, the string '5' is automatically coerced to the integer 5 when passed to an int-typed parameter."} | верно | Coercive typing приводит "5" к 5; strict_types=1 требует точного типа. |
T06-L1 1.2 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 parameters in __construct to be promoted to properties by adding a visibility modifier and type directly in the parameter list.
Raw{"answer": "yes", "explanation": "Constructor property promotion was introduced in PHP 8.0, allowing parameters in __construct to be promoted to properties by adding a visibility modifier and type directly in the parameter list."} | верно | С PHP 8.0 параметр с модификатором создаёт свойство и присваивание. |
T06-L2 0.63 c | OOP: classes and inheritance | Which keyword prevents a method from being overridden in subclasses? | «final» Пояснение: In PHP, the 'final' keyword before a method declaration prevents it from being overridden in subclasses.
Raw{"answer": "final", "explanation": "In PHP, the 'final' keyword before a method declaration prevents it from being overridden in subclasses."} | верно | final. |
T06-L3 0.61 c | OOP: classes and inheritance | A method declared final cannot be overridden in a subclass. | «yes» Пояснение: In PHP, the final keyword prevents a method from being overridden in any subclass.
Raw{"answer": "yes", "explanation": "In PHP, the final keyword prevents a method from being overridden in any subclass."} | верно | final запрещает переопределение метода и наследование класса. |
T06-L4 0.98 c | OOP: classes and inheritance | Parent properties with private visibility are accessible in a subclass. | «no» Пояснение: In PHP, private properties are only accessible within the class that defines them; subclasses cannot access them (that would require 'protected' visibility).
Raw{"answer": "no", "explanation": "In PHP, private properties are only accessible within the class that defines them; subclasses cannot access them (that would require 'protected' visibility)."} | верно | В подклассе видны protected и public; private — только внутри своего класса. |
T06-L5 3.02 c | OOP: classes and inheritance | What does get_class(new class {}) return? Answer with the part of the name before the NUL byte (without the file path). | «class@anonymous» Пояснение: In PHP, get_class(new class {}) returns a generated name in the format 'class@anonymous' followed by a NUL byte and the file path/line number; the part before the NUL byte is 'class@anonymous'.
Raw{"answer": "class@anonymous", "explanation": "In PHP, get_class(new class {}) returns a generated name in the format 'class@anonymous' followed by a NUL byte and the file path/line number; the part before the NUL byte is 'class@anonymous'."} | верно | get_class анонимного класса печатает class@anonymous\0<файл>:<строка>$n; короткая форма — часть до NUL-байта. Проверено php -r (hex). |
T06-L6 1.57 c | OOP: classes and inheritance | A private parent method is not part of the inheritance contract: a child may declare a method with the same name and any visibility. | «yes» Пояснение: In PHP, private methods are completely hidden from child classes, so a child can freely declare a same-named method with any visibility without it being treated as an override.
Raw{"answer": "yes", "explanation": "In PHP, private methods are completely hidden from child classes, so a child can freely declare a same-named method with any visibility without it being treated as an override."} | верно | private-члены не наследуются — правила совместимости подписей не действуют. |
T06-L7 1.79 c | OOP: classes and inheritance | The magic method __get() is called only for non-existent properties. | «no» Пояснение: __get() is also called when reading inaccessible (protected or private) properties that do exist, not just non-existent ones.
Raw{"answer": "no", "explanation": "__get() is also called when reading inaccessible (protected or private) properties that do exist, not just non-existent ones."} | верно | __get срабатывает и для существующих, но недоступных (private/protected извне). |
T06-L8 1.44 c | OOP: classes and inheritance | What does reassigning a readonly property throw — Exception or Error? | «error» Пояснение: In PHP, reassigning a readonly property after initialization throws an instance of Error (not Exception).
Raw{"answer": "Error", "explanation": "In PHP, reassigning a readonly property after initialization throws an instance of Error (not Exception)."} | верно | Error (readonly с 8.1); оговорка: в __clone() переинициализация допустима (8.3+). |
T07-L1 0.66 c | Interfaces, traits, enum | An interface can declare constants. | «yes» Пояснение: PHP interfaces allow the declaration of public constants, which can be accessed by any implementing class.
Raw{"answer": "yes", "explanation": "PHP interfaces allow the declaration of public constants, which can be accessed by any implementing class."} | верно | Константы интерфейса наследуются реализациями. |
T07-L2 0.9 c | Interfaces, traits, enum | Which operator checks whether an object is an instance of a class or interface? | «instanceof» Пояснение: The instanceof operator in PHP checks whether an object is an instance of a specific class or interface.
Raw{"answer": "instanceof", "explanation": "The instanceof operator in PHP checks whether an object is an instance of a specific class or interface."} | верно | instanceof. |
T07-L3 1.63 c | Interfaces, traits, enum | An interface can declare static methods. | «yes» Пояснение: PHP interfaces can declare static methods; implementing classes are not required to implement them.
Raw{"answer": "yes", "explanation": "PHP interfaces can declare static methods; implementing classes are not required to implement them."} | верно | Реализация обязана дать статический метод с той же сигнатурой. |
T07-L4 1.0 c | Interfaces, traits, enum | The instanceof operator only checks class inheritance: it ignores interfaces. | «no» Пояснение: PHP's instanceof operator checks both class inheritance and interface implementation; an object is considered an instance of any interface it implements.
Raw{"answer": "no", "explanation": "PHP's instanceof operator checks both class inheritance and interface implementation; an object is considered an instance of any interface it implements."} | верно | instanceof возвращает true и для интерфейсов объекта. |
T07-L5 2.04 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 implementation body); only traits (and abstract classes) provide default method implementations.
Raw{"answer": "no", "explanation": "In PHP, interface methods are always abstract (no implementation body); only traits (and abstract classes) provide default method implementations."} | верно | Методы интерфейса — только сигнатуры; тело даёт реализующий класс. |
T07-L6 1.06 c | Interfaces, traits, enum | An abstract method in an abstract class may have protected visibility. | «yes» Пояснение: In PHP, abstract methods can be declared with public, protected, or (since 7.1) private visibility, so protected is perfectly valid.
Raw{"answer": "yes", "explanation": "In PHP, abstract methods can be declared with public, protected, or (since 7.1) private visibility, so protected is perfectly valid."} | верно | В абстрактном классе — любая видимость; в интерфейсе — только public. |
T07-L7 0.82 c | Interfaces, traits, enum | How many elements will Foo::cases() return for enum Foo { case A; case B; case C; }? | «3» Пояснение: Foo::cases() returns an array containing all enum cases, which are A, B, and C — three elements in total.
Raw{"answer": 3, "explanation": "Foo::cases() returns an array containing all enum cases, which are A, B, and C — three elements in total."} | верно | Статический метод cases(): 3. |
T07-L8 1.19 c | Interfaces, traits, enum | A trait can declare constants. | «yes» Пояснение: PHP traits are allowed to declare constants, just as they can declare methods and (with restrictions) properties.
Raw{"answer": "yes", "explanation": "PHP traits are allowed to declare constants, just as they can declare methods and (with restrictions) properties."} | верно | С PHP 8.2 трейты могут объявлять константы (RFC constants_in_traits); до 8.2 — нет. |
T08-L1 1.13 c | Exceptions and errors | The Throwable interface is a common ancestor of both Exception and Error. | «yes» Пояснение: In PHP 7+, both Exception and Error implement the Throwable interface, making it their common ancestor in the type hierarchy.
Raw{"answer": "yes", "explanation": "In PHP 7+, both Exception and Error implement the Throwable interface, making it their common ancestor in the type hierarchy."} | верно | Иерархия с PHP 7: Throwable → Exception и Throwable → Error. |
T08-L2 1.28 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; both Exception and Error are separate branches under the Throwable interface, so catch(Exception) does not catch TypeError.
Raw{"answer": "no", "explanation": "TypeError extends Error, not Exception; both Exception and Error are separate branches under the Throwable interface, so catch(Exception) does not catch TypeError."} | верно | TypeError наследуется от Error; catch (Exception) его не ловит. |
T08-L3 2.03 c | Exceptions and errors | The @ operator suppresses exceptions too. | «no» Пояснение: The @ operator only suppresses errors/warnings/notices, not exceptions; exceptions must still be caught with try/catch.
Raw{"answer": "no", "explanation": "The @ operator only suppresses errors/warnings/notices, not exceptions; exceptions must still be caught with try/catch."} | верно | @ глушит диагностику (warnings/notices), исключения не перехватывает. |
T08-L4 1.0 c | Exceptions and errors | What error class does intdiv(5, 0) throw? | «divisionbyzeroerror» Пояснение: intdiv(5, 0) throws a DivisionByZeroError, which is a subclass of ArithmeticError in PHP.
Raw{"answer": "DivisionByZeroError", "explanation": "intdiv(5, 0) throws a DivisionByZeroError, which is a subclass of ArithmeticError in PHP."} | верно | DivisionByZeroError (иерархия Error, не Exception); php-грейдер объективен. |
T08-L5 1.0 c | Exceptions and errors | The finally block runs only if the exception was caught by a catch block. | «no» Пояснение: The finally block executes regardless of whether an exception was thrown or caught; it always runs.
Raw{"answer": "no", "explanation": "The finally block executes regardless of whether an exception was thrown or caught; it always runs."} | верно | Наоборот: finally выполняется всегда — даже когда исключение не поймано и уходит выше. Проверено php -r. |
T08-L6 1.8 c | Exceptions and errors | An exception thrown inside a finally block has no effect on the result of the try block. | «no» Пояснение: An exception thrown in a finally block will propagate and can replace or override any exception from the try/catch block, so it does have an effect on the overall result.
Raw{"answer": "no", "explanation": "An exception thrown in a finally block will propagate and can replace or override any exception from the try/catch block, so it does have an effect on the overall result."} | верно | Исключение из finally перекрывает исходное и уходит вместо него. |
T08-L7 0.85 c | Exceptions and errors | What does the expression (bool) new Exception('x') return? | «yes» Пояснение: In PHP, casting any object (including an Exception) to bool always results in true.
Raw{"answer": "yes", "explanation": "In PHP, casting any object (including an Exception) to bool always results in true."} | верно | Любой объект при приведении к bool — true. Формы ответа: true или да. |
T08-L8 3.1 c | Exceptions and errors | Functions registered via register_shutdown_function() run when exit is called. | «no» Пояснение: Shutdown functions registered with register_shutdown_function() are called on normal script termination, but they are NOT called when exit() or die() is invoked.
Raw{"answer": "no", "explanation": "Shutdown functions registered with register_shutdown_function() are called on normal script termination, but they are NOT called when exit() or die() is invoked."} | неверно верный: «yes» | exit завершает скрипт, но shutdown-функции отрабатывают. |
T09-L1 1.08 c | Namespaces and autoloading | The use App\Service\Mailer; statement itself loads the class file. | «no» Пояснение: The 'use' statement only creates a compile-time alias; the class file is loaded (via autoloader) only when the class is actually referenced at runtime.
Raw{"answer": "no", "explanation": "The 'use' statement only creates a compile-time alias; the class file is loaded (via autoloader) only when the class is actually referenced at runtime."} | верно | use — псевдоним на этапе компиляции; файл грузит автозагрузчик при первом обращении. |
T09-L2 0.89 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 Namespace\funcName;', while 'use const' is for importing constants.
Raw{"answer": "function", "explanation": "In PHP, to import a function you use 'use function Namespace\\funcName;', while 'use const' is for importing constants."} | верно | use function ...; (и use const для констант). |
T09-L3 1.26 c | Namespaces and autoloading | Into which file (path from src/) does the PSR-4 mapping "App\ → src/" place the class App\Controller\Api\UserController? | «controller/api/usercontroller.php» Пояснение: PSR-4 strips the 'App\' prefix and converts the remaining namespace segments (Controller\Api) to directory paths, then appends the class name with .php extension.
Raw{"answer": "Controller/Api/UserController.php", "explanation": "PSR-4 strips the 'App\\' prefix and converts the remaining namespace segments (Controller\\Api) to directory paths, then appends the class name with .php extension."} | верно | Остаток имени после префикса, \ → /. |
T09-L4 0.97 c | Namespaces and autoloading | Including vendor/autoload.php registers autoloaders via spl_autoload_register(). | «yes» Пояснение: Composer's vendor/autoload.php ultimately calls spl_autoload_register() to register its autoload function with PHP's SPL autoloading mechanism.
Raw{"answer": "yes", "explanation": "Composer's vendor/autoload.php ultimately calls spl_autoload_register() to register its autoload function with PHP's SPL autoloading mechanism."} | верно | Composer ставит автозагрузчик именно на spl_autoload_register. |
T09-L5 0.65 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 fully qualified name of the current namespace (or an empty string if no namespace is defined).
Raw{"answer": "yes", "explanation": "__NAMESPACE__ is a PHP magic constant that returns the fully qualified name of the current namespace (or an empty string if no namespace is defined)."} | верно | В корневом пространстве — пустая строка. |
T09-L6 1.6 c | Namespaces and autoloading | An unqualified class name (without a leading \) in new is resolved from the global root. | «no» Пояснение: In PHP, an unqualified class name in 'new' is resolved relative to the current namespace, not the global root; only a leading backslash forces global root resolution.
Raw{"answer": "no", "explanation": "In PHP, an unqualified class name in 'new' is resolved relative to the current namespace, not the global root; only a leading backslash forces global root resolution."} | верно | Резолвится относительно текущего namespace (с учётом импортов). |
T09-L7 1.21 c | Namespaces and autoloading | With the PSR-4 mapping "App\ → src/", the class App\Model\User lives in the file src/Model/User.php. | «yes» Пояснение: PSR-4 maps the namespace 'App\Model\User' by stripping the 'App\' prefix, converting remaining '\' to '/', and appending '.php', yielding 'src/Model/User.php'.
Raw{"answer": "yes", "explanation": "PSR-4 maps the namespace 'App\\Model\\User' by stripping the 'App\\' prefix, converting remaining '\\' to '/', and appending '.php', yielding 'src/Model/User.php'."} | верно | Остаток имени после префикса переносится в путь как есть. |
T09-L8 1.31 c | Namespaces and autoloading | A use statement may be written inside a function body — the import then applies to that function only. | «yes» Пояснение: PHP allows a use alias inside a function body, and that alias is scoped to that function only.
Raw{"answer": "yes", "explanation": "PHP allows a use alias inside a function body, and that alias is scoped to that function only."} | неверно верный: «no» | use внутри тела функции — parse error; импорты файловые и компиляционные. |
T10-L1 1.58 c | References and scope | Arrays are copied on assignment rather than passed by reference. | «yes» Пояснение: In PHP, arrays use value semantics: assignment and function calls copy the array by default (with internal copy-on-write optimization), rather than using reference semantics.
Raw{"answer": "yes", "explanation": "In PHP, arrays use value semantics: assignment and function calls copy the array by default (with internal copy-on-write optimization), rather than using reference semantics."} | верно | Присваивание массива — копия (в движке — copy-on-write). |
T10-L2 0.94 c | References and scope | What will this print: $a = [1, 2]; $b = $a; $b[] = 3; echo count($a); | «2» Пояснение: PHP arrays are copied by value on assignment, so appending to $b does not affect $a, which still contains 2 elements.
Raw{"answer": 2, "explanation": "PHP arrays are copied by value on assignment, so appending to $b does not affect $a, which still contains 2 elements."} | верно | Присваивание — копия: в $a по-прежнему 2 элемента. |
T10-L3 1.12 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 declared with the `global` keyword, accessed via the `$GLOBALS` superglobal array, or passed as parameters.
Raw{"answer": "yes", "explanation": "In PHP, variables defined in the global scope are not accessible inside a function unless declared with the `global` keyword, accessed via the `$GLOBALS` superglobal array, or passed as parameters."} | верно | Область видимости функций изолирована; исключение — суперглобалы ($_GET и др.). |
T10-L4 1.36 c | References and scope | unset($GLOBALS['x']) inside a function removes the global variable only for that function. | «no» Пояснение: $GLOBALS['x'] is a direct reference to the global variable, so unset($GLOBALS['x']) removes it globally, not just within that function's scope.
Raw{"answer": "no", "explanation": "$GLOBALS['x'] is a direct reference to the global variable, so unset($GLOBALS['x']) removes it globally, not just within that function's scope."} | верно | $GLOBALS — прямое окно в глобальную область: unset удалит её по-настоящему. |
T10-L5 0.65 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 changed from 5 to 6.
Raw{"answer": 6, "explanation": "The function increments $x by reference, so $n is changed from 5 to 6."} | верно | Ссылка меняет оригинал: 6. |
T10-L6 3.33 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. | «yes» Пояснение: In PHP, foreach iterates over the original array using an internal pointer, so appending or modifying elements inside the loop body is visible in the same pass (e.g., new elements added via $array[] will be iterated over).
Raw{"answer": "yes", "explanation": "In PHP, foreach iterates over the original array using an internal pointer, so appending or modifying elements inside the loop body is visible in the same pass (e.g., new elements added via $array[] will be iterated over)."} | неверно верный: «no» | По значению foreach итерирует копию-снимок. |
T10-L7 0.97 c | References and scope | A static property belongs to each instance separately: changes in one object are not visible in others. | «no» Пояснение: A static property belongs to the class itself and is shared among all instances, so changes made through one object are visible in all others.
Raw{"answer": "no", "explanation": "A static property belongs to the class itself and is shared among all instances, so changes made through one object are visible in all others."} | верно | Наоборот: статическое свойство общее для всех экземпляров класса. Проверено php -r. |
T10-L8 1.24 c | References and scope | An array can have a boolean key true, and it will be stored as bool. | «no» Пояснение: In PHP, boolean array keys are cast to integers: true becomes 1 and false becomes 0, so the key is stored as an int, not as a bool.
Raw{"answer": "no", "explanation": "In PHP, boolean array keys are cast to integers: true becomes 1 and false becomes 0, so the key is stored as an int, not as a bool."} | верно | Булев ключ приводится к int: true → 1, false → 0. |
T11-L1 1.48 c | Generators, iterators, SPL | Inside a generator, return with a value can be used, and it becomes available via $gen->getReturn(). | «yes» Пояснение: Since PHP 7.0, a generator can return a value, which is accessible via the Generator::getReturn() method after the generator is complete.
Raw{"answer": "yes", "explanation": "Since PHP 7.0, a generator can return a value, which is accessible via the Generator::getReturn() method after the generator is complete."} | верно | return-значение генератора доступно через getReturn() после прохода. |
T11-L2 1.14 c | Generators, iterators, SPL | A fully consumed generator can be rewound with rewind() and traversed again. | «no» Пояснение: A generator is a one-time iterator; once fully consumed, you must call the generator function again to obtain a new Generator instance rather than calling rewind().
Raw{"answer": "no", "explanation": "A generator is a one-time iterator; once fully consumed, you must call the generator function again to obtain a new Generator instance rather than calling rewind()."} | верно | Генератор одноразовый: rewind после начала итерации бросает Exception. |
T11-L3 0.9 c | Generators, iterators, SPL | The yield from construct delegates traversal to another generator or iterable. | «yes» Пояснение: In PHP, `yield from` delegates iteration to another generator or iterable, yielding its values as if they were yielded directly by the current generator.
Raw{"answer": "yes", "explanation": "In PHP, `yield from` delegates iteration to another generator or iterable, yielding its values as if they were yielded directly by the current generator."} | верно | yield from проксирует значения, ключи и return-значение внутреннего генератора. |
T11-L4 1.77 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() returns its class name as a string.
Raw{"answer": "Generator", "explanation": "Calling a generator function returns a Generator object, and get_class() returns its class name as a string."} | верно | Функция с yield возвращает Generator. |
T11-L5 1.09 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 to 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 to an array of 3 elements, and count returns 3."} | верно | yield from делегирует все 3 элемента. |
T11-L6 0.63 c | Generators, iterators, SPL | The SplStack class implements a FIFO queue. | «no» Пояснение: SplStack implements a LIFO (Last In, First Out) stack, not a FIFO queue; SplQueue is the class that implements a FIFO queue.
Raw{"answer": "no", "explanation": "SplStack implements a LIFO (Last In, First Out) stack, not a FIFO queue; SplQueue is the class that implements a FIFO queue."} | верно | SplStack — стек LIFO; очередь FIFO — SplQueue. |
T11-L7 0.75 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 explicit 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 explicit iterator methods."} | верно | Объектная обёртка над массивом. |
T11-L8 0.93 c | Generators, iterators, SPL | An ArrayObject instance cannot be traversed with foreach. | «no» Пояснение: ArrayObject implements IteratorAggregate, so it can be traversed with foreach.
Raw{"answer": "no", "explanation": "ArrayObject implements IteratorAggregate, so it can be traversed with foreach."} | верно | ArrayObject реализует IteratorAggregate — foreach по нему работает. |
T12-L1 1.67 c | Configuration and security | password_hash() generates a salt automatically — passing one separately is not needed. | «yes» Пояснение: password_hash() internally generates and embeds a random salt in the returned hash; the function signature has no separate salt parameter.
Raw{"answer": "yes", "explanation": "password_hash() internally generates and embeds a random salt in the returned hash; the function signature has no separate salt parameter."} | верно | Соль встраивается в строку результата; параметр salt устарел. |
T12-L2 1.78 c | Configuration and security | In PHP 8, PASSWORD_DEFAULT is md5 with an automatically added salt. | «no» Пояснение: In PHP 8, PASSWORD_DEFAULT is bcrypt (PASSWORD_BCRYPT), not md5; md5 is not used by password_hash() at all.
Raw{"answer": "no", "explanation": "In PHP 8, PASSWORD_DEFAULT is bcrypt (PASSWORD_BCRYPT), not md5; md5 is not used by password_hash() at all."} | верно | PASSWORD_DEFAULT — bcrypt; md5 для паролей непригоден (перебирается массово). |
T12-L3 0.97 c | Configuration and security | What does password_verify('secret', password_hash('secret', PASSWORD_DEFAULT)) return? | «yes» Пояснение: password_verify checks if the plaintext matches the hash; since both use 'secret', it returns true.
Raw{"answer": "yes", "explanation": "password_verify checks if the plaintext matches the hash; since both use 'secret', it returns true."} | верно | Соль и хеш в одной строке: true (форма ответа: true или да). |
T12-L4 0.99 c | Configuration and security | strip_tags() protects against SQL injection. | «no» Пояснение: strip_tags() removes HTML/PHP tags from a string; SQL injection is protected against by prepared statements/parameterized queries, not by stripping HTML tags.
Raw{"answer": "no", "explanation": "strip_tags() removes HTML/PHP tags from a string; SQL injection is protected against by prepared statements/parameterized queries, not by stripping HTML tags."} | верно | strip_tags режет HTML-теги (помощник против XSS), к параметризации SQL отношения не имеет. |
T12-L5 1.0 c | Configuration and security | session_regenerate_id() is used to protect against session fixation upon user login. | «yes» Пояснение: session_regenerate_id() is the standard PHP function used to change the session ID after privilege changes like login, preventing an attacker from reusing a known session ID (session fixation).
Raw{"answer": "yes", "explanation": "session_regenerate_id() is the standard PHP function used to change the session ID after privilege changes like login, preventing an attacker from reusing a known session ID (session fixation)."} | верно | Новый ID сессии после логина — стандартная защита от session fixation. |
T12-L6 0.91 c | Configuration and security | Which built-in function returns the SAPI name (e.g., cli)? | «php_sapi_name()» Пояснение: The built-in function php_sapi_name() returns the name of the current SAPI module, such as 'cli' for the command-line interface.
Raw{"answer": "php_sapi_name()", "explanation": "The built-in function php_sapi_name() returns the name of the current SAPI module, such as 'cli' for the command-line interface."} | верно | php_sapi_name(). |
T12-L7 1.54 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 (PHPSESSID) remains in the browser unless explicitly deleted with setcookie().
Raw{"answer": "yes", "explanation": "session_destroy() only removes the session data on the server; the session cookie (PHPSESSID) remains in the browser unless explicitly deleted with setcookie()."} | верно | Удаление cookie — отдельный шаг через setcookie с истёкшим сроком. |
T12-L8 1.01 c | Configuration and security | Without calling session_start(), the $_SESSION array is automatically populated with session data. | «no» Пояснение: The $_SESSION superglobal is only populated with stored session data after session_start() is called; without it, $_SESSION is simply an empty array.
Raw{"answer": "no", "explanation": "The $_SESSION superglobal is only populated with stored session data after session_start() is called; without it, $_SESSION is simply an empty array."} | верно | Без session_start() данные сессии в массив не загружаются ($_SESSION можно заполнить вручную, но привязки к сессии нет). |
VC-L1 2.83 c | PHP 8.4–8.5 | In which PHP version was the array_find() function introduced? | «never» Пояснение: array_find() is not a built-in PHP function; it is a commonly used user-defined function, so it was not introduced in any specific PHP version.
Raw{"answer": "never", "explanation": "array_find() is not a built-in PHP function; it is a commonly used user-defined function, so it was not introduced in any specific PHP version."} | неверно верный: «8.4» | PHP 8.4 (RFC array_find). |
VC-L2 0.78 c | PHP 8.4–8.5 | Property hooks (get/set right in the property declaration) landed in PHP 8.4. | «yes» Пояснение: PHP 8.4 introduced property hooks, allowing custom get/set logic to be defined directly in the property declaration.
Raw{"answer": "yes", "explanation": "PHP 8.4 introduced property hooks, allowing custom get/set logic to be defined directly in the property declaration."} | верно | Property hooks — PHP 8.4 (ноябрь 2024). |
VC-L3 0.97 c | PHP 8.4–8.5 | Asymmetric visibility (public private(set) string $name) appeared in PHP 8.4. | «yes» Пояснение: Asymmetric visibility (e.g. public private(set) string $name) was indeed introduced as a new feature in PHP 8.4.
Raw{"answer": "yes", "explanation": "Asymmetric visibility (e.g. public private(set) string $name) was indeed introduced as a new feature in PHP 8.4."} | верно | Asymmetric visibility v2 — PHP 8.4. |
VC-L4 3.44 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 by the caller.
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 by the caller."} | неверно верный: «8.5» | #[\NoDiscard] — PHP 8.5 (marking return values as important). |
VC-L5 2.4 c | PHP 8.4–8.5 | In which PHP version did the pipe operator |> first appear? Answer with the version number. | «8.4» Пояснение: The pipe operator |> was introduced in PHP 8.4 as part of the Pipe Operator RFC.
Raw{"answer": "8.4", "explanation": "The pipe operator |> was introduced in PHP 8.4 as part of the Pipe Operator RFC."} | неверно верный: «8.5» | Pipe operator — PHP 8.5 (2025). |
VC-L6 1.15 c | PHP 8.4–8.5 | In which PHP version did clone-with — the syntax clone($obj, ['x' => 1]) — appear? Answer with the version number. | «8.4» Пояснение: The clone-with syntax (clone($obj, ['x' => 1]) was introduced in PHP 8.4, released in November 2024.
Raw{"answer": "8.4", "explanation": "The clone-with syntax (clone($obj, ['x' => 1]) was introduced in PHP 8.4, released in November 2024."} | неверно верный: «8.5» | Clone with v2 — PHP 8.5. |
VC-L7 1.61 c | PHP 8.4–8.5 | In which PHP version were the array_first() and array_last() functions introduced? | «8.4» Пояснение: The array_first() and array_last() functions were introduced in PHP 8.4.
Raw{"answer": "8.4", "explanation": "The array_first() and array_last() functions were introduced in PHP 8.4."} | неверно верный: «8.5» | PHP 8.5. |
VC-L8 2.53 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 1.02 c | PHP: 8.6+ and the future | For which PHP version was the RFC clamp_v2 (the clamp() function) implemented, as of 2026-11-07? Answer with the version number. | «8.4» Пояснение: The clamp() function (RFC clamp_v2) was implemented in PHP 8.4.
Raw{"answer": "8.4", "explanation": "The clamp() function (RFC clamp_v2) was implemented in PHP 8.4."} | неверно верный: «8.6» | По данным владельца (wiki.php.net/rfc): clamp_v2 — 8.6; clamp() в 8.5.11 отсутствует (косвенное подтверждение). Дата-якорь делает клетку монотонной. |
VF-L2 5.65 c | PHP: 8.6+ and the future | RFC Context Managers v2 has already been adopted in PHP (as of 2026-11-07). | «yes» Пояснение: The RFC for Context Managers v2 (providing a 'using' construct for automatic resource cleanup) was adopted into PHP before November 2026.
Raw{"answer": "yes", "explanation": "The RFC for Context Managers v2 (providing a 'using' construct for automatic resource cleanup) was adopted into PHP before November 2026."} | неверно верный: «no» | На 06.11.2026 — в обсуждении (создан 2026-10-23); не принят. |
VF-L3 4.8 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) was indeed declined, continuing PHP's long history of not yet implementing native generics.
Raw{"answer": "yes", "explanation": "The RFC for Bound-Erased Generic Types (generics) was indeed declined, continuing PHP's long history of not yet implementing native generics."} | верно | Голосование завершилось 2026-06-28: отклонён (wiki.php.net/rfc). |
VF-L4 4.46 c | PHP: 8.6+ and the future | As of 2026-11-07, the RFC enabling multithreading (ZTS) by default has already been accepted in PHP. | «no» Пояснение: As of late 2026, no RFC making ZTS (Zend Thread-Safe) the default build for PHP has been formally accepted; NTS remains the default distribution build.
Raw{"answer": "no", "explanation": "As of late 2026, no RFC making ZTS (Zend Thread-Safe) the default build for PHP has been formally accepted; NTS remains the default distribution build."} | верно | Такого принятого RFC нет на дату якоря; якорь делает клетку монотонной — при принятии RFC позже клетка не перевернётся. |
VF-L5 2.4 c | PHP: 8.6+ and the future | As of PHP 8.5, generics (parameterized types) are still absent. | «yes» Пояснение: PHP has never shipped built-in runtime generics; even in PHP 8.5 the feature remains absent, with only PHPDoc-level @template annotations available.
Raw{"answer": "yes", "explanation": "PHP has never shipped built-in runtime generics; even in PHP 8.5 the feature remains absent, with only PHPDoc-level @template annotations available."} | верно | Generics в PHP отсутствуют; отрицательный контроль (не путать с C#/Java). |
VF-L6 2.28 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 November release cycle; PHP 8.5 would be the latest stable as of early November 2026, with PHP 8.6's GA scheduled for mid-November 2026.
Raw{"answer": "yes", "explanation": "PHP follows a November release cycle; PHP 8.5 would be the latest stable as of early November 2026, with PHP 8.6's GA scheduled for mid-November 2026."} | верно | 8.5 — релиз осени 2025; 8.6 GA 19.11.2026 (wiki.php.net/todo/php86). Дата снимка — 06.11.2026. |
VF-L7 1.34 c | PHP: 8.6+ and the future | The PHP 6 branch never shipped: after PHP 5.6 came PHP 7.0 directly. | «yes» Пояснение: PHP skipped version 6 and went directly from 5.6 to 7.0 to signal major breaking changes.
Raw{"answer": "yes", "explanation": "PHP skipped version 6 and went directly from 5.6 to 7.0 to signal major breaking changes."} | верно | Исторический факт: ветка 6 не была релизнута. |
VF-L8 4.34 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 not adopted into PHP core; deprecation is still communicated via docblocks and the trigger_error() mechanism.
Raw{"answer": "no", "explanation": "The RFC proposing a built-in #[\\Deprecated] attribute was not adopted into PHP core; deprecation is still communicated via docblocks and the trigger_error() mechanism."} | неверно верный: «yes» | #[\Deprecated] — принят, реализован в PHP 8.4. |
T25-L1 0.95 c | Clean architecture | The dependency rule of clean and onion architecture: inner layers know nothing about outer ones — dependencies point toward the center. | «yes» Пояснение: In both Clean and Onion architecture, the dependency rule dictates that inner (core/domain) layers must not reference outer layers; all dependencies point inward toward the center.
Raw{"answer": "yes", "explanation": "In both Clean and Onion architecture, the dependency rule dictates that inner (core/domain) layers must not reference outer layers; all dependencies point inward toward the center."} | верно | Чистая (Robert C. Martin), луковичная (Jeffrey Palermo) и гексагональная (ports & adapters) — варианты одной идеи: зависимости направлены внутрь, к домену. Слоями в проекте следит deptrac. |
T25-L2 1.42 c | Clean architecture | Domain entities import neither Doctrine nor Symfony — only the language and, possibly, the standard library. | «yes» Пояснение: In clean/DDD architecture, domain entities are framework-agnostic PHP classes that depend only on the language itself and possibly the standard library, not on Doctrine or Symfony.
Raw{"answer": "yes", "explanation": "In clean/DDD architecture, domain entities are framework-agnostic PHP classes that depend only on the language itself and possibly the standard library, not on Doctrine or Symfony."} | верно | Изоляция домена от инфраструктуры; deptrac в проекте как раз следит за слоями. |
T25-L3 2.03 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 (interface) layer, not the business-logic layer; they translate HTTP requests/responses into use-case calls and back, while the business-logic layer contains the use cases themselves.
Raw{"answer": "no", "explanation": "Controllers and Twig templates belong to the presentation (interface) layer, not the business-logic layer; they translate HTTP requests/responses into use-case calls and back, while the business-logic layer contains the use cases themselves."} | верно | Наоборот: это интерфейсные адаптеры (внешний слой); они зависят от use cases, а не наоборот. |
T25-L4 1.5 c | Clean architecture | What sits at the very center of the onion architecture? | «entities» Пояснение: In onion architecture, the innermost layer contains the core domain entities and business rules, which are independent of any framework or external detail.
Raw{"answer": "Entities", "explanation": "In onion architecture, the innermost layer contains the core domain entities and business rules, which are independent of any framework or external detail."} | неверно верный: «domain model» | Центральное кольцо — Domain Model: сущности и бизнес-правила без зависимостей; далее Domain Services → Application Services → Infrastructure/UI/Tests (Palermo). |
T25-L5 1.14 c | Clean architecture | Layer boundary violations can be caught automatically: a layer-dependency analyzer (e.g. deptrac) fails on a forbidden call. | «yes» Пояснение: Deptrac (and similar tools like PHPMD, ArchUnit for Java) can define layer-dependency rules and automatically fail the build when a forbidden inter-layer call is detected.
Raw{"answer": "yes", "explanation": "Deptrac (and similar tools like PHPMD, ArchUnit for Java) can define layer-dependency rules and automatically fail the build when a forbidden inter-layer call is detected."} | верно | depfile.yaml в проекте TasK: CI проверяет правила слоёв на каждом пайплайне. |
T25-L6 1.73 c | Clean architecture | A use case (interactor) may accept an HTTP request or an EntityManager as arguments — it is simpler that way. | «no» Пояснение: A use case (interactor) should be framework-agnostic and persistence-agnostic; accepting an HTTP Request or EntityManager couples it to specific frameworks, violating the dependency inversion principle.
Raw{"answer": "no", "explanation": "A use case (interactor) should be framework-agnostic and persistence-agnostic; accepting an HTTP Request or EntityManager couples it to specific frameworks, violating the dependency inversion principle."} | верно | Use case принимает DTO и порты; привязка к HTTP/ORM протекает инфраструктуру во внутренние слои. |
T25-L7 0.91 c | Clean architecture | What is the component called that provides a collection of aggregates/entities while hiding the storage mechanism behind an interface? | «repository» Пояснение: In DDD, a Repository provides a collection-like interface for accessing domain aggregates/entities while abstracting the underlying storage mechanism.
Raw{"answer": "Repository", "explanation": "In DDD, 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 2.1 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 outermost detail behind an interface, so the domain and use-case layers depend only on abstractions and remain unchanged when the underlying database is swapped.
Raw{"answer": "yes", "explanation": "In Clean Architecture the database is an outermost detail behind an interface, so the domain and use-case layers depend only on abstractions and remain unchanged when the underlying database is swapped."} | верно | Следствие правила зависимостей: инфраструктура взаимозаменяема. |
T26-L1 1.52 c | DDD | In DDD, an aggregate is just another name for a database table. | «no» Пояснение: In DDD, an aggregate is a domain-level cluster of objects with a root that enforces invariants; it is a conceptual boundary, not a database table, though it may be persisted across multiple tables.
Raw{"answer": "no", "explanation": "In DDD, an aggregate is a domain-level cluster of objects with a root that enforces invariants; it is a conceptual boundary, not a database table, though it may be persisted across multiple tables."} | верно | Агрегат — кластер объектов с границей согласованности (транзакционной вокруг корня); таблица — деталь хранения. |
T26-L2 1.06 c | DDD | A Value Object is immutable and compared by the values of its fields, not by identity. | «yes» Пояснение: By definition in Domain-Driven Design, a Value Object is immutable and its equality is determined by the equality of its field values rather than by object identity.
Raw{"answer": "yes", "explanation": "By definition in Domain-Driven Design, a Value Object is immutable and its equality is determined by the equality of its field values rather than by object identity."} | верно | Классика Evans: Money, Email; равенство структурное. |
T26-L3 1.25 c | DDD | What is the single external entry point of an aggregate, through which all changes must go, called? | «aggregate root» Пояснение: In Domain-Driven Design, the Aggregate Root is the single external entry point through which all changes to the aggregate must pass.
Raw{"answer": "Aggregate Root", "explanation": "In Domain-Driven Design, the Aggregate Root is the single external entry point through which all changes to the aggregate must pass."} | верно | Aggregate Root: внешние объекты ссылаются только на корень; он защищает инварианты агрегата. |
T26-L4 1.19 c | DDD | In DDD, a repository is declared for an aggregate (its root), not for every entity. | «yes» Пояснение: In DDD, repositories are declared for Aggregates (via their Aggregate Root), not for every individual entity within the aggregate.
Raw{"answer": "yes", "explanation": "In DDD, repositories are declared for Aggregates (via their Aggregate Root), not for every individual entity within the aggregate."} | верно | Репозиторий корня хранит границу согласованности агрегата; вложенные сущности доступны только через корень. |
T26-L5 1.05 c | DDD | Ubiquitous language is the model's shared language common to developers and domain experts. | «yes» Пояснение: In Domain-Driven Design, the Ubiquitous Language is the shared vocabulary used consistently by both developers and domain experts to ensure the model, code, and discussions align.
Raw{"answer": "yes", "explanation": "In Domain-Driven Design, the Ubiquitous Language is the shared vocabulary used consistently by both developers and domain experts to ensure the model, code, and discussions align."} | верно | Evans: язык из требований переходит в имена классов и методов. |
T26-L6 5.63 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 bounded context within which a model and its language maintain consistent meaning, while outside it the same terms refer to different models or interpretations.
Raw{"answer": "frame", "explanation": "A frame is the bounded context within which a model and its language maintain consistent meaning, while outside it the same terms refer to different models or interpretations."} | неверно верный: «bounded context» | Bounded Context; «Заказ» в биллинге и в доставке — разные модели. |
T26-L7 1.6 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 is encapsulated in entities/aggregates, not an anemic model with logic delegated to services.
Raw{"answer": "no", "explanation": "DDD recommends a rich domain model where business logic is encapsulated in entities/aggregates, not an anemic model with logic delegated to services."} | верно | Наоборот: Evans называет анемичность антипаттерном — поведение должно жить в доменных объектах. |
T26-L8 2.27 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 distinct model, so the same real-world concept (e.g., 'Customer') 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 distinct model, so the same real-world concept (e.g., 'Customer') is represented by different classes with different attributes and behaviors in different contexts."} | верно | Модели контекстов независимы; между ними — явная интеграция (ACL, published language). |
T13-L1 1.47 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 when it is first requested (e.g., via $container->get() or autowiring), not at container bootstrap time.
Raw{"answer": "yes", "explanation": "Symfony's DI container instantiates services lazily by default, meaning a service object is only created when it is first requested (e.g., via $container->get() or autowiring), not at container bootstrap time."} | верно | Контейнер инстанцирует сервис при первом извлечении; eager-создания по умолчанию нет. |
T13-L2 1.06 c | Symfony | Which Symfony console command lists all registered routes? | «debug:router» Пояснение: In Symfony, the console command 'debug:router' (invoked as 'bin/console debug:router') lists all registered routes.
Raw{"answer": "debug:router", "explanation": "In Symfony, the console command 'debug:router' (invoked as 'bin/console debug:router') lists all registered routes."} | верно | bin/console debug:router (FrameworkBundle); в Symfony 3 команда называлась router:debug. |
T13-L3 1.2 c | Symfony | Symfony autowiring requires manually declaring every service in services.yaml. | «no» Пояснение: Autowiring's whole purpose is to automatically resolve dependencies based on type hints, so you do NOT need to manually declare every service in services.yaml.
Raw{"answer": "no", "explanation": "Autowiring's whole purpose is to automatically resolve dependencies based on type hints, so you do NOT need to manually declare every service in services.yaml."} | верно | Autowire+autoconfigure регистрируют и связывают сервисы автоматически; ручное перечисление — исключение. |
T13-L4 1.57 c | Symfony | Twig templates are compiled into PHP classes and cached between requests. | «yes» Пояснение: Twig compiles templates into PHP classes and stores the resulting PHP files in a cache directory so they can be reused on subsequent requests without recompilation.
Raw{"answer": "yes", "explanation": "Twig compiles templates into PHP classes and stores the resulting PHP files in a cache directory so they can be reused on subsequent requests without recompilation."} | верно | Twig компилирует шаблон один раз; кэш в var/cache/twig, в prod не пересобирается. |
T13-L5 1.43 c | Symfony | In the Symfony dev environment the DI container is rebuilt only after tracked files change, not on every request. | «yes» Пояснение: Symfony caches the compiled DI container and only rebuilds it when tracked files (e.g., service definitions, config) change, not on every request.
Raw{"answer": "yes", "explanation": "Symfony caches the compiled DI container and only rebuilds it when tracked files (e.g., service definitions, config) change, not on every request."} | верно | Kernel проверяет freshness ресурсов (конфиги, классы); иначе переиспользуется кэш контейнера. |
T13-L6 2.14 c | Symfony | Which environment variable selects the active Symfony environment (dev/prod)? | «symfony_env» Пояснение: The SYMFONY_ENV environment variable is used to select the active Symfony environment (e.g., dev, prod, staging).
Raw{"answer": "SYMFONY_ENV", "explanation": "The SYMFONY_ENV environment variable is used to select the active Symfony environment (e.g., dev, prod, staging)."} | неверно верный: «app_env» | APP_ENV в .env; APP_DEBUG — отдельный флаг отладки. |
T13-L7 3.48 c | Symfony | A controller method can be private — Symfony routing works with any method of the class. | «no» Пояснение: Symfony's ControllerResolver requires the action method to be public; a private (or protected) method will trigger a ReflectionException, so routing does not work with any arbitrary method of the class.
Raw{"answer": "no", "explanation": "Symfony's ControllerResolver requires the action method to be public; a private (or protected) method will trigger a ReflectionException, so routing does not work with any arbitrary method of the class."} | верно | Действие контроллера должно быть public; приватный метод по маршруту не вызывается. |
T13-L8 1.9 c | Symfony | Event subscribers always receive events before listeners, because the interface gives them priority. | «no» Пояснение: In Symfony's EventDispatcher, both listeners and subscribers are ordered by the priority parameter they specify, not by whether they are a listener or a subscriber; neither type inherently receives events first.
Raw{"answer": "no", "explanation": "In Symfony's EventDispatcher, both listeners and subscribers are ordered by the priority parameter they specify, not by whether they are a listener or a subscriber; neither type inherently receives events first."} | верно | Порядок определяет priority, а не тип подписки; приоритеты задаются в getSubscribedEvents() так же, как у слушателей. |
T22-L1 4.32 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+ uses the new authenticator system (with AuthenticationEntryPointInterface, etc.) as the primary authentication mechanism, and the old Guard system was deprecated in 6.0 and removed in 7.0.
Raw{"answer": "yes", "explanation": "Symfony 6.0+ uses the new authenticator system (with AuthenticationEntryPointInterface, etc.) as the primary authentication mechanism, and the old Guard system was deprecated in 6.0 and removed in 7.0."} | верно | Guard объявлен устаревшим в 5.3 и удалён в 6.0; в проекте symfony/security-bundle 8.1. |
T22-L2 1.96 c | Symfony: Security and forms | Which Symfony attribute checks a role/permission right on a controller method (403 without it)? | «isgranted» Пояснение: The #[IsGranted] attribute from Symfony Security checks whether the current user has a specified role or permission on a controller method, returning a 403 AccessDeniedException if they do not.
Raw{"answer": "IsGranted", "explanation": "The #[IsGranted] attribute from Symfony Security checks whether the current user has a specified role or permission on a controller method, returning a 403 AccessDeniedException if they do not."} | верно | #[IsGranted('ROLE_ADMIN')]; атрибут из symfony/security-http. |
T22-L3 0.97 c | Symfony: Security and forms | Voters are Symfony's mechanism for checking access to a specific object: isGranted('EDIT', $post). | «yes» Пояснение: Voters are Symfony's authorization mechanism for object-level access checks, used via isGranted('EDIT', $post).
Raw{"answer": "yes", "explanation": "Voters are Symfony's authorization mechanism for object-level access checks, used via isGranted('EDIT', $post)."} | верно | VoterInterface->vote(); docs Symfony — Voters. |
T22-L4 2.07 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, Doctrine annotation support was removed; PHP 8 attributes (e.g. #[Assert\NotBlank]) are the only supported way to declare validation constraints.
Raw{"answer": "yes", "explanation": "In Symfony 7, Doctrine annotation support was removed; PHP 8 attributes (e.g. #[Assert\\NotBlank]) are the only supported way to declare validation constraints."} | верно | Докблок-аннотации удалены в Symfony 7.0; стандарт — атрибуты. В проекте symfony/validator 8.1. |
T22-L5 0.92 c | Symfony: Security and forms | CSRF protection of Symfony forms is enabled by default: the form validates the token on submission. | «yes» Пояснение: Symfony automatically adds a CSRF token to every form and validates it on submission by default (since Symfony 2.0).
Raw{"answer": "yes", "explanation": "Symfony automatically adds a CSRF token to every form and validates it on submission by default (since Symfony 2.0)."} | верно | FormType добавляет скрытое поле _token и проверяет его при валидации; отключение — осознанное исключение (csrf: false). |
T22-L6 1.21 c | Symfony: Security and forms | Form validation in Symfony runs server-side even if the client-side (HTML5) checks passed. | «yes» Пояснение: Symfony form validation is performed server-side upon form submission, regardless of whether HTML5 client-side validation passed, as server-side validation is the authoritative check.
Raw{"answer": "yes", "explanation": "Symfony form validation is performed server-side upon form submission, regardless of whether HTML5 client-side validation passed, as server-side validation is the authoritative check."} | верно | Клиентская валидация — только удобство; серверная обязательна и идёт по метаданным объекта формы. |
T22-L7 0.6 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.19 c | Symfony: Security and forms | Symfony stores the user's password in the session in plain text. | «no» Пояснение: Symfony stores the user identifier and authentication token in the session, while the password is kept hashed in the database; the plain-text password is never placed in the session.
Raw{"answer": "no", "explanation": "Symfony stores the user identifier and authentication token in the session, while the password is kept hashed in the database; the plain-text password is never placed in the session."} | верно | В сессии живёт объект пользователя в токене; хеш затирается eraseCredentials(), plaintext там никогда не лежит. |
T23-L1 1.13 c | Symfony: configuration and services | Symfony bundle configuration lives in config/packages — one file per bundle or topic. | «yes» Пояснение: In modern Symfony (4+ with Flex), bundle and framework configuration is organized in config/packages/, with one YAML/XML file per bundle or topic (e.g., framework.yaml, twig.yaml, doctrine.yaml).
Raw{"answer": "yes", "explanation": "In modern Symfony (4+ with Flex), bundle and framework configuration is organized in config/packages/, with one YAML/XML file per bundle or topic (e.g., framework.yaml, twig.yaml, doctrine.yaml)."} | верно | Стандартная структура (config/packages/*.yaml); перегрузка — config/packages/<env>. |
T23-L2 3.85 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 well-known PHP convention (especially in Symfony) where .env holds committed dev defaults and .env.local holds uncommitted local secrets/overrides.
Raw{"answer": "yes", "explanation": "This is a well-known PHP convention (especially in Symfony) where .env holds committed dev defaults and .env.local holds uncommitted local secrets/overrides."} | верно | symfony/dotenv: .env — общий безопасный набор значений; локальные секреты — .env.local (gitignored) или secrets-хранилище. |
T23-L3 0.98 c | Symfony: configuration and services | Which Symfony command lists the container's registered services and their aliases? | «debug:container» Пояснение: The Symfony command 'bin/console debug:container' lists all registered services and their aliases in the service container.
Raw{"answer": "debug:container", "explanation": "The Symfony command 'bin/console debug:container' lists all registered services and their aliases in the service container."} | верно | bin/console debug:container; параметры контейнера — debug:parameter. |
T23-L4 2.41 c | Symfony: configuration and services | The Symfony container allows changing parameters at runtime: $container->setParameter() works from a controller. | «no» Пояснение: The Symfony container is frozen once the first service (e.g., the controller itself) is resolved, so calling setParameter() from a controller throws a LogicException.
Raw{"answer": "no", "explanation": "The Symfony container is frozen once the first service (e.g., the controller itself) is resolved, so calling setParameter() from a controller throws a LogicException."} | верно | Контейнер компилируется и замораживается; runtime-значения — только через переменные окружения. |
T23-L5 1.3 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; you must explicitly set public: true to fetch them from the container.
Raw{"answer": "no", "explanation": "Since Symfony 4, services are private (public: false) by default; you must explicitly set public: true to fetch them from the container."} | верно | С Symfony 4.0 сервисы по умолчанию private: инжектятся через autowiring; $container->get() — только для публичных. |
T23-L6 1.41 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 with all-default settings and do not require a dedicated config file in config/packages; a bundle only needs to be registered to function.
Raw{"answer": "no", "explanation": "Many Symfony bundles work with all-default settings and do not require a dedicated config file in config/packages; a bundle only needs to be registered to function."} | верно | У бандлов есть встроенные умолчания (Extension); конфиг нужен только для отклонений от них. |
T23-L7 0.85 c | Symfony: configuration and services | Environment variable values are injected into services.yaml using the %env(VAR)% syntax. | «yes» Пояснение: In Symfony, environment variables are referenced in services.yaml (and other config files) using the %env(VAR_NAME)% syntax.
Raw{"answer": "yes", "explanation": "In Symfony, environment variables are referenced in services.yaml (and other config files) using the %env(VAR_NAME)% syntax."} | верно | %env(...)% резолвится в рантайме env-процессорами; docs — Env Var Processors. |
T23-L8 1.16 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 in .env) enables or disables debug mode, which activates the profiler and Twig's debug features.
Raw{"answer": "APP_DEBUG", "explanation": "In Symfony, the APP_DEBUG environment variable (set in .env) enables or disables debug mode, which activates the profiler and Twig's debug features."} | верно | APP_DEBUG=1 (в .env dev-окружения); окружение выбирает APP_ENV — см. T13-L6. |
T16-L1 1.01 c | Symfony: Messenger | A single message in Symfony Messenger can only have one handler. | «no» Пояснение: Symfony Messenger allows multiple handlers to be registered for the same message class, and all of them will be invoked (ordered by priority).
Raw{"answer": "no", "explanation": "Symfony Messenger allows multiple handlers to be registered for the same message class, and all of them will be invoked (ordered by priority)."} | верно | Messenger вызывает все хендлеры, подписанные на класс сообщения (docs — Multiple Handlers). |
T16-L2 1.27 c | Symfony: Messenger | The sync transport in Messenger queues the message for a worker, just like async. | «no» Пояснение: The sync transport handles the message immediately in the same process without queuing it for a worker; that's the behavior of async transports.
Raw{"answer": "no", "explanation": "The sync transport handles the message immediately in the same process without queuing it for a worker; that's the behavior of async transports."} | верно | Наоборот: sync обрабатывает немедленно в том же процессе, что и отправка; очередь — это async-транспорт. |
T16-L3 0.87 c | Symfony: Messenger | Which console command starts the worker that processes Messenger queue messages? | «php bin/console messenger:consume» Пояснение: In Symfony, the messenger:consume command starts the worker process that pulls and dispatches queued messages from a transport.
Raw{"answer": "php bin/console messenger:consume", "explanation": "In Symfony, the messenger:consume command starts the worker process that pulls and dispatches queued messages from a transport."} | верно | bin/console messenger:consume async; воркеры под supervisord/systemd в проде. |
T16-L4 2.51 c | Symfony: Messenger | Retries for failed messages (retry_strategy) are configured per Messenger transport. | «no» Пояснение: In Symfony Messenger, the retry strategy (retry_strategy middleware) is configured per messenger bus, not per transport.
Raw{"answer": "no", "explanation": "In Symfony Messenger, the retry strategy (retry_strategy middleware) is configured per messenger bus, not per transport."} | неверно верный: «yes» | retry_strategy на транспорте: max_retries, delay, multiplier; docs — Failed Messages & Retries. |
T16-L5 1.26 c | Symfony: Messenger | By default, Messenger serializes messages to JSON. | «no» Пояснение: By default, Symfony Messenger uses PHP's native serializer (serialize/unserialize), not JSON.
Raw{"answer": "no", "explanation": "By default, Symfony Messenger uses PHP's native serializer (serialize/unserialize), not JSON."} | верно | Дефолтный сериализатор — PhpSerializer (serialize()); JSON-сериализатор включается отдельно. |
T16-L6 5.3 c | Symfony: Messenger | Symfony Scheduler produces messages on a schedule and dispatches them through Messenger. | «yes» Пояснение: Symfony Scheduler schedules tasks at defined intervals and integrates with Messenger to produce and dispatch messages on that schedule.
Raw{"answer": "yes", "explanation": "Symfony Scheduler schedules tasks at defined intervals and integrates with Messenger to produce and dispatch messages on that schedule."} | верно | Schedule → RecurringMessage → шина Messenger; docs — Scheduler. |
T16-L7 1.06 c | Symfony: Messenger | Which built-in Messenger transport stores messages in database tables via Doctrine? | «doctrine» Пояснение: Symfony Messenger's Doctrine transport persists messages to database tables using Doctrine ORM.
Raw{"answer": "Doctrine", "explanation": "Symfony Messenger's Doctrine transport persists messages to database tables using Doctrine ORM."} | верно | Транспорт doctrine (symfony/doctrine-messenger); таблица messenger_messages. В проекте стоит amqp-messenger + doctrine-messenger. |
T16-L8 1.73 c | Symfony: Messenger | The Messenger pipeline can be extended with custom middleware, placed before or after the built-in ones. | «yes» Пояснение: Laravel's Messenger pipeline is extensible; you can register custom middleware in the pipeline before or after the built-in middleware such as Dispatchable, Queueable, and SerializesModels.
Raw{"answer": "yes", "explanation": "Laravel's Messenger pipeline is extensible; you can register custom middleware in the pipeline before or after the built-in middleware such as Dispatchable, Queueable, and SerializesModels."} | верно | messenger.bus.*.middleware в yaml; docs — Middleware. |
T28-L1 1.55 c | Symfony: versions | Symfony major releases come every two years, minor ones every six months (in May and November). | «yes» Пояснение: Symfony follows a fixed schedule with major releases every two years in May and minor releases every six months in May and November.
Raw{"answer": "yes", "explanation": "Symfony follows a fixed schedule with major releases every two years in May and minor releases every six months in May and November."} | верно | Стандартный релизный цикл: 8.0 — ноябрь 2025, 8.1 — май 2026, 8.2 — ноябрь 2026. |
T28-L2 1.4 c | Symfony: versions | What is the minimum PHP version required by Symfony 8? | «8.4» Пояснение: Symfony 8 requires PHP 8.4 as the minimum version, following the pattern of each major Symfony version bumping the minimum PHP requirement.
Raw{"answer": "8.4", "explanation": "Symfony 8 requires PHP 8.4 as the minimum version, following the pattern of each major Symfony version bumping the minimum PHP requirement."} | верно | Symfony 8.0 поднял требование до PHP >= 8.4.1 (в vendor проекта: "php": ">=8.4.1"). |
T28-L3 1.1 c | Symfony: versions | Symfony 7.0 kept support for docblock annotations (validation, routes). | «no» Пояснение: Symfony 7.0 removed docblock annotation support entirely; only PHP 8 attributes are supported for validation, routing, etc.
Raw{"answer": "no", "explanation": "Symfony 7.0 removed docblock annotation support entirely; only PHP 8 attributes are supported for validation, routing, etc."} | верно | Наоборот: в 7.0 аннотации удалены — только PHP-атрибуты (#[Route], #[Assert\NotBlank]). |
T28-L4 1.58 c | Symfony: versions | AssetMapper manages CSS/JS without node or webpack — via importmap.php. | «yes» Пояснение: Symfony's AssetMapper component (7.1+) manages CSS/JS assets on the PHP side using importmap.php for package resolution, without requiring Node.js or webpack.
Raw{"answer": "yes", "explanation": "Symfony's AssetMapper component (7.1+) manages CSS/JS assets on the PHP side using importmap.php for package resolution, without requiring Node.js or webpack."} | верно | symfony/asset-mapper (с 6.3, стандарт с 7.x); в проекте — importmap.php в корне и asset-mapper 8.1. |
T28-L5 1.62 c | Symfony: versions | Symfony 6.4 is a regular release without long-term support. | «no» Пояснение: Symfony 6.4 is a Long-Term Support (LTS) release, receiving 2 years of bug fixes and 3 years of security fixes, unlike regular releases.
Raw{"answer": "no", "explanation": "Symfony 6.4 is a Long-Term Support (LTS) release, receiving 2 years of bug fixes and 3 years of security fixes, unlike regular releases."} | верно | Наоборот: 6.4 — LTS (расширенная поддержка); LTS выходит вместе с очередным мажором (6.4 — вместе с 7.0). |
T28-L6 3.24 c | Symfony: versions | When moving to a new Symfony major version, deprecations of the previous branch keep working — major releases do not remove them. | «no» Пояснение: Symfony's deprecation policy states that features deprecated in a given major version are removed in the next major version, so upgrading to a new major branch does remove the previous branch's deprecations.
Raw{"answer": "no", "explanation": "Symfony's deprecation policy states that features deprecated in a given major version are removed in the next major version, so upgrading to a new major branch does remove the previous branch's deprecations."} | верно | Наоборот: мажорный релиз удаляет всё устаревшее (7.0 убрал деприкейшены 6.x, 8.0 — 7.x). |
T28-L7 2.06 c | Symfony: versions | Every Symfony major release is accompanied by an UPGRADE guide listing the changes. | «yes» Пояснение: Symfony follows a long-standing convention of providing UPGRADE files (e.g., UPGRADE-6.0.md) in each component and bundle for every major release to document breaking changes.
Raw{"answer": "yes", "explanation": "Symfony follows a long-standing convention of providing UPGRADE files (e.g., UPGRADE-6.0.md) in each component and bundle for every major release to document breaking changes."} | верно | UPGRADE-7.0.md, UPGRADE-8.0.md в репозитории symfony/symfony. |
T28-L8 1.61 c | Symfony: versions | Which Symfony component manages assets and the importmap without node/webpack? | «assetmapper» Пояснение: Symfony's AssetMapper component (introduced in 6.3) manages assets and provides an import-map feature without requiring Node.js or Webpack.
Raw{"answer": "AssetMapper", "explanation": "Symfony's AssetMapper component (introduced in 6.3) manages assets and provides an import-map feature without requiring Node.js or Webpack."} | верно | symfony/asset-mapper 8.1 — в проекте. |
T29-L1 7.86 c | Symfony: 8.2 and beyond | As of 2026-11-07, Symfony 8.2 has already been released. | «no» Пояснение: Following Symfony's ~6-month release cadence, by November 2026 the latest would be around Symfony 7.4 or 8.0 at most; 8.2 would not be released until roughly 2027.
Raw{"answer": "no", "explanation": "Following Symfony's ~6-month release cadence, by November 2026 the latest would be around Symfony 7.4 or 8.0 at most; 8.2 would not be released until roughly 2027."} | верно | Наоборот: 8.2 ещё не выпущена — релиз в конце ноября 2026; последняя стабильная — 8.1. |
T29-L2 7.71 c | Symfony: 8.2 and beyond | As of 2026-11-07, Symfony 8.2 is scheduled for November 2026, following the usual six-month cycle. | «no» Пояснение: Following Symfony's six-month release cycle (Nov/May), Symfony 8.2 is scheduled for May 2026, while November 2026 corresponds to Symfony 8.3.
Raw{"answer": "no", "explanation": "Following Symfony's six-month release cycle (Nov/May), Symfony 8.2 is scheduled for May 2026, while November 2026 corresponds to Symfony 8.3."} | неверно верный: «yes» | Политика релизов: 8.1 — май 2026, 8.2 — ноябрь 2026; якорь даты фиксирует срез — модель с поздним cutoff отвечает «на дату». |
T29-L3 1.33 c | Symfony: 8.2 and beyond | Which Symfony version comes after 8.1 (as of 2026-11-07)? | «8.2» Пояснение: Following standard versioning, the next minor release after 8.1 is 8.2.
Raw{"answer": "8.2", "explanation": "Following standard versioning, the next minor release after 8.1 is 8.2."} | верно | 8.2 — следующий минорный релиз (ноябрь 2026); после его выхода проект переходит с 8.1.* на 8.2.*. |
T29-L4 2.17 c | Symfony: 8.2 and beyond | Symfony 8.2 is a major release requiring applications to be rewritten for new APIs. | «no» Пояснение: Symfony 8.2 is a minor release (x.2), not a major one (x.0); minor releases add features without breaking changes and do not require applications to be rewritten.
Raw{"answer": "no", "explanation": "Symfony 8.2 is a minor release (x.2), not a major one (x.0); minor releases add features without breaking changes and do not require applications to be rewritten."} | верно | Наоборот: 8.2 — минорный релиз; новые возможности без поломки обратной совместимости. Мажор — 9.0. |
T29-L5 2.52 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 guarantees backward compatibility for minor version upgrades (e.g., 8.1 → 8.2) within the same major version; only major version bumps may introduce breaking changes.
Raw{"answer": "yes", "explanation": "PHP guarantees backward compatibility for minor version upgrades (e.g., 8.1 → 8.2) within the same major version; only major version bumps may introduce breaking changes."} | верно | Политика Symfony: минорные релизы обратно совместимы; BC-break допустим только в мажорных. |
T29-L6 1.9 c | Symfony: 8.2 and beyond | Which minor version of the 8.x branch is released last, before Symfony 9.0? | «8.4» Пояснение: The last minor release of Symfony 8.x before Symfony 9.0 is 8.4, following Symfony's pattern of .0 through .4 minor versions per major branch.
Raw{"answer": "8.4", "explanation": "The last minor release of Symfony 8.x before Symfony 9.0 is 8.4, following Symfony's pattern of .0 through .4 minor versions per major branch."} | верно | По циклу: 8.2 (ноя 2026), 8.3 (май 2027), 8.4 (ноя 2027, вместе с 9.0) — как 6.4 выходила вместе с 7.0. |
T29-L7 5.27 c | Symfony: 8.2 and beyond | Symfony 8.2 will require PHP 8.5 — you would have to upgrade PHP along with it. | «no» Пояснение: Symfony 8.x (including 8.2) requires PHP 8.4 as its minimum version, not PHP 8.5.
Raw{"answer": "no", "explanation": "Symfony 8.x (including 8.2) requires PHP 8.4 as its minimum version, not PHP 8.5."} | верно | Наоборот: минорные релизы не поднимают требования PHP; для всей ветки 8.x остаётся PHP >= 8.4. |
T29-L8 2.37 c | Symfony: 8.2 and beyond | Deprecations added in the 8.x branch will not be removed before Symfony 9.0. | «yes» Пояснение: Symfony's deprecation policy guarantees that deprecations introduced in a given major version (8.x) are only removed in the following major version (9.0), so they will not be removed before 9.0.
Raw{"answer": "yes", "explanation": "Symfony's deprecation policy guarantees that deprecations introduced in a given major version (8.x) are only removed in the following major version (9.0), so they will not be removed before 9.0."} | верно | Политика: деприкейшены живут до следующего мажора; 9.0 — ноябрь 2027. |
T21-L1 2.25 c | Twig | Inside {{ }}, Twig allows calling arbitrary PHP code directly. | «no» Пояснение: Twig's {{ }} expressions support a limited subset (variables, method calls, filters, operators) but do not allow arbitrary PHP code like instantiating classes or calling any PHP function directly.
Raw{"answer": "no", "explanation": "Twig's {{ }} expressions support a limited subset (variables, method calls, filters, operators) but do not allow arbitrary PHP code like instantiating classes or calling any PHP function directly."} | верно | Twig — DSL: только разрешённые окружением функции/фильтры; произвольный PHP не исполняется. |
T21-L2 0.81 c | Twig | By default, Twig auto-escapes printed variables. | «yes» Пояснение: Twig enables auto-escaping with the 'html' strategy by default to protect against XSS and other injection attacks.
Raw{"answer": "yes", "explanation": "Twig enables auto-escaping with the 'html' strategy by default to protect against XSS and other injection attacks."} | верно | Autoescape включён по умолчанию; {{ '<b>' }} → <b>. Проверено на Twig 3.30. |
T21-L3 1.38 c | Twig | The Twig |e filter escapes a string for safe output in an HTML context. | «yes» Пояснение: The Twig |e (escape) filter defaults to HTML context, escaping special characters like <, >, &, ", and ' for safe HTML output.
Raw{"answer": "yes", "explanation": "The Twig |e (escape) filter defaults to HTML context, escaping special characters like <, >, &, \", and ' for safe HTML output."} | верно | |e ('html') по умолчанию; есть контексты js/url/css. От SQL-инъекций он не защищает — это задача подготовленных запросов Doctrine. |
T21-L4 0.82 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 specified locale using the PHP Intl extension.
Raw{"answer": "number_format", "explanation": "The twig/intl-extra package provides the 'number_format' filter which formats a number according to a specified locale using the PHP Intl extension."} | неверно верный: «format_number» | |format_number(locale=...) из IntlExtension (twig/intl-extra есть в проекте). Проверено на Twig 3.30: 12345.6 → 12 345,6 (ru). |
T21-L5 1.14 c | Twig | The |raw filter disables auto-escaping for the value. | «yes» Пояснение: In Twig, the |raw filter (alias of |safe) marks a value as already safe, preventing the template engine from auto-escaping it.
Raw{"answer": "yes", "explanation": "In Twig, the |raw filter (alias of |safe) marks a value as already safe, preventing the template engine from auto-escaping it."} | верно | {{ x|raw }} выводит HTML как есть; опасно с пользовательскими данными. Проверено на Twig 3.30. |
T21-L6 1.17 c | Twig | In Twig, {{ }} prints an expression value, while {% %} executes tags — conditions, loops, set. | «yes» Пояснение: In Twig, {{ }} is used to output/print expression values, while {% %} is used for control structures such as if, for, set, etc.
Raw{"answer": "yes", "explanation": "In Twig, {{ }} is used to output/print expression values, while {% %} is used for control structures such as if, for, set, etc."} | верно | Два блока синтаксиса Twig: вывод (echo) против логики. |
T21-L7 1.13 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, as well as through loop variables and other built-in constructs.
Raw{"answer": "no", "explanation": "Twig allows you to declare variables inside a template using the {% set %} tag, as well as through loop variables and other built-in constructs."} | верно | {% set y = ... %} объявляет переменную в шаблоне. Проверено на Twig 3.30. |
T21-L8 0.77 c | Twig | Which Twig function dumps the debug structure of a variable (array, object)? | «dump» Пояснение: The Twig 'dump()' function outputs the debug structure of variables such as arrays and objects.
Raw{"answer": "dump", "explanation": "The Twig 'dump()' function outputs the debug structure of variables such as arrays and objects."} | верно | {{ dump(x) }} (DebugExtension; в Symfony доступна в dev-окружении). |
T24-L1 1.24 c | Bootstrap | Bootstrap is a CSS/JS library of ready-made UI components, not an SPA framework. | «yes» Пояснение: Bootstrap is a CSS/JS UI component library, not a Single Page Application framework like React, Angular, or Vue.
Raw{"answer": "yes", "explanation": "Bootstrap is a CSS/JS UI component library, not a Single Page Application framework like React, Angular, or Vue."} | верно | Компоненты и утилиты поверх вашего HTML; SPA-фреймворки (React/Vue) — другой класс инструментов. В проекте vendored 5.3.3. |
T24-L2 1.12 c | Bootstrap | Which Bootstrap class gives a responsive container with a fixed max width per breakpoint? | «container» Пояснение: The .container class in Bootstrap provides a responsive fixed-width container with a maximum width that changes at each breakpoint (e.g., 540px, 720px, 960px, 1140px, 1320px).
Raw{"answer": "container", "explanation": "The .container class in Bootstrap provides a responsive fixed-width container with a maximum width that changes at each breakpoint (e.g., 540px, 720px, 960px, 1140px, 1320px)."} | верно | .container (фиксированная макс-ширина по брейкпоинтам) vs .container-fluid (на всю ширину). |
T24-L3 1.39 c | Bootstrap | The Bootstrap grid is built on CSS floats and splits a row into 16 columns. | «no» Пояснение: The Bootstrap grid splits a row into 12 columns, not 16, and modern versions (Bootstrap 4+) use Flexbox rather than CSS floats.
Raw{"answer": "no", "explanation": "The Bootstrap grid splits a row into 12 columns, not 16, and modern versions (Bootstrap 4+) use Flexbox rather than CSS floats."} | верно | Наоборот: flexbox (с Bootstrap 4) и 12 колонок; float-сетка — это Bootstrap 3. |
T24-L4 1.62 c | Bootstrap | Bootstrap's named breakpoints (the infix used in class names) are sm, md, lg, xl, xxl — five of them. | «yes» Пояснение: In Bootstrap 5, the five breakpoints with class-name infixes are sm, md, lg, xl, and xxl (xs is the default and requires no prefix).
Raw{"answer": "yes", "explanation": "In Bootstrap 5, the five breakpoints with class-name infixes are sm, md, lg, xl, and xxl (xs is the default and requires no prefix)."} | верно | Тиров всего шесть: xs (без инфикса) + пять именованных (576/768/992/1200/1400 px). |
T24-L5 3.4 c | Bootstrap | Utilities like .mt-3 or .px-2 use the spacing scale: the number is a multiple of $spacer. | «yes» Пояснение: Bootstrap's spacing utilities like .mt-3 and .px-2 draw from the $spacers map, whose default values are calculated as multiples (or fractions) of the $spacer variable.
Raw{"answer": "yes", "explanation": "Bootstrap's spacing utilities like .mt-3 and .px-2 draw from the $spacers map, whose default values are calculated as multiples (or fractions) of the $spacer variable."} | неверно верный: «no» | Spacing utilities; $spacer = 1rem. |
T24-L6 0.86 c | Bootstrap | Which Bootstrap 5 data attribute enables an interactive component (e.g. dropdown) on an element? | «data-bs-toggle» Пояснение: Bootstrap 5 uses the data-bs-toggle attribute to enable interactive components such as dropdowns, collapses, and tooltips on an element.
Raw{"answer": "data-bs-toggle", "explanation": "Bootstrap 5 uses the data-bs-toggle attribute to enable interactive components such as dropdowns, collapses, and tooltips on an element."} | верно | data-bs-toggle="dropdown" и т.п.; в Bootstrap 4 атрибут назывался data-toggle. |
T24-L7 0.75 c | Bootstrap | Bootstrap 5 components work without jQuery — in plain vanilla JS. | «yes» Пояснение: Bootstrap 5 removed the jQuery dependency and all its interactive components are built with vanilla JavaScript.
Raw{"answer": "yes", "explanation": "Bootstrap 5 removed the jQuery dependency and all its interactive components are built with vanilla JavaScript."} | верно | jQuery удалён в Bootstrap 5.0: data-bs-* атрибуты и JS API. В проекте vendored 5.3.3. |
T24-L8 1.71 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.36 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 run a schema tool command (e.g., orm:schema-tool:create) or use migrations to generate the database schema.
Raw{"answer": "no", "explanation": "Doctrine ORM does not auto-create tables at runtime; you must explicitly run a schema tool command (e.g., orm:schema-tool:create) or use migrations to generate the database schema."} | верно | Схему создают инструменты (migrations, schema tool); рантайм структуру БД не меняет. |
T14-L2 0.76 c | Doctrine | Which EntityManager method marks a new object as managed without executing SQL until flush()? | «persist» Пояснение: EntityManager::persist() schedules a new entity for insertion and marks it as managed without executing SQL until flush() is called.
Raw{"answer": "persist", "explanation": "EntityManager::persist() schedules a new entity for insertion and marks it as managed without executing SQL until flush() is called."} | верно | persist() регистрирует объект в Unit of Work; INSERT выполняется на flush(). |
T14-L3 5.2 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; you can simply call persist() or work with the entity directly instead of merging a detached instance back.
Raw{"answer": "no", "explanation": "In Doctrine ORM 3, EntityManager::merge() was removed; you can simply call persist() or work with the entity directly instead of merging a detached instance back."} | верно | В ORM 3 merge() удалён (в vendor проекта 3.7.6 метода нет); в Doctrine 2.x merge() возвращал управляемую копию. Версия зафиксирована — ORM 3. |
T14-L4 1.04 c | Doctrine | DQL queries are written in terms of entities and their fields, not tables and columns. | «yes» Пояснение: DQL (Doctrine Query Language) is an object-oriented query language that references entity class names and their mapped properties rather than raw table and column names.
Raw{"answer": "yes", "explanation": "DQL (Doctrine Query Language) is an object-oriented query language that references entity class names and their mapped properties rather than raw table and column names."} | верно | Doctrine транслирует DQL в SQL; docs — DQL (Doctrine Query Language). |
T14-L5 1.15 c | Doctrine | What does $repository->find(999) return when no record with id 999 exists? | «null» Пояснение: Doctrine's Repository::find() returns null when no entity with the given ID exists.
Raw{"answer": "null", "explanation": "Doctrine's Repository::find() returns null when no entity with the given ID exists."} | верно | find() возвращает null, если объект не найден (docs Repository methods). |
T14-L6 3.35 c | Doctrine | DoctrineBundle in Symfony automatically calls flush() at the end of every request. | «yes» Пояснение: DoctrineBundle registers a kernel.response event listener that automatically calls EntityManager::flush() at the end of each request.
Raw{"answer": "yes", "explanation": "DoctrineBundle registers a kernel.response event listener that automatically calls EntityManager::flush() at the end of each request."} | неверно верный: «no» | Авто-flush нет — flush() зовёт разработчик; незакрытая транзакция в конце запроса откатывается. |
T14-L7 1.76 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» Пояснение: A managed entity is already tracked by the Unit of Work, so property modifications are detected during change-set computation and committed on flush() without needing persist() again.
Raw{"answer": "yes", "explanation": "A managed entity is already tracked by the Unit of Work, so property modifications are detected during change-set computation and committed on flush() without needing persist() again."} | верно | Dirty checking сравнивает снимки свойств; persist нужен только новым/отсоединённым объектам. |
T14-L8 1.06 c | Doctrine | remove() executes the SQL DELETE immediately, without waiting for flush(). | «no» Пояснение: In Doctrine ORM, remove() merely marks the entity as 'removed' in the UnitOfWork; the actual SQL DELETE is only issued when flush() is called.
Raw{"answer": "no", "explanation": "In Doctrine ORM, remove() merely marks the entity as 'removed' in the UnitOfWork; the actual SQL DELETE is only issued when flush() is called."} | верно | remove() планирует удаление в Unit of Work; DELETE выполняется на flush() (docs — Deleting Objects). |
T15-L1 1.41 c | PostgreSQL | PostgreSQL uses MVCC, therefore readers block writers and writers block readers. | «no» Пояснение: MVCC in PostgreSQL ensures that readers do NOT block writers and writers do NOT block readers; readers see a consistent snapshot while writers can proceed independently.
Raw{"answer": "no", "explanation": "MVCC in PostgreSQL ensures that readers do NOT block writers and writers do NOT block readers; readers see a consistent snapshot while writers can proceed independently."} | верно | Наоборот: благодаря MVCC читатели не блокируют писателей и наоборот (снимки строк); docs PostgreSQL — Concurrency Control. |
T15-L2 1.25 c | PostgreSQL | Which SQL command shows a query's execution plan without executing the query? | «explain» Пояснение: The EXPLAIN command displays the query's execution plan (how the database will process the query) without actually running it.
Raw{"answer": "EXPLAIN", "explanation": "The EXPLAIN command displays the query's execution plan (how the database will process the query) without actually running it."} | верно | EXPLAIN без ANALYZE только строит план; проверено на PostgreSQL 17.7. |
T15-L3 3.8 c | PostgreSQL | SERIAL and GENERATED ... AS IDENTITY are just two names for the same mechanism. | «no» Пояснение: SERIAL is a shorthand that creates a sequence and a column DEFAULT, while GENERATED ... AS IDENTITY creates a true identity column with additional semantics (e.g., GENERATED ALWAYS vs BY DEFAULT, different behavior in information_schema, and different ALTER syntax), so they are related but not the same mechanism.
Raw{"answer": "no", "explanation": "SERIAL is a shorthand that creates a sequence and a column DEFAULT, while GENERATED ... AS IDENTITY creates a true identity column with additional semantics (e.g., GENERATED ALWAYS vs BY DEFAULT, different behavior in information_schema, and different ALTER syntax), so they are related but not the same mechanism."} | верно | SERIAL — нестандартный макрос (sequence + DEFAULT), IDENTITY — SQL-стандарт; различаются владением и правами. Оба есть в PG 17 (проверено). |
T15-L4 1.48 c | PostgreSQL | By default, a PostgreSQL UNIQUE constraint allows only one row with NULL in the column. | «no» Пояснение: By default, PostgreSQL treats NULLs as distinct from each other in a UNIQUE constraint, so multiple rows can have NULL in that column.
Raw{"answer": "no", "explanation": "By default, PostgreSQL treats NULLs as distinct from each other in a UNIQUE constraint, so multiple rows can have NULL in that column."} | верно | Наоборот: NULLS DISTINCT по умолчанию — несколько NULL допустимы; NULLS NOT DISTINCT — опция с PG 15. Проверено на PG 17.7. |
T15-L5 0.78 c | PostgreSQL | Which PostgreSQL aggregate function concatenates strings with a separator? | «string_agg» Пояснение: PostgreSQL's string_agg() aggregate function concatenates strings with a specified separator, e.g. string_agg(col, ', ').
Raw{"answer": "string_agg", "explanation": "PostgreSQL's string_agg() aggregate function concatenates strings with a specified separator, e.g. string_agg(col, ', ')."} | верно | string_agg(значение, разделитель); проверено на PostgreSQL 17.7. |
T15-L6 1.54 c | PostgreSQL | Plain VACUUM returns the space occupied by dead tuples to the operating system. | «no» Пояснение: Plain VACUUM only marks dead tuple space as reusable within the table file; it does not shrink the file or return space to the operating system (that requires VACUUM FULL).
Raw{"answer": "no", "explanation": "Plain VACUUM only marks dead tuple space as reusable within the table file; it does not shrink the file or return space to the operating system (that requires VACUUM FULL)."} | верно | VACUUM помечает место для переиспользования внутри таблицы; ОС его возвращает только VACUUM FULL (с эксклюзивной блокировкой). |
T15-L7 1.07 c | PostgreSQL | Which keyword in a window function definition partitions rows into groups the function is computed over? | «partition by» Пояснение: In SQL window functions, the PARTITION BY clause divides rows into groups over which the window function is computed.
Raw{"answer": "PARTITION BY", "explanation": "In SQL window functions, the PARTITION BY clause divides rows into groups over which the window function is computed."} | верно | OVER (PARTITION BY ...); проверено на PostgreSQL 17.7. |
T15-L8 1.46 c | PostgreSQL | The READ COMMITTED isolation level protects against non-repeatable reads. | «no» Пояснение: READ COMMITTED only prevents dirty reads (reading uncommitted data); non-repeatable reads require the REPEATABLE READ isolation level to be protected against.
Raw{"answer": "no", "explanation": "READ COMMITTED only prevents dirty reads (reading uncommitted data); non-repeatable reads require the REPEATABLE READ isolation level to be protected against."} | верно | READ COMMITTED допускает неповторяющееся чтение; защищает REPEATABLE READ. Проверено: SHOW transaction_isolation → read committed. |
T17-L1 0.95 c | PostgreSQL: transactions and indexes | By default, PostgreSQL wraps each single SQL statement in its own implicit transaction (autocommit). | «yes» Пояснение: PostgreSQL operates in autocommit mode by default, meaning each individual SQL statement is automatically committed in its own implicit transaction unless an explicit BEGIN/COMMIT block is used.
Raw{"answer": "yes", "explanation": "PostgreSQL operates in autocommit mode by default, meaning each individual SQL statement is automatically committed in its own implicit transaction unless an explicit BEGIN/COMMIT block is used."} | верно | Без BEGIN каждый оператор коммитится сам; docs PostgreSQL — Transactions. Проверено на PG 17. |
T17-L2 0.47 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.12 c | PostgreSQL: transactions and indexes | Indexes speed up more than SELECT: UPDATE and DELETE with a search on an indexed column benefit too. | «yes» Пояснение: Indexes are used by the database engine to quickly locate rows, so UPDATE and DELETE statements with a WHERE clause on an indexed column also benefit from the index, avoiding a full table scan.
Raw{"answer": "yes", "explanation": "Indexes are used by the database engine to quickly locate rows, so UPDATE and DELETE statements with a WHERE clause on an indexed column also benefit from the index, avoiding a full table scan."} | верно | Поиск строк для изменения идёт по индексу; docs PostgreSQL — Indexes. |
T17-L4 0.88 c | PostgreSQL: transactions and indexes | To roll back part of the statements inside a transaction, PostgreSQL uses SAVEPOINT. | «yes» Пояснение: PostgreSQL supports SAVEPOINT within a transaction, allowing partial rollback via ROLLBACK TO SAVEPOINT without undoing the entire transaction.
Raw{"answer": "yes", "explanation": "PostgreSQL supports SAVEPOINT within a transaction, allowing partial rollback via ROLLBACK TO SAVEPOINT without undoing the entire transaction."} | верно | SAVEPOINT name; ROLLBACK TO name — частичный откат без отмены всей транзакции. Проверено на PG 17. |
T17-L5 1.49 c | PostgreSQL: transactions and indexes | EXPLAIN ANALYZE shows the query plan without executing the query. | «no» Пояснение: EXPLAIN ANALYZE actually executes the query to provide real execution time statistics; plain EXPLAIN shows the plan without executing.
Raw{"answer": "no", "explanation": "EXPLAIN ANALYZE actually executes the query to provide real execution time statistics; plain EXPLAIN shows the plan without executing."} | верно | Наоборот: ANALYZE реально выполняет запрос (с побочными эффектами!) и показывает фактические времена узлов; план без выполнения — plain EXPLAIN. |
T17-L6 0.75 c | PostgreSQL: transactions and indexes | Which PostgreSQL extension adds vector types and indexes for embedding search? | «pgvector» Пояснение: pgvector is the PostgreSQL extension that adds a vector data type and index types (IVFFlat, HNSW) for embedding similarity search.
Raw{"answer": "pgvector", "explanation": "pgvector is the PostgreSQL extension that adds a vector data type and index types (IVFFlat, HNSW) for embedding similarity search."} | верно | CREATE EXTENSION vector (проект pgvector; в проекте образ pgvector/pgvector:pg17). |
T17-L7 1.11 c | PostgreSQL: transactions and indexes | A partial index (CREATE INDEX ... WHERE ...) is built only over rows satisfying the condition. | «yes» Пояснение: A partial index only includes rows that satisfy the specified WHERE condition, so it is indeed built only over those rows.
Raw{"answer": "yes", "explanation": "A partial index only includes rows that satisfy the specified WHERE condition, so it is indeed built only over those rows."} | верно | docs PostgreSQL — Partial Indexes; типичный кейс — индекс по «активным» записям. |
T17-L8 1.85 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 serialization anomalies via dependency tracking and aborts a transaction if a cycle is found, rather than locking the rows a transaction reads.
Raw{"answer": "no", "explanation": "PostgreSQL implements SERIALIZABLE using Serializable Snapshot Isolation (SSI), which detects serialization anomalies via dependency tracking and aborts a transaction if a cycle is found, rather than locking the rows a transaction reads."} | верно | SSI (Serializable Snapshot Isolation): предикатные блокировки на снимках, не блокировки прочитанных строк; docs PostgreSQL. |
T19-L1 0.57 c | HTTP and REST API | HTTP status 201 means the request resulted in a new resource being created. | «yes» Пояснение: HTTP 201 'Created' indicates that the request was successful and a new resource has been created as a result.
Raw{"answer": "yes", "explanation": "HTTP 201 'Created' indicates that the request was successful and a new resource has been created as a result."} | верно | 201 Created; обычно на POST, часто с Location; RFC 9110. |
T19-L2 1.21 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 6.6 c | HTTP and REST API | The DELETE method is idempotent per the HTTP specification: repeating the request for the same resource does not change the outcome. | «yes» Пояснение: RFC 7231/9110 explicitly classifies DELETE as an idempotent method: issuing the same DELETE request multiple times results in the same server state as issuing it once.
Raw{"answer": "yes", "explanation": "RFC 7231/9110 explicitly classifies DELETE as an idempotent method: issuing the same DELETE request multiple times results in the same server state as issuing it once."} | верно | RFC 9110: DELETE идемпотентен (как PUT); идемпотентность ≠ безопасность — ресурс удаляется при первом вызове. |
T19-L4 1.2 c | HTTP and REST API | The Access-Control-Allow-Origin header is sent by the client so that the server agrees to accept requests from another origin. | «no» Пояснение: The Access-Control-Allow-Origin header is sent by the server in the response to indicate which origin is allowed to access the resource, not by the client.
Raw{"answer": "no", "explanation": "The Access-Control-Allow-Origin header is sent by the server in the response to indicate which origin is allowed to access the resource, not by the client."} | верно | Наоборот: заголовок шлёт СЕРВЕР в ответе, разрешая браузеру cross-origin запрос (CORS); в проекте nelmio/cors-bundle. |
T19-L5 1.12 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 (defined in RFC 6585) is specifically used to indicate that a client has sent too many requests in a given time frame, i.e., rate limiting.
Raw{"answer": "yes", "explanation": "HTTP 429 Too Many Requests (defined in RFC 6585) is specifically used to indicate that a client has sent too many requests in a given time frame, i.e., rate limiting."} | верно | 429 (+ Retry-After); RFC 6585. В проекте symfony/rate-limiter. |
T19-L6 0.81 c | HTTP and REST API | 5xx codes mean a client error, while 4xx means a server-side error. | «no» Пояснение: It's the opposite: 4xx codes indicate client errors, and 5xx codes indicate server-side errors.
Raw{"answer": "no", "explanation": "It's the opposite: 4xx codes indicate client errors, and 5xx codes indicate server-side errors."} | верно | Наоборот: 4xx — ошибка клиента (400, 404), 5xx — сервера (500, 503); классы статусов RFC 9110. |
T19-L7 0.44 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.26 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, whereas PUT is defined as idempotent in the HTTP specification.
Raw{"answer": "yes", "explanation": "RFC 5789 explicitly states that PATCH is not idempotent, whereas PUT is defined as idempotent in the HTTP specification."} | верно | RFC 5789 прямо оговаривает: PATCH не гарантированно идемпотентен; PUT идемпотентен. |
T20-L1 1.56 c | Security and OAuth | Checking a password by comparing its hash to the stored hash with a plain == is sufficient. | «no» Пояснение: Plain == is vulnerable to timing attacks; PHP's hash_equals() should be used for constant-time comparison of password hashes.
Raw{"answer": "no", "explanation": "Plain == is vulnerable to timing attacks; PHP's hash_equals() should be used for constant-time comparison of password hashes."} | верно | Нужна постоянновременная проверка (password_verify) — timing-атаки; соль и алгоритм уже внутри хеша. |
T20-L2 1.08 c | Security and OAuth | A CSRF token is issued by the server (bound to the session) and verified server-side on unsafe requests (POST etc.). | «yes» Пояснение: A CSRF token is generated server-side, bound to the user's session, and validated server-side on unsafe (state-changing) requests like POST, PUT, or DELETE.
Raw{"answer": "yes", "explanation": "A CSRF token is generated server-side, bound to the user's session, and validated server-side on unsafe (state-changing) requests like POST, PUT, or DELETE."} | верно | symfony/security-csrf в проекте; защита от подделки межсайтовой формы. |
T20-L3 0.73 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 a CSP policy that restricts the sources from which a browser can load resources.
Raw{"answer": "Content-Security-Policy", "explanation": "The Content-Security-Policy HTTP header is used to declare a CSP policy that restricts the sources from which a browser can load resources."} | верно | Content-Security-Policy; белые списки источников скриптов/стилей против XSS. |
T20-L4 2.37 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 (not authentication) protocol; the access token represents granted permissions/scopes, while identity is conveyed by an ID token from OpenID Connect.
Raw{"answer": "no", "explanation": "OAuth 2.0 is an authorization (not authentication) protocol; the access token represents granted permissions/scopes, while identity is conveyed by an ID token from OpenID Connect."} | верно | OAuth 2.0 — авторизация/делегирование доступа; аутентификацию добавляет OpenID Connect. В проекте knpuniversity/oauth2-client-bundle (yandex/github/google). |
T20-L5 2.63 c | Security and OAuth | XSS is prevented by validating input on the server before writing it to the database. | «no» Пояснение: XSS is primarily prevented by context-aware output encoding when rendering data in the browser, not by input validation before database storage; input validation is a helpful defense-in-depth measure but is not the reliable primary defense against XSS.
Raw{"answer": "no", "explanation": "XSS is primarily prevented by context-aware output encoding when rendering data in the browser, not by input validation before database storage; input validation is a helpful defense-in-depth measure but is not the reliable primary defense against XSS."} | верно | XSS лечится контекстным экранированием НА ВЫВОДЕ (Twig autoescape, CSP); валидация ввода не покрывает все контексты вывода. |
T20-L6 1.58 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? | «authorization code» Пояснение: In the OAuth 2.0 authorization code flow, the authorization server redirects the user agent back to the redirect_uri with a 'code' parameter (the authorization code), which the client then exchanges for an access token at the token endpoint.
Raw{"answer": "authorization code", "explanation": "In the OAuth 2.0 authorization code flow, the authorization server redirects the user agent back to the redirect_uri with a 'code' parameter (the authorization code), which the client then exchanges for an access token at the token endpoint."} | верно | Параметр code; обмен на токен POST-ом на /token с client_secret. |
T20-L7 1.11 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 in OAuth2 are designed to have a longer lifespan than access tokens and are used to obtain new access tokens without requiring the user to re-authenticate.
Raw{"answer": "yes", "explanation": "Refresh tokens in OAuth2 are designed to have a longer lifespan than access tokens and are used to obtain new access tokens without requiring the user to re-authenticate."} | верно | Стандартная схема OAuth/OIDC: короткий access + длинный refresh. |
T20-L8 1.47 c | Security and OAuth | A password salt must be kept secret: without it the hash cannot be verified. | «no» Пояснение: A salt does not need to be secret; it is typically stored alongside the hash (e.g., in a database) because its purpose is to ensure uniqueness against rainbow-table attacks, not to provide secrecy.
Raw{"answer": "no", "explanation": "A salt does not need to be secret; it is typically stored alongside the hash (e.g., in a database) because its purpose is to ensure uniqueness against rainbow-table attacks, not to provide secrecy."} | верно | Соль хранится открыто (password_hash включает её в строку хеша); секретность соли не нужна. |
T18-L1 1.48 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; it will not discover or run test methods in arbitrary classes that do not extend it.
Raw{"answer": "no", "explanation": "PHPUnit requires test classes to extend PHPUnit\\Framework\\TestCase; it will not discover or run test methods in arbitrary classes that do not extend it."} | верно | Тестом считается метод класса, наследующего TestCase (PHPUnit 10). |
T18-L2 0.86 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 0.79 c | Testing: PHPUnit | A data provider lets a test run with exactly one set of arguments. | «no» Пояснение: A data provider is specifically designed to let a test run with multiple sets of arguments, not just one.
Raw{"answer": "no", "explanation": "A data provider is specifically designed to let a test run with multiple sets of arguments, not just one."} | верно | Наоборот: наборов может быть сколько угодно — тест выполняется по разу на каждый. Проверено на PHPUnit 10.5 (#[DataProvider]). |
T18-L4 0.73 c | Testing: PHPUnit | Which PHPUnit method declares an expectation that an exception of a given class is thrown? | «expectexception» Пояснение: PHPUnit's expectException() method declares an expectation that an exception of a given class will be thrown.
Raw{"answer": "expectException", "explanation": "PHPUnit's expectException() method declares an expectation that an exception of a given class will be thrown."} | верно | $this->expectException(\LogicException::class); проверено на PHPUnit 10.5. |
T18-L5 1.08 c | Testing: PHPUnit | In PHPUnit, a stub verifies which methods were called on it, while a mock only returns data. | «no» Пояснение: The statement has it backwards: a stub returns predefined data, while a mock verifies that expected methods were called.
Raw{"answer": "no", "explanation": "The statement has it backwards: a stub returns predefined data, while a mock verifies that expected methods were called."} | верно | Наоборот: стаб подставляет данные, мок проверяет взаимодействия (createStub/createMock); docs PHPUnit — Test Doubles. |
T18-L6 1.51 c | Testing: PHPUnit | In PHPUnit 10+, the recommended way to pass data to a test is the #[DataProvider] attribute (the @dataProvider annotation is deprecated). | «yes» Пояснение: In PHPUnit 10+, the #[DataProvider] attribute is the recommended replacement for the deprecated @dataProvider docblock annotation.
Raw{"answer": "yes", "explanation": "In PHPUnit 10+, the #[DataProvider] attribute is the recommended replacement for the deprecated @dataProvider docblock annotation."} | верно | Аннотация ещё парсится в PHPUnit 10/11 (AnnotationParser в 10.5.66), удаление — в 12; атрибут — стандарт. |
T18-L7 1.01 c | Testing: PHPUnit | PHPUnit does not allow one test to depend on the result of another. | «no» Пояснение: PHPUnit provides the @depends annotation (or depends() method) that allows a test to depend on and receive the return value of another test.
Raw{"answer": "no", "explanation": "PHPUnit provides the @depends annotation (or depends() method) that allows a test to depend on and receive the return value of another test."} | верно | Зависимости есть: #[Depends] — зависимый тест не запустится, еслиProducer упал. |
T18-L8 1.78 c | Testing: PHPUnit | Which PHPUnit command-line option makes tests run in random order? | «--random-order» Пояснение: The --random-order PHPUnit command-line option causes tests to be executed in a random sequence.
Raw{"answer": "--random-order", "explanation": "The --random-order PHPUnit command-line option causes tests to be executed in a random sequence."} | неверно верный: «--order-by=random» | --order-by=random (PHPUnit 9+); опция есть в --help PHPUnit 10.5 (проектная). |
T01-L9 3.88 c | Syntax and operators | What does this code output?
```php
echo intdiv(7, 2) . intdiv(-7, 2);
``` | «3-3» Пояснение: intdiv(7,2) is 3 and intdiv(-7,2) is -3 (truncates toward zero), concatenated as a string gives '3-3'.
Raw{"answer": "3-3", "explanation": "intdiv(7,2) is 3 and intdiv(-7,2) is -3 (truncates toward zero), concatenated as a string gives '3-3'."} | верно | intdiv truncates toward zero: intdiv(-7, 2) = -3, not -4. |
T01-L10 1.05 c | Syntax and operators | What does this code output?
```php
echo -3 ** 2;
``` | «-9» Пояснение: In PHP, the exponentiation operator ** has higher precedence than unary minus, so -3 ** 2 is parsed as -(3**2) = -9.
Raw{"answer": -9, "explanation": "In PHP, the exponentiation operator ** has higher precedence than unary minus, so -3 ** 2 is parsed as -(3**2) = -9."} | верно | ** is right-associative and binds tighter than unary minus: -(3²). |
T02-L9 2.59 c | Types and comparisons | What does this code output?
```php
echo '1e1' == '10' ? 'true' : 'false';
``` | «true» Пояснение: '1e1' and '10' are both numeric strings (scientific notation 1×10¹ = 10), so PHP compares them numerically as 10 == 10, which is true.
Raw{"answer": "true", "explanation": "'1e1' and '10' are both numeric strings (scientific notation 1×10¹ = 10), so PHP compares them numerically as 10 == 10, which is true."} | верно | Both strings are numeric — compared as numbers: 10 == 10. |
T02-L10 3.37 c | Types and comparisons | What does this code output?
```php
switch ('a') {
case 0: echo 'zero'; break;
default: echo 'other';
}
``` | «zero» Пояснение: PHP switch uses loose comparison (==), and in PHP 7, 'a' == 0 evaluates to true because 'a' is cast to the integer 0, so the case 0 branch is matched.
Raw{"answer": "zero", "explanation": "PHP switch uses loose comparison (==), and in PHP 7, 'a' == 0 evaluates to true because 'a' is cast to the integer 0, so the case 0 branch is matched."} | неверно верный: «other» | PHP 8: 'a' == 0 → false (used to be true) — default fires. |
T03-L9 3.1 c | Strings | What does this code output?
```php
echo strtr('abc', ['a' => '1', 'ab' => '2']);
``` | «2c» Пояснение: strtr with an array does a single pass; at position 0 both 'a' and 'ab' match, but the longest key 'ab' wins, so it's replaced with '2', leaving 'c' unchanged.
Raw{"answer": "2c", "explanation": "strtr with an array does a single pass; at position 0 both 'a' and 'ab' match, but the longest key 'ab' wins, so it's replaced with '2', leaving 'c' unchanged."} | верно | strtr with an array prefers the longest matching key. |
T03-L10 4.49 c | Strings | What does this code output?
```php
echo '[' . substr('hello', -10) . ']';
``` | «[]» Пояснение: In PHP 8, substr() returns an empty string when the negative start offset's absolute value exceeds the string length, so the result is '[]'.
Raw{"answer": "[]", "explanation": "In PHP 8, substr() returns an empty string when the negative start offset's absolute value exceeds the string length, so the result is '[]'."} | неверно верный: «[hello]» | A negative start beyond the string is clamped to the beginning. |
T04-L9 1.66 c | Arrays | What does this code output?
```php
$a = ['k' => 1, 'n' => 2];
$b = ['k' => 9, 'm' => 3];
echo implode(',', array_keys($a + $b));
``` | «k,n,m» Пояснение: The array union operator (+) keeps left-side values for duplicate keys and appends right-side unique keys, so array_keys yields ['k','n','m'], which implode outputs as 'k,n,m'.
Raw{"answer": "k,n,m", "explanation": "The array union operator (+) keeps left-side values for duplicate keys and appends right-side unique keys, so array_keys yields ['k','n','m'], which implode outputs as 'k,n,m'."} | верно | The + operator: on duplicate string keys the left array wins. |
T04-L10 2.0 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 index 2, giving order [2,'y',1], [1,'x',2], [3,'z',2]; array_column($a,1) extracts ['y','x','z']; implode yields 'yxz'.
Raw{"answer": "yxz", "explanation": "usort sorts by index 2, giving order [2,'y',1], [1,'x',2], [3,'z',2]; array_column($a,1) extracts ['y','x','z']; implode yields 'yxz'."} | верно | Sorts are stable since 8.0: x and z keep their order on a tie. |
T05-L10 5.29 c | Functions and closures | What does this code output?
```php
function f(int $a, int $b): int
{
return $a - $b;
}
echo f(...['b' => 1, 'a' => 5]);
``` | «4» Пояснение: Spreading an array with string keys creates named arguments, so b:1 and a:5 are matched by name, giving $a=5 and $b=1, resulting in 5-1=4.
Raw{"answer": 4, "explanation": "Spreading an array with string keys creates named arguments, so b:1 and a:5 are matched by name, giving $a=5 and $b=1, resulting in 5-1=4."} | верно | String keys of a spread array become named arguments. |
T05-L9 3.8 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(...) creates a closure bound to the object instance itself, not to the variable $p, so setting $p = null does not affect the closure's reference to the object, and $f() still returns 3.
Raw{"answer": 3, "explanation": "The first-class callable syntax $p->g(...) creates a closure bound to the object instance itself, not to the variable $p, so setting $p = null does not affect the closure's reference to the object, and $f() still returns 3."} | верно | First-class callable syntax binds $this at creation time. |
T06-L9 1.0 c | OOP: classes and inheritance | What does this code output?
```php
class A
{
public function who(): string { return static::class; }
}
class B extends A {}
echo (new B)->who();
``` | «b» Пояснение: static::class uses late static binding, so it resolves to the actual class of the object (B), not the class where the method is defined (A).
Raw{"answer": "B", "explanation": "static::class uses late static binding, so it resolves to the actual class of the object (B), not the class where the method is defined (A)."} | верно | Late static binding: static::class is the receiver's class. |
T06-L10 2.62 c | OOP: classes and inheritance | What does this code output on PHP 8.5?
```php
class C
{
public int $x = 0 {
set { $this->x = $value * 2; }
}
}
$c = new C;
$c->x = 5;
echo $c->x;
``` | «10» Пояснение: The setter multiplies the assigned value by 2, so assigning 5 sets the property to 10 (the assignment inside the setter does not recursively invoke the setter).
Raw{"answer": 10, "explanation": "The setter multiplies the assigned value by 2, so assigning 5 sets the property to 10 (the assignment inside the setter does not recursively invoke the setter)."} | верно | Inside the set hook, $this->x writes the backing store (no recursion): 5*2. |
T07-L9 1.32 c | Interfaces, traits, enum | What does this code output?
```php
trait TA
{
public function f(): string { return 'A'; }
}
trait TB
{
public function f(): string { return 'B'; }
}
class TC
{
use TA, TB { TB::f insteadof TA; TA::f as g; }
}
echo (new TC)->f() . (new TC)->g();
``` | «ba» Пояснение: TB::f insteadof TA makes f() return 'B', and TA::f as g aliases TA's f() as g() returning 'A', so the concatenation is 'BA'.
Raw{"answer": "BA", "explanation": "TB::f insteadof TA makes f() return 'B', and TA::f as g aliases TA's f() as g() returning 'A', so the concatenation is 'BA'."} | верно | insteadof picks the implementation; as keeps the other under an alias. |
T07-L10 1.99 c | Interfaces, traits, enum | What does this code output?
```php
trait Counter
{
public static int $n = 0;
}
class CX { use Counter; }
class CY { use Counter; }
CX::$n = 1;
echo CY::$n;
``` | «0» Пояснение: Each class that uses a trait gets its own independent copy of the static property, so setting CX::$n does not affect CY::$n which remains 0.
Raw{"answer": 0, "explanation": "Each class that uses a trait gets its own independent copy of the static property, so setting CX::$n does not affect CY::$n which remains 0."} | верно | A trait's static property is copied into each consuming class. |
T08-L10 1.34 c | Exceptions and errors | What does this code output?
```php
function f(): int
{
try { return 1; } finally { return 2; }
}
echo f();
``` | «2» Пояснение: A return statement in a finally block overrides the return value from the try block, so the function returns 2.
Raw{"answer": 2, "explanation": "A return statement in a finally block overrides the return value from the try block, so the function returns 2."} | верно | A return in finally overrides the return from try. |
T08-L9 1.35 c | Exceptions and errors | What does this code output?
```php
try {
try {
throw new RuntimeException('first');
} finally {
throw new LogicException('second');
}
} catch (LogicException $e) {
echo $e->getMessage();
}
``` | «second» Пояснение: When a finally block throws a new exception, it replaces the original RuntimeException, so the outer catch(LogicException) catches it and prints 'second'.
Raw{"answer": "second", "explanation": "When a finally block throws a new exception, it replaces the original RuntimeException, so the outer catch(LogicException) catches it and prints 'second'."} | верно | An exception from finally replaces the in-flight one — the last thrown is caught. |
T09-L9 2.14 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, outputting '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, outputting 'App\\Foo|Baz'."} | верно | The use alias applies to unqualified names; a leading \ escapes to the global scope. |
T09-L10 1.98 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 in the global namespace (not found, so 'no'), while class_exists('Ns\\Foo') finds the class defined in namespace Ns (so 'yes').
Raw{"answer": "noyes", "explanation": "class_exists('Foo') looks in the global namespace (not found, so 'no'), while class_exists('Ns\\\\Foo') finds the class defined in namespace Ns (so 'yes')."} | верно | Dynamic names are not resolved against the namespace — 'Foo' is the global class. |
T10-L9 1.27 c | References and scope | What does this code output?
```php
$a = [1, 2, 3];
foreach ($a as &$v) {}
$v = 99;
echo implode(',', $a);
``` | «1,2,99» Пояснение: After foreach by reference, $v remains a reference to the last element $a[2], so assigning 99 to $v changes $a[2] to 99, resulting in 1,2,99.
Raw{"answer": "1,2,99", "explanation": "After foreach by reference, $v remains a reference to the last element $a[2], so assigning 99 to $v changes $a[2] to 99, resulting in 1,2,99."} | верно | After a by-ref foreach, $v remains a reference to the last element. |
T10-L10 1.93 c | References and scope | What does this code output?
```php
class A
{
public function inc(): int
{
static $n = 0;
return ++$n;
}
}
class B extends A {}
$a = new A;
$b = new B;
$a->inc();
$b->inc();
echo $a->inc();
``` | «3» Пояснение: Static variables in a method are shared per class definition; since B inherits inc() from A, all calls share the same static $n, so after three ++$n calls the value is 3.
Raw{"answer": 3, "explanation": "Static variables in a method are shared per class definition; since B inherits inc() from A, all calls share the same static $n, so after three ++$n calls the value is 3."} | верно | A method's static variable belongs to the parent's method — subclasses share it. |
T11-L9 1.38 c | Generators, iterators, SPL | What does this code output?
```php
function g(): Generator
{
$x = yield 1;
return $x + 1;
}
$g = g();
$g->send(10);
echo $g->getReturn();
``` | «11» Пояснение: send(10) assigns x=10, then return x+1 evaluates to 11, which getReturn() retrieves and echo prints.
Raw{"answer": 11, "explanation": "send(10) assigns x=10, then return x+1 evaluates to 11, which getReturn() retrieves and echo prints."} | верно | send() resumes the generator: $x = 10, return 10+1. |
T11-L10 1.5 c | Generators, iterators, SPL | What does this code output?
```php
function inner(): Generator
{
yield 1;
yield 2;
return 'ok';
}
function outer(): Generator
{
$r = yield from inner();
yield $r;
}
echo implode(',', iterator_to_array(outer()));
``` | «1,2,ok» Пояснение: yield from inner() yields 1 and 2, captures the return value 'ok' into $r, then outer() yields $r, so the full sequence is 1, 2, 'ok'.
Raw{"answer": "1,2,ok", "explanation": "yield from inner() yields 1 and 2, captures the return value 'ok' into $r, then outer() yields $r, so the full sequence is 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.35 c | Configuration and security | What does this code output?
```php
$hash = password_hash('x', PASSWORD_BCRYPT, ['cost' => 4]);
echo password_needs_rehash($hash, PASSWORD_BCRYPT, ['cost' => 4]) ? 'yes' : 'no';
echo password_needs_rehash($hash, PASSWORD_BCRYPT, ['cost' => 5]) ? 'yes' : 'no';
``` | «noyes» Пояснение: The hash is created with cost 4, so password_needs_rehash with cost 4 returns false ('no'), and with cost 5 returns true ('yes').
Raw{"answer": "noyes", "explanation": "The hash is created with cost 4, so password_needs_rehash with cost 4 returns false ('no'), and with cost 5 returns true ('yes')."} | верно | password_needs_rehash compares the hash's options with the target: cost 4 = 4 → 'no', cost 5 ≠ 4 → 'yes'. |
T12-L10 7.01 c | Configuration and security | What does this code output on PHP 8.5?
```php
echo (E_ALL & 2048) === 0 ? 'strict-out' : 'strict-in';
``` | «strict-out» Пояснение: In PHP 8.5, E_STRICT (2048) is removed from E_ALL, so E_ALL & 2048 equals 0, making the ternary evaluate to 'strict-out'.
Raw{"answer": "strict-out", "explanation": "In PHP 8.5, E_STRICT (2048) is removed from E_ALL, so E_ALL & 2048 equals 0, making the ternary evaluate to 'strict-out'."} | верно | Since PHP 8.4, E_STRICT is out of E_ALL: the 2048 bit is unset → 'strict-out' (2048 is the historical E_STRICT bit). |
T13-L9 1.4 c | Symfony | What does this code output?
```php
use Symfony\Component\HttpFoundation\Request;
$r = Request::create('/demo', 'GET', [], [], [], ['HTTP_X_TOKEN' => 'abc']);
echo $r->headers->get('X-Token') === 'abc' ? 'mapped' : 'missing';
``` | «mapped» Пояснение: Symfony's HeaderBag automatically maps HTTP_X_TOKEN server parameter to the X-Token header, so the comparison returns true.
Raw{"answer": "mapped", "explanation": "Symfony's HeaderBag automatically maps HTTP_X_TOKEN server parameter to the X-Token header, so the comparison returns true."} | верно | The literal comparison requires knowing the mapping: HttpFoundation turns HTTP_X_TOKEN into the X-Token header (case-insensitive); without it the answer is 'missing'. |
T13-L10 1.17 c | Symfony | What does this code output?
```php
use Symfony\Component\EventDispatcher\EventDispatcher;
use Symfony\Contracts\EventDispatcher\Event;
$d = new EventDispatcher();
$out = '';
$d->addListener('e', function () use (&$out) { $out .= 'B'; }, 10);
$d->addListener('e', function () use (&$out) { $out .= 'A'; });
$d->addListener('e', function () use (&$out) { $out .= 'C'; }, 5);
$d->dispatch(new Event(), 'e');
echo $out;
``` | «bca» Пояснение: Listeners are called in descending priority order: priority 10 (B), priority 5 (C), then default priority 0 (A).
Raw{"answer": "BCA", "explanation": "Listeners are called in descending priority order: priority 10 (B), priority 5 (C), then default priority 0 (A)."} | верно | Listeners run by descending priority: 10 (B), 5 (C), 0 (A). |
T14-L10 1.76 c | Doctrine | Given: Doctrine ORM 3, an EntityManager on in-memory SQLite, entity User with an auto-increment primary key. The users table is empty. What does this code output?
```php
$u = new User(name: 'A');
$em->persist($u);
$em->flush();
$a = $em->find(User::class, $u->getId());
$b = $em->find(User::class, $u->getId());
echo spl_object_id($a) === spl_object_id($b) ? 'same' : 'diff';
``` | «same» Пояснение: Doctrine's EntityManager identity map ensures that calling find() with the same ID returns the same object instance, so spl_object_id is equal for both $a and $b.
Raw{"answer": "same", "explanation": "Doctrine's EntityManager identity map ensures that calling find() with the same ID returns the same object instance, so spl_object_id is equal for both $a and $b."} | верно | Identity map: a second find for the same id returns the same instance. |
T14-L9 18.48 c | Doctrine | Given: Doctrine ORM 3, an EntityManager on in-memory SQLite, entity User with an auto-increment primary key. The users table is empty. What does this code output?
```php
$u = new User(name: 'B');
$em->persist($u);
$em->remove($u);
$em->flush();
echo count($em->getConnection()->fetchAllAssociative('SELECT * FROM users'));
``` | «0» Пояснение: When persist() is followed by remove() before flush(), Doctrine's UnitOfWork cancels the pending INSERT (the entity's state is REMOVED, so it is excluded from the insert set during computeChangeSets), and since no ID was ever assigned (auto-increment, never actually inserted), the scheduled DELETE is a no-op, leaving the table empty.
Raw{"answer": 0, "explanation": "When persist() is followed by remove() before flush(), Doctrine's UnitOfWork cancels the pending INSERT (the entity's state is REMOVED, so it is excluded from the insert set during computeChangeSets), and since no ID was ever assigned (auto-increment, never actually inserted), the scheduled DELETE is a no-op, leaving the table empty."} | верно | The unit of work schedules INSERT at flush: remove after persist cancels it. |
T15-L10 1.11 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) only counts non-NULL values in column x, and there is one NULL row, so the result is 1.
Raw{"answer": 1, "explanation": "COUNT(x) only counts non-NULL values in column x, and there is one NULL row, so the result is 1."} | верно | count(column) skips NULLs; count(*) would return 2. |
T15-L9 1.58 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 sums 10, 30, 60, and string_agg concatenates them with commas in id order.
Raw{"answer": "10,30,60", "explanation": "The window function sum(x) OVER (ORDER BY id) produces running sums 10, 30, 60, and string_agg concatenates them with commas in id order."} | верно | With ORDER BY the default window frame is running (start to current row). |
T16-L9 1.51 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» Пояснение: Middleware is processed in order: M1 echoes 'M1' then delegates to M2 which echoes 'M2' before reaching the terminal handler, so the output is 'M1M2'.
Raw{"answer": "M1M2", "explanation": "Middleware is processed in order: M1 echoes 'M1' then delegates to M2 which echoes 'M2' before reaching the terminal handler, so the output is 'M1M2'."} | верно | The first-added middleware runs first (outermost). |
T16-L10 24.34 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 with a HandlersLocator containing multiple handlers for the same message type invokes all of them in sequence, so both closures execute: $n += 1 then $n += 10, yielding 11.
Raw{"answer": 11, "explanation": "HandleMessageMiddleware with a HandlersLocator containing multiple handlers for the same message type invokes all of them in sequence, so both closures execute: $n += 1 then $n += 10, yielding 11."} | верно | All registered handlers of the message run: 1 + 10 = 11. |
T17-L9 1.64 c | PostgreSQL: transactions and indexes | What does this SQL query return (PostgreSQL 17)?
```sql
CREATE TEMP TABLE t (a int);
CREATE UNIQUE INDEX ON t (a);
INSERT INTO t VALUES (1) ON CONFLICT DO NOTHING;
INSERT INTO t VALUES (1) ON CONFLICT DO NOTHING;
SELECT count(*) FROM t;
``` | «1» Пояснение: The first INSERT succeeds, the second is skipped by ON CONFLICT DO NOTHING due to the unique index, leaving one row in the table.
Raw{"answer": 1, "explanation": "The first INSERT succeeds, the second is skipped by ON CONFLICT DO NOTHING due to the unique index, leaving one row in the table."} | верно | ON CONFLICT DO NOTHING skips the duplicate: one insert. |
T17-L10 1.84 c | PostgreSQL: transactions and indexes | What does this sequence of psql commands output?
```sql
BEGIN;
CREATE TEMP TABLE t (a int, UNIQUE (a) DEFERRABLE INITIALLY DEFERRED);
INSERT INTO t VALUES (1);
INSERT INTO t VALUES (1);
SELECT count(*) FROM t;
``` | «2» Пояснение: Because the UNIQUE constraint is DEFERRABLE INITIALLY DEFERRED, the uniqueness check is postponed until COMMIT, so both INSERTs succeed and the table contains 2 rows.
Raw{"answer": 2, "explanation": "Because the UNIQUE constraint is DEFERRABLE INITIALLY DEFERRED, the uniqueness check is postponed until COMMIT, so both INSERTs succeed and the table contains 2 rows."} | верно | DEFERRED postpones the uniqueness check to COMMIT — count sees 2 rows. |
T18-L9 2.26 c | Testing: PHPUnit | How many tests will this command run?
```php
use PHPUnit\Framework\TestCase;
use PHPUnit\Framework\Attributes\DataProvider;
final class CalcTest extends TestCase
{
public static function prov(): array
{
return [[1], [2], [3]];
}
#[DataProvider('prov')]
public function test_sum(int $x): void
{
$this->assertTrue($x > 0);
}
#[DataProvider('prov')]
public function test_sum_abs(int $x): void
{
$this->assertTrue($x > 0);
}
public function test_other(): void
{
$this->assertTrue(true);
}
}
```
Command: `phpunit CalcTest.php --filter test_sum` (PHPUnit 10.5) | «6» Пояснение: The --filter test_sum regex matches both test_sum (3 data sets) and test_sum_abs (3 data sets), totaling 6 tests.
Raw{"answer": 6, "explanation": "The --filter test_sum regex matches both test_sum (3 data sets) and test_sum_abs (3 data sets), totaling 6 tests."} | верно | --filter is a substring match: test_sum also matches test_sum_abs (3+3 datasets). |
T18-L10 1.36 c | Testing: PHPUnit | How many tests will this command run, and how many of them will fail? Answer with two comma-separated numbers (ran, failed).
```php
use PHPUnit\Framework\TestCase;
use PHPUnit\Framework\Attributes\DataProvider;
final class Calc2Test extends TestCase
{
public function prov(): array
{
return [[1], [-1]];
}
#[DataProvider('prov')]
public function test_x(int $x): void
{
$this->assertTrue($x > 0);
}
}
```
Command: `phpunit Calc2Test.php` (PHPUnit 10.5) | «2, 1» Пояснение: The data provider supplies two values (1 and -1), so 2 tests run; the assertion $x > 0 fails for -1, so 1 test fails.
Raw{"answer": "2, 1", "explanation": "The data provider supplies two values (1 and -1), so 2 tests run; the assertion $x > 0 fails for -1, so 1 test fails."} | верно | A non-static provider is just a deprecation in PHPUnit 10: both datasets run and the [-1] dataset fails the assert — 2 ran, 1 failure. |
T19-L9 0.73 c | HTTP and REST API | Which HTTP method does this command send?
```bash
curl -s -d 'a=1' http://demo.local/api
``` | «post» Пояснение: The -d flag in curl sends data in the request body, which automatically sets the HTTP method to POST.
Raw{"answer": "POST", "explanation": "The -d flag in curl sends data in the request body, which automatically sets the HTTP method to POST."} | верно | -d/-F switches curl to POST by default. |
T19-L10 1.02 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 instructs curl to use the GET method, appending the -d data as a query string to the URL.
Raw{"answer": "GET", "explanation": "The -G flag instructs curl to use the GET method, appending the -d data as a query string to the URL."} | верно | -G turns -d data into the query string; the method stays GET. |
T20-L9 1.56 c | Security and OAuth | A client hits the token endpoint (RFC 6749) with a non-existent client_id. What value of the error field does the endpoint return? | «invalid_client» Пояснение: RFC 6749 Section 5.2 specifies that if the client fails authentication (e.g., non-existent client_id), the token endpoint returns the error value 'invalid_client'.
Raw{"answer": "invalid_client", "explanation": "RFC 6749 Section 5.2 specifies that if the client fails authentication (e.g., non-existent client_id), the token endpoint returns the error value 'invalid_client'."} | верно | Unknown client → invalid_client (RFC 6749 §5.2). |
T20-L10 1.39 c | Security and OAuth | OAuth 2.0: the client started the flow with response_type=token. In which part of the redirect_uri does the authorization server pass the access_token? | «fragment» Пояснение: In the OAuth 2.0 implicit flow (response_type=token), the access token is passed in the fragment (the part after #) of the redirect URI, so it is not transmitted in the HTTP Referer header.
Raw{"answer": "fragment", "explanation": "In the OAuth 2.0 implicit flow (response_type=token), the access token is passed in the fragment (the part after #) of the redirect URI, so it is not transmitted in the HTTP Referer header."} | верно | The implicit flow passes the token in the URL fragment (#) — it never reaches the server. |
T21-L9 9.63 c | Twig | What does this Twig template output?
```twig
{{ false|default(2) * 3 }}
``` | «6» Пояснение: In Twig, the default filter considers false as empty (via PHP's empty()), so false|default(2) evaluates to 2, and 2 * 3 = 6.
Raw{"answer": 6, "explanation": "In Twig, the default filter considers false as empty (via PHP's empty()), so false|default(2) evaluates to 2, and 2 * 3 = 6."} | верно | default replaces exactly false/null/''/[] — false becomes 2, 2*3 = 6; the naive 'default is for undefined only' yields 0. |
T21-L10 6.46 c | Twig | What exception class does render() of this template throw?
```twig
{{ 'a' ~ 1 + 2 }}
``` | «a3» Пояснение: In Twig, the + operator has higher precedence than ~, so the expression evaluates as 'a' ~ (1+2) = 'a' ~ 3 = 'a3' with no exception thrown.
Raw{"answer": "a3", "explanation": "In Twig, the + operator has higher precedence than ~, so the expression evaluates as 'a' ~ (1+2) = 'a' ~ 3 = 'a3' with no exception thrown."} | неверно верный: «runtimeerror» | In Twig ~ binds tighter than +: ('a' ~ 1) + 2 → string + int → a render error (RuntimeError). |
T22-L9 2.87 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» Пояснение: NotBlank fails only on null, empty string, false, or an empty array (count 0); since [''] has one element it passes, yielding 0 violations.
Raw{"answer": 0, "explanation": "NotBlank fails only on null, empty string, false, or an empty array (count 0); since [''] has one element it passes, yielding 0 violations."} | верно | NotBlank treats null, '', [] as blank — the array [''] is not blank. |
T22-L10 5.18 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 an unsubmitted form throws a LogicException because a form that has not been submitted can never be valid.
Raw{"answer": "Symfony\\Component\\Form\\Exception\\LogicException", "explanation": "Calling isValid() on an unsubmitted form throws a LogicException because a form that has not been submitted can never be valid."} | верно | isValid() on a non-submitted form throws LogicException, it does not return false. |
T23-L9 2.17 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» Пояснение: By default, Symfony DI services are shared (singleton), so repeated calls to get() return the same cached instance.
Raw{"answer": "same", "explanation": "By default, Symfony DI services are shared (singleton), so repeated calls to get() return the same cached instance."} | верно | Container services are shared: two get() calls yield one instance. |
T23-L10 1.3 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 parameters are resolved during compile: 'name' is 'Bob', 'greeting' becomes 'hi Bob', and 'message' becomes 'hi Bob!'.
Raw{"answer": "hi Bob!", "explanation": "The parameters are resolved during compile: 'name' is 'Bob', 'greeting' becomes 'hi Bob', and 'message' becomes 'hi Bob!'."} | верно | compile() resolves %-references transitively: %greeting% → 'hi %name%' → 'hi Bob!', the answer assembles over two hops. |
T24-L9 1.68 c | Bootstrap | What is the max-width of .container in Bootstrap 5.3 at a 992px viewport? | «960px» Пояснение: At a 992px viewport the lg breakpoint (≥992px) applies, and Bootstrap 5.3 sets .container's max-width to 960px at that breakpoint.
Raw{"answer": "960px", "explanation": "At a 992px viewport the lg breakpoint (≥992px) applies, and Bootstrap 5.3 sets .container's max-width to 960px at that breakpoint."} | верно | 5.x container widths: 540/720/960/1140/1320 (sm–xxl); 992 → 960px. |
T24-L10 1.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 is defined after text-primary, so with equal specificity the later rule wins the cascade.
Raw{"answer": "text-danger", "explanation": "In Bootstrap 5.3's generated CSS, text-danger is defined after text-primary, so with equal specificity the later rule wins the cascade."} | верно | Specificity ties — the later rule wins: text-danger is declared after text-primary. |
T25-L9 1.25 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 class is in the Domain layer, which may only depend on Domain; using Application\PlaceOrder and Infrastructure\Db are two violations.
Raw{"answer": 2, "explanation": "The class is in the Domain layer, which may only depend on Domain; using Application\\PlaceOrder and Infrastructure\\Db are two violations."} | верно | Domain may depend only on Domain: PlaceOrder (Application) + Db (Infrastructure) = 2. |
T25-L10 1.34 c | Clean architecture | Layers: Domain, Application, Infrastructure. Deptrac rules: Application → Domain; Infrastructure → Domain, Application; Domain → Domain only.
How many violations will deptrac report for this class?
```php
namespace App\Domain;
use App\Application\PlaceOrder;
use App\Infrastructure\Db;
class BillingService
{
public function __construct(
private PlaceOrder $handler,
private Db $db,
private \App\Infrastructure\Logger $logger,
) {}
}
``` | «3» Пояснение: The Domain class depends on App\Application\PlaceOrder (1 violation), App\Infrastructure\Db (2nd violation), and App\Infrastructure\Logger (3rd violation), since Domain may only depend on Domain.
Raw{"answer": 3, "explanation": "The Domain class depends on App\\Application\\PlaceOrder (1 violation), App\\Infrastructure\\Db (2nd violation), and App\\Infrastructure\\Logger (3rd violation), since Domain may only depend on Domain."} | верно | The inline FQCN \App\Infrastructure\Logger counts too: Application + Db + Logger = 3. |
T26-L10 0.9 c | DDD | What does this code output?
```php
final class Money
{
public function __construct(public readonly int $amount) {}
public function add(Money $o): Money
{
return new self($this->amount + $o->amount);
}
}
$a = new Money(10);
$c = $a->add(new Money(5));
echo $a->amount . ',' . $c->amount;
``` | «10,15» Пояснение: The Money object is immutable (readonly int), so $a retains amount 10 while $c is a new object with amount 15.
Raw{"answer": "10,15", "explanation": "The Money object is immutable (readonly int), so $a retains amount 10 while $c is a new object with amount 15."} | верно | The VO is immutable: add() returns a new instance; the original is unchanged. |
T26-L9 1.16 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 before unsetting, so the item 'a' remains in the array, and count() returns 1.
Raw{"answer": 1, "explanation": "The remove method throws before unsetting, so the item 'a' remains in the array, and count() returns 1."} | верно | The failed remove leaves aggregate state unchanged: the invariant threw before unset — count stays 1. |
VC-L9 3.63 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 5.44 c | PHP 8.4–8.5 | What does this code output on PHP 8.5?
```php
class Heavy
{
public int $v = 0;
}
$r = new ReflectionClass(Heavy::class);
$o = $r->newLazyGhost(function (Heavy $obj) {
$obj->v = 21;
});
echo $r->isUninitializedLazyObject($o) ? 'yes' : 'no';
$o->v;
echo $r->isUninitializedLazyObject($o) ? 'yes' : 'no';
``` | «yesno» Пояснение: Before property access the lazy ghost is uninitialized (prints 'yes'), and after accessing $o->v the object is initialized (prints 'no').
Raw{"answer": "yesno", "explanation": "Before property access the lazy ghost is uninitialized (prints 'yes'), and after accessing $o->v the object is initialized (prints 'no')."} | верно | newLazyGhost (8.4): the object stays lazy until first access — reading a property initializes it and clears the flag. |
T28-L9 1.5 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 authenticator system (including AbstractGuardAuthenticator) was removed in Symfony 6.0, so the class does not exist in Symfony 8.1.
Raw{"answer": "no", "explanation": "The Guard authenticator system (including AbstractGuardAuthenticator) was removed in Symfony 6.0, so the class does not exist in Symfony 8.1."} | верно | Guard authentication was removed in Symfony 7.0 — the class is gone in 8.1. |
T28-L10 2.42 c | Symfony: versions | The project was upgraded from Symfony 6.4 to 8.1. What does this code output on 8.1?
```php
echo class_exists(\Symfony\Component\Routing\Loader\AnnotationClassLoader::class)
? 'yes' : 'no';
echo class_exists(\Symfony\Component\Routing\Loader\AttributeClassLoader::class)
? 'yes' : 'no';
``` | «noyes» Пояснение: In Symfony 8.1, AnnotationClassLoader was removed (deprecated in 6.1, removed in 7.0), while AttributeClassLoader exists, so the output is 'no' followed by 'yes'.
Raw{"answer": "noyes", "explanation": "In Symfony 8.1, AnnotationClassLoader was removed (deprecated in 6.1, removed in 7.0), while AttributeClassLoader exists, so the output is 'no' followed by 'yes'."} | верно | Annotation loaders were removed in 7.0; only attribute loaders remain (Annotation→Attribute). |