Пример запроса (первая клетка). System одинаковый во всех запросах прогона, user — свой вопрос для каждой клетки:
| Клетка | Тема | Утверждение | Ответ |
Результат | Обоснование |
T01-L1 4.35 c | Syntax and operators | Double-quoted and single-quoted strings are processed identically; the difference is only in speed. | «no» Пояснение: Double-quoted strings interpolate variables and interpret escape sequences (e.g. \n, \t), while single-quoted strings treat content almost literally; the difference is not merely speed.
Raw{"answer":"no","explanation":"Double-quoted strings interpolate variables and interpret escape sequences (e.g. \\n, \\t), while single-quoted strings treat content almost literally; the difference is not merely speed."} | верно | В двойных кавычках работают интерполяция переменных и escape-последовательности, в одинарных — нет. |
T01-L2 0.96 c | Syntax and operators | The ?? operator follows isset semantics and raises no warnings for undefined variables. | «yes» Пояснение: The null coalescing operator (??) is shorthand for isset() ?: and does not raise warnings or notices for undefined variables.
Raw{"answer": "yes", "explanation": "The null coalescing operator (??) is shorthand for isset() ?: and does not raise warnings or notices for undefined variables."} | верно | ?? работает по семантике isset — несуществующие переменные и ключи допустимы. |
T01-L3 0.7 c | Syntax and operators | What will this print: echo 'a', 'b'; | «ab» Пояснение: The echo statement in PHP accepts multiple comma-separated arguments and prints them consecutively without any separator.
Raw{"answer": "ab", "explanation": "The echo statement in PHP accepts multiple comma-separated arguments and prints them consecutively without any separator."} | верно | echo принимает список аргументов: ab. |
T01-L4 2.32 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 evaluates to the string '1', so it can be used inside expressions (unlike echo).
Raw{"answer": "yes", "explanation": "In PHP, print is a language construct that evaluates to the string '1', so it can be used inside expressions (unlike echo)."} | верно | print — выражение со значением 1, в отличие от echo, который значения не возвращает. |
T01-L5 0.98 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 1.17 c | Syntax and operators | In PHP 8, the concatenation operator (.) has lower precedence than addition and subtraction. | «yes» Пояснение: In PHP, the concatenation operator (.) has lower precedence than arithmetic operators like + and -, so 'a + b . c' is parsed as '(a + b) . c'.
Raw{"answer": "yes", "explanation": "In PHP, the concatenation operator (.) has lower precedence than arithmetic operators like + and -, so 'a + b . c' is parsed as '(a + b) . c'."} | верно | С PHP 8 (RFC concat precedence) '.' имеет приоритет ниже арифметики: 'сумма: ' . 2 + 3 → 'сумма: 5' (в PHP 7 было иначе). |
T01-L7 0.94 c | Syntax and operators | The expression 2 ** 3 ** 2 in PHP evaluates as (2 ** 3) ** 2, that is, 64. | «no» Пояснение: The ** operator is right-associative in PHP, so 2 ** 3 ** 2 evaluates as 2 ** (3 ** 2) = 2 ** 9 = 512, not 64.
Raw{"answer": "no", "explanation": "The ** operator is right-associative in PHP, so 2 ** 3 ** 2 evaluates as 2 ** (3 ** 2) = 2 ** 9 = 512, not 64."} | верно | ** право-ассоциативен: 2 ** (3 ** 2) = 2 ** 9 = 512. |
T01-L8 1.38 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 it is parsed as 'sum: ' . (2 + 3) = 'sum: 5'.
Raw{"answer": "sum: 5", "explanation": "The + operator has higher precedence than the . concatenation operator, so it is parsed as 'sum: ' . (2 + 3) = 'sum: 5'."} | верно | Парная к verify-клетке про приоритет: 'сумма: 5'. |
T02-L1 0.88 c | Types and comparisons | With strict comparison (===), arrays are considered equal regardless of element order. | «no» Пояснение: With strict comparison (===), arrays must have the same key/value pairs in the same order and be of the same type to be considered equal.
Raw{"answer": "no", "explanation": "With strict comparison (===), arrays must have the same key/value pairs in the same order and be of the same type to be considered equal."} | верно | === для массивов требует совпадения и значений, и их порядка. |
T02-L2 1.02 c | Types and comparisons | The comparison 0 == false returns false because it is a strict comparison. | «no» Пояснение: 0 == false returns true (not false), and == is a loose comparison, not a strict one (=== is strict).
Raw{"answer": "no", "explanation": "0 == false returns true (not false), and == is a loose comparison, not a strict one (=== is strict)."} | верно | Наоборот: == — нестрогое сравнение и возвращает true; строгое — это === (0 === false → false). |
T02-L3 1.43 c | Types and comparisons | In PHP 8, the expression "abc" == 0 returns true. | «no» Пояснение: In PHP 8, when comparing a non-numeric string to an integer, the integer is cast to a string instead, so 'abc' == 0 becomes 'abc' == '0', which is false.
Raw{"answer": "no", "explanation": "In PHP 8, when comparing a non-numeric string to an integer, the integer is cast to a string instead, so 'abc' == 0 becomes 'abc' == '0', which is false."} | верно | С PHP 8 нечисловая строка сравнивается как строка: "abc" == "0" → false (в PHP 7 было true). |
T02-L4 2.42 c | Types and comparisons | Under loose comparison, null equals 0, the empty string, and false at the same time. | «yes» Пояснение: In PHP (prior to 8.0), null == 0, null == '', and null == false all evaluate to true under loose comparison.
Raw{"answer": "yes", "explanation": "In PHP (prior to 8.0), null == 0, null == '', and null == false all evaluate to true under loose comparison."} | верно | null == 0, null == "" и null == false — все true. |
T02-L5 0.92 c | Types and comparisons | What does the expression (int) '42abc' return? | «42» Пояснение: Casting a string to int in PHP parses the leading numeric portion, so '42abc' becomes 42.
Raw{"answer": 42, "explanation": "Casting a string to int in PHP parses the leading numeric portion, so '42abc' becomes 42."} | верно | Ведущая числовая часть: 42, без ошибок и warning. |
T02-L6 0.73 c | Types and comparisons | What does the expression '5' + 5 return? | «10» Пояснение: PHP coerces the numeric string '5' to an integer and performs arithmetic addition, resulting in the integer 10.
Raw{"answer": 10, "explanation": "PHP coerces the numeric string '5' to an integer and performs arithmetic addition, resulting in the integer 10."} | верно | Числовая строка приводится: int 10. |
T02-L7 0.83 c | Types and comparisons | When cast to string, false becomes "0". | «no» Пояснение: Casting false to a string in PHP results in an empty string "", not "0".
Raw{"answer": "no", "explanation": "Casting false to a string in PHP results in an empty string \"\", not \"0\"."} | верно | false → "", true → "1". |
T02-L8 1.36 c | Types and comparisons | The comparison 0.1 + 0.2 === 0.3 returns false. | «yes» Пояснение: Due to floating-point precision, 0.1 + 0.2 equals 0.30000000000000004, which is not strictly equal (===) to 0.3.
Raw{"answer": "yes", "explanation": "Due to floating-point precision, 0.1 + 0.2 equals 0.30000000000000004, which is not strictly equal (===) to 0.3."} | верно | Двоичная погрешность float: 0.1 + 0.2 = 0.30000000000000004. |
T03-L1 1.25 c | Strings | strrev() correctly reverses a UTF-8 string. | «no» Пояснение: strrev() reverses a string byte-by-byte, which corrupts multi-byte UTF-8 characters; use mb_strrev() instead.
Raw{"answer":"no","explanation":"strrev() reverses a string byte-by-byte, which corrupts multi-byte UTF-8 characters; use mb_strrev() instead."} | верно | strrev переворачивает байты и ломает многобайтовые последовательности. |
T03-L2 0.76 c | Strings | str_contains('Hello world', 'world') returns true. | «yes» Пояснение: str_contains() returns true because 'world' is found as a substring in 'Hello world'.
Raw{"answer": "yes", "explanation": "str_contains() returns true because 'world' is found as a substring in 'Hello world'."} | верно | str_contains с PHP 8.0 проверяет вхождение подстроки. |
T03-L3 0.74 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).
Raw{"answer": "no", "explanation": "str_pad() can pad on the left (STR_PAD_LEFT), right (STR_PAD_RIGHT), or both sides (STR_PAD_BOTH)."} | верно | STR_PAD_LEFT / STR_PAD_BOTH меняют сторону дополнения. |
T03-L4 1.15 c | Strings | By default trim() strips only spaces, leaving tabs and newlines intact. | «no» Пояснение: By default, trim() strips spaces, tabs, newlines, returns, nulls, and vertical tabs — not just spaces.
Raw{"answer": "no", "explanation": "By default, trim() strips spaces, tabs, newlines, returns, nulls, and vertical tabs — not just spaces."} | верно | Список символов по умолчанию: « \t\n\r\0\x0B» — пробелы, табы, переводы строк, возврат каретки, null-байт, вертикальный таб. Проверено php -r. |
T03-L5 1.18 c | Strings | How many BYTES does strlen('héllo') return for a UTF-8 string? | «6» Пояснение: In UTF-8, 'h'=1 byte, 'é'=2 bytes (U+00E9 → 0xC3A9), 'l'=1, 'l'=1, 'o'=1, totaling 6 bytes.
Raw{"answer": 6, "explanation": "In UTF-8, 'h'=1 byte, 'é'=2 bytes (U+00E9 → 0xC3A9), 'l'=1, 'l'=1, 'o'=1, totaling 6 bytes."} | верно | 6 букв по 2 байта: 12. |
T03-L6 1.15 c | Strings | What does substr('abcdef', -3) return? | «def» Пояснение: substr with a negative start position of -3 begins 3 characters from the end of 'abcdef', returning 'def'.
Raw{"answer": "def", "explanation": "substr with a negative start position of -3 begins 3 characters from the end of 'abcdef', returning 'def'."} | верно | Отрицательное смещение — с конца: def. |
T03-L7 0.81 c | Strings | ucfirst() modifies the string passed to it in place. | «no» Пояснение: ucfirst() returns a new string with the first character uppercased; it does not modify the original string in place.
Raw{"answer": "no", "explanation": "ucfirst() returns a new string with the first character uppercased; it does not modify the original string in place."} | верно | Строки неизменяемы; ucfirst возвращает новую строку. |
T03-L8 1.08 c | Strings | Variable interpolation works in heredoc but not in nowdoc. | «yes» Пояснение: Heredoc (<<EOF) interpolates variables like double-quoted strings, while nowdoc (<<<'EOF') treats content as a single-quoted string with no interpolation.
Raw{"answer": "yes", "explanation": "Heredoc (<<EOF) interpolates variables like double-quoted strings, while nowdoc (<<<'EOF') treats content as a single-quoted string with no interpolation."} | верно | Nowdoc — «одинарные кавычки» в тройном синтаксисе: текст как есть. |
T04-L1 0.98 c | Arrays | The sort() function preserves the key-to-value association of the array. | «no» Пояснение: sort() re-indexes the array with numeric keys; asort() is the function that preserves key-to-value association.
Raw{"answer": "no", "explanation": "sort() re-indexes the array with numeric keys; asort() is the function that preserves key-to-value association."} | верно | sort перенумеровывает ключи; связь сохраняет asort. |
T04-L2 0.78 c | Arrays | The string key '5' in an array is stored as the integer 5. | «yes» Пояснение: In PHP, string keys that represent valid integers are automatically cast to integer keys, so '5' is stored as the integer 5.
Raw{"answer": "yes", "explanation": "In PHP, string keys that represent valid integers are automatically cast to integer keys, so '5' is stored as the integer 5."} | верно | Каноничные десятичные строковые ключи приводятся к int. |
T04-L3 0.8 c | Arrays | The in_array() function uses strict comparison (===) by default. | «no» Пояснение: in_array() uses loose comparison (==) by default; the third parameter $strict must be explicitly set to true to use ===.
Raw{"answer": "no", "explanation": "in_array() uses loose comparison (==) by default; the third parameter $strict must be explicitly set to true to use ===."} | верно | По умолчанию сравнение нестрогое; строгое — третий аргумент true. |
T04-L4 1.07 c | Arrays | Without a callback, array_filter() removes all "empty" (falsy) elements from the array. | «yes» Пояснение: Without a callback, array_filter() removes elements that evaluate to falsy (false, 0, '', '0', null, []) by default.
Raw{"answer": "yes", "explanation": "Without a callback, array_filter() removes elements that evaluate to falsy (false, 0, '', '0', null, []) by default."} | верно | Убирает 0, "", null, false и пустые массивы. |
T04-L5 0.94 c | Arrays | By default, array_slice() preserves the original numeric keys of the array. | «no» Пояснение: By default, the $preserve_keys parameter is false, so array_slice() reindexes the resulting array starting from 0.
Raw{"answer": "no", "explanation": "By default, the $preserve_keys parameter is false, so array_slice() reindexes the resulting array starting from 0."} | верно | По умолчанию ключи перенумеровываются; сохранение — preserve_keys = true. |
T04-L6 1.12 c | Arrays | What does array_slice([10, 20, 30, 40], 1, 2) return? | «[20, 30]» Пояснение: array_slice starts at index 1 and takes 2 elements, yielding [20, 30].
Raw{"answer": "[20, 30]", "explanation": "array_slice starts at index 1 and takes 2 elements, yielding [20, 30]."} | верно | [20,30]; ключи перенумеровываются. |
T04-L7 1.36 c | Arrays | How many elements will count(['a' => 1] + ['a' => 9, 'b' => 2]) return? | «2» Пояснение: Array union keeps left-side values for duplicate keys and only adds new keys from the right side, resulting in ['a'=>1, 'b'=>2'].
Raw{"answer": 2, "explanation": "Array union keeps left-side values for duplicate keys and only adds new keys from the right side, resulting in ['a'=>1, 'b'=>2']."} | верно | Оператор + : по ключу 'a' побеждает левый; итого 2. |
T04-L8 1.3 c | Arrays | Since PHP 8.1, the spread operator [...$a, ...$b] supports arrays with string keys. | «yes» Пояснение: PHP 8.1 extended the array spread operator to allow arrays with string keys, previously it only worked with integer keys.
Raw{"answer": "yes", "explanation": "PHP 8.1 extended the array spread operator to allow arrays with string keys, previously it only worked with integer keys."} | верно | В 8.0 — только числовые ключи; 8.1 снял ограничение. |
T05-L1 2.54 c | Functions and closures | Named arguments cannot be combined with argument unpacking ...$args in a single call. | «no» Пояснение: Named arguments can be combined with argument unpacking in a single call, as long as the named arguments come before the ...$args unpacking (e.g., func(a: 1, ...$args) is valid).
Raw{"answer": "no", "explanation": "Named arguments can be combined with argument unpacking in a single call, as long as the named arguments come before the ...$args unpacking (e.g., func(a: 1, ...$args) is valid)."} | верно | Можно: f(...$args, имя: значение). Нельзя только позиционный аргумент после распаковки. |
T05-L2 0.78 c | Functions and closures | An anonymous function without use sees variables from the outer scope. | «no» Пояснение: In PHP, closures do not automatically inherit outer scope variables; you must explicitly use the 'use' keyword to import them.
Raw{"answer": "no", "explanation": "In PHP, closures do not automatically inherit outer scope variables; you must explicitly use the 'use' keyword to import them."} | верно | Без use внешние переменные недоступны; авто-захват только у fn. |
T05-L3 0.83 c | Functions and closures | What will func_num_args() return inside function f($a) { return func_num_args(); } when called as f(1, 2, 3)? | «3» Пояснение: func_num_args() returns the number of arguments passed to the function call, which is 3 (1, 2, 3), regardless of how many parameters are declared.
Raw{"answer": 3, "explanation": "func_num_args() returns the number of arguments passed to the function call, which is 3 (1, 2, 3), regardless of how many parameters are declared."} | верно | Считает переданные аргументы: 3. |
T05-L4 1.12 c | Functions and closures | The body of an arrow function fn may consist of several expressions in curly braces. | «no» Пояснение: Arrow functions (fn) in PHP are limited to a single expression body; they cannot use curly braces with multiple statements.
Raw{"answer": "no", "explanation": "Arrow functions (fn) in PHP are limited to a single expression body; they cannot use curly braces with multiple statements."} | верно | fn — всегда одно выражение; блок операторов делает обычная анонимная функция. |
T05-L5 4.02 c | Functions and closures | An arrow function fn captures outer variables by reference (lazily, at use time). | «no» Пояснение: PHP arrow functions (fn) capture outer variables by value at the time of creation, not by reference at use time.
Raw```json ⏎ {"answer": "no", "explanation": "PHP arrow functions (fn) capture outer variables by value at the time of creation, not by reference at use time."} ⏎ ``` | верно | fn захватывает только по значению, автоматически; по ссылке — только &$var в use у обычной функции (fn так не умеет). |
T05-L6 0.91 c | Functions and closures | A closure declared as static function () {} does not capture $this. | «yes» Пояснение: In PHP, a static closure does not bind to the object scope, so $this is not available inside it.
Raw{"answer": "yes", "explanation": "In PHP, a static closure does not bind to the object scope, so $this is not available inside it."} | верно | static-замыкание отвязано от объекта: $this внутри недоступен. |
T05-L7 1.18 c | Functions and closures | What will this print: $x = 5; $f = function () use ($x) { return $x; }; $x = 7; echo $f(); | «5» Пояснение: The closure captures $x by value at creation time (5), so the later reassignment to 7 does not affect it.
Raw{"answer": 5, "explanation": "The closure captures $x by value at creation time (5), so the later reassignment to 7 does not affect it."} | верно | use захватывает по значению в момент создания: 5. |
T05-L8 1.05 c | Functions and closures | In weak typing mode (without strict_types), passing the string "5" to an int parameter is allowed. | «yes» Пояснение: In coercive (weak) typing mode, PHP automatically converts compatible values like the string '5' to the expected int type.
Raw{"answer": "yes", "explanation": "In coercive (weak) typing mode, PHP automatically converts compatible values like the string '5' to the expected int type."} | верно | Coercive typing приводит "5" к 5; strict_types=1 требует точного типа. |
T06-L1 0.74 c | OOP: classes and inheritance | PHP supports constructor property promotion: public function __construct(private int $x) {}. | «yes» Пояснение: Constructor property promotion was introduced in PHP 8.0, allowing properties to be declared and assigned directly in the constructor parameters.
Raw{"answer": "yes", "explanation": "Constructor property promotion was introduced in PHP 8.0, allowing properties to be declared and assigned directly in the constructor parameters."} | верно | С PHP 8.0 параметр с модификатором создаёт свойство и присваивание. |
T06-L2 0.58 c | OOP: classes and inheritance | Which keyword prevents a method from being overridden in subclasses? | «final» Пояснение: The 'final' keyword in PHP prevents a method from being overridden by subclasses.
Raw{"answer": "final", "explanation": "The 'final' keyword in PHP prevents a method from being overridden by subclasses."} | верно | final. |
T06-L3 0.79 c | OOP: classes and inheritance | A method declared final cannot be overridden in a subclass. | «yes» Пояснение: In PHP, a final method cannot be overridden in a subclass; attempting to do so results in a fatal error.
Raw{"answer": "yes", "explanation": "In PHP, a final method cannot be overridden in a subclass; attempting to do so results in a fatal error."} | верно | final запрещает переопределение метода и наследование класса. |
T06-L4 0.69 c | OOP: classes and inheritance | Parent properties with private visibility are accessible in a subclass. | «no» Пояснение: Private properties are only accessible within the class that defines them, not in subclasses.
Raw{"answer": "no", "explanation": "Private properties are only accessible within the class that defines them, not in subclasses."} | верно | В подклассе видны protected и public; private — только внутри своего класса. |
T06-L5 2.67 c | OOP: classes and inheritance | What does get_class(new class {}) return? Answer with the part of the name before the NUL byte (without the file path). | «class@anonymous» Пояснение: Anonymous classes in PHP have a generated name where the part before the NUL byte is 'Class@anonymous'.
Raw```json ⏎ {"answer": "Class@anonymous", "explanation": "Anonymous classes in PHP have a generated name where the part before the NUL byte is 'Class@anonymous'."} ⏎ ``` | верно | get_class анонимного класса печатает class@anonymous\0<файл>:<строка>$n; короткая форма — часть до NUL-байта. Проверено php -r (hex). |
T06-L6 1.96 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» Пояснение: A private method in the parent class is not visible to the child, so the child is free to declare a method with the same name using any visibility (public, protected, or private).
Raw{"answer": "yes", "explanation": "A private method in the parent class is not visible to the child, so the child is free to declare a method with the same name using any visibility (public, protected, or private)."} | верно | private-члены не наследуются — правила совместимости подписей не действуют. |
T06-L7 1.16 c | OOP: classes and inheritance | The magic method __get() is called only for non-existent properties. | «no» Пояснение: __get() is called for both inaccessible (private/protected) and undefined properties when accessed from outside the class.
Raw{"answer": "no", "explanation": "__get() is called for both inaccessible (private/protected) and undefined properties when accessed from outside the class."} | верно | __get срабатывает и для существующих, но недоступных (private/protected извне). |
T06-L8 1.03 c | OOP: classes and inheritance | What does reassigning a readonly property throw — Exception or Error? | «error» Пояснение: Reassigning a readonly property in PHP 8.1+ throws an Error (not an Exception).
Raw{"answer": "Error", "explanation": "Reassigning a readonly property in PHP 8.1+ throws an Error (not an Exception)."} | верно | Error (readonly с 8.1); оговорка: в __clone() переинициализация допустима (8.3+). |
T07-L1 0.83 c | Interfaces, traits, enum | An interface can declare constants. | «yes» Пояснение: In PHP, interfaces can declare constants, which are always public and cannot be overridden by implementing classes.
Raw{"answer": "yes", "explanation": "In PHP, interfaces can declare constants, which are always public and cannot be overridden by implementing classes."} | верно | Константы интерфейса наследуются реализациями. |
T07-L2 0.42 c | Interfaces, traits, enum | Which operator checks whether an object is an instance of a class or interface? | «instanceof» Пояснение: The instanceof operator in PHP checks whether an object is an instance of a specific class or interface.
Raw{"answer": "instanceof", "explanation": "The instanceof operator in PHP checks whether an object is an instance of a specific class or interface."} | верно | instanceof. |
T07-L3 1.41 c | Interfaces, traits, enum | An interface can declare static methods. | «yes» Пояснение: PHP interfaces can declare static methods, and the implementing class must provide the static method implementation.
Raw{"answer": "yes", "explanation": "PHP interfaces can declare static methods, and the implementing class must provide the static method implementation."} | верно | Реализация обязана дать статический метод с той же сигнатурой. |
T07-L4 1.06 c | Interfaces, traits, enum | The instanceof operator only checks class inheritance: it ignores interfaces. | «no» Пояснение: PHP's instanceof operator checks both class inheritance and interface implementation, so an object is instanceof an interface if its class implements that interface.
Raw{"answer": "no", "explanation": "PHP's instanceof operator checks both class inheritance and interface implementation, so an object is instanceof an interface if its class implements that interface."} | верно | instanceof возвращает true и для интерфейсов объекта. |
T07-L5 1.22 c | Interfaces, traits, enum | An interface method may have a default implementation, like a trait method. | «no» Пояснение: PHP interface methods must be abstract and cannot have a body; only traits (and regular classes) can provide default method implementations.
Raw{"answer": "no", "explanation": "PHP interface methods must be abstract and cannot have a body; only traits (and regular classes) can provide default method implementations."} | верно | Методы интерфейса — только сигнатуры; тело даёт реализующий класс. |
T07-L6 1.29 c | Interfaces, traits, enum | An abstract method in an abstract class may have protected visibility. | «yes» Пояснение: In PHP, abstract methods can be declared as public or protected, so protected visibility is allowed.
Raw{"answer": "yes", "explanation": "In PHP, abstract methods can be declared as public or protected, so protected visibility is allowed."} | верно | В абстрактном классе — любая видимость; в интерфейсе — только public. |
T07-L7 0.81 c | Interfaces, traits, enum | How many elements will Foo::cases() return for enum Foo { case A; case B; case C; }? | «3» Пояснение: Foo::cases() returns an array of all enum cases, and there are three: A, B, and C.
Raw{"answer": 3, "explanation": "Foo::cases() returns an array of all enum cases, and there are three: A, B, and C."} | верно | Статический метод cases(): 3. |
T07-L8 0.69 c | Interfaces, traits, enum | A trait can declare constants. | «yes» Пояснение: Traits in PHP can declare constants, which are then accessible in any class that uses the trait.
Raw{"answer": "yes", "explanation": "Traits in PHP can declare constants, which are then accessible in any class that uses the trait."} | верно | С PHP 8.2 трейты могут объявлять константы (RFC constants_in_traits); до 8.2 — нет. |
T08-L1 1.16 c | Exceptions and errors | The Throwable interface is a common ancestor of both Exception and Error. | «yes» Пояснение: In PHP 7+, both Exception and Error implement the Throwable interface, making it their common ancestor.
Raw{"answer": "yes", "explanation": "In PHP 7+, both Exception and Error implement the Throwable interface, making it their common ancestor."} | верно | Иерархия с PHP 7: Throwable → Exception и Throwable → Error. |
T08-L2 0.98 c | Exceptions and errors | A catch (Exception $e) block will also catch TypeError, because TypeError ultimately inherits from Exception. | «no» Пояснение: TypeError extends Error, not Exception; they are sibling classes both implementing Throwable, so catch(Exception) will not catch TypeError.
Raw{"answer": "no", "explanation": "TypeError extends Error, not Exception; they are sibling classes both implementing Throwable, so catch(Exception) will not catch TypeError."} | верно | TypeError наследуется от Error; catch (Exception) его не ловит. |
T08-L3 0.93 c | Exceptions and errors | The @ operator suppresses exceptions too. | «no» Пояснение: The @ operator suppresses errors (warnings, notices) but does not suppress exceptions; exceptions will still be thrown and must be handled with try/catch.
Raw{"answer": "no", "explanation": "The @ operator suppresses errors (warnings, notices) but does not suppress exceptions; exceptions will still be thrown and must be handled with try/catch."} | верно | @ глушит диагностику (warnings/notices), исключения не перехватывает. |
T08-L4 0.78 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 0.9 c | Exceptions and errors | The finally block runs only if the exception was caught by a catch block. | «no» Пояснение: The finally block runs regardless of whether an exception was thrown or caught; it always executes.
Raw{"answer": "no", "explanation": "The finally block runs regardless of whether an exception was thrown or caught; it always executes."} | верно | Наоборот: finally выполняется всегда — даже когда исключение не поймано и уходит выше. Проверено php -r. |
T08-L6 1.34 c | Exceptions and errors | An exception thrown inside a finally block has no effect on the result of the try block. | «no» Пояснение: An exception thrown in a finally block will actually suppress (replace) any exception that was thrown in the try block, so it does have an effect.
Raw{"answer": "no", "explanation": "An exception thrown in a finally block will actually suppress (replace) any exception that was thrown in the try block, so it does have an effect."} | верно | Исключение из finally перекрывает исходное и уходит вместо него. |
T08-L7 1.01 c | Exceptions and errors | What does the expression (bool) new Exception('x') return? | «yes» Пояснение: In PHP, casting any object to bool always results in true, so (bool) new Exception('x') evaluates to true (yes).
Raw{"answer": "yes", "explanation": "In PHP, casting any object to bool always results in true, so (bool) new Exception('x') evaluates to true (yes)."} | верно | Любой объект при приведении к bool — true. Формы ответа: true или да. |
T08-L8 1.06 c | Exceptions and errors | Functions registered via register_shutdown_function() run when exit is called. | «yes» Пояснение: Shutdown functions registered with register_shutdown_function() are called during the shutdown process, which is triggered when exit() or die() is called.
Raw{"answer": "yes", "explanation": "Shutdown functions registered with register_shutdown_function() are called during the shutdown process, which is triggered when exit() or die() is called."} | верно | exit завершает скрипт, но shutdown-функции отрабатывают. |
T09-L1 1.11 c | Namespaces and autoloading | The use App\Service\Mailer; statement itself loads the class file. | «no» Пояснение: The use statement is a compile-time alias that simply maps a shorter name to a fully qualified class name; it does not trigger autoloading or load the file.
Raw{"answer": "no", "explanation": "The use statement is a compile-time alias that simply maps a shorter name to a fully qualified class name; it does not trigger autoloading or load the file."} | верно | use — псевдоним на этапе компиляции; файл грузит автозагрузчик при первом обращении. |
T09-L2 0.78 c | Namespaces and autoloading | What follows use to import a function (not a class): the word function or const? | «function» Пояснение: In PHP, 'use function' is used to import a function from a namespace, while 'use const' is used to import a constant.
Raw{"answer": "function", "explanation": "In PHP, 'use function' is used to import a function from a namespace, while 'use const' is used to import a constant."} | верно | use function ...; (и use const для констант). |
T09-L3 1.14 c | Namespaces and autoloading | Into which file (path from src/) does the PSR-4 mapping "App\ → src/" place the class App\Controller\Api\UserController? | «controller/api/usercontroller.php» Пояснение: PSR-4 strips the 'App\' prefix, converts remaining namespace separators to directory slashes, and appends .php, giving src/Controller/Api/UserController.php.
Raw{"answer": "Controller/Api/UserController.php", "explanation": "PSR-4 strips the 'App\\' prefix, converts remaining namespace separators to directory slashes, and appends .php, giving src/Controller/Api/UserController.php."} | верно | Остаток имени после префикса, \ → /. |
T09-L4 1.01 c | Namespaces and autoloading | Including vendor/autoload.php registers autoloaders via spl_autoload_register(). | «yes» Пояснение: Composer's vendor/autoload.php ultimately creates a ClassLoader instance and registers it via spl_autoload_register().
Raw{"answer": "yes", "explanation": "Composer's vendor/autoload.php ultimately creates a ClassLoader instance and registers it via spl_autoload_register()."} | верно | Composer ставит автозагрузчик именно на spl_autoload_register. |
T09-L5 0.74 c | Namespaces and autoloading | The magic constant __NAMESPACE__ contains the name of the current namespace. | «yes» Пояснение: __NAMESPACE__ is a PHP magic constant that is compiled at build time and contains the name of the current namespace (or an empty string for the global namespace).
Raw{"answer": "yes", "explanation": "__NAMESPACE__ is a PHP magic constant that is compiled at build time and contains the name of the current namespace (or an empty string for the global namespace)."} | верно | В корневом пространстве — пустая строка. |
T09-L6 1.38 c | Namespaces and autoloading | An unqualified class name (without a leading \) in new is resolved from the global root. | «no» Пояснение: An unqualified class name in `new` is resolved relative to the current namespace, not the global root; a leading backslash is required to force global resolution.
Raw{"answer":"no","explanation":"An unqualified class name in `new` is resolved relative to the current namespace, not the global root; a leading backslash is required to force global resolution."} | верно | Резолвится относительно текущего namespace (с учётом импортов). |
T09-L7 1.25 c | Namespaces and autoloading | With the PSR-4 mapping "App\ → src/", the class App\Model\User lives in the file src/Model/User.php. | «yes» Пояснение: PSR-4 maps the remaining namespace segments (Model\User) to subdirectories and filename, resulting in src/Model/User.php.
Raw{"answer": "yes", "explanation": "PSR-4 maps the remaining namespace segments (Model\\User) to subdirectories and filename, resulting in src/Model/User.php."} | верно | Остаток имени после префикса переносится в путь как есть. |
T09-L8 0.95 c | Namespaces and autoloading | A use statement may be written inside a function body — the import then applies to that function only. | «yes» Пояснение: In PHP, a use statement can be placed inside a function body, in which case the imported alias is scoped to that function only.
Raw{"answer": "yes", "explanation": "In PHP, a use statement can be placed inside a function body, in which case the imported alias is scoped to that function only."} | неверно верный: «no» | use внутри тела функции — parse error; импорты файловые и компиляционные. |
T10-L1 1.05 c | References and scope | Arrays are copied on assignment rather than passed by reference. | «yes» Пояснение: In PHP, arrays are value types and are copied on assignment (using copy-on-write optimization since PHP 5.3), not passed by reference by default.
Raw{"answer": "yes", "explanation": "In PHP, arrays are value types and are copied on assignment (using copy-on-write optimization since PHP 5.3), not passed by reference by default."} | верно | Присваивание массива — копия (в движке — copy-on-write). |
T10-L2 1.22 c | References and scope | What will this print: $a = [1, 2]; $b = $a; $b[] = 3; echo count($a); | «2» Пояснение: PHP arrays are copied by value (copy-on-write), so modifying $b does not affect $a, which still has 2 elements.
Raw{"answer": 2, "explanation": "PHP arrays are copied by value (copy-on-write), so modifying $b does not affect $a, which still has 2 elements."} | верно | Присваивание — копия: в $a по-прежнему 2 элемента. |
T10-L3 0.99 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 in the global scope are not visible inside function scope unless explicitly accessed via the global keyword, $GLOBALS superglobal, or passed as parameters.
Raw{"answer": "yes", "explanation": "In PHP, variables in the global scope are not visible inside function scope unless explicitly accessed via the global keyword, $GLOBALS superglobal, or passed as parameters."} | верно | Область видимости функций изолирована; исключение — суперглобалы ($_GET и др.). |
T10-L4 1.44 c | References and scope | unset($GLOBALS['x']) inside a function removes the global variable only for that function. | «no» Пояснение: $GLOBALS['x'] is a direct reference to the global variable, so unset($GLOBALS['x']) removes the global variable entirely, not just for the current function scope.
Raw```json ⏎ {"answer": "no", "explanation": "$GLOBALS['x'] is a direct reference to the global variable, so unset($GLOBALS['x']) removes the global variable entirely, not just for the current function scope."} ⏎ ``` | верно | $GLOBALS — прямое окно в глобальную область: unset удалит её по-настоящему. |
T10-L5 0.77 c | References and scope | What will this print: function inc(&$x) { $x++; } $n = 5; inc($n); echo $n; | «6» Пояснение: The function takes $x by reference, so incrementing $x inside the function modifies $n directly, resulting in 6.
Raw{"answer": 6, "explanation": "The function takes $x by reference, so incrementing $x inside the function modifies $n directly, resulting in 6."} | верно | Ссылка меняет оригинал: 6. |
T10-L6 4.02 c | References and scope | A foreach over an array (by value) works with the "live" array: changes to the array inside the loop are visible in the same pass. | «no» Пояснение: PHP's foreach (by value) iterates over the array's internal structure as it exists at loop start; newly added elements are not visited in the same pass, and removals can cause elements to be skipped.
Raw{"answer": "no", "explanation": "PHP's foreach (by value) iterates over the array's internal structure as it exists at loop start; newly added elements are not visited in the same pass, and removals can cause elements to be skipped."} | верно | По значению foreach итерирует копию-снимок. |
T10-L7 0.82 c | References and scope | A static property belongs to each instance separately: changes in one object are not visible in others. | «no» Пояснение: A static property belongs to the class itself, not to individual instances, so all objects share the same value and changes are visible across all instances.
Raw{"answer": "no", "explanation": "A static property belongs to the class itself, not to individual instances, so all objects share the same value and changes are visible across all instances."} | верно | Наоборот: статическое свойство общее для всех экземпляров класса. Проверено php -r. |
T10-L8 1.03 c | References and scope | An array can have a boolean key true, and it will be stored as bool. | «no» Пояснение: In PHP, boolean array keys are cast to integers: true becomes 1 and false becomes 0, so they are stored as int, not bool.
Raw{"answer": "no", "explanation": "In PHP, boolean array keys are cast to integers: true becomes 1 and false becomes 0, so they are stored as int, not bool."} | верно | Булев ключ приводится к int: true → 1, false → 0. |
T11-L1 1.31 c | Generators, iterators, SPL | Inside a generator, return with a value can be used, and it becomes available via $gen->getReturn(). | «yes» Пояснение: Since PHP 7.1, a generator can return a value (not yield it), and that value is accessible via the Generator::getReturn() method after the generator is fully consumed.
Raw{"answer": "yes", "explanation": "Since PHP 7.1, a generator can return a value (not yield it), and that value is accessible via the Generator::getReturn() method after the generator is fully consumed."} | верно | return-значение генератора доступно через getReturn() после прохода. |
T11-L2 1.29 c | Generators, iterators, SPL | A fully consumed generator can be rewound with rewind() and traversed again. | «no» Пояснение: PHP generators are one-shot iterators; once fully consumed, they cannot be rewound or traversed again.
Raw{"answer": "no", "explanation": "PHP generators are one-shot iterators; once fully consumed, they cannot be rewound or traversed again."} | верно | Генератор одноразовый: rewind после начала итерации бросает Exception. |
T11-L3 3.2 c | Generators, iterators, SPL | The yield from construct delegates traversal to another generator or iterable. | «yes» Пояснение: The yield from construct (a Python feature) does delegate traversal to another generator or iterable, making the statement true.
Raw{"answer": "yes", "explanation": "The yield from construct (a Python feature) does delegate traversal to another generator or iterable, making the statement true."} | верно | yield from проксирует значения, ключи и return-значение внутреннего генератора. |
T11-L4 0.94 c | Generators, iterators, SPL | What does get_class(g()) return for function g() { yield 1; }? | «generator» Пояснение: A function containing yield returns a Generator object, and get_class() returns its class name 'Generator'.
Raw{"answer": "Generator", "explanation": "A function containing yield returns a Generator object, and get_class() returns its class name 'Generator'."} | верно | Функция с yield возвращает Generator. |
T11-L5 1.34 c | Generators, iterators, SPL | How many elements will count(iterator_to_array((function () { yield from [1, 2, 3]; })())) return? | «3» Пояснение: The generator yields 3 elements (1, 2, 3) via yield from, iterator_to_array converts them to an array of 3 elements, and count returns 3.
Raw{"answer": 3, "explanation": "The generator yields 3 elements (1, 2, 3) via yield from, iterator_to_array converts them to an array of 3 elements, and count returns 3."} | верно | yield from делегирует все 3 элемента. |
T11-L6 0.7 c | Generators, iterators, SPL | The SplStack class implements a FIFO queue. | «no» Пояснение: SplStack implements a LIFO (Last-In, First-Out) stack, not a FIFO queue; SplQueue is the class that implements a FIFO queue.
Raw{"answer": "no", "explanation": "SplStack implements a LIFO (Last-In, First-Out) stack, not a FIFO queue; SplQueue is the class that implements a FIFO queue."} | верно | SplStack — стек LIFO; очередь FIFO — SplQueue. |
T11-L7 0.83 c | Generators, iterators, SPL | ArrayIterator allows wrapping an array and traversing it via the Iterator interface. | «yes» Пояснение: ArrayIterator is a built-in PHP class that wraps an array and implements the Iterator interface, allowing traversal via current(), key(), next(), rewind(), and valid() methods.
Raw{"answer": "yes", "explanation": "ArrayIterator is a built-in PHP class that wraps an array and implements the Iterator interface, allowing traversal via current(), key(), next(), rewind(), and valid() methods."} | верно | Объектная обёртка над массивом. |
T11-L8 1.22 c | Generators, iterators, SPL | An ArrayObject instance cannot be traversed with foreach. | «no» Пояснение: ArrayObject implements the Iterator interface, so it can be traversed with foreach.
Raw{"answer": "no", "explanation": "ArrayObject implements the Iterator interface, so it can be traversed with foreach."} | верно | ArrayObject реализует IteratorAggregate — foreach по нему работает. |
T12-L1 1.06 c | Configuration and security | password_hash() generates a salt automatically — passing one separately is not needed. | «yes» Пояснение: password_hash() automatically generates and embeds a random salt in the returned hash; there is no salt parameter to pass.
Raw{"answer": "yes", "explanation": "password_hash() automatically generates and embeds a random salt in the returned hash; there is no salt parameter to pass."} | верно | Соль встраивается в строку результата; параметр salt устарел. |
T12-L2 1.04 c | Configuration and security | In PHP 8, PASSWORD_DEFAULT is md5 with an automatically added salt. | «no» Пояснение: In PHP 8, PASSWORD_DEFAULT is Argon2id, not MD5.
Raw{"answer": "no", "explanation": "In PHP 8, PASSWORD_DEFAULT is Argon2id, not MD5."} | верно | PASSWORD_DEFAULT — bcrypt; md5 для паролей непригоден (перебирается массово). |
T12-L3 0.93 c | Configuration and security | What does password_verify('secret', password_hash('secret', PASSWORD_DEFAULT)) return? | «yes» Пояснение: password_verify() returns true when the plaintext password matches the given hash, which it does here since the hash was generated from the same string 'secret'.
Raw{"answer": "yes", "explanation": "password_verify() returns true when the plaintext password matches the given hash, which it does here since the hash was generated from the same string 'secret'."} | верно | Соль и хеш в одной строке: true (форма ответа: true или да). |
T12-L4 0.97 c | Configuration and security | strip_tags() protects against SQL injection. | «no» Пояснение: strip_tags() removes HTML/PHP tags and has no role in preventing SQL injection; that requires prepared statements or proper escaping.
Raw{"answer": "no", "explanation": "strip_tags() removes HTML/PHP tags and has no role in preventing SQL injection; that requires prepared statements or proper escaping."} | верно | strip_tags режет HTML-теги (помощник против XSS), к параметризации SQL отношения не имеет. |
T12-L5 0.94 c | Configuration and security | session_regenerate_id() is used to protect against session fixation upon user login. | «yes» Пояснение: session_regenerate_id() creates a new session ID, invalidating the old one, which is the standard defense against session fixation attacks, especially upon privilege changes like login.
Raw{"answer": "yes", "explanation": "session_regenerate_id() creates a new session ID, invalidating the old one, which is the standard defense against session fixation attacks, especially upon privilege changes like login."} | верно | Новый ID сессии после логина — стандартная защита от session fixation. |
T12-L6 0.53 c | Configuration and security | Which built-in function returns the SAPI name (e.g., cli)? | «php_sapi_name()» Пояснение: php_sapi_name() returns the SAPI name, such as 'cli' for command-line interface.
Raw{"answer": "php_sapi_name()", "explanation": "php_sapi_name() returns the SAPI name, such as 'cli' for command-line interface."} | верно | php_sapi_name(). |
T12-L7 1.21 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 destroys the session data on the server; the session cookie in the browser must be explicitly cleared with setcookie() or a header.
Raw{"answer": "yes", "explanation": "session_destroy() only destroys the session data on the server; the session cookie in the browser must be explicitly cleared with setcookie() or a header."} | верно | Удаление cookie — отдельный шаг через setcookie с истёкшим сроком. |
T12-L8 0.89 c | Configuration and security | Without calling session_start(), the $_SESSION array is automatically populated with session data. | «no» Пояснение: session_start() must be called before $_SESSION is available; it is not automatically populated without it.
Raw{"answer": "no", "explanation": "session_start() must be called before $_SESSION is available; it is not automatically populated without it."} | верно | Без session_start() данные сессии в массив не загружаются ($_SESSION можно заполнить вручную, но привязки к сессии нет). |
VC-L1 3.84 c | PHP 8.4–8.5 | In which PHP version was the array_find() function introduced? | «not introduced» Пояснение: array_find() is not a built-in PHP function; no such function exists in PHP's standard library.
Raw{"answer": "not introduced", "explanation": "array_find() is not a built-in PHP function; no such function exists in PHP's standard library."} | неверно верный: «8.4» | PHP 8.4 (RFC array_find). |
VC-L2 2.35 c | PHP 8.4–8.5 | Property hooks (get/set right in the property declaration) landed in PHP 8.4. | «yes» Пояснение: PHP 8.4 introduced property hooks, allowing get/set logic to be defined directly in the property declaration.
Raw{"answer": "yes", "explanation": "PHP 8.4 introduced property hooks, allowing get/set logic to be defined directly in the property declaration."} | верно | Property hooks — PHP 8.4 (ноябрь 2024). |
VC-L3 1.0 c | PHP 8.4–8.5 | Asymmetric visibility (public private(set) string $name) appeared in PHP 8.4. | «yes» Пояснение: Asymmetric visibility (e.g., public private(set) string $name) is a new feature introduced in PHP 8.4.
Raw{"answer": "yes", "explanation": "Asymmetric visibility (e.g., public private(set) string $name) is a new feature introduced in PHP 8.4."} | верно | Asymmetric visibility v2 — PHP 8.4. |
VC-L4 1.58 c | PHP 8.4–8.5 | In which PHP version was the #[\NoDiscard] attribute introduced? Answer with the version number. | «8.4» Пояснение: The #[\NoDiscard] attribute was introduced in PHP 8.4 to indicate that a function's return value should not be silently discarded.
Raw{"answer": "8.4", "explanation": "The #[\\NoDiscard] attribute was introduced in PHP 8.4 to indicate that a function's return value should not be silently discarded."} | неверно верный: «8.5» | #[\NoDiscard] — PHP 8.5 (marking return values as important). |
VC-L5 3.18 c | PHP 8.4–8.5 | In which PHP version did the pipe operator |> first appear? Answer with the version number. | «none» Пояснение: The pipe operator |> has been proposed in PHP RFCs but has not been accepted or released in any PHP version as of PHP 8.4.
Raw{"answer": "none", "explanation": "The pipe operator |> has been proposed in PHP RFCs but has not been accepted or released in any PHP version as of PHP 8.4."} | неверно верный: «8.5» | Pipe operator — PHP 8.5 (2025). |
VC-L6 2.42 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 released PHP version; PHP's clone keyword only supports the simple clone $object form.
Raw{"answer": "no", "explanation": "The 'clone-with' syntax clone($obj, ['x' => 1]) does not exist in any released PHP version; PHP's clone keyword only supports the simple clone $object form."} | неверно верный: «8.5» | Clone with v2 — PHP 8.5. |
VC-L7 4.38 c | PHP 8.4–8.5 | In which PHP version were the array_first() and array_last() functions introduced? | «not introduced» Пояснение: array_first() and array_last() are not built-in PHP functions in any released version as of PHP 8.4; they are commonly found in frameworks like Laravel but are not part of the standard PHP library.
Raw{"answer": "not introduced", "explanation": "array_first() and array_last() are not built-in PHP functions in any released version as of PHP 8.4; they are commonly found in frameworks like Laravel but are not part of the standard PHP library."} | неверно верный: «8.5» | PHP 8.5. |
VC-L8 3.64 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. | «n/a» Пояснение: There is no RFC called 'Partial Function Application v2' in PHP; this appears to be a fabricated RFC name.
Raw{"answer": "N/A", "explanation": "There is no RFC called 'Partial Function Application v2' in PHP; this appears to be a fabricated RFC name."} | неверно верный: «8.6» | PFA v2 принят 05.12.2025 (33-0-0), реализован в PHP 8.6. |
VF-L1 0.95 c | PHP: 8.6+ and the future | For which PHP version was the RFC clamp_v2 (the clamp() function) implemented, as of 2026-11-07? Answer with the version number. | «8.4» Пояснение: The clamp() function was introduced in PHP 8.4 via the accepted RFC clamp_v2.
Raw{"answer": "8.4", "explanation": "The clamp() function was introduced in PHP 8.4 via the accepted RFC clamp_v2."} | неверно верный: «8.6» | По данным владельца (wiki.php.net/rfc): clamp_v2 — 8.6; clamp() в 8.5.11 отсутствует (косвенное подтверждение). Дата-якорь делает клетку монотонной. |
VF-L2 2.35 c | PHP: 8.6+ and the future | RFC Context Managers v2 has already been adopted in PHP (as of 2026-11-07). | «no» Пояснение: The Context Managers v2 RFC has not been adopted into PHP; it was rejected or remains unaccepted as of the stated date.
Raw```json ⏎ {"answer": "no", "explanation": "The Context Managers v2 RFC has not been adopted into PHP; it was rejected or remains unaccepted as of the stated date."} ⏎ ``` | верно | На 06.11.2026 — в обсуждении (создан 2026-10-23); не принят. |
VF-L3 3.48 c | PHP: 8.6+ and the future | RFC Bound-Erased Generic Types (generics) was declined in 2026. | «no» Пояснение: The Bound-Erased Generic Types RFC was declined in 2025, not 2026.
Raw{"answer": "no", "explanation": "The Bound-Erased Generic Types RFC was declined in 2025, not 2026."} | неверно верный: «yes» | Голосование завершилось 2026-06-28: отклонён (wiki.php.net/rfc). |
VF-L4 2.16 c | PHP: 8.6+ and the future | As of 2026-11-07, the RFC enabling multithreading (ZTS) by default has already been accepted in PHP. | «no» Пояснение: As of the current date, no RFC enabling ZTS (Zend Thread Safety) multithreading by default has been accepted in PHP; the default build remains non-thread-safe.
Raw{"answer": "no", "explanation": "As of the current date, no RFC enabling ZTS (Zend Thread Safety) multithreading by default has been accepted in PHP; the default build remains non-thread-safe."} | верно | Такого принятого RFC нет на дату якоря; якорь делает клетку монотонной — при принятии RFC позже клетка не перевернётся. |
VF-L5 1.56 c | PHP: 8.6+ and the future | As of PHP 8.5, generics (parameterized types) are still absent. | «yes» Пояснение: PHP has never implemented true generics (parameterized types), and no such feature exists in PHP 8.5 or any prior version.
Raw{"answer": "yes", "explanation": "PHP has never implemented true generics (parameterized types), and no such feature exists in PHP 8.5 or any prior version."} | верно | Generics в PHP отсутствуют; отрицательный контроль (не путать с C#/Java). |
VF-L6 2.72 c | PHP: 8.6+ and the future | As of 2026-11-07, the latest stable PHP version is 8.5, and PHP 8.6 has not been released yet (GA — 2026-11-19). | «yes» Пояснение: PHP follows a yearly November release cycle, so PHP 8.5 (released Nov 2025) would be the latest stable as of Nov 7, 2026, with PHP 8.6's GA expected around Nov 19, 2026.
Raw{"answer": "yes", "explanation": "PHP follows a yearly November release cycle, so PHP 8.5 (released Nov 2025) would be the latest stable as of Nov 7, 2026, with PHP 8.6's GA expected around Nov 19, 2026."} | верно | 8.5 — релиз осени 2025; 8.6 GA 19.11.2026 (wiki.php.net/todo/php86). Дата снимка — 06.11.2026. |
VF-L7 1.13 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 planned but never released; PHP 7.0 (December 2015) followed directly after the PHP 5.6 series.
Raw{"answer": "yes", "explanation": "PHP 6 was planned but never released; PHP 7.0 (December 2015) followed directly after the PHP 5.6 series."} | верно | Исторический факт: ветка 6 не была релизнута. |
VF-L8 2.25 c | PHP: 8.6+ and the future | The RFC adding the #[\Deprecated] attribute to the core was adopted. | «no» Пояснение: The RFC to add a built-in #[\Deprecated] attribute to PHP core was not adopted; deprecation is still handled via E_DEPRECATED notices and @deprecated docblocks.
Raw```json ⏎ {"answer": "no", "explanation": "The RFC to add a built-in #[\\Deprecated] attribute to PHP core was not adopted; deprecation is still handled via E_DEPRECATED notices and @deprecated docblocks."} ⏎ ``` | неверно верный: «yes» | #[\Deprecated] — принят, реализован в PHP 8.4. |
T25-L1 1.26 c | Clean architecture | The dependency rule of clean and onion architecture: inner layers know nothing about outer ones — dependencies point toward the center. | «yes» Пояснение: In clean and onion architecture, the dependency rule dictates that all dependencies point inward toward the domain core, so inner layers have no knowledge of outer ones.
Raw{"answer": "yes", "explanation": "In clean and onion architecture, the dependency rule dictates that all dependencies point inward toward the domain core, so inner layers have no knowledge of outer ones."} | верно | Чистая (Robert C. Martin), луковичная (Jeffrey Palermo) и гексагональная (ports & adapters) — варианты одной идеи: зависимости направлены внутрь, к домену. Слоями в проекте следит deptrac. |
T25-L2 1.17 c | Clean architecture | Domain entities import neither Doctrine nor Symfony — only the language and, possibly, the standard library. | «yes» Пояснение: In DDD and clean architecture, domain entities are pure PHP objects that should have no dependencies on frameworks like Symfony or ORMs like Doctrine, keeping the domain layer decoupled from infrastructure.
Raw{"answer": "yes", "explanation": "In DDD and clean architecture, domain entities are pure PHP objects that should have no dependencies on frameworks like Symfony or ORMs like Doctrine, keeping the domain layer decoupled from infrastructure."} | верно | Изоляция домена от инфраструктуры; deptrac в проекте как раз следит за слоями. |
T25-L3 1.25 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 call use cases but are not themselves business logic.
Raw{"answer": "no", "explanation": "Controllers and Twig templates belong to the presentation (interface) layer, not the business-logic layer; they call use cases but are not themselves business logic."} | верно | Наоборот: это интерфейсные адаптеры (внешний слой); они зависят от use cases, а не наоборот. |
T25-L4 1.23 c | Clean architecture | What sits at the very center of the onion architecture? | «domain» Пояснение: In onion architecture, the domain layer (entities and business rules) sits at the very center, with all other layers depending inward toward it.
Raw{"answer": "Domain", "explanation": "In onion architecture, the domain layer (entities and business rules) sits at the very center, with all other layers depending inward toward it."} | неверно верный: «domain model» | Центральное кольцо — Domain Model: сущности и бизнес-правила без зависимостей; далее Domain Services → Application Services → Infrastructure/UI/Tests (Palermo). |
T25-L5 1.05 c | Clean architecture | Layer boundary violations can be caught automatically: a layer-dependency analyzer (e.g. deptrac) fails on a forbidden call. | «yes» Пояснение: Deptrac is a PHP layer-dependency analyzer that enforces architectural rules and fails the build when a forbidden layer dependency is detected.
Raw{"answer": "yes", "explanation": "Deptrac is a PHP layer-dependency analyzer that enforces architectural rules and fails the build when a forbidden layer dependency is detected."} | верно | depfile.yaml в проекте TasK: CI проверяет правила слоёв на каждом пайплайне. |
T25-L6 1.68 c | Clean architecture | A use case (interactor) may accept an HTTP request or an EntityManager as arguments — it is simpler that way. | «no» Пояснение: Use cases (interactors) should be framework-agnostic and infrastructure-agnostic; accepting an HTTP request or EntityManager couples them to specific technologies, violating Clean Architecture principles.
Raw{"answer": "no", "explanation": "Use cases (interactors) should be framework-agnostic and infrastructure-agnostic; accepting an HTTP request or EntityManager couples them to specific technologies, violating Clean Architecture principles."} | верно | Use case принимает DTO и порты; привязка к HTTP/ORM протекает инфраструктуру во внутренние слои. |
T25-L7 1.06 c | Clean architecture | What is the component called that provides a collection of aggregates/entities while hiding the storage mechanism behind an interface? | «repository» Пояснение: The Repository pattern provides a collection-like interface for accessing domain aggregates/entities while abstracting the underlying storage mechanism.
Raw{"answer": "Repository", "explanation": "The Repository pattern provides a collection-like interface for accessing domain aggregates/entities while abstracting the underlying storage mechanism."} | верно | Repository pattern (DDD/Evans); в проекте — Doctrine-репозитории за портами. |
T25-L8 1.94 c | Clean architecture | In clean architecture, swapping PostgreSQL for another database touches only the outer layer — the domain and use cases stay unchanged. | «yes» Пояснение: In Clean Architecture the database is an outermost-layer detail; the domain and use cases depend only on interfaces (ports), so swapping the DB engine requires changes only in the frameworks/drivers layer.
Raw{"answer": "yes", "explanation": "In Clean Architecture the database is an outermost-layer detail; the domain and use cases depend only on interfaces (ports), so swapping the DB engine requires changes only in the frameworks/drivers layer."} | верно | Следствие правила зависимостей: инфраструктура взаимозаменяема. |
T26-L1 1.34 c | DDD | In DDD, an aggregate is just another name for a database table. | «no» Пояснение: An aggregate is a domain-level consistency boundary (a cluster of entities and value objects), not a technical storage structure like a database table; they exist at different layers of the architecture and do not necessarily map one-to-one.
Raw{"answer": "no", "explanation": "An aggregate is a domain-level consistency boundary (a cluster of entities and value objects), not a technical storage structure like a database table; they exist at different layers of the architecture and do not necessarily map one-to-one."} | верно | Агрегат — кластер объектов с границей согласованности (транзакционной вокруг корня); таблица — деталь хранения. |
T26-L2 0.82 c | DDD | A Value Object is immutable and compared by the values of its fields, not by identity. | «yes» Пояснение: Value Objects are immutable and their equality is determined by the values of their fields, not by object identity (reference equality).
Raw{"answer": "yes", "explanation": "Value Objects are immutable and their equality is determined by the values of their fields, not by object identity (reference equality)."} | верно | Классика Evans: Money, Email; равенство структурное. |
T26-L3 0.76 c | DDD | What is the single external entry point of an aggregate, through which all changes must go, called? | «aggregate root» Пояснение: In Domain-Driven Design, the Aggregate Root is the single entry point of an aggregate through which all external modifications must pass.
Raw{"answer": "Aggregate Root", "explanation": "In Domain-Driven Design, the Aggregate Root is the single entry point of an aggregate through which all external modifications must pass."} | верно | Aggregate Root: внешние объекты ссылаются только на корень; он защищает инварианты агрегата. |
T26-L4 1.24 c | DDD | In DDD, a repository is declared for an aggregate (its root), not for every entity. | «yes» Пояснение: In DDD, a repository is defined for an aggregate root, and all entities within that aggregate are accessed through the root, not via their own repositories.
Raw{"answer": "yes", "explanation": "In DDD, a repository is defined for an aggregate root, and all entities within that aggregate are accessed through the root, not via their own repositories."} | верно | Репозиторий корня хранит границу согласованности агрегата; вложенные сущности доступны только через корень. |
T26-L5 0.85 c | DDD | Ubiquitous language is the model's shared language common to developers and domain experts. | «yes» Пояснение: In Domain-Driven Design, Ubiquitous Language is the shared vocabulary used consistently by both developers and domain experts to describe the domain model.
Raw{"answer": "yes", "explanation": "In Domain-Driven Design, Ubiquitous Language is the shared vocabulary used consistently by both developers and domain experts to describe the domain model."} | верно | Evans: язык из требований переходит в имена классов и методов. |
T26-L6 1.18 c | DDD | What is the boundary called within which a model and its language are consistent, while outside the same words mean other models? | «bounded context» Пояснение: In Domain-Driven Design, a bounded context is the boundary within which a model and its ubiquitous language are consistent, while the same terms may mean different things outside it.
Raw{"answer": "bounded context", "explanation": "In Domain-Driven Design, a bounded context is the boundary within which a model and its ubiquitous language are consistent, while the same terms may mean different things outside it."} | верно | Bounded Context; «Заказ» в биллинге и в доставке — разные модели. |
T26-L7 1.09 c | DDD | An anemic model (objects with only getters/setters, logic in services) is the recommended DDD style. | «no» Пояснение: DDD recommends rich domain models where business logic is encapsulated within the domain objects themselves; anemic models with logic in services are considered an anti-pattern in DDD.
Raw{"answer": "no", "explanation": "DDD recommends rich domain models where business logic is encapsulated within the domain objects themselves; anemic models with logic in services are considered an anti-pattern in DDD."} | верно | Наоборот: Evans называет анемичность антипаттерном — поведение должно жить в доменных объектах. |
T26-L8 1.4 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 a boundary within which a domain model applies, and the same real-world concept can be modeled as different classes with different attributes and behaviors in different contexts.
Raw{"answer": "yes", "explanation": "In Domain-Driven Design, a bounded context is a boundary within which a domain model applies, and the same real-world concept can be modeled as different classes with different attributes and behaviors in different contexts."} | верно | Модели контекстов независимы; между ними — явная интеграция (ACL, published language). |
T13-L1 0.97 c | Symfony | Services in the Symfony DI container are created lazily by default — on first use. | «yes» Пояснение: Symfony's DI container instantiates services only when they are first requested (e.g., via get() or injection), not eagerly at container build time.
Raw{"answer": "yes", "explanation": "Symfony's DI container instantiates services only when they are first requested (e.g., via get() or injection), not eagerly at container build time."} | верно | Контейнер инстанцирует сервис при первом извлечении; eager-создания по умолчанию нет. |
T13-L2 0.85 c | Symfony | Which Symfony console command lists all registered routes? | «debug:router» Пояснение: The Symfony console command 'debug:router' lists all registered routes in the application.
Raw{"answer": "debug:router", "explanation": "The Symfony console command 'debug:router' lists all registered routes in the application."} | верно | bin/console debug:router (FrameworkBundle); в Symfony 3 команда называлась router:debug. |
T13-L3 1.28 c | Symfony | Symfony autowiring requires manually declaring every service in services.yaml. | «no» Пояснение: The whole purpose of autowiring is to automatically resolve dependencies based on type hints, eliminating the need to manually declare most services in services.yaml.
Raw{"answer": "no", "explanation": "The whole purpose of autowiring is to automatically resolve dependencies based on type hints, eliminating the need to manually declare most services in services.yaml."} | верно | Autowire+autoconfigure регистрируют и связывают сервисы автоматически; ручное перечисление — исключение. |
T13-L4 0.76 c | Symfony | Twig templates are compiled into PHP classes and cached between requests. | «yes» Пояснение: Twig compiles templates into PHP classes (extending Twig\Template) and caches the resulting PHP files to avoid recompilation on subsequent requests.
Raw{"answer": "yes", "explanation": "Twig compiles templates into PHP classes (extending Twig\\Template) and caches the resulting PHP files to avoid recompilation on subsequent requests."} | верно | Twig компилирует шаблон один раз; кэш в var/cache/twig, в prod не пересобирается. |
T13-L5 1.15 c | Symfony | In the Symfony dev environment the DI container is rebuilt only after tracked files change, not on every request. | «yes» Пояснение: In the dev environment, Symfony caches the compiled container and only rebuilds it when tracked files (e.g., service config, kernel) have changed.
Raw{"answer": "yes", "explanation": "In the dev environment, Symfony caches the compiled container and only rebuilds it when tracked files (e.g., service config, kernel) have changed."} | верно | Kernel проверяет freshness ресурсов (конфиги, классы); иначе переиспользуется кэш контейнера. |
T13-L6 0.78 c | Symfony | Which environment variable selects the active Symfony environment (dev/prod)? | «app_env» Пояснение: Since Symfony 4.4/5.x, the APP_ENV environment variable determines the active environment (e.g., dev, prod, test).
Raw{"answer": "APP_ENV", "explanation": "Since Symfony 4.4/5.x, the APP_ENV environment variable determines the active environment (e.g., dev, prod, test)."} | верно | APP_ENV в .env; APP_DEBUG — отдельный флаг отладки. |
T13-L7 1.06 c | Symfony | A controller method can be private — Symfony routing works with any method of the class. | «no» Пояснение: Symfony controller action methods must be public; the framework invokes them via reflection and will throw an error if the method is private.
Raw{"answer": "no", "explanation": "Symfony controller action methods must be public; the framework invokes them via reflection and will throw an error if the method is private."} | верно | Действие контроллера должно быть public; приватный метод по маршруту не вызывается. |
T13-L8 1.35 c | Symfony | Event subscribers always receive events before listeners, because the interface gives them priority. | «no» Пояснение: Both listeners and subscribers are ordered by priority value, not by their type; a subscriber with low priority will be called after a listener with high priority.
Raw{"answer": "no", "explanation": "Both listeners and subscribers are ordered by priority value, not by their type; a subscriber with low priority will be called after a listener with high priority."} | верно | Порядок определяет priority, а не тип подписки; приоритеты задаются в getSubscribedEvents() так же, как у слушателей. |
T22-L1 1.2 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 Guard authentication system was removed in Symfony 6.0, and the new system is based on AuthenticatorInterface (introduced in 5.3).
Raw{"answer": "yes", "explanation": "The Guard authentication system was removed in Symfony 6.0, and the new system is based on AuthenticatorInterface (introduced in 5.3)."} | верно | Guard объявлен устаревшим в 5.3 и удалён в 6.0; в проекте symfony/security-bundle 8.1. |
T22-L2 1.15 c | Symfony: Security and forms | Which Symfony attribute checks a role/permission right on a controller method (403 without it)? | «isgranted» Пояснение: The #[IsGranted] attribute in Symfony checks if the current user has the specified role or permission on a controller method, returning a 403 Forbidden if they don't.
Raw{"answer": "IsGranted", "explanation": "The #[IsGranted] attribute in Symfony checks if the current user has the specified role or permission on a controller method, returning a 403 Forbidden if they don't."} | верно | #[IsGranted('ROLE_ADMIN')]; атрибут из symfony/security-http. |
T22-L3 1.25 c | Symfony: Security and forms | Voters are Symfony's mechanism for checking access to a specific object: isGranted('EDIT', $post). | «yes» Пояснение: Voters in Symfony are the mechanism for object-level access control, and isGranted('EDIT', $post) is the typical way to check a specific permission on a specific object using the Voter system.
Raw{"answer": "yes", "explanation": "Voters in Symfony are the mechanism for object-level access control, and isGranted('EDIT', $post) is the typical way to check a specific permission on a specific object using the Voter system."} | верно | VoterInterface->vote(); docs Symfony — Voters. |
T22-L4 2.07 c | Symfony: Security and forms | In modern Symfony (7+) validation constraints are declared as PHP attributes (#[Assert\NotBlank]); doctrine annotations are no longer supported. | «yes» Пояснение: Symfony 7 removed support for the doctrine/annotations-based annotation syntax, so validation constraints must be declared using PHP 8 attributes like #[Assert\NotBlank].
Raw{"answer": "yes", "explanation": "Symfony 7 removed support for the doctrine/annotations-based annotation syntax, so validation constraints must be declared using PHP 8 attributes like #[Assert\\NotBlank]."} | верно | Докблок-аннотации удалены в Symfony 7.0; стандарт — атрибуты. В проекте symfony/validator 8.1. |
T22-L5 0.92 c | Symfony: Security and forms | CSRF protection of Symfony forms is enabled by default: the form validates the token on submission. | «yes» Пояснение: Symfony forms have CSRF protection enabled by default; a token is automatically added and validated on submission unless explicitly disabled.
Raw{"answer": "yes", "explanation": "Symfony forms have CSRF protection enabled by default; a token is automatically added and validated on submission unless explicitly disabled."} | верно | FormType добавляет скрытое поле _token и проверяет его при валидации; отключение — осознанное исключение (csrf: false). |
T22-L6 0.96 c | Symfony: Security and forms | Form validation in Symfony runs server-side even if the client-side (HTML5) checks passed. | «yes» Пояснение: Symfony always performs server-side form validation; client-side HTML5 checks are only a UX convenience and can be bypassed, so server-side validation is mandatory.
Raw{"answer": "yes", "explanation": "Symfony always performs server-side form validation; client-side HTML5 checks are only a UX convenience and can be bypassed, so server-side validation is mandatory."} | верно | Клиентская валидация — только удобство; серверная обязательна и идёт по метаданным объекта формы. |
T22-L7 0.74 c | Symfony: Security and forms | Which Symfony maker command generates a form class (FormType)? | «make:form» Пояснение: The Symfony MakerBundle command 'make:form' generates a FormType class.
Raw{"answer": "make:form", "explanation": "The Symfony MakerBundle command 'make:form' generates a FormType class."} | верно | bin/console make:form (symfony/maker-bundle — в проекте). |
T22-L8 1.26 c | Symfony: Security and forms | Symfony stores the user's password in the session in plain text. | «no» Пояснение: Symfony only stores the user's identity (e.g., user ID) in the session after authentication; the password is never stored in the session, as it is verified against a hash and then discarded.
Raw{"answer": "no", "explanation": "Symfony only stores the user's identity (e.g., user ID) in the session after authentication; the password is never stored in the session, as it is verified against a hash and then discarded."} | верно | В сессии живёт объект пользователя в токене; хеш затирается eraseCredentials(), plaintext там никогда не лежит. |
T23-L1 0.96 c | Symfony: configuration and services | Symfony bundle configuration lives in config/packages — one file per bundle or topic. | «yes» Пояснение: In Symfony, bundle configurations are conventionally stored in config/packages/ with one file per bundle or topic (e.g., framework.yaml, doctrine.yaml, twig.yaml).
Raw{"answer": "yes", "explanation": "In Symfony, bundle configurations are conventionally stored in config/packages/ with one file per bundle or topic (e.g., framework.yaml, doctrine.yaml, twig.yaml)."} | верно | Стандартная структура (config/packages/*.yaml); перегрузка — config/packages/<env>. |
T23-L2 1.12 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 best practice: commit a .env with safe dev defaults for reference, while keeping actual secrets in a gitignored .env.local (or similar) file.
Raw{"answer": "yes", "explanation": "This is a common best practice: commit a .env with safe dev defaults for reference, while keeping actual secrets in a gitignored .env.local (or similar) file."} | верно | symfony/dotenv: .env — общий безопасный набор значений; локальные секреты — .env.local (gitignored) или secrets-хранилище. |
T23-L3 0.8 c | Symfony: configuration and services | Which Symfony command lists the container's registered services and their aliases? | «debug:container» Пояснение: The Symfony command 'debug:container' lists all registered services and their aliases in the service container.
Raw{"answer": "debug:container", "explanation": "The Symfony command 'debug:container' lists all registered services and their aliases in the service container."} | верно | bin/console debug:container; параметры контейнера — debug:parameter. |
T23-L4 1.61 c | Symfony: configuration and services | The Symfony container allows changing parameters at runtime: $container->setParameter() works from a controller. | «no» Пояснение: Once the container is frozen (which happens at kernel boot), calling setParameter() throws a LogicException; you can only get parameters, not set them, from a controller.
Raw{"answer": "no", "explanation": "Once the container is frozen (which happens at kernel boot), calling setParameter() throws a LogicException; you can only get parameters, not set them, from a controller."} | верно | Контейнер компилируется и замораживается; runtime-значения — только через переменные окружения. |
T23-L5 0.95 c | Symfony: configuration and services | By default, Symfony services are public (public: true) — you can fetch them directly from the container. | «no» Пояснение: Since Symfony 4.0, services are private by default (public: false) to allow the container to optimize and remove unused services.
Raw{"answer": "no", "explanation": "Since Symfony 4.0, services are private by default (public: false) to allow the container to optimize and remove unused services."} | верно | С Symfony 4.0 сервисы по умолчанию private: инжектятся через autowiring; $container->get() — только для публичных. |
T23-L6 1.21 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 work without any configuration file in config/packages, as they can rely on autoconfiguration or have sensible defaults built in.
Raw{"answer": "no", "explanation": "Many bundles work without any configuration file in config/packages, as they can rely on autoconfiguration or have sensible defaults built in."} | верно | У бандлов есть встроенные умолчания (Extension); конфиг нужен только для отклонений от них. |
T23-L7 0.72 c | Symfony: configuration and services | Environment variable values are injected into services.yaml using the %env(VAR)% syntax. | «yes» Пояснение: In Symfony, environment variables are referenced in YAML configuration files (like services.yaml) using the %env(VAR)% syntax.
Raw{"answer": "yes", "explanation": "In Symfony, environment variables are referenced in YAML configuration files (like services.yaml) using the %env(VAR)% syntax."} | верно | %env(...)% резолвится в рантайме env-процессорами; docs — Env Var Processors. |
T23-L8 1.06 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 controls debug mode, enabling the profiler, Twig debug toolbar, and detailed error pages.
Raw{"answer": "APP_DEBUG", "explanation": "The APP_DEBUG environment variable in Symfony controls debug mode, enabling the profiler, Twig debug toolbar, and detailed error pages."} | верно | APP_DEBUG=1 (в .env dev-окружения); окружение выбирает APP_ENV — см. T13-L6. |
T16-L1 0.92 c | Symfony: Messenger | A single message in Symfony Messenger can only have one handler. | «no» Пояснение: Symfony Messenger allows multiple handlers for a single message, which will all be executed in sequence.
Raw{"answer": "no", "explanation": "Symfony Messenger allows multiple handlers for a single message, which will all be executed in sequence."} | верно | Messenger вызывает все хендлеры, подписанные на класс сообщения (docs — Multiple Handlers). |
T16-L2 1.05 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 any queueing; it does not wait for a worker.
Raw{"answer": "no", "explanation": "The sync transport processes the message immediately in the same process without any queueing; it does not wait for a worker."} | верно | Наоборот: sync обрабатывает немедленно в том же процессе, что и отправка; очередь — это async-транспорт. |
T16-L3 0.7 c | Symfony: Messenger | Which console command starts the worker that processes Messenger queue messages? | «messenger:consume» Пояснение: The Symfony console command `messenger:consume` starts the worker that processes messages from the Messenger queue transport.
Raw{"answer": "messenger:consume", "explanation": "The Symfony console command `messenger:consume` starts the worker that processes messages from the Messenger queue transport."} | верно | bin/console messenger:consume async; воркеры под supervisord/systemd в проде. |
T16-L4 1.08 c | Symfony: Messenger | Retries for failed messages (retry_strategy) are configured per Messenger transport. | «yes» Пояснение: In Symfony Messenger, the retry_strategy (max_retries, delay, multiplier, max_delay) is configured per transport in the framework configuration.
Raw{"answer": "yes", "explanation": "In Symfony Messenger, the retry_strategy (max_retries, delay, multiplier, max_delay) is configured per transport in the framework configuration."} | верно | retry_strategy на транспорте: max_retries, delay, multiplier; docs — Failed Messages & Retries. |
T16-L5 1.51 c | Symfony: Messenger | By default, Messenger serializes messages to JSON. | «yes» Пояснение: Symfony Messenger's default Serializer uses the Symfony Serializer component with 'json' as the default format.
Raw{"answer": "yes", "explanation": "Symfony Messenger's default Serializer uses the Symfony Serializer component with 'json' as the default format."} | неверно верный: «no» | Дефолтный сериализатор — PhpSerializer (serialize()); JSON-сериализатор включается отдельно. |
T16-L6 1.06 c | Symfony: Messenger | Symfony Scheduler produces messages on a schedule and dispatches them through Messenger. | «yes» Пояснение: Symfony Scheduler is designed to schedule the dispatching of messages through the Messenger component at defined times.
Raw{"answer": "yes", "explanation": "Symfony Scheduler is designed to schedule the dispatching of messages through the Messenger component at defined times."} | верно | Schedule → RecurringMessage → шина Messenger; docs — Scheduler. |
T16-L7 0.88 c | Symfony: Messenger | Which built-in Messenger transport stores messages in database tables via Doctrine? | «doctrine» Пояснение: The 'doctrine' transport in Symfony Messenger stores messages in database tables managed by Doctrine ORM.
Raw{"answer": "doctrine", "explanation": "The 'doctrine' transport in Symfony Messenger stores messages in database tables managed by Doctrine ORM."} | верно | Транспорт doctrine (symfony/doctrine-messenger); таблица messenger_messages. В проекте стоит amqp-messenger + doctrine-messenger. |
T16-L8 1.56 c | Symfony: Messenger | The Messenger pipeline can be extended with custom middleware, placed before or after the built-in ones. | «yes» Пояснение: Laravel's Messenger allows you to extend its pipeline by adding custom middleware via the $middleware property on a command, which can be placed before or after built-in middleware.
Raw{"answer": "yes", "explanation": "Laravel's Messenger allows you to extend its pipeline by adding custom middleware via the $middleware property on a command, which can be placed before or after built-in middleware."} | верно | messenger.bus.*.middleware в yaml; docs — Middleware. |
T28-L1 1.19 c | Symfony: versions | Symfony major releases come every two years, minor ones every six months (in May and November). | «no» Пояснение: Symfony major releases come out every year (not every two years), while minor releases do come every six months in May and November.
Raw{"answer": "no", "explanation": "Symfony major releases come out every year (not every two years), while minor releases do come every six months in May and November."} | неверно верный: «yes» | Стандартный релизный цикл: 8.0 — ноябрь 2025, 8.1 — май 2026, 8.2 — ноябрь 2026. |
T28-L2 2.47 c | Symfony: versions | What is the minimum PHP version required by Symfony 8? | «8.4» Пояснение: Symfony 8 requires a minimum PHP version of 8.4, following Symfony's pattern of requiring the latest stable PHP release.
Raw{"answer": 8.4, "explanation": "Symfony 8 requires a minimum PHP version of 8.4, following Symfony's pattern of requiring the latest stable PHP release."} | верно | Symfony 8.0 поднял требование до PHP >= 8.4.1 (в vendor проекта: "php": ">=8.4.1"). |
T28-L3 1.04 c | Symfony: versions | Symfony 7.0 kept support for docblock annotations (validation, routes). | «no» Пояснение: Symfony 7.0 removed support for docblock annotations; PHP 8 attributes are now the only supported way to configure validation, routes, etc.
Raw{"answer": "no", "explanation": "Symfony 7.0 removed support for docblock annotations; PHP 8 attributes are now the only supported way to configure validation, routes, etc."} | верно | Наоборот: в 7.0 аннотации удалены — только PHP-атрибуты (#[Route], #[Assert\NotBlank]). |
T28-L4 1.0 c | Symfony: versions | AssetMapper manages CSS/JS without node or webpack — via importmap.php. | «yes» Пояснение: Symfony's AssetMapper component manages CSS/JS assets using an import map (importmap.php) without requiring Node.js or webpack.
Raw{"answer": "yes", "explanation": "Symfony's AssetMapper component manages CSS/JS assets using an import map (importmap.php) without requiring Node.js or webpack."} | верно | symfony/asset-mapper (с 6.3, стандарт с 7.x); в проекте — importmap.php в корне и asset-mapper 8.1. |
T28-L5 1.32 c | Symfony: versions | Symfony 6.4 is a regular release without long-term support. | «no» Пояснение: Symfony 6.4 is a Long-Term Support (LTS) release, with bug fixes until November 2025 and security fixes until November 2027.
Raw{"answer": "no", "explanation": "Symfony 6.4 is a Long-Term Support (LTS) release, with bug fixes until November 2025 and security fixes until November 2027."} | верно | Наоборот: 6.4 — LTS (расширенная поддержка); LTS выходит вместе с очередным мажором (6.4 — вместе с 7.0). |
T28-L6 1.29 c | Symfony: versions | When moving to a new Symfony major version, deprecations of the previous branch keep working — major releases do not remove them. | «no» Пояснение: Symfony removes deprecated features in the next major version; that is the entire purpose of the deprecation cycle.
Raw{"answer": "no", "explanation": "Symfony removes deprecated features in the next major version; that is the entire purpose of the deprecation cycle."} | верно | Наоборот: мажорный релиз удаляет всё устаревшее (7.0 убрал деприкейшены 6.x, 8.0 — 7.x). |
T28-L7 0.83 c | Symfony: versions | Every Symfony major release is accompanied by an UPGRADE guide listing the changes. | «yes» Пояснение: Symfony provides an UPGRADE-X.Y.md guide for each major release, documenting all breaking changes and migration steps.
Raw{"answer": "yes", "explanation": "Symfony provides an UPGRADE-X.Y.md guide for each major release, documenting all breaking changes and migration steps."} | верно | UPGRADE-7.0.md, UPGRADE-8.0.md в репозитории symfony/symfony. |
T28-L8 1.68 c | Symfony: versions | Which Symfony component manages assets and the importmap without node/webpack? | «assetmapper» Пояснение: Symfony AssetMapper (symfony/asset-mapper) is the component that manages assets and importmaps without requiring Node.js or Webpack.
Raw{"answer": "AssetMapper", "explanation": "Symfony AssetMapper (symfony/asset-mapper) is the component that manages assets and importmaps without requiring Node.js or Webpack."} | верно | symfony/asset-mapper 8.1 — в проекте. |
T29-L1 4.22 c | Symfony: 8.2 and beyond | As of 2026-11-07, Symfony 8.2 has already been released. | «no» Пояснение: Symfony releases minor versions roughly every 6 months; as of November 2026, at most Symfony 8.0 or 8.1 could be out, making 8.2 not yet released.
Raw{"answer": "no", "explanation": "Symfony releases minor versions roughly every 6 months; as of November 2026, at most Symfony 8.0 or 8.1 could be out, making 8.2 not yet released."} | верно | Наоборот: 8.2 ещё не выпущена — релиз в конце ноября 2026; последняя стабильная — 8.1. |
T29-L2 9.54 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 the six-month cycle from Symfony 7.0 (May 2024), version 8.2 would land around November 2027, not November 2026 (which would correspond to ~8.0).
Raw{"answer": "no", "explanation": "Following the six-month cycle from Symfony 7.0 (May 2024), version 8.2 would land around November 2027, not November 2026 (which would correspond to ~8.0)."} | неверно верный: «yes» | Политика релизов: 8.1 — май 2026, 8.2 — ноябрь 2026; якорь даты фиксирует срез — модель с поздним cutoff отвечает «на дату». |
T29-L3 1.55 c | Symfony: 8.2 and beyond | Which Symfony version comes after 8.1 (as of 2026-11-07)? | «8.2» Пояснение: Following Symfony's semver minor release cadence, the version after 8.1 is 8.2.
Raw{"answer": "8.2", "explanation": "Following Symfony's semver minor release cadence, the version after 8.1 is 8.2."} | верно | 8.2 — следующий минорный релиз (ноябрь 2026); после его выхода проект переходит с 8.1.* на 8.2.*. |
T29-L4 2.06 c | Symfony: 8.2 and beyond | Symfony 8.2 is a major release requiring applications to be rewritten for new APIs. | «no» Пояснение: Symfony major releases introduce breaking changes requiring migration work, but not a full rewrite, and '8.2' would be a minor release within the 8.x line, not a major one.
Raw{"answer": "no", "explanation": "Symfony major releases introduce breaking changes requiring migration work, but not a full rewrite, and '8.2' would be a minor release within the 8.x line, not a major one."} | верно | Наоборот: 8.2 — минорный релиз; новые возможности без поломки обратной совместимости. Мажор — 9.0. |
T29-L5 2.12 c | Symfony: 8.2 and beyond | Updating within a major branch (8.1 → 8.2) should not require code changes — backward compatibility is preserved. | «yes» Пояснение: PHP's backward compatibility policy guarantees that within the same major version (e.g., 8.1 → 8.2), existing code will not be broken; only new features are added and deprecations may be introduced without removal.
Raw{"answer": "yes", "explanation": "PHP's backward compatibility policy guarantees that within the same major version (e.g., 8.1 → 8.2), existing code will not be broken; only new features are added and deprecations may be introduced without removal."} | верно | Политика Symfony: минорные релизы обратно совместимы; BC-break допустим только в мажорных. |
T29-L6 2.92 c | Symfony: 8.2 and beyond | Which minor version of the 8.x branch is released last, before Symfony 9.0? | «8.4» Пояснение: Following Symfony's pattern of five minor releases per major branch (like 5.4 and 6.4), the last minor version of the 8.x line before 9.0 is 8.4.
Raw{"answer": "8.4", "explanation": "Following Symfony's pattern of five minor releases per major branch (like 5.4 and 6.4), the last minor version of the 8.x line before 9.0 is 8.4."} | верно | По циклу: 8.2 (ноя 2026), 8.3 (май 2027), 8.4 (ноя 2027, вместе с 9.0) — как 6.4 выходила вместе с 7.0. |
T29-L7 1.62 c | Symfony: 8.2 and beyond | Symfony 8.2 will require PHP 8.5 — you would have to upgrade PHP along with it. | «no» Пояснение: Symfony 8.2 does not exist; the current major line is Symfony 7.x, and no such version with a PHP 8.5 requirement is documented.
Raw{"answer": "no", "explanation": "Symfony 8.2 does not exist; the current major line is Symfony 7.x, and no such version with a PHP 8.5 requirement is documented."} | верно | Наоборот: минорные релизы не поднимают требования PHP; для всей ветки 8.x остаётся PHP >= 8.4. |
T29-L8 1.54 c | Symfony: 8.2 and beyond | Deprecations added in the 8.x branch will not be removed before Symfony 9.0. | «yes» Пояснение: Symfony's deprecation policy guarantees that deprecated features are only removed in the next major version, so deprecations introduced in 8.x will persist at least until 9.0.
Raw```json ⏎ {"answer": "yes", "explanation": "Symfony's deprecation policy guarantees that deprecated features are only removed in the next major version, so deprecations introduced in 8.x will persist at least until 9.0."} ⏎ ``` | верно | Политика: деприкейшены живут до следующего мажора; 9.0 — ноябрь 2027. |
T21-L1 1.67 c | Twig | Inside {{ }}, Twig allows calling arbitrary PHP code directly. | «no» Пояснение: Twig's {{ }} syntax only supports its own limited expression language (variables, filters, basic operators, method calls on objects) and does not allow calling arbitrary PHP functions or code directly.
Raw{"answer": "no", "explanation": "Twig's {{ }} syntax only supports its own limited expression language (variables, filters, basic operators, method calls on objects) and does not allow calling arbitrary PHP functions or code directly."} | верно | Twig — DSL: только разрешённые окружением функции/фильтры; произвольный PHP не исполняется. |
T21-L2 0.78 c | Twig | By default, Twig auto-escapes printed variables. | «yes» Пояснение: Twig auto-escapes variables by default using the 'html' escaping strategy to prevent XSS attacks.
Raw{"answer": "yes", "explanation": "Twig auto-escapes variables by default using the 'html' escaping strategy to prevent XSS attacks."} | верно | Autoescape включён по умолчанию; {{ '<b>' }} → <b>. Проверено на Twig 3.30. |
T21-L3 1.03 c | Twig | The Twig |e filter escapes a string for safe output in an HTML context. | «yes» Пояснение: The |e filter (short for |escape) escapes a string for safe HTML output by default using htmlspecialchars.
Raw{"answer": "yes", "explanation": "The |e filter (short for |escape) escapes a string for safe HTML output by default using htmlspecialchars."} | верно | |e ('html') по умолчанию; есть контексты js/url/css. От SQL-инъекций он не защищает — это задача подготовленных запросов Doctrine. |
T21-L4 0.8 c | Twig | Which filter from twig/intl-extra formats a number according to a locale? | «number_format» Пояснение: The number_format filter from twig/intl-extra formats a number according to a given locale.
Raw{"answer": "number_format", "explanation": "The number_format filter from twig/intl-extra formats a number according to a given locale."} | неверно верный: «format_number» | |format_number(locale=...) из IntlExtension (twig/intl-extra есть в проекте). Проверено на Twig 3.30: 12345.6 → 12 345,6 (ru). |
T21-L5 1.27 c | Twig | The |raw filter disables auto-escaping for the value. | «yes» Пояснение: In Blade templates, the |raw filter prevents auto-escaping, allowing the value to be output as-is (equivalent to using {!! !!} syntax).
Raw{"answer": "yes", "explanation": "In Blade templates, the |raw filter prevents auto-escaping, allowing the value to be output as-is (equivalent to using {!! !!} syntax)."} | верно | {{ x|raw }} выводит HTML как есть; опасно с пользовательскими данными. Проверено на Twig 3.30. |
T21-L6 0.99 c | Twig | In Twig, {{ }} prints an expression value, while {% %} executes tags — conditions, loops, set. | «yes» Пояснение: In Twig, {{ }} is used to output the value of an expression, while {% %} is used to execute structural tags like if, for, and set.
Raw{"answer": "yes", "explanation": "In Twig, {{ }} is used to output the value of an expression, while {% %} is used to execute structural tags like if, for, and set."} | верно | Два блока синтаксиса Twig: вывод (echo) против логики. |
T21-L7 0.79 c | Twig | In Twig you cannot declare a variable inside a template — values only come from the controller. | «no» Пояснение: Twig allows declaring variables inside templates using the {% set %} tag.
Raw{"answer": "no", "explanation": "Twig allows declaring variables inside templates using the {% set %} tag."} | верно | {% set y = ... %} объявляет переменную в шаблоне. Проверено на Twig 3.30. |
T21-L8 0.62 c | Twig | Which Twig function dumps the debug structure of a variable (array, object)? | «dump» Пояснение: The dump() function in Twig outputs the debug structure of a variable, similar to var_dump() in PHP.
Raw{"answer": "dump", "explanation": "The dump() function in Twig outputs the debug structure of a variable, similar to var_dump() in PHP."} | верно | {{ dump(x) }} (DebugExtension; в Symfony доступна в dev-окружении). |
T24-L1 1.17 c | Bootstrap | Bootstrap is a CSS/JS library of ready-made UI components, not an SPA framework. | «yes» Пояснение: Bootstrap is a front-end CSS/JS library providing UI components (grids, buttons, modals, etc.) and is not an SPA framework like React, Angular, or Vue.
Raw{"answer": "yes", "explanation": "Bootstrap is a front-end CSS/JS library providing UI components (grids, buttons, modals, etc.) and is not an SPA framework like React, Angular, or Vue."} | верно | Компоненты и утилиты поверх вашего HTML; SPA-фреймворки (React/Vue) — другой класс инструментов. В проекте vendored 5.3.3. |
T24-L2 1.03 c | Bootstrap | Which Bootstrap class gives a responsive container with a fixed max width per breakpoint? | «container» Пояснение: The .container class in Bootstrap provides a responsive centered container with a fixed max-width at each breakpoint, unlike .container-fluid which is always 100% width.
Raw{"answer": "container", "explanation": "The .container class in Bootstrap provides a responsive centered container with a fixed max-width at each breakpoint, unlike .container-fluid which is always 100% width."} | верно | .container (фиксированная макс-ширина по брейкпоинтам) vs .container-fluid (на всю ширину). |
T24-L3 0.99 c | Bootstrap | The Bootstrap grid is built on CSS floats and splits a row into 16 columns. | «no» Пояснение: The Bootstrap grid splits a row into 12 columns (not 16), and modern Bootstrap (v4+) uses Flexbox rather than CSS floats.
Raw{"answer": "no", "explanation": "The Bootstrap grid splits a row into 12 columns (not 16), and modern Bootstrap (v4+) uses Flexbox rather than CSS floats."} | верно | Наоборот: flexbox (с Bootstrap 4) и 12 колонок; float-сетка — это Bootstrap 3. |
T24-L4 0.83 c | Bootstrap | Bootstrap's named breakpoints (the infix used in class names) are sm, md, lg, xl, xxl — five of them. | «yes» Пояснение: Bootstrap 5 defines exactly five named breakpoints: sm, md, lg, xl, and xxl.
Raw{"answer": "yes", "explanation": "Bootstrap 5 defines exactly five named breakpoints: sm, md, lg, xl, and xxl."} | верно | Тиров всего шесть: xs (без инфикса) + пять именованных (576/768/992/1200/1400 px). |
T24-L5 0.95 c | Bootstrap | Utilities like .mt-3 or .px-2 use the spacing scale: the number is a multiple of $spacer. | «yes» Пояснение: In Bootstrap, spacing utilities like .mt-3 or .px-2 compute their value as the number multiplied by $spacer (e.g., 3 * $spacer).
Raw{"answer": "yes", "explanation": "In Bootstrap, spacing utilities like .mt-3 or .px-2 compute their value as the number multiplied by $spacer (e.g., 3 * $spacer)."} | неверно верный: «no» | Spacing utilities; $spacer = 1rem. |
T24-L6 0.91 c | Bootstrap | Which Bootstrap 5 data attribute enables an interactive component (e.g. dropdown) on an element? | «data-bs-toggle» Пояснение: In Bootstrap 5, the data-bs-toggle attribute is used to enable interactive components such as dropdowns, tooltips, popovers, and collapse on an element.
Raw{"answer": "data-bs-toggle", "explanation": "In Bootstrap 5, the data-bs-toggle attribute is used to enable interactive components such as dropdowns, tooltips, popovers, and collapse on an element."} | верно | data-bs-toggle="dropdown" и т.п.; в Bootstrap 4 атрибут назывался data-toggle. |
T24-L7 0.72 c | Bootstrap | Bootstrap 5 components work without jQuery — in plain vanilla JS. | «yes» Пояснение: Bootstrap 5 removed its jQuery dependency and all components are built with vanilla JavaScript.
Raw{"answer": "yes", "explanation": "Bootstrap 5 removed its jQuery dependency and all components are built with vanilla JavaScript."} | верно | jQuery удалён в Bootstrap 5.0: data-bs-* атрибуты и JS API. В проекте vendored 5.3.3. |
T24-L8 0.79 c | Bootstrap | Dark mode in Bootstrap is enabled with a .dark class on the root element. | «no» Пояснение: Bootstrap 5 dark mode is enabled with the data-bs-theme="dark" attribute, not a .dark class.
Raw{"answer": "no", "explanation": "Bootstrap 5 dark mode is enabled with the data-bs-theme=\"dark\" attribute, not a .dark class."} | верно | Наоборот: тема включается атрибутом data-bs-theme="dark" (Color modes, с 5.3); класса .dark не существует. В проекте 5.3.3. |
T14-L1 0.93 c | Doctrine | Doctrine ORM creates database tables on the fly the first time an entity is used at runtime. | «no» Пояснение: Doctrine ORM does not automatically create tables at runtime; you must explicitly run schema tools (e.g., orm:schema-tool:update) to create or update the database schema.
Raw{"answer": "no", "explanation": "Doctrine ORM does not automatically create tables at runtime; you must explicitly run schema tools (e.g., orm:schema-tool:update) to create or update the database schema."} | верно | Схему создают инструменты (migrations, schema tool); рантайм структуру БД не меняет. |
T14-L2 0.84 c | Doctrine | Which EntityManager method marks a new object as managed without executing SQL until flush()? | «persist» Пояснение: EntityManager::persist() marks an entity as managed and schedules an INSERT, but the SQL is only executed when flush() is called.
Raw{"answer": "persist", "explanation": "EntityManager::persist() marks an entity as managed and schedules an INSERT, but the SQL is only executed when flush() is called."} | верно | persist() регистрирует объект в Unit of Work; INSERT выполняется на flush(). |
T14-L3 0.84 c | Doctrine | In Doctrine ORM 3, the EntityManager::merge() method exists and makes the passed object managed. | «yes» Пояснение: EntityManager::merge() exists in Doctrine ORM 3 and returns a managed copy of the passed detached entity.
Raw{"answer": "yes", "explanation": "EntityManager::merge() exists in Doctrine ORM 3 and returns a managed copy of the passed detached entity."} | неверно верный: «no» | В ORM 3 merge() удалён (в vendor проекта 3.7.6 метода нет); в Doctrine 2.x merge() возвращал управляемую копию. Версия зафиксирована — ORM 3. |
T14-L4 1.15 c | Doctrine | DQL queries are written in terms of entities and their fields, not tables and columns. | «yes» Пояснение: DQL (Doctrine Query Language) is an ORM-level query language that uses entity names and their mapped fields rather than raw table and column names.
Raw{"answer": "yes", "explanation": "DQL (Doctrine Query Language) is an ORM-level query language that uses entity names and their mapped fields rather than raw table and column names."} | верно | Doctrine транслирует DQL в SQL; docs — DQL (Doctrine Query Language). |
T14-L5 0.79 c | Doctrine | What does $repository->find(999) return when no record with id 999 exists? | «null» Пояснение: Doctrine's EntityRepository::find() returns null when no entity with the given ID is found.
Raw{"answer": "null", "explanation": "Doctrine's EntityRepository::find() returns null when no entity with the given ID is found."} | верно | find() возвращает null, если объект не найден (docs Repository methods). |
T14-L6 1.05 c | Doctrine | DoctrineBundle in Symfony automatically calls flush() at the end of every request. | «yes» Пояснение: By default, DoctrineBundle's auto_commit option is true, which causes flush() to be called automatically at the end of each request.
Raw{"answer": "yes", "explanation": "By default, DoctrineBundle's auto_commit option is true, which causes flush() to be called automatically at the end of each request."} | неверно верный: «no» | Авто-flush нет — flush() зовёт разработчик; незакрытая транзакция в конце запроса откатывается. |
T14-L7 1.38 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» Пояснение: The Unit of Work tracks managed entities and detects property changes automatically, so flush() will generate the appropriate UPDATE query without needing an explicit persist() call.
Raw{"answer": "yes", "explanation": "The Unit of Work tracks managed entities and detects property changes automatically, so flush() will generate the appropriate UPDATE query without needing an explicit persist() call."} | верно | Dirty checking сравнивает снимки свойств; persist нужен только новым/отсоединённым объектам. |
T14-L8 0.99 c | Doctrine | remove() executes the SQL DELETE immediately, without waiting for flush(). | «no» Пояснение: Doctrine's remove() only schedules the deletion in the Unit of Work; the actual SQL DELETE is executed when flush() is called.
Raw{"answer": "no", "explanation": "Doctrine's remove() only schedules the deletion in the Unit of Work; the actual SQL DELETE is executed when flush() is called."} | верно | remove() планирует удаление в Unit of Work; DELETE выполняется на flush() (docs — Deleting Objects). |
T15-L1 1.07 c | PostgreSQL | PostgreSQL uses MVCC, therefore readers block writers and writers block readers. | «no» Пояснение: MVCC's purpose is precisely the opposite: readers do not block writers and writers do not block readers, as they operate on different versions of the data.
Raw{"answer": "no", "explanation": "MVCC's purpose is precisely the opposite: readers do not block writers and writers do not block readers, as they operate on different versions of the data."} | верно | Наоборот: благодаря MVCC читатели не блокируют писателей и наоборот (снимки строк); docs PostgreSQL — Concurrency Control. |
T15-L2 1.06 c | PostgreSQL | Which SQL command shows a query's execution plan without executing the query? | «explain» Пояснение: The EXPLAIN command displays the query execution plan without actually running the query.
Raw{"answer": "EXPLAIN", "explanation": "The EXPLAIN command displays the query execution plan without actually running the query."} | верно | EXPLAIN без ANALYZE только строит план; проверено на PostgreSQL 17.7. |
T15-L3 2.37 c | PostgreSQL | SERIAL and GENERATED ... AS IDENTITY are just two names for the same mechanism. | «no» Пояснение: While both auto-generate integers, SERIAL is a PostgreSQL shorthand that creates a separate sequence + default + unique constraint, whereas GENERATED AS IDENTITY is a SQL-standard column attribute with different management and behavior.
Raw{"answer": "no", "explanation": "While both auto-generate integers, SERIAL is a PostgreSQL shorthand that creates a separate sequence + default + unique constraint, whereas GENERATED AS IDENTITY is a SQL-standard column attribute with different management and behavior."} | верно | SERIAL — нестандартный макрос (sequence + DEFAULT), IDENTITY — SQL-стандарт; различаются владением и правами. Оба есть в PG 17 (проверено). |
T15-L4 1.02 c | PostgreSQL | By default, a PostgreSQL UNIQUE constraint allows only one row with NULL in the column. | «no» Пояснение: In PostgreSQL, NULL values are considered distinct from each other, so a UNIQUE constraint allows multiple rows with NULL in the same column.
Raw{"answer": "no", "explanation": "In PostgreSQL, NULL values are considered distinct from each other, so a UNIQUE constraint allows multiple rows with NULL in the same column."} | верно | Наоборот: NULLS DISTINCT по умолчанию — несколько NULL допустимы; NULLS NOT DISTINCT — опция с PG 15. Проверено на PG 17.7. |
T15-L5 0.59 c | PostgreSQL | Which PostgreSQL aggregate function concatenates strings with a separator? | «string_agg» Пояснение: PostgreSQL's string_agg() aggregate function concatenates strings with a specified separator.
Raw{"answer": "string_agg", "explanation": "PostgreSQL's string_agg() aggregate function concatenates strings with a specified separator."} | верно | string_agg(значение, разделитель); проверено на PostgreSQL 17.7. |
T15-L6 1.81 c | PostgreSQL | Plain VACUUM returns the space occupied by dead tuples to the operating system. | «no» Пояснение: Plain VACUUM only marks dead tuple space as reusable within the table; it does not return space to the operating system (that requires VACUUM FULL).
Raw{"answer": "no", "explanation": "Plain VACUUM only marks dead tuple space as reusable within the table; it does not return space to the operating system (that requires VACUUM FULL)."} | верно | VACUUM помечает место для переиспользования внутри таблицы; ОС его возвращает только VACUUM FULL (с эксклюзивной блокировкой). |
T15-L7 0.61 c | PostgreSQL | Which keyword in a window function definition partitions rows into groups the function is computed over? | «partition by» Пояснение: The PARTITION BY clause in a window function divides the result set into groups over which the window function is computed.
Raw{"answer": "PARTITION BY", "explanation": "The PARTITION BY clause in a window function divides the result set into groups over which the window function is computed."} | верно | OVER (PARTITION BY ...); проверено на PostgreSQL 17.7. |
T15-L8 1.14 c | PostgreSQL | The READ COMMITTED isolation level protects against non-repeatable reads. | «no» Пояснение: READ COMMITTED only prevents dirty reads; non-repeatable reads are prevented at the REPEATABLE READ level or higher.
Raw{"answer": "no", "explanation": "READ COMMITTED only prevents dirty reads; non-repeatable reads are prevented at the REPEATABLE READ level or higher."} | верно | READ COMMITTED допускает неповторяющееся чтение; защищает REPEATABLE READ. Проверено: SHOW transaction_isolation → read committed. |
T17-L1 0.9 c | PostgreSQL: transactions and indexes | By default, PostgreSQL wraps each single SQL statement in its own implicit transaction (autocommit). | «yes» Пояснение: By default, PostgreSQL runs in autocommit mode, where each SQL statement is automatically committed upon completion unless explicitly wrapped in a BEGIN...COMMIT block.
Raw{"answer": "yes", "explanation": "By default, PostgreSQL runs in autocommit mode, where each SQL statement is automatically committed upon completion unless explicitly wrapped in a BEGIN...COMMIT block."} | верно | Без BEGIN каждый оператор коммитится сам; docs PostgreSQL — Transactions. Проверено на PG 17. |
T17-L2 0.42 c | PostgreSQL: transactions and indexes | Which SQL command ends a transaction, committing all its changes? | «commit» Пояснение: The COMMIT SQL command ends a transaction and permanently saves all changes made within it.
Raw{"answer": "COMMIT", "explanation": "The COMMIT SQL command ends a transaction and permanently saves all changes made within it."} | верно | COMMIT (END — синоним). Проверено на PG 17. |
T17-L3 0.92 c | PostgreSQL: transactions and indexes | Indexes speed up more than SELECT: UPDATE and DELETE with a search on an indexed column benefit too. | «yes» Пояснение: Indexes help the database engine quickly locate rows for any DML operation (SELECT, UPDATE, DELETE) that uses the indexed column in the WHERE clause.
Raw{"answer": "yes", "explanation": "Indexes help the database engine quickly locate rows for any DML operation (SELECT, UPDATE, DELETE) that uses the indexed column in the WHERE clause."} | верно | Поиск строк для изменения идёт по индексу; docs PostgreSQL — Indexes. |
T17-L4 0.85 c | PostgreSQL: transactions and indexes | To roll back part of the statements inside a transaction, PostgreSQL uses SAVEPOINT. | «yes» Пояснение: SAVEPOINT allows you to create a named point within a transaction that you can roll back to, undoing only the statements after that point without aborting the entire transaction.
Raw{"answer": "yes", "explanation": "SAVEPOINT allows you to create a named point within a transaction that you can roll back to, undoing only the statements after that point without aborting the entire transaction."} | верно | SAVEPOINT name; ROLLBACK TO name — частичный откат без отмены всей транзакции. Проверено на PG 17. |
T17-L5 0.82 c | PostgreSQL: transactions and indexes | EXPLAIN ANALYZE shows the query plan without executing the query. | «no» Пояснение: EXPLAIN ANALYZE actually executes the query and reports real execution times, whereas plain EXPLAIN shows the plan without executing.
Raw{"answer": "no", "explanation": "EXPLAIN ANALYZE actually executes the query and reports real execution times, whereas plain EXPLAIN shows the plan without executing."} | верно | Наоборот: ANALYZE реально выполняет запрос (с побочными эффектами!) и показывает фактические времена узлов; план без выполнения — plain EXPLAIN. |
T17-L6 0.62 c | PostgreSQL: transactions and indexes | Which PostgreSQL extension adds vector types and indexes for embedding search? | «pgvector» Пояснение: pgvector is a PostgreSQL extension that adds a vector type and supports vector similarity indexing for embedding search.
Raw{"answer": "pgvector", "explanation": "pgvector is a PostgreSQL extension that adds a vector type and supports vector similarity indexing for embedding search."} | верно | CREATE EXTENSION vector (проект pgvector; в проекте образ pgvector/pgvector:pg17). |
T17-L7 1.46 c | PostgreSQL: transactions and indexes | A partial index (CREATE INDEX ... WHERE ...) is built only over rows satisfying the condition. | «yes» Пояснение: A partial index in PostgreSQL contains only the rows that satisfy the specified WHERE condition, reducing index size and improving performance for targeted queries.
Raw{"answer": "yes", "explanation": "A partial index in PostgreSQL contains only the rows that satisfy the specified WHERE condition, reducing index size and improving performance for targeted queries."} | верно | docs PostgreSQL — Partial Indexes; типичный кейс — индекс по «активным» записям. |
T17-L8 1.97 c | PostgreSQL: transactions and indexes | The SERIALIZABLE level in PostgreSQL is implemented by locking the rows a transaction reads. | «no» Пояснение: PostgreSQL implements SERIALIZABLE using Serializable Snapshot Isolation (SSI), which relies on MVCC and anomaly detection/aborts, not by locking rows read by the transaction.
Raw{"answer": "no", "explanation": "PostgreSQL implements SERIALIZABLE using Serializable Snapshot Isolation (SSI), which relies on MVCC and anomaly detection/aborts, not by locking rows read by the transaction."} | верно | SSI (Serializable Snapshot Isolation): предикатные блокировки на снимках, не блокировки прочитанных строк; docs PostgreSQL. |
T19-L1 0.67 c | HTTP and REST API | HTTP status 201 means the request resulted in a new resource being created. | «yes» Пояснение: HTTP 201 'Created' indicates that the request was successful and a new resource was created as a result.
Raw{"answer": "yes", "explanation": "HTTP 201 'Created' indicates that the request was successful and a new resource was created as a result."} | верно | 201 Created; обычно на POST, часто с Location; RFC 9110. |
T19-L2 0.94 c | HTTP and REST API | Which HTTP status means a successful request with an empty response body (e.g. after DELETE)? | «204» Пояснение: HTTP 204 No Content indicates a successful request with an empty response body, commonly returned after DELETE operations.
Raw{"answer": 204, "explanation": "HTTP 204 No Content indicates a successful request with an empty response body, commonly returned after DELETE operations."} | верно | 204 No Content; RFC 9110. |
T19-L3 2.47 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» Пояснение: The HTTP specification (RFC 7231) explicitly classifies DELETE as an idempotent method, meaning repeated requests have the same effect on the server state.
Raw{"answer": "yes", "explanation": "The HTTP specification (RFC 7231) explicitly classifies DELETE as an idempotent method, meaning repeated requests have the same effect on the server state."} | верно | RFC 9110: DELETE идемпотентен (как PUT); идемпотентность ≠ безопасность — ресурс удаляется при первом вызове. |
T19-L4 1.05 c | HTTP and REST API | The Access-Control-Allow-Origin header is sent by the client so that the server agrees to accept requests from another origin. | «no» Пояснение: The Access-Control-Allow-Origin header is sent by the server (not the client) to indicate which origin is permitted to access the resource.
Raw{"answer": "no", "explanation": "The Access-Control-Allow-Origin header is sent by the server (not the client) to indicate which origin is permitted to access the resource."} | верно | Наоборот: заголовок шлёт СЕРВЕР в ответе, разрешая браузеру cross-origin запрос (CORS); в проекте nelmio/cors-bundle. |
T19-L5 0.97 c | HTTP and REST API | Status 429 Too Many Requests is used when a client exceeds a rate limit. | «yes» Пояснение: HTTP 429 Too Many Requests is specifically defined (RFC 6585) for indicating that a client has sent too many requests in a given time frame, i.e., it has exceeded a rate limit.
Raw{"answer": "yes", "explanation": "HTTP 429 Too Many Requests is specifically defined (RFC 6585) for indicating that a client has sent too many requests in a given time frame, i.e., it has exceeded a rate limit."} | верно | 429 (+ Retry-After); RFC 6585. В проекте symfony/rate-limiter. |
T19-L6 0.83 c | HTTP and REST API | 5xx codes mean a client error, while 4xx means a server-side error. | «no» Пояснение: It's the opposite: 4xx codes indicate client errors and 5xx codes indicate server errors.
Raw{"answer": "no", "explanation": "It's the opposite: 4xx codes indicate client errors and 5xx codes indicate server errors."} | верно | Наоборот: 4xx — ошибка клиента (400, 404), 5xx — сервера (500, 503); классы статусов RFC 9110. |
T19-L7 0.45 c | HTTP and REST API | Which HTTP header indicates the MIME type of the request or response body? | «content-type» Пояснение: The Content-Type HTTP header specifies the MIME type of the request or response body.
Raw{"answer": "Content-Type", "explanation": "The Content-Type HTTP header specifies the MIME type of the request or response body."} | верно | Content-Type: application/json и т.п. |
T19-L8 0.97 c | HTTP and REST API | PATCH is not required to be idempotent per RFC 5789, unlike PUT. | «yes» Пояснение: RFC 5789 explicitly states that PATCH is not idempotent by default, whereas PUT is required to be idempotent per RFC 7231.
Raw{"answer": "yes", "explanation": "RFC 5789 explicitly states that PATCH is not idempotent by default, whereas PUT is required to be idempotent per RFC 7231."} | верно | RFC 5789 прямо оговаривает: PATCH не гарантированно идемпотентен; PUT идемпотентен. |
T20-L1 0.95 c | Security and OAuth | Checking a password by comparing its hash to the stored hash with a plain == is sufficient. | «no» Пояснение: Using == is vulnerable to timing attacks; you should use hash_equals() for constant-time comparison.
Raw{"answer":"no","explanation":"Using == is vulnerable to timing attacks; you should use hash_equals() for constant-time comparison."} | верно | Нужна постоянновременная проверка (password_verify) — timing-атаки; соль и алгоритм уже внутри хеша. |
T20-L2 0.95 c | Security and OAuth | A CSRF token is issued by the server (bound to the session) and verified server-side on unsafe requests (POST etc.). | «yes» Пояснение: CSRF tokens are server-generated, bound to the session, and validated server-side on state-changing requests like POST, PUT, DELETE.
Raw{"answer": "yes", "explanation": "CSRF tokens are server-generated, bound to the session, and validated server-side on state-changing requests like POST, PUT, DELETE."} | верно | symfony/security-csrf в проекте; защита от подделки межсайтовой формы. |
T20-L3 0.61 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 which resources are allowed to load on a page.
Raw{"answer": "Content-Security-Policy", "explanation": "The Content-Security-Policy HTTP header is used to declare which resources are allowed to load on a page."} | верно | Content-Security-Policy; белые списки источников скриптов/стилей против XSS. |
T20-L4 1.21 c | Security and OAuth | OAuth 2.0 is an authentication protocol: the access token tells you who the user is. | «no» Пояснение: OAuth 2.0 is an authorization protocol, not an authentication protocol; it grants access to resources on behalf of a user without necessarily identifying who that user is (that's OpenID Connect's role).
Raw{"answer": "no", "explanation": "OAuth 2.0 is an authorization protocol, not an authentication protocol; it grants access to resources on behalf of a user without necessarily identifying who that user is (that's OpenID Connect's role)."} | верно | OAuth 2.0 — авторизация/делегирование доступа; аутентификацию добавляет OpenID Connect. В проекте knpuniversity/oauth2-client-bundle (yandex/github/google). |
T20-L5 1.55 c | Security and OAuth | XSS is prevented by validating input on the server before writing it to the database. | «no» Пояснение: XSS is primarily prevented by context-aware output encoding when rendering data in HTML, not by input validation before database storage.
Raw{"answer": "no", "explanation": "XSS is primarily prevented by context-aware output encoding when rendering data in HTML, not by input validation before database storage."} | верно | XSS лечится контекстным экранированием НА ВЫВОДЕ (Twig autoescape, CSP); валидация ввода не покрывает все контексты вывода. |
T20-L6 0.89 c | Security and OAuth | In the OAuth 2.0 authorization code flow, which parameter arrives at the redirect_uri and is exchanged for an access token? | «code» Пояснение: In the OAuth 2.0 authorization code flow, the 'code' parameter is returned to the redirect_uri and then exchanged for an access token at the token endpoint.
Raw{"answer": "code", "explanation": "In the OAuth 2.0 authorization code flow, the 'code' parameter is returned to the redirect_uri and then exchanged for an access token at the token endpoint."} | верно | Параметр code; обмен на токен POST-ом на /token с client_secret. |
T20-L7 1.0 c | Security and OAuth | A refresh token lives longer than an access token and allows obtaining a new access token without the user logging in again. | «yes» Пояснение: Refresh tokens are designed to have a longer lifespan than access tokens and are used to obtain new access tokens without requiring the user to re-authenticate.
Raw{"answer": "yes", "explanation": "Refresh tokens are designed to have a longer lifespan than access tokens and are used to obtain new access tokens without requiring the user to re-authenticate."} | верно | Стандартная схема OAuth/OIDC: короткий access + длинный refresh. |
T20-L8 1.4 c | Security and OAuth | A password salt must be kept secret: without it the hash cannot be verified. | «no» Пояснение: The salt does not need to be secret; it is typically stored alongside the hash (e.g., in bcrypt or argon2 output) and its purpose is uniqueness, not confidentiality.
Raw{"answer": "no", "explanation": "The salt does not need to be secret; it is typically stored alongside the hash (e.g., in bcrypt or argon2 output) and its purpose is uniqueness, not confidentiality."} | верно | Соль хранится открыто (password_hash включает её в строку хеша); секретность соли не нужна. |
T18-L1 0.92 c | Testing: PHPUnit | PHPUnit runs test methods of any class — extending TestCase is not required. | «no» Пояснение: PHPUnit requires test classes to extend PHPUnit\Framework\TestCase in order to be recognized and executed.
Raw{"answer": "no", "explanation": "PHPUnit requires test classes to extend PHPUnit\\Framework\\TestCase in order to be recognized and executed."} | верно | Тестом считается метод класса, наследующего TestCase (PHPUnit 10). |
T18-L2 0.71 c | Testing: PHPUnit | In PHPUnit, setUp() runs once before all tests of the class. | «no» Пояснение: setUp() runs before each test method; setUpBeforeClass() (static) runs once before all tests.
Raw{"answer": "no", "explanation": "setUp() runs before each test method; setUpBeforeClass() (static) runs once before all tests."} | верно | setUp() — перед КАЖДЫМ тестом; один раз на класс — setUpBeforeClass(). Проверено живым счётчиком на PHPUnit 10.5. |
T18-L3 1.15 c | Testing: PHPUnit | A data provider lets a test run with exactly one set of arguments. | «no» Пояснение: A data provider allows a test to run with multiple sets of arguments, not just one.
Raw{"answer": "no", "explanation": "A data provider allows a test to run with multiple sets of arguments, not just one."} | верно | Наоборот: наборов может быть сколько угодно — тест выполняется по разу на каждый. Проверено на PHPUnit 10.5 (#[DataProvider]). |
T18-L4 0.78 c | Testing: PHPUnit | Which PHPUnit method declares an expectation that an exception of a given class is thrown? | «expectexception» Пояснение: The PHPUnit method expectException() declares an expectation that an exception of the given class will be thrown.
Raw{"answer": "expectException", "explanation": "The PHPUnit method expectException() declares an expectation that an exception of the given class will be thrown."} | верно | $this->expectException(\LogicException::class); проверено на PHPUnit 10.5. |
T18-L5 1.06 c | Testing: PHPUnit | In PHPUnit, a stub verifies which methods were called on it, while a mock only returns data. | «no» Пояснение: It's the opposite: a stub returns pre-programmed data, while a mock verifies which methods were called (and can also return data).
Raw{"answer": "no", "explanation": "It's the opposite: a stub returns pre-programmed data, while a mock verifies which methods were called (and can also return data)."} | верно | Наоборот: стаб подставляет данные, мок проверяет взаимодействия (createStub/createMock); docs PHPUnit — Test Doubles. |
T18-L6 0.8 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» Пояснение: PHPUnit 10 deprecated the @dataProvider docblock annotation in favor of the #[DataProvider] PHP attribute.
Raw{"answer": "yes", "explanation": "PHPUnit 10 deprecated the @dataProvider docblock annotation in favor of the #[DataProvider] PHP attribute."} | верно | Аннотация ещё парсится в PHPUnit 10/11 (AnnotationParser в 10.5.66), удаление — в 12; атрибут — стандарт. |
T18-L7 1.04 c | Testing: PHPUnit | PHPUnit does not allow one test to depend on the result of another. | «no» Пояснение: PHPUnit supports test dependencies via the @depends annotation or depends() method, allowing one test to receive the result of another as a parameter.
Raw{"answer": "no", "explanation": "PHPUnit supports test dependencies via the @depends annotation or depends() method, allowing one test to receive the result of another as a parameter."} | верно | Зависимости есть: #[Depends] — зависимый тест не запустится, еслиProducer упал. |
T18-L8 1.21 c | Testing: PHPUnit | Which PHPUnit command-line option makes tests run in random order? | «--order-by=random» Пояснение: PHPUnit's --order-by option accepts 'random' as a value to shuffle test execution order.
Raw{"answer": "--order-by=random", "explanation": "PHPUnit's --order-by option accepts 'random' as a value to shuffle test execution order."} | верно | --order-by=random (PHPUnit 9+); опция есть в --help PHPUnit 10.5 (проектная). |
T01-L9 3.86 c | Syntax and operators | What does this code output?
```php
echo intdiv(7, 2) . intdiv(-7, 2);
``` | «3-4» Пояснение: intdiv(7,2) is 3 and intdiv(-7,2) is -4 (floor division), concatenated as string '3-4'.
Raw{"answer": "3-4", "explanation": "intdiv(7,2) is 3 and intdiv(-7,2) is -4 (floor division), concatenated as string '3-4'."} | неверно верный: «3-3» | intdiv truncates toward zero: intdiv(-7, 2) = -3, not -4. |
T01-L10 1.26 c | Syntax and operators | What does this code output?
```php
echo -3 ** 2;
``` | «-9» Пояснение: In PHP, the exponentiation operator ** has higher precedence than unary minus, so -3 ** 2 is parsed as -(3 ** 2) = -9.
Raw{"answer": -9, "explanation": "In PHP, the exponentiation operator ** has higher precedence than unary minus, so -3 ** 2 is parsed as -(3 ** 2) = -9."} | верно | ** is right-associative and binds tighter than unary minus: -(3²). |
T02-L9 0.9 c | Types and comparisons | What does this code output?
```php
echo '1e1' == '10' ? 'true' : 'false';
``` | «true» Пояснение: Both '1e1' and '10' are numeric strings, so PHP compares them as numbers (10 == 10), making the condition true.
Raw{"answer": "true", "explanation": "Both '1e1' and '10' are numeric strings, so PHP compares them as numbers (10 == 10), making the condition true."} | верно | Both strings are numeric — compared as numbers: 10 == 10. |
T02-L10 1.04 c | Types and comparisons | What does this code output?
```php
switch ('a') {
case 0: echo 'zero'; break;
default: echo 'other';
}
``` | «other» Пояснение: 'a' loosely compared to 0 is false (non-numeric string), so it falls to the default case.
Raw{"answer": "other", "explanation": "'a' loosely compared to 0 is false (non-numeric string), so it falls to the default case."} | верно | PHP 8: 'a' == 0 → false (used to be true) — default fires. |
T03-L9 1.62 c | Strings | What does this code output?
```php
echo strtr('abc', ['a' => '1', 'ab' => '2']);
``` | «2c» Пояснение: strtr with an array replaces keys sorted by length (longest first), so 'ab' is replaced with '2' first, yielding '2c', then 'a' is not found in the remaining string.
Raw{"answer": "2c", "explanation": "strtr with an array replaces keys sorted by length (longest first), so 'ab' is replaced with '2' first, yielding '2c', then 'a' is not found in the remaining string."} | верно | strtr with an array prefers the longest matching key. |
T03-L10 1.5 c | Strings | What does this code output?
```php
echo '[' . substr('hello', -10) . ']';
``` | «[]» Пояснение: The string 'hello' has length 5, so offset -10 is before the start of the string, causing substr to return an empty string.
Raw{"answer": "[]", "explanation": "The string 'hello' has length 5, so offset -10 is before the start of the string, causing substr to return an empty string."} | неверно верный: «[hello]» | A negative start beyond the string is clamped to the beginning. |
T04-L9 1.56 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 union operator + keeps keys from $a and only adds non-duplicate keys from $b, so the result has keys k, n, m.
Raw{"answer": "k,n,m", "explanation": "The union operator + keeps keys from $a and only adds non-duplicate keys from $b, so the result has keys k, n, m."} | верно | The + operator: on duplicate string keys the left array wins. |
T04-L10 1.93 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» Пояснение: After sorting by the third element (index 2), the order is [2,'y',1], [1,'x',2], [3,'z',2], and extracting column 1 gives 'y','x','z' → 'yxz'.
Raw{"answer": "yxz", "explanation": "After sorting by the third element (index 2), the order is [2,'y',1], [1,'x',2], [3,'z',2], and extracting column 1 gives 'y','x','z' → 'yxz'."} | верно | Sorts are stable since 8.0: x and z keep their order on a tie. |
T05-L10 1.2 c | Functions and closures | What does this code output?
```php
function f(int $a, int $b): int
{
return $a - $b;
}
echo f(...['b' => 1, 'a' => 5]);
``` | «4» Пояснение: The spread operator with an associative array maps values by key to parameter names, so $a=5 and $b=1, giving 5-1=4.
Raw{"answer": 4, "explanation": "The spread operator with an associative array maps values by key to parameter names, so $a=5 and $b=1, giving 5-1=4."} | верно | String keys of a spread array become named arguments. |
T05-L9 2.06 c | Functions and closures | What does this code output?
```php
class P
{
private int $v = 3;
public function g(): int { return $this->v; }
}
$p = new P;
$f = $p->g(...);
$p = null;
echo $f();
``` | «3» Пояснение: The closure created by $p->g(...) holds a reference to the object, so even after $p = null, the object is still alive and $f() calls g() which returns $this->v = 3.
Raw```json ⏎ {"answer": 3, "explanation": "The closure created by $p->g(...) holds a reference to the object, so even after $p = null, the object is still alive and $f() calls g() which returns $this->v = 3."} ⏎ ``` | верно | First-class callable syntax binds $this at creation time. |
T06-L9 1.1 c | OOP: classes and inheritance | What does this code output?
```php
class A
{
public function who(): string { return static::class; }
}
class B extends A {}
echo (new B)->who();
``` | «b» Пояснение: static::class uses late static binding, so it resolves to the class of the actual object instance (B), not the class where the method is defined (A).
Raw{"answer": "B", "explanation": "static::class uses late static binding, so it resolves to the class of the actual object instance (B), not the class where the method is defined (A)."} | верно | Late static binding: static::class is the receiver's class. |
T06-L10 4.52 c | OOP: classes and inheritance | What does this code output on PHP 8.5?
```php
class C
{
public int $x = 0 {
set { $this->x = $value * 2; }
}
}
$c = new C;
$c->x = 5;
echo $c->x;
``` | «10» Пояснение: The set hook multiplies the value by 2 (5*2=10), and since no get hook is defined, the default getter returns the backing store value of 10.
Raw```json ⏎ {"answer": 10, "explanation": "The set hook multiplies the value by 2 (5*2=10), and since no get hook is defined, the default getter returns the backing store value of 10."} ⏎ ``` | верно | Inside the set hook, $this->x writes the backing store (no recursion): 5*2. |
T07-L9 1.25 c | Interfaces, traits, enum | What does this code output?
```php
trait TA
{
public function f(): string { return 'A'; }
}
trait TB
{
public function f(): string { return 'B'; }
}
class TC
{
use TA, TB { TB::f insteadof TA; TA::f as g; }
}
echo (new TC)->f() . (new TC)->g();
``` | «ba» Пояснение: TB::f insteadof TA means f() returns 'B', and TA::f as g aliases TA's f to g() returning 'A', so concatenation gives 'BA'.
Raw{"answer": "BA", "explanation": "TB::f insteadof TA means f() returns 'B', and TA::f as g aliases TA's f to g() returning 'A', so concatenation gives 'BA'."} | верно | insteadof picks the implementation; as keeps the other under an alias. |
T07-L10 1.41 c | Interfaces, traits, enum | What does this code output?
```php
trait Counter
{
public static int $n = 0;
}
class CX { use Counter; }
class CY { use Counter; }
CX::$n = 1;
echo CY::$n;
``` | «0» Пояснение: Each class that uses a trait gets its own independent copy of static properties, so CX::$n = 1 does not affect CY::$n which remains 0.
Raw{"answer": 0, "explanation": "Each class that uses a trait gets its own independent copy of static properties, so CX::$n = 1 does not affect CY::$n which remains 0."} | верно | A trait's static property is copied into each consuming class. |
T08-L10 0.78 c | Exceptions and errors | What does this code output?
```php
function f(): int
{
try { return 1; } finally { return 2; }
}
echo f();
``` | «2» Пояснение: In PHP, a return statement in a finally block overrides the return value from the try block.
Raw{"answer": 2, "explanation": "In PHP, a return statement in a finally block overrides the return value from the try block."} | верно | A return in finally overrides the return from try. |
T08-L9 1.25 c | Exceptions and errors | What does this code output?
```php
try {
try {
throw new RuntimeException('first');
} finally {
throw new LogicException('second');
}
} catch (LogicException $e) {
echo $e->getMessage();
}
``` | «second» Пояснение: The finally block throws a new LogicException which replaces the pending RuntimeException, and the outer catch block catches it and prints its message.
Raw{"answer": "second", "explanation": "The finally block throws a new LogicException which replaces the pending RuntimeException, and the outer catch block catches it and prints its message."} | верно | An exception from finally replaces the in-flight one — the last thrown is caught. |
T09-L9 1.48 c | Namespaces and autoloading | What does this code output?
```php
namespace N;
use App\Foo as Baz;
echo Baz::class . '|' . \Baz::class;
``` | «app\foo|baz» Пояснение: The use statement aliases App\Foo as Baz, so Baz::class resolves to App\Foo, while \Baz::class refers to the global class Baz.
Raw{"answer": "App\\Foo|Baz", "explanation": "The use statement aliases App\\Foo as Baz, so Baz::class resolves to App\\Foo, while \\Baz::class refers to the global class Baz."} | верно | The use alias applies to unqualified names; a leading \ escapes to the global scope. |
T09-L10 1.84 c | Namespaces and autoloading | What does this code output?
```php
namespace Ns;
class Foo {}
$c = 'Foo';
echo (class_exists($c) ? 'yes' : 'no')
. (class_exists(__NAMESPACE__ . '\\' . $c) ? 'yes' : 'no');
``` | «noyes» Пояснение: class_exists('Foo') looks in the global namespace and finds nothing, while class_exists('Ns\Foo') finds the defined class.
Raw{"answer": "noyes", "explanation": "class_exists('Foo') looks in the global namespace and finds nothing, while class_exists('Ns\\Foo') finds the defined class."} | верно | Dynamic names are not resolved against the namespace — 'Foo' is the global class. |
T10-L9 1.14 c | References and scope | What does this code output?
```php
$a = [1, 2, 3];
foreach ($a as &$v) {}
$v = 99;
echo implode(',', $a);
``` | «1,2,99» Пояснение: After the foreach by reference, $v remains a reference to the last element of $a, so setting $v=99 modifies $a[2].
Raw{"answer": "1,2,99", "explanation": "After the foreach by reference, $v remains a reference to the last element of $a, so setting $v=99 modifies $a[2]."} | верно | After a by-ref foreach, $v remains a reference to the last element. |
T10-L10 1.73 c | References and scope | What does this code output?
```php
class A
{
public function inc(): int
{
static $n = 0;
return ++$n;
}
}
class B extends A {}
$a = new A;
$b = new B;
$a->inc();
$b->inc();
echo $a->inc();
``` | «3» Пояснение: Static variables in PHP are shared across all instances and inherited calls, so $n increments to 1, 2, 3 across the three inc() calls.
Raw{"answer": 3, "explanation": "Static variables in PHP are shared across all instances and inherited calls, so $n increments to 1, 2, 3 across the three inc() calls."} | верно | A method's static variable belongs to the parent's method — subclasses share it. |
T11-L9 1.25 c | Generators, iterators, SPL | What does this code output?
```php
function g(): Generator
{
$x = yield 1;
return $x + 1;
}
$g = g();
$g->send(10);
echo $g->getReturn();
``` | «11» Пояснение: send(10) assigns 10 to $x, then the generator returns $x + 1 = 11, which is retrieved by getReturn().
Raw{"answer": 11, "explanation": "send(10) assigns 10 to $x, then the generator returns $x + 1 = 11, which is retrieved by getReturn()."} | верно | send() resumes the generator: $x = 10, return 10+1. |
T11-L10 1.42 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, then inner() returns 'ok' which is assigned to $r and yielded, producing the sequence 1, 2, ok.
Raw```json ⏎ {"answer": "1,2,ok", "explanation": "yield from inner() yields 1 and 2, then inner() returns 'ok' which is assigned to $r and yielded, producing the sequence 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.4 c | Configuration and security | What does this code output?
```php
$hash = password_hash('x', PASSWORD_BCRYPT, ['cost' => 4]);
echo password_needs_rehash($hash, PASSWORD_BCRYPT, ['cost' => 4]) ? 'yes' : 'no';
echo password_needs_rehash($hash, PASSWORD_BCRYPT, ['cost' => 5]) ? 'yes' : 'no';
``` | «noyes» Пояснение: The hash was created with cost 4, so it doesn't need rehashing at cost 4 (no), but does need rehashing at cost 5 (yes).
Raw{"answer": "noyes", "explanation": "The hash was created with cost 4, so it doesn't need rehashing at cost 4 (no), but does need rehashing at cost 5 (yes)."} | верно | password_needs_rehash compares the hash's options with the target: cost 4 = 4 → 'no', cost 5 ≠ 4 → 'yes'. |
T12-L10 7.0 c | Configuration and security | What does this code output on PHP 8.5?
```php
echo (E_ALL & 2048) === 0 ? 'strict-out' : 'strict-in';
``` | «strict-out» Пояснение: In PHP 8.5, E_STRICT (2048) is no longer included in the E_ALL bitmask, so E_ALL & 2048 evaluates to 0.
Raw```json ⏎ {"answer": "strict-out", "explanation": "In PHP 8.5, E_STRICT (2048) is no longer included in the E_ALL bitmask, so E_ALL & 2048 evaluates to 0."} ⏎ ``` | верно | Since PHP 8.4, E_STRICT is out of E_ALL: the 2048 bit is unset → 'strict-out' (2048 is the historical E_STRICT bit). |
T13-L9 2.82 c | Symfony | What does this code output?
```php
use Symfony\Component\HttpFoundation\Request;
$r = Request::create('/demo', 'GET', [], [], [], ['HTTP_X_TOKEN' => 'abc']);
echo $r->headers->get('X-Token') === 'abc' ? 'mapped' : 'missing';
``` | «mapped» Пояснение: Symfony's ServerBag strips the HTTP_ prefix and converts underscores to hyphens, and HeaderBag::get() is case-insensitive, so 'HTTP_X_TOKEN' maps to 'X-Token' returning 'abc'.
Raw```json ⏎ {"answer": "mapped", "explanation": "Symfony's ServerBag strips the HTTP_ prefix and converts underscores to hyphens, and HeaderBag::get() is case-insensitive, so 'HTTP_X_TOKEN' maps to 'X-Token' returning 'abc'."} ⏎ ``` | верно | The literal comparison requires knowing the mapping: HttpFoundation turns HTTP_X_TOKEN into the X-Token header (case-insensitive); without it the answer is 'missing'. |
T13-L10 10.66 c | Symfony | What does this code output?
```php
use Symfony\Component\EventDispatcher\EventDispatcher;
use Symfony\Contracts\EventDispatcher\Event;
$d = new EventDispatcher();
$out = '';
$d->addListener('e', function () use (&$out) { $out .= 'B'; }, 10);
$d->addListener('e', function () use (&$out) { $out .= 'A'; });
$d->addListener('e', function () use (&$out) { $out .= 'C'; }, 5);
$d->dispatch(new Event(), 'e');
echo $out;
``` | «bca» Пояснение: Symfony's EventDispatcher calls listeners in descending priority order (higher first): B (priority 10), C (priority 5), A (priority 0).
Raw```json ⏎ {"answer": "BCA", "explanation": "Symfony's EventDispatcher calls listeners in descending priority order (higher first): B (priority 10), C (priority 5), A (priority 0)."} ⏎ ``` | верно | Listeners run by descending priority: 10 (B), 5 (C), 0 (A). |
T14-L10 11.57 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» Пояснение: EntityManager::find() checks the UnitOfWork identity map first; since the entity was already persisted and is in the identity map, both calls return the same object instance.
Raw```json ⏎ {"answer": "same", "explanation": "EntityManager::find() checks the UnitOfWork identity map first; since the entity was already persisted and is in the identity map, both calls return the same object instance."} ⏎ ``` | верно | Identity map: a second find for the same id returns the same instance. |
T14-L9 2.18 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» Пояснение: Calling remove() on a persisted-but-never-flushed entity cancels the pending INSERT, so flush() has nothing to write to the database.
Raw```json ⏎ {"answer": 0, "explanation": "Calling remove() on a persisted-but-never-flushed entity cancels the pending INSERT, so flush() has nothing to write to the database."} ⏎ ``` | верно | The unit of work schedules INSERT at flush: remove after persist cancels it. |
T15-L10 0.73 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 non-NULL values in column x, so it returns 1 (the NULL row is excluded).
Raw{"answer": 1, "explanation": "COUNT(x) counts non-NULL values in column x, so it returns 1 (the NULL row is excluded)."} | верно | count(column) skips NULLs; count(*) would return 2. |
T15-L9 1.42 c | PostgreSQL | What does this SQL query return (PostgreSQL 17)?
```sql
CREATE TEMP TABLE t (id int, x int);
INSERT INTO t VALUES (1, 10), (2, 20), (3, 30);
SELECT string_agg(s::text, ',' ORDER BY id) FROM (
SELECT id, sum(x) OVER (ORDER BY id) AS s FROM t
) q;
``` | «10,30,60» Пояснение: The window function sum(x) OVER (ORDER BY id) produces a running sum (10, 30, 60), and string_agg concatenates them with commas in id order.
Raw{"answer": "10,30,60", "explanation": "The window function sum(x) OVER (ORDER BY id) produces a running sum (10, 30, 60), and string_agg concatenates them with commas in id order."} | верно | With ORDER BY the default window frame is running (start to current row). |
T16-L9 1.64 c | Symfony: Messenger | What does this code output?
```php
use Symfony\Component\Messenger\MessageBus;
use Symfony\Component\Messenger\Middleware\MiddlewareInterface;
use Symfony\Component\Messenger\Middleware\StackInterface;
use Symfony\Component\Messenger\Envelope;
final class Trace implements MiddlewareInterface
{
public function __construct(private string $tag) {}
public function handle(Envelope $e, StackInterface $stack): Envelope
{
echo $this->tag;
return $stack->next()->handle($e, $stack);
}
}
$bus = new MessageBus([new Trace('M1'), new Trace('M2')]);
$bus->dispatch(new Envelope(new stdClass()));
``` | «m1m2» Пояснение: Middleware executes in order: M1 echoes 'M1' then delegates to M2, which echoes 'M2' before reaching the terminal handler.
Raw```json ⏎ {"answer": "M1M2", "explanation": "Middleware executes in order: M1 echoes 'M1' then delegates to M2, which echoes 'M2' before reaching the terminal handler."} ⏎ ``` | верно | The first-added middleware runs first (outermost). |
T16-L10 2.37 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 handlers in the locator for the message class, so both closures execute: $n = 0 + 1 + 10 = 11.
Raw{"answer": 11, "explanation": "HandleMessageMiddleware calls all handlers in the locator for the message class, so both closures execute: $n = 0 + 1 + 10 = 11."} | верно | All registered handlers of the message run: 1 + 10 = 11. |
T17-L9 1.18 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 unique index on column a prevents the second INSERT of value 1, and ON CONFLICT DO NOTHING silently skips it, leaving exactly one row.
Raw{"answer": 1, "explanation": "The unique index on column a prevents the second INSERT of value 1, and ON CONFLICT DO NOTHING silently skips it, leaving exactly one row."} | верно | ON CONFLICT DO NOTHING skips the duplicate: one insert. |
T17-L10 1.68 c | PostgreSQL: transactions and indexes | What does this sequence of psql commands output?
```sql
BEGIN;
CREATE TEMP TABLE t (a int, UNIQUE (a) DEFERRABLE INITIALLY DEFERRED);
INSERT INTO t VALUES (1);
INSERT INTO t VALUES (1);
SELECT count(*) FROM t;
``` | «2» Пояснение: The UNIQUE constraint is DEFERRABLE INITIALLY DEFERRED, so it is not enforced until COMMIT, allowing both duplicate inserts to succeed within the transaction.
Raw{"answer": 2, "explanation": "The UNIQUE constraint is DEFERRABLE INITIALLY DEFERRED, so it is not enforced until COMMIT, allowing both duplicate inserts to succeed within the transaction."} | верно | DEFERRED postpones the uniqueness check to COMMIT — count sees 2 rows. |
T18-L9 1.87 c | Testing: PHPUnit | How many tests will this command run?
```php
use PHPUnit\Framework\TestCase;
use PHPUnit\Framework\Attributes\DataProvider;
final class CalcTest extends TestCase
{
public static function prov(): array
{
return [[1], [2], [3]];
}
#[DataProvider('prov')]
public function test_sum(int $x): void
{
$this->assertTrue($x > 0);
}
#[DataProvider('prov')]
public function test_sum_abs(int $x): void
{
$this->assertTrue($x > 0);
}
public function test_other(): void
{
$this->assertTrue(true);
}
}
```
Command: `phpunit CalcTest.php --filter test_sum` (PHPUnit 10.5) | «6» Пояснение: The --filter test_sum regex matches both test_sum (3 data sets) and test_sum_abs (3 data sets), giving 3 + 3 = 6 tests.
Raw{"answer": 6, "explanation": "The --filter test_sum regex matches both test_sum (3 data sets) and test_sum_abs (3 data sets), giving 3 + 3 = 6 tests."} | верно | --filter is a substring match: test_sum also matches test_sum_abs (3+3 datasets). |
T18-L10 1.21 c | Testing: PHPUnit | How many tests will this command run, and how many of them will fail? Answer with two comma-separated numbers (ran, failed).
```php
use PHPUnit\Framework\TestCase;
use PHPUnit\Framework\Attributes\DataProvider;
final class Calc2Test extends TestCase
{
public function prov(): array
{
return [[1], [-1]];
}
#[DataProvider('prov')]
public function test_x(int $x): void
{
$this->assertTrue($x > 0);
}
}
```
Command: `phpunit Calc2Test.php` (PHPUnit 10.5) | «2, 1» Пояснение: The data provider yields two sets of data ([1] and [-1]), so two tests run; the one with $x = -1 fails because -1 > 0 is false.
Raw```json ⏎ {"answer": "2, 1", "explanation": "The data provider yields two sets of data ([1] and [-1]), so two tests run; the one with $x = -1 fails because -1 > 0 is false."} ⏎ ``` | верно | A non-static provider is just a deprecation in PHPUnit 10: both datasets run and the [-1] dataset fails the assert — 2 ran, 1 failure. |
T19-L9 0.81 c | HTTP and REST API | Which HTTP method does this command send?
```bash
curl -s -d 'a=1' http://demo.local/api
``` | «post» Пояснение: The -d flag in curl sends data in the request body, which automatically sets the HTTP method to POST.
Raw{"answer": "POST", "explanation": "The -d flag in curl sends data in the request body, which automatically sets the HTTP method to POST."} | верно | -d/-F switches curl to POST by default. |
T19-L10 1.14 c | HTTP and REST API | Which HTTP method does this command send?
```bash
curl -s -G -d 'a=1' http://demo.local/api
``` | «get» Пояснение: The -G flag forces curl to use the GET method, appending the -d data as a query string to the URL.
Raw{"answer": "GET", "explanation": "The -G flag forces curl to use the GET method, appending the -d data as a query string to the URL."} | верно | -G turns -d data into the query string; the method stays GET. |
T20-L9 1.3 c | Security and OAuth | A client hits the token endpoint (RFC 6749) with a non-existent client_id. What value of the error field does the endpoint return? | «invalid_client» Пояснение: RFC 6749 Section 5.2 specifies that when the client is not recognized or authentication fails, the token endpoint returns the error value 'invalid_client'.
Raw{"answer": "invalid_client", "explanation": "RFC 6749 Section 5.2 specifies that when the client is not recognized or authentication fails, the token endpoint returns the error value 'invalid_client'."} | верно | Unknown client → invalid_client (RFC 6749 §5.2). |
T20-L10 0.87 c | Security and OAuth | OAuth 2.0: the client started the flow with response_type=token. In which part of the redirect_uri does the authorization server pass the access_token? | «fragment» Пояснение: In the OAuth 2.0 implicit flow (response_type=token), the access token is returned in the URI fragment (the part after #) of the redirect_uri.
Raw{"answer": "fragment", "explanation": "In the OAuth 2.0 implicit flow (response_type=token), the access token is returned in the URI fragment (the part after #) of the redirect_uri."} | верно | The implicit flow passes the token in the URL fragment (#) — it never reaches the server. |
T21-L9 2.07 c | Twig | What does this Twig template output?
```twig
{{ false|default(2) * 3 }}
``` | «0» Пояснение: The default filter only replaces null/undefined values, not false, so false|default(2) remains false (0 in numeric context), and 0 * 3 = 0.
Raw{"answer": 0, "explanation": "The default filter only replaces null/undefined values, not false, so false|default(2) remains false (0 in numeric context), and 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 2.53 c | Twig | What exception class does render() of this template throw?
```twig
{{ 'a' ~ 1 + 2 }}
``` | «a3» Пояснение: In Twig, the + operator has higher precedence than ~, so the expression is parsed as 'a' ~ (1+2), which concatenates 'a' with 3 to produce 'a3'.
Raw{"answer": "a3", "explanation": "In Twig, the + operator has higher precedence than ~, so the expression is parsed as 'a' ~ (1+2), which concatenates 'a' with 3 to produce 'a3'."} | неверно верный: «runtimeerror» | In Twig ~ binds tighter than +: ('a' ~ 1) + 2 → string + int → a render error (RuntimeError). |
T22-L9 2.28 c | Symfony: Security and forms | What does this code output?
```php
use Symfony\Component\Validator\Validation;
use Symfony\Component\Validator\Constraints as Assert;
$v = Validation::createValidator();
echo count($v->validate([''], [new Assert\NotBlank()]));
``` | «0» Пояснение: The NotBlank constraint checks the top-level value; [''] is a non-empty array, so it passes and produces no violations.
Raw{"answer": 0, "explanation": "The NotBlank constraint checks the top-level value; [''] is a non-empty array, so it passes and produces no violations."} | верно | NotBlank treats null, '', [] as blank — the array [''] is not blank. |
T22-L10 5.1 c | Symfony: Security and forms | What does this code output?
```php
use Symfony\Component\Form\Forms;
use Symfony\Component\Form\Extension\Core\Type\TextType;
$factory = Forms::createFormFactoryBuilder()->getFormFactory();
$form = $factory->create(TextType::class);
try {
echo $form->isValid() ? 'valid' : 'invalid';
} catch (Throwable $e) {
echo get_class($e);
}
``` | «valid» Пояснение: Calling isValid() on a non-submitted Symfony form returns true because validate() returns early without adding any errors, so the error count is 0.
Raw```json ⏎ {"answer": "valid", "explanation": "Calling isValid() on a non-submitted Symfony form returns true because validate() returns early without adding any errors, so the error count is 0."} ⏎ ``` | неверно верный: «symfony\component\form\exception\logicexception» | isValid() on a non-submitted form throws LogicException, it does not return false. |
T23-L9 2.22 c | Symfony: configuration and services | What does this code output?
```php
use Symfony\Component\DependencyInjection\ContainerBuilder;
$c = new ContainerBuilder();
$c->register('a', stdClass::class)->setPublic(true);
$c->compile();
echo spl_object_id($c->get('a')) === spl_object_id($c->get('a')) ? 'same' : 'diff';
``` | «same» Пояснение: By default, Symfony DI services are shared (singleton), so calling get() multiple times returns the same instance.
Raw{"answer": "same", "explanation": "By default, Symfony DI services are shared (singleton), so calling get() multiple times returns the same instance."} | верно | Container services are shared: two get() calls yield one instance. |
T23-L10 1.59 c | Symfony: configuration and services | What does this code output?
```php
use Symfony\Component\DependencyInjection\ContainerBuilder;
$c = new ContainerBuilder();
$c->setParameter('name', 'Bob');
$c->setParameter('greeting', 'hi %name%');
$c->setParameter('message', '%greeting%!');
$c->compile();
echo $c->getParameter('message');
``` | «hi bob!» Пояснение: During compile(), Symfony recursively resolves parameter placeholders: %greeting% expands to 'hi %name%', then %name% expands to 'Bob', yielding 'hi Bob!'.
Raw{"answer":"hi Bob!","explanation":"During compile(), Symfony recursively resolves parameter placeholders: %greeting% expands to 'hi %name%', then %name% expands to 'Bob', yielding 'hi Bob!'."} | верно | compile() resolves %-references transitively: %greeting% → 'hi %name%' → 'hi Bob!', the answer assembles over two hops. |
T24-L9 1.19 c | Bootstrap | What is the max-width of .container in Bootstrap 5.3 at a 992px viewport? | «960» Пояснение: In Bootstrap 5.3, at the lg breakpoint (≥992px), the .container max-width is set to 960px.
Raw{"answer": 960, "explanation": "In Bootstrap 5.3, at the lg breakpoint (≥992px), the .container max-width is set to 960px."} | верно | 5.x container widths: 540/720/960/1140/1320 (sm–xxl); 992 → 960px. |
T24-L10 2.67 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, both classes have the same specificity, so the one appearing later in the generated CSS wins; 'danger' comes after 'primary' in the theme-colors map, making .text-danger the last rule applied.
Raw{"answer": "text-danger", "explanation": "In Bootstrap 5.3, both classes have the same specificity, so the one appearing later in the generated CSS wins; 'danger' comes after 'primary' in the theme-colors map, making .text-danger the last rule applied."} | верно | Specificity ties — the later rule wins: text-danger is declared after text-primary. |
T25-L9 1.07 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 both Application and Infrastructure, both of which violate the rule that Domain can only depend on Domain.
Raw```json ⏎ {"answer": 2, "explanation": "The Domain class depends on both Application and Infrastructure, both of which violate the rule that Domain can only depend on Domain."} ⏎ ``` | верно | Domain may depend only on Domain: PlaceOrder (Application) + Db (Infrastructure) = 2. |
T25-L10 1.46 c | Clean architecture | Layers: Domain, Application, Infrastructure. Deptrac rules: Application → Domain; Infrastructure → Domain, Application; Domain → Domain only.
How many violations will deptrac report for this class?
```php
namespace App\Domain;
use App\Application\PlaceOrder;
use App\Infrastructure\Db;
class BillingService
{
public function __construct(
private PlaceOrder $handler,
private Db $db,
private \App\Infrastructure\Logger $logger,
) {}
}
``` | «3» Пояснение: The Domain class depends on Application (PlaceOrder) and Infrastructure (Db, Logger), violating the rule that Domain may only depend on Domain.
Raw```json ⏎ {"answer": 3, "explanation": "The Domain class depends on Application (PlaceOrder) and Infrastructure (Db, Logger), violating the rule that Domain may only depend on Domain."} ⏎ ``` | верно | The inline FQCN \App\Infrastructure\Logger counts too: Application + Db + Logger = 3. |
T26-L10 1.33 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 object with 10+5=15, so the echo outputs '10,15'.
Raw{"answer": "10,15", "explanation": "$a has amount 10, and $c is a new Money object with 10+5=15, so the echo outputs '10,15'."} | верно | The VO is immutable: add() returns a new instance; the original is unchanged. |
T26-L9 1.34 c | DDD | What does this code output?
```php
final class Order
{
private array $items = [];
public function add(string $sku): void
{
$this->items[$sku] = true;
}
public function count(): int
{
return count($this->items);
}
public function remove(string $sku): void
{
if (count($this->items) === 1) {
throw new DomainException('last item');
}
unset($this->items[$sku]);
}
}
$o = new Order;
$o->add('a');
try {
$o->remove('a');
} catch (DomainException) {
}
echo $o->count();
``` | «1» Пояснение: The exception is thrown before unset() executes, so the item remains and count() returns 1.
Raw{"answer": 1, "explanation": "The exception is thrown before unset() executes, so the item remains and count() returns 1."} | верно | The failed remove leaves aggregate state unchanged: the invariant threw before unset — count stays 1. |
VC-L9 0.59 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, calls hi() which returns 'hi', and echoes it.
Raw{"answer": "hi", "explanation": "The code instantiates class C, calls hi() which returns 'hi', and echoes it."} | верно | Since 8.4, new in a method chain works without wrapping parentheses. |
VC-L10 2.25 c | PHP 8.4–8.5 | What does this code output on PHP 8.5?
```php
class Heavy
{
public int $v = 0;
}
$r = new ReflectionClass(Heavy::class);
$o = $r->newLazyGhost(function (Heavy $obj) {
$obj->v = 21;
});
echo $r->isUninitializedLazyObject($o) ? 'yes' : 'no';
$o->v;
echo $r->isUninitializedLazyObject($o) ? 'yes' : 'no';
``` | «yesno» Пояснение: After newLazyGhost the object is an uninitialized lazy object (yes), but after accessing $o->v the initializer fires and the ghost is hydrated, so it is no longer uninitialized (no).
Raw{"answer": "yesno", "explanation": "After newLazyGhost the object is an uninitialized lazy object (yes), but after accessing $o->v the initializer fires and the ghost is hydrated, so it is no longer uninitialized (no)."} | верно | newLazyGhost (8.4): the object stays lazy until first access — reading a property initializes it and clears the flag. |
T28-L9 1.17 c | Symfony: versions | The project was upgraded from Symfony 6.4 to 8.1. What does this code output on 8.1?
```php
echo class_exists(\Symfony\Component\Security\Guard\AbstractGuardAuthenticator::class)
? 'yes' : 'no';
``` | «no» Пояснение: The Symfony Security Guard component (including AbstractGuardAuthenticator) was removed in Symfony 6.0, so the class does not exist in Symfony 8.1.
Raw{"answer": "no", "explanation": "The Symfony Security Guard component (including AbstractGuardAuthenticator) was removed in Symfony 6.0, so the class does not exist in Symfony 8.1."} | верно | Guard authentication was removed in Symfony 7.0 — the class is gone in 8.1. |
T28-L10 1.35 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» Пояснение: AnnotationClassLoader was removed in Symfony 7.0, while AttributeClassLoader exists in 8.1.
Raw{"answer":"noyes","explanation":"AnnotationClassLoader was removed in Symfony 7.0, while AttributeClassLoader exists in 8.1."} | верно | Annotation loaders were removed in 7.0; only attribute loaders remain (Annotation→Attribute). |