Bird
Raised Fist0
PHPprogramming~10 mins

Interface vs abstract class vs trait in PHP - Interactive Practice

Choose your learning style10 modes available
Practice - 5 Tasks
Answer the questions below
1fill in blank
easy

Complete the code to declare an interface named Logger.

PHP
<?php
interface [1] {
    public function log(string $msg);
}
?>
Drag options to blanks, or click blank then click option'
ALogTrait
BLogger
CLogInterface
DAbstractLogger
Attempts:
3 left
💡 Hint
Common Mistakes
Using trait or abstract class names instead of interface name.
2fill in blank
medium

Complete the code to declare an abstract class named Vehicle.

PHP
<?php
abstract class [1] {
    abstract public function startEngine();
}
?>
Drag options to blanks, or click blank then click option'
ADrive
BCar
CVehicle
DEngine
Attempts:
3 left
💡 Hint
Common Mistakes
Using specific class names instead of a general abstract class name.
3fill in blank
hard

Fix the error in the trait declaration by completing the code.

PHP
<?php
trait [1] {
    public function sayHello() {
        echo "Hello!";
    }
}
?>
Drag options to blanks, or click blank then click option'
AGreetingTrait
BHelloInterface
CAbstractGreeting
DSayHelloClass
Attempts:
3 left
💡 Hint
Common Mistakes
Using interface or class names instead of trait name.
4fill in blank
hard

Fill both blanks to implement the Logger interface and use the GreetingTrait in the class.

PHP
<?php
class User implements [1] {
    use [2];
    public function log(string $msg) {
        echo $msg;
    }
}
?>
Drag options to blanks, or click blank then click option'
ALogger
BGreetingTrait
CLogTrait
DAbstractLogger
Attempts:
3 left
💡 Hint
Common Mistakes
Confusing trait names with interface names.
Using wrong keywords for implementation or usage.
5fill in blank
hard

Fill all three blanks to declare an abstract class with an abstract method and use a trait inside it.

PHP
<?php
abstract class [1] {
    use [2];
    abstract public function [3]();
}
?>
Drag options to blanks, or click blank then click option'
AVehicle
BGreetingTrait
CstartEngine
DLogger
Attempts:
3 left
💡 Hint
Common Mistakes
Using interface names instead of class names.
Confusing method names with trait or class names.

Practice

(1/5)
1. Which of the following best describes a PHP interface?
easy
A. It is used to create objects directly without classes.
B. It allows code reuse by including methods directly into classes.
C. It can contain both implemented and abstract methods to share common behavior.
D. It defines method signatures without implementation, forcing classes to implement them.

Solution

  1. Step 1: Understand what an interface is in PHP

    An interface only declares method names without any code, so classes must implement all methods.
  2. Step 2: Compare with traits and abstract classes

    Traits provide reusable code, and abstract classes can have both code and abstract methods, unlike interfaces.
  3. Final Answer:

    It defines method signatures without implementation, forcing classes to implement them. -> Option D
  4. Quick Check:

    Interface = method signatures only [OK]
Hint: Interfaces only declare methods, no code inside [OK]
Common Mistakes:
  • Thinking interfaces can have method bodies
  • Confusing traits with interfaces
  • Believing interfaces can be instantiated
2. Which of the following is the correct syntax to declare a trait in PHP?
easy
A. abstract trait Logger {}
B. interface Logger {}
C. trait Logger {}
D. class Logger {}

Solution

  1. Step 1: Recall PHP syntax for traits

    Traits are declared using the keyword trait followed by the trait name and curly braces.
  2. Step 2: Eliminate incorrect options

    abstract trait Logger {} is invalid because traits cannot be abstract. interface Logger {} declares an interface, and class Logger {} declares a class.
  3. Final Answer:

    trait Logger {} -> Option C
  4. Quick Check:

    Trait declaration uses 'trait' keyword [OK]
Hint: Traits start with 'trait' keyword, no 'abstract' needed [OK]
Common Mistakes:
  • Adding 'abstract' before trait keyword
  • Confusing trait with interface or class syntax
  • Using 'class' keyword for traits
3. What will be the output of the following PHP code?
trait Hello {
    public function sayHello() {
        return "Hello from trait!";
    }
}

abstract class Base {
    abstract public function sayHello();
}

class MyClass extends Base {
    use Hello;
}

$obj = new MyClass();
echo $obj->sayHello();
medium
A. Hello from trait!
B. Fatal error: Class MyClass contains 1 abstract method
C. Hello from Base
D. Syntax error

Solution

  1. Step 1: Understand trait usage in class extending abstract

    The trait Hello provides the method sayHello(). The abstract class Base declares sayHello() as abstract.
  2. Step 2: Check if MyClass implements abstract method

    MyClass uses the trait which provides the required method, so no error occurs and the method returns the trait's string.
  3. Final Answer:

    Hello from trait! -> Option A
  4. Quick Check:

    Trait method satisfies abstract method [OK]
Hint: Trait methods fulfill abstract methods if used [OK]
Common Mistakes:
  • Expecting fatal error for missing method
  • Confusing trait method with abstract class method
  • Thinking abstract method must be implemented in class only
4. Identify the error in the following PHP code:
interface Logger {
    public function log(string $msg);
}

trait Logger {
    public function log(string $msg) {
        echo $msg;
    }
}

class FileLogger implements Logger {
    use Logger;
}
medium
A. Trait and interface cannot have the same name.
B. Class cannot implement interface and use trait simultaneously.
C. Trait methods cannot have parameters.
D. Interface methods must have implementation.

Solution

  1. Step 1: Check naming conflicts

    Both the interface and trait are named Logger, which causes a fatal error due to name collision.
  2. Step 2: Verify other rules

    Classes can implement interfaces and use traits simultaneously. Traits can have parameters in methods. Interface methods cannot have implementation.
  3. Final Answer:

    Trait and interface cannot have the same name. -> Option A
  4. Quick Check:

    Name collision between trait and interface [OK]
Hint: Trait and interface names must differ [OK]
Common Mistakes:
  • Thinking class can't use trait and implement interface
  • Believing traits can't have parameters
  • Assuming interface methods have code
5. You want to create a PHP class that must implement a method connect() defined by an interface, share common code for disconnect() from an abstract class, and reuse logging code from a trait. Which is the best way to design this?
hard
A. Create an interface with connect() and disconnect(), a trait with logging, and a class that extends the interface and uses the trait.
B. Create an interface with connect(), an abstract class with disconnect(), a trait with logging, then a class that implements the interface, extends the abstract class, and uses the trait.
C. Create an abstract class with connect() and disconnect(), a trait with logging, and a class that implements the trait and extends the interface.
D. Create a trait with connect() and disconnect(), an abstract class with logging, and a class that extends the trait and implements the abstract class.

Solution

  1. Step 1: Understand roles of interface, abstract class, and trait

    Interface defines required methods like connect(). Abstract class can provide shared code like disconnect(). Trait is for reusable code like logging.
  2. Step 2: Combine them correctly in a class

    PHP allows a class to implement interfaces, extend one abstract class, and use multiple traits. So the class should implement the interface, extend the abstract class, and use the trait.
  3. Final Answer:

    Create an interface with connect(), an abstract class with disconnect(), a trait with logging, then a class that implements the interface, extends the abstract class, and uses the trait. -> Option B
  4. Quick Check:

    Interface + abstract class + trait combined properly [OK]
Hint: Interface for methods, abstract class for code, trait for reuse [OK]
Common Mistakes:
  • Trying to extend multiple classes
  • Confusing trait and abstract class roles
  • Extending interface instead of implementing
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard