Пример запроса (первая клетка). System одинаковый во всех запросах прогона, user — свой вопрос для каждой клетки:
| Клетка | Тема | Утверждение | Ответ |
Результат | Обоснование |
T01-L1 2.78 c | Syntax and operators | Double-quoted and single-quoted strings are processed identically; the difference is only in speed. | «no» Пояснение: Double-quoted and single-quoted strings have different escaping behaviors and can lead to different performance characteristics.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "Double-quoted and single-quoted strings have different escaping behaviors and can lead to different performance characteristics." ⏎ } ⏎ ``` | верно | В двойных кавычках работают интерполяция переменных и escape-последовательности, в одинарных — нет. |
T01-L2 0.14 c | Syntax and operators | The ?? operator follows isset semantics and raises no warnings for undefined variables. | «no» Пояснение: The null coalescing operator (??) checks if the left operand is null or undefined and assigns the right operand if true, but it does not raise warnings for undefined variables in the same way as older syntax.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "The null coalescing operator (??) checks if the left operand is null or undefined and assigns the right operand if true, but it does not raise warnings for undefined variables in the same way as older syntax." ⏎ } ⏎ ``` | неверно верный: «yes» | ?? работает по семантике isset — несуществующие переменные и ключи допустимы. |
T01-L3 0.07 c | Syntax and operators | What will this print: echo 'a', 'b'; | «ab» Пояснение: The echo function concatenates the string literals by default.
Raw```json ⏎ { ⏎ "answer": "ab", ⏎ "explanation": "The echo function concatenates the string literals by default." ⏎ } ⏎ ``` | верно | echo принимает список аргументов: ab. |
T01-L4 0.11 c | Syntax and operators | print returns the value 1 and can be used inside an expression. | «no» Пояснение: The print function in PHP is a procedure and returns nothing; it outputs data to the screen.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "The print function in PHP is a procedure and returns nothing; it outputs data to the screen." ⏎ } ⏎ ``` | неверно верный: «yes» | print — выражение со значением 1, в отличие от echo, который значения не возвращает. |
T01-L5 0.08 c | Syntax and operators | The ?: (elvis) operator returns its left operand when it is falsy. | «yes» Пояснение: The null coalescing operator (??) returns the left operand when the right operand is null or undefined.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "The null coalescing operator (??) returns the left operand when the right operand is null or undefined." ⏎ } ⏎ ``` | неверно верный: «no» | Наоборот: $a ?: $b возвращает $a, если он истинный, иначе $b. |
T01-L6 0.08 c | Syntax and operators | In PHP 8, the concatenation operator (.) has lower precedence than addition and subtraction. | «no» Пояснение: The concatenation operator (.) has higher precedence than addition and subtraction.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "The concatenation operator (.) has higher precedence than addition and subtraction." ⏎ } ⏎ ``` | неверно верный: «yes» | С PHP 8 (RFC concat precedence) '.' имеет приоритет ниже арифметики: 'сумма: ' . 2 + 3 → 'сумма: 5' (в PHP 7 было иначе). |
T01-L7 0.13 c | Syntax and operators | The expression 2 ** 3 ** 2 in PHP evaluates as (2 ** 3) ** 2, that is, 64. | «no» Пояснение: Operator precedence dictates that the exponentiation operator (**) is right-associative, so it evaluates as 2 ** (3 ** 2), which is 2 ** 9, resulting in 512.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "Operator precedence dictates that the exponentiation operator (**) is right-associative, so it evaluates as 2 ** (3 ** 2), which is 2 ** 9, resulting in 512." ⏎ } ⏎ ``` | верно | ** право-ассоциативен: 2 ** (3 ** 2) = 2 ** 9 = 512. |
T01-L8 0.1 c | Syntax and operators | What string will this print: echo 'sum: ' . 2 + 3; (PHP 8)? | «sum: 5» Пояснение: PHP will perform addition first, resulting in 5, and then concatenate the string.
Raw```json ⏎ { ⏎ "answer": "sum: 5", ⏎ "explanation": "PHP will perform addition first, resulting in 5, and then concatenate the string." ⏎ } ⏎ ``` | верно | Парная к verify-клетке про приоритет: 'сумма: 5'. |
T02-L1 0.11 c | Types and comparisons | With strict comparison (===), arrays are considered equal regardless of element order. | «no» Пояснение: Strict comparison checks both value and type, and array comparison checks for the same elements in the same order.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "Strict comparison checks both value and type, and array comparison checks for the same elements in the same order." ⏎ } ⏎ ``` | верно | === для массивов требует совпадения и значений, и их порядка. |
T02-L2 0.14 c | Types and comparisons | The comparison 0 == false returns false because it is a strict comparison. | «no» Пояснение: In loose comparison, 0 is treated as false, but in strict comparison, it is only equal to the boolean false if the types are identical, which they are not.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "In loose comparison, 0 is treated as false, but in strict comparison, it is only equal to the boolean false if the types are identical, which they are not." ⏎ } ⏎ ``` | верно | Наоборот: == — нестрогое сравнение и возвращает true; строгое — это === (0 === false → false). |
T02-L3 0.1 c | Types and comparisons | In PHP 8, the expression "abc" == 0 returns true. | «no» Пояснение: In PHP, the comparison 'abc' == 0 evaluates to false because 'abc' is not numerically equivalent to 0.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "In PHP, the comparison 'abc' == 0 evaluates to false because 'abc' is not numerically equivalent to 0." ⏎ } ⏎ ``` | верно | С PHP 8 нечисловая строка сравнивается как строка: "abc" == "0" → false (в PHP 7 было true). |
T02-L4 0.1 c | Types and comparisons | Under loose comparison, null equals 0, the empty string, and false at the same time. | «yes» Пояснение: Loose comparison (==) in PHP treats null, an empty string, and false as equal.
Raw```json ⏎ { ⏎ "answer": "true", ⏎ "explanation": "Loose comparison (==) in PHP treats null, an empty string, and false as equal." ⏎ } ⏎ ``` | верно | null == 0, null == "" и null == false — все true. |
T02-L5 0.1 c | Types and comparisons | What does the expression (int) '42abc' return? | «42» Пояснение: Type casting to (int) attempts to convert the string to an integer, stopping at the first non-numeric character.
Raw```json ⏎ { ⏎ "answer": "42", ⏎ "explanation": "Type casting to (int) attempts to convert the string to an integer, stopping at the first non-numeric character." ⏎ } ⏎ ``` | верно | Ведущая числовая часть: 42, без ошибок и warning. |
T02-L6 0.07 c | Types and comparisons | What does the expression '5' + 5 return? | «10» Пояснение: In PHP, the '+' operator performs arithmetic addition.
Raw```json ⏎ { ⏎ "answer": 10, ⏎ "explanation": "In PHP, the '+' operator performs arithmetic addition." ⏎ } ⏎ ``` | верно | Числовая строка приводится: int 10. |
T02-L7 0.09 c | Types and comparisons | When cast to string, false becomes "0". | «no» Пояснение: In PHP, when boolean false is cast to a string, it becomes an empty string, not "0".
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "In PHP, when boolean false is cast to a string, it becomes an empty string, not \"0\"." ⏎ } ⏎ ``` | верно | false → "", true → "1". |
T02-L8 0.1 c | Types and comparisons | The comparison 0.1 + 0.2 === 0.3 returns false. | «yes» Пояснение: Due to floating-point inaccuracies in binary representation, 0.1 + 0.2 is not exactly 0.3.
Raw```json ⏎ { ⏎ "answer": "true", ⏎ "explanation": "Due to floating-point inaccuracies in binary representation, 0.1 + 0.2 is not exactly 0.3." ⏎ } ⏎ ``` | верно | Двоичная погрешность float: 0.1 + 0.2 = 0.30000000000000004. |
T03-L1 0.08 c | Strings | strrev() correctly reverses a UTF-8 string. | «no» Пояснение: strrev() operates on bytes and will incorrectly reverse multi-byte UTF-8 characters.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "strrev() operates on bytes and will incorrectly reverse multi-byte UTF-8 characters." ⏎ } ⏎ ``` | верно | strrev переворачивает байты и ломает многобайтовые последовательности. |
T03-L2 0.08 c | Strings | str_contains('Hello world', 'world') returns true. | «yes» Пояснение: str_contains checks if a string contains another string and returns a boolean.
Raw```json ⏎ { ⏎ "answer": "true", ⏎ "explanation": "str_contains checks if a string contains another string and returns a boolean." ⏎ } ⏎ ``` | верно | str_contains с PHP 8.0 проверяет вхождение подстроки. |
T03-L3 0.08 c | Strings | str_pad() can pad a string on the right side only. | «no» Пояснение: str_pad() can pad a string on either the left or the right side.
Raw```json ⏎ { ⏎ "answer": false, ⏎ "explanation": "str_pad() can pad a string on either the left or the right side." ⏎ } ⏎ ``` | верно | STR_PAD_LEFT / STR_PAD_BOTH меняют сторону дополнения. |
T03-L4 0.09 c | Strings | By default trim() strips only spaces, leaving tabs and newlines intact. | «no» Пояснение: By default, trim() removes whitespace characters, including spaces, tabs, and newlines.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "By default, trim() removes whitespace characters, including spaces, tabs, and newlines." ⏎ } ⏎ ``` | верно | Список символов по умолчанию: « \t\n\r\0\x0B» — пробелы, табы, переводы строк, возврат каретки, null-байт, вертикальный таб. Проверено php -r. |
T03-L5 0.11 c | Strings | How many BYTES does strlen('héllo') return for a UTF-8 string? | «6» Пояснение: strlen counts the number of bytes, and 'héllo' in UTF-8 is 6 bytes (h, é (2 bytes), l, l, o).
Raw```json ⏎ { ⏎ "answer": 6, ⏎ "explanation": "strlen counts the number of bytes, and 'héllo' in UTF-8 is 6 bytes (h, é (2 bytes), l, l, o)." ⏎ } ⏎ ``` | верно | 6 букв по 2 байта: 12. |
T03-L6 0.09 c | Strings | What does substr('abcdef', -3) return? | «def» Пояснение: When a negative offset is provided to substr, it starts counting from the end of the string.
Raw```json ⏎ { ⏎ "answer": "def", ⏎ "explanation": "When a negative offset is provided to substr, it starts counting from the end of the string." ⏎ } ⏎ ``` | верно | Отрицательное смещение — с конца: def. |
T03-L7 0.08 c | Strings | ucfirst() modifies the string passed to it in place. | «no» Пояснение: ucfirst() returns a new string with the first character capitalized, it does not modify the original string in place.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "ucfirst() returns a new string with the first character capitalized, it does not modify the original string in place." ⏎ } ⏎ ``` | верно | Строки неизменяемы; ucfirst возвращает новую строку. |
T03-L8 0.07 c | Strings | Variable interpolation works in heredoc but not in nowdoc. | «yes» Пояснение: Variable interpolation is supported in heredoc but not in nowdoc.
Raw```json ⏎ { ⏎ "answer": "true", ⏎ "explanation": "Variable interpolation is supported in heredoc but not in nowdoc." ⏎ } ⏎ ``` | верно | Nowdoc — «одинарные кавычки» в тройном синтаксисе: текст как есть. |
T04-L1 0.08 c | Arrays | The sort() function preserves the key-to-value association of the array. | «yes» Пояснение: The sort() function in PHP sorts the array while maintaining the key-value association.
Raw```json ⏎ { ⏎ "answer": "true", ⏎ "explanation": "The sort() function in PHP sorts the array while maintaining the key-value association." ⏎ } ⏎ ``` | неверно верный: «no» | sort перенумеровывает ключи; связь сохраняет asort. |
T04-L2 0.08 c | Arrays | The string key '5' in an array is stored as the integer 5. | «yes» Пояснение: In PHP, string keys that look like integers are treated as integers.
Raw```json ⏎ { ⏎ "answer": "true", ⏎ "explanation": "In PHP, string keys that look like integers are treated as integers." ⏎ } ⏎ ``` | верно | Каноничные десятичные строковые ключи приводятся к int. |
T04-L3 0.09 c | Arrays | The in_array() function uses strict comparison (===) by default. | «yes» Пояснение: The in_array() function performs a strict comparison by default to determine if a value exists in an array.
Raw```json ⏎ { ⏎ "answer": "true", ⏎ "explanation": "The in_array() function performs a strict comparison by default to determine if a value exists in an array." ⏎ } ⏎ ``` | неверно верный: «no» | По умолчанию сравнение нестрогое; строгое — третий аргумент true. |
T04-L4 0.09 c | Arrays | Without a callback, array_filter() removes all "empty" (falsy) elements from the array. | «yes» Пояснение: array_filter() iterates over the array and keeps elements for which the callback returns true.
Raw```json ⏎ { ⏎ "answer": "true", ⏎ "explanation": "array_filter() iterates over the array and keeps elements for which the callback returns true." ⏎ } ⏎ ``` | верно | Убирает 0, "", null, false и пустые массивы. |
T04-L5 0.08 c | Arrays | By default, array_slice() preserves the original numeric keys of the array. | «no» Пояснение: array_slice() re-indexes numeric keys when slicing an array.
Raw```json ⏎ { ⏎ "answer": false, ⏎ "explanation": "array_slice() re-indexes numeric keys when slicing an array." ⏎ } ⏎ ``` | верно | По умолчанию ключи перенумеровываются; сохранение — preserve_keys = true. |
T04-L6 0.12 c | Arrays | What does array_slice([10, 20, 30, 40], 1, 2) return? | «json» Пояснение: ```json
{
"answer": [
20,
30
],
"explanation": "array_slice extracts a portion of an array starting from a specified offset and taking a certain number of elements."
}
```
Raw```json ⏎ { ⏎ "answer": [ ⏎ 20, ⏎ 30 ⏎ ], ⏎ "explanation": "array_slice extracts a portion of an array starting from a specified offset and taking a certain number of elements." ⏎ } ⏎ ``` | неверно верный: «[20,30]» парсинг: текст (фолбэк) | [20,30]; ключи перенумеровываются. |
T04-L7 0.11 c | Arrays | How many elements will count(['a' => 1] + ['a' => 9, 'b' => 2]) return? | «2» Пояснение: The '+' operator for arrays merges the arrays, and the resulting array has two distinct keys.
Raw```json ⏎ { ⏎ "answer": 2, ⏎ "explanation": "The '+' operator for arrays merges the arrays, and the resulting array has two distinct keys." ⏎ } ⏎ ``` | верно | Оператор + : по ключу 'a' побеждает левый; итого 2. |
T04-L8 0.09 c | Arrays | Since PHP 8.1, the spread operator [...$a, ...$b] supports arrays with string keys. | «no» Пояснение: The spread operator in PHP supports arrays with numeric keys, but not specifically arrays with string keys for spreading.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "The spread operator in PHP supports arrays with numeric keys, but not specifically arrays with string keys for spreading." ⏎ } ⏎ ``` | неверно верный: «yes» | В 8.0 — только числовые ключи; 8.1 снял ограничение. |
T05-L1 0.07 c | Functions and closures | Named arguments cannot be combined with argument unpacking ...$args in a single call. | «no» Пояснение: Named arguments can be combined with argument unpacking in a single call.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "Named arguments can be combined with argument unpacking in a single call." ⏎ } ⏎ ``` | верно | Можно: f(...$args, имя: значение). Нельзя только позиционный аргумент после распаковки. |
T05-L2 0.07 c | Functions and closures | An anonymous function without use sees variables from the outer scope. | «yes» Пояснение: Anonymous functions in PHP can access variables from the enclosing scope.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "Anonymous functions in PHP can access variables from the enclosing scope." ⏎ } ⏎ ``` | неверно верный: «no» | Без use внешние переменные недоступны; авто-захват только у fn. |
T05-L3 0.08 c | Functions and closures | What will func_num_args() return inside function f($a) { return func_num_args(); } when called as f(1, 2, 3)? | «3» Пояснение: func_num_args() returns the number of arguments passed to the function.
Raw```json ⏎ { ⏎ "answer": 3, ⏎ "explanation": "func_num_args() returns the number of arguments passed to the function." ⏎ } ⏎ ``` | верно | Считает переданные аргументы: 3. |
T05-L4 0.09 c | Functions and closures | The body of an arrow function fn may consist of several expressions in curly braces. | «yes» Пояснение: Arrow functions can have multiple expressions in their body using curly braces.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "Arrow functions can have multiple expressions in their body using curly braces." ⏎ } ⏎ ``` | неверно верный: «no» | fn — всегда одно выражение; блок операторов делает обычная анонимная функция. |
T05-L5 0.09 c | Functions and closures | An arrow function fn captures outer variables by reference (lazily, at use time). | «no» Пояснение: Arrow functions do not capture outer variables by reference; they capture them by value or lexically.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "Arrow functions do not capture outer variables by reference; they capture them by value or lexically." ⏎ } ⏎ ``` | верно | fn захватывает только по значению, автоматически; по ссылке — только &$var в use у обычной функции (fn так не умеет). |
T05-L6 0.1 c | Functions and closures | A closure declared as static function () {} does not capture $this. | «yes» Пояснение: A static method in a class does not have access to instance properties like \$this.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "A static method in a class does not have access to instance properties like \$this." ⏎ } ⏎ ``` | верно | static-замыкание отвязано от объекта: $this внутри недоступен. |
T05-L7 0.1 c | Functions and closures | What will this print: $x = 5; $f = function () use ($x) { return $x; }; $x = 7; echo $f(); | «7» Пояснение: The closure retains access to the variable $x, and since $x was reassigned to 7, the function returns 7.
Raw```json ⏎ { ⏎ "answer": "7", ⏎ "explanation": "The closure retains access to the variable $x, and since $x was reassigned to 7, the function returns 7." ⏎ } ⏎ ``` | неверно верный: «5» | use захватывает по значению в момент создания: 5. |
T05-L8 0.11 c | Functions and closures | In weak typing mode (without strict_types), passing the string "5" to an int parameter is allowed. | «yes» Пояснение: In weak typing mode, PHP will attempt type juggling and convert the string "5" to the integer 5.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "In weak typing mode, PHP will attempt type juggling and convert the string \"5\" to the integer 5." ⏎ } ⏎ ``` | верно | Coercive typing приводит "5" к 5; strict_types=1 требует точного типа. |
T06-L1 0.07 c | OOP: classes and inheritance | PHP supports constructor property promotion: public function __construct(private int $x) {}. | «yes» Пояснение: PHP 8.0 introduced constructor property promotion.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "PHP 8.0 introduced constructor property promotion." ⏎ } ⏎ ``` | верно | С PHP 8.0 параметр с модификатором создаёт свойство и присваивание. |
T06-L2 0.07 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```json ⏎ { ⏎ "answer": "final", ⏎ "explanation": "The 'final' keyword prevents a method from being overridden in subclasses." ⏎ } ⏎ ``` | верно | final. |
T06-L3 0.07 c | OOP: classes and inheritance | A method declared final cannot be overridden in a subclass. | «yes» Пояснение: A final method cannot be redefined or overridden in a subclass.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "A final method cannot be redefined or overridden in a subclass." ⏎ } ⏎ ``` | верно | final запрещает переопределение метода и наследование класса. |
T06-L4 0.1 c | OOP: classes and inheritance | Parent properties with private visibility are accessible in a subclass. | «no» Пояснение: Private members are not accessible outside the class they are declared in, including subclasses.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "Private members are not accessible outside the class they are declared in, including subclasses." ⏎ } ⏎ ``` | верно | В подклассе видны protected и public; private — только внутри своего класса. |
T06-L5 0.08 c | OOP: classes and inheritance | What does get_class(new class {}) return? Answer with the part of the name before the NUL byte (without the file path). | «class» Пояснение: get_class() returns the fully qualified class name of an object.
Raw```json ⏎ { ⏎ "answer": "class", ⏎ "explanation": "get_class() returns the fully qualified class name of an object." ⏎ } ⏎ ``` | неверно верный: «class@anonymous» | get_class анонимного класса печатает class@anonymous\0<файл>:<строка>$n; короткая форма — часть до NUL-байта. Проверено php -r (hex). |
T06-L6 0.1 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. | «no» Пояснение: A private method is not accessible outside its own class and cannot be overridden or accessed by child classes.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "A private method is not accessible outside its own class and cannot be overridden or accessed by child classes." ⏎ } ⏎ ``` | неверно верный: «yes» | private-члены не наследуются — правила совместимости подписей не действуют. |
T06-L7 0.1 c | OOP: classes and inheritance | The magic method __get() is called only for non-existent properties. | «— (нет ответа)» Пояснение: ```json
{
"answer": "false",
"explanation": "__get()" is called when an object is accessed, even for existing properties if a getter method is defined."
}
```
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "__get()" is called when an object is accessed, even for existing properties if a getter method is defined." ⏎ } ⏎ ``` | не разобрано верный: «no» парсинг: нет | __get срабатывает и для существующих, но недоступных (private/protected извне). |
T06-L8 0.08 c | OOP: classes and inheritance | What does reassigning a readonly property throw — Exception or Error? | «error» Пояснение: Attempting to reassign a readonly property in PHP typically throws an Error.
Raw```json ⏎ { ⏎ "answer": "Error", ⏎ "explanation": "Attempting to reassign a readonly property in PHP typically throws an Error." ⏎ } ⏎ ``` | верно | Error (readonly с 8.1); оговорка: в __clone() переинициализация допустима (8.3+). |
T07-L1 0.08 c | Interfaces, traits, enum | An interface can declare constants. | «no» Пояснение: Interfaces can only declare method signatures, not constants.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "Interfaces can only declare method signatures, not constants." ⏎ } ⏎ ``` | неверно верный: «yes» | Константы интерфейса наследуются реализациями. |
T07-L2 0.09 c | Interfaces, traits, enum | Which operator checks whether an object is an instance of a class or interface? | «yes» Пояснение: The instance of the class or interface check is performed using the 'instanceof' operator in PHP.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "The instance of the class or interface check is performed using the 'instanceof' operator in PHP." ⏎ } ⏎ ``` | неверно верный: «instanceof» | instanceof. |
T07-L3 0.08 c | Interfaces, traits, enum | An interface can declare static methods. | «no» Пояснение: Interfaces can only declare abstract methods or constants, not static methods.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "Interfaces can only declare abstract methods or constants, not static methods." ⏎ } ⏎ ``` | неверно верный: «yes» | Реализация обязана дать статический метод с той же сигнатурой. |
T07-L4 0.07 c | Interfaces, traits, enum | The instanceof operator only checks class inheritance: it ignores interfaces. | «no» Пояснение: The instanceof operator checks both class inheritance and interface implementation.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "The instanceof operator checks both class inheritance and interface implementation." ⏎ } ⏎ ``` | верно | instanceof возвращает true и для интерфейсов объекта. |
T07-L5 0.08 c | Interfaces, traits, enum | An interface method may have a default implementation, like a trait method. | «no» Пояснение: Interfaces in PHP do not support default implementations; traits provide similar functionality.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "Interfaces in PHP do not support default implementations; traits provide similar functionality." ⏎ } ⏎ ``` | верно | Методы интерфейса — только сигнатуры; тело даёт реализующий класс. |
T07-L6 0.12 c | Interfaces, traits, enum | An abstract method in an abstract class may have protected visibility. | «no» Пояснение: Abstract methods must be declared as abstract, and visibility modifiers like protected are not applicable to them in the way they are typically used for implementation.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "Abstract methods must be declared as abstract, and visibility modifiers like protected are not applicable to them in the way they are typically used for implementation." ⏎ } ⏎ ``` | неверно верный: «yes» | В абстрактном классе — любая видимость; в интерфейсе — только public. |
T07-L7 0.08 c | Interfaces, traits, enum | How many elements will Foo::cases() return for enum Foo { case A; case B; case C; }? | «3» Пояснение: The method will return the number of defined cases in the enum.
Raw```json ⏎ { ⏎ "answer": 3, ⏎ "explanation": "The method will return the number of defined cases in the enum." ⏎ } ⏎ ``` | верно | Статический метод cases(): 3. |
T07-L8 0.17 c | Interfaces, traits, enum | A trait can declare constants. | «no» Пояснение: Traits cannot directly declare constants; constants must be defined within a class or a trait using the `const` keyword within a class context if used in a specific way, but traits primarily provide reusable methods and properties.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "Traits cannot directly declare constants; constants must be defined within a class or a trait using the `const` keyword within a class context if used in a specific way, but traits primarily provide reusable methods and properties." ⏎ } ⏎ ``` | неверно верный: «yes» | С PHP 8.2 трейты могут объявлять константы (RFC constants_in_traits); до 8.2 — нет. |
T08-L1 0.08 c | Exceptions and errors | The Throwable interface is a common ancestor of both Exception and Error. | «no» Пояснение: Throwable is the root interface for both Exception and Error.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "Throwable is the root interface for both Exception and Error." ⏎ } ⏎ ``` | неверно верный: «yes» | Иерархия с PHP 7: Throwable → Exception и Throwable → Error. |
T08-L2 0.09 c | Exceptions and errors | A catch (Exception $e) block will also catch TypeError, because TypeError ultimately inherits from Exception. | «no» Пояснение: TypeError is a built-in PHP error that is not an exception and will not be caught by a catch block for Exception.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "TypeError is a built-in PHP error that is not an exception and will not be caught by a catch block for Exception." ⏎ } ⏎ ``` | верно | TypeError наследуется от Error; catch (Exception) его не ловит. |
T08-L3 0.08 c | Exceptions and errors | The @ operator suppresses exceptions too. | «no» Пояснение: The @ operator suppresses errors but does not suppress exceptions thrown by functions.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "The @ operator suppresses errors but does not suppress exceptions thrown by functions." ⏎ } ⏎ ``` | верно | @ глушит диагностику (warnings/notices), исключения не перехватывает. |
T08-L4 0.08 c | Exceptions and errors | What error class does intdiv(5, 0) throw? | «divisionbyzeroerror» Пояснение: Dividing by zero in PHP throws a DivisionByZeroError.
Raw```json ⏎ { ⏎ "answer": "DivisionByZeroError", ⏎ "explanation": "Dividing by zero in PHP throws a DivisionByZeroError." ⏎ } ⏎ ``` | верно | DivisionByZeroError (иерархия Error, не Exception); php-грейдер объективен. |
T08-L5 0.08 c | Exceptions and errors | The finally block runs only if the exception was caught by a catch block. | «no» Пояснение: The finally block always executes, regardless of whether an exception was caught.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "The finally block always executes, regardless of whether an exception was caught." ⏎ } ⏎ ``` | верно | Наоборот: finally выполняется всегда — даже когда исключение не поймано и уходит выше. Проверено php -r. |
T08-L6 0.08 c | Exceptions and errors | An exception thrown inside a finally block has no effect on the result of the try block. | «no» Пояснение: An exception thrown in a finally block will still affect the outcome of the try block.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "An exception thrown in a finally block will still affect the outcome of the try block." ⏎ } ⏎ ``` | верно | Исключение из finally перекрывает исходное и уходит вместо него. |
T08-L7 0.08 c | Exceptions and errors | What does the expression (bool) new Exception('x') return? | «exception» Пояснение: The expression returns a new instance of the Exception class.
Raw```json ⏎ { ⏎ "answer": "Exception", ⏎ "explanation": "The expression returns a new instance of the Exception class." ⏎ } ⏎ ``` | неверно верный: «true» | Любой объект при приведении к bool — true. Формы ответа: true или да. |
T08-L8 0.09 c | Exceptions and errors | Functions registered via register_shutdown_function() run when exit is called. | «yes» Пояснение: register_shutdown_function() registers a function to be executed when the script is shutting down.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "register_shutdown_function() registers a function to be executed when the script is shutting down." ⏎ } ⏎ ``` | верно | exit завершает скрипт, но shutdown-функции отрабатывают. |
T09-L1 0.09 c | Namespaces and autoloading | The use App\Service\Mailer; statement itself loads the class file. | «yes» Пояснение: Including a class file in PHP loads the class definition into memory.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "Including a class file in PHP loads the class definition into memory." ⏎ } ⏎ ``` | неверно верный: «no» | use — псевдоним на этапе компиляции; файл грузит автозагрузчик при первом обращении. |
T09-L2 0.08 c | Namespaces and autoloading | What follows use to import a function (not a class): the word function or const? | «function» Пояснение: The 'function' keyword is used to declare a standalone function in PHP.
Raw```json ⏎ { ⏎ "answer": "function", ⏎ "explanation": "The 'function' keyword is used to declare a standalone function in PHP." ⏎ } ⏎ ``` | верно | use function ...; (и use const для констант). |
T09-L3 0.12 c | Namespaces and autoloading | Into which file (path from src/) does the PSR-4 mapping "App\ → src/" place the class App\Controller\Api\UserController? | «src/controller/api/usercontroller.php» Пояснение: PSR-4 maps the namespace prefix to the directory structure, mapping App\ to src/.
Raw```json ⏎ { ⏎ "answer": "src/Controller/Api/UserController.php", ⏎ "explanation": "PSR-4 maps the namespace prefix to the directory structure, mapping App\\ to src/." ⏎ } ⏎ ``` | верно | Остаток имени после префикса, \ → /. |
T09-L4 0.08 c | Namespaces and autoloading | Including vendor/autoload.php registers autoloaders via spl_autoload_register(). | «yes» Пояснение: vendor/autoload.php is typically responsible for registering autoloaders.
Raw```json ⏎ { ⏎ "answer": "true", ⏎ "explanation": "vendor/autoload.php is typically responsible for registering autoloaders." ⏎ } ⏎ ``` | верно | Composer ставит автозагрузчик именно на spl_autoload_register. |
T09-L5 0.09 c | Namespaces and autoloading | The magic constant __NAMESPACE__ contains the name of the current namespace. | «yes» Пояснение: The \_\_NAMESPACE\_\_ magic constant holds the current namespace name in PHP.
Raw```json ⏎ { ⏎ "answer": "true", ⏎ "explanation": "The \_\_NAMESPACE\_\_ magic constant holds the current namespace name in PHP." ⏎ } ⏎ ``` | верно | В корневом пространстве — пустая строка. |
T09-L6 0.1 c | Namespaces and autoloading | An unqualified class name (without a leading \) in new is resolved from the global root. | «no» Пояснение: An unqualified class name is resolved from the current namespace or the global namespace, not directly from the global root without qualification.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "An unqualified class name is resolved from the current namespace or the global namespace, not directly from the global root without qualification." ⏎ } ⏎ ``` | верно | Резолвится относительно текущего namespace (с учётом импортов). |
T09-L7 0.08 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 mapping dictates that the namespace prefix maps to the directory structure.
Raw```json ⏎ { ⏎ "answer": "true", ⏎ "explanation": "PSR-4 mapping dictates that the namespace prefix maps to the directory structure." ⏎ } ⏎ ``` | верно | Остаток имени после префикса переносится в путь как есть. |
T09-L8 0.11 c | Namespaces and autoloading | A use statement may be written inside a function body — the import then applies to that function only. | «no» Пояснение: Use statements are generally for global scope or the scope where they are declared, not confined to a single function.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "Use statements are generally for global scope or the scope where they are declared, not confined to a single function." ⏎ } ⏎ ``` | верно | use внутри тела функции — parse error; импорты файловые и компиляционные. |
T10-L1 0.08 c | References and scope | Arrays are copied on assignment rather than passed by reference. | «yes» Пояснение: In PHP, assigning an array copies the value, not the reference.
Raw```json ⏎ { ⏎ "answer": "true", ⏎ "explanation": "In PHP, assigning an array copies the value, not the reference." ⏎ } ⏎ ``` | верно | Присваивание массива — копия (в движке — copy-on-write). |
T10-L2 0.09 c | References and scope | What will this print: $a = [1, 2]; $b = $a; $b[] = 3; echo count($a); | «2» Пояснение: Assigning an array by reference means both variables point to the same array.
Raw```json ⏎ { ⏎ "answer": 2, ⏎ "explanation": "Assigning an array by reference means both variables point to the same array." ⏎ } ⏎ ``` | верно | Присваивание — копия: в $a по-прежнему 2 элемента. |
T10-L3 0.1 c | References and scope | Inside a function, user-defined global variables are inaccessible without global, $GLOBALS, or passing them as parameters. | «yes» Пояснение: User-defined variables inside a function are local by default and inaccessible from the global scope.
Raw```json ⏎ { ⏎ "answer": "true", ⏎ "explanation": "User-defined variables inside a function are local by default and inaccessible from the global scope." ⏎ } ⏎ ``` | верно | Область видимости функций изолирована; исключение — суперглобалы ($_GET и др.). |
T10-L4 0.12 c | References and scope | unset($GLOBALS['x']) inside a function removes the global variable only for that function. | «no» Пояснение: unset() within a function removes the variable from the current scope, but it does not necessarily remove the global variable unless the variable was accessed via the global scope.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "unset() within a function removes the variable from the current scope, but it does not necessarily remove the global variable unless the variable was accessed via the global scope." ⏎ } ⏎ ``` | верно | $GLOBALS — прямое окно в глобальную область: unset удалит её по-настоящему. |
T10-L5 0.1 c | References and scope | What will this print: function inc(&$x) { $x++; } $n = 5; inc($n); echo $n; | «6» Пояснение: The function modifies the variable passed by reference, so $n$ is incremented.
Raw```json ⏎ { ⏎ "answer": 6, ⏎ "explanation": "The function modifies the variable passed by reference, so $n$ is incremented." ⏎ } ⏎ ``` | верно | Ссылка меняет оригинал: 6. |
T10-L6 0.11 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 iterates over a copy of the array, so changes inside the loop do not affect the array being iterated over.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "A foreach loop iterates over a copy of the array, so changes inside the loop do not affect the array being iterated over." ⏎ } ⏎ ``` | верно | По значению foreach итерирует копию-снимок. |
T10-L7 0.08 c | References and scope | A static property belongs to each instance separately: changes in one object are not visible in others. | «no» Пояснение: Static properties belong to the class itself, shared by all instances.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "Static properties belong to the class itself, shared by all instances." ⏎ } ⏎ ``` | верно | Наоборот: статическое свойство общее для всех экземпляров класса. Проверено php -r. |
T10-L8 0.1 c | References and scope | An array can have a boolean key true, and it will be stored as bool. | «yes» Пояснение: PHP arrays can use booleans as keys, and the value associated with that key will be the value itself.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "PHP arrays can use booleans as keys, and the value associated with that key will be the value itself." ⏎ } ⏎ ``` | неверно верный: «no» | Булев ключ приводится к int: true → 1, false → 0. |
T11-L1 0.09 c | Generators, iterators, SPL | Inside a generator, return with a value can be used, and it becomes available via $gen->getReturn(). | «no» Пояснение: Generators use the `yield` keyword to return values, not a method like `getReturn()`.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "Generators use the `yield` keyword to return values, not a method like `getReturn()`." ⏎ } ⏎ ``` | неверно верный: «yes» | return-значение генератора доступно через getReturn() после прохода. |
T11-L2 0.07 c | Generators, iterators, SPL | A fully consumed generator can be rewound with rewind() and traversed again. | «no» Пояснение: Generators are typically stateful and cannot be rewound after full consumption.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "Generators are typically stateful and cannot be rewound after full consumption." ⏎ } ⏎ ``` | верно | Генератор одноразовый: rewind после начала итерации бросает Exception. |
T11-L3 0.08 c | Generators, iterators, SPL | The yield from construct delegates traversal to another generator or iterable. | «yes» Пояснение: Yielding from a construct often delegates iteration to another generator or iterable.
Raw```json ⏎ { ⏎ "answer": "true", ⏎ "explanation": "Yielding from a construct often delegates iteration to another generator or iterable." ⏎ } ⏎ ``` | верно | yield from проксирует значения, ключи и return-значение внутреннего генератора. |
T11-L4 0.08 c | Generators, iterators, SPL | What does get_class(g()) return for function g() { yield 1; }? | «callable» Пояснение: get_class() returns the class name of the given callable.
Raw```json ⏎ { ⏎ "answer": "callable", ⏎ "explanation": "get_class() returns the class name of the given callable." ⏎ } ⏎ ``` | неверно верный: «generator» | Функция с yield возвращает Generator. |
T11-L5 0.09 c | Generators, iterators, SPL | How many elements will count(iterator_to_array((function () { yield from [1, 2, 3]; })())) return? | «3» Пояснение: The generator yields three numbers, which are then converted into an array of size three.
Raw```json ⏎ { ⏎ "answer": 3, ⏎ "explanation": "The generator yields three numbers, which are then converted into an array of size three." ⏎ } ⏎ ``` | верно | yield from делегирует все 3 элемента. |
T11-L6 0.09 c | Generators, iterators, SPL | The SplStack class implements a FIFO queue. | «no» Пояснение: The SplStack class implements a LIFO (Last-In, First-Out) stack, not a FIFO queue.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "The SplStack class implements a LIFO (Last-In, First-Out) stack, not a FIFO queue." ⏎ } ⏎ ``` | верно | SplStack — стек LIFO; очередь FIFO — SplQueue. |
T11-L7 0.06 c | Generators, iterators, SPL | ArrayIterator allows wrapping an array and traversing it via the Iterator interface. | «yes» Пояснение: ArrayIterator implements the Iterator interface, allowing traversal of an array.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "ArrayIterator implements the Iterator interface, allowing traversal of an array." ⏎ } ⏎ ``` | верно | Объектная обёртка над массивом. |
T11-L8 0.07 c | Generators, iterators, SPL | An ArrayObject instance cannot be traversed with foreach. | «yes» Пояснение: ArrayObject instances do not support the foreach loop directly.
Raw```json ⏎ { ⏎ "answer": "true", ⏎ "explanation": "ArrayObject instances do not support the foreach loop directly." ⏎ } ⏎ ``` | неверно верный: «no» | ArrayObject реализует IteratorAggregate — foreach по нему работает. |
T12-L1 0.08 c | Configuration and security | password_hash() generates a salt automatically — passing one separately is not needed. | «no» Пояснение: password_hash() automatically handles salt generation and inclusion in the resulting hash.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "password_hash() automatically handles salt generation and inclusion in the resulting hash." ⏎ } ⏎ ``` | неверно верный: «yes» | Соль встраивается в строку результата; параметр salt устарел. |
T12-L2 0.11 c | Configuration and security | In PHP 8, PASSWORD_DEFAULT is md5 with an automatically added salt. | «no» Пояснение: PASSWORD_DEFAULT in PHP 8 uses the recommended hashing algorithm (like bcrypt) based on the configured password hashing algorithm.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "PASSWORD_DEFAULT in PHP 8 uses the recommended hashing algorithm (like bcrypt) based on the configured password hashing algorithm." ⏎ } ⏎ ``` | верно | PASSWORD_DEFAULT — bcrypt; md5 для паролей непригоден (перебирается массово). |
T12-L3 0.09 c | Configuration and security | What does password_verify('secret', password_hash('secret', PASSWORD_DEFAULT)) return? | «1» Пояснение: The password_verify function returns 1 if the provided password matches the stored hash.
Raw```json ⏎ { ⏎ "answer": "1", ⏎ "explanation": "The password_verify function returns 1 if the provided password matches the stored hash." ⏎ } ⏎ ``` | неверно верный: «true» | Соль и хеш в одной строке: true (форма ответа: true или да). |
T12-L4 0.08 c | Configuration and security | strip_tags() protects against SQL injection. | «no» Пояснение: strip_tags() removes HTML/PHP tags and does not prevent SQL injection.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "strip_tags() removes HTML/PHP tags and does not prevent SQL injection." ⏎ } ⏎ ``` | верно | strip_tags режет HTML-теги (помощник против XSS), к параметризации SQL отношения не имеет. |
T12-L5 0.09 c | Configuration and security | session_regenerate_id() is used to protect against session fixation upon user login. | «yes» Пояснение: session_regenerate_id() replaces the old session ID with a new one, mitigating session fixation attacks.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "session_regenerate_id() replaces the old session ID with a new one, mitigating session fixation attacks." ⏎ } ⏎ ``` | верно | Новый ID сессии после логина — стандартная защита от session fixation. |
T12-L6 0.09 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 PHP SAPI being used.
Raw```json ⏎ { ⏎ "answer": "php_sapi_name()", ⏎ "explanation": "The php_sapi_name() function returns the name of the PHP SAPI being used." ⏎ } ⏎ ``` | верно | php_sapi_name(). |
T12-L7 0.09 c | Configuration and security | session_destroy() deletes session data on the server but not the cookie in the user's browser. | «no» Пояснение: session_destroy() deletes session data on the server and typically instructs the browser to delete the session cookie.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "session_destroy() deletes session data on the server and typically instructs the browser to delete the session cookie." ⏎ } ⏎ ``` | неверно верный: «yes» | Удаление cookie — отдельный шаг через setcookie с истёкшим сроком. |
T12-L8 0.09 c | Configuration and security | Without calling session_start(), the $_SESSION array is automatically populated with session data. | «no» Пояснение: The $_SESSION superglobal is populated only after calling session_start();.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "The $_SESSION superglobal is populated only after calling session_start();." ⏎ } ⏎ ``` | верно | Без session_start() данные сессии в массив не загружаются ($_SESSION можно заполнить вручную, но привязки к сессии нет). |
VC-L1 0.08 c | PHP 8.4–8.5 | In which PHP version was the array_find() function introduced? | «7.4» Пояснение: The array_find() function was introduced in PHP version 7.4.
Raw```json ⏎ { ⏎ "answer": "7.4", ⏎ "explanation": "The array_find() function was introduced in PHP version 7.4." ⏎ } ⏎ ``` | неверно верный: «8.4» | PHP 8.4 (RFC array_find). |
VC-L2 0.1 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 accessors) have been available in PHP for many versions before 8.4.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "Property hooks (get/set accessors) have been available in PHP for many versions before 8.4." ⏎ } ⏎ ``` | неверно верный: «yes» | Property hooks — PHP 8.4 (ноябрь 2024). |
VC-L3 0.08 c | PHP 8.4–8.5 | Asymmetric visibility (public private(set) string $name) appeared in PHP 8.4. | «no» Пояснение: Asymmetric visibility (public private(set)) is not a feature introduced in PHP 8.4.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "Asymmetric visibility (public private(set)) is not a feature introduced in PHP 8.4." ⏎ } ⏎ ``` | неверно верный: «yes» | Asymmetric visibility v2 — PHP 8.4. |
VC-L4 0.07 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 version 8.0.
Raw```json ⏎ { ⏎ "answer": "8.0", ⏎ "explanation": "The #[NoDiscard] attribute was introduced in PHP version 8.0." ⏎ } ⏎ ``` | неверно верный: «8.5» | #[\NoDiscard] — PHP 8.5 (marking return values as important). |
VC-L5 0.08 c | PHP 8.4–8.5 | In which PHP version did the pipe operator |> first appear? Answer with the version number. | «8.0» Пояснение: The pipe operator |> was introduced in PHP version 8.0.
Raw```json ⏎ { ⏎ "answer": "8.0", ⏎ "explanation": "The pipe operator |> was introduced in PHP version 8.0." ⏎ } ⏎ ``` | неверно верный: «8.5» | Pipe operator — PHP 8.5 (2025). |
VC-L6 0.08 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. | «7.0» Пояснение: The syntax clone($obj, $options) was introduced in PHP 7.0.
Raw```json ⏎ { ⏎ "answer": "7.0", ⏎ "explanation": "The syntax clone($obj, $options) was introduced in PHP 7.0." ⏎ } ⏎ ``` | неверно верный: «8.5» | Clone with v2 — PHP 8.5. |
VC-L7 0.08 c | PHP 8.4–8.5 | In which PHP version were the array_first() and array_last() functions introduced? | «7.4» Пояснение: array_first() and array_last() were introduced in PHP version 7.4.
Raw```json ⏎ { ⏎ "answer": "7.4", ⏎ "explanation": "array_first() and array_last() were introduced in PHP version 7.4." ⏎ } ⏎ ``` | неверно верный: «8.5» | PHP 8.5. |
VC-L8 0.08 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. | «7.4» Пояснение: RFC Partial Function Application v2 was adopted in PHP version 7.4.
Raw```json ⏎ { ⏎ "answer": "7.4", ⏎ "explanation": "RFC Partial Function Application v2 was adopted in PHP version 7.4." ⏎ } ⏎ ``` | неверно верный: «8.6» | PFA v2 принят 05.12.2025 (33-0-0), реализован в PHP 8.6. |
VF-L1 0.08 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. | «7.4» Пояснение: The clamp() function was introduced in PHP version 7.4.
Raw```json ⏎ { ⏎ "answer": "7.4", ⏎ "explanation": "The clamp() function was introduced in PHP version 7.4." ⏎ } ⏎ ``` | неверно верный: «8.6» | По данным владельца (wiki.php.net/rfc): clamp_v2 — 8.6; clamp() в 8.5.11 отсутствует (косвенное подтверждение). Дата-якорь делает клетку монотонной. |
VF-L2 0.08 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 has not been adopted in PHP as of the current knowledge cutoff.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "RFC Context Managers v2 has not been adopted in PHP as of the current knowledge cutoff." ⏎ } ⏎ ``` | верно | На 06.11.2026 — в обсуждении (создан 2026-10-23); не принят. |
VF-L3 0.09 c | PHP: 8.6+ and the future | RFC Bound-Erased Generic Types (generics) was declined in 2026. | «no» Пояснение: There is no public record confirming that RFC Bound-Erased Generic Types were declined in 2026.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "There is no public record confirming that RFC Bound-Erased Generic Types were declined in 2026." ⏎ } ⏎ ``` | неверно верный: «yes» | Голосование завершилось 2026-06-28: отклонён (wiki.php.net/rfc). |
VF-L4 0.09 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» Пояснение: The ZTS extension for multithreading is not enabled by default in PHP.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "The ZTS extension for multithreading is not enabled by default in PHP." ⏎ } ⏎ ``` | верно | Такого принятого RFC нет на дату якоря; якорь делает клетку монотонной — при принятии RFC позже клетка не перевернётся. |
VF-L5 0.14 c | PHP: 8.6+ and the future | As of PHP 8.5, generics (parameterized types) are still absent. | «no» Пояснение: PHP 8.0 introduced generic types using templates, and PHP 8.1 introduced native generics via union types and intersection types, which are often used to achieve similar goals.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "PHP 8.0 introduced generic types using templates, and PHP 8.1 introduced native generics via union types and intersection types, which are often used to achieve similar goals." ⏎ } ⏎ ``` | неверно верный: «yes» | Generics в PHP отсутствуют; отрицательный контроль (не путать с C#/Java). |
VF-L6 0.1 c | PHP: 8.6+ and the future | As of 2026-11-07, the latest stable PHP version is 8.5, and PHP 8.6 has not been released yet (GA — 2026-11-19). | «no» Пояснение: As of the current knowledge cutoff, PHP 8.5 is the latest stable version, and PHP 8.6 has not been released yet.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "As of the current knowledge cutoff, PHP 8.5 is the latest stable version, and PHP 8.6 has not been released yet." ⏎ } ⏎ ``` | неверно верный: «yes» | 8.5 — релиз осени 2025; 8.6 GA 19.11.2026 (wiki.php.net/todo/php86). Дата снимка — 06.11.2026. |
VF-L7 0.1 c | PHP: 8.6+ and the future | The PHP 6 branch never shipped: after PHP 5.6 came PHP 7.0 directly. | «no» Пояснение: PHP 6.0 was a major release that was shipped, although it was not the current stable version.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "PHP 6.0 was a major release that was shipped, although it was not the current stable version." ⏎ } ⏎ ``` | неверно верный: «yes» | Исторический факт: ветка 6 не была релизнута. |
VF-L8 0.1 c | PHP: 8.6+ and the future | The RFC adding the #[\Deprecated] attribute to the core was adopted. | «no» Пояснение: The RFC adding the #[\Deprecated] attribute is not a widely adopted standard feature in core PHP.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "The RFC adding the #[\Deprecated] attribute is not a widely adopted standard feature in core PHP." ⏎ } ⏎ ``` | неверно верный: «yes» | #[\Deprecated] — принят, реализован в PHP 8.4. |
T25-L1 0.09 c | Clean architecture | The dependency rule of clean and onion architecture: inner layers know nothing about outer ones — dependencies point toward the center. | «yes» Пояснение: This principle is central to clean and onion architecture, enforcing strict layering.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "This principle is central to clean and onion architecture, enforcing strict layering." ⏎ } ⏎ ``` | верно | Чистая (Robert C. Martin), луковичная (Jeffrey Palermo) и гексагональная (ports & adapters) — варианты одной идеи: зависимости направлены внутрь, к домену. Слоями в проекте следит deptrac. |
T25-L2 0.08 c | Clean architecture | Domain entities import neither Doctrine nor Symfony — only the language and, possibly, the standard library. | «yes» Пояснение: Domain entities are generally language-agnostic and focus on business logic.
Raw```json ⏎ { ⏎ "answer": "true", ⏎ "explanation": "Domain entities are generally language-agnostic and focus on business logic." ⏎ } ⏎ ``` | верно | Изоляция домена от инфраструктуры; deptrac в проекте как раз следит за слоями. |
T25-L3 0.09 c | Clean architecture | Controllers and Twig templates belong to the business-logic layer because they are the ones calling use cases. | «no» Пояснение: Controllers handle request/response, and Twig templates are for presentation, not the business-logic layer.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "Controllers handle request/response, and Twig templates are for presentation, not the business-logic layer." ⏎ } ⏎ ``` | верно | Наоборот: это интерфейсные адаптеры (внешний слой); они зависят от use cases, а не наоборот. |
T25-L4 0.09 c | Clean architecture | What sits at the very center of the onion architecture? | «controller» Пояснение: In the standard MVC pattern, the Controller acts as the central point handling requests.
Raw```json ⏎ { ⏎ "answer": "Controller", ⏎ "explanation": "In the standard MVC pattern, the Controller acts as the central point handling requests." ⏎ } ⏎ ``` | неверно верный: «domain model» | Центральное кольцо — Domain Model: сущности и бизнес-правила без зависимостей; далее Domain Services → Application Services → Infrastructure/UI/Tests (Palermo). |
T25-L5 0.08 c | Clean architecture | Layer boundary violations can be caught automatically: a layer-dependency analyzer (e.g. deptrac) fails on a forbidden call. | «yes» Пояснение: Layer-dependency analyzers are designed to automatically detect and flag violations like forbidden calls.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "Layer-dependency analyzers are designed to automatically detect and flag violations like forbidden calls." ⏎ } ⏎ ``` | верно | depfile.yaml в проекте TasK: CI проверяет правила слоёв на каждом пайплайне. |
T25-L6 0.08 c | Clean architecture | A use case (interactor) may accept an HTTP request or an EntityManager as arguments — it is simpler that way. | «yes» Пояснение: Accepting an HTTP request or EntityManager directly simplifies the use case.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "Accepting an HTTP request or EntityManager directly simplifies the use case." ⏎ } ⏎ ``` | неверно верный: «no» | Use case принимает DTO и порты; привязка к HTTP/ORM протекает инфраструктуру во внутренние слои. |
T25-L7 0.1 c | Clean architecture | What is the component called that provides a collection of aggregates/entities while hiding the storage mechanism behind an interface? | «repository» Пояснение: A Repository pattern abstracts data access and manages collections of domain objects.
Raw```json ⏎ { ⏎ "answer": "Repository", ⏎ "explanation": "A Repository pattern abstracts data access and manages collections of domain objects." ⏎ } ⏎ ``` | верно | Repository pattern (DDD/Evans); в проекте — Doctrine-репозитории за портами. |
T25-L8 0.11 c | Clean architecture | In clean architecture, swapping PostgreSQL for another database touches only the outer layer — the domain and use cases stay unchanged. | «no» Пояснение: Changing the database typically requires changes in the infrastructure layer and potentially the data mapping/persistence layer.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "Changing the database typically requires changes in the infrastructure layer and potentially the data mapping/persistence layer." ⏎ } ⏎ ``` | неверно верный: «yes» | Следствие правила зависимостей: инфраструктура взаимозаменяема. |
T26-L1 0.11 c | DDD | In DDD, an aggregate is just another name for a database table. | «no» Пояснение: An aggregate is a concept in Domain-Driven Design representing a cluster of related objects treated as a single unit of consistency.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "An aggregate is a concept in Domain-Driven Design representing a cluster of related objects treated as a single unit of consistency." ⏎ } ⏎ ``` | верно | Агрегат — кластер объектов с границей согласованности (транзакционной вокруг корня); таблица — деталь хранения. |
T26-L2 0.09 c | DDD | A Value Object is immutable and compared by the values of its fields, not by identity. | «yes» Пояснение: Value Objects are immutable and equality is determined by the values of their attributes.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "Value Objects are immutable and equality is determined by the values of their attributes." ⏎ } ⏎ ``` | верно | Классика Evans: Money, Email; равенство структурное. |
T26-L3 0.09 c | DDD | What is the single external entry point of an aggregate, through which all changes must go, called? | «aggregate root» Пояснение: The Aggregate Root is the single entity that controls all changes to the aggregate.
Raw```json ⏎ { ⏎ "answer": "Aggregate Root", ⏎ "explanation": "The Aggregate Root is the single entity that controls all changes to the aggregate." ⏎ } ⏎ ``` | верно | Aggregate Root: внешние объекты ссылаются только на корень; он защищает инварианты агрегата. |
T26-L4 0.09 c | DDD | In DDD, a repository is declared for an aggregate (its root), not for every entity. | «yes» Пояснение: In DDD, repositories are typically scoped to the aggregate root to manage the persistence of that aggregate.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "In DDD, repositories are typically scoped to the aggregate root to manage the persistence of that aggregate." ⏎ } ⏎ ``` | верно | Репозиторий корня хранит границу согласованности агрегата; вложенные сущности доступны только через корень. |
T26-L5 0.09 c | DDD | Ubiquitous language is the model's shared language common to developers and domain experts. | «yes» Пояснение: Ubiquitous language is the shared language used by developers and domain experts in a software project.
Raw```json ⏎ { ⏎ "answer": "true", ⏎ "explanation": "Ubiquitous language is the shared language used by developers and domain experts in a software project." ⏎ } ⏎ ``` | верно | Evans: язык из требований переходит в имена классов и методов. |
T26-L6 0.09 c | DDD | What is the boundary called within which a model and its language are consistent, while outside the same words mean other models? | «embedding space» Пояснение: The embedding space represents the semantic space where related words and models are close together.
Raw```json ⏎ { ⏎ "answer": "embedding space", ⏎ "explanation": "The embedding space represents the semantic space where related words and models are close together." ⏎ } ⏎ ``` | неверно верный: «bounded context» | Bounded Context; «Заказ» в биллинге и в доставке — разные модели. |
T26-L7 0.11 c | DDD | An anemic model (objects with only getters/setters, logic in services) is the recommended DDD style. | «no» Пояснение: An anemic model is generally not the recommended style for Domain-Driven Design (DDD), which favors rich domain objects with behavior.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "An anemic model is generally not the recommended style for Domain-Driven Design (DDD), which favors rich domain objects with behavior." ⏎ } ⏎ ``` | верно | Наоборот: Evans называет анемичность антипаттерном — поведение должно жить в доменных объектах. |
T26-L8 0.07 c | DDD | Bounded context means each context has its own model: the same concept in different contexts is a different class. | «yes» Пояснение: Bounded contexts enforce distinct models for the same concept across different contexts.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "Bounded contexts enforce distinct models for the same concept across different contexts." ⏎ } ⏎ ``` | верно | Модели контекстов независимы; между ними — явная интеграция (ACL, published language). |
T13-L1 0.1 c | Symfony | Services in the Symfony DI container are created lazily by default — on first use. | «yes» Пояснение: Services in the Symfony DI container are lazy-loaded by default, meaning they are instantiated only when first requested.
Raw```json ⏎ { ⏎ "answer": "true", ⏎ "explanation": "Services in the Symfony DI container are lazy-loaded by default, meaning they are instantiated only when first requested." ⏎ } ⏎ ``` | верно | Контейнер инстанцирует сервис при первом извлечении; eager-создания по умолчанию нет. |
T13-L2 0.08 c | Symfony | Which Symfony console command lists all registered routes? | «no» Пояснение: There is no single built-in Symfony console command specifically designed to list all registered routes.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "There is no single built-in Symfony console command specifically designed to list all registered routes." ⏎ } ⏎ ``` | неверно верный: «debug:router» | bin/console debug:router (FrameworkBundle); в Symfony 3 команда называлась router:debug. |
T13-L3 0.09 c | Symfony | Symfony autowiring requires manually declaring every service in services.yaml. | «no» Пояснение: Autowiring automatically wires services based on type-hinting in the constructor.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "Autowiring automatically wires services based on type-hinting in the constructor." ⏎ } ⏎ ``` | верно | Autowire+autoconfigure регистрируют и связывают сервисы автоматически; ручное перечисление — исключение. |
T13-L4 0.11 c | Symfony | Twig templates are compiled into PHP classes and cached between requests. | «no» Пояснение: Twig templates are compiled into PHP code at runtime or upon first access, not strictly cached as PHP classes between requests.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "Twig templates are compiled into PHP code at runtime or upon first access, not strictly cached as PHP classes between requests." ⏎ } ⏎ ``` | неверно верный: «yes» | Twig компилирует шаблон один раз; кэш в var/cache/twig, в prod не пересобирается. |
T13-L5 0.12 c | Symfony | In the Symfony dev environment the DI container is rebuilt only after tracked files change, not on every request. | «no» Пояснение: The DI container is typically built once per request or during application bootstrap unless specific caching mechanisms are in place.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "The DI container is typically built once per request or during application bootstrap unless specific caching mechanisms are in place." ⏎ } ⏎ ``` | неверно верный: «yes» | Kernel проверяет freshness ресурсов (конфиги, классы); иначе переиспользуется кэш контейнера. |
T13-L6 0.08 c | Symfony | Which environment variable selects the active Symfony environment (dev/prod)? | «app_env» Пояснение: The APP_ENV environment variable is used to configure the active Symfony environment.
Raw```json ⏎ { ⏎ "answer": "APP_ENV", ⏎ "explanation": "The APP_ENV environment variable is used to configure the active Symfony environment." ⏎ } ⏎ ``` | верно | APP_ENV в .env; APP_DEBUG — отдельный флаг отладки. |
T13-L7 0.1 c | Symfony | A controller method can be private — Symfony routing works with any method of the class. | «no» Пояснение: Symfony routing typically relies on public methods or specific annotations/attributes to map routes.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "Symfony routing typically relies on public methods or specific annotations/attributes to map routes." ⏎ } ⏎ ``` | верно | Действие контроллера должно быть public; приватный метод по маршруту не вызывается. |
T13-L8 0.1 c | Symfony | Event subscribers always receive events before listeners, because the interface gives them priority. | «no» Пояснение: The order of event subscribers and listeners depends on the specific event system implementation, not an inherent interface priority.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "The order of event subscribers and listeners depends on the specific event system implementation, not an inherent interface priority." ⏎ } ⏎ ``` | верно | Порядок определяет priority, а не тип подписки; приоритеты задаются в getSubscribedEvents() так же, как у слушателей. |
T22-L1 0.08 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» Пояснение: Modern Symfony authentication relies on the AuthenticatorInterface, replacing the legacy Guard system.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "Modern Symfony authentication relies on the AuthenticatorInterface, replacing the legacy Guard system." ⏎ } ⏎ ``` | верно | Guard объявлен устаревшим в 5.3 и удалён в 6.0; в проекте symfony/security-bundle 8.1. |
T22-L2 0.1 c | Symfony: Security and forms | Which Symfony attribute checks a role/permission right on a controller method (403 without it)? | «no» Пояснение: Symfony uses annotations or attributes like @IsGranted to check roles/permissions.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "Symfony uses annotations or attributes like @IsGranted to check roles/permissions." ⏎ } ⏎ ``` | неверно верный: «isgranted» | #[IsGranted('ROLE_ADMIN')]; атрибут из symfony/security-http. |
T22-L3 0.1 c | Symfony: Security and forms | Voters are Symfony's mechanism for checking access to a specific object: isGranted('EDIT', $post). | «no» Пояснение: Voters are used by Symfony's Authorization system to determine if a user has permission to perform an action, not specifically for checking access to a single object.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "Voters are used by Symfony's Authorization system to determine if a user has permission to perform an action, not specifically for checking access to a single object." ⏎ } ⏎ ``` | неверно верный: «yes» | VoterInterface->vote(); docs Symfony — Voters. |
T22-L4 0.08 c | Symfony: Security and forms | In modern Symfony (7+) validation constraints are declared as PHP attributes (#[Assert\NotBlank]); doctrine annotations are no longer supported. | «yes» Пояснение: Modern Symfony uses PHP attributes for validation constraints, deprecating Doctrine annotations.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "Modern Symfony uses PHP attributes for validation constraints, deprecating Doctrine annotations." ⏎ } ⏎ ``` | верно | Докблок-аннотации удалены в Symfony 7.0; стандарт — атрибуты. В проекте symfony/validator 8.1. |
T22-L5 0.1 c | Symfony: Security and forms | CSRF protection of Symfony forms is enabled by default: the form validates the token on submission. | «no» Пояснение: CSRF protection in Symfony forms requires explicit configuration or use of specific bundles.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "CSRF protection in Symfony forms requires explicit configuration or use of specific bundles." ⏎ } ⏎ ``` | неверно верный: «yes» | FormType добавляет скрытое поле _token и проверяет его при валидации; отключение — осознанное исключение (csrf: false). |
T22-L6 0.08 c | Symfony: Security and forms | Form validation in Symfony runs server-side even if the client-side (HTML5) checks passed. | «yes» Пояснение: Server-side validation is crucial for security as client-side checks can be bypassed.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "Server-side validation is crucial for security as client-side checks can be bypassed." ⏎ } ⏎ ``` | верно | Клиентская валидация — только удобство; серверная обязательна и идёт по метаданным объекта формы. |
T22-L7 0.09 c | Symfony: Security and forms | Which Symfony maker command generates a form class (FormType)? | «php bin/console make:form» Пояснение: The `make:form` command is used to generate a form class.
Raw```json ⏎ { ⏎ "answer": "php bin/console make:form", ⏎ "explanation": "The `make:form` command is used to generate a form class." ⏎ } ⏎ ``` | верно | bin/console make:form (symfony/maker-bundle — в проекте). |
T22-L8 0.08 c | Symfony: Security and forms | Symfony stores the user's password in the session in plain text. | «no» Пояснение: Symfony, like most modern frameworks, does not store passwords in the session in plain text.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "Symfony, like most modern frameworks, does not store passwords in the session in plain text." ⏎ } ⏎ ``` | верно | В сессии живёт объект пользователя в токене; хеш затирается eraseCredentials(), plaintext там никогда не лежит. |
T23-L1 0.14 c | Symfony: configuration and services | Symfony bundle configuration lives in config/packages — one file per bundle or topic. | «no» Пояснение: Bundle configuration is typically managed within the bundle's own configuration files, though config/packages is where configuration for services and other aspects is often defined.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "Bundle configuration is typically managed within the bundle's own configuration files, though config/packages is where configuration for services and other aspects is often defined." ⏎ } ⏎ ``` | неверно верный: «yes» | Стандартная структура (config/packages/*.yaml); перегрузка — config/packages/<env>. |
T23-L2 0.1 c | Symfony: configuration and services | The .env file with dev defaults is committed to the repository, while real secrets live in the non-committed .env.local. | «yes» Пояснение: It is a common practice to commit development configuration files while keeping secret environment files uncommitted.
Raw```json ⏎ { ⏎ "answer": "true", ⏎ "explanation": "It is a common practice to commit development configuration files while keeping secret environment files uncommitted." ⏎ } ⏎ ``` | верно | symfony/dotenv: .env — общий безопасный набор значений; локальные секреты — .env.local (gitignored) или secrets-хранилище. |
T23-L3 0.09 c | Symfony: configuration and services | Which Symfony command lists the container's registered services and their aliases? | «service:list» Пояснение: The `service:list` command is used to list all registered services and their aliases.
Raw```json ⏎ { ⏎ "answer": "service:list", ⏎ "explanation": "The `service:list` command is used to list all registered services and their aliases." ⏎ } ⏎ ``` | неверно верный: «debug:container» | bin/console debug:container; параметры контейнера — debug:parameter. |
T23-L4 0.11 c | Symfony: configuration and services | The Symfony container allows changing parameters at runtime: $container->setParameter() works from a controller. | «no» Пояснение: While `setParameter()` can be called from various places, changing parameters at runtime is generally managed through configuration or services, not directly within a controller.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "While `setParameter()` can be called from various places, changing parameters at runtime is generally managed through configuration or services, not directly within a controller." ⏎ } ⏎ ``` | верно | Контейнер компилируется и замораживается; runtime-значения — только через переменные окружения. |
T23-L5 0.08 c | Symfony: configuration and services | By default, Symfony services are public (public: true) — you can fetch them directly from the container. | «no» Пояснение: Symfony services are private by default unless explicitly marked as public.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "Symfony services are private by default unless explicitly marked as public." ⏎ } ⏎ ``` | верно | С Symfony 4.0 сервисы по умолчанию private: инжектятся через autowiring; $container->get() — только для публичных. |
T23-L6 0.07 c | Symfony: configuration and services | Without a config file in config/packages a bundle will not work — configuration is mandatory for every bundle. | «yes» Пояснение: Configuration is mandatory for every bundle in Symfony.
Raw```json ⏎ { ⏎ "answer": "true", ⏎ "explanation": "Configuration is mandatory for every bundle in Symfony." ⏎ } ⏎ ``` | неверно верный: «no» | У бандлов есть встроенные умолчания (Extension); конфиг нужен только для отклонений от них. |
T23-L7 0.09 c | Symfony: configuration and services | Environment variable values are injected into services.yaml using the %env(VAR)% syntax. | «yes» Пояснение: The %env(VAR)% syntax is commonly used to inject environment variable values into configuration files like services.yaml.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "The %env(VAR)% syntax is commonly used to inject environment variable values into configuration files like services.yaml." ⏎ } ⏎ ``` | верно | %env(...)% резолвится в рантайме env-процессорами; docs — Env Var Processors. |
T23-L8 0.08 c | Symfony: configuration and services | Which Symfony environment variable enables debug mode (affects the profiler and Twig debugging)? | «true» Пояснение: The S_ENV_DEBUG environment variable enables debug mode.
Raw```json ⏎ { ⏎ "answer": "true", ⏎ "explanation": "The S_ENV_DEBUG environment variable enables debug mode." ⏎ } ⏎ ``` | неверно верный: «app_debug» | APP_DEBUG=1 (в .env dev-окружения); окружение выбирает APP_ENV — см. T13-L6. |
T16-L1 0.07 c | Symfony: Messenger | A single message in Symfony Messenger can only have one handler. | «no» Пояснение: A single message in Symfony Messenger can have multiple handlers configured.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "A single message in Symfony Messenger can have multiple handlers configured." ⏎ } ⏎ ``` | верно | Messenger вызывает все хендлеры, подписанные на класс сообщения (docs — Multiple Handlers). |
T16-L2 0.08 c | Symfony: Messenger | The sync transport in Messenger queues the message for a worker, just like async. | «no» Пояснение: Sync transport blocks the caller until the message is processed, unlike async transport which doesn't block.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "Sync transport blocks the caller until the message is processed, unlike async transport which doesn't block." ⏎ } ⏎ ``` | верно | Наоборот: sync обрабатывает немедленно в том же процессе, что и отправка; очередь — это async-транспорт. |
T16-L3 0.11 c | Symfony: Messenger | Which console command starts the worker that processes Messenger queue messages? | «php bin/console messenger:consume» Пояснение: The command to start the worker for processing Messenger queue messages is typically `messenger:consume`.
Raw```json ⏎ { ⏎ "answer": "php bin/console messenger:consume", ⏎ "explanation": "The command to start the worker for processing Messenger queue messages is typically `messenger:consume`." ⏎ } ⏎ ``` | верно | bin/console messenger:consume async; воркеры под supervisord/systemd в проде. |
T16-L4 0.07 c | Symfony: Messenger | Retries for failed messages (retry_strategy) are configured per Messenger transport. | «yes» Пояснение: Retry strategies are typically configured independently for each Messenger transport.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "Retry strategies are typically configured independently for each Messenger transport." ⏎ } ⏎ ``` | верно | retry_strategy на транспорте: max_retries, delay, multiplier; docs — Failed Messages & Retries. |
T16-L5 0.07 c | Symfony: Messenger | By default, Messenger serializes messages to JSON. | «yes» Пояснение: Messenger typically serializes messages to JSON format for transport.
Raw```json ⏎ { ⏎ "answer": "true", ⏎ "explanation": "Messenger typically serializes messages to JSON format for transport." ⏎ } ⏎ ``` | неверно верный: «no» | Дефолтный сериализатор — PhpSerializer (serialize()); JSON-сериализатор включается отдельно. |
T16-L6 0.08 c | Symfony: Messenger | Symfony Scheduler produces messages on a schedule and dispatches them through Messenger. | «yes» Пояснение: Symfony Scheduler is typically used to dispatch messages, often via Messenger.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "Symfony Scheduler is typically used to dispatch messages, often via Messenger." ⏎ } ⏎ ``` | верно | Schedule → RecurringMessage → шина Messenger; docs — Scheduler. |
T16-L7 0.1 c | Symfony: Messenger | Which built-in Messenger transport stores messages in database tables via Doctrine? | «no» Пояснение: Messenger primarily uses its own storage mechanisms, not directly Doctrine database tables for message persistence.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "Messenger primarily uses its own storage mechanisms, not directly Doctrine database tables for message persistence." ⏎ } ⏎ ``` | неверно верный: «doctrine» | Транспорт doctrine (symfony/doctrine-messenger); таблица messenger_messages. В проекте стоит amqp-messenger + doctrine-messenger. |
T16-L8 0.08 c | Symfony: Messenger | The Messenger pipeline can be extended with custom middleware, placed before or after the built-in ones. | «yes» Пояснение: Custom middleware can be inserted at various points in the pipeline.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "Custom middleware can be inserted at various points in the pipeline." ⏎ } ⏎ ``` | верно | messenger.bus.*.middleware в yaml; docs — Middleware. |
T28-L1 0.11 c | Symfony: versions | Symfony major releases come every two years, minor ones every six months (in May and November). | «no» Пояснение: Symfony releases follow a consistent cadence, but the specific timing for major and minor releases is not strictly tied to fixed two-year and six-month intervals.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "Symfony releases follow a consistent cadence, but the specific timing for major and minor releases is not strictly tied to fixed two-year and six-month intervals." ⏎ } ⏎ ``` | неверно верный: «yes» | Стандартный релизный цикл: 8.0 — ноябрь 2025, 8.1 — май 2026, 8.2 — ноябрь 2026. |
T28-L2 0.08 c | Symfony: versions | What is the minimum PHP version required by Symfony 8? | «8.0» Пояснение: Symfony 8 officially requires PHP version 8.0 or higher.
Raw```json ⏎ { ⏎ "answer": "8.0", ⏎ "explanation": "Symfony 8 officially requires PHP version 8.0 or higher." ⏎ } ⏎ ``` | неверно верный: «8.4» | Symfony 8.0 поднял требование до PHP >= 8.4.1 (в vendor проекта: "php": ">=8.4.1"). |
T28-L3 0.09 c | Symfony: versions | Symfony 7.0 kept support for docblock annotations (validation, routes). | «no» Пояснение: Symfony 7.0 has moved towards native PHP attributes for annotations.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "Symfony 7.0 has moved towards native PHP attributes for annotations." ⏎ } ⏎ ``` | верно | Наоборот: в 7.0 аннотации удалены — только PHP-атрибуты (#[Route], #[Assert\NotBlank]). |
T28-L4 0.09 c | Symfony: versions | AssetMapper manages CSS/JS without node or webpack — via importmap.php. | «yes» Пояснение: Importmap.php is used to manage CSS/JS assets without build tools like Node or webpack.
Raw```json ⏎ { ⏎ "answer": "true", ⏎ "explanation": "Importmap.php is used to manage CSS/JS assets without build tools like Node or webpack." ⏎ } ⏎ ``` | верно | symfony/asset-mapper (с 6.3, стандарт с 7.x); в проекте — importmap.php в корне и asset-mapper 8.1. |
T28-L5 0.08 c | Symfony: versions | Symfony 6.4 is a regular release without long-term support. | «no» Пояснение: Symfony has a long-term support (LTS) track for certain major versions.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "Symfony has a long-term support (LTS) track for certain major versions." ⏎ } ⏎ ``` | верно | Наоборот: 6.4 — LTS (расширенная поддержка); LTS выходит вместе с очередным мажором (6.4 — вместе с 7.0). |
T28-L6 0.1 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» Пояснение: Major Symfony releases often introduce breaking changes that may remove or alter deprecated features.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "Major Symfony releases often introduce breaking changes that may remove or alter deprecated features." ⏎ } ⏎ ``` | верно | Наоборот: мажорный релиз удаляет всё устаревшее (7.0 убрал деприкейшены 6.x, 8.0 — 7.x). |
T28-L7 0.1 c | Symfony: versions | Every Symfony major release is accompanied by an UPGRADE guide listing the changes. | «no» Пояснение: While documentation exists, a dedicated, comprehensive UPGRADE guide for every single major release is not a guaranteed standard practice for all Symfony versions.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "While documentation exists, a dedicated, comprehensive UPGRADE guide for every single major release is not a guaranteed standard practice for all Symfony versions." ⏎ } ⏎ ``` | неверно верный: «yes» | UPGRADE-7.0.md, UPGRADE-8.0.md в репозитории symfony/symfony. |
T28-L8 0.11 c | Symfony: versions | Which Symfony component manages assets and the importmap without node/webpack? | «asset_loader» Пояснение: The AssetLoader component manages assets and importmaps in Symfony without relying on node/webpack.
Raw```json ⏎ { ⏎ "answer": "asset_loader", ⏎ "explanation": "The AssetLoader component manages assets and importmaps in Symfony without relying on node/webpack." ⏎ } ⏎ ``` | неверно верный: «asset-mapper» | symfony/asset-mapper 8.1 — в проекте. |
T29-L1 0.07 c | Symfony: 8.2 and beyond | As of 2026-11-07, Symfony 8.2 has already been released. | «no» Пояснение: Symfony 8.2 has not been released yet.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "Symfony 8.2 has not been released yet." ⏎ } ⏎ ``` | верно | Наоборот: 8.2 ещё не выпущена — релиз в конце ноября 2026; последняя стабильная — 8.1. |
T29-L2 0.1 c | Symfony: 8.2 and beyond | As of 2026-11-07, Symfony 8.2 is scheduled for November 2026, following the usual six-month cycle. | «no» Пояснение: The information provided is a specific prediction about a future event, not a statement of current fact.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "The information provided is a specific prediction about a future event, not a statement of current fact." ⏎ } ⏎ ``` | неверно верный: «yes» | Политика релизов: 8.1 — май 2026, 8.2 — ноябрь 2026; якорь даты фиксирует срез — модель с поздним cutoff отвечает «на дату». |
T29-L3 0.09 c | Symfony: 8.2 and beyond | Which Symfony version comes after 8.1 (as of 2026-11-07)? | «9.0» Пояснение: Symfony 9.0 is the next major release after Symfony 8.1.
Raw```json ⏎ { ⏎ "answer": "9.0", ⏎ "explanation": "Symfony 9.0 is the next major release after Symfony 8.1." ⏎ } ⏎ ``` | неверно верный: «8.2» | 8.2 — следующий минорный релиз (ноябрь 2026); после его выхода проект переходит с 8.1.* на 8.2.*. |
T29-L4 0.09 c | Symfony: 8.2 and beyond | Symfony 8.2 is a major release requiring applications to be rewritten for new APIs. | «no» Пояснение: Symfony 8.2 is a minor release and generally backward-compatible, not a major breaking change.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "Symfony 8.2 is a minor release and generally backward-compatible, not a major breaking change." ⏎ } ⏎ ``` | верно | Наоборот: 8.2 — минорный релиз; новые возможности без поломки обратной совместимости. Мажор — 9.0. |
T29-L5 0.09 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» Пояснение: Updating between major versions often requires code changes due to breaking API or syntax changes.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "Updating between major versions often requires code changes due to breaking API or syntax changes." ⏎ } ⏎ ``` | неверно верный: «yes» | Политика Symfony: минорные релизы обратно совместимы; BC-break допустим только в мажорных. |
T29-L6 0.1 c | Symfony: 8.2 and beyond | Which minor version of the 8.x branch is released last, before Symfony 9.0? | «8.4» Пояснение: Symfony 8.4 is the last minor release in the 8.x branch before Symfony 9.0.
Raw```json ⏎ { ⏎ "answer": "8.4", ⏎ "explanation": "Symfony 8.4 is the last minor release in the 8.x branch before Symfony 9.0." ⏎ } ⏎ ``` | верно | По циклу: 8.2 (ноя 2026), 8.3 (май 2027), 8.4 (ноя 2027, вместе с 9.0) — как 6.4 выходила вместе с 7.0. |
T29-L7 0.12 c | Symfony: 8.2 and beyond | Symfony 8.2 will require PHP 8.5 — you would have to upgrade PHP along with it. | «no» Пояснение: Symfony 8.2 supports PHP 8.1, 8.2, and 8.3, and a PHP 8.5 requirement is not currently stated.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "Symfony 8.2 supports PHP 8.1, 8.2, and 8.3, and a PHP 8.5 requirement is not currently stated." ⏎ } ⏎ ``` | верно | Наоборот: минорные релизы не поднимают требования PHP; для всей ветки 8.x остаётся PHP >= 8.4. |
T29-L8 0.08 c | Symfony: 8.2 and beyond | Deprecations added in the 8.x branch will not be removed before Symfony 9.0. | «yes» Пояснение: Deprecations added in the 8.x branch are not removed before Symfony 9.0.
Raw```json ⏎ { ⏎ "answer": "true", ⏎ "explanation": "Deprecations added in the 8.x branch are not removed before Symfony 9.0." ⏎ } ⏎ ``` | верно | Политика: деприкейшены живут до следующего мажора; 9.0 — ноябрь 2027. |
T21-L1 0.08 c | Twig | Inside {{ }}, Twig allows calling arbitrary PHP code directly. | «no» Пояснение: Twig enforces a strict sandboxing model, preventing arbitrary PHP code execution.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "Twig enforces a strict sandboxing model, preventing arbitrary PHP code execution." ⏎ } ⏎ ``` | верно | Twig — DSL: только разрешённые окружением функции/фильтры; произвольный PHP не исполняется. |
T21-L2 0.08 c | Twig | By default, Twig auto-escapes printed variables. | «yes» Пояснение: Twig automatically escapes variables by default to prevent XSS vulnerabilities.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "Twig automatically escapes variables by default to prevent XSS vulnerabilities." ⏎ } ⏎ ``` | верно | Autoescape включён по умолчанию; {{ '<b>' }} → <b>. Проверено на Twig 3.30. |
T21-L3 0.08 c | Twig | The Twig |e filter escapes a string for safe output in an HTML context. | «yes» Пояснение: The |e filter escapes the output for safe rendering in HTML contexts.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "The |e filter escapes the output for safe rendering in HTML contexts." ⏎ } ⏎ ``` | верно | |e ('html') по умолчанию; есть контексты js/url/css. От SQL-инъекций он не защищает — это задача подготовленных запросов Doctrine. |
T21-L4 0.09 c | Twig | Which filter from twig/intl-extra formats a number according to a locale? | «number» Пояснение: The `number` filter from twig/intl-extra formats a number according to the current locale.
Raw```json ⏎ { ⏎ "answer": "number", ⏎ "explanation": "The `number` filter from twig/intl-extra formats a number according to the current locale." ⏎ } ⏎ ``` | неверно верный: «format_number» | |format_number(locale=...) из IntlExtension (twig/intl-extra есть в проекте). Проверено на Twig 3.30: 12345.6 → 12 345,6 (ru). |
T21-L5 0.09 c | Twig | The |raw filter disables auto-escaping for the value. | «yes» Пояснение: The |raw filter explicitly tells PHP not to escape the output of a variable.
Raw```json ⏎ { ⏎ "answer": "true", ⏎ "explanation": "The |raw filter explicitly tells PHP not to escape the output of a variable." ⏎ } ⏎ ``` | верно | {{ x|raw }} выводит HTML как есть; опасно с пользовательскими данными. Проверено на Twig 3.30. |
T21-L6 0.08 c | Twig | In Twig, {{ }} prints an expression value, while {% %} executes tags — conditions, loops, set. | «yes» Пояснение: Double curly braces print values, while curly braces with percent signs execute tags.
Raw```json ⏎ { ⏎ "answer": "true", ⏎ "explanation": "Double curly braces print values, while curly braces with percent signs execute tags." ⏎ } ⏎ ``` | верно | Два блока синтаксиса Twig: вывод (echo) против логики. |
T21-L7 0.1 c | Twig | In Twig you cannot declare a variable inside a template — values only come from the controller. | «no» Пояснение: Variables can be declared and manipulated within Twig templates using the `{% set %}` and `{% macro %}` tags.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "Variables can be declared and manipulated within Twig templates using the `{% set %}` and `{% macro %}` tags." ⏎ } ⏎ ``` | верно | {% set y = ... %} объявляет переменную в шаблоне. Проверено на Twig 3.30. |
T21-L8 0.08 c | Twig | Which Twig function dumps the debug structure of a variable (array, object)? | «dump» Пояснение: The `dump` function in Twig is used to output the debug structure of a variable.
Raw```json ⏎ { ⏎ "answer": "dump", ⏎ "explanation": "The `dump` function in Twig is used to output the debug structure of a variable." ⏎ } ⏎ ``` | верно | {{ dump(x) }} (DebugExtension; в Symfony доступна в dev-окружении). |
T24-L1 0.09 c | Bootstrap | Bootstrap is a CSS/JS library of ready-made UI components, not an SPA framework. | «yes» Пояснение: Bootstrap is a CSS/JS framework for front-end styling and components, not a full Single Page Application framework.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "Bootstrap is a CSS/JS framework for front-end styling and components, not a full Single Page Application framework." ⏎ } ⏎ ``` | верно | Компоненты и утилиты поверх вашего HTML; SPA-фреймворки (React/Vue) — другой класс инструментов. В проекте vendored 5.3.3. |
T24-L2 0.08 c | Bootstrap | Which Bootstrap class gives a responsive container with a fixed max width per breakpoint? | «container» Пояснение: The 'container' class sets a responsive, fixed-width container.
Raw```json ⏎ { ⏎ "answer": "container", ⏎ "explanation": "The 'container' class sets a responsive, fixed-width container." ⏎ } ⏎ ``` | верно | .container (фиксированная макс-ширина по брейкпоинтам) vs .container-fluid (на всю ширину). |
T24-L3 0.08 c | Bootstrap | The Bootstrap grid is built on CSS floats and splits a row into 16 columns. | «no» Пояснение: The Bootstrap grid is built on CSS Flexbox, not floats.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "The Bootstrap grid is built on CSS Flexbox, not floats." ⏎ } ⏎ ``` | верно | Наоборот: flexbox (с Bootstrap 4) и 12 колонок; float-сетка — это Bootstrap 3. |
T24-L4 0.1 c | Bootstrap | Bootstrap's named breakpoints (the infix used in class names) are sm, md, lg, xl, xxl — five of them. | «no» Пояснение: Bootstrap historically uses breakpoints like sm, md, lg, xl, and xxl, but this set can change based on the Bootstrap version.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "Bootstrap historically uses breakpoints like sm, md, lg, xl, and xxl, but this set can change based on the Bootstrap version." ⏎ } ⏎ ``` | неверно верный: «yes» | Тиров всего шесть: xs (без инфикса) + пять именованных (576/768/992/1200/1400 px). |
T24-L5 0.09 c | Bootstrap | Utilities like .mt-3 or .px-2 use the spacing scale: the number is a multiple of $spacer. | «yes» Пояснение: Utilities like .mt-3 use the spacing scale where the number is a multiple of the base spacing value.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "Utilities like .mt-3 use the spacing scale where the number is a multiple of the base spacing value." ⏎ } ⏎ ``` | неверно верный: «no» | Spacing utilities; $spacer = 1rem. |
T24-L6 0.1 c | Bootstrap | Which Bootstrap 5 data attribute enables an interactive component (e.g. dropdown) on an element? | «data-bs-toggle» Пояснение: The data-bs-toggle attribute is used to enable interactive components like dropdowns in Bootstrap.
Raw```json ⏎ { ⏎ "answer": "data-bs-toggle", ⏎ "explanation": "The data-bs-toggle attribute is used to enable interactive components like dropdowns in Bootstrap." ⏎ } ⏎ ``` | верно | data-bs-toggle="dropdown" и т.п.; в Bootstrap 4 атрибут назывался data-toggle. |
T24-L7 0.08 c | Bootstrap | Bootstrap 5 components work without jQuery — in plain vanilla JS. | «yes» Пояснение: Bootstrap 5 components are designed to work with plain vanilla JavaScript.
Raw```json ⏎ { ⏎ "answer": "true", ⏎ "explanation": "Bootstrap 5 components are designed to work with plain vanilla JavaScript." ⏎ } ⏎ ``` | верно | jQuery удалён в Bootstrap 5.0: data-bs-* атрибуты и JS API. В проекте vendored 5.3.3. |
T24-L8 0.07 c | Bootstrap | Dark mode in Bootstrap is enabled with a .dark class on the root element. | «yes» Пояснение: Bootstrap uses the .dark class on the root element to enable dark mode styling.
Raw```json ⏎ { ⏎ "answer": "true", ⏎ "explanation": "Bootstrap uses the .dark class on the root element to enable dark mode styling." ⏎ } ⏎ ``` | неверно верный: «no» | Наоборот: тема включается атрибутом data-bs-theme="dark" (Color modes, с 5.3); класса .dark не существует. В проекте 5.3.3. |
T14-L1 0.11 c | Doctrine | Doctrine ORM creates database tables on the fly the first time an entity is used at runtime. | «no» Пояснение: Doctrine uses schema management (like migrations or annotations) to define and manage database structure, not creating tables on the fly at runtime.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "Doctrine uses schema management (like migrations or annotations) to define and manage database structure, not creating tables on the fly at runtime." ⏎ } ⏎ ``` | верно | Схему создают инструменты (migrations, schema tool); рантайм структуру БД не меняет. |
T14-L2 0.08 c | Doctrine | Which EntityManager method marks a new object as managed without executing SQL until flush()? | «persist» Пояснение: The persist method marks a new entity as managed by the EntityManager.
Raw```json ⏎ { ⏎ "answer": "persist", ⏎ "explanation": "The persist method marks a new entity as managed by the EntityManager." ⏎ } ⏎ ``` | верно | persist() регистрирует объект в Unit of Work; INSERT выполняется на flush(). |
T14-L3 0.09 c | Doctrine | In Doctrine ORM 3, the EntityManager::merge() method exists and makes the passed object managed. | «yes» Пояснение: The EntityManager::merge() method is used to merge a detached entity into the persistence context, making it managed.
Raw```json ⏎ { ⏎ "answer": "true", ⏎ "explanation": "The EntityManager::merge() method is used to merge a detached entity into the persistence context, making it managed." ⏎ } ⏎ ``` | неверно верный: «no» | В ORM 3 merge() удалён (в vendor проекта 3.7.6 метода нет); в Doctrine 2.x merge() возвращал управляемую копию. Версия зафиксирована — ORM 3. |
T14-L4 0.09 c | Doctrine | DQL queries are written in terms of entities and their fields, not tables and columns. | «yes» Пояснение: DQL (Data Query Language) queries focus on entities and their fields rather than the underlying table and column structures.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "DQL (Data Query Language) queries focus on entities and their fields rather than the underlying table and column structures." ⏎ } ⏎ ``` | верно | Doctrine транслирует DQL в SQL; docs — DQL (Doctrine Query Language). |
T14-L5 0.08 c | Doctrine | What does $repository->find(999) return when no record with id 999 exists? | «json» Пояснение: ,
"explanation": "When no record is found, find() typically returns null."
}
```
Raw```json ⏎ { ⏎ "answer": null, ⏎ "explanation": "When no record is found, find() typically returns null." ⏎ } ⏎ ``` | неверно верный: «null» парсинг: текст (фолбэк) | find() возвращает null, если объект не найден (docs Repository methods). |
T14-L6 0.09 c | Doctrine | DoctrineBundle in Symfony automatically calls flush() at the end of every request. | «no» Пояснение: Doctrine does not automatically call flush() at the end of every request; it needs to be explicitly called.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "Doctrine does not automatically call flush() at the end of every request; it needs to be explicitly called." ⏎ } ⏎ ``` | верно | Авто-flush нет — flush() зовёт разработчик; незакрытая транзакция в конце запроса откатывается. |
T14-L7 0.09 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» Пояснение: While the Unit of Work tracks changes, flushing is the action that commits those changes to the database.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "While the Unit of Work tracks changes, flushing is the action that commits those changes to the database." ⏎ } ⏎ ``` | неверно верный: «yes» | Dirty checking сравнивает снимки свойств; persist нужен только новым/отсоединённым объектам. |
T14-L8 0.12 c | Doctrine | remove() executes the SQL DELETE immediately, without waiting for flush(). | «no» Пояснение: PDO's remove() method typically queues the operation; the actual execution depends on the connection's settings or explicit flush calls.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "PDO's remove() method typically queues the operation; the actual execution depends on the connection's settings or explicit flush calls." ⏎ } ⏎ ``` | верно | remove() планирует удаление в Unit of Work; DELETE выполняется на flush() (docs — Deleting Objects). |
T15-L1 0.08 c | PostgreSQL | PostgreSQL uses MVCC, therefore readers block writers and writers block readers. | «no» Пояснение: MVCC allows readers and writers to proceed concurrently without blocking each other.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "MVCC allows readers and writers to proceed concurrently without blocking each other." ⏎ } ⏎ ``` | верно | Наоборот: благодаря MVCC читатели не блокируют писателей и наоборот (снимки строк); docs PostgreSQL — Concurrency Control. |
T15-L2 0.08 c | PostgreSQL | Which SQL command shows a query's execution plan without executing the query? | «explain» Пояснение: The EXPLAIN command is used in SQL to show the execution plan of a query.
Raw```json ⏎ { ⏎ "answer": "EXPLAIN", ⏎ "explanation": "The EXPLAIN command is used in SQL to show the execution plan of a query." ⏎ } ⏎ ``` | верно | EXPLAIN без ANALYZE только строит план; проверено на PostgreSQL 17.7. |
T15-L3 0.1 c | PostgreSQL | SERIAL and GENERATED ... AS IDENTITY are just two names for the same mechanism. | «no» Пояснение: SERIAL and GENERATED AS IDENTITY are different syntax/feature names used in different SQL dialects for auto-incrementing primary keys.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "SERIAL and GENERATED AS IDENTITY are different syntax/feature names used in different SQL dialects for auto-incrementing primary keys." ⏎ } ⏎ ``` | верно | SERIAL — нестандартный макрос (sequence + DEFAULT), IDENTITY — SQL-стандарт; различаются владением и правами. Оба есть в PG 17 (проверено). |
T15-L4 0.09 c | PostgreSQL | By default, a PostgreSQL UNIQUE constraint allows only one row with NULL in the column. | «no» Пояснение: By default, a PostgreSQL UNIQUE constraint allows multiple rows with NULL values unless explicitly specified otherwise.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "By default, a PostgreSQL UNIQUE constraint allows multiple rows with NULL values unless explicitly specified otherwise." ⏎ } ⏎ ``` | верно | Наоборот: NULLS DISTINCT по умолчанию — несколько NULL допустимы; NULLS NOT DISTINCT — опция с PG 15. Проверено на PG 17.7. |
T15-L5 0.08 c | PostgreSQL | Which PostgreSQL aggregate function concatenates strings with a separator? | «string_agg» Пояснение: string_agg is the PostgreSQL function used to concatenate strings within a group.
Raw```json ⏎ { ⏎ "answer": "string_agg", ⏎ "explanation": "string_agg is the PostgreSQL function used to concatenate strings within a group." ⏎ } ⏎ ``` | верно | string_agg(значение, разделитель); проверено на PostgreSQL 17.7. |
T15-L6 0.09 c | PostgreSQL | Plain VACUUM returns the space occupied by dead tuples to the operating system. | «no» Пояснение: Plain VACUUM primarily marks dead tuples as reusable; it does not necessarily return space to the OS.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "Plain VACUUM primarily marks dead tuples as reusable; it does not necessarily return space to the OS." ⏎ } ⏎ ``` | верно | VACUUM помечает место для переиспользования внутри таблицы; ОС его возвращает только VACUUM FULL (с эксклюзивной блокировкой). |
T15-L7 0.09 c | PostgreSQL | Which keyword in a window function definition partitions rows into groups the function is computed over? | «partition by» Пояснение: The PARTITION BY clause is used in window functions to divide the rows into partitions.
Raw```json ⏎ { ⏎ "answer": "PARTITION BY", ⏎ "explanation": "The PARTITION BY clause is used in window functions to divide the rows into partitions." ⏎ } ⏎ ``` | верно | OVER (PARTITION BY ...); проверено на PostgreSQL 17.7. |
T15-L8 0.08 c | PostgreSQL | The READ COMMITTED isolation level protects against non-repeatable reads. | «no» Пояснение: The READ COMMITTED isolation level protects against dirty reads, not non-repeatable reads.
Raw```json ⏎ { ⏎ "answer": false, ⏎ "explanation": "The READ COMMITTED isolation level protects against dirty reads, not non-repeatable reads." ⏎ } ⏎ ``` | верно | READ COMMITTED допускает неповторяющееся чтение; защищает REPEATABLE READ. Проверено: SHOW transaction_isolation → read committed. |
T17-L1 0.09 c | PostgreSQL: transactions and indexes | By default, PostgreSQL wraps each single SQL statement in its own implicit transaction (autocommit). | «no» Пояснение: PostgreSQL operates in transaction mode by default, requiring explicit COMMIT or ROLLBACK.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "PostgreSQL operates in transaction mode by default, requiring explicit COMMIT or ROLLBACK." ⏎ } ⏎ ``` | неверно верный: «yes» | Без BEGIN каждый оператор коммитится сам; docs PostgreSQL — Transactions. Проверено на PG 17. |
T17-L2 0.08 c | PostgreSQL: transactions and indexes | Which SQL command ends a transaction, committing all its changes? | «commit» Пояснение: The COMMIT command permanently saves the changes made during the current transaction.
Raw```json ⏎ { ⏎ "answer": "COMMIT", ⏎ "explanation": "The COMMIT command permanently saves the changes made during the current transaction." ⏎ } ⏎ ``` | верно | COMMIT (END — синоним). Проверено на PG 17. |
T17-L3 0.08 c | PostgreSQL: transactions and indexes | Indexes speed up more than SELECT: UPDATE and DELETE with a search on an indexed column benefit too. | «no» Пояснение: Indexes primarily speed up SELECT operations, not UPDATE or DELETE operations directly.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "Indexes primarily speed up SELECT operations, not UPDATE or DELETE operations directly." ⏎ } ⏎ ``` | неверно верный: «yes» | Поиск строк для изменения идёт по индексу; docs PostgreSQL — Indexes. |
T17-L4 0.09 c | PostgreSQL: transactions and indexes | To roll back part of the statements inside a transaction, PostgreSQL uses SAVEPOINT. | «yes» Пояснение: SAVEPOINTs are used to mark points within a transaction to which you can roll back.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "SAVEPOINTs are used to mark points within a transaction to which you can roll back." ⏎ } ⏎ ``` | верно | SAVEPOINT name; ROLLBACK TO name — частичный откат без отмены всей транзакции. Проверено на PG 17. |
T17-L5 0.08 c | PostgreSQL: transactions and indexes | EXPLAIN ANALYZE shows the query plan without executing the query. | «yes» Пояснение: EXPLAIN ANALYZE displays the query plan along with the actual execution times.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "EXPLAIN ANALYZE displays the query plan along with the actual execution times." ⏎ } ⏎ ``` | неверно верный: «no» | Наоборот: ANALYZE реально выполняет запрос (с побочными эффектами!) и показывает фактические времена узлов; план без выполнения — plain EXPLAIN. |
T17-L6 0.07 c | PostgreSQL: transactions and indexes | Which PostgreSQL extension adds vector types and indexes for embedding search? | «pgvector» Пояснение: pgvector is the PostgreSQL extension that adds vector types and indexes for embedding search.
Raw```json ⏎ { ⏎ "answer": "pgvector", ⏎ "explanation": "pgvector is the PostgreSQL extension that adds vector types and indexes for embedding search." ⏎ } ⏎ ``` | верно | CREATE EXTENSION vector (проект pgvector; в проекте образ pgvector/pgvector:pg17). |
T17-L7 0.09 c | PostgreSQL: transactions and indexes | A partial index (CREATE INDEX ... WHERE ...) is built only over rows satisfying the condition. | «yes» Пояснение: A partial index is constructed only for rows that match the specified WHERE clause condition.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "A partial index is constructed only for rows that match the specified WHERE clause condition." ⏎ } ⏎ ``` | верно | docs PostgreSQL — Partial Indexes; типичный кейс — индекс по «активным» записям. |
T17-L8 0.12 c | PostgreSQL: transactions and indexes | The SERIALIZABLE level in PostgreSQL is implemented by locking the rows a transaction reads. | «no» Пояснение: SERIALIZABLE isolation level in PostgreSQL prevents write conflicts by checking for serialization anomalies, not just by locking read rows.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "SERIALIZABLE isolation level in PostgreSQL prevents write conflicts by checking for serialization anomalies, not just by locking read rows." ⏎ } ⏎ ``` | верно | SSI (Serializable Snapshot Isolation): предикатные блокировки на снимках, не блокировки прочитанных строк; docs PostgreSQL. |
T19-L1 0.1 c | HTTP and REST API | HTTP status 201 means the request resulted in a new resource being created. | «yes» Пояснение: HTTP status code 201 indicates that the request has succeeded and a new resource has been created.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "HTTP status code 201 indicates that the request has succeeded and a new resource has been created." ⏎ } ⏎ ``` | верно | 201 Created; обычно на POST, часто с Location; RFC 9110. |
T19-L2 0.1 c | HTTP and REST API | Which HTTP status means a successful request with an empty response body (e.g. after DELETE)? | «204» Пояснение: HTTP status code 204 No Content is used to indicate success where no content is returned in the response body.
Raw```json ⏎ { ⏎ "answer": 204, ⏎ "explanation": "HTTP status code 204 No Content is used to indicate success where no content is returned in the response body." ⏎ } ⏎ ``` | верно | 204 No Content; RFC 9110. |
T19-L3 0.1 c | HTTP and REST API | The DELETE method is idempotent per the HTTP specification: repeating the request for the same resource does not change the outcome. | «no» Пояснение: DELETE is generally not considered idempotent as subsequent requests might return a different status code (e.g., 404 Not Found) if the resource is already deleted.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "DELETE is generally not considered idempotent as subsequent requests might return a different status code (e.g., 404 Not Found) if the resource is already deleted." ⏎ } ⏎ ``` | неверно верный: «yes» | RFC 9110: DELETE идемпотентен (как PUT); идемпотентность ≠ безопасность — ресурс удаляется при первом вызове. |
T19-L4 0.09 c | HTTP and REST API | The Access-Control-Allow-Origin header is sent by the client so that the server agrees to accept requests from another origin. | «no» Пояснение: The Access-Control-Allow-Origin header is sent by the server to the client to specify which origins are allowed to access the resource.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "The Access-Control-Allow-Origin header is sent by the server to the client to specify which origins are allowed to access the resource." ⏎ } ⏎ ``` | верно | Наоборот: заголовок шлёт СЕРВЕР в ответе, разрешая браузеру cross-origin запрос (CORS); в проекте nelmio/cors-bundle. |
T19-L5 0.09 c | HTTP and REST API | Status 429 Too Many Requests is used when a client exceeds a rate limit. | «yes» Пояснение: HTTP status code 429 indicates that the user has sent too many requests in a given amount of time.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "HTTP status code 429 indicates that the user has sent too many requests in a given amount of time." ⏎ } ⏎ ``` | верно | 429 (+ Retry-After); RFC 6585. В проекте symfony/rate-limiter. |
T19-L6 0.07 c | HTTP and REST API | 5xx codes mean a client error, while 4xx means a server-side error. | «no» Пояснение: 5xx codes indicate server errors, while 4xx codes indicate client errors.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "5xx codes indicate server errors, while 4xx codes indicate client errors." ⏎ } ⏎ ``` | верно | Наоборот: 4xx — ошибка клиента (400, 404), 5xx — сервера (500, 503); классы статусов RFC 9110. |
T19-L7 0.08 c | HTTP and REST API | Which HTTP header indicates the MIME type of the request or response body? | «content-type» Пояснение: The Content-Type header specifies the media type of the resource being sent.
Raw```json ⏎ { ⏎ "answer": "Content-Type", ⏎ "explanation": "The Content-Type header specifies the media type of the resource being sent." ⏎ } ⏎ ``` | верно | Content-Type: application/json и т.п. |
T19-L8 0.08 c | HTTP and REST API | PATCH is not required to be idempotent per RFC 5789, unlike PUT. | «no» Пояснение: Both PUT and PATCH operations can be designed to be idempotent according to HTTP specifications.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "Both PUT and PATCH operations can be designed to be idempotent according to HTTP specifications." ⏎ } ⏎ ``` | неверно верный: «yes» | RFC 5789 прямо оговаривает: PATCH не гарантированно идемпотентен; PUT идемпотентен. |
T20-L1 0.12 c | Security and OAuth | Checking a password by comparing its hash to the stored hash with a plain == is sufficient. | «no» Пояснение: Using a plain equality check is insecure for password comparison due to timing attacks; use a constant-time comparison function instead.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "Using a plain equality check is insecure for password comparison due to timing attacks; use a constant-time comparison function instead." ⏎ } ⏎ ``` | верно | Нужна постоянновременная проверка (password_verify) — timing-атаки; соль и алгоритм уже внутри хеша. |
T20-L2 0.09 c | Security and OAuth | A CSRF token is issued by the server (bound to the session) and verified server-side on unsafe requests (POST etc.). | «yes» Пояснение: CSRF tokens are server-generated and validated on state-changing requests.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "CSRF tokens are server-generated and validated on state-changing requests." ⏎ } ⏎ ``` | верно | symfony/security-csrf в проекте; защита от подделки межсайтовой формы. |
T20-L3 0.08 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 define the CSP policy.
Raw```json ⏎ { ⏎ "answer": "Content-Security-Policy", ⏎ "explanation": "The Content-Security-Policy header is used to define the CSP policy." ⏎ } ⏎ ``` | верно | Content-Security-Policy; белые списки источников скриптов/стилей против XSS. |
T20-L4 0.1 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 strictly an authentication protocol; the access token grants permission to access resources.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "OAuth 2.0 is an authorization framework, not strictly an authentication protocol; the access token grants permission to access resources." ⏎ } ⏎ ``` | верно | OAuth 2.0 — авторизация/делегирование доступа; аутентификацию добавляет OpenID Connect. В проекте knpuniversity/oauth2-client-bundle (yandex/github/google). |
T20-L5 0.12 c | Security and OAuth | XSS is prevented by validating input on the server before writing it to the database. | «no» Пояснение: XSS is primarily prevented by output encoding/escaping data when rendering it in the browser, not solely server-side input validation.
Raw```json ⏎ { ⏎ "answer": false, ⏎ "explanation": "XSS is primarily prevented by output encoding/escaping data when rendering it in the browser, not solely server-side input validation." ⏎ } ⏎ ``` | верно | XSS лечится контекстным экранированием НА ВЫВОДЕ (Twig autoescape, CSP); валидация ввода не покрывает все контексты вывода. |
T20-L6 0.09 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? | «authorization_code» Пояснение: The authorization code is the token exchanged for an access token in the token endpoint.
Raw```json ⏎ { ⏎ "answer": "authorization_code", ⏎ "explanation": "The authorization code is the token exchanged for an access token in the token endpoint." ⏎ } ⏎ ``` | неверно верный: «code» | Параметр code; обмен на токен POST-ом на /token с client_secret. |
T20-L7 0.08 c | Security and OAuth | A refresh token lives longer than an access token and allows obtaining a new access token without the user logging in again. | «yes» Пояснение: Refresh tokens are longer-lived and are used to obtain new access tokens securely.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "Refresh tokens are longer-lived and are used to obtain new access tokens securely." ⏎ } ⏎ ``` | верно | Стандартная схема OAuth/OIDC: короткий access + длинный refresh. |
T20-L8 0.09 c | Security and OAuth | A password salt must be kept secret: without it the hash cannot be verified. | «no» Пояснение: The password salt does not need to be kept secret; it is stored alongside the hash to allow for verification.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "The password salt does not need to be kept secret; it is stored alongside the hash to allow for verification." ⏎ } ⏎ ``` | верно | Соль хранится открыто (password_hash включает её в строку хеша); секретность соли не нужна. |
T18-L1 0.1 c | Testing: PHPUnit | PHPUnit runs test methods of any class — extending TestCase is not required. | «no» Пояснение: Extending TestCase is generally required to gain access to useful testing methods provided by PHPUnit.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "Extending TestCase is generally required to gain access to useful testing methods provided by PHPUnit." ⏎ } ⏎ ``` | верно | Тестом считается метод класса, наследующего TestCase (PHPUnit 10). |
T18-L2 0.08 c | Testing: PHPUnit | In PHPUnit, setUp() runs once before all tests of the class. | «no» Пояснение: setUp() runs before each test method, not once before all tests.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "setUp() runs before each test method, not once before all tests." ⏎ } ⏎ ``` | верно | setUp() — перед КАЖДЫМ тестом; один раз на класс — setUpBeforeClass(). Проверено живым счётчиком на PHPUnit 10.5. |
T18-L3 0.08 c | Testing: PHPUnit | A data provider lets a test run with exactly one set of arguments. | «no» Пояснение: A data provider can be configured to return multiple sets of arguments.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "A data provider can be configured to return multiple sets of arguments." ⏎ } ⏎ ``` | верно | Наоборот: наборов может быть сколько угодно — тест выполняется по разу на каждый. Проверено на PHPUnit 10.5 (#[DataProvider]). |
T18-L4 0.09 c | Testing: PHPUnit | Which PHPUnit method declares an expectation that an exception of a given class is thrown? | «expectexception» Пояснение: The expectException method is used in PHPUnit to assert that an exception of a specific type is thrown.
Raw```json ⏎ { ⏎ "answer": "expectException", ⏎ "explanation": "The expectException method is used in PHPUnit to assert that an exception of a specific type is thrown." ⏎ } ⏎ ``` | верно | $this->expectException(\LogicException::class); проверено на PHPUnit 10.5. |
T18-L5 0.08 c | Testing: PHPUnit | In PHPUnit, a stub verifies which methods were called on it, while a mock only returns data. | «no» Пояснение: Mocks are used to verify interactions, whereas stubs are used to provide canned answers.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "Mocks are used to verify interactions, whereas stubs are used to provide canned answers." ⏎ } ⏎ ``` | верно | Наоборот: стаб подставляет данные, мок проверяет взаимодействия (createStub/createMock); docs PHPUnit — Test Doubles. |
T18-L6 0.09 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» Пояснение: The #[DataProvider] attribute is the modern, recommended way to provide data for tests in PHPUnit.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "The #[DataProvider] attribute is the modern, recommended way to provide data for tests in PHPUnit." ⏎ } ⏎ ``` | верно | Аннотация ещё парсится в PHPUnit 10/11 (AnnotationParser в 10.5.66), удаление — в 12; атрибут — стандарт. |
T18-L7 0.1 c | Testing: PHPUnit | PHPUnit does not allow one test to depend on the result of another. | «no» Пояснение: PHPUnit allows tests to depend on the results of other tests using test groups or specific setup mechanisms.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "PHPUnit allows tests to depend on the results of other tests using test groups or specific setup mechanisms." ⏎ } ⏎ ``` | верно | Зависимости есть: #[Depends] — зависимый тест не запустится, еслиProducer упал. |
T18-L8 0.07 c | Testing: PHPUnit | Which PHPUnit command-line option makes tests run in random order? | «random» Пояснение: The --random option is used to run tests in a random order.
Raw```json ⏎ { ⏎ "answer": "random", ⏎ "explanation": "The --random option is used to run tests in a random order." ⏎ } ⏎ ``` | неверно верный: «--order-by=random» | --order-by=random (PHPUnit 9+); опция есть в --help PHPUnit 10.5 (проектная). |
T01-L9 2.54 c | Syntax and operators | What does this code output?
```php
echo intdiv(7, 2) . intdiv(-7, 2);
``` | «-4 -4» Пояснение: intdiv performs integer division, truncating towards zero for negative numbers.
Raw```json ⏎ { ⏎ "answer": "-4 -4", ⏎ "explanation": "intdiv performs integer division, truncating towards zero for negative numbers." ⏎ } ⏎ ``` | неверно верный: «3-3» | intdiv truncates toward zero: intdiv(-7, 2) = -3, not -4. |
T01-L10 0.08 c | Syntax and operators | What does this code output?
```php
echo -3 ** 2;
``` | «9» Пояснение: The code calculates the power of -3 squared, which is 9.
Raw```json ⏎ { ⏎ "answer": 9, ⏎ "explanation": "The code calculates the power of -3 squared, which is 9." ⏎ } ⏎ ``` | неверно верный: «-9» | ** is right-associative and binds tighter than unary minus: -(3²). |
T02-L9 0.08 c | Types and comparisons | What does this code output?
```php
echo '1e1' == '10' ? 'true' : 'false';
``` | «false» Пояснение: The string '1e1' is not equal to the string '10'.
Raw```json ⏎ { ⏎ "answer": "false", ⏎ "explanation": "The string '1e1' is not equal to the string '10'." ⏎ } ⏎ ``` | неверно верный: «true» | Both strings are numeric — compared as numbers: 10 == 10. |
T02-L10 0.09 c | Types and comparisons | What does this code output?
```php
switch ('a') {
case 0: echo 'zero'; break;
default: echo 'other';
}
``` | «other» Пояснение: Since 'a' does not match the case 0, the default case is executed.
Raw```json ⏎ { ⏎ "answer": "other", ⏎ "explanation": "Since 'a' does not match the case 0, the default case is executed." ⏎ } ⏎ ``` | верно | PHP 8: 'a' == 0 → false (used to be true) — default fires. |
T03-L9 0.1 c | Strings | What does this code output?
```php
echo strtr('abc', ['a' => '1', 'ab' => '2']);
``` | «1» Пояснение: strtr replaces substrings within a string based on an associative array.
Raw```json ⏎ { ⏎ "answer": "1", ⏎ "explanation": "strtr replaces substrings within a string based on an associative array." ⏎ } ⏎ ``` | неверно верный: «2c» | strtr with an array prefers the longest matching key. |
T03-L10 0.14 c | Strings | What does this code output?
```php
echo '[' . substr('hello', -10) . ']';
``` | «['l']» Пояснение: substr('hello', -10) extracts the last 10 characters from the string 'hello', which results in 'hello' itself, and then it is enclosed in square brackets.
Raw```json ⏎ { ⏎ "answer": "['l']", ⏎ "explanation": "substr('hello', -10) extracts the last 10 characters from the string 'hello', which results in 'hello' itself, and then it is enclosed in square brackets." ⏎ } ⏎ ``` | неверно верный: «[hello]» | A negative start beyond the string is clamped to the beginning. |
T04-L9 0.12 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,m» Пояснение: The '+' operator for arrays merges them, and array_keys extracts the keys, which are then joined by a comma.
Raw```json ⏎ { ⏎ "answer": "k,m", ⏎ "explanation": "The '+' operator for arrays merges them, and array_keys extracts the keys, which are then joined by a comma." ⏎ } ⏎ ``` | неверно верный: «k,n,m» | The + operator: on duplicate string keys the left array wins. |
T04-L10 0.26 c | Arrays | What does this code output?
```php
$a = [[1, 'x', 2], [2, 'y', 1], [3, 'z', 2]];
usort($a, fn($p, $q) => $p[2] <=> $q[2]);
echo implode('', array_column($a, 1));
``` | «xyz» Пояснение: The array is sorted based on the third element (index 2) of each inner array, which are 2, 1, and 2, resulting in the order [2, 'y', 1], [1, 'x', 2], [3, 'z', 2] if stable sort was not guaranteed, but the final output depends on the order of the second elements, which are 'y', 'x', 'z' after sorting based on the third element.
Raw```json ⏎ { ⏎ "answer": "xyz", ⏎ "explanation": "The array is sorted based on the third element (index 2) of each inner array, which are 2, 1, and 2, resulting in the order [2, 'y', 1], [1, 'x', 2], [3, 'z', 2] if stable sort was not guaranteed, but the final output depends on the order of the second elements, which are 'y', 'x', 'z' after sorting based on the third element." ⏎ } ⏎ ``` | неверно верный: «yxz» | Sorts are stable since 8.0: x and z keep their order on a tie. |
T05-L10 4.05 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]);
``` | «1» Пояснение: The spread operator unpacks the array into arguments, and the function returns 5 - 1.
Raw```json ⏎ { ⏎ "answer": "1", ⏎ "explanation": "The spread operator unpacks the array into arguments, and the function returns 5 - 1." ⏎ } ⏎ ``` | неверно верный: «4» | String keys of a spread array become named arguments. |
T05-L9 0.96 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();
``` | «0» Пояснение: The method call `$f()` on `$f` results in a fatal error because `$f` is an integer, but if we assume `$f` was meant to be the result of the method call and then called, the original code is flawed, but based on the structure, `$f` is the integer 3, and calling an integer throws an error, but if the intention was to call the method on an object, the null assignment prevents further calls.
Raw```json ⏎ { ⏎ "answer": "0", ⏎ "explanation": "The method call `$f()` on `$f` results in a fatal error because `$f` is an integer, but if we assume `$f` was meant to be the result of the method call and then called, the original code is flawed, but based on the structure, `$f` is the integer 3, and calling an integer throws an error, but if the intention was to call the method on an object, the null assignment prevents further calls." ⏎ } ⏎ ``` | неверно верный: «3» | First-class callable syntax binds $this at creation time. |
T06-L9 0.09 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 static call resolves to the class name of the class being instantiated, which is B.
Raw```json ⏎ { ⏎ "answer": "B", ⏎ "explanation": "The static call resolves to the class name of the class being instantiated, which is B." ⏎ } ⏎ ``` | верно | Late static binding: static::class is the receiver's class. |
T06-L10 0.1 c | OOP: classes and inheritance | What does this code output on PHP 8.5?
```php
class C
{
public int $x = 0 {
set { $this->x = $value * 2; }
}
}
$c = new C;
$c->x = 5;
echo $c->x;
``` | «10» Пояснение: The setter method multiplies the input value by 2, so 5 becomes 10.
Raw```json ⏎ { ⏎ "answer": 10, ⏎ "explanation": "The setter method multiplies the input value by 2, so 5 becomes 10." ⏎ } ⏎ ``` | верно | Inside the set hook, $this->x writes the backing store (no recursion): 5*2. |
T07-L9 0.1 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 order of trait resolution determines which function is called, and the alias 'g' points to the function from TA.
Raw```json ⏎ { ⏎ "answer": "BA", ⏎ "explanation": "The order of trait resolution determines which function is called, and the alias 'g' points to the function from TA." ⏎ } ⏎ ``` | верно | insteadof picks the implementation; as keeps the other under an alias. |
T07-L10 0.11 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» Пояснение: The static property is shared across classes using the trait, and setting it in one class affects all classes using the trait.
Raw```json ⏎ { ⏎ "answer": 1, ⏎ "explanation": "The static property is shared across classes using the trait, and setting it in one class affects all classes using the trait." ⏎ } ⏎ ``` | неверно верный: «0» | A trait's static property is copied into each consuming class. |
T08-L10 0.09 c | Exceptions and errors | What does this code output?
```php
function f(): int
{
try { return 1; } finally { return 2; }
}
echo f();
``` | «2» Пояснение: The return value of a finally block overrides any return value from the try block.
Raw```json ⏎ { ⏎ "answer": 2, ⏎ "explanation": "The return value of a finally block overrides any return value from the try block." ⏎ } ⏎ ``` | верно | A return in finally overrides the return from try. |
T08-L9 0.08 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 LogicException thrown in the finally block is caught and its message is echoed.
Raw```json ⏎ { ⏎ "answer": "second", ⏎ "explanation": "The LogicException thrown in the finally block is caught and its message is echoed." ⏎ } ⏎ ``` | верно | An exception from finally replaces the in-flight one — the last thrown is caught. |
T09-L9 0.11 c | Namespaces and autoloading | What does this code output?
```php
namespace N;
use App\Foo as Baz;
echo Baz::class . '|' . \Baz::class;
``` | «n\app\foo|n\app\foo» Пояснение: The code echoes the fully qualified class names of the imported classes.
Raw```json ⏎ { ⏎ "answer": "N\\App\\Foo|N\\App\\Foo", ⏎ "explanation": "The code echoes the fully qualified class names of the imported classes." ⏎ } ⏎ ``` | неверно верный: «app\foo|baz» | The use alias applies to unqualified names; a leading \ escapes to the global scope. |
T09-L10 0.1 c | Namespaces and autoloading | What does this code output?
```php
namespace Ns;
class Foo {}
$c = 'Foo';
echo (class_exists($c) ? 'yes' : 'no')
. (class_exists(__NAMESPACE__ . '\\' . $c) ? 'yes' : 'no');
``` | «no» Пояснение: The class 'Foo' is not defined in the current namespace, so class_exists returns false for both checks.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "The class 'Foo' is not defined in the current namespace, so class_exists returns false for both checks." ⏎ } ⏎ ``` | неверно верный: «noyes» | Dynamic names are not resolved against the namespace — 'Foo' is the global class. |
T10-L9 0.12 c | References and scope | What does this code output?
```php
$a = [1, 2, 3];
foreach ($a as &$v) {}
$v = 99;
echo implode(',', $a);
``` | «1,2,3» Пояснение: The foreach loop iterates over the array, and modifying $v modifies the elements of the array because of the reference (&).
Raw```json ⏎ { ⏎ "answer": "1,2,3", ⏎ "explanation": "The foreach loop iterates over the array, and modifying $v modifies the elements of the array because of the reference (&)." ⏎ } ⏎ ``` | неверно верный: «1,2,99» | After a by-ref foreach, $v remains a reference to the last element. |
T10-L10 0.13 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();
``` | «2» Пояснение: The static variable $n is shared across instances of class A and B, so the calls increment the same counter.
Raw```json ⏎ { ⏎ "answer": "2", ⏎ "explanation": "The static variable $n is shared across instances of class A and B, so the calls increment the same counter." ⏎ } ⏎ ``` | неверно верный: «3» | A method's static variable belongs to the parent's method — subclasses share it. |
T11-L9 0.12 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, the value sent (10) is received by yield, and the function returns 10 + 1, which is 11.
Raw```json ⏎ { ⏎ "answer": "11", ⏎ "explanation": "The generator yields 1, the value sent (10) is received by yield, and the function returns 10 + 1, which is 11." ⏎ } ⏎ ``` | верно | send() resumes the generator: $x = 10, return 10+1. |
T11-L10 0.13 c | Generators, iterators, SPL | What does this code output?
```php
function inner(): Generator
{
yield 1;
yield 2;
return 'ok';
}
function outer(): Generator
{
$r = yield from inner();
yield $r;
}
echo implode(',', iterator_to_array(outer()));
``` | «1,2» Пояснение: The generator yields values from inner(), and outer() yields the yielded values from inner(), which are then joined by a comma.
Raw```json ⏎ { ⏎ "answer": "1,2", ⏎ "explanation": "The generator yields values from inner(), and outer() yields the yielded values from inner(), which are then joined by a comma." ⏎ } ⏎ ``` | неверно верный: «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.16 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';
``` | «no» Пояснение: The cost factor is 4, and rehash will only be needed if the cost is increased.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "The cost factor is 4, and rehash will only be needed if the cost is increased." ⏎ } ⏎ ``` | неверно верный: «noyes» | password_needs_rehash compares the hash's options with the target: cost 4 = 4 → 'no', cost 5 ≠ 4 → 'yes'. |
T12-L10 0.44 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 is a large integer, and bitwise AND with 2048 will likely result in a non-zero value, making the condition false.
Raw```json ⏎ { ⏎ "answer": "strict-in", ⏎ "explanation": "E_ALL is a large integer, and bitwise AND with 2048 will likely result in a non-zero value, making the condition false." ⏎ } ⏎ ``` | неверно верный: «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.39 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» Пояснение: The code checks if the 'X-Token' header value matches 'abc', which it does.
Raw```json ⏎ { ⏎ "answer": "mapped", ⏎ "explanation": "The code checks if the 'X-Token' header value matches 'abc', which it does." ⏎ } ⏎ ``` | верно | 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.13 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;
``` | «abc» Пояснение: Event listeners are executed in the order of their priority, with lower numbers executing first, and multiple listeners for the same event are executed sequentially.
Raw```json ⏎ { ⏎ "answer": "ABC", ⏎ "explanation": "Event listeners are executed in the order of their priority, with lower numbers executing first, and multiple listeners for the same event are executed sequentially." ⏎ } ⏎ ``` | неверно верный: «bca» | Listeners run by descending priority: 10 (B), 5 (C), 0 (A). |
T14-L10 0.43 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» Пояснение: find() will return the same managed entity instance if the ID exists.
Raw```json ⏎ { ⏎ "answer": "same", ⏎ "explanation": "find() will return the same managed entity instance if the ID exists." ⏎ } ⏎ ``` | верно | Identity map: a second find for the same id returns the same instance. |
T14-L9 0.33 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» Пояснение: The user is persisted and then removed, resulting in an empty table.
Raw```json ⏎ { ⏎ "answer": "0", ⏎ "explanation": "The user is persisted and then removed, resulting in an empty table." ⏎ } ⏎ ``` | верно | The unit of work schedules INSERT at flush: remove after persist cancels it. |
T15-L10 0.5 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;
``` | «2» Пояснение: The query counts the non-NULL values in the table, which are 1 and the row with a NULL value.
Raw```json ⏎ { ⏎ "answer": 2, ⏎ "explanation": "The query counts the non-NULL values in the table, which are 1 and the row with a NULL value." ⏎ } ⏎ ``` | неверно верный: «1» | count(column) skips NULLs; count(*) would return 2. |
T15-L9 0.44 c | PostgreSQL | What does this SQL query return (PostgreSQL 17)?
```sql
CREATE TEMP TABLE t (id int, x int);
INSERT INTO t VALUES (1, 10), (2, 20), (3, 30);
SELECT string_agg(s::text, ',' ORDER BY id) FROM (
SELECT id, sum(x) OVER (ORDER BY id) AS s FROM t
) q;
``` | «10,30,50» Пояснение: The query calculates the cumulative sum of x ordered by id and then aggregates the resulting values as a comma-separated string.
Raw```json ⏎ { ⏎ "answer": "10,30,50", ⏎ "explanation": "The query calculates the cumulative sum of x ordered by id and then aggregates the resulting values as a comma-separated string." ⏎ } ⏎ ``` | неверно верный: «10,30,60» | With ORDER BY the default window frame is running (start to current row). |
T16-L9 0.12 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 Trace middleware echoes its tag before passing the envelope to the next middleware, which will also echo its tag.
Raw```json ⏎ { ⏎ "answer": "M1M2", ⏎ "explanation": "The Trace middleware echoes its tag before passing the envelope to the next middleware, which will also echo its tag." ⏎ } ⏎ ``` | верно | The first-added middleware runs first (outermost). |
T16-L10 0.11 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;
``` | «10» Пояснение: The first handler increments $n by 1, and the second handler increments $n by 10, resulting in $n being 10.
Raw```json ⏎ { ⏎ "answer": "10", ⏎ "explanation": "The first handler increments $n by 1, and the second handler increments $n by 10, resulting in $n being 10." ⏎ } ⏎ ``` | неверно верный: «11» | All registered handlers of the message run: 1 + 10 = 11. |
T17-L9 0.09 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 table will contain only one unique entry, so the count will be 1.
Raw```json ⏎ { ⏎ "answer": 1, ⏎ "explanation": "The table will contain only one unique entry, so the count will be 1." ⏎ } ⏎ ``` | верно | ON CONFLICT DO NOTHING skips the duplicate: one insert. |
T17-L10 0.1 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;
``` | «1» Пояснение: The UNIQUE constraint prevents the second insert of the same value, so only one row is successfully inserted.
Raw```json ⏎ { ⏎ "answer": "1", ⏎ "explanation": "The UNIQUE constraint prevents the second insert of the same value, so only one row is successfully inserted." ⏎ } ⏎ ``` | неверно верный: «2» | DEFERRED postpones the uniqueness check to COMMIT — count sees 2 rows. |
T18-L9 0.12 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) | «1» Пояснение: The command filters tests to run only 'test_sum', which is covered by the data provider, resulting in one test execution.
Raw```json ⏎ { ⏎ "answer": "1", ⏎ "explanation": "The command filters tests to run only 'test_sum', which is covered by the data provider, resulting in one test execution." ⏎ } ⏎ ``` | неверно верный: «6» | --filter is a substring match: test_sum also matches test_sum_abs (3+3 datasets). |
T18-L10 0.2 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,2» Пояснение: The DataProvider provides two test cases, and both will fail because the assertion $x > 0 is false for both 1 and -1.
Raw```json ⏎ { ⏎ "answer": "2,2", ⏎ "explanation": "The DataProvider provides two test cases, and both will fail because the assertion $x > 0 is false for both 1 and -1." ⏎ } ⏎ ``` | неверно верный: «2,1» | 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.11 c | HTTP and REST API | Which HTTP method does this command send?
```bash
curl -s -d 'a=1' http://demo.local/api
``` | «post» Пояснение: The `-d` flag in curl is used to send data in the body of an HTTP request, typically used with POST requests.
Raw```json ⏎ { ⏎ "answer": "POST", ⏎ "explanation": "The `-d` flag in curl is used to send data in the body of an HTTP request, typically used with POST requests." ⏎ } ⏎ ``` | верно | -d/-F switches curl to POST by default. |
T19-L10 0.12 c | HTTP and REST API | Which HTTP method does this command send?
```bash
curl -s -G -d 'a=1' http://demo.local/api
``` | «post» Пояснение: The `-d` flag in curl is used to send data in the body of the request, typically used with POST or PUT methods.
Raw```json ⏎ { ⏎ "answer": "POST", ⏎ "explanation": "The `-d` flag in curl is used to send data in the body of the request, typically used with POST or PUT methods." ⏎ } ⏎ ``` | неверно верный: «get» | -G turns -d data into the query string; the method stays GET. |
T20-L9 0.09 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? | «401» Пояснение: A non-existent client_id typically results in a 401 Unauthorized error.
Raw```json ⏎ { ⏎ "answer": 401, ⏎ "explanation": "A non-existent client_id typically results in a 401 Unauthorized error." ⏎ } ⏎ ``` | неверно верный: «invalid_client» | Unknown client → invalid_client (RFC 6749 §5.2). |
T20-L10 0.09 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? | «no» Пояснение: The access_token is typically returned in the body of the redirect response, not in the redirect_uri.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "The access_token is typically returned in the body of the redirect response, not in the redirect_uri." ⏎ } ⏎ ``` | неверно верный: «fragment» | The implicit flow passes the token in the URL fragment (#) — it never reaches the server. |
T21-L9 1.09 c | Twig | What does this Twig template output?
```twig
{{ false|default(2) * 3 }}
``` | «6» Пояснение: The `default(2)` provides the value 2 when `false` is falsey, and then the expression becomes `2 * 3`, which is 6.
Raw```json ⏎ { ⏎ "answer": 6, ⏎ "explanation": "The `default(2)` provides the value 2 when `false` is falsey, and then the expression becomes `2 * 3`, which is 6." ⏎ } ⏎ ``` | верно | default replaces exactly false/null/''/[] — false becomes 2, 2*3 = 6; the naive 'default is for undefined only' yields 0. |
T21-L10 0.08 c | Twig | What exception class does render() of this template throw?
```twig
{{ 'a' ~ 1 + 2 }}
``` | «none» Пояснение: The provided Twig template code is a simple expression and does not inherently throw an exception.
Raw```json ⏎ { ⏎ "answer": "none", ⏎ "explanation": "The provided Twig template code is a simple expression and does not inherently throw an exception." ⏎ } ⏎ ``` | неверно верный: «runtimeerror» | In Twig ~ binds tighter than +: ('a' ~ 1) + 2 → string + int → a render error (RuntimeError). |
T22-L9 0.1 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()]));
``` | «2» Пояснение: The validation process counts two constraints: one for the empty string and one for 'NotBlank'.
Raw```json ⏎ { ⏎ "answer": "2", ⏎ "explanation": "The validation process counts two constraints: one for the empty string and one for 'NotBlank'." ⏎ } ⏎ ``` | неверно верный: «0» | NotBlank treats null, '', [] as blank — the array [''] is not blank. |
T22-L10 0.09 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» Пояснение: The TextType form is considered valid by default as it has no required fields.
Raw```json ⏎ { ⏎ "answer": "valid", ⏎ "explanation": "The TextType form is considered valid by default as it has no required fields." ⏎ } ⏎ ``` | неверно верный: «symfony\component\form\exception\logicexception» | isValid() on a non-submitted form throws LogicException, it does not return false. |
T23-L9 0.09 c | Symfony: configuration and services | What does this code output?
```php
use Symfony\Component\DependencyInjection\ContainerBuilder;
$c = new ContainerBuilder();
$c->register('a', stdClass::class)->setPublic(true);
$c->compile();
echo spl_object_id($c->get('a')) === spl_object_id($c->get('a')) ? 'same' : 'diff';
``` | «same» Пояснение: The code retrieves the same object instance from the container and compares their object IDs.
Raw```json ⏎ { ⏎ "answer": "same", ⏎ "explanation": "The code retrieves the same object instance from the container and compares their object IDs." ⏎ } ⏎ ``` | верно | Container services are shared: two get() calls yield one instance. |
T23-L10 0.41 c | Symfony: configuration and services | What does this code output?
```php
use Symfony\Component\DependencyInjection\ContainerBuilder;
$c = new ContainerBuilder();
$c->setParameter('name', 'Bob');
$c->setParameter('greeting', 'hi %name%');
$c->setParameter('message', '%greeting%!');
$c->compile();
echo $c->getParameter('message');
``` | «hi bob!» Пояснение: The code sets parameters and then retrieves the compiled message, which substitutes the 'name' parameter.
Raw```json ⏎ { ⏎ "answer": "hi Bob!", ⏎ "explanation": "The code sets parameters and then retrieves the compiled message, which substitutes the 'name' parameter." ⏎ } ⏎ ``` | верно | compile() resolves %-references transitively: %greeting% → 'hi %name%' → 'hi Bob!', the answer assembles over two hops. |
T24-L9 0.11 c | Bootstrap | What is the max-width of .container in Bootstrap 5.3 at a 992px viewport? | «1140px» Пояснение: Bootstrap 5.3 defines the max-width for .container at 992px as 1140px.
Raw```json ⏎ { ⏎ "answer": "1140px", ⏎ "explanation": "Bootstrap 5.3 defines the max-width for .container at 992px as 1140px." ⏎ } ⏎ ``` | неверно верный: «960» | 5.x container widths: 540/720/960/1140/1320 (sm–xxl); 992 → 960px. |
T24-L10 0.09 c | Bootstrap | Which utility sets the text color in Bootstrap 5.3 for `<p class="text-danger text-primary">…</p>`? Answer with the winning class name. | «text-danger» Пояснение: The text-danger class sets the text color to the danger color in Bootstrap.
Raw```json ⏎ { ⏎ "answer": "text-danger", ⏎ "explanation": "The text-danger class sets the text color to the danger color in Bootstrap." ⏎ } ⏎ ``` | верно | Specificity ties — the later rule wins: text-danger is declared after text-primary. |
T25-L9 0.1 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 violates the rule Application -> Domain and Infrastructure -> Domain, Application.
Raw```json ⏎ { ⏎ "answer": 2, ⏎ "explanation": "The class violates the rule Application -> Domain and Infrastructure -> Domain, Application." ⏎ } ⏎ ``` | верно | Domain may depend only on Domain: PlaceOrder (Application) + Db (Infrastructure) = 2. |
T25-L10 0.12 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,
) {}
}
``` | «1» Пояснение: The dependency App\Infrastructure\Logger in Domain layer violates the rule that Domain should only depend on Domain.
Raw```json ⏎ { ⏎ "answer": 1, ⏎ "explanation": "The dependency App\Infrastructure\Logger in Domain layer violates the rule that Domain should only depend on Domain." ⏎ } ⏎ ``` | неверно верный: «3» | 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;
``` | «15,15» Пояснение: The code creates two Money objects, adds their amounts, and then prints the amounts of the original and the result.
Raw```json ⏎ { ⏎ "answer": "15,15", ⏎ "explanation": "The code creates two Money objects, adds their amounts, and then prints the amounts of the original and the result." ⏎ } ⏎ ``` | неверно верный: «10,15» | The VO is immutable: add() returns a new instance; the original is unchanged. |
T26-L9 0.39 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();
``` | «0» Пояснение: The item 'a' is removed, so the count of items is zero.
Raw```json ⏎ { ⏎ "answer": 0, ⏎ "explanation": "The item 'a' is removed, so the count of items is zero." ⏎ } ⏎ ``` | неверно верный: «1» | The failed remove leaves aggregate state unchanged: the invariant threw before unset — count stays 1. |
VC-L9 2.6 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 the hi method, which returns the string 'hi'.
Raw```json ⏎ { ⏎ "answer": "hi", ⏎ "explanation": "The code instantiates class C and calls the hi method, which returns the string 'hi'." ⏎ } ⏎ ``` | верно | Since 8.4, new in a method chain works without wrapping parentheses. |
VC-L10 2.65 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';
``` | «no» Пояснение: The lazy object is initialized immediately upon access, so isUninitializedLazyObject returns false.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "The lazy object is initialized immediately upon access, so isUninitializedLazyObject returns false." ⏎ } ⏎ ``` | неверно верный: «yesno» | newLazyGhost (8.4): the object stays lazy until first access — reading a property initializes it and clears the flag. |
T28-L9 0.1 c | Symfony: versions | The project was upgraded from Symfony 6.4 to 8.1. What does this code output on 8.1?
```php
echo class_exists(\Symfony\Component\Security\Guard\AbstractGuardAuthenticator::class)
? 'yes' : 'no';
``` | «no» Пояснение: The class path for the security authenticator changed significantly between Symfony 6 and 8.
Raw```json ⏎ { ⏎ "answer": "no", ⏎ "explanation": "The class path for the security authenticator changed significantly between Symfony 6 and 8." ⏎ } ⏎ ``` | верно | Guard authentication was removed in Symfony 7.0 — the class is gone in 8.1. |
T28-L10 0.07 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';
``` | «yes» Пояснение: Both class names exist in Symfony 8.1.
Raw```json ⏎ { ⏎ "answer": "yes", ⏎ "explanation": "Both class names exist in Symfony 8.1." ⏎ } ⏎ ``` | неверно верный: «noyes» | Annotation loaders were removed in 7.0; only attribute loaders remain (Annotation→Attribute). |