An auto parts company wants to protect the path /parts/suspension/struts/manufacturer. Resources appear under an application Context Root of /parts…

In PingAccess, once the application context-root (/parts) is stripped, the remaining request path is /suspension/struts/manufacturer.

With default ordering, the policy engine chooses the “most specific” resource—i.e., the pattern with the greatest number of explicit path segments and the fewest wildcards.

Among the candidates:

• /suspension/struts/manufacturer contains four fixed segments and no wildcards.

• //struts/manufacturer and //manufacturer both contain multi-segment wildcards (//).

• ///manufacturer contains two wildcards.

Because /suspension/struts/manufacturer is the longest exact match and has zero wildcards, it outranks the others, so the policy engine selects it.

A. //struts/manufacturer – Matches, but wildcard (//) makes it less specific than the exact path; loses in default ordering.

B. //manufacturer – Wildcard plus only one fixed segment; lower specificity than both A and C.

D. ///manufacturer – Two consecutive wildcards; lowest specificity of all candidates.

1. Ping Identity. “PingAccess Administrator Guide 9.3,” Section “Resource Path Patterns → Evaluation Order,” pp. 220-223: “The resource with the greatest number of explicit path segments and the fewest wildcards is chosen.”

2. Ping Identity. “PingAccess 9.3 – Defining Resources,” Example table “/foo/bar vs //bar,” p. 225.

3. Ping Identity. “PingAccess 8.3 Administrator Guide,” Appendix A, “Wildcard Matching Rules,” p. 310 (rules for // multi-segment wildcard).