The idea being tested is using a shared container to grant the same access to many people. A group account acts as a single identity that represents a set of user accounts; when permissions are given to that group account, every member of the group inherits those rights. This makes administration simpler because you manage access at the group level rather than configuring permissions for each individual user, and you can add or remove members to adjust who has the access. Other terms point to different ideas: permissions are the actual rights granted, not the container that holds multiple users; discretionary access control is a model where owners decide who can access resources; and RBAC is a system that assigns permissions to roles which are then assigned to users. The concept described—a single account representing multiple users to provide the same access—is best described as a group account.

Authorization determines what rights and privileges an entity has. It happens after authentication, when the system applies policies to decide what a user or process is allowed to do with resources. In practice, once identity is verified, the system checks roles, attributes, or rules (such as ACLs or RBAC) to grant or deny specific actions like read, write, or execute. This separation matters: authentication verifies who you are, identification is the claimed identity, and accounting logs what you did. For example, after logging in (authentication), a user’s role is consulted to determine if they can access a file or perform a change (authorization).

Remote Desktop Protocol relies on a dedicated TCP port by default, which is the one most commonly associated with and expected for RDP connections. That default port is what makes it the best answer here, because knowing this port helps you configure firewalls and access controls around RDP. The other ports correspond to different services you might see on a network—SSH for secure remote login, HTTP for web traffic, and HTTPS for secure web traffic—so they’re not the standard port used by RDP. While you can reconfigure RDP to listen on another port, using the default port is the common, recognized choice, and it’s important to secure it properly (for example, by restricting exposure to the internet and using VPN or a gateway).

Ownership as a factor in multifactor authentication means you must prove you possess something physical. A hardware device that generates a code or cryptographic response on demand is a hard authentication token—the classic physical token used to demonstrate you have the device. This token is produced by the device itself and changes over time or per event, which is exactly what shows possession of the hardware. Biometric authentication isn’t an ownership factor but a “something you are” factor. Smart cards are hardware credentials and can serve as possession devices, but the term that emphasizes the generated token from the hardware device is hard authentication token. A security key is a hardware credential as well, but the phrasing here centers on the token generated by the device, which aligns with the hard token concept.