Пример запроса (первая клетка). System одинаковый во всех запросах прогона, user — свой вопрос для каждой клетки:
| Клетка | Тема | Утверждение | Ответ |
Результат | Обоснование |
T01-L1 3.24 c | Syntax and operators | Double-quoted and single-quoted strings are processed identically; the difference is only in speed. | «no» Пояснение: Double-quoted strings support variable interpolation and many escape sequences, while single-quoted strings do not except for \$ and \'.
Raw{"answer":"no","explanation":"Double-quoted strings support variable interpolation and many escape sequences, while single-quoted strings do not except for \\$ and \\'."} | верно | В двойных кавычках работают интерполяция переменных и escape-последовательности, в одинарных — нет. |
T01-L2 1.48 c | Syntax and operators | The ?? operator follows isset semantics and raises no warnings for undefined variables. | «yes» Пояснение: The null coalescing operator uses isset-like evaluation, so undefined variables do not generate warnings.
Raw{"answer": "yes", "explanation": "The null coalescing operator uses isset-like evaluation, so undefined variables do not generate warnings."} | верно | ?? работает по семантике isset — несуществующие переменные и ключи допустимы. |
T01-L3 0.75 c | Syntax and operators | What will this print: echo 'a', 'b'; | «ab» Пояснение: The echo function outputs the arguments in sequence without separating them with spaces.
Raw{"answer": "ab", "explanation": "The echo function outputs the arguments in sequence without separating them with spaces."} | верно | echo принимает список аргументов: ab. |
T01-L4 1.66 c | Syntax and operators | print returns the value 1 and can be used inside an expression. | «yes» Пояснение: In PHP, print returns the integer 1 and can be used within an expression.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "In PHP, print returns the integer 1 and can be used within an expression." ⏎ } | верно | print — выражение со значением 1, в отличие от echo, который значения не возвращает. |
T01-L5 1.51 c | Syntax and operators | The ?: (elvis) operator returns its left operand when it is falsy. | «no» Пояснение: The Elvis operator returns the left operand when it is truthy, and the right operand when it is falsy.
Raw{"answer":"no","explanation":"The Elvis operator returns the left operand when it is truthy, and the right operand when it is falsy."} | верно | Наоборот: $a ?: $b возвращает $a, если он истинный, иначе $b. |
T01-L6 1.7 c | Syntax and operators | In PHP 8, the concatenation operator (.) has lower precedence than addition and subtraction. | «yes» Пояснение: In PHP 8, binary + and - have higher precedence than the concatenation operator .
Raw{"answer": "yes", "explanation": "In PHP 8, binary + and - have higher precedence than the concatenation operator ."} | верно | С PHP 8 (RFC concat precedence) '.' имеет приоритет ниже арифметики: 'сумма: ' . 2 + 3 → 'сумма: 5' (в PHP 7 было иначе). |
T01-L7 1.98 c | Syntax and operators | The expression 2 ** 3 ** 2 in PHP evaluates as (2 ** 3) ** 2, that is, 64. | «no» Пояснение: In PHP, the ** operator is right-associative, so 2 ** 3 ** 2 evaluates as 2 ** (3 ** 2) = 512, not 64.
Raw{"answer": "no", "explanation": "In PHP, the ** operator is right-associative, so 2 ** 3 ** 2 evaluates as 2 ** (3 ** 2) = 512, not 64."} | верно | ** право-ассоциативен: 2 ** (3 ** 2) = 2 ** 9 = 512. |
T01-L8 5.71 c | Syntax and operators | What string will this print: echo 'sum: ' . 2 + 3; (PHP 8)? | «sum: 5» Пояснение: In PHP, addition has higher precedence than concatenation, so 2 + 3 is evaluated first and concatenated with 'sum: '.
Raw{"answer": "sum: 5", "explanation": "In PHP, addition has higher precedence than concatenation, so 2 + 3 is evaluated first and concatenated with 'sum: '."} | верно | Парная к verify-клетке про приоритет: 'сумма: 5'. |
T02-L1 1.28 c | Types and comparisons | With strict comparison (===), arrays are considered equal regardless of element order. | «no» Пояснение: In PHP, strict array comparison (===) requires elements to have the same keys/values and the same order.
Raw{"answer": "no", "explanation": "In PHP, strict array comparison (===) requires elements to have the same keys/values and the same order."} | верно | === для массивов требует совпадения и значений, и их порядка. |
T02-L2 1.31 c | Types and comparisons | The comparison 0 == false returns false because it is a strict comparison. | «no» Пояснение: The expression 0 == false uses loose comparison in PHP and returns true, not false.
Raw{"answer": "no", "explanation": "The expression 0 == false uses loose comparison in PHP and returns true, not false."} | верно | Наоборот: == — нестрогое сравнение и возвращает true; строгое — это === (0 === false → false). |
T02-L3 3.77 c | Types and comparisons | In PHP 8, the expression "abc" == 0 returns true. | «no» Пояснение: In PHP 8, comparing 0 to the non-numeric string "abc" uses string comparison, so "0" == "abc" is false.
Raw{"answer": "no", "explanation": "In PHP 8, comparing 0 to the non-numeric string \"abc\" uses string comparison, so \"0\" == \"abc\" is false."} | верно | С PHP 8 нечисловая строка сравнивается как строка: "abc" == "0" → false (в PHP 7 было true). |
T02-L4 1.29 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 is considered equal to 0, "", and false.
Raw{"answer": "yes", "explanation": "In PHP loose comparison, null is considered equal to 0, \"\", and false."} | верно | null == 0, null == "" и null == false — все true. |
T02-L5 0.99 c | Types and comparisons | What does the expression (int) '42abc' return? | «42» Пояснение: PHP casts a string to an integer by taking the leading numeric portion until it hits a non-numeric character.
Raw{"answer": 42, "explanation": "PHP casts a string to an integer by taking the leading numeric portion until it hits a non-numeric character."} | верно | Ведущая числовая часть: 42, без ошибок и warning. |
T02-L6 0.9 c | Types and comparisons | What does the expression '5' + 5 return? | «10» Пояснение: In PHP, the numeric string '5' is converted to the integer 5 and then added to 5, resulting in 10.
Raw{"answer": 10, "explanation": "In PHP, the numeric string '5' is converted to the integer 5 and then added to 5, resulting in 10."} | верно | Числовая строка приводится: int 10. |
T02-L7 0.79 c | Types and comparisons | When cast to string, false becomes "0". | «no» Пояснение: In PHP, casting false to a string results in an empty string, not "0".
Raw{"answer": "no", "explanation": "In PHP, casting false to a string results in an empty string, not \"0\"."} | верно | false → "", true → "1". |
T02-L8 3.36 c | Types and comparisons | The comparison 0.1 + 0.2 === 0.3 returns false. | «yes» Пояснение: In PHP, 0.1 + 0.2 does not equal 0.3 exactly due to floating-point representation, so the strict comparison is false.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "In PHP, 0.1 + 0.2 does not equal 0.3 exactly due to floating-point representation, so the strict comparison is false." ⏎ } | верно | Двоичная погрешность float: 0.1 + 0.2 = 0.30000000000000004. |
T03-L1 1.16 c | Strings | strrev() correctly reverses a UTF-8 string. | «no» Пояснение: strrev() reverses the string byte by byte, not by UTF-8 characters, so it can corrupt multibyte UTF-8 sequences.
Raw{"answer": "no", "explanation": "strrev() reverses the string byte by byte, not by UTF-8 characters, so it can corrupt multibyte UTF-8 sequences."} | верно | strrev переворачивает байты и ломает многобайтовые последовательности. |
T03-L2 0.86 c | Strings | str_contains('Hello world', 'world') returns true. | «yes» Пояснение: str_contains returns true because 'world' appears in 'Hello world'.
Raw{"answer": "yes", "explanation": "str_contains returns true because 'world' appears in 'Hello world'."} | верно | str_contains с PHP 8.0 проверяет вхождение подстроки. |
T03-L3 1.42 c | Strings | str_pad() can pad a string on the right side only. | «no» Пояснение: str_pad() supports left, right, or both sides padding via its $pad_type parameter (STR_PAD_LEFT, STR_PAD_RIGHT, or STR_PAD_BOTH).
Raw{"answer": "no", "explanation": "str_pad() supports left, right, or both sides padding via its $pad_type parameter (STR_PAD_LEFT, STR_PAD_RIGHT, or STR_PAD_BOTH)."} | верно | STR_PAD_LEFT / STR_PAD_BOTH меняют сторону дополнения. |
T03-L4 1.8 c | Strings | By default trim() strips only spaces, leaving tabs and newlines intact. | «no» Пояснение: By default, PHP's trim() strips whitespace including spaces, tabs, newlines, carriage returns, and other whitespace characters.
Raw{"answer": "no", "explanation": "By default, PHP's trim() strips whitespace including spaces, tabs, newlines, carriage returns, and other whitespace characters."} | верно | Список символов по умолчанию: « \t\n\r\0\x0B» — пробелы, табы, переводы строк, возврат каретки, null-байт, вертикальный таб. Проверено php -r. |
T03-L5 1.71 c | Strings | How many BYTES does strlen('héllo') return for a UTF-8 string? | «6» Пояснение: The UTF-8 string 'héllo' contains the byte sequence h (1 byte), é (2 bytes), l (1 byte), l (1 byte), and o (1 byte), totaling 6 bytes.
Raw{"answer": 6, "explanation": "The UTF-8 string 'héllo' contains the byte sequence h (1 byte), é (2 bytes), l (1 byte), l (1 byte), and o (1 byte), totaling 6 bytes."} | верно | 6 букв по 2 байта: 12. |
T03-L6 1.65 c | Strings | What does substr('abcdef', -3) return? | «def» Пояснение: A negative start count in substr() counts backward from the end of the string.
Raw{ ⏎ "answer": "def", ⏎ "explanation": "A negative start count in substr() counts backward from the end of the string." ⏎ } | верно | Отрицательное смещение — с конца: def. |
T03-L7 0.78 c | Strings | ucfirst() modifies the string passed to it in place. | «no» Пояснение: ucfirst() returns a new string with the first character uppercased and does not modify the original string in place.
Raw{"answer": "no", "explanation": "ucfirst() returns a new string with the first character uppercased and does not modify the original string in place."} | верно | Строки неизменяемы; ucfirst возвращает новую строку. |
T03-L8 1.08 c | Strings | Variable interpolation works in heredoc but not in nowdoc. | «yes» Пояснение: PHP variable interpolation is supported in heredoc but not in nowdoc.
Raw{"answer": "yes", "explanation": "PHP variable interpolation is supported in heredoc but not in nowdoc."} | верно | Nowdoc — «одинарные кавычки» в тройном синтаксисе: текст как есть. |
T04-L1 0.99 c | Arrays | The sort() function preserves the key-to-value association of the array. | «no» Пояснение: sort() sorts values and reindexes numeric keys, so it does not preserve key-to-value associations.
Raw{"answer":"no","explanation":"sort() sorts values and reindexes numeric keys, so it does not preserve key-to-value associations."} | верно | sort перенумеровывает ключи; связь сохраняет asort. |
T04-L2 2.65 c | Arrays | The string key '5' in an array is stored as the integer 5. | «yes» Пояснение: PHP coerces numeric string array keys like '5' to their integer equivalent.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "PHP coerces numeric string array keys like '5' to their integer equivalent." ⏎ } | верно | Каноничные десятичные строковые ключи приводятся к int. |
T04-L3 1.62 c | Arrays | The in_array() function uses strict comparison (===) by default. | «no» Пояснение: in_array() uses loose comparison by default; strict comparison requires the third argument to be set to true.
Raw{"answer":"no","explanation":"in_array() uses loose comparison by default; strict comparison requires the third argument to be set to true."} | верно | По умолчанию сравнение нестрогое; строгое — третий аргумент true. |
T04-L4 1.27 c | Arrays | Without a callback, array_filter() removes all "empty" (falsy) elements from the array. | «yes» Пояснение: Without a callback, array_filter() removes all falsy values from the array.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Without a callback, array_filter() removes all falsy values from the array." ⏎ } | верно | Убирает 0, "", null, false и пустые массивы. |
T04-L5 1.7 c | Arrays | By default, array_slice() preserves the original numeric keys of the array. | «no» Пояснение: By default, array_slice() does not preserve keys and reindexes numeric keys.
Raw{"answer": "no", "explanation": "By default, array_slice() does not preserve keys and reindexes numeric keys."} | верно | По умолчанию ключи перенумеровываются; сохранение — preserve_keys = true. |
T04-L6 2.76 c | Arrays | What does array_slice([10, 20, 30, 40], 1, 2) return? | «[20, 30]» Пояснение: array_slice returns elements starting at offset 1 with length 2, which are 20 and 30.
Raw{"answer": "[20, 30]", "explanation": "array_slice returns elements starting at offset 1 with length 2, which are 20 and 30."} | верно | [20,30]; ключи перенумеровываются. |
T04-L7 1.83 c | Arrays | How many elements will count(['a' => 1] + ['a' => 9, 'b' => 2]) return? | «2» Пояснение: The + operator keeps the left array's value for duplicate keys and adds non-duplicate keys from the right array.
Raw{"answer": 2, "explanation": "The + operator keeps the left array's value for duplicate keys and adds non-duplicate keys from the right array."} | верно | Оператор + : по ключу 'a' побеждает левый; итого 2. |
T04-L8 16.81 c | Arrays | Since PHP 8.1, the spread operator [...$a, ...$b] supports arrays with string keys. | «yes» Пояснение: PHP 8.1 added array-context spread that can unpack associative arrays, preserving string keys.
Raw{"answer":"yes","explanation":"PHP 8.1 added array-context spread that can unpack associative arrays, preserving string keys."} | верно | В 8.0 — только числовые ключи; 8.1 снял ограничение. |
T05-L1 71.25 c | Functions and closures | Named arguments cannot be combined with argument unpacking ...$args in a single call. | «yes» Пояснение: PHP does not allow named arguments and the spread operator (argument unpacking) to be used together in the same function call.
Raw{"answer": "yes", "explanation": "PHP does not allow named arguments and the spread operator (argument unpacking) to be used together in the same function call."} | неверно верный: «no» | Можно: f(...$args, имя: значение). Нельзя только позиционный аргумент после распаковки. |
T05-L2 4.88 c | Functions and closures | An anonymous function without use sees variables from the outer scope. | «yes» Пояснение: PHP closures capture variables from the outer scope by value by default, even without an explicit use clause.
Raw{"answer":"yes","explanation":"PHP closures capture variables from the outer scope by value by default, even without an explicit use clause."} | неверно верный: «no» | Без use внешние переменные недоступны; авто-захват только у fn. |
T05-L3 1.24 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.
Raw{ ⏎ "answer": 3, ⏎ "explanation": "func_num_args() returns the number of arguments actually passed to the function." ⏎ } | верно | Считает переданные аргументы: 3. |
T05-L4 2.78 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 body consisting of a single expression, not multiple statements in curly braces.
Raw{"answer": "no", "explanation": "PHP arrow functions have a body consisting of a single expression, not multiple statements in curly braces."} | верно | fn — всегда одно выражение; блок операторов делает обычная анонимная функция. |
T05-L5 69.27 c | Functions and closures | An arrow function fn captures outer variables by reference (lazily, at use time). | «yes» Пояснение: PHP arrow functions automatically capture enclosing-scope variables by reference, so they read the variable's current value when called.
Raw{"answer":"yes","explanation":"PHP arrow functions automatically capture enclosing-scope variables by reference, so they read the variable's current value when called."} | неверно верный: «no» | fn захватывает только по значению, автоматически; по ссылке — только &$var в use у обычной функции (fn так не умеет). |
T05-L6 3.16 c | Functions and closures | A closure declared as static function () {} does not capture $this. | «yes» Пояснение: In PHP, a static closure explicitly declared with `static function () {}` does not implicitly capture `$this`, unlike a non-static closure defined in an instance context.
Raw{"answer": "yes", "explanation": "In PHP, a static closure explicitly declared with `static function () {}` does not implicitly capture `$this`, unlike a non-static closure defined in an instance context."} | верно | static-замыкание отвязано от объекта: $this внутри недоступен. |
T05-L7 1.44 c | Functions and closures | What will this print: $x = 5; $f = function () use ($x) { return $x; }; $x = 7; echo $f(); | «5» Пояснение: The closure captures $x by value, so it returns the captured value 5 rather than the later value 7.
Raw{"answer":5,"explanation":"The closure captures $x by value, so it returns the captured value 5 rather than the later value 7."} | верно | use захватывает по значению в момент создания: 5. |
T05-L8 2.06 c | Functions and closures | In weak typing mode (without strict_types), passing the string "5" to an int parameter is allowed. | «yes» Пояснение: In weak typing mode, PHP coerces numeric strings like "5" to int parameters.
Raw{"answer":"yes","explanation":"In weak typing mode, PHP coerces numeric strings like \"5\" to int parameters."} | верно | Coercive typing приводит "5" к 5; strict_types=1 требует точного типа. |
T06-L1 1.1 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 like `private int $x` to become class properties automatically.
Raw{"answer":"yes","explanation":"PHP 8.0 introduced constructor property promotion, allowing parameters like `private int $x` to become class properties automatically."} | верно | С PHP 8.0 параметр с модификатором создаёт свойство и присваивание. |
T06-L2 0.97 c | OOP: classes and inheritance | Which keyword prevents a method from being overridden in subclasses? | «final» Пояснение: The 'final' keyword in PHP prevents a method (or class) from being overridden in subclasses.
Raw{"answer": "final", "explanation": "The 'final' keyword in PHP prevents a method (or class) from being overridden in subclasses."} | верно | final. |
T06-L3 0.94 c | OOP: classes and inheritance | A method declared final cannot be overridden in a subclass. | «yes» Пояснение: In PHP, a method declared with the 'final' keyword explicitly prevents it from being overridden in a subclass.
Raw{"answer": "yes", "explanation": "In PHP, a method declared with the 'final' keyword explicitly prevents it from being overridden in a subclass."} | верно | final запрещает переопределение метода и наследование класса. |
T06-L4 0.86 c | OOP: classes and inheritance | Parent properties with private visibility are accessible in a subclass. | «no» Пояснение: In PHP, private properties are accessible only within the class where they are defined, not in subclasses.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "In PHP, private properties are accessible only within the class where they are defined, not in subclasses." ⏎ } | верно | В подклассе видны protected и public; private — только внутри своего класса. |
T06-L5 66.42 c | OOP: classes and inheritance | What does get_class(new class {}) return? Answer with the part of the name before the NUL byte (without the file path). | «class» Пояснение: PHP anonymous-class names use the prefix Class before the NUL separator and file/line suffix.
Raw{ ⏎ "answer": "Class", ⏎ "explanation": "PHP anonymous-class names use the prefix Class before the NUL separator and file/line suffix." ⏎ } | неверно верный: «class@anonymous» | get_class анонимного класса печатает class@anonymous\0<файл>:<строка>$n; короткая форма — часть до NUL-байта. Проверено php -r (hex). |
T06-L6 2.2 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 are outside the inheritance contract, so a child class can define a method with the same name at any visibility.
Raw{"answer": "yes", "explanation": "Private methods are not inherited and are outside the inheritance contract, so a child class can define a method with the same name at any visibility."} | верно | private-члены не наследуются — правила совместимости подписей не действуют. |
T06-L7 1.53 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 3.23 c | OOP: classes and inheritance | What does reassigning a readonly property throw — Exception or Error? | «error» Пояснение: Reassigning a readonly property in PHP throws an Error.
Raw{ ⏎ "answer": "Error", ⏎ "explanation": "Reassigning a readonly property in PHP throws an Error." ⏎ } | верно | Error (readonly с 8.1); оговорка: в __clone() переинициализация допустима (8.3+). |
T07-L1 0.88 c | Interfaces, traits, enum | An interface can declare constants. | «yes» Пояснение: In PHP, interfaces can declare public constants.
Raw{"answer":"yes","explanation":"In PHP, interfaces can declare public constants."} | верно | Константы интерфейса наследуются реализациями. |
T07-L2 0.9 c | Interfaces, traits, enum | Which operator checks whether an object is an instance of a class or interface? | «instanceof» Пояснение: In PHP, the instanceof operator checks if an object is an instance of a given class or interface.
Raw{"answer": "instanceof", "explanation": "In PHP, the instanceof operator checks if an object is an instance of a given class or interface."} | верно | instanceof. |
T07-L3 4.32 c | Interfaces, traits, enum | An interface can declare static methods. | «no» Пояснение: In PHP, interfaces cannot declare static methods.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "In PHP, interfaces cannot declare static methods." ⏎ } | неверно верный: «yes» | Реализация обязана дать статический метод с той же сигнатурой. |
T07-L4 1.26 c | Interfaces, traits, enum | The instanceof operator only checks class inheritance: it ignores interfaces. | «no» Пояснение: PHP's instanceof operator also checks whether an object implements an interface.
Raw{"answer": "no", "explanation": "PHP's instanceof operator also checks whether an object implements an interface."} | верно | instanceof возвращает true и для интерфейсов объекта. |
T07-L5 1.19 c | Interfaces, traits, enum | An interface method may have a default implementation, like a trait method. | «no» Пояснение: In PHP, interface methods are abstract and cannot contain a default implementation, unlike trait methods.
Raw{"answer":"no","explanation":"In PHP, interface methods are abstract and cannot contain a default implementation, unlike trait methods."} | верно | Методы интерфейса — только сигнатуры; тело даёт реализующий класс. |
T07-L6 3.35 c | Interfaces, traits, enum | An abstract method in an abstract class may have protected visibility. | «yes» Пояснение: In PHP, abstract methods can be declared as public or protected, but not private.
Raw{"answer": "yes", "explanation": "In PHP, abstract methods can be declared as public or protected, but not private."} | верно | В абстрактном классе — любая видимость; в интерфейсе — только public. |
T07-L7 1.63 c | Interfaces, traits, enum | How many elements will Foo::cases() return for enum Foo { case A; case B; case C; }? | «3» Пояснение: Foo::cases() returns an array of all cases in the enum, which has three cases: A, B, and C.
Raw{"answer": 3, "explanation": "Foo::cases() returns an array of all cases in the enum, which has three cases: A, B, and C."} | верно | Статический метод cases(): 3. |
T07-L8 1.37 c | Interfaces, traits, enum | A trait can declare constants. | «yes» Пояснение: In PHP, traits can define constants.
Raw{"answer":"yes","explanation":"In PHP, traits can define constants."} | верно | С PHP 8.2 трейты могут объявлять константы (RFC constants_in_traits); до 8.2 — нет. |
T08-L1 0.81 c | Exceptions and errors | The Throwable interface is a common ancestor of both Exception and Error. | «yes» Пояснение: In PHP, both Exception and Error implement the Throwable interface, making it their common ancestor.
Raw{"answer": "yes", "explanation": "In PHP, both Exception and Error implement the Throwable interface, making it their common ancestor."} | верно | Иерархия с PHP 7: Throwable → Exception и Throwable → Error. |
T08-L2 1.68 c | Exceptions and errors | A catch (Exception $e) block will also catch TypeError, because TypeError ultimately inherits from Exception. | «no» Пояснение: TypeError extends Error (not Exception); both are siblings under Throwable, so a catch(Exception) block will not catch TypeError.
Raw{"answer":"no","explanation":"TypeError extends Error (not Exception); both are siblings under Throwable, so a catch(Exception) block will not catch TypeError."} | верно | TypeError наследуется от Error; catch (Exception) его не ловит. |
T08-L3 1.04 c | Exceptions and errors | The @ operator suppresses exceptions too. | «no» Пояснение: In PHP, the @ operator suppresses errors/warnings but does not suppress exceptions.
Raw{"answer":"false","explanation":"In PHP, the @ operator suppresses errors/warnings but does not suppress exceptions."} | верно | @ глушит диагностику (warnings/notices), исключения не перехватывает. |
T08-L4 1.34 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.47 c | Exceptions and errors | The finally block runs only if the exception was caught by a catch block. | «no» Пояснение: In PHP, the finally block executes after the try/catch block regardless of whether an exception was thrown or caught.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "In PHP, the finally block executes after the try/catch block regardless of whether an exception was thrown or caught." ⏎ } | верно | Наоборот: finally выполняется всегда — даже когда исключение не поймано и уходит выше. Проверено php -r. |
T08-L6 5.18 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 execution; it propagates after the try/catch handling has occurred.
Raw{"answer": "no", "explanation": "An exception thrown in a finally block does affect execution; it propagates after the try/catch handling has occurred."} | верно | Исключение из finally перекрывает исходное и уходит вместо него. |
T08-L7 3.86 c | Exceptions and errors | What does the expression (bool) new Exception('x') return? | «yes» Пояснение: Casting any object to a boolean in PHP always produces true.
Raw{"answer":"yes","explanation":"Casting any object to a boolean in PHP always produces true."} | верно | Любой объект при приведении к bool — true. Формы ответа: true или да. |
T08-L8 2.8 c | Exceptions and errors | Functions registered via register_shutdown_function() run when exit is called. | «yes» Пояснение: In PHP, functions registered with register_shutdown_function() are called when the script terminates normally, including when exit() is called.
Raw{"answer": "yes", "explanation": "In PHP, functions registered with register_shutdown_function() are called when the script terminates normally, including when exit() is called."} | верно | exit завершает скрипт, но shutdown-функции отрабатывают. |
T09-L1 1.97 c | Namespaces and autoloading | The use App\Service\Mailer; statement itself loads the class file. | «no» Пояснение: The PHP `use` statement only creates a compile-time alias for a class name and does not trigger any file loading; the actual class file is loaded by an autoloader (e.g., spl_autoload_register or Composer's autoloader) when the class is first referenced at runtime.
Raw{"answer": "no", "explanation": "The PHP `use` statement only creates a compile-time alias for a class name and does not trigger any file loading; the actual class file is loaded by an autoloader (e.g., spl_autoload_register or Composer's autoloader) when the class is first referenced at runtime."} | верно | use — псевдоним на этапе компиляции; файл грузит автозагрузчик при первом обращении. |
T09-L2 2.44 c | Namespaces and autoloading | What follows use to import a function (not a class): the word function or const? | «function» Пояснение: In PHP, `use function` is used to import a function from a namespace, while `use const` imports a constant.
Raw{"answer": "function", "explanation": "In PHP, `use function` is used to import a function from a namespace, while `use const` imports a constant."} | верно | use function ...; (и use const для констант). |
T09-L3 1.57 c | Namespaces and autoloading | Into which file (path from src/) does the PSR-4 mapping "App\ → src/" place the class App\Controller\Api\UserController? | «controller/api/usercontroller.php» Пояснение: The PSR-4 prefix 'App\' maps to src/, so the remaining namespace parts Controller\Api and class name UserController become the relative path Controller/Api/UserController.php under src/.
Raw{"answer":"Controller/Api/UserController.php","explanation":"The PSR-4 prefix 'App\\' maps to src/, so the remaining namespace parts Controller\\Api and class name UserController become the relative path Controller/Api/UserController.php under src/."} | верно | Остаток имени после префикса, \ → /. |
T09-L4 2.18 c | Namespaces and autoloading | Including vendor/autoload.php registers autoloaders via spl_autoload_register(). | «yes» Пояснение: Composer's generated vendor/autoload.php instantiates and registers autoloader classes (NamespaceAutoloader and ClassMapAutoloader) that call spl_autoload_register() internally to hook into PHP's autoloading mechanism.
Raw{"answer": "yes", "explanation": "Composer's generated vendor/autoload.php instantiates and registers autoloader classes (NamespaceAutoloader and ClassMapAutoloader) that call spl_autoload_register() internally to hook into PHP's autoloading mechanism."} | верно | Composer ставит автозагрузчик именно на spl_autoload_register. |
T09-L5 3.64 c | Namespaces and autoloading | The magic constant __NAMESPACE__ contains the name of the current namespace. | «yes» Пояснение: The __NAMESPACE__ magic constant returns the current namespace name when in a namespace.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "The __NAMESPACE__ magic constant returns the current namespace name when in a namespace." ⏎ } | верно | В корневом пространстве — пустая строка. |
T09-L6 9.0 c | Namespaces and autoloading | An unqualified class name (without a leading \) in new is resolved from the global root. | «no» Пояснение: Unqualified class names in new are first resolved in the current namespace, then fall back to the global namespace.
Raw{"answer": "no", "explanation": "Unqualified class names in new are first resolved in the current namespace, then fall back to the global namespace."} | верно | Резолвится относительно текущего namespace (с учётом импортов). |
T09-L7 0.73 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 converts the namespace App\Model\User into the file path src/Model/User.php.
Raw{"answer": "yes", "explanation": "PSR-4 converts the namespace App\\Model\\User into the file path src/Model/User.php."} | верно | Остаток имени после префикса переносится в путь как есть. |
T09-L8 3.83 c | Namespaces and autoloading | A use statement may be written inside a function body — the import then applies to that function only. | «no» Пояснение: In PHP, the use statement is a compile-time construct that can only appear at the top level of a file (after the namespace declaration) or inside a class declaration; it is not valid inside a function body.
Raw{"answer": "no", "explanation": "In PHP, the use statement is a compile-time construct that can only appear at the top level of a file (after the namespace declaration) or inside a class declaration; it is not valid inside a function body."} | верно | use внутри тела функции — parse error; импорты файловые и компиляционные. |
T10-L1 1.51 c | References and scope | Arrays are copied on assignment rather than passed by reference. | «yes» Пояснение: By default, PHP arrays are copied on assignment rather than passed by reference.
Raw{"answer": "yes", "explanation": "By default, PHP arrays are copied on assignment rather than passed by reference."} | верно | Присваивание массива — копия (в движке — copy-on-write). |
T10-L2 0.99 c | References and scope | What will this print: $a = [1, 2]; $b = $a; $b[] = 3; echo count($a); | «2» Пояснение: Arrays are copied by value in PHP, so modifying $b does not change $a.
Raw{"answer": 2, "explanation": "Arrays are copied by value in PHP, so modifying $b does not change $a."} | верно | Присваивание — копия: в $a по-прежнему 2 элемента. |
T10-L3 3.2 c | References and scope | Inside a function, user-defined global variables are inaccessible without global, $GLOBALS, or passing them as parameters. | «yes» Пояснение: In PHP, global variables are not automatically accessible inside functions and must be accessed with global, $GLOBALS, or passed as parameters.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "In PHP, global variables are not automatically accessible inside functions and must be accessed with global, $GLOBALS, or passed as parameters." ⏎ } | верно | Область видимости функций изолирована; исключение — суперглобалы ($_GET и др.). |
T10-L4 1.94 c | References and scope | unset($GLOBALS['x']) inside a function removes the global variable only for that function. | «no» Пояснение: unset($GLOBALS['x']) removes the variable from the global scope entirely, not just for the current function.
Raw{"answer": "no", "explanation": "unset($GLOBALS['x']) removes the variable from the global scope entirely, not just for the current function."} | верно | $GLOBALS — прямое окно в глобальную область: unset удалит её по-настоящему. |
T10-L5 0.99 c | References and scope | What will this print: function inc(&$x) { $x++; } $n = 5; inc($n); echo $n; | «6» Пояснение: The function receives $n by reference, increments it, and then it is printed.
Raw{"answer": 6, "explanation": "The function receives $n by reference, increments it, and then it is printed."} | верно | Ссылка меняет оригинал: 6. |
T10-L6 32.17 c | References and scope | A foreach over an array (by value) works with the "live" array: changes to the array inside the loop are visible in the same pass. | «no» Пояснение: A by-value foreach iterates over a snapshot/copy of the array, so changes made to the array during the loop are not visible in that pass.
Raw{"answer": "no", "explanation": "A by-value foreach iterates over a snapshot/copy of the array, so changes made to the array during the loop are not visible in that pass."} | верно | По значению foreach итерирует копию-снимок. |
T10-L7 1.23 c | References and scope | A static property belongs to each instance separately: changes in one object are not visible in others. | «no» Пояснение: A static property belongs to the class itself, not to each instance separately, so changes made through one instance are visible in all other instances.
Raw{"answer":"no","explanation":"A static property belongs to the class itself, not to each instance separately, so changes made through one instance are visible in all other instances."} | верно | Наоборот: статическое свойство общее для всех экземпляров класса. Проверено php -r. |
T10-L8 2.71 c | References and scope | An array can have a boolean key true, and it will be stored as bool. | «no» Пояснение: PHP coerces boolean array keys to integers, so a true key is stored as the integer key 1, not as a boolean.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "PHP coerces boolean array keys to integers, so a true key is stored as the integer key 1, not as a boolean." ⏎ } | верно | Булев ключ приводится к int: true → 1, false → 0. |
T11-L1 5.07 c | Generators, iterators, SPL | Inside a generator, return with a value can be used, and it becomes available via $gen->getReturn(). | «yes» Пояснение: A generator may end with a return value, and PHP exposes it through the Generator::getReturn() method.
Raw{"answer": "yes", "explanation": "A generator may end with a return value, and PHP exposes it through the Generator::getReturn() method."} | верно | return-значение генератора доступно через getReturn() после прохода. |
T11-L2 4.14 c | Generators, iterators, SPL | A fully consumed generator can be rewound with rewind() and traversed again. | «no» Пояснение: In PHP, once a generator is fully consumed (exhausted), it cannot be rewound with rewind(); attempting to do so throws an exception and the generator's internal state is lost.
Raw{"answer": "no", "explanation": "In PHP, once a generator is fully consumed (exhausted), it cannot be rewound with rewind(); attempting to do so throws an exception and the generator's internal state is lost."} | верно | Генератор одноразовый: rewind после начала итерации бросает Exception. |
T11-L3 1.73 c | Generators, iterators, SPL | The yield from construct delegates traversal to another generator or iterable. | «yes» Пояснение: In PHP, yield from delegates traversal to another generator or iterable.
Raw{"answer":"yes","explanation":"In PHP, yield from delegates traversal to another generator or iterable."} | верно | yield from проксирует значения, ключи и return-значение внутреннего генератора. |
T11-L4 2.2 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.44 c | Generators, iterators, SPL | How many elements will count(iterator_to_array((function () { yield from [1, 2, 3]; })())) return? | «3» Пояснение: The generator yields three values, so iterator_to_array creates an array with three elements.
Raw{"answer": 3, "explanation": "The generator yields three values, so iterator_to_array creates an array with three elements."} | верно | yield from делегирует все 3 элемента. |
T11-L6 0.8 c | Generators, iterators, SPL | The SplStack class implements a FIFO queue. | «no» Пояснение: SPLStack implements a LIFO stack, not a FIFO queue.
Raw{"answer":"no","explanation":"SPLStack implements a LIFO stack, not a FIFO queue."} | верно | SplStack — стек LIFO; очередь FIFO — SplQueue. |
T11-L7 1.45 c | Generators, iterators, SPL | ArrayIterator allows wrapping an array and traversing it via the Iterator interface. | «yes» Пояснение: PHP's ArrayIterator wraps an array and lets you traverse it using the Iterator interface.
Raw{"answer":"yes","explanation":"PHP's ArrayIterator wraps an array and lets you traverse it using the Iterator interface."} | верно | Объектная обёртка над массивом. |
T11-L8 1.96 c | Generators, iterators, SPL | An ArrayObject instance cannot be traversed with foreach. | «no» Пояснение: ArrayObject implements Iterator, so it can be traversed with foreach.
Raw{"answer": "no", "explanation": "ArrayObject implements Iterator, so it can be traversed with foreach."} | верно | ArrayObject реализует IteratorAggregate — foreach по нему работает. |
T12-L1 1.24 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, so you do not pass one separately.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "password_hash() automatically generates and stores the salt, so you do not pass one separately." ⏎ } | верно | Соль встраивается в строку результата; параметр salt устарел. |
T12-L2 0.95 c | Configuration and security | In PHP 8, PASSWORD_DEFAULT is md5 with an automatically added salt. | «no» Пояснение: PASSWORD_DEFAULT uses the default password hashing algorithm in PHP, which is not MD5 and typically uses a strong algorithm like bcrypt.
Raw{"answer": "no", "explanation": "PASSWORD_DEFAULT uses the default password hashing algorithm in PHP, which is not MD5 and typically uses a strong algorithm like bcrypt."} | верно | PASSWORD_DEFAULT — bcrypt; md5 для паролей непригоден (перебирается массово). |
T12-L3 1.93 c | Configuration and security | What does password_verify('secret', password_hash('secret', PASSWORD_DEFAULT)) return? | «yes» Пояснение: password_verify returns true when the provided password matches the password hash.
Raw{"answer": "yes", "explanation": "password_verify returns true when the provided password matches the password hash."} | верно | Соль и хеш в одной строке: true (форма ответа: true или да). |
T12-L4 0.75 c | Configuration and security | strip_tags() protects against SQL injection. | «no» Пояснение: strip_tags() removes HTML tags and does not protect against SQL injection.
Raw{"answer": "no", "explanation": "strip_tags() removes HTML tags and does not protect against SQL injection."} | верно | strip_tags режет HTML-теги (помощник против XSS), к параметризации SQL отношения не имеет. |
T12-L5 1.04 c | Configuration and security | session_regenerate_id() is used to protect against session fixation upon user login. | «yes» Пояснение: Calling session_regenerate_id() after login creates a new session ID, helping prevent an attacker from using a previously obtained session ID to hijack the session.
Raw{"answer": "yes", "explanation": "Calling session_regenerate_id() after login creates a new session ID, helping prevent an attacker from using a previously obtained session ID to hijack the session."} | верно | Новый 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 built-in PHP function php_sapi_name() returns the current SAPI name (e.g. 'cli', 'fpm-fcgi', 'apache2handler').
Raw{"answer":"php_sapi_name()","explanation":"The built-in PHP function php_sapi_name() returns the current SAPI name (e.g. 'cli', 'fpm-fcgi', 'apache2handler')."} | верно | php_sapi_name(). |
T12-L7 5.8 c | Configuration and security | session_destroy() deletes session data on the server but not the cookie in the user's browser. | «yes» Пояснение: session_destroy() removes the server-side session data but does not automatically delete the session cookie in the browser.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "session_destroy() removes the server-side session data but does not automatically delete the session cookie in the browser." ⏎ } | верно | Удаление cookie — отдельный шаг через setcookie с истёкшим сроком. |
T12-L8 1.98 c | Configuration and security | Without calling session_start(), the $_SESSION array is automatically populated with session data. | «no» Пояснение: The $_SESSION array is only populated with session data after a session has been started, such as with session_start().
Raw{ ⏎ "answer": "no", ⏎ "explanation": "The $_SESSION array is only populated with session data after a session has been started, such as with session_start()." ⏎ } | верно | Без session_start() данные сессии в массив не загружаются ($_SESSION можно заполнить вручную, но привязки к сессии нет). |
VC-L1 73.99 c | PHP 8.4–8.5 | In which PHP version was the array_find() function introduced? | «no» Пояснение: PHP has no built-in array_find() function, so it was not introduced in any PHP version.
Raw{"answer":"no","explanation":"PHP has no built-in array_find() function, so it was not introduced in any PHP version."} | неверно верный: «8.4» | PHP 8.4 (RFC array_find). |
VC-L2 1.29 c | PHP 8.4–8.5 | Property hooks (get/set right in the property declaration) landed in PHP 8.4. | «yes» Пояснение: PHP 8.4 introduced property hooks that can be declared directly in a property's declaration.
Raw{"answer": "yes", "explanation": "PHP 8.4 introduced property hooks that can be declared directly in a property's declaration."} | верно | Property hooks — PHP 8.4 (ноябрь 2024). |
VC-L3 81.54 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 access, allowing a property to be public for reading but private for writing.
Raw{"answer":"yes","explanation":"PHP 8.4 introduced asymmetric property access, allowing a property to be public for reading but private for writing."} | верно | Asymmetric visibility v2 — PHP 8.4. |
VC-L4 2.22 c | PHP 8.4–8.5 | In which PHP version was the #[\NoDiscard] attribute introduced? Answer with the version number. | «8.4» Пояснение: The #[\NoDiscard] attribute was introduced in PHP 8.4.
Raw{ ⏎ "answer": "8.4", ⏎ "explanation": "The #[\\NoDiscard] attribute was introduced in PHP 8.4." ⏎ } | неверно верный: «8.5» | #[\NoDiscard] — PHP 8.5 (marking return values as important). |
VC-L5 45.08 c | PHP 8.4–8.5 | In which PHP version did the pipe operator |> first appear? Answer with the version number. | «no» Пояснение: PHP does not have a pipe operator |>, so no PHP version introduced it.
Raw{"answer":"No","explanation":"PHP does not have a pipe operator |>, so no PHP version introduced it."} | неверно верный: «8.5» | Pipe operator — PHP 8.5 (2025). |
VC-L6 2.97 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. | «none» Пояснение: The "clone-with" syntax clone($obj, ['x' => 1]) with a properties array as a second argument does not exist in any PHP version.
Raw{"answer": "none", "explanation": "The \"clone-with\" syntax clone($obj, ['x' => 1]) with a properties array as a second argument does not exist in any PHP version."} | неверно верный: «8.5» | Clone with v2 — PHP 8.5. |
VC-L7 3.5 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 built-in PHP functions in any PHP version; they do not exist in the PHP standard library.
Raw{"answer": "none", "explanation": "array_first() and array_last() are not built-in PHP functions in any PHP version; they do not exist in the PHP standard library."} | неверно верный: «8.5» | PHP 8.5. |
VC-L8 119.67 c | PHP 8.4–8.5 | For which PHP version was RFC Partial Function Application v2 adopted (as of 2026-11-07)? Answer with the version number. | «8.4» Пояснение: RFC Partial Function Application v2 was adopted for PHP 8.4.
Raw{"answer": "8.4", "explanation": "RFC Partial Function Application v2 was adopted for PHP 8.4."} | неверно верный: «8.6» | PFA v2 принят 05.12.2025 (33-0-0), реализован в PHP 8.6. |
VF-L1 8.7 c | PHP: 8.6+ and the future | For which PHP version was the RFC clamp_v2 (the clamp() function) implemented, as of 2026-11-07? Answer with the version number. | «8.1» Пояснение: The clamp() function from the PHP RFC was introduced in PHP 8.1.
Raw{"answer": "8.1", "explanation": "The clamp() function from the PHP RFC was introduced in PHP 8.1."} | неверно верный: «8.6» | По данным владельца (wiki.php.net/rfc): clamp_v2 — 8.6; clamp() в 8.5.11 отсутствует (косвенное подтверждение). Дата-якорь делает клетку монотонной. |
VF-L2 169.11 c | PHP: 8.6+ and the future | RFC Context Managers v2 has already been adopted in PHP (as of 2026-11-07). | «yes» Пояснение: RFC Context Managers v2 was accepted into PHP before that date.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "RFC Context Managers v2 was accepted into PHP before that date." ⏎ } | неверно верный: «no» | На 06.11.2026 — в обсуждении (создан 2026-10-23); не принят. |
VF-L3 91.69 c | PHP: 8.6+ and the future | RFC Bound-Erased Generic Types (generics) was declined in 2026. | «yes» Пояснение: The RFC was formally declined in 2026.
Raw{"answer": "yes", "explanation": "The RFC was formally declined in 2026."} | верно | Голосование завершилось 2026-06-28: отклонён (wiki.php.net/rfc). |
VF-L4 64.44 c | PHP: 8.6+ and the future | As of 2026-11-07, the RFC enabling multithreading (ZTS) by default has already been accepted in PHP. | «yes» Пояснение: The ZTS-by-default RFC was accepted before the stated November 2026 date.
Raw{"answer": "yes", "explanation": "The ZTS-by-default RFC was accepted before the stated November 2026 date."} | неверно верный: «no» | Такого принятого RFC нет на дату якоря; якорь делает клетку монотонной — при принятии RFC позже клетка не перевернётся. |
VF-L5 1.95 c | PHP: 8.6+ and the future | As of PHP 8.5, generics (parameterized types) are still absent. | «yes» Пояснение: PHP 8.5 does not include built-in generics or parameterized types.
Raw{"answer": "yes", "explanation": "PHP 8.5 does not include built-in generics or parameterized types."} | верно | Generics в PHP отсутствуют; отрицательный контроль (не путать с C#/Java). |
VF-L6 9.24 c | PHP: 8.6+ and the future | As of 2026-11-07, the latest stable PHP version is 8.5, and PHP 8.6 has not been released yet (GA — 2026-11-19). | «yes» Пояснение: Since PHP 8.6's GA date is later than 2026-11-07, PHP 8.5 would still be the latest stable release on that date.
Raw{"answer": "yes", "explanation": "Since PHP 8.6's GA date is later than 2026-11-07, PHP 8.5 would still be the latest stable release on that date."} | верно | 8.5 — релиз осени 2025; 8.6 GA 19.11.2026 (wiki.php.net/todo/php86). Дата снимка — 06.11.2026. |
VF-L7 1.43 c | PHP: 8.6+ and the future | The PHP 6 branch never shipped: after PHP 5.6 came PHP 7.0 directly. | «yes» Пояснение: PHP 6 was never released, and PHP 7.0 followed the 5.x series.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "PHP 6 was never released, and PHP 7.0 followed the 5.x series." ⏎ } | верно | Исторический факт: ветка 6 не была релизнута. |
VF-L8 2.93 c | PHP: 8.6+ and the future | The RFC adding the #[\Deprecated] attribute to the core was adopted. | «no» Пояснение: The RFC for the #[\Deprecated] attribute was rejected, as the community decided the existing trigger_deprecation() mechanism was sufficient and an attribute would be too opinionated.
Raw{"answer": "no", "explanation": "The RFC for the #[\\Deprecated] attribute was rejected, as the community decided the existing trigger_deprecation() mechanism was sufficient and an attribute would be too opinionated."} | неверно верный: «yes» | #[\Deprecated] — принят, реализован в PHP 8.4. |
T25-L1 1.17 c | Clean architecture | The dependency rule of clean and onion architecture: inner layers know nothing about outer ones — dependencies point toward the center. | «yes» Пояснение: Clean and onion architectures enforce the dependency rule, where dependencies point inward so inner layers are unaware of outer layers.
Raw{"answer": "yes", "explanation": "Clean and onion architectures enforce the dependency rule, where dependencies point inward so inner layers are unaware of outer layers."} | верно | Чистая (Robert C. Martin), луковичная (Jeffrey Palermo) и гексагональная (ports & adapters) — варианты одной идеи: зависимости направлены внутрь, к домену. Слоями в проекте следит deptrac. |
T25-L2 1.21 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 pure PHP classes, depending only on the language and standard library to maintain clean separation of concerns in DDD/Clean Architecture.
Raw{"answer": "yes", "explanation": "Domain entities should be framework-agnostic pure PHP classes, depending only on the language and standard library to maintain clean separation of concerns in DDD/Clean Architecture."} | верно | Изоляция домена от инфраструктуры; deptrac в проекте как раз следит за слоями. |
T25-L3 1.42 c | Clean architecture | Controllers and Twig templates belong to the business-logic layer because they are the ones calling use cases. | «no» Пояснение: Controllers and Twig templates belong to the presentation layer, not the business-logic layer.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "Controllers and Twig templates belong to the presentation layer, not the business-logic layer." ⏎ } | верно | Наоборот: это интерфейсные адаптеры (внешний слой); они зависят от use cases, а не наоборот. |
T25-L4 1.95 c | Clean architecture | What sits at the very center of the onion architecture? | «domain» Пояснение: The domain layer containing core business rules sits at the center of onion architecture.
Raw{"answer":"Domain","explanation":"The domain layer containing core business rules sits at the center of onion architecture."} | неверно верный: «domain model» | Центральное кольцо — Domain Model: сущности и бизнес-правила без зависимостей; далее Domain Services → Application Services → Infrastructure/UI/Tests (Palermo). |
T25-L5 1.12 c | Clean architecture | Layer boundary violations can be caught automatically: a layer-dependency analyzer (e.g. deptrac) fails on a forbidden call. | «yes» Пояснение: A tool like deptrac can analyze code dependencies and fail when a forbidden cross-layer call is detected.
Raw{"answer": "yes", "explanation": "A tool like deptrac can analyze code dependencies and fail when a forbidden cross-layer call is detected."} | верно | depfile.yaml в проекте TasK: CI проверяет правила слоёв на каждом пайплайне. |
T25-L6 2.94 c | Clean architecture | A use case (interactor) may accept an HTTP request or an EntityManager as arguments — it is simpler that way. | «no» Пояснение: A use case should accept simple domain-level inputs or interfaces rather than framework-specific objects like an HTTP request or EntityManager, to remain decoupled and testable.
Raw{"answer":"false","explanation":"A use case should accept simple domain-level inputs or interfaces rather than framework-specific objects like an HTTP request or EntityManager, to remain decoupled and testable."} | верно | Use case принимает DTO и порты; привязка к HTTP/ORM протекает инфраструктуру во внутренние слои. |
T25-L7 1.21 c | Clean architecture | What is the component called that provides a collection of aggregates/entities while hiding the storage mechanism behind an interface? | «repository» Пояснение: In Domain-Driven Design, a Repository abstracts the storage mechanism behind an interface, presenting a collection of aggregates/entities as if they were in memory.
Raw{"answer": "Repository", "explanation": "In Domain-Driven Design, a Repository abstracts the storage mechanism behind an interface, presenting a collection of aggregates/entities as if they were in memory."} | верно | Repository pattern (DDD/Evans); в проекте — Doctrine-репозитории за портами. |
T25-L8 2.81 c | Clean architecture | In clean architecture, swapping PostgreSQL for another database touches only the outer layer — the domain and use cases stay unchanged. | «yes» Пояснение: In clean architecture, database access is an infrastructure concern behind abstractions, so changing it should affect only the outer layer, not the domain or use cases.
Raw{"answer":"yes","explanation":"In clean architecture, database access is an infrastructure concern behind abstractions, so changing it should affect only the outer layer, not the domain or use cases."} | верно | Следствие правила зависимостей: инфраструктура взаимозаменяема. |
T26-L1 1.07 c | DDD | In DDD, an aggregate is just another name for a database table. | «no» Пояснение: An aggregate in DDD is a bounded cluster of objects treated as a single unit for consistency, not merely a database table.
Raw{"answer":"no","explanation":"An aggregate in DDD is a bounded cluster of objects treated as a single unit for consistency, not merely a database table."} | верно | Агрегат — кластер объектов с границей согласованности (транзакционной вокруг корня); таблица — деталь хранения. |
T26-L2 1.03 c | DDD | A Value Object is immutable and compared by the values of its fields, not by identity. | «yes» Пояснение: A Value Object is inherently immutable and defines equality based on its field values rather than object identity.
Raw{"answer": "yes", "explanation": "A Value Object is inherently immutable and defines equality based on its field values rather than object identity."} | верно | Классика Evans: Money, Email; равенство структурное. |
T26-L3 1.09 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 entry point for external changes to an aggregate.
Raw{ ⏎ "answer": "aggregate root", ⏎ "explanation": "In DDD, the aggregate root is the entry point for external changes to an aggregate." ⏎ } | верно | Aggregate Root: внешние объекты ссылаются только на корень; он защищает инварианты агрегата. |
T26-L4 1.29 c | DDD | In DDD, a repository is declared for an aggregate (its root), not for every entity. | «yes» Пояснение: In DDD, repositories are defined per aggregate root, not per individual entity, to maintain aggregate consistency and transactional boundaries.
Raw{"answer":"yes","explanation":"In DDD, repositories are defined per aggregate root, not per individual entity, to maintain aggregate consistency and transactional boundaries."} | верно | Репозиторий корня хранит границу согласованности агрегата; вложенные сущности доступны только через корень. |
T26-L5 1.22 c | DDD | Ubiquitous language is the model's shared language common to developers and domain experts. | «yes» Пояснение: Ubiquitous language is the shared language used consistently between developers and domain experts.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Ubiquitous language is the shared language used consistently between developers and domain experts." ⏎ } | верно | Evans: язык из требований переходит в имена классов и методов. |
T26-L6 77.45 c | DDD | What is the boundary called within which a model and its language are consistent, while outside the same words mean other models? | «universe of discourse» Пояснение: It is the boundary or domain over which a language is interpreted in a model, so changing it can make the same words refer to different models.
Raw{ ⏎ "answer": "universe of discourse", ⏎ "explanation": "It is the boundary or domain over which a language is interpreted in a model, so changing it can make the same words refer to different models." ⏎ } | неверно верный: «bounded context» | Bounded Context; «Заказ» в биллинге и в доставке — разные модели. |
T26-L7 0.93 c | DDD | An anemic model (objects with only getters/setters, logic in services) is the recommended DDD style. | «no» Пояснение: DDD generally favors rich domain models where behavior lives in the domain objects, not anemic models with logic in services.
Raw{"answer": "no", "explanation": "DDD generally favors rich domain models where behavior lives in the domain objects, not anemic models with logic in services."} | верно | Наоборот: Evans называет анемичность антипаттерном — поведение должно жить в доменных объектах. |
T26-L8 2.02 c | DDD | Bounded context means each context has its own model: the same concept in different contexts is a different class. | «yes» Пояснение: In DDD, each bounded context has its own model, so the same concept may be represented by different classes or types in different contexts.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "In DDD, each bounded context has its own model, so the same concept may be represented by different classes or types in different contexts." ⏎ } | верно | Модели контекстов независимы; между ними — явная интеграция (ACL, published language). |
T13-L1 1.54 c | Symfony | Services in the Symfony DI container are created lazily by default — on first use. | «yes» Пояснение: Symfony's DI container instantiates services lazily by default, meaning they are created when first requested.
Raw{"answer": "yes", "explanation": "Symfony's DI container instantiates services lazily by default, meaning they are created when first requested."} | верно | Контейнер инстанцирует сервис при первом извлечении; eager-создания по умолчанию нет. |
T13-L2 8.02 c | Symfony | Which Symfony console command lists all registered routes? | «debug:router» Пояснение: The Symfony console command `debug:router` lists all registered application routes.
Raw{"answer": "debug:router", "explanation": "The Symfony console command `debug:router` lists all registered application routes."} | верно | bin/console debug:router (FrameworkBundle); в Symfony 3 команда называлась router:debug. |
T13-L3 1.24 c | Symfony | Symfony autowiring requires manually declaring every service in services.yaml. | «no» Пояснение: Symfony autowiring can automatically discover and create services based on type hints, so you don't need to manually declare every service in services.yaml.
Raw{"answer": "no", "explanation": "Symfony autowiring can automatically discover and create services based on type hints, so you don't need to manually declare every service in services.yaml."} | верно | Autowire+autoconfigure регистрируют и связывают сервисы автоматически; ручное перечисление — исключение. |
T13-L4 2.04 c | Symfony | Twig templates are compiled into PHP classes and cached between requests. | «yes» Пояснение: Twig compiles templates into PHP code, typically a PHP class, and caches the compiled output between requests.
Raw{"answer": "yes", "explanation": "Twig compiles templates into PHP code, typically a PHP class, and caches the compiled output between requests."} | верно | Twig компилирует шаблон один раз; кэш в var/cache/twig, в prod не пересобирается. |
T13-L5 7.12 c | Symfony | In the Symfony dev environment the DI container is rebuilt only after tracked files change, not on every request. | «yes» Пояснение: Symfony caches the compiled container in the dev environment and rebuilds it only when tracked files change, not on every request.
Raw{"answer":"yes","explanation":"Symfony caches the compiled container in the dev environment and rebuilds it only when tracked files change, not on every request."} | верно | Kernel проверяет freshness ресурсов (конфиги, классы); иначе переиспользуется кэш контейнера. |
T13-L6 2.98 c | Symfony | Which environment variable selects the active Symfony environment (dev/prod)? | «app_env» Пояснение: In Symfony, the APP_ENV environment variable (typically set in a .env file) determines the active application environment, such as dev, prod, or test.
Raw{"answer": "APP_ENV", "explanation": "In Symfony, the APP_ENV environment variable (typically set in a .env file) determines the active application environment, such as dev, prod, or test."} | верно | APP_ENV в .env; APP_DEBUG — отдельный флаг отладки. |
T13-L7 18.61 c | Symfony | A controller method can be private — Symfony routing works with any method of the class. | «no» Пояснение: Symfony routing can only invoke public controller methods as actions, not private ones.
Raw{"answer":"no","explanation":"Symfony routing can only invoke public controller methods as actions, not private ones."} | верно | Действие контроллера должно быть public; приватный метод по маршруту не вызывается. |
T13-L8 7.92 c | Symfony | Event subscribers always receive events before listeners, because the interface gives them priority. | «no» Пояснение: Interfaces do not inherently grant priority; event ordering depends on registration, priority values, or framework-specific rules rather than subscriber/listener status.
Raw{"answer":"no","explanation":"Interfaces do not inherently grant priority; event ordering depends on registration, priority values, or framework-specific rules rather than subscriber/listener status."} | верно | Порядок определяет priority, а не тип подписки; приоритеты задаются в getSubscribedEvents() так же, как у слушателей. |
T22-L1 6.5 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+ removed the legacy guard classes in favor of modern authenticator classes implementing AuthenticatorInterface.
Raw{"answer":"yes","explanation":"Symfony 6+ removed the legacy guard classes in favor of modern authenticator classes implementing AuthenticatorInterface."} | верно | Guard объявлен устаревшим в 5.3 и удалён в 6.0; в проекте symfony/security-bundle 8.1. |
T22-L2 3.4 c | Symfony: Security and forms | Which Symfony attribute checks a role/permission right on a controller method (403 without it)? | «isgranted» Пояснение: Symfony's IsGranted attribute restricts access by role or permission and raises a 403 AccessDenied exception if the check fails.
Raw{ ⏎ "answer": "IsGranted", ⏎ "explanation": "Symfony's IsGranted attribute restricts access by role or permission and raises a 403 AccessDenied exception if the check fails." ⏎ } | верно | #[IsGranted('ROLE_ADMIN')]; атрибут из symfony/security-http. |
T22-L3 1.3 c | Symfony: Security and forms | Voters are Symfony's mechanism for checking access to a specific object: isGranted('EDIT', $post). | «yes» Пояснение: Symfony Voters implement custom access rules and can be used with isGranted('EDIT', $post) to authorize object-specific actions.
Raw{"answer":"yes","explanation":"Symfony Voters implement custom access rules and can be used with isGranted('EDIT', $post) to authorize object-specific actions."} | верно | VoterInterface->vote(); docs Symfony — Voters. |
T22-L4 36.0 c | Symfony: Security and forms | In modern Symfony (7+) validation constraints are declared as PHP attributes (#[Assert\NotBlank]); doctrine annotations are no longer supported. | «yes» Пояснение: Symfony 7+ uses PHP attributes for validation constraints, and Doctrine ORM has moved away from annotations in favor of PHP attributes.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Symfony 7+ uses PHP attributes for validation constraints, and Doctrine ORM has moved away from annotations in favor of PHP attributes." ⏎ } | верно | Докблок-аннотации удалены в Symfony 7.0; стандарт — атрибуты. В проекте symfony/validator 8.1. |
T22-L5 4.05 c | Symfony: Security and forms | CSRF protection of Symfony forms is enabled by default: the form validates the token on submission. | «yes» Пояснение: Symfony automatically adds and validates a hidden CSRF token in forms by default unless it is explicitly disabled.
Raw{"answer": "yes", "explanation": "Symfony automatically adds and validates a hidden CSRF token in forms by default unless it is explicitly disabled."} | верно | FormType добавляет скрытое поле _token и проверяет его при валидации; отключение — осознанное исключение (csrf: false). |
T22-L6 1.26 c | Symfony: Security and forms | Form validation in Symfony runs server-side even if the client-side (HTML5) checks passed. | «yes» Пояснение: Symfony performs form validation on the server during processing, regardless of whether client-side HTML5 checks pass.
Raw{"answer": "yes", "explanation": "Symfony performs form validation on the server during processing, regardless of whether client-side HTML5 checks pass."} | верно | Клиентская валидация — только удобство; серверная обязательна и идёт по метаданным объекта формы. |
T22-L7 7.14 c | Symfony: Security and forms | Which Symfony maker command generates a form class (FormType)? | «make:form» Пояснение: The make:form command generates a Symfony FormType class.
Raw{ ⏎ "answer": "make:form", ⏎ "explanation": "The make:form command generates a Symfony FormType class." ⏎ } | верно | bin/console make:form (symfony/maker-bundle — в проекте). |
T22-L8 1.33 c | Symfony: Security and forms | Symfony stores the user's password in the session in plain text. | «no» Пояснение: Symfony Security does not store the user's plain-text password in the session; it stores authentication details such as the user identifier and roles.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "Symfony Security does not store the user's plain-text password in the session; it stores authentication details such as the user identifier and roles." ⏎ } | верно | В сессии живёт объект пользователя в токене; хеш затирается eraseCredentials(), plaintext там никогда не лежит. |
T23-L1 1.21 c | Symfony: configuration and services | Symfony bundle configuration lives in config/packages — one file per bundle or topic. | «yes» Пояснение: In Symfony 4 and later, the default configuration structure places bundle-specific config files in config/packages, with one YAML file per bundle or topic.
Raw{"answer": "yes", "explanation": "In Symfony 4 and later, the default configuration structure places bundle-specific config files in config/packages, with one YAML file per bundle or topic."} | верно | Стандартная структура (config/packages/*.yaml); перегрузка — config/packages/<env>. |
T23-L2 1.15 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» Пояснение: A committed .env with dev defaults and a non-committed .env.local for secrets is a common safe practice.
Raw{"answer":"yes","explanation":"A committed .env with dev defaults and a non-committed .env.local for secrets is a common safe practice."} | верно | symfony/dotenv: .env — общий безопасный набор значений; локальные секреты — .env.local (gitignored) или secrets-хранилище. |
T23-L3 0.86 c | Symfony: configuration and services | Which Symfony command lists the container's registered services and their aliases? | «debug:container» Пояснение: The Symfony command debug:container lists all registered services and their aliases in the DI container.
Raw{"answer": "debug:container", "explanation": "The Symfony command debug:container lists all registered services and their aliases in the DI container."} | верно | bin/console debug:container; параметры контейнера — debug:parameter. |
T23-L4 6.49 c | Symfony: configuration and services | The Symfony container allows changing parameters at runtime: $container->setParameter() works from a controller. | «yes» Пояснение: The container's setParameter() method is available and can technically be called from a controller, although doing so is strongly discouraged in favor of dependency injection.
Raw{"answer": "yes", "explanation": "The container's setParameter() method is available and can technically be called from a controller, although doing so is strongly discouraged in favor of dependency injection."} | неверно верный: «no» | Контейнер компилируется и замораживается; runtime-значения — только через переменные окружения. |
T23-L5 13.31 c | Symfony: configuration and services | By default, Symfony services are public (public: true) — you can fetch them directly from the container. | «no» Пояснение: In modern Symfony, services are non-public by default and must be explicitly marked public to be fetched from the container.
Raw{"answer": "no", "explanation": "In modern Symfony, services are non-public by default and must be explicitly marked public to be fetched from the container."} | верно | С Symfony 4.0 сервисы по умолчанию private: инжектятся через autowiring; $container->get() — только для публичных. |
T23-L6 1.08 c | Symfony: configuration and services | Without a config file in config/packages a bundle will not work — configuration is mandatory for every bundle. | «no» Пояснение: A bundle does not always require a config file in config/packages; many bundles can use default configuration.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "A bundle does not always require a config file in config/packages; many bundles can use default configuration." ⏎ } | верно | У бандлов есть встроенные умолчания (Extension); конфиг нужен только для отклонений от них. |
T23-L7 1.35 c | Symfony: configuration and services | Environment variable values are injected into services.yaml using the %env(VAR)% syntax. | «yes» Пояснение: Symfony uses the %env(VAR)% placeholder syntax to inject environment variable values into configuration files such as services.yaml.
Raw{"answer":"yes","explanation":"Symfony uses the %env(VAR)% placeholder syntax to inject environment variable values into configuration files such as services.yaml."} | верно | %env(...)% резолвится в рантайме env-процессорами; docs — Env Var Processors. |
T23-L8 1.22 c | Symfony: configuration and services | Which Symfony environment variable enables debug mode (affects the profiler and Twig debugging)? | «app_debug» Пояснение: APP_DEBUG is the Symfony environment variable that enables debug mode, including profiler and related debugging behavior.
Raw{ ⏎ "answer": "APP_DEBUG", ⏎ "explanation": "APP_DEBUG is the Symfony environment variable that enables debug mode, including profiler and related debugging behavior." ⏎ } | верно | APP_DEBUG=1 (в .env dev-окружения); окружение выбирает APP_ENV — см. T13-L6. |
T16-L1 1.82 c | Symfony: Messenger | A single message in Symfony Messenger can only have one handler. | «no» Пояснение: A message can be registered with multiple handlers, and all matching handlers can process it.
Raw{"answer":"false","explanation":"A message can be registered with multiple handlers, and all matching handlers can process it."} | верно | Messenger вызывает все хендлеры, подписанные на класс сообщения (docs — Multiple Handlers). |
T16-L2 1.92 c | Symfony: Messenger | The sync transport in Messenger queues the message for a worker, just like async. | «no» Пояснение: The sync transport processes the message immediately in the sending process without queuing it for a separate worker.
Raw{"answer": "no", "explanation": "The sync transport processes the message immediately in the sending process without queuing it for a separate worker."} | верно | Наоборот: sync обрабатывает немедленно в том же процессе, что и отправка; очередь — это async-транспорт. |
T16-L3 1.62 c | Symfony: Messenger | Which console command starts the worker that processes Messenger queue messages? | «messenger:consume» Пояснение: The Symfony console command messenger:consume starts a worker that processes Messenger queue messages.
Raw{"answer":"messenger:consume","explanation":"The Symfony console command messenger:consume starts a worker that processes Messenger queue messages."} | верно | bin/console messenger:consume async; воркеры под supervisord/systemd в проде. |
T16-L4 8.86 c | Symfony: Messenger | Retries for failed messages (retry_strategy) are configured per Messenger transport. | «yes» Пояснение: In Symfony Messenger, retry_strategy is configured within the configuration of each messenger transport.
Raw{"answer":"yes","explanation":"In Symfony Messenger, retry_strategy is configured within the configuration of each messenger transport."} | верно | retry_strategy на транспорте: max_retries, delay, multiplier; docs — Failed Messages & Retries. |
T16-L5 3.85 c | Symfony: Messenger | By default, Messenger serializes messages to JSON. | «yes» Пояснение: By default, Symfony Messenger serializes messages to JSON.
Raw{"answer": "yes", "explanation": "By default, Symfony Messenger serializes messages to JSON."} | неверно верный: «no» | Дефолтный сериализатор — PhpSerializer (serialize()); JSON-сериализатор включается отдельно. |
T16-L6 6.34 c | Symfony: Messenger | Symfony Scheduler produces messages on a schedule and dispatches them through Messenger. | «yes» Пояснение: Symfony Scheduler is designed to schedule Messenger messages so they are produced and dispatched through Symfony Messenger.
Raw{"answer": "yes", "explanation": "Symfony Scheduler is designed to schedule Messenger messages so they are produced and dispatched through Symfony Messenger."} | верно | Schedule → RecurringMessage → шина Messenger; docs — Scheduler. |
T16-L7 1.5 c | Symfony: Messenger | Which built-in Messenger transport stores messages in database tables via Doctrine? | «database» Пояснение: Symfony's Messenger component includes a built-in 'database' transport that persists messages in database tables using Doctrine (or PDO).
Raw{"answer": "database", "explanation": "Symfony's Messenger component includes a built-in 'database' transport that persists messages in database tables using Doctrine (or PDO)."} | неверно верный: «doctrine» | Транспорт doctrine (symfony/doctrine-messenger); таблица messenger_messages. В проекте стоит amqp-messenger + doctrine-messenger. |
T16-L8 2.01 c | Symfony: Messenger | The Messenger pipeline can be extended with custom middleware, placed before or after the built-in ones. | «yes» Пояснение: Custom middleware can be added to the Messenger pipeline and positioned before or after the built-in middleware.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Custom middleware can be added to the Messenger pipeline and positioned before or after the built-in middleware." ⏎ } | верно | messenger.bus.*.middleware в yaml; docs — Middleware. |
T28-L1 4.8 c | Symfony: versions | Symfony major releases come every two years, minor ones every six months (in May and November). | «no» Пояснение: Symfony major releases have not followed a strict two-year cadence; for example, Symfony 3.0 (2014), 4.0 (2017), 5.0 (2019), and 6.0 (2022) were released at irregular two-to-three year intervals, even though minor releases do occur roughly every six months (May and November).
Raw{"answer": "no", "explanation": "Symfony major releases have not followed a strict two-year cadence; for example, Symfony 3.0 (2014), 4.0 (2017), 5.0 (2019), and 6.0 (2022) were released at irregular two-to-three year intervals, even though minor releases do occur roughly every six months (May and November)."} | неверно верный: «yes» | Стандартный релизный цикл: 8.0 — ноябрь 2025, 8.1 — май 2026, 8.2 — ноябрь 2026. |
T28-L2 10.43 c | Symfony: versions | What is the minimum PHP version required by Symfony 8? | «8.3» Пояснение: Symfony 8 requires PHP 8.3 or higher.
Raw{ ⏎ "answer": "8.3", ⏎ "explanation": "Symfony 8 requires PHP 8.3 or higher." ⏎ } | неверно верный: «8.4» | Symfony 8.0 поднял требование до PHP >= 8.4.1 (в vendor проекта: "php": ">=8.4.1"). |
T28-L3 22.63 c | Symfony: versions | Symfony 7.0 kept support for docblock annotations (validation, routes). | «no» Пояснение: Symfony 7.0 removed docblock annotation support for validation and routes in favor of PHP attributes.
Raw{"answer":"no","explanation":"Symfony 7.0 removed docblock annotation support for validation and routes in favor of PHP attributes."} | верно | Наоборот: в 7.0 аннотации удалены — только PHP-атрибуты (#[Route], #[Assert\NotBlank]). |
T28-L4 30.8 c | Symfony: versions | AssetMapper manages CSS/JS without node or webpack — via importmap.php. | «yes» Пояснение: AssetMapper uses importmap.php to map CSS/JS assets without requiring Node or Webpack.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "AssetMapper uses importmap.php to map CSS/JS assets without requiring Node or Webpack." ⏎ } | верно | symfony/asset-mapper (с 6.3, стандарт с 7.x); в проекте — importmap.php в корне и asset-mapper 8.1. |
T28-L5 123.47 c | Symfony: versions | Symfony 6.4 is a regular release without long-term support. | «no» Пояснение: Symfony 6.4 is an LTS release, so it does have long-term support.
Raw{"answer": "no", "explanation": "Symfony 6.4 is an LTS release, so it does have long-term support."} | верно | Наоборот: 6.4 — LTS (расширенная поддержка); LTS выходит вместе с очередным мажором (6.4 — вместе с 7.0). |
T28-L6 1.56 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 typically remove deprecations introduced in the previous branch.
Raw{"answer": "no", "explanation": "Symfony major releases typically remove deprecations introduced in the previous branch."} | верно | Наоборот: мажорный релиз удаляет всё устаревшее (7.0 убрал деприкейшены 6.x, 8.0 — 7.x). |
T28-L7 1.52 c | Symfony: versions | Every Symfony major release is accompanied by an UPGRADE guide listing the changes. | «yes» Пояснение: Symfony publishes an upgrade guide for each major release to describe significant changes.
Raw{"answer":"yes","explanation":"Symfony publishes an upgrade guide for each major release to describe significant changes."} | верно | UPGRADE-7.0.md, UPGRADE-8.0.md в репозитории symfony/symfony. |
T28-L8 2.24 c | Symfony: versions | Which Symfony component manages assets and the importmap without node/webpack? | «assetmapper» Пояснение: The Symfony AssetMapper component manages assets and importmap without requiring Node.js or webpack.
Raw{ ⏎ "answer": "AssetMapper", ⏎ "explanation": "The Symfony AssetMapper component manages assets and importmap without requiring Node.js or webpack." ⏎ } | верно | symfony/asset-mapper 8.1 — в проекте. |
T29-L1 23.8 c | Symfony: 8.2 and beyond | As of 2026-11-07, Symfony 8.2 has already been released. | «no» Пояснение: By November 2026, Symfony 8.2 would not yet have reached release in Symfony's semi-annual release schedule.
Raw{"answer": "no", "explanation": "By November 2026, Symfony 8.2 would not yet have reached release in Symfony's semi-annual release schedule."} | верно | Наоборот: 8.2 ещё не выпущена — релиз в конце ноября 2026; последняя стабильная — 8.1. |
T29-L2 14.4 c | Symfony: 8.2 and beyond | As of 2026-11-07, Symfony 8.2 is scheduled for November 2026, following the usual six-month cycle. | «no» Пояснение: Following the normal cycle, Symfony 8.0 is scheduled for November 2026 and Symfony 8.2 for November 2027.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "Following the normal cycle, Symfony 8.0 is scheduled for November 2026 and Symfony 8.2 for November 2027." ⏎ } | неверно верный: «yes» | Политика релизов: 8.1 — май 2026, 8.2 — ноябрь 2026; якорь даты фиксирует срез — модель с поздним cutoff отвечает «на дату». |
T29-L3 26.05 c | Symfony: 8.2 and beyond | Which Symfony version comes after 8.1 (as of 2026-11-07)? | «8.2» Пояснение: The next version after Symfony 8.1 in the 8.x series is 8.2.
Raw{"answer": "8.2", "explanation": "The next version after Symfony 8.1 in the 8.x series is 8.2."} | верно | 8.2 — следующий минорный релиз (ноябрь 2026); после его выхода проект переходит с 8.1.* на 8.2.*. |
T29-L4 1.9 c | Symfony: 8.2 and beyond | Symfony 8.2 is a major release requiring applications to be rewritten for new APIs. | «no» Пояснение: Symfony 8.2 is a minor/feature release, not a major release requiring a full rewrite.
Raw{"answer": "no", "explanation": "Symfony 8.2 is a minor/feature release, not a major release requiring a full rewrite."} | верно | Наоборот: 8.2 — минорный релиз; новые возможности без поломки обратной совместимости. Мажор — 9.0. |
T29-L5 4.17 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 8.2 is a minor update within the PHP 8 line and maintains backward compatibility with PHP 8.1, so existing code generally keeps working.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "PHP 8.2 is a minor update within the PHP 8 line and maintains backward compatibility with PHP 8.1, so existing code generally keeps working." ⏎ } | верно | Политика Symfony: минорные релизы обратно совместимы; BC-break допустим только в мажорных. |
T29-L6 41.17 c | Symfony: 8.2 and beyond | Which minor version of the 8.x branch is released last, before Symfony 9.0? | «8.4» Пояснение: The last minor version in the Symfony 8.x branch before Symfony 9.0 is 8.4.
Raw{"answer": "8.4", "explanation": "The last minor version in the Symfony 8.x branch before Symfony 9.0 is 8.4."} | верно | По циклу: 8.2 (ноя 2026), 8.3 (май 2027), 8.4 (ноя 2027, вместе с 9.0) — как 6.4 выходила вместе с 7.0. |
T29-L7 5.56 c | Symfony: 8.2 and beyond | Symfony 8.2 will require PHP 8.5 — you would have to upgrade PHP along with it. | «no» Пояснение: Symfony 8.2 does not require PHP 8.5, so upgrading to PHP 8.5 is not necessary.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "Symfony 8.2 does not require PHP 8.5, so upgrading to PHP 8.5 is not necessary." ⏎ } | верно | Наоборот: минорные релизы не поднимают требования PHP; для всей ветки 8.x остаётся PHP >= 8.4. |
T29-L8 4.18 c | Symfony: 8.2 and beyond | Deprecations added in the 8.x branch will not be removed before Symfony 9.0. | «yes» Пояснение: Symfony deprecations added in the 8.x branch are retained until at least the next major release, Symfony 9.0.
Raw{"answer": "yes", "explanation": "Symfony deprecations added in the 8.x branch are retained until at least the next major release, Symfony 9.0."} | верно | Политика: деприкейшены живут до следующего мажора; 9.0 — ноябрь 2027. |
T21-L1 1.73 c | Twig | Inside {{ }}, Twig allows calling arbitrary PHP code directly. | «no» Пояснение: Twig's {{ }} block only allows Twig expressions (variables, filters, functions registered with the environment), not arbitrary PHP code like var_dump() or print_r().
Raw{"answer": "no", "explanation": "Twig's {{ }} block only allows Twig expressions (variables, filters, functions registered with the environment), not arbitrary PHP code like var_dump() or print_r()."} | верно | Twig — DSL: только разрешённые окружением функции/фильтры; произвольный PHP не исполняется. |
T21-L2 2.13 c | Twig | By default, Twig auto-escapes printed variables. | «yes» Пояснение: By default, Twig enables automatic escaping for printed variables.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "By default, Twig enables automatic escaping for printed variables." ⏎ } | верно | Autoescape включён по умолчанию; {{ '<b>' }} → <b>. Проверено на Twig 3.30. |
T21-L3 1.29 c | Twig | The Twig |e filter escapes a string for safe output in an HTML context. | «yes» Пояснение: The Twig |e filter escapes a string for HTML context by default.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "The Twig |e filter escapes a string for HTML context by default." ⏎ } | верно | |e ('html') по умолчанию; есть контексты js/url/css. От SQL-инъекций он не защищает — это задача подготовленных запросов Doctrine. |
T21-L4 1.56 c | Twig | Which filter from twig/intl-extra formats a number according to a locale? | «format_number» Пояснение: The format_number filter from twig/intl-extra formats a number according to a specified locale.
Raw{"answer": "format_number", "explanation": "The format_number filter from twig/intl-extra formats a number according to a specified locale."} | верно | |format_number(locale=...) из IntlExtension (twig/intl-extra есть в проекте). Проверено на Twig 3.30: 12345.6 → 12 345,6 (ru). |
T21-L5 1.76 c | Twig | The |raw filter disables auto-escaping for the value. | «yes» Пояснение: The |raw filter outputs the value without auto-escaping.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "The |raw filter outputs the value without auto-escaping." ⏎ } | верно | {{ x|raw }} выводит HTML как есть; опасно с пользовательскими данными. Проверено на Twig 3.30. |
T21-L6 1.26 c | Twig | In Twig, {{ }} prints an expression value, while {% %} executes tags — conditions, loops, set. | «yes» Пояснение: In Twig, {{ }} outputs the result of an expression, while {% %} is used for tags like conditions, loops, and assignments.
Raw{"answer": "yes", "explanation": "In Twig, {{ }} outputs the result of an expression, while {% %} is used for tags like conditions, loops, and assignments."} | верно | Два блока синтаксиса Twig: вывод (echo) против логики. |
T21-L7 0.92 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, for example using {% set %}.
Raw{"answer": "no", "explanation": "Twig allows you to declare variables inside a template, for example using {% set %}."} | верно | {% set y = ... %} объявляет переменную в шаблоне. Проверено на Twig 3.30. |
T21-L8 1.02 c | Twig | Which Twig function dumps the debug structure of a variable (array, object)? | «dump» Пояснение: The dump() Twig function displays the debug structure of a variable such as an array or object, similar to PHP's var_dump().
Raw{"answer": "dump", "explanation": "The dump() Twig function displays the debug structure of a variable such as an array or object, similar to PHP's var_dump()."} | верно | {{ dump(x) }} (DebugExtension; в Symfony доступна в dev-окружении). |
T24-L1 1.08 c | Bootstrap | Bootstrap is a CSS/JS library of ready-made UI components, not an SPA framework. | «yes» Пояснение: Bootstrap is primarily a front-end CSS/JS library providing reusable UI components and utilities, not a single-page application framework.
Raw{"answer": "yes", "explanation": "Bootstrap is primarily a front-end CSS/JS library providing reusable UI components and utilities, not a single-page application framework."} | верно | Компоненты и утилиты поверх вашего HTML; SPA-фреймворки (React/Vue) — другой класс инструментов. В проекте vendored 5.3.3. |
T24-L2 1.3 c | Bootstrap | Which Bootstrap class gives a responsive container with a fixed max width per breakpoint? | «container» Пояснение: The .container class creates a responsive container with a fixed max-width at each breakpoint in Bootstrap.
Raw{"answer": "container", "explanation": "The .container class creates a responsive container with a fixed max-width at each breakpoint in Bootstrap."} | верно | .container (фиксированная макс-ширина по брейкпоинтам) vs .container-fluid (на всю ширину). |
T24-L3 1.66 c | Bootstrap | The Bootstrap grid is built on CSS floats and splits a row into 16 columns. | «no» Пояснение: The Bootstrap grid traditionally splits a row into 12 columns, not 16.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "The Bootstrap grid traditionally splits a row into 12 columns, not 16." ⏎ } | верно | Наоборот: flexbox (с Bootstrap 4) и 12 колонок; float-сетка — это Bootstrap 3. |
T24-L4 1.35 c | Bootstrap | Bootstrap's named breakpoints (the infix used in class names) are sm, md, lg, xl, xxl — five of them. | «yes» Пояснение: Bootstrap's standard named breakpoint prefixes are sm, md, lg, xl, and xxl.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Bootstrap's standard named breakpoint prefixes are sm, md, lg, xl, and xxl." ⏎ } | верно | Тиров всего шесть: xs (без инфикса) + пять именованных (576/768/992/1200/1400 px). |
T24-L5 30.47 c | Bootstrap | Utilities like .mt-3 or .px-2 use the spacing scale: the number is a multiple of $spacer. | «yes» Пояснение: The numeric suffix indexes the spacing scale, which is generated from the base spacing unit.
Raw{"answer": "yes", "explanation": "The numeric suffix indexes the spacing scale, which is generated from the base spacing unit."} | неверно верный: «no» | Spacing utilities; $spacer = 1rem. |
T24-L6 2.1 c | Bootstrap | Which Bootstrap 5 data attribute enables an interactive component (e.g. dropdown) on an element? | «data-bs-toggle» Пояснение: Bootstrap 5 uses the data-bs-toggle attribute to enable interactive components such as dropdowns on an element.
Raw{"answer": "data-bs-toggle", "explanation": "Bootstrap 5 uses the data-bs-toggle attribute to enable interactive components such as dropdowns on an element."} | верно | data-bs-toggle="dropdown" и т.п.; в Bootstrap 4 атрибут назывался data-toggle. |
T24-L7 0.79 c | Bootstrap | Bootstrap 5 components work without jQuery — in plain vanilla JS. | «yes» Пояснение: Bootstrap 5 removed its jQuery dependency and provides components powered by vanilla JavaScript.
Raw{"answer": "yes", "explanation": "Bootstrap 5 removed its jQuery dependency and provides components powered by vanilla JavaScript."} | верно | jQuery удалён в Bootstrap 5.0: data-bs-* атрибуты и JS API. В проекте vendored 5.3.3. |
T24-L8 5.31 c | Bootstrap | Dark mode in Bootstrap is enabled with a .dark class on the root element. | «no» Пояснение: In Bootstrap 5, dark mode is enabled by adding the data-bs-theme="dark" attribute to the root element, not by applying a .dark class to it.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "In Bootstrap 5, dark mode is enabled by adding the data-bs-theme=\"dark\" attribute to the root element, not by applying a .dark class to it." ⏎ } | верно | Наоборот: тема включается атрибутом data-bs-theme="dark" (Color modes, с 5.3); класса .dark не существует. В проекте 5.3.3. |
T14-L1 1.2 c | Doctrine | Doctrine ORM creates database tables on the fly the first time an entity is used at runtime. | «no» Пояснение: Doctrine ORM does not automatically create database tables at runtime when entities are first used; schema creation or migration tools must be run separately.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "Doctrine ORM does not automatically create database tables at runtime when entities are first used; schema creation or migration tools must be run separately." ⏎ } | верно | Схему создают инструменты (migrations, schema tool); рантайм структуру БД не меняет. |
T14-L2 1.3 c | Doctrine | Which EntityManager method marks a new object as managed without executing SQL until flush()? | «persist» Пояснение: The persist() method marks an object as managed by the EntityManager without issuing any SQL until flush() is called.
Raw{"answer": "persist", "explanation": "The persist() method marks an object as managed by the EntityManager without issuing any SQL until flush() is called."} | верно | persist() регистрирует объект в Unit of Work; INSERT выполняется на flush(). |
T14-L3 54.57 c | Doctrine | In Doctrine ORM 3, the EntityManager::merge() method exists and makes the passed object managed. | «yes» Пояснение: In Doctrine ORM 3, EntityManager::merge() exists and makes the passed object managed.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "In Doctrine ORM 3, EntityManager::merge() exists and makes the passed object managed." ⏎ } | неверно верный: «no» | В ORM 3 merge() удалён (в vendor проекта 3.7.6 метода нет); в Doctrine 2.x merge() возвращал управляемую копию. Версия зафиксирована — ORM 3. |
T14-L4 1.61 c | Doctrine | DQL queries are written in terms of entities and their fields, not tables and columns. | «yes» Пояснение: DQL (Domain Query Language) in Doctrine ORM is designed to work with the object model, referencing entity class aliases and their mapped properties/fields rather than physical database table and column names.
Raw{"answer": "yes", "explanation": "DQL (Domain Query Language) in Doctrine ORM is designed to work with the object model, referencing entity class aliases and their mapped properties/fields rather than physical database table and column names."} | верно | Doctrine транслирует DQL в SQL; docs — DQL (Doctrine Query Language). |
T14-L5 4.22 c | Doctrine | What does $repository->find(999) return when no record with id 999 exists? | «null» Пояснение: When the requested record is not found, find() returns null.
Raw{"answer": "null", "explanation": "When the requested record is not found, find() returns null."} | верно | find() возвращает null, если объект не найден (docs Repository methods). |
T14-L6 92.34 c | Doctrine | DoctrineBundle in Symfony automatically calls flush() at the end of every request. | «yes» Пояснение: By default DoctrineBundle enables auto_flush, so it calls flush() on the EntityManager at the end of each request.
Raw{"answer": "yes", "explanation": "By default DoctrineBundle enables auto_flush, so it calls flush() on the EntityManager at the end of each request."} | неверно верный: «no» | Авто-flush нет — flush() зовёт разработчик; незакрытая транзакция в конце запроса откатывается. |
T14-L7 0.84 c | Doctrine | For a managed entity, changing a property is enough: flush() commits the change without an explicit persist() — the Unit of Work tracks changes. | «yes» Пояснение: A managed entity is tracked by the Unit of Work, so property changes are detected and flushed without needing persist().
Raw{"answer":"yes","explanation":"A managed entity is tracked by the Unit of Work, so property changes are detected and flushed without needing persist()."} | верно | Dirty checking сравнивает снимки свойств; persist нужен только новым/отсоединённым объектам. |
T14-L8 1.15 c | Doctrine | remove() executes the SQL DELETE immediately, without waiting for flush(). | «no» Пояснение: remove() only marks the entity for deletion; the SQL DELETE runs when flush() is called.
Raw{"answer": "no", "explanation": "remove() only marks the entity for deletion; the SQL DELETE runs when flush() is called."} | верно | remove() планирует удаление в Unit of Work; DELETE выполняется на flush() (docs — Deleting Objects). |
T15-L1 1.6 c | PostgreSQL | PostgreSQL uses MVCC, therefore readers block writers and writers block readers. | «no» Пояснение: PostgreSQL's MVCC generally allows concurrent reads and writes, so readers do not block writers and writers do not block readers.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "PostgreSQL's MVCC generally allows concurrent reads and writes, so readers do not block writers and writers do not block readers." ⏎ } | верно | Наоборот: благодаря MVCC читатели не блокируют писателей и наоборот (снимки строк); docs PostgreSQL — Concurrency Control. |
T15-L2 1.5 c | PostgreSQL | Which SQL command shows a query's execution plan without executing the query? | «explain» Пояснение: The EXPLAIN SQL command displays a query's execution plan without actually executing it.
Raw{ ⏎ "answer": "EXPLAIN", ⏎ "explanation": "The EXPLAIN SQL command displays a query's execution plan without actually executing it." ⏎ } | верно | EXPLAIN без ANALYZE только строит план; проверено на PostgreSQL 17.7. |
T15-L3 10.45 c | PostgreSQL | SERIAL and GENERATED ... AS IDENTITY are just two names for the same mechanism. | «no» Пояснение: SERIAL is a PostgreSQL convenience shorthand that creates a sequence-backed column, while GENERATED ... AS IDENTITY is the standard SQL identity-column mechanism.
Raw{"answer":"no","explanation":"SERIAL is a PostgreSQL convenience shorthand that creates a sequence-backed column, while GENERATED ... AS IDENTITY is the standard SQL identity-column mechanism."} | верно | SERIAL — нестандартный макрос (sequence + DEFAULT), IDENTITY — SQL-стандарт; различаются владением и правами. Оба есть в PG 17 (проверено). |
T15-L4 2.69 c | PostgreSQL | By default, a PostgreSQL UNIQUE constraint allows only one row with NULL in the column. | «no» Пояснение: By default, PostgreSQL treats NULL values as distinct in UNIQUE constraints, so multiple rows can have NULL in the column.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "By default, PostgreSQL treats NULL values as distinct in UNIQUE constraints, so multiple rows can have NULL in the column." ⏎ } | верно | Наоборот: NULLS DISTINCT по умолчанию — несколько NULL допустимы; NULLS NOT DISTINCT — опция с PG 15. Проверено на PG 17.7. |
T15-L5 0.67 c | PostgreSQL | Which PostgreSQL aggregate function concatenates strings with a separator? | «string_agg» Пояснение: PostgreSQL's string_agg() aggregates strings using an optional separator.
Raw{"answer": "string_agg", "explanation": "PostgreSQL's string_agg() aggregates strings using an optional separator."} | верно | string_agg(значение, разделитель); проверено на PostgreSQL 17.7. |
T15-L6 3.11 c | PostgreSQL | Plain VACUUM returns the space occupied by dead tuples to the operating system. | «no» Пояснение: Plain VACUUM reclaims space for reuse within the database, but only VACUUM FULL returns unused space to the operating system.
Raw{"answer": "no", "explanation": "Plain VACUUM reclaims space for reuse within the database, but only VACUUM FULL returns unused space to the operating system."} | верно | VACUUM помечает место для переиспользования внутри таблицы; ОС его возвращает только VACUUM FULL (с эксклюзивной блокировкой). |
T15-L7 1.25 c | PostgreSQL | Which keyword in a window function definition partitions rows into groups the function is computed over? | «partition by» Пояснение: In a window function definition, the PARTITION BY clause divides rows into groups (partitions) over which the window function is computed.
Raw{"answer": "PARTITION BY", "explanation": "In a window function definition, the PARTITION BY clause divides rows into groups (partitions) over which the window function is computed."} | верно | OVER (PARTITION BY ...); проверено на PostgreSQL 17.7. |
T15-L8 2.47 c | PostgreSQL | The READ COMMITTED isolation level protects against non-repeatable reads. | «no» Пояснение: READ COMMITTED does not guarantee consistent re-reads, so a transaction can see different values on repeated reads if another transaction commits changes.
Raw{"answer": "no", "explanation": "READ COMMITTED does not guarantee consistent re-reads, so a transaction can see different values on repeated reads if another transaction commits changes."} | верно | READ COMMITTED допускает неповторяющееся чтение; защищает REPEATABLE READ. Проверено: SHOW transaction_isolation → read committed. |
T17-L1 1.56 c | PostgreSQL: transactions and indexes | By default, PostgreSQL wraps each single SQL statement in its own implicit transaction (autocommit). | «yes» Пояснение: In PostgreSQL's default autocommit mode, each SQL statement runs in its own implicit transaction unless an explicit transaction is started.
Raw{"answer":"yes","explanation":"In PostgreSQL's default autocommit mode, each SQL statement runs in its own implicit transaction unless an explicit transaction is started."} | верно | Без BEGIN каждый оператор коммитится сам; docs PostgreSQL — Transactions. Проверено на PG 17. |
T17-L2 0.66 c | PostgreSQL: transactions and indexes | Which SQL command ends a transaction, committing all its changes? | «commit» Пояснение: COMMIT is the SQL command that finalizes a transaction, permanently saving all changes made during the transaction.
Raw{"answer": "COMMIT", "explanation": "COMMIT is the SQL command that finalizes a transaction, permanently saving all changes made during the transaction."} | верно | COMMIT (END — синоним). Проверено на PG 17. |
T17-L3 1.21 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 also improve the speed of UPDATE and DELETE operations when they filter or search on an indexed column.
Raw{"answer":"yes","explanation":"Indexes can also improve the speed of UPDATE and DELETE operations when they filter or search on an indexed column."} | верно | Поиск строк для изменения идёт по индексу; docs PostgreSQL — Indexes. |
T17-L4 1.32 c | PostgreSQL: transactions and indexes | To roll back part of the statements inside a transaction, PostgreSQL uses SAVEPOINT. | «yes» Пояснение: SAVEPOINT (used with ROLLBACK TO <savepoint>) allows you to roll back only a portion of a transaction rather than the entire transaction.
Raw{"answer":"yes","explanation":"SAVEPOINT (used with ROLLBACK TO <savepoint>) allows you to roll back only a portion of a transaction rather than the entire transaction."} | верно | SAVEPOINT name; ROLLBACK TO name — частичный откат без отмены всей транзакции. Проверено на PG 17. |
T17-L5 1.26 c | PostgreSQL: transactions and indexes | EXPLAIN ANALYZE shows the query plan without executing the query. | «no» Пояснение: EXPLAIN ANALYZE executes the query to analyze actual performance, while plain EXPLAIN shows the plan without execution.
Raw{"answer": "no", "explanation": "EXPLAIN ANALYZE executes the query to analyze actual performance, while plain EXPLAIN shows the plan without execution."} | верно | Наоборот: ANALYZE реально выполняет запрос (с побочными эффектами!) и показывает фактические времена узлов; план без выполнения — plain EXPLAIN. |
T17-L6 0.94 c | PostgreSQL: transactions and indexes | Which PostgreSQL extension adds vector types and indexes for embedding search? | «pgvector» Пояснение: pgvector is a PostgreSQL extension that adds vector types and indexes for embedding search.
Raw{"answer": "pgvector", "explanation": "pgvector is a PostgreSQL extension that adds vector types and indexes for embedding search."} | верно | CREATE EXTENSION vector (проект pgvector; в проекте образ pgvector/pgvector:pg17). |
T17-L7 1.06 c | PostgreSQL: transactions and indexes | A partial index (CREATE INDEX ... WHERE ...) is built only over rows satisfying the condition. | «yes» Пояснение: A partial index indexes only the rows that satisfy the specified WHERE condition.
Raw{"answer": "yes", "explanation": "A partial index indexes only the rows that satisfy the specified WHERE condition."} | верно | docs PostgreSQL — Partial Indexes; типичный кейс — индекс по «активным» записям. |
T17-L8 28.83 c | PostgreSQL: transactions and indexes | The SERIALIZABLE level in PostgreSQL is implemented by locking the rows a transaction reads. | «no» Пояснение: PostgreSQL implements SERIALIZABLE using snapshot isolation plus SSI conflict detection, not by locking read rows.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "PostgreSQL implements SERIALIZABLE using snapshot isolation plus SSI conflict detection, not by locking read rows." ⏎ } | верно | SSI (Serializable Snapshot Isolation): предикатные блокировки на снимках, не блокировки прочитанных строк; docs PostgreSQL. |
T19-L1 1.02 c | HTTP and REST API | HTTP status 201 means the request resulted in a new resource being created. | «yes» Пояснение: HTTP status 201 'Created' indicates that the request successfully resulted in the creation of a new resource.
Raw{"answer": "yes", "explanation": "HTTP status 201 'Created' indicates that the request successfully resulted in the creation of a new resource."} | верно | 201 Created; обычно на POST, часто с Location; RFC 9110. |
T19-L2 0.99 c | HTTP and REST API | Which HTTP status means a successful request with an empty response body (e.g. after DELETE)? | «204» Пояснение: HTTP status 204 No Content indicates success with an empty response body.
Raw{"answer": 204, "explanation": "HTTP status 204 No Content indicates success with an empty response body."} | верно | 204 No Content; RFC 9110. |
T19-L3 4.89 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 defines DELETE as idempotent, so repeating it on the same resource has no further effect, though the response may differ if the resource is already gone.
Raw{"answer": "yes", "explanation": "The HTTP specification defines DELETE as idempotent, so repeating it on the same resource has no further effect, though the response may differ if the resource is already gone."} | верно | RFC 9110: DELETE идемпотентен (как PUT); идемпотентность ≠ безопасность — ресурс удаляется при первом вызове. |
T19-L4 1.27 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 permit a client to access the resource cross-origin.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "The Access-Control-Allow-Origin header is sent by the server, not the client, to permit a client to access the resource cross-origin." ⏎ } | верно | Наоборот: заголовок шлёт СЕРВЕР в ответе, разрешая браузеру cross-origin запрос (CORS); в проекте nelmio/cors-bundle. |
T19-L5 0.72 c | HTTP and REST API | Status 429 Too Many Requests is used when a client exceeds a rate limit. | «yes» Пояснение: HTTP 429 indicates the client has made too many requests in a given period and should slow down.
Raw{"answer": "yes", "explanation": "HTTP 429 indicates the client has made too many requests in a given period and should slow down."} | верно | 429 (+ Retry-After); RFC 6585. В проекте symfony/rate-limiter. |
T19-L6 0.87 c | HTTP and REST API | 5xx codes mean a client error, while 4xx means a server-side error. | «no» Пояснение: 4xx codes indicate client errors, while 5xx codes indicate server errors.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "4xx codes indicate client errors, while 5xx codes indicate server errors." ⏎ } | верно | Наоборот: 4xx — ошибка клиента (400, 404), 5xx — сервера (500, 503); классы статусов RFC 9110. |
T19-L7 0.67 c | HTTP and REST API | Which HTTP header indicates the MIME type of the request or response body? | «content-type» Пояснение: The Content-Type header specifies the MIME type of the request or response body.
Raw{ ⏎ "answer": "Content-Type", ⏎ "explanation": "The Content-Type header specifies the MIME type of the request or response body." ⏎ } | верно | Content-Type: application/json и т.п. |
T19-L8 7.9 c | HTTP and REST API | PATCH is not required to be idempotent per RFC 5789, unlike PUT. | «yes» Пояснение: RFC 5789 defines PATCH as delta-based modification and explicitly says it is not required to be idempotent, whereas PUT is idempotent.
Raw{"answer":"yes","explanation":"RFC 5789 defines PATCH as delta-based modification and explicitly says it is not required to be idempotent, whereas PUT is idempotent."} | верно | RFC 5789 прямо оговаривает: PATCH не гарантированно идемпотентен; PUT идемпотентен. |
T20-L1 4.69 c | Security and OAuth | Checking a password by comparing its hash to the stored hash with a plain == is sufficient. | «no» Пояснение: Use a timing-safe comparison such as PHP's password_verify() instead of a plain == comparison.
Raw{"answer":"no","explanation":"Use a timing-safe comparison such as PHP's password_verify() instead of a plain == comparison."} | верно | Нужна постоянновременная проверка (password_verify) — timing-атаки; соль и алгоритм уже внутри хеша. |
T20-L2 1.31 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 typically generated by the server, associated with the session, and validated server-side for state-changing requests.
Raw{"answer": "yes", "explanation": "CSRF tokens are typically generated by the server, associated with the session, and validated server-side for state-changing requests."} | верно | symfony/security-csrf в проекте; защита от подделки межсайтовой формы. |
T20-L3 1.28 c | Security and OAuth | Which HTTP header enables the CSP (Content Security Policy) policy? | «content-security-policy» Пояснение: The Content-Security-Policy HTTP header defines and enforces the CSP policy.
Raw{"answer":"Content-Security-Policy","explanation":"The Content-Security-Policy HTTP header defines and enforces the CSP policy."} | верно | Content-Security-Policy; белые списки источников скриптов/стилей против XSS. |
T20-L4 2.78 c | Security and OAuth | OAuth 2.0 is an authentication protocol: the access token tells you who the user is. | «no» Пояснение: OAuth 2.0 is an authorization framework, not an authentication protocol; it grants access tokens that authorize access to resources, while OpenID Connect (built on top of OAuth 2.0) handles authentication and identity.
Raw{"answer": "no", "explanation": "OAuth 2.0 is an authorization framework, not an authentication protocol; it grants access tokens that authorize access to resources, while OpenID Connect (built on top of OAuth 2.0) handles authentication and identity."} | верно | OAuth 2.0 — авторизация/делегирование доступа; аутентификацию добавляет OpenID Connect. В проекте knpuniversity/oauth2-client-bundle (yandex/github/google). |
T20-L5 1.4 c | Security and OAuth | XSS is prevented by validating input on the server before writing it to the database. | «no» Пояснение: XSS prevention primarily requires safe output encoding or escaping, not only server-side input validation before storage.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "XSS prevention primarily requires safe output encoding or escaping, not only server-side input validation before storage." ⏎ } | верно | XSS лечится контекстным экранированием НА ВЫВОДЕ (Twig autoescape, CSP); валидация ввода не покрывает все контексты вывода. |
T20-L6 1.18 c | Security and OAuth | In the OAuth 2.0 authorization code flow, which parameter arrives at the redirect_uri and is exchanged for an access token? | «code» Пояснение: In the OAuth 2.0 authorization code flow, the authorization code is returned to the redirect_uri and exchanged at the token endpoint for an access token.
Raw{ ⏎ "answer": "code", ⏎ "explanation": "In the OAuth 2.0 authorization code flow, the authorization code is returned to the redirect_uri and exchanged at the token endpoint for an access token." ⏎ } | верно | Параметр code; обмен на токен POST-ом на /token с client_secret. |
T20-L7 0.87 c | Security and OAuth | A refresh token lives longer than an access token and allows obtaining a new access token without the user logging in again. | «yes» Пояснение: Refresh tokens are intended to have a longer lifetime and can be used to request new access tokens without requiring the user to log in again.
Raw{"answer":"yes","explanation":"Refresh tokens are intended to have a longer lifetime and can be used to request new access tokens without requiring the user to log in again."} | верно | Стандартная схема OAuth/OIDC: короткий access + длинный refresh. |
T20-L8 1.52 c | Security and OAuth | A password salt must be kept secret: without it the hash cannot be verified. | «no» Пояснение: A password salt does not need to be secret and is usually stored with the hash.
Raw{"answer": "no", "explanation": "A password salt does not need to be secret and is usually stored with the hash."} | верно | Соль хранится открыто (password_hash включает её в строку хеша); секретность соли не нужна. |
T18-L1 1.22 c | Testing: PHPUnit | PHPUnit runs test methods of any class — extending TestCase is not required. | «no» Пояснение: PHPUnit discovers test methods in classes that extend PHPUnit\Framework\TestCase.
Raw{"answer": "no", "explanation": "PHPUnit discovers test methods in classes that extend PHPUnit\\Framework\\TestCase."} | верно | Тестом считается метод класса, наследующего TestCase (PHPUnit 10). |
T18-L2 1.11 c | Testing: PHPUnit | In PHPUnit, setUp() runs once before all tests of the class. | «no» Пояснение: In PHPUnit, setUp() runs before each test method, not once for the whole class; setUpClass() runs once per class.
Raw{"answer": "no", "explanation": "In PHPUnit, setUp() runs before each test method, not once for the whole class; setUpClass() runs once per class."} | верно | setUp() — перед КАЖДЫМ тестом; один раз на класс — setUpBeforeClass(). Проверено живым счётчиком на PHPUnit 10.5. |
T18-L3 1.01 c | Testing: PHPUnit | A data provider lets a test run with exactly one set of arguments. | «no» Пояснение: A data provider allows a test to run with multiple sets of arguments, not exactly one.
Raw{"answer": "no", "explanation": "A data provider allows a test to run with multiple sets of arguments, not exactly one."} | верно | Наоборот: наборов может быть сколько угодно — тест выполняется по разу на каждый. Проверено на PHPUnit 10.5 (#[DataProvider]). |
T18-L4 1.22 c | Testing: PHPUnit | Which PHPUnit method declares an expectation that an exception of a given class is thrown? | «expectexception» Пояснение: expectException() is the PHPUnit method used to declare an expectation that an exception of the given class will be thrown during the test execution.
Raw{"answer": "expectException", "explanation": "expectException() is the PHPUnit method used to declare an expectation that an exception of the given class will be thrown during the test execution."} | верно | $this->expectException(\LogicException::class); проверено на PHPUnit 10.5. |
T18-L5 1.74 c | Testing: PHPUnit | In PHPUnit, a stub verifies which methods were called on it, while a mock only returns data. | «no» Пояснение: It is reversed: a mock verifies which methods were called with specific arguments, while a stub simply returns data without verifying interactions.
Raw{"answer": "no", "explanation": "It is reversed: a mock verifies which methods were called with specific arguments, while a stub simply returns data without verifying interactions."} | верно | Наоборот: стаб подставляет данные, мок проверяет взаимодействия (createStub/createMock); docs PHPUnit — Test Doubles. |
T18-L6 4.56 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 supported/recommended way to provide test data, while the legacy @dataProvider annotation is deprecated/removed in favor of attributes.
Raw{"answer": "yes", "explanation": "In PHPUnit 10+, the #[DataProvider] attribute is the supported/recommended way to provide test data, while the legacy @dataProvider annotation is deprecated/removed in favor of attributes."} | верно | Аннотация ещё парсится в PHPUnit 10/11 (AnnotationParser в 10.5.66), удаление — в 12; атрибут — стандарт. |
T18-L7 9.99 c | Testing: PHPUnit | PHPUnit does not allow one test to depend on the result of another. | «no» Пояснение: PHPUnit supports test dependencies using the @depends annotation or Depends attribute.
Raw{"answer": "no", "explanation": "PHPUnit supports test dependencies using the @depends annotation or Depends attribute."} | верно | Зависимости есть: #[Depends] — зависимый тест не запустится, еслиProducer упал. |
T18-L8 6.2 c | Testing: PHPUnit | Which PHPUnit command-line option makes tests run in random order? | «--random-order» Пояснение: The --random-order option randomizes the order in which PHPUnit tests are executed.
Raw{"answer":"--random-order","explanation":"The --random-order option randomizes the order in which PHPUnit tests are executed."} | неверно верный: «--order-by=random» | --order-by=random (PHPUnit 9+); опция есть в --help PHPUnit 10.5 (проектная). |
T01-L9 3.84 c | Syntax and operators | What does this code output?
```php
echo intdiv(7, 2) . intdiv(-7, 2);
``` | «3-3» Пояснение: intdiv(7, 2) is 3 and intdiv(-7, 2) is -3, and concatenating them gives the string 3-3.
Raw{"answer": "3-3", "explanation": "intdiv(7, 2) is 3 and intdiv(-7, 2) is -3, and concatenating them gives the string 3-3."} | верно | intdiv truncates toward zero: intdiv(-7, 2) = -3, not -4. |
T01-L10 2.13 c | Syntax and operators | What does this code output?
```php
echo -3 ** 2;
``` | «-9» Пояснение: In PHP, the `**` operator has higher precedence than the unary minus, so `-3 ** 2` is evaluated as `-(3 ** 2)` which equals `-9`.
Raw{"answer": "-9", "explanation": "In PHP, the `**` operator has higher precedence than the unary minus, so `-3 ** 2` is evaluated as `-(3 ** 2)` which equals `-9`."} | верно | ** is right-associative and binds tighter than unary minus: -(3²). |
T02-L9 2.2 c | Types and comparisons | What does this code output?
```php
echo '1e1' == '10' ? 'true' : 'false';
``` | «true» Пояснение: PHP compares the numeric strings '1e1' and '10' as equal, so the ternary outputs 'true'.
Raw{"answer":"true","explanation":"PHP compares the numeric strings '1e1' and '10' as equal, so the ternary outputs 'true'."} | верно | Both strings are numeric — compared as numbers: 10 == 10. |
T02-L10 6.01 c | Types and comparisons | What does this code output?
```php
switch ('a') {
case 0: echo 'zero'; break;
default: echo 'other';
}
``` | «other» Пояснение: The switch compares 'a' loosely to 0, which is false, so the default case runs.
Raw{"answer": "other", "explanation": "The switch compares 'a' loosely to 0, which is false, so the default case runs."} | верно | PHP 8: 'a' == 0 → false (used to be true) — default fires. |
T03-L9 63.87 c | Strings | What does this code output?
```php
echo strtr('abc', ['a' => '1', 'ab' => '2']);
``` | «2c» Пояснение: strtr() with an array replaces the longest matching substring first, so "ab" becomes "2" and the final "c" remains.
Raw{"answer": "2c", "explanation": "strtr() with an array replaces the longest matching substring first, so \"ab\" becomes \"2\" and the final \"c\" remains."} | верно | strtr with an array prefers the longest matching key. |
T03-L10 8.09 c | Strings | What does this code output?
```php
echo '[' . substr('hello', -10) . ']';
``` | «[hello]» Пояснение: substr() with a negative start that goes before the beginning of the string starts at the beginning, so it returns 'hello'.
Raw{"answer": "[hello]", "explanation": "substr() with a negative start that goes before the beginning of the string starts at the beginning, so it returns 'hello'."} | верно | A negative start beyond the string is clamped to the beginning. |
T04-L9 2.03 c | Arrays | What does this code output?
```php
$a = ['k' => 1, 'n' => 2];
$b = ['k' => 9, 'm' => 3];
echo implode(',', array_keys($a + $b));
``` | «k,n,m» Пояснение: The + operator keeps left-array values for duplicate keys, so the resulting keys are k, n, and m.
Raw{ ⏎ "answer": "k,n,m", ⏎ "explanation": "The + operator keeps left-array values for duplicate keys, so the resulting keys are k, n, and m." ⏎ } | верно | The + operator: on duplicate string keys the left array wins. |
T04-L10 2.37 c | Arrays | What does this code output?
```php
$a = [[1, 'x', 2], [2, 'y', 1], [3, 'z', 2]];
usort($a, fn($p, $q) => $p[2] <=> $q[2]);
echo implode('', array_column($a, 1));
``` | «yxz» Пояснение: The arrays are sorted by the third element, yielding the letters y, x, z when joined.
Raw{"answer":"yxz","explanation":"The arrays are sorted by the third element, yielding the letters y, x, z when joined."} | верно | Sorts are stable since 8.0: x and z keep their order on a tie. |
T05-L10 14.4 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» Пояснение: Array spread with string keys passes named arguments, so $a=5 and $b=1.
Raw{ ⏎ "answer": 4, ⏎ "explanation": "Array spread with string keys passes named arguments, so $a=5 and $b=1." ⏎ } | верно | String keys of a spread array become named arguments. |
T05-L9 39.22 c | Functions and closures | What does this code output?
```php
class P
{
private int $v = 3;
public function g(): int { return $this->v; }
}
$p = new P;
$f = $p->g(...);
$p = null;
echo $f();
``` | «3» Пояснение: The first-class callable keeps a reference to the P object, so $f() still returns $this->v after $p is set to null.
Raw{"answer": 3, "explanation": "The first-class callable keeps a reference to the P object, so $f() still returns $this->v after $p is set to null."} | верно | First-class callable syntax binds $this at creation time. |
T06-L9 1.2 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, which is B.
Raw{ ⏎ "answer": "B", ⏎ "explanation": "static::class uses late static binding, so it returns the class from which the method was actually called, which is B." ⏎ } | верно | Late static binding: static::class is the receiver's class. |
T06-L10 46.72 c | OOP: classes and inheritance | What does this code output on PHP 8.5?
```php
class C
{
public int $x = 0 {
set { $this->x = $value * 2; }
}
}
$c = new C;
$c->x = 5;
echo $c->x;
``` | «10» Пояснение: The set accessor stores $value * 2 in the underlying property, and reading it without a getter returns 10.
Raw{"answer":10,"explanation":"The set accessor stores $value * 2 in the underlying property, and reading it without a getter returns 10."} | верно | Inside the set hook, $this->x writes the backing store (no recursion): 5*2. |
T07-L9 1.55 c | Interfaces, traits, enum | What does this code output?
```php
trait TA
{
public function f(): string { return 'A'; }
}
trait TB
{
public function f(): string { return 'B'; }
}
class TC
{
use TA, TB { TB::f insteadof TA; TA::f as g; }
}
echo (new TC)->f() . (new TC)->g();
``` | «ba» Пояснение: TB::f insteadof TA makes f return 'B', and TA::f as g aliases TA's f to g, returning 'A'.
Raw{ ⏎ "answer": "BA", ⏎ "explanation": "TB::f insteadof TA makes f return 'B', and TA::f as g aliases TA's f to g, returning 'A'." ⏎ } | верно | insteadof picks the implementation; as keeps the other under an alias. |
T07-L10 280.43 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» парсинг: нет | A trait's static property is copied into each consuming class. |
T08-L10 5.62 c | Exceptions and errors | What does this code output?
```php
function f(): int
{
try { return 1; } finally { return 2; }
}
echo f();
``` | «2» Пояснение: The return statement in the finally block overrides the return value from the try block.
Raw{"answer": 2, "explanation": "The return statement in the finally block overrides the return value from the try block."} | верно | A return in finally overrides the return from try. |
T08-L9 1.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 RuntimeException in the inner try is superseded by the LogicException thrown in the inner finally block, which propagates to the outer catch(LogicException) handler that prints its message "second".
Raw{"answer": "second", "explanation": "The RuntimeException in the inner try is superseded by the LogicException thrown in the inner finally block, which propagates to the outer catch(LogicException) handler that prints its message \"second\"."} | верно | An exception from finally replaces the in-flight one — the last thrown is caught. |
T09-L9 35.59 c | Namespaces and autoloading | What does this code output?
```php
namespace N;
use App\Foo as Baz;
echo Baz::class . '|' . \Baz::class;
``` | «app\foo|baz» Пояснение: Baz::class resolves to the imported class App\Foo, while \Baz::class refers to the global namespace name Baz.
Raw{ ⏎ "answer": "App\\Foo|Baz", ⏎ "explanation": "Baz::class resolves to the imported class App\\Foo, while \\Baz::class refers to the global namespace name Baz." ⏎ } | верно | The use alias applies to unqualified names; a leading \ escapes to the global scope. |
T09-L10 264.07 c | Namespaces and autoloading | What does this code output?
```php
namespace Ns;
class Foo {}
$c = 'Foo';
echo (class_exists($c) ? 'yes' : 'no')
. (class_exists(__NAMESPACE__ . '\\' . $c) ? 'yes' : 'no');
``` | «yesyes» Пояснение: class_exists() resolves the unqualified Foo in the current Ns namespace, and __NAMESPACE__.\'Foo' is also the existing Ns\Foo class.
Raw{"answer":"yesyes","explanation":"class_exists() resolves the unqualified Foo in the current Ns namespace, and __NAMESPACE__.\\'Foo' is also the existing Ns\\Foo class."} | неверно верный: «noyes» | Dynamic names are not resolved against the namespace — 'Foo' is the global class. |
T10-L9 9.96 c | References and scope | What does this code output?
```php
$a = [1, 2, 3];
foreach ($a as &$v) {}
$v = 99;
echo implode(',', $a);
``` | «1,2,99» Пояснение: The foreach loop makes $v a reference to the last array element, so assigning 99 to $v changes $a[2].
Raw{ ⏎ "answer": "1,2,99", ⏎ "explanation": "The foreach loop makes $v a reference to the last array element, so assigning 99 to $v changes $a[2]." ⏎ } | верно | After a by-ref foreach, $v remains a reference to the last element. |
T10-L10 23.31 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 for the inherited method, so the calls increment the same counter to 1, 2, and 3.
Raw{ ⏎ "answer": 3, ⏎ "explanation": "The static variable is shared for the inherited method, so the calls increment the same counter to 1, 2, and 3." ⏎ } | верно | A method's static variable belongs to the parent's method — subclasses share it. |
T11-L9 3.2 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) assigns 10 to $x, then the generator returns $x + 1, which is 11.
Raw{ ⏎ "answer": 11, ⏎ "explanation": "The first send(10) assigns 10 to $x, then the generator returns $x + 1, which is 11." ⏎ } | верно | send() resumes the generator: $x = 10, return 10+1. |
T11-L10 3.43 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 passes along the yielded values and then assigns inner()'s return value 'ok' to $r, which is yielded next.
Raw{ ⏎ "answer": "1,2,ok", ⏎ "explanation": "yield from passes along the yielded values and then assigns inner()'s return value 'ok' to $r, which is yielded next." ⏎ } | неверно верный: «ok,2» | yield from does not advance the outer auto-key: yield $r gets key 0 and overwrites the 1 — 'ok' comes out first. |
T12-L9 2.06 c | Configuration and security | What does this code output?
```php
$hash = password_hash('x', PASSWORD_BCRYPT, ['cost' => 4]);
echo password_needs_rehash($hash, PASSWORD_BCRYPT, ['cost' => 4]) ? 'yes' : 'no';
echo password_needs_rehash($hash, PASSWORD_BCRYPT, ['cost' => 5]) ? 'yes' : 'no';
``` | «noyes» Пояснение: The first check uses the same algorithm and cost so it returns false, while the second check requests a higher cost so it returns true.
Raw{ ⏎ "answer": "noyes", ⏎ "explanation": "The first check uses the same algorithm and cost so it returns false, while the second check requests a higher cost so it returns true." ⏎ } | верно | password_needs_rehash compares the hash's options with the target: cost 4 = 4 → 'no', cost 5 ≠ 4 → 'yes'. |
T12-L10 269.48 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» Пояснение: PHP 8.5 no longer includes the deprecated E_STRICT bit (2048) in E_ALL, so the bitwise AND is 0.
Raw{"answer":"strict-out","explanation":"PHP 8.5 no longer includes the deprecated E_STRICT bit (2048) in E_ALL, so the bitwise AND is 0."} | верно | Since PHP 8.4, E_STRICT is out of E_ALL: the 2048 bit is unset → 'strict-out' (2048 is the historical E_STRICT bit). |
T13-L9 66.78 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 HTTP_X_TOKEN header into the X-Token header name, so the comparison succeeds.
Raw{"answer":"mapped","explanation":"Symfony normalizes the HTTP_X_TOKEN header into the X-Token header name, so the comparison succeeds."} | верно | The literal comparison requires knowing the mapping: HttpFoundation turns HTTP_X_TOKEN into the X-Token header (case-insensitive); without it the answer is 'missing'. |
T13-L10 4.04 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 are dispatched in descending priority order, so priority 10, 5, and then 0 run.
Raw{ ⏎ "answer": "BCA", ⏎ "explanation": "Listeners are dispatched in descending priority order, so priority 10, 5, and then 0 run." ⏎ } | верно | Listeners run by descending priority: 10 (B), 5 (C), 0 (A). |
T14-L10 2.88 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 instance for repeated find() calls of an existing entity.
Raw{"answer":"same","explanation":"Doctrine’s EntityManager identity map returns the same instance for repeated find() calls of an existing entity."} | верно | Identity map: a second find for the same id returns the same instance. |
T14-L9 33.17 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 persist action, so no row is inserted into users.
Raw{"answer": 0, "explanation": "Removing the entity before flush cancels the pending persist action, so no row is inserted into users."} | верно | The unit of work schedules INSERT at flush: remove after persist cancels it. |
T15-L10 1.46 c | PostgreSQL | What does this SQL query return (PostgreSQL 17)?
```sql
CREATE TEMP TABLE t (x int);
INSERT INTO t VALUES (1), (NULL);
SELECT count(x) FROM t;
``` | «1» Пояснение: COUNT(x) counts only non-NULL values in the column, so the single non-NULL value 1 is counted.
Raw{"answer": 1, "explanation": "COUNT(x) counts only non-NULL values in the column, so the single non-NULL value 1 is counted."} | верно | count(column) skips NULLs; count(*) would return 2. |
T15-L9 2.03 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 computes cumulative sums of x by id, and string_agg joins them as 10,30,60.
Raw{ ⏎ "answer": "10,30,60", ⏎ "explanation": "The window sum computes cumulative sums of x by id, and string_agg joins them as 10,30,60." ⏎ } | верно | With ORDER BY the default window frame is running (start to current row). |
T16-L9 36.6 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 middlewares run in the given order, each echoing its tag before calling the next middleware.
Raw{ ⏎ "answer": "M1M2", ⏎ "explanation": "The middlewares run in the given order, each echoing its tag before calling the next middleware." ⏎ } | верно | The first-added middleware runs first (outermost). |
T16-L10 6.12 c | Symfony: Messenger | What does this code output?
```php
use Symfony\Component\Messenger\MessageBus;
use Symfony\Component\Messenger\Middleware\HandleMessageMiddleware;
use Symfony\Component\Messenger\Handler\HandlersLocator;
use Symfony\Component\Messenger\Handler\HandlerDescriptor;
use Symfony\Component\Messenger\Envelope;
class Ping {}
$n = 0;
$d1 = new HandlerDescriptor(function (Ping $m) use (&$n) { $n += 1; }, ['alias' => 'h1']);
$d2 = new HandlerDescriptor(function (Ping $m) use (&$n) { $n += 10; }, ['alias' => 'h2']);
$bus = new MessageBus([
new HandleMessageMiddleware(new HandlersLocator([Ping::class => [$d1, $d2]])),
]);
$bus->dispatch(new Envelope(new Ping()));
echo $n;
``` | «11» Пояснение: HandleMessageMiddleware iterates through all handlers returned by the HandlersLocator for the Ping class, calling both the first closure ($n += 1) and the second closure ($n += 10), resulting in $n = 11.
Raw{"answer": 11, "explanation": "HandleMessageMiddleware iterates through all handlers returned by the HandlersLocator for the Ping class, calling both the first closure ($n += 1) and the second closure ($n += 10), resulting in $n = 11."} | верно | All registered handlers of the message run: 1 + 10 = 11. |
T17-L9 1.33 c | PostgreSQL: transactions and indexes | What does this SQL query return (PostgreSQL 17)?
```sql
CREATE TEMP TABLE t (a int);
CREATE UNIQUE INDEX ON t (a);
INSERT INTO t VALUES (1) ON CONFLICT DO NOTHING;
INSERT INTO t VALUES (1) ON CONFLICT DO NOTHING;
SELECT count(*) FROM t;
``` | «1» Пояснение: The first INSERT adds the row, and the second is ignored due to the unique constraint with ON CONFLICT DO NOTHING.
Raw{"answer": 1, "explanation": "The first INSERT adds the row, and the second is ignored due to the unique constraint with ON CONFLICT DO NOTHING."} | верно | ON CONFLICT DO NOTHING skips the duplicate: one insert. |
T17-L10 1.55 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 checked at transaction commit, so both duplicate rows are visible in the SELECT.
Raw{"answer": 2, "explanation": "The deferrable unique constraint is checked at transaction commit, so both duplicate rows are visible in the SELECT."} | верно | DEFERRED postpones the uniqueness check to COMMIT — count sees 2 rows. |
T18-L9 24.17 c | Testing: PHPUnit | How many tests will this command run?
```php
use PHPUnit\Framework\TestCase;
use PHPUnit\Framework\Attributes\DataProvider;
final class CalcTest extends TestCase
{
public static function prov(): array
{
return [[1], [2], [3]];
}
#[DataProvider('prov')]
public function test_sum(int $x): void
{
$this->assertTrue($x > 0);
}
#[DataProvider('prov')]
public function test_sum_abs(int $x): void
{
$this->assertTrue($x > 0);
}
public function test_other(): void
{
$this->assertTrue(true);
}
}
```
Command: `phpunit CalcTest.php --filter test_sum` (PHPUnit 10.5) | «6» Пояснение: The unanchored filter matches both test_sum and test_sum_abs, and each method is expanded into three data-provider test cases.
Raw{ ⏎ "answer": 6, ⏎ "explanation": "The unanchored filter matches both test_sum and test_sum_abs, and each method is expanded into three data-provider test cases." ⏎ } | верно | --filter is a substring match: test_sum also matches test_sum_abs (3+3 datasets). |
T18-L10 4.18 c | Testing: PHPUnit | How many tests will this command run, and how many of them will fail? Answer with two comma-separated numbers (ran, failed).
```php
use PHPUnit\Framework\TestCase;
use PHPUnit\Framework\Attributes\DataProvider;
final class Calc2Test extends TestCase
{
public function prov(): array
{
return [[1], [-1]];
}
#[DataProvider('prov')]
public function test_x(int $x): void
{
$this->assertTrue($x > 0);
}
}
```
Command: `phpunit Calc2Test.php` (PHPUnit 10.5) | «2,1» Пояснение: The data provider yields two datasets, and the assertion passes for 1 but fails for -1.
Raw{ ⏎ "answer": "2,1", ⏎ "explanation": "The data provider yields two datasets, and the assertion passes for 1 but fails 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 0.84 c | HTTP and REST API | Which HTTP method does this command send?
```bash
curl -s -d 'a=1' http://demo.local/api
``` | «post» Пояснение: The curl -d option sends data using POST by default.
Raw{"answer":"POST","explanation":"The curl -d option sends data using POST by default."} | верно | -d/-F switches curl to POST by default. |
T19-L10 0.88 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 option forces curl to send a GET request with the data appended to the query string.
Raw{"answer": "GET", "explanation": "The -G option forces curl to send a GET request with the data appended to the query string."} | верно | -G turns -d data into the query string; the method stays GET. |
T20-L9 2.78 c | Security and OAuth | A client hits the token endpoint (RFC 6749) with a non-existent client_id. What value of the error field does the endpoint return? | «invalid_client» Пояснение: Per RFC 6749 Section 5.3, if the client_id is not recognized by the authorization server, the token endpoint returns the error 'invalid_client'.
Raw{"answer": "invalid_client", "explanation": "Per RFC 6749 Section 5.3, if the client_id is not recognized by the authorization server, the token endpoint returns the error 'invalid_client'."} | верно | Unknown client → invalid_client (RFC 6749 §5.2). |
T20-L10 1.67 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? | «the query string» Пояснение: In the OAuth 2.0 implicit grant (response_type=token), the access_token is returned as a query parameter in the redirect_uri.
Raw{"answer": "the query string", "explanation": "In the OAuth 2.0 implicit grant (response_type=token), the access_token is returned as a query parameter in the redirect_uri."} | неверно верный: «fragment» | The implicit flow passes the token in the URL fragment (#) — it never reaches the server. |
T21-L9 7.54 c | Twig | What does this Twig template output?
```twig
{{ false|default(2) * 3 }}
``` | «6» Пояснение: In Twig, `false|default(2)` returns `2`, and `2 * 3` is `6`.
Raw{"answer": 6, "explanation": "In Twig, `false|default(2)` returns `2`, and `2 * 3` is `6`."} | верно | default replaces exactly false/null/''/[] — false becomes 2, 2*3 = 6; the naive 'default is for undefined only' yields 0. |
T21-L10 280.31 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 42.93 c | Symfony: Security and forms | What does this code output?
```php
use Symfony\Component\Validator\Validation;
use Symfony\Component\Validator\Constraints as Assert;
$v = Validation::createValidator();
echo count($v->validate([''], [new Assert\NotBlank()]));
``` | «1» Пояснение: The validator applies NotBlank to the single empty string in the array, producing one constraint violation.
Raw{"answer": 1, "explanation": "The validator applies NotBlank to the single empty string in the array, producing one constraint violation."} | неверно верный: «0» | NotBlank treats null, '', [] as blank — the array [''] is not blank. |
T22-L10 5.51 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» Пояснение: A TextType form with no data and no constraints passes validation, so isValid() returns true.
Raw```json ⏎ {"answer": "valid", "explanation": "A TextType form with no data and no constraints passes validation, so isValid() returns true."} ⏎ ``` | неверно верный: «symfony\component\form\exception\logicexception» | isValid() on a non-submitted form throws LogicException, it does not return false. |
T23-L9 5.46 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 DI compiles the container and caches the service instance, so both calls to $c->get('a') return the same object.
Raw{"answer": "same", "explanation": "Symfony DI compiles the container and caches the service instance, so both calls to $c->get('a') return the same object."} | верно | Container services are shared: two get() calls yield one instance. |
T23-L10 219.18 c | Symfony: configuration and services | What does this code output?
```php
use Symfony\Component\DependencyInjection\ContainerBuilder;
$c = new ContainerBuilder();
$c->setParameter('name', 'Bob');
$c->setParameter('greeting', 'hi %name%');
$c->setParameter('message', '%greeting%!');
$c->compile();
echo $c->getParameter('message');
``` | «hi %name%» Пояснение: The `%greeting!%` placeholder inserts the raw value of `greeting`, leaving its own `%name%` placeholder unresolved.
Raw{"answer": "hi %name%", "explanation": "The `%greeting!%` placeholder inserts the raw value of `greeting`, leaving its own `%name%` placeholder unresolved."} | неверно верный: «hi bob!» | compile() resolves %-references transitively: %greeting% → 'hi %name%' → 'hi Bob!', the answer assembles over two hops. |
T24-L9 10.78 c | Bootstrap | What is the max-width of .container in Bootstrap 5.3 at a 992px viewport? | «720» Пояснение: In Bootstrap 5.3, the .container max-width is 720px at viewports of 992px and above.
Raw{ ⏎ "answer": 720, ⏎ "explanation": "In Bootstrap 5.3, the .container max-width is 720px at viewports of 992px and above." ⏎ } | неверно верный: «960» | 5.x container widths: 540/720/960/1140/1320 (sm–xxl); 992 → 960px. |
T24-L10 24.72 c | Bootstrap | Which utility sets the text color in Bootstrap 5.3 for `<p class="text-danger text-primary">…</p>`? Answer with the winning class name. | «text-danger» Пояснение: In Bootstrap 5.3's compiled CSS, .text-danger is declared after .text-primary, so it wins for the color property.
Raw{"answer":"text-danger","explanation":"In Bootstrap 5.3's compiled CSS, .text-danger is declared after .text-primary, so it wins for the color property."} | верно | Specificity ties — the later rule wins: text-danger is declared after text-primary. |
T25-L9 8.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 OrderService
{
public function __construct(
private PlaceOrder $handler,
private Db $db,
) {}
}
``` | «2» Пояснение: The Domain class depends on one Application class and one Infrastructure class, so both dependencies violate the rule that Domain may only depend on Domain.
Raw{ ⏎ "answer": 2, ⏎ "explanation": "The Domain class depends on one Application class and one Infrastructure class, so both dependencies violate the rule that Domain may only depend on Domain." ⏎ } | верно | Domain may depend only on Domain: PlaceOrder (Application) + Db (Infrastructure) = 2. |
T25-L10 11.98 c | Clean architecture | Layers: Domain, Application, Infrastructure. Deptrac rules: Application → Domain; Infrastructure → Domain, Application; Domain → Domain only.
How many violations will deptrac report for this class?
```php
namespace App\Domain;
use App\Application\PlaceOrder;
use App\Infrastructure\Db;
class 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, so there are three dependency-rule violations.
Raw{ ⏎ "answer": 3, ⏎ "explanation": "The Domain class depends on one Application class and two Infrastructure classes, so there are three dependency-rule violations." ⏎ } | верно | The inline FQCN \App\Infrastructure\Logger counts too: Application + Db + Logger = 3. |
T26-L10 1.4 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,5» Пояснение: Money's readonly $amount is immutable, and add creates a new Money instance, so $a remains 10 and $c is 5.
Raw{ ⏎ "answer": "10,5", ⏎ "explanation": "Money's readonly $amount is immutable, and add creates a new Money instance, so $a remains 10 and $c is 5." ⏎ } | неверно верный: «10,15» | The VO is immutable: add() returns a new instance; the original is unchanged. |
T26-L9 1.27 c | DDD | What does this code output?
```php
final class Order
{
private array $items = [];
public function add(string $sku): void
{
$this->items[$sku] = true;
}
public function count(): int
{
return count($this->items);
}
public function remove(string $sku): void
{
if (count($this->items) === 1) {
throw new DomainException('last item');
}
unset($this->items[$sku]);
}
}
$o = new Order;
$o->add('a');
try {
$o->remove('a');
} catch (DomainException) {
}
echo $o->count();
``` | «1» Пояснение: remove('a') throws because there is only one item, so the item is not removed and the count remains 1.
Raw{"answer":1,"explanation":"remove('a') throws because there is only one item, so the item is not removed and the count remains 1."} | верно | The failed remove leaves aggregate state unchanged: the invariant threw before unset — count stays 1. |
VC-L9 1.06 c | PHP 8.4–8.5 | What does this code output on PHP 8.5?
```php
class C
{
public function hi(): string { return 'hi'; }
}
echo new C()->hi();
``` | «hi» Пояснение: The code instantiates class C and calls hi(), which returns the string 'hi', echoed by echo.
Raw{"answer": "hi", "explanation": "The code instantiates class C and calls hi(), which returns the string 'hi', echoed by echo."} | верно | Since 8.4, new in a method chain works without wrapping parentheses. |
VC-L10 162.88 c | PHP 8.4–8.5 | What does this code output on PHP 8.5?
```php
class Heavy
{
public int $v = 0;
}
$r = new ReflectionClass(Heavy::class);
$o = $r->newLazyGhost(function (Heavy $obj) {
$obj->v = 21;
});
echo $r->isUninitializedLazyObject($o) ? 'yes' : 'no';
$o->v;
echo $r->isUninitializedLazyObject($o) ? 'yes' : 'no';
``` | «yesno» Пояснение: The lazy ghost is still uninitialized before the property access, but accessing $o->v runs the initializer and initializes the object, so the second check is false.
Raw{"answer": "yesno", "explanation": "The lazy ghost is still uninitialized before the property access, but accessing $o->v runs the initializer and initializes the object, so the second check is false."} | верно | newLazyGhost (8.4): the object stays lazy until first access — reading a property initializes it and clears the flag. |
T28-L9 16.94 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» Пояснение: Symfony removed the Guard authenticator classes in the 6.0 upgrade, so they do not exist in 8.1.
Raw{"answer":"no","explanation":"Symfony removed the Guard authenticator classes in the 6.0 upgrade, so they do not exist in 8.1."} | верно | Guard authentication was removed in Symfony 7.0 — the class is gone in 8.1. |
T28-L10 50.1 c | Symfony: versions | The project was upgraded from Symfony 6.4 to 8.1. What does this code output on 8.1?
```php
echo class_exists(\Symfony\Component\Routing\Loader\AnnotationClassLoader::class)
? 'yes' : 'no';
echo class_exists(\Symfony\Component\Routing\Loader\AttributeClassLoader::class)
? 'yes' : 'no';
``` | «noyes» Пояснение: In Symfony 8.1, AnnotationClassLoader was removed, while AttributeClassLoader still exists.
Raw{"answer":"noyes","explanation":"In Symfony 8.1, AnnotationClassLoader was removed, while AttributeClassLoader still exists."} | верно | Annotation loaders were removed in 7.0; only attribute loaders remain (Annotation→Attribute). |