Пример запроса (первая клетка). System одинаковый во всех запросах прогона, user — свой вопрос для каждой клетки:
| Клетка | Тема | Утверждение | Ответ |
Результат | Обоснование |
T01-L1 4.34 c | Syntax and operators | Double-quoted and single-quoted strings are processed identically; the difference is only in speed. | «no» Пояснение: Double-quoted strings support variable interpolation and full escape sequences, while single-quoted strings do not, so they are not processed identically—the difference is functional, not only in speed.
Raw{"answer": "no", "explanation": "Double-quoted strings support variable interpolation and full escape sequences, while single-quoted strings do not, so they are not processed identically—the difference is functional, not only in speed."} | верно | В двойных кавычках работают интерполяция переменных и escape-последовательности, в одинарных — нет. |
T01-L2 1.1 c | Syntax and operators | The ?? operator follows isset semantics and raises no warnings for undefined variables. | «yes» Пояснение: The null coalescing operator (??) internally uses isset() semantics, so it returns the right-hand value without raising any notice or warning for undefined variables.
Raw{"answer": "yes", "explanation": "The null coalescing operator (??) internally uses isset() semantics, so it returns the right-hand value without raising any notice or warning for undefined variables."} | верно | ?? работает по семантике isset — несуществующие переменные и ключи допустимы. |
T01-L3 0.73 c | Syntax and operators | What will this print: echo 'a', 'b'; | «ab» Пояснение: In PHP, echo with comma-separated arguments prints them concatenated together without any separator, so it outputs 'ab'.
Raw{"answer": "ab", "explanation": "In PHP, echo with comma-separated arguments prints them concatenated together without any separator, so it outputs 'ab'."} | верно | echo принимает список аргументов: ab. |
T01-L4 4.64 c | Syntax and operators | print returns the value 1 and can be used inside an expression. | «yes» Пояснение: In PHP, print is a language construct that outputs a string and returns the integer 1, and unlike echo it can be used in an expression (e.g., $x = print "hello";).
Raw{"answer": "yes", "explanation": "In PHP, print is a language construct that outputs a string and returns the integer 1, and unlike echo it can be used in an expression (e.g., $x = print \"hello\";)."} | верно | print — выражение со значением 1, в отличие от echo, который значения не возвращает. |
T01-L5 1.36 c | Syntax and operators | The ?: (elvis) operator returns its left operand when it is falsy. | «no» Пояснение: The Elvis operator (?:) returns the left operand when it is truthy, and the right operand when the left is falsy.
Raw{"answer": "no", "explanation": "The Elvis operator (?:) returns the left operand when it is truthy, and the right operand when the left is falsy."} | верно | Наоборот: $a ?: $b возвращает $a, если он истинный, иначе $b. |
T01-L6 1.23 c | Syntax and operators | In PHP 8, the concatenation operator (.) has lower precedence than addition and subtraction. | «yes» Пояснение: In PHP, the concatenation operator (.) has lower precedence than arithmetic operators like + and -, so in an expression like 5 + 3 . 'hello', the addition is evaluated first, yielding '8hello'.
Raw{"answer": "yes", "explanation": "In PHP, the concatenation operator (.) has lower precedence than arithmetic operators like + and -, so in an expression like 5 + 3 . 'hello', the addition is evaluated first, yielding '8hello'."} | верно | С PHP 8 (RFC concat precedence) '.' имеет приоритет ниже арифметики: 'сумма: ' . 2 + 3 → 'сумма: 5' (в PHP 7 было иначе). |
T01-L7 0.78 c | Syntax and operators | The expression 2 ** 3 ** 2 in PHP evaluates as (2 ** 3) ** 2, that is, 64. | «no» Пояснение: The ** operator in PHP is right-associative, so 2 ** 3 ** 2 evaluates as 2 ** (3 ** 2) = 2 ** 9 = 512, not (2 ** 3) ** 2 = 64.
Raw{"answer": "no", "explanation": "The ** operator in PHP is right-associative, so 2 ** 3 ** 2 evaluates as 2 ** (3 ** 2) = 2 ** 9 = 512, not (2 ** 3) ** 2 = 64."} | верно | ** право-ассоциативен: 2 ** (3 ** 2) = 2 ** 9 = 512. |
T01-L8 1.85 c | Syntax and operators | What string will this print: echo 'sum: ' . 2 + 3; (PHP 8)? | «3» Пояснение: The concatenation operator '.' has higher precedence than '+', so it parses as ('sum: ' . 2) + 3, which is 'sum: 2' + 3, and the non-numeric string casts to 0, yielding 3.
Raw{"answer": 3, "explanation": "The concatenation operator '.' has higher precedence than '+', so it parses as ('sum: ' . 2) + 3, which is 'sum: 2' + 3, and the non-numeric string casts to 0, yielding 3."} | неверно верный: «sum: 5» | Парная к verify-клетке про приоритет: 'сумма: 5'. |
T02-L1 1.59 c | Types and comparisons | With strict comparison (===), arrays are considered equal regardless of element order. | «no» Пояснение: With ===, arrays are considered equal only if they have the same key/value pairs in the same order and are of the same type; order matters.
Raw{"answer": "no", "explanation": "With ===, arrays are considered equal only if they have the same key/value pairs in the same order and are of the same type; order matters."} | верно | === для массивов требует совпадения и значений, и их порядка. |
T02-L2 1.35 c | Types and comparisons | The comparison 0 == false returns false because it is a strict comparison. | «no» Пояснение: 0 == false uses loose comparison (==) and actually returns true, since 0 and false are considered equal in a non-strict comparison.
Raw{"answer": "no", "explanation": "0 == false uses loose comparison (==) and actually returns true, since 0 and false are considered equal in a non-strict comparison."} | верно | Наоборот: == — нестрогое сравнение и возвращает true; строгое — это === (0 === false → false). |
T02-L3 1.22 c | Types and comparisons | In PHP 8, the expression "abc" == 0 returns true. | «no» Пояснение: In PHP 8, comparing a non-numeric string to an integer performs a string comparison ('abc' == '0'), which is false, unlike PHP 7 where the string was cast to 0.
Raw{"answer": "no", "explanation": "In PHP 8, comparing a non-numeric string to an integer performs a string comparison ('abc' == '0'), which is false, unlike PHP 7 where the string was cast to 0."} | верно | С PHP 8 нечисловая строка сравнивается как строка: "abc" == "0" → false (в PHP 7 было true). |
T02-L4 1.53 c | Types and comparisons | Under loose comparison, null equals 0, the empty string, and false at the same time. | «yes» Пояснение: In PHP's loose comparison (==), null is considered equal to 0, the empty string "", and false, all at the same time.
Raw{"answer": "yes", "explanation": "In PHP's loose comparison (==), null is considered equal to 0, the empty string \"\", and false, all at the same time."} | верно | null == 0, null == "" и null == false — все true. |
T02-L5 0.89 c | Types and comparisons | What does the expression (int) '42abc' return? | «42» Пояснение: Casting a string to int in PHP reads the leading numeric portion, so '42abc' becomes 42.
Raw{"answer": 42, "explanation": "Casting a string to int in PHP reads the leading numeric portion, so '42abc' becomes 42."} | верно | Ведущая числовая часть: 42, без ошибок и warning. |
T02-L6 0.7 c | Types and comparisons | What does the expression '5' + 5 return? | «10» Пояснение: In PHP, the numeric string '5' is cast to an integer when used with the + operator, so '5' + 5 equals 10.
Raw{"answer": 10, "explanation": "In PHP, the numeric string '5' is cast to an integer when used with the + operator, so '5' + 5 equals 10."} | верно | Числовая строка приводится: int 10. |
T02-L7 1.3 c | Types and comparisons | When cast to string, false becomes "0". | «no» Пояснение: In PHP, casting false to a string yields an empty string "", not "0"; it is (int)false that gives 0.
Raw{"answer": "no", "explanation": "In PHP, casting false to a string yields an empty string \"\", not \"0\"; it is (int)false that gives 0."} | верно | false → "", true → "1". |
T02-L8 1.39 c | Types and comparisons | The comparison 0.1 + 0.2 === 0.3 returns false. | «yes» Пояснение: Due to floating-point precision, 0.1 + 0.2 yields 0.30000000000000004, which is not strictly equal (===) to 0.3.
Raw{"answer": "yes", "explanation": "Due to floating-point precision, 0.1 + 0.2 yields 0.30000000000000004, which is not strictly equal (===) to 0.3."} | верно | Двоичная погрешность float: 0.1 + 0.2 = 0.30000000000000004. |
T03-L1 1.95 c | Strings | strrev() correctly reverses a UTF-8 string. | «no» Пояснение: strrev() reverses a string byte by byte, which corrupts multi-byte UTF-8 characters; you need mb-based or regex-based reversal for correct UTF-8 handling.
Raw{"answer": "no", "explanation": "strrev() reverses a string byte by byte, which corrupts multi-byte UTF-8 characters; you need mb-based or regex-based reversal for correct UTF-8 handling."} | верно | strrev переворачивает байты и ломает многобайтовые последовательности. |
T03-L2 0.53 c | Strings | str_contains('Hello world', 'world') returns true. | «yes» Пояснение: The string 'Hello world' does contain the substring 'world', so str_contains returns true.
Raw{"answer": "yes", "explanation": "The string 'Hello world' does contain the substring 'world', so str_contains returns true."} | верно | str_contains с PHP 8.0 проверяет вхождение подстроки. |
T03-L3 0.75 c | Strings | str_pad() can pad a string on the right side only. | «no» Пояснение: str_pad() can pad on the right (STR_PAD_RIGHT, default), left (STR_PAD_LEFT), or both (STR_PAD_BOTH).
Raw{"answer": "no", "explanation": "str_pad() can pad on the right (STR_PAD_RIGHT, default), left (STR_PAD_LEFT), or both (STR_PAD_BOTH)."} | верно | STR_PAD_LEFT / STR_PAD_BOTH меняют сторону дополнения. |
T03-L4 1.04 c | Strings | By default trim() strips only spaces, leaving tabs and newlines intact. | «no» Пояснение: By default, trim() strips spaces, tabs, newlines, carriage returns, null bytes, and vertical tabs — not just spaces.
Raw{"answer": "no", "explanation": "By default, trim() strips spaces, tabs, newlines, carriage returns, null bytes, and vertical tabs — not just spaces."} | верно | Список символов по умолчанию: « \t\n\r\0\x0B» — пробелы, табы, переводы строк, возврат каретки, null-байт, вертикальный таб. Проверено php -r. |
T03-L5 1.06 c | Strings | How many BYTES does strlen('héllo') return for a UTF-8 string? | «6» Пояснение: strlen() counts bytes: 'h'(1) + 'é'(2 in UTF-8) + 'l'(1) + 'l'(1) + 'o'(1) = 6 bytes.
Raw{"answer": 6, "explanation": "strlen() counts bytes: 'h'(1) + 'é'(2 in UTF-8) + 'l'(1) + 'l'(1) + 'o'(1) = 6 bytes."} | верно | 6 букв по 2 байта: 12. |
T03-L6 0.89 c | Strings | What does substr('abcdef', -3) return? | «def» Пояснение: substr('abcdef', -3) starts 3 characters from the end of the string, returning the substring 'def'.
Raw{"answer": "def", "explanation": "substr('abcdef', -3) starts 3 characters from the end of the string, returning the substring 'def'."} | верно | Отрицательное смещение — с конца: def. |
T03-L7 1.06 c | Strings | ucfirst() modifies the string passed to it in place. | «no» Пояснение: ucfirst() returns a new string with the first character uppercased; it does not modify the original string in place (PHP strings are passed by value).
Raw{"answer": "no", "explanation": "ucfirst() returns a new string with the first character uppercased; it does not modify the original string in place (PHP strings are passed by value)."} | верно | Строки неизменяемы; ucfirst возвращает новую строку. |
T03-L8 1.16 c | Strings | Variable interpolation works in heredoc but not in nowdoc. | «yes» Пояснение: Heredoc supports variable interpolation like double-quoted strings, while nowdoc (delimited by single quotes) treats all content as literal text, similar to single-quoted strings.
Raw{"answer": "yes", "explanation": "Heredoc supports variable interpolation like double-quoted strings, while nowdoc (delimited by single quotes) treats all content as literal text, similar to single-quoted strings."} | верно | Nowdoc — «одинарные кавычки» в тройном синтаксисе: текст как есть. |
T04-L1 0.86 c | Arrays | The sort() function preserves the key-to-value association of the array. | «no» Пояснение: PHP's sort() re-indexes the array with sequential numeric keys, while asort() is the function that preserves key-to-value associations.
Raw{"answer": "no", "explanation": "PHP's sort() re-indexes the array with sequential numeric keys, while asort() is the function that preserves key-to-value associations."} | верно | sort перенумеровывает ключи; связь сохраняет asort. |
T04-L2 0.79 c | Arrays | The string key '5' in an array is stored as the integer 5. | «yes» Пояснение: PHP automatically converts string keys that represent valid integers into integer keys, so '5' is stored as the integer 5.
Raw{"answer": "yes", "explanation": "PHP automatically converts string keys that represent valid integers into integer keys, so '5' is stored as the integer 5."} | верно | Каноничные десятичные строковые ключи приводятся к int. |
T04-L3 0.96 c | Arrays | The in_array() function uses strict comparison (===) by default. | «no» Пояснение: in_array() uses loose comparison (==) by default; you must pass true as the third $strict parameter to use === comparison.
Raw{"answer": "no", "explanation": "in_array() uses loose comparison (==) by default; you must pass true as the third $strict parameter to use === comparison."} | верно | По умолчанию сравнение нестрогое; строгое — третий аргумент true. |
T04-L4 1.11 c | Arrays | Without a callback, array_filter() removes all "empty" (falsy) elements from the array. | «yes» Пояснение: Without a callback, array_filter() keeps only elements that are truthy, effectively removing all falsy values (0, '', null, false, '0', empty array).
Raw{"answer": "yes", "explanation": "Without a callback, array_filter() keeps only elements that are truthy, effectively removing all falsy values (0, '', null, false, '0', empty array)."} | верно | Убирает 0, "", null, false и пустые массивы. |
T04-L5 1.01 c | Arrays | By default, array_slice() preserves the original numeric keys of the array. | «no» Пояснение: The fourth parameter $preserve_keys defaults to false, so array_slice() reindexes the array starting from 0 by default.
Raw{"answer": "no", "explanation": "The fourth parameter $preserve_keys defaults to false, so array_slice() reindexes the array starting from 0 by default."} | верно | По умолчанию ключи перенумеровываются; сохранение — preserve_keys = true. |
T04-L6 1.17 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, giving the subarray [20, 30].
Raw{"answer": "[20, 30]", "explanation": "array_slice starts at index 1 and takes 2 elements, giving the subarray [20, 30]."} | верно | [20,30]; ключи перенумеровываются. |
T04-L7 1.63 c | Arrays | How many elements will count(['a' => 1] + ['a' => 9, 'b' => 2]) return? | «2» Пояснение: The + operator merges arrays with left-side keys taking precedence, so the result is ['a' => 1, 'b' => 2], which has 2 elements.
Raw{"answer": 2, "explanation": "The + operator merges arrays with left-side keys taking precedence, so the result is ['a' => 1, 'b' => 2], which has 2 elements."} | верно | Оператор + : по ключу 'a' побеждает левый; итого 2. |
T04-L8 1.94 c | Arrays | Since PHP 8.1, the spread operator [...$a, ...$b] supports arrays with string keys. | «yes» Пояснение: PHP 8.1 introduced the array spread operator which supports both integer and string keys.
Raw{"answer": "yes", "explanation": "PHP 8.1 introduced the array spread operator which supports both integer and string keys."} | верно | В 8.0 — только числовые ключи; 8.1 снял ограничение. |
T05-L1 3.15 c | Functions and closures | Named arguments cannot be combined with argument unpacking ...$args in a single call. | «no» Пояснение: Named arguments can be combined with argument unpacking (...$args) in a single call, as long as the named arguments are placed before the spread operator (e.g., foo(a: 1, ...$args)).
Raw{"answer": "no", "explanation": "Named arguments can be combined with argument unpacking (...$args) in a single call, as long as the named arguments are placed before the spread operator (e.g., foo(a: 1, ...$args))."} | верно | Можно: f(...$args, имя: значение). Нельзя только позиционный аргумент после распаковки. |
T05-L2 0.93 c | Functions and closures | An anonymous function without use sees variables from the outer scope. | «no» Пояснение: In PHP, closures do not have access to outer-scope variables unless they are explicitly passed via the 'use' keyword.
Raw{"answer": "no", "explanation": "In PHP, closures do not have access to outer-scope variables unless they are explicitly passed via the 'use' keyword."} | верно | Без use внешние переменные недоступны; авто-захват только у fn. |
T05-L3 0.83 c | Functions and closures | What will func_num_args() return inside function f($a) { return func_num_args(); } when called as f(1, 2, 3)? | «3» Пояснение: func_num_args() returns the number of arguments passed to the function call (3), regardless of the declared parameter count (1).
Raw{"answer": 3, "explanation": "func_num_args() returns the number of arguments passed to the function call (3), regardless of the declared parameter count (1)."} | верно | Считает переданные аргументы: 3. |
T05-L4 1.08 c | Functions and closures | The body of an arrow function fn may consist of several expressions in curly braces. | «no» Пояснение: An arrow function (fn) in PHP can only contain a single expression after the '=>' and does not support a curly-brace body with multiple expressions.
Raw{"answer": "no", "explanation": "An arrow function (fn) in PHP can only contain a single expression after the '=>' and does not support a curly-brace body with multiple expressions."} | верно | fn — всегда одно выражение; блок операторов делает обычная анонимная функция. |
T05-L5 1.56 c | Functions and closures | An arrow function fn captures outer variables by reference (lazily, at use time). | «no» Пояснение: PHP arrow functions (fn) capture outer variables by value at the time of creation, not by reference.
Raw{"answer": "no", "explanation": "PHP arrow functions (fn) capture outer variables by value at the time of creation, not by reference."} | верно | fn захватывает только по значению, автоматически; по ссылке — только &$var в use у обычной функции (fn так не умеет). |
T05-L6 1.75 c | Functions and closures | A closure declared as static function () {} does not capture $this. | «yes» Пояснение: In PHP, a static closure explicitly excludes $this from its scope, so it cannot access or capture the object instance.
Raw{"answer": "yes", "explanation": "In PHP, a static closure explicitly excludes $this from its scope, so it cannot access or capture the object instance."} | верно | static-замыкание отвязано от объекта: $this внутри недоступен. |
T05-L7 1.37 c | Functions and closures | What will this print: $x = 5; $f = function () use ($x) { return $x; }; $x = 7; echo $f(); | «5» Пояснение: The use($x) in the closure captures the value of $x (5) by value at the time the closure is created, so the later reassignment to 7 does not affect it.
Raw{"answer": 5, "explanation": "The use($x) in the closure captures the value of $x (5) by value at the time the closure is created, so the later reassignment to 7 does not affect it."} | верно | use захватывает по значению в момент создания: 5. |
T05-L8 1.01 c | Functions and closures | In weak typing mode (without strict_types), passing the string "5" to an int parameter is allowed. | «yes» Пояснение: In weak typing mode (the default without strict_types=1), PHP will coerce the string '5' to the integer 5 when passed to an int-typed parameter.
Raw{"answer": "yes", "explanation": "In weak typing mode (the default without strict_types=1), PHP will coerce the string '5' to the integer 5 when passed to an int-typed parameter."} | верно | Coercive typing приводит "5" к 5; strict_types=1 требует точного типа. |
T06-L1 0.98 c | OOP: classes and inheritance | PHP supports constructor property promotion: public function __construct(private int $x) {}. | «yes» Пояснение: Constructor property promotion was introduced in PHP 8.0, allowing properties to be declared directly in constructor parameters with visibility modifiers like 'private'.
Raw{"answer": "yes", "explanation": "Constructor property promotion was introduced in PHP 8.0, allowing properties to be declared directly in constructor parameters with visibility modifiers like 'private'."} | верно | С PHP 8.0 параметр с модификатором создаёт свойство и присваивание. |
T06-L2 0.62 c | OOP: classes and inheritance | Which keyword prevents a method from being overridden in subclasses? | «final» Пояснение: In PHP, the 'final' keyword prevents a method from being overridden in subclasses.
Raw{"answer": "final", "explanation": "In PHP, the 'final' keyword prevents a method from being overridden in subclasses."} | верно | final. |
T06-L3 0.74 c | OOP: classes and inheritance | A method declared final cannot be overridden in a subclass. | «yes» Пояснение: In PHP, the 'final' keyword on a method prevents it from being overridden in any subclass.
Raw{"answer": "yes", "explanation": "In PHP, the 'final' keyword on a method prevents it from being overridden in any subclass."} | верно | final запрещает переопределение метода и наследование класса. |
T06-L4 0.73 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 where they are declared and are not visible to subclasses.
Raw{"answer": "no", "explanation": "In PHP, private properties are only accessible within the class where they are declared and are not visible to subclasses."} | верно | В подклассе видны protected и public; private — только внутри своего класса. |
T06-L5 3.43 c | OOP: classes and inheritance | What does get_class(new class {}) return? Answer with the part of the name before the NUL byte (without the file path). | «class@anonymous» Пояснение: In PHP, get_class() on an anonymous class returns a string like 'class@anonymous/path:line\0<random>', so the part before the NUL byte without the file path is 'class@anonymous'.
Raw{"answer": "class@anonymous", "explanation": "In PHP, get_class() on an anonymous class returns a string like 'class@anonymous/path:line\\0<random>', so the part before the NUL byte without the file path is 'class@anonymous'."} | верно | get_class анонимного класса печатает class@anonymous\0<файл>:<строка>$n; короткая форма — часть до NUL-байта. Проверено php -r (hex). |
T06-L6 1.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» Пояснение: In PHP, private methods are completely hidden from child classes and are not part of the inheritance contract, so a child class is free to declare a method with the same name at any visibility level without conflict.
Raw{"answer": "yes", "explanation": "In PHP, private methods are completely hidden from child classes and are not part of the inheritance contract, so a child class is free to declare a method with the same name at any visibility level without conflict."} | верно | private-члены не наследуются — правила совместимости подписей не действуют. |
T06-L7 1.6 c | OOP: classes and inheritance | The magic method __get() is called only for non-existent properties. | «no» Пояснение: __get() is called for both non-existent and inaccessible (private/protected) properties, not only non-existent ones.
Raw{"answer": "no", "explanation": "__get() is called for both non-existent and inaccessible (private/protected) properties, not only non-existent ones."} | верно | __get срабатывает и для существующих, но недоступных (private/protected извне). |
T06-L8 1.85 c | OOP: classes and inheritance | What does reassigning a readonly property throw — Exception or Error? | «error» Пояснение: Reassigning a readonly property throws a TypeError, which extends \Error, not \Exception.
Raw{"answer": "Error", "explanation": "Reassigning a readonly property throws a TypeError, which extends \\Error, not \\Exception."} | верно | Error (readonly с 8.1); оговорка: в __clone() переинициализация допустима (8.3+). |
T07-L1 0.64 c | Interfaces, traits, enum | An interface can declare constants. | «yes» Пояснение: PHP interfaces allow public constant declarations alongside method signatures.
Raw{"answer": "yes", "explanation": "PHP interfaces allow public constant declarations alongside method signatures."} | верно | Константы интерфейса наследуются реализациями. |
T07-L2 0.95 c | Interfaces, traits, enum | Which operator checks whether an object is an instance of a class or interface? | «instanceof» Пояснение: In PHP, the 'instanceof' operator checks whether an object is an instance of a specific class or implements a specific interface.
Raw{"answer": "instanceof", "explanation": "In PHP, the 'instanceof' operator checks whether an object is an instance of a specific class or implements a specific interface."} | верно | instanceof. |
T07-L3 1.39 c | Interfaces, traits, enum | An interface can declare static methods. | «no» Пояснение: In PHP, interfaces can only declare public, abstract (non-static) methods; declaring a static method in an interface results in a fatal error.
Raw{"answer": "no", "explanation": "In PHP, interfaces can only declare public, abstract (non-static) methods; declaring a static method in an interface results in a fatal error."} | неверно верный: «yes» | Реализация обязана дать статический метод с той же сигнатурой. |
T07-L4 0.97 c | Interfaces, traits, enum | The instanceof operator only checks class inheritance: it ignores interfaces. | «no» Пояснение: PHP's instanceof operator checks both class inheritance and interface implementation; it returns true if the object is an instance of the class or implements the interface.
Raw{"answer": "no", "explanation": "PHP's instanceof operator checks both class inheritance and interface implementation; it returns true if the object is an instance of the class or implements the interface."} | верно | instanceof возвращает true и для интерфейсов объекта. |
T07-L5 1.11 c | Interfaces, traits, enum | An interface method may have a default implementation, like a trait method. | «no» Пояснение: In PHP, interface methods must be abstract and cannot have a body or default implementation; only traits (and abstract classes) can provide concrete method implementations.
Raw{"answer": "no", "explanation": "In PHP, interface methods must be abstract and cannot have a body or default implementation; only traits (and abstract classes) can provide concrete method implementations."} | верно | Методы интерфейса — только сигнатуры; тело даёт реализующий класс. |
T07-L6 1.46 c | Interfaces, traits, enum | An abstract method in an abstract class may have protected visibility. | «yes» Пояснение: In PHP, abstract methods can be declared with public, protected, or (since 7.1) private visibility; protected is a valid and common choice.
Raw{"answer": "yes", "explanation": "In PHP, abstract methods can be declared with public, protected, or (since 7.1) private visibility; protected is a valid and common choice."} | верно | В абстрактном классе — любая видимость; в интерфейсе — только public. |
T07-L7 0.78 c | Interfaces, traits, enum | How many elements will Foo::cases() return for enum Foo { case A; case B; case C; }? | «3» Пояснение: The enum Foo defines three cases (A, B, C), so Foo::cases() returns an array of 3 elements.
Raw{"answer": 3, "explanation": "The enum Foo defines three cases (A, B, C), so Foo::cases() returns an array of 3 elements."} | верно | Статический метод cases(): 3. |
T07-L8 0.75 c | Interfaces, traits, enum | A trait can declare constants. | «yes» Пояснение: PHP traits can declare constants alongside methods and properties, though they cannot declare non-constant properties or constructors.
Raw{"answer": "yes", "explanation": "PHP traits can declare constants alongside methods and properties, though they cannot declare non-constant properties or constructors."} | верно | С PHP 8.2 трейты могут объявлять константы (RFC constants_in_traits); до 8.2 — нет. |
T08-L1 0.76 c | Exceptions and errors | The Throwable interface is a common ancestor of both Exception and Error. | «yes» Пояснение: In PHP 7+, Throwable is the common interface implemented by both Exception and Error, making it their shared ancestor.
Raw{"answer": "yes", "explanation": "In PHP 7+, Throwable is the common interface implemented by both Exception and Error, making it their shared ancestor."} | верно | Иерархия с PHP 7: Throwable → Exception и Throwable → Error. |
T08-L2 1.27 c | Exceptions and errors | A catch (Exception $e) block will also catch TypeError, because TypeError ultimately inherits from Exception. | «no» Пояснение: In PHP, TypeError extends Error (not Exception), so a catch (Exception $e) block will not catch it; you would need catch (Throwable $e) or catch (Error $e).
Raw{"answer": "no", "explanation": "In PHP, TypeError extends Error (not Exception), so a catch (Exception $e) block will not catch it; you would need catch (Throwable $e) or catch (Error $e)."} | верно | TypeError наследуется от Error; catch (Exception) его не ловит. |
T08-L3 1.06 c | Exceptions and errors | The @ operator suppresses exceptions too. | «no» Пояснение: The @ operator only suppresses error reporting (warnings, notices, etc.), not exceptions, which are handled separately via try/catch.
Raw{"answer": "no", "explanation": "The @ operator only suppresses error reporting (warnings, notices, etc.), not exceptions, which are handled separately via try/catch."} | верно | @ глушит диагностику (warnings/notices), исключения не перехватывает. |
T08-L4 0.83 c | Exceptions and errors | What error class does intdiv(5, 0) throw? | «divisionbyzeroerror» Пояснение: intdiv(5, 0) throws a DivisionByZeroError, which is a subclass of ArithmeticError, when the divisor is zero.
Raw{"answer": "DivisionByZeroError", "explanation": "intdiv(5, 0) throws a DivisionByZeroError, which is a subclass of ArithmeticError, when the divisor is zero."} | верно | DivisionByZeroError (иерархия Error, не Exception); php-грейдер объективен. |
T08-L5 0.8 c | Exceptions and errors | The finally block runs only if the exception was caught by a catch block. | «no» Пояснение: The finally block always executes, regardless of whether an exception was thrown, caught, or not present at all.
Raw{"answer": "no", "explanation": "The finally block always executes, regardless of whether an exception was thrown, caught, or not present at all."} | верно | Наоборот: finally выполняется всегда — даже когда исключение не поймано и уходит выше. Проверено php -r. |
T08-L6 1.16 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 in a finally block supersedes (replaces) any exception from the try block, so it does have an effect.
Raw{"answer": "no", "explanation": "In PHP, an exception thrown in a finally block supersedes (replaces) any exception from the try block, so it does have an effect."} | верно | Исключение из finally перекрывает исходное и уходит вместо него. |
T08-L7 2.3 c | Exceptions and errors | What does the expression (bool) new Exception('x') return? | «yes» Пояснение: In PHP, casting any object (including a new Exception) to bool always evaluates to true.
Raw{"answer": "yes", "explanation": "In PHP, casting any object (including a new Exception) to bool always evaluates to true."} | верно | Любой объект при приведении к bool — true. Формы ответа: true или да. |
T08-L8 1.74 c | Exceptions and errors | Functions registered via register_shutdown_function() run when exit is called. | «yes» Пояснение: Shutdown functions registered with register_shutdown_function() are executed during script termination, which includes when exit() or die() is called.
Raw{"answer": "yes", "explanation": "Shutdown functions registered with register_shutdown_function() are executed during script termination, which includes when exit() or die() is called."} | верно | exit завершает скрипт, но shutdown-функции отрабатывают. |
T09-L1 1.17 c | Namespaces and autoloading | The use App\Service\Mailer; statement itself loads the class file. | «no» Пояснение: The 'use' statement only creates a local alias for a fully qualified class name; the class file is not loaded until the class is actually referenced (e.g., instantiated), at which point the autoloader triggers.
Raw{"answer": "no", "explanation": "The 'use' statement only creates a local alias for a fully qualified class name; the class file is not loaded until the class is actually referenced (e.g., instantiated), at which point the autoloader triggers."} | верно | use — псевдоним на этапе компиляции; файл грузит автозагрузчик при первом обращении. |
T09-L2 0.8 c | Namespaces and autoloading | What follows use to import a function (not a class): the word function or const? | «function» Пояснение: In PHP, the syntax to import a function is 'use function namespace\functionName;', while 'use const' is used for importing constants.
Raw{"answer": "function", "explanation": "In PHP, the syntax to import a function is 'use function namespace\\functionName;', while 'use const' is used for importing constants."} | верно | use function ...; (и use const для констант). |
T09-L3 1.11 c | Namespaces and autoloading | Into which file (path from src/) does the PSR-4 mapping "App\ → src/" place the class App\Controller\Api\UserController? | «controller/api/usercontroller.php» Пояснение: PSR-4 strips the mapped prefix 'App\' and converts the remaining namespace segments 'Controller\Api\UserController' into a relative file path with a .php extension.
Raw{"answer": "Controller/Api/UserController.php", "explanation": "PSR-4 strips the mapped prefix 'App\\' and converts the remaining namespace segments 'Controller\\Api\\UserController' into a relative file path with a .php extension."} | верно | Остаток имени после префикса, \ → /. |
T09-L4 1.14 c | Namespaces and autoloading | Including vendor/autoload.php registers autoloaders via spl_autoload_register(). | «yes» Пояснение: Composer's vendor/autoload.php registers its PSR-4, PSR-0, and classmap autoloaders by calling spl_autoload_register() for each.
Raw{"answer": "yes", "explanation": "Composer's vendor/autoload.php registers its PSR-4, PSR-0, and classmap autoloaders by calling spl_autoload_register() for each."} | верно | Composer ставит автозагрузчик именно на spl_autoload_register. |
T09-L5 0.66 c | Namespaces and autoloading | The magic constant __NAMESPACE__ contains the name of the current namespace. | «yes» Пояснение: __NAMESPACE__ is a PHP magic constant that returns the name of the current namespace (or an empty string if in the global namespace).
Raw{"answer": "yes", "explanation": "__NAMESPACE__ is a PHP magic constant that returns the name of the current namespace (or an empty string if in the global namespace)."} | верно | В корневом пространстве — пустая строка. |
T09-L6 1.11 c | Namespaces and autoloading | An unqualified class name (without a leading \) in new is resolved from the global root. | «no» Пояснение: An unqualified class name in PHP is resolved relative to the current namespace, not from the global root; only a leading backslash (\) forces global resolution.
Raw{"answer": "no", "explanation": "An unqualified class name in PHP is resolved relative to the current namespace, not from the global root; only a leading backslash (\\) forces global resolution."} | верно | Резолвится относительно текущего namespace (с учётом импортов). |
T09-L7 1.35 c | Namespaces and autoloading | With the PSR-4 mapping "App\ → src/", the class App\Model\User lives in the file src/Model/User.php. | «yes» Пояснение: PSR-4 maps the prefix App\ to src/, and the remaining sub-namespace Model\User translates to Model/User.php, giving the full path src/Model/User.php.
Raw{"answer": "yes", "explanation": "PSR-4 maps the prefix App\\ to src/, and the remaining sub-namespace Model\\User translates to Model/User.php, giving the full path src/Model/User.php."} | верно | Остаток имени после префикса переносится в путь как есть. |
T09-L8 3.63 c | Namespaces and autoloading | A use statement may be written inside a function body — the import then applies to that function only. | «no» Пояснение: In PHP, a 'use' statement for namespace imports is a compile-time directive that must appear at the top level of a file or within a namespace block; it cannot be placed inside a function body.
Raw{"answer": "no", "explanation": "In PHP, a 'use' statement for namespace imports is a compile-time directive that must appear at the top level of a file or within a namespace block; it cannot be placed inside a function body."} | верно | use внутри тела функции — parse error; импорты файловые и компиляционные. |
T10-L1 1.25 c | References and scope | Arrays are copied on assignment rather than passed by reference. | «yes» Пояснение: In PHP, arrays are copied by value on assignment by default; you must explicitly use the & operator to pass an array by reference.
Raw{"answer": "yes", "explanation": "In PHP, arrays are copied by value on assignment by default; you must explicitly use the & operator to pass an array by reference."} | верно | Присваивание массива — копия (в движке — copy-on-write). |
T10-L2 1.33 c | References and scope | What will this print: $a = [1, 2]; $b = $a; $b[] = 3; echo count($a); | «2» Пояснение: PHP arrays are passed by value (Copy on Write), so modifying $b does not affect $a, which still contains [1, 2].
Raw{"answer": 2, "explanation": "PHP arrays are passed by value (Copy on Write), so modifying $b does not affect $a, which still contains [1, 2]."} | верно | Присваивание — копия: в $a по-прежнему 2 элемента. |
T10-L3 1.06 c | References and scope | Inside a function, user-defined global variables are inaccessible without global, $GLOBALS, or passing them as parameters. | «yes» Пояснение: In PHP, variables defined in the global scope are not visible inside a function unless accessed via the global keyword, the $GLOBALS superglobal array, or passed as parameters.
Raw{"answer": "yes", "explanation": "In PHP, variables defined in the global scope are not visible inside a function unless accessed via the global keyword, the $GLOBALS superglobal array, or passed as parameters."} | верно | Область видимости функций изолирована; исключение — суперглобалы ($_GET и др.). |
T10-L4 1.29 c | References and scope | unset($GLOBALS['x']) inside a function removes the global variable only for that function. | «no» Пояснение: $GLOBALS is a reference to the global symbol table, so unset($GLOBALS['x']) removes the variable globally, not just within that function's scope.
Raw{"answer": "no", "explanation": "$GLOBALS is a reference to the global symbol table, so unset($GLOBALS['x']) removes the variable globally, not just within that function's scope."} | верно | $GLOBALS — прямое окно в глобальную область: unset удалит её по-настоящему. |
T10-L5 0.97 c | References and scope | What will this print: function inc(&$x) { $x++; } $n = 5; inc($n); echo $n; | «6» Пояснение: The function takes $x by reference, so $n is incremented from 5 to 6 before echo is called.
Raw{"answer": 6, "explanation": "The function takes $x by reference, so $n is incremented from 5 to 6 before echo is called."} | верно | Ссылка меняет оригинал: 6. |
T10-L6 2.17 c | References and scope | A foreach over an array (by value) works with the "live" array: changes to the array inside the loop are visible in the same pass. | «no» Пояснение: A PHP foreach (by value) iterates over a fixed snapshot of the array's elements; modifications to the array during the loop do not affect the current iteration.
Raw{"answer": "no", "explanation": "A PHP foreach (by value) iterates over a fixed snapshot of the array's elements; modifications to the array during the loop do not affect the current iteration."} | верно | По значению foreach итерирует копию-снимок. |
T10-L7 0.79 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, not to individual instances, so all objects share the same value and changes are visible in every instance.
Raw{"answer": "no", "explanation": "A static property belongs to the class, not to individual instances, so all objects share the same value and changes are visible in every instance."} | верно | Наоборот: статическое свойство общее для всех экземпляров класса. Проверено php -r. |
T10-L8 1.12 c | References and scope | An array can have a boolean key true, and it will be stored as bool. | «no» Пояснение: In PHP, boolean array keys are cast to integers: true becomes 1 and false becomes 0, so it is stored as an int, not a bool.
Raw{"answer": "no", "explanation": "In PHP, boolean array keys are cast to integers: true becomes 1 and false becomes 0, so it is stored as an int, not a bool."} | верно | Булев ключ приводится к int: true → 1, false → 0. |
T11-L1 1.14 c | Generators, iterators, SPL | Inside a generator, return with a value can be used, and it becomes available via $gen->getReturn(). | «yes» Пояснение: In PHP generators, a return statement with a value is allowed, and once the generator is fully exhausted, the value can be retrieved via $gen->getReturn().
Raw{"answer": "yes", "explanation": "In PHP generators, a return statement with a value is allowed, and once the generator is fully exhausted, the value can be retrieved via $gen->getReturn()."} | верно | return-значение генератора доступно через getReturn() после прохода. |
T11-L2 2.24 c | Generators, iterators, SPL | A fully consumed generator can be rewound with rewind() and traversed again. | «no» Пояснение: PHP generators are one-shot iterators; once fully consumed, they cannot be rewound or traversed again.
Raw{"answer": "no", "explanation": "PHP generators are one-shot iterators; once fully consumed, they cannot be rewound or traversed again."} | верно | Генератор одноразовый: rewind после начала итерации бросает Exception. |
T11-L3 4.93 c | Generators, iterators, SPL | The yield from construct delegates traversal to another generator or iterable. | «yes» Пояснение: The yield from construct (as in Python) does delegate iteration/traversal to another generator or iterable, allowing a generator to transparently yield items from a sub-iterable.
Raw{"answer": "yes", "explanation": "The yield from construct (as in Python) does delegate iteration/traversal to another generator or iterable, allowing a generator to transparently yield items from a sub-iterable."} | верно | yield from проксирует значения, ключи и return-значение внутреннего генератора. |
T11-L4 1.07 c | Generators, iterators, SPL | What does get_class(g()) return for function g() { yield 1; }? | «generator» Пояснение: A function containing yield is a generator function, and calling it returns a Generator object, so get_class() returns the string "Generator".
Raw{"answer": "Generator", "explanation": "A function containing yield is a generator function, and calling it returns a Generator object, so get_class() returns the string \"Generator\"."} | верно | Функция с yield возвращает Generator. |
T11-L5 1.09 c | Generators, iterators, SPL | How many elements will count(iterator_to_array((function () { yield from [1, 2, 3]; })())) return? | «3» Пояснение: The generator yields 1, 2, 3; iterator_to_array converts it to [1, 2, 3]; count returns 3.
Raw{"answer": 3, "explanation": "The generator yields 1, 2, 3; iterator_to_array converts it to [1, 2, 3]; count returns 3."} | верно | yield from делегирует все 3 элемента. |
T11-L6 0.91 c | Generators, iterators, SPL | The SplStack class implements a FIFO queue. | «no» Пояснение: SplStack implements a LIFO (Last In, First Out) stack, not a FIFO queue; SplQueue is the one that implements a FIFO queue.
Raw{"answer": "no", "explanation": "SplStack implements a LIFO (Last In, First Out) stack, not a FIFO queue; SplQueue is the one that implements a FIFO queue."} | верно | SplStack — стек LIFO; очередь FIFO — SplQueue. |
T11-L7 0.77 c | Generators, iterators, SPL | ArrayIterator allows wrapping an array and traversing it via the Iterator interface. | «yes» Пояснение: ArrayIterator is a built-in PHP class that wraps an array and implements the Iterator interface, allowing traversal via methods like current(), next(), key(), valid(), and rewind().
Raw{"answer": "yes", "explanation": "ArrayIterator is a built-in PHP class that wraps an array and implements the Iterator interface, allowing traversal via methods like current(), next(), key(), valid(), and rewind()."} | верно | Объектная обёртка над массивом. |
T11-L8 0.53 c | Generators, iterators, SPL | An ArrayObject instance cannot be traversed with foreach. | «no» Пояснение: ArrayObject implements Iterator and IteratorAggregate, so it can be directly traversed with foreach.
Raw{"answer": "no", "explanation": "ArrayObject implements Iterator and IteratorAggregate, so it can be directly traversed with foreach."} | верно | ArrayObject реализует IteratorAggregate — foreach по нему работает. |
T12-L1 1.37 c | Configuration and security | password_hash() generates a salt automatically — passing one separately is not needed. | «yes» Пояснение: password_hash() always generates a random salt internally and embeds it in the returned hash string; its signature has no parameter for supplying a custom salt.
Raw{"answer": "yes", "explanation": "password_hash() always generates a random salt internally and embeds it in the returned hash string; its signature has no parameter for supplying a custom salt."} | верно | Соль встраивается в строку результата; параметр salt устарел. |
T12-L2 1.06 c | Configuration and security | In PHP 8, PASSWORD_DEFAULT is md5 with an automatically added salt. | «no» Пояснение: In PHP 8, PASSWORD_DEFAULT is Argon2id (not md5); md5 is a fast, unsalted-by-default hash algorithm unsuitable for password storage.
Raw{"answer": "no", "explanation": "In PHP 8, PASSWORD_DEFAULT is Argon2id (not md5); md5 is a fast, unsalted-by-default hash algorithm unsuitable for password storage."} | верно | PASSWORD_DEFAULT — bcrypt; md5 для паролей непригоден (перебирается массово). |
T12-L3 1.13 c | Configuration and security | What does password_verify('secret', password_hash('secret', PASSWORD_DEFAULT)) return? | «yes» Пояснение: password_verify compares the plain-text string against the hash produced by password_hash of the same string, so it returns the boolean true.
Raw{"answer": "yes", "explanation": "password_verify compares the plain-text string against the hash produced by password_hash of the same string, so it returns the boolean true."} | верно | Соль и хеш в одной строке: true (форма ответа: true или да). |
T12-L4 1.52 c | Configuration and security | strip_tags() protects against SQL injection. | «no» Пояснение: strip_tags() only removes HTML/PHP tags and has no effect on SQL injection payloads; SQL injection must be prevented with parameterized queries or proper escaping.
Raw{"answer": "no", "explanation": "strip_tags() only removes HTML/PHP tags and has no effect on SQL injection payloads; SQL injection must be prevented with parameterized queries or proper escaping."} | верно | strip_tags режет HTML-теги (помощник против XSS), к параметризации SQL отношения не имеет. |
T12-L5 1.15 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 upon login, invalidating any previously known ID an attacker may have set, thereby preventing session fixation attacks.
Raw{"answer": "yes", "explanation": "session_regenerate_id() creates a new session ID upon login, invalidating any previously known ID an attacker may have set, thereby preventing session fixation attacks."} | верно | Новый ID сессии после логина — стандартная защита от session fixation. |
T12-L6 1.0 c | Configuration and security | Which built-in function returns the SAPI name (e.g., cli)? | «php_sapi_name()» Пояснение: The built-in function php_sapi_name() returns the name of the current SAPI (Server API) module, such as 'cli', 'apache2', or 'fpm-fcgi'.
Raw{"answer": "php_sapi_name()", "explanation": "The built-in function php_sapi_name() returns the name of the current SAPI (Server API) module, such as 'cli', 'apache2', or 'fpm-fcgi'."} | верно | php_sapi_name(). |
T12-L7 1.46 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 removes the session data on the server side; the PHPSESSID cookie in the browser remains until it expires or is explicitly deleted with setcookie().
Raw{"answer": "yes", "explanation": "session_destroy() only removes the session data on the server side; the PHPSESSID cookie in the browser remains until it expires or is explicitly deleted with setcookie()."} | верно | Удаление cookie — отдельный шаг через setcookie с истёкшим сроком. |
T12-L8 0.97 c | Configuration and security | Without calling session_start(), the $_SESSION array is automatically populated with session data. | «no» Пояснение: The $_SESSION array is only available and populated after session_start() is called; without it, no session data is loaded.
Raw{"answer": "no", "explanation": "The $_SESSION array is only available and populated after session_start() is called; without it, no session data is loaded."} | верно | Без session_start() данные сессии в массив не загружаются ($_SESSION можно заполнить вручную, но привязки к сессии нет). |
VC-L1 1.67 c | PHP 8.4–8.5 | In which PHP version was the array_find() function introduced? | «not a real php function» Пояснение: PHP does not have a built-in array_find() function; it has array_filter(), in_array(), and array_search() instead.
Raw{"answer": "not a real PHP function", "explanation": "PHP does not have a built-in array_find() function; it has array_filter(), in_array(), and array_search() instead."} | неверно верный: «8.4» | PHP 8.4 (RFC array_find). |
VC-L2 3.07 c | PHP 8.4–8.5 | Property hooks (get/set right in the property declaration) landed in PHP 8.4. | «yes» Пояснение: Property hooks (defining get/set logic directly in the property declaration) were indeed introduced in PHP 8.4.
Raw{"answer": "yes", "explanation": "Property hooks (defining get/set logic directly in the property declaration) were indeed introduced in PHP 8.4."} | верно | Property hooks — PHP 8.4 (ноябрь 2024). |
VC-L3 1.82 c | PHP 8.4–8.5 | Asymmetric visibility (public private(set) string $name) appeared in PHP 8.4. | «yes» Пояснение: Asymmetric visibility, allowing different visibility for reading and writing a property (e.g., public private(set) string $name), was indeed introduced in PHP 8.4.
Raw{"answer": "yes", "explanation": "Asymmetric visibility, allowing different visibility for reading and writing a property (e.g., public private(set) string $name), was indeed introduced in PHP 8.4."} | верно | Asymmetric visibility v2 — PHP 8.4. |
VC-L4 2.27 c | PHP 8.4–8.5 | In which PHP version was the #[\NoDiscard] attribute introduced? Answer with the version number. | «8.4» Пояснение: The #[\NoDiscard] attribute was introduced in PHP 8.4 to indicate that a function's return value should not be ignored.
Raw{"answer": "8.4", "explanation": "The #[\\NoDiscard] attribute was introduced in PHP 8.4 to indicate that a function's return value should not be ignored."} | неверно верный: «8.5» | #[\NoDiscard] — PHP 8.5 (marking return values as important). |
VC-L5 4.48 c | PHP 8.4–8.5 | In which PHP version did the pipe operator |> first appear? Answer with the version number. | «none» Пояснение: PHP has never implemented a pipe operator (|>) in any released version; it does not exist in the PHP language.
Raw{"answer": "none", "explanation": "PHP has never implemented a pipe operator (|>) in any released version; it does not exist in the PHP language."} | неверно верный: «8.5» | Pipe operator — PHP 8.5 (2025). |
VC-L6 3.89 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. | «does not exist» Пояснение: PHP has never introduced a clone-with syntax (clone($obj, ['x' => 1])); the clone keyword only performs a shallow copy with no parameter for property overrides.
Raw{"answer": "does not exist", "explanation": "PHP has never introduced a clone-with syntax (clone($obj, ['x' => 1])); the clone keyword only performs a shallow copy with no parameter for property overrides."} | неверно верный: «8.5» | Clone with v2 — PHP 8.5. |
VC-L7 4.28 c | PHP 8.4–8.5 | In which PHP version were the array_first() and array_last() functions introduced? | «these functions do not exist in any php version» Пояснение: array_first() and array_last() are not built-in PHP functions in any released version of PHP.
Raw{"answer": "These functions do not exist in any PHP version", "explanation": "array_first() and array_last() are not built-in PHP functions in any released version of PHP."} | неверно верный: «8.5» | PHP 8.5. |
VC-L8 3.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. | «not adopted» Пояснение: There is no known PHP RFC titled 'Partial Function Application v2'; this does not correspond to any accepted PHP feature.
Raw{"answer": "not adopted", "explanation": "There is no known PHP RFC titled 'Partial Function Application v2'; this does not correspond to any accepted PHP feature."} | неверно верный: «8.6» | PFA v2 принят 05.12.2025 (33-0-0), реализован в PHP 8.6. |
VF-L1 0.98 c | PHP: 8.6+ and the future | For which PHP version was the RFC clamp_v2 (the clamp() function) implemented, as of 2026-11-07? Answer with the version number. | «8.4» Пояснение: The clamp() function (RFC clamp_v2) was implemented in PHP 8.4.
Raw{"answer": "8.4", "explanation": "The clamp() function (RFC clamp_v2) was implemented in PHP 8.4."} | неверно верный: «8.6» | По данным владельца (wiki.php.net/rfc): clamp_v2 — 8.6; clamp() в 8.5.11 отсутствует (косвенное подтверждение). Дата-якорь делает клетку монотонной. |
VF-L2 3.08 c | PHP: 8.6+ and the future | RFC Context Managers v2 has already been adopted in PHP (as of 2026-11-07). | «no» Пояснение: There is no known adopted PHP RFC titled 'Context Managers v2'; this does not correspond to a recognized, accepted PHP RFC.
Raw{"answer": "no", "explanation": "There is no known adopted PHP RFC titled 'Context Managers v2'; this does not correspond to a recognized, accepted PHP RFC."} | верно | На 06.11.2026 — в обсуждении (создан 2026-10-23); не принят. |
VF-L3 3.69 c | PHP: 8.6+ and the future | RFC Bound-Erased Generic Types (generics) was declined in 2026. | «no» Пояснение: There is no verified PHP RFC titled 'Bound-Erased Generic Types' that was declined in 2026; this appears to be a fabricated claim.
Raw{"answer": "no", "explanation": "There is no verified PHP RFC titled 'Bound-Erased Generic Types' that was declined in 2026; this appears to be a fabricated claim."} | неверно верный: «yes» | Голосование завершилось 2026-06-28: отклонён (wiki.php.net/rfc). |
VF-L4 2.59 c | PHP: 8.6+ and the future | As of 2026-11-07, the RFC enabling multithreading (ZTS) by default has already been accepted in PHP. | «no» Пояснение: As of the known PHP development timeline, no RFC to make ZTS (multithreading) the default build has been accepted; PHP continues to default to NTS builds.
Raw{"answer": "no", "explanation": "As of the known PHP development timeline, no RFC to make ZTS (multithreading) the default build has been accepted; PHP continues to default to NTS builds."} | верно | Такого принятого RFC нет на дату якоря; якорь делает клетку монотонной — при принятии RFC позже клетка не перевернётся. |
VF-L5 1.29 c | PHP: 8.6+ and the future | As of PHP 8.5, generics (parameterized types) are still absent. | «yes» Пояснение: PHP has never included built-in generics or parameterized types, and PHP 8.5 does not introduce them either.
Raw{"answer": "yes", "explanation": "PHP has never included built-in generics or parameterized types, and PHP 8.5 does not introduce them either."} | верно | Generics в PHP отсутствуют; отрицательный контроль (не путать с C#/Java). |
VF-L6 2.22 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» Пояснение: Following PHP's annual November release cycle, PHP 8.5 would have been released around November 2025, making it the latest stable version as of 2026-11-07, while PHP 8.6's GA on 2026-11-19 is still in the future.
Raw{"answer": "yes", "explanation": "Following PHP's annual November release cycle, PHP 8.5 would have been released around November 2025, making it the latest stable version as of 2026-11-07, while PHP 8.6's GA on 2026-11-19 is still in the future."} | верно | 8.5 — релиз осени 2025; 8.6 GA 19.11.2026 (wiki.php.net/todo/php86). Дата снимка — 06.11.2026. |
VF-L7 1.09 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 a planned major revision that was never released; the team renumbered the project and shipped PHP 7.0 directly after PHP 5.6.
Raw{"answer": "yes", "explanation": "PHP 6 was a planned major revision that was never released; the team renumbered the project and shipped PHP 7.0 directly after PHP 5.6."} | верно | Исторический факт: ветка 6 не была релизнута. |
VF-L8 2.0 c | PHP: 8.6+ and the future | The RFC adding the #[\Deprecated] attribute to the core was adopted. | «no» Пояснение: The RFC proposing a #[\Deprecated] attribute for PHP core was not adopted; PHP continues to handle deprecation via docblock annotations and E_DEPRECATED notices.
Raw{"answer": "no", "explanation": "The RFC proposing a #[\\Deprecated] attribute for PHP core was not adopted; PHP continues to handle deprecation via docblock annotations and E_DEPRECATED notices."} | неверно верный: «yes» | #[\Deprecated] — принят, реализован в PHP 8.4. |
T25-L1 1.47 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/Onion Architecture, the Dependency Rule mandates that all source-code dependencies point only inward toward the center (the domain), meaning inner layers have no knowledge of outer layers.
Raw{"answer": "yes", "explanation": "In Clean/Onion Architecture, the Dependency Rule mandates that all source-code dependencies point only inward toward the center (the domain), meaning inner layers have no knowledge of outer layers."} | верно | Чистая (Robert C. Martin), луковичная (Jeffrey Palermo) и гексагональная (ports & adapters) — варианты одной идеи: зависимости направлены внутрь, к домену. Слоями в проекте следит deptrac. |
T25-L2 2.35 c | Clean architecture | Domain entities import neither Doctrine nor Symfony — only the language and, possibly, the standard library. | «yes» Пояснение: In a well-structured DDD application, domain entities should be pure PHP classes free of framework (Symfony) and ORM (Doctrine) dependencies, using only the language and possibly the standard library.
Raw{"answer": "yes", "explanation": "In a well-structured DDD application, domain entities should be pure PHP classes free of framework (Symfony) and ORM (Doctrine) dependencies, using only the language and possibly the standard library."} | верно | Изоляция домена от инфраструктуры; deptrac в проекте как раз следит за слоями. |
T25-L3 2.27 c | Clean architecture | Controllers and Twig templates belong to the business-logic layer because they are the ones calling use cases. | «no» Пояснение: Controllers and Twig templates belong to the presentation (UI) layer; they are responsible for handling HTTP requests and rendering views, not for containing business logic, even though they call use cases.
Raw{"answer": "no", "explanation": "Controllers and Twig templates belong to the presentation (UI) layer; they are responsible for handling HTTP requests and rendering views, not for containing business logic, even though they call use cases."} | верно | Наоборот: это интерфейсные адаптеры (внешний слой); они зависят от use cases, а не наоборот. |
T25-L4 2.1 c | Clean architecture | What sits at the very center of the onion architecture? | «domain» Пояснение: In the onion architecture, the innermost layer at the center contains the domain model or enterprise business rules (entities and core business logic).
Raw{"answer": "Domain", "explanation": "In the onion architecture, the innermost layer at the center contains the domain model or enterprise business rules (entities and core business logic)."} | неверно верный: «domain model» | Центральное кольцо — Domain Model: сущности и бизнес-правила без зависимостей; далее Domain Services → Application Services → Infrastructure/UI/Tests (Palermo). |
T25-L5 1.14 c | Clean architecture | Layer boundary violations can be caught automatically: a layer-dependency analyzer (e.g. deptrac) fails on a forbidden call. | «yes» Пояснение: Tools like deptrac enforce layer dependency rules and fail the build when a forbidden cross-layer call is detected, automatically catching boundary violations.
Raw{"answer": "yes", "explanation": "Tools like deptrac enforce layer dependency rules and fail the build when a forbidden cross-layer call is detected, automatically catching boundary violations."} | верно | depfile.yaml в проекте TasK: CI проверяет правила слоёв на каждом пайплайне. |
T25-L6 2.17 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 (interactor) should depend on abstractions (interfaces, DTOs) rather than framework-specific classes like HTTP requests or EntityManagers, to keep business logic decoupled, testable, and framework-agnostic.
Raw{"answer": "no", "explanation": "A use case (interactor) should depend on abstractions (interfaces, DTOs) rather than framework-specific classes like HTTP requests or EntityManagers, to keep business logic decoupled, testable, and framework-agnostic."} | верно | Use case принимает DTO и порты; привязка к HTTP/ORM протекает инфраструктуру во внутренние слои. |
T25-L7 1.05 c | Clean architecture | What is the component called that provides a collection of aggregates/entities while hiding the storage mechanism behind an interface? | «repository» Пояснение: The Repository pattern in DDD provides a collection-like interface for accessing domain aggregates/entities while abstracting the underlying storage mechanism behind an interface.
Raw{"answer": "Repository", "explanation": "The Repository pattern in DDD provides a collection-like interface for accessing domain aggregates/entities while abstracting the underlying storage mechanism behind an interface."} | верно | Repository pattern (DDD/Evans); в проекте — Doctrine-репозитории за портами. |
T25-L8 2.54 c | Clean architecture | In clean architecture, swapping PostgreSQL for another database touches only the outer layer — the domain and use cases stay unchanged. | «yes» Пояснение: In Clean Architecture, the database lives in the outermost layer (Frameworks & Drivers); use cases depend only on repository interfaces, so swapping PostgreSQL for another DB requires changes only in the outer implementation layer while domain entities and use cases remain untouched.
Raw{"answer": "yes", "explanation": "In Clean Architecture, the database lives in the outermost layer (Frameworks & Drivers); use cases depend only on repository interfaces, so swapping PostgreSQL for another DB requires changes only in the outer implementation layer while domain entities and use cases remain untouched."} | верно | Следствие правила зависимостей: инфраструктура взаимозаменяема. |
T26-L1 1.33 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 with a defined consistency boundary, not a synonym for a database table; it is a domain-level concept that may be persisted across multiple tables.
Raw{"answer": "no", "explanation": "In DDD, an aggregate is a cluster of domain objects with a defined consistency boundary, not a synonym for a database table; it is a domain-level concept that may be persisted across multiple tables."} | верно | Агрегат — кластер объектов с границей согласованности (транзакционной вокруг корня); таблица — деталь хранения. |
T26-L2 0.98 c | DDD | A Value Object is immutable and compared by the values of its fields, not by identity. | «yes» Пояснение: Value Objects are defined by their immutability and value-based equality (compared by field values rather than object identity/reference).
Raw{"answer": "yes", "explanation": "Value Objects are defined by their immutability and value-based equality (compared by field values rather than object identity/reference)."} | верно | Классика Evans: Money, Email; равенство структурное. |
T26-L3 1.38 c | DDD | What is the single external entry point of an aggregate, through which all changes must go, called? | «aggregate root» Пояснение: In Domain-Driven Design, the Aggregate Root is the single entry point of an aggregate through which all external modifications must pass.
Raw{"answer": "Aggregate Root", "explanation": "In Domain-Driven Design, the Aggregate Root is the single entry point of an aggregate through which all external modifications must pass."} | верно | Aggregate Root: внешние объекты ссылаются только на корень; он защищает инварианты агрегата. |
T26-L4 1.13 c | DDD | In DDD, a repository is declared for an aggregate (its root), not for every entity. | «yes» Пояснение: In DDD, a repository is defined per aggregate (root), and entities within that aggregate are accessed through the root, not via their own repositories.
Raw{"answer": "yes", "explanation": "In DDD, a repository is defined per aggregate (root), and entities within that aggregate are accessed through the root, not via their own repositories."} | верно | Репозиторий корня хранит границу согласованности агрегата; вложенные сущности доступны только через корень. |
T26-L5 0.96 c | DDD | Ubiquitous language is the model's shared language common to developers and domain experts. | «yes» Пояснение: In Domain-Driven Design, Ubiquitous Language is the shared vocabulary used consistently by both developers and domain experts to ensure clear communication between the model and the business domain.
Raw{"answer": "yes", "explanation": "In Domain-Driven Design, Ubiquitous Language is the shared vocabulary used consistently by both developers and domain experts to ensure clear communication between the model and the business domain."} | верно | Evans: язык из требований переходит в имена классов и методов. |
T26-L6 4.48 c | DDD | What is the boundary called within which a model and its language are consistent, while outside the same words mean other models? | «domain» Пояснение: In model theory, the domain (or universe of discourse) is the boundary within which a model consistently interprets its language, while outside it the same symbols may be interpreted differently in other models.
Raw{"answer": "domain", "explanation": "In model theory, the domain (or universe of discourse) is the boundary within which a model consistently interprets its language, while outside it the same symbols may be interpreted differently in other models."} | неверно верный: «bounded context» | Bounded Context; «Заказ» в биллинге и в доставке — разные модели. |
T26-L7 1.34 c | DDD | An anemic model (objects with only getters/setters, logic in services) is the recommended DDD style. | «no» Пояснение: DDD explicitly advocates for rich domain models where entities and value objects encapsulate their own business logic, making anemic models (data-only objects with logic in services) an anti-pattern in DDD.
Raw{"answer": "no", "explanation": "DDD explicitly advocates for rich domain models where entities and value objects encapsulate their own business logic, making anemic models (data-only objects with logic in services) an anti-pattern in DDD."} | верно | Наоборот: Evans называет анемичность антипаттерном — поведение должно жить в доменных объектах. |
T26-L8 1.98 c | DDD | Bounded context means each context has its own model: the same concept in different contexts is a different class. | «yes» Пояснение: In DDD, a bounded context defines its own internal model, so the same universal concept (e.g., 'Product') can be represented by different classes with different attributes in different contexts.
Raw{"answer": "yes", "explanation": "In DDD, a bounded context defines its own internal model, so the same universal concept (e.g., 'Product') can be represented by different classes with different attributes in different contexts."} | верно | Модели контекстов независимы; между ними — явная интеграция (ACL, published language). |
T13-L1 1.09 c | Symfony | Services in the Symfony DI container are created lazily by default — on first use. | «yes» Пояснение: Symfony's DI container defines services and their dependencies but does not instantiate them until they are actually requested (i.e., on first use).
Raw{"answer": "yes", "explanation": "Symfony's DI container defines services and their dependencies but does not instantiate them until they are actually requested (i.e., on first use)."} | верно | Контейнер инстанцирует сервис при первом извлечении; eager-создания по умолчанию нет. |
T13-L2 1.62 c | Symfony | Which Symfony console command lists all registered routes? | «debug:router» Пояснение: The Symfony console command `debug:router` lists all registered routes in the application.
Raw{"answer": "debug:router", "explanation": "The Symfony console command `debug:router` lists all registered routes in the application."} | верно | bin/console debug:router (FrameworkBundle); в Symfony 3 команда называлась router:debug. |
T13-L3 1.51 c | Symfony | Symfony autowiring requires manually declaring every service in services.yaml. | «no» Пояснение: Symfony autowiring automatically resolves dependencies via type hints, so you do not need to manually declare every service in services.yaml; only services that cannot be auto-resolved require explicit configuration.
Raw{"answer": "no", "explanation": "Symfony autowiring automatically resolves dependencies via type hints, so you do not need to manually declare every service in services.yaml; only services that cannot be auto-resolved require explicit configuration."} | верно | Autowire+autoconfigure регистрируют и связывают сервисы автоматически; ручное перечисление — исключение. |
T13-L4 1.05 c | Symfony | Twig templates are compiled into PHP classes and cached between requests. | «yes» Пояснение: Twig compiles templates into PHP classes (extending Twig\Template) and caches the compiled output to avoid re-compilation on subsequent requests.
Raw{"answer": "yes", "explanation": "Twig compiles templates into PHP classes (extending Twig\\Template) and caches the compiled output to avoid re-compilation on subsequent requests."} | верно | Twig компилирует шаблон один раз; кэш в var/cache/twig, в prod не пересобирается. |
T13-L5 2.29 c | Symfony | In the Symfony dev environment the DI container is rebuilt only after tracked files change, not on every request. | «yes» Пояснение: In Symfony's dev environment the container is compiled once and cached; it is only rebuilt when the modification times of tracked files (config, service definitions, etc.) indicate a change, not on every request.
Raw{"answer": "yes", "explanation": "In Symfony's dev environment the container is compiled once and cached; it is only rebuilt when the modification times of tracked files (config, service definitions, etc.) indicate a change, not on every request."} | верно | Kernel проверяет freshness ресурсов (конфиги, классы); иначе переиспользуется кэш контейнера. |
T13-L6 1.88 c | Symfony | Which environment variable selects the active Symfony environment (dev/prod)? | «app_env» Пояснение: In Symfony (5+), the APP_ENV environment variable (e.g., APP_ENV=prod or APP_ENV=dev) selects the active runtime environment.
Raw{"answer": "APP_ENV", "explanation": "In Symfony (5+), the APP_ENV environment variable (e.g., APP_ENV=prod or APP_ENV=dev) selects the active runtime environment."} | верно | APP_ENV в .env; APP_DEBUG — отдельный флаг отладки. |
T13-L7 1.04 c | Symfony | A controller method can be private — Symfony routing works with any method of the class. | «no» Пояснение: Symfony controller methods must be public; private or protected methods cannot be invoked by the routing/controller resolver.
Raw{"answer": "no", "explanation": "Symfony controller methods must be public; private or protected methods cannot be invoked by the routing/controller resolver."} | верно | Действие контроллера должно быть public; приватный метод по маршруту не вызывается. |
T13-L8 1.94 c | Symfony | Event subscribers always receive events before listeners, because the interface gives them priority. | «no» Пояснение: In frameworks like Symfony, the call order of event subscribers and listeners is determined by their numeric priority value, not by whether they implement a subscriber interface; a subscriber with a lower priority is called after a listener with a higher priority.
Raw{"answer": "no", "explanation": "In frameworks like Symfony, the call order of event subscribers and listeners is determined by their numeric priority value, not by whether they implement a subscriber interface; a subscriber with a lower priority is called after a listener with a higher priority."} | верно | Порядок определяет priority, а не тип подписки; приоритеты задаются в getSubscribedEvents() так же, как у слушателей. |
T22-L1 1.58 c | Symfony: Security and forms | In modern Symfony (6.0+) authentication is built on authenticator classes (AuthenticatorInterface); the old guard system has been removed. | «yes» Пояснение: The guard authentication system was deprecated in Symfony 5.3 and removed in 6.0, replaced by the new AuthenticatorInterface-based system.
Raw{"answer": "yes", "explanation": "The guard authentication system was deprecated in Symfony 5.3 and removed in 6.0, replaced by the new AuthenticatorInterface-based system."} | верно | Guard объявлен устаревшим в 5.3 и удалён в 6.0; в проекте symfony/security-bundle 8.1. |
T22-L2 1.81 c | Symfony: Security and forms | Which Symfony attribute checks a role/permission right on a controller method (403 without it)? | «isgranted» Пояснение: The #[IsGranted] attribute in Symfony checks a role or permission on a controller method and returns a 403 Forbidden response if the user lacks the required access.
Raw{"answer": "IsGranted", "explanation": "The #[IsGranted] attribute in Symfony checks a role or permission on a controller method and returns a 403 Forbidden response if the user lacks the required access."} | верно | #[IsGranted('ROLE_ADMIN')]; атрибут из symfony/security-http. |
T22-L3 1.04 c | Symfony: Security and forms | Voters are Symfony's mechanism for checking access to a specific object: isGranted('EDIT', $post). | «yes» Пояснение: Symfony Voters are the built-in mechanism for object-level security, allowing you to check permissions on a specific subject (e.g., isGranted('EDIT', $post)).
Raw{"answer": "yes", "explanation": "Symfony Voters are the built-in mechanism for object-level security, allowing you to check permissions on a specific subject (e.g., isGranted('EDIT', $post))."} | верно | VoterInterface->vote(); docs Symfony — Voters. |
T22-L4 2.49 c | Symfony: Security and forms | In modern Symfony (7+) validation constraints are declared as PHP attributes (#[Assert\NotBlank]); doctrine annotations are no longer supported. | «yes» Пояснение: Symfony 7+ (requiring PHP 8.2+) removed support for the old Doctrine Annotations syntax and mandates native PHP attributes (e.g. #[Assert\NotBlank]) for validation constraints.
Raw{"answer": "yes", "explanation": "Symfony 7+ (requiring PHP 8.2+) removed support for the old Doctrine Annotations syntax and mandates native PHP attributes (e.g. #[Assert\\NotBlank]) for validation constraints."} | верно | Докблок-аннотации удалены в Symfony 7.0; стандарт — атрибуты. В проекте symfony/validator 8.1. |
T22-L5 1.1 c | Symfony: Security and forms | CSRF protection of Symfony forms is enabled by default: the form validates the token on submission. | «yes» Пояснение: Symfony's Form component enables CSRF protection by default; a CSRF token field is automatically added to every form and validated on submission unless explicitly disabled.
Raw{"answer": "yes", "explanation": "Symfony's Form component enables CSRF protection by default; a CSRF token field is automatically added to every form and validated on submission unless explicitly disabled."} | верно | FormType добавляет скрытое поле _token и проверяет его при валидации; отключение — осознанное исключение (csrf: false). |
T22-L6 1.05 c | Symfony: Security and forms | Form validation in Symfony runs server-side even if the client-side (HTML5) checks passed. | «yes» Пояснение: Symfony always performs server-side form validation regardless of client-side (HTML5) validation results, as client-side checks are only for UX and cannot be trusted.
Raw{"answer": "yes", "explanation": "Symfony always performs server-side form validation regardless of client-side (HTML5) validation results, as client-side checks are only for UX and cannot be trusted."} | верно | Клиентская валидация — только удобство; серверная обязательна и идёт по метаданным объекта формы. |
T22-L7 0.67 c | Symfony: Security and forms | Which Symfony maker command generates a form class (FormType)? | «make:form» Пояснение: The Symfony MakerBundle command 'make:form' generates a FormType class for creating forms.
Raw{"answer": "make:form", "explanation": "The Symfony MakerBundle command 'make:form' generates a FormType class for creating forms."} | верно | bin/console make:form (symfony/maker-bundle — в проекте). |
T22-L8 1.53 c | Symfony: Security and forms | Symfony stores the user's password in the session in plain text. | «no» Пояснение: Symfony never stores the plain-text password in the session; it stores a hashed credential (e.g., bcrypt hash) as part of the security token, and the password itself is only used transiently during the authentication check.
Raw{"answer": "no", "explanation": "Symfony never stores the plain-text password in the session; it stores a hashed credential (e.g., bcrypt hash) as part of the security token, and the password itself is only used transiently during the authentication check."} | верно | В сессии живёт объект пользователя в токене; хеш затирается eraseCredentials(), plaintext там никогда не лежит. |
T23-L1 1.18 c | Symfony: configuration and services | Symfony bundle configuration lives in config/packages — one file per bundle or topic. | «yes» Пояснение: In Symfony 4+, bundle configuration is recommended to be stored in config/packages/, with one file per bundle or topic (e.g., doctrine.yaml, twig.yaml).
Raw{"answer": "yes", "explanation": "In Symfony 4+, bundle configuration is recommended to be stored in config/packages/, with one file per bundle or topic (e.g., doctrine.yaml, twig.yaml)."} | верно | Стандартная структура (config/packages/*.yaml); перегрузка — config/packages/<env>. |
T23-L2 3.68 c | Symfony: configuration and services | The .env file with dev defaults is committed to the repository, while real secrets live in the non-committed .env.local. | «yes» Пояснение: This is a common and recommended pattern (e.g., in Symfony): the committed .env holds safe dev defaults, while .env.local (gitignored) stores real secrets.
Raw{"answer": "yes", "explanation": "This is a common and recommended pattern (e.g., in Symfony): the committed .env holds safe dev defaults, while .env.local (gitignored) stores real secrets."} | верно | symfony/dotenv: .env — общий безопасный набор значений; локальные секреты — .env.local (gitignored) или secrets-хранилище. |
T23-L3 1.6 c | Symfony: configuration and services | Which Symfony command lists the container's registered services and their aliases? | «debug:container» Пояснение: The Symfony command 'debug:container' (alias 'container:debug') lists all services and their aliases registered in the service container.
Raw{"answer": "debug:container", "explanation": "The Symfony command 'debug:container' (alias 'container:debug') lists all services and their aliases registered in the service container."} | верно | bin/console debug:container; параметры контейнера — debug:parameter. |
T23-L4 6.62 c | Symfony: configuration and services | The Symfony container allows changing parameters at runtime: $container->setParameter() works from a controller. | «no» Пояснение: The Symfony container is frozen after compilation; while setParameter() exists on the base class, the container is designed to be immutable and modifying parameters at runtime is not a supported practice (already-injected services won't see the change).
Raw{"answer": "no", "explanation": "The Symfony container is frozen after compilation; while setParameter() exists on the base class, the container is designed to be immutable and modifying parameters at runtime is not a supported practice (already-injected services won't see the change)."} | верно | Контейнер компилируется и замораживается; runtime-значения — только через переменные окружения. |
T23-L5 0.9 c | Symfony: configuration and services | By default, Symfony services are public (public: true) — you can fetch them directly from the container. | «no» Пояснение: Since Symfony 4, services are private by default; you must explicitly set public: true to make them fetchable from the container.
Raw{"answer": "no", "explanation": "Since Symfony 4, services are private by default; you must explicitly set public: true to make them fetchable from the container."} | верно | С Symfony 4.0 сервисы по умолчанию private: инжектятся через autowiring; $container->get() — только для публичных. |
T23-L6 1.09 c | Symfony: configuration and services | Without a config file in config/packages a bundle will not work — configuration is mandatory for every bundle. | «no» Пояснение: Many Symfony bundles work perfectly fine without any configuration file in config/packages/; configuration is optional for most bundles.
Raw{"answer": "no", "explanation": "Many Symfony bundles work perfectly fine without any configuration file in config/packages/; configuration is optional for most bundles."} | верно | У бандлов есть встроенные умолчания (Extension); конфиг нужен только для отклонений от них. |
T23-L7 0.8 c | Symfony: configuration and services | Environment variable values are injected into services.yaml using the %env(VAR)% syntax. | «yes» Пояснение: In Symfony, environment variables are referenced in configuration files like services.yaml using the %env(VAR_NAME)% syntax.
Raw{"answer": "yes", "explanation": "In Symfony, environment variables are referenced in configuration files like services.yaml using the %env(VAR_NAME)% syntax."} | верно | %env(...)% резолвится в рантайме env-процессорами; docs — Env Var Processors. |
T23-L8 2.03 c | Symfony: configuration and services | Which Symfony environment variable enables debug mode (affects the profiler and Twig debugging)? | «app_debug» Пояснение: In Symfony, the APP_DEBUG environment variable (set in .env) enables debug mode, which activates the profiler and Twig's debug features.
Raw{"answer": "APP_DEBUG", "explanation": "In Symfony, the APP_DEBUG environment variable (set in .env) enables debug mode, which activates the profiler and Twig's debug features."} | верно | APP_DEBUG=1 (в .env dev-окружения); окружение выбирает APP_ENV — см. T13-L6. |
T16-L1 2.23 c | Symfony: Messenger | A single message in Symfony Messenger can only have one handler. | «no» Пояснение: Symfony Messenger allows registering multiple handlers for the same message class, and they can be invoked in priority order.
Raw{"answer": "no", "explanation": "Symfony Messenger allows registering multiple handlers for the same message class, and they can be invoked in priority order."} | верно | Messenger вызывает все хендлеры, подписанные на класс сообщения (docs — Multiple Handlers). |
T16-L2 1.02 c | Symfony: Messenger | The sync transport in Messenger queues the message for a worker, just like async. | «no» Пояснение: The sync transport handles the message immediately in the same process; it does not queue it for a worker like async transports do.
Raw{"answer": "no", "explanation": "The sync transport handles the message immediately in the same process; it does not queue it for a worker like async transports do."} | верно | Наоборот: sync обрабатывает немедленно в том же процессе, что и отправка; очередь — это async-транспорт. |
T16-L3 0.87 c | Symfony: Messenger | Which console command starts the worker that processes Messenger queue messages? | «messenger:consume» Пояснение: The Symfony console command `messenger:consume` starts a worker process that pulls and processes messages from Messenger queues.
Raw{"answer": "messenger:consume", "explanation": "The Symfony console command `messenger:consume` starts a worker process that pulls and processes messages from Messenger queues."} | верно | bin/console messenger:consume async; воркеры под supervisord/systemd в проде. |
T16-L4 3.05 c | Symfony: Messenger | Retries for failed messages (retry_strategy) are configured per Messenger transport. | «yes» Пояснение: In Symfony Messenger, the retry_strategy (max_retries, delay, multiplier, etc.) is configured per transport in the framework configuration, with an optional global default.
Raw{"answer": "yes", "explanation": "In Symfony Messenger, the retry_strategy (max_retries, delay, multiplier, etc.) is configured per transport in the framework configuration, with an optional global default."} | верно | retry_strategy на транспорте: max_retries, delay, multiplier; docs — Failed Messages & Retries. |
T16-L5 1.83 c | Symfony: Messenger | By default, Messenger serializes messages to JSON. | «yes» Пояснение: Symfony Messenger's SerializerTransport uses the Symfony Serializer component with JSON as the default serialization format.
Raw{"answer": "yes", "explanation": "Symfony Messenger's SerializerTransport uses the Symfony Serializer component with JSON as the default serialization format."} | неверно верный: «no» | Дефолтный сериализатор — PhpSerializer (serialize()); JSON-сериализатор включается отдельно. |
T16-L6 1.72 c | Symfony: Messenger | Symfony Scheduler produces messages on a schedule and dispatches them through Messenger. | «no» Пояснение: Symfony Scheduler schedules recurring tasks (closures/callbacks) to run at intervals; it does not dispatch messages through the Messenger component.
Raw{"answer": "no", "explanation": "Symfony Scheduler schedules recurring tasks (closures/callbacks) to run at intervals; it does not dispatch messages through the Messenger component."} | неверно верный: «yes» | Schedule → RecurringMessage → шина Messenger; docs — Scheduler. |
T16-L7 1.17 c | Symfony: Messenger | Which built-in Messenger transport stores messages in database tables via Doctrine? | «doctrine» Пояснение: Symfony Messenger's built-in Doctrine transport (doctrine://) persists messages in database tables managed by Doctrine.
Raw{"answer": "doctrine", "explanation": "Symfony Messenger's built-in Doctrine transport (doctrine://) persists messages in database tables managed by Doctrine."} | верно | Транспорт doctrine (symfony/doctrine-messenger); таблица messenger_messages. В проекте стоит amqp-messenger + doctrine-messenger. |
T16-L8 1.2 c | Symfony: Messenger | The Messenger pipeline can be extended with custom middleware, placed before or after the built-in ones. | «yes» Пояснение: Symfony's Messenger middleware pipeline is fully extensible; you can register custom middleware at any position in the chain, before or after the built-in ones.
Raw{"answer": "yes", "explanation": "Symfony's Messenger middleware pipeline is fully extensible; you can register custom middleware at any position in the chain, before or after the built-in ones."} | верно | messenger.bus.*.middleware в yaml; docs — Middleware. |
T28-L1 1.34 c | Symfony: versions | Symfony major releases come every two years, minor ones every six months (in May and November). | «no» Пояснение: Symfony major releases come every year, not every two years; minor releases do follow a six-month (May/November) cadence.
Raw{"answer": "no", "explanation": "Symfony major releases come every year, not every two years; minor releases do follow a six-month (May/November) cadence."} | неверно верный: «yes» | Стандартный релизный цикл: 8.0 — ноябрь 2025, 8.1 — май 2026, 8.2 — ноябрь 2026. |
T28-L2 0.93 c | Symfony: versions | What is the minimum PHP version required by Symfony 8? | «8.4» Пояснение: Symfony 8 requires PHP 8.4 as its minimum supported version.
Raw{"answer": "8.4", "explanation": "Symfony 8 requires PHP 8.4 as its minimum supported version."} | верно | Symfony 8.0 поднял требование до PHP >= 8.4.1 (в vendor проекта: "php": ">=8.4.1"). |
T28-L3 1.85 c | Symfony: versions | Symfony 7.0 kept support for docblock annotations (validation, routes). | «no» Пояснение: Symfony 7.0 removed support for docblock annotations; you must use PHP 8 attributes (or configuration) instead.
Raw{"answer": "no", "explanation": "Symfony 7.0 removed support for docblock annotations; you must use PHP 8 attributes (or configuration) instead."} | верно | Наоборот: в 7.0 аннотации удалены — только PHP-атрибуты (#[Route], #[Assert\NotBlank]). |
T28-L4 1.09 c | Symfony: versions | AssetMapper manages CSS/JS without node or webpack — via importmap.php. | «yes» Пояснение: Symfony's AssetMapper component manages CSS/JS assets without requiring Node.js or webpack, using an importmap.php file to track and resolve imports.
Raw{"answer": "yes", "explanation": "Symfony's AssetMapper component manages CSS/JS assets without requiring Node.js or webpack, using an importmap.php file to track and resolve imports."} | верно | symfony/asset-mapper (с 6.3, стандарт с 7.x); в проекте — importmap.php в корне и asset-mapper 8.1. |
T28-L5 2.05 c | Symfony: versions | Symfony 6.4 is a regular release without long-term support. | «no» Пояснение: Symfony 6.4 is an even-numbered minor release, which qualifies as a Long-Term Support (LTS) release with extended bug-fix and security support.
Raw{"answer": "no", "explanation": "Symfony 6.4 is an even-numbered minor release, which qualifies as a Long-Term Support (LTS) release with extended bug-fix and security support."} | верно | Наоборот: 6.4 — LTS (расширенная поддержка); LTS выходит вместе с очередным мажором (6.4 — вместе с 7.0). |
T28-L6 1.3 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's deprecation policy means that features deprecated in one major version are removed in the next major version, so moving to a new major release does remove prior deprecations.
Raw{"answer": "no", "explanation": "Symfony's deprecation policy means that features deprecated in one major version are removed in the next major version, so moving to a new major release does remove prior deprecations."} | верно | Наоборот: мажорный релиз удаляет всё устаревшее (7.0 убрал деприкейшены 6.x, 8.0 — 7.x). |
T28-L7 1.13 c | Symfony: versions | Every Symfony major release is accompanied by an UPGRADE guide listing the changes. | «yes» Пояснение: Symfony includes an UPGRADE-<major>.<minor>.md file in the repository root for each major release documenting all breaking changes and deprecations.
Raw{"answer": "yes", "explanation": "Symfony includes an UPGRADE-<major>.<minor>.md file in the repository root for each major release documenting all breaking changes and deprecations."} | верно | UPGRADE-7.0.md, UPGRADE-8.0.md в репозитории symfony/symfony. |
T28-L8 1.09 c | Symfony: versions | Which Symfony component manages assets and the importmap without node/webpack? | «assetmapper» Пояснение: Symfony's AssetMapper component manages assets and integrates with ImportMap to handle JavaScript/CSS dependencies without requiring Node.js or webpack.
Raw{"answer": "AssetMapper", "explanation": "Symfony's AssetMapper component manages assets and integrates with ImportMap to handle JavaScript/CSS dependencies without requiring Node.js or webpack."} | верно | symfony/asset-mapper 8.1 — в проекте. |
T29-L1 4.36 c | Symfony: 8.2 and beyond | As of 2026-11-07, Symfony 8.2 has already been released. | «yes» Пояснение: Following Symfony's typical release cycle (major in November, .1 in ~May, .2 in ~November), Symfony 8.0 would land in November 2025 and 8.2 in November 2026, consistent with the date given.
Raw{"answer": "yes", "explanation": "Following Symfony's typical release cycle (major in November, .1 in ~May, .2 in ~November), Symfony 8.0 would land in November 2025 and 8.2 in November 2026, consistent with the date given."} | неверно верный: «no» | Наоборот: 8.2 ещё не выпущена — релиз в конце ноября 2026; последняя стабильная — 8.1. |
T29-L2 2.58 c | Symfony: 8.2 and beyond | As of 2026-11-07, Symfony 8.2 is scheduled for November 2026, following the usual six-month cycle. | «yes» Пояснение: Symfony follows a six-month minor release cycle (May and November), so after 8.0 in November 2025 and 8.1 in May 2026, 8.2 would indeed be scheduled for November 2026.
Raw{"answer": "yes", "explanation": "Symfony follows a six-month minor release cycle (May and November), so after 8.0 in November 2025 and 8.1 in May 2026, 8.2 would indeed be scheduled for November 2026."} | верно | Политика релизов: 8.1 — май 2026, 8.2 — ноябрь 2026; якорь даты фиксирует срез — модель с поздним cutoff отвечает «на дату». |
T29-L3 1.67 c | Symfony: 8.2 and beyond | Which Symfony version comes after 8.1 (as of 2026-11-07)? | «8.2» Пояснение: Symfony follows a sequential minor release cycle, so the version after 8.1 is 8.2.
Raw{"answer": "8.2", "explanation": "Symfony follows a sequential minor release cycle, so the version after 8.1 is 8.2."} | верно | 8.2 — следующий минорный релиз (ноябрь 2026); после его выхода проект переходит с 8.1.* на 8.2.*. |
T29-L4 2.15 c | Symfony: 8.2 and beyond | Symfony 8.2 is a major release requiring applications to be rewritten for new APIs. | «no» Пояснение: Symfony 8.2 does not exist as a released version, and even major Symfony releases follow semantic versioning with deprecation paths rather than requiring a full rewrite.
Raw{"answer": "no", "explanation": "Symfony 8.2 does not exist as a released version, and even major Symfony releases follow semantic versioning with deprecation paths rather than requiring a full rewrite."} | верно | Наоборот: 8.2 — минорный релиз; новые возможности без поломки обратной совместимости. Мажор — 9.0. |
T29-L5 1.61 c | Symfony: 8.2 and beyond | Updating within a major branch (8.1 → 8.2) should not require code changes — backward compatibility is preserved. | «yes» Пояснение: PHP follows a policy where minor version updates within the same major branch (e.g., 8.1 to 8.2) maintain backward compatibility and do not require code changes.
Raw{"answer": "yes", "explanation": "PHP follows a policy where minor version updates within the same major branch (e.g., 8.1 to 8.2) maintain backward compatibility and do not require code changes."} | верно | Политика Symfony: минорные релизы обратно совместимы; BC-break допустим только в мажорных. |
T29-L6 3.01 c | Symfony: 8.2 and beyond | Which minor version of the 8.x branch is released last, before Symfony 9.0? | «8.4» Пояснение: Following Symfony's consistent release pattern where each major branch ends at .4 (4.4, 5.4, 6.4, 7.4), the last minor version of the 8.x branch before 9.0 is 8.4.
Raw{"answer": "8.4", "explanation": "Following Symfony's consistent release pattern where each major branch ends at .4 (4.4, 5.4, 6.4, 7.4), the last minor version of the 8.x branch before 9.0 is 8.4."} | верно | По циклу: 8.2 (ноя 2026), 8.3 (май 2027), 8.4 (ноя 2027, вместе с 9.0) — как 6.4 выходила вместе с 7.0. |
T29-L7 2.98 c | Symfony: 8.2 and beyond | Symfony 8.2 will require PHP 8.5 — you would have to upgrade PHP along with it. | «no» Пояснение: Symfony 8.2 is not a known or announced release; as of current versions, Symfony 7.x requires PHP 8.2+, and no Symfony 8.2 with a PHP 8.5 requirement has been confirmed.
Raw{"answer": "no", "explanation": "Symfony 8.2 is not a known or announced release; as of current versions, Symfony 7.x requires PHP 8.2+, and no Symfony 8.2 with a PHP 8.5 requirement has been confirmed."} | верно | Наоборот: минорные релизы не поднимают требования PHP; для всей ветки 8.x остаётся PHP >= 8.4. |
T29-L8 3.2 c | Symfony: 8.2 and beyond | Deprecations added in the 8.x branch will not be removed before Symfony 9.0. | «yes» Пояснение: Symfony's deprecation policy guarantees that deprecations introduced in a major version (8.x) remain for the entire lifecycle of that major version and are only removed in the next major release (9.0).
Raw{"answer": "yes", "explanation": "Symfony's deprecation policy guarantees that deprecations introduced in a major version (8.x) remain for the entire lifecycle of that major version and are only removed in the next major release (9.0)."} | верно | Политика: деприкейшены живут до следующего мажора; 9.0 — ноябрь 2027. |
T21-L1 1.65 c | Twig | Inside {{ }}, Twig allows calling arbitrary PHP code directly. | «no» Пояснение: Twig's {{ }} tags only allow a limited set of expression syntax (variables, filters, method calls on whitelisted objects, arithmetic, etc.) and do not permit calling arbitrary PHP code directly.
Raw{"answer": "no", "explanation": "Twig's {{ }} tags only allow a limited set of expression syntax (variables, filters, method calls on whitelisted objects, arithmetic, etc.) and do not permit calling arbitrary PHP code directly."} | верно | Twig — DSL: только разрешённые окружением функции/фильтры; произвольный PHP не исполняется. |
T21-L2 0.62 c | Twig | By default, Twig auto-escapes printed variables. | «yes» Пояснение: Twig enables auto-escaping by default to prevent XSS attacks, automatically escaping variables printed with {{ }}.
Raw{"answer": "yes", "explanation": "Twig enables auto-escaping by default to prevent XSS attacks, automatically escaping variables printed with {{ }}."} | верно | Autoescape включён по умолчанию; {{ '<b>' }} → <b>. Проверено на Twig 3.30. |
T21-L3 1.23 c | Twig | The Twig |e filter escapes a string for safe output in an HTML context. | «yes» Пояснение: The Twig |e (escape) filter defaults to escaping a string for safe HTML output using htmlspecialchars with ENT_QUOTES.
Raw{"answer": "yes", "explanation": "The Twig |e (escape) filter defaults to escaping a string for safe HTML output using htmlspecialchars with ENT_QUOTES."} | верно | |e ('html') по умолчанию; есть контексты js/url/css. От SQL-инъекций он не защищает — это задача подготовленных запросов Doctrine. |
T21-L4 0.84 c | Twig | Which filter from twig/intl-extra formats a number according to a locale? | «localnumber» Пояснение: The localnumber filter in twig/intl-extra formats a number according to a given locale using the Intl\NumberFormatter class.
Raw{"answer": "localnumber", "explanation": "The localnumber filter in twig/intl-extra formats a number according to a given locale using the Intl\\NumberFormatter class."} | неверно верный: «format_number» | |format_number(locale=...) из IntlExtension (twig/intl-extra есть в проекте). Проверено на Twig 3.30: 12345.6 → 12 345,6 (ru). |
T21-L5 1.18 c | Twig | The |raw filter disables auto-escaping for the value. | «yes» Пояснение: The |raw filter (used in Twig templating) marks a value as safe and prevents automatic HTML escaping.
Raw{"answer": "yes", "explanation": "The |raw filter (used in Twig templating) marks a value as safe and prevents automatic HTML escaping."} | верно | {{ x|raw }} выводит HTML как есть; опасно с пользовательскими данными. Проверено на Twig 3.30. |
T21-L6 1.09 c | Twig | In Twig, {{ }} prints an expression value, while {% %} executes tags — conditions, loops, set. | «yes» Пояснение: In Twig, {{ }} outputs the value of an expression, while {% %} is used for structural tags such as if, for, set, and other control flow.
Raw{"answer": "yes", "explanation": "In Twig, {{ }} outputs the value of an expression, while {% %} is used for structural tags such as if, for, set, and other control flow."} | верно | Два блока синтаксиса Twig: вывод (echo) против логики. |
T21-L7 0.86 c | Twig | In Twig you cannot declare a variable inside a template — values only come from the controller. | «no» Пояснение: Twig allows you to declare variables inside a template using the {% set %} tag, so values are not limited to coming from the controller.
Raw{"answer": "no", "explanation": "Twig allows you to declare variables inside a template using the {% set %} tag, so values are not limited to coming from the controller."} | верно | {% set y = ... %} объявляет переменную в шаблоне. Проверено на Twig 3.30. |
T21-L8 0.75 c | Twig | Which Twig function dumps the debug structure of a variable (array, object)? | «dump» Пояснение: The Twig `dump()` function (from the Twig Debug extension) outputs the debug structure of a variable such as an array or object.
Raw{"answer": "dump", "explanation": "The Twig `dump()` function (from the Twig Debug extension) outputs the debug structure of a variable such as an array or object."} | верно | {{ dump(x) }} (DebugExtension; в Symfony доступна в dev-окружении). |
T24-L1 1.08 c | Bootstrap | Bootstrap is a CSS/JS library of ready-made UI components, not an SPA framework. | «yes» Пояснение: Bootstrap is a front-end CSS/JS component library providing ready-made UI elements (navbar, modal, carousel, etc.), not a Single Page Application framework like React, Angular, or Vue.
Raw{"answer": "yes", "explanation": "Bootstrap is a front-end CSS/JS component library providing ready-made UI elements (navbar, modal, carousel, etc.), not a Single Page Application framework like React, Angular, or Vue."} | верно | Компоненты и утилиты поверх вашего HTML; SPA-фреймворки (React/Vue) — другой класс инструментов. В проекте vendored 5.3.3. |
T24-L2 1.08 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 fixed-width container with a max-width that changes at each breakpoint, unlike .container-fluid which is always 100% wide.
Raw{"answer": "container", "explanation": "The .container class in Bootstrap provides a responsive fixed-width container with a max-width that changes at each breakpoint, unlike .container-fluid which is always 100% wide."} | верно | .container (фиксированная макс-ширина по брейкпоинтам) vs .container-fluid (на всю ширину). |
T24-L3 1.23 c | Bootstrap | The Bootstrap grid is built on CSS floats and splits a row into 16 columns. | «no» Пояснение: Bootstrap's grid uses 12 columns (not 16), and modern versions (Bootstrap 4+) are built on CSS Flexbox rather than CSS floats.
Raw{"answer": "no", "explanation": "Bootstrap's grid uses 12 columns (not 16), and modern versions (Bootstrap 4+) are built on CSS Flexbox rather than CSS floats."} | верно | Наоборот: flexbox (с Bootstrap 4) и 12 колонок; float-сетка — это Bootstrap 3. |
T24-L4 2.68 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 breakpoint infixes used in class names are sm, md, lg, xl, and xxl (the default xs has no infix), giving exactly five.
Raw{"answer": "yes", "explanation": "In Bootstrap 5, the breakpoint infixes used in class names are sm, md, lg, xl, and xxl (the default xs has no infix), giving exactly five."} | верно | Тиров всего шесть: xs (без инфикса) + пять именованных (576/768/992/1200/1400 px). |
T24-L5 1.47 c | Bootstrap | Utilities like .mt-3 or .px-2 use the spacing scale: the number is a multiple of $spacer. | «yes» Пояснение: In Bootstrap, spacing utilities like .mt-3 or .px-2 compute their value as the number multiplied by $spacer (e.g., 3 × 1rem = 3rem).
Raw{"answer": "yes", "explanation": "In Bootstrap, spacing utilities like .mt-3 or .px-2 compute their value as the number multiplied by $spacer (e.g., 3 × 1rem = 3rem)."} | неверно верный: «no» | Spacing utilities; $spacer = 1rem. |
T24-L6 0.74 c | Bootstrap | Which Bootstrap 5 data attribute enables an interactive component (e.g. dropdown) on an element? | «data-bs-toggle» Пояснение: In Bootstrap 5, the data-bs-toggle attribute is used to enable interactive components such as dropdowns, collapse, or tooltips on an element.
Raw{"answer": "data-bs-toggle", "explanation": "In Bootstrap 5, the data-bs-toggle attribute is used to enable interactive components such as dropdowns, collapse, or tooltips on an element."} | верно | data-bs-toggle="dropdown" и т.п.; в Bootstrap 4 атрибут назывался data-toggle. |
T24-L7 0.81 c | Bootstrap | Bootstrap 5 components work without jQuery — in plain vanilla JS. | «yes» Пояснение: Bootstrap 5 removed the jQuery dependency and all its interactive components (modals, dropdowns, tooltips, etc.) are powered by vanilla JavaScript.
Raw{"answer": "yes", "explanation": "Bootstrap 5 removed the jQuery dependency and all its interactive components (modals, dropdowns, tooltips, etc.) are powered by vanilla JavaScript."} | верно | jQuery удалён в Bootstrap 5.0: data-bs-* атрибуты и JS API. В проекте vendored 5.3.3. |
T24-L8 1.59 c | Bootstrap | Dark mode in Bootstrap is enabled with a .dark class on the root element. | «no» Пояснение: In Bootstrap 5, dark mode is enabled by adding the data-bs-theme="dark" attribute to the <html> element, not by adding a .dark class.
Raw{"answer": "no", "explanation": "In Bootstrap 5, dark mode is enabled by adding the data-bs-theme=\"dark\" attribute to the <html> element, not by adding a .dark class."} | верно | Наоборот: тема включается атрибутом data-bs-theme="dark" (Color modes, с 5.3); класса .dark не существует. В проекте 5.3.3. |
T14-L1 1.36 c | Doctrine | Doctrine ORM creates database tables on the fly the first time an entity is used at runtime. | «no» Пояснение: Doctrine ORM does not auto-create tables at runtime; you must explicitly use SchemaTool, migrations, or manual SQL to create or alter database schema.
Raw{"answer": "no", "explanation": "Doctrine ORM does not auto-create tables at runtime; you must explicitly use SchemaTool, migrations, or manual SQL to create or alter database schema."} | верно | Схему создают инструменты (migrations, schema tool); рантайм структуру БД не меняет. |
T14-L2 0.85 c | Doctrine | Which EntityManager method marks a new object as managed without executing SQL until flush()? | «persist» Пояснение: EntityManager::persist() marks a new entity as managed and queues it for insertion, but no SQL is executed until flush() is called.
Raw{"answer": "persist", "explanation": "EntityManager::persist() marks a new entity as managed and queues it for insertion, but no SQL is executed until flush() is called."} | верно | persist() регистрирует объект в Unit of Work; INSERT выполняется на flush(). |
T14-L3 2.19 c | Doctrine | In Doctrine ORM 3, the EntityManager::merge() method exists and makes the passed object managed. | «yes» Пояснение: In Doctrine ORM 3, EntityManager::merge() still exists and its purpose is to make a detached entity managed, returning the managed instance.
Raw{"answer": "yes", "explanation": "In Doctrine ORM 3, EntityManager::merge() still exists and its purpose is to make a detached entity managed, returning the managed instance."} | неверно верный: «no» | В ORM 3 merge() удалён (в vendor проекта 3.7.6 метода нет); в Doctrine 2.x merge() возвращал управляемую копию. Версия зафиксирована — ORM 3. |
T14-L4 0.95 c | Doctrine | DQL queries are written in terms of entities and their fields, not tables and columns. | «yes» Пояснение: DQL (Doctrine Query Language) is an object-oriented query language that operates on entities and their fields, abstracting away the underlying database tables and columns.
Raw{"answer": "yes", "explanation": "DQL (Doctrine Query Language) is an object-oriented query language that operates on entities and their fields, abstracting away the underlying database tables and columns."} | верно | Doctrine транслирует DQL в SQL; docs — DQL (Doctrine Query Language). |
T14-L5 2.07 c | Doctrine | What does $repository->find(999) return when no record with id 999 exists? | «null» Пояснение: In Doctrine, $repository->find() returns null when no entity with the given ID exists in the database.
Raw{"answer": "null", "explanation": "In Doctrine, $repository->find() returns null when no entity with the given ID exists in the database."} | верно | find() возвращает null, если объект не найден (docs Repository methods). |
T14-L6 2.43 c | Doctrine | DoctrineBundle in Symfony automatically calls flush() at the end of every request. | «no» Пояснение: By default, DoctrineBundle does not automatically call flush() at the end of a request; the developer must explicitly call $entityManager->flush() to persist pending changes.
Raw{"answer": "no", "explanation": "By default, DoctrineBundle does not automatically call flush() at the end of a request; the developer must explicitly call $entityManager->flush() to persist pending changes."} | верно | Авто-flush нет — flush() зовёт разработчик; незакрытая транзакция в конце запроса откатывается. |
T14-L7 1.73 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» Пояснение: In Doctrine's Unit of Work, once an entity is in the managed state, any property modification is tracked against its original snapshot, and flush() automatically generates an UPDATE without needing persist() again.
Raw{"answer": "yes", "explanation": "In Doctrine's Unit of Work, once an entity is in the managed state, any property modification is tracked against its original snapshot, and flush() automatically generates an UPDATE without needing persist() again."} | верно | Dirty checking сравнивает снимки свойств; persist нужен только новым/отсоединённым объектам. |
T14-L8 1.12 c | Doctrine | remove() executes the SQL DELETE immediately, without waiting for flush(). | «no» Пояснение: In Doctrine ORM, remove() only schedules the entity for deletion in the Unit of Work; the actual SQL DELETE is sent to the database when flush() is called.
Raw{"answer": "no", "explanation": "In Doctrine ORM, remove() only schedules the entity for deletion in the Unit of Work; the actual SQL DELETE is sent to the database when flush() is called."} | верно | remove() планирует удаление в Unit of Work; DELETE выполняется на flush() (docs — Deleting Objects). |
T15-L1 1.18 c | PostgreSQL | PostgreSQL uses MVCC, therefore readers block writers and writers block readers. | «no» Пояснение: MVCC allows readers and writers to operate concurrently without blocking each other, which is the primary benefit of the multi-version concurrency control mechanism.
Raw{"answer": "no", "explanation": "MVCC allows readers and writers to operate concurrently without blocking each other, which is the primary benefit of the multi-version concurrency control mechanism."} | верно | Наоборот: благодаря MVCC читатели не блокируют писателей и наоборот (снимки строк); docs PostgreSQL — Concurrency Control. |
T15-L2 0.91 c | PostgreSQL | Which SQL command shows a query's execution plan without executing the query? | «explain» Пояснение: The EXPLAIN command displays the query execution plan (table access method, join order, indexes used) without actually running the query.
Raw{"answer": "EXPLAIN", "explanation": "The EXPLAIN command displays the query execution plan (table access method, join order, indexes used) without actually running the query."} | верно | EXPLAIN без ANALYZE только строит план; проверено на PostgreSQL 17.7. |
T15-L3 3.49 c | PostgreSQL | SERIAL and GENERATED ... AS IDENTITY are just two names for the same mechanism. | «no» Пояснение: While both use a sequence under the hood, SERIAL is a PostgreSQL shorthand (sequence + DEFAULT) whereas GENERATED ... AS IDENTITY is a SQL-standard column property with different semantics (no DEFAULT allowed, GENERATED ALWAYS vs BY DEFAULT, OVERRIDING SYSTEM VALUE), so they are not merely two names for the same mechanism.
Raw{"answer": "no", "explanation": "While both use a sequence under the hood, SERIAL is a PostgreSQL shorthand (sequence + DEFAULT) whereas GENERATED ... AS IDENTITY is a SQL-standard column property with different semantics (no DEFAULT allowed, GENERATED ALWAYS vs BY DEFAULT, OVERRIDING SYSTEM VALUE), so they are not merely two names for the same mechanism."} | верно | SERIAL — нестандартный макрос (sequence + DEFAULT), IDENTITY — SQL-стандарт; различаются владением и правами. Оба есть в PG 17 (проверено). |
T15-L4 1.02 c | PostgreSQL | By default, a PostgreSQL UNIQUE constraint allows only one row with NULL in the column. | «no» Пояснение: In PostgreSQL, a UNIQUE constraint treats NULL values as distinct, so multiple rows can have NULL in the constrained column.
Raw{"answer": "no", "explanation": "In PostgreSQL, a UNIQUE constraint treats NULL values as distinct, so multiple rows can have NULL in the constrained column."} | верно | Наоборот: NULLS DISTINCT по умолчанию — несколько NULL допустимы; NULLS NOT DISTINCT — опция с PG 15. Проверено на PG 17.7. |
T15-L5 0.78 c | PostgreSQL | Which PostgreSQL aggregate function concatenates strings with a separator? | «string_agg» Пояснение: PostgreSQL's string_agg() aggregate function concatenates strings with a specified separator, e.g. string_agg(col, ',').
Raw{"answer": "string_agg", "explanation": "PostgreSQL's string_agg() aggregate function concatenates strings with a specified separator, e.g. string_agg(col, ',')."} | верно | string_agg(значение, разделитель); проверено на PostgreSQL 17.7. |
T15-L6 1.47 c | PostgreSQL | Plain VACUUM returns the space occupied by dead tuples to the operating system. | «no» Пояснение: Plain VACUUM only marks dead tuple space as reusable within the table file; it does not return the space to the OS. Only VACUUM FULL rewrites the table and shrinks the file.
Raw{"answer": "no", "explanation": "Plain VACUUM only marks dead tuple space as reusable within the table file; it does not return the space to the OS. Only VACUUM FULL rewrites the table and shrinks the file."} | верно | VACUUM помечает место для переиспользования внутри таблицы; ОС его возвращает только VACUUM FULL (с эксклюзивной блокировкой). |
T15-L7 0.6 c | PostgreSQL | Which keyword in a window function definition partitions rows into groups the function is computed over? | «partition» Пояснение: In SQL window functions, the PARTITION BY clause divides rows into groups over which the window function is computed.
Raw{"answer": "PARTITION", "explanation": "In SQL window functions, the PARTITION BY clause divides rows into groups over which the window function is computed."} | неверно верный: «partition by» | OVER (PARTITION BY ...); проверено на PostgreSQL 17.7. |
T15-L8 1.14 c | PostgreSQL | The READ COMMITTED isolation level protects against non-repeatable reads. | «no» Пояснение: READ COMMITTED only prevents dirty reads; non-repeatable reads are prevented starting at the REPEATABLE READ isolation level.
Raw{"answer": "no", "explanation": "READ COMMITTED only prevents dirty reads; non-repeatable reads are prevented starting at the REPEATABLE READ isolation level."} | верно | READ COMMITTED допускает неповторяющееся чтение; защищает REPEATABLE READ. Проверено: SHOW transaction_isolation → read committed. |
T17-L1 0.89 c | PostgreSQL: transactions and indexes | By default, PostgreSQL wraps each single SQL statement in its own implicit transaction (autocommit). | «yes» Пояснение: By default, PostgreSQL operates in autocommit mode, meaning each individual SQL statement is automatically committed in its own implicit transaction unless you explicitly begin a transaction with BEGIN.
Raw{"answer": "yes", "explanation": "By default, PostgreSQL operates in autocommit mode, meaning each individual SQL statement is automatically committed in its own implicit transaction unless you explicitly begin a transaction with BEGIN."} | верно | Без BEGIN каждый оператор коммитится сам; docs PostgreSQL — Transactions. Проверено на PG 17. |
T17-L2 0.52 c | PostgreSQL: transactions and indexes | Which SQL command ends a transaction, committing all its changes? | «commit» Пояснение: The COMMIT statement finalizes a transaction, making all changes permanent and ending the transaction.
Raw{"answer": "COMMIT", "explanation": "The COMMIT statement finalizes a transaction, making all changes permanent and ending the transaction."} | верно | COMMIT (END — синоним). Проверено на PG 17. |
T17-L3 1.23 c | PostgreSQL: transactions and indexes | Indexes speed up more than SELECT: UPDATE and DELETE with a search on an indexed column benefit too. | «yes» Пояснение: Indexes help the database engine locate rows quickly for any DML statement (SELECT, UPDATE, DELETE) that filters on the indexed column, not just SELECT.
Raw{"answer": "yes", "explanation": "Indexes help the database engine locate rows quickly for any DML statement (SELECT, UPDATE, DELETE) that filters on the indexed column, not just SELECT."} | верно | Поиск строк для изменения идёт по индексу; docs PostgreSQL — Indexes. |
T17-L4 1.21 c | PostgreSQL: transactions and indexes | To roll back part of the statements inside a transaction, PostgreSQL uses SAVEPOINT. | «yes» Пояснение: SAVEPOINT allows you to mark a point within a transaction and later use ROLLBACK TO SAVEPOINT to undo only the statements executed after that point, without aborting the entire transaction.
Raw{"answer": "yes", "explanation": "SAVEPOINT allows you to mark a point within a transaction and later use ROLLBACK TO SAVEPOINT to undo only the statements executed after that point, without aborting the entire transaction."} | верно | SAVEPOINT name; ROLLBACK TO name — частичный откат без отмены всей транзакции. Проверено на PG 17. |
T17-L5 1.39 c | PostgreSQL: transactions and indexes | EXPLAIN ANALYZE shows the query plan without executing the query. | «no» Пояснение: EXPLAIN ANALYZE actually executes the query to collect real runtime statistics (actual rows, timing), whereas plain EXPLAIN shows the plan without executing.
Raw{"answer": "no", "explanation": "EXPLAIN ANALYZE actually executes the query to collect real runtime statistics (actual rows, timing), whereas plain EXPLAIN shows the plan without executing."} | верно | Наоборот: ANALYZE реально выполняет запрос (с побочными эффектами!) и показывает фактические времена узлов; план без выполнения — plain EXPLAIN. |
T17-L6 0.82 c | PostgreSQL: transactions and indexes | Which PostgreSQL extension adds vector types and indexes for embedding search? | «pgvector» Пояснение: pgvector is the PostgreSQL extension that adds a vector data type and index methods (IVFFlat and HNSW) for efficient similarity search on embeddings.
Raw{"answer": "pgvector", "explanation": "pgvector is the PostgreSQL extension that adds a vector data type and index methods (IVFFlat and HNSW) for efficient similarity search on embeddings."} | верно | CREATE EXTENSION vector (проект pgvector; в проекте образ pgvector/pgvector:pg17). |
T17-L7 0.83 c | PostgreSQL: transactions and indexes | A partial index (CREATE INDEX ... WHERE ...) is built only over rows satisfying the condition. | «yes» Пояснение: A partial index (CREATE INDEX ... WHERE ...) in PostgreSQL only indexes rows that satisfy the given predicate, making it smaller and more efficient.
Raw{"answer": "yes", "explanation": "A partial index (CREATE INDEX ... WHERE ...) in PostgreSQL only indexes rows that satisfy the given predicate, making it smaller and more efficient."} | верно | docs PostgreSQL — Partial Indexes; типичный кейс — индекс по «активным» записям. |
T17-L8 2.57 c | PostgreSQL: transactions and indexes | The SERIALIZABLE level in PostgreSQL is implemented by locking the rows a transaction reads. | «no» Пояснение: PostgreSQL implements SERIALIZABLE via Serializable Snapshot Isolation (SSI) with conflict detection, not by placing shared locks on read rows (that is MySQL/InnoDB's approach).
Raw{"answer": "no", "explanation": "PostgreSQL implements SERIALIZABLE via Serializable Snapshot Isolation (SSI) with conflict detection, not by placing shared locks on read rows (that is MySQL/InnoDB's approach)."} | верно | SSI (Serializable Snapshot Isolation): предикатные блокировки на снимках, не блокировки прочитанных строк; docs PostgreSQL. |
T19-L1 0.65 c | HTTP and REST API | HTTP status 201 means the request resulted in a new resource being created. | «yes» Пояснение: HTTP 201 Created indicates that the request has succeeded and a new resource has been created as a result.
Raw{"answer": "yes", "explanation": "HTTP 201 Created indicates that the request has succeeded and a new resource has been created as a result."} | верно | 201 Created; обычно на POST, часто с Location; RFC 9110. |
T19-L2 1.31 c | HTTP and REST API | Which HTTP status means a successful request with an empty response body (e.g. after DELETE)? | «204» Пояснение: HTTP 204 'No Content' indicates a successful request where the server intentionally returns no response body, commonly used after DELETE operations.
Raw{"answer": 204, "explanation": "HTTP 204 'No Content' indicates a successful request where the server intentionally returns no response body, commonly used after DELETE operations."} | верно | 204 No Content; RFC 9110. |
T19-L3 14.27 c | HTTP and REST API | The DELETE method is idempotent per the HTTP specification: repeating the request for the same resource does not change the outcome. | «yes» Пояснение: The HTTP specification (RFC 9110/7231) classifies DELETE as idempotent: deleting an already-deleted resource does not further change server state, so repeating the request yields the same end result.
Raw{"answer": "yes", "explanation": "The HTTP specification (RFC 9110/7231) classifies DELETE as idempotent: deleting an already-deleted resource does not further change server state, so repeating the request yields the same end result."} | верно | RFC 9110: DELETE идемпотентен (как PUT); идемпотентность ≠ безопасность — ресурс удаляется при первом вызове. |
T19-L4 1.17 c | HTTP and REST API | The Access-Control-Allow-Origin header is sent by the client so that the server agrees to accept requests from another origin. | «no» Пояснение: The Access-Control-Allow-Origin header is sent by the server (as a response header), not by the client; the client sends the Origin header instead.
Raw{"answer": "no", "explanation": "The Access-Control-Allow-Origin header is sent by the server (as a response header), not by the client; the client sends the Origin header instead."} | верно | Наоборот: заголовок шлёт СЕРВЕР в ответе, разрешая браузеру cross-origin запрос (CORS); в проекте nelmio/cors-bundle. |
T19-L5 0.73 c | HTTP and REST API | Status 429 Too Many Requests is used when a client exceeds a rate limit. | «yes» Пояснение: HTTP 429 Too Many Requests is the standard status code defined in RFC 6585 for indicating that a client has exceeded a rate limit.
Raw{"answer": "yes", "explanation": "HTTP 429 Too Many Requests is the standard status code defined in RFC 6585 for indicating that a client has exceeded a rate limit."} | верно | 429 (+ Retry-After); RFC 6585. В проекте symfony/rate-limiter. |
T19-L6 1.19 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 (e.g., 404 Not Found), while 5xx codes indicate server errors (e.g., 500 Internal Server Error).
Raw{"answer": "no", "explanation": "It is the opposite: 4xx codes indicate client errors (e.g., 404 Not Found), while 5xx codes indicate server errors (e.g., 500 Internal Server Error)."} | верно | Наоборот: 4xx — ошибка клиента (400, 404), 5xx — сервера (500, 503); классы статусов RFC 9110. |
T19-L7 0.44 c | HTTP and REST API | Which HTTP header indicates the MIME type of the request or response body? | «content-type» Пояснение: The Content-Type HTTP header specifies the MIME type of the request or response body.
Raw{"answer": "Content-Type", "explanation": "The Content-Type HTTP header specifies the MIME type of the request or response body."} | верно | Content-Type: application/json и т.п. |
T19-L8 1.19 c | HTTP and REST API | PATCH is not required to be idempotent per RFC 5789, unlike PUT. | «yes» Пояснение: RFC 5789 explicitly states that PATCH is not idempotent, whereas PUT (RFC 7231) is defined as idempotent.
Raw{"answer": "yes", "explanation": "RFC 5789 explicitly states that PATCH is not idempotent, whereas PUT (RFC 7231) is defined as idempotent."} | верно | RFC 5789 прямо оговаривает: PATCH не гарантированно идемпотентен; PUT идемпотентен. |
T20-L1 1.1 c | Security and OAuth | Checking a password by comparing its hash to the stored hash with a plain == is sufficient. | «no» Пояснение: Using == for hash comparison is vulnerable to timing attacks; one should use hash_equals() for a constant-time comparison.
Raw{"answer": "no", "explanation": "Using == for hash comparison is vulnerable to timing attacks; one should use hash_equals() for a constant-time comparison."} | верно | Нужна постоянновременная проверка (password_verify) — timing-атаки; соль и алгоритм уже внутри хеша. |
T20-L2 1.18 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» Пояснение: A CSRF token is indeed generated by the server, tied to the user's session, and validated on the server side when handling unsafe methods like POST, PUT, or DELETE.
Raw{"answer": "yes", "explanation": "A CSRF token is indeed generated by the server, tied to the user's session, and validated on the server side when handling unsafe methods like POST, PUT, or DELETE."} | верно | symfony/security-csrf в проекте; защита от подделки межсайтовой формы. |
T20-L3 0.83 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 enable and define the CSP policy for a web page.
Raw{"answer": "Content-Security-Policy", "explanation": "The Content-Security-Policy HTTP header is used to enable and define the CSP policy for a web page."} | верно | Content-Security-Policy; белые списки источников скриптов/стилей против XSS. |
T20-L4 2.27 c | Security and OAuth | OAuth 2.0 is an authentication protocol: the access token tells you who the user is. | «no» Пояснение: OAuth 2.0 is an authorization protocol (granting scoped access to resources), not an authentication protocol; identifying who the user is is the role of OpenID Connect (ID tokens), which layers on top of OAuth 2.0.
Raw{"answer": "no", "explanation": "OAuth 2.0 is an authorization protocol (granting scoped access to resources), not an authentication protocol; identifying who the user is is the role of OpenID Connect (ID tokens), which layers on top of OAuth 2.0."} | верно | OAuth 2.0 — авторизация/делегирование доступа; аутентификацию добавляет OpenID Connect. В проекте knpuniversity/oauth2-client-bundle (yandex/github/google). |
T20-L5 3.61 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 output encoding/escaping when rendering data in the browser, not by input validation before storing it in the database; input validation alone is insufficient and unreliable against XSS.
Raw{"answer": "no", "explanation": "XSS is primarily prevented by output encoding/escaping when rendering data in the browser, not by input validation before storing it in the database; input validation alone is insufficient and unreliable against XSS."} | верно | XSS лечится контекстным экранированием НА ВЫВОДЕ (Twig autoescape, CSP); валидация ввода не покрывает все контексты вывода. |
T20-L6 0.95 c | Security and OAuth | In the OAuth 2.0 authorization code flow, which parameter arrives at the redirect_uri and is exchanged for an access token? | «code» Пояснение: In the OAuth 2.0 authorization code flow, the 'code' parameter is returned to the redirect_uri and then exchanged for an access token at the token endpoint.
Raw{"answer": "code", "explanation": "In the OAuth 2.0 authorization code flow, the 'code' parameter is returned to the redirect_uri and then exchanged for an access token at the token endpoint."} | верно | Параметр code; обмен на токен POST-ом на /token с client_secret. |
T20-L7 0.94 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» Пояснение: In OAuth2, a refresh token has a longer lifetime than an access token and is used to request a new access token without requiring the user to log in again.
Raw{"answer": "yes", "explanation": "In OAuth2, a refresh token has a longer lifetime than an access token and is used to request a new access token without requiring the user to log in again."} | верно | Стандартная схема OAuth/OIDC: короткий access + длинный refresh. |
T20-L8 1.38 c | Security and OAuth | A password salt must be kept secret: without it the hash cannot be verified. | «no» Пояснение: A salt does not need to be secret; it is typically stored alongside the hash to prevent rainbow-table attacks, and security relies on the hash function's one-way property, not the salt's confidentiality.
Raw{"answer": "no", "explanation": "A salt does not need to be secret; it is typically stored alongside the hash to prevent rainbow-table attacks, and security relies on the hash function's one-way property, not the salt's confidentiality."} | верно | Соль хранится открыто (password_hash включает её в строку хеша); секретность соли не нужна. |
T18-L1 1.07 c | Testing: PHPUnit | PHPUnit runs test methods of any class — extending TestCase is not required. | «no» Пояснение: PHPUnit requires test classes to extend PHPUnit\Framework\TestCase in order to be discovered and executed by the test runner.
Raw{"answer": "no", "explanation": "PHPUnit requires test classes to extend PHPUnit\\Framework\\TestCase in order to be discovered and executed by the test runner."} | верно | Тестом считается метод класса, наследующего TestCase (PHPUnit 10). |
T18-L2 0.79 c | Testing: PHPUnit | In PHPUnit, setUp() runs once before all tests of the class. | «no» Пояснение: setUp() runs before EACH test method; setUpBeforeClass() (static) is the one that runs once before all tests in the class.
Raw{"answer": "no", "explanation": "setUp() runs before EACH test method; setUpBeforeClass() (static) is the one that runs once before all tests in the class."} | верно | setUp() — перед КАЖДЫМ тестом; один раз на класс — setUpBeforeClass(). Проверено живым счётчиком на PHPUnit 10.5. |
T18-L3 1.42 c | Testing: PHPUnit | A data provider lets a test run with exactly one set of arguments. | «no» Пояснение: A data provider is designed to let a test run with multiple sets of arguments, not exactly one.
Raw{"answer": "no", "explanation": "A data provider is designed to let a test run with multiple sets of arguments, not exactly one."} | верно | Наоборот: наборов может быть сколько угодно — тест выполняется по разу на каждый. Проверено на PHPUnit 10.5 (#[DataProvider]). |
T18-L4 0.78 c | Testing: PHPUnit | Which PHPUnit method declares an expectation that an exception of a given class is thrown? | «expectexception» Пояснение: PHPUnit's expectException() method declares that a specific exception class is expected to be thrown during test execution.
Raw{"answer": "expectException", "explanation": "PHPUnit's expectException() method declares that a specific exception class is expected to be thrown during test execution."} | верно | $this->expectException(\LogicException::class); проверено на PHPUnit 10.5. |
T18-L5 1.4 c | Testing: PHPUnit | In PHPUnit, a stub verifies which methods were called on it, while a mock only returns data. | «no» Пояснение: The statement is reversed: a stub only returns pre-programmed data, while a mock both returns data and verifies that methods were called as expected.
Raw{"answer": "no", "explanation": "The statement is reversed: a stub only returns pre-programmed data, while a mock both returns data and verifies that methods were called as expected."} | верно | Наоборот: стаб подставляет данные, мок проверяет взаимодействия (createStub/createMock); docs PHPUnit — Test Doubles. |
T18-L6 0.9 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 docblock annotation.
Raw{"answer": "yes", "explanation": "In PHPUnit 10+, the #[DataProvider] attribute is the recommended replacement for the deprecated @dataProvider docblock annotation."} | верно | Аннотация ещё парсится в PHPUnit 10/11 (AnnotationParser в 10.5.66), удаление — в 12; атрибут — стандарт. |
T18-L7 0.84 c | Testing: PHPUnit | PHPUnit does not allow one test to depend on the result of another. | «no» Пояснение: PHPUnit supports test dependencies via the @depends annotation or #[DependsOn] attribute, allowing one test to receive the return value of another.
Raw{"answer": "no", "explanation": "PHPUnit supports test dependencies via the @depends annotation or #[DependsOn] attribute, allowing one test to receive the return value of another."} | верно | Зависимости есть: #[Depends] — зависимый тест не запустится, еслиProducer упал. |
T18-L8 0.7 c | Testing: PHPUnit | Which PHPUnit command-line option makes tests run in random order? | «--random» Пояснение: The --random option in PHPUnit shuffles the order in which tests are executed.
Raw{"answer": "--random", "explanation": "The --random option in PHPUnit shuffles the order in which tests are executed."} | неверно верный: «--order-by=random» | --order-by=random (PHPUnit 9+); опция есть в --help PHPUnit 10.5 (проектная). |
T01-L9 4.58 c | Syntax and operators | What does this code output?
```php
echo intdiv(7, 2) . intdiv(-7, 2);
``` | «3-3» Пояснение: intdiv(7,2)=3 and intdiv(-7,2)=-3 (truncation toward zero), concatenated with '.' gives the string "3-3".
Raw{"answer": "3-3", "explanation": "intdiv(7,2)=3 and intdiv(-7,2)=-3 (truncation toward zero), concatenated with '.' gives the string \"3-3\"."} | верно | intdiv truncates toward zero: intdiv(-7, 2) = -3, not -4. |
T01-L10 0.92 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 parsed as -(3 ** 2) = -9.
Raw{"answer": -9, "explanation": "In PHP, the ** (exponentiation) operator has higher precedence than the unary minus, so -3 ** 2 is parsed as -(3 ** 2) = -9."} | верно | ** is right-associative and binds tighter than unary minus: -(3²). |
T02-L9 2.46 c | Types and comparisons | What does this code output?
```php
echo '1e1' == '10' ? 'true' : 'false';
``` | «true» Пояснение: Both '1e1' and '10' are numeric strings, so PHP compares them numerically; 1e1 (scientific notation for 10) equals 10, making the expression true.
Raw{"answer": "true", "explanation": "Both '1e1' and '10' are numeric strings, so PHP compares them numerically; 1e1 (scientific notation for 10) equals 10, making the expression true."} | верно | Both strings are numeric — compared as numbers: 10 == 10. |
T02-L10 0.93 c | Types and comparisons | What does this code output?
```php
switch ('a') {
case 0: echo 'zero'; break;
default: echo 'other';
}
``` | «zero» Пояснение: PHP switch uses loose comparison (==), and the non-numeric string 'a' is coerced to 0, so it matches case 0.
Raw{"answer": "zero", "explanation": "PHP switch uses loose comparison (==), and the non-numeric string 'a' is coerced to 0, so it matches case 0."} | неверно верный: «other» | PHP 8: 'a' == 0 → false (used to be true) — default fires. |
T03-L9 4.55 c | Strings | What does this code output?
```php
echo strtr('abc', ['a' => '1', 'ab' => '2']);
``` | «1bc» Пояснение: With an array parameter, strtr processes replacements sequentially in array order: first 'a'→'1' gives '1bc', then 'ab' is not found in '1bc', so the result is '1bc'.
Raw{"answer": "1bc", "explanation": "With an array parameter, strtr processes replacements sequentially in array order: first 'a'→'1' gives '1bc', then 'ab' is not found in '1bc', so the result is '1bc'."} | неверно верный: «2c» | strtr with an array prefers the longest matching key. |
T03-L10 1.92 c | Strings | What does this code output?
```php
echo '[' . substr('hello', -10) . ']';
``` | «[]» Пояснение: substr('hello', -10) returns an empty string because the negative offset (-10) exceeds the string length (5), so the result is '[' . '' . ']' which is '[]'.
Raw{"answer": "[]", "explanation": "substr('hello', -10) returns an empty string because the negative offset (-10) exceeds the string length (5), so the result is '[' . '' . ']' which is '[]'."} | неверно верный: «[hello]» | A negative start beyond the string is clamped to the beginning. |
T04-L9 1.55 c | Arrays | What does this code output?
```php
$a = ['k' => 1, 'n' => 2];
$b = ['k' => 9, 'm' => 3];
echo implode(',', array_keys($a + $b));
``` | «k,n,m» Пояснение: The array union operator + keeps left-hand keys and appends right-hand keys not present on the left, so the keys are k, n, m.
Raw{"answer": "k,n,m", "explanation": "The array union operator + keeps left-hand keys and appends right-hand keys not present on the left, so the keys are k, n, m."} | верно | The + operator: on duplicate string keys the left array wins. |
T04-L10 2.92 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» Пояснение: Sorting by the third element (1, 2, 2) reorders to [2,'y',1], [1,'x',2], [3,'z',2]; array_column with index 1 gives ['y','x','z']; implode produces 'yxz'.
Raw{"answer": "yxz", "explanation": "Sorting by the third element (1, 2, 2) reorders to [2,'y',1], [1,'x',2], [3,'z',2]; array_column with index 1 gives ['y','x','z']; implode produces 'yxz'."} | верно | Sorts are stable since 8.0: x and z keep their order on a tie. |
T05-L10 1.25 c | Functions and closures | What does this code output?
```php
function f(int $a, int $b): int
{
return $a - $b;
}
echo f(...['b' => 1, 'a' => 5]);
``` | «4» Пояснение: The spread operator with named keys maps 'a' => 5 and 'b' => 1, so f computes 5 - 1 = 4.
Raw{"answer": 4, "explanation": "The spread operator with named keys maps 'a' => 5 and 'b' => 1, so f computes 5 - 1 = 4."} | верно | String keys of a spread array become named arguments. |
T05-L9 9.02 c | Functions and closures | What does this code output?
```php
class P
{
private int $v = 3;
public function g(): int { return $this->v; }
}
$p = new P;
$f = $p->g(...);
$p = null;
echo $f();
``` | «3» Пояснение: The code as written is not valid PHP syntax ($p->g(...) is not a recognized expression), so it would produce a Parse/Fatal error rather than outputting a value; however, the intended question likely tests that the object's private property v equals 3, which is what g() would return.
Raw{"answer": 3, "explanation": "The code as written is not valid PHP syntax ($p->g(...) is not a recognized expression), so it would produce a Parse/Fatal error rather than outputting a value; however, the intended question likely tests that the object's private property v equals 3, which is what g() would return."} | верно | First-class callable syntax binds $this at creation time. |
T06-L9 0.93 c | OOP: classes and inheritance | What does this code output?
```php
class A
{
public function who(): string { return static::class; }
}
class B extends A {}
echo (new B)->who();
``` | «b» Пояснение: static::class uses late static binding, so it resolves to the class that was actually instantiated, which is B.
Raw{"answer": "B", "explanation": "static::class uses late static binding, so it resolves to the class that was actually instantiated, which is B."} | верно | Late static binding: static::class is the receiver's class. |
T06-L10 2.08 c | OOP: classes and inheritance | What does this code output on PHP 8.5?
```php
class C
{
public int $x = 0 {
set { $this->x = $value * 2; }
}
}
$c = new C;
$c->x = 5;
echo $c->x;
``` | «10» Пояснение: The setter multiplies the assigned value by 2, so assigning 5 stores 10, which is then echoed.
Raw{"answer": 10, "explanation": "The setter multiplies the assigned value by 2, so assigning 5 stores 10, which is then echoed."} | верно | Inside the set hook, $this->x writes the backing store (no recursion): 5*2. |
T07-L9 1.44 c | Interfaces, traits, enum | What does this code output?
```php
trait TA
{
public function f(): string { return 'A'; }
}
trait TB
{
public function f(): string { return 'B'; }
}
class TC
{
use TA, TB { TB::f insteadof TA; TA::f as g; }
}
echo (new TC)->f() . (new TC)->g();
``` | «ba» Пояснение: TB::f insteadof TA makes f() return 'B', and TA::f as g aliases TA's f to g() returning 'A', so the concatenation is 'BA'.
Raw{"answer": "BA", "explanation": "TB::f insteadof TA makes f() return 'B', and TA::f as g aliases TA's f to g() returning 'A', so the concatenation is 'BA'."} | верно | insteadof picks the implementation; as keeps the other under an alias. |
T07-L10 2.47 c | Interfaces, traits, enum | What does this code output?
```php
trait Counter
{
public static int $n = 0;
}
class CX { use Counter; }
class CY { use Counter; }
CX::$n = 1;
echo CY::$n;
``` | «0» Пояснение: Each class that uses a trait gets its own independent copy of static properties, so CX::$n = 1 does not affect CY::$n, which remains 0.
Raw{"answer": 0, "explanation": "Each class that uses a trait gets its own independent copy of static properties, so CX::$n = 1 does not affect CY::$n, which remains 0."} | верно | A trait's static property is copied into each consuming class. |
T08-L10 0.88 c | Exceptions and errors | What does this code output?
```php
function f(): int
{
try { return 1; } finally { return 2; }
}
echo f();
``` | «2» Пояснение: In PHP, a return statement in a finally block overrides the return value from the try block, so the function returns 2.
Raw{"answer": 2, "explanation": "In PHP, a return statement in a finally block overrides the return value from the try block, so the function returns 2."} | верно | A return in finally overrides the return from try. |
T08-L9 1.36 c | Exceptions and errors | What does this code output?
```php
try {
try {
throw new RuntimeException('first');
} finally {
throw new LogicException('second');
}
} catch (LogicException $e) {
echo $e->getMessage();
}
``` | «second» Пояснение: The finally block throws a LogicException which replaces the original RuntimeException, and the outer catch catches that LogicException and prints its message 'second'.
Raw{"answer": "second", "explanation": "The finally block throws a LogicException which replaces the original RuntimeException, and the outer catch catches that LogicException and prints its message 'second'."} | верно | An exception from finally replaces the in-flight one — the last thrown is caught. |
T09-L9 1.42 c | Namespaces and autoloading | What does this code output?
```php
namespace N;
use App\Foo as Baz;
echo Baz::class . '|' . \Baz::class;
``` | «app\foo|baz» Пояснение: Baz::class resolves to the aliased import App\Foo, while \Baz::class refers to the global class Baz.
Raw{"answer": "App\\Foo|Baz", "explanation": "Baz::class resolves to the aliased import App\\Foo, while \\Baz::class refers to the global class Baz."} | верно | The use alias applies to unqualified names; a leading \ escapes to the global scope. |
T09-L10 1.77 c | Namespaces and autoloading | What does this code output?
```php
namespace Ns;
class Foo {}
$c = 'Foo';
echo (class_exists($c) ? 'yes' : 'no')
. (class_exists(__NAMESPACE__ . '\\' . $c) ? 'yes' : 'no');
``` | «noyes» Пояснение: class_exists('Foo') looks in the global namespace where no Foo exists (it's in Ns), returning 'no'; class_exists('Ns\\Foo') finds the class defined in namespace Ns, returning 'yes'.
Raw{"answer": "noyes", "explanation": "class_exists('Foo') looks in the global namespace where no Foo exists (it's in Ns), returning 'no'; class_exists('Ns\\\\Foo') finds the class defined in namespace Ns, returning 'yes'."} | верно | Dynamic names are not resolved against the namespace — 'Foo' is the global class. |
T10-L9 1.3 c | References and scope | What does this code output?
```php
$a = [1, 2, 3];
foreach ($a as &$v) {}
$v = 99;
echo implode(',', $a);
``` | «1,2,99» Пояснение: After foreach by reference, $v still references the last element of $a, so assigning $v=99 changes $a[2] to 99.
Raw{"answer": "1,2,99", "explanation": "After foreach by reference, $v still references the last element of $a, so assigning $v=99 changes $a[2] to 99."} | верно | After a by-ref foreach, $v remains a reference to the last element. |
T10-L10 2.12 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 across all instances; each call to inc() (whether on A or B) increments it, so after three calls it equals 3.
Raw{"answer": 3, "explanation": "The static variable $n is shared across all instances; each call to inc() (whether on A or B) increments it, so after three calls it equals 3."} | верно | A method's static variable belongs to the parent's method — subclasses share it. |
T11-L9 2.17 c | Generators, iterators, SPL | What does this code output?
```php
function g(): Generator
{
$x = yield 1;
return $x + 1;
}
$g = g();
$g->send(10);
echo $g->getReturn();
``` | «11» Пояснение: send(10) assigns $x=10, then the generator returns $x+1=11, which getReturn() retrieves.
Raw{"answer": 11, "explanation": "send(10) assigns $x=10, then the generator returns $x+1=11, which getReturn() retrieves."} | верно | send() resumes the generator: $x = 10, return 10+1. |
T11-L10 1.73 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 delegates to inner() yielding 1 and 2, then the return value 'ok' is captured in $r and yielded by outer(), so iterator_to_array collects [1, 2, 'ok'] which implode joins as '1,2,ok'.
Raw{"answer": "1,2,ok", "explanation": "yield from delegates to inner() yielding 1 and 2, then the return value 'ok' is captured in $r and yielded by outer(), so iterator_to_array collects [1, 2, 'ok'] which implode joins as '1,2,ok'."} | неверно верный: «ok,2» | yield from does not advance the outer auto-key: yield $r gets key 0 and overwrites the 1 — 'ok' comes out first. |
T12-L9 1.33 c | Configuration and security | What does this code output?
```php
$hash = password_hash('x', PASSWORD_BCRYPT, ['cost' => 4]);
echo password_needs_rehash($hash, PASSWORD_BCRYPT, ['cost' => 4]) ? 'yes' : 'no';
echo password_needs_rehash($hash, PASSWORD_BCRYPT, ['cost' => 5]) ? 'yes' : 'no';
``` | «noyes» Пояснение: The first call checks against the same cost (4) so no rehash is needed ('no'), the second checks against a higher cost (5) so a rehash is needed ('yes').
Raw{"answer": "noyes", "explanation": "The first call checks against the same cost (4) so no rehash is needed ('no'), the second checks against a higher cost (5) so a rehash is needed ('yes')."} | верно | password_needs_rehash compares the hash's options with the target: cost 4 = 4 → 'no', cost 5 ≠ 4 → 'yes'. |
T12-L10 6.17 c | Configuration and security | What does this code output on PHP 8.5?
```php
echo (E_ALL & 2048) === 0 ? 'strict-out' : 'strict-in';
``` | «strict-in» Пояснение: E_STRICT (2048) is deprecated in PHP 8.4 but still included in E_ALL in PHP 8.5, so E_ALL & 2048 equals 2048 (not 0), making the ternary evaluate to 'strict-in'.
Raw{"answer": "strict-in", "explanation": "E_STRICT (2048) is deprecated in PHP 8.4 but still included in E_ALL in PHP 8.5, so E_ALL & 2048 equals 2048 (not 0), making the ternary evaluate to 'strict-in'."} | неверно верный: «strict-out» | Since PHP 8.4, E_STRICT is out of E_ALL: the 2048 bit is unset → 'strict-out' (2048 is the historical E_STRICT bit). |
T13-L9 1.56 c | Symfony | What does this code output?
```php
use Symfony\Component\HttpFoundation\Request;
$r = Request::create('/demo', 'GET', [], [], [], ['HTTP_X_TOKEN' => 'abc']);
echo $r->headers->get('X-Token') === 'abc' ? 'mapped' : 'missing';
``` | «mapped» Пояснение: Symfony's Request normalizes the server variable HTTP_X_TOKEN into the header X-Token, so the header lookup returns 'abc' and the strict comparison succeeds.
Raw{"answer": "mapped", "explanation": "Symfony's Request normalizes the server variable HTTP_X_TOKEN into the header X-Token, so the header lookup returns 'abc' and the strict comparison succeeds."} | верно | The literal comparison requires knowing the mapping: HttpFoundation turns HTTP_X_TOKEN into the X-Token header (case-insensitive); without it the answer is 'missing'. |
T13-L10 1.22 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» Пояснение: In Symfony's EventDispatcher, higher priority values are called first: B (priority 10), C (priority 5), A (priority 0).
Raw{"answer": "BCA", "explanation": "In Symfony's EventDispatcher, higher priority values are called first: B (priority 10), C (priority 5), A (priority 0)."} | верно | Listeners run by descending priority: 10 (B), 5 (C), 0 (A). |
T14-L10 2.37 c | Doctrine | Given: Doctrine ORM 3, an EntityManager on in-memory SQLite, entity User with an auto-increment primary key. The users table is empty. What does this code output?
```php
$u = new User(name: 'A');
$em->persist($u);
$em->flush();
$a = $em->find(User::class, $u->getId());
$b = $em->find(User::class, $u->getId());
echo spl_object_id($a) === spl_object_id($b) ? 'same' : 'diff';
``` | «same» Пояснение: Doctrine's identity map guarantees a single instance per entity ID, so both find() calls return the same object already tracked by the EntityManager.
Raw{"answer": "same", "explanation": "Doctrine's identity map guarantees a single instance per entity ID, so both find() calls return the same object already tracked by the EntityManager."} | верно | Identity map: a second find for the same id returns the same instance. |
T14-L9 2.58 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» Пояснение: Persisting then removing a new entity before flush simply untracks it from the Unit of Work; no INSERT is ever issued, so the table remains empty.
Raw{"answer": 0, "explanation": "Persisting then removing a new entity before flush simply untracks it from the Unit of Work; no INSERT is ever issued, so the table remains empty."} | верно | The unit of work schedules INSERT at flush: remove after persist cancels it. |
T15-L10 1.33 c | PostgreSQL | What does this SQL query return (PostgreSQL 17)?
```sql
CREATE TEMP TABLE t (x int);
INSERT INTO t VALUES (1), (NULL);
SELECT count(x) FROM t;
``` | «1» Пояснение: COUNT(x) counts only non-NULL values in column x, so it returns 1 (the NULL row is excluded).
Raw{"answer": 1, "explanation": "COUNT(x) counts only non-NULL values in column x, so it returns 1 (the NULL row is excluded)."} | верно | count(column) skips NULLs; count(*) would return 2. |
T15-L9 1.59 c | PostgreSQL | What does this SQL query return (PostgreSQL 17)?
```sql
CREATE TEMP TABLE t (id int, x int);
INSERT INTO t VALUES (1, 10), (2, 20), (3, 30);
SELECT string_agg(s::text, ',' ORDER BY id) FROM (
SELECT id, sum(x) OVER (ORDER BY id) AS s FROM t
) q;
``` | «10,30,60» Пояснение: The window function computes running sums (10, 30, 60), and string_agg concatenates them as text with commas.
Raw{"answer": "10,30,60", "explanation": "The window function computes running sums (10, 30, 60), and string_agg concatenates them as text with commas."} | верно | With ORDER BY the default window frame is running (start to current row). |
T16-L9 5.66 c | Symfony: Messenger | What does this code output?
```php
use Symfony\Component\Messenger\MessageBus;
use Symfony\Component\Messenger\Middleware\MiddlewareInterface;
use Symfony\Component\Messenger\Middleware\StackInterface;
use Symfony\Component\Messenger\Envelope;
final class Trace implements MiddlewareInterface
{
public function __construct(private string $tag) {}
public function handle(Envelope $e, StackInterface $stack): Envelope
{
echo $this->tag;
return $stack->next()->handle($e, $stack);
}
}
$bus = new MessageBus([new Trace('M1'), new Trace('M2')]);
$bus->dispatch(new Envelope(new stdClass()));
``` | «m1m2» Пояснение: The middleware stack executes in order: Trace('M1') echoes 'M1' then calls next, Trace('M2') echoes 'M2' then calls next, so the output is 'M1M2' (before a HandlerNotFound exception would be thrown since no handler is registered).
Raw{"answer": "M1M2", "explanation": "The middleware stack executes in order: Trace('M1') echoes 'M1' then calls next, Trace('M2') echoes 'M2' then calls next, so the output is 'M1M2' (before a HandlerNotFound exception would be thrown since no handler is registered)."} | верно | The first-added middleware runs first (outermost). |
T16-L10 3.52 c | Symfony: Messenger | What does this code output?
```php
use Symfony\Component\Messenger\MessageBus;
use Symfony\Component\Messenger\Middleware\HandleMessageMiddleware;
use Symfony\Component\Messenger\Handler\HandlersLocator;
use Symfony\Component\Messenger\Handler\HandlerDescriptor;
use Symfony\Component\Messenger\Envelope;
class Ping {}
$n = 0;
$d1 = new HandlerDescriptor(function (Ping $m) use (&$n) { $n += 1; }, ['alias' => 'h1']);
$d2 = new HandlerDescriptor(function (Ping $m) use (&$n) { $n += 10; }, ['alias' => 'h2']);
$bus = new MessageBus([
new HandleMessageMiddleware(new HandlersLocator([Ping::class => [$d1, $d2]])),
]);
$bus->dispatch(new Envelope(new Ping()));
echo $n;
``` | «11» Пояснение: Both handlers in the HandlersLocator are invoked sequentially for the same Ping message: the first adds 1 to $n (making it 1) and the second adds 10 (making it 11).
Raw{"answer": 11, "explanation": "Both handlers in the HandlersLocator are invoked sequentially for the same Ping message: the first adds 1 to $n (making it 1) and the second adds 10 (making it 11)."} | верно | All registered handlers of the message run: 1 + 10 = 11. |
T17-L9 1.68 c | PostgreSQL: transactions and indexes | What does this SQL query return (PostgreSQL 17)?
```sql
CREATE TEMP TABLE t (a int);
CREATE UNIQUE INDEX ON t (a);
INSERT INTO t VALUES (1) ON CONFLICT DO NOTHING;
INSERT INTO t VALUES (1) ON CONFLICT DO NOTHING;
SELECT count(*) FROM t;
``` | «1» Пояснение: The first INSERT adds value 1; the second INSERT is silently skipped due to the unique index conflict (ON CONFLICT DO NOTHING), so the table contains only one row.
Raw{"answer": 1, "explanation": "The first INSERT adds value 1; the second INSERT is silently skipped due to the unique index conflict (ON CONFLICT DO NOTHING), so the table contains only one row."} | верно | ON CONFLICT DO NOTHING skips the duplicate: one insert. |
T17-L10 2.35 c | PostgreSQL: transactions and indexes | What does this sequence of psql commands output?
```sql
BEGIN;
CREATE TEMP TABLE t (a int, UNIQUE (a) DEFERRABLE INITIALLY DEFERRED);
INSERT INTO t VALUES (1);
INSERT INTO t VALUES (1);
SELECT count(*) FROM t;
``` | «2» Пояснение: The UNIQUE constraint is DEFERRABLE INITIALLY DEFERRED, so violations are only checked at COMMIT time; both INSERTs succeed within the transaction, and SELECT count(*) returns 2.
Raw{"answer": 2, "explanation": "The UNIQUE constraint is DEFERRABLE INITIALLY DEFERRED, so violations are only checked at COMMIT time; both INSERTs succeed within the transaction, and SELECT count(*) returns 2."} | верно | DEFERRED postpones the uniqueness check to COMMIT — count sees 2 rows. |
T18-L9 1.41 c | Testing: PHPUnit | How many tests will this command run?
```php
use PHPUnit\Framework\TestCase;
use PHPUnit\Framework\Attributes\DataProvider;
final class CalcTest extends TestCase
{
public static function prov(): array
{
return [[1], [2], [3]];
}
#[DataProvider('prov')]
public function test_sum(int $x): void
{
$this->assertTrue($x > 0);
}
#[DataProvider('prov')]
public function test_sum_abs(int $x): void
{
$this->assertTrue($x > 0);
}
public function test_other(): void
{
$this->assertTrue(true);
}
}
```
Command: `phpunit CalcTest.php --filter test_sum` (PHPUnit 10.5) | «6» Пояснение: The filter 'test_sum' matches both test_sum (3 data sets) and test_sum_abs (3 data sets), giving 6 total tests.
Raw{"answer": 6, "explanation": "The filter 'test_sum' matches both test_sum (3 data sets) and test_sum_abs (3 data sets), giving 6 total tests."} | верно | --filter is a substring match: test_sum also matches test_sum_abs (3+3 datasets). |
T18-L10 1.58 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 returns two datasets ([1] and [-1]), producing 2 test runs; the assertion $x > 0 fails only for -1, so 1 test fails.
Raw{"answer": "2, 1", "explanation": "The data provider returns two datasets ([1] and [-1]), producing 2 test runs; the assertion $x > 0 fails only for -1, so 1 test 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 0.84 c | HTTP and REST API | Which HTTP method does this command send?
```bash
curl -s -d 'a=1' http://demo.local/api
``` | «post» Пояснение: The -d flag in curl sends data in the request body, which automatically changes the HTTP method from the default GET to POST.
Raw{"answer": "POST", "explanation": "The -d flag in curl sends data in the request body, which automatically changes the HTTP method from the default GET to POST."} | верно | -d/-F switches curl to POST by default. |
T19-L10 1.33 c | HTTP and REST API | Which HTTP method does this command send?
```bash
curl -s -G -d 'a=1' http://demo.local/api
``` | «get» Пояснение: The -G flag overrides the default POST behavior of -d, causing the data to be appended as a query string and the request to be sent as a GET.
Raw{"answer": "GET", "explanation": "The -G flag overrides the default POST behavior of -d, causing the data to be appended as a query string and the request to be sent as a GET."} | верно | -G turns -d data into the query string; the method stays GET. |
T20-L9 1.79 c | Security and OAuth | A client hits the token endpoint (RFC 6749) with a non-existent client_id. What value of the error field does the endpoint return? | «invalid_client» Пояснение: RFC 6749 §5.2 specifies that when the client identifier is not recognized (non-existent client_id), the token endpoint returns the error 'invalid_client'.
Raw{"answer": "invalid_client", "explanation": "RFC 6749 §5.2 specifies that when the client identifier is not recognized (non-existent client_id), the token endpoint returns the error 'invalid_client'."} | верно | Unknown client → invalid_client (RFC 6749 §5.2). |
T20-L10 1.22 c | Security and OAuth | OAuth 2.0: the client started the flow with response_type=token. In which part of the redirect_uri does the authorization server pass the access_token? | «fragment» Пояснение: In the OAuth 2.0 implicit flow (response_type=token), the authorization server returns the access_token in the URI fragment (after the # symbol) of the redirect_uri.
Raw{"answer": "fragment", "explanation": "In the OAuth 2.0 implicit flow (response_type=token), the authorization server returns the access_token in the URI fragment (after the # symbol) of the redirect_uri."} | верно | The implicit flow passes the token in the URL fragment (#) — it never reaches the server. |
T21-L9 1.33 c | Twig | What does this Twig template output?
```twig
{{ false|default(2) * 3 }}
``` | «0» Пояснение: The default filter only replaces null/undefined values, not falsy ones like false, so false is kept and false * 3 evaluates to 0 in PHP.
Raw{"answer": 0, "explanation": "The default filter only replaces null/undefined values, not falsy ones like false, so false is kept and false * 3 evaluates to 0 in PHP."} | неверно верный: «6» | default replaces exactly false/null/''/[] — false becomes 2, 2*3 = 6; the naive 'default is for undefined only' yields 0. |
T21-L10 5.44 c | Twig | What exception class does render() of this template throw?
```twig
{{ 'a' ~ 1 + 2 }}
``` | «a3» Пояснение: In Twig, the + operator has higher precedence than ~, so the expression is parsed as 'a' ~ (1 + 2) = 'a' ~ 3 = 'a3', which renders successfully without throwing any exception.
Raw{"answer": "a3", "explanation": "In Twig, the + operator has higher precedence than ~, so the expression is parsed as 'a' ~ (1 + 2) = 'a' ~ 3 = 'a3', which renders successfully without throwing any exception."} | неверно верный: «runtimeerror» | In Twig ~ binds tighter than +: ('a' ~ 1) + 2 → string + int → a render error (RuntimeError). |
T22-L9 2.39 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 array [''] has one element (empty string), and NotBlank on an empty string produces one violation, so count() returns 1.
Raw{"answer": 1, "explanation": "The array [''] has one element (empty string), and NotBlank on an empty string produces one violation, so count() returns 1."} | неверно верный: «0» | NotBlank treats null, '', [] as blank — the array [''] is not blank. |
T22-L10 3.23 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» Пояснение: Calling isValid() on a non-submitted Symfony form throws a LogicException, which is caught and its class name is printed.
Raw{"answer": "Symfony\\Component\\Form\\Exception\\LogicException", "explanation": "Calling isValid() on a non-submitted Symfony form throws a LogicException, which is caught and its class name is printed."} | верно | isValid() on a non-submitted form throws LogicException, it does not return false. |
T23-L9 1.45 c | Symfony: configuration and services | What does this code output?
```php
use Symfony\Component\DependencyInjection\ContainerBuilder;
$c = new ContainerBuilder();
$c->register('a', stdClass::class)->setPublic(true);
$c->compile();
echo spl_object_id($c->get('a')) === spl_object_id($c->get('a')) ? 'same' : 'diff';
``` | «same» Пояснение: Symfony's DI container services are singletons (shared) by default, so get() returns the same object instance each time, making both spl_object_id() values equal.
Raw{"answer": "same", "explanation": "Symfony's DI container services are singletons (shared) by default, so get() returns the same object instance each time, making both spl_object_id() values equal."} | верно | Container services are shared: two get() calls yield one instance. |
T23-L10 1.02 c | Symfony: configuration and services | What does this code output?
```php
use Symfony\Component\DependencyInjection\ContainerBuilder;
$c = new ContainerBuilder();
$c->setParameter('name', 'Bob');
$c->setParameter('greeting', 'hi %name%');
$c->setParameter('message', '%greeting%!');
$c->compile();
echo $c->getParameter('message');
``` | «hi bob!» Пояснение: Symfony's ContainerBuilder resolves nested parameter references during compile(), so '%greeting%!' becomes 'hi Bob!'.
Raw{"answer": "hi Bob!", "explanation": "Symfony's ContainerBuilder resolves nested parameter references during compile(), so '%greeting%!' becomes 'hi Bob!'."} | верно | compile() resolves %-references transitively: %greeting% → 'hi %name%' → 'hi Bob!', the answer assembles over two hops. |
T24-L9 1.52 c | Bootstrap | What is the max-width of .container in Bootstrap 5.3 at a 992px viewport? | «960px» Пояснение: In Bootstrap 5.3, the .container max-width at the ≥992px (xl) breakpoint is 960px.
Raw{"answer": "960px", "explanation": "In Bootstrap 5.3, the .container max-width at the ≥992px (xl) breakpoint is 960px."} | верно | 5.x container widths: 540/720/960/1140/1320 (sm–xxl); 992 → 960px. |
T24-L10 3.51 c | Bootstrap | Which utility sets the text color in Bootstrap 5.3 for `<p class="text-danger text-primary">…</p>`? Answer with the winning class name. | «text-danger» Пояснение: In Bootstrap 5.3's generated CSS, text-danger appears after text-primary in source order, so with equal specificity, the later rule wins.
Raw{"answer": "text-danger", "explanation": "In Bootstrap 5.3's generated CSS, text-danger appears after text-primary in source order, so with equal specificity, the later rule wins."} | верно | Specificity ties — the later rule wins: text-danger is declared after text-primary. |
T25-L9 1.24 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» Пояснение: Domain can only depend on Domain, but this class depends on both Application and Infrastructure, resulting in 2 violations.
Raw{"answer": 2, "explanation": "Domain can only depend on Domain, but this class depends on both Application and Infrastructure, resulting in 2 violations."} | верно | Domain may depend only on Domain: PlaceOrder (Application) + Db (Infrastructure) = 2. |
T25-L10 1.17 c | Clean architecture | Layers: Domain, Application, Infrastructure. Deptrac rules: Application → Domain; Infrastructure → Domain, Application; Domain → Domain only.
How many violations will deptrac report for this class?
```php
namespace App\Domain;
use App\Application\PlaceOrder;
use App\Infrastructure\Db;
class BillingService
{
public function __construct(
private PlaceOrder $handler,
private Db $db,
private \App\Infrastructure\Logger $logger,
) {}
}
``` | «3» Пояснение: The Domain class depends on Application (PlaceOrder) and Infrastructure (Db, Logger), which violates the rule that Domain can only depend on Domain.
Raw{"answer": 3, "explanation": "The Domain class depends on Application (PlaceOrder) and Infrastructure (Db, Logger), which violates the rule that Domain can only depend on Domain."} | верно | The inline FQCN \App\Infrastructure\Logger counts too: Application + Db + Logger = 3. |
T26-L10 1.4 c | DDD | What does this code output?
```php
final class Money
{
public function __construct(public readonly int $amount) {}
public function add(Money $o): Money
{
return new self($this->amount + $o->amount);
}
}
$a = new Money(10);
$c = $a->add(new Money(5));
echo $a->amount . ',' . $c->amount;
``` | «10,15» Пояснение: $a holds amount 10, and $c is a new Money object with 10+5=15, so concatenating them with a comma gives '10,15'.
Raw{"answer": "10,15", "explanation": "$a holds amount 10, and $c is a new Money object with 10+5=15, so concatenating them with a comma gives '10,15'."} | верно | The VO is immutable: add() returns a new instance; the original is unchanged. |
T26-L9 1.44 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() method throws a DomainException when count is 1 before unsetting, so the item 'a' is never removed and count() still returns 1.
Raw{"answer": 1, "explanation": "The remove() method throws a DomainException when count is 1 before unsetting, so the item 'a' is never removed and count() still returns 1."} | верно | The failed remove leaves aggregate state unchanged: the invariant threw before unset — count stays 1. |
VC-L9 0.64 c | PHP 8.4–8.5 | What does this code output on PHP 8.5?
```php
class C
{
public function hi(): string { return 'hi'; }
}
echo new C()->hi();
``` | «hi» Пояснение: The code creates an instance of class C and calls its hi() method, which returns the string 'hi', which is then echoed.
Raw{"answer": "hi", "explanation": "The code creates an instance of class C and calls its hi() method, which returns the string 'hi', which is then echoed."} | верно | Since 8.4, new in a method chain works without wrapping parentheses. |
VC-L10 3.03 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» Пояснение: Before property access the lazy ghost is uninitialized (outputs 'yes'), and after accessing $o->v the initialization callback runs, so it's no longer uninitialized (outputs 'no').
Raw{"answer": "yesno", "explanation": "Before property access the lazy ghost is uninitialized (outputs 'yes'), and after accessing $o->v the initialization callback runs, so it's no longer uninitialized (outputs 'no')."} | верно | newLazyGhost (8.4): the object stays lazy until first access — reading a property initializes it and clears the flag. |
T28-L9 1.11 c | Symfony: versions | The project was upgraded from Symfony 6.4 to 8.1. What does this code output on 8.1?
```php
echo class_exists(\Symfony\Component\Security\Guard\AbstractGuardAuthenticator::class)
? 'yes' : 'no';
``` | «no» Пояснение: The Guard authentication component (including AbstractGuardAuthenticator) was removed in Symfony 6.0, so it does not exist in Symfony 8.1.
Raw{"answer": "no", "explanation": "The Guard authentication component (including AbstractGuardAuthenticator) was removed in Symfony 6.0, so it does not exist in Symfony 8.1."} | верно | Guard authentication was removed in Symfony 7.0 — the class is gone in 8.1. |
T28-L10 2.71 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 7.0+ (and thus 8.1), AnnotationClassLoader was removed (output 'no'), while AttributeClassLoader exists as its replacement (output 'yes').
Raw{"answer": "noyes", "explanation": "In Symfony 7.0+ (and thus 8.1), AnnotationClassLoader was removed (output 'no'), while AttributeClassLoader exists as its replacement (output 'yes')."} | верно | Annotation loaders were removed in 7.0; only attribute loaders remain (Annotation→Attribute). |