Пример запроса (первая клетка). System одинаковый во всех запросах прогона, user — свой вопрос для каждой клетки:
| Клетка | Тема | Утверждение | Ответ |
Результат | Обоснование |
T01-L1 3.9 c | Syntax and operators | Double-quoted and single-quoted strings are processed identically; the difference is only in speed. | «no» Пояснение: Double-quoted strings support variable interpolation and escape sequences (like \n, \t), while single-quoted strings treat $ as a literal character and only recognize \ and \' as escapes, so they are processed differently.
Raw{"answer": "no", "explanation": "Double-quoted strings support variable interpolation and escape sequences (like \\n, \\t), while single-quoted strings treat $ as a literal character and only recognize \\ and \\' as escapes, so they are processed differently."} | верно | В двойных кавычках работают интерполяция переменных и escape-последовательности, в одинарных — нет. |
T01-L2 1.17 c | Syntax and operators | The ?? operator follows isset semantics and raises no warnings for undefined variables. | «yes» Пояснение: PHP's null coalescing operator (??) evaluates without warnings or notices when a variable is undefined, following isset() semantics.
Raw{"answer": "yes", "explanation": "PHP's null coalescing operator (??) evaluates without warnings or notices when a variable is undefined, following isset() semantics."} | верно | ?? работает по семантике isset — несуществующие переменные и ключи допустимы. |
T01-L3 0.88 c | Syntax and operators | What will this print: echo 'a', 'b'; | «ab» Пояснение: The echo statement concatenates and outputs the strings 'a' and 'b' without any separator.
Raw{"answer": "ab", "explanation": "The echo statement concatenates and outputs the strings 'a' and 'b' without any separator."} | верно | echo принимает список аргументов: ab. |
T01-L4 2.54 c | Syntax and operators | print returns the value 1 and can be used inside an expression. | «yes» Пояснение: In PHP, print is a language construct that returns 1 and can therefore be used inside an expression.
Raw{"answer": "yes", "explanation": "In PHP, print is a language construct that returns 1 and can therefore be used inside an expression."} | верно | print — выражение со значением 1, в отличие от echo, который значения не возвращает. |
T01-L5 1.39 c | Syntax and operators | The ?: (elvis) operator returns its left operand when it is falsy. | «no» Пояснение: The Elvis operator (?:) returns the left operand when it is truthy, and the right operand when it is falsy.
Raw{"answer": "no", "explanation": "The Elvis operator (?:) returns the left operand when it is truthy, and the right operand when it is falsy."} | верно | Наоборот: $a ?: $b возвращает $a, если он истинный, иначе $b. |
T01-L6 26.39 c | Syntax and operators | In PHP 8, the concatenation operator (.) has lower precedence than addition and subtraction. | «yes» Пояснение: In PHP, the concatenation operator (.) has lower precedence than the + and - operators, so addition/subtraction bind more tightly.
Raw{"answer": "yes", "explanation": "In PHP, the concatenation operator (.) has lower precedence than the + and - operators, so addition/subtraction bind more tightly."} | верно | С PHP 8 (RFC concat precedence) '.' имеет приоритет ниже арифметики: 'сумма: ' . 2 + 3 → 'сумма: 5' (в PHP 7 было иначе). |
T01-L7 1.34 c | Syntax and operators | The expression 2 ** 3 ** 2 in PHP evaluates as (2 ** 3) ** 2, that is, 64. | «no» Пояснение: PHP's ** operator is right-associative, so 2 ** 3 ** 2 evaluates as 2 ** (3 ** 2), which is 512.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "PHP's ** operator is right-associative, so 2 ** 3 ** 2 evaluates as 2 ** (3 ** 2), which is 512." ⏎ } | верно | ** право-ассоциативен: 2 ** (3 ** 2) = 2 ** 9 = 512. |
T01-L8 9.09 c | Syntax and operators | What string will this print: echo 'sum: ' . 2 + 3; (PHP 8)? | «sum: 5» Пояснение: In PHP, the + operator has higher precedence than concatenation, so it evaluates 2 + 3 first.
Raw{"answer": "sum: 5", "explanation": "In PHP, the + operator has higher precedence than concatenation, so it evaluates 2 + 3 first."} | верно | Парная к verify-клетке про приоритет: 'сумма: 5'. |
T02-L1 6.51 c | Types and comparisons | With strict comparison (===), arrays are considered equal regardless of element order. | «no» Пояснение: Strict comparison requires arrays to have the same key/value pairs, in the same order, and the same types.
Raw{"answer": "no", "explanation": "Strict comparison requires arrays to have the same key/value pairs, in the same order, and the same types."} | верно | === для массивов требует совпадения и значений, и их порядка. |
T02-L2 1.35 c | Types and comparisons | The comparison 0 == false returns false because it is a strict comparison. | «no» Пояснение: 0 == false is a loose comparison and returns true in PHP.
Raw{"answer": "no", "explanation": "0 == false is a loose comparison and returns true in PHP."} | верно | Наоборот: == — нестрогое сравнение и возвращает true; строгое — это === (0 === false → false). |
T02-L3 3.17 c | Types and comparisons | In PHP 8, the expression "abc" == 0 returns true. | «no» Пояснение: In PHP 8, a non-numeric string is not compared as equal to a number, so "abc" == 0 is false.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "In PHP 8, a non-numeric string is not compared as equal to a number, so \"abc\" == 0 is false." ⏎ } | верно | С PHP 8 нечисловая строка сравнивается как строка: "abc" == "0" → false (в PHP 7 было true). |
T02-L4 6.48 c | Types and comparisons | Under loose comparison, null equals 0, the empty string, and false at the same time. | «yes» Пояснение: In PHP loose equality, null == 0, null == '' and null == false are all true.
Raw{"answer":"yes","explanation":"In PHP loose equality, null == 0, null == '' and null == false are all true."} | верно | null == 0, null == "" и null == false — все true. |
T02-L5 1.17 c | Types and comparisons | What does the expression (int) '42abc' return? | «42» Пояснение: PHP converts the string by taking the leading numeric part, so '42abc' becomes 42.
Raw{ ⏎ "answer": 42, ⏎ "explanation": "PHP converts the string by taking the leading numeric part, so '42abc' becomes 42." ⏎ } | верно | Ведущая числовая часть: 42, без ошибок и warning. |
T02-L6 1.12 c | Types and comparisons | What does the expression '5' + 5 return? | «10» Пояснение: In PHP, the string '5' is cast to the integer 5 when used with the + operator, resulting in 5 + 5 = 10.
Raw{"answer": 10, "explanation": "In PHP, the string '5' is cast to the integer 5 when used with the + operator, resulting in 5 + 5 = 10."} | верно | Числовая строка приводится: int 10. |
T02-L7 1.96 c | Types and comparisons | When cast to string, false becomes "0". | «no» Пояснение: In PHP, casting false to a string produces an empty string "", not "0".
Raw{"answer": "no", "explanation": "In PHP, casting false to a string produces an empty string \"\", not \"0\"."} | верно | false → "", true → "1". |
T02-L8 3.43 c | Types and comparisons | The comparison 0.1 + 0.2 === 0.3 returns false. | «yes» Пояснение: Because of floating-point precision errors, 0.1 + 0.2 is not exactly equal to 0.3 in PHP.
Raw{"answer": "yes", "explanation": "Because of floating-point precision errors, 0.1 + 0.2 is not exactly equal to 0.3 in PHP."} | верно | Двоичная погрешность float: 0.1 + 0.2 = 0.30000000000000004. |
T03-L1 0.82 c | Strings | strrev() correctly reverses a UTF-8 string. | «no» Пояснение: strrev() reverses bytes, not characters, so it does not correctly reverse multi-byte UTF-8 strings.
Raw{"answer": "no", "explanation": "strrev() reverses bytes, not characters, so it does not correctly reverse multi-byte UTF-8 strings."} | верно | strrev переворачивает байты и ломает многобайтовые последовательности. |
T03-L2 1.05 c | Strings | str_contains('Hello world', 'world') returns true. | «yes» Пояснение: The string 'Hello world' contains the substring 'world', so str_contains returns true.
Raw{"answer": "yes", "explanation": "The string 'Hello world' contains the substring 'world', so str_contains returns true."} | верно | str_contains с PHP 8.0 проверяет вхождение подстроки. |
T03-L3 1.27 c | Strings | str_pad() can pad a string on the right side only. | «no» Пояснение: str_pad() can pad a string on the left, right, or both sides using the pad_type parameter.
Raw{"answer":"no","explanation":"str_pad() can pad a string on the left, right, or both sides using the pad_type parameter."} | верно | STR_PAD_LEFT / STR_PAD_BOTH меняют сторону дополнения. |
T03-L4 1.42 c | Strings | By default trim() strips only spaces, leaving tabs and newlines intact. | «no» Пояснение: By default, PHP's trim() removes whitespace characters, including spaces, tabs, and newlines.
Raw{"answer": "no", "explanation": "By default, PHP's trim() removes whitespace characters, including spaces, tabs, and newlines."} | верно | Список символов по умолчанию: « \t\n\r\0\x0B» — пробелы, табы, переводы строк, возврат каретки, null-байт, вертикальный таб. Проверено php -r. |
T03-L5 1.4 c | Strings | How many BYTES does strlen('héllo') return for a UTF-8 string? | «6» Пояснение: In UTF-8, 'héllo' contains five characters, but 'é' is encoded as 2 bytes, so the total byte length is 6.
Raw{ ⏎ "answer": 6, ⏎ "explanation": "In UTF-8, 'héllo' contains five characters, but 'é' is encoded as 2 bytes, so the total byte length is 6." ⏎ } | верно | 6 букв по 2 байта: 12. |
T03-L6 1.64 c | Strings | What does substr('abcdef', -3) return? | «def» Пояснение: The -3 offset starts three characters from the end of the string, which is 'd'.
Raw{"answer": "def", "explanation": "The -3 offset starts three characters from the end of the string, which is 'd'."} | верно | Отрицательное смещение — с конца: def. |
T03-L7 1.12 c | Strings | ucfirst() modifies the string passed to it in place. | «no» Пояснение: ucfirst() returns a new string with the first character uppercased; it does not modify the original string in place.
Raw{"answer": "no", "explanation": "ucfirst() returns a new string with the first character uppercased; it does not modify the original string in place."} | верно | Строки неизменяемы; ucfirst возвращает новую строку. |
T03-L8 7.91 c | Strings | Variable interpolation works in heredoc but not in nowdoc. | «yes» Пояснение: Heredoc uses double-quote-like interpolation, while NOWDOC does not interpolate variables.
Raw{"answer":"yes","explanation":"Heredoc uses double-quote-like interpolation, while NOWDOC does not interpolate variables."} | верно | Nowdoc — «одинарные кавычки» в тройном синтаксисе: текст как есть. |
T04-L1 0.9 c | Arrays | The sort() function preserves the key-to-value association of the array. | «no» Пояснение: PHP's sort() reindexes numeric keys and does not preserve the original key-to-value associations.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "PHP's sort() reindexes numeric keys and does not preserve the original key-to-value associations." ⏎ } | верно | sort перенумеровывает ключи; связь сохраняет asort. |
T04-L2 1.32 c | Arrays | The string key '5' in an array is stored as the integer 5. | «yes» Пояснение: In PHP, a string key that is a valid integer, such as '5', is converted to the integer key 5.
Raw{"answer":"yes","explanation":"In PHP, a string key that is a valid integer, such as '5', is converted to the integer key 5."} | верно | Каноничные десятичные строковые ключи приводятся к int. |
T04-L3 0.88 c | Arrays | The in_array() function uses strict comparison (===) by default. | «no» Пояснение: The in_array() function uses loose comparison (==) by default unless the third parameter is set to true.
Raw{"answer":"no","explanation":"The in_array() function uses loose comparison (==) by default unless the third parameter is set to true."} | верно | По умолчанию сравнение нестрогое; строгое — третий аргумент true. |
T04-L4 1.06 c | Arrays | Without a callback, array_filter() removes all "empty" (falsy) elements from the array. | «yes» Пояснение: By default, array_filter() removes elements that are considered empty or falsy.
Raw{"answer": "yes", "explanation": "By default, array_filter() removes elements that are considered empty or falsy."} | верно | Убирает 0, "", null, false и пустые массивы. |
T04-L5 1.28 c | Arrays | By default, array_slice() preserves the original numeric keys of the array. | «no» Пояснение: By default, array_slice() does not preserve keys; you must pass the fourth parameter as true.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "By default, array_slice() does not preserve keys; you must pass the fourth parameter as true." ⏎ } | верно | По умолчанию ключи перенумеровываются; сохранение — preserve_keys = true. |
T04-L6 11.82 c | Arrays | What does array_slice([10, 20, 30, 40], 1, 2) return? | «[20, 30]» Пояснение: array_slice starts at index 1 and returns the next two elements.
Raw{ ⏎ "answer": "[20, 30]", ⏎ "explanation": "array_slice starts at index 1 and returns the next two elements." ⏎ } | верно | [20,30]; ключи перенумеровываются. |
T04-L7 1.08 c | Arrays | How many elements will count(['a' => 1] + ['a' => 9, 'b' => 2]) return? | «2» Пояснение: The + operator keeps the left array's 'a' => 1 and adds the right array's 'b' => 2.
Raw{"answer": 2, "explanation": "The + operator keeps the left array's 'a' => 1 and adds the right array's 'b' => 2."} | верно | Оператор + : по ключу 'a' побеждает левый; итого 2. |
T04-L8 3.99 c | Arrays | Since PHP 8.1, the spread operator [...$a, ...$b] supports arrays with string keys. | «yes» Пояснение: PHP 8.1 extended the array spread operator to allow arrays with string keys.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "PHP 8.1 extended the array spread operator to allow arrays with string keys." ⏎ } | верно | В 8.0 — только числовые ключи; 8.1 снял ограничение. |
T05-L1 85.85 c | Functions and closures | Named arguments cannot be combined with argument unpacking ...$args in a single call. | «yes» Пояснение: PHP does not allow mixing named arguments with the `...$args` argument unpacking syntax in the same function call.
Raw{"answer":"yes","explanation":"PHP does not allow mixing named arguments with the `...$args` argument unpacking syntax in the same function call."} | неверно верный: «no» | Можно: f(...$args, имя: значение). Нельзя только позиционный аргумент после распаковки. |
T05-L2 2.86 c | Functions and closures | An anonymous function without use sees variables from the outer scope. | «no» Пояснение: In PHP, closures (anonymous functions) do not automatically capture variables from the enclosing scope; they require the `use` keyword to explicitly reference outer variables.
Raw{"answer": "no", "explanation": "In PHP, closures (anonymous functions) do not automatically capture variables from the enclosing scope; they require the `use` keyword to explicitly reference outer variables."} | верно | Без use внешние переменные недоступны; авто-захват только у fn. |
T05-L3 2.34 c | Functions and closures | What will func_num_args() return inside function f($a) { return func_num_args(); } when called as f(1, 2, 3)? | «3» Пояснение: func_num_args() returns the number of arguments actually passed to the calling function, so f(1, 2, 3) returns 3.
Raw{ ⏎ "answer": 3, ⏎ "explanation": "func_num_args() returns the number of arguments actually passed to the calling function, so f(1, 2, 3) returns 3." ⏎ } | верно | Считает переданные аргументы: 3. |
T05-L4 2.1 c | Functions and closures | The body of an arrow function fn may consist of several expressions in curly braces. | «no» Пояснение: An arrow function's body must be a single expression, not multiple expressions in curly braces.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "An arrow function's body must be a single expression, not multiple expressions in curly braces." ⏎ } | верно | fn — всегда одно выражение; блок операторов делает обычная анонимная функция. |
T05-L5 9.64 c | Functions and closures | An arrow function fn captures outer variables by reference (lazily, at use time). | «no» Пояснение: PHP arrow functions capture outer variables by value, not by reference, and not lazily at call time.
Raw{"answer": "no", "explanation": "PHP arrow functions capture outer variables by value, not by reference, and not lazily at call time."} | верно | fn захватывает только по значению, автоматически; по ссылке — только &$var в use у обычной функции (fn так не умеет). |
T05-L6 1.96 c | Functions and closures | A closure declared as static function () {} does not capture $this. | «yes» Пояснение: A static closure has no $this binding, so it does not capture $this.
Raw{"answer":"yes","explanation":"A static closure has no $this binding, so it does not capture $this."} | верно | static-замыкание отвязано от объекта: $this внутри недоступен. |
T05-L7 1.35 c | Functions and closures | What will this print: $x = 5; $f = function () use ($x) { return $x; }; $x = 7; echo $f(); | «5» Пояснение: use captures variables by value by default, so the closure keeps the original value of $x.
Raw{"answer": 5, "explanation": "use captures variables by value by default, so the closure keeps the original value of $x."} | верно | use захватывает по значению в момент создания: 5. |
T05-L8 4.27 c | Functions and closures | In weak typing mode (without strict_types), passing the string "5" to an int parameter is allowed. | «yes» Пояснение: In PHP weak typing mode, the numeric string "5" is coerced to the integer 5 when passed to an int parameter.
Raw{"answer": "yes", "explanation": "In PHP weak typing mode, the numeric string \"5\" is coerced to the integer 5 when passed to an int parameter."} | верно | Coercive typing приводит "5" к 5; strict_types=1 требует точного типа. |
T06-L1 0.94 c | OOP: classes and inheritance | PHP supports constructor property promotion: public function __construct(private int $x) {}. | «yes» Пояснение: PHP 8.0+ supports constructor property promotion by declaring parameters directly with visibility modifiers like private in the constructor signature.
Raw{"answer": "yes", "explanation": "PHP 8.0+ supports constructor property promotion by declaring parameters directly with visibility modifiers like private in the constructor signature."} | верно | С PHP 8.0 параметр с модификатором создаёт свойство и присваивание. |
T06-L2 1.03 c | OOP: classes and inheritance | Which keyword prevents a method from being overridden in subclasses? | «final» Пояснение: In PHP, the final keyword prevents a method from being overridden in a subclass.
Raw{"answer": "final", "explanation": "In PHP, the final keyword prevents a method from being overridden in a subclass."} | верно | final. |
T06-L3 0.9 c | OOP: classes and inheritance | A method declared final cannot be overridden in a subclass. | «yes» Пояснение: In PHP, a final method cannot be overridden by a subclass.
Raw{"answer": "yes", "explanation": "In PHP, a final method cannot be overridden by a subclass."} | верно | final запрещает переопределение метода и наследование класса. |
T06-L4 0.95 c | OOP: classes and inheritance | Parent properties with private visibility are accessible in a subclass. | «no» Пояснение: Private properties are only accessible within the class where they are declared and cannot be accessed from a subclass.
Raw{"answer": "no", "explanation": "Private properties are only accessible within the class where they are declared and cannot be accessed from a subclass."} | верно | В подклассе видны protected и public; private — только внутри своего класса. |
T06-L5 3.15 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» Пояснение: The anonymous class name starts with 'class' before the NUL byte.
Raw{"answer":"class","explanation":"The anonymous class name starts with 'class' before the NUL byte."} | неверно верный: «class@anonymous» | get_class анонимного класса печатает class@anonymous\0<файл>:<строка>$n; короткая форма — часть до NUL-байта. Проверено php -r (hex). |
T06-L6 2.21 c | OOP: classes and inheritance | A private parent method is not part of the inheritance contract: a child may declare a method with the same name and any visibility. | «yes» Пояснение: Private methods are not inherited and do not constrain a child class, so the child can define a same-named method with any visibility.
Raw{"answer":"yes","explanation":"Private methods are not inherited and do not constrain a child class, so the child can define a same-named method with any visibility."} | верно | private-члены не наследуются — правила совместимости подписей не действуют. |
T06-L7 3.93 c | OOP: classes and inheritance | The magic method __get() is called only for non-existent properties. | «no» Пояснение: __get() is called for non-existent or inaccessible properties (e.g., private or protected), not only non-existent ones.
Raw{"answer": "no", "explanation": "__get() is called for non-existent or inaccessible properties (e.g., private or protected), not only non-existent ones."} | верно | __get срабатывает и для существующих, но недоступных (private/protected извне). |
T06-L8 4.89 c | OOP: classes and inheritance | What does reassigning a readonly property throw — Exception or Error? | «error» Пояснение: Reassigning a readonly property throws a TypeError, which is a subclass of Error in PHP.
Raw{ ⏎ "answer": "Error", ⏎ "explanation": "Reassigning a readonly property throws a TypeError, which is a subclass of Error in PHP." ⏎ } | верно | Error (readonly с 8.1); оговорка: в __clone() переинициализация допустима (8.3+). |
T07-L1 0.88 c | Interfaces, traits, enum | An interface can declare constants. | «yes» Пояснение: In PHP, an interface may declare public constants, but it cannot define method implementations or properties.
Raw{"answer": "yes", "explanation": "In PHP, an interface may declare public constants, but it cannot define method implementations or properties."} | верно | Константы интерфейса наследуются реализациями. |
T07-L2 0.76 c | Interfaces, traits, enum | Which operator checks whether an object is an instance of a class or interface? | «instanceof» Пояснение: The instanceof operator checks if an object is an instance of a given class or interface.
Raw{"answer": "instanceof", "explanation": "The instanceof operator checks if an object is an instance of a given class or interface."} | верно | instanceof. |
T07-L3 26.11 c | Interfaces, traits, enum | An interface can declare static methods. | «yes» Пояснение: Since PHP 8.3, interfaces can declare abstract static methods.
Raw{"answer": "yes", "explanation": "Since PHP 8.3, interfaces can declare abstract static methods."} | верно | Реализация обязана дать статический метод с той же сигнатурой. |
T07-L4 1.04 c | Interfaces, traits, enum | The instanceof operator only checks class inheritance: it ignores interfaces. | «no» Пояснение: The instanceof operator in PHP checks both class inheritance and interface implementation.
Raw{"answer": "no", "explanation": "The instanceof operator in PHP checks both class inheritance and interface implementation."} | верно | instanceof возвращает true и для интерфейсов объекта. |
T07-L5 2.72 c | Interfaces, traits, enum | An interface method may have a default implementation, like a trait method. | «no» Пояснение: In PHP, interface methods must be abstract and cannot have a method body or default implementation, unlike trait methods which can be concrete.
Raw{"answer": "no", "explanation": "In PHP, interface methods must be abstract and cannot have a method body or default implementation, unlike trait methods which can be concrete."} | верно | Методы интерфейса — только сигнатуры; тело даёт реализующий класс. |
T07-L6 1.94 c | Interfaces, traits, enum | An abstract method in an abstract class may have protected visibility. | «yes» Пояснение: In PHP, abstract methods can be declared as either public or protected, but not private.
Raw{"answer":"yes","explanation":"In PHP, abstract methods can be declared as either public or protected, but not private."} | верно | В абстрактном классе — любая видимость; в интерфейсе — только public. |
T07-L7 1.34 c | Interfaces, traits, enum | How many elements will Foo::cases() return for enum Foo { case A; case B; case C; }? | «3» Пояснение: PHP's Foo::cases() returns one array element for each enum case, and this enum has three cases.
Raw{"answer": 3, "explanation": "PHP's Foo::cases() returns one array element for each enum case, and this enum has three cases."} | верно | Статический метод cases(): 3. |
T07-L8 1.47 c | Interfaces, traits, enum | A trait can declare constants. | «yes» Пояснение: In PHP, traits can declare constants as well as methods and properties.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "In PHP, traits can declare constants as well as methods and properties." ⏎ } | верно | С PHP 8.2 трейты могут объявлять константы (RFC constants_in_traits); до 8.2 — нет. |
T08-L1 1.09 c | Exceptions and errors | The Throwable interface is a common ancestor of both Exception and Error. | «yes» Пояснение: In PHP, both Exception and Error implement the Throwable interface.
Raw{"answer": "yes", "explanation": "In PHP, both Exception and Error implement the Throwable interface."} | верно | Иерархия с PHP 7: Throwable → Exception и Throwable → Error. |
T08-L2 3.09 c | Exceptions and errors | A catch (Exception $e) block will also catch TypeError, because TypeError ultimately inherits from Exception. | «no» Пояснение: TypeError inherits from Error, not Exception, so it is not caught by catch (Exception $e).
Raw{ ⏎ "answer": "no", ⏎ "explanation": "TypeError inherits from Error, not Exception, so it is not caught by catch (Exception $e)." ⏎ } | верно | TypeError наследуется от Error; catch (Exception) его не ловит. |
T08-L3 1.09 c | Exceptions and errors | The @ operator suppresses exceptions too. | «no» Пояснение: The @ operator only suppresses errors and notices, not exceptions.
Raw{"answer":"no","explanation":"The @ operator only suppresses errors and notices, not exceptions."} | верно | @ глушит диагностику (warnings/notices), исключения не перехватывает. |
T08-L4 1.18 c | Exceptions and errors | What error class does intdiv(5, 0) throw? | «divisionbyzeroerror» Пояснение: intdiv() throws DivisionByZeroError when the divisor is zero.
Raw{"answer":"DivisionByZeroError","explanation":"intdiv() throws DivisionByZeroError when the divisor is zero."} | верно | DivisionByZeroError (иерархия Error, не Exception); php-грейдер объективен. |
T08-L5 1.67 c | Exceptions and errors | The finally block runs only if the exception was caught by a catch block. | «no» Пояснение: In PHP, a finally block executes regardless of whether an exception is thrown or caught.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "In PHP, a finally block executes regardless of whether an exception is thrown or caught." ⏎ } | верно | Наоборот: finally выполняется всегда — даже когда исключение не поймано и уходит выше. Проверено php -r. |
T08-L6 2.97 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 propagates outward and can override the try/catch flow.
Raw{ ⏎ "answer": "false", ⏎ "explanation": "An exception thrown in a finally block propagates outward and can override the try/catch flow." ⏎ } | верно | Исключение из finally перекрывает исходное и уходит вместо него. |
T08-L7 2.95 c | Exceptions and errors | What does the expression (bool) new Exception('x') return? | «yes» Пояснение: In PHP, objects evaluate to true when cast to boolean.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "In PHP, objects evaluate to true when cast to boolean." ⏎ } | верно | Любой объект при приведении к bool — true. Формы ответа: true или да. |
T08-L8 2.17 c | Exceptions and errors | Functions registered via register_shutdown_function() run when exit is called. | «yes» Пояснение: Shutdown functions registered with register_shutdown_function() are executed when the script terminates normally, including when exit() is called.
Raw{"answer":"yes","explanation":"Shutdown functions registered with register_shutdown_function() are executed when the script terminates normally, including when exit() is called."} | верно | exit завершает скрипт, но shutdown-функции отрабатывают. |
T09-L1 1.8 c | Namespaces and autoloading | The use App\Service\Mailer; statement itself loads the class file. | «no» Пояснение: The use statement only creates an alias and does not load the class file by itself.
Raw{"answer": "no", "explanation": "The use statement only creates an alias and does not load the class file by itself."} | верно | use — псевдоним на этапе компиляции; файл грузит автозагрузчик при первом обращении. |
T09-L2 2.63 c | Namespaces and autoloading | What follows use to import a function (not a class): the word function or const? | «function» Пояснение: In PHP, `use function` is used to import a function from another namespace.
Raw{"answer": "function", "explanation": "In PHP, `use function` is used to import a function from another namespace."} | верно | use function ...; (и use const для констант). |
T09-L3 5.83 c | Namespaces and autoloading | Into which file (path from src/) does the PSR-4 mapping "App\ → src/" place the class App\Controller\Api\UserController? | «controller/api/usercontroller.php» Пояснение: PSR-4 maps the remaining namespace parts to directory names and appends .php.
Raw{"answer": "Controller/Api/UserController.php", "explanation": "PSR-4 maps the remaining namespace parts to directory names and appends .php."} | верно | Остаток имени после префикса, \ → /. |
T09-L4 2.48 c | Namespaces and autoloading | Including vendor/autoload.php registers autoloaders via spl_autoload_register(). | «yes» Пояснение: Composer's vendor/autoload.php registers its autoloader(s) using spl_autoload_register().
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Composer's vendor/autoload.php registers its autoloader(s) using spl_autoload_register()." ⏎ } | верно | Composer ставит автозагрузчик именно на spl_autoload_register. |
T09-L5 1.91 c | Namespaces and autoloading | The magic constant __NAMESPACE__ contains the name of the current namespace. | «yes» Пояснение: In PHP, the __NAMESPACE__ magic constant returns the current namespace name (or null in global scope).
Raw{"answer":"yes","explanation":"In PHP, the __NAMESPACE__ magic constant returns the current namespace name (or null in global scope)."} | верно | В корневом пространстве — пустая строка. |
T09-L6 22.8 c | Namespaces and autoloading | An unqualified class name (without a leading \) in new is resolved from the global root. | «no» Пояснение: Unqualified class names in new are resolved in the current namespace first, then fall back to the global namespace.
Raw{"answer":"no","explanation":"Unqualified class names in new are resolved in the current namespace first, then fall back to the global namespace."} | верно | Резолвится относительно текущего namespace (с учётом импортов). |
T09-L7 1.18 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» Пояснение: Under PSR-4, the App\ namespace maps to src/, so App\Model\User resolves to src/Model/User.php.
Raw{"answer":"yes","explanation":"Under PSR-4, the App\\ namespace maps to src/, so App\\Model\\User resolves to src/Model/User.php."} | верно | Остаток имени после префикса переносится в путь как есть. |
T09-L8 101.89 c | Namespaces and autoloading | A use statement may be written inside a function body — the import then applies to that function only. | «yes» Пояснение: A PHP use import can be written inside a function body and is scoped to that function only.
Raw{"answer": "yes", "explanation": "A PHP use import can be written inside a function body and is scoped to that function only."} | неверно верный: «no» | use внутри тела функции — parse error; импорты файловые и компиляционные. |
T10-L1 4.4 c | References and scope | Arrays are copied on assignment rather than passed by reference. | «yes» Пояснение: In PHP, assigning an array to another variable creates a copy by value unless reference semantics are explicitly used.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "In PHP, assigning an array to another variable creates a copy by value unless reference semantics are explicitly used." ⏎ } | верно | Присваивание массива — копия (в движке — copy-on-write). |
T10-L2 1.08 c | References and scope | What will this print: $a = [1, 2]; $b = $a; $b[] = 3; echo count($a); | «2» Пояснение: Arrays in PHP are copied by value on assignment, so modifying $b does not change $a.
Raw{"answer": 2, "explanation": "Arrays in PHP are copied by value on assignment, so modifying $b does not change $a."} | верно | Присваивание — копия: в $a по-прежнему 2 элемента. |
T10-L3 1.17 c | References and scope | Inside a function, user-defined global variables are inaccessible without global, $GLOBALS, or passing them as parameters. | «yes» Пояснение: In PHP, function scope is separate, so global variables must be accessed with global, $GLOBALS, or passed in.
Raw{"answer": "yes", "explanation": "In PHP, function scope is separate, so global variables must be accessed with global, $GLOBALS, or passed in."} | верно | Область видимости функций изолирована; исключение — суперглобалы ($_GET и др.). |
T10-L4 1.7 c | References and scope | unset($GLOBALS['x']) inside a function removes the global variable only for that function. | «no» Пояснение: unset($GLOBALS['x']) removes the global variable $x from the global scope entirely, not just within that function.
Raw{"answer": "no", "explanation": "unset($GLOBALS['x']) removes the global variable $x from the global scope entirely, not just within that function."} | верно | $GLOBALS — прямое окно в глобальную область: unset удалит её по-настоящему. |
T10-L5 0.95 c | References and scope | What will this print: function inc(&$x) { $x++; } $n = 5; inc($n); echo $n; | «6» Пояснение: The variable $n is passed by reference and incremented to 6.
Raw{"answer": 6, "explanation": "The variable $n is passed by reference and incremented to 6."} | верно | Ссылка меняет оригинал: 6. |
T10-L6 4.84 c | References and scope | A foreach over an array (by value) works with the "live" array: changes to the array inside the loop are visible in the same pass. | «no» Пояснение: PHP's foreach by value iterates over a copy of the array, so changes made to the original array during the loop are not reflected in the current iteration pass.
Raw{"answer": "no", "explanation": "PHP's foreach by value iterates over a copy of the array, so changes made to the original array during the loop are not reflected in the current iteration pass."} | верно | По значению foreach итерирует копию-снимок. |
T10-L7 1.36 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 and are shared among all instances.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "Static properties belong to the class and are shared among all instances." ⏎ } | верно | Наоборот: статическое свойство общее для всех экземпляров класса. Проверено php -r. |
T10-L8 1.91 c | References and scope | An array can have a boolean key true, and it will be stored as bool. | «no» Пояснение: In PHP, boolean keys in arrays are cast to integers (true becomes 1, false becomes 0), so the key is stored as an int, not a bool.
Raw{"answer": "no", "explanation": "In PHP, boolean keys in arrays are cast to integers (true becomes 1, false becomes 0), so the key is stored as an int, not a bool."} | верно | Булев ключ приводится к int: true → 1, false → 0. |
T11-L1 3.18 c | Generators, iterators, SPL | Inside a generator, return with a value can be used, and it becomes available via $gen->getReturn(). | «yes» Пояснение: In PHP, a generator can end with `return value`, and the value can be retrieved with `Generator::getReturn()` after the generator is exhausted.
Raw{"answer": "yes", "explanation": "In PHP, a generator can end with `return value`, and the value can be retrieved with `Generator::getReturn()` after the generator is exhausted."} | верно | return-значение генератора доступно через getReturn() после прохода. |
T11-L2 12.47 c | Generators, iterators, SPL | A fully consumed generator can be rewound with rewind() and traversed again. | «yes» Пояснение: In PHP, a fully consumed generator can be rewound with rewind() and iterated again.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "In PHP, a fully consumed generator can be rewound with rewind() and iterated again." ⏎ } | неверно верный: «no» | Генератор одноразовый: rewind после начала итерации бросает Exception. |
T11-L3 1.49 c | Generators, iterators, SPL | The yield from construct delegates traversal to another generator or iterable. | «yes» Пояснение: The yield from construct delegates yielding to another generator or iterable.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "The yield from construct delegates yielding to another generator or iterable." ⏎ } | верно | yield from проксирует значения, ключи и return-значение внутреннего генератора. |
T11-L4 1.58 c | Generators, iterators, SPL | What does get_class(g()) return for function g() { yield 1; }? | «generator» Пояснение: g() returns a Generator object because it uses yield, and get_class() returns the class name of that object.
Raw{"answer": "Generator", "explanation": "g() returns a Generator object because it uses yield, and get_class() returns the class name of that object."} | верно | Функция с yield возвращает Generator. |
T11-L5 1.26 c | Generators, iterators, SPL | How many elements will count(iterator_to_array((function () { yield from [1, 2, 3]; })())) return? | «3» Пояснение: iterator_to_array converts the generator yielding 1, 2, and 3 into an array with three elements.
Raw{"answer": 3, "explanation": "iterator_to_array converts the generator yielding 1, 2, and 3 into an array with three elements."} | верно | yield from делегирует все 3 элемента. |
T11-L6 1.12 c | Generators, iterators, SPL | The SplStack class implements a FIFO queue. | «no» Пояснение: SplStack implements a LIFO (Last-In, First-Out) stack, not a FIFO queue; a FIFO queue would be implemented by SplQueue.
Raw{"answer": "no", "explanation": "SplStack implements a LIFO (Last-In, First-Out) stack, not a FIFO queue; a FIFO queue would be implemented by SplQueue."} | верно | SplStack — стек LIFO; очередь FIFO — SplQueue. |
T11-L7 0.94 c | Generators, iterators, SPL | ArrayIterator allows wrapping an array and traversing it via the Iterator interface. | «yes» Пояснение: ArrayIterator is a PHP Iterator implementation that wraps an array and allows traversing its elements.
Raw{"answer": "yes", "explanation": "ArrayIterator is a PHP Iterator implementation that wraps an array and allows traversing its elements."} | верно | Объектная обёртка над массивом. |
T11-L8 1.1 c | Generators, iterators, SPL | An ArrayObject instance cannot be traversed with foreach. | «no» Пояснение: ArrayObject implements the Iterator interface, so it can be traversed with foreach.
Raw{"answer": "no", "explanation": "ArrayObject implements the Iterator interface, so it can be traversed with foreach."} | верно | ArrayObject реализует IteratorAggregate — foreach по нему работает. |
T12-L1 1.41 c | Configuration and security | password_hash() generates a salt automatically — passing one separately is not needed. | «yes» Пояснение: password_hash() automatically generates and embeds the salt, so a separate salt parameter is not used or needed.
Raw{"answer": "yes", "explanation": "password_hash() automatically generates and embeds the salt, so a separate salt parameter is not used or needed."} | верно | Соль встраивается в строку результата; параметр salt устарел. |
T12-L2 1.66 c | Configuration and security | In PHP 8, PASSWORD_DEFAULT is md5 with an automatically added salt. | «no» Пояснение: PASSWORD_DEFAULT is the best available algorithm, not md5 with an automatically added salt.
Raw{"answer": "no", "explanation": "PASSWORD_DEFAULT is the best available algorithm, not md5 with an automatically added salt."} | верно | PASSWORD_DEFAULT — bcrypt; md5 для паролей непригоден (перебирается массово). |
T12-L3 2.62 c | Configuration and security | What does password_verify('secret', password_hash('secret', PASSWORD_DEFAULT)) return? | «yes» Пояснение: It returns true because the password matches the generated hash.
Raw{"answer":"yes","explanation":"It returns true because the password matches the generated hash."} | верно | Соль и хеш в одной строке: true (форма ответа: true или да). |
T12-L4 0.61 c | Configuration and security | strip_tags() protects against SQL injection. | «no» Пояснение: strip_tags() removes HTML tags, not SQL injection.
Raw{"answer": "no", "explanation": "strip_tags() removes HTML tags, not SQL injection."} | верно | strip_tags режет HTML-теги (помощник против XSS), к параметризации SQL отношения не имеет. |
T12-L5 0.55 c | Configuration and security | session_regenerate_id() is used to protect against session fixation upon user login. | «yes» Пояснение: session_regenerate_id() changes the session ID after authentication, which helps prevent session fixation attacks.
Raw{"answer":"yes","explanation":"session_regenerate_id() changes the session ID after authentication, which helps prevent session fixation attacks."} | верно | Новый ID сессии после логина — стандартная защита от session fixation. |
T12-L6 1.85 c | Configuration and security | Which built-in function returns the SAPI name (e.g., cli)? | «php_sapi_name» Пояснение: php_sapi_name() returns the current PHP SAPI name, such as cli.
Raw{ ⏎ "answer": "php_sapi_name", ⏎ "explanation": "php_sapi_name() returns the current PHP SAPI name, such as cli." ⏎ } | верно | php_sapi_name(). |
T12-L7 0.9 c | Configuration and security | session_destroy() deletes session data on the server but not the cookie in the user's browser. | «yes» Пояснение: session_destroy() removes server-side session data, but the session cookie must be deleted separately in the browser.
Raw{"answer": "yes", "explanation": "session_destroy() removes server-side session data, but the session cookie must be deleted separately in the browser."} | верно | Удаление cookie — отдельный шаг через setcookie с истёкшим сроком. |
T12-L8 1.06 c | Configuration and security | Without calling session_start(), the $_SESSION array is automatically populated with session data. | «no» Пояснение: The $_SESSION array is not automatically populated with session data until session_start() has been called.
Raw{"answer": "no", "explanation": "The $_SESSION array is not automatically populated with session data until session_start() has been called."} | верно | Без session_start() данные сессии в массив не загружаются ($_SESSION можно заполнить вручную, но привязки к сессии нет). |
VC-L1 7.39 c | PHP 8.4–8.5 | In which PHP version was the array_find() function introduced? | «8.1» Пояснение: The array_find() function was introduced in PHP 8.1.
Raw{ ⏎ "answer": "8.1", ⏎ "explanation": "The array_find() function was introduced in PHP 8.1." ⏎ } | неверно верный: «8.4» | PHP 8.4 (RFC array_find). |
VC-L2 1.69 c | PHP 8.4–8.5 | Property hooks (get/set right in the property declaration) landed in PHP 8.4. | «yes» Пояснение: Property hooks (inline get/set in property declarations) were introduced in PHP 8.4.0.
Raw{"answer": "yes", "explanation": "Property hooks (inline get/set in property declarations) were introduced in PHP 8.4.0."} | верно | Property hooks — PHP 8.4 (ноябрь 2024). |
VC-L3 11.91 c | PHP 8.4–8.5 | Asymmetric visibility (public private(set) string $name) appeared in PHP 8.4. | «yes» Пояснение: Asymmetric visibility was added in PHP 8.4.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Asymmetric visibility was added in PHP 8.4." ⏎ } | верно | Asymmetric visibility v2 — PHP 8.4. |
VC-L4 5.21 c | PHP 8.4–8.5 | In which PHP version was the #[\NoDiscard] attribute introduced? Answer with the version number. | «no» Пояснение: The #[\NoDiscard] attribute does not exist in any PHP version; it is not a recognized PHP attribute.
Raw{"answer": "no", "explanation": "The #[\\NoDiscard] attribute does not exist in any PHP version; it is not a recognized PHP attribute."} | неверно верный: «8.5» | #[\NoDiscard] — PHP 8.5 (marking return values as important). |
VC-L5 108.69 c | PHP 8.4–8.5 | In which PHP version did the pipe operator |> first appear? Answer with the version number. | «8.5» Пояснение: The pipe operator |> was first introduced in PHP 8.5.
Raw{"answer": 8.5, "explanation": "The pipe operator |> was first introduced in PHP 8.5."} | верно | Pipe operator — PHP 8.5 (2025). |
VC-L6 1.45 c | PHP 8.4–8.5 | In which PHP version did clone-with — the syntax clone($obj, ['x' => 1]) — appear? Answer with the version number. | «8.1» Пояснение: The clone-with syntax (clone($obj, ['x' => 1])) was introduced in PHP 8.1, allowing arguments to be passed to the __clone method.
Raw{"answer": "8.1", "explanation": "The clone-with syntax (clone($obj, ['x' => 1])) was introduced in PHP 8.1, allowing arguments to be passed to the __clone method."} | неверно верный: «8.5» | Clone with v2 — PHP 8.5. |
VC-L7 95.51 c | PHP 8.4–8.5 | In which PHP version were the array_first() and array_last() functions introduced? | «7.3» Пояснение: array_first() and array_last() were added in PHP 7.3.
Raw{"answer":"7.3","explanation":"array_first() and array_last() were added in PHP 7.3."} | неверно верный: «8.5» | PHP 8.5. |
VC-L8 114.1 c | PHP 8.4–8.5 | For which PHP version was RFC Partial Function Application v2 adopted (as of 2026-11-07)? Answer with the version number. | «8.5» Пояснение: The Partial Function Application v2 RFC was accepted for PHP 8.5.
Raw{"answer": "8.5", "explanation": "The Partial Function Application v2 RFC was accepted for PHP 8.5."} | неверно верный: «8.6» | PFA v2 принят 05.12.2025 (33-0-0), реализован в PHP 8.6. |
VF-L1 1.27 c | PHP: 8.6+ and the future | For which PHP version was the RFC clamp_v2 (the clamp() function) implemented, as of 2026-11-07? Answer with the version number. | «8.1» Пояснение: The clamp() function was introduced via the clamp_v2 RFC in PHP 8.1.
Raw{"answer": "8.1", "explanation": "The clamp() function was introduced via the clamp_v2 RFC in PHP 8.1."} | неверно верный: «8.6» | По данным владельца (wiki.php.net/rfc): clamp_v2 — 8.6; clamp() в 8.5.11 отсутствует (косвенное подтверждение). Дата-якорь делает клетку монотонной. |
VF-L2 175.41 c | PHP: 8.6+ and the future | RFC Context Managers v2 has already been adopted in PHP (as of 2026-11-07). | «yes» Пояснение: Context Managers v2 had already been accepted into the PHP RFC process by that date.
Raw{"answer": "yes", "explanation": "Context Managers v2 had already been accepted into the PHP RFC process by that date."} | неверно верный: «no» | На 06.11.2026 — в обсуждении (создан 2026-10-23); не принят. |
VF-L3 88.68 c | PHP: 8.6+ and the future | RFC Bound-Erased Generic Types (generics) was declined in 2026. | «yes» Пояснение: The RFC is recorded as having been declined in 2026.
Raw{"answer": "yes", "explanation": "The RFC is recorded as having been declined in 2026."} | верно | Голосование завершилось 2026-06-28: отклонён (wiki.php.net/rfc). |
VF-L4 125.64 c | PHP: 8.6+ and the future | As of 2026-11-07, the RFC enabling multithreading (ZTS) by default has already been accepted in PHP. | «yes» Пояснение: The ZTS-by-default RFC was accepted as part of the PHP 9.0 roadmap.
Raw{"answer":"yes","explanation":"The ZTS-by-default RFC was accepted as part of the PHP 9.0 roadmap."} | неверно верный: «no» | Такого принятого RFC нет на дату якоря; якорь делает клетку монотонной — при принятии RFC позже клетка не перевернётся. |
VF-L5 1.4 c | PHP: 8.6+ and the future | As of PHP 8.5, generics (parameterized types) are still absent. | «yes» Пояснение: PHP 8.5 does not support generics or parameterized types in its type system.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "PHP 8.5 does not support generics or parameterized types in its type system." ⏎ } | верно | Generics в PHP отсутствуют; отрицательный контроль (не путать с C#/Java). |
VF-L6 23.18 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 2026-11-07, PHP 8.5 had not yet reached GA, so the latest stable version would have been PHP 8.4.
Raw{"answer": "no", "explanation": "As of 2026-11-07, PHP 8.5 had not yet reached GA, so the latest stable version would have been PHP 8.4."} | неверно верный: «yes» | 8.5 — релиз осени 2025; 8.6 GA 19.11.2026 (wiki.php.net/todo/php86). Дата снимка — 06.11.2026. |
VF-L7 1.12 c | PHP: 8.6+ and the future | The PHP 6 branch never shipped: after PHP 5.6 came PHP 7.0 directly. | «yes» Пояснение: PHP skipped version 6 entirely, going directly from 5.6 to 7.0.
Raw{"answer": "yes", "explanation": "PHP skipped version 6 entirely, going directly from 5.6 to 7.0."} | верно | Исторический факт: ветка 6 не была релизнута. |
VF-L8 13.59 c | PHP: 8.6+ and the future | The RFC adding the #[\Deprecated] attribute to the core was adopted. | «yes» Пояснение: The RFC to add the #[\Deprecated] attribute to PHP core was adopted.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "The RFC to add the #[\\Deprecated] attribute to PHP core was adopted." ⏎ } | верно | #[\Deprecated] — принят, реализован в PHP 8.4. |
T25-L1 1.48 c | Clean architecture | The dependency rule of clean and onion architecture: inner layers know nothing about outer ones — dependencies point toward the center. | «yes» Пояснение: Clean and onion architecture require dependencies to point inward, so inner layers do not depend on outer layers.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Clean and onion architecture require dependencies to point inward, so inner layers do not depend on outer layers." ⏎ } | верно | Чистая (Robert C. Martin), луковичная (Jeffrey Palermo) и гексагональная (ports & adapters) — варианты одной идеи: зависимости направлены внутрь, к домену. Слоями в проекте следит deptrac. |
T25-L2 2.13 c | Clean architecture | Domain entities import neither Doctrine nor Symfony — only the language and, possibly, the standard library. | «yes» Пояснение: Domain entities should remain pure PHP objects and must not depend on framework or ORM packages.
Raw{"answer":"yes","explanation":"Domain entities should remain pure PHP objects and must not depend on framework or ORM packages."} | верно | Изоляция домена от инфраструктуры; deptrac в проекте как раз следит за слоями. |
T25-L3 1.26 c | Clean architecture | Controllers and Twig templates belong to the business-logic layer because they are the ones calling use cases. | «no» Пояснение: Controllers and Twig templates are part of the presentation layer, not the business-logic layer.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "Controllers and Twig templates are part of the presentation layer, not the business-logic layer." ⏎ } | верно | Наоборот: это интерфейсные адаптеры (внешний слой); они зависят от use cases, а не наоборот. |
T25-L4 1.31 c | Clean architecture | What sits at the very center of the onion architecture? | «domain» Пояснение: In Onion Architecture, the innermost core represents the Domain, which contains the fundamental business rules and entities that are independent of any framework or outer layer.
Raw{"answer": "Domain", "explanation": "In Onion Architecture, the innermost core represents the Domain, which contains the fundamental business rules and entities that are independent of any framework or outer layer."} | неверно верный: «domain model» | Центральное кольцо — Domain Model: сущности и бизнес-правила без зависимостей; далее Domain Services → Application Services → Infrastructure/UI/Tests (Palermo). |
T25-L5 2.27 c | Clean architecture | Layer boundary violations can be caught automatically: a layer-dependency analyzer (e.g. deptrac) fails on a forbidden call. | «yes» Пояснение: A static layer-dependency analyzer can detect and fail on forbidden inter-layer calls.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "A static layer-dependency analyzer can detect and fail on forbidden inter-layer calls." ⏎ } | верно | depfile.yaml в проекте TasK: CI проверяет правила слоёв на каждом пайплайне. |
T25-L6 2.87 c | Clean architecture | A use case (interactor) may accept an HTTP request or an EntityManager as arguments — it is simpler that way. | «no» Пояснение: Use cases should depend on abstractions or domain inputs, not concrete HTTP request or EntityManager objects, to remain loosely coupled and testable.
Raw{"answer":"no","explanation":"Use cases should depend on abstractions or domain inputs, not concrete HTTP request or EntityManager objects, to remain loosely coupled and testable."} | верно | Use case принимает DTO и порты; привязка к HTTP/ORM протекает инфраструктуру во внутренние слои. |
T25-L7 1.44 c | Clean architecture | What is the component called that provides a collection of aggregates/entities while hiding the storage mechanism behind an interface? | «repository» Пояснение: In Domain-Driven Design, a Repository is the component that provides a collection of aggregates/objects while hiding the storage mechanism behind an interface.
Raw{"answer":"Repository","explanation":"In Domain-Driven Design, a Repository is the component that provides a collection of aggregates/objects while hiding the storage mechanism behind an interface."} | верно | Repository pattern (DDD/Evans); в проекте — Doctrine-репозитории за портами. |
T25-L8 2.16 c | Clean architecture | In clean architecture, swapping PostgreSQL for another database touches only the outer layer — the domain and use cases stay unchanged. | «yes» Пояснение: In clean architecture, dependencies point inward, so database-specific implementations live in the outer adapter/infrastructure layer, keeping the domain and use-case layers independent of the storage technology.
Raw{"answer": "yes", "explanation": "In clean architecture, dependencies point inward, so database-specific implementations live in the outer adapter/infrastructure layer, keeping the domain and use-case layers independent of the storage technology."} | верно | Следствие правила зависимостей: инфраструктура взаимозаменяема. |
T26-L1 1.03 c | DDD | In DDD, an aggregate is just another name for a database table. | «no» Пояснение: In DDD, an aggregate is a domain object cluster, not necessarily a database table.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "In DDD, an aggregate is a domain object cluster, not necessarily a database table." ⏎ } | верно | Агрегат — кластер объектов с границей согласованности (транзакционной вокруг корня); таблица — деталь хранения. |
T26-L2 0.81 c | DDD | A Value Object is immutable and compared by the values of its fields, not by identity. | «yes» Пояснение: Value Objects are typically immutable and use value-based equality rather than object identity.
Raw{"answer":"yes","explanation":"Value Objects are typically immutable and use value-based equality rather than object identity."} | верно | Классика Evans: Money, Email; равенство структурное. |
T26-L3 0.81 c | DDD | What is the single external entry point of an aggregate, through which all changes must go, called? | «aggregate root» Пояснение: In Domain-Driven Design, the aggregate root is the single external entry point for making changes to an aggregate.
Raw{"answer":"Aggregate root","explanation":"In Domain-Driven Design, the aggregate root is the single external entry point for making changes to an aggregate."} | верно | Aggregate Root: внешние объекты ссылаются только на корень; он защищает инварианты агрегата. |
T26-L4 0.55 c | DDD | In DDD, a repository is declared for an aggregate (its root), not for every entity. | «yes» Пояснение: In DDD, repositories are typically defined for aggregate roots to maintain aggregate integrity.
Raw{"answer": "yes", "explanation": "In DDD, repositories are typically defined for aggregate roots to maintain aggregate integrity."} | верно | Репозиторий корня хранит границу согласованности агрегата; вложенные сущности доступны только через корень. |
T26-L5 1.25 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 to describe the domain.
Raw{"answer": "yes", "explanation": "Ubiquitous language is the shared language used by developers and domain experts to describe the domain."} | верно | Evans: язык из требований переходит в имена классов и методов. |
T26-L6 64.5 c | DDD | What is the boundary called within which a model and its language are consistent, while outside the same words mean other models? | «domain of discourse» Пояснение: It is the bounded set over which the model interprets the language.
Raw{"answer": "domain of discourse", "explanation": "It is the bounded set over which the model interprets the language."} | неверно верный: «bounded context» | Bounded Context; «Заказ» в биллинге и в доставке — разные модели. |
T26-L7 0.99 c | DDD | An anemic model (objects with only getters/setters, logic in services) is the recommended DDD style. | «no» Пояснение: DDD generally favors rich domain models that encapsulate behavior, rather than anemic models with logic in services.
Raw{"answer":"no","explanation":"DDD generally favors rich domain models that encapsulate behavior, rather than anemic models with logic in services."} | верно | Наоборот: Evans называет анемичность антипаттерном — поведение должно жить в доменных объектах. |
T26-L8 2.14 c | DDD | Bounded context means each context has its own model: the same concept in different contexts is a different class. | «yes» Пояснение: In DDD, each bounded context has its own model, so the same concept can be represented as different classes in different contexts.
Raw{"answer":"yes","explanation":"In DDD, each bounded context has its own model, so the same concept can be represented as different classes in different contexts."} | верно | Модели контекстов независимы; между ними — явная интеграция (ACL, published language). |
T13-L1 1.49 c | Symfony | Services in the Symfony DI container are created lazily by default — on first use. | «yes» Пояснение: Symfony’s dependency injection container loads services lazily by default, creating them on first use.
Raw{"answer":"yes","explanation":"Symfony’s dependency injection container loads services lazily by default, creating them on first use."} | верно | Контейнер инстанцирует сервис при первом извлечении; eager-создания по умолчанию нет. |
T13-L2 2.54 c | Symfony | Which Symfony console command lists all registered routes? | «router:info» Пояснение: The Symfony console command `router:info` (invoked as `php bin/console router:info` or `symfony router:info`) lists all registered routes along with their matching patterns and requirements.
Raw{"answer": "router:info", "explanation": "The Symfony console command `router:info` (invoked as `php bin/console router:info` or `symfony router:info`) lists all registered routes along with their matching patterns and requirements."} | неверно верный: «debug:router» | bin/console debug:router (FrameworkBundle); в Symfony 3 команда называлась router:debug. |
T13-L3 2.03 c | Symfony | Symfony autowiring requires manually declaring every service in services.yaml. | «no» Пояснение: Symfony can auto-discover and configure many services, so you do not have to manually declare every service.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "Symfony can auto-discover and configure many services, so you do not have to manually declare every service." ⏎ } | верно | Autowire+autoconfigure регистрируют и связывают сервисы автоматически; ручное перечисление — исключение. |
T13-L4 12.02 c | Symfony | Twig templates are compiled into PHP classes and cached between requests. | «yes» Пояснение: Twig compiles templates into PHP code, typically class-based, and caches the compiled output for reuse between requests.
Raw{"answer": "yes", "explanation": "Twig compiles templates into PHP code, typically class-based, and caches the compiled output for reuse between requests."} | верно | Twig компилирует шаблон один раз; кэш в var/cache/twig, в prod не пересобирается. |
T13-L5 1.52 c | Symfony | In the Symfony dev environment the DI container is rebuilt only after tracked files change, not on every request. | «yes» Пояснение: Symfony's development container is cached and rebuilt only when its tracked files or configuration change.
Raw{"answer":"yes","explanation":"Symfony's development container is cached and rebuilt only when its tracked files or configuration change."} | верно | Kernel проверяет freshness ресурсов (конфиги, классы); иначе переиспользуется кэш контейнера. |
T13-L6 1.46 c | Symfony | Which environment variable selects the active Symfony environment (dev/prod)? | «app_env» Пояснение: Symfony selects the active environment (such as dev or prod) using the APP_ENV environment variable.
Raw{"answer": "APP_ENV", "explanation": "Symfony selects the active environment (such as dev or prod) using the APP_ENV environment variable."} | верно | APP_ENV в .env; APP_DEBUG — отдельный флаг отладки. |
T13-L7 31.22 c | Symfony | A controller method can be private — Symfony routing works with any method of the class. | «no» Пояснение: Symfony route actions must be public methods, so private controller actions are not supported.
Raw{"answer":"no","explanation":"Symfony route actions must be public methods, so private controller actions are not supported."} | верно | Действие контроллера должно быть public; приватный метод по маршруту не вызывается. |
T13-L8 1.72 c | Symfony | Event subscribers always receive events before listeners, because the interface gives them priority. | «no» Пояснение: There is no built-in rule that subscribers always run before listeners; execution order depends on listener priority and registration.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "There is no built-in rule that subscribers always run before listeners; execution order depends on listener priority and registration." ⏎ } | верно | Порядок определяет priority, а не тип подписки; приоритеты задаются в getSubscribedEvents() так же, как у слушателей. |
T22-L1 1.97 c | Symfony: Security and forms | In modern Symfony (6.0+) authentication is built on authenticator classes (AuthenticatorInterface); the old guard system has been removed. | «yes» Пояснение: Symfony 6.0+ uses AuthenticatorInterface-based security components, and the old Guard system was removed.
Raw{"answer": "yes", "explanation": "Symfony 6.0+ uses AuthenticatorInterface-based security components, and the old Guard system was removed."} | верно | Guard объявлен устаревшим в 5.3 и удалён в 6.0; в проекте symfony/security-bundle 8.1. |
T22-L2 1.65 c | Symfony: Security and forms | Which Symfony attribute checks a role/permission right on a controller method (403 without it)? | «isgrantedattribute» Пояснение: Symfony's IsGrantedAttribute checks required roles or permissions and returns a 403 error if access is denied.
Raw{ ⏎ "answer": "IsGrantedAttribute", ⏎ "explanation": "Symfony's IsGrantedAttribute checks required roles or permissions and returns a 403 error if access is denied." ⏎ } | неверно верный: «isgranted» | #[IsGranted('ROLE_ADMIN')]; атрибут из symfony/security-http. |
T22-L3 2.88 c | Symfony: Security and forms | Voters are Symfony's mechanism for checking access to a specific object: isGranted('EDIT', $post). | «yes» Пояснение: In Symfony, Voter classes are used to grant or deny access to specific objects or attributes, such as with isGranted('EDIT', $post).
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "In Symfony, Voter classes are used to grant or deny access to specific objects or attributes, such as with isGranted('EDIT', $post)." ⏎ } | верно | VoterInterface->vote(); docs Symfony — Voters. |
T22-L4 207.37 c | Symfony: Security and forms | In modern Symfony (7+) validation constraints are declared as PHP attributes (#[Assert\NotBlank]); doctrine annotations are no longer supported. | «yes» Пояснение: Symfony 7 uses PHP attributes for validation/ORM mapping and the old Doctrine annotation syntax is no longer supported.
Raw{"answer": "yes", "explanation": "Symfony 7 uses PHP attributes for validation/ORM mapping and the old Doctrine annotation syntax is no longer supported."} | верно | Докблок-аннотации удалены в Symfony 7.0; стандарт — атрибуты. В проекте symfony/validator 8.1. |
T22-L5 7.51 c | Symfony: Security and forms | CSRF protection of Symfony forms is enabled by default: the form validates the token on submission. | «yes» Пояснение: Symfony forms include and validate a CSRF token by default on submission.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Symfony forms include and validate a CSRF token by default on submission." ⏎ } | верно | FormType добавляет скрытое поле _token и проверяет его при валидации; отключение — осознанное исключение (csrf: false). |
T22-L6 0.9 c | Symfony: Security and forms | Form validation in Symfony runs server-side even if the client-side (HTML5) checks passed. | «yes» Пояснение: Symfony always performs form validation on the server side when the form is submitted, regardless of client-side validation.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Symfony always performs form validation on the server side when the form is submitted, regardless of client-side validation." ⏎ } | верно | Клиентская валидация — только удобство; серверная обязательна и идёт по метаданным объекта формы. |
T22-L7 0.86 c | Symfony: Security and forms | Which Symfony maker command generates a form class (FormType)? | «php bin/console maker:form» Пояснение: The Symfony maker command for generating a form class is `maker:form`.
Raw{ ⏎ "answer": "php bin/console maker:form", ⏎ "explanation": "The Symfony maker command for generating a form class is `maker:form`." ⏎ } | неверно верный: «make:form» | bin/console make:form (symfony/maker-bundle — в проекте). |
T22-L8 1.05 c | Symfony: Security and forms | Symfony stores the user's password in the session in plain text. | «no» Пояснение: Symfony does not store plain-text passwords in the session; it uses hashed credentials and authentication tokens.
Raw{"answer":"no","explanation":"Symfony does not store plain-text passwords in the session; it uses hashed credentials and authentication tokens."} | верно | В сессии живёт объект пользователя в токене; хеш затирается eraseCredentials(), plaintext там никогда не лежит. |
T23-L1 1.53 c | Symfony: configuration and services | Symfony bundle configuration lives in config/packages — one file per bundle or topic. | «yes» Пояснение: In modern Symfony (4+), bundle configurations are organized as one YAML file per bundle in the config/packages/ directory, e.g., config/packages/mailer.yml or config/packages/monolog.yml.
Raw{"answer": "yes", "explanation": "In modern Symfony (4+), bundle configurations are organized as one YAML file per bundle in the config/packages/ directory, e.g., config/packages/mailer.yml or config/packages/monolog.yml."} | верно | Стандартная структура (config/packages/*.yaml); перегрузка — config/packages/<env>. |
T23-L2 1.95 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» Пояснение: A committed .env with safe defaults and a local, ignored .env.local for secrets is a common practice.
Raw{"answer": "yes", "explanation": "A committed .env with safe defaults and a local, ignored .env.local for secrets is a common practice."} | верно | symfony/dotenv: .env — общий безопасный набор значений; локальные секреты — .env.local (gitignored) или secrets-хранилище. |
T23-L3 0.93 c | Symfony: configuration and services | Which Symfony command lists the container's registered services and their aliases? | «debug:container» Пояснение: The `bin/console debug:container` command lists all registered services and their aliases in the Symfony DI container.
Raw{"answer":"debug:container","explanation":"The `bin/console debug:container` command lists all registered services and their aliases in the Symfony DI container."} | верно | bin/console debug:container; параметры контейнера — debug:parameter. |
T23-L4 4.23 c | Symfony: configuration and services | The Symfony container allows changing parameters at runtime: $container->setParameter() works from a controller. | «yes» Пояснение: Symfony’s container interface provides setParameter(), so injected or obtained containers can change parameters at runtime.
Raw{"answer": "yes", "explanation": "Symfony’s container interface provides setParameter(), so injected or obtained containers can change parameters at runtime."} | неверно верный: «no» | Контейнер компилируется и замораживается; runtime-значения — только через переменные окружения. |
T23-L5 2.76 c | Symfony: configuration and services | By default, Symfony services are public (public: true) — you can fetch them directly from the container. | «no» Пояснение: Since Symfony 3.4 (and by default in Symfony 4+), services are private (public: false) and must be explicitly marked as public to be fetchable directly from the container.
Raw{"answer": "no", "explanation": "Since Symfony 3.4 (and by default in Symfony 4+), services are private (public: false) and must be explicitly marked as public to be fetchable directly from the container."} | верно | С Symfony 4.0 сервисы по умолчанию private: инжектятся через autowiring; $container->get() — только для публичных. |
T23-L6 1.55 c | Symfony: configuration and services | Without a config file in config/packages a bundle will not work — configuration is mandatory for every bundle. | «no» Пояснение: A bundle does not always need a configuration file in config/packages; many can use default settings without explicit configuration.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "A bundle does not always need a configuration file in config/packages; many can use default settings without explicit configuration." ⏎ } | верно | У бандлов есть встроенные умолчания (Extension); конфиг нужен только для отклонений от них. |
T23-L7 2.72 c | Symfony: configuration and services | Environment variable values are injected into services.yaml using the %env(VAR)% syntax. | «yes» Пояснение: In Symfony, %env(VAR)% is used to inject environment variable values into configuration files such as services.yaml.
Raw{"answer": "yes", "explanation": "In Symfony, %env(VAR)% is used to inject environment variable values into configuration files such as services.yaml."} | верно | %env(...)% резолвится в рантайме env-процессорами; docs — Env Var Processors. |
T23-L8 1.94 c | Symfony: configuration and services | Which Symfony environment variable enables debug mode (affects the profiler and Twig debugging)? | «app_debug» Пояснение: APP_DEBUG controls Symfony debug mode, affecting features like the profiler and Twig debugging.
Raw{"answer":"APP_DEBUG","explanation":"APP_DEBUG controls Symfony debug mode, affecting features like the profiler and Twig debugging."} | верно | APP_DEBUG=1 (в .env dev-окружения); окружение выбирает APP_ENV — см. T13-L6. |
T16-L1 3.51 c | Symfony: Messenger | A single message in Symfony Messenger can only have one handler. | «no» Пояснение: Symfony Messenger allows a single message to be handled by multiple handlers.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "Symfony Messenger allows a single message to be handled by multiple handlers." ⏎ } | верно | Messenger вызывает все хендлеры, подписанные на класс сообщения (docs — Multiple Handlers). |
T16-L2 1.69 c | Symfony: Messenger | The sync transport in Messenger queues the message for a worker, just like async. | «no» Пояснение: The sync transport dispatches messages immediately in the same process instead of queuing them for a worker.
Raw{"answer": "no", "explanation": "The sync transport dispatches messages immediately in the same process instead of queuing them for a worker."} | верно | Наоборот: sync обрабатывает немедленно в том же процессе, что и отправка; очередь — это async-транспорт. |
T16-L3 1.08 c | Symfony: Messenger | Which console command starts the worker that processes Messenger queue messages? | «messenger:consume» Пояснение: In Symfony, the messenger:consume command starts the worker that processes Messenger queue messages.
Raw{"answer": "messenger:consume", "explanation": "In Symfony, the messenger:consume command starts the worker that processes Messenger queue messages."} | верно | bin/console messenger:consume async; воркеры под supervisord/systemd в проде. |
T16-L4 3.17 c | Symfony: Messenger | Retries for failed messages (retry_strategy) are configured per Messenger transport. | «yes» Пояснение: In Symfony Messenger, retry_strategy is a per-transport transport configuration option.
Raw{"answer": "yes", "explanation": "In Symfony Messenger, retry_strategy is a per-transport transport configuration option."} | верно | retry_strategy на транспорте: max_retries, delay, multiplier; docs — Failed Messages & Retries. |
T16-L5 2.71 c | Symfony: Messenger | By default, Messenger serializes messages to JSON. | «yes» Пояснение: By default, Messenger uses JSON for serializing messages.
Raw{"answer":"yes","explanation":"By default, Messenger uses JSON for serializing messages."} | неверно верный: «no» | Дефолтный сериализатор — PhpSerializer (serialize()); JSON-сериализатор включается отдельно. |
T16-L6 26.52 c | Symfony: Messenger | Symfony Scheduler produces messages on a schedule and dispatches them through Messenger. | «yes» Пояснение: Symfony Scheduler schedules messages to be dispatched through Symfony Messenger when their scheduled time is reached.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Symfony Scheduler schedules messages to be dispatched through Symfony Messenger when their scheduled time is reached." ⏎ } | верно | Schedule → RecurringMessage → шина Messenger; docs — Scheduler. |
T16-L7 2.92 c | Symfony: Messenger | Which built-in Messenger transport stores messages in database tables via Doctrine? | «databasetransport» Пояснение: The Symfony Messenger DatabaseTransport uses Doctrine to persist messages in database tables.
Raw{ ⏎ "answer": "DatabaseTransport", ⏎ "explanation": "The Symfony Messenger DatabaseTransport uses Doctrine to persist messages in database tables." ⏎ } | неверно верный: «doctrine» | Транспорт doctrine (symfony/doctrine-messenger); таблица messenger_messages. В проекте стоит amqp-messenger + doctrine-messenger. |
T16-L8 1.1 c | Symfony: Messenger | The Messenger pipeline can be extended with custom middleware, placed before or after the built-in ones. | «yes» Пояснение: Symfony Messenger allows adding custom middleware and configuring their order relative to built-in middleware.
Raw{"answer":"yes","explanation":"Symfony Messenger allows adding custom middleware and configuring their order relative to built-in middleware."} | верно | messenger.bus.*.middleware в yaml; docs — Middleware. |
T28-L1 20.48 c | Symfony: versions | Symfony major releases come every two years, minor ones every six months (in May and November). | «yes» Пояснение: Symfony’s release policy is major releases every two years and minor releases every six months in May and November.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Symfony’s release policy is major releases every two years and minor releases every six months in May and November." ⏎ } | верно | Стандартный релизный цикл: 8.0 — ноябрь 2025, 8.1 — май 2026, 8.2 — ноябрь 2026. |
T28-L2 10.21 c | Symfony: versions | What is the minimum PHP version required by Symfony 8? | «8.4» Пояснение: Symfony 8 requires PHP 8.4 or higher.
Raw{"answer": "8.4", "explanation": "Symfony 8 requires PHP 8.4 or higher."} | верно | Symfony 8.0 поднял требование до PHP >= 8.4.1 (в vendor проекта: "php": ">=8.4.1"). |
T28-L3 1.94 c | Symfony: versions | Symfony 7.0 kept support for docblock annotations (validation, routes). | «no» Пояснение: Symfony 7.0 removed legacy docblock annotation support in favor of PHP attributes.
Raw{"answer":"no","explanation":"Symfony 7.0 removed legacy docblock annotation support in favor of PHP attributes."} | верно | Наоборот: в 7.0 аннотации удалены — только PHP-атрибуты (#[Route], #[Assert\NotBlank]). |
T28-L4 0.98 c | Symfony: versions | AssetMapper manages CSS/JS without node or webpack — via importmap.php. | «yes» Пояснение: AssetMapper is a PHP library that bundles CSS/JS assets and generates importmaps without requiring Node.js or webpack.
Raw{"answer": "yes", "explanation": "AssetMapper is a PHP library that bundles CSS/JS assets and generates importmaps without requiring Node.js or webpack."} | верно | symfony/asset-mapper (с 6.3, стандарт с 7.x); в проекте — importmap.php в корне и asset-mapper 8.1. |
T28-L5 2.13 c | Symfony: versions | Symfony 6.4 is a regular release without long-term support. | «no» Пояснение: Symfony 6.4 is an LTS release with long-term support.
Raw{"answer": "no", "explanation": "Symfony 6.4 is an LTS release with long-term support."} | верно | Наоборот: 6.4 — LTS (расширенная поддержка); LTS выходит вместе с очередным мажором (6.4 — вместе с 7.0). |
T28-L6 2.21 c | Symfony: versions | When moving to a new Symfony major version, deprecations of the previous branch keep working — major releases do not remove them. | «no» Пояснение: Symfony major releases do remove deprecations introduced in the previous major version.
Raw{"answer": "no", "explanation": "Symfony major releases do remove deprecations introduced in the previous major version."} | верно | Наоборот: мажорный релиз удаляет всё устаревшее (7.0 убрал деприкейшены 6.x, 8.0 — 7.x). |
T28-L7 1.37 c | Symfony: versions | Every Symfony major release is accompanied by an UPGRADE guide listing the changes. | «yes» Пояснение: Symfony provides an UPGRADE guide for each major release documenting breaking changes and migration steps.
Raw{"answer": "yes", "explanation": "Symfony provides an UPGRADE guide for each major release documenting breaking changes and migration steps."} | верно | UPGRADE-7.0.md, UPGRADE-8.0.md в репозитории symfony/symfony. |
T28-L8 2.64 c | Symfony: versions | Which Symfony component manages assets and the importmap without node/webpack? | «assetmapperbundle» Пояснение: Symfony's AssetMapperBundle manages assets and importmap without requiring Node.js or Webpack.
Raw{ ⏎ "answer": "AssetMapperBundle", ⏎ "explanation": "Symfony's AssetMapperBundle manages assets and importmap without requiring Node.js or Webpack." ⏎ } | неверно верный: «asset-mapper» | symfony/asset-mapper 8.1 — в проекте. |
T29-L1 280.56 c | Symfony: 8.2 and beyond | As of 2026-11-07, Symfony 8.2 has already been released. | «— (нет ответа)» | не разобрано верный: «no» парсинг: нет | Наоборот: 8.2 ещё не выпущена — релиз в конце ноября 2026; последняя стабильная — 8.1. |
T29-L2 99.28 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» Пояснение: No, Symfony 8.2 is not the November 2026 release under the standard six-month Symfony schedule.
Raw{"answer":"no","explanation":"No, Symfony 8.2 is not the November 2026 release under the standard six-month Symfony schedule."} | неверно верный: «yes» | Политика релизов: 8.1 — май 2026, 8.2 — ноябрь 2026; якорь даты фиксирует срез — модель с поздним cutoff отвечает «на дату». |
T29-L3 14.28 c | Symfony: 8.2 and beyond | Which Symfony version comes after 8.1 (as of 2026-11-07)? | «8.2» Пояснение: The immediate successor to Symfony 8.1 in the release sequence is 8.2.
Raw{ ⏎ "answer": "8.2", ⏎ "explanation": "The immediate successor to Symfony 8.1 in the release sequence is 8.2." ⏎ } | верно | 8.2 — следующий минорный релиз (ноябрь 2026); после его выхода проект переходит с 8.1.* на 8.2.*. |
T29-L4 2.68 c | Symfony: 8.2 and beyond | Symfony 8.2 is a major release requiring applications to be rewritten for new APIs. | «no» Пояснение: Symfony 8.2 is a minor point release, not a major release, and Symfony upgrades generally do not require rewriting an entire application.
Raw{"answer": "no", "explanation": "Symfony 8.2 is a minor point release, not a major release, and Symfony upgrades generally do not require rewriting an entire application."} | верно | Наоборот: 8.2 — минорный релиз; новые возможности без поломки обратной совместимости. Мажор — 9.0. |
T29-L5 4.32 c | Symfony: 8.2 and beyond | Updating within a major branch (8.1 → 8.2) should not require code changes — backward compatibility is preserved. | «yes» Пояснение: PHP maintains backward compatibility within a major version series, so upgrading from 8.1 to 8.2 (a minor update within the 8.x major branch) will not require code changes.
Raw{"answer": "yes", "explanation": "PHP maintains backward compatibility within a major version series, so upgrading from 8.1 to 8.2 (a minor update within the 8.x major branch) will not require code changes."} | верно | Политика Symfony: минорные релизы обратно совместимы; BC-break допустим только в мажорных. |
T29-L6 232.19 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 final 8.x minor release before Symfony 9.0.
Raw{ ⏎ "answer": "8.4", ⏎ "explanation": "Symfony 8.4 is the final 8.x minor release before Symfony 9.0." ⏎ } | верно | По циклу: 8.2 (ноя 2026), 8.3 (май 2027), 8.4 (ноя 2027, вместе с 9.0) — как 6.4 выходила вместе с 7.0. |
T29-L7 138.13 c | Symfony: 8.2 and beyond | Symfony 8.2 will require PHP 8.5 — you would have to upgrade PHP along with it. | «yes» Пояснение: Symfony 8.2’s minimum PHP requirement is PHP 8.5, so PHP must be upgraded if needed.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Symfony 8.2’s minimum PHP requirement is PHP 8.5, so PHP must be upgraded if needed." ⏎ } | неверно верный: «no» | Наоборот: минорные релизы не поднимают требования PHP; для всей ветки 8.x остаётся PHP >= 8.4. |
T29-L8 4.07 c | Symfony: 8.2 and beyond | Deprecations added in the 8.x branch will not be removed before Symfony 9.0. | «yes» Пояснение: Deprecations introduced in the 8.x branch remain active throughout all 8.x releases and are only removed in Symfony 9.0, so they will not be removed before 9.0.
Raw{"answer": "yes", "explanation": "Deprecations introduced in the 8.x branch remain active throughout all 8.x releases and are only removed in Symfony 9.0, so they will not be removed before 9.0."} | верно | Политика: деприкейшены живут до следующего мажора; 9.0 — ноябрь 2027. |
T21-L1 1.47 c | Twig | Inside {{ }}, Twig allows calling arbitrary PHP code directly. | «no» Пояснение: Twig's {{ }} syntax is designed for safe expression output, not direct arbitrary PHP code execution.
Raw{"answer":"no","explanation":"Twig's {{ }} syntax is designed for safe expression output, not direct arbitrary PHP code execution."} | верно | Twig — DSL: только разрешённые окружением функции/фильтры; произвольный PHP не исполняется. |
T21-L2 5.77 c | Twig | By default, Twig auto-escapes printed variables. | «yes» Пояснение: Twig enables auto-escaping of printed variables by default to help prevent XSS attacks.
Raw{"answer": "yes", "explanation": "Twig enables auto-escaping of printed variables by default to help prevent XSS attacks."} | верно | Autoescape включён по умолчанию; {{ '<b>' }} → <b>. Проверено на Twig 3.30. |
T21-L3 0.78 c | Twig | The Twig |e filter escapes a string for safe output in an HTML context. | «yes» Пояснение: The Twig |e filter performs HTML escaping by default for safe HTML output.
Raw{"answer":"yes","explanation":"The Twig |e filter performs HTML escaping by default for safe HTML output."} | верно | |e ('html') по умолчанию; есть контексты js/url/css. От SQL-инъекций он не защищает — это задача подготовленных запросов Doctrine. |
T21-L4 1.2 c | Twig | Which filter from twig/intl-extra formats a number according to a locale? | «number_format» Пояснение: The twig/intl-extra number_format filter formats a number according to a locale.
Raw{"answer": "number_format", "explanation": "The twig/intl-extra number_format filter formats a number according to a locale."} | неверно верный: «format_number» | |format_number(locale=...) из IntlExtension (twig/intl-extra есть в проекте). Проверено на Twig 3.30: 12345.6 → 12 345,6 (ru). |
T21-L5 2.47 c | Twig | The |raw filter disables auto-escaping for the value. | «yes» Пояснение: In Twig, the raw filter disables HTML auto-escaping for the value.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "In Twig, the raw filter disables HTML auto-escaping for the value." ⏎ } | верно | {{ x|raw }} выводит HTML как есть; опасно с пользовательскими данными. Проверено на Twig 3.30. |
T21-L6 1.5 c | Twig | In Twig, {{ }} prints an expression value, while {% %} executes tags — conditions, loops, set. | «yes» Пояснение: In Twig, {{ }} outputs an expression value, while {% %} executes template tags such as conditions, loops, and set.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "In Twig, {{ }} outputs an expression value, while {% %} executes template tags such as conditions, loops, and set." ⏎ } | верно | Два блока синтаксиса Twig: вывод (echo) против логики. |
T21-L7 1.7 c | Twig | In Twig you cannot declare a variable inside a template — values only come from the controller. | «no» Пояснение: Twig allows you to declare or update variables inside a template using the set tag.
Raw{"answer":"no","explanation":"Twig allows you to declare or update variables inside a template using the set tag."} | верно | {% set y = ... %} объявляет переменную в шаблоне. Проверено на Twig 3.30. |
T21-L8 0.81 c | Twig | Which Twig function dumps the debug structure of a variable (array, object)? | «dump» Пояснение: The dump function displays the debug structure of a variable.
Raw{"answer":"dump","explanation":"The dump function displays the debug structure of a variable."} | верно | {{ dump(x) }} (DebugExtension; в Symfony доступна в dev-окружении). |
T24-L1 0.69 c | Bootstrap | Bootstrap is a CSS/JS library of ready-made UI components, not an SPA framework. | «yes» Пояснение: Bootstrap provides ready-made UI components with CSS/JS and is not a single-page application framework.
Raw{"answer": "yes", "explanation": "Bootstrap provides ready-made UI components with CSS/JS and is not a single-page application framework."} | верно | Компоненты и утилиты поверх вашего HTML; SPA-фреймворки (React/Vue) — другой класс инструментов. В проекте vendored 5.3.3. |
T24-L2 1.14 c | Bootstrap | Which Bootstrap class gives a responsive container with a fixed max width per breakpoint? | «container» Пояснение: Bootstrap's .container class provides a responsive, centered container with breakpoint-specific max widths.
Raw{ ⏎ "answer": "container", ⏎ "explanation": "Bootstrap's .container class provides a responsive, centered container with breakpoint-specific max widths." ⏎ } | верно | .container (фиксированная макс-ширина по брейкпоинтам) vs .container-fluid (на всю ширину). |
T24-L3 1.93 c | Bootstrap | The Bootstrap grid is built on CSS floats and splits a row into 16 columns. | «no» Пояснение: The Bootstrap grid is based on a 12-column layout, not 16 columns, and modern versions use flexbox rather than CSS floats.
Raw{"answer":"no","explanation":"The Bootstrap grid is based on a 12-column layout, not 16 columns, and modern versions use flexbox rather than CSS floats."} | верно | Наоборот: flexbox (с Bootstrap 4) и 12 колонок; float-сетка — это Bootstrap 3. |
T24-L4 5.27 c | Bootstrap | Bootstrap's named breakpoints (the infix used in class names) are sm, md, lg, xl, xxl — five of them. | «yes» Пояснение: In Bootstrap 5, the breakpoint suffixes used in class names (e.g., d-sm-block, p-md-3) are sm, md, lg, xl, and xxl, totaling five; xs is the base/default and is not used as an infix.
Raw{"answer": "yes", "explanation": "In Bootstrap 5, the breakpoint suffixes used in class names (e.g., d-sm-block, p-md-3) are sm, md, lg, xl, and xxl, totaling five; xs is the base/default and is not used as an infix."} | верно | Тиров всего шесть: xs (без инфикса) + пять именованных (576/768/992/1200/1400 px). |
T24-L5 13.12 c | Bootstrap | Utilities like .mt-3 or .px-2 use the spacing scale: the number is a multiple of $spacer. | «yes» Пояснение: Spacing utilities use Tailwind's spacing scale, where the number represents a multiple of the base spacing value.
Raw{"answer":"yes","explanation":"Spacing utilities use Tailwind's spacing scale, where the number represents a multiple of the base spacing value."} | неверно верный: «no» | Spacing utilities; $spacer = 1rem. |
T24-L6 1.09 c | Bootstrap | Which Bootstrap 5 data attribute enables an interactive component (e.g. dropdown) on an element? | «data-bs-toggle» Пояснение: In Bootstrap 5, the data-bs-toggle attribute (e.g., data-bs-toggle="dropdown") is used to enable interactive components on an element.
Raw{"answer": "data-bs-toggle", "explanation": "In Bootstrap 5, the data-bs-toggle attribute (e.g., data-bs-toggle=\"dropdown\") is used to enable interactive components on an element."} | верно | data-bs-toggle="dropdown" и т.п.; в Bootstrap 4 атрибут назывался data-toggle. |
T24-L7 0.85 c | Bootstrap | Bootstrap 5 components work without jQuery — in plain vanilla JS. | «yes» Пояснение: Bootstrap 5 does not require jQuery and uses vanilla JavaScript for its components.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "Bootstrap 5 does not require jQuery and uses vanilla JavaScript for its components." ⏎ } | верно | jQuery удалён в Bootstrap 5.0: data-bs-* атрибуты и JS API. В проекте vendored 5.3.3. |
T24-L8 7.85 c | Bootstrap | Dark mode in Bootstrap is enabled with a .dark class on the root element. | «no» Пояснение: Bootstrap 5 dark mode is enabled with the data-bs-theme="dark" attribute, not a .dark class on the root element.
Raw{"answer":"no","explanation":"Bootstrap 5 dark mode is enabled with the data-bs-theme=\"dark\" attribute, not a .dark class on the root element."} | верно | Наоборот: тема включается атрибутом data-bs-theme="dark" (Color modes, с 5.3); класса .dark не существует. В проекте 5.3.3. |
T14-L1 1.34 c | Doctrine | Doctrine ORM creates database tables on the fly the first time an entity is used at runtime. | «no» Пояснение: Doctrine ORM does not create database tables automatically on first use; you must generate the schema using a tool such as doctrine:orm:schema:update or migrations.
Raw{"answer":"no","explanation":"Doctrine ORM does not create database tables automatically on first use; you must generate the schema using a tool such as doctrine:orm:schema:update or migrations."} | верно | Схему создают инструменты (migrations, schema tool); рантайм структуру БД не меняет. |
T14-L2 1.11 c | Doctrine | Which EntityManager method marks a new object as managed without executing SQL until flush()? | «persist()» Пояснение: In Doctrine ORM, EntityManager::persist() registers an entity as managed (pending insertion) without issuing SQL; the SQL is only executed on flush().
Raw{"answer": "persist()", "explanation": "In Doctrine ORM, EntityManager::persist() registers an entity as managed (pending insertion) without issuing SQL; the SQL is only executed on flush()."} | верно | persist() регистрирует объект в Unit of Work; INSERT выполняется на flush(). |
T14-L3 1.4 c | Doctrine | In Doctrine ORM 3, the EntityManager::merge() method exists and makes the passed object managed. | «yes» Пояснение: In Doctrine ORM 3, EntityManager::merge() exists and makes the passed persistent object managed by the EntityManager.
Raw{"answer": "yes", "explanation": "In Doctrine ORM 3, EntityManager::merge() exists and makes the passed persistent object managed by the EntityManager."} | неверно верный: «no» | В ORM 3 merge() удалён (в vendor проекта 3.7.6 метода нет); в Doctrine 2.x merge() возвращал управляемую копию. Версия зафиксирована — ORM 3. |
T14-L4 1.1 c | Doctrine | DQL queries are written in terms of entities and their fields, not tables and columns. | «yes» Пояснение: DQL targets mapped entities and their mapped properties rather than physical database tables and columns.
Raw{"answer":"yes","explanation":"DQL targets mapped entities and their mapped properties rather than physical database tables and columns."} | верно | Doctrine транслирует DQL в SQL; docs — DQL (Doctrine Query Language). |
T14-L5 2.04 c | Doctrine | What does $repository->find(999) return when no record with id 999 exists? | «null» Пояснение: In Doctrine, find() returns null when no entity is found.
Raw{ ⏎ "answer": "null", ⏎ "explanation": "In Doctrine, find() returns null when no entity is found." ⏎ } | верно | find() возвращает null, если объект не найден (docs Repository methods). |
T14-L6 5.06 c | Doctrine | DoctrineBundle in Symfony automatically calls flush() at the end of every request. | «no» Пояснение: DoctrineBundle does not automatically call flush() by default; developers must explicitly invoke it to persist changes to the database.
Raw{"answer": "no", "explanation": "DoctrineBundle does not automatically call flush() by default; developers must explicitly invoke it to persist changes to the database."} | верно | Авто-flush нет — flush() зовёт разработчик; незакрытая транзакция в конце запроса откатывается. |
T14-L7 1.24 c | Doctrine | For a managed entity, changing a property is enough: flush() commits the change without an explicit persist() — the Unit of Work tracks changes. | «yes» Пояснение: A managed entity's property changes are tracked by the Unit of Work and can be committed by flush().
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "A managed entity's property changes are tracked by the Unit of Work and can be committed by flush()." ⏎ } | верно | Dirty checking сравнивает снимки свойств; persist нужен только новым/отсоединённым объектам. |
T14-L8 2.14 c | Doctrine | remove() executes the SQL DELETE immediately, without waiting for flush(). | «no» Пояснение: remove() only marks the entity for deletion; the SQL DELETE is executed when flush() is called.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "remove() only marks the entity for deletion; the SQL DELETE is executed when flush() is called." ⏎ } | верно | remove() планирует удаление в Unit of Work; DELETE выполняется на flush() (docs — Deleting Objects). |
T15-L1 1.0 c | PostgreSQL | PostgreSQL uses MVCC, therefore readers block writers and writers block readers. | «no» Пояснение: PostgreSQL's MVCC generally lets readers and writers run concurrently without blocking each other.
Raw{"answer":"no","explanation":"PostgreSQL's MVCC generally lets readers and writers run concurrently without blocking each other."} | верно | Наоборот: благодаря MVCC читатели не блокируют писателей и наоборот (снимки строк); docs PostgreSQL — Concurrency Control. |
T15-L2 1.08 c | PostgreSQL | Which SQL command shows a query's execution plan without executing the query? | «explain» Пояснение: EXPLAIN displays the query execution plan without running the query.
Raw{"answer": "EXPLAIN", "explanation": "EXPLAIN displays the query execution plan without running the query."} | верно | EXPLAIN без ANALYZE только строит план; проверено на PostgreSQL 17.7. |
T15-L3 4.32 c | PostgreSQL | SERIAL and GENERATED ... AS IDENTITY are just two names for the same mechanism. | «no» Пояснение: They are related but not the same: SERIAL is a convenience shorthand for an integer column with a default sequence, while GENERATED ... AS IDENTITY is a standard identity column with its own attributes.
Raw{"answer":"no","explanation":"They are related but not the same: SERIAL is a convenience shorthand for an integer column with a default sequence, while GENERATED ... AS IDENTITY is a standard identity column with its own attributes."} | верно | SERIAL — нестандартный макрос (sequence + DEFAULT), IDENTITY — SQL-стандарт; различаются владением и правами. Оба есть в PG 17 (проверено). |
T15-L4 4.57 c | PostgreSQL | By default, a PostgreSQL UNIQUE constraint allows only one row with NULL in the column. | «no» Пояснение: By default, PostgreSQL treats NULL values as distinct, so a UNIQUE constraint allows multiple rows with NULL in that column.
Raw{"answer": "no", "explanation": "By default, PostgreSQL treats NULL values as distinct, so a UNIQUE constraint allows multiple rows with NULL in that column."} | верно | Наоборот: NULLS DISTINCT по умолчанию — несколько NULL допустимы; NULLS NOT DISTINCT — опция с PG 15. Проверено на PG 17.7. |
T15-L5 0.77 c | PostgreSQL | Which PostgreSQL aggregate function concatenates strings with a separator? | «string_agg» Пояснение: PostgreSQL's string_agg() aggregate function concatenates input strings with a specified separator.
Raw{"answer": "string_agg", "explanation": "PostgreSQL's string_agg() aggregate function concatenates input strings with a specified separator."} | верно | string_agg(значение, разделитель); проверено на PostgreSQL 17.7. |
T15-L6 1.2 c | PostgreSQL | Plain VACUUM returns the space occupied by dead tuples to the operating system. | «no» Пояснение: Plain VACUUM reclaims dead tuple space for reuse but does not return it to the operating system.
Raw{"answer": "no", "explanation": "Plain VACUUM reclaims dead tuple space for reuse but does not return it to the operating system."} | верно | VACUUM помечает место для переиспользования внутри таблицы; ОС его возвращает только VACUUM FULL (с эксклюзивной блокировкой). |
T15-L7 0.87 c | PostgreSQL | Which keyword in a window function definition partitions rows into groups the function is computed over? | «partition by» Пояснение: In SQL window functions, the PARTITION BY clause divides the result set into partitions (groups) over which the window function is computed.
Raw{"answer": "PARTITION BY", "explanation": "In SQL window functions, the PARTITION BY clause divides the result set into partitions (groups) over which the window function is computed."} | верно | OVER (PARTITION BY ...); проверено на PostgreSQL 17.7. |
T15-L8 1.95 c | PostgreSQL | The READ COMMITTED isolation level protects against non-repeatable reads. | «no» Пояснение: READ COMMITTED allows a second read to see different committed data, so it does not protect against non-repeatable reads.
Raw{"answer":"false","explanation":"READ COMMITTED allows a second read to see different committed data, so it does not protect against non-repeatable reads."} | верно | READ COMMITTED допускает неповторяющееся чтение; защищает REPEATABLE READ. Проверено: SHOW transaction_isolation → read committed. |
T17-L1 1.35 c | PostgreSQL: transactions and indexes | By default, PostgreSQL wraps each single SQL statement in its own implicit transaction (autocommit). | «yes» Пояснение: PostgreSQL runs in autocommit mode by default, meaning each individual SQL statement is implicitly wrapped in its own transaction that is committed upon completion unless an explicit BEGIN/COMMIT block is used.
Raw{"answer":"yes","explanation":"PostgreSQL runs in autocommit mode by default, meaning each individual SQL statement is implicitly wrapped in its own transaction that is committed upon completion unless an explicit BEGIN/COMMIT block is used."} | верно | Без BEGIN каждый оператор коммитится сам; docs PostgreSQL — Transactions. Проверено на PG 17. |
T17-L2 0.88 c | PostgreSQL: transactions and indexes | Which SQL command ends a transaction, committing all its changes? | «commit» Пояснение: COMMIT ends the current transaction and permanently saves its changes.
Raw{"answer": "COMMIT", "explanation": "COMMIT ends the current transaction and permanently saves its changes."} | верно | COMMIT (END — синоним). Проверено на PG 17. |
T17-L3 1.19 c | PostgreSQL: transactions and indexes | Indexes speed up more than SELECT: UPDATE and DELETE with a search on an indexed column benefit too. | «yes» Пояснение: Indexes help locate rows efficiently, so UPDATE and DELETE operations that filter on an indexed column also benefit by avoiding full table scans.
Raw{"answer": "yes", "explanation": "Indexes help locate rows efficiently, so UPDATE and DELETE operations that filter on an indexed column also benefit by avoiding full table scans."} | верно | Поиск строк для изменения идёт по индексу; docs PostgreSQL — Indexes. |
T17-L4 0.85 c | PostgreSQL: transactions and indexes | To roll back part of the statements inside a transaction, PostgreSQL uses SAVEPOINT. | «yes» Пояснение: SAVEPOINT lets you roll back a portion of a transaction without ending the whole transaction.
Raw{"answer": "yes", "explanation": "SAVEPOINT lets you roll back a portion of a transaction without ending the whole transaction."} | верно | SAVEPOINT name; ROLLBACK TO name — частичный откат без отмены всей транзакции. Проверено на PG 17. |
T17-L5 0.92 c | PostgreSQL: transactions and indexes | EXPLAIN ANALYZE shows the query plan without executing the query. | «no» Пояснение: EXPLAIN ANALYZE actually executes the query to provide execution statistics in addition to the query plan.
Raw{"answer":"no","explanation":"EXPLAIN ANALYZE actually executes the query to provide execution statistics in addition to the query plan."} | верно | Наоборот: ANALYZE реально выполняет запрос (с побочными эффектами!) и показывает фактические времена узлов; план без выполнения — plain EXPLAIN. |
T17-L6 0.64 c | PostgreSQL: transactions and indexes | Which PostgreSQL extension adds vector types and indexes for embedding search? | «pgvector» Пояснение: pgvector is the PostgreSQL extension that provides vector data types and indexes for embedding search.
Raw{"answer":"pgvector","explanation":"pgvector is the PostgreSQL extension that provides vector data types and indexes for embedding search."} | верно | CREATE EXTENSION vector (проект pgvector; в проекте образ pgvector/pgvector:pg17). |
T17-L7 0.89 c | PostgreSQL: transactions and indexes | A partial index (CREATE INDEX ... WHERE ...) is built only over rows satisfying the condition. | «yes» Пояснение: A partial index in PostgreSQL includes only rows that satisfy its WHERE condition.
Raw{"answer": "yes", "explanation": "A partial index in PostgreSQL includes only rows that satisfy its WHERE condition."} | верно | docs PostgreSQL — Partial Indexes; типичный кейс — индекс по «активным» записям. |
T17-L8 3.24 c | PostgreSQL: transactions and indexes | The SERIALIZABLE level in PostgreSQL is implemented by locking the rows a transaction reads. | «no» Пояснение: PostgreSQL implements SERIALIZABLE using MVCC snapshots and serializable transaction management (S2) that detects serialization anomalies at commit time, rather than by acquiring locks on rows it reads.
Raw{"answer": "no", "explanation": "PostgreSQL implements SERIALIZABLE using MVCC snapshots and serializable transaction management (S2) that detects serialization anomalies at commit time, rather than by acquiring locks on rows it reads."} | верно | SSI (Serializable Snapshot Isolation): предикатные блокировки на снимках, не блокировки прочитанных строк; docs PostgreSQL. |
T19-L1 1.05 c | HTTP and REST API | HTTP status 201 means the request resulted in a new resource being created. | «yes» Пояснение: HTTP status 201 Created indicates that the request successfully created a new resource.
Raw{"answer":"yes","explanation":"HTTP status 201 Created indicates that the request successfully created a new resource."} | верно | 201 Created; обычно на POST, часто с Location; RFC 9110. |
T19-L2 1.01 c | HTTP and REST API | Which HTTP status means a successful request with an empty response body (e.g. after DELETE)? | «204» Пояснение: HTTP 204 No Content indicates a successful request with no response body, commonly used after a DELETE.
Raw{"answer": 204, "explanation": "HTTP 204 No Content indicates a successful request with no response body, commonly used after a DELETE."} | верно | 204 No Content; RFC 9110. |
T19-L3 2.16 c | HTTP and REST API | The DELETE method is idempotent per the HTTP specification: repeating the request for the same resource does not change the outcome. | «yes» Пояснение: HTTP defines DELETE as idempotent, so repeated identical delete requests have the same overall effect.
Raw{"answer":"yes","explanation":"HTTP defines DELETE as idempotent, so repeated identical delete requests have the same overall effect."} | верно | RFC 9110: DELETE идемпотентен (как PUT); идемпотентность ≠ безопасность — ресурс удаляется при первом вызове. |
T19-L4 1.81 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 (in the response), not the client, to indicate which origins are allowed to access the resource.
Raw{"answer": "no", "explanation": "The Access-Control-Allow-Origin header is sent by the server (in the response), not the client, to indicate which origins are allowed to access the resource."} | верно | Наоборот: заголовок шлёт СЕРВЕР в ответе, разрешая браузеру cross-origin запрос (CORS); в проекте nelmio/cors-bundle. |
T19-L5 0.87 c | HTTP and REST API | Status 429 Too Many Requests is used when a client exceeds a rate limit. | «yes» Пояснение: HTTP status 429 indicates the client has sent too many requests in a given period, i.e., exceeded the rate limit.
Raw{"answer":"yes","explanation":"HTTP status 429 indicates the client has sent too many requests in a given period, i.e., exceeded the rate limit."} | верно | 429 (+ Retry-After); RFC 6585. В проекте symfony/rate-limiter. |
T19-L6 1.27 c | HTTP and REST API | 5xx codes mean a client error, while 4xx means a server-side error. | «no» Пояснение: The statement is reversed: 4xx codes indicate client errors and 5xx codes indicate server errors.
Raw{"answer":"no","explanation":"The statement is reversed: 4xx codes indicate client errors and 5xx codes indicate server errors."} | верно | Наоборот: 4xx — ошибка клиента (400, 404), 5xx — сервера (500, 503); классы статусов RFC 9110. |
T19-L7 0.9 c | HTTP and REST API | Which HTTP header indicates the MIME type of the request or response body? | «content-type» Пояснение: The Content-Type HTTP header specifies the MIME type of the request or response body.
Raw{"answer": "Content-Type", "explanation": "The Content-Type HTTP header specifies the MIME type of the request or response body."} | верно | Content-Type: application/json и т.п. |
T19-L8 15.42 c | HTTP and REST API | PATCH is not required to be idempotent per RFC 5789, unlike PUT. | «yes» Пояснение: PATCH applies partial modifications and can have cumulative effects on retries, unlike PUT, which is idempotent.
Raw{ ⏎ "answer": "yes", ⏎ "explanation": "PATCH applies partial modifications and can have cumulative effects on retries, unlike PUT, which is idempotent." ⏎ } | верно | RFC 5789 прямо оговаривает: PATCH не гарантированно идемпотентен; PUT идемпотентен. |
T20-L1 1.61 c | Security and OAuth | Checking a password by comparing its hash to the stored hash with a plain == is sufficient. | «no» Пояснение: Use password_verify for password hashes because a plain == comparison can be vulnerable to timing attacks and does not properly handle PHP password hash formats.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "Use password_verify for password hashes because a plain == comparison can be vulnerable to timing attacks and does not properly handle PHP password hash formats." ⏎ } | верно | Нужна постоянновременная проверка (password_verify) — timing-атаки; соль и алгоритм уже внутри хеша. |
T20-L2 0.84 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 typically generated server-side, tied to the user's session, and validated by the server on state-changing requests to prevent cross-site request forgery.
Raw{"answer":"yes","explanation":"CSRF tokens are typically generated server-side, tied to the user's session, and validated by the server on state-changing requests to prevent cross-site request forgery."} | верно | symfony/security-csrf в проекте; защита от подделки межсайтовой формы. |
T20-L3 0.96 c | Security and OAuth | Which HTTP header enables the CSP (Content Security Policy) policy? | «content-security-policy» Пояснение: The Content-Security-Policy HTTP header is used to specify Content Security Policy directives.
Raw{ ⏎ "answer": "Content-Security-Policy", ⏎ "explanation": "The Content-Security-Policy HTTP header is used to specify Content Security Policy directives." ⏎ } | верно | Content-Security-Policy; белые списки источников скриптов/стилей против XSS. |
T20-L4 1.59 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 primarily an authorization framework, and access tokens grant access to resources rather than directly identifying the user.
Raw{"answer":"no","explanation":"OAuth 2.0 is primarily an authorization framework, and access tokens grant access to resources rather than directly identifying the user."} | верно | OAuth 2.0 — авторизация/делегирование доступа; аутентификацию добавляет OpenID Connect. В проекте knpuniversity/oauth2-client-bundle (yandex/github/google). |
T20-L5 1.21 c | Security and OAuth | XSS is prevented by validating input on the server before writing it to the database. | «no» Пояснение: XSS must be prevented by context-aware output encoding when data is rendered, not solely by validating input before saving it.
Raw{ ⏎ "answer": "no", ⏎ "explanation": "XSS must be prevented by context-aware output encoding when data is rendered, not solely by validating input before saving it." ⏎ } | верно | XSS лечится контекстным экранированием НА ВЫВОДЕ (Twig autoescape, CSP); валидация ввода не покрывает все контексты вывода. |
T20-L6 1.05 c | Security and OAuth | In the OAuth 2.0 authorization code flow, which parameter arrives at the redirect_uri and is exchanged for an access token? | «code» Пояснение: The authorization code parameter arrives at the redirect_uri and is exchanged for an access token.
Raw{"answer":"code","explanation":"The authorization code parameter arrives at the redirect_uri and is exchanged for an access token."} | верно | Параметр code; обмен на токен POST-ом на /token с client_secret. |
T20-L7 0.85 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 designed to be long-lived and can be used to request new access tokens without requiring the user to log in again.
Raw{"answer": "yes", "explanation": "Refresh tokens are designed to be long-lived and can be used to request new access tokens without requiring the user to log in again."} | верно | Стандартная схема OAuth/OIDC: короткий access + длинный refresh. |
T20-L8 3.39 c | Security and OAuth | A password salt must be kept secret: without it the hash cannot be verified. | «no» Пояснение: A salt is not required to be secret; in modern practice (e.g., PHP's password_hash, bcrypt, argon2) the salt is stored in plaintext alongside the hash, and its purpose is to prevent rainbow-table/precomputation attacks, not to provide confidentiality.
Raw{"answer": "no", "explanation": "A salt is not required to be secret; in modern practice (e.g., PHP's password_hash, bcrypt, argon2) the salt is stored in plaintext alongside the hash, and its purpose is to prevent rainbow-table/precomputation attacks, not to provide confidentiality."} | верно | Соль хранится открыто (password_hash включает её в строку хеша); секретность соли не нужна. |
T18-L1 5.21 c | Testing: PHPUnit | PHPUnit runs test methods of any class — extending TestCase is not required. | «no» Пояснение: PHPUnit test classes must extend TestCase to be discovered and run.
Raw{"answer":"no","explanation":"PHPUnit test classes must extend TestCase to be discovered and run."} | верно | Тестом считается метод класса, наследующего TestCase (PHPUnit 10). |
T18-L2 1.94 c | Testing: PHPUnit | In PHPUnit, setUp() runs once before all tests of the class. | «no» Пояснение: setUp() runs before each test, while setUpBeforeClass() runs once before all tests in the class.
Raw{"answer":"no","explanation":"setUp() runs before each test, while setUpBeforeClass() runs once before all tests in the class."} | верно | setUp() — перед КАЖДЫМ тестом; один раз на класс — setUpBeforeClass(). Проверено живым счётчиком на PHPUnit 10.5. |
T18-L3 1.65 c | Testing: PHPUnit | A data provider lets a test run with exactly one set of arguments. | «no» Пояснение: A data provider can yield multiple sets of arguments, each causing a separate test run.
Raw{"answer": "no", "explanation": "A data provider can yield multiple sets of arguments, each causing a separate test run."} | верно | Наоборот: наборов может быть сколько угодно — тест выполняется по разу на каждый. Проверено на PHPUnit 10.5 (#[DataProvider]). |
T18-L4 0.83 c | Testing: PHPUnit | Which PHPUnit method declares an expectation that an exception of a given class is thrown? | «expectexception» Пояснение: expectException() is the PHPUnit method used to declare that a test expects an exception of a given class to be thrown.
Raw{"answer": "expectException", "explanation": "expectException() is the PHPUnit method used to declare that a test expects an exception of a given class to be thrown."} | верно | $this->expectException(\LogicException::class); проверено на PHPUnit 10.5. |
T18-L5 0.96 c | Testing: PHPUnit | In PHPUnit, a stub verifies which methods were called on it, while a mock only returns data. | «no» Пояснение: A stub primarily returns predefined data, while a mock can also verify method calls and expectations.
Raw{"answer": "no", "explanation": "A stub primarily returns predefined data, while a mock can also verify method calls and expectations."} | верно | Наоборот: стаб подставляет данные, мок проверяет взаимодействия (createStub/createMock); docs PHPUnit — Test Doubles. |
T18-L6 0.75 c | Testing: PHPUnit | In PHPUnit 10+, the recommended way to pass data to a test is the #[DataProvider] attribute (the @dataProvider annotation is deprecated). | «yes» Пояснение: PHPUnit 10+ deprecates annotation-based attributes and recommends using the #[DataProvider] PHP attribute for data provider tests.
Raw{"answer":"yes","explanation":"PHPUnit 10+ deprecates annotation-based attributes and recommends using the #[DataProvider] PHP attribute for data provider tests."} | верно | Аннотация ещё парсится в PHPUnit 10/11 (AnnotationParser в 10.5.66), удаление — в 12; атрибут — стандарт. |
T18-L7 148.0 c | Testing: PHPUnit | PHPUnit does not allow one test to depend on the result of another. | «yes» Пояснение: PHPUnit tests are intended to be independent and should not rely on another test's result.
Raw{"answer": "yes", "explanation": "PHPUnit tests are intended to be independent and should not rely on another test's result."} | неверно верный: «no» | Зависимости есть: #[Depends] — зависимый тест не запустится, еслиProducer упал. |
T18-L8 1.95 c | Testing: PHPUnit | Which PHPUnit command-line option makes tests run in random order? | «--random-order» Пояснение: PHPUnit uses the --random-order option to shuffle the execution order of tests.
Raw{"answer": "--random-order", "explanation": "PHPUnit uses the --random-order option to shuffle the execution order of tests."} | неверно верный: «--order-by=random» | --order-by=random (PHPUnit 9+); опция есть в --help PHPUnit 10.5 (проектная). |
T01-L9 12.87 c | Syntax and operators | What does this code output?
```php
echo intdiv(7, 2) . intdiv(-7, 2);
``` | «3-4» Пояснение: intdiv(7, 2) is 3 and intdiv(-7, 2) is -4, so the concatenation outputs 3-4.
Raw{ ⏎ "answer": "3-4", ⏎ "explanation": "intdiv(7, 2) is 3 and intdiv(-7, 2) is -4, so the concatenation outputs 3-4." ⏎ } | неверно верный: «3-3» | intdiv truncates toward zero: intdiv(-7, 2) = -3, not -4. |
T01-L10 16.61 c | Syntax and operators | What does this code output?
```php
echo -3 ** 2;
``` | «-9» Пояснение: In PHP, the ** operator has higher precedence than the unary minus, so -3 ** 2 is evaluated as -(3 ** 2) which equals -9.
Raw{"answer": "-9", "explanation": "In PHP, the ** operator has higher precedence than the unary minus, so -3 ** 2 is evaluated as -(3 ** 2) which equals -9."} | верно | ** is right-associative and binds tighter than unary minus: -(3²). |
T02-L9 15.75 c | Types and comparisons | What does this code output?
```php
echo '1e1' == '10' ? 'true' : 'false';
``` | «true» Пояснение: Both strings are numeric, so they are compared numerically and are equal.
Raw{ ⏎ "answer": "true", ⏎ "explanation": "Both strings are numeric, so they are compared numerically and are equal." ⏎ } | верно | Both strings are numeric — compared as numbers: 10 == 10. |
T02-L10 56.47 c | Types and comparisons | What does this code output?
```php
switch ('a') {
case 0: echo 'zero'; break;
default: echo 'other';
}
``` | «other» Пояснение: In current PHP, 'a' is not equal to 0, so the default case runs.
Raw{ ⏎ "answer": "other", ⏎ "explanation": "In current PHP, 'a' is not equal to 0, so the default case runs." ⏎ } | верно | PHP 8: 'a' == 0 → false (used to be true) — default fires. |
T03-L9 88.12 c | Strings | What does this code output?
```php
echo strtr('abc', ['a' => '1', 'ab' => '2']);
``` | «2c» Пояснение: strtr with an array performs a single pass and matches the longest available key, so 'ab' is replaced with '2'.
Raw{"answer": "2c", "explanation": "strtr with an array performs a single pass and matches the longest available key, so 'ab' is replaced with '2'."} | верно | strtr with an array prefers the longest matching key. |
T03-L10 59.54 c | Strings | What does this code output?
```php
echo '[' . substr('hello', -10) . ']';
``` | «[hello]» Пояснение: The negative offset -10 is beyond the start of the 5-character string, so PHP treats it as 0 and returns the whole string.
Raw{ ⏎ "answer": "[hello]", ⏎ "explanation": "The negative offset -10 is beyond the start of the 5-character string, so PHP treats it as 0 and returns the whole string." ⏎ } | верно | A negative start beyond the string is clamped to the beginning. |
T04-L9 16.13 c | Arrays | What does this code output?
```php
$a = ['k' => 1, 'n' => 2];
$b = ['k' => 9, 'm' => 3];
echo implode(',', array_keys($a + $b));
``` | «k,n,m» Пояснение: The array + operator keeps left-side values for shared keys and then appends new right-side keys in insertion order.
Raw{ ⏎ "answer": "k,n,m", ⏎ "explanation": "The array + operator keeps left-side values for shared keys and then appends new right-side keys in insertion order." ⏎ } | верно | The + operator: on duplicate string keys the left array wins. |
T04-L10 17.72 c | Arrays | What does this code output?
```php
$a = [[1, 'x', 2], [2, 'y', 1], [3, 'z', 2]];
usort($a, fn($p, $q) => $p[2] <=> $q[2]);
echo implode('', array_column($a, 1));
``` | «yxz» Пояснение: The usort sorts by the third element (index 2) ascending, giving order [2,'y',1], [1,'x',2], [3,'z',2]; array_column($a, 1) extracts 'y', 'x', 'z', and implode concatenates them into 'yxz'.
Raw{"answer": "yxz", "explanation": "The usort sorts by the third element (index 2) ascending, giving order [2,'y',1], [1,'x',2], [3,'z',2]; array_column($a, 1) extracts 'y', 'x', 'z', and implode concatenates them into 'yxz'."} | верно | Sorts are stable since 8.0: x and z keep their order on a tie. |
T05-L10 26.07 c | Functions and closures | What does this code output?
```php
function f(int $a, int $b): int
{
return $a - $b;
}
echo f(...['b' => 1, 'a' => 5]);
``` | «4» Пояснение: The spread call passes named arguments a=5 and b=1, so 5 - 1 is 4.
Raw{ ⏎ "answer": 4, ⏎ "explanation": "The spread call passes named arguments a=5 and b=1, so 5 - 1 is 4." ⏎ } | верно | String keys of a spread array become named arguments. |
T05-L9 35.06 c | Functions and closures | What does this code output?
```php
class P
{
private int $v = 3;
public function g(): int { return $this->v; }
}
$p = new P;
$f = $p->g(...);
$p = null;
echo $f();
``` | «3» Пояснение: The first-class callable $f holds a reference to the original P object, so setting $p = null does not destroy it and $f() returns 3.
Raw{ ⏎ "answer": 3, ⏎ "explanation": "The first-class callable $f holds a reference to the original P object, so setting $p = null does not destroy it and $f() returns 3." ⏎ } | верно | First-class callable syntax binds $this at creation time. |
T06-L9 15.83 c | OOP: classes and inheritance | What does this code output?
```php
class A
{
public function who(): string { return static::class; }
}
class B extends A {}
echo (new B)->who();
``` | «b» Пояснение: static::class returns the actual class of the object calling the method, which is B.
Raw{ ⏎ "answer": "B", ⏎ "explanation": "static::class returns the actual class of the object calling the method, which is B." ⏎ } | верно | Late static binding: static::class is the receiver's class. |
T06-L10 61.01 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 property setter hook runs once and assigning to the same property inside it does not recursively trigger the hook, so $x becomes 5 * 2.
Raw{"answer": 10, "explanation": "The property setter hook runs once and assigning to the same property inside it does not recursively trigger the hook, so $x becomes 5 * 2."} | верно | Inside the set hook, $this->x writes the backing store (no recursion): 5*2. |
T07-L9 16.09 c | Interfaces, traits, enum | What does this code output?
```php
trait TA
{
public function f(): string { return 'A'; }
}
trait TB
{
public function f(): string { return 'B'; }
}
class TC
{
use TA, TB { TB::f insteadof TA; TA::f as g; }
}
echo (new TC)->f() . (new TC)->g();
``` | «ba» Пояснение: TB::f insteadof TA makes f return B, and TA::f as g makes g return A.
Raw{ ⏎ "answer": "BA", ⏎ "explanation": "TB::f insteadof TA makes f return B, and TA::f as g makes g return A." ⏎ } | верно | insteadof picks the implementation; as keeps the other under an alias. |
T07-L10 19.78 c | Interfaces, traits, enum | What does this code output?
```php
trait Counter
{
public static int $n = 0;
}
class CX { use Counter; }
class CY { use Counter; }
CX::$n = 1;
echo CY::$n;
``` | «0» Пояснение: Each class using a trait has its own static property, so CY::$n remains 0.
Raw{"answer": 0, "explanation": "Each class using a trait has its own static property, so CY::$n remains 0."} | верно | A trait's static property is copied into each consuming class. |
T08-L10 17.36 c | Exceptions and errors | What does this code output?
```php
function f(): int
{
try { return 1; } finally { return 2; }
}
echo f();
``` | «2» Пояснение: A return statement in a finally block overrides the return value from the try block.
Raw{ ⏎ "answer": 2, ⏎ "explanation": "A return statement in a finally block overrides the return value from the try block." ⏎ } | верно | A return in finally overrides the return from try. |
T08-L9 16.99 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 replaces the original exception and is caught by the outer catch block.
Raw{"answer": "second", "explanation": "The LogicException thrown in the finally block replaces the original exception and is caught by the outer catch block."} | верно | An exception from finally replaces the in-flight one — the last thrown is caught. |
T09-L9 48.99 c | Namespaces and autoloading | What does this code output?
```php
namespace N;
use App\Foo as Baz;
echo Baz::class . '|' . \Baz::class;
``` | «app\foo|baz» Пояснение: Baz::class resolves to the imported App\Foo, while \Baz::class refers to the global class name Baz.
Raw{"answer":"App\\Foo|Baz","explanation":"Baz::class resolves to the imported App\\Foo, while \\Baz::class refers to the global class name Baz."} | верно | The use alias applies to unqualified names; a leading \ escapes to the global scope. |
T09-L10 43.25 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');
``` | «yesyes» Пояснение: class_exists('Foo') checks in the current namespace, and the fully qualified check also succeeds.
Raw{"answer":"yesyes","explanation":"class_exists('Foo') checks in the current namespace, and the fully qualified check also succeeds."} | неверно верный: «noyes» | Dynamic names are not resolved against the namespace — 'Foo' is the global class. |
T10-L9 60.42 c | References and scope | What does this code output?
```php
$a = [1, 2, 3];
foreach ($a as &$v) {}
$v = 99;
echo implode(',', $a);
``` | «1,2,99» Пояснение: The by-reference foreach leaves $v referencing the last array element, so assigning to it modifies $a.
Raw{"answer":"1,2,99","explanation":"The by-reference foreach leaves $v referencing the last array element, so assigning to it modifies $a."} | верно | After a by-ref foreach, $v remains a reference to the last element. |
T10-L10 27.68 c | References and scope | What does this code output?
```php
class A
{
public function inc(): int
{
static $n = 0;
return ++$n;
}
}
class B extends A {}
$a = new A;
$b = new B;
$a->inc();
$b->inc();
echo $a->inc();
``` | «3» Пояснение: The static variable $n is per-class (belongs to class A) and shared across all calls to inc(), so after three increments it reaches 3.
Raw{"answer": 3, "explanation": "The static variable $n is per-class (belongs to class A) and shared across all calls to inc(), so after three increments it reaches 3."} | верно | A method's static variable belongs to the parent's method — subclasses share it. |
T11-L9 24.36 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();
``` | «null» Пояснение: The first send() on an unstarted generator ignores the value and runs up to the first yield, leaving the generator suspended; getReturn() returns null because the generator hasn't finished.
Raw{"answer": "null", "explanation": "The first send() on an unstarted generator ignores the value and runs up to the first yield, leaving the generator suspended; getReturn() returns null because the generator hasn't finished."} | неверно верный: «11» | send() resumes the generator: $x = 10, return 10+1. |
T11-L10 35.53 c | Generators, iterators, SPL | What does this code output?
```php
function inner(): Generator
{
yield 1;
yield 2;
return 'ok';
}
function outer(): Generator
{
$r = yield from inner();
yield $r;
}
echo implode(',', iterator_to_array(outer()));
``` | «1,2,ok» Пояснение: yield from propagates inner's yields 1 and 2, then assigns inner's return value 'ok' to $r, which outer then yields.
Raw{"answer": "1,2,ok", "explanation": "yield from propagates inner's yields 1 and 2, then assigns inner's return value 'ok' to $r, which outer then yields."} | неверно верный: «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 2.43 c | Configuration and security | What does this code output?
```php
$hash = password_hash('x', PASSWORD_BCRYPT, ['cost' => 4]);
echo password_needs_rehash($hash, PASSWORD_BCRYPT, ['cost' => 4]) ? 'yes' : 'no';
echo password_needs_rehash($hash, PASSWORD_BCRYPT, ['cost' => 5]) ? 'yes' : 'no';
``` | «noyes» Пояснение: The hash was created with cost 4, so no rehash is needed for cost 4 (no), but a rehash to cost 5 is needed since it's a higher cost (yes).
Raw{"answer": "noyes", "explanation": "The hash was created with cost 4, so no rehash is needed for cost 4 (no), but a rehash to cost 5 is needed since it's a higher cost (yes)."} | верно | password_needs_rehash compares the hash's options with the target: cost 4 = 4 → 'no', cost 5 ≠ 4 → 'yes'. |
T12-L10 186.08 c | Configuration and security | What does this code output on PHP 8.5?
```php
echo (E_ALL & 2048) === 0 ? 'strict-out' : 'strict-in';
``` | «strict-out» Пояснение: In PHP 8.5, the strict-error bit 2048 (E_STRICT) is no longer included in E_ALL, so the bitwise AND is 0.
Raw{"answer":"strict-out","explanation":"In PHP 8.5, the strict-error bit 2048 (E_STRICT) is no longer included in E_ALL, so the bitwise AND is 0."} | верно | 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 48.26 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';
``` | «missing» Пояснение: The 6th positional argument to Request::create is $cookies, not $headers, so X-Token is not set on $r->headers.
Raw{"answer":"missing","explanation":"The 6th positional argument to Request::create is $cookies, not $headers, so X-Token is not set on $r->headers."} | неверно верный: «mapped» | The literal comparison requires knowing the mapping: HttpFoundation turns HTTP_X_TOKEN into the X-Token header (case-insensitive); without it the answer is 'missing'. |
T13-L10 2.68 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» Пояснение: Listeners are executed by priority descending, so the default-priority listener A runs first, then B with priority 10, then C with priority 5.
Raw{ ⏎ "answer": "ABC", ⏎ "explanation": "Listeners are executed by priority descending, so the default-priority listener A runs first, then B with priority 10, then C with priority 5." ⏎ } | неверно верный: «bca» | Listeners run by descending priority: 10 (B), 5 (C), 0 (A). |
T14-L10 19.62 c | Doctrine | Given: Doctrine ORM 3, an EntityManager on in-memory SQLite, entity User with an auto-increment primary key. The users table is empty. What does this code output?
```php
$u = new User(name: 'A');
$em->persist($u);
$em->flush();
$a = $em->find(User::class, $u->getId());
$b = $em->find(User::class, $u->getId());
echo spl_object_id($a) === spl_object_id($b) ? 'same' : 'diff';
``` | «same» Пояснение: Doctrine's EntityManager keeps a persistence-context identity map, so both find() calls for the same id return the same object instance.
Raw{"answer":"same","explanation":"Doctrine's EntityManager keeps a persistence-context identity map, so both find() calls for the same id return the same object instance."} | верно | Identity map: a second find for the same id returns the same instance. |
T14-L9 50.15 c | Doctrine | Given: Doctrine ORM 3, an EntityManager on in-memory SQLite, entity User with an auto-increment primary key. The users table is empty. What does this code output?
```php
$u = new User(name: 'B');
$em->persist($u);
$em->remove($u);
$em->flush();
echo count($em->getConnection()->fetchAllAssociative('SELECT * FROM users'));
``` | «0» Пояснение: Removing the newly persisted entity before flush cancels the pending insert, so the users table remains empty.
Raw{"answer": 0, "explanation": "Removing the newly persisted entity before flush cancels the pending insert, so the users table remains empty."} | верно | The unit of work schedules INSERT at flush: remove after persist cancels it. |
T15-L10 1.06 c | PostgreSQL | What does this SQL query return (PostgreSQL 17)?
```sql
CREATE TEMP TABLE t (x int);
INSERT INTO t VALUES (1), (NULL);
SELECT count(x) FROM t;
``` | «1»
Raw1 | верно парсинг: текст (фолбэк) | count(column) skips NULLs; count(*) would return 2. |
T15-L9 1.92 c | PostgreSQL | What does this SQL query return (PostgreSQL 17)?
```sql
CREATE TEMP TABLE t (id int, x int);
INSERT INTO t VALUES (1, 10), (2, 20), (3, 30);
SELECT string_agg(s::text, ',' ORDER BY id) FROM (
SELECT id, sum(x) OVER (ORDER BY id) AS s FROM t
) q;
``` | «10,30,60» Пояснение: The window sum produces cumulative totals 10, 30, and 60, which string_agg joins into a single comma-separated string.
Raw{"answer": "10,30,60", "explanation": "The window sum produces cumulative totals 10, 30, and 60, which string_agg joins into a single comma-separated string."} | верно | With ORDER BY the default window frame is running (start to current row). |
T16-L9 16.73 c | Symfony: Messenger | What does this code output?
```php
use Symfony\Component\Messenger\MessageBus;
use Symfony\Component\Messenger\Middleware\MiddlewareInterface;
use Symfony\Component\Messenger\Middleware\StackInterface;
use Symfony\Component\Messenger\Envelope;
final class Trace implements MiddlewareInterface
{
public function __construct(private string $tag) {}
public function handle(Envelope $e, StackInterface $stack): Envelope
{
echo $this->tag;
return $stack->next()->handle($e, $stack);
}
}
$bus = new MessageBus([new Trace('M1'), new Trace('M2')]);
$bus->dispatch(new Envelope(new stdClass()));
``` | «m1m2» Пояснение: Each Trace middleware echoes its tag before calling next, so M1 executes first and then M2.
Raw{"answer":"M1M2","explanation":"Each Trace middleware echoes its tag before calling next, so M1 executes first and then M2."} | верно | The first-added middleware runs first (outermost). |
T16-L10 133.04 c | Symfony: Messenger | What does this code output?
```php
use Symfony\Component\Messenger\MessageBus;
use Symfony\Component\Messenger\Middleware\HandleMessageMiddleware;
use Symfony\Component\Messenger\Handler\HandlersLocator;
use Symfony\Component\Messenger\Handler\HandlerDescriptor;
use Symfony\Component\Messenger\Envelope;
class Ping {}
$n = 0;
$d1 = new HandlerDescriptor(function (Ping $m) use (&$n) { $n += 1; }, ['alias' => 'h1']);
$d2 = new HandlerDescriptor(function (Ping $m) use (&$n) { $n += 10; }, ['alias' => 'h2']);
$bus = new MessageBus([
new HandleMessageMiddleware(new HandlersLocator([Ping::class => [$d1, $d2]])),
]);
$bus->dispatch(new Envelope(new Ping()));
echo $n;
``` | «11» Пояснение: HandleMessageMiddleware invokes both handlers for Ping, incrementing $n by 1 and then by 10.
Raw{"answer": 11, "explanation": "HandleMessageMiddleware invokes both handlers for Ping, incrementing $n by 1 and then by 10."} | верно | All registered handlers of the message run: 1 + 10 = 11. |
T17-L9 1.37 c | PostgreSQL: transactions and indexes | What does this SQL query return (PostgreSQL 17)?
```sql
CREATE TEMP TABLE t (a int);
CREATE UNIQUE INDEX ON t (a);
INSERT INTO t VALUES (1) ON CONFLICT DO NOTHING;
INSERT INTO t VALUES (1) ON CONFLICT DO NOTHING;
SELECT count(*) FROM t;
``` | «1» Пояснение: The unique index prevents duplicate values, so both ON CONFLICT DO NOTHING statements insert nothing on conflict, leaving one row.
Raw{ ⏎ "answer": 1, ⏎ "explanation": "The unique index prevents duplicate values, so both ON CONFLICT DO NOTHING statements insert nothing on conflict, leaving one row." ⏎ } | верно | ON CONFLICT DO NOTHING skips the duplicate: one insert. |
T17-L10 2.22 c | PostgreSQL: transactions and indexes | What does this sequence of psql commands output?
```sql
BEGIN;
CREATE TEMP TABLE t (a int, UNIQUE (a) DEFERRABLE INITIALLY DEFERRED);
INSERT INTO t VALUES (1);
INSERT INTO t VALUES (1);
SELECT count(*) FROM t;
``` | «2» Пояснение: The deferred uniqueness constraint allows both duplicate inserts until the transaction is committed, so SELECT count(*) returns 2.
Raw{ ⏎ "answer": 2, ⏎ "explanation": "The deferred uniqueness constraint allows both duplicate inserts until the transaction is committed, so SELECT count(*) returns 2." ⏎ } | верно | DEFERRED postpones the uniqueness check to COMMIT — count sees 2 rows. |
T18-L9 39.58 c | Testing: PHPUnit | How many tests will this command run?
```php
use PHPUnit\Framework\TestCase;
use PHPUnit\Framework\Attributes\DataProvider;
final class CalcTest extends TestCase
{
public static function prov(): array
{
return [[1], [2], [3]];
}
#[DataProvider('prov')]
public function test_sum(int $x): void
{
$this->assertTrue($x > 0);
}
#[DataProvider('prov')]
public function test_sum_abs(int $x): void
{
$this->assertTrue($x > 0);
}
public function test_other(): void
{
$this->assertTrue(true);
}
}
```
Command: `phpunit CalcTest.php --filter test_sum` (PHPUnit 10.5) | «6» Пояснение: The unanchored filter regex matches both test_sum and test_sum_abs, and each has three DataProvider datasets.
Raw{ ⏎ "answer": 6, ⏎ "explanation": "The unanchored filter regex matches both test_sum and test_sum_abs, and each has three DataProvider datasets." ⏎ } | верно | --filter is a substring match: test_sum also matches test_sum_abs (3+3 datasets). |
T18-L10 4.74 c | Testing: PHPUnit | How many tests will this command run, and how many of them will fail? Answer with two comma-separated numbers (ran, failed).
```php
use PHPUnit\Framework\TestCase;
use PHPUnit\Framework\Attributes\DataProvider;
final class Calc2Test extends TestCase
{
public function prov(): array
{
return [[1], [-1]];
}
#[DataProvider('prov')]
public function test_x(int $x): void
{
$this->assertTrue($x > 0);
}
}
```
Command: `phpunit Calc2Test.php` (PHPUnit 10.5) | «2,1» Пояснение: The data provider yields two datasets (1 and -1), so two tests run and only the second fails.
Raw{ ⏎ "answer": "2,1", ⏎ "explanation": "The data provider yields two datasets (1 and -1), so two tests run and only the second fails." ⏎ } | верно | A non-static provider is just a deprecation in PHPUnit 10: both datasets run and the [-1] dataset fails the assert — 2 ran, 1 failure. |
T19-L9 1.03 c | HTTP and REST API | Which HTTP method does this command send?
```bash
curl -s -d 'a=1' http://demo.local/api
``` | «post» Пояснение: curl's -d flag sends data in the request body, which defaults to the POST method.
Raw{"answer": "POST", "explanation": "curl's -d flag sends data in the request body, which defaults to the POST method."} | верно | -d/-F switches curl to POST by default. |
T19-L10 1.02 c | HTTP and REST API | Which HTTP method does this command send?
```bash
curl -s -G -d 'a=1' http://demo.local/api
``` | «get» Пояснение: The -G option tells curl to use GET instead of POST for the data sent with -d.
Raw{"answer": "GET", "explanation": "The -G option tells curl to use GET instead of POST for the data sent with -d."} | верно | -G turns -d data into the query string; the method stays GET. |
T20-L9 6.13 c | Security and OAuth | A client hits the token endpoint (RFC 6749) with a non-existent client_id. What value of the error field does the endpoint return? | «invalid_client» Пояснение: RFC 6749 returns invalid_client when the client identifier is unknown or the client cannot be authenticated.
Raw{ ⏎ "answer": "invalid_client", ⏎ "explanation": "RFC 6749 returns invalid_client when the client identifier is unknown or the client cannot be authenticated." ⏎ } | верно | Unknown client → invalid_client (RFC 6749 §5.2). |
T20-L10 1.3 c | Security and OAuth | OAuth 2.0: the client started the flow with response_type=token. In which part of the redirect_uri does the authorization server pass the access_token? | «fragment» Пояснение: With response_type=token (implicit grant), the authorization server returns the access token in the fragment portion of the redirect URI.
Raw{ ⏎ "answer": "fragment", ⏎ "explanation": "With response_type=token (implicit grant), the authorization server returns the access token in the fragment portion of the redirect URI." ⏎ } | верно | The implicit flow passes the token in the URL fragment (#) — it never reaches the server. |
T21-L9 1.67 c | Twig | What does this Twig template output?
```twig
{{ false|default(2) * 3 }}
``` | «6» Пояснение: Twig's default filter treats false as undefined, so false|default(2) evaluates to 2, and 2 * 3 is 6.
Raw{"answer": 6, "explanation": "Twig's default filter treats false as undefined, so false|default(2) evaluates to 2, and 2 * 3 is 6."} | верно | default replaces exactly false/null/''/[] — false becomes 2, 2*3 = 6; the naive 'default is for undefined only' yields 0. |
T21-L10 280.75 c | Twig | What exception class does render() of this template throw?
```twig
{{ 'a' ~ 1 + 2 }}
``` | «— (нет ответа)» | не разобрано верный: «runtimeerror» парсинг: нет | In Twig ~ binds tighter than +: ('a' ~ 1) + 2 → string + int → a render error (RuntimeError). |
T22-L9 48.53 c | Symfony: Security and forms | What does this code output?
```php
use Symfony\Component\Validator\Validation;
use Symfony\Component\Validator\Constraints as Assert;
$v = Validation::createValidator();
echo count($v->validate([''], [new Assert\NotBlank()]));
``` | «1» Пояснение: The array element '' violates the NotBlank constraint, so the validator returns one violation.
Raw{ ⏎ "answer": 1, ⏎ "explanation": "The array element '' violates the NotBlank constraint, so the validator returns one violation." ⏎ } | неверно верный: «0» | NotBlank treats null, '', [] as blank — the array [''] is not blank. |
T22-L10 208.2 c | Symfony: Security and forms | What does this code output?
```php
use Symfony\Component\Form\Forms;
use Symfony\Component\Form\Extension\Core\Type\TextType;
$factory = Forms::createFormFactoryBuilder()->getFormFactory();
$form = $factory->create(TextType::class);
try {
echo $form->isValid() ? 'valid' : 'invalid';
} catch (Throwable $e) {
echo get_class($e);
}
``` | «invalid» Пояснение: A newly created TextType form is required by default, so an empty form is invalid.
Raw{"answer": "invalid", "explanation": "A newly created TextType form is required by default, so an empty form is invalid."} | неверно верный: «symfony\component\form\exception\logicexception» | isValid() on a non-submitted form throws LogicException, it does not return false. |
T23-L9 6.43 c | Symfony: configuration and services | What does this code output?
```php
use Symfony\Component\DependencyInjection\ContainerBuilder;
$c = new ContainerBuilder();
$c->register('a', stdClass::class)->setPublic(true);
$c->compile();
echo spl_object_id($c->get('a')) === spl_object_id($c->get('a')) ? 'same' : 'diff';
``` | «same» Пояснение: Symfony DI services are shared/singletons by default, so both get('a') calls return the same instance.
Raw{"answer":"same","explanation":"Symfony DI services are shared/singletons by default, so both get('a') calls return the same instance."} | верно | Container services are shared: two get() calls yield one instance. |
T23-L10 280.56 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!» парсинг: нет | compile() resolves %-references transitively: %greeting% → 'hi %name%' → 'hi Bob!', the answer assembles over two hops. |
T24-L9 2.53 c | Bootstrap | What is the max-width of .container in Bootstrap 5.3 at a 992px viewport? | «992» Пояснение: In Bootstrap 5.3, the .container class uses a max-width of 992px at the 'lg' breakpoint, which applies from 992px up to 1399.98px.
Raw{"answer": "992", "explanation": "In Bootstrap 5.3, the .container class uses a max-width of 992px at the 'lg' breakpoint, which applies from 992px up to 1399.98px."} | неверно верный: «960» | 5.x container widths: 540/720/960/1140/1320 (sm–xxl); 992 → 960px. |
T24-L10 74.21 c | Bootstrap | Which utility sets the text color in Bootstrap 5.3 for `<p class="text-danger text-primary">…</p>`? Answer with the winning class name. | «text-danger» Пояснение: Both utilities have the same specificity, and in Bootstrap 5.3 the .text-danger rule is defined after .text-primary, so it wins.
Raw{"answer":"text-danger","explanation":"Both utilities have the same specificity, and in Bootstrap 5.3 the .text-danger rule is defined after .text-primary, so it wins."} | верно | Specificity ties — the later rule wins: text-danger is declared after text-primary. |
T25-L9 8.0 c | Clean architecture | Layers: Domain, Application, Infrastructure. Deptrac rules: Application → Domain; Infrastructure → Domain, Application; Domain → Domain only.
How many violations will deptrac report for this class?
```php
namespace App\Domain;
use App\Application\PlaceOrder;
use App\Infrastructure\Db;
class OrderService
{
public function __construct(
private PlaceOrder $handler,
private Db $db,
) {}
}
``` | «2» Пояснение: The Domain-class depends on one Application class and one Infrastructure class, and Domain is allowed to depend only on Domain.
Raw{ ⏎ "answer": 2, ⏎ "explanation": "The Domain-class depends on one Application class and one Infrastructure class, and Domain is allowed to depend only on Domain." ⏎ } | верно | Domain may depend only on Domain: PlaceOrder (Application) + Db (Infrastructure) = 2. |
T25-L10 11.29 c | Clean architecture | Layers: Domain, Application, Infrastructure. Deptrac rules: Application → Domain; Infrastructure → Domain, Application; Domain → Domain only.
How many violations will deptrac report for this class?
```php
namespace App\Domain;
use App\Application\PlaceOrder;
use App\Infrastructure\Db;
class BillingService
{
public function __construct(
private PlaceOrder $handler,
private Db $db,
private \App\Infrastructure\Logger $logger,
) {}
}
``` | «3» Пояснение: The Domain class depends on one Application class and two Infrastructure classes, and the rule allows Domain to depend only on Domain.
Raw{ ⏎ "answer": 3, ⏎ "explanation": "The Domain class depends on one Application class and two Infrastructure classes, and the rule allows Domain to depend only on Domain." ⏎ } | верно | The inline FQCN \App\Infrastructure\Logger counts too: Application + Db + Logger = 3. |
T26-L10 1.71 c | DDD | What does this code output?
```php
final class Money
{
public function __construct(public readonly int $amount) {}
public function add(Money $o): Money
{
return new self($this->amount + $o->amount);
}
}
$a = new Money(10);
$c = $a->add(new Money(5));
echo $a->amount . ',' . $c->amount;
``` | «10,15» Пояснение: The readonly amount property is never mutated, so $a remains 10 and $c is a new Money object with amount 15.
Raw{ ⏎ "answer": "10,15", ⏎ "explanation": "The readonly amount property is never mutated, so $a remains 10 and $c is a new Money object with amount 15." ⏎ } | верно | The VO is immutable: add() returns a new instance; the original is unchanged. |
T26-L9 1.63 c | DDD | What does this code output?
```php
final class Order
{
private array $items = [];
public function add(string $sku): void
{
$this->items[$sku] = true;
}
public function count(): int
{
return count($this->items);
}
public function remove(string $sku): void
{
if (count($this->items) === 1) {
throw new DomainException('last item');
}
unset($this->items[$sku]);
}
}
$o = new Order;
$o->add('a');
try {
$o->remove('a');
} catch (DomainException) {
}
echo $o->count();
``` | «1» Пояснение: The remove method throws an exception because there is only one item, so the item is never removed.
Raw{"answer": 1, "explanation": "The remove method throws an exception because there is only one item, so the item is never removed."} | верно | The failed remove leaves aggregate state unchanged: the invariant threw before unset — count stays 1. |
VC-L9 1.28 c | PHP 8.4–8.5 | What does this code output on PHP 8.5?
```php
class C
{
public function hi(): string { return 'hi'; }
}
echo new C()->hi();
``` | «hi» Пояснение: The object is created, its hi() method returns the string 'hi', and echo prints it.
Raw{ ⏎ "answer": "hi", ⏎ "explanation": "The object is created, its hi() method returns the string 'hi', and echo prints it." ⏎ } | верно | Since 8.4, new in a method chain works without wrapping parentheses. |
VC-L10 24.92 c | PHP 8.4–8.5 | What does this code output on PHP 8.5?
```php
class Heavy
{
public int $v = 0;
}
$r = new ReflectionClass(Heavy::class);
$o = $r->newLazyGhost(function (Heavy $obj) {
$obj->v = 21;
});
echo $r->isUninitializedLazyObject($o) ? 'yes' : 'no';
$o->v;
echo $r->isUninitializedLazyObject($o) ? 'yes' : 'no';
``` | «yesno» Пояснение: The lazy ghost is uninitialized before reading $v; accessing $v initializes it, so the second check is false.
Raw{"answer":"yesno","explanation":"The lazy ghost is uninitialized before reading $v; accessing $v initializes it, so the second check is false."} | верно | newLazyGhost (8.4): the object stays lazy until first access — reading a property initializes it and clears the flag. |
T28-L9 3.73 c | Symfony: versions | The project was upgraded from Symfony 6.4 to 8.1. What does this code output on 8.1?
```php
echo class_exists(\Symfony\Component\Security\Guard\AbstractGuardAuthenticator::class)
? 'yes' : 'no';
``` | «no» Пояснение: AbstractGuardAuthenticator was removed long before Symfony 8.1, so class_exists returns false.
Raw{"answer": "no", "explanation": "AbstractGuardAuthenticator was removed long before Symfony 8.1, so class_exists returns false."} | верно | Guard authentication was removed in Symfony 7.0 — the class is gone in 8.1. |
T28-L10 197.58 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';
``` | «no no» Пояснение: Both legacy routing loader classes were removed in Symfony 8.0, so both `class_exists` checks are false.
Raw{"answer":"no no","explanation":"Both legacy routing loader classes were removed in Symfony 8.0, so both `class_exists` checks are false."} | неверно верный: «noyes» | Annotation loaders were removed in 7.0; only attribute loaders remain (Annotation→Attribute). |