Пример запроса (первая клетка). 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 most escape sequences, while single-quoted strings only recognize \\' and \\\\, so they are processed differently, not just at different speeds.
Raw{"answer": "no", "explanation": "Double-quoted strings support variable interpolation and most escape sequences, while single-quoted strings only recognize \\\\' and \\\\\\\\, so they are processed differently, not just at different speeds."} | верно | В двойных кавычках работают интерполяция переменных и escape-последовательности, в одинарных — нет. |
T01-L2 1.16 c | Syntax and operators | The ?? operator follows isset semantics and raises no warnings for undefined variables. | «yes» Пояснение: The ?? operator is equivalent to isset($var) ? $var : default, so it safely handles undefined variables without raising warnings or notices.
Raw{"answer": "yes", "explanation": "The ?? operator is equivalent to isset($var) ? $var : default, so it safely handles undefined variables without raising warnings or notices."} | верно | ?? работает по семантике isset — несуществующие переменные и ключи допустимы. |
T01-L3 0.65 c | Syntax and operators | What will this print: echo 'a', 'b'; | «ab» Пояснение: In PHP, echo can take multiple comma-separated arguments and concatenates them without any separator.
Raw{"answer": "ab", "explanation": "In PHP, echo can take multiple comma-separated arguments and concatenates them without any separator."} | верно | echo принимает список аргументов: ab. |
T01-L4 3.16 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, so it can be used inside expressions (e.g., $x = print 'hello'; assigns 1 to $x), unlike echo which does not return a usable value.
Raw{"answer": "yes", "explanation": "In PHP, print is a language construct that always returns the integer 1, so it can be used inside expressions (e.g., $x = print 'hello'; assigns 1 to $x), unlike echo which does not return a usable value."} | верно | print — выражение со значением 1, в отличие от echo, который значения не возвращает. |
T01-L5 1.11 c | Syntax and operators | The ?: (elvis) operator returns its left operand when it is falsy. | «no» Пояснение: The Elvis operator ($a ?: $b) returns the left operand when it is truthy, not falsy; when falsy, it returns the right operand.
Raw{"answer": "no", "explanation": "The Elvis operator ($a ?: $b) returns the left operand when it is truthy, not falsy; when falsy, it returns the right operand."} | верно | Наоборот: $a ?: $b возвращает $a, если он истинный, иначе $b. |
T01-L6 1.58 c | Syntax and operators | In PHP 8, the concatenation operator (.) has lower precedence than addition and subtraction. | «no» Пояснение: In PHP, the concatenation operator (.) has the same precedence level as addition (+) and subtraction (-), not lower.
Raw{"answer": "no", "explanation": "In PHP, the concatenation operator (.) has the same precedence level as addition (+) and subtraction (-), not lower."} | неверно верный: «yes» | С PHP 8 (RFC concat precedence) '.' имеет приоритет ниже арифметики: 'сумма: ' . 2 + 3 → 'сумма: 5' (в PHP 7 было иначе). |
T01-L7 1.06 c | Syntax and operators | The expression 2 ** 3 ** 2 in PHP evaluates as (2 ** 3) ** 2, that is, 64. | «no» Пояснение: The ** operator in PHP is right-associative, so 2 ** 3 ** 2 is evaluated as 2 ** (3 ** 2) = 2 ** 9 = 512, not (2 ** 3) ** 2 = 64.
Raw{"answer": "no", "explanation": "The ** operator in PHP is right-associative, so 2 ** 3 ** 2 is evaluated as 2 ** (3 ** 2) = 2 ** 9 = 512, not (2 ** 3) ** 2 = 64."} | верно | ** право-ассоциативен: 2 ** (3 ** 2) = 2 ** 9 = 512. |
T01-L8 1.71 c | Syntax and operators | What string will this print: echo 'sum: ' . 2 + 3; (PHP 8)? | «sum: 5» Пояснение: In PHP, the + operator has higher precedence than the . concatenation operator, so it evaluates as 'sum: ' . (2 + 3) = 'sum: 5'.
Raw{"answer": "sum: 5", "explanation": "In PHP, the + operator has higher precedence than the . concatenation operator, so it evaluates as 'sum: ' . (2 + 3) = 'sum: 5'."} | верно | Парная к verify-клетке про приоритет: 'сумма: 5'. |
T02-L1 2.81 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 of the same types; order does matter.
Raw{"answer": "no", "explanation": "With ===, arrays must have the same key/value pairs in the same order and of the same types; order does matter."} | верно | === для массивов требует совпадения и значений, и их порядка. |
T02-L2 1.32 c | Types and comparisons | The comparison 0 == false returns false because it is a strict comparison. | «no» Пояснение: 0 == false returns true (not false) in PHP, and == is a loose (not strict) comparison; strict comparison uses ===.
Raw{"answer": "no", "explanation": "0 == false returns true (not false) in PHP, and == is a loose (not strict) comparison; strict comparison uses ===."} | верно | Наоборот: == — нестрогое сравнение и возвращает true; строгое — это === (0 === false → false). |
T02-L3 3.28 c | Types and comparisons | In PHP 8, the expression "abc" == 0 returns true. | «no» Пояснение: In PHP 8, comparing a non-numeric string to a number casts the number to a string, so 'abc' == 0 becomes 'abc' == '0', which is false.
Raw{"answer": "no", "explanation": "In PHP 8, comparing a non-numeric string to a number casts the number to a string, so 'abc' == 0 becomes 'abc' == '0', which is false."} | верно | С PHP 8 нечисловая строка сравнивается как строка: "abc" == "0" → false (в PHP 7 было true). |
T02-L4 4.32 c | Types and comparisons | Under loose comparison, null equals 0, the empty string, and false at the same time. | «yes» Пояснение: In PHP's loose comparison (==), null is considered equal to 0, the empty string '', and false (this was the behavior in PHP 7 and earlier; PHP 8 changed null==0 and null=='' to false, but null==false remains true).
Raw{"answer": "yes", "explanation": "In PHP's loose comparison (==), null is considered equal to 0, the empty string '', and false (this was the behavior in PHP 7 and earlier; PHP 8 changed null==0 and null=='' to false, but null==false remains true)."} | верно | null == 0, null == "" и null == false — все true. |
T02-L5 1.05 c | Types and comparisons | What does the expression (int) '42abc' return? | «42» Пояснение: PHP's (int) cast parses the leading numeric portion of a string and stops at the first non-numeric character, so '42abc' becomes 42.
Raw{"answer": 42, "explanation": "PHP's (int) cast parses the leading numeric portion of a string and stops at the first non-numeric character, so '42abc' becomes 42."} | верно | Ведущая числовая часть: 42, без ошибок и warning. |
T02-L6 0.92 c | Types and comparisons | What does the expression '5' + 5 return? | «10» Пояснение: In PHP, the + operator performs arithmetic addition, so the numeric string '5' is cast to int and added to 5, yielding 10.
Raw{"answer": 10, "explanation": "In PHP, the + operator performs arithmetic addition, so the numeric string '5' is cast to int and added to 5, yielding 10."} | верно | Числовая строка приводится: int 10. |
T02-L7 1.73 c | Types and comparisons | When cast to string, false becomes "0". | «no» Пояснение: In PHP, casting false to a string results in an empty string "", not "0".
Raw{"answer": "no", "explanation": "In PHP, casting false to a string results in an empty string \"\", not \"0\"."} | верно | false → "", true → "1". |
T02-L8 1.21 c | Types and comparisons | The comparison 0.1 + 0.2 === 0.3 returns false. | «yes» Пояснение: Due to floating-point precision, 0.1 + 0.2 yields 0.30000000000000004, which is not strictly equal to 0.3, so === returns false.
Raw{"answer": "yes", "explanation": "Due to floating-point precision, 0.1 + 0.2 yields 0.30000000000000004, which is not strictly equal to 0.3, so === returns false."} | верно | Двоичная погрешность float: 0.1 + 0.2 = 0.30000000000000004. |
T03-L1 1.46 c | Strings | strrev() correctly reverses a UTF-8 string. | «no» Пояснение: strrev() reverses strings byte-by-byte, which corrupts multi-byte UTF-8 characters; you need mb-aware functions to correctly reverse UTF-8 strings.
Raw{"answer": "no", "explanation": "strrev() reverses strings byte-by-byte, which corrupts multi-byte UTF-8 characters; you need mb-aware functions to correctly reverse UTF-8 strings."} | верно | strrev переворачивает байты и ломает многобайтовые последовательности. |
T03-L2 0.6 c | Strings | str_contains('Hello world', 'world') returns true. | «yes» Пояснение: str_checks() returns true because the string 'Hello world' does contain the substring 'world'.
Raw{"answer": "yes", "explanation": "str_checks() returns true because the string 'Hello world' does contain the substring 'world'."} | верно | str_contains с PHP 8.0 проверяет вхождение подстроки. |
T03-L3 1.05 c | Strings | str_pad() can pad a string on the right side only. | «no» Пояснение: str_pad() can pad on the right (STR_PAD_RIGHT), left (STR_PAD_LEFT), or both sides (STR_PAD_BOTH) via its pad_type parameter.
Raw{"answer": "no", "explanation": "str_pad() can pad on the right (STR_PAD_RIGHT), left (STR_PAD_LEFT), or both sides (STR_PAD_BOTH) via its pad_type parameter."} | верно | STR_PAD_LEFT / STR_PAD_BOTH меняют сторону дополнения. |
T03-L4 1.2 c | Strings | By default trim() strips only spaces, leaving tabs and newlines intact. | «no» Пояснение: By default, trim() strips spaces, tabs, newlines, carriage returns, NUL bytes, and vertical tabs, not just spaces.
Raw{"answer": "no", "explanation": "By default, trim() strips spaces, tabs, newlines, carriage returns, NUL bytes, and vertical tabs, not just spaces."} | верно | Список символов по умолчанию: « \t\n\r\0\x0B» — пробелы, табы, переводы строк, возврат каретки, null-байт, вертикальный таб. Проверено php -r. |
T03-L5 1.16 c | Strings | How many BYTES does strlen('héllo') return for a UTF-8 string? | «6» Пояснение: strlen() counts bytes; in UTF-8, 'é' is 2 bytes while 'h','l','l','o' are 1 byte each, giving 1+2+1+1+1=6.
Raw{"answer": 6, "explanation": "strlen() counts bytes; in UTF-8, 'é' is 2 bytes while 'h','l','l','o' are 1 byte each, giving 1+2+1+1+1=6."} | верно | 6 букв по 2 байта: 12. |
T03-L6 1.25 c | Strings | What does substr('abcdef', -3) return? | «def» Пояснение: substr with a negative start of -3 begins 3 characters from the end of 'abcdef', yielding 'def'.
Raw{"answer": "def", "explanation": "substr with a negative start of -3 begins 3 characters from the end of 'abcdef', yielding 'def'."} | верно | Отрицательное смещение — с конца: def. |
T03-L7 0.97 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 since PHP strings are passed by value.
Raw{"answer": "no", "explanation": "ucfirst() returns a new string with the first character uppercased; it does not modify the original string in place since PHP strings are passed by value."} | верно | Строки неизменяемы; ucfirst возвращает новую строку. |
T03-L8 0.86 c | Strings | Variable interpolation works in heredoc but not in nowdoc. | «yes» Пояснение: Heredoc interpolates variables like double-quoted strings, while nowdoc treats content as literal (like single-quoted strings), so no variable interpolation occurs.
Raw{"answer": "yes", "explanation": "Heredoc interpolates variables like double-quoted strings, while nowdoc treats content as literal (like single-quoted strings), so no variable interpolation occurs."} | верно | Nowdoc — «одинарные кавычки» в тройном синтаксисе: текст как есть. |
T04-L1 0.71 c | Arrays | The sort() function preserves the key-to-value association of the array. | «no» Пояснение: sort() reindexes the array with integer keys; asort() is the function that preserves key-to-value associations.
Raw{"answer": "no", "explanation": "sort() reindexes the array with integer keys; asort() is the function that preserves key-to-value associations."} | верно | sort перенумеровывает ключи; связь сохраняет asort. |
T04-L2 0.79 c | Arrays | The string key '5' in an array is stored as the integer 5. | «yes» Пояснение: PHP automatically casts numeric string keys like '5' to the integer 5 when used as array keys.
Raw{"answer": "yes", "explanation": "PHP automatically casts numeric string keys like '5' to the integer 5 when used as array keys."} | верно | Каноничные десятичные строковые ключи приводятся к int. |
T04-L3 0.93 c | Arrays | The in_array() function uses strict comparison (===) by default. | «no» Пояснение: The in_array() function defaults to $strict = false, meaning it uses loose comparison (==) rather than strict comparison (===) unless the third parameter is explicitly set to true.
Raw{"answer": "no", "explanation": "The in_array() function defaults to $strict = false, meaning it uses loose comparison (==) rather than strict comparison (===) unless the third parameter is explicitly set to true."} | верно | По умолчанию сравнение нестрогое; строгое — третий аргумент true. |
T04-L4 0.97 c | Arrays | Without a callback, array_filter() removes all "empty" (falsy) elements from the array. | «yes» Пояснение: Without a callback, array_filter() keeps only elements that evaluate to true, effectively removing all falsy values (0, '', null, false, '0', empty array).
Raw{"answer": "yes", "explanation": "Without a callback, array_filter() keeps only elements that evaluate to true, effectively removing all falsy values (0, '', null, false, '0', empty array)."} | верно | Убирает 0, "", null, false и пустые массивы. |
T04-L5 1.06 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, so keys are reindexed by default.
Raw{"answer": "no", "explanation": "The $preserve_keys parameter of array_slice() defaults to false, so keys are reindexed by default."} | верно | По умолчанию ключи перенумеровываются; сохранение — preserve_keys = true. |
T04-L6 1.01 c | Arrays | What does array_slice([10, 20, 30, 40], 1, 2) return? | «[20, 30]» Пояснение: array_slice starts at offset 1 and takes 2 elements, yielding [20, 30].
Raw{"answer": "[20, 30]", "explanation": "array_slice starts at offset 1 and takes 2 elements, yielding [20, 30]."} | верно | [20,30]; ключи перенумеровываются. |
T04-L7 1.59 c | Arrays | How many elements will count(['a' => 1] + ['a' => 9, 'b' => 2]) return? | «2» Пояснение: The array union operator (+) keeps the left array's value for duplicate keys and adds only new keys from the right, resulting in ['a' => 1, 'b' => 2], which has 2 elements.
Raw{"answer": 2, "explanation": "The array union operator (+) keeps the left array's value for duplicate keys and adds only new keys from the right, resulting in ['a' => 1, 'b' => 2], which has 2 elements."} | верно | Оператор + : по ключу 'a' побеждает левый; итого 2. |
T04-L8 2.0 c | Arrays | Since PHP 8.1, the spread operator [...$a, ...$b] supports arrays with string keys. | «yes» Пояснение: PHP 8.1 extended the spread operator in array literals to support arrays with string (associative) keys, which previously caused a TypeError.
Raw{"answer": "yes", "explanation": "PHP 8.1 extended the spread operator in array literals to support arrays with string (associative) keys, which previously caused a TypeError."} | верно | В 8.0 — только числовые ключи; 8.1 снял ограничение. |
T05-L1 3.07 c | Functions and closures | Named arguments cannot be combined with argument unpacking ...$args in a single call. | «no» Пояснение: PHP does allow combining named arguments with the spread/unpacking operator in a single call (e.g., foo(a: 1, ...$args, c: 3)); the only restriction is that once a named argument is used, all subsequent arguments must also be named.
Raw{"answer": "no", "explanation": "PHP does allow combining named arguments with the spread/unpacking operator in a single call (e.g., foo(a: 1, ...$args, c: 3)); the only restriction is that once a named argument is used, all subsequent arguments must also be named."} | верно | Можно: f(...$args, имя: значение). Нельзя только позиционный аргумент после распаковки. |
T05-L2 0.88 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; you must explicitly use the 'use' keyword to import them.
Raw{"answer": "no", "explanation": "In PHP, closures do not automatically inherit variables from the outer scope; you must explicitly use the 'use' keyword to import them."} | верно | Без use внешние переменные недоступны; авто-захват только у fn. |
T05-L3 0.98 c | Functions and closures | What will func_num_args() return inside function f($a) { return func_num_args(); } when called as f(1, 2, 3)? | «3» Пояснение: func_num_args() returns the number of arguments actually passed to the function, which is 3 (1, 2, 3), regardless of how many parameters are declared.
Raw{"answer": 3, "explanation": "func_num_args() returns the number of arguments actually passed to the function, which is 3 (1, 2, 3), regardless of how many parameters are declared."} | верно | Считает переданные аргументы: 3. |
T05-L4 1.53 c | Functions and closures | The body of an arrow function fn may consist of several expressions in curly braces. | «no» Пояснение: An arrow function (fn) in PHP must consist of exactly one expression after the => operator; it does not use curly braces or allow multiple expressions.
Raw{"answer": "no", "explanation": "An arrow function (fn) in PHP must consist of exactly one expression after the => operator; it does not use curly braces or allow multiple expressions."} | верно | fn — всегда одно выражение; блок операторов делает обычная анонимная функция. |
T05-L5 1.98 c | Functions and closures | An arrow function fn captures outer variables by reference (lazily, at use time). | «no» Пояснение: PHP arrow functions (fn) capture outer variables by value at the time of creation, not by reference or lazily at use time.
Raw{"answer": "no", "explanation": "PHP arrow functions (fn) capture outer variables by value at the time of creation, not by reference or lazily at use time."} | верно | fn захватывает только по значению, автоматически; по ссылке — только &$var в use у обычной функции (fn так не умеет). |
T05-L6 0.97 c | Functions and closures | A closure declared as static function () {} does not capture $this. | «yes» Пояснение: A static closure in PHP explicitly breaks the automatic $this binding, so it has no access to $this.
Raw{"answer": "yes", "explanation": "A static closure in PHP explicitly breaks the automatic $this binding, so it has no access to $this."} | верно | static-замыкание отвязано от объекта: $this внутри недоступен. |
T05-L7 1.03 c | Functions and closures | What will this print: $x = 5; $f = function () use ($x) { return $x; }; $x = 7; echo $f(); | «5» Пояснение: The closure captures $x by value (5) at definition time via use($x), so the later reassignment to 7 has no effect.
Raw{"answer": 5, "explanation": "The closure captures $x by value (5) at definition time via use($x), so the later reassignment to 7 has no effect."} | верно | use захватывает по значению в момент создания: 5. |
T05-L8 0.96 c | Functions and closures | In weak typing mode (without strict_types), passing the string "5" to an int parameter is allowed. | «yes» Пояснение: In PHP's default weak typing mode, a numeric string like "5" is automatically coerced to the integer 5 when passed to a function with an int type hint.
Raw{"answer": "yes", "explanation": "In PHP's default weak typing mode, a numeric string like \"5\" is automatically coerced to the integer 5 when passed to a function with an int type hint."} | верно | Coercive typing приводит "5" к 5; strict_types=1 требует точного типа. |
T06-L1 0.98 c | OOP: classes and inheritance | PHP supports constructor property promotion: public function __construct(private int $x) {}. | «yes» Пояснение: Constructor property promotion was introduced in PHP 8.0, allowing parameters like 'private int $x' in __construct to automatically create and assign a property.
Raw{"answer": "yes", "explanation": "Constructor property promotion was introduced in PHP 8.0, allowing parameters like 'private int $x' in __construct to automatically create and assign a property."} | верно | С PHP 8.0 параметр с модификатором создаёт свойство и присваивание. |
T06-L2 0.53 c | OOP: classes and inheritance | Which keyword prevents a method from being overridden in subclasses? | «final» Пояснение: In PHP, the 'final' keyword before a method declaration prevents subclasses from overriding that method.
Raw{"answer": "final", "explanation": "In PHP, the 'final' keyword before a method declaration prevents subclasses from overriding that method."} | верно | final. |
T06-L3 0.67 c | OOP: classes and inheritance | A method declared final cannot be overridden in a subclass. | «yes» Пояснение: In PHP, declaring a method as final prevents it from being overridden in any subclass.
Raw{"answer": "yes", "explanation": "In PHP, declaring a method as final prevents it from being overridden in any subclass."} | верно | final запрещает переопределение метода и наследование класса. |
T06-L4 0.74 c | OOP: classes and inheritance | Parent properties with private visibility are accessible in a subclass. | «no» Пояснение: In PHP, private properties are only accessible within the class that defines them and are not accessible in subclasses; only public and protected properties are inherited.
Raw{"answer": "no", "explanation": "In PHP, private properties are only accessible within the class that defines them and are not accessible in subclasses; only public and protected properties are inherited."} | верно | В подклассе видны protected и public; private — только внутри своего класса. |
T06-L5 1.47 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» Пояснение: Anonymous classes in PHP are named 'class@anonymous' followed by a NUL byte and then the file path and line number.
Raw{"answer": "class@anonymous", "explanation": "Anonymous classes in PHP are named 'class@anonymous' followed by a NUL byte and then the file path and line number."} | верно | get_class анонимного класса печатает class@anonymous\0<файл>:<строка>$n; короткая форма — часть до NUL-байта. Проверено php -r (hex). |
T06-L6 1.23 c | OOP: classes and inheritance | A private parent method is not part of the inheritance contract: a child may declare a method with the same name and any visibility. | «yes» Пояснение: Private methods are scoped to their declaring class and are not part of the inheritance contract, so a child class is free to declare a same-named method with any visibility.
Raw{"answer": "yes", "explanation": "Private methods are scoped to their declaring class and are not part of the inheritance contract, so a child class is free to declare a same-named method with any visibility."} | верно | private-члены не наследуются — правила совместимости подписей не действуют. |
T06-L7 1.19 c | OOP: classes and inheritance | The magic method __get() is called only for non-existent properties. | «no» Пояснение: __get() is called for both non-existent properties AND inaccessible (private/protected) properties when accessed from outside the class.
Raw{"answer": "no", "explanation": "__get() is called for both non-existent properties AND inaccessible (private/protected) properties when accessed from outside the class."} | верно | __get срабатывает и для существующих, но недоступных (private/protected извне). |
T06-L8 0.9 c | OOP: classes and inheritance | What does reassigning a readonly property throw — Exception or Error? | «error» Пояснение: Reassigning a readonly property in PHP throws an Error (not an Exception), specifically a fatal Error with a message like 'Cannot modify readonly property'.
Raw{"answer": "Error", "explanation": "Reassigning a readonly property in PHP throws an Error (not an Exception), specifically a fatal Error with a message like 'Cannot modify readonly property'."} | верно | Error (readonly с 8.1); оговорка: в __clone() переинициализация допустима (8.3+). |
T07-L1 0.67 c | Interfaces, traits, enum | An interface can declare constants. | «yes» Пояснение: In PHP, interfaces can declare public constants, which are accessible and immutable.
Raw{"answer": "yes", "explanation": "In PHP, interfaces can declare public constants, which are accessible and immutable."} | верно | Константы интерфейса наследуются реализациями. |
T07-L2 0.59 c | Interfaces, traits, enum | Which operator checks whether an object is an instance of a class or interface? | «instanceof» Пояснение: In PHP, the instanceof operator is used to check whether an object is an instance of a specific class or implements a specific interface.
Raw{"answer": "instanceof", "explanation": "In PHP, the instanceof operator is used to check whether an object is an instance of a specific class or implements a specific interface."} | верно | instanceof. |
T07-L3 2.07 c | Interfaces, traits, enum | An interface can declare static methods. | «yes» Пояснение: PHP interfaces can declare static methods, which the implementing class must also implement as static.
Raw{"answer": "yes", "explanation": "PHP interfaces can declare static methods, which the implementing class must also implement as static."} | верно | Реализация обязана дать статический метод с той же сигнатурой. |
T07-L4 0.77 c | Interfaces, traits, enum | The instanceof operator only checks class inheritance: it ignores interfaces. | «no» Пояснение: PHP's instanceof operator checks both class inheritance and interface implementation, so it does not ignore interfaces.
Raw{"answer": "no", "explanation": "PHP's instanceof operator checks both class inheritance and interface implementation, so it does not ignore interfaces."} | верно | instanceof возвращает true и для интерфейсов объекта. |
T07-L5 1.67 c | Interfaces, traits, enum | An interface method may have a default implementation, like a trait method. | «no» Пояснение: In PHP, interface methods must be abstract (signature only, no body); they cannot have a default implementation, unlike trait methods which can be concrete.
Raw{"answer": "no", "explanation": "In PHP, interface methods must be abstract (signature only, no body); they cannot have a default implementation, unlike trait methods which can be concrete."} | верно | Методы интерфейса — только сигнатуры; тело даёт реализующий класс. |
T07-L6 0.85 c | Interfaces, traits, enum | An abstract method in an abstract class may have protected visibility. | «yes» Пояснение: In PHP, abstract methods can be declared as either public or protected (but not private), so protected visibility is allowed for abstract methods in an abstract class.
Raw{"answer": "yes", "explanation": "In PHP, abstract methods can be declared as either public or protected (but not private), so protected visibility is allowed for abstract methods in an abstract class."} | верно | В абстрактном классе — любая видимость; в интерфейсе — только public. |
T07-L7 0.92 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.
Raw{"answer": 3, "explanation": "Foo::cases() returns an array containing all defined cases of the enum, which are A, B, and C."} | верно | Статический метод cases(): 3. |
T07-L8 2.34 c | Interfaces, traits, enum | A trait can declare constants. | «yes» Пояснение: PHP traits are allowed to declare constants, which become available to any class that uses the trait.
Raw{"answer": "yes", "explanation": "PHP traits are allowed to declare constants, which become available to any class that uses the trait."} | верно | С PHP 8.2 трейты могут объявлять константы (RFC constants_in_traits); до 8.2 — нет. |
T08-L1 0.69 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.1 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, so a catch(Exception $e) block will not catch TypeError; you'd need catch(Throwable $e) to catch both.
Raw{"answer": "no", "explanation": "TypeError extends Error, not Exception, so a catch(Exception $e) block will not catch TypeError; you'd need catch(Throwable $e) to catch both."} | верно | TypeError наследуется от Error; catch (Exception) его не ловит. |
T08-L3 1.05 c | Exceptions and errors | The @ operator suppresses exceptions too. | «no» Пояснение: The @ operator only suppresses error reporting (warnings, notices, etc.) and does not prevent exceptions from being thrown.
Raw{"answer": "no", "explanation": "The @ operator only suppresses error reporting (warnings, notices, etc.) and does not prevent exceptions from being thrown."} | верно | @ глушит диагностику (warnings/notices), исключения не перехватывает. |
T08-L4 0.82 c | Exceptions and errors | What error class does intdiv(5, 0) throw? | «divisionbyzeroerror» Пояснение: intdiv() throws a DivisionByZeroError (a subclass of ArithmeticError) when the divisor is zero.
Raw{"answer": "DivisionByZeroError", "explanation": "intdiv() throws a DivisionByZeroError (a subclass of ArithmeticError) when the divisor is zero."} | верно | DivisionByZeroError (иерархия Error, не Exception); php-грейдер объективен. |
T08-L5 1.03 c | Exceptions and errors | The finally block runs only if the exception was caught by a catch block. | «no» Пояснение: The finally block executes regardless of whether an exception was thrown, caught, or even if no exception occurred at all.
Raw{"answer": "no", "explanation": "The finally block executes regardless of whether an exception was thrown, caught, or even if no exception occurred at all."} | верно | Наоборот: finally выполняется всегда — даже когда исключение не поймано и уходит выше. Проверено php -r. |
T08-L6 2.87 c | Exceptions and errors | An exception thrown inside a finally block has no effect on the result of the try block. | «no» Пояснение: In PHP, an exception thrown in a finally block actually supersedes (replaces) any pending exception from the try or catch block, so it does affect the outcome.
Raw{"answer": "no", "explanation": "In PHP, an exception thrown in a finally block actually supersedes (replaces) any pending exception from the try or catch block, so it does affect the outcome."} | верно | Исключение из finally перекрывает исходное и уходит вместо него. |
T08-L7 0.76 c | Exceptions and errors | What does the expression (bool) new Exception('x') return? | «yes» Пояснение: In PHP, casting any existing object (including an Exception) to bool always yields true.
Raw{"answer": "yes", "explanation": "In PHP, casting any existing object (including an Exception) to bool always yields true."} | верно | Любой объект при приведении к bool — true. Формы ответа: true или да. |
T08-L8 1.15 c | Exceptions and errors | Functions registered via register_shutdown_function() run when exit is called. | «yes» Пояснение: register_shutdown_function() callbacks are executed during script shutdown, which is triggered when exit() or die() is called.
Raw{"answer": "yes", "explanation": "register_shutdown_function() callbacks are executed during script shutdown, which is triggered when exit() or die() is called."} | верно | exit завершает скрипт, но shutdown-функции отрабатывают. |
T09-L1 1.36 c | Namespaces and autoloading | The use App\Service\Mailer; statement itself loads the class file. | «no» Пояснение: The use statement only registers an alias for a fully-qualified class name; the class file is actually loaded (via the autoloader) only when the class is first referenced at runtime.
Raw{"answer": "no", "explanation": "The use statement only registers an alias for a fully-qualified class name; the class file is actually loaded (via the autoloader) only when the class is first referenced at runtime."} | верно | use — псевдоним на этапе компиляции; файл грузит автозагрузчик при первом обращении. |
T09-L2 0.92 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 Namespace\function;', while 'use const' is used for importing constants.
Raw{"answer": "function", "explanation": "In PHP, to import a function you use 'use function Namespace\\function;', while 'use const' is used for importing constants."} | верно | use function ...; (и use const для констант). |
T09-L3 1.02 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 each namespace segment to a directory: App\→src/, so App\Controller\Api\UserController becomes src/Controller/Api/UserController.php.
Raw{"answer": "Controller/Api/UserController.php", "explanation": "PSR-4 maps each namespace segment to a directory: App\\→src/, so App\\Controller\\Api\\UserController becomes src/Controller/Api/UserController.php."} | верно | Остаток имени после префикса, \ → /. |
T09-L4 1.27 c | Namespaces and autoloading | Including vendor/autoload.php registers autoloaders via spl_autoload_register(). | «yes» Пояснение: Composer's vendor/autoload.php bootstraps the autoloading system by ultimately calling spl_autoload_register() to register the Composer\Autoload\ClassLoader.
Raw{"answer": "yes", "explanation": "Composer's vendor/autoload.php bootstraps the autoloading system by ultimately calling spl_autoload_register() to register the Composer\\Autoload\\ClassLoader."} | верно | Composer ставит автозагрузчик именно на spl_autoload_register. |
T09-L5 0.63 c | Namespaces and autoloading | The magic constant __NAMESPACE__ contains the name of the current namespace. | «yes» Пояснение: __NAMESPACE__ is a PHP magic constant that returns the name of the current namespace (or an empty string in the global namespace).
Raw{"answer": "yes", "explanation": "__NAMESPACE__ is a PHP magic constant that returns the name of the current namespace (or an empty string in the global namespace)."} | верно | В корневом пространстве — пустая строка. |
T09-L6 2.4 c | Namespaces and autoloading | An unqualified class name (without a leading \) in new is resolved from the global root. | «no» Пояснение: An unqualified class name without a leading backslash is resolved relative to the current namespace first, and only falls back to the global root if the class is not found in the current namespace.
Raw{"answer": "no", "explanation": "An unqualified class name without a leading backslash is resolved relative to the current namespace first, and only falls back to the global root if the class is not found in the current namespace."} | верно | Резолвится относительно текущего namespace (с учётом импортов). |
T09-L7 1.27 c | Namespaces and autoloading | With the PSR-4 mapping "App\ → src/", the class App\Model\User lives in the file src/Model/User.php. | «yes» Пояснение: PSR-4 maps the remaining namespace segments after the prefix (Model\User) to subdirectories, yielding src/Model/User.php.
Raw{"answer": "yes", "explanation": "PSR-4 maps the remaining namespace segments after the prefix (Model\\User) to subdirectories, yielding src/Model/User.php."} | верно | Остаток имени после префикса переносится в путь как есть. |
T09-L8 1.99 c | Namespaces and autoloading | A use statement may be written inside a function body — the import then applies to that function only. | «no» Пояснение: In PHP, use statements must be declared in the outermost (global) scope of a file and cannot be placed inside a function body.
Raw{"answer": "no", "explanation": "In PHP, use statements must be declared in the outermost (global) scope of a file and cannot be placed inside a function body."} | верно | use внутри тела функции — parse error; импорты файловые и компиляционные. |
T10-L1 1.07 c | References and scope | Arrays are copied on assignment rather than passed by reference. | «yes» Пояснение: In PHP, arrays are value types; assigning an array to another variable creates a copy (using copy-on-write internally), not a reference.
Raw{"answer": "yes", "explanation": "In PHP, arrays are value types; assigning an array to another variable creates a copy (using copy-on-write internally), not a reference."} | верно | Присваивание массива — копия (в движке — copy-on-write). |
T10-L2 1.09 c | References and scope | What will this print: $a = [1, 2]; $b = $a; $b[] = 3; echo count($a); | «2» Пояснение: PHP arrays are copied by value on assignment, so modifying $b does not affect $a, which still contains 2 elements.
Raw{"answer": 2, "explanation": "PHP arrays are copied by value on assignment, so modifying $b does not affect $a, which still contains 2 elements."} | верно | Присваивание — копия: в $a по-прежнему 2 элемента. |
T10-L3 1.15 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 directly accessible inside a function; you must use the 'global' keyword, the $GLOBALS array, or pass them as parameters to access them.
Raw{"answer": "yes", "explanation": "In PHP, variables defined in the global scope are not directly accessible inside a function; you must use the 'global' keyword, the $GLOBALS array, or pass them as parameters to access them."} | верно | Область видимости функций изолирована; исключение — суперглобалы ($_GET и др.). |
T10-L4 1.98 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 symbol table entirely, not just within the function's scope.
Raw{"answer": "no", "explanation": "unset($GLOBALS['x']) removes the variable from the global symbol table entirely, not just within the function's scope."} | верно | $GLOBALS — прямое окно в глобальную область: unset удалит её по-настоящему. |
T10-L5 1.04 c | References and scope | What will this print: function inc(&$x) { $x++; } $n = 5; inc($n); echo $n; | «6» Пояснение: The function parameter is passed by reference (&$x), so $n is incremented from 5 to 6 and the change is visible in the calling scope.
Raw{"answer": 6, "explanation": "The function parameter is passed by reference (&$x), so $n is incremented from 5 to 6 and the change is visible in the calling scope."} | верно | Ссылка меняет оригинал: 6. |
T10-L6 4.17 c | References and scope | A foreach over an array (by value) works with the "live" array: changes to the array inside the loop are visible in the same pass. | «no» Пояснение: PHP's foreach by value iterates over a snapshot of the array taken at the start of the loop, so elements added or removed inside the loop do not affect the current pass.
Raw{"answer": "no", "explanation": "PHP's foreach by value iterates over a snapshot of the array taken at the start of the loop, so elements added or removed inside the loop do not affect the current pass."} | верно | По значению foreach итерирует копию-снимок. |
T10-L7 0.98 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, so all instances share the same value; it is non-static (instance) properties that are separate per object.
Raw{"answer": "no", "explanation": "A static property belongs to the class itself, so all instances share the same value; it is non-static (instance) properties that are separate per object."} | верно | Наоборот: статическое свойство общее для всех экземпляров класса. Проверено php -r. |
T10-L8 1.47 c | References and scope | An array can have a boolean key true, and it will be stored as bool. | «no» Пояснение: In PHP, boolean values used as array keys are cast to integers (true becomes 1, false becomes 0); they are not stored as bool keys.
Raw{"answer": "no", "explanation": "In PHP, boolean values used as array keys are cast to integers (true becomes 1, false becomes 0); they are not stored as bool keys."} | верно | Булев ключ приводится к int: true → 1, false → 0. |
T11-L1 1.32 c | Generators, iterators, SPL | Inside a generator, return with a value can be used, and it becomes available via $gen->getReturn(). | «yes» Пояснение: In PHP generators, a return statement with a value is supported, and that value can be retrieved after the generator is exhausted via the Generator object's getReturn() method.
Raw{"answer": "yes", "explanation": "In PHP generators, a return statement with a value is supported, and that value can be retrieved after the generator is exhausted via the Generator object's getReturn() method."} | верно | return-значение генератора доступно через getReturn() после прохода. |
T11-L2 1.84 c | Generators, iterators, SPL | A fully consumed generator can be rewound with rewind() and traversed again. | «no» Пояснение: PHP generators are one-shot iterators; once fully consumed, they cannot be rewound or iterated again.
Raw{"answer": "no", "explanation": "PHP generators are one-shot iterators; once fully consumed, they cannot be rewound or iterated again."} | верно | Генератор одноразовый: rewind после начала итерации бросает Exception. |
T11-L3 2.62 c | Generators, iterators, SPL | The yield from construct delegates traversal to another generator or iterable. | «yes» Пояснение: yield from is a Python construct that delegates iteration to another iterable or generator, forwarding yielded values and handling send/return/throw, making the statement true.
Raw{"answer": "yes", "explanation": "yield from is a Python construct that delegates iteration to another iterable or generator, forwarding yielded values and handling send/return/throw, making the statement true."} | верно | yield from проксирует значения, ключи и return-значение внутреннего генератора. |
T11-L4 1.02 c | Generators, iterators, SPL | What does get_class(g()) return for function g() { yield 1; }? | «generator» Пояснение: A function containing 'yield' returns a Generator object, so get_class() on it returns the string 'Generator'.
Raw{"answer": "Generator", "explanation": "A function containing 'yield' returns a Generator object, so get_class() on it returns the string 'Generator'."} | верно | Функция с yield возвращает Generator. |
T11-L5 1.24 c | Generators, iterators, SPL | How many elements will count(iterator_to_array((function () { yield from [1, 2, 3]; })())) return? | «3» Пояснение: The generator yields three values (1, 2, 3), iterator_to_array produces an array with 3 elements, and count returns 3.
Raw{"answer": 3, "explanation": "The generator yields three values (1, 2, 3), iterator_to_array produces an array with 3 elements, and count returns 3."} | верно | yield from делегирует все 3 элемента. |
T11-L6 0.84 c | Generators, iterators, SPL | The SplStack class implements a FIFO queue. | «no» Пояснение: SplStack implements a LIFO (Last In, First Out) structure, while SplQueue implements a FIFO queue.
Raw{"answer": "no", "explanation": "SplStack implements a LIFO (Last In, First Out) structure, while SplQueue implements a FIFO queue."} | верно | SplStack — стек LIFO; очередь FIFO — SplQueue. |
T11-L7 0.81 c | Generators, iterators, SPL | ArrayIterator allows wrapping an array and traversing it via the Iterator interface. | «yes» Пояснение: ArrayIterator is a built-in PHP class that wraps an array and implements the Iterator interface, allowing traversal via current(), key(), next(), rewind(), and valid() methods.
Raw{"answer": "yes", "explanation": "ArrayIterator is a built-in PHP class that wraps an array and implements the Iterator interface, allowing traversal via current(), key(), next(), rewind(), and valid() methods."} | верно | Объектная обёртка над массивом. |
T11-L8 0.78 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.18 c | Configuration and security | password_hash() generates a salt automatically — passing one separately is not needed. | «yes» Пояснение: password_hash() automatically generates and embeds a random salt in the resulting hash, so there is no need to supply one separately.
Raw{"answer": "yes", "explanation": "password_hash() automatically generates and embeds a random salt in the resulting hash, so there is no need to supply one separately."} | верно | Соль встраивается в строку результата; параметр salt устарел. |
T12-L2 1.2 c | Configuration and security | In PHP 8, PASSWORD_DEFAULT is md5 with an automatically added salt. | «no» Пояснение: In PHP 8, PASSWORD_DEFAULT is bcrypt (PASSWORD_BCRYPT), not md5; md5 is not a secure or supported password hashing algorithm in PHP's password_* functions.
Raw{"answer": "no", "explanation": "In PHP 8, PASSWORD_DEFAULT is bcrypt (PASSWORD_BCRYPT), not md5; md5 is not a secure or supported password hashing algorithm in PHP's password_* functions."} | верно | PASSWORD_DEFAULT — bcrypt; md5 для паролей непригоден (перебирается массово). |
T12-L3 0.92 c | Configuration and security | What does password_verify('secret', password_hash('secret', PASSWORD_DEFAULT)) return? | «yes» Пояснение: password_verify checks if the given password matches the hash, and since 'secret' was used to generate the hash, it returns true.
Raw{"answer": "yes", "explanation": "password_verify checks if the given password matches the hash, and since 'secret' was used to generate the hash, it returns true."} | верно | Соль и хеш в одной строке: true (форма ответа: true или да). |
T12-L4 1.45 c | Configuration and security | strip_tags() protects against SQL injection. | «no» Пояснение: strip_tags() only removes HTML and PHP tags from a string; it has no effect on SQL injection, which must be prevented with prepared statements or proper parameterized queries.
Raw{"answer": "no", "explanation": "strip_tags() only removes HTML and PHP tags from a string; it has no effect on SQL injection, which must be prevented with prepared statements or proper parameterized queries."} | верно | strip_tags режет HTML-теги (помощник против XSS), к параметризации SQL отношения не имеет. |
T12-L5 1.06 c | Configuration and security | session_regenerate_id() is used to protect against session fixation upon user login. | «yes» Пояснение: session_regenerate_id() creates a new session ID, invalidating the old one, which is the standard technique to mitigate session fixation attacks after a user's privilege level changes (e.g., upon login).
Raw{"answer": "yes", "explanation": "session_regenerate_id() creates a new session ID, invalidating the old one, which is the standard technique to mitigate session fixation attacks after a user's privilege level changes (e.g., upon login)."} | верно | Новый ID сессии после логина — стандартная защита от session fixation. |
T12-L6 0.88 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 PHP function that returns the current SAPI module name, such as 'cli', 'apache2', or 'fpm-fcgi'.
Raw{"answer": "php_sapi_name", "explanation": "php_sapi_name() is the built-in PHP function that returns the current SAPI module name, such as 'cli', 'apache2', or 'fpm-fcgi'."} | верно | php_sapi_name(). |
T12-L7 1.33 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 stored server-side; the session cookie in the browser persists unless explicitly deleted via setcookie() with a past expiration.
Raw{"answer": "yes", "explanation": "session_destroy() only removes the session data stored server-side; the session cookie in the browser persists unless explicitly deleted via setcookie() with a past expiration."} | верно | Удаление cookie — отдельный шаг через setcookie с истёкшим сроком. |
T12-L8 1.08 c | Configuration and security | Without calling session_start(), the $_SESSION array is automatically populated with session data. | «no» Пояснение: The $_SESSION array is only populated with session data after session_start() is called; without it, $_SESSION remains empty.
Raw{"answer": "no", "explanation": "The $_SESSION array is only populated with session data after session_start() is called; without it, $_SESSION remains empty."} | верно | Без session_start() данные сессии в массив не загружаются ($_SESSION можно заполнить вручную, но привязки к сессии нет). |
VC-L1 1.91 c | PHP 8.4–8.5 | In which PHP version was the array_find() function introduced? | «8.4» Пояснение: The array_find() function was introduced as part of the new array helper functions in PHP 8.4.
Raw{"answer": "8.4", "explanation": "The array_find() function was introduced as part of the new array helper functions in PHP 8.4."} | верно | PHP 8.4 (RFC array_find). |
VC-L2 1.48 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 1.12 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) string $name) was introduced as a new feature in PHP 8.4.
Raw{"answer": "yes", "explanation": "Asymmetric visibility (e.g., public private(set) string $name) was introduced as a new feature in PHP 8.4."} | верно | Asymmetric visibility v2 — PHP 8.4. |
VC-L4 3.39 c | PHP 8.4–8.5 | In which PHP version was the #[\NoDiscard] attribute introduced? Answer with the version number. | «no» Пояснение: The #[\NoDiscard] attribute does not exist in any released version of PHP.
Raw{"answer": "no", "explanation": "The #[\\NoDiscard] attribute does not exist in any released version of PHP."} | неверно верный: «8.5» | #[\NoDiscard] — PHP 8.5 (marking return values as important). |
VC-L5 3.83 c | PHP 8.4–8.5 | In which PHP version did the pipe operator |> first appear? Answer with the version number. | «no» Пояснение: PHP has never introduced a pipe operator '|>'; the '|' in PHP is only the bitwise OR operator.
Raw{"answer": "no", "explanation": "PHP has never introduced a pipe operator '|>'; the '|' in PHP is only the bitwise OR operator."} | неверно верный: «8.5» | Pipe operator — PHP 8.5 (2025). |
VC-L6 2.66 c | PHP 8.4–8.5 | In which PHP version did clone-with — the syntax clone($obj, ['x' => 1]) — appear? Answer with the version number. | «does not exist» Пояснение: PHP has never introduced a 'clone-with' syntax like clone($obj, ['x' => 1]); the clone operator only accepts a single object and has no provision for additional parameters in any released PHP version.
Raw{"answer": "does not exist", "explanation": "PHP has never introduced a 'clone-with' syntax like clone($obj, ['x' => 1]); the clone operator only accepts a single object and has no provision for additional parameters in any released PHP version."} | неверно верный: «8.5» | Clone with v2 — PHP 8.5. |
VC-L7 2.49 c | PHP 8.4–8.5 | In which PHP version were the array_first() and array_last() functions introduced? | «never» Пояснение: array_first() and array_last() are not built-in PHP functions in any released version of PHP.
Raw{"answer": "never", "explanation": "array_first() and array_last() are not built-in PHP functions in any released version of PHP."} | неверно верный: «8.5» | PHP 8.5. |
VC-L8 3.98 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. | «9.0» Пояснение: The Partial Function Application v2 RFC is associated with PHP 9.0.
Raw{"answer": 9.0, "explanation": "The Partial Function Application v2 RFC is associated with PHP 9.0."} | неверно верный: «8.6» | PFA v2 принят 05.12.2025 (33-0-0), реализован в PHP 8.6. |
VF-L1 4.63 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_v2 RFC, which introduced the clamp() function, was implemented in PHP 8.4.
Raw{"answer": "8.4", "explanation": "The clamp_v2 RFC, which introduced the clamp() function, was implemented in PHP 8.4."} | неверно верный: «8.6» | По данным владельца (wiki.php.net/rfc): clamp_v2 — 8.6; clamp() в 8.5.11 отсутствует (косвенное подтверждение). Дата-якорь делает клетку монотонной. |
VF-L2 3.2 c | PHP: 8.6+ and the future | RFC Context Managers v2 has already been adopted in PHP (as of 2026-11-07). | «no» Пояснение: There is no known adopted PHP RFC called 'Context Managers v2' as of the given date.
Raw{"answer": "no", "explanation": "There is no known adopted PHP RFC called 'Context Managers v2' as of the given date."} | верно | На 06.11.2026 — в обсуждении (создан 2026-10-23); не принят. |
VF-L3 2.39 c | PHP: 8.6+ and the future | RFC Bound-Erased Generic Types (generics) was declined in 2026. | «no» Пояснение: There is no known PHP RFC titled 'Bound-Erased Generic Types' that was declined in 2026; PHP has not had a generics RFC with that name in its public RFC process.
Raw{"answer": "no", "explanation": "There is no known PHP RFC titled 'Bound-Erased Generic Types' that was declined in 2026; PHP has not had a generics RFC with that name in its public RFC process."} | неверно верный: «yes» | Голосование завершилось 2026-06-28: отклонён (wiki.php.net/rfc). |
VF-L4 2.67 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, no RFC has been accepted to make ZTS (Zend Thread Safety) the default PHP build; NTS remains the default, and ZTS only makes the engine thread-safe for embedding, it does not enable multithreading of PHP scripts.
Raw{"answer": "no", "explanation": "As of 2026, no RFC has been accepted to make ZTS (Zend Thread Safety) the default PHP build; NTS remains the default, and ZTS only makes the engine thread-safe for embedding, it does not enable multithreading of PHP scripts."} | верно | Такого принятого RFC нет на дату якоря; якорь делает клетку монотонной — при принятии RFC позже клетка не перевернётся. |
VF-L5 2.4 c | PHP: 8.6+ and the future | As of PHP 8.5, generics (parameterized types) are still absent. | «yes» Пояснение: PHP has never implemented generics (parameterized types); as of PHP 8.5 they remain absent from the language.
Raw{"answer": "yes", "explanation": "PHP has never implemented generics (parameterized types); as of PHP 8.5 they remain absent from the language."} | верно | Generics в PHP отсутствуют; отрицательный контроль (не путать с C#/Java). |
VF-L6 8.97 c | PHP: 8.6+ and the future | As of 2026-11-07, the latest stable PHP version is 8.5, and PHP 8.6 has not been released yet (GA — 2026-11-19). | «yes» Пояснение: Following PHP's annual November release cycle, PHP 8.5 (released Nov 2025) would be the latest stable on 2026-11-07, with PHP 8.6 not yet having reached GA on 2026-11-19.
Raw{"answer": "yes", "explanation": "Following PHP's annual November release cycle, PHP 8.5 (released Nov 2025) would be the latest stable on 2026-11-07, with PHP 8.6 not yet having reached GA on 2026-11-19."} | верно | 8.5 — релиз осени 2025; 8.6 GA 19.11.2026 (wiki.php.net/todo/php86). Дата снимка — 06.11.2026. |
VF-L7 1.26 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 planned as a major internal rewrite but was cancelled; PHP 7.0 (December 2015) followed directly after PHP 5.6 (November 2014).
Raw{"answer": "yes", "explanation": "PHP 6 was planned as a major internal rewrite but was cancelled; PHP 7.0 (December 2015) followed directly after PHP 5.6 (November 2014)."} | верно | Исторический факт: ветка 6 не была релизнута. |
VF-L8 1.42 c | PHP: 8.6+ and the future | The RFC adding the #[\Deprecated] attribute to the core was adopted. | «no» Пояснение: PHP never adopted a #[\Deprecated] attribute in its core; deprecation is indicated via @deprecated docblocks, and no such RFC was accepted.
Raw{"answer": "no", "explanation": "PHP never adopted a #[\\Deprecated] attribute in its core; deprecation is indicated via @deprecated docblocks, and no such RFC was accepted."} | неверно верный: «yes» | #[\Deprecated] — принят, реализован в PHP 8.4. |
T25-L1 0.98 c | Clean architecture | The dependency rule of clean and onion architecture: inner layers know nothing about outer ones — dependencies point toward the center. | «yes» Пояснение: In clean and onion architecture, the dependency rule mandates that dependencies point inwards toward the core domain, meaning inner layers have no knowledge of outer layers.
Raw{"answer": "yes", "explanation": "In clean and onion architecture, the dependency rule mandates that dependencies point inwards toward the core domain, meaning inner layers have no knowledge of outer layers."} | верно | Чистая (Robert C. Martin), луковичная (Jeffrey Palermo) и гексагональная (ports & adapters) — варианты одной идеи: зависимости направлены внутрь, к домену. Слоями в проекте следит deptrac. |
T25-L2 1.24 c | Clean architecture | Domain entities import neither Doctrine nor Symfony — only the language and, possibly, the standard library. | «yes» Пояснение: In DDD/Clean Architecture, domain entities are pure PHP classes that must not depend on Doctrine or Symfony, keeping the domain layer framework-agnostic and easily testable.
Raw{"answer": "yes", "explanation": "In DDD/Clean Architecture, domain entities are pure PHP classes that must not depend on Doctrine or Symfony, keeping the domain layer framework-agnostic and easily testable."} | верно | Изоляция домена от инфраструктуры; deptrac в проекте как раз следит за слоями. |
T25-L3 1.42 c | Clean architecture | Controllers and Twig templates belong to the business-logic layer because they are the ones calling use cases. | «no» Пояснение: Controllers and Twig templates belong to the presentation (or infrastructure) layer; they call use cases in the application layer, but they themselves are not part of the business-logic layer.
Raw{"answer": "no", "explanation": "Controllers and Twig templates belong to the presentation (or infrastructure) layer; they call use cases in the application layer, but they themselves are not part of the business-logic layer."} | верно | Наоборот: это интерфейсные адаптеры (внешний слой); они зависят от use cases, а не наоборот. |
T25-L4 1.69 c | Clean architecture | What sits at the very center of the onion architecture? | «entities» Пояснение: In onion architecture, the very center is the Entities layer, containing the core domain objects and business rules that are independent of all other layers.
Raw{"answer": "Entities", "explanation": "In onion architecture, the very center is the Entities layer, containing the core domain objects and business rules that are independent of all other layers."} | неверно верный: «domain model» | Центральное кольцо — Domain Model: сущности и бизнес-правила без зависимостей; далее Domain Services → Application Services → Infrastructure/UI/Tests (Palermo). |
T25-L5 1.33 c | Clean architecture | Layer boundary violations can be caught automatically: a layer-dependency analyzer (e.g. deptrac) fails on a forbidden call. | «yes» Пояснение: deptrac is a static analysis tool for PHP that enforces layer boundaries by failing the build when a forbidden dependency (e.g., a Controller calling a Repository directly) is detected.
Raw{"answer": "yes", "explanation": "deptrac is a static analysis tool for PHP that enforces layer boundaries by failing the build when a forbidden dependency (e.g., a Controller calling a Repository directly) is detected."} | верно | depfile.yaml в проекте TasK: CI проверяет правила слоёв на каждом пайплайне. |
T25-L6 1.94 c | Clean architecture | A use case (interactor) may accept an HTTP request or an EntityManager as arguments — it is simpler that way. | «no» Пояснение: Use cases (interactors) should be framework-agnostic and accept domain-level data (DTOs, value objects) rather than infrastructure-specific types like HTTP requests or EntityManagers, to preserve loose coupling, testability, and reusability.
Raw{"answer": "no", "explanation": "Use cases (interactors) should be framework-agnostic and accept domain-level data (DTOs, value objects) rather than infrastructure-specific types like HTTP requests or EntityManagers, to preserve loose coupling, testability, and reusability."} | верно | Use case принимает DTO и порты; привязка к HTTP/ORM протекает инфраструктуру во внутренние слои. |
T25-L7 1.23 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 is the design pattern component that provides a collection of aggregates/entities and abstracts the storage/persistence mechanism behind a common interface.
Raw{"answer": "Repository", "explanation": "A Repository is the design pattern component that provides a collection of aggregates/entities and abstracts the storage/persistence mechanism behind a common interface."} | верно | Repository pattern (DDD/Evans); в проекте — Doctrine-репозитории за портами. |
T25-L8 2.18 c | Clean architecture | In clean architecture, swapping PostgreSQL for another database touches only the outer layer — the domain and use cases stay unchanged. | «yes» Пояснение: In Clean Architecture, the database driver is an outermost-layer detail; domain and use cases depend only on abstractions (ports/interfaces), so swapping the database requires changes only in the outer adapter/driver layer.
Raw{"answer": "yes", "explanation": "In Clean Architecture, the database driver is an outermost-layer detail; domain and use cases depend only on abstractions (ports/interfaces), so swapping the database requires changes only in the outer adapter/driver layer."} | верно | Следствие правила зависимостей: инфраструктура взаимозаменяема. |
T26-L1 1.27 c | DDD | In DDD, an aggregate is just another name for a database table. | «no» Пояснение: In DDD, an aggregate is a domain-level consistency boundary made of entities and value objects with a root entity; it is a modeling concept, not a persistence concept, and may span multiple tables or share tables with other aggregates.
Raw{"answer": "no", "explanation": "In DDD, an aggregate is a domain-level consistency boundary made of entities and value objects with a root entity; it is a modeling concept, not a persistence concept, and may span multiple tables or share tables with other aggregates."} | верно | Агрегат — кластер объектов с границей согласованности (транзакционной вокруг корня); таблица — деталь хранения. |
T26-L2 1.16 c | DDD | A Value Object is immutable and compared by the values of its fields, not by identity. | «yes» Пояснение: In Domain-Driven Design, a Value Object is immutable and two instances are considered equal if all their field values match, rather than being the same object in memory (identity).
Raw{"answer": "yes", "explanation": "In Domain-Driven Design, a Value Object is immutable and two instances are considered equal if all their field values match, rather than being the same object in memory (identity)."} | верно | Классика Evans: Money, Email; равенство структурное. |
T26-L3 1.76 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 external entry point of an aggregate through which all modifications must be made.
Raw{"answer": "Aggregate Root", "explanation": "In Domain-Driven Design, the Aggregate Root is the single external entry point of an aggregate through which all modifications must be made."} | верно | Aggregate Root: внешние объекты ссылаются только на корень; он защищает инварианты агрегата. |
T26-L4 1.09 c | DDD | In DDD, a repository is declared for an aggregate (its root), not for every entity. | «yes» Пояснение: In DDD, one Repository is defined per Aggregate Root, not per entity, to maintain aggregate invariants and encapsulation.
Raw{"answer": "yes", "explanation": "In DDD, one Repository is defined per Aggregate Root, not per entity, to maintain aggregate invariants and encapsulation."} | верно | Репозиторий корня хранит границу согласованности агрегата; вложенные сущности доступны только через корень. |
T26-L5 1.18 c | DDD | Ubiquitous language is the model's shared language common to developers and domain experts. | «yes» Пояснение: Ubiquitous Language in Domain-Driven Design is precisely the shared vocabulary used consistently by both developers and domain experts to describe the model.
Raw{"answer": "yes", "explanation": "Ubiquitous Language in Domain-Driven Design is precisely the shared vocabulary used consistently by both developers and domain experts to describe the model."} | верно | Evans: язык из требований переходит в имена классов и методов. |
T26-L6 4.39 c | DDD | What is the boundary called within which a model and its language are consistent, while outside the same words mean other models? | «frame» Пояснение: A frame is the conceptual/linguistic boundary within which a model and its terminology remain consistent, while outside that frame the same words map to different models or meanings.
Raw{"answer": "frame", "explanation": "A frame is the conceptual/linguistic boundary within which a model and its terminology remain consistent, while outside that frame the same words map to different models or meanings."} | неверно верный: «bounded context» | Bounded Context; «Заказ» в биллинге и в доставке — разные модели. |
T26-L7 1.19 c | DDD | An anemic model (objects with only getters/setters, logic in services) is the recommended DDD style. | «no» Пояснение: DDD advocates for rich domain models where entities and value objects encapsulate their own business logic, while anemic models are widely regarded as an anti-pattern in DDD.
Raw{"answer": "no", "explanation": "DDD advocates for rich domain models where entities and value objects encapsulate their own business logic, while anemic models are widely regarded as an anti-pattern in DDD."} | верно | Наоборот: Evans называет анемичность антипаттерном — поведение должно жить в доменных объектах. |
T26-L8 2.86 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 within which a domain model is valid, and the same real-world concept (e.g., 'Customer') is modeled as a distinct class in each context with its own structure and behavior.
Raw{"answer": "yes", "explanation": "In DDD, a bounded context defines a boundary within which a domain model is valid, and the same real-world concept (e.g., 'Customer') is modeled as a distinct class in each context with its own structure and behavior."} | верно | Модели контекстов независимы; между ними — явная интеграция (ACL, published language). |
T13-L1 1.18 c | Symfony | Services in the Symfony DI container are created lazily by default — on first use. | «yes» Пояснение: Symfony's DI container stores service definitions and only instantiates a service object when it is first requested (e.g., via $container->get()), which is the default lazy behavior.
Raw{"answer": "yes", "explanation": "Symfony's DI container stores service definitions and only instantiates a service object when it is first requested (e.g., via $container->get()), which is the default lazy behavior."} | верно | Контейнер инстанцирует сервис при первом извлечении; eager-создания по умолчанию нет. |
T13-L2 0.89 c | Symfony | Which Symfony console command lists all registered routes? | «debug:router» Пояснение: The Symfony console command 'debug:router' (run via 'php bin/console debug:router') lists all registered routes in the application.
Raw{"answer": "debug:router", "explanation": "The Symfony console command 'debug:router' (run via 'php bin/console debug:router') lists all registered routes in the application."} | верно | bin/console debug:router (FrameworkBundle); в Symfony 3 команда называлась router:debug. |
T13-L3 1.16 c | Symfony | Symfony autowiring requires manually declaring every service in services.yaml. | «no» Пояснение: The purpose of Symfony autowiring is to automatically resolve dependencies based on type hints, eliminating the need to manually declare and wire every service in services.yaml.
Raw{"answer": "no", "explanation": "The purpose of Symfony autowiring is to automatically resolve dependencies based on type hints, eliminating the need to manually declare and wire every service in services.yaml."} | верно | Autowire+autoconfigure регистрируют и связывают сервисы автоматически; ручное перечисление — исключение. |
T13-L4 1.14 c | Symfony | Twig templates are compiled into PHP classes and cached between requests. | «yes» Пояснение: Twig compiles templates into PHP classes and stores them in a cache directory so they are reused on subsequent requests until the source template changes.
Raw{"answer": "yes", "explanation": "Twig compiles templates into PHP classes and stores them in a cache directory so they are reused on subsequent requests until the source template changes."} | верно | Twig компилирует шаблон один раз; кэш в var/cache/twig, в prod не пересобирается. |
T13-L5 1.67 c | Symfony | In the Symfony dev environment the DI container is rebuilt only after tracked files change, not on every request. | «yes» Пояснение: In the Symfony dev environment, the container is cached and only recompiled when tracked files (config, service definitions, etc.) have changed since the last dump, not on every single request.
Raw{"answer": "yes", "explanation": "In the Symfony dev environment, the container is cached and only recompiled when tracked files (config, service definitions, etc.) have changed since the last dump, not on every single request."} | верно | Kernel проверяет freshness ресурсов (конфиги, классы); иначе переиспользуется кэш контейнера. |
T13-L6 0.82 c | Symfony | Which environment variable selects the active Symfony environment (dev/prod)? | «app_env» Пояснение: In Symfony, the APP_ENV environment variable determines the active environment (e.g., dev, prod, test).
Raw{"answer": "APP_ENV", "explanation": "In Symfony, the APP_ENV environment variable determines the active environment (e.g., dev, prod, test)."} | верно | APP_ENV в .env; APP_DEBUG — отдельный флаг отладки. |
T13-L7 1.04 c | Symfony | A controller method can be private — Symfony routing works with any method of the class. | «no» Пояснение: Symfony controller actions must be public methods; the router invokes them from outside the class, so private or protected methods cannot be used as routed actions.
Raw{"answer": "no", "explanation": "Symfony controller actions must be public methods; the router invokes them from outside the class, so private or protected methods cannot be used as routed actions."} | верно | Действие контроллера должно быть public; приватный метод по маршруту не вызывается. |
T13-L8 1.98 c | Symfony | Event subscribers always receive events before listeners, because the interface gives them priority. | «no» Пояснение: Priority is determined by the numeric priority value assigned at registration time, not by whether the handler is a subscriber or a listener; both can have any priority.
Raw{"answer": "no", "explanation": "Priority is determined by the numeric priority value assigned at registration time, not by whether the handler is a subscriber or a listener; both can have any priority."} | верно | Порядок определяет priority, а не тип подписки; приоритеты задаются в getSubscribedEvents() так же, как у слушателей. |
T22-L1 1.41 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 legacy guard authentication system, and the modern authenticator-based system (AuthenticatorInterface) is the standard for building authentication.
Raw{"answer": "yes", "explanation": "Symfony 6.0 removed the legacy guard authentication system, and the modern authenticator-based system (AuthenticatorInterface) is the standard for building authentication."} | верно | Guard объявлен устаревшим в 5.3 и удалён в 6.0; в проекте symfony/security-bundle 8.1. |
T22-L2 1.81 c | Symfony: Security and forms | Which Symfony attribute checks a role/permission right on a controller method (403 without it)? | «isgranted» Пояснение: The Symfony #[IsGranted] attribute is placed on a controller method to verify the user has a specific role or permission, throwing a 403 AccessDeniedException if not.
Raw{"answer": "IsGranted", "explanation": "The Symfony #[IsGranted] attribute is placed on a controller method to verify the user has a specific role or permission, throwing a 403 AccessDeniedException if not."} | верно | #[IsGranted('ROLE_ADMIN')]; атрибут из symfony/security-http. |
T22-L3 1.23 c | Symfony: Security and forms | Voters are Symfony's mechanism for checking access to a specific object: isGranted('EDIT', $post). | «yes» Пояснение: Voters (implementing VoteInterface) are Symfony's mechanism for object-level authorization, used via isGranted('EDIT', $post) to check permissions on a specific object.
Raw{"answer": "yes", "explanation": "Voters (implementing VoteInterface) are Symfony's mechanism for object-level authorization, used via isGranted('EDIT', $post) to check permissions on a specific object."} | верно | VoterInterface->vote(); docs Symfony — Voters. |
T22-L4 3.25 c | Symfony: Security and forms | In modern Symfony (7+) validation constraints are declared as PHP attributes (#[Assert\NotBlank]); doctrine annotations are no longer supported. | «yes» Пояснение: Symfony 7 (requiring PHP 8.2+) has removed support for the legacy doctrine/annotations style and mandates PHP 8 attributes (e.g., #[Assert\NotBlank]) for validation constraints.
Raw{"answer": "yes", "explanation": "Symfony 7 (requiring PHP 8.2+) has removed support for the legacy doctrine/annotations style and mandates PHP 8 attributes (e.g., #[Assert\\NotBlank]) for validation constraints."} | верно | Докблок-аннотации удалены в Symfony 7.0; стандарт — атрибуты. В проекте symfony/validator 8.1. |
T22-L5 0.94 c | Symfony: Security and forms | CSRF protection of Symfony forms is enabled by default: the form validates the token on submission. | «yes» Пояснение: Symfony forms include a CSRF token field by default and validate it on submission unless explicitly disabled with 'csrf_protection' => false.
Raw{"answer": "yes", "explanation": "Symfony forms include a CSRF token field by default and validate it on submission unless explicitly disabled with 'csrf_protection' => false."} | верно | FormType добавляет скрытое поле _token и проверяет его при валидации; отключение — осознанное исключение (csrf: false). |
T22-L6 1.51 c | Symfony: Security and forms | Form validation in Symfony runs server-side even if the client-side (HTML5) checks passed. | «yes» Пояснение: Symfony form constraints are always validated server-side; HTML5 client-side checks are merely a UX convenience and do not replace or prevent server-side validation.
Raw{"answer": "yes", "explanation": "Symfony form constraints are always validated server-side; HTML5 client-side checks are merely a UX convenience and do not replace or prevent server-side validation."} | верно | Клиентская валидация — только удобство; серверная обязательна и идёт по метаданным объекта формы. |
T22-L7 0.74 c | Symfony: Security and forms | Which Symfony maker command generates a form class (FormType)? | «maker:form» Пояснение: The Symfony MakerBundle command `php bin/console maker:form` generates a FormType class for building forms.
Raw{"answer": "maker:form", "explanation": "The Symfony MakerBundle command `php bin/console maker:form` generates a FormType class for building forms."} | неверно верный: «make:form» | bin/console make:form (symfony/maker-bundle — в проекте). |
T22-L8 1.22 c | Symfony: Security and forms | Symfony stores the user's password in the session in plain text. | «no» Пояснение: Symfony stores only the user's identity (e.g., username or ID) in the session to maintain the authenticated state; the password is never stored in the session.
Raw{"answer": "no", "explanation": "Symfony stores only the user's identity (e.g., username or ID) in the session to maintain the authenticated state; the password is never stored in the session."} | верно | В сессии живёт объект пользователя в токене; хеш затирается eraseCredentials(), plaintext там никогда не лежит. |
T23-L1 0.95 c | Symfony: configuration and services | Symfony bundle configuration lives in config/packages — one file per bundle or topic. | «yes» Пояснение: In modern Symfony, bundle configurations are stored as individual YAML files in the config/packages/ directory, one per bundle or topic.
Raw{"answer": "yes", "explanation": "In modern Symfony, bundle configurations are stored as individual YAML files in the config/packages/ directory, one per bundle or topic."} | верно | Стандартная структура (config/packages/*.yaml); перегрузка — config/packages/<env>. |
T23-L2 2.13 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» Пояснение: In Symfony (a common PHP framework), the .env file with development defaults is committed to the repo, while .env.local holds real secrets and is listed in .gitignore so it is never committed.
Raw{"answer": "yes", "explanation": "In Symfony (a common PHP framework), the .env file with development defaults is committed to the repo, while .env.local holds real secrets and is listed in .gitignore so it is never committed."} | верно | symfony/dotenv: .env — общий безопасный набор значений; локальные секреты — .env.local (gitignored) или secrets-хранилище. |
T23-L3 0.69 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 2.39 c | Symfony: configuration and services | The Symfony container allows changing parameters at runtime: $container->setParameter() works from a controller. | «no» Пояснение: In Symfony the container is frozen once the kernel boots, so calling setParameter() from a controller (at runtime) will throw a LogicException; parameters cannot be changed after the container is compiled and frozen.
Raw{"answer": "no", "explanation": "In Symfony the container is frozen once the kernel boots, so calling setParameter() from a controller (at runtime) will throw a LogicException; parameters cannot be changed after the container is compiled and frozen."} | верно | Контейнер компилируется и замораживается; runtime-значения — только через переменные окружения. |
T23-L5 0.9 c | Symfony: configuration and services | By default, Symfony services are public (public: true) — you can fetch them directly from the container. | «no» Пояснение: Since Symfony 4.0, services are private by default (public: false); you must explicitly set public: true to retrieve them from the container.
Raw{"answer": "no", "explanation": "Since Symfony 4.0, services are private by default (public: false); you must explicitly set public: true to retrieve them from the container."} | верно | С Symfony 4.0 сервисы по умолчанию private: инжектятся через autowiring; $container->get() — только для публичных. |
T23-L6 1.85 c | Symfony: configuration and services | Without a config file in config/packages a bundle will not work — configuration is mandatory for every bundle. | «no» Пояснение: Many Symfony bundles work perfectly fine without a dedicated config file in config/packages, as they provide sensible defaults or require no configuration at all.
Raw{"answer": "no", "explanation": "Many Symfony bundles work perfectly fine without a dedicated config file in config/packages, as they provide sensible defaults or require no configuration at all."} | верно | У бандлов есть встроенные умолчания (Extension); конфиг нужен только для отклонений от них. |
T23-L7 0.71 c | Symfony: configuration and services | Environment variable values are injected into services.yaml using the %env(VAR)% syntax. | «yes» Пояснение: In Symfony, environment variables are referenced in configuration files such as services.yaml using the %env(VAR_NAME)% syntax.
Raw{"answer": "yes", "explanation": "In Symfony, environment variables are referenced in configuration files such as services.yaml using the %env(VAR_NAME)% syntax."} | верно | %env(...)% резолвится в рантайме env-процессорами; docs — Env Var Processors. |
T23-L8 0.84 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, enabling the profiler and Twig debug helpers like dump() and dd().
Raw{"answer": "APP_DEBUG", "explanation": "The APP_DEBUG environment variable in Symfony controls debug mode, enabling the profiler and Twig debug helpers like dump() and dd()."} | верно | APP_DEBUG=1 (в .env dev-окружения); окружение выбирает APP_ENV — см. T13-L6. |
T16-L1 0.97 c | Symfony: Messenger | A single message in Symfony Messenger can only have one handler. | «no» Пояснение: Symfony Messenger allows multiple handlers to be registered for the same message; they are invoked in order of their priority.
Raw{"answer": "no", "explanation": "Symfony Messenger allows multiple handlers to be registered for the same message; they are invoked in order of their priority."} | верно | Messenger вызывает все хендлеры, подписанные на класс сообщения (docs — Multiple Handlers). |
T16-L2 1.3 c | Symfony: Messenger | The sync transport in Messenger queues the message for a worker, just like async. | «no» Пояснение: The sync transport handles the message immediately in the current process without queuing it for a worker; only async transports queue messages for a worker to pick up later.
Raw{"answer": "no", "explanation": "The sync transport handles the message immediately in the current process without queuing it for a worker; only async transports queue messages for a worker to pick up later."} | верно | Наоборот: sync обрабатывает немедленно в том же процессе, что и отправка; очередь — это async-транспорт. |
T16-L3 0.79 c | Symfony: Messenger | Which console command starts the worker that processes Messenger queue messages? | «messenger:consume» Пояснение: In Symfony, the `messenger:consume` console command starts a worker that processes messages from the Messenger component's queues.
Raw{"answer": "messenger:consume", "explanation": "In Symfony, the `messenger:consume` console command starts a worker that processes messages from the Messenger component's queues."} | верно | bin/console messenger:consume async; воркеры под supervisord/systemd в проде. |
T16-L4 1.1 c | Symfony: Messenger | Retries for failed messages (retry_strategy) are configured per Messenger transport. | «yes» Пояснение: In Symfony Messenger, the retry_strategy (max_retries, multiplier, delay, etc.) is defined under each individual transport in the framework configuration.
Raw{"answer": "yes", "explanation": "In Symfony Messenger, the retry_strategy (max_retries, multiplier, delay, etc.) is defined under each individual transport in the framework configuration."} | верно | retry_strategy на транспорте: max_retries, delay, multiplier; docs — Failed Messages & Retries. |
T16-L5 1.6 c | Symfony: Messenger | By default, Messenger serializes messages to JSON. | «yes» Пояснение: Symfony Messenger uses JSON as the default serialization format for messages when no custom serializer is configured.
Raw{"answer": "yes", "explanation": "Symfony Messenger uses JSON as the default serialization format for messages when no custom serializer is configured."} | неверно верный: «no» | Дефолтный сериализатор — PhpSerializer (serialize()); JSON-сериализатор включается отдельно. |
T16-L6 1.69 c | Symfony: Messenger | Symfony Scheduler produces messages on a schedule and dispatches them through Messenger. | «yes» Пояснение: Symfony Scheduler (introduced in 6.3) generates messages according to a defined schedule and dispatches them via the Messenger component for asynchronous processing.
Raw{"answer": "yes", "explanation": "Symfony Scheduler (introduced in 6.3) generates messages according to a defined schedule and dispatches them via the Messenger component for asynchronous processing."} | верно | Schedule → RecurringMessage → шина Messenger; docs — Scheduler. |
T16-L7 1.01 c | Symfony: Messenger | Which built-in Messenger transport stores messages in database tables via Doctrine? | «doctrine» Пояснение: Symfony Messenger's 'doctrine' transport persists messages in database tables using Doctrine ORM/DBAL.
Raw{"answer": "doctrine", "explanation": "Symfony Messenger's 'doctrine' transport persists messages in database tables using Doctrine ORM/DBAL."} | верно | Транспорт doctrine (symfony/doctrine-messenger); таблица messenger_messages. В проекте стоит amqp-messenger + doctrine-messenger. |
T16-L8 0.92 c | Symfony: Messenger | The Messenger pipeline can be extended with custom middleware, placed before or after the built-in ones. | «yes» Пояснение: Symfony Messenger allows you to register custom middleware in the pipeline, and you can place them before or after the built-in middleware by configuring their order in the service container.
Raw{"answer": "yes", "explanation": "Symfony Messenger allows you to register custom middleware in the pipeline, and you can place them before or after the built-in middleware by configuring their order in the service container."} | верно | messenger.bus.*.middleware в yaml; docs — Middleware. |
T28-L1 4.05 c | Symfony: versions | Symfony major releases come every two years, minor ones every six months (in May and November). | «no» Пояснение: Symfony major releases come approximately every year, not every two years, while minor releases do come every six months in May and November.
Raw{"answer": "no", "explanation": "Symfony major releases come approximately every year, not every two years, while minor releases do come every six months in May and November."} | неверно верный: «yes» | Стандартный релизный цикл: 8.0 — ноябрь 2025, 8.1 — май 2026, 8.2 — ноябрь 2026. |
T28-L2 2.83 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, following the pattern of each major Symfony version bumping the required PHP version.
Raw{"answer": "8.4", "explanation": "Symfony 8 requires a minimum PHP version of 8.4, following the pattern of each major Symfony version bumping the required PHP version."} | верно | Symfony 8.0 поднял требование до PHP >= 8.4.1 (в vendor проекта: "php": ">=8.4.1"). |
T28-L3 1.92 c | Symfony: versions | Symfony 7.0 kept support for docblock annotations (validation, routes). | «no» Пояснение: Symfony 7.0 removed support for docblock annotations; PHP attributes (or YAML/XML) are the only supported ways to define validation constraints and routes.
Raw{"answer": "no", "explanation": "Symfony 7.0 removed support for docblock annotations; PHP attributes (or YAML/XML) are the only supported ways to define validation constraints and routes."} | верно | Наоборот: в 7.0 аннотации удалены — только PHP-атрибуты (#[Route], #[Assert\NotBlank]). |
T28-L4 1.63 c | Symfony: versions | AssetMapper manages CSS/JS without node or webpack — via importmap.php. | «yes» Пояснение: Symfony's AssetMapper component resolves CSS/JS imports natively in PHP and is configured through the importmap.php file, eliminating the need for Node.js or webpack.
Raw{"answer": "yes", "explanation": "Symfony's AssetMapper component resolves CSS/JS imports natively in PHP and is configured through the importmap.php file, eliminating the need for Node.js or webpack."} | верно | symfony/asset-mapper (с 6.3, стандарт с 7.x); в проекте — importmap.php в корне и asset-mapper 8.1. |
T28-L5 4.0 c | Symfony: versions | Symfony 6.4 is a regular release without long-term support. | «no» Пояснение: Symfony 6.4 is one of the long-term support (LTS) releases within the 6.x cycle; the .4 minor releases are specifically designated for extended production support.
Raw{"answer": "no", "explanation": "Symfony 6.4 is one of the long-term support (LTS) releases within the 6.x cycle; the .4 minor releases are specifically designated for extended production support."} | верно | Наоборот: 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» Пояснение: Symfony's deprecation policy explicitly states that features deprecated in one major version are removed in the next major version; that is the entire purpose of the deprecation cycle.
Raw{"answer": "no", "explanation": "Symfony's deprecation policy explicitly states that features deprecated in one major version are removed in the next major version; that is the entire purpose of the deprecation cycle."} | верно | Наоборот: мажорный релиз удаляет всё устаревшее (7.0 убрал деприкейшены 6.x, 8.0 — 7.x). |
T28-L7 1.02 c | Symfony: versions | Every Symfony major release is accompanied by an UPGRADE guide listing the changes. | «yes» Пояснение: Symfony publishes UPGRADE guides (e.g., UPGRADE-5.0.md, UPGRADE-6.0.md) with every major release to document breaking changes and deprecations.
Raw{"answer": "yes", "explanation": "Symfony publishes UPGRADE guides (e.g., UPGRADE-5.0.md, UPGRADE-6.0.md) with every major release to document breaking changes and deprecations."} | верно | UPGRADE-7.0.md, UPGRADE-8.0.md в репозитории symfony/symfony. |
T28-L8 3.77 c | Symfony: versions | Which Symfony component manages assets and the importmap without node/webpack? | «assetmapper» Пояснение: Symfony's AssetMapper component (introduced in Symfony 7) manages frontend assets and, together with the ImportMap component, eliminates the need for Node.js/webpack.
Raw{"answer": "AssetMapper", "explanation": "Symfony's AssetMapper component (introduced in Symfony 7) manages frontend assets and, together with the ImportMap component, eliminates the need for Node.js/webpack."} | верно | symfony/asset-mapper 8.1 — в проекте. |
T29-L1 6.25 c | Symfony: 8.2 and beyond | As of 2026-11-07, Symfony 8.2 has already been released. | «no» Пояснение: Based on Symfony's typical release cycle (major versions in November, minor versions every ~6 months), Symfony 8.2 would not have been released by early November 2026.
Raw{"answer": "no", "explanation": "Based on Symfony's typical release cycle (major versions in November, minor versions every ~6 months), Symfony 8.2 would not have been released by early November 2026."} | верно | Наоборот: 8.2 ещё не выпущена — релиз в конце ноября 2026; последняя стабильная — 8.1. |
T29-L2 9.38 c | Symfony: 8.2 and beyond | As of 2026-11-07, Symfony 8.2 is scheduled for November 2026, following the usual six-month cycle. | «no» Пояснение: Following Symfony's six-month release cycle, Symfony 8.2 would not be reached until approximately 2028; November 2026 would correspond to a Symfony 7.x release (e.g., 7.3).
Raw{"answer": "no", "explanation": "Following Symfony's six-month release cycle, Symfony 8.2 would not be reached until approximately 2028; November 2026 would correspond to a Symfony 7.x release (e.g., 7.3)."} | неверно верный: «yes» | Политика релизов: 8.1 — май 2026, 8.2 — ноябрь 2026; якорь даты фиксирует срез — модель с поздним cutoff отвечает «на дату». |
T29-L3 1.05 c | Symfony: 8.2 and beyond | Which Symfony version comes after 8.1 (as of 2026-11-07)? | «8.2» Пояснение: Symfony versions increment the minor number sequentially, so the version immediately following 8.1 is 8.2.
Raw{"answer": "8.2", "explanation": "Symfony versions increment the minor number sequentially, so the version immediately following 8.1 is 8.2."} | верно | 8.2 — следующий минорный релиз (ноябрь 2026); после его выхода проект переходит с 8.1.* на 8.2.*. |
T29-L4 2.26 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), not a major one; minor releases follow semver and do not introduce breaking API changes requiring rewrites.
Raw{"answer": "no", "explanation": "Symfony 8.2 is a minor release (x.2), not a major one; minor releases follow semver and do not introduce breaking API changes requiring rewrites."} | верно | Наоборот: 8.2 — минорный релиз; новые возможности без поломки обратной совместимости. Мажор — 9.0. |
T29-L5 1.57 c | Symfony: 8.2 and beyond | Updating within a major branch (8.1 → 8.2) should not require code changes — backward compatibility is preserved. | «yes» Пояснение: PHP follows a compatibility promise for minor version bumps (8.1 → 8.2), meaning no breaking changes are introduced and existing code should continue to work without modifications.
Raw{"answer": "yes", "explanation": "PHP follows a compatibility promise for minor version bumps (8.1 → 8.2), meaning no breaking changes are introduced and existing code should continue to work without modifications."} | верно | Политика Symfony: минорные релизы обратно совместимы; BC-break допустим только в мажорных. |
T29-L6 4.02 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 of 5 minor releases per major branch (e.g., 5.0–5.4, 6.0–6.4), so the 8.x branch ends at 8.4 before Symfony 9.0.
Raw{"answer": "8.4", "explanation": "Symfony follows a pattern of 5 minor releases per major branch (e.g., 5.0–5.4, 6.0–6.4), so the 8.x branch ends at 8.4 before Symfony 9.0."} | верно | По циклу: 8.2 (ноя 2026), 8.3 (май 2027), 8.4 (ноя 2027, вместе с 9.0) — как 6.4 выходила вместе с 7.0. |
T29-L7 2.11 c | Symfony: 8.2 and beyond | Symfony 8.2 will require PHP 8.5 — you would have to upgrade PHP along with it. | «no» Пояснение: There is no confirmed Symfony 8.2 release requiring PHP 8.5; this statement is not based on an actual announced version requirement.
Raw{"answer": "no", "explanation": "There is no confirmed Symfony 8.2 release requiring PHP 8.5; this statement is not based on an actual announced version requirement."} | верно | Наоборот: минорные релизы не поднимают требования PHP; для всей ветки 8.x остаётся PHP >= 8.4. |
T29-L8 2.85 c | Symfony: 8.2 and beyond | Deprecations added in the 8.x branch will not be removed before Symfony 9.0. | «yes» Пояснение: Symfony's deprecation policy states that deprecations introduced in the 8.x series are removed in the next major version (9.0), meaning they are not removed before 9.0.
Raw{"answer": "yes", "explanation": "Symfony's deprecation policy states that deprecations introduced in the 8.x series are removed in the next major version (9.0), meaning they are not removed before 9.0."} | верно | Политика: деприкейшены живут до следующего мажора; 9.0 — ноябрь 2027. |
T21-L1 1.69 c | Twig | Inside {{ }}, Twig allows calling arbitrary PHP code directly. | «no» Пояснение: Twig's {{ }} syntax only allows its own expressions (variables, filters, functions, method calls on whitelisted objects); it does not permit arbitrary raw PHP code execution.
Raw{"answer": "no", "explanation": "Twig's {{ }} syntax only allows its own expressions (variables, filters, functions, method calls on whitelisted objects); it does not permit arbitrary raw PHP code execution."} | верно | Twig — DSL: только разрешённые окружением функции/фильтры; произвольный PHP не исполняется. |
T21-L2 0.96 c | Twig | By default, Twig auto-escapes printed variables. | «yes» Пояснение: Twig has auto-escaping enabled by default (using the 'html' strategy) to prevent XSS attacks on all printed variables.
Raw{"answer": "yes", "explanation": "Twig has auto-escaping enabled by default (using the 'html' strategy) to prevent XSS attacks on all printed variables."} | верно | Autoescape включён по умолчанию; {{ '<b>' }} → <b>. Проверено на Twig 3.30. |
T21-L3 0.97 c | Twig | The Twig |e filter escapes a string for safe output in an HTML context. | «yes» Пояснение: The Twig |e (escape) filter defaults to HTML context, escaping characters like <, >, &, ", and ' for safe HTML output.
Raw{"answer": "yes", "explanation": "The Twig |e (escape) filter defaults to HTML context, escaping characters like <, >, &, \", and ' for safe HTML output."} | верно | |e ('html') по умолчанию; есть контексты js/url/css. От SQL-инъекций он не защищает — это задача подготовленных запросов Doctrine. |
T21-L4 2.04 c | Twig | Which filter from twig/intl-extra formats a number according to a locale? | «locale_number» Пояснение: The twig/intl-extra package provides the locale_number filter, which formats a number according to a given locale using PHP's intl NumberFormatter.
Raw{"answer": "locale_number", "explanation": "The twig/intl-extra package provides the locale_number filter, which formats a number according to a given locale using PHP's intl NumberFormatter."} | неверно верный: «format_number» | |format_number(locale=...) из IntlExtension (twig/intl-extra есть в проекте). Проверено на Twig 3.30: 12345.6 → 12 345,6 (ru). |
T21-L5 2.01 c | Twig | The |raw filter disables auto-escaping for the value. | «yes» Пояснение: In Twig (a PHP templating engine), the |raw (or |safe) filter marks a value as trusted and disables auto-escaping.
Raw{"answer": "yes", "explanation": "In Twig (a PHP templating engine), the |raw (or |safe) filter marks a value as trusted and disables auto-escaping."} | верно | {{ x|raw }} выводит HTML как есть; опасно с пользовательскими данными. Проверено на Twig 3.30. |
T21-L6 1.08 c | Twig | In Twig, {{ }} prints an expression value, while {% %} executes tags — conditions, loops, set. | «yes» Пояснение: In Twig, double curly braces {{ }} are for outputting expression values, while double percent signs {% %} are for control structures and tags like if, for, and set.
Raw{"answer": "yes", "explanation": "In Twig, double curly braces {{ }} are for outputting expression values, while double percent signs {% %} are for control structures and tags like if, for, and set."} | верно | Два блока синтаксиса Twig: вывод (echo) против логики. |
T21-L7 1.03 c | Twig | In Twig you cannot declare a variable inside a template — values only come from the controller. | «no» Пояснение: Twig allows you to declare variables inside a template using the {% set %} tag, e.g. {% set message = 'Hello' %}.
Raw{"answer": "no", "explanation": "Twig allows you to declare variables inside a template using the {% set %} tag, e.g. {% set message = 'Hello' %}."} | верно | {% set y = ... %} объявляет переменную в шаблоне. Проверено на Twig 3.30. |
T21-L8 0.72 c | Twig | Which Twig function dumps the debug structure of a variable (array, object)? | «dump» Пояснение: Twig's `dump()` function outputs the debug structure of a variable (array, object, etc.), similar to PHP's var_dump().
Raw{"answer": "dump", "explanation": "Twig's `dump()` function outputs the debug structure of a variable (array, object, etc.), similar to PHP's var_dump()."} | верно | {{ dump(x) }} (DebugExtension; в Symfony доступна в dev-окружении). |
T24-L1 1.21 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 system, etc.), not a Single Page Application framework like React, Angular, or Vue.
Raw{"answer": "yes", "explanation": "Bootstrap is a CSS/JS library providing ready-made UI components (buttons, modals, grid system, etc.), not a Single Page Application framework like React, Angular, or Vue."} | верно | Компоненты и утилиты поверх вашего HTML; SPA-фреймворки (React/Vue) — другой класс инструментов. В проекте vendored 5.3.3. |
T24-L2 1.0 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 that adjusts its max-width at each breakpoint (sm, md, lg, xl, xxl).
Raw{"answer": "container", "explanation": "The .container class in Bootstrap provides a responsive fixed-width container that adjusts its max-width at each breakpoint (sm, md, lg, xl, xxl)."} | верно | .container (фиксированная макс-ширина по брейкпоинтам) vs .container-fluid (на всю ширину). |
T24-L3 1.12 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 CSS Flexbox rather than floats.
Raw{"answer": "no", "explanation": "The Bootstrap grid splits a row into 12 columns (not 16), and modern Bootstrap (v4+) uses CSS Flexbox rather than floats."} | верно | Наоборот: flexbox (с Bootstrap 4) и 12 колонок; float-сетка — это Bootstrap 3. |
T24-L4 3.05 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 six breakpoints (xs, sm, md, lg, xl, xxl), but xs has no infix in class names, leaving exactly five named infixes: sm, md, lg, xl, xxl.
Raw{"answer": "yes", "explanation": "Bootstrap 5 defines six breakpoints (xs, sm, md, lg, xl, xxl), but xs has no infix in class names, leaving exactly five named infixes: sm, md, lg, xl, xxl."} | верно | Тиров всего шесть: xs (без инфикса) + пять именованных (576/768/992/1200/1400 px). |
T24-L5 1.22 c | Bootstrap | Utilities like .mt-3 or .px-2 use the spacing scale: the number is a multiple of $spacer. | «yes» Пояснение: In Bootstrap, utilities like .mt-3 and .px-2 calculate their value as the number multiplied by the $spacer variable (e.g., margin-top: calc($spacer * 3)).
Raw{"answer": "yes", "explanation": "In Bootstrap, utilities like .mt-3 and .px-2 calculate their value as the number multiplied by the $spacer variable (e.g., margin-top: calc($spacer * 3))."} | неверно верный: «no» | Spacing utilities; $spacer = 1rem. |
T24-L6 1.06 c | Bootstrap | Which Bootstrap 5 data attribute enables an interactive component (e.g. dropdown) on an element? | «data-bs-toggle» Пояснение: In Bootstrap 5, the data-bs-toggle attribute (e.g., data-bs-toggle="dropdown") is what activates/enables an interactive component on an element.
Raw{"answer": "data-bs-toggle", "explanation": "In Bootstrap 5, the data-bs-toggle attribute (e.g., data-bs-toggle=\"dropdown\") is what activates/enables an interactive component on an element."} | верно | data-bs-toggle="dropdown" и т.п.; в Bootstrap 4 атрибут назывался data-toggle. |
T24-L7 0.65 c | Bootstrap | Bootstrap 5 components work without jQuery — in plain vanilla JS. | «yes» Пояснение: Bootstrap 5 removed its jQuery dependency and all interactive components are powered by vanilla JavaScript (with Popper.js for tooltips/popovers).
Raw{"answer": "yes", "explanation": "Bootstrap 5 removed its jQuery dependency and all interactive components are powered by vanilla JavaScript (with Popper.js for tooltips/popovers)."} | верно | jQuery удалён в Bootstrap 5.0: data-bs-* атрибуты и JS API. В проекте vendored 5.3.3. |
T24-L8 3.09 c | Bootstrap | Dark mode in Bootstrap is enabled with a .dark class on the root element. | «no» Пояснение: In Bootstrap 5, dark mode is enabled by setting 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 by setting 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.44 c | Doctrine | Doctrine ORM creates database tables on the fly the first time an entity is used at runtime. | «no» Пояснение: Doctrine ORM does not auto-create tables at runtime; you must explicitly generate the schema via SchemaTool or run Doctrine Migrations to create or alter tables.
Raw{"answer": "no", "explanation": "Doctrine ORM does not auto-create tables at runtime; you must explicitly generate the schema via SchemaTool or run Doctrine Migrations to create or alter tables."} | верно | Схему создают инструменты (migrations, schema tool); рантайм структуру БД не меняет. |
T14-L2 1.12 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 the SQL is only executed upon flush().
Raw{"answer": "persist", "explanation": "EntityManager::persist() marks a new entity as managed and schedules an INSERT, but the SQL is only executed upon flush()."} | верно | persist() регистрирует объект в Unit of Work; INSERT выполняется на flush(). |
T14-L3 1.45 c | Doctrine | In Doctrine ORM 3, the EntityManager::merge() method exists and makes the passed object managed. | «no» Пояснение: In Doctrine ORM 3, the EntityManager::merge() method was removed entirely; it no longer exists.
Raw{"answer": "no", "explanation": "In Doctrine ORM 3, the EntityManager::merge() method was removed entirely; it no longer exists."} | верно | В ORM 3 merge() удалён (в vendor проекта 3.7.6 метода нет); в Doctrine 2.x merge() возвращал управляемую копию. Версия зафиксирована — ORM 3. |
T14-L4 0.89 c | Doctrine | DQL queries are written in terms of entities and their fields, not tables and columns. | «yes» Пояснение: DQL (Doctrine Query Language) operates at the entity level, referencing entities and their mapped fields/properties rather than raw database tables and columns.
Raw{"answer": "yes", "explanation": "DQL (Doctrine Query Language) operates at the entity level, referencing entities and their mapped fields/properties rather than raw database tables and columns."} | верно | Doctrine транслирует DQL в SQL; docs — DQL (Doctrine Query Language). |
T14-L5 0.92 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 ID is found.
Raw{"answer": "null", "explanation": "Doctrine's Repository::find() method returns null when no entity with the given ID is found."} | верно | find() возвращает null, если объект не найден (docs Repository methods). |
T14-L6 2.38 c | Doctrine | DoctrineBundle in Symfony automatically calls flush() at the end of every request. | «no» Пояснение: DoctrineBundle in Symfony does not automatically call flush() at the end of every request; you must explicitly call $em->flush() to persist changes to the database.
Raw{"answer": "no", "explanation": "DoctrineBundle in Symfony does not automatically call flush() at the end of every request; you must explicitly call $em->flush() to persist changes to the database."} | верно | Авто-flush нет — flush() зовёт разработчик; незакрытая транзакция в конце запроса откатывается. |
T14-L7 1.42 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 tracks all managed entities and detects property changes during flush(), generating an UPDATE without requiring a new persist() call.
Raw{"answer": "yes", "explanation": "The Unit of Work tracks all managed entities and detects property changes during flush(), generating an UPDATE without requiring a new persist() call."} | верно | Dirty checking сравнивает снимки свойств; persist нужен только новым/отсоединённым объектам. |
T14-L8 1.01 c | Doctrine | remove() executes the SQL DELETE immediately, without waiting for flush(). | «no» Пояснение: In Doctrine ORM, remove() only schedules the entity for deletion in the Unit of Work; the actual SQL DELETE is executed when flush() is called.
Raw{"answer": "no", "explanation": "In Doctrine ORM, remove() only schedules the entity for deletion in the Unit of Work; the actual SQL DELETE is executed when flush() is called."} | верно | remove() планирует удаление в Unit of Work; DELETE выполняется на flush() (docs — Deleting Objects). |
T15-L1 1.15 c | PostgreSQL | PostgreSQL uses MVCC, therefore readers block writers and writers block readers. | «no» Пояснение: MVCC in PostgreSQL is designed so that readers do NOT block writers and writers do NOT block readers; each sees a consistent snapshot via multiple row versions.
Raw{"answer": "no", "explanation": "MVCC in PostgreSQL is designed so that readers do NOT block writers and writers do NOT block readers; each sees a consistent snapshot via multiple row versions."} | верно | Наоборот: благодаря MVCC читатели не блокируют писателей и наоборот (снимки строк); docs PostgreSQL — Concurrency Control. |
T15-L2 1.11 c | PostgreSQL | Which SQL command shows a query's execution plan without executing the query? | «explain» Пояснение: The EXPLAIN SQL command displays a query's execution plan (access type, possible keys, etc.) without actually running the query.
Raw{"answer": "EXPLAIN", "explanation": "The EXPLAIN SQL command displays a query's execution plan (access type, possible keys, etc.) without actually running the query."} | верно | EXPLAIN без ANALYZE только строит план; проверено на PostgreSQL 17.7. |
T15-L3 2.81 c | PostgreSQL | SERIAL and GENERATED ... AS IDENTITY are just two names for the same mechanism. | «no» Пояснение: SERIAL creates a separate sequence object plus a default, while GENERATED AS IDENTITY is a column-level attribute (SQL standard); they differ in management, semantics (ALWAYS vs BY DEFAULT), and object lifecycle.
Raw{"answer": "no", "explanation": "SERIAL creates a separate sequence object plus a default, while GENERATED AS IDENTITY is a column-level attribute (SQL standard); they differ in management, semantics (ALWAYS vs BY DEFAULT), and object lifecycle."} | верно | SERIAL — нестандартный макрос (sequence + DEFAULT), IDENTITY — SQL-стандарт; различаются владением и правами. Оба есть в PG 17 (проверено). |
T15-L4 2.04 c | PostgreSQL | By default, a PostgreSQL UNIQUE constraint allows only one row with NULL in the column. | «no» Пояснение: By default, PostgreSQL treats NULL values as distinct from each other in a UNIQUE constraint, so multiple rows can have NULL in that column.
Raw{"answer": "no", "explanation": "By default, PostgreSQL treats NULL values as distinct from each other in a UNIQUE constraint, so multiple rows can have NULL in that column."} | верно | Наоборот: NULLS DISTINCT по умолчанию — несколько NULL допустимы; NULLS NOT DISTINCT — опция с PG 15. Проверено на PG 17.7. |
T15-L5 0.65 c | PostgreSQL | Which PostgreSQL aggregate function concatenates strings with a separator? | «string_agg» Пояснение: PostgreSQL's string_agg() aggregate function concatenates strings together with a specified separator.
Raw{"answer": "string_agg", "explanation": "PostgreSQL's string_agg() aggregate function concatenates strings together with a specified separator."} | верно | string_agg(значение, разделитель); проверено на PostgreSQL 17.7. |
T15-L6 1.51 c | PostgreSQL | Plain VACUUM returns the space occupied by dead tuples to the operating system. | «no» Пояснение: Plain VACUUM marks space occupied by dead tuples as reusable within the table but does not return it to the operating system; only VACUUM FULL rewrites the table and returns disk space to the OS.
Raw{"answer": "no", "explanation": "Plain VACUUM marks space occupied by dead tuples as reusable within the table but does not return it to the operating system; only VACUUM FULL rewrites the table and returns disk space to the OS."} | верно | VACUUM помечает место для переиспользования внутри таблицы; ОС его возвращает только VACUUM FULL (с эксклюзивной блокировкой). |
T15-L7 0.66 c | PostgreSQL | Which keyword in a window function definition partitions rows into groups the function is computed over? | «partition» Пояснение: In a SQL window function, the PARTITION BY clause divides rows into groups over which the window function is computed.
Raw{"answer": "PARTITION", "explanation": "In a SQL window function, the PARTITION BY clause divides rows into groups over which the window function is computed."} | неверно верный: «partition by» | OVER (PARTITION BY ...); проверено на PostgreSQL 17.7. |
T15-L8 1.17 c | PostgreSQL | The READ COMMITTED isolation level protects against non-repeatable reads. | «no» Пояснение: READ COMMITTED only prevents dirty reads; non-repeatable reads require at least the REPEATABLE READ isolation level to be prevented.
Raw{"answer": "no", "explanation": "READ COMMITTED only prevents dirty reads; non-repeatable reads require at least the REPEATABLE READ isolation level to be prevented."} | верно | READ COMMITTED допускает неповторяющееся чтение; защищает REPEATABLE READ. Проверено: SHOW transaction_isolation → read committed. |
T17-L1 0.87 c | PostgreSQL: transactions and indexes | By default, PostgreSQL wraps each single SQL statement in its own implicit transaction (autocommit). | «yes» Пояснение: By default, PostgreSQL runs each SQL statement in its own implicit transaction (autocommit mode) unless you explicitly begin a transaction with BEGIN/START TRANSACTION.
Raw{"answer": "yes", "explanation": "By default, PostgreSQL runs each SQL statement in its own implicit transaction (autocommit mode) unless you explicitly begin a transaction with BEGIN/START TRANSACTION."} | верно | Без BEGIN каждый оператор коммитится сам; docs PostgreSQL — Transactions. Проверено на PG 17. |
T17-L2 0.56 c | PostgreSQL: transactions and indexes | Which SQL command ends a transaction, committing all its changes? | «commit» Пояснение: The COMMIT SQL command ends a transaction and permanently saves all changes made within it.
Raw{"answer": "COMMIT", "explanation": "The COMMIT SQL command ends a transaction and permanently saves all changes made within it."} | верно | COMMIT (END — синоним). Проверено на PG 17. |
T17-L3 1.1 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 quickly locate rows for SELECT, UPDATE, and DELETE operations alike, avoiding full table scans.
Raw{"answer": "yes", "explanation": "Indexes are used by the query optimizer to quickly locate rows for SELECT, UPDATE, and DELETE operations alike, avoiding full table scans."} | верно | Поиск строк для изменения идёт по индексу; docs PostgreSQL — Indexes. |
T17-L4 0.78 c | PostgreSQL: transactions and indexes | To roll back part of the statements inside a transaction, PostgreSQL uses SAVEPOINT. | «yes» Пояснение: PostgreSQL's SAVEPOINT allows rolling back to a specific point within a transaction without aborting the entire transaction.
Raw{"answer": "yes", "explanation": "PostgreSQL's SAVEPOINT allows rolling back to a specific point within a transaction without aborting the entire transaction."} | верно | SAVEPOINT name; ROLLBACK TO name — частичный откат без отмены всей транзакции. Проверено на PG 17. |
T17-L5 1.17 c | PostgreSQL: transactions and indexes | EXPLAIN ANALYZE shows the query plan without executing the query. | «no» Пояснение: EXPLAIN ANALYZE actually executes the query to collect real timing and row-count statistics, whereas plain EXPLAIN shows the plan without executing it.
Raw{"answer": "no", "explanation": "EXPLAIN ANALYZE actually executes the query to collect real timing and row-count statistics, whereas plain EXPLAIN shows the plan without executing it."} | верно | Наоборот: ANALYZE реально выполняет запрос (с побочными эффектами!) и показывает фактические времена узлов; план без выполнения — plain EXPLAIN. |
T17-L6 0.86 c | PostgreSQL: transactions and indexes | Which PostgreSQL extension adds vector types and indexes for embedding search? | «pgvector» Пояснение: pgvector is the PostgreSQL extension that adds a vector data type along with IVFFlat and HNSW index types for efficient similarity search on embeddings.
Raw{"answer": "pgvector", "explanation": "pgvector is the PostgreSQL extension that adds a vector data type along with IVFFlat and HNSW index types for efficient similarity search on embeddings."} | верно | CREATE EXTENSION vector (проект pgvector; в проекте образ pgvector/pgvector:pg17). |
T17-L7 1.2 c | PostgreSQL: transactions and indexes | A partial index (CREATE INDEX ... WHERE ...) is built only over rows satisfying the condition. | «yes» Пояснение: A partial index in PostgreSQL (and similar databases) only indexes rows that satisfy the WHERE condition, reducing index size and improving performance.
Raw{"answer": "yes", "explanation": "A partial index in PostgreSQL (and similar databases) only indexes rows that satisfy the WHERE condition, reducing index size and improving performance."} | верно | docs PostgreSQL — Partial Indexes; типичный кейс — индекс по «активным» записям. |
T17-L8 1.93 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), which detects serialization anomalies via transaction metadata rather than by locking read rows.
Raw{"answer": "no", "explanation": "PostgreSQL implements SERIALIZABLE using Serializable Snapshot Isolation (SSI), which detects serialization anomalies via transaction metadata rather than by locking read rows."} | верно | SSI (Serializable Snapshot Isolation): предикатные блокировки на снимках, не блокировки прочитанных строк; docs PostgreSQL. |
T19-L1 0.59 c | HTTP and REST API | HTTP status 201 means the request resulted in a new resource being created. | «yes» Пояснение: HTTP 201 Created indicates that the request has been successfully processed and a new resource has been created as a result.
Raw{"answer": "yes", "explanation": "HTTP 201 Created indicates that the request has been successfully processed and a new resource has been created as a result."} | верно | 201 Created; обычно на POST, часто с Location; RFC 9110. |
T19-L2 1.26 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 the server successfully processed the request but is returning no response body, commonly used after DELETE operations.
Raw{"answer": 204, "explanation": "HTTP 204 'No Content' indicates the server successfully processed the request but is returning no response body, commonly used after DELETE operations."} | верно | 204 No Content; RFC 9110. |
T19-L3 11.85 c | HTTP and REST API | The DELETE method is idempotent per the HTTP specification: repeating the request for the same resource does not change the outcome. | «yes» Пояснение: RFC 7231 (§4.3.2) explicitly lists DELETE among the idempotent methods, meaning repeating the request does not further change the server's state (the resource is already gone).
Raw{"answer": "yes", "explanation": "RFC 7231 (§4.3.2) explicitly lists DELETE among the idempotent methods, meaning repeating the request does not further change the server's state (the resource is already gone)."} | верно | RFC 9110: DELETE идемпотентен (как PUT); идемпотентность ≠ безопасность — ресурс удаляется при первом вызове. |
T19-L4 0.91 c | HTTP and REST API | The Access-Control-Allow-Origin header is sent by the client so that the server agrees to accept requests from another origin. | «no» Пояснение: The Access-Control-Allow-Origin header is sent by the server (not the client) to indicate which origin is permitted to access the resource.
Raw{"answer": "no", "explanation": "The Access-Control-Allow-Origin header is sent by the server (not the client) to indicate which origin is permitted to access the resource."} | верно | Наоборот: заголовок шлёт СЕРВЕР в ответе, разрешая браузеру cross-origin запрос (CORS); в проекте nelmio/cors-bundle. |
T19-L5 0.85 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 defined specifically to indicate that a client has exceeded a rate limit.
Raw{"answer": "yes", "explanation": "HTTP 429 Too Many Requests is defined specifically to indicate that a client has exceeded a rate limit."} | верно | 429 (+ Retry-After); RFC 6585. В проекте symfony/rate-limiter. |
T19-L6 0.8 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 errors.
Raw{"answer": "no", "explanation": "It's the opposite: 4xx codes indicate client errors and 5xx codes indicate server errors."} | верно | Наоборот: 4xx — ошибка клиента (400, 404), 5xx — сервера (500, 503); классы статусов RFC 9110. |
T19-L7 0.44 c | HTTP and REST API | Which HTTP header indicates the MIME type of the request or response body? | «content-type» Пояснение: The Content-Type HTTP header specifies the MIME type of the request or response body.
Raw{"answer": "Content-Type", "explanation": "The Content-Type HTTP header specifies the MIME type of the request or response body."} | верно | Content-Type: application/json и т.п. |
T19-L8 1.36 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, while PUT (defined in RFC 9110/7231) is required to be idempotent.
Raw{"answer": "yes", "explanation": "RFC 5789 explicitly states that PATCH is not idempotent, while PUT (defined in RFC 9110/7231) is required to be idempotent."} | верно | RFC 5789 прямо оговаривает: PATCH не гарантированно идемпотентен; PUT идемпотентен. |
T20-L1 0.94 c | Security and OAuth | Checking a password by comparing its hash to the stored hash with a plain == is sufficient. | «no» Пояснение: Using == for hash comparison is vulnerable to timing attacks; hash_equals() should be used instead for constant-time comparison.
Raw{"answer": "no", "explanation": "Using == for hash comparison is vulnerable to timing attacks; hash_equals() should be used instead for constant-time comparison."} | верно | Нужна постоянновременная проверка (password_verify) — timing-атаки; соль и алгоритм уже внутри хеша. |
T20-L2 1.44 c | Security and OAuth | A CSRF token is issued by the server (bound to the session) and verified server-side on unsafe requests (POST etc.). | «yes» Пояснение: A CSRF token is indeed generated by the server, tied to the user's session, and validated server-side on state-changing (unsafe) HTTP methods such as POST, PUT, or DELETE.
Raw{"answer": "yes", "explanation": "A CSRF token is indeed generated by the server, tied to the user's session, and validated server-side on state-changing (unsafe) HTTP methods such as POST, PUT, or DELETE."} | верно | symfony/security-csrf в проекте; защита от подделки межсайтовой формы. |
T20-L3 0.73 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 by web developers to declare which resources are allowed to load and execute on a page, thereby mitigating XSS and data injection attacks.
Raw{"answer": "Content-Security-Policy", "explanation": "The Content-Security-Policy HTTP header is used by web developers to declare which resources are allowed to load and execute on a page, thereby mitigating XSS and data injection attacks."} | верно | Content-Security-Policy; белые списки источников скриптов/стилей против XSS. |
T20-L4 1.34 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, not an authentication protocol; the access token grants permission to access resources, while user identity is handled by OpenID Connect (ID token).
Raw{"answer": "no", "explanation": "OAuth 2.0 is an authorization protocol, not an authentication protocol; the access token grants permission to access resources, while user identity is handled by OpenID Connect (ID token)."} | верно | OAuth 2.0 — авторизация/делегирование доступа; аутентификацию добавляет OpenID Connect. В проекте knpuniversity/oauth2-client-bundle (yandex/github/google). |
T20-L5 2.15 c | Security and OAuth | XSS is prevented by validating input on the server before writing it to the database. | «no» Пояснение: XSS is best prevented by context-appropriate output encoding at the point of rendering, not by input validation before storage, because the required escaping depends on the output context (HTML, JS, CSS, URL) and data may be legitimate at input time but dangerous in a particular output context.
Raw{"answer": "no", "explanation": "XSS is best prevented by context-appropriate output encoding at the point of rendering, not by input validation before storage, because the required escaping depends on the output context (HTML, JS, CSS, URL) and data may be legitimate at input time but dangerous in a particular output context."} | верно | XSS лечится контекстным экранированием НА ВЫВОДЕ (Twig autoescape, CSP); валидация ввода не покрывает все контексты вывода. |
T20-L6 1.06 c | Security and OAuth | In the OAuth 2.0 authorization code flow, which parameter arrives at the redirect_uri and is exchanged for an access token? | «code» Пояснение: In the OAuth 2.0 authorization code flow, the 'code' parameter is returned to the redirect_uri and then exchanged at the token endpoint for an access token.
Raw{"answer": "code", "explanation": "In the OAuth 2.0 authorization code flow, the 'code' parameter is returned to the redirect_uri and then exchanged at the token endpoint for an access token."} | верно | Параметр code; обмен на токен POST-ом на /token с client_secret. |
T20-L7 0.7 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» Пояснение: A refresh token has a longer validity period than an access token and is used to request a new access token without requiring the user to log in again.
Raw{"answer": "yes", "explanation": "A refresh token has a longer validity period than an access token and is used to request a new access token without requiring the user to log in again."} | верно | Стандартная схема OAuth/OIDC: короткий access + длинный refresh. |
T20-L8 2.03 c | Security and OAuth | A password salt must be kept secret: without it the hash cannot be verified. | «no» Пояснение: A salt does not need to be kept secret; it is typically stored alongside the hash (e.g., in a database) and its purpose is to prevent rainbow-table attacks, not to provide secrecy.
Raw{"answer": "no", "explanation": "A salt does not need to be kept secret; it is typically stored alongside the hash (e.g., in a database) and its purpose is to prevent rainbow-table attacks, not to provide secrecy."} | верно | Соль хранится открыто (password_hash включает её в строку хеша); секретность соли не нужна. |
T18-L1 0.84 c | Testing: PHPUnit | PHPUnit runs test methods of any class — extending TestCase is not required. | «no» Пояснение: PHPUnit requires test classes to extend PHPUnit\Framework\TestCase in order to recognize and run their test methods.
Raw{"answer": "no", "explanation": "PHPUnit requires test classes to extend PHPUnit\\Framework\\TestCase in order to recognize and run their test methods."} | верно | Тестом считается метод класса, наследующего TestCase (PHPUnit 10). |
T18-L2 0.8 c | Testing: PHPUnit | In PHPUnit, setUp() runs once before all tests of the class. | «no» Пояснение: setUp() runs before each individual test method; setUpBeforeClass() is the one that runs once before all tests in the class.
Raw{"answer": "no", "explanation": "setUp() runs before each individual test method; setUpBeforeClass() is the one that runs once before all tests in the class."} | верно | setUp() — перед КАЖДЫМ тестом; один раз на класс — setUpBeforeClass(). Проверено живым счётчиком на PHPUnit 10.5. |
T18-L3 1.08 c | Testing: PHPUnit | A data provider lets a test run with exactly one set of arguments. | «no» Пояснение: A data provider is designed to supply multiple sets of arguments, causing the test to run once per dataset, not just once.
Raw{"answer": "no", "explanation": "A data provider is designed to supply multiple sets of arguments, causing the test to run once per dataset, not just once."} | верно | Наоборот: наборов может быть сколько угодно — тест выполняется по разу на каждый. Проверено на PHPUnit 10.5 (#[DataProvider]). |
T18-L4 0.78 c | Testing: PHPUnit | Which PHPUnit method declares an expectation that an exception of a given class is thrown? | «expectexception» Пояснение: PHPUnit's expectException() method declares that an exception of a specified class is expected to be thrown.
Raw{"answer": "expectException", "explanation": "PHPUnit's expectException() method declares that an exception of a specified class is expected to be thrown."} | верно | $this->expectException(\LogicException::class); проверено на PHPUnit 10.5. |
T18-L5 1.45 c | Testing: PHPUnit | In PHPUnit, a stub verifies which methods were called on it, while a mock only returns data. | «no» Пояснение: The statement is reversed: a stub only returns pre-programmed data, while a mock object also verifies which methods were called (it is a stub with expectations).
Raw{"answer": "no", "explanation": "The statement is reversed: a stub only returns pre-programmed data, while a mock object also verifies which methods were called (it is a stub with expectations)."} | верно | Наоборот: стаб подставляет данные, мок проверяет взаимодействия (createStub/createMock); docs PHPUnit — Test Doubles. |
T18-L6 0.92 c | Testing: PHPUnit | In PHPUnit 10+, the recommended way to pass data to a test is the #[DataProvider] attribute (the @dataProvider annotation is deprecated). | «yes» Пояснение: In PHPUnit 10+, the #[DataProvider] attribute is the recommended and supported way, while the @dataProvider docblock annotation has been deprecated.
Raw{"answer": "yes", "explanation": "In PHPUnit 10+, the #[DataProvider] attribute is the recommended and supported way, while the @dataProvider docblock annotation has been deprecated."} | верно | Аннотация ещё парсится в PHPUnit 10/11 (AnnotationParser в 10.5.66), удаление — в 12; атрибут — стандарт. |
T18-L7 1.0 c | Testing: PHPUnit | PHPUnit does not allow one test to depend on the result of another. | «no» Пояснение: PHPUnit supports test dependencies via the @depends annotation or #[Depends] attribute, allowing a test to receive the return value of another test.
Raw{"answer": "no", "explanation": "PHPUnit supports test dependencies via the @depends annotation or #[Depends] attribute, allowing a test to receive the return value of another test."} | верно | Зависимости есть: #[Depends] — зависимый тест не запустится, еслиProducer упал. |
T18-L8 1.14 c | Testing: PHPUnit | Which PHPUnit command-line option makes tests run in random order? | «--random-order» Пояснение: The PHPUnit command-line option --random-order shuffles the order in which tests are executed.
Raw{"answer": "--random-order", "explanation": "The PHPUnit command-line option --random-order shuffles the order in which tests are executed."} | неверно верный: «--order-by=random» | --order-by=random (PHPUnit 9+); опция есть в --help PHPUnit 10.5 (проектная). |
T01-L9 4.12 c | Syntax and operators | What does this code output?
```php
echo intdiv(7, 2) . intdiv(-7, 2);
``` | «3-3» Пояснение: intdiv(7,2) gives 3 and intdiv(-7,2) gives -3 (truncation toward zero), concatenated with the dot operator yields the string "3-3".
Raw{"answer": "3-3", "explanation": "intdiv(7,2) gives 3 and intdiv(-7,2) gives -3 (truncation toward zero), concatenated with the dot operator yields the string \"3-3\"."} | верно | intdiv truncates toward zero: intdiv(-7, 2) = -3, not -4. |
T01-L10 1.07 c | Syntax and operators | What does this code output?
```php
echo -3 ** 2;
``` | «-9» Пояснение: In PHP, the exponentiation operator ** has higher precedence than unary minus, so -3 ** 2 is parsed as -(3**2) = -9.
Raw{"answer": -9, "explanation": "In PHP, the exponentiation operator ** has higher precedence than unary minus, so -3 ** 2 is parsed as -(3**2) = -9."} | верно | ** is right-associative and binds tighter than unary minus: -(3²). |
T02-L9 6.59 c | Types and comparisons | What does this code output?
```php
echo '1e1' == '10' ? 'true' : 'false';
``` | «true» Пояснение: In PHP (prior to 8.0), both '1e1' and '10' are numeric strings, so they are compared numerically; '1e1' is scientific notation for 10, so 10 == 10 is true.
Raw{"answer": "true", "explanation": "In PHP (prior to 8.0), both '1e1' and '10' are numeric strings, so they are compared numerically; '1e1' is scientific notation for 10, so 10 == 10 is true."} | верно | Both strings are numeric — compared as numbers: 10 == 10. |
T02-L10 2.09 c | Types and comparisons | What does this code output?
```php
switch ('a') {
case 0: echo 'zero'; break;
default: echo 'other';
}
``` | «other» Пояснение: The string 'a' is not loosely equal to 0, so the default case executes and outputs 'other'.
Raw{"answer": "other", "explanation": "The string 'a' is not loosely equal to 0, so the default case executes and outputs 'other'."} | верно | PHP 8: 'a' == 0 → false (used to be true) — default fires. |
T03-L9 3.69 c | Strings | What does this code output?
```php
echo strtr('abc', ['a' => '1', 'ab' => '2']);
``` | «2c» Пояснение: strtr with an array replaces the longest matching key first at each position, so 'ab' (length 2) matches before 'a' (length 1), giving '2c'.
Raw{"answer": "2c", "explanation": "strtr with an array replaces the longest matching key first at each position, so 'ab' (length 2) matches before 'a' (length 1), giving '2c'."} | верно | strtr with an array prefers the longest matching key. |
T03-L10 3.26 c | Strings | What does this code output?
```php
echo '[' . substr('hello', -10) . ']';
``` | «[]» Пояснение: substr('hello', -10) returns an empty string because the negative start position (-10) exceeds the string length (5), so nothing is extracted, resulting in empty brackets.
Raw{"answer": "[]", "explanation": "substr('hello', -10) returns an empty string because the negative start position (-10) exceeds the string length (5), so nothing is extracted, resulting in empty brackets."} | неверно верный: «[hello]» | A negative start beyond the string is clamped to the beginning. |
T04-L9 1.59 c | Arrays | What does this code output?
```php
$a = ['k' => 1, 'n' => 2];
$b = ['k' => 9, 'm' => 3];
echo implode(',', array_keys($a + $b));
``` | «k,n,m» Пояснение: The + operator merges arrays with left-operand keys taking precedence, so $a+$b = ['k'=>1,'n'=>2,'m'=>3], and implode of its keys gives 'k,n,m'.
Raw{"answer": "k,n,m", "explanation": "The + operator merges arrays with left-operand keys taking precedence, so $a+$b = ['k'=>1,'n'=>2,'m'=>3], and implode of its keys gives 'k,n,m'."} | верно | The + operator: on duplicate string keys the left array wins. |
T04-L10 1.88 c | Arrays | What does this code output?
```php
$a = [[1, 'x', 2], [2, 'y', 1], [3, 'z', 2]];
usort($a, fn($p, $q) => $p[2] <=> $q[2]);
echo implode('', array_column($a, 1));
``` | «yxz» Пояснение: The array is sorted by the third element (index 2) ascending, giving [2,'y',1], [1,'x',2], [3,'z',2], then array_column extracts the second element from each sub-array, resulting in 'yxz'.
Raw{"answer": "yxz", "explanation": "The array is sorted by the third element (index 2) ascending, giving [2,'y',1], [1,'x',2], [3,'z',2], then array_column extracts the second element from each sub-array, resulting in 'yxz'."} | верно | Sorts are stable since 8.0: x and z keep their order on a tie. |
T05-L10 1.48 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 an associative array passes arguments by name, so $a=5 and $b=1, giving 5-1=4.
Raw{"answer": 4, "explanation": "The spread operator with an associative array passes arguments by name, so $a=5 and $b=1, giving 5-1=4."} | верно | String keys of a spread array become named arguments. |
T05-L9 2.2 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 $p; even after $p is set to null, the closure still holds a reference to the object, so calling $f() invokes g() on the original instance and returns 3.
Raw{"answer": 3, "explanation": "The first-class callable syntax $p->g(...) creates a Closure bound to the object $p; even after $p is set to null, the closure still holds a reference to the object, so calling $f() invokes g() on the original instance and returns 3."} | верно | First-class callable syntax binds $this at creation time. |
T06-L9 1.01 c | OOP: classes and inheritance | What does this code output?
```php
class A
{
public function who(): string { return static::class; }
}
class B extends A {}
echo (new B)->who();
``` | «b» Пояснение: static::class uses late static binding, so it resolves to the actual class of the object (B), not the defining class (A).
Raw{"answer": "B", "explanation": "static::class uses late static binding, so it resolves to the actual class of the object (B), not the defining class (A)."} | верно | Late static binding: static::class is the receiver's class. |
T06-L10 3.59 c | OOP: classes and inheritance | What does this code output on PHP 8.5?
```php
class C
{
public int $x = 0 {
set { $this->x = $value * 2; }
}
}
$c = new C;
$c->x = 5;
echo $c->x;
``` | «10» Пояснение: The set hook doubles the value (5*2=10), and reassigning within the hook does not re-trigger it, so the property stores 10.
Raw{"answer": 10, "explanation": "The set hook doubles the value (5*2=10), and reassigning within the hook does not re-trigger it, so the property stores 10."} | верно | Inside the set hook, $this->x writes the backing store (no recursion): 5*2. |
T07-L9 1.44 c | Interfaces, traits, enum | What does this code output?
```php
trait TA
{
public function f(): string { return 'A'; }
}
trait TB
{
public function f(): string { return 'B'; }
}
class TC
{
use TA, TB { TB::f insteadof TA; TA::f as g; }
}
echo (new TC)->f() . (new TC)->g();
``` | «ba» Пояснение: TB::f insteadof TA makes f() return 'B', and TA::f as g aliases TA's f() to g() returning 'A', so the concatenation is 'BA'.
Raw{"answer": "BA", "explanation": "TB::f insteadof TA makes f() return 'B', and TA::f as g aliases TA's f() to g() returning 'A', so the concatenation is 'BA'."} | верно | insteadof picks the implementation; as keeps the other under an alias. |
T07-L10 1.29 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 using a trait gets its own independent copy of the trait's static properties, so modifying CX::$n does not affect CY::$n.
Raw{"answer": 0, "explanation": "Each class using a trait gets its own independent copy of the trait's static properties, so modifying CX::$n does not affect CY::$n."} | верно | A trait's static property is copied into each consuming class. |
T08-L10 1.12 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{"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.38 c | Exceptions and errors | What does this code output?
```php
try {
try {
throw new RuntimeException('first');
} finally {
throw new LogicException('second');
}
} catch (LogicException $e) {
echo $e->getMessage();
}
``` | «second» Пояснение: The finally block throws a LogicException which replaces the original RuntimeException, and that LogicException is caught by the outer catch block, printing its message 'second'.
Raw{"answer": "second", "explanation": "The finally block throws a LogicException which replaces the original RuntimeException, and that LogicException is caught by the outer catch block, printing its message 'second'."} | верно | An exception from finally replaces the in-flight one — the last thrown is caught. |
T09-L9 2.36 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 via the use alias to 'App\Foo', while \Baz::class references the global class 'Baz' directly.
Raw{"answer": "App\\Foo|Baz", "explanation": "Baz::class resolves via the use alias to 'App\\Foo', while \\Baz::class references the global class 'Baz' directly."} | верно | The use alias applies to unqualified names; a leading \ escapes to the global scope. |
T09-L10 3.48 c | Namespaces and autoloading | What does this code output?
```php
namespace Ns;
class Foo {}
$c = 'Foo';
echo (class_exists($c) ? 'yes' : 'no')
. (class_exists(__NAMESPACE__ . '\\' . $c) ? 'yes' : 'no');
``` | «noyes» Пояснение: class_exists('Foo') checks for a global class Foo (not Ns\Foo) so it returns no; class_exists('Ns\\Foo') finds the defined class and returns yes.
Raw{"answer": "noyes", "explanation": "class_exists('Foo') checks for a global class Foo (not Ns\\Foo) so it returns no; class_exists('Ns\\\\Foo') finds the defined class and returns yes."} | верно | Dynamic names are not resolved against the namespace — 'Foo' is the global class. |
T10-L9 1.0 c | References and scope | What does this code output?
```php
$a = [1, 2, 3];
foreach ($a as &$v) {}
$v = 99;
echo implode(',', $a);
``` | «1,2,99» Пояснение: The foreach loop leaves $v as a reference to the last element of $a, so assigning 99 to $v changes the last element, resulting in [1, 2, 99].
Raw{"answer": "1,2,99", "explanation": "The foreach loop leaves $v as a reference to the last element of $a, so assigning 99 to $v changes the last element, resulting in [1, 2, 99]."} | верно | After a by-ref foreach, $v remains a reference to the last element. |
T10-L10 2.35 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 are shared per-class (where defined), so all calls to inc() on A or B share the same counter, which reaches 3 after three increments.
Raw{"answer": 3, "explanation": "Static variables in PHP are shared per-class (where defined), so all calls to inc() on A or B share the same counter, which reaches 3 after three increments."} | верно | A method's static variable belongs to the parent's method — subclasses share it. |
T11-L9 2.42 c | Generators, iterators, SPL | What does this code output?
```php
function g(): Generator
{
$x = yield 1;
return $x + 1;
}
$g = g();
$g->send(10);
echo $g->getReturn();
``` | «11» Пояснение: send(10) starts the generator, the yield 1 receives 10 so $x=10, then return 10+1=11, and getReturn() retrieves 11.
Raw{"answer": 11, "explanation": "send(10) starts the generator, the yield 1 receives 10 so $x=10, then return 10+1=11, and getReturn() retrieves 11."} | верно | send() resumes the generator: $x = 10, return 10+1. |
T11-L10 1.66 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 inner() yields 1 and 2, then the return value 'ok' is assigned to $r and yielded, producing the sequence 1, 2, ok.
Raw{"answer": "1,2,ok", "explanation": "yield from inner() yields 1 and 2, then the return value 'ok' is assigned to $r and yielded, producing the sequence 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.26 c | Configuration and security | What does this code output?
```php
$hash = password_hash('x', PASSWORD_BCRYPT, ['cost' => 4]);
echo password_needs_rehash($hash, PASSWORD_BCRYPT, ['cost' => 4]) ? 'yes' : 'no';
echo password_needs_rehash($hash, PASSWORD_BCRYPT, ['cost' => 5]) ? 'yes' : 'no';
``` | «noyes» Пояснение: The first check compares cost 4 with cost 4 (no rehash needed → 'no'), the second compares cost 4 with cost 5 (rehash needed → 'yes').
Raw{"answer": "noyes", "explanation": "The first check compares cost 4 with cost 4 (no rehash needed → 'no'), the second compares cost 4 with cost 5 (rehash needed → 'yes')."} | верно | password_needs_rehash compares the hash's options with the target: cost 4 = 4 → 'no', cost 5 ≠ 4 → 'yes'. |
T12-L10 4.5 c | Configuration and security | What does this code output on PHP 8.5?
```php
echo (E_ALL & 2048) === 0 ? 'strict-out' : 'strict-in';
``` | «strict-out» Пояснение: In PHP 8.4+, E_STRICT (2048) was removed from E_ALL, so (E_ALL & 2048) === 0 evaluates to true, yielding 'strict-out'.
Raw{"answer": "strict-out", "explanation": "In PHP 8.4+, E_STRICT (2048) was removed from E_ALL, so (E_ALL & 2048) === 0 evaluates to true, yielding 'strict-out'."} | верно | Since PHP 8.4, E_STRICT is out of E_ALL: the 2048 bit is unset → 'strict-out' (2048 is the historical E_STRICT bit). |
T13-L9 2.04 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 HeaderBag normalizes both the stored key (HTTP_X_TOKEN → x-token) and the lookup key (X-Token → x-token) to the same form, so the value is found.
Raw{"answer": "mapped", "explanation": "Symfony's HeaderBag normalizes both the stored key (HTTP_X_TOKEN → x-token) and the lookup key (X-Token → x-token) to the same form, so the value is found."} | верно | 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.17 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 EventDispatcher calls listeners in descending priority order (10, 5, 0), so B, C, A are appended in that order.
Raw{"answer": "BCA", "explanation": "Symfony EventDispatcher calls listeners in descending priority order (10, 5, 0), so B, C, A are appended in that order."} | верно | Listeners run by descending priority: 10 (B), 5 (C), 0 (A). |
T14-L10 1.79 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 ORM's identity map ensures that $em->find() returns the same managed instance for the same entity ID, so both $a and $b reference the identical object.
Raw{"answer": "same", "explanation": "Doctrine ORM's identity map ensures that $em->find() returns the same managed instance for the same entity ID, so both $a and $b reference the identical object."} | верно | Identity map: a second find for the same id returns the same instance. |
T14-L9 2.78 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» Пояснение: When an entity is persisted and then removed before flush, Doctrine cancels the scheduled INSERT (no DELETE is issued since it was never in the DB), so flush is a no-op and the table remains empty.
Raw{"answer": 0, "explanation": "When an entity is persisted and then removed before flush, Doctrine cancels the scheduled INSERT (no DELETE is issued since it was never in the DB), so flush is a no-op and the table remains empty."} | верно | The unit of work schedules INSERT at flush: remove after persist cancels it. |
T15-L10 1.09 c | PostgreSQL | What does this SQL query return (PostgreSQL 17)?
```sql
CREATE TEMP TABLE t (x int);
INSERT INTO t VALUES (1), (NULL);
SELECT count(x) FROM t;
``` | «1» Пояснение: COUNT(x) counts only non-NULL values in column x, so it returns 1 (excluding the NULL row).
Raw{"answer": 1, "explanation": "COUNT(x) counts only non-NULL values in column x, so it returns 1 (excluding the NULL row)."} | верно | count(column) skips NULLs; count(*) would return 2. |
T15-L9 1.56 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 sum(x) OVER (ORDER BY id) produces running totals (10, 30, 60), and string_agg concatenates them in id order with commas.
Raw{"answer": "10,30,60", "explanation": "The window function sum(x) OVER (ORDER BY id) produces running totals (10, 30, 60), and string_agg concatenates them in id order with commas."} | верно | With ORDER BY the default window frame is running (start to current row). |
T16-L9 4.78 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» Пояснение: Each middleware echoes its tag before delegating to the next one in the stack, so M1 echoes first, then M2 echoes, producing 'M1M2'.
Raw{"answer": "M1M2", "explanation": "Each middleware echoes its tag before delegating to the next one in the stack, so M1 echoes first, then M2 echoes, producing 'M1M2'."} | верно | The first-added middleware runs first (outermost). |
T16-L10 4.94 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;
``` | «1» Пояснение: HandleMessageMiddleware calls HandlersLocator::getHandler() which returns only the first matching handler descriptor ($d1), so $n is incremented by 1 only.
Raw{"answer": 1, "explanation": "HandleMessageMiddleware calls HandlersLocator::getHandler() which returns only the first matching handler descriptor ($d1), so $n is incremented by 1 only."} | неверно верный: «11» | All registered handlers of the message run: 1 + 10 = 11. |
T17-L9 1.52 c | PostgreSQL: transactions and indexes | What does this SQL query return (PostgreSQL 17)?
```sql
CREATE TEMP TABLE t (a int);
CREATE UNIQUE INDEX ON t (a);
INSERT INTO t VALUES (1) ON CONFLICT DO NOTHING;
INSERT INTO t VALUES (1) ON CONFLICT DO NOTHING;
SELECT count(*) FROM t;
``` | «1» Пояснение: The first INSERT adds row (1), the second INSERT is a no-op due to ON CONFLICT DO NOTHING, so count(*) returns 1.
Raw{"answer": 1, "explanation": "The first INSERT adds row (1), the second INSERT is a no-op due to ON CONFLICT DO NOTHING, so count(*) returns 1."} | верно | ON CONFLICT DO NOTHING skips the duplicate: one insert. |
T17-L10 2.18 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» Пояснение: Because the UNIQUE constraint is DEFERRABLE INITIALLY DEFERRED, both INSERTs succeed within the transaction; the duplicate is only detected at COMMIT, so SELECT count(*) returns 2.
Raw{"answer": 2, "explanation": "Because the UNIQUE constraint is DEFERRABLE INITIALLY DEFERRED, both INSERTs succeed within the transaction; the duplicate is only detected at COMMIT, so SELECT count(*) returns 2."} | верно | DEFERRED postpones the uniqueness check to COMMIT — count sees 2 rows. |
T18-L9 2.81 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' regex matches both test_sum (3 data provider sets) and test_sum_abs (3 data provider sets), totaling 6 tests.
Raw{"answer": 6, "explanation": "The --filter 'test_sum' regex matches both test_sum (3 data provider sets) and test_sum_abs (3 data provider sets), totaling 6 tests."} | верно | --filter is a substring match: test_sum also matches test_sum_abs (3+3 datasets). |
T18-L10 1.34 c | Testing: PHPUnit | How many tests will this command run, and how many of them will fail? Answer with two comma-separated numbers (ran, failed).
```php
use PHPUnit\Framework\TestCase;
use PHPUnit\Framework\Attributes\DataProvider;
final class Calc2Test extends TestCase
{
public function prov(): array
{
return [[1], [-1]];
}
#[DataProvider('prov')]
public function test_x(int $x): void
{
$this->assertTrue($x > 0);
}
}
```
Command: `phpunit Calc2Test.php` (PHPUnit 10.5) | «2, 1» Пояснение: The DataProvider supplies two datasets ([1] and [-1]), so the test runs twice; the second run with -1 fails because -1 > 0 is false.
Raw{"answer": "2, 1", "explanation": "The DataProvider supplies two datasets ([1] and [-1]), so the test runs twice; the second run with -1 fails because -1 > 0 is false."} | верно | 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.77 c | HTTP and REST API | Which HTTP method does this command send?
```bash
curl -s -d 'a=1' http://demo.local/api
``` | «post» Пояснение: The -d flag in curl sends data in the request body and implicitly sets the HTTP method to POST.
Raw{"answer": "POST", "explanation": "The -d flag in curl sends data in the request body and implicitly sets the HTTP method to POST."} | верно | -d/-F switches curl to POST by default. |
T19-L10 0.97 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 in 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 in the URL."} | верно | -G turns -d data into the query string; the method stays GET. |
T20-L9 3.25 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 specifies that when client authentication fails (e.g., a non-existent client_id), the token endpoint returns the error code 'invalid_client'.
Raw{"answer": "invalid_client", "explanation": "RFC 6749 Section 5.2 specifies that when client authentication fails (e.g., a non-existent client_id), the token endpoint returns the error code 'invalid_client'."} | верно | Unknown client → invalid_client (RFC 6749 §5.2). |
T20-L10 1.4 c | Security and OAuth | OAuth 2.0: the client started the flow with response_type=token. In which part of the redirect_uri does the authorization server pass the access_token? | «fragment» Пояснение: In the OAuth 2.0 implicit grant (response_type=token), the access token is returned in the URL fragment (after '#') of the redirect_uri, so it is not sent to the server or stored in logs.
Raw{"answer": "fragment", "explanation": "In the OAuth 2.0 implicit grant (response_type=token), the access token is returned in the URL fragment (after '#') of the redirect_uri, so it is not sent to the server or stored in logs."} | верно | The implicit flow passes the token in the URL fragment (#) — it never reaches the server. |
T21-L9 1.8 c | Twig | What does this Twig template output?
```twig
{{ false|default(2) * 3 }}
``` | «0» Пояснение: The default filter only replaces null/undefined values, so false passes through unchanged, and false * 3 evaluates to 0 in PHP/Twig arithmetic.
Raw{"answer": 0, "explanation": "The default filter only replaces null/undefined values, so false passes through unchanged, and false * 3 evaluates to 0 in PHP/Twig arithmetic."} | неверно верный: «6» | default replaces exactly false/null/''/[] — false becomes 2, 2*3 = 6; the naive 'default is for undefined only' yields 0. |
T21-L10 2.63 c | Twig | What exception class does render() of this template throw?
```twig
{{ 'a' ~ 1 + 2 }}
``` | «a3» Пояснение: In Twig, 1+2 evaluates to 3, and the ~ operator concatenates the string 'a' with the integer 3, producing the string 'a3'.
Raw{"answer": "a3", "explanation": "In Twig, 1+2 evaluates to 3, and the ~ operator concatenates the string 'a' with the integer 3, producing the string 'a3'."} | неверно верный: «runtimeerror» | In Twig ~ binds tighter than +: ('a' ~ 1) + 2 → string + int → a render error (RuntimeError). |
T22-L9 2.81 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 only checks if the array is empty (count === 0); since [''] has one element, the constraint passes and there are 0 violations.
Raw{"answer": 0, "explanation": "NotBlank on an array only checks if the array is empty (count === 0); since [''] has one element, the constraint passes and there are 0 violations."} | верно | NotBlank treats null, '', [] as blank — the array [''] is not blank. |
T22-L10 4.14 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\unexpectedtypeexception» Пояснение: Calling isValid() on a form that was never submitted (no data passed) throws an UnexpectedTypeException because the form's data is null instead of the expected array/string type.
Raw{"answer": "Symfony\\Component\\Form\\Exception\\UnexpectedTypeException", "explanation": "Calling isValid() on a form that was never submitted (no data passed) throws an UnexpectedTypeException because the form's data is null instead of the expected array/string type."} | неверно верный: «symfony\component\form\exception\logicexception» | isValid() on a non-submitted form throws LogicException, it does not return false. |
T23-L9 2.55 c | Symfony: configuration and services | What does this code output?
```php
use Symfony\Component\DependencyInjection\ContainerBuilder;
$c = new ContainerBuilder();
$c->register('a', stdClass::class)->setPublic(true);
$c->compile();
echo spl_object_id($c->get('a')) === spl_object_id($c->get('a')) ? 'same' : 'diff';
``` | «same» Пояснение: Symfony DI services are singletons by default, so calling get('a') twice returns the same stdClass instance, making the spl_object_id comparison true.
Raw{"answer": "same", "explanation": "Symfony DI services are singletons by default, so calling get('a') twice returns the same stdClass instance, making the spl_object_id comparison true."} | верно | Container services are shared: two get() calls yield one instance. |
T23-L10 1.33 c | Symfony: configuration and services | What does this code output?
```php
use Symfony\Component\DependencyInjection\ContainerBuilder;
$c = new ContainerBuilder();
$c->setParameter('name', 'Bob');
$c->setParameter('greeting', 'hi %name%');
$c->setParameter('message', '%greeting%!');
$c->compile();
echo $c->getParameter('message');
``` | «hi bob!» Пояснение: Symfony's ContainerBuilder resolves parameter references recursively during compilation: %greeting%! → hi %name%! → hi Bob!
Raw{"answer": "hi Bob!", "explanation": "Symfony's ContainerBuilder resolves parameter references recursively during compilation: %greeting%! → hi %name%! → hi Bob!"} | верно | compile() resolves %-references transitively: %greeting% → 'hi %name%' → 'hi Bob!', the answer assembles over two hops. |
T24-L9 1.24 c | Bootstrap | What is the max-width of .container in Bootstrap 5.3 at a 992px viewport? | «960px» Пояснение: In Bootstrap 5.3, the .container max-width at the ≥992px breakpoint is 960px.
Raw{"answer": "960px", "explanation": "In Bootstrap 5.3, the .container max-width at the ≥992px breakpoint is 960px."} | верно | 5.x container widths: 540/720/960/1140/1320 (sm–xxl); 992 → 960px. |
T24-L10 7.08 c | Bootstrap | Which utility sets the text color in Bootstrap 5.3 for `<p class="text-danger text-primary">…</p>`? Answer with the winning class name. | «text-danger» Пояснение: In Bootstrap 5.3's generated CSS, .text-danger appears after .text-primary in the stylesheet (following the $theme-colors map order), so with equal specificity it wins the cascade.
Raw{"answer": "text-danger", "explanation": "In Bootstrap 5.3's generated CSS, .text-danger appears after .text-primary in the stylesheet (following the $theme-colors map order), so with equal specificity it wins the cascade."} | верно | Specificity ties — the later rule wins: text-danger is declared after text-primary. |
T25-L9 1.27 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 class depends on both Application (PlaceOrder) and Infrastructure (Db), but Domain may only depend on Domain, resulting in 2 violations.
Raw{"answer": 2, "explanation": "The Domain layer class depends on both Application (PlaceOrder) and Infrastructure (Db), but Domain may only depend on Domain, resulting in 2 violations."} | верно | Domain may depend only on Domain: PlaceOrder (Application) + Db (Infrastructure) = 2. |
T25-L10 1.53 c | Clean architecture | Layers: Domain, Application, Infrastructure. Deptrac rules: Application → Domain; Infrastructure → Domain, Application; Domain → Domain only.
How many violations will deptrac report for this class?
```php
namespace App\Domain;
use App\Application\PlaceOrder;
use App\Infrastructure\Db;
class BillingService
{
public function __construct(
private PlaceOrder $handler,
private Db $db,
private \App\Infrastructure\Logger $logger,
) {}
}
``` | «3» Пояснение: The Domain class depends on Application\PlaceOrder and two Infrastructure classes (Db, Logger), each violating the 'Domain → Domain only' rule.
Raw{"answer": 3, "explanation": "The Domain class depends on Application\\PlaceOrder and two Infrastructure classes (Db, Logger), each violating the 'Domain → Domain only' rule."} | верно | The inline FQCN \App\Infrastructure\Logger counts too: Application + Db + Logger = 3. |
T26-L10 1.02 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» Пояснение: Money is immutable (readonly property), so $a remains 10 and $c gets 10+5=15, producing the string '10,15'.
Raw{"answer": "10,15", "explanation": "Money is immutable (readonly property), so $a remains 10 and $c gets 10+5=15, producing the string '10,15'."} | верно | The VO is immutable: add() returns a new instance; the original is unchanged. |
T26-L9 1.37 c | DDD | What does this code output?
```php
final class Order
{
private array $items = [];
public function add(string $sku): void
{
$this->items[$sku] = true;
}
public function count(): int
{
return count($this->items);
}
public function remove(string $sku): void
{
if (count($this->items) === 1) {
throw new DomainException('last item');
}
unset($this->items[$sku]);
}
}
$o = new Order;
$o->add('a');
try {
$o->remove('a');
} catch (DomainException) {
}
echo $o->count();
``` | «1» Пояснение: The remove() method throws a DomainException when only one item remains, so unset() is never executed and the item stays, making count() return 1.
Raw{"answer": 1, "explanation": "The remove() method throws a DomainException when only one item remains, so unset() is never executed and the item stays, making count() return 1."} | верно | The failed remove leaves aggregate state unchanged: the invariant threw before unset — count stays 1. |
VC-L9 0.64 c | PHP 8.4–8.5 | What does this code output on PHP 8.5?
```php
class C
{
public function hi(): string { return 'hi'; }
}
echo new C()->hi();
``` | «hi» Пояснение: The code creates an instance of class C and calls its hi() method, which returns the string 'hi', and echoes it.
Raw{"answer": "hi", "explanation": "The code creates an instance of class C and calls its hi() method, which returns the string 'hi', and echoes it."} | верно | Since 8.4, new in a method chain works without wrapping parentheses. |
VC-L10 2.7 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 accessing $o->v the lazy ghost is uninitialized (prints 'yes'); after the property access triggers the initializer callback, it becomes initialized (prints 'no').
Raw{"answer": "yesno", "explanation": "Before accessing $o->v the lazy ghost is uninitialized (prints 'yes'); after the property access triggers the initializer callback, it becomes initialized (prints 'no')."} | верно | newLazyGhost (8.4): the object stays lazy until first access — reading a property initializes it and clears the flag. |
T28-L9 1.01 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 authentication system (including AbstractGuardAuthenticator) was removed in Symfony 6.0, so the class does not exist in 8.1.
Raw{"answer": "no", "explanation": "The Symfony Guard authentication system (including AbstractGuardAuthenticator) was removed in Symfony 6.0, so the class does not exist in 8.1."} | верно | Guard authentication was removed in Symfony 7.0 — the class is gone in 8.1. |
T28-L10 5.0 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 6.0 (deprecated in 5.3), so it doesn't exist in 8.1; AttributeClassLoader has been the replacement since 5.3 and still exists in 8.1.
Raw{"answer": "noyes", "explanation": "AnnotationClassLoader was removed in Symfony 6.0 (deprecated in 5.3), so it doesn't exist in 8.1; AttributeClassLoader has been the replacement since 5.3 and still exists in 8.1."} | верно | Annotation loaders were removed in 7.0; only attribute loaders remain (Annotation→Attribute). |