Пример запроса (первая клетка). System одинаковый во всех запросах прогона, user — свой вопрос для каждой клетки:
| Клетка | Тема | Утверждение | Ответ |
Результат | Обоснование |
T01-L1 4.17 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 additional escape sequences (e.g. \n, \t), while single-quoted strings only interpret \\ and \' — the difference is functional, not just speed.
Raw{"answer":"no","explanation":"Double-quoted strings support variable interpolation and additional escape sequences (e.g. \\n, \\t), while single-quoted strings only interpret \\\\ and \\' — the difference is functional, not just speed."} | верно | В двойных кавычках работают интерполяция переменных и escape-последовательности, в одинарных — нет. |
T01-L2 1.17 c | Syntax and operators | The ?? operator follows isset semantics and raises no warnings for undefined variables. | «yes» Пояснение: The ?? operator is defined as a shorthand for isset($var) ? $var : default, so it does not raise warnings for undefined variables.
Raw{"answer": "yes", "explanation": "The ?? operator is defined as a shorthand for isset($var) ? $var : default, so it does not raise warnings for undefined variables."} | верно | ?? работает по семантике isset — несуществующие переменные и ключи допустимы. |
T01-L3 0.64 c | Syntax and operators | What will this print: echo 'a', 'b'; | «ab» Пояснение: PHP's echo statement accepts multiple comma-separated arguments and prints them concatenated together.
Raw{"answer": "ab", "explanation": "PHP's echo statement accepts multiple comma-separated arguments and prints them concatenated together."} | верно | echo принимает список аргументов: ab. |
T01-L4 1.11 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 always returns the integer 1, allowing it to be used within expressions (unlike echo, which returns nothing).
Raw{"answer": "yes", "explanation": "In PHP, print is a language construct that always returns the integer 1, allowing it to be used within expressions (unlike echo, which returns nothing)."} | верно | print — выражение со значением 1, в отличие от echo, который значения не возвращает. |
T01-L5 1.04 c | Syntax and operators | The ?: (elvis) operator returns its left operand when it is falsy. | «no» Пояснение: The Elvis operator (?:) returns its left operand when it is truthy, not falsy; when falsy it returns the right operand.
Raw{"answer": "no", "explanation": "The Elvis operator (?:) returns its left operand when it is truthy, not falsy; when falsy it returns the right operand."} | верно | Наоборот: $a ?: $b возвращает $a, если он истинный, иначе $b. |
T01-L6 1.91 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 + and -, so expressions like 'a' . 1 + 2 are parsed as 'a' . (1 + 2).
Raw{"answer": "yes", "explanation": "In PHP, the concatenation operator (.) has lower precedence than + and -, so expressions like 'a' . 1 + 2 are parsed as 'a' . (1 + 2)."} | верно | С PHP 8 (RFC concat precedence) '.' имеет приоритет ниже арифметики: 'сумма: ' . 2 + 3 → 'сумма: 5' (в PHP 7 было иначе). |
T01-L7 0.91 c | Syntax and operators | The expression 2 ** 3 ** 2 in PHP evaluates as (2 ** 3) ** 2, that is, 64. | «no» Пояснение: In PHP, the ** operator is right-associative, so 2 ** 3 ** 2 evaluates as 2 ** (3 ** 2) = 2 ** 9 = 512, not 64.
Raw{"answer":"no","explanation":"In PHP, the ** operator is right-associative, so 2 ** 3 ** 2 evaluates as 2 ** (3 ** 2) = 2 ** 9 = 512, not 64."} | верно | ** право-ассоциативен: 2 ** (3 ** 2) = 2 ** 9 = 512. |
T01-L8 2.22 c | Syntax and operators | What string will this print: echo 'sum: ' . 2 + 3; (PHP 8)? | «3» Пояснение: Concatenation (.) has higher precedence than addition (+), so it parses as ('sum: '.2)+3, which becomes 'sum: 2'+3; the non-numeric string casts to 0, giving 0+3=3.
Raw{"answer": 3, "explanation": "Concatenation (.) has higher precedence than addition (+), so it parses as ('sum: '.2)+3, which becomes 'sum: 2'+3; the non-numeric string casts to 0, giving 0+3=3."} | неверно верный: «sum: 5» | Парная к verify-клетке про приоритет: 'сумма: 5'. |
T02-L1 1.02 c | Types and comparisons | With strict comparison (===), arrays are considered equal regardless of element order. | «no» Пояснение: With ===, arrays must have the same key-value pairs in the same order and matching types.
Raw{"answer": "no", "explanation": "With ===, arrays must have the same key-value pairs in the same order and matching types."} | верно | === для массивов требует совпадения и значений, и их порядка. |
T02-L2 1.26 c | Types and comparisons | The comparison 0 == false returns false because it is a strict comparison. | «no» Пояснение: 0 == false returns true (not false), and == is a loose comparison, not a strict one.
Raw{"answer": "no", "explanation": "0 == false returns true (not false), and == is a loose comparison, not a strict one."} | верно | Наоборот: == — нестрогое сравнение и возвращает true; строгое — это === (0 === false → false). |
T02-L3 1.73 c | Types and comparisons | In PHP 8, the expression "abc" == 0 returns true. | «no» Пояснение: In PHP 8, when comparing a non-numeric string with an integer, the integer is cast to a string, so 'abc' == 0 becomes 'abc' == '0', which is false.
Raw{"answer": "no", "explanation": "In PHP 8, when comparing a non-numeric string with an integer, the integer is cast to a string, so 'abc' == 0 becomes 'abc' == '0', which is false."} | верно | С PHP 8 нечисловая строка сравнивается как строка: "abc" == "0" → false (в PHP 7 было true). |
T02-L4 0.89 c | Types and comparisons | Under loose comparison, null equals 0, the empty string, and false at the same time. | «yes» Пояснение: In PHP, using the loose comparison operator (==), null == 0, null == '', and null == false all evaluate to true.
Raw{"answer": "yes", "explanation": "In PHP, using the loose comparison operator (==), null == 0, null == '', and null == false all evaluate to true."} | верно | null == 0, null == "" и null == false — все true. |
T02-L5 1.16 c | Types and comparisons | What does the expression (int) '42abc' return? | «42» Пояснение: PHP casts a string to int by reading numeric characters from the start and stopping at the first non-numeric character, so '42abc' becomes 42.
Raw{"answer": 42, "explanation": "PHP casts a string to int by reading numeric characters from the start and stopping at the first non-numeric character, so '42abc' becomes 42."} | верно | Ведущая числовая часть: 42, без ошибок и warning. |
T02-L6 0.86 c | Types and comparisons | What does the expression '5' + 5 return? | «10» Пояснение: In PHP, the numeric string '5' is coerced to the integer 5, so 5 + 5 equals 10.
Raw{"answer": 10, "explanation": "In PHP, the numeric string '5' is coerced to the integer 5, so 5 + 5 equals 10."} | верно | Числовая строка приводится: int 10. |
T02-L7 1.35 c | Types and comparisons | When cast to string, false becomes "0". | «no» Пояснение: When false is cast to a string in PHP, it becomes an empty string "", not "0".
Raw{"answer": "no", "explanation": "When false is cast to a string in PHP, it becomes an empty string \"\", not \"0\"."} | верно | false → "", true → "1". |
T02-L8 1.45 c | Types and comparisons | The comparison 0.1 + 0.2 === 0.3 returns false. | «yes» Пояснение: Due to floating-point precision, 0.1 + 0.2 equals approximately 0.30000000000000004, which is not strictly equal to 0.3, so === returns false.
Raw{"answer": "yes", "explanation": "Due to floating-point precision, 0.1 + 0.2 equals approximately 0.30000000000000004, which is not strictly equal to 0.3, so === returns false."} | верно | Двоичная погрешность float: 0.1 + 0.2 = 0.30000000000000004. |
T03-L1 1.44 c | Strings | strrev() correctly reverses a UTF-8 string. | «no» Пояснение: strrev() reverses bytes, not characters, so multi-byte UTF-8 characters get split and produce invalid output.
Raw{"answer":"no","explanation":"strrev() reverses bytes, not characters, so multi-byte UTF-8 characters get split and produce invalid output."} | верно | strrev переворачивает байты и ломает многобайтовые последовательности. |
T03-L2 0.75 c | Strings | str_contains('Hello world', 'world') returns true. | «yes» Пояснение: str_contains() returns true when the haystack contains the needle, and 'Hello world' does contain 'world'.
Raw{"answer": "yes", "explanation": "str_contains() returns true when the haystack contains the needle, and 'Hello world' does contain 'world'."} | верно | str_contains с PHP 8.0 проверяет вхождение подстроки. |
T03-L3 0.83 c | Strings | str_pad() can pad a string on the right side only. | «no» Пояснение: str_pad() can pad on the right, left, or both sides using the $pad_type parameter (STR_PAD_RIGHT, STR_PAD_LEFT, STR_PAD_BOTH).
Raw{"answer": "no", "explanation": "str_pad() can pad on the right, left, or both sides using the $pad_type parameter (STR_PAD_RIGHT, STR_PAD_LEFT, STR_PAD_BOTH)."} | верно | STR_PAD_LEFT / STR_PAD_BOTH меняют сторону дополнения. |
T03-L4 1.16 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 (" \t\n\r\0\x0B"), not just spaces.
Raw{"answer":"no","explanation":"By default trim() strips spaces, tabs, newlines, carriage returns, null bytes, and vertical tabs (\" \\t\\n\\r\\0\\x0B\"), not just spaces."} | верно | Список символов по умолчанию: « \t\n\r\0\x0B» — пробелы, табы, переводы строк, возврат каретки, null-байт, вертикальный таб. Проверено php -r. |
T03-L5 1.02 c | Strings | How many BYTES does strlen('héllo') return for a UTF-8 string? | «6» Пояснение: strlen() counts bytes; 'é' is 2 bytes in UTF-8, plus 4 single-byte ASCII characters = 6 bytes total.
Raw{"answer": 6, "explanation": "strlen() counts bytes; 'é' is 2 bytes in UTF-8, plus 4 single-byte ASCII characters = 6 bytes total."} | верно | 6 букв по 2 байта: 12. |
T03-L6 0.9 c | Strings | What does substr('abcdef', -3) return? | «def» Пояснение: substr with a negative start of -3 begins 3 characters from the end of the string, returning 'def'.
Raw{"answer": "def", "explanation": "substr with a negative start of -3 begins 3 characters from the end of the string, returning 'def'."} | верно | Отрицательное смещение — с конца: def. |
T03-L7 0.96 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.
Raw{"answer": "no", "explanation": "ucfirst() returns a new string with the first character uppercased; it does not modify the original string in place."} | верно | Строки неизменяемы; ucfirst возвращает новую строку. |
T03-L8 0.88 c | Strings | Variable interpolation works in heredoc but not in nowdoc. | «yes» Пояснение: Heredoc supports variable interpolation (like double-quoted strings), while nowdoc treats the content like a single-quoted string, so variables are not expanded.
Raw{"answer": "yes", "explanation": "Heredoc supports variable interpolation (like double-quoted strings), while nowdoc treats the content like a single-quoted string, so variables are not expanded."} | верно | Nowdoc — «одинарные кавычки» в тройном синтаксисе: текст как есть. |
T04-L1 0.93 c | Arrays | The sort() function preserves the key-to-value association of the array. | «no» Пояснение: sort() re-indexes the array with numeric keys, while asort() is the function that preserves key-to-value associations.
Raw{"answer": "no", "explanation": "sort() re-indexes the array with numeric keys, while asort() is the function that preserves key-to-value associations."} | верно | sort перенумеровывает ключи; связь сохраняет asort. |
T04-L2 0.77 c | Arrays | The string key '5' in an array is stored as the integer 5. | «yes» Пояснение: In PHP, numeric string keys in arrays are automatically cast to integers, so '5' and 5 refer to the same key.
Raw{"answer": "yes", "explanation": "In PHP, numeric string keys in arrays are automatically cast to integers, so '5' and 5 refer to the same key."} | верно | Каноничные десятичные строковые ключи приводятся к int. |
T04-L3 0.83 c | Arrays | The in_array() function uses strict comparison (===) by default. | «no» Пояснение: in_array() uses loose comparison (==) by default; strict comparison requires the third parameter to be set to true.
Raw{"answer": "no", "explanation": "in_array() uses loose comparison (==) by default; strict comparison requires the third parameter to be set to true."} | верно | По умолчанию сравнение нестрогое; строгое — третий аргумент true. |
T04-L4 0.8 c | Arrays | Without a callback, array_filter() removes all "empty" (falsy) elements from the array. | «yes» Пояснение: When array_filter() is called without a callback, it removes all elements that evaluate to falsy (0, '', null, false, '0').
Raw{"answer": "yes", "explanation": "When array_filter() is called without a callback, it removes all elements that evaluate to falsy (0, '', null, false, '0')."} | верно | Убирает 0, "", null, false и пустые массивы. |
T04-L5 0.98 c | Arrays | By default, array_slice() preserves the original numeric keys of the array. | «no» Пояснение: The $preserve_keys parameter of array_slice() defaults to false, meaning keys are reindexed by default.
Raw{"answer": "no", "explanation": "The $preserve_keys parameter of array_slice() defaults to false, meaning keys are reindexed by default."} | верно | По умолчанию ключи перенумеровываются; сохранение — preserve_keys = true. |
T04-L6 1.36 c | Arrays | What does array_slice([10, 20, 30, 40], 1, 2) return? | «[20, 30]» Пояснение: array_slice with offset 1 and length 2 returns the two elements starting at index 1, which are 20 and 30.
Raw{"answer": "[20, 30]", "explanation": "array_slice with offset 1 and length 2 returns the two elements starting at index 1, which are 20 and 30."} | верно | [20,30]; ключи перенумеровываются. |
T04-L7 1.67 c | Arrays | How many elements will count(['a' => 1] + ['a' => 9, 'b' => 2]) return? | «2» Пояснение: The + operator keeps left array values for duplicate keys and only adds new keys from the right, resulting in ['a' => 1, 'b' => 2].
Raw{"answer": 2, "explanation": "The + operator keeps left array values for duplicate keys and only adds new keys from the right, resulting in ['a' => 1, 'b' => 2]."} | верно | Оператор + : по ключу 'a' побеждает левый; итого 2. |
T04-L8 1.91 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, preserving them in the resulting array.
Raw{"answer": "yes", "explanation": "PHP 8.1 introduced the array spread operator which supports both integer and string keys, preserving them in the resulting array."} | верно | В 8.0 — только числовые ключи; 8.1 снял ограничение. |
T05-L1 1.81 c | Functions and closures | Named arguments cannot be combined with argument unpacking ...$args in a single call. | «no» Пояснение: In PHP 8.0+, named arguments can be combined with argument unpacking in the same call, e.g. foo(...$args, c: 3).
Raw{"answer": "no", "explanation": "In PHP 8.0+, named arguments can be combined with argument unpacking in the same call, e.g. foo(...$args, c: 3)."} | верно | Можно: f(...$args, имя: значение). Нельзя только позиционный аргумент после распаковки. |
T05-L2 1.28 c | Functions and closures | An anonymous function without use sees variables from the outer scope. | «no» Пояснение: In PHP, closures do not automatically inherit variables from the outer scope; they must be explicitly imported using the 'use' keyword.
Raw{"answer": "no", "explanation": "In PHP, closures do not automatically inherit variables from the outer scope; they must be explicitly imported using the 'use' keyword."} | верно | Без use внешние переменные недоступны; авто-захват только у fn. |
T05-L3 0.79 c | Functions and closures | What will func_num_args() return inside function f($a) { return func_num_args(); } when called as f(1, 2, 3)? | «3» Пояснение: func_num_args() returns the number of arguments actually passed to the function (3), regardless of how many parameters are declared in the signature.
Raw{"answer": 3, "explanation": "func_num_args() returns the number of arguments actually passed to the function (3), regardless of how many parameters are declared in the signature."} | верно | Считает переданные аргументы: 3. |
T05-L4 1.03 c | Functions and closures | The body of an arrow function fn may consist of several expressions in curly braces. | «no» Пояснение: An arrow function (fn) body must be a single expression, not multiple statements in curly braces.
Raw{"answer": "no", "explanation": "An arrow function (fn) body must be a single expression, not multiple statements in curly braces."} | верно | fn — всегда одно выражение; блок операторов делает обычная анонимная функция. |
T05-L5 1.15 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, not by reference.
Raw{"answer": "no", "explanation": "PHP arrow functions (fn) capture outer variables by value, not by reference."} | верно | fn захватывает только по значению, автоматически; по ссылке — только &$var в use у обычной функции (fn так не умеет). |
T05-L6 0.94 c | Functions and closures | A closure declared as static function () {} does not capture $this. | «yes» Пояснение: In PHP, a static closure explicitly does not bind $this, unlike a regular closure which captures $this automatically when created within an object context.
Raw{"answer": "yes", "explanation": "In PHP, a static closure explicitly does not bind $this, unlike a regular closure which captures $this automatically when created within an object context."} | верно | static-замыкание отвязано от объекта: $this внутри недоступен. |
T05-L7 1.36 c | Functions and closures | What will this print: $x = 5; $f = function () use ($x) { return $x; }; $x = 7; echo $f(); | «5» Пояснение: The use clause captures $x by value (no &), so the closure retains the original value of 5 even after $x is reassigned to 7.
Raw{"answer": 5, "explanation": "The use clause captures $x by value (no &), so the closure retains the original value of 5 even after $x is reassigned to 7."} | верно | use захватывает по значению в момент создания: 5. |
T05-L8 1.06 c | Functions and closures | In weak typing mode (without strict_types), passing the string "5" to an int parameter is allowed. | «yes» Пояснение: In weak typing mode (default), PHP performs type coercion, so the string '5' is automatically converted to the integer 5 when passed to an int parameter.
Raw{"answer": "yes", "explanation": "In weak typing mode (default), PHP performs type coercion, so the string '5' is automatically converted to the integer 5 when passed to an int parameter."} | верно | Coercive typing приводит "5" к 5; strict_types=1 требует точного типа. |
T06-L1 0.71 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.
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."} | верно | С PHP 8.0 параметр с модификатором создаёт свойство и присваивание. |
T06-L2 0.64 c | OOP: classes and inheritance | Which keyword prevents a method from being overridden in subclasses? | «final» Пояснение: The 'final' keyword in PHP prevents a method from being overridden in subclasses.
Raw{"answer": "final", "explanation": "The 'final' keyword in PHP prevents a method from being overridden in subclasses."} | верно | final. |
T06-L3 0.63 c | OOP: classes and inheritance | A method declared final cannot be overridden in a subclass. | «yes» Пояснение: In PHP, the final keyword prevents a method from being overridden by subclasses.
Raw{"answer": "yes", "explanation": "In PHP, the final keyword prevents a method from being overridden by subclasses."} | верно | final запрещает переопределение метода и наследование класса. |
T06-L4 0.67 c | OOP: classes and inheritance | Parent properties with private visibility are accessible in a subclass. | «no» Пояснение: Private properties are only accessible within the class where they are declared, not in subclasses.
Raw{"answer": "no", "explanation": "Private properties are only accessible within the class where they are declared, not in subclasses."} | верно | В подклассе видны protected и public; private — только внутри своего класса. |
T06-L5 2.54 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, anonymous classes created with 'new class {}' get a generated name in the format 'class@anonymous\0/path/to/file.php:line', so the part before the NUL byte is 'class@anonymous'.
Raw```json ⏎ {"answer": "class@anonymous", "explanation": "In PHP, anonymous classes created with 'new class {}' get a generated name in the format 'class@anonymous\\0/path/to/file.php:line', so the part before the NUL byte is 'class@anonymous'."} ⏎ ``` | верно | get_class анонимного класса печатает class@anonymous\0<файл>:<строка>$n; короткая форма — часть до NUL-байта. Проверено php -r (hex). |
T06-L6 1.35 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 not inherited and are invisible to child classes, so a child can declare a method with the same name and any visibility without conflict.
Raw{"answer": "yes", "explanation": "In PHP, private methods are not inherited and are invisible to child classes, so a child can declare a method with the same name and any visibility without conflict."} | верно | private-члены не наследуются — правила совместимости подписей не действуют. |
T06-L7 1.09 c | OOP: classes and inheritance | The magic method __get() is called only for non-existent properties. | «no» Пояснение: __get() is called for both inaccessible (private/protected) and non-existent properties, not just non-existent ones.
Raw{"answer": "no", "explanation": "__get() is called for both inaccessible (private/protected) and non-existent properties, not just non-existent ones."} | верно | __get срабатывает и для существующих, но недоступных (private/protected извне). |
T06-L8 1.5 c | OOP: classes and inheritance | What does reassigning a readonly property throw — Exception or Error? | «error» Пояснение: Reassigning a readonly property in PHP throws a ReadOnlyProperty error, which extends the Error class.
Raw{"answer": "Error", "explanation": "Reassigning a readonly property in PHP throws a ReadOnlyProperty error, which extends the Error class."} | верно | Error (readonly с 8.1); оговорка: в __clone() переинициализация допустима (8.3+). |
T07-L1 0.65 c | Interfaces, traits, enum | An interface can declare constants. | «yes» Пояснение: PHP interfaces can declare constants, which are always implicitly public and can be accessed via the interface name.
Raw{"answer": "yes", "explanation": "PHP interfaces can declare constants, which are always implicitly public and can be accessed via the interface name."} | верно | Константы интерфейса наследуются реализациями. |
T07-L2 0.4 c | Interfaces, traits, enum | Which operator checks whether an object is an instance of a class or interface? | «instanceof» Пояснение: The instanceof operator checks whether an object is an instance of a specific class or interface.
Raw{"answer": "instanceof", "explanation": "The instanceof operator checks whether an object is an instance of a specific class or interface."} | верно | instanceof. |
T07-L3 1.2 c | Interfaces, traits, enum | An interface can declare static methods. | «no» Пояснение: In PHP, interface methods must be abstract and non-static; declaring a static method in an interface results in a fatal error.
Raw{"answer": "no", "explanation": "In PHP, interface methods must be abstract and non-static; declaring a static method in an interface results in a fatal error."} | неверно верный: «yes» | Реализация обязана дать статический метод с той же сигнатурой. |
T07-L4 1.17 c | Interfaces, traits, enum | The instanceof operator only checks class inheritance: it ignores interfaces. | «no» Пояснение: The instanceof operator in PHP returns true if the object is an instance of a class OR implements an interface, so it does not ignore interfaces.
Raw{"answer":"no","explanation":"The instanceof operator in PHP returns true if the object is an instance of a class OR implements an interface, so it does not ignore interfaces."} | верно | instanceof возвращает true и для интерфейсов объекта. |
T07-L5 1.4 c | Interfaces, traits, enum | An interface method may have a default implementation, like a trait method. | «no» Пояснение: Interface methods in PHP are always abstract and cannot have a default implementation; only traits can provide method bodies.
Raw{"answer": "no", "explanation": "Interface methods in PHP are always abstract and cannot have a default implementation; only traits can provide method bodies."} | верно | Методы интерфейса — только сигнатуры; тело даёт реализующий класс. |
T07-L6 0.79 c | Interfaces, traits, enum | An abstract method in an abstract class may have protected visibility. | «yes» Пояснение: In PHP, abstract methods can be declared as public or protected, but not private.
Raw{"answer": "yes", "explanation": "In PHP, abstract methods can be declared as public or protected, but not private."} | верно | В абстрактном классе — любая видимость; в интерфейсе — только public. |
T07-L7 0.82 c | Interfaces, traits, enum | How many elements will Foo::cases() return for enum Foo { case A; case B; case C; }? | «3» Пояснение: Foo::cases() returns an array containing all defined cases of the enum, which are A, B, and C — three elements.
Raw{"answer": 3, "explanation": "Foo::cases() returns an array containing all defined cases of the enum, which are A, B, and C — three elements."} | верно | Статический метод cases(): 3. |
T07-L8 0.81 c | Interfaces, traits, enum | A trait can declare constants. | «yes» Пояснение: Traits in PHP can declare constants, which are then available to any class that uses the trait.
Raw{"answer": "yes", "explanation": "Traits in PHP can declare constants, which are then available to any class that uses the trait."} | верно | С PHP 8.2 трейты могут объявлять константы (RFC constants_in_traits); до 8.2 — нет. |
T08-L1 1.06 c | Exceptions and errors | The Throwable interface is a common ancestor of both Exception and Error. | «yes» Пояснение: In PHP 7+, both Exception and Error implement the Throwable interface, making it their common ancestor.
Raw{"answer": "yes", "explanation": "In PHP 7+, both Exception and Error implement the Throwable interface, making it their common ancestor."} | верно | Иерархия с PHP 7: Throwable → Exception и Throwable → Error. |
T08-L2 1.43 c | Exceptions and errors | A catch (Exception $e) block will also catch TypeError, because TypeError ultimately inherits from Exception. | «no» Пояснение: TypeError extends Error, not Exception; both Exception and Error are separate branches under the Throwable interface.
Raw{"answer": "no", "explanation": "TypeError extends Error, not Exception; both Exception and Error are separate branches under the Throwable interface."} | верно | TypeError наследуется от Error; catch (Exception) его не ловит. |
T08-L3 0.75 c | Exceptions and errors | The @ operator suppresses exceptions too. | «no» Пояснение: The @ operator only suppresses errors (warnings, notices, etc.), not exceptions; exceptions must still be caught with try/catch.
Raw{"answer": "no", "explanation": "The @ operator only suppresses errors (warnings, notices, etc.), not exceptions; exceptions must still be caught with try/catch."} | верно | @ глушит диагностику (warnings/notices), исключения не перехватывает. |
T08-L4 1.32 c | Exceptions and errors | What error class does intdiv(5, 0) throw? | «divisionbyzeroerror» Пояснение: intdiv(5, 0) throws a DivisionByZeroError in PHP 7.0+, which extends ArithmeticError.
Raw{"answer": "DivisionByZeroError", "explanation": "intdiv(5, 0) throws a DivisionByZeroError in PHP 7.0+, which extends ArithmeticError."} | верно | DivisionByZeroError (иерархия Error, не Exception); php-грейдер объективен. |
T08-L5 1.02 c | Exceptions and errors | The finally block runs only if the exception was caught by a catch block. | «no» Пояснение: The finally block runs regardless of whether an exception was thrown, caught, or not — it always executes after the try/catch blocks.
Raw{"answer": "no", "explanation": "The finally block runs regardless of whether an exception was thrown, caught, or not — it always executes after the try/catch blocks."} | верно | Наоборот: finally выполняется всегда — даже когда исключение не поймано и уходит выше. Проверено php -r. |
T08-L6 1.39 c | Exceptions and errors | An exception thrown inside a finally block has no effect on the result of the try block. | «no» Пояснение: An exception thrown in a finally block will replace (suppress) any exception from the try/catch block, so it does have an effect on the result.
Raw{"answer": "no", "explanation": "An exception thrown in a finally block will replace (suppress) any exception from the try/catch block, so it does have an effect on the result."} | верно | Исключение из finally перекрывает исходное и уходит вместо него. |
T08-L7 1.14 c | Exceptions and errors | What does the expression (bool) new Exception('x') return? | «yes» Пояснение: In PHP, any object cast to bool always results in true, because objects are inherently truthy.
Raw{"answer": "yes", "explanation": "In PHP, any object cast to bool always results in true, because objects are inherently truthy."} | верно | Любой объект при приведении к bool — true. Формы ответа: true или да. |
T08-L8 1.23 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 at the end of the request cycle, which includes when exit or die is called.
Raw{"answer": "yes", "explanation": "Shutdown functions registered with register_shutdown_function() are executed at the end of the request cycle, which includes when exit or die is called."} | верно | exit завершает скрипт, но shutdown-функции отрабатывают. |
T09-L1 1.01 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 the FQCN; the class file is actually loaded (via autoloading) only when the class is first used at runtime.
Raw{"answer": "no", "explanation": "The use statement only creates a local alias for the FQCN; the class file is actually loaded (via autoloading) only when the class is first used at runtime."} | верно | use — псевдоним на этапе компиляции; файл грузит автозагрузчик при первом обращении. |
T09-L2 1.06 c | Namespaces and autoloading | What follows use to import a function (not a class): the word function or const? | «function» Пояснение: In PHP, to import a function you use 'use function' (e.g., use function Foo\bar();), while 'use const' is for importing constants.
Raw{"answer": "function", "explanation": "In PHP, to import a function you use 'use function' (e.g., use function Foo\\bar();), while 'use const' is for importing constants."} | верно | use function ...; (и use const для констант). |
T09-L3 1.45 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 maps the remaining sub-namespaces (Controller\Api) to subdirectories and the class name to the filename, appended to the base path src/.
Raw```json ⏎ {"answer": "Controller/Api/UserController.php", "explanation": "PSR-4 maps the remaining sub-namespaces (Controller\\Api) to subdirectories and the class name to the filename, appended to the base path src/."} ⏎ ``` | верно | Остаток имени после префикса, \ → /. |
T09-L4 0.84 c | Namespaces and autoloading | Including vendor/autoload.php registers autoloaders via spl_autoload_register(). | «yes» Пояснение: Composer's generated vendor/autoload.php ultimately calls spl_autoload_register() to register its autoloader.
Raw{"answer": "yes", "explanation": "Composer's generated vendor/autoload.php ultimately calls spl_autoload_register() to register its autoloader."} | верно | Composer ставит автозагрузчик именно на spl_autoload_register. |
T09-L5 0.82 c | Namespaces and autoloading | The magic constant __NAMESPACE__ contains the name of the current namespace. | «yes» Пояснение: __NAMESPACE__ is a PHP magic constant that evaluates to 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 evaluates to the name of the current namespace (or an empty string if in the global namespace)."} | верно | В корневом пространстве — пустая строка. |
T09-L6 1.56 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 'new' is resolved relative to the current namespace, not from the global root; only a leading backslash forces global resolution.
Raw```json ⏎ {"answer": "no", "explanation": "An unqualified class name in 'new' is resolved relative to the current namespace, not from the global root; only a leading backslash forces global resolution."} ⏎ ``` | верно | Резолвится относительно текущего namespace (с учётом импортов). |
T09-L7 1.24 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 strips the mapped namespace prefix 'App\', converts the remaining 'Model\User' to a relative path 'Model/User.php', and prepends the base directory 'src/', yielding src/Model/User.php.
Raw{"answer": "yes", "explanation": "PSR-4 strips the mapped namespace prefix 'App\\', converts the remaining 'Model\\User' to a relative path 'Model/User.php', and prepends the base directory 'src/', yielding src/Model/User.php."} | верно | Остаток имени после префикса переносится в путь как есть. |
T09-L8 1.94 c | Namespaces and autoloading | A use statement may be written inside a function body — the import then applies to that function only. | «yes» Пояснение: PHP allows a use statement inside a function body, creating a local alias that only applies within that function's scope.
Raw{"answer": "yes", "explanation": "PHP allows a use statement inside a function body, creating a local alias that only applies within that function's scope."} | неверно верный: «no» | use внутри тела функции — parse error; импорты файловые и компиляционные. |
T10-L1 1.16 c | References and scope | Arrays are copied on assignment rather than passed by reference. | «yes» Пояснение: In PHP, arrays are value types and are copied on assignment by default; you must explicitly use the & operator to pass or assign by reference.
Raw{"answer": "yes", "explanation": "In PHP, arrays are value types and are copied on assignment by default; you must explicitly use the & operator to pass or assign by reference."} | верно | Присваивание массива — копия (в движке — copy-on-write). |
T10-L2 1.04 c | References and scope | What will this print: $a = [1, 2]; $b = $a; $b[] = 3; echo count($a); | «2» Пояснение: PHP arrays are copied by value, so modifying $b does not affect $a, which still contains 2 elements.
Raw{"answer": 2, "explanation": "PHP arrays are copied by value, so modifying $b does not affect $a, which still contains 2 elements."} | верно | Присваивание — копия: в $a по-прежнему 2 элемента. |
T10-L3 1.05 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 functions unless explicitly accessed via global, $GLOBALS, or passed as parameters.
Raw{"answer": "yes", "explanation": "In PHP, variables defined in the global scope are not visible inside functions unless explicitly accessed via global, $GLOBALS, or passed as parameters."} | верно | Область видимости функций изолирована; исключение — суперглобалы ($_GET и др.). |
T10-L4 1.43 c | References and scope | unset($GLOBALS['x']) inside a function removes the global variable only for that function. | «no» Пояснение: unset($GLOBALS['x']) removes the variable from the global scope entirely, not just within that function's local scope.
Raw{"answer": "no", "explanation": "unset($GLOBALS['x']) removes the variable from the global scope entirely, not just within that function's local scope."} | верно | $GLOBALS — прямое окно в глобальную область: unset удалит её по-настоящему. |
T10-L5 0.98 c | References and scope | What will this print: function inc(&$x) { $x++; } $n = 5; inc($n); echo $n; | «6» Пояснение: The parameter is passed by reference (&$x), so incrementing $x inside the function also increments $n, making it 6.
Raw{"answer": 6, "explanation": "The parameter is passed by reference (&$x), so incrementing $x inside the function also increments $n, making it 6."} | верно | Ссылка меняет оригинал: 6. |
T10-L6 2.98 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 foreach by value iterates over a copy of the array, so modifications to the original array inside the loop are not reflected in the current pass.
Raw```json ⏎ {"answer": "no", "explanation": "A foreach by value iterates over a copy of the array, so modifications to the original array inside the loop are not reflected in the current pass."} ⏎ ``` | верно | По значению foreach итерирует копию-снимок. |
T10-L7 0.95 c | References and scope | A static property belongs to each instance separately: changes in one object are not visible in others. | «no» Пояснение: A static property belongs to the class itself and is shared among all instances; changes made through one instance are visible in all others.
Raw{"answer": "no", "explanation": "A static property belongs to the class itself and is shared among all instances; changes made through one instance are visible in all others."} | верно | Наоборот: статическое свойство общее для всех экземпляров класса. Проверено php -r. |
T10-L8 1.15 c | References and scope | An array can have a boolean key true, and it will be stored as bool. | «no» Пояснение: In PHP, boolean keys are cast to integers: true becomes 1 and false becomes 0, so the key is stored as an integer, not a boolean.
Raw{"answer": "no", "explanation": "In PHP, boolean keys are cast to integers: true becomes 1 and false becomes 0, so the key is stored as an integer, not a boolean."} | верно | Булев ключ приводится к int: true → 1, false → 0. |
T11-L1 0.9 c | Generators, iterators, SPL | Inside a generator, return with a value can be used, and it becomes available via $gen->getReturn(). | «yes» Пояснение: Since PHP 7.0, generators support return with a value, accessible via $gen->getReturn().
Raw{"answer": "yes", "explanation": "Since PHP 7.0, generators support return with a value, accessible via $gen->getReturn()."} | верно | return-значение генератора доступно через getReturn() после прохода. |
T11-L2 1.11 c | Generators, iterators, SPL | A fully consumed generator can be rewound with rewind() and traversed again. | «no» Пояснение: Once a generator is fully consumed and closed, calling rewind() on it throws a RuntimeException; generators are one-shot iterators.
Raw{"answer": "no", "explanation": "Once a generator is fully consumed and closed, calling rewind() on it throws a RuntimeException; generators are one-shot iterators."} | верно | Генератор одноразовый: rewind после начала итерации бросает Exception. |
T11-L3 1.39 c | Generators, iterators, SPL | The yield from construct delegates traversal to another generator or iterable. | «no» Пояснение: PHP has 'yield' but no 'yield from' construct; 'yield from' is a Python feature.
Raw{"answer": "no", "explanation": "PHP has 'yield' but no 'yield from' construct; 'yield from' is a Python feature."} | неверно верный: «yes» | yield from проксирует значения, ключи и return-значение внутреннего генератора. |
T11-L4 1.09 c | Generators, iterators, SPL | What does get_class(g()) return for function g() { yield 1; }? | «generator» Пояснение: Calling a generator function returns an instance of the built-in Generator class, so get_class() returns the string 'Generator'.
Raw```json ⏎ {"answer": "Generator", "explanation": "Calling a generator function returns an instance of the built-in Generator class, so get_class() returns the string 'Generator'."} ⏎ ``` | верно | Функция с yield возвращает Generator. |
T11-L5 1.31 c | Generators, iterators, SPL | How many elements will count(iterator_to_array((function () { yield from [1, 2, 3]; })())) return? | «3» Пояснение: yield from [1, 2, 3] produces three values, and count() on the resulting array returns 3.
Raw{"answer": 3, "explanation": "yield from [1, 2, 3] produces three values, and count() on the resulting array returns 3."} | верно | yield from делегирует все 3 элемента. |
T11-L6 0.59 c | Generators, iterators, SPL | The SplStack class implements a FIFO queue. | «no» Пояснение: SplStack implements a LIFO (Last In, First Out) stack, while SplQueue implements a FIFO queue.
Raw{"answer": "no", "explanation": "SplStack implements a LIFO (Last In, First Out) stack, while SplQueue implements a FIFO queue."} | верно | SplStack — стек LIFO; очередь FIFO — SplQueue. |
T11-L7 0.7 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 implements the Iterator interface and is designed to wrap an array for traversal.
Raw{"answer": "yes", "explanation": "ArrayIterator is a built-in PHP class that implements the Iterator interface and is designed to wrap an array for traversal."} | верно | Объектная обёртка над массивом. |
T11-L8 1.05 c | Generators, iterators, SPL | An ArrayObject instance cannot be traversed with foreach. | «no» Пояснение: ArrayObject implements the Iterator interface, so it can be traversed with foreach.
Raw{"answer": "no", "explanation": "ArrayObject implements the Iterator interface, so it can be traversed with foreach."} | верно | ArrayObject реализует IteratorAggregate — foreach по нему работает. |
T12-L1 1.36 c | Configuration and security | password_hash() generates a salt automatically — passing one separately is not needed. | «yes» Пояснение: password_hash() automatically generates a random salt and embeds it in the returned hash string; no separate salt is required.
Raw{"answer": "yes", "explanation": "password_hash() automatically generates a random salt and embeds it in the returned hash string; no separate salt is required."} | верно | Соль встраивается в строку результата; параметр salt устарел. |
T12-L2 1.09 c | Configuration and security | In PHP 8, PASSWORD_DEFAULT is md5 with an automatically added salt. | «no» Пояснение: In PHP 8, PASSWORD_DEFAULT is Argon2id (or Argon2/bcrypt as fallback), not md5.
Raw{"answer": "no", "explanation": "In PHP 8, PASSWORD_DEFAULT is Argon2id (or Argon2/bcrypt as fallback), not md5."} | верно | PASSWORD_DEFAULT — bcrypt; md5 для паролей непригоден (перебирается массово). |
T12-L3 0.91 c | Configuration and security | What does password_verify('secret', password_hash('secret', PASSWORD_DEFAULT)) return? | «yes» Пояснение: password_verify() returns true when the plaintext password matches the hash generated by password_hash().
Raw{"answer": "yes", "explanation": "password_verify() returns true when the plaintext password matches the hash generated by password_hash()."} | верно | Соль и хеш в одной строке: true (форма ответа: true или да). |
T12-L4 0.92 c | Configuration and security | strip_tags() protects against SQL injection. | «no» Пояснение: strip_tags() removes HTML/PHP tags from a string but does not protect against SQL injection; prepared statements or parameterized queries are needed for that.
Raw{"answer": "no", "explanation": "strip_tags() removes HTML/PHP tags from a string but does not protect against SQL injection; prepared statements or parameterized queries are needed for that."} | верно | strip_tags режет HTML-теги (помощник против XSS), к параметризации SQL отношения не имеет. |
T12-L5 1.17 c | Configuration and security | session_regenerate_id() is used to protect against session fixation upon user login. | «yes» Пояснение: session_regenerate_id() generates a new session ID, which is a standard defense against session fixation attacks, typically called after login.
Raw{"answer": "yes", "explanation": "session_regenerate_id() generates a new session ID, which is a standard defense against session fixation attacks, typically called after login."} | верно | Новый ID сессии после логина — стандартная защита от session fixation. |
T12-L6 0.69 c | Configuration and security | Which built-in function returns the SAPI name (e.g., cli)? | «php_sapi_name()» Пояснение: php_sapi_name() is the built-in function that returns the current SAPI module name, such as 'cli' for command-line usage.
Raw{"answer": "php_sapi_name()", "explanation": "php_sapi_name() is the built-in function that returns the current SAPI module name, such as 'cli' for command-line usage."} | верно | php_sapi_name(). |
T12-L7 1.08 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; the session cookie in the browser must be deleted separately (e.g., with setcookie() setting an expiration in the past).
Raw{"answer": "yes", "explanation": "session_destroy() only removes the session data on the server; the session cookie in the browser must be deleted separately (e.g., with setcookie() setting an expiration in the past)."} | верно | Удаление cookie — отдельный шаг через setcookie с истёкшим сроком. |
T12-L8 0.85 c | Configuration and security | Without calling session_start(), the $_SESSION array is automatically populated with session data. | «no» Пояснение: The $_SESSION superglobal is only populated with session data after session_start() has been called.
Raw{"answer": "no", "explanation": "The $_SESSION superglobal is only populated with session data after session_start() has been called."} | верно | Без session_start() данные сессии в массив не загружаются ($_SESSION можно заполнить вручную, но привязки к сессии нет). |
VC-L1 3.93 c | PHP 8.4–8.5 | In which PHP version was the array_find() function introduced? | «8.4» Пояснение: The array_find() function was introduced in PHP 8.4 as part of new array helper functions.
Raw{"answer": "8.4", "explanation": "The array_find() function was introduced in PHP 8.4 as part of new array helper functions."} | верно | PHP 8.4 (RFC array_find). |
VC-L2 1.12 c | PHP 8.4–8.5 | Property hooks (get/set right in the property declaration) landed in PHP 8.4. | «yes» Пояснение: Property hooks, allowing custom get/set logic directly in the property declaration, were introduced in PHP 8.4.
Raw{"answer": "yes", "explanation": "Property hooks, allowing custom get/set logic directly in the property declaration, were introduced in PHP 8.4."} | верно | Property hooks — PHP 8.4 (ноябрь 2024). |
VC-L3 0.93 c | PHP 8.4–8.5 | Asymmetric visibility (public private(set) string $name) appeared in PHP 8.4. | «yes» Пояснение: Asymmetric visibility (e.g., public private(set)) was introduced as a new feature in PHP 8.4.
Raw{"answer": "yes", "explanation": "Asymmetric visibility (e.g., public private(set)) was introduced as a new feature in PHP 8.4."} | верно | Asymmetric visibility v2 — PHP 8.4. |
VC-L4 4.06 c | PHP 8.4–8.5 | In which PHP version was the #[\NoDiscard] attribute introduced? Answer with the version number. | «not a real attribute» Пояснение: There is no built-in #[\NoDiscard] attribute in PHP; it is not part of any released version.
Raw{"answer": "not a real attribute", "explanation": "There is no built-in #[\\NoDiscard] attribute in PHP; it is not part of any released version."} | неверно верный: «8.5» | #[\NoDiscard] — PHP 8.5 (marking return values as important). |
VC-L5 2.36 c | PHP 8.4–8.5 | In which PHP version did the pipe operator |> first appear? Answer with the version number. | «8.4» Пояснение: The pipe operator |> was introduced in PHP 8.4 as a new language feature.
Raw```json ⏎ {"answer": 8.4, "explanation": "The pipe operator |> was introduced in PHP 8.4 as a new language feature."} ⏎ ``` | неверно верный: «8.5» | Pipe operator — PHP 8.5 (2025). |
VC-L6 5.94 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. | «no» Пояснение: The clone-with syntax clone($obj, ['x' => 1]) has not been implemented in any released PHP version; it remains a proposed/unaccepted feature.
Raw{"answer": "no", "explanation": "The clone-with syntax clone($obj, ['x' => 1]) has not been implemented in any released PHP version; it remains a proposed/unaccepted feature."} | неверно верный: «8.5» | Clone with v2 — PHP 8.5. |
VC-L7 1.14 c | PHP 8.4–8.5 | In which PHP version were the array_first() and array_last() functions introduced? | «8.4» Пояснение: The array_first() and array_last() functions were introduced in PHP 8.4.
Raw```json ⏎ {"answer": "8.4", "explanation": "The array_first() and array_last() functions were introduced in PHP 8.4."} ⏎ ``` | неверно верный: «8.5» | PHP 8.5. |
VC-L8 3.57 c | PHP 8.4–8.5 | For which PHP version was RFC Partial Function Application v2 adopted (as of 2026-11-07)? Answer with the version number. | «8.4» Пояснение: The RFC Partial Function Application v2 was adopted for PHP 8.4.
Raw{"answer": "8.4", "explanation": "The RFC Partial Function Application v2 was adopted for PHP 8.4."} | неверно верный: «8.6» | PFA v2 принят 05.12.2025 (33-0-0), реализован в PHP 8.6. |
VF-L1 1.19 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 was introduced in PHP 8.4 via the clamp_v2 RFC.
Raw{"answer": "8.4", "explanation": "The clamp() function was introduced in PHP 8.4 via the clamp_v2 RFC."} | неверно верный: «8.6» | По данным владельца (wiki.php.net/rfc): clamp_v2 — 8.6; clamp() в 8.5.11 отсутствует (косвенное подтверждение). Дата-якорь делает клетку монотонной. |
VF-L2 1.73 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 widely known 'RFC Context Managers v2' adopted in PHP; the term 'context managers' is more closely associated with Python's 'with' statement.
Raw{"answer":"no","explanation":"There is no widely known 'RFC Context Managers v2' adopted in PHP; the term 'context managers' is more closely associated with Python's 'with' statement."} | верно | На 06.11.2026 — в обсуждении (создан 2026-10-23); не принят. |
VF-L3 3.58 c | PHP: 8.6+ and the future | RFC Bound-Erased Generic Types (generics) was declined in 2026. | «no» Пояснение: The Generics RFC (Bound-Erased Generic Types) was accepted for PHP 8.5, not declined.
Raw```json ⏎ {"answer": "no", "explanation": "The Generics RFC (Bound-Erased Generic Types) was accepted for PHP 8.5, not declined."} ⏎ ``` | неверно верный: «yes» | Голосование завершилось 2026-06-28: отклонён (wiki.php.net/rfc). |
VF-L4 3.76 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 2026, PHP has not accepted an RFC to make Zend Thread Safety (ZTS) the default build mode; NTS remains the default.
Raw```json ⏎ {"answer": "no", "explanation": "As of 2026, PHP has not accepted an RFC to make Zend Thread Safety (ZTS) the default build mode; NTS remains the default."} ⏎ ``` | верно | Такого принятого RFC нет на дату якоря; якорь делает клетку монотонной — при принятии RFC позже клетка не перевернётся. |
VF-L5 1.79 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 (parameterized types), and no accepted RFC adds them by PHP 8.5.
Raw{"answer": "yes", "explanation": "PHP has never included built-in generics (parameterized types), and no accepted RFC adds them by PHP 8.5."} | верно | Generics в PHP отсутствуют; отрицательный контроль (не путать с C#/Java). |
VF-L6 2.24 c | PHP: 8.6+ and the future | As of 2026-11-07, the latest stable PHP version is 8.5, and PHP 8.6 has not been released yet (GA — 2026-11-19). | «yes» Пояснение: PHP follows a mid-November GA release cycle, so PHP 8.5 (released Nov 2025) would be the latest stable as of 2026-11-07, with PHP 8.6's GA scheduled for 2026-11-19.
Raw```json ⏎ {"answer": "yes", "explanation": "PHP follows a mid-November GA release cycle, so PHP 8.5 (released Nov 2025) would be the latest stable as of 2026-11-07, with PHP 8.6's GA scheduled for 2026-11-19."} ⏎ ``` | верно | 8.5 — релиз осени 2025; 8.6 GA 19.11.2026 (wiki.php.net/todo/php86). Дата снимка — 06.11.2026. |
VF-L7 0.99 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 in development for years but was skipped; after PHP 5.6, the next major release was PHP 7.0 in December 2015.
Raw{"answer": "yes", "explanation": "PHP 6 was in development for years but was skipped; after PHP 5.6, the next major release was PHP 7.0 in December 2015."} | верно | Исторический факт: ветка 6 не была релизнута. |
VF-L8 1.91 c | PHP: 8.6+ and the future | The RFC adding the #[\Deprecated] attribute to the core was adopted. | «no» Пояснение: The RFC for a built-in #[\Deprecated] attribute was proposed but rejected during the voting process and was not adopted into PHP core.
Raw{"answer": "no", "explanation": "The RFC for a built-in #[\\Deprecated] attribute was proposed but rejected during the voting process and was not adopted into PHP core."} | неверно верный: «yes» | #[\Deprecated] — принят, реализован в PHP 8.4. |
T25-L1 1.23 c | Clean architecture | The dependency rule of clean and onion architecture: inner layers know nothing about outer ones — dependencies point toward the center. | «yes» Пояснение: The dependency rule in both Clean and Onion architecture states that dependencies must always point inward, meaning inner layers (domain) have no knowledge of outer layers (frameworks, UI, DB).
Raw{"answer": "yes", "explanation": "The dependency rule in both Clean and Onion architecture states that dependencies must always point inward, meaning inner layers (domain) have no knowledge of outer layers (frameworks, UI, DB)."} | верно | Чистая (Robert C. Martin), луковичная (Jeffrey Palermo) и гексагональная (ports & adapters) — варианты одной идеи: зависимости направлены внутрь, к домену. Слоями в проекте следит deptrac. |
T25-L2 1.26 c | Clean architecture | Domain entities import neither Doctrine nor Symfony — only the language and, possibly, the standard library. | «yes» Пояснение: In DDD and clean architecture, domain entities should be pure objects that depend only on the language and standard library, with no coupling to frameworks like Doctrine or Symfony.
Raw{"answer": "yes", "explanation": "In DDD and clean architecture, domain entities should be pure objects that depend only on the language and standard library, with no coupling to frameworks like Doctrine or Symfony."} | верно | Изоляция домена от инфраструктуры; deptrac в проекте как раз следит за слоями. |
T25-L3 1.19 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 (or interface) layer, not the business-logic layer; they merely orchestrate calls to use cases.
Raw{"answer": "no", "explanation": "Controllers and Twig templates belong to the presentation (or interface) layer, not the business-logic layer; they merely orchestrate calls to use cases."} | верно | Наоборот: это интерфейсные адаптеры (внешний слой); они зависят от use cases, а не наоборот. |
T25-L4 1.3 c | Clean architecture | What sits at the very center of the onion architecture? | «entity» Пояснение: In onion architecture, the innermost layer contains the core entities (domain model) representing the enterprise business rules.
Raw{"answer": "Entity", "explanation": "In onion architecture, the innermost layer contains the core entities (domain model) representing the enterprise business rules."} | неверно верный: «domain model» | Центральное кольцо — Domain Model: сущности и бизнес-правила без зависимостей; далее Domain Services → Application Services → Infrastructure/UI/Tests (Palermo). |
T25-L5 0.99 c | Clean architecture | Layer boundary violations can be caught automatically: a layer-dependency analyzer (e.g. deptrac) fails on a forbidden call. | «yes» Пояснение: Deptrac and similar layer-dependency analyzers enforce architectural rules by failing the build when a forbidden inter-layer dependency is detected.
Raw{"answer": "yes", "explanation": "Deptrac and similar layer-dependency analyzers enforce architectural rules by failing the build when a forbidden inter-layer dependency is detected."} | верно | depfile.yaml в проекте TasK: CI проверяет правила слоёв на каждом пайплайне. |
T25-L6 2.27 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 and domain entities, not on external details like HTTP requests or EntityManagers, to maintain framework-agnostic and easily testable business logic.
Raw{"answer": "no", "explanation": "A use case (interactor) should depend on abstractions and domain entities, not on external details like HTTP requests or EntityManagers, to maintain framework-agnostic and easily testable business logic."} | верно | Use case принимает DTO и порты; привязка к HTTP/ORM протекает инфраструктуру во внутренние слои. |
T25-L7 1.02 c | Clean architecture | What is the component called that provides a collection of aggregates/entities while hiding the storage mechanism behind an interface? | «repository» Пояснение: A Repository provides a collection-like interface for accessing domain aggregates/entities while abstracting away the underlying storage mechanism.
Raw{"answer": "Repository", "explanation": "A Repository provides a collection-like interface for accessing domain aggregates/entities while abstracting away the underlying storage mechanism."} | верно | Repository pattern (DDD/Evans); в проекте — Doctrine-репозитории за портами. |
T25-L8 2.39 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 domain and use cases depend only on abstract interfaces; the concrete database adapter lives in the outermost (frameworks & drivers) layer, so swapping the DB engine only affects that outer layer.
Raw```json ⏎ {"answer": "yes", "explanation": "In Clean Architecture, the domain and use cases depend only on abstract interfaces; the concrete database adapter lives in the outermost (frameworks & drivers) layer, so swapping the DB engine only affects that outer layer."} ⏎ ``` | верно | Следствие правила зависимостей: инфраструктура взаимозаменяема. |
T26-L1 1.26 c | DDD | In DDD, an aggregate is just another name for a database table. | «no» Пояснение: An aggregate in DDD is a cluster of domain objects treated as a consistency boundary, not a database table; mapping it to a table is a persistence concern, not part of the definition.
Raw{"answer": "no", "explanation": "An aggregate in DDD is a cluster of domain objects treated as a consistency boundary, not a database table; mapping it to a table is a persistence concern, not part of the definition."} | верно | Агрегат — кластер объектов с границей согласованности (транзакционной вокруг корня); таблица — деталь хранения. |
T26-L2 0.81 c | DDD | A Value Object is immutable and compared by the values of its fields, not by identity. | «yes» Пояснение: By definition in DDD, Value Objects are immutable and their equality is determined by their field values, not by reference identity.
Raw{"answer": "yes", "explanation": "By definition in DDD, Value Objects are immutable and their equality is determined by their field values, not by reference identity."} | верно | Классика Evans: Money, Email; равенство структурное. |
T26-L3 0.75 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 changes must be made.
Raw{"answer": "Aggregate Root", "explanation": "In Domain-Driven Design, the Aggregate Root is the single entry point of an aggregate through which all external changes must be made."} | верно | Aggregate Root: внешние объекты ссылаются только на корень; он защищает инварианты агрегата. |
T26-L4 1.01 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, managing the entire aggregate as a unit, and internal entities are accessed through the root.
Raw{"answer": "yes", "explanation": "In DDD, a repository is defined per aggregate root, managing the entire aggregate as a unit, and internal entities are accessed through the root."} | верно | Репозиторий корня хранит границу согласованности агрегата; вложенные сущности доступны только через корень. |
T26-L5 0.99 c | DDD | Ubiquitous language is the model's shared language common to developers and domain experts. | «yes» Пояснение: Ubiquitous Language, a concept from Domain-Driven Design (Eric Evans), is precisely the shared language between developers and domain experts that is used consistently in code, documentation, and conversation.
Raw{"answer": "yes", "explanation": "Ubiquitous Language, a concept from Domain-Driven Design (Eric Evans), is precisely the shared language between developers and domain experts that is used consistently in code, documentation, and conversation."} | верно | Evans: язык из требований переходит в имена классов и методов. |
T26-L6 5.24 c | DDD | What is the boundary called within which a model and its language are consistent, while outside the same words mean other models? | «paradigm» Пояснение: A paradigm is the boundary within which a model and its language are internally consistent, while outside it the same terms may refer to different models or frameworks.
Raw{"answer": "paradigm", "explanation": "A paradigm is the boundary within which a model and its language are internally consistent, while outside it the same terms may refer to different models or frameworks."} | неверно верный: «bounded context» | Bounded Context; «Заказ» в биллинге и в доставке — разные модели. |
T26-L7 1.29 c | DDD | An anemic model (objects with only getters/setters, logic in services) is the recommended DDD style. | «no» Пояснение: DDD recommends a rich domain model where entities and value objects encapsulate both state and behavior, not an anemic model with logic pushed into services.
Raw{"answer": "no", "explanation": "DDD recommends a rich domain model where entities and value objects encapsulate both state and behavior, not an anemic model with logic pushed into services."} | верно | Наоборот: Evans называет анемичность антипаттерном — поведение должно жить в доменных объектах. |
T26-L8 1.41 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 a boundary where a domain model is consistent; the same real-world concept (e.g., 'Customer') can be modeled as different classes with different attributes in different bounded contexts.
Raw{"answer": "yes", "explanation": "In DDD, a bounded context defines a boundary where a domain model is consistent; the same real-world concept (e.g., 'Customer') can be modeled as different classes with different attributes in different bounded contexts."} | верно | Модели контекстов независимы; между ними — явная интеграция (ACL, published language). |
T13-L1 0.94 c | Symfony | Services in the Symfony DI container are created lazily by default — on first use. | «yes» Пояснение: Symfony DI container services are instantiated lazily by default, meaning they are created only when first requested via get() rather than at container build time.
Raw{"answer": "yes", "explanation": "Symfony DI container services are instantiated lazily by default, meaning they are created only when first requested via get() rather than at container build time."} | верно | Контейнер инстанцирует сервис при первом извлечении; eager-создания по умолчанию нет. |
T13-L2 0.66 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.31 c | Symfony | Symfony autowiring requires manually declaring every service in services.yaml. | «no» Пояснение: The whole point of autowiring is that Symfony automatically resolves and injects dependencies based on type hints, so you do not need to manually declare every service.
Raw{"answer": "no", "explanation": "The whole point of autowiring is that Symfony automatically resolves and injects dependencies based on type hints, so you do not need to manually declare every service."} | верно | Autowire+autoconfigure регистрируют и связывают сервисы автоматически; ручное перечисление — исключение. |
T13-L4 0.93 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 them on disk to avoid recompilation on subsequent requests.
Raw{"answer": "yes", "explanation": "Twig compiles templates into PHP classes (extending Twig\\Template) and caches them on disk to avoid recompilation on subsequent requests."} | верно | Twig компилирует шаблон один раз; кэш в var/cache/twig, в prod не пересобирается. |
T13-L5 1.52 c | Symfony | In the Symfony dev environment the DI container is rebuilt only after tracked files change, not on every request. | «yes» Пояснение: In the dev environment, Symfony caches the compiled container and only rebuilds it when tracked files (services, configs, etc.) have changed, not on every request.
Raw{"answer": "yes", "explanation": "In the dev environment, Symfony caches the compiled container and only rebuilds it when tracked files (services, configs, etc.) have changed, not on every request."} | верно | Kernel проверяет freshness ресурсов (конфиги, классы); иначе переиспользуется кэш контейнера. |
T13-L6 0.8 c | Symfony | Which environment variable selects the active Symfony environment (dev/prod)? | «app_env» Пояснение: In Symfony, the APP_ENV environment variable selects the active environment (e.g., dev, prod).
Raw{"answer": "APP_ENV", "explanation": "In Symfony, the APP_ENV environment variable selects the active environment (e.g., dev, prod)."} | верно | APP_ENV в .env; APP_DEBUG — отдельный флаг отладки. |
T13-L7 2.3 c | Symfony | A controller method can be private — Symfony routing works with any method of the class. | «yes» Пояснение: Symfony's controller resolver uses ReflectionMethod to invoke the action, which can call private, protected, or public methods regardless of visibility.
Raw{"answer": "yes", "explanation": "Symfony's controller resolver uses ReflectionMethod to invoke the action, which can call private, protected, or public methods regardless of visibility."} | неверно верный: «no» | Действие контроллера должно быть public; приватный метод по маршруту не вызывается. |
T13-L8 1.67 c | Symfony | Event subscribers always receive events before listeners, because the interface gives them priority. | «no» Пояснение: Both subscribers and listeners are ordered by their numeric priority value; a listener with a higher priority will be called before a subscriber with a lower priority.
Raw{"answer": "no", "explanation": "Both subscribers and listeners are ordered by their numeric priority value; a listener with a higher priority will be called before a subscriber with a lower priority."} | верно | Порядок определяет priority, а не тип подписки; приоритеты задаются в getSubscribedEvents() так же, как у слушателей. |
T22-L1 1.33 c | Symfony: Security and forms | In modern Symfony (6.0+) authentication is built on authenticator classes (AuthenticatorInterface); the old guard system has been removed. | «yes» Пояснение: Symfony 6.0 removed the old Guard system entirely, and the new authentication system is built around AuthenticatorInterface and its implementations.
Raw{"answer":"yes","explanation":"Symfony 6.0 removed the old Guard system entirely, and the new authentication system is built around AuthenticatorInterface and its implementations."} | верно | Guard объявлен устаревшим в 5.3 и удалён в 6.0; в проекте symfony/security-bundle 8.1. |
T22-L2 2.05 c | Symfony: Security and forms | Which Symfony attribute checks a role/permission right on a controller method (403 without it)? | «isgranted» Пояснение: The #[IsGranted] attribute (Symfony 6.3+) checks a role or permission on a controller method and returns a 403 Forbidden response if the user lacks it.
Raw{"answer": "IsGranted", "explanation": "The #[IsGranted] attribute (Symfony 6.3+) checks a role or permission on a controller method and returns a 403 Forbidden response if the user lacks it."} | верно | #[IsGranted('ROLE_ADMIN')]; атрибут из symfony/security-http. |
T22-L3 1.28 c | Symfony: Security and forms | Voters are Symfony's mechanism for checking access to a specific object: isGranted('EDIT', $post). | «yes» Пояснение: Symfony Voters implement object-level access control, and isGranted('EDIT', $post) is the standard way to check permissions on a specific object using them.
Raw{"answer": "yes", "explanation": "Symfony Voters implement object-level access control, and isGranted('EDIT', $post) is the standard way to check permissions on a specific object using them."} | верно | VoterInterface->vote(); docs Symfony — Voters. |
T22-L4 3.01 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» Пояснение: In Symfony 7+, the doctrine/annotations package is no longer a framework dependency, so PHP 8 attributes (#[Assert\NotBlank]) are the required and supported way to declare validation constraints.
Raw```json ⏎ {"answer": "yes", "explanation": "In Symfony 7+, the doctrine/annotations package is no longer a framework dependency, so PHP 8 attributes (#[Assert\NotBlank]) are the required and supported way to declare validation constraints."} ⏎ ``` | верно | Докблок-аннотации удалены в Symfony 7.0; стандарт — атрибуты. В проекте symfony/validator 8.1. |
T22-L5 0.99 c | Symfony: Security and forms | CSRF protection of Symfony forms is enabled by default: the form validates the token on submission. | «yes» Пояснение: Symfony forms have CSRF protection enabled by default (since Symfony 2.0), automatically adding and validating a CSRF token on submission.
Raw{"answer": "yes", "explanation": "Symfony forms have CSRF protection enabled by default (since Symfony 2.0), automatically adding and validating a CSRF token on submission."} | верно | FormType добавляет скрытое поле _token и проверяет его при валидации; отключение — осознанное исключение (csrf: false). |
T22-L6 1.2 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 on submission; client-side HTML5 checks are merely a UX convenience and can be bypassed.
Raw```json ⏎ {"answer": "yes", "explanation": "Symfony always performs server-side form validation on submission; client-side HTML5 checks are merely a UX convenience and can be bypassed."} ⏎ ``` | верно | Клиентская валидация — только удобство; серверная обязательна и идёт по метаданным объекта формы. |
T22-L7 0.52 c | Symfony: Security and forms | Which Symfony maker command generates a form class (FormType)? | «make:form» Пояснение: The Symfony MakerBundle command 'php bin/console make:form' generates a FormType class.
Raw{"answer": "make:form", "explanation": "The Symfony MakerBundle command 'php bin/console make:form' generates a FormType class."} | верно | bin/console make:form (symfony/maker-bundle — в проекте). |
T22-L8 1.03 c | Symfony: Security and forms | Symfony stores the user's password in the session in plain text. | «no» Пояснение: Symfony stores a serialized token (containing user identifier and roles) in the session, not the plain text password; passwords are hashed and stored in the database.
Raw{"answer": "no", "explanation": "Symfony stores a serialized token (containing user identifier and roles) in the session, not the plain text password; passwords are hashed and stored in the database."} | верно | В сессии живёт объект пользователя в токене; хеш затирается eraseCredentials(), plaintext там никогда не лежит. |
T23-L1 0.98 c | Symfony: configuration and services | Symfony bundle configuration lives in config/packages — one file per bundle or topic. | «yes» Пояснение: In Symfony, bundle configuration files are conventionally placed in config/packages/ with one file per bundle or topic (e.g., doctrine.yaml, security.yaml).
Raw{"answer": "yes", "explanation": "In Symfony, bundle configuration files are conventionally placed in config/packages/ with one file per bundle or topic (e.g., doctrine.yaml, security.yaml)."} | верно | Стандартная структура (config/packages/*.yaml); перегрузка — config/packages/<env>. |
T23-L2 2.72 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 well-known pattern (used by Symfony) where .env holds committed dev defaults and .env.local holds uncommitted real secrets.
Raw{"answer": "yes", "explanation": "This is a well-known pattern (used by Symfony) where .env holds committed dev defaults and .env.local holds uncommitted real secrets."} | верно | symfony/dotenv: .env — общий безопасный набор значений; локальные секреты — .env.local (gitignored) или secrets-хранилище. |
T23-L3 0.89 c | Symfony: configuration and services | Which Symfony command lists the container's registered services and their aliases? | «debug:container» Пояснение: The Symfony command 'debug:container' lists all registered services and their aliases in the service container.
Raw{"answer": "debug:container", "explanation": "The Symfony command 'debug:container' lists all registered services and their aliases in the service container."} | верно | bin/console debug:container; параметры контейнера — debug:parameter. |
T23-L4 3.43 c | Symfony: configuration and services | The Symfony container allows changing parameters at runtime: $container->setParameter() works from a controller. | «yes» Пояснение: Container::setParameter() is a public method that works at runtime, though it's generally discouraged in compiled (production) containers since already-resolved services won't see the updated value.
Raw{"answer": "yes", "explanation": "Container::setParameter() is a public method that works at runtime, though it's generally discouraged in compiled (production) containers since already-resolved services won't see the updated value."} | неверно верный: «no» | Контейнер компилируется и замораживается; 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 3.3, services are private by default; you must explicitly set public: true to fetch them from the container.
Raw{"answer": "no", "explanation": "Since Symfony 3.3, services are private by default; you must explicitly set public: true to fetch them from the container."} | верно | С Symfony 4.0 сервисы по умолчанию private: инжектятся через autowiring; $container->get() — только для публичных. |
T23-L6 1.12 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 have sensible defaults and work without any configuration file in config/packages; only bundles that require specific settings need one.
Raw{"answer": "no", "explanation": "Many Symfony bundles have sensible defaults and work without any configuration file in config/packages; only bundles that require specific settings need one."} | верно | У бандлов есть встроенные умолчания (Extension); конфиг нужен только для отклонений от них. |
T23-L7 0.72 c | Symfony: configuration and services | Environment variable values are injected into services.yaml using the %env(VAR)% syntax. | «yes» Пояснение: In Symfony, environment variables are indeed injected into services.yaml using the %env(VAR)% syntax.
Raw{"answer": "yes", "explanation": "In Symfony, environment variables are indeed injected into services.yaml using the %env(VAR)% syntax."} | верно | %env(...)% резолвится в рантайме env-процессорами; docs — Env Var Processors. |
T23-L8 0.76 c | Symfony: configuration and services | Which Symfony environment variable enables debug mode (affects the profiler and Twig debugging)? | «app_debug» Пояснение: The APP_DEBUG environment variable in Symfony controls debug mode, which enables the profiler and Twig debugging features.
Raw{"answer": "APP_DEBUG", "explanation": "The APP_DEBUG environment variable in Symfony controls debug mode, which enables the profiler and Twig debugging features."} | верно | APP_DEBUG=1 (в .env dev-окружения); окружение выбирает APP_ENV — см. T13-L6. |
T16-L1 1.0 c | Symfony: Messenger | A single message in Symfony Messenger can only have one handler. | «no» Пояснение: Symfony Messenger supports multiple handlers per message; they are executed in order unless propagation is stopped explicitly.
Raw{"answer": "no", "explanation": "Symfony Messenger supports multiple handlers per message; they are executed in order unless propagation is stopped explicitly."} | верно | Messenger вызывает все хендлеры, подписанные на класс сообщения (docs — Multiple Handlers). |
T16-L2 0.94 c | Symfony: Messenger | The sync transport in Messenger queues the message for a worker, just like async. | «no» Пояснение: The sync transport processes the message immediately in the same process without queuing it for a worker; that's what async transports do.
Raw{"answer": "no", "explanation": "The sync transport processes the message immediately in the same process without queuing it for a worker; that's what async transports do."} | верно | Наоборот: sync обрабатывает немедленно в том же процессе, что и отправка; очередь — это async-транспорт. |
T16-L3 0.56 c | Symfony: Messenger | Which console command starts the worker that processes Messenger queue messages? | «messenger:consume» Пояснение: The Symfony console command `messenger:consume` starts the worker that processes messages from Messenger queues.
Raw{"answer": "messenger:consume", "explanation": "The Symfony console command `messenger:consume` starts the worker that processes messages from Messenger queues."} | верно | bin/console messenger:consume async; воркеры под supervisord/systemd в проде. |
T16-L4 0.93 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, max_delay) is configured per transport in the framework configuration.
Raw{"answer": "yes", "explanation": "In Symfony Messenger, the retry_strategy (max_retries, delay, multiplier, max_delay) is configured per transport in the framework configuration."} | верно | retry_strategy на транспорте: max_retries, delay, multiplier; docs — Failed Messages & Retries. |
T16-L5 2.54 c | Symfony: Messenger | By default, Messenger serializes messages to JSON. | «no» Пояснение: By default, Symfony Messenger uses PhpSerializer which relies on PHP's native serialize()/unserialize(), not JSON.
Raw{"answer": "no", "explanation": "By default, Symfony Messenger uses PhpSerializer which relies on PHP's native serialize()/unserialize(), not JSON."} | верно | Дефолтный сериализатор — PhpSerializer (serialize()); JSON-сериализатор включается отдельно. |
T16-L6 1.54 c | Symfony: Messenger | Symfony Scheduler produces messages on a schedule and dispatches them through Messenger. | «yes» Пояснение: Symfony Scheduler is designed to trigger scheduled messages that are dispatched through the Messenger component.
Raw{"answer": "yes", "explanation": "Symfony Scheduler is designed to trigger scheduled messages that are dispatched through the Messenger component."} | верно | Schedule → RecurringMessage → шина Messenger; docs — Scheduler. |
T16-L7 0.82 c | Symfony: Messenger | Which built-in Messenger transport stores messages in database tables via Doctrine? | «doctrine» Пояснение: The Doctrine transport in Symfony Messenger stores messages in database tables managed by Doctrine ORM.
Raw{"answer": "doctrine", "explanation": "The Doctrine transport in Symfony Messenger stores messages in database tables managed by Doctrine ORM."} | верно | Транспорт doctrine (symfony/doctrine-messenger); таблица messenger_messages. В проекте стоит amqp-messenger + doctrine-messenger. |
T16-L8 4.82 c | Symfony: Messenger | The Messenger pipeline can be extended with custom middleware, placed before or after the built-in ones. | «yes» Пояснение: The Messenger pipeline supports custom middleware via the $middleware property on commands, which are processed in the pipeline before built-in middleware like ShouldBeUnique, and the pipeline pattern allows flexible ordering.
Raw```json ⏎ {"answer": "yes", "explanation": "The Messenger pipeline supports custom middleware via the $middleware property on commands, which are processed in the pipeline before built-in middleware like ShouldBeUnique, and the pipeline pattern allows flexible ordering."} ⏎ ``` | верно | messenger.bus.*.middleware в yaml; docs — Middleware. |
T28-L1 1.7 c | Symfony: versions | Symfony major releases come every two years, minor ones every six months (in May and November). | «yes» Пояснение: Symfony follows a release cycle with minor versions every 6 months (May and November) and major versions approximately every 2 years.
Raw```json ⏎ {"answer": "yes", "explanation": "Symfony follows a release cycle with minor versions every 6 months (May and November) and major versions approximately every 2 years."} ⏎ ``` | верно | Стандартный релизный цикл: 8.0 — ноябрь 2025, 8.1 — май 2026, 8.2 — ноябрь 2026. |
T28-L2 1.05 c | Symfony: versions | What is the minimum PHP version required by Symfony 8? | «8.4» Пояснение: Symfony 8 requires a minimum PHP version of 8.4.
Raw{"answer": "8.4", "explanation": "Symfony 8 requires a minimum PHP version of 8.4."} | верно | Symfony 8.0 поднял требование до PHP >= 8.4.1 (в vendor проекта: "php": ">=8.4.1"). |
T28-L3 1.2 c | Symfony: versions | Symfony 7.0 kept support for docblock annotations (validation, routes). | «no» Пояснение: Symfony 7.0 removed support for docblock annotations; only PHP 8 native attributes are supported.
Raw```json ⏎ {"answer": "no", "explanation": "Symfony 7.0 removed support for docblock annotations; only PHP 8 native attributes are supported."} ⏎ ``` | верно | Наоборот: в 7.0 аннотации удалены — только PHP-атрибуты (#[Route], #[Assert\NotBlank]). |
T28-L4 1.05 c | Symfony: versions | AssetMapper manages CSS/JS without node or webpack — via importmap.php. | «yes» Пояснение: Symfony's AssetMapper component manages CSS/JS assets without Node.js or Webpack, using an importmap.php configuration file to define asset imports and dependencies.
Raw```json ⏎ {"answer": "yes", "explanation": "Symfony's AssetMapper component manages CSS/JS assets without Node.js or Webpack, using an importmap.php configuration file to define asset imports and dependencies."} ⏎ ``` | верно | symfony/asset-mapper (с 6.3, стандарт с 7.x); в проекте — importmap.php в корне и asset-mapper 8.1. |
T28-L5 1.04 c | Symfony: versions | Symfony 6.4 is a regular release without long-term support. | «no» Пояснение: Symfony 6.4 is an LTS (Long-Term Support) release, as all even-numbered minor versions in Symfony are LTS.
Raw{"answer": "no", "explanation": "Symfony 6.4 is an LTS (Long-Term Support) release, as all even-numbered minor versions in Symfony are LTS."} | верно | Наоборот: 6.4 — LTS (расширенная поддержка); LTS выходит вместе с очередным мажором (6.4 — вместе с 7.0). |
T28-L6 1.47 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» Пояснение: In Symfony's versioning policy, features deprecated in a major version are removed in the next major version.
Raw```json ⏎ {"answer": "no", "explanation": "In Symfony's versioning policy, features deprecated in a major version are removed in the next major version."} ⏎ ``` | верно | Наоборот: мажорный релиз удаляет всё устаревшее (7.0 убрал деприкейшены 6.x, 8.0 — 7.x). |
T28-L7 1.04 c | Symfony: versions | Every Symfony major release is accompanied by an UPGRADE guide listing the changes. | «yes» Пояснение: Symfony provides UPGRADE-*.md files in its repository for each major release, documenting breaking changes and deprecations.
Raw{"answer": "yes", "explanation": "Symfony provides UPGRADE-*.md files in its repository for each major release, documenting breaking changes and deprecations."} | верно | UPGRADE-7.0.md, UPGRADE-8.0.md в репозитории symfony/symfony. |
T28-L8 1.25 c | Symfony: versions | Which Symfony component manages assets and the importmap without node/webpack? | «assetmapper» Пояснение: Symfony's AssetMapper component (introduced in 6.4/7.0) manages assets and importmaps without requiring Node.js or Webpack.
Raw{"answer": "AssetMapper", "explanation": "Symfony's AssetMapper component (introduced in 6.4/7.0) manages assets and importmaps without requiring Node.js or Webpack."} | верно | symfony/asset-mapper 8.1 — в проекте. |
T29-L1 5.11 c | Symfony: 8.2 and beyond | As of 2026-11-07, Symfony 8.2 has already been released. | «no» Пояснение: Following Symfony's 6-month release cycle, 7.4 (LTS) is expected in May 2026 and 8.0 in November 2026, meaning 8.2 would not be released until approximately November 2027.
Raw{"answer": "no", "explanation": "Following Symfony's 6-month release cycle, 7.4 (LTS) is expected in May 2026 and 8.0 in November 2026, meaning 8.2 would not be released until approximately November 2027."} | верно | Наоборот: 8.2 ещё не выпущена — релиз в конце ноября 2026; последняя стабильная — 8.1. |
T29-L2 1.2 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 release cycle: 8.0 in November 2025, 8.1 in May 2026, and 8.2 in November 2026.
Raw```json ⏎ {"answer": "yes", "explanation": "Symfony follows a six-month release cycle: 8.0 in November 2025, 8.1 in May 2026, and 8.2 in November 2026."} ⏎ ``` | верно | Политика релизов: 8.1 — май 2026, 8.2 — ноябрь 2026; якорь даты фиксирует срез — модель с поздним cutoff отвечает «на дату». |
T29-L3 3.6 c | Symfony: 8.2 and beyond | Which Symfony version comes after 8.1 (as of 2026-11-07)? | «8.2» Пояснение: Symfony minor versions increment sequentially, so the version after 8.1 is 8.2.
Raw```json ⏎ {"answer": 8.2, "explanation": "Symfony minor versions increment sequentially, so the version after 8.1 is 8.2."} ⏎ ``` | верно | 8.2 — следующий минорный релиз (ноябрь 2026); после его выхода проект переходит с 8.1.* на 8.2.*. |
T29-L4 1.87 c | Symfony: 8.2 and beyond | Symfony 8.2 is a major release requiring applications to be rewritten for new APIs. | «no» Пояснение: Symfony 8.2 is a minor release (x.2), which is backward compatible and does not require rewriting; only major releases (x.0) introduce breaking changes.
Raw```json ⏎ {"answer": "no", "explanation": "Symfony 8.2 is a minor release (x.2), which is backward compatible and does not require rewriting; only major releases (x.0) introduce breaking changes."} ⏎ ``` | верно | Наоборот: 8.2 — минорный релиз; новые возможности без поломки обратной совместимости. Мажор — 9.0. |
T29-L5 1.96 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 semantic versioning: minor version updates within the same major branch (e.g., 8.1 → 8.2) are designed to preserve backward compatibility, so code should not require changes.
Raw{"answer": "yes", "explanation": "PHP follows semantic versioning: minor version updates within the same major branch (e.g., 8.1 → 8.2) are designed to preserve backward compatibility, so code should not require changes."} | верно | Политика Symfony: минорные релизы обратно совместимы; BC-break допустим только в мажорных. |
T29-L6 3.54 c | Symfony: 8.2 and beyond | Which minor version of the 8.x branch is released last, before Symfony 9.0? | «8.4» Пояснение: Symfony follows a pattern where each major version has minor releases .0 through .4, with .4 being the LTS, making 8.4 the last minor release before 9.0.
Raw{"answer": "8.4", "explanation": "Symfony follows a pattern where each major version has minor releases .0 through .4, with .4 being the LTS, making 8.4 the last minor release before 9.0."} | верно | По циклу: 8.2 (ноя 2026), 8.3 (май 2027), 8.4 (ноя 2027, вместе с 9.0) — как 6.4 выходила вместе с 7.0. |
T29-L7 3.39 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's minimum PHP requirement is set at the major version level (e.g., Symfony 8.0 would require PHP 8.4); minor releases like 8.2 typically maintain the same minimum PHP version rather than bumping it to a newer one like 8.5.
Raw{"answer": "no", "explanation": "Symfony's minimum PHP requirement is set at the major version level (e.g., Symfony 8.0 would require PHP 8.4); minor releases like 8.2 typically maintain the same minimum PHP version rather than bumping it to a newer one like 8.5."} | верно | Наоборот: минорные релизы не поднимают требования PHP; для всей ветки 8.x остаётся PHP >= 8.4. |
T29-L8 1.14 c | Symfony: 8.2 and beyond | Deprecations added in the 8.x branch will not be removed before Symfony 9.0. | «yes» Пояснение: Symfony's policy guarantees that deprecations introduced in a given major version (8.x) are only removed in the next major version (9.0), ensuring backward compatibility within the major release.
Raw{"answer": "yes", "explanation": "Symfony's policy guarantees that deprecations introduced in a given major version (8.x) are only removed in the next major version (9.0), ensuring backward compatibility within the major release."} | верно | Политика: деприкейшены живут до следующего мажора; 9.0 — ноябрь 2027. |
T21-L1 2.03 c | Twig | Inside {{ }}, Twig allows calling arbitrary PHP code directly. | «no» Пояснение: Twig's {{ }} tag uses its own limited expression language (variables, filters, method calls on objects, arithmetic), not arbitrary PHP code.
Raw{"answer": "no", "explanation": "Twig's {{ }} tag uses its own limited expression language (variables, filters, method calls on objects, arithmetic), not arbitrary PHP code."} | верно | Twig — DSL: только разрешённые окружением функции/фильтры; произвольный PHP не исполняется. |
T21-L2 0.8 c | Twig | By default, Twig auto-escapes printed variables. | «yes» Пояснение: Twig has auto-escaping enabled by default, using the 'html' escaping strategy, which helps prevent XSS attacks.
Raw{"answer": "yes", "explanation": "Twig has auto-escaping enabled by default, using the 'html' escaping strategy, which helps prevent XSS attacks."} | верно | Autoescape включён по умолчанию; {{ '<b>' }} → <b>. Проверено на Twig 3.30. |
T21-L3 0.96 c | Twig | The Twig |e filter escapes a string for safe output in an HTML context. | «yes» Пояснение: The Twig |e (escape) filter defaults to the 'html' strategy, escaping strings for safe output in an HTML context.
Raw{"answer": "yes", "explanation": "The Twig |e (escape) filter defaults to the 'html' strategy, escaping strings for safe output in an HTML context."} | верно | |e ('html') по умолчанию; есть контексты js/url/css. От SQL-инъекций он не защищает — это задача подготовленных запросов Doctrine. |
T21-L4 0.79 c | Twig | Which filter from twig/intl-extra formats a number according to a locale? | «number_format» Пояснение: The number_format filter in twig/intl-extra formats a number according to a specified locale.
Raw{"answer": "number_format", "explanation": "The number_format filter in twig/intl-extra formats a number according to a specified locale."} | неверно верный: «format_number» | |format_number(locale=...) из IntlExtension (twig/intl-extra есть в проекте). Проверено на Twig 3.30: 12345.6 → 12 345,6 (ru). |
T21-L5 0.88 c | Twig | The |raw filter disables auto-escaping for the value. | «yes» Пояснение: The |raw filter marks a value as safe, preventing the template engine from applying auto-escaping to it.
Raw{"answer": "yes", "explanation": "The |raw filter marks a value as safe, preventing the template engine from applying auto-escaping to it."} | верно | {{ x|raw }} выводит HTML как есть; опасно с пользовательскими данными. Проверено на Twig 3.30. |
T21-L6 1.02 c | Twig | In Twig, {{ }} prints an expression value, while {% %} executes tags — conditions, loops, set. | «yes» Пояснение: In Twig, {{ }} is the expression tag for outputting values, while {% %} is the statement tag for control structures like if, for, and set.
Raw{"answer": "yes", "explanation": "In Twig, {{ }} is the expression tag for outputting values, while {% %} is the statement tag for control structures like if, for, and set."} | верно | Два блока синтаксиса Twig: вывод (echo) против логики. |
T21-L7 1.06 c | Twig | In Twig you cannot declare a variable inside a template — values only come from the controller. | «no» Пояснение: In Twig you can declare variables inside a template using the {% set %} tag, so values are not only coming from the controller.
Raw{"answer": "no", "explanation": "In Twig you can declare variables inside a template using the {% set %} tag, so values are not only coming from the controller."} | верно | {% set y = ... %} объявляет переменную в шаблоне. Проверено на Twig 3.30. |
T21-L8 0.83 c | Twig | Which Twig function dumps the debug structure of a variable (array, object)? | «dump» Пояснение: The dump() function in Twig outputs a debug representation of a variable, showing its structure for arrays, objects, etc.
Raw{"answer": "dump", "explanation": "The dump() function in Twig outputs a debug representation of a variable, showing its structure for arrays, objects, etc."} | верно | {{ dump(x) }} (DebugExtension; в Symfony доступна в dev-окружении). |
T24-L1 1.2 c | Bootstrap | Bootstrap is a CSS/JS library of ready-made UI components, not an SPA framework. | «yes» Пояснение: Bootstrap is a CSS/JS library providing ready-made UI components (buttons, modals, grid, etc.), while SPA frameworks are things like React, Angular, or Vue.js.
Raw{"answer": "yes", "explanation": "Bootstrap is a CSS/JS library providing ready-made UI components (buttons, modals, grid, etc.), while SPA frameworks are things like React, Angular, or Vue.js."} | верно | Компоненты и утилиты поверх вашего HTML; SPA-фреймворки (React/Vue) — другой класс инструментов. В проекте vendored 5.3.3. |
T24-L2 1.01 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 max-widths that change at each breakpoint.
Raw{"answer": "container", "explanation": "The .container class in Bootstrap provides a responsive fixed-width container with max-widths that change at each breakpoint."} | верно | .container (фиксированная макс-ширина по брейкпоинтам) vs .container-fluid (на всю ширину). |
T24-L3 1.03 c | Bootstrap | The Bootstrap grid is built on CSS floats and splits a row into 16 columns. | «no» Пояснение: The Bootstrap grid splits a row into 12 columns, not 16, and modern Bootstrap (v4+) uses Flexbox rather than CSS floats.
Raw{"answer": "no", "explanation": "The Bootstrap grid splits a row into 12 columns, not 16, and modern Bootstrap (v4+) uses Flexbox rather than CSS floats."} | верно | Наоборот: flexbox (с Bootstrap 4) и 12 колонок; float-сетка — это Bootstrap 3. |
T24-L4 1.44 c | Bootstrap | Bootstrap's named breakpoints (the infix used in class names) are sm, md, lg, xl, xxl — five of them. | «yes» Пояснение: Bootstrap 5 defines exactly five named breakpoint infixes: sm, md, lg, xl, and xxl.
Raw{"answer": "yes", "explanation": "Bootstrap 5 defines exactly five named breakpoint infixes: sm, md, lg, xl, and xxl."} | верно | Тиров всего шесть: xs (без инфикса) + пять именованных (576/768/992/1200/1400 px). |
T24-L5 3.74 c | Bootstrap | Utilities like .mt-3 or .px-2 use the spacing scale: the number is a multiple of $spacer. | «no» Пояснение: The number in the class name is an index into a predefined spacing scale, not a direct multiple of $spacer (e.g., in Bootstrap 4, .mt-3 equals $spacer * 3/4, not $spacer * 3).
Raw```json ⏎ {"answer": "no", "explanation": "The number in the class name is an index into a predefined spacing scale, not a direct multiple of $spacer (e.g., in Bootstrap 4, .mt-3 equals $spacer * 3/4, not $spacer * 3)."} ⏎ ``` | верно | Spacing utilities; $spacer = 1rem. |
T24-L6 0.87 c | Bootstrap | Which Bootstrap 5 data attribute enables an interactive component (e.g. dropdown) on an element? | «data-bs-toggle» Пояснение: In Bootstrap 5, data-bs-toggle is the attribute used to enable interactive components such as dropdowns, collapses, and tabs.
Raw{"answer": "data-bs-toggle", "explanation": "In Bootstrap 5, data-bs-toggle is the attribute used to enable interactive components such as dropdowns, collapses, and tabs."} | верно | data-bs-toggle="dropdown" и т.п.; в Bootstrap 4 атрибут назывался data-toggle. |
T24-L7 0.67 c | Bootstrap | Bootstrap 5 components work without jQuery — in plain vanilla JS. | «yes» Пояснение: Bootstrap 5 removed its jQuery dependency and all interactive components are built with vanilla JavaScript.
Raw{"answer": "yes", "explanation": "Bootstrap 5 removed its jQuery dependency and all interactive components are built with vanilla JavaScript."} | верно | jQuery удалён в Bootstrap 5.0: data-bs-* атрибуты и JS API. В проекте vendored 5.3.3. |
T24-L8 0.84 c | Bootstrap | Dark mode in Bootstrap is enabled with a .dark class on the root element. | «no» Пояснение: In Bootstrap 5, dark mode is enabled with the data-bs-theme="dark" attribute on the <html> element, not a .dark class.
Raw{"answer": "no", "explanation": "In Bootstrap 5, dark mode is enabled with the data-bs-theme=\"dark\" attribute on the <html> element, not a .dark class."} | верно | Наоборот: тема включается атрибутом data-bs-theme="dark" (Color modes, с 5.3); класса .dark не существует. В проекте 5.3.3. |
T14-L1 1.17 c | Doctrine | Doctrine ORM creates database tables on the fly the first time an entity is used at runtime. | «no» Пояснение: Doctrine ORM does not automatically create tables at runtime; you must explicitly run schema update or migration commands to create/update the database schema.
Raw```json ⏎ {"answer": "no", "explanation": "Doctrine ORM does not automatically create tables at runtime; you must explicitly run schema update or migration commands to create/update the database schema."} ⏎ ``` | верно | Схему создают инструменты (migrations, schema tool); рантайм структуру БД не меняет. |
T14-L2 0.9 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 schedules an INSERT, but no SQL is executed until flush() is called.
Raw{"answer": "persist", "explanation": "EntityManager::persist() marks a new entity as managed and schedules an INSERT, but no SQL is executed until flush() is called."} | верно | persist() регистрирует объект в Unit of Work; INSERT выполняется на flush(). |
T14-L3 1.54 c | Doctrine | In Doctrine ORM 3, the EntityManager::merge() method exists and makes the passed object managed. | «no» Пояснение: EntityManager::merge() was removed in Doctrine ORM 3; it existed in ORM 2 but is no longer part of the interface.
Raw```json ⏎ {"answer": "no", "explanation": "EntityManager::merge() was removed in Doctrine ORM 3; it existed in ORM 2 but is no longer part of the interface."} ⏎ ``` | верно | В ORM 3 merge() удалён (в vendor проекта 3.7.6 метода нет); в Doctrine 2.x merge() возвращал управляемую копию. Версия зафиксирована — ORM 3. |
T14-L4 1.01 c | Doctrine | DQL queries are written in terms of entities and their fields, not tables and columns. | «yes» Пояснение: DQL (Doctrine Query Language) is designed to operate at the entity level, referencing entities and their mapped properties rather than raw database tables and columns.
Raw{"answer": "yes", "explanation": "DQL (Doctrine Query Language) is designed to operate at the entity level, referencing entities and their mapped properties rather than raw database tables and columns."} | верно | Doctrine транслирует DQL в SQL; docs — DQL (Doctrine Query Language). |
T14-L5 0.75 c | Doctrine | What does $repository->find(999) return when no record with id 999 exists? | «null» Пояснение: Doctrine's repository find() method returns null when no entity with the given identifier exists.
Raw{"answer": "null", "explanation": "Doctrine's repository find() method returns null when no entity with the given identifier exists."} | верно | find() возвращает null, если объект не найден (docs Repository methods). |
T14-L6 1.9 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; you must either call flush() explicitly or enable the 'auto_commit' option in the configuration.
Raw{"answer": "no", "explanation": "By default, DoctrineBundle does not automatically call flush() at the end of a request; you must either call flush() explicitly or enable the 'auto_commit' option in the configuration."} | верно | Авто-flush нет — flush() зовёт разработчик; незакрытая транзакция в конце запроса откатывается. |
T14-L7 1.43 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» Пояснение: The Unit of Work performs dirty-checking on managed entities, so flush() automatically detects and commits property changes without needing an explicit persist() call.
Raw{"answer": "yes", "explanation": "The Unit of Work performs dirty-checking on managed entities, so flush() automatically detects and commits property changes without needing an explicit persist() call."} | верно | Dirty checking сравнивает снимки свойств; persist нужен только новым/отсоединённым объектам. |
T14-L8 1.1 c | Doctrine | remove() executes the SQL DELETE immediately, without waiting for flush(). | «no» Пояснение: In Doctrine ORM, remove() only marks the entity for deletion in the UnitOfWork; the actual SQL DELETE is executed when flush() is called.
Raw{"answer": "no", "explanation": "In Doctrine ORM, remove() only marks the entity for deletion in the UnitOfWork; the actual SQL DELETE is executed when flush() is called."} | верно | remove() планирует удаление в Unit of Work; DELETE выполняется на flush() (docs — Deleting Objects). |
T15-L1 0.97 c | PostgreSQL | PostgreSQL uses MVCC, therefore readers block writers and writers block readers. | «no» Пояснение: MVCC is designed so that readers do NOT block writers and writers do NOT block readers; that's the entire purpose of multi-version concurrency control.
Raw{"answer": "no", "explanation": "MVCC is designed so that readers do NOT block writers and writers do NOT block readers; that's the entire purpose of multi-version concurrency control."} | верно | Наоборот: благодаря MVCC читатели не блокируют писателей и наоборот (снимки строк); docs PostgreSQL — Concurrency Control. |
T15-L2 0.95 c | PostgreSQL | Which SQL command shows a query's execution plan without executing the query? | «explain» Пояснение: The EXPLAIN command (or EXPLAIN ANALYZE in some databases) displays the query execution plan without actually running the query.
Raw{"answer": "EXPLAIN", "explanation": "The EXPLAIN command (or EXPLAIN ANALYZE in some databases) displays the query execution plan without actually running the query."} | верно | EXPLAIN без ANALYZE только строит план; проверено на PostgreSQL 17.7. |
T15-L3 2.12 c | PostgreSQL | SERIAL and GENERATED ... AS IDENTITY are just two names for the same mechanism. | «no» Пояснение: SERIAL is PostgreSQL-specific syntactic sugar that creates a separate sequence object, while GENERATED AS IDENTITY is a SQL-standard mechanism where the column itself is an identity column with different semantics (e.g., ALTER COLUMN vs ALTER SEQUENCE, GENERATED BY DEFAULT vs ALWAYS).
Raw{"answer": "no", "explanation": "SERIAL is PostgreSQL-specific syntactic sugar that creates a separate sequence object, while GENERATED AS IDENTITY is a SQL-standard mechanism where the column itself is an identity column with different semantics (e.g., ALTER COLUMN vs ALTER SEQUENCE, GENERATED BY DEFAULT vs ALWAYS)."} | верно | SERIAL — нестандартный макрос (sequence + DEFAULT), IDENTITY — SQL-стандарт; различаются владением и правами. Оба есть в PG 17 (проверено). |
T15-L4 1.49 c | PostgreSQL | By default, a PostgreSQL UNIQUE constraint allows only one row with NULL in the column. | «no» Пояснение: By default, PostgreSQL treats NULLs as distinct from each other, so a UNIQUE constraint allows multiple rows with NULL values in the column.
Raw{"answer": "no", "explanation": "By default, PostgreSQL treats NULLs as distinct from each other, so a UNIQUE constraint allows multiple rows with NULL values in the column."} | верно | Наоборот: NULLS DISTINCT по умолчанию — несколько NULL допустимы; NULLS NOT DISTINCT — опция с PG 15. Проверено на PG 17.7. |
T15-L5 0.57 c | PostgreSQL | Which PostgreSQL aggregate function concatenates strings with a separator? | «string_agg» Пояснение: string_agg(column, delimiter) is the PostgreSQL aggregate function that concatenates strings with a specified separator.
Raw{"answer": "string_agg", "explanation": "string_agg(column, delimiter) is the PostgreSQL aggregate function that concatenates strings with a specified separator."} | верно | string_agg(значение, разделитель); проверено на PostgreSQL 17.7. |
T15-L6 0.96 c | PostgreSQL | Plain VACUUM returns the space occupied by dead tuples to the operating system. | «no» Пояснение: Plain VACUUM only marks space as reusable within the table; VACUUM FULL is what returns the space to the operating system.
Raw{"answer": "no", "explanation": "Plain VACUUM only marks space as reusable within the table; VACUUM FULL is what returns the space to the operating system."} | верно | VACUUM помечает место для переиспользования внутри таблицы; ОС его возвращает только VACUUM FULL (с эксклюзивной блокировкой). |
T15-L7 0.73 c | PostgreSQL | Which keyword in a window function definition partitions rows into groups the function is computed over? | «partition by» Пояснение: The PARTITION BY clause in a window function definition divides rows into groups over which the function is computed, similar to GROUP BY but without collapsing rows.
Raw{"answer": "PARTITION BY", "explanation": "The PARTITION BY clause in a window function definition divides rows into groups over which the function is computed, similar to GROUP BY but without collapsing rows."} | верно | OVER (PARTITION BY ...); проверено на PostgreSQL 17.7. |
T15-L8 1.13 c | PostgreSQL | The READ COMMITTED isolation level protects against non-repeatable reads. | «no» Пояснение: READ COMMITTED only protects against dirty reads; non-repeatable reads are prevented by REPEATABLE READ and above.
Raw{"answer": "no", "explanation": "READ COMMITTED only protects against dirty reads; non-repeatable reads are prevented by REPEATABLE READ and above."} | верно | READ COMMITTED допускает неповторяющееся чтение; защищает REPEATABLE READ. Проверено: SHOW transaction_isolation → read committed. |
T17-L1 0.84 c | PostgreSQL: transactions and indexes | By default, PostgreSQL wraps each single SQL statement in its own implicit transaction (autocommit). | «yes» Пояснение: By default, PostgreSQL runs in autocommit mode, where each individual SQL statement is automatically committed as its own transaction unless explicitly wrapped in BEGIN/COMMIT.
Raw{"answer": "yes", "explanation": "By default, PostgreSQL runs in autocommit mode, where each individual SQL statement is automatically committed as its own transaction unless explicitly wrapped in BEGIN/COMMIT."} | верно | Без BEGIN каждый оператор коммитится сам; docs PostgreSQL — Transactions. Проверено на PG 17. |
T17-L2 0.43 c | PostgreSQL: transactions and indexes | Which SQL command ends a transaction, committing all its changes? | «commit» Пояснение: COMMIT is the SQL command that ends a transaction and permanently saves all changes made within it.
Raw{"answer": "COMMIT", "explanation": "COMMIT is the SQL command that ends a transaction and permanently saves all changes made within it."} | верно | COMMIT (END — синоним). Проверено на PG 17. |
T17-L3 0.9 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 are used by the query optimizer to locate rows efficiently for SELECT, UPDATE, and DELETE operations that filter on indexed columns.
Raw{"answer": "yes", "explanation": "Indexes are used by the query optimizer to locate rows efficiently for SELECT, UPDATE, and DELETE operations that filter on indexed columns."} | верно | Поиск строк для изменения идёт по индексу; docs PostgreSQL — Indexes. |
T17-L4 0.83 c | PostgreSQL: transactions and indexes | To roll back part of the statements inside a transaction, PostgreSQL uses SAVEPOINT. | «yes» Пояснение: SAVEPOINT allows you to set a named point within a transaction that you can roll back to, undoing only the statements executed after that point without aborting the entire transaction.
Raw{"answer": "yes", "explanation": "SAVEPOINT allows you to set a named point within a transaction that you can roll back to, undoing only the statements executed after that point without aborting the entire transaction."} | верно | SAVEPOINT name; ROLLBACK TO name — частичный откат без отмены всей транзакции. Проверено на PG 17. |
T17-L5 0.87 c | PostgreSQL: transactions and indexes | EXPLAIN ANALYZE shows the query plan without executing the query. | «no» Пояснение: EXPLAIN ANALYZE actually executes the query to gather real performance data, while plain EXPLAIN shows the plan without execution.
Raw{"answer": "no", "explanation": "EXPLAIN ANALYZE actually executes the query to gather real performance data, while plain EXPLAIN shows the plan without execution."} | верно | Наоборот: ANALYZE реально выполняет запрос (с побочными эффектами!) и показывает фактические времена узлов; план без выполнения — plain EXPLAIN. |
T17-L6 0.64 c | PostgreSQL: transactions and indexes | Which PostgreSQL extension adds vector types and indexes for embedding search? | «pgvector» Пояснение: pgvector is a PostgreSQL extension that adds a vector data type and support for vector similarity search indexes.
Raw{"answer": "pgvector", "explanation": "pgvector is a PostgreSQL extension that adds a vector data type and support for vector similarity search indexes."} | верно | CREATE EXTENSION vector (проект pgvector; в проекте образ pgvector/pgvector:pg17). |
T17-L7 1.01 c | PostgreSQL: transactions and indexes | A partial index (CREATE INDEX ... WHERE ...) is built only over rows satisfying the condition. | «yes» Пояснение: A partial index in PostgreSQL includes only rows that satisfy the WHERE condition, reducing index size and improving query performance for matching queries.
Raw{"answer": "yes", "explanation": "A partial index in PostgreSQL includes only rows that satisfy the WHERE condition, reducing index size and improving query performance for matching queries."} | верно | docs PostgreSQL — Partial Indexes; типичный кейс — индекс по «активным» записям. |
T17-L8 1.71 c | PostgreSQL: transactions and indexes | The SERIALIZABLE level in PostgreSQL is implemented by locking the rows a transaction reads. | «no» Пояснение: PostgreSQL implements SERIALIZABLE using Serializable Snapshot Isolation (SSI) with predicate locking and MVCC, not by locking the rows a transaction reads.
Raw{"answer": "no", "explanation": "PostgreSQL implements SERIALIZABLE using Serializable Snapshot Isolation (SSI) with predicate locking and MVCC, not by locking the rows a transaction reads."} | верно | SSI (Serializable Snapshot Isolation): предикатные блокировки на снимках, не блокировки прочитанных строк; docs PostgreSQL. |
T19-L1 0.85 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 was successful and a new resource has been created as a result.
Raw{"answer": "yes", "explanation": "HTTP 201 'Created' indicates that the request was successful and a new resource has been created as a result."} | верно | 201 Created; обычно на POST, часто с Location; RFC 9110. |
T19-L2 0.88 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 with an empty response body, commonly used after DELETE operations.
Raw{"answer": 204, "explanation": "HTTP 204 No Content indicates a successful request with an empty response body, commonly used after DELETE operations."} | верно | 204 No Content; RFC 9110. |
T19-L3 5.03 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. | «no» Пояснение: Per RFC 9110 (Section 9.2.1), the idempotent methods are GET, HEAD, OPTIONS, PUT, and TRACE; DELETE is explicitly not included, because a second DELETE on an already-deleted resource returns 404, a different response than the first.
Raw{"answer": "no", "explanation": "Per RFC 9110 (Section 9.2.1), the idempotent methods are GET, HEAD, OPTIONS, PUT, and TRACE; DELETE is explicitly not included, because a second DELETE on an already-deleted resource returns 404, a different response than the first."} | неверно верный: «yes» | RFC 9110: DELETE идемпотентен (как PUT); идемпотентность ≠ безопасность — ресурс удаляется при первом вызове. |
T19-L4 1.09 c | HTTP and REST API | The Access-Control-Allow-Origin header is sent by the client so that the server agrees to accept requests from another origin. | «no» Пояснение: Access-Control-Allow-Origin is sent by the server (as a response header), not by the client.
Raw{"answer": "no", "explanation": "Access-Control-Allow-Origin is sent by the server (as a response header), not by the client."} | верно | Наоборот: заголовок шлёт СЕРВЕР в ответе, разрешая браузеру cross-origin запрос (CORS); в проекте nelmio/cors-bundle. |
T19-L5 0.95 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 specifically defined for rate limiting scenarios when a client exceeds the allowed request rate.
Raw{"answer": "yes", "explanation": "HTTP 429 'Too Many Requests' is specifically defined for rate limiting scenarios when a client exceeds the allowed request rate."} | верно | 429 (+ Retry-After); RFC 6585. В проекте symfony/rate-limiter. |
T19-L6 0.78 c | HTTP and REST API | 5xx codes mean a client error, while 4xx means a server-side error. | «no» Пояснение: It's the opposite: 4xx codes indicate client errors and 5xx codes indicate server-side errors.
Raw{"answer": "no", "explanation": "It's the opposite: 4xx codes indicate client errors and 5xx codes indicate server-side errors."} | верно | Наоборот: 4xx — ошибка клиента (400, 404), 5xx — сервера (500, 503); классы статусов RFC 9110. |
T19-L7 0.38 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.69 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 by default, while PUT (per RFC 7231) is required to be idempotent.
Raw{"answer": "yes", "explanation": "RFC 5789 explicitly states that PATCH is not idempotent by default, while PUT (per RFC 7231) is required to be idempotent."} | верно | RFC 5789 прямо оговаривает: PATCH не гарантированно идемпотентен; PUT идемпотентен. |
T20-L1 1.4 c | Security and OAuth | Checking a password by comparing its hash to the stored hash with a plain == is sufficient. | «no» Пояснение: Using == is vulnerable to type juggling (e.g., '0e...' strings) and timing attacks; hash_equals() should be used instead.
Raw{"answer": "no", "explanation": "Using == is vulnerable to type juggling (e.g., '0e...' strings) and timing attacks; hash_equals() should be used instead."} | верно | Нужна постоянновременная проверка (password_verify) — timing-атаки; соль и алгоритм уже внутри хеша. |
T20-L2 1.26 c | Security and OAuth | A CSRF token is issued by the server (bound to the session) and verified server-side on unsafe requests (POST etc.). | «yes» Пояснение: CSRF tokens are generated by the server, tied to the session, and validated server-side on state-changing (unsafe) requests like POST, PUT, DELETE.
Raw{"answer": "yes", "explanation": "CSRF tokens are generated by the server, tied to the session, and validated server-side on state-changing (unsafe) requests like POST, PUT, DELETE."} | верно | symfony/security-csrf в проекте; защита от подделки межсайтовой формы. |
T20-L3 0.63 c | Security and OAuth | Which HTTP header enables the CSP (Content Security Policy) policy? | «content-security-policy» Пояснение: The Content-Security-Policy HTTP header is used to define allowed sources of content and help mitigate XSS attacks.
Raw{"answer": "Content-Security-Policy", "explanation": "The Content-Security-Policy HTTP header is used to define allowed sources of content and help mitigate XSS attacks."} | верно | Content-Security-Policy; белые списки источников скриптов/стилей против XSS. |
T20-L4 0.97 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; the access token grants access to resources, while identifying the user (authentication) is handled by OpenID Connect's ID token.
Raw{"answer": "no", "explanation": "OAuth 2.0 is an authorization protocol; the access token grants access to resources, while identifying the user (authentication) is handled by OpenID Connect's ID token."} | верно | OAuth 2.0 — авторизация/делегирование доступа; аутентификацию добавляет OpenID Connect. В проекте knpuniversity/oauth2-client-bundle (yandex/github/google). |
T20-L5 1.86 c | Security and OAuth | XSS is prevented by validating input on the server before writing it to the database. | «no» Пояснение: XSS is prevented by encoding/escaping output at the point of rendering, not by input validation before writing to the database.
Raw{"answer": "no", "explanation": "XSS is prevented by encoding/escaping output at the point of rendering, not by input validation before writing to the database."} | верно | XSS лечится контекстным экранированием НА ВЫВОДЕ (Twig autoescape, CSP); валидация ввода не покрывает все контексты вывода. |
T20-L6 0.87 c | Security and OAuth | In the OAuth 2.0 authorization code flow, which parameter arrives at the redirect_uri and is exchanged for an access token? | «code» Пояснение: In the OAuth 2.0 authorization code flow, the authorization code (parameter 'code') is returned to the redirect_uri and then exchanged at the token endpoint for an access token.
Raw{"answer": "code", "explanation": "In the OAuth 2.0 authorization code flow, the authorization code (parameter 'code') is returned to the redirect_uri and then exchanged at the token endpoint for an access token."} | верно | Параметр code; обмен на токен POST-ом на /token с client_secret. |
T20-L7 1.01 c | Security and OAuth | A refresh token lives longer than an access token and allows obtaining a new access token without the user logging in again. | «yes» Пояснение: Refresh tokens are designed to have a longer lifetime than access tokens and allow clients to obtain new access tokens without requiring the user to authenticate again.
Raw{"answer": "yes", "explanation": "Refresh tokens are designed to have a longer lifetime than access tokens and allow clients to obtain new access tokens without requiring the user to authenticate again."} | верно | Стандартная схема OAuth/OIDC: короткий access + длинный refresh. |
T20-L8 2.05 c | Security and OAuth | A password salt must be kept secret: without it the hash cannot be verified. | «no» Пояснение: The salt does not need to be kept secret; it is typically stored alongside the hash so that verification can be performed.
Raw{"answer": "no", "explanation": "The salt does not need to be kept secret; it is typically stored alongside the hash so that verification can be performed."} | верно | Соль хранится открыто (password_hash включает её в строку хеша); секретность соли не нужна. |
T18-L1 2.03 c | Testing: PHPUnit | PHPUnit runs test methods of any class — extending TestCase is not required. | «no» Пояснение: In PHPUnit, test classes must extend PHPUnit\Framework\TestCase to be recognized and executed as test suites.
Raw{"answer": "no", "explanation": "In PHPUnit, test classes must extend PHPUnit\\Framework\\TestCase to be recognized and executed as test suites."} | верно | Тестом считается метод класса, наследующего TestCase (PHPUnit 10). |
T18-L2 0.78 c | Testing: PHPUnit | In PHPUnit, setUp() runs once before all tests of the class. | «no» Пояснение: setUp() runs before each test method; setUpBeforeClass() is the static method that runs once before all tests in the class.
Raw{"answer": "no", "explanation": "setUp() runs before each test method; setUpBeforeClass() is the static method that runs once before all tests in the class."} | верно | setUp() — перед КАЖДЫМ тестом; один раз на класс — setUpBeforeClass(). Проверено живым счётчиком на PHPUnit 10.5. |
T18-L3 1.18 c | Testing: PHPUnit | A data provider lets a test run with exactly one set of arguments. | «no» Пояснение: A data provider is specifically designed to supply multiple sets of arguments so the test can run multiple times with different inputs.
Raw{"answer": "no", "explanation": "A data provider is specifically designed to supply multiple sets of arguments so the test can run multiple times with different inputs."} | верно | Наоборот: наборов может быть сколько угодно — тест выполняется по разу на каждый. Проверено на PHPUnit 10.5 (#[DataProvider]). |
T18-L4 0.86 c | Testing: PHPUnit | Which PHPUnit method declares an expectation that an exception of a given class is thrown? | «expectexception» Пояснение: PHPUnit's expectException() method is used to declare that a specific exception class is expected to be thrown during a test.
Raw{"answer": "expectException", "explanation": "PHPUnit's expectException() method is used to declare that a specific exception class is expected to be thrown during a test."} | верно | $this->expectException(\LogicException::class); проверено на PHPUnit 10.5. |
T18-L5 1.19 c | Testing: PHPUnit | In PHPUnit, a stub verifies which methods were called on it, while a mock only returns data. | «no» Пояснение: It's the opposite: a stub only returns pre-defined data, while a mock verifies which methods were called (and can also return data).
Raw{"answer": "no", "explanation": "It's the opposite: a stub only returns pre-defined data, while a mock verifies which methods were called (and can also return data)."} | верно | Наоборот: стаб подставляет данные, мок проверяет взаимодействия (createStub/createMock); docs PHPUnit — Test Doubles. |
T18-L6 0.96 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+, PHP 8 attributes like #[DataProvider] are the recommended replacement for the @dataProvider doc-comment annotation.
Raw{"answer": "yes", "explanation": "In PHPUnit 10+, PHP 8 attributes like #[DataProvider] are the recommended replacement for the @dataProvider doc-comment annotation."} | верно | Аннотация ещё парсится в PHPUnit 10/11 (AnnotationParser в 10.5.66), удаление — в 12; атрибут — стандарт. |
T18-L7 0.94 c | Testing: PHPUnit | PHPUnit does not allow one test to depend on the result of another. | «no» Пояснение: PHPUnit allows test dependencies via the depends() method, which can skip a test if the test it depends on fails.
Raw{"answer": "no", "explanation": "PHPUnit allows test dependencies via the depends() method, which can skip a test if the test it depends on fails."} | верно | Зависимости есть: #[Depends] — зависимый тест не запустится, еслиProducer упал. |
T18-L8 1.5 c | Testing: PHPUnit | Which PHPUnit command-line option makes tests run in random order? | «--random-order» Пояснение: The --random-order PHPUnit flag shuffles the test execution order randomly.
Raw{"answer": "--random-order", "explanation": "The --random-order PHPUnit flag shuffles the test execution order randomly."} | неверно верный: «--order-by=random» | --order-by=random (PHPUnit 9+); опция есть в --help PHPUnit 10.5 (проектная). |
T01-L9 3.76 c | Syntax and operators | What does this code output?
```php
echo intdiv(7, 2) . intdiv(-7, 2);
``` | «3-3» Пояснение: intdiv(7,2) returns 3 and intdiv(-7,2) returns -3, concatenated as the string '3-3'.
Raw```json ⏎ {"answer": "3-3", "explanation": "intdiv(7,2) returns 3 and intdiv(-7,2) returns -3, concatenated as the string '3-3'."} ⏎ ``` | верно | intdiv truncates toward zero: intdiv(-7, 2) = -3, not -4. |
T01-L10 1.01 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 1.4 c | Types and comparisons | What does this code output?
```php
echo '1e1' == '10' ? 'true' : 'false';
``` | «true» Пояснение: '1e1' is a numeric string (scientific notation for 10), so both strings are compared as numbers, and 10 == 10 is true.
Raw{"answer": "true", "explanation": "'1e1' is a numeric string (scientific notation for 10), so both strings are compared as numbers, and 10 == 10 is true."} | верно | Both strings are numeric — compared as numbers: 10 == 10. |
T02-L10 3.94 c | Types and comparisons | What does this code output?
```php
switch ('a') {
case 0: echo 'zero'; break;
default: echo 'other';
}
``` | «zero» Пояснение: In PHP 8.0+, comparing a non-numeric string with an integer using == casts the string to an int, so 'a' becomes 0, which matches case 0.
Raw{"answer": "zero", "explanation": "In PHP 8.0+, comparing a non-numeric string with an integer using == casts the string to an int, so 'a' becomes 0, which matches case 0."} | неверно верный: «other» | PHP 8: 'a' == 0 → false (used to be true) — default fires. |
T03-L9 1.51 c | Strings | What does this code output?
```php
echo strtr('abc', ['a' => '1', 'ab' => '2']);
``` | «2c» Пояснение: strtr with an array replaces longer keys first, so 'ab' is replaced with '2' before 'a' with '1', turning 'abc' into '2c'.
Raw```json ⏎ {"answer": "2c", "explanation": "strtr with an array replaces longer keys first, so 'ab' is replaced with '2' before 'a' with '1', turning 'abc' into '2c'."} ⏎ ``` | верно | strtr with an array prefers the longest matching key. |
T03-L10 1.16 c | Strings | What does this code output?
```php
echo '[' . substr('hello', -10) . ']';
``` | «[]» Пояснение: substr('hello', -10) returns an empty string because the start offset -10 is beyond the length of the 5-character string, so the result is brackets with nothing inside.
Raw{"answer":"[]","explanation":"substr('hello', -10) returns an empty string because the start offset -10 is beyond the length of the 5-character string, so the result is brackets with nothing inside."} | неверно верный: «[hello]» | A negative start beyond the string is clamped to the beginning. |
T04-L9 1.9 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 keys from $a (k, n) and adds keys from $b that don't exist in $a (m), so array_keys returns ['k','n','m'].
Raw{"answer": "k,n,m", "explanation": "The array union operator + keeps keys from $a (k, n) and adds keys from $b that don't exist in $a (m), so array_keys returns ['k','n','m']."} | верно | The + operator: on duplicate string keys the left array wins. |
T04-L10 2.5 c | Arrays | What does this code output?
```php
$a = [[1, 'x', 2], [2, 'y', 1], [3, 'z', 2]];
usort($a, fn($p, $q) => $p[2] <=> $q[2]);
echo implode('', array_column($a, 1));
``` | «yxz» Пояснение: usort sorts by the third element (index 2), yielding order [1],[2],[2] → ['y','x','z'], which implode produces 'yxz'.
Raw{"answer": "yxz", "explanation": "usort sorts by the third element (index 2), yielding order [1],[2],[2] → ['y','x','z'], which implode produces 'yxz'."} | верно | Sorts are stable since 8.0: x and z keep their order on a tie. |
T05-L10 4.32 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 a string-keyed array maps values by key name to parameter names, so $a=5 and $b=1, giving 5-1=4.
Raw```json ⏎ {"answer": 4, "explanation": "The spread operator with a string-keyed array maps values by key name to parameter names, so $a=5 and $b=1, giving 5-1=4."} ⏎ ``` | верно | String keys of a spread array become named arguments. |
T05-L9 1.87 c | Functions and closures | What does this code output?
```php
class P
{
private int $v = 3;
public function g(): int { return $this->v; }
}
$p = new P;
$f = $p->g(...);
$p = null;
echo $f();
``` | «3» Пояснение: The first-class callable syntax $p->g(...) creates a closure bound to the object at the time of creation, so even after $p = null, the closure still holds a reference to the original object and returns its private property $v = 3.
Raw{"answer": 3, "explanation": "The first-class callable syntax $p->g(...) creates a closure bound to the object at the time of creation, so even after $p = null, the closure still holds a reference to the original object and returns its private property $v = 3."} | верно | First-class callable syntax binds $this at creation time. |
T06-L9 0.94 c | OOP: classes and inheritance | What does this code output?
```php
class A
{
public function who(): string { return static::class; }
}
class B extends A {}
echo (new B)->who();
``` | «b» Пояснение: static::class uses late static binding, so it returns the called class name (B) rather than the defining class (A).
Raw{"answer": "B", "explanation": "static::class uses late static binding, so it returns the called class name (B) rather than the defining class (A)."} | верно | Late static binding: static::class is the receiver's class. |
T06-L10 1.41 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 custom setter multiplies the assigned value by 2, so assigning 5 results in the property storing 10.
Raw{"answer": 10, "explanation": "The custom setter multiplies the assigned value by 2, so assigning 5 results in the property storing 10."} | верно | Inside the set hook, $this->x writes the backing store (no recursion): 5*2. |
T07-L9 1.45 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 means f() resolves to TB's version returning 'B', and TA::f as g aliases TA's f() as g() returning 'A', so the concatenation is 'BA'.
Raw{"answer": "BA", "explanation": "TB::f insteadof TA means f() resolves to TB's version returning 'B', and TA::f as g aliases TA's f() as g() returning 'A', so the concatenation is 'BA'."} | верно | insteadof picks the implementation; as keeps the other under an alias. |
T07-L10 1.19 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 the trait's static properties, so CX::$n and CY::$n are separate and CY::$n remains 0.
Raw```json ⏎ {"answer": 0, "explanation": "Each class that uses a trait gets its own independent copy of the trait's static properties, so CX::$n and CY::$n are separate and CY::$n remains 0."} ⏎ ``` | верно | A trait's static property is copied into each consuming class. |
T08-L10 1.37 c | Exceptions and errors | What does this code output?
```php
function f(): int
{
try { return 1; } finally { return 2; }
}
echo f();
``` | «2» Пояснение: A return statement in a finally block overrides the return value from the try block, so the function returns 2.
Raw```json ⏎ {"answer": 2, "explanation": "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.59 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» Пояснение: When a new exception is thrown in a finally block, it replaces the original propagating exception, so the LogicException('second') is caught by the outer catch.
Raw{"answer": "second", "explanation": "When a new exception is thrown in a finally block, it replaces the original propagating exception, so the LogicException('second') is caught by the outer catch."} | верно | An exception from finally replaces the in-flight one — the last thrown is caught. |
T09-L9 1.54 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 App\Foo via the use alias, while \Baz::class refers to the global class Baz.
Raw{"answer": "App\\Foo|Baz", "explanation": "Baz::class resolves to App\\Foo via the use alias, 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 2.4 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 for global Foo (not found, returns 'no'), while class_exists('Ns\Foo') finds the class defined in namespace Ns (returns 'yes').
Raw{"answer": "noyes", "explanation": "class_exists('Foo') looks for global Foo (not found, returns 'no'), while class_exists('Ns\\Foo') finds the class defined in namespace Ns (returns 'yes')."} | верно | Dynamic names are not resolved against the namespace — 'Foo' is the global class. |
T10-L9 1.27 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 a foreach by reference, $v remains a reference to the last element of the array, so assigning 99 to $v changes the last element from 3 to 99.
Raw{"answer":"1,2,99","explanation":"After a foreach by reference, $v remains a reference to the last element of the array, so assigning 99 to $v changes the last element from 3 to 99."} | верно | After a by-ref foreach, $v remains a reference to the last element. |
T10-L10 1.67 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» Пояснение: Static variables in PHP methods are shared between parent and child classes, so all calls to inc() increment the same variable: 0→1, 1→2, 2→3.
Raw{"answer": 3, "explanation": "Static variables in PHP methods are shared between parent and child classes, so all calls to inc() increment the same variable: 0→1, 1→2, 2→3."} | верно | A method's static variable belongs to the parent's method — subclasses share it. |
T11-L9 5.38 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();
``` | «—» Пояснение: After send(10), the generator is suspended at 'yield 1' (not complete), so getReturn() returns null, and echoing null produces an empty string.
Raw```json ⏎ {"answer": "", "explanation": "After send(10), the generator is suspended at 'yield 1' (not complete), so getReturn() returns null, and echoing null produces an empty string."} ⏎ ``` | неверно верный: «11» | send() resumes the generator: $x = 10, return 10+1. |
T11-L10 1.81 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() which yields 1 and 2, then its return value 'ok' is assigned to $r and yielded by outer(), so the full sequence is 1, 2, ok.
Raw```json ⏎ {"answer": "1,2,ok", "explanation": "yield from delegates to inner() which yields 1 and 2, then its return value 'ok' is assigned to $r and yielded by outer(), so the full sequence is 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.43 c | Configuration and security | What does this code output?
```php
$hash = password_hash('x', PASSWORD_BCRYPT, ['cost' => 4]);
echo password_needs_rehash($hash, PASSWORD_BCRYPT, ['cost' => 4]) ? 'yes' : 'no';
echo password_needs_rehash($hash, PASSWORD_BCRYPT, ['cost' => 5]) ? 'yes' : 'no';
``` | «noyes» Пояснение: The hash was created with cost 4, so it doesn't need rehashing at cost 4 (no) but does need rehashing at cost 5 (yes).
Raw```json ⏎ {"answer": "noyes", "explanation": "The hash was created with cost 4, so it doesn't need rehashing at cost 4 (no) but does need rehashing at cost 5 (yes)."} ⏎ ``` | верно | password_needs_rehash compares the hash's options with the target: cost 4 = 4 → 'no', cost 5 ≠ 4 → 'yes'. |
T12-L10 2.56 c | Configuration and security | What does this code output on PHP 8.5?
```php
echo (E_ALL & 2048) === 0 ? 'strict-out' : 'strict-in';
``` | «strict-out» Пояснение: In PHP 8.4+, E_STRICT (2048) was removed from E_ALL, so the bitwise AND yields 0, making the condition true.
Raw```json ⏎ {"answer": "strict-out", "explanation": "In PHP 8.4+, E_STRICT (2048) was removed from E_ALL, so the bitwise AND yields 0, making the condition true."} ⏎ ``` | верно | 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.63 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 maps the HTTP_X_TOKEN server variable to the X-Token header, so get('X-Token') returns 'abc'.
Raw{"answer":"mapped","explanation":"Symfony's Request maps the HTTP_X_TOKEN server variable to the X-Token header, so get('X-Token') returns 'abc'."} | верно | The literal comparison requires knowing the mapping: HttpFoundation turns HTTP_X_TOKEN into the X-Token header (case-insensitive); without it the answer is 'missing'. |
T13-L10 1.28 c | Symfony | What does this code output?
```php
use Symfony\Component\EventDispatcher\EventDispatcher;
use Symfony\Contracts\EventDispatcher\Event;
$d = new EventDispatcher();
$out = '';
$d->addListener('e', function () use (&$out) { $out .= 'B'; }, 10);
$d->addListener('e', function () use (&$out) { $out .= 'A'; });
$d->addListener('e', function () use (&$out) { $out .= 'C'; }, 5);
$d->dispatch(new Event(), 'e');
echo $out;
``` | «bca» Пояснение: Symfony's EventDispatcher calls listeners in descending priority order: B (10), C (5), A (0 default).
Raw```json ⏎ {"answer": "BCA", "explanation": "Symfony's EventDispatcher calls listeners in descending priority order: B (10), C (5), A (0 default)."} ⏎ ``` | верно | Listeners run by descending priority: 10 (B), 5 (C), 0 (A). |
T14-L10 2.76 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 (first-level cache) ensures that find() returns the already-managed entity instance for a given ID, so both $a and $b are the same object (in fact, the same as $u).
Raw{"answer": "same", "explanation": "Doctrine's Identity Map (first-level cache) ensures that find() returns the already-managed entity instance for a given ID, so both $a and $b are the same object (in fact, the same as $u)."} | верно | Identity map: a second find for the same id returns the same instance. |
T14-L9 5.62 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 an entity before flush moves it from the insertions set to the deletions set in the UnitOfWork, so during flush only a DELETE is issued (affecting 0 rows since the INSERT never happened).
Raw```json ⏎ {"answer": 0, "explanation": "Persisting then removing an entity before flush moves it from the insertions set to the deletions set in the UnitOfWork, so during flush only a DELETE is issued (affecting 0 rows since the INSERT never happened)."} ⏎ ``` | верно | The unit of work schedules INSERT at flush: remove after persist cancels it. |
T15-L10 1.05 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; there is one non-NULL value (1) and one NULL, so the result is 1.
Raw{"answer": 1, "explanation": "COUNT(x) counts only non-NULL values in column x; there is one non-NULL value (1) and one NULL, so the result is 1."} | верно | count(column) skips NULLs; count(*) would return 2. |
T15-L9 1.64 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), then string_agg concatenates them as text with commas in id order.
Raw{"answer": "10,30,60", "explanation": "The window function computes running sums (10, 30, 60), then string_agg concatenates them as text with commas in id order."} | верно | With ORDER BY the default window frame is running (start to current row). |
T16-L9 4.5 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» Пояснение: Middleware executes in order: Trace('M1') echoes 'M1' then delegates to the next, Trace('M2') echoes 'M2' then delegates to the final handler.
Raw{"answer": "M1M2", "explanation": "Middleware executes in order: Trace('M1') echoes 'M1' then delegates to the next, Trace('M2') echoes 'M2' then delegates to the final handler."} | верно | The first-added middleware runs first (outermost). |
T16-L10 2.12 c | Symfony: Messenger | What does this code output?
```php
use Symfony\Component\Messenger\MessageBus;
use Symfony\Component\Messenger\Middleware\HandleMessageMiddleware;
use Symfony\Component\Messenger\Handler\HandlersLocator;
use Symfony\Component\Messenger\Handler\HandlerDescriptor;
use Symfony\Component\Messenger\Envelope;
class Ping {}
$n = 0;
$d1 = new HandlerDescriptor(function (Ping $m) use (&$n) { $n += 1; }, ['alias' => 'h1']);
$d2 = new HandlerDescriptor(function (Ping $m) use (&$n) { $n += 10; }, ['alias' => 'h2']);
$bus = new MessageBus([
new HandleMessageMiddleware(new HandlersLocator([Ping::class => [$d1, $d2]])),
]);
$bus->dispatch(new Envelope(new Ping()));
echo $n;
``` | «11» Пояснение: The HandleMessageMiddleware calls all registered handlers for the Ping class, so $n is incremented by 1 and then by 10, resulting in 11.
Raw```json ⏎ {"answer": 11, "explanation": "The HandleMessageMiddleware calls all registered handlers for the Ping class, so $n is incremented by 1 and then by 10, resulting in 11."} ⏎ ``` | верно | All registered handlers of the message run: 1 + 10 = 11. |
T17-L9 1.26 c | PostgreSQL: transactions and indexes | What does this SQL query return (PostgreSQL 17)?
```sql
CREATE TEMP TABLE t (a int);
CREATE UNIQUE INDEX ON t (a);
INSERT INTO t VALUES (1) ON CONFLICT DO NOTHING;
INSERT INTO t VALUES (1) ON CONFLICT DO NOTHING;
SELECT count(*) FROM t;
``` | «1» Пояснение: The first insert succeeds, the second insert is skipped due to the unique index conflict with DO NOTHING, so the table contains one row.
Raw{"answer": 1, "explanation": "The first insert succeeds, the second insert is skipped due to the unique index conflict with DO NOTHING, so the table contains one row."} | верно | ON CONFLICT DO NOTHING skips the duplicate: one insert. |
T17-L10 1.77 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» Пояснение: DEFERRABLE INITIALLY DEFERRED means the unique constraint is only checked at transaction end, so both inserts succeed and count(*) returns 2.
Raw{"answer": 2, "explanation": "DEFERRABLE INITIALLY DEFERRED means the unique constraint is only checked at transaction end, so both inserts succeed and count(*) returns 2."} | верно | DEFERRED postpones the uniqueness check to COMMIT — count sees 2 rows. |
T18-L9 1.25 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), totaling 6 tests.
Raw{"answer": 6, "explanation": "The --filter test_sum matches both test_sum (3 data sets) and test_sum_abs (3 data sets), totaling 6 tests."} | верно | --filter is a substring match: test_sum also matches test_sum_abs (3+3 datasets). |
T18-L10 1.02 c | Testing: PHPUnit | How many tests will this command run, and how many of them will fail? Answer with two comma-separated numbers (ran, failed).
```php
use PHPUnit\Framework\TestCase;
use PHPUnit\Framework\Attributes\DataProvider;
final class Calc2Test extends TestCase
{
public function prov(): array
{
return [[1], [-1]];
}
#[DataProvider('prov')]
public function test_x(int $x): void
{
$this->assertTrue($x > 0);
}
}
```
Command: `phpunit Calc2Test.php` (PHPUnit 10.5) | «2, 1» Пояснение: The data provider supplies two values (1 and -1), both tests run, but assertTrue(-1 > 0) fails for the second case.
Raw{"answer": "2, 1", "explanation": "The data provider supplies two values (1 and -1), both tests run, but assertTrue(-1 > 0) fails for the second case."} | верно | 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.85 c | HTTP and REST API | Which HTTP method does this command send?
```bash
curl -s -d 'a=1' http://demo.local/api
``` | «post» Пояснение: curl's -d (or --data) flag sends data in the body and implicitly sets the HTTP method to POST.
Raw{"answer": "POST", "explanation": "curl's -d (or --data) flag sends data in the body and implicitly sets the HTTP method to POST."} | верно | -d/-F switches curl to POST by default. |
T19-L10 1.21 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 tells curl to use the GET method and append the -d data as a query string to the URL.
Raw{"answer": "GET", "explanation": "The -G flag tells curl to use the GET method and append the -d data as a query string to the URL."} | верно | -G turns -d data into the query string; the method stays GET. |
T20-L9 3.14 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 Section 5.2 defines 'invalid_client' as the error returned when client authentication fails, such as when the client_id is unknown to the authorization server.
Raw```json ⏎ {"answer": "invalid_client", "explanation": "RFC 6749 Section 5.2 defines 'invalid_client' as the error returned when client authentication fails, such as when the client_id is unknown to the authorization server."} ⏎ ``` | верно | Unknown client → invalid_client (RFC 6749 §5.2). |
T20-L10 1.18 c | Security and OAuth | OAuth 2.0: the client started the flow with response_type=token. In which part of the redirect_uri does the authorization server pass the access_token? | «fragment» Пояснение: In the OAuth 2.0 implicit grant (response_type=token), the access token is passed in the fragment part of the redirect URI (after the # symbol), not in the query string.
Raw{"answer": "fragment", "explanation": "In the OAuth 2.0 implicit grant (response_type=token), the access token is passed in the fragment part of the redirect URI (after the # symbol), not in the query string."} | верно | The implicit flow passes the token in the URL fragment (#) — it never reaches the server. |
T21-L9 1.99 c | Twig | What does this Twig template output?
```twig
{{ false|default(2) * 3 }}
``` | «0» Пояснение: The default filter only replaces null/undefined values (not false), so false remains false, which is cast to 0 in arithmetic, giving 0 * 3 = 0.
Raw{"answer": 0, "explanation": "The default filter only replaces null/undefined values (not false), so false remains false, which is cast to 0 in arithmetic, giving 0 * 3 = 0."} | неверно верный: «6» | default replaces exactly false/null/''/[] — false becomes 2, 2*3 = 6; the naive 'default is for undefined only' yields 0. |
T21-L10 7.57 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'.
Raw```json ⏎ {"answer": "a3", "explanation": "In Twig, the + operator has higher precedence than ~, so the expression is parsed as 'a' ~ (1 + 2) = 'a' ~ 3 = 'a3'."} ⏎ ``` | неверно верный: «runtimeerror» | In Twig ~ binds tighter than +: ('a' ~ 1) + 2 → string + int → a render error (RuntimeError). |
T22-L9 2.74 c | Symfony: Security and forms | What does this code output?
```php
use Symfony\Component\Validator\Validation;
use Symfony\Component\Validator\Constraints as Assert;
$v = Validation::createValidator();
echo count($v->validate([''], [new Assert\NotBlank()]));
``` | «0» Пояснение: NotBlank on an array checks if it is empty (count === 0); since [''] has one element, the constraint passes with 0 violations.
Raw{"answer": 0, "explanation": "NotBlank on an array checks if it is empty (count === 0); since [''] has one element, the constraint passes with 0 violations."} | верно | NotBlank treats null, '', [] as blank — the array [''] is not blank. |
T22-L10 4.22 c | Symfony: Security and forms | What does this code output?
```php
use Symfony\Component\Form\Forms;
use Symfony\Component\Form\Extension\Core\Type\TextType;
$factory = Forms::createFormFactoryBuilder()->getFormFactory();
$form = $factory->create(TextType::class);
try {
echo $form->isValid() ? 'valid' : 'invalid';
} catch (Throwable $e) {
echo get_class($e);
}
``` | «symfony\component\form\exception\logicexception» Пояснение: Calling isValid() on a form that has not been submitted throws a LogicException, which is caught and its class name is printed.
Raw{"answer": "Symfony\\Component\\Form\\Exception\\LogicException", "explanation": "Calling isValid() on a form that has not been submitted 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.48 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» Пояснение: Services in Symfony's DI container are shared (singleton) by default, so calling get() twice returns the same instance.
Raw{"answer": "same", "explanation": "Services in Symfony's DI container are shared (singleton) by default, so calling get() twice returns the same instance."} | верно | Container services are shared: two get() calls yield one instance. |
T23-L10 1.42 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!» Пояснение: During compile(), Symfony resolves nested parameter references: %name% becomes 'Bob', %greeting% becomes 'hi Bob', so %greeting%! becomes 'hi Bob!'.
Raw{"answer": "hi Bob!", "explanation": "During compile(), Symfony resolves nested parameter references: %name% becomes 'Bob', %greeting% becomes 'hi Bob', so %greeting%! becomes 'hi Bob!'."} | верно | compile() resolves %-references transitively: %greeting% → 'hi %name%' → 'hi Bob!', the answer assembles over two hops. |
T24-L9 1.16 c | Bootstrap | What is the max-width of .container in Bootstrap 5.3 at a 992px viewport? | «960» Пояснение: At the lg breakpoint (≥992px), Bootstrap 5.3 sets the .container max-width to 960px.
Raw{"answer": 960, "explanation": "At the lg breakpoint (≥992px), Bootstrap 5.3 sets the .container max-width to 960px."} | верно | 5.x container widths: 540/720/960/1140/1320 (sm–xxl); 992 → 960px. |
T24-L10 16.2 c | Bootstrap | Which utility sets the text color in Bootstrap 5.3 for `<p class="text-danger text-primary">…</p>`? Answer with the winning class name. | «text-primary» Пояснение: In Bootstrap 5.3's compiled CSS, .text-primary appears after .text-danger, so it wins the cascade when both classes are present on the same element.
Raw```json ⏎ {"answer": "text-primary", "explanation": "In Bootstrap 5.3's compiled CSS, .text-primary appears after .text-danger, so it wins the cascade when both classes are present on the same element."} ⏎ ``` | неверно верный: «text-danger» | Specificity ties — the later rule wins: text-danger is declared after text-primary. |
T25-L9 1.35 c | Clean architecture | Layers: Domain, Application, Infrastructure. Deptrac rules: Application → Domain; Infrastructure → Domain, Application; Domain → Domain only.
How many violations will deptrac report for this class?
```php
namespace App\Domain;
use App\Application\PlaceOrder;
use App\Infrastructure\Db;
class OrderService
{
public function __construct(
private PlaceOrder $handler,
private Db $db,
) {}
}
``` | «2» Пояснение: The Domain layer is in App\Domain and depends on both App\Application (PlaceOrder) and App\Infrastructure (Db), but Domain may only depend on Domain — two violations.
Raw{"answer": 2, "explanation": "The Domain layer is in App\\Domain and depends on both App\\Application (PlaceOrder) and App\\Infrastructure (Db), but Domain may only depend on Domain — two violations."} | верно | Domain may depend only on Domain: PlaceOrder (Application) + Db (Infrastructure) = 2. |
T25-L10 1.34 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 class is in the Domain layer which may only depend on Domain, but it references Application (PlaceOrder) and Infrastructure (Db, Logger), giving 3 violations.
Raw```json ⏎ {"answer": 3, "explanation": "The class is in the Domain layer which may only depend on Domain, but it references Application (PlaceOrder) and Infrastructure (Db, Logger), giving 3 violations."} ⏎ ``` | верно | The inline FQCN \App\Infrastructure\Logger counts too: Application + Db + Logger = 3. |
T26-L10 1.69 c | DDD | What does this code output?
```php
final class Money
{
public function __construct(public readonly int $amount) {}
public function add(Money $o): Money
{
return new self($this->amount + $o->amount);
}
}
$a = new Money(10);
$c = $a->add(new Money(5));
echo $a->amount . ',' . $c->amount;
``` | «10,15» Пояснение: The add method returns a new Money instance with the sum (15), while the original object $a retains its amount of 10.
Raw{"answer": "10,15", "explanation": "The add method returns a new Money instance with the sum (15), while the original object $a retains its amount of 10."} | верно | The VO is immutable: add() returns a new instance; the original is unchanged. |
T26-L9 1.56 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 before calling unset, so the item 'a' remains in the array and count returns 1.
Raw{"answer": 1, "explanation": "The remove method throws a DomainException before calling unset, so the item 'a' remains in the array and count returns 1."} | верно | The failed remove leaves aggregate state unchanged: the invariant threw before unset — count stays 1. |
VC-L9 3.57 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'.
Raw{"answer": "hi", "explanation": "The code creates an instance of class C and calls its hi() method, which returns the string 'hi'."} | верно | Since 8.4, new in a method chain works without wrapping parentheses. |
VC-L10 6.1 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 any property access the ghost is uninitialized (echoes 'yes'); after accessing $o->v the initializer runs and the object becomes initialized (echoes 'no').
Raw{"answer": "yesno", "explanation": "Before any property access the ghost is uninitialized (echoes 'yes'); after accessing $o->v the initializer runs and the object becomes initialized (echoes 'no')."} | верно | newLazyGhost (8.4): the object stays lazy until first access — reading a property initializes it and clears the flag. |
T28-L9 1.12 c | Symfony: versions | The project was upgraded from Symfony 6.4 to 8.1. What does this code output on 8.1?
```php
echo class_exists(\Symfony\Component\Security\Guard\AbstractGuardAuthenticator::class)
? 'yes' : 'no';
``` | «no» Пояснение: The Symfony Guard component was removed in Symfony 7.0, so AbstractGuardAuthenticator no longer exists in Symfony 8.1.
Raw```json ⏎ {"answer": "no", "explanation": "The Symfony Guard component was removed in Symfony 7.0, so AbstractGuardAuthenticator no longer exists in Symfony 8.1."} ⏎ ``` | верно | Guard authentication was removed in Symfony 7.0 — the class is gone in 8.1. |
T28-L10 1.57 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» Пояснение: AnnotationClassLoader was removed in Symfony 7.0, while AttributeClassLoader exists as its replacement.
Raw{"answer": "noyes", "explanation": "AnnotationClassLoader was removed in Symfony 7.0, while AttributeClassLoader exists as its replacement."} | верно | Annotation loaders were removed in 7.0; only attribute loaders remain (Annotation→Attribute). |