Which of the following can be used to configure the scope of the Cookie visibility?

The scope of cookie visibility can be configured using the following attributes:

1. Domain Attribute: This specifies which hosts are allowed to receive the cookie. If specified, subdomains are included. For example, if you set the domain attribute to “example.com”, then cookies are available for “sub.example.com” as well.

2. Path Attribute: This restricts the cookie to a specified path on the domain. Only requests to this path will send the cookie. For instance, if the path is set to “/shop”, the cookie is only sent for requests that go to “example.com/shop” and its sub-paths.

3. Secure Attribute: When this attribute is set, the cookie will only be sent over secure connections, i.e., HTTPS. This helps to ensure that the cookie is not exposed through a less secure or unencrypted connection.

4. HttpOnly Attribute: This makes the cookie inaccessible to JavaScript’s `Document.cookie` API; it’s only sent to the server. This is a mitigation against cross-site scripting (XSS) attacks.

5. SameSite Attribute: This attribute controls whether a cookie is sent with cross-origin requests, providing some protection against cross-site request forgery attacks (CSRF). It has three options: `Strict`, `Lax`, and `None`. `Strict` means the cookie is only sent for same-site requests, `Lax` allows it for some cross-site usage (like links), and `None` specifies