Passed Exam Today AIF-C01

Comprehensive and Detailed Explanation From Exact AWS AI documents:

Feature engineering focuses on:

Creating new features

Selecting the most relevant existing features

Improving model signal and accuracy

AWS ML best practices identify feature engineering as a key driver of predictive performance.

Why the other options are incorrect:

Visualization (A) helps understanding, not feature creation.

Hyperparameter tuning (B) optimizes models, not features.

Data collection (D) expands datasets but does not engineer features.

AWS AI document references:

Feature Engineering Best Practices

Improving Model Accuracy on AWS

ML Model Development Lifecycle

 Sentiment analysis → Text data

 Traffic sign recognition → Image data

 Customer demographics & purchase history → Tabular data

 Stock price forecasting → Time series data

 AWS classifies NLP tasks like sentiment analysis under text data

 Computer vision tasks such as object and sign recognition use image data

 Structured rows and columns (demographics, transactions) are tabular data

 Sequential data indexed by time (prices, metrics) is time series data

Underfitting occurs when a machine learning model is too simple to capture the underlying patterns in the training data. AWS documentation explains that an underfit model performs poorly on both training and test datasets, which directly matches the scenario described.

In this case, the model shows low accuracy during training and evaluation, indicating that it has not learned sufficient relationships from the data. AWS identifies common causes of underfitting as insufficient model complexity, inadequate feature representation, overly aggressive regularization, or insufficient training time.

Underfitting is different from overfitting. Overfitting occurs when a model performs well on training data but poorly on test data, which is not the situation here. Hallucination applies to generative AI outputs, not supervised ML model accuracy. Cross-validation is a model evaluation technique, not a cause of poor performance.

AWS emphasizes the importance of diagnosing underfitting early in the model development lifecycle. Remedies include increasing model complexity, adding relevant features, reducing regularization, or selecting a more expressive algorithm. These steps allow the model to better learn from the data and improve accuracy across both training and test sets.

AWS machine learning best practices clearly associate low performance on both datasets with underfitting, making this the most likely cause of the problem described.

To comply with the company ' s security policy, which restricts each team to access data for only their own customers, creating an Amazon Bedrock custom service role for each team is the correct solution.

Custom Service Role Per Team:

A custom service role for each team ensures that the access control is granular, allowing only specific teams to access their own customer data in Amazon S3.

This setup aligns with the principle of least privilege, ensuring teams can only interact with data they are authorized to access.

Why Option A is Correct:

Access Control: Allows precise access permissions for each team ' s data.

Security Compliance: Directly meets the company ' s security policy requirements by ensuring data segregation.

Why Other Options are Incorrect:

B. Custom service role with customer name specification: This approach is impractical as it relies on manual input, which is prone to errors and does not inherently enforce data access controls.

C. Redacting personal data and updating S3 bucket policy: Redaction does not solve the requirement for team-specific access, and updating bucket policies is less granular than creating roles.

D. One Bedrock role with full S3 access and IAM roles for teams: This setup does not meet the least privilege principle, as having a single role with full access is contrary to the company ' s security policy.

Thus, A is the correct answer to meet the company ' s security requirements.