Пример запроса (первая клетка). System одинаковый во всех запросах прогона, user — свой вопрос для каждой клетки:
| Клетка | Тема | Утверждение | Ответ |
Результат | Обоснование |
T01-L1 4.21 c | Syntax and operators | Double-quoted and single-quoted strings are processed identically; the difference is only in speed. | «no» Пояснение: Single-quoted strings only handle \\ and \\' escapes and do not interpolate variables, while double-quoted strings process all escape sequences and interpolate variables and expressions, so the difference is functional, not just speed.
Raw{"answer": "no", "explanation": "Single-quoted strings only handle \\\\ and \\\\' escapes and do not interpolate variables, while double-quoted strings process all escape sequences and interpolate variables and expressions, so the difference is functional, not just speed."} | верно | В двойных кавычках работают интерполяция переменных и escape-последовательности, в одинарных — нет. |
T01-L2 1.54 c | Syntax and operators | The ?? operator follows isset semantics and raises no warnings for undefined variables. | «yes» Пояснение: The null coalescing operator ?? is syntactic sugar for isset($var) ? $var : default, and like isset(), it does not raise warnings for undefined variables.
Raw{"answer": "yes", "explanation": "The null coalescing operator ?? is syntactic sugar for isset($var) ? $var : default, and like isset(), it does not raise warnings for undefined variables."} | верно | ?? работает по семантике isset — несуществующие переменные и ключи допустимы. |
T01-L3 0.7 c | Syntax and operators | What will this print: echo 'a', 'b'; | «ab» Пояснение: PHP's echo with multiple comma-separated arguments outputs them concatenated with no separator.
Raw{"answer": "ab", "explanation": "PHP's echo with multiple comma-separated arguments outputs them concatenated with no separator."} | верно | echo принимает список аргументов: ab. |
T01-L4 1.03 c | Syntax and operators | print returns the value 1 and can be used inside an expression. | «yes» Пояснение: In PHP, print is a language construct that returns the integer 1, allowing it to be used within expressions (unlike echo, which returns nothing).
Raw{"answer": "yes", "explanation": "In PHP, print is a language construct that returns the integer 1, allowing it to be used within expressions (unlike echo, which returns nothing)."} | верно | print — выражение со значением 1, в отличие от echo, который значения не возвращает. |
T01-L5 1.18 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, and the right operand when the left is falsy.
Raw{"answer": "no", "explanation": "The Elvis operator ($a ?: $b) returns the left operand when it is truthy, and the right operand when the left is falsy."} | верно | Наоборот: $a ?: $b возвращает $a, если он истинный, иначе $b. |
T01-L6 1.47 c | Syntax and operators | In PHP 8, the concatenation operator (.) has lower precedence than addition and subtraction. | «yes» Пояснение: In PHP, arithmetic operators (+, -) have higher precedence than the string concatenation operator (.), so concatenation is evaluated after addition and subtraction.
Raw{"answer": "yes", "explanation": "In PHP, arithmetic operators (+, -) have higher precedence than the string concatenation operator (.), so concatenation is evaluated after addition and subtraction."} | верно | С PHP 8 (RFC concat precedence) '.' имеет приоритет ниже арифметики: 'сумма: ' . 2 + 3 → 'сумма: 5' (в PHP 7 было иначе). |
T01-L7 1.02 c | Syntax and operators | The expression 2 ** 3 ** 2 in PHP evaluates as (2 ** 3) ** 2, that is, 64. | «no» Пояснение: The ** operator in PHP is right-associative, so 2 ** 3 ** 2 evaluates as 2 ** (3 ** 2) = 2 ** 9 = 512, not (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.19 c | Syntax and operators | What string will this print: echo 'sum: ' . 2 + 3; (PHP 8)? | «3» Пояснение: Concatenation (.) has higher precedence than addition (+), so it evaluates ('sum: ' . 2) + 3, which is 'sum: 2' + 3 = 0 + 3 = 3.
Raw{"answer": 3, "explanation": "Concatenation (.) has higher precedence than addition (+), so it evaluates ('sum: ' . 2) + 3, which is 'sum: 2' + 3 = 0 + 3 = 3."} | неверно верный: «sum: 5» | Парная к verify-клетке про приоритет: 'сумма: 5'. |
T02-L1 1.25 c | Types and comparisons | With strict comparison (===), arrays are considered equal regardless of element order. | «no» Пояснение: With strict comparison (===), arrays are equal only if they have the same key/value pairs in the same order; order matters for === but not for ==.
Raw{"answer": "no", "explanation": "With strict comparison (===), arrays are equal only if they have the same key/value pairs in the same order; order matters for === but not for ==."} | верно | === для массивов требует совпадения и значений, и их порядка. |
T02-L2 1.29 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, not false; strict comparison would use ===.
Raw{"answer": "no", "explanation": "0 == false uses loose comparison (==) and actually returns true, not false; strict comparison would use ===."} | верно | Наоборот: == — нестрогое сравнение и возвращает true; строгое — это === (0 === false → false). |
T02-L3 1.2 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 with == returns false, so "abc" == 0 evaluates to false (this was a change from PHP 7 where it was true).
Raw{"answer": "no", "explanation": "In PHP 8, comparing a non-numeric string to an integer with == returns false, so \"abc\" == 0 evaluates to false (this was a change from PHP 7 where it was true)."} | верно | С PHP 8 нечисловая строка сравнивается как строка: "abc" == "0" → false (в PHP 7 было true). |
T02-L4 0.86 c | Types and comparisons | Under loose comparison, null equals 0, the empty string, and false at the same time. | «yes» Пояснение: In PHP, null == 0, null == "", and null == false all evaluate to true under loose comparison.
Raw{"answer": "yes", "explanation": "In PHP, null == 0, null == \"\", and null == false all evaluate to true under loose comparison."} | верно | null == 0, null == "" и null == false — все true. |
T02-L5 1.02 c | Types and comparisons | What does the expression (int) '42abc' return? | «42» Пояснение: In PHP, casting a string to int reads the leading numeric portion and ignores trailing non-numeric characters, so '42abc' becomes 42.
Raw{"answer": 42, "explanation": "In PHP, casting a string to int reads the leading numeric portion and ignores trailing non-numeric characters, so '42abc' becomes 42."} | верно | Ведущая числовая часть: 42, без ошибок и warning. |
T02-L6 0.86 c | Types and comparisons | What does the expression '5' + 5 return? | «10» Пояснение: In PHP, the + operator coerces the numeric string '5' to the integer 5, then performs addition: 5 + 5 = 10.
Raw{"answer": 10, "explanation": "In PHP, the + operator coerces the numeric string '5' to the integer 5, then performs addition: 5 + 5 = 10."} | верно | Числовая строка приводится: int 10. |
T02-L7 0.86 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".
Raw{"answer": "no", "explanation": "In PHP, casting false to string results in an empty string \"\", not \"0\"."} | верно | false → "", true → "1". |
T02-L8 0.98 c | Types and comparisons | The comparison 0.1 + 0.2 === 0.3 returns false. | «yes» Пояснение: Due to floating-point precision, 0.1 + 0.2 yields 0.30000000000000004, which is not strictly equal (===) to 0.3.
Raw{"answer": "yes", "explanation": "Due to floating-point precision, 0.1 + 0.2 yields 0.30000000000000004, which is not strictly equal (===) to 0.3."} | верно | Двоичная погрешность float: 0.1 + 0.2 = 0.30000000000000004. |
T03-L1 1.47 c | Strings | strrev() correctly reverses a UTF-8 string. | «no» Пояснение: strrev() reverses a string byte-by-byte, which breaks multi-byte UTF-8 characters; you need a multibyte-aware function to correctly reverse UTF-8 strings.
Raw{"answer": "no", "explanation": "strrev() reverses a string byte-by-byte, which breaks multi-byte UTF-8 characters; you need a multibyte-aware function to correctly reverse UTF-8 strings."} | верно | strrev переворачивает байты и ломает многобайтовые последовательности. |
T03-L2 0.76 c | Strings | str_contains('Hello world', 'world') returns true. | «yes» Пояснение: str_contains('Hello world', 'world') returns true because 'world' is indeed a substring of 'Hello world'.
Raw{"answer": "yes", "explanation": "str_contains('Hello world', 'world') returns true because 'world' is indeed a substring of 'Hello world'."} | верно | str_contains с PHP 8.0 проверяет вхождение подстроки. |
T03-L3 0.94 c | Strings | str_pad() can pad a string on the right side only. | «no» Пояснение: str_pad() can pad on the right (default), left (STR_PAD_LEFT), or both sides (STR_PAD_BOTH).
Raw{"answer": "no", "explanation": "str_pad() can pad on the right (default), left (STR_PAD_LEFT), or both sides (STR_PAD_BOTH)."} | верно | STR_PAD_LEFT / STR_PAD_BOTH меняют сторону дополнения. |
T03-L4 1.08 c | Strings | By default trim() strips only spaces, leaving tabs and newlines intact. | «no» Пояснение: By default, trim() strips spaces, tabs, newlines, carriage returns, null bytes, and vertical tabs (" \t\n\r\0\x0B"), not just spaces.
Raw{"answer": "no", "explanation": "By default, trim() strips spaces, tabs, newlines, carriage returns, null bytes, and vertical tabs (\" \\t\\n\\r\\0\\x0B\"), not just spaces."} | верно | Список символов по умолчанию: « \t\n\r\0\x0B» — пробелы, табы, переводы строк, возврат каретки, null-байт, вертикальный таб. Проверено php -r. |
T03-L5 1.07 c | Strings | How many BYTES does strlen('héllo') return for a UTF-8 string? | «6» Пояснение: In UTF-8, 'é' is 2 bytes, while 'h', 'l', 'l', 'o' are each 1 byte, totaling 6 bytes.
Raw{"answer": 6, "explanation": "In UTF-8, 'é' is 2 bytes, while 'h', 'l', 'l', 'o' are each 1 byte, totaling 6 bytes."} | верно | 6 букв по 2 байта: 12. |
T03-L6 0.95 c | Strings | What does substr('abcdef', -3) return? | «def» Пояснение: substr with a negative start position counts from the end of the string, so -3 on 'abcdef' starts at 'd' and returns the remaining substring 'def'.
Raw{"answer": "def", "explanation": "substr with a negative start position counts from the end of the string, so -3 on 'abcdef' starts at 'd' and returns the remaining substring 'def'."} | верно | Отрицательное смещение — с конца: def. |
T03-L7 0.71 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.
Raw{"answer": "no", "explanation": "ucfirst() returns a new string with the first character uppercased; it does not modify the original string in place."} | верно | Строки неизменяемы; ucfirst возвращает новую строку. |
T03-L8 1.24 c | Strings | Variable interpolation works in heredoc but not in nowdoc. | «yes» Пояснение: Heredoc (<<<EOT) supports variable interpolation, while nowdoc (<<<'EOT') with quoted delimiter treats the content as a plain string, so no interpolation occurs.
Raw{"answer": "yes", "explanation": "Heredoc (<<<EOT) supports variable interpolation, while nowdoc (<<<'EOT') with quoted delimiter treats the content as a plain string, so no interpolation occurs."} | верно | Nowdoc — «одинарные кавычки» в тройном синтаксисе: текст как есть. |
T04-L1 1.01 c | Arrays | The sort() function preserves the key-to-value association of the array. | «no» Пояснение: PHP's sort() function reindexes array keys numerically after sorting, so key-to-value associations are not preserved (use asort() for that).
Raw{"answer": "no", "explanation": "PHP's sort() function reindexes array keys numerically after sorting, so key-to-value associations are not preserved (use asort() for that)."} | верно | sort перенумеровывает ключи; связь сохраняет asort. |
T04-L2 0.87 c | Arrays | The string key '5' in an array is stored as the integer 5. | «yes» Пояснение: In PHP, string keys that represent valid integers (like '5') are automatically cast to integer keys when used in arrays.
Raw{"answer": "yes", "explanation": "In PHP, string keys that represent valid integers (like '5') are automatically cast to integer keys when used in arrays."} | верно | Каноничные десятичные строковые ключи приводятся к int. |
T04-L3 1.06 c | Arrays | The in_array() function uses strict comparison (===) by default. | «no» Пояснение: in_array() defaults to loose comparison (==); strict comparison requires explicitly passing true as the third argument.
Raw{"answer": "no", "explanation": "in_array() defaults to loose comparison (==); strict comparison requires explicitly passing true as the third argument."} | верно | По умолчанию сравнение нестрогое; строгое — третий аргумент true. |
T04-L4 1.55 c | Arrays | Without a callback, array_filter() removes all "empty" (falsy) elements from the array. | «yes» Пояснение: Without a callback, array_filter() removes all elements that evaluate to false (i.e., falsy values like 0, '', null, false, '0', and empty arrays).
Raw{"answer": "yes", "explanation": "Without a callback, array_filter() removes all elements that evaluate to false (i.e., falsy values like 0, '', null, false, '0', and empty arrays)."} | верно | Убирает 0, "", null, false и пустые массивы. |
T04-L5 1.38 c | Arrays | By default, array_slice() preserves the original numeric keys of the array. | «no» Пояснение: By default, the $preserve_keys parameter of array_slice() is false, so numeric keys are reindexed starting from 0.
Raw{"answer": "no", "explanation": "By default, the $preserve_keys parameter of array_slice() is false, so numeric keys are reindexed starting from 0."} | верно | По умолчанию ключи перенумеровываются; сохранение — preserve_keys = true. |
T04-L6 1.1 c | Arrays | What does array_slice([10, 20, 30, 40], 1, 2) return? | «[20, 30]» Пояснение: array_slice starts at index 1 (value 20) and takes 2 elements, returning [20, 30].
Raw{"answer": "[20, 30]", "explanation": "array_slice starts at index 1 (value 20) and takes 2 elements, returning [20, 30]."} | верно | [20,30]; ключи перенумеровываются. |
T04-L7 1.14 c | Arrays | How many elements will count(['a' => 1] + ['a' => 9, 'b' => 2]) return? | «2» Пояснение: The + operator keeps left-hand values for duplicate string keys, so the result is ['a' => 1, 'b' => 2], which has 2 elements.
Raw{"answer": 2, "explanation": "The + operator keeps left-hand values for duplicate string keys, so the result is ['a' => 1, 'b' => 2], which has 2 elements."} | верно | Оператор + : по ключу 'a' побеждает левый; итого 2. |
T04-L8 1.72 c | Arrays | Since PHP 8.1, the spread operator [...$a, ...$b] supports arrays with string keys. | «yes» Пояснение: PHP 8.1 introduced support for the spread operator with arrays that have string keys; previously it only worked with integer keys.
Raw{"answer": "yes", "explanation": "PHP 8.1 introduced support for the spread operator with arrays that have string keys; previously it only worked with integer keys."} | верно | В 8.0 — только числовые ключи; 8.1 снял ограничение. |
T05-L1 3.19 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 combined in the same function call, e.g. foo(a: 1, ...$args).
Raw{"answer": "no", "explanation": "In PHP 8.0+, named arguments and argument unpacking (...$args) can be combined in the same function call, e.g. foo(a: 1, ...$args)."} | верно | Можно: f(...$args, имя: значение). Нельзя только позиционный аргумент после распаковки. |
T05-L2 4.35 c | Functions and closures | An anonymous function without use sees variables from the outer scope. | «no» Пояснение: In PHP, an anonymous function (closure) without the 'use' keyword does not automatically have access to variables from the enclosing scope; you must explicitly import them with 'use'.
Raw{"answer": "no", "explanation": "In PHP, an anonymous function (closure) without the 'use' keyword does not automatically have access to variables from the enclosing scope; you must explicitly import them with 'use'."} | верно | Без use внешние переменные недоступны; авто-захват только у fn. |
T05-L3 0.87 c | Functions and closures | What will func_num_args() return inside function f($a) { return func_num_args(); } when called as f(1, 2, 3)? | «3» Пояснение: func_num_args() returns the total number of arguments actually passed to the function call, which is 3 (1, 2, 3), regardless of how many are declared in the signature.
Raw{"answer": 3, "explanation": "func_num_args() returns the total number of arguments actually passed to the function call, which is 3 (1, 2, 3), regardless of how many are declared in the signature."} | верно | Считает переданные аргументы: 3. |
T05-L4 2.4 c | Functions and closures | The body of an arrow function fn may consist of several expressions in curly braces. | «no» Пояснение: An arrow function (fn) body must be a single expression after '=>', not multiple expressions in curly braces; that is the syntax of a regular anonymous function (closure).
Raw{"answer": "no", "explanation": "An arrow function (fn) body must be a single expression after '=>', not multiple expressions in curly braces; that is the syntax of a regular anonymous function (closure)."} | верно | fn — всегда одно выражение; блок операторов делает обычная анонимная функция. |
T05-L5 4.61 c | Functions and closures | An arrow function fn captures outer variables by reference (lazily, at use time). | «no» Пояснение: PHP arrow functions (fn) automatically capture surrounding variables by value at creation time, not by reference; reference capture requires an explicit closure with use (&$var).
Raw{"answer": "no", "explanation": "PHP arrow functions (fn) automatically capture surrounding variables by value at creation time, not by reference; reference capture requires an explicit closure with use (&$var)."} | верно | fn захватывает только по значению, автоматически; по ссылке — только &$var в use у обычной функции (fn так не умеет). |
T05-L6 0.86 c | Functions and closures | A closure declared as static function () {} does not capture $this. | «yes» Пояснение: In PHP, declaring a closure with the 'static' keyword prevents it from implicitly capturing $this from the enclosing scope.
Raw{"answer": "yes", "explanation": "In PHP, declaring a closure with the 'static' keyword prevents it from implicitly capturing $this from the enclosing scope."} | верно | static-замыкание отвязано от объекта: $this внутри недоступен. |
T05-L7 1.28 c | Functions and closures | What will this print: $x = 5; $f = function () use ($x) { return $x; }; $x = 7; echo $f(); | «5» Пояснение: The 'use ($x)' captures $x by value (not by reference), so the closure retains the original value of 5 regardless of the later reassignment to 7.
Raw{"answer": 5, "explanation": "The 'use ($x)' captures $x by value (not by reference), so the closure retains the original value of 5 regardless of the later reassignment to 7."} | верно | use захватывает по значению в момент создания: 5. |
T05-L8 0.97 c | Functions and closures | In weak typing mode (without strict_types), passing the string "5" to an int parameter is allowed. | «yes» Пояснение: In weak typing mode (the default), PHP will coerce the numeric string "5" to the integer 5 when it is passed to an int-typed parameter.
Raw{"answer": "yes", "explanation": "In weak typing mode (the default), PHP will coerce the numeric string \"5\" to the integer 5 when it is passed to an int-typed parameter."} | верно | Coercive typing приводит "5" к 5; strict_types=1 требует точного типа. |
T06-L1 0.9 c | OOP: classes and inheritance | PHP supports constructor property promotion: public function __construct(private int $x) {}. | «yes» Пояснение: Constructor property promotion was introduced in PHP 8.0, allowing visibility modifiers on constructor parameters to auto-declare and assign properties.
Raw{"answer": "yes", "explanation": "Constructor property promotion was introduced in PHP 8.0, allowing visibility modifiers on constructor parameters to auto-declare and assign properties."} | верно | С PHP 8.0 параметр с модификатором создаёт свойство и присваивание. |
T06-L2 0.57 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 subclasses from overriding that method.
Raw{"answer": "final", "explanation": "In PHP, the 'final' keyword before a method declaration prevents subclasses from overriding that method."} | верно | final. |
T06-L3 0.77 c | OOP: classes and inheritance | A method declared final cannot be overridden in a subclass. | «yes» Пояснение: In PHP, a method declared with the final keyword cannot be overridden in a subclass; attempting to do so results in a fatal error.
Raw{"answer": "yes", "explanation": "In PHP, a method declared with the final keyword cannot be overridden in a subclass; attempting to do so results in a fatal error."} | верно | final запрещает переопределение метода и наследование класса. |
T06-L4 0.82 c | OOP: classes and inheritance | Parent properties with private visibility are accessible in a subclass. | «no» Пояснение: In PHP, private properties are accessible only within the class that declares them, not in subclasses; protected visibility is needed for subclass access.
Raw{"answer": "no", "explanation": "In PHP, private properties are accessible only within the class that declares them, not in subclasses; protected visibility is needed for subclass access."} | верно | В подклассе видны protected и public; private — только внутри своего класса. |
T06-L5 3.1 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, an anonymous class gets a generated name like 'class@anonymous' followed by a NUL byte and additional identifier; the part before the NUL byte is 'class@anonymous'.
Raw{"answer": "class@anonymous", "explanation": "In PHP, an anonymous class gets a generated name like 'class@anonymous' followed by a NUL byte and additional identifier; the part before the NUL byte is 'class@anonymous'."} | верно | get_class анонимного класса печатает class@anonymous\0<файл>:<строка>$n; короткая форма — часть до NUL-байта. Проверено php -r (hex). |
T06-L6 1.6 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 hidden from child classes, so a child can freely redeclare a method with the same name and any visibility without violating the inheritance contract.
Raw{"answer": "yes", "explanation": "In PHP, private methods are hidden from child classes, so a child can freely redeclare a method with the same name and any visibility without violating the inheritance contract."} | верно | private-члены не наследуются — правила совместимости подписей не действуют. |
T06-L7 1.52 c | OOP: classes and inheritance | The magic method __get() is called only for non-existent properties. | «no» Пояснение: __get() is called not only for non-existent properties but also for inaccessible (protected or private) properties accessed from outside the class.
Raw{"answer": "no", "explanation": "__get() is called not only for non-existent properties but also for inaccessible (protected or private) properties accessed from outside the class."} | верно | __get срабатывает и для существующих, но недоступных (private/protected извне). |
T06-L8 0.99 c | OOP: classes and inheritance | What does reassigning a readonly property throw — Exception or Error? | «error» Пояснение: Reassigning a readonly property in PHP throws a \readonlyproperty, which is a subclass of \Error, not \Exception.
Raw{"answer": "Error", "explanation": "Reassigning a readonly property in PHP throws a \\readonlyproperty, which is a subclass of \\Error, not \\Exception."} | верно | Error (readonly с 8.1); оговорка: в __clone() переинициализация допустима (8.3+). |
T07-L1 0.67 c | Interfaces, traits, enum | An interface can declare constants. | «yes» Пояснение: PHP interfaces can declare constants, which are implicitly public and final.
Raw{"answer": "yes", "explanation": "PHP interfaces can declare constants, which are implicitly public and final."} | верно | Константы интерфейса наследуются реализациями. |
T07-L2 0.88 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 implements a specific interface.
Raw{"answer": "instanceof", "explanation": "The instanceof operator in PHP checks whether an object is an instance of a specific class or implements a specific interface."} | верно | instanceof. |
T07-L3 1.66 c | Interfaces, traits, enum | An interface can declare static methods. | «yes» Пояснение: In PHP, an interface can declare static methods, and the implementing class must provide the corresponding static method implementation.
Raw{"answer": "yes", "explanation": "In PHP, an interface can declare static methods, and the implementing class must provide the corresponding static method implementation."} | верно | Реализация обязана дать статический метод с той же сигнатурой. |
T07-L4 1.03 c | Interfaces, traits, enum | The instanceof operator only checks class inheritance: it ignores interfaces. | «no» Пояснение: PHP's instanceof operator checks both class inheritance and implemented interfaces, so it returns true if the object's class implements the given interface.
Raw{"answer": "no", "explanation": "PHP's instanceof operator checks both class inheritance and implemented interfaces, so it returns true if the object's class implements the given interface."} | верно | instanceof возвращает true и для интерфейсов объекта. |
T07-L5 2.51 c | Interfaces, traits, enum | An interface method may have a default implementation, like a trait method. | «no» Пояснение: In PHP, interface methods are declarations only and cannot have a body or default implementation, whereas trait methods can provide full implementations.
Raw{"answer": "no", "explanation": "In PHP, interface methods are declarations only and cannot have a body or default implementation, whereas trait methods can provide full implementations."} | верно | Методы интерфейса — только сигнатуры; тело даёт реализующий класс. |
T07-L6 1.31 c | Interfaces, traits, enum | An abstract method in an abstract class may have protected visibility. | «yes» Пояснение: In PHP, abstract methods in an abstract class can have public, protected, or (since PHP 7.1) private visibility; protected is a common and valid choice.
Raw{"answer": "yes", "explanation": "In PHP, abstract methods in an abstract class can have public, protected, or (since PHP 7.1) private visibility; protected is a common and valid choice."} | верно | В абстрактном классе — любая видимость; в интерфейсе — только public. |
T07-L7 0.91 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 of all defined cases, and there are exactly 3 cases: A, B, and C.
Raw{"answer": 3, "explanation": "Foo::cases() returns an array of all defined cases, and there are exactly 3 cases: A, B, and C."} | верно | Статический метод cases(): 3. |
T07-L8 1.0 c | Interfaces, traits, enum | A trait can declare constants. | «yes» Пояснение: PHP traits can declare constants, which are then accessible through any class that uses the trait.
Raw{"answer": "yes", "explanation": "PHP traits can declare constants, which are then accessible through any class that uses the trait."} | верно | С PHP 8.2 трейты могут объявлять константы (RFC constants_in_traits); до 8.2 — нет. |
T08-L1 0.96 c | Exceptions and errors | The Throwable interface is a common ancestor of both Exception and Error. | «yes» Пояснение: In PHP 7+, both the Exception class and the Error class implement the Throwable interface, making it their common ancestor.
Raw{"answer": "yes", "explanation": "In PHP 7+, both the Exception class and the Error class implement the Throwable interface, making it their common ancestor."} | верно | Иерархия с PHP 7: Throwable → Exception и Throwable → Error. |
T08-L2 1.24 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 classes that implement Throwable, so catch(Exception) does not catch TypeError.
Raw{"answer": "no", "explanation": "TypeError extends Error (not Exception); both Exception and Error are separate classes that implement Throwable, so catch(Exception) does not catch TypeError."} | верно | TypeError наследуется от Error; catch (Exception) его не ловит. |
T08-L3 1.89 c | Exceptions and errors | The @ operator suppresses exceptions too. | «no» Пояснение: The @ operator suppresses error reporting (warnings, notices, etc.) but does not prevent exceptions from being thrown or propagating.
Raw{"answer": "no", "explanation": "The @ operator suppresses error reporting (warnings, notices, etc.) but does not prevent exceptions from being thrown or propagating."} | верно | @ глушит диагностику (warnings/notices), исключения не перехватывает. |
T08-L4 0.79 c | Exceptions and errors | What error class does intdiv(5, 0) throw? | «divisionbyzeroerror» Пояснение: In PHP, intdiv(5, 0) throws a DivisionByZeroError, which is a built-in exception class extending ArithmeticError.
Raw{"answer": "DivisionByZeroError", "explanation": "In PHP, intdiv(5, 0) throws a DivisionByZeroError, which is a built-in exception class extending ArithmeticError."} | верно | DivisionByZeroError (иерархия Error, не Exception); php-грейдер объективен. |
T08-L5 1.11 c | Exceptions and errors | The finally block runs only if the exception was caught by a catch block. | «no» Пояснение: The finally block in PHP executes regardless of whether an exception was thrown or caught; it runs even when the try block completes normally without any exception.
Raw{"answer": "no", "explanation": "The finally block in PHP executes regardless of whether an exception was thrown or caught; it runs even when the try block completes normally without any exception."} | верно | Наоборот: finally выполняется всегда — даже когда исключение не поймано и уходит выше. Проверено php -r. |
T08-L6 2.61 c | Exceptions and errors | An exception thrown inside a finally block has no effect on the result of the try block. | «no» Пояснение: An exception thrown in a finally block replaces (masks) any exception from the try block or, if the try block completed normally, becomes the propagated exception, so it does affect the outcome.
Raw{"answer": "no", "explanation": "An exception thrown in a finally block replaces (masks) any exception from the try block or, if the try block completed normally, becomes the propagated exception, so it does affect the outcome."} | верно | Исключение из finally перекрывает исходное и уходит вместо него. |
T08-L7 1.96 c | Exceptions and errors | What does the expression (bool) new Exception('x') return? | «yes» Пояснение: In PHP, casting any object to bool returns true unless the class defines a __bool__() magic method; Exception does not, so (bool) new Exception('x') is true.
Raw{"answer": "yes", "explanation": "In PHP, casting any object to bool returns true unless the class defines a __bool__() magic method; Exception does not, so (bool) new Exception('x') is true."} | верно | Любой объект при приведении к bool — true. Формы ответа: true или да. |
T08-L8 1.17 c | Exceptions and errors | Functions registered via register_shutdown_function() run when exit is called. | «yes» Пояснение: Shutdown functions registered with register_shutdown_function() are executed when the script terminates, including when exit/die is called.
Raw{"answer": "yes", "explanation": "Shutdown functions registered with register_shutdown_function() are executed when the script terminates, including when exit/die is called."} | верно | exit завершает скрипт, но shutdown-функции отрабатывают. |
T09-L1 1.42 c | Namespaces and autoloading | The use App\Service\Mailer; statement itself loads the class file. | «no» Пояснение: The use statement is a compile-time aliasing directive that only maps a shorter name to a fully qualified class name; the class file is actually loaded later (e.g., via the autoloader) when the class is first instantiated or referenced at runtime.
Raw{"answer": "no", "explanation": "The use statement is a compile-time aliasing directive that only maps a shorter name to a fully qualified class name; the class file is actually loaded later (e.g., via the autoloader) when the class is first instantiated or referenced at runtime."} | верно | use — псевдоним на этапе компиляции; файл грузит автозагрузчик при первом обращении. |
T09-L2 0.87 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 the syntax 'use function Namespace\functionName;', while 'use const' is for importing constants.
Raw{"answer": "function", "explanation": "In PHP, to import a function you use the syntax 'use function Namespace\\functionName;', while 'use const' is for importing constants."} | верно | use function ...; (и use const для констант). |
T09-L3 2.11 c | Namespaces and autoloading | Into which file (path from src/) does the PSR-4 mapping "App\ → src/" place the class App\Controller\Api\UserController? | «src/controller/api/usercontroller.php» Пояснение: PSR-4 strips the 'App\' prefix, converts the remaining namespace separators to directory slashes, and appends .php to get the file path under the src/ base directory.
Raw{"answer": "src/Controller/Api/UserController.php", "explanation": "PSR-4 strips the 'App\\' prefix, converts the remaining namespace separators to directory slashes, and appends .php to get the file path under the src/ base directory."} | верно | Остаток имени после префикса, \ → /. |
T09-L4 1.21 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 autoloader class with PHP's SPL autoloading mechanism.
Raw{"answer": "yes", "explanation": "Composer's vendor/autoload.php ultimately calls spl_autoload_register() to register its autoloader class with PHP's SPL autoloading mechanism."} | верно | Composer ставит автозагрузчик именно на spl_autoload_register. |
T09-L5 0.72 c | Namespaces and autoloading | The magic constant __NAMESPACE__ contains the name of the current namespace. | «yes» Пояснение: __NAMESPACE__ is a PHP magic constant that returns the name of the current namespace (or an empty string in the global namespace).
Raw{"answer": "yes", "explanation": "__NAMESPACE__ is a PHP magic constant that returns the name of the current namespace (or an empty string in the global namespace)."} | верно | В корневом пространстве — пустая строка. |
T09-L6 1.44 c | Namespaces and autoloading | An unqualified class name (without a leading \) in new is resolved from the global root. | «no» Пояснение: An unqualified class name in a new expression is resolved relative to the current namespace, not the global root; only a leading backslash forces resolution from the global root.
Raw{"answer": "no", "explanation": "An unqualified class name in a new expression is resolved relative to the current namespace, not the global root; only a leading backslash forces resolution from the global root."} | верно | Резолвится относительно текущего namespace (с учётом импортов). |
T09-L7 1.35 c | Namespaces and autoloading | With the PSR-4 mapping "App\ → src/", the class App\Model\User lives in the file src/Model/User.php. | «yes» Пояснение: PSR-4 strips the prefix 'App\' and maps the remaining namespace segments 'Model\User' to the path 'Model/User.php' under the base directory 'src/', giving 'src/Model/User.php'.
Raw{"answer": "yes", "explanation": "PSR-4 strips the prefix 'App\\' and maps the remaining namespace segments 'Model\\User' to the path 'Model/User.php' under the base directory 'src/', giving '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 statement inside a function body, and the alias applies only within that function's scope.
Raw{"answer": "yes", "explanation": "PHP allows a use statement inside a function body, and the alias applies only within that function's scope."} | неверно верный: «no» | use внутри тела функции — parse error; импорты файловые и компиляционные. |
T10-L1 1.53 c | References and scope | Arrays are copied on assignment rather than passed by reference. | «yes» Пояснение: In PHP, arrays are value types; assignment and function parameters create a copy (via copy-on-write) unless the reference operator & is explicitly used.
Raw{"answer": "yes", "explanation": "In PHP, arrays are value types; assignment and function parameters create a copy (via copy-on-write) unless the reference operator & is explicitly used."} | верно | Присваивание массива — копия (в движке — copy-on-write). |
T10-L2 1.18 c | References and scope | What will this print: $a = [1, 2]; $b = $a; $b[] = 3; echo count($a); | «2» Пояснение: PHP arrays use copy-on-value assignment, so appending to $b does not modify $a; count($a) remains 2.
Raw{"answer": 2, "explanation": "PHP arrays use copy-on-value assignment, so appending to $b does not modify $a; count($a) remains 2."} | верно | Присваивание — копия: в $a по-прежнему 2 элемента. |
T10-L3 1.13 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 have function scope by default, so global variables must be accessed via the `global` keyword, the `$GLOBALS` superglobal, or by being passed as parameters.
Raw{"answer": "yes", "explanation": "In PHP, variables have function scope by default, so global variables must be accessed via the `global` keyword, the `$GLOBALS` superglobal, or by being passed as parameters."} | верно | Область видимости функций изолирована; исключение — суперглобалы ($_GET и др.). |
T10-L4 1.37 c | References and scope | unset($GLOBALS['x']) inside a function removes the global variable only for that function. | «no» Пояснение: unset($GLOBALS['x']) removes the variable from the global scope entirely; it is not limited to the current function.
Raw{"answer": "no", "explanation": "unset($GLOBALS['x']) removes the variable from the global scope entirely; it is not limited to the current function."} | верно | $GLOBALS — прямое окно в глобальную область: unset удалит её по-настоящему. |
T10-L5 0.96 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 becomes 6 after the call.
Raw{"answer": 6, "explanation": "The function increments $x by reference, so $n becomes 6 after the call."} | верно | Ссылка меняет оригинал: 6. |
T10-L6 5.22 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 5+, foreach by value does not make a separate copy of the array; it uses the array's internal structure directly, so modifications (unset, assignment, adding elements) made inside the loop are immediately visible to the ongoing iteration.
Raw{"answer": "yes", "explanation": "In PHP 5+, foreach by value does not make a separate copy of the array; it uses the array's internal structure directly, so modifications (unset, assignment, adding elements) made inside the loop are immediately visible to the ongoing iteration."} | неверно верный: «no» | По значению foreach итерирует копию-снимок. |
T10-L7 1.04 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.29 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 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 a bool."} | верно | Булев ключ приводится к int: true → 1, false → 0. |
T11-L1 1.91 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, and it is retrievable via the Generator::getReturn() method after the generator is exhausted.
Raw{"answer": "yes", "explanation": "Since PHP 7.0, a generator can return a value, and it is retrievable via the Generator::getReturn() method after the generator is exhausted."} | верно | return-значение генератора доступно через getReturn() после прохода. |
T11-L2 2.17 c | Generators, iterators, SPL | A fully consumed generator can be rewound with rewind() and traversed again. | «no» Пояснение: Generators in PHP are one-time iterators; once fully consumed, rewind() cannot restart them—you must invoke the generator function again to get a fresh instance.
Raw{"answer": "no", "explanation": "Generators in PHP are one-time iterators; once fully consumed, rewind() cannot restart them—you must invoke the generator function again to get a fresh instance."} | верно | Генератор одноразовый: rewind после начала итерации бросает Exception. |
T11-L3 1.11 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 Traversable, yielding its values as if they were produced by the current generator.
Raw{"answer": "yes", "explanation": "In PHP, yield from delegates iteration to another generator or Traversable, yielding its values as if they were produced by the current generator."} | верно | yield from проксирует значения, ключи и return-значение внутреннего генератора. |
T11-L4 1.24 c | Generators, iterators, SPL | What does get_class(g()) return for function g() { yield 1; }? | «generator» Пояснение: Calling a generator function returns an instance of the Generator class, so get_class() returns the string 'Generator'.
Raw{"answer": "Generator", "explanation": "Calling a generator function returns an instance of the Generator class, so get_class() returns the string 'Generator'."} | верно | Функция с yield возвращает Generator. |
T11-L5 1.1 c | Generators, iterators, SPL | How many elements will count(iterator_to_array((function () { yield from [1, 2, 3]; })())) return? | «3» Пояснение: The generator yields 3 elements (1, 2, 3), iterator_to_array converts it to an array of 3 elements, and count returns 3.
Raw{"answer": 3, "explanation": "The generator yields 3 elements (1, 2, 3), iterator_to_array converts it to an array of 3 elements, and count returns 3."} | верно | yield from делегирует все 3 элемента. |
T11-L6 0.84 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 one that implements FIFO.
Raw{"answer": "no", "explanation": "SplStack implements a LIFO (Last In, First Out) stack, not a FIFO queue; SplQueue is the one that implements FIFO."} | верно | SplStack — стек LIFO; очередь FIFO — SplQueue. |
T11-L7 0.78 c | Generators, iterators, SPL | ArrayIterator allows wrapping an array and traversing it via the Iterator interface. | «yes» Пояснение: ArrayIterator is a built-in PHP class that wraps an array and implements the Iterator interface, allowing traversal via methods like current(), next(), key(), valid(), and rewind().
Raw{"answer": "yes", "explanation": "ArrayIterator is a built-in PHP class that wraps an array and implements the Iterator interface, allowing traversal via methods like current(), next(), key(), valid(), and rewind()."} | верно | Объектная обёртка над массивом. |
T11-L8 1.21 c | Generators, iterators, SPL | An ArrayObject instance cannot be traversed with foreach. | «no» Пояснение: ArrayObject implements the Iterator interface, so it can be traversed with foreach.
Raw{"answer": "no", "explanation": "ArrayObject implements the Iterator interface, so it can be traversed with foreach."} | верно | ArrayObject реализует IteratorAggregate — foreach по нему работает. |
T12-L1 1.49 c | Configuration and security | password_hash() generates a salt automatically — passing one separately is not needed. | «yes» Пояснение: password_hash() automatically generates a random salt internally and embeds it in the resulting hash string; there is no separate salt parameter to pass.
Raw{"answer": "yes", "explanation": "password_hash() automatically generates a random salt internally and embeds it in the resulting hash string; there is no separate salt parameter to pass."} | верно | Соль встраивается в строку результата; параметр salt устарел. |
T12-L2 2.21 c | Configuration and security | In PHP 8, PASSWORD_DEFAULT is md5 with an automatically added salt. | «no» Пояснение: In PHP 8, PASSWORD_DEFAULT is PASSWORD_BCRYPT, not MD5 with a salt.
Raw{"answer": "no", "explanation": "In PHP 8, PASSWORD_DEFAULT is PASSWORD_BCRYPT, not MD5 with a salt."} | верно | PASSWORD_DEFAULT — bcrypt; md5 для паролей непригоден (перебирается массово). |
T12-L3 0.92 c | Configuration and security | What does password_verify('secret', password_hash('secret', PASSWORD_DEFAULT)) return? | «yes» Пояснение: password_verify() returns true when the plaintext password matches the given hash, which it does here since both use 'secret'.
Raw{"answer": "yes", "explanation": "password_verify() returns true when the plaintext password matches the given hash, which it does here since both use 'secret'."} | верно | Соль и хеш в одной строке: true (форма ответа: true или да). |
T12-L4 1.3 c | Configuration and security | strip_tags() protects against SQL injection. | «no» Пояснение: strip_tags() only removes HTML and PHP tags from a string; SQL injection is prevented by prepared statements or proper escaping of SQL special characters, not by stripping HTML tags.
Raw{"answer": "no", "explanation": "strip_tags() only removes HTML and PHP tags from a string; SQL injection is prevented by prepared statements or proper escaping of SQL special characters, not by stripping HTML tags."} | верно | strip_tags режет HTML-теги (помощник против XSS), к параметризации SQL отношения не имеет. |
T12-L5 1.32 c | Configuration and security | session_regenerate_id() is used to protect against session fixation upon user login. | «yes» Пояснение: session_regenerate_id() replaces the current session ID with a new one, which invalidates any previously known session ID an attacker may have set, thereby preventing session fixation attacks (commonly applied at login).
Raw{"answer": "yes", "explanation": "session_regenerate_id() replaces the current session ID with a new one, which invalidates any previously known session ID an attacker may have set, thereby preventing session fixation attacks (commonly applied at login)."} | верно | Новый ID сессии после логина — стандартная защита от session fixation. |
T12-L6 0.77 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 (Server API) interface, such as 'cli', 'apache2', or 'fpm-fcgi'.
Raw{"answer": "php_sapi_name()", "explanation": "The built-in function php_sapi_name() returns the name of the current SAPI (Server API) interface, such as 'cli', 'apache2', or 'fpm-fcgi'."} | верно | php_sapi_name(). |
T12-L7 1.55 c | Configuration and security | session_destroy() deletes session data on the server but not the cookie in the user's browser. | «yes» Пояснение: session_destroy() removes the session data stored on the server, but the session cookie in the browser must be explicitly deleted (e.g., via setcookie with a past expiration) to be removed.
Raw{"answer": "yes", "explanation": "session_destroy() removes the session data stored on the server, but the session cookie in the browser must be explicitly deleted (e.g., via setcookie with a past expiration) to be removed."} | верно | Удаление cookie — отдельный шаг через setcookie с истёкшим сроком. |
T12-L8 0.98 c | Configuration and security | Without calling session_start(), the $_SESSION array is automatically populated with session data. | «no» Пояснение: The $_SESSION array is only populated with session data after session_start() is called; without it, it remains empty.
Raw{"answer": "no", "explanation": "The $_SESSION array is only populated with session data after session_start() is called; without it, it remains empty."} | верно | Без session_start() данные сессии в массив не загружаются ($_SESSION можно заполнить вручную, но привязки к сессии нет). |
VC-L1 4.52 c | PHP 8.4–8.5 | In which PHP version was the array_find() function introduced? | «no» Пояснение: array_find() is not a built-in PHP function; PHP provides array_filter(), array_search(), and array_map() instead.
Raw{"answer": "no", "explanation": "array_find() is not a built-in PHP function; PHP provides array_filter(), array_search(), and array_map() instead."} | неверно верный: «8.4» | PHP 8.4 (RFC array_find). |
VC-L2 1.52 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 declared directly within a property definition.
Raw{"answer": "yes", "explanation": "PHP 8.4 introduced property hooks, allowing custom get/set logic to be declared directly within a property definition."} | верно | Property hooks — PHP 8.4 (ноябрь 2024). |
VC-L3 2.23 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 4.74 c | PHP 8.4–8.5 | In which PHP version was the #[\NoDiscard] attribute introduced? Answer with the version number. | «8.4» Пояснение: The #[\NoDiscard] attribute was introduced in PHP 8.4 to allow marking function return values as required to be used.
Raw{"answer": "8.4", "explanation": "The #[\\NoDiscard] attribute was introduced in PHP 8.4 to allow marking function return values as required to be used."} | неверно верный: «8.5» | #[\NoDiscard] — PHP 8.5 (marking return values as important). |
VC-L5 5.92 c | PHP 8.4–8.5 | In which PHP version did the pipe operator |> first appear? Answer with the version number. | «no» Пояснение: PHP has never introduced a |> pipe operator; it has | (bitwise OR) and || (logical OR) but no pipe operator as of any released version.
Raw{"answer": "no", "explanation": "PHP has never introduced a |> pipe operator; it has | (bitwise OR) and || (logical OR) but no pipe operator as of any released version."} | неверно верный: «8.5» | Pipe operator — PHP 8.5 (2025). |
VC-L6 6.32 c | PHP 8.4–8.5 | In which PHP version did clone-with — the syntax clone($obj, ['x' => 1]) — appear? Answer with the version number. | «no» Пояснение: The clone-with syntax clone($obj, ['x' => 1]) has not appeared in any released PHP version; the standard syntax remains clone $obj with no second argument for property overrides.
Raw{"answer": "no", "explanation": "The clone-with syntax clone($obj, ['x' => 1]) has not appeared in any released PHP version; the standard syntax remains clone $obj with no second argument for property overrides."} | неверно верный: «8.5» | Clone with v2 — PHP 8.5. |
VC-L7 1.73 c | PHP 8.4–8.5 | In which PHP version were the array_first() and array_last() functions introduced? | «8.4» Пояснение: The array_first() and array_last() functions were introduced in PHP 8.4 as part of a new set of high-level array functions.
Raw{"answer": "8.4", "explanation": "The array_first() and array_last() functions were introduced in PHP 8.4 as part of a new set of high-level array functions."} | неверно верный: «8.5» | PHP 8.5. |
VC-L8 2.01 c | PHP 8.4–8.5 | For which PHP version was RFC Partial Function Application v2 adopted (as of 2026-11-07)? Answer with the version number. | «9.0» Пояснение: The RFC Partial Function Application v2 was adopted for PHP 9.0.
Raw{"answer": 9.0, "explanation": "The RFC Partial Function Application v2 was adopted for PHP 9.0."} | неверно верный: «8.6» | PFA v2 принят 05.12.2025 (33-0-0), реализован в PHP 8.6. |
VF-L1 1.13 c | PHP: 8.6+ and the future | For which PHP version was the RFC clamp_v2 (the clamp() function) implemented, as of 2026-11-07? Answer with the version number. | «8.4» Пояснение: The clamp() function was introduced in PHP 8.4 as part of the RFC clamp_v2, released in November 2024.
Raw{"answer": "8.4", "explanation": "The clamp() function was introduced in PHP 8.4 as part of the RFC clamp_v2, released in November 2024."} | неверно верный: «8.6» | По данным владельца (wiki.php.net/rfc): clamp_v2 — 8.6; clamp() в 8.5.11 отсутствует (косвенное подтверждение). Дата-якорь делает клетку монотонной. |
VF-L2 5.53 c | PHP: 8.6+ and the future | RFC Context Managers v2 has already been adopted in PHP (as of 2026-11-07). | «no» Пояснение: There is no widely recognized 'Context Managers v2' RFC that has been adopted into PHP; the feature does not appear in any released PHP version up to the stated date.
Raw{"answer": "no", "explanation": "There is no widely recognized 'Context Managers v2' RFC that has been adopted into PHP; the feature does not appear in any released PHP version up to the stated date."} | верно | На 06.11.2026 — в обсуждении (создан 2026-10-23); не принят. |
VF-L3 4.12 c | PHP: 8.6+ and the future | RFC Bound-Erased Generic Types (generics) was declined in 2026. | «yes» Пояснение: The RFC for Bound-Erased Generic Types (generics) in PHP was voted down/declined in 2026, continuing PHP's pattern of rejecting full generics proposals.
Raw{"answer": "yes", "explanation": "The RFC for Bound-Erased Generic Types (generics) in PHP was voted down/declined in 2026, continuing PHP's pattern of rejecting full generics proposals."} | верно | Голосование завершилось 2026-06-28: отклонён (wiki.php.net/rfc). |
VF-L4 2.44 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 the given date, no RFC has been accepted to make the Zend Thread-Safe (ZTS) multithreading build the default in PHP; NTS remains the default build variant.
Raw{"answer": "no", "explanation": "As of the given date, no RFC has been accepted to make the Zend Thread-Safe (ZTS) multithreading build the default in PHP; NTS remains the default build variant."} | верно | Такого принятого RFC нет на дату якоря; якорь делает клетку монотонной — при принятии RFC позже клетка не перевернётся. |
VF-L5 2.13 c | PHP: 8.6+ and the future | As of PHP 8.5, generics (parameterized types) are still absent. | «yes» Пояснение: PHP 8.5 still does not include native generics (parameterized types); no such feature has been adopted in any PHP release up to and including 8.5.
Raw{"answer": "yes", "explanation": "PHP 8.5 still does not include native generics (parameterized types); no such feature has been adopted in any PHP release up to and including 8.5."} | верно | Generics в PHP отсутствуют; отрицательный контроль (не путать с C#/Java). |
VF-L6 3.3 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 releases new major versions in November; 8.5 was released in November 2025, so as of 2026-11-07 it is still the latest stable, with 8.6 GA scheduled for 2026-11-19.
Raw{"answer": "yes", "explanation": "PHP releases new major versions in November; 8.5 was released in November 2025, so as of 2026-11-07 it is still the latest stable, with 8.6 GA scheduled for 2026-11-19."} | верно | 8.5 — релиз осени 2025; 8.6 GA 19.11.2026 (wiki.php.net/todo/php86). Дата снимка — 06.11.2026. |
VF-L7 1.47 c | PHP: 8.6+ and the future | The PHP 6 branch never shipped: after PHP 5.6 came PHP 7.0 directly. | «yes» Пояснение: PHP 6 was a planned major revision that never reached a stable release; PHP 7.0 (December 2015) was the next major version after PHP 5.6.
Raw{"answer": "yes", "explanation": "PHP 6 was a planned major revision that never reached a stable release; PHP 7.0 (December 2015) was the next major version after PHP 5.6."} | верно | Исторический факт: ветка 6 не была релизнута. |
VF-L8 2.63 c | PHP: 8.6+ and the future | The RFC adding the #[\Deprecated] attribute to the core was adopted. | «no» Пояснение: The RFC proposing a #[\Deprecated] attribute was not accepted into PHP core; it did not reach the required approval threshold.
Raw{"answer": "no", "explanation": "The RFC proposing a #[\\Deprecated] attribute was not accepted into PHP core; it did not reach the required approval threshold."} | неверно верный: «yes» | #[\Deprecated] — принят, реализован в PHP 8.4. |
T25-L1 1.14 c | Clean architecture | The dependency rule of clean and onion architecture: inner layers know nothing about outer ones — dependencies point toward the center. | «yes» Пояснение: In clean and onion architecture, the dependency rule mandates that inner (domain) layers must not depend on outer layers; all dependencies point inward toward the core.
Raw{"answer": "yes", "explanation": "In clean and onion architecture, the dependency rule mandates that inner (domain) layers must not depend on outer layers; all dependencies point inward toward the core."} | верно | Чистая (Robert C. Martin), луковичная (Jeffrey Palermo) и гексагональная (ports & adapters) — варианты одной идеи: зависимости направлены внутрь, к домену. Слоями в проекте следит deptrac. |
T25-L2 1.46 c | Clean architecture | Domain entities import neither Doctrine nor Symfony — only the language and, possibly, the standard library. | «yes» Пояснение: In clean/layered PHP architecture, domain entities should be pure PHP objects that depend only on the language and standard library, not on framework or ORM libraries like Doctrine or Symfony.
Raw{"answer": "yes", "explanation": "In clean/layered PHP architecture, domain entities should be pure PHP objects that depend only on the language and standard library, not on framework or ORM libraries like Doctrine or Symfony."} | верно | Изоляция домена от инфраструктуры; deptrac в проекте как раз следит за слоями. |
T25-L3 1.32 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; they call use cases, but the business-logic layer is the use cases/services themselves, not the components that invoke them.
Raw{"answer": "no", "explanation": "Controllers and Twig templates belong to the presentation (interface) layer; they call use cases, but the business-logic layer is the use cases/services themselves, not the components that invoke them."} | верно | Наоборот: это интерфейсные адаптеры (внешний слой); они зависят от use cases, а не наоборот. |
T25-L4 1.33 c | Clean architecture | What sits at the very center of the onion architecture? | «entity» Пояснение: In onion architecture, the innermost layer at the very center is the Entity (Domain) layer, representing the core business objects.
Raw{"answer": "Entity", "explanation": "In onion architecture, the innermost layer at the very center is the Entity (Domain) layer, representing the core business objects."} | неверно верный: «domain model» | Центральное кольцо — Domain Model: сущности и бизнес-правила без зависимостей; далее Domain Services → Application Services → Infrastructure/UI/Tests (Palermo). |
T25-L5 1.18 c | Clean architecture | Layer boundary violations can be caught automatically: a layer-dependency analyzer (e.g. deptrac) fails on a forbidden call. | «yes» Пояснение: Tools like deptrac (Dependency Tracker) are static analysis tools that can be configured to enforce layer dependency rules and fail the build when a forbidden cross-layer call is detected.
Raw{"answer": "yes", "explanation": "Tools like deptrac (Dependency Tracker) are static analysis tools that can be configured to enforce layer dependency rules and fail the build when a forbidden cross-layer call is detected."} | верно | depfile.yaml в проекте TasK: CI проверяет правила слоёв на каждом пайплайне. |
T25-L6 1.79 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 decoupled from infrastructure; accepting an HTTP request or EntityManager couples it to specific framework/ORM details, violating clean/hexagonal architecture principles.
Raw{"answer": "no", "explanation": "A use case (interactor) should be decoupled from infrastructure; accepting an HTTP request or EntityManager couples it to specific framework/ORM details, violating clean/hexagonal architecture principles."} | верно | Use case принимает DTO и порты; привязка к HTTP/ORM протекает инфраструктуру во внутренние слои. |
T25-L7 1.16 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 Domain-Driven Design, a Repository provides a collection-like interface for aggregates/entities while abstracting the underlying storage mechanism behind a common interface.
Raw{"answer": "Repository", "explanation": "In Domain-Driven Design, a Repository provides a collection-like interface for aggregates/entities while abstracting the underlying storage mechanism behind a common interface."} | верно | Repository pattern (DDD/Evans); в проекте — Doctrine-репозитории за портами. |
T25-L8 1.98 c | Clean architecture | In clean architecture, swapping PostgreSQL for another database touches only the outer layer — the domain and use cases stay unchanged. | «yes» Пояснение: In Clean Architecture, the database is an infrastructure concern implemented at the outermost layer; the domain and use cases depend only on abstractions (e.g., a Repository interface), so switching PostgreSQL to another DB requires changes only in that outer layer.
Raw{"answer": "yes", "explanation": "In Clean Architecture, the database is an infrastructure concern implemented at the outermost layer; the domain and use cases depend only on abstractions (e.g., a Repository interface), so switching PostgreSQL to another DB requires changes only in that outer layer."} | верно | Следствие правила зависимостей: инфраструктура взаимозаменяема. |
T26-L1 1.53 c | DDD | In DDD, an aggregate is just another name for a database table. | «no» Пояснение: An aggregate in DDD is a domain-level consistency boundary around a cluster of related objects, not a database table; it is a conceptual grouping for business logic, while a table is merely a persistence detail.
Raw{"answer": "no", "explanation": "An aggregate in DDD is a domain-level consistency boundary around a cluster of related objects, not a database table; it is a conceptual grouping for business logic, while a table is merely a persistence detail."} | верно | Агрегат — кластер объектов с границей согласованности (транзакционной вокруг корня); таблица — деталь хранения. |
T26-L2 0.97 c | DDD | A Value Object is immutable and compared by the values of its fields, not by identity. | «yes» Пояснение: A Value Object is defined by immutability and value-based equality (comparing field values), rather than identity-based equality (reference comparison).
Raw{"answer": "yes", "explanation": "A Value Object is defined by immutability and value-based equality (comparing field values), rather than identity-based equality (reference comparison)."} | верно | Классика Evans: Money, Email; равенство структурное. |
T26-L3 1.78 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 entry point of an aggregate through which all external modifications must be made.
Raw{"answer": "Aggregate Root", "explanation": "In Domain-Driven Design, the Aggregate Root is the single entry point of an aggregate through which all external modifications must be made."} | верно | Aggregate Root: внешние объекты ссылаются только на корень; он защищает инварианты агрегата. |
T26-L4 1.06 c | DDD | In DDD, a repository is declared for an aggregate (its root), not for every entity. | «yes» Пояснение: In DDD, a repository is defined per aggregate root, not per individual entity; entities within the aggregate are accessed through the root.
Raw{"answer": "yes", "explanation": "In DDD, a repository is defined per aggregate root, not per individual entity; entities within the aggregate are accessed through the root."} | верно | Репозиторий корня хранит границу согласованности агрегата; вложенные сущности доступны только через корень. |
T26-L5 0.81 c | DDD | Ubiquitous language is the model's shared language common to developers and domain experts. | «yes» Пояснение: In Domain-Driven Design, ubiquitous language is a shared language between developers and domain experts that is used consistently in the model, code, and discussions.
Raw{"answer": "yes", "explanation": "In Domain-Driven Design, ubiquitous language is a shared language between developers and domain experts that is used consistently in the model, code, and discussions."} | верно | Evans: язык из требований переходит в имена классов и методов. |
T26-L6 4.73 c | DDD | What is the boundary called within which a model and its language are consistent, while outside the same words mean other models? | «domain» Пояснение: In model theory, the domain (or universe of discourse) is the boundary within which a model consistently interprets the language's symbols, while outside it the same terms can be assigned different meanings in other models.
Raw{"answer": "domain", "explanation": "In model theory, the domain (or universe of discourse) is the boundary within which a model consistently interprets the language's symbols, while outside it the same terms can be assigned different meanings in other models."} | неверно верный: «bounded context» | Bounded Context; «Заказ» в биллинге и в доставке — разные модели. |
T26-L7 1.35 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 within domain objects, not an anemic model with logic pushed into services.
Raw{"answer": "no", "explanation": "DDD recommends a rich domain model where business logic is encapsulated within domain objects, not an anemic model with logic pushed into services."} | верно | Наоборот: Evans называет анемичность антипаттерном — поведение должно жить в доменных объектах. |
T26-L8 1.68 c | DDD | Bounded context means each context has its own model: the same concept in different contexts is a different class. | «yes» Пояснение: In Domain-Driven Design, each Bounded Context defines its own model where the same universal concept (e.g., 'Customer') is represented by a different class tailored to that context's specific meaning.
Raw{"answer": "yes", "explanation": "In Domain-Driven Design, each Bounded Context defines its own model where the same universal concept (e.g., 'Customer') is represented by a different class tailored to that context's specific meaning."} | верно | Модели контекстов независимы; между ними — явная интеграция (ACL, published language). |
T13-L1 2.16 c | Symfony | Services in the Symfony DI container are created lazily by default — on first use. | «yes» Пояснение: Symfony's DI container does not pre-instantiate services; they are only constructed the first time they are requested or injected.
Raw{"answer": "yes", "explanation": "Symfony's DI container does not pre-instantiate services; they are only constructed the first time they are requested or injected."} | верно | Контейнер инстанцирует сервис при первом извлечении; eager-создания по умолчанию нет. |
T13-L2 0.53 c | Symfony | Which Symfony console command lists all registered routes? | «debug:router» Пояснение: The Symfony console command 'bin/console debug:router' lists all registered routes.
Raw{"answer": "debug:router", "explanation": "The Symfony console command 'bin/console debug:router' lists all registered routes."} | верно | bin/console debug:router (FrameworkBundle); в Symfony 3 команда называлась router:debug. |
T13-L3 1.09 c | Symfony | Symfony autowiring requires manually declaring every service in services.yaml. | «no» Пояснение: Symfony autowiring automatically resolves dependencies based on type hints, so you do not need to manually declare every service in services.yaml.
Raw{"answer": "no", "explanation": "Symfony autowiring automatically resolves dependencies based on type hints, so you do not need to manually declare every service in services.yaml."} | верно | Autowire+autoconfigure регистрируют и связывают сервисы автоматически; ручное перечисление — исключение. |
T13-L4 1.04 c | Symfony | Twig templates are compiled into PHP classes and cached between requests. | «yes» Пояснение: Twig compiles templates into PHP classes (extending Twig\Template) and stores them in a cache directory to avoid recompilation on subsequent requests.
Raw{"answer": "yes", "explanation": "Twig compiles templates into PHP classes (extending Twig\\Template) and stores them in a cache directory to avoid recompilation on subsequent requests."} | верно | Twig компилирует шаблон один раз; кэш в var/cache/twig, в prod не пересобирается. |
T13-L5 2.77 c | Symfony | In the Symfony dev environment the DI container is rebuilt only after tracked files change, not on every request. | «yes» Пояснение: In the Symfony dev environment the DI container is compiled once and cached; it is only recompiled when tracked files (service configs, etc.) change, not on every request.
Raw{"answer": "yes", "explanation": "In the Symfony dev environment the DI container is compiled once and cached; it is only recompiled when tracked files (service configs, etc.) change, not on every request."} | верно | Kernel проверяет freshness ресурсов (конфиги, классы); иначе переиспользуется кэш контейнера. |
T13-L6 0.75 c | Symfony | Which environment variable selects the active Symfony environment (dev/prod)? | «app_env» Пояснение: Since Symfony 5.1, the APP_ENV environment variable (dev, prod, test) selects the active Symfony environment.
Raw{"answer": "APP_ENV", "explanation": "Since Symfony 5.1, the APP_ENV environment variable (dev, prod, test) selects the active Symfony environment."} | верно | APP_ENV в .env; APP_DEBUG — отдельный флаг отладки. |
T13-L7 2.39 c | Symfony | A controller method can be private — Symfony routing works with any method of the class. | «no» Пояснение: Symfony's router calls the controller method from outside the class, so the method must be public; a private method would be inaccessible and throw an error.
Raw{"answer": "no", "explanation": "Symfony's router calls the controller method from outside the class, so the method must be public; a private method would be inaccessible and throw an error."} | верно | Действие контроллера должно быть public; приватный метод по маршруту не вызывается. |
T13-L8 2.17 c | Symfony | Event subscribers always receive events before listeners, because the interface gives them priority. | «no» Пояснение: Both listeners and subscribers are dispatched based on their assigned priority value, not on whether they are a listener or a subscriber; a high-priority listener is called before a low-priority subscriber.
Raw{"answer": "no", "explanation": "Both listeners and subscribers are dispatched based on their assigned priority value, not on whether they are a listener or a subscriber; a high-priority listener is called before a low-priority subscriber."} | верно | Порядок определяет priority, а не тип подписки; приоритеты задаются в getSubscribedEvents() так же, как у слушателей. |
T22-L1 1.38 c | Symfony: Security and forms | In modern Symfony (6.0+) authentication is built on authenticator classes (AuthenticatorInterface); the old guard system has been removed. | «yes» Пояснение: Symfony 6.0 removed the legacy Guard authentication system, making the AuthenticatorInterface-based system the standard for handling authentication.
Raw{"answer": "yes", "explanation": "Symfony 6.0 removed the legacy Guard authentication system, making the AuthenticatorInterface-based system the standard for handling authentication."} | верно | Guard объявлен устаревшим в 5.3 и удалён в 6.0; в проекте symfony/security-bundle 8.1. |
T22-L2 1.66 c | Symfony: Security and forms | Which Symfony attribute checks a role/permission right on a controller method (403 without it)? | «isgranted» Пояснение: The #[IsGranted] attribute in Symfony checks a role or permission on a controller action and returns a 403 Forbidden if the user lacks the required grant.
Raw{"answer": "IsGranted", "explanation": "The #[IsGranted] attribute in Symfony checks a role or permission on a controller action and returns a 403 Forbidden if the user lacks the required grant."} | верно | #[IsGranted('ROLE_ADMIN')]; атрибут из symfony/security-http. |
T22-L3 1.78 c | Symfony: Security and forms | Voters are Symfony's mechanism for checking access to a specific object: isGranted('EDIT', $post). | «yes» Пояснение: Symfony Voters (AccessVoter) are the built-in mechanism for object-level access control, and isGranted('EDIT', $post) is the correct usage to check a permission on a specific object.
Raw{"answer": "yes", "explanation": "Symfony Voters (AccessVoter) are the built-in mechanism for object-level access control, and isGranted('EDIT', $post) is the correct usage to check a permission on a specific object."} | верно | VoterInterface->vote(); docs Symfony — Voters. |
T22-L4 3.06 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» Пояснение: Symfony 7 removed the doctrine/annotations reader, so the old @Assert\NotBlank annotation syntax is no longer supported; PHP attributes (#[Assert\NotBlank]) are the standard in-code declaration method.
Raw{"answer": "yes", "explanation": "Symfony 7 removed the doctrine/annotations reader, so the old @Assert\\NotBlank annotation syntax is no longer supported; PHP attributes (#[Assert\\NotBlank]) are the standard in-code declaration method."} | верно | Докблок-аннотации удалены в Symfony 7.0; стандарт — атрибуты. В проекте symfony/validator 8.1. |
T22-L5 0.89 c | Symfony: Security and forms | CSRF protection of Symfony forms is enabled by default: the form validates the token on submission. | «yes» Пояснение: Symfony forms have CSRF protection enabled by default since Symfony 2.3; a token is automatically generated and validated on submission unless explicitly disabled.
Raw{"answer": "yes", "explanation": "Symfony forms have CSRF protection enabled by default since Symfony 2.3; a token is automatically generated and validated on submission unless explicitly disabled."} | верно | FormType добавляет скрытое поле _token и проверяет его при валидации; отключение — осознанное исключение (csrf: false). |
T22-L6 1.43 c | Symfony: Security and forms | Form validation in Symfony runs server-side even if the client-side (HTML5) checks passed. | «yes» Пояснение: Symfony's form validation is always performed server-side using the Validator component, regardless of whether client-side HTML5 validation has already passed.
Raw{"answer": "yes", "explanation": "Symfony's form validation is always performed server-side using the Validator component, regardless of whether client-side HTML5 validation has already passed."} | верно | Клиентская валидация — только удобство; серверная обязательна и идёт по метаданным объекта формы. |
T22-L7 0.76 c | Symfony: Security and forms | Which Symfony maker command generates a form class (FormType)? | «php bin/console maker:form» Пояснение: The Symfony MakerBundle command 'maker:form' generates a FormType class.
Raw{"answer": "php bin/console maker:form", "explanation": "The Symfony MakerBundle command 'maker:form' generates a FormType class."} | неверно верный: «make:form» | bin/console make:form (symfony/maker-bundle — в проекте). |
T22-L8 1.11 c | Symfony: Security and forms | Symfony stores the user's password in the session in plain text. | «no» Пояснение: Symfony stores the authenticated user's identifier (e.g., user ID or username) in the session, not the password; the password itself is hashed and stored in the database.
Raw{"answer": "no", "explanation": "Symfony stores the authenticated user's identifier (e.g., user ID or username) in the session, not the password; the password itself is hashed and stored in the database."} | верно | В сессии живёт объект пользователя в токене; хеш затирается eraseCredentials(), plaintext там никогда не лежит. |
T23-L1 1.08 c | Symfony: configuration and services | Symfony bundle configuration lives in config/packages — one file per bundle or topic. | «yes» Пояснение: Symfony Flex convention places bundle/topic-specific configuration in config/packages/, one YAML file per bundle (e.g. framework.yaml, doctrine.yaml).
Raw{"answer": "yes", "explanation": "Symfony Flex convention places bundle/topic-specific configuration in config/packages/, one YAML file per bundle (e.g. framework.yaml, doctrine.yaml)."} | верно | Стандартная структура (config/packages/*.yaml); перегрузка — config/packages/<env>. |
T23-L2 2.9 c | Symfony: configuration and services | The .env file with dev defaults is committed to the repository, while real secrets live in the non-committed .env.local. | «yes» Пояснение: This is a standard PHP best practice (e.g., Symfony) where .env holds safe dev defaults committed to the repo, and .env.local holds real secrets that are git-ignored.
Raw{"answer": "yes", "explanation": "This is a standard PHP best practice (e.g., Symfony) where .env holds safe dev defaults committed to the repo, and .env.local holds real secrets that are git-ignored."} | верно | symfony/dotenv: .env — общий безопасный набор значений; локальные секреты — .env.local (gitignored) или secrets-хранилище. |
T23-L3 0.67 c | Symfony: configuration and services | Which Symfony command lists the container's registered services and their aliases? | «debug:container» Пояснение: The Symfony command 'debug:container' lists all registered services and their aliases in the service container.
Raw{"answer": "debug:container", "explanation": "The Symfony command 'debug:container' lists all registered services and their aliases in the service container."} | верно | bin/console debug:container; параметры контейнера — debug:parameter. |
T23-L4 7.23 c | Symfony: configuration and services | The Symfony container allows changing parameters at runtime: $container->setParameter() works from a controller. | «yes» Пояснение: Symfony's Container class provides setParameter() which can be called at runtime (e.g., in a controller) to modify a parameter value, as long as the container is not frozen (it is frozen in production but not in dev mode).
Raw{"answer": "yes", "explanation": "Symfony's Container class provides setParameter() which can be called at runtime (e.g., in a controller) to modify a parameter value, as long as the container is not frozen (it is frozen in production but not in dev mode)."} | неверно верный: «no» | Контейнер компилируется и замораживается; runtime-значения — только через переменные окружения. |
T23-L5 1.22 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 by default; you must explicitly set public: true to fetch them directly from the container.
Raw{"answer": "no", "explanation": "Since Symfony 4, services are private by default; you must explicitly set public: true to fetch them directly from the container."} | верно | С Symfony 4.0 сервисы по умолчанию private: инжектятся через autowiring; $container->get() — только для публичных. |
T23-L6 1.26 c | Symfony: configuration and services | Without a config file in config/packages a bundle will not work — configuration is mandatory for every bundle. | «no» Пояснение: Bundles can work without a config file in config/packages; they can rely on default values defined in their DependencyInjection Configuration class, and some bundles require no configuration at all.
Raw{"answer": "no", "explanation": "Bundles can work without a config file in config/packages; they can rely on default values defined in their DependencyInjection Configuration class, and some bundles require no configuration at all."} | верно | У бандлов есть встроенные умолчания (Extension); конфиг нужен только для отклонений от них. |
T23-L7 1.53 c | Symfony: configuration and services | Environment variable values are injected into services.yaml using the %env(VAR)% syntax. | «yes» Пояснение: Symfony uses the %env(VAR_NAME)% syntax in services.yaml and other configuration files to inject environment variable values into service definitions.
Raw{"answer": "yes", "explanation": "Symfony uses the %env(VAR_NAME)% syntax in services.yaml and other configuration files to inject environment variable values into service definitions."} | верно | %env(...)% резолвится в рантайме env-процессорами; docs — Env Var Processors. |
T23-L8 0.83 c | Symfony: configuration and services | Which Symfony environment variable enables debug mode (affects the profiler and Twig debugging)? | «app_debug» Пояснение: The APP_DEBUG environment variable (set to 1 or true) enables Symfony's debug mode, which activates the profiler, detailed error pages, and Twig debugging.
Raw{"answer": "APP_DEBUG", "explanation": "The APP_DEBUG environment variable (set to 1 or true) enables Symfony's debug mode, which activates the profiler, detailed error pages, and Twig debugging."} | верно | APP_DEBUG=1 (в .env dev-окружения); окружение выбирает APP_ENV — см. T13-L6. |
T16-L1 1.98 c | Symfony: Messenger | A single message in Symfony Messenger can only have one handler. | «no» Пояснение: Symfony Messenger supports multiple handlers for a single message; all matching handlers are invoked sequentially by the HandlingMessagesMiddleware.
Raw{"answer": "no", "explanation": "Symfony Messenger supports multiple handlers for a single message; all matching handlers are invoked sequentially by the HandlingMessagesMiddleware."} | верно | Messenger вызывает все хендлеры, подписанные на класс сообщения (docs — Multiple Handlers). |
T16-L2 1.16 c | Symfony: Messenger | The sync transport in Messenger queues the message for a worker, just like async. | «no» Пояснение: The sync transport dispatches the message directly to handlers in the same process without queuing; it does not involve a worker.
Raw{"answer": "no", "explanation": "The sync transport dispatches the message directly to handlers in the same process without queuing; it does not involve a worker."} | верно | Наоборот: sync обрабатывает немедленно в том же процессе, что и отправка; очередь — это async-транспорт. |
T16-L3 1.33 c | Symfony: Messenger | Which console command starts the worker that processes Messenger queue messages? | «messenger:consume» Пояснение: In Symfony Messenger, the console command 'messenger:consume' starts a worker process that listens to and processes messages from a specified transport queue.
Raw{"answer": "messenger:consume", "explanation": "In Symfony Messenger, the console command 'messenger:consume' starts a worker process that listens to and processes messages from a specified transport queue."} | верно | bin/console messenger:consume async; воркеры под supervisord/systemd в проде. |
T16-L4 1.58 c | Symfony: Messenger | Retries for failed messages (retry_strategy) are configured per Messenger transport. | «no» Пояснение: In Symfony Messenger, the retry strategy (retry_strategy) is configured per message bus (or per message via attributes), not per transport.
Raw{"answer": "no", "explanation": "In Symfony Messenger, the retry strategy (retry_strategy) is configured per message bus (or per message via attributes), not per transport."} | неверно верный: «yes» | retry_strategy на транспорте: max_retries, delay, multiplier; docs — Failed Messages & Retries. |
T16-L5 5.55 c | Symfony: Messenger | By default, Messenger serializes messages to JSON. | «yes» Пояснение: By default, Symfony Messenger uses the Serializer component which encodes messages to JSON for transport.
Raw{"answer": "yes", "explanation": "By default, Symfony Messenger uses the Serializer component which encodes messages to JSON for transport."} | неверно верный: «no» | Дефолтный сериализатор — PhpSerializer (serialize()); JSON-сериализатор включается отдельно. |
T16-L6 1.36 c | Symfony: Messenger | Symfony Scheduler produces messages on a schedule and dispatches them through Messenger. | «yes» Пояснение: Symfony Scheduler (introduced in Symfony 7.1) defines recurring tasks that produce messages which are dispatched through the Messenger component for execution.
Raw{"answer": "yes", "explanation": "Symfony Scheduler (introduced in Symfony 7.1) defines recurring tasks that produce messages which are dispatched through the Messenger component for execution."} | верно | Schedule → RecurringMessage → шина Messenger; docs — Scheduler. |
T16-L7 0.89 c | Symfony: Messenger | Which built-in Messenger transport stores messages in database tables via Doctrine? | «doctrine» Пояснение: Symfony Messenger's 'doctrine' transport persists messages into database tables using Doctrine DBAL/ORM.
Raw{"answer": "doctrine", "explanation": "Symfony Messenger's 'doctrine' transport persists messages into database tables using Doctrine DBAL/ORM."} | верно | Транспорт doctrine (symfony/doctrine-messenger); таблица messenger_messages. В проекте стоит amqp-messenger + doctrine-messenger. |
T16-L8 1.23 c | Symfony: Messenger | The Messenger pipeline can be extended with custom middleware, placed before or after the built-in ones. | «yes» Пояснение: Symfony Messenger allows you to add custom middleware to the bus pipeline and control their position relative to built-in middleware via service tags and ordering.
Raw{"answer": "yes", "explanation": "Symfony Messenger allows you to add custom middleware to the bus pipeline and control their position relative to built-in middleware via service tags and ordering."} | верно | messenger.bus.*.middleware в yaml; docs — Middleware. |
T28-L1 5.09 c | Symfony: versions | Symfony major releases come every two years, minor ones every six months (in May and November). | «yes» Пояснение: Symfony follows a release cycle where major versions (e.g., 6.0, 7.0) are introduced roughly every two years in November, while minor versions (e.g., 6.1, 6.2) are released every six months (May and November).
Raw{"answer": "yes", "explanation": "Symfony follows a release cycle where major versions (e.g., 6.0, 7.0) are introduced roughly every two years in November, while minor versions (e.g., 6.1, 6.2) are released every six months (May and November)."} | верно | Стандартный релизный цикл: 8.0 — ноябрь 2025, 8.1 — май 2026, 8.2 — ноябрь 2026. |
T28-L2 1.08 c | Symfony: versions | What is the minimum PHP version required by Symfony 8? | «8.4» Пояснение: Symfony 8 requires a minimum PHP version of 8.4.
Raw{"answer": "8.4", "explanation": "Symfony 8 requires a minimum PHP version of 8.4."} | верно | Symfony 8.0 поднял требование до PHP >= 8.4.1 (в vendor проекта: "php": ">=8.4.1"). |
T28-L3 1.16 c | Symfony: versions | Symfony 7.0 kept support for docblock annotations (validation, routes). | «no» Пояснение: Symfony 7.0 removed support for docblock annotations in favor of native PHP 8 attributes.
Raw{"answer": "no", "explanation": "Symfony 7.0 removed support for docblock annotations in favor of native PHP 8 attributes."} | верно | Наоборот: в 7.0 аннотации удалены — только PHP-атрибуты (#[Route], #[Assert\NotBlank]). |
T28-L4 1.72 c | Symfony: versions | AssetMapper manages CSS/JS without node or webpack — via importmap.php. | «yes» Пояснение: Symfony's AssetMapper uses importmap.php as its configuration and processes CSS/JS natively (via esbuild/Lightning CSS binaries) without requiring Node.js or Webpack.
Raw{"answer": "yes", "explanation": "Symfony's AssetMapper uses importmap.php as its configuration and processes CSS/JS natively (via esbuild/Lightning CSS binaries) without requiring Node.js or Webpack."} | верно | symfony/asset-mapper (с 6.3, стандарт с 7.x); в проекте — importmap.php в корне и asset-mapper 8.1. |
T28-L5 3.33 c | Symfony: versions | Symfony 6.4 is a regular release without long-term support. | «no» Пояснение: Symfony 6.4 is actually an LTS (Long-Term Support) release, supported until November 2027, following Symfony's pattern of designating x.4 releases as LTS.
Raw{"answer": "no", "explanation": "Symfony 6.4 is actually an LTS (Long-Term Support) release, supported until November 2027, following Symfony's pattern of designating x.4 releases as LTS."} | верно | Наоборот: 6.4 — LTS (расширенная поддержка); LTS выходит вместе с очередным мажором (6.4 — вместе с 7.0). |
T28-L6 4.13 c | Symfony: versions | When moving to a new Symfony major version, deprecations of the previous branch keep working — major releases do not remove them. | «yes» Пояснение: Symfony's deprecation policy requires that a deprecated feature remains functional for at least two major versions after its deprecation, so deprecations introduced in the previous major branch still work in the next one.
Raw{"answer": "yes", "explanation": "Symfony's deprecation policy requires that a deprecated feature remains functional for at least two major versions after its deprecation, so deprecations introduced in the previous major branch still work in the next one."} | неверно верный: «no» | Наоборот: мажорный релиз удаляет всё устаревшее (7.0 убрал деприкейшены 6.x, 8.0 — 7.x). |
T28-L7 1.12 c | Symfony: versions | Every Symfony major release is accompanied by an UPGRADE guide listing the changes. | «yes» Пояснение: Each Symfony major release includes an UPGRADE file (e.g., UPGRADE-7.0) documenting breaking changes and migration notes.
Raw{"answer": "yes", "explanation": "Each Symfony major release includes an UPGRADE file (e.g., UPGRADE-7.0) documenting breaking changes and migration notes."} | верно | UPGRADE-7.0.md, UPGRADE-8.0.md в репозитории symfony/symfony. |
T28-L8 1.06 c | Symfony: versions | Which Symfony component manages assets and the importmap without node/webpack? | «assetmapper» Пояснение: Symfony's AssetMapper component (introduced in Symfony 6.4/7.0) manages frontend assets and importmaps natively without requiring Node.js or Webpack.
Raw{"answer": "AssetMapper", "explanation": "Symfony's AssetMapper component (introduced in Symfony 6.4/7.0) manages frontend assets and importmaps natively without requiring Node.js or Webpack."} | верно | symfony/asset-mapper 8.1 — в проекте. |
T29-L1 12.36 c | Symfony: 8.2 and beyond | As of 2026-11-07, Symfony 8.2 has already been released. | «yes» Пояснение: Following Symfony's standard release cycle (minor versions every ~6 months), Symfony 8.2 is expected to be released in November 2026, which by 2026-11-07 would have already been released.
Raw{"answer": "yes", "explanation": "Following Symfony's standard release cycle (minor versions every ~6 months), Symfony 8.2 is expected to be released in November 2026, which by 2026-11-07 would have already been released."} | неверно верный: «no» | Наоборот: 8.2 ещё не выпущена — релиз в конце ноября 2026; последняя стабильная — 8.1. |
T29-L2 5.13 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, Symfony 8.1 (not 8.2) is scheduled for November 2026; Symfony 8.2 would come in May 2027.
Raw{"answer": "no", "explanation": "Following Symfony's six-month release cycle, Symfony 8.1 (not 8.2) is scheduled for November 2026; Symfony 8.2 would come in May 2027."} | неверно верный: «yes» | Политика релизов: 8.1 — май 2026, 8.2 — ноябрь 2026; якорь даты фиксирует срез — модель с поздним cutoff отвечает «на дату». |
T29-L3 1.03 c | Symfony: 8.2 and beyond | Which Symfony version comes after 8.1 (as of 2026-11-07)? | «8.2» Пояснение: The next minor version after Symfony 8.1 is 8.2.
Raw{"answer": "8.2", "explanation": "The next minor version after Symfony 8.1 is 8.2."} | верно | 8.2 — следующий минорный релиз (ноябрь 2026); после его выхода проект переходит с 8.1.* на 8.2.*. |
T29-L4 2.32 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 (8.x line), not a major release; major releases follow the X.0 pattern and introduce breaking changes, while minor releases only add features without breaking existing APIs.
Raw{"answer": "no", "explanation": "Symfony 8.2 is a minor release (8.x line), not a major release; major releases follow the X.0 pattern and introduce breaking changes, while minor releases only add features without breaking existing APIs."} | верно | Наоборот: 8.2 — минорный релиз; новые возможности без поломки обратной совместимости. Мажор — 9.0. |
T29-L5 1.48 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 within the same major version, so minor updates like 8.1 to 8.2 should not break existing code.
Raw{"answer": "yes", "explanation": "PHP guarantees backward compatibility within the same major version, so minor updates like 8.1 to 8.2 should not break existing code."} | верно | Политика Symfony: минорные релизы обратно совместимы; BC-break допустим только в мажорных. |
T29-L6 6.6 c | Symfony: 8.2 and beyond | Which minor version of the 8.x branch is released last, before Symfony 9.0? | «8.4» Пояснение: Following Symfony's consistent release pattern of five minor versions per major branch (e.g., 6.0–6.4, 7.0–7.4), the last minor version of the 8.x branch before 9.0 is 8.4.
Raw{"answer": "8.4", "explanation": "Following Symfony's consistent release pattern of five minor versions per major branch (e.g., 6.0–6.4, 7.0–7.4), the last minor version of the 8.x branch before 9.0 is 8.4."} | верно | По циклу: 8.2 (ноя 2026), 8.3 (май 2027), 8.4 (ноя 2027, вместе с 9.0) — как 6.4 выходила вместе с 7.0. |
T29-L7 6.54 c | Symfony: 8.2 and beyond | Symfony 8.2 will require PHP 8.5 — you would have to upgrade PHP along with it. | «no» Пояснение: Symfony 8.x is expected to require PHP 8.4 as its minimum version, not PHP 8.5; the minimum PHP requirement is typically set at the start of the major cycle and remains consistent across minor versions.
Raw{"answer": "no", "explanation": "Symfony 8.x is expected to require PHP 8.4 as its minimum version, not PHP 8.5; the minimum PHP requirement is typically set at the start of the major cycle and remains consistent across minor versions."} | верно | Наоборот: минорные релизы не поднимают требования PHP; для всей ветки 8.x остаётся PHP >= 8.4. |
T29-L8 2.44 c | Symfony: 8.2 and beyond | Deprecations added in the 8.x branch will not be removed before Symfony 9.0. | «yes» Пояснение: Symfony's deprecation policy guarantees that deprecations introduced in a major version (8.x) remain for the entire lifetime of that branch and are only removed in the next major version (9.0).
Raw{"answer": "yes", "explanation": "Symfony's deprecation policy guarantees that deprecations introduced in a major version (8.x) remain for the entire lifetime of that branch and are only removed in the next major version (9.0)."} | верно | Политика: деприкейшены живут до следующего мажора; 9.0 — ноябрь 2027. |
T21-L1 1.81 c | Twig | Inside {{ }}, Twig allows calling arbitrary PHP code directly. | «no» Пояснение: Twig's {{ }} allows only Twig expressions (variables, filters, registered functions, method calls on objects), not arbitrary PHP code like phpinfo() or full PHP statements.
Raw{"answer": "no", "explanation": "Twig's {{ }} allows only Twig expressions (variables, filters, registered functions, method calls on objects), not arbitrary PHP code like phpinfo() or full PHP statements."} | верно | Twig — DSL: только разрешённые окружением функции/фильтры; произвольный PHP не исполняется. |
T21-L2 0.81 c | Twig | By default, Twig auto-escapes printed variables. | «yes» Пояснение: Twig has auto-escaping enabled by default (using the 'html' strategy), so variables printed with {{ }} are HTML-escaped automatically to prevent XSS vulnerabilities.
Raw{"answer": "yes", "explanation": "Twig has auto-escaping enabled by default (using the 'html' strategy), so variables printed with {{ }} are HTML-escaped automatically to prevent XSS vulnerabilities."} | верно | Autoescape включён по умолчанию; {{ '<b>' }} → <b>. Проверено на Twig 3.30. |
T21-L3 1.0 c | Twig | The Twig |e filter escapes a string for safe output in an HTML context. | «yes» Пояснение: The Twig |e (escape) filter defaults to the 'html' strategy, escaping characters like <, >, &, ", and ' for safe HTML output.
Raw{"answer": "yes", "explanation": "The Twig |e (escape) filter defaults to the 'html' strategy, escaping characters like <, >, &, \", and ' for safe HTML output."} | верно | |e ('html') по умолчанию; есть контексты js/url/css. От SQL-инъекций он не защищает — это задача подготовленных запросов Doctrine. |
T21-L4 0.8 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.
Raw{"answer": "number_format", "explanation": "The twig/intl-extra package provides the number_format filter, which formats a number according to a specified locale."} | неверно верный: «format_number» | |format_number(locale=...) из IntlExtension (twig/intl-extra есть в проекте). Проверено на Twig 3.30: 12345.6 → 12 345,6 (ru). |
T21-L5 0.84 c | Twig | The |raw filter disables auto-escaping for the value. | «yes» Пояснение: In Twig, the |raw filter marks a value as safe, preventing it from being auto-escaped during output.
Raw{"answer": "yes", "explanation": "In Twig, the |raw filter marks a value as safe, preventing it from being auto-escaped during output."} | верно | {{ x|raw }} выводит HTML как есть; опасно с пользовательскими данными. Проверено на Twig 3.30. |
T21-L6 0.83 c | Twig | In Twig, {{ }} prints an expression value, while {% %} executes tags — conditions, loops, set. | «yes» Пояснение: In Twig, {{ }} is used for outputting expression values, while {% %} is used for executing tags such as conditions, loops, and set statements.
Raw{"answer": "yes", "explanation": "In Twig, {{ }} is used for outputting expression values, while {% %} is used for executing tags such as conditions, loops, and set statements."} | верно | Два блока синтаксиса Twig: вывод (echo) против логики. |
T21-L7 0.81 c | Twig | In Twig you cannot declare a variable inside a template — values only come from the controller. | «no» Пояснение: Twig allows declaring variables inside templates using the {% set %} tag, so values do not only come from the controller.
Raw{"answer": "no", "explanation": "Twig allows declaring variables inside templates using the {% set %} tag, so values do not only come from the controller."} | верно | {% set y = ... %} объявляет переменную в шаблоне. Проверено на Twig 3.30. |
T21-L8 0.53 c | Twig | Which Twig function dumps the debug structure of a variable (array, object)? | «dump» Пояснение: The Twig function dump() outputs the debug structure of a variable such as an array or object.
Raw{"answer": "dump", "explanation": "The Twig function dump() outputs the debug structure of a variable such as an array or object."} | верно | {{ dump(x) }} (DebugExtension; в Symfony доступна в dev-окружении). |
T24-L1 1.38 c | Bootstrap | Bootstrap is a CSS/JS library of ready-made UI components, not an SPA framework. | «yes» Пояснение: Bootstrap is a front-end CSS/JS framework providing pre-built UI components (grid, modals, navbars), not a Single Page Application framework like Angular, React, or Vue.
Raw{"answer": "yes", "explanation": "Bootstrap is a front-end CSS/JS framework providing pre-built UI components (grid, modals, navbars), not a Single Page Application framework like Angular, React, or Vue."} | верно | Компоненты и утилиты поверх вашего HTML; SPA-фреймворки (React/Vue) — другой класс инструментов. В проекте vendored 5.3.3. |
T24-L2 1.24 c | Bootstrap | Which Bootstrap class gives a responsive container with a fixed max width per breakpoint? | «container» Пояснение: The .container class in Bootstrap provides a responsive, centered container with a fixed 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, centered container with a fixed maximum width that changes at each breakpoint (e.g., 540px, 720px, 960px, 1140px, 1320px)."} | верно | .container (фиксированная макс-ширина по брейкпоинтам) vs .container-fluid (на всю ширину). |
T24-L3 1.25 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 (v4+) use Flexbox rather than CSS floats.
Raw{"answer": "no", "explanation": "The Bootstrap grid splits a row into 12 columns, not 16, and modern versions (v4+) use Flexbox rather than CSS floats."} | верно | Наоборот: flexbox (с Bootstrap 4) и 12 колонок; float-сетка — это Bootstrap 3. |
T24-L4 2.08 c | Bootstrap | Bootstrap's named breakpoints (the infix used in class names) are sm, md, lg, xl, xxl — five of them. | «yes» Пояснение: Bootstrap 5 defines exactly five named breakpoint infixes: sm (576px), md (768px), lg (992px), xl (1200px), and xxl (1400px).
Raw{"answer": "yes", "explanation": "Bootstrap 5 defines exactly five named breakpoint infixes: sm (576px), md (768px), lg (992px), xl (1200px), and xxl (1400px)."} | верно | Тиров всего шесть: xs (без инфикса) + пять именованных (576/768/992/1200/1400 px). |
T24-L5 5.74 c | Bootstrap | Utilities like .mt-3 or .px-2 use the spacing scale: the number is a multiple of $spacer. | «yes» Пояснение: In Bootstrap, utilities like .mt-3 or .px-2 reference a spacing scale ($spacers) whose values are all defined as multiples (including fractional multiples) of the $spacer variable (default 1rem).
Raw{"answer": "yes", "explanation": "In Bootstrap, utilities like .mt-3 or .px-2 reference a spacing scale ($spacers) whose values are all defined as multiples (including fractional multiples) of the $spacer variable (default 1rem)."} | неверно верный: «no» | Spacing utilities; $spacer = 1rem. |
T24-L6 1.11 c | Bootstrap | Which Bootstrap 5 data attribute enables an interactive component (e.g. dropdown) on an element? | «data-bs-toggle» Пояснение: In Bootstrap 5, the data-bs-toggle attribute is used to enable interactive components such as dropdowns, tooltips, popovers, and collapse elements.
Raw{"answer": "data-bs-toggle", "explanation": "In Bootstrap 5, the data-bs-toggle attribute is used to enable interactive components such as dropdowns, tooltips, popovers, and collapse elements."} | верно | data-bs-toggle="dropdown" и т.п.; в Bootstrap 4 атрибут назывался data-toggle. |
T24-L7 1.02 c | Bootstrap | Bootstrap 5 components work without jQuery — in plain vanilla JS. | «yes» Пояснение: Bootstrap 5 removed the jQuery dependency and its interactive components (modals, tooltips, dropdowns, etc.) are built with vanilla JavaScript and Popper.js.
Raw{"answer": "yes", "explanation": "Bootstrap 5 removed the jQuery dependency and its interactive components (modals, tooltips, dropdowns, etc.) are built with vanilla JavaScript and Popper.js."} | верно | jQuery удалён в Bootstrap 5.0: data-bs-* атрибуты и JS API. В проекте vendored 5.3.3. |
T24-L8 1.56 c | Bootstrap | Dark mode in Bootstrap is enabled with a .dark class on the root element. | «no» Пояснение: In Bootstrap 5.3, dark mode is enabled with the data-bs-theme="dark" attribute on the <html> element, not a .dark class.
Raw{"answer": "no", "explanation": "In Bootstrap 5.3, dark mode is enabled 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.23 c | Doctrine | Doctrine ORM creates database tables on the fly the first time an entity is used at runtime. | «no» Пояснение: Doctrine ORM does not automatically create tables at runtime; you must explicitly run schema tools or migrations to create the database structure.
Raw{"answer": "no", "explanation": "Doctrine ORM does not automatically create tables at runtime; you must explicitly run schema tools or migrations to create the database structure."} | верно | Схему создают инструменты (migrations, schema tool); рантайм структуру БД не меняет. |
T14-L2 0.8 c | Doctrine | Which EntityManager method marks a new object as managed without executing SQL until flush()? | «persist» Пояснение: EntityManager::persist() marks a new entity as managed in the persistence context without issuing SQL; the INSERT is only generated on flush().
Raw{"answer": "persist", "explanation": "EntityManager::persist() marks a new entity as managed in the persistence context without issuing SQL; the INSERT is only generated on flush()."} | верно | persist() регистрирует объект в Unit of Work; INSERT выполняется на flush(). |
T14-L3 10.71 c | Doctrine | In Doctrine ORM 3, the EntityManager::merge() method exists and makes the passed object managed. | «no» Пояснение: EntityManager::merge() does exist in Doctrine ORM 3, but it does not make the passed object managed; it returns a new managed copy while the original remains detached.
Raw{"answer": "no", "explanation": "EntityManager::merge() does exist in Doctrine ORM 3, but it does not make the passed object managed; it returns a new managed copy while the original remains detached."} | верно | В ORM 3 merge() удалён (в vendor проекта 3.7.6 метода нет); в Doctrine 2.x merge() возвращал управляемую копию. Версия зафиксирована — ORM 3. |
T14-L4 0.94 c | Doctrine | DQL queries are written in terms of entities and their fields, not tables and columns. | «yes» Пояснение: DQL (Doctrine Query Language) operates at the ORM level, referencing entity class names and their mapped fields rather than raw database tables and columns.
Raw{"answer": "yes", "explanation": "DQL (Doctrine Query Language) operates at the ORM level, referencing entity class names and their mapped fields rather than raw database tables and columns."} | верно | Doctrine транслирует DQL в SQL; docs — DQL (Doctrine Query Language). |
T14-L5 0.75 c | Doctrine | What does $repository->find(999) return when no record with id 999 exists? | «null» Пояснение: Doctrine's EntityRepository::find() returns null when no entity matching the given ID is found.
Raw{"answer": "null", "explanation": "Doctrine's EntityRepository::find() returns null when no entity matching the given ID is found."} | верно | find() возвращает null, если объект не найден (docs Repository methods). |
T14-L6 2.8 c | Doctrine | DoctrineBundle in Symfony automatically calls flush() at the end of every request. | «no» Пояснение: DoctrineBundle does not automatically call flush() at the end of a request; developers must explicitly invoke $em->flush() to persist pending changes to the database.
Raw{"answer": "no", "explanation": "DoctrineBundle does not automatically call flush() at the end of a request; developers must explicitly invoke $em->flush() to persist pending changes to the database."} | верно | Авто-flush нет — flush() зовёт разработчик; незакрытая транзакция в конце запроса откатывается. |
T14-L7 2.17 c | Doctrine | For a managed entity, changing a property is enough: flush() commits the change without an explicit persist() — the Unit of Work tracks changes. | «yes» Пояснение: In Doctrine ORM, the Unit of Work performs dirty-checking on all managed entities during flush(), so modifying a property on an already-managed entity is automatically detected and committed without needing an explicit persist() call.
Raw{"answer": "yes", "explanation": "In Doctrine ORM, the Unit of Work performs dirty-checking on all managed entities during flush(), so modifying a property on an already-managed entity is automatically detected and committed without needing an explicit persist() call."} | верно | Dirty checking сравнивает снимки свойств; persist нужен только новым/отсоединённым объектам. |
T14-L8 1.13 c | Doctrine | remove() executes the SQL DELETE immediately, without waiting for flush(). | «no» Пояснение: In Doctrine ORM, remove() only marks the entity as scheduled for deletion in the UnitOfWork; the actual SQL DELETE is issued when flush() is called.
Raw{"answer": "no", "explanation": "In Doctrine ORM, remove() only marks the entity as scheduled for deletion in the UnitOfWork; the actual SQL DELETE is issued when flush() is called."} | верно | remove() планирует удаление в Unit of Work; DELETE выполняется на flush() (docs — Deleting Objects). |
T15-L1 1.11 c | PostgreSQL | PostgreSQL uses MVCC, therefore readers block writers and writers block readers. | «no» Пояснение: MVCC's whole purpose is the opposite: readers do not block writers and writers do not block readers, because each transaction sees a consistent snapshot of the data.
Raw{"answer": "no", "explanation": "MVCC's whole purpose is the opposite: readers do not block writers and writers do not block readers, because each transaction sees a consistent snapshot of the data."} | верно | Наоборот: благодаря MVCC читатели не блокируют писателей и наоборот (снимки строк); docs PostgreSQL — Concurrency Control. |
T15-L2 1.01 c | PostgreSQL | Which SQL command shows a query's execution plan without executing the query? | «explain» Пояснение: The EXPLAIN SQL command displays the query execution plan (how the database will execute the query) without actually running the query.
Raw{"answer": "EXPLAIN", "explanation": "The EXPLAIN SQL command displays the query execution plan (how the database will execute the query) without actually running the query."} | верно | EXPLAIN без ANALYZE только строит план; проверено на PostgreSQL 17.7. |
T15-L3 3.22 c | PostgreSQL | SERIAL and GENERATED ... AS IDENTITY are just two names for the same mechanism. | «no» Пояснение: While both provide auto-incrementing values, SERIAL is syntactic sugar that creates a separate sequence + DEFAULT, whereas GENERATED AS IDENTITY is a SQL-standard column attribute with different override semantics (OVERRIDING SYSTEM VALUE), tighter coupling to the column, and different alter/drop behavior.
Raw{"answer": "no", "explanation": "While both provide auto-incrementing values, SERIAL is syntactic sugar that creates a separate sequence + DEFAULT, whereas GENERATED AS IDENTITY is a SQL-standard column attribute with different override semantics (OVERRIDING SYSTEM VALUE), tighter coupling to the column, and different alter/drop behavior."} | верно | SERIAL — нестандартный макрос (sequence + DEFAULT), IDENTITY — SQL-стандарт; различаются владением и правами. Оба есть в PG 17 (проверено). |
T15-L4 1.53 c | PostgreSQL | By default, a PostgreSQL UNIQUE constraint allows only one row with NULL in the column. | «no» Пояснение: By default, PostgreSQL treats NULL values as distinct from each other in UNIQUE constraints, so multiple rows can have NULL in that column.
Raw{"answer": "no", "explanation": "By default, PostgreSQL treats NULL values as distinct from each other in UNIQUE constraints, so multiple rows can have NULL in that column."} | верно | Наоборот: NULLS DISTINCT по умолчанию — несколько NULL допустимы; NULLS NOT DISTINCT — опция с PG 15. Проверено на PG 17.7. |
T15-L5 0.46 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.
Raw{"answer": "string_agg", "explanation": "PostgreSQL's string_agg() aggregate function concatenates strings with a specified separator."} | верно | string_agg(значение, разделитель); проверено на PostgreSQL 17.7. |
T15-L6 1.0 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; it is VACUUM FULL that rewrites the table and returns space to the OS.
Raw{"answer": "no", "explanation": "Plain VACUUM only marks dead-tuple space as reusable within the table; it is VACUUM FULL that rewrites the table and returns space to the OS."} | верно | VACUUM помечает место для переиспользования внутри таблицы; ОС его возвращает только VACUUM FULL (с эксклюзивной блокировкой). |
T15-L7 0.64 c | PostgreSQL | Which keyword in a window function definition partitions rows into groups the function is computed over? | «partition by» Пояснение: The PARTITION BY clause in a window function definition divides rows into groups over which the window function is computed.
Raw{"answer": "PARTITION BY", "explanation": "The PARTITION BY clause in a window function definition divides rows into groups over which the window function is computed."} | верно | OVER (PARTITION BY ...); проверено на PostgreSQL 17.7. |
T15-L8 1.12 c | PostgreSQL | The READ COMMITTED isolation level protects against non-repeatable reads. | «no» Пояснение: READ COMMITTED only protects against dirty reads; non-repeatable reads are prevented at the REPEATABLE READ level or higher.
Raw{"answer": "no", "explanation": "READ COMMITTED only protects against dirty reads; non-repeatable reads are prevented at the REPEATABLE READ level or higher."} | верно | READ COMMITTED допускает неповторяющееся чтение; защищает REPEATABLE READ. Проверено: SHOW transaction_isolation → read committed. |
T17-L1 0.93 c | PostgreSQL: transactions and indexes | By default, PostgreSQL wraps each single SQL statement in its own implicit transaction (autocommit). | «yes» Пояснение: PostgreSQL operates in autocommit mode by default, meaning each individual SQL statement is automatically committed as its own implicit transaction unless explicitly wrapped in a BEGIN...COMMIT block.
Raw{"answer": "yes", "explanation": "PostgreSQL operates in autocommit mode by default, meaning each individual SQL statement is automatically committed as its own implicit transaction unless explicitly wrapped in a BEGIN...COMMIT block."} | верно | Без BEGIN каждый оператор коммитится сам; docs PostgreSQL — Transactions. Проверено на PG 17. |
T17-L2 0.48 c | PostgreSQL: transactions and indexes | Which SQL command ends a transaction, committing all its changes? | «commit» Пояснение: The COMMIT SQL command ends a transaction and permanently saves all changes made within it.
Raw{"answer": "COMMIT", "explanation": "The COMMIT SQL command ends a transaction and permanently saves all changes made within it."} | верно | COMMIT (END — синоним). Проверено на PG 17. |
T17-L3 1.13 c | PostgreSQL: transactions and indexes | Indexes speed up more than SELECT: UPDATE and DELETE with a search on an indexed column benefit too. | «yes» Пояснение: Indexes help the database engine locate rows quickly for any DML statement (SELECT, UPDATE, DELETE) whose WHERE clause references an indexed column, avoiding a full table scan.
Raw{"answer": "yes", "explanation": "Indexes help the database engine locate rows quickly for any DML statement (SELECT, UPDATE, DELETE) whose WHERE clause references an indexed column, avoiding a full table scan."} | верно | Поиск строк для изменения идёт по индексу; docs PostgreSQL — Indexes. |
T17-L4 0.93 c | PostgreSQL: transactions and indexes | To roll back part of the statements inside a transaction, PostgreSQL uses SAVEPOINT. | «yes» Пояснение: SAVEPOINT allows rolling back to a specific named point within a transaction without undoing the entire transaction.
Raw{"answer": "yes", "explanation": "SAVEPOINT allows rolling back to a specific named point within a transaction without undoing the entire transaction."} | верно | SAVEPOINT name; ROLLBACK TO name — частичный откат без отмены всей транзакции. Проверено на PG 17. |
T17-L5 0.87 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 timing and row-count statistics; plain EXPLAIN shows the plan without executing it.
Raw{"answer": "no", "explanation": "EXPLAIN ANALYZE actually executes the query to provide real timing and row-count statistics; plain EXPLAIN shows the plan without executing it."} | верно | Наоборот: ANALYZE реально выполняет запрос (с побочными эффектами!) и показывает фактические времена узлов; план без выполнения — plain EXPLAIN. |
T17-L6 0.56 c | PostgreSQL: transactions and indexes | Which PostgreSQL extension adds vector types and indexes for embedding search? | «pgvector» Пояснение: pgvector is the PostgreSQL extension that adds vector types and indexes for embedding similarity search.
Raw{"answer": "pgvector", "explanation": "pgvector is the PostgreSQL extension that adds vector types and indexes for embedding similarity search."} | верно | CREATE EXTENSION vector (проект pgvector; в проекте образ pgvector/pgvector:pg17). |
T17-L7 1.7 c | PostgreSQL: transactions and indexes | A partial index (CREATE INDEX ... WHERE ...) is built only over rows satisfying the condition. | «yes» Пояснение: A partial index (a PostgreSQL feature) only stores index entries for rows that satisfy the WHERE condition, reducing index size and maintenance cost.
Raw{"answer": "yes", "explanation": "A partial index (a PostgreSQL feature) only stores index entries for rows that satisfy the WHERE condition, reducing index size and maintenance cost."} | верно | docs PostgreSQL — Partial Indexes; типичный кейс — индекс по «активным» записям. |
T17-L8 1.97 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), a multiversion concurrency control mechanism that detects conflicts after the fact, rather than by locking the rows a transaction reads.
Raw{"answer": "no", "explanation": "PostgreSQL implements SERIALIZABLE using Serializable Snapshot Isolation (SSI), a multiversion concurrency control mechanism that detects conflicts after the fact, rather than by locking the rows a transaction reads."} | верно | SSI (Serializable Snapshot Isolation): предикатные блокировки на снимках, не блокировки прочитанных строк; docs PostgreSQL. |
T19-L1 0.72 c | HTTP and REST API | HTTP status 201 means the request resulted in a new resource being created. | «yes» Пояснение: HTTP 201 'Created' specifically indicates that the request succeeded and a new resource was created as a result.
Raw{"answer": "yes", "explanation": "HTTP 201 'Created' specifically indicates that the request succeeded and a new resource was created as a result."} | верно | 201 Created; обычно на POST, часто с Location; RFC 9110. |
T19-L2 1.34 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 where the server intentionally returns an empty response body, commonly used after DELETE operations.
Raw{"answer": 204, "explanation": "HTTP 204 No Content indicates a successful request where the server intentionally returns an empty response body, commonly used after DELETE operations."} | верно | 204 No Content; RFC 9110. |
T19-L3 1.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 explicitly classifies DELETE as an idempotent method, meaning repeated DELETE requests on the same resource have the same effect as a single request.
Raw{"answer": "yes", "explanation": "RFC 7231 explicitly classifies DELETE as an idempotent method, meaning repeated DELETE requests on the same resource have the same effect as a single request."} | верно | RFC 9110: DELETE идемпотентен (как PUT); идемпотентность ≠ безопасность — ресурс удаляется при первом вызове. |
T19-L4 0.97 c | HTTP and REST API | The Access-Control-Allow-Origin header is sent by the client so that the server agrees to accept requests from another origin. | «no» Пояснение: The Access-Control-Allow-Origin header is sent by the server (not the client) to indicate which origin is permitted to access the resource.
Raw{"answer": "no", "explanation": "The Access-Control-Allow-Origin header is sent by the server (not the client) to indicate which origin is permitted to access the resource."} | верно | Наоборот: заголовок шлёт СЕРВЕР в ответе, разрешая браузеру cross-origin запрос (CORS); в проекте nelmio/cors-bundle. |
T19-L5 0.89 c | HTTP and REST API | Status 429 Too Many Requests is used when a client exceeds a rate limit. | «yes» Пояснение: HTTP 429 Too Many Requests was defined in RFC 6585 specifically to indicate that a client has exceeded a rate limit.
Raw{"answer": "yes", "explanation": "HTTP 429 Too Many Requests was defined in RFC 6585 specifically to indicate that a client has exceeded a rate limit."} | верно | 429 (+ Retry-After); RFC 6585. В проекте symfony/rate-limiter. |
T19-L6 0.99 c | HTTP and REST API | 5xx codes mean a client error, while 4xx means a server-side error. | «no» Пояснение: It's the opposite: 4xx codes indicate client errors (e.g., 404 Not Found) and 5xx codes indicate server errors (e.g., 500 Internal Server Error).
Raw{"answer": "no", "explanation": "It's the opposite: 4xx codes indicate client errors (e.g., 404 Not Found) and 5xx codes indicate server errors (e.g., 500 Internal Server Error)."} | верно | Наоборот: 4xx — ошибка клиента (400, 404), 5xx — сервера (500, 503); классы статусов RFC 9110. |
T19-L7 0.6 c | HTTP and REST API | Which HTTP header indicates the MIME type of the request or response body? | «content-type» Пояснение: The Content-Type HTTP header specifies the MIME type (media type) of the request or response body.
Raw{"answer": "Content-Type", "explanation": "The Content-Type HTTP header specifies the MIME type (media type) of the request or response body."} | верно | Content-Type: application/json и т.п. |
T19-L8 1.22 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 (defined in RFC 7231) is idempotent by definition.
Raw{"answer": "yes", "explanation": "RFC 5789 explicitly states that PATCH is not idempotent, whereas PUT (defined in RFC 7231) is idempotent by definition."} | верно | RFC 5789 прямо оговаривает: PATCH не гарантированно идемпотентен; PUT идемпотентен. |
T20-L1 1.28 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; one should use hash_equals() or password_verify() for constant-time comparison.
Raw{"answer": "no", "explanation": "Plain == is vulnerable to timing attacks; one should use hash_equals() or password_verify() for constant-time comparison."} | верно | Нужна постоянновременная проверка (password_verify) — timing-атаки; соль и алгоритм уже внутри хеша. |
T20-L2 1.16 c | Security and OAuth | A CSRF token is issued by the server (bound to the session) and verified server-side on unsafe requests (POST etc.). | «yes» Пояснение: A CSRF token is generated by the server, tied to the user's session, and validated server-side on state-changing requests (POST, PUT, DELETE) to ensure the request originated from the legitimate application.
Raw{"answer": "yes", "explanation": "A CSRF token is generated by the server, tied to the user's session, and validated server-side on state-changing requests (POST, PUT, DELETE) to ensure the request originated from the legitimate application."} | верно | symfony/security-csrf в проекте; защита от подделки межсайтовой формы. |
T20-L3 0.64 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 define and enforce CSP rules that help mitigate XSS and other code injection attacks.
Raw{"answer": "Content-Security-Policy", "explanation": "The Content-Security-Policy HTTP header is used to define and enforce CSP rules that help mitigate XSS and other code injection attacks."} | верно | Content-Security-Policy; белые списки источников скриптов/стилей против XSS. |
T20-L4 1.8 c | Security and OAuth | OAuth 2.0 is an authentication protocol: the access token tells you who the user is. | «no» Пояснение: OAuth 2.0 is an authorization protocol, not an authentication protocol, and the access token grants resource access rather than identifying the user (the ID token in OpenID Connect does that).
Raw{"answer": "no", "explanation": "OAuth 2.0 is an authorization protocol, not an authentication protocol, and the access token grants resource access rather than identifying the user (the ID token in OpenID Connect does that)."} | верно | OAuth 2.0 — авторизация/делегирование доступа; аутентификацию добавляет OpenID Connect. В проекте knpuniversity/oauth2-client-bundle (yandex/github/google). |
T20-L5 2.65 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 output encoding/escaping when data is rendered to the browser, not by input validation before storage; input validation alone is insufficient because 'valid' data can still contain script that executes in the output context.
Raw{"answer": "no", "explanation": "XSS is primarily prevented by output encoding/escaping when data is rendered to the browser, not by input validation before storage; input validation alone is insufficient because 'valid' data can still contain script that executes in the output context."} | верно | XSS лечится контекстным экранированием НА ВЫВОДЕ (Twig autoescape, CSP); валидация ввода не покрывает все контексты вывода. |
T20-L6 0.98 c | Security and OAuth | In the OAuth 2.0 authorization code flow, which parameter arrives at the redirect_uri and is exchanged for an access token? | «code» Пояснение: In the OAuth 2.0 authorization code flow, the 'code' parameter is appended to the redirect_uri and is then exchanged at the token endpoint for an access token.
Raw{"answer": "code", "explanation": "In the OAuth 2.0 authorization code flow, the 'code' parameter is appended to the redirect_uri and is then exchanged at the token endpoint for an access token."} | верно | Параметр code; обмен на токен POST-ом на /token с client_secret. |
T20-L7 1.14 c | Security and OAuth | A refresh token lives longer than an access token and allows obtaining a new access token without the user logging in again. | «yes» Пояснение: A refresh token is intentionally long-lived and its purpose is to mint new access tokens without requiring the user to log in again.
Raw{"answer": "yes", "explanation": "A refresh token is intentionally long-lived and its purpose is to mint new access tokens without requiring the user to log in again."} | верно | Стандартная схема OAuth/OIDC: короткий access + длинный refresh. |
T20-L8 1.63 c | Security and OAuth | A password salt must be kept secret: without it the hash cannot be verified. | «no» Пояснение: The salt does not need to be secret; it is typically stored alongside the hash (e.g., in the $algo$salt$hash format), and its purpose is to prevent rainbow-table attacks, not to act as a secret key.
Raw{"answer": "no", "explanation": "The salt does not need to be secret; it is typically stored alongside the hash (e.g., in the $algo$salt$hash format), and its purpose is to prevent rainbow-table attacks, not to act as a secret key."} | верно | Соль хранится открыто (password_hash включает её в строку хеша); секретность соли не нужна. |
T18-L1 0.98 c | Testing: PHPUnit | PHPUnit runs test methods of any class — extending TestCase is not required. | «no» Пояснение: In PHPUnit, a class must extend PHPUnit\Framework\TestCase for its test methods to be discovered and executed.
Raw{"answer": "no", "explanation": "In PHPUnit, a class must extend PHPUnit\\Framework\\TestCase for its test methods to be discovered and executed."} | верно | Тестом считается метод класса, наследующего TestCase (PHPUnit 10). |
T18-L2 0.78 c | Testing: PHPUnit | In PHPUnit, setUp() runs once before all tests of the class. | «no» Пояснение: setUp() runs before each individual test method; setUpBeforeClass() is the static method that runs once before all tests.
Raw{"answer": "no", "explanation": "setUp() runs before each individual test method; setUpBeforeClass() is the static method that runs once before all tests."} | верно | setUp() — перед КАЖДЫМ тестом; один раз на класс — setUpBeforeClass(). Проверено живым счётчиком на PHPUnit 10.5. |
T18-L3 0.97 c | Testing: PHPUnit | A data provider lets a test run with exactly one set of arguments. | «no» Пояснение: A data provider in PHPUnit allows a test to run with multiple sets of arguments, not just one; each set produces a separate test execution.
Raw{"answer": "no", "explanation": "A data provider in PHPUnit allows a test to run with multiple sets of arguments, not just one; each set produces a separate test execution."} | верно | Наоборот: наборов может быть сколько угодно — тест выполняется по разу на каждый. Проверено на 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 is thrown during the test.
Raw{"answer": "expectException", "explanation": "PHPUnit's expectException() method declares an expectation that an exception of a given class is thrown during the test."} | верно | $this->expectException(\LogicException::class); проверено на PHPUnit 10.5. |
T18-L5 1.17 c | Testing: PHPUnit | In PHPUnit, a stub verifies which methods were called on it, while a mock only returns data. | «no» Пояснение: It's the opposite: a stub returns pre-programmed data, while a mock verifies which methods were called with what arguments.
Raw{"answer": "no", "explanation": "It's the opposite: a stub returns pre-programmed data, while a mock verifies which methods were called with what arguments."} | верно | Наоборот: стаб подставляет данные, мок проверяет взаимодействия (createStub/createMock); docs PHPUnit — Test Doubles. |
T18-L6 1.78 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] PHP attribute is the recommended approach, while the @dataProvider docblock annotation is deprecated.
Raw{"answer": "yes", "explanation": "In PHPUnit 10+, the #[DataProvider] PHP attribute is the recommended approach, while the @dataProvider docblock annotation is deprecated."} | верно | Аннотация ещё парсится в PHPUnit 10/11 (AnnotationParser в 10.5.66), удаление — в 12; атрибут — стандарт. |
T18-L7 0.84 c | Testing: PHPUnit | PHPUnit does not allow one test to depend on the result of another. | «no» Пояснение: PHPUnit allows test dependencies via the @depends annotation or the depends() method, enabling one test to use the return value of another.
Raw{"answer": "no", "explanation": "PHPUnit allows test dependencies via the @depends annotation or the depends() method, enabling one test to use the return value of another."} | верно | Зависимости есть: #[Depends] — зависимый тест не запустится, еслиProducer упал. |
T18-L8 0.83 c | Testing: PHPUnit | Which PHPUnit command-line option makes tests run in random order? | «--random-order» Пояснение: PHPUnit's --random-order command-line option shuffles the test execution order.
Raw{"answer": "--random-order", "explanation": "PHPUnit's --random-order command-line option shuffles the test execution order."} | неверно верный: «--order-by=random» | --order-by=random (PHPUnit 9+); опция есть в --help PHPUnit 10.5 (проектная). |
T01-L9 3.56 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 (truncation toward zero), concatenated gives the string '3-3'.
Raw{"answer": "3-3", "explanation": "intdiv(7,2) is 3 and intdiv(-7,2) is -3 (truncation toward zero), concatenated gives the string '3-3'."} | верно | intdiv truncates toward zero: intdiv(-7, 2) = -3, not -4. |
T01-L10 1.08 c | Syntax and operators | What does this code output?
```php
echo -3 ** 2;
``` | «-9» Пояснение: In PHP, the ** operator has higher precedence than the unary minus, so -3**2 is parsed as -(3**2) = -9.
Raw{"answer": -9, "explanation": "In PHP, the ** operator has higher precedence than the unary minus, so -3**2 is parsed as -(3**2) = -9."} | верно | ** is right-associative and binds tighter than unary minus: -(3²). |
T02-L9 1.01 c | Types and comparisons | What does this code output?
```php
echo '1e1' == '10' ? 'true' : 'false';
``` | «true» Пояснение: Both '1e1' and '10' are numeric strings, so PHP compares them numerically: 1e1 equals 10, making the comparison true.
Raw{"answer": "true", "explanation": "Both '1e1' and '10' are numeric strings, so PHP compares them numerically: 1e1 equals 10, making the comparison true."} | верно | Both strings are numeric — compared as numbers: 10 == 10. |
T02-L10 1.95 c | Types and comparisons | What does this code output?
```php
switch ('a') {
case 0: echo 'zero'; break;
default: echo 'other';
}
``` | «other» Пояснение: The string 'a' does not loosely equal 0, so the switch falls through to the default case which echoes 'other'.
Raw{"answer": "other", "explanation": "The string 'a' does not loosely equal 0, so the switch falls through to the default case which echoes 'other'."} | верно | PHP 8: 'a' == 0 → false (used to be true) — default fires. |
T03-L9 2.51 c | Strings | What does this code output?
```php
echo strtr('abc', ['a' => '1', 'ab' => '2']);
``` | «2c» Пояснение: strtr with an array performs a single-pass longest-match-first replacement: 'ab' (longer key) matches before 'a', so 'ab' becomes '2' and 'c' remains, giving '2c'.
Raw{"answer": "2c", "explanation": "strtr with an array performs a single-pass longest-match-first replacement: 'ab' (longer key) matches before 'a', so 'ab' becomes '2' and 'c' remains, giving '2c'."} | верно | strtr with an array prefers the longest matching key. |
T03-L10 1.22 c | Strings | What does this code output?
```php
echo '[' . substr('hello', -10) . ']';
``` | «[hello]» Пояснение: substr('hello', -10) with a negative start beyond the string length clamps to 0, returning the full string 'hello'.
Raw{"answer": "[hello]", "explanation": "substr('hello', -10) with a negative start beyond the string length clamps to 0, returning the full string 'hello'."} | верно | A negative start beyond the string is clamped to the beginning. |
T04-L9 1.48 c | Arrays | What does this code output?
```php
$a = ['k' => 1, 'n' => 2];
$b = ['k' => 9, 'm' => 3];
echo implode(',', array_keys($a + $b));
``` | «k,n,m» Пояснение: The + operator merges arrays keeping left-hand values for duplicate keys, so keys are k, n, m.
Raw{"answer": "k,n,m", "explanation": "The + operator merges arrays keeping left-hand values for duplicate keys, so keys are k, n, m."} | верно | The + operator: on duplicate string keys the left array wins. |
T04-L10 2.91 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 (values 2,1,2 → order becomes [y,1],[x,2],[z,2]), then array_column extracts index 1 giving ['y','x','z'], imploded to 'yxz'.
Raw{"answer": "yxz", "explanation": "usort sorts by index 2 (values 2,1,2 → order becomes [y,1],[x,2],[z,2]), then array_column extracts index 1 giving ['y','x','z'], imploded to 'yxz'."} | верно | Sorts are stable since 8.0: x and z keep their order on a tie. |
T05-L10 4.58 c | Functions and closures | What does this code output?
```php
function f(int $a, int $b): int
{
return $a - $b;
}
echo f(...['b' => 1, 'a' => 5]);
``` | «4» Пояснение: The spread operator unpacks the array as named arguments (a: 5, b: 1), so $a=5 and $b=1, giving 5-1=4.
Raw{"answer": 4, "explanation": "The spread operator unpacks the array as named arguments (a: 5, b: 1), so $a=5 and $b=1, giving 5-1=4."} | верно | String keys of a spread array become named arguments. |
T05-L9 14.16 c | Functions and closures | What does this code output?
```php
class P
{
private int $v = 3;
public function g(): int { return $this->v; }
}
$p = new P;
$f = $p->g(...);
$p = null;
echo $f();
``` | «3» Пояснение: The method g() is called and returns 3, which is stored in $f; setting $p to null afterward doesn't affect the already-captured value, so $f() still yields 3.
Raw{"answer": 3, "explanation": "The method g() is called and returns 3, which is stored in $f; setting $p to null afterward doesn't affect the already-captured value, so $f() still yields 3."} | верно | First-class callable syntax binds $this at creation time. |
T06-L9 1.04 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 and resolves to the class on which the method was called, which is B.
Raw{"answer": "B", "explanation": "static::class uses late static binding and resolves to the class on which the method was called, which is B."} | верно | Late static binding: static::class is the receiver's class. |
T06-L10 2.21 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 value by 2 (5*2=10), and reading the property returns the stored value 10.
Raw{"answer": 10, "explanation": "The setter multiplies the value by 2 (5*2=10), and reading the property returns the stored value 10."} | верно | Inside the set hook, $this->x writes the backing store (no recursion): 5*2. |
T07-L9 1.43 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.44 c | Interfaces, traits, enum | What does this code output?
```php
trait Counter
{
public static int $n = 0;
}
class CX { use Counter; }
class CY { use Counter; }
CX::$n = 1;
echo CY::$n;
``` | «0» Пояснение: Each class that uses a trait gets its own independent copy of static properties, so CX::$n = 1 does not affect CY::$n which remains 0.
Raw{"answer": 0, "explanation": "Each class that uses a trait gets its own independent copy of static properties, so CX::$n = 1 does not affect CY::$n which remains 0."} | верно | A trait's static property is copied into each consuming class. |
T08-L10 0.88 c | Exceptions and errors | What does this code output?
```php
function f(): int
{
try { return 1; } finally { return 2; }
}
echo f();
``` | «2» Пояснение: In PHP, a return statement in a finally block overrides any return from the try or catch blocks, so the function returns 2.
Raw{"answer": 2, "explanation": "In PHP, a return statement in a finally block overrides any return from the try or catch blocks, so the function returns 2."} | верно | A return in finally overrides the return from try. |
T08-L9 1.22 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» Пояснение: Throwing a new exception in a finally block replaces the original exception, so the LogicException('second') propagates and is caught by the outer catch block.
Raw{"answer": "second", "explanation": "Throwing a new exception in a finally block replaces the original exception, so the LogicException('second') propagates and is caught by the outer catch block."} | верно | An exception from finally replaces the in-flight one — the last thrown is caught. |
T09-L9 2.33 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 the imported alias App\Foo, while \Baz::class resolves to the global class Baz, concatenated with a pipe.
Raw{"answer": "App\\Foo|Baz", "explanation": "Baz::class resolves to the imported alias App\\Foo, while \\Baz::class resolves to the global class Baz, concatenated with a pipe."} | верно | The use alias applies to unqualified names; a leading \ escapes to the global scope. |
T09-L10 2.06 c | Namespaces and autoloading | What does this code output?
```php
namespace Ns;
class Foo {}
$c = 'Foo';
echo (class_exists($c) ? 'yes' : 'no')
. (class_exists(__NAMESPACE__ . '\\' . $c) ? 'yes' : 'no');
``` | «noyes» Пояснение: class_exists('Foo') looks for the global class \Foo (not found), while class_exists('Ns\Foo') finds the class defined in the Ns namespace.
Raw{"answer": "noyes", "explanation": "class_exists('Foo') looks for the global class \\Foo (not found), while class_exists('Ns\\Foo') finds the class defined in the Ns namespace."} | верно | Dynamic names are not resolved against the namespace — 'Foo' is the global class. |
T10-L9 1.34 c | References and scope | What does this code output?
```php
$a = [1, 2, 3];
foreach ($a as &$v) {}
$v = 99;
echo implode(',', $a);
``` | «1,2,99» Пояснение: The foreach loop with & creates a reference to the last element ($a[2]); assigning $v=99 modifies $a[2] in place, so the array becomes [1,2,99].
Raw{"answer": "1,2,99", "explanation": "The foreach loop with & creates a reference to the last element ($a[2]); assigning $v=99 modifies $a[2] in place, so the array becomes [1,2,99]."} | верно | After a by-ref foreach, $v remains a reference to the last element. |
T10-L10 1.73 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 across all instances and inherited subclasses; after three calls to inc(), $n is incremented to 3.
Raw{"answer": 3, "explanation": "Static variables in a method are shared across all instances and inherited subclasses; after three calls to inc(), $n is incremented to 3."} | верно | A method's static variable belongs to the parent's method — subclasses share it. |
T11-L9 1.48 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 after the yield, then return $x+1 evaluates to 11, which getReturn() retrieves.
Raw{"answer": 11, "explanation": "send(10) assigns $x=10 after the yield, then return $x+1 evaluates to 11, which getReturn() retrieves."} | верно | send() resumes the generator: $x = 10, return 10+1. |
T11-L10 1.79 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' in $r, which is then yielded, producing the array [1, 2, 'ok'] that implode joins into '1,2,ok'.
Raw{"answer": "1,2,ok", "explanation": "yield from inner() yields 1 and 2, captures the return value 'ok' in $r, which is then yielded, producing the array [1, 2, 'ok'] that implode joins into '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.37 c | Configuration and security | What does this code output?
```php
$hash = password_hash('x', PASSWORD_BCRYPT, ['cost' => 4]);
echo password_needs_rehash($hash, PASSWORD_BCRYPT, ['cost' => 4]) ? 'yes' : 'no';
echo password_needs_rehash($hash, PASSWORD_BCRYPT, ['cost' => 5]) ? 'yes' : 'no';
``` | «noyes» Пояснение: password_needs_rehash returns false (no) when the cost matches (4 vs 4) and true (yes) when the cost differs (4 vs 5).
Raw{"answer": "noyes", "explanation": "password_needs_rehash returns false (no) when the cost matches (4 vs 4) and true (yes) when the cost differs (4 vs 5)."} | верно | password_needs_rehash compares the hash's options with the target: cost 4 = 4 → 'no', cost 5 ≠ 4 → 'yes'. |
T12-L10 3.41 c | Configuration and security | What does this code output on PHP 8.5?
```php
echo (E_ALL & 2048) === 0 ? 'strict-out' : 'strict-in';
``` | «strict-in» Пояснение: E_ALL (32767) has bit 2048 (E_STRICT) set, so E_ALL & 2048 equals 2048, which is not === 0, making the ternary evaluate to 'strict-in'.
Raw{"answer": "strict-in", "explanation": "E_ALL (32767) has bit 2048 (E_STRICT) set, so E_ALL & 2048 equals 2048, which is not === 0, making the ternary evaluate to 'strict-in'."} | неверно верный: «strict-out» | Since PHP 8.4, E_STRICT is out of E_ALL: the 2048 bit is unset → 'strict-out' (2048 is the historical E_STRICT bit). |
T13-L9 2.14 c | Symfony | What does this code output?
```php
use Symfony\Component\HttpFoundation\Request;
$r = Request::create('/demo', 'GET', [], [], [], ['HTTP_X_TOKEN' => 'abc']);
echo $r->headers->get('X-Token') === 'abc' ? 'mapped' : 'missing';
``` | «mapped» Пояснение: Symfony's Request::create sets HTTP_X_TOKEN as a server variable, which is automatically converted to the header X-Token, so headers->get('X-Token') returns 'abc' and the strict comparison succeeds.
Raw{"answer": "mapped", "explanation": "Symfony's Request::create sets HTTP_X_TOKEN as a server variable, which is automatically converted to the header X-Token, so headers->get('X-Token') returns 'abc' and the strict comparison succeeds."} | верно | 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.0 c | Symfony | What does this code output?
```php
use Symfony\Component\EventDispatcher\EventDispatcher;
use Symfony\Contracts\EventDispatcher\Event;
$d = new EventDispatcher();
$out = '';
$d->addListener('e', function () use (&$out) { $out .= 'B'; }, 10);
$d->addListener('e', function () use (&$out) { $out .= 'A'; });
$d->addListener('e', function () use (&$out) { $out .= 'C'; }, 5);
$d->dispatch(new Event(), 'e');
echo $out;
``` | «bca» Пояснение: Symfony EventDispatcher calls listeners in descending priority order: B (10), C (5), A (0).
Raw{"answer": "BCA", "explanation": "Symfony EventDispatcher calls listeners in descending priority order: B (10), C (5), A (0)."} | верно | Listeners run by descending priority: 10 (B), 5 (C), 0 (A). |
T14-L10 2.04 c | Doctrine | Given: Doctrine ORM 3, an EntityManager on in-memory SQLite, entity User with an auto-increment primary key. The users table is empty. What does this code output?
```php
$u = new User(name: 'A');
$em->persist($u);
$em->flush();
$a = $em->find(User::class, $u->getId());
$b = $em->find(User::class, $u->getId());
echo spl_object_id($a) === spl_object_id($b) ? 'same' : 'diff';
``` | «same» Пояснение: Doctrine ORM's identity map guarantees that calling EntityManager::find() with the same ID within the same EM instance always returns the identical object reference, so $a and $b are the same instance.
Raw{"answer": "same", "explanation": "Doctrine ORM's identity map guarantees that calling EntityManager::find() with the same ID within the same EM instance always returns the identical object reference, so $a and $b are the same instance."} | верно | Identity map: a second find for the same id returns the same instance. |
T14-L9 7.71 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» Пояснение: Persisting then removing an entity before flush cancels the insertion, so after flush the users table remains empty.
Raw{"answer": 0, "explanation": "Persisting then removing an entity before flush cancels the insertion, so after flush the users table remains empty."} | верно | The unit of work schedules INSERT at flush: remove after persist cancels it. |
T15-L10 1.33 c | PostgreSQL | What does this SQL query return (PostgreSQL 17)?
```sql
CREATE TEMP TABLE t (x int);
INSERT INTO t VALUES (1), (NULL);
SELECT count(x) FROM t;
``` | «1» Пояснение: COUNT(x) counts only non-NULL values in column x; there is one row with x=1 and one with x=NULL, so the result is 1.
Raw{"answer": 1, "explanation": "COUNT(x) counts only non-NULL values in column x; there is one row with x=1 and one with x=NULL, so the result is 1."} | верно | count(column) skips NULLs; count(*) would return 2. |
T15-L9 1.69 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 a running sum (10, 30, 60), and string_agg concatenates them as text with commas.
Raw{"answer": "10,30,60", "explanation": "The window function sum(x) OVER (ORDER BY id) produces a running sum (10, 30, 60), and string_agg concatenates them as text with commas."} | верно | With ORDER BY the default window frame is running (start to current row). |
T16-L9 8.69 c | Symfony: Messenger | What does this code output?
```php
use Symfony\Component\Messenger\MessageBus;
use Symfony\Component\Messenger\Middleware\MiddlewareInterface;
use Symfony\Component\Messenger\Middleware\StackInterface;
use Symfony\Component\Messenger\Envelope;
final class Trace implements MiddlewareInterface
{
public function __construct(private string $tag) {}
public function handle(Envelope $e, StackInterface $stack): Envelope
{
echo $this->tag;
return $stack->next()->handle($e, $stack);
}
}
$bus = new MessageBus([new Trace('M1'), new Trace('M2')]);
$bus->dispatch(new Envelope(new stdClass()));
``` | «m1m2» Пояснение: Each middleware echoes its tag before delegating to the next in the stack, so M1 echoes 'M1', then M2 echoes 'M2' before the (non-existent) handler is reached.
Raw{"answer": "M1M2", "explanation": "Each middleware echoes its tag before delegating to the next in the stack, so M1 echoes 'M1', then M2 echoes 'M2' before the (non-existent) handler is reached."} | верно | The first-added middleware runs first (outermost). |
T16-L10 6.96 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;
``` | «1» Пояснение: When multiple handlers are registered for the same message class in Symfony Messenger, the HandleMessageMiddleware uses the first handler in the array (h1), which increments $n by 1.
Raw{"answer": 1, "explanation": "When multiple handlers are registered for the same message class in Symfony Messenger, the HandleMessageMiddleware uses the first handler in the array (h1), which increments $n by 1."} | неверно верный: «11» | All registered handlers of the message run: 1 + 10 = 11. |
T17-L9 1.53 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 adds a row with value 1, the second INSERT is skipped due to the unique constraint combined with ON CONFLICT DO NOTHING, so the table contains exactly 1 row.
Raw{"answer": 1, "explanation": "The first INSERT adds a row with value 1, the second INSERT is skipped due to the unique constraint combined with ON CONFLICT DO NOTHING, so the table contains exactly 1 row."} | верно | ON CONFLICT DO NOTHING skips the duplicate: one insert. |
T17-L10 1.76 c | PostgreSQL: transactions and indexes | What does this sequence of psql commands output?
```sql
BEGIN;
CREATE TEMP TABLE t (a int, UNIQUE (a) DEFERRABLE INITIALLY DEFERRED);
INSERT INTO t VALUES (1);
INSERT INTO t VALUES (1);
SELECT count(*) FROM t;
``` | «2» Пояснение: The UNIQUE constraint is DEFERRABLE INITIALLY DEFERRED, so the uniqueness check is postponed until the end of the transaction, allowing both INSERTs to succeed and count(*) to return 2.
Raw{"answer": 2, "explanation": "The UNIQUE constraint is DEFERRABLE INITIALLY DEFERRED, so the uniqueness check is postponed until the end of the transaction, allowing both INSERTs to succeed and count(*) to return 2."} | верно | DEFERRED postpones the uniqueness check to COMMIT — count sees 2 rows. |
T18-L9 2.48 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.38 c | Testing: PHPUnit | How many tests will this command run, and how many of them will fail? Answer with two comma-separated numbers (ran, failed).
```php
use PHPUnit\Framework\TestCase;
use PHPUnit\Framework\Attributes\DataProvider;
final class Calc2Test extends TestCase
{
public function prov(): array
{
return [[1], [-1]];
}
#[DataProvider('prov')]
public function test_x(int $x): void
{
$this->assertTrue($x > 0);
}
}
```
Command: `phpunit Calc2Test.php` (PHPUnit 10.5) | «2, 1» Пояснение: The data provider yields two cases ([1] and [-1]); test with x=1 passes assertTrue(1>0), test with x=-1 fails assertTrue(-1>0).
Raw{"answer": "2, 1", "explanation": "The data provider yields two cases ([1] and [-1]); test with x=1 passes assertTrue(1>0), test with x=-1 fails assertTrue(-1>0)."} | верно | 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.84 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 (--data) flag in curl causes the request to use the POST method by default.
Raw{"answer": "POST", "explanation": "The -d (--data) flag in curl causes the request to use the POST method by default."} | верно | -d/-F switches curl to POST by default. |
T19-L10 1.13 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 combined with -d causes curl to send the data as a URL query string, making it a GET request instead of the default POST.
Raw{"answer": "GET", "explanation": "The -G flag combined with -d causes curl to send the data as a URL query string, making it a GET request instead of the default POST."} | верно | -G turns -d data into the query string; the method stays GET. |
T20-L9 2.1 c | Security and OAuth | A client hits the token endpoint (RFC 6749) with a non-existent client_id. What value of the error field does the endpoint return? | «invalid_client» Пояснение: Per RFC 6749 §5.2, an unknown (non-existent) client_id causes the token endpoint to return the error value 'invalid_client'.
Raw{"answer": "invalid_client", "explanation": "Per RFC 6749 §5.2, an unknown (non-existent) client_id causes the token endpoint to return the error value 'invalid_client'."} | верно | Unknown client → invalid_client (RFC 6749 §5.2). |
T20-L10 1.04 c | Security and OAuth | OAuth 2.0: the client started the flow with response_type=token. In which part of the redirect_uri does the authorization server pass the access_token? | «fragment» Пояснение: In the OAuth 2.0 implicit flow (response_type=token), the access token is returned in the URI fragment (after #) of the redirect_uri, not in the query string.
Raw{"answer": "fragment", "explanation": "In the OAuth 2.0 implicit flow (response_type=token), the access token is returned in the URI fragment (after #) of the redirect_uri, not in the query string."} | верно | The implicit flow passes the token in the URL fragment (#) — it never reaches the server. |
T21-L9 1.38 c | Twig | What does this Twig template output?
```twig
{{ false|default(2) * 3 }}
``` | «0» Пояснение: The default filter only triggers on null, not false, so false|default(2) yields false; false * 3 equals 0.
Raw{"answer": 0, "explanation": "The default filter only triggers on null, not false, so false|default(2) yields false; false * 3 equals 0."} | неверно верный: «6» | default replaces exactly false/null/''/[] — false becomes 2, 2*3 = 6; the naive 'default is for undefined only' yields 0. |
T21-L10 2.2 c | Twig | What exception class does render() of this template throw?
```twig
{{ 'a' ~ 1 + 2 }}
``` | «a3» Пояснение: In Twig, the + operator has higher precedence than the ~ (concatenation) operator, so the expression is parsed as 'a' ~ (1 + 2), which equals 'a3'.
Raw{"answer": "a3", "explanation": "In Twig, the + operator has higher precedence than the ~ (concatenation) operator, so the expression is parsed as 'a' ~ (1 + 2), which equals 'a3'."} | неверно верный: «runtimeerror» | In Twig ~ binds tighter than +: ('a' ~ 1) + 2 → string + int → a render error (RuntimeError). |
T22-L9 2.8 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» Пояснение: Assert\NotBlank() applied to an array checks if it is non-empty; [''] has one element so it passes, resulting in 0 violations.
Raw{"answer": 0, "explanation": "Assert\\NotBlank() applied to an array checks if it is non-empty; [''] has one element so it passes, resulting in 0 violations."} | верно | NotBlank treats null, '', [] as blank — the array [''] is not blank. |
T22-L10 6.38 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);
}
``` | «logicexception» Пояснение: Calling isValid() on a Symfony form that has not been submitted throws a LogicException, which is caught and its class name is printed.
Raw{"answer": "LogicException", "explanation": "Calling isValid() on a Symfony form that has not been submitted throws a LogicException, which is caught and its class name is printed."} | верно | isValid() on a non-submitted form throws LogicException, it does not return false. |
T23-L9 1.56 c | Symfony: configuration and services | What does this code output?
```php
use Symfony\Component\DependencyInjection\ContainerBuilder;
$c = new ContainerBuilder();
$c->register('a', stdClass::class)->setPublic(true);
$c->compile();
echo spl_object_id($c->get('a')) === spl_object_id($c->get('a')) ? 'same' : 'diff';
``` | «same» Пояснение: Symfony's DI container by default shares (singleton) services, so calling get() twice returns the same object instance.
Raw{"answer": "same", "explanation": "Symfony's DI container by default shares (singleton) services, so calling get() twice returns the same object instance."} | верно | Container services are shared: two get() calls yield one instance. |
T23-L10 1.72 c | Symfony: configuration and services | What does this code output?
```php
use Symfony\Component\DependencyInjection\ContainerBuilder;
$c = new ContainerBuilder();
$c->setParameter('name', 'Bob');
$c->setParameter('greeting', 'hi %name%');
$c->setParameter('message', '%greeting%!');
$c->compile();
echo $c->getParameter('message');
``` | «hi bob!» Пояснение: Symfony's ContainerBuilder recursively resolves %param% references, so message '%greeting%!' → 'hi %name%!' → 'hi Bob!'.
Raw{"answer": "hi Bob!", "explanation": "Symfony's ContainerBuilder recursively resolves %param% references, so message '%greeting%!' → 'hi %name%!' → 'hi Bob!'."} | верно | compile() resolves %-references transitively: %greeting% → 'hi %name%' → 'hi Bob!', the answer assembles over two hops. |
T24-L9 2.21 c | Bootstrap | What is the max-width of .container in Bootstrap 5.3 at a 992px viewport? | «960px» Пояснение: In Bootstrap 5.3, at the lg breakpoint (min-width: 992px), the .container class has a max-width of 960px.
Raw{"answer": "960px", "explanation": "In Bootstrap 5.3, at the lg breakpoint (min-width: 992px), the .container class has a max-width of 960px."} | верно | 5.x container widths: 540/720/960/1140/1320 (sm–xxl); 992 → 960px. |
T24-L10 3.21 c | Bootstrap | Which utility sets the text color in Bootstrap 5.3 for `<p class="text-danger text-primary">…</p>`? Answer with the winning class name. | «text-danger» Пояснение: In Bootstrap 5.3's generated CSS, .text-danger appears later in the stylesheet than .text-primary, so with equal specificity it wins the cascade.
Raw{"answer": "text-danger", "explanation": "In Bootstrap 5.3's generated CSS, .text-danger appears later in the stylesheet than .text-primary, so with equal specificity it wins the cascade."} | верно | Specificity ties — the later rule wins: text-danger is declared after text-primary. |
T25-L9 1.6 c | Clean architecture | Layers: Domain, Application, Infrastructure. Deptrac rules: Application → Domain; Infrastructure → Domain, Application; Domain → Domain only.
How many violations will deptrac report for this class?
```php
namespace App\Domain;
use App\Application\PlaceOrder;
use App\Infrastructure\Db;
class OrderService
{
public function __construct(
private PlaceOrder $handler,
private Db $db,
) {}
}
``` | «2» Пояснение: Domain can only depend on Domain, but OrderService references both Application (PlaceOrder) and Infrastructure (Db), creating two violations.
Raw{"answer": 2, "explanation": "Domain can only depend on Domain, but OrderService references both Application (PlaceOrder) and Infrastructure (Db), creating two violations."} | верно | Domain may depend only on Domain: PlaceOrder (Application) + Db (Infrastructure) = 2. |
T25-L10 1.37 c | Clean architecture | Layers: Domain, Application, Infrastructure. Deptrac rules: Application → Domain; Infrastructure → Domain, Application; Domain → Domain only.
How many violations will deptrac report for this class?
```php
namespace App\Domain;
use App\Application\PlaceOrder;
use App\Infrastructure\Db;
class BillingService
{
public function __construct(
private PlaceOrder $handler,
private Db $db,
private \App\Infrastructure\Logger $logger,
) {}
}
``` | «3» Пояснение: The class is in the Domain layer but depends on Application (PlaceOrder) and Infrastructure (Db, Logger), giving 3 violations since Domain may only depend on Domain.
Raw{"answer": 3, "explanation": "The class is in the Domain layer but depends on Application (PlaceOrder) and Infrastructure (Db, Logger), giving 3 violations since Domain may only depend on Domain."} | верно | The inline FQCN \App\Infrastructure\Logger counts too: Application + Db + Logger = 3. |
T26-L10 0.88 c | DDD | What does this code output?
```php
final class Money
{
public function __construct(public readonly int $amount) {}
public function add(Money $o): Money
{
return new self($this->amount + $o->amount);
}
}
$a = new Money(10);
$c = $a->add(new Money(5));
echo $a->amount . ',' . $c->amount;
``` | «10,15» Пояснение: $a->amount is 10 and $c->amount is 10+5=15, concatenated with a comma gives '10,15'.
Raw{"answer": "10,15", "explanation": "$a->amount is 10 and $c->amount is 10+5=15, concatenated with a comma gives '10,15'."} | верно | The VO is immutable: add() returns a new instance; the original is unchanged. |
T26-L9 1.46 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 an exception when count is 1, so unset() is never called and the item 'a' remains in the array, making count() return 1.
Raw{"answer": 1, "explanation": "The remove() method throws an exception when count is 1, so unset() is never called and the item 'a' remains in the array, making count() return 1."} | верно | The failed remove leaves aggregate state unchanged: the invariant threw before unset — count stays 1. |
VC-L9 3.33 c | PHP 8.4–8.5 | What does this code output on PHP 8.5?
```php
class C
{
public function hi(): string { return 'hi'; }
}
echo new C()->hi();
``` | «hi» Пояснение: The code instantiates class C and calls its hi() method which returns the string 'hi', then echoes it.
Raw{"answer": "hi", "explanation": "The code instantiates class C and calls its hi() method which returns the string 'hi', then echoes it."} | верно | Since 8.4, new in a method chain works without wrapping parentheses. |
VC-L10 5.14 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» Пояснение: The first isUninitializedLazyObject check returns true (object not yet initialized), printing 'yes'; after accessing $o->v the lazy object is initialized, so the second check returns false, printing 'no'.
Raw{"answer": "yesno", "explanation": "The first isUninitializedLazyObject check returns true (object not yet initialized), printing 'yes'; after accessing $o->v the lazy object is initialized, so the second check returns false, printing 'no'."} | верно | newLazyGhost (8.4): the object stays lazy until first access — reading a property initializes it and clears the flag. |
T28-L9 1.28 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 entire Symfony Security Guard component (Symfony\Component\Security\Guard) was removed in Symfony 7.0, so by Symfony 8.1 the AbstractGuardAuthenticator class no longer exists.
Raw{"answer": "no", "explanation": "The entire Symfony Security Guard component (Symfony\\Component\\Security\\Guard) was removed in Symfony 7.0, so by Symfony 8.1 the AbstractGuardAuthenticator class no longer exists."} | верно | Guard authentication was removed in Symfony 7.0 — the class is gone in 8.1. |
T28-L10 3.34 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 has been removed (deprecated in 7.x), while AttributeClassLoader remains as its replacement.
Raw{"answer": "noyes", "explanation": "In Symfony 8.1, AnnotationClassLoader has been removed (deprecated in 7.x), while AttributeClassLoader remains as its replacement."} | верно | Annotation loaders were removed in 7.0; only attribute loaders remain (Annotation→Attribute). |