Пример запроса (первая клетка). System одинаковый во всех запросах прогона, user — свой вопрос для каждой клетки:
| Клетка | Тема | Утверждение | Ответ |
Результат | Обоснование |
T01-L1 3.47 c | Syntax and operators | Double-quoted and single-quoted strings are processed identically; the difference is only in speed. | «no» Пояснение: Double-quoted strings support variable interpolation and a full set of escape sequences, while single-quoted strings do not, so they are processed differently, not just at different speeds.
Raw{"answer": "no", "explanation": "Double-quoted strings support variable interpolation and a full set of escape sequences, while single-quoted strings do not, so they are processed differently, not just at different speeds."} | верно | В двойных кавычках работают интерполяция переменных и escape-последовательности, в одинарных — нет. |
T01-L2 1.88 c | Syntax and operators | The ?? operator follows isset semantics and raises no warnings for undefined variables. | «yes» Пояснение: The null coalescing operator (??) in PHP uses isset semantics, so it silently falls back to the right operand when the left operand is undefined or null, without raising any warnings or notices.
Raw{"answer": "yes", "explanation": "The null coalescing operator (??) in PHP uses isset semantics, so it silently falls back to the right operand when the left operand is undefined or null, without raising any warnings or notices."} | верно | ?? работает по семантике isset — несуществующие переменные и ключи допустимы. |
T01-L3 0.95 c | Syntax and operators | What will this print: echo 'a', 'b'; | «ab» Пояснение: In PHP, the echo statement accepts multiple arguments separated by commas, and it outputs them concatenated together in sequence.
Raw{"answer": "ab", "explanation": "In PHP, the echo statement accepts multiple arguments separated by commas, and it outputs them concatenated together in sequence."} | верно | echo принимает список аргументов: ab. |
T01-L4 10.2 c | Syntax and operators | print returns the value 1 and can be used inside an expression. | «yes» Пояснение: In PHP, print is a language construct that always outputs its argument and returns the value 1, which means it can be assigned or used within an expression (unlike echo, which has no return value).
Raw{"answer": "yes", "explanation": "In PHP, print is a language construct that always outputs its argument and returns the value 1, which means it can be assigned or used within an expression (unlike echo, which has no return value)."} | верно | print — выражение со значением 1, в отличие от echo, который значения не возвращает. |
T01-L5 2.37 c | Syntax and operators | The ?: (elvis) operator returns its left operand when it is falsy. | «no» Пояснение: The Elvis operator returns the left operand when it is truthy, and the right operand when it is falsy.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "The Elvis operator returns the left operand when it is truthy, and the right operand when it is falsy." ⏎ } | верно | Наоборот: $a ?: $b возвращает $a, если он истинный, иначе $b. |
T01-L6 5.8 c | Syntax and operators | In PHP 8, the concatenation operator (.) has lower precedence than addition and subtraction. | «no» Пояснение: In PHP, the concatenation operator (.) actually has HIGHER precedence than addition and subtraction, so in an expression like $a + $b . $c, the concatenation $b . $c is evaluated first.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "In PHP, the concatenation operator (.) actually has HIGHER precedence than addition and subtraction, so in an expression like $a + $b . $c, the concatenation $b . $c is evaluated first." ⏎ } | неверно верный: «yes» | С PHP 8 (RFC concat precedence) '.' имеет приоритет ниже арифметики: 'сумма: ' . 2 + 3 → 'сумма: 5' (в PHP 7 было иначе). |
T01-L7 1.83 c | Syntax and operators | The expression 2 ** 3 ** 2 in PHP evaluates as (2 ** 3) ** 2, that is, 64. | «no» Пояснение: PHP's ** operator is right-associative, so 2 ** 3 ** 2 is evaluated as 2 ** (3 ** 2) = 2 ** 9 = 512, not (2 ** 3) ** 2 = 64.
Raw{"answer": "no", "explanation": "PHP's ** operator is right-associative, so 2 ** 3 ** 2 is evaluated as 2 ** (3 ** 2) = 2 ** 9 = 512, not (2 ** 3) ** 2 = 64."} | верно | ** право-ассоциативен: 2 ** (3 ** 2) = 2 ** 9 = 512. |
T01-L8 8.01 c | Syntax and operators | What string will this print: echo 'sum: ' . 2 + 3; (PHP 8)? | «sum: 5» Пояснение: The + operator has higher precedence than the . concatenation operator, so the expression is parsed as 'sum: ' . (2 + 3), which equals 'sum: 5'.
Raw{"answer": "sum: 5", "explanation": "The + operator has higher precedence than the . concatenation operator, so the expression is parsed as 'sum: ' . (2 + 3), which equals 'sum: 5'."} | верно | Парная к verify-клетке про приоритет: 'сумма: 5'. |
T02-L1 2.47 c | Types and comparisons | With strict comparison (===), arrays are considered equal regardless of element order. | «no» Пояснение: With ===, arrays must have the same keys and values in the same order to be considered equal; element order does matter.
Raw{"answer": "no", "explanation": "With ===, arrays must have the same keys and values in the same order to be considered equal; element order does matter."} | верно | === для массивов требует совпадения и значений, и их порядка. |
T02-L2 1.93 c | Types and comparisons | The comparison 0 == false returns false because it is a strict comparison. | «no» Пояснение: The == operator is a loose (non-strict) comparison, and 0 == false actually evaluates to true because false is type-cast to 0.
Raw{"answer": "no", "explanation": "The == operator is a loose (non-strict) comparison, and 0 == false actually evaluates to true because false is type-cast to 0."} | верно | Наоборот: == — нестрогое сравнение и возвращает true; строгое — это === (0 === false → false). |
T02-L3 4.99 c | Types and comparisons | In PHP 8, the expression "abc" == 0 returns true. | «no» Пояснение: In PHP 8, when comparing a non-numeric string with a number, the number is converted to a string and a string comparison is performed, so "abc" == "0" evaluates to false.
Raw{"answer": "no", "explanation": "In PHP 8, when comparing a non-numeric string with a number, the number is converted to a string and a string comparison is performed, so \"abc\" == \"0\" evaluates to false."} | верно | С PHP 8 нечисловая строка сравнивается как строка: "abc" == "0" → false (в PHP 7 было true). |
T02-L4 1.23 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.3 c | Types and comparisons | What does the expression (int) '42abc' return? | «42» Пояснение: PHP casts a string to an integer by parsing the leading numeric prefix and ignoring any trailing non-numeric characters, so '42abc' becomes 42.
Raw{"answer": 42, "explanation": "PHP casts a string to an integer by parsing the leading numeric prefix and ignoring any trailing non-numeric characters, so '42abc' becomes 42."} | верно | Ведущая числовая часть: 42, без ошибок и warning. |
T02-L6 0.99 c | Types and comparisons | What does the expression '5' + 5 return? | «10» Пояснение: In PHP, the + operator converts both operands to numbers; '5' becomes 5 and 5 + 5 equals 10.
Raw{"answer": 10, "explanation": "In PHP, the + operator converts both operands to numbers; '5' becomes 5 and 5 + 5 equals 10."} | верно | Числовая строка приводится: int 10. |
T02-L7 1.02 c | Types and comparisons | When cast to string, false becomes "0". | «no» Пояснение: In PHP, casting false to a string results in an empty string (""), not "0".
Raw{"answer": "no", "explanation": "In PHP, casting false to a string results in an empty string (\"\"), not \"0\"."} | верно | false → "", true → "1". |
T02-L8 2.08 c | Types and comparisons | The comparison 0.1 + 0.2 === 0.3 returns false. | «yes» Пояснение: Due to floating-point precision issues, 0.1 + 0.2 equals approximately 0.30000000000000004, not exactly 0.3, so the strict equality comparison returns false.
Raw{"answer": "yes", "explanation": "Due to floating-point precision issues, 0.1 + 0.2 equals approximately 0.30000000000000004, not exactly 0.3, so the strict equality comparison returns false."} | верно | Двоичная погрешность float: 0.1 + 0.2 = 0.30000000000000004. |
T03-L1 1.64 c | Strings | strrev() correctly reverses a UTF-8 string. | «no» Пояснение: strrev() reverses a string byte-by-byte, which breaks multi-byte UTF-8 characters into invalid sequences, so it does not correctly reverse UTF-8 text.
Raw{"answer": "no", "explanation": "strrev() reverses a string byte-by-byte, which breaks multi-byte UTF-8 characters into invalid sequences, so it does not correctly reverse UTF-8 text."} | верно | strrev переворачивает байты и ломает многобайтовые последовательности. |
T03-L2 1.34 c | Strings | str_contains('Hello world', 'world') returns true. | «yes» Пояснение: The string 'Hello world' does contain the substring 'world', so str_contains() returns true.
Raw{"answer": "yes", "explanation": "The string 'Hello world' does contain the substring 'world', so str_contains() returns true."} | верно | str_contains с PHP 8.0 проверяет вхождение подстроки. |
T03-L3 1.63 c | Strings | str_pad() can pad a string on the right side only. | «no» Пояснение: str_pad() can pad on the left (STR_PAD_LEFT), right (STR_PAD_RIGHT), or both sides (STR_PAD_BOTH) depending on the $type parameter, so it is not limited to the right side only.
Raw{"answer": "no", "explanation": "str_pad() can pad on the left (STR_PAD_LEFT), right (STR_PAD_RIGHT), or both sides (STR_PAD_BOTH) depending on the $type parameter, so it is not limited to the right side only."} | верно | STR_PAD_LEFT / STR_PAD_BOTH меняют сторону дополнения. |
T03-L4 1.3 c | Strings | By default trim() strips only spaces, leaving tabs and newlines intact. | «no» Пояснение: By default trim() strips all whitespace characters (spaces, tabs, newlines, carriage returns, and null bytes), not just spaces.
Raw{"answer":"no","explanation":"By default trim() strips all whitespace characters (spaces, tabs, newlines, carriage returns, and null bytes), not just spaces."} | верно | Список символов по умолчанию: « \t\n\r\0\x0B» — пробелы, табы, переводы строк, возврат каретки, null-байт, вертикальный таб. Проверено php -r. |
T03-L5 1.46 c | Strings | How many BYTES does strlen('héllo') return for a UTF-8 string? | «6» Пояснение: In UTF-8, 'h' is 1 byte, 'é' is 2 bytes, and each of 'l', 'l', 'o' is 1 byte, totaling 6 bytes which strlen returns.
Raw{"answer": 6, "explanation": "In UTF-8, 'h' is 1 byte, 'é' is 2 bytes, and each of 'l', 'l', 'o' is 1 byte, totaling 6 bytes which strlen returns."} | верно | 6 букв по 2 байта: 12. |
T03-L6 1.68 c | Strings | What does substr('abcdef', -3) return? | «def» Пояснение: A negative start position in substr() counts from the end of the string, so -3 means starting at the third character from the end, yielding 'def'.
Raw{"answer": "def", "explanation": "A negative start position in substr() counts from the end of the string, so -3 means starting at the third character from the end, yielding 'def'."} | верно | Отрицательное смещение — с конца: def. |
T03-L7 1.12 c | Strings | ucfirst() modifies the string passed to it in place. | «no» Пояснение: In PHP, ucfirst() returns a new string with the first character uppercased and does not modify the original string, because PHP strings are value types, not references.
Raw{"answer": "no", "explanation": "In PHP, ucfirst() returns a new string with the first character uppercased and does not modify the original string, because PHP strings are value types, not references."} | верно | Строки неизменяемы; ucfirst возвращает новую строку. |
T03-L8 1.29 c | Strings | Variable interpolation works in heredoc but not in nowdoc. | «yes» Пояснение: In PHP, heredoc allows variable interpolation ($var), while nowdoc treats the content as a literal string with no interpolation.
Raw{"answer":"yes","explanation":"In PHP, heredoc allows variable interpolation ($var), while nowdoc treats the content as a literal string with no interpolation."} | верно | Nowdoc — «одинарные кавычки» в тройном синтаксисе: текст как есть. |
T04-L1 1.25 c | Arrays | The sort() function preserves the key-to-value association of the array. | «no» Пояснение: PHP's sort() resets numeric keys after sorting; use asort() instead to preserve key-to-value associations.
Raw{"answer": "no", "explanation": "PHP's sort() resets numeric keys after sorting; use asort() instead to preserve key-to-value associations."} | верно | sort перенумеровывает ключи; связь сохраняет asort. |
T04-L2 1.66 c | Arrays | The string key '5' in an array is stored as the integer 5. | «yes» Пояснение: In PHP, array keys that are strings which can be interpreted as integers (like '5') are automatically converted to their integer equivalent, so the key is stored as the integer 5.
Raw{"answer":"yes","explanation":"In PHP, array keys that are strings which can be interpreted as integers (like '5') are automatically converted to their integer equivalent, so the key is stored as the integer 5."} | верно | Каноничные десятичные строковые ключи приводятся к int. |
T04-L3 1.33 c | Arrays | The in_array() function uses strict comparison (===) by default. | «no» Пояснение: By default, in_array() uses loose comparison (==); the $strict parameter must be explicitly set to true for strict (===) comparison.
Raw{"answer": "no", "explanation": "By default, in_array() uses loose comparison (==); the $strict parameter must be explicitly set to true for strict (===) comparison."} | верно | По умолчанию сравнение нестрогое; строгое — третий аргумент true. |
T04-L4 1.18 c | Arrays | Without a callback, array_filter() removes all "empty" (falsy) elements from the array. | «yes» Пояснение: array_filter() without a callback removes all falsy values (false, 0, 0.0, "", "0", [], null) from the array.
Raw{"answer": "yes", "explanation": "array_filter() without a callback removes all falsy values (false, 0, 0.0, \"\", \"0\", [], null) from the array."} | верно | Убирает 0, "", null, false и пустые массивы. |
T04-L5 1.3 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 it re-indexes the array starting from 0 instead of preserving original keys.
Raw{"answer": "no", "explanation": "By default, the $preserve_keys parameter of array_slice() is false, so it re-indexes the array starting from 0 instead of preserving original keys."} | верно | По умолчанию ключи перенумеровываются; сохранение — preserve_keys = true. |
T04-L6 2.25 c | Arrays | What does array_slice([10, 20, 30, 40], 1, 2) return? | «[20, 30]» Пояснение: array_slice starts at offset 1 (value 20) and takes 2 elements, returning [20, 30].
Raw{"answer": "[20, 30]", "explanation": "array_slice starts at offset 1 (value 20) and takes 2 elements, returning [20, 30]."} | верно | [20,30]; ключи перенумеровываются. |
T04-L7 1.01 c | Arrays | How many elements will count(['a' => 1] + ['a' => 9, 'b' => 2]) return? | «2» Пояснение: The + operator unions arrays and keeps the left array's value for the duplicate 'a' key, resulting in two elements.
Raw{"answer": 2, "explanation": "The + operator unions arrays and keeps the left array's value for the duplicate 'a' key, resulting in two elements."} | верно | Оператор + : по ключу 'a' побеждает левый; итого 2. |
T04-L8 2.05 c | Arrays | Since PHP 8.1, the spread operator [...$a, ...$b] supports arrays with string keys. | «yes» Пояснение: PHP 8.1 extended the spread operator in array context to work with arrays that have string keys, not just integer-keyed arrays.
Raw{"answer": "yes", "explanation": "PHP 8.1 extended the spread operator in array context to work with arrays that have string keys, not just integer-keyed arrays."} | верно | В 8.0 — только числовые ключи; 8.1 снял ограничение. |
T05-L1 4.21 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 can be combined in a single function call, e.g., foo(a: 1, ...[2, 3]);
Raw{ ⏎ "answer": "no", ⏎ "explanation": "In PHP 8.0+, named arguments and argument unpacking can be combined in a single function call, e.g., foo(a: 1, ...[2, 3]);" ⏎ } | верно | Можно: f(...$args, имя: значение). Нельзя только позиционный аргумент после распаковки. |
T05-L2 2.61 c | Functions and closures | An anonymous function without use sees variables from the outer scope. | «no» Пояснение: In PHP, an anonymous function (closure) cannot access variables from the enclosing scope unless they are explicitly captured using the use keyword.
Raw{"answer": "no", "explanation": "In PHP, an anonymous function (closure) cannot access variables from the enclosing scope unless they are explicitly captured using the use keyword."} | верно | Без use внешние переменные недоступны; авто-захват только у fn. |
T05-L3 1.43 c | Functions and closures | What will func_num_args() return inside function f($a) { return func_num_args(); } when called as f(1, 2, 3)? | «3» Пояснение: func_num_args() returns the total number of arguments passed to the function, regardless of how many parameters are declared in the function signature.
Raw{"answer": 3, "explanation": "func_num_args() returns the total number of arguments passed to the function, regardless of how many parameters are declared in the function signature."} | верно | Считает переданные аргументы: 3. |
T05-L4 5.48 c | Functions and closures | The body of an arrow function fn may consist of several expressions in curly braces. | «no» Пояснение: The body of a PHP arrow function (fn) can only consist of a single expression (returned with `=>` or a single `return`/`echo` statement within curly braces), not several expressions.
Raw{"answer": "no", "explanation": "The body of a PHP arrow function (fn) can only consist of a single expression (returned with `=>` or a single `return`/`echo` statement within curly braces), not several expressions."} | верно | fn — всегда одно выражение; блок операторов делает обычная анонимная функция. |
T05-L5 13.32 c | Functions and closures | An arrow function fn captures outer variables by reference (lazily, at use time). | «yes» Пояснение: In PHP 8.1+, arrow functions implicitly close over outer variables by reference, meaning the value is read at call time (lazily) rather than being snapshotted at definition time, just like regular closures without a `use` clause.
Raw{"answer": "yes", "explanation": "In PHP 8.1+, arrow functions implicitly close over outer variables by reference, meaning the value is read at call time (lazily) rather than being snapshotted at definition time, just like regular closures without a `use` clause."} | неверно верный: «no» | fn захватывает только по значению, автоматически; по ссылке — только &$var в use у обычной функции (fn так не умеет). |
T05-L6 4.17 c | Functions and closures | A closure declared as static function () {} does not capture $this. | «yes» Пояснение: A static function closure in PHP is not bound to any object instance, so $this is not available in its scope and cannot be captured via use ($this).
Raw{"answer": "yes", "explanation": "A static function closure in PHP is not bound to any object instance, so $this is not available in its scope and cannot be captured via use ($this)."} | верно | static-замыкание отвязано от объекта: $this внутри недоступен. |
T05-L7 1.95 c | Functions and closures | What will this print: $x = 5; $f = function () use ($x) { return $x; }; $x = 7; echo $f(); | «5» Пояснение: The use ($x) keyword captures $x by value at the time the closure is created, so the closure always returns 5 regardless of the later reassignment.
Raw{"answer": 5, "explanation": "The use ($x) keyword captures $x by value at the time the closure is created, so the closure always returns 5 regardless of the later reassignment."} | верно | use захватывает по значению в момент создания: 5. |
T05-L8 1.09 c | Functions and closures | In weak typing mode (without strict_types), passing the string "5" to an int parameter is allowed. | «yes» Пояснение: In PHP weak (coercive) typing, the engine automatically casts the string "5" to the integer 5 when it is passed to an int-typed parameter.
Raw{"answer": "yes", "explanation": "In PHP weak (coercive) typing, the engine automatically casts the string \"5\" to the integer 5 when it is passed to an int-typed parameter."} | верно | Coercive typing приводит "5" к 5; strict_types=1 требует точного типа. |
T06-L1 1.16 c | OOP: classes and inheritance | PHP supports constructor property promotion: public function __construct(private int $x) {}. | «yes» Пояснение: PHP 8.0 introduced constructor property promotion, allowing parameters with visibility modifiers (private, public, protected) in the constructor to automatically create and assign class properties.
Raw{"answer": "yes", "explanation": "PHP 8.0 introduced constructor property promotion, allowing parameters with visibility modifiers (private, public, protected) in the constructor to automatically create and assign class properties."} | верно | С PHP 8.0 параметр с модификатором создаёт свойство и присваивание. |
T06-L2 0.77 c | OOP: classes and inheritance | Which keyword prevents a method from being overridden in subclasses? | «final» Пояснение: In PHP, the 'final' keyword before a method declaration prevents it from being overridden in child classes.
Raw{"answer": "final", "explanation": "In PHP, the 'final' keyword before a method declaration prevents it from being overridden in child classes."} | верно | final. |
T06-L3 0.87 c | OOP: classes and inheritance | A method declared final cannot be overridden in a subclass. | «yes» Пояснение: In PHP, the 'final' keyword on a method prevents any subclass from overriding it.
Raw{"answer": "yes", "explanation": "In PHP, the 'final' keyword on a method prevents any subclass from overriding it."} | верно | final запрещает переопределение метода и наследование класса. |
T06-L4 1.19 c | OOP: classes and inheritance | Parent properties with private visibility are accessible in a subclass. | «no» Пояснение: Private properties are only accessible within the class where they are defined and are not accessible from a subclass.
Raw{"answer": "no", "explanation": "Private properties are only accessible within the class where they are defined and are not accessible from a subclass."} | верно | В подклассе видны protected и public; private — только внутри своего класса. |
T06-L5 4.44 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» Пояснение: get_class() on an anonymous class instance returns a string like "class\0/path/to/file.php:N" where \0 is a literal NUL byte, so the part before the NUL byte is "class".
Raw{"answer":"class","explanation":"get_class() on an anonymous class instance returns a string like \"class\\0/path/to/file.php:N\" where \\0 is a literal NUL byte, so the part before the NUL byte is \"class\"."} | неверно верный: «class@anonymous» | get_class анонимного класса печатает class@anonymous\0<файл>:<строка>$n; короткая форма — часть до NUL-байта. Проверено php -r (hex). |
T06-L6 1.8 c | OOP: classes and inheritance | A private parent method is not part of the inheritance contract: a child may declare a method with the same name and any visibility. | «yes» Пояснение: Private methods are hidden from child classes in PHP, so they are not part of the inheritance contract and a child class may freely define a method with the same name using any visibility.
Raw{"answer":"yes","explanation":"Private methods are hidden from child classes in PHP, so they are not part of the inheritance contract and a child class may freely define a method with the same name using any visibility."} | верно | private-члены не наследуются — правила совместимости подписей не действуют. |
T06-L7 5.24 c | OOP: classes and inheritance | The magic method __get() is called only for non-existent properties. | «no» Пояснение: The __get() magic method is also called for inaccessible properties (e.g., private or protected properties accessed from outside the class), not only for non-existent ones.
Raw{"answer": "no", "explanation": "The __get() magic method is also called for inaccessible properties (e.g., private or protected properties accessed from outside the class), not only for non-existent ones."} | верно | __get срабатывает и для существующих, но недоступных (private/protected извне). |
T06-L8 1.86 c | OOP: classes and inheritance | What does reassigning a readonly property throw — Exception or Error? | «error» Пояснение: In PHP 8.1+, reassigning a readonly property throws an Error (not an Exception).
Raw{"answer":"Error","explanation":"In PHP 8.1+, reassigning a readonly property throws an Error (not an Exception)."} | верно | Error (readonly с 8.1); оговорка: в __clone() переинициализация допустима (8.3+). |
T07-L1 2.01 c | Interfaces, traits, enum | An interface can declare constants. | «yes» Пояснение: In PHP, interfaces can declare constants (e.g., `const MY_CONST = 42;`), which are implicitly public and can be referenced via the interface name or an implementing class.
Raw{"answer": "yes", "explanation": "In PHP, interfaces can declare constants (e.g., `const MY_CONST = 42;`), which are implicitly public and can be referenced via the interface name or an implementing class."} | верно | Константы интерфейса наследуются реализациями. |
T07-L2 0.91 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 a given object is an instance of a specified class or implements a specified interface.
Raw{"answer": "instanceof", "explanation": "The instanceof operator in PHP checks whether a given object is an instance of a specified class or implements a specified interface."} | верно | instanceof. |
T07-L3 2.07 c | Interfaces, traits, enum | An interface can declare static methods. | «yes» Пояснение: In PHP, interfaces can declare static methods, including abstract static methods (since PHP 5.5) and concrete static methods (since PHP 8.4).
Raw{"answer": "yes", "explanation": "In PHP, interfaces can declare static methods, including abstract static methods (since PHP 5.5) and concrete static methods (since PHP 8.4)."} | верно | Реализация обязана дать статический метод с той же сигнатурой. |
T07-L4 2.23 c | Interfaces, traits, enum | The instanceof operator only checks class inheritance: it ignores interfaces. | «no» Пояснение: The instanceof operator also returns true when the specified type is an interface that the object implements, so it is not limited to class inheritance.
Raw{"answer": "no", "explanation": "The instanceof operator also returns true when the specified type is an interface that the object implements, so it is not limited to class inheritance."} | верно | instanceof возвращает true и для интерфейсов объекта. |
T07-L5 1.3 c | Interfaces, traits, enum | An interface method may have a default implementation, like a trait method. | «no» Пояснение: In PHP, interface methods must be abstract (declare without a body) and cannot have default implementations; only traits can provide concrete method bodies.
Raw{"answer":"no","explanation":"In PHP, interface methods must be abstract (declare without a body) and cannot have default implementations; only traits can provide concrete method bodies."} | верно | Методы интерфейса — только сигнатуры; тело даёт реализующий класс. |
T07-L6 2.39 c | Interfaces, traits, enum | An abstract method in an abstract class may have protected visibility. | «yes» Пояснение: In PHP, abstract methods can be declared with either public or protected visibility, so a protected abstract method is perfectly valid.
Raw{"answer": "yes", "explanation": "In PHP, abstract methods can be declared with either public or protected visibility, so a protected abstract method is perfectly valid."} | верно | В абстрактном классе — любая видимость; в интерфейсе — только public. |
T07-L7 1.27 c | Interfaces, traits, enum | How many elements will Foo::cases() return for enum Foo { case A; case B; case C; }? | «3» Пояснение: The cases() class method returns all enum cases, and Foo has three cases (A, B, C).
Raw{"answer": 3, "explanation": "The cases() class method returns all enum cases, and Foo has three cases (A, B, C)."} | верно | Статический метод cases(): 3. |
T07-L8 1.1 c | Interfaces, traits, enum | A trait can declare constants. | «yes» Пояснение: Traits in PHP have supported constant declarations since PHP 5.3, allowing constants to be defined within the trait and accessed by classes that use it.
Raw{"answer": "yes", "explanation": "Traits in PHP have supported constant declarations since PHP 5.3, allowing constants to be defined within the trait and accessed by classes that use it."} | верно | С PHP 8.2 трейты могут объявлять константы (RFC constants_in_traits); до 8.2 — нет. |
T08-L1 0.93 c | Exceptions and errors | The Throwable interface is a common ancestor of both Exception and Error. | «yes» Пояснение: In PHP, both Exception and Error classes extend the abstract Throwable class, making it their common ancestor.
Raw{"answer": "yes", "explanation": "In PHP, both Exception and Error classes extend the abstract Throwable class, making it their common ancestor."} | верно | Иерархия с PHP 7: Throwable → Exception и Throwable → Error. |
T08-L2 1.92 c | Exceptions and errors | A catch (Exception $e) block will also catch TypeError, because TypeError ultimately inherits from Exception. | «no» Пояснение: In PHP, TypeError inherits from Error, and Error and Exception are separate branches under Throwable, so catching Exception will not catch TypeError.
Raw{"answer":"no","explanation":"In PHP, TypeError inherits from Error, and Error and Exception are separate branches under Throwable, so catching Exception will not catch TypeError."} | верно | TypeError наследуется от Error; catch (Exception) его не ловит. |
T08-L3 1.66 c | Exceptions and errors | The @ operator suppresses exceptions too. | «no» Пояснение: The @ operator in PHP only suppresses errors, warnings, and notices, not exceptions, which are handled separately via try/catch/throw.
Raw{"answer": "no", "explanation": "The @ operator in PHP only suppresses errors, warnings, and notices, not exceptions, which are handled separately via try/catch/throw."} | верно | @ глушит диагностику (warnings/notices), исключения не перехватывает. |
T08-L4 3.92 c | Exceptions and errors | What error class does intdiv(5, 0) throw? | «divisionbyzeroerror» Пояснение: intdiv(5, 0) throws a DivisionByZeroError because the divisor is zero.
Raw{"answer": "DivisionByZeroError", "explanation": "intdiv(5, 0) throws a DivisionByZeroError because the divisor is zero."} | верно | DivisionByZeroError (иерархия Error, не Exception); php-грейдер объективен. |
T08-L5 1.5 c | Exceptions and errors | The finally block runs only if the exception was caught by a catch block. | «no» Пояснение: The finally block executes regardless of whether an exception is caught, uncaught, or not thrown at all.
Raw{"answer": "no", "explanation": "The finally block executes regardless of whether an exception is caught, uncaught, or not thrown at all."} | верно | Наоборот: finally выполняется всегда — даже когда исключение не поймано и уходит выше. Проверено php -r. |
T08-L6 3.84 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 overrides the normal flow or the exception handled in the try/catch block and propagates outward, so it does have an effect.
Raw{"answer": "no", "explanation": "An exception thrown in a finally block overrides the normal flow or the exception handled in the try/catch block and propagates outward, so it does have an effect."} | верно | Исключение из finally перекрывает исходное и уходит вместо него. |
T08-L7 1.26 c | Exceptions and errors | What does the expression (bool) new Exception('x') return? | «yes» Пояснение: In PHP, casting any object to boolean always results in true, because objects are inherently truthy.
Raw{"answer": "yes", "explanation": "In PHP, casting any object to boolean always results in true, because objects are inherently truthy."} | верно | Любой объект при приведении к bool — true. Формы ответа: true или да. |
T08-L8 4.13 c | Exceptions and errors | Functions registered via register_shutdown_function() run when exit is called. | «yes» Пояснение: According to the PHP documentation, functions registered with register_shutdown_function() are executed when the script terminates, including when exit() is called.
Raw{"answer": "yes", "explanation": "According to the PHP documentation, functions registered with register_shutdown_function() are executed when the script terminates, including when exit() is called."} | верно | exit завершает скрипт, но shutdown-функции отрабатывают. |
T09-L1 1.4 c | Namespaces and autoloading | The use App\Service\Mailer; statement itself loads the class file. | «no» Пояснение: The 'use' statement in PHP is a compile-time alias/namespace import; it does not load the class file. The class file is loaded at runtime via the autoloader when the class is actually referenced or instantiated.
Raw{"answer": "no", "explanation": "The 'use' statement in PHP is a compile-time alias/namespace import; it does not load the class file. The class file is loaded at runtime via the autoloader when the class is actually referenced or instantiated."} | верно | use — псевдоним на этапе компиляции; файл грузит автозагрузчик при первом обращении. |
T09-L2 9.09 c | Namespaces and autoloading | What follows use to import a function (not a class): the word function or const? | «neither» Пояснение: In PHP, to import a function from a namespace you simply write `use Namespace\function_name;` without the words "function" or "const"; the `const` keyword is reserved for importing constants.
Raw{"answer": "neither", "explanation": "In PHP, to import a function from a namespace you simply write `use Namespace\\function_name;` without the words \"function\" or \"const\"; the `const` keyword is reserved for importing constants."} | неверно верный: «function» | use function ...; (и use const для констант). |
T09-L3 1.65 c | Namespaces and autoloading | Into which file (path from src/) does the PSR-4 mapping "App\ → src/" place the class App\Controller\Api\UserController? | «controller/api/usercontroller.php» Пояснение: PSR-4 strips the mapped namespace 'App\' leaving 'Controller\Api\UserController', which converts to the directory path 'Controller/Api/UserController.php' under the base path 'src/.'
Raw{"answer": "Controller/Api/UserController.php", "explanation": "PSR-4 strips the mapped namespace 'App\\' leaving 'Controller\\Api\\UserController', which converts to the directory path 'Controller/Api/UserController.php' under the base path 'src/.'"} | верно | Остаток имени после префикса, \ → /. |
T09-L4 1.02 c | Namespaces and autoloading | Including vendor/autoload.php registers autoloaders via spl_autoload_register(). | «yes» Пояснение: Including vendor/autoload.php calls spl_autoload_register() to register Composer's autoloaders for resolving classes.
Raw{"answer": "yes", "explanation": "Including vendor/autoload.php calls spl_autoload_register() to register Composer's autoloaders for resolving classes."} | верно | Composer ставит автозагрузчик именно на spl_autoload_register. |
T09-L5 1.24 c | Namespaces and autoloading | The magic constant __NAMESPACE__ contains the name of the current namespace. | «yes» Пояснение: __NAMESPACE__ is a PHP magic constant that evaluates to the name of the namespace it is used in (or the global namespace, which is represented as an empty string).
Raw{"answer": "yes", "explanation": "__NAMESPACE__ is a PHP magic constant that evaluates to the name of the namespace it is used in (or the global namespace, which is represented as an empty string)."} | верно | В корневом пространстве — пустая строка. |
T09-L6 2.07 c | Namespaces and autoloading | An unqualified class name (without a leading \) in new is resolved from the global root. | «no» Пояснение: An unqualified class name in `new` is first resolved in the current namespace (prefixed by it); only if not found there does PHP fall back to the global root namespace.
Raw{"answer": "no", "explanation": "An unqualified class name in `new` is first resolved in the current namespace (prefixed by it); only if not found there does PHP fall back to the global root namespace."} | верно | Резолвится относительно текущего namespace (с учётом импортов). |
T09-L7 1.93 c | Namespaces and autoloading | With the PSR-4 mapping "App\ → src/", the class App\Model\User lives in the file src/Model/User.php. | «yes» Пояснение: Under PSR-4, the namespace App\Model\User maps to src/Model/User.php by stripping the root namespace 'App\' and converting the remaining namespace components and class name into directory/file paths.
Raw{"answer": "yes", "explanation": "Under PSR-4, the namespace App\\Model\\User maps to src/Model/User.php by stripping the root namespace 'App\\' and converting the remaining namespace components and class name into directory/file paths."} | верно | Остаток имени после префикса переносится в путь как есть. |
T09-L8 3.02 c | Namespaces and autoloading | A use statement may be written inside a function body — the import then applies to that function only. | «no» Пояснение: In PHP, a `use` statement for importing a class or interface must be placed at the top level of a file or within a namespace; it cannot be written inside a function body.
Raw{"answer": "no", "explanation": "In PHP, a `use` statement for importing a class or interface must be placed at the top level of a file or within a namespace; it cannot be written inside a function body."} | верно | use внутри тела функции — parse error; импорты файловые и компиляционные. |
T10-L1 1.75 c | References and scope | Arrays are copied on assignment rather than passed by reference. | «yes» Пояснение: In PHP, array assignment by default creates a copy of the array (using copy-on-write optimization), so modifying one array does not affect the other unless an explicit reference (`&`) is used.
Raw{"answer":"yes","explanation":"In PHP, array assignment by default creates a copy of the array (using copy-on-write optimization), so modifying one array does not affect the other unless an explicit reference (`&`) is used."} | верно | Присваивание массива — копия (в движке — copy-on-write). |
T10-L2 1.65 c | References and scope | What will this print: $a = [1, 2]; $b = $a; $b[] = 3; echo count($a); | «2» Пояснение: In PHP, arrays are value types, so $b = $a creates a copy; modifying $b with $b[] = 3 does not affect $a, which still contains 2 elements.
Raw{"answer": 2, "explanation": "In PHP, arrays are value types, so $b = $a creates a copy; modifying $b with $b[] = 3 does not affect $a, which still contains 2 elements."} | верно | Присваивание — копия: в $a по-прежнему 2 элемента. |
T10-L3 2.35 c | References and scope | Inside a function, user-defined global variables are inaccessible without global, $GLOBALS, or passing them as parameters. | «yes» Пояснение: In PHP, variables defined in the global scope are not automatically visible inside a function's local scope, so you must use the global keyword, $GLOBALS, or pass them as parameters to access them.
Raw{"answer": "yes", "explanation": "In PHP, variables defined in the global scope are not automatically visible inside a function's local scope, so you must use the global keyword, $GLOBALS, or pass them as parameters to access them."} | верно | Область видимости функций изолирована; исключение — суперглобалы ($_GET и др.). |
T10-L4 1.8 c | References and scope | unset($GLOBALS['x']) inside a function removes the global variable only for that function. | «no» Пояснение: $GLOBALS is a reference to the global scope, so unset($GLOBALS['x']) permanently removes the variable from the global scope for the rest of the script, not just within that function.
Raw{"answer": "no", "explanation": "$GLOBALS is a reference to the global scope, so unset($GLOBALS['x']) permanently removes the variable from the global scope for the rest of the script, not just within that function."} | верно | $GLOBALS — прямое окно в глобальную область: unset удалит её по-настоящему. |
T10-L5 1.06 c | References and scope | What will this print: function inc(&$x) { $x++; } $n = 5; inc($n); echo $n; | «6» Пояснение: The function inc() receives $n by reference, so the increment inside the function also modifies the original variable $n from 5 to 6.
Raw{"answer": 6, "explanation": "The function inc() receives $n by reference, so the increment inside the function also modifies the original variable $n from 5 to 6."} | верно | Ссылка меняет оригинал: 6. |
T10-L6 13.75 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, a by-value foreach does not make a complete snapshot of the array; it reads from the live array during iteration, so modifications to the array (e.g., changing unvisited elements or appending) are visible in the same pass.
Raw{"answer": "yes", "explanation": "In PHP, a by-value foreach does not make a complete snapshot of the array; it reads from the live array during iteration, so modifications to the array (e.g., changing unvisited elements or appending) are visible in the same pass."} | неверно верный: «no» | По значению foreach итерирует копию-снимок. |
T10-L7 1.1 c | References and scope | A static property belongs to each instance separately: changes in one object are not visible in others. | «no» Пояснение: Static properties belong to the class itself and are shared among all instances; a change made through any instance is visible to every other instance of that class.
Raw{"answer": "no", "explanation": "Static properties belong to the class itself and are shared among all instances; a change made through any instance is visible to every other instance of that class."} | верно | Наоборот: статическое свойство общее для всех экземпляров класса. Проверено php -r. |
T10-L8 2.21 c | References and scope | An array can have a boolean key true, and it will be stored as bool. | «no» Пояснение: PHP arrays can only have integer or string keys; a boolean key like true is converted to the integer 1, not stored as a boolean.
Raw{"answer":"no","explanation":"PHP arrays can only have integer or string keys; a boolean key like true is converted to the integer 1, not stored as a boolean."} | верно | Булев ключ приводится к int: true → 1, false → 0. |
T11-L1 8.42 c | Generators, iterators, SPL | Inside a generator, return with a value can be used, and it becomes available via $gen->getReturn(). | «no» Пояснение: While `return value;` can indeed be used inside a PHP generator to stop it, the Generator object does not have a `getReturn()` method to access that returned value.
Raw{"answer":"no","explanation":"While `return value;` can indeed be used inside a PHP generator to stop it, the Generator object does not have a `getReturn()` method to access that returned value."} | неверно верный: «yes» | return-значение генератора доступно через getReturn() после прохода. |
T11-L2 1.14 c | Generators, iterators, SPL | A fully consumed generator can be rewound with rewind() and traversed again. | «yes» Пояснение: PHP generators are rewindable; once exhausted, calling rewind() resets them so they can be traversed again.
Raw{"answer": "yes", "explanation": "PHP generators are rewindable; once exhausted, calling rewind() resets them so they can be traversed again."} | неверно верный: «no» | Генератор одноразовый: rewind после начала итерации бросает Exception. |
T11-L3 1.12 c | Generators, iterators, SPL | The yield from construct delegates traversal to another generator or iterable. | «yes» Пояснение: The yield from construct in PHP delegates traversal to another generator or Traversable object, forwarding its values to the caller.
Raw{"answer": "yes", "explanation": "The yield from construct in PHP delegates traversal to another generator or Traversable object, forwarding its values to the caller."} | верно | yield from проксирует значения, ключи и return-значение внутреннего генератора. |
T11-L4 1.84 c | Generators, iterators, SPL | What does get_class(g()) return for function g() { yield 1; }? | «generator» Пояснение: g() is a generator function, so calling g() returns a Generator object, and get_class() returns its class name string.
Raw{"answer":"Generator","explanation":"g() is a generator function, so calling g() returns a Generator object, and get_class() returns its class name string."} | верно | Функция с yield возвращает Generator. |
T11-L5 2.02 c | Generators, iterators, SPL | How many elements will count(iterator_to_array((function () { yield from [1, 2, 3]; })())) return? | «3» Пояснение: The anonymous generator yields the three elements of [1, 2, 3] via yield from, and iterator_to_array collects all three into an array, so count returns 3.
Raw{"answer": 3, "explanation": "The anonymous generator yields the three elements of [1, 2, 3] via yield from, and iterator_to_array collects all three into an array, so count returns 3."} | верно | yield from делегирует все 3 элемента. |
T11-L6 1.01 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; a FIFO queue in PHP is implemented by the SplQueue class.
Raw{"answer": "no", "explanation": "SplStack implements a LIFO (Last In, First Out) stack, not a FIFO queue; a FIFO queue in PHP is implemented by the SplQueue class."} | верно | SplStack — стек LIFO; очередь FIFO — SplQueue. |
T11-L7 0.98 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 provides Iterator interface methods (current, next, key, valid, rewind) to traverse it.
Raw{"answer": "yes", "explanation": "ArrayIterator is a built-in PHP class that wraps an array and provides Iterator interface methods (current, next, key, valid, rewind) to traverse it."} | верно | Объектная обёртка над массивом. |
T11-L8 1.34 c | Generators, iterators, SPL | An ArrayObject instance cannot be traversed with foreach. | «no» Пояснение: ArrayObject implements the Iterator interface, so it can be directly traversed with foreach.
Raw{"answer": "no", "explanation": "ArrayObject implements the Iterator interface, so it can be directly traversed with foreach."} | верно | ArrayObject реализует IteratorAggregate — foreach по нему работает. |
T12-L1 1.54 c | Configuration and security | password_hash() generates a salt automatically — passing one separately is not needed. | «yes» Пояснение: password_hash() has no salt parameter; it generates and embeds the salt internally in the returned hash string automatically.
Raw{"answer": "yes", "explanation": "password_hash() has no salt parameter; it generates and embeds the salt internally in the returned hash string automatically."} | верно | Соль встраивается в строку результата; параметр salt устарел. |
T12-L2 2.2 c | Configuration and security | In PHP 8, PASSWORD_DEFAULT is md5 with an automatically added salt. | «no» Пояснение: PASSWORD_DEFAULT in PHP 8 is set to 'argon2i' (falling back to 'bcrypt' if unavailable), not md5.
Raw{"answer":"no","explanation":"PASSWORD_DEFAULT in PHP 8 is set to 'argon2i' (falling back to 'bcrypt' if unavailable), not md5."} | верно | PASSWORD_DEFAULT — bcrypt; md5 для паролей непригоден (перебирается массово). |
T12-L3 1.87 c | Configuration and security | What does password_verify('secret', password_hash('secret', PASSWORD_DEFAULT)) return? | «yes» Пояснение: password_verify returns true (boolean) when the password matches the provided hash, and since 'secret' is the password used to generate the hash, it matches.
Raw{"answer": "yes", "explanation": "password_verify returns true (boolean) when the password matches the provided hash, and since 'secret' is the password used to generate the hash, it matches."} | верно | Соль и хеш в одной строке: true (форма ответа: true или да). |
T12-L4 1.06 c | Configuration and security | strip_tags() protects against SQL injection. | «no» Пояснение: strip_tags() removes HTML/XML tags to prevent XSS attacks, not SQL injection; SQL injection is mitigated with prepared statements or parameterized queries.
Raw{"answer": "no", "explanation": "strip_tags() removes HTML/XML tags to prevent XSS attacks, not SQL injection; SQL injection is mitigated with prepared statements or parameterized queries."} | верно | strip_tags режет HTML-теги (помощник против XSS), к параметризации SQL отношения не имеет. |
T12-L5 1.54 c | Configuration and security | session_regenerate_id() is used to protect against session fixation upon user login. | «yes» Пояснение: session_regenerate_id() generates a new session ID after login, invalidating the previous one and preventing an attacker from using a pre-set session ID to hijack the authenticated session.
Raw{"answer": "yes", "explanation": "session_regenerate_id() generates a new session ID after login, invalidating the previous one and preventing an attacker from using a pre-set session ID to hijack the authenticated session."} | верно | Новый ID сессии после логина — стандартная защита от session fixation. |
T12-L6 1.2 c | Configuration and security | Which built-in function returns the SAPI name (e.g., cli)? | «php_sapi_name» Пояснение: The php_sapi_name() function returns the name of the SAPI (Server API) that was used to load PHP, such as 'cli' for command-line execution.
Raw{"answer": "php_sapi_name", "explanation": "The php_sapi_name() function returns the name of the SAPI (Server API) that was used to load PHP, such as 'cli' for command-line execution."} | верно | php_sapi_name(). |
T12-L7 2.26 c | Configuration and security | session_destroy() deletes session data on the server but not the cookie in the user's browser. | «yes» Пояснение: session_destroy() only removes the server-side session data; the PHPSESSID cookie remains in the browser and must be deleted separately (e.g., with setcookie()).
Raw{"answer": "yes", "explanation": "session_destroy() only removes the server-side session data; the PHPSESSID cookie remains in the browser and must be deleted separately (e.g., with setcookie())."} | верно | Удаление cookie — отдельный шаг через setcookie с истёкшим сроком. |
T12-L8 1.03 c | Configuration and security | Without calling session_start(), the $_SESSION array is automatically populated with session data. | «no» Пояснение: The $_SESSION superglobal array is only available after session_start() has been called; without it, the array is not populated.
Raw{"answer": "no", "explanation": "The $_SESSION superglobal array is only available after session_start() has been called; without it, the array is not populated."} | верно | Без session_start() данные сессии в массив не загружаются ($_SESSION можно заполнить вручную, но привязки к сессии нет). |
VC-L1 3.53 c | PHP 8.4–8.5 | In which PHP version was the array_find() function introduced? | «never» Пояснение: array_find() is not a built-in PHP function; it was never introduced in any PHP version.
Raw{"answer": "never", "explanation": "array_find() is not a built-in PHP function; it was never introduced in any PHP version."} | неверно верный: «8.4» | PHP 8.4 (RFC array_find). |
VC-L2 4.55 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 (get/set), allowing get and set methods to be declared within a class alongside a property without needing __get__/__set__.
Raw{"answer": "yes", "explanation": "PHP 8.4 introduced property hooks (get/set), allowing get and set methods to be declared within a class alongside a property without needing __get__/__set__."} | верно | Property hooks — PHP 8.4 (ноябрь 2024). |
VC-L3 1.38 c | PHP 8.4–8.5 | Asymmetric visibility (public private(set) string $name) appeared in PHP 8.4. | «no» Пояснение: Asymmetric visibility (e.g., public private(set) string $name) was introduced in PHP 8.1, not PHP 8.4.
Raw{"answer": "no", "explanation": "Asymmetric visibility (e.g., public private(set) string $name) was introduced in PHP 8.1, not PHP 8.4."} | неверно верный: «yes» | Asymmetric visibility v2 — PHP 8.4. |
VC-L4 2.92 c | PHP 8.4–8.5 | In which PHP version was the #[\NoDiscard] attribute introduced? Answer with the version number. | «8.2» Пояснение: The #[\NoDiscard] attribute was introduced in PHP 8.2 to inform the compiler that a return value must not be discarded.
Raw{"answer": "8.2", "explanation": "The #[\\NoDiscard] attribute was introduced in PHP 8.2 to inform the compiler that a return value must not be discarded."} | неверно верный: «8.5» | #[\NoDiscard] — PHP 8.5 (marking return values as important). |
VC-L5 4.38 c | PHP 8.4–8.5 | In which PHP version did the pipe operator |> first appear? Answer with the version number. | «n/a» Пояснение: PHP has never had a pipe operator |>; the bitwise OR operator | has existed since PHP 3.0, but there is no |> pipe operator in any PHP version.
Raw{"answer": "N/A", "explanation": "PHP has never had a pipe operator |>; the bitwise OR operator | has existed since PHP 3.0, but there is no |> pipe operator in any PHP version."} | неверно верный: «8.5» | Pipe operator — PHP 8.5 (2025). |
VC-L6 5.55 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]) does not exist in any PHP version; PHP's clone has always been used as a simple language construct (clone $obj;).
Raw{"answer": "no", "explanation": "The clone-with syntax clone($obj, ['x' => 1]) does not exist in any PHP version; PHP's clone has always been used as a simple language construct (clone $obj;)."} | неверно верный: «8.5» | Clone with v2 — PHP 8.5. |
VC-L7 3.93 c | PHP 8.4–8.5 | In which PHP version were the array_first() and array_last() functions introduced? | «no» Пояснение: array_first() and array_last() are not built-in PHP functions; they were never introduced in any PHP version.
Raw{"answer": "no", "explanation": "array_first() and array_last() are not built-in PHP functions; they were never introduced in any PHP version."} | неверно верный: «8.5» | PHP 8.5. |
VC-L8 8.77 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» Пояснение: RFC Partial Function Application v2 was adopted for PHP 9.0.
Raw{"answer": "9.0", "explanation": "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 2.1 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.1» Пояснение: The clamp() function, as defined by the clamp_v2 RFC, was implemented in PHP 8.1.
Raw{"answer": "8.1", "explanation": "The clamp() function, as defined by the clamp_v2 RFC, was implemented in PHP 8.1."} | неверно верный: «8.6» | По данным владельца (wiki.php.net/rfc): clamp_v2 — 8.6; clamp() в 8.5.11 отсутствует (косвенное подтверждение). Дата-якорь делает клетку монотонной. |
VF-L2 3.32 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 known 'RFC Context Managers v2' in PHP's RFC process; this appears to be a fabricated RFC name.
Raw{"answer": "no", "explanation": "There is no known 'RFC Context Managers v2' in PHP's RFC process; this appears to be a fabricated RFC name."} | верно | На 06.11.2026 — в обсуждении (создан 2026-10-23); не принят. |
VF-L3 2.2 c | PHP: 8.6+ and the future | RFC Bound-Erased Generic Types (generics) was declined in 2026. | «no» Пояснение: No such RFC called 'Bound-Erased Generic Types' was submitted or declined in 2026 for PHP; PHP has never pursued a generics system in this form.
Raw{"answer": "no", "explanation": "No such RFC called 'Bound-Erased Generic Types' was submitted or declined in 2026 for PHP; PHP has never pursued a generics system in this form."} | неверно верный: «yes» | Голосование завершилось 2026-06-28: отклонён (wiki.php.net/rfc). |
VF-L4 4.28 c | PHP: 8.6+ and the future | As of 2026-11-07, the RFC enabling multithreading (ZTS) by default has already been accepted in PHP. | «no» Пояснение: As of 2026, ZTS (Zend Thread Safety) remains an optional build option in PHP rather than the default, and no accepted RFC has made it the default due to the extensive ecosystem of extensions that would need ZTS compatibility.
Raw{"answer": "no", "explanation": "As of 2026, ZTS (Zend Thread Safety) remains an optional build option in PHP rather than the default, and no accepted RFC has made it the default due to the extensive ecosystem of extensions that would need ZTS compatibility."} | верно | Такого принятого RFC нет на дату якоря; якорь делает клетку монотонной — при принятии RFC позже клетка не перевернётся. |
VF-L5 1.88 c | PHP: 8.6+ and the future | As of PHP 8.5, generics (parameterized types) are still absent. | «yes» Пояснение: PHP 8.5 (released November 2024) introduced property hooks and readonly property enhancements but did not add generics/parameterized types, which remain absent from the language.
Raw{"answer": "yes", "explanation": "PHP 8.5 (released November 2024) introduced property hooks and readonly property enhancements but did not add generics/parameterized types, which remain absent from the language."} | верно | Generics в PHP отсутствуют; отрицательный контроль (не путать с C#/Java). |
VF-L6 9.81 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» Пояснение: This aligns with PHP's typical ~6-month minor release cycle, with 8.5 having been GA'd in late 2025 and 8.6 scheduled for late November 2026, making the statement true.
Raw{"answer": "yes", "explanation": "This aligns with PHP's typical ~6-month minor release cycle, with 8.5 having been GA'd in late 2025 and 8.6 scheduled for late November 2026, making the statement true."} | верно | 8.5 — релиз осени 2025; 8.6 GA 19.11.2026 (wiki.php.net/todo/php86). Дата снимка — 06.11.2026. |
VF-L7 2.06 c | PHP: 8.6+ and the future | The PHP 6 branch never shipped: after PHP 5.6 came PHP 7.0 directly. | «yes» Пояснение: PHP 6 was never released as a stable version; the next major release after PHP 5.6 was PHP 7.0 in 2015.
Raw{"answer": "yes", "explanation": "PHP 6 was never released as a stable version; the next major release after PHP 5.6 was PHP 7.0 in 2015."} | верно | Исторический факт: ветка 6 не была релизнута. |
VF-L8 5.2 c | PHP: 8.6+ and the future | The RFC adding the #[\Deprecated] attribute to the core was adopted. | «no» Пояснение: The #[\Deprecated] attribute RFC was not adopted for any PHP release; it went through multiple cycles of discussion and revision but was not finalized.
Raw{"answer": "no", "explanation": "The #[\\Deprecated] attribute RFC was not adopted for any PHP release; it went through multiple cycles of discussion and revision but was not finalized."} | неверно верный: «yes» | #[\Deprecated] — принят, реализован в PHP 8.4. |
T25-L1 2.22 c | Clean architecture | The dependency rule of clean and onion architecture: inner layers know nothing about outer ones — dependencies point toward the center. | «yes» Пояснение: In clean/onion architecture, the dependency rule states that all dependencies point inward toward the center, so inner layers have no knowledge of or dependency on outer layers.
Raw{"answer": "yes", "explanation": "In clean/onion architecture, the dependency rule states that all dependencies point inward toward the center, so inner layers have no knowledge of or dependency on outer layers."} | верно | Чистая (Robert C. Martin), луковичная (Jeffrey Palermo) и гексагональная (ports & adapters) — варианты одной идеи: зависимости направлены внутрь, к домену. Слоями в проекте следит deptrac. |
T25-L2 1.76 c | Clean architecture | Domain entities import neither Doctrine nor Symfony — only the language and, possibly, the standard library. | «yes» Пояснение: In DDD, domain entities must be framework-agnostic and pure, depending only on the language and standard library to keep the domain layer isolated from infrastructure like Doctrine or Symfony.
Raw{"answer": "yes", "explanation": "In DDD, domain entities must be framework-agnostic and pure, depending only on the language and standard library to keep the domain layer isolated from infrastructure like Doctrine or Symfony."} | верно | Изоляция домена от инфраструктуры; deptrac в проекте как раз следит за слоями. |
T25-L3 2.08 c | Clean architecture | Controllers and Twig templates belong to the business-logic layer because they are the ones calling use cases. | «no» Пояснение: Controllers and Twig templates belong to the presentation (interface) layer, not the business-logic layer; they merely call use cases to mediate between the user and the domain.
Raw{"answer": "no", "explanation": "Controllers and Twig templates belong to the presentation (interface) layer, not the business-logic layer; they merely call use cases to mediate between the user and the domain."} | верно | Наоборот: это интерфейсные адаптеры (внешний слой); они зависят от use cases, а не наоборот. |
T25-L4 3.01 c | Clean architecture | What sits at the very center of the onion architecture? | «business logic» Пояснение: In the Onion Architecture, the core business logic (domain rules) sits at the very center, with all other layers depending inward on it rather than outward.
Raw{"answer": "business logic", "explanation": "In the Onion Architecture, the core business logic (domain rules) sits at the very center, with all other layers depending inward on it rather than outward."} | неверно верный: «domain model» | Центральное кольцо — Domain Model: сущности и бизнес-правила без зависимостей; далее Domain Services → Application Services → Infrastructure/UI/Tests (Palermo). |
T25-L5 1.25 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 perform static analysis to detect and report forbidden cross-layer dependencies in PHP projects automatically.
Raw{"answer":"yes","explanation":"Tools like deptrac perform static analysis to detect and report forbidden cross-layer dependencies in PHP projects automatically."} | верно | depfile.yaml в проекте TasK: CI проверяет правила слоёв на каждом пайплайне. |
T25-L6 3.05 c | Clean architecture | A use case (interactor) may accept an HTTP request or an EntityManager as arguments — it is simpler that way. | «no» Пояснение: Passing an HTTP request or an EntityManager into a use case couples it to the framework and persistence layer, violating separation of concerns and making it harder to test and reuse; a use case should instead accept plain domain objects or commands and interact with persistence through an abstract repository interface.
Raw{"answer": "no", "explanation": "Passing an HTTP request or an EntityManager into a use case couples it to the framework and persistence layer, violating separation of concerns and making it harder to test and reuse; a use case should instead accept plain domain objects or commands and interact with persistence through an abstract repository interface."} | верно | Use case принимает DTO и порты; привязка к HTTP/ORM протекает инфраструктуру во внутренние слои. |
T25-L7 1.2 c | Clean architecture | What is the component called that provides a collection of aggregates/entities while hiding the storage mechanism behind an interface? | «repository» Пояснение: A Repository is a pattern from Domain-Driven Design that provides an in-memory collection of domain objects (aggregates/entities) while abstracting the storage mechanism behind an interface.
Raw{"answer": "Repository", "explanation": "A Repository is a pattern from Domain-Driven Design that provides an in-memory collection of domain objects (aggregates/entities) while abstracting the storage mechanism behind an interface."} | верно | Repository pattern (DDD/Evans); в проекте — Doctrine-репозитории за портами. |
T25-L8 2.26 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 a detail in the outer layer (interfaces/adapters and frameworks/drivers), while the domain and use cases are inner layers that depend on abstractions, so swapping the database only affects the outer layer.
Raw{"answer": "yes", "explanation": "In clean architecture, the database is a detail in the outer layer (interfaces/adapters and frameworks/drivers), while the domain and use cases are inner layers that depend on abstractions, so swapping the database only affects the outer layer."} | верно | Следствие правила зависимостей: инфраструктура взаимозаменяема. |
T26-L1 1.91 c | DDD | In DDD, an aggregate is just another name for a database table. | «no» Пояснение: An aggregate is a domain model concept representing a consistency boundary within the bounded context, whereas a database table is a persistence/storage structure; they are not the same thing and can map to each other in many-to-many or many-to-one relationships.
Raw{"answer": "no", "explanation": "An aggregate is a domain model concept representing a consistency boundary within the bounded context, whereas a database table is a persistence/storage structure; they are not the same thing and can map to each other in many-to-many or many-to-one relationships."} | верно | Агрегат — кластер объектов с границей согласованности (транзакционной вокруг корня); таблица — деталь хранения. |
T26-L2 1.37 c | DDD | A Value Object is immutable and compared by the values of its fields, not by identity. | «yes» Пояснение: In Domain-Driven Design, Value Objects are defined as immutable and are considered equal if their field values match, regardless of object identity.
Raw{"answer": "yes", "explanation": "In Domain-Driven Design, Value Objects are defined as immutable and are considered equal if their field values match, regardless of object identity."} | верно | Классика Evans: Money, Email; равенство структурное. |
T26-L3 0.86 c | DDD | What is the single external entry point of an aggregate, through which all changes must go, called? | «aggregate root» Пояснение: In Domain-Driven Design, the Aggregate Root is the single external entry point of an aggregate through which all changes must be made to maintain invariants.
Raw{"answer": "Aggregate Root", "explanation": "In Domain-Driven Design, the Aggregate Root is the single external entry point of an aggregate through which all changes must be made to maintain invariants."} | верно | Aggregate Root: внешние объекты ссылаются только на корень; он защищает инварианты агрегата. |
T26-L4 1.13 c | DDD | In DDD, a repository is declared for an aggregate (its root), not for every entity. | «yes» Пояснение: In DDD, repositories are associated with aggregate roots (not individual entities), as the aggregate is the unit of consistency and the repository manages it as a whole.
Raw{"answer": "yes", "explanation": "In DDD, repositories are associated with aggregate roots (not individual entities), as the aggregate is the unit of consistency and the repository manages it as a whole."} | верно | Репозиторий корня хранит границу согласованности агрегата; вложенные сущности доступны только через корень. |
T26-L5 1.69 c | DDD | Ubiquitous language is the model's shared language common to developers and domain experts. | «yes» Пояснение: In Domain-Driven Design, the Ubiquitous Language is indeed the common language shared between developers and domain experts for describing the domain and its model.
Raw{"answer": "yes", "explanation": "In Domain-Driven Design, the Ubiquitous Language is indeed the common language shared between developers and domain experts for describing the domain and its model."} | верно | Evans: язык из требований переходит в имена классов и методов. |
T26-L6 8.43 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) of a model is the set of objects within which the language's symbols are interpreted consistently, and the same language can be interpreted over different domains yielding different models.
Raw{"answer": "domain", "explanation": "In model theory, the domain (or universe of discourse) of a model is the set of objects within which the language's symbols are interpreted consistently, and the same language can be interpreted over different domains yielding different models."} | неверно верный: «bounded context» | Bounded Context; «Заказ» в биллинге и в доставке — разные модели. |
T26-L7 1.69 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 entities, value objects, and aggregates encapsulate business logic and invariants, rather than an anemic model where behavior is pushed into service classes.
Raw{"answer": "no", "explanation": "DDD recommends a rich domain model where entities, value objects, and aggregates encapsulate business logic and invariants, rather than an anemic model where behavior is pushed into service classes."} | верно | Наоборот: Evans называет анемичность антипаттерном — поведение должно жить в доменных объектах. |
T26-L8 1.9 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, a Bounded Context is explicitly a boundary within which a single model applies, and the same concept can be modeled as different classes in different contexts (e.g., 'Customer' in Sales vs. 'Customer' in Inventory).
Raw{"answer": "yes", "explanation": "In Domain-Driven Design, a Bounded Context is explicitly a boundary within which a single model applies, and the same concept can be modeled as different classes in different contexts (e.g., 'Customer' in Sales vs. 'Customer' in Inventory)."} | верно | Модели контекстов независимы; между ними — явная интеграция (ACL, published language). |
T13-L1 2.31 c | Symfony | Services in the Symfony DI container are created lazily by default — on first use. | «yes» Пояснение: Symfony's DI container instantiates services on first request (lazy loading) rather than eagerly at boot, unless explicitly marked as eager or a singleton requiring immediate creation.
Raw{"answer":"yes","explanation":"Symfony's DI container instantiates services on first request (lazy loading) rather than eagerly at boot, unless explicitly marked as eager or a singleton requiring immediate creation."} | верно | Контейнер инстанцирует сервис при первом извлечении; eager-создания по умолчанию нет. |
T13-L2 3.47 c | Symfony | Which Symfony console command lists all registered routes? | «symfony:routes» Пояснение: The Symfony console command 'symfony:routes' lists all registered routes in the application.
Raw{"answer": "symfony:routes", "explanation": "The Symfony console command 'symfony:routes' lists all registered routes in the application."} | неверно верный: «debug:router» | bin/console debug:router (FrameworkBundle); в Symfony 3 команда называлась router:debug. |
T13-L3 1.8 c | Symfony | Symfony autowiring requires manually declaring every service in services.yaml. | «no» Пояснение: Symfony autowiring is designed precisely to eliminate the need for manually declaring every service; it automatically detects and registers services based on directory scanning, attributes, and conventions.
Raw{"answer": "no", "explanation": "Symfony autowiring is designed precisely to eliminate the need for manually declaring every service; it automatically detects and registers services based on directory scanning, attributes, and conventions."} | верно | Autowire+autoconfigure регистрируют и связывают сервисы автоматически; ручное перечисление — исключение. |
T13-L4 1.27 c | Symfony | Twig templates are compiled into PHP classes and cached between requests. | «yes» Пояснение: Twig compiles templates into PHP classes (or PHP files) and stores them in a cache directory so they are reused across requests rather than being recompiled every time.
Raw{"answer": "yes", "explanation": "Twig compiles templates into PHP classes (or PHP files) and stores them in a cache directory so they are reused across requests rather than being recompiled every time."} | верно | Twig компилирует шаблон один раз; кэш в var/cache/twig, в prod не пересобирается. |
T13-L5 1.24 c | Symfony | In the Symfony dev environment the DI container is rebuilt only after tracked files change, not on every request. | «yes» Пояснение: In Symfony's dev environment, the container is compiled and cached on first use, then only recompiled when tracked files change rather than on every request.
Raw{"answer": "yes", "explanation": "In Symfony's dev environment, the container is compiled and cached on first use, then only recompiled when tracked files change rather than on every request."} | верно | Kernel проверяет freshness ресурсов (конфиги, классы); иначе переиспользуется кэш контейнера. |
T13-L6 4.11 c | Symfony | Which environment variable selects the active Symfony environment (dev/prod)? | «symfony_env» Пояснение: The SYMFONY_ENV environment variable is used to select the active Symfony environment (e.g., dev, prod).
Raw{"answer": "SYMFONY_ENV", "explanation": "The SYMFONY_ENV environment variable is used to select the active Symfony environment (e.g., dev, prod)."} | неверно верный: «app_env» | APP_ENV в .env; APP_DEBUG — отдельный флаг отладки. |
T13-L7 2.97 c | Symfony | A controller method can be private — Symfony routing works with any method of the class. | «yes» Пояснение: Symfony uses reflection with setAccessible(true) to invoke controller actions, so routing works with private (and any other visibility) methods of the controller class.
Raw{"answer": "yes", "explanation": "Symfony uses reflection with setAccessible(true) to invoke controller actions, so routing works with private (and any other visibility) methods of the controller class."} | неверно верный: «no» | Действие контроллера должно быть public; приватный метод по маршруту не вызывается. |
T13-L8 2.02 c | Symfony | Event subscribers always receive events before listeners, because the interface gives them priority. | «no» Пояснение: PHP does not define an interface that gives event subscribers inherent priority over listeners; processing order is determined by explicitly assigned priorities, not by the subscriber/listener distinction.
Raw{"answer": "no", "explanation": "PHP does not define an interface that gives event subscribers inherent priority over listeners; processing order is determined by explicitly assigned priorities, not by the subscriber/listener distinction."} | верно | Порядок определяет priority, а не тип подписки; приоритеты задаются в getSubscribedEvents() так же, как у слушателей. |
T22-L1 2.7 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» Пояснение: The legacy Guard architecture (used from Symfony 2 through 5.2) was deprecated in 5.3 and removed in Symfony 6.0, replaced by the new Firewall architecture built on AuthenticatorInterface.
Raw{"answer": "yes", "explanation": "The legacy Guard architecture (used from Symfony 2 through 5.2) was deprecated in 5.3 and removed in Symfony 6.0, replaced by the new Firewall architecture built on AuthenticatorInterface."} | верно | Guard объявлен устаревшим в 5.3 и удалён в 6.0; в проекте symfony/security-bundle 8.1. |
T22-L2 1.98 c | Symfony: Security and forms | Which Symfony attribute checks a role/permission right on a controller method (403 without it)? | «isgranted» Пояснение: The #[IsGranted] attribute (Symfony\Component\Security\Attribute\IsGranted) checks whether the current user has the specified role or permission, returning a 403 Forbidden response if the check fails.
Raw{"answer":"IsGranted","explanation":"The #[IsGranted] attribute (Symfony\\Component\\Security\\Attribute\\IsGranted) checks whether the current user has the specified role or permission, returning a 403 Forbidden response if the check fails."} | верно | #[IsGranted('ROLE_ADMIN')]; атрибут из symfony/security-http. |
T22-L3 1.54 c | Symfony: Security and forms | Voters are Symfony's mechanism for checking access to a specific object: isGranted('EDIT', $post). | «yes» Пояснение: Voters are the component in Symfony's AccessDecisionManager used to make authorization decisions about whether a user is granted access to a specific resource, as illustrated by isGranted('EDIT', $post).
Raw{"answer": "yes", "explanation": "Voters are the component in Symfony's AccessDecisionManager used to make authorization decisions about whether a user is granted access to a specific resource, as illustrated by isGranted('EDIT', $post)."} | верно | VoterInterface->vote(); docs Symfony — Voters. |
T22-L4 4.54 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 annotation component, and the corresponding Doctrine 3 removed annotation-based ORM mapping, both in favor of PHP attributes.
Raw{"answer": "yes", "explanation": "Symfony 7 removed the annotation component, and the corresponding Doctrine 3 removed annotation-based ORM mapping, both in favor of PHP attributes."} | верно | Докблок-аннотации удалены в Symfony 7.0; стандарт — атрибуты. В проекте symfony/validator 8.1. |
T22-L5 1.07 c | Symfony: Security and forms | CSRF protection of Symfony forms is enabled by default: the form validates the token on submission. | «yes» Пояснение: Symfony automatically adds a CSRF token to forms and validates it on submission by default without any extra configuration.
Raw{"answer": "yes", "explanation": "Symfony automatically adds a CSRF token to forms and validates it on submission by default without any extra configuration."} | верно | 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 always performs form validation on the server-side, regardless of whether client-side HTML5 validation passed or was bypassed.
Raw{"answer": "yes", "explanation": "Symfony always performs form validation on the server-side, regardless of whether client-side HTML5 validation passed or was bypassed."} | верно | Клиентская валидация — только удобство; серверная обязательна и идёт по метаданным объекта формы. |
T22-L7 0.81 c | Symfony: Security and forms | Which Symfony maker command generates a form class (FormType)? | «make:form» Пояснение: The Symfony maker command 'make:form' generates a FormType class for creating a form.
Raw{"answer":"make:form","explanation":"The Symfony maker command 'make:form' generates a FormType class for creating a form."} | верно | bin/console make:form (symfony/maker-bundle — в проекте). |
T22-L8 1.42 c | Symfony: Security and forms | Symfony stores the user's password in the session in plain text. | «no» Пояснение: Symfony never stores passwords in plain text; it hashes them (typically using bcrypt via password_hash) and stores the hash, keeping only user identity in the session.
Raw{"answer": "no", "explanation": "Symfony never stores passwords in plain text; it hashes them (typically using bcrypt via password_hash) and stores the hash, keeping only user identity in the session."} | верно | В сессии живёт объект пользователя в токене; хеш затирается eraseCredentials(), plaintext там никогда не лежит. |
T23-L1 1.68 c | Symfony: configuration and services | Symfony bundle configuration lives in config/packages — one file per bundle or topic. | «yes» Пояснение: In modern Symfony projects, bundle configurations are placed in config/packages/ with one file per bundle or topic (e.g., config/packages/security.yaml), and these files are automatically loaded.
Raw{"answer": "yes", "explanation": "In modern Symfony projects, bundle configurations are placed in config/packages/ with one file per bundle or topic (e.g., config/packages/security.yaml), and these files are automatically loaded."} | верно | Стандартная структура (config/packages/*.yaml); перегрузка — config/packages/<env>. |
T23-L2 1.35 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 common convention (e.g., in Laravel) where .env holds committed dev defaults and .env.local holds uncommitted real secrets, typically ignored via .gitignore.
Raw{"answer": "yes", "explanation": "This is a common convention (e.g., in Laravel) where .env holds committed dev defaults and .env.local holds uncommitted real secrets, typically ignored via .gitignore."} | верно | symfony/dotenv: .env — общий безопасный набор значений; локальные секреты — .env.local (gitignored) или secrets-хранилище. |
T23-L3 0.94 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 in the DI container along with their aliases.
Raw{"answer": "debug:container", "explanation": "The Symfony command 'debug:container' lists all registered services in the DI container along with their aliases."} | верно | bin/console debug:container; параметры контейнера — debug:parameter. |
T23-L4 1.96 c | Symfony: configuration and services | The Symfony container allows changing parameters at runtime: $container->setParameter() works from a controller. | «no» Пояснение: The Symfony container is frozen after compilation, so parameters cannot be modified at runtime with setParameter().
Raw{"answer": "no", "explanation": "The Symfony container is frozen after compilation, so parameters cannot be modified at runtime with setParameter()."} | верно | Контейнер компилируется и замораживается; runtime-значения — только через переменные окружения. |
T23-L5 1.12 c | Symfony: configuration and services | By default, Symfony services are public (public: true) — you can fetch them directly from the container. | «no» Пояснение: Since Symfony 3, services are non-public (public: false) by default and must be explicitly marked public to be fetched from the container.
Raw{"answer": "no", "explanation": "Since Symfony 3, services are non-public (public: false) by default and must be explicitly marked public to be fetched from the container."} | верно | С Symfony 4.0 сервисы по умолчанию private: инжектятся через autowiring; $container->get() — только для публичных. |
T23-L6 2.36 c | Symfony: configuration and services | Without a config file in config/packages a bundle will not work — configuration is mandatory for every bundle. | «no» Пояснение: Many bundles in Symfony work with their default configurations and do not require a dedicated config file to function.
Raw{"answer": "no", "explanation": "Many bundles in Symfony work with their default configurations and do not require a dedicated config file to function."} | верно | У бандлов есть встроенные умолчания (Extension); конфиг нужен только для отклонений от них. |
T23-L7 5.34 c | Symfony: configuration and services | Environment variable values are injected into services.yaml using the %env(VAR)% syntax. | «yes» Пояснение: In Symfony, environment variable placeholders in configuration files like services.yaml use the %env(VAR)% syntax (written as %%env(VAR)%% in raw YAML) to inject the value of the corresponding environment variable.
Raw{"answer": "yes", "explanation": "In Symfony, environment variable placeholders in configuration files like services.yaml use the %env(VAR)% syntax (written as %%env(VAR)%% in raw YAML) to inject the value of the corresponding environment variable."} | верно | %env(...)% резолвится в рантайме env-процессорами; docs — Env Var Processors. |
T23-L8 0.91 c | Symfony: configuration and services | Which Symfony environment variable enables debug mode (affects the profiler and Twig debugging)? | «app_debug» Пояснение: The APP_DEBUG environment variable in Symfony enables debug mode, which activates the web profiler and Twig debug mode.
Raw{"answer": "APP_DEBUG", "explanation": "The APP_DEBUG environment variable in Symfony enables debug mode, which activates the web profiler and Twig debug mode."} | верно | APP_DEBUG=1 (в .env dev-окружения); окружение выбирает APP_ENV — см. T13-L6. |
T16-L1 1.15 c | Symfony: Messenger | A single message in Symfony Messenger can only have one handler. | «no» Пояснение: In Symfony Messenger, a single message can have multiple handlers; all registered handlers for that message class or channel will be invoked.
Raw{"answer": "no", "explanation": "In Symfony Messenger, a single message can have multiple handlers; all registered handlers for that message class or channel will be invoked."} | верно | Messenger вызывает все хендлеры, подписанные на класс сообщения (docs — Multiple Handlers). |
T16-L2 1.8 c | Symfony: Messenger | The sync transport in Messenger queues the message for a worker, just like async. | «no» Пояснение: The sync transport processes the message immediately in the same process without queueing it, unlike async transports which place the message on a queue for a worker to pick up.
Raw{"answer": "no", "explanation": "The sync transport processes the message immediately in the same process without queueing it, unlike async transports which place the message on a queue for a worker to pick up."} | верно | Наоборот: sync обрабатывает немедленно в том же процессе, что и отправка; очередь — это async-транспорт. |
T16-L3 1.22 c | Symfony: Messenger | Which console command starts the worker that processes Messenger queue messages? | «bin/console messenger:consume» Пояснение: In Symfony, the messenger:consume command starts a worker that processes queued messages from a Messenger transport.
Raw{"answer":"bin/console messenger:consume","explanation":"In Symfony, the messenger:consume command starts a worker that processes queued messages from a Messenger transport."} | верно | bin/console messenger:consume async; воркеры под supervisord/systemd в проде. |
T16-L4 1.27 c | Symfony: Messenger | Retries for failed messages (retry_strategy) are configured per Messenger transport. | «yes» Пояснение: In Symfony Messenger, retry_strategy options (max_retries, time_limit, etc.) are defined per transport in the messenger configuration, allowing each transport to have its own retry behavior.
Raw{"answer":"yes","explanation":"In Symfony Messenger, retry_strategy options (max_retries, time_limit, etc.) are defined per transport in the messenger configuration, allowing each transport to have its own retry behavior."} | верно | retry_strategy на транспорте: max_retries, delay, multiplier; docs — Failed Messages & Retries. |
T16-L5 3.18 c | Symfony: Messenger | By default, Messenger serializes messages to JSON. | «yes» Пояснение: In Symfony Messenger, the default serializer used to encode and decode messages is JsonSerializer.
Raw{"answer": "yes", "explanation": "In Symfony Messenger, the default serializer used to encode and decode messages is JsonSerializer."} | неверно верный: «no» | Дефолтный сериализатор — PhpSerializer (serialize()); JSON-сериализатор включается отдельно. |
T16-L6 5.96 c | Symfony: Messenger | Symfony Scheduler produces messages on a schedule and dispatches them through Messenger. | «no» Пояснение: There is no official 'Symfony Scheduler' component; Symfony does not ship a dedicated scheduler that produces and dispatches messages through Messenger—scheduling is typically handled externally (e.g., via cron) or through third-party packages.
Raw{"answer": "false", "explanation": "There is no official 'Symfony Scheduler' component; Symfony does not ship a dedicated scheduler that produces and dispatches messages through Messenger—scheduling is typically handled externally (e.g., via cron) or through third-party packages."} | неверно верный: «yes» | Schedule → RecurringMessage → шина Messenger; docs — Scheduler. |
T16-L7 1.67 c | Symfony: Messenger | Which built-in Messenger transport stores messages in database tables via Doctrine? | «database» Пояснение: Symfony Messenger's 'database' transport uses Doctrine to store messages in database tables (messenger_messages and messenger_sent_messages).
Raw{"answer": "database", "explanation": "Symfony Messenger's 'database' transport uses Doctrine to store messages in database tables (messenger_messages and messenger_sent_messages)."} | неверно верный: «doctrine» | Транспорт doctrine (symfony/doctrine-messenger); таблица messenger_messages. В проекте стоит amqp-messenger + doctrine-messenger. |
T16-L8 1.45 c | Symfony: Messenger | The Messenger pipeline can be extended with custom middleware, placed before or after the built-in ones. | «yes» Пояснение: Symfony's Messenger component allows you to add custom middleware to the pipeline with configurable priority to place them before or after built-in middleware.
Raw{"answer":"yes","explanation":"Symfony's Messenger component allows you to add custom middleware to the pipeline with configurable priority to place them before or after built-in middleware."} | верно | messenger.bus.*.middleware в yaml; docs — Middleware. |
T28-L1 9.5 c | Symfony: versions | Symfony major releases come every two years, minor ones every six months (in May and November). | «yes» Пояснение: Symfony's documented release cycle states major versions every two years and minor versions every six months, with releases shipped in May and November.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Symfony's documented release cycle states major versions every two years and minor versions every six months, with releases shipped in May and November." ⏎ } | верно | Стандартный релизный цикл: 8.0 — ноябрь 2025, 8.1 — май 2026, 8.2 — ноябрь 2026. |
T28-L2 1.83 c | Symfony: versions | What is the minimum PHP version required by Symfony 8? | «8.2» Пояснение: Symfony 8 requires a minimum PHP version of 8.2.
Raw{"answer": "8.2", "explanation": "Symfony 8 requires a minimum PHP version of 8.2."} | неверно верный: «8.4» | Symfony 8.0 поднял требование до PHP >= 8.4.1 (в vendor проекта: "php": ">=8.4.1"). |
T28-L3 2.47 c | Symfony: versions | Symfony 7.0 kept support for docblock annotations (validation, routes). | «no» Пояснение: Symfony 7.0 removed support for docblock annotations (validation, routes, and other annotation-based features), having already deprecated them in Symfony 6.0 in favor of PHP attributes.
Raw{"answer": "no", "explanation": "Symfony 7.0 removed support for docblock annotations (validation, routes, and other annotation-based features), having already deprecated them in Symfony 6.0 in favor of PHP attributes."} | верно | Наоборот: в 7.0 аннотации удалены — только PHP-атрибуты (#[Route], #[Assert\NotBlank]). |
T28-L4 3.81 c | Symfony: versions | AssetMapper manages CSS/JS without node or webpack — via importmap.php. | «no» Пояснение: AssetManager (mcbrae) is a pure-PHP asset manager that does not require Node/webpack, but it does not operate via an 'importmap.php' file; it serves assets through its own routes/API.
Raw{"answer":"no","explanation":"AssetManager (mcbrae) is a pure-PHP asset manager that does not require Node/webpack, but it does not operate via an 'importmap.php' file; it serves assets through its own routes/API."} | неверно верный: «yes» | symfony/asset-mapper (с 6.3, стандарт с 7.x); в проекте — importmap.php в корне и asset-mapper 8.1. |
T28-L5 2.46 c | Symfony: versions | Symfony 6.4 is a regular release without long-term support. | «no» Пояснение: Symfony 6.4 is actually a Long-Term Support (LTS) release, supported until November 2027, since all even-numbered major releases (4.4, 5.4, 6.4, 7.4) are LTS releases.
Raw{"answer": "no", "explanation": "Symfony 6.4 is actually a Long-Term Support (LTS) release, supported until November 2027, since all even-numbered major releases (4.4, 5.4, 6.4, 7.4) are LTS releases."} | верно | Наоборот: 6.4 — LTS (расширенная поддержка); LTS выходит вместе с очередным мажором (6.4 — вместе с 7.0). |
T28-L6 2.4 c | Symfony: versions | When moving to a new Symfony major version, deprecations of the previous branch keep working — major releases do not remove them. | «no» Пояснение: Major Symfony releases remove the deprecations introduced in the previous branch, so they no longer exist or work in the new major version.
Raw{"answer": "no", "explanation": "Major Symfony releases remove the deprecations introduced in the previous branch, so they no longer exist or work in the new major version."} | верно | Наоборот: мажорный релиз удаляет всё устаревшее (7.0 убрал деприкейшены 6.x, 8.0 — 7.x). |
T28-L7 1.27 c | Symfony: versions | Every Symfony major release is accompanied by an UPGRADE guide listing the changes. | «yes» Пояснение: Symfony provides an UPGRADE guide for each major release, documenting all breaking changes and deprecations introduced in that version.
Raw{"answer": "yes", "explanation": "Symfony provides an UPGRADE guide for each major release, documenting all breaking changes and deprecations introduced in that version."} | верно | UPGRADE-7.0.md, UPGRADE-8.0.md в репозитории symfony/symfony. |
T28-L8 3.52 c | Symfony: versions | Which Symfony component manages assets and the importmap without node/webpack? | «asset-mapper» Пояснение: Symfony's AssetMapper component (Symfony\Component\AssetMapper) provides a pure-PHP solution for managing assets and generating the importmap without requiring node or webpack.
Raw{"answer": "asset-mapper", "explanation": "Symfony's AssetMapper component (Symfony\\Component\\AssetMapper) provides a pure-PHP solution for managing assets and generating the importmap without requiring node or webpack."} | верно | symfony/asset-mapper 8.1 — в проекте. |
T29-L1 9.74 c | Symfony: 8.2 and beyond | As of 2026-11-07, Symfony 8.2 has already been released. | «no» Пояснение: Symfony 8.2 would not be released until around 2027, so it had not yet been released as of November 7, 2026.
Raw{"answer": "no", "explanation": "Symfony 8.2 would not be released until around 2027, so it had not yet been released as of November 7, 2026."} | верно | Наоборот: 8.2 ещё не выпущена — релиз в конце ноября 2026; последняя стабильная — 8.1. |
T29-L2 6.42 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 cycle from Symfony 6.0 (November 2024), November 2026 would be Symfony 7.1, not 8.2.
Raw{"answer": "no", "explanation": "Following Symfony's six-month cycle from Symfony 6.0 (November 2024), November 2026 would be Symfony 7.1, not 8.2."} | неверно верный: «yes» | Политика релизов: 8.1 — май 2026, 8.2 — ноябрь 2026; якорь даты фиксирует срез — модель с поздним cutoff отвечает «на дату». |
T29-L3 8.15 c | Symfony: 8.2 and beyond | Which Symfony version comes after 8.1 (as of 2026-11-07)? | «8.2» Пояснение: Following Symfony's standard release cycle, the version that comes after 8.1 is 8.2.
Raw{"answer": "8.2", "explanation": "Following Symfony's standard release cycle, the version that comes after 8.1 is 8.2."} | верно | 8.2 — следующий минорный релиз (ноябрь 2026); после его выхода проект переходит с 8.1.* на 8.2.*. |
T29-L4 3.42 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 (the '2' indicates the minor version), not a major release; only major releases like 8.0 introduce breaking API changes that would require rewriting applications.
Raw{"answer":"no","explanation":"Symfony 8.2 is a minor release (the '2' indicates the minor version), not a major release; only major releases like 8.0 introduce breaking API changes that would require rewriting applications."} | верно | Наоборот: 8.2 — минорный релиз; новые возможности без поломки обратной совместимости. Мажор — 9.0. |
T29-L5 3.91 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 a major version series, so upgrading from 8.1 to 8.2 (a minor bump within the 8.x branch) will not break existing code.
Raw{"answer": "yes", "explanation": "PHP guarantees backward compatibility within a major version series, so upgrading from 8.1 to 8.2 (a minor bump within the 8.x branch) will not break existing code."} | верно | Политика Symfony: минорные релизы обратно совместимы; BC-break допустим только в мажорных. |
T29-L6 1.6 c | Symfony: 8.2 and beyond | Which minor version of the 8.x branch is released last, before Symfony 9.0? | «8.4» Пояснение: Symfony 8.4 was the final minor release in the 8.x branch before Symfony 9.0 was released.
Raw{"answer": "8.4", "explanation": "Symfony 8.4 was the final minor release in the 8.x branch before Symfony 9.0 was released."} | верно | По циклу: 8.2 (ноя 2026), 8.3 (май 2027), 8.4 (ноя 2027, вместе с 9.0) — как 6.4 выходила вместе с 7.0. |
T29-L7 4.39 c | Symfony: 8.2 and beyond | Symfony 8.2 will require PHP 8.5 — you would have to upgrade PHP along with it. | «yes» Пояснение: Symfony 8.2 requires PHP 8.5, so upgrading to it necessarily includes upgrading the PHP version.
Raw{"answer": "yes", "explanation": "Symfony 8.2 requires PHP 8.5, so upgrading to it necessarily includes upgrading the PHP version."} | неверно верный: «no» | Наоборот: минорные релизы не поднимают требования PHP; для всей ветки 8.x остаётся PHP >= 8.4. |
T29-L8 7.09 c | Symfony: 8.2 and beyond | Deprecations added in the 8.x branch will not be removed before Symfony 9.0. | «yes» Пояснение: In Symfony's deprecation policy, deprecations introduced in an 8.x minor release are scheduled for removal in the next major version, 9.0, meaning they are not removed before 9.0.
Raw{"answer": "yes", "explanation": "In Symfony's deprecation policy, deprecations introduced in an 8.x minor release are scheduled for removal in the next major version, 9.0, meaning they are not removed before 9.0."} | верно | Политика: деприкейшены живут до следующего мажора; 9.0 — ноябрь 2027. |
T21-L1 1.62 c | Twig | Inside {{ }}, Twig allows calling arbitrary PHP code directly. | «no» Пояснение: Twig's {{ }} expression language is a restricted, sandboxed syntax that only permits predefined Twig functions, filters, and constructs — it does not allow calling arbitrary PHP code directly.
Raw{"answer": "no", "explanation": "Twig's {{ }} expression language is a restricted, sandboxed syntax that only permits predefined Twig functions, filters, and constructs — it does not allow calling arbitrary PHP code directly."} | верно | Twig — DSL: только разрешённые окружением функции/фильтры; произвольный PHP не исполняется. |
T21-L2 1.02 c | Twig | By default, Twig auto-escapes printed variables. | «yes» Пояснение: Twig applies the `html` escape filter to all output variables by default to prevent XSS, and it can only be overridden with the `|raw` filter.
Raw{"answer": "yes", "explanation": "Twig applies the `html` escape filter to all output variables by default to prevent XSS, and it can only be overridden with the `|raw` filter."} | верно | Autoescape включён по умолчанию; {{ '<b>' }} → <b>. Проверено на Twig 3.30. |
T21-L3 1.41 c | Twig | The Twig |e filter escapes a string for safe output in an HTML context. | «yes» Пояснение: By default, the Twig |e filter escapes a string for an HTML context, preventing issues like HTML injection.
Raw{"answer": "yes", "explanation": "By default, the Twig |e filter escapes a string for an HTML context, preventing issues like HTML injection."} | верно | |e ('html') по умолчанию; есть контексты js/url/css. От SQL-инъекций он не защищает — это задача подготовленных запросов Doctrine. |
T21-L4 1.75 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 using the intl library according to the specified locale.
Raw{"answer": "number_format", "explanation": "The twig/intl-extra package provides the number_format filter, which formats a number using the intl library according to the specified locale."} | неверно верный: «format_number» | |format_number(locale=...) из IntlExtension (twig/intl-extra есть в проекте). Проверено на Twig 3.30: 12345.6 → 12 345,6 (ru). |
T21-L5 1.1 c | Twig | The |raw filter disables auto-escaping for the value. | «yes» Пояснение: In Twig, the |raw filter outputs a value without applying auto-escaping, which is the opposite of the default behavior.
Raw{"answer":"yes","explanation":"In Twig, the |raw filter outputs a value without applying auto-escaping, which is the opposite of the default behavior."} | верно | {{ x|raw }} выводит HTML как есть; опасно с пользовательскими данными. Проверено на Twig 3.30. |
T21-L6 1.29 c | Twig | In Twig, {{ }} prints an expression value, while {% %} executes tags — conditions, loops, set. | «yes» Пояснение: In Twig, double curly braces {{ }} render the value of an expression, while percent curly braces {% %} delimit structural tags such as if, for, and set.
Raw{"answer": "yes", "explanation": "In Twig, double curly braces {{ }} render the value of an expression, while percent curly braces {% %} delimit structural tags such as if, for, and set."} | верно | Два блока синтаксиса Twig: вывод (echo) против логики. |
T21-L7 1.66 c | Twig | In Twig you cannot declare a variable inside a template — values only come from the controller. | «no» Пояснение: Twig allows you to declare variables inside a template using the set tag, e.g. {% set my_var = 'hello' %}.
Raw{"answer": "no", "explanation": "Twig allows you to declare variables inside a template using the set tag, e.g. {% set my_var = 'hello' %}."} | верно | {% set y = ... %} объявляет переменную в шаблоне. Проверено на Twig 3.30. |
T21-L8 1.64 c | Twig | Which Twig function dumps the debug structure of a variable (array, object)? | «dump» Пояснение: The Twig function `dump()` (e.g., {{ dump(myVar) }} or {{ myVar|dump }}) outputs the debug structure of a variable in a human-readable format.
Raw{"answer": "dump", "explanation": "The Twig function `dump()` (e.g., {{ dump(myVar) }} or {{ myVar|dump }}) outputs the debug structure of a variable in a human-readable format."} | верно | {{ dump(x) }} (DebugExtension; в Symfony доступна в dev-окружении). |
T24-L1 1.22 c | Bootstrap | Bootstrap is a CSS/JS library of ready-made UI components, not an SPA framework. | «yes» Пояснение: Bootstrap provides a pre-built set of CSS and JavaScript UI components (buttons, modals, navbars, etc.) and is not a SPA framework like React, Angular, or Vue.
Raw{"answer":"yes","explanation":"Bootstrap provides a pre-built set of CSS and JavaScript UI components (buttons, modals, navbars, etc.) and is not a SPA framework like React, Angular, or Vue."} | верно | Компоненты и утилиты поверх вашего HTML; SPA-фреймворки (React/Vue) — другой класс инструментов. В проекте vendored 5.3.3. |
T24-L2 2.32 c | Bootstrap | Which Bootstrap class gives a responsive container with a fixed max width per breakpoint? | «container» Пояснение: In Bootstrap, the .container class provides a responsive container whose max-width increases at each breakpoint (e.g., 540px, 720px, 960px, 1140px).
Raw{"answer":"container","explanation":"In Bootstrap, the .container class provides a responsive container whose max-width increases at each breakpoint (e.g., 540px, 720px, 960px, 1140px)."} | верно | .container (фиксированная макс-ширина по брейкпоинтам) vs .container-fluid (на всю ширину). |
T24-L3 1.7 c | Bootstrap | The Bootstrap grid is built on CSS floats and splits a row into 16 columns. | «no» Пояснение: The Bootstrap grid is split into 12 columns (not 16), and while Bootstrap 3 used CSS floats, Bootstrap 4 and 5 use Flexbox instead.
Raw{"answer": "no", "explanation": "The Bootstrap grid is split into 12 columns (not 16), and while Bootstrap 3 used CSS floats, Bootstrap 4 and 5 use Flexbox instead."} | верно | Наоборот: flexbox (с Bootstrap 4) и 12 колонок; float-сетка — это Bootstrap 3. |
T24-L4 1.95 c | Bootstrap | Bootstrap's named breakpoints (the infix used in class names) are sm, md, lg, xl, xxl — five of them. | «yes» Пояснение: Bootstrap (versions 4 and 5) defines five named breakpoints: sm, md, lg, xl, and xxl.
Raw{"answer": "yes", "explanation": "Bootstrap (versions 4 and 5) defines five named breakpoints: sm, md, lg, xl, and xxl."} | верно | Тиров всего шесть: xs (без инфикса) + пять именованных (576/768/992/1200/1400 px). |
T24-L5 2.86 c | Bootstrap | Utilities like .mt-3 or .px-2 use the spacing scale: the number is a multiple of $spacer. | «yes» Пояснение: In Tailwind CSS, utility classes like .mt-3 or .px-2 generate values that are the specified number multiplied by the base spacing unit (default 0.25rem), so .mt-3 equals 0.75rem and .px-2 equals 0.5rem.
Raw{"answer": "yes", "explanation": "In Tailwind CSS, utility classes like .mt-3 or .px-2 generate values that are the specified number multiplied by the base spacing unit (default 0.25rem), so .mt-3 equals 0.75rem and .px-2 equals 0.5rem."} | неверно верный: «no» | Spacing utilities; $spacer = 1rem. |
T24-L6 1.14 c | Bootstrap | Which Bootstrap 5 data attribute enables an interactive component (e.g. dropdown) on an element? | «data-bs-toggle» Пояснение: The data-bs-toggle attribute is used in Bootstrap 5 to enable interactive components such as dropdowns, modals, and tooltips on elements.
Raw{"answer": "data-bs-toggle", "explanation": "The data-bs-toggle attribute is used in Bootstrap 5 to enable interactive components such as dropdowns, modals, and tooltips on elements."} | верно | data-bs-toggle="dropdown" и т.п.; в Bootstrap 4 атрибут назывался data-toggle. |
T24-L7 1.1 c | Bootstrap | Bootstrap 5 components work without jQuery — in plain vanilla JS. | «yes» Пояснение: Bootstrap 5 removed its jQuery dependency and its components (modals, dropdowns, tooltips, etc.) are built with vanilla ES6+ JavaScript.
Raw{"answer": "yes", "explanation": "Bootstrap 5 removed its jQuery dependency and its components (modals, dropdowns, tooltips, etc.) are built with vanilla ES6+ JavaScript."} | верно | jQuery удалён в Bootstrap 5.0: data-bs-* атрибуты и JS API. В проекте vendored 5.3.3. |
T24-L8 1.54 c | Bootstrap | Dark mode in Bootstrap is enabled with a .dark class on the root element. | «no» Пояснение: In Bootstrap 5, dark mode is enabled by adding the `data-bs-theme="dark"` attribute to the root element, not by using a `.dark` class.
Raw{"answer": "no", "explanation": "In Bootstrap 5, dark mode is enabled by adding the `data-bs-theme=\"dark\"` attribute to the root element, not by using a `.dark` class."} | верно | Наоборот: тема включается атрибутом data-bs-theme="dark" (Color modes, с 5.3); класса .dark не существует. В проекте 5.3.3. |
T14-L1 1.32 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 create them using tools like Doctrine Migrations or the SchemaTool.
Raw{"answer": "no", "explanation": "Doctrine ORM does not automatically create tables at runtime; you must explicitly create them using tools like Doctrine Migrations or the SchemaTool."} | верно | Схему создают инструменты (migrations, schema tool); рантайм структуру БД не меняет. |
T14-L2 1.35 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 and defers any SQL until flush() is invoked.
Raw{"answer": "persist()", "explanation": "EntityManager.persist() marks a new entity as managed and defers any SQL until flush() is invoked."} | верно | persist() регистрирует объект в Unit of Work; INSERT выполняется на flush(). |
T14-L3 1.96 c | Doctrine | In Doctrine ORM 3, the EntityManager::merge() method exists and makes the passed object managed. | «yes» Пояснение: In Doctrine ORM 3, EntityManager::merge() takes a detached or unmanaged entity and makes it managed again, associating it with the current EntityManager so that changes can be flushed.
Raw{"answer": "yes", "explanation": "In Doctrine ORM 3, EntityManager::merge() takes a detached or unmanaged entity and makes it managed again, associating it with the current EntityManager so that changes can be flushed."} | неверно верный: «no» | В ORM 3 merge() удалён (в vendor проекта 3.7.6 метода нет); в Doctrine 2.x merge() возвращал управляемую копию. Версия зафиксирована — ORM 3. |
T14-L4 1.36 c | Doctrine | DQL queries are written in terms of entities and their fields, not tables and columns. | «yes» Пояснение: DQL (as used in JPA/JPQL) is object-oriented and references entity classes and their mapped fields rather than physical table and column names.
Raw{"answer": "yes", "explanation": "DQL (as used in JPA/JPQL) is object-oriented and references entity classes and their mapped fields rather than physical table and column names."} | верно | Doctrine транслирует DQL в SQL; docs — DQL (Doctrine Query Language). |
T14-L5 4.17 c | Doctrine | What does $repository->find(999) return when no record with id 999 exists? | «null» Пояснение: In Doctrine ORM (and similar PHP ORM repositories), the find() method returns null when no entity matching the given primary key is found in the database.
Raw{"answer": "null", "explanation": "In Doctrine ORM (and similar PHP ORM repositories), the find() method returns null when no entity matching the given primary key is found in the database."} | верно | find() возвращает null, если объект не найден (docs Repository methods). |
T14-L6 4.99 c | Doctrine | DoctrineBundle in Symfony automatically calls flush() at the end of every request. | «no» Пояснение: Symfony's DoctrineBundle does not automatically call flush() at the end of every request; developers must explicitly call flush() on the EntityManager when they want to persist changes to the database.
Raw{"answer": "no", "explanation": "Symfony's DoctrineBundle does not automatically call flush() at the end of every request; developers must explicitly call flush() on the EntityManager when they want to persist changes to the database."} | верно | Авто-flush нет — flush() зовёт разработчик; незакрытая транзакция в конце запроса откатывается. |
T14-L7 1.76 c | Doctrine | For a managed entity, changing a property is enough: flush() commits the change without an explicit persist() — the Unit of Work tracks changes. | «yes» Пояснение: Once an entity is managed, the Unit of Work automatically tracks property modifications, so a flush() is all that's needed to persist the changes.
Raw{"answer": "yes", "explanation": "Once an entity is managed, the Unit of Work automatically tracks property modifications, so a flush() is all that's needed to persist the changes."} | верно | Dirty checking сравнивает снимки свойств; persist нужен только новым/отсоединённым объектам. |
T14-L8 1.43 c | Doctrine | remove() executes the SQL DELETE immediately, without waiting for flush(). | «no» Пояснение: In Doctrine ORM, remove() only marks the entity for deletion in the Unit of Work; the actual SQL DELETE is not executed until flush() is called.
Raw{"answer": "no", "explanation": "In Doctrine ORM, remove() only marks the entity for deletion in the Unit of Work; the actual SQL DELETE is not executed until flush() is called."} | верно | remove() планирует удаление в Unit of Work; DELETE выполняется на flush() (docs — Deleting Objects). |
T15-L1 2.4 c | PostgreSQL | PostgreSQL uses MVCC, therefore readers block writers and writers block readers. | «no» Пояснение: MVCC in PostgreSQL is specifically designed so that readers and writers do NOT block each other; readers see a snapshot at their transaction start and writers can proceed without waiting for readers.
Raw{"answer": "no", "explanation": "MVCC in PostgreSQL is specifically designed so that readers and writers do NOT block each other; readers see a snapshot at their transaction start and writers can proceed without waiting for readers."} | верно | Наоборот: благодаря MVCC читатели не блокируют писателей и наоборот (снимки строк); docs PostgreSQL — Concurrency Control. |
T15-L2 1.25 c | PostgreSQL | Which SQL command shows a query's execution plan without executing the query? | «explain» Пояснение: The EXPLAIN SQL command displays the query execution plan without actually running the query.
Raw{"answer": "EXPLAIN", "explanation": "The EXPLAIN SQL command displays the query execution plan without actually running the query."} | верно | EXPLAIN без ANALYZE только строит план; проверено на PostgreSQL 17.7. |
T15-L3 4.6 c | PostgreSQL | SERIAL and GENERATED ... AS IDENTITY are just two names for the same mechanism. | «no» Пояснение: While both create an auto-incrementing sequence-backed column in PostgreSQL, they are distinct mechanisms: SERIAL is a PostgreSQL-specific shorthand (a column with a DEFAULT nextval() constraint), whereas GENERATED ... AS IDENTITY is a SQL:2003 standard feature with additional options (ALWAYS vs BY DEFAULT) and a different internal implementation.
Raw{"answer": "no", "explanation": "While both create an auto-incrementing sequence-backed column in PostgreSQL, they are distinct mechanisms: SERIAL is a PostgreSQL-specific shorthand (a column with a DEFAULT nextval() constraint), whereas GENERATED ... AS IDENTITY is a SQL:2003 standard feature with additional options (ALWAYS vs BY DEFAULT) and a different internal implementation."} | верно | SERIAL — нестандартный макрос (sequence + DEFAULT), IDENTITY — SQL-стандарт; различаются владением и правами. Оба есть в PG 17 (проверено). |
T15-L4 1.56 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 not equal to each other, so a UNIQUE constraint allows multiple rows with NULL in the column.
Raw{"answer": "no", "explanation": "By default, PostgreSQL treats NULL values as not equal to each other, so a UNIQUE constraint allows multiple rows with NULL in the column."} | верно | Наоборот: NULLS DISTINCT по умолчанию — несколько NULL допустимы; NULLS NOT DISTINCT — опция с PG 15. Проверено на PG 17.7. |
T15-L5 0.78 c | PostgreSQL | Which PostgreSQL aggregate function concatenates strings with a separator? | «string_agg» Пояснение: string_agg is the PostgreSQL aggregate function that concatenates strings using a specified separator.
Raw{"answer": "string_agg", "explanation": "string_agg is the PostgreSQL aggregate function that concatenates strings using a specified separator."} | верно | string_agg(значение, разделитель); проверено на PostgreSQL 17.7. |
T15-L6 2.55 c | PostgreSQL | Plain VACUUM returns the space occupied by dead tuples to the operating system. | «no» Пояснение: Plain VACUUM in PostgreSQL reclaims space for reuse within the table but does not return disk space to the operating system; only VACUUM FULL does that.
Raw{"answer": "no", "explanation": "Plain VACUUM in PostgreSQL reclaims space for reuse within the table but does not return disk space to the operating system; only VACUUM FULL does that."} | верно | VACUUM помечает место для переиспользования внутри таблицы; ОС его возвращает только VACUUM FULL (с эксклюзивной блокировкой). |
T15-L7 0.81 c | PostgreSQL | Which keyword in a window function definition partitions rows into groups the function is computed over? | «partition by» Пояснение: In SQL window function definitions, PARTITION BY specifies the grouping of rows over which the window function is computed.
Raw{"answer": "PARTITION BY", "explanation": "In SQL window function definitions, PARTITION BY specifies the grouping of rows over which the window function is computed."} | верно | OVER (PARTITION BY ...); проверено на PostgreSQL 17.7. |
T15-L8 3.27 c | PostgreSQL | The READ COMMITTED isolation level protects against non-repeatable reads. | «no» Пояснение: READ COMMITTED only prevents dirty reads; non-repeatable reads are prevented by the REPEATABLE READ isolation level.
Raw{"answer": "no", "explanation": "READ COMMITTED only prevents dirty reads; non-repeatable reads are prevented by the REPEATABLE READ isolation level."} | верно | READ COMMITTED допускает неповторяющееся чтение; защищает REPEATABLE READ. Проверено: SHOW transaction_isolation → read committed. |
T17-L1 1.19 c | PostgreSQL: transactions and indexes | By default, PostgreSQL wraps each single SQL statement in its own implicit transaction (autocommit). | «yes» Пояснение: PostgreSQL's default mode is autocommit, meaning each SQL statement is executed and committed as its own implicit transaction unless you explicitly start one with BEGIN.
Raw{"answer": "yes", "explanation": "PostgreSQL's default mode is autocommit, meaning each SQL statement is executed and committed as its own implicit transaction unless you explicitly start one with BEGIN."} | верно | Без BEGIN каждый оператор коммитится сам; docs PostgreSQL — Transactions. Проверено на PG 17. |
T17-L2 0.61 c | PostgreSQL: transactions and indexes | Which SQL command ends a transaction, committing all its changes? | «commit» Пояснение: The COMMIT statement is used to save all changes made within a transaction and permanently apply them to the database.
Raw{"answer": "COMMIT", "explanation": "The COMMIT statement is used to save all changes made within a transaction and permanently apply them to the database."} | верно | COMMIT (END — синоним). Проверено на PG 17. |
T17-L3 1.38 c | PostgreSQL: transactions and indexes | Indexes speed up more than SELECT: UPDATE and DELETE with a search on an indexed column benefit too. | «yes» Пояснение: Indexes are used by the query optimizer for any statement that needs to locate rows via a WHERE condition on the indexed column, including UPDATE and DELETE, not just SELECT.
Raw{"answer": "yes", "explanation": "Indexes are used by the query optimizer for any statement that needs to locate rows via a WHERE condition on the indexed column, including UPDATE and DELETE, not just SELECT."} | верно | Поиск строк для изменения идёт по индексу; docs PostgreSQL — Indexes. |
T17-L4 1.57 c | PostgreSQL: transactions and indexes | To roll back part of the statements inside a transaction, PostgreSQL uses SAVEPOINT. | «yes» Пояснение: SAVEPOINT creates a named checkpoint within a transaction, and ROLLBACK TO <savepoint> undoes only the statements executed after that point without aborting the entire transaction.
Raw{"answer": "yes", "explanation": "SAVEPOINT creates a named checkpoint within a transaction, and ROLLBACK TO <savepoint> undoes only the statements executed after that point without aborting the entire transaction."} | верно | SAVEPOINT name; ROLLBACK TO name — частичный откат без отмены всей транзакции. Проверено на PG 17. |
T17-L5 1.5 c | PostgreSQL: transactions and indexes | EXPLAIN ANALYZE shows the query plan without executing the query. | «no» Пояснение: EXPLAIN ANALYZE actually executes the query to gather real execution statistics (e.g., actual row counts and timing), whereas plain EXPLAIN shows the plan without executing.
Raw{"answer": "no", "explanation": "EXPLAIN ANALYZE actually executes the query to gather real execution statistics (e.g., actual row counts and timing), whereas plain EXPLAIN shows the plan without executing."} | верно | Наоборот: ANALYZE реально выполняет запрос (с побочными эффектами!) и показывает фактические времена узлов; план без выполнения — plain EXPLAIN. |
T17-L6 1.39 c | PostgreSQL: transactions and indexes | Which PostgreSQL extension adds vector types and indexes for embedding search? | «pgvector» Пояснение: pgvector is a PostgreSQL extension that introduces vector types, distance operators, and index types (HNSW, IVFFlat) designed for embedding and vector similarity search.
Raw{"answer":"pgvector","explanation":"pgvector is a PostgreSQL extension that introduces vector types, distance operators, and index types (HNSW, IVFFlat) designed for embedding and vector similarity search."} | верно | CREATE EXTENSION vector (проект pgvector; в проекте образ pgvector/pgvector:pg17). |
T17-L7 1.09 c | PostgreSQL: transactions and indexes | A partial index (CREATE INDEX ... WHERE ...) is built only over rows satisfying the condition. | «yes» Пояснение: A partial index only contains index entries for rows that match the WHERE condition, reducing index size and improving query performance on filtered data.
Raw{"answer": "yes", "explanation": "A partial index only contains index entries for rows that match the WHERE condition, reducing index size and improving query performance on filtered data."} | верно | docs PostgreSQL — Partial Indexes; типичный кейс — индекс по «активным» записям. |
T17-L8 3.6 c | PostgreSQL: transactions and indexes | The SERIALIZABLE level in PostgreSQL is implemented by locking the rows a transaction reads. | «no» Пояснение: PostgreSQL implements SERIALIZABLE via Serializable Snapshot Isolation (SSI), which uses a snapshot-based mechanism and conflict detection (dependency graph) rather than locking rows a transaction reads.
Raw{"answer": "no", "explanation": "PostgreSQL implements SERIALIZABLE via Serializable Snapshot Isolation (SSI), which uses a snapshot-based mechanism and conflict detection (dependency graph) rather than locking rows a transaction reads."} | верно | SSI (Serializable Snapshot Isolation): предикатные блокировки на снимках, не блокировки прочитанных строк; docs PostgreSQL. |
T19-L1 0.83 c | HTTP and REST API | HTTP status 201 means the request resulted in a new resource being created. | «yes» Пояснение: HTTP status 201 'Created' is returned when a resource has been successfully created in response to a request, such as a POST.
Raw{"answer": "yes", "explanation": "HTTP status 201 'Created' is returned when a resource has been successfully created in response to a request, such as a POST."} | верно | 201 Created; обычно на POST, часто с Location; RFC 9110. |
T19-L2 1.54 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 the request succeeded and the server is intentionally not returning a response body, commonly used after DELETE operations.
Raw{"answer": 204, "explanation": "HTTP 204 (No Content) indicates the request succeeded and the server is intentionally not returning a response body, commonly used after DELETE operations."} | верно | 204 No Content; RFC 9110. |
T19-L3 4.07 c | HTTP and REST API | The DELETE method is idempotent per the HTTP specification: repeating the request for the same resource does not change the outcome. | «yes» Пояснение: Per RFC 7231 Section 4.1, the DELETE method is defined as idempotent, meaning a repeated request for the same resource produces the same outcome (e.g., a 410 Gone if already deleted).
Raw{"answer":"yes","explanation":"Per RFC 7231 Section 4.1, the DELETE method is defined as idempotent, meaning a repeated request for the same resource produces the same outcome (e.g., a 410 Gone if already deleted)."} | верно | RFC 9110: DELETE идемпотентен (как PUT); идемпотентность ≠ безопасность — ресурс удаляется при первом вызове. |
T19-L4 2.54 c | HTTP and REST API | The Access-Control-Allow-Origin header is sent by the client so that the server agrees to accept requests from another origin. | «no» Пояснение: The Access-Control-Allow-Origin header is sent by the server in its response to inform the browser that it permits the requesting origin to access the resource, not the other way around.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "The Access-Control-Allow-Origin header is sent by the server in its response to inform the browser that it permits the requesting origin to access the resource, not the other way around." ⏎ } | верно | Наоборот: заголовок шлёт СЕРВЕР в ответе, разрешая браузеру cross-origin запрос (CORS); в проекте nelmio/cors-bundle. |
T19-L5 1.29 c | HTTP and REST API | Status 429 Too Many Requests is used when a client exceeds a rate limit. | «yes» Пояснение: HTTP status 429 Too Many Requests is specifically defined in RFC 6585 as a response indicating the client has made too many requests in a given period of time, i.e., it has exceeded a rate limit.
Raw{"answer": "yes", "explanation": "HTTP status 429 Too Many Requests is specifically defined in RFC 6585 as a response indicating the client has made too many requests in a given period of time, i.e., it has exceeded a rate limit."} | верно | 429 (+ Retry-After); RFC 6585. В проекте symfony/rate-limiter. |
T19-L6 1.05 c | HTTP and REST API | 5xx codes mean a client error, while 4xx means a server-side error. | «no» Пояснение: It's the other way around: 4xx codes indicate client errors, while 5xx codes indicate server errors.
Raw{"answer": "no", "explanation": "It's the other way around: 4xx codes indicate client errors, while 5xx codes indicate server errors."} | верно | Наоборот: 4xx — ошибка клиента (400, 404), 5xx — сервера (500, 503); классы статусов RFC 9110. |
T19-L7 0.95 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 (media) type of the request or response body.
Raw{"answer": "Content-Type", "explanation": "The Content-Type HTTP header specifies the MIME (media) type of the request or response body."} | верно | Content-Type: application/json и т.п. |
T19-L8 1.59 c | HTTP and REST API | PATCH is not required to be idempotent per RFC 5789, unlike PUT. | «yes» Пояснение: RFC 5789 explicitly states that unlike PUT, PATCH is not required to be idempotent.
Raw{"answer": "yes", "explanation": "RFC 5789 explicitly states that unlike PUT, PATCH is not required to be idempotent."} | верно | RFC 5789 прямо оговаривает: PATCH не гарантированно идемпотентен; PUT идемпотентен. |
T20-L1 2.1 c | Security and OAuth | Checking a password by comparing its hash to the stored hash with a plain == is sufficient. | «no» Пояснение: In PHP, you should use password_verify() (which performs a constant-time comparison and correctly handles the algorithm and cost embedded in the hash string) rather than a plain ==, which is vulnerable to timing attacks.
Raw{"answer":"no","explanation":"In PHP, you should use password_verify() (which performs a constant-time comparison and correctly handles the algorithm and cost embedded in the hash string) rather than a plain ==, which is vulnerable to timing attacks."} | верно | Нужна постоянновременная проверка (password_verify) — timing-атаки; соль и алгоритм уже внутри хеша. |
T20-L2 1.76 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 and stored on the server (tied to the session), then validated by server-side code on state-changing requests like POST, PUT, or DELETE to prevent cross-site request forgery.
Raw{"answer":"yes","explanation":"A CSRF token is generated and stored on the server (tied to the session), then validated by server-side code on state-changing requests like POST, PUT, or DELETE to prevent cross-site request forgery."} | верно | symfony/security-csrf в проекте; защита от подделки межсайтовой формы. |
T20-L3 0.87 c | Security and OAuth | Which HTTP header enables the CSP (Content Security Policy) policy? | «content-security-policy» Пояснение: The Content-Security-Policy HTTP header is used to declare the set of resources from which a web page can load scripts and stylesheets.
Raw{"answer": "Content-Security-Policy", "explanation": "The Content-Security-Policy HTTP header is used to declare the set of resources from which a web page can load scripts and stylesheets."} | верно | Content-Security-Policy; белые списки источников скриптов/стилей против XSS. |
T20-L4 2.55 c | Security and OAuth | OAuth 2.0 is an authentication protocol: the access token tells you who the user is. | «no» Пояснение: OAuth 2.0 is an authorization framework, not an authentication protocol; it grants access to resources without requiring the user's credentials, and authentication is handled separately (e.g., via OpenID Connect).
Raw{"answer": "no", "explanation": "OAuth 2.0 is an authorization framework, not an authentication protocol; it grants access to resources without requiring the user's credentials, and authentication is handled separately (e.g., via OpenID Connect)."} | верно | OAuth 2.0 — авторизация/делегирование доступа; аутентификацию добавляет OpenID Connect. В проекте knpuniversity/oauth2-client-bundle (yandex/github/google). |
T20-L5 2.63 c | Security and OAuth | XSS is prevented by validating input on the server before writing it to the database. | «no» Пояснение: XSS is prevented by proper output encoding/escaping when rendering data in HTML, not by input validation before storage; input validation does not guarantee that stored data is safe when later displayed in a browser context.
Raw{"answer": "no", "explanation": "XSS is prevented by proper output encoding/escaping when rendering data in HTML, not by input validation before storage; input validation does not guarantee that stored data is safe when later displayed in a browser context."} | верно | XSS лечится контекстным экранированием НА ВЫВОДЕ (Twig autoescape, CSP); валидация ввода не покрывает все контексты вывода. |
T20-L6 1.29 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 authorization code (parameter 'code') is returned via the redirect_uri and subsequently exchanged for an access token.
Raw{"answer": "code", "explanation": "In the OAuth 2.0 authorization code flow, the authorization code (parameter 'code') is returned via the redirect_uri and subsequently exchanged for an access token."} | верно | Параметр code; обмен на токен POST-ом на /token с client_secret. |
T20-L7 1.4 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» Пояснение: In OAuth 2.0, refresh tokens have a much longer expiry than access tokens and are specifically designed to exchange for a new access token without requiring the user to re-authenticate.
Raw{"answer": "yes", "explanation": "In OAuth 2.0, refresh tokens have a much longer expiry than access tokens and are specifically designed to exchange for a new access token without requiring the user to re-authenticate."} | верно | Стандартная схема OAuth/OIDC: короткий access + длинный refresh. |
T20-L8 3.17 c | Security and OAuth | A password salt must be kept secret: without it the hash cannot be verified. | «no» Пояснение: A password salt is not required to be secret; it is typically stored alongside the hash (e.g., in the database or encoded in the hash string) because its purpose is to defeat rainbow-table precomputation, not to provide secrecy.
Raw{"answer":"no","explanation":"A password salt is not required to be secret; it is typically stored alongside the hash (e.g., in the database or encoded in the hash string) because its purpose is to defeat rainbow-table precomputation, not to provide secrecy."} | верно | Соль хранится открыто (password_hash включает её в строку хеша); секретность соли не нужна. |
T18-L1 2.33 c | Testing: PHPUnit | PHPUnit runs test methods of any class — extending TestCase is not required. | «no» Пояснение: In PHPUnit, test classes must extend PHPUnit\Framework\TestCase (or a subclass) for the test runner to discover and execute the test methods.
Raw{"answer": "no", "explanation": "In PHPUnit, test classes must extend PHPUnit\\Framework\\TestCase (or a subclass) for the test runner to discover and execute the test methods."} | верно | Тестом считается метод класса, наследующего TestCase (PHPUnit 10). |
T18-L2 3.85 c | Testing: PHPUnit | In PHPUnit, setUp() runs once before all tests of the class. | «no» Пояснение: setUp() runs before each individual test in the class; it is setUpBeforeClass() (a static method) that runs once before all tests of the class.
Raw{"answer":"no","explanation":"setUp() runs before each individual test in the class; it is setUpBeforeClass() (a static method) that runs once before all tests of the class."} | верно | setUp() — перед КАЖДЫМ тестом; один раз на класс — setUpBeforeClass(). Проверено живым счётчиком на PHPUnit 10.5. |
T18-L3 1.84 c | Testing: PHPUnit | A data provider lets a test run with exactly one set of arguments. | «no» Пояснение: A data provider is used to let a test run with multiple sets of arguments, not just one.
Raw{"answer": "no", "explanation": "A data provider is used to let a test run with multiple sets of arguments, not just one."} | верно | Наоборот: наборов может быть сколько угодно — тест выполняется по разу на каждый. Проверено на PHPUnit 10.5 (#[DataProvider]). |
T18-L4 0.93 c | Testing: PHPUnit | Which PHPUnit method declares an expectation that an exception of a given class is thrown? | «expectexception» Пояснение: expectException() is the PHPUnit method that declares an expectation that an exception of a given class will be thrown by the code under test.
Raw{"answer": "expectException", "explanation": "expectException() is the PHPUnit method that declares an expectation that an exception of a given class will be thrown by the code under test."} | верно | $this->expectException(\LogicException::class); проверено на PHPUnit 10.5. |
T18-L5 2.62 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 mock verifies which methods were called, while a stub only returns predefined data.
Raw{"answer":"no","explanation":"It's the opposite: a mock verifies which methods were called, while a stub only returns predefined data."} | верно | Наоборот: стаб подставляет данные, мок проверяет взаимодействия (createStub/createMock); docs PHPUnit — Test Doubles. |
T18-L6 5.14 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, PHP attributes like #[DataProvider] replaced the old PHPDoc annotations, which were removed from support.
Raw{"answer": "yes", "explanation": "In PHPUnit 10, PHP attributes like #[DataProvider] replaced the old PHPDoc annotations, which were removed from support."} | верно | Аннотация ещё парсится в PHPUnit 10/11 (AnnotationParser в 10.5.66), удаление — в 12; атрибут — стандарт. |
T18-L7 1.24 c | Testing: PHPUnit | PHPUnit does not allow one test to depend on the result of another. | «no» Пояснение: PHPUnit does support test dependencies via the @depends annotation or the dependsOn() method, allowing one test to run after (and depend on the output of) another test.
Raw{"answer": "no", "explanation": "PHPUnit does support test dependencies via the @depends annotation or the dependsOn() method, allowing one test to run after (and depend on the output of) another test."} | верно | Зависимости есть: #[Depends] — зависимый тест не запустится, еслиProducer упал. |
T18-L8 1.04 c | Testing: PHPUnit | Which PHPUnit command-line option makes tests run in random order? | «--random-order» Пояснение: PHPUnit provides the --random-order CLI option to shuffle and run test methods in a random order.
Raw{"answer": "--random-order", "explanation": "PHPUnit provides the --random-order CLI option to shuffle and run test methods in a random order."} | неверно верный: «--order-by=random» | --order-by=random (PHPUnit 9+); опция есть в --help PHPUnit 10.5 (проектная). |
T01-L9 4.75 c | Syntax and operators | What does this code output?
```php
echo intdiv(7, 2) . intdiv(-7, 2);
``` | «3-4» Пояснение: intdiv(7, 2) equals 3 and intdiv(-7, 2) equals -4 (truncates toward negative infinity), so the concatenated string is "3-4".
Raw{"answer": "3-4", "explanation": "intdiv(7, 2) equals 3 and intdiv(-7, 2) equals -4 (truncates toward negative infinity), so the concatenated string is \"3-4\"."} | неверно верный: «3-3» | intdiv truncates toward zero: intdiv(-7, 2) = -3, not -4. |
T01-L10 1.25 c | Syntax and operators | What does this code output?
```php
echo -3 ** 2;
``` | «-9» Пояснение: The `**` operator has higher precedence than the unary `-`, so the expression is evaluated as `-(3 ** 2)` which equals -9.
Raw{"answer": -9, "explanation": "The `**` operator has higher precedence than the unary `-`, so the expression is evaluated as `-(3 ** 2)` which equals -9."} | верно | ** is right-associative and binds tighter than unary minus: -(3²). |
T02-L9 1.92 c | Types and comparisons | What does this code output?
```php
echo '1e1' == '10' ? 'true' : 'false';
``` | «true» Пояснение: In PHP, the loose equality operator (==) converts numeric strings to numbers before comparing, so '1e1' (which equals 10) == '10' is true, resulting in the string 'true' being echoed.
Raw{"answer": "true", "explanation": "In PHP, the loose equality operator (==) converts numeric strings to numbers before comparing, so '1e1' (which equals 10) == '10' is true, resulting in the string 'true' being echoed."} | верно | Both strings are numeric — compared as numbers: 10 == 10. |
T02-L10 2.11 c | Types and comparisons | What does this code output?
```php
switch ('a') {
case 0: echo 'zero'; break;
default: echo 'other';
}
``` | «other» Пояснение: In PHP, switch uses strict comparison (===), and the string 'a' does not match the integer 0, so it falls through to the default case which echoes 'other'.
Raw{"answer":"other","explanation":"In PHP, switch uses strict comparison (===), and the string 'a' does not match the integer 0, so it falls through to the default case which echoes 'other'."} | верно | PHP 8: 'a' == 0 → false (used to be true) — default fires. |
T03-L9 4.34 c | Strings | What does this code output?
```php
echo strtr('abc', ['a' => '1', 'ab' => '2']);
``` | «2c» Пояснение: strtr performs simultaneous replacements and uses the longest match at each position, so 'ab' (length 2) is replaced with '2' before 'a' (length 1) could match, leaving 'c' unchanged.
Raw{"answer": "2c", "explanation": "strtr performs simultaneous replacements and uses the longest match at each position, so 'ab' (length 2) is replaced with '2' before 'a' (length 1) could match, leaving 'c' unchanged."} | верно | strtr with an array prefers the longest matching key. |
T03-L10 2.77 c | Strings | What does this code output?
```php
echo '[' . substr('hello', -10) . ']';
``` | «[hello]» Пояснение: The string 'hello' is only 5 characters long, so starting at position -10 is before the start of the string; PHP clamps the start to 0 and returns the entire string 'hello'.
Raw{"answer": "[hello]", "explanation": "The string 'hello' is only 5 characters long, so starting at position -10 is before the start of the string; PHP clamps the start to 0 and returns the entire string 'hello'."} | верно | A negative start beyond the string is clamped to the beginning. |
T04-L9 2.64 c | Arrays | What does this code output?
```php
$a = ['k' => 1, 'n' => 2];
$b = ['k' => 9, 'm' => 3];
echo implode(',', array_keys($a + $b));
``` | «k,n,m» Пояснение: The + operator merges arrays keeping the left value for duplicate keys, preserving order: k(1), n(2), m(3); array_keys returns ['k','n','m'] which implode outputs as "k,n,m".
Raw{"answer": "k,n,m", "explanation": "The + operator merges arrays keeping the left value for duplicate keys, preserving order: k(1), n(2), m(3); array_keys returns ['k','n','m'] which implode outputs as \"k,n,m\"."} | верно | The + operator: on duplicate string keys the left array wins. |
T04-L10 3.12 c | Arrays | What does this code output?
```php
$a = [[1, 'x', 2], [2, 'y', 1], [3, 'z', 2]];
usort($a, fn($p, $q) => $p[2] <=> $q[2]);
echo implode('', array_column($a, 1));
``` | «yxz» Пояснение: usort sorts by the third element (index 2): values 1, 2, 2 → [2,'y',1], [1,'x',2], [3,'z',2], then array_column extracts the 'y', 'x', 'z' strings which implode into "yxz".
Raw{"answer": "yxz", "explanation": "usort sorts by the third element (index 2): values 1, 2, 2 → [2,'y',1], [1,'x',2], [3,'z',2], then array_column extracts the 'y', 'x', 'z' strings which implode into \"yxz\"."} | верно | Sorts are stable since 8.0: x and z keep their order on a tie. |
T05-L10 1.78 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 on an associative array unpacks values as named arguments, so it's equivalent to f(a: 5, b: 1), which returns 5 - 1 = 4.
Raw```json ⏎ {"answer": "4", "explanation": "The spread operator on an associative array unpacks values as named arguments, so it's equivalent to f(a: 5, b: 1), which returns 5 - 1 = 4."} ⏎ ``` | верно | String keys of a spread array become named arguments. |
T05-L9 8.59 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();
``` | «syntaxerror» Пояснение: The code `$p->g(...)` uses the spread operator `...` without a following array expression, which is a parse error in PHP.
Raw{ ⏎ "answer": "SyntaxError", ⏎ "explanation": "The code `$p->g(...)` uses the spread operator `...` without a following array expression, which is a parse error in PHP." ⏎ } | неверно верный: «3» | First-class callable syntax binds $this at creation time. |
T06-L9 0.98 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 refers to the actual class of the object (late static binding), so it returns 'B' rather than 'A'.
Raw{"answer": "B", "explanation": "static::class refers to the actual class of the object (late static binding), so it returns 'B' rather than 'A'."} | верно | Late static binding: static::class is the receiver's class. |
T06-L10 17.1 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» Пояснение: In PHP 8.5, property hooks are supported; the setter stores $value * 2 (5 * 2 = 10) in the backing property, and since no getter hook is defined, reading $c->x returns the raw backing value of 10.
Raw{"answer": 10, "explanation": "In PHP 8.5, property hooks are supported; the setter stores $value * 2 (5 * 2 = 10) in the backing property, and since no getter hook is defined, reading $c->x returns the raw backing value of 10."} | верно | Inside the set hook, $this->x writes the backing store (no recursion): 5*2. |
T07-L9 1.99 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 overrides TA::f for method f(), so f() returns 'B'; TA::f is aliased as g(), so g() returns 'A', giving the concatenated string 'BA'.
Raw{"answer":"BA","explanation":"TB::f overrides TA::f for method f(), so f() returns 'B'; TA::f is aliased as g(), so g() returns 'A', giving the concatenated string 'BA'."} | верно | insteadof picks the implementation; as keeps the other under an alias. |
T07-L10 4.11 c | Interfaces, traits, enum | What does this code output?
```php
trait Counter
{
public static int $n = 0;
}
class CX { use Counter; }
class CY { use Counter; }
CX::$n = 1;
echo CY::$n;
``` | «0» Пояснение: Each class that uses a trait gets its own independent copy of the trait's static properties, so CY::$n remains 0 after CX::$n is set to 1.
Raw{"answer": 0, "explanation": "Each class that uses a trait gets its own independent copy of the trait's static properties, so CY::$n remains 0 after CX::$n is set to 1."} | верно | A trait's static property is copied into each consuming class. |
T08-L10 2.69 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 the finally block overrides the return value of the try block, so the function returns 2.
Raw```json ⏎ {"answer": 2, "explanation": "In PHP, a return statement in the finally block overrides the return value of the try block, so the function returns 2."} ⏎ ``` | верно | A return in finally overrides the return from try. |
T08-L9 2.34 c | Exceptions and errors | What does this code output?
```php
try {
try {
throw new RuntimeException('first');
} finally {
throw new LogicException('second');
}
} catch (LogicException $e) {
echo $e->getMessage();
}
``` | «second» Пояснение: The RuntimeException in the inner try triggers the finally block, where a LogicException is thrown, which replaces the original exception and is caught by the outer catch handler.
Raw{"answer": "second", "explanation": "The RuntimeException in the inner try triggers the finally block, where a LogicException is thrown, which replaces the original exception and is caught by the outer catch handler."} | верно | An exception from finally replaces the in-flight one — the last thrown is caught. |
T09-L9 3.1 c | Namespaces and autoloading | What does this code output?
```php
namespace N;
use App\Foo as Baz;
echo Baz::class . '|' . \Baz::class;
``` | «app\foo|baz» Пояснение: Baz::class resolves to App\Foo (the alias defined by the use statement), while \Baz::class resolves to Baz in the global namespace.
Raw```json ⏎ {"answer": "App\\Foo|Baz", "explanation": "Baz::class resolves to App\\Foo (the alias defined by the use statement), while \\Baz::class resolves to Baz in the global namespace."} ⏎ ``` | верно | The use alias applies to unqualified names; a leading \ escapes to the global scope. |
T09-L10 4.13 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');
``` | «yesyes» Пояснение: class_exists('Foo') resolves 'Foo' against the current namespace Ns and finds Ns\Foo (yes), and class_exists('Ns\Foo') directly finds the class (yes), so the output is 'yesyes'.
Raw{"answer": "yesyes", "explanation": "class_exists('Foo') resolves 'Foo' against the current namespace Ns and finds Ns\\Foo (yes), and class_exists('Ns\\Foo') directly finds the class (yes), so the output is 'yesyes'."} | неверно верный: «noyes» | Dynamic names are not resolved against the namespace — 'Foo' is the global class. |
T10-L9 2.39 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» Пояснение: Using foreach with a reference (&$v) makes $v a reference to the last element of the array even after the loop ends, so assigning 99 to $v modifies the third element of $a.
Raw```json ⏎ {"answer": "1,2,99", "explanation": "Using foreach with a reference (&$v) makes $v a reference to the last element of the array even after the loop ends, so assigning 99 to $v modifies the third element of $a."} ⏎ ``` | верно | After a by-ref foreach, $v remains a reference to the last element. |
T10-L10 2.35 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 belong to the class (A), not individual instances; the three calls to inc() increment the same static counter, and the third call returns 3.
Raw{"answer": "3", "explanation": "Static variables belong to the class (A), not individual instances; the three calls to inc() increment the same static counter, and the third call returns 3."} | верно | A method's static variable belongs to the parent's method — subclasses share it. |
T11-L9 5.18 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();
``` | «—» Пояснение: After $g->send(10) the generator is still paused at the yield statement and has not reached the return, so $g->getReturn() returns null, which echo prints as an empty string.
Raw{"answer": "", "explanation": "After $g->send(10) the generator is still paused at the yield statement and has not reached the return, so $g->getReturn() returns null, which echo prints as an empty string."} | неверно верный: «11» | send() resumes the generator: $x = 10, return 10+1. |
T11-L10 2.87 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 from inner, then the return value 'ok' is stored in $r and yielded, so the generator yields 1, 2, 'ok', which implode joins into '1,2,ok'.
Raw{"answer": "1,2,ok", "explanation": "yield from inner() yields 1 and 2 from inner, then the return value 'ok' is stored in $r and yielded, so the generator yields 1, 2, 'ok', which 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.5 c | Configuration and security | What does this code output?
```php
$hash = password_hash('x', PASSWORD_BCRYPT, ['cost' => 4]);
echo password_needs_rehash($hash, PASSWORD_BCRYPT, ['cost' => 4]) ? 'yes' : 'no';
echo password_needs_rehash($hash, PASSWORD_BCRYPT, ['cost' => 5]) ? 'yes' : 'no';
``` | «noyes» Пояснение: The first check compares cost 4 with the existing cost 4 (no rehash needed), the second checks cost 5 against existing cost 4 (rehash needed).
Raw{"answer": "noyes", "explanation": "The first check compares cost 4 with the existing cost 4 (no rehash needed), the second checks cost 5 against existing cost 4 (rehash needed)."} | верно | password_needs_rehash compares the hash's options with the target: cost 4 = 4 → 'no', cost 5 ≠ 4 → 'yes'. |
T12-L10 10.74 c | Configuration and security | What does this code output on PHP 8.5?
```php
echo (E_ALL & 2048) === 0 ? 'strict-out' : 'strict-in';
``` | «strict-out» Пояснение: In PHP 8.5, E_STRICT (2048) was removed from E_ALL (it was deprecated since 7.2 and removed in 8.3), so E_ALL & 2048 equals 0, making the ternary evaluate to 'strict-out'.
Raw```json ⏎ {"answer": "strict-out", "explanation": "In PHP 8.5, E_STRICT (2048) was removed from E_ALL (it was deprecated since 7.2 and removed in 8.3), so E_ALL & 2048 equals 0, making the ternary evaluate to 'strict-out'."} ⏎ ``` | верно | Since PHP 8.4, E_STRICT is out of E_ALL: the 2048 bit is unset → 'strict-out' (2048 is the historical E_STRICT bit). |
T13-L9 8.36 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';
``` | «missing» Пояснение: The header key 'HTTP_X_TOKEN' does not match 'X-Token' even case-insensitively, so get('X-Token') returns null, making the ternary evaluate to 'missing'.
Raw{"answer": "missing", "explanation": "The header key 'HTTP_X_TOKEN' does not match 'X-Token' even case-insensitively, so get('X-Token') returns null, making the ternary evaluate to 'missing'."} | неверно верный: «mapped» | 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 2.51 c | Symfony | What does this code output?
```php
use Symfony\Component\EventDispatcher\EventDispatcher;
use Symfony\Contracts\EventDispatcher\Event;
$d = new EventDispatcher();
$out = '';
$d->addListener('e', function () use (&$out) { $out .= 'B'; }, 10);
$d->addListener('e', function () use (&$out) { $out .= 'A'; });
$d->addListener('e', function () use (&$out) { $out .= 'C'; }, 5);
$d->dispatch(new Event(), 'e');
echo $out;
``` | «bca» Пояснение: Symfony EventDispatcher calls listeners in order of descending priority (higher first), with a default priority of 0, so 'B' (10), 'C' (5), and 'A' (0) execute in that order.
Raw{"answer":"BCA","explanation":"Symfony EventDispatcher calls listeners in order of descending priority (higher first), with a default priority of 0, so 'B' (10), 'C' (5), and 'A' (0) execute in that order."} | верно | Listeners run by descending priority: 10 (B), 5 (C), 0 (A). |
T14-L10 4.4 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 uses an identity map: after flush() the User is managed, so both find() calls hit the identity map and return the exact same object instance.
Raw{"answer": "same", "explanation": "Doctrine ORM uses an identity map: after flush() the User is managed, so both find() calls hit the identity map and return the exact same object instance."} | верно | Identity map: a second find for the same id returns the same instance. |
T14-L9 3.78 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» Пояснение: persist() only adds the entity to the Unit of Work without issuing SQL; remove() detaches it before any INSERT is ever executed, so flush() has nothing to persist, leaving the table empty.
Raw{"answer": 0, "explanation": "persist() only adds the entity to the Unit of Work without issuing SQL; remove() detaches it before any INSERT is ever executed, so flush() has nothing to persist, leaving the table empty."} | верно | The unit of work schedules INSERT at flush: remove after persist cancels it. |
T15-L10 1.59 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, so it returns 1 (the row with x=NULL is excluded).
Raw{"answer": 1, "explanation": "COUNT(x) counts only non-NULL values in column x, so it returns 1 (the row with x=NULL is excluded)."} | верно | count(column) skips NULLs; count(*) would return 2. |
T15-L9 3.23 c | PostgreSQL | What does this SQL query return (PostgreSQL 17)?
```sql
CREATE TEMP TABLE t (id int, x int);
INSERT INTO t VALUES (1, 10), (2, 20), (3, 30);
SELECT string_agg(s::text, ',' ORDER BY id) FROM (
SELECT id, sum(x) OVER (ORDER BY id) AS s FROM t
) q;
``` | «10,30,60» Пояснение: The window function SUM(x) OVER (ORDER BY id) produces running sums (10, 30, 60), which are then concatenated by string_agg in order to form '10,30,60'.
Raw{"answer": "10,30,60", "explanation": "The window function SUM(x) OVER (ORDER BY id) produces running sums (10, 30, 60), which are then concatenated by string_agg in order to form '10,30,60'."} | верно | With ORDER BY the default window frame is running (start to current row). |
T16-L9 3.29 c | Symfony: Messenger | What does this code output?
```php
use Symfony\Component\Messenger\MessageBus;
use Symfony\Component\Messenger\Middleware\MiddlewareInterface;
use Symfony\Component\Messenger\Middleware\StackInterface;
use Symfony\Component\Messenger\Envelope;
final class Trace implements MiddlewareInterface
{
public function __construct(private string $tag) {}
public function handle(Envelope $e, StackInterface $stack): Envelope
{
echo $this->tag;
return $stack->next()->handle($e, $stack);
}
}
$bus = new MessageBus([new Trace('M1'), new Trace('M2')]);
$bus->dispatch(new Envelope(new stdClass()));
``` | «m1m2» Пояснение: The middleware stack processes M1 first (echoing 'M1'), which then delegates to M2 (echoing 'M2') before reaching the end of the stack.
Raw{"answer": "M1M2", "explanation": "The middleware stack processes M1 first (echoing 'M1'), which then delegates to M2 (echoing 'M2') before reaching the end of the stack."} | верно | The first-added middleware runs first (outermost). |
T16-L10 6.66 c | Symfony: Messenger | What does this code output?
```php
use Symfony\Component\Messenger\MessageBus;
use Symfony\Component\Messenger\Middleware\HandleMessageMiddleware;
use Symfony\Component\Messenger\Handler\HandlersLocator;
use Symfony\Component\Messenger\Handler\HandlerDescriptor;
use Symfony\Component\Messenger\Envelope;
class Ping {}
$n = 0;
$d1 = new HandlerDescriptor(function (Ping $m) use (&$n) { $n += 1; }, ['alias' => 'h1']);
$d2 = new HandlerDescriptor(function (Ping $m) use (&$n) { $n += 10; }, ['alias' => 'h2']);
$bus = new MessageBus([
new HandleMessageMiddleware(new HandlersLocator([Ping::class => [$d1, $d2]])),
]);
$bus->dispatch(new Envelope(new Ping()));
echo $n;
``` | «11» Пояснение: HandleMessageMiddleware calls all registered handlers for Ping::class, so both closures execute: $n goes from 0 to 1 to 11.
Raw{"answer": 11, "explanation": "HandleMessageMiddleware calls all registered handlers for Ping::class, so both closures execute: $n goes from 0 to 1 to 11."} | верно | All registered handlers of the message run: 1 + 10 = 11. |
T17-L9 2.51 c | PostgreSQL: transactions and indexes | What does this SQL query return (PostgreSQL 17)?
```sql
CREATE TEMP TABLE t (a int);
CREATE UNIQUE INDEX ON t (a);
INSERT INTO t VALUES (1) ON CONFLICT DO NOTHING;
INSERT INTO t VALUES (1) ON CONFLICT DO NOTHING;
SELECT count(*) FROM t;
``` | «1» Пояснение: The first INSERT succeeds, adding one row; the second INSERT hits the unique index constraint on column a but ON CONFLICT DO NOTHING silently skips it, so the table has 1 row.
Raw{"answer": 1, "explanation": "The first INSERT succeeds, adding one row; the second INSERT hits the unique index constraint on column a but ON CONFLICT DO NOTHING silently skips it, so the table has 1 row."} | верно | ON CONFLICT DO NOTHING skips the duplicate: one insert. |
T17-L10 2.84 c | PostgreSQL: transactions and indexes | What does this sequence of psql commands output?
```sql
BEGIN;
CREATE TEMP TABLE t (a int, UNIQUE (a) DEFERRABLE INITIALLY DEFERRED);
INSERT INTO t VALUES (1);
INSERT INTO t VALUES (1);
SELECT count(*) FROM t;
``` | «2» Пояснение: Because the UNIQUE constraint is DEFERRABLE INITIALLY DEFERRED, the constraint is not checked until the transaction ends, so both inserts succeed and the count returns 2.
Raw{"answer": 2, "explanation": "Because the UNIQUE constraint is DEFERRABLE INITIALLY DEFERRED, the constraint is not checked until the transaction ends, so both inserts succeed and the count returns 2."} | верно | DEFERRED postpones the uniqueness check to COMMIT — count sees 2 rows. |
T18-L9 4.42 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 option uses a regex match, so 'test_sum' matches both test_sum and test_sum_abs (each with 3 data points from the data provider), giving 3 + 3 = 6 tests.
Raw{"answer": 6, "explanation": "The --filter option uses a regex match, so 'test_sum' matches both test_sum and test_sum_abs (each with 3 data points from the data provider), giving 3 + 3 = 6 tests."} | верно | --filter is a substring match: test_sum also matches test_sum_abs (3+3 datasets). |
T18-L10 1.9 c | Testing: PHPUnit | How many tests will this command run, and how many of them will fail? Answer with two comma-separated numbers (ran, failed).
```php
use PHPUnit\Framework\TestCase;
use PHPUnit\Framework\Attributes\DataProvider;
final class Calc2Test extends TestCase
{
public function prov(): array
{
return [[1], [-1]];
}
#[DataProvider('prov')]
public function test_x(int $x): void
{
$this->assertTrue($x > 0);
}
}
```
Command: `phpunit Calc2Test.php` (PHPUnit 10.5) | «2, 1» Пояснение: The data provider supplies two datasets ([1] and [-1]), so two test cases are executed; only the case with -1 fails the assertTrue($x > 0) assertion.
Raw{"answer": "2, 1", "explanation": "The data provider supplies two datasets ([1] and [-1]), so two test cases are executed; only the case with -1 fails the assertTrue($x > 0) assertion."} | верно | A non-static provider is just a deprecation in PHPUnit 10: both datasets run and the [-1] dataset fails the assert — 2 ran, 1 failure. |
T19-L9 1.13 c | HTTP and REST API | Which HTTP method does this command send?
```bash
curl -s -d 'a=1' http://demo.local/api
``` | «post» Пояснение: The -d flag in curl sends the data as the body of a POST request by default.
Raw{"answer": "POST", "explanation": "The -d flag in curl sends the data as the body of a POST request by default."} | верно | -d/-F switches curl to POST by default. |
T19-L10 1.67 c | HTTP and REST API | Which HTTP method does this command send?
```bash
curl -s -G -d 'a=1' http://demo.local/api
``` | «get» Пояснение: The -G flag forces curl to send the request using the GET method, appending the -d data as a URL query string instead of a POST body.
Raw{"answer": "GET", "explanation": "The -G flag forces curl to send the request using the GET method, appending the -d data as a URL query string instead of a POST body."} | верно | -G turns -d data into the query string; the method stays GET. |
T20-L9 5.81 c | Security and OAuth | A client hits the token endpoint (RFC 6749) with a non-existent client_id. What value of the error field does the endpoint return? | «invalid_client» Пояснение: Per RFC 6749 Section 5.3, when the client_id is invalid (non-existent), the token endpoint returns the error 'invalid_client'.
Raw{"answer": "invalid_client", "explanation": "Per RFC 6749 Section 5.3, when the client_id is invalid (non-existent), the token endpoint returns the error 'invalid_client'."} | верно | Unknown client → invalid_client (RFC 6749 §5.2). |
T20-L10 1.55 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 implicit grant (response_type=token), the access_token is returned in the fragment (the portion after #) of the redirect_uri, which prevents it from appearing in server logs.
Raw{"answer": "fragment", "explanation": "In the implicit grant (response_type=token), the access_token is returned in the fragment (the portion after #) of the redirect_uri, which prevents it from appearing in server logs."} | верно | The implicit flow passes the token in the URL fragment (#) — it never reaches the server. |
T21-L9 3.87 c | Twig | What does this Twig template output?
```twig
{{ false|default(2) * 3 }}
``` | «0» Пояснение: In Twig, the default filter only substitutes the fallback when the value is null; false is not null so it remains false, which is cast to 0 in arithmetic, giving 0 * 3 = 0.
Raw{"answer": 0, "explanation": "In Twig, the default filter only substitutes the fallback when the value is null; false is not null so it remains false, which is cast to 0 in arithmetic, giving 0 * 3 = 0."} | неверно верный: «6» | default replaces exactly false/null/''/[] — false becomes 2, 2*3 = 6; the naive 'default is for undefined only' yields 0. |
T21-L10 68.16 c | Twig | What exception class does render() of this template throw?
```twig
{{ 'a' ~ 1 + 2 }}
``` | «twig\error\compileerror» Пояснение: In Twig the `+` operator between a string ('a1') and an integer (2) raises a CompileError because mixed string/int arithmetic is not allowed.
Raw{"answer": "Twig\\Error\\CompileError", "explanation": "In Twig the `+` operator between a string ('a1') and an integer (2) raises a CompileError because mixed string/int arithmetic is not allowed."} | неверно верный: «runtimeerror» | In Twig ~ binds tighter than +: ('a' ~ 1) + 2 → string + int → a render error (RuntimeError). |
T22-L9 1.69 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()]));
``` | «1» Пояснение: The empty string '' violates the NotBlank constraint, so validate() returns one violation and count() returns 1.
Raw{"answer": 1, "explanation": "The empty string '' violates the NotBlank constraint, so validate() returns one violation and count() returns 1."} | неверно верный: «0» | NotBlank treats null, '', [] as blank — the array [''] is not blank. |
T22-L10 11.0 c | Symfony: Security and forms | What does this code output?
```php
use Symfony\Component\Form\Forms;
use Symfony\Component\Form\Extension\Core\Type\TextType;
$factory = Forms::createFormFactoryBuilder()->getFormFactory();
$form = $factory->create(TextType::class);
try {
echo $form->isValid() ? 'valid' : 'invalid';
} catch (Throwable $e) {
echo get_class($e);
}
``` | «invalid» Пояснение: Calling isValid() on a form that has not been submitted simply returns false because isSubmitted() is false, so 'invalid' is echoed.
Raw```json ⏎ {"answer": "invalid", "explanation": "Calling isValid() on a form that has not been submitted simply returns false because isSubmitted() is false, so 'invalid' is echoed."} ⏎ ``` | неверно верный: «symfony\component\form\exception\logicexception» | isValid() on a non-submitted form throws LogicException, it does not return false. |
T23-L9 3.15 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 compiled container caches service instances, so calling get('a') twice returns the same stdClass object, making both spl_object_id() calls equal.
Raw{"answer": "same", "explanation": "Symfony's compiled container caches service instances, so calling get('a') twice returns the same stdClass object, making both spl_object_id() calls equal."} | верно | Container services are shared: two get() calls yield one instance. |
T23-L10 22.97 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');
``` | «throws an exception (parameternotfoundexception): the parameter 'greeting!' was not found» Пояснение: In Symfony DI, the '!' before the closing '%' is part of the parameter name, so '%greeting!%' looks for a parameter named 'greeting!' which was never set (only 'greeting' was set).
Raw{"answer": "Throws an exception (ParameterNotFoundException): the parameter 'greeting!' was not found", "explanation": "In Symfony DI, the '!' before the closing '%' is part of the parameter name, so '%greeting!%' looks for a parameter named 'greeting!' which was never set (only 'greeting' was set)."} | неверно верный: «hi bob!» | compile() resolves %-references transitively: %greeting% → 'hi %name%' → 'hi Bob!', the answer assembles over two hops. |
T24-L9 3.41 c | Bootstrap | What is the max-width of .container in Bootstrap 5.3 at a 992px viewport? | «720» Пояснение: At a 992px viewport, the lg breakpoint (>= 992px) is active, giving .container a max-width of 720px in Bootstrap 5.3.
Raw{"answer": 720, "explanation": "At a 992px viewport, the lg breakpoint (>= 992px) is active, giving .container a max-width of 720px in Bootstrap 5.3."} | неверно верный: «960» | 5.x container widths: 540/720/960/1140/1320 (sm–xxl); 992 → 960px. |
T24-L10 6.75 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, .text-danger is defined after .text-primary in the CSS source, so it wins by last-in-source-order at the same specificity.
Raw{"answer": "text-danger", "explanation": "In Bootstrap 5.3, .text-danger is defined after .text-primary in the CSS source, so it wins by last-in-source-order at the same specificity."} | верно | Specificity ties — the later rule wins: text-danger is declared after text-primary. |
T25-L9 1.98 c | Clean architecture | Layers: Domain, Application, Infrastructure. Deptrac rules: Application → Domain; Infrastructure → Domain, Application; Domain → Domain only.
How many violations will deptrac report for this class?
```php
namespace App\Domain;
use App\Application\PlaceOrder;
use App\Infrastructure\Db;
class OrderService
{
public function __construct(
private PlaceOrder $handler,
private Db $db,
) {}
}
``` | «2» Пояснение: The Domain class depends on Application (PlaceOrder) and Infrastructure (Db), but Domain is only allowed to depend on Domain, so both are violations.
Raw{"answer": 2, "explanation": "The Domain class depends on Application (PlaceOrder) and Infrastructure (Db), but Domain is only allowed to depend on Domain, so both are violations."} | верно | Domain may depend only on Domain: PlaceOrder (Application) + Db (Infrastructure) = 2. |
T25-L10 6.31 c | Clean architecture | Layers: Domain, Application, Infrastructure. Deptrac rules: Application → Domain; Infrastructure → Domain, Application; Domain → Domain only.
How many violations will deptrac report for this class?
```php
namespace App\Domain;
use App\Application\PlaceOrder;
use App\Infrastructure\Db;
class 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 PlaceOrder (Application), Db (Infrastructure), and Logger (Infrastructure); since Domain may only depend on Domain, each of these three type references in the constructor violates the dependency rule.
Raw```json ⏎ {"answer": 3, "explanation": "The class is in the Domain layer but depends on PlaceOrder (Application), Db (Infrastructure), and Logger (Infrastructure); since Domain may only depend on Domain, each of these three type references in the constructor violates the dependency rule."} ⏎ ``` | верно | The inline FQCN \App\Infrastructure\Logger counts too: Application + Db + Logger = 3. |
T26-L10 2.07 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 has amount 10 and $c is a new Money created by adding 10 + 5, so $c->amount is 15; echoing them with a comma between produces '10,15'.
Raw{"answer": "10,15", "explanation": "$a has amount 10 and $c is a new Money created by adding 10 + 5, so $c->amount is 15; echoing them with a comma between produces '10,15'."} | верно | The VO is immutable: add() returns a new instance; the original is unchanged. |
T26-L9 2.0 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» Пояснение: remove() throws an exception before unset() executes, so the item 'a' is never removed and count() still returns 1.
Raw{"answer": 1, "explanation": "remove() throws an exception before unset() executes, so the item 'a' is never removed and count() still returns 1."} | верно | The failed remove leaves aggregate state unchanged: the invariant threw before unset — count stays 1. |
VC-L9 0.89 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', which is then echoed.
Raw{"answer": "hi", "explanation": "The code instantiates class C and calls its hi() method which returns the string 'hi', which is then echoed."} | верно | Since 8.4, new in a method chain works without wrapping parentheses. |
VC-L10 5.94 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 ("yes") because the lazy ghost hasn't been accessed yet, and accessing $o->v triggers initialization (calling the closure to set $v=21), after which the second check returns false ("no").
Raw{"answer": "yesno", "explanation": "The first isUninitializedLazyObject check returns true (\"yes\") because the lazy ghost hasn't been accessed yet, and accessing $o->v triggers initialization (calling the closure to set $v=21), after which the second check returns false (\"no\")."} | верно | newLazyGhost (8.4): the object stays lazy until first access — reading a property initializes it and clears the flag. |
T28-L9 5.5 c | Symfony: versions | The project was upgraded from Symfony 6.4 to 8.1. What does this code output on 8.1?
```php
echo class_exists(\Symfony\Component\Security\Guard\AbstractGuardAuthenticator::class)
? 'yes' : 'no';
``` | «no» Пояснение: The Guard component (including AbstractGuardAuthenticator) was removed in Symfony 5.0, so the class does not exist in Symfony 8.1.
Raw{"answer": "no", "explanation": "The Guard component (including AbstractGuardAuthenticator) was removed in Symfony 5.0, so the class does not exist in Symfony 8.1."} | верно | Guard authentication was removed in Symfony 7.0 — the class is gone in 8.1. |
T28-L10 3.52 c | Symfony: versions | The project was upgraded from Symfony 6.4 to 8.1. What does this code output on 8.1?
```php
echo class_exists(\Symfony\Component\Routing\Loader\AnnotationClassLoader::class)
? 'yes' : 'no';
echo class_exists(\Symfony\Component\Routing\Loader\AttributeClassLoader::class)
? 'yes' : 'no';
``` | «noyes» Пояснение: Symfony 8.1 removed the AnnotationClassLoader (removed in Symfony 7.0), but includes the AttributeClassLoader (introduced in 6.3).
Raw{"answer": "noyes", "explanation": "Symfony 8.1 removed the AnnotationClassLoader (removed in Symfony 7.0), but includes the AttributeClassLoader (introduced in 6.3)."} | верно | Annotation loaders were removed in 7.0; only attribute loaders remain (Annotation→Attribute). |