Scaled Agile SAFe-RTE Exam Actual Questions
SAFe Release Train Engineer (Page 8 )

Simple explanation

• The Azure VPN gateway to connect to
• Authentication settings
• Routes for networks that the client can access

• Alice is co-resident on the same physical host and exploits shared hardware (the processor cache) to infer secrets. This is the classic definition of a side-channel attack—information leakage through implementation details (like timing or cache behavior) rather than by breaking a protocol or injecting code.

• Observing cache timing or access patterns to deduce cryptographic keys or plaintext data from the victim VM.

• Man-in-the-cloud attack: targets cloud trust/auth, not local hardware sharing.
• SQL injection: exploits input to run SQL commands, not a VM/caching vector.
• Service hijacking: takes control of a service, not about covert data leakage via shared hardware.

• Notice phrases like “shared hardware resources,” “co-resident,” or “cache”—these indicate a side-channel vector.

• Active vs passive: Active assessment involves actively scanning targets by sending probes/packets to identify hosts, services, and vulnerabilities. Passive assessment observes traffic without probing.
• External vs internal: External assessment is about testing from outside the network perimeter; the scenario doesn’t specify external vantage, only that tools are identifying hosts/services across the enterprise network.

• Correct answer: Day 3 (Option B)

• Why: In Engagement Studio, when the program is paused, the prospects’ wait times are also paused and do not count down. They resume from the same point when the program restarts. Here, the prospect was at day 3 of a 5-day wait when paused, so they resume on day 3 after the 1-day pause.

• The 99.99% availability SLA for VMs is achieved when you run VMs across two or more Availability Zones.
• Two VMs in a single Availability Zone do not meet the 99.99% target (their SLA is lower, e.g., around 99.95% or less depending on configuration).

• Deploy at least two VMs across two different Availability Zones (one VM in each zone, or both in two zones with a load balancer).
• This provides the required zone redundancy and the 99.99% SLA.

• Define the contractor’s deliverables, responsibilities, acceptance criteria, and deadlines.
• Agree on a reporting cadence to monitor progress.
• Allow the local company to use its expertise and manage its own work.

• A: “Under the supervision of the project manager” suggests excessive direct control and is less empowering.
• B: Micromanaging prevents the contractor from functioning independently and is inefficient.
• D: Deploying the contractor’s staff under the PM’s supervision creates a staffing/control arrangement rather than empowering the contracted company.

• The correct permission is Manage Sandboxes (the official Salesforce name; the option in the list is written as “Manage Sandbox,” which is effectively the same idea but the canonical name uses the plural).
• Why: Sandboxes are a lifecycle feature. Only users with the explicit Manage Sandboxes permission can perform create, delete, refresh, or activate actions.
• Why the other options aren’t correct:

• Business
• People
• Governance
• Platform
• Security
• Operations

• Program and project management
• Risk management
• Cloud financial management
• Data governance
• Portfolio management

• Sustainability
• Performance efficiency
• Reliability

• Goal: serving a static website globally with minimal latency.
• Why C works: CloudFront is a Content Delivery Network (CDN) that caches content at many edge locations around the world. When users request the site, CloudFront serves cached copies from the nearest edge location, greatly reducing latency. It also reduces load on your EC2 origin by handling many requests at the edge.
• Why the other options aren’t as good:

• Incidents & alerts — see how the phishing activity was detected, correlated, and investigated.
• Threat Explorer — search for the malicious messages, recipients, URLs, attachments, and campaign activity.
• Email and collaboration reports — assess how many users or messages were affected.
• Remediation details — verify whether messages were quarantined, removed, or otherwise contained.

• Microsoft 365 admin center — general tenant administration.
• Microsoft Entra admin center — identity and access management.
• Exchange admin center — mail-flow and Exchange configuration, rather than full phishing-incident investigation.

• Answer: D. Select an IdP

• Why: To reduce the number of credentials across multiple SaaS apps, implement a single sign-on approach via an Identity Provider. The first step is choosing the IdP; once selected, you can enable SAML (A) or OAuth as supported by apps. Password vaulting (C) is not a true SSO solution, and B is not the foundational step.

• Correct answer: A — The degradation of a service.

• Why: A service request is a formal request from a user for something that is pre-approved and routine (e.g., provisioning a laptop, replacing a toner cartridge). Those are typical service request actions. The degradation of a service, however, is an incident: it describes a problem affecting service quality or availability and is handled by Incident Management (and possibly Problem Management), not as a standard service request.

• Quick note on the other options:

• Security Development Operations (SDO): a security-focused take on DevOps, integrating security into the development pipeline.
• Service Data Object (SDO): a data representation used in some middleware or enterprise apps.
• Software-Defined Overlay (SDO): a networking overlay concept.
• Secure Data Object: a generic data-security term.

• Primary and core nodes: Use On-Demand Instances because the workload is business-critical. These nodes manage the cluster and store/process HDFS data.
• Task nodes: Use Spot Instances in an instance fleet. Task nodes are suitable for interruption because they do not hold essential cluster data and can be replaced or diversified across instance types.
• Terminate the entire cluster after processing: The job runs only about six hours each morning, and EMRFS stores data in Amazon S3. Keeping the cluster running for the rest of the day would waste money.

• A: Using Spot for primary and core nodes risks interruption of the critical cluster.
• C: All On-Demand is reliable but unnecessarily expensive; terminating the cluster helps, but Spot task nodes provide greater savings.
• D: Leaving primary and core nodes running after the task finishes continues to incur costs. Savings Plans also are less appropriate for this intermittent workload.

Why B works

• AWS KMS keys are Regional resources. A normal customer managed key in Region A cannot be used directly in Region B.
• A customer managed multi-Region KMS key (MRK) has related key replicas in both Regions. The replicas share key material and key ID, although each has a Regional ARN.
• With client-side encryption, the application encrypts the data before storing it in S3. Cross-Region replication then copies already-encrypted objects, so S3 does not need to decrypt and re-encrypt them with a different Regional key.

Why the other choices are weaker

• A and C: SSE-S3 uses Amazon-managed S3 keys, not the required customer managed KMS key.
• D: SSE-KMS can work only if the solution creates and configures the appropriate KMS key or multi-Region key replica in each Region. As written, it says to create a customer managed KMS key in each Region, which implies separate keys—not the same KMS key. Replication also requires additional KMS permissions and destination encryption configuration.

• Answer: C — Spot Instances

• Why: The workload is a test environment that can be interrupted and does not need to run continuously. Spot Instances let you bid on unused EC2 capacity at a deep discount, making them the most cost-effective option for interruptible workloads.

• Why not the others:

• Quick tips:

• Correct choice: Box 1 = Yes, Box 2 = Yes, Box 3 = No (Answer: A)

• Box 1: Yes – Microsoft Purview Compliance Manager provides a risk-based compliance score that helps you understand your overall compliance posture. The score reflects how well you’re meeting regulatory requirements and internal policies.
• Box 2: Yes – It also offers step-by-step remediation guidance through actionable “improvement actions.” These guide you to implement fixes and align controls, often with links to the relevant consoles.
• Box 3: No – Compliance Manager is not part of Microsoft Defender. It is part of Microsoft Purview. Defender is a separate security product family, while Compliance Manager is in Purview for compliance risk and remediation.

• Use Purview Compliance Manager to view your compliance score and follow improvement actions.
• Improvement actions provide actionable steps and guidance for remediation.
• Defender and Purview are distinct services; do not confuse their scopes.

• Cross-account access is typically implemented with an IAM role. You create a role in the target account (where the resources live) and configure a trust policy that allows principals from the source account to assume that role.
• Users in the source account then assume the role (via Switch Role in the console or STS:AssumeRole) and receive temporary credentials with the role’s permissions to access the resources.

• IAM group: Groups exist inside a single account; they don’t grant cross-account access.
• IAM tag: Tags are metadata and do not grant access.
• IAM Access Analyzer: It analyzes and identifies public or cross-account access but does not grant access itself.

• In the AWS shared responsibility model, AWS manages the security of the “infrastructure,” including the physical hardware and underlying virtualization.
• The customer is responsible for everything else in the cloud stack: the guest OS on EC2, the NoSQL database software running on it, data, patching the OS, and configuring access controls like security groups.
• So, for a self-managed NoSQL database on EC2, AWS would handle the physical hardware, while you would patch the guest OS and manage DB availability, backups, and security.

• Answer: Internal load balancers (ILB) — option C.

• An ILB has a frontend IP address that must be a private IP within the subnet’s address space. You pick this IP when you create the ILB, and it can be Static or Dynamic.
• Other options don’t require a per-subnet IP:

• The Accrue liability on product receipt flag controls whether a liability is accrued and posted at the time of receiving the item.
• If this checkbox is unchecked, receipts won’t create postings to the Product receipt journal. Enabling it ensures the system posts inventory value and the vendor liability when the item is received.

• Go to the Item model group setup form.
• Enable (check) Accrue liability on product receipt.
• Save.

• The other option, Include physical value, affects how physical value is handled but is not the direct cause of postings to the product receipt journal. If issues persist after enabling accrual, you may need to verify related posting definitions or journal setup.

• The correct answer: C. Tokenization

• Why:

• Why the others are weaker:

• Answer: S3 Inventory report.

• Why: The S3 Inventory report provides a scheduled listing of objects within a bucket, including metadata about each object. When you configure it to include object tagging, you can see tags for each object, and the object keys (which reflect prefixes) and bucket scope are captured in the report. This makes it suitable for auditing and tracking “tags, buckets, and prefixes” across S3 objects.

• What the other options do (not suitable for this purpose):

• Tip: If you need tags in the report, enable the inventory option to include object tagging in the configuration.

• Correct answer: B — From the code repository, modify Startup.cs (in ASP.NET Core you configure the Application Insights SDK in code, not with ApplicationInsights.config).

• Why the other options aren’t correct:

• How to implement fixed-rate sampling (ASP.NET Core):

var builder = WebApplication.CreateBuilder(args); 


    builder.Services.Configure<TelemetryConfiguration>(telemetryConfiguration => 
    { 
        var builder = telemetryConfiguration.DefaultTelemetrySink.TelemetryProcessorChainBuilder; 
        double fixedSamplingPercentage = 10; // 10% sampling 
        builder.UseSampling(fixedSamplingPercentage); 
    }); 


    builder.Services.AddApplicationInsightsTelemetry(new ApplicationInsightsServiceOptions 
    { 
        EnableAdaptiveSampling = false 
    }); 


    var app = builder.Build();

• Correct answer: A
• What this is saying: You need to write a Transact-SQL query that uses REGEXP_SUBSTR to extract the ID from MessageText, and you should apply STRING_ESCAPE(MessageText, 'json') before calling REGEXP_SUBSTR.

• MessageText may contain JSON characters (quotes, backslashes, etc.). Escaping the JSON content first ensures the string you pass to the regex is safe and won’t confuse the regex engine.
• The pattern you apply with REGEXP_SUBSTR would then extract the first substring that matches your ID pattern from the (escaped) text.

• Example (conceptual):

• The question implies REGEXP_SUBSTR is available in this environment; some SQL Server and Fabric contexts don’t expose it natively in all versions. If REGEXP_SUBSTR isn’t available, you’d need an alternative approach (e.g., using built-in regex-like capabilities or CLR/UDFs).
• If you need the ID specifically from the first paragraph, you might first isolate the first paragraph and then apply REGEXP_SUBSTR, or compose a single pattern that anchors to the first paragraph.

1. Create a new AMI or copy the existing AMI while specifying EBS encryption and an appropriate AWS KMS key.
2. This creates an encrypted AMI backed by encrypted EBS snapshots.
3. Copy the encrypted AMI to the destination Region, using a KMS key available there.
4. Launch the application stack from the encrypted AMI.

• B: AWS KMS does not encrypt an existing unencrypted AMI in place. You must create an encrypted copy.
• C: AWS Certificate Manager manages TLS certificates, not EBS or AMI encryption.
• D: Enabling encryption by default affects newly created EBS volumes and snapshots; it does not encrypt an existing unencrypted AMI during copying.

• The correct answer is A: CCTV recordings are not regularly reviewed.

• CCTV is a monitoring/control mechanism. If recordings aren’t reviewed, security events (break-ins, policy violations, equipment tampering) can go undetected and unaddressed.
• Regular review is essential for deterrence, incident response, and forensic evidence. Without it, the entire CCTV control provides little value.

• B (records deleted after one year) affects forensic availability, but it’s a data-retention issue rather than the ongoing effectiveness of the surveillance program.
• C (footage not recorded 24x7) creates gaps in coverage, which is a concern, but regular review of available footage still supports detection; 24x7 coverage is a separate policy/perimeter issue.
• D (cameras not in break rooms) is more about privacy and space planning than core data-center security monitoring.

• Why: After listing all resources, you need to assign who is responsible for each task. A RACI chart (Responsible, Accountable, Consulted, Informed) documents these roles for every activity.

• What RACI means:

• Why the others aren’t suitable here:

• Quick example: Task "Create user authentication module" — Responsible: Developer, Accountable: Tech Lead, Consulted: Security Architect, Informed: PM.

• A private IP address on the virtual network
• A public IP address associated with its IP configuration

• The requirement is a fully managed file server that natively supports Microsoft workloads and file systems and uses the SMB protocol. FSx for Windows File Server is built specifically for Windows workloads, provides native SMB file shares, and supports Windows permissions/Active Directory integration.
• Why the others don’t fit:

• If the account name includes the parsed search string, show the element; otherwise hide it.
• In CSS, to show an element you can set display to a visible value (commonly 'block' for block-level elements), and to hide you set display to 'none'.

• The ternary should map true to a visible display value and false to 'none'.
• Therefore the placeholder should be replaced with 'block' : 'none' (so the code becomes: accountName.includes(parsedSearchString) ? 'block' : 'none').

• There are several typos in the snippet (e.g., quesrySelectorAll, toLOwerCase, Style.display). In a working version you’d also fix those to document.querySelectorAll, account.innerHTML.toLowerCase(), and account.style.display.

• Basic: Self-help only; no technical support or design assessment.
• Developer/Standard: Technical support, but generally not the full proactive architecture guidance required here.
• Professional Direct: Includes proactive guidance and architecture recommendations.
• Premier: Also supports this, but is not the minimum-cost option.

• Multiple AWS accounts: Create a separate account for each department or workload. This provides clear isolation and makes it easier to track each department’s usage and costs for chargeback.
• Consolidated billing: AWS Organizations can combine billing for multiple accounts into one central payer account. The company can still view costs by account while managing payment centrally.

• Placement groups: Control how EC2 instances are physically placed for networking or performance; they do not provide departmental billing separation.
• Edge locations: Infrastructure used by services such as Amazon CloudFront; unrelated to chargeback.
• AWS Config: Records and evaluates resource configurations and compliance; it is not a billing-separation mechanism.

• Elicited and documented customer requirements
• Converted them into clear, measurable specifications
• Validated the requirements with the customer
• Used them as the basis for design, quality checks, and acceptance

• A: Requirements should reflect the customer’s needs—not the supplier’s standards.
• B: Iteration review planning does not replace proper requirements collection.
• D: A retrospective occurs after work is completed and is mainly for process improvement, not initial requirements definition.

• Workspace: Stores notebooks, libraries, jobs, and other project resources.
• Notebooks: Interactive documents containing code, queries, visualizations, and explanations. Common languages include Python, SQL, Scala, and R.
• Clusters: Groups of virtual machines that run Spark workloads. Clusters can be started, stopped, and automatically scaled.
• Data access: Databricks can read from services such as Azure Data Lake Storage, Azure Blob Storage, and Azure SQL.
• Jobs: Automate notebooks or data-processing workflows on a schedule or in response to events.

• A. IDS attack signatures: An IDS primarily detects suspicious network activity and usually alerts rather than directly scanning and blocking uploaded files.
• C. Load balancer: Distributes traffic among servers but does not inspect files for malware.
• D. WAF: Protects web applications from attacks such as SQL injection, cross-site scripting, and some malicious requests. It is not primarily a PDF-malware scanning solution.

• The connecting host keeps the private key securely.
• The destination host stores the corresponding public key in its authorized keys.
• Authentication can occur without a person entering credentials each time.
• SSH also provides encrypted communication and host authentication.

• Biometric: Requires a human user and is difficult to automate.
• Smart card: Often requires user interaction or card access.
• Hard-coded password: Unsafe because passwords stored in scripts or applications can be exposed, reused, or difficult to manage securely.

• ?????? CPU
• ?????????????????
• ??????????????????????????
• ???????????? throughput
• ??????????????????????????????

• A ??????? system software ????????????????????????????????? ??????????????????????????????????
• B ?????????????????????????? ????????????????????????? ?????????????????????????????
• D ????????????????????????? ?????????????? ?????????????????????????????????????????

• Correct answer: B) Context window.

• Why: The context window is the number of tokens the foundation model can process in a single inference. It sets the maximum length of the combined input (prompt) and the model’s output. A larger context window allows more content to be included in one prompt.

• How to use: Check the FM’s context window value and ensure your prompt length plus the desired completion stays within that limit. If needed, summarize or split input across multiple prompts.

• Why the other options aren’t correct:

• Quick tip: Verify the specific FM’s context window for Bedrock, since different models have different token limits.

• Source: on-premises SQL Server Database1
• Destination: Fabric Warehouse Warehouse1
• Connectivity: on-premises data gateway

• Dataflow Gen1: Primarily for Power Query transformations and isn’t the best Fabric-native choice for this copy operation.
• KQL queryset: Queries data; it does not orchestrate copying from SQL Server.
• Notebook: Could perform custom code-based movement, but it is unnecessary and less direct than a pipeline.

• Why: ADS is designed to collect information about on-premises environments to plan migrations. It inventories details like hostname, IP address, MAC address, OS, hardware, and installed software, plus dependency mappings. This data helps you understand your current environment before moving to AWS.

• How it differs from the other options:

• Practical use: Install the ADS agent on on-prem hosts to collect data, then view the inventory in Migration Hub to inform migration planning and sequencing.

• Correct answer: Power BI dataset

• The scenario says the data model already contains several measures and you want to create a report from the existing data with minimal development. Reusing a published Power BI dataset lets you inherit the existing measures and data model, so you don’t have to recreate them.
• How to do it: In Power BI Desktop, use the connector Power BI datasets (Get Data > Power BI datasets) and connect to the existing dataset, then build visuals using the pre-defined measures.
• Why the other options are less suitable:

• Topic: Conditional Access (CA) policy and MFA for Azure management.
• Policy name: Policy1, created with the template “Require multifactor authentication for Azure management.”
• What the template does: It enforces MFA when signing in to manage Azure resources (Azure management) for the users included in the policy.
• Who is included: The question lists Admin1, Admin2, Admin3, and Admin4 as the admins in the tenant. The template’s default scope for this scenario is to apply to those admin accounts (i.e., all four admins unless you explicitly limit the scope).

• CA policy for “Azure management” targets admin sign-ins.
• If the policy includes Admin1–Admin4, all of them must use MFA on their next sign-in (choice D).

• Correct answer: D) Amazon Aurora Serverless

• Aurora Serverless is serverless, so compute capacity scales automatically and can pause during idle periods. This minimizes ongoing administration and you pay only for actual usage, which is ideal for infrequent workloads.
• PostgreSQL on EC2 requires full OS and DB administration.
• RDS for PostgreSQL is managed but still involves provisioning capacity and some maintenance tasks.
• Aurora PostgreSQL (non-Serverless) is managed but requires you to manage capacity, though with some automation; it’s not as hands-off as Serverless for intermittent usage.

• Correct answer: D — AWS Migration Hub

• AWS Migration Hub provides a single location to track the progress of application migrations. It offers a centralized dashboard to view migration status across multiple tools and projects.

• AWS Application Discovery Service helps inventory and map on-prem applications and their dependencies, not a single progress tracker.
• AWS Application Migration Service (formerly SMS) performs the actual lift-and-shift migrations, but isn’t the centralized tracker itself.
• AWS Service Catalog manages catalogs of IT services for self-service deployment, not migration progress.

• Context: You’re configuring a Windows Autopilot deployment profile (Profile1) for Windows 11 devices. The hotspot asks you to pick the correct behavior for two statements based on the profile’s settings.

• Box 1: “can modify the desktop settings only for themselves”

• Box 2: “Cortana settings” with options like computer name, keyboard layout, etc.

• IaaS: You deploy and manage virtual machines, operating systems, disks, and networking. Azure manages the physical datacenter and host infrastructure.
• PaaS: Azure manages the operating system and runtime so you can focus on deploying applications, such as with Azure App Service or Azure Functions.
• SaaS: You consume a complete, provider-managed application.

• Reusing features across different models and teams
• Consistent feature definitions
• Managing feature versions and metadata
• Using features for both training and inference

• SageMaker Data Wrangler: Prepares and transforms data; it is not primarily a shared feature repository.
• SageMaker Clarify: Helps detect bias and explain model predictions.
• SageMaker Model Cards: Documents models, including intended use, risks, and evaluation results.

• The Act requires:

• It does not, as a public obligation, mandate publishing a detailed report on the training data used.
• Also, the Act does not specify a fixed “six months” retention for system logs in a way that would clearly make A required; logs for traceability are implied, but the six-month period is not a defined, universal requirement.

• Answer: D

• The strongest security comes from enforcing access at the storage layer. An IAM policy scoped to the Cognito identity prefix restricts each user to their own S3 prefix (folder), so users can only access their own files regardless of client or server code.
• This per-user isolation reduces risk of cross-user data access and is more robust than UI validation or Lambda/API validation alone.
• Implementation note: attach a policy to the Cognito identity role that allows actions on arn:aws:s3:::your-bucket/${cognito-identity.amazonaws.com:sub}/* (per-user prefix). Ensure TLS in transit and enable at-rest encryption (SSE-S3 or SSE-KMS). Use multipart upload for large files up to 300 MB.