{"id":15411,"date":"2026-09-17T12:45:58","date_gmt":"2026-09-17T12:45:58","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=15411"},"modified":"2026-09-17T13:03:10","modified_gmt":"2026-09-17T13:03:10","slug":"microsoft-mb-700-practice-test-questions-and-exam-dumps-part20-q381-400","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/microsoft-mb-700-practice-test-questions-and-exam-dumps-part20-q381-400\/","title":{"rendered":"Microsoft MB-700 Practice Test Questions and Exam Dumps Part20 Q381-400"},"content":{"rendered":"

<\/h1>\n

View Full\u00a0<\/b> Microsoft MB-700 Exam Dumps <\/b><\/a>and Practice Test Dumps<\/b><\/h2>\n

 <\/p>\n

Question 381.<\/b><\/p>\n

A company wants to reduce risk when implementing a new integration between Dynamics 365 and an external application. What should the solution architect define first?<\/b><\/p>\n

    \n
  1. <\/b> Business requirements, data ownership, latency, and volume<\/span>
    \n<\/span>2.<\/b> User interface colors<\/span>
    \n<\/span>3.<\/b> Office working hours<\/span>
    \n<\/span>4.<\/b> Printer configuration<\/span><\/li>\n<\/ol>\n

    Correct Answer: 1. Business requirements, data ownership, latency, and volume<\/b><\/p>\n

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

    Integration design should begin with the business process and workload requirements rather than with technology selection. The architect should understand what data must move, which system owns it, how quickly it must be available, expected transaction volumes, and what should happen when processing fails. These factors determine whether synchronous, asynchronous, batch, or event-driven integration is appropriate. Security, monitoring, retries, and support ownership should also be considered. Defining these requirements first helps prevent overengineering and ensures that the selected integration pattern is reliable, scalable, and aligned with actual business needs.<\/span><\/p>\n

    Question 382.<\/b><\/p>\n

    A company wants to prevent developers from deploying untested changes directly to production. What should the architect recommend?<\/b><\/p>\n

      \n
    1. <\/b> Shared administrator accounts<\/span>
      \n<\/span>2.<\/b> A controlled ALM process with testing and approvals<\/span>
      \n<\/span>3.<\/b> Development directly in production<\/span>
      \n<\/span>4.<\/b> Manual copying without version control<\/span><\/li>\n<\/ol>\n

      Correct Answer: 2. A controlled ALM process with testing and approvals<\/b><\/p>\n

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

      Application lifecycle management should provide a structured path for changes from development through testing and into production. The process should include source control, builds, validation, approvals, deployment governance, and appropriate permissions. Restricting direct production access helps prevent accidental or unauthorized changes. Testing should occur in suitable non-production environments before release. Manual file copying and shared accounts weaken traceability and increase deployment risk. A controlled ALM process improves consistency, auditability, and production stability while allowing teams to identify exactly which version of the solution has been deployed.<\/span><\/p>\n

      Question 383.<\/b><\/p>\n

      A company wants to ensure that customer data remains consistent across Dynamics 365 and three external applications. What should the solution architect establish?<\/b><\/p>\n

        \n
      1. <\/b> Independent customer definitions in each system<\/span>
        \n<\/span>2.<\/b> Manual reconciliation only<\/span>
        \n<\/span>3.<\/b> Authoritative ownership, shared identifiers, and synchronization rules<\/span>
        \n<\/span>4.<\/b> Unrestricted updates from all systems<\/span><\/li>\n<\/ol>\n

        Correct Answer: 3. Authoritative ownership, shared identifiers, and synchronization rules<\/b><\/p>\n

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

        Consistent customer data requires clear ownership and synchronization rules. The architect should establish which system is authoritative for each entity or attribute, define shared identifiers, and document how updates move between applications. Validation, duplicate detection, and conflict-resolution behavior should also be considered. Without this governance, different systems may overwrite one another or maintain conflicting versions of the same customer. A common data strategy improves reporting, integrations, and operational accuracy. It also reduces the amount of manual reconciliation needed across the enterprise application landscape.<\/span><\/p>\n

        Question 384.<\/b><\/p>\n

        A business process can tolerate delayed processing if an external service becomes temporarily unavailable. Which integration approach should the architect consider?<\/b><\/p>\n

          \n
        1. <\/b> Synchronous blocking only<\/span>
          \n<\/span>2.<\/b> Direct database writes<\/span>
          \n<\/span>3.<\/b> Manual processing<\/span>
          \n<\/span>4.<\/b> Asynchronous queue-based processing**<\/span><\/li>\n<\/ol>\n

          Correct Answer: 4. Asynchronous queue-based processing<\/b><\/p>\n

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

          Asynchronous queue-based processing allows the source system to continue working even when the destination is temporarily unavailable. Transactions can be stored safely and processed once the external service becomes available again. The architect should include retries, monitoring, duplicate protection, and recovery procedures. This approach reduces tight runtime dependencies and improves resilience. Synchronous processing is more appropriate when an immediate response is essential, but it is unnecessary when the business can tolerate some delay. Queue-based processing provides a reliable pattern for handling temporary outages without losing transactions.<\/span><\/p>\n

          Question 385.<\/b><\/p>\n

          A company wants to reduce technical debt in its Dynamics 365 implementation. What should the architect review first?<\/b><\/p>\n

            \n
          1. <\/b> Existing customizations that may now be replaced by standard functionality<\/span>
            \n<\/span>2.<\/b> Office network layout<\/span>
            \n<\/span>3.<\/b> User monitor specifications<\/span>
            \n<\/span>4.<\/b> Printer hardware<\/span><\/li>\n<\/ol>\n

            Correct Answer: 1. Existing customizations that may now be replaced by standard functionality<\/b><\/p>\n

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

            Customizations should be periodically reviewed because Dynamics 365 continues to add standard capabilities. A feature that once required custom code may now be supported natively. Replacing unnecessary customization with standard functionality can reduce maintenance, regression testing, upgrade risk, and overall technical debt. The architect should still evaluate dependencies, user impact, integrations, and data before retiring any component. Custom code that remains necessary should follow supported extension patterns and have clear ownership. Simplifying the solution over time improves maintainability and long-term supportability.<\/span><\/p>\n

            Question 386.<\/b><\/p>\n

            A company wants to ensure that users can perform their assigned tasks but cannot access unrelated administrative functions. Which security principle should be applied?<\/b><\/p>\n

              \n
            1. <\/b> Shared access<\/span>
              \n<\/span>2.<\/b> Least privilege<\/span>
              \n<\/span>3.<\/b> Anonymous authentication<\/span>
              \n<\/span>4.<\/b> Full administrator access<\/span><\/li>\n<\/ol>\n

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

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

              Least privilege means users receive only the permissions required for their responsibilities. The architect should design security roles around business duties and avoid granting administrative access unless it is genuinely needed. Legal-entity scope, sensitive information, and segregation-of-duties conflicts should also be considered. Security testing should verify both allowed and denied actions for representative user personas. Excessive permissions increase the risk of unauthorized transactions, configuration changes, and data exposure. Applying least privilege helps create a more secure and manageable Dynamics 365 environment.<\/span><\/p>\n

              Question 387.<\/b><\/p>\n

              A company plans to migrate data from several legacy systems. What should be completed before final production migration?<\/b><\/p>\n

                \n
              1. <\/b> Source-system shutdown<\/span>
                \n<\/span>2.<\/b> Permanent removal of validation<\/span>
                \n<\/span>3.<\/b> Trial migrations, cleansing, mapping, and reconciliation<\/span>
                \n<\/span>4.<\/b> Immediate deletion of historical records<\/span><\/li>\n<\/ol>\n

                Correct Answer: 3. Trial migrations, cleansing, mapping, and reconciliation<\/b><\/p>\n

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

                A production migration should be preceded by multiple rehearsals using realistic data volumes. The team should cleanse source data, map fields, validate transformations, and reconcile results using agreed business control totals. Trial migrations also reveal processing-time issues and hidden dependencies. Errors should be corrected before final cutover, and recovery procedures should be documented. Deleting source systems or disabling validation too early introduces unnecessary risk. A repeatable, tested migration process provides greater confidence that production data can be transferred accurately and within the planned cutover window.<\/span><\/p>\n

                Question 388.<\/b><\/p>\n

                An integration sometimes receives the same transaction multiple times because of retry behavior. What should the architect implement?<\/b><\/p>\n

                  \n
                1. <\/b> Manual review of every transaction<\/span>
                  \n<\/span>2.<\/b> Removal of retry logic<\/span>
                  \n<\/span>3.<\/b> Shared service accounts<\/span>
                  \n<\/span>4.<\/b> Idempotent processing and duplicate detection**<\/span><\/li>\n<\/ol>\n

                  Correct Answer: 4. Idempotent processing and duplicate detection<\/b><\/p>\n

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

                  Retries are important for resilient integrations, but repeated delivery should not create duplicate orders, invoices, payments, or other business records. Idempotent processing enables the same logical transaction to be processed more than once without creating unintended duplicates. The design can use unique identifiers, transaction keys, or duplicate checks. Monitoring and reconciliation should also be included. Removing retries would reduce resilience, while manual review would not scale for enterprise workloads. Duplicate protection should be built into the integration architecture from the beginning.<\/span><\/p>\n

                  Question 389.<\/b><\/p>\n

                  A company wants to improve consistency when promoting changes through development, test, and production environments. What should the architect recommend?<\/b><\/p>\n

                    \n
                  1. <\/b> Standardized deployment pipelines and release procedures<\/span>
                    \n<\/span>2.<\/b> Manual copying by individual developers<\/span>
                    \n<\/span>3.<\/b> Different deployment methods for each team<\/span>
                    \n<\/span>4.<\/b> Direct editing in production<\/span><\/li>\n<\/ol>\n

                    Correct Answer: 1. Standardized deployment pipelines and release procedures<\/b><\/p>\n

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

                    Standardized deployment processes improve repeatability and reduce errors when changes move between environments. Automation can be used where appropriate to package and deploy approved changes consistently. The process should remain integrated with source control, testing, approvals, and rollback or recovery planning. Different deployment methods for each team can create inconsistencies and make troubleshooting difficult. Direct production editing should be minimized because it can create environment drift. A common release approach improves traceability, reliability, and confidence in the application lifecycle.<\/span><\/p>\n

                    Question 390.<\/b><\/p>\n

                    A company wants complex analytics to run without affecting critical Dynamics 365 transactions. What should the solution architect consider?<\/b><\/p>\n

                      \n
                    1. <\/b> Running all analytics directly against operational workloads<\/span>
                      \n<\/span>2.<\/b> Separating analytical workloads onto an appropriate data platform<\/span>
                      \n<\/span>3.<\/b> Giving analysts administrator access<\/span>
                      \n<\/span>4.<\/b> Disabling all reporting<\/span><\/li>\n<\/ol>\n

                      Correct Answer: 2. Separating analytical workloads onto an appropriate data platform<\/b><\/p>\n

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

                      Complex analytical workloads can consume resources required for interactive business transactions. The architect should evaluate whether reporting and historical analysis should use a separate analytical platform or replicated dataset. The design should consider freshness, security, transformation, query volume, and retention requirements. Operational reports may still need current transactional data, but strategic analytics often benefit from workload separation. This approach can improve scalability and protect critical transaction performance while still providing rich analytical capabilities. Reporting architecture should balance business insight needs with system efficiency.<\/span><\/p>\n

                      Question 391.<\/b><\/p>\n

                      A company is evaluating a third-party solution for a critical Dynamics 365 process. What should the architect assess first?<\/b><\/p>\n

                        \n
                      1. <\/b> Functional fit with the business requirement<\/span>
                        \n<\/span>2.<\/b> Product logo design<\/span>
                        \n<\/span>3.<\/b> Vendor office size<\/span>
                        \n<\/span>4.<\/b> Interface font<\/span><\/li>\n<\/ol>\n

                        Correct Answer: 1. Functional fit with the business requirement<\/b><\/p>\n

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

                        The architect should first determine whether the third-party solution actually satisfies the required business capability. After functional fit is confirmed, the evaluation should include integration, security, performance, licensing, vendor support, update compatibility, and long-term lifecycle impact. A product that does not meet the core requirement should not move forward regardless of appearance or marketing. A structured assessment helps ensure that the ISV solution fits the wider Dynamics 365 architecture and can be supported reliably throughout its expected lifecycle.<\/span><\/p>\n

                        Question 392.<\/b><\/p>\n

                        A finance department wants to prevent users from creating vendors and approving payments to those vendors. What should the architect review?<\/b><\/p>\n

                          \n
                        1. <\/b> User-interface settings<\/span>
                          \n<\/span>2.<\/b> Training attendance<\/span>
                          \n<\/span>3.<\/b> Segregation-of-duties conflicts<\/span>
                          \n<\/span>4.<\/b> Device inventory<\/span><\/li>\n<\/ol>\n

                          Correct Answer: 3. Segregation-of-duties conflicts<\/b><\/p>\n

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

                          Segregation of duties is designed to prevent a single user from performing incompatible activities that could create fraud or control risks. Vendor creation and payment approval are a common example. The architect should work with business and compliance stakeholders to define important conflicts and structure security roles accordingly. Any exceptions should be documented, approved, and monitored. This analysis should be combined with least privilege and representative security testing. Reviewing conflicts before go-live strengthens internal controls and reduces financial and compliance risk.<\/span><\/p>\n

                          Question 393.<\/b><\/p>\n

                          A company wants to retire a legacy application while preserving historical records required for audits. What should the architect recommend?<\/b><\/p>\n

                            \n
                          1. <\/b> Delete all historical records<\/span>
                            \n<\/span>2.<\/b> Keep the application running forever<\/span>
                            \n<\/span>3.<\/b> Export data to personal spreadsheets<\/span>
                            \n<\/span>4.<\/b> Implement a governed archival and retrieval solution**<\/span><\/li>\n<\/ol>\n

                            Correct Answer: 4. Implement a governed archival and retrieval solution<\/b><\/p>\n

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

                            Historical records may remain necessary for audit, compliance, legal, or reporting purposes after the legacy application is retired. The architect should design an archival solution that preserves required data, retention periods, security, and retrieval capabilities. The archive should be validated before the old system is shut down. Keeping the legacy application indefinitely can increase cost and security risk, while uncontrolled spreadsheets are not suitable for enterprise retention. A governed archive enables decommissioning while ensuring that required historical information remains accessible to authorized users.<\/span><\/p>\n

                            Question 394.<\/b><\/p>\n

                            A company wants to reduce configuration drift between environments. What should the architect recommend?<\/b><\/p>\n

                              \n
                            1. <\/b> Controlled configuration promotion and documentation<\/span>
                              \n<\/span>2.<\/b> Untracked production edits<\/span>
                              \n<\/span>3.<\/b> Different configuration standards for each environment<\/span>
                              \n<\/span>4.<\/b> Shared administrator accounts<\/span><\/li>\n<\/ol>\n

                              Correct Answer: 1. Controlled configuration promotion and documentation<\/b><\/p>\n

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

                              Configuration should be managed as part of the application lifecycle. Changes should be documented, tested, approved, and promoted consistently through development, test, and production environments. This helps keep environments aligned and ensures that testing reflects what will ultimately be deployed. Direct production edits can create differences that are difficult to reproduce and troubleshoot. The architect should define ownership and procedures for configuration movement. Strong configuration management improves release quality and makes future support and troubleshooting more predictable.<\/span><\/p>\n

                              Question 395.<\/b><\/p>\n

                              A company wants support teams to trace a transaction across several integrated systems. What should the architect include?<\/b><\/p>\n

                                \n
                              1. <\/b> Correlation identifiers and end-to-end logging<\/span>
                                \n<\/span>2.<\/b> No diagnostic logs<\/span>
                                \n<\/span>3.<\/b> Shared administrator passwords<\/span>
                                \n<\/span>4.<\/b> Manual searching only<\/span><\/li>\n<\/ol>\n

                                Correct Answer: 1. Correlation identifiers and end-to-end logging<\/b><\/p>\n

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

                                Correlation identifiers allow the same business transaction to be traced across multiple systems and processing stages. When combined with meaningful logs and monitoring, they help support teams quickly determine where a failure occurred and which records were affected. Logs should provide enough information for troubleshooting without exposing unnecessary sensitive data. Manual searching without common identifiers can be slow and unreliable. End-to-end observability is particularly valuable in complex integration landscapes where one transaction may pass through several services before completion.<\/span><\/p>\n

                                Question 396.<\/b><\/p>\n

                                A company is deciding whether to defer a complex feature from the first production release. What should drive the decision?<\/b><\/p>\n

                                  \n
                                1. <\/b> The order in which it was requested<\/span>
                                  \n<\/span>2.<\/b> Business value, risk, dependencies, and impact on readiness<\/span>
                                  \n<\/span>3.<\/b> Developer preference<\/span>
                                  \n<\/span>4.<\/b> The length of the specification<\/span><\/li>\n<\/ol>\n

                                  Correct Answer: 2. Business value, risk, dependencies, and impact on readiness<\/b><\/p>\n

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

                                  Release scope should be prioritized based on business value and delivery risk. The architect should assess how the feature affects integrations, migration, security, testing, performance, and overall go-live readiness. A low-value feature with significant complexity may be better deferred, while a difficult requirement may need to remain if it supports critical operations or compliance. Structured prioritization helps stakeholders understand trade-offs and prevents optional complexity from threatening the stability of the initial release. The decision should be based on measurable value rather than personal preference.<\/span><\/p>\n

                                  Question 397.<\/b><\/p>\n

                                  A company wants to verify that an integration recovers correctly after an external-service outage. What should the test plan include?<\/b><\/p>\n

                                    \n
                                  1. <\/b> Simulated failures, retries, recovery, and duplicate prevention<\/span>
                                    \n<\/span>2.<\/b> Successful transactions only<\/span>
                                    \n<\/span>3.<\/b> User-interface testing only<\/span>
                                    \n<\/span>4.<\/b> No testing because retry logic exists<\/span><\/li>\n<\/ol>\n

                                    Correct Answer: 1. Simulated failures, retries, recovery, and duplicate prevention<\/b><\/p>\n

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

                                    Resilience testing should simulate conditions such as unavailable endpoints, network timeouts, failed authentication, and temporary service interruptions. The team should confirm that retry logic behaves correctly, messages are not lost, duplicate transactions are prevented, and processing resumes after service restoration. Monitoring and alerts should also be validated. Testing only successful scenarios cannot demonstrate how the integration behaves under real failure conditions. Verifying recovery before production reduces operational risk and ensures that support teams understand how to respond when external dependencies fail.<\/span><\/p>\n

                                    Question 398.<\/b><\/p>\n

                                    A company wants to use production-like data in non-production environments without unnecessarily exposing sensitive information. What should the architect recommend?<\/b><\/p>\n

                                      \n
                                    1. <\/b> Copy all production data without controls<\/span>
                                      \n<\/span>2.<\/b> Use masking, anonymization, and restricted access where appropriate<\/span>
                                      \n<\/span>3.<\/b> Disable test-environment security<\/span>
                                      \n<\/span>4.<\/b> Store data on personal devices<\/span><\/li>\n<\/ol>\n

                                      Correct Answer: 2. Use masking, anonymization, and restricted access where appropriate<\/b><\/p>\n

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

                                      Production-like datasets can improve test quality, but sensitive information must remain protected. The architect should determine whether masking or anonymization is necessary and restrict access to users with legitimate needs. Retention, disposal, and privacy requirements should also be considered. Non-production environments should not become uncontrolled repositories of confidential customer, employee, or financial information. A secure data-handling strategy supports realistic testing while reducing security and compliance risk. Data protection should apply throughout the full application lifecycle, not only in production.<\/span><\/p>\n

                                      Question 399.<\/b><\/p>\n

                                      A company plans to modify a shared API contract used by several applications. What should the architect do first?<\/b><\/p>\n

                                        \n
                                      1. <\/b> Change the contract immediately<\/span>
                                        \n<\/span>2.<\/b> Ignore current consumers<\/span>
                                        \n<\/span>3.<\/b> Perform impact analysis and compatibility assessment<\/span>
                                        \n<\/span>4.<\/b> Remove regression testing<\/span><\/li>\n<\/ol>\n

                                        Correct Answer: 3. Perform impact analysis and compatibility assessment<\/b><\/p>\n

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

                                        Changes to a shared API contract can affect many consumers. The architect should identify every dependent application and determine whether schemas, authentication, response behavior, timing, or error handling will change. Backward compatibility and versioning should be considered where consumers cannot update at the same time. Regression testing should validate critical scenarios before release. Changing a shared contract without understanding dependencies can cause widespread production failures. Impact analysis allows the service to evolve in a controlled way while protecting existing business processes.<\/span><\/p>\n

                                        Question 400.<\/b><\/p>\n

                                        A Dynamics 365 implementation is ready for final production deployment. What should the solution architect confirm before approving go-live?<\/b><\/p>\n

                                          \n
                                        1. <\/b> Every optional feature has been completed<\/span>
                                          \n<\/span>2.<\/b> All users have administrator access<\/span>
                                          \n<\/span>3.<\/b> All previous project issues have been deleted<\/span>
                                          \n<\/span>4.<\/b> Critical testing, migration, security, support, cutover, and risk criteria have been reviewed**<\/span><\/li>\n<\/ol>\n

                                          Correct Answer: 4. Critical testing, migration, security, support, cutover, and risk criteria have been reviewed<\/b><\/p>\n

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

                                          Final go-live approval should be based on comprehensive business and technical readiness. The team should confirm that critical testing is complete, migration and reconciliation procedures are ready, security has been validated, integrations are operational, and support teams understand monitoring and recovery. The cutover plan should include owners, timing, checkpoints, and contingency actions. Remaining risks and defects should be documented and either resolved or formally accepted by appropriate stakeholders. A structured readiness review ensures that production deployment proceeds because the organization is prepared, not simply because the planned date has arrived.<\/span><\/p>\n

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

                                          View Full\u00a0 Microsoft MB-700 Exam Dumps and Practice Test Dumps   Question 381. A company wants to reduce risk when implementing a new integration between Dynamics 365 and an external application. What should the solution architect define first? Business requirements, data ownership, latency, and volume 2. User interface colors 3. Office working hours 4. Printer […]<\/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\/15411"}],"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=15411"}],"version-history":[{"count":2,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/15411\/revisions"}],"predecessor-version":[{"id":15433,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/15411\/revisions\/15433"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=15411"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=15411"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=15411"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}