LPI 300-300 Practice Test Questions, Exam Dumps

Practice Exams:

View All

300-300 LPI Practice Test Questions and Exam Dumps

Question No 1:

Which of the following statements is true about raw printing with Samba?

A. Print jobs are submitted as vector files, including font files, which are rendered and printed by Samba.
B. Printing jobs are always submitted to Samba in raw postscript.
C. Any printed file, e.g. an office document, is submitted to the printer without any further processing in exactly the same bit sequence as it is stored on disk.
D. Samba converts printer-specific jobs to raw data to make them printable on an arbitrary printer.
E. Printing jobs are rendered on the client and passed on to the printer by Samba.

Correct Answer: C

Explanation:

In raw printing with Samba, the print jobs are submitted to the printer exactly as they are stored on the disk without any modification or processing by Samba. This means that the data is transmitted to the printer in the same bit sequence as it is stored, whether it’s an image, office document, or other types of files. This approach is commonly used when you want the printer to handle all the formatting, rendering, and processing, instead of relying on Samba or the server to manipulate the print data.

Option A is incorrect because raw printing does not involve Samba rendering or processing vector files and fonts; this would be the case for standard printing where Samba would handle the conversion and rendering.

Option B is not correct because raw printing doesn't involve specific formats like PostScript; it simply passes the data in its raw form to the printer.

Option D is incorrect because Samba doesn't convert printer-specific jobs to raw data. It allows raw data to be sent as-is to the printer, without conversion.

Option E is incorrect because raw printing bypasses the rendering process on the client side and relies on the printer to handle all the job processing. Samba simply sends the data as-is.

Question No 2:

The configuration of a Samba share contains the following line: force directory mode = 0555. If a client creates a new directory with the permissions 0750, which permissions will the resulting directory have in the Samba server's file system?

A. 0755
B. 0750
C. 0200
D. 0555
E. 0777

Correct Answer: D

Explanation:

In Samba, the force directory mode setting is used to specify the permissions that should be applied to newly created directories on the server, regardless of the permissions set by the client creating the directory. In this case, the line force directory mode = 0555 specifies that any directory created in this share will have its permissions overridden to 0555.

Even though the client attempts to create a directory with 0750 permissions, the Samba configuration overrides this and forces the permissions to be set as 0555 on the server. The 0555 permissions indicate that the directory will be readable and executable by all users but not writable by anyone.

To summarize:

The client may attempt to create a directory with 0750 permissions.
However, due to the force directory mode = 0555 setting, Samba will modify the permissions to 0555 when the directory is actually created on the server's file system.

Therefore, the correct answer is D, as the resulting directory permissions will be 0555 due to the forced setting in the Samba configuration.

Question No 3:

Which of the following smb.conf options turns a regular file share into a DFS share?

A. msdfs root = yes
B. addfs support = yes
C. dfs forward = yes
D. follow symlinks = yes
E. proxy share = yes

Correct Answer: A

Explanation:

In Samba, the msdfs root option is used to configure Distributed File System (DFS) support. Setting this option to yes indicates that the share is a DFS root share. DFS allows multiple file servers to be logically grouped under a single namespace, enabling users to access shared resources across different servers as if they were in a single location. When msdfs root is set to yes in the smb.conf configuration file, it tells Samba to treat the shared resource as part of the DFS structure. This effectively turns the regular file share into a DFS share, which is essential for DFS to function properly.

Option B, addfs support, is not a valid Samba configuration option related to DFS. It seems to be a misstatement or confusion with another feature, but it does not turn a regular file share into a DFS share.

Option C, dfs forward, is not a valid Samba configuration option either. While there are settings for DFS in some systems, dfs forward is not part of the smb.conf file.

Option D, follow symlinks, is used to allow Samba to follow symbolic links within a shared directory. It does not have any effect on turning a share into a DFS share. It simply controls how symbolic links are treated during file access.

Option E, proxy share, is not a valid option in the smb.conf configuration file. Although there are concepts like proxying shares, proxy share is not a recognized directive in the Samba configuration.

Thus, the correct answer is A, msdfs root = yes, as it specifically enables DFS root functionality in Samba.

Question No 4:

Which parameter within a share definition in the Samba configuration makes Samba only show files and directories on a file share which a user can access?

A. hide unreadable = yes
B. valid files = read,write
C. browse mask = 000
D. browseable = readable
E. display mode = 100

Correct Answer: A

Explanation:

The hide unreadable = yes parameter in the Samba configuration ensures that only files and directories a user can access are displayed in the file share. When this option is enabled, Samba hides any files or directories that the user does not have permission to read. This helps provide a more secure and user-friendly experience by preventing unauthorized users from seeing files or directories they cannot access.

Let’s break down the other options:

B. valid files = read,write: This option does not exist in the Samba configuration. While you can define valid users or groups in Samba, this specific parameter does not control file visibility based on user permissions.
C. browse mask = 000: The browse mask controls the visibility of the share itself, not individual files or directories within the share. A browse mask of "000" would make the share invisible to users, but it doesn't impact file or directory visibility based on user permissions.
D. browseable = readable: The correct parameter for controlling whether a share is visible in a network browse list is browseable, but the term "readable" is not a valid option. The browseable parameter, when set to "no," makes the share not visible at all, regardless of file access permissions.
E. display mode = 100: This is not a valid Samba configuration option. It doesn’t control file visibility or permissions.

Therefore, the correct answer is A, as hide unreadable = yes makes Samba only show files and directories the user has permission to access.

Question No 5:

Which of the following lines is missing in the given [printers] share definition?

A. printcap name = cups
B. printable = yes
C. print script = /usr/bin/lp -d %P %s
D. print admin = Administrator, root, @lpadmin
E. load printers = yes

Correct Answer: B

Explanation:

In a typical Samba configuration, the [printers] share section is defined to manage print services. Among the provided options, the line that is often necessary to enable a printer share in the configuration is printable = yes. This directive tells Samba that the share is for a printer, enabling it to act as a print share rather than a file share.

Option A refers to the printcap name parameter, which points to the location of the printcap file, typically used to configure printers. While useful for some setups, it is not mandatory for a simple printer share definition.

Option C is a script that specifies the command for printing. This line would be necessary if you are defining a custom printing script, but it is not the most essential part of the configuration.

Option D refers to the print admin parameter, which defines who can administer the printer share. While it is useful for administrative control, it is not a required line to define a basic printer share.

Option E refers to load printers = yes, which ensures printers are automatically discovered. However, this setting is not directly part of the [printers] section. It is used more generally to specify whether the server should load printer definitions automatically.

Thus, the correct answer is B, as the printable = yes line is essential for defining a printer share.

Question No 6:

The [homes] section of smb.conf contains the parameter browseable = no. What are the resulting consequences? (Choose two.)

A. When browsing the Samba server, there is no visible share named after the current user.
B. If the Samba server is part of an Active Directory Domain, only users in the group SeBrowsingUsers can browse the homes share.
C. When browsing the Samba server, users can open the homes share but they cannot see the content of their home directories.
D. The homes share can be directly accessed by specifically opening this share by its UNC path.
E. When browsing the Samba server, there is no visible share called homes.

Correct answers: A, E

Explanation:

The parameter browseable = no in the [homes] section of smb.conf has specific consequences on how the Samba server shares are handled, particularly in relation to visibility and access by users.

A. When browsing the Samba server, there is no visible share named after the current user is correct. Setting browseable = no in the [homes] section means that users will not see a share named after their username when browsing the available shares. However, they can still access the share if they know the UNC path (Universal Naming Convention), which leads to the next consequence.

B. If the Samba server is part of an Active Directory Domain, only users in the group SeBrowsingUsers can browse the homes share is incorrect. The browseable = no setting does not relate to a specific user group like SeBrowsingUsers. The setting merely makes the share invisible when browsing the server, but it doesn’t restrict access based on group membership.

C. When browsing the Samba server, users can open the homes share but they cannot see the content of their home directories is incorrect. With browseable = no, the share itself is not visible when browsing the server, so users won’t be able to open it unless they access it via a specific path. This statement implies that the share is visible and accessible in some form, which is not the case when browsing.

D. The homes share can be directly accessed by specifically opening this share by its UNC path is correct. Despite setting browseable = no, users can still access their homes share directly by specifying the exact UNC path (e.g., \\server\homes\username), as the share itself is still available to those who know the path.

E. When browsing the Samba server, there is no visible share called homes is correct. This is a direct consequence of setting browseable = no. The homes share will not be displayed in the list of available shares when users browse the server through tools like smbclient or network browsing in Windows.

In conclusion, setting browseable = no hides the homes share from being displayed during browsing, but users can still access it directly via its path if they know it. This ensures a level of obscurity without denying access entirely.

Question No 7:

Which Samba utility, when launched with the appropriate parameters, generates the following output?

A. smbcacls
B. smbclient
C. getfacl
D. smbxattr
E. smbfacl

correct answer is A,

Explanation:

The smbcacls command (A) is used to manage and display the Access Control Lists (ACLs) of files and directories on a Samba share. When launched with the appropriate parameters, it provides information about the permissions set on the files and directories, including user-specific permissions.

smbclient (B) is a client tool used for accessing and interacting with SMB shares, but it is not designed specifically for ACLs and would not generate this kind of output.
getfacl (C) is used for viewing ACLs on Linux file systems but is not related to Samba specifically, so it would not produce this output for a Samba share.
smbxattr (D) is used for managing extended attributes on files in an SMB share and doesn't focus on ACLs.
smbfacl (E) is not a valid Samba command for managing ACLs.

Given the options, the correct answer is A, as smbcacls is the tool used for ACL management on Samba shares.

Question No 8:

Which two options can be used to limit access to a Samba share?

A. untrusted users
B. write list
C. valid groups
D. valid users
E. accept list

Answer: C, D

Explanation:

To control access to a Samba share, there are several directives that can be used to define who can access the shared resources. The correct options are valid groups and valid users because they specifically deal with controlling which users or groups are allowed access to a Samba share.

valid groups: This directive allows access only to members of specific groups. When used, Samba checks the group membership of users attempting to access the share and permits access only if they belong to the listed groups. This is a common way to limit access based on group membership.
valid users: Similar to valid groups, this directive restricts access to specified users. Only the users listed in this directive can access the share. This is particularly useful if you want to specify a group of users by username rather than group membership.

Now, let’s discuss the other options:

A. untrusted users: This is not a directive used to limit access. In fact, the term untrusted users refers to users who are considered outside the trusted domain or environment, but it's not a directive used for controlling access in Samba configuration files.
B. write list: This directive is used to specify which users or groups are allowed to write to the share. It does not limit general access to the share; it only defines who can write to it once access is granted.
E. accept list: This is not a valid directive in Samba for controlling access. While deny list exists in some configurations, accept list is not a recognized access control option for Samba shares.

In summary, the valid users and valid groups directives are used to specifically limit access to a Samba share by user or group, making them the correct options.

Question No 9:

In case the following parameters are set in a Samba file share configuration: create mask = 711 force create mode = 750

What are the effective permissions of a file created with the permissions 777?

A. 066
B. 027
C. 777
D. 761
E. 751

Correct answer: E

Explanation:

In this scenario, two parameters are set in the Samba configuration: create mask = 711 and force create mode = 750. To understand the effective permissions, we need to evaluate the impact of each setting.

create mask: This parameter determines the maximum permissions that can be granted to a newly created file. In this case, the value 711 specifies that the file can have permissions that allow full read, write, and execute access for the owner (7), and execute permissions for the group and others (1 for group and 1 for others). Therefore, the create mask ensures that no file can be created with more than 711 permissions.
force create mode: This parameter enforces a specific permission setting on all files created, regardless of what the user requests. In this case, the value 750 ensures that files will always have the permission set 750, which grants full read, write, and execute permissions to the owner (7), read and execute permissions to the group (5), and no permissions to others (0).

When a file is created with an initial permission of 777 (full permissions for all), the create mask and force create mode will both modify the permissions:

create mask = 711 means that the maximum permissions the file can have are 711 (rwx--x--x).
force create mode = 750 forces the file to have permissions of 750 (rwxr-x---) regardless of the requested permissions.

Given that force create mode takes precedence over the create mask, the effective permissions for the file will be 751, which is 750 permissions with the execute permission for others enforced by the create mask.

Thus, the final effective permissions are 751, as the execute permission for others is allowed by the create mask but restricted by the force create mode. Therefore, the correct answer is E.

Question No 10:

Which of the following are valid Samba backends to store user and group information? (Choose two.)

A. sdb
B. smbpasswd
C. ldapsam
D. krb
E. smb

Correct answer: B,C

Explanation:

Samba provides different backends to manage user and group information. These backends determine how Samba stores and retrieves data related to users and groups. Let's review the options to identify the valid backends.

A. sdb: This option is not a commonly used backend for storing user and group information in Samba. While it might refer to an LDAP backend for a different context, it's not a standard Samba user/group backend.
B. smbpasswd: This is a valid backend used in Samba. The smbpasswd backend stores user information in the /etc/smbpasswd file, which is a traditional method for handling authentication in earlier versions of Samba. This backend is still supported, though other backends have become more common.
C. ldapsam: This is another valid Samba backend. The ldapsam backend allows Samba to integrate with an LDAP directory for user and group management. It is commonly used in environments where LDAP is already in use for managing users and groups, such as in Active Directory or other LDAP-based systems.
D. krb: This is not a valid Samba backend for storing user and group information. krb is typically associated with Kerberos, a network authentication protocol, but it is not directly used as a backend for user/group storage in Samba.
E. smb: This is also not a valid backend for user and group information in Samba. While smb refers to the SMB/CIFS protocol itself, it is not a backend for storing data about users or groups.

In conclusion, the correct options for valid Samba backends are B (smbpasswd) and C (ldapsam), as these are commonly used and supported methods for storing user and group information.