{"id":23446,"date":"2026-09-28T06:56:23","date_gmt":"2026-09-28T06:56:23","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=23446"},"modified":"2026-09-28T06:56:23","modified_gmt":"2026-09-28T06:56:23","slug":"google-professional-cloud-developer-practice-test-questions-and-exam-dumps-part2-q21-40","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/google-professional-cloud-developer-practice-test-questions-and-exam-dumps-part2-q21-40\/","title":{"rendered":"Google Professional Cloud Developer Practice Test Questions and Exam Dumps Part2 Q21-40"},"content":{"rendered":"

View Full <\/b>Google Professional Cloud Developer Exam Dumps<\/b><\/a> and Practice Test Dumps.<\/b><\/h2>\n

 <\/p>\n

Question 21<\/b><\/h3>\n

A developer is building a service that must process HTTP requests and automatically scale based on incoming traffic. The application is packaged as a container. Which deployment option is suitable?<\/b><\/p>\n

    \n
  1. Cloud Storage<\/span><\/li>\n
  2. Cloud Run<\/span><\/li>\n
  3. Cloud DNS<\/span><\/li>\n
  4. Cloud Scheduler<\/span><\/li>\n<\/ol>\n

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

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

    Cloud Run is designed to run containerized applications as managed services and automatically adjusts the number of instances based on incoming requests and configured scaling settings. Developers can deploy container images without managing a cluster or individual virtual machines. It supports HTTP-based services and integrates with Google Cloud identity, logging, monitoring, and networking capabilities. This makes it useful for APIs, web backends, and other stateless workloads. Cloud Storage stores objects, Cloud DNS manages domain records, and Cloud Scheduler initiates scheduled tasks. Cloud Run fits the requirement for a containerized HTTP service with managed scaling.<\/span><\/p>\n

    Question 22<\/b><\/h3>\n

    A team wants to create repeatable infrastructure deployments for its application environments using declarative configuration. Which Google Cloud service can help manage infrastructure as code?<\/b><\/p>\n

      \n
    1. Cloud Deployment Manager<\/span><\/li>\n
    2. Cloud Trace<\/span><\/li>\n
    3. Cloud CDN<\/span><\/li>\n
    4. Secret Manager<\/span><\/li>\n<\/ol>\n

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

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

      Cloud Deployment Manager is a Google Cloud infrastructure deployment service that uses declarative configuration to define and provision supported cloud resources. Infrastructure as code helps teams make deployments repeatable, review configuration changes, and maintain consistency across environments. Developers can describe resources and their relationships in configuration files rather than manually creating each resource through a console. Teams should also consider the current lifecycle and support status of the infrastructure tool they select when designing new solutions. Cloud Trace focuses on request tracing, Cloud CDN accelerates content delivery, and Secret Manager stores sensitive information. Deployment Manager is the service historically associated with declarative Google Cloud resource deployment.<\/span><\/p>\n

      Question 23<\/b><\/h3>\n

      An application deployed on Google Kubernetes Engine needs to expose a group of pods through a stable internal network address. Which Kubernetes resource should be configured?<\/b><\/p>\n

        \n
      1. ConfigMap<\/span><\/li>\n
      2. Secret<\/span><\/li>\n
      3. Service<\/span><\/li>\n
      4. PersistentVolume<\/span><\/li>\n<\/ol>\n

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

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

        A Kubernetes Service provides a stable network abstraction for accessing a set of pods. Because pods can be replaced or recreated with different IP addresses, applications should not depend on individual pod addresses for ongoing communication. A Service selects the relevant pods and provides a consistent endpoint for other workloads within the cluster or, depending on its type, external clients. ConfigMaps store non-sensitive configuration, Secrets hold sensitive configuration data, and PersistentVolumes represent storage resources. A Service is therefore appropriate when an application needs a stable network address for communicating with a group of pods.<\/span><\/p>\n

        Question 24<\/b><\/h3>\n

        A GKE application needs configuration values that can be changed independently of its container image. Which Kubernetes object is intended for non-sensitive configuration data?<\/b><\/p>\n

          \n
        1. ConfigMap<\/span><\/li>\n
        2. PersistentVolume<\/span><\/li>\n
        3. Service<\/span><\/li>\n
        4. Ingress<\/span><\/li>\n<\/ol>\n

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

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

          A Kubernetes ConfigMap stores non-sensitive configuration data separately from application container images. Developers can use ConfigMaps to provide settings such as application modes, feature options, or configuration files to workloads. This separation allows configuration to be updated without rebuilding the application image, although the application may need to reload or restart to consume changed values. Sensitive information should instead be managed using Kubernetes Secrets or an appropriate external secret-management solution. PersistentVolumes provide storage, Services expose workloads through stable networking, and Ingress manages HTTP routing. ConfigMap is the appropriate object for separating ordinary configuration from application code.<\/span><\/p>\n

          Question 25<\/b><\/h3>\n

          A containerized application on GKE requires a persistent disk that remains available when a pod is recreated. Which Kubernetes resource represents a request for persistent storage?<\/b><\/p>\n

            \n
          1. Deployment<\/span><\/li>\n
          2. PersistentVolumeClaim<\/span><\/li>\n
          3. ConfigMap<\/span><\/li>\n
          4. ServiceAccount<\/span><\/li>\n<\/ol>\n

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

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

            A PersistentVolumeClaim (PVC) is a Kubernetes resource through which a workload requests persistent storage with specified requirements, such as capacity and access mode. Kubernetes can bind the claim to a suitable PersistentVolume, which represents the storage resource available to the cluster. This allows applications to retain data beyond the lifecycle of an individual pod, subject to the storage configuration and underlying service behavior. A Deployment manages replicated application pods, a ConfigMap stores non-sensitive settings, and a ServiceAccount provides an identity for workloads. A PVC is therefore the appropriate resource for requesting persistent storage.<\/span><\/p>\n

            Question 26<\/b><\/h3>\n

            A developer needs to ensure that a GKE application maintains a specified number of pod replicas and replaces failed pods. Which Kubernetes object should be used?<\/b><\/p>\n

              \n
            1. Deployment<\/span><\/li>\n
            2. ConfigMap<\/span><\/li>\n
            3. Secret<\/span><\/li>\n
            4. Ingress<\/span><\/li>\n<\/ol>\n

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

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

              A Kubernetes Deployment manages application replicas and supports declarative updates to workloads. It maintains the desired number of pod replicas by creating replacements when existing pods fail or are removed. Deployments also support rollout strategies and revision history, allowing teams to manage application updates in a controlled manner. Developers specify the desired state, and Kubernetes controllers work toward maintaining it. ConfigMaps store non-sensitive configuration, Secrets manage sensitive values, and Ingress defines HTTP or HTTPS routing rules. A Deployment is therefore suitable when an application requires a managed replica count and automated replacement of failed pods.<\/span><\/p>\n

              Question 27<\/b><\/h3>\n

              A GKE application must receive external HTTP traffic through hostname-based routing to different backend services. Which Kubernetes resource is commonly used for this purpose?<\/b><\/p>\n

                \n
              1. PersistentVolumeClaim<\/span><\/li>\n
              2. ConfigMap<\/span><\/li>\n
              3. Ingress<\/span><\/li>\n
              4. Secret<\/span><\/li>\n<\/ol>\n

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

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

                Kubernetes Ingress defines rules for routing HTTP and HTTPS traffic to services within a cluster. It can support hostname-based and path-based routing, allowing a single external entry point to direct requests to different application services. An Ingress resource requires a compatible Ingress controller or implementation to provision and enforce the routing behavior. Developers should also configure TLS and backend services according to application security and networking requirements. PersistentVolumeClaims request storage, ConfigMaps hold non-sensitive configuration, and Secrets store sensitive data. Ingress is therefore appropriate for defining external web traffic routing to Kubernetes services.<\/span><\/p>\n

                Question 28<\/b><\/h3>\n

                A GKE workload needs to access Google Cloud APIs using its own identity rather than a developer’s credentials. Which approach is recommended for associating Kubernetes workloads with Google Cloud IAM identities?<\/b><\/p>\n

                  \n
                1. Workload Identity Federation for GKE<\/span><\/li>\n
                2. Public IP access<\/span><\/li>\n
                3. Shared user passwords<\/span><\/li>\n
                4. Anonymous API requests<\/span><\/li>\n<\/ol>\n

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

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

                  Workload Identity Federation for GKE enables Kubernetes workloads to access supported Google Cloud resources using federated identities and IAM permissions. It avoids distributing long-lived service account keys to application containers and allows administrators to grant access to specific workloads. This supports stronger credential management and more precise authorization. The Kubernetes service account and associated IAM configuration must be set up correctly for the workload’s required APIs. Public IP access does not establish identity, shared passwords create security and accountability risks, and anonymous requests are unsuitable for protected resources. Workload Identity Federation for GKE is therefore the recommended identity approach.<\/span><\/p>\n

                  Question 29<\/b><\/h3>\n

                  A developer needs to store application data in a globally distributed, strongly consistent NoSQL database with automatic scaling. Which Google Cloud service is designed for this use case?<\/b><\/p>\n

                    \n
                  1. Cloud SQL<\/span><\/li>\n
                  2. Cloud Spanner<\/span><\/li>\n
                  3. Cloud Storage<\/span><\/li>\n
                  4. Cloud DNS<\/span><\/li>\n<\/ol>\n

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

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

                    Cloud Spanner is a managed relational database service designed for high availability, horizontal scalability, and strong consistency across distributed deployments. It supports SQL queries and transactions while enabling applications to scale beyond the typical limits of a single database server. Cloud Spanner can be appropriate for globally distributed applications that require relational data modeling and consistent transactional behavior. Cloud SQL provides managed relational databases with different scaling characteristics, Cloud Storage stores objects, and Cloud DNS manages name resolution. Cloud Spanner is therefore suitable when an application needs a globally distributed database with strong consistency and horizontal scalability.<\/span><\/p>\n

                    Question 30<\/b><\/h3>\n

                    A developer is designing a low-latency application that needs to store and retrieve large volumes of time-series or analytical data using a wide-column NoSQL model. Which service should be considered?<\/b><\/p>\n

                      \n
                    1. Cloud Bigtable<\/span><\/li>\n
                    2. Cloud Scheduler<\/span><\/li>\n
                    3. Cloud Build<\/span><\/li>\n
                    4. Cloud Armor<\/span><\/li>\n<\/ol>\n

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

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

                      Cloud Bigtable is a managed, scalable wide-column NoSQL database designed for large workloads that require high throughput and low-latency access. It is commonly used for time-series data, analytical workloads, operational monitoring, and applications that need to process large amounts of structured or semi-structured data. Its data model differs from a traditional relational database, so developers should design row keys and access patterns carefully to support efficient queries. Cloud Scheduler handles scheduled jobs, Cloud Build automates build workflows, and Cloud Armor provides application security. Cloud Bigtable is appropriate for high-volume, low-latency wide-column data workloads.<\/span><\/p>\n

                      Question 31<\/b><\/h3>\n

                      A developer wants to deploy a new application version to GKE while gradually replacing existing pods and maintaining application availability. Which Kubernetes deployment strategy is appropriate?<\/b><\/p>\n

                        \n
                      1. Rolling update<\/span><\/li>\n
                      2. Delete all resources<\/span><\/li>\n
                      3. Manual database export<\/span><\/li>\n
                      4. Disable health checks<\/span><\/li>\n<\/ol>\n

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

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

                        A rolling update replaces existing application pods gradually with pods running the new version. Kubernetes Deployments support this strategy through update parameters that control how many pods can be unavailable or created during a rollout. When configured appropriately, rolling updates help maintain application availability while introducing new software. Developers should use readiness probes and monitor rollout progress to detect problems before all replicas are updated. Deleting all resources can cause avoidable downtime, manual database export does not control application rollout, and disabling health checks reduces operational visibility. A rolling update is therefore suitable for gradual application version replacement.<\/span><\/p>\n

                        Question 32<\/b><\/h3>\n

                        A containerized application must be packaged consistently so it can run in development, testing, and production environments. Which artifact should the developer create?<\/b><\/p>\n

                          \n
                        1. Container image<\/span><\/li>\n
                        2. DNS zone<\/span><\/li>\n
                        3. IAM policy<\/span><\/li>\n
                        4. Monitoring dashboard<\/span><\/li>\n<\/ol>\n

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

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

                          A container image packages an application and its required runtime dependencies into a portable artifact. This helps maintain consistency across development, testing, and production because each environment can run the same built image while supplying environment-specific configuration separately. Images can be versioned, scanned, stored in Artifact Registry, and deployed to services such as Cloud Run or GKE. A DNS zone manages domain records, an IAM policy controls access, and a monitoring dashboard displays operational information. A container image is therefore the appropriate artifact for packaging an application consistently across deployment environments.<\/span><\/p>\n

                          Question 33<\/b><\/h3>\n

                          A developer needs to automatically build and deploy a container image whenever a change is pushed to a source repository. Which capability should be configured?<\/b><\/p>\n

                            \n
                          1. Cloud Build trigger<\/span><\/li>\n
                          2. Cloud DNS record<\/span><\/li>\n
                          3. Cloud Storage lifecycle rule<\/span><\/li>\n
                          4. Cloud Monitoring dashboard<\/span><\/li>\n<\/ol>\n

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

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

                            A Cloud Build trigger can initiate a build workflow when a configured source repository event occurs, such as a code push or pull request update. The build configuration can run tests, compile the application, build a container image, and publish the artifact to a registry. Additional deployment steps can then release the image to a supported runtime environment. Triggers help standardize continuous integration and delivery processes, reducing reliance on manual execution. DNS records resolve hostnames, storage lifecycle rules manage object retention, and monitoring dashboards display metrics. A Cloud Build trigger is therefore appropriate for repository-driven automated builds.<\/span><\/p>\n

                            Question 34<\/b><\/h3>\n

                            A developer wants to deploy application revisions to Cloud Run while retaining the ability to direct traffic between versions. Which Cloud Run feature supports this?<\/b><\/p>\n

                              \n
                            1. Revisions<\/span><\/li>\n
                            2. PersistentVolumeClaims<\/span><\/li>\n
                            3. ConfigMaps<\/span><\/li>\n
                            4. DNSSEC<\/span><\/li>\n<\/ol>\n

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

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

                              Cloud Run creates revisions when a service is updated with a new configuration or container image. Each revision represents a specific version of the service and can be managed independently within the service’s revision history. Developers can use traffic allocation features to direct requests to selected revisions, supporting controlled rollouts and rollback scenarios. Revision-based deployment helps teams observe a new version before routing all traffic to it. PersistentVolumeClaims and ConfigMaps are Kubernetes resources, while DNSSEC is a DNS security extension. Cloud Run revisions are therefore the relevant feature for managing and directing traffic among application versions.<\/span><\/p>\n

                              Question 35<\/b><\/h3>\n

                              A developer needs to ensure a Cloud Run service accepts requests only from authenticated callers with authorized identities. Which control should be configured?<\/b><\/p>\n

                                \n
                              1. IAM-based authentication<\/span><\/li>\n
                              2. Public unauthenticated access<\/span><\/li>\n
                              3. Disable identity checks<\/span><\/li>\n
                              4. Store credentials in application logs<\/span><\/li>\n<\/ol>\n

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

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

                                Cloud Run supports IAM-based access control, allowing developers to restrict invocation to identities that have the required permissions. This is useful for internal APIs, service-to-service communication, and applications that should not be publicly accessible. The calling identity must be authenticated and granted the appropriate invocation permission. Developers should also ensure that application-level authorization is implemented when requests require finer-grained access decisions. Public unauthenticated access removes the invocation restriction, disabling identity checks weakens security, and logging credentials can expose secrets. IAM-based authentication is therefore appropriate for controlling which identities may invoke a Cloud Run service.<\/span><\/p>\n

                                Question 36<\/b><\/h3>\n

                                A developer wants to reduce repeated database queries for frequently requested, relatively stable application data. Which Google Cloud service can provide a managed in-memory caching layer?<\/b><\/p>\n

                                  \n
                                1. Memorystore<\/span><\/li>\n
                                2. Cloud DNS<\/span><\/li>\n
                                3. Cloud Build<\/span><\/li>\n
                                4. Cloud Armor<\/span><\/li>\n<\/ol>\n

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

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

                                  Memorystore provides managed in-memory data stores, including Redis and Memcached offerings, that applications can use for caching and other low-latency data access patterns. By caching frequently requested information, an application may reduce repeated database queries and improve response times, provided the cache is designed with appropriate expiration and invalidation behavior. Developers should account for cache consistency, memory limits, and failure handling. Cloud DNS manages name resolution, Cloud Build automates software builds, and Cloud Armor provides application protection. Memorystore is therefore a relevant service when an application needs a managed in-memory caching layer.<\/span><\/p>\n

                                  Question 37<\/b><\/h3>\n

                                  A developer wants to route application logs to a centralized destination for searching, filtering, and troubleshooting across Google Cloud services. Which service should be used?<\/b><\/p>\n

                                    \n
                                  1. Cloud Logging<\/span><\/li>\n
                                  2. Cloud Scheduler<\/span><\/li>\n
                                  3. Cloud NAT<\/span><\/li>\n
                                  4. Cloud CDN<\/span><\/li>\n<\/ol>\n

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

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

                                    Cloud Logging collects and manages log data from Google Cloud services and supported application integrations. Developers can search, filter, analyze, and route logs to support troubleshooting, auditing, and operational monitoring. Structured application logs with meaningful severity levels and contextual fields can make investigations more efficient. Log-based metrics and alerting integrations can also help teams identify recurring errors or unusual behavior. Cloud Scheduler triggers scheduled jobs, Cloud NAT provides outbound connectivity, and Cloud CDN caches content. Cloud Logging is therefore the appropriate service for centralized application and infrastructure log management.<\/span><\/p>\n

                                    Question 38<\/b><\/h3>\n

                                    A developer needs to investigate an application crash by examining error events, stack traces, and associated diagnostic information. Which Google Cloud service is designed to group and analyze application errors?<\/b><\/p>\n

                                      \n
                                    1. Error Reporting<\/span><\/li>\n
                                    2. Cloud DNS<\/span><\/li>\n
                                    3. Cloud Storage<\/span><\/li>\n
                                    4. Cloud NAT<\/span><\/li>\n<\/ol>\n

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

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

                                      Error Reporting helps developers identify, group, and analyze application errors reported through supported Google Cloud integrations. It can organize recurring exceptions and provide diagnostic details that help teams investigate failures without manually searching every log entry. When combined with Cloud Logging and monitoring practices, it contributes to a more complete application observability workflow. Developers should still inspect relevant logs, reproduce failures where possible, and validate fixes through testing. Cloud DNS manages domain resolution, Cloud Storage stores objects, and Cloud NAT provides network translation. Error Reporting is therefore suitable for tracking and investigating application exceptions.<\/span><\/p>\n

                                      Question 39<\/b><\/h3>\n

                                      A developer wants to automate deployment to Google Cloud using a declarative release process with defined targets and promotion stages. Which service is designed for managed continuous delivery?<\/b><\/p>\n

                                        \n
                                      1. Cloud Deploy<\/span><\/li>\n
                                      2. Cloud Trace<\/span><\/li>\n
                                      3. Cloud DNS<\/span><\/li>\n
                                      4. Secret Manager<\/span><\/li>\n<\/ol>\n

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

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

                                        Cloud Deploy is a managed continuous delivery service for deploying applications to supported runtime targets, including Google Kubernetes Engine and Cloud Run. It supports delivery pipelines, release creation, promotion between targets, and deployment progress tracking. This helps teams standardize release processes and separate application build activities from controlled deployment stages. Developers can integrate Cloud Deploy with build systems and artifact repositories to create a consistent software delivery workflow. Cloud Trace supports distributed tracing, Cloud DNS manages domain records, and Secret Manager stores sensitive values. Cloud Deploy is therefore appropriate for managing structured application release and promotion processes.<\/span><\/p>\n

                                        Question 40<\/b><\/h3>\n

                                        A developer is designing an application that must remain available if one zone experiences a failure. Which deployment approach can improve resilience for a GKE workload?<\/b><\/p>\n

                                          \n
                                        1. Run all replicas in one zone<\/span><\/li>\n
                                        2. Deploy replicas across multiple zones<\/span><\/li>\n
                                        3. Disable health checks<\/span><\/li>\n
                                        4. Store all application state in a single pod<\/span><\/li>\n<\/ol>\n

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

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

                                          Deploying application replicas across multiple zones can improve resilience by reducing dependence on a single zone. If one zone becomes unavailable, workloads in other zones may continue serving requests, provided the cluster, networking, storage, and application architecture are configured to support that behavior. Developers should also use suitable health checks, disruption controls, capacity planning, and resilient data services. Running all replicas in one zone creates a larger zone-level failure risk, disabling health checks reduces failure detection, and storing all state in one pod creates a single point of failure. Multi-zone deployment is therefore an important resilience strategy for GKE workloads.<\/span><\/p>\n

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

                                          View Full Google Professional Cloud Developer Exam Dumps and Practice Test Dumps.   Question 21 A developer is building a service that must process HTTP requests and automatically scale based on incoming traffic. The application is packaged as a container. Which deployment option is suitable? Cloud Storage Cloud Run Cloud DNS Cloud Scheduler Correct Answer: […]<\/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\/23446"}],"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=23446"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/23446\/revisions"}],"predecessor-version":[{"id":23447,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/23446\/revisions\/23447"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=23446"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=23446"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=23446"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}