Пример запроса (первая клетка). 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» Пояснение: Single-quoted and double-quoted strings differ in whether they undergo variable substitution and escape-sequence processing.
Raw{ ⏎ "answer": "false", ⏎ "explanation": "Single-quoted and double-quoted strings differ in whether they undergo variable substitution and escape-sequence processing." ⏎ } | верно | В двойных кавычках работают интерполяция переменных и escape-последовательности, в одинарных — нет. |
T01-L2 0.44 c | Syntax and operators | The ?? operator follows isset semantics and raises no warnings for undefined variables. | «yes» Пояснение: The null coalescing operator (??) checks if the left operand is set and not null without raising a notice for undefined variables, unlike the ternary operator with isset().
Raw{"answer": "yes", "explanation": "The null coalescing operator (??) checks if the left operand is set and not null without raising a notice for undefined variables, unlike the ternary operator with isset()."} | верно | ?? работает по семантике isset — несуществующие переменные и ключи допустимы. |
T01-L3 0.35 c | Syntax and operators | What will this print: echo 'a', 'b'; | «ab» Пояснение: The comma operator evaluates the first expression ('a'), then the second ('b'), and the last evaluated value is used for the print.
Raw{"answer":"ab","explanation":"The comma operator evaluates the first expression ('a'), then the second ('b'), and the last evaluated value is used for the print."} | верно | echo принимает список аргументов: ab. |
T01-L4 0.45 c | Syntax and operators | print returns the value 1 and can be used inside an expression. | «no» Пояснение: In PHP, the print statement returns the string "1" (not the integer 1) and is a language construct that cannot be used as an expression like a function or variable.
Raw{"answer": "no", "explanation": "In PHP, the print statement returns the string \"1\" (not the integer 1) and is a language construct that cannot be used as an expression like a function or variable."} | неверно верный: «yes» | print — выражение со значением 1, в отличие от echo, который значения не возвращает. |
T01-L5 0.29 c | Syntax and operators | The ?: (elvis) operator returns its left operand when it is falsy. | «no» Пояснение: The Elvis operator returns its left operand when it is truthy, not falsy.
Raw{"answer": "no", "explanation": "The Elvis operator returns its left operand when it is truthy, not falsy."} | верно | Наоборот: $a ?: $b возвращает $a, если он истинный, иначе $b. |
T01-L6 0.47 c | Syntax and operators | In PHP 8, the concatenation operator (.) has lower precedence than addition and subtraction. | «yes» Пояснение: The concatenation operator (.) has lower precedence than + and - in PHP, so a + b . c is evaluated as (a + b) . c.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "The concatenation operator (.) has lower precedence than + and - in PHP, so a + b . c is evaluated as (a + b) . c." ⏎ } | верно | С PHP 8 (RFC concat precedence) '.' имеет приоритет ниже арифметики: 'сумма: ' . 2 + 3 → 'сумма: 5' (в PHP 7 было иначе). |
T01-L7 0.64 c | Syntax and operators | The expression 2 ** 3 ** 2 in PHP evaluates as (2 ** 3) ** 2, that is, 64. | «yes» Пояснение: In PHP, the ** operator is right-associative, so 2 ** 3 ** 2 is evaluated as 2 ** (3 ** 2), which equals 2 ** 9 = 512, not (2 ** 3) ** 2 = 64.
Raw{"answer": "yes", "explanation": "In PHP, the ** operator is right-associative, so 2 ** 3 ** 2 is evaluated as 2 ** (3 ** 2), which equals 2 ** 9 = 512, not (2 ** 3) ** 2 = 64."} | неверно верный: «no» | ** право-ассоциативен: 2 ** (3 ** 2) = 2 ** 9 = 512. |
T01-L8 0.76 c | Syntax and operators | What string will this print: echo 'sum: ' . 2 + 3; (PHP 8)? | «sum: 2» Пояснение: The string concatenation operator '.' has higher precedence than the addition operator '+', so it first concatenates the string 'sum: ' with the integer 2, and then attempts to add 3 to the resulting string 'sum: 2', which is coerced to 0, resulting in 'sum: 2' being printed.
Raw{"answer": "sum: 2", "explanation": "The string concatenation operator '.' has higher precedence than the addition operator '+', so it first concatenates the string 'sum: ' with the integer 2, and then attempts to add 3 to the resulting string 'sum: 2', which is coerced to 0, resulting in 'sum: 2' being printed."} | неверно верный: «sum: 5» | Парная к verify-клетке про приоритет: 'сумма: 5'. |
T02-L1 0.37 c | Types and comparisons | With strict comparison (===), arrays are considered equal regardless of element order. | «no» Пояснение: Strict comparison of arrays requires them to have identical key/value pairs in the same order.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "Strict comparison of arrays requires them to have identical key/value pairs in the same order." ⏎ } | верно | === для массивов требует совпадения и значений, и их порядка. |
T02-L2 0.31 c | Types and comparisons | The comparison 0 == false returns false because it is a strict comparison. | «no» Пояснение: 0 == false is a loose comparison that returns true, not false.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "0 == false is a loose comparison that returns true, not false." ⏎ } | верно | Наоборот: == — нестрогое сравнение и возвращает true; строгое — это === (0 === false → false). |
T02-L3 0.49 c | Types and comparisons | In PHP 8, the expression "abc" == 0 returns true. | «no» Пояснение: In PHP 8, the loose comparison 'abc' == 0 returns false, as the comparison rules were changed so that a non-numeric string is not converted to a number when compared to a number.
Raw{"answer": "no", "explanation": "In PHP 8, the loose comparison 'abc' == 0 returns false, as the comparison rules were changed so that a non-numeric string is not converted to a number when compared to a number."} | верно | С PHP 8 нечисловая строка сравнивается как строка: "abc" == "0" → false (в PHP 7 было true). |
T02-L4 0.33 c | Types and comparisons | Under loose comparison, null equals 0, the empty string, and false at the same time. | «no» Пояснение: In PHP loose comparison, null equals false and the empty string, but it is not equal to the integer 0.
Raw{"answer":"no","explanation":"In PHP loose comparison, null equals false and the empty string, but it is not equal to the integer 0."} | неверно верный: «yes» | null == 0, null == "" и null == false — все true. |
T02-L5 0.46 c | Types and comparisons | What does the expression (int) '42abc' return? | «42» Пояснение: In PHP, casting a string to int takes the leading numeric value and ignores any trailing non-numeric characters, so (int) '42abc' evaluates to 42.
Raw{"answer": 42, "explanation": "In PHP, casting a string to int takes the leading numeric value and ignores any trailing non-numeric characters, so (int) '42abc' evaluates to 42."} | верно | Ведущая числовая часть: 42, без ошибок и warning. |
T02-L6 0.43 c | Types and comparisons | What does the expression '5' + 5 return? | «10» Пояснение: In PHP, the string '5' is converted to the integer 5, and the result of the addition is 10.
Raw{ ⏎ "answer": 10, ⏎ "explanation": "In PHP, the string '5' is converted to the integer 5, and the result of the addition is 10." ⏎ } | верно | Числовая строка приводится: int 10. |
T02-L7 0.3 c | Types and comparisons | When cast to string, false becomes "0". | «yes» Пояснение: In PHP, casting the boolean false to a string results in the string "0".
Raw{"answer": "yes", "explanation": "In PHP, casting the boolean false to a string results in the string \"0\"."} | неверно верный: «no» | false → "", true → "1". |
T02-L8 0.57 c | Types and comparisons | The comparison 0.1 + 0.2 === 0.3 returns false. | «yes» Пояснение: In PHP, 0.1 + 0.2 evaluates to 0.30000000000000004 due to floating-point precision errors, which is not strictly equal to 0.3.
Raw{"answer": "yes", "explanation": "In PHP, 0.1 + 0.2 evaluates to 0.30000000000000004 due to floating-point precision errors, which is not strictly equal to 0.3."} | верно | Двоичная погрешность float: 0.1 + 0.2 = 0.30000000000000004. |
T03-L1 0.36 c | Strings | strrev() correctly reverses a UTF-8 string. | «no» Пояснение: strrev() reverses bytes, not characters, so it will corrupt multi-byte UTF-8 characters.
Raw{"answer": "no", "explanation": "strrev() reverses bytes, not characters, so it will corrupt multi-byte UTF-8 characters."} | верно | strrev переворачивает байты и ломает многобайтовые последовательности. |
T03-L2 0.28 c | Strings | str_contains('Hello world', 'world') returns true. | «yes» Пояснение: The string 'Hello world' does contain the substring 'world'.
Raw{"answer": "yes", "explanation": "The string 'Hello world' does contain the substring 'world'."} | верно | str_contains с PHP 8.0 проверяет вхождение подстроки. |
T03-L3 0.32 c | Strings | str_pad() can pad a string on the right side only. | «no» Пояснение: str_pad() allows padding on the left, right, or both sides via the $pad_side parameter.
Raw{"answer": "no", "explanation": "str_pad() allows padding on the left, right, or both sides via the $pad_side parameter."} | верно | STR_PAD_LEFT / STR_PAD_BOTH меняют сторону дополнения. |
T03-L4 0.37 c | Strings | By default trim() strips only spaces, leaving tabs and newlines intact. | «no» Пояснение: The trim() function, by default, strips whitespace characters which include spaces, tabs, newlines, carriage returns, and null bytes.
Raw{"answer": "no", "explanation": "The trim() function, by default, strips whitespace characters which include spaces, tabs, newlines, carriage returns, and null bytes."} | верно | Список символов по умолчанию: « \t\n\r\0\x0B» — пробелы, табы, переводы строк, возврат каретки, null-байт, вертикальный таб. Проверено php -r. |
T03-L5 0.45 c | Strings | How many BYTES does strlen('héllo') return for a UTF-8 string? | «6» Пояснение: The character 'é' is represented by 2 bytes in UTF-8, so 'héllo' contains 5 characters totaling 6 bytes.
Raw{ ⏎ "answer": 6, ⏎ "explanation": "The character 'é' is represented by 2 bytes in UTF-8, so 'héllo' contains 5 characters totaling 6 bytes." ⏎ } | верно | 6 букв по 2 байта: 12. |
T03-L6 0.47 c | Strings | What does substr('abcdef', -3) return? | «def» Пояснение: The substr function with a negative start position counts from the end of the string, so starting at -3 of 'abcdef' returns the last three characters, 'def'.
Raw{"answer": "def", "explanation": "The substr function with a negative start position counts from the end of the string, so starting at -3 of 'abcdef' returns the last three characters, 'def'."} | верно | Отрицательное смещение — с конца: def. |
T03-L7 0.37 c | Strings | ucfirst() modifies the string passed to it in place. | «no» Пояснение: In PHP, strings are passed to functions by value, so ucfirst() returns a modified copy rather than modifying the original variable in place.
Raw{"answer": "no", "explanation": "In PHP, strings are passed to functions by value, so ucfirst() returns a modified copy rather than modifying the original variable in place."} | верно | Строки неизменяемы; ucfirst возвращает новую строку. |
T03-L8 0.39 c | Strings | Variable interpolation works in heredoc but not in nowdoc. | «no» Пояснение: Both heredoc and nowdoc support variable interpolation, with the main difference being that heredoc requires double quotes while nowdoc uses single quotes.
Raw{"answer": "no", "explanation": "Both heredoc and nowdoc support variable interpolation, with the main difference being that heredoc requires double quotes while nowdoc uses single quotes."} | неверно верный: «yes» | Nowdoc — «одинарные кавычки» в тройном синтаксисе: текст как есть. |
T04-L1 0.5 c | Arrays | The sort() function preserves the key-to-value association of the array. | «no» Пояснение: The sort() function reindexes the array with sequential numeric keys, thereby destroying the original key-to-value association (use ksort() or arsort() to sort by keys while preserving them).
Raw```json ⏎ {"answer": "no", "explanation": "The sort() function reindexes the array with sequential numeric keys, thereby destroying the original key-to-value association (use ksort() or arsort() to sort by keys while preserving them)."} ⏎ ``` | верно | sort перенумеровывает ключи; связь сохраняет asort. |
T04-L2 0.56 c | Arrays | The string key '5' in an array is stored as the integer 5. | «no» Пояснение: In PHP, array keys are automatically cast to integers if they are numeric strings, but the key '5' itself is the string '5' before conversion, so it is not stored as the integer 5 by default.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "In PHP, array keys are automatically cast to integers if they are numeric strings, but the key '5' itself is the string '5' before conversion, so it is not stored as the integer 5 by default." ⏎ } | неверно верный: «yes» | Каноничные десятичные строковые ключи приводятся к int. |
T04-L3 0.41 c | Arrays | The in_array() function uses strict comparison (===) by default. | «no» Пояснение: The in_array() function uses loose comparison (==) by default, and you must set the third parameter to true to use strict comparison.
Raw{"answer": "no", "explanation": "The in_array() function uses loose comparison (==) by default, and you must set the third parameter to true to use strict comparison."} | верно | По умолчанию сравнение нестрогое; строгое — третий аргумент true. |
T04-L4 0.41 c | Arrays | Without a callback, array_filter() removes all "empty" (falsy) elements from the array. | «yes» Пояснение: When array_filter() is called without a callback, it removes all elements that are falsy (e.g., 0, "", null, false).
Raw{"answer": "yes", "explanation": "When array_filter() is called without a callback, it removes all elements that are falsy (e.g., 0, \"\", null, false)."} | верно | Убирает 0, "", null, false и пустые массивы. |
T04-L5 0.44 c | Arrays | By default, array_slice() preserves the original numeric keys of the array. | «no» Пояснение: By default, array_slice() resets the array keys to sequential integers starting from 0, unless the preserve_keys parameter is explicitly set to true.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "By default, array_slice() resets the array keys to sequential integers starting from 0, unless the preserve_keys parameter is explicitly set to true." ⏎ } | верно | По умолчанию ключи перенумеровываются; сохранение — preserve_keys = true. |
T04-L6 0.51 c | Arrays | What does array_slice([10, 20, 30, 40], 1, 2) return? | «[20, 30]» Пояснение: array_slice extracts 2 elements starting from index 1 of the array [10, 20, 30, 40], returning [20, 30].
Raw{"answer": "[20, 30]", "explanation": "array_slice extracts 2 elements starting from index 1 of the array [10, 20, 30, 40], returning [20, 30]."} | верно | [20,30]; ключи перенумеровываются. |
T04-L7 0.43 c | Arrays | How many elements will count(['a' => 1] + ['a' => 9, 'b' => 2]) return? | «2» Пояснение: In PHP, the array addition operator (+) does not overwrite existing keys; it only adds new key-value pairs from the right-hand array.
Raw{"answer": 2, "explanation": "In PHP, the array addition operator (+) does not overwrite existing keys; it only adds new key-value pairs from the right-hand array."} | верно | Оператор + : по ключу 'a' побеждает левый; итого 2. |
T04-L8 0.44 c | Arrays | Since PHP 8.1, the spread operator [...$a, ...$b] supports arrays with string keys. | «yes» Пояснение: PHP 8.1 introduced the array spread operator (which uses the same [] syntax) for merging arrays, and it supports both numeric and string keys.
Raw{"answer": "yes", "explanation": "PHP 8.1 introduced the array spread operator (which uses the same [] syntax) for merging arrays, and it supports both numeric and string keys."} | верно | В 8.0 — только числовые ключи; 8.1 снял ограничение. |
T05-L1 0.37 c | Functions and closures | Named arguments cannot be combined with argument unpacking ...$args in a single call. | «yes» Пояснение: PHP syntax does not allow mixing named arguments with the spread operator ($args) in the same function call.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "PHP syntax does not allow mixing named arguments with the spread operator ($args) in the same function call." ⏎ } | неверно верный: «no» | Можно: f(...$args, имя: значение). Нельзя только позиционный аргумент после распаковки. |
T05-L2 0.49 c | Functions and closures | An anonymous function without use sees variables from the outer scope. | «no» Пояснение: By default, anonymous functions in PHP do not inherit the scope of the outer variable; you must explicitly pass them using the 'use' keyword or by relying on global variables with global().
Raw{ ⏎ "answer": "false", ⏎ "explanation": "By default, anonymous functions in PHP do not inherit the scope of the outer variable; you must explicitly pass them using the 'use' keyword or by relying on global variables with global()." ⏎ } | верно | Без use внешние переменные недоступны; авто-захват только у fn. |
T05-L3 0.39 c | Functions and closures | What will func_num_args() return inside function f($a) { return func_num_args(); } when called as f(1, 2, 3)? | «3» Пояснение: func_num_args() returns the number of arguments actually passed to the function, which is 3 in this call.
Raw```json ⏎ {"answer": 3, "explanation": "func_num_args() returns the number of arguments actually passed to the function, which is 3 in this call."} ⏎ ``` | верно | Считает переданные аргументы: 3. |
T05-L4 0.39 c | Functions and closures | The body of an arrow function fn may consist of several expressions in curly braces. | «no» Пояснение: The body of an arrow function must be a single expression unless a block body is used with braces and explicit return statements.
Raw{"answer": "false", "explanation": "The body of an arrow function must be a single expression unless a block body is used with braces and explicit return statements."} | верно | fn — всегда одно выражение; блок операторов делает обычная анонимная функция. |
T05-L5 0.49 c | Functions and closures | An arrow function fn captures outer variables by reference (lazily, at use time). | «yes» Пояснение: Arrow functions in PHP use lexical scoping, meaning they automatically capture variables from the outer scope and maintain a reference to them rather than copying their values at the time of closure creation.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Arrow functions in PHP use lexical scoping, meaning they automatically capture variables from the outer scope and maintain a reference to them rather than copying their values at the time of closure creation." ⏎ } | неверно верный: «no» | fn захватывает только по значению, автоматически; по ссылке — только &$var в use у обычной функции (fn так не умеет). |
T05-L6 0.43 c | Functions and closures | A closure declared as static function () {} does not capture $this. | «yes» Пояснение: In PHP, static functions do not have a $this object, so any closure declared as static does not capture $this from its enclosing scope.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "In PHP, static functions do not have a $this object, so any closure declared as static does not capture $this from its enclosing scope." ⏎ } | верно | static-замыкание отвязано от объекта: $this внутри недоступен. |
T05-L7 0.36 c | Functions and closures | What will this print: $x = 5; $f = function () use ($x) { return $x; }; $x = 7; echo $f(); | «5» Пояснение: The closure captures the value of $x at the time of its creation, not by reference.
Raw{ ⏎ "answer": 5, ⏎ "explanation": "The closure captures the value of $x at the time of its creation, not by reference." ⏎ } | верно | 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 PHP weak typing mode, strings that represent integers are implicitly converted to integers when passed to int parameters.
Raw```json ⏎ {"answer": "yes", "explanation": "In PHP weak typing mode, strings that represent integers are implicitly converted to integers when passed to int parameters."} ⏎ ``` | верно | Coercive typing приводит "5" к 5; strict_types=1 требует точного типа. |
T06-L1 0.46 c | OOP: classes and inheritance | PHP supports constructor property promotion: public function __construct(private int $x) {}. | «yes» Пояснение: Constructor property promotion is a PHP 8.0 feature that allows properties to be declared and assigned in the constructor parameters using visibility keywords.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "Constructor property promotion is a PHP 8.0 feature that allows properties to be declared and assigned in the constructor parameters using visibility keywords." ⏎ } ⏎ ``` | верно | С PHP 8.0 параметр с модификатором создаёт свойство и присваивание. |
T06-L2 0.26 c | OOP: classes and inheritance | Which keyword prevents a method from being overridden in subclasses? | «final» Пояснение: The final keyword prevents a method from being overridden in subclasses.
Raw{"answer": "final", "explanation": "The final keyword prevents a method from being overridden in subclasses."} | верно | final. |
T06-L3 0.31 c | OOP: classes and inheritance | A method declared final cannot be overridden in a subclass. | «yes» Пояснение: The final keyword prevents a method from being overridden by subclasses in PHP.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "The final keyword prevents a method from being overridden by subclasses in PHP." ⏎ } | верно | final запрещает переопределение метода и наследование класса. |
T06-L4 0.41 c | OOP: classes and inheritance | Parent properties with private visibility are accessible in a subclass. | «no» Пояснение: Private properties in the parent class are not accessible from the child class and can only be accessed within the scope in which they are defined.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "Private properties in the parent class are not accessible from the child class and can only be accessed within the scope in which they are defined." ⏎ } | верно | В подклассе видны protected и public; private — только внутри своего класса. |
T06-L5 0.4 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 classes are assigned a generated name consisting of the class name followed by a NUL byte, so the portion before the NUL byte is an empty string.
Raw{"answer": "", "explanation": "Anonymous classes are assigned a generated name consisting of the class name followed by a NUL byte, so the portion before the NUL byte is an empty string."} | неверно верный: «class@anonymous» | get_class анонимного класса печатает class@anonymous\0<файл>:<строка>$n; короткая форма — часть до NUL-байта. Проверено php -r (hex). |
T06-L6 0.52 c | OOP: classes and inheritance | A private parent method is not part of the inheritance contract: a child may declare a method with the same name and any visibility. | «yes» Пояснение: Private methods are not inherited, so a child class is free to declare a same-named method with any visibility without conflicting with the parent's private method.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "Private methods are not inherited, so a child class is free to declare a same-named method with any visibility without conflicting with the parent's private method." ⏎ } ⏎ ``` | верно | private-члены не наследуются — правила совместимости подписей не действуют. |
T06-L7 0.45 c | OOP: classes and inheritance | The magic method __get() is called only for non-existent properties. | «no» Пояснение: The __get() magic method is called only when you attempt to access a property that is not declared, inaccessible (private/protected), or has no value.
Raw{"answer": "no", "explanation": "The __get() magic method is called only when you attempt to access a property that is not declared, inaccessible (private/protected), or has no value."} | верно | __get срабатывает и для существующих, но недоступных (private/protected извне). |
T06-L8 0.37 c | OOP: classes and inheritance | What does reassigning a readonly property throw — Exception or Error? | «error» Пояснение: Reassigning a readonly property in PHP 8.1+ throws a readonly property modification exception, which is a subclass of Error.
Raw{"answer": "Error", "explanation": "Reassigning a readonly property in PHP 8.1+ throws a readonly property modification exception, which is a subclass of Error."} | верно | Error (readonly с 8.1); оговорка: в __clone() переинициализация допустима (8.3+). |
T07-L1 0.32 c | Interfaces, traits, enum | An interface can declare constants. | «yes» Пояснение: PHP interfaces can declare constants, which must be public, immutable, and initialized with a literal value.
Raw{"answer": "yes", "explanation": "PHP interfaces can declare constants, which must be public, immutable, and initialized with a literal value."} | верно | Константы интерфейса наследуются реализациями. |
T07-L2 0.42 c | Interfaces, traits, enum | Which operator checks whether an object is an instance of a class or interface? | «instanceof» Пояснение: In PHP, the 'instanceof' operator checks if an object is an instance of a particular class or implements a specific interface.
Raw{ ⏎ "answer": "instanceof", ⏎ "explanation": "In PHP, the 'instanceof' operator checks if an object is an instance of a particular class or implements a specific interface." ⏎ } | верно | instanceof. |
T07-L3 0.31 c | Interfaces, traits, enum | An interface can declare static methods. | «no» Пояснение: Interfaces can only declare abstract methods and constants, as they cannot contain method implementations or static methods.
Raw{"answer": "no", "explanation": "Interfaces can only declare abstract methods and constants, as they cannot contain method implementations or static methods."} | неверно верный: «yes» | Реализация обязана дать статический метод с той же сигнатурой. |
T07-L4 0.42 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 specified class or its subclass, or if it implements a specified interface.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "The instanceof operator returns true if an object is an instance of a specified class or its subclass, or if it implements a specified interface." ⏎ } | верно | instanceof возвращает true и для интерфейсов объекта. |
T07-L5 0.39 c | Interfaces, traits, enum | An interface method may have a default implementation, like a trait method. | «yes» Пояснение: PHP 8.1 introduced default implementations for methods in interfaces using the `abstract` keyword for methods without a body.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "PHP 8.1 introduced default implementations for methods in interfaces using the `abstract` keyword for methods without a body." ⏎ } | неверно верный: «no» | Методы интерфейса — только сигнатуры; тело даёт реализующий класс. |
T07-L6 0.27 c | Interfaces, traits, enum | An abstract method in an abstract class may have protected visibility. | «yes» Пояснение: Abstract methods in PHP can have public, protected, or private visibility.
Raw{"answer": "yes", "explanation": "Abstract methods in PHP can have public, protected, or private visibility."} | верно | В абстрактном классе — любая видимость; в интерфейсе — только public. |
T07-L7 0.38 c | Interfaces, traits, enum | How many elements will Foo::cases() return for enum Foo { case A; case B; case C; }? | «3» Пояснение: The static method cases() on an enum returns all its defined cases, and there are exactly three cases (A, B, and C).
Raw{"answer": 3, "explanation": "The static method cases() on an enum returns all its defined cases, and there are exactly three cases (A, B, and C)."} | верно | Статический метод cases(): 3. |
T07-L8 0.37 c | Interfaces, traits, enum | A trait can declare constants. | «yes» Пояснение: PHP traits support the declaration of class constants, which can be accessed from the using class.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "PHP traits support the declaration of class constants, which can be accessed from the using class." ⏎ } | верно | С 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, both Exception and Error classes inherit from the Throwable interface, making it their common ancestor.
Raw{"answer": "yes", "explanation": "In PHP, both Exception and Error classes inherit from the Throwable interface, making it their common ancestor."} | верно | Иерархия с PHP 7: Throwable → Exception и Throwable → Error. |
T08-L2 0.36 c | Exceptions and errors | A catch (Exception $e) block will also catch TypeError, because TypeError ultimately inherits from Exception. | «yes» Пояснение: In PHP, the TypeError class extends the built-in Exception class, so any code catching Exception will automatically catch TypeError as well.
Raw{"answer": "yes", "explanation": "In PHP, the TypeError class extends the built-in Exception class, so any code catching Exception will automatically catch TypeError as well."} | неверно верный: «no» | TypeError наследуется от Error; catch (Exception) его не ловит. |
T08-L3 0.43 c | Exceptions and errors | The @ operator suppresses exceptions too. | «yes» Пояснение: The @ operator in PHP suppresses most runtime notices, warnings, and deprecations, effectively acting as a simple error suppression mechanism, though it is discouraged in modern development.
Raw{"answer": "yes", "explanation": "The @ operator in PHP suppresses most runtime notices, warnings, and deprecations, effectively acting as a simple error suppression mechanism, though it is discouraged in modern development."} | неверно верный: «no» | @ глушит диагностику (warnings/notices), исключения не перехватывает. |
T08-L4 0.4 c | Exceptions and errors | What error class does intdiv(5, 0) throw? | «divisionbyzeroerror» Пояснение: In PHP 7.0+, the intdiv function with a zero divisor throws a DivisionByZeroError.
Raw{ ⏎ "answer": "DivisionByZeroError", ⏎ "explanation": "In PHP 7.0+, the intdiv function with a zero divisor throws a DivisionByZeroError." ⏎ } | верно | DivisionByZeroError (иерархия Error, не Exception); php-грейдер объективен. |
T08-L5 0.3 c | Exceptions and errors | The finally block runs only if the exception was caught by a catch block. | «no» Пояснение: The finally block executes regardless of whether the exception is caught or the try block completes normally.
Raw{"answer": "no", "explanation": "The finally block executes regardless of whether the exception is caught or the try block completes normally."} | верно | Наоборот: finally выполняется всегда — даже когда исключение не поймано и уходит выше. Проверено php -r. |
T08-L6 0.41 c | Exceptions and errors | An exception thrown inside a finally block has no effect on the result of the try block. | «yes» Пояснение: An exception thrown in a finally block propagates out of the try-finally construct and masks any prior exception, effectively altering the outcome of the try block.
Raw{"answer": "yes", "explanation": "An exception thrown in a finally block propagates out of the try-finally construct and masks any prior exception, effectively altering the outcome of the try block."} | неверно верный: «no» | Исключение из finally перекрывает исходное и уходит вместо него. |
T08-L7 0.36 c | Exceptions and errors | What does the expression (bool) new Exception('x') return? | «yes» Пояснение: In PHP, any object instance is cast to boolean true, so (bool) new Exception('x') evaluates to true.
Raw{"answer": "yes", "explanation": "In PHP, any object instance is cast to boolean true, so (bool) new Exception('x') evaluates to true."} | верно | Любой объект при приведении к bool — true. Формы ответа: true или да. |
T08-L8 0.56 c | Exceptions and errors | Functions registered via register_shutdown_function() run when exit is called. | «yes» Пояснение: Functions registered via register_shutdown_function() run when the script exits normally, including when exit() is called, unless the script is terminated abruptly by a fatal error or an exit code set in a way that prevents them from running.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Functions registered via register_shutdown_function() run when the script exits normally, including when exit() is called, unless the script is terminated abruptly by a fatal error or an exit code set in a way that prevents them from running." ⏎ } | верно | exit завершает скрипт, но shutdown-функции отрабатывают. |
T09-L1 0.51 c | Namespaces and autoloading | The use App\Service\Mailer; statement itself loads the class file. | «no» Пояснение: The `use` statement is a compile-time alias that does not trigger autoloaders or load class files; it is typically executed during compilation or runtime before any instantiation occurs.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "The `use` statement is a compile-time alias that does not trigger autoloaders or load class files; it is typically executed during compilation or runtime before any instantiation occurs." ⏎ } | верно | use — псевдоним на этапе компиляции; файл грузит автозагрузчик при первом обращении. |
T09-L2 0.46 c | Namespaces and autoloading | What follows use to import a function (not a class): the word function or const? | «function» Пояснение: In PHP's namespace import syntax, you use the 'use' statement followed by the 'function' keyword to import a function, whereas 'const' is used for importing constants or classes.
Raw{"answer": "function", "explanation": "In PHP's namespace import syntax, you use the 'use' statement followed by the 'function' keyword to import a function, whereas 'const' is used for importing constants or classes."} | верно | use function ...; (и use const для констант). |
T09-L3 0.51 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 autoloading converts backslashes in the namespace to directory separators, mapping App\Controller\Api\UserController to src/Controller/Api/UserController.php.
Raw{"answer":"src/Controller/Api/UserController.php","explanation":"PSR-4 autoloading converts backslashes in the namespace to directory separators, mapping App\\Controller\\Api\\UserController to src/Controller/Api/UserController.php."} | верно | Остаток имени после префикса, \ → /. |
T09-L4 0.4 c | Namespaces and autoloading | Including vendor/autoload.php registers autoloaders via spl_autoload_register(). | «yes» Пояснение: Including vendor/autoload.php registers autoloader adapters (such as classmap and PSR-4) via spl_autoload_register().
Raw{"answer": "yes", "explanation": "Including vendor/autoload.php registers autoloader adapters (such as classmap and PSR-4) via spl_autoload_register()."} | верно | Composer ставит автозагрузчик именно на spl_autoload_register. |
T09-L5 0.42 c | Namespaces and autoloading | The magic constant __NAMESPACE__ contains the name of the current namespace. | «no» Пояснение: __NAMESPACE__ is a magic constant that resolves to the name of the namespace it is defined in, not a magic constant that contains it by name in the way stated.
Raw{"answer": "no", "explanation": "__NAMESPACE__ is a magic constant that resolves to the name of the namespace it is defined in, not a magic constant that contains it by name in the way stated."} | неверно верный: «yes» | В корневом пространстве — пустая строка. |
T09-L6 0.42 c | Namespaces and autoloading | An unqualified class name (without a leading \) in new is resolved from the global root. | «no» Пояснение: An unqualified class name in `new` is resolved using the current namespace, and only if not found in that namespace does it fall back to the global root.
Raw{"answer": "no", "explanation": "An unqualified class name in `new` is resolved using the current namespace, and only if not found in that namespace does it fall back to the global root."} | верно | Резолвится относительно текущего namespace (с учётом импортов). |
T09-L7 0.43 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 the namespace subdirectory structure to mirror the class hierarchy, so App\Model\User maps to src/Model/User.php.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "PSR-4 requires the namespace subdirectory structure to mirror the class hierarchy, so App\\Model\\User maps to src/Model/User.php." ⏎ } | верно | Остаток имени после префикса переносится в путь как есть. |
T09-L8 0.41 c | Namespaces and autoloading | A use statement may be written inside a function body — the import then applies to that function only. | «yes» Пояснение: In PHP, use statements can be placed inside a function, class, or namespace, and in a function the import is scoped to that function body.
Raw{"answer":"yes","explanation":"In PHP, use statements can be placed inside a function, class, or namespace, and in a function the import is scoped to that function body."} | неверно верный: «no» | use внутри тела функции — parse error; импорты файловые и компиляционные. |
T10-L1 0.27 c | References and scope | Arrays are copied on assignment rather than passed by reference. | «no» Пояснение: Arrays in PHP are copied on assignment, so this statement is true.
Raw{"answer": "no", "explanation": "Arrays in PHP are copied on assignment, so this statement is true."} | неверно верный: «yes» | Присваивание массива — копия (в движке — copy-on-write). |
T10-L2 0.48 c | References and scope | What will this print: $a = [1, 2]; $b = $a; $b[] = 3; echo count($a); | «2» Пояснение: In PHP, assigning one array to another creates a copy (copy-on-write), so modifying $b with $b[] = 3 does not affect $a, which still contains two elements.
Raw{"answer": 2, "explanation": "In PHP, assigning one array to another creates a copy (copy-on-write), so modifying $b with $b[] = 3 does not affect $a, which still contains two elements."} | верно | Присваивание — копия: в $a по-прежнему 2 элемента. |
T10-L3 0.43 c | References and scope | Inside a function, user-defined global variables are inaccessible without global, $GLOBALS, or passing them as parameters. | «yes» Пояснение: Variables defined in the global scope are not visible inside a function unless accessed via the global keyword, the $GLOBALS array, or passed explicitly as parameters.
Raw{"answer": "yes", "explanation": "Variables defined in the global scope are not visible inside a function unless accessed via the global keyword, the $GLOBALS array, or passed explicitly as parameters."} | верно | Область видимости функций изолирована; исключение — суперглобалы ($_GET и др.). |
T10-L4 0.37 c | References and scope | unset($GLOBALS['x']) inside a function removes the global variable only for that function. | «yes» Пояснение: unset() on a global array element removes the variable from the global scope, not just for that function.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "unset() on a global array element removes the variable from the global scope, not just for that function." ⏎ } | неверно верный: «no» | $GLOBALS — прямое окно в глобальную область: unset удалит её по-настоящему. |
T10-L5 0.32 c | References and scope | What will this print: function inc(&$x) { $x++; } $n = 5; inc($n); echo $n; | «6» Пояснение: The function inc modifies $n by reference, incrementing it from 5 to 6.
Raw{"answer": "6", "explanation": "The function inc modifies $n by reference, incrementing it from 5 to 6."} | верно | Ссылка меняет оригинал: 6. |
T10-L6 0.41 c | References and scope | A foreach over an array (by value) works with the "live" array: changes to the array inside the loop are visible in the same pass. | «no» Пояснение: A foreach loop over an array by value operates on a copy of the array, so changes made to the array inside the loop do not affect the original array.
Raw{"answer": "false", "explanation": "A foreach loop over an array by value operates on a copy of the array, so changes made to the array inside the loop do not affect the original array."} | верно | По значению foreach итерирует копию-снимок. |
T10-L7 0.42 c | References and scope | A static property belongs to each instance separately: changes in one object are not visible in others. | «no» Пояснение: Static properties are shared among all instances of a class, so changes in one instance are visible in all others.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "Static properties are shared among all instances of a class, so changes in one instance are visible in all others." ⏎ } | верно | Наоборот: статическое свойство общее для всех экземпляров класса. Проверено php -r. |
T10-L8 0.36 c | References and scope | An array can have a boolean key true, and it will be stored as bool. | «no» Пояснение: PHP arrays do not allow boolean keys; only integers and strings can be used as array keys.
Raw{ ⏎ "answer": "false", ⏎ "explanation": "PHP arrays do not allow boolean keys; only integers and strings can be used as array keys." ⏎ } | верно | Булев ключ приводится к int: true → 1, false → 0. |
T11-L1 0.5 c | Generators, iterators, SPL | Inside a generator, return with a value can be used, and it becomes available via $gen->getReturn(). | «yes» Пояснение: Since PHP 7.2, generators support a 'yield from' style return value via the 'return' statement inside the generator function, which is accessible via the 'getReturn()' method on the Generator object.
Raw{"answer": "yes", "explanation": "Since PHP 7.2, generators support a 'yield from' style return value via the 'return' statement inside the generator function, which is accessible via the 'getReturn()' method on the Generator object."} | верно | return-значение генератора доступно через getReturn() после прохода. |
T11-L2 0.39 c | Generators, iterators, SPL | A fully consumed generator can be rewound with rewind() and traversed again. | «yes» Пояснение: In PHP, a fully consumed generator can be rewound and traversed again by calling the rewind() method on it.
Raw{"answer": "yes", "explanation": "In PHP, a fully consumed generator can be rewound and traversed again by calling the rewind() method on it."} | неверно верный: «no» | Генератор одноразовый: rewind после начала итерации бросает Exception. |
T11-L3 0.35 c | Generators, iterators, SPL | The yield from construct delegates traversal to another generator or iterable. | «yes» Пояснение: The yield from construct in PHP is used to delegate traversal to another generator or iterable, effectively flattening a generator of generators.
Raw{"answer": "yes", "explanation": "The yield from construct in PHP is used to delegate traversal to another generator or iterable, effectively flattening a generator of generators."} | верно | yield from проксирует значения, ключи и return-значение внутреннего генератора. |
T11-L4 0.36 c | Generators, iterators, SPL | What does get_class(g()) return for function g() { yield 1; }? | «generator» Пояснение: In PHP, calling a generator function returns a Generator object, so get_class(g()) returns 'Generator'.
Raw```json ⏎ {"answer": "Generator", "explanation": "In PHP, calling a generator function returns a Generator object, so get_class(g()) returns 'Generator'."} ⏎ ``` | верно | Функция с yield возвращает Generator. |
T11-L5 0.36 c | Generators, iterators, SPL | How many elements will count(iterator_to_array((function () { yield from [1, 2, 3]; })())) return? | «3» Пояснение: The generator yields three elements (1, 2, and 3) which are all included in the resulting array.
Raw{"answer": 3, "explanation": "The generator yields three elements (1, 2, and 3) which are all included in the resulting array."} | верно | yield from делегирует все 3 элемента. |
T11-L6 0.41 c | Generators, iterators, SPL | The SplStack class implements a FIFO queue. | «yes» Пояснение: The SplStack class in PHP implements a LIFO (Last-In, First-Out) stack, not a FIFO queue.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "The SplStack class in PHP implements a LIFO (Last-In, First-Out) stack, not a FIFO queue." ⏎ } | неверно верный: «no» | SplStack — стек LIFO; очередь FIFO — SplQueue. |
T11-L7 0.33 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 provides a standard way to iterate over arrays using the Iterator interface.
Raw{"answer": "yes", "explanation": "ArrayIterator is a built-in PHP class that provides a standard way to iterate over arrays using the Iterator interface."} | верно | Объектная обёртка над массивом. |
T11-L8 0.32 c | Generators, iterators, SPL | An ArrayObject instance cannot be traversed with foreach. | «no» Пояснение: ArrayObject is traversable and can be used with the foreach statement.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "ArrayObject is traversable and can be used with the foreach statement." ⏎ } | верно | ArrayObject реализует IteratorAggregate — foreach по нему работает. |
T12-L1 0.39 c | Configuration and security | password_hash() generates a salt automatically — passing one separately is not needed. | «yes» Пояснение: Yes, password_hash() automatically generates and stores a unique salt with the password hash, so there is no need to pass a separate salt argument.
Raw{"answer": "yes", "explanation": "Yes, password_hash() automatically generates and stores a unique salt with the password hash, so there is no need to pass a separate salt argument."} | верно | Соль встраивается в строку результата; параметр salt устарел. |
T12-L2 0.31 c | Configuration and security | In PHP 8, PASSWORD_DEFAULT is md5 with an automatically added salt. | «no» Пояснение: PASSWORD_DEFAULT in PHP uses the bcrypt algorithm (or a better alternative if available), not md5.
Raw{"answer": "no", "explanation": "PASSWORD_DEFAULT in PHP uses the bcrypt algorithm (or a better alternative if available), not md5."} | верно | PASSWORD_DEFAULT — bcrypt; md5 для паролей непригоден (перебирается массово). |
T12-L3 0.37 c | Configuration and security | What does password_verify('secret', password_hash('secret', PASSWORD_DEFAULT)) return? | «true» Пояснение: The password_verify function compares the given password to the hash and returns true if the password matches the hash.
Raw{ ⏎ "answer": "true", ⏎ "explanation": "The password_verify function compares the given password to the hash and returns true if the password matches the hash." ⏎ } | верно | Соль и хеш в одной строке: true (форма ответа: true или да). |
T12-L4 0.32 c | Configuration and security | strip_tags() protects against SQL injection. | «no» Пояснение: strip_tags() is used for removing HTML tags from a string and is unrelated to preventing SQL injection.
Raw{"answer": "no", "explanation": "strip_tags() is used for removing HTML tags from a string and is unrelated to preventing SQL injection."} | верно | strip_tags режет HTML-теги (помощник против XSS), к параметризации SQL отношения не имеет. |
T12-L5 0.38 c | Configuration and security | session_regenerate_id() is used to protect against session fixation upon user login. | «yes» Пояснение: session_regenerate_id() generates a new session ID and invalidates the old one, which is the standard method for protecting against session fixation attacks.
Raw{"answer": "yes", "explanation": "session_regenerate_id() generates a new session ID and invalidates the old one, which is the standard method for protecting against session fixation attacks."} | верно | Новый ID сессии после логина — стандартная защита от session fixation. |
T12-L6 0.49 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 current SAPI (Server API) module, such as "cli", "apache2handler", etc.
Raw{ ⏎ "answer": "php_sapi_name", ⏎ "explanation": "The php_sapi_name() function returns the name of the current SAPI (Server API) module, such as \"cli\", \"apache2handler\", etc." ⏎ } | верно | php_sapi_name(). |
T12-L7 0.41 c | Configuration and security | session_destroy() deletes session data on the server but not the cookie in the user's browser. | «yes» Пояснение: session_destroy() removes the session data from the server's storage, but it does not automatically delete the session cookie from the user's browser.
Raw{"answer": "yes", "explanation": "session_destroy() removes the session data from the server's storage, but it does not automatically delete the session cookie from the user's browser."} | верно | Удаление cookie — отдельный шаг через setcookie с истёкшим сроком. |
T12-L8 0.36 c | Configuration and security | Without calling session_start(), the $_SESSION array is automatically populated with session data. | «no» Пояснение: The $_SESSION array is not automatically populated; you must call session_start() to initialize the session.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "The $_SESSION array is not automatically populated; you must call session_start() to initialize the session." ⏎ } | верно | Без session_start() данные сессии в массив не загружаются ($_SESSION можно заполнить вручную, но привязки к сессии нет). |
VC-L1 0.29 c | PHP 8.4–8.5 | In which PHP version was the array_find() function introduced? | «php 8.4» Пояснение: array_find() was introduced in PHP 8.4.
Raw{"answer": "PHP 8.4", "explanation": "array_find() was introduced in PHP 8.4."} | верно | PHP 8.4 (RFC array_find). |
VC-L2 0.4 c | PHP 8.4–8.5 | Property hooks (get/set right in the property declaration) landed in PHP 8.4. | «no» Пояснение: Property hooks (get/set in property declarations) landed in PHP 8.3, not PHP 8.4.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "Property hooks (get/set in property declarations) landed in PHP 8.3, not PHP 8.4." ⏎ } | неверно верный: «yes» | Property hooks — PHP 8.4 (ноябрь 2024). |
VC-L3 0.35 c | PHP 8.4–8.5 | Asymmetric visibility (public private(set) string $name) appeared in PHP 8.4. | «yes» Пояснение: Asymmetric visibility (e.g. public private(set) string $name) was introduced in PHP 8.4.
Raw{"answer": "yes", "explanation": "Asymmetric visibility (e.g. public private(set) string $name) was introduced in PHP 8.4."} | верно | Asymmetric visibility v2 — PHP 8.4. |
VC-L4 0.46 c | PHP 8.4–8.5 | In which PHP version was the #[\NoDiscard] attribute introduced? Answer with the version number. | «8.0» Пояснение: The #[\NoDiscard] attribute was introduced in PHP 8.0 to indicate that the return value of a function should not be discarded.
Raw{ ⏎ "answer": "8.0", ⏎ "explanation": "The #[\\NoDiscard] attribute was introduced in PHP 8.0 to indicate that the return value of a function should not be discarded." ⏎ } | неверно верный: «8.5» | #[\NoDiscard] — PHP 8.5 (marking return values as important). |
VC-L5 0.35 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 (|>) for pipelines was introduced in PHP 8.1.
Raw{"answer": "8.1", "explanation": "The pipe operator (|>) for pipelines was introduced in PHP 8.1."} | неверно верный: «8.5» | Pipe operator — PHP 8.5 (2025). |
VC-L6 0.27 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.4» Пояснение: Clone-with was introduced in PHP 8.4.
Raw{"answer": "8.4", "explanation": "Clone-with was introduced in PHP 8.4."} | неверно верный: «8.5» | Clone with v2 — PHP 8.5. |
VC-L7 0.35 c | PHP 8.4–8.5 | In which PHP version were the array_first() and array_last() functions introduced? | «8.3» Пояснение: array_first() and array_last() were introduced in PHP 8.3.
Raw{ ⏎ "answer": "8.3", ⏎ "explanation": "array_first() and array_last() were introduced in PHP 8.3." ⏎ } | неверно верный: «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» Пояснение: RFC Partial Function Application v2 (RFC 3033) was accepted for PHP 8.4.
Raw{"answer": "8.4", "explanation": "RFC Partial Function Application v2 (RFC 3033) was accepted for PHP 8.4."} | неверно верный: «8.6» | PFA v2 принят 05.12.2025 (33-0-0), реализован в PHP 8.6. |
VF-L1 0.26 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.
Raw{"answer":"8.1","explanation":"The clamp() function was introduced in PHP 8.1."} | неверно верный: «8.6» | По данным владельца (wiki.php.net/rfc): clamp_v2 — 8.6; clamp() в 8.5.11 отсутствует (косвенное подтверждение). Дата-якорь делает клетку монотонной. |
VF-L2 0.42 c | PHP: 8.6+ and the future | RFC Context Managers v2 has already been adopted in PHP (as of 2026-11-07). | «no» Пояснение: RFC Context Managers v2 was not adopted in PHP as of November 7, 2026.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "RFC Context Managers v2 was not adopted in PHP as of November 7, 2026." ⏎ } | верно | На 06.11.2026 — в обсуждении (создан 2026-10-23); не принят. |
VF-L3 0.45 c | PHP: 8.6+ and the future | RFC Bound-Erased Generic Types (generics) was declined in 2026. | «yes» Пояснение: The proposal for RFC Bound-Erased Generic Types was indeed declined during the PHP 8.4.0 planning phase in 2026.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "The proposal for RFC Bound-Erased Generic Types was indeed declined during the PHP 8.4.0 planning phase in 2026." ⏎ } | верно | Голосование завершилось 2026-06-28: отклонён (wiki.php.net/rfc). |
VF-L4 0.64 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 PHP 8.3 and the roadmap through PHP 9.0 (late 2026), there is no accepted or scheduled RFC to make ZTS (Zend Thread Safety) the default threading model for PHP; ZTS remains an optional build variant.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "As of PHP 8.3 and the roadmap through PHP 9.0 (late 2026), there is no accepted or scheduled RFC to make ZTS (Zend Thread Safety) the default threading model for PHP; ZTS remains an optional build variant." ⏎ } | верно | Такого принятого RFC нет на дату якоря; якорь делает клетку монотонной — при принятии RFC позже клетка не перевернётся. |
VF-L5 0.38 c | PHP: 8.6+ and the future | As of PHP 8.5, generics (parameterized types) are still absent. | «yes» Пояснение: PHP 8.5 does not include support for generics or parameterized types, which remain an unresolved feature request.
Raw{"answer": "yes", "explanation": "PHP 8.5 does not include support for generics or parameterized types, which remain an unresolved feature request."} | верно | Generics в PHP отсутствуют; отрицательный контроль (не путать с C#/Java). |
VF-L6 0.6 c | PHP: 8.6+ and the future | As of 2026-11-07, the latest stable PHP version is 8.5, and PHP 8.6 has not been released yet (GA — 2026-11-19). | «yes» Пояснение: As of 2026-11-07, PHP 8.5 is the latest stable release, with PHP 8.6 scheduled for general availability on 2026-11-19.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "As of 2026-11-07, PHP 8.5 is the latest stable release, with PHP 8.6 scheduled for general availability on 2026-11-19." ⏎ } | верно | 8.5 — релиз осени 2025; 8.6 GA 19.11.2026 (wiki.php.net/todo/php86). Дата снимка — 06.11.2026. |
VF-L7 0.4 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 officially canceled, so PHP 7.0 became the next major version after PHP 5.x.
Raw{"answer": "yes", "explanation": "PHP 6 was officially canceled, so PHP 7.0 became the next major version after PHP 5.x."} | верно | Исторический факт: ветка 6 не была релизнута. |
VF-L8 0.35 c | PHP: 8.6+ and the future | The RFC adding the #[\Deprecated] attribute to the core was adopted. | «yes» Пояснение: The RFC for adding the #[\Deprecated] attribute was adopted for PHP 8.0.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "The RFC for adding the #[\\Deprecated] attribute was adopted for PHP 8.0." ⏎ } | верно | #[\Deprecated] — принят, реализован в PHP 8.4. |
T25-L1 0.35 c | Clean architecture | The dependency rule of clean and onion architecture: inner layers know nothing about outer ones — dependencies point toward the center. | «yes» Пояснение: The dependency rule in clean and onion architecture mandates that dependencies point inward, meaning inner layers have no knowledge of outer layers.
Raw{"answer": "yes", "explanation": "The dependency rule in clean and onion architecture mandates that dependencies point inward, meaning inner layers have no knowledge of outer layers."} | верно | Чистая (Robert C. Martin), луковичная (Jeffrey Palermo) и гексагональная (ports & adapters) — варианты одной идеи: зависимости направлены внутрь, к домену. Слоями в проекте следит deptrac. |
T25-L2 0.39 c | Clean architecture | Domain entities import neither Doctrine nor Symfony — only the language and, possibly, the standard library. | «yes» Пояснение: Domain entities in DDD are pure PHP classes that should not depend on frameworks or ORMs like Symfony or Doctrine.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Domain entities in DDD are pure PHP classes that should not depend on frameworks or ORMs like Symfony or Doctrine." ⏎ } | верно | Изоляция домена от инфраструктуры; deptrac в проекте как раз следит за слоями. |
T25-L3 0.41 c | Clean architecture | Controllers and Twig templates belong to the business-logic layer because they are the ones calling use cases. | «yes» Пояснение: In layered architecture, the presentation layer (controllers and views/templates) is the business-logic layer that invokes use cases, which then call domain services and repositories.
Raw{"answer": "yes", "explanation": "In layered architecture, the presentation layer (controllers and views/templates) is the business-logic layer that invokes use cases, which then call domain services and repositories."} | неверно верный: «no» | Наоборот: это интерфейсные адаптеры (внешний слой); они зависят от use cases, а не наоборот. |
T25-L4 0.47 c | Clean architecture | What sits at the very center of the onion architecture? | «use case» Пояснение: In the Onion architecture, the core business rules and use cases sit at the very center, with the interface, data access, and presentation layers arranged around it.
Raw{ ⏎ "answer": "Use case", ⏎ "explanation": "In the Onion architecture, the core business rules and use cases sit at the very center, with the interface, data access, and presentation layers arranged around it." ⏎ } | неверно верный: «domain model» | Центральное кольцо — Domain Model: сущности и бизнес-правила без зависимостей; далее Domain Services → Application Services → Infrastructure/UI/Tests (Palermo). |
T25-L5 0.39 c | Clean architecture | Layer boundary violations can be caught automatically: a layer-dependency analyzer (e.g. deptrac) fails on a forbidden call. | «yes» Пояснение: Static analysis tools like deptrac can automatically enforce architectural boundaries by detecting forbidden dependencies between layers.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Static analysis tools like deptrac can automatically enforce architectural boundaries by detecting forbidden dependencies between layers." ⏎ } | верно | depfile.yaml в проекте TasK: CI проверяет правила слоёв на каждом пайплайне. |
T25-L6 0.33 c | Clean architecture | A use case (interactor) may accept an HTTP request or an EntityManager as arguments — it is simpler that way. | «no» Пояснение: Use cases should generally avoid direct dependencies on HTTP or ORM objects to maintain loose coupling and ease of testing.
Raw{"answer": "no", "explanation": "Use cases should generally avoid direct dependencies on HTTP or ORM objects to maintain loose coupling and ease of testing."} | верно | Use case принимает DTO и порты; привязка к HTTP/ORM протекает инфраструктуру во внутренние слои. |
T25-L7 0.45 c | Clean architecture | What is the component called that provides a collection of aggregates/entities while hiding the storage mechanism behind an interface? | «repository» Пояснение: In the Domain-Driven Design and Entity-Relationship patterns, a repository is the interface used to encapsulate data access and storage details, exposing a collection of entities to the domain layer.
Raw{"answer": "repository", "explanation": "In the Domain-Driven Design and Entity-Relationship patterns, a repository is the interface used to encapsulate data access and storage details, exposing a collection of entities to the domain layer."} | верно | Repository pattern (DDD/Evans); в проекте — Doctrine-репозитории за портами. |
T25-L8 0.4 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 are independent of infrastructure details, so database swaps only affect the outer boundary layers.
Raw{"answer": "yes", "explanation": "In clean architecture, the domain and use cases are independent of infrastructure details, so database swaps only affect the outer boundary layers."} | верно | Следствие правила зависимостей: инфраструктура взаимозаменяема. |
T26-L1 0.46 c | DDD | In DDD, an aggregate is just another name for a database table. | «no» Пояснение: In DDD, an aggregate is a cluster of domain objects with a single identity and consistency boundary, which is a domain concept distinct from a physical database table.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "In DDD, an aggregate is a cluster of domain objects with a single identity and consistency boundary, which is a domain concept distinct from a physical database table." ⏎ } | верно | Агрегат — кластер объектов с границей согласованности (транзакционной вокруг корня); таблица — деталь хранения. |
T26-L2 0.51 c | DDD | A Value Object is immutable and compared by the values of its fields, not by identity. | «yes» Пояснение: In Domain-Driven Design, a Value Object is defined by its attributes (value) rather than a unique identity, and it is typically immutable to ensure its state remains consistent throughout its lifecycle.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "In Domain-Driven Design, a Value Object is defined by its attributes (value) rather than a unique identity, and it is typically immutable to ensure its state remains consistent throughout its lifecycle." ⏎ } | верно | Классика Evans: Money, Email; равенство структурное. |
T26-L3 0.41 c | DDD | What is the single external entry point of an aggregate, through which all changes must go, called? | «aggregate root» Пояснение: In Domain-Driven Design, the aggregate root is the single external entry point for an aggregate through which all modifications are made.
Raw{"answer": "Aggregate root", "explanation": "In Domain-Driven Design, the aggregate root is the single external entry point for an aggregate through which all modifications are made."} | верно | Aggregate Root: внешние объекты ссылаются только на корень; он защищает инварианты агрегата. |
T26-L4 0.34 c | DDD | In DDD, a repository is declared for an aggregate (its root), not for every entity. | «yes» Пояснение: In DDD, repositories manage aggregates and are typically declared for the root entity, not individual entities within the aggregate.
Raw{"answer": "yes", "explanation": "In DDD, repositories manage aggregates and are typically declared for the root entity, not individual entities within the aggregate."} | верно | Репозиторий корня хранит границу согласованности агрегата; вложенные сущности доступны только через корень. |
T26-L5 0.43 c | DDD | Ubiquitous language is the model's shared language common to developers and domain experts. | «yes» Пояснение: Ubiquitous language is a concept from Domain-Driven Design that emphasizes the need for a shared language between the development team and domain experts.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Ubiquitous language is a concept from Domain-Driven Design that emphasizes the need for a shared language between the development team and domain experts." ⏎ } | верно | Evans: язык из требований переходит в имена классов и методов. |
T26-L6 0.81 c | DDD | What is the boundary called within which a model and its language are consistent, while outside the same words mean other models? | «the boundary of a language model's training data or domain, often referred to as the model's 'knowledge cutoff' or 'validity domain', within which its predictions are consistent and outside of which the same inputs may yield different or invalid outputs depending on the model» Пояснение: The question describes the limit of a model's learned knowledge or intended application area, which is often defined by its training data or specific domain of use.
Raw{"answer": "The boundary of a language model's training data or domain, often referred to as the model's 'knowledge cutoff' or 'validity domain', within which its predictions are consistent and outside of which the same inputs may yield different or invalid outputs depending on the model.", "explanation": "The question describes the limit of a model's learned knowledge or intended application area, which is often defined by its training data or specific domain of use."} | неверно верный: «bounded context» | Bounded Context; «Заказ» в биллинге и в доставке — разные модели. |
T26-L7 0.48 c | DDD | An anemic model (objects with only getters/setters, logic in services) is the recommended DDD style. | «no» Пояснение: DDD recommends Rich Domain Models (anemic models are considered bad practice) where behavior and logic reside within the domain entities themselves rather than in separate services.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "DDD recommends Rich Domain Models (anemic models are considered bad practice) where behavior and logic reside within the domain entities themselves rather than in separate services." ⏎ } | верно | Наоборот: Evans называет анемичность антипаттерном — поведение должно жить в доменных объектах. |
T26-L8 0.47 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 ensures that the meaning of a domain concept is unambiguous within its scope, meaning the same term can refer to different models or classes in different contexts.
Raw{"answer": "yes", "explanation": "In Domain-Driven Design, a bounded context ensures that the meaning of a domain concept is unambiguous within its scope, meaning the same term can refer to different models or classes in different contexts."} | верно | Модели контекстов независимы; между ними — явная интеграция (ACL, published language). |
T13-L1 0.45 c | Symfony | Services in the Symfony DI container are created lazily by default — on first use. | «yes» Пояснение: Symfony's Dependency Injection container instantiates services lazily (by default), meaning they are not created until they are first requested or resolved.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Symfony's Dependency Injection container instantiates services lazily (by default), meaning they are not created until they are first requested or resolved." ⏎ } | верно | Контейнер инстанцирует сервис при первом извлечении; eager-создания по умолчанию нет. |
T13-L2 0.32 c | Symfony | Which Symfony console command lists all registered routes? | «route:list» Пояснение: The built-in Symfony console command route:list displays all the registered routes.
Raw{ ⏎ "answer": "route:list", ⏎ "explanation": "The built-in Symfony console command route:list displays all the registered routes." ⏎ } | неверно верный: «debug:router» | bin/console debug:router (FrameworkBundle); в Symfony 3 команда называлась router:debug. |
T13-L3 0.37 c | Symfony | Symfony autowiring requires manually declaring every service in services.yaml. | «no» Пояснение: Symfony's autowiring system automatically detects and wires services based on their type and constructor arguments without requiring manual declaration for most standard services.
Raw{"answer": "no", "explanation": "Symfony's autowiring system automatically detects and wires services based on their type and constructor arguments without requiring manual declaration for most standard services."} | верно | Autowire+autoconfigure регистрируют и связывают сервисы автоматически; ручное перечисление — исключение. |
T13-L4 0.4 c | Symfony | Twig templates are compiled into PHP classes and cached between requests. | «yes» Пояснение: The Twig engine compiles templates into PHP templates, which are then compiled into classes and cached in a directory to improve performance.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "The Twig engine compiles templates into PHP templates, which are then compiled into classes and cached in a directory to improve performance." ⏎ } | верно | 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. | «yes» Пояснение: The Symfony development container is cached and rebuilt only when the environment changes, not on every request.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "The Symfony development container is cached and rebuilt only when the environment changes, not on every request." ⏎ } | верно | Kernel проверяет freshness ресурсов (конфиги, классы); иначе переиспользуется кэш контейнера. |
T13-L6 0.3 c | Symfony | Which environment variable selects the active Symfony environment (dev/prod)? | «symfony_env» Пояснение: The active Symfony environment is selected by the SYMFONY_ENV environment variable.
Raw{"answer": "SYMFONY_ENV", "explanation": "The active Symfony environment is selected by the SYMFONY_ENV environment variable."} | неверно верный: «app_env» | APP_ENV в .env; APP_DEBUG — отдельный флаг отладки. |
T13-L7 0.28 c | Symfony | A controller method can be private — Symfony routing works with any method of the class. | «no» Пояснение: Symfony routing requires controller actions to be public methods to be invoked by the framework.
Raw{"answer": "no", "explanation": "Symfony routing requires controller actions to be public methods to be invoked by the framework."} | верно | Действие контроллера должно быть public; приватный метод по маршруту не вызывается. |
T13-L8 0.59 c | Symfony | Event subscribers always receive events before listeners, because the interface gives them priority. | «no» Пояснение: In PHP's PSR-12 (and common event architecture), 'subscribers' and 'listeners' are often used interchangeably for the same component type, and there is no inherent priority given to one over the other by the interface.
Raw{ ⏎ "answer": "false", ⏎ "explanation": "In PHP's PSR-12 (and common event architecture), 'subscribers' and 'listeners' are often used interchangeably for the same component type, and there is no inherent priority given to one over the other by the interface." ⏎ } | верно | Порядок определяет priority, а не тип подписки; приоритеты задаются в getSubscribedEvents() так же, как у слушателей. |
T22-L1 0.39 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 legacy Guard system was removed in Symfony 5.0 in favor of the new Security component using AuthenticatorInterface.
Raw{"answer": "yes", "explanation": "The legacy Guard system was removed in Symfony 5.0 in favor of the new Security component using AuthenticatorInterface."} | верно | Guard объявлен устаревшим в 5.3 и удалён в 6.0; в проекте symfony/security-bundle 8.1. |
T22-L2 0.38 c | Symfony: Security and forms | Which Symfony attribute checks a role/permission right on a controller method (403 without it)? | «isgranted» Пояснение: Symfony uses the IsGranted attribute to check permissions and returns a 403 error if the required role or permission is missing.
Raw{"answer": "IsGranted", "explanation": "Symfony uses the IsGranted attribute to check permissions and returns a 403 error if the required role or permission is missing."} | верно | #[IsGranted('ROLE_ADMIN')]; атрибут из symfony/security-http. |
T22-L3 0.41 c | Symfony: Security and forms | Voters are Symfony's mechanism for checking access to a specific object: isGranted('EDIT', $post). | «yes» Пояснение: The Symfony Access Checker uses voters to determine permission checks, and the isGranted method accepts a role and an object as arguments.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "The Symfony Access Checker uses voters to determine permission checks, and the isGranted method accepts a role and an object as arguments." ⏎ } | верно | VoterInterface->vote(); docs Symfony — Voters. |
T22-L4 0.53 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 recommended and supported method for validation constraints, Doctrine annotations are not entirely unsupported in modern Symfony; they are simply deprecated and will be removed in future versions, meaning they are not strictly 'no longer supported' yet.
Raw{"answer": "no", "explanation": "While PHP attributes are the recommended and supported method for validation constraints, Doctrine annotations are not entirely unsupported in modern Symfony; they are simply deprecated and will be removed in future versions, meaning they are not strictly 'no longer supported' yet."} | неверно верный: «yes» | Докблок-аннотации удалены в Symfony 7.0; стандарт — атрибуты. В проекте symfony/validator 8.1. |
T22-L5 0.33 c | Symfony: Security and forms | CSRF protection of Symfony forms is enabled by default: the form validates the token on submission. | «yes» Пояснение: Symfony's forms automatically generate and validate CSRF tokens on submission by default for security purposes.
Raw{"answer": "yes", "explanation": "Symfony's forms automatically generate and validate CSRF tokens on submission by default for security purposes."} | верно | FormType добавляет скрытое поле _token и проверяет его при валидации; отключение — осознанное исключение (csrf: false). |
T22-L6 0.38 c | Symfony: Security and forms | Form validation in Symfony runs server-side even if the client-side (HTML5) checks passed. | «yes» Пояснение: Symfony enforces server-side form validation as the final security check, ensuring data integrity and validation even after client-side HTML5 checks pass.
Raw{"answer": "yes", "explanation": "Symfony enforces server-side form validation as the final security check, ensuring data integrity and validation even after client-side HTML5 checks pass."} | верно | Клиентская валидация — только удобство; серверная обязательна и идёт по метаданным объекта формы. |
T22-L7 0.29 c | Symfony: Security and forms | Which Symfony maker command generates a form class (FormType)? | «php bin/console make:form» Пояснение: This command generates a FormType class in a Symfony project.
Raw{"answer": "php bin/console make:form", "explanation": "This command generates a FormType class in a Symfony project."} | верно | bin/console make:form (symfony/maker-bundle — в проекте). |
T22-L8 0.26 c | Symfony: Security and forms | Symfony stores the user's password in the session in plain text. | «no» Пояснение: Symfony stores passwords using salted hashing algorithms, not plain text.
Raw{"answer": "no", "explanation": "Symfony stores passwords using salted hashing algorithms, not plain text."} | верно | В сессии живёт объект пользователя в токене; хеш затирается eraseCredentials(), plaintext там никогда не лежит. |
T23-L1 0.47 c | Symfony: configuration and services | Symfony bundle configuration lives in config/packages — one file per bundle or topic. | «yes» Пояснение: In Symfony 4 and later, it is a standard convention to place bundle configuration in separate PHP files under config/packages, such as doctrine.yaml or webapp.yaml.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "In Symfony 4 and later, it is a standard convention to place bundle configuration in separate PHP files under config/packages, such as doctrine.yaml or webapp.yaml." ⏎ } | верно | Стандартная структура (config/packages/*.yaml); перегрузка — config/packages/<env>. |
T23-L2 0.37 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. | «no» Пояснение: In the described setup, it is the real secrets (.env.local) that are non-committed, not the dev defaults file.
Raw{"answer": "no", "explanation": "In the described setup, it is the real secrets (.env.local) that are non-committed, not the dev defaults file."} | неверно верный: «yes» | symfony/dotenv: .env — общий безопасный набор значений; локальные секреты — .env.local (gitignored) или secrets-хранилище. |
T23-L3 0.31 c | Symfony: configuration and services | Which Symfony command lists the container's registered services and their aliases? | «bin/console debug:container» Пояснение: This command displays all registered services and their aliases in the Symfony service container.
Raw{"answer": "bin/console debug:container", "explanation": "This command displays all registered services and their aliases in the Symfony service container."} | верно | bin/console debug:container; параметры контейнера — debug:parameter. |
T23-L4 0.38 c | Symfony: configuration and services | The Symfony container allows changing parameters at runtime: $container->setParameter() works from a controller. | «no» Пояснение: The Symfony container is immutable and frozen after construction, so you cannot change parameters at runtime using setParameter().
Raw{ ⏎ "answer": "no", ⏎ "explanation": "The Symfony container is immutable and frozen after construction, so you cannot change parameters at runtime using setParameter()." ⏎ } | верно | Контейнер компилируется и замораживается; runtime-значения — только через переменные окружения. |
T23-L5 0.33 c | Symfony: configuration and services | By default, Symfony services are public (public: true) — you can fetch them directly from the container. | «yes» Пояснение: By default, Symfony services are public and can be directly fetched from the container unless explicitly marked as private.
Raw{"answer": "yes", "explanation": "By default, Symfony services are public and can be directly fetched from the container unless explicitly marked as private."} | неверно верный: «no» | С 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» Пояснение: Bundles do not require a configuration file to function, as they can use default settings and be configured through services or parameters if needed.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "Bundles do not require a configuration file to function, as they can use default settings and be configured through services or parameters if needed." ⏎ } | верно | У бандлов есть встроенные умолчания (Extension); конфиг нужен только для отклонений от них. |
T23-L7 0.34 c | Symfony: configuration and services | Environment variable values are injected into services.yaml using the %env(VAR)% syntax. | «yes» Пояснение: Symfony's config system supports environment variable interpolation using the %env(VAR)% syntax in configuration files like services.yaml.
Raw{"answer": "yes", "explanation": "Symfony's config system supports environment variable interpolation using the %env(VAR)% syntax in configuration files like services.yaml."} | верно | %env(...)% резолвится в рантайме env-процессорами; docs — Env Var Processors. |
T23-L8 0.39 c | Symfony: configuration and services | Which Symfony environment variable enables debug mode (affects the profiler and Twig debugging)? | «app_debug» Пояснение: The APP_DEBUG environment variable controls whether Symfony runs in debug mode, which activates the debug toolbar and profiler features.
Raw{ ⏎ "answer": "APP_DEBUG", ⏎ "explanation": "The APP_DEBUG environment variable controls whether Symfony runs in debug mode, which activates the debug toolbar and profiler features." ⏎ } | верно | APP_DEBUG=1 (в .env dev-окружения); окружение выбирает APP_ENV — см. T13-L6. |
T16-L1 0.32 c | Symfony: Messenger | A single message in Symfony Messenger can only have one handler. | «no» Пояснение: A single message in Symfony Messenger can be handled by multiple handlers, which are executed in a specific order.
Raw{"answer": "no", "explanation": "A single message in Symfony Messenger can be handled by multiple handlers, which are executed in a specific order."} | верно | Messenger вызывает все хендлеры, подписанные на класс сообщения (docs — Multiple Handlers). |
T16-L2 0.3 c | Symfony: Messenger | The sync transport in Messenger queues the message for a worker, just like async. | «no» Пояснение: The synchronous transport does not queue the message; it executes it immediately within the current process.
Raw{"answer": "no", "explanation": "The synchronous transport does not queue the message; it executes it immediately within the current process."} | верно | Наоборот: sync обрабатывает немедленно в том же процессе, что и отправка; очередь — это async-транспорт. |
T16-L3 0.34 c | Symfony: Messenger | Which console command starts the worker that processes Messenger queue messages? | «bin/console messenger:consume» Пояснение: This Symfony console command starts a worker process that consumes and processes messages from the Messenger queue.
Raw{"answer": "bin/console messenger:consume", "explanation": "This Symfony console command starts a worker process that consumes and processes messages from the Messenger queue."} | верно | bin/console messenger:consume async; воркеры под supervisord/systemd в проде. |
T16-L4 0.39 c | Symfony: Messenger | Retries for failed messages (retry_strategy) are configured per Messenger transport. | «yes» Пояснение: In Symfony's Messenger component, retry strategies are configured at the transport level, specifically within the transport's DSN configuration.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "In Symfony's Messenger component, retry strategies are configured at the transport level, specifically within the transport's DSN configuration." ⏎ } | верно | retry_strategy на транспорте: max_retries, delay, multiplier; docs — Failed Messages & Retries. |
T16-L5 0.33 c | Symfony: Messenger | By default, Messenger serializes messages to JSON. | «yes» Пояснение: In Symfony Messenger, if no serializer is configured or specified, the default behavior is to serialize messages to JSON.
Raw{"answer": "yes", "explanation": "In Symfony Messenger, if no serializer is configured or specified, the default behavior is to serialize messages to JSON."} | неверно верный: «no» | Дефолтный сериализатор — PhpSerializer (serialize()); JSON-сериализатор включается отдельно. |
T16-L6 0.29 c | Symfony: Messenger | Symfony Scheduler produces messages on a schedule and dispatches them through Messenger. | «yes» Пояснение: Symfony Scheduler is designed to dispatch scheduled jobs through Symfony Messenger, making the statement true.
Raw{"answer": "yes", "explanation": "Symfony Scheduler is designed to dispatch scheduled jobs through Symfony Messenger, making the statement true."} | верно | Schedule → RecurringMessage → шина Messenger; docs — Scheduler. |
T16-L7 0.32 c | Symfony: Messenger | Which built-in Messenger transport stores messages in database tables via Doctrine? | «database» Пояснение: The 'database' transport in the Symfony Messenger component uses Doctrine DBAL to store messages in database tables.
Raw{"answer": "database", "explanation": "The 'database' transport in the Symfony Messenger component uses Doctrine DBAL to store 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's middleware system allows developers to add custom handlers that can be inserted at any position in the pipeline.
Raw{"answer": "yes", "explanation": "Symfony Messenger's middleware system allows developers to add custom handlers that can be inserted at any position in the pipeline."} | верно | messenger.bus.*.middleware в yaml; docs — Middleware. |
T28-L1 0.61 c | Symfony: versions | Symfony major releases come every two years, minor ones every six months (in May and November). | «no» Пояснение: The statement is false because Symfony releases follow a different cycle: major versions occur annually (e.g., 5.0 in November 2021, 6.0 in November 2022), while minor releases occur every six months.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "The statement is false because Symfony releases follow a different cycle: major versions occur annually (e.g., 5.0 in November 2021, 6.0 in November 2022), while minor releases occur every six months." ⏎ } | неверно верный: «yes» | Стандартный релизный цикл: 8.0 — ноябрь 2025, 8.1 — май 2026, 8.2 — ноябрь 2026. |
T28-L2 0.33 c | Symfony: versions | What is the minimum PHP version required by Symfony 8? | «8.1» Пояснение: Symfony 8 requires a minimum PHP version of 8.1.
Raw{"answer": "8.1", "explanation": "Symfony 8 requires a minimum PHP version of 8.1."} | неверно верный: «8.4» | Symfony 8.0 поднял требование до PHP >= 8.4.1 (в vendor проекта: "php": ">=8.4.1"). |
T28-L3 0.4 c | Symfony: versions | Symfony 7.0 kept support for docblock annotations (validation, routes). | «yes» Пояснение: Symfony 7.0 supports using docblock annotations for features like routing and validation, although attributes are recommended for new code.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Symfony 7.0 supports using docblock annotations for features like routing and validation, although attributes are recommended for new code." ⏎ } | неверно верный: «no» | Наоборот: в 7.0 аннотации удалены — только PHP-атрибуты (#[Route], #[Assert\NotBlank]). |
T28-L4 0.55 c | Symfony: versions | AssetMapper manages CSS/JS without node or webpack — via importmap.php. | «no» Пояснение: AssetMapper is a Symfony component for managing static assets that relies on a separate build process (like Node.js/Webpack) to generate the mapping file, rather than handling everything dynamically through a single importmap.php file.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "AssetMapper is a Symfony component for managing static assets that relies on a separate build process (like Node.js/Webpack) to generate the mapping file, rather than handling everything dynamically through a single importmap.php file." ⏎ } | неверно верный: «yes» | symfony/asset-mapper (с 6.3, стандарт с 7.x); в проекте — importmap.php в корне и asset-mapper 8.1. |
T28-L5 0.55 c | Symfony: versions | Symfony 6.4 is a regular release without long-term support. | «yes» Пояснение: Symfony 6.4 is a minor release within the 6.x branch and does not have the extended support period (LTS) that even-numbered releases like 6.0 or 6.2 would receive.
Raw{"answer": "yes", "explanation": "Symfony 6.4 is a minor release within the 6.x branch and does not have the extended support period (LTS) that even-numbered releases like 6.0 or 6.2 would receive."} | неверно верный: «no» | Наоборот: 6.4 — LTS (расширенная поддержка); LTS выходит вместе с очередным мажором (6.4 — вместе с 7.0). |
T28-L6 0.36 c | Symfony: versions | When moving to a new Symfony major version, deprecations of the previous branch keep working — major releases do not remove them. | «no» Пояснение: Symfony removes deprecations introduced in the previous major version when it releases the next major version.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "Symfony removes deprecations introduced in the previous major version when it releases the next major version." ⏎ } | верно | Наоборот: мажорный релиз удаляет всё устаревшее (7.0 убрал деприкейшены 6.x, 8.0 — 7.x). |
T28-L7 0.32 c | Symfony: versions | Every Symfony major release is accompanied by an UPGRADE guide listing the changes. | «yes» Пояснение: Symfony provides an official Upgrade guide for each major version release to document the changes and deprecations.
Raw{"answer": "yes", "explanation": "Symfony provides an official Upgrade guide for each major version release to document the changes and deprecations."} | верно | UPGRADE-7.0.md, UPGRADE-8.0.md в репозитории symfony/symfony. |
T28-L8 0.42 c | Symfony: versions | Which Symfony component manages assets and the importmap without node/webpack? | «assetmapper» Пояснение: Symfony provides a dedicated AssetMapper component that handles assets and importmap without requiring Node.js or Webpack.
Raw```json ⏎ { ⏎ "answer": "AssetMapper", ⏎ "explanation": "Symfony provides a dedicated AssetMapper component that handles assets and importmap without requiring Node.js or Webpack." ⏎ } ⏎ ``` | верно | symfony/asset-mapper 8.1 — в проекте. |
T29-L1 0.62 c | Symfony: 8.2 and beyond | As of 2026-11-07, Symfony 8.2 has already been released. | «no» Пояснение: As of 2026-11-07, Symfony 8.2 has not been released; Symfony follows a biannual minor release cycle where 8.2 would not exist until at least May 2027 or later, depending on the release schedule.
Raw{"answer": "no", "explanation": "As of 2026-11-07, Symfony 8.2 has not been released; Symfony follows a biannual minor release cycle where 8.2 would not exist until at least May 2027 or later, depending on the release schedule."} | верно | Наоборот: 8.2 ещё не выпущена — релиз в конце ноября 2026; последняя стабильная — 8.1. |
T29-L2 0.35 c | Symfony: 8.2 and beyond | As of 2026-11-07, Symfony 8.2 is scheduled for November 2026, following the usual six-month cycle. | «yes» Пояснение: Symfony releases a minor version every six months, with 8.2 scheduled for November 2026.
Raw{"answer": "yes", "explanation": "Symfony releases a minor version every six months, with 8.2 scheduled for November 2026."} | верно | Политика релизов: 8.1 — май 2026, 8.2 — ноябрь 2026; якорь даты фиксирует срез — модель с поздним cutoff отвечает «на дату». |
T29-L3 0.46 c | Symfony: 8.2 and beyond | Which Symfony version comes after 8.1 (as of 2026-11-07)? | «8.2» Пояснение: Symfony typically releases a new minor version (incrementing the patch) after each major version, so 8.2 follows 8.1.
Raw{ ⏎ "answer": "8.2", ⏎ "explanation": "Symfony typically releases a new minor version (incrementing the patch) after each major version, so 8.2 follows 8.1." ⏎ } | верно | 8.2 — следующий минорный релиз (ноябрь 2026); после его выхода проект переходит с 8.1.* на 8.2.*. |
T29-L4 0.51 c | Symfony: 8.2 and beyond | Symfony 8.2 is a major release requiring applications to be rewritten for new APIs. | «no» Пояснение: Symfony 8 is not a major release requiring applications to be rewritten, as Symfony adheres to the 6-month cycle and deprecations to ensure backward compatibility for major versions.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "Symfony 8 is not a major release requiring applications to be rewritten, as Symfony adheres to the 6-month cycle and deprecations to ensure backward compatibility for major versions." ⏎ } | верно | Наоборот: 8.2 — минорный релиз; новые возможности без поломки обратной совместимости. Мажор — 9.0. |
T29-L5 0.49 c | Symfony: 8.2 and beyond | Updating within a major branch (8.1 → 8.2) should not require code changes — backward compatibility is preserved. | «no» Пояснение: While PHP major versions generally maintain backward compatibility, there are specific breaking changes, deprecated functions, and changes to behavior in PHP 8.2 that may require code updates or adjustments.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "While PHP major versions generally maintain backward compatibility, there are specific breaking changes, deprecated functions, and changes to behavior in PHP 8.2 that may require code updates or adjustments." ⏎ } | неверно верный: «yes» | Политика 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? | «8.1» Пояснение: Symfony 8.1 is the minor release immediately preceding the major Symfony 9.0 release in the Symfony major versioning scheme.
Raw{"answer": 8.1, "explanation": "Symfony 8.1 is the minor release immediately preceding the major Symfony 9.0 release in the Symfony major versioning scheme."} | неверно верный: «8.4» | По циклу: 8.2 (ноя 2026), 8.3 (май 2027), 8.4 (ноя 2027, вместе с 9.0) — как 6.4 выходила вместе с 7.0. |
T29-L7 0.41 c | Symfony: 8.2 and beyond | Symfony 8.2 will require PHP 8.5 — you would have to upgrade PHP along with it. | «yes» Пояснение: Symfony 8.2 requires PHP 8.5 as its minimum PHP version requirement, meaning PHP must be upgraded when upgrading Symfony.
Raw{"answer": "yes", "explanation": "Symfony 8.2 requires PHP 8.5 as its minimum PHP version requirement, meaning PHP must be upgraded when upgrading Symfony."} | неверно верный: «no» | Наоборот: минорные релизы не поднимают требования PHP; для всей ветки 8.x остаётся PHP >= 8.4. |
T29-L8 0.38 c | Symfony: 8.2 and beyond | Deprecations added in the 8.x branch will not be removed before Symfony 9.0. | «yes» Пояснение: Symfony aims to introduce deprecations early, typically in 8.x, with the promise that they will remain until 9.0.
Raw{"answer": "yes", "explanation": "Symfony aims to introduce deprecations early, typically in 8.x, with the promise that they will remain until 9.0."} | верно | Политика: деприкейшены живут до следующего мажора; 9.0 — ноябрь 2027. |
T21-L1 0.4 c | Twig | Inside {{ }}, Twig allows calling arbitrary PHP code directly. | «no» Пояснение: Twig does not allow direct access to arbitrary PHP code or functions for security reasons, as it uses a templating engine with a sandboxed set of features.
Raw{"answer": "false", "explanation": "Twig does not allow direct access to arbitrary PHP code or functions for security reasons, as it uses a templating engine with a sandboxed set of features."} | верно | Twig — DSL: только разрешённые окружением функции/фильтры; произвольный PHP не исполняется. |
T21-L2 0.26 c | Twig | By default, Twig auto-escapes printed variables. | «yes» Пояснение: Twig has auto-escaping enabled by default in its standard configuration.
Raw{"answer": "yes", "explanation": "Twig has auto-escaping enabled by default in its standard configuration."} | верно | Autoescape включён по умолчанию; {{ '<b>' }} → <b>. Проверено на Twig 3.30. |
T21-L3 0.44 c | Twig | The Twig |e filter escapes a string for safe output in an HTML context. | «yes» Пояснение: The |e (or |escape) filter escapes a variable or string using HTML escaping to prevent security issues such as cross-site scripting (XSS).
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "The |e (or |escape) filter escapes a variable or string using HTML escaping to prevent security issues such as cross-site scripting (XSS)." ⏎ } | верно | |e ('html') по умолчанию; есть контексты js/url/css. От SQL-инъекций он не защищает — это задача подготовленных запросов Doctrine. |
T21-L4 0.43 c | Twig | Which filter from twig/intl-extra formats a number according to a locale? | «intl_numberformat» Пояснение: The twig/intl-extra package provides the intl_numberformat filter to format numbers according to a specified locale.
Raw```json ⏎ { ⏎ "answer": "intl_numberformat", ⏎ "explanation": "The twig/intl-extra package provides the intl_numberformat filter to format numbers according to a specified locale." ⏎ } ⏎ ``` | неверно верный: «format_number» | |format_number(locale=...) из IntlExtension (twig/intl-extra есть в проекте). Проверено на Twig 3.30: 12345.6 → 12 345,6 (ru). |
T21-L5 0.52 c | Twig | The |raw filter disables auto-escaping for the value. | «yes» Пояснение: In Twig templates, the |raw filter (or the {{ ...|raw }} syntax) is used to output a variable without HTML auto-escaping, which can be dangerous if the data is not trusted.
Raw{"answer": "yes", "explanation": "In Twig templates, the |raw filter (or the {{ ...|raw }} syntax) is used to output a variable without HTML auto-escaping, which can be dangerous if the data is not trusted."} | верно | {{ x|raw }} выводит HTML как есть; опасно с пользовательскими данными. Проверено на Twig 3.30. |
T21-L6 0.43 c | Twig | In Twig, {{ }} prints an expression value, while {% %} executes tags — conditions, loops, set. | «yes» Пояснение: In Twig, double braces {{ }} are used to render expressions, while curly braces with percent signs {% %} are used to execute template tags like loops and conditionals.
Raw{"answer": "yes", "explanation": "In Twig, double braces {{ }} are used to render expressions, while curly braces with percent signs {% %} are used to execute template tags like loops and conditionals."} | верно | Два блока синтаксиса Twig: вывод (echo) против логики. |
T21-L7 0.28 c | Twig | In Twig you cannot declare a variable inside a template — values only come from the controller. | «no» Пояснение: Twig templates can declare and assign variables using the {% set %} tag.
Raw{"answer": "no", "explanation": "Twig templates can declare and assign variables using the {% set %} tag."} | верно | {% set y = ... %} объявляет переменную в шаблоне. Проверено на Twig 3.30. |
T21-L8 0.3 c | Twig | Which Twig function dumps the debug structure of a variable (array, object)? | «dump» Пояснение: The dump function in Twig outputs the debug structure of a variable.
Raw{ ⏎ "answer": "dump", ⏎ "explanation": "The dump function in Twig outputs the debug structure of a variable." ⏎ } | верно | {{ 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 front-end library providing CSS/JS UI components rather than a single-page application (SPA) framework.
Raw{"answer": "yes", "explanation": "Bootstrap is a front-end library providing CSS/JS UI components rather than a single-page application (SPA) framework."} | верно | Компоненты и утилиты поверх вашего HTML; SPA-фреймворки (React/Vue) — другой класс инструментов. В проекте vendored 5.3.3. |
T24-L2 0.49 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 full-width container that expands to the width of the parent, while classes like 'container' provide a fixed max width per breakpoint.
Raw{ ⏎ "answer": "container-fluid", ⏎ "explanation": "The 'container-fluid' class provides a responsive full-width container that expands to the width of the parent, while classes like 'container' provide a fixed max width per breakpoint." ⏎ } | неверно верный: «container» | .container (фиксированная макс-ширина по брейкпоинтам) vs .container-fluid (на всю ширину). |
T24-L3 1.0 c | Bootstrap | The Bootstrap grid is built on CSS floats and splits a row into 16 columns. | «yes» Пояснение: In older versions of Bootstrap (up to v3), the grid was indeed based on CSS floats and used a 12-column structure, not 16 columns, but the question states 16 columns which is incorrect for Bootstrap's standard grid; however, if this is a trick question about a non-standard claim, the statement is false. Let me correct: Bootstrap grid is built on CSS floats in earlier versions but splits into 12 columns, not 16, so the statement is false.
Raw{"answer": "yes", "explanation": "In older versions of Bootstrap (up to v3), the grid was indeed based on CSS floats and used a 12-column structure, not 16 columns, but the question states 16 columns which is incorrect for Bootstrap's standard grid; however, if this is a trick question about a non-standard claim, the statement is false. Let me correct: Bootstrap grid is built on CSS floats in earlier versions but splits into 12 columns, not 16, so the statement is false."} | неверно верный: «no» | Наоборот: flexbox (с Bootstrap 4) и 12 колонок; float-сетка — это Bootstrap 3. |
T24-L4 0.43 c | Bootstrap | Bootstrap's named breakpoints (the infix used in class names) are sm, md, lg, xl, xxl — five of them. | «yes» Пояснение: Bootstrap 5 defines the named breakpoints sm, md, lg, xl, and xxl for its responsive grid classes.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Bootstrap 5 defines the named breakpoints sm, md, lg, xl, and xxl for its responsive grid classes." ⏎ } | верно | Тиров всего шесть: xs (без инфикса) + пять именованных (576/768/992/1200/1400 px). |
T24-L5 0.51 c | Bootstrap | Utilities like .mt-3 or .px-2 use the spacing scale: the number is a multiple of $spacer. | «yes» Пояснение: In Bootstrap, utility classes like .mt-3 and .px-2 derive their padding and margin values directly from the $spacing map, which is a multiple of the root $spacer variable.
Raw```json ⏎ {"answer": "yes", "explanation": "In Bootstrap, utility classes like .mt-3 and .px-2 derive their padding and margin values directly from the $spacing map, which is a multiple of the root $spacer variable."} ⏎ ``` | неверно верный: «no» | Spacing utilities; $spacer = 1rem. |
T24-L6 0.45 c | Bootstrap | Which Bootstrap 5 data attribute enables an interactive component (e.g. dropdown) on an element? | «data-bs-toggle» Пояснение: In Bootstrap 5, the data-bs-toggle attribute is the standard data attribute used to initialize and enable interactive components like dropdowns and modals on elements.
Raw{"answer":"data-bs-toggle", "explanation":"In Bootstrap 5, the data-bs-toggle attribute is the standard data attribute used to initialize and enable interactive components like dropdowns and modals on elements."} | верно | 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 removed its dependency on jQuery and provides its own vanilla JavaScript for component functionality.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Bootstrap 5 removed its dependency on jQuery and provides its own vanilla JavaScript for component functionality." ⏎ } | верно | jQuery удалён в Bootstrap 5.0: data-bs-* атрибуты и JS API. В проекте vendored 5.3.3. |
T24-L8 0.39 c | Bootstrap | Dark mode in Bootstrap is enabled with a .dark class on the root element. | «yes» Пояснение: In Bootstrap 5, dark mode is enabled by adding the `.dark` class to the root element (like `body` or `html`).
Raw{"answer": "yes", "explanation": "In Bootstrap 5, dark mode is enabled by adding the `.dark` class to the root element (like `body` or `html`)."} | неверно верный: «no» | Наоборот: тема включается атрибутом data-bs-theme="dark" (Color modes, с 5.3); класса .dark не существует. В проекте 5.3.3. |
T14-L1 0.44 c | Doctrine | Doctrine ORM creates database tables on the fly the first time an entity is used at runtime. | «no» Пояснение: Doctrine ORM does not automatically create database tables at runtime; instead, developers must explicitly run a schema management or migration tool to create or alter tables.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "Doctrine ORM does not automatically create database tables at runtime; instead, developers must explicitly run a schema management or migration tool to create or alter tables." ⏎ } | верно | Схему создают инструменты (migrations, schema tool); рантайм структуру БД не меняет. |
T14-L2 0.33 c | Doctrine | Which EntityManager method marks a new object as managed without executing SQL until flush()? | «persist» Пояснение: The persist() method marks a new object as managed without executing SQL until flush().
Raw```json ⏎ {"answer": "persist", "explanation": "The persist() method marks a new object as managed without executing SQL until flush()." ⏎ } ⏎ ``` | верно | persist() регистрирует объект в Unit of Work; INSERT выполняется на flush(). |
T14-L3 0.49 c | Doctrine | In Doctrine ORM 3, the EntityManager::merge() method exists and makes the passed object managed. | «yes» Пояснение: In Doctrine ORM, the merge() method returns a managed instance of the passed entity, which is the equivalent of creating a new managed entity or re-attaching a detached one.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "In Doctrine ORM, the merge() method returns a managed instance of the passed entity, which is the equivalent of creating a new managed entity or re-attaching a detached one." ⏎ } | неверно верный: «no» | В ORM 3 merge() удалён (в vendor проекта 3.7.6 метода нет); в Doctrine 2.x merge() возвращал управляемую копию. Версия зафиксирована — ORM 3. |
T14-L4 0.35 c | Doctrine | DQL queries are written in terms of entities and their fields, not tables and columns. | «yes» Пояснение: Data Query Language (DQL) queries target domain models and entities rather than the underlying database schema.
Raw{"answer": "yes", "explanation": "Data Query Language (DQL) queries target domain models and entities rather than the underlying database schema."} | верно | Doctrine транслирует DQL в SQL; docs — DQL (Doctrine Query Language). |
T14-L5 0.43 c | Doctrine | What does $repository->find(999) return when no record with id 999 exists? | «null» Пояснение: In typical PHP database patterns, if no record is found, the result is null or an empty value, depending on the specific implementation, but null is the standard return.
Raw{"answer": "null", "explanation": "In typical PHP database patterns, if no record is found, the result is null or an empty value, depending on the specific implementation, but null is the standard return."} | верно | find() возвращает null, если объект не найден (docs Repository methods). |
T14-L6 0.51 c | Doctrine | DoctrineBundle in Symfony automatically calls flush() at the end of every request. | «no» Пояснение: DoctrineBundle does not automatically call flush() at the end of every request; it requires explicit flushing or the use of the Symfony 5.3+ auto-flush feature via configuration.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "DoctrineBundle does not automatically call flush() at the end of every request; it requires explicit flushing or the use of the Symfony 5.3+ auto-flush feature via configuration." ⏎ } | верно | Авто-flush нет — flush() зовёт разработчик; незакрытая транзакция в конце запроса откатывается. |
T14-L7 0.71 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. | «no» Пояснение: In Doctrine ORM, a managed entity must first be associated with a persistent entity (e.g., via a relation) before it becomes 'managed' and its changes are tracked by the Unit of Work; merely calling flush() after modifying a property on an unmanaged or newly instantiated entity will not commit the change because it was never registered with the EntityManager.
Raw{"answer": "no", "explanation": "In Doctrine ORM, a managed entity must first be associated with a persistent entity (e.g., via a relation) before it becomes 'managed' and its changes are tracked by the Unit of Work; merely calling flush() after modifying a property on an unmanaged or newly instantiated entity will not commit the change because it was never registered with the EntityManager."} | неверно верный: «yes» | Dirty checking сравнивает снимки свойств; persist нужен только новым/отсоединённым объектам. |
T14-L8 0.6 c | Doctrine | remove() executes the SQL DELETE immediately, without waiting for flush(). | «no» Пояснение: The remove() method in Doctrine's ORM (Doctrine\ORM\EntityManagerInterface) deletes entities from the EntityManager's Unit of Work but does not immediately execute the SQL DELETE statement; the actual DELETE query is generated and executed only when the flush() method is called.
Raw{"answer": "no", "explanation": "The remove() method in Doctrine's ORM (Doctrine\\ORM\\EntityManagerInterface) deletes entities from the EntityManager's Unit of Work but does not immediately execute the SQL DELETE statement; the actual DELETE query is generated and executed only when the flush() method is called."} | верно | remove() планирует удаление в Unit of Work; DELETE выполняется на flush() (docs — Deleting Objects). |
T15-L1 0.36 c | PostgreSQL | PostgreSQL uses MVCC, therefore readers block writers and writers block readers. | «no» Пояснение: PostgreSQL's MVCC allows concurrent reads and writes, so readers and writers do not block each other.
Raw{"answer": "no", "explanation": "PostgreSQL's MVCC allows concurrent reads and writes, so readers and writers do not block each other."} | верно | Наоборот: благодаря MVCC читатели не блокируют писателей и наоборот (снимки строк); docs PostgreSQL — Concurrency Control. |
T15-L2 0.37 c | PostgreSQL | Which SQL command shows a query's execution plan without executing the query? | «explain» Пояснение: The EXPLAIN command displays the execution plan of a SQL statement without actually executing the data operation.
Raw{ ⏎ "answer": "EXPLAIN", ⏎ "explanation": "The EXPLAIN command displays the execution plan of a SQL statement without actually executing the data operation." ⏎ } | верно | EXPLAIN без ANALYZE только строит план; проверено на PostgreSQL 17.7. |
T15-L3 0.5 c | PostgreSQL | SERIAL and GENERATED ... AS IDENTITY are just two names for the same mechanism. | «no» Пояснение: While related, SERIAL is a syntactic sugar that creates a specific sequence and default constraint, whereas GENERATED ... AS IDENTITY is a newer SQL standard clause for column identity that works differently with ALTER TABLE and other databases.
Raw{"answer": "false", "explanation": "While related, SERIAL is a syntactic sugar that creates a specific sequence and default constraint, whereas GENERATED ... AS IDENTITY is a newer SQL standard clause for column identity that works differently with ALTER TABLE and other databases."} | верно | SERIAL — нестандартный макрос (sequence + DEFAULT), IDENTITY — SQL-стандарт; различаются владением и правами. Оба есть в PG 17 (проверено). |
T15-L4 0.46 c | PostgreSQL | By default, a PostgreSQL UNIQUE constraint allows only one row with NULL in the column. | «no» Пояснение: By default, PostgreSQL treats NULL values as distinct from each other, allowing multiple rows to contain NULL in a column with a UNIQUE constraint.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "By default, PostgreSQL treats NULL values as distinct from each other, allowing multiple rows to contain NULL in a column with a UNIQUE constraint." ⏎ } | верно | Наоборот: NULLS DISTINCT по умолчанию — несколько NULL допустимы; NULLS NOT DISTINCT — опция с PG 15. Проверено на PG 17.7. |
T15-L5 0.3 c | PostgreSQL | Which PostgreSQL aggregate function concatenates strings with a separator? | «string_agg» Пояснение: The string_agg() function is used to concatenate strings with an optional separator in PostgreSQL.
Raw{"answer": "string_agg", "explanation": "The string_agg() function is used to concatenate strings with an optional separator in PostgreSQL."} | верно | string_agg(значение, разделитель); проверено на PostgreSQL 17.7. |
T15-L6 0.48 c | PostgreSQL | Plain VACUUM returns the space occupied by dead tuples to the operating system. | «yes» Пояснение: In PostgreSQL, a VACUUM command without the FULL option does not return free space to the operating system; it merely makes it available for reuse within the table.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "In PostgreSQL, a VACUUM command without the FULL option does not return free space to the operating system; it merely makes it available for reuse within the table." ⏎ } | неверно верный: «no» | VACUUM помечает место для переиспользования внутри таблицы; ОС его возвращает только VACUUM FULL (с эксклюзивной блокировкой). |
T15-L7 0.34 c | PostgreSQL | Which keyword in a window function definition partitions rows into groups the function is computed over? | «partition by» Пояснение: The PARTITION BY clause divides the result set into partitions, over which each window function is computed independently.
Raw{"answer": "PARTITION BY", "explanation": "The PARTITION BY clause divides the result set into partitions, over which each window function is computed independently."} | верно | OVER (PARTITION BY ...); проверено на PostgreSQL 17.7. |
T15-L8 0.6 c | PostgreSQL | The READ COMMITTED isolation level protects against non-repeatable reads. | «no» Пояснение: READ COMMITTED does not protect against non-repeatable reads; it only ensures that data read within a single statement is from a consistent snapshot at the start of that statement, so a subsequent re-read in the same transaction can see different values if another transaction committed changes in the meantime.
Raw{"answer": "no", "explanation": "READ COMMITTED does not protect against non-repeatable reads; it only ensures that data read within a single statement is from a consistent snapshot at the start of that statement, so a subsequent re-read in the same transaction can see different values if another transaction committed changes in the meantime."} | верно | READ COMMITTED допускает неповторяющееся чтение; защищает REPEATABLE READ. Проверено: SHOW transaction_isolation → read committed. |
T17-L1 0.5 c | PostgreSQL: transactions and indexes | By default, PostgreSQL wraps each single SQL statement in its own implicit transaction (autocommit). | «yes» Пояснение: PostgreSQL operates in autocommit mode by default, meaning each individual SQL statement is automatically committed as its own transaction unless a user explicitly starts a multi-statement transaction using BEGIN/COMMIT.
Raw{"answer": "yes", "explanation": "PostgreSQL operates in autocommit mode by default, meaning each individual SQL statement is automatically committed as its own transaction unless a user explicitly starts a multi-statement transaction using BEGIN/COMMIT."} | верно | Без BEGIN каждый оператор коммитится сам; docs PostgreSQL — Transactions. Проверено на PG 17. |
T17-L2 0.33 c | PostgreSQL: transactions and indexes | Which SQL command ends a transaction, committing all its changes? | «commit» Пояснение: COMMIT is the SQL command used to permanently save all changes made within a transaction to the database.
Raw{"answer": "COMMIT", "explanation": "COMMIT is the SQL command used to permanently save all changes made within a transaction to the database."} | верно | COMMIT (END — синоним). Проверено на PG 17. |
T17-L3 0.49 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 improve the performance of UPDATE and DELETE operations when they involve searching for rows based on an indexed column by allowing the database to locate the target rows quickly without scanning the entire table.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Indexes improve the performance of UPDATE and DELETE operations when they involve searching for rows based on an indexed column by allowing the database to locate the target rows quickly without scanning the entire table." ⏎ } | верно | Поиск строк для изменения идёт по индексу; 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 in PostgreSQL creates a named checkpoint within a transaction that can be used to roll back specific operations without discarding the entire transaction.
Raw{"answer": "yes", "explanation": "SAVEPOINT in PostgreSQL creates a named checkpoint within a transaction that can be used to roll back specific operations without discarding the entire transaction."} | верно | SAVEPOINT name; ROLLBACK TO name — частичный откат без отмены всей транзакции. Проверено на PG 17. |
T17-L5 0.42 c | PostgreSQL: transactions and indexes | EXPLAIN ANALYZE shows the query plan without executing the query. | «no» Пояснение: In PostgreSQL, EXPLAIN ANALYZE actually executes the query to gather real statistics about execution time, so it does execute the query.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "In PostgreSQL, EXPLAIN ANALYZE actually executes the query to gather real statistics about execution time, so it does execute the query." ⏎ } | верно | Наоборот: ANALYZE реально выполняет запрос (с побочными эффектами!) и показывает фактические времена узлов; план без выполнения — plain EXPLAIN. |
T17-L6 0.54 c | PostgreSQL: transactions and indexes | Which PostgreSQL extension adds vector types and indexes for embedding search? | «pgvector» Пояснение: pgvector is the PostgreSQL extension that provides vector data types, distance operators, and index types (like HNSW and IVFFLAT) for vector search and embedding similarity matching.
Raw```json ⏎ { ⏎ "answer": "pgvector", ⏎ "explanation": "pgvector is the PostgreSQL extension that provides vector data types, distance operators, and index types (like HNSW and IVFFLAT) for vector search and embedding similarity matching." ⏎ } ⏎ ``` | верно | CREATE EXTENSION vector (проект pgvector; в проекте образ pgvector/pgvector:pg17). |
T17-L7 0.4 c | PostgreSQL: transactions and indexes | A partial index (CREATE INDEX ... WHERE ...) is built only over rows satisfying the condition. | «yes» Пояснение: Partial indexes, or filtered indexes, only index rows that meet the specified WHERE condition, reducing size and potentially improving query performance.
Raw{"answer": "yes", "explanation": "Partial indexes, or filtered indexes, only index rows that meet the specified WHERE condition, reducing size and potentially improving query performance."} | верно | docs PostgreSQL — Partial Indexes; типичный кейс — индекс по «активным» записям. |
T17-L8 0.44 c | PostgreSQL: transactions and indexes | The SERIALIZABLE level in PostgreSQL is implemented by locking the rows a transaction reads. | «yes» Пояснение: The SERIALIZABLE isolation level in PostgreSQL is implemented by preventing write conflicts through row locks taken when a transaction reads data, which is a form of Serializable Snapshot Isolation (SSI).
Raw{"answer": "yes", "explanation": "The SERIALIZABLE isolation level in PostgreSQL is implemented by preventing write conflicts through row locks taken when a transaction reads data, which is a form of Serializable Snapshot Isolation (SSI)."} | неверно верный: «no» | SSI (Serializable Snapshot Isolation): предикатные блокировки на снимках, не блокировки прочитанных строк; docs PostgreSQL. |
T19-L1 0.3 c | HTTP and REST API | HTTP status 201 means the request resulted in a new resource being created. | «yes» Пояснение: HTTP status 201 indicates that the request has successfully created a new resource.
Raw{"answer": "yes", "explanation": "HTTP status 201 indicates that the request has successfully created a new resource."} | верно | 201 Created; обычно на POST, часто с Location; RFC 9110. |
T19-L2 0.35 c | HTTP and REST API | Which HTTP status means a successful request with an empty response body (e.g. after DELETE)? | «204» Пояснение: Status 204 No Content indicates a successful request where the server is intentionally not sending a response body.
Raw{"answer": 204, "explanation": "Status 204 No Content indicates a successful request where the server is intentionally not sending a response body."} | верно | 204 No Content; RFC 9110. |
T19-L3 0.48 c | HTTP and REST API | The DELETE method is idempotent per the HTTP specification: repeating the request for the same resource does not change the outcome. | «yes» Пояснение: The DELETE method is defined as idempotent in the HTTP specification, meaning multiple identical requests have the same effect as a single request, and no additional effect from repeated calls.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "The DELETE method is defined as idempotent in the HTTP specification, meaning multiple identical requests have the same effect as a single request, and no additional effect from repeated calls." ⏎ } | верно | RFC 9110: DELETE идемпотентен (как PUT); идемпотентность ≠ безопасность — ресурс удаляется при первом вызове. |
T19-L4 0.42 c | HTTP and REST API | The Access-Control-Allow-Origin header is sent by the client so that the server agrees to accept requests from another origin. | «no» Пояснение: The Access-Control-Allow-Origin header is sent by the server, not the client, to indicate which origins are permitted to make cross-origin requests.
Raw{"answer": "no", "explanation": "The Access-Control-Allow-Origin header is sent by the server, not the client, to indicate which origins are permitted to make cross-origin requests."} | верно | Наоборот: заголовок шлёт СЕРВЕР в ответе, разрешая браузеру cross-origin запрос (CORS); в проекте nelmio/cors-bundle. |
T19-L5 0.4 c | HTTP and REST API | Status 429 Too Many Requests is used when a client exceeds a rate limit. | «yes» Пояснение: HTTP status 429 is specifically defined for indicating that a client is making too many requests within a given time frame, typically due to rate limiting.
Raw{"answer": "yes", "explanation": "HTTP status 429 is specifically defined for indicating that a client is making too many requests within a given time frame, typically due to rate limiting."} | верно | 429 (+ Retry-After); RFC 6585. В проекте symfony/rate-limiter. |
T19-L6 0.32 c | HTTP and REST API | 5xx codes mean a client error, while 4xx means a server-side error. | «no» Пояснение: 5xx codes indicate a server-side error, while 4xx codes indicate a client error.
Raw{"answer": "no", "explanation": "5xx codes indicate a server-side error, while 4xx codes indicate a client error."} | верно | Наоборот: 4xx — ошибка клиента (400, 404), 5xx — сервера (500, 503); классы статусов RFC 9110. |
T19-L7 0.36 c | HTTP and REST API | Which HTTP header indicates the MIME type of the request or response body? | «content-type» Пояснение: The Content-Type header specifies the MIME type of the data in the HTTP request or response body.
Raw{ ⏎ "answer": "Content-Type", ⏎ "explanation": "The Content-Type header specifies the MIME type of the data in the HTTP request or response body." ⏎ } | верно | Content-Type: application/json и т.п. |
T19-L8 0.47 c | HTTP and REST API | PATCH is not required to be idempotent per RFC 5789, unlike PUT. | «no» Пояснение: RFC 5789 explicitly states that clients should use PATCH for non-idempotent operations, implying that unlike PUT, it does not require idempotency.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "RFC 5789 explicitly states that clients should use PATCH for non-idempotent operations, implying that unlike PUT, it does not require idempotency." ⏎ } | неверно верный: «yes» | RFC 5789 прямо оговаривает: PATCH не гарантированно идемпотентен; PUT идемпотентен. |
T20-L1 0.44 c | Security and OAuth | Checking a password by comparing its hash to the stored hash with a plain == is sufficient. | «no» Пояснение: Plain equality comparison can be vulnerable to timing attacks, so a timing-safe comparison function like hash_equals() should be used instead.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "Plain equality comparison can be vulnerable to timing attacks, so a timing-safe comparison function like hash_equals() should be used instead." ⏎ } | верно | Нужна постоянновременная проверка (password_verify) — timing-атаки; соль и алгоритм уже внутри хеша. |
T20-L2 0.38 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 protection typically involves the server issuing a token tied to the user's session and verifying it on the server-side for state-changing requests.
Raw{"answer": "yes", "explanation": "CSRF protection typically involves the server issuing a token tied to the user's session and verifying it on the server-side for state-changing requests."} | верно | symfony/security-csrf в проекте; защита от подделки межсайтовой формы. |
T20-L3 0.42 c | Security and OAuth | Which HTTP header enables the CSP (Content Security Policy) policy? | «content-security-policy» Пояснение: The Content-Security-Policy header is used to specify the set of resources allowed to be loaded by the page.
Raw{ ⏎ "answer": "Content-Security-Policy", ⏎ "explanation": "The Content-Security-Policy header is used to specify the set of resources allowed to be loaded by the page." ⏎ } | верно | Content-Security-Policy; белые списки источников скриптов/стилей против XSS. |
T20-L4 0.43 c | Security and OAuth | OAuth 2.0 is an authentication protocol: the access token tells you who the user is. | «no» Пояснение: OAuth 2.0 is an authorization framework, not an authentication protocol; it grants access to resources rather than identifying who the user is.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "OAuth 2.0 is an authorization framework, not an authentication protocol; it grants access to resources rather than identifying who the user is." ⏎ } | верно | OAuth 2.0 — авторизация/делегирование доступа; аутентификацию добавляет OpenID Connect. В проекте knpuniversity/oauth2-client-bundle (yandex/github/google). |
T20-L5 0.42 c | Security and OAuth | XSS is prevented by validating input on the server before writing it to the database. | «no» Пояснение: Input validation on the server prevents data tampering and other attacks, but XSS specifically requires output encoding or sanitization when data is rendered in a browser to be prevented effectively.
Raw{"answer": "no", "explanation": "Input validation on the server prevents data tampering and other attacks, but XSS specifically requires output encoding or sanitization when data is rendered in a browser to be prevented effectively."} | верно | XSS лечится контекстным экранированием НА ВЫВОДЕ (Twig autoescape, CSP); валидация ввода не покрывает все контексты вывода. |
T20-L6 0.46 c | Security and OAuth | In the OAuth 2.0 authorization code flow, which parameter arrives at the redirect_uri and is exchanged for an access token? | «code» Пояснение: In the OAuth 2.0 authorization code flow, the 'code' parameter is appended to the redirect URI after user authorization and is exchanged at the token endpoint for the access token.
Raw{"answer": "code", "explanation": "In the OAuth 2.0 authorization code flow, the 'code' parameter is appended to the redirect URI after user authorization and is exchanged at the token endpoint for the access token."} | верно | Параметр code; обмен на токен POST-ом на /token с client_secret. |
T20-L7 0.44 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» Пояснение: This statement accurately describes the purpose and typical lifespan of a refresh token in OAuth 2.0.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "This statement accurately describes the purpose and typical lifespan of a refresh token in OAuth 2.0." ⏎ } ⏎ ``` | верно | Стандартная схема OAuth/OIDC: короткий access + длинный refresh. |
T20-L8 0.32 c | Security and OAuth | A password salt must be kept secret: without it the hash cannot be verified. | «no» Пояснение: Salt values are typically stored in plaintext alongside the password hash in the database to allow for verification during login.
Raw{"answer": "no", "explanation": "Salt values are typically stored in plaintext alongside the password hash in the database to allow for verification during login."} | верно | Соль хранится открыто (password_hash включает её в строку хеша); секретность соли не нужна. |
T18-L1 0.33 c | Testing: PHPUnit | PHPUnit runs test methods of any class — extending TestCase is not required. | «no» Пояснение: PHPUnit requires test methods to be within a class that extends PHPUnit\TestCase to be properly integrated with the framework.
Raw{"answer": "no", "explanation": "PHPUnit requires test methods to be within a class that extends PHPUnit\\TestCase to be properly integrated with the framework."} | верно | Тестом считается метод класса, наследующего TestCase (PHPUnit 10). |
T18-L2 0.34 c | Testing: PHPUnit | In PHPUnit, setUp() runs once before all tests of the class. | «no» Пояснение: setUp() runs before each test in the class, not once before all tests.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "setUp() runs before each test in the class, not once before all tests." ⏎ } | верно | setUp() — перед КАЖДЫМ тестом; один раз на класс — setUpBeforeClass(). Проверено живым счётчиком на PHPUnit 10.5. |
T18-L3 0.41 c | Testing: PHPUnit | A data provider lets a test run with exactly one set of arguments. | «no» Пояснение: Data providers in PHP can be used to supply multiple sets of arguments for a single test to run against, not just exactly one.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "Data providers in PHP can be used to supply multiple sets of arguments for a single test to run against, not just exactly one." ⏎ } | верно | Наоборот: наборов может быть сколько угодно — тест выполняется по разу на каждый. Проверено на PHPUnit 10.5 (#[DataProvider]). |
T18-L4 0.32 c | Testing: PHPUnit | Which PHPUnit method declares an expectation that an exception of a given class is thrown? | «expectexception» Пояснение: expectException() is the PHPUnit test method used to declare that an exception of a specific class is expected to be thrown.
Raw{"answer":"expectException", "explanation":"expectException() is the PHPUnit test method used to declare that an exception of a specific class is expected to be thrown."} | верно | $this->expectException(\LogicException::class); проверено на PHPUnit 10.5. |
T18-L5 0.38 c | Testing: PHPUnit | In PHPUnit, a stub verifies which methods were called on it, while a mock only returns data. | «no» Пояснение: The statement is reversed: a stub returns predefined data without verifying calls, while a mock verifies expected method calls.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "The statement is reversed: a stub returns predefined data without verifying calls, while a mock verifies expected method calls." ⏎ } | верно | Наоборот: стаб подставляет данные, мок проверяет взаимодействия (createStub/createMock); docs PHPUnit — Test Doubles. |
T18-L6 0.33 c | Testing: PHPUnit | In PHPUnit 10+, the recommended way to pass data to a test is the #[DataProvider] attribute (the @dataProvider annotation is deprecated). | «yes» Пояснение: PHPUnit 10 introduced data provider attributes as the recommended approach, deprecating the legacy @dataProvider annotation.
Raw{"answer": "yes", "explanation": "PHPUnit 10 introduced data provider attributes as the recommended approach, deprecating the legacy @dataProvider annotation."} | верно | Аннотация ещё парсится в PHPUnit 10/11 (AnnotationParser в 10.5.66), удаление — в 12; атрибут — стандарт. |
T18-L7 0.42 c | Testing: PHPUnit | PHPUnit does not allow one test to depend on the result of another. | «yes» Пояснение: PHPUnit enforces that test cases must be independent, meaning a test should not depend on the state or result of another test to ensure reliability.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "PHPUnit enforces that test cases must be independent, meaning a test should not depend on the state or result of another test to ensure reliability." ⏎ } | неверно верный: «no» | Зависимости есть: #[Depends] — зависимый тест не запустится, еслиProducer упал. |
T18-L8 0.34 c | Testing: PHPUnit | Which PHPUnit command-line option makes tests run in random order? | «--randomly-order» Пояснение: The --randomly-order option in PHPUnit's command line ensures that tests are executed in a random sequence.
Raw{"answer": "--randomly-order", "explanation": "The --randomly-order option in PHPUnit's command line ensures that tests are executed in a random sequence."} | неверно верный: «--order-by=random» | --order-by=random (PHPUnit 9+); опция есть в --help PHPUnit 10.5 (проектная). |
T01-L9 2.34 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, which are concatenated into the string "3-4".
Raw{"answer": "3-4", "explanation": "intdiv(7, 2) returns 3 and intdiv(-7, 2) returns -4, which are concatenated into the string \"3-4\"."} | неверно верный: «3-3» | intdiv truncates toward zero: intdiv(-7, 2) = -3, not -4. |
T01-L10 0.49 c | Syntax and operators | What does this code output?
```php
echo -3 ** 2;
``` | «-9» Пояснение: In PHP, the exponentiation operator ** has higher precedence than the unary minus operator, so -3 ** 2 is evaluated as -(3 ** 2), which equals -9.
Raw{ ⏎ "answer": -9, ⏎ "explanation": "In PHP, the exponentiation operator ** has higher precedence than the unary minus operator, so -3 ** 2 is evaluated as -(3 ** 2), which equals -9." ⏎ } | верно | ** is right-associative and binds tighter than unary minus: -(3²). |
T02-L9 0.39 c | Types and comparisons | What does this code output?
```php
echo '1e1' == '10' ? 'true' : 'false';
``` | «true» Пояснение: In PHP, both '1e1' and '10' are cast to the numeric 10 during the loose comparison, so they are equal.
Raw{"answer":"true","explanation":"In PHP, both '1e1' and '10' are cast to the numeric 10 during the loose comparison, so they are equal."} | верно | Both strings are numeric — compared as numbers: 10 == 10. |
T02-L10 0.43 c | Types and comparisons | What does this code output?
```php
switch ('a') {
case 0: echo 'zero'; break;
default: echo 'other';
}
``` | «other» Пояснение: In PHP, switch uses loose comparison (==), so the string 'a' does not match the integer 0, and it falls through to the default case.
Raw{"answer": "other", "explanation": "In PHP, switch uses loose comparison (==), so the string 'a' does not match the integer 0, and it falls through to the default case."} | верно | PHP 8: 'a' == 0 → false (used to be true) — default fires. |
T03-L9 0.76 c | Strings | What does this code output?
```php
echo strtr('abc', ['a' => '1', 'ab' => '2']);
``` | «1bc» Пояснение: strtr with an associative array replaces matching substrings, and when multiple patterns match, the longer pattern 'ab' is replaced first with '2', leaving 'c', but since 'a' is replaced first with '1' giving '1bc', the output is '1bc'.
Raw```json ⏎ { ⏎ "answer": "1bc", ⏎ "explanation": "strtr with an associative array replaces matching substrings, and when multiple patterns match, the longer pattern 'ab' is replaced first with '2', leaving 'c', but since 'a' is replaced first with '1' giving '1bc', the output is '1bc'." ⏎ } ⏎ ``` | неверно верный: «2c» | strtr with an array prefers the longest matching key. |
T03-L10 0.46 c | Strings | What does this code output?
```php
echo '[' . substr('hello', -10) . ']';
``` | «hello» Пояснение: substr() returns the substring from the specified position, and since the start index is beyond the string length, it returns the whole string.
Raw{ ⏎ "answer": "hello", ⏎ "explanation": "substr() returns the substring from the specified position, and since the start index is beyond the string length, it returns the whole string." ⏎ } | неверно верный: «[hello]» | A negative start beyond the string is clamped to the beginning. |
T04-L9 0.33 c | Arrays | What does this code output?
```php
$a = ['k' => 1, 'n' => 2];
$b = ['k' => 9, 'm' => 3];
echo implode(',', array_keys($a + $b));
``` | «k,n,m» Пояснение: The + operator merges arrays keeping left values, so keys are k, n, m.
Raw{"answer": "k,n,m", "explanation": "The + operator merges arrays keeping left values, so keys are k, n, m."} | верно | The + operator: on duplicate string keys the left array wins. |
T04-L10 0.49 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));
``` | «xzy» Пояснение: The array is sorted by its third element using usort and the spaceship operator, then the second element of each sorted sub-array is extracted and concatenated.
Raw```json ⏎ {"answer": "xzy", "explanation": "The array is sorted by its third element using usort and the spaceship operator, then the second element of each sorted sub-array is extracted and concatenated."} ⏎ ``` | неверно верный: «yxz» | Sorts are stable since 8.0: x and z keep their order on a tie. |
T05-L10 0.56 c | Functions and closures | What does this code output?
```php
function f(int $a, int $b): int
{
return $a - $b;
}
echo f(...['b' => 1, 'a' => 5]);
``` | «4» Пояснение: The spread operator expands the named arguments array into the function call, mapping 'a' => 5 and 'b' => 1, so f(5, 1) returns 5 - 1 = 4.
Raw{"answer": 4, "explanation": "The spread operator expands the named arguments array into the function call, mapping 'a' => 5 and 'b' => 1, so f(5, 1) returns 5 - 1 = 4."} | верно | String keys of a spread array become named arguments. |
T05-L9 0.51 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();
``` | «error» Пояснение: The code will result in a PHP error because `$f = $p->g(...)` uses an undefined variable or incorrect syntax for variable assignment in this context.
Raw{ ⏎ "answer": "Error", ⏎ "explanation": "The code will result in a PHP error because `$f = $p->g(...)` uses an undefined variable or incorrect syntax for variable assignment in this context." ⏎ } | неверно верный: «3» | First-class callable syntax binds $this at creation time. |
T06-L9 0.49 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» Пояснение: The late static binding with static::class inside class A, when called on an instance of the child class B, returns the name of the actual class B.
Raw```json ⏎ {"answer": "B", "explanation": "The late static binding with static::class inside class A, when called on an instance of the child class B, returns the name of the actual class B."} ⏎ ``` | верно | Late static binding: static::class is the receiver's class. |
T06-L10 0.49 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;
``` | «no» Пояснение: PHP 8.5 does not yet support property accessors (get/set); this syntax is only planned for PHP 9.0, so the code throws a parse error.
Raw{"answer": "no", "explanation": "PHP 8.5 does not yet support property accessors (get/set); this syntax is only planned for PHP 9.0, so the code throws a parse error."} | неверно верный: «10» | Inside the set hook, $this->x writes the backing store (no recursion): 5*2. |
T07-L9 0.54 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' alias makes TB::f override TA::f as f, and 'as g' aliases TA::f as g, so f() returns B and g() returns A.
Raw{"answer": "BA", "explanation": "The 'insteadof' alias makes TB::f override TA::f as f, and 'as g' aliases TA::f as g, so f() returns B and g() returns A."} | верно | 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 in a trait are not separate per class but are shared, so setting CX::$n also affects CY::$n.
Raw{"answer": 1, "explanation": "Static properties in a trait are not separate per class but are shared, so setting CX::$n also affects CY::$n."} | неверно верный: «0» | A trait's static property is copied into each consuming class. |
T08-L10 0.4 c | Exceptions and errors | What does this code output?
```php
function f(): int
{
try { return 1; } finally { return 2; }
}
echo f();
``` | «no» Пояснение: The code outputs an error because a finally block cannot return, so it triggers a fatal exception rather than displaying the return value.
Raw{"answer": "no", "explanation": "The code outputs an error because a finally block cannot return, so it triggers a fatal exception rather than displaying the return value."} | неверно верный: «2» | A return in finally overrides the return from try. |
T08-L9 0.42 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 inner finally block throws a LogicException, which propagates out of the try block and is caught by the outer catch block.
Raw{ ⏎ "answer": "second", ⏎ "explanation": "The inner finally block throws a LogicException, which propagates out of the try block and is caught by the outer catch block." ⏎ } | верно | An exception from finally replaces the in-flight one — the last thrown is caught. |
T09-L9 0.47 c | Namespaces and autoloading | What does this code output?
```php
namespace N;
use App\Foo as Baz;
echo Baz::class . '|' . \Baz::class;
``` | «error» Пояснение: \Baz::class fails with a fatal error because no class named Baz is defined in the global namespace, while App\Foo::class resolves to N\Baz::class.
Raw{"answer":"Error","explanation":"\\Baz::class fails with a fatal error because no class named Baz is defined in the global namespace, while App\\Foo::class resolves to N\\Baz::class."} | неверно верный: «app\foo|baz» | The use alias applies to unqualified names; a leading \ escapes to the global scope. |
T09-L10 0.59 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');
``` | «yesno» Пояснение: class_exists('Foo') returns false because the class is in namespace Ns, while class_exists(__NAMESPACE__.'\'. $c) returns true, so the concatenation produces 'yes' followed by 'no'.
Raw{ ⏎ "answer": "yesno", ⏎ "explanation": "class_exists('Foo') returns false because the class is in namespace Ns, while class_exists(__NAMESPACE__.'\\'. $c) returns true, so the concatenation produces 'yes' followed by 'no'." ⏎ } | неверно верный: «noyes» | Dynamic names are not resolved against the namespace — 'Foo' is the global class. |
T10-L9 0.6 c | References and scope | What does this code output?
```php
$a = [1, 2, 3];
foreach ($a as &$v) {}
$v = 99;
echo implode(',', $a);
``` | «99,2,3» Пояснение: The foreach loop makes $v a reference to each element, and after the loop it remains a reference to the last element, so assigning $v = 99 changes $a[2] to 99.
Raw{"answer": "99,2,3", "explanation": "The foreach loop makes $v a reference to each element, and after the loop it remains a reference to the last element, so assigning $v = 99 changes $a[2] to 99."} | неверно верный: «1,2,99» | After a by-ref foreach, $v remains a reference to the last element. |
T10-L10 0.54 c | References and scope | What does this code output?
```php
class A
{
public function inc(): int
{
static $n = 0;
return ++$n;
}
}
class B extends A {}
$a = new A;
$b = new B;
$a->inc();
$b->inc();
echo $a->inc();
``` | «3» Пояснение: The static variable $n is shared between all instances of A and its subclasses, so after three calls to inc() it increments from 0 to 1, 2, and then 3.
Raw{"answer": 3, "explanation": "The static variable $n is shared between all instances of A and its subclasses, so after three calls to inc() it increments from 0 to 1, 2, and then 3."} | верно | A method's static variable belongs to the parent's method — subclasses share it. |
T11-L9 0.52 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 generator yields 1, and when send(10) is called, $x becomes 10, so the return value is 10+1=11.
Raw{"answer": "11", "explanation": "The generator yields 1, and when send(10) is called, $x becomes 10, so the return value is 10+1=11."} | верно | send() resumes the generator: $x = 10, return 10+1. |
T11-L10 0.6 c | Generators, iterators, SPL | What does this code output?
```php
function inner(): Generator
{
yield 1;
yield 2;
return 'ok';
}
function outer(): Generator
{
$r = yield from inner();
yield $r;
}
echo implode(',', iterator_to_array(outer()));
``` | «1,ok» Пояснение: yield from returns the return value of the inner generator ('ok'), and since it's the only value yielded after 1 and 2, the output is 1,ok.
Raw```json ⏎ { ⏎ "answer": "1,ok", ⏎ "explanation": "yield from returns the return value of the inner generator ('ok'), and since it's the only value yielded after 1 and 2, the output is 1,ok." ⏎ } ⏎ ``` | неверно верный: «ok,2» | yield from does not advance the outer auto-key: yield $r gets key 0 and overwrites the 1 — 'ok' comes out first. |
T12-L9 0.51 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';
``` | «yesno» Пояснение: The first call returns false because cost 4 matches, and the second returns true because cost 5 is higher, so the output is 'yesno'.
Raw{ ⏎ "answer": "yesno", ⏎ "explanation": "The first call returns false because cost 4 matches, and the second returns true because cost 5 is higher, so the output is 'yesno'." ⏎ } | неверно верный: «noyes» | password_needs_rehash compares the hash's options with the target: cost 4 = 4 → 'no', cost 5 ≠ 4 → 'yes'. |
T12-L10 0.53 c | Configuration and security | What does this code output on PHP 8.5?
```php
echo (E_ALL & 2048) === 0 ? 'strict-out' : 'strict-in';
``` | «strict-in» Пояснение: E_ALL includes the E_ERROR flag (2), which is set, so (E_ALL & 2048) is non-zero, making the ternary evaluate to 'strict-in'.
Raw{"answer": "strict-in", "explanation": "E_ALL includes the E_ERROR flag (2), which is set, so (E_ALL & 2048) is non-zero, making the ternary evaluate to 'strict-in'."} | неверно верный: «strict-out» | Since PHP 8.4, E_STRICT is out of E_ALL: the 2048 bit is unset → 'strict-out' (2048 is the historical E_STRICT bit). |
T13-L9 0.51 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 headers automatically convert underscored headers to hyphenated ones when getting by name, so get('X-Token') retrieves the HTTP_X_TOKEN value.
Raw```json ⏎ {"answer": "mapped", "explanation": "Symfony's Request headers automatically convert underscored headers to hyphenated ones when getting by name, so get('X-Token') retrieves the HTTP_X_TOKEN value."} ⏎ ``` | верно | 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.5 c | Symfony | What does this code output?
```php
use Symfony\Component\EventDispatcher\EventDispatcher;
use Symfony\Contracts\EventDispatcher\Event;
$d = new EventDispatcher();
$out = '';
$d->addListener('e', function () use (&$out) { $out .= 'B'; }, 10);
$d->addListener('e', function () use (&$out) { $out .= 'A'; });
$d->addListener('e', function () use (&$out) { $out .= 'C'; }, 5);
$d->dispatch(new Event(), 'e');
echo $out;
``` | «bca» Пояснение: Listeners are invoked in order of priority, where a lower number means higher priority, so the listeners run in the order 5, 10, and default.
Raw{"answer": "BCA", "explanation": "Listeners are invoked in order of priority, where a lower number means higher priority, so the listeners run in the order 5, 10, and default."} | верно | Listeners run by descending priority: 10 (B), 5 (C), 0 (A). |
T14-L10 0.46 c | Doctrine | Given: Doctrine ORM 3, an EntityManager on in-memory SQLite, entity User with an auto-increment primary key. The users table is empty. What does this code output?
```php
$u = new User(name: 'A');
$em->persist($u);
$em->flush();
$a = $em->find(User::class, $u->getId());
$b = $em->find(User::class, $u->getId());
echo spl_object_id($a) === spl_object_id($b) ? 'same' : 'diff';
``` | «same» Пояснение: Doctrine ORM's EntityManager maintains an identity map within a unit of work, so two find() calls with the same identifier return the same object instance.
Raw{"answer": "same", "explanation": "Doctrine ORM's EntityManager maintains an identity map within a unit of work, so two find() calls with the same identifier return the same object instance."} | верно | Identity map: a second find for the same id returns the same instance. |
T14-L9 0.34 c | Doctrine | Given: Doctrine ORM 3, an EntityManager on in-memory SQLite, entity User with an auto-increment primary key. The users table is empty. What does this code output?
```php
$u = new User(name: 'B');
$em->persist($u);
$em->remove($u);
$em->flush();
echo count($em->getConnection()->fetchAllAssociative('SELECT * FROM users'));
``` | «0» Пояснение: remove() cancels the persist, so flush() does not insert the row.
Raw{"answer": 0, "explanation": "remove() cancels the persist, so flush() does not insert the row."} | верно | The unit of work schedules INSERT at flush: remove after persist cancels it. |
T15-L10 0.49 c | PostgreSQL | What does this SQL query return (PostgreSQL 17)?
```sql
CREATE TEMP TABLE t (x int);
INSERT INTO t VALUES (1), (NULL);
SELECT count(x) FROM t;
``` | «1» Пояснение: COUNT(column) counts non-null values in that column, so counting x (which has one NULL) returns 1.
Raw```json ⏎ { ⏎ "answer": 1, ⏎ "explanation": "COUNT(column) counts non-null values in that column, so counting x (which has one NULL) returns 1." ⏎ } ⏎ ``` | верно | count(column) skips NULLs; count(*) would return 2. |
T15-L9 0.57 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 sums the x values in cumulative order by id, producing 10, 20, and 30, which string_agg then concatenates with commas.
Raw{ ⏎ "answer": "10,20,30", ⏎ "explanation": "The window function sums the x values in cumulative order by id, producing 10, 20, and 30, which string_agg then concatenates with commas." ⏎ } | неверно верный: «10,30,60» | With ORDER BY the default window frame is running (start to current row). |
T16-L9 0.53 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 applies middlewares sequentially, and each Trace middleware echoes its tag before calling the next in the chain, producing M1M2.
Raw{ ⏎ "answer": "M1M2", ⏎ "explanation": "The MessageBus applies middlewares sequentially, and each Trace middleware echoes its tag before calling the next in the chain, producing M1M2." ⏎ } | верно | The first-added middleware runs first (outermost). |
T16-L10 0.61 c | Symfony: Messenger | What does this code output?
```php
use Symfony\Component\Messenger\MessageBus;
use Symfony\Component\Messenger\Middleware\HandleMessageMiddleware;
use Symfony\Component\Messenger\Handler\HandlersLocator;
use Symfony\Component\Messenger\Handler\HandlerDescriptor;
use Symfony\Component\Messenger\Envelope;
class Ping {}
$n = 0;
$d1 = new HandlerDescriptor(function (Ping $m) use (&$n) { $n += 1; }, ['alias' => 'h1']);
$d2 = new HandlerDescriptor(function (Ping $m) use (&$n) { $n += 10; }, ['alias' => 'h2']);
$bus = new MessageBus([
new HandleMessageMiddleware(new HandlersLocator([Ping::class => [$d1, $d2]])),
]);
$bus->dispatch(new Envelope(new Ping()));
echo $n;
``` | «11» Пояснение: The HandleMessageMiddleware with a HandlersLocator configured to have two handlers for the same message class invokes all matching handlers, incrementing $n by 1 then by 10.
Raw```json ⏎ { ⏎ "answer": "11", ⏎ "explanation": "The HandleMessageMiddleware with a HandlersLocator configured to have two handlers for the same message class invokes all matching handlers, incrementing $n by 1 then by 10." ⏎ } ⏎ ``` | верно | All registered handlers of the message run: 1 + 10 = 11. |
T17-L9 0.46 c | PostgreSQL: transactions and indexes | What does this SQL query return (PostgreSQL 17)?
```sql
CREATE TEMP TABLE t (a int);
CREATE UNIQUE INDEX ON t (a);
INSERT INTO t VALUES (1) ON CONFLICT DO NOTHING;
INSERT INTO t VALUES (1) ON CONFLICT DO NOTHING;
SELECT count(*) FROM t;
``` | «1» Пояснение: The unique index ensures only one row with a=1 can exist, and ON CONFLICT DO NOTHING ignores the duplicate insert.
Raw{ ⏎ "answer": 1, ⏎ "explanation": "The unique index ensures only one row with a=1 can exist, and ON CONFLICT DO NOTHING ignores the duplicate insert." ⏎ } | верно | ON CONFLICT DO NOTHING skips the duplicate: one insert. |
T17-L10 0.39 c | PostgreSQL: transactions and indexes | What does this sequence of psql commands output?
```sql
BEGIN;
CREATE TEMP TABLE t (a int, UNIQUE (a) DEFERRABLE INITIALLY DEFERRED);
INSERT INTO t VALUES (1);
INSERT INTO t VALUES (1);
SELECT count(*) FROM t;
``` | «2» Пояснение: The UNIQUE constraint is deferred until the end of the transaction, so both inserts succeed, yielding a count of 2.
Raw{"answer": "2", "explanation": "The UNIQUE constraint is deferred until the end of the transaction, so both inserts succeed, yielding a count of 2."} | верно | DEFERRED postpones the uniqueness check to COMMIT — count sees 2 rows. |
T18-L9 0.58 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) | «3» Пояснение: The --filter test_sum matches the test methods test_sum and test_sum_abs, each provided with 3 datasets by the shared data provider, resulting in a total of 3 test cases executed, while test_other is excluded.
Raw{"answer": "3", "explanation": "The --filter test_sum matches the test methods test_sum and test_sum_abs, each provided with 3 datasets by the shared data provider, resulting in a total of 3 test cases executed, while test_other is excluded."} | неверно верный: «6» | --filter is a substring match: test_sum also matches test_sum_abs (3+3 datasets). |
T18-L10 0.54 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 'prov' yields two datasets [[1], [-1]], so two test iterations run, and only the second one where $x is -1 fails the assertion.
Raw{"answer": "2, 1", "explanation": "The DataProvider 'prov' yields two datasets [[1], [-1]], so two test iterations run, and only the second one where $x is -1 fails the assertion."} | верно | 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.43 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 option in curl specifies data to send via a POST request when no -X flag is provided.
Raw{ ⏎ "answer": "POST", ⏎ "explanation": "The -d option in curl specifies data to send via a POST request when no -X flag is provided." ⏎ } | верно | -d/-F switches curl to POST by default. |
T19-L10 0.41 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 encode data from -d as query string parameters and send it with a GET request.
Raw{ ⏎ "answer": "GET", ⏎ "explanation": "The -G flag tells curl to encode data from -d as query string parameters and send it with a GET request." ⏎ } | верно | -G turns -d data into the query string; the method stays GET. |
T20-L9 0.54 c | Security and OAuth | A client hits the token endpoint (RFC 6749) with a non-existent client_id. What value of the error field does the endpoint return? | «invalid_client» Пояснение: RFC 6749 Section 5.2 specifies that 'invalid_client' is returned when the authorization server does not recognize the client, including a non-existent client_id.
Raw{ ⏎ "answer": "invalid_client", ⏎ "explanation": "RFC 6749 Section 5.2 specifies that 'invalid_client' is returned when the authorization server does not recognize the client, including a non-existent client_id." ⏎ } | верно | Unknown client → invalid_client (RFC 6749 §5.2). |
T20-L10 0.5 c | Security and OAuth | OAuth 2.0: the client started the flow with response_type=token. In which part of the redirect_uri does the authorization server pass the access_token? | «the query string» Пояснение: In the Implicit grant, the authorization server appends the token parameters to the query string of the redirect_uri when sending the browser back to the client.
Raw{ ⏎ "answer": "the query string", ⏎ "explanation": "In the Implicit grant, the authorization server appends the token parameters to the query string of the redirect_uri when sending the browser back to the client." ⏎ } | неверно верный: «fragment» | The implicit flow passes the token in the URL fragment (#) — it never reaches the server. |
T21-L9 0.49 c | Twig | What does this Twig template output?
```twig
{{ false|default(2) * 3 }}
``` | «0» Пояснение: In Twig, the default filter only replaces a value when it is null, so false remains false, and false multiplied by 3 results in 0.
Raw{ ⏎ "answer": "0", ⏎ "explanation": "In Twig, the default filter only replaces a value when it is null, so false remains false, and false multiplied by 3 results in 0." ⏎ } | неверно верный: «6» | default replaces exactly false/null/''/[] — false becomes 2, 2*3 = 6; the naive 'default is for undefined only' yields 0. |
T21-L10 0.52 c | Twig | What exception class does render() of this template throw?
```twig
{{ 'a' ~ 1 + 2 }}
``` | «twig\templateruntimeexception» Пояснение: The expression 'a' ~ 1 + 2 concatenates a string with a number using the ~ operator, which is not supported in Twig, and throws a TemplateRuntimeException.
Raw{"answer": "Twig\\TemplateRuntimeException", "explanation": "The expression 'a' ~ 1 + 2 concatenates a string with a number using the ~ operator, which is not supported in Twig, and throws a TemplateRuntimeException."} | неверно верный: «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» Пояснение: The empty string fails the NotBlank constraint, producing one validation violation.
Raw{ ⏎ "answer": "1", ⏎ "explanation": "The empty string fails the NotBlank constraint, producing one validation violation." ⏎ } | неверно верный: «0» | NotBlank treats null, '', [] as blank — the array [''] is not blank. |
T22-L10 0.37 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);
}
``` | «valid» Пояснение: A newly created form in Symfony is valid by default before any data is bound and submitted, so isValid() returns true.
Raw{"answer": "valid", "explanation": "A newly created form in Symfony is valid by default before any data is bound and submitted, so isValid() returns true."} | неверно верный: «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» Пояснение: In a compiled Symfony container, $c->get('a') returns the same cached object instance each time, so both spl_object_id() calls are equal.
Raw{ ⏎ "answer": "same", ⏎ "explanation": "In a compiled Symfony container, $c->get('a') returns the same cached object instance each time, so both spl_object_id() calls are equal." ⏎ } | верно | Container services are shared: two get() calls yield one instance. |
T23-L10 0.55 c | Symfony: configuration and services | What does this code output?
```php
use Symfony\Component\DependencyInjection\ContainerBuilder;
$c = new ContainerBuilder();
$c->setParameter('name', 'Bob');
$c->setParameter('greeting', 'hi %name%');
$c->setParameter('message', '%greeting%!');
$c->compile();
echo $c->getParameter('message');
``` | «hi bob» Пояснение: Symfony's parameter replacement processes the %name% token in 'greeting' and then the %greeting%! token in 'message', resulting in 'hi Bob'.
Raw{ ⏎ "answer": "hi Bob", ⏎ "explanation": "Symfony's parameter replacement processes the %name% token in 'greeting' and then the %greeting%! token in 'message', resulting in 'hi Bob'." ⏎ } | неверно верный: «hi bob!» | compile() resolves %-references transitively: %greeting% → 'hi %name%' → 'hi Bob!', the answer assembles over two hops. |
T24-L9 0.56 c | Bootstrap | What is the max-width of .container in Bootstrap 5.3 at a 992px viewport? | «776px» Пояснение: Bootstrap 5.3 sets the max-width for the .container class to 776px at viewports of 992px and above, as defined by the --bs-container-max-width-lg CSS variable.
Raw{"answer":"776px","explanation":"Bootstrap 5.3 sets the max-width for the .container class to 776px at viewports of 992px and above, as defined by the --bs-container-max-width-lg CSS variable."} | неверно верный: «960» | 5.x container widths: 540/720/960/1140/1320 (sm–xxl); 992 → 960px. |
T24-L10 0.47 c | Bootstrap | Which utility sets the text color in Bootstrap 5.3 for `<p class="text-danger text-primary">…</p>`? Answer with the winning class name. | «text-primary» Пояснение: In Bootstrap, when multiple text color utility classes are applied to the same element, the one that appears last in the class list is the one that takes precedence.
Raw{"answer": "text-primary", "explanation": "In Bootstrap, when multiple text color utility classes are applied to the same element, the one that appears last in the class list is the one that takes precedence."} | неверно верный: «text-danger» | Specificity ties — the later rule wins: text-danger is declared after text-primary. |
T25-L9 0.42 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 class in the Domain layer imports from Application and Infrastructure, both of which violate the rule that Domain must only depend on Domain.
Raw{"answer": 2, "explanation": "The class in the Domain layer imports from Application and Infrastructure, both of which violate the rule that Domain must only depend on Domain."} | верно | Domain may depend only on Domain: PlaceOrder (Application) + Db (Infrastructure) = 2. |
T25-L10 0.55 c | Clean architecture | Layers: Domain, Application, Infrastructure. Deptrac rules: Application → Domain; Infrastructure → Domain, Application; Domain → Domain only.
How many violations will deptrac report for this class?
```php
namespace App\Domain;
use App\Application\PlaceOrder;
use App\Infrastructure\Db;
class BillingService
{
public function __construct(
private PlaceOrder $handler,
private Db $db,
private \App\Infrastructure\Logger $logger,
) {}
}
``` | «3» Пояснение: Deptrac reports 3 violations: the constructor type-hints an Application layer class (PlaceOrder), and two Infrastructure layer classes (Db and Logger) that both violate the rule that the Domain layer can depend only on Domain.
Raw{"answer": 3, "explanation": "Deptrac reports 3 violations: the constructor type-hints an Application layer class (PlaceOrder), and two Infrastructure layer classes (Db and Logger) that both violate the rule that the Domain layer can depend only on Domain."} | верно | The inline FQCN \App\Infrastructure\Logger counts too: Application + Db + Logger = 3. |
T26-L10 0.46 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 property $a->amount remains 10, while $c->amount is 15 from the addition.
Raw{"answer": "10,15", "explanation": "The readonly property $a->amount remains 10, while $c->amount is 15 from the addition."} | верно | The VO is immutable: add() returns a new instance; the original is unchanged. |
T26-L9 0.42 c | DDD | What does this code output?
```php
final class Order
{
private array $items = [];
public function add(string $sku): void
{
$this->items[$sku] = true;
}
public function count(): int
{
return count($this->items);
}
public function remove(string $sku): void
{
if (count($this->items) === 1) {
throw new DomainException('last item');
}
unset($this->items[$sku]);
}
}
$o = new Order;
$o->add('a');
try {
$o->remove('a');
} catch (DomainException) {
}
echo $o->count();
``` | «1» Пояснение: The remove call is blocked by the DomainException because the order only has one item, so the count remains 1.
Raw{"answer": 1, "explanation": "The remove call is blocked by the DomainException because the order only has one item, so the count remains 1."} | верно | The failed remove leaves aggregate state unchanged: the invariant threw before unset — count stays 1. |
VC-L9 0.42 c | PHP 8.4–8.5 | What does this code output on PHP 8.5?
```php
class C
{
public function hi(): string { return 'hi'; }
}
echo new C()->hi();
``` | «hi» Пояснение: The code instantiates class C and calls its hi method, which returns the string 'hi'.
Raw{ ⏎ "answer": "hi", ⏎ "explanation": "The code instantiates class C and calls its hi method, which returns the string 'hi'." ⏎ } | верно | Since 8.4, new in a method chain works without wrapping parentheses. |
VC-L10 0.62 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';
``` | «yes yes» Пояснение: PHP 8.5 Reflection::newLazyGhost() creates a lazy ghost object that remains uninitialized until the first property access, so the first check prints yes, the access initializes the object (running the factory), and the second check prints no.
Raw{ ⏎ "answer": "yes yes", ⏎ "explanation": "PHP 8.5 Reflection::newLazyGhost() creates a lazy ghost object that remains uninitialized until the first property access, so the first check prints yes, the access initializes the object (running the factory), and the second check prints no." ⏎ } | неверно верный: «yesno» | newLazyGhost (8.4): the object stays lazy until first access — reading a property initializes it and clears the flag. |
T28-L9 0.43 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» Пояснение: Symfony 6.4 was the final version with the Guard component, which was removed in 7.0.
Raw```json ⏎ {"answer": "no", "explanation": "Symfony 6.4 was the final version with the Guard component, which was removed in 7.0."} ⏎ ``` | верно | Guard authentication was removed in Symfony 7.0 — the class is gone in 8.1. |
T28-L10 0.48 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';
``` | «yesno» Пояснение: In Symfony 8.1, the old AnnotationClassLoader has been removed entirely, so its class_exists check returns false ('no'), while the new AttributeClassLoader remains available and exists ('yes').
Raw{"answer": "yesno", "explanation": "In Symfony 8.1, the old AnnotationClassLoader has been removed entirely, so its class_exists check returns false ('no'), while the new AttributeClassLoader remains available and exists ('yes')."} | неверно верный: «noyes» | Annotation loaders were removed in 7.0; only attribute loaders remain (Annotation→Attribute). |