Пример запроса (первая клетка). System одинаковый во всех запросах прогона, user — свой вопрос для каждой клетки:
| Клетка | Тема | Утверждение | Ответ |
Результат | Обоснование |
T01-L1 1.9 c | Syntax and operators | Double-quoted and single-quoted strings are processed identically; the difference is only in speed. | «no» Пояснение: Double-quoted strings interpolate variables and process escape sequences like \n, while single-quoted strings do not (only \' and \\ are escaped), so they are not processed identically.
Raw{"answer": "no", "explanation": "Double-quoted strings interpolate variables and process escape sequences like \\n, while single-quoted strings do not (only \\' and \\\\ are escaped), so they are not processed identically."} | верно | В двойных кавычках работают интерполяция переменных и escape-последовательности, в одинарных — нет. |
T01-L2 2.36 c | Syntax and operators | The ?? operator follows isset semantics and raises no warnings for undefined variables. | «yes» Пояснение: The ?? operator uses isset() semantics internally, so undefined variables, array keys, and properties produce no notice or warning and simply fall through to the right-hand value.
Raw{"answer": "yes", "explanation": "The ?? operator uses isset() semantics internally, so undefined variables, array keys, and properties produce no notice or warning and simply fall through to the right-hand value."} | верно | ?? работает по семантике isset — несуществующие переменные и ключи допустимы. |
T01-L3 1.69 c | Syntax and operators | What will this print: echo 'a', 'b'; | «ab» Пояснение: PHP's echo accepts multiple comma-separated arguments and outputs each in sequence with no separator, so 'a' and 'b' print as ab.
Raw{"answer": "ab", "explanation": "PHP's echo accepts multiple comma-separated arguments and outputs each in sequence with no separator, so 'a' and 'b' print as ab."} | верно | echo принимает список аргументов: ab. |
T01-L4 1.52 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 1, so it can be used within expressions, unlike echo.
Raw{"answer": "yes", "explanation": "In PHP, print is a language construct that always returns 1, so it can be used within expressions, unlike echo."} | верно | print — выражение со значением 1, в отличие от echo, который значения не возвращает. |
T01-L5 2.22 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, and the right operand when the left is falsy.
Raw{"answer": "no", "explanation": "The elvis operator `$a ?: $b` returns the left operand when it is truthy, and the right operand when the left is falsy."} | верно | Наоборот: $a ?: $b возвращает $a, если он истинный, иначе $b. |
T01-L6 2.36 c | Syntax and operators | In PHP 8, the concatenation operator (.) has lower precedence than addition and subtraction. | «yes» Пояснение: In PHP 8, the concatenation operator (.) was given lower precedence than + and -, so arithmetic is evaluated before concatenation.
Raw{"answer": "yes", "explanation": "In PHP 8, the concatenation operator (.) was given lower precedence than + and -, so arithmetic is evaluated before concatenation."} | верно | С PHP 8 (RFC concat precedence) '.' имеет приоритет ниже арифметики: 'сумма: ' . 2 + 3 → 'сумма: 5' (в PHP 7 было иначе). |
T01-L7 2.17 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 2 ** (3 ** 2) = 2 ** 9 = 512, not 64.
Raw{"answer": "no", "explanation": "The ** operator in PHP is right-associative, so 2 ** 3 ** 2 is 2 ** (3 ** 2) = 2 ** 9 = 512, not 64."} | верно | ** право-ассоциативен: 2 ** (3 ** 2) = 2 ** 9 = 512. |
T01-L8 2.41 c | Syntax and operators | What string will this print: echo 'sum: ' . 2 + 3; (PHP 8)? | «sum: 5» Пояснение: In PHP 8, the arithmetic `+` binds tighter than the concatenation operator `.`, so `2 + 3` is evaluated first as 5, then concatenated with 'sum: '.
Raw{"answer": "sum: 5", "explanation": "In PHP 8, the arithmetic `+` binds tighter than the concatenation operator `.`, so `2 + 3` is evaluated first as 5, then concatenated with 'sum: '."} | верно | Парная к verify-клетке про приоритет: 'сумма: 5'. |
T02-L1 2.02 c | Types and comparisons | With strict comparison (===), arrays are considered equal regardless of element order. | «no» Пояснение: With ===, arrays are equal only if they have the same key/value pairs in the same order and of the same types; == ignores order, but === does not.
Raw{"answer": "no", "explanation": "With ===, arrays are equal only if they have the same key/value pairs in the same order and of the same types; == ignores order, but === does not."} | верно | === для массивов требует совпадения и значений, и их порядка. |
T02-L2 1.58 c | Types and comparisons | The comparison 0 == false returns false because it is a strict comparison. | «no» Пояснение: 0 == false is a loose comparison that performs type juggling and evaluates to true; the strict comparison 0 === false would return false.
Raw{"answer": "no", "explanation": "0 == false is a loose comparison that performs type juggling and evaluates to true; the strict comparison 0 === false would return false."} | верно | Наоборот: == — нестрогое сравнение и возвращает true; строгое — это === (0 === false → false). |
T02-L3 2.09 c | Types and comparisons | In PHP 8, the expression "abc" == 0 returns true. | «no» Пояснение: PHP 8 changed string-to-number comparison: a non-numeric string like "abc" is compared as a string with 0 (converted to "0"), so "abc" == 0 is false.
Raw{"answer": "no", "explanation": "PHP 8 changed string-to-number comparison: a non-numeric string like \"abc\" is compared as a string with 0 (converted to \"0\"), so \"abc\" == 0 is false."} | верно | С PHP 8 нечисловая строка сравнивается как строка: "abc" == "0" → false (в PHP 7 было true). |
T02-L4 2.5 c | Types and comparisons | Under loose comparison, null equals 0, the empty string, and false at the same time. | «yes» Пояснение: In PHP, null loosely equals 0, the empty string, and false (null == 0, null == "", and null == false are all true), even though 0 and "" are not loosely equal to each other in PHP 8.
Raw{"answer": "yes", "explanation": "In PHP, null loosely equals 0, the empty string, and false (null == 0, null == \"\", and null == false are all true), even though 0 and \"\" are not loosely equal to each other in PHP 8."} | верно | null == 0, null == "" и null == false — все true. |
T02-L5 1.51 c | Types and comparisons | What does the expression (int) '42abc' return? | «42» Пояснение: PHP's integer cast of a string reads the leading numeric portion and ignores the trailing non-numeric characters, yielding 42.
Raw{"answer": 42, "explanation": "PHP's integer cast of a string reads the leading numeric portion and ignores the trailing non-numeric characters, yielding 42."} | верно | Ведущая числовая часть: 42, без ошибок и warning. |
T02-L6 2.06 c | Types and comparisons | What does the expression '5' + 5 return? | «10» Пояснение: PHP converts the numeric string '5' to an integer in arithmetic, so '5' + 5 yields the integer 10.
Raw{"answer": 10, "explanation": "PHP converts the numeric string '5' to an integer in arithmetic, so '5' + 5 yields the integer 10."} | верно | Числовая строка приводится: int 10. |
T02-L7 1.68 c | Types and comparisons | When cast to string, false becomes "0". | «no» Пояснение: In PHP, false cast to string becomes an empty string "", not "0"; it is null-like, while true becomes "1".
Raw{"answer": "no", "explanation": "In PHP, false cast to string becomes an empty string \"\", not \"0\"; it is null-like, while true becomes \"1\"."} | верно | false → "", true → "1". |
T02-L8 2.42 c | Types and comparisons | The comparison 0.1 + 0.2 === 0.3 returns false. | «yes» Пояснение: In PHP, 0.1 + 0.2 evaluates to about 0.30000000000000004 due to binary floating-point representation, so the strict comparison with 0.3 returns false.
Raw{"answer": "yes", "explanation": "In PHP, 0.1 + 0.2 evaluates to about 0.30000000000000004 due to binary floating-point representation, so the strict comparison with 0.3 returns false."} | верно | Двоичная погрешность float: 0.1 + 0.2 = 0.30000000000000004. |
T03-L1 1.69 c | Strings | strrev() correctly reverses a UTF-8 string. | «no» Пояснение: strrev() reverses by bytes, not characters, so multibyte UTF-8 characters get their bytes scrambled and produce invalid output.
Raw{"answer": "no", "explanation": "strrev() reverses by bytes, not characters, so multibyte UTF-8 characters get their bytes scrambled and produce invalid output."} | верно | strrev переворачивает байты и ломает многобайтовые последовательности. |
T03-L2 1.53 c | Strings | str_contains('Hello world', 'world') returns true. | «yes» Пояснение: str_contains() returns true when the needle 'world' is found within the haystack 'Hello world', which it is.
Raw{"answer": "yes", "explanation": "str_contains() returns true when the needle 'world' is found within the haystack 'Hello world', which it is."} | верно | str_contains с PHP 8.0 проверяет вхождение подстроки. |
T03-L3 1.62 c | Strings | str_pad() can pad a string on the right side only. | «no» Пояснение: str_pad() can pad on the right (STR_PAD_RIGHT, the default), left (STR_PAD_LEFT), or both sides (STR_PAD_BOTH).
Raw{"answer": "no", "explanation": "str_pad() can pad on the right (STR_PAD_RIGHT, the default), left (STR_PAD_LEFT), or both sides (STR_PAD_BOTH)."} | верно | STR_PAD_LEFT / STR_PAD_BOTH меняют сторону дополнения. |
T03-L4 2.18 c | Strings | By default trim() strips only spaces, leaving tabs and newlines intact. | «no» Пояснение: PHP's trim() by default strips spaces, tabs, newlines, carriage returns, NUL bytes, and vertical tabs (\x0B), not just spaces.
Raw{"answer": "no", "explanation": "PHP's trim() by default strips spaces, tabs, newlines, carriage returns, NUL bytes, and vertical tabs (\\x0B), not just spaces."} | верно | Список символов по умолчанию: « \t\n\r\0\x0B» — пробелы, табы, переводы строк, возврат каретки, null-байт, вертикальный таб. Проверено php -r. |
T03-L5 1.93 c | Strings | How many BYTES does strlen('héllo') return for a UTF-8 string? | «6» Пояснение: strlen counts bytes, and the 'é' character occupies 2 bytes in UTF-8, so 'h' + 2 bytes + 'llo' totals 6 bytes.
Raw'héllo' has 5 characters, but é is two bytes in UTF-8 (C3 A9), so total bytes = 6. ⏎ ⏎ {"answer": 6, "explanation": "strlen counts bytes, and the 'é' character occupies 2 bytes in UTF-8, so 'h' + 2 bytes + 'llo' totals 6 bytes."} | верно | 6 букв по 2 байта: 12. |
T03-L6 1.51 c | Strings | What does substr('abcdef', -3) return? | «def» Пояснение: A negative start position counts from the end of the string, so -3 begins at the third-to-last character and returns the rest of the string.
Raw{"answer": "def", "explanation": "A negative start position counts from the end of the string, so -3 begins at the third-to-last character and returns the rest of the string."} | верно | Отрицательное смещение — с конца: def. |
T03-L7 1.62 c | Strings | ucfirst() modifies the string passed to it in place. | «no» Пояснение: PHP's ucfirst() returns a new string with the first character uppercased and does not modify the original string passed to it.
Raw{"answer": "no", "explanation": "PHP's ucfirst() returns a new string with the first character uppercased and does not modify the original string passed to it."} | верно | Строки неизменяемы; ucfirst возвращает новую строку. |
T03-L8 1.56 c | Strings | Variable interpolation works in heredoc but not in nowdoc. | «yes» Пояснение: Heredoc strings behave like double-quoted strings and interpolate variables, while nowdoc strings behave like single-quoted strings and do not.
Raw{"answer": "yes", "explanation": "Heredoc strings behave like double-quoted strings and interpolate variables, while nowdoc strings behave like single-quoted strings and do not."} | верно | Nowdoc — «одинарные кавычки» в тройном синтаксисе: текст как есть. |
T04-L1 2.06 c | Arrays | The sort() function preserves the key-to-value association of the array. | «no» Пояснение: PHP's sort() removes the existing keys and reindexes the array with sequential numeric keys; asort() preserves key-to-value association.
Raw{"answer": "no", "explanation": "PHP's sort() removes the existing keys and reindexes the array with sequential numeric keys; asort() preserves key-to-value association."} | верно | sort перенумеровывает ключи; связь сохраняет asort. |
T04-L2 1.61 c | Arrays | The string key '5' in an array is stored as the integer 5. | «yes» Пояснение: PHP converts numeric string keys that are canonical decimal integers, such as '5', into integer keys, so '5' is stored as 5.
Raw{"answer": "yes", "explanation": "PHP converts numeric string keys that are canonical decimal integers, such as '5', into integer keys, so '5' is stored as 5."} | верно | Каноничные десятичные строковые ключи приводятся к int. |
T04-L3 1.64 c | Arrays | The in_array() function uses strict comparison (===) by default. | «no» Пояснение: in_array() uses loose comparison (==) by default; strict comparison requires passing true as the third argument.
Raw{"answer": "no", "explanation": "in_array() uses loose comparison (==) by default; strict comparison requires passing true as the third argument."} | верно | По умолчанию сравнение нестрогое; строгое — третий аргумент true. |
T04-L4 1.61 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, so falsy values such as 0, '', null, false, and empty arrays are removed.
Raw{"answer": "yes", "explanation": "Without a callback, array_filter() keeps only elements that evaluate to true, so falsy values such as 0, '', null, false, and empty arrays are removed."} | верно | Убирает 0, "", null, false и пустые массивы. |
T04-L5 2.31 c | Arrays | By default, array_slice() preserves the original numeric keys of the array. | «no» Пояснение: By default, array_slice() reindexes numeric keys starting from 0; the preserve_keys parameter must be set to true to keep the original numeric keys.
Raw{"answer": "no", "explanation": "By default, array_slice() reindexes numeric keys starting from 0; the preserve_keys parameter must be set to true to keep the original numeric keys."} | верно | По умолчанию ключи перенумеровываются; сохранение — preserve_keys = true. |
T04-L6 2.69 c | Arrays | What does array_slice([10, 20, 30, 40], 1, 2) return? | «{"answer": [20, 30], "explanation": "array_slice starts at index 1 and takes 2 elements, giving 20 and 30; it re-indexes the result from 0."}» Пояснение: {"answer": [20, 30], "explanation": "array_slice starts at index 1 and takes 2 elements, giving 20 and 30; it re-indexes the result from 0."}
Raw{"answer": [20, 30], "explanation": "array_slice starts at index 1 and takes 2 elements, giving 20 and 30; it re-indexes the result from 0."} | верно парсинг: текст (фолбэк) | [20,30]; ключи перенумеровываются. |
T04-L7 2.46 c | Arrays | How many elements will count(['a' => 1] + ['a' => 9, 'b' => 2]) return? | «2» Пояснение: The `+` operator merges arrays by key, keeping the left value for 'a' and adding 'b', giving ['a' => 1, 'b' => 2] with 2 elements.
Raw{"answer": 2, "explanation": "The `+` operator merges arrays by key, keeping the left value for 'a' and adding 'b', giving ['a' => 1, 'b' => 2] with 2 elements."} | верно | Оператор + : по ключу 'a' побеждает левый; итого 2. |
T04-L8 2.16 c | Arrays | Since PHP 8.1, the spread operator [...$a, ...$b] supports arrays with string keys. | «yes» Пояснение: PHP 8.1 added support for unpacking arrays with string keys in array literals, so [...$a, ...$b] now works with associative arrays.
Raw{"answer": "yes", "explanation": "PHP 8.1 added support for unpacking arrays with string keys in array literals, so [...$a, ...$b] now works with associative arrays."} | верно | В 8.0 — только числовые ключи; 8.1 снял ограничение. |
T05-L1 2.61 c | Functions and closures | Named arguments cannot be combined with argument unpacking ...$args in a single call. | «no» Пояснение: PHP 8.1+ allows named arguments alongside unpacking, e.g. `foo(...$positional, name: 'x')` or `foo(...['a' => 1])`, as long as named arguments come after positional ones.
Raw{"answer": "no", "explanation": "PHP 8.1+ allows named arguments alongside unpacking, e.g. `foo(...$positional, name: 'x')` or `foo(...['a' => 1])`, as long as named arguments come after positional ones."} | верно | Можно: f(...$args, имя: значение). Нельзя только позиционный аргумент после распаковки. |
T05-L2 1.69 c | Functions and closures | An anonymous function without use sees variables from the outer scope. | «no» Пояснение: In PHP, a closure without a use clause cannot access variables from the enclosing scope; they must be imported with use (arrow functions being the exception, which capture by value automatically).
Raw{"answer": "no", "explanation": "In PHP, a closure without a use clause cannot access variables from the enclosing scope; they must be imported with use (arrow functions being the exception, which capture by value automatically)."} | верно | Без use внешние переменные недоступны; авто-захват только у fn. |
T05-L3 1.56 c | Functions and closures | What will func_num_args() return inside function f($a) { return func_num_args(); } when called as f(1, 2, 3)? | «3» Пояснение: func_num_args() returns the number of arguments passed to the function, which is 3 here even though only one parameter is declared.
Raw{"answer": 3, "explanation": "func_num_args() returns the number of arguments passed to the function, which is 3 here even though only one parameter is declared."} | верно | Считает переданные аргументы: 3. |
T05-L4 2.53 c | Functions and closures | The body of an arrow function fn may consist of several expressions in curly braces. | «no» Пояснение: PHP arrow functions (fn) take a single expression as their body and do not support a curly-brace block with multiple statements.
Raw{"answer": "no", "explanation": "PHP arrow functions (fn) take a single expression as their body and do not support a curly-brace block with multiple statements."} | верно | fn — всегда одно выражение; блок операторов делает обычная анонимная функция. |
T05-L5 1.94 c | Functions and closures | An arrow function fn captures outer variables by reference (lazily, at use time). | «no» Пояснение: PHP arrow functions capture outer variables by value at the moment the arrow function is created, not by reference or lazily at call time.
Raw{"answer": "no", "explanation": "PHP arrow functions capture outer variables by value at the moment the arrow function is created, not by reference or lazily at call time."} | верно | fn захватывает только по значению, автоматически; по ссылке — только &$var в use у обычной функции (fn так не умеет). |
T05-L6 1.61 c | Functions and closures | A closure declared as static function () {} does not capture $this. | «yes» Пояснение: A static closure cannot bind $this automatically from its defining scope, so it does not capture $this, and attempting to use $this inside it causes an error.
Raw{"answer": "yes", "explanation": "A static closure cannot bind $this automatically from its defining scope, so it does not capture $this, and attempting to use $this inside it causes an error."} | верно | static-замыкание отвязано от объекта: $this внутри недоступен. |
T05-L7 1.52 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 when it is created, so later reassignment of $x to 7 does not affect the captured value of 5.
Raw{"answer": 5, "explanation": "The closure captures $x by value when it is created, so later reassignment of $x to 7 does not affect the captured value of 5."} | верно | use захватывает по значению в момент создания: 5. |
T05-L8 1.55 c | Functions and closures | In weak typing mode (without strict_types), passing the string "5" to an int parameter is allowed. | «yes» Пояснение: Without strict_types, PHP coerces the numeric string "5" to the integer 5 for an int parameter.
Raw{"answer": "yes", "explanation": "Without strict_types, PHP coerces the numeric string \"5\" to the integer 5 for an int parameter."} | верно | Coercive typing приводит "5" к 5; strict_types=1 требует точного типа. |
T06-L1 1.61 c | OOP: classes and inheritance | PHP supports constructor property promotion: public function __construct(private int $x) {}. | «yes» Пояснение: Constructor property promotion, introduced in PHP 8.0, lets visibility modifiers on constructor parameters automatically declare and assign the corresponding properties.
Raw{"answer": "yes", "explanation": "Constructor property promotion, introduced in PHP 8.0, lets visibility modifiers on constructor parameters automatically declare and assign the corresponding properties."} | верно | С PHP 8.0 параметр с модификатором создаёт свойство и присваивание. |
T06-L2 1.53 c | OOP: classes and inheritance | Which keyword prevents a method from being overridden in subclasses? | «final» Пояснение: Declaring a method with the final keyword prevents subclasses from overriding it.
Raw{"answer": "final", "explanation": "Declaring a method with the final keyword prevents subclasses from overriding it."} | верно | final. |
T06-L3 1.56 c | OOP: classes and inheritance | A method declared final cannot be overridden in a subclass. | «yes» Пояснение: In PHP, declaring a method as final prevents child classes from overriding it, and attempting to do so causes a fatal error.
Raw{"answer": "yes", "explanation": "In PHP, declaring a method as final prevents child classes from overriding it, and attempting to do so causes a fatal error."} | верно | final запрещает переопределение метода и наследование класса. |
T06-L4 1.51 c | OOP: classes and inheritance | Parent properties with private visibility are accessible in a subclass. | «no» Пояснение: Private properties are only accessible within the class that declares them, so a subclass cannot access a parent's private property directly.
Raw{"answer": "no", "explanation": "Private properties are only accessible within the class that declares them, so a subclass cannot access a parent's private property directly."} | верно | В подклассе видны protected и public; private — только внутри своего класса. |
T06-L5 2.76 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» Пояснение: PHP names anonymous classes with the prefix class@anonymous (or ParentName@anonymous if it extends a parent), followed by a NUL byte and the file path and offset.
Raw{"answer": "class@anonymous", "explanation": "PHP names anonymous classes with the prefix class@anonymous (or ParentName@anonymous if it extends a parent), followed by a NUL byte and the file path and offset."} | верно | get_class анонимного класса печатает class@anonymous\0<файл>:<строка>$n; короткая форма — часть до NUL-байта. Проверено php -r (hex). |
T06-L6 2.08 c | OOP: classes and inheritance | A private parent method is not part of the inheritance contract: a child may declare a method with the same name and any visibility. | «yes» Пояснение: In PHP, private methods are not overridden by child classes, so a child can declare a same-named method with any visibility without a conflict.
Raw{"answer": "yes", "explanation": "In PHP, private methods are not overridden by child classes, so a child can declare a same-named method with any visibility without a conflict."} | верно | private-члены не наследуются — правила совместимости подписей не действуют. |
T06-L7 2.63 c | OOP: classes and inheritance | The magic method __get() is called only for non-existent properties. | «no» Пояснение: __get() is also triggered for inaccessible properties, such as private or protected ones accessed from outside the class scope, not only for non-existent properties.
Raw{"answer": "no", "explanation": "__get() is also triggered for inaccessible properties, such as private or protected ones accessed from outside the class scope, not only for non-existent properties."} | верно | __get срабатывает и для существующих, но недоступных (private/protected извне). |
T06-L8 1.5 c | OOP: classes and inheritance | What does reassigning a readonly property throw — Exception or Error? | «error» Пояснение: Reassigning an initialized readonly property throws an Error (Error: Cannot modify readonly property), not an Exception.
Raw{"answer": "Error", "explanation": "Reassigning an initialized readonly property throws an Error (Error: Cannot modify readonly property), not an Exception."} | верно | Error (readonly с 8.1); оговорка: в __clone() переинициализация допустима (8.3+). |
T07-L1 2.01 c | Interfaces, traits, enum | An interface can declare constants. | «yes» Пояснение: PHP interfaces can declare constants, which implementing classes inherit and can access, though they cannot be overridden by implementers before PHP 8.1 (final constants in 8.1+ control overriding).
Raw{"answer": "yes", "explanation": "PHP interfaces can declare constants, which implementing classes inherit and can access, though they cannot be overridden by implementers before PHP 8.1 (final constants in 8.1+ control overriding)."} | верно | Константы интерфейса наследуются реализациями. |
T07-L2 1.46 c | Interfaces, traits, enum | Which operator checks whether an object is an instance of a class or interface? | «instanceof» Пояснение: The instanceof operator checks whether an object is an instance of a specified class, interface, or class that implements it.
Raw{"answer": "instanceof", "explanation": "The instanceof operator checks whether an object is an instance of a specified class, interface, or class that implements it."} | верно | instanceof. |
T07-L3 2.02 c | Interfaces, traits, enum | An interface can declare static methods. | «yes» Пояснение: PHP interfaces can declare static method signatures, and implementing classes must define them with compatible signatures.
Raw{"answer": "yes", "explanation": "PHP interfaces can declare static method signatures, and implementing classes must define them with compatible signatures."} | верно | Реализация обязана дать статический метод с той же сигнатурой. |
T07-L4 1.75 c | Interfaces, traits, enum | The instanceof operator only checks class inheritance: it ignores interfaces. | «no» Пояснение: PHP's instanceof operator also returns true when an object's class implements the interface being checked, not just when it inherits from a class.
Raw{"answer": "no", "explanation": "PHP's instanceof operator also returns true when an object's class implements the interface being checked, not just when it inherits from a class."} | верно | instanceof возвращает true и для интерфейсов объекта. |
T07-L5 1.59 c | Interfaces, traits, enum | An interface method may have a default implementation, like a trait method. | «no» Пояснение: PHP interface methods cannot have a body or default implementation; they are only signatures, while traits are the mechanism that provides method implementations.
Raw{"answer": "no", "explanation": "PHP interface methods cannot have a body or default implementation; they are only signatures, while traits are the mechanism that provides method implementations."} | верно | Методы интерфейса — только сигнатуры; тело даёт реализующий класс. |
T07-L6 2.17 c | Interfaces, traits, enum | An abstract method in an abstract class may have protected visibility. | «yes» Пояснение: Abstract methods can be declared public or protected, but not private, since subclasses must be able to implement them.
Raw{"answer": "yes", "explanation": "Abstract methods can be declared public or protected, but not private, since subclasses must be able to implement them."} | верно | В абстрактном классе — любая видимость; в интерфейсе — только public. |
T07-L7 1.8 c | Interfaces, traits, enum | How many elements will Foo::cases() return for enum Foo { case A; case B; case C; }? | «3» Пояснение: Foo::cases() returns an array of all enum case instances, and this enum declares three cases: A, B, and C.
Raw{"answer": 3, "explanation": "Foo::cases() returns an array of all enum case instances, and this enum declares three cases: A, B, and C."} | верно | Статический метод cases(): 3. |
T07-L8 2.54 c | Interfaces, traits, enum | A trait can declare constants. | «yes» Пояснение: Traits can declare constants since PHP 8.2; earlier versions did not allow constants in traits.
Raw{"answer": "yes", "explanation": "Traits can declare constants since PHP 8.2; earlier versions did not allow constants in traits."} | верно | С PHP 8.2 трейты могут объявлять константы (RFC constants_in_traits); до 8.2 — нет. |
T08-L1 1.52 c | Exceptions and errors | The Throwable interface is a common ancestor of both Exception and Error. | «yes» Пояснение: In PHP 7 and later, Throwable is an interface implemented by both the Exception and Error classes, making it their common ancestor.
Raw{"answer": "yes", "explanation": "In PHP 7 and later, Throwable is an interface implemented by both the Exception and Error classes, making it their common ancestor."} | верно | Иерархия с PHP 7: Throwable → Exception и Throwable → Error. |
T08-L2 1.59 c | Exceptions and errors | A catch (Exception $e) block will also catch TypeError, because TypeError ultimately inherits from Exception. | «no» Пояснение: TypeError implements the Throwable interface and extends Error, not Exception, so catch (Exception $e) will not catch it.
Raw{"answer": "no", "explanation": "TypeError implements the Throwable interface and extends Error, not Exception, so catch (Exception $e) will not catch it."} | верно | TypeError наследуется от Error; catch (Exception) его не ловит. |
T08-L3 2.38 c | Exceptions and errors | The @ operator suppresses exceptions too. | «no» Пояснение: The @ operator only suppresses PHP error messages such as warnings and notices by temporarily setting error_reporting; it does not catch or suppress thrown exceptions.
Raw{"answer": "no", "explanation": "The @ operator only suppresses PHP error messages such as warnings and notices by temporarily setting error_reporting; it does not catch or suppress thrown exceptions."} | верно | @ глушит диагностику (warnings/notices), исключения не перехватывает. |
T08-L4 1.7 c | Exceptions and errors | What error class does intdiv(5, 0) throw? | «divisionbyzeroerror» Пояснение: intdiv() throws a DivisionByZeroError when the divisor is zero, as do the / and % operators in PHP 7+.
Rawintdiv(5, 0) throws DivisionByZeroError in PHP 7 and later. ⏎ ⏎ {"answer": "DivisionByZeroError", "explanation": "intdiv() throws a DivisionByZeroError when the divisor is zero, as do the / and % operators in PHP 7+."} | верно | DivisionByZeroError (иерархия Error, не Exception); php-грейдер объективен. |
T08-L5 1.64 c | Exceptions and errors | The finally block runs only if the exception was caught by a catch block. | «no» Пояснение: A finally block runs whether or not an exception was thrown or caught, including when no exception occurs or when the exception is uncaught.
Raw{"answer": "no", "explanation": "A finally block runs whether or not an exception was thrown or caught, including when no exception occurs or when the exception is uncaught."} | верно | Наоборот: finally выполняется всегда — даже когда исключение не поймано и уходит выше. Проверено php -r. |
T08-L6 2.45 c | Exceptions and errors | An exception thrown inside a finally block has no effect on the result of the try block. | «no» Пояснение: An exception thrown in a finally block replaces the try block's outcome, discarding any pending exception or return value from the try or catch.
Raw{"answer": "no", "explanation": "An exception thrown in a finally block replaces the try block's outcome, discarding any pending exception or return value from the try or catch."} | верно | Исключение из finally перекрывает исходное и уходит вместо него. |
T08-L7 1.67 c | Exceptions and errors | What does the expression (bool) new Exception('x') return? | «yes» Пояснение: Objects always cast to true in PHP, so casting an Exception object to bool gives true.
RawCasting any object to bool in PHP yields true (objects are always truthy, regardless of their properties). ⏎ ⏎ {"answer": "yes", "explanation": "Objects always cast to true in PHP, so casting an Exception object to bool gives true."} | верно | Любой объект при приведении к bool — true. Формы ответа: true или да. |
T08-L8 1.52 c | Exceptions and errors | Functions registered via register_shutdown_function() run when exit is called. | «yes» Пояснение: Shutdown functions registered with register_shutdown_function() are executed when the script ends, including when exit() is called.
Raw{"answer": "yes", "explanation": "Shutdown functions registered with register_shutdown_function() are executed when the script ends, including when exit() is called."} | верно | exit завершает скрипт, но shutdown-функции отрабатывают. |
T09-L1 1.61 c | Namespaces and autoloading | The use App\Service\Mailer; statement itself loads the class file. | «no» Пояснение: The use statement only creates an alias for a fully qualified class name at compile time; it does not load or autoload the class file, which happens only when the class is actually referenced at runtime.
Raw{"answer": "no", "explanation": "The use statement only creates an alias for a fully qualified class name at compile time; it does not load or autoload the class file, which happens only when the class is actually referenced at runtime."} | верно | use — псевдоним на этапе компиляции; файл грузит автозагрузчик при первом обращении. |
T09-L2 1.89 c | Namespaces and autoloading | What follows use to import a function (not a class): the word function or const? | «function» Пояснение: In PHP, `use function Namespace\functionName;` imports a function, while `use const` imports constants and plain `use` imports classes.
Raw{"answer": "function", "explanation": "In PHP, `use function Namespace\\functionName;` imports a function, while `use const` imports constants and plain `use` imports classes."} | верно | use function ...; (и use const для констант). |
T09-L3 1.73 c | Namespaces and autoloading | Into which file (path from src/) does the PSR-4 mapping "App\ → src/" place the class App\Controller\Api\UserController? | «src/controller/api/usercontroller.php» Пояснение: PSR-4 maps the namespace prefix App\ to src/, so the remaining namespace segments Controller\Api become directories and the class name becomes the file name with a .php extension.
Raw{"answer": "src/Controller/Api/UserController.php", "explanation": "PSR-4 maps the namespace prefix App\\ to src/, so the remaining namespace segments Controller\\Api become directories and the class name becomes the file name with a .php extension."} | верно | Остаток имени после префикса, \ → /. |
T09-L4 1.92 c | Namespaces and autoloading | Including vendor/autoload.php registers autoloaders via spl_autoload_register(). | «no» Пояснение: Including vendor/autoload.php does not itself register autoloaders; it loads Composer's autoload file, which in turn calls spl_autoload_register() (via ClassLoader::register) to register the loader, so the statement is misleadingly incomplete rather than strictly accurate.
Raw{"answer": "no", "explanation": "Including vendor/autoload.php does not itself register autoloaders; it loads Composer's autoload file, which in turn calls spl_autoload_register() (via ClassLoader::register) to register the loader, so the statement is misleadingly incomplete rather than strictly accurate."} | неверно верный: «yes» | Composer ставит автозагрузчик именно на spl_autoload_register. |
T09-L5 1.62 c | Namespaces and autoloading | The magic constant __NAMESPACE__ contains the name of the current namespace. | «yes» Пояснение: __NAMESPACE__ is a PHP magic constant that evaluates to the name of the current namespace as a string.
Raw{"answer": "yes", "explanation": "__NAMESPACE__ is a PHP magic constant that evaluates to the name of the current namespace as a string."} | верно | В корневом пространстве — пустая строка. |
T09-L6 2.15 c | Namespaces and autoloading | An unqualified class name (without a leading \) in new is resolved from the global root. | «no» Пояснение: An unqualified class name in `new` is resolved relative to the current namespace (or an imported `use` alias), not from the global root; only a leading `\` forces global resolution.
Raw{"answer": "no", "explanation": "An unqualified class name in `new` is resolved relative to the current namespace (or an imported `use` alias), not from the global root; only a leading `\` forces global resolution."} | верно | Резолвится относительно текущего namespace (с учётом импортов). |
T09-L7 1.65 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 namespace prefix App\ to the src/ directory, so the remaining namespace segments Model\User become the path src/Model/User.php.
Raw{"answer": "yes", "explanation": "PSR-4 maps the namespace prefix App\\ to the src/ directory, so the remaining namespace segments Model\\User become the path src/Model/User.php."} | верно | Остаток имени после префикса переносится в путь как есть. |
T09-L8 2.49 c | Namespaces and autoloading | A use statement may be written inside a function body — the import then applies to that function only. | «no» Пояснение: PHP's `use` import statements must appear at the top level of a file or inside a namespace block, not inside a function body; `use` inside a function only applies to closure variable binding.
Raw{"answer": "no", "explanation": "PHP's `use` import statements must appear at the top level of a file or inside a namespace block, not inside a function body; `use` inside a function only applies to closure variable binding."} | верно | use внутри тела функции — parse error; импорты файловые и компиляционные. |
T10-L1 1.99 c | References and scope | Arrays are copied on assignment rather than passed by reference. | «yes» Пояснение: In PHP, arrays are assigned by value, so assigning an array to a new variable creates a copy (implemented via copy-on-write), unlike objects, which are assigned by handle.
Raw{"answer": "yes", "explanation": "In PHP, arrays are assigned by value, so assigning an array to a new variable creates a copy (implemented via copy-on-write), unlike objects, which are assigned by handle."} | верно | Присваивание массива — копия (в движке — copy-on-write). |
T10-L2 1.53 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 appending to $b does not affect $a, which still has two elements.
Raw{"answer": 2, "explanation": "PHP arrays are copied by value on assignment, so appending to $b does not affect $a, which still has two elements."} | верно | Присваивание — копия: в $a по-прежнему 2 элемента. |
T10-L3 1.58 c | References and scope | Inside a function, user-defined global variables are inaccessible without global, $GLOBALS, or passing them as parameters. | «yes» Пояснение: In PHP, global variables are not automatically visible inside functions, so they must be accessed via the global keyword, $GLOBALS array, or passed as parameters.
Raw{"answer": "yes", "explanation": "In PHP, global variables are not automatically visible inside functions, so they must be accessed via the global keyword, $GLOBALS array, or passed as parameters."} | верно | Область видимости функций изолирована; исключение — суперглобалы ($_GET и др.). |
T10-L4 2.44 c | References and scope | unset($GLOBALS['x']) inside a function removes the global variable only for that function. | «no» Пояснение: Since PHP 8.1, $GLOBALS is a read-only copy, but unset($GLOBALS['x']) still removes the global variable itself for all code, not just the function.
Raw{"answer": "no", "explanation": "Since PHP 8.1, $GLOBALS is a read-only copy, but unset($GLOBALS['x']) still removes the global variable itself for all code, not just the function."} | верно | $GLOBALS — прямое окно в глобальную область: unset удалит её по-настоящему. |
T10-L5 1.63 c | References and scope | What will this print: function inc(&$x) { $x++; } $n = 5; inc($n); echo $n; | «6» Пояснение: The parameter $x is passed by reference, so incrementing it changes the original variable $n from 5 to 6.
Raw{"answer": 6, "explanation": "The parameter $x is passed by reference, so incrementing it changes the original variable $n from 5 to 6."} | верно | Ссылка меняет оригинал: 6. |
T10-L6 2.63 c | References and scope | A foreach over an array (by value) works with the "live" array: changes to the array inside the loop are visible in the same pass. | «no» Пояснение: A by-value foreach iterates over a copy of the array, so changes made to the original array inside the loop are not seen during that pass.
Raw{"answer": "no", "explanation": "A by-value foreach iterates over a copy of the array, so changes made to the original array inside the loop are not seen during that pass."} | верно | По значению foreach итерирует копию-снимок. |
T10-L7 1.53 c | References and scope | A static property belongs to each instance separately: changes in one object are not visible in others. | «no» Пояснение: A static property belongs to the class itself and is shared by all instances, so a change made through one object is visible to all others.
Raw{"answer": "no", "explanation": "A static property belongs to the class itself and is shared by all instances, so a change made through one object is visible to all others."} | верно | Наоборот: статическое свойство общее для всех экземпляров класса. Проверено php -r. |
T10-L8 2.05 c | References and scope | An array can have a boolean key true, and it will be stored as bool. | «no» Пояснение: PHP casts boolean array keys to integers, so true becomes key 1 and is not stored as a bool.
Raw{"answer": "no", "explanation": "PHP casts boolean array keys to integers, so true becomes key 1 and is not stored as a bool."} | верно | Булев ключ приводится к int: true → 1, false → 0. |
T11-L1 1.67 c | Generators, iterators, SPL | Inside a generator, return with a value can be used, and it becomes available via $gen->getReturn(). | «yes» Пояснение: Since PHP 7.0, a generator can use return with a value, which is retrieved after completion via $gen->getReturn().
Raw{"answer": "yes", "explanation": "Since PHP 7.0, a generator can use return with a value, which is retrieved after completion via $gen->getReturn()."} | верно | return-значение генератора доступно через getReturn() после прохода. |
T11-L2 1.69 c | Generators, iterators, SPL | A fully consumed generator can be rewound with rewind() and traversed again. | «no» Пояснение: PHP generators cannot be rewound after they have advanced past the first yield; calling rewind() then throws an Exception 'Cannot rewind a generator that was already run'.
Raw{"answer": "no", "explanation": "PHP generators cannot be rewound after they have advanced past the first yield; calling rewind() then throws an Exception 'Cannot rewind a generator that was already run'."} | верно | Генератор одноразовый: rewind после начала итерации бросает Exception. |
T11-L3 1.59 c | Generators, iterators, SPL | The yield from construct delegates traversal to another generator or iterable. | «yes» Пояснение: The yield from expression delegates iteration to a sub-generator or any iterable, passing its values through to the caller.
Raw{"answer": "yes", "explanation": "The yield from expression delegates iteration to a sub-generator or any iterable, passing its values through to the caller."} | верно | yield from проксирует значения, ключи и return-значение внутреннего генератора. |
T11-L4 1.98 c | Generators, iterators, SPL | What does get_class(g()) return for function g() { yield 1; }? | «generator» Пояснение: Calling a function that contains yield returns an instance of the built-in Generator class, so get_class returns its name.
Raw{"answer": "Generator", "explanation": "Calling a function that contains yield returns an instance of the built-in Generator class, so get_class returns its name."} | верно | Функция с yield возвращает Generator. |
T11-L5 2.3 c | Generators, iterators, SPL | How many elements will count(iterator_to_array((function () { yield from [1, 2, 3]; })())) return? | «3» Пояснение: The generator yields the three array elements via yield from, and iterator_to_array preserves their keys 0, 1, 2 with no collisions, so the count is 3.
Raw{"answer": 3, "explanation": "The generator yields the three array elements via yield from, and iterator_to_array preserves their keys 0, 1, 2 with no collisions, so the count is 3."} | верно | yield from делегирует все 3 элемента. |
T11-L6 1.76 c | Generators, iterators, SPL | The SplStack class implements a FIFO queue. | «no» Пояснение: SplStack is a LIFO (last in, first out) structure; the FIFO queue behavior belongs to SplQueue.
Raw{"answer": "no", "explanation": "SplStack is a LIFO (last in, first out) structure; the FIFO queue behavior belongs to SplQueue."} | верно | SplStack — стек LIFO; очередь FIFO — SplQueue. |
T11-L7 1.56 c | Generators, iterators, SPL | ArrayIterator allows wrapping an array and traversing it via the Iterator interface. | «yes» Пояснение: ArrayIterator implements the SeekableIterator, Traversable and Iterator interfaces, letting you wrap an array (or object) and iterate over it with foreach or Iterator methods.
Raw{"answer": "yes", "explanation": "ArrayIterator implements the SeekableIterator, Traversable and Iterator interfaces, letting you wrap an array (or object) and iterate over it with foreach or Iterator methods."} | верно | Объектная обёртка над массивом. |
T11-L8 1.99 c | Generators, iterators, SPL | An ArrayObject instance cannot be traversed with foreach. | «no» Пояснение: ArrayObject implements IteratorAggregate (and Traversable), so it can be traversed with foreach.
Raw{"answer": "no", "explanation": "ArrayObject implements IteratorAggregate (and Traversable), so it can be traversed with foreach."} | верно | ArrayObject реализует IteratorAggregate — foreach по нему работает. |
T12-L1 1.69 c | Configuration and security | password_hash() generates a salt automatically — passing one separately is not needed. | «yes» Пояснение: PHP's password_hash() automatically generates a cryptographically secure random salt and embeds it in the resulting hash, so no separate salt needs to be supplied (and the old salt option is deprecated/removed).
Raw{"answer": "yes", "explanation": "PHP's password_hash() automatically generates a cryptographically secure random salt and embeds it in the resulting hash, so no separate salt needs to be supplied (and the old salt option is deprecated/removed)."} | верно | Соль встраивается в строку результата; параметр salt устарел. |
T12-L2 2.07 c | Configuration and security | In PHP 8, PASSWORD_DEFAULT is md5 with an automatically added salt. | «no» Пояснение: PASSWORD_DEFAULT currently refers to the bcrypt algorithm (and may change over time), not md5, which is not suitable for password hashing.
Raw{"answer": "no", "explanation": "PASSWORD_DEFAULT currently refers to the bcrypt algorithm (and may change over time), not md5, which is not suitable for password hashing."} | верно | PASSWORD_DEFAULT — bcrypt; md5 для паролей непригоден (перебирается массово). |
T12-L3 1.58 c | Configuration and security | What does password_verify('secret', password_hash('secret', PASSWORD_DEFAULT)) return? | «yes» Пояснение: password_hash creates a salted hash of 'secret', and password_verify checks the plaintext against that hash, returning true.
Raw{"answer": "yes", "explanation": "password_hash creates a salted hash of 'secret', and password_verify checks the plaintext against that hash, returning true."} | верно | Соль и хеш в одной строке: true (форма ответа: true или да). |
T12-L4 1.53 c | Configuration and security | strip_tags() protects against SQL injection. | «no» Пояснение: strip_tags() removes HTML and PHP tags for output sanitization; it does not protect against SQL injection, which requires prepared statements or parameterized queries.
Raw{"answer": "no", "explanation": "strip_tags() removes HTML and PHP tags for output sanitization; it does not protect against SQL injection, which requires prepared statements or parameterized queries."} | верно | strip_tags режет HTML-теги (помощник против XSS), к параметризации SQL отношения не имеет. |
T12-L5 1.61 c | Configuration and security | session_regenerate_id() is used to protect against session fixation upon user login. | «yes» Пояснение: Calling session_regenerate_id() after login issues a new session ID, preventing an attacker's fixed session ID from being reused by the authenticated user.
Raw{"answer": "yes", "explanation": "Calling session_regenerate_id() after login issues a new session ID, preventing an attacker's fixed session ID from being reused by the authenticated user."} | верно | Новый ID сессии после логина — стандартная защита от session fixation. |
T12-L6 1.56 c | Configuration and security | Which built-in function returns the SAPI name (e.g., cli)? | «php_sapi_name» Пояснение: php_sapi_name() returns the server API (SAPI) name the PHP process is running under, such as "cli" or "apache2handler".
Raw{"answer": "php_sapi_name", "explanation": "php_sapi_name() returns the server API (SAPI) name the PHP process is running under, such as \"cli\" or \"apache2handler\"."} | верно | php_sapi_name(). |
T12-L7 2.47 c | Configuration and security | session_destroy() deletes session data on the server but not the cookie in the user's browser. | «yes» Пояснение: session_destroy() removes the session data stored on the server, but the session cookie remains in the browser unless it is explicitly expired, for example with setcookie().
Raw{"answer": "yes", "explanation": "session_destroy() removes the session data stored on the server, but the session cookie remains in the browser unless it is explicitly expired, for example with setcookie()."} | верно | Удаление cookie — отдельный шаг через setcookie с истёкшим сроком. |
T12-L8 1.67 c | Configuration and security | Without calling session_start(), the $_SESSION array is automatically populated with session data. | «no» Пояснение: Without session_start() (or session.auto_start enabled), PHP does not load session data, so $_SESSION is not populated.
Raw{"answer": "no", "explanation": "Without session_start() (or session.auto_start enabled), PHP does not load session data, so $_SESSION is not populated."} | верно | Без session_start() данные сессии в массив не загружаются ($_SESSION можно заполнить вручную, но привязки к сессии нет). |
VC-L1 2.15 c | PHP 8.4–8.5 | In which PHP version was the array_find() function introduced? | «8.4» Пояснение: array_find() was added in PHP 8.4 as part of the new array search functions alongside array_find_key(), array_any(), and array_all().
Raw{"answer": "8.4", "explanation": "array_find() was added in PHP 8.4 as part of the new array search functions alongside array_find_key(), array_any(), and array_all()."} | верно | PHP 8.4 (RFC array_find). |
VC-L2 1.51 c | PHP 8.4–8.5 | Property hooks (get/set right in the property declaration) landed in PHP 8.4. | «yes» Пояснение: Property hooks were introduced in PHP 8.4, allowing get and set logic to be declared directly within a property declaration.
Raw{"answer": "yes", "explanation": "Property hooks were introduced in PHP 8.4, allowing get and set logic to be declared directly within a property declaration."} | верно | Property hooks — PHP 8.4 (ноябрь 2024). |
VC-L3 1.6 c | PHP 8.4–8.5 | Asymmetric visibility (public private(set) string $name) appeared in PHP 8.4. | «yes» Пояснение: PHP 8.4 introduced asymmetric visibility, allowing separate read and write visibility such as public private(set) for properties.
Raw{"answer": "yes", "explanation": "PHP 8.4 introduced asymmetric visibility, allowing separate read and write visibility such as public private(set) for properties."} | верно | Asymmetric visibility v2 — PHP 8.4. |
VC-L4 2.53 c | PHP 8.4–8.5 | In which PHP version was the #[\NoDiscard] attribute introduced? Answer with the version number. | «8.5» Пояснение: The #[\NoDiscard] attribute, which warns when a function's return value is ignored, was added in PHP 8.5.
Raw{"answer": "8.5", "explanation": "The #[\\NoDiscard] attribute, which warns when a function's return value is ignored, was added in PHP 8.5."} | верно | #[\NoDiscard] — PHP 8.5 (marking return values as important). |
VC-L5 2.44 c | PHP 8.4–8.5 | In which PHP version did the pipe operator |> first appear? Answer with the version number. | «8.5» Пояснение: The pipe operator |> was accepted for PHP 8.5 after earlier proposals, and it was not part of PHP 8.4.
Raw{"answer": "8.5", "explanation": "The pipe operator |> was accepted for PHP 8.5 after earlier proposals, and it was not part of PHP 8.4."} | верно | Pipe operator — PHP 8.5 (2025). |
VC-L6 3.74 c | PHP 8.4–8.5 | In which PHP version did clone-with — the syntax clone($obj, ['x' => 1]) — appear? Answer with the version number. | «8.5» Пояснение: The clone-with feature, which lets clone() take an array of property overrides, was added in PHP 8.5.
Raw{"answer": "8.5", "explanation": "The clone-with feature, which lets clone() take an array of property overrides, was added in PHP 8.5."} | верно | Clone with v2 — PHP 8.5. |
VC-L7 2.65 c | PHP 8.4–8.5 | In which PHP version were the array_first() and array_last() functions introduced? | «8.5» Пояснение: array_first() and array_last() were added in PHP 8.5, as part of the array helper functions introduced with that release.
Raw{"answer": "8.5", "explanation": "array_first() and array_last() were added in PHP 8.5, as part of the array helper functions introduced with that release."} | верно | PHP 8.5. |
VC-L8 3.72 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. | «none» Пояснение: As far as I know, the Partial Function Application v2 RFC was not adopted into any PHP version, so no version applies.
Raw{"answer": "none", "explanation": "As far as I know, the Partial Function Application v2 RFC was not adopted into any PHP version, so no version applies."} | неверно верный: «8.6» | PFA v2 принят 05.12.2025 (33-0-0), реализован в PHP 8.6. |
VF-L1 4.4 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.5» Пояснение: The clamp_v2 RFC targeted PHP 8.5, the release after 8.4, though I'm not certain it was ultimately accepted.
Raw{"answer": 8.5, "explanation": "The clamp_v2 RFC targeted PHP 8.5, the release after 8.4, though I'm not certain it was ultimately accepted."} | неверно верный: «8.6» | По данным владельца (wiki.php.net/rfc): clamp_v2 — 8.6; clamp() в 8.5.11 отсутствует (косвенное подтверждение). Дата-якорь делает клетку монотонной. |
VF-L2 3.79 c | PHP: 8.6+ and the future | RFC Context Managers v2 has already been adopted in PHP (as of 2026-11-07). | «no» Пояснение: I have no record of a 'Context Managers v2' RFC being adopted into PHP, and I can't verify events up to the stated date, so I assume it has not been adopted.
Raw{"answer": "no", "explanation": "I have no record of a 'Context Managers v2' RFC being adopted into PHP, and I can't verify events up to the stated date, so I assume it has not been adopted."} | верно | На 06.11.2026 — в обсуждении (создан 2026-10-23); не принят. |
VF-L3 3.94 c | PHP: 8.6+ and the future | RFC Bound-Erased Generic Types (generics) was declined in 2026. | «no» Пояснение: I'm not aware of any PHP RFC titled 'Bound-Erased Generic Types' being declined in 2026, and I can't verify that this event occurred.
Raw{"answer": "no", "explanation": "I'm not aware of any PHP RFC titled 'Bound-Erased Generic Types' being declined in 2026, and I can't verify that this event occurred."} | неверно верный: «yes» | Голосование завершилось 2026-06-28: отклонён (wiki.php.net/rfc). |
VF-L4 3.51 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» Пояснение: I'm not aware of any accepted RFC making ZTS (thread-safe builds) the default; ZTS remains an opt-in build, and I can't verify events after my knowledge cutoff.
Raw{"answer": "no", "explanation": "I'm not aware of any accepted RFC making ZTS (thread-safe builds) the default; ZTS remains an opt-in build, and I can't verify events after my knowledge cutoff."} | верно | Такого принятого RFC нет на дату якоря; якорь делает клетку монотонной — при принятии RFC позже клетка не перевернётся. |
VF-L5 2.32 c | PHP: 8.6+ and the future | As of PHP 8.5, generics (parameterized types) are still absent. | «yes» Пояснение: PHP 8.5 does not include generics; the generics RFCs have not been accepted, so PHP still lacks parameterized types.
Raw{"answer": "yes", "explanation": "PHP 8.5 does not include generics; the generics RFCs have not been accepted, so PHP still lacks parameterized types."} | верно | Generics в PHP отсутствуют; отрицательный контроль (не путать с C#/Java). |
VF-L6 4.02 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). | «no» Пояснение: PHP 8.5 was released in November 2025, but I can't confirm an official PHP 8.6 release schedule or a GA date of 2026-11-19, so the claim can't be verified as true.
Raw{"answer": "no", "explanation": "PHP 8.5 was released in November 2025, but I can't confirm an official PHP 8.6 release schedule or a GA date of 2026-11-19, so the claim can't be verified as true."} | неверно верный: «yes» | 8.5 — релиз осени 2025; 8.6 GA 19.11.2026 (wiki.php.net/todo/php86). Дата снимка — 06.11.2026. |
VF-L7 1.61 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 developed but abandoned due to Unicode-related difficulties and was never released; the next major version after PHP 5.6 was PHP 7.0.
Raw{"answer": "yes", "explanation": "PHP 6 was developed but abandoned due to Unicode-related difficulties and was never released; the next major version after PHP 5.6 was PHP 7.0."} | верно | Исторический факт: ветка 6 не была релизнута. |
VF-L8 3.63 c | PHP: 8.6+ and the future | The RFC adding the #[\Deprecated] attribute to the core was adopted. | «yes» Пояснение: The #[\Deprecated] attribute was added to PHP core in version 8.4 after its RFC was accepted, letting code mark functions, methods, and constants as deprecated.
Raw{"answer": "yes", "explanation": "The #[\\Deprecated] attribute was added to PHP core in version 8.4 after its RFC was accepted, letting code mark functions, methods, and constants as deprecated."} | верно | #[\Deprecated] — принят, реализован в PHP 8.4. |
T25-L1 1.64 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 architectures, source code dependencies point inward toward the domain at the center, so inner layers have no knowledge of outer layers.
Raw{"answer": "yes", "explanation": "In clean and onion architectures, source code dependencies point inward toward the domain at the center, so inner layers have no knowledge of outer layers."} | верно | Чистая (Robert C. Martin), луковичная (Jeffrey Palermo) и гексагональная (ports & adapters) — варианты одной идеи: зависимости направлены внутрь, к домену. Слоями в проекте следит deptrac. |
T25-L2 1.77 c | Clean architecture | Domain entities import neither Doctrine nor Symfony — only the language and, possibly, the standard library. | «yes» Пояснение: Keeping domain entities free of framework and ORM imports (only PHP language and standard library) is a core principle of clean/hexagonal architecture.
Raw{"answer": "yes", "explanation": "Keeping domain entities free of framework and ORM imports (only PHP language and standard library) is a core principle of clean/hexagonal architecture."} | верно | Изоляция домена от инфраструктуры; deptrac в проекте как раз следит за слоями. |
T25-L3 2.45 c | Clean architecture | Controllers and Twig templates belong to the business-logic layer because they are the ones calling use cases. | «no» Пояснение: Controllers and Twig templates belong to the presentation (UI/infrastructure) layer, not the business-logic layer; they merely invoke use cases that live in the application or domain layer.
Raw{"answer": "no", "explanation": "Controllers and Twig templates belong to the presentation (UI/infrastructure) layer, not the business-logic layer; they merely invoke use cases that live in the application or domain layer."} | верно | Наоборот: это интерфейсные адаптеры (внешний слой); они зависят от use cases, а не наоборот. |
T25-L4 1.58 c | Clean architecture | What sits at the very center of the onion architecture? | «domain model» Пояснение: In onion architecture, the domain model (entities and domain logic) forms the innermost core, with layers like application services and infrastructure surrounding it.
Raw{"answer": "Domain model", "explanation": "In onion architecture, the domain model (entities and domain logic) forms the innermost core, with layers like application services and infrastructure surrounding it."} | верно | Центральное кольцо — Domain Model: сущности и бизнес-правила без зависимостей; далее Domain Services → Application Services → Infrastructure/UI/Tests (Palermo). |
T25-L5 1.58 c | Clean architecture | Layer boundary violations can be caught automatically: a layer-dependency analyzer (e.g. deptrac) fails on a forbidden call. | «yes» Пояснение: Tools like deptrac analyze class dependencies against configured layer rules and report or fail the build when a forbidden dependency exists.
Raw{"answer": "yes", "explanation": "Tools like deptrac analyze class dependencies against configured layer rules and report or fail the build when a forbidden dependency exists."} | верно | depfile.yaml в проекте TasK: CI проверяет правила слоёв на каждом пайплайне. |
T25-L6 1.61 c | Clean architecture | A use case (interactor) may accept an HTTP request or an EntityManager as arguments — it is simpler that way. | «no» Пояснение: In Clean Architecture, use cases should not depend on framework or infrastructure concerns like HTTP requests or EntityManager; they should receive plain input data and depend on abstractions.
Raw{"answer": "no", "explanation": "In Clean Architecture, use cases should not depend on framework or infrastructure concerns like HTTP requests or EntityManager; they should receive plain input data and depend on abstractions."} | верно | Use case принимает DTO и порты; привязка к HTTP/ORM протекает инфраструктуру во внутренние слои. |
T25-L7 1.61 c | Clean architecture | What is the component called that provides a collection of aggregates/entities while hiding the storage mechanism behind an interface? | «repository» Пояснение: A repository provides an in-memory-like collection interface for aggregates or entities while abstracting away the underlying persistence mechanism.
Raw{"answer": "Repository", "explanation": "A repository provides an in-memory-like collection interface for aggregates or entities while abstracting away the underlying persistence mechanism."} | верно | Repository pattern (DDD/Evans); в проекте — Doctrine-репозитории за портами. |
T25-L8 1.72 c | Clean architecture | In clean architecture, swapping PostgreSQL for another database touches only the outer layer — the domain and use cases stay unchanged. | «yes» Пояснение: In clean architecture, the domain and use cases depend only on abstractions (ports/interfaces), so the database is an outer-layer detail that can be replaced by a new adapter without changing inner layers.
Raw{"answer": "yes", "explanation": "In clean architecture, the domain and use cases depend only on abstractions (ports/interfaces), so the database is an outer-layer detail that can be replaced by a new adapter without changing inner layers."} | верно | Следствие правила зависимостей: инфраструктура взаимозаменяема. |
T26-L1 1.68 c | DDD | In DDD, an aggregate is just another name for a database table. | «no» Пояснение: In Domain-Driven Design, an aggregate is a cluster of domain objects treated as a single unit for data changes, and it is not the same as a database table, though it may be persisted across one or more tables.
Raw{"answer": "no", "explanation": "In Domain-Driven Design, an aggregate is a cluster of domain objects treated as a single unit for data changes, and it is not the same as a database table, though it may be persisted across one or more tables."} | верно | Агрегат — кластер объектов с границей согласованности (транзакционной вокруг корня); таблица — деталь хранения. |
T26-L2 1.8 c | DDD | A Value Object is immutable and compared by the values of its fields, not by identity. | «yes» Пояснение: Value Objects are defined by their attribute values rather than a unique identity, and they are immutable, so equality is based on field values.
Raw{"answer": "yes", "explanation": "Value Objects are defined by their attribute values rather than a unique identity, and they are immutable, so equality is based on field values."} | верно | Классика Evans: Money, Email; равенство структурное. |
T26-L3 1.7 c | DDD | What is the single external entry point of an aggregate, through which all changes must go, called? | «aggregate root» Пояснение: In Domain-Driven Design, the aggregate root is the single entry point through which all external changes to an aggregate must pass.
Raw{"answer": "Aggregate Root", "explanation": "In Domain-Driven Design, the aggregate root is the single entry point through which all external changes to an aggregate must pass."} | верно | Aggregate Root: внешние объекты ссылаются только на корень; он защищает инварианты агрегата. |
T26-L4 1.65 c | DDD | In DDD, a repository is declared for an aggregate (its root), not for every entity. | «yes» Пояснение: In Domain-Driven Design, repositories are defined per aggregate root, since the root is the only entry point for accessing and modifying objects within the aggregate.
Raw{"answer": "yes", "explanation": "In Domain-Driven Design, repositories are defined per aggregate root, since the root is the only entry point for accessing and modifying objects within the aggregate."} | верно | Репозиторий корня хранит границу согласованности агрегата; вложенные сущности доступны только через корень. |
T26-L5 1.65 c | DDD | Ubiquitous language is the model's shared language common to developers and domain experts. | «yes» Пояснение: In Domain-Driven Design, the ubiquitous language is the shared vocabulary used by developers and domain experts, derived from and reflected in the domain model.
Raw{"answer": "yes", "explanation": "In Domain-Driven Design, the ubiquitous language is the shared vocabulary used by developers and domain experts, derived from and reflected in the domain model."} | верно | Evans: язык из требований переходит в имена классов и методов. |
T26-L6 3.63 c | DDD | What is the boundary called within which a model and its language are consistent, while outside the same words mean other models? | «context» Пояснение: The question describes the boundary within which a model and its language stay consistent, which is the context in which the words have their intended meaning.
Raw{"answer": "context", "explanation": "The question describes the boundary within which a model and its language stay consistent, which is the context in which the words have their intended meaning."} | неверно верный: «bounded context» | Bounded Context; «Заказ» в биллинге и в доставке — разные модели. |
T26-L7 1.68 c | DDD | An anemic model (objects with only getters/setters, logic in services) is the recommended DDD style. | «no» Пояснение: DDD advocates a rich domain model where behavior and business rules live within entities and value objects, and the anemic model (getters/setters with logic in services) is widely considered an anti-pattern.
Raw{"answer": "no", "explanation": "DDD advocates a rich domain model where behavior and business rules live within entities and value objects, and the anemic model (getters/setters with logic in services) is widely considered an anti-pattern."} | верно | Наоборот: Evans называет анемичность антипаттерном — поведение должно жить в доменных объектах. |
T26-L8 1.62 c | DDD | Bounded context means each context has its own model: the same concept in different contexts is a different class. | «yes» Пояснение: In Domain-Driven Design, a bounded context delimits where a particular model applies, so the same real-world concept (e.g., a Customer) can be modeled as different classes in different contexts.
Raw{"answer": "yes", "explanation": "In Domain-Driven Design, a bounded context delimits where a particular model applies, so the same real-world concept (e.g., a Customer) can be modeled as different classes in different contexts."} | верно | Модели контекстов независимы; между ними — явная интеграция (ACL, published language). |
T13-L1 3.82 c | Symfony | Services in the Symfony DI container are created lazily by default — on first use. | «yes» Пояснение: The Symfony DI container instantiates a service only when it is first requested, unless it is explicitly marked as lazy-proxied or eagerly needed by another service.
Raw{"answer": "yes", "explanation": "The Symfony DI container instantiates a service only when it is first requested, unless it is explicitly marked as lazy-proxied or eagerly needed by another service."} | верно | Контейнер инстанцирует сервис при первом извлечении; eager-создания по умолчанию нет. |
T13-L2 1.63 c | Symfony | Which Symfony console command lists all registered routes? | «php bin/console debug:router» Пояснение: The debug:router command (alias for debug:route in older versions) lists all registered routes in a Symfony application.
Raw{"answer": "php bin/console debug:router", "explanation": "The debug:router command (alias for debug:route in older versions) lists all registered routes in a Symfony application."} | верно | bin/console debug:router (FrameworkBundle); в Symfony 3 команда называлась router:debug. |
T13-L3 1.69 c | Symfony | Symfony autowiring requires manually declaring every service in services.yaml. | «no» Пояснение: Symfony's autowiring and autoconfiguration let services be registered automatically via resource loading in services.yaml, so manual declaration of every service is not required.
Raw{"answer": "no", "explanation": "Symfony's autowiring and autoconfiguration let services be registered automatically via resource loading in services.yaml, so manual declaration of every service is not required."} | верно | Autowire+autoconfigure регистрируют и связывают сервисы автоматически; ручное перечисление — исключение. |
T13-L4 1.69 c | Symfony | Twig templates are compiled into PHP classes and cached between requests. | «yes» Пояснение: Twig compiles templates into PHP classes, which are stored in a cache directory and reused across requests until the template changes.
Raw{"answer": "yes", "explanation": "Twig compiles templates into PHP classes, which are stored in a cache directory and reused across requests until the template changes."} | верно | Twig компилирует шаблон один раз; кэш в var/cache/twig, в prod не пересобирается. |
T13-L5 2.59 c | Symfony | In the Symfony dev environment the DI container is rebuilt only after tracked files change, not on every request. | «yes» Пояснение: In debug mode, Symfony checks the container's tracked resource files for changes and rebuilds the cached container only when one of them has been modified, not on every request.
Raw{"answer": "yes", "explanation": "In debug mode, Symfony checks the container's tracked resource files for changes and rebuilds the cached container only when one of them has been modified, not on every request."} | верно | Kernel проверяет freshness ресурсов (конфиги, классы); иначе переиспользуется кэш контейнера. |
T13-L6 1.87 c | Symfony | Which environment variable selects the active Symfony environment (dev/prod)? | «app_env» Пояснение: Symfony reads the APP_ENV environment variable (typically set in .env) to determine the active environment such as dev or prod.
Raw{"answer": "APP_ENV", "explanation": "Symfony reads the APP_ENV environment variable (typically set in .env) to determine the active environment such as dev or prod."} | верно | APP_ENV в .env; APP_DEBUG — отдельный флаг отладки. |
T13-L7 2.26 c | Symfony | A controller method can be private — Symfony routing works with any method of the class. | «no» Пояснение: Symfony must be able to call the controller action, so it has to be public; private or protected methods are not callable by the router and will fail.
Raw{"answer": "no", "explanation": "Symfony must be able to call the controller action, so it has to be public; private or protected methods are not callable by the router and will fail."} | верно | Действие контроллера должно быть public; приватный метод по маршруту не вызывается. |
T13-L8 2.37 c | Symfony | Event subscribers always receive events before listeners, because the interface gives them priority. | «no» Пояснение: Event subscribers have no inherent priority over listeners; execution order is determined by the priority values assigned to each registered listener or subscriber method.
Raw{"answer": "no", "explanation": "Event subscribers have no inherent priority over listeners; execution order is determined by the priority values assigned to each registered listener or subscriber method."} | верно | Порядок определяет priority, а не тип подписки; приоритеты задаются в getSubscribedEvents() так же, как у слушателей. |
T22-L1 3.71 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 Guard authenticator system, and authentication is now handled by authenticators implementing AuthenticatorInterface.
Raw{"answer": "yes", "explanation": "Symfony 6.0 removed the Guard authenticator system, and authentication is now handled by authenticators implementing AuthenticatorInterface."} | верно | Guard объявлен устаревшим в 5.3 и удалён в 6.0; в проекте symfony/security-bundle 8.1. |
T22-L2 1.7 c | Symfony: Security and forms | Which Symfony attribute checks a role/permission right on a controller method (403 without it)? | «isgranted» Пояснение: The #[IsGranted] attribute (Symfony\Component\Security\Http\Attributes\IsGranted) checks a role or permission on a controller and throws an access denied exception (403) when it fails.
Raw{"answer": "IsGranted", "explanation": "The #[IsGranted] attribute (Symfony\\Component\\Security\\Http\\Attributes\\IsGranted) checks a role or permission on a controller and throws an access denied exception (403) when it fails."} | верно | #[IsGranted('ROLE_ADMIN')]; атрибут из symfony/security-http. |
T22-L3 1.57 c | Symfony: Security and forms | Voters are Symfony's mechanism for checking access to a specific object: isGranted('EDIT', $post). | «yes» Пояснение: Symfony voters evaluate whether a user has a given attribute (such as EDIT) on a specific subject object, and isGranted('EDIT', $post) invokes them for that purpose.
Raw{"answer": "yes", "explanation": "Symfony voters evaluate whether a user has a given attribute (such as EDIT) on a specific subject object, and isGranted('EDIT', $post) invokes them for that purpose."} | верно | VoterInterface->vote(); docs Symfony — Voters. |
T22-L4 3.7 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 6.0 removed support for Doctrine annotations in favour of PHP 8 attributes, so Symfony 7 validation constraints are declared with attributes such as #[Assert\NotBlank].
Raw{"answer": "yes", "explanation": "Symfony 6.0 removed support for Doctrine annotations in favour of PHP 8 attributes, so Symfony 7 validation constraints are declared with attributes such as #[Assert\\NotBlank]."} | верно | Докблок-аннотации удалены в Symfony 7.0; стандарт — атрибуты. В проекте symfony/validator 8.1. |
T22-L5 2.21 c | Symfony: Security and forms | CSRF protection of Symfony forms is enabled by default: the form validates the token on submission. | «yes» Пояснение: Symfony enables CSRF protection for forms by default, and the form validates the submitted CSRF token automatically (configurable via the csrf_protection option).
Raw{"answer": "yes", "explanation": "Symfony enables CSRF protection for forms by default, and the form validates the submitted CSRF token automatically (configurable via the csrf_protection option)."} | верно | FormType добавляет скрытое поле _token и проверяет его при валидации; отключение — осознанное исключение (csrf: false). |
T22-L6 1.54 c | Symfony: Security and forms | Form validation in Symfony runs server-side even if the client-side (HTML5) checks passed. | «yes» Пояснение: Symfony's form validation constraints are enforced on the server when the form is submitted, regardless of any HTML5 client-side validation that may have passed.
Raw{"answer": "yes", "explanation": "Symfony's form validation constraints are enforced on the server when the form is submitted, regardless of any HTML5 client-side validation that may have passed."} | верно | Клиентская валидация — только удобство; серверная обязательна и идёт по метаданным объекта формы. |
T22-L7 1.76 c | Symfony: Security and forms | Which Symfony maker command generates a form class (FormType)? | «make:form» Пояснение: The Symfony MakerBundle command php bin/console make:form generates a new form type class.
Raw{"answer": "make:form", "explanation": "The Symfony MakerBundle command php bin/console make:form generates a new form type class."} | верно | bin/console make:form (symfony/maker-bundle — в проекте). |
T22-L8 1.67 c | Symfony: Security and forms | Symfony stores the user's password in the session in plain text. | «no» Пояснение: Symfony's security component does not store the plain-text password in the session; it stores the authenticated user (serialized, with the password typically hashed) and can erase credentials via eraseCredentials().
Raw{"answer": "no", "explanation": "Symfony's security component does not store the plain-text password in the session; it stores the authenticated user (serialized, with the password typically hashed) and can erase credentials via eraseCredentials()."} | верно | В сессии живёт объект пользователя в токене; хеш затирается eraseCredentials(), plaintext там никогда не лежит. |
T23-L1 1.86 c | Symfony: configuration and services | Symfony bundle configuration lives in config/packages — one file per bundle or topic. | «yes» Пояснение: Symfony stores bundle configuration in config/packages, typically with one YAML (or PHP/XML) file per bundle or topic, such as framework.yaml or doctrine.yaml.
Raw{"answer": "yes", "explanation": "Symfony stores bundle configuration in config/packages, typically with one YAML (or PHP/XML) file per bundle or topic, such as framework.yaml or doctrine.yaml."} | верно | Стандартная структура (config/packages/*.yaml); перегрузка — config/packages/<env>. |
T23-L2 2.73 c | Symfony: configuration and services | The .env file with dev defaults is committed to the repository, while real secrets live in the non-committed .env.local. | «yes» Пояснение: This matches the Symfony convention: .env is committed with default values, and .env.local (git-ignored) holds machine-specific overrides and real secrets.
Raw{"answer": "yes", "explanation": "This matches the Symfony convention: .env is committed with default values, and .env.local (git-ignored) holds machine-specific overrides and real secrets."} | верно | symfony/dotenv: .env — общий безопасный набор значений; локальные секреты — .env.local (gitignored) или secrets-хранилище. |
T23-L3 1.53 c | Symfony: configuration and services | Which Symfony command lists the container's registered services and their aliases? | «debug:container» Пояснение: The php bin/console debug:container command lists all registered services, including their aliases.
Raw{"answer": "debug:container", "explanation": "The php bin/console debug:container command lists all registered services, including their aliases."} | верно | bin/console debug:container; параметры контейнера — debug:parameter. |
T23-L4 3.75 c | Symfony: configuration and services | The Symfony container allows changing parameters at runtime: $container->setParameter() works from a controller. | «no» Пояснение: At runtime the compiled container's ParameterBag is frozen, so calling setParameter() throws a LogicException; parameters can only be set during container building.
Raw{"answer": "no", "explanation": "At runtime the compiled container's ParameterBag is frozen, so calling setParameter() throws a LogicException; parameters can only be set during container building."} | верно | Контейнер компилируется и замораживается; runtime-значения — только через переменные окружения. |
T23-L5 2.38 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, so they can't be fetched directly from the container unless explicitly marked public: true (public services were the default only in Symfony 3.4 and earlier).
Raw{"answer": "no", "explanation": "Since Symfony 4.0, services are private by default, so they can't be fetched directly from the container unless explicitly marked public: true (public services were the default only in Symfony 3.4 and earlier)."} | верно | С Symfony 4.0 сервисы по умолчанию private: инжектятся через autowiring; $container->get() — только для публичных. |
T23-L6 1.78 c | Symfony: configuration and services | Without a config file in config/packages a bundle will not work — configuration is mandatory for every bundle. | «no» Пояснение: Bundles work with default configuration; a config file in config/packages is optional and only needed to override defaults, since bundles can define default values in their Configuration class.
Raw{"answer": "no", "explanation": "Bundles work with default configuration; a config file in config/packages is optional and only needed to override defaults, since bundles can define default values in their Configuration class."} | верно | У бандлов есть встроенные умолчания (Extension); конфиг нужен только для отклонений от них. |
T23-L7 2.28 c | Symfony: configuration and services | Environment variable values are injected into services.yaml using the %env(VAR)% syntax. | «yes» Пояснение: Symfony's DI container resolves environment variables in service definitions with the %env(VAR)% syntax, such as in services.yaml.
Raw{"answer": "yes", "explanation": "Symfony's DI container resolves environment variables in service definitions with the %env(VAR)% syntax, such as in services.yaml."} | верно | %env(...)% резолвится в рантайме env-процессорами; docs — Env Var Processors. |
T23-L8 1.53 c | Symfony: configuration and services | Which Symfony environment variable enables debug mode (affects the profiler and Twig debugging)? | «app_debug» Пояснение: Symfony's APP_DEBUG environment variable toggles debug mode, which controls the profiler and Twig debugging features.
Raw{"answer": "APP_DEBUG", "explanation": "Symfony's APP_DEBUG environment variable toggles debug mode, which controls the profiler and Twig debugging features."} | верно | APP_DEBUG=1 (в .env dev-окружения); окружение выбирает APP_ENV — см. T13-L6. |
T16-L1 2.49 c | Symfony: Messenger | A single message in Symfony Messenger can only have one handler. | «no» Пояснение: Symfony Messenger allows a single message to be routed to multiple handlers, and each matching handler will be invoked.
Raw{"answer": "no", "explanation": "Symfony Messenger allows a single message to be routed to multiple handlers, and each matching handler will be invoked."} | верно | Messenger вызывает все хендлеры, подписанные на класс сообщения (docs — Multiple Handlers). |
T16-L2 2.23 c | Symfony: Messenger | The sync transport in Messenger queues the message for a worker, just like async. | «no» Пояснение: The sync transport does not queue messages for a worker; it handles the message immediately in the same process, synchronously, when dispatched.
Raw{"answer": "no", "explanation": "The sync transport does not queue messages for a worker; it handles the message immediately in the same process, synchronously, when dispatched."} | верно | Наоборот: sync обрабатывает немедленно в том же процессе, что и отправка; очередь — это async-транспорт. |
T16-L3 1.55 c | Symfony: Messenger | Which console command starts the worker that processes Messenger queue messages? | «php bin/console messenger:consume» Пояснение: The Symfony Messenger component provides the messenger:consume command to start a worker that processes queued messages.
Raw{"answer": "php bin/console messenger:consume", "explanation": "The Symfony Messenger component provides the messenger:consume command to start a worker that processes queued messages."} | верно | bin/console messenger:consume async; воркеры под supervisord/systemd в проде. |
T16-L4 2.26 c | Symfony: Messenger | Retries for failed messages (retry_strategy) are configured per Messenger transport. | «yes» Пояснение: In Symfony Messenger, retry_strategy (max_retries, delay, multiplier, etc.) is set under each individual transport's configuration in framework.messenger.transports.
Raw{"answer": "yes", "explanation": "In Symfony Messenger, retry_strategy (max_retries, delay, multiplier, etc.) is set under each individual transport's configuration in framework.messenger.transports."} | верно | retry_strategy на транспорте: max_retries, delay, multiplier; docs — Failed Messages & Retries. |
T16-L5 2.5 c | Symfony: Messenger | By default, Messenger serializes messages to JSON. | «yes» Пояснение: Symfony Messenger's default transport serializer encodes messages using the JSON format via the Symfony Serializer component.
Raw{"answer": "yes", "explanation": "Symfony Messenger's default transport serializer encodes messages using the JSON format via the Symfony Serializer component."} | неверно верный: «no» | Дефолтный сериализатор — PhpSerializer (serialize()); JSON-сериализатор включается отдельно. |
T16-L6 2.77 c | Symfony: Messenger | Symfony Scheduler produces messages on a schedule and dispatches them through Messenger. | «yes» Пояснение: Symfony Scheduler generates messages from its schedule (RecurringMessage definitions) and dispatches them through the Messenger component's bus and transports.
Raw{"answer": "yes", "explanation": "Symfony Scheduler generates messages from its schedule (RecurringMessage definitions) and dispatches them through the Messenger component's bus and transports."} | верно | Schedule → RecurringMessage → шина Messenger; docs — Scheduler. |
T16-L7 1.81 c | Symfony: Messenger | Which built-in Messenger transport stores messages in database tables via Doctrine? | «doctrine» Пояснение: Symfony Messenger's Doctrine transport stores messages in a database table using Doctrine DBAL, selected via the doctrine:// DSN scheme.
Raw{"answer": "doctrine", "explanation": "Symfony Messenger's Doctrine transport stores messages in a database table using Doctrine DBAL, selected via the doctrine:// DSN scheme."} | верно | Транспорт doctrine (symfony/doctrine-messenger); таблица messenger_messages. В проекте стоит amqp-messenger + doctrine-messenger. |
T16-L8 2.11 c | Symfony: Messenger | The Messenger pipeline can be extended with custom middleware, placed before or after the built-in ones. | «yes» Пояснение: Symfony Messenger lets you register custom middleware in a bus's middleware list, and you can position it before or after the built-in middleware.
Raw{"answer": "yes", "explanation": "Symfony Messenger lets you register custom middleware in a bus's middleware list, and you can position it before or after the built-in middleware."} | верно | messenger.bus.*.middleware в yaml; docs — Middleware. |
T28-L1 2.36 c | Symfony: versions | Symfony major releases come every two years, minor ones every six months (in May and November). | «yes» Пояснение: Symfony publishes a major release every two years and minor releases every six months, in May and November.
Raw{"answer": "yes", "explanation": "Symfony publishes a major release every two years and minor releases every six months, in May and November."} | верно | Стандартный релизный цикл: 8.0 — ноябрь 2025, 8.1 — май 2026, 8.2 — ноябрь 2026. |
T28-L2 2.65 c | Symfony: versions | What is the minimum PHP version required by Symfony 8? | «8.4» Пояснение: Symfony 8.0 raises the minimum requirement to PHP 8.4, up from PHP 8.2 for Symfony 7.
Raw{"answer": "8.4", "explanation": "Symfony 8.0 raises the minimum requirement to PHP 8.4, up from PHP 8.2 for Symfony 7."} | верно | Symfony 8.0 поднял требование до PHP >= 8.4.1 (в vendor проекта: "php": ">=8.4.1"). |
T28-L3 3.97 c | Symfony: versions | Symfony 7.0 kept support for docblock annotations (validation, routes). | «no» Пояснение: Symfony 7.0 removed support for docblock annotations, so routes, validation, and other config must use PHP attributes instead.
Raw{"answer": "no", "explanation": "Symfony 7.0 removed support for docblock annotations, so routes, validation, and other config must use PHP attributes instead."} | верно | Наоборот: в 7.0 аннотации удалены — только PHP-атрибуты (#[Route], #[Assert\NotBlank]). |
T28-L4 2.2 c | Symfony: versions | AssetMapper manages CSS/JS without node or webpack — via importmap.php. | «yes» Пояснение: Symfony's AssetMapper component serves and versions CSS and JS without Node.js or webpack, and uses an importmap.php file to declare JavaScript dependencies.
Raw{"answer": "yes", "explanation": "Symfony's AssetMapper component serves and versions CSS and JS without Node.js or webpack, and uses an importmap.php file to declare JavaScript dependencies."} | верно | symfony/asset-mapper (с 6.3, стандарт с 7.x); в проекте — importmap.php в корне и asset-mapper 8.1. |
T28-L5 2.02 c | Symfony: versions | Symfony 6.4 is a regular release without long-term support. | «no» Пояснение: Symfony 6.4 is a long-term support (LTS) release, receiving bug fixes for 3 years and security fixes for 4 years.
Raw{"answer": "no", "explanation": "Symfony 6.4 is a long-term support (LTS) release, receiving bug fixes for 3 years and security fixes for 4 years."} | верно | Наоборот: 6.4 — LTS (расширенная поддержка); LTS выходит вместе с очередным мажором (6.4 — вместе с 7.0). |
T28-L6 2.17 c | Symfony: versions | When moving to a new Symfony major version, deprecations of the previous branch keep working — major releases do not remove them. | «no» Пояснение: Symfony major releases remove features that were deprecated in the previous major branch, so code relying on those deprecated features breaks and must be updated before upgrading.
Raw{"answer": "no", "explanation": "Symfony major releases remove features that were deprecated in the previous major branch, so code relying on those deprecated features breaks and must be updated before upgrading."} | верно | Наоборот: мажорный релиз удаляет всё устаревшее (7.0 убрал деприкейшены 6.x, 8.0 — 7.x). |
T28-L7 2.55 c | Symfony: versions | Every Symfony major release is accompanied by an UPGRADE guide listing the changes. | «yes» Пояснение: Symfony publishes an UPGRADE-x.0.md file in its repository for each major release, listing the breaking changes and migration steps.
Raw{"answer": "yes", "explanation": "Symfony publishes an UPGRADE-x.0.md file in its repository for each major release, listing the breaking changes and migration steps."} | верно | UPGRADE-7.0.md, UPGRADE-8.0.md в репозитории symfony/symfony. |
T28-L8 1.72 c | Symfony: versions | Which Symfony component manages assets and the importmap without node/webpack? | «assetmapper» Пояснение: Symfony's AssetMapper component (symfony/asset-mapper) serves and versions assets and manages importmaps without requiring Node.js or Webpack.
Raw{"answer": "AssetMapper", "explanation": "Symfony's AssetMapper component (symfony/asset-mapper) serves and versions assets and manages importmaps without requiring Node.js or Webpack."} | верно | symfony/asset-mapper 8.1 — в проекте. |
T29-L1 3.19 c | Symfony: 8.2 and beyond | As of 2026-11-07, Symfony 8.2 has already been released. | «no» Пояснение: Symfony releases every six months, so 8.0 would be around May 2026 and 8.1 around November 2026, making 8.2 expected around May 2027.
Raw{"answer": "no", "explanation": "Symfony releases every six months, so 8.0 would be around May 2026 and 8.1 around November 2026, making 8.2 expected around May 2027."} | верно | Наоборот: 8.2 ещё не выпущена — релиз в конце ноября 2026; последняя стабильная — 8.1. |
T29-L2 4.09 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» Пояснение: Under the six-month cycle, Symfony 8.0 arrives in May 2026 and 8.1 in November 2026, so 8.2 falls in May 2027.
Raw{"answer": "no", "explanation": "Under the six-month cycle, Symfony 8.0 arrives in May 2026 and 8.1 in November 2026, so 8.2 falls in May 2027."} | неверно верный: «yes» | Политика релизов: 8.1 — май 2026, 8.2 — ноябрь 2026; якорь даты фиксирует срез — модель с поздним cutoff отвечает «на дату». |
T29-L3 3.5 c | Symfony: 8.2 and beyond | Which Symfony version comes after 8.1 (as of 2026-11-07)? | «8.2» Пояснение: Symfony minor versions ship every six months, so the release after 8.1 is 8.2, expected around November 2027.
Raw{"answer": "8.2", "explanation": "Symfony minor versions ship every six months, so the release after 8.1 is 8.2, expected around November 2027."} | верно | 8.2 — следующий минорный релиз (ноябрь 2026); после его выхода проект переходит с 8.1.* на 8.2.*. |
T29-L4 2.68 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 would be a minor release, and Symfony minor versions stay backward compatible, so they don't require rewriting applications; only major versions can introduce breaking changes.
Raw{"answer": "no", "explanation": "Symfony 8.2 would be a minor release, and Symfony minor versions stay backward compatible, so they don't require rewriting applications; only major versions can introduce breaking changes."} | верно | Наоборот: 8.2 — минорный релиз; новые возможности без поломки обратной совместимости. Мажор — 9.0. |
T29-L5 4.84 c | Symfony: 8.2 and beyond | Updating within a major branch (8.1 → 8.2) should not require code changes — backward compatibility is preserved. | «no» Пояснение: PHP aims to keep minor releases backward compatible, but 8.2 added deprecations (such as dynamic properties) and some edge-case behavior changes, so code may need updates.
Raw{"answer": "no", "explanation": "PHP aims to keep minor releases backward compatible, but 8.2 added deprecations (such as dynamic properties) and some edge-case behavior changes, so code may need updates."} | неверно верный: «yes» | Политика Symfony: минорные релизы обратно совместимы; BC-break допустим только в мажорных. |
T29-L6 4.61 c | Symfony: 8.2 and beyond | Which minor version of the 8.x branch is released last, before Symfony 9.0? | «4» Пояснение: Symfony majors end with a 4th minor that is the LTS release (like 6.4 and 7.4), so the last 8.x minor before 9.0 should be 8.4.
Raw{"answer": 4, "explanation": "Symfony majors end with a 4th minor that is the LTS release (like 6.4 and 7.4), so the last 8.x minor before 9.0 should be 8.4."} | неверно верный: «8.4» | По циклу: 8.2 (ноя 2026), 8.3 (май 2027), 8.4 (ноя 2027, вместе с 9.0) — как 6.4 выходила вместе с 7.0. |
T29-L7 3.81 c | Symfony: 8.2 and beyond | Symfony 8.2 will require PHP 8.5 — you would have to upgrade PHP along with it. | «no» Пояснение: Symfony raises its minimum PHP version only with major releases, so Symfony 8.x is expected to keep requiring PHP 8.4, not 8.5.
Raw{"answer": "no", "explanation": "Symfony raises its minimum PHP version only with major releases, so Symfony 8.x is expected to keep requiring PHP 8.4, not 8.5."} | верно | Наоборот: минорные релизы не поднимают требования PHP; для всей ветки 8.x остаётся PHP >= 8.4. |
T29-L8 2.42 c | Symfony: 8.2 and beyond | Deprecations added in the 8.x branch will not be removed before Symfony 9.0. | «yes» Пояснение: Symfony's backward compatibility policy only removes features deprecated in a minor release at the next major version, so 8.x deprecations stay until 9.0 at the earliest.
Raw{"answer": "yes", "explanation": "Symfony's backward compatibility policy only removes features deprecated in a minor release at the next major version, so 8.x deprecations stay until 9.0 at the earliest."} | верно | Политика: деприкейшены живут до следующего мажора; 9.0 — ноябрь 2027. |
T21-L1 2.14 c | Twig | Inside {{ }}, Twig allows calling arbitrary PHP code directly. | «no» Пояснение: Twig expressions inside {{ }} use Twig's own syntax and can only call functions, filters, and methods that are explicitly exposed to the template, not arbitrary PHP code.
Raw{"answer": "no", "explanation": "Twig expressions inside {{ }} use Twig's own syntax and can only call functions, filters, and methods that are explicitly exposed to the template, not arbitrary PHP code."} | верно | Twig — DSL: только разрешённые окружением функции/фильтры; произвольный PHP не исполняется. |
T21-L2 1.59 c | Twig | By default, Twig auto-escapes printed variables. | «yes» Пояснение: Twig's autoescape option is enabled by default, so printed variables are HTML-escaped unless a filter like raw is applied.
Raw{"answer": "yes", "explanation": "Twig's autoescape option is enabled by default, so printed variables are HTML-escaped unless a filter like raw is applied."} | верно | Autoescape включён по умолчанию; {{ '<b>' }} → <b>. Проверено на Twig 3.30. |
T21-L3 1.99 c | Twig | The Twig |e filter escapes a string for safe output in an HTML context. | «yes» Пояснение: Twig's `e` filter (alias of `escape`) defaults to HTML escaping, converting characters like <, >, &, and quotes into safe entities.
Raw{"answer": "yes", "explanation": "Twig's `e` filter (alias of `escape`) defaults to HTML escaping, converting characters like <, >, &, and quotes into safe entities."} | верно | |e ('html') по умолчанию; есть контексты js/url/css. От SQL-инъекций он не защищает — это задача подготовленных запросов Doctrine. |
T21-L4 1.65 c | Twig | Which filter from twig/intl-extra formats a number according to a locale? | «format_number» Пояснение: The twig/intl-extra package provides the format_number filter, which formats a number according to the locale and supports options like style and currency.
Raw{"answer": "format_number", "explanation": "The twig/intl-extra package provides the format_number filter, which formats a number according to the locale and supports options like style and currency."} | верно | |format_number(locale=...) из IntlExtension (twig/intl-extra есть в проекте). Проверено на Twig 3.30: 12345.6 → 12 345,6 (ru). |
T21-L5 2.21 c | Twig | The |raw filter disables auto-escaping for the value. | «yes» Пояснение: In Twig, the raw filter marks a value as safe, so auto-escaping is not applied to it.
Raw{"answer": "yes", "explanation": "In Twig, the raw filter marks a value as safe, so auto-escaping is not applied to it."} | верно | {{ x|raw }} выводит HTML как есть; опасно с пользовательскими данными. Проверено на Twig 3.30. |
T21-L6 1.66 c | Twig | In Twig, {{ }} prints an expression value, while {% %} executes tags — conditions, loops, set. | «yes» Пояснение: In Twig, {{ }} outputs the result of an expression, while {% %} is used for tags such as if, for, and set that control logic.
Raw{"answer": "yes", "explanation": "In Twig, {{ }} outputs the result of an expression, while {% %} is used for tags such as if, for, and set that control logic."} | верно | Два блока синтаксиса Twig: вывод (echo) против логики. |
T21-L7 2.26 c | Twig | In Twig you cannot declare a variable inside a template — values only come from the controller. | «no» Пояснение: Twig supports the `{% set %}` tag, which lets you declare and assign variables directly inside a template, not only values passed from the controller.
Raw{"answer": "no", "explanation": "Twig supports the `{% set %}` tag, which lets you declare and assign variables directly inside a template, not only values passed from the controller."} | верно | {% set y = ... %} объявляет переменную в шаблоне. Проверено на Twig 3.30. |
T21-L8 1.58 c | Twig | Which Twig function dumps the debug structure of a variable (array, object)? | «dump» Пояснение: Twig's dump() function outputs debugging information about a variable, such as its structure for arrays and objects, and requires the debug extension to be enabled.
Raw{"answer": "dump", "explanation": "Twig's dump() function outputs debugging information about a variable, such as its structure for arrays and objects, and requires the debug extension to be enabled."} | верно | {{ dump(x) }} (DebugExtension; в Symfony доступна в dev-окружении). |
T24-L1 1.62 c | Bootstrap | Bootstrap is a CSS/JS library of ready-made UI components, not an SPA framework. | «yes» Пояснение: Bootstrap is a front-end library providing CSS styles and JavaScript components, not a single-page application framework that manages routing and application state.
Raw{"answer": "yes", "explanation": "Bootstrap is a front-end library providing CSS styles and JavaScript components, not a single-page application framework that manages routing and application state."} | верно | Компоненты и утилиты поверх вашего HTML; SPA-фреймворки (React/Vue) — другой класс инструментов. В проекте vendored 5.3.3. |
T24-L2 1.5 c | Bootstrap | Which Bootstrap class gives a responsive container with a fixed max width per breakpoint? | «container» Пояснение: The Bootstrap `.container` class sets a responsive fixed max-width that changes at each breakpoint.
Raw{"answer": "container", "explanation": "The Bootstrap `.container` class sets a responsive fixed max-width that changes at each breakpoint."} | верно | .container (фиксированная макс-ширина по брейкпоинтам) vs .container-fluid (на всю ширину). |
T24-L3 2.25 c | Bootstrap | The Bootstrap grid is built on CSS floats and splits a row into 16 columns. | «no» Пояснение: Bootstrap's grid uses 12 columns per row, not 16, and since Bootstrap 4 it is built on flexbox rather than floats.
Raw{"answer": "no", "explanation": "Bootstrap's grid uses 12 columns per row, not 16, and since Bootstrap 4 it is built on flexbox rather than floats."} | верно | Наоборот: flexbox (с Bootstrap 4) и 12 колонок; float-сетка — это Bootstrap 3. |
T24-L4 3.42 c | Bootstrap | Bootstrap's named breakpoints (the infix used in class names) are sm, md, lg, xl, xxl — five of them. | «yes» Пояснение: Bootstrap 5 uses the infixes sm, md, lg, xl, and xxl (xs has no infix), giving five named breakpoints.
Raw{"answer": "yes", "explanation": "Bootstrap 5 uses the infixes sm, md, lg, xl, and xxl (xs has no infix), giving five named breakpoints."} | верно | Тиров всего шесть: xs (без инфикса) + пять именованных (576/768/992/1200/1400 px). |
T24-L5 3.85 c | Bootstrap | Utilities like .mt-3 or .px-2 use the spacing scale: the number is a multiple of $spacer. | «no» Пояснение: In Bootstrap, the number is an index into a spacing map (1 to $spacer*0.25, 2 to $spacer*0.5, 3 to $spacer, 4 to $spacer*1.5, 5 to $spacer*3), not a direct multiple of $spacer.
Raw{"answer": "no", "explanation": "In Bootstrap, the number is an index into a spacing map (1 to $spacer*0.25, 2 to $spacer*0.5, 3 to $spacer, 4 to $spacer*1.5, 5 to $spacer*3), not a direct multiple of $spacer."} | верно | Spacing utilities; $spacer = 1rem. |
T24-L6 1.58 c | Bootstrap | Which Bootstrap 5 data attribute enables an interactive component (e.g. dropdown) on an element? | «data-bs-toggle» Пояснение: In Bootstrap 5, the data-bs-toggle attribute is used to activate interactive components such as dropdowns, modals, and collapses.
Raw{"answer": "data-bs-toggle", "explanation": "In Bootstrap 5, the data-bs-toggle attribute is used to activate interactive components such as dropdowns, modals, and collapses."} | верно | data-bs-toggle="dropdown" и т.п.; в Bootstrap 4 атрибут назывался data-toggle. |
T24-L7 1.82 c | Bootstrap | Bootstrap 5 components work without jQuery — in plain vanilla JS. | «yes» Пояснение: Bootstrap 5 dropped its jQuery dependency and its components are written in vanilla JavaScript, so they work without jQuery.
Raw{"answer": "yes", "explanation": "Bootstrap 5 dropped its jQuery dependency and its components are written in vanilla JavaScript, so they work without jQuery."} | верно | jQuery удалён в Bootstrap 5.0: data-bs-* атрибуты и JS API. В проекте vendored 5.3.3. |
T24-L8 2.29 c | Bootstrap | Dark mode in Bootstrap is enabled with a .dark class on the root element. | «no» Пояснение: Bootstrap 5.3 enables dark mode with the data-bs-theme="dark" attribute on an element, not a .dark class.
Raw{"answer": "no", "explanation": "Bootstrap 5.3 enables dark mode with the data-bs-theme=\"dark\" attribute on an element, not a .dark class."} | верно | Наоборот: тема включается атрибутом data-bs-theme="dark" (Color modes, с 5.3); класса .dark не существует. В проекте 5.3.3. |
T14-L1 1.6 c | Doctrine | Doctrine ORM creates database tables on the fly the first time an entity is used at runtime. | «no» Пояснение: Doctrine ORM does not create tables at runtime; schema changes are made explicitly via commands such as doctrine:schema:update or migrations.
Raw{"answer": "no", "explanation": "Doctrine ORM does not create tables at runtime; schema changes are made explicitly via commands such as doctrine:schema:update or migrations."} | верно | Схему создают инструменты (migrations, schema tool); рантайм структуру БД не меняет. |
T14-L2 1.82 c | Doctrine | Which EntityManager method marks a new object as managed without executing SQL until flush()? | «persist» Пояснение: EntityManager::persist() schedules a new entity for insertion and makes it managed, with no SQL executed until flush() is called.
RawThe Doctrine ORM method is persist(), which marks an entity for insertion and makes it managed; the actual SQL INSERT runs on flush(). ⏎ ⏎ {"answer": "persist", "explanation": "EntityManager::persist() schedules a new entity for insertion and makes it managed, with no SQL executed until flush() is called."} | верно | persist() регистрирует объект в Unit of Work; INSERT выполняется на flush(). |
T14-L3 2.42 c | Doctrine | In Doctrine ORM 3, the EntityManager::merge() method exists and makes the passed object managed. | «no» Пояснение: Doctrine ORM 3.0 removed EntityManager::merge(), which was deprecated in 2.x; the method no longer exists.
Raw{"answer": "no", "explanation": "Doctrine ORM 3.0 removed EntityManager::merge(), which was deprecated in 2.x; the method no longer exists."} | верно | В ORM 3 merge() удалён (в vendor проекта 3.7.6 метода нет); в Doctrine 2.x merge() возвращал управляемую копию. Версия зафиксирована — ORM 3. |
T14-L4 2.43 c | Doctrine | DQL queries are written in terms of entities and their fields, not tables and columns. | «yes» Пояснение: DQL (Doctrine Query Language) queries reference PHP entity classes and their properties rather than database tables and columns.
Raw{"answer": "yes", "explanation": "DQL (Doctrine Query Language) queries reference PHP entity classes and their properties rather than database tables and columns."} | верно | Doctrine транслирует DQL в SQL; docs — DQL (Doctrine Query Language). |
T14-L5 1.68 c | Doctrine | What does $repository->find(999) return when no record with id 999 exists? | «{"answer": null, "explanation": "doctrine's find() returns null when no entity matches the given identifier."}» Пояснение: , "explanation": "Doctrine's find() returns null when no entity matches the given identifier."}
Raw{"answer": null, "explanation": "Doctrine's find() returns null when no entity matches the given identifier."} | верно парсинг: текст (фолбэк) | find() возвращает null, если объект не найден (docs Repository methods). |
T14-L6 1.49 c | Doctrine | DoctrineBundle in Symfony automatically calls flush() at the end of every request. | «no» Пояснение: Doctrine does not flush automatically at the end of a request; changes must be persisted explicitly by calling EntityManager::flush().
Raw{"answer": "no", "explanation": "Doctrine does not flush automatically at the end of a request; changes must be persisted explicitly by calling EntityManager::flush()."} | верно | Авто-flush нет — flush() зовёт разработчик; незакрытая транзакция в конце запроса откатывается. |
T14-L7 4.44 c | Doctrine | For a managed entity, changing a property is enough: flush() commits the change without an explicit persist() — the Unit of Work tracks changes. | «yes» Пояснение: Doctrine's Unit of Work tracks managed entities, so flush() detects property changes and issues the UPDATE without calling persist().
Raw{"answer": "yes", "explanation": "Doctrine's Unit of Work tracks managed entities, so flush() detects property changes and issues the UPDATE without calling persist()."} | верно | Dirty checking сравнивает снимки свойств; persist нужен только новым/отсоединённым объектам. |
T14-L8 2.41 c | Doctrine | remove() executes the SQL DELETE immediately, without waiting for flush(). | «no» Пояснение: In Doctrine's EntityManager, remove() only schedules the entity for deletion; the SQL DELETE is executed when flush() is called.
Raw{"answer": "no", "explanation": "In Doctrine's EntityManager, remove() only schedules the entity for deletion; the SQL DELETE is executed when flush() is called."} | верно | remove() планирует удаление в Unit of Work; DELETE выполняется на flush() (docs — Deleting Objects). |
T15-L1 1.54 c | PostgreSQL | PostgreSQL uses MVCC, therefore readers block writers and writers block readers. | «no» Пояснение: PostgreSQL's MVCC means readers do not block writers and writers do not block readers, since readers see a consistent snapshot while writers create new row versions.
Raw{"answer": "no", "explanation": "PostgreSQL's MVCC means readers do not block writers and writers do not block readers, since readers see a consistent snapshot while writers create new row versions."} | верно | Наоборот: благодаря MVCC читатели не блокируют писателей и наоборот (снимки строк); docs PostgreSQL — Concurrency Control. |
T15-L2 1.59 c | PostgreSQL | Which SQL command shows a query's execution plan without executing the query? | «explain» Пояснение: EXPLAIN displays the query execution plan the optimizer would use without actually running the statement.
Raw{"answer": "EXPLAIN", "explanation": "EXPLAIN displays the query execution plan the optimizer would use without actually running the statement."} | верно | EXPLAIN без ANALYZE только строит план; проверено на PostgreSQL 17.7. |
T15-L3 3.63 c | PostgreSQL | SERIAL and GENERATED ... AS IDENTITY are just two names for the same mechanism. | «no» Пояснение: SERIAL creates a sequence with a column DEFAULT of nextval(), while GENERATED AS IDENTITY is the SQL-standard mechanism that rejects explicit inserts unless OVERRIDING is used, so they differ in behavior.
Raw{"answer": "no", "explanation": "SERIAL creates a sequence with a column DEFAULT of nextval(), while GENERATED AS IDENTITY is the SQL-standard mechanism that rejects explicit inserts unless OVERRIDING is used, so they differ in behavior."} | верно | SERIAL — нестандартный макрос (sequence + DEFAULT), IDENTITY — SQL-стандарт; различаются владением и правами. Оба есть в PG 17 (проверено). |
T15-L4 1.61 c | PostgreSQL | By default, a PostgreSQL UNIQUE constraint allows only one row with NULL in the column. | «no» Пояснение: In PostgreSQL, NULL values are considered distinct from each other, so a UNIQUE constraint allows multiple rows with NULL in the column by default (unless NULLS NOT DISTINCT is specified in PostgreSQL 15+).
Raw{"answer": "no", "explanation": "In PostgreSQL, NULL values are considered distinct from each other, so a UNIQUE constraint allows multiple rows with NULL in the column by default (unless NULLS NOT DISTINCT is specified in PostgreSQL 15+)."} | верно | Наоборот: NULLS DISTINCT по умолчанию — несколько NULL допустимы; NULLS NOT DISTINCT — опция с PG 15. Проверено на PG 17.7. |
T15-L5 1.7 c | PostgreSQL | Which PostgreSQL aggregate function concatenates strings with a separator? | «string_agg» Пояснение: PostgreSQL's string_agg(expression, delimiter) concatenates non-null input values into a string, separated by the given delimiter.
Raw{"answer": "string_agg", "explanation": "PostgreSQL's string_agg(expression, delimiter) concatenates non-null input values into a string, separated by the given delimiter."} | верно | string_agg(значение, разделитель); проверено на PostgreSQL 17.7. |
T15-L6 1.78 c | PostgreSQL | Plain VACUUM returns the space occupied by dead tuples to the operating system. | «no» Пояснение: Plain VACUUM only marks dead tuple space as reusable within the table and does not shrink the file or return space to the operating system; VACUUM FULL is needed for that.
Raw{"answer": "no", "explanation": "Plain VACUUM only marks dead tuple space as reusable within the table and does not shrink the file or return space to the operating system; VACUUM FULL is needed for that."} | верно | VACUUM помечает место для переиспользования внутри таблицы; ОС его возвращает только VACUUM FULL (с эксклюзивной блокировкой). |
T15-L7 1.51 c | PostgreSQL | Which keyword in a window function definition partitions rows into groups the function is computed over? | «partition by» Пояснение: The PARTITION BY clause divides the result set into groups over which the window function is computed independently.
Raw{"answer": "PARTITION BY", "explanation": "The PARTITION BY clause divides the result set into groups over which the window function is computed independently."} | верно | OVER (PARTITION BY ...); проверено на PostgreSQL 17.7. |
T15-L8 1.71 c | PostgreSQL | The READ COMMITTED isolation level protects against non-repeatable reads. | «no» Пояснение: READ COMMITTED only prevents dirty reads; non-repeatable reads are prevented starting at REPEATABLE READ isolation level.
Raw{"answer": "no", "explanation": "READ COMMITTED only prevents dirty reads; non-repeatable reads are prevented starting at REPEATABLE READ isolation level."} | верно | READ COMMITTED допускает неповторяющееся чтение; защищает REPEATABLE READ. Проверено: SHOW transaction_isolation → read committed. |
T17-L1 1.59 c | PostgreSQL: transactions and indexes | By default, PostgreSQL wraps each single SQL statement in its own implicit transaction (autocommit). | «yes» Пояснение: PostgreSQL runs each standalone SQL statement in its own implicit transaction, committing it automatically unless an explicit transaction block is used.
Raw{"answer": "yes", "explanation": "PostgreSQL runs each standalone SQL statement in its own implicit transaction, committing it automatically unless an explicit transaction block is used."} | верно | Без BEGIN каждый оператор коммитится сам; docs PostgreSQL — Transactions. Проверено на PG 17. |
T17-L2 1.66 c | PostgreSQL: transactions and indexes | Which SQL command ends a transaction, committing all its changes? | «commit» Пояснение: The COMMIT statement ends the current transaction and makes all its changes permanent.
Raw{"answer": "COMMIT", "explanation": "The COMMIT statement ends the current transaction and makes all its changes permanent."} | верно | COMMIT (END — синоним). Проверено на PG 17. |
T17-L3 1.77 c | PostgreSQL: transactions and indexes | Indexes speed up more than SELECT: UPDATE and DELETE with a search on an indexed column benefit too. | «yes» Пояснение: UPDATE and DELETE statements with WHERE clauses on indexed columns can locate matching rows faster via the index, just like SELECT.
Raw{"answer": "yes", "explanation": "UPDATE and DELETE statements with WHERE clauses on indexed columns can locate matching rows faster via the index, just like SELECT."} | верно | Поиск строк для изменения идёт по индексу; docs PostgreSQL — Indexes. |
T17-L4 1.53 c | PostgreSQL: transactions and indexes | To roll back part of the statements inside a transaction, PostgreSQL uses SAVEPOINT. | «yes» Пояснение: ROLLBACK TO SAVEPOINT undoes only the statements executed after the named savepoint while keeping the rest of the transaction open.
Raw{"answer": "yes", "explanation": "ROLLBACK TO SAVEPOINT undoes only the statements executed after the named savepoint while keeping the rest of the transaction open."} | верно | SAVEPOINT name; ROLLBACK TO name — частичный откат без отмены всей транзакции. Проверено на PG 17. |
T17-L5 1.56 c | PostgreSQL: transactions and indexes | EXPLAIN ANALYZE shows the query plan without executing the query. | «no» Пояснение: EXPLAIN ANALYZE actually executes the query and reports real timing and row counts, whereas plain EXPLAIN only shows the plan without executing it.
Raw{"answer": "no", "explanation": "EXPLAIN ANALYZE actually executes the query and reports real timing and row counts, whereas plain EXPLAIN only shows the plan without executing it."} | верно | Наоборот: ANALYZE реально выполняет запрос (с побочными эффектами!) и показывает фактические времена узлов; план без выполнения — plain EXPLAIN. |
T17-L6 1.52 c | PostgreSQL: transactions and indexes | Which PostgreSQL extension adds vector types and indexes for embedding search? | «pgvector» Пояснение: The pgvector extension adds a vector data type and indexes (IVFFlat and HNSW) for similarity search over embeddings in PostgreSQL.
Raw{"answer": "pgvector", "explanation": "The pgvector extension adds a vector data type and indexes (IVFFlat and HNSW) for similarity search over embeddings in PostgreSQL."} | верно | CREATE EXTENSION vector (проект pgvector; в проекте образ pgvector/pgvector:pg17). |
T17-L7 1.55 c | PostgreSQL: transactions and indexes | A partial index (CREATE INDEX ... WHERE ...) is built only over rows satisfying the condition. | «yes» Пояснение: A partial index includes only the table rows that satisfy its WHERE predicate, which makes it smaller and cheaper to maintain.
Raw{"answer": "yes", "explanation": "A partial index includes only the table rows that satisfy its WHERE predicate, which makes it smaller and cheaper to maintain."} | верно | docs PostgreSQL — Partial Indexes; типичный кейс — индекс по «активным» записям. |
T17-L8 1.75 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 tracks read/write dependencies with predicate locks and aborts transactions on conflict rather than locking the rows read.
Raw{"answer": "no", "explanation": "PostgreSQL implements SERIALIZABLE using Serializable Snapshot Isolation (SSI), which tracks read/write dependencies with predicate locks and aborts transactions on conflict rather than locking the rows read."} | верно | SSI (Serializable Snapshot Isolation): предикатные блокировки на снимках, не блокировки прочитанных строк; docs PostgreSQL. |
T19-L1 1.54 c | HTTP and REST API | HTTP status 201 means the request resulted in a new resource being created. | «yes» Пояснение: HTTP status 201 Created indicates that the request succeeded and a new resource was created as a result.
Raw{"answer": "yes", "explanation": "HTTP status 201 Created indicates that the request succeeded and a new resource was created as a result."} | верно | 201 Created; обычно на POST, часто с Location; RFC 9110. |
T19-L2 1.66 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 request succeeded and there is no content to return in the response body.
Raw{"answer": 204, "explanation": "HTTP 204 No Content indicates the request succeeded and there is no content to return in the response body."} | верно | 204 No Content; RFC 9110. |
T19-L3 3.95 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 9110 defines DELETE as idempotent, meaning repeated identical requests have the same intended effect on server state, though the response status may differ (e.g., 200 then 404).
Raw{"answer": "yes", "explanation": "RFC 9110 defines DELETE as idempotent, meaning repeated identical requests have the same intended effect on server state, though the response status may differ (e.g., 200 then 404)."} | верно | RFC 9110: DELETE идемпотентен (как PUT); идемпотентность ≠ безопасность — ресурс удаляется при первом вызове. |
T19-L4 1.5 c | HTTP and REST API | The Access-Control-Allow-Origin header is sent by the client so that the server agrees to accept requests from another origin. | «no» Пояснение: Access-Control-Allow-Origin is a response header sent by the server to tell the browser which origins may read the response; the client sends the Origin header instead.
Raw{"answer": "no", "explanation": "Access-Control-Allow-Origin is a response header sent by the server to tell the browser which origins may read the response; the client sends the Origin header instead."} | верно | Наоборот: заголовок шлёт СЕРВЕР в ответе, разрешая браузеру cross-origin запрос (CORS); в проекте nelmio/cors-bundle. |
T19-L5 1.7 c | HTTP and REST API | Status 429 Too Many Requests is used when a client exceeds a rate limit. | «yes» Пояснение: HTTP status 429 Too Many Requests indicates the user has sent too many requests in a given time, typically exceeding a rate limit.
Raw{"answer": "yes", "explanation": "HTTP status 429 Too Many Requests indicates the user has sent too many requests in a given time, typically exceeding a rate limit."} | верно | 429 (+ Retry-After); RFC 6585. В проекте symfony/rate-limiter. |
T19-L6 1.63 c | HTTP and REST API | 5xx codes mean a client error, while 4xx means a server-side error. | «no» Пояснение: It is reversed: 4xx status codes indicate client errors, while 5xx codes indicate server-side errors.
Raw{"answer": "no", "explanation": "It is reversed: 4xx status codes indicate client errors, while 5xx codes indicate server-side errors."} | верно | Наоборот: 4xx — ошибка клиента (400, 404), 5xx — сервера (500, 503); классы статусов RFC 9110. |
T19-L7 1.51 c | HTTP and REST API | Which HTTP header indicates the MIME type of the request or response body? | «content-type» Пояснение: The Content-Type header specifies the MIME type of the body in a request or response.
Raw{"answer": "Content-Type", "explanation": "The Content-Type header specifies the MIME type of the body in a request or response."} | верно | Content-Type: application/json и т.п. |
T19-L8 2.32 c | HTTP and REST API | PATCH is not required to be idempotent per RFC 5789, unlike PUT. | «yes» Пояснение: RFC 5789 states that PATCH is neither safe nor idempotent, whereas PUT is required to be idempotent under RFC 7231.
Raw{"answer": "yes", "explanation": "RFC 5789 states that PATCH is neither safe nor idempotent, whereas PUT is required to be idempotent under RFC 7231."} | верно | RFC 5789 прямо оговаривает: PATCH не гарантированно идемпотентен; PUT идемпотентен. |
T20-L1 2.24 c | Security and OAuth | Checking a password by comparing its hash to the stored hash with a plain == is sufficient. | «no» Пояснение: A plain == comparison can leak timing information, so hash comparisons should use hash_equals() or password_verify() instead.
Raw{"answer": "no", "explanation": "A plain == comparison can leak timing information, so hash comparisons should use hash_equals() or password_verify() instead."} | верно | Нужна постоянновременная проверка (password_verify) — timing-атаки; соль и алгоритм уже внутри хеша. |
T20-L2 1.56 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 session-bound CSRF token generated by the server and checked on state-changing requests like POST is the standard defense against cross-site request forgery.
Raw{"answer": "yes", "explanation": "A session-bound CSRF token generated by the server and checked on state-changing requests like POST is the standard defense against cross-site request forgery."} | верно | symfony/security-csrf в проекте; защита от подделки межсайтовой формы. |
T20-L3 1.51 c | Security and OAuth | Which HTTP header enables the CSP (Content Security Policy) policy? | «content-security-policy» Пояснение: The Content-Security-Policy HTTP response header enables and defines the Content Security Policy for a page.
Raw{"answer": "Content-Security-Policy", "explanation": "The Content-Security-Policy HTTP response header enables and defines the Content Security Policy for a page."} | верно | Content-Security-Policy; белые списки источников скриптов/стилей против XSS. |
T20-L4 1.87 c | Security and OAuth | OAuth 2.0 is an authentication protocol: the access token tells you who the user is. | «no» Пояснение: OAuth 2.0 is an authorization framework, not an authentication protocol; an access token grants delegated access to resources and does not itself identify the user (OpenID Connect adds the ID token for authentication).
Raw{"answer": "no", "explanation": "OAuth 2.0 is an authorization framework, not an authentication protocol; an access token grants delegated access to resources and does not itself identify the user (OpenID Connect adds the ID token for authentication)."} | верно | OAuth 2.0 — авторизация/делегирование доступа; аутентификацию добавляет OpenID Connect. В проекте knpuniversity/oauth2-client-bundle (yandex/github/google). |
T20-L5 1.64 c | Security and OAuth | XSS is prevented by validating input on the server before writing it to the database. | «no» Пояснение: XSS is prevented by context-aware output encoding/escaping when data is rendered, since input validation alone cannot stop all XSS and data may be safe in one context but not another.
Raw{"answer": "no", "explanation": "XSS is prevented by context-aware output encoding/escaping when data is rendered, since input validation alone cannot stop all XSS and data may be safe in one context but not another."} | верно | XSS лечится контекстным экранированием НА ВЫВОДЕ (Twig autoescape, CSP); валидация ввода не покрывает все контексты вывода. |
T20-L6 1.68 c | Security and OAuth | In the OAuth 2.0 authorization code flow, which parameter arrives at the redirect_uri and is exchanged for an access token? | «code» Пояснение: The authorization server redirects to redirect_uri with a 'code' query parameter, which the client exchanges for an access token at the token endpoint.
Raw{"answer": "code", "explanation": "The authorization server redirects to redirect_uri with a 'code' query parameter, which the client exchanges for an access token at the token endpoint."} | верно | Параметр code; обмен на токен POST-ом на /token с client_secret. |
T20-L7 1.73 c | Security and OAuth | A refresh token lives longer than an access token and allows obtaining a new access token without the user logging in again. | «yes» Пояснение: Refresh tokens have a longer lifetime than access tokens and are used to obtain new access tokens without requiring the user to re-authenticate.
Raw{"answer": "yes", "explanation": "Refresh tokens have a longer lifetime than access tokens and are used to obtain new access tokens without requiring the user to re-authenticate."} | верно | Стандартная схема OAuth/OIDC: короткий access + длинный refresh. |
T20-L8 1.57 c | Security and OAuth | A password salt must be kept secret: without it the hash cannot be verified. | «no» Пояснение: Salts are stored alongside the hash and are not secret; their purpose is to prevent precomputed rainbow table attacks, and verification uses the stored salt.
Raw{"answer": "no", "explanation": "Salts are stored alongside the hash and are not secret; their purpose is to prevent precomputed rainbow table attacks, and verification uses the stored salt."} | верно | Соль хранится открыто (password_hash включает её в строку хеша); секретность соли не нужна. |
T18-L1 2.63 c | Testing: PHPUnit | PHPUnit runs test methods of any class — extending TestCase is not required. | «no» Пояснение: PHPUnit only discovers and runs test classes that extend PHPUnit\Framework\TestCase (or otherwise implement its Test interface), so extending it is required.
Raw{"answer": "no", "explanation": "PHPUnit only discovers and runs test classes that extend PHPUnit\\Framework\\TestCase (or otherwise implement its Test interface), so extending it is required."} | верно | Тестом считается метод класса, наследующего TestCase (PHPUnit 10). |
T18-L2 1.52 c | Testing: PHPUnit | In PHPUnit, setUp() runs once before all tests of the class. | «no» Пояснение: PHPUnit's setUp() runs before each individual test method, not once before the whole class; setUpBeforeClass() is the method that runs once per class.
Raw{"answer": "no", "explanation": "PHPUnit's setUp() runs before each individual test method, not once before the whole class; setUpBeforeClass() is the method that runs once per class."} | верно | setUp() — перед КАЖДЫМ тестом; один раз на класс — setUpBeforeClass(). Проверено живым счётчиком на PHPUnit 10.5. |
T18-L3 2.49 c | Testing: PHPUnit | A data provider lets a test run with exactly one set of arguments. | «no» Пояснение: A PHPUnit data provider supplies multiple argument sets, and the test runs once for each set, not just one.
Raw{"answer": "no", "explanation": "A PHPUnit data provider supplies multiple argument sets, and the test runs once for each set, not just one."} | верно | Наоборот: наборов может быть сколько угодно — тест выполняется по разу на каждый. Проверено на PHPUnit 10.5 (#[DataProvider]). |
T18-L4 1.49 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 the test expects an exception of the given class to be thrown.
Raw{"answer": "expectException", "explanation": "PHPUnit's expectException() method declares that the test expects an exception of the given class to be thrown."} | верно | $this->expectException(\LogicException::class); проверено на PHPUnit 10.5. |
T18-L5 2.02 c | Testing: PHPUnit | In PHPUnit, a stub verifies which methods were called on it, while a mock only returns data. | «no» Пояснение: It is reversed: a stub only returns canned data for method calls, while a mock additionally verifies that expected methods were called on it.
Raw{"answer": "no", "explanation": "It is reversed: a stub only returns canned data for method calls, while a mock additionally verifies that expected methods were called on it."} | верно | Наоборот: стаб подставляет данные, мок проверяет взаимодействия (createStub/createMock); docs PHPUnit — Test Doubles. |
T18-L6 1.61 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» Пояснение: PHPUnit 10 and later use the #[DataProvider] attribute, and the older @dataProvider docblock annotation is deprecated in favor of it.
Raw{"answer": "yes", "explanation": "PHPUnit 10 and later use the #[DataProvider] attribute, and the older @dataProvider docblock annotation is deprecated in favor of it."} | верно | Аннотация ещё парсится в PHPUnit 10/11 (AnnotationParser в 10.5.66), удаление — в 12; атрибут — стандарт. |
T18-L7 2.01 c | Testing: PHPUnit | PHPUnit does not allow one test to depend on the result of another. | «no» Пояснение: PHPUnit supports test dependencies through the @depends annotation (or #[Depends] attribute), which lets one test consume the return value of another.
Raw{"answer": "no", "explanation": "PHPUnit supports test dependencies through the @depends annotation (or #[Depends] attribute), which lets one test consume the return value of another."} | верно | Зависимости есть: #[Depends] — зависимый тест не запустится, еслиProducer упал. |
T18-L8 1.67 c | Testing: PHPUnit | Which PHPUnit command-line option makes tests run in random order? | «--order-by=random» Пояснение: PHPUnit's --order-by option with the random value runs tests in random order (also settable via --random-order, which exists in newer versions as a shortcut).
Raw{"answer": "--order-by=random", "explanation": "PHPUnit's --order-by option with the random value runs tests in random order (also settable via --random-order, which exists in newer versions as a shortcut)."} | верно | --order-by=random (PHPUnit 9+); опция есть в --help PHPUnit 10.5 (проектная). |
T01-L9 1.75 c | Syntax and operators | What does this code output?
```php
echo intdiv(7, 2) . intdiv(-7, 2);
``` | «3-3» Пояснение: intdiv(7, 2) is 3 and intdiv(-7, 2) truncates toward zero to -3, so concatenating gives "3-3".
Rawintdiv(7,2) = 3. intdiv(-7,2) truncates toward zero = -3. Concatenation gives "3" . "-3" = "3-3". ⏎ ⏎ {"answer": "3-3", "explanation": "intdiv(7, 2) is 3 and intdiv(-7, 2) truncates toward zero to -3, so concatenating gives \"3-3\"."} | верно | intdiv truncates toward zero: intdiv(-7, 2) = -3, not -4. |
T01-L10 1.74 c | Syntax and operators | What does this code output?
```php
echo -3 ** 2;
``` | «-9» Пояснение: The exponentiation operator binds tighter than unary minus, so it evaluates as -(3**2) = -9.
RawIn PHP, ** has higher precedence than unary minus, so -3 ** 2 is -(3 ** 2) = -9. ⏎ ⏎ {"answer": -9, "explanation": "The exponentiation operator binds tighter than unary minus, so it evaluates as -(3**2) = -9."} | верно | ** is right-associative and binds tighter than unary minus: -(3²). |
T02-L9 2.64 c | Types and comparisons | What does this code output?
```php
echo '1e1' == '10' ? 'true' : 'false';
``` | «true» Пояснение: Both '1e1' and '10' are numeric strings, so PHP compares them numerically (10 == 10), which is true.
Raw{"answer": "true", "explanation": "Both '1e1' and '10' are numeric strings, so PHP compares them numerically (10 == 10), which is true."} | верно | Both strings are numeric — compared as numbers: 10 == 10. |
T02-L10 2.88 c | Types and comparisons | What does this code output?
```php
switch ('a') {
case 0: echo 'zero'; break;
default: echo 'other';
}
``` | «other» Пояснение: In PHP 8, 'a' == 0 is false because the non-numeric string is compared as a string with '0', so the default branch runs (PHP 7 would have matched 'zero').
Raw{"answer": "other", "explanation": "In PHP 8, 'a' == 0 is false because the non-numeric string is compared as a string with '0', so the default branch runs (PHP 7 would have matched 'zero')."} | верно | PHP 8: 'a' == 0 → false (used to be true) — default fires. |
T03-L9 2.25 c | Strings | What does this code output?
```php
echo strtr('abc', ['a' => '1', 'ab' => '2']);
``` | «2c» Пояснение: When strtr is given an array, it replaces the longest matching key first, so 'ab' is replaced by '2' and the remaining 'c' is unchanged.
Raw{"answer": "2c", "explanation": "When strtr is given an array, it replaces the longest matching key first, so 'ab' is replaced by '2' and the remaining 'c' is unchanged."} | верно | strtr with an array prefers the longest matching key. |
T03-L10 3.46 c | Strings | What does this code output?
```php
echo '[' . substr('hello', -10) . ']';
``` | «[hello]» Пояснение: A negative start larger than the string length is clamped to 0, so substr returns the whole string 'hello'.
Raw{"answer": "[hello]", "explanation": "A negative start larger than the string length is clamped to 0, so substr returns the whole string 'hello'."} | верно | A negative start beyond the string is clamped to the beginning. |
T04-L9 2.37 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, keeping the left array's keys first (k, n) and then adding keys only present on the right (m), so array_keys yields k, n, m.
Raw{"answer": "k,n,m", "explanation": "The + operator merges arrays, keeping the left array's keys first (k, n) and then adding keys only present on the right (m), so array_keys yields k, n, m."} | верно | The + operator: on duplicate string keys the left array wins. |
T04-L10 2.46 c | Arrays | What does this code output?
```php
$a = [[1, 'x', 2], [2, 'y', 1], [3, 'z', 2]];
usort($a, fn($p, $q) => $p[2] <=> $q[2]);
echo implode('', array_column($a, 1));
``` | «yxz» Пояснение: Sorting by index 2 ascending puts [2,'y',1] first, and since PHP 8's sort is stable the tied elements keep their order, giving y, x, z.
Raw{"answer": "yxz", "explanation": "Sorting by index 2 ascending puts [2,'y',1] first, and since PHP 8's sort is stable the tied elements keep their order, giving y, x, z."} | верно | Sorts are stable since 8.0: x and z keep their order on a tie. |
T05-L10 2.04 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» Пояснение: Since PHP 8.1, spreading an array with string keys passes them as named arguments, so a=5 and b=1, giving 5 - 1 = 4.
Raw{"answer": 4, "explanation": "Since PHP 8.1, spreading an array with string keys passes them as named arguments, so a=5 and b=1, giving 5 - 1 = 4."} | верно | String keys of a spread array become named arguments. |
T05-L9 2.39 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 `$p->g(...)` creates a Closure that holds a reference to the object, so setting `$p = null` does not destroy it and `$f()` still returns `$this->v`, which is 3.
Raw{"answer": 3, "explanation": "The first-class callable `$p->g(...)` creates a Closure that holds a reference to the object, so setting `$p = null` does not destroy it and `$f()` still returns `$this->v`, which is 3."} | верно | First-class callable syntax binds $this at creation time. |
T06-L9 1.71 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 resolves to the late static binding class, which is B since the method is called on a B instance.
Raw{"answer": "B", "explanation": "static::class resolves to the late static binding class, which is B since the method is called on a B instance."} | верно | Late static binding: static::class is the receiver's class. |
T06-L10 3.1 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» Пояснение: Inside its own set hook, assigning to $this->x bypasses the hook (recursion guard), so the backing value is set to 5 * 2 = 10, which is then echoed.
Raw{"answer": 10, "explanation": "Inside its own set hook, assigning to $this->x bypasses the hook (recursion guard), so the backing value is set to 5 * 2 = 10, which is then echoed."} | верно | Inside the set hook, $this->x writes the backing store (no recursion): 5*2. |
T07-L9 3.48 c | Interfaces, traits, enum | What does this code output?
```php
trait TA
{
public function f(): string { return 'A'; }
}
trait TB
{
public function f(): string { return 'B'; }
}
class TC
{
use TA, TB { TB::f insteadof TA; TA::f as g; }
}
echo (new TC)->f() . (new TC)->g();
``` | «ba» Пояснение: The `insteadof` rule makes TC's `f` come from TB (returns 'B'), and the `TA::f as g` alias makes `g` the TA version (returns 'A'), so the concatenation is 'BA'.
Raw{"answer": "BA", "explanation": "The `insteadof` rule makes TC's `f` come from TB (returns 'B'), and the `TA::f as g` alias makes `g` the TA version (returns 'A'), so the concatenation is 'BA'."} | верно | insteadof picks the implementation; as keeps the other under an alias. |
T07-L10 2.27 c | Interfaces, traits, enum | What does this code output?
```php
trait Counter
{
public static int $n = 0;
}
class CX { use Counter; }
class CY { use Counter; }
CX::$n = 1;
echo CY::$n;
``` | «0» Пояснение: A static property declared in a trait is copied into each class that uses it, so CX and CY each get their own $n, and setting CX::$n leaves CY::$n at its default of 0.
Raw{"answer": 0, "explanation": "A static property declared in a trait is copied into each class that uses it, so CX and CY each get their own $n, and setting CX::$n leaves CY::$n at its default of 0."} | верно | A trait's static property is copied into each consuming class. |
T08-L10 1.61 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 the finally block overrides the return value from the try block, so the function returns 2.
Raw{"answer": 2, "explanation": "A return statement in the 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 2.59 c | Exceptions and errors | What does this code output?
```php
try {
try {
throw new RuntimeException('first');
} finally {
throw new LogicException('second');
}
} catch (LogicException $e) {
echo $e->getMessage();
}
``` | «second» Пояснение: The exception thrown in the finally block replaces the pending RuntimeException, so the outer catch receives the LogicException and echoes its message.
Raw{"answer": "second", "explanation": "The exception thrown in the finally block replaces the pending RuntimeException, so the outer catch receives the LogicException and echoes its message."} | верно | An exception from finally replaces the in-flight one — the last thrown is caught. |
T09-L9 2.88 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 through the `use` alias to `App\Foo`, while `\Baz::class` is the fully qualified global name `Baz`.
Raw{"answer": "App\\Foo|Baz", "explanation": "`Baz::class` resolves through the `use` alias to `App\\Foo`, while `\\Baz::class` is the fully qualified global name `Baz`."} | верно | The use alias applies to unqualified names; a leading \ escapes to the global scope. |
T09-L10 2.78 c | Namespaces and autoloading | What does this code output?
```php
namespace Ns;
class Foo {}
$c = 'Foo';
echo (class_exists($c) ? 'yes' : 'no')
. (class_exists(__NAMESPACE__ . '\\' . $c) ? 'yes' : 'no');
``` | «noyes» Пояснение: class_exists('Foo') looks for a global class and returns false, while class_exists('Ns\Foo') finds the namespaced class and returns true.
Raw{"answer": "noyes", "explanation": "class_exists('Foo') looks for a global class and returns false, while class_exists('Ns\\Foo') finds the namespaced class and returns true."} | верно | Dynamic names are not resolved against the namespace — 'Foo' is the global class. |
T10-L9 2.32 c | References and scope | What does this code output?
```php
$a = [1, 2, 3];
foreach ($a as &$v) {}
$v = 99;
echo implode(',', $a);
``` | «1,2,99» Пояснение: After the by-reference foreach, $v still references the last element $a[2], so $v = 99 overwrites that element.
Raw{"answer": "1,2,99", "explanation": "After the by-reference foreach, $v still references the last element $a[2], so $v = 99 overwrites that element."} | верно | After a by-ref foreach, $v remains a reference to the last element. |
T10-L10 2.54 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» Пояснение: Since PHP 8.1, an inherited method that isn't overridden shares its static variables with the parent, so $n is incremented to 1, then 2, then 3 across the three calls.
Raw{"answer": 3, "explanation": "Since PHP 8.1, an inherited method that isn't overridden shares its static variables with the parent, so $n is incremented to 1, then 2, then 3 across the three calls."} | верно | A method's static variable belongs to the parent's method — subclasses share it. |
T11-L9 3.44 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» Пояснение: Calling send(10) on an unstarted generator first runs it to the first yield, then passes 10 in as that yield's result, so $x = 10 and the return value is 10 + 1 = 11.
Raw{"answer": 11, "explanation": "Calling send(10) on an unstarted generator first runs it to the first yield, then passes 10 in as that yield's result, so $x = 10 and the return value is 10 + 1 = 11."} | верно | send() resumes the generator: $x = 10, return 10+1. |
T11-L10 3.82 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()));
``` | «ok,2» Пояснение: iterator_to_array preserves keys: inner yields keys 0 and 1 (1, 2), then outer's own yield gets key 0 and overwrites the value 1 with 'ok', leaving [0=>'ok', 1=>2].
Raw{"answer": "ok,2", "explanation": "iterator_to_array preserves keys: inner yields keys 0 and 1 (1, 2), then outer's own yield gets key 0 and overwrites the value 1 with 'ok', leaving [0=>'ok', 1=>2]."} | верно | yield from does not advance the outer auto-key: yield $r gets key 0 and overwrites the 1 — 'ok' comes out first. |
T12-L9 2.12 c | Configuration and security | What does this code output?
```php
$hash = password_hash('x', PASSWORD_BCRYPT, ['cost' => 4]);
echo password_needs_rehash($hash, PASSWORD_BCRYPT, ['cost' => 4]) ? 'yes' : 'no';
echo password_needs_rehash($hash, PASSWORD_BCRYPT, ['cost' => 5]) ? 'yes' : 'no';
``` | «noyes» Пояснение: The hash was made with cost 4, so checking against cost 4 returns 'no', while checking against cost 5 returns 'yes' because the cost differs.
Raw{"answer": "noyes", "explanation": "The hash was made with cost 4, so checking against cost 4 returns 'no', while checking against cost 5 returns 'yes' because the cost differs."} | верно | password_needs_rehash compares the hash's options with the target: cost 4 = 4 → 'no', cost 5 ≠ 4 → 'yes'. |
T12-L10 3.41 c | Configuration and security | What does this code output on PHP 8.5?
```php
echo (E_ALL & 2048) === 0 ? 'strict-out' : 'strict-in';
``` | «strict-in» Пояснение: Since PHP 8.0, E_ALL is 32767, which includes the E_STRICT bit (2048), so E_ALL & 2048 is 2048, not 0.
Raw{"answer": "strict-in", "explanation": "Since PHP 8.0, E_ALL is 32767, which includes the E_STRICT bit (2048), so E_ALL & 2048 is 2048, not 0."} | неверно верный: «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 3.78 c | Symfony | What does this code output?
```php
use Symfony\Component\HttpFoundation\Request;
$r = Request::create('/demo', 'GET', [], [], [], ['HTTP_X_TOKEN' => 'abc']);
echo $r->headers->get('X-Token') === 'abc' ? 'mapped' : 'missing';
``` | «mapped» Пояснение: Request::create passes the server array into the constructor, and ServerBag::getHeaders() converts HTTP_X_TOKEN into the header X-Token, so the lookup returns 'abc'.
Raw{"answer": "mapped", "explanation": "Request::create passes the server array into the constructor, and ServerBag::getHeaders() converts HTTP_X_TOKEN into the header X-Token, so the lookup returns 'abc'."} | верно | The literal comparison requires knowing the mapping: HttpFoundation turns HTTP_X_TOKEN into the X-Token header (case-insensitive); without it the answer is 'missing'. |
T13-L10 2.62 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 calls listeners in descending priority order: B (10), then C (5), then A (0, default).
Raw{"answer": "BCA", "explanation": "Symfony calls listeners in descending priority order: B (10), then C (5), then A (0, default)."} | верно | Listeners run by descending priority: 10 (B), 5 (C), 0 (A). |
T14-L10 2.34 c | Doctrine | Given: Doctrine ORM 3, an EntityManager on in-memory SQLite, entity User with an auto-increment primary key. The users table is empty. What does this code output?
```php
$u = new User(name: 'A');
$em->persist($u);
$em->flush();
$a = $em->find(User::class, $u->getId());
$b = $em->find(User::class, $u->getId());
echo spl_object_id($a) === spl_object_id($b) ? 'same' : 'diff';
``` | «same» Пояснение: Doctrine's identity map returns the already-managed entity instance for both find() calls, so $a and $b are the same object.
Raw{"answer": "same", "explanation": "Doctrine's identity map returns the already-managed entity instance for both find() calls, so $a and $b are the same object."} | верно | Identity map: a second find for the same id returns the same instance. |
T14-L9 2.39 c | Doctrine | Given: Doctrine ORM 3, an EntityManager on in-memory SQLite, entity User with an auto-increment primary key. The users table is empty. What does this code output?
```php
$u = new User(name: 'B');
$em->persist($u);
$em->remove($u);
$em->flush();
echo count($em->getConnection()->fetchAllAssociative('SELECT * FROM users'));
``` | «0» Пояснение: Removing an entity that was persisted but not yet flushed cancels its scheduled insert, so nothing is written and the table stays empty.
Raw{"answer": 0, "explanation": "Removing an entity that was persisted but not yet flushed cancels its scheduled insert, so nothing is written and the table stays empty."} | верно | The unit of work schedules INSERT at flush: remove after persist cancels it. |
T15-L10 2.18 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(column) counts only non-NULL values, and the table holds 1 and NULL, so only the 1 is counted.
Raw{"answer": 1, "explanation": "count(column) counts only non-NULL values, and the table holds 1 and NULL, so only the 1 is counted."} | верно | count(column) skips NULLs; count(*) would return 2. |
T15-L9 2.94 c | PostgreSQL | What does this SQL query return (PostgreSQL 17)?
```sql
CREATE TEMP TABLE t (id int, x int);
INSERT INTO t VALUES (1, 10), (2, 20), (3, 30);
SELECT string_agg(s::text, ',' ORDER BY id) FROM (
SELECT id, sum(x) OVER (ORDER BY id) AS s FROM t
) q;
``` | «10,30,60» Пояснение: The window sum is a running total ordered by id (10, 30, 60), and string_agg concatenates these in id order with commas.
Raw{"answer": "10,30,60", "explanation": "The window sum is a running total ordered by id (10, 30, 60), and string_agg concatenates these in id order with commas."} | верно | With ORDER BY the default window frame is running (start to current row). |
T16-L9 4.19 c | Symfony: Messenger | What does this code output?
```php
use Symfony\Component\Messenger\MessageBus;
use Symfony\Component\Messenger\Middleware\MiddlewareInterface;
use Symfony\Component\Messenger\Middleware\StackInterface;
use Symfony\Component\Messenger\Envelope;
final class Trace implements MiddlewareInterface
{
public function __construct(private string $tag) {}
public function handle(Envelope $e, StackInterface $stack): Envelope
{
echo $this->tag;
return $stack->next()->handle($e, $stack);
}
}
$bus = new MessageBus([new Trace('M1'), new Trace('M2')]);
$bus->dispatch(new Envelope(new stdClass()));
``` | «m1m2» Пояснение: The bus runs the first middleware, which echoes M1 and then passes to the next, which echoes M2; the end of the stack returns the envelope without output.
Raw{"answer": "M1M2", "explanation": "The bus runs the first middleware, which echoes M1 and then passes to the next, which echoes M2; the end of the stack returns the envelope without output."} | верно | The first-added middleware runs first (outermost). |
T16-L10 3.61 c | Symfony: Messenger | What does this code output?
```php
use Symfony\Component\Messenger\MessageBus;
use Symfony\Component\Messenger\Middleware\HandleMessageMiddleware;
use Symfony\Component\Messenger\Handler\HandlersLocator;
use Symfony\Component\Messenger\Handler\HandlerDescriptor;
use Symfony\Component\Messenger\Envelope;
class Ping {}
$n = 0;
$d1 = new HandlerDescriptor(function (Ping $m) use (&$n) { $n += 1; }, ['alias' => 'h1']);
$d2 = new HandlerDescriptor(function (Ping $m) use (&$n) { $n += 10; }, ['alias' => 'h2']);
$bus = new MessageBus([
new HandleMessageMiddleware(new HandlersLocator([Ping::class => [$d1, $d2]])),
]);
$bus->dispatch(new Envelope(new Ping()));
echo $n;
``` | «11» Пояснение: HandleMessageMiddleware invokes every handler registered for Ping (neither has been handled yet), so $n becomes 1 + 10 = 11.
Raw{"answer": 11, "explanation": "HandleMessageMiddleware invokes every handler registered for Ping (neither has been handled yet), so $n becomes 1 + 10 = 11."} | верно | All registered handlers of the message run: 1 + 10 = 11. |
T17-L9 3.08 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 unique index makes the second INSERT of the value 1 hit a conflict, which ON CONFLICT DO NOTHING silently skips, so only one row remains.
Raw{"answer": 1, "explanation": "The unique index makes the second INSERT of the value 1 hit a conflict, which ON CONFLICT DO NOTHING silently skips, so only one row remains."} | верно | ON CONFLICT DO NOTHING skips the duplicate: one insert. |
T17-L10 3.37 c | PostgreSQL: transactions and indexes | What does this sequence of psql commands output?
```sql
BEGIN;
CREATE TEMP TABLE t (a int, UNIQUE (a) DEFERRABLE INITIALLY DEFERRED);
INSERT INTO t VALUES (1);
INSERT INTO t VALUES (1);
SELECT count(*) FROM t;
``` | «2» Пояснение: The UNIQUE constraint is deferred until commit, so both inserted rows are visible within the open transaction and the count is 2 (the violation would only surface at COMMIT).
Raw{"answer": 2, "explanation": "The UNIQUE constraint is deferred until commit, so both inserted rows are visible within the open transaction and the count is 2 (the violation would only surface at COMMIT)."} | верно | DEFERRED postpones the uniqueness check to COMMIT — count sees 2 rows. |
T18-L9 2.63 c | Testing: PHPUnit | How many tests will this command run?
```php
use PHPUnit\Framework\TestCase;
use PHPUnit\Framework\Attributes\DataProvider;
final class CalcTest extends TestCase
{
public static function prov(): array
{
return [[1], [2], [3]];
}
#[DataProvider('prov')]
public function test_sum(int $x): void
{
$this->assertTrue($x > 0);
}
#[DataProvider('prov')]
public function test_sum_abs(int $x): void
{
$this->assertTrue($x > 0);
}
public function test_other(): void
{
$this->assertTrue(true);
}
}
```
Command: `phpunit CalcTest.php --filter test_sum` (PHPUnit 10.5) | «6» Пояснение: The filter `test_sum` matches both `test_sum` and `test_sum_abs`, each with 3 data sets, while `test_other` is excluded, giving 3 + 3 = 6.
Raw{"answer": 6, "explanation": "The filter `test_sum` matches both `test_sum` and `test_sum_abs`, each with 3 data sets, while `test_other` is excluded, giving 3 + 3 = 6."} | верно | --filter is a substring match: test_sum also matches test_sum_abs (3+3 datasets). |
T18-L10 2.16 c | Testing: PHPUnit | How many tests will this command run, and how many of them will fail? Answer with two comma-separated numbers (ran, failed).
```php
use PHPUnit\Framework\TestCase;
use PHPUnit\Framework\Attributes\DataProvider;
final class Calc2Test extends TestCase
{
public function prov(): array
{
return [[1], [-1]];
}
#[DataProvider('prov')]
public function test_x(int $x): void
{
$this->assertTrue($x > 0);
}
}
```
Command: `phpunit Calc2Test.php` (PHPUnit 10.5) | «2, 1» Пояснение: The data provider yields two cases: x=1 passes the assertion, and x=-1 fails it, so two tests run and one fails.
Raw{"answer": "2, 1", "explanation": "The data provider yields two cases: x=1 passes the assertion, and x=-1 fails it, so two tests run and one fails."} | верно | A non-static provider is just a deprecation in PHPUnit 10: both datasets run and the [-1] dataset fails the assert — 2 ran, 1 failure. |
T19-L9 1.72 c | HTTP and REST API | Which HTTP method does this command send?
```bash
curl -s -d 'a=1' http://demo.local/api
``` | «post» Пояснение: Using -d (--data) with curl makes it send a POST request by default, unless another method is specified with -X.
Raw{"answer": "POST", "explanation": "Using -d (--data) with curl makes it send a POST request by default, unless another method is specified with -X."} | верно | -d/-F switches curl to POST by default. |
T19-L10 2.22 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 (--get) flag makes curl append the -d data to the URL as a query string and send a GET request.
Raw{"answer": "GET", "explanation": "The -G (--get) flag makes curl append the -d data to the URL as a query string and send a GET request."} | верно | -G turns -d data into the query string; the method stays GET. |
T20-L9 2.86 c | Security and OAuth | A client hits the token endpoint (RFC 6749) with a non-existent client_id. What value of the error field does the endpoint return? | «invalid_client» Пояснение: RFC 6749 Section 5.2 defines invalid_client for client authentication failures, including an unknown client.
Raw{"answer": "invalid_client", "explanation": "RFC 6749 Section 5.2 defines invalid_client for client authentication failures, including an unknown client."} | верно | Unknown client → invalid_client (RFC 6749 §5.2). |
T20-L10 2.5 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» Пояснение: With response_type=token (implicit grant), the authorization server returns the access_token in the URL fragment (after #) of the redirect_uri.
Raw{"answer": "fragment", "explanation": "With response_type=token (implicit grant), the authorization server returns the access_token in the URL fragment (after #) of the redirect_uri."} | верно | The implicit flow passes the token in the URL fragment (#) — it never reaches the server. |
T21-L9 3.31 c | Twig | What does this Twig template output?
```twig
{{ false|default(2) * 3 }}
``` | «6» Пояснение: The default filter returns 2 because false counts as empty, and the filter binds tighter than *, so 2 * 3 = 6.
Raw{"answer": 6, "explanation": "The default filter returns 2 because false counts as empty, and the filter binds tighter than *, so 2 * 3 = 6."} | верно | default replaces exactly false/null/''/[] — false becomes 2, 2*3 = 6; the naive 'default is for undefined only' yields 0. |
T21-L10 8.73 c | Twig | What exception class does render() of this template throw?
```twig
{{ 'a' ~ 1 + 2 }}
``` | «typeerror» Пояснение: Twig's `~` binds tighter than `+`, so this parses as ('a' ~ 1) + 2, which adds the non-numeric string 'a1' to 2 and PHP 8 throws a TypeError.
Raw{"answer": "TypeError", "explanation": "Twig's `~` binds tighter than `+`, so this parses as ('a' ~ 1) + 2, which adds the non-numeric string 'a1' to 2 and PHP 8 throws a TypeError."} | неверно верный: «runtimeerror» | In Twig ~ binds tighter than +: ('a' ~ 1) + 2 → string + int → a render error (RuntimeError). |
T22-L9 3.34 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» Пояснение: The value is the array [''], which is not null or an empty string, so NotBlank passes and there are no violations.
Raw{"answer": 0, "explanation": "The value is the array [''], which is not null or an empty string, so NotBlank passes and there are no violations."} | верно | NotBlank treats null, '', [] as blank — the array [''] is not blank. |
T22-L10 3.21 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);
}
``` | «invalid» Пояснение: The form is never submitted, and Symfony's isValid() returns false for unsubmitted forms instead of throwing, so the ternary outputs 'invalid'.
Raw{"answer": "invalid", "explanation": "The form is never submitted, and Symfony's isValid() returns false for unsubmitted forms instead of throwing, so the ternary outputs 'invalid'."} | неверно верный: «symfony\component\form\exception\logicexception» | isValid() on a non-submitted form throws LogicException, it does not return false. |
T23-L9 2.32 c | Symfony: configuration and services | What does this code output?
```php
use Symfony\Component\DependencyInjection\ContainerBuilder;
$c = new ContainerBuilder();
$c->register('a', stdClass::class)->setPublic(true);
$c->compile();
echo spl_object_id($c->get('a')) === spl_object_id($c->get('a')) ? 'same' : 'diff';
``` | «same» Пояснение: Services registered with the default shared behavior return the same instance on each get() call, so the object IDs match.
Raw{"answer": "same", "explanation": "Services registered with the default shared behavior return the same instance on each get() call, so the object IDs match."} | верно | Container services are shared: two get() calls yield one instance. |
T23-L10 5.6 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 resolves parameter placeholders recursively at compile time, so %greeting% expands to 'hi %name%', which then expands to 'hi Bob', giving 'hi Bob!'.
Raw{"answer": "hi Bob!", "explanation": "Symfony resolves parameter placeholders recursively at compile time, so %greeting% expands to 'hi %name%', which then expands to 'hi Bob', giving 'hi Bob!'."} | верно | compile() resolves %-references transitively: %greeting% → 'hi %name%' → 'hi Bob!', the answer assembles over two hops. |
T24-L9 2.46 c | Bootstrap | What is the max-width of .container in Bootstrap 5.3 at a 992px viewport? | «960px» Пояснение: At 992px, the lg breakpoint (≥992px) applies, and Bootstrap 5.3 sets .container max-width to 960px there.
Raw{"answer": "960px", "explanation": "At 992px, the lg breakpoint (≥992px) applies, and Bootstrap 5.3 sets .container max-width to 960px there."} | верно | 5.x container widths: 540/720/960/1140/1320 (sm–xxl); 992 → 960px. |
T24-L10 3.4 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» Пояснение: Both classes use !important with equal specificity, so the one defined later in Bootstrap's generated CSS wins, and text-danger comes after text-primary in the theme color order.
Raw{"answer": "text-danger", "explanation": "Both classes use !important with equal specificity, so the one defined later in Bootstrap's generated CSS wins, and text-danger comes after text-primary in the theme color order."} | верно | Specificity ties — the later rule wins: text-danger is declared after text-primary. |
T25-L9 3.04 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 depends on both Application (PlaceOrder) and Infrastructure (Db) through the promoted constructor property types, and Domain may only depend on Domain, so each is one violation.
Raw{"answer": 2, "explanation": "The Domain layer depends on both Application (PlaceOrder) and Infrastructure (Db) through the promoted constructor property types, and Domain may only depend on Domain, so each is one violation."} | верно | Domain may depend only on Domain: PlaceOrder (Application) + Db (Infrastructure) = 2. |
T25-L10 3.72 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» Пояснение: Domain may only depend on Domain, so the three cross-layer references (PlaceOrder from Application, Db and the fully qualified Logger from Infrastructure) each count as a violation.
Raw{"answer": 3, "explanation": "Domain may only depend on Domain, so the three cross-layer references (PlaceOrder from Application, Db and the fully qualified Logger from Infrastructure) each count as a violation."} | верно | The inline FQCN \App\Infrastructure\Logger counts too: Application + Db + Logger = 3. |
T26-L10 1.68 c | DDD | What does this code output?
```php
final class Money
{
public function __construct(public readonly int $amount) {}
public function add(Money $o): Money
{
return new self($this->amount + $o->amount);
}
}
$a = new Money(10);
$c = $a->add(new Money(5));
echo $a->amount . ',' . $c->amount;
``` | «10,15» Пояснение: The add method returns a new Money instance without modifying $a, so $a->amount stays 10 and $c->amount is 15.
Raw{"answer": "10,15", "explanation": "The add method returns a new Money instance without modifying $a, so $a->amount stays 10 and $c->amount is 15."} | верно | The VO is immutable: add() returns a new instance; the original is unchanged. |
T26-L9 2.77 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» Пояснение: After adding 'a', remove('a') sees count 1 and throws DomainException, which is caught without removing the item, so count() still returns 1.
Raw{"answer": 1, "explanation": "After adding 'a', remove('a') sees count 1 and throws DomainException, which is caught without removing the item, so count() still returns 1."} | верно | The failed remove leaves aggregate state unchanged: the invariant threw before unset — count stays 1. |
VC-L9 3.55 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» Пояснение: Since PHP 8.4, a method can be called directly on a `new` expression with `new C()->hi()`, so it returns 'hi' and echo prints it.
Raw{"answer": "hi", "explanation": "Since PHP 8.4, a method can be called directly on a `new` expression with `new C()->hi()`, so it returns 'hi' and echo prints it."} | верно | Since 8.4, new in a method chain works without wrapping parentheses. |
VC-L10 3.76 c | PHP 8.4–8.5 | What does this code output on PHP 8.5?
```php
class Heavy
{
public int $v = 0;
}
$r = new ReflectionClass(Heavy::class);
$o = $r->newLazyGhost(function (Heavy $obj) {
$obj->v = 21;
});
echo $r->isUninitializedLazyObject($o) ? 'yes' : 'no';
$o->v;
echo $r->isUninitializedLazyObject($o) ? 'yes' : 'no';
``` | «yesno» Пояснение: The ghost starts uninitialized, so the first check prints 'yes'; reading $o->v runs the initializer, which sets v, so the second check prints 'no'.
Raw{"answer": "yesno", "explanation": "The ghost starts uninitialized, so the first check prints 'yes'; reading $o->v runs the initializer, which sets v, so the second check prints 'no'."} | верно | newLazyGhost (8.4): the object stays lazy until first access — reading a property initializes it and clears the flag. |
T28-L9 2.59 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» Пояснение: AbstractGuardAuthenticator was deprecated in Symfony 5.3 and removed in 6.0, so class_exists() returns false on 8.1.
Raw{"answer": "no", "explanation": "AbstractGuardAuthenticator was deprecated in Symfony 5.3 and removed in 6.0, so class_exists() returns false on 8.1."} | верно | Guard authentication was removed in Symfony 7.0 — the class is gone in 8.1. |
T28-L10 3.87 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 deprecated in 6.4 and removed in Symfony 7.0, while its replacement AttributeClassLoader still exists in 8.1, so class_exists returns false then true.
Raw{"answer": "noyes", "explanation": "AnnotationClassLoader was deprecated in 6.4 and removed in Symfony 7.0, while its replacement AttributeClassLoader still exists in 8.1, so class_exists returns false then true."} | верно | Annotation loaders were removed in 7.0; only attribute loaders remain (Annotation→Attribute). |