{"name":"user. normal. authorize","uri":"http:\/\/legacy-a pi. us. market. zdn\/api\/{version}\/api_account\/d eprecated_authorize","protocol":"le gacy"},{"name":"user. fb. authorize","uri":"http:\/\/legacy-a pi. us. market. zdn\/api\/{version}\/api_account\/d eprecated_authorize_fb","protocol": "legacy"},{"name":"user. fb. register","uri":"http:\/\/legacy-ap i. us. market. zdn\/api\/{version}\/api_account\/d eprecated_register_fb","protocol":" legacy"},{"name":"user. fb. merge","uri":"http:\/\/legacy-

Answer b would be a good url

Solution: the categorization of functional and non-functional requirement are as follows: some of the more typical functional requirements include: • business rules• transaction corrections, adjustments and cancellations• administrative functions• authentication• authorization levels• audit tracking• external interfaces• certification requirements• reporting requirements• historical data• legal or regulatory requirementswhile,some typical non-functional requirements are: • performance – for example response time, throughput, utilization, static volumetric• scalability• capacity• availability• reliability• recoverability• maintainability• serviceability• security• regulatory• manageability• environmental• data integrity• usability• interoperability