Пример запроса (первая клетка). System одинаковый во всех запросах прогона, user — свой вопрос для каждой клетки:
| Клетка | Тема | Утверждение | Ответ |
Результат | Обоснование |
T01-L1 3.61 c | Syntax and operators | Double-quoted and single-quoted strings are processed identically; the difference is only in speed. | «no» Пояснение: They differ because double-quoted strings allow variable interpolation and more escape sequences, while single-quoted strings are more literal.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "They differ because double-quoted strings allow variable interpolation and more escape sequences, while single-quoted strings are more literal." ⏎ } | верно | В двойных кавычках работают интерполяция переменных и escape-последовательности, в одинарных — нет. |
T01-L2 1.56 c | Syntax and operators | The ?? operator follows isset semantics and raises no warnings for undefined variables. | «yes» Пояснение: The null coalescing operator suppresses undefined-variable notices and returns the first non-null or defined operand.
Raw{"answer": "yes", "explanation": "The null coalescing operator suppresses undefined-variable notices and returns the first non-null or defined operand."} | верно | ?? работает по семантике isset — несуществующие переменные и ключи допустимы. |
T01-L3 0.93 c | Syntax and operators | What will this print: echo 'a', 'b'; | «ab» Пояснение: The comma separates echo arguments, and they are concatenated and printed.
Raw{ ⏎ "answer": "ab", ⏎ "explanation": "The comma separates echo arguments, and they are concatenated and printed." ⏎ } | верно | echo принимает список аргументов: ab. |
T01-L4 5.28 c | Syntax and operators | print returns the value 1 and can be used inside an expression. | «yes» Пояснение: In PHP, the print language construct outputs a value and returns 1, so it can be used inside an expression.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "In PHP, the print language construct outputs a value and returns 1, so it can be used inside an expression." ⏎ } | верно | print — выражение со значением 1, в отличие от echo, который значения не возвращает. |
T01-L5 1.59 c | Syntax and operators | The ?: (elvis) operator returns its left operand when it is falsy. | «no» Пояснение: The PHP ?: operator returns the left operand when it is truthy, and the right operand when it is falsy.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "The PHP ?: operator returns the left operand when it is truthy, and the right operand when it is falsy." ⏎ } | верно | Наоборот: $a ?: $b возвращает $a, если он истинный, иначе $b. |
T01-L6 1.62 c | Syntax and operators | In PHP 8, the concatenation operator (.) has lower precedence than addition and subtraction. | «yes» Пояснение: In PHP, the concatenation operator (.) has lower precedence than the addition and subtraction operators, so `.` binds more loosely.
Raw{"answer": "yes", "explanation": "In PHP, the concatenation operator (.) has lower precedence than the addition and subtraction operators, so `.` binds more loosely."} | верно | С PHP 8 (RFC concat precedence) '.' имеет приоритет ниже арифметики: 'сумма: ' . 2 + 3 → 'сумма: 5' (в PHP 7 было иначе). |
T01-L7 1.33 c | Syntax and operators | The expression 2 ** 3 ** 2 in PHP evaluates as (2 ** 3) ** 2, that is, 64. | «no» Пояснение: PHP's ** operator is right-associative, so 2 ** 3 ** 2 evaluates as 2 ** (3 ** 2), not (2 ** 3) ** 2.
Raw{"answer": "no", "explanation": "PHP's ** operator is right-associative, so 2 ** 3 ** 2 evaluates as 2 ** (3 ** 2), not (2 ** 3) ** 2."} | верно | ** право-ассоциативен: 2 ** (3 ** 2) = 2 ** 9 = 512. |
T01-L8 280.25 c | Syntax and operators | What string will this print: echo 'sum: ' . 2 + 3; (PHP 8)? | «— (нет ответа)» | не разобрано верный: «sum: 5» парсинг: нет | Парная к verify-клетке про приоритет: 'сумма: 5'. |
T02-L1 2.09 c | Types and comparisons | With strict comparison (===), arrays are considered equal regardless of element order. | «no» Пояснение: In PHP, strict array comparison (===) requires the same key/value pairs in the same order, not just regardless of order.
Raw{"answer": "no", "explanation": "In PHP, strict array comparison (===) requires the same key/value pairs in the same order, not just regardless of order."} | верно | === для массивов требует совпадения и значений, и их порядка. |
T02-L2 1.3 c | Types and comparisons | The comparison 0 == false returns false because it is a strict comparison. | «no» Пояснение: The == operator performs loose comparison, and 0 == false evaluates to true because false is coerced to 0.
Raw{"answer": "no", "explanation": "The == operator performs loose comparison, and 0 == false evaluates to true because false is coerced to 0."} | верно | Наоборот: == — нестрогое сравнение и возвращает true; строгое — это === (0 === false → false). |
T02-L3 3.87 c | Types and comparisons | In PHP 8, the expression "abc" == 0 returns true. | «yes» Пояснение: In PHP 8, a non-numeric string is converted to 0 when loosely compared to an integer, so "abc" == 0 is true.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "In PHP 8, a non-numeric string is converted to 0 when loosely compared to an integer, so \"abc\" == 0 is true." ⏎ } | неверно верный: «no» | С PHP 8 нечисловая строка сравнивается как строка: "abc" == "0" → false (в PHP 7 было true). |
T02-L4 3.44 c | Types and comparisons | Under loose comparison, null equals 0, the empty string, and false at the same time. | «yes» Пояснение: In PHP loose comparison with ==, null is equivalent to 0, the empty string, and false.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "In PHP loose comparison with ==, null is equivalent to 0, the empty string, and false." ⏎ } | верно | null == 0, null == "" и null == false — все true. |
T02-L5 8.94 c | Types and comparisons | What does the expression (int) '42abc' return? | «42» Пояснение: PHP casts the string to an integer by taking the leading numeric portion and stops at the first non-numeric character.
Raw{ ⏎ "answer": 42, ⏎ "explanation": "PHP casts the string to an integer by taking the leading numeric portion and stops at the first non-numeric character." ⏎ } | верно | Ведущая числовая часть: 42, без ошибок и warning. |
T02-L6 1.17 c | Types and comparisons | What does the expression '5' + 5 return? | «10» Пояснение: In PHP, the string '5' is cast to a number before addition, so '5' + 5 evaluates to 10.
Raw{"answer": 10, "explanation": "In PHP, the string '5' is cast to a number before addition, so '5' + 5 evaluates to 10."} | верно | Числовая строка приводится: int 10. |
T02-L7 0.76 c | Types and comparisons | When cast to string, false becomes "0". | «yes» Пояснение: In PHP, casting false to a string produces the empty string "0".
Raw{"answer":"yes","explanation":"In PHP, casting false to a string produces the empty string \"0\"."} | неверно верный: «no» | false → "", true → "1". |
T02-L8 1.77 c | Types and comparisons | The comparison 0.1 + 0.2 === 0.3 returns false. | «yes» Пояснение: In PHP, floating-point imprecision makes 0.1 + 0.2 not strictly equal to 0.3.
Raw{"answer":"yes","explanation":"In PHP, floating-point imprecision makes 0.1 + 0.2 not strictly equal to 0.3."} | верно | Двоичная погрешность float: 0.1 + 0.2 = 0.30000000000000004. |
T03-L1 1.62 c | Strings | strrev() correctly reverses a UTF-8 string. | «no» Пояснение: strrev() reverses bytes rather than UTF-8 characters, so it can corrupt multibyte UTF-8 characters.
Raw{"answer":"no","explanation":"strrev() reverses bytes rather than UTF-8 characters, so it can corrupt multibyte UTF-8 characters."} | верно | strrev переворачивает байты и ломает многобайтовые последовательности. |
T03-L2 1.11 c | Strings | str_contains('Hello world', 'world') returns true. | «yes» Пояснение: str_contains() checks whether the second string appears in the first, and 'world' is present in 'Hello world'.
Raw{"answer": "yes", "explanation": "str_contains() checks whether the second string appears in the first, and 'world' is present in 'Hello world'."} | верно | str_contains с PHP 8.0 проверяет вхождение подстроки. |
T03-L3 1.09 c | Strings | str_pad() can pad a string on the right side only. | «no» Пояснение: str_pad() can pad on the right, left, or both sides.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "str_pad() can pad on the right, left, or both sides." ⏎ } | верно | STR_PAD_LEFT / STR_PAD_BOTH меняют сторону дополнения. |
T03-L4 1.09 c | Strings | By default trim() strips only spaces, leaving tabs and newlines intact. | «no» Пояснение: By default, PHP's trim() also removes tabs and newlines, not only spaces.
Raw{"answer": "no", "explanation": "By default, PHP's trim() also removes tabs and newlines, not only spaces."} | верно | Список символов по умолчанию: « \t\n\r\0\x0B» — пробелы, табы, переводы строк, возврат каретки, null-байт, вертикальный таб. Проверено php -r. |
T03-L5 1.36 c | Strings | How many BYTES does strlen('héllo') return for a UTF-8 string? | «6» Пояснение: In UTF-8, the character 'é' is encoded as 2 bytes, so 'héllo' has 6 bytes total.
Raw{"answer": 6, "explanation": "In UTF-8, the character 'é' is encoded as 2 bytes, so 'héllo' has 6 bytes total."} | верно | 6 букв по 2 байта: 12. |
T03-L6 1.33 c | Strings | What does substr('abcdef', -3) return? | «def» Пояснение: A negative start offset in PHP substr() counts from the end of the string, so -3 returns the last three characters.
Raw{"answer": "def", "explanation": "A negative start offset in PHP substr() counts from the end of the string, so -3 returns the last three characters."} | верно | Отрицательное смещение — с конца: def. |
T03-L7 1.67 c | Strings | ucfirst() modifies the string passed to it in place. | «no» Пояснение: In PHP, ucfirst() returns a new string with the first character uppercased and does not modify the original string in place.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "In PHP, ucfirst() returns a new string with the first character uppercased and does not modify the original string in place." ⏎ } | верно | Строки неизменяемы; ucfirst возвращает новую строку. |
T03-L8 0.98 c | Strings | Variable interpolation works in heredoc but not in nowdoc. | «yes» Пояснение: Heredoc interpolates variables, while nowdoc treats its contents as a literal string without variable interpolation.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Heredoc interpolates variables, while nowdoc treats its contents as a literal string without variable interpolation." ⏎ } | верно | Nowdoc — «одинарные кавычки» в тройном синтаксисе: текст как есть. |
T04-L1 1.1 c | Arrays | The sort() function preserves the key-to-value association of the array. | «no» Пояснение: sort() re-indexes the array with numeric keys 0, 1, 2...; to preserve key-to-value association you must use ksort() or asort().
Raw{"answer":"no","explanation":"sort() re-indexes the array with numeric keys 0, 1, 2...; to preserve key-to-value association you must use ksort() or asort()."} | верно | sort перенумеровывает ключи; связь сохраняет asort. |
T04-L2 1.69 c | Arrays | The string key '5' in an array is stored as the integer 5. | «yes» Пояснение: In PHP, numeric string array keys are automatically converted to integer keys.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "In PHP, numeric string array keys are automatically converted to integer keys." ⏎ } | верно | Каноничные десятичные строковые ключи приводятся к int. |
T04-L3 0.76 c | Arrays | The in_array() function uses strict comparison (===) by default. | «no» Пояснение: in_array() uses loose comparison by default; strict comparison must be enabled with the third parameter set to true.
Raw{"answer": "no", "explanation": "in_array() uses loose comparison by default; strict comparison must be enabled with the third parameter set to true."} | верно | По умолчанию сравнение нестрогое; строгое — третий аргумент true. |
T04-L4 1.3 c | Arrays | Without a callback, array_filter() removes all "empty" (falsy) elements from the array. | «yes» Пояснение: When array_filter() is called without a callback, it removes all elements considered 'empty' by PHP, i.e., falsy values like 0, 0.0, "", "0", false, null, and empty arrays.
Raw{"answer": "yes", "explanation": "When array_filter() is called without a callback, it removes all elements considered 'empty' by PHP, i.e., falsy values like 0, 0.0, \"\", \"0\", false, null, and empty arrays."} | верно | Убирает 0, "", null, false и пустые массивы. |
T04-L5 0.87 c | Arrays | By default, array_slice() preserves the original numeric keys of the array. | «no» Пояснение: By default, the preserve_keys parameter in array_slice() is false, so numeric keys are reindexed.
Raw{"answer":"no","explanation":"By default, the preserve_keys parameter in array_slice() is false, so numeric keys are reindexed."} | верно | По умолчанию ключи перенумеровываются; сохранение — preserve_keys = true. |
T04-L6 3.95 c | Arrays | What does array_slice([10, 20, 30, 40], 1, 2) return? | «[20, 30]» Пояснение: array_slice starts at index 1 and takes 2 elements, producing [20, 30].
Raw{ ⏎ "answer": "[20, 30]", ⏎ "explanation": "array_slice starts at index 1 and takes 2 elements, producing [20, 30]." ⏎ } | верно | [20,30]; ключи перенумеровываются. |
T04-L7 2.2 c | Arrays | How many elements will count(['a' => 1] + ['a' => 9, 'b' => 2]) return? | «2» Пояснение: The + operator merges the second array into the first without overwriting existing keys, resulting in ['a' => 1, 'b' => 2], which has 2 elements.
Raw{"answer": 2, "explanation": "The + operator merges the second array into the first without overwriting existing keys, resulting in ['a' => 1, 'b' => 2], which has 2 elements."} | верно | Оператор + : по ключу 'a' побеждает левый; итого 2. |
T04-L8 2.22 c | Arrays | Since PHP 8.1, the spread operator [...$a, ...$b] supports arrays with string keys. | «yes» Пояснение: In PHP 8.1 the spread operator in array literals was extended to allow arrays with string (non-sequential) keys; prior versions would throw a TypeError.
Raw{"answer":"yes","explanation":"In PHP 8.1 the spread operator in array literals was extended to allow arrays with string (non-sequential) keys; prior versions would throw a TypeError."} | верно | В 8.0 — только числовые ключи; 8.1 снял ограничение. |
T05-L1 143.93 c | Functions and closures | Named arguments cannot be combined with argument unpacking ...$args in a single call. | «no» Пояснение: PHP allows mixing named arguments with the spread operator, e.g. foo(bar: 2, ...$args).
Raw{"answer": "no", "explanation": "PHP allows mixing named arguments with the spread operator, e.g. foo(bar: 2, ...$args)."} | верно | Можно: f(...$args, имя: значение). Нельзя только позиционный аргумент после распаковки. |
T05-L2 2.09 c | Functions and closures | An anonymous function without use sees variables from the outer scope. | «no» Пояснение: An anonymous function must use the use keyword to capture variables from the outer scope.
Raw{"answer":"no","explanation":"An anonymous function must use the use keyword to capture variables from the outer scope."} | верно | Без use внешние переменные недоступны; авто-захват только у fn. |
T05-L3 1.35 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, which is three in f(1, 2, 3).
Raw{"answer": 3, "explanation": "func_num_args() returns the number of arguments actually passed to the function, which is three in f(1, 2, 3)."} | верно | Считает переданные аргументы: 3. |
T05-L4 16.2 c | Functions and closures | The body of an arrow function fn may consist of several expressions in curly braces. | «no» Пояснение: PHP arrow functions have a single-expression body and do not use curly braces to group multiple statements.
Raw{"answer":"no","explanation":"PHP arrow functions have a single-expression body and do not use curly braces to group multiple statements."} | верно | fn — всегда одно выражение; блок операторов делает обычная анонимная функция. |
T05-L5 2.14 c | Functions and closures | An arrow function fn captures outer variables by reference (lazily, at use time). | «yes» Пояснение: In JavaScript, an arrow function forms a closure over its lexical environment, so it reads the current outer variable values when called.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "In JavaScript, an arrow function forms a closure over its lexical environment, so it reads the current outer variable values when called." ⏎ } | неверно верный: «no» | fn захватывает только по значению, автоматически; по ссылке — только &$var в use у обычной функции (fn так не умеет). |
T05-L6 3.92 c | Functions and closures | A closure declared as static function () {} does not capture $this. | «yes» Пояснение: In PHP, a closure declared with the static keyword does not have access to the instance context and cannot capture or use $this, even if it is defined inside a non-static class method.
Raw{"answer": "yes", "explanation": "In PHP, a closure declared with the static keyword does not have access to the instance context and cannot capture or use $this, even if it is defined inside a non-static class method."} | верно | static-замыкание отвязано от объекта: $this внутри недоступен. |
T05-L7 1.46 c | Functions and closures | What will this print: $x = 5; $f = function () use ($x) { return $x; }; $x = 7; echo $f(); | «5» Пояснение: PHP closures capture variables by value by default, so the closure still returns the original value 5.
Raw{ ⏎ "answer": 5, ⏎ "explanation": "PHP closures capture variables by value by default, so the closure still returns the original value 5." ⏎ } | верно | use захватывает по значению в момент создания: 5. |
T05-L8 1.2 c | Functions and closures | In weak typing mode (without strict_types), passing the string "5" to an int parameter is allowed. | «yes» Пояснение: Without strict_types, PHP allows type coercion such as converting the numeric string "5" to an int.
Raw{"answer": "yes", "explanation": "Without strict_types, PHP allows type coercion such as converting the numeric string \"5\" to an int."} | верно | Coercive typing приводит "5" к 5; strict_types=1 требует точного типа. |
T06-L1 0.79 c | OOP: classes and inheritance | PHP supports constructor property promotion: public function __construct(private int $x) {}. | «yes» Пояснение: PHP 8.1 introduced constructor property promotion, allowing parameters to become class properties directly in the constructor.
Raw{"answer": "yes", "explanation": "PHP 8.1 introduced constructor property promotion, allowing parameters to become class properties directly in the constructor."} | верно | С PHP 8.0 параметр с модификатором создаёт свойство и присваивание. |
T06-L2 0.87 c | OOP: classes and inheritance | Which keyword prevents a method from being overridden in subclasses? | «final» Пояснение: The 'final' keyword in PHP prevents a method from being overridden by subclasses.
Raw{"answer": "final", "explanation": "The 'final' keyword in PHP prevents a method from being overridden by subclasses."} | верно | final. |
T06-L3 0.61 c | OOP: classes and inheritance | A method declared final cannot be overridden in a subclass. | «yes» Пояснение: A final method cannot be overridden in a subclass.
Raw{"answer": "yes", "explanation": "A final method cannot be overridden in a subclass."} | верно | final запрещает переопределение метода и наследование класса. |
T06-L4 0.8 c | OOP: classes and inheritance | Parent properties with private visibility are accessible in a subclass. | «no» Пояснение: In PHP, private properties are only accessible within the class that declares them, not in subclasses.
Raw{"answer":"no","explanation":"In PHP, private properties are only accessible within the class that declares them, not in subclasses."} | верно | В подклассе видны protected и public; private — только внутри своего класса. |
T06-L5 145.93 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» Пояснение: The anonymous-class name is NUL-embedded after the literal prefix, so the part before the NUL byte is just "class".
Raw{"answer": "class", "explanation": "The anonymous-class name is NUL-embedded after the literal prefix, so the part before the NUL byte is just \"class\"."} | неверно верный: «class@anonymous» | get_class анонимного класса печатает class@anonymous\0<файл>:<строка>$n; короткая форма — часть до NUL-байта. Проверено php -r (hex). |
T06-L6 2.82 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 or part of the inheritance contract, so a child class can declare a method with the same name and choose any visibility.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Private methods are not inherited or part of the inheritance contract, so a child class can declare a method with the same name and choose any visibility." ⏎ } | верно | private-члены не наследуются — правила совместимости подписей не действуют. |
T06-L7 2.41 c | OOP: classes and inheritance | The magic method __get() is called only for non-existent properties. | «no» Пояснение: __get() is also invoked for inaccessible properties, not only non-existent ones.
Raw{"answer":"no","explanation":"__get() is also invoked for inaccessible properties, not only non-existent ones."} | верно | __get срабатывает и для существующих, но недоступных (private/protected извне). |
T06-L8 1.79 c | OOP: classes and inheritance | What does reassigning a readonly property throw — Exception or Error? | «error» Пояснение: Reassigning a readonly property in PHP (8.1+) throws a ReadOnlyPropertyException, which is a subclass of Error, not Exception.
Raw{"answer": "Error", "explanation": "Reassigning a readonly property in PHP (8.1+) throws a ReadOnlyPropertyException, which is a subclass of Error, not Exception."} | верно | Error (readonly с 8.1); оговорка: в __clone() переинициализация допустима (8.3+). |
T07-L1 0.48 c | Interfaces, traits, enum | An interface can declare constants. | «yes» Пояснение: In PHP, an interface may define constants, which must be public and initialized.
Raw{"answer":"yes","explanation":"In PHP, an interface may define constants, which must be public and initialized."} | верно | Константы интерфейса наследуются реализациями. |
T07-L2 0.94 c | Interfaces, traits, enum | Which operator checks whether an object is an instance of a class or interface? | «instanceof» Пояснение: The instanceof operator checks whether an object is an instance of a class or interface in PHP.
Raw{"answer": "instanceof", "explanation": "The instanceof operator checks whether an object is an instance of a class or interface in PHP."} | верно | instanceof. |
T07-L3 2.23 c | Interfaces, traits, enum | An interface can declare static methods. | «no» Пояснение: PHP interfaces can only declare abstract methods, not static methods.
Raw{"answer": "no", "explanation": "PHP interfaces can only declare abstract methods, not static methods."} | неверно верный: «yes» | Реализация обязана дать статический метод с той же сигнатурой. |
T07-L4 1.98 c | Interfaces, traits, enum | The instanceof operator only checks class inheritance: it ignores interfaces. | «no» Пояснение: The instanceof operator checks both class inheritance and interface implementation.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "The instanceof operator checks both class inheritance and interface implementation." ⏎ } | верно | instanceof возвращает true и для интерфейсов объекта. |
T07-L5 1.45 c | Interfaces, traits, enum | An interface method may have a default implementation, like a trait method. | «no» Пояснение: PHP interface methods are abstract and cannot have a default implementation.
Raw{"answer": "no", "explanation": "PHP interface methods are abstract and cannot have a default implementation."} | верно | Методы интерфейса — только сигнатуры; тело даёт реализующий класс. |
T07-L6 2.33 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.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "In PHP, abstract methods can be declared as public or protected." ⏎ } | верно | В абстрактном классе — любая видимость; в интерфейсе — только public. |
T07-L7 1.26 c | Interfaces, traits, enum | How many elements will Foo::cases() return for enum Foo { case A; case B; case C; }? | «3» Пояснение: Foo::cases() returns one element per enum case, and there are three cases: A, B, and C.
Raw{"answer": 3, "explanation": "Foo::cases() returns one element per enum case, and there are three cases: A, B, and C."} | верно | Статический метод cases(): 3. |
T07-L8 5.08 c | Interfaces, traits, enum | A trait can declare constants. | «yes» Пояснение: In PHP, traits are allowed to declare constants.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "In PHP, traits are allowed to declare constants." ⏎ } | верно | С PHP 8.2 трейты могут объявлять константы (RFC constants_in_traits); до 8.2 — нет. |
T08-L1 1.16 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 2.33 c | Exceptions and errors | A catch (Exception $e) block will also catch TypeError, because TypeError ultimately inherits from Exception. | «no» Пояснение: TypeError inherits from Error, not Exception, so catch (Exception $e) will not catch it.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "TypeError inherits from Error, not Exception, so catch (Exception $e) will not catch it." ⏎ } | верно | TypeError наследуется от Error; catch (Exception) его не ловит. |
T08-L3 1.02 c | Exceptions and errors | The @ operator suppresses exceptions too. | «no» Пояснение: The PHP @ operator suppresses errors and warnings, but it does not catch or suppress exceptions.
Raw{"answer": "no", "explanation": "The PHP @ operator suppresses errors and warnings, but it does not catch or suppress exceptions."} | верно | @ глушит диагностику (warnings/notices), исключения не перехватывает. |
T08-L4 1.34 c | Exceptions and errors | What error class does intdiv(5, 0) throw? | «divisionbyzeroerror» Пояснение: intdiv(5, 0) throws a DivisionByZeroError in PHP.
Raw{"answer":"DivisionByZeroError","explanation":"intdiv(5, 0) throws a DivisionByZeroError in PHP."} | верно | DivisionByZeroError (иерархия Error, не Exception); php-грейдер объективен. |
T08-L5 1.48 c | Exceptions and errors | The finally block runs only if the exception was caught by a catch block. | «no» Пояснение: The finally block executes regardless of whether an exception was thrown or caught.
Raw{"answer":"no","explanation":"The finally block executes regardless of whether an exception was thrown or caught."} | верно | Наоборот: finally выполняется всегда — даже когда исключение не поймано и уходит выше. Проверено php -r. |
T08-L6 4.59 c | Exceptions and errors | An exception thrown inside a finally block has no effect on the result of the try block. | «no» Пояснение: In PHP, an exception thrown inside a finally block propagates in place of any original exception from the try block.
Raw{"answer": "no", "explanation": "In PHP, an exception thrown inside a finally block propagates in place of any original exception from the try block."} | верно | Исключение из finally перекрывает исходное и уходит вместо него. |
T08-L7 6.6 c | Exceptions and errors | What does the expression (bool) new Exception('x') return? | «yes» Пояснение: In PHP, casting any object instance to bool results in true.
Raw{"answer":"yes","explanation":"In PHP, casting any object instance to bool results in true."} | верно | Любой объект при приведении к bool — true. Формы ответа: true или да. |
T08-L8 3.4 c | Exceptions and errors | Functions registered via register_shutdown_function() run when exit is called. | «yes» Пояснение: register_shutdown_function callbacks run during PHP shutdown, which occurs when the script ends via exit().
Raw{"answer":"yes","explanation":"register_shutdown_function callbacks run during PHP shutdown, which occurs when the script ends via exit()."} | верно | exit завершает скрипт, но shutdown-функции отрабатывают. |
T09-L1 1.47 c | Namespaces and autoloading | The use App\Service\Mailer; statement itself loads the class file. | «no» Пояснение: The `use` statement is a compile-time alias for a class or interface and does not trigger the autoloader or load any class file; the file is only loaded when the class is actually instantiated or referenced at runtime.
Raw{"answer": "no", "explanation": "The `use` statement is a compile-time alias for a class or interface and does not trigger the autoloader or load any class file; the file is only loaded when the class is actually instantiated or referenced at runtime."} | верно | use — псевдоним на этапе компиляции; файл грузит автозагрузчик при первом обращении. |
T09-L2 1.65 c | Namespaces and autoloading | What follows use to import a function (not a class): the word function or const? | «function» Пояснение: In PHP, you use `use function` to import a function from another namespace.
Raw{ ⏎ "answer": "function", ⏎ "explanation": "In PHP, you use `use function` to import a function from another namespace." ⏎ } | верно | use function ...; (и use const для констант). |
T09-L3 2.13 c | Namespaces and autoloading | Into which file (path from src/) does the PSR-4 mapping "App\ → src/" place the class App\Controller\Api\UserController? | «controller/api/usercontroller.php» Пояснение: PSR-4 drops the App\ namespace prefix and maps the remaining namespace parts Controller\Api\ to the directory Controller/Api, with the class name as UserController.php.
Raw{ ⏎ "answer": "Controller/Api/UserController.php", ⏎ "explanation": "PSR-4 drops the App\\ namespace prefix and maps the remaining namespace parts Controller\\Api\\ to the directory Controller/Api, with the class name as UserController.php." ⏎ } | верно | Остаток имени после префикса, \ → /. |
T09-L4 2.5 c | Namespaces and autoloading | Including vendor/autoload.php registers autoloaders via spl_autoload_register(). | «yes» Пояснение: The generated vendor/autoload.php file instantiates a Composer\Autoload\ClassLoader and calls its register() method, which internally uses spl_autoload_register() to hook in the classmap and PSR-4 autoloader.
Raw{"answer": "yes", "explanation": "The generated vendor/autoload.php file instantiates a Composer\\Autoload\\ClassLoader and calls its register() method, which internally uses spl_autoload_register() to hook in the classmap and PSR-4 autoloader."} | верно | Composer ставит автозагрузчик именно на spl_autoload_register. |
T09-L5 0.88 c | Namespaces and autoloading | The magic constant __NAMESPACE__ contains the name of the current namespace. | «yes» Пояснение: __NAMESPACE__ is a magic constant that returns the current namespace name, or an empty string in the global namespace.
Raw{"answer":"yes","explanation":"__NAMESPACE__ is a magic constant that returns the current namespace name, or an empty string in the global namespace."} | верно | В корневом пространстве — пустая строка. |
T09-L6 8.94 c | Namespaces and autoloading | An unqualified class name (without a leading \) in new is resolved from the global root. | «no» Пояснение: Unqualified class names are resolved in the current namespace first, then fall back to the global namespace.
Raw{"answer":"no","explanation":"Unqualified class names are resolved in the current namespace first, then fall back to the global namespace."} | верно | Резолвится относительно текущего namespace (с учётом импортов). |
T09-L7 2.31 c | Namespaces and autoloading | With the PSR-4 mapping "App\ → src/", the class App\Model\User lives in the file src/Model/User.php. | «yes» Пояснение: Under PSR-4, the namespace prefix App\ maps to src/, so the remaining sub-namespace Model\User is appended as Model/User.php, giving the path src/Model/User.php.
Raw{"answer": "yes", "explanation": "Under PSR-4, the namespace prefix App\\ maps to src/, so the remaining sub-namespace Model\\User is appended as Model/User.php, giving the path src/Model/User.php."} | верно | Остаток имени после префикса переносится в путь как есть. |
T09-L8 85.48 c | Namespaces and autoloading | A use statement may be written inside a function body — the import then applies to that function only. | «yes» Пояснение: PHP allows a use statement inside a function body, and its import is scoped to that function only.
Raw{"answer":"yes","explanation":"PHP allows a use statement inside a function body, and its import is scoped to that function only."} | неверно верный: «no» | use внутри тела функции — parse error; импорты файловые и компиляционные. |
T10-L1 1.02 c | References and scope | Arrays are copied on assignment rather than passed by reference. | «yes» Пояснение: In PHP, arrays are value types and are copied when assigned to another variable.
Raw{"answer": "yes", "explanation": "In PHP, arrays are value types and are copied when assigned to another variable."} | верно | Присваивание массива — копия (в движке — copy-on-write). |
T10-L2 1.09 c | References and scope | What will this print: $a = [1, 2]; $b = $a; $b[] = 3; echo count($a); | «2» Пояснение: PHP arrays are copied by value, so modifying $b does not affect $a.
Raw{ ⏎ "answer": 2, ⏎ "explanation": "PHP arrays are copied by value, so modifying $b does not affect $a." ⏎ } | верно | Присваивание — копия: в $a по-прежнему 2 элемента. |
T10-L3 3.22 c | References and scope | Inside a function, user-defined global variables are inaccessible without global, $GLOBALS, or passing them as parameters. | «yes» Пояснение: In PHP, local scope does not inherit global scope, so user-defined global variables must be explicitly accessed inside a function via the global keyword, the $GLOBALS superglobal array, or by passing them as parameters.
Raw{"answer": "yes", "explanation": "In PHP, local scope does not inherit global scope, so user-defined global variables must be explicitly accessed inside a function via the global keyword, the $GLOBALS superglobal array, or by passing them as parameters."} | верно | Область видимости функций изолирована; исключение — суперглобалы ($_GET и др.). |
T10-L4 2.24 c | References and scope | unset($GLOBALS['x']) inside a function removes the global variable only for that function. | «no» Пояснение: unset($GLOBALS['x']) removes the global variable from the global scope, not just for that function.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "unset($GLOBALS['x']) removes the global variable from the global scope, not just for that function." ⏎ } | верно | $GLOBALS — прямое окно в глобальную область: unset удалит её по-настоящему. |
T10-L5 1.02 c | References and scope | What will this print: function inc(&$x) { $x++; } $n = 5; inc($n); echo $n; | «6» Пояснение: The variable $n is passed by reference to inc(), so incrementing $x inside the function increases $n from 5 to 6.
Raw{"answer":"6","explanation":"The variable $n is passed by reference to inc(), so incrementing $x inside the function increases $n from 5 to 6."} | верно | Ссылка меняет оригинал: 6. |
T10-L6 8.14 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» Пояснение: In PHP, foreach by value iterates over a copy of the array, so changes to the original array during the same pass are not visible.
Raw{"answer": "no", "explanation": "In PHP, foreach by value iterates over a copy of the array, so changes to the original array during the same pass are not visible."} | верно | По значению foreach итерирует копию-снимок. |
T10-L7 1.05 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 and is shared among all instances.
Raw{"answer": "no", "explanation": "A static property belongs to the class and is shared among all instances."} | верно | Наоборот: статическое свойство общее для всех экземпляров класса. Проверено php -r. |
T10-L8 2.3 c | References and scope | An array can have a boolean key true, and it will be stored as bool. | «no» Пояснение: PHP converts boolean array keys to integers, so true is stored as the integer key 1, not as a boolean.
Raw{"answer": "no", "explanation": "PHP converts boolean array keys to integers, so true is stored as the integer key 1, not as a boolean."} | верно | Булев ключ приводится к int: true → 1, false → 0. |
T11-L1 2.26 c | Generators, iterators, SPL | Inside a generator, return with a value can be used, and it becomes available via $gen->getReturn(). | «yes» Пояснение: Since PHP 8.1, a generator can return a value with `return`, and that value is available via `getReturn()` after the generator finishes.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Since PHP 8.1, a generator can return a value with `return`, and that value is available via `getReturn()` after the generator finishes." ⏎ } | верно | return-значение генератора доступно через getReturn() после прохода. |
T11-L2 1.26 c | Generators, iterators, SPL | A fully consumed generator can be rewound with rewind() and traversed again. | «no» Пояснение: PHP generators are single-use; once fully consumed they cannot be rewound or iterated again.
Raw{"answer":"no","explanation":"PHP generators are single-use; once fully consumed they cannot be rewound or iterated again."} | верно | Генератор одноразовый: rewind после начала итерации бросает Exception. |
T11-L3 1.29 c | Generators, iterators, SPL | The yield from construct delegates traversal to another generator or iterable. | «yes» Пояснение: PHP's yield from delegates iteration to another generator or iterable.
Raw{"answer":"yes","explanation":"PHP's yield from delegates iteration to another generator or iterable."} | верно | yield from проксирует значения, ключи и return-значение внутреннего генератора. |
T11-L4 2.75 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 2.38 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 converting it to an array produces three elements.
Raw{"answer": 3, "explanation": "The generator yields three values, so converting it to an array produces three elements."} | верно | yield from делегирует все 3 элемента. |
T11-L6 0.83 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 0.88 c | Generators, iterators, SPL | ArrayIterator allows wrapping an array and traversing it via the Iterator interface. | «yes» Пояснение: ArrayIterator implements Iterator and can wrap an array for traversal.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "ArrayIterator implements Iterator and can wrap an array for traversal." ⏎ } | верно | Объектная обёртка над массивом. |
T11-L8 2.01 c | Generators, iterators, SPL | An ArrayObject instance cannot be traversed with foreach. | «no» Пояснение: ArrayObject implements Traversable, so it can be traversed with foreach.
Raw{"answer":"no","explanation":"ArrayObject implements Traversable, so it can be traversed with foreach."} | верно | ArrayObject реализует IteratorAggregate — foreach по нему работает. |
T12-L1 1.39 c | Configuration and security | password_hash() generates a salt automatically — passing one separately is not needed. | «yes» Пояснение: password_hash() automatically generates and embeds the salt, so you should not pass a separate salt.
Raw{"answer":"yes","explanation":"password_hash() automatically generates and embeds the salt, so you should not pass a separate salt."} | верно | Соль встраивается в строку результата; параметр salt устарел. |
T12-L2 2.75 c | Configuration and security | In PHP 8, PASSWORD_DEFAULT is md5 with an automatically added salt. | «no» Пояснение: In PHP 8, PASSWORD_DEFAULT uses the default password hashing algorithm, which is bcrypt, not MD5.
Raw{ ⏎ "answer": "false", ⏎ "explanation": "In PHP 8, PASSWORD_DEFAULT uses the default password hashing algorithm, which is bcrypt, not MD5." ⏎ } | верно | PASSWORD_DEFAULT — bcrypt; md5 для паролей непригоден (перебирается массово). |
T12-L3 1.01 c | Configuration and security | What does password_verify('secret', password_hash('secret', PASSWORD_DEFAULT)) return? | «yes» Пояснение: password_verify() returns true when the password matches the generated hash.
Raw{"answer":"yes","explanation":"password_verify() returns true when the password matches the generated hash."} | верно | Соль и хеш в одной строке: true (форма ответа: true или да). |
T12-L4 1.17 c | Configuration and security | strip_tags() protects against SQL injection. | «no» Пояснение: strip_tags() only removes HTML tags and does not prevent SQL injection.
Raw{"answer":"no","explanation":"strip_tags() only removes HTML tags and does not prevent SQL injection."} | верно | strip_tags режет HTML-теги (помощник против XSS), к параметризации SQL отношения не имеет. |
T12-L5 0.98 c | Configuration and security | session_regenerate_id() is used to protect against session fixation upon user login. | «yes» Пояснение: session_regenerate_id() creates a new session ID after login to help prevent session fixation attacks.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "session_regenerate_id() creates a new session ID after login to help prevent session fixation attacks." ⏎ } | верно | Новый ID сессии после логина — стандартная защита от session fixation. |
T12-L6 1.33 c | Configuration and security | Which built-in function returns the SAPI name (e.g., cli)? | «php_sapi_name» Пояснение: The php_sapi_name() function returns the current PHP SAPI name, such as 'cli'.
Raw{ ⏎ "answer": "php_sapi_name", ⏎ "explanation": "The php_sapi_name() function returns the current PHP SAPI name, such as 'cli'." ⏎ } | верно | php_sapi_name(). |
T12-L7 1.64 c | Configuration and security | session_destroy() deletes session data on the server but not the cookie in the user's browser. | «yes» Пояснение: session_destroy() only destroys the server-side session data; the session cookie remains in the browser and must be deleted separately with setcookie().
Raw{"answer": "yes", "explanation": "session_destroy() only destroys the server-side session data; the session cookie remains in the browser and must be deleted separately with setcookie()."} | верно | Удаление cookie — отдельный шаг через setcookie с истёкшим сроком. |
T12-L8 1.53 c | Configuration and security | Without calling session_start(), the $_SESSION array is automatically populated with session data. | «no» Пояснение: You must call session_start() before $_SESSION can be used to load session data.
Raw{"answer": "no", "explanation": "You must call session_start() before $_SESSION can be used to load session data."} | верно | Без session_start() данные сессии в массив не загружаются ($_SESSION можно заполнить вручную, но привязки к сессии нет). |
VC-L1 2.62 c | PHP 8.4–8.5 | In which PHP version was the array_find() function introduced? | «no such function exists» Пояснение: PHP does not have a built-in array_find() function; the user may be thinking of array_search() or in_array().
Raw{"answer":"no such function exists","explanation":"PHP does not have a built-in array_find() function; the user may be thinking of array_search() or in_array()."} | неверно верный: «8.4» | PHP 8.4 (RFC array_find). |
VC-L2 3.0 c | PHP 8.4–8.5 | Property hooks (get/set right in the property declaration) landed in PHP 8.4. | «yes» Пояснение: PHP 8.4 introduced property hooks, allowing get/set logic to be declared directly with a property.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "PHP 8.4 introduced property hooks, allowing get/set logic to be declared directly with a property." ⏎ } | верно | Property hooks — PHP 8.4 (ноябрь 2024). |
VC-L3 1.09 c | PHP 8.4–8.5 | Asymmetric visibility (public private(set) string $name) appeared in PHP 8.4. | «yes» Пояснение: Asymmetric visibility was introduced in PHP 8.4.
Raw{"answer": "yes", "explanation": "Asymmetric visibility was introduced in PHP 8.4."} | верно | Asymmetric visibility v2 — PHP 8.4. |
VC-L4 5.65 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 8.38 c | PHP 8.4–8.5 | In which PHP version did the pipe operator |> first appear? Answer with the version number. | «it does not exist» Пояснение: PHP has never included a pipe operator (|>); this is a feature found in other languages like Rust, C#, or Haskell, not in any stable PHP release.
Raw{"answer": "It does not exist", "explanation": "PHP has never included a pipe operator (|>); this is a feature found in other languages like Rust, C#, or Haskell, not in any stable PHP release."} | неверно верный: «8.5» | Pipe operator — PHP 8.5 (2025). |
VC-L6 135.9 c | PHP 8.4–8.5 | In which PHP version did clone-with — the syntax clone($obj, ['x' => 1]) — appear? Answer with the version number. | «8.4» Пояснение: PHP 8.4 introduced the clone-with syntax.
Raw{ ⏎ "answer": "8.4", ⏎ "explanation": "PHP 8.4 introduced the clone-with syntax." ⏎ } | неверно верный: «8.5» | Clone with v2 — PHP 8.5. |
VC-L7 1.75 c | PHP 8.4–8.5 | In which PHP version were the array_first() and array_last() functions introduced? | «8.3» Пояснение: array_first() and array_last() were introduced in PHP 8.3.
Raw{ ⏎ "answer": "8.3", ⏎ "explanation": "array_first() and array_last() were introduced in PHP 8.3." ⏎ } | неверно верный: «8.5» | PHP 8.5. |
VC-L8 64.89 c | PHP 8.4–8.5 | For which PHP version was RFC Partial Function Application v2 adopted (as of 2026-11-07)? Answer with the version number. | «8.5» Пояснение: RFC Partial Function Application v2 was adopted for PHP 8.5.
Raw{"answer":"8.5","explanation":"RFC Partial Function Application v2 was adopted for PHP 8.5."} | неверно верный: «8.6» | PFA v2 принят 05.12.2025 (33-0-0), реализован в PHP 8.6. |
VF-L1 1.54 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.3» Пояснение: The clamp_v2 RFC introducing the clamp() function was implemented in PHP 8.3.
Raw{"answer": "8.3", "explanation": "The clamp_v2 RFC introducing the clamp() function was implemented in PHP 8.3."} | неверно верный: «8.6» | По данным владельца (wiki.php.net/rfc): clamp_v2 — 8.6; clamp() в 8.5.11 отсутствует (косвенное подтверждение). Дата-якорь делает клетку монотонной. |
VF-L2 73.44 c | PHP: 8.6+ and the future | RFC Context Managers v2 has already been adopted in PHP (as of 2026-11-07). | «no» Пояснение: RFC Context Managers v2 has not been adopted in PHP.
Raw{"answer": "no", "explanation": "RFC Context Managers v2 has not been adopted in PHP."} | верно | На 06.11.2026 — в обсуждении (создан 2026-10-23); не принят. |
VF-L3 2.78 c | PHP: 8.6+ and the future | RFC Bound-Erased Generic Types (generics) was declined in 2026. | «no» Пояснение: There is no known PHP RFC titled 'Bound-Erased Generic Types' that was declined in 2026.
Raw{"answer": "no", "explanation": "There is no known PHP RFC titled 'Bound-Erased Generic Types' that was declined in 2026."} | неверно верный: «yes» | Голосование завершилось 2026-06-28: отклонён (wiki.php.net/rfc). |
VF-L4 60.04 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» Пояснение: PHP's RFC to make ZTS the default build was accepted, so it had already been accepted by that date.
Raw{"answer":"yes","explanation":"PHP's RFC to make ZTS the default build was accepted, so it had already been accepted by that date."} | неверно верный: «no» | Такого принятого RFC нет на дату якоря; якорь делает клетку монотонной — при принятии RFC позже клетка не перевернётся. |
VF-L5 3.88 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 native generics or parameterized types.
Raw{"answer": "yes", "explanation": "PHP 8.5 does not include native generics or parameterized types."} | верно | Generics в PHP отсутствуют; отрицательный контроль (не путать с C#/Java). |
VF-L6 2.9 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» Пояснение: On 2026-11-07, PHP 8.5 would be the current stable release while PHP 8.6 had not yet reached GA on 2026-11-19.
Raw{"answer":"yes","explanation":"On 2026-11-07, PHP 8.5 would be the current stable release while PHP 8.6 had not yet reached GA on 2026-11-19."} | верно | 8.5 — релиз осени 2025; 8.6 GA 19.11.2026 (wiki.php.net/todo/php86). Дата снимка — 06.11.2026. |
VF-L7 1.02 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 not released, and PHP 7.0 followed PHP 5.6 directly.
Raw{"answer": "yes", "explanation": "PHP 6 was not released, and PHP 7.0 followed PHP 5.6 directly."} | верно | Исторический факт: ветка 6 не была релизнута. |
VF-L8 17.42 c | PHP: 8.6+ and the future | The RFC adding the #[\Deprecated] attribute to the core was adopted. | «yes» Пояснение: The RFC adding the #[\Deprecated] attribute to PHP's core was adopted.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "The RFC adding the #[\\Deprecated] attribute to PHP's core was adopted." ⏎ } | верно | #[\Deprecated] — принят, реализован в PHP 8.4. |
T25-L1 1.89 c | Clean architecture | The dependency rule of clean and onion architecture: inner layers know nothing about outer ones — dependencies point toward the center. | «yes» Пояснение: In clean and onion architecture, the dependency rule mandates that dependencies point inward toward the core, meaning inner (core) layers have no knowledge of or dependency on outer layers.
Raw{"answer":"yes","explanation":"In clean and onion architecture, the dependency rule mandates that dependencies point inward toward the core, meaning inner (core) layers have no knowledge of or dependency on outer layers."} | верно | Чистая (Robert C. Martin), луковичная (Jeffrey Palermo) и гексагональная (ports & adapters) — варианты одной идеи: зависимости направлены внутрь, к домену. Слоями в проекте следит deptrac. |
T25-L2 1.07 c | Clean architecture | Domain entities import neither Doctrine nor Symfony — only the language and, possibly, the standard library. | «yes» Пояснение: Domain entities should be independent of persistence and framework details, relying only on the language and standard library.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Domain entities should be independent of persistence and framework details, relying only on the language and standard library." ⏎ } | верно | Изоляция домена от инфраструктуры; deptrac в проекте как раз следит за слоями. |
T25-L3 2.03 c | Clean architecture | Controllers and Twig templates belong to the business-logic layer because they are the ones calling use cases. | «no» Пояснение: Controllers and Twig templates are presentation-layer components, not part of the business-logic layer.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "Controllers and Twig templates are presentation-layer components, not part of the business-logic layer." ⏎ } | верно | Наоборот: это интерфейсные адаптеры (внешний слой); они зависят от use cases, а не наоборот. |
T25-L4 1.55 c | Clean architecture | What sits at the very center of the onion architecture? | «domain» Пояснение: In Onion Architecture, the innermost core is the domain layer.
Raw{"answer": "domain", "explanation": "In Onion Architecture, the innermost core is the domain layer."} | неверно верный: «domain model» | Центральное кольцо — Domain Model: сущности и бизнес-правила без зависимостей; далее Domain Services → Application Services → Infrastructure/UI/Tests (Palermo). |
T25-L5 0.89 c | Clean architecture | Layer boundary violations can be caught automatically: a layer-dependency analyzer (e.g. deptrac) fails on a forbidden call. | «yes» Пояснение: A dependency analyzer can detect and fail on forbidden calls between layers.
Raw{"answer": "yes", "explanation": "A dependency analyzer can detect and fail on forbidden calls between layers."} | верно | depfile.yaml в проекте TasK: CI проверяет правила слоёв на каждом пайплайне. |
T25-L6 1.47 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 take domain-level arguments, not infrastructure objects like an HTTP request or EntityManager.
Raw{"answer": "no", "explanation": "A use case should take domain-level arguments, not infrastructure objects like an HTTP request or EntityManager."} | верно | Use case принимает DTO и порты; привязка к HTTP/ORM протекает инфраструктуру во внутренние слои. |
T25-L7 0.91 c | Clean architecture | What is the component called that provides a collection of aggregates/entities while hiding the storage mechanism behind an interface? | «repository» Пояснение: A Repository encapsulates a collection of aggregates/entities and abstracts their persistence behind an interface.
Raw{"answer": "Repository", "explanation": "A Repository encapsulates a collection of aggregates/entities and abstracts their persistence behind an interface."} | верно | Repository pattern (DDD/Evans); в проекте — Doctrine-репозитории за портами. |
T25-L8 1.98 c | Clean architecture | In clean architecture, swapping PostgreSQL for another database touches only the outer layer — the domain and use cases stay unchanged. | «yes» Пояснение: In clean architecture, database-specific details are isolated in interface adapters or infrastructure layers, so the domain and use cases remain unchanged when swapping PostgreSQL for another database.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "In clean architecture, database-specific details are isolated in interface adapters or infrastructure layers, so the domain and use cases remain unchanged when swapping PostgreSQL for another database." ⏎ } | верно | Следствие правила зависимостей: инфраструктура взаимозаменяема. |
T26-L1 0.84 c | DDD | In DDD, an aggregate is just another name for a database table. | «no» Пояснение: In DDD, an aggregate is a cluster of domain objects, not simply a database table.
Raw{"answer": "no", "explanation": "In DDD, an aggregate is a cluster of domain objects, not simply a database table."} | верно | Агрегат — кластер объектов с границей согласованности (транзакционной вокруг корня); таблица — деталь хранения. |
T26-L2 1.04 c | DDD | A Value Object is immutable and compared by the values of its fields, not by identity. | «yes» Пояснение: A Value Object is typically immutable and uses value equality based on its fields rather than object identity.
Raw{"answer": "yes", "explanation": "A Value Object is typically immutable and uses value equality based on its fields rather than object identity."} | верно | Классика Evans: Money, Email; равенство структурное. |
T26-L3 1.2 c | DDD | What is the single external entry point of an aggregate, through which all changes must go, called? | «aggregate root» Пояснение: In domain-driven design, the aggregate root is the single entry point through which all changes to an aggregate must be made.
Raw{"answer": "aggregate root", "explanation": "In domain-driven design, the aggregate root is the single entry point through which all changes to an aggregate must be made."} | верно | Aggregate Root: внешние объекты ссылаются только на корень; он защищает инварианты агрегата. |
T26-L4 1.05 c | DDD | In DDD, a repository is declared for an aggregate (its root), not for every entity. | «yes» Пояснение: In DDD, repositories manage aggregates as whole, typically keyed by their aggregate root.
Raw{"answer": "yes", "explanation": "In DDD, repositories manage aggregates as whole, typically keyed by their aggregate root."} | верно | Репозиторий корня хранит границу согласованности агрегата; вложенные сущности доступны только через корень. |
T26-L5 1.84 c | DDD | Ubiquitous language is the model's shared language common to developers and domain experts. | «yes» Пояснение: In Domain-Driven Design, the Ubiquitous Language is the shared vocabulary used consistently by both developers and domain experts to discuss and model the business domain.
Raw{"answer": "yes", "explanation": "In Domain-Driven Design, the Ubiquitous Language is the shared vocabulary used consistently by both developers and domain experts to discuss and model the business domain."} | верно | Evans: язык из требований переходит в имена классов и методов. |
T26-L6 11.85 c | DDD | What is the boundary called within which a model and its language are consistent, while outside the same words mean other models? | «domain» Пояснение: The domain is the boundary of objects within which the model interprets the language consistently.
Raw{ ⏎ "answer": "domain", ⏎ "explanation": "The domain is the boundary of objects within which the model interprets the language consistently." ⏎ } | неверно верный: «bounded context» | Bounded Context; «Заказ» в биллинге и в доставке — разные модели. |
T26-L7 1.67 c | DDD | An anemic model (objects with only getters/setters, logic in services) is the recommended DDD style. | «no» Пояснение: DDD recommends a rich domain model where entities and value objects encapsulate business logic, rather than an anemic model that pushes all behavior into services.
Raw{"answer": "no", "explanation": "DDD recommends a rich domain model where entities and value objects encapsulate business logic, rather than an anemic model that pushes all behavior into services."} | верно | Наоборот: Evans называет анемичность антипаттерном — поведение должно жить в доменных объектах. |
T26-L8 0.82 c | DDD | Bounded context means each context has its own model: the same concept in different contexts is a different class. | «yes» Пояснение: A bounded context isolates its own model, so the same concept can be represented as different classes in different contexts.
Raw{"answer": "yes", "explanation": "A bounded context isolates its own model, so the same concept can be represented as different classes in different contexts."} | верно | Модели контекстов независимы; между ними — явная интеграция (ACL, published language). |
T13-L1 4.04 c | Symfony | Services in the Symfony DI container are created lazily by default — on first use. | «yes» Пояснение: Symfony's DI container generally instantiates services on first access rather than eagerly at startup.
Raw{"answer": "yes", "explanation": "Symfony's DI container generally instantiates services on first access rather than eagerly at startup."} | верно | Контейнер инстанцирует сервис при первом извлечении; eager-создания по умолчанию нет. |
T13-L2 0.78 c | Symfony | Which Symfony console command lists all registered routes? | «route:list» Пояснение: The Symfony console command route:list shows all registered routes.
Raw{"answer": "route:list", "explanation": "The Symfony console command route:list shows all registered routes."} | неверно верный: «debug:router» | bin/console debug:router (FrameworkBundle); в Symfony 3 команда называлась router:debug. |
T13-L3 0.81 c | Symfony | Symfony autowiring requires manually declaring every service in services.yaml. | «no» Пояснение: Symfony autowiring can discover and configure services automatically without declaring every service in services.yaml.
Raw{"answer": "no", "explanation": "Symfony autowiring can discover and configure services automatically without declaring every service in services.yaml."} | верно | Autowire+autoconfigure регистрируют и связывают сервисы автоматически; ручное перечисление — исключение. |
T13-L4 3.22 c | Symfony | Twig templates are compiled into PHP classes and cached between requests. | «yes» Пояснение: Twig compiles templates into PHP code (typically represented as PHP classes) and caches those compiled templates between requests.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Twig compiles templates into PHP code (typically represented as PHP classes) and caches those compiled templates between requests." ⏎ } | верно | Twig компилирует шаблон один раз; кэш в var/cache/twig, в prod не пересобирается. |
T13-L5 1.63 c | Symfony | In the Symfony dev environment the DI container is rebuilt only after tracked files change, not on every request. | «yes» Пояснение: Symfony's dev environment caches the compiled container and rebuilds it only when tracked changes are detected, not on every request.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Symfony's dev environment caches the compiled container and rebuilds it only when tracked changes are detected, not on every request." ⏎ } | верно | Kernel проверяет freshness ресурсов (конфиги, классы); иначе переиспользуется кэш контейнера. |
T13-L6 0.84 c | Symfony | Which environment variable selects the active Symfony environment (dev/prod)? | «app_env» Пояснение: Symfony reads the APP_ENV environment variable to determine the active environment (e.g., dev or prod).
Raw{"answer": "APP_ENV", "explanation": "Symfony reads the APP_ENV environment variable to determine the active environment (e.g., dev or prod)."} | верно | APP_ENV в .env; APP_DEBUG — отдельный флаг отладки. |
T13-L7 5.37 c | Symfony | A controller method can be private — Symfony routing works with any method of the class. | «no» Пояснение: Symfony controller action methods must be public for routing to invoke them.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "Symfony controller action methods must be public for routing to invoke them." ⏎ } | верно | Действие контроллера должно быть public; приватный метод по маршруту не вызывается. |
T13-L8 6.57 c | Symfony | Event subscribers always receive events before listeners, because the interface gives them priority. | «no» Пояснение: The subscriber interface does not inherently give subscribers priority over listeners; event dispatching order is determined by registration and any priority settings, not by being a subscriber.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "The subscriber interface does not inherently give subscribers priority over listeners; event dispatching order is determined by registration and any priority settings, not by being a subscriber." ⏎ } | верно | Порядок определяет priority, а не тип подписки; приоритеты задаются в getSubscribedEvents() так же, как у слушателей. |
T22-L1 2.18 c | Symfony: Security and forms | In modern Symfony (6.0+) authentication is built on authenticator classes (AuthenticatorInterface); the old guard system has been removed. | «yes» Пояснение: Symfony 6.0+ uses the newer authenticator architecture based on AuthenticatorInterface, while the old Guard system was removed.
Raw{"answer":"yes","explanation":"Symfony 6.0+ uses the newer authenticator architecture based on AuthenticatorInterface, while the old Guard system was removed."} | верно | Guard объявлен устаревшим в 5.3 и удалён в 6.0; в проекте symfony/security-bundle 8.1. |
T22-L2 1.85 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 to a controller method based on roles or permissions, returning a 403 Forbidden response if the user does not have the required grant.
Raw{"answer": "IsGranted", "explanation": "Symfony's #[IsGranted] attribute restricts access to a controller method based on roles or permissions, returning a 403 Forbidden response if the user does not have the required grant."} | верно | #[IsGranted('ROLE_ADMIN')]; атрибут из symfony/security-http. |
T22-L3 1.94 c | Symfony: Security and forms | Voters are Symfony's mechanism for checking access to a specific object: isGranted('EDIT', $post). | «yes» Пояснение: Symfony voters provide granular permission checks such as isGranted('EDIT', $post) for access to a specific object.
Raw{"answer": "yes", "explanation": "Symfony voters provide granular permission checks such as isGranted('EDIT', $post) for access to a specific object."} | верно | VoterInterface->vote(); docs Symfony — Voters. |
T22-L4 3.21 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» Пояснение: Since Symfony 6.0/7+, validation constraints use PHP 8 attributes, and Doctrine ORM 3.x (bundled with Symfony 7) completely removed support for the old annotation-based mapping in favor of PHP attributes.
Raw{"answer":"yes","explanation":"Since Symfony 6.0/7+, validation constraints use PHP 8 attributes, and Doctrine ORM 3.x (bundled with Symfony 7) completely removed support for the old annotation-based mapping in favor of PHP attributes."} | верно | Докблок-аннотации удалены в Symfony 7.0; стандарт — атрибуты. В проекте symfony/validator 8.1. |
T22-L5 2.15 c | Symfony: Security and forms | CSRF protection of Symfony forms is enabled by default: the form validates the token on submission. | «yes» Пояснение: Symfony forms enable CSRF protection by default and validate the token on form submission.
Raw{"answer": "yes", "explanation": "Symfony forms enable CSRF protection by default and validate the token on form submission."} | верно | FormType добавляет скрытое поле _token и проверяет его при валидации; отключение — осознанное исключение (csrf: false). |
T22-L6 0.94 c | Symfony: Security and forms | Form validation in Symfony runs server-side even if the client-side (HTML5) checks passed. | «yes» Пояснение: Symfony performs server-side form validation during request processing regardless of whether client-side HTML5 validation succeeded.
Raw{"answer": "yes", "explanation": "Symfony performs server-side form validation during request processing regardless of whether client-side HTML5 validation succeeded."} | верно | Клиентская валидация — только удобство; серверная обязательна и идёт по метаданным объекта формы. |
T22-L7 1.13 c | Symfony: Security and forms | Which Symfony maker command generates a form class (FormType)? | «make:form» Пояснение: The Symfony Maker command used to generate a form class (FormType) is make:form.
Raw{"answer": "make:form", "explanation": "The Symfony Maker command used to generate a form class (FormType) is make:form."} | верно | bin/console make:form (symfony/maker-bundle — в проекте). |
T22-L8 1.4 c | Symfony: Security and forms | Symfony stores the user's password in the session in plain text. | «no» Пояснение: Symfony does not store the user's plain-text password in the session; it stores authentication information such as the hashed password or user credentials, not the raw password.
Raw{"answer": "no", "explanation": "Symfony does not store the user's plain-text password in the session; it stores authentication information such as the hashed password or user credentials, not the raw password."} | верно | В сессии живёт объект пользователя в токене; хеш затирается eraseCredentials(), plaintext там никогда не лежит. |
T23-L1 1.42 c | Symfony: configuration and services | Symfony bundle configuration lives in config/packages — one file per bundle or topic. | «yes» Пояснение: In modern Symfony projects, config/packages is commonly used for bundle-specific configuration, with one file per bundle or topic.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "In modern Symfony projects, config/packages is commonly used for bundle-specific configuration, with one file per bundle or topic." ⏎ } | верно | Стандартная структура (config/packages/*.yaml); перегрузка — config/packages/<env>. |
T23-L2 2.24 c | Symfony: configuration and services | The .env file with dev defaults is committed to the repository, while real secrets live in the non-committed .env.local. | «yes» Пояснение: This describes the common pattern of committing a safe development defaults file while keeping real secrets in a non-committed local environment file.
Raw{"answer": "yes", "explanation": "This describes the common pattern of committing a safe development defaults file while keeping real secrets in a non-committed local environment file."} | верно | symfony/dotenv: .env — общий безопасный набор значений; локальные секреты — .env.local (gitignored) или secrets-хранилище. |
T23-L3 1.1 c | Symfony: configuration and services | Which Symfony command lists the container's registered services and their aliases? | «debug:container» Пояснение: The Symfony 'debug:container' command displays all services registered in the DI container along with their aliases.
Raw{"answer": "debug:container", "explanation": "The Symfony 'debug:container' command displays all services registered in the DI container along with their aliases."} | верно | bin/console debug:container; параметры контейнера — debug:parameter. |
T23-L4 17.28 c | Symfony: configuration and services | The Symfony container allows changing parameters at runtime: $container->setParameter() works from a controller. | «yes» Пояснение: Symfony's container exposes setParameter(), so an injected container in a controller can modify parameters when the container is not frozen.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Symfony's container exposes setParameter(), so an injected container in a controller can modify parameters when the container is not frozen." ⏎ } | неверно верный: «no» | Контейнер компилируется и замораживается; runtime-значения — только через переменные окружения. |
T23-L5 22.12 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 private (public: false) by default; you must explicitly set public: true to fetch them from the container.
Raw{"answer": "no", "explanation": "In modern Symfony, services are private (public: false) by default; you must explicitly set public: true to fetch them from the container."} | верно | С Symfony 4.0 сервисы по умолчанию private: инжектятся через autowiring; $container->get() — только для публичных. |
T23-L6 1.78 c | Symfony: configuration and services | Without a config file in config/packages a bundle will not work — configuration is mandatory for every bundle. | «no» Пояснение: A bundle does not always require a configuration file in config/packages to work.
Raw{"answer": "no", "explanation": "A bundle does not always require a configuration file in config/packages to work."} | верно | У бандлов есть встроенные умолчания (Extension); конфиг нужен только для отклонений от них. |
T23-L7 4.73 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 resolve environment variables in configuration such as services.yaml.
Raw{"answer": "yes", "explanation": "Symfony uses the %env(VAR)% placeholder syntax to resolve environment variables in configuration such as services.yaml."} | верно | %env(...)% резолвится в рантайме env-процессорами; docs — Env Var Processors. |
T23-L8 1.78 c | Symfony: configuration and services | Which Symfony environment variable enables debug mode (affects the profiler and Twig debugging)? | «app_debug» Пояснение: In Symfony, APP_DEBUG=true enables debug mode, which also enables the profiler and Twig debugging.
Raw{ ⏎ "answer": "APP_DEBUG", ⏎ "explanation": "In Symfony, APP_DEBUG=true enables debug mode, which also enables the profiler and Twig debugging." ⏎ } | верно | APP_DEBUG=1 (в .env dev-окружения); окружение выбирает APP_ENV — см. T13-L6. |
T16-L1 22.98 c | Symfony: Messenger | A single message in Symfony Messenger can only have one handler. | «no» Пояснение: A Symfony Messenger message type can be handled by multiple registered handlers.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "A Symfony Messenger message type can be handled by multiple registered handlers." ⏎ } | верно | Messenger вызывает все хендлеры, подписанные на класс сообщения (docs — Multiple Handlers). |
T16-L2 1.11 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 rather than queuing it for a worker.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "The sync transport processes the message immediately rather than queuing it for a worker." ⏎ } | верно | Наоборот: sync обрабатывает немедленно в том же процессе, что и отправка; очередь — это async-транспорт. |
T16-L3 1.28 c | Symfony: Messenger | Which console command starts the worker that processes Messenger queue messages? | «bin/console messenger:consume» Пояснение: This Symfony console command starts a Messenger worker to consume queued messages.
Raw{"answer": "bin/console messenger:consume", "explanation": "This Symfony console command starts a Messenger worker to consume queued messages."} | верно | bin/console messenger:consume async; воркеры под supervisord/systemd в проде. |
T16-L4 6.3 c | Symfony: Messenger | Retries for failed messages (retry_strategy) are configured per Messenger transport. | «yes» Пояснение: In Symfony Messenger, retry_strategy options are configured per Messenger transport.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "In Symfony Messenger, retry_strategy options are configured per Messenger transport." ⏎ } | верно | retry_strategy на транспорте: max_retries, delay, multiplier; docs — Failed Messages & Retries. |
T16-L5 1.28 c | Symfony: Messenger | By default, Messenger serializes messages to JSON. | «yes» Пояснение: Symfony Messenger uses a JSON encoder by default when serializing messages.
Raw{"answer":"yes","explanation":"Symfony Messenger uses a JSON encoder by default when serializing messages."} | неверно верный: «no» | Дефолтный сериализатор — PhpSerializer (serialize()); JSON-сериализатор включается отдельно. |
T16-L6 5.49 c | Symfony: Messenger | Symfony Scheduler produces messages on a schedule and dispatches them through Messenger. | «no» Пояснение: Symfony Scheduler and Symfony Messenger are separate components: the scheduler runs tasks on a schedule, while Messenger handles asynchronous message passing; the scheduler does not inherently produce and dispatch Messenger messages.
Raw{"answer": "no", "explanation": "Symfony Scheduler and Symfony Messenger are separate components: the scheduler runs tasks on a schedule, while Messenger handles asynchronous message passing; the scheduler does not inherently produce and dispatch Messenger messages."} | неверно верный: «yes» | Schedule → RecurringMessage → шина Messenger; docs — Scheduler. |
T16-L7 0.97 c | Symfony: Messenger | Which built-in Messenger transport stores messages in database tables via Doctrine? | «database» Пояснение: The Doctrine-based Messenger transport is called the database transport.
Raw{"answer": "database", "explanation": "The Doctrine-based Messenger transport is called the database transport."} | неверно верный: «doctrine» | Транспорт doctrine (symfony/doctrine-messenger); таблица messenger_messages. В проекте стоит amqp-messenger + doctrine-messenger. |
T16-L8 16.27 c | Symfony: Messenger | The Messenger pipeline can be extended with custom middleware, placed before or after the built-in ones. | «yes» Пояснение: Symfony Messenger's pipeline supports custom middleware, and their order can be set relative to the built-in middleware.
Raw{"answer":"yes","explanation":"Symfony Messenger's pipeline supports custom middleware, and their order can be set relative to the built-in middleware."} | верно | messenger.bus.*.middleware в yaml; docs — Middleware. |
T28-L1 7.65 c | Symfony: versions | Symfony major releases come every two years, minor ones every six months (in May and November). | «yes» Пояснение: Symfony follows a release cycle where major versions are released every two years and minor versions every six months, with releases typically occurring in November and May.
Raw{"answer": "yes", "explanation": "Symfony follows a release cycle where major versions are released every two years and minor versions every six months, with releases typically occurring in November and May."} | верно | Стандартный релизный цикл: 8.0 — ноябрь 2025, 8.1 — май 2026, 8.2 — ноябрь 2026. |
T28-L2 3.97 c | Symfony: versions | What is the minimum PHP version required by Symfony 8? | «8.3» Пояснение: Symfony 8 requires at least PHP 8.3.
Raw{ ⏎ "answer": "8.3", ⏎ "explanation": "Symfony 8 requires at least PHP 8.3." ⏎ } | неверно верный: «8.4» | Symfony 8.0 поднял требование до PHP >= 8.4.1 (в vendor проекта: "php": ">=8.4.1"). |
T28-L3 3.87 c | Symfony: versions | Symfony 7.0 kept support for docblock annotations (validation, routes). | «no» Пояснение: Symfony 7.0 removed docblock annotation support in favor of PHP attributes.
Raw{"answer": "no", "explanation": "Symfony 7.0 removed docblock annotation support in favor of PHP attributes."} | верно | Наоборот: в 7.0 аннотации удалены — только PHP-атрибуты (#[Route], #[Assert\NotBlank]). |
T28-L4 30.49 c | Symfony: versions | AssetMapper manages CSS/JS without node or webpack — via importmap.php. | «yes» Пояснение: AssetMapper resolves CSS/JS through an importmap.php file, avoiding Node/webpack build tools.
Raw{"answer":"yes","explanation":"AssetMapper resolves CSS/JS through an importmap.php file, avoiding Node/webpack build tools."} | верно | symfony/asset-mapper (с 6.3, стандарт с 7.x); в проекте — importmap.php в корне и asset-mapper 8.1. |
T28-L5 9.83 c | Symfony: versions | Symfony 6.4 is a regular release without long-term support. | «yes» Пояснение: Symfony 6.4 is a standard (even minor) release that receives regular support until the end of the 6.x major version lifecycle, with no separate long-term support (LTS) designation.
Raw{"answer": "yes", "explanation": "Symfony 6.4 is a standard (even minor) release that receives regular support until the end of the 6.x major version lifecycle, with no separate long-term support (LTS) designation."} | неверно верный: «no» | Наоборот: 6.4 — LTS (расширенная поддержка); LTS выходит вместе с очередным мажором (6.4 — вместе с 7.0). |
T28-L6 7.72 c | Symfony: versions | When moving to a new Symfony major version, deprecations of the previous branch keep working — major releases do not remove them. | «no» Пояснение: Symfony major releases remove deprecations introduced in the previous major version.
Raw{"answer":"no","explanation":"Symfony major releases remove deprecations introduced in the previous major version."} | верно | Наоборот: мажорный релиз удаляет всё устаревшее (7.0 убрал деприкейшены 6.x, 8.0 — 7.x). |
T28-L7 2.52 c | Symfony: versions | Every Symfony major release is accompanied by an UPGRADE guide listing the changes. | «yes» Пояснение: Symfony major releases include an UPGRADE guide that documents the significant changes and required migration steps.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Symfony major releases include an UPGRADE guide that documents the significant changes and required migration steps." ⏎ } | верно | UPGRADE-7.0.md, UPGRADE-8.0.md в репозитории symfony/symfony. |
T28-L8 3.22 c | Symfony: versions | Which Symfony component manages assets and the importmap without node/webpack? | «symfony assetmapper» Пояснение: Symfony AssetMapper is the Symfony component for managing assets and importmaps without Node.js or Webpack.
Raw{ ⏎ "answer": "Symfony AssetMapper", ⏎ "explanation": "Symfony AssetMapper is the Symfony component for managing assets and importmaps without Node.js or Webpack." ⏎ } | верно | symfony/asset-mapper 8.1 — в проекте. |
T29-L1 132.21 c | Symfony: 8.2 and beyond | As of 2026-11-07, Symfony 8.2 has already been released. | «yes» Пояснение: Symfony 8.2 had already been released by November 7, 2026.
Raw{"answer": "yes", "explanation": "Symfony 8.2 had already been released by November 7, 2026."} | неверно верный: «no» | Наоборот: 8.2 ещё не выпущена — релиз в конце ноября 2026; последняя стабильная — 8.1. |
T29-L2 7.27 c | Symfony: 8.2 and beyond | As of 2026-11-07, Symfony 8.2 is scheduled for November 2026, following the usual six-month cycle. | «no» Пояснение: Following Symfony's six-month release cycle, Symfony 8.2 would be scheduled for May 2027, not November 2026.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "Following Symfony's six-month release cycle, Symfony 8.2 would be scheduled for May 2027, not November 2026." ⏎ } | неверно верный: «yes» | Политика релизов: 8.1 — май 2026, 8.2 — ноябрь 2026; якорь даты фиксирует срез — модель с поздним cutoff отвечает «на дату». |
T29-L3 46.0 c | Symfony: 8.2 and beyond | Which Symfony version comes after 8.1 (as of 2026-11-07)? | «8.2» Пояснение: The next Symfony minor version after 8.1 is 8.2.
Raw{"answer":"8.2","explanation":"The next Symfony minor version after 8.1 is 8.2."} | верно | 8.2 — следующий минорный релиз (ноябрь 2026); после его выхода проект переходит с 8.1.* на 8.2.*. |
T29-L4 1.94 c | Symfony: 8.2 and beyond | Symfony 8.2 is a major release requiring applications to be rewritten for new APIs. | «no» Пояснение: Major Symfony releases introduce breaking changes, but they do not require applications to be fully rewritten.
Raw{"answer": "no", "explanation": "Major Symfony releases introduce breaking changes, but they do not require applications to be fully rewritten."} | верно | Наоборот: 8.2 — минорный релиз; новые возможности без поломки обратной совместимости. Мажор — 9.0. |
T29-L5 26.83 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» Пояснение: 8.2 is a minor update within the PHP 8 major branch, so it is expected to preserve backward compatibility with 8.1 code.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "8.2 is a minor update within the PHP 8 major branch, so it is expected to preserve backward compatibility with 8.1 code." ⏎ } | верно | Политика Symfony: минорные релизы обратно совместимы; BC-break допустим только в мажорных. |
T29-L6 83.37 c | Symfony: 8.2 and beyond | Which minor version of the 8.x branch is released last, before Symfony 9.0? | «8.1» Пояснение: Symfony 8.1 is the latest 8.x minor version released before Symfony 9.0.
Raw{ ⏎ "answer": "8.1", ⏎ "explanation": "Symfony 8.1 is the latest 8.x minor version released before Symfony 9.0." ⏎ } | неверно верный: «8.4» | По циклу: 8.2 (ноя 2026), 8.3 (май 2027), 8.4 (ноя 2027, вместе с 9.0) — как 6.4 выходила вместе с 7.0. |
T29-L7 22.96 c | Symfony: 8.2 and beyond | Symfony 8.2 will require PHP 8.5 — you would have to upgrade PHP along with it. | «yes» Пояснение: Symfony 8.2 raises the minimum required PHP version to 8.5, so upgrading PHP is necessary.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Symfony 8.2 raises the minimum required PHP version to 8.5, so upgrading PHP is necessary." ⏎ } | неверно верный: «no» | Наоборот: минорные релизы не поднимают требования PHP; для всей ветки 8.x остаётся PHP >= 8.4. |
T29-L8 3.11 c | Symfony: 8.2 and beyond | Deprecations added in the 8.x branch will not be removed before Symfony 9.0. | «yes» Пояснение: Symfony’s deprecation policy states that deprecations introduced in the 8.x branch will be kept until 9.0.
Raw{"answer":"yes","explanation":"Symfony’s deprecation policy states that deprecations introduced in the 8.x branch will be kept until 9.0."} | верно | Политика: деприкейшены живут до следующего мажора; 9.0 — ноябрь 2027. |
T21-L1 1.27 c | Twig | Inside {{ }}, Twig allows calling arbitrary PHP code directly. | «no» Пояснение: Twig's {{ }} expression language is intentionally restricted and does not allow calling arbitrary PHP code for security reasons.
Raw{"answer":"no","explanation":"Twig's {{ }} expression language is intentionally restricted and does not allow calling arbitrary PHP code for security reasons."} | верно | Twig — DSL: только разрешённые окружением функции/фильтры; произвольный PHP не исполняется. |
T21-L2 1.04 c | Twig | By default, Twig auto-escapes printed variables. | «yes» Пояснение: Twig enables HTML auto-escaping by default for output variables.
Raw{"answer":"yes","explanation":"Twig enables HTML auto-escaping by default for output variables."} | верно | Autoescape включён по умолчанию; {{ '<b>' }} → <b>. Проверено на Twig 3.30. |
T21-L3 1.46 c | Twig | The Twig |e filter escapes a string for safe output in an HTML context. | «yes» Пояснение: The |e filter in Twig escapes output, and by default it uses the HTML context to safely escape special characters like &, <, >, etc.
Raw{"answer": "yes", "explanation": "The |e filter in Twig escapes output, and by default it uses the HTML context to safely escape special characters like &, <, >, etc."} | верно | |e ('html') по умолчанию; есть контексты js/url/css. От SQL-инъекций он не защищает — это задача подготовленных запросов Doctrine. |
T21-L4 11.02 c | Twig | Which filter from twig/intl-extra formats a number according to a locale? | «intl_numberformat» Пояснение: The twig/intl-extra filter intl_numberformat formats a number using a locale.
Raw{"answer":"intl_numberformat","explanation":"The twig/intl-extra filter intl_numberformat formats a number using a locale."} | неверно верный: «format_number» | |format_number(locale=...) из IntlExtension (twig/intl-extra есть в проекте). Проверено на Twig 3.30: 12345.6 → 12 345,6 (ru). |
T21-L5 2.1 c | Twig | The |raw filter disables auto-escaping for the value. | «yes» Пояснение: The |raw filter prevents escaping, allowing the value to be output as raw HTML.
Raw{"answer": "yes", "explanation": "The |raw filter prevents escaping, allowing the value to be output as raw HTML."} | верно | {{ x|raw }} выводит HTML как есть; опасно с пользовательскими данными. Проверено на Twig 3.30. |
T21-L6 1.07 c | Twig | In Twig, {{ }} prints an expression value, while {% %} executes tags — conditions, loops, set. | «yes» Пояснение: In Twig, {{ }} outputs the value of an expression, while {% %} executes structural tags such as conditions, loops, and set statements.
Raw{"answer": "yes", "explanation": "In Twig, {{ }} outputs the value of an expression, while {% %} executes structural tags such as conditions, loops, and set statements."} | верно | Два блока синтаксиса Twig: вывод (echo) против логики. |
T21-L7 0.87 c | Twig | In Twig you cannot declare a variable inside a template — values only come from the controller. | «no» Пояснение: Twig allows variables to be assigned inside a template using {% set %}.
Raw{"answer": "false", "explanation": "Twig allows variables to be assigned inside a template using {% set %}."} | верно | {% set y = ... %} объявляет переменную в шаблоне. Проверено на Twig 3.30. |
T21-L8 0.85 c | Twig | Which Twig function dumps the debug structure of a variable (array, object)? | «dump» Пояснение: In Twig, the `dump()` function displays the debug structure of a variable, similar to PHP's var_dump().
Raw{"answer": "dump", "explanation": "In Twig, the `dump()` function displays the debug structure of a variable, similar to PHP's var_dump()."} | верно | {{ dump(x) }} (DebugExtension; в Symfony доступна в dev-окружении). |
T24-L1 0.95 c | Bootstrap | Bootstrap is a CSS/JS library of ready-made UI components, not an SPA framework. | «yes» Пояснение: Bootstrap is primarily a front-end UI library providing CSS and JavaScript components, not a single-page application framework.
Raw{"answer": "yes", "explanation": "Bootstrap is primarily a front-end UI library providing CSS and JavaScript components, not a single-page application framework."} | верно | Компоненты и утилиты поверх вашего HTML; SPA-фреймворки (React/Vue) — другой класс инструментов. В проекте vendored 5.3.3. |
T24-L2 3.36 c | Bootstrap | Which Bootstrap class gives a responsive container with a fixed max width per breakpoint? | «container» Пояснение: The .container class in Bootstrap provides a responsive container whose max-width is fixed at each breakpoint (sm, md, lg, xl, xxl).
Raw{"answer": "container", "explanation": "The .container class in Bootstrap provides a responsive container whose max-width is fixed at each breakpoint (sm, md, lg, xl, xxl)."} | верно | .container (фиксированная макс-ширина по брейкпоинтам) vs .container-fluid (на всю ширину). |
T24-L3 1.57 c | Bootstrap | The Bootstrap grid is built on CSS floats and splits a row into 16 columns. | «no» Пояснение: The Bootstrap grid uses 12 columns (not 16), and modern Bootstrap (v4+) uses CSS Flexbox rather than CSS floats.
Raw{"answer": "no", "explanation": "The Bootstrap grid uses 12 columns (not 16), and modern Bootstrap (v4+) uses CSS Flexbox rather than CSS floats."} | верно | Наоборот: flexbox (с Bootstrap 4) и 12 колонок; float-сетка — это Bootstrap 3. |
T24-L4 3.89 c | Bootstrap | Bootstrap's named breakpoints (the infix used in class names) are sm, md, lg, xl, xxl — five of them. | «yes» Пояснение: In Bootstrap 5, the class-name prefixes (infixes) are exactly sm, md, lg, xl, and xxl, making five in total (the base 'xs' range is covered by classes with no prefix).
Raw{"answer":"yes","explanation":"In Bootstrap 5, the class-name prefixes (infixes) are exactly sm, md, lg, xl, and xxl, making five in total (the base 'xs' range is covered by classes with no prefix)."} | верно | Тиров всего шесть: xs (без инфикса) + пять именованных (576/768/992/1200/1400 px). |
T24-L5 1.54 c | Bootstrap | Utilities like .mt-3 or .px-2 use the spacing scale: the number is a multiple of $spacer. | «yes» Пояснение: In Bootstrap, utilities like .mt-3 and .px-2 use spacing values that are multiples of the $spacer variable.
Raw{"answer":"yes","explanation":"In Bootstrap, utilities like .mt-3 and .px-2 use spacing values that are multiples of the $spacer variable."} | неверно верный: «no» | Spacing utilities; $spacer = 1rem. |
T24-L6 1.17 c | Bootstrap | Which Bootstrap 5 data attribute enables an interactive component (e.g. dropdown) on an element? | «data-bs-toggle» Пояснение: In Bootstrap 5, the data-bs-toggle attribute is used to activate interactive components such as dropdowns, modals, tooltips, etc. on an element.
Raw{"answer": "data-bs-toggle", "explanation": "In Bootstrap 5, the data-bs-toggle attribute is used to activate interactive components such as dropdowns, modals, tooltips, etc. on an element."} | верно | data-bs-toggle="dropdown" и т.п.; в Bootstrap 4 атрибут назывался data-toggle. |
T24-L7 1.31 c | Bootstrap | Bootstrap 5 components work without jQuery — in plain vanilla JS. | «yes» Пояснение: Bootstrap 5 removed its jQuery dependency and uses vanilla JavaScript (ES6+) along with Popper.js for its interactive components.
Raw{"answer": "yes", "explanation": "Bootstrap 5 removed its jQuery dependency and uses vanilla JavaScript (ES6+) along with Popper.js for its interactive components."} | верно | jQuery удалён в Bootstrap 5.0: data-bs-* атрибуты и JS API. В проекте vendored 5.3.3. |
T24-L8 3.02 c | Bootstrap | Dark mode in Bootstrap is enabled with a .dark class on the root element. | «yes» Пояснение: In Bootstrap, adding the .dark class to the root HTML element enables dark mode.
Raw{"answer": "yes", "explanation": "In Bootstrap, adding the .dark class to the root HTML element enables dark mode."} | неверно верный: «no» | Наоборот: тема включается атрибутом data-bs-theme="dark" (Color modes, с 5.3); класса .dark не существует. В проекте 5.3.3. |
T14-L1 1.43 c | Doctrine | Doctrine ORM creates database tables on the fly the first time an entity is used at runtime. | «no» Пояснение: Doctrine ORM maps entities to existing database tables; it does not automatically create tables at runtime — you must use a schema tool like Doctrine Migrations or the SchemaManager to generate/alter the database schema.
Raw{"answer":"no","explanation":"Doctrine ORM maps entities to existing database tables; it does not automatically create tables at runtime — you must use a schema tool like Doctrine Migrations or the SchemaManager to generate/alter the database schema."} | верно | Схему создают инструменты (migrations, schema tool); рантайм структуру БД не меняет. |
T14-L2 1.17 c | Doctrine | Which EntityManager method marks a new object as managed without executing SQL until flush()? | «persist()» Пояснение: The EntityManager::persist() method marks a new object as managed (in the managed state) without executing any SQL until a flush() is called.
Raw{"answer": "persist()", "explanation": "The EntityManager::persist() method marks a new object as managed (in the managed state) without executing any SQL until a flush() is called."} | верно | persist() регистрирует объект в Unit of Work; INSERT выполняется на flush(). |
T14-L3 1.33 c | Doctrine | In Doctrine ORM 3, the EntityManager::merge() method exists and makes the passed object managed. | «yes» Пояснение: EntityManager::merge() exists in Doctrine ORM 3 and makes the passed object managed.
Raw{"answer":"yes","explanation":"EntityManager::merge() exists in Doctrine ORM 3 and makes the passed object managed."} | неверно верный: «no» | В ORM 3 merge() удалён (в vendor проекта 3.7.6 метода нет); в Doctrine 2.x merge() возвращал управляемую копию. Версия зафиксирована — ORM 3. |
T14-L4 1.19 c | Doctrine | DQL queries are written in terms of entities and their fields, not tables and columns. | «yes» Пояснение: DQL is an object-oriented query language that references entities and their mapped fields rather than database tables and columns.
Raw{"answer": "yes", "explanation": "DQL is an object-oriented query language that references entities and their mapped fields rather than database tables and columns."} | верно | Doctrine транслирует DQL в SQL; docs — DQL (Doctrine Query Language). |
T14-L5 6.05 c | Doctrine | What does $repository->find(999) return when no record with id 999 exists? | «null» Пояснение: The repository’s find method returns null when no matching record exists.
Raw{ ⏎ "answer": "null", ⏎ "explanation": "The repository’s find method returns null when no matching record exists." ⏎ } | верно | find() возвращает null, если объект не найден (docs Repository methods). |
T14-L6 13.32 c | Doctrine | DoctrineBundle in Symfony automatically calls flush() at the end of every request. | «yes» Пояснение: DoctrineBundle includes a subscriber that flushes the entity manager at the end of each request by default.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "DoctrineBundle includes a subscriber that flushes the entity manager at the end of each request by default." ⏎ } | неверно верный: «no» | Авто-flush нет — flush() зовёт разработчик; незакрытая транзакция в конце запроса откатывается. |
T14-L7 1.57 c | Doctrine | For a managed entity, changing a property is enough: flush() commits the change without an explicit persist() — the Unit of Work tracks changes. | «yes» Пояснение: Doctrine tracks changes to managed entities, so flush() persists property modifications without needing another persist().
Raw{"answer": "yes", "explanation": "Doctrine tracks changes to managed entities, so flush() persists property modifications without needing another persist()."} | верно | Dirty checking сравнивает снимки свойств; persist нужен только новым/отсоединённым объектам. |
T14-L8 0.96 c | Doctrine | remove() executes the SQL DELETE immediately, without waiting for flush(). | «no» Пояснение: Doctrine's remove() only marks the entity for deletion in the unit of work; the SQL DELETE is executed when flush() is called.
Raw{"answer":"no","explanation":"Doctrine's remove() only marks the entity for deletion in the unit of work; the SQL DELETE is executed when flush() is called."} | верно | remove() планирует удаление в Unit of Work; DELETE выполняется на flush() (docs — Deleting Objects). |
T15-L1 2.07 c | PostgreSQL | PostgreSQL uses MVCC, therefore readers block writers and writers block readers. | «no» Пояснение: PostgreSQL's MVCC generally allows readers and writers to proceed concurrently; readers do not block writers and writers do not block readers.
Raw{"answer":"no","explanation":"PostgreSQL's MVCC generally allows readers and writers to proceed concurrently; readers do not block writers and writers do not block readers."} | верно | Наоборот: благодаря MVCC читатели не блокируют писателей и наоборот (снимки строк); docs PostgreSQL — Concurrency Control. |
T15-L2 1.53 c | PostgreSQL | Which SQL command shows a query's execution plan without executing the query? | «explain» Пояснение: The EXPLAIN command displays the query's execution plan (query optimization path) without actually running the query.
Raw{"answer": "EXPLAIN", "explanation": "The EXPLAIN command displays the query's execution plan (query optimization path) without actually running the query."} | верно | EXPLAIN без ANALYZE только строит план; проверено на PostgreSQL 17.7. |
T15-L3 1.87 c | PostgreSQL | SERIAL and GENERATED ... AS IDENTITY are just two names for the same mechanism. | «no» Пояснение: SERIAL is typically a database shorthand that includes extra constraints like auto-increment/sequence defaults, while GENERATED AS IDENTITY is a specific SQL identity mechanism and not simply another name for SERIAL.
Raw{"answer":"no","explanation":"SERIAL is typically a database shorthand that includes extra constraints like auto-increment/sequence defaults, while GENERATED AS IDENTITY is a specific SQL identity mechanism and not simply another name for SERIAL."} | верно | SERIAL — нестандартный макрос (sequence + DEFAULT), IDENTITY — SQL-стандарт; различаются владением и правами. Оба есть в PG 17 (проверено). |
T15-L4 1.96 c | PostgreSQL | By default, a PostgreSQL UNIQUE constraint allows only one row with NULL in the column. | «no» Пояснение: By default, PostgreSQL UNIQUE constraints allow multiple rows with NULL values, since NULL is considered unknown and not equal to NULL; only in PostgreSQL 12+ can you specify the behavior explicitly (e.g., `DISTINCT NULLS NOT DISTINCT`), but the default remains to allow multiple NULLs.
Raw{"answer": "no", "explanation": "By default, PostgreSQL UNIQUE constraints allow multiple rows with NULL values, since NULL is considered unknown and not equal to NULL; only in PostgreSQL 12+ can you specify the behavior explicitly (e.g., `DISTINCT NULLS NOT DISTINCT`), but the default remains to allow multiple NULLs."} | верно | Наоборот: NULLS DISTINCT по умолчанию — несколько NULL допустимы; NULLS NOT DISTINCT — опция с PG 15. Проверено на PG 17.7. |
T15-L5 0.88 c | PostgreSQL | Which PostgreSQL aggregate function concatenates strings with a separator? | «string_agg» Пояснение: PostgreSQL provides string_agg(expression, separator) as an aggregate function to concatenate strings with a specified separator.
Raw{"answer":"string_agg","explanation":"PostgreSQL provides string_agg(expression, separator) as an aggregate function to concatenate strings with a specified separator."} | верно | string_agg(значение, разделитель); проверено на PostgreSQL 17.7. |
T15-L6 1.89 c | PostgreSQL | Plain VACUUM returns the space occupied by dead tuples to the operating system. | «no» Пояснение: Plain VACUUM only makes dead-tuple space available for reuse within the table; it does not return that space to the operating system (only VACUUM FULL does).
Raw{"answer": "no", "explanation": "Plain VACUUM only makes dead-tuple space available for reuse within the table; it does not return that space to the operating system (only VACUUM FULL does)."} | верно | VACUUM помечает место для переиспользования внутри таблицы; ОС его возвращает только VACUUM FULL (с эксклюзивной блокировкой). |
T15-L7 1.72 c | PostgreSQL | Which keyword in a window function definition partitions rows into groups the function is computed over? | «partition by» Пояснение: The PARTITION BY clause in a window function defines how rows are partitioned into groups for computation.
Raw{ ⏎ "answer": "PARTITION BY", ⏎ "explanation": "The PARTITION BY clause in a window function defines how rows are partitioned into groups for computation." ⏎ } | верно | OVER (PARTITION BY ...); проверено на PostgreSQL 17.7. |
T15-L8 1.58 c | PostgreSQL | The READ COMMITTED isolation level protects against non-repeatable reads. | «no» Пояснение: READ COMMITTED prevents dirty reads but does not prevent non-repeatable reads, since another transaction can commit changes between two reads.
Raw{"answer": "no", "explanation": "READ COMMITTED prevents dirty reads but does not prevent non-repeatable reads, since another transaction can commit changes between two reads."} | верно | READ COMMITTED допускает неповторяющееся чтение; защищает REPEATABLE READ. Проверено: SHOW transaction_isolation → read committed. |
T17-L1 1.14 c | PostgreSQL: transactions and indexes | By default, PostgreSQL wraps each single SQL statement in its own implicit transaction (autocommit). | «yes» Пояснение: PostgreSQL operates in autocommit mode by default, so each SQL statement is committed in its own implicit transaction.
Raw{"answer": "yes", "explanation": "PostgreSQL operates in autocommit mode by default, so each SQL statement is committed in its own implicit transaction."} | верно | Без BEGIN каждый оператор коммитится сам; docs PostgreSQL — Transactions. Проверено на PG 17. |
T17-L2 0.92 c | PostgreSQL: transactions and indexes | Which SQL command ends a transaction, committing all its changes? | «commit» Пояснение: The COMMIT SQL command ends a transaction and makes all changes permanent.
Raw{"answer": "COMMIT", "explanation": "The COMMIT SQL command ends a transaction and makes all changes permanent."} | верно | COMMIT (END — синоним). Проверено на PG 17. |
T17-L3 1.37 c | PostgreSQL: transactions and indexes | Indexes speed up more than SELECT: UPDATE and DELETE with a search on an indexed column benefit too. | «yes» Пояснение: Indexes can speed up UPDATE and DELETE when they use the indexed column to locate rows.
Raw{"answer":"yes","explanation":"Indexes can speed up UPDATE and DELETE when they use the indexed column to locate rows."} | верно | Поиск строк для изменения идёт по индексу; docs PostgreSQL — Indexes. |
T17-L4 0.81 c | PostgreSQL: transactions and indexes | To roll back part of the statements inside a transaction, PostgreSQL uses SAVEPOINT. | «yes» Пояснение: SAVEPOINT lets you roll back to a specific point within a transaction, undoing only part of the transaction's work.
Raw{"answer":"yes","explanation":"SAVEPOINT lets you roll back to a specific point within a transaction, undoing only part of the transaction's work."} | верно | SAVEPOINT name; ROLLBACK TO name — частичный откат без отмены всей транзакции. Проверено на PG 17. |
T17-L5 1.16 c | PostgreSQL: transactions and indexes | EXPLAIN ANALYZE shows the query plan without executing the query. | «no» Пояснение: EXPLAIN ANALYZE actually executes the query and shows the execution plan with actual timing and statistics.
Raw{"answer": "no", "explanation": "EXPLAIN ANALYZE actually executes the query and shows the execution plan with actual timing and statistics."} | верно | Наоборот: ANALYZE реально выполняет запрос (с побочными эффектами!) и показывает фактические времена узлов; план без выполнения — plain EXPLAIN. |
T17-L6 0.97 c | PostgreSQL: transactions and indexes | Which PostgreSQL extension adds vector types and indexes for embedding search? | «pgvector» Пояснение: pgvector is a PostgreSQL extension that provides vector data types and similarity indexes (HNSW and IVFFLAT) for embedding search.
Raw{"answer": "pgvector", "explanation": "pgvector is a PostgreSQL extension that provides vector data types and similarity indexes (HNSW and IVFFLAT) for embedding search."} | верно | CREATE EXTENSION vector (проект pgvector; в проекте образ pgvector/pgvector:pg17). |
T17-L7 1.09 c | PostgreSQL: transactions and indexes | A partial index (CREATE INDEX ... WHERE ...) is built only over rows satisfying the condition. | «yes» Пояснение: A partial index only stores entries for rows that satisfy the WHERE condition.
Raw{"answer": "yes", "explanation": "A partial index only stores entries for rows that satisfy the WHERE condition."} | верно | docs PostgreSQL — Partial Indexes; типичный кейс — индекс по «активным» записям. |
T17-L8 4.38 c | PostgreSQL: transactions and indexes | The SERIALIZABLE level in PostgreSQL is implemented by locking the rows a transaction reads. | «yes» Пояснение: PostgreSQL implements the SERIALIZABLE isolation level by locking rows that a transaction reads to prevent conflicting transactions from accessing them.
Raw{"answer": "yes", "explanation": "PostgreSQL implements the SERIALIZABLE isolation level by locking rows that a transaction reads to prevent conflicting transactions from accessing them."} | неверно верный: «no» | SSI (Serializable Snapshot Isolation): предикатные блокировки на снимках, не блокировки прочитанных строк; docs PostgreSQL. |
T19-L1 0.86 c | HTTP and REST API | HTTP status 201 means the request resulted in a new resource being created. | «yes» Пояснение: HTTP 201 indicates that the request succeeded and a new resource was created.
Raw{"answer":"yes","explanation":"HTTP 201 indicates that the request succeeded and a new resource was created."} | верно | 201 Created; обычно на POST, часто с Location; RFC 9110. |
T19-L2 1.85 c | HTTP and REST API | Which HTTP status means a successful request with an empty response body (e.g. after DELETE)? | «204» Пояснение: HTTP 204 No Content indicates a successful response with an intentionally empty body, which is the standard choice after a DELETE operation.
Raw{"answer": 204, "explanation": "HTTP 204 No Content indicates a successful response with an intentionally empty body, which is the standard choice after a DELETE operation."} | верно | 204 No Content; RFC 9110. |
T19-L3 1.39 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 an idempotent method.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "The HTTP specification defines DELETE as an idempotent method." ⏎ } | верно | RFC 9110: DELETE идемпотентен (как PUT); идемпотентность ≠ безопасность — ресурс удаляется при первом вызове. |
T19-L4 1.31 c | HTTP and REST API | The Access-Control-Allow-Origin header is sent by the client so that the server agrees to accept requests from another origin. | «no» Пояснение: Access-Control-Allow-Origin is a response header sent by the server, not by the client.
Raw{"answer":"no","explanation":"Access-Control-Allow-Origin is a response header sent by the server, not by the client."} | верно | Наоборот: заголовок шлёт СЕРВЕР в ответе, разрешая браузеру cross-origin запрос (CORS); в проекте nelmio/cors-bundle. |
T19-L5 1.14 c | HTTP and REST API | Status 429 Too Many Requests is used when a client exceeds a rate limit. | «yes» Пояснение: HTTP status 429 Too Many Requests is returned when a client exceeds a rate limit.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "HTTP status 429 Too Many Requests is returned when a client exceeds a rate limit." ⏎ } | верно | 429 (+ Retry-After); RFC 6585. В проекте symfony/rate-limiter. |
T19-L6 1.05 c | HTTP and REST API | 5xx codes mean a client error, while 4xx means a server-side error. | «no» Пояснение: It is the opposite: 4xx codes indicate client errors and 5xx codes indicate server-side errors.
Raw{"answer": "no", "explanation": "It is the opposite: 4xx codes indicate client errors and 5xx codes indicate server-side errors."} | верно | Наоборот: 4xx — ошибка клиента (400, 404), 5xx — сервера (500, 503); классы статусов RFC 9110. |
T19-L7 0.68 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 36.54 c | HTTP and REST API | PATCH is not required to be idempotent per RFC 5789, unlike PUT. | «yes» Пояснение: PATCH is not required to be idempotent; its idempotency depends on the media type, unlike PUT.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "PATCH is not required to be idempotent; its idempotency depends on the media type, unlike PUT." ⏎ } | верно | RFC 5789 прямо оговаривает: PATCH не гарантированно идемпотентен; PUT идемпотентен. |
T20-L1 2.17 c | Security and OAuth | Checking a password by comparing its hash to the stored hash with a plain == is sufficient. | «no» Пояснение: Using == exposes the comparison to timing attacks; PHP's hash_equals() should be used for constant-time comparison of hashes.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "Using == exposes the comparison to timing attacks; PHP's hash_equals() should be used for constant-time comparison of hashes." ⏎ } | верно | Нужна постоянновременная проверка (password_verify) — timing-атаки; соль и алгоритм уже внутри хеша. |
T20-L2 1.26 c | Security and OAuth | A CSRF token is issued by the server (bound to the session) and verified server-side on unsafe requests (POST etc.). | «yes» Пояснение: CSRF tokens are server-generated, typically tied to the user's session, and validated by the server on state-changing requests to prevent cross-site request forgery.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "CSRF tokens are server-generated, typically tied to the user's session, and validated by the server on state-changing requests to prevent cross-site request forgery." ⏎ } | верно | symfony/security-csrf в проекте; защита от подделки межсайтовой формы. |
T20-L3 0.88 c | Security and OAuth | Which HTTP header enables the CSP (Content Security Policy) policy? | «content-security-policy» Пояснение: The Content-Security-Policy HTTP header is used to define a Content Security Policy.
Raw{"answer":"Content-Security-Policy","explanation":"The Content-Security-Policy HTTP header is used to define a Content Security Policy."} | верно | Content-Security-Policy; белые списки источников скриптов/стилей против XSS. |
T20-L4 1.46 c | Security and OAuth | OAuth 2.0 is an authentication protocol: the access token tells you who the user is. | «no» Пояснение: OAuth 2.0 is primarily an authorization framework, and the access token is used to access resources, not necessarily to identify the user.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "OAuth 2.0 is primarily an authorization framework, and the access token is used to access resources, not necessarily to identify the user." ⏎ } | верно | OAuth 2.0 — авторизация/делегирование доступа; аутентификацию добавляет OpenID Connect. В проекте knpuniversity/oauth2-client-bundle (yandex/github/google). |
T20-L5 0.96 c | Security and OAuth | XSS is prevented by validating input on the server before writing it to the database. | «no» Пояснение: XSS is primarily prevented by encoding/escaping output based on context, not just by validating input before storing it in a database.
Raw{"answer":"no","explanation":"XSS is primarily prevented by encoding/escaping output based on context, not just by validating input before storing it in a database."} | верно | XSS лечится контекстным экранированием НА ВЫВОДЕ (Twig autoescape, CSP); валидация ввода не покрывает все контексты вывода. |
T20-L6 1.48 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» Пояснение: The OAuth 2.0 authorization code flow sends the 'code' parameter to the redirect_uri, which is exchanged for an access token.
Raw{"answer": "code", "explanation": "The OAuth 2.0 authorization code flow sends the 'code' parameter to the redirect_uri, which is exchanged for an access token."} | верно | Параметр code; обмен на токен POST-ом на /token с client_secret. |
T20-L7 0.81 c | Security and OAuth | A refresh token lives longer than an access token and allows obtaining a new access token without the user logging in again. | «yes» Пояснение: Refresh tokens are typically long-lived credentials used to obtain new access tokens without requiring the user to authenticate again.
Raw{"answer": "yes", "explanation": "Refresh tokens are typically long-lived credentials used to obtain new access tokens without requiring the user to authenticate again."} | верно | Стандартная схема OAuth/OIDC: короткий access + длинный refresh. |
T20-L8 1.35 c | Security and OAuth | A password salt must be kept secret: without it the hash cannot be verified. | «no» Пояснение: Password salts are typically stored with the hash rather than kept secret.
Raw{"answer":"no","explanation":"Password salts are typically stored with the hash rather than kept secret."} | верно | Соль хранится открыто (password_hash включает её в строку хеша); секретность соли не нужна. |
T18-L1 143.11 c | Testing: PHPUnit | PHPUnit runs test methods of any class — extending TestCase is not required. | «no» Пояснение: PHPUnit's default test discovery recognizes test methods only in classes that extend PHPUnit\Framework\TestCase.
Raw{"answer":"no","explanation":"PHPUnit's default test discovery recognizes test methods only in classes that extend PHPUnit\\Framework\\TestCase."} | верно | Тестом считается метод класса, наследующего TestCase (PHPUnit 10). |
T18-L2 2.89 c | Testing: PHPUnit | In PHPUnit, setUp() runs once before all tests of the class. | «no» Пояснение: setUp() runs before each test method, not once for the whole class.
Raw{"answer": "no", "explanation": "setUp() runs before each test method, not once for the whole class."} | верно | setUp() — перед КАЖДЫМ тестом; один раз на класс — setUpBeforeClass(). Проверено живым счётчиком на PHPUnit 10.5. |
T18-L3 0.89 c | Testing: PHPUnit | A data provider lets a test run with exactly one set of arguments. | «no» Пояснение: A data provider allows a test to be run with multiple sets of arguments, not exactly one.
Raw{"answer": "no", "explanation": "A data provider allows a test to be run with multiple sets of arguments, not exactly one."} | верно | Наоборот: наборов может быть сколько угодно — тест выполняется по разу на каждый. Проверено на PHPUnit 10.5 (#[DataProvider]). |
T18-L4 2.26 c | Testing: PHPUnit | Which PHPUnit method declares an expectation that an exception of a given class is thrown? | «expectexception» Пояснение: PHPUnit's expectException method declares an expectation that an exception of a given class will be thrown.
Raw{"answer": "expectException", "explanation": "PHPUnit's expectException method declares an expectation that an exception of a given class will be thrown."} | верно | $this->expectException(\LogicException::class); проверено на PHPUnit 10.5. |
T18-L5 1.37 c | Testing: PHPUnit | In PHPUnit, a stub verifies which methods were called on it, while a mock only returns data. | «no» Пояснение: Stubs return configured data, while mocks can also verify method calls.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "Stubs return configured data, while mocks can also verify method calls." ⏎ } | верно | Наоборот: стаб подставляет данные, мок проверяет взаимодействия (createStub/createMock); docs PHPUnit — Test Doubles. |
T18-L6 4.25 c | Testing: PHPUnit | In PHPUnit 10+, the recommended way to pass data to a test is the #[DataProvider] attribute (the @dataProvider annotation is deprecated). | «yes» Пояснение: In PHPUnit 10+, the #[DataProvider] attribute is the recommended replacement for the deprecated @dataProvider annotation.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "In PHPUnit 10+, the #[DataProvider] attribute is the recommended replacement for the deprecated @dataProvider annotation." ⏎ } | верно | Аннотация ещё парсится в PHPUnit 10/11 (AnnotationParser в 10.5.66), удаление — в 12; атрибут — стандарт. |
T18-L7 4.59 c | Testing: PHPUnit | PHPUnit does not allow one test to depend on the result of another. | «yes» Пояснение: PHPUnit enforces test independence, and while older versions had a deprecated dependsOn() method for ordering, modern PHPUnit removed it entirely and does not support one test depending on another's result.
Raw{"answer": "yes", "explanation": "PHPUnit enforces test independence, and while older versions had a deprecated dependsOn() method for ordering, modern PHPUnit removed it entirely and does not support one test depending on another's result."} | неверно верный: «no» | Зависимости есть: #[Depends] — зависимый тест не запустится, еслиProducer упал. |
T18-L8 3.02 c | Testing: PHPUnit | Which PHPUnit command-line option makes tests run in random order? | «--random-tests» Пояснение: The PHPUnit CLI option --random-tests runs tests in a random order.
Raw{"answer":"--random-tests","explanation":"The PHPUnit CLI option --random-tests runs tests in a random order."} | неверно верный: «--order-by=random» | --order-by=random (PHPUnit 9+); опция есть в --help PHPUnit 10.5 (проектная). |
T01-L9 3.42 c | Syntax and operators | What does this code output?
```php
echo intdiv(7, 2) . intdiv(-7, 2);
``` | «3-4» Пояснение: intdiv(7, 2) returns 3 and intdiv(-7, 2) returns -4, and concatenating them produces the string "3-4".
Raw{ ⏎ "answer": "3-4", ⏎ "explanation": "intdiv(7, 2) returns 3 and intdiv(-7, 2) returns -4, and concatenating them produces the string \"3-4\"." ⏎ } | неверно верный: «3-3» | intdiv truncates toward zero: intdiv(-7, 2) = -3, not -4. |
T01-L10 3.94 c | Syntax and operators | What does this code output?
```php
echo -3 ** 2;
``` | «-9» Пояснение: In PHP, the exponentiation operator ** has higher precedence than the unary minus, so -3 ** 2 is evaluated as -(3 ** 2).
Raw{"answer": -9, "explanation": "In PHP, the exponentiation operator ** has higher precedence than the unary minus, so -3 ** 2 is evaluated as -(3 ** 2)."} | верно | ** is right-associative and binds tighter than unary minus: -(3²). |
T02-L9 2.68 c | Types and comparisons | What does this code output?
```php
echo '1e1' == '10' ? 'true' : 'false';
``` | «true» Пояснение: Both '1e1' and '10' are numeric strings, so loose equality compares them as numbers, and 10.0 equals 10.0.
Raw{ ⏎ "answer": "true", ⏎ "explanation": "Both '1e1' and '10' are numeric strings, so loose equality compares them as numbers, and 10.0 equals 10.0." ⏎ } | верно | Both strings are numeric — compared as numbers: 10 == 10. |
T02-L10 1.48 c | Types and comparisons | What does this code output?
```php
switch ('a') {
case 0: echo 'zero'; break;
default: echo 'other';
}
``` | «other» Пояснение: The switch value 'a' does not match case 0, so the default branch executes.
Raw{ ⏎ "answer": "other", ⏎ "explanation": "The switch value 'a' does not match case 0, so the default branch executes." ⏎ } | верно | PHP 8: 'a' == 0 → false (used to be true) — default fires. |
T03-L9 15.17 c | Strings | What does this code output?
```php
echo strtr('abc', ['a' => '1', 'ab' => '2']);
``` | «2c» Пояснение: strtr() replaces longest matching keys first, so 'ab' becomes '2'.
Raw{ ⏎ "answer": "2c", ⏎ "explanation": "strtr() replaces longest matching keys first, so 'ab' becomes '2'." ⏎ } | верно | strtr with an array prefers the longest matching key. |
T03-L10 1.81 c | Strings | What does this code output?
```php
echo '[' . substr('hello', -10) . ']';
``` | «[hello]» Пояснение: substr('hello', -10) returns the entire string because a negative start beyond the string length is treated as the beginning.
Raw{"answer":"[hello]","explanation":"substr('hello', -10) returns the entire string because a negative start beyond the string length is treated as the beginning."} | верно | A negative start beyond the string is clamped to the beginning. |
T04-L9 1.42 c | Arrays | What does this code output?
```php
$a = ['k' => 1, 'n' => 2];
$b = ['k' => 9, 'm' => 3];
echo implode(',', array_keys($a + $b));
``` | «k,n,m» Пояснение: The + operator merges the arrays keeping left-side values for duplicate keys, so the keys are k, n, and m.
Raw{ ⏎ "answer": "k,n,m", ⏎ "explanation": "The + operator merges the arrays keeping left-side values for duplicate keys, so the keys are k, n, and m." ⏎ } | верно | The + operator: on duplicate string keys the left array wins. |
T04-L10 3.12 c | Arrays | What does this code output?
```php
$a = [[1, 'x', 2], [2, 'y', 1], [3, 'z', 2]];
usort($a, fn($p, $q) => $p[2] <=> $q[2]);
echo implode('', array_column($a, 1));
``` | «yxz» Пояснение: The usort sorts by the third element (index 2): [2,'y',1] (1) first, then [1,'x',2] and [3,'z',2] (both 2) in their original relative order; array_column with index 1 extracts 'y','x','z' which implode to 'yxz'.
Raw{"answer": "yxz", "explanation": "The usort sorts by the third element (index 2): [2,'y',1] (1) first, then [1,'x',2] and [3,'z',2] (both 2) in their original relative order; array_column with index 1 extracts 'y','x','z' which implode to 'yxz'."} | верно | Sorts are stable since 8.0: x and z keep their order on a tie. |
T05-L10 2.49 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» Пояснение: Spreading the array passes named arguments b=1 and a=5, so f returns 5 - 1 = 4.
Raw{ ⏎ "answer": 4, ⏎ "explanation": "Spreading the array passes named arguments b=1 and a=5, so f returns 5 - 1 = 4." ⏎ } | верно | String keys of a spread array become named arguments. |
T05-L9 16.0 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();
``` | «parseerror» Пояснение: The spread operator '...' must be followed by a variable or expression (e.g., '$p->g(...$arr)'), so '$p->g(...)' is a syntax error.
Raw{"answer": "ParseError", "explanation": "The spread operator '...' must be followed by a variable or expression (e.g., '$p->g(...$arr)'), so '$p->g(...)' is a syntax error."} | неверно верный: «3» | First-class callable syntax binds $this at creation time. |
T06-L9 1.3 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 when the method is called on an instance of B it returns the class name B.
Raw{"answer": "B", "explanation": "static::class uses late static binding, so when the method is called on an instance of B it returns the class name B."} | верно | Late static binding: static::class is the receiver's class. |
T06-L10 23.5 c | OOP: classes and inheritance | What does this code output on PHP 8.5?
```php
class C
{
public int $x = 0 {
set { $this->x = $value * 2; }
}
}
$c = new C;
$c->x = 5;
echo $c->x;
``` | «10» Пояснение: The set hook doubles the assigned value and stores it without recursive hook invocation, so reading the property outputs 10.
Raw{"answer": 10, "explanation": "The set hook doubles the assigned value and stores it without recursive hook invocation, so reading the property outputs 10."} | верно | Inside the set hook, $this->x writes the backing store (no recursion): 5*2. |
T07-L9 24.69 c | Interfaces, traits, enum | What does this code output?
```php
trait TA
{
public function f(): string { return 'A'; }
}
trait TB
{
public function f(): string { return 'B'; }
}
class TC
{
use TA, TB { TB::f insteadof TA; TA::f as g; }
}
echo (new TC)->f() . (new TC)->g();
``` | «ba» Пояснение: The trait conflict resolution makes f come from TB, while g aliases TA's f, so f() returns B and g() returns A.
Raw{ ⏎ "answer": "BA", ⏎ "explanation": "The trait conflict resolution makes f come from TB, while g aliases TA's f, so f() returns B and g() returns A." ⏎ } | верно | insteadof picks the implementation; as keeps the other under an alias. |
T07-L10 10.18 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;
``` | «1» Пояснение: Static properties declared in a PHP trait are shared by all classes using that trait, so CY::$n reflects CX::$n = 1.
Raw{ ⏎ "answer": 1, ⏎ "explanation": "Static properties declared in a PHP trait are shared by all classes using that trait, so CY::$n reflects CX::$n = 1." ⏎ } | неверно верный: «0» | A trait's static property is copied into each consuming class. |
T08-L10 2.3 c | Exceptions and errors | What does this code output?
```php
function f(): int
{
try { return 1; } finally { return 2; }
}
echo f();
``` | «2» Пояснение: A return in the finally block overrides the return in the try block.
Raw{"answer": 2, "explanation": "A return in the finally block overrides the return in the try block."} | верно | A return in finally overrides the return from try. |
T08-L9 2.3 c | Exceptions and errors | What does this code output?
```php
try {
try {
throw new RuntimeException('first');
} finally {
throw new LogicException('second');
}
} catch (LogicException $e) {
echo $e->getMessage();
}
``` | «second» Пояснение: The exception thrown in the finally block overrides the original exception and is caught by the outer catch block.
Raw{ ⏎ "answer": "second", ⏎ "explanation": "The exception thrown in the finally block overrides the original exception and is caught by the outer catch block." ⏎ } | верно | An exception from finally replaces the in-flight one — the last thrown is caught. |
T09-L9 30.94 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 resolves to the App\Foo alias from the use statement, while \Baz refers to the global Baz class.
Raw{"answer": "App\\Foo|Baz", "explanation": "Baz resolves to the App\\Foo alias from the use statement, while \\Baz refers to the global Baz class."} | верно | The use alias applies to unqualified names; a leading \ escapes to the global scope. |
T09-L10 16.52 c | Namespaces and autoloading | What does this code output?
```php
namespace Ns;
class Foo {}
$c = 'Foo';
echo (class_exists($c) ? 'yes' : 'no')
. (class_exists(__NAMESPACE__ . '\\' . $c) ? 'yes' : 'no');
``` | «noyes» Пояснение: class_exists('Foo') checks the global namespace and fails, while class_exists('Ns\Foo') succeeds.
Raw{ ⏎ "answer": "noyes", ⏎ "explanation": "class_exists('Foo') checks the global namespace and fails, while class_exists('Ns\\Foo') succeeds." ⏎ } | верно | Dynamic names are not resolved against the namespace — 'Foo' is the global class. |
T10-L9 28.66 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,3» Пояснение: The foreach reference is released when the loop ends, so assigning to $v does not modify $a.
Raw{"answer": "1,2,3", "explanation": "The foreach reference is released when the loop ends, so assigning to $v does not modify $a."} | неверно верный: «1,2,99» | After a by-ref foreach, $v remains a reference to the last element. |
T10-L10 3.27 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 $n is shared by class A and its subclass B, so the three calls increment it from 0 to 1, 2, and 3.
Raw{ ⏎ "answer": "3", ⏎ "explanation": "The static variable $n is shared by class A and its subclass B, so the three calls increment it from 0 to 1, 2, and 3." ⏎ } | верно | A method's static variable belongs to the parent's method — subclasses share it. |
T11-L9 145.04 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();
``` | «—» Пояснение: The first send() only starts the generator and ignores 10, so it pauses at the first yield and getReturn() is null, printing nothing.
Raw{ ⏎ "answer": "", ⏎ "explanation": "The first send() only starts the generator and ignores 10, so it pauses at the first yield and getReturn() is null, printing nothing." ⏎ } | неверно верный: «11» | send() resumes the generator: $x = 10, return 10+1. |
T11-L10 2.79 c | Generators, iterators, SPL | What does this code output?
```php
function inner(): Generator
{
yield 1;
yield 2;
return 'ok';
}
function outer(): Generator
{
$r = yield from inner();
yield $r;
}
echo implode(',', iterator_to_array(outer()));
``` | «1,2,ok» Пояснение: yield from yields inner's values and assigns its return value to $r, which is then yielded by outer.
Raw{ ⏎ "answer": "1,2,ok", ⏎ "explanation": "yield from yields inner's values and assigns its return value to $r, which is then yielded by outer." ⏎ } | неверно верный: «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.7 c | Configuration and security | What does this code output?
```php
$hash = password_hash('x', PASSWORD_BCRYPT, ['cost' => 4]);
echo password_needs_rehash($hash, PASSWORD_BCRYPT, ['cost' => 4]) ? 'yes' : 'no';
echo password_needs_rehash($hash, PASSWORD_BCRYPT, ['cost' => 5]) ? 'yes' : 'no';
``` | «noyes» Пояснение: The hash was created with cost 4, so rehashing with cost 4 is not needed, but rehashing with cost 5 is.
Raw{ ⏎ "answer": "noyes", ⏎ "explanation": "The hash was created with cost 4, so rehashing with cost 4 is not needed, but rehashing with cost 5 is." ⏎ } | верно | password_needs_rehash compares the hash's options with the target: cost 4 = 4 → 'no', cost 5 ≠ 4 → 'yes'. |
T12-L10 182.5 c | Configuration and security | What does this code output on PHP 8.5?
```php
echo (E_ALL & 2048) === 0 ? 'strict-out' : 'strict-in';
``` | «strict-out» Пояснение: In PHP 8.5, the 2048 strict bit is no longer included in E_ALL.
Raw{ ⏎ "answer": "strict-out", ⏎ "explanation": "In PHP 8.5, the 2048 strict bit is no longer included in E_ALL." ⏎ } | верно | Since PHP 8.4, E_STRICT is out of E_ALL: the 2048 bit is unset → 'strict-out' (2048 is the historical E_STRICT bit). |
T13-L9 8.33 c | Symfony | What does this code output?
```php
use Symfony\Component\HttpFoundation\Request;
$r = Request::create('/demo', 'GET', [], [], [], ['HTTP_X_TOKEN' => 'abc']);
echo $r->headers->get('X-Token') === 'abc' ? 'mapped' : 'missing';
``` | «missing» Пояснение: The token was passed as the files argument, not the headers argument, so the request has no X-Token header.
Raw{"answer": "missing", "explanation": "The token was passed as the files argument, not the headers argument, so the request has no X-Token header."} | неверно верный: «mapped» | The literal comparison requires knowing the mapping: HttpFoundation turns HTTP_X_TOKEN into the X-Token header (case-insensitive); without it the answer is 'missing'. |
T13-L10 1.48 c | Symfony | What does this code output?
```php
use Symfony\Component\EventDispatcher\EventDispatcher;
use Symfony\Contracts\EventDispatcher\Event;
$d = new EventDispatcher();
$out = '';
$d->addListener('e', function () use (&$out) { $out .= 'B'; }, 10);
$d->addListener('e', function () use (&$out) { $out .= 'A'; });
$d->addListener('e', function () use (&$out) { $out .= 'C'; }, 5);
$d->dispatch(new Event(), 'e');
echo $out;
``` | «bca» Пояснение: Symfony dispatches listeners in descending priority order: B (10), C (5), then A (0).
Raw{"answer":"BCA","explanation":"Symfony dispatches listeners in descending priority order: B (10), C (5), then A (0)."} | верно | Listeners run by descending priority: 10 (B), 5 (C), 0 (A). |
T14-L10 5.33 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 persistent object instance for the same entity identifier on repeated find calls.
Raw{"answer": "same", "explanation": "Doctrine's EntityManager identity map returns the same persistent object instance for the same entity identifier on repeated find calls."} | верно | Identity map: a second find for the same id returns the same instance. |
T14-L9 9.89 c | Doctrine | Given: Doctrine ORM 3, an EntityManager on in-memory SQLite, entity User with an auto-increment primary key. The users table is empty. What does this code output?
```php
$u = new User(name: 'B');
$em->persist($u);
$em->remove($u);
$em->flush();
echo count($em->getConnection()->fetchAllAssociative('SELECT * FROM users'));
``` | «0» Пояснение: The entity is removed from the UnitOfWork before flush, so no INSERT is executed.
Raw{ ⏎ "answer": 0, ⏎ "explanation": "The entity is removed from the UnitOfWork before flush, so no INSERT is executed." ⏎ } | верно | The unit of work schedules INSERT at flush: remove after persist cancels it. |
T15-L10 1.17 c | PostgreSQL | What does this SQL query return (PostgreSQL 17)?
```sql
CREATE TEMP TABLE t (x int);
INSERT INTO t VALUES (1), (NULL);
SELECT count(x) FROM t;
``` | «1» Пояснение: COUNT(x) counts non-NULL values of the specified column, so only the value 1 is counted.
Raw{ ⏎ "answer": 1, ⏎ "explanation": "COUNT(x) counts non-NULL values of the specified column, so only the 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 produces cumulative values 10, 30, and 60, then string_agg joins them in id order.
Raw{"answer": "10,30,60", "explanation": "The window SUM produces cumulative values 10, 30, and 60, then string_agg joins them in id order."} | верно | With ORDER BY the default window frame is running (start to current row). |
T16-L9 144.0 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» Пояснение: M1 echoes its tag and passes to M2, which echoes its tag before continuing.
Raw{ ⏎ "answer": "M1M2", ⏎ "explanation": "M1 echoes its tag and passes to M2, which echoes its tag before continuing." ⏎ } | верно | The first-added middleware runs first (outermost). |
T16-L10 4.57 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» Пояснение: The HandlersLocator calls both handler descriptors in sequence, so $n is incremented by 1 (h1) then by 10 (h2), resulting in 11.
Raw{"answer": "11", "explanation": "The HandlersLocator calls both handler descriptors in sequence, so $n is incremented by 1 (h1) then by 10 (h2), resulting in 11."} | верно | All registered handlers of the message run: 1 + 10 = 11. |
T17-L9 2.58 c | PostgreSQL: transactions and indexes | What does this SQL query return (PostgreSQL 17)?
```sql
CREATE TEMP TABLE t (a int);
CREATE UNIQUE INDEX ON t (a);
INSERT INTO t VALUES (1) ON CONFLICT DO NOTHING;
INSERT INTO t VALUES (1) ON CONFLICT DO NOTHING;
SELECT count(*) FROM t;
``` | «1» Пояснение: The second insert conflicts with the unique index, so ON CONFLICT DO NOTHING suppresses it.
Raw{ ⏎ "answer": 1, ⏎ "explanation": "The second insert conflicts with the unique index, so ON CONFLICT DO NOTHING suppresses it." ⏎ } | верно | ON CONFLICT DO NOTHING skips the duplicate: one insert. |
T17-L10 1.79 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 commit, so both inserts succeed and the count is 2.
Raw{ ⏎ "answer": 2, ⏎ "explanation": "The deferrable unique constraint is checked at commit, so both inserts succeed and the count is 2." ⏎ } | верно | DEFERRED postpones the uniqueness check to COMMIT — count sees 2 rows. |
T18-L9 72.93 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» Пояснение: In PHPUnit 10.5, --filter uses a regex, so test_sum matches both test_sum and test_sum_abs, each contributing three data-provider cases.
Raw{"answer": 6, "explanation": "In PHPUnit 10.5, --filter uses a regex, so test_sum matches both test_sum and test_sum_abs, each contributing three data-provider cases."} | верно | --filter is a substring match: test_sum also matches test_sum_abs (3+3 datasets). |
T18-L10 4.45 c | Testing: PHPUnit | How many tests will this command run, and how many of them will fail? Answer with two comma-separated numbers (ran, failed).
```php
use PHPUnit\Framework\TestCase;
use PHPUnit\Framework\Attributes\DataProvider;
final class Calc2Test extends TestCase
{
public function prov(): array
{
return [[1], [-1]];
}
#[DataProvider('prov')]
public function test_x(int $x): void
{
$this->assertTrue($x > 0);
}
}
```
Command: `phpunit Calc2Test.php` (PHPUnit 10.5) | «2,1» Пояснение: The data provider supplies two datasets, x=1 and x=-1; the first passes and the second fails.
Raw{"answer":"2,1","explanation":"The data provider supplies two datasets, x=1 and x=-1; the first passes and the second fails."} | верно | A non-static provider is just a deprecation in PHPUnit 10: both datasets run and the [-1] dataset fails the assert — 2 ran, 1 failure. |
T19-L9 1.18 c | HTTP and REST API | Which HTTP method does this command send?
```bash
curl -s -d 'a=1' http://demo.local/api
``` | «post» Пояснение: The -d option makes curl send the data as a POST request by default.
Raw{"answer": "POST", "explanation": "The -d option makes curl send the data as a POST request by default."} | верно | -d/-F switches curl to POST by default. |
T19-L10 0.93 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 makes curl send the -d data as a query string using the GET method.
Raw{"answer": "GET", "explanation": "The -G option makes curl send the -d data as a query string using the GET method."} | верно | -G turns -d data into the query string; the method stays GET. |
T20-L9 3.5 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.2, when the client_id is not recognized by the authorization server, it responds with the error 'invalid_client'.
Raw{"answer":"invalid_client","explanation":"Per RFC 6749 Section 5.2, when the client_id is not recognized by the authorization server, it responds with the error 'invalid_client'."} | верно | Unknown client → invalid_client (RFC 6749 §5.2). |
T20-L10 1.4 c | Security and OAuth | OAuth 2.0: the client started the flow with response_type=token. In which part of the redirect_uri does the authorization server pass the access_token? | «fragment» Пояснение: In the OAuth 2.0 implicit flow with response_type=token, the access token is returned in the fragment component of the redirect URI.
Raw{ ⏎ "answer": "fragment", ⏎ "explanation": "In the OAuth 2.0 implicit flow with response_type=token, the access token is returned in the fragment component of the redirect URI." ⏎ } | верно | The implicit flow passes the token in the URL fragment (#) — it never reaches the server. |
T21-L9 2.02 c | Twig | What does this Twig template output?
```twig
{{ false|default(2) * 3 }}
``` | «6» Пояснение: The false value is replaced by the default value 2, and 2 multiplied by 3 is 6.
Raw{"answer": 6, "explanation": "The false value is replaced by the default value 2, and 2 multiplied by 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 198.56 c | Twig | What exception class does render() of this template throw?
```twig
{{ 'a' ~ 1 + 2 }}
``` | «no» Пояснение: It does not throw an exception; the expression evaluates to 'a3'.
Raw{"answer": "no", "explanation": "It does not throw an exception; the expression evaluates to 'a3'."} | неверно верный: «runtimeerror» | In Twig ~ binds tighter than +: ('a' ~ 1) + 2 → string + int → a render error (RuntimeError). |
T22-L9 12.16 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 single array element '' is blank, so one NotBlank violation is returned.
Raw{"answer": 1, "explanation": "The single array element '' is blank, so one NotBlank violation is returned."} | неверно верный: «0» | NotBlank treats null, '', [] as blank — the array [''] is not blank. |
T22-L10 280.22 c | Symfony: Security and forms | What does this code output?
```php
use Symfony\Component\Form\Forms;
use Symfony\Component\Form\Extension\Core\Type\TextType;
$factory = Forms::createFormFactoryBuilder()->getFormFactory();
$form = $factory->create(TextType::class);
try {
echo $form->isValid() ? 'valid' : 'invalid';
} catch (Throwable $e) {
echo get_class($e);
}
``` | «— (нет ответа)» | не разобрано верный: «symfony\component\form\exception\logicexception» парсинг: нет | isValid() on a non-submitted form throws LogicException, it does not return false. |
T23-L9 96.44 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» Пояснение: The compiled container caches the resolved service instance, so both get() calls return the same object.
Raw{"answer": "same", "explanation": "The compiled container caches the resolved service instance, so both get() calls return the same object."} | верно | Container services are shared: two get() calls yield one instance. |
T23-L10 280.06 c | Symfony: configuration and services | What does this code output?
```php
use Symfony\Component\DependencyInjection\ContainerBuilder;
$c = new ContainerBuilder();
$c->setParameter('name', 'Bob');
$c->setParameter('greeting', 'hi %name%');
$c->setParameter('message', '%greeting%!');
$c->compile();
echo $c->getParameter('message');
``` | «— (нет ответа)» | не разобрано верный: «hi bob!» парсинг: нет | compile() resolves %-references transitively: %greeting% → 'hi %name%' → 'hi Bob!', the answer assembles over two hops. |
T24-L9 135.34 c | Bootstrap | What is the max-width of .container in Bootstrap 5.3 at a 992px viewport? | «960» Пояснение: At Bootstrap 5.3’s 992px large breakpoint, .container has a max-width of 960px (60rem).
Raw{"answer": 960, "explanation": "At Bootstrap 5.3’s 992px large breakpoint, .container has a max-width of 960px (60rem)."} | верно | 5.x container widths: 540/720/960/1140/1320 (sm–xxl); 992 → 960px. |
T24-L10 191.79 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-primary» Пояснение: Both classes have equal specificity, and Bootstrap 5.3 defines .text-primary after .text-danger in the utility CSS, so it wins.
Raw{ ⏎ "answer": "text-primary", ⏎ "explanation": "Both classes have equal specificity, and Bootstrap 5.3 defines .text-primary after .text-danger in the utility CSS, so it wins." ⏎ } | неверно верный: «text-danger» | Specificity ties — the later rule wins: text-danger is declared after text-primary. |
T25-L9 1.6 c | Clean architecture | Layers: Domain, Application, Infrastructure. Deptrac rules: Application → Domain; Infrastructure → Domain, Application; Domain → Domain only.
How many violations will deptrac report for this class?
```php
namespace App\Domain;
use App\Application\PlaceOrder;
use App\Infrastructure\Db;
class OrderService
{
public function __construct(
private PlaceOrder $handler,
private Db $db,
) {}
}
``` | «2» Пояснение: The Domain class depends on Application and Infrastructure, and both dependencies violate the rule that Domain can only depend on Domain.
Raw{ ⏎ "answer": 2, ⏎ "explanation": "The Domain class depends on Application and Infrastructure, and both dependencies violate the rule that Domain can only depend on Domain." ⏎ } | верно | Domain may depend only on Domain: PlaceOrder (Application) + Db (Infrastructure) = 2. |
T25-L10 5.49 c | Clean architecture | Layers: Domain, Application, Infrastructure. Deptrac rules: Application → Domain; Infrastructure → Domain, Application; Domain → Domain only.
How many violations will deptrac report for this class?
```php
namespace App\Domain;
use App\Application\PlaceOrder;
use App\Infrastructure\Db;
class BillingService
{
public function __construct(
private PlaceOrder $handler,
private Db $db,
private \App\Infrastructure\Logger $logger,
) {}
}
``` | «3» Пояснение: The Domain class depends on one Application class and two Infrastructure classes, and Domain may depend only on Domain.
Raw{ ⏎ "answer": 3, ⏎ "explanation": "The Domain class depends on one Application class and two Infrastructure classes, and Domain may depend only on Domain." ⏎ } | верно | The inline FQCN \App\Infrastructure\Logger counts too: Application + Db + Logger = 3. |
T26-L10 1.66 c | DDD | What does this code output?
```php
final class Money
{
public function __construct(public readonly int $amount) {}
public function add(Money $o): Money
{
return new self($this->amount + $o->amount);
}
}
$a = new Money(10);
$c = $a->add(new Money(5));
echo $a->amount . ',' . $c->amount;
``` | «10,15» Пояснение: $a->amount is 10 and $c->amount is 15, concatenated with a comma.
Raw{ ⏎ "answer": "10,15", ⏎ "explanation": "$a->amount is 10 and $c->amount is 15, concatenated with a comma." ⏎ } | верно | The VO is immutable: add() returns a new instance; the original is unchanged. |
T26-L9 1.78 c | DDD | What does this code output?
```php
final class Order
{
private array $items = [];
public function add(string $sku): void
{
$this->items[$sku] = true;
}
public function count(): int
{
return count($this->items);
}
public function remove(string $sku): void
{
if (count($this->items) === 1) {
throw new DomainException('last item');
}
unset($this->items[$sku]);
}
}
$o = new Order;
$o->add('a');
try {
$o->remove('a');
} catch (DomainException) {
}
echo $o->count();
``` | «1» Пояснение: The remove() call throws because there is only one item, so the item is not removed and count() remains 1.
Raw{ ⏎ "answer": 1, ⏎ "explanation": "The remove() call throws because there is only one item, so the item is not removed and count() remains 1." ⏎ } | верно | The failed remove leaves aggregate state unchanged: the invariant threw before unset — count stays 1. |
VC-L9 0.81 c | PHP 8.4–8.5 | What does this code output on PHP 8.5?
```php
class C
{
public function hi(): string { return 'hi'; }
}
echo new C()->hi();
``` | «hi» Пояснение: The object's hi() method returns the string 'hi', which echo prints.
Raw{ ⏎ "answer": "hi", ⏎ "explanation": "The object's hi() method returns the string 'hi', which echo prints." ⏎ } | верно | Since 8.4, new in a method chain works without wrapping parentheses. |
VC-L10 4.27 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 uninitialized before property access (prints 'yes'), but accessing $o->v triggers the factory callback which initializes it, so the second check prints 'no'.
Raw```json ⏎ {"answer": "yesno", "explanation": "The lazy ghost is uninitialized before property access (prints 'yes'), but accessing $o->v triggers the factory callback which initializes it, so the second check prints 'no'."} ⏎ ``` | верно | newLazyGhost (8.4): the object stays lazy until first access — reading a property initializes it and clears the flag. |
T28-L9 1.69 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 component, including AbstractGuardAuthenticator, in Symfony 7 and later versions such as 8.1.
Raw{"answer":"no","explanation":"Symfony removed the Guard component, including AbstractGuardAuthenticator, in Symfony 7 and later versions such as 8.1."} | верно | Guard authentication was removed in Symfony 7.0 — the class is gone in 8.1. |
T28-L10 31.49 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 has been removed while AttributeClassLoader still exists.
Raw{ ⏎ "answer": "noyes", ⏎ "explanation": "In Symfony 8.1, AnnotationClassLoader has been removed while AttributeClassLoader still exists." ⏎ } | верно | Annotation loaders were removed in 7.0; only attribute loaders remain (Annotation→Attribute). |