Пример запроса (первая клетка). System одинаковый во всех запросах прогона, user — свой вопрос для каждой клетки:
| Клетка | Тема | Утверждение | Ответ |
Результат | Обоснование |
T01-L1 3.25 c | Syntax and operators | Double-quoted and single-quoted strings are processed identically; the difference is only in speed. | «no» Пояснение: Double-quoted strings allow variable interpolation and escape sequences, while single-quoted strings generally do not.
Raw{"answer": "no", "explanation": "Double-quoted strings allow variable interpolation and escape sequences, while single-quoted strings generally do not."} | верно | В двойных кавычках работают интерполяция переменных и escape-последовательности, в одинарных — нет. |
T01-L2 3.65 c | Syntax and operators | The ?? operator follows isset semantics and raises no warnings for undefined variables. | «yes» Пояснение: The ?? operator suppresses notices/warnings for undefined variables and behaves like isset in deciding when to use a default.
Raw{"answer": "yes", "explanation": "The ?? operator suppresses notices/warnings for undefined variables and behaves like isset in deciding when to use a default."} | верно | ?? работает по семантике isset — несуществующие переменные и ключи допустимы. |
T01-L3 0.78 c | Syntax and operators | What will this print: echo 'a', 'b'; | «ab» Пояснение: The echo statement in PHP accepts multiple expressions separated by commas, so it outputs 'a' followed by 'b'.
Raw{"answer": "ab", "explanation": "The echo statement in PHP accepts multiple expressions separated by commas, so it outputs 'a' followed by 'b'."} | верно | echo принимает список аргументов: ab. |
T01-L4 134.82 c | Syntax and operators | print returns the value 1 and can be used inside an expression. | «yes» Пояснение: print outputs its argument and returns 1, so it can be used in an expression, unlike echo.
Raw{"answer": "yes", "explanation": "print outputs its argument and returns 1, so it can be used in an expression, unlike echo."} | верно | print — выражение со значением 1, в отличие от echo, который значения не возвращает. |
T01-L5 1.32 c | Syntax and operators | The ?: (elvis) operator returns its left operand when it is falsy. | «no» Пояснение: The Elvis operator returns its left operand when it is truthy, not when it is falsy.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "The Elvis operator returns its left operand when it is truthy, not when it is falsy." ⏎ } | верно | Наоборот: $a ?: $b возвращает $a, если он истинный, иначе $b. |
T01-L6 3.67 c | Syntax and operators | In PHP 8, the concatenation operator (.) has lower precedence than addition and subtraction. | «yes» Пояснение: In PHP, the string concatenation operator (.) has lower precedence than the arithmetic + and - operators, so expressions like 1 + 2 . 3 are evaluated as (1 + 2) . 3.
Raw{"answer": "yes", "explanation": "In PHP, the string concatenation operator (.) has lower precedence than the arithmetic + and - operators, so expressions like 1 + 2 . 3 are evaluated as (1 + 2) . 3."} | верно | С PHP 8 (RFC concat precedence) '.' имеет приоритет ниже арифметики: 'сумма: ' . 2 + 3 → 'сумма: 5' (в PHP 7 было иначе). |
T01-L7 2.11 c | Syntax and operators | The expression 2 ** 3 ** 2 in PHP evaluates as (2 ** 3) ** 2, that is, 64. | «no» Пояснение: In PHP, the ** operator is right-associative, so 2 ** 3 ** 2 is evaluated as 2 ** (3 ** 2) = 2 ** 9 = 512, not (2 ** 3) ** 2 = 64.
Raw{"answer": "no", "explanation": "In PHP, the ** operator is right-associative, so 2 ** 3 ** 2 is evaluated as 2 ** (3 ** 2) = 2 ** 9 = 512, not (2 ** 3) ** 2 = 64."} | верно | ** право-ассоциативен: 2 ** (3 ** 2) = 2 ** 9 = 512. |
T01-L8 280.19 c | Syntax and operators | What string will this print: echo 'sum: ' . 2 + 3; (PHP 8)? | «— (нет ответа)» | не разобрано верный: «sum: 5» парсинг: нет | Парная к verify-клетке про приоритет: 'сумма: 5'. |
T02-L1 1.54 c | Types and comparisons | With strict comparison (===), arrays are considered equal regardless of element order. | «no» Пояснение: In PHP, === compares arrays with the same order of key/value pairs, not ignoring order.
Raw{"answer":"no","explanation":"In PHP, === compares arrays with the same order of key/value pairs, not ignoring order."} | верно | === для массивов требует совпадения и значений, и их порядка. |
T02-L2 1.87 c | Types and comparisons | The comparison 0 == false returns false because it is a strict comparison. | «no» Пояснение: The statement is false because == is a loose comparison and 0 == false evaluates to true.
Raw{"answer": "no", "explanation": "The statement is false because == is a loose comparison and 0 == false evaluates to true."} | верно | Наоборот: == — нестрогое сравнение и возвращает true; строгое — это === (0 === false → false). |
T02-L3 9.87 c | Types and comparisons | In PHP 8, the expression "abc" == 0 returns true. | «no» Пояснение: In PHP 8, comparing a non-numeric string to a number is done as a string comparison after converting the number to a string, so 'abc' is not equal to '0'.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "In PHP 8, comparing a non-numeric string to a number is done as a string comparison after converting the number to a string, so 'abc' is not equal to '0'." ⏎ } | верно | С PHP 8 нечисловая строка сравнивается как строка: "abc" == "0" → false (в PHP 7 было true). |
T02-L4 8.42 c | Types and comparisons | Under loose comparison, null equals 0, the empty string, and false at the same time. | «no» Пояснение: In modern PHP, null is loosely equal to false/null, but not to 0 or the empty string.
Raw{"answer":"no","explanation":"In modern PHP, null is loosely equal to false/null, but not to 0 or the empty string."} | неверно верный: «yes» | null == 0, null == "" и null == false — все true. |
T02-L5 1.26 c | Types and comparisons | What does the expression (int) '42abc' return? | «42» Пояснение: In PHP, casting a string to int takes the leading numeric value, so '42abc' becomes 42.
Raw{ ⏎ "answer": 42, ⏎ "explanation": "In PHP, casting a string to int takes the leading numeric value, so '42abc' becomes 42." ⏎ } | верно | Ведущая числовая часть: 42, без ошибок и warning. |
T02-L6 0.9 c | Types and comparisons | What does the expression '5' + 5 return? | «10» Пояснение: PHP coerces the numeric string '5' to a number before adding it to 5.
Raw{"answer": 10, "explanation": "PHP coerces the numeric string '5' to a number before adding it to 5."} | верно | Числовая строка приводится: int 10. |
T02-L7 1.21 c | Types and comparisons | When cast to string, false becomes "0". | «no» Пояснение: In PHP, casting false to a string results in an empty string "", not "0".
Raw{ ⏎ "answer": "no", ⏎ "explanation": "In PHP, casting false to a string results in an empty string \"\", not \"0\"." ⏎ } | верно | false → "", true → "1". |
T02-L8 2.04 c | Types and comparisons | The comparison 0.1 + 0.2 === 0.3 returns false. | «yes» Пояснение: In PHP, 0.1 + 0.2 produces a floating-point value slightly different from 0.3, so strict equality === returns false.
Raw{"answer": "yes", "explanation": "In PHP, 0.1 + 0.2 produces a floating-point value slightly different from 0.3, so strict equality === returns false."} | верно | Двоичная погрешность float: 0.1 + 0.2 = 0.30000000000000004. |
T03-L1 1.81 c | Strings | strrev() correctly reverses a UTF-8 string. | «no» Пояснение: strrev() operates byte-by-byte, so it corrupts multi-byte UTF-8 characters; use mb_strrev() instead for correct UTF-8 handling.
Raw{"answer":"no","explanation":"strrev() operates byte-by-byte, so it corrupts multi-byte UTF-8 characters; use mb_strrev() instead for correct UTF-8 handling."} | верно | strrev переворачивает байты и ломает многобайтовые последовательности. |
T03-L2 0.76 c | Strings | str_contains('Hello world', 'world') returns true. | «yes» Пояснение: str_contains performs a case-sensitive substring check, and 'world' appears in 'Hello world'.
Raw{"answer": "yes", "explanation": "str_contains performs a case-sensitive substring check, and 'world' appears in 'Hello world'."} | верно | str_contains с PHP 8.0 проверяет вхождение подстроки. |
T03-L3 1.42 c | Strings | str_pad() can pad a string on the right side only. | «no» Пояснение: PHP's str_pad() can pad on the right, left, or both sides depending on the padding_type argument.
Raw{"answer": "no", "explanation": "PHP's str_pad() can pad on the right, left, or both sides depending on the padding_type argument."} | верно | STR_PAD_LEFT / STR_PAD_BOTH меняют сторону дополнения. |
T03-L4 1.41 c | Strings | By default trim() strips only spaces, leaving tabs and newlines intact. | «no» Пояснение: By default, PHP's trim() strips all whitespace characters, including spaces, tabs, newlines, carriage returns, null bytes, and vertical tabs.
Raw{"answer": "no", "explanation": "By default, PHP's trim() strips all whitespace characters, including spaces, tabs, newlines, carriage returns, null bytes, and vertical tabs."} | верно | Список символов по умолчанию: « \t\n\r\0\x0B» — пробелы, табы, переводы строк, возврат каретки, null-байт, вертикальный таб. Проверено php -r. |
T03-L5 1.32 c | Strings | How many BYTES does strlen('héllo') return for a UTF-8 string? | «6» Пояснение: The character é is encoded as 2 bytes in UTF-8, so 'héllo' contains 6 bytes total.
Raw{"answer": 6, "explanation": "The character é is encoded as 2 bytes in UTF-8, so 'héllo' contains 6 bytes total."} | верно | 6 букв по 2 байта: 12. |
T03-L6 0.76 c | Strings | What does substr('abcdef', -3) return? | «def» Пояснение: Starting at -3 takes the last three characters of the string.
Raw{"answer":"def","explanation":"Starting at -3 takes the last three characters of the string."} | верно | Отрицательное смещение — с конца: def. |
T03-L7 1.28 c | Strings | ucfirst() modifies the string passed to it in place. | «no» Пояснение: PHP strings are passed by value, and ucfirst() returns a modified copy rather than altering the original string.
Raw{"answer":"no","explanation":"PHP strings are passed by value, and ucfirst() returns a modified copy rather than altering the original string."} | верно | Строки неизменяемы; ucfirst возвращает новую строку. |
T03-L8 1.09 c | Strings | Variable interpolation works in heredoc but not in nowdoc. | «yes» Пояснение: Heredoc allows variable interpolation, while nowdoc treats the content as literal and does not interpolate variables.
Raw{"answer": "yes", "explanation": "Heredoc allows variable interpolation, while nowdoc treats the content as literal and does not interpolate variables."} | верно | Nowdoc — «одинарные кавычки» в тройном синтаксисе: текст как есть. |
T04-L1 0.8 c | Arrays | The sort() function preserves the key-to-value association of the array. | «no» Пояснение: sort() sorts by values and reindexes numeric keys, so it does not preserve key-to-value associations.
Raw{"answer": "no", "explanation": "sort() sorts by values and reindexes numeric keys, so it does not preserve key-to-value associations."} | верно | sort перенумеровывает ключи; связь сохраняет asort. |
T04-L2 0.92 c | Arrays | The string key '5' in an array is stored as the integer 5. | «yes» Пояснение: In PHP, array keys that are numeric strings are automatically converted to integers.
Raw{"answer": "yes", "explanation": "In PHP, array keys that are numeric strings are automatically converted to integers."} | верно | Каноничные десятичные строковые ключи приводятся к int. |
T04-L3 1.39 c | Arrays | The in_array() function uses strict comparison (===) by default. | «no» Пояснение: By default in_array() uses non-strict comparison; strict comparison requires the third parameter to be true.
Raw{"answer": "no", "explanation": "By default in_array() uses non-strict comparison; strict comparison requires the third parameter to be true."} | верно | По умолчанию сравнение нестрогое; строгое — третий аргумент true. |
T04-L4 1.18 c | Arrays | Without a callback, array_filter() removes all "empty" (falsy) elements from the array. | «yes» Пояснение: Without a callback, array_filter() removes elements that are falsy, such as 0, "0", "", null, false, and empty arrays.
Raw{"answer": "yes", "explanation": "Without a callback, array_filter() removes elements that are falsy, such as 0, \"0\", \"\", null, false, and empty arrays."} | верно | Убирает 0, "", null, false и пустые массивы. |
T04-L5 1.46 c | Arrays | By default, array_slice() preserves the original numeric keys of the array. | «no» Пояснение: By default, array_slice() reindexes numeric keys; preservation requires preserve_keys to be true.
Raw{"answer": "no", "explanation": "By default, array_slice() reindexes numeric keys; preservation requires preserve_keys to be true."} | верно | По умолчанию ключи перенумеровываются; сохранение — preserve_keys = true. |
T04-L6 2.04 c | Arrays | What does array_slice([10, 20, 30, 40], 1, 2) return? | «[20, 30]» Пояснение: array_slice starts at index 1 (value 20) and extracts 2 elements, yielding [20, 30].
Raw{"answer": "[20, 30]", "explanation": "array_slice starts at index 1 (value 20) and extracts 2 elements, yielding [20, 30]."} | верно | [20,30]; ключи перенумеровываются. |
T04-L7 1.5 c | Arrays | How many elements will count(['a' => 1] + ['a' => 9, 'b' => 2]) return? | «2» Пояснение: The + operator combines the arrays while preserving the left array's keys, resulting in 'a' and 'b'.
Raw{"answer": 2, "explanation": "The + operator combines the arrays while preserving the left array's keys, resulting in 'a' and 'b'."} | верно | Оператор + : по ключу 'a' побеждает левый; итого 2. |
T04-L8 34.12 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.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "PHP 8.1 extended the array spread operator to allow arrays with string keys." ⏎ } | верно | В 8.0 — только числовые ключи; 8.1 снял ограничение. |
T05-L1 72.0 c | Functions and closures | Named arguments cannot be combined with argument unpacking ...$args in a single call. | «yes» Пояснение: PHP does not allow named arguments and the spread/unpacking operator to be mixed in the same function call.
Raw{"answer": "yes", "explanation": "PHP does not allow named arguments and the spread/unpacking operator to be mixed in the same function call."} | неверно верный: «no» | Можно: f(...$args, имя: значение). Нельзя только позиционный аргумент после распаковки. |
T05-L2 1.55 c | Functions and closures | An anonymous function without use sees variables from the outer scope. | «yes» Пояснение: By default, a PHP anonymous function automatically captures variables from the outer scope.
Raw{"answer":"yes","explanation":"By default, a PHP anonymous function automatically captures variables from the outer scope."} | неверно верный: «no» | Без use внешние переменные недоступны; авто-захват только у fn. |
T05-L3 1.56 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, which is 3.
Raw{"answer": 3, "explanation": "func_num_args() returns the number of arguments passed to the function, which is 3."} | верно | Считает переданные аргументы: 3. |
T05-L4 1.5 c | Functions and closures | The body of an arrow function fn may consist of several expressions in curly braces. | «no» Пояснение: PHP arrow functions only allow a single expression after the => arrow, not multiple statements in a block.
Raw{"answer": "no", "explanation": "PHP arrow functions only allow a single expression after the => arrow, not multiple statements in a block."} | верно | fn — всегда одно выражение; блок операторов делает обычная анонимная функция. |
T05-L5 139.93 c | Functions and closures | An arrow function fn captures outer variables by reference (lazily, at use time). | «no» Пояснение: PHP arrow functions capture outer variables by value, not by reference.
Raw{"answer": "no", "explanation": "PHP arrow functions capture outer variables by value, not by reference."} | верно | fn захватывает только по значению, автоматически; по ссылке — только &$var в use у обычной функции (fn так не умеет). |
T05-L6 2.08 c | Functions and closures | A closure declared as static function () {} does not capture $this. | «yes» Пояснение: In PHP, a static closure does not bind to or capture the $this object, so $this is not available inside it.
Raw{"answer": "yes", "explanation": "In PHP, a static closure does not bind to or capture the $this object, so $this is not available inside it."} | верно | static-замыкание отвязано от объекта: $this внутри недоступен. |
T05-L7 1.85 c | Functions and closures | What will this print: $x = 5; $f = function () use ($x) { return $x; }; $x = 7; echo $f(); | «5» Пояснение: The closure captures the variable $x by value at definition time, so it returns the original value 5.
Raw{"answer": 5, "explanation": "The closure captures the variable $x by value at definition time, so it returns the original value 5."} | верно | use захватывает по значению в момент создания: 5. |
T05-L8 3.35 c | Functions and closures | In weak typing mode (without strict_types), passing the string "5" to an int parameter is allowed. | «yes» Пояснение: In weak typing mode, PHP automatically casts the string "5" to the integer 5 when passed to an int parameter.
Raw{"answer":"yes","explanation":"In weak typing mode, PHP automatically casts the string \"5\" to the integer 5 when passed to an int parameter."} | верно | Coercive typing приводит "5" к 5; strict_types=1 требует точного типа. |
T06-L1 1.4 c | OOP: classes and inheritance | PHP supports constructor property promotion: public function __construct(private int $x) {}. | «yes» Пояснение: PHP 8.0 and later support constructor property promotion.
Raw{"answer": "yes", "explanation": "PHP 8.0 and later support constructor property promotion."} | верно | С PHP 8.0 параметр с модификатором создаёт свойство и присваивание. |
T06-L2 0.67 c | OOP: classes and inheritance | Which keyword prevents a method from being overridden in subclasses? | «final» Пояснение: The final keyword marks a method as non-overridable in subclasses.
Raw{"answer": "final", "explanation": "The final keyword marks a method as non-overridable in subclasses."} | верно | final. |
T06-L3 0.84 c | OOP: classes and inheritance | A method declared final cannot be overridden in a subclass. | «yes» Пояснение: A final method cannot be overridden in a subclass.
Raw{"answer": "yes", "explanation": "A final method cannot be overridden in a subclass."} | верно | final запрещает переопределение метода и наследование класса. |
T06-L4 0.84 c | OOP: classes and inheritance | Parent properties with private visibility are accessible in a subclass. | «no» Пояснение: In PHP, private properties are not accessible from a subclass.
Raw{"answer":"no","explanation":"In PHP, private properties are not accessible from a subclass."} | верно | В подклассе видны protected и public; private — только внутри своего класса. |
T06-L5 79.23 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). | «anonymousclass» Пояснение: PHP's get_class() returns the class name of an anonymous class, which is AnonymousClass.
Raw{"answer":"AnonymousClass","explanation":"PHP's get_class() returns the class name of an anonymous class, which is AnonymousClass."} | неверно верный: «class@anonymous» | get_class анонимного класса печатает class@anonymous\0<файл>:<строка>$n; короткая форма — часть до NUL-байта. Проверено php -r (hex). |
T06-L6 2.04 c | OOP: classes and inheritance | A private parent method is not part of the inheritance contract: a child may declare a method with the same name and any visibility. | «yes» Пояснение: Private parent methods are hidden from child classes, so a child can declare a separately defined method with the same name and any visibility.
Raw{"answer":"yes","explanation":"Private parent methods are hidden from child classes, so a child can declare a separately defined method with the same name and any visibility."} | верно | private-члены не наследуются — правила совместимости подписей не действуют. |
T06-L7 4.33 c | OOP: classes and inheritance | The magic method __get() is called only for non-existent properties. | «no» Пояснение: __get() is also called for inaccessible properties, such as protected or private ones, not only nonexistent properties.
Raw{"answer":"false","explanation":"__get() is also called for inaccessible properties, such as protected or private ones, not only nonexistent properties."} | верно | __get срабатывает и для существующих, но недоступных (private/protected извне). |
T06-L8 1.64 c | OOP: classes and inheritance | What does reassigning a readonly property throw — Exception or Error? | «error» Пояснение: In PHP, reassigning a readonly property after it has been set throws an Error (specifically a TypeError).
Raw{"answer":"Error","explanation":"In PHP, reassigning a readonly property after it has been set throws an Error (specifically a TypeError)."} | верно | Error (readonly с 8.1); оговорка: в __clone() переинициализация допустима (8.3+). |
T07-L1 0.8 c | Interfaces, traits, enum | An interface can declare constants. | «yes» Пояснение: PHP interfaces can declare public constants.
Raw{"answer": "yes", "explanation": "PHP interfaces can declare public constants."} | верно | Константы интерфейса наследуются реализациями. |
T07-L2 0.81 c | Interfaces, traits, enum | Which operator checks whether an object is an instance of a class or interface? | «instanceof» Пояснение: The instanceof operator checks whether an object is an instance of a class or interface.
Raw{"answer": "instanceof", "explanation": "The instanceof operator checks whether an object is an instance of a class or interface."} | верно | instanceof. |
T07-L3 86.23 c | Interfaces, traits, enum | An interface can declare static methods. | «yes» Пояснение: An interface can declare static abstract methods, and implementing classes must implement them as static.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "An interface can declare static abstract methods, and implementing classes must implement them as static." ⏎ } | верно | Реализация обязана дать статический метод с той же сигнатурой. |
T07-L4 1.7 c | Interfaces, traits, enum | The instanceof operator only checks class inheritance: it ignores interfaces. | «no» Пояснение: The instanceof operator returns true if the object is a subclass of the specified class or implements the specified interface.
Raw{"answer": "no", "explanation": "The instanceof operator returns true if the object is a subclass of the specified class or implements the specified interface."} | верно | instanceof возвращает true и для интерфейсов объекта. |
T07-L5 1.01 c | Interfaces, traits, enum | An interface method may have a default implementation, like a trait method. | «no» Пояснение: PHP interfaces only declare method signatures and cannot include method bodies, while traits can provide default implementations.
Raw{"answer": "no", "explanation": "PHP interfaces only declare method signatures and cannot include method bodies, while traits can provide default implementations."} | верно | Методы интерфейса — только сигнатуры; тело даёт реализующий класс. |
T07-L6 0.5 c | Interfaces, traits, enum | An abstract method in an abstract class may have protected visibility. | «yes» Пояснение: In PHP, abstract methods can be public, protected, or private.
Raw{"answer": "yes", "explanation": "In PHP, abstract methods can be public, protected, or private."} | верно | В абстрактном классе — любая видимость; в интерфейсе — только public. |
T07-L7 1.36 c | Interfaces, traits, enum | How many elements will Foo::cases() return for enum Foo { case A; case B; case C; }? | «3» Пояснение: Foo::cases() returns one element for each enum case, and there are three cases.
Raw{"answer": 3, "explanation": "Foo::cases() returns one element for each enum case, and there are three cases."} | верно | Статический метод cases(): 3. |
T07-L8 0.84 c | Interfaces, traits, enum | A trait can declare constants. | «yes» Пояснение: In PHP, traits can declare constants.
Raw{"answer": "yes", "explanation": "In PHP, traits can declare constants."} | верно | С PHP 8.2 трейты могут объявлять константы (RFC constants_in_traits); до 8.2 — нет. |
T08-L1 1.13 c | Exceptions and errors | The Throwable interface is a common ancestor of both Exception and Error. | «yes» Пояснение: In PHP 7+, both Exception and Error are subtypes of the Throwable interface.
Raw{"answer":"yes","explanation":"In PHP 7+, both Exception and Error are subtypes of the Throwable interface."} | верно | Иерархия с PHP 7: Throwable → Exception и Throwable → Error. |
T08-L2 1.6 c | Exceptions and errors | A catch (Exception $e) block will also catch TypeError, because TypeError ultimately inherits from Exception. | «yes» Пояснение: In PHP, TypeError extends LogicException, which extends Exception, so catching Exception catches TypeError as well.
Raw{"answer": "yes", "explanation": "In PHP, TypeError extends LogicException, which extends Exception, so catching Exception catches TypeError as well."} | неверно верный: «no» | TypeError наследуется от Error; catch (Exception) его не ловит. |
T08-L3 0.96 c | Exceptions and errors | The @ operator suppresses exceptions too. | «no» Пояснение: The @ operator only silences certain PHP error notices/warnings/errors, not exceptions.
Raw{"answer": "no", "explanation": "The @ operator only silences certain PHP error notices/warnings/errors, not exceptions."} | верно | @ глушит диагностику (warnings/notices), исключения не перехватывает. |
T08-L4 1.1 c | Exceptions and errors | What error class does intdiv(5, 0) throw? | «divisionbyzeroerror» Пояснение: intdiv(5, 0) throws a DivisionByZeroError when the divisor is zero.
Raw{"answer": "DivisionByZeroError", "explanation": "intdiv(5, 0) throws a DivisionByZeroError when the divisor is zero."} | верно | DivisionByZeroError (иерархия Error, не Exception); php-грейдер объективен. |
T08-L5 2.3 c | Exceptions and errors | The finally block runs only if the exception was caught by a catch block. | «no» Пояснение: In PHP, a finally block executes regardless of whether an exception is thrown and caught, or not caught at all, unless execution terminates abruptly.
Raw{"answer":"no","explanation":"In PHP, a finally block executes regardless of whether an exception is thrown and caught, or not caught at all, unless execution terminates abruptly."} | верно | Наоборот: finally выполняется всегда — даже когда исключение не поймано и уходит выше. Проверено php -r. |
T08-L6 4.07 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 propagates and can override or change the result of the try/catch flow.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "An exception thrown in a finally block propagates and can override or change the result of the try/catch flow." ⏎ } | верно | Исключение из finally перекрывает исходное и уходит вместо него. |
T08-L7 20.15 c | Exceptions and errors | What does the expression (bool) new Exception('x') return? | «yes» Пояснение: In PHP, casting any object to boolean is considered true.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "In PHP, casting any object to boolean is considered true." ⏎ } | верно | Любой объект при приведении к bool — true. Формы ответа: true или да. |
T08-L8 1.95 c | Exceptions and errors | Functions registered via register_shutdown_function() run when exit is called. | «yes» Пояснение: PHP calls registered shutdown functions when the script terminates, including via exit().
Raw{"answer": "yes", "explanation": "PHP calls registered shutdown functions when the script terminates, including via exit()."} | верно | exit завершает скрипт, но shutdown-функции отрабатывают. |
T09-L1 1.11 c | Namespaces and autoloading | The use App\Service\Mailer; statement itself loads the class file. | «no» Пояснение: A PHP use statement only creates an alias and does not automatically load the class file.
Raw{"answer": "no", "explanation": "A PHP use statement only creates an alias and does not automatically load the class file."} | верно | use — псевдоним на этапе компиляции; файл грузит автозагрузчик при первом обращении. |
T09-L2 3.21 c | Namespaces and autoloading | What follows use to import a function (not a class): the word function or const? | «function» Пояснение: In PHP, you import a function with the `use function` statement.
Raw{"answer":"function","explanation":"In PHP, you import a function with the `use function` statement."} | верно | use function ...; (и use const для констант). |
T09-L3 1.88 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» Пояснение: The namespace App\ maps to src/, so removing App\ leaves Controller\Api\UserController, which becomes the relative file path.
Raw{ ⏎ "answer": "Controller/Api/UserController.php", ⏎ "explanation": "The namespace App\\ maps to src/, so removing App\\ leaves Controller\\Api\\UserController, which becomes the relative file path." ⏎ } | верно | Остаток имени после префикса, \ → /. |
T09-L4 0.86 c | Namespaces and autoloading | Including vendor/autoload.php registers autoloaders via spl_autoload_register(). | «yes» Пояснение: Including vendor/autoload.php loads Composer's autoloader, which calls spl_autoload_register() to register the autoloaders.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Including vendor/autoload.php loads Composer's autoloader, which calls spl_autoload_register() to register the autoloaders." ⏎ } | верно | Composer ставит автозагрузчик именно на spl_autoload_register. |
T09-L5 1.09 c | Namespaces and autoloading | The magic constant __NAMESPACE__ contains the name of the current namespace. | «yes» Пояснение: The magic constant __NAMESPACE__ returns the name of the namespace in which it is used, or null if no namespace is defined.
Raw{"answer":"yes","explanation":"The magic constant __NAMESPACE__ returns the name of the namespace in which it is used, or null if no namespace is defined."} | верно | В корневом пространстве — пустая строка. |
T09-L6 5.4 c | Namespaces and autoloading | An unqualified class name (without a leading \) in new is resolved from the global root. | «no» Пояснение: Unqualified class names are resolved in the current namespace first, then fall back to the global namespace.
Raw{"answer":"no","explanation":"Unqualified class names are resolved in the current namespace first, then fall back to the global namespace."} | верно | Резолвится относительно текущего namespace (с учётом импортов). |
T09-L7 1.11 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 each namespace segment to a directory under the configured source path, so App\Model\User maps to src/Model/User.php.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "PSR-4 maps each namespace segment to a directory under the configured source path, so App\\Model\\User maps to src/Model/User.php." ⏎ } | верно | Остаток имени после префикса переносится в путь как есть. |
T09-L8 32.4 c | Namespaces and autoloading | A use statement may be written inside a function body — the import then applies to that function only. | «yes» Пояснение: A PHP use statement can be placed inside a function body, in which case the import is scoped only to that function.
Raw{"answer":"yes","explanation":"A PHP use statement can be placed inside a function body, in which case the import is scoped only to that function."} | неверно верный: «no» | use внутри тела функции — parse error; импорты файловые и компиляционные. |
T10-L1 0.84 c | References and scope | Arrays are copied on assignment rather than passed by reference. | «yes» Пояснение: In PHP, assigning an array creates a copy of the array by value.
Raw{"answer": "yes", "explanation": "In PHP, assigning an array creates a copy of the array by value."} | верно | Присваивание массива — копия (в движке — copy-on-write). |
T10-L2 1.18 c | References and scope | What will this print: $a = [1, 2]; $b = $a; $b[] = 3; echo count($a); | «2» Пояснение: Arrays in PHP are copied by value when assigned, so modifying $b does not change $a.
Raw{"answer": 2, "explanation": "Arrays in PHP are copied by value when assigned, so modifying $b does not change $a."} | верно | Присваивание — копия: в $a по-прежнему 2 элемента. |
T10-L3 2.55 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 directly accessible inside a function by name; you must use the global keyword, the $GLOBALS superglobal array, or pass the variable as a parameter to access it.
Raw{"answer": "yes", "explanation": "In PHP, variables in the global scope are not directly accessible inside a function by name; you must use the global keyword, the $GLOBALS superglobal array, or pass the variable as a parameter to access it."} | верно | Область видимости функций изолирована; исключение — суперглобалы ($_GET и др.). |
T10-L4 1.57 c | References and scope | unset($GLOBALS['x']) inside a function removes the global variable only for that function. | «no» Пояснение: unset($GLOBALS['x']) removes the variable from the global scope entirely, so it is no longer available after the function returns.
Raw{"answer":"no","explanation":"unset($GLOBALS['x']) removes the variable from the global scope entirely, so it is no longer available after the function returns."} | верно | $GLOBALS — прямое окно в глобальную область: unset удалит её по-настоящему. |
T10-L5 1.46 c | References and scope | What will this print: function inc(&$x) { $x++; } $n = 5; inc($n); echo $n; | «6» Пояснение: The parameter is passed by reference, so $n is incremented from 5 to 6.
Raw{ ⏎ "answer": 6, ⏎ "explanation": "The parameter is passed by reference, so $n is incremented from 5 to 6." ⏎ } | верно | Ссылка меняет оригинал: 6. |
T10-L6 8.23 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 iterates over a snapshot of the array at the start of the loop, so modifications to the array (adding, removing, or changing elements) inside the loop are not reflected during the same pass.
Raw{"answer": "no", "explanation": "PHP's foreach iterates over a snapshot of the array at the start of the loop, so modifications to the array (adding, removing, or changing elements) inside the loop are not reflected during the same pass."} | верно | По значению foreach итерирует копию-снимок. |
T10-L7 1.23 c | References and scope | A static property belongs to each instance separately: changes in one object are not visible in others. | «no» Пояснение: Static properties belong to the class and are shared among all instances, so changes in one object ARE visible in others.
Raw{"answer": "no", "explanation": "Static properties belong to the class and are shared among all instances, so changes in one object ARE visible in others."} | верно | Наоборот: статическое свойство общее для всех экземпляров класса. Проверено php -r. |
T10-L8 2.47 c | References and scope | An array can have a boolean key true, and it will be stored as bool. | «no» Пояснение: PHP converts boolean array keys to integers, so a true key is stored as 1.
Raw{"answer":"no","explanation":"PHP converts boolean array keys to integers, so a true key is stored as 1."} | верно | Булев ключ приводится к int: true → 1, false → 0. |
T11-L1 2.16 c | Generators, iterators, SPL | Inside a generator, return with a value can be used, and it becomes available via $gen->getReturn(). | «yes» Пояснение: In PHP generators, returning a value terminates the generator and that value can be accessed with getReturn().
Raw{"answer": "yes", "explanation": "In PHP generators, returning a value terminates the generator and that value can be accessed with getReturn()."} | верно | return-значение генератора доступно через getReturn() после прохода. |
T11-L2 2.84 c | Generators, iterators, SPL | A fully consumed generator can be rewound with rewind() and traversed again. | «no» Пояснение: Once a PHP generator has been fully exhausted, it cannot be rewound and traversed again.
Raw{"answer":"no","explanation":"Once a PHP generator has been fully exhausted, it cannot be rewound and traversed again."} | верно | Генератор одноразовый: rewind после начала итерации бросает Exception. |
T11-L3 2.24 c | Generators, iterators, SPL | The yield from construct delegates traversal to another generator or iterable. | «yes» Пояснение: yield from in PHP delegates to another generator or iterable, yielding all of its values as if they were produced by the current generator.
Raw{"answer": "yes", "explanation": "yield from in PHP delegates to another generator or iterable, yielding all of its values as if they were produced by the current generator."} | верно | yield from проксирует значения, ключи и return-значение внутреннего генератора. |
T11-L4 1.89 c | Generators, iterators, SPL | What does get_class(g()) return for function g() { yield 1; }? | «generator» Пояснение: Calling a generator function in PHP returns a Generator object.
Raw{"answer": "Generator", "explanation": "Calling a generator function in PHP returns a Generator object."} | верно | Функция с yield возвращает Generator. |
T11-L5 3.93 c | Generators, iterators, SPL | How many elements will count(iterator_to_array((function () { yield from [1, 2, 3]; })())) return? | «3» Пояснение: The closure is a generator that yields the three elements from the array, so the converted array has three elements.
Raw{"answer": 3, "explanation": "The closure is a generator that yields the three elements from the array, so the converted array has three elements."} | верно | yield from делегирует все 3 элемента. |
T11-L6 1.32 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; PHP uses SplQueue for a FIFO queue.
Raw{"answer": "no", "explanation": "SplStack implements a LIFO (Last-In, First-Out) stack, not a FIFO queue; PHP uses SplQueue for a FIFO queue."} | верно | SplStack — стек LIFO; очередь FIFO — SplQueue. |
T11-L7 1.67 c | Generators, iterators, SPL | ArrayIterator allows wrapping an array and traversing it via the Iterator interface. | «yes» Пояснение: ArrayIterator is PHP's built-in iterator class for arrays and implements the Iterator interface.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "ArrayIterator is PHP's built-in iterator class for arrays and implements the Iterator interface." ⏎ } | верно | Объектная обёртка над массивом. |
T11-L8 0.95 c | Generators, iterators, SPL | An ArrayObject instance cannot be traversed with foreach. | «no» Пояснение: ArrayObject implements the Traversable interface, making it directly iterable with foreach.
Raw{"answer": "no", "explanation": "ArrayObject implements the Traversable interface, making it directly iterable with foreach."} | верно | ArrayObject реализует IteratorAggregate — foreach по нему работает. |
T12-L1 0.85 c | Configuration and security | password_hash() generates a salt automatically — passing one separately is not needed. | «yes» Пояснение: password_hash() automatically generates and stores the salt with the hash, so you should not supply a separate salt.
Raw{"answer": "yes", "explanation": "password_hash() automatically generates and stores the salt with the hash, so you should not supply a separate salt."} | верно | Соль встраивается в строку результата; параметр salt устарел. |
T12-L2 2.56 c | Configuration and security | In PHP 8, PASSWORD_DEFAULT is md5 with an automatically added salt. | «no» Пояснение: PASSWORD_DEFAULT selects the default password hashing algorithm, such as bcrypt, not MD5.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "PASSWORD_DEFAULT selects the default password hashing algorithm, such as bcrypt, not MD5." ⏎ } | верно | PASSWORD_DEFAULT — bcrypt; md5 для паролей непригоден (перебирается массово). |
T12-L3 2.69 c | Configuration and security | What does password_verify('secret', password_hash('secret', PASSWORD_DEFAULT)) return? | «yes» Пояснение: password_verify() returns true when the supplied password matches the generated hash.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "password_verify() returns true when the supplied password matches the generated hash." ⏎ } | верно | Соль и хеш в одной строке: true (форма ответа: true или да). |
T12-L4 1.11 c | Configuration and security | strip_tags() protects against SQL injection. | «no» Пояснение: strip_tags() removes HTML/XML tags and is related to preventing XSS, not SQL injection.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "strip_tags() removes HTML/XML tags and is related to preventing XSS, not SQL injection." ⏎ } | верно | strip_tags режет HTML-теги (помощник против XSS), к параметризации SQL отношения не имеет. |
T12-L5 0.73 c | Configuration and security | session_regenerate_id() is used to protect against session fixation upon user login. | «yes» Пояснение: session_regenerate_id() regenerates the session ID, which helps prevent session fixation attacks, especially on login.
Raw{"answer": "yes", "explanation": "session_regenerate_id() regenerates the session ID, which helps prevent session fixation attacks, especially on login."} | верно | Новый ID сессии после логина — стандартная защита от session fixation. |
T12-L6 0.76 c | Configuration and security | Which built-in function returns the SAPI name (e.g., cli)? | «php_sapi_name» Пояснение: It returns the name of the SAPI in use, such as cli or cli-server.
Raw{"answer":"php_sapi_name","explanation":"It returns the name of the SAPI in use, such as cli or cli-server."} | верно | php_sapi_name(). |
T12-L7 1.4 c | Configuration and security | session_destroy() deletes session data on the server but not the cookie in the user's browser. | «yes» Пояснение: session_destroy() removes the session data from the server but does not delete the session cookie from the browser.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "session_destroy() removes the session data from the server but does not delete the session cookie from the browser." ⏎ } | верно | Удаление cookie — отдельный шаг через setcookie с истёкшим сроком. |
T12-L8 1.17 c | Configuration and security | Without calling session_start(), the $_SESSION array is automatically populated with session data. | «no» Пояснение: The $_SESSION superglobal is only available and populated after session_start() is called (or after a session is otherwise initiated); without it, $_SESSION is undefined.
Raw{"answer": "no", "explanation": "The $_SESSION superglobal is only available and populated after session_start() is called (or after a session is otherwise initiated); without it, $_SESSION is undefined."} | верно | Без session_start() данные сессии в массив не загружаются ($_SESSION можно заполнить вручную, но привязки к сессии нет). |
VC-L1 2.63 c | PHP 8.4–8.5 | In which PHP version was the array_find() function introduced? | «no» Пояснение: PHP does not have an array_find() function in any version; it uses array_search() instead.
Raw{"answer": "no", "explanation": "PHP does not have an array_find() function in any version; it uses array_search() instead."} | неверно верный: «8.4» | PHP 8.4 (RFC array_find). |
VC-L2 2.48 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 hooks to be declared directly in the property declaration.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "PHP 8.4 introduced property hooks, allowing get/set hooks to be declared directly in the property declaration." ⏎ } | верно | Property hooks — PHP 8.4 (ноябрь 2024). |
VC-L3 1.88 c | PHP 8.4–8.5 | Asymmetric visibility (public private(set) string $name) appeared in PHP 8.4. | «yes» Пояснение: PHP 8.4 introduced asymmetric property visibility, allowing syntax like public private(set) string $name;
Raw{"answer":"yes","explanation":"PHP 8.4 introduced asymmetric property visibility, allowing syntax like public private(set) string $name;"} | верно | Asymmetric visibility v2 — PHP 8.4. |
VC-L4 1.55 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 mark expressions whose return values must not be discarded.
Raw{"answer":"8.4","explanation":"The #[NoDiscard] attribute was introduced in PHP 8.4 to mark expressions whose return values must not be discarded."} | неверно верный: «8.5» | #[\NoDiscard] — PHP 8.5 (marking return values as important). |
VC-L5 3.4 c | PHP 8.4–8.5 | In which PHP version did the pipe operator |> first appear? Answer with the version number. | «no» Пояснение: PHP does not have a pipe operator (|>) in any released version; the premise is false.
Raw{"answer": "no", "explanation": "PHP does not have a pipe operator (|>) in any released version; the premise is false."} | неверно верный: «8.5» | Pipe operator — PHP 8.5 (2025). |
VC-L6 30.76 c | PHP 8.4–8.5 | In which PHP version did clone-with — the syntax clone($obj, ['x' => 1]) — appear? Answer with the version number. | «8.4» Пояснение: Clone-with appeared in PHP 8.4.
Raw{"answer": 8.4, "explanation": "Clone-with appeared in PHP 8.4."} | неверно верный: «8.5» | Clone with v2 — PHP 8.5. |
VC-L7 113.99 c | PHP 8.4–8.5 | In which PHP version were the array_first() and array_last() functions introduced? | «8.5» Пояснение: array_first() and array_last() were introduced in PHP 8.5.
Raw{"answer": 8.5, "explanation": "array_first() and array_last() were introduced in PHP 8.5."} | верно | PHP 8.5. |
VC-L8 87.24 c | PHP 8.4–8.5 | For which PHP version was RFC Partial Function Application v2 adopted (as of 2026-11-07)? Answer with the version number. | «8.4» Пояснение: RFC Partial Function Application v2 was adopted for PHP 8.4.
Raw{"answer":"8.4","explanation":"RFC Partial Function Application v2 was adopted for PHP 8.4."} | неверно верный: «8.6» | PFA v2 принят 05.12.2025 (33-0-0), реализован в PHP 8.6. |
VF-L1 62.71 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_v2 RFC shipped with the PHP 8.4 release.
Raw{"answer": "8.4", "explanation": "The clamp_v2 RFC shipped with the PHP 8.4 release."} | неверно верный: «8.6» | По данным владельца (wiki.php.net/rfc): clamp_v2 — 8.6; clamp() в 8.5.11 отсутствует (косвенное подтверждение). Дата-якорь делает клетку монотонной. |
VF-L2 71.38 c | PHP: 8.6+ and the future | RFC Context Managers v2 has already been adopted in PHP (as of 2026-11-07). | «yes» Пояснение: The Context Managers v2 RFC is in an accepted/adopted status.
Raw{"answer": "yes", "explanation": "The Context Managers v2 RFC is in an accepted/adopted status."} | неверно верный: «no» | На 06.11.2026 — в обсуждении (создан 2026-10-23); не принят. |
VF-L3 101.53 c | PHP: 8.6+ and the future | RFC Bound-Erased Generic Types (generics) was declined in 2026. | «no» Пояснение: The RFC was not declined in 2026.
Raw{"answer": "no", "explanation": "The RFC was not declined in 2026."} | неверно верный: «yes» | Голосование завершилось 2026-06-28: отклонён (wiki.php.net/rfc). |
VF-L4 91.13 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. | «yes» Пояснение: The ZTS-by-default RFC was accepted for PHP 8.4.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "The ZTS-by-default RFC was accepted for PHP 8.4." ⏎ } | неверно верный: «no» | Такого принятого RFC нет на дату якоря; якорь делает клетку монотонной — при принятии RFC позже клетка не перевернётся. |
VF-L5 2.67 c | PHP: 8.6+ and the future | As of PHP 8.5, generics (parameterized types) are still absent. | «yes» Пояснение: PHP has never implemented generics/parameterized types; none were added in PHP 8.5 either.
Raw{"answer": "yes", "explanation": "PHP has never implemented generics/parameterized types; none were added in PHP 8.5 either."} | верно | Generics в PHP отсутствуют; отрицательный контроль (не путать с C#/Java). |
VF-L6 4.24 c | PHP: 8.6+ and the future | As of 2026-11-07, the latest stable PHP version is 8.5, and PHP 8.6 has not been released yet (GA — 2026-11-19). | «yes» Пояснение: As of 2026-11-07, PHP 8.5 is the latest stable release and PHP 8.6 is not yet generally available.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "As of 2026-11-07, PHP 8.5 is the latest stable release and PHP 8.6 is not yet generally available." ⏎ } | верно | 8.5 — релиз осени 2025; 8.6 GA 19.11.2026 (wiki.php.net/todo/php86). Дата снимка — 06.11.2026. |
VF-L7 3.65 c | PHP: 8.6+ and the future | The PHP 6 branch never shipped: after PHP 5.6 came PHP 7.0 directly. | «yes» Пояснение: PHP 6 was never released as a stable version; PHP 5.6 was followed by PHP 7.0.
Raw{"answer":"yes","explanation":"PHP 6 was never released as a stable version; PHP 5.6 was followed by PHP 7.0."} | верно | Исторический факт: ветка 6 не была релизнута. |
VF-L8 9.53 c | PHP: 8.6+ and the future | The RFC adding the #[\Deprecated] attribute to the core was adopted. | «yes» Пояснение: The RFC to add the #[\Deprecated] attribute to the PHP core was adopted.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "The RFC to add the #[\\Deprecated] attribute to the PHP core was adopted." ⏎ } | верно | #[\Deprecated] — принят, реализован в PHP 8.4. |
T25-L1 1.07 c | Clean architecture | The dependency rule of clean and onion architecture: inner layers know nothing about outer ones — dependencies point toward the center. | «yes» Пояснение: Clean and onion architectures require dependencies to point inward, so inner layers must not know about or depend on outer layers.
Raw{"answer":"yes","explanation":"Clean and onion architectures require dependencies to point inward, so inner layers must not know about or depend on outer layers."} | верно | Чистая (Robert C. Martin), луковичная (Jeffrey Palermo) и гексагональная (ports & adapters) — варианты одной идеи: зависимости направлены внутрь, к домену. Слоями в проекте следит deptrac. |
T25-L2 1.27 c | Clean architecture | Domain entities import neither Doctrine nor Symfony — only the language and, possibly, the standard library. | «yes» Пояснение: Domain entities should remain framework-agnostic and depend only on core language features and, at most, the standard library.
Raw{"answer":"yes","explanation":"Domain entities should remain framework-agnostic and depend only on core language features and, at most, the standard library."} | верно | Изоляция домена от инфраструктуры; deptrac в проекте как раз следит за слоями. |
T25-L3 0.99 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 are presentation-layer components that call use cases, not business-logic components.
Raw{"answer": "no", "explanation": "Controllers and Twig templates are presentation-layer components that call use cases, not business-logic components."} | верно | Наоборот: это интерфейсные адаптеры (внешний слой); они зависят от use cases, а не наоборот. |
T25-L4 1.62 c | Clean architecture | What sits at the very center of the onion architecture? | «core business logic» Пояснение: In onion architecture, the innermost layer contains the core business rules and domain logic.
Raw{"answer": "core business logic", "explanation": "In onion architecture, the innermost layer contains the core business rules and domain logic."} | неверно верный: «domain model» | Центральное кольцо — Domain Model: сущности и бизнес-правила без зависимостей; далее Domain Services → Application Services → Infrastructure/UI/Tests (Palermo). |
T25-L5 1.01 c | Clean architecture | Layer boundary violations can be caught automatically: a layer-dependency analyzer (e.g. deptrac) fails on a forbidden call. | «yes» Пояснение: A layer-dependency analyzer can statically detect and report forbidden cross-layer calls, causing the analysis to fail.
Raw{"answer":"yes","explanation":"A layer-dependency analyzer can statically detect and report forbidden cross-layer calls, causing the analysis to fail."} | верно | depfile.yaml в проекте TasK: CI проверяет правила слоёв на каждом пайплайне. |
T25-L6 4.3 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 should not depend on framework-specific inputs like HTTP requests or an EntityManager; they should receive domain objects or repository interfaces instead.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "Use cases should not depend on framework-specific inputs like HTTP requests or an EntityManager; they should receive domain objects or repository interfaces instead." ⏎ } | верно | Use case принимает DTO и порты; привязка к HTTP/ORM протекает инфраструктуру во внутренние слои. |
T25-L7 1.14 c | Clean architecture | What is the component called that provides a collection of aggregates/entities while hiding the storage mechanism behind an interface? | «repository» Пояснение: A Repository provides a collection of entities or aggregates while abstracting away the underlying storage mechanism.
Raw{"answer": "Repository", "explanation": "A Repository provides a collection of entities or aggregates while abstracting away the underlying storage mechanism."} | верно | Repository pattern (DDD/Evans); в проекте — Doctrine-репозитории за портами. |
T25-L8 1.67 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, database access is an outer infrastructure concern behind interfaces, so domain and use cases can remain unchanged when swapping databases.
Raw{"answer":"yes","explanation":"In clean architecture, database access is an outer infrastructure concern behind interfaces, so domain and use cases can remain unchanged when swapping databases."} | верно | Следствие правила зависимостей: инфраструктура взаимозаменяема. |
T26-L1 1.75 c | DDD | In DDD, an aggregate is just another name for a database table. | «no» Пояснение: In DDD, an aggregate is a domain modeling concept representing a cluster of entities and value objects with a shared identity and consistency boundary, not a synonym for a database table.
Raw{"answer": "no", "explanation": "In DDD, an aggregate is a domain modeling concept representing a cluster of entities and value objects with a shared identity and consistency boundary, not a synonym for a database table."} | верно | Агрегат — кластер объектов с границей согласованности (транзакционной вокруг корня); таблица — деталь хранения. |
T26-L2 0.48 c | DDD | A Value Object is immutable and compared by the values of its fields, not by identity. | «yes» Пояснение: Value objects are defined by their attributes, are immutable, and equality is determined by field values rather than identity.
Raw{"answer": "yes", "explanation": "Value objects are defined by their attributes, are immutable, and equality is determined by field values rather than identity."} | верно | Классика Evans: Money, Email; равенство структурное. |
T26-L3 0.83 c | DDD | What is the single external entry point of an aggregate, through which all changes must go, called? | «aggregate root» Пояснение: In DDD, the aggregate root is the single external entry point for all changes to an aggregate.
Raw{"answer": "aggregate root", "explanation": "In DDD, the aggregate root is the single external entry point for all changes to an aggregate."} | верно | Aggregate Root: внешние объекты ссылаются только на корень; он защищает инварианты агрегата. |
T26-L4 1.79 c | DDD | In DDD, a repository is declared for an aggregate (its root), not for every entity. | «yes» Пояснение: Repositories are used to persist aggregate roots as complete aggregates, preserving invariants and identity.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Repositories are used to persist aggregate roots as complete aggregates, preserving invariants and identity." ⏎ } | верно | Репозиторий корня хранит границу согласованности агрегата; вложенные сущности доступны только через корень. |
T26-L5 1.19 c | DDD | Ubiquitous language is the model's shared language common to developers and domain experts. | «yes» Пояснение: In DDD, the Ubiquitous Language is the shared vocabulary used across all teams and artifacts to represent the domain, bridging developers and domain experts.
Raw{"answer": "yes", "explanation": "In DDD, the Ubiquitous Language is the shared vocabulary used across all teams and artifacts to represent the domain, bridging developers and domain experts."} | верно | Evans: язык из требований переходит в имена классов и методов. |
T26-L6 29.85 c | DDD | What is the boundary called within which a model and its language are consistent, while outside the same words mean other models? | «domain» Пояснение: In a model, the domain (or universe of discourse) is the boundary where its language is consistently interpreted, while outside it the same words may be interpreted in other models.
Raw{ ⏎ "answer": "domain", ⏎ "explanation": "In a model, the domain (or universe of discourse) is the boundary where its language is consistently interpreted, while outside it the same words may be interpreted in other models." ⏎ } | неверно верный: «bounded context» | Bounded Context; «Заказ» в биллинге и в доставке — разные модели. |
T26-L7 0.94 c | DDD | An anemic model (objects with only getters/setters, logic in services) is the recommended DDD style. | «no» Пояснение: DDD generally favors rich domain models over anemic models with logic in services.
Raw{"answer": "no", "explanation": "DDD generally favors rich domain models over anemic models with logic in services."} | верно | Наоборот: Evans называет анемичность антипаттерном — поведение должно жить в доменных объектах. |
T26-L8 0.73 c | DDD | Bounded context means each context has its own model: the same concept in different contexts is a different class. | «yes» Пояснение: In DDD, bounded contexts isolate models so shared terms can be represented independently in each context.
Raw{"answer":"yes","explanation":"In DDD, bounded contexts isolate models so shared terms can be represented independently in each context."} | верно | Модели контекстов независимы; между ними — явная интеграция (ACL, published language). |
T13-L1 11.04 c | Symfony | Services in the Symfony DI container are created lazily by default — on first use. | «yes» Пояснение: Yes, Symfony services are normally resolved and instantiated lazily when first requested from the container.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Yes, Symfony services are normally resolved and instantiated lazily when first requested from the container." ⏎ } | верно | Контейнер инстанцирует сервис при первом извлечении; eager-создания по умолчанию нет. |
T13-L2 0.83 c | Symfony | Which Symfony console command lists all registered routes? | «routes:list» Пояснение: In Symfony, the 'routes:list' console command displays all registered routes in the application.
Raw{"answer": "routes:list", "explanation": "In Symfony, the 'routes:list' console command displays all registered routes in the application."} | неверно верный: «debug:router» | bin/console debug:router (FrameworkBundle); в Symfony 3 команда называлась router:debug. |
T13-L3 0.79 c | Symfony | Symfony autowiring requires manually declaring every service in services.yaml. | «no» Пояснение: Symfony autowiring can automatically register many services based on type hints and annotations, so not every service must be declared manually in services.yaml.
Raw{"answer":"no","explanation":"Symfony autowiring can automatically register many services based on type hints and annotations, so not every service must be declared manually in services.yaml."} | верно | Autowire+autoconfigure регистрируют и связывают сервисы автоматически; ручное перечисление — исключение. |
T13-L4 4.99 c | Symfony | Twig templates are compiled into PHP classes and cached between requests. | «yes» Пояснение: Twig compiles templates into PHP classes and caches them to be reused across requests.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Twig compiles templates into PHP classes and caches them to be reused across requests." ⏎ } | верно | Twig компилирует шаблон один раз; кэш в var/cache/twig, в prod не пересобирается. |
T13-L5 1.75 c | Symfony | In the Symfony dev environment the DI container is rebuilt only after tracked files change, not on every request. | «yes» Пояснение: In Symfony’s dev environment, the DI container is cached and only rebuilt when tracked files change or the cache is invalidated.
Raw{"answer":"yes","explanation":"In Symfony’s dev environment, the DI container is cached and only rebuilt when tracked files change or the cache is invalidated."} | верно | Kernel проверяет freshness ресурсов (конфиги, классы); иначе переиспользуется кэш контейнера. |
T13-L6 0.91 c | Symfony | Which environment variable selects the active Symfony environment (dev/prod)? | «app_env» Пояснение: Symfony reads the APP_ENV environment variable to determine the active environment (e.g., dev, prod, test).
Raw{"answer": "APP_ENV", "explanation": "Symfony reads the APP_ENV environment variable to determine the active environment (e.g., dev, prod, test)."} | верно | APP_ENV в .env; APP_DEBUG — отдельный флаг отладки. |
T13-L7 17.09 c | Symfony | A controller method can be private — Symfony routing works with any method of the class. | «no» Пояснение: Symfony routing invokes controller action methods, which must be public; private methods are not routable.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "Symfony routing invokes controller action methods, which must be public; private methods are not routable." ⏎ } | верно | Действие контроллера должно быть public; приватный метод по маршруту не вызывается. |
T13-L8 5.6 c | Symfony | Event subscribers always receive events before listeners, because the interface gives them priority. | «no» Пояснение: There is no built-in priority rule that makes subscribers always receive events before listeners; ordering is determined by the event dispatcher’s priority settings and registration order.
Raw{"answer":"no","explanation":"There is no built-in priority rule that makes subscribers always receive events before listeners; ordering is determined by the event dispatcher’s priority settings and registration order."} | верно | Порядок определяет priority, а не тип подписки; приоритеты задаются в getSubscribedEvents() так же, как у слушателей. |
T22-L1 3.0 c | Symfony: Security and forms | In modern Symfony (6.0+) authentication is built on authenticator classes (AuthenticatorInterface); the old guard system has been removed. | «yes» Пояснение: Symfony 6.0 removed the old Guard classes and uses AuthenticatorInterface-based authenticators for authentication.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Symfony 6.0 removed the old Guard classes and uses AuthenticatorInterface-based authenticators for authentication." ⏎ } | верно | Guard объявлен устаревшим в 5.3 и удалён в 6.0; в проекте symfony/security-bundle 8.1. |
T22-L2 2.91 c | Symfony: Security and forms | Which Symfony attribute checks a role/permission right on a controller method (403 without it)? | «#[isgranted]» Пояснение: In Symfony (6.1+), the #[IsGranted] attribute placed on a controller method checks whether the authenticated user has the specified role or permission, and returns a 403 Forbidden response if they do not.
Raw{"answer":"#[IsGranted]","explanation":"In Symfony (6.1+), the #[IsGranted] attribute placed on a controller method checks whether the authenticated user has the specified role or permission, and returns a 403 Forbidden response if they do not."} | верно | #[IsGranted('ROLE_ADMIN')]; атрибут из symfony/security-http. |
T22-L3 2.29 c | Symfony: Security and forms | Voters are Symfony's mechanism for checking access to a specific object: isGranted('EDIT', $post). | «yes» Пояснение: Symfony AccessVoters are used for object-specific authorization checks like isGranted('EDIT', $post).
Raw{"answer":"yes","explanation":"Symfony AccessVoters are used for object-specific authorization checks like isGranted('EDIT', $post)."} | верно | VoterInterface->vote(); docs Symfony — Voters. |
T22-L4 159.23 c | Symfony: Security and forms | In modern Symfony (7+) validation constraints are declared as PHP attributes (#[Assert\NotBlank]); doctrine annotations are no longer supported. | «no» Пояснение: Doctrine annotations can still be used in Symfony 7 if doctrine/annotations is installed and enabled, though PHP attributes are the preferred approach.
Raw{"answer": "no", "explanation": "Doctrine annotations can still be used in Symfony 7 if doctrine/annotations is installed and enabled, though PHP attributes are the preferred approach."} | неверно верный: «yes» | Докблок-аннотации удалены в Symfony 7.0; стандарт — атрибуты. В проекте symfony/validator 8.1. |
T22-L5 1.03 c | Symfony: Security and forms | CSRF protection of Symfony forms is enabled by default: the form validates the token on submission. | «yes» Пояснение: Symfony automatically generates and validates the CSRF token in forms by default, so the statement is true.
Raw{"answer": "yes", "explanation": "Symfony automatically generates and validates the CSRF token in forms by default, so the statement is true."} | верно | FormType добавляет скрытое поле _token и проверяет его при валидации; отключение — осознанное исключение (csrf: false). |
T22-L6 1.46 c | Symfony: Security and forms | Form validation in Symfony runs server-side even if the client-side (HTML5) checks passed. | «yes» Пояснение: Symfony always re-validates form data on the server, regardless of whether client-side HTML5 validation passed, as this is a fundamental security principle.
Raw{"answer":"yes","explanation":"Symfony always re-validates form data on the server, regardless of whether client-side HTML5 validation passed, as this is a fundamental security principle."} | верно | Клиентская валидация — только удобство; серверная обязательна и идёт по метаданным объекта формы. |
T22-L7 1.46 c | Symfony: Security and forms | Which Symfony maker command generates a form class (FormType)? | «php bin/console maker:form» Пояснение: The Symfony MakerBundle command maker:form generates a FormType class for a form.
Raw{ ⏎ "answer": "php bin/console maker:form", ⏎ "explanation": "The Symfony MakerBundle command maker:form generates a FormType class for a form." ⏎ } | неверно верный: «make:form» | bin/console make:form (symfony/maker-bundle — в проекте). |
T22-L8 1.0 c | Symfony: Security and forms | Symfony stores the user's password in the session in plain text. | «no» Пояснение: Symfony does not store passwords in plain text; passwords are hashed with a password hasher and the session normally stores user identity, not the password.
Raw{"answer": "no", "explanation": "Symfony does not store passwords in plain text; passwords are hashed with a password hasher and the session normally stores user identity, not the password."} | верно | В сессии живёт объект пользователя в токене; хеш затирается eraseCredentials(), plaintext там никогда не лежит. |
T23-L1 1.2 c | Symfony: configuration and services | Symfony bundle configuration lives in config/packages — one file per bundle or topic. | «yes» Пояснение: Since Symfony 4.3, the recommended layout places each bundle's or topic's configuration in a separate file under config/packages (e.g., config/packages/doctrine.yaml, config/packages/messenger.yaml).
Raw{"answer": "yes", "explanation": "Since Symfony 4.3, the recommended layout places each bundle's or topic's configuration in a separate file under config/packages (e.g., config/packages/doctrine.yaml, config/packages/messenger.yaml)."} | верно | Стандартная структура (config/packages/*.yaml); перегрузка — config/packages/<env>. |
T23-L2 1.67 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 widely recommended best practice: a committed .env file documents required variables with safe dev defaults, while .env.local holds actual secrets and is excluded via .gitignore.
Raw{"answer": "yes", "explanation": "This is a widely recommended best practice: a committed .env file documents required variables with safe dev defaults, while .env.local holds actual secrets and is excluded via .gitignore."} | верно | symfony/dotenv: .env — общий безопасный набор значений; локальные секреты — .env.local (gitignored) или secrets-хранилище. |
T23-L3 0.64 c | Symfony: configuration and services | Which Symfony command lists the container's registered services and their aliases? | «debug:container» Пояснение: The debug:container command lists registered container services and their aliases.
Raw{"answer": "debug:container", "explanation": "The debug:container command lists registered container services and their aliases."} | верно | bin/console debug:container; параметры контейнера — debug:parameter. |
T23-L4 4.64 c | Symfony: configuration and services | The Symfony container allows changing parameters at runtime: $container->setParameter() works from a controller. | «yes» Пояснение: The Symfony Container class has a setParameter() method that can be called from a controller (via injected container instance), though it is only effective in non-frozen (development) mode and is generally discouraged for production use.
Raw{"answer": "yes", "explanation": "The Symfony Container class has a setParameter() method that can be called from a controller (via injected container instance), though it is only effective in non-frozen (development) mode and is generally discouraged for production use."} | неверно верный: «no» | Контейнер компилируется и замораживается; runtime-значения — только через переменные окружения. |
T23-L5 3.74 c | Symfony: configuration and services | By default, Symfony services are public (public: true) — you can fetch them directly from the container. | «yes» Пояснение: In Symfony, services are public by default unless explicitly marked private.
Raw{"answer": "yes", "explanation": "In Symfony, services are public by default unless explicitly marked private."} | неверно верный: «no» | С Symfony 4.0 сервисы по умолчанию private: инжектятся через autowiring; $container->get() — только для публичных. |
T23-L6 1.08 c | Symfony: configuration and services | Without a config file in config/packages a bundle will not work — configuration is mandatory for every bundle. | «no» Пояснение: A bundle does not require a configuration file in config/packages; it may work using defaults or no configuration.
Raw{"answer": "no", "explanation": "A bundle does not require a configuration file in config/packages; it may work using defaults or no configuration."} | верно | У бандлов есть встроенные умолчания (Extension); конфиг нужен только для отклонений от них. |
T23-L7 1.2 c | Symfony: configuration and services | Environment variable values are injected into services.yaml using the %env(VAR)% syntax. | «yes» Пояснение: In Symfony, the %env(VAR)% syntax is used in services.yaml to inject environment variable values into the configuration.
Raw{"answer": "yes", "explanation": "In Symfony, the %env(VAR)% syntax is used in services.yaml to inject environment variable values into the configuration."} | верно | %env(...)% резолвится в рантайме env-процессорами; docs — Env Var Processors. |
T23-L8 1.34 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 enables Symfony debug mode, which affects the profiler and Twig debugging.
Raw{"answer": "APP_DEBUG", "explanation": "The APP_DEBUG environment variable enables Symfony debug mode, which affects the profiler and Twig debugging."} | верно | APP_DEBUG=1 (в .env dev-окружения); окружение выбирает APP_ENV — см. T13-L6. |
T16-L1 1.88 c | Symfony: Messenger | A single message in Symfony Messenger can only have one handler. | «no» Пояснение: Symfony Messenger can have multiple handlers registered for the same message type.
Raw{"answer": "no", "explanation": "Symfony Messenger can have multiple handlers registered for the same message type."} | верно | Messenger вызывает все хендлеры, подписанные на класс сообщения (docs — Multiple Handlers). |
T16-L2 2.1 c | Symfony: Messenger | The sync transport in Messenger queues the message for a worker, just like async. | «no» Пояснение: The sync transport processes the message in-process by calling the handlers directly, rather than queueing the message for a worker to consume.
Raw{"answer": "no", "explanation": "The sync transport processes the message in-process by calling the handlers directly, rather than queueing the message for a worker to consume."} | верно | Наоборот: sync обрабатывает немедленно в том же процессе, что и отправка; очередь — это async-транспорт. |
T16-L3 1.75 c | Symfony: Messenger | Which console command starts the worker that processes Messenger queue messages? | «messenger:consume» Пояснение: This Symfony console command starts a worker to consume Messenger queue messages.
Raw{ ⏎ "answer": "messenger:consume", ⏎ "explanation": "This Symfony console command starts a worker to consume Messenger queue messages." ⏎ } | верно | bin/console messenger:consume async; воркеры под supervisord/systemd в проде. |
T16-L4 4.42 c | Symfony: Messenger | Retries for failed messages (retry_strategy) are configured per Messenger transport. | «yes» Пояснение: In Symfony Messenger, retry_strategy is a per-transport option for handling failed messages.
Raw{"answer":"yes","explanation":"In Symfony Messenger, retry_strategy is a per-transport option for handling failed messages."} | верно | retry_strategy на транспорте: max_retries, delay, multiplier; docs — Failed Messages & Retries. |
T16-L5 1.38 c | Symfony: Messenger | By default, Messenger serializes messages to JSON. | «yes» Пояснение: Symfony Messenger's default serializer is JSON unless another serializer is configured.
Raw{"answer":"yes","explanation":"Symfony Messenger's default serializer is JSON unless another serializer is configured."} | неверно верный: «no» | Дефолтный сериализатор — PhpSerializer (serialize()); JSON-сериализатор включается отдельно. |
T16-L6 10.33 c | Symfony: Messenger | Symfony Scheduler produces messages on a schedule and dispatches them through Messenger. | «yes» Пояснение: The Symfony Scheduler creates scheduled messages and sends them through the Messenger dispatcher.
Raw{"answer": "yes", "explanation": "The Symfony Scheduler creates scheduled messages and sends them through the Messenger dispatcher."} | верно | Schedule → RecurringMessage → шина Messenger; docs — Scheduler. |
T16-L7 1.41 c | Symfony: Messenger | Which built-in Messenger transport stores messages in database tables via Doctrine? | «database» Пояснение: Symfony Messenger's built-in database transport uses Doctrine to store messages in database tables.
Raw{"answer": "database", "explanation": "Symfony Messenger's built-in database transport uses Doctrine to store messages in database tables."} | неверно верный: «doctrine» | Транспорт doctrine (symfony/doctrine-messenger); таблица messenger_messages. В проекте стоит amqp-messenger + doctrine-messenger. |
T16-L8 15.2 c | Symfony: Messenger | The Messenger pipeline can be extended with custom middleware, placed before or after the built-in ones. | «yes» Пояснение: Custom middleware can be added to the Messenger pipeline and placed before or after the built-in middleware.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Custom middleware can be added to the Messenger pipeline and placed before or after the built-in middleware." ⏎ } | верно | messenger.bus.*.middleware в yaml; docs — Middleware. |
T28-L1 107.41 c | Symfony: versions | Symfony major releases come every two years, minor ones every six months (in May and November). | «yes» Пояснение: Symfony's standard release cycle is a major version every two years and a minor version every six months, in May and November.
Raw{"answer": "yes", "explanation": "Symfony's standard release cycle is a major version every two years and a minor version every six months, in May and November."} | верно | Стандартный релизный цикл: 8.0 — ноябрь 2025, 8.1 — май 2026, 8.2 — ноябрь 2026. |
T28-L2 8.7 c | Symfony: versions | What is the minimum PHP version required by Symfony 8? | «8.3» Пояснение: Symfony 8 requires at least PHP 8.3.
Raw{"answer":"8.3","explanation":"Symfony 8 requires at least PHP 8.3."} | неверно верный: «8.4» | Symfony 8.0 поднял требование до PHP >= 8.4.1 (в vendor проекта: "php": ">=8.4.1"). |
T28-L3 3.14 c | Symfony: versions | Symfony 7.0 kept support for docblock annotations (validation, routes). | «no» Пояснение: Symfony 7.0 removed support for docblock annotations, requiring PHP attributes instead.
Raw{"answer":"no","explanation":"Symfony 7.0 removed support for docblock annotations, requiring PHP attributes instead."} | верно | Наоборот: в 7.0 аннотации удалены — только PHP-атрибуты (#[Route], #[Assert\NotBlank]). |
T28-L4 3.23 c | Symfony: versions | AssetMapper manages CSS/JS without node or webpack — via importmap.php. | «yes» Пояснение: AssetMapper can handle CSS and JavaScript asset mapping without Node.js or webpack using an importmap.php file.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "AssetMapper can handle CSS and JavaScript asset mapping without Node.js or webpack using an importmap.php file." ⏎ } | верно | symfony/asset-mapper (с 6.3, стандарт с 7.x); в проекте — importmap.php в корне и asset-mapper 8.1. |
T28-L5 7.08 c | Symfony: versions | Symfony 6.4 is a regular release without long-term support. | «no» Пояснение: Symfony 6.4 is an LTS (Long Term Upgrade) release, so it does receive long-term support.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "Symfony 6.4 is an LTS (Long Term Upgrade) release, so it does receive long-term support." ⏎ } | верно | Наоборот: 6.4 — LTS (расширенная поддержка); LTS выходит вместе с очередным мажором (6.4 — вместе с 7.0). |
T28-L6 1.88 c | Symfony: versions | When moving to a new Symfony major version, deprecations of the previous branch keep working — major releases do not remove them. | «no» Пояснение: Major Symfony releases remove the deprecations from the previous branch; the deprecation cycle works by deprecating in one major version and removing in the next major version.
Raw{"answer": "no", "explanation": "Major Symfony releases remove the deprecations from the previous branch; the deprecation cycle works by deprecating in one major version and removing in the next major version."} | верно | Наоборот: мажорный релиз удаляет всё устаревшее (7.0 убрал деприкейшены 6.x, 8.0 — 7.x). |
T28-L7 0.94 c | Symfony: versions | Every Symfony major release is accompanied by an UPGRADE guide listing the changes. | «yes» Пояснение: Symfony publishes an UPGRADE guide for each major release documenting breaking changes and upgrade instructions.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Symfony publishes an UPGRADE guide for each major release documenting breaking changes and upgrade instructions." ⏎ } | верно | UPGRADE-7.0.md, UPGRADE-8.0.md в репозитории symfony/symfony. |
T28-L8 4.51 c | Symfony: versions | Which Symfony component manages assets and the importmap without node/webpack? | «symfony assetmapper» Пояснение: The Symfony AssetMapper component manages assets and importmap without Node.js or webpack.
Raw{ ⏎ "answer": "Symfony AssetMapper", ⏎ "explanation": "The Symfony AssetMapper component manages assets and importmap without Node.js or webpack." ⏎ } | верно | symfony/asset-mapper 8.1 — в проекте. |
T29-L1 45.41 c | Symfony: 8.2 and beyond | As of 2026-11-07, Symfony 8.2 has already been released. | «yes» Пояснение: Symfony's release schedule places version 8.2 in 2026 before November 7, 2026.
Raw{"answer":"yes","explanation":"Symfony's release schedule places version 8.2 in 2026 before November 7, 2026."} | неверно верный: «no» | Наоборот: 8.2 ещё не выпущена — релиз в конце ноября 2026; последняя стабильная — 8.1. |
T29-L2 71.85 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» Пояснение: Under Symfony’s normal release cadence, November 2026 corresponds to Symfony 7.4 LTS, not 8.2.
Raw{"answer":"no","explanation":"Under Symfony’s normal release cadence, November 2026 corresponds to Symfony 7.4 LTS, not 8.2."} | неверно верный: «yes» | Политика релизов: 8.1 — май 2026, 8.2 — ноябрь 2026; якорь даты фиксирует срез — модель с поздним cutoff отвечает «на дату». |
T29-L3 23.13 c | Symfony: 8.2 and beyond | Which Symfony version comes after 8.1 (as of 2026-11-07)? | «8.2» Пояснение: Symfony 8.2 is the next minor release after 8.1.
Raw{"answer":"8.2","explanation":"Symfony 8.2 is the next minor release after 8.1."} | верно | 8.2 — следующий минорный релиз (ноябрь 2026); после его выхода проект переходит с 8.1.* на 8.2.*. |
T29-L4 3.04 c | Symfony: 8.2 and beyond | Symfony 8.2 is a major release requiring applications to be rewritten for new APIs. | «no» Пояснение: Symfony 8.2 is a minor release within the 8.x line, not a major release requiring a full rewrite.
Raw{"answer": "no", "explanation": "Symfony 8.2 is a minor release within the 8.x line, not a major release requiring a full rewrite."} | верно | Наоборот: 8.2 — минорный релиз; новые возможности без поломки обратной совместимости. Мажор — 9.0. |
T29-L5 12.65 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» Пояснение: A 8.1 → 8.2 update is a minor release within the same PHP 8 major line and is intended to remain backward compatible.
Raw{"answer":"yes","explanation":"A 8.1 → 8.2 update is a minor release within the same PHP 8 major line and is intended to remain backward compatible."} | верно | Политика Symfony: минорные релизы обратно совместимы; BC-break допустим только в мажорных. |
T29-L6 14.95 c | Symfony: 8.2 and beyond | Which minor version of the 8.x branch is released last, before Symfony 9.0? | «8.4» Пояснение: Following Symfony's consistent pattern of five minor releases per major branch (e.g., 4.4 before 5.0, 5.4 before 6.0, 6.4 before 7.0, 7.4 before 8.0), the last 8.x minor version before Symfony 9.0 is 8.4.
Raw{"answer": 8.4, "explanation": "Following Symfony's consistent pattern of five minor releases per major branch (e.g., 4.4 before 5.0, 5.4 before 6.0, 6.4 before 7.0, 7.4 before 8.0), the last 8.x minor version before Symfony 9.0 is 8.4."} | верно | По циклу: 8.2 (ноя 2026), 8.3 (май 2027), 8.4 (ноя 2027, вместе с 9.0) — как 6.4 выходила вместе с 7.0. |
T29-L7 36.31 c | Symfony: 8.2 and beyond | Symfony 8.2 will require PHP 8.5 — you would have to upgrade PHP along with it. | «yes» Пояснение: Symfony 8.2 requires PHP 8.5, so PHP must be upgraded to meet the new requirement.
Raw{"answer":"yes","explanation":"Symfony 8.2 requires PHP 8.5, so PHP must be upgraded to meet the new requirement."} | неверно верный: «no» | Наоборот: минорные релизы не поднимают требования PHP; для всей ветки 8.x остаётся PHP >= 8.4. |
T29-L8 2.25 c | Symfony: 8.2 and beyond | Deprecations added in the 8.x branch will not be removed before Symfony 9.0. | «yes» Пояснение: Deprecations introduced in the Symfony 8.x branch are intended to remain until they are removed in Symfony 9.0.
Raw{"answer": "yes", "explanation": "Deprecations introduced in the Symfony 8.x branch are intended to remain until they are removed in Symfony 9.0."} | верно | Политика: деприкейшены живут до следующего мажора; 9.0 — ноябрь 2027. |
T21-L1 1.87 c | Twig | Inside {{ }}, Twig allows calling arbitrary PHP code directly. | «no» Пояснение: Twig's {{ }} output tags use a restricted expression language for rendering variables, registered functions, and filters, not arbitrary PHP code.
Raw{"answer": "no", "explanation": "Twig's {{ }} output tags use a restricted expression language for rendering variables, registered functions, and filters, not arbitrary PHP code."} | верно | Twig — DSL: только разрешённые окружением функции/фильтры; произвольный PHP не исполняется. |
T21-L2 1.8 c | Twig | By default, Twig auto-escapes printed variables. | «yes» Пояснение: Twig automatically escapes printed variables by default to prevent security issues.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Twig automatically escapes printed variables by default to prevent security issues." ⏎ } | верно | Autoescape включён по умолчанию; {{ '<b>' }} → <b>. Проверено на Twig 3.30. |
T21-L3 0.91 c | Twig | The Twig |e filter escapes a string for safe output in an HTML context. | «yes» Пояснение: By default, Twig's |e filter escapes a string for safe output in an HTML context.
Raw{"answer": "yes", "explanation": "By default, Twig's |e filter escapes a string for safe output in an HTML context."} | верно | |e ('html') по умолчанию; есть контексты js/url/css. От SQL-инъекций он не защищает — это задача подготовленных запросов Doctrine. |
T21-L4 74.73 c | Twig | Which filter from twig/intl-extra formats a number according to a locale? | «format_number» Пояснение: The format_number filter in twig/intl-extra formats a numeric value using the specified locale.
Raw{"answer":"format_number","explanation":"The format_number filter in twig/intl-extra formats a numeric value using the specified locale."} | верно | |format_number(locale=...) из IntlExtension (twig/intl-extra есть в проекте). Проверено на Twig 3.30: 12345.6 → 12 345,6 (ru). |
T21-L5 6.75 c | Twig | The |raw filter disables auto-escaping for the value. | «yes» Пояснение: The raw filter outputs the value without escaping.
Raw{"answer":"yes","explanation":"The raw filter outputs the value without escaping."} | верно | {{ x|raw }} выводит HTML как есть; опасно с пользовательскими данными. Проверено на Twig 3.30. |
T21-L6 1.03 c | Twig | In Twig, {{ }} prints an expression value, while {% %} executes tags — conditions, loops, set. | «yes» Пояснение: In Twig, {{ }} prints an expression value, while {% %} executes tags such as conditions, loops, and assignments.
Raw{"answer":"yes","explanation":"In Twig, {{ }} prints an expression value, while {% %} executes tags such as conditions, loops, and assignments."} | верно | Два блока синтаксиса Twig: вывод (echo) против логики. |
T21-L7 1.28 c | Twig | In Twig you cannot declare a variable inside a template — values only come from the controller. | «no» Пояснение: Twig allows you to declare variables inside templates using the `set` tag.
Raw{"answer": "no", "explanation": "Twig allows you to declare variables inside templates using the `set` tag."} | верно | {% set y = ... %} объявляет переменную в шаблоне. Проверено на Twig 3.30. |
T21-L8 0.99 c | Twig | Which Twig function dumps the debug structure of a variable (array, object)? | «dump» Пояснение: The Twig dump function outputs the debug structure of a variable.
Raw{"answer": "dump", "explanation": "The Twig dump function outputs the debug structure of a variable."} | верно | {{ dump(x) }} (DebugExtension; в Symfony доступна в dev-окружении). |
T24-L1 0.89 c | Bootstrap | Bootstrap is a CSS/JS library of ready-made UI components, not an SPA framework. | «yes» Пояснение: Bootstrap is primarily a CSS/JavaScript library for UI components, not a single-page application framework.
Raw{"answer": "yes", "explanation": "Bootstrap is primarily a CSS/JavaScript library for UI components, not a single-page application framework."} | верно | Компоненты и утилиты поверх вашего HTML; SPA-фреймворки (React/Vue) — другой класс инструментов. В проекте vendored 5.3.3. |
T24-L2 0.89 c | Bootstrap | Which Bootstrap class gives a responsive container with a fixed max width per breakpoint? | «container» Пояснение: The Bootstrap .container class provides a responsive container with fixed max-width values at each breakpoint.
Raw{"answer": "container", "explanation": "The Bootstrap .container class provides a responsive container with fixed max-width values at each breakpoint."} | верно | .container (фиксированная макс-ширина по брейкпоинтам) vs .container-fluid (на всю ширину). |
T24-L3 1.4 c | Bootstrap | The Bootstrap grid is built on CSS floats and splits a row into 16 columns. | «no» Пояснение: The Bootstrap grid is based on 12 columns, and modern Bootstrap uses flexbox rather than CSS floats.
Raw{"answer": "no", "explanation": "The Bootstrap grid is based on 12 columns, and modern Bootstrap uses flexbox rather than CSS floats."} | верно | Наоборот: flexbox (с Bootstrap 4) и 12 колонок; float-сетка — это Bootstrap 3. |
T24-L4 1.59 c | Bootstrap | Bootstrap's named breakpoints (the infix used in class names) are sm, md, lg, xl, xxl — five of them. | «yes» Пояснение: Modern Bootstrap (e.g., Bootstrap 4/5) defines five named breakpoints: sm, md, lg, xl, and xxl.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Modern Bootstrap (e.g., Bootstrap 4/5) defines five named breakpoints: sm, md, lg, xl, and xxl." ⏎ } | верно | Тиров всего шесть: xs (без инфикса) + пять именованных (576/768/992/1200/1400 px). |
T24-L5 2.03 c | Bootstrap | Utilities like .mt-3 or .px-2 use the spacing scale: the number is a multiple of $spacer. | «yes» Пояснение: Utilities like .mt-3 and .px-2 use a number multiplied by the base spacing value, such as $spacer.
Raw{"answer": "yes", "explanation": "Utilities like .mt-3 and .px-2 use a number multiplied by the base spacing value, such as $spacer."} | неверно верный: «no» | Spacing utilities; $spacer = 1rem. |
T24-L6 2.92 c | Bootstrap | Which Bootstrap 5 data attribute enables an interactive component (e.g. dropdown) on an element? | «data-bs-toggle» Пояснение: In Bootstrap 5, data-bs-toggle is used to enable and trigger interactive components such as dropdowns.
Raw{"answer": "data-bs-toggle", "explanation": "In Bootstrap 5, data-bs-toggle is used to enable and trigger interactive components such as dropdowns."} | верно | data-bs-toggle="dropdown" и т.п.; в Bootstrap 4 атрибут назывался data-toggle. |
T24-L7 1.0 c | Bootstrap | Bootstrap 5 components work without jQuery — in plain vanilla JS. | «yes» Пояснение: Bootstrap 5 dropped its jQuery dependency in favor of its own vanilla JavaScript implementation.
Raw{"answer": "yes", "explanation": "Bootstrap 5 dropped its jQuery dependency in favor of its own vanilla JavaScript implementation."} | верно | jQuery удалён в Bootstrap 5.0: data-bs-* атрибуты и JS API. В проекте vendored 5.3.3. |
T24-L8 2.61 c | Bootstrap | Dark mode in Bootstrap is enabled with a .dark class on the root element. | «no» Пояснение: In Bootstrap 5, dark mode is enabled by adding data-bs-theme="dark" to the root element, not by a .dark class.
Raw{"answer":"no","explanation":"In Bootstrap 5, dark mode is enabled by adding data-bs-theme=\"dark\" to the root element, not by a .dark class."} | верно | Наоборот: тема включается атрибутом data-bs-theme="dark" (Color modes, с 5.3); класса .dark не существует. В проекте 5.3.3. |
T14-L1 1.4 c | Doctrine | Doctrine ORM creates database tables on the fly the first time an entity is used at runtime. | «no» Пояснение: Doctrine ORM does not create database tables automatically when an entity is first used at runtime.
Raw{ ⏎ "answer": "false", ⏎ "explanation": "Doctrine ORM does not create database tables automatically when an entity is first used at runtime." ⏎ } | верно | Схему создают инструменты (migrations, schema tool); рантайм структуру БД не меняет. |
T14-L2 2.0 c | Doctrine | Which EntityManager method marks a new object as managed without executing SQL until flush()? | «persist» Пояснение: EntityManager::persist() marks a new object as managed without executing SQL until flush() is called.
Raw{"answer": "persist", "explanation": "EntityManager::persist() marks a new object as managed without executing SQL until flush() is called."} | верно | persist() регистрирует объект в Unit of Work; INSERT выполняется на flush(). |
T14-L3 1.31 c | Doctrine | In Doctrine ORM 3, the EntityManager::merge() method exists and makes the passed object managed. | «yes» Пояснение: In Doctrine ORM 3, EntityManager::merge() exists and makes the passed object managed.
Raw{"answer": "yes", "explanation": "In Doctrine ORM 3, EntityManager::merge() exists and makes the passed object managed."} | неверно верный: «no» | В ORM 3 merge() удалён (в vendor проекта 3.7.6 метода нет); в Doctrine 2.x merge() возвращал управляемую копию. Версия зафиксирована — ORM 3. |
T14-L4 0.99 c | Doctrine | DQL queries are written in terms of entities and their fields, not tables and columns. | «yes» Пояснение: Doctrine Query Language is entity-oriented and uses entities and their properties rather than database tables and columns.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Doctrine Query Language is entity-oriented and uses entities and their properties rather than database tables and columns." ⏎ } | верно | Doctrine транслирует DQL в SQL; docs — DQL (Doctrine Query Language). |
T14-L5 5.63 c | Doctrine | What does $repository->find(999) return when no record with id 999 exists? | «null» Пояснение: The find method returns null when no record with the given id exists.
Raw{"answer":"null","explanation":"The find method returns null when no record with the given id exists."} | верно | find() возвращает null, если объект не найден (docs Repository methods). |
T14-L6 2.44 c | Doctrine | DoctrineBundle in Symfony automatically calls flush() at the end of every request. | «yes» Пояснение: The DoctrineBundle's EventSubscriber listens to the kernel.end_request event and calls EntityManager::flush() automatically at the end of every request.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "The DoctrineBundle's EventSubscriber listens to the kernel.end_request event and calls EntityManager::flush() automatically at the end of every request." ⏎ } | неверно верный: «no» | Авто-flush нет — flush() зовёт разработчик; незакрытая транзакция в конце запроса откатывается. |
T14-L7 2.33 c | Doctrine | For a managed entity, changing a property is enough: flush() commits the change without an explicit persist() — the Unit of Work tracks changes. | «yes» Пояснение: A managed entity is already tracked by the Unit of Work, so property changes are detected automatically and flush() issues the corresponding UPDATE without needing persist().
Raw{"answer": "yes", "explanation": "A managed entity is already tracked by the Unit of Work, so property changes are detected automatically and flush() issues the corresponding UPDATE without needing persist()."} | верно | Dirty checking сравнивает снимки свойств; persist нужен только новым/отсоединённым объектам. |
T14-L8 1.49 c | Doctrine | remove() executes the SQL DELETE immediately, without waiting for flush(). | «no» Пояснение: remove() only marks the entity for deletion in the unit of work; the actual SQL DELETE is executed when flush() is called (or implicitly at the end of a request/transaction).
Raw{"answer": "no", "explanation": "remove() only marks the entity for deletion in the unit of work; the actual SQL DELETE is executed when flush() is called (or implicitly at the end of a request/transaction)."} | верно | remove() планирует удаление в Unit of Work; DELETE выполняется на flush() (docs — Deleting Objects). |
T15-L1 1.6 c | PostgreSQL | PostgreSQL uses MVCC, therefore readers block writers and writers block readers. | «no» Пояснение: PostgreSQL's MVCC allows readers and writers to proceed concurrently without blocking each other.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "PostgreSQL's MVCC allows readers and writers to proceed concurrently without blocking each other." ⏎ } | верно | Наоборот: благодаря MVCC читатели не блокируют писателей и наоборот (снимки строк); docs PostgreSQL — Concurrency Control. |
T15-L2 1.18 c | PostgreSQL | Which SQL command shows a query's execution plan without executing the query? | «explain» Пояснение: The EXPLAIN command in SQL displays how a query will be executed (the execution plan) without actually running the query.
Raw{"answer":"EXPLAIN","explanation":"The EXPLAIN command in SQL displays how a query will be executed (the execution plan) without actually running the query."} | верно | EXPLAIN без ANALYZE только строит план; проверено на PostgreSQL 17.7. |
T15-L3 4.49 c | PostgreSQL | SERIAL and GENERATED ... AS IDENTITY are just two names for the same mechanism. | «no» Пояснение: SERIAL is a convenience shorthand that creates a sequence and default, while GENERATED ... AS IDENTITY is a separate SQL standard identity-column mechanism with different semantics.
Raw{"answer": "no", "explanation": "SERIAL is a convenience shorthand that creates a sequence and default, while GENERATED ... AS IDENTITY is a separate SQL standard identity-column mechanism with different semantics."} | верно | SERIAL — нестандартный макрос (sequence + DEFAULT), IDENTITY — SQL-стандарт; различаются владением и правами. Оба есть в PG 17 (проверено). |
T15-L4 17.5 c | PostgreSQL | By default, a PostgreSQL UNIQUE constraint allows only one row with NULL in the column. | «no» Пояснение: PostgreSQL treats NULL values as distinct by default, so a UNIQUE constraint allows multiple rows with NULL in the column.
Raw{"answer":"no","explanation":"PostgreSQL treats NULL values as distinct by default, so a UNIQUE constraint allows multiple rows with NULL in the column."} | верно | Наоборот: NULLS DISTINCT по умолчанию — несколько NULL допустимы; NULLS NOT DISTINCT — опция с PG 15. Проверено на PG 17.7. |
T15-L5 0.95 c | PostgreSQL | Which PostgreSQL aggregate function concatenates strings with a separator? | «string_agg()» Пояснение: PostgreSQL's string_agg() is an aggregate function that concatenates values with a specified separator, e.g., string_agg(column, ',').
Raw{"answer": "string_agg()", "explanation": "PostgreSQL's string_agg() is an aggregate function that concatenates values with a specified separator, e.g., string_agg(column, ',')."} | верно | string_agg(значение, разделитель); проверено на PostgreSQL 17.7. |
T15-L6 1.16 c | PostgreSQL | Plain VACUUM returns the space occupied by dead tuples to the operating system. | «no» Пояснение: Plain VACUUM reclaims space for reuse within the table but does not shrink it or return pages to the operating system.
Raw{"answer": "no", "explanation": "Plain VACUUM reclaims space for reuse within the table but does not shrink it or return pages to the operating system."} | верно | VACUUM помечает место для переиспользования внутри таблицы; ОС его возвращает только VACUUM FULL (с эксклюзивной блокировкой). |
T15-L7 0.85 c | PostgreSQL | Which keyword in a window function definition partitions rows into groups the function is computed over? | «partition by» Пояснение: The PARTITION BY keyword in a SQL window function definition divides the result set into groups (partitions) over which the window function is computed.
Raw{"answer": "PARTITION BY", "explanation": "The PARTITION BY keyword in a SQL window function definition divides the result set into groups (partitions) over which the window function is computed."} | верно | OVER (PARTITION BY ...); проверено на PostgreSQL 17.7. |
T15-L8 1.86 c | PostgreSQL | The READ COMMITTED isolation level protects against non-repeatable reads. | «no» Пояснение: READ COMMITTED prevents dirty reads but does not protect against non-repeatable reads.
Raw{"answer": "no", "explanation": "READ COMMITTED prevents dirty reads but does not protect against non-repeatable reads."} | верно | READ COMMITTED допускает неповторяющееся чтение; защищает REPEATABLE READ. Проверено: SHOW transaction_isolation → read committed. |
T17-L1 1.74 c | PostgreSQL: transactions and indexes | By default, PostgreSQL wraps each single SQL statement in its own implicit transaction (autocommit). | «yes» Пояснение: By default, PostgreSQL is in autocommit mode, so each statement is executed in its own transaction and committed automatically.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "By default, PostgreSQL is in autocommit mode, so each statement is executed in its own transaction and committed automatically." ⏎ } | верно | Без BEGIN каждый оператор коммитится сам; docs PostgreSQL — Transactions. Проверено на PG 17. |
T17-L2 0.89 c | PostgreSQL: transactions and indexes | Which SQL command ends a transaction, committing all its changes? | «commit» Пояснение: COMMIT ends a transaction and makes all changes permanent.
Raw{ ⏎ "answer": "COMMIT", ⏎ "explanation": "COMMIT ends a transaction and makes all changes permanent." ⏎ } | верно | COMMIT (END — синоним). Проверено на PG 17. |
T17-L3 1.89 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 can speed up UPDATE and DELETE statements when they search on an indexed column, in addition to SELECT.
Raw{"answer": "yes", "explanation": "Indexes can speed up UPDATE and DELETE statements when they search on an indexed column, in addition to SELECT."} | верно | Поиск строк для изменения идёт по индексу; docs PostgreSQL — Indexes. |
T17-L4 1.37 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 checkpoint within a transaction, and ROLLBACK TO <savepoint> undoes only the statements executed after that point while preserving the rest of the transaction.
Raw{"answer":"yes","explanation":"SAVEPOINT allows you to create a named checkpoint within a transaction, and ROLLBACK TO <savepoint> undoes only the statements executed after that point while preserving the rest of the transaction."} | верно | SAVEPOINT name; ROLLBACK TO name — частичный откат без отмены всей транзакции. Проверено на PG 17. |
T17-L5 1.31 c | PostgreSQL: transactions and indexes | EXPLAIN ANALYZE shows the query plan without executing the query. | «no» Пояснение: EXPLAIN ANALYZE executes the query to collect actual execution statistics.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "EXPLAIN ANALYZE executes the query to collect actual execution statistics." ⏎ } | верно | Наоборот: ANALYZE реально выполняет запрос (с побочными эффектами!) и показывает фактические времена узлов; план без выполнения — plain EXPLAIN. |
T17-L6 0.74 c | PostgreSQL: transactions and indexes | Which PostgreSQL extension adds vector types and indexes for embedding search? | «pgvector» Пояснение: pgvector is the PostgreSQL extension that provides vector types and index support for embedding search.
Raw{"answer": "pgvector", "explanation": "pgvector is the PostgreSQL extension that provides vector types and index support for embedding search."} | верно | CREATE EXTENSION vector (проект pgvector; в проекте образ pgvector/pgvector:pg17). |
T17-L7 0.73 c | PostgreSQL: transactions and indexes | A partial index (CREATE INDEX ... WHERE ...) is built only over rows satisfying the condition. | «yes» Пояснение: A partial index stores only the rows whose rows satisfy the WHERE condition.
Raw{"answer":"yes","explanation":"A partial index stores only the rows whose rows satisfy the WHERE condition."} | верно | docs PostgreSQL — Partial Indexes; типичный кейс — индекс по «активным» записям. |
T17-L8 3.94 c | PostgreSQL: transactions and indexes | The SERIALIZABLE level in PostgreSQL is implemented by locking the rows a transaction reads. | «no» Пояснение: PostgreSQL implements SERIALIZABLE through serializable snapshot isolation with anomaly detection, not by simply locking the rows a transaction reads.
Raw{"answer": "no", "explanation": "PostgreSQL implements SERIALIZABLE through serializable snapshot isolation with anomaly detection, not by simply locking the rows a transaction reads."} | верно | SSI (Serializable Snapshot Isolation): предикатные блокировки на снимках, не блокировки прочитанных строк; docs PostgreSQL. |
T19-L1 0.95 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 successfully created a new resource.
Raw{"answer": "yes", "explanation": "HTTP 201 Created indicates that the request successfully created a new resource."} | верно | 201 Created; обычно на POST, часто с Location; RFC 9110. |
T19-L2 1.48 c | HTTP and REST API | Which HTTP status means a successful request with an empty response body (e.g. after DELETE)? | «204» Пояснение: HTTP status 204 No Content indicates a successful request where the server intentionally returns no body in the response, which is the typical response after a DELETE operation.
Raw{"answer": 204, "explanation": "HTTP status 204 No Content indicates a successful request where the server intentionally returns no body in the response, which is the typical response after a DELETE operation."} | верно | 204 No Content; RFC 9110. |
T19-L3 2.07 c | HTTP and REST API | The DELETE method is idempotent per the HTTP specification: repeating the request for the same resource does not change the outcome. | «yes» Пояснение: Per RFC 9110, DELETE is explicitly defined as an idempotent HTTP method, meaning repeating the same DELETE request has the same effect as a single request (the resource is deleted the first time and subsequent attempts find nothing to delete).
Raw{"answer": "yes", "explanation": "Per RFC 9110, DELETE is explicitly defined as an idempotent HTTP method, meaning repeating the same DELETE request has the same effect as a single request (the resource is deleted the first time and subsequent attempts find nothing to delete)."} | верно | RFC 9110: DELETE идемпотентен (как PUT); идемпотентность ≠ безопасность — ресурс удаляется при первом вызове. |
T19-L4 1.67 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» Пояснение: Access-Control-Allow-Origin is a server response header, not a client-sent header.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "Access-Control-Allow-Origin is a server response header, not a client-sent header." ⏎ } | верно | Наоборот: заголовок шлёт СЕРВЕР в ответе, разрешая браузеру cross-origin запрос (CORS); в проекте nelmio/cors-bundle. |
T19-L5 0.82 c | HTTP and REST API | Status 429 Too Many Requests is used when a client exceeds a rate limit. | «yes» Пояснение: HTTP 429 indicates that the client has sent too many requests in a given amount of time, often due to rate limiting.
Raw{"answer": "yes", "explanation": "HTTP 429 indicates that the client has sent too many requests in a given amount of time, often due to rate limiting."} | верно | 429 (+ Retry-After); RFC 6585. В проекте symfony/rate-limiter. |
T19-L6 0.97 c | HTTP and REST API | 5xx codes mean a client error, while 4xx means a server-side error. | «no» Пояснение: 4xx codes indicate client errors, while 5xx codes indicate server-side errors.
Raw{"answer": "no", "explanation": "4xx codes indicate client errors, while 5xx codes indicate server-side errors."} | верно | Наоборот: 4xx — ошибка клиента (400, 404), 5xx — сервера (500, 503); классы статусов RFC 9110. |
T19-L7 0.87 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 26.78 c | HTTP and REST API | PATCH is not required to be idempotent per RFC 5789, unlike PUT. | «yes» Пояснение: True: unlike PUT, PATCH is not required to be idempotent.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "True: unlike PUT, PATCH is not required to be idempotent." ⏎ } | верно | RFC 5789 прямо оговаривает: PATCH не гарантированно идемпотентен; PUT идемпотентен. |
T20-L1 2.8 c | Security and OAuth | Checking a password by comparing its hash to the stored hash with a plain == is sufficient. | «no» Пояснение: A plain == comparison is not sufficient because it is vulnerable to timing attacks; PHP's hash_equals() function should be used instead to perform a constant-time comparison.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "A plain == comparison is not sufficient because it is vulnerable to timing attacks; PHP's hash_equals() function should be used instead to perform a constant-time comparison." ⏎ } | верно | Нужна постоянновременная проверка (password_verify) — timing-атаки; соль и алгоритм уже внутри хеша. |
T20-L2 1.0 c | Security and OAuth | A CSRF token is issued by the server (bound to the session) and verified server-side on unsafe requests (POST etc.). | «yes» Пояснение: CSRF tokens are generated and bound to the user's session, then validated server-side for unsafe methods like POST to prevent cross-site request forgery.
Raw{"answer":"yes","explanation":"CSRF tokens are generated and bound to the user's session, then validated server-side for unsafe methods like POST to prevent cross-site request forgery."} | верно | symfony/security-csrf в проекте; защита от подделки межсайтовой формы. |
T20-L3 0.63 c | Security and OAuth | Which HTTP header enables the CSP (Content Security Policy) policy? | «content-security-policy» Пояснение: The Content-Security-Policy HTTP header defines and enforces a Content Security Policy.
Raw{"answer":"Content-Security-Policy","explanation":"The Content-Security-Policy HTTP header defines and enforces a Content Security Policy."} | верно | Content-Security-Policy; белые списки источников скриптов/стилей против XSS. |
T20-L4 1.06 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, and access tokens are primarily for resource access rather than identifying the user.
Raw{"answer": "no", "explanation": "OAuth 2.0 is an authorization protocol, and access tokens are primarily for resource access rather than identifying the user."} | верно | OAuth 2.0 — авторизация/делегирование доступа; аутентификацию добавляет OpenID Connect. В проекте knpuniversity/oauth2-client-bundle (yandex/github/google). |
T20-L5 1.79 c | Security and OAuth | XSS is prevented by validating input on the server before writing it to the database. | «no» Пояснение: Server-side validation before storing data does not reliably prevent XSS, because unsafe content can still be rendered later without proper output encoding.
Raw{"answer":"no","explanation":"Server-side validation before storing data does not reliably prevent XSS, because unsafe content can still be rendered later without proper output encoding."} | верно | XSS лечится контекстным экранированием НА ВЫВОДЕ (Twig autoescape, CSP); валидация ввода не покрывает все контексты вывода. |
T20-L6 0.99 c | Security and OAuth | In the OAuth 2.0 authorization code flow, which parameter arrives at the redirect_uri and is exchanged for an access token? | «authorization_code» Пояснение: In the OAuth 2.0 authorization code flow, the authorization_code parameter is returned to the redirect_uri and then exchanged at the token endpoint for an access token.
Raw{"answer": "authorization_code", "explanation": "In the OAuth 2.0 authorization code flow, the authorization_code parameter is returned to the redirect_uri and then exchanged at the token endpoint for an access token."} | неверно верный: «code» | Параметр code; обмен на токен POST-ом на /token с client_secret. |
T20-L7 1.47 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 typically longer-lived than access tokens and can be used to obtain new access tokens without the user logging in again.
Raw{"answer": "yes", "explanation": "Refresh tokens are typically longer-lived than access tokens and can be used to obtain new access tokens without the user logging in again."} | верно | Стандартная схема OAuth/OIDC: короткий access + длинный refresh. |
T20-L8 1.59 c | Security and OAuth | A password salt must be kept secret: without it the hash cannot be verified. | «no» Пояснение: A salt does not need to be kept secret; it is typically stored alongside the hash to allow verification while preventing rainbow table attacks.
Raw{"answer": "no", "explanation": "A salt does not need to be kept secret; it is typically stored alongside the hash to allow verification while preventing rainbow table attacks."} | верно | Соль хранится открыто (password_hash включает её в строку хеша); секретность соли не нужна. |
T18-L1 1.38 c | Testing: PHPUnit | PHPUnit runs test methods of any class — extending TestCase is not required. | «no» Пояснение: PHPUnit requires test classes to extend PHPUnit's TestCase class to run its test methods.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "PHPUnit requires test classes to extend PHPUnit's TestCase class to run its test methods." ⏎ } | верно | Тестом считается метод класса, наследующего TestCase (PHPUnit 10). |
T18-L2 1.01 c | Testing: PHPUnit | In PHPUnit, setUp() runs once before all tests of the class. | «no» Пояснение: setUp() runs before each individual test method, while setUpBeforeClass() (formerly setUpClass()) runs once before all tests of the class.
Raw{"answer": "no", "explanation": "setUp() runs before each individual test method, while setUpBeforeClass() (formerly setUpClass()) runs once before all tests of the class."} | верно | setUp() — перед КАЖДЫМ тестом; один раз на класс — setUpBeforeClass(). Проверено живым счётчиком на PHPUnit 10.5. |
T18-L3 1.64 c | Testing: PHPUnit | A data provider lets a test run with exactly one set of arguments. | «no» Пояснение: A data provider can provide multiple sets of arguments for a test.
Raw{"answer":"no","explanation":"A data provider can provide multiple sets of arguments for a test."} | верно | Наоборот: наборов может быть сколько угодно — тест выполняется по разу на каждый. Проверено на PHPUnit 10.5 (#[DataProvider]). |
T18-L4 5.67 c | Testing: PHPUnit | Which PHPUnit method declares an expectation that an exception of a given class is thrown? | «expectexception» Пояснение: The PHPUnit method expectException() declares that an exception of the given class is expected to be thrown.
Raw{ ⏎ "answer": "expectException", ⏎ "explanation": "The PHPUnit method expectException() declares that an exception of the given class is expected to be thrown." ⏎ } | верно | $this->expectException(\LogicException::class); проверено на PHPUnit 10.5. |
T18-L5 0.98 c | Testing: PHPUnit | In PHPUnit, a stub verifies which methods were called on it, while a mock only returns data. | «no» Пояснение: In PHPUnit, a mock verifies method calls, while a stub primarily returns predefined data without verification.
Raw{"answer": "no", "explanation": "In PHPUnit, a mock verifies method calls, while a stub primarily returns predefined data without verification."} | верно | Наоборот: стаб подставляет данные, мок проверяет взаимодействия (createStub/createMock); docs PHPUnit — Test Doubles. |
T18-L6 1.15 c | Testing: PHPUnit | In PHPUnit 10+, the recommended way to pass data to a test is the #[DataProvider] attribute (the @dataProvider annotation is deprecated). | «yes» Пояснение: In PHPUnit 10+, the #[DataProvider] attribute is the recommended and supported way to provide data for tests, while the legacy @dataProvider docblock annotation is deprecated.
Raw{"answer": "yes", "explanation": "In PHPUnit 10+, the #[DataProvider] attribute is the recommended and supported way to provide data for tests, while the legacy @dataProvider docblock annotation is deprecated."} | верно | Аннотация ещё парсится в PHPUnit 10/11 (AnnotationParser в 10.5.66), удаление — в 12; атрибут — стандарт. |
T18-L7 1.61 c | Testing: PHPUnit | PHPUnit does not allow one test to depend on the result of another. | «yes» Пояснение: PHPUnit is designed around the principle of test independence, explicitly forbidding one test from depending on the result or execution order of another.
Raw{"answer": "yes", "explanation": "PHPUnit is designed around the principle of test independence, explicitly forbidding one test from depending on the result or execution order of another."} | неверно верный: «no» | Зависимости есть: #[Depends] — зависимый тест не запустится, еслиProducer упал. |
T18-L8 226.71 c | Testing: PHPUnit | Which PHPUnit command-line option makes tests run in random order? | «— (нет ответа)» | не разобрано верный: «--order-by=random» парсинг: нет | --order-by=random (PHPUnit 9+); опция есть в --help PHPUnit 10.5 (проектная). |
T01-L9 4.37 c | Syntax and operators | What does this code output?
```php
echo intdiv(7, 2) . intdiv(-7, 2);
``` | «3-3» Пояснение: intdiv(7, 2) is 3 and intdiv(-7, 2) is -3, concatenated into the string "3-3".
Raw{"answer": "3-3", "explanation": "intdiv(7, 2) is 3 and intdiv(-7, 2) is -3, concatenated into the string \"3-3\"."} | верно | intdiv truncates toward zero: intdiv(-7, 2) = -3, not -4. |
T01-L10 2.79 c | Syntax and operators | What does this code output?
```php
echo -3 ** 2;
``` | «-9» Пояснение: In PHP, the exponentiation operator ** has higher precedence than the unary minus operator, so this is equivalent to -(3 ** 2).
Raw{ ⏎ "answer": -9, ⏎ "explanation": "In PHP, the exponentiation operator ** has higher precedence than the unary minus operator, so this is equivalent to -(3 ** 2)." ⏎ } | верно | ** is right-associative and binds tighter than unary minus: -(3²). |
T02-L9 84.77 c | Types and comparisons | What does this code output?
```php
echo '1e1' == '10' ? 'true' : 'false';
``` | «true» Пояснение: Both operands are numeric strings, so PHP's loose comparison treats them as numbers, and 1e1 equals 10.
Raw{"answer": "true", "explanation": "Both operands are numeric strings, so PHP's loose comparison treats them as numbers, and 1e1 equals 10."} | верно | Both strings are numeric — compared as numbers: 10 == 10. |
T02-L10 58.81 c | Types and comparisons | What does this code output?
```php
switch ('a') {
case 0: echo 'zero'; break;
default: echo 'other';
}
``` | «other» Пояснение: Assuming current PHP (8+), the non-numeric string 'a' is not treated as 0, so the default case executes.
Raw{"answer": "other", "explanation": "Assuming current PHP (8+), the non-numeric string 'a' is not treated as 0, so the default case executes."} | верно | PHP 8: 'a' == 0 → false (used to be true) — default fires. |
T03-L9 61.76 c | Strings | What does this code output?
```php
echo strtr('abc', ['a' => '1', 'ab' => '2']);
``` | «2c» Пояснение: strtr with an associative array replaces the longest matching key first, so 'ab' becomes '2'.
Raw{"answer": "2c", "explanation": "strtr with an associative array replaces the longest matching key first, so 'ab' becomes '2'."} | верно | strtr with an array prefers the longest matching key. |
T03-L10 1.55 c | Strings | What does this code output?
```php
echo '[' . substr('hello', -10) . ']';
``` | «[hello]» Пояснение: A negative start of -10 is beyond the beginning of 'hello', so substr returns the entire string.
Raw{ ⏎ "answer": "[hello]", ⏎ "explanation": "A negative start of -10 is beyond the beginning of 'hello', so substr returns the entire string." ⏎ } | верно | A negative start beyond the string is clamped to the beginning. |
T04-L9 1.38 c | Arrays | What does this code output?
```php
$a = ['k' => 1, 'n' => 2];
$b = ['k' => 9, 'm' => 3];
echo implode(',', array_keys($a + $b));
``` | «k,n,m» Пояснение: The + operator merges the arrays while preserving left-array values, resulting in keys k, n, and m.
Raw{"answer": "k,n,m", "explanation": "The + operator merges the arrays while preserving left-array values, resulting in keys k, n, and m."} | верно | The + operator: on duplicate string keys the left array wins. |
T04-L10 3.15 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» Пояснение: The array is sorted by each sub-array's third element, producing rows in the order y, x, z.
Raw{ ⏎ "answer": "yxz", ⏎ "explanation": "The array is sorted by each sub-array's third element, producing rows in the order y, x, z." ⏎ } | верно | Sorts are stable since 8.0: x and z keep their order on a tie. |
T05-L10 2.61 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 array passes named arguments, assigning $b = 1 and $a = 5, so $a - $b is 5 - 1.
Raw{"answer": 4, "explanation": "The spread array passes named arguments, assigning $b = 1 and $a = 5, so $a - $b is 5 - 1."} | верно | String keys of a spread array become named arguments. |
T05-L9 20.63 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» Пояснение: $f = $p->g(...) creates a first-class callable bound to the P object's g method, and the callable retains the object even after $p = null, so it returns 3.
Raw{ ⏎ "answer": 3, ⏎ "explanation": "$f = $p->g(...) creates a first-class callable bound to the P object's g method, and the callable retains the object even after $p = null, so it returns 3." ⏎ } | верно | First-class callable syntax binds $this at creation time. |
T06-L9 1.17 c | OOP: classes and inheritance | What does this code output?
```php
class A
{
public function who(): string { return static::class; }
}
class B extends A {}
echo (new B)->who();
``` | «b» Пояснение: static::class uses late static binding and returns the class of the object that called the method.
Raw{"answer": "B", "explanation": "static::class uses late static binding and returns the class of the object that called the method."} | верно | Late static binding: static::class is the receiver's class. |
T06-L10 16.19 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 doubles the assigned value, and assignment inside the hook writes to the property's internal storage without re-invoking the setter.
Raw{ ⏎ "answer": 10, ⏎ "explanation": "The set hook doubles the assigned value, and assignment inside the hook writes to the property's internal storage without re-invoking the setter." ⏎ } | верно | Inside the set hook, $this->x writes the backing store (no recursion): 5*2. |
T07-L9 2.54 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 is chosen for f() via insteadof, while TA::f is aliased to g().
Raw{ ⏎ "answer": "BA", ⏎ "explanation": "TB::f is chosen for f() via insteadof, while TA::f is aliased to g()." ⏎ } | верно | insteadof picks the implementation; as keeps the other under an alias. |
T07-L10 7.77 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 separate static property, so CY::$n is not affected by changing CX::$n.
Raw{"answer": 0, "explanation": "Each class that uses a trait gets its own separate static property, so CY::$n is not affected by changing CX::$n."} | верно | A trait's static property is copied into each consuming class. |
T08-L10 3.05 c | Exceptions and errors | What does this code output?
```php
function f(): int
{
try { return 1; } finally { return 2; }
}
echo f();
``` | «2» Пояснение: A return statement inside the finally block overrides the return value from the try block.
Raw{"answer": 2, "explanation": "A return statement inside the finally block overrides the return value from the try block."} | верно | A return in finally overrides the return from try. |
T08-L9 2.45 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 LogicException thrown in the finally block replaces the RuntimeException, and it is caught by the outer catch(LogicException) handler, which echoes 'second'.
Raw{"answer": "second", "explanation": "The LogicException thrown in the finally block replaces the RuntimeException, and it is caught by the outer catch(LogicException) handler, which echoes 'second'."} | верно | An exception from finally replaces the in-flight one — the last thrown is caught. |
T09-L9 12.11 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 imported alias Baz::class resolves to App\Foo, while \Baz::class refers to the global class name Baz.
Raw{ ⏎ "answer": "App\\Foo|Baz", ⏎ "explanation": "The imported alias Baz::class resolves to App\\Foo, while \\Baz::class refers to the global class name Baz." ⏎ } | верно | The use alias applies to unqualified names; a leading \ escapes to the global scope. |
T09-L10 4.62 c | Namespaces and autoloading | What does this code output?
```php
namespace Ns;
class Foo {}
$c = 'Foo';
echo (class_exists($c) ? 'yes' : 'no')
. (class_exists(__NAMESPACE__ . '\\' . $c) ? 'yes' : 'no');
``` | «yesyes» Пояснение: Both class_exists checks find the class Foo in the current Ns namespace.
Raw{ ⏎ "answer": "yesyes", ⏎ "explanation": "Both class_exists checks find the class Foo in the current Ns namespace." ⏎ } | неверно верный: «noyes» | Dynamic names are not resolved against the namespace — 'Foo' is the global class. |
T10-L9 1.59 c | References and scope | What does this code output?
```php
$a = [1, 2, 3];
foreach ($a as &$v) {}
$v = 99;
echo implode(',', $a);
``` | «1,2,99» Пояснение: The foreach loop leaves $v as a reference to the last array element, so assigning to $v changes that element to 99.
Raw{"answer": "1,2,99", "explanation": "The foreach loop leaves $v as a reference to the last array element, so assigning to $v changes that element to 99."} | верно | After a by-ref foreach, $v remains a reference to the last element. |
T10-L10 3.06 c | References and scope | What does this code output?
```php
class A
{
public function inc(): int
{
static $n = 0;
return ++$n;
}
}
class B extends A {}
$a = new A;
$b = new B;
$a->inc();
$b->inc();
echo $a->inc();
``` | «3» Пояснение: The static variable in the inherited method is shared across both objects, so it increments three times.
Raw{ ⏎ "answer": 3, ⏎ "explanation": "The static variable in the inherited method is shared across both objects, so it increments three times." ⏎ } | верно | A method's static variable belongs to the parent's method — subclasses share it. |
T11-L9 2.1 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 10 + 1, so getReturn() outputs 11.
Raw{ ⏎ "answer": 11, ⏎ "explanation": "send(10) assigns 10 to $x, then the generator returns 10 + 1, so getReturn() outputs 11." ⏎ } | верно | send() resumes the generator: $x = 10, return 10+1. |
T11-L10 13.92 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 forwards the values yielded by inner (1 and 2) and returns inner's explicit return value ('ok'), which outer then yields.
Raw{"answer":"1,2,ok","explanation":"yield from forwards the values yielded by inner (1 and 2) and returns inner's explicit return value ('ok'), which outer then yields."} | неверно верный: «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 2.76 c | Configuration and security | What does this code output?
```php
$hash = password_hash('x', PASSWORD_BCRYPT, ['cost' => 4]);
echo password_needs_rehash($hash, PASSWORD_BCRYPT, ['cost' => 4]) ? 'yes' : 'no';
echo password_needs_rehash($hash, PASSWORD_BCRYPT, ['cost' => 5]) ? 'yes' : 'no';
``` | «noyes» Пояснение: The first call returns false because the hash uses the same bcrypt cost, and the second returns true because a higher cost requires rehashing.
Raw{"answer":"noyes","explanation":"The first call returns false because the hash uses the same bcrypt cost, and the second returns true because a higher cost requires rehashing."} | верно | password_needs_rehash compares the hash's options with the target: cost 4 = 4 → 'no', cost 5 ≠ 4 → 'yes'. |
T12-L10 246.02 c | Configuration and security | What does this code output on PHP 8.5?
```php
echo (E_ALL & 2048) === 0 ? 'strict-out' : 'strict-in';
``` | «strict-in» Пояснение: On PHP 8.5, the 2048 bit (E_COMPILE_ERROR) is included in E_ALL, so the bitwise AND is non-zero.
Raw{"answer": "strict-in", "explanation": "On PHP 8.5, the 2048 bit (E_COMPILE_ERROR) is included in E_ALL, so the bitwise AND is non-zero."} | неверно верный: «strict-out» | Since PHP 8.4, E_STRICT is out of E_ALL: the 2048 bit is unset → 'strict-out' (2048 is the historical E_STRICT bit). |
T13-L9 44.2 c | Symfony | What does this code output?
```php
use Symfony\Component\HttpFoundation\Request;
$r = Request::create('/demo', 'GET', [], [], [], ['HTTP_X_TOKEN' => 'abc']);
echo $r->headers->get('X-Token') === 'abc' ? 'mapped' : 'missing';
``` | «missing» Пояснение: The sixth argument in Request::create is the contents parameter, not the headers parameter, so the X-Token header is not set.
Raw{ ⏎ "answer": "missing", ⏎ "explanation": "The sixth argument in Request::create is the contents parameter, not the headers parameter, so the X-Token header is not set." ⏎ } | неверно верный: «mapped» | The literal comparison requires knowing the mapping: HttpFoundation turns HTTP_X_TOKEN into the X-Token header (case-insensitive); without it the answer is 'missing'. |
T13-L10 197.45 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;
``` | «cba» Пояснение: Symfony listeners are invoked in ascending priority order, so C (5), B (10), then A with the default priority of 100.
Raw{"answer": "CBA", "explanation": "Symfony listeners are invoked in ascending priority order, so C (5), B (10), then A with the default priority of 100."} | неверно верный: «bca» | Listeners run by descending priority: 10 (B), 5 (C), 0 (A). |
T14-L10 2.82 c | Doctrine | Given: Doctrine ORM 3, an EntityManager on in-memory SQLite, entity User with an auto-increment primary key. The users table is empty. What does this code output?
```php
$u = new User(name: 'A');
$em->persist($u);
$em->flush();
$a = $em->find(User::class, $u->getId());
$b = $em->find(User::class, $u->getId());
echo spl_object_id($a) === spl_object_id($b) ? 'same' : 'diff';
``` | «same» Пояснение: Doctrine's identity map returns the existing loaded entity for the same ID from the same EntityManager, so both find calls return the same object instance.
Raw{ ⏎ "answer": "same", ⏎ "explanation": "Doctrine's identity map returns the existing loaded entity for the same ID from the same EntityManager, so both find calls return the same object instance." ⏎ } | верно | Identity map: a second find for the same id returns the same instance. |
T14-L9 3.3 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» Пояснение: The entity is persisted and then removed before any flush, so the auto-increment insert never executes and nothing is inserted into the users table.
Raw```json ⏎ {"answer": 0, "explanation": "The entity is persisted and then removed before any flush, so the auto-increment insert never executes and nothing is inserted into the users table."} ⏎ ``` | верно | The unit of work schedules INSERT at flush: remove after persist cancels it. |
T15-L10 0.97 c | PostgreSQL | What does this SQL query return (PostgreSQL 17)?
```sql
CREATE TEMP TABLE t (x int);
INSERT INTO t VALUES (1), (NULL);
SELECT count(x) FROM t;
``` | «1» Пояснение: COUNT(x) counts only non-NULL values in column x.
Raw{"answer": 1, "explanation": "COUNT(x) counts only non-NULL values in column x."} | верно | count(column) skips NULLs; count(*) would return 2. |
T15-L9 2.41 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 sum produces cumulative totals 10, 30, and 60, which are concatenated with commas.
Raw{ ⏎ "answer": "10,30,60", ⏎ "explanation": "The window sum produces cumulative totals 10, 30, and 60, which are concatenated with commas." ⏎ } | верно | With ORDER BY the default window frame is running (start to current row). |
T16-L9 81.15 c | Symfony: Messenger | What does this code output?
```php
use Symfony\Component\Messenger\MessageBus;
use Symfony\Component\Messenger\Middleware\MiddlewareInterface;
use Symfony\Component\Messenger\Middleware\StackInterface;
use Symfony\Component\Messenger\Envelope;
final class Trace implements MiddlewareInterface
{
public function __construct(private string $tag) {}
public function handle(Envelope $e, StackInterface $stack): Envelope
{
echo $this->tag;
return $stack->next()->handle($e, $stack);
}
}
$bus = new MessageBus([new Trace('M1'), new Trace('M2')]);
$bus->dispatch(new Envelope(new stdClass()));
``` | «m1m2» Пояснение: The two middlewares run in constructor order and echo their tags before the missing next middleware would throw.
Raw{"answer": "M1M2", "explanation": "The two middlewares run in constructor order and echo their tags before the missing next middleware would throw."} | верно | The first-added middleware runs first (outermost). |
T16-L10 17.88 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» Пояснение: Both handlers registered for Ping are invoked, so $n increases by 1 and then by 10.
Raw{ ⏎ "answer": 11, ⏎ "explanation": "Both handlers registered for Ping are invoked, so $n increases by 1 and then by 10." ⏎ } | верно | All registered handlers of the message run: 1 + 10 = 11. |
T17-L9 1.46 c | PostgreSQL: transactions and indexes | What does this SQL query return (PostgreSQL 17)?
```sql
CREATE TEMP TABLE t (a int);
CREATE UNIQUE INDEX ON t (a);
INSERT INTO t VALUES (1) ON CONFLICT DO NOTHING;
INSERT INTO t VALUES (1) ON CONFLICT DO NOTHING;
SELECT count(*) FROM t;
``` | «1» Пояснение: The first insert succeeds and the second is ignored due to the unique index conflict.
Raw{ ⏎ "answer": 1, ⏎ "explanation": "The first insert succeeds and the second is ignored due to the unique index conflict." ⏎ } | верно | ON CONFLICT DO NOTHING skips the duplicate: one insert. |
T17-L10 2.94 c | PostgreSQL: transactions and indexes | What does this sequence of psql commands output?
```sql
BEGIN;
CREATE TEMP TABLE t (a int, UNIQUE (a) DEFERRABLE INITIALLY DEFERRED);
INSERT INTO t VALUES (1);
INSERT INTO t VALUES (1);
SELECT count(*) FROM t;
``` | «2» Пояснение: Because the unique constraint is DEFERRABLE INITIALLY DEFERRED, both duplicate inserts are allowed until COMMIT, so SELECT count(*) returns 2.
Raw{"answer": 2, "explanation": "Because the unique constraint is DEFERRABLE INITIALLY DEFERRED, both duplicate inserts are allowed until COMMIT, so SELECT count(*) returns 2."} | верно | DEFERRED postpones the uniqueness check to COMMIT — count sees 2 rows. |
T18-L9 60.82 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 unanchored --filter regex matches both test_sum and test_sum_abs, and each data-provider method contributes three test variants.
Raw{ ⏎ "answer": 6, ⏎ "explanation": "The unanchored --filter regex matches both test_sum and test_sum_abs, and each data-provider method contributes three test variants." ⏎ } | верно | --filter is a substring match: test_sum also matches test_sum_abs (3+3 datasets). |
T18-L10 7.52 c | Testing: PHPUnit | How many tests will this command run, and how many of them will fail? Answer with two comma-separated numbers (ran, failed).
```php
use PHPUnit\Framework\TestCase;
use PHPUnit\Framework\Attributes\DataProvider;
final class Calc2Test extends TestCase
{
public function prov(): array
{
return [[1], [-1]];
}
#[DataProvider('prov')]
public function test_x(int $x): void
{
$this->assertTrue($x > 0);
}
}
```
Command: `phpunit Calc2Test.php` (PHPUnit 10.5) | «2, 1» Пояснение: The data provider yields two datasets, $x=1 and $x=-1, and only the negative case fails assertTrue($x > 0).
Raw{ ⏎ "answer": "2, 1", ⏎ "explanation": "The data provider yields two datasets, $x=1 and $x=-1, and only the negative case fails assertTrue($x > 0)." ⏎ } | верно | A non-static provider is just a deprecation in PHPUnit 10: both datasets run and the [-1] dataset fails the assert — 2 ran, 1 failure. |
T19-L9 0.87 c | HTTP and REST API | Which HTTP method does this command send?
```bash
curl -s -d 'a=1' http://demo.local/api
``` | «post» Пояснение: curl's -d option sends the data in the body using POST by default.
Raw{"answer":"POST","explanation":"curl's -d option sends the data in the body using POST by default."} | верно | -d/-F switches curl to POST by default. |
T19-L10 0.83 c | HTTP and REST API | Which HTTP method does this command send?
```bash
curl -s -G -d 'a=1' http://demo.local/api
``` | «get» Пояснение: curl -G makes -d send the data as a query string with a GET request.
Raw{"answer": "GET", "explanation": "curl -G makes -d send the data as a query string with a GET request."} | верно | -G turns -d data into the query string; the method stays GET. |
T20-L9 3.29 c | Security and OAuth | A client hits the token endpoint (RFC 6749) with a non-existent client_id. What value of the error field does the endpoint return? | «invalid_client» Пояснение: Per RFC 6749 Section 4.1.2.3, when the authorization server does not recognize the client_id provided in the token request, it returns the error value 'invalid_client'.
Raw{"answer": "invalid_client", "explanation": "Per RFC 6749 Section 4.1.2.3, when the authorization server does not recognize the client_id provided in the token request, it returns the error value 'invalid_client'."} | верно | Unknown client → invalid_client (RFC 6749 §5.2). |
T20-L10 5.03 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 grant (response_type=token), the authorization server returns the access token in the fragment part of the redirect_uri.
Raw{ ⏎ "answer": "fragment", ⏎ "explanation": "In the OAuth 2.0 implicit grant (response_type=token), the authorization server returns the access token in the fragment part of the redirect_uri." ⏎ } | верно | The implicit flow passes the token in the URL fragment (#) — it never reaches the server. |
T21-L9 18.43 c | Twig | What does this Twig template output?
```twig
{{ false|default(2) * 3 }}
``` | «6» Пояснение: The false value triggers the default filter to return 2, which is then multiplied by 3.
Raw{"answer": 6, "explanation": "The false value triggers the default filter to return 2, which is then multiplied by 3."} | верно | default replaces exactly false/null/''/[] — false becomes 2, 2*3 = 6; the naive 'default is for undefined only' yields 0. |
T21-L10 280.87 c | Twig | What exception class does render() of this template throw?
```twig
{{ 'a' ~ 1 + 2 }}
``` | «— (нет ответа)» | не разобрано верный: «runtimeerror» парсинг: нет | In Twig ~ binds tighter than +: ('a' ~ 1) + 2 → string + int → a render error (RuntimeError). |
T22-L9 27.62 c | Symfony: Security and forms | What does this code output?
```php
use Symfony\Component\Validator\Validation;
use Symfony\Component\Validator\Constraints as Assert;
$v = Validation::createValidator();
echo count($v->validate([''], [new Assert\NotBlank()]));
``` | «1» Пояснение: The empty string element violates the listable NotBlank constraint, producing one violation.
Raw{ ⏎ "answer": 1, ⏎ "explanation": "The empty string element violates the listable NotBlank constraint, producing one violation." ⏎ } | неверно верный: «0» | NotBlank treats null, '', [] as blank — the array [''] is not blank. |
T22-L10 280.12 c | Symfony: Security and forms | What does this code output?
```php
use Symfony\Component\Form\Forms;
use Symfony\Component\Form\Extension\Core\Type\TextType;
$factory = Forms::createFormFactoryBuilder()->getFormFactory();
$form = $factory->create(TextType::class);
try {
echo $form->isValid() ? 'valid' : 'invalid';
} catch (Throwable $e) {
echo get_class($e);
}
``` | «— (нет ответа)» | не разобрано верный: «symfony\component\form\exception\logicexception» парсинг: нет | isValid() on a non-submitted form throws LogicException, it does not return false. |
T23-L9 10.09 c | Symfony: configuration and services | What does this code output?
```php
use Symfony\Component\DependencyInjection\ContainerBuilder;
$c = new ContainerBuilder();
$c->register('a', stdClass::class)->setPublic(true);
$c->compile();
echo spl_object_id($c->get('a')) === spl_object_id($c->get('a')) ? 'same' : 'diff';
``` | «same» Пояснение: Symfony's container caches the instantiated service, so both calls to get('a') return the same object.
Raw{ ⏎ "answer": "same", ⏎ "explanation": "Symfony's container caches the instantiated service, so both calls to get('a') return the same object." ⏎ } | верно | Container services are shared: two get() calls yield one instance. |
T23-L10 128.86 c | Symfony: configuration and services | What does this code output?
```php
use Symfony\Component\DependencyInjection\ContainerBuilder;
$c = new ContainerBuilder();
$c->setParameter('name', 'Bob');
$c->setParameter('greeting', 'hi %name%');
$c->setParameter('message', '%greeting%!');
$c->compile();
echo $c->getParameter('message');
``` | «hi bob» Пояснение: Symfony resolves the parameter placeholder to the value of the already resolved 'greeting' parameter.
Raw{"answer": "hi Bob", "explanation": "Symfony resolves the parameter placeholder to the value of the already resolved 'greeting' parameter."} | неверно верный: «hi bob!» | compile() resolves %-references transitively: %greeting% → 'hi %name%' → 'hi Bob!', the answer assembles over two hops. |
T24-L9 4.94 c | Bootstrap | What is the max-width of .container in Bootstrap 5.3 at a 992px viewport? | «992px» Пояснение: Bootstrap 5.3 sets .container's max-width to 992px at the 992px and above breakpoint.
Raw{ ⏎ "answer": "992px", ⏎ "explanation": "Bootstrap 5.3 sets .container's max-width to 992px at the 992px and above breakpoint." ⏎ } | неверно верный: «960» | 5.x container widths: 540/720/960/1140/1320 (sm–xxl); 992 → 960px. |
T24-L10 7.92 c | Bootstrap | Which utility sets the text color in Bootstrap 5.3 for `<p class="text-danger text-primary">…</p>`? Answer with the winning class name. | «text-danger» Пояснение: In Bootstrap 5.3, the .text-danger rule is declared after .text-primary, so it wins the cascade.
Raw{"answer":"text-danger","explanation":"In Bootstrap 5.3, the .text-danger rule is declared after .text-primary, so it wins the cascade."} | верно | Specificity ties — the later rule wins: text-danger is declared after text-primary. |
T25-L9 5.25 c | Clean architecture | Layers: Domain, Application, Infrastructure. Deptrac rules: Application → Domain; Infrastructure → Domain, Application; Domain → Domain only.
How many violations will deptrac report for this class?
```php
namespace App\Domain;
use App\Application\PlaceOrder;
use App\Infrastructure\Db;
class OrderService
{
public function __construct(
private PlaceOrder $handler,
private Db $db,
) {}
}
``` | «2» Пояснение: The Domain class depends on both Application and Infrastructure, violating the Domain → Domain-only rule twice.
Raw{ ⏎ "answer": 2, ⏎ "explanation": "The Domain class depends on both Application and Infrastructure, violating the Domain → Domain-only rule twice." ⏎ } | верно | Domain may depend only on Domain: PlaceOrder (Application) + Db (Infrastructure) = 2. |
T25-L10 2.82 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 BillingService class is in the Domain layer, which may only depend on Domain. It depends on PlaceOrder (Application) and Db + Logger (Infrastructure), giving 3 violations.
Raw{ ⏎ "answer": 3, ⏎ "explanation": "The BillingService class is in the Domain layer, which may only depend on Domain. It depends on PlaceOrder (Application) and Db + Logger (Infrastructure), giving 3 violations." ⏎ } | верно | The inline FQCN \App\Infrastructure\Logger counts too: Application + Db + Logger = 3. |
T26-L10 10.69 c | DDD | What does this code output?
```php
final class Money
{
public function __construct(public readonly int $amount) {}
public function add(Money $o): Money
{
return new self($this->amount + $o->amount);
}
}
$a = new Money(10);
$c = $a->add(new Money(5));
echo $a->amount . ',' . $c->amount;
``` | «10,15» Пояснение: The readonly amount is assigned in the constructor and $c receives the sum of 10 and 5.
Raw{"answer": "10,15", "explanation": "The readonly amount is assigned in the constructor and $c receives the sum of 10 and 5."} | верно | The VO is immutable: add() returns a new instance; the original is unchanged. |
T26-L9 10.94 c | DDD | What does this code output?
```php
final class Order
{
private array $items = [];
public function add(string $sku): void
{
$this->items[$sku] = true;
}
public function count(): int
{
return count($this->items);
}
public function remove(string $sku): void
{
if (count($this->items) === 1) {
throw new DomainException('last item');
}
unset($this->items[$sku]);
}
}
$o = new Order;
$o->add('a');
try {
$o->remove('a');
} catch (DomainException) {
}
echo $o->count();
``` | «1» Пояснение: remove() throws a DomainException before unsetting 'a' because count is 1, the exception is caught, and the item remains, so count() returns 1.
Raw{"answer":"1","explanation":"remove() throws a DomainException before unsetting 'a' because count is 1, the exception is caught, and the item remains, so count() returns 1."} | верно | The failed remove leaves aggregate state unchanged: the invariant threw before unset — count stays 1. |
VC-L9 12.64 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 method returns the string 'hi' and echo prints it.
Raw{ ⏎ "answer": "hi", ⏎ "explanation": "The method returns the string 'hi' and echo prints it." ⏎ } | верно | Since 8.4, new in a method chain works without wrapping parentheses. |
VC-L10 64.55 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» Пояснение: Reading a property on an uninitialized lazy ghost triggers its initializer, so the second check is no.
Raw{ ⏎ "answer": "yesno", ⏎ "explanation": "Reading a property on an uninitialized lazy ghost triggers its initializer, so the second check is no." ⏎ } | верно | newLazyGhost (8.4): the object stays lazy until first access — reading a property initializes it and clears the flag. |
T28-L9 19.15 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» Пояснение: AbstractGuardAuthenticator was deprecated in Symfony 6.3 and removed in Symfony 7.0, so it no longer exists in 8.1 and class_exists returns false.
Raw{"answer":"no","explanation":"AbstractGuardAuthenticator was deprecated in Symfony 6.3 and removed in Symfony 7.0, so it no longer exists in 8.1 and class_exists returns false."} | верно | Guard authentication was removed in Symfony 7.0 — the class is gone in 8.1. |
T28-L10 260.07 c | Symfony: versions | The project was upgraded from Symfony 6.4 to 8.1. What does this code output on 8.1?
```php
echo class_exists(\Symfony\Component\Routing\Loader\AnnotationClassLoader::class)
? 'yes' : 'no';
echo class_exists(\Symfony\Component\Routing\Loader\AttributeClassLoader::class)
? 'yes' : 'no';
``` | «noyes» Пояснение: Symfony 8.1 no longer ships the annotation class loader but still ships the attribute class loader, so the checks are false then true.
Raw{"answer": "noyes", "explanation": "Symfony 8.1 no longer ships the annotation class loader but still ships the attribute class loader, so the checks are false then true."} | верно | Annotation loaders were removed in 7.0; only attribute loaders remain (Annotation→Attribute). |