A secure paved-road architecture provides development teams with approved, reusable engineering patterns that incorporate security controls into the standard software delivery process.
Option A combines several complementary capabilities necessary for achieving this objective.
Open Policy Agent (OPA) provides policy-as-code enforcement, allowing organizations to evaluate deployment configurations, infrastructure definitions, and application policies against centrally maintained rules.
Versioned architecture blueprints establish repeatable infrastructure and application patterns while supporting change tracking, review, and controlled updates.
Standardized CI/CD templates provide consistent build, testing, security validation, and deployment processes across development teams.
Requiring an approved vault service supports secure management of application credentials, API keys, and other sensitive information without embedding secrets directly into source code.
Together, these capabilities make secure implementation patterns easier to adopt and harder to bypass.
Option B includes valuable infrastructure automation and static analysis but lacks the broader policy enforcement and standardized architectural governance described in option A.
Option C relies partly on recommendations and permits inconsistent enforcement.
Option D depends heavily on documentation and manual reviews, limiting scalability and consistency.
An effective paved-road implementation should also incorporate automated compliance checks, clearly defined exception procedures, and ongoing template maintenance.
Official reference / study topic: Open Policy Agent, OPA in CI/CD Pipelines and Policy-as-Code Enforcement.
===============
Submit