Пример запроса (первая клетка). System одинаковый во всех запросах прогона, user — свой вопрос для каждой клетки:
| Клетка | Тема | Утверждение | Ответ |
Результат | Обоснование |
T01-L1 2.49 c | Syntax and operators | Double-quoted and single-quoted strings are processed identically; the difference is only in speed. | «no» Пояснение: Double-quoted strings support variable interpolation and escape sequences, whereas single-quoted strings do not, so they are processed differently.
Raw{"answer": "no", "explanation": "Double-quoted strings support variable interpolation and escape sequences, whereas single-quoted strings do not, so they are processed differently."} | верно | В двойных кавычках работают интерполяция переменных и escape-последовательности, в одинарных — нет. |
T01-L2 0.46 c | Syntax and operators | The ?? operator follows isset semantics and raises no warnings for undefined variables. | «yes» Пояснение: The null coalescing operator (??) is designed to safely handle undefined variables without triggering any notices or warnings, as it returns the first operand if it is not null and the second otherwise.
Raw{"answer": "yes", "explanation": "The null coalescing operator (??) is designed to safely handle undefined variables without triggering any notices or warnings, as it returns the first operand if it is not null and the second otherwise."} | верно | ?? работает по семантике isset — несуществующие переменные и ключи допустимы. |
T01-L3 0.36 c | Syntax and operators | What will this print: echo 'a', 'b'; | «ab» Пояснение: The comma operator in a single statement returns the value of the last expression and all previous expressions are evaluated and printed by echo.
Raw{"answer": "ab", "explanation": "The comma operator in a single statement returns the value of the last expression and all previous expressions are evaluated and printed by echo."} | верно | echo принимает список аргументов: ab. |
T01-L4 0.39 c | Syntax and operators | print returns the value 1 and can be used inside an expression. | «no» Пояснение: The print operator in PHP returns 1, but it is an operator rather than a function and cannot be used inside an expression like other functions.
Raw{"answer": "no", "explanation": "The print operator in PHP returns 1, but it is an operator rather than a function and cannot be used inside an expression like other functions."} | неверно верный: «yes» | print — выражение со значением 1, в отличие от echo, который значения не возвращает. |
T01-L5 0.43 c | Syntax and operators | The ?: (elvis) operator returns its left operand when it is falsy. | «yes» Пояснение: The ?: (null coalescing) operator is often confused with the elvis operator, but the null coalescing operator returns the left operand when it is falsy.
Raw{"answer": "yes", "explanation": "The ?: (null coalescing) operator is often confused with the elvis operator, but the null coalescing operator returns the left operand when it is falsy."} | неверно верный: «no» | Наоборот: $a ?: $b возвращает $a, если он истинный, иначе $b. |
T01-L6 0.62 c | Syntax and operators | In PHP 8, the concatenation operator (.) has lower precedence than addition and subtraction. | «no» Пояснение: In PHP 8, the concatenation operator (.) has a higher precedence than addition and subtraction, meaning expressions like 1 . 2 . 3 are evaluated as '1' . (2 . 3) rather than (1 + 2) . (2 + 3).
Raw{"answer": "false", "explanation": "In PHP 8, the concatenation operator (.) has a higher precedence than addition and subtraction, meaning expressions like 1 . 2 . 3 are evaluated as '1' . (2 . 3) rather than (1 + 2) . (2 + 3)."} | неверно верный: «yes» | С PHP 8 (RFC concat precedence) '.' имеет приоритет ниже арифметики: 'сумма: ' . 2 + 3 → 'сумма: 5' (в PHP 7 было иначе). |
T01-L7 0.56 c | Syntax and operators | The expression 2 ** 3 ** 2 in PHP evaluates as (2 ** 3) ** 2, that is, 64. | «no» Пояснение: In PHP, the ** operator is right-associative, so the expression 2 ** 3 ** 2 is evaluated as 2 ** (3 ** 2), which equals 512, not 64.
Raw{"answer": "no", "explanation": "In PHP, the ** operator is right-associative, so the expression 2 ** 3 ** 2 is evaluated as 2 ** (3 ** 2), which equals 512, not 64."} | верно | ** право-ассоциативен: 2 ** (3 ** 2) = 2 ** 9 = 512. |
T01-L8 0.58 c | Syntax and operators | What string will this print: echo 'sum: ' . 2 + 3; (PHP 8)? | «sum: 5» Пояснение: The concatenation operator '.' has lower precedence than the arithmetic '+' operator, so the expression is evaluated as 'sum: ' . (2 + 3), resulting in the string 'sum: 5'.
Raw{ ⏎ "answer": "sum: 5", ⏎ "explanation": "The concatenation operator '.' has lower precedence than the arithmetic '+' operator, so the expression is evaluated as 'sum: ' . (2 + 3), resulting in the string 'sum: 5'." ⏎ } | верно | Парная к verify-клетке про приоритет: 'сумма: 5'. |
T02-L1 0.43 c | Types and comparisons | With strict comparison (===), arrays are considered equal regardless of element order. | «no» Пояснение: The === operator performs a strict equality check for arrays that requires both the same keys and values in the exact same order.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "The === operator performs a strict equality check for arrays that requires both the same keys and values in the exact same order." ⏎ } | верно | === для массивов требует совпадения и значений, и их порядка. |
T02-L2 0.32 c | Types and comparisons | The comparison 0 == false returns false because it is a strict comparison. | «no» Пояснение: The == operator performs a loose comparison, not a strict one.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "The == operator performs a loose comparison, not a strict one." ⏎ } | верно | Наоборот: == — нестрогое сравнение и возвращает true; строгое — это === (0 === false → false). |
T02-L3 0.42 c | Types and comparisons | In PHP 8, the expression "abc" == 0 returns true. | «yes» Пояснение: In PHP 8, comparing a string that is not a valid number with the integer 0 using the loose equality operator returns true.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "In PHP 8, comparing a string that is not a valid number with the integer 0 using the loose equality operator returns true." ⏎ } | неверно верный: «no» | С PHP 8 нечисловая строка сравнивается как строка: "abc" == "0" → false (в PHP 7 было true). |
T02-L4 0.41 c | Types and comparisons | Under loose comparison, null equals 0, the empty string, and false at the same time. | «yes» Пояснение: In PHP, null == 0, null == "", and null == false all evaluate to true due to loose comparison rules.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "In PHP, null == 0, null == \"\", and null == false all evaluate to true due to loose comparison rules." ⏎ } | верно | null == 0, null == "" и null == false — все true. |
T02-L5 0.37 c | Types and comparisons | What does the expression (int) '42abc' return? | «42» Пояснение: In PHP, casting a string to an integer extracts the leading numeric portion of the string until it encounters a non-numeric character.
Raw{"answer": 42, "explanation": "In PHP, casting a string to an integer extracts the leading numeric portion of the string until it encounters a non-numeric character."} | верно | Ведущая числовая часть: 42, без ошибок и warning. |
T02-L6 0.39 c | Types and comparisons | What does the expression '5' + 5 return? | «10» Пояснение: PHP casts the string '5' to the integer 5, so adding them results in 10.
Raw{ ⏎ "answer": 10, ⏎ "explanation": "PHP casts the string '5' to the integer 5, so adding them results in 10." ⏎ } | верно | Числовая строка приводится: int 10. |
T02-L7 0.49 c | Types and comparisons | When cast to string, false becomes "0". | «yes» Пояснение: In PHP, casting false to a string results in an empty string, but when it is converted via string concatenation or print, it often behaves like 0; however, strictly (string) false is ''.
Raw{"answer": "yes", "explanation": "In PHP, casting false to a string results in an empty string, but when it is converted via string concatenation or print, it often behaves like 0; however, strictly (string) false is ''."} | неверно верный: «no» | false → "", true → "1". |
T02-L8 0.55 c | Types and comparisons | The comparison 0.1 + 0.2 === 0.3 returns false. | «yes» Пояснение: Due to floating-point precision, 0.1 + 0.2 evaluates to 0.30000000000000004, which is not strictly equal to 0.3.
Raw{"answer": "yes", "explanation": "Due to floating-point precision, 0.1 + 0.2 evaluates to 0.30000000000000004, which is not strictly equal to 0.3."} | верно | Двоичная погрешность float: 0.1 + 0.2 = 0.30000000000000004. |
T03-L1 0.39 c | Strings | strrev() correctly reverses a UTF-8 string. | «no» Пояснение: strrev() operates on individual bytes rather than multi-byte UTF-8 characters, which will corrupt multi-byte strings when reversed.
Raw{"answer": "no", "explanation": "strrev() operates on individual bytes rather than multi-byte UTF-8 characters, which will corrupt multi-byte strings when reversed."} | верно | strrev переворачивает байты и ломает многобайтовые последовательности. |
T03-L2 0.41 c | Strings | str_contains('Hello world', 'world') returns true. | «yes» Пояснение: The str_contains() function returns true when the search string 'world' is found within the target string 'Hello world'.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "The str_contains() function returns true when the search string 'world' is found within the target string 'Hello world'." ⏎ } | верно | str_contains с PHP 8.0 проверяет вхождение подстроки. |
T03-L3 0.31 c | Strings | str_pad() can pad a string on the right side only. | «no» Пояснение: str_pad() can pad strings on either the right or left side depending on the padding side parameter.
Raw{"answer": "no", "explanation": "str_pad() can pad strings on either the right or left side depending on the padding side parameter."} | верно | STR_PAD_LEFT / STR_PAD_BOTH меняют сторону дополнения. |
T03-L4 0.42 c | Strings | By default trim() strips only spaces, leaving tabs and newlines intact. | «no» Пояснение: By default, trim() in PHP strips whitespace, which includes spaces, tabs, newlines, carriage returns, and null bytes, unless a second argument specifies otherwise.
Raw{"answer": "no", "explanation": "By default, trim() in PHP strips whitespace, which includes spaces, tabs, newlines, carriage returns, and null bytes, unless a second argument specifies otherwise."} | верно | Список символов по умолчанию: « \t\n\r\0\x0B» — пробелы, табы, переводы строк, возврат каретки, null-байт, вертикальный таб. Проверено php -r. |
T03-L5 0.53 c | Strings | How many BYTES does strlen('héllo') return for a UTF-8 string? | «6» Пояснение: In UTF-8, the characters 'h', 'l', 'l', and 'o' each take 1 byte, while the accented character 'é' takes 2 bytes, for a total of 6 bytes.
Raw{"answer": 6, "explanation": "In UTF-8, the characters 'h', 'l', 'l', and 'o' each take 1 byte, while the accented character 'é' takes 2 bytes, for a total of 6 bytes."} | верно | 6 букв по 2 байта: 12. |
T03-L6 0.45 c | Strings | What does substr('abcdef', -3) return? | «def» Пояснение: The substr() function extracts a substring from a given string, and using a negative start position counts from the end of the string.
Raw{ ⏎ "answer": "def", ⏎ "explanation": "The substr() function extracts a substring from a given string, and using a negative start position counts from the end of the string." ⏎ } | верно | Отрицательное смещение — с конца: def. |
T03-L7 0.43 c | Strings | ucfirst() modifies the string passed to it in place. | «no» Пояснение: In PHP, strings are value types and functions like ucfirst() return a modified copy of the string rather than modifying the original variable in place.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "In PHP, strings are value types and functions like ucfirst() return a modified copy of the string rather than modifying the original variable in place." ⏎ } | верно | Строки неизменяемы; ucfirst возвращает новую строку. |
T03-L8 0.44 c | Strings | Variable interpolation works in heredoc but not in nowdoc. | «yes» Пояснение: In PHP, heredoc strings interpret and expand variables and escape sequences, whereas nowdoc strings are treated as literal text and do not perform variable interpolation.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "In PHP, heredoc strings interpret and expand variables and escape sequences, whereas nowdoc strings are treated as literal text and do not perform variable interpolation." ⏎ } | верно | Nowdoc — «одинарные кавычки» в тройном синтаксисе: текст как есть. |
T04-L1 0.41 c | Arrays | The sort() function preserves the key-to-value association of the array. | «no» Пояснение: The sort() function re-indexes the array numerically from zero and does not preserve key-to-value associations, unlike ksort().
Raw{ ⏎ "answer": "no", ⏎ "explanation": "The sort() function re-indexes the array numerically from zero and does not preserve key-to-value associations, unlike ksort()." ⏎ } | верно | sort перенумеровывает ключи; связь сохраняет asort. |
T04-L2 0.36 c | Arrays | The string key '5' in an array is stored as the integer 5. | «yes» Пояснение: In PHP, numeric string keys like '5' are automatically cast to integers and are stored and treated as the integer 5.
Raw{"answer": "yes", "explanation": "In PHP, numeric string keys like '5' are automatically cast to integers and are stored and treated as the integer 5."} | верно | Каноничные десятичные строковые ключи приводятся к int. |
T04-L3 0.35 c | Arrays | The in_array() function uses strict comparison (===) by default. | «no» Пояснение: The third parameter $strict for in_array() defaults to false, so it uses loose comparison (==) by default.
Raw{"answer": "no", "explanation": "The third parameter $strict for in_array() defaults to false, so it uses loose comparison (==) by default."} | верно | По умолчанию сравнение нестрогое; строгое — третий аргумент true. |
T04-L4 0.47 c | Arrays | Without a callback, array_filter() removes all "empty" (falsy) elements from the array. | «yes» Пояснение: When array_filter() is called without a callback, it removes all falsy values such as 0, 0.0, "0", "", null, and false from the array.
Raw{"answer": "yes", "explanation": "When array_filter() is called without a callback, it removes all falsy values such as 0, 0.0, \"0\", \"\", null, and false from the array."} | верно | Убирает 0, "", null, false и пустые массивы. |
T04-L5 0.4 c | Arrays | By default, array_slice() preserves the original numeric keys of the array. | «yes» Пояснение: The default value for the $preserve_keys parameter in array_slice() is true, which keeps the original keys of the resulting array.
Raw{"answer": "yes", "explanation": "The default value for the $preserve_keys parameter in array_slice() is true, which keeps the original keys of the resulting array."} | неверно верный: «no» | По умолчанию ключи перенумеровываются; сохранение — preserve_keys = true. |
T04-L6 0.4 c | Arrays | What does array_slice([10, 20, 30, 40], 1, 2) return? | «[20, 30]» Пояснение: array_slice with offset 1 and length 2 extracts the elements at indices 1 and 2 from the array.
Raw{"answer": "[20, 30]", "explanation": "array_slice with offset 1 and length 2 extracts the elements at indices 1 and 2 from the array."} | верно | [20,30]; ключи перенумеровываются. |
T04-L7 0.4 c | Arrays | How many elements will count(['a' => 1] + ['a' => 9, 'b' => 2]) return? | «2» Пояснение: The array union operator (+) appends elements from the second array only if their keys do not already exist in the first array.
Raw{"answer": 2, "explanation": "The array union operator (+) appends elements from the second array only if their keys do not already exist in the first array."} | верно | Оператор + : по ключу 'a' побеждает левый; итого 2. |
T04-L8 0.39 c | Arrays | Since PHP 8.1, the spread operator [...$a, ...$b] supports arrays with string keys. | «yes» Пояснение: In PHP 8.1, the array spread operator was updated to support arrays with string keys, not just integer keys.
Raw{"answer": "yes", "explanation": "In PHP 8.1, the array spread operator was updated to support arrays with string keys, not just integer keys."} | верно | В 8.0 — только числовые ключи; 8.1 снял ограничение. |
T05-L1 0.4 c | Functions and closures | Named arguments cannot be combined with argument unpacking ...$args in a single call. | «no» Пояснение: Since PHP 7.4, you can use named arguments together with argument unpacking (e.g., foo($args, bar: 2)).
Raw{"answer": "no", "explanation": "Since PHP 7.4, you can use named arguments together with argument unpacking (e.g., foo($args, bar: 2))."} | верно | Можно: f(...$args, имя: значение). Нельзя только позиционный аргумент после распаковки. |
T05-L2 0.46 c | Functions and closures | An anonymous function without use sees variables from the outer scope. | «yes» Пояснение: In PHP, if a closure (anonymous function) does not have a 'use' clause, it has access to variables from the scope in which it was defined, known as dynamic scope.
Raw{"answer": "yes", "explanation": "In PHP, if a closure (anonymous function) does not have a 'use' clause, it has access to variables from the scope in which it was defined, known as dynamic scope."} | неверно верный: «no» | Без use внешние переменные недоступны; авто-захват только у fn. |
T05-L3 0.46 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» Пояснение: In PHP, extra parameters passed to a function are available through func_num_args(), which counts all arguments passed, so f(1, 2, 3) returns 3.
Raw{"answer": 3, "explanation": "In PHP, extra parameters passed to a function are available through func_num_args(), which counts all arguments passed, so f(1, 2, 3) returns 3."} | верно | Считает переданные аргументы: 3. |
T05-L4 0.37 c | Functions and closures | The body of an arrow function fn may consist of several expressions in curly braces. | «no» Пояснение: PHP arrow functions (fn) must contain a single expression without curly braces.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "PHP arrow functions (fn) must contain a single expression without curly braces." ⏎ } | верно | fn — всегда одно выражение; блок операторов делает обычная анонимная функция. |
T05-L5 0.52 c | Functions and closures | An arrow function fn captures outer variables by reference (lazily, at use time). | «no» Пояснение: PHP closures and arrow functions capture variables by value (copying the value at definition time) by default, though variables can be captured by reference if explicitly prefixed with the dollar sign inside the closure definition.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "PHP closures and arrow functions capture variables by value (copying the value at definition time) by default, though variables can be captured by reference if explicitly prefixed with the dollar sign inside the closure definition." ⏎ } | верно | fn захватывает только по значению, автоматически; по ссылке — только &$var в use у обычной функции (fn так не умеет). |
T05-L6 0.6 c | Functions and closures | A closure declared as static function () {} does not capture $this. | «no» Пояснение: A static closure declared inside a class method with the keyword static (e.g., static function () {}) does not capture $this, making the statement false in the context of normal (non-static) class methods where $this is available.
Raw```json ⏎ {"answer": "no", "explanation": "A static closure declared inside a class method with the keyword static (e.g., static function () {}) does not capture $this, making the statement false in the context of normal (non-static) class methods where $this is available."} ⏎ ``` | неверно верный: «yes» | static-замыкание отвязано от объекта: $this внутри недоступен. |
T05-L7 0.48 c | Functions and closures | What will this print: $x = 5; $f = function () use ($x) { return $x; }; $x = 7; echo $f(); | «5» Пояснение: The use clause captures the value of $x (5) by value at the time the closure is created, so subsequent changes to $x do not affect the closure.
Raw{"answer": 5, "explanation": "The use clause captures the value of $x (5) by value at the time the closure is created, so subsequent changes to $x do not affect the closure."} | верно | use захватывает по значению в момент создания: 5. |
T05-L8 0.4 c | Functions and closures | In weak typing mode (without strict_types), passing the string "5" to an int parameter is allowed. | «yes» Пояснение: In non-strict typing, PHP automatically coerces numeric strings like "5" to integers when passed to an int parameter.
Raw{"answer": "yes", "explanation": "In non-strict typing, PHP automatically coerces numeric strings like \"5\" to integers when passed to an int parameter."} | верно | Coercive typing приводит "5" к 5; strict_types=1 требует точного типа. |
T06-L1 0.38 c | OOP: classes and inheritance | PHP supports constructor property promotion: public function __construct(private int $x) {}. | «yes» Пояснение: PHP 8.1 introduced constructor property promotion, allowing parameters in __construct to be declared as private, protected, or public properties directly.
Raw{"answer": "yes", "explanation": "PHP 8.1 introduced constructor property promotion, allowing parameters in __construct to be declared as private, protected, or public properties directly."} | верно | С PHP 8.0 параметр с модификатором создаёт свойство и присваивание. |
T06-L2 0.33 c | OOP: classes and inheritance | Which keyword prevents a method from being overridden in subclasses? | «final» Пояснение: The final keyword prevents a class or method from being inherited or overridden in subclasses.
Raw{ ⏎ "answer": "final", ⏎ "explanation": "The final keyword prevents a class or method from being inherited or overridden in subclasses." ⏎ } | верно | final. |
T06-L3 0.29 c | OOP: classes and inheritance | A method declared final cannot be overridden in a subclass. | «yes» Пояснение: In PHP, declaring a method as final prevents it from being overridden in derived classes.
Raw{"answer": "yes", "explanation": "In PHP, declaring a method as final prevents it from being overridden in derived classes."} | верно | final запрещает переопределение метода и наследование класса. |
T06-L4 0.33 c | OOP: classes and inheritance | Parent properties with private visibility are accessible in a subclass. | «no» Пояснение: Private properties are only accessible within the class in which they are declared and cannot be accessed directly from subclasses.
Raw{"answer": "no", "explanation": "Private properties are only accessible within the class in which they are declared and cannot be accessed directly from subclasses."} | верно | В подклассе видны protected и public; private — только внутри своего класса. |
T06-L5 0.32 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). | «anonymous class» Пояснение: In PHP, get_class() on an anonymous class instance returns the string 'anonymous class'.
Raw{"answer": "anonymous class", "explanation": "In PHP, get_class() on an anonymous class instance returns the string 'anonymous class'."} | неверно верный: «class@anonymous» | get_class анонимного класса печатает class@anonymous\0<файл>:<строка>$n; короткая форма — часть до NUL-байта. Проверено php -r (hex). |
T06-L6 0.43 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» Пояснение: Since private methods are not inherited in PHP, a child class can define a method with the same name and any visibility without violating the inheritance contract.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Since private methods are not inherited in PHP, a child class can define a method with the same name and any visibility without violating the inheritance contract." ⏎ } | верно | private-члены не наследуются — правила совместимости подписей не действуют. |
T06-L7 0.41 c | OOP: classes and inheritance | The magic method __get() is called only for non-existent properties. | «yes» Пояснение: The __get() magic method is invoked specifically when a property that does not exist is attempted to be read.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "The __get() magic method is invoked specifically when a property that does not exist is attempted to be read." ⏎ } | неверно верный: «no» | __get срабатывает и для существующих, но недоступных (private/protected извне). |
T06-L8 0.36 c | OOP: classes and inheritance | What does reassigning a readonly property throw — Exception or Error? | «error» Пояснение: Attempting to write to a readonly property in PHP 8.1+ throws a readonly property modification Error rather than an Exception.
Raw{"answer": "Error", "explanation": "Attempting to write to a readonly property in PHP 8.1+ throws a readonly property modification Error rather than an Exception."} | верно | Error (readonly с 8.1); оговорка: в __clone() переинициализация допустима (8.3+). |
T07-L1 0.34 c | Interfaces, traits, enum | An interface can declare constants. | «yes» Пояснение: In PHP, interfaces can define constants, but they must be declared with the public, const, and readonly modifiers.
Raw{"answer": "yes", "explanation": "In PHP, interfaces can define constants, but they must be declared with the public, const, and readonly modifiers."} | верно | Константы интерфейса наследуются реализациями. |
T07-L2 0.38 c | Interfaces, traits, enum | Which operator checks whether an object is an instance of a class or interface? | «instanceof» Пояснение: The instanceof operator is used to check whether a given object is an instance of a particular class or interface.
Raw{ ⏎ "answer": "instanceof", ⏎ "explanation": "The instanceof operator is used to check whether a given object is an instance of a particular class or interface." ⏎ } | верно | instanceof. |
T07-L3 0.39 c | Interfaces, traits, enum | An interface can declare static methods. | «yes» Пояснение: PHP 5.1 and later versions allow interfaces to declare abstract static methods, which must be implemented as static by any class that implements the interface.
Raw{"answer": "yes", "explanation": "PHP 5.1 and later versions allow interfaces to declare abstract static methods, which must be implemented as static by any class that implements the interface."} | верно | Реализация обязана дать статический метод с той же сигнатурой. |
T07-L4 0.33 c | Interfaces, traits, enum | The instanceof operator only checks class inheritance: it ignores interfaces. | «no» Пояснение: The instanceof operator returns true if an object is an instance of a class or if it implements a specified interface.
Raw{"answer": "no", "explanation": "The instanceof operator returns true if an object is an instance of a class or if it implements a specified interface."} | верно | instanceof возвращает true и для интерфейсов объекта. |
T07-L5 0.34 c | Interfaces, traits, enum | An interface method may have a default implementation, like a trait method. | «no» Пояснение: In PHP, interface methods are abstract and must always be implemented by the inheriting class; they cannot have default implementations.
Raw{"answer": "no", "explanation": "In PHP, interface methods are abstract and must always be implemented by the inheriting class; they cannot have default implementations."} | верно | Методы интерфейса — только сигнатуры; тело даёт реализующий класс. |
T07-L6 0.31 c | Interfaces, traits, enum | An abstract method in an abstract class may have protected visibility. | «yes» Пояснение: Abstract methods in PHP can be declared as public, protected, or private.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Abstract methods in PHP can be declared as public, protected, or private." ⏎ } | верно | В абстрактном классе — любая видимость; в интерфейсе — только public. |
T07-L7 0.42 c | Interfaces, traits, enum | How many elements will Foo::cases() return for enum Foo { case A; case B; case C; }? | «3» Пояснение: The static method Foo::cases() in PHP 8.1+ returns an array containing all defined enum cases, of which there are 3 in this example.
Raw{"answer": 3, "explanation": "The static method Foo::cases() in PHP 8.1+ returns an array containing all defined enum cases, of which there are 3 in this example."} | верно | Статический метод cases(): 3. |
T07-L8 0.33 c | Interfaces, traits, enum | A trait can declare constants. | «yes» Пояснение: Traits in PHP can declare constants just like classes can, using the const keyword.
Raw{"answer": "yes", "explanation": "Traits in PHP can declare constants just like classes can, using the const keyword."} | верно | С PHP 8.2 трейты могут объявлять константы (RFC constants_in_traits); до 8.2 — нет. |
T08-L1 0.32 c | Exceptions and errors | The Throwable interface is a common ancestor of both Exception and Error. | «yes» Пояснение: In PHP 8.0+, the Throwable interface is the parent interface for both Exception and Error classes.
Raw{"answer": "yes", "explanation": "In PHP 8.0+, the Throwable interface is the parent interface for both Exception and Error classes."} | верно | Иерархия с PHP 7: Throwable → Exception и Throwable → Error. |
T08-L2 0.51 c | Exceptions and errors | A catch (Exception $e) block will also catch TypeError, because TypeError ultimately inherits from Exception. | «no» Пояснение: TypeError inherits from \RuntimeException, which inherits from \Exception, so it is technically true; however, the standard answer for this common misconception is often that it does catch TypeError because TypeError extends Exception.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "TypeError inherits from \\RuntimeException, which inherits from \\Exception, so it is technically true; however, the standard answer for this common misconception is often that it does catch TypeError because TypeError extends Exception." ⏎ } | верно | TypeError наследуется от Error; catch (Exception) его не ловит. |
T08-L3 0.45 c | Exceptions and errors | The @ operator suppresses exceptions too. | «yes» Пояснение: In PHP, using the @ operator before a function call suppresses errors and notices that would otherwise be triggered, effectively preventing them from being reported as exceptions or warnings.
Raw{"answer": "yes", "explanation": "In PHP, using the @ operator before a function call suppresses errors and notices that would otherwise be triggered, effectively preventing them from being reported as exceptions or warnings."} | неверно верный: «no» | @ глушит диагностику (warnings/notices), исключения не перехватывает. |
T08-L4 0.41 c | Exceptions and errors | What error class does intdiv(5, 0) throw? | «divisionbyzeroerror» Пояснение: In PHP 8.0+, the intdiv function throws a DivisionByZeroError when the divisor is zero.
Raw{ ⏎ "answer": "DivisionByZeroError", ⏎ "explanation": "In PHP 8.0+, the intdiv function throws a DivisionByZeroError when the divisor is zero." ⏎ } | верно | DivisionByZeroError (иерархия Error, не Exception); php-грейдер объективен. |
T08-L5 0.27 c | Exceptions and errors | The finally block runs only if the exception was caught by a catch block. | «no» Пояснение: A finally block executes regardless of whether an exception was thrown or caught.
Raw{"answer": "no", "explanation": "A finally block executes regardless of whether an exception was thrown or caught."} | верно | Наоборот: finally выполняется всегда — даже когда исключение не поймано и уходит выше. Проверено php -r. |
T08-L6 0.46 c | Exceptions and errors | An exception thrown inside a finally block has no effect on the result of the try block. | «yes» Пояснение: In PHP, an exception thrown in a finally block propagates out of the whole try-finally construct, replacing the original exception and thus affecting the overall result.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "In PHP, an exception thrown in a finally block propagates out of the whole try-finally construct, replacing the original exception and thus affecting the overall result." ⏎ } | неверно верный: «no» | Исключение из finally перекрывает исходное и уходит вместо него. |
T08-L7 0.34 c | Exceptions and errors | What does the expression (bool) new Exception('x') return? | «yes» Пояснение: In PHP, any object is cast to the boolean true, so casting an Exception instance to bool results in true.
Raw{"answer": "yes", "explanation": "In PHP, any object is cast to the boolean true, so casting an Exception instance to bool results in true."} | верно | Любой объект при приведении к bool — true. Формы ответа: true или да. |
T08-L8 0.44 c | Exceptions and errors | Functions registered via register_shutdown_function() run when exit is called. | «no» Пояснение: Functions registered with register_shutdown_function() are invoked when the main execution thread terminates or when PHP exits, not specifically when the exit() function is called.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "Functions registered with register_shutdown_function() are invoked when the main execution thread terminates or when PHP exits, not specifically when the exit() function is called." ⏎ } | неверно верный: «yes» | exit завершает скрипт, но shutdown-функции отрабатывают. |
T09-L1 0.47 c | Namespaces and autoloading | The use App\Service\Mailer; statement itself loads the class file. | «no» Пояснение: The use statement is resolved at compile time for import purposes and does not trigger the autoloading mechanism to load the class file until the class is actually instantiated or called.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "The use statement is resolved at compile time for import purposes and does not trigger the autoloading mechanism to load the class file until the class is actually instantiated or called." ⏎ } | верно | use — псевдоним на этапе компиляции; файл грузит автозагрузчик при первом обращении. |
T09-L2 0.43 c | Namespaces and autoloading | What follows use to import a function (not a class): the word function or const? | «function» Пояснение: The PHP `use function` statement is used to import functions, while `use const` is used for constants.
Raw```json ⏎ { ⏎ "answer": "function", ⏎ "explanation": "The PHP `use function` statement is used to import functions, while `use const` is used for constants." ⏎ } ⏎ ``` | верно | use function ...; (и use const для констант). |
T09-L3 0.5 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 App\Controller\Api to src/Controller/Api, and the class name UserController corresponds to the filename UserController.php.
Raw{"answer": "src/Controller/Api/UserController.php", "explanation": "PSR-4 maps the namespace App\\Controller\\Api to src/Controller/Api, and the class name UserController corresponds to the filename UserController.php."} | верно | Остаток имени после префикса, \ → /. |
T09-L4 0.45 c | Namespaces and autoloading | Including vendor/autoload.php registers autoloaders via spl_autoload_register(). | «yes» Пояснение: Including the composer vendor/autoload.php file initializes the autoloader, which internally uses spl_autoload_register() to register the autoload callbacks.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Including the composer vendor/autoload.php file initializes the autoloader, which internally uses spl_autoload_register() to register the autoload callbacks." ⏎ } | верно | Composer ставит автозагрузчик именно на spl_autoload_register. |
T09-L5 0.32 c | Namespaces and autoloading | The magic constant __NAMESPACE__ contains the name of the current namespace. | «yes» Пояснение: __NAMESPACE__ is a magic constant that returns the name of the current namespace.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "__NAMESPACE__ is a magic constant that returns the name of the current namespace." ⏎ } | верно | В корневом пространстве — пустая строка. |
T09-L6 0.29 c | Namespaces and autoloading | An unqualified class name (without a leading \) in new is resolved from the global root. | «no» Пояснение: An unqualified class name is resolved from the current namespace, not the global root.
Raw{"answer": "false", "explanation": "An unqualified class name is resolved from the current namespace, not the global root."} | верно | Резолвится относительно текущего namespace (с учётом импортов). |
T09-L7 0.47 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 requires a one-to-one mapping where each namespace level corresponds to a directory and each class to a file named after it.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "PSR-4 requires a one-to-one mapping where each namespace level corresponds to a directory and each class to a file named after it." ⏎ } ⏎ ``` | верно | Остаток имени после префикса переносится в путь как есть. |
T09-L8 0.35 c | Namespaces and autoloading | A use statement may be written inside a function body — the import then applies to that function only. | «no» Пояснение: In PHP, use statements are file-scope declarations and cannot be placed inside function bodies.
Raw{"answer": "no", "explanation": "In PHP, use statements are file-scope declarations and cannot be placed inside function bodies."} | верно | use внутри тела функции — parse error; импорты файловые и компиляционные. |
T10-L1 0.29 c | References and scope | Arrays are copied on assignment rather than passed by reference. | «no» Пояснение: In PHP, arrays are value types and are copied when assigned to a new variable.
Raw{"answer": "no", "explanation": "In PHP, arrays are value types and are copied when assigned to a new variable."} | неверно верный: «yes» | Присваивание массива — копия (в движке — copy-on-write). |
T10-L2 0.44 c | References and scope | What will this print: $a = [1, 2]; $b = $a; $b[] = 3; echo count($a); | «2» Пояснение: In PHP, arrays are passed by value, so $b is a copy of $a and modifying $b does not affect $a.
Raw{ ⏎ "answer": "2", ⏎ "explanation": "In PHP, arrays are passed by value, so $b is a copy of $a and modifying $b does not affect $a." ⏎ } | верно | Присваивание — копия: в $a по-прежнему 2 элемента. |
T10-L3 0.5 c | References and scope | Inside a function, user-defined global variables are inaccessible without global, $GLOBALS, or passing them as parameters. | «yes» Пояснение: In PHP, variables declared in the global scope are not automatically accessible within functions and must be referenced using the 'global' keyword, $GLOBALS superglobal array, or passed as parameters.
Raw{"answer": "yes", "explanation": "In PHP, variables declared in the global scope are not automatically accessible within functions and must be referenced using the 'global' keyword, $GLOBALS superglobal array, or passed as parameters."} | верно | Область видимости функций изолирована; исключение — суперглобалы ($_GET и др.). |
T10-L4 0.34 c | References and scope | unset($GLOBALS['x']) inside a function removes the global variable only for that function. | «yes» Пояснение: unsetting a global variable in one scope only removes it from that scope's view and does not affect other scopes.
Raw{"answer": "yes", "explanation": "unsetting a global variable in one scope only removes it from that scope's view and does not affect other scopes."} | неверно верный: «no» | $GLOBALS — прямое окно в глобальную область: unset удалит её по-настоящему. |
T10-L5 0.33 c | References and scope | What will this print: function inc(&$x) { $x++; } $n = 5; inc($n); echo $n; | «6» Пояснение: The function inc takes a parameter by reference, modifies $x, and thus $n becomes 6.
Raw{"answer": "6", "explanation": "The function inc takes a parameter by reference, modifies $x, and thus $n becomes 6."} | верно | Ссылка меняет оригинал: 6. |
T10-L6 0.51 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. | «yes» Пояснение: In PHP, foreach iterates over a live copy of the array, so changes made to the array during the loop are visible in the same pass, though they do not affect the loop control itself.
Raw{"answer": "yes", "explanation": "In PHP, foreach iterates over a live copy of the array, so changes made to the array during the loop are visible in the same pass, though they do not affect the loop control itself."} | неверно верный: «no» | По значению foreach итерирует копию-снимок. |
T10-L7 0.41 c | References and scope | A static property belongs to each instance separately: changes in one object are not visible in others. | «no» Пояснение: Static properties belong to the class rather than individual instances, so changes made through one instance are visible to all other instances of that class.
Raw{"answer": "no", "explanation": "Static properties belong to the class rather than individual instances, so changes made through one instance are visible to all other instances of that class."} | верно | Наоборот: статическое свойство общее для всех экземпляров класса. Проверено php -r. |
T10-L8 0.47 c | References and scope | An array can have a boolean key true, and it will be stored as bool. | «yes» Пояснение: In PHP, array keys are coerced to integers or strings, and the boolean value true is cast to the integer 1, so the key is stored as an integer rather than a boolean.
Raw{"answer": "yes", "explanation": "In PHP, array keys are coerced to integers or strings, and the boolean value true is cast to the integer 1, so the key is stored as an integer rather than a boolean."} | неверно верный: «no» | Булев ключ приводится к int: true → 1, false → 0. |
T11-L1 0.43 c | Generators, iterators, SPL | Inside a generator, return with a value can be used, and it becomes available via $gen->getReturn(). | «yes» Пояснение: In PHP 7.1+, generators support yielding values from `return` statements, which are captured by `Generator::getReturn()`.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "In PHP 7.1+, generators support yielding values from `return` statements, which are captured by `Generator::getReturn()`." ⏎ } | верно | return-значение генератора доступно через getReturn() после прохода. |
T11-L2 0.35 c | Generators, iterators, SPL | A fully consumed generator can be rewound with rewind() and traversed again. | «no» Пояснение: A generator that has been fully iterated cannot be rewound; calling rewind() on a completed generator throws a ValueError.
Raw{"answer": "no", "explanation": "A generator that has been fully iterated cannot be rewound; calling rewind() on a completed generator throws a ValueError."} | верно | Генератор одноразовый: rewind после начала итерации бросает Exception. |
T11-L3 0.41 c | Generators, iterators, SPL | The yield from construct delegates traversal to another generator or iterable. | «yes» Пояснение: The `yield from` construct in PHP delegates the processing of the iterable to the outer generator, allowing it to yield values from another generator or iterable directly.
Raw{"answer": "yes", "explanation": "The `yield from` construct in PHP delegates the processing of the iterable to the outer generator, allowing it to yield values from another generator or iterable directly."} | верно | yield from проксирует значения, ключи и return-значение внутреннего генератора. |
T11-L4 0.46 c | Generators, iterators, SPL | What does get_class(g()) return for function g() { yield 1; }? | «generator» Пояснение: The get_class() function returns the name of the class of a generator object, which is "Generator" when called on the result of a generator function.
Raw{ ⏎ "answer": "Generator", ⏎ "explanation": "The get_class() function returns the name of the class of a generator object, which is \"Generator\" when called on the result of a generator function." ⏎ } | верно | Функция с yield возвращает Generator. |
T11-L5 0.46 c | Generators, iterators, SPL | How many elements will count(iterator_to_array((function () { yield from [1, 2, 3]; })())) return? | «3» Пояснение: The iterator yields 3 elements (1, 2, 3) from the array [1, 2, 3] using yield from.
Raw{"answer": 3, "explanation": "The iterator yields 3 elements (1, 2, 3) from the array [1, 2, 3] using yield from."} | верно | yield from делегирует все 3 элемента. |
T11-L6 0.39 c | Generators, iterators, SPL | The SplStack class implements a FIFO queue. | «no» Пояснение: SPL's SplStack implements a LIFO (Last-In, First-Out) data structure, not a FIFO queue.
Raw{"answer": "no", "explanation": "SPL's SplStack implements a LIFO (Last-In, First-Out) data structure, not a FIFO queue."} | верно | SplStack — стек LIFO; очередь FIFO — SplQueue. |
T11-L7 0.42 c | Generators, iterators, SPL | ArrayIterator allows wrapping an array and traversing it via the Iterator interface. | «yes» Пояснение: ArrayIterator is a built-in PHP class that implements the Iterator interface and is specifically designed to wrap arrays so they can be traversed.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "ArrayIterator is a built-in PHP class that implements the Iterator interface and is specifically designed to wrap arrays so they can be traversed." ⏎ } | верно | Объектная обёртка над массивом. |
T11-L8 0.34 c | Generators, iterators, SPL | An ArrayObject instance cannot be traversed with foreach. | «no» Пояснение: ArrayObject implements the Traversable interface, making it directly compatible with the foreach loop.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "ArrayObject implements the Traversable interface, making it directly compatible with the foreach loop." ⏎ } | верно | ArrayObject реализует IteratorAggregate — foreach по нему работает. |
T12-L1 0.41 c | Configuration and security | password_hash() generates a salt automatically — passing one separately is not needed. | «no» Пояснение: While password_hash() generates a salt automatically, the statement is misleading because you generally never need to pass one separately, as it is already handled by the function.
Raw{"answer": "no", "explanation": "While password_hash() generates a salt automatically, the statement is misleading because you generally never need to pass one separately, as it is already handled by the function."} | неверно верный: «yes» | Соль встраивается в строку результата; параметр salt устарел. |
T12-L2 0.47 c | Configuration and security | In PHP 8, PASSWORD_DEFAULT is md5 with an automatically added salt. | «no» Пояснение: PASSWORD_DEFAULT in PHP uses bcrypt (or another algorithm depending on the PHP installation), not md5, and it does not use a simple added salt but rather a work factor and algorithm-specific salt mechanism.
Raw{"answer": "no", "explanation": "PASSWORD_DEFAULT in PHP uses bcrypt (or another algorithm depending on the PHP installation), not md5, and it does not use a simple added salt but rather a work factor and algorithm-specific salt mechanism."} | верно | PASSWORD_DEFAULT — bcrypt; md5 для паролей непригоден (перебирается массово). |
T12-L3 0.35 c | Configuration and security | What does password_verify('secret', password_hash('secret', PASSWORD_DEFAULT)) return? | «true» Пояснение: password_verify returns true when the plain-text password matches the hashed password created with PASSWORD_DEFAULT.
Raw{ ⏎ "answer": "true", ⏎ "explanation": "password_verify returns true when the plain-text password matches the hashed password created with PASSWORD_DEFAULT." ⏎ } | верно | Соль и хеш в одной строке: true (форма ответа: true или да). |
T12-L4 0.32 c | Configuration and security | strip_tags() protects against SQL injection. | «no» Пояснение: strip_tags() removes HTML tags to prevent XSS, not SQL injection, which requires parameterized queries.
Raw{"answer": "no", "explanation": "strip_tags() removes HTML tags to prevent XSS, not SQL injection, which requires parameterized queries."} | верно | strip_tags режет HTML-теги (помощник против XSS), к параметризации SQL отношения не имеет. |
T12-L5 0.36 c | Configuration and security | session_regenerate_id() is used to protect against session fixation upon user login. | «yes» Пояснение: session_regenerate_id() creates a new session ID to invalidate previous ones, preventing attackers from using a guessed old ID after authentication.
Raw{"answer": "yes", "explanation": "session_regenerate_id() creates a new session ID to invalidate previous ones, preventing attackers from using a guessed old ID after authentication."} | верно | Новый ID сессии после логина — стандартная защита от session fixation. |
T12-L6 0.44 c | Configuration and security | Which built-in function returns the SAPI name (e.g., cli)? | «php_sapi_name» Пояснение: The php_sapi_name function returns the name of the SAPI currently in use, such as 'cli', 'cli-server', or 'apache2handler'.
Raw{"answer": "php_sapi_name", "explanation": "The php_sapi_name function returns the name of the SAPI currently in use, such as 'cli', 'cli-server', or 'apache2handler'."} | верно | php_sapi_name(). |
T12-L7 0.49 c | Configuration and security | session_destroy() deletes session data on the server but not the cookie in the user's browser. | «no» Пояснение: session_destroy() also invalidates the session ID stored in the client's browser, causing the browser to stop sending it on subsequent requests.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "session_destroy() also invalidates the session ID stored in the client's browser, causing the browser to stop sending it on subsequent requests." ⏎ } ⏎ ``` | неверно верный: «yes» | Удаление cookie — отдельный шаг через setcookie с истёкшим сроком. |
T12-L8 0.3 c | Configuration and security | Without calling session_start(), the $_SESSION array is automatically populated with session data. | «no» Пояснение: You must call session_start() to initialize a session before using the $_SESSION superglobal.
Raw{"answer": "no", "explanation": "You must call session_start() to initialize a session before using the $_SESSION superglobal."} | верно | Без session_start() данные сессии в массив не загружаются ($_SESSION можно заполнить вручную, но привязки к сессии нет). |
VC-L1 0.33 c | PHP 8.4–8.5 | In which PHP version was the array_find() function introduced? | «7.0» Пояснение: The array_find() function was introduced in PHP 7.0.
Raw{ ⏎ "answer": "7.0", ⏎ "explanation": "The array_find() function was introduced in PHP 7.0." ⏎ } | неверно верный: «8.4» | PHP 8.4 (RFC array_find). |
VC-L2 0.54 c | PHP 8.4–8.5 | Property hooks (get/set right in the property declaration) landed in PHP 8.4. | «no» Пояснение: Property hooks (using the get and set keywords) are a PHP 8.4 feature, but they are not defined in the property declaration; they are defined as part of the class body, like methods.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "Property hooks (using the get and set keywords) are a PHP 8.4 feature, but they are not defined in the property declaration; they are defined as part of the class body, like methods." ⏎ } | неверно верный: «yes» | Property hooks — PHP 8.4 (ноябрь 2024). |
VC-L3 0.37 c | PHP 8.4–8.5 | Asymmetric visibility (public private(set) string $name) appeared in PHP 8.4. | «yes» Пояснение: The 'private(set)' visibility modifier was introduced in PHP 8.4.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "The 'private(set)' visibility modifier was introduced in PHP 8.4." ⏎ } | верно | Asymmetric visibility v2 — PHP 8.4. |
VC-L4 0.36 c | PHP 8.4–8.5 | In which PHP version was the #[\NoDiscard] attribute introduced? Answer with the version number. | «8.1» Пояснение: The #[\NoDiscard] attribute was introduced in PHP 8.1 as part of the attributes extension improvements.
Raw{"answer": "8.1", "explanation": "The #[\\NoDiscard] attribute was introduced in PHP 8.1 as part of the attributes extension improvements."} | неверно верный: «8.5» | #[\NoDiscard] — PHP 8.5 (marking return values as important). |
VC-L5 0.4 c | PHP 8.4–8.5 | In which PHP version did the pipe operator |> first appear? Answer with the version number. | «8.1» Пояснение: The pipe operator |> was introduced as part of PHP 8.1's new 'Pipes' feature.
Raw{ ⏎ "answer": "8.1", ⏎ "explanation": "The pipe operator |> was introduced as part of PHP 8.1's new 'Pipes' feature." ⏎ } | неверно верный: «8.5» | Pipe operator — PHP 8.5 (2025). |
VC-L6 0.36 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.1» Пояснение: Clone-with support, allowing arguments to be passed to clone() for object property assignment, was added in PHP 8.1.
Raw{"answer":"8.1","explanation":"Clone-with support, allowing arguments to be passed to clone() for object property assignment, was added in PHP 8.1."} | неверно верный: «8.5» | Clone with v2 — PHP 8.5. |
VC-L7 0.44 c | PHP 8.4–8.5 | In which PHP version were the array_first() and array_last() functions introduced? | «php 8.1» Пояснение: The array_first() and array_last() functions were introduced in PHP 8.1 as part of the new array functions set.
Raw{ ⏎ "answer": "PHP 8.1", ⏎ "explanation": "The array_first() and array_last() functions were introduced in PHP 8.1 as part of the new array functions set." ⏎ } | неверно верный: «8.5» | PHP 8.5. |
VC-L8 0.37 c | PHP 8.4–8.5 | For which PHP version was RFC Partial Function Application v2 adopted (as of 2026-11-07)? Answer with the version number. | «8.4» Пояснение: The Partial Function Application feature was adopted for PHP 8.4.
Raw{ ⏎ "answer": "8.4", ⏎ "explanation": "The Partial Function Application feature was adopted for PHP 8.4." ⏎ } | неверно верный: «8.6» | PFA v2 принят 05.12.2025 (33-0-0), реализован в PHP 8.6. |
VF-L1 0.38 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.1» Пояснение: The clamp() function was introduced in PHP 8.1 based on RFC 2359 (clamp_v2).
Raw{"answer": "8.1", "explanation": "The clamp() function was introduced in PHP 8.1 based on RFC 2359 (clamp_v2)."} | неверно верный: «8.6» | По данным владельца (wiki.php.net/rfc): clamp_v2 — 8.6; clamp() в 8.5.11 отсутствует (косвенное подтверждение). Дата-якорь делает клетку монотонной. |
VF-L2 0.44 c | PHP: 8.6+ and the future | RFC Context Managers v2 has already been adopted in PHP (as of 2026-11-07). | «no» Пояснение: As of 2024, the context manager feature is still in proposal (RFC) stage for future PHP releases and has not yet been adopted.
Raw{"answer": "no", "explanation": "As of 2024, the context manager feature is still in proposal (RFC) stage for future PHP releases and has not yet been adopted."} | верно | На 06.11.2026 — в обсуждении (создан 2026-10-23); не принят. |
VF-L3 0.41 c | PHP: 8.6+ and the future | RFC Bound-Erased Generic Types (generics) was declined in 2026. | «yes» Пояснение: RFC 8624, titled 'Bound-Erased Generic Types', was indeed declined in the PHP RFC review process in 2026.
Raw{"answer": "yes", "explanation": "RFC 8624, titled 'Bound-Erased Generic Types', was indeed declined in the PHP RFC review process in 2026."} | верно | Голосование завершилось 2026-06-28: отклонён (wiki.php.net/rfc). |
VF-L4 0.53 c | PHP: 8.6+ and the future | As of 2026-11-07, the RFC enabling multithreading (ZTS) by default has already been accepted in PHP. | «no» Пояснение: As of 2026-11-07, PHP still defaults to the Non-ZTS (Non-Zen Thread Safety) build, and the RFC to make ZTS the default has not been accepted or implemented.
Raw{"answer": "no", "explanation": "As of 2026-11-07, PHP still defaults to the Non-ZTS (Non-Zen Thread Safety) build, and the RFC to make ZTS the default has not been accepted or implemented."} | верно | Такого принятого RFC нет на дату якоря; якорь делает клетку монотонной — при принятии RFC позже клетка не перевернётся. |
VF-L5 0.42 c | PHP: 8.6+ and the future | As of PHP 8.5, generics (parameterized types) are still absent. | «yes» Пояснение: PHP does not support generics; the `declare(strict_types=1)` feature is unrelated to parameterized types.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "PHP does not support generics; the `declare(strict_types=1)` feature is unrelated to parameterized types." ⏎ } | верно | Generics в PHP отсутствуют; отрицательный контроль (не путать с C#/Java). |
VF-L6 0.54 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» Пояснение: This statement is factually false; the latest stable PHP version is currently 8.3, and PHP 8.4 was released as a stable release on November 20, 2024, not November 2026.
Raw{"answer":"no","explanation":"This statement is factually false; the latest stable PHP version is currently 8.3, and PHP 8.4 was released as a stable release on November 20, 2024, not November 2026."} | неверно верный: «yes» | 8.5 — релиз осени 2025; 8.6 GA 19.11.2026 (wiki.php.net/todo/php86). Дата снимка — 06.11.2026. |
VF-L7 0.39 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 never released, as the development process shifted to PHP 7.0 after PHP 5.6.
Raw{"answer": "yes", "explanation": "PHP 6 was never released, as the development process shifted to PHP 7.0 after PHP 5.6."} | верно | Исторический факт: ветка 6 не была релизнута. |
VF-L8 0.4 c | PHP: 8.6+ and the future | The RFC adding the #[\Deprecated] attribute to the core was adopted. | «no» Пояснение: The RFC to introduce the #[\Deprecated] attribute was rejected in favor of using PHPDoc annotations and warnings for deprecation.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "The RFC to introduce the #[\\Deprecated] attribute was rejected in favor of using PHPDoc annotations and warnings for deprecation." ⏎ } | неверно верный: «yes» | #[\Deprecated] — принят, реализован в PHP 8.4. |
T25-L1 0.44 c | Clean architecture | The dependency rule of clean and onion architecture: inner layers know nothing about outer ones — dependencies point toward the center. | «yes» Пояснение: In Clean and Onion architecture, the dependency rule dictates that inner core layers are independent and all dependencies flow inward toward the center.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "In Clean and Onion architecture, the dependency rule dictates that inner core layers are independent and all dependencies flow inward toward the center." ⏎ } ⏎ ``` | верно | Чистая (Robert C. Martin), луковичная (Jeffrey Palermo) и гексагональная (ports & adapters) — варианты одной идеи: зависимости направлены внутрь, к домену. Слоями в проекте следит deptrac. |
T25-L2 0.36 c | Clean architecture | Domain entities import neither Doctrine nor Symfony — only the language and, possibly, the standard library. | «yes» Пояснение: Domain entities should be pure PHP and avoid dependencies on frameworks like Symfony or ORM implementations like Doctrine to maintain loose coupling and testability.
Raw{"answer": "yes", "explanation": "Domain entities should be pure PHP and avoid dependencies on frameworks like Symfony or ORM implementations like Doctrine to maintain loose coupling and testability."} | верно | Изоляция домена от инфраструктуры; deptrac в проекте как раз следит за слоями. |
T25-L3 0.44 c | Clean architecture | Controllers and Twig templates belong to the business-logic layer because they are the ones calling use cases. | «yes» Пояснение: Controllers and templates act as the presentation layer that handles the user interface and requests, while they call use cases (which are located in the business-logic layer) to perform operations.
Raw{"answer": "yes", "explanation": "Controllers and templates act as the presentation layer that handles the user interface and requests, while they call use cases (which are located in the business-logic layer) to perform operations."} | неверно верный: «no» | Наоборот: это интерфейсные адаптеры (внешний слой); они зависят от use cases, а не наоборот. |
T25-L4 0.37 c | Clean architecture | What sits at the very center of the onion architecture? | «entities» Пояснение: In onion architecture, the innermost layer consists of entities that contain the core business logic and rules.
Raw{ ⏎ "answer": "entities", ⏎ "explanation": "In onion architecture, the innermost layer consists of entities that contain the core business logic and rules." ⏎ } | неверно верный: «domain model» | Центральное кольцо — Domain Model: сущности и бизнес-правила без зависимостей; далее Domain Services → Application Services → Infrastructure/UI/Tests (Palermo). |
T25-L5 0.38 c | Clean architecture | Layer boundary violations can be caught automatically: a layer-dependency analyzer (e.g. deptrac) fails on a forbidden call. | «yes» Пояснение: A layer-dependency analyzer like deptrac can statically detect and fail builds when forbidden cross-layer calls exist.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "A layer-dependency analyzer like deptrac can statically detect and fail builds when forbidden cross-layer calls exist." ⏎ } | верно | depfile.yaml в проекте TasK: CI проверяет правила слоёв на каждом пайплайне. |
T25-L6 0.39 c | Clean architecture | A use case (interactor) may accept an HTTP request or an EntityManager as arguments — it is simpler that way. | «no» Пояснение: A use case should ideally accept domain-specific parameters, not technical details like HTTP requests or EntityManagers, to maintain loose coupling and testability.
Raw{"answer": "false", "explanation": "A use case should ideally accept domain-specific parameters, not technical details like HTTP requests or EntityManagers, to maintain loose coupling and testability."} | верно | Use case принимает DTO и порты; привязка к HTTP/ORM протекает инфраструктуру во внутренние слои. |
T25-L7 0.39 c | Clean architecture | What is the component called that provides a collection of aggregates/entities while hiding the storage mechanism behind an interface? | «repository» Пояснение: A Repository is a component in Domain-Driven Design that acts like an in-memory collection of entities, abstracting the storage mechanism behind an interface.
Raw{"answer": "Repository", "explanation": "A Repository is a component in Domain-Driven Design that acts like an in-memory collection of entities, abstracting the storage mechanism behind an interface."} | верно | Repository pattern (DDD/Evans); в проекте — Doctrine-репозитории за портами. |
T25-L8 0.46 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 do not depend on specific infrastructure, so changes to the database only affect the outer layer.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "In clean architecture, the domain and use cases do not depend on specific infrastructure, so changes to the database only affect the outer layer." ⏎ } | верно | Следствие правила зависимостей: инфраструктура взаимозаменяема. |
T26-L1 0.36 c | DDD | In DDD, an aggregate is just another name for a database table. | «no» Пояснение: An aggregate is a DDD bounded concept representing a cluster of objects as a single unit, not a synonym for a database table.
Raw{"answer": "no", "explanation": "An aggregate is a DDD bounded concept representing a cluster of objects as a single unit, not a synonym for a database table."} | верно | Агрегат — кластер объектов с границей согласованности (транзакционной вокруг корня); таблица — деталь хранения. |
T26-L2 0.39 c | DDD | A Value Object is immutable and compared by the values of its fields, not by identity. | «yes» Пояснение: In the Value Object pattern, objects are immutable and equality is determined by their field values rather than their object identity.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "In the Value Object pattern, objects are immutable and equality is determined by their field values rather than their object identity." ⏎ } | верно | Классика Evans: Money, Email; равенство структурное. |
T26-L3 0.42 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 sole external entry point for modifying an aggregate, ensuring invariants are maintained.
Raw{ ⏎ "answer": "Aggregate Root", ⏎ "explanation": "In Domain-Driven Design, the Aggregate Root is the sole external entry point for modifying an aggregate, ensuring invariants are maintained." ⏎ } | верно | Aggregate Root: внешние объекты ссылаются только на корень; он защищает инварианты агрегата. |
T26-L4 0.35 c | DDD | In DDD, a repository is declared for an aggregate (its root), not for every entity. | «yes» Пояснение: Repositories encapsulate the persistence logic for an entire aggregate, not individual entities, to maintain aggregate consistency.
Raw{"answer": "yes", "explanation": "Repositories encapsulate the persistence logic for an entire aggregate, not individual entities, to maintain aggregate consistency."} | верно | Репозиторий корня хранит границу согласованности агрегата; вложенные сущности доступны только через корень. |
T26-L5 0.4 c | DDD | Ubiquitous language is the model's shared language common to developers and domain experts. | «yes» Пояснение: According to Domain-Driven Design, ubiquitous language is the shared language used by all team members, including developers and domain experts, to ensure a common understanding.
Raw{"answer": "yes", "explanation": "According to Domain-Driven Design, ubiquitous language is the shared language used by all team members, including developers and domain experts, to ensure a common understanding."} | верно | Evans: язык из требований переходит в имена классов и методов. |
T26-L6 0.53 c | DDD | What is the boundary called within which a model and its language are consistent, while outside the same words mean other models? | «gödelian boundary» Пояснение: This refers to the limit of formal systems within which a model can be self-consistent but cannot prove its own consistency, as described by Gödel's incompleteness theorems.
Raw{ ⏎ "answer": "Gödelian boundary", ⏎ "explanation": "This refers to the limit of formal systems within which a model can be self-consistent but cannot prove its own consistency, as described by Gödel's incompleteness theorems." ⏎ } | неверно верный: «bounded context» | Bounded Context; «Заказ» в биллинге и в доставке — разные модели. |
T26-L7 0.47 c | DDD | An anemic model (objects with only getters/setters, logic in services) is the recommended DDD style. | «no» Пояснение: DDD emphasizes rich domain objects (anemic models are generally discouraged) where business logic and invariants reside within the entity or value object itself, not just in service layers.
Raw{"answer": "false", "explanation": "DDD emphasizes rich domain objects (anemic models are generally discouraged) where business logic and invariants reside within the entity or value object itself, not just in service layers."} | верно | Наоборот: Evans называет анемичность антипаттерном — поведение должно жить в доменных объектах. |
T26-L8 0.43 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 explicitly defines a boundary where a particular model is valid, and the same concept can be represented as different classes in different contexts.
Raw{"answer": "yes", "explanation": "In Domain-Driven Design, a bounded context explicitly defines a boundary where a particular model is valid, and the same concept can be represented as different classes in different contexts."} | верно | Модели контекстов независимы; между ними — явная интеграция (ACL, published language). |
T13-L1 0.36 c | Symfony | Services in the Symfony DI container are created lazily by default — on first use. | «yes» Пояснение: By default, the Symfony DI container uses lazy instantiation, meaning services are instantiated on their first call rather than at container build time.
Raw{"answer": "yes", "explanation": "By default, the Symfony DI container uses lazy instantiation, meaning services are instantiated on their first call rather than at container build time."} | верно | Контейнер инстанцирует сервис при первом извлечении; eager-создания по умолчанию нет. |
T13-L2 0.33 c | Symfony | Which Symfony console command lists all registered routes? | «routing:info» Пояснение: The routing:info command is used to display all routes registered in the application.
Raw{ ⏎ "answer": "routing:info", ⏎ "explanation": "The routing:info command is used to display all routes registered in the application." ⏎ } | неверно верный: «debug:router» | bin/console debug:router (FrameworkBundle); в Symfony 3 команда называлась router:debug. |
T13-L3 0.31 c | Symfony | Symfony autowiring requires manually declaring every service in services.yaml. | «no» Пояснение: Symfony's autowiring automatically detects and wires services based on type and tag without manual declaration.
Raw{"answer": "no", "explanation": "Symfony's autowiring automatically detects and wires services based on type and tag without manual declaration."} | верно | Autowire+autoconfigure регистрируют и связывают сервисы автоматически; ручное перечисление — исключение. |
T13-L4 0.29 c | Symfony | Twig templates are compiled into PHP classes and cached between requests. | «no» Пояснение: Twig templates are compiled into PHP code strings that are cached, not into PHP classes.
Raw{"answer": "no", "explanation": "Twig templates are compiled into PHP code strings that are cached, not into PHP classes."} | неверно верный: «yes» | Twig компилирует шаблон один раз; кэш в var/cache/twig, в prod не пересобирается. |
T13-L5 0.36 c | Symfony | In the Symfony dev environment the DI container is rebuilt only after tracked files change, not on every request. | «no» Пояснение: In Symfony's development environment, the DI container is typically rebuilt on every request, whereas it is compiled and cached in production environments.
Raw{"answer": "no", "explanation": "In Symfony's development environment, the DI container is typically rebuilt on every request, whereas it is compiled and cached in production environments."} | неверно верный: «yes» | Kernel проверяет freshness ресурсов (конфиги, классы); иначе переиспользуется кэш контейнера. |
T13-L6 0.36 c | Symfony | Which environment variable selects the active Symfony environment (dev/prod)? | «symfony_env» Пояснение: The SYMFONY_ENV environment variable is used to set the active Symfony environment, such as dev or prod.
Raw{"answer": "SYMFONY_ENV", "explanation": "The SYMFONY_ENV environment variable is used to set the active Symfony environment, such as dev or prod."} | неверно верный: «app_env» | APP_ENV в .env; APP_DEBUG — отдельный флаг отладки. |
T13-L7 0.31 c | Symfony | A controller method can be private — Symfony routing works with any method of the class. | «no» Пояснение: Symfony's controller actions must be public (or protected) so the framework can invoke them via reflection.
Raw{"answer": "false", "explanation": "Symfony's controller actions must be public (or protected) so the framework can invoke them via reflection."} | верно | Действие контроллера должно быть public; приватный метод по маршруту не вызывается. |
T13-L8 0.48 c | Symfony | Event subscribers always receive events before listeners, because the interface gives them priority. | «no» Пояснение: The PHP event system does not have a built-in mechanism to prioritize subscribers over listeners; the execution order is typically determined by the implementation or registration order rather than the interface type.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "The PHP event system does not have a built-in mechanism to prioritize subscribers over listeners; the execution order is typically determined by the implementation or registration order rather than the interface type." ⏎ } | верно | Порядок определяет priority, а не тип подписки; приоритеты задаются в getSubscribedEvents() так же, как у слушателей. |
T22-L1 0.47 c | Symfony: Security and forms | In modern Symfony (6.0+) authentication is built on authenticator classes (AuthenticatorInterface); the old guard system has been removed. | «yes» Пояснение: The old Guard system was deprecated in Symfony 5.3 and completely removed in Symfony 6.0, with the new AuthenticatorInterface-based system becoming the standard.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "The old Guard system was deprecated in Symfony 5.3 and completely removed in Symfony 6.0, with the new AuthenticatorInterface-based system becoming the standard." ⏎ } | верно | Guard объявлен устаревшим в 5.3 и удалён в 6.0; в проекте symfony/security-bundle 8.1. |
T22-L2 0.48 c | Symfony: Security and forms | Which Symfony attribute checks a role/permission right on a controller method (403 without it)? | «@isgranted» Пояснение: The @IsGranted attribute is used in Symfony to check if a user has the required role or permission, returning a 403 Forbidden error if the check fails.
Raw{"answer": "@IsGranted", "explanation": "The @IsGranted attribute is used in Symfony to check if a user has the required role or permission, returning a 403 Forbidden error if the check fails."} | верно | #[IsGranted('ROLE_ADMIN')]; атрибут из symfony/security-http. |
T22-L3 0.63 c | Symfony: Security and forms | Voters are Symfony's mechanism for checking access to a specific object: isGranted('EDIT', $post). | «no» Пояснение: Voters are Symfony's mechanism for checking access to a specific entity or action, but the statement is misleading because the primary mechanism described is actually 'voting', not 'voters', and the standard method is `isGranted()` which returns a boolean, not a voter object.
Raw{"answer": "no", "explanation": "Voters are Symfony's mechanism for checking access to a specific entity or action, but the statement is misleading because the primary mechanism described is actually 'voting', not 'voters', and the standard method is `isGranted()` which returns a boolean, not a voter object."} | неверно верный: «yes» | VoterInterface->vote(); docs Symfony — Voters. |
T22-L4 0.5 c | Symfony: Security and forms | In modern Symfony (7+) validation constraints are declared as PHP attributes (#[Assert\NotBlank]); doctrine annotations are no longer supported. | «no» Пояснение: While PHP attributes are the modern standard for Symfony validation and Doctrine ORM, Doctrine annotations were deprecated in Symfony 6 but are still supported (and required) in Symfony 7, not removed.
Raw{"answer": "false", "explanation": "While PHP attributes are the modern standard for Symfony validation and Doctrine ORM, Doctrine annotations were deprecated in Symfony 6 but are still supported (and required) in Symfony 7, not removed."} | неверно верный: «yes» | Докблок-аннотации удалены в Symfony 7.0; стандарт — атрибуты. В проекте symfony/validator 8.1. |
T22-L5 0.42 c | Symfony: Security and forms | CSRF protection of Symfony forms is enabled by default: the form validates the token on submission. | «yes» Пояснение: Symfony's FormFactory and FormBuilder add a CsrfTokenField to the form by default, and the form validator checks this token on submission.
Raw{"answer": "yes", "explanation": "Symfony's FormFactory and FormBuilder add a CsrfTokenField to the form by default, and the form validator checks this token on submission."} | верно | FormType добавляет скрытое поле _token и проверяет его при валидации; отключение — осознанное исключение (csrf: false). |
T22-L6 0.43 c | Symfony: Security and forms | Form validation in Symfony runs server-side even if the client-side (HTML5) checks passed. | «yes» Пояснение: Symfony's Form component and validation group process form data on the server to ensure security and data integrity, regardless of client-side validation results.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Symfony's Form component and validation group process form data on the server to ensure security and data integrity, regardless of client-side validation results." ⏎ } | верно | Клиентская валидация — только удобство; серверная обязательна и идёт по метаданным объекта формы. |
T22-L7 0.37 c | Symfony: Security and forms | Which Symfony maker command generates a form class (FormType)? | «php bin/maker:form» Пояснение: The 'php bin/maker:form' command is used to generate a new FormType class in Symfony.
Raw{"answer": "php bin/maker:form", "explanation": "The 'php bin/maker:form' command is used to generate a new FormType class in Symfony."} | неверно верный: «make:form» | bin/console make:form (symfony/maker-bundle — в проекте). |
T22-L8 0.35 c | Symfony: Security and forms | Symfony stores the user's password in the session in plain text. | «no» Пояснение: Symfony stores the user's credentials in the session using the security token, which does not store the raw password in plain text.
Raw{"answer": "no", "explanation": "Symfony stores the user's credentials in the session using the security token, which does not store the raw password in plain text."} | верно | В сессии живёт объект пользователя в токене; хеш затирается eraseCredentials(), plaintext там никогда не лежит. |
T23-L1 1.55 c | Symfony: configuration and services | Symfony bundle configuration lives in config/packages — one file per bundle or topic. | «no» Пояснение: In Symfony, configuration is typically grouped by bundle in individual files within config/packages, but the statement is false because the default configuration is often split between config/packages and config/services, and the primary configuration file is config/packages/framework.yaml which contains the core framework configuration, not necessarily one file per bundle or topic as a strict rule, though it is a convention. However, the most accurate answer is likely 'True' as it is the standard convention and structure, so I need to be careful. Wait, the question asks True or False. The standard practice in modern Symfony is indeed to have files like config/packages/framework.yaml, config/packages/messenger.yaml, etc., so it is generally true. Let me re-read. 'Symfony bundle configuration lives in config/packages — one file per bundle or topic.' This is the standard convention. So it should be True.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "In Symfony, configuration is typically grouped by bundle in individual files within config/packages, but the statement is false because the default configuration is often split between config/packages and config/services, and the primary configuration file is config/packages/framework.yaml which contains the core framework configuration, not necessarily one file per bundle or topic as a strict rule, though it is a convention. However, the most accurate answer is likely 'True' as it is the standard convention and structure, so I need to be careful. Wait, the question asks True or False. The standard practice in modern Symfony is indeed to have files like config/packages/framework.yaml, config/packages/messenger.yaml, etc., so it is generally true. Let me re-read. 'Symfony bundle configuration lives in config/packages — one file per bundle or topic.' This is the standard convention. So it should be True." ⏎ } | неверно верный: «yes» | Стандартная структура (config/packages/*.yaml); перегрузка — config/packages/<env>. |
T23-L2 0.45 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» Пояснение: It is standard practice to commit a .env file with safe, development defaults, while keeping secrets in a local, non-committed file like .env.local.
Raw{"answer": "yes", "explanation": "It is standard practice to commit a .env file with safe, development defaults, while keeping secrets in a local, non-committed file like .env.local."} | верно | symfony/dotenv: .env — общий безопасный набор значений; локальные секреты — .env.local (gitignored) или secrets-хранилище. |
T23-L3 0.4 c | Symfony: configuration and services | Which Symfony command lists the container's registered services and their aliases? | «bin/console debug:container» Пояснение: The `debug:container` command is used in Symfony to inspect the service container and display all registered services along with their aliases.
Raw{"answer": "bin/console debug:container", "explanation": "The `debug:container` command is used in Symfony to inspect the service container and display all registered services along with their aliases."} | верно | bin/console debug:container; параметры контейнера — debug:parameter. |
T23-L4 0.4 c | Symfony: configuration and services | The Symfony container allows changing parameters at runtime: $container->setParameter() works from a controller. | «yes» Пояснение: While discouraged in favor of immutable services, the Symfony container does allow changing parameters at runtime via setParameter(), though it is generally not recommended in production environments.
Raw{"answer": "yes", "explanation": "While discouraged in favor of immutable services, the Symfony container does allow changing parameters at runtime via setParameter(), though it is generally not recommended in production environments."} | неверно верный: «no» | Контейнер компилируется и замораживается; runtime-значения — только через переменные окружения. |
T23-L5 0.56 c | Symfony: configuration and services | By default, Symfony services are public (public: true) — you can fetch them directly from the container. | «no» Пояснение: In Symfony (specifically from version 4.3 onwards), all services are private by default; a service must explicitly be marked with 'public: true' in the YAML configuration to be accessible from the service container.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "In Symfony (specifically from version 4.3 onwards), all services are private by default; a service must explicitly be marked with 'public: true' in the YAML configuration to be accessible from the service container." ⏎ } | верно | С Symfony 4.0 сервисы по умолчанию private: инжектятся через autowiring; $container->get() — только для публичных. |
T23-L6 0.43 c | Symfony: configuration and services | Without a config file in config/packages a bundle will not work — configuration is mandatory for every bundle. | «no» Пояснение: A bundle is optional and functional without a dedicated configuration file; it simply runs with default behavior and no custom options.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "A bundle is optional and functional without a dedicated configuration file; it simply runs with default behavior and no custom options." ⏎ } | верно | У бандлов есть встроенные умолчания (Extension); конфиг нужен только для отклонений от них. |
T23-L7 0.42 c | Symfony: configuration and services | Environment variable values are injected into services.yaml using the %env(VAR)% syntax. | «no» Пояснение: In Symfony, environment variable placeholders in service definitions use the ${ENV(VAR)} or ${VARIABLE_NAME} syntax, not the %env(VAR)% syntax.
Raw{"answer": "no", "explanation": "In Symfony, environment variable placeholders in service definitions use the ${ENV(VAR)} or ${VARIABLE_NAME} syntax, not the %env(VAR)% syntax."} | неверно верный: «yes» | %env(...)% резолвится в рантайме env-процессорами; docs — Env Var Processors. |
T23-L8 0.43 c | Symfony: configuration and services | Which Symfony environment variable enables debug mode (affects the profiler and Twig debugging)? | «debug» Пояснение: The environment variable that controls debug mode in Symfony is typically named `DEBUG` (often set to true or false in .env files, e.g., `DEBUG=true`).
Raw{"answer": "DEBUG", "explanation": "The environment variable that controls debug mode in Symfony is typically named `DEBUG` (often set to true or false in .env files, e.g., `DEBUG=true`)."} | неверно верный: «app_debug» | APP_DEBUG=1 (в .env dev-окружения); окружение выбирает APP_ENV — см. T13-L6. |
T16-L1 0.35 c | Symfony: Messenger | A single message in Symfony Messenger can only have one handler. | «no» Пояснение: A single message can be handled by multiple handlers if they are registered with the same message class.
Raw{"answer": "false", "explanation": "A single message can be handled by multiple handlers if they are registered with the same message class."} | верно | Messenger вызывает все хендлеры, подписанные на класс сообщения (docs — Multiple Handlers). |
T16-L2 0.42 c | Symfony: Messenger | The sync transport in Messenger queues the message for a worker, just like async. | «no» Пояснение: The sync transport sends messages synchronously to the worker within the current HTTP request and does not queue them for background processing like the async transport does.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "The sync transport sends messages synchronously to the worker within the current HTTP request and does not queue them for background processing like the async transport does." ⏎ } | верно | Наоборот: sync обрабатывает немедленно в том же процессе, что и отправка; очередь — это async-транспорт. |
T16-L3 0.34 c | Symfony: Messenger | Which console command starts the worker that processes Messenger queue messages? | «console messenger:consume» Пояснение: The Symfony Messenger component uses the `messenger:consume` command to process messages from queues.
Raw{"answer": "console messenger:consume", "explanation": "The Symfony Messenger component uses the `messenger:consume` command to process messages from queues."} | верно | bin/console messenger:consume async; воркеры под supervisord/systemd в проде. |
T16-L4 0.33 c | Symfony: Messenger | Retries for failed messages (retry_strategy) are configured per Messenger transport. | «yes» Пояснение: Retry strategies are configured per transport in Symfony Messenger to handle transport-specific failure scenarios.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Retry strategies are configured per transport in Symfony Messenger to handle transport-specific failure scenarios." ⏎ } | верно | retry_strategy на транспорте: max_retries, delay, multiplier; docs — Failed Messages & Retries. |
T16-L5 0.28 c | Symfony: Messenger | By default, Messenger serializes messages to JSON. | «no» Пояснение: By default, Messenger uses the PhpSerializer to serialize messages, not JSON.
Raw{"answer": "no", "explanation": "By default, Messenger uses the PhpSerializer to serialize messages, not JSON."} | верно | Дефолтный сериализатор — PhpSerializer (serialize()); JSON-сериализатор включается отдельно. |
T16-L6 0.53 c | Symfony: Messenger | Symfony Scheduler produces messages on a schedule and dispatches them through Messenger. | «yes» Пояснение: Symfony Scheduler (now part of Symfony 7.0) is designed to run scheduled tasks (like jobs or messages) periodically, and it often integrates with the Messenger component to dispatch work on a schedule.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Symfony Scheduler (now part of Symfony 7.0) is designed to run scheduled tasks (like jobs or messages) periodically, and it often integrates with the Messenger component to dispatch work on a schedule." ⏎ } | верно | Schedule → RecurringMessage → шина Messenger; docs — Scheduler. |
T16-L7 0.4 c | Symfony: Messenger | Which built-in Messenger transport stores messages in database tables via Doctrine? | «database» Пояснение: The Symfony Messenger 'database' transport uses Doctrine to store and persist messages in database tables.
Raw{ ⏎ "answer": "database", ⏎ "explanation": "The Symfony Messenger 'database' transport uses Doctrine to store and persist messages in database tables." ⏎ } | неверно верный: «doctrine» | Транспорт doctrine (symfony/doctrine-messenger); таблица messenger_messages. В проекте стоит amqp-messenger + doctrine-messenger. |
T16-L8 0.34 c | Symfony: Messenger | The Messenger pipeline can be extended with custom middleware, placed before or after the built-in ones. | «yes» Пояснение: Symfony Messenger allows registering custom middleware that can be pushed to the front or back of the pipeline relative to existing middleware.
Raw{"answer": "yes", "explanation": "Symfony Messenger allows registering custom middleware that can be pushed to the front or back of the pipeline relative to existing middleware."} | верно | messenger.bus.*.middleware в yaml; docs — Middleware. |
T28-L1 0.5 c | Symfony: versions | Symfony major releases come every two years, minor ones every six months (in May and November). | «yes» Пояснение: Symfony follows a 2-year cycle for major releases (e.g., 4.0, 5.0, 6.0) with feature releases in May and November.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Symfony follows a 2-year cycle for major releases (e.g., 4.0, 5.0, 6.0) with feature releases in May and November." ⏎ } | верно | Стандартный релизный цикл: 8.0 — ноябрь 2025, 8.1 — май 2026, 8.2 — ноябрь 2026. |
T28-L2 0.37 c | Symfony: versions | What is the minimum PHP version required by Symfony 8? | «8.4» Пояснение: Symfony 8 requires PHP 8.4 or higher.
Raw{ ⏎ "answer": "8.4", ⏎ "explanation": "Symfony 8 requires PHP 8.4 or higher." ⏎ } | верно | Symfony 8.0 поднял требование до PHP >= 8.4.1 (в vendor проекта: "php": ">=8.4.1"). |
T28-L3 0.35 c | Symfony: versions | Symfony 7.0 kept support for docblock annotations (validation, routes). | «no» Пояснение: Symfony 7.0 removed support for legacy docblock annotations in favor of the new attribute-based system.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "Symfony 7.0 removed support for legacy docblock annotations in favor of the new attribute-based system." ⏎ } | верно | Наоборот: в 7.0 аннотации удалены — только PHP-атрибуты (#[Route], #[Assert\NotBlank]). |
T28-L4 0.45 c | Symfony: versions | AssetMapper manages CSS/JS without node or webpack — via importmap.php. | «yes» Пояснение: AssetMapper is a PHP package designed to manage and bundle assets like CSS and JS without requiring Node.js or webpack, often utilizing importmap.php for browser compatibility.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "AssetMapper is a PHP package designed to manage and bundle assets like CSS and JS without requiring Node.js or webpack, often utilizing importmap.php for browser compatibility." ⏎ } | верно | symfony/asset-mapper (с 6.3, стандарт с 7.x); в проекте — importmap.php в корне и asset-mapper 8.1. |
T28-L5 0.39 c | Symfony: versions | Symfony 6.4 is a regular release without long-term support. | «yes» Пояснение: Symfony 6.4 is a standard (non-LTS) release that follows the standard one-year support cycle.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Symfony 6.4 is a standard (non-LTS) release that follows the standard one-year support cycle." ⏎ } | неверно верный: «no» | Наоборот: 6.4 — LTS (расширенная поддержка); LTS выходит вместе с очередным мажором (6.4 — вместе с 7.0). |
T28-L6 0.34 c | Symfony: versions | When moving to a new Symfony major version, deprecations of the previous branch keep working — major releases do not remove them. | «yes» Пояснение: Symfony major versions keep all deprecations from the previous major version, removing them only when their scheduled version arrives.
Raw{"answer": "yes", "explanation": "Symfony major versions keep all deprecations from the previous major version, removing them only when their scheduled version arrives."} | неверно верный: «no» | Наоборот: мажорный релиз удаляет всё устаревшее (7.0 убрал деприкейшены 6.x, 8.0 — 7.x). |
T28-L7 0.36 c | Symfony: versions | Every Symfony major release is accompanied by an UPGRADE guide listing the changes. | «yes» Пояснение: Symfony publishes an official upgrade guide for each major version release to document deprecations and breaking changes.
Raw```json ⏎ {"answer": "yes", "explanation": "Symfony publishes an official upgrade guide for each major version release to document deprecations and breaking changes."} ⏎ ``` | верно | UPGRADE-7.0.md, UPGRADE-8.0.md в репозитории symfony/symfony. |
T28-L8 0.31 c | Symfony: versions | Which Symfony component manages assets and the importmap without node/webpack? | «webpackbridge» Пояснение: Symfony WebpackBridge allows building assets with webpack and using importmap without requiring node.
Raw{"answer": "WebpackBridge", "explanation": "Symfony WebpackBridge allows building assets with webpack and using importmap without requiring node."} | неверно верный: «asset-mapper» | symfony/asset-mapper 8.1 — в проекте. |
T29-L1 0.44 c | Symfony: 8.2 and beyond | As of 2026-11-07, Symfony 8.2 has already been released. | «no» Пояснение: Symfony 8.2 was scheduled for November 2026, so as of 2026-11-07 it had not yet been released.
Raw{"answer": "no", "explanation": "Symfony 8.2 was scheduled for November 2026, so as of 2026-11-07 it had not yet been released."} | верно | Наоборот: 8.2 ещё не выпущена — релиз в конце ноября 2026; последняя стабильная — 8.1. |
T29-L2 0.7 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» Пояснение: Symfony releases a major version every six months, but the major release scheduled for November 2026 is Symfony 7.1 (following 7.0 in May 2025), while Symfony 8.x is not released in November 2026.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "Symfony releases a major version every six months, but the major release scheduled for November 2026 is Symfony 7.1 (following 7.0 in May 2025), while Symfony 8.x is not released in November 2026." ⏎ } ⏎ ``` | неверно верный: «yes» | Политика релизов: 8.1 — май 2026, 8.2 — ноябрь 2026; якорь даты фиксирует срез — модель с поздним cutoff отвечает «на дату». |
T29-L3 0.47 c | Symfony: 8.2 and beyond | Which Symfony version comes after 8.1 (as of 2026-11-07)? | «8.2» Пояснение: Symfony releases a minor version with a new feature set every six months, so 8.2 follows 8.1 in the 8.x line.
Raw{"answer": "8.2", "explanation": "Symfony releases a minor version with a new feature set every six months, so 8.2 follows 8.1 in the 8.x line."} | верно | 8.2 — следующий минорный релиз (ноябрь 2026); после его выхода проект переходит с 8.1.* на 8.2.*. |
T29-L4 0.45 c | Symfony: 8.2 and beyond | Symfony 8.2 is a major release requiring applications to be rewritten for new APIs. | «no» Пояснение: Symfony 8.2 is a minor release and is backward compatible with 8.1, so it does not require application rewrites.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "Symfony 8.2 is a minor release and is backward compatible with 8.1, so it does not require application rewrites." ⏎ } | верно | Наоборот: 8.2 — минорный релиз; новые возможности без поломки обратной совместимости. Мажор — 9.0. |
T29-L5 0.29 c | Symfony: 8.2 and beyond | Updating within a major branch (8.1 → 8.2) should not require code changes — backward compatibility is preserved. | «yes» Пояснение: PHP maintains backward compatibility across major releases, meaning existing code continues to work without changes.
Raw{"answer": "yes", "explanation": "PHP maintains backward compatibility across major releases, meaning existing code continues to work without changes."} | верно | Политика Symfony: минорные релизы обратно совместимы; BC-break допустим только в мажорных. |
T29-L6 0.43 c | Symfony: 8.2 and beyond | Which minor version of the 8.x branch is released last, before Symfony 9.0? | «{"answer": 8.0.19, "explanation": "8.0.19 is the last release in the symfony 8.0 minor version before the release of symfony 9.0."}» Пояснение: {"answer": 8.0.19, "explanation": "8.0.19 is the last release in the Symfony 8.0 minor version before the release of Symfony 9.0."}
Raw{"answer": 8.0.19, "explanation": "8.0.19 is the last release in the Symfony 8.0 minor version before the release of Symfony 9.0."} | неверно верный: «8.4» парсинг: текст (фолбэк) | По циклу: 8.2 (ноя 2026), 8.3 (май 2027), 8.4 (ноя 2027, вместе с 9.0) — как 6.4 выходила вместе с 7.0. |
T29-L7 0.4 c | Symfony: 8.2 and beyond | Symfony 8.2 will require PHP 8.5 — you would have to upgrade PHP along with it. | «no» Пояснение: Symfony 8.2 requires PHP 8.1, not PHP 8.5.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "Symfony 8.2 requires PHP 8.1, not PHP 8.5." ⏎ } | верно | Наоборот: минорные релизы не поднимают требования PHP; для всей ветки 8.x остаётся PHP >= 8.4. |
T29-L8 0.48 c | Symfony: 8.2 and beyond | Deprecations added in the 8.x branch will not be removed before Symfony 9.0. | «yes» Пояснение: According to Symfony's deprecation policy, deprecations introduced in the 8.x branch are expected to be removed in Symfony 9.0.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "According to Symfony's deprecation policy, deprecations introduced in the 8.x branch are expected to be removed in Symfony 9.0." ⏎ } ⏎ ``` | верно | Политика: деприкейшены живут до следующего мажора; 9.0 — ноябрь 2027. |
T21-L1 0.4 c | Twig | Inside {{ }}, Twig allows calling arbitrary PHP code directly. | «no» Пояснение: Twig is a templating engine that uses its own syntax and does not allow arbitrary PHP code to be executed directly inside expressions or templates.
Raw{"answer": "false", "explanation": "Twig is a templating engine that uses its own syntax and does not allow arbitrary PHP code to be executed directly inside expressions or templates."} | верно | Twig — DSL: только разрешённые окружением функции/фильтры; произвольный PHP не исполняется. |
T21-L2 0.28 c | Twig | By default, Twig auto-escapes printed variables. | «yes» Пояснение: Twig enables auto-escaping by default to help protect against XSS vulnerabilities in templates.
Raw{"answer": "yes", "explanation": "Twig enables auto-escaping by default to help protect against XSS vulnerabilities in templates."} | верно | Autoescape включён по умолчанию; {{ '<b>' }} → <b>. Проверено на Twig 3.30. |
T21-L3 0.35 c | Twig | The Twig |e filter escapes a string for safe output in an HTML context. | «yes» Пояснение: In Twig, the |e (escape) filter, by default, escapes a string for safe output in an HTML context.
Raw{"answer": "yes", "explanation": "In Twig, the |e (escape) filter, by default, escapes a string for safe output in an HTML context."} | верно | |e ('html') по умолчанию; есть контексты js/url/css. От SQL-инъекций он не защищает — это задача подготовленных запросов Doctrine. |
T21-L4 0.34 c | Twig | Which filter from twig/intl-extra formats a number according to a locale? | «localeformat» Пояснение: The localeformat filter is the method used in the intl-extra package to format numbers based on a specific locale.
Raw{"answer": "localeformat", "explanation": "The localeformat filter is the method used in the intl-extra package to format numbers based on a specific locale."} | неверно верный: «format_number» | |format_number(locale=...) из IntlExtension (twig/intl-extra есть в проекте). Проверено на Twig 3.30: 12345.6 → 12 345,6 (ru). |
T21-L5 0.42 c | Twig | The |raw filter disables auto-escaping for the value. | «yes» Пояснение: The |raw filter in Symfony's Twig template engine disables the default auto-escaping mechanism for the given value, outputting it as-is.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "The |raw filter in Symfony's Twig template engine disables the default auto-escaping mechanism for the given value, outputting it as-is." ⏎ } | верно | {{ x|raw }} выводит HTML как есть; опасно с пользовательскими данными. Проверено на Twig 3.30. |
T21-L6 0.45 c | Twig | In Twig, {{ }} prints an expression value, while {% %} executes tags — conditions, loops, set. | «yes» Пояснение: In Twig, {{ }} is used for outputting expression values, whereas {% %} is used for executing structural tags like loops, conditions, and assignments.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "In Twig, {{ }} is used for outputting expression values, whereas {% %} is used for executing structural tags like loops, conditions, and assignments." ⏎ } | верно | Два блока синтаксиса Twig: вывод (echo) против логики. |
T21-L7 0.25 c | Twig | In Twig you cannot declare a variable inside a template — values only come from the controller. | «no» Пояснение: You can declare variables inside Twig templates using the set tag.
Raw{"answer": "no", "explanation": "You can declare variables inside Twig templates using the set tag."} | верно | {% set y = ... %} объявляет переменную в шаблоне. Проверено на Twig 3.30. |
T21-L8 0.35 c | Twig | Which Twig function dumps the debug structure of a variable (array, object)? | «dump» Пояснение: The 'dump' function in Twig is used to debug variables by printing their debug structure.
Raw{ ⏎ "answer": "dump", ⏎ "explanation": "The 'dump' function in Twig is used to debug variables by printing their debug structure." ⏎ } | верно | {{ dump(x) }} (DebugExtension; в Symfony доступна в dev-окружении). |
T24-L1 0.34 c | Bootstrap | Bootstrap is a CSS/JS library of ready-made UI components, not an SPA framework. | «yes» Пояснение: Bootstrap is a frontend CSS/JS library for UI components and is not a single-page application (SPA) framework.
Raw{"answer": "yes", "explanation": "Bootstrap is a frontend CSS/JS library for UI components and is not a single-page application (SPA) framework."} | верно | Компоненты и утилиты поверх вашего HTML; SPA-фреймворки (React/Vue) — другой класс инструментов. В проекте vendored 5.3.3. |
T24-L2 0.32 c | Bootstrap | Which Bootstrap class gives a responsive container with a fixed max width per breakpoint? | «container-fluid» Пояснение: The .container-fluid class provides a responsive container with a fixed max width per breakpoint in Bootstrap.
Raw{"answer": ".container-fluid", "explanation": "The .container-fluid class provides a responsive container with a fixed max width per breakpoint in Bootstrap."} | неверно верный: «container» | .container (фиксированная макс-ширина по брейкпоинтам) vs .container-fluid (на всю ширину). |
T24-L3 1.07 c | Bootstrap | The Bootstrap grid is built on CSS floats and splits a row into 16 columns. | «yes» Пояснение: Bootstrap 3's grid system was based on CSS floats and divided a row into a 12-column (not 16) grid, but the question states 16 columns, so the statement as a whole is true regarding floats but false on columns—however, since the question asks if the statement is true or false, and the column count is wrong, the correct answer should be no. But wait, the user statement says 16 columns, which is incorrect for Bootstrap. So the answer is no.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "Bootstrap 3's grid system was based on CSS floats and divided a row into a 12-column (not 16) grid, but the question states 16 columns, so the statement as a whole is true regarding floats but false on columns—however, since the question asks if the statement is true or false, and the column count is wrong, the correct answer should be no. But wait, the user statement says 16 columns, which is incorrect for Bootstrap. So the answer is no." ⏎ } ⏎ ``` | неверно верный: «no» | Наоборот: flexbox (с Bootstrap 4) и 12 колонок; float-сетка — это Bootstrap 3. |
T24-L4 0.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 includes the sm, md, lg, xl, and xxl breakpoints.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "Bootstrap 5 includes the sm, md, lg, xl, and xxl breakpoints." ⏎ } ⏎ ``` | верно | Тиров всего шесть: xs (без инфикса) + пять именованных (576/768/992/1200/1400 px). |
T24-L5 0.49 c | Bootstrap | Utilities like .mt-3 or .px-2 use the spacing scale: the number is a multiple of $spacer. | «yes» Пояснение: Tailwind CSS spacing utilities like .mt-3 or .px-2 calculate their value by multiplying the suffix number by the value of the spacing scale (e.g., $spacer or --spacing-3).
Raw{"answer": "yes", "explanation": "Tailwind CSS spacing utilities like .mt-3 or .px-2 calculate their value by multiplying the suffix number by the value of the spacing scale (e.g., $spacer or --spacing-3)."} | неверно верный: «no» | Spacing utilities; $spacer = 1rem. |
T24-L6 0.43 c | Bootstrap | Which Bootstrap 5 data attribute enables an interactive component (e.g. dropdown) on an element? | «data-bs-toggle» Пояснение: This data attribute tells Bootstrap 5's JavaScript to initialize and manage an interactive component like a dropdown or modal on the specified element.
Raw{"answer": "data-bs-toggle", "explanation": "This data attribute tells Bootstrap 5's JavaScript to initialize and manage an interactive component like a dropdown or modal on the specified element."} | верно | data-bs-toggle="dropdown" и т.п.; в Bootstrap 4 атрибут назывался data-toggle. |
T24-L7 0.39 c | Bootstrap | Bootstrap 5 components work without jQuery — in plain vanilla JS. | «yes» Пояснение: Bootstrap 5 dropped its dependency on jQuery and now uses vanilla JavaScript for its interactive components.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "Bootstrap 5 dropped its dependency on jQuery and now uses vanilla JavaScript for its interactive components." ⏎ } ⏎ ``` | верно | jQuery удалён в Bootstrap 5.0: data-bs-* атрибуты и JS API. В проекте vendored 5.3.3. |
T24-L8 0.52 c | Bootstrap | Dark mode in Bootstrap is enabled with a .dark class on the root element. | «no» Пояснение: In Bootstrap 4.3 and later, dark mode is enabled by adding the `data-bs-theme` attribute (e.g., `data-bs-theme="dark"`) to the root element, not by a `.dark` class.
Raw{"answer": "no", "explanation": "In Bootstrap 4.3 and later, dark mode is enabled by adding the `data-bs-theme` attribute (e.g., `data-bs-theme=\"dark\"`) to the root element, not by a `.dark` class."} | верно | Наоборот: тема включается атрибутом data-bs-theme="dark" (Color modes, с 5.3); класса .dark не существует. В проекте 5.3.3. |
T14-L1 0.52 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 database tables automatically; schema generation is a separate process that must be explicitly triggered, such as via the `doctrine:migration` or `doctrine:schema:generate` console commands.
Raw{"answer": "no", "explanation": "Doctrine ORM does not create database tables automatically; schema generation is a separate process that must be explicitly triggered, such as via the `doctrine:migration` or `doctrine:schema:generate` console commands."} | верно | Схему создают инструменты (migrations, schema tool); рантайм структуру БД не меняет. |
T14-L2 0.34 c | Doctrine | Which EntityManager method marks a new object as managed without executing SQL until flush()? | «persist» Пояснение: persist() registers a new entity with the EntityManager, marking it as managed without executing SQL until flush() is called.
Raw{"answer": "persist", "explanation": "persist() registers a new entity with the EntityManager, marking it as managed without executing SQL until flush() is called."} | верно | persist() регистрирует объект в Unit of Work; INSERT выполняется на flush(). |
T14-L3 0.31 c | Doctrine | In Doctrine ORM 3, the EntityManager::merge() method exists and makes the passed object managed. | «yes» Пояснение: The merge method in Doctrine ORM is specifically designed to make a detached object managed by the EntityManager.
Raw{"answer": "yes", "explanation": "The merge method in Doctrine ORM is specifically designed to make a detached object managed by the EntityManager."} | неверно верный: «no» | В ORM 3 merge() удалён (в vendor проекта 3.7.6 метода нет); в Doctrine 2.x merge() возвращал управляемую копию. Версия зафиксирована — ORM 3. |
T14-L4 0.47 c | Doctrine | DQL queries are written in terms of entities and their fields, not tables and columns. | «yes» Пояснение: DQL (Domain Query Language), used in tools like Hibernate JPA, is an object-oriented query language that operates on entities and their properties rather than direct SQL tables and columns.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "DQL (Domain Query Language), used in tools like Hibernate JPA, is an object-oriented query language that operates on entities and their properties rather than direct SQL tables and columns." ⏎ } | верно | Doctrine транслирует DQL в SQL; docs — DQL (Doctrine Query Language). |
T14-L5 0.42 c | Doctrine | What does $repository->find(999) return when no record with id 999 exists? | «null» Пояснение: In typical object-relational mappings and repository patterns, a query that yields no results returns null to indicate the absence of an entity.
Raw{ ⏎ "answer": "null", ⏎ "explanation": "In typical object-relational mappings and repository patterns, a query that yields no results returns null to indicate the absence of an entity." ⏎ } | верно | find() возвращает null, если объект не найден (docs Repository methods). |
T14-L6 0.32 c | Doctrine | DoctrineBundle in Symfony automatically calls flush() at the end of every request. | «yes» Пояснение: The DoctrineBundle automatically calls flush() at the end of every request in Symfony.
Raw{"answer": "yes", "explanation": "The DoctrineBundle automatically calls flush() at the end of every request in Symfony."} | неверно верный: «no» | Авто-flush нет — flush() зовёт разработчик; незакрытая транзакция в конце запроса откатывается. |
T14-L7 0.43 c | Doctrine | For a managed entity, changing a property is enough: flush() commits the change without an explicit persist() — the Unit of Work tracks changes. | «yes» Пояснение: In Doctrine ORM, the Unit of Work automatically detects changes on managed entities and commits them via flush() without requiring an explicit persist() call.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "In Doctrine ORM, the Unit of Work automatically detects changes on managed entities and commits them via flush() without requiring an explicit persist() call." ⏎ } | верно | Dirty checking сравнивает снимки свойств; persist нужен только новым/отсоединённым объектам. |
T14-L8 0.51 c | Doctrine | remove() executes the SQL DELETE immediately, without waiting for flush(). | «no» Пояснение: In Doctrine ORM, the remove() method only marks the object as to-be-deleted in the Unit of Work, and the actual SQL DELETE statement is only generated and sent when flush() is called.
Raw{"answer": "no", "explanation": "In Doctrine ORM, the remove() method only marks the object as to-be-deleted in the Unit of Work, and the actual SQL DELETE statement is only generated and sent when flush() is called."} | верно | remove() планирует удаление в Unit of Work; DELETE выполняется на flush() (docs — Deleting Objects). |
T15-L1 0.42 c | PostgreSQL | PostgreSQL uses MVCC, therefore readers block writers and writers block readers. | «no» Пояснение: PostgreSQL's MVCC design allows readers and writers to operate concurrently without blocking each other for most operations, as readers see snapshots of data and do not block writers.
Raw{"answer": "no", "explanation": "PostgreSQL's MVCC design allows readers and writers to operate concurrently without blocking each other for most operations, as readers see snapshots of data and do not block writers."} | верно | Наоборот: благодаря MVCC читатели не блокируют писателей и наоборот (снимки строк); docs PostgreSQL — Concurrency Control. |
T15-L2 0.27 c | PostgreSQL | Which SQL command shows a query's execution plan without executing the query? | «explain» Пояснение: The EXPLAIN keyword displays the execution plan for a query without actually running it.
Raw{"answer":"EXPLAIN","explanation":"The EXPLAIN keyword displays the execution plan for a query without actually running it."} | верно | EXPLAIN без ANALYZE только строит план; проверено на PostgreSQL 17.7. |
T15-L3 0.38 c | PostgreSQL | SERIAL and GENERATED ... AS IDENTITY are just two names for the same mechanism. | «yes» Пояснение: Both are keywords used to define an identity column that automatically generates a unique value on insertion.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "Both are keywords used to define an identity column that automatically generates a unique value on insertion." ⏎ } ⏎ ``` | неверно верный: «no» | SERIAL — нестандартный макрос (sequence + DEFAULT), IDENTITY — SQL-стандарт; различаются владением и правами. Оба есть в PG 17 (проверено). |
T15-L4 0.45 c | PostgreSQL | By default, a PostgreSQL UNIQUE constraint allows only one row with NULL in the column. | «yes» Пояснение: By default in PostgreSQL, a UNIQUE constraint treats multiple rows with NULL values in the same column as distinct, allowing multiple rows to contain NULL in that column.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "By default in PostgreSQL, a UNIQUE constraint treats multiple rows with NULL values in the same column as distinct, allowing multiple rows to contain NULL in that column." ⏎ } | неверно верный: «no» | Наоборот: NULLS DISTINCT по умолчанию — несколько NULL допустимы; NULLS NOT DISTINCT — опция с PG 15. Проверено на PG 17.7. |
T15-L5 0.35 c | PostgreSQL | Which PostgreSQL aggregate function concatenates strings with a separator? | «string_agg» Пояснение: In PostgreSQL, the string_agg() aggregate function concatenates strings with a specified separator.
Raw{ ⏎ "answer": "string_agg", ⏎ "explanation": "In PostgreSQL, the string_agg() aggregate function concatenates strings with a specified separator." ⏎ } | верно | string_agg(значение, разделитель); проверено на PostgreSQL 17.7. |
T15-L6 0.36 c | PostgreSQL | Plain VACUUM returns the space occupied by dead tuples to the operating system. | «no» Пояснение: Plain VACUUM reclaims space for internal reuse, but only VACUUM FULL releases space to the operating system.
Raw{"answer": "no", "explanation": "Plain VACUUM reclaims space for internal reuse, but only VACUUM FULL releases space to the operating system."} | верно | VACUUM помечает место для переиспользования внутри таблицы; ОС его возвращает только VACUUM FULL (с эксклюзивной блокировкой). |
T15-L7 0.41 c | PostgreSQL | Which keyword in a window function definition partitions rows into groups the function is computed over? | «partition by» Пояснение: The PARTITION BY clause in a SQL window function definition specifies the columns used to partition the row set into groups over which the window function is calculated.
Raw{"answer": "PARTITION BY", "explanation": "The PARTITION BY clause in a SQL window function definition specifies the columns used to partition the row set into groups over which the window function is calculated."} | верно | OVER (PARTITION BY ...); проверено на PostgreSQL 17.7. |
T15-L8 0.54 c | PostgreSQL | The READ COMMITTED isolation level protects against non-repeatable reads. | «yes» Пояснение: READ COMMITTED prevents non-repeatable reads by ensuring that each query sees data committed at the time of its execution, preventing the same row from being read with different values within the same transaction.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "READ COMMITTED prevents non-repeatable reads by ensuring that each query sees data committed at the time of its execution, preventing the same row from being read with different values within the same transaction." ⏎ } | неверно верный: «no» | READ COMMITTED допускает неповторяющееся чтение; защищает REPEATABLE READ. Проверено: SHOW transaction_isolation → read committed. |
T17-L1 0.38 c | PostgreSQL: transactions and indexes | By default, PostgreSQL wraps each single SQL statement in its own implicit transaction (autocommit). | «yes» Пояснение: PostgreSQL's default autocommit mode ensures that each individual SQL statement is automatically committed upon completion, creating an implicit transaction for each one.
Raw{"answer": "yes", "explanation": "PostgreSQL's default autocommit mode ensures that each individual SQL statement is automatically committed upon completion, creating an implicit transaction for each one."} | верно | Без BEGIN каждый оператор коммитится сам; docs PostgreSQL — Transactions. Проверено на PG 17. |
T17-L2 0.3 c | PostgreSQL: transactions and indexes | Which SQL command ends a transaction, committing all its changes? | «commit» Пояснение: The COMMIT SQL command ends a transaction and permanently saves all changes made during that transaction.
Raw{"answer": "COMMIT", "explanation": "The COMMIT SQL command ends a transaction and permanently saves all changes made during that transaction."} | верно | COMMIT (END — синоним). Проверено на PG 17. |
T17-L3 0.34 c | PostgreSQL: transactions and indexes | Indexes speed up more than SELECT: UPDATE and DELETE with a search on an indexed column benefit too. | «yes» Пояснение: Indexes speed up UPDATE and DELETE operations when they filter rows based on the indexed column.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Indexes speed up UPDATE and DELETE operations when they filter rows based on the indexed column." ⏎ } | верно | Поиск строк для изменения идёт по индексу; docs PostgreSQL — Indexes. |
T17-L4 0.4 c | PostgreSQL: transactions and indexes | To roll back part of the statements inside a transaction, PostgreSQL uses SAVEPOINT. | «yes» Пояснение: SAVEPOINT allows partial rollbacks within a transaction, while ROLLBACK reverts the entire transaction.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "SAVEPOINT allows partial rollbacks within a transaction, while ROLLBACK reverts the entire transaction." ⏎ } ⏎ ``` | верно | SAVEPOINT name; ROLLBACK TO name — частичный откат без отмены всей транзакции. Проверено на PG 17. |
T17-L5 0.35 c | PostgreSQL: transactions and indexes | EXPLAIN ANALYZE shows the query plan without executing the query. | «no» Пояснение: EXPLAIN ANALYZE executes the query to gather actual execution statistics before displaying the plan.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "EXPLAIN ANALYZE executes the query to gather actual execution statistics before displaying the plan." ⏎ } | верно | Наоборот: ANALYZE реально выполняет запрос (с побочными эффектами!) и показывает фактические времена узлов; план без выполнения — plain EXPLAIN. |
T17-L6 0.36 c | PostgreSQL: transactions and indexes | Which PostgreSQL extension adds vector types and indexes for embedding search? | «pgvector» Пояснение: pgvector is a PostgreSQL extension that provides vector data types and index methods for embedding search.
Raw{ ⏎ "answer": "pgvector", ⏎ "explanation": "pgvector is a PostgreSQL extension that provides vector data types and index methods for embedding search." ⏎ } | верно | CREATE EXTENSION vector (проект pgvector; в проекте образ pgvector/pgvector:pg17). |
T17-L7 0.36 c | PostgreSQL: transactions and indexes | A partial index (CREATE INDEX ... WHERE ...) is built only over rows satisfying the condition. | «yes» Пояснение: A partial index, or filtered index, indexes only the rows that meet the specified WHERE clause condition.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "A partial index, or filtered index, indexes only the rows that meet the specified WHERE clause condition." ⏎ } | верно | docs PostgreSQL — Partial Indexes; типичный кейс — индекс по «активным» записям. |
T17-L8 0.38 c | PostgreSQL: transactions and indexes | The SERIALIZABLE level in PostgreSQL is implemented by locking the rows a transaction reads. | «yes» Пояснение: In PostgreSQL, the SERIALIZABLE isolation level is implemented using a snapshot isolation mechanism combined with serialization via row-level locks and serializability checks.
Raw{"answer": "yes", "explanation": "In PostgreSQL, the SERIALIZABLE isolation level is implemented using a snapshot isolation mechanism combined with serialization via row-level locks and serializability checks."} | неверно верный: «no» | SSI (Serializable Snapshot Isolation): предикатные блокировки на снимках, не блокировки прочитанных строк; docs PostgreSQL. |
T19-L1 0.36 c | HTTP and REST API | HTTP status 201 means the request resulted in a new resource being created. | «yes» Пояснение: HTTP status code 201 (Created) indicates that the request has successfully resulted in the creation of a new resource.
Raw{"answer": "yes", "explanation": "HTTP status code 201 (Created) indicates that the request has successfully resulted in the creation of a new resource."} | верно | 201 Created; обычно на POST, часто с Location; RFC 9110. |
T19-L2 0.39 c | HTTP and REST API | Which HTTP status means a successful request with an empty response body (e.g. after DELETE)? | «204» Пояснение: The 204 No Content status code indicates a successful request with an empty response body, commonly used after DELETE or PUT operations.
Raw{"answer": 204, "explanation": "The 204 No Content status code indicates a successful request with an empty response body, commonly used after DELETE or PUT operations."} | верно | 204 No Content; RFC 9110. |
T19-L3 0.34 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» Пояснение: DELETE is defined as idempotent in HTTP semantics, meaning a repeated request has no additional effect beyond the first.
Raw{"answer": "yes", "explanation": "DELETE is defined as idempotent in HTTP semantics, meaning a repeated request has no additional effect beyond the first."} | верно | RFC 9110: DELETE идемпотентен (как PUT); идемпотентность ≠ безопасность — ресурс удаляется при первом вызове. |
T19-L4 0.44 c | HTTP and REST API | The Access-Control-Allow-Origin header is sent by the client so that the server agrees to accept requests from another origin. | «no» Пояснение: The Access-Control-Allow-Origin header is sent by the server to indicate that the resource can be shared with the specified origin, not by the client.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "The Access-Control-Allow-Origin header is sent by the server to indicate that the resource can be shared with the specified origin, not by the client." ⏎ } | верно | Наоборот: заголовок шлёт СЕРВЕР в ответе, разрешая браузеру cross-origin запрос (CORS); в проекте nelmio/cors-bundle. |
T19-L5 0.41 c | HTTP and REST API | Status 429 Too Many Requests is used when a client exceeds a rate limit. | «yes» Пояснение: HTTP 429 is specifically designed to indicate that the client has sent too many requests in a given amount of time.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "HTTP 429 is specifically designed to indicate that the client has sent too many requests in a given amount of time." ⏎ } | верно | 429 (+ Retry-After); RFC 6585. В проекте symfony/rate-limiter. |
T19-L6 0.39 c | HTTP and REST API | 5xx codes mean a client error, while 4xx means a server-side error. | «no» Пояснение: In HTTP, 4xx codes indicate client errors, whereas 5xx codes indicate server-side errors, so the statement has them reversed.
Raw{"answer": "no", "explanation": "In HTTP, 4xx codes indicate client errors, whereas 5xx codes indicate server-side errors, so the statement has them reversed."} | верно | Наоборот: 4xx — ошибка клиента (400, 404), 5xx — сервера (500, 503); классы статусов RFC 9110. |
T19-L7 0.38 c | HTTP and REST API | Which HTTP header indicates the MIME type of the request or response body? | «content-type» Пояснение: The Content-Type header specifies the media type, or MIME type, of the data contained in the body.
Raw{ ⏎ "answer": "Content-Type", ⏎ "explanation": "The Content-Type header specifies the media type, or MIME type, of the data contained in the body." ⏎ } | верно | Content-Type: application/json и т.п. |
T19-L8 0.49 c | HTTP and REST API | PATCH is not required to be idempotent per RFC 5789, unlike PUT. | «yes» Пояснение: RFC 5789 defines the PATCH method as not necessarily being idempotent, whereas RFC 9110 states that PUT is required to be idempotent.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "RFC 5789 defines the PATCH method as not necessarily being idempotent, whereas RFC 9110 states that PUT is required to be idempotent." ⏎ } | верно | RFC 5789 прямо оговаривает: PATCH не гарантированно идемпотентен; PUT идемпотентен. |
T20-L1 0.45 c | Security and OAuth | Checking a password by comparing its hash to the stored hash with a plain == is sufficient. | «no» Пояснение: A plain == comparison is vulnerable to timing attacks; a timing-safe function like hash_equals() is required for secure password hash comparisons.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "A plain == comparison is vulnerable to timing attacks; a timing-safe function like hash_equals() is required for secure password hash comparisons." ⏎ } | верно | Нужна постоянновременная проверка (password_verify) — timing-атаки; соль и алгоритм уже внутри хеша. |
T20-L2 0.41 c | Security and OAuth | A CSRF token is issued by the server (bound to the session) and verified server-side on unsafe requests (POST etc.). | «yes» Пояснение: CSRF tokens are generated by the server and typically tied to the user's session, then validated server-side during state-changing requests to prevent unauthorized cross-site actions.
Raw{"answer": "yes", "explanation": "CSRF tokens are generated by the server and typically tied to the user's session, then validated server-side during state-changing requests to prevent unauthorized cross-site actions."} | верно | symfony/security-csrf в проекте; защита от подделки межсайтовой формы. |
T20-L3 0.5 c | Security and OAuth | Which HTTP header enables the CSP (Content Security Policy) policy? | «content-security-policy» Пояснение: The Content-Security-Policy header is used by the HTTP protocol to define and enforce policies for how a web browser should load content and prevent the execution of scripts.
Raw{ ⏎ "answer": "Content-Security-Policy", ⏎ "explanation": "The Content-Security-Policy header is used by the HTTP protocol to define and enforce policies for how a web browser should load content and prevent the execution of scripts." ⏎ } | верно | Content-Security-Policy; белые списки источников скриптов/стилей против XSS. |
T20-L4 0.46 c | Security and OAuth | OAuth 2.0 is an authentication protocol: the access token tells you who the user is. | «no» Пояснение: OAuth 2.0 is an authorization protocol, and the access token grants permission for a specific scope rather than identifying the user (which requires an OpenID Connect token).
Raw{"answer": "no", "explanation": "OAuth 2.0 is an authorization protocol, and the access token grants permission for a specific scope rather than identifying the user (which requires an OpenID Connect token)."} | верно | OAuth 2.0 — авторизация/делегирование доступа; аутентификацию добавляет OpenID Connect. В проекте knpuniversity/oauth2-client-bundle (yandex/github/google). |
T20-L5 0.35 c | Security and OAuth | XSS is prevented by validating input on the server before writing it to the database. | «no» Пояснение: Server-side validation does not prevent XSS, which is mitigated by output encoding or escaping when data is rendered in the browser.
Raw{"answer": "false", "explanation": "Server-side validation does not prevent XSS, which is mitigated by output encoding or escaping when data is rendered in the browser."} | верно | XSS лечится контекстным экранированием НА ВЫВОДЕ (Twig autoescape, CSP); валидация ввода не покрывает все контексты вывода. |
T20-L6 0.36 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 code is the parameter that the authorization server returns to the redirect_uri and the client later exchanges for an access token.
Raw{"answer": "code", "explanation": "The authorization code is the parameter that the authorization server returns to the redirect_uri and the client later exchanges for an access token."} | верно | Параметр code; обмен на токен POST-ом на /token с client_secret. |
T20-L7 0.47 c | Security and OAuth | A refresh token lives longer than an access token and allows obtaining a new access token without the user logging in again. | «yes» Пояснение: In OAuth 2.0 and similar token systems, refresh tokens have longer expiration times and are specifically used to request new access tokens without requiring the user to re-authenticate.
Raw{"answer": "yes", "explanation": "In OAuth 2.0 and similar token systems, refresh tokens have longer expiration times and are specifically used to request new access tokens without requiring the user to re-authenticate."} | верно | Стандартная схема OAuth/OIDC: короткий access + длинный refresh. |
T20-L8 0.48 c | Security and OAuth | A password salt must be kept secret: without it the hash cannot be verified. | «no» Пояснение: Salts are typically stored in plaintext alongside the hash in the database because they only need to be unique to prevent rainbow tables, not secret, whereas the password hash itself provides the secrecy.
Raw{ ⏎ "answer": "false", ⏎ "explanation": "Salts are typically stored in plaintext alongside the hash in the database because they only need to be unique to prevent rainbow tables, not secret, whereas the password hash itself provides the secrecy." ⏎ } | верно | Соль хранится открыто (password_hash включает её в строку хеша); секретность соли не нужна. |
T18-L1 0.31 c | Testing: PHPUnit | PHPUnit runs test methods of any class — extending TestCase is not required. | «no» Пояснение: PHPUnit requires test classes to extend TestCase to access its testing features and properly execute the test methods.
Raw{"answer": "false", "explanation": "PHPUnit requires test classes to extend TestCase to access its testing features and properly execute the test methods."} | верно | Тестом считается метод класса, наследующего TestCase (PHPUnit 10). |
T18-L2 0.35 c | Testing: PHPUnit | In PHPUnit, setUp() runs once before all tests of the class. | «no» Пояснение: setUp() runs once before each test method in the class, not once before all tests.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "setUp() runs once before each test method in the class, not once before all tests." ⏎ } | верно | setUp() — перед КАЖДЫМ тестом; один раз на класс — setUpBeforeClass(). Проверено живым счётчиком на PHPUnit 10.5. |
T18-L3 0.36 c | Testing: PHPUnit | A data provider lets a test run with exactly one set of arguments. | «no» Пояснение: Data providers in PHP testing frameworks like PHPUnit allow a test method to run multiple times with different sets of arguments, not just one.
Raw{"answer": "no", "explanation": "Data providers in PHP testing frameworks like PHPUnit allow a test method to run multiple times with different sets of arguments, not just one."} | верно | Наоборот: наборов может быть сколько угодно — тест выполняется по разу на каждый. Проверено на PHPUnit 10.5 (#[DataProvider]). |
T18-L4 0.31 c | Testing: PHPUnit | Which PHPUnit method declares an expectation that an exception of a given class is thrown? | «expectexception» Пояснение: expectException is the PHPUnit method used to declare that a specific exception class is expected to be thrown.
Raw{"answer": "expectException", "explanation": "expectException is the PHPUnit method used to declare that a specific exception class is expected to be thrown."} | верно | $this->expectException(\LogicException::class); проверено на PHPUnit 10.5. |
T18-L5 0.4 c | Testing: PHPUnit | In PHPUnit, a stub verifies which methods were called on it, while a mock only returns data. | «no» Пояснение: The definition is reversed: a stub returns canned data without verifying calls, while a mock records interactions to verify they were made.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "The definition is reversed: a stub returns canned data without verifying calls, while a mock records interactions to verify they were made." ⏎ } | верно | Наоборот: стаб подставляет данные, мок проверяет взаимодействия (createStub/createMock); docs PHPUnit — Test Doubles. |
T18-L6 0.31 c | Testing: PHPUnit | In PHPUnit 10+, the recommended way to pass data to a test is the #[DataProvider] attribute (the @dataProvider annotation is deprecated). | «yes» Пояснение: In PHPUnit 10, the #[DataProvider] attribute is the modern replacement for the legacy @dataProvider annotation.
Raw{"answer":"yes","explanation":"In PHPUnit 10, the #[DataProvider] attribute is the modern replacement for the legacy @dataProvider annotation."} | верно | Аннотация ещё парсится в PHPUnit 10/11 (AnnotationParser в 10.5.66), удаление — в 12; атрибут — стандарт. |
T18-L7 0.33 c | Testing: PHPUnit | PHPUnit does not allow one test to depend on the result of another. | «no» Пояснение: PHPUnit allows tests to be made dependent on other tests using the @depends annotation, so this statement is false.
Raw{"answer": "false", "explanation": "PHPUnit allows tests to be made dependent on other tests using the @depends annotation, so this statement is false."} | верно | Зависимости есть: #[Depends] — зависимый тест не запустится, еслиProducer упал. |
T18-L8 0.33 c | Testing: PHPUnit | Which PHPUnit command-line option makes tests run in random order? | «--random-order» Пояснение: The --random-order option shuffles the order in which tests are executed.
Raw{ ⏎ "answer": "--random-order", ⏎ "explanation": "The --random-order option shuffles the order in which tests are executed." ⏎ } | неверно верный: «--order-by=random» | --order-by=random (PHPUnit 9+); опция есть в --help PHPUnit 10.5 (проектная). |
T01-L9 2.45 c | Syntax and operators | What does this code output?
```php
echo intdiv(7, 2) . intdiv(-7, 2);
``` | «3-4» Пояснение: intdiv(7, 2) returns 3, and intdiv(-7, 2) returns -4 because intdiv performs integer division truncating toward negative infinity, and the results are concatenated with a dot.
Raw{ ⏎ "answer": "3-4", ⏎ "explanation": "intdiv(7, 2) returns 3, and intdiv(-7, 2) returns -4 because intdiv performs integer division truncating toward negative infinity, and the results are concatenated with a dot." ⏎ } | неверно верный: «3-3» | intdiv truncates toward zero: intdiv(-7, 2) = -3, not -4. |
T01-L10 0.48 c | Syntax and operators | What does this code output?
```php
echo -3 ** 2;
``` | «-9» Пояснение: The exponentiation operator has higher precedence than the unary minus, so it evaluates as -(3**2) = -9.
Raw```json ⏎ { ⏎ "answer": -9, ⏎ "explanation": "The exponentiation operator has higher precedence than the unary minus, so it evaluates as -(3**2) = -9." ⏎ } ⏎ ``` | верно | ** is right-associative and binds tighter than unary minus: -(3²). |
T02-L9 0.43 c | Types and comparisons | What does this code output?
```php
echo '1e1' == '10' ? 'true' : 'false';
``` | «true» Пояснение: In PHP, the loose equality operator == converts both strings to numbers before comparing, so '1e1' equals 10 and the ternary operator outputs 'true'.
Raw{"answer":"true","explanation":"In PHP, the loose equality operator == converts both strings to numbers before comparing, so '1e1' equals 10 and the ternary operator outputs 'true'."} | верно | Both strings are numeric — compared as numbers: 10 == 10. |
T02-L10 0.34 c | Types and comparisons | What does this code output?
```php
switch ('a') {
case 0: echo 'zero'; break;
default: echo 'other';
}
``` | «other» Пояснение: The switch compares 'a' with 0, which fails, so the default case executes and outputs 'other'.
Raw{"answer":"other","explanation":"The switch compares 'a' with 0, which fails, so the default case executes and outputs 'other'."} | верно | PHP 8: 'a' == 0 → false (used to be true) — default fires. |
T03-L9 0.41 c | Strings | What does this code output?
```php
echo strtr('abc', ['a' => '1', 'ab' => '2']);
``` | «1bc» Пояснение: strtr() replaces the longest matching keys first, so 'a' is replaced by '1' in the string 'abc' resulting in '1bc'.
Raw{"answer":"1bc","explanation":"strtr() replaces the longest matching keys first, so 'a' is replaced by '1' in the string 'abc' resulting in '1bc'."} | неверно верный: «2c» | strtr with an array prefers the longest matching key. |
T03-L10 0.43 c | Strings | What does this code output?
```php
echo '[' . substr('hello', -10) . ']';
``` | «[hello]» Пояснение: substr('hello', -10) starts 10 characters before the end, which is before the string begins, so it returns the entire string 'hello'.
Raw{"answer":"[hello]","explanation":"substr('hello', -10) starts 10 characters before the end, which is before the string begins, so it returns the entire string 'hello'."} | верно | A negative start beyond the string is clamped to the beginning. |
T04-L9 1.46 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» Пояснение: The + operator merges $a first, so 'k' becomes 1, then adds 'n' (2) from $a and 'm' (3) from $b, resulting in keys k, n, m, but since the question asks for the output, we need to list the keys. The array keys are k, n, m, but in the order they appear in the merged array. However, the correct answer is 'k,n,m' but let me recheck. Actually, the + operator keeps the keys from the first array first, then adds new keys from the second. So the keys are k (from a), n (from a), m (from b) in that order. The answer is 'k,n,m'.
Raw{ ⏎ "answer": "k,n", ⏎ "explanation": "The + operator merges $a first, so 'k' becomes 1, then adds 'n' (2) from $a and 'm' (3) from $b, resulting in keys k, n, m, but since the question asks for the output, we need to list the keys. The array keys are k, n, m, but in the order they appear in the merged array. However, the correct answer is 'k,n,m' but let me recheck. Actually, the + operator keeps the keys from the first array first, then adds new keys from the second. So the keys are k (from a), n (from a), m (from b) in that order. The answer is 'k,n,m'." ⏎ } | неверно верный: «k,n,m» | The + operator: on duplicate string keys the left array wins. |
T04-L10 0.72 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));
``` | «xyz» Пояснение: The array is sorted by the third element using usort, which results in the order [1, 'x', 2], [2, 'y', 1], [3, 'z', 2] (stable sort for equal keys), and array_column then extracts 'xyz' from the second element.
Raw{"answer": "xyz", "explanation": "The array is sorted by the third element using usort, which results in the order [1, 'x', 2], [2, 'y', 1], [3, 'z', 2] (stable sort for equal keys), and array_column then extracts 'xyz' from the second element."} | неверно верный: «yxz» | Sorts are stable since 8.0: x and z keep their order on a tie. |
T05-L10 0.64 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» Пояснение: PHP 8.0+ supports named arguments, so f(...['b' => 1, 'a' => 5]) calls f(a: 5, b: 1), and 5 - 1 is 4.
Raw{ ⏎ "answer": "4", ⏎ "explanation": "PHP 8.0+ supports named arguments, so f(...['b' => 1, 'a' => 5]) calls f(a: 5, b: 1), and 5 - 1 is 4." ⏎ } | верно | String keys of a spread array become named arguments. |
T05-L9 0.52 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 closure $f captures $p by value at creation time, so even after $p is set to null, the closure still holds the original P instance and its private property $v=3.
Raw{"answer": "3", "explanation": "The closure $f captures $p by value at creation time, so even after $p is set to null, the closure still holds the original P instance and its private property $v=3."} | верно | First-class callable syntax binds $this at creation time. |
T06-L9 0.4 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 name, which is B in this case.
Raw{ ⏎ "answer": "B", ⏎ "explanation": "static::class resolves to the late static binding class name, which is B in this case." ⏎ } | верно | Late static binding: static::class is the receiver's class. |
T06-L10 0.54 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;
``` | «yes» Пояснение: PHP 8.5 is not a released stable version; the latest major stable PHP is 8.3, so this code cannot be executed on PHP 8.5 and is not a valid answerable runtime scenario.
Raw{"answer":"yes","explanation":"PHP 8.5 is not a released stable version; the latest major stable PHP is 8.3, so this code cannot be executed on PHP 8.5 and is not a valid answerable runtime scenario."} | неверно верный: «10» | Inside the set hook, $this->x writes the backing store (no recursion): 5*2. |
T07-L9 0.47 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 clause makes TB::f override TA::f for f, while TA::f is aliased as g.
Raw{ ⏎ "answer": "BA", ⏎ "explanation": "The insteadof clause makes TB::f override TA::f for f, while TA::f is aliased as g." ⏎ } | верно | insteadof picks the implementation; as keeps the other under an alias. |
T07-L10 0.41 c | Interfaces, traits, enum | What does this code output?
```php
trait Counter
{
public static int $n = 0;
}
class CX { use Counter; }
class CY { use Counter; }
CX::$n = 1;
echo CY::$n;
``` | «1» Пояснение: Static properties declared in a trait are shared by all classes that use it, so CX and CY access the same $n.
Raw{"answer": "1", "explanation": "Static properties declared in a trait are shared by all classes that use it, so CX and CY access the same $n."} | неверно верный: «0» | A trait's static property is copied into each consuming class. |
T08-L10 0.57 c | Exceptions and errors | What does this code output?
```php
function f(): int
{
try { return 1; } finally { return 2; }
}
echo f();
``` | «php fatal error: uncaught error: function f() declared to return int, but return statement in finally block ignored» Пояснение: PHP throws an Error when a 'return' statement is used in a 'finally' block.
Raw{ ⏎ "answer": "PHP Fatal error: Uncaught Error: Function f() declared to return int, but return statement in finally block ignored", ⏎ "explanation": "PHP throws an Error when a 'return' statement is used in a 'finally' block." ⏎ } | неверно верный: «2» | A return in finally overrides the return from try. |
T08-L9 0.45 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 outer finally block throws a LogicException that overrides the RuntimeException from the inner try block, and the outer catch catches the LogicException and prints its message.
Raw{"answer": "second", "explanation": "The outer finally block throws a LogicException that overrides the RuntimeException from the inner try block, and the outer catch catches the LogicException and prints its message."} | верно | An exception from finally replaces the in-flight one — the last thrown is caught. |
T09-L9 0.54 c | Namespaces and autoloading | What does this code output?
```php
namespace N;
use App\Foo as Baz;
echo Baz::class . '|' . \Baz::class;
``` | «app\foo|baz» Пояснение: The alias Baz resolves to App\Foo, while the fully-qualified name \Baz refers to the global Baz class, so concatenation yields 'App\Foo|Baz'.
Raw{"answer": "App\\Foo|Baz", "explanation": "The alias Baz resolves to App\\Foo, while the fully-qualified name \\Baz refers to the global Baz class, so concatenation yields 'App\\Foo|Baz'."} | верно | The use alias applies to unqualified names; a leading \ escapes to the global scope. |
T09-L10 0.57 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');
``` | «no yes» Пояснение: class_exists($c) fails because the class Foo is only defined in namespace Ns, but class_exists(__NAMESPACE__ . '\' . $c) succeeds because it resolves to Ns\Foo.
Raw```json ⏎ {"answer": "no yes", "explanation": "class_exists($c) fails because the class Foo is only defined in namespace Ns, but class_exists(__NAMESPACE__ . '\\' . $c) succeeds because it resolves to Ns\\Foo."} ⏎ ``` | неверно верный: «noyes» | Dynamic names are not resolved against the namespace — 'Foo' is the global class. |
T10-L9 0.53 c | References and scope | What does this code output?
```php
$a = [1, 2, 3];
foreach ($a as &$v) {}
$v = 99;
echo implode(',', $a);
``` | «1,2,99» Пояснение: The foreach loop with & creates references to each array element, and $v remains a reference to the last element after the loop, so changing $v to 99 changes $a[2].
Raw{"answer":"1,2,99","explanation":"The foreach loop with & creates references to each array element, and $v remains a reference to the last element after the loop, so changing $v to 99 changes $a[2]."} | верно | After a by-ref foreach, $v remains a reference to the last element. |
T10-L10 0.55 c | References and scope | What does this code output?
```php
class A
{
public function inc(): int
{
static $n = 0;
return ++$n;
}
}
class B extends A {}
$a = new A;
$b = new B;
$a->inc();
$b->inc();
echo $a->inc();
``` | «3» Пояснение: The static property is scoped to the class A, and since B does not override it or declare its own, it is shared; inc() is called three times total, so the third call returns 3.
Raw{"answer": "3", "explanation": "The static property is scoped to the class A, and since B does not override it or declare its own, it is shared; inc() is called three times total, so the third call returns 3."} | верно | A method's static variable belongs to the parent's method — subclasses share it. |
T11-L9 0.54 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» Пояснение: The send(10) causes $x to be 10, and the generator returns $x + 1, so getReturn() gives 11.
Raw{ ⏎ "answer": 11, ⏎ "explanation": "The send(10) causes $x to be 10, and the generator returns $x + 1, so getReturn() gives 11." ⏎ } | верно | send() resumes the generator: $x = 10, return 10+1. |
T11-L10 0.45 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()));
``` | «12ok» Пояснение: yield from passes values (1,2) directly into outer's iterator, and the returned string 'ok' is yielded as the final value.
Raw{"answer": "12ok", "explanation": "yield from passes values (1,2) directly into outer's iterator, and the returned string 'ok' is yielded as the final value."} | неверно верный: «ok,2» | yield from does not advance the outer auto-key: yield $r gets key 0 and overwrites the 1 — 'ok' comes out first. |
T12-L9 0.4 c | Configuration and security | What does this code output?
```php
$hash = password_hash('x', PASSWORD_BCRYPT, ['cost' => 4]);
echo password_needs_rehash($hash, PASSWORD_BCRYPT, ['cost' => 4]) ? 'yes' : 'no';
echo password_needs_rehash($hash, PASSWORD_BCRYPT, ['cost' => 5]) ? 'yes' : 'no';
``` | «noyes» Пояснение: The first call returns false since cost 4 matches, while the second returns true because cost 5 is higher.
Raw{"answer": "noyes", "explanation": "The first call returns false since cost 4 matches, while the second returns true because cost 5 is higher."} | верно | password_needs_rehash compares the hash's options with the target: cost 4 = 4 → 'no', cost 5 ≠ 4 → 'yes'. |
T12-L10 0.65 c | Configuration and security | What does this code output on PHP 8.5?
```php
echo (E_ALL & 2048) === 0 ? 'strict-out' : 'strict-in';
``` | «strict-out» Пояснение: In PHP 8.5, the new error_reporting constant E_STRICT is defined as 0x0800, so E_ALL & 2048 is 0, making the expression evaluate to 'strict-out'.
Raw{ ⏎ "answer": "strict-out", ⏎ "explanation": "In PHP 8.5, the new error_reporting constant E_STRICT is defined as 0x0800, so E_ALL & 2048 is 0, making the expression evaluate to '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 0.52 c | Symfony | What does this code output?
```php
use Symfony\Component\HttpFoundation\Request;
$r = Request::create('/demo', 'GET', [], [], [], ['HTTP_X_TOKEN' => 'abc']);
echo $r->headers->get('X-Token') === 'abc' ? 'mapped' : 'missing';
``` | «mapped» Пояснение: Symfony's Request::create converts the HTTP header name 'HTTP_X_TOKEN' into 'X-Token' when accessed via $r->headers->get('X-Token').
Raw```json ⏎ {"answer": "mapped", "explanation": "Symfony's Request::create converts the HTTP header name 'HTTP_X_TOKEN' into 'X-Token' when accessed via $r->headers->get('X-Token')."} ⏎ ``` | верно | 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 0.57 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;
``` | «cab» Пояснение: Symfony's EventDispatcher calls listeners in order of priority (highest first), so the listeners with priorities 10, default, and 5 execute as B, A, C.
Raw{ ⏎ "answer": "CAB", ⏎ "explanation": "Symfony's EventDispatcher calls listeners in order of priority (highest first), so the listeners with priorities 10, default, and 5 execute as B, A, C." ⏎ } | неверно верный: «bca» | Listeners run by descending priority: 10 (B), 5 (C), 0 (A). |
T14-L10 0.49 c | Doctrine | Given: Doctrine ORM 3, an EntityManager on in-memory SQLite, entity User with an auto-increment primary key. The users table is empty. What does this code output?
```php
$u = new User(name: 'A');
$em->persist($u);
$em->flush();
$a = $em->find(User::class, $u->getId());
$b = $em->find(User::class, $u->getId());
echo spl_object_id($a) === spl_object_id($b) ? 'same' : 'diff';
``` | «same» Пояснение: Doctrine ORM caches loaded entities within the EntityManager's identity map, so two find() calls with the same id return the same instance.
Raw{ ⏎ "answer": "same", ⏎ "explanation": "Doctrine ORM caches loaded entities within the EntityManager's identity map, so two find() calls with the same id return the same instance." ⏎ } | верно | Identity map: a second find for the same id returns the same instance. |
T14-L9 0.44 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» Пояснение: persist() and remove() on the same detached object cancel each other, so no rows are inserted during flush.
Raw{ ⏎ "answer": 0, ⏎ "explanation": "persist() and remove() on the same detached object cancel each other, so no rows are inserted during flush." ⏎ } | верно | The unit of work schedules INSERT at flush: remove after persist cancels it. |
T15-L10 0.47 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» Пояснение: The count(x) function only counts non-NULL values in column x, so it returns 1.
Raw```json ⏎ { ⏎ "answer": "1", ⏎ "explanation": "The count(x) function only counts non-NULL values in column x, so it returns 1." ⏎ } ⏎ ``` | верно | count(column) skips NULLs; count(*) would return 2. |
T15-L9 0.75 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,20,30» Пояснение: The window function sum(x) OVER (ORDER BY id) computes running totals of x in id order: id 1 -> 10, id 2 -> 30, id 3 -> 60, and string_agg concatenates the cast values as "10,20,30".
Raw{"answer": "10,20,30", "explanation": "The window function sum(x) OVER (ORDER BY id) computes running totals of x in id order: id 1 -> 10, id 2 -> 30, id 3 -> 60, and string_agg concatenates the cast values as \"10,20,30\"."} | неверно верный: «10,30,60» | With ORDER BY the default window frame is running (start to current row). |
T16-L9 0.58 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 MessageBus executes middleware in the order provided, and each Trace middleware echoes its tag before passing the envelope to the next one, resulting in 'M1' followed by 'M2'.
Raw{"answer": "M1M2", "explanation": "The MessageBus executes middleware in the order provided, and each Trace middleware echoes its tag before passing the envelope to the next one, resulting in 'M1' followed by 'M2'."} | верно | The first-added middleware runs first (outermost). |
T16-L10 0.62 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» Пояснение: Symfony Messenger dispatches messages to all handlers listed for a given message class, so both $d1 (+1) and $d2 (+10) execute, resulting in $n being 11.
Raw{ ⏎ "answer": "11", ⏎ "explanation": "Symfony Messenger dispatches messages to all handlers listed for a given message class, so both $d1 (+1) and $d2 (+10) execute, resulting in $n being 11." ⏎ } | верно | All registered handlers of the message run: 1 + 10 = 11. |
T17-L9 0.39 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 ON CONFLICT DO NOTHING clause prevents the duplicate insertion, leaving only one row in the temporary table.
Raw{"answer": 1, "explanation": "The ON CONFLICT DO NOTHING clause prevents the duplicate insertion, leaving only one row in the temporary table."} | верно | ON CONFLICT DO NOTHING skips the duplicate: one insert. |
T17-L10 0.47 c | PostgreSQL: transactions and indexes | What does this sequence of psql commands output?
```sql
BEGIN;
CREATE TEMP TABLE t (a int, UNIQUE (a) DEFERRABLE INITIALLY DEFERRED);
INSERT INTO t VALUES (1);
INSERT INTO t VALUES (1);
SELECT count(*) FROM t;
``` | «2» Пояснение: Because the UNIQUE constraint is DEFERRABLE and INITIALLY DEFERRED, duplicate inserts are allowed within the transaction and only checked at COMMIT.
Raw```json ⏎ {"answer": "2", "explanation": "Because the UNIQUE constraint is DEFERRABLE and INITIALLY DEFERRED, duplicate inserts are allowed within the transaction and only checked at COMMIT."} ⏎ ``` | верно | DEFERRED postpones the uniqueness check to COMMIT — count sees 2 rows. |
T18-L9 0.52 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» Пояснение: PHPUnit's --filter matches methods whose name contains 'test_sum', so it selects both data-provided test_sum methods (3 variants each, total 6), while excluding test_other.
Raw{"answer": 6, "explanation": "PHPUnit's --filter matches methods whose name contains 'test_sum', so it selects both data-provided test_sum methods (3 variants each, total 6), while excluding test_other."} | верно | --filter is a substring match: test_sum also matches test_sum_abs (3+3 datasets). |
T18-L10 0.44 c | Testing: PHPUnit | How many tests will this command run, and how many of them will fail? Answer with two comma-separated numbers (ran, failed).
```php
use PHPUnit\Framework\TestCase;
use PHPUnit\Framework\Attributes\DataProvider;
final class Calc2Test extends TestCase
{
public function prov(): array
{
return [[1], [-1]];
}
#[DataProvider('prov')]
public function test_x(int $x): void
{
$this->assertTrue($x > 0);
}
}
```
Command: `phpunit Calc2Test.php` (PHPUnit 10.5) | «2, 1» Пояснение: The DataProvider provides two datasets, resulting in two tests being run, but the assertion fails for the negative number dataset.
Raw{"answer": "2, 1", "explanation": "The DataProvider provides two datasets, resulting in two tests being run, but the assertion fails for the negative number dataset."} | верно | A non-static provider is just a deprecation in PHPUnit 10: both datasets run and the [-1] dataset fails the assert — 2 ran, 1 failure. |
T19-L9 0.37 c | HTTP and REST API | Which HTTP method does this command send?
```bash
curl -s -d 'a=1' http://demo.local/api
``` | «post» Пояснение: The -d flag in curl sets the HTTP method to POST when no -X flag is explicitly specified.
Raw{"answer": "POST", "explanation": "The -d flag in curl sets the HTTP method to POST when no -X flag is explicitly specified."} | верно | -d/-F switches curl to POST by default. |
T19-L10 0.42 c | HTTP and REST API | Which HTTP method does this command send?
```bash
curl -s -G -d 'a=1' http://demo.local/api
``` | «get» Пояснение: The -G flag tells curl to put the -d data in the URL query string instead of the body, which changes the default POST to a GET request.
Raw{"answer": "GET", "explanation": "The -G flag tells curl to put the -d data in the URL query string instead of the body, which changes the default POST to a GET request."} | верно | -G turns -d data into the query string; the method stays GET. |
T20-L9 0.57 c | Security and OAuth | A client hits the token endpoint (RFC 6749) with a non-existent client_id. What value of the error field does the endpoint return? | «invalid_client» Пояснение: Per RFC 6749 Section 4.1.2.1, if a client is not recognized or does not have a registered client_id, the token endpoint must respond with the error code "invalid_client".
Raw{"answer": "invalid_client", "explanation": "Per RFC 6749 Section 4.1.2.1, if a client is not recognized or does not have a registered client_id, the token endpoint must respond with the error code \"invalid_client\"."} | верно | Unknown client → invalid_client (RFC 6749 §5.2). |
T20-L10 0.43 c | Security and OAuth | OAuth 2.0: the client started the flow with response_type=token. In which part of the redirect_uri does the authorization server pass the access_token? | «fragment» Пояснение: In the Implicit Grant flow (response_type=token), the authorization server returns the access token and other parameters in the fragment component of the redirect URI.
Raw{"answer": "Fragment", "explanation": "In the Implicit Grant flow (response_type=token), the authorization server returns the access token and other parameters in the fragment component of the redirect URI."} | верно | The implicit flow passes the token in the URL fragment (#) — it never reaches the server. |
T21-L9 2.49 c | Twig | What does this Twig template output?
```twig
{{ false|default(2) * 3 }}
``` | «0» Пояснение: In Twig the default filter is only applied when its argument is falsey, and since false is considered falsey in PHP, false|default(2) evaluates to 2, making 2*3 equal 6? Wait correction: Twig's default filter checks if the value is falsey; false is falsey so it returns 2, so 2*3=6, but wait: Actually in Twig, the default filter returns the default only if the variable is not defined, or in some versions if it is falsey, but false is falsey, so false|default(2) returns 2, so 2*3=6. I need to be precise. The Twig default filter docs say it replaces a value by another if it is falsey. False is falsey. So false|default(2) -> 2. Then 2 * 3 -> 6. So answer should be 6. Let me double-check: In PHP, false * 3 is 0, but Twig's default filter would replace false with 2 before multiplication. So 2*3 = 6. Yes, answer is 6. But I must ensure no off-by: The expression is {{ false|default(2) * 3 }}. Twig precedence: filter applies to false first, giving 2, then multiplied by 3, giving 6. So result is 6.
Raw{"answer": 0, "explanation": "In Twig the default filter is only applied when its argument is falsey, and since false is considered falsey in PHP, false|default(2) evaluates to 2, making 2*3 equal 6? Wait correction: Twig's default filter checks if the value is falsey; false is falsey so it returns 2, so 2*3=6, but wait: Actually in Twig, the default filter returns the default only if the variable is not defined, or in some versions if it is falsey, but false is falsey, so false|default(2) returns 2, so 2*3=6. I need to be precise. The Twig default filter docs say it replaces a value by another if it is falsey. False is falsey. So false|default(2) -> 2. Then 2 * 3 -> 6. So answer should be 6. Let me double-check: In PHP, false * 3 is 0, but Twig's default filter would replace false with 2 before multiplication. So 2*3 = 6. Yes, answer is 6. But I must ensure no off-by: The expression is {{ false|default(2) * 3 }}. Twig precedence: filter applies to false first, giving 2, then multiplied by 3, giving 6. So result is 6."} | неверно верный: «6» | default replaces exactly false/null/''/[] — false becomes 2, 2*3 = 6; the naive 'default is for undefined only' yields 0. |
T21-L10 0.43 c | Twig | What exception class does render() of this template throw?
```twig
{{ 'a' ~ 1 + 2 }}
``` | «twig\twigexception» Пояснение: The template engine throws a TwigException when encountering the invalid syntax of mixing a string literal with numbers using arithmetic operators.
Raw{"answer": "Twig\\TwigException", "explanation": "The template engine throws a TwigException when encountering the invalid syntax of mixing a string literal with numbers using arithmetic operators."} | неверно верный: «runtimeerror» | In Twig ~ binds tighter than +: ('a' ~ 1) + 2 → string + int → a render error (RuntimeError). |
T22-L9 0.4 c | Symfony: Security and forms | What does this code output?
```php
use Symfony\Component\Validator\Validation;
use Symfony\Component\Validator\Constraints as Assert;
$v = Validation::createValidator();
echo count($v->validate([''], [new Assert\NotBlank()]));
``` | «1» Пояснение: Validating an empty string against a NotBlank constraint produces one violation, so the count is 1.
Raw{ ⏎ "answer": 1, ⏎ "explanation": "Validating an empty string against a NotBlank constraint produces one violation, so the count is 1." ⏎ } | неверно верный: «0» | NotBlank treats null, '', [] as blank — the array [''] is not blank. |
T22-L10 0.44 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» Пояснение: Symfony form's isValid() returns false by default for a form that has not been bound with data and validated.
Raw{ ⏎ "answer": "invalid", ⏎ "explanation": "Symfony form's isValid() returns false by default for a form that has not been bound with data and validated." ⏎ } | неверно верный: «symfony\component\form\exception\logicexception» | isValid() on a non-submitted form throws LogicException, it does not return false. |
T23-L9 0.52 c | Symfony: configuration and services | What does this code output?
```php
use Symfony\Component\DependencyInjection\ContainerBuilder;
$c = new ContainerBuilder();
$c->register('a', stdClass::class)->setPublic(true);
$c->compile();
echo spl_object_id($c->get('a')) === spl_object_id($c->get('a')) ? 'same' : 'diff';
``` | «same» Пояснение: The ContainerBuilder caches the resolved service instance, so both calls to $c->get('a') return the exact same object, making the spl_object_id comparison true.
Raw```json ⏎ {"answer": "same", "explanation": "The ContainerBuilder caches the resolved service instance, so both calls to $c->get('a') return the exact same object, making the spl_object_id comparison true."} ⏎ ``` | верно | Container services are shared: two get() calls yield one instance. |
T23-L10 0.45 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» Пояснение: The ContainerBuilder resolves parameter placeholders during compile, replacing %name% and then %greeting% with their values.
Raw{ ⏎ "answer": "hi Bob", ⏎ "explanation": "The ContainerBuilder resolves parameter placeholders during compile, replacing %name% and then %greeting% with their values." ⏎ } | неверно верный: «hi bob!» | compile() resolves %-references transitively: %greeting% → 'hi %name%' → 'hi Bob!', the answer assembles over two hops. |
T24-L9 0.52 c | Bootstrap | What is the max-width of .container in Bootstrap 5.3 at a 992px viewport? | «992px» Пояснение: In Bootstrap 5.3, the .container class uses the --bs-container-max-width: 992px custom property for viewports at least 992px wide.
Raw{"answer": "992px", "explanation": "In Bootstrap 5.3, the .container class uses the --bs-container-max-width: 992px custom property for viewports at least 992px wide."} | неверно верный: «960» | 5.x container widths: 540/720/960/1140/1320 (sm–xxl); 992 → 960px. |
T24-L10 0.48 c | Bootstrap | Which utility sets the text color in Bootstrap 5.3 for `<p class="text-danger text-primary">…</p>`? Answer with the winning class name. | «text-primary» Пояснение: In HTML class lists, the last matching utility class for the same property generally overrides the previous one, so text-primary wins over text-danger for the text color.
Raw{"answer": "text-primary", "explanation": "In HTML class lists, the last matching utility class for the same property generally overrides the previous one, so text-primary wins over text-danger for the text color."} | неверно верный: «text-danger» | Specificity ties — the later rule wins: text-danger is declared after text-primary. |
T25-L9 0.39 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 Application layer using Domain (OrderService) and Infrastructure using Domain (Db) are the two dependency violations.
Raw{"answer": 2, "explanation": "The Application layer using Domain (OrderService) and Infrastructure using Domain (Db) are the two dependency violations."} | верно | Domain may depend only on Domain: PlaceOrder (Application) + Db (Infrastructure) = 2. |
T25-L10 0.9 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,
) {}
}
``` | «2» Пояснение: Domain is only allowed to depend on Domain, but this class references two classes from the Infrastructure layer (Db and Logger) and one from the Application layer (PlaceOrder), resulting in three total non-allowed dependencies; however, the question likely expects only violations of the 'Infrastructure -> Domain' rule if misinterpreted, but based on the rules Domain -> Domain only, all external references violate, so it should be 3.
Raw{ ⏎ "answer": 2, ⏎ "explanation": "Domain is only allowed to depend on Domain, but this class references two classes from the Infrastructure layer (Db and Logger) and one from the Application layer (PlaceOrder), resulting in three total non-allowed dependencies; however, the question likely expects only violations of the 'Infrastructure -> Domain' rule if misinterpreted, but based on the rules Domain -> Domain only, all external references violate, so it should be 3." ⏎ } | неверно верный: «3» | The inline FQCN \App\Infrastructure\Logger counts too: Application + Db + Logger = 3. |
T26-L10 0.61 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 readonly constructor property prevents mutation, and add() creates a new Money instance with the sum, so $a->amount stays 10 and $c->amount is 15.
Raw{ ⏎ "answer": "10,15", ⏎ "explanation": "The readonly constructor property prevents mutation, and add() creates a new Money instance with the sum, 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 0.44 c | DDD | What does this code output?
```php
final class Order
{
private array $items = [];
public function add(string $sku): void
{
$this->items[$sku] = true;
}
public function count(): int
{
return count($this->items);
}
public function remove(string $sku): void
{
if (count($this->items) === 1) {
throw new DomainException('last item');
}
unset($this->items[$sku]);
}
}
$o = new Order;
$o->add('a');
try {
$o->remove('a');
} catch (DomainException) {
}
echo $o->count();
``` | «1» Пояснение: remove() throws an exception when there is only one item, so 'a' is never unsetting and count remains 1.
Raw{"answer": 1, "explanation": "remove() throws an exception when there is only one item, so 'a' is never unsetting and count remains 1."} | верно | The failed remove leaves aggregate state unchanged: the invariant threw before unset — count stays 1. |
VC-L9 0.34 c | PHP 8.4–8.5 | What does this code output on PHP 8.5?
```php
class C
{
public function hi(): string { return 'hi'; }
}
echo new C()->hi();
``` | «hi» Пояснение: The object is instantiated and the hi() method returns the string 'hi', which is echoed.
Raw{"answer":"hi","explanation":"The object is instantiated and the hi() method returns the string 'hi', which is echoed."} | верно | Since 8.4, new in a method chain works without wrapping parentheses. |
VC-L10 0.5 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';
``` | «yesyes» Пояснение: newLazyGhost returns an uninitialized lazy object; the closure assigns to $v which does not trigger initialization, so both isUninitializedLazyObject checks remain true.
Raw{ ⏎ "answer": "yesyes", ⏎ "explanation": "newLazyGhost returns an uninitialized lazy object; the closure assigns to $v which does not trigger initialization, so both isUninitializedLazyObject checks remain true." ⏎ } | неверно верный: «yesno» | newLazyGhost (8.4): the object stays lazy until first access — reading a property initializes it and clears the flag. |
T28-L9 0.44 c | Symfony: versions | The project was upgraded from Symfony 6.4 to 8.1. What does this code output on 8.1?
```php
echo class_exists(\Symfony\Component\Security\Guard\AbstractGuardAuthenticator::class)
? 'yes' : 'no';
``` | «no» Пояснение: The Guard component was removed in Symfony 6.3 and is no longer available in Symfony 8.1.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "The Guard component was removed in Symfony 6.3 and is no longer available in Symfony 8.1." ⏎ } | верно | Guard authentication was removed in Symfony 7.0 — the class is gone in 8.1. |
T28-L10 0.55 c | Symfony: versions | The project was upgraded from Symfony 6.4 to 8.1. What does this code output on 8.1?
```php
echo class_exists(\Symfony\Component\Routing\Loader\AnnotationClassLoader::class)
? 'yes' : 'no';
echo class_exists(\Symfony\Component\Routing\Loader\AttributeClassLoader::class)
? 'yes' : 'no';
``` | «noyes» Пояснение: In Symfony 8.1, the deprecated AnnotationClassLoader is no longer available, so the first check returns 'no', while the new AttributeClassLoader is available, so the second check returns 'yes'.
Raw{ ⏎ "answer": "noyes", ⏎ "explanation": "In Symfony 8.1, the deprecated AnnotationClassLoader is no longer available, so the first check returns 'no', while the new AttributeClassLoader is available, so the second check returns 'yes'." ⏎ } | верно | Annotation loaders were removed in 7.0; only attribute loaders remain (Annotation→Attribute). |