{"id":18628,"date":"2026-09-22T08:55:48","date_gmt":"2026-09-22T08:55:48","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=18628"},"modified":"2026-09-22T08:55:48","modified_gmt":"2026-09-22T08:55:48","slug":"lpi-101-500-practice-test-questions-and-exam-dumps-part-12-q221-240","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/lpi-101-500-practice-test-questions-and-exam-dumps-part-12-q221-240\/","title":{"rendered":"LPI 101-500 Practice Test Questions and Exam Dumps Part 12 Q221-240"},"content":{"rendered":"

View Full<\/b> LPI 101-500<\/b> Exam Dumps<\/b><\/a> and Practice Test Dumps<\/b><\/p>\n

 <\/p>\n

Question: 221. Which file commonly lists the shells that are recognized as valid login shells on a Linux system?<\/b><\/p>\n

    \n
  1. <\/b> \/etc\/profile<\/span>
    \n<\/span>2.<\/b> \/etc\/bashrc<\/span>
    \n<\/span>3.<\/b> \/etc\/shells<\/span>
    \n<\/span>4.<\/b> \/etc\/login.conf<\/span><\/li>\n<\/ol>\n

    Correct Answer: 3. <\/b>\/etc\/shells<\/b><\/p>\n

    Explanation:<\/b><\/p>\n

    The <\/span>\/etc\/shells<\/span> file contains a list of valid login shells available on the system. Programs can consult this file when determining whether a particular shell is permitted as a user’s login shell. Common entries may include paths such as <\/span>\/bin\/bash<\/span>, <\/span>\/bin\/sh<\/span>, or other installed shells. It is different from <\/span>\/etc\/passwd<\/span>, which stores each user’s configured login shell as part of the account information. <\/span>\/etc\/profile<\/span> is instead a shell startup configuration file used by login shells. Understanding <\/span>\/etc\/shells<\/span> is important when working with user accounts and shell configuration on Linux systems.<\/span><\/p>\n

    Question: 222. What is the primary purpose of <\/b>\/etc\/nologin<\/b> when it exists on a Linux system?<\/b><\/p>\n

      \n
    1. <\/b> It prevents ordinary users from logging in while allowing appropriate administrative access<\/span>
      \n<\/span>2.<\/b> It permanently deletes all user accounts<\/span>
      \n<\/span>3.<\/b> It disables networking during system startup<\/span>
      \n<\/span>4.<\/b> It changes the default command shell for every user<\/span><\/li>\n<\/ol>\n

      Correct Answer: 1. It prevents ordinary users from logging in while allowing appropriate administrative access<\/b><\/p>\n

      Explanation:<\/b><\/p>\n

      The <\/span>\/etc\/nologin<\/span> file is commonly used to temporarily prevent non-privileged users from logging into a Linux system. If the file exists, login programs may display its contents as a message explaining why logins are currently unavailable. This can be useful during maintenance, shutdown, or other administrative activities. Its presence does not mean that user accounts have been deleted or permanently disabled. The exact behavior can depend on the authentication and login mechanisms in use, but the standard concept tested in Linux administration is that <\/span>\/etc\/nologin<\/span> temporarily blocks ordinary user logins.<\/span><\/p>\n

      Question: 223. Which directory commonly contains programs intended primarily for system administration that are not normally needed by ordinary users?<\/b><\/p>\n

        \n
      1. <\/b> \/home<\/span>
        \n<\/span>2.<\/b> \/usr\/sbin<\/span>
        \n<\/span>3.<\/b> \/tmp<\/span>
        \n<\/span>4.<\/b> \/var\/cache<\/span><\/li>\n<\/ol>\n

        Correct Answer: 2. <\/b>\/usr\/sbin<\/b><\/p>\n

        Explanation:<\/b><\/p>\n

        The <\/span>\/usr\/sbin<\/span> directory commonly contains system-administration commands, particularly programs intended for use by administrators rather than ordinary users. Examples can include utilities involved in system services, account management, networking, and other administrative tasks. On modern Linux distributions, the traditional distinction between <\/span>\/bin<\/span>, <\/span>\/sbin<\/span>, <\/span>\/usr\/bin<\/span>, and <\/span>\/usr\/sbin<\/span> can be affected by filesystem unification, where some directories are symbolic links or merged into <\/span>\/usr<\/span>. Nevertheless, understanding the conventional purpose of <\/span>\/usr\/sbin<\/span> remains relevant for Linux certification exams. It should not be confused with <\/span>\/home<\/span>, which normally contains users’ personal directories.<\/span><\/p>\n

        Question: 224. What is the typical purpose of the <\/b>\/lib64<\/b> directory on a 64-bit Linux system?<\/b><\/p>\n

          \n
        1. <\/b> It stores temporary files created by applications<\/span>
          \n<\/span>2.<\/b> It contains users’ home directories<\/span>
          \n<\/span>3.<\/b> It stores system log files<\/span>
          \n<\/span>4.<\/b> It commonly contains 64-bit shared libraries required by programs<\/span><\/li>\n<\/ol>\n

          Correct Answer: 4. It commonly contains 64-bit shared libraries required by programs<\/b><\/p>\n

          Explanation:<\/b><\/p>\n

          On systems that use a traditional filesystem layout, <\/span>\/lib64<\/span> commonly contains 64-bit shared libraries and related runtime components required by 64-bit programs. Shared libraries provide reusable code that applications can load instead of carrying separate copies of the same functionality. The exact directory structure varies between distributions and architectures, and some modern systems may use a unified <\/span>\/usr<\/span> layout. Nevertheless, the conventional meaning of <\/span>\/lib64<\/span> is associated with 64-bit libraries. It should not be confused with <\/span>\/var\/log<\/span>, which stores logs, or <\/span>\/home<\/span>, which normally contains users’ personal data and configuration files.<\/span><\/p>\n

          Question: 225. Which directory is commonly used for cached application or package data that can generally be regenerated if necessary?<\/b><\/p>\n

            \n
          1. <\/b> \/var\/cache<\/span>
            \n<\/span>2.<\/b> \/var\/spool<\/span>
            \n<\/span>3.<\/b> \/boot<\/span>
            \n<\/span>4.<\/b> \/dev<\/span><\/li>\n<\/ol>\n

            Correct Answer: 1. <\/b>\/var\/cache<\/b><\/p>\n

            Explanation:<\/b><\/p>\n

            The <\/span>\/var\/cache<\/span> directory is conventionally used for cached data generated by applications and system services. Cached information is generally stored to improve performance or avoid repeatedly downloading or generating the same information. A key characteristic of cache data is that it can often be regenerated when necessary, although deleting cache files may affect performance temporarily. This differs from <\/span>\/var\/spool<\/span>, which holds queued data waiting for processing, such as print or mail queues. <\/span>\/boot<\/span> contains files involved in booting the system, while <\/span>\/dev<\/span> provides device-related filesystem entries. These distinctions are useful when understanding Linux filesystem organization.<\/span><\/p>\n

            Question: 226. What type of data is conventionally stored under <\/b>\/var\/spool<\/b>?<\/b><\/p>\n

              \n
            1. <\/b> Kernel source code<\/span>
              \n<\/span>2.<\/b> Files waiting in queues for later processing<\/span>
              \n<\/span>3.<\/b> User home directories<\/span>
              \n<\/span>4.<\/b> Bootloader configuration only<\/span><\/li>\n<\/ol>\n

              Correct Answer: 2. Files waiting in queues for later processing<\/b><\/p>\n

              Explanation:<\/b><\/p>\n

              The <\/span>\/var\/spool<\/span> directory is traditionally used for data that is waiting to be processed by a system service or application. Examples include print jobs waiting for a printer, mail waiting for delivery, or other queued tasks. Spooling allows a producer and consumer to operate at different times or speeds. This differs from <\/span>\/var\/cache<\/span>, where data is stored primarily for performance and can generally be regenerated. <\/span>\/var\/spool<\/span> is part of the variable-data hierarchy because its contents can change frequently as queued jobs are created, processed, and removed. Understanding these directory purposes helps administrators locate service-related data.<\/span><\/p>\n

              Question: 227. Which directory is intended for temporary files that may need to remain available longer than files in <\/b>\/tmp<\/b>?<\/b><\/p>\n

                \n
              1. <\/b> \/boot<\/span>
                \n<\/span>2.<\/b> \/etc<\/span>
                \n<\/span>3.<\/b> \/var\/tmp<\/span>
                \n<\/span>4.<\/b> \/usr<\/span><\/li>\n<\/ol>\n

                Correct Answer: 3. <\/b>\/var\/tmp<\/b><\/p>\n

                Explanation:<\/b><\/p>\n

                The <\/span>\/var\/tmp<\/span> directory is designed for temporary files that may need to persist across system reboots. In contrast, <\/span>\/tmp<\/span> is intended for temporary data and may be cleaned more aggressively, depending on system configuration. The exact cleanup policy is distribution- and configuration-dependent, but the traditional distinction is that <\/span>\/var\/tmp<\/span> provides a more persistent location for temporary data. Neither directory should be treated as permanent storage for important user files. <\/span>\/var\/tmp<\/span> belongs under <\/span>\/var<\/span> because its contents can change frequently. This distinction is useful when selecting an appropriate temporary storage location for scripts and applications.<\/span><\/p>\n

                Question: 228. Which command option causes <\/b>ls<\/b> to display file sizes in a human-readable format such as K, M, or G?<\/b><\/p>\n

                  \n
                1. <\/b> ls -R<\/span>
                  \n<\/span>2.<\/b> ls -a<\/span>
                  \n<\/span>3.<\/b> ls -F<\/span>
                  \n<\/span>4.<\/b> ls -h<\/span><\/li>\n<\/ol>\n

                  Correct Answer: 4. <\/b>ls -h<\/b><\/p>\n

                  Explanation:<\/b><\/p>\n

                  The <\/span>-h<\/span> option of <\/span>ls<\/span> requests human-readable file sizes, typically when used together with a long listing such as <\/span>ls -lh<\/span>. Instead of displaying large byte counts that may be difficult to interpret quickly, the output can use units such as K, M, or G. The <\/span>-a<\/span> option displays hidden entries, <\/span>-R<\/span> recursively lists subdirectories, and <\/span>-F<\/span> adds indicators to certain filenames. Therefore, when the goal is specifically to make file sizes easier for humans to read, <\/span>ls -h<\/span> is the relevant option. Combining options is common when inspecting files interactively.<\/span><\/p>\n

                  Question: 229. What does <\/b>ls -R<\/b> do?<\/b><\/p>\n

                    \n
                  1. <\/b> It displays only hidden files<\/span>
                    \n<\/span>2.<\/b> It recursively lists the contents of directories and their subdirectories<\/span>
                    \n<\/span>3.<\/b> It reverses filename sorting only<\/span>
                    \n<\/span>4.<\/b> It displays file sizes in gigabytes<\/span><\/li>\n<\/ol>\n

                    Correct Answer: 2. It recursively lists the contents of directories and their subdirectories<\/b><\/p>\n

                    Explanation:<\/b><\/p>\n

                    The <\/span>-R<\/span> option tells <\/span>ls<\/span> to list directories recursively. When a directory contains subdirectories, <\/span>ls -R<\/span> enters those subdirectories and displays their contents as well, continuing through nested directory levels. This can be useful when you need a quick textual overview of an entire directory tree. It differs from <\/span>ls -a<\/span>, which reveals hidden entries, and <\/span>ls -h<\/span>, which makes file sizes human-readable. The recursive option can produce a large amount of output when used on a directory tree containing many files, so it should be used carefully on large filesystem hierarchies.<\/span><\/p>\n

                    Question: 230. What does <\/b>ls -F<\/b> commonly add to directory listings?<\/b><\/p>\n

                      \n
                    1. <\/b> File type indicators such as <\/span>\/<\/span> for directories<\/span>
                      \n<\/span>2.<\/b> Full inode tables for every file<\/span>
                      \n<\/span>3.<\/b> File contents after each filename<\/span>
                      \n<\/span>4.<\/b> Detailed ownership information<\/span><\/li>\n<\/ol>\n

                      Correct Answer: 1. File type indicators such as <\/b>\/<\/b> for directories<\/b><\/p>\n

                      Explanation:<\/b><\/p>\n

                      The <\/span>-F<\/span> option causes <\/span>ls<\/span> to append indicators to certain filenames so that users can more easily recognize file types. For example, a directory is commonly displayed with a trailing <\/span>\/<\/span>, while an executable file may receive an asterisk. Symbolic links can also receive an appropriate indicator. This does not display file contents or provide the complete ownership and permission information associated with <\/span>ls -l<\/span>. The purpose of <\/span>-F<\/span> is visual identification of file types within a directory listing. It can be particularly convenient when working interactively at a shell prompt.<\/span><\/p>\n

                      Question: 231. Which command can resolve a symbolic link to its final target path, following links recursively?<\/b><\/p>\n

                        \n
                      1. <\/b> echo<\/span>
                        \n<\/span>2.<\/b> basename<\/span>
                        \n<\/span>3.<\/b> readlink -f<\/span>
                        \n<\/span>4.<\/b> dirname<\/span><\/li>\n<\/ol>\n

                        Correct Answer: 3. <\/b>readlink -f<\/b><\/p>\n

                        Explanation:<\/b><\/p>\n

                        The <\/span>readlink -f<\/span> command can resolve a pathname by following symbolic links and producing a canonicalized absolute path when the relevant target path exists. This is useful in scripts when the actual location behind a symbolic link needs to be determined. <\/span>basename<\/span> extracts the final component of a pathname, while <\/span>dirname<\/span> extracts the directory portion. <\/span>echo<\/span> simply writes arguments to standard output and does not resolve links by itself. The exact behavior of canonicalization can depend on whether components of the path exist, but <\/span>readlink -f<\/span> is the standard command associated with fully resolving symbolic-link paths.<\/span><\/p>\n

                        Question: 232. What is an important property of a hard link compared with a symbolic link?<\/b><\/p>\n

                          \n
                        1. <\/b> A hard link normally cannot cross filesystem boundaries<\/span>
                          \n<\/span>2.<\/b> A hard link always points to a different inode<\/span>
                          \n<\/span>3.<\/b> A hard link can reference any directory on another filesystem<\/span>
                          \n<\/span>4.<\/b> A hard link becomes broken whenever the original filename is removed<\/span><\/li>\n<\/ol>\n

                          Correct Answer: 1. A hard link normally cannot cross filesystem boundaries<\/b><\/p>\n

                          Explanation:<\/b><\/p>\n

                          A hard link is another directory entry referring to the same inode as an existing file. Because the inode belongs to a particular filesystem, hard links normally cannot be created across different filesystem boundaries. Removing one filename does not destroy the underlying file as long as another hard link still references the inode. This differs from a symbolic link, which stores a pathname pointing to another object and can generally cross filesystem boundaries. Hard links also have restrictions, such as the normal prohibition against creating hard links to directories for ordinary users, helping prevent filesystem structures from becoming cyclic.<\/span><\/p>\n

                          Question: 233. What is an inode in a Unix-like filesystem?<\/b><\/p>\n

                            \n
                          1. <\/b> A network address assigned to a computer<\/span>
                            \n<\/span>2.<\/b> A kernel process identifier<\/span>
                            \n<\/span>3.<\/b> A data structure containing filesystem metadata about a file<\/span>
                            \n<\/span>4.<\/b> A shell variable containing the current directory<\/span><\/li>\n<\/ol>\n

                            Correct Answer: 3. A data structure containing filesystem metadata about a file<\/b><\/p>\n

                            Explanation:<\/b><\/p>\n

                            An inode is a filesystem data structure that stores metadata about a filesystem object, such as ownership, permissions, timestamps, file type, and information used to locate the file’s data blocks. The filename itself is generally stored in a directory entry that maps the name to an inode number. This is why multiple hard links can reference the same inode while having different filenames. Inodes are fundamental to understanding Unix-like filesystems and file identity. The exact inode structure and allocation details vary by filesystem implementation, but the general concept remains central to Linux filesystem administration.<\/span><\/p>\n

                            Question: 234. What is the purpose of the <\/b>du -sh<\/b> command when used with a directory?<\/b><\/p>\n

                              \n
                            1. <\/b> It displays all running processes<\/span>
                              \n<\/span>2.<\/b> It shows the total disk usage of the directory in a human-readable form<\/span>
                              \n<\/span>3.<\/b> It changes the directory permissions<\/span>
                              \n<\/span>4.<\/b> It removes unused files from the directory<\/span><\/li>\n<\/ol>\n

                              Correct Answer: 2. It shows the total disk usage of the directory in a human-readable form<\/b><\/p>\n

                              Explanation:<\/b><\/p>\n

                              The <\/span>du -sh<\/span> command is commonly used to obtain a concise, human-readable summary of disk usage. The <\/span>-s<\/span> option requests a summary rather than listing usage for every nested item, while <\/span>-h<\/span> formats sizes in units that are easier for humans to interpret. For example, a directory might be reported using megabytes or gigabytes rather than a large number of filesystem blocks. <\/span>du<\/span> measures space associated with files and directories, whereas <\/span>df<\/span> reports filesystem-level space usage. Therefore, <\/span>du -sh<\/span> is especially useful when identifying how much space a particular directory hierarchy consumes.<\/span><\/p>\n

                              Question: 235. What does the <\/b>-h<\/b> option commonly do when used with <\/b>df<\/b>?<\/b><\/p>\n

                                \n
                              1. <\/b> It hides mounted filesystems<\/span>
                                \n<\/span>2.<\/b> It displays filesystem space values in human-readable units<\/span>
                                \n<\/span>3.<\/b> It deletes unused filesystem blocks<\/span>
                                \n<\/span>4.<\/b> It changes the filesystem type<\/span><\/li>\n<\/ol>\n

                                Correct Answer: 2. It displays filesystem space values in human-readable units<\/b><\/p>\n

                                Explanation:<\/b><\/p>\n

                                The <\/span>-h<\/span> option of <\/span>df<\/span> requests human-readable filesystem size information. Instead of displaying large values primarily as raw blocks, the command can present values using units such as K, M, G, or T. For example, <\/span>df -h<\/span> is commonly used when administrators want a quick overview of filesystem capacity, used space, available space, and utilization percentages. This option does not modify the filesystem or delete data. It only changes how the reported values are presented. Understanding the distinction between presentation options and filesystem-modifying commands is important when working safely from the Linux command line.<\/span><\/p>\n

                                Question: 236. What is a mount point in Linux?<\/b><\/p>\n

                                  \n
                                1. <\/b> A process that automatically mounts every disk<\/span>
                                  \n<\/span>2.<\/b> A special type of executable file<\/span>
                                  \n<\/span>3.<\/b> A directory where a filesystem is attached and made accessible<\/span>
                                  \n<\/span>4.<\/b> A user account used for mounting devices<\/span><\/li>\n<\/ol>\n

                                  Correct Answer: 3. A directory where a filesystem is attached and made accessible<\/b><\/p>\n

                                  Explanation:<\/b><\/p>\n

                                  A mount point is a directory in the existing filesystem hierarchy where another filesystem is attached and made accessible. Once mounted, the contents of the mounted filesystem appear through that directory. For example, a separate filesystem might be mounted at <\/span>\/mnt\/data<\/span> or another appropriate directory. The mount point itself is not a special executable program or user account. Linux presents filesystems through a unified directory tree, so mounting provides the connection between a filesystem device or source and a location in that tree. Understanding mount points is essential for managing disks and filesystems.<\/span><\/p>\n

                                  Question: 237. What does <\/b>mount -a<\/b> generally do?<\/b><\/p>\n

                                    \n
                                  1. <\/b> It attempts to mount all appropriate filesystems listed in <\/span>\/etc\/fstab<\/span>
                                    \n<\/span>2.<\/b> It removes all existing mounts<\/span>
                                    \n<\/span>3.<\/b> It formats every available disk<\/span>
                                    \n<\/span>4.<\/b> It lists only unmounted devices<\/span><\/li>\n<\/ol>\n

                                    Correct Answer: 1. It attempts to mount all appropriate filesystems listed in <\/b>\/etc\/fstab<\/b><\/p>\n

                                    Explanation:<\/b><\/p>\n

                                    The <\/span>mount -a<\/span> command tells the <\/span>mount<\/span> utility to attempt mounting all filesystems listed in <\/span>\/etc\/fstab<\/span> that are configured for automatic mounting. Entries that are marked with the appropriate options are considered, while entries such as those using <\/span>noauto<\/span> are excluded from automatic mounting. This command is often useful after editing <\/span>\/etc\/fstab<\/span> to test or activate configured mounts without rebooting. It does not format disks or remove existing mounts. Administrators should verify <\/span>\/etc\/fstab<\/span> carefully before using <\/span>mount -a<\/span>, because incorrect entries can cause mounting errors.<\/span><\/p>\n

                                    Question: 238. In the output of <\/b>ps<\/b>, what does a process state of <\/b>Z<\/b> generally indicate?<\/b><\/p>\n

                                      \n
                                    1. <\/b> The process is actively running on a CPU<\/span>
                                      \n<\/span>2.<\/b> The process is sleeping normally<\/span>
                                      \n<\/span>3.<\/b> The process is stopped by a terminal<\/span>
                                      \n<\/span>4.<\/b> The process is a zombie waiting for its parent to collect its exit status<\/span><\/li>\n<\/ol>\n

                                      Correct Answer: 4. The process is a zombie waiting for its parent to collect its exit status<\/b><\/p>\n

                                      Explanation:<\/b><\/p>\n

                                      A process with a <\/span>Z<\/span> state is generally a zombie process. A zombie has already terminated, so it is no longer executing, but an entry remains in the process table because its parent has not yet collected its termination status through an appropriate wait operation. Zombies therefore do not consume CPU time like active processes, although they occupy process-table resources. The appropriate solution is usually to address the parent process or the software responsible for failing to reap child processes. Simply sending ordinary termination signals to a process that has already exited does not make the zombie execute again.<\/span><\/p>\n

                                      Question: 239. Which signal is sent by <\/b>kill -9<\/b>?<\/b><\/p>\n

                                        \n
                                      1. <\/b> SIGTERM<\/span>
                                        \n<\/span>2.<\/b> SIGKILL<\/span>
                                        \n<\/span>3.<\/b> SIGSTOP<\/span>
                                        \n<\/span>4.<\/b> SIGCONT<\/span><\/li>\n<\/ol>\n

                                        Correct Answer: 2. <\/b>SIGKILL<\/b><\/p>\n

                                        Explanation:<\/b><\/p>\n

                                        The command <\/span>kill -9<\/span> sends signal number 9, which is <\/span>SIGKILL<\/span> on standard Linux systems. <\/span>SIGKILL<\/span> requests immediate termination and cannot be caught, blocked, or handled by the target process. This makes it significantly different from <\/span>SIGTERM<\/span>, which allows a program an opportunity to perform cleanup before exiting. Because <\/span>SIGKILL<\/span> prevents normal cleanup handling, it should generally not be the first choice when a process can be terminated gracefully. <\/span>SIGSTOP<\/span> stops a process, while <\/span>SIGCONT<\/span> resumes a stopped process. Understanding these signal differences is important for process management.<\/span><\/p>\n

                                        Question: 240. Which shell parameter represents the number of positional parameters supplied to a shell script or function?<\/b><\/p>\n

                                          \n
                                        1. <\/b> $?<\/span>
                                          \n<\/span>2.<\/b> $0<\/span>
                                          \n<\/span>3.<\/b> $#<\/span>
                                          \n<\/span>4.<\/b> $PWD<\/span><\/li>\n<\/ol>\n

                                          Correct Answer: 3. <\/b>$#<\/b><\/p>\n

                                          Explanation:<\/b><\/p>\n

                                          The special shell parameter <\/span>$#<\/span> contains the number of positional parameters supplied to a shell script or function. For example, if a script is executed with three arguments, <\/span>$#<\/span> evaluates to <\/span>3<\/span>. <\/span>$0<\/span> generally represents the name used to invoke the script or function context, while <\/span>$?<\/span> contains the exit status of the most recently executed command. <\/span>$PWD<\/span> normally contains the current working directory maintained by the shell. Positional parameters such as <\/span>$1<\/span>, <\/span>$2<\/span>, and so on contain individual arguments, making <\/span>$#<\/span> useful for checking how many arguments were supplied.<\/span><\/p>\n

                                           <\/p>\n","protected":false},"excerpt":{"rendered":"

                                          View Full LPI 101-500 Exam Dumps and Practice Test Dumps   Question: 221. Which file commonly lists the shells that are recognized as valid login shells on a Linux system? \/etc\/profile 2. \/etc\/bashrc 3. \/etc\/shells 4. \/etc\/login.conf Correct Answer: 3. \/etc\/shells Explanation: The \/etc\/shells file contains a list of valid login shells available on the […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[1648,1647],"tags":[],"_links":{"self":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/18628"}],"collection":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/comments?post=18628"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/18628\/revisions"}],"predecessor-version":[{"id":18629,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/18628\/revisions\/18629"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=18628"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=18628"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=18628"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}