{"id":17587,"date":"2026-09-21T10:21:17","date_gmt":"2026-09-21T10:21:17","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=17587"},"modified":"2026-09-21T10:21:17","modified_gmt":"2026-09-21T10:21:17","slug":"omnissa-1h0_25-practice-test-questions-and-exam-dumps-part15-q281-300","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/omnissa-1h0_25-practice-test-questions-and-exam-dumps-part15-q281-300\/","title":{"rendered":"Omnissa 1H0_25 Practice Test Questions and Exam Dumps Part15 Q281-300"},"content":{"rendered":"

View Full <\/b>Omnissa 1H0_25 Exam Dumps<\/b><\/a> and Practice Test Dumps.<\/b><\/p>\n


\n<\/b>Q281. In App Volumes, which assignment type ensures that an entity always receives the package currently marked as CURRENT for an application?<\/b><\/p>\n

    \n
  1. <\/b> Marker<\/span>
    \n<\/span>2.<\/b> Package<\/span>
    \n<\/span>3.<\/b> Multiple<\/span>
    \n<\/span>4.<\/b> Writable<\/span><\/li>\n<\/ol>\n

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

    Explanation:<\/b> The Marker assignment type associates an entity with the package currently marked as <\/span>CURRENT<\/span> for an App Volumes application. This is useful when administrators want users or computers to automatically receive the latest package designated as the active production version without manually changing each assignment whenever a new package becomes current. A Package assignment pins the entity to one specific package version. Multiple assignment permits several on-demand package versions, including CURRENT, to be available so the user can choose. Marker therefore supports streamlined application lifecycle management where consumers should follow the administrator-designated current release.<\/span><\/p>\n

    Q282. An administrator wants a user to continue receiving exactly version 3 of an App Volumes package even after version 4 becomes CURRENT. Which assignment type should be used?<\/b><\/p>\n

      \n
    1. <\/b> Marker<\/span>
      \n<\/span>2.<\/b> Multiple<\/span>
      \n<\/span>3.<\/b> CURRENT<\/span>
      \n<\/span>4.<\/b> Package<\/span><\/li>\n<\/ol>\n

      Correct Answer: 4. Package<\/b><\/p>\n

      Explanation:<\/b> A Package assignment targets a specific version of an App Volumes application package. If version 3 is explicitly assigned, the entity continues to receive that package rather than automatically moving to version 4 when the newer version becomes CURRENT. This is useful for staged migrations, compatibility requirements, testing groups, or users who must remain on an older approved release. Marker assignments follow the CURRENT package, while Multiple assignments expose several on-demand versions. Selecting Package therefore gives administrators precise version control instead of tying the assignment to whichever release is currently designated as the latest.<\/span><\/p>\n

      Q283. Which App Volumes assignment type allows an end user to choose between multiple on-demand package versions of the same application?<\/b><\/p>\n

        \n
      1. <\/b> Computer<\/span>
        \n<\/span>2.<\/b> Multiple<\/span>
        \n<\/span>3.<\/b> Marker<\/span>
        \n<\/span>4.<\/b> Writable Volume<\/span><\/li>\n<\/ol>\n

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

        Explanation:<\/b> The Multiple assignment type allows several application packages, including the package marked CURRENT, to be assigned to an entity at the same time for on-demand delivery. This gives end users the option to select which available application version they want to run. The capability can be useful when different application releases are required for compatibility testing or specialized workflows. Marker follows only the CURRENT package, while a Package assignment delivers one specified version. Writable Volumes serve a different purpose involving supported user-specific data or applications. Multiple assignment therefore provides the flexibility required when several versions must coexist for user selection.<\/span><\/p>\n

        Q284. In App Volumes Manager, which tab can an administrator use to view application packages and Writable Volumes that are currently attached and in use?<\/b><\/p>\n

          \n
        1. <\/b> Programs<\/span>
          \n<\/span>2.<\/b> Assignments<\/span>
          \n<\/span>3.<\/b> Attachments<\/span>
          \n<\/span>4.<\/b> Infrastructure<\/span><\/li>\n<\/ol>\n

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

          Explanation:<\/b> The Attachments tab in App Volumes Manager displays packages and Writable Volumes that are currently delivered and attached to endpoint computers. Administrators can review information such as the application associated with the package, the host computer receiving the volume, disk mode, assignment information, and other attachment details. For on-demand packages, the attachment count changes when the user actually launches the application’s shortcut. This makes the Attachments view particularly useful for troubleshooting delivery and determining whether a package is actively mounted. Programs focuses on package contents, while Assignments shows which applications are assigned to entities.<\/span><\/p>\n

          Q285. When an App Volumes package is delivered through a Horizon Published App on Demand entitlement, what value can appear in the Assignment column of the App Volumes Attachments view?<\/b><\/p>\n

            \n
          1. <\/b> Horizon<\/span>
            \n<\/span>2.<\/b> Manual<\/span>
            \n<\/span>3.<\/b> Dynamic<\/span>
            \n<\/span>4.<\/b> RDS<\/span><\/li>\n<\/ol>\n

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

            Explanation:<\/b> If an App Volumes package attachment is triggered by an entitlement configured through Horizon Published Apps on Demand, the App Volumes Manager Attachments view identifies the assignment source as <\/span>Horizon<\/span>. This helps administrators distinguish packages delivered through Horizon integration from those delivered through standard App Volumes assignments. The information is useful during troubleshooting because it shows the delivery path that caused the package to attach to the host. On-demand attachments also appear only when the user actually launches the associated application. Understanding the assignment source helps administrators determine whether an issue belongs to Horizon entitlement configuration or traditional App Volumes assignment logic.<\/span><\/p>\n

            Q286. Which entity types can receive App Volumes application assignments when Microsoft Entra ID is the registered identity domain?<\/b><\/p>\n

              \n
            1. <\/b> Users and OUs only<\/span>
              \n<\/span>2.<\/b> OUs and computers only<\/span>
              \n<\/span>3.<\/b> Users, groups, and computers<\/span>
              \n<\/span>4.<\/b> Users, groups, computers, and OUs<\/span><\/li>\n<\/ol>\n

              Correct Answer: 3. Users, groups, and computers<\/b><\/p>\n

              Explanation:<\/b> When Microsoft Entra ID is the registered identity domain, App Volumes supports application assignments to users, groups, and computers. Organizational units are an Active Directory construct and are therefore not available as an Entra ID assignment entity in this model. By comparison, when traditional Active Directory is registered, App Volumes can assign applications to users, computers, groups, and OUs. Understanding this difference is important when designing assignment strategies across identity platforms. Administrators migrating from Active Directory to Entra ID should not assume that OU-based targeting will remain available and may need to redesign assignments around supported groups or devices.<\/span><\/p>\n

              Q287. An application consumes substantial CPU and memory, and an administrator wants Horizon to avoid launching too many instances on the same RDS host. Which feature should be configured?<\/b><\/p>\n

                \n
              1. <\/b> Session Collaboration<\/span>
                \n<\/span>2.<\/b> Client Restriction<\/span>
                \n<\/span>3.<\/b> Folder Preference<\/span>
                \n<\/span>4.<\/b> Application anti-affinity rule<\/span><\/li>\n<\/ol>\n

                Correct Answer: 4. Application anti-affinity rule<\/b><\/p>\n

                Explanation:<\/b> Horizon application anti-affinity rules help prevent resource-intensive applications from concentrating too many instances on one RDS host. The administrator defines one or more application process-matching patterns and a maximum count. Horizon Agent evaluates the number of matching processes on an RDS host, and Connection Server can skip that host for new application sessions when the configured maximum has been reached. This mechanism is particularly useful for CPU- or memory-intensive software. Client Restrictions control endpoint eligibility, Folder Preferences organize user resources, and Session Collaboration supports shared sessions. Anti-affinity directly addresses per-host application concentration and capacity protection.<\/span><\/p>\n

                Q288. An application anti-affinity rule has a maximum count of 2 for <\/b>autocad.exe<\/b>. What happens when two matching instances are already running on an RDS host and another session is requested?<\/b><\/p>\n

                  \n
                1. <\/b> Horizon terminates both existing instances<\/span>
                  \n<\/span>2.<\/b> Connection Server skips that RDS host when selecting a host for the new application session<\/span>
                  \n<\/span>3.<\/b> The RDS host is removed from the farm<\/span>
                  \n<\/span>4.<\/b> The application pool is automatically disabled<\/span><\/li>\n<\/ol>\n

                  Correct Answer: 2. Connection Server skips that RDS host when selecting a host for the new application session<\/b><\/p>\n

                  Explanation:<\/b> With an anti-affinity maximum count of two, Horizon evaluates how many matching processes are already running on each RDS host. If the configured count has been reached, Connection Server excludes that RDS host when selecting where to launch the next applicable application session. Existing sessions are not terminated, and the host remains part of the farm. The application pool also stays enabled. The rule is designed to influence placement of new sessions rather than disrupt active users. This allows administrators to spread demanding applications across available RDS hosts while preserving existing workloads.<\/span><\/p>\n

                  Q289. Which wildcard in a Horizon application anti-affinity pattern matches any single character?<\/b><\/p>\n

                    \n
                  1. <\/b> *<\/span>
                    \n<\/span>2.<\/b> %<\/span>
                    \n<\/span>3.<\/b> ?<\/span>
                    \n<\/span>4.<\/b> #<\/span><\/li>\n<\/ol>\n

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

                    Explanation:<\/b> Horizon anti-affinity application-matching patterns support common wildcard syntax. A question mark (<\/span>?<\/span>) matches exactly one character, while an asterisk (<\/span>*<\/span>) matches zero or more characters. This allows administrators to build patterns that match groups of related process names without specifying every executable individually. For example, patterns can be designed to match similar application executable names or extensions. Accurate pattern construction is important because the anti-affinity rule controls which RDS hosts remain eligible for new application sessions. Using an incorrect wildcard can cause the rule to match too many processes or fail to match the intended application workload.<\/span><\/p>\n

                    Q290. An administrator needs to change the ID of an existing Horizon application pool. What is the correct approach?<\/b><\/p>\n

                      \n
                    1. <\/b> The application pool ID cannot be changed after creation<\/span>
                      \n<\/span>2.<\/b> Edit it from the General tab<\/span>
                      \n<\/span>3.<\/b> Change the farm ID first<\/span>
                      \n<\/span>4.<\/b> Rename it through Horizon Client<\/span><\/li>\n<\/ol>\n

                      Correct Answer: 1. The application pool ID cannot be changed after creation<\/b><\/p>\n

                      Explanation:<\/b> Horizon allows administrators to edit many application-pool properties, including display name, publisher, executable path, start folder, parameters, description, and related settings. However, the application pool ID cannot be modified after the pool is created. If an organization requires a different ID, the administrator would generally need to create an appropriately configured replacement application pool rather than trying to rename the immutable identifier. The access group also cannot be changed directly on the application pool. Horizon Client is an end-user interface and cannot modify administrative pool identifiers. Distinguishing IDs from editable display names helps prevent unnecessary troubleshooting.<\/span><\/p>\n

                      Q291. Which statement correctly describes changing the access group of an existing Horizon application pool?<\/b><\/p>\n

                        \n
                      1. <\/b> It can be changed directly from the application pool editor<\/span>
                        \n<\/span>2.<\/b> It cannot be directly changed on the application pool<\/span>
                        \n<\/span>3.<\/b> Users can change it in Horizon Client<\/span>
                        \n<\/span>4.<\/b> It changes automatically whenever the display name changes<\/span><\/li>\n<\/ol>\n

                        Correct Answer: 2. It cannot be directly changed on the application pool<\/b><\/p>\n

                        Explanation:<\/b> Horizon documentation specifies that an application pool’s access group cannot be edited directly. Published applications are associated with farms, and administrative scoping is tied to that underlying farm structure. This means administrators should plan access-group organization carefully when designing farms and published application resources. Other application-pool settings such as display name, executable path, publisher, parameters, and description remain editable. End users cannot change administrative access groups from Horizon Client, and changing an application’s display name does not alter its administrative scope. Understanding these limitations is important when implementing delegated administration across large Horizon deployments.<\/span><\/p>\n

                        Q292. What distinguishes an automated instant-clone RDS farm from a manual RDS farm?<\/b><\/p>\n

                          \n
                        1. <\/b> Manual farms cannot provide published applications<\/span>
                          \n<\/span>2.<\/b> Automated farms cannot contain Windows servers<\/span>
                          \n<\/span>3.<\/b> Manual farms require Cloud Pod Architecture<\/span>
                          \n<\/span>4.<\/b> Connection Server provisions the RDS virtual machines for an automated instant-clone farm<\/span><\/li>\n<\/ol>\n

                          Correct Answer: 4. Connection Server provisions the RDS virtual machines for an automated instant-clone farm<\/b><\/p>\n

                          Explanation:<\/b> A manual farm consists of RDS hosts that already exist and are manually added to Horizon. Those hosts can be supported physical or virtual machines. In an automated instant-clone farm, Connection Server provisions the RDS virtual machines using the configuration parameters and image selected by the administrator. This allows Horizon to manage capacity and lifecycle more consistently across standardized hosts. Both farm types can be used to deliver published applications or desktops when properly configured. Cloud Pod Architecture is unrelated to whether the farm is manual or automated. The key distinction is whether Horizon automatically provisions and manages the RDSH virtual machines.<\/span><\/p>\n

                          Q293. Which Horizon privilege allows administrators to add or remove administrator users and groups in Horizon Console?<\/b><\/p>\n

                            \n
                          1. <\/b> Manage Roles and Permissions<\/span>
                            \n<\/span>2.<\/b> Manage Machine<\/span>
                            \n<\/span>3.<\/b> Manage Sessions<\/span>
                            \n<\/span>4.<\/b> Manage Global Entitlements<\/span><\/li>\n<\/ol>\n

                            Correct Answer: 1. Manage Roles and Permissions<\/b><\/p>\n

                            Explanation:<\/b> Administrators who hold the Manage Roles and Permissions privilege can add or remove Horizon administrator users and groups. This is a powerful capability because administrative assignments determine who can configure, monitor, and control Horizon resources. Organizations should therefore grant this privilege only to appropriately trusted administrators. Horizon includes predefined roles, but custom roles can also be created from selected privileges to implement a least-privilege model. Manage Machine and Manage Sessions control operational actions on machines or sessions, while Cloud Pod privileges govern federation resources. Manage Roles and Permissions specifically controls Horizon administrative authorization management.<\/span><\/p>\n

                            Q294. Which Horizon Console role is described as the most powerful built-in administrative role?<\/b><\/p>\n

                              \n
                            1. <\/b> Help Desk Administrators<\/span>
                              \n<\/span>2.<\/b> Administrators<\/span>
                              \n<\/span>3.<\/b> Inventory Administrators<\/span>
                              \n<\/span>4.<\/b> Local Administrators<\/span><\/li>\n<\/ol>\n

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

                              Explanation:<\/b> The Administrators role is the most powerful predefined role in Horizon Console. During Connection Server installation, an Administrators account is specified, and members of that account receive the Administrators role. The account can be a supported local Administrators group on Connection Server or a domain user or group, depending on the deployment configuration. Because this role provides extensive control, organizations should limit membership and delegate narrower tasks through predefined or custom roles whenever possible. Horizon’s role-based administration model is intended to avoid granting full administrative access to personnel who require only monitoring, help desk, pool-management, or other specific operational capabilities.<\/span><\/p>\n

                              Q295. What is the purpose of privilege scope in Horizon delegated administration?<\/b><\/p>\n

                                \n
                              1. <\/b> To select the Horizon display protocol<\/span>
                                \n<\/span>2.<\/b> To determine which App Volumes packages attach<\/span>
                                \n<\/span>3.<\/b> To change the user authentication method<\/span>
                                \n<\/span>4.<\/b> To define the extent of objects on which an administrator’s privileges apply<\/span><\/li>\n<\/ol>\n

                                Correct Answer: 4. To define the extent of objects on which an administrator’s privileges apply<\/b><\/p>\n

                                Explanation:<\/b> Privilege scope determines where a Horizon administrative privilege is effective. Some privileges apply globally across the environment, while object-specific privileges apply to resources such as desktop pools, farms, or machines. Other operations can require permissions at a root access group or, in Cloud Pod Architecture, the federation root. Understanding scope is essential when designing least-privilege roles because granting a privilege alone does not always define all resources on which that administrator can exercise it. Display protocols, application attachments, and authentication methods are separate configuration concepts. Scope is specifically about the boundaries within which Horizon administrative permissions operate.<\/span><\/p>\n

                                Q296. Which statement correctly describes Unified Access Gateway built-in High Availability?<\/b><\/p>\n

                                  \n
                                1. <\/b> It replaces every type of load balancer for every protocol<\/span>
                                  \n<\/span>2.<\/b> It is a generic enterprise load-balancing product<\/span>
                                  \n<\/span>3.<\/b> It can reduce the need for a third-party load balancer in front of UAG for supported use cases<\/span>
                                  \n<\/span>4.<\/b> It requires Horizon Connection Server to share the same IP address<\/span><\/li>\n<\/ol>\n

                                  Correct Answer: 3. It can reduce the need for a third-party load balancer in front of UAG for supported use cases<\/b><\/p>\n

                                  Explanation:<\/b> Unified Access Gateway includes a built-in High Availability capability intended for supported Horizon and related end-user-computing use cases. It can reduce deployment complexity by eliminating the requirement for a separate third-party load balancer in front of UAG in suitable environments. Omnissa explicitly states that this capability is not a generic-purpose load balancer, and third-party load balancers remain supported for organizations that prefer them. The UAG HA design uses a shared virtual IP and cluster configuration rather than requiring Connection Server to share the same IP address. Architects should also verify platform-specific support limitations.<\/span><\/p>\n

                                  Q297. Which two key values are required when configuring Unified Access Gateway built-in High Availability nodes as part of the same cluster?<\/b><\/p>\n

                                    \n
                                  1. <\/b> The same application package and desktop pool<\/span>
                                    \n<\/span>2.<\/b> A virtual IP address and group ID<\/span>
                                    \n<\/span>3.<\/b> The same Horizon Client certificate and username<\/span>
                                    \n<\/span>4.<\/b> A DEM profile path and UAG tunnel URL<\/span><\/li>\n<\/ol>\n

                                    Correct Answer: 2. A virtual IP address and group ID<\/b><\/p>\n

                                    Explanation:<\/b> Unified Access Gateway High Availability requires administrators to configure an IPv4 virtual IP address and a group ID. Nodes intended to participate in the same HA cluster use the same virtual IP and group identifier. UAG ensures that the virtual IP is assigned to one node in the cluster at a time, providing the front-end address through which supported client traffic is received. These values have nothing to do with application packages, profile archives, or user credentials. Administrators should also ensure that the virtual IP is unique, reachable, and properly placed within the expected network topology.<\/span><\/p>\n

                                    Q298. During troubleshooting of Unified Access Gateway High Availability, which command can confirm whether the configured virtual IP address is assigned to the appliance’s network interface?<\/b><\/p>\n

                                      \n
                                    1. <\/b> net user<\/span>
                                      \n<\/span>2.<\/b> vdmadmin<\/span>
                                      \n<\/span>3.<\/b> ipconfig \/renew<\/span>
                                      \n<\/span>4.<\/b> ip addr<\/span><\/li>\n<\/ol>\n

                                      Correct Answer: 4. <\/b>ip addr<\/b><\/p>\n

                                      Explanation:<\/b> Omnissa’s UAG High Availability troubleshooting guidance recommends using the <\/span>ip addr<\/span> command from the Unified Access Gateway console to verify whether the configured virtual IP address is assigned to the expected interface, such as <\/span>eth0<\/span>. Administrators should also confirm that the virtual IP belongs to the same subnet where required, is reachable from clients, and is not already in use by another physical or virtual machine. <\/span>vdmadmin<\/span> is a Horizon Connection Server administration utility, while Windows commands such as <\/span>net user<\/span> and <\/span>ipconfig \/renew<\/span> are not the documented Linux appliance command for this UAG HA verification.<\/span><\/p>\n

                                      Q299. In an App Volumes deployment using Local Copy package access mode, which volume type is not supported for delivery to the Windows endpoint?<\/b><\/p>\n

                                        \n
                                      1. <\/b> Application packages assigned to users<\/span>
                                        \n<\/span>2.<\/b> Application packages assigned to computers<\/span>
                                        \n<\/span>3.<\/b> Writable Volumes<\/span>
                                        \n<\/span>4.<\/b> CURRENT application packages<\/span><\/li>\n<\/ol>\n

                                        Correct Answer: 3. Writable Volumes<\/b><\/p>\n

                                        Explanation:<\/b> In Local Copy package access mode, App Volumes supports delivery of application packages assigned to users or computers, but Writable Volumes are not supported. Local Copy is designed around copying supported application package content to the Windows endpoint rather than attaching the same types of shared-storage volumes used in traditional virtual desktop scenarios. This difference is important when architects compare laptop, remote-device, and VDI delivery models. If users require Writable Volumes, the deployment must use an architecture where that volume type is supported. Administrators should therefore check App Volumes delivery-mode compatibility before selecting Local Copy for an endpoint population.<\/span><\/p>\n

                                        Q300. In a shared-storage App Volumes VDI environment, which scenario supports a user-assigned Writable Volume according to the documented compatibility matrix?<\/b><\/p>\n

                                          \n
                                        1. <\/b> A floating VDI desktop<\/span>
                                          \n<\/span>2.<\/b> A dedicated VDI desktop<\/span>
                                          \n<\/span>3.<\/b> A published application RDSH session<\/span>
                                          \n<\/span>4.<\/b> A published desktop RDSH session<\/span><\/li>\n<\/ol>\n

                                          Correct Answer: 1. A floating VDI desktop<\/b><\/p>\n

                                          Explanation:<\/b> App Volumes’ documented shared-storage compatibility matrix supports a user-assigned Writable Volume with floating VDI desktops. The same matrix does not list user-assigned Writable Volumes as supported for dedicated VDI desktops, published applications, or published desktops in the referenced scenario. RDSH environments can support different computer-assigned Writable Volume combinations according to the matrix. Because App Volumes behavior varies depending on entity type, volume type, desktop assignment model, and delivery architecture, administrators should consult the current compatibility documentation rather than assuming that Writable Volumes work identically across every Horizon resource type.<\/span><\/p>\n

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

                                          View Full Omnissa 1H0_25 Exam Dumps and Practice Test Dumps. Q281. In App Volumes, which assignment type ensures that an entity always receives the package currently marked as CURRENT for an application? Marker 2. Package 3. Multiple 4. Writable Correct Answer: 1. Marker Explanation: The Marker assignment type associates an entity with the package currently […]<\/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\/17587"}],"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=17587"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/17587\/revisions"}],"predecessor-version":[{"id":17588,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/17587\/revisions\/17588"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=17587"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=17587"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=17587"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}