Пример запроса (первая клетка). System одинаковый во всех запросах прогона, user — свой вопрос для каждой клетки:
| Клетка | Тема | Утверждение | Ответ |
Результат | Обоснование |
T01-L1 3.0 c | Syntax and operators | Double-quoted and single-quoted strings are processed identically; the difference is only in speed. | «no» Пояснение: Single-quoted strings do not interpolate variables or process most escape sequences, while double-quoted strings do.
Raw{"answer": "no", "explanation": "Single-quoted strings do not interpolate variables or process most escape sequences, while double-quoted strings do."} | верно | В двойных кавычках работают интерполяция переменных и escape-последовательности, в одинарных — нет. |
T01-L2 1.03 c | Syntax and operators | The ?? operator follows isset semantics and raises no warnings for undefined variables. | «yes» Пояснение: PHP's null coalescing operator (??) uses isset-like semantics and does not raise warnings for undefined variables.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "PHP's null coalescing operator (??) uses isset-like semantics and does not raise warnings for undefined variables." ⏎ } | верно | ?? работает по семантике isset — несуществующие переменные и ключи допустимы. |
T01-L3 0.88 c | Syntax and operators | What will this print: echo 'a', 'b'; | «ab» Пояснение: PHP's echo outputs its arguments consecutively when separated by commas.
Raw{"answer": "ab", "explanation": "PHP's echo outputs its arguments consecutively when separated by commas."} | верно | echo принимает список аргументов: ab. |
T01-L4 3.88 c | Syntax and operators | print returns the value 1 and can be used inside an expression. | «yes» Пояснение: In PHP, print returns 1 and can be used inside an expression.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "In PHP, print returns 1 and can be used inside an expression." ⏎ } | верно | print — выражение со значением 1, в отличие от echo, который значения не возвращает. |
T01-L5 1.62 c | Syntax and operators | The ?: (elvis) operator returns its left operand when it is falsy. | «no» Пояснение: The elvis operator returns its right operand when its left operand is falsy.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "The elvis operator returns its right operand when its left operand is falsy." ⏎ } | верно | Наоборот: $a ?: $b возвращает $a, если он истинный, иначе $b. |
T01-L6 221.49 c | Syntax and operators | In PHP 8, the concatenation operator (.) has lower precedence than addition and subtraction. | «yes» Пояснение: In PHP, the concatenation operator has lower precedence than addition and subtraction, so "a" . 1 + 2 becomes "a" . 3.
Raw{"answer":"yes","explanation":"In PHP, the concatenation operator has lower precedence than addition and subtraction, so \"a\" . 1 + 2 becomes \"a\" . 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» Пояснение: The ** operator in PHP 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": "The ** operator in PHP 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.43 c | Syntax and operators | What string will this print: echo 'sum: ' . 2 + 3; (PHP 8)? | «— (нет ответа)» | не разобрано верный: «sum: 5» парсинг: нет | Парная к verify-клетке про приоритет: 'сумма: 5'. |
T02-L1 2.68 c | Types and comparisons | With strict comparison (===), arrays are considered equal regardless of element order. | «no» Пояснение: PHP's === compares arrays only if they have identical keys and values in the same order.
Raw{"answer": "no", "explanation": "PHP's === compares arrays only if they have identical keys and values in the same order."} | верно | === для массивов требует совпадения и значений, и их порядка. |
T02-L2 1.69 c | Types and comparisons | The comparison 0 == false returns false because it is a strict comparison. | «no» Пояснение: The == operator is a loose comparison, and 0 == false returns true because false is compared as 0.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "The == operator is a loose comparison, and 0 == false returns true because false is compared as 0." ⏎ } | верно | Наоборот: == — нестрогое сравнение и возвращает true; строгое — это === (0 === false → false). |
T02-L3 3.01 c | Types and comparisons | In PHP 8, the expression "abc" == 0 returns true. | «no» Пояснение: In PHP 8, the non-numeric string "abc" is not converted to 0, and it is compared as a string to "0", so "abc" == 0 is false.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "In PHP 8, the non-numeric string \"abc\" is not converted to 0, and it is compared as a string to \"0\", so \"abc\" == 0 is false." ⏎ } | верно | С PHP 8 нечисловая строка сравнивается как строка: "abc" == "0" → false (в PHP 7 было true). |
T02-L4 1.73 c | Types and comparisons | Under loose comparison, null equals 0, the empty string, and false at the same time. | «yes» Пояснение: In PHP loose comparison, null == 0, null == '', and null == false are all true.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "In PHP loose comparison, null == 0, null == '', and null == false are all true." ⏎ } | верно | null == 0, null == "" и null == false — все true. |
T02-L5 5.42 c | Types and comparisons | What does the expression (int) '42abc' return? | «42» Пояснение: PHP casts a string to its leading numeric part and ignores the trailing 'abc'.
Raw{"answer": 42, "explanation": "PHP casts a string to its leading numeric part and ignores the trailing 'abc'."} | верно | Ведущая числовая часть: 42, без ошибок и warning. |
T02-L6 0.97 c | Types and comparisons | What does the expression '5' + 5 return? | «10» Пояснение: The string '5' is cast to the number 5, so 5 + 5 equals 10.
Raw{ ⏎ "answer": 10, ⏎ "explanation": "The string '5' is cast to the number 5, so 5 + 5 equals 10." ⏎ } | верно | Числовая строка приводится: int 10. |
T02-L7 0.74 c | Types and comparisons | When cast to string, false becomes "0". | «yes» Пояснение: In PHP, casting the boolean false to a string produces "0".
Raw{"answer":"yes","explanation":"In PHP, casting the boolean false to a string produces \"0\"."} | неверно верный: «no» | false → "", true → "1". |
T02-L8 1.27 c | Types and comparisons | The comparison 0.1 + 0.2 === 0.3 returns false. | «yes» Пояснение: PHP uses binary floating-point arithmetic, so 0.1 + 0.2 is not exactly equal to 0.3.
Raw{"answer": "yes", "explanation": "PHP uses binary floating-point arithmetic, so 0.1 + 0.2 is not exactly equal to 0.3."} | верно | Двоичная погрешность float: 0.1 + 0.2 = 0.30000000000000004. |
T03-L1 1.28 c | Strings | strrev() correctly reverses a UTF-8 string. | «no» Пояснение: strrev() reverses bytes, not characters, so UTF-8 multibyte sequences are usually corrupted.
Raw{"answer": "no", "explanation": "strrev() reverses bytes, not characters, so UTF-8 multibyte sequences are usually corrupted."} | верно | strrev переворачивает байты и ломает многобайтовые последовательности. |
T03-L2 0.75 c | Strings | str_contains('Hello world', 'world') returns true. | «yes» Пояснение: The string 'Hello world' contains the substring 'world'.
Raw{"answer": "yes", "explanation": "The string 'Hello world' contains the substring 'world'."} | верно | str_contains с PHP 8.0 проверяет вхождение подстроки. |
T03-L3 1.57 c | Strings | str_pad() can pad a string on the right side only. | «no» Пояснение: str_pad() can pad on the left, right, or both sides.
Raw{"answer":"no","explanation":"str_pad() can pad on the left, right, or both sides."} | верно | STR_PAD_LEFT / STR_PAD_BOTH меняют сторону дополнения. |
T03-L4 1.18 c | Strings | By default trim() strips only spaces, leaving tabs and newlines intact. | «no» Пояснение: By default, PHP's trim() strips whitespace, including spaces, tabs, and newlines.
Raw{"answer":"no","explanation":"By default, PHP's trim() strips whitespace, including spaces, tabs, and newlines."} | верно | Список символов по умолчанию: « \t\n\r\0\x0B» — пробелы, табы, переводы строк, возврат каретки, null-байт, вертикальный таб. Проверено php -r. |
T03-L5 1.36 c | Strings | How many BYTES does strlen('héllo') return for a UTF-8 string? | «6» Пояснение: The UTF-8 encoding of 'é' takes 2 bytes, while the other four characters take 1 byte each, for a total of 6 bytes.
Raw{"answer": 6, "explanation": "The UTF-8 encoding of 'é' takes 2 bytes, while the other four characters take 1 byte each, for a total of 6 bytes."} | верно | 6 букв по 2 байта: 12. |
T03-L6 0.98 c | Strings | What does substr('abcdef', -3) return? | «def» Пояснение: Starting from offset -3 takes the last three characters of the string.
Raw{"answer": "def", "explanation": "Starting from offset -3 takes the last three characters of the string."} | верно | Отрицательное смещение — с конца: def. |
T03-L7 1.33 c | Strings | ucfirst() modifies the string passed to it in place. | «no» Пояснение: ucfirst() does not modify the string in place; it returns a new string with the first character capitalized.
Raw{"answer":"no","explanation":"ucfirst() does not modify the string in place; it returns a new string with the first character capitalized."} | верно | Строки неизменяемы; ucfirst возвращает новую строку. |
T03-L8 0.9 c | Strings | Variable interpolation works in heredoc but not in nowdoc. | «yes» Пояснение: Heredoc allows variable interpolation while nowdoc treats all content as literal, so variables are not interpolated in nowdoc.
Raw{"answer": "yes", "explanation": "Heredoc allows variable interpolation while nowdoc treats all content as literal, so variables are not interpolated in nowdoc."} | верно | Nowdoc — «одинарные кавычки» в тройном синтаксисе: текст как есть. |
T04-L1 1.28 c | Arrays | The sort() function preserves the key-to-value association of the array. | «no» Пояснение: PHP's sort() reindexes the array and does not preserve key-to-value associations; ksort() or asort() do.
Raw{"answer":"no","explanation":"PHP's sort() reindexes the array and does not preserve key-to-value associations; ksort() or asort() do."} | верно | sort перенумеровывает ключи; связь сохраняет asort. |
T04-L2 1.44 c | Arrays | The string key '5' in an array is stored as the integer 5. | «yes» Пояснение: In PHP, array keys that are valid integer representations (like the string '5') are automatically cast to integers, so $arr['5'] and $arr[5] are the same.
Raw{"answer": "yes", "explanation": "In PHP, array keys that are valid integer representations (like the string '5') are automatically cast to integers, so $arr['5'] and $arr[5] are the same."} | верно | Каноничные десятичные строковые ключи приводятся к int. |
T04-L3 1.1 c | Arrays | The in_array() function uses strict comparison (===) by default. | «no» Пояснение: in_array() uses loose comparison by default unless the strict parameter is set to true.
Raw{"answer": "no", "explanation": "in_array() uses loose comparison by default unless the strict parameter is set to true."} | верно | По умолчанию сравнение нестрогое; строгое — третий аргумент true. |
T04-L4 1.04 c | Arrays | Without a callback, array_filter() removes all "empty" (falsy) elements from the array. | «yes» Пояснение: In PHP, array_filter() without a callback keeps only elements that are truthy and removes falsy values.
Raw{"answer": "yes", "explanation": "In PHP, array_filter() without a callback keeps only elements that are truthy and removes falsy values."} | верно | Убирает 0, "", null, false и пустые массивы. |
T04-L5 1.07 c | Arrays | By default, array_slice() preserves the original numeric keys of the array. | «yes» Пояснение: The preserve_keys parameter of array_slice() defaults to true, which keeps the original indices of the elements in the array.
Raw{"answer": "yes", "explanation": "The preserve_keys parameter of array_slice() defaults to true, which keeps the original indices of the elements in the array."} | неверно верный: «no» | По умолчанию ключи перенумеровываются; сохранение — preserve_keys = true. |
T04-L6 3.46 c | Arrays | What does array_slice([10, 20, 30, 40], 1, 2) return? | «[20, 30]» Пояснение: array_slice() returns the subarray starting at offset 1 with length 2.
Raw{"answer": "[20, 30]", "explanation": "array_slice() returns the subarray starting at offset 1 with length 2."} | верно | [20,30]; ключи перенумеровываются. |
T04-L7 1.12 c | Arrays | How many elements will count(['a' => 1] + ['a' => 9, 'b' => 2]) return? | «2» Пояснение: The + operator merges arrays, with right-array keys overriding left-array keys for matching keys, resulting in two elements.
Raw{"answer": 2, "explanation": "The + operator merges arrays, with right-array keys overriding left-array keys for matching keys, resulting in two elements."} | верно | Оператор + : по ключу 'a' побеждает левый; итого 2. |
T04-L8 4.12 c | Arrays | Since PHP 8.1, the spread operator [...$a, ...$b] supports arrays with string keys. | «yes» Пояснение: PHP 8.1 extended array spread literals to support arrays with string keys.
Raw{"answer":"yes","explanation":"PHP 8.1 extended array spread literals to support arrays with string keys."} | верно | В 8.0 — только числовые ключи; 8.1 снял ограничение. |
T05-L1 103.68 c | Functions and closures | Named arguments cannot be combined with argument unpacking ...$args in a single call. | «no» Пояснение: PHP allows mixing named arguments with ...$args in one call, as long as the named arguments come after the unpacked arguments.
Raw{"answer": "no", "explanation": "PHP allows mixing named arguments with ...$args in one call, as long as the named arguments come after the unpacked arguments."} | верно | Можно: f(...$args, имя: значение). Нельзя только позиционный аргумент после распаковки. |
T05-L2 4.24 c | Functions and closures | An anonymous function without use sees variables from the outer scope. | «no» Пояснение: A PHP closure must capture outer variables with use, except $this is automatically inherited in class context.
Raw{"answer": "no", "explanation": "A PHP closure must capture outer variables with use, except $this is automatically inherited in class context."} | верно | Без use внешние переменные недоступны; авто-захват только у fn. |
T05-L3 1.71 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 actually passed to the function, so f(1, 2, 3) returns 3.
Raw{"answer": 3, "explanation": "func_num_args() returns the number of arguments actually passed to the function, so f(1, 2, 3) returns 3."} | верно | Считает переданные аргументы: 3. |
T05-L4 1.54 c | Functions and closures | The body of an arrow function fn may consist of several expressions in curly braces. | «no» Пояснение: PHP arrow functions have a single-expression body and do not support multiple expressions in curly braces.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "PHP arrow functions have a single-expression body and do not support multiple expressions in curly braces." ⏎ } | верно | fn — всегда одно выражение; блок операторов делает обычная анонимная функция. |
T05-L5 8.59 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) at the time of invocation, as specified in the PHP 8.0 RFC and documentation.
Raw{"answer": "no", "explanation": "PHP arrow functions capture outer variables by value (not by reference) at the time of invocation, as specified in the PHP 8.0 RFC and documentation."} | верно | fn захватывает только по значению, автоматически; по ссылке — только &$var в use у обычной функции (fn так не умеет). |
T05-L6 7.07 c | Functions and closures | A closure declared as static function () {} does not capture $this. | «yes» Пояснение: In PHP, a closure declared as static does not automatically capture the enclosing $this.
Raw{"answer":"yes","explanation":"In PHP, a closure declared as static does not automatically capture the enclosing $this."} | верно | static-замыкание отвязано от объекта: $this внутри недоступен. |
T05-L7 1.25 c | Functions and closures | What will this print: $x = 5; $f = function () use ($x) { return $x; }; $x = 7; echo $f(); | «5» Пояснение: use ($x) copies the value of $x by default, so the closure returns 5 even after $x is changed to 7.
Raw{"answer": 5, "explanation": "use ($x) copies the value of $x by default, so the closure returns 5 even after $x is changed to 7."} | верно | use захватывает по значению в момент создания: 5. |
T05-L8 1.18 c | Functions and closures | In weak typing mode (without strict_types), passing the string "5" to an int parameter is allowed. | «yes» Пояснение: Without strict_types, PHP coerces the numeric string "5" to an integer for an int parameter.
Raw{"answer": "yes", "explanation": "Without strict_types, PHP coerces the numeric string \"5\" to an integer for an int parameter."} | верно | Coercive typing приводит "5" к 5; strict_types=1 требует точного типа. |
T06-L1 0.62 c | OOP: classes and inheritance | PHP supports constructor property promotion: public function __construct(private int $x) {}. | «yes» Пояснение: PHP 8.0 introduced constructor property promotion, allowing parameters to become class properties.
Raw{"answer": "yes", "explanation": "PHP 8.0 introduced constructor property promotion, allowing parameters to become class properties."} | верно | С PHP 8.0 параметр с модификатором создаёт свойство и присваивание. |
T06-L2 1.13 c | OOP: classes and inheritance | Which keyword prevents a method from being overridden in subclasses? | «final» Пояснение: In PHP, the final keyword prevents a method from being overridden in subclasses.
Raw{ ⏎ "answer": "final", ⏎ "explanation": "In PHP, the final keyword prevents a method from being overridden in subclasses." ⏎ } | верно | final. |
T06-L3 0.76 c | OOP: classes and inheritance | A method declared final cannot be overridden in a subclass. | «yes» Пояснение: In PHP, a method declared final cannot be overridden by a subclass.
Raw{"answer": "yes", "explanation": "In PHP, a method declared final cannot be overridden by a subclass."} | верно | final запрещает переопределение метода и наследование класса. |
T06-L4 0.99 c | OOP: classes and inheritance | Parent properties with private visibility are accessible in a subclass. | «no» Пояснение: Private properties in a PHP parent class are not accessible from a subclass.
Raw{"answer": "no", "explanation": "Private properties in a PHP parent class are not accessible from a subclass."} | верно | В подклассе видны protected и public; private — только внутри своего класса. |
T06-L5 157.82 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» Пояснение: get_class(new class {}) returns a generated name whose prefix before the NUL byte is AnonymousClass, followed by the file/path identifier.
Raw{ ⏎ "answer": "AnonymousClass", ⏎ "explanation": "get_class(new class {}) returns a generated name whose prefix before the NUL byte is AnonymousClass, followed by the file/path identifier." ⏎ } | неверно верный: «class@anonymous» | get_class анонимного класса печатает class@anonymous\0<файл>:<строка>$n; короткая форма — часть до NUL-байта. Проверено php -r (hex). |
T06-L6 2.88 c | OOP: classes and inheritance | A private parent method is not part of the inheritance contract: a child may declare a method with the same name and any visibility. | «yes» Пояснение: Private methods are not inherited and do not impose a visibility requirement on similarly named methods in child classes.
Raw{"answer":"true","explanation":"Private methods are not inherited and do not impose a visibility requirement on similarly named methods in child classes."} | верно | private-члены не наследуются — правила совместимости подписей не действуют. |
T06-L7 2.59 c | OOP: classes and inheritance | The magic method __get() is called only for non-existent properties. | «no» Пояснение: __get() is also called for inaccessible properties, not only non-existent ones.
Raw{"answer": "no", "explanation": "__get() is also called for inaccessible properties, not only non-existent ones."} | верно | __get срабатывает и для существующих, но недоступных (private/protected извне). |
T06-L8 2.08 c | OOP: classes and inheritance | What does reassigning a readonly property throw — Exception or Error? | «error» Пояснение: Attempting to reassign a readonly property in PHP throws an Error, not an Exception.
Raw{"answer": "Error", "explanation": "Attempting to reassign a readonly property in PHP throws an Error, not an Exception."} | верно | Error (readonly с 8.1); оговорка: в __clone() переинициализация допустима (8.3+). |
T07-L1 0.8 c | Interfaces, traits, enum | An interface can declare constants. | «yes» Пояснение: In PHP, interfaces can declare constants.
Raw{"answer": "yes", "explanation": "In PHP, interfaces can declare constants."} | верно | Константы интерфейса наследуются реализациями. |
T07-L2 0.9 c | Interfaces, traits, enum | Which operator checks whether an object is an instance of a class or interface? | «instanceof» Пояснение: The instanceof operator checks whether a given object is an instance of a particular class or implements a specified interface.
Raw{ ⏎ "answer": "instanceof", ⏎ "explanation": "The instanceof operator checks whether a given object is an instance of a particular class or implements a specified interface." ⏎ } | верно | instanceof. |
T07-L3 60.79 c | Interfaces, traits, enum | An interface can declare static methods. | «yes» Пояснение: PHP interfaces can declare abstract static methods, which implementing classes must define.
Raw{"answer": "yes", "explanation": "PHP interfaces can declare abstract static methods, which implementing classes must define."} | верно | Реализация обязана дать статический метод с той же сигнатурой. |
T07-L4 2.04 c | Interfaces, traits, enum | The instanceof operator only checks class inheritance: it ignores interfaces. | «no» Пояснение: PHP's instanceof operator can also check whether an object implements a given interface.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "PHP's instanceof operator can also check whether an object implements a given interface." ⏎ } | верно | instanceof возвращает true и для интерфейсов объекта. |
T07-L5 2.42 c | Interfaces, traits, enum | An interface method may have a default implementation, like a trait method. | «no» Пояснение: In PHP, interface methods can only declare signatures without a method body; they cannot have default implementations, unlike trait methods.
Raw{"answer": "no", "explanation": "In PHP, interface methods can only declare signatures without a method body; they cannot have default implementations, unlike trait methods."} | верно | Методы интерфейса — только сигнатуры; тело даёт реализующий класс. |
T07-L6 0.83 c | Interfaces, traits, enum | An abstract method in an abstract class may have protected visibility. | «yes» Пояснение: In PHP, abstract methods are allowed to have either public or protected visibility.
Raw{"answer": "yes", "explanation": "In PHP, abstract methods are allowed to have either public or protected visibility."} | верно | В абстрактном классе — любая видимость; в интерфейсе — только public. |
T07-L7 1.22 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 array element for each enum case.
Raw{"answer": 3, "explanation": "Foo::cases() returns one array element for each enum case."} | верно | Статический метод cases(): 3. |
T07-L8 1.25 c | Interfaces, traits, enum | A trait can declare constants. | «yes» Пояснение: In PHP, traits are allowed to declare constants.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "In PHP, traits are allowed to declare constants." ⏎ } | верно | С PHP 8.2 трейты могут объявлять константы (RFC constants_in_traits); до 8.2 — нет. |
T08-L1 3.54 c | Exceptions and errors | The Throwable interface is a common ancestor of both Exception and Error. | «yes» Пояснение: Throwable is the common abstract parent of both Exception and Error in PHP, making it the shared ancestor in the throwable hierarchy.
Raw{"answer": "yes", "explanation": "Throwable is the common abstract parent of both Exception and Error in PHP, making it the shared ancestor in the throwable hierarchy."} | верно | Иерархия с PHP 7: Throwable → Exception и Throwable → Error. |
T08-L2 8.47 c | Exceptions and errors | A catch (Exception $e) block will also catch TypeError, because TypeError ultimately inherits from Exception. | «no» Пояснение: In PHP, TypeError extends Error, not Exception, so catch (Exception $e) does not catch TypeError.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "In PHP, TypeError extends Error, not Exception, so catch (Exception $e) does not catch TypeError." ⏎ } | верно | TypeError наследуется от Error; catch (Exception) его не ловит. |
T08-L3 0.93 c | Exceptions and errors | The @ operator suppresses exceptions too. | «no» Пояснение: The @ operator suppresses PHP errors, not exceptions.
Raw{"answer": "no", "explanation": "The @ operator suppresses PHP errors, not exceptions."} | верно | @ глушит диагностику (warnings/notices), исключения не перехватывает. |
T08-L4 1.33 c | Exceptions and errors | What error class does intdiv(5, 0) throw? | «divisionbyzeroerror» Пояснение: intdiv() throws a DivisionByZeroError when the divisor is zero.
Raw{ ⏎ "answer": "DivisionByZeroError", ⏎ "explanation": "intdiv() throws a DivisionByZeroError when the divisor is zero." ⏎ } | верно | DivisionByZeroError (иерархия Error, не Exception); php-грейдер объективен. |
T08-L5 1.81 c | Exceptions and errors | The finally block runs only if the exception was caught by a catch block. | «no» Пояснение: A finally block runs when the try-catch-finally block exits, regardless of whether an exception was caught.
Raw{"answer":"no","explanation":"A finally block runs when the try-catch-finally block exits, regardless of whether an exception was caught."} | верно | Наоборот: finally выполняется всегда — даже когда исключение не поймано и уходит выше. Проверено php -r. |
T08-L6 1.41 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 does affect control flow and can propagate outward, overriding the try block's result.
Raw{"answer": "no", "explanation": "An exception thrown in a finally block does affect control flow and can propagate outward, overriding the try block's result."} | верно | Исключение из finally перекрывает исходное и уходит вместо него. |
T08-L7 2.4 c | Exceptions and errors | What does the expression (bool) new Exception('x') return? | «yes» Пояснение: In PHP, casting an object to boolean always results in true.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "In PHP, casting an object to boolean always results in true." ⏎ } | верно | Любой объект при приведении к bool — true. Формы ответа: true или да. |
T08-L8 7.69 c | Exceptions and errors | Functions registered via register_shutdown_function() run when exit is called. | «yes» Пояснение: PHP calls registered shutdown functions during normal script termination, including when exit() or die() is invoked.
Raw{"answer":"yes","explanation":"PHP calls registered shutdown functions during normal script termination, including when exit() or die() is invoked."} | верно | exit завершает скрипт, но shutdown-функции отрабатывают. |
T09-L1 2.07 c | Namespaces and autoloading | The use App\Service\Mailer; statement itself loads the class file. | «no» Пояснение: The use statement is only an alias/import declaration that does not trigger any class loading; the class file is actually loaded later when the class is first referenced (e.g., via `new`), and only then does the autoloader (or explicit require/include) load it.
Raw{"answer": "no", "explanation": "The use statement is only an alias/import declaration that does not trigger any class loading; the class file is actually loaded later when the class is first referenced (e.g., via `new`), and only then does the autoloader (or explicit require/include) load it."} | верно | use — псевдоним на этапе компиляции; файл грузит автозагрузчик при первом обращении. |
T09-L2 1.73 c | Namespaces and autoloading | What follows use to import a function (not a class): the word function or const? | «function» Пояснение: In PHP, a function is imported with `use function namespace\function();`.
Raw{"answer": "function", "explanation": "In PHP, a function is imported with `use function namespace\\function();`."} | верно | use function ...; (и use const для констант). |
T09-L3 1.58 c | Namespaces and autoloading | Into which file (path from src/) does the PSR-4 mapping "App\ → src/" place the class App\Controller\Api\UserController? | «controller/api/usercontroller.php» Пояснение: PSR-4 converts the sub-namespaces Controller and Api into directories and the class name into a .php file under src/.
Raw{ ⏎ "answer": "Controller/Api/UserController.php", ⏎ "explanation": "PSR-4 converts the sub-namespaces Controller and Api into directories and the class name into a .php file under src/." ⏎ } | верно | Остаток имени после префикса, \ → /. |
T09-L4 1.62 c | Namespaces and autoloading | Including vendor/autoload.php registers autoloaders via spl_autoload_register(). | «yes» Пояснение: Composer's vendor/autoload.php loads autoloader configurations and registers handlers using spl_autoload_register().
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Composer's vendor/autoload.php loads autoloader configurations and registers handlers using spl_autoload_register()." ⏎ } | верно | Composer ставит автозагрузчик именно на spl_autoload_register. |
T09-L5 4.76 c | Namespaces and autoloading | The magic constant __NAMESPACE__ contains the name of the current namespace. | «yes» Пояснение: In PHP, __NAMESPACE__ returns the name of the namespace in which the current file is compiled.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "In PHP, __NAMESPACE__ returns the name of the namespace in which the current file is compiled." ⏎ } | верно | В корневом пространстве — пустая строка. |
T09-L6 52.91 c | Namespaces and autoloading | An unqualified class name (without a leading \) in new is resolved from the global root. | «no» Пояснение: An unqualified class name is resolved relative to the current namespace, while a leading backslash is used to reference the global root.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "An unqualified class name is resolved relative to the current namespace, while a leading backslash is used to reference the global root." ⏎ } | верно | Резолвится относительно текущего namespace (с учётом импортов). |
T09-L7 1.17 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 App\Model\User to src/Model/User.php by converting namespace parts into directory names and the class name into the filename.
Raw{"answer":"yes","explanation":"PSR-4 maps App\\Model\\User to src/Model/User.php by converting namespace parts into directory names and the class name into the filename."} | верно | Остаток имени после префикса переносится в путь как есть. |
T09-L8 80.29 c | Namespaces and autoloading | A use statement may be written inside a function body — the import then applies to that function only. | «yes» Пояснение: PHP permits a use import inside a function body, and the imported alias is scoped to that function only.
Raw{"answer":"yes","explanation":"PHP permits a use import inside a function body, and the imported alias is scoped to that function only."} | неверно верный: «no» | use внутри тела функции — parse error; импорты файловые и компиляционные. |
T10-L1 0.91 c | References and scope | Arrays are copied on assignment rather than passed by reference. | «yes» Пояснение: In PHP, arrays are value types, so assigning one array to another creates a copy.
Raw{"answer": "yes", "explanation": "In PHP, arrays are value types, so assigning one array to another creates a copy."} | верно | Присваивание массива — копия (в движке — copy-on-write). |
T10-L2 1.39 c | References and scope | What will this print: $a = [1, 2]; $b = $a; $b[] = 3; echo count($a); | «2» Пояснение: PHP arrays are copied by value on assignment, so modifying $b does not affect $a.
Raw{ ⏎ "answer": 2, ⏎ "explanation": "PHP arrays are copied by value on assignment, so modifying $b does not affect $a." ⏎ } | верно | Присваивание — копия: в $a по-прежнему 2 элемента. |
T10-L3 4.43 c | References and scope | Inside a function, user-defined global variables are inaccessible without global, $GLOBALS, or passing them as parameters. | «yes» Пояснение: A function's local scope does not automatically expose top-level PHP variables, so access requires the global keyword, $GLOBALS, or passing the variable as a parameter.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "A function's local scope does not automatically expose top-level PHP variables, so access requires the global keyword, $GLOBALS, or passing the variable as a parameter." ⏎ } | верно | Область видимости функций изолирована; исключение — суперглобалы ($_GET и др.). |
T10-L4 1.73 c | References and scope | unset($GLOBALS['x']) inside a function removes the global variable only for that function. | «no» Пояснение: unset($GLOBALS['x']) unsets the variable from the global scope, not only for the current function.
Raw{"answer": "no", "explanation": "unset($GLOBALS['x']) unsets the variable from the global scope, not only for the current function."} | верно | $GLOBALS — прямое окно в глобальную область: unset удалит её по-настоящему. |
T10-L5 1.01 c | References and scope | What will this print: function inc(&$x) { $x++; } $n = 5; inc($n); echo $n; | «6» Пояснение: The function modifies $n by reference, incrementing it from 5 to 6.
Raw{"answer": 6, "explanation": "The function modifies $n by reference, incrementing it from 5 to 6."} | верно | Ссылка меняет оригинал: 6. |
T10-L6 160.34 c | References and scope | A foreach over an array (by value) works with the "live" array: changes to the array inside the loop are visible in the same pass. | «yes» Пояснение: PHP's foreach over an array by value does not copy the array itself; it copies only the current element, so in-loop array changes are reflected.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "PHP's foreach over an array by value does not copy the array itself; it copies only the current element, so in-loop array changes are reflected." ⏎ } | неверно верный: «no» | По значению foreach итерирует копию-снимок. |
T10-L7 1.04 c | References and scope | A static property belongs to each instance separately: changes in one object are not visible in others. | «no» Пояснение: Static properties belong to the class, so they are shared by all instances.
Raw{"answer":"no","explanation":"Static properties belong to the class, so they are shared by all instances."} | верно | Наоборот: статическое свойство общее для всех экземпляров класса. Проверено php -r. |
T10-L8 2.19 c | References and scope | An array can have a boolean key true, and it will be stored as bool. | «no» Пояснение: In PHP, a boolean key like true is cast to the integer 1 when used as an array key, not stored as a boolean.
Raw{"answer": "no", "explanation": "In PHP, a boolean key like true is cast to the integer 1 when used as an array key, not stored as a boolean."} | верно | Булев ключ приводится к int: true → 1, false → 0. |
T11-L1 2.23 c | Generators, iterators, SPL | Inside a generator, return with a value can be used, and it becomes available via $gen->getReturn(). | «yes» Пояснение: A generator's return value is accessible through Generator::getReturn() after iteration completes.
Raw{"answer":"yes","explanation":"A generator's return value is accessible through Generator::getReturn() after iteration completes."} | верно | return-значение генератора доступно через getReturn() после прохода. |
T11-L2 3.64 c | Generators, iterators, SPL | A fully consumed generator can be rewound with rewind() and traversed again. | «no» Пояснение: In PHP, generators are one-shot iterators and cannot be restarted after being fully consumed.
Raw{"answer": "no", "explanation": "In PHP, generators are one-shot iterators and cannot be restarted after being fully consumed."} | верно | Генератор одноразовый: rewind после начала итерации бросает Exception. |
T11-L3 1.43 c | Generators, iterators, SPL | The yield from construct delegates traversal to another generator or iterable. | «yes» Пояснение: In Python, `yield from` delegates iteration to another generator or iterable.
Raw{"answer": "yes", "explanation": "In Python, `yield from` delegates iteration to another generator or iterable."} | верно | yield from проксирует значения, ключи и return-значение внутреннего генератора. |
T11-L4 1.93 c | Generators, iterators, SPL | What does get_class(g()) return for function g() { yield 1; }? | «generator» Пояснение: Calling a generator function returns a Generator object, and get_class() returns its class name.
Raw{ ⏎ "answer": "Generator", ⏎ "explanation": "Calling a generator function returns a Generator object, and get_class() returns its class name." ⏎ } | верно | Функция с yield возвращает Generator. |
T11-L5 1.83 c | Generators, iterators, SPL | How many elements will count(iterator_to_array((function () { yield from [1, 2, 3]; })())) return? | «3» Пояснение: The generator yields the three values 1, 2, and 3, so iterator_to_array returns a three-element array.
Raw{"answer": 3, "explanation": "The generator yields the three values 1, 2, and 3, so iterator_to_array returns a three-element array."} | верно | yield from делегирует все 3 элемента. |
T11-L6 0.86 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.
Raw{"answer": "no", "explanation": "SplStack implements a LIFO (last-in, first-out) stack, not a FIFO queue."} | верно | SplStack — стек LIFO; очередь FIFO — SplQueue. |
T11-L7 0.95 c | Generators, iterators, SPL | ArrayIterator allows wrapping an array and traversing it via the Iterator interface. | «yes» Пояснение: ArrayIterator wraps an array and implements the Iterator interface, allowing it to be traversed.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "ArrayIterator wraps an array and implements the Iterator interface, allowing it to be traversed." ⏎ } | верно | Объектная обёртка над массивом. |
T11-L8 1.47 c | Generators, iterators, SPL | An ArrayObject instance cannot be traversed with foreach. | «no» Пояснение: ArrayObject is a Traversable object and can be directly traversed with foreach.
Raw{"answer": "no", "explanation": "ArrayObject is a Traversable object and can be directly traversed with foreach."} | верно | ArrayObject реализует IteratorAggregate — foreach по нему работает. |
T12-L1 0.82 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 in the returned hash, so you should not pass a separate salt.
Raw{"answer": "yes", "explanation": "password_hash() automatically generates and stores the salt in the returned hash, so you should not pass a separate salt."} | верно | Соль встраивается в строку результата; параметр salt устарел. |
T12-L2 1.0 c | Configuration and security | In PHP 8, PASSWORD_DEFAULT is md5 with an automatically added salt. | «no» Пояснение: PASSWORD_DEFAULT selects the recommended password hashing algorithm, not MD5, and it does not add a salt automatically because that is part of the chosen algorithm's hashing process.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "PASSWORD_DEFAULT selects the recommended password hashing algorithm, not MD5, and it does not add a salt automatically because that is part of the chosen algorithm's hashing process." ⏎ } | верно | PASSWORD_DEFAULT — bcrypt; md5 для паролей непригоден (перебирается массово). |
T12-L3 1.87 c | Configuration and security | What does password_verify('secret', password_hash('secret', PASSWORD_DEFAULT)) return? | «yes» Пояснение: password_verify returns true because the provided password matches the hash generated from the same password.
Raw{"answer": "yes", "explanation": "password_verify returns true because the provided password matches the hash generated from the same password."} | верно | Соль и хеш в одной строке: true (форма ответа: true или да). |
T12-L4 0.73 c | Configuration and security | strip_tags() protects against SQL injection. | «no» Пояснение: strip_tags() only removes HTML tags and does not prevent SQL injection.
Raw{"answer":"no","explanation":"strip_tags() only removes HTML tags and does not prevent SQL injection."} | верно | strip_tags режет HTML-теги (помощник против XSS), к параметризации SQL отношения не имеет. |
T12-L5 1.39 c | Configuration and security | session_regenerate_id() is used to protect against session fixation upon user login. | «yes» Пояснение: session_regenerate_id() generates a new session ID, which is a standard technique to prevent session fixation attacks by ensuring a fresh session identifier after authentication events like login.
Raw{"answer": "yes", "explanation": "session_regenerate_id() generates a new session ID, which is a standard technique to prevent session fixation attacks by ensuring a fresh session identifier after authentication events like login."} | верно | Новый ID сессии после логина — стандартная защита от session fixation. |
T12-L6 1.4 c | Configuration and security | Which built-in function returns the SAPI name (e.g., cli)? | «php_sapi_name» Пояснение: The php_sapi_name() built-in PHP function returns a string containing the name of the active SAPI, such as 'cli', 'fpm', or 'apache2handler'.
Raw{"answer": "php_sapi_name", "explanation": "The php_sapi_name() built-in PHP function returns a string containing the name of the active SAPI, such as 'cli', 'fpm', or 'apache2handler'."} | верно | php_sapi_name(). |
T12-L7 0.87 c | Configuration and security | session_destroy() deletes session data on the server but not the cookie in the user's browser. | «yes» Пояснение: session_destroy() deletes the session data on the server, but the session cookie remains in the browser unless explicitly deleted.
Raw{"answer": "yes", "explanation": "session_destroy() deletes the session data on the server, but the session cookie remains in the browser unless explicitly deleted."} | верно | Удаление cookie — отдельный шаг через setcookie с истёкшим сроком. |
T12-L8 1.06 c | Configuration and security | Without calling session_start(), the $_SESSION array is automatically populated with session data. | «no» Пояснение: The $_SESSION array is only populated with session data after you call session_start(), which initializes the session and loads the associated data into the superglobal.
Raw{"answer": "no", "explanation": "The $_SESSION array is only populated with session data after you call session_start(), which initializes the session and loads the associated data into the superglobal."} | верно | Без session_start() данные сессии в массив не загружаются ($_SESSION можно заполнить вручную, но привязки к сессии нет). |
VC-L1 2.79 c | PHP 8.4–8.5 | In which PHP version was the array_find() function introduced? | «no» Пояснение: array_find() is not a PHP function; it does not exist in any PHP version.
Raw{"answer": "no", "explanation": "array_find() is not a PHP function; it does not exist in any PHP version."} | неверно верный: «8.4» | PHP 8.4 (RFC array_find). |
VC-L2 1.52 c | PHP 8.4–8.5 | Property hooks (get/set right in the property declaration) landed in PHP 8.4. | «yes» Пояснение: Property hooks that define get/set logic directly in a property declaration were introduced in PHP 8.4.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Property hooks that define get/set logic directly in a property declaration were introduced in PHP 8.4." ⏎ } | верно | Property hooks — PHP 8.4 (ноябрь 2024). |
VC-L3 48.14 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 a property to be publicly readable but privately settable, e.g. `public private(set) string $name;`.
Raw{"answer":"yes","explanation":"PHP 8.4 introduced asymmetric property visibility, allowing a property to be publicly readable but privately settable, e.g. `public private(set) string $name;`."} | верно | Asymmetric visibility v2 — PHP 8.4. |
VC-L4 3.4 c | PHP 8.4–8.5 | In which PHP version was the #[\NoDiscard] attribute introduced? Answer with the version number. | «8.3» Пояснение: The #[\NoDiscard] attribute was introduced in PHP 8.3 to mark function return values as non-discardable, requiring the value to be used.
Raw{"answer": "8.3", "explanation": "The #[\\NoDiscard] attribute was introduced in PHP 8.3 to mark function return values as non-discardable, requiring the value to be used."} | неверно верный: «8.5» | #[\NoDiscard] — PHP 8.5 (marking return values as important). |
VC-L5 114.78 c | PHP 8.4–8.5 | In which PHP version did the pipe operator |> first appear? Answer with the version number. | «none» Пояснение: PHP has no built-in pipe operator (|>) in any released PHP version.
Raw{ ⏎ "answer": "none", ⏎ "explanation": "PHP has no built-in pipe operator (|>) in any released PHP version." ⏎ } | неверно верный: «8.5» | Pipe operator — PHP 8.5 (2025). |
VC-L6 59.66 c | PHP 8.4–8.5 | In which PHP version did clone-with — the syntax clone($obj, ['x' => 1]) — appear? Answer with the version number. | «8.4» Пояснение: The clone-with syntax was introduced in PHP 8.4.
Raw{"answer": "8.4", "explanation": "The clone-with syntax was introduced in PHP 8.4."} | неверно верный: «8.5» | Clone with v2 — PHP 8.5. |
VC-L7 5.04 c | PHP 8.4–8.5 | In which PHP version were the array_first() and array_last() functions introduced? | «none» Пояснение: array_first() and array_last() are not part of PHP's standard library in any version; they are Laravel helper functions, not built-in PHP functions.
Raw{"answer": "none", "explanation": "array_first() and array_last() are not part of PHP's standard library in any version; they are Laravel helper functions, not built-in PHP functions."} | неверно верный: «8.5» | PHP 8.5. |
VC-L8 79.44 c | PHP 8.4–8.5 | For which PHP version was RFC Partial Function Application v2 adopted (as of 2026-11-07)? Answer with the version number. | «8.5» Пояснение: RFC Partial Function Application v2 was accepted for PHP 8.5.
Raw{ ⏎ "answer": "8.5", ⏎ "explanation": "RFC Partial Function Application v2 was accepted for PHP 8.5." ⏎ } | неверно верный: «8.6» | PFA v2 принят 05.12.2025 (33-0-0), реализован в PHP 8.6. |
VF-L1 7.31 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.5» Пояснение: The clamp() function was implemented in PHP 8.5 following the clamp_v2 RFC.
Raw{"answer": "8.5", "explanation": "The clamp() function was implemented in PHP 8.5 following the clamp_v2 RFC."} | неверно верный: «8.6» | По данным владельца (wiki.php.net/rfc): clamp_v2 — 8.6; clamp() в 8.5.11 отсутствует (косвенное подтверждение). Дата-якорь делает клетку монотонной. |
VF-L2 125.71 c | PHP: 8.6+ and the future | RFC Context Managers v2 has already been adopted in PHP (as of 2026-11-07). | «yes» Пояснение: Context Managers v2 was adopted for PHP 8.5.
Raw{"answer": "yes", "explanation": "Context Managers v2 was adopted for PHP 8.5."} | неверно верный: «no» | На 06.11.2026 — в обсуждении (создан 2026-10-23); не принят. |
VF-L3 111.13 c | PHP: 8.6+ and the future | RFC Bound-Erased Generic Types (generics) was declined in 2026. | «no» Пояснение: The RFC was declined in a different year, not 2026.
Raw{"answer": "no", "explanation": "The RFC was declined in a different year, not 2026."} | неверно верный: «yes» | Голосование завершилось 2026-06-28: отклонён (wiki.php.net/rfc). |
VF-L4 4.55 c | PHP: 8.6+ and the future | As of 2026-11-07, the RFC enabling multithreading (ZTS) by default has already been accepted in PHP. | «no» Пояснение: To my knowledge, no RFC enabling ZTS (Zend Thread Safety / multithreading) by default has been accepted in PHP; the default build mode has historically remained non-ZTS.
Raw{"answer": "no", "explanation": "To my knowledge, no RFC enabling ZTS (Zend Thread Safety / multithreading) by default has been accepted in PHP; the default build mode has historically remained non-ZTS."} | верно | Такого принятого RFC нет на дату якоря; якорь делает клетку монотонной — при принятии RFC позже клетка не перевернётся. |
VF-L5 1.47 c | PHP: 8.6+ and the future | As of PHP 8.5, generics (parameterized types) are still absent. | «yes» Пояснение: PHP 8.5 still does not include built-in generics or parameterized types.
Raw{"answer": "yes", "explanation": "PHP 8.5 still does not include built-in generics or parameterized types."} | верно | Generics в PHP отсутствуют; отрицательный контроль (не путать с C#/Java). |
VF-L6 6.05 c | PHP: 8.6+ and the future | As of 2026-11-07, the latest stable PHP version is 8.5, and PHP 8.6 has not been released yet (GA — 2026-11-19). | «yes» Пояснение: PHP has been released in November each year since 8.0, so 8.5 (Nov 2025) would be the latest stable before 8.6 GA in Nov 2026, making the statement consistent with PHP's established release cycle.
Raw{"answer": "yes", "explanation": "PHP has been released in November each year since 8.0, so 8.5 (Nov 2025) would be the latest stable before 8.6 GA in Nov 2026, making the statement consistent with PHP's established release cycle."} | верно | 8.5 — релиз осени 2025; 8.6 GA 19.11.2026 (wiki.php.net/todo/php86). Дата снимка — 06.11.2026. |
VF-L7 1.72 c | PHP: 8.6+ and the future | The PHP 6 branch never shipped: after PHP 5.6 came PHP 7.0 directly. | «yes» Пояснение: PHP 7.0 was released after PHP 5.6, with no stable PHP 6 release.
Raw{"answer":"yes","explanation":"PHP 7.0 was released after PHP 5.6, with no stable PHP 6 release."} | верно | Исторический факт: ветка 6 не была релизнута. |
VF-L8 29.6 c | PHP: 8.6+ and the future | The RFC adding the #[\Deprecated] attribute to the core was adopted. | «yes» Пояснение: The RFC was accepted and the Deprecated attribute was added to PHP core.
Raw{"answer": "yes", "explanation": "The RFC was accepted and the Deprecated attribute was added to PHP core."} | верно | #[\Deprecated] — принят, реализован в PHP 8.4. |
T25-L1 1.29 c | Clean architecture | The dependency rule of clean and onion architecture: inner layers know nothing about outer ones — dependencies point toward the center. | «yes» Пояснение: In clean and onion architectures, dependencies point inward so inner/core layers do not depend on outer layers.
Raw{"answer": "yes", "explanation": "In clean and onion architectures, dependencies point inward so inner/core layers do not depend on outer layers."} | верно | Чистая (Robert C. Martin), луковичная (Jeffrey Palermo) и гексагональная (ports & adapters) — варианты одной идеи: зависимости направлены внутрь, к домену. Слоями в проекте следит deptrac. |
T25-L2 1.75 c | Clean architecture | Domain entities import neither Doctrine nor Symfony — only the language and, possibly, the standard library. | «yes» Пояснение: Domain entities should be framework-agnostic and typically depend only on core PHP and standard library features.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Domain entities should be framework-agnostic and typically depend only on core PHP and standard library features." ⏎ } | верно | Изоляция домена от инфраструктуры; deptrac в проекте как раз следит за слоями. |
T25-L3 0.94 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, not business-logic layer components.
Raw{"answer": "no", "explanation": "Controllers and Twig templates are presentation-layer components, not business-logic layer components."} | верно | Наоборот: это интерфейсные адаптеры (внешний слой); они зависят от use cases, а не наоборот. |
T25-L4 1.59 c | Clean architecture | What sits at the very center of the onion architecture? | «domain logic» Пояснение: The center of onion architecture contains the core business or domain logic, which outer layers depend on.
Raw{ ⏎ "answer": "domain logic", ⏎ "explanation": "The center of onion architecture contains the core business or domain logic, which outer layers depend on." ⏎ } | неверно верный: «domain model» | Центральное кольцо — Domain Model: сущности и бизнес-правила без зависимостей; далее Domain Services → Application Services → Infrastructure/UI/Tests (Palermo). |
T25-L5 1.89 c | Clean architecture | Layer boundary violations can be caught automatically: a layer-dependency analyzer (e.g. deptrac) fails on a forbidden call. | «yes» Пояснение: Layer-dependency analyzers like deptrac can automatically detect and fail on forbidden cross-layer calls that violate architectural layer boundaries.
Raw{"answer":"yes","explanation":"Layer-dependency analyzers like deptrac can automatically detect and fail on forbidden cross-layer calls that violate architectural layer boundaries."} | верно | depfile.yaml в проекте TasK: CI проверяет правила слоёв на каждом пайплайне. |
T25-L6 2.42 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 accept domain inputs and depend on abstractions, not HTTP requests or concrete persistence objects like an EntityManager.
Raw{"answer": "no", "explanation": "Use cases should accept domain inputs and depend on abstractions, not HTTP requests or concrete persistence objects like an EntityManager."} | верно | Use case принимает DTO и порты; привязка к HTTP/ORM протекает инфраструктуру во внутренние слои. |
T25-L7 1.58 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 domain aggregates or entities through an interface while abstracting the storage mechanism.
Raw{"answer":"Repository","explanation":"A repository provides a collection of domain aggregates or entities through an interface while abstracting the storage mechanism."} | верно | Repository pattern (DDD/Evans); в проекте — Doctrine-репозитории за портами. |
T25-L8 5.29 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-specific implementations belong in the outer adapter layer, leaving the inner domain and use-case logic unchanged.
Raw{"answer": "yes", "explanation": "In clean architecture, database-specific implementations belong in the outer adapter layer, leaving the inner domain and use-case logic unchanged."} | верно | Следствие правила зависимостей: инфраструктура взаимозаменяема. |
T26-L1 0.72 c | DDD | In DDD, an aggregate is just another name for a database table. | «no» Пояснение: An aggregate is a bounded domain object that encapsulates business rules and consistency, not merely a database table.
Raw{"answer": "no", "explanation": "An aggregate is a bounded domain object that encapsulates business rules and consistency, not merely a database table."} | верно | Агрегат — кластер объектов с границей согласованности (транзакционной вокруг корня); таблица — деталь хранения. |
T26-L2 1.07 c | DDD | A Value Object is immutable and compared by the values of its fields, not by identity. | «yes» Пояснение: Value Objects are typically immutable and use value equality rather than reference identity for comparison.
Raw{"answer": "yes", "explanation": "Value Objects are typically immutable and use value equality rather than reference identity for comparison."} | верно | Классика Evans: Money, Email; равенство структурное. |
T26-L3 0.91 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 sole entry point for modifying the aggregate.
Raw{"answer": "Aggregate root", "explanation": "In DDD, the aggregate root is the sole entry point for modifying the aggregate."} | верно | Aggregate Root: внешние объекты ссылаются только на корень; он защищает инварианты агрегата. |
T26-L4 0.88 c | DDD | In DDD, a repository is declared for an aggregate (its root), not for every entity. | «yes» Пояснение: In DDD, repositories are responsible for persisting and retrieving aggregate roots, not individual entities.
Raw{"answer":"yes","explanation":"In DDD, repositories are responsible for persisting and retrieving aggregate roots, not individual entities."} | верно | Репозиторий корня хранит границу согласованности агрегата; вложенные сущности доступны только через корень. |
T26-L5 1.42 c | DDD | Ubiquitous language is the model's shared language common to developers and domain experts. | «yes» Пояснение: In domain-driven design, the ubiquitous language is the shared vocabulary used by developers and domain experts to describe the model.
Raw{"answer":"yes","explanation":"In domain-driven design, the ubiquitous language is the shared vocabulary used by developers and domain experts to describe the model."} | верно | Evans: язык из требований переходит в имена классов и методов. |
T26-L6 70.05 c | DDD | What is the boundary called within which a model and its language are consistent, while outside the same words mean other models? | «namespace» Пояснение: A namespace is the scoping boundary where related models and identifiers are unambiguous, while the same names elsewhere can refer to different models.
Raw{"answer": "namespace", "explanation": "A namespace is the scoping boundary where related models and identifiers are unambiguous, while the same names elsewhere can refer to different models."} | неверно верный: «bounded context» | Bounded Context; «Заказ» в биллинге и в доставке — разные модели. |
T26-L7 1.2 c | DDD | An anemic model (objects with only getters/setters, logic in services) is the recommended DDD style. | «no» Пояснение: DDD generally recommends rich domain models with behavior inside aggregates, not anemic models.
Raw{"answer": "no", "explanation": "DDD generally recommends rich domain models with behavior inside aggregates, not anemic models."} | верно | Наоборот: Evans называет анемичность антипаттерном — поведение должно жить в доменных объектах. |
T26-L8 1.15 c | DDD | Bounded context means each context has its own model: the same concept in different contexts is a different class. | «yes» Пояснение: In a bounded context, each context has its own model, so the same concept can be represented by different classes in different contexts.
Raw{"answer": "yes", "explanation": "In a bounded context, each context has its own model, so the same concept can be represented by different classes in different contexts."} | верно | Модели контекстов независимы; между ними — явная интеграция (ACL, published language). |
T13-L1 1.63 c | Symfony | Services in the Symfony DI container are created lazily by default — on first use. | «yes» Пояснение: Symfony container services are typically instantiated only when first requested or when injected, not all at startup.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Symfony container services are typically instantiated only when first requested or when injected, not all at startup." ⏎ } | верно | Контейнер инстанцирует сервис при первом извлечении; eager-создания по умолчанию нет. |
T13-L2 3.05 c | Symfony | Which Symfony console command lists all registered routes? | «symfony:routes» Пояснение: The Symfony console command symfony:routes displays all registered routes.
Raw{"answer": "symfony:routes", "explanation": "The Symfony console command symfony:routes displays all registered routes."} | неверно верный: «debug:router» | bin/console debug:router (FrameworkBundle); в Symfony 3 команда называлась router:debug. |
T13-L3 1.45 c | Symfony | Symfony autowiring requires manually declaring every service in services.yaml. | «no» Пояснение: Symfony autowiring automatically discovers and registers services based on their type-hints, so you do not need to manually declare every service in services.yaml.
Raw{"answer": "no", "explanation": "Symfony autowiring automatically discovers and registers services based on their type-hints, so you do not need to manually declare every service in services.yaml."} | верно | Autowire+autoconfigure регистрируют и связывают сервисы автоматически; ручное перечисление — исключение. |
T13-L4 3.0 c | Symfony | Twig templates are compiled into PHP classes and cached between requests. | «yes» Пояснение: Twig compiles templates into PHP code (often as template classes) and caches them for reuse across requests.
Raw{"answer": "yes", "explanation": "Twig compiles templates into PHP code (often as template classes) and caches them for reuse across requests."} | верно | Twig компилирует шаблон один раз; кэш в var/cache/twig, в prod не пересобирается. |
T13-L5 1.48 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 development environment, the container is compiled and cached, and is only recompiled when tracked source files have been modified.
Raw{"answer": "yes", "explanation": "In Symfony's development environment, the container is compiled and cached, and is only recompiled when tracked source files have been modified."} | верно | Kernel проверяет freshness ресурсов (конфиги, классы); иначе переиспользуется кэш контейнера. |
T13-L6 2.14 c | Symfony | Which environment variable selects the active Symfony environment (dev/prod)? | «app_env» Пояснение: In modern Symfony (4.x and later), the APP_ENV environment variable selects the active environment (e.g., dev, prod, staging).
Raw{"answer": "APP_ENV", "explanation": "In modern Symfony (4.x and later), the APP_ENV environment variable selects the active environment (e.g., dev, prod, staging)."} | верно | APP_ENV в .env; APP_DEBUG — отдельный флаг отладки. |
T13-L7 10.0 c | Symfony | A controller method can be private — Symfony routing works with any method of the class. | «no» Пояснение: Symfony routing resolves controller actions as external callables or via reflection, both of which respect PHP method visibility; private methods cannot be invoked from outside the class, so they cannot be used as route actions.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "Symfony routing resolves controller actions as external callables or via reflection, both of which respect PHP method visibility; private methods cannot be invoked from outside the class, so they cannot be used as route actions." ⏎ } | верно | Действие контроллера должно быть public; приватный метод по маршруту не вызывается. |
T13-L8 2.29 c | Symfony | Event subscribers always receive events before listeners, because the interface gives them priority. | «no» Пояснение: There is no built-in PHP rule that event subscribers receive events before listeners based on their interface.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "There is no built-in PHP rule that event subscribers receive events before listeners based on their interface." ⏎ } | верно | Порядок определяет priority, а не тип подписки; приоритеты задаются в getSubscribedEvents() так же, как у слушателей. |
T22-L1 1.13 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 system and uses the new AuthenticatorInterface-based authentication mechanism.
Raw{"answer":"yes","explanation":"Symfony 6.0 removed the old Guard system and uses the new AuthenticatorInterface-based authentication mechanism."} | верно | Guard объявлен устаревшим в 5.3 и удалён в 6.0; в проекте symfony/security-bundle 8.1. |
T22-L2 2.47 c | Symfony: Security and forms | Which Symfony attribute checks a role/permission right on a controller method (403 without it)? | «isgranted» Пояснение: The IsGranted attribute checks a user's role or permission on a controller action and raises a 403 AccessDeniedException when access is denied.
Raw{ ⏎ "answer": "IsGranted", ⏎ "explanation": "The IsGranted attribute checks a user's role or permission on a controller action and raises a 403 AccessDeniedException when access is denied." ⏎ } | верно | #[IsGranted('ROLE_ADMIN')]; атрибут из symfony/security-http. |
T22-L3 1.19 c | Symfony: Security and forms | Voters are Symfony's mechanism for checking access to a specific object: isGranted('EDIT', $post). | «yes» Пояснение: Symfony voters are used by isGranted() to determine whether the current user has permission to perform an action on a specific object.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Symfony voters are used by isGranted() to determine whether the current user has permission to perform an action on a specific object." ⏎ } | верно | VoterInterface->vote(); docs Symfony — Voters. |
T22-L4 137.62 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 mapping annotations are deprecated but still supported in Symfony 7, so they are not no longer supported.
Raw{"answer":"no","explanation":"Doctrine mapping annotations are deprecated but still supported in Symfony 7, so they are not no longer supported."} | неверно верный: «yes» | Докблок-аннотации удалены в Symfony 7.0; стандарт — атрибуты. В проекте symfony/validator 8.1. |
T22-L5 2.85 c | Symfony: Security and forms | CSRF protection of Symfony forms is enabled by default: the form validates the token on submission. | «yes» Пояснение: Symfony forms include CSRF protection by default and validate the submitted CSRF token during form validation.
Raw{"answer": "yes", "explanation": "Symfony forms include CSRF protection by default and validate the submitted CSRF token during form validation."} | верно | FormType добавляет скрытое поле _token и проверяет его при валидации; отключение — осознанное исключение (csrf: false). |
T22-L6 1.03 c | Symfony: Security and forms | Form validation in Symfony runs server-side even if the client-side (HTML5) checks passed. | «yes» Пояснение: Client-side HTML5 validation only checks the browser, and Symfony still performs its own server-side validation when the form is submitted.
Raw{"answer": "yes", "explanation": "Client-side HTML5 validation only checks the browser, and Symfony still performs its own server-side validation when the form is submitted."} | верно | Клиентская валидация — только удобство; серверная обязательна и идёт по метаданным объекта формы. |
T22-L7 0.9 c | Symfony: Security and forms | Which Symfony maker command generates a form class (FormType)? | «make:form» Пояснение: The Symfony MakerBundle command make:form generates a form type class.
Raw{"answer": "make:form", "explanation": "The Symfony MakerBundle command make:form generates a form type class."} | верно | bin/console make:form (symfony/maker-bundle — в проекте). |
T22-L8 0.84 c | Symfony: Security and forms | Symfony stores the user's password in the session in plain text. | «no» Пояснение: Symfony does not store the user's password in plain text in the session; passwords are hashed and only authentication data such as a user identifier is stored.
Raw{"answer": "no", "explanation": "Symfony does not store the user's password in plain text in the session; passwords are hashed and only authentication data such as a user identifier is stored."} | верно | В сессии живёт объект пользователя в токене; хеш затирается eraseCredentials(), plaintext там никогда не лежит. |
T23-L1 1.16 c | Symfony: configuration and services | Symfony bundle configuration lives in config/packages — one file per bundle or topic. | «yes» Пояснение: Symfony bundle configuration is typically organized in config/packages with one file per bundle or topic.
Raw{"answer":"yes","explanation":"Symfony bundle configuration is typically organized in config/packages with one file per bundle or topic."} | верно | Стандартная структура (config/packages/*.yaml); перегрузка — config/packages/<env>. |
T23-L2 4.65 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» Пояснение: Committed .env files usually hold default/non-secret values, while .env.local holds local secrets and is ignored.
Raw{"answer":"yes","explanation":"Committed .env files usually hold default/non-secret values, while .env.local holds local secrets and is ignored."} | верно | symfony/dotenv: .env — общий безопасный набор значений; локальные секреты — .env.local (gitignored) или secrets-хранилище. |
T23-L3 0.97 c | Symfony: configuration and services | Which Symfony command lists the container's registered services and their aliases? | «debug:container» Пояснение: The debug:container command lists all registered services in the service container along with their aliases.
Raw{"answer": "debug:container", "explanation": "The debug:container command lists all registered services in the service container along with their aliases."} | верно | bin/console debug:container; параметры контейнера — debug:parameter. |
T23-L4 42.87 c | Symfony: configuration and services | The Symfony container allows changing parameters at runtime: $container->setParameter() works from a controller. | «no» Пояснение: The container/service locator used in a controller is read-only, so setParameter() is not available to change parameters at runtime.
Raw{"answer":"no","explanation":"The container/service locator used in a controller is read-only, so setParameter() is not available to change parameters at runtime."} | верно | Контейнер компилируется и замораживается; runtime-значения — только через переменные окружения. |
T23-L5 1.18 c | Symfony: configuration and services | By default, Symfony services are public (public: true) — you can fetch them directly from the container. | «no» Пояснение: By default, Symfony services are not public (public: false), which is the case since Symfony 3.4+ to enforce encapsulation and security.
Raw{"answer": "no", "explanation": "By default, Symfony services are not public (public: false), which is the case since Symfony 3.4+ to enforce encapsulation and security."} | верно | С Symfony 4.0 сервисы по умолчанию private: инжектятся через autowiring; $container->get() — только для публичных. |
T23-L6 1.56 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 always require a configuration file; many can work without one.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "A bundle does not always require a configuration file; many can work without one." ⏎ } | верно | У бандлов есть встроенные умолчания (Extension); конфиг нужен только для отклонений от них. |
T23-L7 69.09 c | Symfony: configuration and services | Environment variable values are injected into services.yaml using the %env(VAR)% syntax. | «yes» Пояснение: Yes, %env(VAR)% is the placeholder syntax used to reference environment variables in Symfony service configuration.
Raw{"answer":"yes","explanation":"Yes, %env(VAR)% is the placeholder syntax used to reference environment variables in Symfony service configuration."} | верно | %env(...)% резолвится в рантайме env-процессорами; docs — Env Var Processors. |
T23-L8 1.18 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's debug mode, affecting the profiler and Twig debugging.
Raw{ ⏎ "answer": "APP_DEBUG", ⏎ "explanation": "The APP_DEBUG environment variable enables Symfony's debug mode, affecting the profiler and Twig debugging." ⏎ } | верно | APP_DEBUG=1 (в .env dev-окружения); окружение выбирает APP_ENV — см. T13-L6. |
T16-L1 13.58 c | Symfony: Messenger | A single message in Symfony Messenger can only have one handler. | «no» Пояснение: Symfony Messenger allows a single message to be handled by multiple handlers/subscribers.
Raw{"answer": "no", "explanation": "Symfony Messenger allows a single message to be handled by multiple handlers/subscribers."} | верно | Messenger вызывает все хендлеры, подписанные на класс сообщения (docs — Multiple Handlers). |
T16-L2 1.61 c | Symfony: Messenger | The sync transport in Messenger queues the message for a worker, just like async. | «no» Пояснение: The sync transport processes the message immediately within the current process rather than queueing it for a separate worker to handle asynchronously.
Raw{"answer": "no", "explanation": "The sync transport processes the message immediately within the current process rather than queueing it for a separate worker to handle asynchronously."} | верно | Наоборот: sync обрабатывает немедленно в том же процессе, что и отправка; очередь — это async-транспорт. |
T16-L3 0.99 c | Symfony: Messenger | Which console command starts the worker that processes Messenger queue messages? | «messenger:consume» Пояснение: The Symfony Messenger component uses the messenger:consume command to start a worker that processes queued messages.
Raw{"answer": "messenger:consume", "explanation": "The Symfony Messenger component uses the messenger:consume command to start a worker that processes queued messages."} | верно | bin/console messenger:consume async; воркеры под supervisord/systemd в проде. |
T16-L4 5.16 c | Symfony: Messenger | Retries for failed messages (retry_strategy) are configured per Messenger transport. | «yes» Пояснение: In Symfony Messenger, the retry option (including multiplier, max_attempts, and lock_timeout) is configured within each transport's options in the messenger configuration, making it a per-transport setting.
Raw{"answer": "yes", "explanation": "In Symfony Messenger, the retry option (including multiplier, max_attempts, and lock_timeout) is configured within each transport's options in the messenger configuration, making it a per-transport setting."} | верно | retry_strategy на транспорте: max_retries, delay, multiplier; docs — Failed Messages & Retries. |
T16-L5 2.13 c | Symfony: Messenger | By default, Messenger serializes messages to JSON. | «yes» Пояснение: Symfony Messenger serializes messages to JSON by default.
Raw{"answer":"yes","explanation":"Symfony Messenger serializes messages to JSON by default."} | неверно верный: «no» | Дефолтный сериализатор — PhpSerializer (serialize()); JSON-сериализатор включается отдельно. |
T16-L6 1.96 c | Symfony: Messenger | Symfony Scheduler produces messages on a schedule and dispatches them through Messenger. | «yes» Пояснение: Symfony Scheduler is intended to create and dispatch messages through Symfony Messenger on a defined schedule.
Raw{"answer":"yes","explanation":"Symfony Scheduler is intended to create and dispatch messages through Symfony Messenger on a defined schedule."} | верно | Schedule → RecurringMessage → шина Messenger; docs — Scheduler. |
T16-L7 2.44 c | Symfony: Messenger | Which built-in Messenger transport stores messages in database tables via Doctrine? | «database» Пояснение: Symfony Messenger's built-in DatabaseTransport uses Doctrine to persist messages in database tables.
Raw{"answer": "database", "explanation": "Symfony Messenger's built-in DatabaseTransport uses Doctrine to persist messages in database tables."} | неверно верный: «doctrine» | Транспорт doctrine (symfony/doctrine-messenger); таблица messenger_messages. В проекте стоит amqp-messenger + doctrine-messenger. |
T16-L8 4.88 c | Symfony: Messenger | The Messenger pipeline can be extended with custom middleware, placed before or after the built-in ones. | «yes» Пояснение: The Messenger pipeline supports adding custom middleware that can be inserted before or after existing built-in middleware.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "The Messenger pipeline supports adding custom middleware that can be inserted before or after existing built-in middleware." ⏎ } | верно | messenger.bus.*.middleware в yaml; docs — Middleware. |
T28-L1 11.83 c | Symfony: versions | Symfony major releases come every two years, minor ones every six months (in May and November). | «yes» Пояснение: Symfony follows a release cadence with major/LTS releases every two years and minor releases every six months, typically in May and November.
Raw{"answer": "yes", "explanation": "Symfony follows a release cadence with major/LTS releases every two years and minor releases every six months, typically in May and November."} | верно | Стандартный релизный цикл: 8.0 — ноябрь 2025, 8.1 — май 2026, 8.2 — ноябрь 2026. |
T28-L2 27.63 c | Symfony: versions | What is the minimum PHP version required by Symfony 8? | «8.4» Пояснение: Symfony 8 requires PHP 8.4 or newer.
Raw{"answer": "8.4", "explanation": "Symfony 8 requires PHP 8.4 or newer."} | верно | Symfony 8.0 поднял требование до PHP >= 8.4.1 (в vendor проекта: "php": ">=8.4.1"). |
T28-L3 15.69 c | Symfony: versions | Symfony 7.0 kept support for docblock annotations (validation, routes). | «no» Пояснение: Symfony removed legacy docblock annotation support in 6.0, so 7.0 requires PHP attributes for validation and routing.
Raw{"answer":"no","explanation":"Symfony removed legacy docblock annotation support in 6.0, so 7.0 requires PHP attributes for validation and routing."} | верно | Наоборот: в 7.0 аннотации удалены — только PHP-атрибуты (#[Route], #[Assert\NotBlank]). |
T28-L4 9.44 c | Symfony: versions | AssetMapper manages CSS/JS without node or webpack — via importmap.php. | «yes» Пояснение: AssetMapper uses an importmap.php-based import map to manage CSS/JS assets without requiring Node.js or Webpack.
Raw{"answer":"yes","explanation":"AssetMapper uses an importmap.php-based import map to manage CSS/JS assets without requiring Node.js or Webpack."} | верно | symfony/asset-mapper (с 6.3, стандарт с 7.x); в проекте — importmap.php в корне и asset-mapper 8.1. |
T28-L5 5.08 c | Symfony: versions | Symfony 6.4 is a regular release without long-term support. | «no» Пояснение: Symfony 6.4 is a long-term support release, not just a regular release without LTS.
Raw{"answer": "no", "explanation": "Symfony 6.4 is a long-term support release, not just a regular release without LTS."} | верно | Наоборот: 6.4 — LTS (расширенная поддержка); LTS выходит вместе с очередным мажором (6.4 — вместе с 7.0). |
T28-L6 3.19 c | Symfony: versions | When moving to a new Symfony major version, deprecations of the previous branch keep working — major releases do not remove them. | «no» Пояснение: Symfony major releases remove deprecations that were introduced in the previous major branch.
Raw{"answer":"false","explanation":"Symfony major releases remove deprecations that were introduced in the previous major branch."} | верно | Наоборот: мажорный релиз удаляет всё устаревшее (7.0 убрал деприкейшены 6.x, 8.0 — 7.x). |
T28-L7 1.48 c | Symfony: versions | Every Symfony major release is accompanied by an UPGRADE guide listing the changes. | «yes» Пояснение: Symfony provides an UPGRADE guide with each major release documenting all changes, deprecations, and breaking changes.
Raw{"answer": "yes", "explanation": "Symfony provides an UPGRADE guide with each major release documenting all changes, deprecations, and breaking changes."} | верно | UPGRADE-7.0.md, UPGRADE-8.0.md в репозитории symfony/symfony. |
T28-L8 2.27 c | Symfony: versions | Which Symfony component manages assets and the importmap without node/webpack? | «asset mapper» Пояснение: Symfony's Asset Mapper (symfony/asset-mapper), introduced in Symfony 6.1, manages CSS/JS assets and importmaps without requiring Node.js or webpack.
Raw{"answer": "Asset Mapper", "explanation": "Symfony's Asset Mapper (symfony/asset-mapper), introduced in Symfony 6.1, manages CSS/JS assets and importmaps without requiring Node.js or webpack."} | верно | symfony/asset-mapper 8.1 — в проекте. |
T29-L1 92.85 c | Symfony: 8.2 and beyond | As of 2026-11-07, Symfony 8.2 has already been released. | «no» Пояснение: Symfony 8.2 was not yet released as of 2026-11-07.
Raw{"answer":"no","explanation":"Symfony 8.2 was not yet released as of 2026-11-07."} | верно | Наоборот: 8.2 ещё не выпущена — релиз в конце ноября 2026; последняя стабильная — 8.1. |
T29-L2 7.65 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. | «yes» Пояснение: Symfony's usual six-month release cycle places Symfony 8.2 in November 2026, after Symfony 8.1 in May 2026.
Raw{"answer":"yes","explanation":"Symfony's usual six-month release cycle places Symfony 8.2 in November 2026, after Symfony 8.1 in May 2026."} | верно | Политика релизов: 8.1 — май 2026, 8.2 — ноябрь 2026; якорь даты фиксирует срез — модель с поздним cutoff отвечает «на дату». |
T29-L3 33.56 c | Symfony: 8.2 and beyond | Which Symfony version comes after 8.1 (as of 2026-11-07)? | «8.2» Пояснение: The immediate next Symfony version after 8.1 is 8.2.
Raw{"answer":"8.2","explanation":"The immediate next Symfony version after 8.1 is 8.2."} | верно | 8.2 — следующий минорный релиз (ноябрь 2026); после его выхода проект переходит с 8.1.* на 8.2.*. |
T29-L4 4.19 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 would be a minor (or patch) release within the 8.x cycle, not a major release; the major release would be 8.0, and as of current knowledge Symfony 8 has not yet been released.
Raw{"answer": "no", "explanation": "Symfony 8.2 would be a minor (or patch) release within the 8.x cycle, not a major release; the major release would be 8.0, and as of current knowledge Symfony 8 has not yet been released."} | верно | Наоборот: 8.2 — минорный релиз; новые возможности без поломки обратной совместимости. Мажор — 9.0. |
T29-L5 5.37 c | Symfony: 8.2 and beyond | Updating within a major branch (8.1 → 8.2) should not require code changes — backward compatibility is preserved. | «yes» Пояснение: PHP minor releases like 8.1 to 8.2 maintain backward compatibility, so no code changes are required.
Raw{"answer": "yes", "explanation": "PHP minor releases like 8.1 to 8.2 maintain backward compatibility, so no code changes are required."} | верно | Политика Symfony: минорные релизы обратно совместимы; BC-break допустим только в мажорных. |
T29-L6 94.47 c | Symfony: 8.2 and beyond | Which minor version of the 8.x branch is released last, before Symfony 9.0? | «8.4» Пояснение: Symfony 8.4 is the final minor release in the 8.x branch before Symfony 9.0.
Raw{"answer":"8.4","explanation":"Symfony 8.4 is the final minor release in the 8.x branch before Symfony 9.0."} | верно | По циклу: 8.2 (ноя 2026), 8.3 (май 2027), 8.4 (ноя 2027, вместе с 9.0) — как 6.4 выходила вместе с 7.0. |
T29-L7 8.75 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 will require PHP 8.5, so you would need to upgrade PHP to use that Symfony version.
Raw{"answer": "yes", "explanation": "Symfony 8.2 will require PHP 8.5, so you would need to upgrade PHP to use that Symfony version."} | неверно верный: «no» | Наоборот: минорные релизы не поднимают требования PHP; для всей ветки 8.x остаётся PHP >= 8.4. |
T29-L8 5.93 c | Symfony: 8.2 and beyond | Deprecations added in the 8.x branch will not be removed before Symfony 9.0. | «yes» Пояснение: Deprecations added in Symfony 8.x are kept until at least the next major release, Symfony 9.0.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Deprecations added in Symfony 8.x are kept until at least the next major release, Symfony 9.0." ⏎ } | верно | Политика: деприкейшены живут до следующего мажора; 9.0 — ноябрь 2027. |
T21-L1 1.01 c | Twig | Inside {{ }}, Twig allows calling arbitrary PHP code directly. | «no» Пояснение: Twig's {{ }} expressions use a restricted template language and do not allow arbitrary PHP code.
Raw{"answer": "no", "explanation": "Twig's {{ }} expressions use a restricted template language and do not allow arbitrary PHP code."} | верно | Twig — DSL: только разрешённые окружением функции/фильтры; произвольный PHP не исполняется. |
T21-L2 6.32 c | Twig | By default, Twig auto-escapes printed variables. | «no» Пояснение: Twig does not auto-escape printed variables by default; you must enable auto-escaping explicitly.
Raw{"answer":"no","explanation":"Twig does not auto-escape printed variables by default; you must enable auto-escaping explicitly."} | неверно верный: «yes» | Autoescape включён по умолчанию; {{ '<b>' }} → <b>. Проверено на Twig 3.30. |
T21-L3 1.01 c | Twig | The Twig |e filter escapes a string for safe output in an HTML context. | «yes» Пояснение: The Twig |e filter escapes a string by default for safe output in an HTML context.
Raw{"answer": "yes", "explanation": "The Twig |e filter escapes a string by default for safe output in an HTML context."} | верно | |e ('html') по умолчанию; есть контексты js/url/css. От SQL-инъекций он не защищает — это задача подготовленных запросов Doctrine. |
T21-L4 2.13 c | Twig | Which filter from twig/intl-extra formats a number according to a locale? | «number_format» Пояснение: The twig/intl-extra package provides the `number_format` filter, which uses ICU to format a number with locale-appropriate separators and grouping.
Raw{"answer": "number_format", "explanation": "The twig/intl-extra package provides the `number_format` filter, which uses ICU to format a number with locale-appropriate separators and grouping."} | неверно верный: «format_number» | |format_number(locale=...) из IntlExtension (twig/intl-extra есть в проекте). Проверено на Twig 3.30: 12345.6 → 12 345,6 (ru). |
T21-L5 25.83 c | Twig | The |raw filter disables auto-escaping for the value. | «yes» Пояснение: In Blade, the |raw filter outputs the value without auto-escaping.
Raw{"answer":"yes","explanation":"In Blade, the |raw filter outputs the value without auto-escaping."} | верно | {{ x|raw }} выводит HTML как есть; опасно с пользовательскими данными. Проверено на Twig 3.30. |
T21-L6 1.15 c | Twig | In Twig, {{ }} prints an expression value, while {% %} executes tags — conditions, loops, set. | «yes» Пояснение: In Twig, {{ }} outputs an expression value, while {% %} executes tags such as if, for, and set.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "In Twig, {{ }} outputs an expression value, while {% %} executes tags such as if, for, and set." ⏎ } | верно | Два блока синтаксиса Twig: вывод (echo) против логики. |
T21-L7 1.87 c | Twig | In Twig you cannot declare a variable inside a template — values only come from the controller. | «no» Пояснение: Twig allows you to declare variables inside a template using {% set %}.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "Twig allows you to declare variables inside a template using {% set %}." ⏎ } | верно | {% set y = ... %} объявляет переменную в шаблоне. Проверено на Twig 3.30. |
T21-L8 1.16 c | Twig | Which Twig function dumps the debug structure of a variable (array, object)? | «dump» Пояснение: Twig's dump function displays the debug structure of a variable.
Raw{ ⏎ "answer": "dump", ⏎ "explanation": "Twig's dump function displays the debug structure of a variable." ⏎ } | верно | {{ dump(x) }} (DebugExtension; в Symfony доступна в dev-окружении). |
T24-L1 0.72 c | Bootstrap | Bootstrap is a CSS/JS library of ready-made UI components, not an SPA framework. | «yes» Пояснение: Bootstrap is primarily a front-end UI library, not a single-page application framework.
Raw{"answer":"yes","explanation":"Bootstrap is primarily a front-end UI library, not a single-page application framework."} | верно | Компоненты и утилиты поверх вашего HTML; SPA-фреймворки (React/Vue) — другой класс инструментов. В проекте vendored 5.3.3. |
T24-L2 2.13 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 a fixed max-width at each breakpoint.
Raw{"answer":"container","explanation":"The Bootstrap container class provides a responsive container with a fixed max-width at each breakpoint."} | верно | .container (фиксированная макс-ширина по брейкпоинтам) vs .container-fluid (на всю ширину). |
T24-L3 1.37 c | Bootstrap | The Bootstrap grid is built on CSS floats and splits a row into 16 columns. | «no» Пояснение: The Bootstrap grid uses 12 columns, and modern versions use Flexbox rather than CSS floats.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "The Bootstrap grid uses 12 columns, and modern versions use Flexbox rather than CSS floats." ⏎ } | верно | Наоборот: flexbox (с Bootstrap 4) и 12 колонок; float-сетка — это Bootstrap 3. |
T24-L4 1.15 c | Bootstrap | Bootstrap's named breakpoints (the infix used in class names) are sm, md, lg, xl, xxl — five of them. | «yes» Пояснение: Bootstrap's class-name infixes for named breakpoints are sm, md, lg, xl, and xxl.
Raw{"answer":"yes","explanation":"Bootstrap's class-name infixes for named breakpoints are sm, md, lg, xl, and xxl."} | верно | Тиров всего шесть: xs (без инфикса) + пять именованных (576/768/992/1200/1400 px). |
T24-L5 73.85 c | Bootstrap | Utilities like .mt-3 or .px-2 use the spacing scale: the number is a multiple of $spacer. | «no» Пояснение: The number is an index into the spacing scale, not a literal multiple of $spacer (e.g., .px-2 is 0.5rem, not 2rem).
Raw{"answer":"no","explanation":"The number is an index into the spacing scale, not a literal multiple of $spacer (e.g., .px-2 is 0.5rem, not 2rem)."} | верно | Spacing utilities; $spacer = 1rem. |
T24-L6 1.73 c | Bootstrap | Which Bootstrap 5 data attribute enables an interactive component (e.g. dropdown) on an element? | «data-bs-toggle» Пояснение: In Bootstrap 5, the data-bs-toggle attribute is used to enable interactive components such as dropdowns, modals, and tooltips on an element.
Raw{"answer": "data-bs-toggle", "explanation": "In Bootstrap 5, the data-bs-toggle attribute is used to enable interactive components such as dropdowns, modals, and tooltips on an element."} | верно | data-bs-toggle="dropdown" и т.п.; в Bootstrap 4 атрибут назывался data-toggle. |
T24-L7 0.8 c | Bootstrap | Bootstrap 5 components work without jQuery — in plain vanilla JS. | «yes» Пояснение: Bootstrap 5 removed its dependency on jQuery and its components can be used with vanilla JavaScript.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Bootstrap 5 removed its dependency on jQuery and its components can be used with vanilla JavaScript." ⏎ } | верно | jQuery удалён в Bootstrap 5.0: data-bs-* атрибуты и JS API. В проекте vendored 5.3.3. |
T24-L8 1.89 c | Bootstrap | Dark mode in Bootstrap is enabled with a .dark class on the root element. | «no» Пояснение: Bootstrap 5 enables dark mode with data-bs-theme="dark", not a .dark class on the root element.
Raw{"answer": "no", "explanation": "Bootstrap 5 enables dark mode with data-bs-theme=\"dark\", not a .dark class on the root element."} | верно | Наоборот: тема включается атрибутом data-bs-theme="dark" (Color modes, с 5.3); класса .dark не существует. В проекте 5.3.3. |
T14-L1 1.43 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 tables automatically at runtime; you must explicitly generate or migrate the schema using Doctrine Migrations or the schema generation tools.
Raw{"answer": "no", "explanation": "Doctrine ORM does not create tables automatically at runtime; you must explicitly generate or migrate the schema using Doctrine Migrations or the schema generation tools."} | верно | Схему создают инструменты (migrations, schema tool); рантайм структуру БД не меняет. |
T14-L2 1.01 c | Doctrine | Which EntityManager method marks a new object as managed without executing SQL until flush()? | «persist» Пояснение: EntityManager::persist() registers a new object as managed without issuing SQL until flush().
Raw{"answer": "persist", "explanation": "EntityManager::persist() registers a new object as managed without issuing SQL until flush()."} | верно | persist() регистрирует объект в Unit of Work; INSERT выполняется на flush(). |
T14-L3 2.74 c | Doctrine | In Doctrine ORM 3, the EntityManager::merge() method exists and makes the passed object managed. | «yes» Пояснение: In Doctrine ORM 3, EntityManager::merge() takes a detached object and returns a managed instance, making it tracked by the EntityManager.
Raw{"answer":"yes","explanation":"In Doctrine ORM 3, EntityManager::merge() takes a detached object and returns a managed instance, making it tracked by the EntityManager."} | неверно верный: «no» | В ORM 3 merge() удалён (в vendor проекта 3.7.6 метода нет); в Doctrine 2.x merge() возвращал управляемую копию. Версия зафиксирована — ORM 3. |
T14-L4 1.26 c | Doctrine | DQL queries are written in terms of entities and their fields, not tables and columns. | «yes» Пояснение: DQL is object-oriented and uses entity and field names rather than database table or column names.
Raw{"answer":"yes","explanation":"DQL is object-oriented and uses entity and field names rather than database table or column names."} | верно | Doctrine транслирует DQL в SQL; docs — DQL (Doctrine Query Language). |
T14-L5 3.38 c | Doctrine | What does $repository->find(999) return when no record with id 999 exists? | «null» Пояснение: When no record with the given ID is found, find() returns null.
Raw{ ⏎ "answer": "null", ⏎ "explanation": "When no record with the given ID is found, find() returns null." ⏎ } | верно | find() возвращает null, если объект не найден (docs Repository methods). |
T14-L6 2.89 c | Doctrine | DoctrineBundle in Symfony automatically calls flush() at the end of every request. | «no» Пояснение: DoctrineBundle does not automatically call flush() at the end of every request; the developer must explicitly call EntityManager::flush().
Raw{"answer": "false", "explanation": "DoctrineBundle does not automatically call flush() at the end of every request; the developer must explicitly call EntityManager::flush()."} | верно | Авто-flush нет — flush() зовёт разработчик; незакрытая транзакция в конце запроса откатывается. |
T14-L7 1.36 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» Пояснение: Doctrine's Unit of Work tracks modifications to managed entities, so flush() can commit property changes without persist().
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Doctrine's Unit of Work tracks modifications to managed entities, so flush() can commit property changes without persist()." ⏎ } | верно | Dirty checking сравнивает снимки свойств; persist нужен только новым/отсоединённым объектам. |
T14-L8 1.65 c | Doctrine | remove() executes the SQL DELETE immediately, without waiting for flush(). | «no» Пояснение: remove() only schedules the entity for deletion; the SQL DELETE is executed when flush() is called.
Raw{"answer": "no", "explanation": "remove() only schedules the entity for deletion; the SQL DELETE is executed when flush() is called."} | верно | remove() планирует удаление в Unit of Work; DELETE выполняется на flush() (docs — Deleting Objects). |
T15-L1 1.26 c | PostgreSQL | PostgreSQL uses MVCC, therefore readers block writers and writers block readers. | «no» Пояснение: PostgreSQL's MVCC generally allows readers and writers to operate concurrently without blocking each other.
Raw{"answer": "no", "explanation": "PostgreSQL's MVCC generally allows readers and writers to operate concurrently without blocking each other."} | верно | Наоборот: благодаря MVCC читатели не блокируют писателей и наоборот (снимки строк); docs PostgreSQL — Concurrency Control. |
T15-L2 1.48 c | PostgreSQL | Which SQL command shows a query's execution plan without executing the query? | «explain» Пояснение: The EXPLAIN command displays a query's execution plan without actually executing the query.
Raw{"answer":"EXPLAIN","explanation":"The EXPLAIN command displays a query's execution plan without actually executing the query."} | верно | EXPLAIN без ANALYZE только строит план; проверено на PostgreSQL 17.7. |
T15-L3 1.57 c | PostgreSQL | SERIAL and GENERATED ... AS IDENTITY are just two names for the same mechanism. | «no» Пояснение: SERIAL is PostgreSQL's legacy convenience type for creating sequence-backed columns, while GENERATED AS IDENTITY is the standard SQL identity mechanism, so they are similar but not simply two names for the same thing.
Raw{"answer": "no", "explanation": "SERIAL is PostgreSQL's legacy convenience type for creating sequence-backed columns, while GENERATED AS IDENTITY is the standard SQL identity mechanism, so they are similar but not simply two names for the same thing."} | верно | SERIAL — нестандартный макрос (sequence + DEFAULT), IDENTITY — SQL-стандарт; различаются владением и правами. Оба есть в PG 17 (проверено). |
T15-L4 6.16 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 containing NULL in the column.
Raw{"answer":"no","explanation":"PostgreSQL treats NULL values as distinct by default, so a UNIQUE constraint allows multiple rows containing NULL in the column."} | верно | Наоборот: NULLS DISTINCT по умолчанию — несколько NULL допустимы; NULLS NOT DISTINCT — опция с PG 15. Проверено на PG 17.7. |
T15-L5 0.92 c | PostgreSQL | Which PostgreSQL aggregate function concatenates strings with a separator? | «string_agg» Пояснение: In PostgreSQL, string_agg() is the aggregate function that concatenates strings using a specified separator.
Raw{ ⏎ "answer": "string_agg", ⏎ "explanation": "In PostgreSQL, string_agg() is the aggregate function that concatenates strings using a specified separator." ⏎ } | верно | string_agg(значение, разделитель); проверено на PostgreSQL 17.7. |
T15-L6 3.29 c | PostgreSQL | Plain VACUUM returns the space occupied by dead tuples to the operating system. | «no» Пояснение: Plain VACUUM reclaims space within the database but does not return it to the operating system.
Raw{"answer": "false", "explanation": "Plain VACUUM reclaims space within the database but does not return it to the operating system."} | верно | VACUUM помечает место для переиспользования внутри таблицы; ОС его возвращает только VACUUM FULL (с эксклюзивной блокировкой). |
T15-L7 4.23 c | PostgreSQL | Which keyword in a window function definition partitions rows into groups the function is computed over? | «partition by» Пояснение: The PARTITION BY clause groups rows for the window function to compute over.
Raw{"answer":"PARTITION BY","explanation":"The PARTITION BY clause groups rows for the window function to compute over."} | верно | OVER (PARTITION BY ...); проверено на PostgreSQL 17.7. |
T15-L8 1.79 c | PostgreSQL | The READ COMMITTED isolation level protects against non-repeatable reads. | «no» Пояснение: READ COMMITTED prevents dirty reads but does not prevent non-repeatable reads.
Raw{"answer": "no", "explanation": "READ COMMITTED prevents dirty reads but does not prevent non-repeatable reads."} | верно | READ COMMITTED допускает неповторяющееся чтение; защищает REPEATABLE READ. Проверено: SHOW transaction_isolation → read committed. |
T17-L1 0.98 c | PostgreSQL: transactions and indexes | By default, PostgreSQL wraps each single SQL statement in its own implicit transaction (autocommit). | «yes» Пояснение: In autocommit mode, PostgreSQL automatically commits each individual SQL statement in its own transaction.
Raw{"answer":"yes","explanation":"In autocommit mode, PostgreSQL automatically commits each individual SQL statement in its own transaction."} | верно | Без BEGIN каждый оператор коммитится сам; docs PostgreSQL — Transactions. Проверено на PG 17. |
T17-L2 0.87 c | PostgreSQL: transactions and indexes | Which SQL command ends a transaction, committing all its changes? | «commit» Пояснение: The COMMIT command ends a transaction and permanently saves the changes made within it.
Raw{"answer": "COMMIT", "explanation": "The COMMIT command ends a transaction and permanently saves the changes made within it."} | верно | COMMIT (END — синоним). Проверено на PG 17. |
T17-L3 1.64 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 that filter rows using indexed columns by helping locate the matching rows quickly.
Raw{"answer": "yes", "explanation": "Indexes can speed up UPDATE and DELETE statements that filter rows using indexed columns by helping locate the matching rows quickly."} | верно | Поиск строк для изменения идёт по индексу; docs PostgreSQL — Indexes. |
T17-L4 1.11 c | PostgreSQL: transactions and indexes | To roll back part of the statements inside a transaction, PostgreSQL uses SAVEPOINT. | «yes» Пояснение: SAVEPOINT allows you to roll back a transaction to a specific point, undoing only the statements after that savepoint.
Raw{"answer":"yes","explanation":"SAVEPOINT allows you to roll back a transaction to a specific point, undoing only the statements after that savepoint."} | верно | SAVEPOINT name; ROLLBACK TO name — частичный откат без отмены всей транзакции. Проверено на PG 17. |
T17-L5 1.12 c | PostgreSQL: transactions and indexes | EXPLAIN ANALYZE shows the query plan without executing the query. | «no» Пояснение: EXPLAIN ANALYZE actually executes the query to collect real execution statistics, unlike plain EXPLAIN.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "EXPLAIN ANALYZE actually executes the query to collect real execution statistics, unlike plain EXPLAIN." ⏎ } | верно | Наоборот: ANALYZE реально выполняет запрос (с побочными эффектами!) и показывает фактические времена узлов; план без выполнения — plain EXPLAIN. |
T17-L6 1.11 c | PostgreSQL: transactions and indexes | Which PostgreSQL extension adds vector types and indexes for embedding search? | «pgvector» Пояснение: pgvector is a PostgreSQL extension that adds native vector data types and GIN/GiST indexes for vector similarity search, commonly used for embedding search in AI applications.
Raw{"answer": "pgvector", "explanation": "pgvector is a PostgreSQL extension that adds native vector data types and GIN/GiST indexes for vector similarity search, commonly used for embedding search in AI applications."} | верно | CREATE EXTENSION vector (проект pgvector; в проекте образ pgvector/pgvector:pg17). |
T17-L7 1.32 c | PostgreSQL: transactions and indexes | A partial index (CREATE INDEX ... WHERE ...) is built only over rows satisfying the condition. | «yes» Пояснение: A partial index in PostgreSQL (and similar databases) contains only the index entries for rows that satisfy the WHERE condition, making it smaller and more efficient for queries that filter by that same condition.
Raw{"answer": "yes", "explanation": "A partial index in PostgreSQL (and similar databases) contains only the index entries for rows that satisfy the WHERE condition, making it smaller and more efficient for queries that filter by that same condition."} | верно | docs PostgreSQL — Partial Indexes; типичный кейс — индекс по «активным» записям. |
T17-L8 2.31 c | PostgreSQL: transactions and indexes | The SERIALIZABLE level in PostgreSQL is implemented by locking the rows a transaction reads. | «no» Пояснение: PostgreSQL implements SERIALIZABLE using serializable snapshot isolation, not by locking the rows a transaction reads; it detects serializable anomalies (such as write skew) and aborts the transaction instead.
Raw{"answer": "no", "explanation": "PostgreSQL implements SERIALIZABLE using serializable snapshot isolation, not by locking the rows a transaction reads; it detects serializable anomalies (such as write skew) and aborts the transaction instead."} | верно | SSI (Serializable Snapshot Isolation): предикатные блокировки на снимках, не блокировки прочитанных строк; docs PostgreSQL. |
T19-L1 0.87 c | HTTP and REST API | HTTP status 201 means the request resulted in a new resource being created. | «yes» Пояснение: HTTP 201 indicates that the request successfully created a new resource.
Raw{"answer": "yes", "explanation": "HTTP 201 indicates that the request successfully created a new resource."} | верно | 201 Created; обычно на POST, часто с Location; RFC 9110. |
T19-L2 1.27 c | HTTP and REST API | Which HTTP status means a successful request with an empty response body (e.g. after DELETE)? | «204» Пояснение: HTTP 204 No Content indicates success with no response body, commonly used after a successful DELETE.
Raw{"answer": 204, "explanation": "HTTP 204 No Content indicates success with no response body, commonly used after a successful DELETE."} | верно | 204 No Content; RFC 9110. |
T19-L3 2.76 c | HTTP and REST API | The DELETE method is idempotent per the HTTP specification: repeating the request for the same resource does not change the outcome. | «yes» Пояснение: The HTTP specification (RFC 7231) defines DELETE as an idempotent method: a second DELETE for an already-deleted resource has no further effect, so repeating the request does not change the outcome beyond the first.
Raw{"answer": "yes", "explanation": "The HTTP specification (RFC 7231) defines DELETE as an idempotent method: a second DELETE for an already-deleted resource has no further effect, so repeating the request does not change the outcome beyond the first."} | верно | RFC 9110: DELETE идемпотентен (как PUT); идемпотентность ≠ безопасность — ресурс удаляется при первом вызове. |
T19-L4 1.04 c | HTTP and REST API | The Access-Control-Allow-Origin header is sent by the client so that the server agrees to accept requests from another origin. | «no» Пояснение: The Access-Control-Allow-Origin header is sent by the server, not the client, to indicate which origins are allowed to access the resource.
Raw{"answer":"no","explanation":"The Access-Control-Allow-Origin header is sent by the server, not the client, to indicate which origins are allowed to access the resource."} | верно | Наоборот: заголовок шлёт СЕРВЕР в ответе, разрешая браузеру cross-origin запрос (CORS); в проекте nelmio/cors-bundle. |
T19-L5 0.97 c | HTTP and REST API | Status 429 Too Many Requests is used when a client exceeds a rate limit. | «yes» Пояснение: HTTP status 429 Too Many Requests is specifically used to indicate that a client has exceeded the server's rate limit.
Raw{"answer": "yes", "explanation": "HTTP status 429 Too Many Requests is specifically used to indicate that a client has exceeded the server's rate limit."} | верно | 429 (+ Retry-After); RFC 6585. В проекте symfony/rate-limiter. |
T19-L6 1.06 c | HTTP and REST API | 5xx codes mean a client error, while 4xx means a server-side error. | «no» Пояснение: It's the opposite: 4xx codes indicate client errors, while 5xx codes indicate server errors.
Raw{"answer": "no", "explanation": "It's the opposite: 4xx codes indicate client errors, while 5xx codes indicate server errors."} | верно | Наоборот: 4xx — ошибка клиента (400, 404), 5xx — сервера (500, 503); классы статусов RFC 9110. |
T19-L7 0.97 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 3.74 c | HTTP and REST API | PATCH is not required to be idempotent per RFC 5789, unlike PUT. | «yes» Пояснение: RFC 5789 explicitly states that PATCH is not required to be idempotent, unlike PUT, which is idempotent by definition in the HTTP specification.
Raw{"answer": "yes", "explanation": "RFC 5789 explicitly states that PATCH is not required to be idempotent, unlike PUT, which is idempotent by definition in the HTTP specification."} | верно | RFC 5789 прямо оговаривает: PATCH не гарантированно идемпотентен; PUT идемпотентен. |
T20-L1 2.84 c | Security and OAuth | Checking a password by comparing its hash to the stored hash with a plain == is sufficient. | «no» Пояснение: Use password_verify() or hash_equals() because a plain == comparison is not safe or reliable for hash validation.
Raw{"answer": "no", "explanation": "Use password_verify() or hash_equals() because a plain == comparison is not safe or reliable for hash validation."} | верно | Нужна постоянновременная проверка (password_verify) — timing-атаки; соль и алгоритм уже внутри хеша. |
T20-L2 0.78 c | Security and OAuth | A CSRF token is issued by the server (bound to the session) and verified server-side on unsafe requests (POST etc.). | «yes» Пояснение: CSRF tokens are server-generated, session-bound values checked server-side on state-changing requests.
Raw{"answer": "yes", "explanation": "CSRF tokens are server-generated, session-bound values checked server-side on state-changing requests."} | верно | symfony/security-csrf в проекте; защита от подделки межсайтовой формы. |
T20-L3 0.97 c | Security and OAuth | Which HTTP header enables the CSP (Content Security Policy) policy? | «content-security-policy» Пояснение: The Content-Security-Policy HTTP header is used to declare and enforce CSP.
Raw{"answer": "Content-Security-Policy", "explanation": "The Content-Security-Policy HTTP header is used to declare and enforce CSP."} | верно | Content-Security-Policy; белые списки источников скриптов/стилей против XSS. |
T20-L4 1.18 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 primarily an authorization framework, and access tokens are used to grant permission rather than identify the user.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "OAuth 2.0 is primarily an authorization framework, and access tokens are used to grant permission rather than identify the user." ⏎ } | верно | OAuth 2.0 — авторизация/делегирование доступа; аутентификацию добавляет OpenID Connect. В проекте knpuniversity/oauth2-client-bundle (yandex/github/google). |
T20-L5 1.11 c | Security and OAuth | XSS is prevented by validating input on the server before writing it to the database. | «no» Пояснение: Preventing XSS mainly requires context-specific output encoding when data is displayed, not just input validation before storage.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "Preventing XSS mainly requires context-specific output encoding when data is displayed, not just input validation before storage." ⏎ } | верно | XSS лечится контекстным экранированием НА ВЫВОДЕ (Twig autoescape, CSP); валидация ввода не покрывает все контексты вывода. |
T20-L6 1.5 c | Security and OAuth | In the OAuth 2.0 authorization code flow, which parameter arrives at the redirect_uri and is exchanged for an access token? | «code» Пояснение: In the OAuth 2.0 authorization code flow, the authorization server sends an authorization code in the 'code' query parameter to the redirect_uri, which the client then exchanges at the token endpoint for an access token.
Raw{"answer": "code", "explanation": "In the OAuth 2.0 authorization code flow, the authorization server sends an authorization code in the 'code' query parameter to the redirect_uri, which the client then exchanges at the token endpoint for an access token."} | верно | Параметр code; обмен на токен POST-ом на /token с client_secret. |
T20-L7 1.06 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 typically have longer validity periods and are used to obtain new access tokens without requiring the user to log in again.
Raw{"answer": "yes", "explanation": "Refresh tokens typically have longer validity periods and are used to obtain new access tokens without requiring the user to log in again."} | верно | Стандартная схема OAuth/OIDC: короткий access + длинный refresh. |
T20-L8 1.3 c | Security and OAuth | A password salt must be kept secret: without it the hash cannot be verified. | «no» Пояснение: A password salt is usually stored with the hash and does not need to be kept secret.
Raw{"answer": "no", "explanation": "A password salt is usually stored with the hash and does not need to be kept secret."} | верно | Соль хранится открыто (password_hash включает её в строку хеша); секретность соли не нужна. |
T18-L1 94.15 c | Testing: PHPUnit | PHPUnit runs test methods of any class — extending TestCase is not required. | «yes» Пояснение: PHPUnit discovers test methods by the "test" prefix and does not require the test class to extend TestCase.
Raw{"answer": "yes", "explanation": "PHPUnit discovers test methods by the \"test\" prefix and does not require the test class to extend TestCase."} | неверно верный: «no» | Тестом считается метод класса, наследующего TestCase (PHPUnit 10). |
T18-L2 3.65 c | Testing: PHPUnit | In PHPUnit, setUp() runs once before all tests of the class. | «no» Пояснение: setUp() runs before each individual test method, not once; the method that runs once before all tests is setUpBeforeClass().
Raw{"answer": "no", "explanation": "setUp() runs before each individual test method, not once; the method that runs once before all tests is setUpBeforeClass()."} | верно | setUp() — перед КАЖДЫМ тестом; один раз на класс — setUpBeforeClass(). Проверено живым счётчиком на PHPUnit 10.5. |
T18-L3 1.17 c | Testing: PHPUnit | A data provider lets a test run with exactly one set of arguments. | «no» Пояснение: A data provider lets a test run with multiple sets of arguments, not exactly one.
Raw{"answer": "no", "explanation": "A data provider lets a test run with multiple sets of arguments, not exactly one."} | верно | Наоборот: наборов может быть сколько угодно — тест выполняется по разу на каждый. Проверено на PHPUnit 10.5 (#[DataProvider]). |
T18-L4 1.32 c | Testing: PHPUnit | Which PHPUnit method declares an expectation that an exception of a given class is thrown? | «expectexception()» Пояснение: expectException() is the PHPUnit method that sets an expectation that a specific exception class will be thrown when the test code runs.
Raw{"answer":"expectException()","explanation":"expectException() is the PHPUnit method that sets an expectation that a specific exception class will be thrown when the test code runs."} | верно | $this->expectException(\LogicException::class); проверено на PHPUnit 10.5. |
T18-L5 0.85 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 only returns data.
Raw{"answer": "no", "explanation": "In PHPUnit, a mock verifies method calls while a stub only returns data."} | верно | Наоборот: стаб подставляет данные, мок проверяет взаимодействия (createStub/createMock); docs PHPUnit — Test Doubles. |
T18-L6 1.44 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 way to attach a data provider to a test, while the @dataProvider annotation is deprecated.
Raw{"answer":"yes","explanation":"In PHPUnit 10+, the #[DataProvider] attribute is the recommended way to attach a data provider to a test, while the @dataProvider annotation is deprecated."} | верно | Аннотация ещё парсится в PHPUnit 10/11 (AnnotationParser в 10.5.66), удаление — в 12; атрибут — стандарт. |
T18-L7 33.06 c | Testing: PHPUnit | PHPUnit does not allow one test to depend on the result of another. | «no» Пояснение: PHPUnit supports @depends (and the Depends attribute) to declare test dependencies, although such dependencies are discouraged.
Raw{"answer":"no","explanation":"PHPUnit supports @depends (and the Depends attribute) to declare test dependencies, although such dependencies are discouraged."} | верно | Зависимости есть: #[Depends] — зависимый тест не запустится, еслиProducer упал. |
T18-L8 0.87 c | Testing: PHPUnit | Which PHPUnit command-line option makes tests run in random order? | «--random-order» Пояснение: PHPUnit 11 introduced the --random-order command-line option to shuffle the order in which tests are executed.
Raw{"answer": "--random-order", "explanation": "PHPUnit 11 introduced the --random-order command-line option to shuffle the order in which tests are executed."} | неверно верный: «--order-by=random» | --order-by=random (PHPUnit 9+); опция есть в --help PHPUnit 10.5 (проектная). |
T01-L9 3.4 c | Syntax and operators | What does this code output?
```php
echo intdiv(7, 2) . intdiv(-7, 2);
``` | «3-4» Пояснение: intdiv(7, 2) is 3 and intdiv(-7, 2) is -4 because PHP intdiv truncates toward negative infinity, so concatenation outputs 3-4.
Raw{ ⏎ "answer": "3-4", ⏎ "explanation": "intdiv(7, 2) is 3 and intdiv(-7, 2) is -4 because PHP intdiv truncates toward negative infinity, so concatenation outputs 3-4." ⏎ } | неверно верный: «3-3» | intdiv truncates toward zero: intdiv(-7, 2) = -3, not -4. |
T01-L10 142.07 c | Syntax and operators | What does this code output?
```php
echo -3 ** 2;
``` | «-9» Пояснение: In PHP, ** has higher precedence than unary minus, so the code is parsed as -(3 ** 2).
Raw{"answer": -9, "explanation": "In PHP, ** has higher precedence than unary minus, so the code is parsed as -(3 ** 2)."} | верно | ** is right-associative and binds tighter than unary minus: -(3²). |
T02-L9 1.89 c | Types and comparisons | What does this code output?
```php
echo '1e1' == '10' ? 'true' : 'false';
``` | «true» Пояснение: PHP compares both numeric strings as numbers, so 1e1 equals 10.
Raw{ ⏎ "answer": "true", ⏎ "explanation": "PHP compares both numeric strings as numbers, so 1e1 equals 10." ⏎ } | верно | Both strings are numeric — compared as numbers: 10 == 10. |
T02-L10 4.91 c | Types and comparisons | What does this code output?
```php
switch ('a') {
case 0: echo 'zero'; break;
default: echo 'other';
}
``` | «other» Пояснение: The switch subject 'a' does not match case 0, so the default case runs.
Raw{"answer":"other","explanation":"The switch subject 'a' does not match case 0, so the default case runs."} | верно | PHP 8: 'a' == 0 → false (used to be true) — default fires. |
T03-L9 8.27 c | Strings | What does this code output?
```php
echo strtr('abc', ['a' => '1', 'ab' => '2']);
``` | «2c» Пояснение: strtr replaces the longest matching substring first, so 'ab' is replaced by '2'.
Raw{"answer":"2c","explanation":"strtr replaces the longest matching substring first, so 'ab' is replaced by '2'."} | верно | strtr with an array prefers the longest matching key. |
T03-L10 1.77 c | Strings | What does this code output?
```php
echo '[' . substr('hello', -10) . ']';
``` | «[hello]» Пояснение: The negative start value of -10 is less than the string length, so substr() starts at the beginning of 'hello'.
Raw{ ⏎ "answer": "[hello]", ⏎ "explanation": "The negative start value of -10 is less than the string length, so substr() starts at the beginning of 'hello'." ⏎ } | верно | A negative start beyond the string is clamped to the beginning. |
T04-L9 1.6 c | Arrays | What does this code output?
```php
$a = ['k' => 1, 'n' => 2];
$b = ['k' => 9, 'm' => 3];
echo implode(',', array_keys($a + $b));
``` | «k,n,m» Пояснение: The array union keeps the left array's 'k' value and adds the right array's 'm' key, yielding keys k, n, and m.
Raw{ ⏎ "answer": "k,n,m", ⏎ "explanation": "The array union keeps the left array's 'k' value and adds the right array's 'm' key, yielding keys k, n, and m." ⏎ } | верно | The + operator: on duplicate string keys the left array wins. |
T04-L10 9.55 c | Arrays | What does this code output?
```php
$a = [[1, 'x', 2], [2, 'y', 1], [3, 'z', 2]];
usort($a, fn($p, $q) => $p[2] <=> $q[2]);
echo implode('', array_column($a, 1));
``` | «yxz» Пояснение: usort orders the sub-arrays by their third element (1, 2, 2), giving [2,'y',1], [1,'x',2], [3,'z',2]; array_column picks index 1 yielding ['y','x','z'] which implode to 'yxz'.
Raw```json ⏎ {"answer": "yxz", "explanation": "usort orders the sub-arrays by their third element (1, 2, 2), giving [2,'y',1], [1,'x',2], [3,'z',2]; array_column picks index 1 yielding ['y','x','z'] which implode to 'yxz'."} ⏎ ``` | верно | Sorts are stable since 8.0: x and z keep their order on a tie. |
T05-L10 6.63 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 array unpacks as named arguments a=5 and b=1, so the function returns 5 - 1.
Raw{"answer": 4, "explanation": "The array unpacks as named arguments a=5 and b=1, so the function returns 5 - 1."} | верно | String keys of a spread array become named arguments. |
T05-L9 21.33 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» Пояснение: $p->g(...) creates a first-class callable bound to the P object, so the object survives $p = null and $f() returns its private v.
Raw{"answer":3,"explanation":"$p->g(...) creates a first-class callable bound to the P object, so the object survives $p = null and $f() returns its private v."} | верно | First-class callable syntax binds $this at creation time. |
T06-L9 11.7 c | OOP: classes and inheritance | What does this code output?
```php
class A
{
public function who(): string { return static::class; }
}
class B extends A {}
echo (new B)->who();
``` | «b» Пояснение: static::class uses late static binding, so it returns the class from which the method was actually called, B.
Raw{"answer": "B", "explanation": "static::class uses late static binding, so it returns the class from which the method was actually called, B."} | верно | Late static binding: static::class is the receiver's class. |
T06-L10 143.8 c | OOP: classes and inheritance | What does this code output on PHP 8.5?
```php
class C
{
public int $x = 0 {
set { $this->x = $value * 2; }
}
}
$c = new C;
$c->x = 5;
echo $c->x;
``` | «10» Пояснение: The setter stores the doubled value 10, and reading the property with no getter returns that stored value.
Raw{ ⏎ "answer": 10, ⏎ "explanation": "The setter stores the doubled value 10, and reading the property with no getter returns that stored value." ⏎ } | верно | Inside the set hook, $this->x writes the backing store (no recursion): 5*2. |
T07-L9 18.9 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» Пояснение: The conflict is resolved so f uses TB, and TA::f is aliased as g, so f() returns 'B' and g() returns 'A'.
Raw{ ⏎ "answer": "BA", ⏎ "explanation": "The conflict is resolved so f uses TB, and TA::f is aliased as g, so f() returns 'B' and g() returns 'A'." ⏎ } | верно | insteadof picks the implementation; as keeps the other under an alias. |
T07-L10 19.65 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 the trait gets its own static property, so CY::$n is unchanged.
Raw{"answer": 0, "explanation": "Each class that uses the trait gets its own static property, so CY::$n is unchanged."} | верно | A trait's static property is copied into each consuming class. |
T08-L10 12.64 c | Exceptions and errors | What does this code output?
```php
function f(): int
{
try { return 1; } finally { return 2; }
}
echo f();
``` | «2» Пояснение: A return statement in a finally block overrides the return value from the try block.
Raw{ ⏎ "answer": 2, ⏎ "explanation": "A return statement in a finally block overrides the return value from the try block." ⏎ } | верно | A return in finally overrides the return from try. |
T08-L9 15.81 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 exception thrown in the finally block replaces the original RuntimeException and is caught by the outer catch.
Raw{"answer": "second", "explanation": "The exception thrown in the finally block replaces the original RuntimeException and is caught by the outer catch."} | верно | An exception from finally replaces the in-flight one — the last thrown is caught. |
T09-L9 47.16 c | Namespaces and autoloading | What does this code output?
```php
namespace N;
use App\Foo as Baz;
echo Baz::class . '|' . \Baz::class;
``` | «app\foo|baz» Пояснение: Baz is an alias for App\Foo, while \Baz::class resolves to the global class name Baz.
Raw{"answer": "App\\Foo|Baz", "explanation": "Baz is an alias for App\\Foo, while \\Baz::class resolves to the global class name Baz."} | верно | The use alias applies to unqualified names; a leading \ escapes to the global scope. |
T09-L10 19.39 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» Пояснение: In namespace Ns, class_exists('Foo') finds Ns\Foo, and class_exists('Ns\Foo') also finds it, so both parts output yes.
Raw{ ⏎ "answer": "yesyes", ⏎ "explanation": "In namespace Ns, class_exists('Foo') finds Ns\\Foo, and class_exists('Ns\\Foo') also finds it, so both parts output yes." ⏎ } | неверно верный: «noyes» | Dynamic names are not resolved against the namespace — 'Foo' is the global class. |
T10-L9 90.93 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» Пояснение: A foreach by reference leaves $v referencing the last array element, so assigning $v = 99 modifies $a[2].
Raw{ ⏎ "answer": "1,2,99", ⏎ "explanation": "A foreach by reference leaves $v referencing the last array element, so assigning $v = 99 modifies $a[2]." ⏎ } | верно | After a by-ref foreach, $v remains a reference to the last element. |
T10-L10 57.76 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 is shared by all calls to A's inc() method, including from B, so the third call returns 3.
Raw{"answer": 3, "explanation": "The static variable is shared by all calls to A's inc() method, including from B, so the third call returns 3."} | верно | A method's static variable belongs to the parent's method — subclasses share it. |
T11-L9 19.09 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» Пояснение: The first send(10) starts the generator, which yields 1, assigns 10 to $x, then executes return $x + 1 = 11.
Raw{"answer": 11, "explanation": "The first send(10) starts the generator, which yields 1, assigns 10 to $x, then executes return $x + 1 = 11."} | верно | send() resumes the generator: $x = 10, return 10+1. |
T11-L10 125.63 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 yields 1 and 2, assigns the inner return value 'ok' to $r, and outer then yields that value once.
Raw{"answer":"1,2,ok","explanation":"yield from yields 1 and 2, assigns the inner return value 'ok' to $r, and outer then yields that value once."} | неверно верный: «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 21.45 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 uses the same algorithm and cost, so no rehash is needed; the second uses a higher cost, so rehashing is recommended.
Raw{ ⏎ "answer": "noyes", ⏎ "explanation": "The first call uses the same algorithm and cost, so no rehash is needed; the second uses a higher cost, so rehashing is recommended." ⏎ } | верно | password_needs_rehash compares the hash's options with the target: cost 4 = 4 → 'no', cost 5 ≠ 4 → 'yes'. |
T12-L10 144.41 c | Configuration and security | What does this code output on PHP 8.5?
```php
echo (E_ALL & 2048) === 0 ? 'strict-out' : 'strict-in';
``` | «strict-out» Пояснение: In PHP 8.5, bit 2048 (E_USER_ERROR) is no longer included in E_ALL, so the bitwise AND is zero.
Raw{"answer": "strict-out", "explanation": "In PHP 8.5, bit 2048 (E_USER_ERROR) is no longer included in E_ALL, so the bitwise AND is zero."} | верно | 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 124.97 c | Symfony | What does this code output?
```php
use Symfony\Component\HttpFoundation\Request;
$r = Request::create('/demo', 'GET', [], [], [], ['HTTP_X_TOKEN' => 'abc']);
echo $r->headers->get('X-Token') === 'abc' ? 'mapped' : 'missing';
``` | «mapped» Пояснение: Symfony normalizes the header HTTP_X_TOKEN to x-token, so get('X-Token') returns 'abc'.
Raw{ ⏎ "answer": "mapped", ⏎ "explanation": "Symfony normalizes the header HTTP_X_TOKEN to x-token, so get('X-Token') returns 'abc'." ⏎ } | верно | The literal comparison requires knowing the mapping: HttpFoundation turns HTTP_X_TOKEN into the X-Token header (case-insensitive); without it the answer is 'missing'. |
T13-L10 19.72 c | Symfony | What does this code output?
```php
use Symfony\Component\EventDispatcher\EventDispatcher;
use Symfony\Contracts\EventDispatcher\Event;
$d = new EventDispatcher();
$out = '';
$d->addListener('e', function () use (&$out) { $out .= 'B'; }, 10);
$d->addListener('e', function () use (&$out) { $out .= 'A'; });
$d->addListener('e', function () use (&$out) { $out .= 'C'; }, 5);
$d->dispatch(new Event(), 'e');
echo $out;
``` | «bca» Пояснение: Listeners run in descending priority order: 10 for B, 5 for C, and the default 0 for A.
Raw{"answer": "BCA", "explanation": "Listeners run in descending priority order: 10 for B, 5 for C, and the default 0 for A."} | верно | Listeners run by descending priority: 10 (B), 5 (C), 0 (A). |
T14-L10 16.57 c | Doctrine | Given: Doctrine ORM 3, an EntityManager on in-memory SQLite, entity User with an auto-increment primary key. The users table is empty. What does this code output?
```php
$u = new User(name: 'A');
$em->persist($u);
$em->flush();
$a = $em->find(User::class, $u->getId());
$b = $em->find(User::class, $u->getId());
echo spl_object_id($a) === spl_object_id($b) ? 'same' : 'diff';
``` | «same» Пояснение: Doctrine's EntityManager identity map returns the same already-loaded User instance for the same ID within the same EntityManager.
Raw{ ⏎ "answer": "same", ⏎ "explanation": "Doctrine's EntityManager identity map returns the same already-loaded User instance for the same ID within the same EntityManager." ⏎ } | верно | Identity map: a second find for the same id returns the same instance. |
T14-L9 108.22 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» Пояснение: Removing the entity before flush cancels the pending insert, so no row is created.
Raw{"answer":0,"explanation":"Removing the entity before flush cancels the pending insert, so no row is created."} | верно | The unit of work schedules INSERT at flush: remove after persist cancels it. |
T15-L10 15.82 c | PostgreSQL | What does this SQL query return (PostgreSQL 17)?
```sql
CREATE TEMP TABLE t (x int);
INSERT INTO t VALUES (1), (NULL);
SELECT count(x) FROM t;
``` | «1» Пояснение: count(x) counts non-null values, so only 1 is counted while NULL is ignored.
Raw{"answer": 1, "explanation": "count(x) counts non-null values, so only 1 is counted while NULL is ignored."} | верно | count(column) skips NULLs; count(*) would return 2. |
T15-L9 16.99 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 running totals 10, 30, and 60, and string_agg concatenates them in id order.
Raw{"answer":"10,30,60","explanation":"The window sum produces running totals 10, 30, and 60, and string_agg concatenates them in id order."} | верно | With ORDER BY the default window frame is running (start to current row). |
T16-L9 35.4 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 MessageBus middleware chain processes in order, with the first middleware in the array being outermost, so M1 echoes first then M2 echoes before delegating to the next handler.
Raw{"answer": "M1M2", "explanation": "The MessageBus middleware chain processes in order, with the first middleware in the array being outermost, so M1 echoes first then M2 echoes before delegating to the next handler."} | верно | The first-added middleware runs first (outermost). |
T16-L10 22.84 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 are invoked, incrementing n by 1 and then by 10.
Raw{ ⏎ "answer": 11, ⏎ "explanation": "Both handlers are invoked, incrementing n by 1 and then by 10." ⏎ } | верно | All registered handlers of the message run: 1 + 10 = 11. |
T17-L9 17.59 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 second insert of 1 conflicts with the unique index and is ignored, so one row remains.
Raw{"answer": 1, "explanation": "The second insert of 1 conflicts with the unique index and is ignored, so one row remains."} | верно | ON CONFLICT DO NOTHING skips the duplicate: one insert. |
T17-L10 18.65 c | PostgreSQL: transactions and indexes | What does this sequence of psql commands output?
```sql
BEGIN;
CREATE TEMP TABLE t (a int, UNIQUE (a) DEFERRABLE INITIALLY DEFERRED);
INSERT INTO t VALUES (1);
INSERT INTO t VALUES (1);
SELECT count(*) FROM t;
``` | «2» Пояснение: The deferrable unique constraint is initially deferred, so duplicate inserts succeed within the transaction until it commits or rolls back.
Raw{"answer": 2, "explanation": "The deferrable unique constraint is initially deferred, so duplicate inserts succeed within the transaction until it commits or rolls back."} | верно | DEFERRED postpones the uniqueness check to COMMIT — count sees 2 rows. |
T18-L9 40.9 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» Пояснение: --filter uses an unanchored regex on test method names, so it matches both test_sum and test_sum_abs, each running with the three data-provider values.
Raw{"answer":6,"explanation":"--filter uses an unanchored regex on test method names, so it matches both test_sum and test_sum_abs, each running with the three data-provider values."} | верно | --filter is a substring match: test_sum also matches test_sum_abs (3+3 datasets). |
T18-L10 23.05 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 DataProvider supplies two datasets (1 and -1), and the assertion fails only for -1.
Raw{"answer": "2,1", "explanation": "The DataProvider supplies two datasets (1 and -1), and the assertion fails only for -1."} | верно | 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 17.65 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 the POST method by default.
Raw{"answer": "POST", "explanation": "curl's -d option sends the data in the body using the POST method by default."} | верно | -d/-F switches curl to POST by default. |
T19-L10 18.63 c | HTTP and REST API | Which HTTP method does this command send?
```bash
curl -s -G -d 'a=1' http://demo.local/api
``` | «get» Пояснение: The -G flag forces curl to use the HTTP GET method and send the -d data as a query string.
Raw{"answer": "GET", "explanation": "The -G flag forces curl to use the HTTP GET method and send the -d data as a query string."} | верно | -G turns -d data into the query string; the method stays GET. |
T20-L9 21.08 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» Пояснение: A non-existent client_id is reported by the token endpoint as an invalid client error under RFC 6749.
Raw{ ⏎ "answer": "invalid_client", ⏎ "explanation": "A non-existent client_id is reported by the token endpoint as an invalid client error under RFC 6749." ⏎ } | верно | Unknown client → invalid_client (RFC 6749 §5.2). |
T20-L10 35.39 c | Security and OAuth | OAuth 2.0: the client started the flow with response_type=token. In which part of the redirect_uri does the authorization server pass the access_token? | «fragment» Пояснение: In the OAuth 2.0 implicit flow (response_type=token), the access_token is passed in the fragment (the part after the #) of the redirect_uri.
Raw{"answer":"fragment","explanation":"In the OAuth 2.0 implicit flow (response_type=token), the access_token is passed in the fragment (the part after the #) of the redirect_uri."} | верно | The implicit flow passes the token in the URL fragment (#) — it never reaches the server. |
T21-L9 49.0 c | Twig | What does this Twig template output?
```twig
{{ false|default(2) * 3 }}
``` | «0» Пояснение: In Twig, false is not undefined or null, so default(2) keeps false, and false * 3 evaluates to 0.
Raw{"answer": 0, "explanation": "In Twig, false is not undefined or null, so default(2) keeps false, and false * 3 evaluates to 0."} | неверно верный: «6» | default replaces exactly false/null/''/[] — false becomes 2, 2*3 = 6; the naive 'default is for undefined only' yields 0. |
T21-L10 310.11 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 15.23 c | Symfony: Security and forms | What does this code output?
```php
use Symfony\Component\Validator\Validation;
use Symfony\Component\Validator\Constraints as Assert;
$v = Validation::createValidator();
echo count($v->validate([''], [new Assert\NotBlank()]));
``` | «0» Пояснение: The array [''] is not empty, so NotBlank does not produce a violation.
Raw{ ⏎ "answer": 0, ⏎ "explanation": "The array [''] is not empty, so NotBlank does not produce a violation." ⏎ } | верно | NotBlank treats null, '', [] as blank — the array [''] is not blank. |
T22-L10 260.2 c | Symfony: Security and forms | What does this code output?
```php
use Symfony\Component\Form\Forms;
use Symfony\Component\Form\Extension\Core\Type\TextType;
$factory = Forms::createFormFactoryBuilder()->getFormFactory();
$form = $factory->create(TextType::class);
try {
echo $form->isValid() ? 'valid' : 'invalid';
} catch (Throwable $e) {
echo get_class($e);
}
``` | «valid» Пояснение: The form has no validator and no validation errors, so isValid() returns true.
Raw{"answer": "valid", "explanation": "The form has no validator and no validation errors, so isValid() returns true."} | неверно верный: «symfony\component\form\exception\logicexception» | isValid() on a non-submitted form throws LogicException, it does not return false. |
T23-L9 13.3 c | Symfony: configuration and services | What does this code output?
```php
use Symfony\Component\DependencyInjection\ContainerBuilder;
$c = new ContainerBuilder();
$c->register('a', stdClass::class)->setPublic(true);
$c->compile();
echo spl_object_id($c->get('a')) === spl_object_id($c->get('a')) ? 'same' : 'diff';
``` | «same» Пояснение: Symfony's DI container caches instantiated services, so calling get('a') twice returns the same object instance.
Raw{"answer":"same","explanation":"Symfony's DI container caches instantiated services, so calling get('a') twice returns the same object instance."} | верно | Container services are shared: two get() calls yield one instance. |
T23-L10 193.98 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');
``` | «%greeting%» Пояснение: The trailing ! marks the placeholder as literal, so compile does not replace it.
Raw{ ⏎ "answer": "%greeting%", ⏎ "explanation": "The trailing ! marks the placeholder as literal, so compile does not replace it." ⏎ } | неверно верный: «hi bob!» | compile() resolves %-references transitively: %greeting% → 'hi %name%' → 'hi Bob!', the answer assembles over two hops. |
T24-L9 14.25 c | Bootstrap | What is the max-width of .container in Bootstrap 5.3 at a 992px viewport? | «960px» Пояснение: In Bootstrap 5.3, the .container's max-width at min-width: 992px is 960px.
Raw{"answer": "960px", "explanation": "In Bootstrap 5.3, the .container's max-width at min-width: 992px is 960px."} | верно | 5.x container widths: 540/720/960/1140/1320 (sm–xxl); 992 → 960px. |
T24-L10 25.69 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, same-specificity utility classes are resolved by source order in the compiled CSS, where .text-danger is generated after .text-primary, so .text-danger wins the cascade.
Raw{"answer":"text-danger","explanation":"In Bootstrap 5.3, same-specificity utility classes are resolved by source order in the compiled CSS, where .text-danger is generated after .text-primary, so .text-danger wins the cascade."} | верно | Specificity ties — the later rule wins: text-danger is declared after text-primary. |
T25-L9 20.66 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 an Application class and an Infrastructure class, so deptrac reports two violations.
Raw{ ⏎ "answer": 2, ⏎ "explanation": "The Domain class depends on an Application class and an Infrastructure class, so deptrac reports two violations." ⏎ } | верно | Domain may depend only on Domain: PlaceOrder (Application) + Db (Infrastructure) = 2. |
T25-L10 33.58 c | Clean architecture | Layers: Domain, Application, Infrastructure. Deptrac rules: Application → Domain; Infrastructure → Domain, Application; Domain → Domain only.
How many violations will deptrac report for this class?
```php
namespace App\Domain;
use App\Application\PlaceOrder;
use App\Infrastructure\Db;
class BillingService
{
public function __construct(
private PlaceOrder $handler,
private Db $db,
private \App\Infrastructure\Logger $logger,
) {}
}
``` | «3» Пояснение: The Domain class depends on one Application class and two Infrastructure classes, and Domain may depend on Domain only.
Raw{ ⏎ "answer": 3, ⏎ "explanation": "The Domain class depends on one Application class and two Infrastructure classes, and Domain may depend on Domain only." ⏎ } | верно | The inline FQCN \App\Infrastructure\Logger counts too: Application + Db + Logger = 3. |
T26-L10 34.17 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 10 for $a and the new Money object from add has 15, so concatenation outputs the string 10,15.
Raw{"answer": "10,15", "explanation": "The readonly amount is 10 for $a and the new Money object from add has 15, so concatenation outputs the string 10,15."} | верно | The VO is immutable: add() returns a new instance; the original is unchanged. |
T26-L9 47.72 c | DDD | What does this code output?
```php
final class Order
{
private array $items = [];
public function add(string $sku): void
{
$this->items[$sku] = true;
}
public function count(): int
{
return count($this->items);
}
public function remove(string $sku): void
{
if (count($this->items) === 1) {
throw new DomainException('last item');
}
unset($this->items[$sku]);
}
}
$o = new Order;
$o->add('a');
try {
$o->remove('a');
} catch (DomainException) {
}
echo $o->count();
``` | «1» Пояснение: The remove call throws DomainException before unset executes, so 'a' remains in $items, and count returns 1.
Raw{"answer": "1", "explanation": "The remove call throws DomainException before unset executes, so 'a' remains in $items, and count returns 1."} | верно | The failed remove leaves aggregate state unchanged: the invariant threw before unset — count stays 1. |
VC-L9 41.51 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 object's hi method returns the string 'hi', which echo outputs.
Raw{"answer": "hi", "explanation": "The object's hi method returns the string 'hi', which echo outputs."} | верно | Since 8.4, new in a method chain works without wrapping parentheses. |
VC-L10 115.49 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» Пояснение: Accessing $o->v triggers initialization of the lazy ghost, so the flag goes from true to false.
Raw{"answer":"yesno","explanation":"Accessing $o->v triggers initialization of the lazy ghost, so the flag goes from true to false."} | верно | newLazyGhost (8.4): the object stays lazy until first access — reading a property initializes it and clears the flag. |
T28-L9 11.2 c | Symfony: versions | The project was upgraded from Symfony 6.4 to 8.1. What does this code output on 8.1?
```php
echo class_exists(\Symfony\Component\Security\Guard\AbstractGuardAuthenticator::class)
? 'yes' : 'no';
``` | «no» Пояснение: The Symfony Guard component, including AbstractGuardAuthenticator, was removed in later Symfony versions, so the class does not exist in Symfony 8.1.
Raw{"answer":"no","explanation":"The Symfony Guard component, including AbstractGuardAuthenticator, was removed in later Symfony versions, so the class does not exist in Symfony 8.1."} | верно | Guard authentication was removed in Symfony 7.0 — the class is gone in 8.1. |
T28-L10 133.24 c | Symfony: versions | The project was upgraded from Symfony 6.4 to 8.1. What does this code output on 8.1?
```php
echo class_exists(\Symfony\Component\Routing\Loader\AnnotationClassLoader::class)
? 'yes' : 'no';
echo class_exists(\Symfony\Component\Routing\Loader\AttributeClassLoader::class)
? 'yes' : 'no';
``` | «noyes» Пояснение: Symfony 8.1 removed AnnotationClassLoader while AttributeClassLoader remains, so the script prints no then yes.
Raw{"answer": "noyes", "explanation": "Symfony 8.1 removed AnnotationClassLoader while AttributeClassLoader remains, so the script prints no then yes."} | верно | Annotation loaders were removed in 7.0; only attribute loaders remain (Annotation→Attribute). |